|
|
|
 Your attribute of personal sacrifice is very noble, but FIRST needs YOU to be successful first. - DanKein [more] |
 |
|
|||||||
|
||||||||
 |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| Your attribute of personal sacrifice is very noble, but FIRST needs YOU to be successful first. - DanKein [more] |
|
|
|||||||
|
||||||||
|
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: cRIO communiciton fell
Check the memory % for the cRIO displayed on the Driver Station Charts tab.
A memory leak could eventually cause a crash. NetConsole might give you useful information, if errors are generated prior to the code crash. 
|
|
#2
21-02-2013, 13:15
|
||||
|
||||
|
Re: cRIO communiciton fell
While I would go as far as saying memory leaks are rare in Labview, I would follow marks advice, in the console look for a watchdog error. It would sound to me like your watch dog isnt gettting fed, he flashes an error on the driverstation and the driver is so busy watching the robot that they miss it. If that is the case, I would disable the watchdog and see if that fixes it
|
|
#3
22-02-2013, 04:13
|
|||
|
|||
|
Re: cRIO communiciton fell
If this happens again, please cable to the cRIO, bypassing the DLink wireless, and see what state it is in. Use the DS to inspect the cRIO CPU usage,memory, error messages, etc. This should help isolate whether the comms is failing on the cRIO, or if the radio is not letting traffic through to the cRIO.
Greg McKaskle
|
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Hybrid Mode
