RTCM 3.0 Support

[vguttmann]

Currently, pyGPSClient doesn't support RTCM 3.0, at least as far as I can tell. The correction service offered by my state (SAPOS Bayern) only supports RTCM 3.0, which, according to SAPOS Support, requires an NMEA Position for them to interpolate between their antennas, which pyGPSClient currently does not send over.
Since pyGPSClient is based on pyGNSSUtils, which already supports RTCM 3, the only thing that would be needed is software support on the side of pyGPSClient, I would think.

[semuadmin]

Hi @vguttmann

PyGPSClient does support RTCM 3.0 (via the pyrtcm library, which is the same library used by pygnssutils) and it does support the sending of NMEA GGA position sentences for those casters that require it. You simply have to set the GGA Interval field to the required send interval in seconds, e.g.:

Are you sure you have the NTRIP client correctly configured? What specific response are you getting from the SAPOS caster?

[vguttmann]

Ahh, that makes sense then. Before setting that field, I was just getting a timeout from SAPOS.

I don't have an RTK fix yet, but the RTK light on my uBlox does occasionally light up, so it's a thing my uBlox doesn't do, and not a software problem any more.

What confused me that I was only able to set 1.0 and 2.0 as a protocol version, perhaps that should be 2.0+ then?

[semuadmin]

Here, for example, is a screenshot from PyGPSClient illustrating an rtk2go.com caster in the Munich area:

You can see the outgoing NMEA GPGGA sentence at the top of the console, mixed in with the incoming RTCM 3 messages.

What confused me that I was only able to set 1.0 and 2.0 as a protocol version, perhaps that should be 2.0+ then?

This refers to the NTRIP protocol version, not the RTCM protocol version. The specific RTCM 3 protocol implemented by the mountpoint (3.1, 3.2, 3.3 - all are supported by pyrtcm) is listed in the sourcetable entry, e.g:

[vguttmann]

Is that a macOS thing, or how do I enable color in the console?

[semuadmin]

Is that a macOS thing, or how do I enable color in the console?

You read the README - available on all OS, not just MacOS ;-)

Basically, you manually edit the *.json configuration file to add a series of user-defined [string, color] tags to a colortags_l list element - e.g:

"colortag_b": 1,
"colortags_l": [
        [
            "NMEA",
            "lightblue1"
        ],
        [
            "UBX",
            "green3"
        ],
        [
            "RTCM",
            "coral1"
        ],
        [
            "SPARTN",
            "maroon1"
        ],
        [
            "NTRIP",
            "#9f30c1"
        ],
        [
            "MQTT",
            "#a53570"
        ],
        [
            "GNTXT",
            "red"
        ],
        [
            "carrSoln=2",
            "cyan"
        ],
        [
            "carrSoln=1",
            "deepskyblue"
        ],
        [
            "txbuf alloc",
            "red"
        ],
        [
            "UNKNOWN PROTOCOL",
            "red"
        ],
        [
            "ERROR",
            "HALT"
        ],
        [
            "WARNING",
            "red"
        ]
    ],