@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

@Aniruddha
How are you connecting the Ground Station to the Starling 2? Seems like your QGC instance is not fully loading up the parameters so you are not getting the sensors tab to do the level horizon calibration.

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

@Alex-Kushleyev Hi Alex thanks for your insight.

Here's the full dmesg output: https://limewire.com/d/QEPzc#F58jn5myhd when this issue is happening.

I am currently disconnecting the M0173 board, I will share the same debug outputs once the board is removed as soon as I can.

Cheeers

@cbay , yes this should work.

Whenever you add cameras of the same type, you should always check for possible I2C (CCI) conflicts. If you look here https://docs.modalai.com/M0188/#image-sensor-interfaces , the sensor IDs 0,2,3,6 (which is what you use) use unique CCI buses 0-3, so that is all good.

If you used ID 1, it would conflict with with another AR0144 on ID6 (both use CCI1)

One last thing to check is the sensor sync.

if you see fsin in the configuration of the sensor (and name of the sensormodule in /usr/lib/camera/), it means it is set up as a sync slave currently you have the IDs 0 and 6 set up as sync slaves, but ID 2 and 3 as free-running

There are two issues enabling sync'ed drivers for AR0144 in ID 2 and 3:

the driver is provided only for ID2 in : /usr/share/modalai/chi-cdk/ar0144-fsin/ - this is easy to fix ID1 and ID3 on M0188 do not have the sync line connected to the camera connector this is easy to fix by installing a 0-ohm resistor, which is DNI by default.

Depending on your requirements for VIO (which VIO are you using?), you may or may not need the cameras synchronized.

Please let me know your requirements and we can go from there..

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

Hello @adam , please see the following post regarding GPS signal quality on Starling 2 and Starling 2 Max : https://forum.modalai.com/topic/5116/gnss-emi-mitigation-guidelines

There is no voxl-gps service - voxl-px4 handles the GPS functionality, so as long as that is running, the GPS module should be active. Please go through the documentation linked above, there are some mitigation steps that are relatively easy to implement.

We apologize for the inconvenience, but enabling usable GPS on Starling 2 will require some tweaks.

Alex

@wilkinsaf

I did the following and was able to get it

installed arducopter 4.7 disabled serial2_option for mavlink forward configured compass configured acceleromter turned off GPS_AUTO_CONFIG set SERIAL3_BAUD to 115200

https://www.loom.com/share/b96c3edd2286477ea294ddbd262dc31e