Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Inertial Labs RESEPI RTK Setup: NTRIP for LiDAR Payloads

Stream RTKdata corrections into Inertial Labs RESEPI and Teledyne EchoONE LiDAR payloads: USB LTE modem, NTRIP Client, AUTO mountpoint, lever arm, fix check.

The Inertial Labs RESEPI payloads (GEN-II M2X-ILX and OS1-ILX, LITE, Ultra LITE) and the Teledyne EchoONE, which Inertial Labs lists as "Powered by Inertial Labs RESEPI GEN-II", are LiDAR payloads for drones; RESEPI payloads are also used on vehicles and backpacks. Each payload has its own GNSS receiver, INS and NTRIP client, so RESEPI RTK with RTKdata is set up in the payload's web GUI, not in the drone. The payload needs its own internet connection, usually a USB LTE modem, and it sends its position back to the caster, which lets the RTKdata AUTO mountpoint pick the nearest reference station. RESEPI is also built into partner-branded payloads that can carry other names and labels; where your payload shows the same web GUI with an RTCM corrections block, this guide applies. For other scanners and payloads, see the LiDAR scanner guides.

RTKdata values for the RTCM corrections block. Choose the server closest to your work area. All three servers share the same reference station network; the difference is routing latency, see Network & Mountpoints.

Field
Value

Connection

NTRIP Client

Caster, North America

rtk.rtkdata.com, IP fallback 13.56.117.10

Caster, Europe

eu.rtkdata.com, IP fallback 3.73.41.96

Caster, Australia

aus.rtkdata.com, IP fallback 54.206.56.130

Port

2101

User

Username from RTK Credentials in your account dashboard. It starts with rtk and is not your website login

Password

Password from RTK Credentials, not your website password

Mount point

AUTO in capitals (alternatives: AUTO_ITRF2020, AUTO_ITRF2014, AUTO_WGS84)

Caster is a free text field, and Inertial Labs does not document whether it takes a hostname, an IP address or both. Enter the hostname of your server first. Switch to the IP fallback of the same server only if the Status page shows no base block (Base Lon, Lat, Alt, Hgt) after you have checked credentials and mountpoint.

  • Connection: NTRIP Client

  • Host (domain): rtk.rtkdata.com, into Caster

  • Host (IP fallback): 13.56.117.10, into Caster only if the hostname is not accepted (no base block on the Status page)

  • Port: 2101, into Port

  • Username / Password: From RTK Credentials in your account dashboard, not your website login, into User and Password

  • Mountpoint (ALL CAPS): AUTO (recommended), or AUTO_ITRF2020, AUTO_ITRF2014, AUTO_WGS84, into Mount point

  • Connection: NTRIP Client

  • Host (domain): eu.rtkdata.com, into Caster

  • Host (IP fallback): 3.73.41.96, into Caster only if the hostname is not accepted (no base block on the Status page)

  • Port: 2101, into Port

  • Username / Password: From RTK Credentials in your account dashboard, not your website login, into User and Password

  • Mountpoint (ALL CAPS): AUTO (recommended), or AUTO_ITRF2020, AUTO_ITRF2014, AUTO_WGS84, into Mount point

  • Connection: NTRIP Client

  • Host (domain): aus.rtkdata.com, into Caster

  • Host (IP fallback): 54.206.56.130, into Caster only if the hostname is not accepted (no base block on the Status page)

  • Port: 2101, into Port

  • Username / Password: From RTK Credentials in your account dashboard, not your website login, into User and Password

  • Mountpoint (ALL CAPS): AUTO (recommended), or AUTO_ITRF2020, AUTO_ITRF2014, AUTO_WGS84, into Mount point

The drone's RTK does not reach the payload. RESEPI and EchoONE have their own GNSS receiver. RTK set up in the drone's controller or ground station positions only the drone. The payload receives corrections only through the RTCM corrections block in its own web GUI. For network RTK on the drone itself, for example on the DJI M350 RTK that Teledyne names as the carrier for EchoONE, see the DJI Matrice 300 / 350 / M30T guide.

Does a RESEPI payload use the drone's RTK corrections?

An Inertial Labs RESEPI or Teledyne EchoONE payload does not use the drone's RTK corrections: it computes its position with its own GNSS receiver and INS and takes RTKdata corrections only through the RTCM corrections block of its web GUI.

  • Network RTK in the drone controller, for example on the DJI M350 RTK that Teledyne names as the carrier for EchoONE, positions the drone. It does not feed the payload.

  • Inertial Labs documents four inputs in the RTCM corrections block: USB RF Modem, NTRIP Client, TCP Connect and TCP Listen. For RTKdata, use NTRIP Client.

  • The MAVLink messages that GEN-II and EchoONE support carry status and trigger data, no RTCM corrections.

If NTRIP is set up only in the drone app, the point cloud is georeferenced without corrections on the payload.

What do you need for RESEPI RTK over NTRIP?

Real-time RTK on an Inertial Labs RESEPI payload needs a unit that Inertial Labs has configured for RTK corrections, an internet connection on the payload itself, a GNSS antenna on the PRI port and RTKdata NTRIP credentials.

  • RTK-enabled payload. Inertial Labs states that RTK over a modem is "only available for specifically configured hardware", and its RTK workflow is meant for payloads bought with the RTK Bundle, which "includes a RTK modem and RESEPI configured to accept RTK corrections". If you are not sure about your unit, check with Inertial Labs support and give them the serial number.

  • USB LTE modem with an active data SIM. If you have the RTK Bundle, use the modem that came with it. Otherwise Inertial Labs recommends the ZTE MF833V. The SIM is not included.

  • A free USB port. RESEPI LITE needs two ports, one for the USB drive that stores the recording and one for the modem; an attached camera can occupy a port. GEN-II and EchoONE have one USB-A port at the front; GEN-II also has an internal 512 GB SSD. If the Status page shows Plug in USB storage to enable recording, recording is set to a USB drive. Where to change this is not described in the public Inertial Labs documentation, so ask Inertial Labs support, or use a standard USB hub for the drive and the modem, which the RESEPI user manual allows when ports run short. Do firmware updates and data transfer, which also use the USB-A port, before you plug in the modem or after the flight.

  • GNSS antenna connected to PRI, with a clear view of the sky.

  • Browser on a laptop, tablet or phone. The GUI runs in the browser, no app is needed.

  • RTKdata account with active RTK credentials (username starts with rtk).

  • RTK coverage in the survey area, checked on the coverage map before the flight.

  • Measured lever arm from the IMU to the antenna, in meters.

  • PCMasterProGL for processing. EchoONE needs version 1.14.2 or newer.

Internet on the payload

The RESEPI GUI has no field for an APN or a SIM PIN, so prepare the modem before it goes into the payload:

  1. Insert the SIM into the stick and connect the stick to a computer. Open the stick's web interface (on the MF833V usually m.home or 192.168.0.1) and set your carrier's APN under Settings > Network Settings > APN.

  2. Disable the SIM PIN beforehand, for example in a phone.

  3. Some MF833V variants are locked to one carrier. Use a stick that works with your SIM.

The alternative is an external Wi-Fi network such as a phone hotspot, which the RESEPI manual lists as a way to supply corrections. Enter it in Settings > Connectivity > Wireless network under SSID RESEPI will search for and Passphrase for that network (WPA or WPA2 Personal only). The payload then gets its address from that network and is no longer reachable at 192.168.12.1; look the address up on the hotspot. To return to the payload's own network, use Clear, Save and Apply, or plug in a USB drive with an empty file named wifi-reset.

Don't have an RTKdata.com account yet? 👉 Start 30-day Free Trial or View Pricing

How do you enter RTKdata in the RESEPI web GUI?

RTKdata goes into the RESEPI web GUI under Settings > Connectivity > RTCM corrections: set Connection to NTRIP Client, fill in Caster (rtk.rtkdata.com, eu.rtkdata.com or aus.rtkdata.com), Port 2101, User and Password from RTK Credentials and Mount point AUTO, and click Save.

Inertial Labs uses two GUI generations: an older blue GUI and a newer black and red GUI on GEN-II and EchoONE. The manufacturer screenshots of the RTCM corrections block show the blue GUI, so labels in the newer GUI may differ.

EchoONE: Teledyne's EchoONE user manual describes only PPK. The Inertial Labs page "Settings Menu Tab - GEN-II and EchoONE" documents the same RTCM corrections block for EchoONE, so the steps below apply.

1

Prepare the payload outdoors

  1. Plug the prepared LTE modem into a free USB port. On GEN-II and EchoONE, do any firmware update first, because it uses the same USB-A port.

  2. Connect the GNSS antenna to PRI.

  3. Power on the payload outdoors with a clear view of the sky.

  4. Wait until the payload has time and a GNSS solution. While GNSS Solution shows INSUFFICIENT OBSERVATIONS,OTHER (blue GUI) or no solution (newer GUI), the payload has no position of its own yet.

2

Open the web GUI

  1. Join the payload's Wi-Fi: RESEPI- followed by six characters, the last six characters of the IMU's MAC address. Password: LidarAndINS.

  2. Open 192.168.12.1 in the browser.

  3. GEN-II and EchoONE can also be reached over Ethernet at 192.168.13.1. Inertial Labs advises against connecting barrel power and Ethernet at the same time.

Partner-branded payloads can use a different network name.

3

Select NTRIP Client

  1. Open the Settings tab, then Connectivity. It has two blocks: Wireless network and RTCM corrections.

  2. In RTCM corrections, set Connection to NTRIP Client before you type anything. The block then shows only the five NTRIP fields.

Do not choose USB RF Modem for an LTE stick. Inertial Labs describes that option as "USB RF Modem like Holybro 915MHz", a radio modem for your own base. The LTE stick only provides internet; the corrections still come through NTRIP Client.

4

Enter the RTKdata values and save

  1. Caster: the hostname of your server, rtk.rtkdata.com, eu.rtkdata.com or aus.rtkdata.com (IP fallback in the tabs above)

  2. Port: 2101

  3. User: your RTKdata username, starting with rtk

  4. Password: your RTKdata NTRIP password

  5. Mount point: AUTO

  6. Click Save before you reload the page. Restore discards unsaved changes.

After Save, the payload starts connecting and, according to Inertial Labs, "will keep trying to connect to the specified address until it succeeds".

  • Type the credentials instead of pasting them, with no spaces at the start or end.

  • Type the mountpoint exactly. RESEPI has no sourcetable lookup, so there is no list to pick from. AUTO is written in capitals. A local coordinate system name is not a mountpoint and returns no corrections.

  • One set of credentials allows one connection at a time. Every device connected at the same time needs its own data stream, see Account & Credentials.

Position (GGA): AUTO picks the reference station from the payload's position, which the payload sends as NMEA GGA. Without GGA the login succeeds, but no corrections arrive and the base block stays empty, see NTRIP & GGA Essentials. RESEPI sends GGA without a setting: the GUI states that "RESEPI sends back GPGGA messages with its current position for virtual reference stations". What the payload sends before it has its own solution is not documented, so power on outdoors, wait for a GNSS solution and only then save the NTRIP settings.

The RTKdata sourcetable loads without a login. A mountpoint list that you see in a browser or another NTRIP app proves neither your credentials nor a correction stream (checked on 25 September 2026). On RESEPI, the documented proof is the base block on the Status page.

5

Enter the lever arm

  1. Open Settings > Geometry > IMU to Antenna Offset.

  2. Enter the measured offset in meters in Right, Forward and Up, then click Save. Reset reverts the values.

  3. Reload the page and check the values.

Inertial Labs says to measure from the IMU to the antenna center, using the orientation references in its documentation, and to adjust for an antenna that sits left of, behind or below the unit. Check the signs against that orientation drawing. The RTK checklist calls the values X, Y and Z; the GUI labels them Right, Forward and Up.

In RTK mode the lever arm is not estimated, so missing or wrong values shift the trajectory even with a fix. According to Inertial Labs, the two Aerial options and Pedestrian under Recording Profile on the Status page carry a primary antenna offset of 0, 0, 0, and MMS carries its own preset values, so applying a standard profile after this step can replace your values. Store your values with Save to Custom and use the Custom profile.

6

Check the recording settings

On the Status page:

  • Record without GNSS: Off. The GUI warns: "If Record without GNSS is enabled, PCMasterPro will not be able to process the data". Click Save.

  • SLAM Settings (RESEPI with SLAM, not EchoONE): no indoor configuration under Current selected SLAM configuration, because an indoor configuration turns off georeferencing.

Under Settings > INS Service, set the secondary antenna data option (Include secondary range data on LITE) to Off when only one GNSS antenna is connected, then click Save.

How do you confirm corrections and fix before takeoff?

A RESEPI payload receives RTKdata corrections when the Status page shows the base block with Base Lon, Lat, Alt and Hgt, and it has an RTK fix when GNSS Solution reads COMPUTED,NARROW INTEGER in the blue GUI or shows Lat STD, Lon STD and Alt STD at centimeter level in the newer GUI.

  • Corrections arrive: the base block appears on the Status page. If it is missing, work through the table below.

  • RTK fix, blue GUI: GNSS Solution shows COMPUTED,NARROW INTEGER. COMPUTED,NARROW FLOAT is only float. Inertial Labs accepts float as the minimum for RTK; we recommend starting the recording only at COMPUTED,NARROW INTEGER.

  • RTK fix, newer GUI: GNSS Solution is shown as plain text. No manufacturer screenshot shows the fixed wording yet, so also wait for Lat STD, Lon STD and Alt STD at centimeter level.

  • GNSS LED: orange on GEN-II and EchoONE means only that "RTK differential corrections are being received". It does not show a fix.

Inertial Labs documents no error message for wrong credentials or a wrong mountpoint, so the base block is the check that counts.

If the base block does not appear

Problem
Cause
Fix

No base block, Connection shows USB RF Modem

Wrong correction input

Select NTRIP Client, enter the values again, click Save

No base block, settings look right

Modem has no data connection (SIM PIN, missing APN, carrier-locked stick)

Set up the stick on a computer or phone, then plug it in again

No base block

Typo or extra space in User, Password or Mount point

Retype the credentials from RTK Credentials and AUTO in capitals

No base block, GNSS Solution shows INSUFFICIENT OBSERVATIONS,OTHER or no solution

No GNSS solution yet, so there is no position for AUTO to pick a reference station

Keep the payload under open sky until it has a GNSS solution, then check the base block again

No base block after all checks above

Caster may not accept the hostname

Enter the IP fallback of your server from the tabs above (13.56.117.10, 3.73.41.96 or 54.206.56.130), port 2101

Values are gone after a reload

Page reloaded before Save

Enter the values again, click Save, then reload and check

Base block visible, solution stays COMPUTED,NARROW FLOAT

Solution not converged, sky view blocked

Keep the payload under open sky and wait; start recording only at COMPUTED,NARROW INTEGER

Base block comes and goes

Another device uses the same credentials at the same time

Disconnect the other device or add a data stream, see Account & Credentials

GUI unreachable at 192.168.12.1

Payload has joined an external Wi-Fi network

Look up its address on the hotspot, or reset with a wifi-reset file on a USB drive

For connection problems that are not specific to RESEPI, see Common Connection Issues.

During the flight

Inertial Labs' RTK mission procedure:

  1. Start the recording with Start under Data recording or with the power button.

  2. Keep the payload static for 30 to 60 seconds.

  3. After the climb, fly sideways at 5 m/s or faster for 5 seconds, then fly a figure eight. The Status page shows INS: Waiting for high velocity until the payload has moved at 4 m/s for 4 seconds.

  4. Corrections have to arrive for the whole flight. Check LTE coverage in the survey area beforehand and watch for dropouts. If corrections drop out, only PPK can rescue the dataset, which needs the Inertial Explorer license and separate base station data.

How do you process the RTK trajectory in PCMasterPro?

RESEPI RTK trajectories recorded with RTKdata corrections are processed in PCMasterProGL by opening the flight's rtk.pcmp file, which needs no Inertial Explorer license, while PPK processing with ppk.pcmp needs that license.

  1. Copy the flight folder to your computer.

  2. Open rtk.pcmp in PCMasterProGL.

  3. Right-click the trajectory and use Start selection here and Finish selection here to select the scan section.

  4. Export with File > Export LAS File(s).

  • Inertial Labs states that the RTK workflow "may result in lower quality results" and gives a usable result only if the payload received corrections during the recording.

  • The command-line version PCMasterProCL requires an "active embedded Inertial License" also for RTK datasets.

  • One-click processing outputs WGS84 by default and shows no intermediate results. For the first jobs, open rtk.pcmp in the GUI workflow and check Current Model.

Current app version when this page was written: PCMasterProGL, not public (September 2026). Current PCMasterProGL releases, payload firmware and release notes are behind the Inertial Labs login, so this page names no current version. The minimum for EchoONE named in the Teledyne EchoONE user manual (Rev A) is PCMasterProGL 1.14.2.

Which coordinate system do the exported point clouds use?

RESEPI point clouds exported from PCMasterPro are labeled WGS 84 / UTM with ellipsoidal heights by default, while the RTK positions computed with the RTKdata AUTO mountpoint are, according to NovAtel for its receivers, in the datum of the corrections, for example NAD83(2011) in the USA; check against ground control points.

  • PCMasterPro: "By default, PCMasterPro projects point clouds using the WGS 84 ellipsoid and UTM coordinate system", shown as Current Model H-EPSG:<zone> + V-EPSG:5030, where 5030 stands for ellipsoidal height.

  • NovAtel, the GNSS receiver in the GEN-II M2X-ILX and the Ultra LITE, documents that an RTK solution is reported as WGS84, but "the position solution is in the same datum as the base station". Inertial Labs does not state this for the RESEPI trajectory explicitly, so check the result against ground control points.

Datum with AUTO. AUTO delivers corrections in your region's datum, for example NAD83(2011) in the USA, NAD83(CSRS)v7 in Canada, ETRS89 (realization ETRF2000) in Europe and GDA2020 in Australia. Where no regional datum is listed, it falls back to WGS84(G2139) at the mid-year epoch. The datum and epoch for every country are listed in Coordinate Systems & Datums.

  • Treat the WGS 84 / UTM label as the regional datum that AUTO delivered. Assign the regional CRS, for example when you import the LAS files, instead of transforming from WGS 84, and check against ground control points.

  • Canada: assign NAD83(CSRS). Do not reproject from WGS 84.

  • AUTO_ITRF2020 and AUTO_ITRF2014 deliver ITRF2020 and ITRF2014 at the current epoch, and AUTO_WGS84 delivers WGS84(G2139) at the mid-year epoch. Use them only when the result stays in a global frame. For deliveries in a regional datum, use AUTO.

  • Heights: choose your national height system under New Vertical Model and put the matching PROJ grid file (.tif) into the PCMasterPro /proj folder. Canada: whether New Vertical Model also transforms from WGS 84 is not documented. Apply the geoid after NAD83(CSRS) has been assigned, in software where you set the CRS yourself, and check heights against ground control points.

  • Coordinate dialog: ribbon Survey Tools > Coordinates Selection (the documentation still says Tools > Coordinates Menu) opens Available Coordinates with New Horizontal Model, New Vertical Model and Reproject. Converted trajectories are written to the convertedTrajectories folder.

  • Other software: point cloud software can take the WGS 84 / UTM label over automatically on import, so set the CRS explicitly.

  • Ground control points: SurveyPro Tools (separate license) expects GCPs as "Easting, Northing, Ellipsoidal Height" and "does not convert units or coordinate systems", so deliver them in the same system and units.

Heights are ellipsoidal, not heights above sea level. See Understanding Heights for applying a geoid. For datum and height handling of point clouds across scanners and payloads, see Georeferencing SLAM Scans.

Frequently asked questions

How do I set up NTRIP corrections on an Inertial Labs RESEPI LiDAR payload?

Plug a USB LTE modem with an active data SIM into the RESEPI payload, join its Wi-Fi, open 192.168.12.1 and go to Settings > Connectivity > RTCM corrections. Set Connection to NTRIP Client, enter the RTKdata hostname for your region in Caster (rtk.rtkdata.com, eu.rtkdata.com or aus.rtkdata.com, IP fallback only if no base block appears), Port 2101, your RTKdata User and Password and Mount point AUTO, click Save and wait for the base block and a fix on the Status page.

Does a RESEPI payload use the DJI drone's RTK corrections?

A RESEPI or EchoONE payload does not use the DJI drone's RTK corrections, because it has its own GNSS receiver and takes RTKdata corrections only through the RTCM corrections block of its web GUI. RTK in the DJI controller positions the drone, so the RTKdata values (Caster, Port 2101, Mount point AUTO) have to be entered in the payload separately.

Which modem do I need for real-time RTK on RESEPI?

Inertial Labs recommends the ZTE MF833V USB LTE stick with an active data SIM for real-time RTK on RESEPI, unless the payload came with the RTK Bundle, which includes an RTK modem; the SIM is not included. Set the APN and disable the SIM PIN before the stick goes into the payload, because the RESEPI GUI has no field for either. An external Wi-Fi network such as a phone hotspot, entered under SSID RESEPI will search for, is the documented alternative. The modem only provides internet; the RTKdata corrections come in through Connection NTRIP Client.

Does Teledyne EchoONE support NTRIP corrections?

Teledyne EchoONE takes RTKdata NTRIP corrections through the same RTCM corrections block as RESEPI GEN-II, according to the Inertial Labs page "Settings Menu Tab - GEN-II and EchoONE": Connection NTRIP Client, your regional RTKdata host in Caster, Port 2101, Mount point AUTO. Teledyne's own EchoONE manual describes only PPK. EchoONE data is processed in PCMasterProGL 1.14.2 or newer.

What does USB RF Modem mean in the RESEPI settings?

USB RF Modem is the RESEPI correction input for a radio modem, which Inertial Labs describes as "USB RF Modem like Holybro 915MHz". It is not the setting for a USB LTE stick: with an LTE stick or a hotspot, set Connection to NTRIP Client and enter the RTKdata values there.

Why does the RESEPI Status page show no base block with RTKdata?

RESEPI shows no documented error message for a failed NTRIP login: after Save it keeps trying to connect until it succeeds, so a missing base block (Base Lon, Lat, Alt, Hgt) on the Status page is the sign that RTKdata corrections are not arriving. Check in this order: Connection is set to NTRIP Client, not USB RF Modem; the LTE stick has a data connection (APN set, SIM PIN off); User, Password and Mount point AUTO are typed without extra spaces; GNSS Solution shows a solution, so the payload can send its GGA position; then enter the IP fallback of your RTKdata server in Caster; finally make sure no other device uses the same credentials at the same time.

Quick reference

  1. USB LTE modem with data SIM (APN set, PIN off) in a free USB port, antenna on PRI, power on outdoors, wait for a GNSS solution.

  2. Wi-Fi RESEPI- plus six characters, password LidarAndINS, open 192.168.12.1, Settings > Connectivity > RTCM corrections, Connection = NTRIP Client.

  3. Caster rtk.rtkdata.com (North America), eu.rtkdata.com (Europe) or aus.rtkdata.com (Australia), IP fallback 13.56.117.10, 3.73.41.96 or 54.206.56.130, Port 2101, User and Password from RTK Credentials, Mount point AUTO, Save.

  4. IMU to Antenna Offset measured, Record without GNSS Off, base block visible and COMPUTED,NARROW INTEGER (newer GUI: STD values at centimeter level) before recording.

  5. Process rtk.pcmp in PCMasterProGL, assign the regional CRS that AUTO delivered to the WGS 84 / UTM output, heights are ellipsoidal.

Related Guides

PreviousEmesent Hovermap RTK
NextGeoSun GS-200G / GS-100G

Last updated

Was this helpful?