NTRIP connection lost on Reach RX

We have been testing the device for two weeks and can only agree what was said before - amazing device with same accuracy as the RS2, also in forests. However you have to be careful if you don’t have a fix status (like with any GNSS receiver).

What we encountered though, is that sometimes when connecting via bluetooth to a third party app (Qfield) the ntrip connection is lost after some time. After removing and adding the BLE ntrip connection in reachview app it woks again. Anybody had the same issue?

Hi @hartl.consulting,

Welcome to our community!

We have been testing the device for two weeks and can only agree what was said before - amazing device with same accuracy as the RS2, also in forests.

Sounds wonderful! Thanks for sharing your experience.

What we encountered though, is that sometimes when connecting via bluetooth to a third party app (Qfield) the ntrip connection is lost after some time. After removing and adding the BLE ntrip connection in reachview app it woks again.

Does anything unusual happen before the connection is lost? How much time passes before that? Can your Reach RX start receiving NTRIP corrections again in a while, or is it necessary to reconnect it manually?

If you haven’t tried to set the correction input and Mock location in the Lefebure NTRIP Client, please let me know if it changes anything. You can find the step-by-step workflow in our docs.

In case it doesn’t help, please share a bit more info about the setup:

  • Is the ReachView 3 app updated to the latest version?

  • What’s your mobile device model and OS version?

  • Do you use a local base or an NTRIP service? If it’s a service, please tell me which one you use.

I had similar issues with corrections being lost while using the RX in Puerto Rico a few weeks ago. I don’t think the issue was with the RX, I believe it was with my NTRIP correction service the Puerto Rico Seismic Network (PRSN) real time GNSS service. I could get a FIX when I had a clear view of the sky but not when I was near any trees. I think the corrections kept timing out as the age of the corrections would keep increasing up to 1 minute and then stop. I think the second issue was that the PRSN NTRIP service was only providing correction data for approximately 9 satellites while the RX could see almost 40 total satellites.

I eventually set up my RS2+ on one of the points that I established with the RX, and then used the Lora antenna and my RS2 as the rover. With this combination I had only one point where I couldn’t get a FIX and that point was over a meter below a concrete aqueduct. I have not had a chance to try this test in a controlled environment but hope to do so in the next month.

Hi @ryanenorth,

As an alternative, you can also work with the Reach RS2/RS2+ base and RX rover using Emlid Caster. Check the guide for more details:

I do this regularly, but since I was in a hurry I decided to just use the pair of RS2 and RS2+ units with Lora.

1 Like

Good to know it works for you!