Re: 3.22 not sending PPS to SHM

[David Taylor]

On 12/01/2021 14:41, Greg Troxel wrote:
> David Taylor <gm8arv@yahoo.co.uk> writes:
>
> > So in the case of the Raspberry Pi, with no DCD or whatever serial PPS
> > signal, the only source of PPS is the GPIO pin 18 (in my
> > case). ntpshmmon shows just NTP0.  When I use servers 127.127.28.0 and
> > 127.127.28.1, SHM0 shows a valid non-zero offset (serial output
> > delay), but SHM1 shows no connection:
>
> Does the RPI's operating system provide a /dev/ppsN device associated
> with that GPIO pin?   Did you pass that device  on the command line?

Greg,

Yes, I see two PPS devices:

  pi@RasPi-22:~ $ ls /dev/pps*
  /dev/pps0  /dev/pps1

These appear after some boot-time configuration commands.  I am only 
running gpsd from the command line right now.  I've had issues with 
automating this in the past so I thought to start the easier way!

  sudo gpsd /dev/ttyS0 -s 115200 -n -F /var/run/gpsd.sock

so I'm unsure how gpsd knows about the PPS device.  To test I would run:

sudo ppstest /dev/pps0
trying PPS source "/dev/pps0"
found PPS source "/dev/pps0"
ok, found 1 source(s), now start fetching data...
source 0 - assert 1610463934.000000417, sequence: 31086 - clear 
0.000000000, sequence: 0
source 0 - assert 1610463935.000002971, sequence: 31087 - clear 
0.000000000, sequence: 0
source 0 - assert 1610463936.000003803, sequence: 31088 - clear 
0.000000000, sequence: 0
source 0 - assert 1610463937.000004803, sequence: 31089 - clear 
0.000000000, sequence: 0

Cheers,
David
--
SatSignal Software - Quality software for you
Web: https://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk
Twitter: @gm8arv