VEX Robot Troubleshooting Flowcharts

1. General Robot Troubleshooting Flowchart

Start

Does Check batteries and power connections. The battery connectors on the
the Cortex Cortex can become bent open over time. If necessary, bend the connectors
turn on? NO back in to ensure a solid power connection.

YES

Is the
Robot LED on Is the Fast Low or missing 9v backup battery. If in a
the Cortex Robot LED or slow competition setting, install a fully charged
YES blinking? YES blink? Fast
consistently 9v backup battery before continuing
red?
NO Slow
NO
Robot battery is dead. Charge
or replace batteries before Programming error. Try switching to the
continuing. Default Code which can be found within
your programming software. If this fixes the
Do all Single issue, return to your user code and attempt
LEDs or double to isolate the issue to a particular line of
flash Red in a blink? Single code. The best way to do this is to comment
YES out various sections at a time and test after
repeating
cycle? Double each change.

NO Update the VEXnet Firmware (Master CPU Firmware

for ROBOTC users) on both the Cortex and the
Joystick using the Firmware Upgrade Utility included
Is
Is the with your programming software. If you do not have
Cortex
Game LED programming software this utility is available on the
VEXnet LED NO NO Downloads page at vexrobotics.com.
flashing?
on?

YES YES 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
Is the Cable.
VEXnet LED
NO
green?
If the units are still not correctly linked, refer to the
Wait 20 second…
YES VEXnet Troubleshooting Flowchart in Section 3.

If your robot seems slow to respond while running user code, it is likely
Is the that there is something in your program that is slowing down the loop time.
robot lagging Check your code for any slow-to-execute commands (such as updating an
or slow LCD screen or printing to a debugging window) that are set to run on every
NO YES cycle of a loop. A slow response time can also be the result of having too
to respond?
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).

Do all Refer to the Motor

motors work Troubleshooting
correctly? NO Flowchart in Section 4.

YES 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 [email protected]. Please note: for programming ques-
tions contact the developer of your programming software.

Page 1 of 4 08/11
 VEX Robot Troubleshooting Flowcharts
2. Competition Robot Troubleshooting Flowchart

Start The main battery on the robot was dead or had

been disconnected from the Cortex. The Cortex
When this was running on the 9V backup battery which is
Did your happened, did all Did the intended to only maintain the VEXnet link in
robot stop motors not connected Robot LED on case of main battery failure.
working during to a Power Expander The Joystick
YES YES YES
a match? completely stop turn red?
moving? After the match, verify that your main
NO NO battery is fully charged and check the
battery’s connection to the Cortex. The
NO
battery connectors on the Cortex can
Did the become bent open over time. If necessary,
It’s possible that the internal thermal
VEXnet LED
breakers in some of the motors are tripping bend the prongs back in to ensure a solid
on the Joystick
as a result of the motors being stalled turn red? YES power connection.
or placed under too high of a load. For
Further assistance, refer to the Motor Did it
NO Refer to the VEXnet
Troubleshooting Flowchart in Section 4. stay red for the
remainder of the Troubleshooting Flowchart
YES in Section 3.
match?

NO
When programming a
The Joystick and Cortex temporarily lost the VEXnet
competition robot, it’s very
link. This may be caused by excess interference, lose
Does your important that you write your
autonomous connections or low batteries in the Joystick. After the
code in a competition template
code start match, make sure all batteries are fully charged and
NO so that the Field Controller will
correctly? check for loose power connections. In particular, make
be able to correctly start your
sure that you are using a fully charged 9V backup battery.
autonomous code.
YES

If this is a reoccurring issue,

it may necessary to move the
Was the VEXnet key to a better location
Game LED
green? YES on your robot. Please note that
the key should be mounted at
Does your
competition code When this happens, least 2 inches (5 cm) away from
NO let the robot sit for 10 anything metal.
(written in a competition
template) execute NO seconds and then try
at all? again.

YES Check the Initialize or pre_auton Did

function in your code for an the robot Check user code and
infinite loop or anything that start moving again redownload. Also
might cause the controller to stay after 10 YES check all motor and
in this function instead of Moving seconds? battery connections.
on to the Autonomous and Driver
Control functions. NO

The robot was disabled by the Field Controller. If this It is likely that one or both of the 4 amp circuit breakers
happened while the match was in progress it may have on the Cortex were tripped. This is usually a result of
been caused by a loose connection to, or possibly an issue the motors being stalled or placed under too high of a
with, the Field Controller. Verify that the Competition loaded. See the Motor Troubleshooting Flowchart in
Cable is correctly plugged into the main VEXnet Joystick. Section 4 for further assistance. Please note that the
See the Field Technician for further assistance. Power Expander also has one 4 amp circuit breaker.

If you’re still having issues with your competition robot, you can refer to the other guides or get help from the
Technical Support staff available at your competition. You can also contact VEX Technical Support by phone
at +1-903-453-0802 or email [email protected]. Please note: When preparing for a competition, the
VEXnet Competition Switch (276-2335) is an excellent tool for testing you’re robot’s autonomous code and
verifying that your robot will correctly respond to the Competition Field Controller.

Page 2 of 4
 VEX Robot Troubleshooting Flowcharts
3. VEXnet Troubleshooting Flowchart

Start

Do Check batteries
both units turn and power
on? NO
connections.

YES

Is the Joystick batteries are

Is the
Joystick LED Joystick LED dead. Replace batteries
red? YES solid? YES before continuing.

NO NO

Update the VEXnet Firmware (Master CPU Firmware for ROBOTC users)
Are both
VEXnet LEDs on both the Cortex and the Joystick using the Firmware Upgrade Utility
on? NO included with your programming software. This utility is also available on the
Downloads Page at vexrobotics.com.
YES

Pair Cortex and Joystick.

Single What color For For instructions, refer to
or double is the VEXnet longer than 20 Section 1 of the Cortex
Double Red Flashing YES
blink? LED? seconds?
Yellow User Guide.
Single Other NO

Units are establishing

VEXnet link. No action
required.

Is
VEXnet Units are correctly
LED flashing multiple
NO linked. If the problem
colors?
persists, check user code
or try using the Default
Code which is available
YES
from within your
programming software.
Lost VEXnet link. Poor signal strength.

No VEXnet key detected. Signal may be blocked or units

Check key connection may be out of range. Consider
and replace key if moving key to a better location or
necessary. Powercycle consider moving the Cortex closer
unit when finished. to the Joystick.

If the issue is still present after following this guide, update both the Cortex and Joystick with the
most recent version of the VEXnet Firmware (Master CPU Firmware for ROBOTC users). If this
does not resolve the problem, try using a different set of VEXnet keys. If you need further assistance
you can post a question on the VEX Forum (vexforum.com) or contact VEX Technical Support by
phone at +1-903-453-0802 or email [email protected].

Page 3 of 4
 VEX Robot Troubleshooting Flowcharts
4. Motor Troubleshooting Flowchart

Start
Are In order to run a 2-Wire Motor off a 3-Wire PWM
you using motor port you must use a Motor Controller 29 Module
Motor Controller (276-2193) for each 2-wire motor. This motor controller
Do the
29 Modules on all acts as a converter between a 2-wire motor and a 3-wire
Motors spin
NO 2-wire motors NO
at all? motor port. Ports 1 and 10 on the Cortex are equipped
plugged into ports
2-9 on the
with built-in Motor Controllers, allowing you to directly
YES
Cortex? control a 2-Wire Motor on these ports.

YES

This could be a programming issue. Try switching If any motors are still not
to the Default Code to isolate the problem. responding, try switching out
motors, motor controllers and
motor ports in order isolate the
issue to a particular piece of
The Cortex is equipped with two 4 amp circuit breakers
hardware. For additional help,
that may trip if the motors pull too much current. Motor
you can post a question on the
Do motors ports 1- 5 on the Cortex share one 4 amp circuit breaker.
VEX Forum (vexforum.com) or
intermittently lose Ports 6-10 share a second 4 amp circuit breaker. It’s
power or stop YES contact VEX Technical Support
recommended that you balance the load from your
working? by phone at +1-903-453-0802 or
motors across these two breakers to prevent the circuit
email [email protected].
breaker from tripping unnecessarily.
NO

If a motor still looses necessary power it is likely that the motor’s

Are your
internal thermal breaker is tripping. This is almost always
motors
NO attributed to the motor being stalled or placed under too high
drifting?
of a load. First check your drivetrain or mechanism for any
unnecessary friction. The best way to do this is to disconnect the
YES
motor from your mechanism and then turn the shaft by hand.
Ideally, your mechanism or drivetrain should spin relatively freely.

You may also need to add additional motors to your application or

switch to a slower and less aggressive gear ratio. If you have a high-
load application and are using 2-wire Motor 269 modules, it may
be a good idea to change them out for 2-wire Motor 393 Modules,
which, in their factory setting, can output 60% more torque.

Are you
having Issues
with using your Refer to the Power Expander Inventor’s Guide which
Power YES is available at the Product Page at vexrobotics.com.
Expander?

If you’re still having problems with motors you can refer to the other
NO
guides or contact VEX Technical Support by phone at +1-903-453-0802
or email [email protected]. You may also want to post a question
The Joystick may need
on the VEX Forum and someone in the VEX community will assist you.
to be recalibrated. For
instructions, see section
6 of the Cortex User
Guide or refer to the help
files included with you
programming software.

Page 4 of 4