I don’t know whether it’s something I do but I see differences in rover POS files when I PPK the same rover OBS using the same RS2 as base but one time I converted the UBX to rinex 3.02 with RTKLIB and one time I took the rinex 3.02 that was recorded directly by the RS2 (all from the same logging of the RS2).
Base reference 2 - when recording raw rinex, ubx is also recorded as backup. I converted the ubx to rinex 3.02 with rtklib.
Note - both of the above were recorded during the same log session of the RS2 simultaneously.
I then PPK’ed the same rover obs file, one time with the raw rinex 3.02 that was saved by the RS2 (base ref 1) and then a second time using the rinex that was converted from ubx file (base ref 2).
Should there be such a difference between these two methods? Shouldn’t it be the same rinex? I didn’t intend to test it. I stumbled across this difference by chance.
@TB_RTK - “waaay out” for float is 10s of meters? isn’t float more like 1-2 [m]?
There is no outer edge for a float so any numbers is possible.
But looking at your pattern above(pointed out by @wizprod) is seems like a systematic error e.g wrong base coordinates (They are all equaly shifted).
But I have also seen bad data produce similar shift.
Convbin is not part of Emlids program (as of writing).
The entire RTKlib has not been tuned to their product line.
I would stick with apps provided by Emlid Kinematic processing | Emlid Studio
Distances between the 2 results are in +10m or +3m? If +3m then I believe the reason is the that your RTKPost setting is reading the position from the header of each Rinex file (Approximate Position XYZ ).
Try to change these 2 lines to have the same values or set them to 0 0 0 and input your base position in RTKPost.
I used the Debian package for ubuntu from here Ubuntu – Package Search Results -- rtklib and that had version 2.4.3 b8. I think the biggest thing with that version was that the ubx conversion yielded after UBX conversion, a single frequency OBS from the RS2 which is not right.
I downloaded the ubuntu binaries from the link you sent and that is
Now all seems OK. Position diff between the raw rinex and converted ubx makes sense now:
I think the b8 version of RTKConv is for L1 only. I was affected by it several months ago and someone from Emlid pointed this out. I did not know that it was for L1 only. b33 version is for L1/L2
This topic is quite old. But it’s never too late for some updates, right? Just wanted to say that now you can use the Emlid Studio app to convert the logs to RINEX. We tried to make the app intuitive, but you can also find all the conversion steps in this guide from Emlid Studio docs.
