RS Documentation

I have finally managed to get through the start-up section to pair the computer with the Reach RS and now continuing with the documentation. I have reached here ReachView App/Status/RTK Parameters/Age of Differential.

I don’t understand the word “steam”.
In case of steady correction steam age of differential will indicate link latency.

An example to illustrate how the age is derived will be very helpful.


It is a typo in the docs (@dmitriy.ershov)

In [the] case of [a] steady correction steam stream[,] age of differential will indicate link latency. [It is] Calculated by subtracting [the] time when the correction message has been generated from the current receiver time. It is an invaluable tool to debug connectivity issues.

This means:

When you have a steady stream of corrections flowing in, then the age of differential figure can be assumed to be equal to the link latency of your connection.

Which further means:

  • If your corrections are coming in too slow, then the age of differential figure will rise and fall over and over. The lowest of which will be similar to what is said next.
  • If your corrections are coming fast enough, then age of differential will be a constant figure that is equal to the delay in communication between base and rover. You could interpret the figure like so:
    • 0 to 1 second: Excellent!
    • 1 to 3 seconds: Good.
    • 4 to 5 seconds: Fine.
    • 5 to 9 seconds: Slow.
    • 9+ seconds: Too slow. A problem needs correcting.

I was practising on a dummy project and then tried to save to .DXF. My anti-virus sounded a Security Alert.
Screenshot 1:

Has this happened to anyone else?


RTK settings: Positioning mode.
Is it appropriate to set the Reach RS Base unit at Static mode to speed up the resolution of ambiguities and produce higher precision in measurements?

GNSS selection: This is recommended for APAC
• GPS+Beidou+SBAS+QZSS at 5 Hz recommended for APAC, where QZSS and Beidou is visible.

but Beidou is frozen. Cannot access. How do we open it for selection?

  1. Deselect GLONASS
  2. Apply “GNSS select” settings
  3. Select BEIDOU, which will be “unfrozen” by this moment
  4. Apply settings one more time
1 Like

@andrei.kuznetcov, thank you. Worked beautifully.

1 Like

@bide, tx. Your explanation is very clear and should be used in the documentation to replace the existing words.

Each Reach unit can operate a base and a rover at the same time. The setting you are asking about is applicable to the function of a rover. You can ignore it when using Reach as a base.

When I use a Reach unit as a base, I typically set the *positioning mode* to **single** and only enable the raw (UBX) log. Doing that provides a reminder that there is no intention for this unit to be operating as a rover doing RTK work.

Note that there are other scenarios where one may want their base to be operating simultaneously as a base and a rover. For that you would make different choices in your settings.

1 Like

This topic was automatically closed after 100 days. New replies are no longer allowed.