Re: [time-nuts] Correcting measured PPS values with receiver sawtooth correction values

2019-02-18 Thread Attila Kinali
On Sun, 17 Feb 2019 00:49:58 + Mark Sims wrote: > The two candidates for the F9P are "add current sawtooth" or "subtract > previous sawtooth". I had been favoring "subtract previous" but some more > detailed analysis seems to favor "add current". The difference between the > results of

Re: [time-nuts] Correcting measured PPS values with receiver sawtooth correction values

2019-02-17 Thread Bob kb8tq
Hi One *could* suggest that the manual would be a great source of information for this sort of thing. The problem there is that pretty much the whole manual talks about the M8 as the target device once you get into the fine print. The big points have been translated over to the F9P. The fine

Re: [time-nuts] Correcting measured PPS values with receiver sawtooth correction values

2019-02-16 Thread Bob kb8tq
Hi The gotcha is that the jitter on the base pps output is high enough in this case that doing a reasonable check (roll over … ) is not as simple as it should be. Best guess is that uBlox has a bug in their GPS side of things. Pretty much par for the course on something this new. Bob > On

[time-nuts] Correcting measured PPS values with receiver sawtooth correction values

2019-02-16 Thread Mark Sims
The F9 has a totally new internal architecture / processor, so it's best to make no assumptions about how it works compared to older models. For the LEA-6T the correction strategy is clearly "add previous sawtooth value". That does not work for the F9P. The two candidates for the F9P are

Re: [time-nuts] Correcting measured PPS values with receiver sawtooth correction values

2019-02-16 Thread Achim Gratz
Mark Sims writes: > For all the receivers that I have tested there is only one combination > that jumps out as being the correct one. However, for the new Ublox > F9P, there are two combinations that produce virtually identical > measurements and statistics (add current sawtooth or subtract

Re: [time-nuts] Correcting measured PPS values with receiver sawtooth correction values

2019-02-15 Thread Azelio Boriani
Why "virtually" and not exactly identical? Maybe the answer is in the details... On Sat, Feb 16, 2019 at 12:01 AM Mark Sims wrote: > > I am adding the ability to Lady Heather to apply receiver sawtooth correction > values to measured PPS values... this requires having a receiver that outputs >

Re: [time-nuts] Correcting measured PPS values with receiver sawtooth correction values

2019-02-15 Thread Bob kb8tq
Hi Well … since you asked …. ummm… F9P: Run a second type of receiver ( Furuno GT-87 maybe) Measure it Sawtooth correct it Compare corrected receiver A to corrected receiver B Sure am glad that I’m too far away to be hit by that rock that just got tossed my way :) Bob > On Feb 15, 2019, at

Re: [time-nuts] Correcting measured PPS values with receiver sawtooth correction values

2019-02-15 Thread Poul-Henning Kamp
In message , Mark Sims writes: >For all the receivers that I have tested there is only one combination >that jumps out as being the correct one. However, for the new >Ublox F9P, there are two combinations that produce virtually identical >measurements and statistics (add current

[time-nuts] Correcting measured PPS values with receiver sawtooth correction values

2019-02-15 Thread Mark Sims
I am adding the ability to Lady Heather to apply receiver sawtooth correction values to measured PPS values... this requires having a receiver that outputs sawtooth values as the main input device and connecting a TICC/counter measuring the receiver PPS output as an auxiliary input device.