Posts made by sssagara

@Kessie Seconding this. We have a triple tracking Starling 2. Initially, when on SDK 1.3.5, QVIO was barely sufficient for ensure stable flight without drift in conditions that were a bit too bright or dark. We upgraded to SDK 1.4.0 to use OpenVINS and had better luck in our lab, with the quality and features metric as reference that it will have accurate positioning estimates. But as soon as we brought it out to a different test area that is well lit with artificial lighting, it seems like OpenVINS momentarily stalls as soon as the drone is armed (see below pic). Even after letting OpenVINS recover, the height will drift very drastically even when the drone is still on the ground (see below pic). We tried a combination of single, double and triple camera setup. en_vio_always_on doesnt seem to make a difference regardless if its true or false. When we do have to leave the drone on the ground, we manage the temperature by having a dedicated fan pointed at the processor until it is ready to fly.

For now, we have resorted to going back to a single camera QVIO setup

@Alex-Kushleyev Hi Alex! Thanks for your reply! I managed to get a hold of a replacement capacitor and it works now! I used a piece of kapton tape to cover the base of the board to prevent any components from getting snagged in the future. Maybe future iterations of the ESC can include something as a simple covering for it

Hi! After not using my Starling2 for about a week, I noticed that I'm unable to power on the drone. After some troubleshooting, I've narrowed down the problem to a capacitor that seems to have knocked off sometime between my previous successful flight and now (pictures as attached). While I'm waiting for a new ESC to be ordered, can anything be done to it that will allow me to at least do bench testing? Or is the ESC absolutely toasted? The LEDs on the ESCs do not turn on and neither do the motors beep. But it still outputs 1.2V instead of the 5V at the main regulator output

Thanks!