For your Triumph-LS+ 'rover' to use ‘beast mode’, simply select the appropriate RTK/DGPS Settings 'RTK Rate' and also check Data UpSampling option.
This will configure your Triumph-LS+ 'rover' to use the 1-second RTK RTCM 3.2 MSM 'base' corrections transmission data rate received from your 'base' via UHF, or TCPO, or NTRIP Caster as an up sampled 'beast-mode'.
The above image, and the following image show the TLS configured to use a 2 Hz (twice per second interval) 'rover RTK position computation rate . . .
With 25 GNSS satellites (GPS + GLO + GAL + BDS) being tracked by the 'rover' with the same number of RTCM 3.2 MSM satellite corrections being provided by the 'base' (that is being used) . . .
Footnote: In the above example, the number of GNSS satellite being used is 25, with two frequencies per constellation.
Therefore, a total of 50 'signals' does not exceed the RTK engine parameters of a 'default' Maximum signals of 60
Related Link:
- see RTK Verification with New Boundary, Precise Topo and Topo Profiles
This will configure your Triumph-LS+ 'rover' to use the 1-second RTK RTCM 3.2 MSM 'base' corrections transmission data rate received from your 'base' via UHF, or TCPO, or NTRIP Caster as an up sampled 'beast-mode'.
The above image, and the following image show the TLS configured to use a 2 Hz (twice per second interval) 'rover RTK position computation rate . . .
With 25 GNSS satellites (GPS + GLO + GAL + BDS) being tracked by the 'rover' with the same number of RTCM 3.2 MSM satellite corrections being provided by the 'base' (that is being used) . . .
Footnote: In the above example, the number of GNSS satellite being used is 25, with two frequencies per constellation.
Therefore, a total of 50 'signals' does not exceed the RTK engine parameters of a 'default' Maximum signals of 60
Related Link:
- see RTK Verification with New Boundary, Precise Topo and Topo Profiles
Last edited: