Tutorials/Getting Started

System Requirements:
Intel® Pentium® processor or compatible, 800 MHz minimum Windows XP Professional or Home Edition with Service Pack 2 or greater 256MB of RAM minimum Up to 30MB of available hard disk space 1 available USB port Compatible Bluetooth adapter (optional)

ROBOTC will not run natively in any other operating system other than Microsoft Windows. ROBOTC will run with a Virtualization client on a Apple Macintosh. ROBOTC has been tested with VMWare Fusion, Parallels Desktop, and Apple's Boot Camp. You will still need to download/install device drivers found on your purchased CD or on the ROBOTC website.

To uninstall ROBOTC, follow these steps:

1. Open the Control Panel from your "Start Menu"

2. Inside of the Control Panel, select "Add or Remove Programs"

3. Navigate through the "Add or Remove Programs" list until you find your version of ROBOTC that you wish to uninstall. Press the "Remove button"

4. Windows will start the uninstall process. When the window below disappears and you are returned to the "Add or Remove Programs" list, ROBOTC has been successfully uninstalled.

1. Double click on the ROBOTC installer. You will be presented with the Installshield installer for ROBOTC. Click "Next" to proceed.

2. Before you can proceed, you must read over the accept the End User License Agreement. Click "I accept" and then the "Next" button to proceed.

3. Choose where you would like to install ROBOTC to. By default, ROBOTC is installed to your "Program Files" folder. Click "Next" to proceed.

4. The installer will ask you to confirm your settings. If everything looks correct, click "Install" to being the installation process.

5. The installer will begin copying files from the installer to your computer. Please wait until this is complete.

6. When the installation is complete, the install will inform you of this. Click "Finish" to complete your install.

7. Double click the "ROBOTC for Mindstorms" icon to launch ROBOTC.

To activate ROBOTC, you will need the License ID and Password that was sent to you during the purchase process.

• If you purchased a ROBOTC license online, the License ID and Password were sent to the email address specified.
• If you ordered the CD-ROM version of ROBOTC, the License ID and Password are printed on the CD label.

If you are Activating the ROBOTC license on computers with internet access, follow the Activation instructions below. If you are activating the ROBOTC license on computers without internet access, skip to Activate by Web instructions.

NOTE: ROBOTC must be activated on each individual computer.

Follow these steps to activate on a computer with internet access:

1. Open ROBOTC and select "Activate ROBOTC" from the start-up prompt.

2. Select "Activate ROBOTC for MINDSTORMS Online"

3. Enter in your License ID and Password that you received via emaill. Click the "Continue" button to proceed.

4. ROBOTC will communicate with the activation server via the internet to verify your License ID and Password.

5. ROBOTC is activated and ready for use. Click Continue to use ROBOTC for MINDSTORMS.

Note: You will need to use a separate computer with Internet access in step 4 at this activation process. You must repeat this process on each computer without internet access.

1. Open ROBOTC and select "Activate ROBOTC" from the menu.

2. Select "Activate by Web"

3. Two user codes will be displayed. Copy both of these down. Take these codes with you to a separate computer with Internet access.

4. At a separate computer with internet access, visit http://www.robotc.net/register. Enter your License ID and Password that you received via email and click "Next."

5. Enter User Code 1 and User Code 2 that you copied down in step 3. Click "Next" to proceed.

6. A Registration code will be displayed. Write this down and return to the original computer on which ROBOTC is installed.

7. Enter the Registration code from step 6 into the "Activation Code 1" field.
Note: Leave Activation Code 2 blank.

8. ROBOTC will be activated and ready for use. Click Continue to use ROBOTC.

• LEGO Mindstorms RCX
• LEGO Mindstorms NXT
• LEGO Mindstorms NXT + TETRIX
• Robot Algebra (NXT)

Before you use ROBOTC, make sure to select which platform you are currently using.

Changing Platform Type: Open the "Robot" menu in ROBOTC and hover your cursor over the "Platform Type" menu option. This will open up the platform select menu. Select the platform you wish you use with ROBOTC. You can change the platform type at any time.

Note: If you are using an Arduino 2560, make sure you take a look at the follow page on how to upgrade your bootloader.

Note: Downloading ROBOTC's Firmware will not remove the ability to use the Arduino "Wiring" Open Source language.

Join the ROBOTC for Arduino discussion on the ROBOTC.net Arduino Forums

Additional help and support can be found at [1] or by e-mailing support@robotc.net

You can update the firmware on the NXT directly from the ROBOTC application. To update the firmware, follow these instructions:

Prerequisite: Make sure that your NXT is connected to your computer via USB and is powered on with a fully charged battery.

1. Open the "Robot" menu and select "Download Firmware."

2. Since NXT is set as the Platform Type, the "NXT Brick Download" screen will appear. From this screen you can rename your NXT and update the firmware. Make sure that your NXT appears under the "NXT Bricks Currently Connected via USB" list before proceeding. If the NXT does not appear, make sure it is connected via USB, powered on, and that the NXT USB driver is installed. Then click the "Refresh Lists" button to see if your brick can be found.

3. To start downloading firmware, click the "F/W Download Button."

4. After clicking the "F/W Download" button, you will see the "Select NXT firmware file" file selection screen. ROBOTC will automatically open to the Firmware folder and show you all of the available firmwares available for the NXT. NXT firmware files have the extension ".rfw". Select the highest numbered firmware file that follows the "NXTXXXX.rfw" format. Once that firmware file is selected, click the "Open" button to start downloading the firmware to the NXT.

Note: Always select the highest version number available with the "NXT" prefix.

5. As the firmware is downloading, your NXT will shut itself off and turn itself back on. Once the firmware has been successfully downloaded, you should see "Firmware download completed" on the "NXT Brick Download" screen, under the "Message Log". Your NXT is now ready to be used with ROBOTC.

To access the sample programs, go to the "File" menu and select "Open Sample Program".

The sample programs folder is organized by topic. ROBOTC will automatically open the sample programs folder for the robot platform you have selected.

Just double click on one of the sample programs to open it up and learn more about ROBOTC programming.

ROBOTC also contains a compiler for turning user generated code into a byte-code language that the different robot platforms can understand. To run the compiler, go to the "Robot" menu and select "Recompile Program" or hit F7 on your keyboard.

When the compiler runs, ROBOTC will check your program for errors and warnings that would cause it to run improperly on the robot. Rather than send broken code to your robot, ROBOTC informs you of these errors.

In the example below:

• The reserved word 'motor' was incorrectly typed as 'Motor', generating a warning. A warning tells the user that they've created an error, but ROBOTC is able to correct it when the program is sent to the robot. A program with warnings will compile successfully, but users should use good programming practice to avoid warnings. Warnings are denoted by a yellow "X".
• The code on line 5 is missing a semicolon, which is generating an error. An error will prevent the program from being sent to the controller. In this example, ROBOTC is informing the user they left a semicolon out of their program which is preventing the program from being compiled. Errors are denoted by a red "X".
  

Once your program has successfully compiled, you can send the program to the controller by selecting the "Compile and Download Program" option under the "Robot" menu or hitting F5 on your keyboard.

Once the download starts, a "Download Progress" window will appear. This window shows the transfer status of the compiled byte-code to the robot.

Once the download finishes, the built-in debugger launch. Some windows will launch, such as the "NXT Device Control Display" and the "Program Debug" window. Others may launch docked into the interface, such as the "Global Variables" screen. You can start your programs execution by clicking the "Start" button on the "Program Debug" window. Learn more about these windows in the 'Debugger' section of the help file.

Sensor Port Configuration Use these drop down menu items to set the sensor type and sensor mode for each of the four sensor ports. When this utility is first opened, it will interrogate the NXT to get the current settings of these values. The “Fast I/O” check-mark is read-only. It is calculated from the type of sensor. If you want to test a LEGO ultrasonic tester with this utility, do not set the type to “SONAR”. This will activate the built-in firmware device driver which will periodically poll the value of the ultra-sonic sensor. The device driver does not expect any other application to send I2C messages to the sensor! Instead set the type to “I2C Custom Slow”.

All I2C Fast Sensor/All I2C Slow Sensors Use either of these two buttons to quickly configure all four sensor ports as a custom I2C sensor. “Fast” sensors will use the ROBOTC firmware capability to transmit I2C messages at five times the speed found in the standard LEGO supplied firmware. Fast mode generally works with all third party sensors, slow mode is required for the LEGO ultrasonic sensor. The difference is that most 3rd party sensors include a microprocessor that has I2C messaging support in hardware and can keep up with the faster ROBOTC messaging rate. Slow sensors have a “bit-banged’ implementation and cannot keep up.

Firmware Version Configure these parameters for either standard LEGO firmware or ROBOTC firmware. Standard firmware does not support fast mode signaling and will always try to send a I2C message three times before reporting failures. Trying three times can easily mask intermittent transient errors. The number of total tries can be user configured in the ROBOTC firmware. The default value is a total of three tries. Setting the number of retries to zero is useful to ensure transient errors are not masked.

Port Selects which of the four ports on the NXT the message will be sent to.

Output Message The hexadecimal bytes of the message to be sent to the sensor

Reply Len (Length) The length of the reply expected from the sensor in bytes

Reply The reply returned from the sensor in hedadecimal (and converted to ASCII)

Select A checkbox to determine if the selected message should be included or excluded from the test cycle.

Once/Continuous Buttons These buttons select whether a single test cycle or continuous testing should be performed.

Verify Write If checked, the NXT will send an ACK message to check if the I2C message was successfully sent to the NXT. The "Failed" text box will return a count of the number of failed messages.

Count A text box containing the number of messages sent in total.

Bus Errors Number of bus errors encountered during error transmission. Bus error is detected by the I2C firmware and usually indicates an attempt to send an I2C message to a sensor that does not support I2C messaging.

No Reply Number of messages sent to the I2C message that did not recieve a reply from the sensor.

Diff Msg (Different Message) Number of different messages recieved from the I2C sensor... this counter will not increment when the same message is recieved from the I2C sensor in succession.

1. Open the Preferences menu under the "View" menu.

2. Select the serial COM port that your controller is attached to from the Communications Port drop-down menu. Click 'OK' to save your settings.
Be sure to also select the correct Platform with the "Platform" drop-down menu.

To update the VEX Master Firmware:
1. Open ROBOTC for IFI. Ensure that your VEX controller is connected and turned on.

2. Go to View > Preferences > Detailed Preferences. On the Platform tab, ensure that VEX 0.5 Microchip is selected as the Platform, alsong with the Prolific USB-to-Serial option as the Communication Port.

3. Go to Robot > Download Firmware > Master CPU Firmware > Standard File to download the Master Firmware.

4. A Download Progress window will appear. When the window closes, the download is complete.

Prerequisites:

• Connect the VEX to your computer and power it on.
• Make sure VEX 0.5 Microchip is selected as the Platform Type

1. Open the Robot menu, select "Download Firmware", "ROBOTC Firmware", and then "Standard File".

2. A Download Progress window will appear. When the window closes, the download is complete.

3. Power cycle the VEX so that the new firmware will take effect.

To access these sample programs, open the "Sample Programs" folder by going to the "File" menu and selecting "Open Sample Program."

Inside of the sample programs folder, there are a number of samples organized by topic. ROBOTC will automatically open the sample programs folder of the platform you currently have selected.

Just double click on one of the sample programs to open it up and learn more about ROBOTC programming.

ROBOTC also contains a compiler for turning this user generated code in a byte-code language that the different controller platforms can understand. To run the compiler, access the compile function from the "Robot" menu.

When the compiler runs, ROBOTC will check your program for errors and warnings that would cause your program to not run properly on the robot. Rather than send this broken code to your robot, ROBOTC will inform you of these errors so they can be corrected.

In the example below:

• The reserved word 'motor' was incorrectly typed as 'Motor', generating a warning. A warning tells the user that they've created an error, but ROBOTC is able to correct this error itself when the program is sent to the controller. A program with warning will compile successfully, but users should use good programming practice to avoid warnings. Warnings are denoted by a yellow "X".
• The code on line 5 is missing a semicolon, which is generating an error. An error will prevent the program from being sent to the controller. ROBOTC will do its best to explain what the error to assist the user. In this example, ROBOTC is informing the user they left a semicolon off a line of their program which is preventing the program from being compiled. Errors are denoted by a red "X".
  

Once your program has successfully compiled, you can send the program to the controller by clicking the "Compile and Download Program" option under the "Robot" menu. Note: Your robot must be turned on and connected to the computer before you can download a program.

Once the download starts, a "Download Progress" bar will appear. This bar will show the status of the transfer of the compiled byte-code to the controller.

Once the download starts, a "Download Progress" bar will appear. This bar will show the status of the transfer of the compiled byte-code to the controller.

Once the download finishes, ROBOTC's built in debugger will be launched. There will be a number of windows that launch, such as the Global Variables window, the Devices window and the Program Debug window. You can start your programs execution by clicking the "Start" button on the "Program Debug" window. Learn more about these windows in the 'Debugger' section of the help file.

To download and update the VEX 2.0 Cortex Master Firmware:

Place your VEX Cortex in "Bootload" Mode Placing your VEX Cortex in "Bootload" mode is necessary before downloading the Master CPU Firmware. Keep the Cortex powered OFF. Plug one end of the USB A-to-A Cable into a USB port on your computer. Do not plug the other end into the Cortex. Note: The order detailed in these steps is crucial. When the Cortex is powered on, it immediately tries to determine how it is connected (over VEXnet, USB, or no connection). Some power is provided to the Cortex over USB, which will allow it to determine that it is connected to your computer.

Use a paperclip or a 5/64 Allen Wrench to press and hold in the CONFIG button on the Cortex.

While pressing in the CONFIG button, connect the other end of the USB A-to-A cable to the USB port on the VEX Cortex. Keep the CONFIG button pressed in for an additional 5 seconds.

Remove the Allen Wrench or paperclip, releasing the CONFIG button. After a few seconds, the ROBOT and GAME lights should blink green.

Make sure a 7.2V Robot battery is connected and move the POWER switch on the Cortex to the ON position. Your setup should resemble the one in this picture, with the USB A-to-A cable connecting your computer and the VEX Cortex, and the 7.2 Volt Robot Battery powering the VEX Cortex. Note (Optional): You can connect two motors to MOTOR Ports 2 and 3 for testing a sample program later in the sequence. You can connect 3-wire motors directly, or the newer 2-wire motors using Motor Controller 29 cables.

Platform Type and Communication Port
Specify that you are using the Cortex and how it is connected to your computer in ROBOTC. Go to Robot > Platform Type > Innovation First (IFI) and select "VEX 2.0 Cortex" or "Natural Language (VEX Cortex)".

Then go to View and choose Select Communication Port.

A new window will appear. From the Communications Port dropdown list, make sure that "Automatic Selection" or the "USB Wired Cable" option are selected. If you plan on programming your robot wirelessly over VEXnet, keeping "Automatic Selection" chosen is recommended. Press OK to save your choice.

Downloading Master Firmware
Go to Robot > Download Firmware > Master CPU Firmware and select "Standard File" to download the latest Master CPU Firmware to your robot.

A Download Progress window will appear and begin the download process.

When the window closes, the firmware download is complete. A ROBOTC Message will appear, and remind you to also download the ROBOTC Firmware.

Note: You only need to download the Master CPU Firmware once, when you first start using a VEX Cortex with ROBOTC, or when you upgrade to a newer version of ROBOTC. Switching programs or download methods does not require a re-download.

Once the Master CPU Firmware finishes downloading, the Cortex will be recognized as a new device, and Windows may ask you to verify the software installation for the Cortex. Press Continue or Continue Anyway to complete the installation.

Note: Once the device driver installation is complete, you should no longer need Administrative privileges on your computer; you should be able to download Master CPU Firmware, ROBOTC firmware, and ROBOTC programs in a permissions-restricted account. Only future updates to ROBOTC and theVEX Cortex Device Driver will require Administrative privileges.

Prerequisites:

• Connect the Cortex to your computer (over VEXnet or USB) and power it on
• Make sure VEX 2.0 Cortex is selected as the Platform Type

Go to Robot > Download Firmware > ROBOTC Firmware and select "Standard File" to download the ROBOTC Firmware to your robot.

A Download Progress window will appear and begin the download process.

Once the Download Progress window closes, the ROBOTC Firmware download is complete. Your VEX Cortex is now ready to be programmed in ROBOTC over the USB A-to-A cable.

Note: You only need to download the ROBOTC Firmware once, when you first start using a VEX Cortex with ROBOTC, or when you upgrade to a newer version of ROBOTC. You do not need to re-download the ROBOTC firmware every time you want to download code.

If you are also using the VEXnet Joysticks, you will need to update its firmware and establish a wireless VEXnet link between it and the Cortex.

You will need to update the firmware on the VEXnet Joystick to ensure that it will operates correctly.

Placing your VEXnet Joystick in "Bootload" mode is necessary before downloading the VEXnet Joystick Firmware. Keep the VEXnet Joystick powered OFF. The process of placing your VEXnet Joystick in Bootload mode is easier if you start by plugging one end of the USB A-to-A cable into the device. Keep the VEXnet Joystick turned OFF, and do not plug the other end of the USB A-to-A cable in yet.

Use a paperclip to press and hold in the CONFIG button on the front of the VEXnet Joystick.

Keeping the CONFIG button pressed in, connect the other end of the USB A-to-A cable to your computer.

After a few seconds, release the CONFIG button. The ROBOT and GAME lights will blink green.

Downloading VEXnet Joystick Firmware
Go to Robot > Download Firmware > VEXnet Joystick Firmware and select "Standard File" to download the latest VEXnet Joystick Firmware to the controller.

A Download Progress window will appear and begin the download process.

When the window closes, the firmware download is complete.

Note: You only need to download the VEXnet Joystick Firmware once, when you first start using it with ROBOTC, or when you upgrade to a newer version of ROBOTC.

VEXnet features include:

• Easy to connect (No IP addresses, MAC addresses, passwords, or special security modes)
• Multiple layers of security built-in and always on
• No wireless access point needed; each VEXnet pair makes its own private network
• Hundreds of robots can operate at once; every VEXnet robot has a hidden unique ID
• Optional tether for wired communication
• Optional 9V battery backup to maintain wireless link during a main 7.2V power loss
• LED scheme displays the status of the Robot, VEXnet link, and Game (Competition Mode)

1. Begin by connecting both the Cortex and VEXnet Remote Control to charged batteries.

1a. Connect a 7.2V robot battery to the Cortex, but do not power it ON.

1b. Remove the battery cover plate on the remote control. Install 6 AAA batteries, and replace the battery cover plate. Do not power the remote control ON.

2. Tether the USB port on the VEXnet Remote Control to the USB port on the Cortex using a USB A-to-A cable.

2a. Plug one end of the USB A-to-A cable into the USB port on the VEXnet Remote Control.

2b. Plug the other end of the USB A-to-A cable into the USB port on the VEX Cortex.

3. Power the Cortex ON. After a few seconds, ROBOT and VEXnet LEDs will blink green, indicating that the Cortex and VEXnet Remote Control have successfully paired

3a. Turn the Cortex ON

3b.The ROBOT and VEXnet LEDs will blink green once the Cortex and VEXnet Remote Control have successfully paired. The GAME LED will also blink green if a program is stored on your Cortex.

4. Turn the Cortex OFF.

5. Remove the USB A-to-A cable from the VEXnet Remote Control and Cortex.

6. Insert VEXnet USB Keys into both the VEXnet Remote Control and Cortex.

Note: It does not matter which VEXnet USB Key you insert into the Cortex versus the VEXnet Remote Control. Pairing the Cortex and VEXnet Remote Control establishes the link; the VEXnet USB Keys act as antennas for the link.

7. Power the Cortex and Remote Control ON. After roughly 15 seconds, the ROBOT and VEXnet LED’s will blink green, indicating that the VEXnet communication link has been established.

7a. Turn the Cortex ON

7b. Turn the VEXnet Remote Control ON

7c. After roughly 15 seconds, the ROBOT and VEXnet status LEDs will start blinking green. With the VEXnet link established, you should power OFF your Cortex and VEXnet Remote Control to preserve battery.

Troubleshooting

Issue: Slow blinking green ROBOT light on the Cortex Solution: Download the Cortex Master Firmware using ROBOTC.

Issue: Slow blinking ROBOT green light on the VEXnet Remote Control Solution: Push and hold CONFIG button for about 5 seconds, until the status LEDs starts blinking green. Release it, wait for another 5 seconds, and then turn the VEXnet Remote Control OFF and then back ON. If that fails, download the VEXnet Joystick Firmware using ROBOTC.

Issue: Yellow or red ROBOT light on the Cortex Solution: Make sure you are using fully charged Robot battery.

Issue: Yellow or red ROBOT light on the VEXnet Remote Control, even though they are both green on the Cortex. Solution: Power cycle both the VEXnet Remote Control and CORTEX.

The VEXnet Remote Control includes two joysticks (each having an X and Y-axis), 8 buttons on the front, and 4 additional trigger buttons on the top. Inside, there is also 3-Axis accelerometer, capable of providing X-Y-Z acceleration values. Values from the joysticks, buttons, and accelerometer are sent as a constant stream of information over VEXnet to the robot, enabling a user to control the robot in real-time. To ensure that the VEXnet Remote Control sends out accurate joystick values, the joysticks must be calibrated before their first use, and after any firmware updates are applied to the remote control.

You will need:

• A VEXnet Remote Control with batteries
• A VEX Cortex with robot battery
• A small Allen wrench (1/16” or smaller) or paper clip

1. Power on the VEXnet Remote Control and VEX Cortex. Allow them to sync over VEXnet.

2. Press and hold the 6U trigger button.

3. While keeping the 6U trigger button pressed in, use your Allen wrench or paper clip to press in the internal CONFIG button until the JOYSTICK LED blinks red and green.

3a. While still pressing in the 6U trigger button, use an Allen wrench or paper clip to press in the CONFIG button.

3b. Once the JOYSTICK LED begins to blink red and green, release both the 6U and CONFIG buttons.

Important - Time Sensitive Instructions
There is a 10 second time limit to complete steps 4 and 5. If they are not completed in time, the calibration process will timeout and the VEXnet LED will blink red briefly.

4. Move both joysticks through their full ranges of motion. When the remote control detects that the joysticks have been fully rotated, the JOYSTICK LED stops blinking red and green, and switches to a solid green.

4a. Move the joysticks through their full ranges of motion - Up, Down, Left, Right, and in a circle.

4b. Once the remote control detects that the joysticks have been fully rotated, the JOYSTICK LED switches to solid green, indicating that you can stop moving the joysticks.

5. Press the 8U button to save the joystick calibration on your remote control. The JOYSTICK LED will blink green for a few seconds.

Additional Information

• If the calibration is not saved, the process will timeout after 10 seconds and the VEXnet LED will blink red.
• To cancel a calibration, press the 7U button. The calibration process will be discontinued and the VEXnet LED will blink red.
• Once the calibration is discontinued or saved, all of the remote control LEDs will resume their normal function.
• The joysticks must be calibrated any time the firmware on the remote control is downloaded.

To access these sample programs, open the "Sample Programs" folder by going to the "File" menu and selecting "Open Sample Program."

Inside of the sample programs folder, there are a number of samples organized by topic. ROBOTC will automatically open the sample programs folder of the platform you currently have selected.

Just double click on one of the sample programs to open it up and learn more about ROBOTC programming.

ROBOTC also contains a compiler for turning this user generated code in a byte-code language that the different controller platforms can understand. To run the compiler, access the compile function from the "Robot" menu.

When the compiler runs, ROBOTC will check your program for errors and warnings that would cause your program to not run properly on the robot. Rather than send this broken code to your robot, ROBOTC will inform you of these errors so they can be corrected.

In the example below:

• The reserved word 'motor' was incorrectly typed as 'Motor', generating a warning. A warning tells the user that they've created an error, but ROBOTC is able to correct this error itself when the program is sent to the controller. A program with warning will compile successfully, but users should use good programming practice to avoid warnings. Warnings are denoted by a yellow "X".
• The code on line 5 is missing a semicolon, which is generating an error. An error will prevent the program from being sent to the controller. ROBOTC will do its best to explain what the error to assist the user. In this example, ROBOTC is informing the user they left a semicolon off a line of their program which is preventing the program from being compiled. Errors are denoted by a red "X".
  

Before downloading code to your robot, you should verify that the "VEX Cortex Download Method" matches your setup.

Option 1: Download Using VEXnet or USB
With this option selected, ROBOTC will download ROBOTC firmware and programs to your Cortex using a VEXnet or USB connection. In this mode, when the Cortex is powered ON it will look for a VEXnet or USB connection before running your program. (The Communication Port > Automatic Selection option in the ROBOTC Preferences should be selected if you plan on switching between VEXnet and USB as your download method.)

Option 2: Download Using USB Only
With this option selected, ROBOTC will download firmware and programs to your Cortex using only the USB connection. In this mode, when the Cortex is powered ON it will immediately run your program. This option is NOT recommended if you are using the VEXnet Joysticks to download to the Cortex, or remotely control it.

Option 3: Download for Competition (VEXnet)
This option disables the ROBOTC debugger, and is not recommended for classroom use.

Note: Switching between Download Modes may require you to power cycle your Cortex before it takes effect.

Once your program has successfully compiled and you've selected the appropriate Download Method, you can send the program to the controller by clicking the "Compile and Download Program" option under the "Robot" menu. Note: Your robot must be turned on and connected to the computer before you can download a program.

Once the download starts, a "Download Progress" bar will appear. This bar will show the status of the transfer of the compiled byte-code to the controller.

Once the download finishes, ROBOTC's built in debugger will be launched. There will be a number of windows that launch, such as the Global Variables window, the Devices window and the Program Debug window. You can start your programs execution by clicking the "Start" button on the "Program Debug" window. Learn more about these windows in the 'Debugger' section of the help file.