Auto mission command DO_CHANGE_SPEED doesn't take effect

Hi everyone,

I’m reaching out for some help regarding speed commands. I recently tested a mission with my quadcopter (Takeoff → 4 Waypoints → RTL) which included three MAV_CMD_DO_CHANGE_SPEED commands.

While the mission was completed successfully, it seems my speed changes were completely ignored. The drone maintained the default WPNAV_SPEED for horizontal travel, and WPNAV_SPEED_DN / UP for vertical movements throughout the entire flight.

I tried all three speed types (Airspeed, Groundspeed, and Throttle) but none had any effect.

Since I cannot share my full logs, here is a snippet of the mission commands I used:

Mission Planner version : 1.3.83
AP: ArduCopter V4.6.2 (1ebd4d99)
AP: ChibiOS: 88b84600
AP: SIYI_N7 00460039 35325118 36363230
AP: IOMCU: 0 0 411FC231
AP: RCOut: PWM:1-8 NeoP:9-12 PWM:13
AP: IMU0: fast sampling enabled 8.0kHz/2.0kHz
AP: Frame: QUAD/X

I cannot figure out which speed type integer is who :

Here Horizontal is 0 and here:

It’s 1.

Set param1 to 0 for the speed change command.

Just for trouble shooting, move the change speed command after the first way point and see if that has any effect.

in copter param 0 and 1 are the same, referring to groundspeed.
Note: The actual horizontal and vertical speed also depends on the distance vertically and horizontally between the two waypoints. So if you have to descent from 11 meters to 6 meters the maximum vertical speed will limit the horizontal speed. The vehicle will always do a trajectory where it reaches the vertical position at the same time as the horizontal.

Thanks for the replies. I will try setting the Speed Type to both 0 and 1 to see if it triggers the horizontal speed change.

However, my concern is also that the climb/descent speed commands were also completely ignored. Despite setting a DO_CHANGE_SPEED for vertical movements at 0.5 m/s, the drone maintained the default WPNAV_SPEED_DN and WPNAV_SPEED_UP values (2 m/s) throughout the mission.

I am aware that the autopilot might throttle down speed when waypoints are close together to manage cornering, but in this case, the distances were more than sufficient to reach the target velocity. It seems the command is being bypassed entirely.

Here is my log : https://drive.google.com/drive/folders/1oMyn0f9cgx2XYijmgAGglpncp2DrpdiT?usp=drive_link

For horizontal speed, we tried with speed type to 1 and it took effect but still not with 0. Seems that 0 is simply ignored ! Bad observations were made during 1st flight for climb and descent speed types, changes were taken into account during 2nd flight …

So conclusion is that XY speed is speed Type =1 , climb = 2 and descent =3.