Thread: Communication Trouble
View Single Post
  #6   Spotlight this post!  
Unread 26-01-2012, 12:45
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: Communication Trouble
Quote:
Originally Posted by jee7s View Post
In the event the power connection isn't the cause...

This also sounds like it could be a watchdog expiration problem. Are you sure you are feeding the watchdog in your program?
Unless you have a specific need for it, there should be no reason to feed the watchdog in your code. This necessity was removed last year and now this is taken care of by the WPI Library functions themselves. This is true for Labview but I'm not sure of other programming languages (but I bet it is).

Can you describe the exact situation of how you lose communication? Does it happen after driving/moving the robot? Do you ever get to enable the robot? Does it happen when you Download and/or Deploy? Do you get any messages on the Diagnostics panel? Does it happen on wireless and wired connections? After this happens are you still able to ping the cRIO and/or the radio?

I'm not 100% sure here, but I think that if you are getting the "No Communications" red light that means your radio has lost connection, and should be independent of the cRIO (i.e. not a power connection problem on the cRIO).
__________________