[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Overlong RTCM3 packets from EUREF-IP
From: |
Marek Szuba |
Subject: |
Re: Overlong RTCM3 packets from EUREF-IP |
Date: |
Tue, 29 Sep 2020 16:05:26 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 |
On 2020-09-29 15:52, Greg Troxel wrote:
>> Indeed, replacing 512 with 2048 in the source code seems to make
>> gpsd-3.21 handle EUREF RTCM data just fine.
>
> 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.
>> What do you think about about increasing RTCM3_MAX to 2048, guys?
>
> I'd say if we don't have a footnote justifying 512 :-), and BKG uses
> 2048, and you are seeing 590, it's entirely reasonable to flip to 2048.
IIRC all the source code says about RTCM3_MAX is that RTCM 3 packets
vary in length more than RTCM 2 ones.
--
MS