LoRa range issue and zero coordinates using TcpGPS

Hi, I’m Marc from Referent Solutions, official Emlid distributor in Spain.

We’re currently facing a couple of issues with a client who rented two Reach RS3 units to work in a mountainous area near Albacete (Spain), using a base and rover setup with Aplitop’s TcpGPS software.

The first and most relevant issue regarding Emlid is that the client reports losing LoRa correction at distances beyond 300 meters. Do you have any recommendations for improving range in terrain with elevation changes and some vegetation? Anything we can try to enhance the LoRa coverage?

The second issue is with TcpGPS itself. When collecting points with the rover through TcpGPS, the displayed coordinates are all zeros (X:0 Y:0 Z:0). The software allows them to save points, but they’re saved without coordinates—just raw data. However, when using Emlid Flow, everything works perfectly: they receive corrections, coordinates are displayed, and points are stored correctly.

Even though we believe this issue is likely related to TcpGPS, we’d like to double-check if there could be anything on the Emlid side affecting the coordinate output to external software, or if there are specific settings to consider when working with TcpGPS.

Thanks a lot in advance for your help!

Best regards,
Marc

Referent Solutions

1 Like

Hi Marc,

I saw that you reached out to us via email regarding the same topic, and I answered you there. Let’s continue the communication in email. Thank you!

1 Like

If you find out the issue with the poor range please let me know. I can get about 1/2mile fairly reliably if there’s not too much obstruction. My RS2 units seemed much better.

1 Like

A post was split to a new topic: LoRa Signal in terrain change