Add support for Septentrio receivers (mosaic-G5 and mosaic-X5, and family) so satpulse can use them as a GPS/time source. Septentrio outputs GNSS data as SBF (Septentrio Binary Format) and is configured over a line-based ASCII command interface.
This issue is the core: the essential support that makes a Septentrio receiver usable -- SBF decode, conversion to the device-independent gpsprot Msg set (time/PPS, position, velocity, satellites, leap seconds, quality), and Tier 2 message-file configuration. Both models are supported (they share the SBF format and the command interface); initial hardware testing is on the G5, the hardware in hand.
Three pieces, fairly decoupled (the conversion depends on the codec; the message-file layer is independent of both):
High-level (Tier 1) configuration and RINEX observation output are separate follow-up issues.
See plan/septentrio-core.md.
Add support for Septentrio receivers (mosaic-G5 and mosaic-X5, and family) so satpulse can use them as a GPS/time source. Septentrio outputs GNSS data as SBF (Septentrio Binary Format) and is configured over a line-based ASCII command interface.
This issue is the core: the essential support that makes a Septentrio receiver usable -- SBF decode, conversion to the device-independent gpsprot Msg set (time/PPS, position, velocity, satellites, leap seconds, quality), and Tier 2 message-file configuration. Both models are supported (they share the SBF format and the command interface); initial hardware testing is on the G5, the hardware in hand.
Three pieces, fairly decoupled (the conversion depends on the codec; the message-file layer is independent of both):
gps/lib/sbfbinplus the packet scanner and a do-nothing PacketProcessorgps/internal/septentrio, the nav-epoch model, and registrationconfigs/gpsmsg/septentrio/, with the$Rreply packet format and the"septentrio"response analyzerHigh-level (Tier 1) configuration and RINEX observation output are separate follow-up issues.
See
plan/septentrio-core.md.