HOW TO USE ROBOTC CODE

An example of a completed Motor setup can be found in the gallery above. IMPORTANT NOTE: You may have to reverse a motor, depending on how it is positioned on the robot.Д¤. In the 'Type' drop-down, select what type of motor or sensor you are using. Enter a name for the motor and/or sensor beside the correct port number. You will have many tabs to choose from, to setup the motor ports, navigate to the 'Motors' tab, for Analog Sensors, navigate to the 'VEX 2.0 Analog Sensors 1-8' tab, etc.ДЈ. Go to 'Robot > Motors and Sensors Setup'Дў. Essentially, make sure your robot has at least a chassis with motors on it before you start programming!ДЎ.

HOW TO USE ROBOTC CODE

If you do not setup these motors, it will be a pain to change all of your motor names in your entire code once that is done. The first thing you should do with any RobotC code, is setup your motors and sensors, so that we can begin to program a drive. If these values are changed incorrectly, your program WILL NOT work! Motor and Sensor Setup: IMPORTANT NOTE: When first opening the Competition Template, do not change ANY values, unless you know EXACTLY what you are doing. To open your first competition template, where we will do all of the programming, go to 'File > New > Competition Template'. Once this has been selected, we are ready to start programming a competition template! Opening your first Competition Template: To do so, go to 'Robot > Platform Type > VEX Robotics > VEX 2.0 Cortex'. The first thing we need to do, after activating the license, is to make sure that the proper platform is selected. In other words, light_blue is an index into the motor array.*Click images to enlarge* Selecting the right platform: The correct way to refer to this motor in code is motor. So, light_blue is not an 'alternate name' for motor, and in fact neither of those names are correct.

(Other things not relevant to this question).

In other words, use open loop control instead of PID control.

Add a function that gets called when you assign a value to motor, which converts that value directly to a power-level signal understood by Vex 393 (and outputs this signal on port7).

Declare a variable of type tMotor and store it in motor.

This tells the preprocessor to generate some code that does the following: In your case, this is the motor config line that you wrote: #pragma config(Motor, port7, light_blue, tmotorVex393, openLoop) The code generated by the preprocessor is saving you from writing a lot of setup code yourself, but it is also making some normal-looking variables do some unexpected things.

The preprocessor is why you have access to the motor array (which you didn't need to declare before using), and why assigning a value to a motor causes your real-world motors to move (which does not happen when assigning to a 'normal' variable). In other words, there is a hidden step - preprocessing - between the code you wrote and the code that the compiler sees. The #pragma config( ) is actually doing a lot of heavy lifting for you because it is a ' preprocessor directive'. I think I see where you're confused, and you're correct in noticing that the motor variables are a little different than regular variables. It's hard to guess what it is you are trying to actually do Motor = 20 // will actually move light_green since testThing function changed its value #pragma config(Motor, motorB, light_green, tmotorNXT, PIDControl, encoder) If i was to look at your code, and accept its functionality as literal then the following would work #pragma config(Motor, motorA, light_blue, tmotorNXT, PIDControl, encoder) The old definitions are temporarily maintained here as well until the new implementation is confirmed So they are automatically configured by the compiler which has better utilities for managing and circuit board type has its own set of 'enum names' and it was becoming too hard to manage them in

the actual 'enum' values for 'tMotor' are automatically defined by the ROBOTC compiler. The actual type of a tmotor is an enum (and used like an int) and the definition can be found in RobotCintrinsics.c included with the product. Your code is very close something like this would work fine #pragma config(Motor, motorA, light_blue, tmotorNXT, PIDControl, encoder)

The #pragma is more like a #define in terms of names, as opposed to a variable declaration.

How to use robotc