Voxl starling crashed all motors stop working mid air
-
My Starlink drone crashed while it was in mid-air, all 4 motors ceased working suddenly. After the crash, I saw qgc was not connected. Has anyone faced this problem? If so can anyone point out the reason and how to solve it? I am assuming it is because the communication failed or the Voxl restarted its services mid-air which led to the crash. If anyone has faced this problem can you please tell me how to sort this out?
-
My Starlink drone crashed while it was in mid-air, all 4 motors ceased working suddenly. After the crash, I saw qgc was not connected. Has anyone faced this problem? If so can anyone point out the reason and how to solve it? I am assuming it is because the communication failed or the Voxl restarted its services mid-air which led to the crash. If anyone has faced this problem can you please tell me how to sort this out?
@Manu-Verma This needs to be debugged. Obviously, that should never happen. The best way to debug this is to provide log information that can be analyzed for clues. If you see this happen and you can extract the log from
dmesg,journalctl -b -u voxl-px4, and the px4 log from/data/px4/logdirectory that will really help to understand what went wrong. -
@Manu-Verma This needs to be debugged. Obviously, that should never happen. The best way to debug this is to provide log information that can be analyzed for clues. If you see this happen and you can extract the log from
dmesg,journalctl -b -u voxl-px4, and the px4 log from/data/px4/logdirectory that will really help to understand what went wrong.@Eric-Katzfey Following is the system_data logs and PX4 logs recorded during last flight.
-
@Eric-Katzfey Following is the system_data logs and PX4 logs recorded during last flight.
@Manu-Verma That log does show that the throttle was pulled all the way down towards the end of the log. Are you sure this is the log from the crash? Did the 4 motors all stop completely or were they still spinning at a lower speed? Were they spinning at all after the vehicle crashed?
-
My Starlink drone crashed while it was in mid-air, all 4 motors ceased working suddenly. After the crash, I saw qgc was not connected. Has anyone faced this problem? If so can anyone point out the reason and how to solve it? I am assuming it is because the communication failed or the Voxl restarted its services mid-air which led to the crash. If anyone has faced this problem can you please tell me how to sort this out?
some useful plots:
Zooming into the Manual Control Inputs,
It looks like the vehicle switched from altitude hold mode to position mode, but then the operator dropped throttle to minimum. Does that sound like something that might have happened?
The commanded and actual ESC commands went to minimum (it looks like around 3000rpm), the vehicle was not able to control attitude and flipped over, then motors were commanded to turn off.
-
some useful plots:
Zooming into the Manual Control Inputs,
It looks like the vehicle switched from altitude hold mode to position mode, but then the operator dropped throttle to minimum. Does that sound like something that might have happened?
The commanded and actual ESC commands went to minimum (it looks like around 3000rpm), the vehicle was not able to control attitude and flipped over, then motors were commanded to turn off.
@Alex-Kushleyev How can I send you the system data logs from Voxl not the px4 logs, since I can't attach any file here, can you tell by checking the system data logs? And how can I share that file here? Also, I gave the throttle to zero after it crashed.
-
@Manu-Verma That log does show that the throttle was pulled all the way down towards the end of the log. Are you sure this is the log from the crash? Did the 4 motors all stop completely or were they still spinning at a lower speed? Were they spinning at all after the vehicle crashed?
@Eric-Katzfey All 4 motors ceased at the same time it was not spinning at a lower speed after the crash.
-
some useful plots:
Zooming into the Manual Control Inputs,
It looks like the vehicle switched from altitude hold mode to position mode, but then the operator dropped throttle to minimum. Does that sound like something that might have happened?
The commanded and actual ESC commands went to minimum (it looks like around 3000rpm), the vehicle was not able to control attitude and flipped over, then motors were commanded to turn off.
@Alex-Kushleyev Just figured out why the motors were ceasing mid-air, it was the power module wire that was loose, so whenever I took off, the board was rebooting, (coz of the loose connection to the power module.)
-
@Alex-Kushleyev Just figured out why the motors were ceasing mid-air, it was the power module wire that was loose, so whenever I took off, the board was rebooting, (coz of the loose connection to the power module.)
@Manu-Verma , that is great that you figured it out!
Can you please help us understand where exactly the loose connection was? Could you please take a picture and mark the location of the issue? That would be really appreciated!
Alex
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login