> 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/fjd-trion-p1-p2-s2.md). # FJD Trion P2 RTK Setup with P1 & S2: NTRIP in Trion Scan Connect FJD Trion P1, P2 and S2 scanners to RTKdata in FJD Trion Scan: phone hotspot, SR RTK model, Ntrip rover card with AUTO and GNSS Fusion in Trion Model. The **FJD Trion P1**, **P2** and **S2** (including **S2 PRO** and **S2 MAX**) are handheld SLAM LiDAR scanners from FJDynamics. They receive RTK corrections through an FJD RTK module (SR) and connect to RTKdata over NTRIP from the **FJD Trion Scan** app on iOS or Android. This page covers the FJD Trion P2 RTK setup, the P1 with the **FJD Trion RTK Module (SR)** (called FJD Trion GNSS Module (SR) in the FJD support center) and the S2 series. The scanner joins your phone's hotspot for internet, the RTKdata connection is saved as an **Ntrip** card under **RTK Settings**, and the georeferenced point cloud is produced afterwards in **FJD Trion Model** with **GNSS Fusion**. FJD lists RTK for the newer Trion T1 and X1 as well, but their correction setup is not documented yet, so they are not covered here. Trion scanners are not the FJD auto-steer systems used in agriculture; those are listed under [RTKdata for Agriculture](/integration-hub/agriculture.md#fj-dynamics-fjd). FJD's separate GNSS receivers such as the V1t and V10i are set up outside Trion Scan according to FJD's manual and are not covered here. Enter these values on the **Ntrip** page in Trion Scan. Choose the server closest to your work area; all three servers share the same base station network ([NTRIP Server Settings](/get-started/network.md)). Select the tab for your region: {% tabs %} {% tab title="North America" %} * **Host (domain):** `rtk.rtkdata.com` in **Server Address** (recommended) * **Host (IP fallback):** `13.56.117.10` in **Server Address**, only if the check stops at **Server Address/Port** with the hostname (older apps: **Server address/account verification**, once the credentials are ruled out) * **Port:** `2101` in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login, in **Username** and **Password** * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, picked as **Node** from the list behind **Source Node** {% endtab %} {% tab title="Europe" %} * **Host (domain):** `eu.rtkdata.com` in **Server Address** (recommended) * **Host (IP fallback):** `3.73.41.96` in **Server Address**, only if the check stops at **Server Address/Port** with the hostname (older apps: **Server address/account verification**, once the credentials are ruled out) * **Port:** `2101` in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login, in **Username** and **Password** * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, picked as **Node** from the list behind **Source Node** {% endtab %} {% tab title="Australia" %} * **Host (domain):** `aus.rtkdata.com` in **Server Address** (recommended) * **Host (IP fallback):** `54.206.56.130` in **Server Address**, only if the check stops at **Server Address/Port** with the hostname (older apps: **Server address/account verification**, once the credentials are ruled out) * **Port:** `2101` in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login, in **Username** and **Password** * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, picked as **Node** from the list behind **Source Node** {% endtab %} {% endtabs %} The same values at a glance: | Field | Value | | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Name** | Any label, for example `RTKdata` | | **Server Address** (North America) | `rtk.rtkdata.com`, IP fallback `13.56.117.10` | | **Server Address** (Europe) | `eu.rtkdata.com`, IP fallback `3.73.41.96` | | **Server Address** (Australia) | `aus.rtkdata.com`, IP fallback `54.206.56.130` | | **Port** | `2101` | | **Source Node** | Tap the icon to load the mountpoint list | | **Node** | `AUTO` in ALL CAPS (alternatives: `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`) | | **Username** | From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/). It starts with `rtk` and is not your website login. | | **Password** | From *RTK Credentials*, not your website login | `AUTO` selects the nearest base station from the device position (NMEA GGA) and delivers corrections in your region's local datum. Pick one of the global frames only when your project needs that frame. Current app version when this page was written: FJD Trion Scan 3.8.3 for iOS (September 2026). The labels on this page come from FJD manuals and published app screens up to January 2026; in Trion Scan 3.8.x they can differ slightly. ## What do you need before connecting an FJD Trion to RTKdata? To connect an FJD Trion to RTKdata you need the scanner with its RTK module mounted, a current FJD Trion Scan (3.8.2 or later on iOS), a phone with mobile data and a hotspot, RTKdata coverage at your site and your RTKdata NTRIP credentials. * **FJD Trion P1, P2 or S2** with the RTK module mounted (see the tabs below) * **FJD Trion Scan 3.8.2 or later** on iOS 15 or later; on Android, the current version from Google Play. Trion Scan 3.8.2 for iOS (10 September 2026) fixed an issue where saving CORS accounts failed. Version 3.8.3 from 14 September 2026 was the current iOS version when this page was written. * **Current scanner firmware**, updated after the app: **Settings** > **Firmware Version** in Trion Scan. Update in the office, not on site. A P1 with the SR module needs firmware V1.5 or later. * **Phone with mobile data and a personal hotspot** that can run on 2.4 GHz * **RTKdata coverage** at your site: check the [Coverage Map](/get-started/coverage-map.md) before you go out. * **RTKdata account** with active RTK credentials (username starts with `rtk`). One set of credentials allows one connection at a time, so a drone or rover that is online at the same time needs its own data stream ([Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices)). * **FJD Trion Model** on a PC for the georeferenced point cloud. P2 data need Trion Model PC V207.001 or later. {% 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 %} Mount the RTK module before you power on the scanner: {% tabs %} {% tab title="P1" %} Place the **GNSS Module** in the **GNSS Holder** and connect its cable. {% endtab %} {% tab title="P2" %} * **Option A** (panoramic external camera plus RTK module, for example with the Insta360 mount): connect the RTK cables and the camera cables. * **Option B** (RTK module package): insert the adapter by aligning the red dots. {% endtab %} {% tab title="S2 / S2 PRO / S2 MAX" %} The RTK module sits on the **Bracket** and connects through the **7pin Cable** (RTK communication and power supply). {% endtab %} {% endtabs %} ## How does the Trion get internet for RTK corrections? The FJD Trion gets internet for RTKdata corrections through your phone: the scanner joins the phone's personal hotspot in network mode, so the phone needs mobile data. In local mode the phone connects to the scanner's own Wi-Fi instead, and according to FJD's manuals the scanner then has no internet and receives no corrections. | Model | Network mode (use this) | Local mode (no internet) | | ---------------------------- | ----------------------- | ------------------------ | | P1 | **STA** mode | **AP** mode | | P2, firmware V1.2.0 or later | **Network Setup Mode** | **Local Area Mode** | | P2, older firmware | **STA Mode** | **AP Mode** | | S2 / S2 PRO / S2 MAX | **WLAN** mode | **Hotspot mode** | | Status LED | Solid green | Solid blue | {% stepper %} {% step %} ### Turn on the phone hotspot Turn on **Personal Hotspot** with mobile data on your phone. The scanners use 2.4 GHz Wi-Fi. On Android, choose the 2.4 GHz band if your phone offers that setting. On an iPhone, Apple advises turning on **Maximize Compatibility** and staying on the **Personal Hotspot** screen until the other device has connected; keep it open until Trion Scan shows **Device Connected**. {% endstep %} {% step %} ### Power on the scanner in network mode 1. Go outdoors under open sky before you power on; RTKdata's `AUTO` needs the scanner's own position. 2. Place the scanner flat and still. 3. Power it on: hold the power button for 1 to 2 seconds on the P1, press it briefly (0.2 to 1 second) on the P2 and S2. 4. After about 15 seconds the LED turns solid green. That is network mode. 5. If the LED turns solid blue, the scanner is in local mode. Switch back with a short press (0.2 to 0.5 seconds) followed by a long press (about 1 second or longer). The P1 starts in STA mode again after every restart. On a P2 with firmware V1.2.0 or later, local mode can be set as the default start mode; if the LED keeps coming up blue, set the default back to **Network Setup Mode**. {% endstep %} {% step %} ### Connect the scanner in Trion Scan 1. Open **FJD Trion Scan** and tap **Add Devices**. 2. On **Connect Device**, pick **FJD Trion P1**, **FJD Trion P2** or **FJD Trion S2** and tap **Next Step**. 3. Allow Bluetooth. The app searches for devices; select your scanner by its serial number. 4. On **Input Hotspot Information**, enter **Hotspot Name\*** and **Hotspot Password\*** of your phone hotspot and tap **Confirm**. 5. The app shows **Device Connected** and **Obtaining Device Information**. {% hint style="warning" %} Do not tap **switching connection method** on the **Connect Device** screen. It leads to local mode without internet, so no corrections reach the scanner. The first time you use a scanner it is locked anyway. {% endhint %} {% endstep %} {% endstepper %} ## How do you set up FJD Trion P2 RTK with RTKdata in Trion Scan? To set up FJD Trion P2 RTK with RTKdata, open **Settings** > **RTK Settings** > **Rover** > **Add** on the connected scanner in FJD Trion Scan and fill in the **Ntrip** page with the RTKdata host for your region (`rtk.rtkdata.com` North America, `eu.rtkdata.com` Europe, `aus.rtkdata.com` Australia), port `2101`, node `AUTO` and your RTKdata credentials. The P1 with the SR module and the S2 use the same page. Older app versions call the **Rover** entry **Mobile Station Settings**. {% stepper %} {% step %} ### Confirm the RTK model SR After the scanner connects, Trion Scan shows the **RTK Model** pop-up (*RTK equipment is detected, please confirm the specific model and parameters.*). 1. Tap **SR** actively, then **OK**. **V1t**, **V10i** and, in newer apps, **V10a** are separate FJD receivers. 2. Some app versions preselect **V10i** (seen in a P1 app on Android). Tapping only **OK** then sets the wrong receiver. 3. The app confirms with **Parameter settings are successful.** and **RTK Settings** shows **Model** = **SR**. To change it later, use **Switch Model** or **Model** on the **RTK Settings** page. {% endstep %} {% step %} ### Match the structure parameters to your mounting On **RTK Settings**, set **Structure Parameters** to the hardware you actually use: * Without a camera mount: **Default**. * P2 with the Insta360 mount: **Camera Stand** = **Yes** on iOS, or **With Camera Mount** on Android. * **Customization** only for your own mounting. FJD does not document what these values change, so match them to the real setup rather than leaving a previous choice. {% endstep %} {% step %} ### Open the Rover list 1. Open the connected scanner's **Settings** tab and tap **RTK Settings** > **Rover**. While no card is applied, **Rover** shows **Not Connected**. In older app versions this entry is **Mobile Station Settings**. 2. If the list shows **No Configuration**, tap **Add** at the bottom. The **Ntrip** page opens. If **RTK Settings** shows neither **Rover** nor **Mobile Station Settings**, FJD's release notes name two other places: rover management in the app's **Software Settings** (Trion Scan 3.6.0) and a **Mobile Station Management** section (S2 firmware V1.4.2). The RTK icon at the top right of the device home screen opens **RTK Data**, which also has a **Settings** button. {% endstep %} {% step %} ### Fill in the Ntrip page 1. **Name**: any label, for example `RTKdata`. 2. **Server Address**: type the host for your region by hand: `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia). 3. **Port**: `2101`. 4. Tap the icon behind **Source Node**. The app loads the mountpoint list from the caster. This works only once **Server Address** and **Port** are correct and the phone has internet. 5. **Node**: pick `AUTO` from the list (search field *Please enter a name*). The list can show further entries; stay on `AUTO` unless your project needs `AUTO_WGS84`, `AUTO_ITRF2020` or `AUTO_ITRF2014`. **Node** is required. 6. **Username** and **Password**: your RTK credentials. Type them rather than paste them, with no spaces at the start or end. {% hint style="info" %} The pin icon labelled **IP** behind **Server Address** is only an address book for saved servers. It does not mean the field needs an IP address. It holds only addresses that were saved on this device before, which can include other correction services, so check that the entry you pick is the RTKdata host for your region, or type the host by hand. From P2 firmware V1.2.0, saved server addresses can be deleted. {% endhint %} {% hint style="warning" %} The RTKdata sourcetable loads without a login. A visible mountpoint list proves neither your credentials nor a correction stream (checked on 25 September 2026). The check dialog and **RTK Status** show whether corrections arrive. {% endhint %} {% endstep %} {% step %} ### Apply the card and watch the check dialog {% hint style="info" %} `AUTO` chooses the base station from the device position (NMEA GGA). Without that position the login still succeeds, but no corrections arrive ([NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md)). The Ntrip page has no GGA setting, and FJD does not document how the scanner reports its position. That is why you switch the scanner on outdoors (see the power-on step): give it time under open sky to find its own position, then apply the card. {% endhint %} 1. Tap **Use** to save and apply the card. **Save** only stores it. 2. A saved card is applied from the list: swipe it and tap the check mark. The other two actions are **Configuration Details** (i) and **Delete** (trash can). 3. Trion Scan checks the connection in the **Rover** dialog: **Network Verification**, **Server Address/Port**, **Username/Password**, **Configure Receiver**. Confirm with **OK**. Older app versions show three steps: **Network verification**, **Server address/account verification**, **Configure receiver**. 4. The card shows **Use: CORS**, **Port: 2101** and **Server Address:** with your RTKdata host, for example `rtk.rtkdata.com`, and a yellow check mark. If the dialog stops at one step, that step points to the fault. See the troubleshooting table below. {% endstep %} {% endstepper %} ## What do the yellow and green check marks mean? On an FJD Trion, a yellow check mark on the RTKdata Ntrip card means the configuration has been applied, and a green check mark means the scanner has an RTK fix. FJD's RTK module manual says the yellow mark turns green automatically "if the current RTK is in an open area and the signal is good enough to obtain a fixed solution". To confirm the fix, tap the RTK icon at the top right of the device home screen. In **RTK Data**: * **RTK Status** must show **Fixed**. The P2 app adds a number, for example **Fixed-0**; FJD does not document its meaning. * **CORS Account** shows **Connected Successfully**. This confirms the login, not the fix. * **Source Node** shows the mountpoint in use, and **Baseline** the distance to the base station (in metres in the P2 app). For the best accuracy, work within 15 km of a base station ([Accuracy Expectations](/get-started/accuracy-expectations.md)). A much longer baseline means the nearest station is far from your site; check the [Coverage Map](/get-started/coverage-map.md). Older app versions label the window **RTK data** with **CORS account** and **Connected successfully.** Tap **Scan** only once **RTK Status** shows **Fixed**. If Trion Scan asks *Abnormal RTK status. Are you sure you want to start scanning?*, tap **Cancel** and wait for the fix. **OK** starts the scan without one. On later starts, Trion Scan applies the last configuration automatically. When you start a scan, wait until *Configuration loading, please wait...* has finished. ### Changing a saved Ntrip card An applied card cannot be edited or deleted; its buttons are greyed out. Swipe the card and tap **Cancel Application** (X) first, then edit it under **Configuration Details** (i) or delete it, and apply the new card. Because the last configuration is applied at every start, changed settings only take effect this way. ## How do you georeference the scan in FJD Trion Model? You georeference an FJD Trion scan with RTKdata positions in FJD Trion Model on the PC: in **Point Cloud Mapping** set **Scanning scene** to **Outdoor**, tick **GNSS Fusion**, choose a **Coord System** on the regional datum that RTKdata's `AUTO` delivers, and leave **Optimize with Control Point** off, because it disables RTK integration. **GNSS Fusion** ties the SLAM point cloud to the RTK positions recorded in the field. Trion Scan records the data; the fusion runs in Trion Model. 1. Open **Point Cloud Mapping**, load the file under **Data File Path** and select the **Device Model** (P1, P2 or S2). P2 data need Trion Model PC V207.001 or later; that version also fixed an issue with exporting large-coordinate point clouds. 2. Set **Scanning scene** to **Outdoor**. 3. Tick **GNSS Fusion** (older versions: **RTK Fusion**). Without it the point cloud stays in local SLAM coordinates, even if the scan had a fix. 4. Under **Coord System**, open **Predefined Coordinates**, set **Continent** and **Region**, and actively choose the system on the regional datum that `AUTO` delivers for your site, in the zone of your site. Check the preselected system before you confirm: it has been seen set to China CGCS 2000 or to the last system used. 5. Leave **Optimize with Control Point** off. FJD states that enabling control point optimization disables RTK integration. Use control points to check accuracy instead. 6. For heights above a local reference, use **Geoid Model** or, with control points, **Elevation Fitting**. {% hint style="info" %} **Datum:** `AUTO` delivers corrections in your region's local datum, for example NAD83(2011) in the USA, NAD83(CSRS)v7 in Canada, ETRS89 (realization ETRF2000) in Europe and GDA2020 in Australia. For every other region, see the table in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md#regional-geodetic-coordinate-system-rgcs). `AUTO_ITRF2020` and `AUTO_ITRF2014` deliver that frame at the current epoch, and `AUTO_WGS84` delivers WGS84(G2139) in the middle of the current year. In Trion Model, choose a target system on the same datum as your mountpoint, and use `AUTO_WGS84` only with a target system based on WGS 84. FJD does not document how Trion Model handles datums internally, so check at least one known control point before you deliver. The general workflow for SLAM scans is in [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md). {% endhint %} {% hint style="info" %} RTKdata corrections deliver **ellipsoidal heights**, not heights above mean sea level. Apply a **Geoid Model** or **Elevation Fitting** in Trion Model when you need orthometric heights. See [Understanding Heights](/get-started/understanding-heights.md). {% endhint %} ## What should you check when there is no fix? When an FJD Trion does not reach a fix with RTKdata, first look at where the **Rover** check dialog stops, because each step tests one part of the connection. | Problem | Cause | Fix | | -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Stops at **Network Verification** | Scanner in local mode, or the hotspot has no mobile data | Check for a solid green LED (network mode), turn on mobile data and reconnect the scanner to the hotspot. | | Stops at **Server Address/Port** | Host or port mistyped, or the hostname is not resolved | Retype the host for your region and `2101` by hand. If it still stops here, enter the IP fallback for your region as **Server Address**: `13.56.117.10` (North America), `3.73.41.96` (Europe) or `54.206.56.130` (Australia). | | Stops at **Username/Password** | Website login used, typo, or a space in the field | Type the username (starts with `rtk`) and password from *RTK Credentials* again. | | Stops at **Server address/account verification** (older apps) | Host, port or credentials wrong | Retype the host for your region and `2101`, then the username and password from *RTK Credentials*. If it still stops, enter the IP fallback for your region as **Server Address** (see above). | | Stops at **Configure Receiver** | Most likely a wrong RTK model or a module that is not detected | Check **Model** = **SR** under **RTK Settings**, and check the module cable, the P2 adapter or the S2 **7pin Cable**. | | No mountpoint list after tapping **Source Node** | **Server Address** or **Port** wrong, or no internet | Correct them first, then tap the icon again. | | Card cannot be saved | **Node** empty, or an older Trion Scan version | Pick `AUTO` as **Node**, and update Trion Scan to the current version (3.8.2 or later on iOS). | | Card cannot be edited or deleted | The card is applied | Tap **Cancel Application** (X) first. | | Scanner keeps connecting with a previous card | The last configuration is applied at every start | Cancel the active card, then apply the RTKdata card with the values above. | | Scanner does not find the hotspot | Hotspot not reachable for a 2.4 GHz device | iPhone: turn on **Maximize Compatibility** and stay on the **Personal Hotspot** screen until the scanner connects (Apple's advice). Android: choose the 2.4 GHz band. | | **Connecting to a hotspot** dialog appears | The scanner is already connected to another phone or computer | Disconnect it from the other phone or computer first. | | Yellow check mark, no green | Card applied, no fix yet | Move to open sky, hold the scanner still and wait for **Fixed**. Under open sky most users reach an RTK fix in 5 to 20 seconds ([NTRIP Server Settings](/get-started/network.md)); give it 60 to 90 seconds to converge ([Accuracy Expectations](/get-started/accuracy-expectations.md)). If it still does not show **Fixed**, check **RTK Data** and continue with the next row. | | **Connected Successfully**, but **RTK Status** never shows **Fixed** | Poor sky view, or the caster has not received the device position (NMEA GGA), so `AUTO` cannot assign a base station | Restart the scanner outdoors under open sky, let it find its own position and apply the card again. If that does not help, contact . | | Fix drops during the scan | Sky view blocked along the route, or the phone loses mobile data | Start and end the scan under open sky with **Fixed**, keep an eye on the RTK status while you scan, and repeat sections where the fix dropped. FJD Trion Model also has a **PPK Calculation** that uses data from a base station of your own; see [Is RTK or PPK better for a handheld SLAM scanner?](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md#is-rtk-or-ppk-better-for-a-handheld-slam-scanner) | | Connection drops or the fix keeps cycling while another device is on | Two devices on one set of credentials | One set of credentials allows one connection at a time. See [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices). | | Point cloud is not georeferenced | **GNSS Fusion** not ticked, or **Scanning scene** on **Indoor** | See the Trion Model section above. | For connection problems that are not specific to the Trion, such as corrections that never arrive or a login that keeps failing, see [Fix NTRIP Connection Issues](/support/common-connection-issues.md). ## Frequently asked questions ### Can the FJD Trion P2 use a third-party NTRIP service? Yes. FJD Trion Scan has an Ntrip page for any NTRIP caster, and FJD notes that "the CORS account needs to be purchased by yourself". For RTKdata, enter the host for your region (`rtk.rtkdata.com`, `eu.rtkdata.com` or `aus.rtkdata.com`), port `2101`, node `AUTO` and your RTK credentials. The P1 with the SR module and the S2 use the same page. ### Where is the Rover menu in FJD Trion Scan? The Rover menu, where you add RTKdata as an Ntrip card, is in the connected scanner's **Settings** tab under **RTK Settings** > **Rover**. Older versions of FJD Trion Scan call it **Mobile Station Settings**. The RTK icon at the top right of the device home screen opens **RTK Data**, which has a **Settings** button as well. ### Why does my FJD Trion show a yellow check mark but no fix? A yellow check mark means Trion Scan has applied the Ntrip card; it turns green only when the scanner has an RTK fix. Move to open sky and wait: under open sky most users reach an RTK fix in 5 to 20 seconds, and RTK can take 60 to 90 seconds to converge. If **RTK Data** shows **CORS Account** **Connected Successfully** but **RTK Status** never reaches **Fixed**, check that **Model** is **SR** and restart the scanner outdoors. RTKdata's `AUTO` mountpoint needs the scanner's own position (NMEA GGA) to pick a base station; without it the login succeeds but no corrections arrive ([NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md)). Give the scanner time under open sky to find its position, apply the card again, and contact RTKdata support if it persists. ### Which RTK model do I choose for the Trion SR module? Choose **SR** for the FJD Trion P1, P2 and S2 with the FJD RTK module. **V1t**, **V10i** and **V10a** are separate FJD receivers. Tap **SR** before **OK**, because some app versions preselect **V10i**. Then add RTKdata under **RTK Settings** > **Rover** with the host for your region, port `2101` and node `AUTO`. ### How do you connect the FJD Trion P1 RTK module to RTKdata? The FJD Trion P1 receives RTKdata corrections through the **FJD Trion RTK Module (SR)**, which needs P1 firmware V1.5 or later. Place the **GNSS Module** in the **GNSS Holder** and connect its cable, connect the P1 to your phone hotspot in **STA** mode, confirm **SR** in the **RTK Model** pop-up, then add RTKdata under **Settings** > **RTK Settings** > **Rover** > **Add** with the host for your region, port `2101` and node `AUTO`. ### Does FJD Trion Scan accept a hostname as server address? Yes. FJD's RTK Module (SR) manual shows a hostname in **Server Address** on the P1, and published iOS videos show a P2 reaching **Fixed** and an S2 connecting with a hostname. On Android the field takes free text, but public examples only use IP addresses. Enter the RTKdata host for your region, for example `eu.rtkdata.com` in Europe; if the check stops at **Server Address/Port** (older apps: **Server address/account verification**, once the credentials are ruled out), use the IP fallback for that region, for example `3.73.41.96`. ## Quick reference 1. Outdoors under open sky: phone hotspot with mobile data on 2.4 GHz, scanner in network mode (solid green LED), a current FJD Trion Scan (3.8.2 or later on iOS). 2. **Add Devices** > model > **Next Step** > hotspot name and password > **Confirm**, then **RTK Model** = **SR** > **OK**. 3. **Settings** > **RTK Settings** > **Rover** > **Add**: **Server Address** `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia), **Port** `2101`, **Node** `AUTO`, RTKdata **Username** and **Password** > **Use**. 4. Only if the check still stops at **Server Address/Port** (older apps: **Server address/account verification**, credentials ruled out): IP fallback `13.56.117.10`, `3.73.41.96` or `54.206.56.130` as **Server Address**. 5. Wait for the green check mark and **RTK Status** **Fixed** before you tap **Scan**. 6. Trion Model: **Point Cloud Mapping** > **Outdoor** > **GNSS Fusion** > **Coord System** on the regional datum that `AUTO` delivers, then check a control point. ## Related Guides * [LiDAR & SLAM Scanner RTK Setup](/integration-hub/lidar-scanners-and-mobile-mapping.md): all scanner guides and the shared RTKdata connection settings * [NTRIP Server Settings](/get-started/network.md): regional hosts, IP fallbacks, port 2101 and how to pick the server closest to your work area * [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): how `AUTO` uses the device position to choose a base station, and why a login alone brings no corrections * [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md): which regional datum `AUTO` delivers in each country, and what the global frames deliver * [Understanding Heights](/get-started/understanding-heights.md): ellipsoidal and orthometric heights, and when a geoid model is needed * [Account & Credentials](/get-started/account-and-credentials.md): where to find your RTK credentials and how many devices can connect at once * [Fix NTRIP Connection Issues](/support/common-connection-issues.md): general checks when you are connected but receive no corrections or stay on FLOAT * [Coverage Map](/get-started/coverage-map.md): how to check RTK coverage at your site before field work * [Accuracy Expectations](/get-started/accuracy-expectations.md): how distance to the base station, sky view and latency affect the fix, and how long to wait for it * [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md): how to match the mountpoint datum, the processing target system and control points for SLAM scans * [RTKdata for Agriculture](/integration-hub/agriculture.md): the FJD auto-steer systems, which are separate products from the Trion scanners --- # 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/fjd-trion-p1-p2-s2.md?ask=&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.