FMS pre match disabled mode

[Thad House]

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.

[Joe Ross]

Per the FMS whitepaper (http://wpilib.screenstepslive.com/s/4485/m/24193/l/291972-fms-whitepaper) it goes Autonomous Disable - state prior to match start
Autonomous Enable - Autonomous period
Autonomous Disable - end of Autonomous period
Teleop Disable - end of Autonomous period, prior to start of Teleop period
Teleop Enable - Teleop period
Teleop Disable - end of Teleop/match end


However, I don't believe any of the FRC frameworks distinguish between Autonomous Disable and Teleop disable

[Thad House]

Per the FMS whitepaper (http://wpilib.screenstepslive.com/s/4485/m/24193/l/291972-fms-whitepaper) it goes

However, I don't believe any of the FRC frameworks distinguish between Autonomous Disable and Teleop disable

Thats what I thought. And LV can allow you to distinguish between the 2. We were using them for safety on our can grabber, so it only worked if it switch from auto disabled to auto enabled. But that does not seem to be working, so we are just going to have the code running all the time.

[MrTechCenter]

Thats what I thought. And LV can allow you to distinguish between the 2. We were using them for safety on our can grabber, so it only worked if it switch from auto disabled to auto enabled. But that does not seem to be working, so we are just going to have the code running all the time.

Just out of curiosity, what exactly were you trying to do?

[Thad House]

Just out of curiosity, what exactly were you trying to do?

Solve the delay from this thread.

http://www.chiefdelphi.com/forums/showthread.php?t=136034&highlight=FMS

[Ivan Helmrich]

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.

[Jared]

Per the FMS whitepaper (http://wpilib.screenstepslive.com/s/4485/m/24193/l/291972-fms-whitepaper) it goes

However, I don't believe any of the FRC frameworks distinguish between Autonomous Disable and Teleop disable

This isn't right for 2015. The field starts in Teleop Disabled in normal competition and practice matches this year.

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?

[Joe Ross]

Is there a way we can get the incorrect documentation corrected?

There is a report errors form at the bottom.

[Eugene Fang]

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.

This is terrible. Any insight into why this is the case?

[Jared]

This is terrible. Any insight into why this is the case?

I'm not sure, but it appeared that the field was e-stopped in autonomous mode, the field failed to fully reset itself for the next match. Several of us had to restart our network adapters, or change our team numbers in our driver station back and forth. A robot on the opposite side even had to restart their robot to get communications to start working.

My guess is that the e-stop procedure wasn't fully tested/updated for this year, and still has a few little glitches.

[MrTechCenter]

I'm not sure, but it appeared that the field was e-stopped in autonomous mode, the field failed to fully reset itself for the next match. Several of us had to restart our network adapters, or change our team numbers in our driver station back and forth. A robot on the opposite side even had to restart their robot to get communications to start working.

My guess is that the e-stop procedure wasn't fully tested/updated for this year, and still has a few little glitches.

Are you sure that whoever was running the field did it right? There's a procedure for when a match needs to be reset, but usually it doesn't happen until after autonomous ends.

[Jared]

There is a report errors form at the bottom.

My reported error was deleted from the page, and I have received no response to the email I provided. Do you know of another way to get in touch with the people who maintain that website?

[Joe Ross]

My reported error was deleted from the page, and I have received no response to the email I provided. Do you know of another way to get in touch with the people who maintain that website?

I believe the reported errors are private. Mine don't show up after I refresh, however they typically get incorporated within a few days. I noticed that it was updated today and removed the differentiation between teleop and autonomous disabled.

[Jared]

I believe the reported errors are private. Mine don't show up after I refresh, however they typically get incorporated within a few days. I noticed that it was updated today and removed the differentiation between teleop and autonomous disabled.

Thanks - somehow I totally missed that the page had been changed when I went to go check.