I have an Emlid Reach RS2+ Base that I use to provide RTK to my M3E. Initially, I was able to use the Reach for corrections and things were working. I had a lot of issues connecting to the Reach’s Hotspot. Now I can connect to the Reach’s hotspot , but I can not get the Pilot app to do anything with the RTK input. When I enter the RTK settings and press Save I get the same messages: “Settings Failed”. This goes away and then it says in red letters “Connecting or not Connected” And that is it. I now can not get any corrections what so ever to M3E. I have check all my settings ad nauseum. My updates are current for both RS2+ and M3E. I setup theRS2+ with the hotspot which I connect to with the DJI RC Pro controller. Shows connected when looking a the RC’s WiFi settings. Output setting is Local NTRIP setting for the RS2+. Any ideas on how to solve this problem would be greatly appreciated! Thanks in Advance!
You’re connecting the RC directly to the receiver? Have you tried forgetting and re-authenticating with it? I usually network the two with my phone hotspot or a router. I found a dedicated networking device to be more reliable.
I’ve had lots of problems with this combination too ( Get a RTK signal Weak. Move to an open area for takeoff or turn off RTK (0x16100066) error message on the DJI RC Pro). I see another forum member posted previously having the same problem.
Like you, my RC Pro was connected to the Emlid with wifi, so it didnt make sense. The previous poster did mention to change your ntrip details to the same as shown in the info section under your Base output.
This seemed to do the trick, you need to reboot the drone as well. I haven’t flown the drone yet, was only trying to troubleshoot at home, hopefully it logs correctly, I’m still a newbie. I don’t understand if I set a Cors stn to my emlid why do i put in a different ntrip to my RC. I presume the ntrip corrections are still relayed through properly.
LightTunnelProd, Sounds like we are kind of in the same boat trying to get this combination working. I also am at my home sorting this out before I go out into the field. I am also a newbie. So from what I understand so far, you need corrections for the satellite signals for each receiver. I am sure that you know this, when you hook up the base and get NTRIP signals you are correcting for the Base’s GPS Error. The way any of these calculations to correct for error is to take an average. This is why the longer the Receiver is able to acquire signals the larger the data base is to use for averaging the more theoretically it is to be close to accurate. The Baseline distance matters. The distance from the Base to the rover has its own set of errors and what ever you can do to minimize that distance reduces that error. So if you are able to get a Base position established through a CORS station with a long data acquisition time it will be theoretically accurate. The small distance of the Reach Base to the Drone normally has very little error. This is why they say that a Reach Base to a Rover is centimeter accurate relative to each other , but only absolute accuracy to how well you set up the bases position. To get back to your question, the corrections from the CORS station is only for the Base to correct itself. Once the Base knows its position, Fix solution, it relays its position correction to the Rover. I am not sure if you are using the Local NTRIP setting in outputs? This is the Port that is used to send corrections from the Base to the Rover. My Question is that the acquisition time that you set under the Base settings in Emlid Flow, is that the time that it uses to average out for the Base’s position calculations? Anybody reading this that can verify my assumptions, I would appreciate any corrections. I don’t want to find out that this was all BS like I did when I found out Santa didn’t exist in my forties’.
Hey MichaelL, Yes, I am connecting directly from the RS2+ to the RC using the Hotspot WiFi. I have recycled the the Custom RTK Network settings in the DJI Pilot 2 App several times to no avail. I guess I will try using my phone’s hotspot and see what happens. Thanks for your help!
The averaging time in base settings is the amount of time that it averages (in a FIX condition if specified) to collect the base point. That’s it. It will not continue to average. It will start the average process again if you tell it to do so, but it will not do it on it’s own.
Your NTRIP settings on the RC must match the Local NTRIP settings, specified by tapping the info button next to local NTRIP on the Reach, exactly. One character off and it will not work at all.
Very specific. And, if you reboot the Reach unit, the IP for local NTRIP output will change, so you have to look at the info screen again and make any adjustments to the setting on the RC. There are no compromises, it has to be perfect.
IMO it’s latency and if you get slightly too far away from the receiver it will act up. Having my phone in between increases that range and a decent Wi-Fi router is even better. A Wi-Fi router with data service is the ultimate in my scenario.
that makes sense actually
Did you guys resolve this problem? I’m having the same issue.
Sorry for the silence here. I noticed you’ve gotten a lot of input from Michael in this thread. Have you found a solution to your issue? Do you have any further questions?
Thanks for checking in on this. I’ve figured out how finicky the M3E can be connecting. But with help from Joe Douglas from E38, I’m getting good connections. Thanks!
Hi Jay. ALL of the RTK drones are very finicky! One character off, and it’s a no-go. And they won’t tell you what the problem is, so it can be frustrating… Welcome to the current state of RTK!