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

[hans mayer]

Yo Gary,

> Well, if /dev/pps1 is not giving you time, that is #2 above, which
> makes it a RasPi problem, not a gpsd problem.

Yes, it seems to be so.

Many thanks for your support all over the time.


Kind regards
Hans

--



Am 18.08.2015 23:13, schrieb Gary E. Miller:
> Yo hans!
>
> On Tue, 18 Aug 2015 22:18:44 +0200
> hans mayer <address@hidden> wrote:
>
> >   > The ERROR is alarmist, I just changed git head to drop that to a
> >   > WARN. It just means no time stamp was available, thus a timeout.
> >   > This is
> > normal
> >   > on some GPS if no sat lock.
> >
> > That's exactly my problem. I don't get a time stamp
> > but I have a 3D fix with about 10 satellites.
>
> Well, that is not exact at all.  At what point do you not have a timestamp?
>
> !. Do you know you have PPS into gpio?  How do you know?
>
> 2. Do you have PPS ini /dev/pps1?  How do you know?
>
> 3. Do you have PPS (not KPPS) in gpsd?  How do you know?
>
> 4. Do you have KPPS (not PPS) in gpsd?  How do you know?
>
> 5. Do you have PPS in SHM from gpsd?  How do you know?
>
> 6. Do you have PPS in chronyd from SHM?  How do you know?
>
> As you see, at least 6 timestamps invovled.
>
> >   > Well, none of this is a problem.  A problem would be if you do not
> >   > get good time from /dev/pps1.
> >
> > I don't get any time.
>
> Well, if /dev/pps1 is not giving you time, that is #2 above, which
> makes it a RasPi problem, not a gpsd problem.
>
> RGDS
> GARY
> ---------------------------------------------------------------------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>         address@hidden  Tel:+1(541)382-8588