Getting Fix on Reach receivers via NTRIP

[jjb (juan borda)]

Just wanted to ask:

1. From the raw logs of base & rover, do you PP in kinematic? How will you identify which point corresponds to the RTK shot? Time stamp?
2. When using NTRIP, it usually takes more than 10 minutes to get a fix signal from the rover. When I tested it, the base & rover were less than 2 meters apart. Is there a tip on why it takes so long to get a fix on the rover? I can see that both units are seeing more than 20 satellites from the status page.

[liudmila.slepova]

Hi Juan,

Sorry for the delayed response.

@jjb

From the raw logs of base & rover, do you PP in kinematic? How will you identify which point corresponds to the RTK shot? Time stamp?

Yes, you can post-process the logs collected in Kinematic mode. I have linked down our PPK guides that explain how to get the solution files by post-processing raw data:

• GPS post-processing
• Understanding PPK solution and analyzing logs from Reach

After you get solution files, you can check the coordinates of the collected points using them.

To see the averaged coordinate of one point after post-processing, you need to specify its collection time in the RTKPlot. To do that, go to Edit → Time Span/Interval and set the start and the end time of the desired point collection. You can check the collection time in the project file exported from the Survey tool. For example, in CSV format. Please note that time in the CSV file is in UTC format, while RTKlib works with GPST format. GPST is 18 seconds ahead of UTC.

You can check an ORI parameter in the top right corner of the window of the Position tab. This parameter shows the averaged coordinate of the point.

@jjb

When using NTRIP, it usually takes more than 10 minutes to get a fix signal from the rover. When I tested it, the base & rover were less than 2 meters apart. Is there a tip on why it takes so long to get a fix on the rover? I can see that both units are seeing more than 20 satellites from the status page.

There are usually two reasons why it’s hard to obtain Fix status for the receiver:

• incorrect placement of the unit
• issues with the hardware setup

Reach RS2 can maintain robust performance even in somewhat challenging conditions like urban or partially wooded areas. However, surveying under the thick woods or near the electrical lines might be too challenging for RS2. They usually cause the worsening of the observational data. Subsequently, it can lead to issues with establishing Fix. Reach RS2 requires at least a partial sky view available. You can check the proper placement of Reach RS2 in this guide.

The inappropriate hardware setup might also be the source of the issues with the solution status. It’s important to keep the unit away from electronic components. If you’re integrating Reach in a complicated hardware setup with internal electronics, it can affect the unit’s performance.

Also, NTRIP depends on an Internet connection. The data stream speed might slow down if there is poor network coverage.