We’ve been having problems getting fix locations with the RS2. For some reason, the Rinex 3.03 files are incomplete or missing satellites. I urgently needed to post-process something so I used RTKconv to get those Rinex files from the UBX. It worked this time, but I know that conversion through RTKconv may cause to lose data to post-process and I want to avoid that as much as possible.
Through a rep from Onpoz, there have been arguments that RS2 is been having converting issues to RINEX 3.03. A test area was done and these were the findings for BASE and ROVER post-process on 4 GCPs, 20-25 minute base logging and 1-minute collecting rover over each GCP, with CORS site less than 3 kilometers away:
- Some missing epochs (data is dropped for unknown reason). When native file is converted to RINEX we can observe the same missing epochs.
Below graph shows missing GPS epochs, but exact same issue is observed on all constellations (missing epochs at same time)
- Missing L2 carrier phase for some satellites
The first graph shows L1 carrier phase (the same file as above but the above graph shows L1 code signal, while the following graph shows the carrier phase). As expected, the L1 carrier phase is received for all satellites.
HOWEVER, if we look at the L2 carrier phase (or L2 code) for the same file as above: **L2 is not available for all satellites **.
The below graph is missing 2 GPS satellites G21 and G21.
This issue was observed on GPS and Beidou constellations (Galileo and Glonass seem ok).
- RINEX conversion issue: When UBX file is converted to RINEX some L2 data is dropped during conversion
Always using the same file: Native_UBX file shown above was converted to RINEX shown below, in the RINEX file there is less L2 signal than in the equivalent UBX file.
Note: conversion to Rinex made by Emlid (using Emlid RINEX conversion tool).
…end of findings.
We also have an RS+ and we can post-process with Rinex 3.03 with no issues. Hence, awareness rose when we weren’t able to get good results from post-process with the RS2.
We reach the emlid developers if this has been an issue and if it can be solved.