We have 2 Reach RS (not plus) units which we have tested under various circumstances. The Reach RSes are updated to the latest version prior to every test, currently v2.11.0.
Scenario 1 - Tested Reach RS as a Rover receiving RTCM 3.1 corrections via WiFi hot spot from a fixed based station with an Arrow Gold and Hemisphere A45 antenna. This worked.
Scenario 2 - Test both Reach RS units, one serving as a base and the other as a rover. Correction data sent via LoRa from unit to unit. This worked with best results achieved when manually registering the base over a known reference point or when using the RTK Fix average function to register the base.
Now we are testing Scenario 3, using the Reach RS unit’s as a base station for other rover units. We cannot get this to work so far. The rover units will not computer an RTK Float or Fix solution but rather remain in Single (GPGGA 1) or Differential (GPGGA 2) solution.
Attempt 1 - Using an Eos Arrow Gold as the rover transmitting RTCM from the Reach Base via TCP. The Reach base and Tablet PC are bother connected to the same hot spot. The Gold is connected to the PC via Bluetooth or USB (same result on both) and the correction is transmitted to the Gold via software provided by Eos which has worked for us with other base stations. The Eos Arrow Gold does not compute a Float or Fix solution.
Attempt 2 - Using a RTKITE GGR2T as a rover. Again the RTCM corrections are transmitted from the Reach Base to the Tablet PC via TCP over WiFi hot spot. Then RTK STRSVR is used to forward the RTCM from the TCP Client to the USB serial connection to the RTKITE. NMEA results are sent from the RTKITE to the PC via Bluetooth. The RTKITE does not computer a Float or Fix solution. An LED on the RTKITE does indicate that unit is receiving the correction.
Has anyone successfully used a Reach RS as a base for a non-reach rover? Any details you can provided on how you did it would be really helpful.