@colombe-ai I'm not sure how much we're going to be able to help to get this going but I'd start with that magnetometer. Put an oscilloscope in the lines and see if you see any activity.

Hello @newdroneflyer , In order to adjust focus of the hires camera, you need to do the following: loosen the screw that holds the lens and prevents it from turning. this will allow the lens to turn within the assembly turn the lens using the lens focus tool (should have come with your Starling 2), it is a black plastic tool that goes around the rim of the lens and allows you to turn the lens. after focusing, tighten the screw that was loosened in step 1. [image: 1768501077911-starling2_hires_focus_steps.png] Here is the picture of the focus tool, it has two sizes - one for hires camera, one for tracking camera (if needed). You should have received one with the Starling2 (in an envelope, probably different packaging). [image: 1768505172374-starling2_focus_tool.jpg] Alex

Hi @JoonaR, Yes, the Starling 2 drones are shipped with the lepton adapter (M0187), but Lepton sensor itself is not included. https://docs.modalai.com/M0187/ Alex [image: 1768357442694-0cb77fc6-242f-4477-a15d-3c89f43d8f69-image.png]

@Alex-Kushleyev This unit was sent in on RMA 796.

@colombe-ai currently 30 business days is quoted on the website: https://www.modalai.com/products/starling-2-max It typically should ship more quickly than that though, likely 2-3 weeks There is no overnight shipping option as all of the drones are built to order

@colombe-ai You can find the batteries here: https://www.modalai.com/products/m10000538 Any 2S LiIon hobby charger will work. Something like this is all you need: https://www.amazon.com/ISDT-608PD-Battery-Charger-Discharger/dp/B0CM9BFQSX Handheld transmitter depends on the configuration of the drone. You can order the drone with a pre-bound charger ready to fly from the website. The main debugging cable is a standard USB-C cable

Hello @HsinSWT , When i see results like this, i would say there is probably 90% chance that the motor is bad. Unfortunately, there is a chance that the ESC is bad as well, and there is no good way to check the ESC without a known good motor (however the ESC failure is unlikely). As I mentioned in the previous post, if you had a milli-ohm meter, you could test the motor winding resistance to confirm whether the motor is good or bad. A tool like that measures resistance with high precision (similar to a regular Ohm meter). However, if you don't have one, it may not be worth buying it.. You will not be able to measure the winding resistance of these motors correctly with a regular Ohm meter. However, you will be able to detect a complete open circuit (which could be the case, maybe worth trying). If testing resistance using a regular Ohm meter, any two connections between the 3 motor phases will read 0 ohm (or close to that). If a wire is broken, then you can detect it. The Starling 2 motor (3000kV) has around 0.360 - 0.370 Ohm phase-to-phase winding resistance. In order to confirm that the ESC is working properly, you could temporarily connect one of the working motors to the ESC Channel 0 and do the same spin test (using voxl-esc tools), just to confirm that the ESC Channel 0 is working fine. In order to fix the issue, you could order a new motor and replace it yourself (will be a lot cheaper): https://www.modalai.com/products/starling-2-replacement-parts?variant=49707605393712 You could also send the whole drone back for repair (https://www.modalai.com/rma) Alex

@colombe-ai , when you flash a voxl2 SDK, there should be an option to set it up from scratch. did you try it? https://docs.modalai.com/voxl-suite/ Alex

@Eric-Katzfey I updated to SDK 1.6.0, which fixed the power display issue. I was still getting no valid local position preflight fail, but after I ran apt update && apt upgrade, things seemed to work.

@Muqing-Cao Here you go: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub/-/blob/dev/src/vio_manager.c?ref_type=heads#L450

@roy-crosthwaite see here: https://www.modalai.com/pages/rma

@Jakub-Tvrz said in Starling 2 Max for indoor: We haven't bought anything yet, but we are deciding what will be the best for our warehouse inventory application. Of course, we considered the ToF option. But you still say: "however, it is not... great" - does that mean that Starling 2 is better for our application? Or does Dual vs Triple camera for Visual Inertial Odometry also have an impact? Reply Depends fully on your use case. I will say that PX4's instance of obstacle avoidance is not fantastic, but it is better than nothing. In my opinion I would go w/ the model that has all the bells and whistles in case you need the hardware and decide to develop your own collision avoidance or somethign of that nature.

Were you able to solve this issue and unbrick the device? Can you explain how?

@jimbow77 , regarding #4, there are four batteries (two sets). #3 - we don't have an option to install FLIR Lepton, but you can purchase it separately (from another vendor) and install it. The adapter is present in Starling 2 Max, so you would just need to install the Lepton sensor into the socket. Alex

@Cliff-Wong Hi there. Thank you for answering my questions. We’re still using the same voxl-open-vins-server.conf settings with "en_vio_always_on": false and "en_auto_reset": true. I also updated the system to SDK 1.5.0 as suggested, but unfortunately, it didn’t seem to resolve the issue. To further investigate, I tested VIO performance by holding the drone in my hand and moving it manually while observing the trajectories in the VIO visualization. I noticed two distinct trajectories being displayed: QVIO and OV. Sometimes the OV trajectory appears more accurate when I move the drone in a “plus” pattern, and sometimes the QVIO trajectory is more accurate, but most of the time it tends to drift significantly, and sometimes QVIO doesn't move at all. I have two questions: 1-) What is the difference between QVIO and OV, and which one is actually used during flight for position estimation? 2-) What could be causing QVIO to fail to track properly, while OV performs well? (or the other way around) Also, I'm not getting any 'manual control lost' errors in QGC, and I'm able to control the drone perfectly fine. However, it doesn't respond to any control inputs on rare occasions, where the drone can't hold its position and continues to ascend when I use VIO in 'Position Hold' mode.