MAVLINK Trigger "MAV_CMD_DO_DIGICAM_CONTROL" from FMU CAM_TRIGG_TYP=MAV

Ground Control Software MAVLink
1

I don’t think this is in the correct place to post this, but at least it’s under MAVLINK :rofl:.
But it applies for all flavours (Copter, Plane)

We have several “custom cameras” (cameras/sensors) attached to FMU via one of the UARTs.
They all respond to mavlink_msg_command_long_decode(msg, &command); Command == 203.
They all have their own COMPONENT_ID 100, 101,102 etc.
We can trigger them from Mission Planner when it is set to component 100 or 101… BUT NOT ALL (Not sure what the message target is for ALL).

I have discovered there is no MAVLINK MAV_CMD_DO_DIGICAM_CONTROL from the FMU.

CAM_TRIGG_TYPE has options for 0: Servo, 1:Relay, 2:GoPro in Solo Gimbal
CAM_TYPE has ): Default 1:BMMCC

There is no MAV_CAM option. unless it is just hidden.
Do I need to raise a PR for this option? or am I just missing something?

Thanks

Anthony

2

Same question here.

no mavlink_msg_digicam_control_decode function

// handle incoming mavlink messages
void AP_Camera::handle_message(mavlink_channel_t chan, const mavlink_message_t &msg)
{
WITH_SEMAPHORE(_rsem);

if (msg.msgid == MAVLINK_MSG_ID_DIGICAM_CONTROL) {
    // decode deprecated MavLink message that controls camera.
    __mavlink_digicam_control_t packet;
    mavlink_msg_digicam_control_decode(&msg, &packet);
    control(packet.session, packet.zoom_pos, packet.zoom_step, packet.focus_lock, packet.shot, packet.command_id);
    return;
}

// call each instance
for (uint8_t instance = 0; instance < AP_CAMERA_MAX_INSTANCES; instance++) {
    if (_backends[instance] != nullptr) {
        _backends[instance]->handle_message(chan, msg);
    }
}

}