Common Issues

Jump to: navigation, search
(Setting up a Cortex (VEXNet))
(Motors will not stop running)
Line 71: Line 71:
 
   |}
 
   |}
  
===Motors will not stop running===
+
===Motors will not stop running after program is run===
 
Usually when we see this it is one of two things; either the robot is not programmed correctly, or the motors are physically plugged in the wrong way. First, have them check that the motors are plugged into the correct ports, that they are plugged in correctly (the Cortex and motor plugs are keyed), and that the battery is freshly charged. If that doesn't solve the issue, have them post the code on the ROBOTC forums (robotc.net/forums); from there, we will be able to determine if it is a coding issue (probable) or something that needs to be looked into further.
 
Usually when we see this it is one of two things; either the robot is not programmed correctly, or the motors are physically plugged in the wrong way. First, have them check that the motors are plugged into the correct ports, that they are plugged in correctly (the Cortex and motor plugs are keyed), and that the battery is freshly charged. If that doesn't solve the issue, have them post the code on the ROBOTC forums (robotc.net/forums); from there, we will be able to determine if it is a coding issue (probable) or something that needs to be looked into further.
  

Revision as of 10:09, 20 February 2013

Common Issues


For information about displaying on the NXT LCD, please see the article: NXT Display Functions.

For information about displaying on the VEX LCD, please see the article: Cortex Display Functions.


When displaying floats, for example, you can tell ROBOTC how many decimals places to display. This is standard across all 'C' - like programing languages. For example, if your float is PI (3.14159265), but you only want to dispay "3.14", your string should contain, "%1.2f".

The number before the decimal is how many digits before the decimal you wish to display, while the number after the decimal is how many digits after the decimal you wish to display. So "%1.2f" tells us to display one digit before the decimal and two digits after the decimal, with "3.14" as the final result.


Contents

Color Key
Function:
Variable:


ROBOTC Setup

ROBOTC Download Page

http://www.robotc.net/download

Downloading, Installing, and Activating ROBOTC (365-day or Perpetual License)

http://www.robotc.net/wiki/Tutorials/Getting_Started

Installing and Activating a Building License File

http://www.robotc.net/wiki/Tutorials/Getting_Started#Building_Licenses

VEX Cortex Resources

Building the RECBot

http://www.education.rec.ri.cmu.edu/products/teaching_robotc_cortex/setup/build/recbot_with_cortex.pdf

Building the SQUAREBot

http://www.education.rec.ri.cmu.edu/products/teaching_robotc_cortex/setup/build/squarebot4.pdf

Setting up a Cortex (Hardwired using a USB cable)

http://www.robotc.net/wiki/Tutorials/Getting_Started/Getting_Started_with_the_VEX_CORTEX#Configuring_the_VEX_Cortex_for_a_WIRED_connection_using_USB

Setting up a Cortex (Wireless using the VEXNet Joystick Controller)

http://www.robotc.net/wiki/Tutorials/Getting_Started/Getting_Started_with_the_VEX_CORTEX#Configuring_the_VEX_Cortex_for_a_WIRELESS_connection_using_the_VEXnet_Joysticks

Beginning Programming (Video Curriculum Trainer)

http://www.education.rec.ri.cmu.edu/products/teaching_robotc_cortex/index.html

VEX Cortex Issues

Cortex won't connect to ROBOTC

If these steps are followed and they are still having problems installing the USB-to-Serial driver, have them contact ROBOTC Technical Support directly at support@robotc.net

From the ROBOTC support ticket database:

First, make sure you have administrator access before downloading the Cortex the Cortex firmware for the first time on each computer.

Unplug the Cortex from the computer. With a batter plugged into the Cortex, plug the USB cable from the computer back into the Cortex, wait a few seconds for Windows to recognize the Cortex (you will see a popup window in the saying 'Installing Device Driver Software'), then turn on the Cortex.

Next, make sure that the correct drivers are installed for the Cortex. ROBOTC will download the drivers as it is being installed, but if the drivers are not installed correctly you can download from our website and install them manually. Depending on which cable is being used, you will either need the 'CORTEX & VEXnet Joystick Drivers'(USB A-to-A) or the 'Prolific USB-to-Serial Driver' (USB-to-Serial Cable). The Cortex will install a driver for each USB port that it is plugged into, so if you change ports please ensure that you install drivers for the new port. Both of the drivers need to be installed as administrator, and can be found on our download page under optional downloads: http://www.robotc.net/download/cortex/

The Cortex is not compatible with SMART Board software and will not work with SMART Board software installed. To resolve this issue, you must disable the SMART Virtual TabletPC driver in Windows Device Manager. Instructions on how to do so can be found here: http://www.robotc.net/support/cortex/smartboard_cortex_fix.pdf

Finally, make sure that the correct COM port is selected in ROBOTC. Navigate to the 'Select Communication Port' option from the 'View' menu in ROBOTC. From the Communications Port drop down list, you should see "Automatic Selection" and one of two additional options: If your VEX Cortex is in "bootload mode" or running an older (2.x) version of the Master CPU Firmware, it will appear as a "USB Wired Cable" option in the list. If your VEX Cortex is running a newer (3.x) version of the Master CPU Firmware, it will appear as a "Vex Robotics Comm Port" in the list. Make sure that "Automatic Selection" or one of the two legitimate options is selected.

If you ever plan on programming your robot wirelessly over VEXnet, choosing "Automatic Selection" is recommended. Press OK to save your choice. Important: If the "USB Wired Cable" or "Vex Robotics Comm Port" options do not appear in the drop down menu when a VEX Cortex is connected, this may indicate that Windows has not recognized the device or access to it is blocked. Ensure that the VEX Cortex Device Driver was successfully installed with Administrative Privileges, disconnect and reconnect your Cortex from the computer, and press "Refresh List" to force ROBOTC to repopulate the list.

Also, try different USB ports (the ones on the front of computers are sometimes unable to provide enough current to the Cortex for it to be recognized) and different cables, if possible. Note that the front USB ports on computers have been known to build up static which can cause intermittent disruptions to data transfers.

If you have followed all these steps and the problem still persists, please provide me with the driver name that is attached to the Cortex (found by navigating to the Device Manager in Windows Control panel; Start -> Control Panel -> Hardware and Sound -> Device Manager), the name of the port in ROBOTC's View -> Select Communication Port window, and any other information that appears (error messages, etc).

Motors will not stop running after program is run

Usually when we see this it is one of two things; either the robot is not programmed correctly, or the motors are physically plugged in the wrong way. First, have them check that the motors are plugged into the correct ports, that they are plugged in correctly (the Cortex and motor plugs are keyed), and that the battery is freshly charged. If that doesn't solve the issue, have them post the code on the ROBOTC forums (robotc.net/forums); from there, we will be able to determine if it is a coding issue (probable) or something that needs to be looked into further.

Programs will run when the Cortex is physically plugged into VEXNet Joystick, but not when disconnected.

When we see this issue, it's normally because the VEXNet Controller and the Cortex needs to be synched together. Have them go through the VEXNet setup portion of the 'Getting Started with a Cortex' guide (http://www.robotc.net/wiki/Tutorials/Getting_Started/Getting_Started_with_the_VEX_CORTEX#Configuring_the_VEX_Cortex_for_a_WIRELESS_connection_using_the_VEXnet_Joysticks) to ensure the Cortex and VEXNet controller are synched properly. If this still doesn't work, have them check and swap out the VEXNet keys, as it is a possibility that the VEXNet keys have gone bad.

All other issues

If it is a coding issue, point them to the ROBOTC forums, otherwise have them contact ROBOTC Technical Support via support@robotc.net We will be able to direct them to the correct avenue from that point.

LEGO MINDSTORMS NXT/TETRIX Resources

Building the REMBot

http://www.education.rec.ri.cmu.edu/previews/robot_c_products/teaching_rc_tetrix_preview/setup/buildshows/rem_print.pdf

Building the Mantis Bot (TETRIX)

http://www.education.rec.ri.cmu.edu/previews/robot_c_products/teaching_rc_tetrix_preview/tetrix_setup/documents/mantis_print.pdf

Setting up an NXT

http://www.robotc.net/wiki/Tutorials/Getting_Started/Getting_Started_with_NXT_and_TETRIX

Setting up a Samantha Module (TETRIX, FTC competition)

http://www.robotc.net/wiki/TETRIX_Samantha_Module

Beginning Programming (Video Curriculum Trainer)

http://www.education.rec.ri.cmu.edu/previews/robot_c_products/teaching_rc_tetrix_preview/index.html

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox