Quote:
Originally Posted by jhersh
Quote:
Originally Posted by full_auto
This code is executed periodically. The problem is that after it executes a few times the DS stops responding and must be restarted to regain functionality. This does not happen if I remove those two lines, so I'm fairly sure that they are the cause.
|
Where are they called from? How quickly are they called? Does rebooting the robot affect anything, or is restarting the driver station application the only thing that makes it work again? |
Quote:
Originally Posted by full_auto
It turns out that the problem was not related to the calls to DriverStationLCD, removing those lines only made the error occur much later. All is well now. Thanks.
|
A note to everyone that doing this to send data back to the DS...
Make sure you aren't running this code CONSTANTLY. Sending new messages and running the updateLCD() method too fast
will run the cRIO out of memory, and my guess is because it backlogs all the packets and fills up the memory. You'll get an OutOfMemoryError, and will have to reboot the cRIO to do anything else (like load new code).
(Found this out the hard way on WPILibJ version 1.0.0a, and my guess is it happens with the latest version too...)
If there was no internet then somebody in FIRST would probably invent it. - Koko Ed [more] 
03-02-2010, 11:20
Similar Threads
Threaded Mode