|
From: | Tom Isaacson |
Subject: | Re: Can't get time |
Date: | Fri, 3 Apr 2020 10:00:04 +1300 |
Yo Tom!
On Fri, 3 Apr 2020 09:12:00 +1300
Tom Isaacson <address@hidden> wrote:
> > Why a 6? results will be not so good.
>
> Because that's what is on the board.
You get what you paid for.
> > If it is not configured, why do you expect it to be working?
>
> I don't. My question is about why gpsd-api isn't showing time, you
> asked about our version of NTPSec.
I'm not sure what you mean by that. Can you explain what you are
looking at and what you expect to see?
Does cgps show a fix, and a time?
> > What do you think that proves? Looks normal to me.
>
> I don't know, that's why I'm asking. This is my first time using
> gpsd, I'm asking people who have more experience.
Send your data here: gpspipe -R -n 100 > raw.log
Maybe also your JSON: gpspipe -w -n 100 > json.log
> > You do NOT want to specify the serial port AND -F
>
> Okay, why? I thought -F specified the control socket location, I
> didn't realise it would clash with the serial port.
And why do you wnat a control socket? The problem is not the
control socket, the problem is that something may try to use it.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
address@hidden Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can't measure it, you can't improve it." - Lord Kelvin
[Prev in Thread] | Current Thread | [Next in Thread] |