|
|
|
 On a side note... "Think outside the robot." - I kinda like that. I'll have to use that in a meeting someday.... - Not2B [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| On a side note... "Think outside the robot." - I kinda like that. I'll have to use that in a meeting someday.... - Not2B [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#2
27-01-2013, 21:50
|
|||
|
|||
|
Re: Moving autonomous programs to teleop
TeleOp is designed to return to the scheduler and be called again every 20ms. If you put code there that takes longer than 20ms to run, it will cause the robot to miss joystick values. I'd recommend putting the code into Periodic tasks and using a global to cause it to start and stop when appropriate, auto or teleop.
Greg McKaskle 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Threaded Mode