[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Overlong RTCM3 packets from EUREF-IP

From: kross
Subject: Re: Overlong RTCM3 packets from EUREF-IP
Date: Tue, 29 Sep 2020 17:02:40 +0200

RTCM Version 3 Frame Structure is:
1 octet preamble
2 octets payload length (first 6 bits reserved) --> max payload length 1023 octets
0-1023 octects payload
3 octets CRC
Kind regards,
Gesendet: Dienstag, 29. September 2020 um 16:43 Uhr
Betreff: gpsd-users Digest, Vol 104, Issue 23
Send gpsd-users mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
Date: Tue, 29 Sep 2020 16:43:49 +0200
From: Marek Szuba <>
Subject: Re: Overlong RTCM3 packets from EUREF-IP
Message-ID: <>
Content-Type: text/plain; charset=utf-8

On 2020-09-29 16:25, Greg Troxel wrote:

>>> By 'handle', do you mean
>>> gpsd 3.21 with that change connects to the EUREF caster at some RTCM3
>>> mountpoint
>>> gpsd sends the RTCM3 to some receiver (F9P?)
>>> the receiver is then able to do RTK successfully
>> I think so. That's what gpsd does with this sort of data, right? Simply
>> forwards it to capable receivers.
> Yes, but I can't see the output from your receiver from here, and was
> asking if in your opinion it is computing an RTK solution in this mode.

I get it now. Yes, I am pretty sure that once I have made RTCM3_MAX
large enough for gpsd not to drop RTCM packets received from the caster,
the receiver does use this data.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]