I searched for others who may have experienced this and the posts I saw either did not match exactly or there was no resolution so I will give this a go with hopefully more detail than what I've seen out there...
I was running this Litchi mission: Mission Hub - Litchi
I crashed early in this mission last week so I added a hundred feet to all waypoints. Well above the trees. I raised up to a point above the first waypoint, switched to F mode and loaded the mission. I made sure there were no spurious waypoints added and then hit go. It started flying. I had good video and data. The somewhere along the route (in the area of WPs 4,5,6 I think) the Litchi voice said "mission completed." Huh? But the distance away from me was still increasing. I was worried about a fly away, so I toggled P2 multiple times. The controller started beeping but it did not initiate RTH. I believe because I did not switch P1 back to P mode so the bird ignored it and stayed in waypoint mode. Then I got the disconnected status on the litchi app. I ran through the house to the porch on the other side to see if I could see or hear it. And then I heard it and it appeared overhead and headed toward the other side of the house where the home point was. It said elevation at 14ft which worried me but now I have to believe it was telling me 14 ft above the first waypoint and not the takeoff point. I ran to through the house again and it landed perfectly at the home point by itself.
When I looked at the healthydrones log ( HealthyDrones.com - Innovative flight data analysis that matters ), what appears to have happened is that it continued to fly normally along the route even though it said mission complete. But then it, at some point did initiate RTH. The CSV shows it switching into go home mode but I believe it is being reported at the wrong location. It is being reported as switching into Go Home when it was basically already home. I'm thinking that when I was traversing through my house there was no connection and it wasn't able to report that status till I got out onto the deck. My theory was also that it had switched to RTH after I was inside the house and it lost signal. But then again Litchi is not supposed to do that right? It's supposed to keep flying the mission (unless I switched P1 at some point back to S and I'm not recalling that in my panic
. And the app was reporting disconnected before I went through the house. And I think it kept flying. I believe D,E,F data loss occurred while I was transiting through the house the first time possible. And G was when I was coming back through to the front.
Thoughts? Why would is report "mission completed" so early in the mission, yet keep flying the mission. Until it made the sharp left to come back home, it was right where it should have been. And I am pretty sure that it did not start RTH when I toggled S2. Because it seemed to take a lot longer to some home than it should have.
Bill
Edit: looked at the video. It flew further than those lines indicate. I guess to be expected since healthy drones data comes from the app on the iPhone which lost connection. Still don't know why it reported mission completed but was on course and still flying.
I was running this Litchi mission: Mission Hub - Litchi
I crashed early in this mission last week so I added a hundred feet to all waypoints. Well above the trees. I raised up to a point above the first waypoint, switched to F mode and loaded the mission. I made sure there were no spurious waypoints added and then hit go. It started flying. I had good video and data. The somewhere along the route (in the area of WPs 4,5,6 I think) the Litchi voice said "mission completed." Huh? But the distance away from me was still increasing. I was worried about a fly away, so I toggled P2 multiple times. The controller started beeping but it did not initiate RTH. I believe because I did not switch P1 back to P mode so the bird ignored it and stayed in waypoint mode. Then I got the disconnected status on the litchi app. I ran through the house to the porch on the other side to see if I could see or hear it. And then I heard it and it appeared overhead and headed toward the other side of the house where the home point was. It said elevation at 14ft which worried me but now I have to believe it was telling me 14 ft above the first waypoint and not the takeoff point. I ran to through the house again and it landed perfectly at the home point by itself.
When I looked at the healthydrones log ( HealthyDrones.com - Innovative flight data analysis that matters ), what appears to have happened is that it continued to fly normally along the route even though it said mission complete. But then it, at some point did initiate RTH. The CSV shows it switching into go home mode but I believe it is being reported at the wrong location. It is being reported as switching into Go Home when it was basically already home. I'm thinking that when I was traversing through my house there was no connection and it wasn't able to report that status till I got out onto the deck. My theory was also that it had switched to RTH after I was inside the house and it lost signal. But then again Litchi is not supposed to do that right? It's supposed to keep flying the mission (unless I switched P1 at some point back to S and I'm not recalling that in my panic
. And the app was reporting disconnected before I went through the house. And I think it kept flying. I believe D,E,F data loss occurred while I was transiting through the house the first time possible. And G was when I was coming back through to the front.Thoughts? Why would is report "mission completed" so early in the mission, yet keep flying the mission. Until it made the sharp left to come back home, it was right where it should have been. And I am pretty sure that it did not start RTH when I toggled S2. Because it seemed to take a lot longer to some home than it should have.
Bill
Edit: looked at the video. It flew further than those lines indicate. I guess to be expected since healthy drones data comes from the app on the iPhone which lost connection. Still don't know why it reported mission completed but was on course and still flying.
Last edited:
. I should have followed the advice I've seen here: start with waypoint altitudes much higher than you think you need. You can always finetune them downwards on subsequent missions. I added a hundred feet to my crashed mission altitudes and reflew the mission. Except for the problem stated above, it ran fine the next time I tried. Turns out it was a good height for my project anyhow So I am going to leave it that way and rerun it when I get better lighting for video.
