Hello everyone,
Im pulling my hair out over here trying to figure out how to get the P4 RTK to work properly.
I got tired of the error " Weak RTK signal - cannot take off" so I flew without the D-RTK2 base with PPK in mind.
Im in a remote mining location - well out of cell range.
I have a Trimble R10 Base station, that I set for logging.
The base is static and is used daily for RTK surveys on our mine site.
The Trimble collected logging data for 1 hour before I sent up the P4RTK.
I turned off RTK in the DJI GS app.
Sent the drone up and began my flight mission.
The flight consisted of 20 flight lines, about 800-900 meters each.
I had to do 4 battery changes during the flight, so I have 4 folders containing the imagery and the phantoms survey files.
Now, this is where I need some help.
I got my .to2 file from my Trimble base. I converted it to Rinex and got my .19o (obs) and .19n (nav)
I took the PPKRAW.bin file from the drone, converted it and got ppkraw.obs and ppkraw.nav
I opened RTKPost and in the RINEX OBS: Rover field, I brought in the PPKRAW.obs
in the RINEX OBS: Base station I brought in the .19o
and for the RINEX NAV field I brought in the .19n
I executed and got the PPKRAW.pos file.
When I plot that file, it is all over the place.
as can be seen below:
Then I converted my .pos file and the Timestamp.MRK into the Aerotas spreadsheet to create an image tag file.
But its not working for me.
Is there a step by step document around that provides the PPK workflow?
I would like to use the D-RTK 2 base but the one and only successful flight I had, the images were all tagged with the wrong elevation - the geoid height above the WGS 84 Ellipsoid wasnt taken into account.
I tried setting the base up over a known point and then going into the advanced settings on the DJI GS app to add the proper lat and long and elevation in decimal degrees, but I only get an error saying im more than 50 meters away from that coordinate.
Which is incorrect. Its a GCP that is used to tie in our projects.
Anyways, any help would be greatly appreciated!
Thanks