01
ENTRY-LEVEL MODULE
NOMAD K16C · Standard RTK
Entry-level RTK tests, education, and early custom-board prototypes using one UART interface.
Kalmix RTK Hardware
RTK GNSS Receivers and Modules
Browse Kalmix RTK hardware by form factor, then compare the configuration and integration work your system requires.
2 hardware forms 8 configurations
Four expanding boundaries show the path from a GNSS module to a
development board, an integrated receiver, and a complete survey
system.
HARDWARE FORMS
Choose a GNSS receiver or RTK module configuration for your system
Start with the hardware boundary: what your team needs to own, what Kalmix currently provides, and which configuration can carry into the next project stage.
CUSTOM OEM HARDWARE
RTK GNSS Module
A surface-mount GNSS module for teams building the carrier board, RF path, antenna integration, host interfaces, enclosure, and production design.
Also called
GPS module or GNSS module. RTK module, RTK GPS module, and RTK GNSS module are common names for correction-capable positioning.
Choose it when
You need the positioning layer to become part of your own product architecture rather than remain an external device.
Your team still owns
Carrier-board design, RF and antenna integration, power, mechanics, firmware integration, validation, and production.
Kalmix supply Kalmix currently offers 4 RTK GNSS module configurations across NOMAD K16 and GUIDE K35.
02
ENTRY-LEVEL MODULE
NOMAD K16E · RTK + DR
Moving-platform prototypes evaluating GNSS and inertial integration through one UART interface.
03
OEM MODULE
GUIDE K35C · Standard RTK
Custom carrier boards and embedded receivers that need standard RTK positioning with board-level interfaces.
04
OEM MODULE
GUIDE K35E · RTK + DR
Embedded products with board-level ownership that need to evaluate an RTK + DR path through brief GNSS interruptions.
FIELD & MACHINE INTEGRATION
Integrated GNSS Receiver
A packaged GNSS receiver combining positioning electronics, antenna path, host connection, cable, and housing for external installation on a host system.
Also called
GPS receiver or GNSS receiver. RTK receiver, RTK GPS receiver, and RTK GNSS receiver describe a correction-capable receiver.
Choose it when
You want to connect, mount, and test a positioning system without designing the complete GNSS hardware stack.
Your team still owns
Host software, correction delivery, mounting, cable routing, installation, and application-level validation.
Kalmix supply Kalmix currently offers 4 integrated GNSS receiver configurations across SCOUT and SCOUT PRO.
05
SCOUT · Standard RTK
Cost-conscious evaluation, education, early prototypes, and open-sky deployment using a packaged USB-C receiver.
06
SCOUT · RTK + DR
Moving-platform evaluation that needs a higher-rate RTK + DR path and route-specific validation.
07
FIELD & MACHINE
SCOUT PRO · Standard RTK
Field-machine and outdoor robotics integration that needs a packaged L1/L5 receiver with standard RTK.
08
FIELD & MACHINE
SCOUT PRO · RTK + DR
Field-machine and outdoor robotics integration that needs an RTK + DR path and validation on the intended route and installation.
All Kalmix configurations 8 across 2 hardware forms
Need product-specific setup details? Open Documentation
| Configuration | Configuration difference | Host / interface | Antenna & integration boundary |
|---|---|---|---|
| RTK GNSS Modules Your team owns the carrier PCB, RF path, power, enclosure, firmware integration, and production validation. | |||
| NOMAD K16C · Standard RTK | Standard RTK at 1 Hz for entry-level evaluation and prototypes. | One UART interface for host data and corrections. | External antenna and carrier-board RF path required. |
| NOMAD K16E · RTK + DR | RTK + DR prototype path with BMI325; up to 10 Hz (1 Hz default). | One UART interface for host data and corrections. | External antenna and carrier-board RF path required. |
| GUIDE K35C · Standard RTK | Standard RTK configuration at 1 Hz. | UART, I²C, and PPS are the relevant module interfaces. | External antenna and RF path required. |
| GUIDE K35E · RTK + DR | RTK + DR configuration at 10 Hz; SPI is supported for the module integration path. | UART, I²C, PPS, and SPI where the final design requires it. | External antenna and RF path required. |
| Integrated GNSS Receivers Kalmix packages the receiver, antenna path, cable, and housing; your team owns host, corrections, mounting, installation, and validation. | |||
| SCOUT · Standard RTK | Standard RTK configuration at 1 Hz; BMI325 is not active in this configuration. | USB-C serial connection to the intended host. | Integrated antenna; validate the installed sky view. |
| SCOUT · RTK + DR | RTK + DR configuration at 10 Hz with BMI325 IMU; it does not make every obstructed route equivalent to open sky. | USB-C serial connection to the intended host. | Integrated antenna; validate the installed sky view and route. |
| SCOUT PRO · Standard RTK | Standard RTK configuration at 1 Hz for a packaged L1/L5 field-machine or outdoor-robotics path. | USB-C serial connection to the intended host. | Integrated antenna; validate placement, sky view, and installation. |
| SCOUT PRO · RTK + DR | RTK + DR configuration at 10 Hz with LSM6DSR IMU for route-specific field-machine or outdoor-robotics validation. | USB-C serial connection to the intended host. | Integrated antenna; validate placement, sky view, installation, and route. |
OTHER VALID FORM FACTORS
These forms solve different integration problems. They remain here to clarify the decision boundary, not as Kalmix product categories.
BENCH EVALUATION
Development Board
A GNSS module on an accessible board for electrical evaluation, firmware work, and interface testing before a production hardware architecture is fixed.
Kalmix supply Kalmix does not currently offer a dedicated development board.
For quick NMEA and correction tests, start with a packaged receiver. For your own board, consider NOMAD K16 for evaluation and early prototypes, or GUIDE K35 for OEM integration. A development board still needs deployment validation.
SURVEY & MAPPING
Survey GNSS System
A complete survey setup combining a receiver, controller, field software, and measurement workflow.
Kalmix supply Kalmix does not currently offer a complete survey GNSS system.
For receiver-only field collection with your existing host and app, compare SCOUT and SCOUT PRO above.
RECEIVER SELECTOR
Narrow the hardware choice in three questions
Use the project constraints you already know to choose a starting path. The result is a form-factor recommendation, not a substitute for integration and field validation.
YOUR RECOMMENDED STARTING PATH
Answer the first question to establish a direction.
WHY THIS PATH
VERIFY BEFORE CHOOSING
SELF-CHECK BEFORE COMPARING
Ownership → operating environment → project stageStart With an RTK GNSS Module
You own the carrier board, RF path, antenna, power, and mechanics. NOMAD K16 supports entry-level evaluation and early prototypes; GUIDE K35 supports OEM product integration.
Compare GNSS Modules →Start With an Evaluation-Friendly Receiver
You need real NMEA output and correction testing before the production hardware architecture is fixed. Kalmix has no dedicated development board; SCOUT is an external evaluation path.
View SCOUT →Start With an Integrated GNSS Receiver
You want to reduce GNSS hardware work and move into host integration, mounting, and field validation. SCOUT and SCOUT PRO are packaged receiver paths.
View SCOUT PRO →Start With a Survey GNSS System Workflow
You need a complete field setup, including the controller, survey software, and measurement workflow. Kalmix does not currently offer a complete survey GNSS system.
Discuss your workflow →SELECTION CHECKS
Seven checks before you compare specifications
A specification sheet is only useful after these system decisions are clear. Use these checks to separate a promising receiver from one that will work in the final product.
RTK module, board, or packaged receiver?
DECISION IMPACT
Sets ownership for PCB, antenna, enclosure, mounting, and validation.
VERIFY
Set the responsibility boundary before comparing chipsets.
What must the receiver connect to?
DECISION IMPACT
USB-C suits host setup; UART, I²C, PPS, and SPI suit embedded design.
VERIFY
Check connector, voltage, driver, data rate, and host data flow.
Single-band or dual-band GNSS?
DECISION IMPACT
Band support changes available signals and expected RTK behavior.
VERIFY
Verify final-SKU bands and constellations, not chipset family.
Compare full GNSS specificationsOpen sky or repeated obstruction?
DECISION IMPACT
Sky conditions change the variant, test route, and validation plan.
Integrated antenna or custom RF path?
DECISION IMPACT
A module adds RF work; a receiver reduces antenna integration.
VERIFY
Confirm mounting, sky view, cable routing, nearby metal, and noise.
How will RTK corrections reach the receiver?
DECISION IMPACT
RTK needs a correction source, host path, and loss behavior.
07Evidence & Support
Can the team reproduce and explain the result?
Specifications shortlist hardware; documentation, logs, test context, and support determine whether the integration can be debugged and maintained.
VERIFY
Look for protocols, mechanical references, tools, test conditions, and a clear support path.
This is the only check about your team, not the hardware.
Open DocumentationVALIDATE YOUR SHORTLIST
Validate the complete integration before deployment
Define the acceptance criteria, test the intended antenna, correction path, host, mounting, route, and operating conditions, then read every result with its documented limitations.
-
Define the Acceptance Criteria
Set measurable requirements for error, availability, degraded states, and a route that represents deployment.
Acceptance criteria -
Test the Complete Integration
Use the intended antenna, mounting, correction path, host connection, motion, and obstruction conditions.
Test logs -
Read the Evidence in Context
Review the route, reference method, solution states, error distribution, degraded periods, and stated limitations.
Evidence-based decision
GUIDE K35E GROUND TRUTH FIELD RECORD
- Documented route
- 58.8 km
- Valid test epochs
- 69,901
- Replayable contexts
- 4 scenarios
Published field result
1.5 cm CEP50 and 99.78% of RTK Fixed epochs below 10 cm.
Module-level result from one documented setup, route, reference method, and analysis window; not a universal claim for every Kalmix product or deployment.
Run and Record the Test
Use TRACE to connect, forward corrections, monitor receiver status, inspect the skyplot, and save test logs.
Get TRACE for WindowsConfirm the Design-In Details
Review interfaces, protocols, mechanical references, compliance files, and product-specific integration documentation.
Open DocumentationDECISION FAQ
GNSS Receiver Selection FAQ
Quick answers to the questions that most often change the receiver form, integration path, or Kalmix starting point.
What is the difference between a GPS receiver and a GNSS receiver?
GPS is one satellite navigation constellation. GNSS is the broader category that can include GPS, Galileo, BeiDou, GLONASS, QZSS, and other supported systems. Many products are still called GPS receivers even when they track several constellations. Compare the exact signals supported by the final product, not only the category name.
Should I choose an RTK module or an integrated RTK receiver?
Choose an RTK module when your team needs control over the PCB, RF path, antenna, power, interfaces, enclosure, and production architecture. Choose an integrated receiver when you want to reduce GNSS hardware work and move faster into host integration, mounting, and field validation.
When is a development board the better choice?
A development board is useful when you need accessible interfaces for bench evaluation, firmware work, and early correction testing before the production architecture is fixed. It is not automatically deployment-ready; the final system may still need a custom antenna, enclosure, cable, mount, and carrier board.
Does an RTK-capable GNSS receiver provide centimeter accuracy by itself?
No. RTK-capable hardware needs suitable satellite measurements, a compatible correction source, and a working data path that delivers corrections to the receiver. Installation, obstruction, multipath, correction age, solution state, and the application’s validation method also affect the result. For the system-level explanation, read What Is RTK GPS.
Which Kalmix option fits a first RTK evaluation?
SCOUT is the packaged receiver path for entry-level RTK evaluation. Choose NOMAD when evaluation or an early prototype requires your own carrier board and one UART interface. GUIDE is the OEM module path, while SCOUT PRO is the packaged receiver path for field-machine and outdoor robotics integration. Validate the intended host, antenna, and correction workflow.
Which Kalmix option fits a custom embedded product?
NOMAD and GUIDE both require a custom carrier board, external antenna, power supply, and host integration. NOMAD focuses on entry-level evaluation and early embedded prototypes; GUIDE focuses on OEM product integration. SCOUT and SCOUT PRO provide packaged receiver paths when you prefer an external device.
What should I check when comparing a Duro GNSS receiver with Kalmix?
Compare the exact Duro model with the Kalmix configuration you are considering. Check host interfaces, position output, correction input, field-software support, and mounting requirements. SCOUT and SCOUT PRO are packaged receiver paths; NOMAD and GUIDE require board-level integration. Validate the complete workflow before treating a Kalmix configuration as a replacement.
How should I choose between NOMAD and GUIDE?
Choose NOMAD K16 for entry-level RTK evaluation, education, and early custom-board prototypes using one UART interface. Choose GUIDE K35 for OEM product integration after checking its documented interfaces and configuration. In either family, C is the RTK option and E is the RTK+DR option. Both require your own board, antenna, power, correction delivery, and application-specific validation.
STILL DECIDING
Not sure which configuration fits your integration?
Share your host, application, operating environment, correction source, project stage, and expected volume. We’ll help identify the more practical starting point before you commit to a receiver form or production design.