Documentation & Resources

Specifications, 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.

At a glance
  • Product documentation for SCOUT PRO, SCOUT, GUIDE, and ZENITH
  • Hardware files — datasheets, mechanical drawings, 3D STEP CAD, interface schematics, and compliance certificates — also published on GitHub
  • GNSS handbook covering signal theory, accuracy statistics, and coordinate systems
  • Application Notes for NMEA 0183 and RTCM 3.x protocol integration
  • Python toolkit for GNSS/RTK developer workflows

Browse by Product

Start from the hardware you are evaluating. Each product hub links to specifications, mechanical files, interface references, protocol notes, setup guides, and compliance documents.

01 / Products
Integrated RTK G-Mouse Receivers
Module & Antenna

Browse by Resource Type

Jump directly to the type of engineering file you need — specifications, mechanical drawings, interface references, protocol notes, or compliance documents.

02 / Resource Types

Specifications

GNSS performance, electrical, environmental, and product-level technical specifications.

Mechanical

Dimensions, mounting references, housing notes, mechanical drawings, and CAD-related files.

Interface

Connector definitions, pinout references, power input, USB, UART, and board-level integration notes.

Compliance

Certification references, regulatory notes, compliance documents, and product-level declarations.

Need raw files? Datasheets, mechanical drawings, STEP files, and developer utilities are also mirrored in the public GitHub repository. github.com/KalmixTech

GNSS Handbook & Application Notes

Engineering references that go beyond product datasheets — covering signal theory, accuracy statistics, protocol structures, and field integration patterns.

03 / References
GNSS Handbook

Conceptual foundations for working with GNSS positioning — signal structure, accuracy statistics, NTRIP corrections, and coordinate systems.

How GNSS Works

One equation, four satellites — how a receiver solves position from pseudorange and clock bias.

GNSS Accuracy Decoded

RMS, CEP, R95 — why positioning accuracy is a probability distribution, not a single number.

Beyond WGS84

Why a perfect GNSS fix can still appear off the map — coordinate systems and datum shifts explained.

Application Notes

Protocol-level engineering references for integrating Kalmix GNSS receivers into your data pipeline.

Browse all engineering articles on the Blog →

Developer Tools & Ecosystem

Utilities, integration references, and ecosystem guides for engineering teams building with Kalmix GNSS hardware.

04 / Tooling
Python Toolkit

GNSS / RTK developer workflows

Command-line utilities and Python examples for parsing NMEA logs, inspecting RTCM frames, and building GNSS data workflows around Kalmix hardware.

$ pip install kalmix-gnss-toolkit $ kalmix parse --input nmea.log $ kalmix rtcm inspect --stream correction.rtcm3
Ecosystem

Built around common robotics and embedded platforms

Kalmix documentation is organized around real integration paths — USB-C receiver workflows, Android testing, NMEA and RTCM protocol handling, and robotics ecosystem resources.

  • ROS 2
  • ArduPilot
  • PX4
  • Raspberry Pi
  • NVIDIA Jetson
  • Linux
  • Android
  • Windows
  • Android integration and Mock Location workflow Guide
  • SCOUT PRO NMEA output and RTCM correction input Protocol
  • SCOUT Series tools, utilities, drivers, and datasheets Tools

Support & Contact Paths

Use the right channel for technical support, integration discussions, volume evaluation, and developer resources.

05 / Support

Need help with integration?

For setup issues, protocol questions, configuration workflows, and product-specific technical support.

Contact technical support

Evaluating Kalmix for a project?

For robotics, AGV, precision agriculture, construction machinery, and low-speed autonomous platform evaluations.

Discuss integration

Documentation FAQ

Quick answers about how Kalmix documentation is organized, where to find technical files, and how to request missing engineering resources.

06 / FAQ

Where should I start if I am evaluating a Kalmix product?

+

Start from the product section on this page. SCOUT PRO and SCOUT are integrated RTK G-Mouse receivers, GUIDE is for module-level integration, and ZENITH is the GNSS antenna accessory. Each product card links to specifications, mechanical files, protocol notes, and compliance resources.

Where can I find datasheets, mechanical drawings, and STEP files?

+

Use the Resource Type section to jump directly to specifications and mechanical documentation. Raw engineering files such as datasheets, mechanical drawings, and STEP files may also be mirrored through the Kalmix GitHub organization when available.

Are NMEA and RTCM references product-specific?

+

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.

Which documents are most useful for hardware integration?

+

For hardware integration, review the specifications, mechanical dimensions, interface or pinout pages, and compliance documents first. For software integration, review the protocol page, tools and utilities page, Android guide, and relevant Application Notes.

Do the documentation pages replace technical support?

+

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.

How often are documentation pages updated?

+

Documentation is updated as product files, integration guides, protocol notes, and compliance materials become available. For the latest product-specific documents, use this documentation hub and the linked product documentation trees.