@thomas.purk wrote:
We always update our Reach RS units to the latest version, currently 2.11. However, we believe we saw some for of this problem going back several versions, but in earlier versions did not yet understand the problem.
The problem is that the Reach RS shows on the Status tab and in the NMEA log the last collection point even after moving the rover to a new location anywhere from 10m - 100m away. So if at location A the rover achieves a very good fix, then we move to point B the rover continues to produce point estimates at location A. We saw this repeatedly several times recently. And we think this explains why some of our test data collected last year were inaccurate by 16 meters at one location and 80 meters at another.
We use the Reach RS as a rover to log real time position estimates to a NMEA log file.
Our testing method;
- Position the Reach RS over a known location
- Start logging
- Stop logging after 20 minutes
- Position the Reach RS over the next known location
- Start logging
6 Stop logging after 20 minitesWe repeat this until we record data at all 18 of our test locations.
RTK Settings
Postion Mode: Static
GPS AR Mode: Fix-and-hold
GLONASS AR Mode: Off
Elevation Mask Angle: 10 degrees
SNR Mask Angle: 30 degrees
Max Acceleration V and H: 1 m/s2
GNSS Select: GPS, GNSS, Galileo
Update Rate: 1 HzThe workaround we found was to toggle off the Base Correction button on the Correction Input tab and click apply and then toggle back on and click apply. We started doing this just before starting to log at each new location.
Posts: 8
Participants: 6