@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

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

@Zachary-Lowell-0 yes, i copied that directly from the terminal after running this command voxl-inspect-detections -a tag_detections.

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

It's complicated to release and it often creates more problems than it solves. Is there something specific you are trying to achieve?

@psafi , are you asking about QVIO?

For QVIO we typically try to get the extrinsics from CAD, which should be quite accurate. If you don't have exact CAD, then XYZ measurements should be within 5mm accuracy or better and within a few degrees rotation. QVIO actually estimates extrinsics, so it will try to correct as part of its estimated state. QVIO will probably converge to correct extrinsics even if you have a larger initial error in the extrinsics, however it's not a good approach to rely on QVIO doing this every time you start QVIO, because it can make the initialization of QVIO more prone to errors.

In the case when exact measurements are not available, you just use your best guess and then run QVIO in a feature rich environment, while holding the the drone by hand, smoothly carrying it around (smoothly rotating and translating). QVIO should converge and its state actually reports the estimate of the IMU to Camera translation and rotation (the extrinsics). Running this test several times (completely restarting QVIO) you can see what extrinsics the QVIO converges to and whether they are consistent. Then, you can update your extrinsics guess to the average value of the translation and rotation you obtained after running QVIO.

Hopefully this helps, let me know if you have any questions.

Alex

@Federico-Wyrwal

Did anything happen between flight 1 and flight 2 which could have damaged anything on the drone?

When you power on your Starling 2, do you see blue lights blinking on the ESC? You can see the description of the expected behavior here : https://docs.modalai.com/voxl-escs/faq/#q-what-is-the-behavior-of-the-four-blue-on-board-leds. In the ESC datasheet (https://docs.modalai.com/voxl-mini-esc-datasheet/) you can see which side the LEDs are located and one of them is labeled, you should be able to spot the other three next to the each MCU.

Do you hear a tone that the ESC typically makes (using motors) when the power is applied?

Please check the integrity of the UART cable that connects the ESC to VOXL2.

Alex

@jakkkkobo ,

The source code of voxl-send-neopixel-cmd test tool is here : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-io-server/-/blob/master/tools/voxl-send-neopixel-cmd.c

The function that creates a binary packet (which is forwarded to the ESC via PX4) is here : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-io-server/-/blob/master/lib/modal_io.c#L181 . Basically you need to provide the following information to this function:

number of LEDs you are controlling LED type (RGB or RGBW) array of LED colors (3 bytes for each LED in case of RGB, or 4 bytes per LED for RGBW). the array should contain all LED values ranging from 0-255, so if you had 3 LEDs and first should be red, second green and third blue (50% power), the LED color array would be : [127, 0, 0, 0, 127, 0, 0,0,127]. this function will create a packet with checksum and send it to PX4, and PX4 will forward the packet to the ESC.

You can modify the voxl-send-neopixel-cmd to do what you need, maybe you can make it accept an array of LED color values via command line.

I know the tool could have been more helpful. If you describe your use case, maybe I can help improve the voxl-send-neopixel-cmd tool.

Alex

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