Emlid Reach M2 / M+ / RX (OEM module)
These steps connect an Emlid Reach M2 / M+ / RX (OEM module) to the Premium Positioning correction network over NTRIP, using Emlid Flow / receiver web interface. They assume you already have your NTRIP credentials.
Before you start
Your NTRIP username and password, from your Premium Positioning welcome email or your account on the customer portal.
Emlid Flow / receiver web interface.
A working internet connection on the controller or phone.
A clear view of the sky at the point you are measuring.
Network settings
These are the same for every Premium Positioning customer. Only your username and password are unique to you.
Server or host: rtkpremium.xyz
Port: 2101
Mountpoint: COMMON
Protocol: NTRIP
Steps
Power up and have your credentials ready: Power the Reach module (on an M2/M+ this is usually done by the host system - drone, robot, or rover). Have the NTRIP username and password from your welcome email to hand - you enter your own; they aren't shown here.
Install Emlid Flow and connect to the receiver: Install Emlid Flow (iOS/Android; a desktop version exists too). For a Reach M2/M+, first connect your phone/tablet Wi-Fi to the module's own hotspot - a network named 'reach:XX:XX', password 'emlidreach' - then open Emlid Flow and pick the receiver. For a Reach RX, pair it over Bluetooth in Emlid Flow instead. Wording varies slightly by app/firmware.
Give the module a path to the internet: NTRIP needs internet. Reach M2/M+: in Emlid Flow on the Receivers screen tap 'Wi-Fi', select your local Wi-Fi or phone hotspot (must be 2.4 GHz), enter the password and 'Connect' - the module then has its own internet. Reach RX: it has no Wi-Fi for this; Emlid Flow uses your phone's internet and relays corrections to the RX over Bluetooth, so keep the phone online.
Set the receiver to RTK / Kinematic mode (recommended): In Emlid Flow open the receiver's Settings > 'GNSS settings'. Set Positioning mode to 'Kinematic' for a moving rover. Emlid's recommended starting values are elevation mask ~15° and SNR mask ~35°, all satellite systems enabled, 5 Hz update rate. Adjust to your application.
Open Correction input: From the receiver's settings tap 'Correction input' - where you tell Reach where to fetch corrections. (Depending on firmware this may sit under a 'Reach settings' or 'Settings' group.)
Choose NTRIP as the correction source: Select 'NTRIP', then 'Add profile' to create a new NTRIP connection. You can save multiple profiles and switch on this screen.
Enter the caster address and port: Address (host): rtkpremium.xyz and Port: 2101. Some versions combine them or call the host 'NTRIP server' - enter the same values whichever wording you see.
Enter your NTRIP username and password: Type the NTRIP username/password from your welcome email - unique to your account, exactly as supplied; do not share them.
Select the mount point COMMON: For Mount point, choose or type COMMON. If the app loads the source table, pick COMMON from the list; otherwise type it exactly (uppercase).
Enable position upload if prompted: If you see 'Send receiver's position to the provider' (for VRS/network services), enable it so the caster tailors corrections to your location. If not shown, skip it.
Save and activate the profile: Tap 'Save' and make sure the new profile is selected/enabled on Correction input. Reach connects to rtkpremium.xyz and begins streaming, usually within a few seconds when online.
Take the antenna outside with a clear sky view: RTK needs open sky (~30°+ above the horizon), away from buildings, trees and metal. Indoors or under cover you won't get a fixed solution.
Confirm the solution reaches FIX: Watch the solution status in Emlid Flow (typically top-right) and/or the status LED: SINGLE (~metre) → FLOAT (sub-metre, converging) → FIX (cm-level). FIX means corrections are working - you're ready to survey or fly. If it stays SINGLE/FLOAT, recheck internet, the four NTRIP fields (especially COMMON and credentials), and sky view.
If the fix will not hold
The Reach M2/M+ are OEM modules usually built into a drone/robot/rover, so 'connecting to the module' may mean joining the host system's network; the M2/M+ get internet over their own Wi-Fi joining your network/hotspot, while the Reach RX relies on your phone's internet over Bluetooth. App/web-interface labels can differ between Emlid Flow versions - match by meaning.
For more, see RTK corrections troubleshooting and Fix inconsistent RTK accuracy on site.
Need help
Support is available 24/7. Include your receiver model, the mountpoint, the solution status, and the correction age when you get in touch.
Last updated
Was this helpful?