@Aniruddha
On QGC, do the Parameters ever fully load? The reason I am asking is because if the connection to the GCS is not fast enough or strong enough for QGC to fully download the parameters then the other tabs like sensors and actuators in QGC will not appear. Which is why you are having an issue doing the level horizon from QGC. I know that QGC is seeing the video feed meaning you are connected, is the Green bar going across the full length of the fly view bar on QGC?

@restore , the change to enable the maximum resolution raw output for OV64B was made at the end of October 2025, so you would need at least SDK 1.6.0, I believe. There was a change in the camera pipeline (not the camera driver) to allow such a large image size. Are you able to test on a newer SDK (just test the latest if you can)?

Additionally, the resolution 9248x6944 cannot be directly used in MISP debayering (which uses OpenCL). There are some special requirements on the image stride, which width of 9248 does not match. So what will happen is the cpu will realign the image before feeding it to the gpu, but it is a lot of data to copy for a 64Mpix sensor. So I made a small change in width from 9248 to 9216 (just cut off 32 pixels) and it can be fed into the gpu directly. That change is not published yet, but i can share it.

Lets first confirm that you can use the 1.6.x SDK to start the camera server at 9248x6944 and you should be able to save raw bayer and view the misp output.

you can always double check the list of available raw resolutions using voxl-camera-server -l

by "start the misp output stream", i mean that you need to have a client that subscribes to the misp output stream, so that the frames start going and AE can work, sending exposure and gain updates to the camera, so that the image is properly exposed. For example, viewing the stream in voxl-portal or just using voxl-inspect-cam hires_misp_color to get the data flowing, then you can save the raw bayer, which will have the proper exposure and gain applied.

Alex

Hi @irw
Can you please post High Res and clear photos of both sides of the VOXL 2?

@Eric-Katzfey
Thank you for your response. I would like to connect to pins 7 and 8 of J19.

7: I2C3 SDA 3.3V
8: I2C3 SCL 3.3V

@tom Thank you!

@Myles-Levine , the VOXL2 SoC is not designed to run at full power for a long time without cooling.

The maximum operating temperature is around 95 deg C, at which point, the CPU will being automatically throttling (reducing) operating frequency.

It is common to rely on air flow from propellers when the drone is flying, however some implementations may have a small fan as well.

Since you mentioned bench testing, installing a small fan next to VOXL2 to get airflow over the board should help. No specific recommendations, you can start with a standard 12V fan used in PC power supplies.

It can be relatively easy to overheat VOXL2 without cooling, because it has quite a powerful processor and the heat is concentrated in such a small package. You can spend more time optimizing the code (if possible) or add passive and / or active cooling.

Alex

Hi @Daehan-Won
To help us, what camera and how is it connected (cable details, with photo will help)
We want to first understand how much power it needs.

However, if it appears upon boot up, that is usually the worst power draw (in-rush), so I'm not inclined to think this is the case. It may be loose wiring, which is why a photo of your cable setup will also help. Even the slighest intermittent glitch on USB will create USB reconect events.
You can monitor that in a VOXL console (over ADB) with this command :

dmesg -w | grep -Ei 'usb|xhci'

Thanks!

@Noah-Heinen , unfortunately it is not possible to add a TOF sensor to your current Voxl2 Mini configuration. M0188 adapter does not support TOF.

The only way this would be possible is:

remove M0188 add M0172 and connect TOF and either M0186 or M0166 camera add another M0172 or M0194 and plug in a single camera. Unfortunately right now we don't have a small adapter like M0172 or M0194 that supports two standard cameras like M0166 or M0186.

So you would probably be losing one of the tracking cameras if you want to add a TOF sensor.

Alex

@Michael-Soul , it is EAR99