Menu

RTK Instruction

Using RTK Positioning with Galois P4

Connect an RTK receiver to Realsee VR and every scan station gets real-world coordinates, accurate to the centimeter.
Your point clouds and deliverables come out georeferenced — ready to drop into GIS, line up with survey control, or overlay on other project data.

What RTK does for your scans

Without RTK, your scan lives in its own local coordinate system. The geometry is accurate, but the model doesn't know where on Earth it sits.
With an RTK receiver connected, Galois P4 records a high-precision geographic position at every scan station. That gets you:
  • Georeferenced deliverables. Point clouds and models land in a real-world coordinate system, so they line up with GIS layers, survey data, and BIM models without manual alignment.
  • More reliable registration. Station coordinates act as constraints during registration — a big help on large sites, long corridors, and repetitive spaces where scan-to-scan matching alone can drift.
  • No extra field work. Positions are captured automatically at each station. There's nothing to tag, log, or write down.
Everything runs through Realsee VR App on your phone. Works the same on iOS and Android.
The NTRIP client is built in — no receiver SIM card, no manufacturer apps, no juggling between apps in the field.

Availability and requirements

RTK Positioning is currently available on Galois P4 only.
Other Realsee scanners aren't supported at this time. Support for additional models is on our roadmap.

You'll need:
Scanner Galois P4 running the lastest firmware
App Realsee VR 3.66.0 or later, iOS or Android
RTK receiver A supported receiver from the list below
Correction service An NTRIP account — a commercial CORS/network RTK subscription, a public network, or your own base station through an NTRIP caster
Connectivity Cell data (Hotspot needed) on your phone during capture. Corrections stream through your phone's connection.
  • You set up your NTRIP account directly with the provider.
  • Realsee doesn't resell correction data. If you're not sure what's available in your area, most regions have several commercial network RTK options, and many state and national agencies run free or low-cost CORS networks.
  • VRS-style networks are fully supported — Realsee VR reports your rough position to the caster automatically.

Supported RTK receivers

Realsee use open industry standards (NTRIP and NMEA over Bluetooth), so we're not locked to any single hardware brand.
Every receiver below has been tested end to end with Galois P4 and Realsee VR App before making the list.

Verified receivers

  • SparkPNT TX2 — Quad-band (L1/L2/L5/E6) receiver in a waterproof aluminum housing, with a 50+ hour battery.
      Connects to Realsee VR over Bluetooth right in the app — no system pairing needed. A strong all-around choice at a competitive price.
  • Emlid Reach RX2 — Compact, pocket-sized network rover (280 g, IP68) that's widely used across the surveying industry.
      On iPhone, pair it once in iOS Settings → Bluetooth first (PIN on screen); after that, Realsee VR picks it up automatically.
      On Android, connect directly in the app.

Have a different receiver?

If your receiver outputs standard NMEA over Bluetooth, there's a good chance it'll work.
A quick way to check: if it connects to the free SW Maps app on iOS using the Generic NMEA (Bluetooth LE) profile and reaches an RTK Fix through SW Maps' built-in NTRIP client, it follows the same connection pattern we support.
Either way, tell us the make and model.


Setting it up

1. Update everything

Make sure your Galois P4 firmware and Realsee VR are on the required versions (see table above).

2. Set up your receiver

Attach the module directly on top of the Galois P4 using the magnetic mounting plate, then turn it on

3. Add the receiver in Realsee VR

Connected with Galois P4 first.
Tap Scan.
On the scan screen, tap the settings icon in the lower-left corner.
Locate the RTK toggle at the bottom of the settings list.
If this is your first time using RTK, tap RTK Configuration below the toggle to configure it.
If RTK has already been configured, simply turn on the toggle.
On the RTK Configuration screen, tap Add Device to connect your RTK Rover.
Select the RTK Rover you want to connect from the list.
If it is not listed, tap Find other RTK, then select the device.

4. Complete the RTK settings

After the device is connected:
- Turn on your phone’s Wi-Fi hotspot. Then under Network Configuration, enter the hotspot name and password.
- Under RTK Account Configuration, enter the CORS network account details provided by your CORS service provider:
  • Account
  • Password
  • Server Address
  • Port
  • Source Node

 

5. Save the configuration and wait for a fixed solution

Tap Save in the upper-right corner then configuration starts automatically. Once configuration is complete, an RTK status indicator appears in the center of the scan screen.
  • No Fix: The RTK module is still acquiring positioning data.
    This usually takes 2–5 minutes, depending on satellite reception at your location. Do not start scanning while this status is displayed.
  • Fixed: The RTK Rover has acquired a fixed solution.
    You can now start scanning. When finished, edit and upload the scan as usual.

Good to know

  1. Sky view matters.

      RTK needs satellite signal. Open and semi-open sites work great; deep indoors, dense tree canopy, and tight urban canyons can prevent a Fix. For mixed indoor/outdoor projects, stations with a Fix anchor the whole model — indoor stations still register through normal scan-to-scan matching.
  2. A weak Fix won't block your scan.

      If signal quality drops at a station, that station gets flagged and capture continues. RTK enhances your results; it never stops the workflow. You can rescan a flagged station or keep moving.
  3. Keep your phone online.

      Corrections stream from your NTRIP provider through your phone's data connection. If your phone drops offline, the receiver falls back to standalone accuracy until the connection returns.
  4. One app is enough — and one connection is the rule.

      Don't run the receiver manufacturer's app (Emlid Flow, etc.) at the same time. Most receivers accept only one Bluetooth connection, so a second app will fight Realsee VR for the link.
  5. Battery and range.

      Keep the receiver within Bluetooth range of your phone (a few meters is ideal). Check receiver battery before long days — the TX2 runs 50+ hours; the RX2 about 16.
  6. Something not connecting?

      Power-cycle the receiver, make sure no other app is holding the Bluetooth connection, and check that your NTRIP credentials are current. Still stuck? Reach out with your receiver model and app version.
Was this article helpful?