Re: [chrony-users] Not getting time from gpsd

2016-08-14 Thread Chris Greenman
Ok I grabbed a sample of the clock statistics. On Fri, Aug 12, 2016 at 2:53 PM, Bill Unruh <un...@physics.ubc.ca> wrote: > On Fri, 12 Aug 2016, Chris Greenman wrote: > > it's a usb puck. so no. Actually I haven't actually looked but typical >> USB is +5v data+ data- and

Re: [chrony-users] Not getting time from gpsd

2016-08-14 Thread Chris Greenman
So how would i tell if my GPS does this and if so how do i get it recognized by the kernel and gpsd? On Fri, Aug 12, 2016 at 2:53 PM, Bill Unruh <un...@physics.ubc.ca> wrote: > On Fri, 12 Aug 2016, Chris Greenman wrote: > > it's a usb puck. so no. Actually I haven't actually loo

[chrony-users] Not getting time from gpsd

2016-08-06 Thread Chris Greenman
Hello, I'm having an issue with getting time from gpsd. My setup is: Raspberry Pi 3 running Jessie Lite USB U-Blox gps gpsd is receiving NMEA from the GPS, cgps also shows time and position properly. My chrony.conf is: server 0.us.pool.ntp.org server 1.us.pool.ntp.org server

Re: [chrony-users] Not getting time from gpsd

2016-08-06 Thread Chris Greenman
Same thing. Already tried it. On Aug 6, 2016 6:35 AM, "Steve Horton" <stevejhor...@gmail.com> wrote: > I'd look closer at the SOCK option under the refclock section. > https://chrony.tuxfamily.org/manual.html#refclock-directive > > On Aug 6, 2016 12:00 AM, &qu

Re: [chrony-users] Not getting time from gpsd

2016-08-06 Thread Chris Greenman
ead the time from that device file via a >>> Unix domain socket. Like I said..look >>> into the sock option and how it relates to gpsd. >>> >>> >>> On Aug 6, 2016 10:10 AM, "Chris Greenman" <chris.m.green...@gmail.com> >>> wro

Re: [chrony-users] Not getting time from gpsd

2016-08-06 Thread Chris Greenman
ite time out to a device file some where and chrony can read > the time from that device file via a Unix domain socket. Like I said..look > into the sock option and how it relates to gpsd. > > On Aug 6, 2016 10:10 AM, "Chris Greenman" <chris.m.green...@gmail.com>

Re: [chrony-users] Not getting time from gpsd

2016-08-06 Thread Chris Greenman
26 1 0 13:36 ?00:00:00 /usr/sbin/gpsd -N -F /var/run/chrony.ttyACM0.sock /dev/ttyACM0 cgps shows 3d fix On Sat, Aug 6, 2016 at 2:11 PM, Steve Horton <stevejhor...@gmail.com> wrote: > Ok..can I see your gpsd conf? > > On Aug 6, 2016 1:39 PM, "Chris Greenman

Re: [chrony-users] Not getting time from gpsd

2016-08-07 Thread Chris Greenman
DESC" "$NAME" do_stop case "$?" in 0|1) do_start case "$?" in 0) log_end_msg 0 ;; 1) log_end_msg 1 ;; # Old process is still running *) log_end_msg 1 ;; # Failed to start esac ;; *) # Failed to stop log_end_msg 1 ;; esac ;; *) echo "Usage: $SCRIPTNAME

Re: [chrony-users] Not getting time from gpsd

2016-08-07 Thread Chris Greenman
> > On Aug 6, 2016 11:37 PM, "Chris Greenman" <chris.m.green...@gmail.com> > wrote: > >> $ file /var/run/chrony.ttyACM0.sock >> /var/run/chrony.ttyACM0.sock: socket >> >> cat /etc/init.d/gpsd >> >> $ cat /etc/init.d/gpsd >> #!/bin

Re: [chrony-users] Not getting time from gpsd

2016-08-08 Thread Chris Greenman
before and got the same results as the distro version. On Mon, Aug 8, 2016 at 9:19 AM, Miroslav Lichvar <mlich...@redhat.com> wrote: > On Mon, Aug 08, 2016 at 09:05:03AM -0400, Chris Greenman wrote: > > I didn't think the -F option was correct but it didn't seem to work > without

Re: [chrony-users] Not getting time from gpsd

2016-08-08 Thread Chris Greenman
than suits my needs. Sorry for wasting everyone's time.I was trying to save time and frustration by using the repo supplied (and you would think tested) binaries. It would have been a lot quicker and less frustrating to just compile. lol. On Mon, Aug 8, 2016 at 11:50 AM, Chris Greenman

Re: [chrony-users] Not getting time from gpsd

2016-08-09 Thread Chris Greenman
Thanks. I already enabled my NTP sources and you're right, the gps is getting marked as bad. I'll play with that today. Chris On Aug 9, 2016 4:42 AM, "Miroslav Lichvar" <mlich...@redhat.com> wrote: > On Mon, Aug 08, 2016 at 01:21:56PM -0400, Chris Greenman wrote: > >

Re: [chrony-users] Not getting time from gpsd

2016-08-09 Thread Chris Greenman
clock is unreachable. I would > have > thought 15 was a more reasonable value for that, but > > > > On Tue, 9 Aug 2016, Chris Greenman wrote: > > Ok I took out the offset, precision, and delay. I let everything >> stabilize a bit and then took 3 samples. >> He

Re: [chrony-users] Not getting time from gpsd

2016-08-22 Thread Chris Greenman
Lichvar <mlich...@redhat.com> wrote: > On Fri, Aug 19, 2016 at 06:26:14PM -0400, Chris Greenman wrote: > > Finally got a chance to grab more stats.my refclock line now looks > like > > this: > > > > refclock SHM 0 refid GPS offset 0.060 delay 0.22 minsamples 64

Re: [chrony-users] Using symbolic network names in /etc/chrony.conf file?

2017-07-25 Thread Chris Greenman
When you specify a hostname, that's it. It's a 32bit address (ipv4 of course). Throwing a netmask on it does nothing except specify that your network segment has 64,510 usable addresses. Now if you edit /etc/networks and add mynet 10.10.0.0 then you can use the mynet/16 notation in your

Re: [chrony-users] Time synchronisation over a high-latency packet radio network

2019-05-07 Thread Chris Greenman
Is there any possibility of using GPS for time? I had a similar dilemma on my raspberry pi based boat computer. I didn't want to rely on internet provided time since it might not be available if away from the slip. On Tue, May 7, 2019, 11:30 AM Lonnie Abelbeck wrote: > > > > On May 6, 2019,