Project Home

Trackers

File Releases

Discussions

Project Info
Artifact artf4826 : Cannot un-estop after estopping a robot Print Preview
Tracker:OffSeason FMS Bugs
Title:Cannot un-estop after estopping a robot
Description:
After e-stopping a robot with the 2015 offseason FMS, it appears as though there is no way to clear the estop for the 
next match. This prevents us from starting matches.

Restarting the FMS does not fix this issue.

MecaNaught on ChiefDelphi posted a set of scripts that circumvents this by allowing you to backup the database before 
starting matches, then replacing out the "bad" database with the backup if you have to estop: http://www.chiefdelphi.com
/forums/showthread.php?p=1542574#post1542574

Obviously that's not an ideal solution though ;)

I'm hoping that the 2016 offseason FMS will already have this fixed, but I'm also not expecting a release of either the 
2015 or 2016 offseason FMS by tomorrow, so I wanted to raise this for awareness.
Submitted By:Bryan Herbst
Submitted On:02/19/2016 3:09 PM GMT
Last Modified:05/18/2016 7:03 PM GMT
Closed:05/18/2016 7:03 PM GMT

Active Tab Status / Comments Inactive Tab - left sideChange Log Inactive Tab - left sideAssociations Inactive Tab - left sideDependencies Inactive Tab - left sideAttachmentsInactive Tab - right side  
Closed
3
None
Planning Folder:*None
2015 FMS OffSeason > 2015 FMS OffSeason (v2.30)
2016 FMS OffSeason > May 2016
Not calculated
0   Hours
0   Hours
0   Hours
0
Comments
#6Alex Herreid (FIRST): 05/18/2016 7:03 PM GMT
 Comment:
Resolved
 Action:Update
Closed set to 05/18/2016
Fixed in Release set to 2016 FMS OffSeason > May 2016
Status changed from Open to Closed
#5Bryan Herbst: 02/19/2016 7:28 PM GMT
 Comment:
Done- agreed that staying out of the database is always a good idea. Thanks for the help!
 Action:Update
#4Alex Herreid (FIRST): 02/19/2016 7:26 PM GMT
 Comment:
Thank you for checking- we will work on an update before a future release. Would you be able to update the folks on the 
thread you quoted, and either point them to this report, or tell them about the solution? 

I would recommend they not do what they were talking about- messing with the database files and re-installing like that 
is likely to lead to corrupt data or unexpected behavior. They should follow the below workaround for now.

Thanks~
 Action:Update
#3Bryan Herbst: 02/19/2016 7:23 PM GMT
 Comment:
You are correct- just restarting the services fixes the issue.
 Action:Update
#2Alex Herreid (FIRST): 02/19/2016 3:44 PM GMT
 Comment:
We unfortunately don't have time to investigate this at the moment, but have something we would like you to try if 
you're willing:
There's no Estop flag in the database, so it's not recommended that you try to make any database edits. Instead, if 
someone is estopped and the flag won't clear, open the "Windows Services" panel on your machine and look for the two 
services that start with "FMS" (Base and SignalR are the names). After closing the FMS Software, right clock on each of 
those and select "Stop". Once they finish, wait a moment, then right click and "Start" those services again. You should 
be able to re-open the software and the estop flag will be cleared. Thanks
 Action:Update
#1Bryan Herbst: 02/19/2016 3:09 PM GMT
 Action:Create