WOW what a great thread, so on time for me Thanks Kris

No. I don't have any other voxl.
Yes, it's properly installed. I had previously worked with the same ADB installation. Suddenly, it stopped responding. I also tried with two other machines with proper ADB installations. It showed the same problem (no device found).

@Ansel-Misfeldt

FW update feature is working in QGC daily build starting today, no change needed on flight core v2.

23df224f-21ae-4469-b90e-bb255be91ab0-image.png

hi @suvasis

#test voxl-esc tools cd /home/root/voxl-esc/tools ./voxl-esc-scan.py #perform ESC testing / calibration #...

this was just a place holder for any testing you want to do with the voxl-esc tools.

#when done, restore original libpx4.so cd /usr/lib/rfsa/adsp rm libpx4.so cp libpx4.so.bak libpx4.so systemctl enable voxl-px4 reboot

This part restores the PX4 functionality, because in order to use voxl-esc tools on VOXL2, the instructions told you to disable PX4 while using voxl-esc tools. Soon we will not require disabling PX4 to use voxl-esc tools, but currently you have to do it.

Please note that we just made some updated to the voxl-esc tools and directory structure has slightly changed. Also, you no longer have to download the binary tools package and add it to the voxl-esc/tools directory. Please see an example params file here : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/dev/voxl-esc-params/old/esc_params_modalai_4_in_1_revb.xml

@Eric-Katzfey said in QGC sensors - compass remains red:

t isn't being specified correctly. It's kind of hard to tell in the picture but, at a minimum, the board is rotated 180 degrees. So it's the IMU rotation that needs to be set.

yes, the board is rotated 180 degrees. So, how do I set the rotation of the IMU to 180 degrees? is it in the same config file?

I rotate it 180 degrees as shown below

AAAA.png

@Moderator Hello - sorry if this isn't needed, but I put some settings/configs from one of the drones a couple messages up. If you could recommend other settings to look at to help get telemetry flowing between FCv2 and VOXL, it would be much appreciated. I'm happy to provide other settings/configs, just let me know what is helpful.

Thanks,

Jay

@Alex-Kushleyev Thank you very much for the solution, I fix it and it works. : )

@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.