Release 7.6.5 Mavlink set_gimbal_move doesn't accept values between +/- 40 (except 0)

[BramHy]

After upgrading the Gremsy T3V3 to the newest firmware release 7.6.5 the default set_gimbal_move doesn't work for values between +/- 40 degree, except 0. When rolling back to 7.5.9 everything works as intended.

Below is a slightly altered set_gimbal_move version which we used in our code.

void Module_Gremsy_Gimbal::setOrientation(float roll, float pitch, float yaw)
{
    // Prepare command for off-board mode
    mavlink_command_long_t comm = {};

    comm.target_system    	= system_id;
    comm.target_component 	= gimbal_id;

    comm.command            = MAV_CMD_DO_MOUNT_CONTROL;
    comm.confirmation     	= false;

    comm.param1             = pitch;
    comm.param2             = roll;
    comm.param3             = yaw;
    comm.param7             = (float) MAV_MOUNT_MODE_MAVLINK_TARGETING;

    qDebug("%f %f %f", pitch, roll, yaw);
    // --------------------------------------------------------------------------
    //   ENCODE
    // --------------------------------------------------------------------------

    mavlink_message_t message;
    mavlink_msg_command_long_encode(system_id, companion_id, &message, &comm);

    // --------------------------------------------------------------------------
    //   WRITE
    // --------------------------------------------------------------------------

    writeMessage(message);
}

Is it possible to verify this issue or guide us to an solution?

[RintoDeVries]

I contacted Gremsy for this issues and it is due to the default deadzone settings. You can change it in the firmware settings using gTuneDesktop.