-
Notifications
You must be signed in to change notification settings - Fork 16.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rover: Cannot enter Guided mode with only wheel-encoders #10752
Comments
On Fri, 8 Mar 2019, Randy Mackay wrote:
Rover-3.5.0 apparently doesn't allow the user to enter Guided mode if only Wheel Encoders are being used for the position estimate. The cause is likely to
do with the new EKF failsafe code that was added to 3.5. The EKF failsafe check likely checks the absolute position estimate is good when it should also
work when only the relative position estimate is good.
I don't think this problem is a result of any EKF changes. The MAVLink
API seems to convert everything into llh.
It would be nice to clarify the callbacks on the modes.
Perhaps "requires_llh" ("requires_global_position"?) and
"requires_position"? Unfortunately, this is a touch simplistic as the
answer is "sometimes". If the user wants to use
MAVLINK_MSG_ID_SET_POSITION_TARGET_LOCAL_NED they will not need (e.g.) a
GPS lock. If they use MAVLINK_MSG_ID_SET_POSITION_TARGET_GLOBAL_INT they
will - and you won't know what they want before entering the mode. So
that probably means you enter guided if you can sense relative position
but need to bounce any attempt to move you in the global FOR.
|
It's a result of this change commit 80e9a54 |
Thanks for the extra info and thoughts above. We should be able to do what we do in Copter. A relative position source is actually OK because we still force the user to set an EKF origin (and thus home) so the vehicle knows where it is in the world. There will be some drift but that's OK. |
Any update on this issue. as we are struggling hard to use my rover with encoder. Any direction or help is appreciated |
I think I've got a fix for this issue in this branch: https://github.com/rmackay9/rmackay9-ardupilot/commits/wenc-fix. I'll hopefully raise a PR in the coming days to get it into Rover-4.0.0. |
This is fixed in master so closing |
Rover-3.5.0 apparently doesn't allow the user to enter Guided mode if only Wheel Encoders are being used for the position estimate. The cause is likely to do with the new EKF failsafe code that was added to 3.5. The EKF failsafe check likely checks the absolute position estimate is good when it should also work when only the relative position estimate is good.
This was reported by @jmachuca77 and @magicrub.
The text was updated successfully, but these errors were encountered: