Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Bill Unruh
On Fri, 24 Feb 2017, Brian Gieryk wrote: Bill, PPS is being referenced as GPS now. Miroslav, that was initial fix. Now, NMEA offset is +198ms std dev is 7301us Sounds about right. GPS (PPS) is offset +23 us std dev is 19us. Seems a bit high. But I do not know either your gps or how well

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Brian Gieryk
This is mine, most online sources are commented out, as internet is very limited here. Brian On Fri, 24 Feb 2017 16:57:15 +0100 Fabian Schörghofer wrote: > What does your chrony.conf look like now? > > I have a similar problem, (also using gpsd and Raspberry Pi with > GPIO-PPS). > > Am 24.02.

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Brian Gieryk
Bill, PPS is being referenced as GPS now. Miroslav, that was initial fix. Now, NMEA offset is +198ms std dev is 7301us GPS (PPS) is offset +23 us std dev is 19us. Brian Sent from my iPhone > On Feb 24, 2017, at 08:48, Miroslav Lichvar wrote: > >> On Fri, Feb 24, 2017 at 08:44:02AM -0700, Br

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Fabian Schörghofer
What does your chrony.conf look like now? I have a similar problem, (also using gpsd and Raspberry Pi with GPIO-PPS). Am 24.02.2017 16:53, schrieb Brian Gieryk: > Bill, PPS is being referenced as GPS now. > > Miroslav, that was initial fix. > > Now, NMEA offset is +198ms std dev is 7301us > >

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Miroslav Lichvar
On Fri, Feb 24, 2017 at 08:44:02AM -0700, Brian Gieryk wrote: > Did as suggested, and seems to be working. NMEA is showing +/- 2599 us and > GPS (PPS) is showing +/- 1831 us. 1800 microseconds is not that good for a PPS. Usually it's just a few microseconds, or better. What does the "chronyc so

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Bill Unruh
Hm. I do not see the PPS refclock in there. William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273 Physics&Astronomy _|___ Advanced Research _| Fax: +1(604)822-5324 UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca Canada V6T 1Z1 | and Gravity

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Brian Gieryk
Did as suggested, and seems to be working. NMEA is showing +/- 2599 us and GPS (PPS) is showing +/- 1831 us. Thank you both! Brian Sent from my iPhone > On Feb 24, 2017, at 08:40, Bill Unruh wrote: > > > > William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273 > Physics&As

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Bill Unruh
William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273 Physics&Astronomy _|___ Advanced Research _| Fax: +1(604)822-5324 UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/ On Fri, 24 F

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Miroslav Lichvar
On Fri, Feb 24, 2017 at 08:01:16AM -0700, Brian Gieryk wrote: > Ok, there is one GPS (with PPS out on a second output, going to GPIO 18 on > the rpi) > > I did a little change (commented out the two NMEA sources. > > I am running gpsd for the GPS source. Ok, the PPS input is on a GPIO instead o

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Brian Gieryk
Smallish update: I changed (in chrony.conf) GPS precision to 1e-6 and added PPS precision at 1e-9. Now chronyc sources is seeing PPS! I will let it cook awhile. Thank you! Brian Sent from my iPhone > On Feb 24, 2017, at 01:34, Miroslav Lichvar wrote: > >> On Fri, Feb 24, 2017 at 12:00:42A

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Brian Gieryk
Recent snipet from refclocks.log === Date (UTC) Time Refid DP L P Raw offset Cooked offset Disp. === 2017-02-24 15:20:01.98715

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Brian Gieryk
Ok, there is one GPS (with PPS out on a second output, going to GPIO 18 on the rpi) I did a little change (commented out the two NMEA sources. I am running gpsd for the GPS source. It is a Dragino LoRaWAN/GPS hat. As I mentioned, the GPS is functioning (what appears to me) correctly. I will a

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Miroslav Lichvar
On Fri, Feb 24, 2017 at 12:00:42AM -0800, Bill Unruh wrote: > You are not logging a crucial thing, refclocks logging. > Put refclocks into the logging line in chrony.conf > > > Note-- it is pps that gines the accuracy. And you need to lock PPS to a > working other source of inaccurate time (bette

Re: [chrony-users] PPS correction not being applied

2017-02-24 Thread Bill Unruh
You are not logging a crucial thing, refclocks logging. Put refclocks into the logging line in chrony.conf Note-- it is pps that gines the accuracy. And you need to lock PPS to a working other source of inaccurate time (better than seconds) William G. Unruh __| Canadian Institute for| Tel

Re: [chrony-users] PPS correction not being applied

2017-02-23 Thread Bill Unruh
On Thu, 23 Feb 2017, Brian Gieryk wrote: I apologize for my seeming ignorance, I have been trying everything I could find in the archives here. No problem. JUst remember that we have no information about your system except what you tell us. I have been using Linux for a grand total of one

Re: [chrony-users] PPS correction not being applied

2017-02-23 Thread Brian Gieryk
I apologize for my seeming ignorance, I have been trying everything I could find in the archives here. I have been using Linux for a grand total of one week, so some patience will be much appreciated. My Pi does not seem to send email directly to anyone other than myself, so it is a 2 step pro

Re: [chrony-users] PPS correction not being applied

2017-02-23 Thread Bill Unruh
On Thu, 23 Feb 2017, Brian Gieryk wrote: Relevant chrony.conf snipet: You do not know what is relevant do you? # offline sources refclock SHM 0 refid GPS precision 1e-1 What is putting this info into shm? refclock SHM 1 refid NMEA precision 1e-9 refclock SOCK /tmp/chrony.ttyS0.sock re

Re: [chrony-users] PPS correction not being applied

2017-02-23 Thread Brian Gieryk
Relevant chrony.conf snipet: # offline sources refclock SHM 0 refid GPS precision 1e-1 refclock SHM 1 refid NMEA precision 1e-9 refclock SOCK /tmp/chrony.ttyS0.sock refid NMEA refclock PPS /dev/pps0 poll 0 refid PPS lock NMEA Sources output: pi@raspberrypi:~ $ sudo chronyc sources 210 Number o

Re: [chrony-users] PPS correction not being applied

2017-02-23 Thread Bill Unruh
You tell it to lock to NMEA. Do you actually have an NMEA refclock running? Ie you might want to show us what your complete chrony.conf is. Also in your sources, what sources are listed? Ie, what is the complete output of chronyc sources command. In the logging of the refclock, are there any e

[chrony-users] PPS correction not being applied

2017-02-23 Thread Brian Gieryk
Good morning. Running chrony 3.1, raspberry Pi 3 model B with the latest Raspbian Jessie. Have GPS working to set the clock with no issue. Have good PPS on /dev/pps0 From searching the archives I have : refclock PPS /dev/pps0 poll 0 refid PPS lock NMEA Appended to the end of /etc/chrony/chrony