[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gpsd Reliable and resilient tcp feed
From: |
Gary E. Miller |
Subject: |
Re: gpsd Reliable and resilient tcp feed |
Date: |
Thu, 30 Sep 2021 10:35:19 -0700 |
Yo Nick!
On Thu, 30 Sep 2021 12:45:02 +0100
Nick Taylor <nicktaylor@dataskill.uk> wrote:
> We need to use tcp feed into gpsd - our customer is providing the
> feed so udp not really an option.
Many other options beyond udp. How many serial and USB ports does your
GNSS receiver have?
> Requirement is for reliable and resilient tcp feed to gpsd. Currently
> it doesn't do very well if feed gets interrupted - either by restart
> of the feed or if we block the connection for a while with iptables
> to simulate interrupted feed.
Yup. Nothing new there. gpsd does not do any reconnect.
> I realise that gpsd is a complex beast and our guy hasn't yet come up
> with working solution - we keep getting bad side effects like gpsd
> failing to respond to client connects and broken shm ntp feed
Yup, as I warned you about your code.
> Any gpsd gurus here interested in some contract work - or can anyone
> point us to someone who could help??
I have been known to accept contracts to add gpsd features. I might have
already added NTRIP reconnect, except I've never seen NTRIP add any
precision. So why bother?
Can you demonstarte that your NTRIP feed improves your precision?
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
gem@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can't measure it, you can't improve it." - Lord Kelvin
pgpg8gbdsX2E0.pgp
Description: OpenPGP digital signature