Variations and wandering in a 10 battery mission

I flew a 10 battery mission yesterday, and besides the focus issues, I also had issues on a couple of the flights with following the route. On the first two flights, all went smoothly. (I REALLY like that the Inspire 1 Pro has such smarts about low battery and landing - glad that MP takes advantage of this!) On the third flight, instead of returning to the point of abandonment, it went back over part of the last leg of the previous flight, then at the next turn, it got back on track. That resulted in a noticeable gap in the mission.

It did this again on either the fifth or sixth flight, (I can't remember for sure). then somewhere around the 8th flight, it flew out to the point of abandonment, and then just hovered there. I had to do a return to Home and try again. It then went flying off course, back over ground it had covered previously and did the hover thing again.

Also, on one of the flights, the low battery warning came through and it started returning to home but then decided to start landing where it was, which was maybe 700 meters away! In a forest! I took over control and brought it back, but that was "exciting", and I'm really looking for "boring" when I fly these missions.

I have a gpx file with the route if you are interested in seeing that. It shows the strange behavior pretty clearly.

Thanks,

Mark

Mark D. Fink 11 de abril de 2017 13:18

Comentario oficial

Usually retracing issues are caused by manual takeover of the aircraft at the time of landing and this will cause issues with the waypoints no longer being synchronized. It sounds like that is what is causing this array of sync issues.

It is totally fine to manually take over when landing but as the warning that pops up says, be sure to put the remote back into programmed flight mode before actually landing so the waypoints won't get out of sync.

Zane 11 de abril de 2017 17:33

Iniciar sesión para dejar un comentario.

2 comentarios

I think that is exactly what happened. There were two flights where I had to take manual control. I did remember reading that the drone needed to be in F mode prior to landing. In these cases, I never switched out of F mode, but flew back and landed while still in F mode. I probably would have had better flight control had I switched into P mode for the manual flying, and I'll likely do that in the future, but will always make sure it is back in F mode prior to landing.

With that in mind, I thought of a feature request that might help in this situation, as well as another scenario. If there was a way to zoom in on a route, then press and hold to place a user defined abandonment point, then I would be able to recover from these situations more gracefully.

For example, if the drone decides to land significantly further away from where Home is, and I need to take manual control to land it, I could then press and hold on a spot to make sure it knows to go there and resume the mission, thereby avoiding the potential sync issue you mentioned.

Another use for this manual abandonment point option would be for cases where a segment of a mission has images that are out of focus, or some other issue, but I don't realize that until after getting back to the office and downloading the images. If I could return to the field and place an abandonment point where the issue started, I could then fly that segment again with the same precise placement. Otherwise, I would have to create a new mission covering that area, but I doubt I would be able to match the route of the original and get the precision I'm looking for.

Thanks,

Mark

Mark D. Fink 12 de abril de 2017 12:51 0 votos