Matrice Stalling During Flight

Should I send you the logs?  This is strange..

The logs won't really help since they don't have any information regarding the reason it might be stopping.

If the upload of the waypoints worked properly (and you shouldn't even be able to take of if it hadn't) the aircraft is in control of how and where it is flying.

Is it only happening in corners? Have you tried slowing down to see if it still does it?

We were flying slow at 4.5 m/s. This happened multiple times where it would just get stuck for no reason. We ended up manually mapping because of it. The other issue is that the craft is not obeying max speed from take off to waypoint 1. Is there any way we can see hdop in telemetry?

As of version 1.4.0 the aircraft goes from the point overhead to the start of the mapping flight path and back from the end at 15 m/s to save battery time. We had a lot of complaints that a lot of time was being wasted going slow on those legs of the trip. The max speed only applies to the mapping.

We will not likely expose HDOP since it isn't available in the SDK.

Will there be a way to adjust that initial speed?  It would be nice to have 2 options normal and fast because when it's cold outside you don't want the craft going max speed to waypoint 1 until the battery and motors are warmed up. 

The time to ascend to the cruising altitude is usually sufficient for this but you shouldn't be taking off until your aircraft is fully ready. We always recommend a test flight for warm up and system check out.

The acceleration to the waypoint flight limited full speed of 15 m/s is pretty slow as is the max speed so there really shouldn't be any issues. If you are concerned about battery and motor temps it is best to handle that outside of Map Pilot.

15 m/s is max forward speed. If I use DJI app to warm up the machine hovering then I can't switch back to map pilot without landing and restarting. My concern isn't the ascending speed but the speed to waypoint 1 in cold weather. 

I use a phantom 3 pro and have the same issue.  after the last update the drone will just hover in place at the start of the mission, when turning, or returning to a abandonment point.  the only error I receive is flight mission speed could not be set due to time out.  It is very frustrating losing all of your progress on a mission when you are 3/4 of the way done.

any help would be great.

Will

The load on the motors and battery is higher on ascent that in is during forward motion. There is very little difference in battery load between moving forward at 5 m/s and 15 m/s. Rapid acceleration and lots of starting or stopping are the nasty parts. 

The warmup hovering could occur a few feet off the ground so you don't waste too much time.

Map Pilot will not take off in the presence of a battery temperature warning.

It's a serious issue hopefully it gets fixed very quickly. We have to manually fly half the missions right now. 

As far as I can tell it's an issue with cached maps. 

William: Thanks for that information. That actually helps us narrow it down. Any time you see an error code for something like this screenshot it and send it to us.

We are really hoping this is not a new SDK issue. We haven't touched the flight control stuff from before. We have a version with a few other fixes coming up but since we don't actually control the flight there is little we can do about this.

Since we are not setting the mission speed at any time other than on the way to a flights starting point we are really surprised to hear it is causing issues so late in the flight...

There will be a setting in the next version to disable that feature.

How soon until the next release?

I can confirm our issue is specific to maps cached using a different basemap that was available on the previous version.

We hope to submit in the next couple of days if we don't come across any other issues.

There is no difference in the flight planning or programming in the cached or new flight plan creation.

Are you saying that it only stops and hovers when using a cached map that was taken with the default Mapbox credentials?

I look forward to the update. I had missions cached using the last version on map pilot. The basemap was not the default mapbox basemap. There were 3 options 2 of which were satalite view. I picked the second satalite view which seems to be no longer available. The missions were cached on a different basemap which seems to be the cause of the issue. Flight planning on the current basemap with the newest version of map pilot is fine as long as there isn't a cached map. 

Does that make sense?