Thread: IF NEEDING HELP POST HERE!
View Single Post
  #4   Spotlight this post!  
Unread 13-01-2011, 15:12
DavidGitz's Avatar
DavidGitz DavidGitz is offline
Lead Technical Advisor
FRC #1208 (MeTool Brigade)
Team Role: Coach
  
Join Date: Dec 2006
Rookie Year: 1996
Location: O'Fallon, IL
Posts: 341
DavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud ofDavidGitz has much to be proud of
Send a message via AIM to DavidGitz Send a message via MSN to DavidGitz Send a message via Yahoo to DavidGitz
Re: IF NEEDING HELP POST HERE!
I would try connecting the cRIO with a crossover to your development computer and try to connect from there. I would make the IP settings on your computer 10.xx.yy.7, 255.0.0.0 and 10.xx.yy.2

Is your classmate able to see "Communications" from the Driver Mode?

What is the RSL pattern? That could give some information too.

This is from last year's documentation, but I assume* it is the same.

Solid ON = Autonomous Enabled
Solid ON, but blinks OFF every 1.5s = Teleoperated Enabled
Slow Blink (900ms on / 900ms off) = System disabled; caused by system watchdog, user
watchdog, or Driver’s Station set to Disabled.
Fast-Slow Blink (200ms on / 900ms off) = Low battery (<12 Volts) or no user code and system disabled either by system watchdog, user watchdog, or Drivers’s Station set to Disabled.
Fast Blink (200ms on / 200ms off) = System error: No Driver’s Station communication, bad cRIO Image, bad team ID, extensive communication errors. (I assume it's this one).
__________________
Reply With Quote