FIRST Robotics Competition Documents

cancel
Showing results for 
Search instead for 
Did you mean: 

FRC 2012 - Known Issues List

Please note that the content contained in this document is out-of-date for the current competition season. Please feel free to use it as a reference moving forward.

 

This document contains the FRC 2012 known issues that were discovered during the 2012 season. Not every issue known to NI will appear on this list; it is intended to only show the severe and common issues.

 

Source Forge Tracker ID
Known Issue
Workaround
  cRIO Imaging Tool - Timeout error due to various network interface configurations
  • Fixed in the latest Utilities Update
  • Enable the wireless on the computer
artf1436 Setup Axis Camera Tool - Axis 206 camera loses communication after power cycle
  • Fixed in the latest Utilities Update
  Kinect does not work if Cypress IO has been set to Enhanced Configuration, but the board is not connected
  • Choose Compatible for the configuration OR plug in the Cypress board
  Running the project has no issues, but building it fails explaining that it cannot save the Vision Processing VI in a bad state without a diagram.
  • Modify the build settings/Additional Exclusion to uncheck the bottom checkbox that says Modify project library file after removing unused members
  If CAN is used in the Autonmous VI, the robot cannot transition to the Disable or Teleop VIs.
  • Terminate the autonomous routine just before the VI would be aborted, to stop calling CAN updates before the end of the autonomous period
  • Move the CAN updates to Periodic tasks and have autonomous simply update setpoints
     
Comments
sciencewhiz
Active Participant
Active Participant
on

Shouldn't the workaround for the imaging be disable (rathern then enable) wireless? It should also say to disable all other network interfaces.

Kevin_F
NI Employee (retired)
on

That issue isn't always resolved by disabling wireless- on certain computers you need to enable the wireless to get it to work correctly. However I would just encourage getting the latest utilities update and avoiding the issue entirely

Kevin Fort
Principal Software Engineer
NI