EMLID Caster NTRIP

Reach RS2 / RS2+ RTK / PPK configuration
1

Good afternoon,

My set up is the Reach RS2+ as my base and a Reach RS3 as my rover. New project in upstate South Carolina. To begin, I set up the base and logged into the South Carolina RTN network to establish a known point. Measured the point in my project for 15 min, averaging FIX. From there, I set corrections input to OFF and set my base output to the EMLID Caster NTRIP and configure my base by selecting the point that I measured in the project. This will show a SINGLE solution, which you would expect.

After this is done I turn on my Reach RS3 and set my corrections INPUT to the EMLID Caster NTRIP. Here is where I am running into an issue. On other sites, using this same workflow, I am able to get a FIX on my rover and then shoot in some other control points or stake out points input from Emlid Flow 360 on my desktop. But, on this site I never see any better than a SINGLE solution. At this point I am lucky because I don’t need centimeter accuracy as all I am doing is locating all sewer manholes on site for test digging purposes. I am concerned that when I decide to conduct drone surveys that I will not get centimeter accuracy. Any thoughts?

Any input would help. Can anyone see flaws in the workflow that I am missing?

Thanks,

Chris Greene
Bullseye Construction, Inc.
Charlotte, NC.

3

Hi Chris, your workflow is correct. You collect a point in the Fix solution using NTRIP correction that you will use as a base position. I just want to add that you don’t need to wait until 15 minutes. With NTRIP correction, you can wait until it gets a Fix and averages for a minute. It should be good!

Yes, it’s correct, the base solution is Single.

Does the status tab show “Waiting for corrections”? If yes, the issue is most likely related to a setup or connectivity issue. If you’re connecting via Bluetooth, please ensure you’re using NTRIP over BLE. Also, place the base and rover in the open sky. If everything is set up correctly, and since you got a Fix on another site, the issue seems related to the internet connection.