[time-nuts] Re: Comparison/evaluation of u-blox timing receivers

2021-08-28 Thread djl
John: I missed this on its intro to the group. Great paper and effort. It's also a very useful intro/primer to measurement methodology beyond application to only the u-blox family. Thanks for leveraging the NSF for our benefit! Don On 2021-08-28 05:02, Julien Goodwin wrote: On 24/8/21 11:51

[time-nuts] Re: Comparison/evaluation of u-blox timing receivers

2021-08-28 Thread Julien Goodwin
On 24/8/21 11:51 am, John Ackermann N8UR wrote: > In 2020 I did an extensive evaluation of the timing ability of the > u-blox LEA-M8F, NEO-M8N, NEO-M8T, NEO-M9N, ZED-F9P, and ZED-F9T.  The > work was made possible by support from the HamSci consortium > (https://hamsci.org) under NSF grants

[time-nuts] Re: Comparison/evaluation of u-blox timing receivers

2021-08-25 Thread John Ackermann
Hi Andrew -- Yes, it's entirely possible the problem was with the setup.  I doubt it was signal level (I was feeding clean 3.3V TTL PPS signals) but I'm not sure that my data capture software was as robust as it could have been. John On Aug 25, 2021, 5:16 PM, at 5:16 PM, Andrew Rodland

[time-nuts] Re: Comparison/evaluation of u-blox timing receivers

2021-08-25 Thread Andrew Rodland
Very interesting. When I built my Arduino Due-based Rb clock (currently disassembled) around a NEO-M8T (more specifically, an EVK-M8T), I used the EXTINT to measure the difference between my onboard PPS and the GPS top-of-second. I ran it pretty long term without seeing any lost or duplicated

[time-nuts] Re: Comparison/evaluation of u-blox timing receivers

2021-08-24 Thread David Taylor via time-nuts
On 24/08/2021 02:51, John Ackermann N8UR wrote: In 2020 I did an extensive evaluation of the timing ability of the u-blox LEA-M8F, NEO-M8N, NEO-M8T, NEO-M9N, ZED-F9P, and ZED-F9T. The work was made possible by support from the HamSci consortium (https://hamsci.org) under NSF grants supporting

[time-nuts] Re: Comparison/evaluation of u-blox timing receivers

2021-08-24 Thread Avamander
Hi, I hope you don't mind me starting a "newcomer" thread based on your sentence: "with a GPSDO, finding one that’s got a clean output is not at all easy". Are there any up-to-date resources that would provide such information about a larger selection of GPSDOs? Are there any GPSDOs that people

[time-nuts] Re: Comparison/evaluation of u-blox timing receivers

2021-08-24 Thread Bob kb8tq
Hi The simple answer is to put a cleanup loop on the output of the GPSDO if you are looking for a low noise signal. In the microwave case, something running at (maybe) 100 MHz with a good OCXO is a pretty bulletproof solution. Indeed, if you need low phase noise at 10 MHz, the same basic

[time-nuts] Re: Comparison/evaluation of u-blox timing receivers

2021-08-24 Thread Dana Whitlow
Thanks very much, John. Dana On Mon, Aug 23, 2021 at 8:52 PM John Ackermann N8UR wrote: > In 2020 I did an extensive evaluation of the timing ability of the > u-blox LEA-M8F, NEO-M8N, NEO-M8T, NEO-M9N, ZED-F9P, and ZED-F9T. The > work was made possible by support from the HamSci consortium >

[time-nuts] Re: Comparison/evaluation of u-blox timing receivers

2021-08-24 Thread Bob kb8tq
Hi The problem with the approach used in the basic GPS / GNSS modules is that the TCXO is not tuned on frequency. Even with an integer relation to the internal oscillator, you still see the pulse drop / pulse add into the divider. The result is that they are noisy. There are a couple of modules

[time-nuts] Re: Comparison/evaluation of u-blox timing receivers

2021-08-24 Thread Marek Doršic
Hello, thank you for sharing valuable comprehensive comparisions. In the high timepulse rate experiment, have you also investigated other rates than the standard 10 MHz? Most Ublox receivers use 48MHz internal clock thus the 10MHz timepulse must be missing some of the clock pulses which