First problem with the Matrice 4 E

[Jaybro130]

Jaja,
I received this email this morning, so they admit it IS a problem. I also highlighted a dewarping issue with them that they are working on…

“Our senior engineer has analyzed this issue:

1. According to the analysis with R&D department, the RTK issue is caused by RTK algorithm, due to the limitation of technical solutions, it might not be possible to be solved effectively at present, and it needs to be updated and optimised in the future.

2. The dewarping issue is indeed exist, thanks for your feedback and our R&D department will solve it in the future fimware update.

3. The current menu for pre-flight checks indeed does not have an option for dewarping. This is because the pre-flight checklist is mainly for the testing of flight systems and sensory systems to ensure flight safety. I will also let R&D department know this request.”
I’m hoping they get a firmware update out soon…

 

[AlexisFraNorge]

Jaja,
I received this email this morning, so they admit it IS a problem. I also highlighted a dewarping issue with them that they are working on…

“Our senior engineer has analyzed this issue:

1. According to the analysis with R&D department, the RTK issue is caused by RTK algorithm, due to the limitation of technical solutions, it might not be possible to be solved effectively at present, and it needs to be updated and optimised in the future.

2. The dewarping issue is indeed exist, thanks for your feedback and our R&D department will solve it in the future fimware update.

3. The current menu for pre-flight checks indeed does not have an option for dewarping. This is because the pre-flight checklist is mainly for the testing of flight systems and sensory systems to ensure flight safety. I will also let R&D department know this request.”
I’m hoping they get a firmware update out soon…

Thank you for sharing this update, @Jaybro130 — much appreciated.

Just to clarify, regarding the dewarping issue mentioned in point #2: is this the same issue referenced in point #3 about the absence of a dewarping option in the pre-flight checklist? Or are they referring to two separate aspects of the same broader problem?

Before switching to the Matrice 4E, I was using the Mavic 3 Classic for mapping missions, paired with an in-house route creation tool. The RAW images from the Mavic 3 Classic also exhibited a noticeable black vignette in the corners, which is typical of uncorrected (undistorted) images straight from the sensor.

However, after applying a lens calibration profile to dewarp the images, the vignette disappeared completely — suggesting that the vignetting is intrinsic to the optical geometry and can be addressed effectively during post-processing.

 

[AlexisFraNorge]

Thanks for the update.

On my end, I could not get the Matrice 4 E to go FIX today. I tried different hotspots and different mount points from my RTK provider. FLOAT only including when in the air.
I messed up and did not bring my Phantom RTK so I don't have my client's data, live and learn to always have Plan B.
I was going to make a map, model and RTK positioned video (repeatable to document progress).
I had to use my Mavic 2 Enterprise Advanced for the video since it will do positioning. I will bring the Phantom RTK out and grab the map and model tomorrow.

I will open up another support case, but we now know that this is a widespread issue. I just want them to get my drone's logs and the RINEX files as I think the more information DJI has, the faster and better the firmware fix will be.

I am on the newest firmware v12.01.06.07 released on March 17, so it is possible that this new firmware is behind this. I may roll back and see if I am back in business.

Keep us updated please, and I will do the same.

Hey @jaja6009,

I just saw your post about using the M4E for repeatable progress videos — really interesting!

I recently tried something similar using RTK and the Waypoint Route feature with Live Mission Recording in DJI Pilot 2 to create a hyperlapse. But I ran into a major limitation: the app doesn't seem to record the drone’s heading or the gimbal tilt/orientation when creating waypoints. As a result, the drone just flies a straight line, and the footage doesn't include the framing I was aiming for.

I'm curious how you’ve been handling this in your progress videos. Are you flying straight paths with fixed headings, or POIs? Or have you found some other workaround to keep things repeatable?

Also, since you’re doing video too — do you find the lack of ND filters limiting at all?

Would love to hear how you're approaching it.

 

[jaja6009]

Hey @jaja6009,

I just saw your post about using the M4E for repeatable progress videos — really interesting!

I recently tried something similar using RTK and the Waypoint Route feature with Live Mission Recording in DJI Pilot 2 to create a hyperlapse. But I ran into a major limitation: the app doesn't seem to record the drone’s heading or the gimbal tilt/orientation when creating waypoints. As a result, the drone just flies a straight line, and the footage doesn't include the framing I was aiming for.

I'm curious how you’ve been handling this in your progress videos. Are you flying straight paths with fixed headings, or POIs? Or have you found some other workaround to keep things repeatable?

Also, since you’re doing video too — do you find the lack of ND filters limiting at all?

Would love to hear how you're approaching it.

When doing a video I do this:

Live Mission Recording, fly how youo want the drone to proceed.

When finished there is now a problem, the drone will run the mission and not stay pointed at a POI.

Open the mission up and add the POI icon to the point of interest and save the mission. The drone will now keep the camera on target. On the videos I have done each mission's video is reasonably the same as the previous, though not perfect even with the RTK. One mission that was more windy has some changes that can be seen if you overlay the videos and look frame by frame.

While ND filters would be nice, I work with what I have.