> For the complete documentation index, see [llms.txt](https://docs.rtkdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rtkdata.com/integration-hub/lidar-scanners-and-mobile-mapping/3dmakerpro-eagle-raven.md).

# 3DMakerpro Eagle RTK & Raven RTK Setup with NTRIP

Set up 3DMakerpro Eagle RTK and Raven Max RTK with NTRIP: phone hotspot, GPS screen with RTKdata host, AUTO in capitals and RTK Calibration in RayStudio.

The **3DMakerpro Eagle RTK** (Eagle Standard or Eagle Max with the factory RTK module) and the **Raven** with RTK are handheld SLAM LiDAR scanners with a built-in NTRIP client: you enter RTKdata on the scanner's **GPS** screen, the scanner goes online through a phone hotspot or Wi-Fi network, and the scan is georeferenced afterwards in **RayStudio** for Windows with **RTK Calibration**. The RayStudio manual describes this workflow for a third-party RTK service with a domain name, port, username and password. The **Hawk** with its RTK kit uses the same **GPS** screen.

Choose the RTKdata server closest to your work area. All three servers share the same reference station network; the difference is routing latency (see [NTRIP Server Settings](/get-started/network.md)). Select the tab for your region:

{% tabs %}
{% tab title="North America" %}

* **Host (domain):** `rtk.rtkdata.com`, entered in **Address**
* **Host (IP fallback):** `13.56.117.10`, in **Address** only if the hostname does not connect
* **Port:** `2101`, entered in **Port**
* **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login, entered in **Username** and **Password**
* **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, entered in **Mount Point**
  {% endtab %}

{% tab title="Europe" %}

* **Host (domain):** `eu.rtkdata.com`, entered in **Address**
* **Host (IP fallback):** `3.73.41.96`, in **Address** only if the hostname does not connect
* **Port:** `2101`, entered in **Port**
* **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login, entered in **Username** and **Password**
* **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, entered in **Mount Point**
  {% endtab %}

{% tab title="Australia" %}

* **Host (domain):** `aus.rtkdata.com`, entered in **Address**
* **Host (IP fallback):** `54.206.56.130`, in **Address** only if the hostname does not connect
* **Port:** `2101`, entered in **Port**
* **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login, entered in **Username** and **Password**
* **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, entered in **Mount Point**
  {% endtab %}
  {% endtabs %}

All values for the scanner's **GPS** screen at a glance:

| Field                       | Value                                                                                                                                                                       |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Address**                 | North America `rtk.rtkdata.com` (IP fallback `13.56.117.10`), Europe `eu.rtkdata.com` (IP fallback `3.73.41.96`), Australia `aus.rtkdata.com` (IP fallback `54.206.56.130`) |
| **Port**                    | `2101`                                                                                                                                                                      |
| **Username**                | From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/). Starts with `rtk`, not your website login                              |
| **Password**                | From *RTK Credentials*, not your website password                                                                                                                           |
| **Mount Point**             | `AUTO` in capital letters (alternatives: `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84`)                                                                                    |
| **Connect GPS** and **RTK** | Both on                                                                                                                                                                     |
| GGA (position)              | No setting on the **GPS** screen. `AUTO` needs the scanner's position, so create and start the project under open sky                                                       |

## Requirements

* **Eagle Standard or Eagle Max with the factory-installed RTK module**, a **Raven Max RTK**, or a **Raven or Raven Max with the RTK Antenna & Signal Module for Raven Series**
* **External GPS antenna** from the RTK kit, mounted on the scanner
* **RTK firmware**: on the Eagle, the RTK line for your model (**Eagle Standard with RTK** 2.1.6r or **Eagle Max with RTK** 1.1.6r)
* **Phone hotspot or Wi-Fi network** on site. The specification lists only Wi-Fi 5 as network support, with no SIM slot or mobile data documented
* **Windows 10 or 11 PC (64-bit)** with **RayStudio 1.0.13**. RayStudio for Windows does not run on macOS
* **RTKdata account** with active RTK credentials (username starts with `rtk`)
* **RTKdata coverage** at your site. Check the [Coverage Map](/get-started/coverage-map.md) before the field day
* **Open sky** where you create and start the project

{% hint style="info" %}
Don't have an RTKdata.com account yet? 👉 [Start 30-day Free Trial](https://rtkdata.com/try-rtk-corrections-free-for-30-days/) or [View Pricing](https://rtkdata.com/pricing/)
{% endhint %}

## Which Eagle and Raven models support RTK?

The 3DMakerpro Eagle Standard or Eagle Max with the factory-installed RTK module, the Raven Max RTK and a Raven or Raven Max with the RTK Antenna & Signal Module for Raven Series have the NTRIP client that takes RTKdata connection details. An Eagle ordered without the module and a Raven Standard without the module have no RTK hardware.

| Model                                                                           | RTK hardware                                                   | Note                                                                                               |
| ------------------------------------------------------------------------------- | -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Eagle Standard (1x camera) or Eagle Max (4x camera), variant **Add RTK Module** | RTK antenna and signal module installed at the factory         | According to the 3DMakerpro shop FAQ, the module can no longer be added once the Eagle has shipped |
| Raven Max RTK                                                                   | RTK module installed at the factory in the side compartment    | Antenna on the top interface                                                                       |
| Raven or Raven Max                                                              | **RTK Antenna & Signal Module for Raven Series**, fitted later | Sold separately by 3DMakerpro; check availability in your region with 3DMakerpro                   |
| Raven Standard without the module                                               | None                                                           | No GPS, even if older firmware shows the GPS settings                                              |
| Hawk with RTK kit                                                               | External GPS from the kit                                      | Same **GPS** screen as the Eagle                                                                   |

{% hint style="info" %}
**No base station of your own and no radio link are needed.** The Eagle product FAQ describes the RTK accessory with a base station and wireless communication on L1 (1575.42 MHz) and L2 (1227.60 MHz). Those are the GPS satellite frequencies the antenna tracks. RTKdata delivers corrections over NTRIP, so the scanner needs the internet connection you set up in **Link Hotspots**, and the **GPS** screen only takes NTRIP details.
{% endhint %}

### Mount the antenna

* **Eagle:** remove the **GPS Lid** and screw the external GPS antenna onto the **GPS Interface**.
* **Raven:** remove the **Antenna Cover** and screw the antenna onto the top interface.
* **Raven retrofit:** the Expansion Kit manual describes the installation. Open the **Side panel**, loosen the screws, insert the chip wearing the supplied anti-static finger cots, plug the cable into the red socket above or below the chip, screw everything back, close the side panel and mount the antenna.

### Update firmware and RayStudio before the field day

1. **Eagle:** download only the RTK line for your model, **Eagle Standard with RTK** 2.1.6r or **Eagle Max with RTK** 1.1.6r (both released on 22 July 2026), from the [Eagle firmware list](https://forum.jimumeta.com/home/help/download2.html?id=89ce7b9ffff54351bd89dc31c66253f4) on 3DMakerpro's JMMeta support site. The download can require a JMMeta account, so do it before the field day.
2. Copy the file to a USB stick, into a folder named `upgrade` that you create yourself.
3. On the scanner, open **Settings** > **Version** (Eagle manual) or **New Version** (Raven manual and newer screens) and tap **Update Now**.
4. Update with a full battery and do not interrupt the update.
5. Afterwards, check that the **GPS** screen shows **RTK**, **Address** and **Mount Point**.
6. Install **RayStudio 1.0.13** on the Windows PC.

**Raven:** 3DMakerpro publishes no firmware list for the Raven. Ask 3DMakerpro support which firmware your Raven needs for NTRIP.

{% hint style="warning" %}
**Load the right Eagle firmware line.** All Eagle firmware files are named `Rayzoom_G100`, for the Standard and the Max, with and without RTK. Owners who installed Eagle Standard firmware on an Eagle Max report that only the front camera worked afterwards, with no published fix. In one forum report, an interrupted update left an Eagle showing only the logo.
{% endhint %}

Current app version when this page was written: RayStudio 1.0.13 (September 2026).

## How does the scanner get internet for NTRIP?

On a 3DMakerpro Eagle or Raven, the NTRIP connection to RTKdata goes over Wi-Fi: the scanner joins a phone hotspot or a site Wi-Fi network through **Settings** > **Hotspot Links** > **Link Hotspots**, and its specification lists only Wi-Fi 5 as network support, with no SIM slot or mobile data documented.

Prepare the phone first:

* Give the hotspot a **short name** and a simple password with at least 8 characters. Both are typed on the scanner's on-screen keyboard.
* **iPhone:** in **Personal Hotspot**, turn on **Maximize Compatibility** and stay on that screen until the scanner has connected.

Then connect the scanner, ideally in the shade, because the display is hard to read in direct sunlight:

1. On the **Scans** home screen, tap the settings icon at the bottom left and open **Settings** > **Hotspot Links**.
2. Turn on **Link Hotspots**. Leave **Activate Hotspot** off.
3. Type the hotspot name in **Please Enter SSID** and the password in **Please Enter Password**.
4. Tap **Connect**. The scanner is online when the button shows **Disconnect**.

The firmware in 3DMakerpro's tutorial video writes some of these labels in lower case (**Link hotspots**, **Please enter SSID**), and 3DMakerpro's Raven guide describes selecting the Wi-Fi network from a list.

{% hint style="info" %}
**Activate Hotspot** makes the scanner itself a hotspot for RayStudio Mobile and data transfer. RayStudio Mobile has no NTRIP settings, and 3DMakerpro does not document whether both hotspot modes can run at the same time. For RTK scans, operate the scanner on its own screen.
{% endhint %}

## How do you set up 3DMakerpro Eagle RTK on the GPS screen?

On a 3DMakerpro Eagle or Raven, connect the scanner to the internet in **Link Hotspots** first, then enter RTKdata on the **GPS** screen of the project dialog: turn on **Connect GPS** and **RTK**, enter `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia) in **Address**, port `2101`, your RTKdata credentials and `AUTO` in capital letters in **Mount Point**, then tap **Save**.

{% stepper %}
{% step %}

### Create a project outdoors

Go outside under open sky. On the **Scans** home screen, tap **Scan** (Eagle) or **Start** (Raven). The project dialog shows **Project Name**, **Camera Settings** and **Acquisition Mode**.
{% endstep %}

{% step %}

### Open the GPS screen

In the project dialog, tap **Connect GPS**. Newer firmware labels this entry **GPS**. The **GPS** screen opens.
{% endstep %}

{% step %}

### Enter the RTKdata details

1. **Connect GPS**: on
2. **RTK**: on. The connection fields are only used with RTK on.
3. **Address**: the hostname for your region, `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia)
4. **Port**: `2101`
5. **Username** and **Password**: your RTK credentials. Type them on the scanner's on-screen keyboard exactly as shown in *RTK Credentials*, with no space at the start or end. Credentials are case sensitive.
6. **Mount Point**: `AUTO` in capital letters. If the field shows the preset `Auto`, change it to `AUTO`.

**Address** takes a hostname: 3DMakerpro's tutorial video enters a hostname in this field, and the RayStudio manual asks for the service's domain name. Enter the hostname first and use the IP fallback from your region's tab only if the hostname does not connect.

A 3DMakerpro distributor suggests tapping **Connect GPS** after typing to close the keyboard. Then check every value in the shade, including that **Connect GPS** and **RTK** are still on. One set of credentials serves one connected device at a time, see [Account & NTRIP Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices).
{% endstep %}

{% step %}

### Save

Tap **Save**. In 3DMakerpro's video the scanner then shows **Connect success!**. According to a 3DMakerpro distributor, the values stay stored on the scanner.

{% hint style="warning" %}
**Connect success! is not an RTK fix.** 3DMakerpro documents no RTK status display during the scan. Check the export and the RayStudio result instead, as described below.
{% endhint %}
{% endstep %}

{% step %}

### Start the scan and wait for GPS

Tap **Save** in the project dialog. What follows depends on the firmware:

* Eagle manual V1.6 and Raven manual V1.0: **GPS Connection Successful**, then tap **Start Collecting**.
* Firmware in 3DMakerpro's video: **Searching for and connecting to GPS...**, then **Place the device on a level surface and keep it still.** with a countdown.
* Raven: **Searching For And Connecting To GPS, The Device Must Remain Level And Still.**, then **Auto-Start Scanning**.
* Some firmware versions ask you to confirm with **Start Scan**.

The first time synchronisation after switching on takes a long time, so allow extra time. Under a roof, in a passage, under dense trees or indoors the scanner shows **GPS Connection Failed** with **Retry** and **Back**: move under open sky and tap **Retry**. Without internet the GPS search can hang, and a scan started anyway has no georeference.

{% hint style="warning" %}
**AUTO needs the scanner's position.** The caster picks the base station from the position the device sends as NMEA GGA. Without it, the login succeeds but no corrections arrive, see [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md). So **Connect success!** alone does not show that corrections flow. The **GPS** screen has no GGA setting, and 3DMakerpro does not document whether or when the scanner sends its position. Create and start the project outdoors so the scanner has a position of its own, wait for **GPS Connection Successful** or the end of the keep-still countdown before you move, and check the export for `RTK_XXXXXX.bin`.
{% endhint %}
{% endstep %}
{% endstepper %}

## Why must the mount point read AUTO in capital letters?

RTKdata mountpoint names are case sensitive, so the 3DMakerpro Eagle and Raven need exactly `AUTO` in **Mount Point**, and the preset `Auto` shown in the manuals does not match.

The manuals show the preset as `Auto`, the firmware in 3DMakerpro's video as `AUTO`. The preset comes from 3DMakerpro, not from RTKdata, so check the field on your own scanner before you tap **Save**. 3DMakerpro's manuals show the preset but not how to change it. A 3DMakerpro distributor's step-by-step guide has you type the mountpoint on the keyboard and stresses that upper and lower case must match. If the field cannot be changed, update to the current RTK firmware and contact 3DMakerpro support, and tell <support@rtkdata.com> which preset your scanner shows. A local coordinate system name such as `ETRS89` is not a mountpoint and returns no corrections.

| Mountpoint      | Output frame                                                                                                                                                | Use it when                                                    |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| `AUTO`          | Regional datum at your location, for example NAD83(2011) in the USA, NAD83(CSRS)v7 in Canada, ETRS89 (realization ETRF2000) in Europe, GDA2020 in Australia | Default for local control points, BIM and regional grids       |
| `AUTO_ITRF2020` | ITRF2020 at the current epoch                                                                                                                               | The project specifies ITRF2020                                 |
| `AUTO_ITRF2014` | ITRF2014 at the current epoch                                                                                                                               | The project specifies ITRF2014                                 |
| `AUTO_WGS84`    | WGS84(G2139) at the middle of the current year                                                                                                              | The project is explicitly in WGS84 or combined with WGS84 data |

Use the same frame for the mountpoint and for your control points. Mixing frames shifts the point cloud by a systematic offset. The datum that `AUTO` delivers in each country is listed in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md).

{% hint style="info" %}
The RTKdata sourcetable loads without a login. A visible mountpoint list, for example in an NTRIP app on your phone, proves neither that your credentials are correct nor that corrections flow (checked on 25 September 2026). If you browse the list, pick `AUTO`.
{% endhint %}

## How do you check that RTK data was recorded?

If a 3DMakerpro Eagle or Raven was set up with RTKdata on the **GPS** screen and its exported project folder has no `RTK_XXXXXX.bin`, no RTK data was recorded during the scan. The file alone does not show the solution quality: confirm it with the **RTK Result** layer in RayStudio on a known point.

This is the first check, because 3DMakerpro documents no fix indicator on the scanner. Export the project by USB stick, card reader or the scanner's own hotspot (**Activate Hotspot**; Wi-Fi `Rayzoom G100` on the Eagle, `JMK6XXXXXX` or `JMK7XXXXXX` on the Raven, `Rayzoom G200` on the Hawk, password `12345678`). Next to the `GPS_`, `IMAGE_` and `LIDAR_` (.bag) files, the folder must contain `RTK_XXXXXX.bin`.

If the SD card supplied with a Raven is not recognised in Windows, users report success with their own exFAT-formatted card or with the USB-C data port on the side.

Before the first real job, run a short test scan outdoors, process it in RayStudio and check the result on a known point.

## How do you georeference the scan in RayStudio?

A 3DMakerpro Eagle or Raven scan with RTKdata corrections is georeferenced in RayStudio for Windows: in **Data Processing**, turn on **RTK Calibration**, keep the coordinate system on **WGS84**, leave the RTK file directory empty and export the **RTK Result** layer.

1. In RayStudio 1.0.13, click **Open Project** and select the exported project.
2. Open **Data Processing** and choose the **Scan Scene**: **Indoor**, **Outdoor** or **Stairwell**.
3. Turn on **RTK Calibration** and leave the coordinate system below it on **WGS84**, the only documented option.
4. Leave **Select the rtk file directory (optional)** empty. It is only for base station files in PPK processing.
5. Click **Start**. When **Processing completed** appears, click **Finish**.
6. Show the data layer **RTK Result** in the **Data Layer List**. Some layers are hidden by default after processing.
7. Export it with **Export** as LAS, PCD, PLY, e57 or xyz.

If **RTK Calibration** stays off, RayStudio creates no **RTK Result** layer and the point cloud keeps relative coordinates, even when the scanner was connected correctly in the field.

The RTK sections of the RayStudio manual name the result `rtk_fixed.las`; its results table lists `rtk_color.las` (colourised) and `rtk_recalculate_result.las` (not colourised). The manual describes the RTK result as not thinned or filtered, so it can contain noise. Filter it afterwards in your point cloud software if needed.

{% hint style="warning" %}
**RayStudio 1.0.13 can differ from the manual.** A user reports that the 1.0.13 interface does not match the manual and tutorial videos. In 3DMakerpro's video, the same options appear under **Basic Data** or **Colorize** as **Real-Time Kinematic**, **RTK Coordinate System:** and **RTK Files Dir:**.
{% endhint %}

### Coordinate system and heights

{% hint style="info" %}
**Datum:** use `AUTO` and keep **WGS84** under **RTK Calibration**. `AUTO` delivers corrections in the regional datum of your location, for example ETRS89 in Europe or NAD83(2011) in the USA. **WGS84** is the only option RayStudio documents under **RTK Calibration**, and 3DMakerpro does not document whether it transforms the coordinates. Expect the result in the regional datum and confirm it on a known control point before you assign the CRS in your GIS. RayStudio does not document which coordinate reference system it writes to the exported LAS file. If the exported coordinates are UTM eastings and northings, assign the projected system of the regional datum in your GIS instead of transforming, for example ETRS89 / UTM zone 32N (EPSG:25832) for a site in UTM zone 32. For regions not listed in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md), `AUTO` falls back to WGS84(G2139) at the mid-year epoch.
{% endhint %}

{% hint style="info" %}
**Heights:** RTKdata corrections deliver **ellipsoidal heights**. RayStudio 1.0.13 calculates orthometric heights only with a `.pgm` geoid file, and the `.pgm` geoid files distributed with GeographicLib are worldwide models such as EGM96 and EGM2008, not national geoids. For official heights, export the ellipsoidal point cloud and apply your national geoid in the GIS. See [Understanding Heights](/get-started/understanding-heights.md).
{% endhint %}

For the datum and control point workflow that applies to all SLAM scanners, see [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md).

## Troubleshooting

RTK problems and SLAM problems can look similar in the point cloud but have different causes. Check the RTK side first.

### RTK and connection problems

| Problem                                                       | Cause                                                                                                   | Fix                                                                                                                                                                           |
| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **GPS** screen has no **RTK**, **Address** or **Mount Point** | Early Eagle firmware supported RTK only for PPK                                                         | Install the RTK firmware line for your model                                                                                                                                  |
| **Connect** never changes to **Disconnect**                   | Hotspot off, a typo in the hotspot name or password, or the iPhone left the **Personal Hotspot** screen | Use a short hotspot name, retype in the shade and turn on **Maximize Compatibility**. On Android, try the 2.4 GHz band with WPA2, as in 3DMakerpro's example                  |
| **GPS Connection Failed**                                     | Project started under a roof, under trees or indoors                                                    | Move under open sky and tap **Retry**. Allow time for the first time synchronisation                                                                                          |
| GPS search hangs                                              | No internet on the scanner                                                                              | Connect **Link Hotspots** first and check that the button shows **Disconnect**                                                                                                |
| `RTK_XXXXXX.bin` missing                                      | **RTK** off, no internet, wrong credentials or `Auto` instead of `AUTO` in **Mount Point**              | Check the **GPS** screen against the connection table and repeat a short scan outdoors                                                                                        |
| **Connect success!** shown, but no `RTK_XXXXXX.bin`           | The caster may not have received the scanner's position, so `AUTO` could not assign a base station      | Create and start the project under open sky and wait for **GPS Connection Successful** or the keep-still countdown before you move                                            |
| Hostname in **Address** does not connect                      | The device or network does not resolve the hostname                                                     | Enter the IP fallback from your region's tab in **Address**. Port, credentials and mountpoint stay the same                                                                   |
| Hotspot works, but still no RTK file                          | Port 2101 may be blocked on the mobile network                                                          | With the scanner off, test your regional host on port `2101` with your credentials in an NTRIP app on the same phone                                                          |
| RTK data missing while another device was connected           | Two devices on one set of credentials                                                                   | One data stream per device connected at the same time, see [Account & NTRIP Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices) |
| All values correct, still no `RTK_XXXXXX.bin`                 | The scanner may not send its position                                                                   | Send the scanner model, the firmware version, your RTKdata username (never the password) and the time of the test scan to <support@rtkdata.com> so the session can be checked |
| No **RTK Result** layer in RayStudio                          | **RTK Calibration** was off, or the layer is hidden                                                     | Reprocess with **RTK Calibration** on and show **RTK Result** in the **Data Layer List**                                                                                      |
| Point cloud offset from control points by a constant amount   | Mountpoint frame differs from the frame of the control points                                           | Use `AUTO` for regional control points and `AUTO_WGS84` only for WGS84 data                                                                                                   |
| Heights differ from benchmarks by a constant amount           | Ellipsoidal heights compared with orthometric heights                                                   | Apply the national geoid in the GIS, see [Understanding Heights](/get-started/understanding-heights.md)                                                                       |

### SLAM effects that RTK does not fix

RTK sets the absolute position of the scan. Drift, double walls or ghosting come from the SLAM processing and can remain even with RTK data recorded.

| Problem                                                    | Cause                                                                                                  | Fix                                                                                             |
| ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------- |
| Trajectory drifts or does not match the walked path        | SLAM drift, mounting or calibration                                                                    | Close loops, compare the RayStudio result with and without RTK, and check it on a control point |
| Shifted trajectories with a camera kit or other mount      | Possibly the mount or accessory; a lever arm setting is not documented                                 | Compare a test scan with and without the accessory on a known point                             |
| Neighbouring scans do not line up on shared control points | According to a user review, the control point correction acts as one solution on the whole point cloud | Check control points per scan and merge the scans afterwards                                    |

For connection problems not covered here, see [Fix NTRIP Connection Issues](/support/common-connection-issues.md).

## Frequently asked questions

### Does the 3DMakerpro Eagle RTK module support NTRIP or only PPK?

The 3DMakerpro Eagle RTK module takes live NTRIP corrections from a service such as RTKdata on the current RTK firmware line, **Eagle Standard with RTK** 2.1.6r or **Eagle Max with RTK** 1.1.6r (released 22 July 2026), while owners reported in 2025 that the module supported only PPK in RayStudio. If **RTK**, **Address** and **Mount Point** are missing on the **GPS** screen, install the RTK line for your model first, then enter the RTKdata host for your region, port `2101` and `AUTO`. PPK with base station files of your own is a separate option in RayStudio.

### Do I need a base station for the 3DMakerpro Eagle RTK module?

No. The 3DMakerpro Eagle RTK module takes corrections from an NTRIP service such as RTKdata: you enter the RTKdata server for your region, for example `eu.rtkdata.com` in Europe, on the **GPS** screen, and the scanner goes online through a phone hotspot or Wi-Fi network set up in **Link Hotspots**. You need no base station of your own and no radio link.

### Can I use my DJI RTK base station with the 3DMakerpro Eagle?

In 3DMakerpro's manuals, the Eagle's **GPS** screen takes only NTRIP details (**Address**, **Port**, **Username**, **Password**, **Mount Point**) and shows no pairing or radio settings. RTKdata delivers corrections over NTRIP, which the scanner takes through **Link Hotspots**, so no base station of your own is needed.

### Which mount point do I enter on the 3DMakerpro Eagle GPS screen?

With RTKdata, enter `AUTO` in capital letters in **Mount Point** on the Eagle's **GPS** screen. If the field shows `Auto`, change it to `AUTO`, because RTKdata mountpoint names are case sensitive. `AUTO` delivers RTKdata corrections in the regional datum at your location. Use `AUTO_ITRF2020`, `AUTO_ITRF2014` or `AUTO_WGS84` only when your project requires that fixed frame.

### Can I add RTK to a 3DMakerpro Raven Standard?

Yes, with the RTK Antenna & Signal Module for Raven Series, which 3DMakerpro lists as compatible with the Raven, Raven Max and Raven Max RTK. Without the module, a Raven Standard has no GPS. The Eagle is different: according to the shop FAQ, its RTK module can no longer be added after shipping. Once the module is fitted on the Raven, enter the RTKdata host for your region, port `2101` and `AUTO` on the **GPS** screen.

### Why does my Eagle say Connect success! but the scan is not georeferenced?

**Connect success!** appears after you save the Eagle's **GPS** screen and does not confirm an RTK fix. Check that the exported project folder contains `RTK_XXXXXX.bin`, then process the scan in RayStudio with **RTK Calibration** on and use the **RTK Result** layer. If the file is missing, check the internet connection in **Link Hotspots**, your RTKdata credentials, the RTKdata host for your region in **Address** (for example `eu.rtkdata.com`) and `AUTO` in capital letters in **Mount Point**, and start the project under open sky so the scanner has a position of its own.

## Quick reference

1. **Hardware and software:** Eagle with factory RTK module, Raven Max RTK or Raven with RTK module; Eagle firmware **Eagle Standard with RTK** 2.1.6r or **Eagle Max with RTK** 1.1.6r from the Eagle firmware list on 3DMakerpro's JMMeta support site; RayStudio 1.0.13 on Windows.
2. **Internet:** **Settings** > **Hotspot Links** > **Link Hotspots** on, SSID and password, **Connect** until the button shows **Disconnect**.
3. **GPS screen:** **Connect GPS** and **RTK** on, **Address** `rtk.rtkdata.com`, `eu.rtkdata.com` or `aus.rtkdata.com` (IP fallback `13.56.117.10`, `3.73.41.96` or `54.206.56.130`), **Port** `2101`, RTK credentials, **Mount Point** `AUTO` in capitals, **Save**. There is no GGA setting, and `AUTO` needs the scanner's position, so create and start the project under open sky.
4. **Scan:** start under open sky, wait for **GPS Connection Successful** or the keep-still countdown, then check the export: without `RTK_XXXXXX.bin`, no RTK data was recorded.
5. **RayStudio:** **Data Processing** > **RTK Calibration** on, **WGS84**, RTK file directory empty, export **RTK Result**; confirm the result on a known control point and assign the CRS of the regional datum in the GIS; heights are ellipsoidal.

## Related Guides

* [LiDAR Scanners & Mobile Mapping](/integration-hub/lidar-scanners-and-mobile-mapping.md): all LiDAR scanner guides and the RTKdata connection details
* [NTRIP Server Settings](/get-started/network.md): regional hosts, IP fallbacks, port 2101 and the AUTO mountpoint
* [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): why AUTO needs the device position and what happens when no GGA arrives
* [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md): which regional datum AUTO delivers in each country and how to avoid datum offsets
* [Understanding Heights](/get-started/understanding-heights.md): ellipsoidal and orthometric heights and how to apply a geoid
* [Account & NTRIP Credentials](/get-started/account-and-credentials.md): where to find your RTK credentials and how data streams work
* [Fix NTRIP Connection Issues](/support/common-connection-issues.md): what to check when the login works but no corrections arrive
* [Coverage Map](/get-started/coverage-map.md): check RTKdata coverage at your site before the field day
* [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md): datum and control point workflow for SLAM point clouds


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rtkdata.com/integration-hub/lidar-scanners-and-mobile-mapping/3dmakerpro-eagle-raven.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.