|
|
|
![]() |
|
|||||||
|
||||||||
| View Poll Results: Do you ever lose control of your robot? | |||
| Never- our controls are always 100% with no sluggishness nor dropouts |
|
26 | 37.14% |
| we started paying careful attention to radio placement and never had another problem |
|
17 | 24.29% |
| Yes we sometimes have sluggishness and dropouts: We always just blame it on our software. |
|
26 | 37.14% |
| We thought sluggishness was a requirement listed in the rule book |
|
9 | 12.86% |
| Multiple Choice Poll. Voters: 70. You may not vote on this poll | |||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#13
|
|||
|
|||
|
Re: Robots not under driver control- does it happen- do you determine why?
I did find in testing that once you enter in autonomous mode you need to keep track of the time spent and return from the method after 15 seconds. I have a keepGoing() method that I put in all the loops and before the next step that forces a return if 15 seconds has expired.
If not, the joysticks are not sampled and the appropriate drive method called. We are doing Java but assume the program constructs are the same in labview or C++. Just because the field switches from autonomous mode to telop mode does not impact the code you have running on your robot. |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|