View Single Post
  #1   Spotlight this post!  
Unread 09-02-2012, 10:57
derekwhite's Avatar
derekwhite derekwhite is offline
Java Virtual Machine Hacker
no team (FIRST@Oracle)
Team Role: Programmer
 
Join Date: May 2009
Rookie Year: 2009
Location: Burlington, MA
Posts: 127
derekwhite is on a distinguished road
Re: Apparent "hangs" in code deploy to cRIO...

The deploy process is not supposed to "finish". It stays connected to your robot in order to display any output that your robot or the cRIO prints out.

This message is printed by WPILibJ if you haven't overridden the disabled() method (which isn't a requirement by the way):
Quote:
[cRIO] Default disabled() method running, consider providing your own
If you see that message, then it's very likely that your robot code is running fine.

This message is printed by the cRIO for some reason. I think it is an ordinary status message though, not any real problem:
Quote:
[cRIO] task 0x25c7a58 (System Web Services Load Thread) deleted: errno=0 (0) status=0 (0)
[cRIO] task 0x2869f70 (mDNS resolve) deleted: errno=0 (0) status=0 (0)
[cRIO] task 0x2bff0d0 (mDNS resolve) deleted: errno=0 (0) status=0 (0)
For your own sanity and/or peace of mind, you might want to print a message at the beginning and end of your disabled(), autonomous() and operatorControl() methods - something like "entering autonomous mode", "exiting autonomous mode", etc.
Reply With Quote