Post

10 followers Follow
1
Avatar

Mavic 2 support

Wondering if you have a timeline for Mavic 2 Pro support?

Bill Stangel

Please sign in to leave a comment.

30 comments

0
Avatar

Can I assume the Mavic 2 Zoom will be supported as well?

 

Thanks

Toney Lowery 0 votes
Comment actions Permalink
0
Avatar

Any update/timeframe as to when the Mavic 2 Pro will be supported?

David 0 votes
Comment actions Permalink
0
Avatar

Any updates on the release of the Mavic 2 Pro support date?

Joey Busalacchi 0 votes
Comment actions Permalink
0
Avatar

There are still some issues with the DJI SDK we are trying to work through before it will be made available. All of the new versions of the Mavic 2 series will be supported.

 

Zane 0 votes
Comment actions Permalink
0
Avatar

For planning purposes:

Mavic 2 Zoom at 24mm - 60 meters, 2.1 cm/px, Max flight speed 6.2 m/s

Mavic 2 Zoom at 36mm - 60 meters, 1.5 cm/px, Max flight speed 4.4 m/s

Mavic 2 Zoom at 48mm - 60 meters, 1.1 cm/px, Max flight speed 2.2 m/s

 

Mavic 2 Pro - 60 meters, 1.4 cm/px, Max flight speed 5.1 m/s

 

Phantom 4 Pro - 60 meters, 1.6 cm/px, Max flight speed 6.0 m/s

Mavic Pro at 24mm - 60 meters, 2.0 cm/px, Max flight speed 5.8 m/s

Zane 0 votes
Comment actions Permalink
0
Avatar

Support for the Mavic 2 Zoom and Mavic 2 Pro has been released in version 2.9.2.

Zane 0 votes
Comment actions Permalink
0
Avatar

I just conducted two mapping missions with my Mavic 2 Pro. The first mission lost several photos. Signal strength was reported as 100% the entire flight, however the log file shows several data drop outs. The second mission I few using connectionless mode. That seemed to work much better.

My guess, the M2P's SDR radios aren't prime time, especially if you need prefect connectivity to snap the shutter. I was at most 400 meters away, line of sight, with no obstructions. Drone was flying at 100 meters.

Steven Wallace 0 votes
Comment actions Permalink
0
Avatar

I can verify that I had the same issues as Steven Wallace.  Random photo collection unless in connectionless mode.  I did two missions at 400ft. with clear view of Mavic 2 Pro the entire flight.

Joey Busalacchi 0 votes
Comment actions Permalink
0
Avatar

You guys really got out there early! The latest version has only been out for a few hours.

It almost always seems like their are radio signal issues with early use of any new aircraft. Keep an eye out for firmware updates. This isn't something we can fix but will keep an eye on it.

 

Zane 0 votes
Comment actions Permalink
0
Avatar

Also just noticed the altidtude of the imagery collected during the same mission is wildly variable. 

I would be happy to share any images if they can help this diagnosis in any way.

Joey Busalacchi 0 votes
Comment actions Permalink
0
Avatar

That doesn't sound good... Please email the affected log file or post the images to Maps Made Easy for processing and let us know which job it is so we can see what is going on.

 

Zane 0 votes
Comment actions Permalink
0
Avatar

The M2P has a bug WRT GPS altitude. It's stuck at "115544442 m Above Sea Level". Depending on your photogrammetry tool, you have to correct based on relative altitude.

Steven Wallace 0 votes
Comment actions Permalink
0
Avatar

@Zane

I have uploaded 73 images below are the project details.  Please let me know if you need anything else.

Mavic 2 Pro Test

Mavic 2 Pro Test, Tallahasse
 
Sept. 23, 2018, 7:59 a.m. Sept. 23, 2018, 5:25 p.m. 73 292
Joey Busalacchi 0 votes
Comment actions Permalink
0
Avatar

FYI, the M2P appears to have a more stable barometer (compared to the P4P). It also appears to have more consistent GPS location information in the images (again, compared to the P4P). My guess is that there's less delay, or more consistent delay, between recording the GPS location and capturing the photo, especially in connectionless mode.

Ssw 0 votes
Comment actions Permalink
0
Avatar

FYI, my missing photos correlated with the following:

Photo Error: Error Domain=DJISDKCameraErrorDomain Code=-3002 "Camera is busy or the command is not supported in the camera's current state(code:-3002)" UserInfo={NSLocalizedDescription=Camera is busy or the command is not supported in the camera's current state(code:-3002)}

The drone was flying pretty fast 9.9m/s. I was using a SanDisk Extreme Pro V30 SD card.

Ssw 0 votes
Comment actions Permalink
0
Avatar

A "Camera Busy" error means you have the SD card write speed set to be too fast in the Settings. The Mavic 2 Pro may be slower to write frames than the P4P so you may need to turn it down. Smaller/Cheaper aircraft usually means less capable hardware so it wouldn't be surprising that it can't handle fast framing like 2 sec/image or even 2.5 sec/image. Try setting it to 3 sec/image to see if that error goes away.

Zane 0 votes
Comment actions Permalink
0
Avatar

We are seeing the weird GPS altitude tags too. We have made the required adjustments in Maps Made Easy to deal use the relative elevation tags if a ground reference image is supplied (just like with any other DJI camera).

 

Zane 0 votes
Comment actions Permalink
0
Avatar

@Zane

Have all of these issues been addressed in a new release?  What version?

 

Thanks

Joey Busalacchi 0 votes
Comment actions Permalink
0
Avatar

Mavic 2 Pro and Zoom support has been officially added but there are still firmware issues that are affecting the accuracy of the exif geotags. This is not something we can fix. Hopefully DJI will address it in a firmware update soon.

Zane 0 votes
Comment actions Permalink
0
Avatar

Hello Zane,

Shall I assume that you have empirically tested the DJI Mavic 2 pro and DJI Mavic 2 zoom to derive the statements:

Mavic 2 Zoom at 24mm - 60 meters, 2.1 cm/px, Max flight speed 6.2 m/s

Mavic 2 Zoom at 36mm - 60 meters, 1.5 cm/px, Max flight speed 4.4 m/s

Mavic 2 Zoom at 48mm - 60 meters, 1.1 cm/px, Max flight speed 2.2 m/s

Mavic 2 Pro - 60 meters, 1.4 cm/px, Max flight speed 5.1 m/s

If you did test the drones, did you also tested how repeatable is the Mavic 2 zoom focal length is?

The reason I'm asking this question is because I event though the camera focal length has been specified through Map Pilot app I fear small readjustments of the focal length each time the battery of the Mavic 2 zoom is swapped for a fresh one leading to photogrammetric flights with slightly different focal lengths on consecutive batteries occurring each time the drone is powered up after each battery change.

By the way, do you have input from DJI support team on when they will fix the weird altitudes tags on the pictures?

Thanks

Isaac

Isaac H. E. 0 votes
Comment actions Permalink
0
Avatar

Isaac: These numbers are calculated numbers based on focal lengths, overlaps and altitudes. The focal lengths should be pretty good since that is handled directly by the DJI SDK and the internals of the camera. We don't have enough good data on this yet due to the tagging issues. 

Feel free to reach out to DJI to let them know this firmware issue is causing large issues for you. They know about it and I would hope an update would be coming out soon.

Zane 0 votes
Comment actions Permalink
0
Avatar

Helo Zane,

I started a forum thread with DJI.

Thanks

Isaac

Isaac H. E. 0 votes
Comment actions Permalink
0
Avatar

Hi Zane,

Someone in DJI forum said: "Fixed in FW v01.00.01.00" (release date from yesterday) but if I check the changelog at https://forum.dji.com/thread-169070-1-1.html doesnt say anything on image tags.

I don't have a Mavic 2 to test this out, has really been ironed?

Thanks

Isaac

Isaac H. E. 0 votes
Comment actions Permalink
0
Avatar

There have been image tag issues before and they didn't spell it out then either... We will test it and verify soon.

Zane 0 votes
Comment actions Permalink
0
Avatar

We ran a couple of test jobs and are not seeing that the latest firmware has fixed things. They changed, but they are not fixed.

Zane 0 votes
Comment actions Permalink
0
Avatar

Hello Zane,

Any chance to get a picture out of your testing so that I can go back to DJI?

Again, I don't (yet) have a Mavic 2 drone to take my own pictures.

Thanks

Isaac

Isaac H. E. 0 votes
Comment actions Permalink
0
Avatar

Here is what we have figured out on the Mavic Air and Mavic 2 tags so far:

 
Changes were made to a previously functioning Mavic Air firmware that broke things. We think this happened around when the Mavic 2 was released. 
 
The Mavic Air has switched from a 2 byte number format for the tag data to a 4 byte format which is why it is messing up a ton of viewers and software. The EXIF standard document says it is 2 bytes. We realize why they did it, RTK data requires the ability to report higher levels of precision, but it is dumb how they did it. They went from providing 7 decimal points (inches of precision) to providing around 15, which equates to providing micrometers of precision in the air. Not useful or realistic. Maybe in 10 more years of technological advances but then the EXIF standard and all the viewers would likely be updated to reflect this. 
 
We suspect that the rest of the DJI cameras and aircraft will eventually use the same formats. 
 
Then, in addition to the issue on the Air, on the Mavic 2 they decided to report the relative altitude in the GPS tags again and then not report the GPS derived altitude at all in the XMP section. Currently, a value of 1.2 meters is reported in all images in the Absolute Altitude number in the XMP tags. For some reason it is reporting a negative number for the Relative Altitude number in the XMP at takeoff. This value is 0 (or close to it) on all other aircraft. 
 
The short story is that we have accommodated the new format in Maps Made Easy to the extent that we can. For the time being Mavic 2 models still have some pretty weird stuff going on. We have added a specific case for handling it, which we do NOT like doing, but support for the Mavic 2 should be OK now. 
 
Feel free to share this. 
Zane 0 votes
Comment actions Permalink
0
Avatar

11/27/2018
I updated my Mavic 2 Pro to the newest firmware 

  • Date: 2018.11.22
  • Aircraft Firmware: v01.00.02.00

I did a small mapping mission on Saturday Nov 24th and the map actually rendered on the correct location in the output on Google Earth.
My previous attempts with the older firmwares resulted in fragmented maps scattered randomly about on Google Maps overlay which were unusable.
The previous issues were a result of incorrect GeoTag data.
Has anyone else tested the latest firmware to confirm the GeoTags are now correct?

View my Sat Nov 24th map created from 62 Mavic 2 Pro images here: https://www.mapsmadeeasy.com/maps/public/d8fe2f0f4cc84a0fb10c9842fbab52b4

Brett Davis 0 votes
Comment actions Permalink