Thanks for your participation in this discussion and your willingness to help!
@james.barnes1177, I’ve read through the whole thread and highlighted the main points, which introduce some uncertainties right now. I’ve left my comments so to help resolve the issues with the setup you faced.
When you’re in the office, your RS2 receivers are connected to the same local Wi-Fi network as your mobile device. When you go outdoors, Reach, and your mobile device loses the connection with this network. It means that the devices aren’t in the same network, so you can’t connect to them in ReachView 3.
You can access multiple Reach devices from ReachView 3 when those receivers and mobile devices are connected to the same network.
You have two RS2 with SIM cards that use mobile data. In such a case, you can select one of the following configurations:
- configure both RS2 to share the separate Wi-Fi networks using the mobile data from a SIM card
For this, do the following:
- Go to the Mobile data tab and enable cellular network
- Enable Share mobile data from Reach in hotspot mode toggle bar
Reach RS2 will start to share the Internet connection via its hotspot. You can connect your mobile device to it.
However, RS2 devices will not be accessible at the same time in the app. For selecting the receivers in the app, you will need to connect to their hotspot in the Wi-Fi settings of the mobile device each time.
- configure both RS2 to connect to the same Wi-Fi network via one of Reach’s hotspot
Here you need to enable one RS2 to share mobile data hotspot. Then, connect your mobile device and the second Reach to this network. All the devices will be connected to the same network so that you can access two RS2 in the app.
Nevertheless, please note that the Reach’s hotspot range isn’t tailored for long-range communication. If you plan to place the base and rover far away from each other, it’s better to use the configuration I’ve described below.
- configure both RS2 to connect to the same Wi-Fi network via an external device
This will allow you to switch between them in the app at once too. Though, here you won’t need two RS2 to use the mobile data via its SIM cards at all. You can use your mobile phone’s hotspot for this when you’re working remotely.
The configuration process of connecting RS2 to the phone’s hotspot is the same as the connection to the office Wi-Fi. The only thing is that you need to choose the Connect to a hidden network before inputting the network credentials.
This point and all the other steps are described in the Connecting Reach to Internet via Wi-Fi guide. Please follow the guide’s instructions step-by-step. If you encounter any issues during the configuration, let me know at what step it appears. We’ll figure this out.
Emlid NTRIP Caster helps you to transmit the corrections between the base and rover using NTRIP protocol. It doesn’t provide corrections itself. You may think of it as an alternative method for LoRa RTK-link. For more info, I suggest checking out this blog article that explains the main differences between NTRIP Caster and Service.
When you’ve connected the base unit to the Caster, the device started to transmit its corrections to the mount point. Your rover would have received the corrections if you’d connected the rover to this mount point.
If you don’t want to keep the light of sight between the receivers, you can use this method of RTK-link establishment. LoRa radio is a low-powered radio, so it’s sensitive to any physical obstacles standing between the devices. Since you have two RS2 with the SIM cards, you can connect them to the Internet and then to the assigned mount point from the Emlid NTRIP Caster profile.
The air data rate value is grayed out when there are many RTCM3 messages selected. The more RTCM3 messages are coming, the less air data rate options are available. So, you need to uncheck some of the messages to work with less air data rate. For example, you can leave 1006 with 1074 enabled and unselect the rest of them.
Still, you can work with the available air data rate at this moment. 18.23 kb/s will shorten the maximum LoRa baseline, but it will not affect the ability to transmit and receive corrections on a small distance. As I understand, you test the connection of two devices placed close, so you should be able to receive the corrections on the rover.
Make sure you selected the same air data rate and frequency on both base and rover devices. Also, there should be no obstacles between the receivers.