@Morten-Nissov , great! You are welcome. Make sure to change that 1us scheduling interval to a more reasonable value 🙂

@Jetson-Nano Unfortunately not given the state of the board

@robertociuch , I tested the dual stereo configuration with M0036 14.5cm extensions on each stereo. Stereo pairs plugged into J6 and J8, just like Camera Configuration 11 shows (link), I unplugged all other cameras. Seems to be working fine. I am attaching the voxl-camera-server.conf file with just stereo set up. Also, i am using SDK 1.3.2, however it should be working with older SDKs. If you find that installing the longer flex is an issue, it is possible that the flex itself is problematic. You can test the stereo pairs individually to find if there is a particular cable that is bad.

Also, please double check that the following sensormodules (camera drivers) are present in the correct location:

voxl2:/$ ls /usr/lib/camera/*combo* /usr/lib/camera/com.qti.sensormodule.ov7251_combo_0.bin /usr/lib/camera/com.qti.sensormodule.ov7251_combo_4.bin /usr/lib/camera/com.qti.sensormodule.ov7251_combo_1.bin /usr/lib/camera/com.qti.sensormodule.ov7251_combo_5.bin { "version": 0.1, "fsync_en": false, "fsync_gpio": 109, "cameras": [{ "type": "ov7251", "name": "stereo_front", "enabled": true, "camera_id": 0, "camera_id_second": 1, "independent_exposure": false, "fps": 30, "en_rotate": true, "en_rotate_second": true, "en_preview": true, "preview_width": 640, "preview_height": 480, "en_raw_preview": true, "ae_mode": "lme_msv", "ae_desired_msv": 60, "exposure_min_us": 20, "exposure_max_us": 33000, "gain_min": 54, "gain_max": 8000, "exposure_soft_min_us": 5000, "ae_filter_alpha": 0.600000023841858, "ae_ignore_fraction": 0.20000000298023224, "ae_slope": 0.05000000074505806, "ae_exposure_period": 1, "ae_gain_period": 1 }, { "type": "ov7251", "name": "stereo_rear", "enabled": true, "camera_id": 3, "camera_id_second": 2, "independent_exposure": false, "fps": 30, "en_rotate": false, "en_rotate_second": false, "en_preview": true, "preview_width": 640, "preview_height": 480, "en_raw_preview": true, "ae_mode": "lme_msv", "ae_desired_msv": 60, "exposure_min_us": 20, "exposure_max_us": 33000, "gain_min": 54, "gain_max": 8000, "exposure_soft_min_us": 5000, "ae_filter_alpha": 0.600000023841858, "ae_ignore_fraction": 0.20000000298023224, "ae_slope": 0.05000000074505806, "ae_exposure_period": 1, "ae_gain_period": 1 }] }

@Alex-Kushleyev Thanks! This is helpful. Definitely easier to overheat these than the last gen so good to have the specs on it.

@Stefan-Amundarain what do the flight logs tell you?

@Prabhav-Gupta , you are welcome!

@Alex-Kushleyev,

Cool, Thanks a lot!

@Alex-Kushleyev I tested the ToF with another VOXL2 board I have. Modified the camera config as only for ToF. On ground tests, the camera server seems to work fine. On terminal system logger publishes similar type of CAM_INFO, CAM_ERR dmesg -w messages as earlier.

We used the same interposer as used in earlier VOXL2 compute.

@Vinny
As per the parameters you provided, this sensor cannot operate at temperatures below 0 degrees Celsius.

Thank you!

@tom Thank you. I'll look it up.

Yes, Hadron is working when plugged into J6 of VOXL2 Mini with default kernel.

You just need to have the following sensormodule files in /usr/lib/camera/:

com.qti.sensormodule.boson_0.bin com.qti.sensormodule.ov64b40_1.bin

And instead of gpio6, you need to use gpio30 to enable the CCI mux, so that communication with the EO camera is enabled:

voxl-gpio -m 30 out voxl-gpio -w 30 1

I will update the Hadron documentation..

Alex

@jbhines929 No problem, thanks for the patience!

@Eric-Katzfey Thanks for the explanation, I was not starting the voxl-camera-server before.

When I started the voxl-camera-server, I had my camera configuration include the tracking camera which stopped the voxl-camera-server from starting correctly.

Once I changed my camera configuration with voxl-configure-cameras to "hires only" I was able to start the camera server and then start the voxl-streamer as well.

WOW! Thanks @Lynn-Koudsi for the help, when we setup the forum this is the kind of interaction we were hoping for, just awesome!!

Sorry for the setup and 'wonkyness' right now, we've been somewhat caught with getting pre-release software out there without all the setup/docs lined up.... so we're doing a little catchup it seems.

@Liping there until we have our docs updated, if this is working, I'd say this is a good approach!

Thank you both for the details, we'll relay this through the team.

Yes, after adding some foam, The UAV now are stable than a bit. Do you think the battery should be problem? Our 3S battery are quite old.

@manzur Interesting, thank you for the information! Perhaps I was wrong about the default Network ID, I will take a note of that.

@xav04 I am trying to do the same thing as you, by using the J9 port on the 5G Modem to attach an RTK GPS.
Were you able to do so?

Also, how should mavros (px4.launch) be run with the internal px4 on the voxl2?

Thanks. I got it working and it appears to be calibrated. It also appears to be responding as intended with MAVROS when I publish to /mavros/setpoint_velocity/cmd_vel_unstamped

I tested with props off and powered via battery. I published 0,0,1,0 corresponding with vertical speed of 1 m/s up and the motors sped up. I then published 0,0,-1,0 and the motors slowed down as expected.

@modaltb Yes, we used r14.1a_1.1.2-M0054-14.1a-FLAT-V3.zip as well.

We will make a try with removing all the hardware connection.