- Joined
- Jun 11, 2019
- Messages
- 614
- Reactions
- 742
- Age
- 64
No tears, but only because of luck and not abbility.
What happened:
Well, I planned another Litchi mission, 689 meters, with a speed of 6 km/h and it would take about 8 minutes. No problem at all.
I lost signal at WP 15, which I expected, since from where I was standing, the MA would fly over the rocks with an altitude of 45 meters and then be out of sight. All well calculated, definetly no people to be there, the climb is pretty steep (35 meters up in less then 120 meters distance...) and everything was fine. But the Ma was gone, 8 minutes, 9, 10... and still no sign or signal, not even a sound. Just as I thought it would have been the final flight, after 17 minutes (!!!) the MA showed up and my tablet told me, it was on RTH with 11% battery left. I took control, landed, packed my things and sat down for a while, regaining my breath.
Back home, I checked the log, but that was fine, only 14:12 "loss of signal", so no clue what had happened. Then I checked the video and I saw what happened: At point 34, I had a wrong altitude. Instead of the planned 50 meters, the MA was ordered to go down to 29,9 meters and it caught itself right here in this deadly corner:
And there it stayed for almost 14 minutes, wanting to go down but not being able to, hindered by the sensors to escape since the concrete of the fortret was to close. Then, as my batterylevel got to 30%, RTH kicked in, lifting the drone to 50 meters and returning it after 17 minutes and 12 seconds.
What did I learn? Well, before I leave home on the next Litchi-mission, I will doublecheck all the altitudes and speeds.
What happened:
Well, I planned another Litchi mission, 689 meters, with a speed of 6 km/h and it would take about 8 minutes. No problem at all.
I lost signal at WP 15, which I expected, since from where I was standing, the MA would fly over the rocks with an altitude of 45 meters and then be out of sight. All well calculated, definetly no people to be there, the climb is pretty steep (35 meters up in less then 120 meters distance...) and everything was fine. But the Ma was gone, 8 minutes, 9, 10... and still no sign or signal, not even a sound. Just as I thought it would have been the final flight, after 17 minutes (!!!) the MA showed up and my tablet told me, it was on RTH with 11% battery left. I took control, landed, packed my things and sat down for a while, regaining my breath.
Back home, I checked the log, but that was fine, only 14:12 "loss of signal", so no clue what had happened. Then I checked the video and I saw what happened: At point 34, I had a wrong altitude. Instead of the planned 50 meters, the MA was ordered to go down to 29,9 meters and it caught itself right here in this deadly corner:
And there it stayed for almost 14 minutes, wanting to go down but not being able to, hindered by the sensors to escape since the concrete of the fortret was to close. Then, as my batterylevel got to 30%, RTH kicked in, lifting the drone to 50 meters and returning it after 17 minutes and 12 seconds.
What did I learn? Well, before I leave home on the next Litchi-mission, I will doublecheck all the altitudes and speeds.
Last edited:
