Waypoint limit error

Thanks for the response Ryan,

At first I thought it may be take-off point to mission distance as well, but I loaded an identically sized mission that was on top of the take-off point and got the same error. These missions are only 50ha and 13.5 km. 

These missions were planned with a battery timer limit of 15m. Although I don't see why this should be a limiting factor as MapPilot is meant to be able to handle multi-battery missions and I have planned larger missions with previous versions without issue. How or why does battery timer affect the number of waypoints for a total mission?  I'll try re-planning a mission with a battery time set > than estimated mission time, 

GPS signal is very good at the mission site and >15 satellites all the time. The error was replicated over multiple times/Missions.

The other very annoying behaviour is that when I initiate a RTH mission resume does not resume at the abandonment point and skips the remainder of the leg it was on. It seems to take photos along the way to the next leg (drops grey markers, but I haven't confirmed images were actually taken.

 I have to say at the moment Map Pilot is less useful than it was, it's great to have features like bringing in kmls etc but not at the expense of basic functionality. Currently I would prefer the beta version I was testing back in the day which was rock solid.

OK I've tried re-planning a mission at various battery timer settings including "Battery limited" "15 Minutes" and "18 Minutes". The mission was 50.58ha and 11.39 km Take-off point was at the mission end point. Alt 120m 207 images. 

The same error persists.

It sounds like it should be working fine... Please take some screenshots of what you are trying to layout and the error and email those to mapping@dronesmadeeasy.com so we can try to see what is going on. Also, please save a mission that won't upload and send us the flights.plist file zipped up so we can inspect that too. 

Have you tried to upload the mission to another DJI aircraft or from another iOS device?

The issue with it taking images on the way back to the next waypoint is likely due to the aircraft being landed manually instead of allowing it to land on its own. There is some weirdness in how the mission is ends in this case and it ends up dropping a new abandonment point where ever you take over. This seems to come and go with every release of the DJI SDK.

Hi Ryan/Tudor,

After a long time I've been able to to test this some more and replicate the error with a previously saved mission that used to fly flawlessly. I'm wondering now if it could be a a/c firmware incompatibility with this version.

I've studiously avoided firmware updates because of repeated issues with DJI updates. I've had a reliable aircraft and saw no reason to change.

My Current overall version status is:

Map Pilot- 1.5.0 Build 031916
Aircraft- 1.4.10

RC- 1.4.3
Go - 2.4.3

We can only support the most up to date firmware and Map Pilot versions. Using old stuff will almost certainly lead to compatibility issues.