There is much information on the VEX Forum and various websites concerning PID, and most of them do a better job of explaining how it works and how to implement it than I could hope to achieve. Here’s a post with links to the resources I found useful.
The Pre-autonomous / Initialize part of your competition template can be used for handy stuff, including sensor calibration and autonomous code selection.
Here are a few new (to us) programming concepts, courtesy of George Gillard. Read on for breaking in auton, slowing down as you approach a target, and an elegant button coding scheme.
Here’s a simple programming concept that was new for me this year, which grew out of moving to RobotC. However, this method can be used in (and recommended for) any language; examples are given here for RobotC and easyC.
This post is part of my journey from easyC to RobotC. I will post things here as I learn them, that might be helpful to others who are also new to this language. This week, I learned how to program a joystick to drive a chassis. Unlike easyC, the standard text-based RobotC does not have […]
If you’re new to using sensors in your autonomous code, you’ll want to read this. A kill timer can break your robot out of a while loop if it’s been running past a reasonable length of time, preventing gear-grinding, stalling, and the like.
The VEX yaw rate gyro sensor has exceedingly little official documentation or instructions. I have tried to collect all of the general information I can find from the VEX Forum along with my personal experience and put it here in one place. [This post does not include specific programming instruction.]
Jumper clips and LEDs are both plugged into digital ports on the cortex and can be used for autonomous code selection, debugging, or an alert system.
The VEX line tracker is used to follow the white tape lines on a competition field during autonomous. This post covers it all: how they work, how to install them on your robot, testing, programming (including easyC), resources, and troubleshooting.
Special thanks to Griffin Tabor who provided this code for how to calibrate your line trackers when you put your robot on the field (before the match starts) to account for ambient lighting conditions.