@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

@Alex-Kushleyev

Connection Method:
I connected the IMX412 camera module directly to the VOXL2 board using the M0076 interposer (not M0135). The M0076 interposer allows direct connection between the camera module and the VOXL2 board without any extension cable.

Setup:

IMX412 camera module → M0076 interposer → VOXL2 board No M0036 extension cable used Direct connection through the interposer

@psafi In this case we don't use voxl-mavlink-server directly because we are essentially setting up a "mavlink device" straight into px4.

Detections is pertinent to voxl-tflite-server and onboard computer vision on yolo, NOT on april tags.

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

@tom Thank you so much. It is working now with your suggestion. I think the README file of voxl-tflite-server need to be updated.

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

Hi @mkriesel
My comment was in regards to Alex's suggestion such that if you use an independent UART cable, you can ascertain whether the issue is with the ESC or the VOXL 2. MCBL-00091 will allow you to do that from a host PC as Alex mentioned.
It is live now on our shopify site if that will help.
https://www.modalai.com/products/mcbl-00091-1?_pos=1&_sid=b6335d3d1&_ss=r

@Alex-Kushleyev Ok great. Thanks.
One more question, to configure VIO/QVIO for a custom frame with a single (downward) camera, how should I go about following the documentations?

I am starting with https://docs.modalai.com/open-vins/

However I came across this:
"This documentaion will assume that there are some steps that have already be taken. ...Assuming that we are working with between two and three camera tracking."

are there different procedures for a system with single camera? Also a high-level roadmap on how to go about configuring VIO/QVIO for a custom frame would be appreciated in case information is in multiple places in documentation. Thank you for your support.

@Sam-Kiley , yes, every Starling 2 / MAX is going to have M0173 board installed and needs to use the option 1.

Alex

@psafi the html file is saved in the same folder where you run voxl-esc-spin* scripts if you have --enable-plot 1 . on VOXL2, the plot wont show up on screen, since there is no screen attached to VOXL2 (which would work on a linux pc), but it will be saved to html. In order to save to html, you will need to have plotly installed. You may first need to install pip3

apt update apt install python3-pip pip3 install plotly --upgrade

Alex

@Federico-Wyrwal , thank you for the reply. More debugging would be needed to figure out the root cause and it looks like you already submitted an RMA for the inspection / repair, so we will take care of it. Thank you.

Alex

@Moderator got it. Thanks!

@Eric-Katzfey never mind about the cable, I found them on Amazon...

@tomverstappen , I am glad you got this resolved. The "unknown board" message you were receiving was due to the older release of voxl-esc package, which did not recognize (and did not have firmware for) the M0129-6 ESC, which is the 6S-compatible version of the M0129 ESC.

I hope this clarifies that issue.

Alex

@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

@Eric-Katzfey
No, I am not saying the sensors are not working.
In fact, I haven't tested yet.
I just stated everything mentioned in the flight-core-v2 user guide.
Link- https://docs.modalai.com/flight-core-v2-onboard-sensors/

So, while testing, I can check it or configure it on PX4 and reprogram.

If everything is working, why user guide say?
87941590-b202-47e4-8c6a-56db8d76c26d-image.png

So, as per you say, BARO1 is working but disabled?
And BARO2 is working perfectly. Even though there is a mention of software not ported?

Please clarify for both.
Thank you.

@Vinny Thank you for reverting back, I will follow the steps you mentioned along with the ESD safe method.

@Vinny Got it. Thanks!