I am having and issue of the "e" version with DJI Mini 3 crashing, or when not crashing it can't find the Mini 3. I close the DJI Fly app before starting the "e" version of Map Pilot Pro.
The "b" version when used with the DJI Air 2s work perfectly.
I have downloaded the "e" version a couple of times with the same result. The Mini 3 connects and works perfectly with the DJI Fly app.
My Android device is the Tripltek 8"
Please sign in to leave a comment.
When is the app crashing? Right when it starts up or when the aircraft tries to connect? Please be very specific.
Version are you using? What version of android are you using?
How many gigabytes of RAM does your device have?
Other drone related apps are fully closed.
Sometimes the app crashes when starting Map Pilot Pro up and sometimes when aircraft tries to connect. I am using Map Pilot Pro 1.9.1e. My Tripltek 8" uses Android 10 and has 8GB. No other apps are active.
Of interest is that the 1.9.1b used with my DJI Air 2s works perfectly.
The last version of the "e" app worked well with my Mini 3.
Do you have anything in the File Manager screen?
Is this operating from a fresh installation or do you have files imported or Mission Plans synced?
The previous version is available if you need it. I am sure you can figure out how to modify the URL to get 1.9.0 instead of 1.9.1.
What firmware version are you using? Remote and aircraft.
This is likely and issue with having both version of Map Pilot Pro on your device. Delete all versions of Map Pilot Pro from your device. Then install the 'e' variant and try to connect to the Mini 3.
I updated the Map Pilot Pro 2.0.0 for both the "b" and "e" versions.
Everything now seems to work properly. The "b" version works with my DJI Air 2s and the "e" version works with my DJI Mini 3.
Zane, somehow you really need to combine both the "b" and "e" together. Seeing two of the same icons on the tablet is somewhat confusing. Then being able to fly the same mission with either the Air 2s, Mini 3, or any other drone simply by selecting the drone settings would be nice.
That is good to hear. We suspect the issue is related to the wrong app being used for the wrong aircraft.
We will be changing the icon on the 'e' variant in a future release.
It is actually impossible for us to build the version 4 of the DJI SDK (Air 2S) into the same app as version 5 of the DJI SDK (Mini 3). We aren't keeping them separate for fun... I doubt DJI is going to make the changes that are needed to build them into the same apps just to enable running all their devices from one app. That is probably why they have so many different apps.
A new problem popped up. Everything begins to look good when trying to use my DJI Mini 3 for a saved mission. The app finds the drone, the app walks me through all the choices and warnings. The mission uploads to the drone. However, when I click fly nothing happens. The drone and controller have the latest firmware updates. I am using the "e" 2.0.0 app. Everything was tried a few times with the same result, the drone wouldn't takeoff and start the mission.
Using the DJI Fly app everything the drone works as it should
I sure have been wasting a lot of time trying to get the "e" version to work properly with my DJI Mini 3.
I use the Android Tripltek 8 Pro tablet (Android 10, 8GB ram)
Is anyone else reporting this problem?
Do you still have both apps on your device? Have you tried deleting the 'b' variant so you only have the enterprise version?
Is it a saved mission? If so, please email the .mme mission file to mapping@dronesmadeeasy.com
I have both the "b" and "e" version of the Map Pilor Pro. You never answered my question if others are have this issue. I will not delete the "b" version that works.
I think I am just going back to my Autel Explorer app Missions and not screw around with Map Pilot Pro apps that don't work. Going back to the Map Pilot Pro free version soon.
This is just wasting too much of my time.
Regards,
Richard
Yes, other people have had issues when both apps are installed (you previously, and now, for example). This is why we were asking about it. We are just trying to see if it works for you with one installed. Removing variables is a common debugging practice. There is nothing damaging with uninstalling the app as it can be installed again.
Just trying to help... It could also be something specific to your saved mission if that is the issue. If you email the mission file to us we could rule that out as being the issue.
