@Eric-Katzfey I configured the drone to have servo5 trigger the camera. When idle, servo 5 shows 1100. When triggered, it goes up to 1300. In the Mavlink messages I can now watch for SERVO_OUTPUT_RAW msg.servo5_raw and detect the rising edge which emulates the trigger.

msg = master.recv_match(type='SERVO_OUTPUT_RAW', blocking=True, timeout=2)
if not msg:
    continue
pwm = msg.servo5_raw

I have done this on a ground station using pymavlink to listen for messages. What is the best way to listen for this mavlink message on the VOXL2? Reminder - I am using Ardupilot.

@Eric-Katzfey We have the Hadron configured with voxl-camera-server.conf

"type": "ov64b",
"name": "hires",
....
"en_snapshot": true,
...

so we can take images with voxl-send-command hires_snapshot snapshot

I would love to configure the camera in Ardupilot with CAM1_TYPE and set DO_SET_CAM_TRIGG_DIST to a distance interval that I will capture images at.

If that is not directly possible, could you help me with a way to create a sort of interface script that sits on VOXL2 that listens for GPIO relay triggers or something like that? Then I can just call the snapshot command when triggered.

I have a VOXL2 running ardupilot and have a Hadron camera connected and configured with voxl-camera-server. I can take snapshots successfully.

I am trying to configure our drone to capture images at a specific distance interval during flight with the DO_SET_CAM_TRIGG_DIST parameter. Is there a way to do this with VOXL2 and ardupilot?

Thanks!

@Alex-Kushleyev thank you! It works now.

Hi,
I'm working with a VOXL2 and the FLIR Hadron 640 camera, and I'm trying to stream video from the OV64B sensor while taking snapshots at the same time.

Initially, I attempted to use "en_preview": true along with "en_snapshot": true, but that configuration did not allow me to stream video. I assumed it might be a resolution constraint, so I modified the configuration to use "en_small_video": true and "en_snapshot": true instead.

Now I can stream video, and when I enter the following command:
voxl2:/data/snapshots$ voxl-send-command hires_snapshot
Successfully sent command to /run/mpa/hires_snapshot/control
In the voxl-camera-server terminal, I receive this error:
ERROR: Camera: hires got unknown Command:
However, when I enter:
voxl2:/data/snapshots$ voxl-send-command hires_snapshot snapshot-no-save
Successfully sent command to /run/mpa/hires_snapshot/control
The camera server shows:
------ voxl-camera-server: Camera server is now running
Camera: hires taking snapshot for pipe only (not saving it)
But I’m unable to access the snapshot data, even after running adb pull.
My Questions:
Is it possible to stream and take snapshots simultaneously on the OV64B?

What does the error message “Camera: hires got unknown Command” mean?

How can I access the output of snapshot-no-save if it's not being saved to disk?

Thanks in advance for your help!
Below is my camera config code:
{
"version": 0.1,
"fsync_en": false,
"fsync_gpio": 109,
"cameras": [
{
"type": "boson",
"name": "boson",
"enabled": true,
"camera_id": 0,
"fps": 30,
"en_preview": true,
"en_misp": false,
"preview_width": 640,
"preview_height": 512,
"en_raw_preview": true,
"en_small_video": false,
"en_large_video": false,
"ae_mode": "off"
},
{
"type": "ov64b",
"name": "hires",
"enabled": true,
"camera_id": 1,
"fps": 15,
"en_preview": false,
"en_misp": false,
"preview_width": 1920,
"preview_height": 1080,
"en_raw_preview": false,
"en_small_video": true,
"small_video_width": 1024,
"small_video_height": 768,
"small_venc_mode": "h265",
"en_large_video": false,
"small_venc_br_ctrl": "cqp",
"small_venc_Qfixed": 30,
"small_venc_Qmin": 15,
"small_venc_Qmax": 40,
"small_venc_nPframes": 9,
"small_venc_mbps": 2,
"en_snapshot": true,
"en_snapshot_width": 1920,
"en_snapshot_height": 1080,
"ae_mode": "isp",
"gain_min": 54,
"gain_max": 32000
}
]
}

I was wondering if there is a way to log altitude and/or barometer data similar to voxl-logger for imu data.

Thanks

@Alex-Kushleyev yes you can reference the log

We were attempting a tuning flight with a fresh rebuild and while checking stability all motors shut off, drone flipped and crashed inverted. Log attached, of note is in the logged messages "landing detected at 09:13 while it was approximately 27m in the air.

https://review.px4.io/plot_app?log=6ad22692-fe3f-4cce-b8f0-a812d91bfa16

Hardware:
VOXL2
FPV ESC
Tmotor MN5006 450kv (params tuned for low kv)
Doodle Meshrider radio
Control via Jeti RC connected to GCS

@Alex-Kushleyev I found that the parameters were just not used and once I set them with px4-param set PARAM_NAME param-value that they show up in QGC

One that I am still stuck on though. I am looking for a parameter TRIG_PINS that is not in the list of params in px4-param show -a

The default is 56 and I need to know how to map the pins to the PWM expansion board. From px4 documentation:

TRIGGER_INTERFACE = 2
"Enables the Seagull MAP2 interface. This allows the use of the Seagull MAP2 to interface to a multitude of supported cameras. Pin 1 of the MAP2 should be connected to the lower AUX pin of TRIG_PINS (therefore, pin 1 to AUX 5 and pin 2 to AUX 6 by default). In this mode, PX4 also supports automatic power control and keep-alive functionalities of Sony Multiport cameras like the QX-1."

@Alex-Kushleyev I am looking to enable the seagull trigger in camera interfaces as shown here , but I do not see that option. I see that the interface is in the modalai repo but how do I enable it to show up in QGC?