Starling drone shut down mid flight
-
I attempted to connect to the drone, but initially, the connection failed. After some time, I was able to establish the connection. While flying the Starling drone in offboard mode, it suddenly shut down mid-flight and fell to the ground. Following the incident, I was unable to connect to the drone using ADB or Wi-Fi for some time. What could be the reason for this, and what can I do to solve this issue?
-
@Shivam-Sehgal , are you able to ADB into VOXL2 and download the PX4 log from the flight?
Also, what SDK version were you using?
-
@Alex-Kushleyev , I am unable to ADB into VOXL2 today but I did download the flight controller log file after I was able to log in again that day from QGC.
https://review.px4.io/plot_app?log=81e3f3cc-1cf2-419a-8202-073a9dd46c3e link to flight review for the log file. I don't remember the sdk version.
-
@Alex-Kushleyev My Voxl SDK version is 1.1.2.
------------------------------------------------------------------------------- system-image: 1.7.1-M0054-14.1a-perf-nightly-20231025 kernel: #1 SMP PREEMPT Thu Oct 26 03:25:38 UTC 2023 4.19.125 -------------------------------------------------------------------------------- hw version: M0054 -------------------------------------------------------------------------------- voxl-suite: 1.1.2 -------------------------------------------------------------------------------- Packages: Repo: http://voxl-packages.modalai.com/ ./dists/qrb5165/sdk-1.1/binary-arm64/ Last Updated: 2024-05-07 02:01:12 List: libmodal-cv 0.4.0 libmodal-exposure 0.1.0 libmodal-journal 0.2.2 libmodal-json 0.4.3 libmodal-pipe 2.9.2 libqrb5165-io 0.4.2 libvoxl-cci-direct 0.2.1 libvoxl-cutils 0.1.1 mv-voxl 0.1-r0 qrb5165-bind 0.1-r0 qrb5165-dfs-server 0.2.0 qrb5165-imu-server 1.0.1 qrb5165-rangefinder-server 0.1.1 qrb5165-slpi-test-sig 01-r0 qrb5165-system-tweaks 0.2.3 qrb5165-tflite 2.8.0-2 voxl-bind-spektrum 0.1.0 voxl-camera-calibration 0.5.3 voxl-camera-server 1.8.9.1 voxl-configurator 0.4.8 voxl-cpu-monitor 0.4.7 voxl-docker-support 1.3.0 voxl-elrs 0.1.3 voxl-esc 1.3.7 voxl-feature-tracker 0.3.2 voxl-flow-server 0.3.3 voxl-gphoto2-server 0.0.10 voxl-jpeg-turbo 2.1.3-5 voxl-lepton-server 1.2.0 voxl-libgphoto2 0.0.4 voxl-libuvc 1.0.7 voxl-logger 0.3.5 voxl-mavcam-manager 0.5.3 voxl-mavlink 0.1.1 voxl-mavlink-server 1.3.2 voxl-microdds-agent 2.4.1-0 voxl-modem 1.0.8 voxl-mongoose 7.7.0-1 voxl-mpa-to-ros 0.3.7 voxl-mpa-to-ros2 0.0.2 voxl-mpa-tools 1.1.3 voxl-neopixel-manager 0.0.3 voxl-opencv 4.5.5-2 voxl-portal 0.6.3 voxl-px4 1.14.0-2.0.63 voxl-px4-imu-server 0.1.2 voxl-px4-params 0.3.3 voxl-qvio-server 1.0.0 voxl-remote-id 0.0.9 voxl-ros2-foxy 0.0.1 voxl-streamer 0.7.4 voxl-suite 1.1.2 voxl-tag-detector 0.0.4 voxl-tflite-server 0.3.2 voxl-utils 1.3.3 voxl-uvc-server 0.1.6 voxl-vision-hub 1.7.3 voxl2-system-image 1.7.1-r0 voxl2-wlan 1.0-r0 --------------------------------------------------------------------------------
-
@Shivam-Sehgal , I have reviewed the log and unfortunately do not see any issues. The log terminates prematurely (before the crash), which may suggest that the PX4 process crashed (as opposed to a sensor issue or ESC issue, causing motor to stop, for example). But this is just a guess.
SDK 1.1.2 is quite old, we recommend using latest SDK if possible, since we always make improvements and fixes.
My recommendation is to get the vehicle back up and running and try to migrate to SDK 1.3.
-
@Alex-Kushleyev i can update the system but I am unable to connect to voxl 2. How can I update the system?
-
@Shivam-Sehgal , quick question.. So after the crash, were you able to connect to VOXL2 (how? ADB or wifi) to get the log from it? And now it no longer connects using ADB?
Here is unbricking procedure for VOX2 https://docs.modalai.com/voxl2-unbricking/, however that is typically done when a software update fails or the file system.
Can you please clarify whether you were able to use VOXL2 between the time after crash and now?
-
@Alex-Kushleyev Yes I was able to connect to drone both via wifi and adb that day, then next day I wasn't able to do so.
(Some Observation if it helps)
Also, I have 3 other starling drone in all of them there are four blue lights on the ESC that constantly flash.
In the one that does not connect there is no flashing. -
@Alex-Kushleyev should I follow the unbricking process?
-
@Shivam-Sehgal , Yes, you should try it, however i am not sure whether the recovery attempt will be successful. Typically unbricking is required when something goes wrong during SDK update or something like that, when the system is left in incomplete state. In your case, the drone was flying and stopped responding after a crash. The fact that it shut off during flight could mean there was a pre-existing issue (before the crash) which may be causing the board not to boot now. However, it is worth to try the unbricking and if does not work, please contact our RMA department, they will help you out.
Alex