|
|
|
![]() |
|
|||||||
|
||||||||
| 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?
We also have pneumatics for lifting our fork lift and have seen that behavior multiple times where it simply retracts the forklift. Something is causing the code to go into the startup state. This has happened to us in practice in the shop so the problem could still be communication related where a drop in communication does the same thing as not feeding the watchdog.
Not sure if it is possible to monitor the communication from the cRIO to have it log anytime it goes into "safe" mode. |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|