View Single Post
  #8   Spotlight this post!  
Unread 03-02-2010, 15:08
jhersh jhersh is offline
National Instruments
AKA: Joe Hershberger
FRC #2468 (Appreciate)
Team Role: Mentor
 
Join Date: May 2008
Rookie Year: 1997
Location: Austin, TX
Posts: 1,006
jhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond repute
Re: sending info to a console

Quote:
Originally Posted by KevinJ View Post
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...)
That's a bit strange. Are you sure that's the only thing that's happening in your loop? I just looked at the code path for that in Java and I don't see any allocations at all in that loop. Are you allocating memory yourself? Is the out of memory error coming from the Java VM or from vxWorks?
Reply With Quote