hardware-test-gps-msgs

GPS hardware testing validates the gpsprot message pipeline by automating the collection, decoding, and plausibility verification of raw binary packets. You build satpulse, configure the serial device, enable messages, and collect logs for end-to-end validation.

End-to-end GPS pipeline validation requires building satpulse, configuring the serial device and speed, and enabling desired GPS messages via --pvt-out or message-file based configuration using -m and -t flags before collecting logs.

Satpulsed message enablement configures GPS output using either full configuration with --pvt-out or message-file based configuration with -m and -t flags, allowing you to collect specific GPS logs for subsequent decoding and plausibility checks.

GPS data plausibility verification is automated by applying log decoding and plausibility checks to collected events and packets. This confirms raw binary packets are correctly parsed and decoded into valid gpsprot data.

GPS hardware testing applies specifically in development environments where real GPS hardware is available. You need physical GPS devices connected via serial interfaces to build, run satpulsed, and collect meaningful test logs.