Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AP_GPS: added GPS_DRV_OPTIONS for fully parsing RTCMv3 injection #26317

Merged
merged 3 commits into from
Mar 6, 2024
Merged

AP_GPS: added GPS_DRV_OPTIONS for fully parsing RTCMv3 injection #26317

merged 3 commits into from
Mar 6, 2024

Commits on Mar 4, 2024

  1. GCS_MAVLink: pass channel number to AP_GPS on RTCM injection

    @tridge
    tridge committed Mar 4, 2024
    Configuration menu
    Copy the full SHA
    29e9dfc View commit details
    Browse the repository at this point in the history

  2. AP_Periph: allow for RTCMv3 packets larger than 300 bytes 

    with newer receivers, RTCMv3 packets can be larger than 300
    @tridge
    tridge committed Mar 4, 2024
    Configuration menu
    Copy the full SHA
    1b549d8 View commit details
    Browse the repository at this point in the history

  3. AP_GPS: added option to decode RTCM injected data 

    this allows for redundent RTCM links (eg. WiFi and SiK links for light
show drones) without causing corruption into the GPS.

If the GPS_DRV_OPTION bit is set then we instantiate a separate RTCM3
decoder per mavlink channel, and only inject when we get a full packet
that passes the RTCM 24 bit CRC
    @tridge
    tridge committed Mar 4, 2024
    Configuration menu
    Copy the full SHA
    74d2c97 View commit details
    Browse the repository at this point in the history