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

@jmltt SDK testing for Sentinel ended at SDK 1.4.0 That doesn't mean that newer releases won't work, it just means we don't put it through the SW QA testing cycles that we do with our newer platforms. You likely won't see any major performance improvements on Sentinel with newer SDK releases but there may be some nice quality of life additions such as helper scripts, voxl-portal updates and others. If you have any questions about any specific packages feel free to ask.

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

@taiwohazeez Can you post a video of it trying to fly?

@Zachary-Lowell-0 Hi, let me explain what i meant by hovering mode. There is a 3-way toggle switch beside the kill switch in the transmitter (toggling down switches to position mode, toggling up switches to the autonomous mode, while toggling to the middle maintains the drone flight positioning. I have another drone that when the button is switched to the middle, it maintains the drone position (thats what i meant by hover mode). My other starling 2 drones maintains their positions when the switch is toggled to the middle position, but this particular starling 2 drone doesnt.

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.

If anyone has run into this again, ensure you update your /etc/modalai/voxl-tag-detector.conf to the tracking camera pipe you would like to do the april tag detection on. the "tracking" has gotten update to "tracking_down" or "tracking_front"

@SystemBrute . The problem has been solved.

@Karthik-Bharadwaj You'll need to insert this into the unused XT30 connector: https://www.modalai.com/products/mcbl-00109?_pos=1&_sid=cc83b4694&_ss=r 3A is more then enough to power the drone on the bench, just make sure never to spin motors on wall power! (You can damage the drone and will not be able to RMA it) In order to disable arming you'd have to look through the PX4 parameters

@roy-crosthwaite , please submit an RMA form for a replacement : https://www.modalai.com/rma Thank you Alex

Hi @souksakone We do not support powering and arming any sUAS from a power supply. The ESC and other electronics will be damaged, and our warranty does not cover that. If you need a bench top supply for code config, development, etc (without arming motors at all), then we sell a 30W adapter for XT60 here and you can adapt to Starling 2 max without much trouble: https://www.modalai.com/collections/accessories/products/ps-xt60

@oiler251 You should be able to arm with the arm gesture (e.g. moving the left stick to bottom right). But since that isn't working I suggested to configure an arm switch. I do see that the RC2_TRIM parameter is set to 1000.0 which is odd. Normally it is around 1500.00. When you look at the QGC radio configuration screen and you move the sticks around do they look normal? And when sticks are centered are they all showing that they centered on the graphics? You could try setting RC2_TRIM to 1500.0 and see if that allows you to arm with the gesture. Please make sure you have the propellers removed when doing this testing!