Since we are asking beginner questions here please let me add mine:
I don’t have an RTK drone, just a normal P4P and use an RS2 with GCP’s. I was always wondering about the local Ntrip connection and how the Emlid sends this to the drone. I’ve asked a few people before and got varying answers.
My Question:
When using the EMLID Local NTRIP connection to broadcast the EMlid position I assume its doing this via the Emlids built-in WIFI connection right?
If so, this would not have a huge range right? Like 100m? But the drone eg a P4P RTK has a range in kilometers, so how does the drone keep connected to the emlid base?
Or does the “Drone controller” connect to the base (while you stay close to the base with the controller), and the controller sends the emlid position on to the drone itself? Which would make sense to me, but was previously told this was not the case?
I’m particularly interested in how that works with the older P4P RTK and the newer M3ERTK as I was thinking of looking to upgrade to either of those.
With Local NTRIP the Reach broadcasts on the local WiFi network, not more broadly through a caster. In our case we put the Reach and the M3E controller onto the same WiFi router, whether we have a mobile network or not. The controller connects to the Reach corrections stream using one of the custom correction setups and the controller takes care of sending the corrections to the drone.
Thanks Mike,
So why the Router in the field?
If you setup your base near where you are standing with the controller, then couldn’t the controller just connect directly to the Emlid Wifi and send the corrections on to the Drone?
So long as you stay within range of the Emlid base with the controller of course…
For us it was about getting one simple, reliable setup. Every time we hit a site the first thing that gets turned on is the WiFi router. Then as everything else is fired up it automatically connects to the WiFi router. It takes the fuss and frustration out of the equation. If there is mobile coverage or there isn’t mobile coverage the network setup is still the same. Otherwise it was a case of phone hotspot, which we found a pain, if there was coverage…
Ahhh, thanks that makes total sense. I had so many problems connecting via Wifi with the RS2 many firmware’s ago, so I now get it.
Of course, now we just use the BT connection so nothing is a problem for that.
But I can see the sense in having the Router all running then bringing everything else online one at a time so everything is connected via the same setup each time.
BTW do you have AC power in vehicle for the Router, or some cool battery powered travel Router?
Ahh awesome, thanks so much Mike.
Thats super helpful. I just looked up that router and it is available here in NZ as well.
5G is very patchy outside main cities here, will t also connect to 3G and 4G?
As is often the case in our community, your question might already have an answer
The local NTRIP function is designed for drone mapping when both the base station and the remote drone controller are on the same Wi-Fi network. Internet access is not required. You can also connect directly to the Reach hotspot, but you’ll need to stay within a few meters.
Does your surveying area have good cellular coverage? If so, you might also consider using Emlid Caster. In this scenario, both devices should have a stable internet connection.
I just wanted to add that you can use your phone’s hotspot regardless if you have a cellular data connection or not. Just like the router option.
The router option is certainly a good approach, especially if you are a team in the field. I generally operate alone. And so long as I keep all the components within range of my phone’s hotspot, everything works perfectly. An additional router is just another possible fail point in that case.
I operate the drone via local NTRIP. And I set control points via LoRa radio, in most cases.
