Please keep in mind that the bayer image may have padding at the end of each row in order to align the line start with 16 or 32 byte boundary. This padding is done by the ISP when it receives the image from the camera.

For example, a number of common raw resolutions have the line stride listed in the FindFrameSize function in voxl-camera-server source code:

https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/dev/src/hal3_camera_mgr.cpp?ref_type=heads#L4636

Hi @jonathankampia
Hate to hand you off but this is out of my realm now.... I think @tom is more suited for helping on this front if we are sure it is no longer a HW issue.

@Alex-Kushleyev Thank you so much. Now the camera is working. Previously, during the installation, I selected a second option of continuing the installation process with the option to keep the same configuration, which was wrong decision. It did not gave me an option to choose my drone name before. But, now that i selected the first option that give questions along the way, i was able to select the correct options for my drone as shown in picture below.
e5761ce3-3a28-4d66-b2dd-eed62fffdf42-Screenshot 2025-09-04 160830.png

@sara-ab We have designed a new GPS mast that will greatly improve GPS performance on Starling 2 Max, please reach out to support@modalai.com

with your order number and link this forum post and we will make sure you get one

@saegsali These are all of the param files loaded on Starling 2 (D0014) by default:

https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/blob/master/scripts/voxl-configure-px4-params?ref_type=heads#L89

They can be found here, organized by folder:
https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/tree/master/params/v1.14?ref_type=heads

@psafi Unfortunately, the Mavlink module is not available on the DSP side. We tried it in the past and there were a lot of issues so we only have it on the apps side. You are welcome to try to add it into the DSP side and see how it goes.

@Federico-Wyrwal , please check the instructions for setting up EIS, specifically

https://docs.modalai.com/camera-video/electronic-image-stabilization/#minimal-software-setup

The latest drivers can be downloaded from here

Please let me know if you have any other questions.

Alex

@Grier Gotcha, please fill out this RMA form: https://www.modalai.com/pages/rma?_pos=1&_sid=6dd8dbced&_ss=r

Please link this forum post in the RMA form as well

VOXL 2 is a Linux computer, so if you want to write software to coordinate multiple UAS you have open access to do so

For Flir support, you can start here: https://docs.modalai.com/M0153/

For flight I/O, you can refer here: https://docs.modalai.com/voxl2-connectors/

For software support, you can refer here: https://docs.modalai.com/voxl-sdk/

@Alex-Kushleyev Thanks

@detlefurig Yes that is something we're actively working on, probably a few months out at this point

Hi @TomP
Looking pretty grim...
That specific signal is all buried at least 3-7 layers deep directly from that pad and it hits other BGA devices right in the pad.... no exposed traces, no exposed pins at all...
You'll have to find a different UART port or some other plan B.... sorry.

@J-B-Song Hello J.B Song, Did you connect HDMI via USB-C on VOXL2? Did you use this image
7d1ec055-c0a2-497c-8c85-be95d56a1125-image.png
Hope your reply soon, thanks so much.

@Huynh-Gremsy You cannot connect peripherals to the USBC port in that way, you'll have to use one of our add-on boards that breakout USB ports