Kalmix® SCOUT PRO
Field-deployable USB-C RTK receiver for robotics, AGV, agriculture, and low-speed autonomy.
Specifications, setup guides, integration references, hardware files, and engineering articles for the Kalmix GNSS product line. Engineered to support real-world hardware integration — from first fix to production deployment.
Start from the hardware you are evaluating. Each product hub links to specifications, mechanical files, interface references, protocol notes, setup guides, and compliance documents.
Field-deployable USB-C RTK receiver for robotics, AGV, agriculture, and low-speed autonomy.
Entry-level dual-band RTK G-Mouse for evaluation, prototyping, and open-environment deployment.
K35 series GNSS module. 24-pin LCC for board-level integration. Standard RTK and RTK+DR variants.
Entry-level K16 series L1/L5 RTK GNSS module for evaluation and prototyping. One UART interface for carrier-board integration.
Survey-grade four-system full-band GNSS antenna. IP67-rated, calibrated for stable RTK lock.
Hardware selection
Not sure which receiver fits?
Compare frequency bands, output rate, interfaces, and correction support.
Use SCOPE on Android or TRACE on Windows to connect a receiver, deliver NTRIP corrections, check RTK status, and save session logs.
Connect a USB-C GNSS receiver in SCOPE, deliver NTRIP corrections, inspect its reported RTK status, and save session logs.
Connect a GNSS receiver through a Windows COM port in TRACE, deliver NTRIP corrections, inspect its reported RTK status, and save session logs.
Jump directly to the type of engineering file you need — specifications, mechanical drawings, interface references, protocol notes, or compliance documents.
GNSS performance, electrical, environmental, and product-level technical specifications.
Dimensions, mounting references, housing notes, mechanical drawings, and CAD-related files.
Connector definitions, pinout references, power input, USB, UART, and board-level integration notes.
NMEA output, RTCM correction input, command references, and protocol integration notes.
Certification references, regulatory notes, compliance documents, and product-level declarations.
Engineering references that go beyond product datasheets — covering signal theory, accuracy statistics, protocol structures, and field integration patterns.
Conceptual foundations for working with GNSS positioning — signal structure, accuracy statistics, NTRIP corrections, and coordinate systems.
One equation, four satellites — how a receiver solves position from pseudorange and clock bias.
L1, L2, L5 — engineering trade-offs between frequency bands and receiver design choices.
RMS, CEP, R95 — why positioning accuracy is a probability distribution, not a single number.
Why a perfect GNSS fix can still appear off the map — coordinate systems and datum shifts explained.
Protocol-level engineering references for integrating Kalmix GNSS receivers into your data pipeline.
Developer reference for parsing NMEA 0183 data from Kalmix GNSS receivers, including core sentence fields.
Developer reference for RTCM 3.x binary frames, MSM messages, masks, and field-level parsing.
Code examples, interface documents, and protocol references for engineering teams building with Kalmix GNSS hardware.
Run Python examples for NMEA 0183 parsing, checksum validation, coordinate handling, GSV reassembly, and RTK fix transitions. NTRIP and RTCM utilities are planned.
Review module interfaces, receiver protocol details, and USB driver notes when bringing a Kalmix device into your software.
Get technical support, explore existing integrations, or find support for a project you plan to share publicly.
For setup issues, protocol questions, configuration workflows, and product-specific technical support.
Contact technical supportSee which Android apps and field workflows are verified with Kalmix receivers, and how each correction path is set up.
Explore integrationsExplore support for hardware integrations, software workflows, and SCOUT accessories you plan to share publicly.
Community Partnership ProgramQuick answers about how Kalmix documentation is organized, where to find technical files, and how to request missing engineering resources.
Choose the path that matches your task. Use Browse by Product when evaluating a receiver, module, or antenna, and Resource Types to find a specific engineering reference. For module evaluation and carrier-board integration, start with the GUIDE documentation or NOMAD documentation. For software controls and session logging, use the SCOPE or TRACE guides under Software & Setup. For existing app and field workflows, see Integrations.
Use Software & Setup to open the TRACE User Guide or the TRACE product page, where the download is available. For SCOUT-specific connection, COM-port, NTRIP, and RTK-status steps, follow Start with Windows from either SCOUT product card.
Use the Resource Type section to jump directly to specifications and mechanical documentation. Public hardware resources are also available through the Kalmix Hardware repository when listed.
Product protocol pages describe the relevant NMEA output, RTCM correction input, and configuration notes for each hardware line. The Application Notes provide broader protocol-level references for developers building parsers, tools, or GNSS data pipelines.
For GUIDE or NOMAD module integration, review the specifications, mechanical dimensions, pin definitions, protocol, and compliance pages, then plan the carrier board, power supply, antenna, and host connection. NOMAD provides one UART interface; start with its pin definitions and interfaces and protocol reference. For SCOUT or SCOUT PRO setup, follow the Android or Windows links in the product cards. For detailed SCOPE controls and session logs, see the SCOPE User Guide. For custom software, continue with the Toolkit and Application Notes.
No. The documentation is designed to answer standard evaluation and integration questions. If your setup involves a specific host platform, custom firmware requirement, volume integration workflow, or missing file request, contact Kalmix support with the product model and integration context.