Although SatPulse can support any module using the vendor-independent NMEA and RTCM protocols, support for protocols defined by the module vendor allows it to perform configuration and provide richer information than is available in NMEA.

SatPulse supports modules from the vendors (ordered approximately by maturity and extent of support):

Supporting a protocol involves:

  • recognizing the protocol’s packet formats; protocols differ in whether they use a single packet format for both periodic data and configuration
  • decoding the packet wire formats
  • for periodic data, mapping the decoded packets into the device-independent data model that drives time-synchronization, observability and timing
  • providing protocol-specific message types for conveniently describing protocol messages in message files
  • handling request/response correlation when sending messages defined in message files
  • providing message files to perform configuration
  • supporting high-level configuration
  • supporting conversion of raw observation messages into RINEX
  • validating the implementation with real hardware