You can also dump frames or record a video , for example:

voxl-record-video hires_large_encoded /data/vid1.h264

please note the resulting video may not be playable directly, but you can fix it using ffmpeg:

ffmpeg -r 30 -i voxl-record-video.h264 -codec copy videofile.mp4

or play on your PC:

ffplay voxl-record-video.h264 -framerate 30

@jocacace13 PX4 sends out it's local position (as Mavlink LOCAL_POSITION_NED)

For hires/tracking config C4, use J7 as shown in docs:
https://docs.modalai.com/voxl2-camera-configs/#c-04-hires-and-tracking

@david-devassy Have you been following the documentation here: https://docs.modalai.com/voxl-mapper/#voxl-mapper?

@utari_ais Since you're using a voxl1 px4 is running on the flight core not on the voxl itself like voxl2. Therefore there is no voxl-px4 service on voxl1

@david-devassy I'd recommend sending in an RMA: https://www.modalai.com/pages/rma and we'll get things sorted

@modaltb Hi thanks for the update. I have used the file which is shared by modal AI team through email and it worked 100%
Here is the file

https://storage.googleapis.com/modalai_public/qdl/2024-02-09-1.7.4-M0054-2.zip

Thanks again.

@Gary-Holmgren ,

Can you please confirm that in your 30cm extension use case you are using:
(starting from VOXL side..)

M0076 interposer 2x M0036 15cm flexes (connected back to back) M0010 stereo splitter 2x M0015 OV7251 cameras

Also, are the cameras being detected when using voxl-camera-server -l but the stream does not work? or neither detection nor streaming work?

We will try to reproduce your test case first and lets go from there..

Alex

@Gary-Holmgren,

Based on your results, the tracking camera is found in both cases (cam slot 2). It looks like one of the stereo cameras is not detected in camera configuration 03.

Are you using the dual flex extension (30cm)?

Maybe try to swap out flex cables?

@Gary-Holmgren , you are correct, the high resolution camera is not used for VIO, we typically use it just for video recording / streaming.

You can certainly add a new transform to the extrinsics file and use it in your application. You should use the same name for the camera in the extrinsics file as you name it in voxl-camera-server.conf just to be consistent.

@Ariel-Saez I already fix the problem, my seeker has the wrong sku version, more details with the fix, see my original topic: https://forum.modalai.com/topic/3286/qgroundcontrol-don-t-detect-transmitter

@modaltb

Hey Travis,

Thank you very much for your explanation and for passing on the link.
I understand how it was done now.

I will consider what is the next possible option for the project.  
I appreciate your time.

Best Regards,
Leon

@Vinny no problem for now I didn't try to charge it while being used it was just a question.
Julien

@Moderator When checking the sensors it appears one of the stereo cams is blurry due to the lens being scuffed, I cannot get it clean so going to have to get a new one as its probably causing the issue.

@Alex-Kushleyev Great, I will look into transferring compressed images. Thanks for the guidance!

@Alex-Kushleyev

Hi Alex, you're right, I am using IMX214 as hires camera,
If I set off the ae mode I should control the gain and shutterspeed in some way;
If I set the ae mode on (ips or lme_msv) I would need to set the min and max gain, min and max shutterspeed, the desired msv and some parameters to control the speed of the adaptation

is this possible?

thank you so much

@Gary-Holmgren , great! The transforms can be tricky sometimes especially with the added complexity of the image rotation in the camera…

Alex

@Gary-Holmgren I'm also going to update the help text on that error in our deploy_to_voxl.sh template as the "ERROR neither dpkg nor opkg found on VOXL" is obviously not accurate