My errors are:
GPS2: Still configuring this GPS
Also, when I have the M2 powered, the error: Pre-arm Baro not healthy comes up. But as soon as I unplug it, the error goes away.
I am pretty new to this, but I know for a fact that the Emlid M2 isn’t receiving corrections based on all of the emlid flow options. So I dont think this is a mission planner problem. Also, on my NTRIP provider, it only sends/receives corrections every ~30 seconds. Please see previous posts in this forum for other information, but this information in this post is all up to date.
I’ve gone over all the parameters. I see you’ve switched the format to ERB this time, but the setup looks correct overall. You’re powering the M2 via a power bank at the moment, and you’re still seeing the GPS configuring message, right?
Have you had a chance to reach out to Mission Planner support for more insights on this error? Since the M2 connects to your NTRIP service and gets a FIX in Emlid Flow, the unit itself is working as expected. To be sure, I can check a full system report. Could you send it to [email protected]?
Do you see a Bad GPS Signal Health error? As far as we know, this can happen when the GPS unit outputs coordinates to the autopilot rarer than 5 times per second. Please try increasing the GNSS update rate to 5 Hz or 10 Hz in Emlid Flow. You’ll find this under Settings > GNSS settings.
If this error persists, it might also help to take a quick look at the signal quality. In some cases, nearby electrical interference or limited sky view can also play a role. I’ll need some raw data logs.
Yes, I saw some other forums say that NMEA wasn’t the best, but switching to ERB doesn’t change anything. Yes, I am still powering the Emlid M2 via power bank. All of the lights are on and it looks like it is operating normally from the lights.
So when it says SINGLE in the top right on emlid flow, that means it is receiving corrections? Because in these screenshots it looks like it isn’t receiving anything, just constantly staying on “waiting for corrections.” On this status page, it has never said “receiving corrections” it has always been “waiting for corrections”
So as I was writing this, I tested it out the drone and I do get a 3dgps fix on mission planner without the “GPS2 unhealthy” and “pre-arm barometer” errors, but on my emlid flow app, I am still not receiving corrections like seen in the previous screenshots. Are these screens supposed to be showing that I am receiving corrections or does the SINGLE at the top right indicate it?
But one issue I did run into was the error: “no signal in xx seconds” I think this error is from the slow correction frequency, not sure tho.
Thanks for the system report. I’ve had a look and didn’t spot anything unusual with the M2 itself. It seems to be working fine on the hardware side.
As far as I know, a 3D GPS FIX and an RTK FIX aren’t the same in Mission Planner. I also came across this thread. RTK FIX refers specifically to a fixed RTK solution that uses corrections, while a 3D GPS FIX just means the unit has enough satellites to get a position.
When you see Single in the Status bar of Emlid Flow, it means the M2 is not receiving corrections yet. Once corrections are coming in, this should switch to Float or Fix, depending on the accuracy level. In Mission Planner, do you see any green bars that indicate the laptop is receiving corrections?
You’ve already tried connecting the M2 to the internet and setting the Corrections input to your NTRIP service instead of Serial, right? In that setup, what solution status did you get? If it were Float or Fix, then it’s likely the issue is on the autopilot or Mission Planner side.
Got it. I’ve never seen “RTK FIX” on mission planner before. It’s always been: “3d dgps”
Yes I do see the green bars that indicate the corrections. Okay, when i have the corrections input set to NTRIP, now it says FLOAT in the top right. So I guess the problem has something to do with the communication between my laptop and the M2.
I highly doubt I will receive much help from the mission planner forums on this issue. I’ve tried posting about it, and they get ignored with no response. I guess its because not a lot of people do this. Before I start digging, I wonder if it has to do with my radio telemetry. I don’t know the specifications on what radio to use, but here’s the one I use, and here’s my settings for the radio:
Just going out on a limb here, but could it be the wire I use to connect my radio to my laptop? I’ve just been using an old micro usb cable to go from my laptop USB to the micro usb on the radio. I know that alot of other radios just plug straight into the USB without a cable. Here’s a pic of my radio connection:
Thanks for your patience. It’s been quiet here due to the long holidays. I’ve checked everything on our end, and there doesn’t seem to be an issue with the M2 itself. We’ve tested a similar setup with Pixhawk, Reach base, and M2, and it worked fine. Since your setup is a bit more customized, it’s a bit tricky for us to dig deeper into it.
I noticed from your screenshot that the frequency is slightly different, so I’d suggest adjusting the parameters to match these.
I do have one question about the GPS system though. In that screenshot, I have 2 GPS systems and the RTK is not getting a fix because I have the antennae disconnected. Am i supposed to have 2 GPS working together or is the RTK supposed to be the only one? Also, when I am connected to RTK it says: GPS2: rtk float, is it supposed to say that? Here are my params just incase
Also, some ideas for mounting an antennae would be nice. On the first flight, I had to land the drone because the vibration of the drone unscrews the antennae.
RTK Float means your drone is receiving corrections from the RS2, but it hasn’t resolved all ambiguities yet. So, the accuracy is at the submeter level. This often happens when the antenna isn’t placed properly or if there’s interference from the drone’s electronics. I recommend checking our tips on antenna placement to improve signal quality.
I also noticed GPS: No Fix in your screenshot. That means the GPS is working and ArduPilot sees the data, but the signal quality isn’t good enough. Are you testing under an open sky? GNSS receivers need a clear sky view, without nearby buildings or trees blocking it.
For the two GPS modules, Mission Planner can combine the readings from both. I found this article helpful for understanding how it works. Reach is usually set as the second GPS using the GPS_TYPE2 parameter. Have you tried changing the GPS_AUTO_SWITCH setting? You can also test with only the Reach receiver enabled to see if performance improves.
Back again with some more issues lol. I have everything set up correctly now I think. But my issue now is that the drone loses RTK fix while in flight. If i have the drone on the ground, it will have RTK Fix consistently and never lose. But when I start flying the drone, it loses RTK and switches to 3D fix. It will switch back to RTK fix for a few seconds then switch back to 3D fix.
I thought it was a voltage issue at the beginning, so i got a portable battery and hooked it up to the M2 and it still had the same issue while flying.
I think it might have something to do with interference. I want to get a second opinion though. If it is, does emlid have some kind of mount to mount the antennae on?
I’m no drone expert at all… but seems like it would be more ideal to consolidate the gnss receivers and antennas??? (Save weight too) I.e. replace the M10 with M2 and Emlid LoRa radios setup? Add compass. And also after u figure this all out consolidate your power to main battery also.
Seems the laptop radio setup may be an issue? Not sure how u would handle that. I guess someone with the proper setup can describe the Emlid base / LoRa / laptop passthrough setup sending corrections to the drone from a NTRIP CORS? Or cellular direct from NTRIP CORS service to the drone?