After completing my first test PPK mission with an RS2 + M2 setup, I have observed some strange behavior with the time/event mark locations. I have prior experience using the M+ and RS+. I seek input on my configuration and/or workflow to amend the event mark positions.
In summary: The time/event mark locations are not associated with the post-processed rover position log/paths, they are scattered about with only light correlation to the rover position file path. The rover position file maintains 99.9% Fix during flight, and the time mark file maintains 100% Fix. Event marks run well off the ends of the survey grid, and wobble greatly along the rover path. Event mark altitudes vary by +/- 40m. Neither of these issues are present in the rover position file, so I do not understand where or how these event mark positions are derived - they are almost certainly not interpolated from the rover position file as I would anticipate, since they are not “between” rover positions along the path. There is a large void in time marks present in the middle of the survey, which does not reflect image capture absences. From my work with the M+ and RS+, missing time marks are nothing new, but this issue seems very new to this combination of equipment and software.
For this mission I used OPUS to process the base station coordinates, tested prior to provide decent accuracy (~1.5cm with 30 minute observation).
Manually inserted OPUS coordinates in Lat/Lon/Height (dms/m) format, as follows:
LAT: 29 6 33.03234 0.008(m)
W LON: (-)81 5 13.87802 0.006(m)
EL HGT: -22.100(m) 0.023(m)
For more details see OPUS report in ZIP file
Used RINEX version 2.11 for consistency with OPUS requirements (Also tried 3.03)
All other steps as prescribed to the best of my understanding
Hardware setup as prescribed in setup guide, powered by external 5.1V BEC. Antenna placement as pictured below.
Now I have flown 2 tests with your latest update of RS and M2.
Flight 1: 88 photo 6.6 ha Height 70 m speed 4m / sec camera shutter 1/500 sec.
Flight 2: 73 photo the same height and settings.
All markings in events were equal to the number of photos.
When running in RTKLIB 33b RS2 as base log rinex 3.03
M2 like Rover log rinex 3.03. The result was outstanding
in both tests, fix everything and a diff in Z of just 2/3 cm.
It looks very promising as it works now.
You have done a very good job.