Learning robotc driver#

Important to note is that motor port numbers are not accessed as they would be in a regular array instead, ROBOTC has predefined constants corresponding to each motor port. To change the power level of a particular motor, use this syntax: motor = your power level. Power levels for motors can range from -127 to 127. The value assigned to any given motor port is constantly read and output by the program to the actual motor hardware. In ROBOTC, the value of power outputs to every motor is stored inside an array called motor. The goal of any robot program is to get the robot to do something, most often move a motor.

Learning robotc driver#

Driver control runs on a loop until the robot is powered off and accepts commands from the driver and operator via joystick. The logic behind these instructions can vary from a simple linear set of commands to complex branching decision logic. Autonomous runs once, executing a series of commands allowing the robot t follow a preset list of instructions. Pre-autonomous runs once before startup and is used to configure user variables for instance, if you have a global variable and you want to decide its value at the very beginning you should do so in pre-autonomous. Commands to the robot go inside these functions. VirtualVEX has these tasks predefined in the program template (as of Alpha 4, only driver control is available). ROBOTC programs are generally split into 3 functions or tasks: pre-autonomous, autonomous, and driver control. This is not an appropriate resource for those wishing to adopt ROBOTC full-time for their physical VEX robot the best guide to learning ROBOTC can be found at the official website ( Furthermore, since ROBOTC is based off the C programming language, a rudimentary knowledge of C is required.

This is intended for teams that do not program in ROBOTC (since some teams use Easењњ) but still want to customize the drive controls of the virtual robot. This section covers some basic concepts of the ROBOTC API.