Reach RS2 with DJI M300 and P1 Payload-PPK possibility?

I have searched quite a bit and have not found an answer yet to this, so I apologize if it’s already out there.

I’m considering a DJI M300 drone with the P1 45mp camera payload. I really dislike the DJI RTK unit and I’d much rather have PPK anyways since I work in pretty difficult areas (mountain canyons, etc.). I’ve found instructions for linking the M300 and RS2 for NTrip but I often won’t have internet on project sites and again, would prefer PPK.

If I buy an RS2, is it possible to use that as a base to collect PPK and integrate that with the M300/P1? Do I need any additional hardware on the drone? If this is possible, are there any instructions/articles?

Hi Jon,

Yes, the RS2 will collect raw data that can be used for PPK with the M300/P1.

No additional hardware is required but you will benefit from software that will apply the leaver arm/IMU corrections to the data - Suggest looking at Klau or redcatch toolbox for this.

Great thank you! I will have to give this a go then.

Hi Jon,

As far as I know, DJI has a PPK Cloud that allows geotagging images in PPK. We haven’t tested it ourselves, so I can hardly say how smoothly you can get the data. From the Reach RS2 base side, you can record raw data logs in RINEX format.

If your drone’s camera has a hot shoe, you can integrate it with Reach M2. It will allow you to calculate precise image centers without establishing a real-time connection between the base and rover. To learn the detailed workflow, you can explore our PPK mapping with Reach guide.

Does the M300 RTK support PPK [Can it log static data?]. On this webpage, I found this saying that functionality is coming soon.

Update for everyone as I was finally able to test this in the field today. On the DJI M300 you don’t need to do anything special; it will automatically record a .mrk file and a .bin file in addition to the not-so-accurate geotags in the photos themselves. As for the RS2, simply set it up before the flight (I do it as the first thing upon arriving on site), set it to log the Rinex (you can do most formats although I did .ubx). Keep it logging until after you’re done with your flights, then transfer the log file so you have it.

Back at the office use a software like @DanM suggested - Klau PPK or REDcatch toolbox. I tried REDcatch as they were super responsive and cheaper. Klau was also pretty responsive but significantly more expensive. Anyways, at the office you simply start REDcatch, select the Drone profile and the output, then import the images, import the .mrk and .bin from the DJI files, and import the Rinex .ubx from the RS2. The program does the rest for you…you can have it copy the images and edit the exif geotag data, or you can choose different outputs. For example, I use the Pix4D option - the software calculates corrected coordinates for all of the images and creates a new Pix4D Mapper file with the images and inserts the corrected geolocation info. So then all you need to do is open the Pix4D file and start processing!

3 Likes

FYI, this page you are looking at is referring to to the D-RTK DJI base station I think…that base station can only record RTK or PPK if I recall correctly (and I think the PPK may be more of a rumor/beta than a true feature option…not entirely sure). If you use the workflow in my “Update” long response above, you don’t need the DJI RTK base station, just the drone itself and the Emlid Reach RS2 (and software like REDcatch). Hope that helps.

In this case, you are assuming that your base is set over a known point. Or at least you have solved for your Base before inputting into REDCatch? Does REDCatch ask for the Base coordinates?

Redcatch will allow average base position, Rinex header, and manual input.

That’s good news. I also have the M300 P1 RTK2 base combo and looking for solutions. I assume you did have the RTK2 connected to the M300 while collecting data from the RS2?

No, no DJI RTK base is needed. Set up the Emlid RS2 before starting the drone operation. If you have a known point, set it up on top of that. Start the RS2 recording logs before drone takeoff, and make sure it records during the flights and don’t stop it until after your last flight is completed. The M300 drone records it’s own logs and using a software like RedCatch, you can PPK (post process) the drone’s photo exif data. In RedCatch, you have to import the photos, the RS2 logs and the M300 logs.

Hi everyone,

I’d like to add a few words. You can use both RTK2 and Reach RS2 as a base for the DJI M300. A good note is that you should record the log on the base during the whole flight of the drone and that you need to place the base on a known point.

As for PPK, you can use the free beta version of Emlid Studio - our desktop application for post-processing. We have detailed guides on how to work with it, and we are always ready to help you if you face any difficulties.

Hi Elena, Trying out the Emlid Studio beta version and the number of time stamps doesn’t match the number of photos. What would cause that? I’m using beta 10.
I guess I should mention I’m using CORS file for the base station not the RS2. Just trying to work through some flows right now.
Thanks

Hi Joe,

What is the current receiver firmware version, and what Emlid Studio version do you use? We have encountered a similar problem before. However, we released Reach Firmware 27.1, which includes the fix of the issue with missing time marks in August. We also fixed this in Emlid Studio.

Hi Elena,
I’m running v 27.1 on the RS2 and not sure what version of the studio just say Beta 10. OK maybe why this isn’t working for me. My rover file is coming from the M300 and the base is coming from the CORS network not from the RS2. I’m flying another site today with the RS2 set as my base so may give it another shot with that.
Thanks for the response.

Hi Joe,

Thanks for your clarification! It all makes sense now. The thing is that Emlid Studio can currently post-process only time marks recorded directly into the raw data log. However, DJI drones record them in a separate file, so our software just doesn’t find time marks in a log.

We understand that we have many users who can work with DJI drones, so I’ll be sure to note this as a future request.