Official comment

You need to enter the following numbers for the P4P to work:
CAMERA_FOCAL_LENGTH = 8.8 mm
PIXEL_PITCH = 2.41228 micron
SENSOR_Y_PIXELS = 3648
SENSOR_X_PIXELS = 5472
P4Pro is not listed in Point estimator. I could enter focal length = 8.8mm but sensor size is not correct, I cannot change with to 1" = 25mm
Image size 4:3 20 MP is automatically set before starting the mission? Because my default setting is 3:2. Or should I change it from GO4?
What do I do?
You need to enter the following numbers for the P4P to work:
CAMERA_FOCAL_LENGTH = 8.8 mm
PIXEL_PITCH = 2.41228 micron
SENSOR_Y_PIXELS = 3648
SENSOR_X_PIXELS = 5472
Please sign in to leave a comment.
Ok, thank you
Image size 4:3 20 MP is automatically set before starting the mission? Because my default setting is 3:2. Or should I change it from GO4?
And what about in GO4?
Do all settings auto set when the quad is on?
This assumes the 3:2 to use the full sensor resolution.
I have to map a large roof (10000 sq m)
It is 13m height.
I simulated flying 20m over the ground but it will be 20m over the roof, so 33m above the ground.
How can I keep 20m grid but flying at 33m ?
Thanks
Here is the reply that was sent to your original support request. Please make sure our email address is whitelisted in your custom domain email service.
Hi Daniel,
For detailed rough inspection use 80/80 overlap settings. Also select 14m as your ground offset to match your target height. For point and missions estimates it is best to set up and simulate within Map Pilot. The P4P can be selected in the settings section of Map Pilot's main page. Make sure P4P is chosen prior to setting up mission estimates or it will clear out unsaved missions.
Thanks,
Ryan
Very good! Thanks a lot!
I just viewed my inbox a there are 4 from you but notices from these posts, not that you mention.
Anyway all is here, Thanks again
Is this okay despite the sensor size is not correct?
Those are the proper dimensions.
I cannot set the offset to +14m because only a half of 20m is allowed
Which do I trust?
I am having some big differences between estimator and iPad mission app.
I don't know why. Maybe shooting/writting speed (U3 card)
No auto-save? After writting previous posts I returned to the app (didn't close it) and the session vanished (iOS)
Map Pilot is the most accurate way to estimate the number of images that will be taken because it knows more about the hardware than you enter in the Point Estimator. The Point Estimator was really only ever intended to be used for big DSLR-type cameras and is a good learning tool.
There is no autosave. If the app is closed the current mission will go away if it wasn't already started as a flight.
Don't cut your survey area that close. Google Maps, Apple Maps and Mapbox don't have published specs on absolute accuracy since there are a million factors that come into play with it. This is a good example of that.
The Ground Offset can only be set to 50% of the flight altitude setting.
This app is driving me crazy.
I saved a mission and closed the app. Then opened and loaded the mission.
Far away of what I saved: 8 points instead of 4 I used to create the area. Also twisted grid ( I want the path lines parallel to the area limits.)
This is loaded mission. Compare it with my previous image. Thanks.
I see three points a flight simulation I made some missions before (all deleted)
Something cached?
Today I was in the field. Very bad experience, very disappointed.
I’ve been using the app time to time with my P3P without major issues.
I understand this a particulary mission: relative low altitude and 80% overlaps as suggested: many photos in short time.
Finally I gave up and left the “diagonal” path instead of parallel lines to the roof borders.
The mission started okay flying at less than 3 m/s and taking photos every 2 or 3 secs.
In the middle of the mission (hundred photos) several warnings about saving images problem.
I am using an iPad mini 2, no other app open, Samsung PRO 64GB U3 almost empty.
Then I started to see shot points too far apart and others to close (I had set U3 cards).
After a while the app crashed/closed. P4P still fliying the path according to uploaded mission and in my desk I realized that P4P ended taking a ride thru the path but not taking photos (if the mission is uploaded why does the quad need the app open? I use other apps that continue all tasks).
To repeat the mission I had to create it again, I didn’t find how to clean all recorded point shots.
Second time happened the same despite I had change card settings from U3 to U1. Also the app crashed.
Going to the first point is fast. Returning to home is very slow (I guess it keeps speed used in the mission) I stopped and returned manually
It sounds like you may have some other issues going on. We would recommend not using Map Pilot until you are certain everything is working properly. If saved missions are not working properly for you please send your log files and flights.plist file to mapping@dronesmadeeasy.com for inspection.
Hi Daniel, re your problem with app crash/close - I've experienced same also with ipad mini 2, the app will 'crash' and show the log screen but aircraft still continue on waypoint path but stop taking photos (in connected mode) as the app isn't responding/connected anymore. Swapping to a more powereful device stopped this particular issue occuring (iPad Air 2). Note you can choose the trash button, then close and re-open mission to start again. I'm still performing some further testing, but currently when P4P in simulator mode, both the v2.45 map pilot ios app and Pix4dcapture both are BOTH stopping at around 16 1/2 minutes for the P4P, don't experience same issue with Inspire 1, so thinking there may also an issue with waypoint missions/DJI SDK, at least on simulator. Should be testing in the field shortly to see if behaviour the same as sim.
For the first time, MME gave me problems yesterday. While doing a mission with a P4P, after a successful one, the Drone went to the starting point, made one line without taking any photos and just took some in the second line. After the communication started to have issues and the Drone stopped and made a controlled landing for itself. Fortunately I was able to open the DJiGO app and get the drone location. Went there and it was hovering in place. However, even with the DJiGo app, it was impossible to control the drone. I don't know if this is a MME problem or a P4P firmware problem but clearly both are not working as reliably as before.
Cheers
The 16 minute issue has been fixed in the most recent firmware update for the for Phantom 4 Pro v01.04.0602.
Hello! for the Mavic Pro Platinum what are the parameters to use it in https://www.mapsmadeeasy.com/point_estimator
Thank you
Eddison
Muchas gracias!