Re: [gpsd-users] syslog error message with new version - kernel PPS failed Connection timed out

[hans mayer]

Yo Garry,

Many thanks again for your support but I am not a step further.
I compiled the kernel with pps debug in the hope to see more.

> You probably do not have KPPS in you kernel

I have. Here are the modules
bananapi:root> lsmod | grep pps
pps_ldisc               2310  0
pps_gpio                3357  0
pps_core               10107  2 pps_ldisc,pps_gpio

Here some syslogs:
( as of the fact I switched on the kernel pps debugging )
Aug  4 23:38:47 bananapi kernel: [ 1011.465714] pps pps0: PPS event at 
1438724326.994917747
Aug  4 23:38:47 bananapi kernel: [ 1011.469126] pps pps0: capture assert 
seq #1001

and NTP also working fine with PPS/ATOM support 127.127.22.0

There is till the issue that original version 3.6 doesn't generate
syslog error messages but self compiled version 3.15 does

> Those messages are not from gpsd.

These are the messages I have:
Aug  4 23:44:44 bananapi gpsd[2580]: gpsd:ERROR: KPPS:/dev/ttyS2 kernel 
PPS failed Connection timed out

And it's not a kernal message, it comes from gpsd.

Why does gpsd try kernel PPS ? And how ?
Also /dev/ttyS2 is confusing me.
ttyS2 is the interface where the GPS module sends the serial data.
The 1PPS is on GPIO pin 18 - a different pin.

I found in the documentation "build.txt" the following
pps=yes is the default
pps=no.  You'll lose support for updating the clock from PPS pulses.

What does it mean ?
Which clock is not updated ?  I don't want that gpsd updates any clocks.
gpsd has only one function to read the data from the gps module.
The 1PPS is directly managed by the ntp daemon itself.

As always any help is highly appreciated.


Kind regards
Hans

--



Am 24.07.2015 19:17, schrieb Gary E. Miller:
> Yo hans!
>
> On Fri, 24 Jul 2015 18:27:47 +0200
> hans mayer <address@hidden> wrote:
>
> >   > The RasPi takes some extra configuration to get right.  Be sure to
> > read the gpsd specific doc on the RasPi.
> >
> > can you point me to an URL ?
> > or some details for what i should search ?
>
> No need for a URL, all you need is in the INSTALL file in the gpsd
> tar ball.  Just search for RasPi.
>
> > offset in peerstats for 127.127.28.1 is typical below 20 micro seconds
>
> That would be a good PPS.
>
> >   > Yeah, you need too fix your KPPS.
> >
> > how ?
>
> You probably do not have KPPS in you kernel.  You probably need to compile
> a new kernel as described in the 'gpsd-time-service-howto.txt' in the
> gpsd tar ball.
>
> > as i wrote, originally i used for gpsd version 3.6
> > with version 3.6 there are no errors in the syslog.
> > these messages came with version 3.15
>
> Those messages are not from gpsd.  Note that they have the prefix 'kernel:'.
>
> They show that you have KPPS in your kernel.  So if gpsd is not
> seeing them then you missed the steps in the INSTALL file that
> tell how to tell gpsd to find the right /dev/pps.
>
> > do you have any further tips for me ?
>
> No, just the same ones, read the INSTALL and gpsd-time-service-howto.txt
> files that are in the gpsd tar ball.  Paying particular attention to the
> parts marked as RasPi.
>
> RGDS
> GARY
> ---------------------------------------------------------------------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>         address@hidden  Tel:+1(541)382-8588