Yesterday on a test photo survey mission, about a third of the hot-shoe CAM messages were missing. All of the TRIG messages (camera shutter commands) were present - about 850 images.
Since having this problem, I’ve remounted the camera on a new quad-copter. The wiring is new. For some reason I no longer have this problem. So my best guess is that I had faulty wiring that wasn’t keeping a good connection.
The camera now works properly. So my best guess is that I had something wrong in the wiring - and it’s now working properly on the new copter.
As info - when CAM messages are missing, it is possible to geotag with the TRIG message - which are all present.
The meaning of the CAM messages changes if you’re using hot-shoe sensing or not. If you’re not using the hot-shoe input, the CAM messages record every time the autopilot commands the camera shutter.
If you’re using hot-shoe sensing, the CAM messages record when the hot-shoe signal occurs - which is when the camera shutter is triggered. Also - a TRIG message is recorded - which records when the autopilot commands the camera shutter. This makes the TRIG messages when using the hot-shoe the same as CAM messages when not using the hot-shoe.
The Mission Planner geotag utility allows using either CAM or TRIG messages. So if the CAM messages are lost, the TRIG messages can still be used for geotagging - even if it’s a little less accurate.
Hello Joseph. Thank you for your response.
Ultimately, the root cause of the malfunction in my FC was found elsewhere.
I am using CUAV’s Nora product, and it turns out that the GPIO pin numbering set by CUAV differs from that mentioned in the Ardupilot wiki. I am attaching a link for your reference, although I’m not sure if it will be helpful to you. https://doc.cuav.net/flight-controller/x7/en/ardupilot-users-manual.html#gpio
Thank you for the active involvement in Ardupilot. I look forward to your continued support.