-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Mission speed change not working #11764
Comments
@bresch any idea why this happens? |
Do you recall when it last worked? |
My guess it's limited to cruise velocity somewhere in position control or flight task but I couldn't find it yet. |
Right, the velocity is limited by the cruise speed parameter. I have to check how "DO_CHANGE_SPEED" is implemented in the mavlink receiver. |
It's implemented in the navigator actually. |
Not fixed properly yet. |
@bresch did you find anything? |
I need to discuss with @MaEtUgR for a proper fix, hopefully tomorrow we can have something. |
Does this only happen with smooth mission enabled or always? Because #11772 only changed the smooth vel task which
|
This happens with default jMAVSim SITL, so whatever comes with that. I don't know what sort of smoothing goes on. |
There seem to be two problems:
|
I did a test with DronecodeSDK and |
@julianoes The DronecodeSDK test seems super picky:
but at least it succeeds if it's within +-1m/s. |
The warning is misleading, that should be a pass overall. |
In recent jMAVSim SITL tests using the Dronecode SDK I found that the MAVLink command MAV_CMD_DO_CHANGE_SPEED does not seem to have any effect.
No matter what the speed is set, the vehicle speed is always 5 m/s presumably the cruise velocity.
Firmware version: 0b548fa
The text was updated successfully, but these errors were encountered: