The VEX IQ Forum is the go-to place for any VEX related question. Have a question about a specific game rule or situation? Ask it in the Official VIQC Q&A channel! Or, if you're having problems with your code or a specific part, post your question in a Technical Support channel for almost instantaneous help from VEX staff or the rest of the community. Feel free to share your creations with us and the rest of the community in the Robot Showcase channel, or on VEX Social Media!
VEX IQ Build Instructions
When building with VEX IQ, make sure that you are always using the most up-to-date set of build instructions, which can be viewed here. The PDF's can also be downloaded by right clicking the link > "Save Link As". Make sure to check out the animated Clawbot instructions also!
VEX Robotics digital resources are made freely available for promotional and private use if proper VEX branding is upheld. Examples of acceptable use would be local team recruitment or fundraising advertisements. Commercial use must credit VEX Robotics, Inc., unless otherwise agreed upon.
To ensure consistency of the VEX brand, please consult the appropriate VEX style guides before utilizing any VEX logos or artwork. Feel free to contact firstname.lastname@example.org with any questions, requests for permission, or information regarding resources not available on this page. For other marketing inquiries, please contact email@example.com.
First, make sure your motor is correctly wired. Ensure the Smart Cables are fully seated by pressing until an audible click is heard (You may need to unplug and replug the cables in). If the problem persists, please perform a firmware update followed by a calibration.
Make sure the system has been correctly tethered per this video. Make sure your Radios is fully inserted. No blue logo should be showing, it helps to push the red button on the Robot Brain while inserting. If this fails, you can also swap the Radio from the Controller into the Robot Brain and vice versa.
If you are using the Smart Radio, make sure your Robot Brain and Controller are upgraded to firmware 1.16 or newer.
If all this fails, please remove your Radios and inspect the radio slot on the Controller & Robot Brain. Make sure there are no exposed or smashed pins.
If a Smart Motor / Sensor fails to be identified by the IQ Upgrade Utility, you will need to attempt to restore it by downloading the latest firmware into the motor/ sensor. To do this, connect ONLY the affected Smart Motor / Sensor into the Robot Brain, and perform a firmware update.
If a brain is not identified by the IQ Upgrade Utility, you will need to engage DFU (Device Firmware Update) Mode. To access DFU mode, simply press and hold the up and down buttons while you power up the brain. Then perform a firmware update.
A red blinking light indicates a battery "fault". This can be caused if battery is allowed to be completely drained. It can also happen if the battery is connected to the robot for several weeks.
Even if the robot is off, users are encouraged to charge batteries after each use and to remove them from the robot when not in use.
Sometimes the IQ Smart Motor will make internal motor sounds, but no output will be provided. This motor has stripped gears, and need to be replaced under warranty.
Another common cause of this problem is that the default demo sensor functionality has been enabled in the Driver Control program. This can be solved by unplugging the Distance Sensor, Gyro Sensor, and Color Sensor while running Driver Control.
Finally, this problem can also be caused by a bug in your ROBOT C or MODKIT program.
This situation could happen if the Controller is grabbed / handled by the joysticks. The sticks get pulled-upwards by a few millimeters, which is the cause of the problem.
To fix this issue, push down hard against the joysticks with your thumbs. They should dig about a millimeter, and give the extra needed space to achieve neutral position.
View the corresponding video for default sensor functionality in this YouTube playlist.
Depending on which compiler you are using, please contact either MODKIT or ROBOTC. A screenshot of your error message or code is recommended.