Drone crashed | M3T | MSDK 5.8
Completed
Hi, drone crashed for one of our customers.
I would like to share the info of that mission with you, and the HMS status.
In the photo above, the green route represents the given mission route (WPML) and the red route represents the flight route - until RC signal is lost.
Before and during the flight, the HMS showed this:
Sensor system error (0x16010007). Land promptly warningLevel=WARNING
Sensor system error (0x16010010). Restart aircraft warningLevel=WARNING
Yet, the mission was started with no issue and no interrupt occurred.
This is urgent, we can't allow our customers to fly and risk their drones.
Any idea what happened?
-
Greetings! The information provided may not be sufficient to explain the aircraft's flight trajectory. Do you have access to the user's waypoint mission file? Can this file reliably reproduce the issue? Sensor errors can indeed affect the aircraft's performance. If the issue cannot be reliably reproduced with the user's mission file, I recommend contacting support@dji.com to request an analysis of this incident. -
If you have confirmed that WPML is not the issue and you can use this information to successfully start the waypoint mission, I suggest reaching out to support@dji.com and analyzing the issue from an aircraft execution perspective. If your code or waypoint file is causing the execution issue, it is likely to be reproducible. DeviceHealthManager continuously pushes health information of the device. When you encounter sensor anomalies, you will receive the message "Sensor system error." For IMU and compass, the SDK can monitor their status. IMU status can be monitored using FlightControllerKey.KeyIMUStatus, and compass anomalies can be checked using FlightControllerKey.KeyCompassHasError.
Please sign in to leave a comment.
Comments
6 comments