rtcm3-knowledge-patch

Name: rtcm3-knowledge-patch
Availability: InStock
Author: Nevaberry

Parse and validate RTCM3 frames and NTRIP connections for GNSS correction streams.

22|Updated Jan 22, 2026

Search Tags:#parsing #rtk #gnss #rtcm3 #ntrip #crc-24q #msm

Ready to run

npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill rtcm3-knowledge-patch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rtcm3-knowledge-patch
Source: https://github.com/Nevaberry/nevaberry-plugins/tree/main/plugins/rtcm3-knowledge-patch/skills/rtcm3-knowledge-patch
Command: npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill rtcm3-knowledge-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides up-to-date protocol knowledge and parsing guidance to avoid stale GNSS corrections, broken NTRIP connections, and incorrect RTCM3 frame handling that lead to RTK failures.

Core Features & Use Cases

Frame parsing: Detailed byte-level layout for RTCM3 frames including preamble, 10-bit length extraction, payload decoding, and CRC-24Q verification.
Message semantics: Explanation of MSM vs legacy observations, MSM subtype recommendations (MSM4/MSM7), and common message type ranges for GPS, GLONASS, Galileo, BDS, and others.
NTRIP guidance: Differences between NTRIP v1 and v2, authentication, sourcetable usage, and VRS/GGA requirements for client implementations.
Operational notes: SSR phase summaries, timestamp alignment fixes for 1 ms issues, and practical rules for choosing message formats in RTK/PPP workflows.

Quick Start

Parse the incoming RTCM3 byte stream, validate the CRC-24Q, extract the 12-bit message type, and choose MSM or legacy handling to determine how to interpret the payload.

Frequently Asked Questions about rtcm3-knowledge-patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I parse RTCM3 frames and verify CRC-24Q for GNSS correction streams?▼

To parse RTCM3 frames, extract the 10-bit payload length, decode the payload, and verify the CRC-24Q checksum to ensure frame integrity for GNSS correction streams. This prevents broken NTRIP connections and RTK failures.

What is the difference between MSM and legacy RTCM3 message types?▼

MSM (Multiple Signal Message) and legacy RTCM3 message types differ in payload structure and satellite observation handling. MSM offers detailed phase and range data with subtypes like MSM4 and MSM7, whereas legacy types provide basic GPS, GLONASS, Galileo, and BDS observations.

How do I set up an NTRIP v2 client connection for RTK corrections?▼

Setting up an NTRIP v2 client connection involves handling authentication, querying the sourcetable for available streams, and sending VRS/GGA position data to the caster to receive RTK corrections properly.

Why is my RTCM3 timestamp alignment causing 1 ms issues in RTK workflows?▼

Timestamp alignment issues causing 1 ms errors in RTK workflows stem from incorrect payload decoding or SSR phase interpretation. Validating the 12-bit message type and applying timestamp alignment fixes ensures accurate RTK and PPP corrections.

Does this parsing approach support multiple GNSS constellations like BDS and Galileo?▼

Yes, this RTCM3 parsing approach supports multiple GNSS constellations including GPS, GLONASS, Galileo, and BDS. It handles both MSM and legacy message type ranges specific to each constellation for comprehensive correction stream integration.

What are the limitations of using legacy RTCM3 messages instead of MSM for GNSS observations?▼

Legacy RTCM3 messages lack the high-resolution phase and range data density found in MSM formats. Using legacy types limits SSR phase interpretation and timestamp alignment precision, making MSM4 or MSM7 better for advanced RTK and PPP workflows.