|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||||
|
||||||
|
Re: 1-2 sec delay when entering new modes
Quote:
|
|
#2
|
|||
|
|||
|
Re: 1-2 sec delay when entering new modes
Thanks for the replies. I'll definitely try it when we get the cRIO back connected to the benchtop. The only thing we do in AutonomousInit is call a couple printf()s and a Timer Reset(). Nothing is called except maybe a printf in TeleopInit.
|
|
#3
|
|||
|
|||
|
Re: 1-2 sec delay when entering new modes
I tried "running a match" once we got our cRIO re-hooked to the benchtop. There seemed to be zero delay on starting Autonomous and about a .3sec delay on starting Teleoperated (Not like what the drivers experienced).
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|