
Hmmm. That's a new one. It might be something with their remote. Try it while connected to the internet.
Hi, I am recieving the following error on my Mavic 3 Multispectral Enterprise controller.
If I restart the controller and switch back to DJI, it can see the remote location no worries.
I can see in the 'location' settings that MPP had requested (and presumably had access to) location data, as the drone did perform 2 lines of a map but then stopped.
Reinstalling the app has not solved the issue, and I am unable to perform flights with MPP now.
Do you have any insight on this?
Controller version 02.00.0407.
Thanks
Please sign in to leave a comment.
Hmmm. That's a new one. It might be something with their remote. Try it while connected to the internet.
I believe I've tried both with internet enabled and not.
As I switch back to DJI, it can see the location OK.
I've had this on 1.4.4. and 1.4.5
Can I share a flight log or something?
It's available on my records, its the flight started:
May 17, 2023, 11:46 a.m. |
Another example is a flight starting:
April 17, 2023, 9:27 a.m. |
It could be something like an invalid corner radius since the error says "TRAJ_DAMP_DIS". If you are restarting after a battery change and this happens choose the previous corner to start at instead of the abandonment point while the blue verification line is showing. We don't adjust the abandonment point location but there are constraints that could cause issues there.
I'm getting this error alot when trying to fly at 7m. 8m seems OK.
Could this be something to do with the minimum flight heights?
It sounds like this might have something to do with the curvature of the waypoints. You could try switching it to use Straight Corners in the Advanced section of the Settings. Straight Corners don't have any radius associated with them. Please email us with screenshots of the layout that throws the issue. Not the error, the layout. So we can see what is going on with it.
Right!
I've cracked it.
The error seems to come from side overlap settings at these low heights. Here are my findings:
At 8m flight height, no more than 65% side overlap allowed.
At 7m flight height, no more than 60% side overlap allowed.
At 4m flight height, no more than 25% overlap allowed.
I'm going to assume this means that there is a minimum distance programmed between each mapping 'line'.
Is this programmed in on the DJI or the MPP side? Is this something you can alter for the enterprise models like the recent minimum flight speed?
I have been tasked with producing a 65/65 map with a 1mm GSD - correlating to 4m on the M3M. Would be amazing if MPP could do this.
Theres also a 'Memory Card Format' misleading error for forward overlaps, but I think this is mentioned elsewhere in the support pages.
And I can't see any advanced settings on 1.4.5.e, where can I find them please?
Hey any updates to this?
Apparently the Android version doesn't have the advanced settings to force square corners. We will get it into one of the next releases.
There are constraints to any 3 waypoints that dictate how far the first and third one can be from the middle waypoint and the angle which that set can form. You are likely getting down to the level that is just not possible with their constraints.
You can try capturing lower overlap data and trying to use TerrainDrop or something like that instead of photogrammetry too.
I also got this error today. The issue was that the home point I initially set was out of range, and I didn't know it was placed in a new spot. I didn't have any of the below messages pop up, though.
Hi Sean, thanks for the update. how exactly did you resolve it?
Hi Jamie, The only way I really fixed it was by redrawing a new pattern on my map over the one I previously made. So not a true fix. I haven't updated the newest app since the newest one couldn't read my DJI M3M.
Thanks Sean.
Have you noiticed with the M3M that the drone flies at an angle (not straight ahead) during missions? It is offset for me and not following the lines correctly which ruins overlap. I'm about to rent a Mavic 3e to test whether it happens with that or whether my M3M needs to go back to DJI.
On another note, my issues with TRAJ_DAMP_DIS_OUT_OF_RANGE are resolved with 1.4.7.e.
It seems that it is to do with the minimum corner radius, when I select straight corners from advanced options I can push that overlap up as much as required.
Thanks!
Excellent Glad it has been fixed. It seems also the issue of connections should be fixed with 1.4.7.e. Ill be sure to download and try it some time out in the field.