Start with Windows

Connect your SCOUT or SCOUT Pro receiver to Windows, open its COM port in TRACE, forward NTRIP corrections, and confirm that the receiver reaches RTK Fixed.

How the system works: TRACE manages the Windows connection, NTRIP forwarding, monitoring, and logging. The RTK solution is calculated by SCOUT or SCOUT Pro.

Before you start

Prepare the receiver, connection, and correction-service details before opening TRACE.

  • A SCOUT or SCOUT Pro receiver
  • A Windows computer
  • A USB-C cable that supports data transfer
  • The complete TRACE ZIP package
  • NTRIP caster, port, mountpoint, username, and password
  • An outdoor location with a clear view of the sky
SCOUT receiver connected to a Windows computer with a USB-C data cable
Connect SCOUT to the computer with a USB-C data cable before opening the COM port.

SCOUT Series baud rates

Use the baud rate configured for your product version. If the receiver has been reconfigured, use its current serial setting instead.

Product version Default baud rate
SCOUT RTK / RTK+DR 115200
SCOUT Pro RTK 115200
SCOUT Pro RTK+DR 921600

Download and open TRACE

  1. Download the Windows ZIP package from the TRACE product page.
  2. Extract the complete ZIP to a local folder. Do not run TRACE from inside the ZIP archive.
  3. Keep the supporting files with the executable, then open KALMIX Trace.exe.
Download TRACE for Windows

Connect SCOUT to Windows

  1. Connect SCOUT or SCOUT Pro to the computer with a USB-C data cable.
  2. Open Windows Device Manager.
  3. Expand Ports (COM & LPT).
  4. Note the COM number assigned to the SCOUT USB serial connection.

The entry may appear as a USB serial device such as USB Serial Device (COMx). The COM number can change when you use a different USB port.

No COM port? Reconnect SCOUT, try another USB port, confirm that the cable supports data transfer, and install the required USB serial driver if Windows does not recognize the device.

Open the COM port and verify NMEA

  1. Open the Connection page in TRACE.
  2. Click Refresh to reload the available COM ports.
  3. Select the SCOUT COM port found in Device Manager.
  4. Select the baud rate for your SCOUT version.
  5. Click Open.
Select the SCOUT COM port and baud rate in TRACE
Refresh the port list, select the SCOUT COM port and baud rate, then open the serial connection.

Connection check: The serial port is open, Live NMEA continues updating, and the position fields show valid coordinates, satellite count, and HDOP.

If Live NMEA is empty or unreadable, check the selected COM port and baud rate first. Also confirm that another application is not already using the same port.

Connect NTRIP corrections

  1. Enter the caster address and port.
  2. Select or enter the mountpoint.
  3. Enter the NTRIP username and password.
  4. Enable periodic GGA upload if required by the correction service.
  5. Connect the NTRIP service.

Correction path: NTRIP caster → TRACE → SCOUT
Status path: SCOUT → NMEA → TRACE

NTRIP correction settings and RTCM counters for a connected SCOUT receiver in TRACE
After connecting NTRIP, verify that both the RTCM received and RTCM forwarded counters continue increasing.

Correction check: NTRIP is connected, RTCM received increases, and RTCM forwarded increases. A connected NTRIP session without forwarded RTCM data is not a complete SCOUT RTK connection.

Confirm RTK Fixed

Move SCOUT outdoors with a clear view of the sky. Keep the serial and NTRIP connections active, then monitor the positioning status reported by the receiver.

How to read the status: TRACE displays the solution state reported by SCOUT or SCOUT Pro; it does not calculate that state. The labels below typically correspond to the receiver’s NMEA GGA quality report. The exact wording and available states can vary by receiver model, firmware, and configuration.

SCOUT reporting RTK Fixed after TRACE forwards RTCM corrections
RTK Fixed confirms that SCOUT is using the forwarded corrections and reporting a fixed solution through NMEA.
Reported state Meaning Next check
No Fix (0) No valid GNSS position. Move outdoors and check satellite visibility.
Standalone (1) A normal GNSS position is available without a differential or RTK solution. Check NTRIP and RTCM forwarding.
Differential (2) Code-differential positioning is available, but the receiver is not RTK fixed. Check the correction source and quality; continue until RTK Float or RTK Fixed if carrier-phase RTK is required.
RTK Float (5) RTK corrections are in use, but carrier ambiguities are not fixed. Keep a clear sky view; check correction age, correction continuity, satellite geometry, and allow time to converge.
RTK Fixed (4) The receiver reports a fixed RTK solution. This is the target state for centimeter-level work when a fixed solution is required. Windows setup is complete.
Inertial / DR (6) On supported SCOUT RTK+DR configurations, the receiver may report an inertial or dead-reckoning-assisted solution during degraded GNSS conditions. It is not RTK Fixed. Check the product configuration, initialization and motion conditions, and whether GNSS visibility and corrections have recovered.

Optional monitoring and logs

The Windows setup is complete when SCOUT reports RTK Fixed. Use the following views only when you need additional signal, stability, or support information.

Skyplot and Scatter View

Skyplot shows satellite distribution and signal levels. Scatter View helps you review static position stability after the receiver has reached a stable solution.

Skyplot and satellite signal view for a connected SCOUT receiver
Use Skyplot to review satellite distribution and signal levels.
Scatter View showing static position samples from a connected SCOUT receiver
Use Scatter View to review static position clustering and stability.

Save a test log

Open the Logging page when you need to preserve a test session or share evidence with Kalmix support. TRACE can save NMEA text, raw RTCM3, and application event logs.

  1. Select the required log types.
  2. Choose a save directory if you do not want to use the default logs folder.
  3. Click Apply.
  4. Run the test, then use Open folder to find the saved files.
TRACE logging settings for saving SCOUT NMEA, RTCM3, and application event logs
Enable only the logs needed for the test, apply the settings, and open the log folder after recording.

Troubleshooting

Work through the connection in order. Resolve the serial connection before troubleshooting NTRIP or RTK status.

Problem Check
No COM port Check the data cable, USB port, SCOUT power, and USB serial driver.
COM port will not open Close other software using the port, refresh the list, and reconnect SCOUT.
NMEA is empty or unreadable Confirm the COM port and baud rate for the connected SCOUT version.
NTRIP will not connect Check the caster, port, mountpoint, username, password, and internet connection.
RTCM received does not increase Check the NTRIP session and whether the selected mountpoint is sending data.
RTCM forwarded does not increase Confirm that the SCOUT COM port remains open and the serial connection is active.
SCOUT remains Standalone or Float Move to an open-sky location, check correction age and satellite visibility, and confirm that both RTCM counters increase.
More detail is required Review the TRACE Events page and save the relevant NMEA, RTCM3, and application event logs.

Need a USB serial driver or another SCOUT utility? Visit Tools & Utilities. Need help with a test? Contact Kalmix support →

Product selection

Choosing between SCOUT and SCOUT PRO?

Compare the two receiver configurations and choose the right starting point for your integration.

View SCOUT PRO View SCOUT