RINEX header provides delta ofset and xyz value.
It seems off when compared to lat/long provided in the excel file when you change position from lat/long to xyz in RKTpost position.
But when processed with rinex header and display base coordinates it fits spot on.
I think i know what happen.
Base shiftet position from when you used it with rover and when you processed it to get accurate absoulte position of base.
You used rover from 0700-0800 . Base was surveyed to find coordinate somewhere around 1030-1300.
And from the image taken from base, it changed positions
So, this will give you only Q0, or Q5 if display singel position is enabled.
Base station was set up on a control point with known coordinates, even though the coordinates were not dialed in during the base station data acquisition. The base was NOT moved, but was turned off from 0900 to 1030.
What is the standard procedure to process Kinematic PPK with known base station coordinates. Why RINEX Header delivers Q1, but correct base station coordinates delivers 0?
I have even changed the coordinates in the RINEX Header to the correct one and left Use RINEX HEADER option… still Q0.
Are you sure that you did not misplace Lat/Lon in RTKPOST when entering base position? Can you please post a screenshot of how you have entered the coordinate?
What if you replace the coordinate in the header with the surveyed one? You can do that with a text editor.
I assume the filed named MBM12310.17o 42193Kb is log from base right?
And the MBM12310.obs 212Mb is the observation files used to correct base?
I would think so, because this gived med Q1 and very accurate reading with coordinates that you attatched in .excel format. But from the time 1030 to about 1300.
The Q1 fix you get, is that at spike AR or did you get Q1 for the entire run on the rover?
A quick process gives me Q1 spike with RINEX header for a short amount of this. I would think that rinex header is giving you fals reading, but i could be wrong.