Data Sheet

VEX Robot Troubleshooting Flowcharts
Page 1 of 4
Is the
Game LED
flashing?
Do all
LEDs
flash Red in a
repeating
cycle?
Is
Cortex
VEXnet LED
on?
Is the
Robot LED
blinking?
Fast
or slow
blink?
Is the
VEXnet LED
green?
Does
the Cortex
turn on?
Start
Single
or double
blink?
Do all
motors work
correctly?
Is the
robot lagging
or slow
to respond?
Is the
Robot LED on
the Cortex
consistently
red?
Check batteries and power connections. The battery connectors on the
Cortex can become bent open over time. If necessary, bend the connectors
back in to ensure a solid power connection.
Low or missing 9v backup battery. If in a
competition setting, install a fully charged
9v backup battery before continuing
Programming error. Try switching to the
Default Code which can be found within
your programming software. If this xes the
issue, return to your user code and attempt
to isolate the issue to a particular line of
code. The best way to do this is to comment
out various sections at a time and test after
each change.
If the units are still not correctly linked, refer to the
VEXnet Troubleshooting Flowchart in Section 3.
Robot battery is dead. Charge
or replace batteries before
continuing.
Fast
Single
Double
Slow
YES
YES
NO
NO
NO
NO
NO
NO
NO
NO
NO
YES
YES
YES
YES
YES
YES
YES
Update the VEXnet Firmware (Master CPU Firmware
for ROBOTC users) on both the Cortex and the
Joystick using the Firmware Upgrade Utility included
with your programming software. If you do not have
programming software this utility is available on the
Downloads page at vexrobotics.com.
The Cortex is currently running an Autonomous Only user code.
If you want to use the VEXnet Joystick, download a VEXnet
Enabled project such as the Default Code using the USB A-A
Cable.
If your robot seems slow to respond while running user code, it is likely
that there is something in your program that is slowing down the loop time.
Check your code for any slow-to-execute commands (such as updating an
LCD screen or printing to a debugging window) that are set to run on every
cycle of a loop. A slow response time can also be the result of having too
many background tasks running at the same time. For further help with this
issue, we recommend posting a question on the VEX Forum (vexforum.com).
For questions regarding a competition robot, see the Competition Robot
Troubleshooting Flowchart in Section 2. If you need further assistance, you
can refer to the other guides or post a question on the VEX Forum (vexforum.
com). You can also contact VEX Technical Support by phone at +1-903-453-
0802 or email support@vexrobotics.com. Please note: for programming ques-
tions contact the developer of your programming software.
Wait 20 second…
Refer to the Motor
Troubleshooting
Flowchart in Section 4.
1. General Robot Troubleshooting Flowchart
08/11

Summary of content (4 pages)