search

rrossbach / fourteentwentyfive

Automatically exported from code.google.com/p/fourteentwentyfive
0 stars 0 forks source link

LiveWindow (test mode) startup isn't reliable #7

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
This may be a problem with the way the commands and subsystems are initialized 
or it may be a problem with how WPILib deals with unexpected data in the 
networktables.  Or both.  Identify the root cause(s) of the crashes and lockups 
and fix them.

Original issue reported on code.google.com by stevet19...@gmail.com on 27 Feb 2013 at 2:38

GoogleCodeExporter commented 8 years ago 
Incorporating changes from the firstforge issue tracker and the robotpy project 
helped.  I also added or fixed some problems with LiveWindow initialization 
calls in the WPI code and in our robot code.  The dashboard's mostly working 
now.

...But if anything gets messed up, especially if the LiveWindow contents are 
changed, the dashboard may still create a corrupted or zero-length save file.

Original comment by stevet19...@gmail.com on 5 Mar 2013 at 7:07

GoogleCodeExporter commented 8 years ago 
The dashboard creates a truncated or zero-length save file any time the robot 
is turned off before the dashboard is shut down.  This appears to be a 
SmartDashboard problem, not a WPILib or robot problem, and I'm not going to be 
able to fix it.  The best workaround seems to be to keep a good copy of the 
dashboard save file around.  The second-best workaround is to hand-edit the 
corrupted file to delete all the test-mode layout information (preserving the 
normal runtime layout, which is usually OK).

Original comment by stevet19...@gmail.com on 22 Oct 2013 at 6:09