|
|
|
 If they're going to blame you for it anyway, you might as well have fun. - Rick TYler [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| If they're going to blame you for it anyway, you might as well have fun. - Rick TYler [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#14
18-02-2010, 20:20
|
|||
|
|||
|
Re: No Robot Code
Reviewing the meaning of the LEDs may help a bit. The robot LED means that the robot IP ping succeeds. The communications LED means that the communications task on the cRIO is responding to the control packets being sent from the DS. Finally, the Robot Code light really means that the robot code is calling into the communications task often enough.
If the cRIO is vastly overtaxed by the code you are writing, it might behave the way you describe, where the WPI framework is not being updating the battery value and other fields as it is supposed to. I don't remember what language you are using, but if you can determine the CPU usage via spy or a similar tool, it may help you figure out what portion of code is responsible. Greg McKaskle 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| No Robot Code | eaglesfan10 | C/C++ | 6 | 03-02-2010 22:34 |
| Compressor Code causes No Robot Code Error | sircedric4 | C/C++ | 25 | 03-02-2010 10:13 |
| No Robot Code | mlim | NI LabVIEW | 10 | 21-01-2010 17:33 |
| Robot Code? | leftylink | Programming | 0 | 18-02-2008 14:34 |
| Default Robot Code | lvhsrobotics | Programming | 2 | 10-01-2003 16:55 |
Threaded Mode