View Single Post
  #3   Spotlight this post!  
Unread 25-03-2010, 12:55
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,752
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Take an exit with dignity

I was assisting at the Dallas regional, and would follow nonmoving robots back to the pits to help resolve the problem. We saw a small number of issues that explained the failures.

The most common issue was loose power connectors. Robots that disable for ~15 secs, then continue had the cRIO reboot -- wiggle the connectors at cRIO and at PD to find which is loose. If the robot is disabled for 30 to 40 secs, check power to the bridge. Also, bridge only power issues don't affect RSL. If it was 40 secs and RSL goes out, check battery connectors.

Clearly, a cRIO reboot that isn't explained by a loose connector can also be a code issue especially if running C/C++.

If the reboots are due to a weak battery, the RSL tends to be dim. Clearly the DS should help identify this as well.

Another issue, harder to diagnose from the stands is the Security button on the bridge. If the bridge can move and an impact can cause the lock button on the front to be pushed, the robot will not move for the remainder of the match, and the Security LED will be blinking green or amber at about 3Hz on the bridge after the match. It blinks green for about two min, then amber for several more minutes.

One well built robot had the bridge security button pushed several times. Testing the bridge outside of the robot, it seemed that the board moved within the case, possibly due to their good job of hard hit testing before ship. Replacing the bridge resolved their issue.

-------

DS setup:
Do not plug Cypress board into an external hub, plug it directly into the laptop port. This may cause the Cypress to stop working, but it may cause the entire hub to drop out. This is often corrected, for awhile, by unplugging and replugging. Hit F1 if the match has already begun.

To test the Cypress board, press the button. If one red LED lights up in response, the board has not been recognized. If zero LEDs light up, everything is fine. This should match the state of the LED on the DS I/O tab.

To test joysticks, click a button and see if the LED on the Diagnostics tab turns blue, or if the listbox line turns blue on the setup page. When disabled, the DS scans for joysticks once per second. This is too expensive during a match, but F1 will force a rescan if connections are changed during a match.

-------

I'm not posting this here to declare that the field or FMS never has issues, but in my investigations, the issue was explained by one of the above. Hopefully this will help with troubleshooting.

Greg McKaskle

Last edited by Greg McKaskle : 25-03-2010 at 12:57.
Reply With Quote