Open MichaelPenner opened 1 month ago
I don't have experience with the latest Betaflight version, but my suggestion is pay attention to the error codes showing by the simple_UI. Does your FC have the blackbox enabled? The data saved by the blackbox may give you some good hints (https://github.com/betaflight/blackbox-log-viewer). Another suggestion is use iNAV instead of Betaflight because Betaflight was not designed for autonomous drones, afaik.
Hi, I'm working on my autonomous drone project. For my setup, I used some spare parts from my Tyro 99 FPV drone. Specifically, I'm using the Matek F405STD flight controller (FC) and the EFM8BB21F16G 4-in-1 30A ESC. I'm also using the standard Tyro 99 2206 2150KV brushless motors. The FC is running the new Betaflight 4.5 version, and I believe all the settings are correct. The port is set to MSP, and the receiver is also configured on MSP. The FC is connected to the Raspberry Pi (which will handle the autonomous steering) via a USB cable, with ttyACM0 on the Raspberry Pi and UART0 (micro USB) on the FC.
I've tried several Multiwii libraries and protocols, but none have worked correctly so far. Telemetry data is functioning fine, so the connection and port settings should be correct. When using the simple_GUI script from this library, the interface loads properly, and arming seems to work, but the motors don't spin up. However, when I use the Betaflight configurator, the motors spin up, so it doesn't seem to be a wiring issue.
I'd appreciate any ideas or suggestions!