SCOPE for Android User Guide
SCOPE is an Android workspace for compatible GNSS receivers connected through USB-C. Use it to open the receiver stream, deliver NTRIP corrections, inspect live positioning data, and keep session logs on the Android device.
What SCOPE does
One mobile workspace for a GNSS receiver session.
SCOPE reads the connected receiver’s data, displays the solution reported by that receiver, and can pass RTCM corrections from an NTRIP service back through the active connection. The receiver calculates its position and solution state; SCOPE makes that session easier to configure, monitor, and record.
Open the receiver stream
Select the appropriate USB serial type and matching baud rate, then connect the receiver.
Deliver corrections
Configure an NTRIP source and monitor the incoming RTCM correction stream.
Validate the session
Review NMEA, map, skyplot, solution status, and optional local log files.
Before you start
Prepare the Android device, receiver, and correction service
App version
This guide covers SCOPE v1.0.7.
Verified Android
Android 15 and Android 16.
Verified receivers
Kalmix SCOUT and SCOUT PRO over USB-C.
The screenshots and instructions below reflect the verified release scope. Android menu names can vary by phone or tablet manufacturer.
- Android phone or tablet: it must run Android 15 or 16, support USB Host / OTG operation, and have SCOPE v1.0.7 installed from the official Kalmix download page.
- USB-C GNSS receiver: the verified workflow covers Kalmix SCOUT and SCOUT PRO. SCOPE is not artificially restricted to Kalmix hardware: another receiver may work when it exposes a compatible USB serial interface, outputs standard NMEA, uses a baud rate available in the app, and accepts the required correction input. Third-party receiver compatibility is not guaranteed until that exact setup has been validated.
- Open-sky environment: use a clear view of the sky when evaluating satellite reception or expecting an RTK solution.
- NTRIP details, when corrections are required: host address, port, mountpoint, and, where required, username and password.
USB permission and OTG: when Android asks to allow SCOPE to access the USB device, approve the request. If the receiver is not detected, check the cable and the Android device’s USB Host / OTG setting before changing app settings.
Navigation
Menu overview
Tap the menu icon in the upper-right corner to move between the main workspace and supporting views. The menu groups receiver monitoring under Status and correction functions under Corrections.
Device
Connect a compatible USB-C receiver
Open Device before configuring corrections. This page defines how SCOPE communicates with the connected receiver. Select the settings required by the receiver, then tap Connect. When the connection opens, the fields are locked and the button changes to Disconnect.
- Choose Device Type. Use USB Serial for the standard SCOUT Series workflow. Use Super USB Serial for the validated high-rate SCOUT PRO RTK+DR configuration, including output at up to 20 Hz. This is a verified Kalmix configuration, not a universal 20 Hz cutoff for every third-party receiver.
- Choose the receiver’s Baud Rate. The available list includes 9600, 19200, 38400, 57600, 115200, 230400, 460800, and 921600 bps. The app and receiver must use the same value.
- Confirm the detected Serial Port. In most cases, leave the default port selected; it does not need to be changed. Then tap Connect.
- Use Mock Location only when Android system-location testing is needed. In Android Developer options, select SCOPE under Select mock location app, then return to SCOPE and enable the switch. This setting is not required to read receiver data or deliver RTCM corrections.
- When you finish, tap Disconnect before unplugging the receiver or ending the session.
Verified high-rate setup: SCOPE v1.0.7 has been validated with SCOUT PRO RTK+DR at up to 20 Hz. Match the receiver configuration, Device Type, and baud rate; the verified high-rate SCOUT PRO RTK+DR path uses Super USB Serial.
If the receiver does not connect: disconnect, verify the cable and Android USB permission, then check the device type and baud rate against the receiver’s documentation. A connected USB device alone does not confirm that its serial stream is using the selected settings.
Dashboard
Read the live session at a glance
The Dashboard is the quickest way to confirm whether the receiver is connected and what solution it is reporting. Most of its live positioning information is parsed from the receiver’s NMEA stream: GGA provides UTC time, coordinates, elevation, position status, correction age, satellites in use, and HDOP, while GSV provides the constellation and visible-satellite counts used in the satellite summary. SCOPE presents the state reported by the connected receiver; it does not calculate the GNSS or RTK solution itself. A recent correction age is useful context, but does not by itself prove that the receiver has reached RTK Fixed. Refer to the Appendix for definitions of the reported position states.
GNSS RECEIVER is the current receiver-connection indicator. Check this card to quickly confirm whether the receiver is connected or disconnected. The MOCK LOCATION card shows the current switch state, so you can immediately see whether Mock Location is enabled or off.
Status · NMEA
Inspect decoded NMEA data and the live stream
The NMEA page provides three decoded views and a live NMEA stream. The green Streaming label confirms that the page is receiving data. The Auto-scroll Active switch controls whether the stream automatically scrolls as new NMEA data arrives; turn it off to pause scrolling while you review the currently displayed data.
GGA
Shows UTC time, latitude, longitude, quality indicator, satellites in use, HDOP, and altitude.
RMC
Shows the receiver’s minimum navigation data, including time, position, validity, speed, course, and date when present.
GSA
Shows active-satellite and dilution-of-precision information reported by the receiver.
Corrections · Source
Configure an NTRIP correction source
Open Corrections → Source after the receiver connection is active. Enter the NTRIP service values supplied by your correction provider, use Sourcetable when you need to select a published mountpoint, save the settings, and tap Connect.
After the source is connected, open Corrections → RTCM to review the incoming correction stream. MESSAGES shows the number of messages received through the current connection; BYTES shows the amount of correction data received; and AGE (S) shows the age, in seconds, of the most recently received correction data.
- Enter the caster Host Address and Port.
- Enter or select the Mountpoint. Use Sourcetable only with the service you intend to use.
- Enter Username and Password if the correction service requires authentication. Both fields are optional in the interface because some services do not require them.
- Enable Send NMEA GGA to Base Station when the provider specifies a VRS or NEAR stream that needs the rover position.
- Choose Auto-Reconnect if you want SCOPE to try to reconnect after an interruption.
- Turn on SAVE to store the current correction-service settings on this Android device for later use. Then tap Connect.
Service credentials: use only the values provided by your correction-service operator. A successful NTRIP connection confirms that SCOPE is receiving from the service; use the RTCM page and the receiver’s reported position status to review the end-to-end result.
Corrections · RTCM
Monitor the RTCM correction stream
The RTCM page shows whether raw correction data is currently arriving. Its summary counts Messages, Bytes, and Age (s); the raw monitor displays the incoming stream. A green Streaming state and advancing counts indicate that SCOPE is receiving data from the source.
Enable Save RTCM Log only when you need a local copy of the incoming correction stream. The Stop RTCM control ends the active RTCM stream. Stop or disconnect controls can appear on the RTCM, Source, and Device pages because they close different layers of the session.
When you finish, stop the RTCM stream first. Return to Corrections → Source and disconnect the NTRIP source if it still shows an active connection, then disconnect the receiver on the Device page.
The Auto-scroll Active switch controls whether the raw RTCM monitor automatically scrolls as new data arrives; turn it off to pause scrolling while you review the displayed data. This switch does not affect whether corrections are received.
Status · Map
Review position and solution status on the map
The Map view places the receiver’s reported position on the map and retains the session summary at the top: latitude, longitude, elevation, number of satellites, solution status, and HDOP. Use + and − to change zoom; use the target icon to center the view on the current position. Drag the map to pan and view other areas.
The marker and status update from the connected receiver. The view is valuable for confirming that the location is plausible, but it should be read together with the status, NMEA, correction age, and skyplot information. Refer to the Appendix for definitions of the reported position states.
Status · Skyplot
Inspect satellite visibility and signal strength
Skyplot provides context when the reported solution is weak, unstable, or taking time to converge. The global skyplot locates tracked satellites by direction and elevation. The constellation summary shows the used/tracked count for GPS, BDS, GLO, GAL, and QZSS. The SNR charts show signal-to-noise ratio in dB-Hz for the satellites reported under each constellation.
Use this view to compare signal availability and geometry with the Dashboard status. A clear, stable view of the sky and continuous corrections normally provide more favorable conditions than obstructed reception, but the receiver remains the source of the actual solution state.
Logs
Save the data needed for session review
Use Logs to control local logging for the overall SCOPE session. Turn on only the categories that are useful for the task, then tap Save to apply the selection.
Output Data of GNSS Receiver
Saves the GNSS receiver’s NMEA output data.
RTCM Stream Data
Logs incoming RTCM correction streams.
System Events & Status
Records running events and error logs for troubleshooting.
Log only the data you need and protect exported session files according to your project’s privacy and data-handling requirements. Receiver logs and system events can contain location or connection information.
Troubleshooting
Check the session in layers
Resolve the USB receiver connection before troubleshooting NTRIP, RTCM, or the final solution state. A connected source alone does not prove that corrections are reaching the receiver or that the receiver has reached RTK Fixed.
| Problem | Check |
|---|---|
| Receiver is not detected | Check the data-capable USB-C cable, USB Host / OTG support, Android USB permission, and receiver power. |
| Device connects but NMEA is empty or unreadable | Confirm Device Type, baud rate, serial port, and that the receiver is outputting standard NMEA on the active interface. |
| NTRIP source will not connect | Check the network, caster address, port, mountpoint, credentials, and whether the service requires rover GGA. |
| RTCM Messages and Bytes do not increase | Confirm that the source is connected, the selected mountpoint is active, and the network remains available. |
| Receiver remains Single, DGPS, or Float | Check correction age, correction continuity, open-sky visibility, satellite geometry, receiver configuration, and convergence time. |
| A downstream app does not use the SCOPE position | Confirm that SCOPE is selected as Android’s mock-location app, the SCOPE switch is enabled, and the downstream app accepts Android system location and mock-location input. |
About
Find app, document, and support information
The About page provides a direct path to Kalmix hardware, documents, email support, and the Kalmix website. It also displays the installed SCOPE version. Include the app version, Android device model, receiver connection settings, and relevant logs when contacting support about a technical issue.
Tap BUY GNSS RECEIVER to open the KALMIX SCOUT Series product page. Tap GET DOCUMENTS to open the KALMIX website documentation page and find related product and support information.
Appendix A
Dashboard Position Status Reference
The reference below explains the common Position Status labels shown on the Dashboard. Use it to connect the receiver-reported state with its usual meaning and the most useful next check during a session.
| Reported state | Meaning | What to check next |
|---|---|---|
| No Fix | The receiver is not reporting a valid GNSS position. | Check the receiver connection, antenna environment, and NMEA stream. |
| Single | A standard GNSS position is available without differential or RTK positioning. | Check correction-source settings and the RTCM monitor when corrections are required. |
| DGPS | The receiver reports a differential solution; it is not a fixed carrier-phase RTK solution. | Check correction continuity, age, sky view, and the receiver’s supported modes. |
| RTK Float | The receiver is using RTK corrections, but its carrier-phase ambiguities are not fixed. | Allow convergence time and check clear sky view, correction age, and satellite geometry. |
| RTK Fixed | The receiver reports a fixed RTK solution. | Continue monitoring or enable the logs needed to retain session evidence. |
| Inertial / DR | On a supported RTK+DR receiver, the reported solution may be dead-reckoning assisted during degraded GNSS conditions. It is not the same as RTK Fixed. | Check receiver initialization, motion conditions, GNSS visibility, and whether corrections have recovered. |
Appendix B
Recommended SCOPE Workflow
Use the following sequence as a practical workflow for a standard receiver session. The exact settings remain dependent on the connected receiver and correction service.
Phase 1
Prepare and connect
Connect the USB device to the Android device.
Launch the SCOPE app and allow USB access when Android requests permission.
Open Logs and choose the data categories to save locally, if logs are required.
Open Device, set the device type and baud rate, enable Mock Location if Android system-location testing is required, then tap Connect.
Open Status, then select NMEA to confirm that receiver data is streaming.
Phase 2
Correct and review
Open Corrections, select Source, configure the correction service, and tap Connect.
Under Corrections, open RTCM to confirm that correction data is streaming.
Open Dashboard to monitor current positioning information.
Under Status, open Skyplot to monitor satellite visibility and signal strength.
Under Status, open Map to review the reported position.
Phase 3
Finish and retain
Under Corrections, open RTCM and tap Stop RTCM.
Return to Source under Corrections and tap Disconnect if the source still shows an active connection.
Return to Device and tap Disconnect to close the USB connection.
Close SCOPE.
Review the locally saved log files, if logging was enabled.