![]() |
FMS pre match disabled mode
Before a match starts, does the FMS give teleop disabled signals or auto disabled signals? We have some code running only in auto disabled, and it didn't run in our first practice match.
|
Re: FMS pre match disabled mode
Per the FMS whitepaper it goes
Quote:
|
Re: FMS pre match disabled mode
Quote:
|
Re: FMS pre match disabled mode
Quote:
|
Re: FMS pre match disabled mode
Quote:
http://www.chiefdelphi.com/forums/sh...&highlight=FMS |
Re: FMS pre match disabled mode
We had a related, possibly same issue at the GKC regional. We use LabVIEW and had coded it to read our autonomous mode from the dashboard when the robot mode was set to Auton Disabled. This worked flawlessly in the shop. At the regional though we just stayed in the default auton mode (do nothing). I asked the same question you just did and I was told that the robot mode is Teleop Disabled before Autonomous. We changed the code to also read the variable when in Teleop Disabled and never had that problem again.
|
Re: FMS pre match disabled mode
Quote:
If the field has been e-stopped while in autonomous mode and reset, it will begin in autonomous disabled, so be sure to test that your code will still work in this situation. Is there a way we can get the incorrect documentation corrected? |
Re: FMS pre match disabled mode
Quote:
|
Re: FMS pre match disabled mode
Quote:
|
Re: FMS pre match disabled mode
Quote:
My guess is that the e-stop procedure wasn't fully tested/updated for this year, and still has a few little glitches. |
Re: FMS pre match disabled mode
Quote:
|
Re: FMS pre match disabled mode
Quote:
|
Re: FMS pre match disabled mode
Quote:
|
Re: FMS pre match disabled mode
Quote:
|
| All times are GMT -5. The time now is 08:44. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi