@Roy-Azriel , the description of Starling 2 Max states that it uses VOXL2, as well as lists other major components and options for camera configurations : https://www.modalai.com/products/starling-2-max?variant=48216084087088 Please let us know what Lidar you are considering adding. Alex

@aheyne , please send us a message via contact form. We don't sell this part separately as a product, but will help you with a replacement. You will need the M0177 flex cable (as the print states on the cable). https://www.modalai.com/pages/contact-us Alex

we just posted an update on this topic, please see https://forum.modalai.com/topic/5116/gnss-emi-mitigation-guidelines .

@colombe-ai , please see https://forum.modalai.com/topic/5116/gnss-emi-mitigation-guidelines

@qubotics-admin First you need to determine the version of PX4 running. With ssh or adb you can run the following at the command line: px4-ver all. You will see PX4 version and Vendor version. So, for example, for px4 version 1.14.0 and vendor version 8.134.3 then you would checkout the tag v1.14.0-8.134.3-dev from the repo to see that commit.

@ey , please send us a request via http://www.modalai.com/pages/contact-us Alex

@Maxwell-Schaefer Thanks for your reply. Is this step also applicable for the BetaFPV Nano RX? Should this also used ModalAI's firmware repo? Or will this use BetaFPV's? I did look into trying to flash the Nano RX initially, but stopped short of doing it as the physical RX itself did not have a BetaFPV silkscreen on it, so I assumed that it might be using a different firmware from the stock BetaFPV Are you able to advise on the other queries regarding the new wifi adapter board?

@Vinny Perfect, thanks!

@Leo-Allesch , if you are talking about VSLAM, which stands for Visual Simultaneous Localization and Mapping, then this is a sub-class of SLAM which uses only cameras (and often IMUs, then it is VISLAM). VSLAM and VISLAM usually generate and maintain a sparse map of 3D features (points), which is used for self localization. If you want to be able to detect a target, and you have your 3D pose from VIO (VIO = VISLAM), then you can either triangulate the target location or get it's location from a single frame if you know the size of the target (such as April tag, etc). Then you can transform the coordinate of the tag from the camera frame into your "world" (VIO) coordinates. The depth sensor would allow you to build a more detailed 3D map / point cloud using the 3D pose output from the VIO algorithm (or just using a depth sensor, which may be more complicated). You can also build a dense 3D map using camera only (and IMU), but that typically requires a lot more computation than using a depth sensor. You don't necessarily need a depth sensor for identifying the position of a specific target that is easily detected by a camera. There is a lot of research material you can find on these topics, please look into it deeper and let us know if you have specific questions about using VOXL2 hardware and software. Alex

@jbhines929 Please fill out the RMA form to get the process started. If it is due to manufactures defect it is covered under warranty and no diagnosis fee will be charged.

@brandon there are likely a number of things going on If the drone sits idle for a period of time, the sensors heat up (accel and baro). When the props start spinning, the temperature drops causing significant drift. If you let the props spin for 10 or 20s cooling off the board, that can help I would guess after 30-60s of flight, the altitude stabilizes. That is the temperature of the sensors stabilizng. The latest SDKs have temperature compensated calibration for IMU and baro. Try calibrating accel and baro and see if that helps. https://docs.modalai.com/calibrate-baro/ https://docs.modalai.com/calibrate-imu/ The GPS on Starling 2 Max has been tricky. We do have a new GPS on the way that looks promising, and hope to make it available in the next 2mo.

@Moderator thank you so much, I will go through that now.

@Moderator Order #7559 And, yes I ordered the configuration without the radio? But I wasn't told that it wouldn't include a GPS module?

@Cliff-Wong the drone is on SDK 1.5.0, I switched to open vins, and the vio portal reflected the movement, but when i toggled my controller from manual mode to position mode, the drone crashed for the first fight, on the second and third trial the drone kept landing, when i tried the fourth time, the drone finally maintained the height and hovered. Why do I have that unpredictable behavior ? I have attached images of my controller to show the toggling i meant. Kindly advice. Thanks. [image: 1771003494197-whatsapp-image-2026-02-13-at-10.53.46-am.jpeg] [image: 1771003494284-whatsapp-image-2026-02-13-at-10.53.46-am-1.jpeg]

@ramp I have the same issue. Can I ask you how did you solve it ?

@Moderator said in Blue Zorro specs?: COTS Radiomaster Zorro Oh interesting that its 1w 915mhz! ok that's so cool. But 2k right?

@Nitin-Varma-Vegesna Well, that's why I asked you to do the full SDK installation. If you install the SDK and set it up as we do from the factory then it should be working like when you first got it. If it doesn't then that potentially points to some damage caused by the crash and not some configuration change you have made since then.

@clange It is technically possible as Stinger is supported by the same VOXL SDK as all of our products. It would likely be a lot of software development to make it happen though