Mavlink Camera Manager not appearing on QGC

[Daniel Ryu]

@Eric-Katzfey

Hires, stereo, tracking mavlink-camera-manager debug outputs (in this order). All three are running at the same time:

Voxl-streamer debug output for hires (only hires had updated debug output, other voxl-streamers only had the standard bootup debug)

[Eric Katzfey]

Okay, thanks! That shows, at least, a mavlink protocol session has been initiated with the mavlink-camera-manager. The camera protocol is documented here: https://mavlink.io/en/services/camera.html. The mavlink-camera-manager module is implementing a portion of that protocol. When it first connects there should be a flurry of protocol messages going back and forth. Once things are setup then it is just heartbeat messages as you see in the debug output above. So the key part of the debug output is the very beginning.

[Daniel Ryu]

@Eric-Katzfey Where can I go from here then, to be able to swap streams from a dropdown menu in QGC?

[Eric Katzfey]

Look at the beginning of the debug output from mavlink-camera-manager. Do you see anything besides the heartbeat / ping messages? If so, can you paste that here?

[Daniel Ryu]

@Eric-Katzfey

[jaredjohansen]

@Eric-Katzfey , we got it working. The secret we were missing was our MAV_SYS_ID was not set to 1, which, apparently, is what this capability expects. Thanks!

[Eric Katzfey]

@jaredjohansen Great! Glad to hear it!

[wilkinsaf]

We are facing a similar issue. Is it correct to say there is not one singular service on VOXL that will automatically stream all cameras to QGC?

We have to write our own script for it correct?

[Daniel Ryu]

@wilkinsaf Way we handled it was creating our own services/scripts for streaming to QGC automatically with mavlink-camera-manager. Hope it helps

[wilkinsaf]

@Daniel-Ryu

I figured. We just wanted to double check that this was the case. Thank you!