OPUS Aborted RS2: Collection interval was not one of the allowed rates

[tatiana.andreeva]

Hey there,

We conducted a couple of tests with OPUS and RINEX data from Reach RS2 and collected some recommendations for log recording to prevent any issues with OPUS:

• In the RTK Settings tab, choose Static Positioning mode, enable GPS only and set up the update rate to 1 Hz
• Go to Logging tab and select RINEX 2.10 raw data format
• Enable raw data recording and log the data for more than 2,5 hours. According to OPUS, it’s better to use raw data logged for 4 hours at least

We also recommend using the latest dev v2.21.1 version to log raw data on Reach RS2 as in this release we’ve fixed the issue with missing epochs in raw data logs and bug with some L2 carrier dropped during conversion to RINEX on Reach.

@Chester

I believe the issue is that the RS2 does not have a tight tolerance for the logging epoch. For example, my logging rate was setup at 1sec and the resulting epochs were shifted from a precise second:

Start: 2019 10 20 20 40 28.0010000

End: 2019 10 20 23 59 32.0100000

According to our tests, it shouldn’t affect PPP in OPUS.

I’d also like to point out that OPUS processes only GPS data. It seems OPUS can accept the logs containing other constellations as well, however, it can abort the processing in case the first epoch doesn’t contain GPS data. That’s why our general recommendation is to log GPS only for OPUS.

Thank you.