|
|
|
 you don't need a fancy workshop to build a good robot, just determined people. - pacoliketaco [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| you don't need a fancy workshop to build a good robot, just determined people. - pacoliketaco [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Stuck in Teleop Init
This is a request for help based on quick and preliminary observations. Has anyone come across a robot becoming stuck in the "Init" state while in Teleop mode? It seems we are not advancing into the "Default" derived robot state. On the dashboard no error messages are displayed, the elapsed time continues increasing, and the joystick indicator lights show data is being read from the joystick. However, when running the code, the value of the derived robot state remains at init, and none of the default code executes. What drives this change?
Note: due to problems with the Watchdog, we temporarily removed it from the code. 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| TeleOp Init/Stop vs. Auton-Iterative Init/Stop | Ziaholic | NI LabVIEW | 11 | 07-02-2010 22:19 |
| adding a second joystick to TeleOp Init | smcmahon | NI LabVIEW | 14 | 17-02-2009 20:43 |
| Wierd basic init | Jeremy J | Programming | 5 | 06-02-2003 11:42 |
| Basic Init Error | yan184 | Programming | 5 | 14-12-2002 13:10 |
Threaded Mode