Five Second Delay at Beginning of TeleOp

[CorruptedArk]

Originally Posted by Jared Russell

Line 371 of Robot.java

That could be it. Do they go to disabled before teleOp during a match? I thought it went straight to teleOp from autonomous.

[RufflesRidge]

Originally Posted by CorruptedArk

That could be it. Do they go to disabled before teleOp during a match? I thought it went straight to teleOp from autonomous.

Here are the mode transitions from the FMS Whitepaper:

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

[CorruptedArk]

Originally Posted by RufflesRidge

Here are the mode transitions from the FMS Whitepaper:

Thanks, I didn't know about that. I think that's the source of our troubles.

[mwtidd]

Originally Posted by CorruptedArk

Thanks, I didn't know about that. I think that's the source of our troubles.

The Timer.delays are something I've been combating for years now. I really believe the tutorials that utilize it do a disservice in the long term.

Yes, I can acknowledge that it helps teams get up and running quickly, but teaches bad practices, and has the potential to create really confusing scenarios when you start utilizing command based programming.

Here's a post I wrote on it last year...

http://www.chiefdelphi.com/forums/sh...27&postcount=2

I realize that it's late in the season to change how you handle this, but in future seasons please reconsider using Timer.delay for anything other than giving the brain a break.