@NikosMav Yes, things will get hotter when running QVIO. But once you arm and start the props everything will cool down. When reflashing the SDK I would grab one of the official releases from our downloads page and not a nightly.

@saegsali But how were you trying to access the I2C? What software? Via PX4?

Sorry to hear that.

https://www.modalai.com/pages/rma

You can provide a link to this post when you submit it.

Hi @Alex-Kushleyev ,

My apologies for the confusion. To be precise: we didn't add any third-party or custom heatsink. However, to replace the damaged 4K and ToF camera flex cables, we did have to unscrew the VOXL 2 board from the frame to access the connectors safely.

Once the new cables were plugged in and the board was screwed back into place, the ICM42688 PCB damage / clock line disconnected error appeared.

I have attached the pictures of the current assembly inside our Starling 2 so you can verify that the M0054 board, the integrated cooling plate, and all camera flex cables are correctly in place and undamaged from the outside.

Given the log and the pictures, what do you propose we do to get the drone operational again?

Regards,
Luis

Image 2026-06-30 at 09.24.19 (1).jpeg Image 2026-06-30 at 09.24.19.jpeg Image 2026-06-30 at 09.24.18 (2).jpeg Image 2026-06-30 at 09.24.18 (1).jpeg Image 2026-06-30 at 09.24.18.jpeg Image 2026-06-30 at 09.24.17.jpeg

Yes, please check the downloads section. C26 , C27 come with TOF sensors, so the CAD model for those variants should contain the correct front camera mount (please let us know if you have an issue finding it).

Also, we do sell a replacement plastics kit for Starling 2 Max (https://www.modalai.com/products/starling-2-max-replacement-parts) but it is not clear which front camera mount it has.. checking..

Alex

@Eric-Katzfey Thank you so much this fixed the issue!

@Raiyan-Alam said in Is there a way to power this Wi-Fi Adapter + Radio using this specific ModalAI UART adapter board?:

rfd900x

Hi @Raiyan-Alam,
My suggestion: keep the Wi-Fi adapter on USB and feed the RFD900X separately.
You can pull an extra 5V feed using this power module cable, which splices off a 5V red JST SFHR connector:
https://docs.modalai.com/cable-datasheets/#mcbl-00095
Splice from that into the RFD900X's 5V input. For the M0151, don't power the RFD900X off USB but pull it directly from the power module supplying VOXL 2 instead.

if no internet is available onboard llm+NPU can help repairing-agent to fix the issue or provide reason of failure.

Hi @Julian ,

Thank you for the detailed report. It does look like there is a missing (or broken? hard to see) magnet in the motor, in which case the motor will not work properly and should be replaced. No further testing is needed, as this is most likely a manufacturing defect of the motor or a result of an impact.

If you believe that the motor was defective when you received the product, you should request a free replacement motor (submit an RMA form) . If the motor was damaged while testing, you can purchase a new motor.

The Starling 2 Max replacement parts can be found here : https://www.modalai.com/products/starling-2-max-replacement-parts (however i don't see just motors without a frame + motors kit, will double check..)

Alex

Hi team — just bumping this in case it slipped through. We're ready to buy one evaluation unit and would really appreciate a quick steer: can the Stinger Vision FPV run AUTONOMOUS VIO/SLAM + AprilTag precision landing, or would Starling 2 / Starling 2 Max be the better evaluation platform for the requirements above? I've also emailed sales@modalai.com in parallel, so whichever channel is easier works for us. Thanks!

@ralinaresg What SDK version is loaded on the Stinger?

For visibility, since this seems related to the old BLE/VOXL discussion here:
https://forum.modalai.com/topic/1730/bluetooth-ble-communication-on-the-voxl-is-it-possible

I was able to get BLE 5.0 extended advertising scanning working on VOXL2 / Starling 2 with an ASUS BT500 / Realtek RTL8761B USB adapter by backporting newer upstream Linux Bluetooth HCI event parsing logic into the QRB5165 4.19 kernel tree. My understanding is future revisions of VOXL will have more up to date kernels that solve this issue without back porting.

The issue we were hitting was with LE Extended Advertising Reports. With BLE 5.0 beacons transmitting extended advertising, the older 4.19 Bluetooth path could mis-handle extended advertising report parsing / event-type bits, leading to bad report handling and, in our case, Bluetooth instability / crashes during scanning.

The relevant upstream Linux changes I used as reference include:

b48b833f9e8a - Bluetooth: HCI: Use skb_pull_data to parse LE Ext Advertising Report event ad38e55e1c89 - Bluetooth: hci_event: Ignore reserved bits in LE Extended Adv Report 0cadf8534f2a - Bluetooth: hci_event: Mask data status from LE ext adv reports

There are also related Realtek / extended-scan quirk changes upstream, but for our immediate case the stronger LE extended advertising parser backport was enough to stop the crash path and allow scanning.

Validated result:

VOXL2 / Starling 2 QRB5165 4.19 kernel ASUS BT500 / RTL8761B USB BLE adapter BLE 5.0 beacons using extended advertising btmgmt --index 0 find -l successfully reports devices and RSSI btmon captures LE Extended Advertising Report events no more Bluetooth NULL pointer dereference / hci_le_ext_adv_report_evt crash during the test observed all 16 expected beacons and repeated RSSI samples

I’m not proposing this as a merge-ready ModalAI patch, but I put the build changes and notes here in case anyone else needs BLE 5.0 extended advertising / RSSI collection on VOXL2:

https://gitlab.com/steven323/qrb5165-kernel-build-docker

Relevant upstream commit links:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b48b833f9e8a
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad38e55e1c89
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0cadf8534f2a