Signalk / Issue resuming GPSD connection

[damien]

Hello Teppo,

Thanks a lot for the reply and the search for a node-gpsd client supporting reconnect (https://github.com/SignalK/signalk-server/issues/1363) ; that should avoid the use for the kind of workaround exposed above.

By the way, I noticed on signalk-server issues on GitHub some discussion about GPS returning wrong dates leading to a problem with set date and time plugin (https://github.com/SignalK/signalk-server/issues/1335) ; I tentatively suggested a possibility to use GPSD which incorporate patches to cope with the 2^10 week rollover leading to incorrect date being returned (documented https://gpsd.gitlab.io/gpsd/gpsd.html):

gpsd uses the startup time of the daemon detect and compensate for rollovers while it is running, but otherwise reports the date as it is reported by the receiver without attempting to correct it.

There was an issue with the code implementation for releases >=3.20 (see https://gitlab.com/gpsd/gpsd/-/issues/144) but has been corrected by Garry Miller in 3.23.1. I have recompiled GPSD V3.23.1. on tinypilot and openplotter and found with a 'buggy' GPS that does not take properly into account the rollover (BU-353 based on SiRF3) that correct date is now reported.

To finish with, thanks a lot to sk team for the great application and time dedicated to it ; really impressive.

Best regards,

Xavier.