Losing RTK While in Flight

I’ve got a pixhawk 6x paired with the Emlid M2. While the drone is not flying and on the ground with open view of the sky, the RTK stays connected just fine. While the drone is flying with open view of the sky, it loses RTK As it starts to ascend. The RTK will come in and out while in flight but will never hold for more than 5 seconds.

No, it is not a power issue. I have a separate battery giving 5V to the M2 and it happens with the battery powering it. I think it has something to do with intereference, but im not sure. Also, my antennae setup isnt the greatest, but I cant find anywhere that will correctly mount this kind of antennae. They all seem to be a different mount and cable. Let me know what you guys think. Yes, the antennae is just screwed onto the 3D printed top. It shakes during flight pretty bad. This could also be the problem. If you guys think it is the problem, please send a link to some kind of mount for that antennae.


Where is your LoRa antenna? It needs to be far away from the structure and other electronics.

Here are some better pictures. You can also see the radio in the last picture of my first post in the bottom left corner. My PDB is right behind the radio with all those wires going to it.


Have you tried turning the antenna down? It is on the wrong plane as is. If the antenna is point towards the base it will lose signal. Also, from experience with similar drones even if the antenna is aligned vertically you may also get interference when the frame of drone is in between the antenna and the base.

You have to use a proprietary Emlid LoRa radio.

I have not tried turning it downward. I will test that today.

What is the reason for having to use that radio? I thought it was communicating over the existing telemetry? Does that radio have something different?

Maybe possibly it does work via the existing telemetry? But from what I understand, if using Emlid M2 to Emlid Base (i.e. RS2/R2+, RS3 or M2 with LoRa external) must be Emlid due to proprietary protocols. But you may be correct if it works as a RTCM3 passthrough?

Either way wanted to throw that out there in case radio compatibility is the issue?

Yeah it works just fine when the drone is grounded and not flying. I receive corrections consistently and good quality too. Thats what makes me think that the existing radio is fine.

Curious, what base are you using?

I use NTRIP. So my base is my computer. The computer receives the corrections and sends them via telemtry to the drone. I use Point One Navigation for NTRIP.

That sounds interesting. So your computer has to be perfectly still during a session? Just looking at the picture again - you have a GNSS antenna, visual antenna and LoRa antenna?

Not necessarily. The way NTRIP works is there is large cell towers in the area that are basically a known GPS point serving as a base station. That’s why a lot of people dont use it because if you are in the middle of nowhere, your RTK RMSE is going to be pretty bad. But NTRIP is just temporary for us. So my laptop has a radio connected to it that sends out the missions and corrections via NTRIP to the drone. Yes, moving the computer and radio around decreases telemetry signal, which in turn decreases RTK signal. But the computer is just a middle man, sending the drone corrections based on that cell tower.

I tried pointing the antennae downward while flying. It still is very wishy washy on what the GPS is set at. For our drone, if it is close to the computer and radio, it seems like it always has RTK fixed. Once it starts flying, it is very hard to keep RTK Fixed. You basically have to stay within 20ft of it. My telemetry signal according to my FC is good, but it still loses RTK sometimes.

I’m guessing the incompatible non-Emlid LoRa radios may be the issue… they may connect temporarily but not 100%. So Emlid can help, might be a good idea to state the radios you are using, both on the drone and the laptop.

Also, the excessive vibration at the M2 antenna might not be ideal also on a side note. May need to damper it.

After some reading, sounds like your telemetry setup is correct. If M2 rover to M2 base, must use Emlid LoRa radios, but your flight controller is passing the GNSS corrections through.

Maybe temporarily try mounting the helical antenna to a mast up and away from the electronics etc that may be causing interference and also mount a circular aluminum ground plane to the bottom of antenna to help with multi-path issues. I hear the helical doesn’t really need one, but you can try if it helps in addition to the mast.

Try another CORS base?

Or even another M2 / ANTENNA with Emlid LoRa radios or a RS2/+/3 for your own base?

Hi @truettjkerby,

Sorry for the radio silence here.

So, did I understand correctly that your setup looks like this?

NTRIP → Ground Control Station → Inject the corrections to M2 via telemetry

Could you please record the raw data logs before and during the flight? I need the RINEX, UBX, and LLH logs from the M2 and the incoming corrections in RTCM3. After that, please generate the Full System Report as well.

This will help us get a clearer picture of what’s happening during the flight. Thanks!

Just DM’d you the raw data logs and full system report.

From what I understand, the Emlid M2 is based on the ZED-F9P chip.

You can perform the test using the u-center software available at https://content.u-blox.com/sites/default/files/2025-06/u-center_v25.06_installer.zip. This software is installed on a laptop.

This software recognizes the receiver connected via USB as a COM port, e.g., COM3. RTK is set in the Receiver->NTRIP Client menu.

Set View→Configuration View→ NAV5→DGNSS Timeout=3→Click send

If the receiver has problems receiving RTK data, a message will appear at the bottom of the window informing you that the NTRIP connection has been lost.

If you continue to lose the FIXED status in RTK, there is a problem with the signal quality being received from the satellites. In this case, setting the SNR mask in the View menu→Configuration View→NAV5→dbHz=30→Click send may help.

If you want to save the configuration permanently, select View→Configuration View→Cfg→Save configuration→ Click Send