This is also posted in the Arduplane 4.4.4 category.
We have a Sony ILX-LR1 trigged by GPIO and a FLIR Vue Pro trigged by PWM. Both cameras trig if I set them as CAM1. The camera used as CAM2 never trigs. The only setting changed beeing CAM1_TYPE = 1 and CAM2_TYPE = 2.
The camera used as CAM1 trigs ok, the camera used as CAM2 don’t trig. This is tested using the “Trigger Camera NOW” command in Mission Planner. I don’t know if the behaviour is the same using the DO_DIGICAM_CONTROL command in a Auto Mission. If the DO_DIGICAM_CONTROL works for both cameras I can live with that - anyone know?
How may I use the newer camera trigger commands from Mission Planner?
Hi,
did you ever manage to solve the problem?
I tried the same today and have the same result. CAM1 (used with Relay) trigs but CAM2 (used with PWM) trigs not. But if I use the Aux Function on Mission Planner tab, set one channel to Camera Trigger and click on “High”, CAM1 (Relay) and CAM2 (Servo) both trigger.
edit: I think I found the problem. The “Camera Trigger” button (and problably the FC in Auto-mode) triggers only CAM1. If I swap the settings to CAM1 = Servo and CAM2 = Relay, on the Servo camera gets triggered. @rmackay9 is there a possibility to change this in the upcoming firmware versions?
I use ArduCopter V4.5.7 and I gave it a try today. So, good news!
The trigger works for both cameras. Also when you trigger via RC, both cameras trigger. On my setup with one camera trigger as relay and the other as servo, it also works! So give the new firmware a try!
One thing I noticed today: CAM1 works perfect but it seems that CAM2 only triggers sometimes. I cannot explain how and why but I tried to do a mapping mission with a Sony A6000 and a Micasense Rededge M. When I assign the Rededge to CAM1, it works perfectly (>400 images taken) but the A6000 (as CAM2) takes only about 23 images. When I swap the assigment, it seems that the A6000 work perfectly and the Rededge takes only a few pictures.
Do you have a similar behaviour?