Re: Mode/Status not updated in shared mem mode

[Владимир Калачихин]

08.01.2025 23:59, Gary E. Miller пишет:
> > ?POLL is historical.
>
> Uh, no.  Works fine.  Some clients use it.  Usually single
> shot clients.
Sorry for my english.
Yes, ?POLL works well too in my proxy. This was originally created to 
support ?POLL. But I mostly use ?WATCH now.



> > The main goal is user-defined lifetime for every
> > value.
>
> Wow, every value?  

        'altHAE' => 20,
        'altMSL' => 20,
        'alt' => 20,
        'lat' => 10,
        'lon' => 10,
        'track' => 10,
        'heading' => 10,
        'speed' => 5,
        'errX' => 30,
        'errY' => 30,
        'errS' => 30,
        'magtrack' => 10,
        'magvar' => 3600,
        'mheading' => 10,
        'depth' => 5,
        'wanglem' => 3,
        'wangler' => 3,
        'wanglet' => 3,
        'wspeedr' => 3,
        'wspeedt' => 3,
        'time' => 10

> Messages are timestamped, not individual data values. 
> And in most GNSS cases, all values all change once per epoch.
>
> So not giving you any new real information.

GNSS, but not AIS. And GNSS and echosounder and windmeter epoch are not 
necessarily in phase.

And any device can freeze, socket can die... Therefore, if there is no 
data during the timeout by gpsd timestamp, the value is set to null.
I can do without the actual coordinates for 10 seconds, but only 5 
without the actual speed. If the gpsd does not send new values within 
this time, the gpsdPROXY will send null to the client.




Владимир Калачихин