I've sent this (or versions of it) to a few customers now. I'm bringing it here for your reference.
On the Triumph-LS:
Make sure that you have the latest versions of software installed.
Make sure that GPS, Glonass, Galileo and Beidou are turned on. Go to Setup and Edit the General Group Profile (top of the screen). Select Advanced > GNSS > Systems & Signals Tracking. Constellations that are on will be white, off will be gray.
On the Triumph-3 / Triumph 1-M:
Make sure that the OAF is up-to-date on the Triumph-3 / Triumph-1M. You can use Base/Rover Setup to update the OAF. With the LS connected to the Internet, connect to the Triumph-3 /Triumph-1M by Bluetooth, then select the button below Start/Stop Base (it has the name of the base and rover). You’ll see an option for Update Options.
Make sure that the firmware is up-to-date on the Triumph-3 / Triumph 1-M. You can use Base/Rover Setup to update the firmware on the Triumph-3 / Triumph 1-M. With the LS connected to the Internet, connect to the Triumph-3 by Bluetooth, then select the button below Start/Stop Base (it has the name of the base and rover). You’ll see an option for Update Firmware. It would also be a good time to update the radio firmware on your Triumph-3. This option is available on the same screen.
In Base/Rover Setup, you need to set your communications to:
Message Format: RTCM 3.2 MSM3 Short
Modulation: D8PSK
All other communication settings are according to your preference.
In the action screen, you’ll need to change the GNSS firmware to one of two multi-constellation firmwares: GPS+GLO+GAL+BDU 6Eng or GPS+GLO+GAL+BDU 2Eng. I believe the 2 engine version to be more robust than the 6 engine version. The 6 engine version divides the constellations by two’s into each engine (Engine 1 = GPS + GLO, Engine 2 = GPS + GAL, etc. ), while the 2 engine version uses three constellations in each engine. Engine 1 has GPS+GLO+GAL and Engine 2 has GLO+GAL+BDU.
If you use the 6 engine version, you can use the same action profiles you used with GPS+GLO (Boundary, Precise Topo, Quick Topo, etc.) If you use the 2 Engine version, you’ll need to make a copy of your favorite profiles and modify them because you only have two engines. So for the Boundary profile, make a copy of it and name the copy “Boundary 2 Eng” or something you can associate with being for the 2 engine firmware. Using a copy, instead of modifying your original, will allow you to use the original in the 6 engine versions. In the Boundary 2 Eng profile you’ll want to set the minimum number of RTK engines to 1 instead of 2 and set the number of engines for validate to 1 instead of 2. The same for Precise Topo. In Quick Topo (if you use it), you’ll want to set the minimum number of engines to 2 instead of 5 (since you don’t have five engines to fix with the 2 engine profile). You will also want to turn off Consistency since it only increments with 2 engines fixed, which can be difficult to obtain in canopy.
You’ll notice that downloading the base data at the end of the session will take a bit longer. That’s because your raw data files are now about twice the size because it includes raw data from two additional constellations. The good news is that DPOS is even more reliable with multi-constellation data than with GPS+Glonass alone. So the files are bigger and download times longer, but the results are much better as well.
On the Triumph-LS:
Make sure that you have the latest versions of software installed.
Make sure that GPS, Glonass, Galileo and Beidou are turned on. Go to Setup and Edit the General Group Profile (top of the screen). Select Advanced > GNSS > Systems & Signals Tracking. Constellations that are on will be white, off will be gray.
On the Triumph-3 / Triumph 1-M:
Make sure that the OAF is up-to-date on the Triumph-3 / Triumph-1M. You can use Base/Rover Setup to update the OAF. With the LS connected to the Internet, connect to the Triumph-3 /Triumph-1M by Bluetooth, then select the button below Start/Stop Base (it has the name of the base and rover). You’ll see an option for Update Options.
Make sure that the firmware is up-to-date on the Triumph-3 / Triumph 1-M. You can use Base/Rover Setup to update the firmware on the Triumph-3 / Triumph 1-M. With the LS connected to the Internet, connect to the Triumph-3 by Bluetooth, then select the button below Start/Stop Base (it has the name of the base and rover). You’ll see an option for Update Firmware. It would also be a good time to update the radio firmware on your Triumph-3. This option is available on the same screen.
In Base/Rover Setup, you need to set your communications to:
Message Format: RTCM 3.2 MSM3 Short
Modulation: D8PSK
All other communication settings are according to your preference.
In the action screen, you’ll need to change the GNSS firmware to one of two multi-constellation firmwares: GPS+GLO+GAL+BDU 6Eng or GPS+GLO+GAL+BDU 2Eng. I believe the 2 engine version to be more robust than the 6 engine version. The 6 engine version divides the constellations by two’s into each engine (Engine 1 = GPS + GLO, Engine 2 = GPS + GAL, etc. ), while the 2 engine version uses three constellations in each engine. Engine 1 has GPS+GLO+GAL and Engine 2 has GLO+GAL+BDU.
If you use the 6 engine version, you can use the same action profiles you used with GPS+GLO (Boundary, Precise Topo, Quick Topo, etc.) If you use the 2 Engine version, you’ll need to make a copy of your favorite profiles and modify them because you only have two engines. So for the Boundary profile, make a copy of it and name the copy “Boundary 2 Eng” or something you can associate with being for the 2 engine firmware. Using a copy, instead of modifying your original, will allow you to use the original in the 6 engine versions. In the Boundary 2 Eng profile you’ll want to set the minimum number of RTK engines to 1 instead of 2 and set the number of engines for validate to 1 instead of 2. The same for Precise Topo. In Quick Topo (if you use it), you’ll want to set the minimum number of engines to 2 instead of 5 (since you don’t have five engines to fix with the 2 engine profile). You will also want to turn off Consistency since it only increments with 2 engines fixed, which can be difficult to obtain in canopy.
You’ll notice that downloading the base data at the end of the session will take a bit longer. That’s because your raw data files are now about twice the size because it includes raw data from two additional constellations. The good news is that DPOS is even more reliable with multi-constellation data than with GPS+Glonass alone. So the files are bigger and download times longer, but the results are much better as well.