Hello, we have a brand new M300 RTK with D-RTK 2 Mobile base station. All firmware and software are up to date. Had it out today for its maiden flight. But we have having an issue with the setting the base coordinates on the controller.

We attempted to input our base position into the controller, but we where given an error that our base position was 26m away from its measured position. I know this to be impossible as we tripled checked the inputted Lat/Long into the controller several times. Eventually we gave up and set the base to an autonomous positioning and flew it with the intention of adjusting the camera positions in Post Process. I checked the autonomous position of the base against our known position, and realized that the distance is much less that 26m. This leads me to believe that there is a mathematical error in the software that computes distance from 2 coordinates (Inputted Position vs Measured Position)



Our Known Base Position (what we input):

Lat: 56.711777999

Long: -111.340810376

Hgt:                        223.254m

Northing:            6285355.007m

Easting:                479136.755m

Elevation:            248.459m



Base Autonomous Position

Lat: 56.711800795

Long: -111.340858877

Hgt:                        224.710m

Northing:             6285357.559m

Easting:                479133.799

Elevation:            247.205m



You can see by the Northings and Eastings, that the true distance between points is only 3.906m Horizontal and 1.254m Vertical and not 26m as it said on the controller…Since this is within the limit of the setting the base position (<15m), It should of allowed me to set the coordinate as I entered it.

Has anyone else had this issue or know a possible solution?


I feel like this is a major downfall and needs to be addressed ASAP.

Potentially unrelated but

1. Make sure the latitude & longitude are in WGS84
2. Elevation value needs to include the rod height measured from ground to the phase center of the D-RTK 2 Mobile Station antenna ~1.8m

djiuser_kMIg5993HklS Posted at 6-14 15:59
Potentially unrelated but

1. Make sure the latitude & longitude are in WGS84

Yes. This was all verified.

I setup my system the following day, and everything appeared to function normally... Seems like it was just a bug in the system, and once everything had a good reset it started working again.

On a side note, I wonder why the minimum distance to set the coordinate was changed to 15m? With the Phantom 4 RTK you could set a coordinate within 50m of the measured point.

I am currently having the same problem

This is a known intermittent problem with this unit. It seems to occur if the D-RTK 2 still has previous base location coordinates in its memory somewhere (has not cleared them out automatically as it should) and that location is farther away than the error threshold. There may be other causes as well.

Getting the unit to accept the true known coordinates for your benchmark may require putting it in autonomous mode for a bit and then going back to trying to enter your coordinates again, as well as cycling the power.

There should be a way to see or at least clear any coordinates currently in memory, but there are many things about this kit that "should be", such as separating out (and remembering) the rod height/APC offset from the benchmark Z coordinate, storing NTRIP setups, allowing one to see the password entered for an NTRIP caster, reading the mountpoint list from the NTRIP caster, etc.

I had same issue but the root cause in my case : I moved the base station when it was initialising...did you start it when it was in position or you started and then installed it?