[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Help needed to configure and compile gpsd to run on a Raspberry Pi 4
From: |
Gary E. Miller |
Subject: |
Re: Help needed to configure and compile gpsd to run on a Raspberry Pi 4 and NOT use systemd |
Date: |
Wed, 13 Nov 2024 14:13:10 -0800 |
Yo Mick!
On Wed, 13 Nov 2024 21:53:35 +0000
Mick Durkin <mickdurkinuk@gmail.com> wrote:
> > Very common thing to do. Did you read any of our howto's for that
>
> I did read the document on the project website, hence my remarks
> about the "missing" old options. I came with these questions after
> reading that document. Evidently, I did not grasp the full story.
I just updated the docs to remove mentions of the removed options. It
will be next week before they are live.
> >> However, this means
> >> electrically things are connected correctly and the Pi's
> >> configuration (e.g. activating the UART and setting up the PPS
> >> pin) is good.
> >
> > That might be stretching the point a bit...
>
> OK, maybe... What I was trying to convey was that the hardware
> was wired up correctly and could be configured to read the GPS
> and PPS signals as we were able to get good output from cgps and
> chrony. My thinking was that if we subsequently did not get good
> results out of gpsd (and, eventually) NTPsec, it would be due to some
> issue caused by how we configured and compiled them.
Unlikely. It would be very hard to mess up the rest of the task.
> >> I am quite happy going down this path, so I persuaded him that
> >> this is the way to go. I also said we might install NTPsec (from
> >> source) rather than Chrony.
> >
> > Depends on the use case. Chrony is better for laptops and systems
> > that boot frequently. NTPec is better as a dedicated chimer that
> > you just leave running on the network.
>
> This is a dedicated timeserver running permanently to deliver time to
> the local network. I was aware of the differing aims of NTPsec and
> chrony. I run NTPsec on my own network, so I prefer using someting I
> understand.
Then NTPSec it will be, for you.
> >> As we
> >> are using simple serial data + PPS into the Pi's UART port, we
> >> don't have a hat.
> >
> > Twp things:
> >
> > 1) RasPi's do not have UARTs That is: Not RTS, CTS, DSR, DCD, etc..
> > Just dumb serial ports (Tx/RX)
>
> Ok, yeah. You got me. Sloppy choice of word 8^)
But an important distinction to get right
> Good to get the accurate info about the options. I will go ahead and
> start building with a straight out of the box git clone.
Let us know how it goes.
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
Re: Help needed to configure and compile gpsd to run on a Raspberry Pi 4 and NOT use systemd, Gary E. Miller, 2024/11/13
Re: Help needed to configure and compile gpsd to run on a Raspberry Pi 4 and NOT use systemd, Mick Durkin, 2024/11/13
- Re: Help needed to configure and compile gpsd to run on a Raspberry Pi 4 and NOT use systemd,
Gary E. Miller <=
Re: Help needed to configure and compile gpsd to run on a Raspberry Pi 4 and NOT use systemd, Mick Durkin, 2024/11/15
Re: Help needed to configure and compile gpsd to run on a Raspberry Pi 4 and NOT use systemd, Mick Durkin, 2024/11/15
Re: Help needed to configure and compile gpsd to run on a Raspberry Pi 4 and NOT use systemd, Mick Durkin, 2024/11/18
Re: Help needed to configure and compile gpsd to run on a Raspberry Pi 4 and NOT use systemd, Mick Durkin, 2024/11/19
Re: Help needed to configure and compile gpsd to run on a Raspberry Pi 4 and NOT use systemd, Mick Durkin, 2024/11/19