Re: [time-nuts] HP 3010Axxxxx oscillator

Corby wrote: The 3010A prefix identifies that date it was made. Specifically, it identifies the "series" of the product -- the date the last revision to the product was adopted. The "3010" part is the encoded date for that particular series (10th week of the 30th year past HP "year one"),

Re: [time-nuts] How to get PPS from ublox mini-PCI GPS to APU2 SoC serial port for ntpd

On Tue, Aug 16, 2016 at 3:36 PM, Attila Kinali wrote: > I disagree here. With the APU and its IRQ system you get already to > sub-us PPS time stamping (probably in the 10ns-100ns range). > An APU1 post said they had 50ms of jitter (as measured by Chrony) so they assumed the

Re: [time-nuts] Holdover

Bob, On 08/16/2016 11:31 PM, Bob Stewart wrote: Hi Attila, In my unit, which is a frequency standard, I chose to tell the receiver to stop sending 1PPS pulses when it loses sync to the sats. And since the 1PPS is no longer coming, the PLL does nothing and the DAC doesn't change. (Let's

Re: [time-nuts] Lady Heather

> I am just starting out using Lady Heather. > > I am trying to create a .cfg file to set the program to COM 3 at startup. > > I created the file and saw the instructions to put it in my “Documents” > folder. > The only documents folder in Windows is “My Documents.” > > I created a text file

Re: [time-nuts] Holdover

Hi Attila, said "Ie you need to figure out what you want to do with those PPS, then figure out what the desired behaviour during hold-over and recovery is and from that you can design the frequency standard." What is the most usual method for *time standards*?  I'm satisfied with how my unit

Re: [time-nuts] Holdover

Hi Attila, In my unit, which is a frequency standard, I chose to tell the receiver to stop sending 1PPS pulses when it loses sync to the sats.  And since the 1PPS is no longer coming, the PLL does nothing and the DAC doesn't change.  (Let's avoid the question of aging correction for now.)  So,

Re: [time-nuts] Holdover

On Tue, 16 Aug 2016 21:31:17 + (UTC) Bob Stewart wrote: > So, that's one way, but probably not a desirable way.  My interest was in > the option of using the OCXO to create the time, which clearly gives a > better option when the receiver syncs back up to the sats.  Is

Re: [time-nuts] Holdover

On Tue, 16 Aug 2016 04:35:40 + (UTC) Bob Stewart wrote: > It's been pointed out to me that I didn't understand the function of > the 1PPS of a time standard.  I confess that somehow I had confused the > term to be timing standard; which would be an entirely different thing. 

[time-nuts] HP 3010Axxxxx oscillator

Perry, The 3010A prefix identifies that date it was made. It should also have a 10811A marking. The resistor value is for applications needing precise EFC. Usually found in HP 5065A, 5061A, and 5061B. If it also has a 60109 marking it has slightly better short term stability at one Tau.

Re: [time-nuts] How to get PPS from ublox mini-PCI GPS to APU2 SoC serial port for ntpd

On Mon, 15 Aug 2016 16:57:27 -0400 Paul wrote: > Finally, these boxes are intended to be routers (hence the three network > interfaces) not time-servers and unless you're irrevocably wedded to the > miniPCIe in APU2 route there are probably better choices for time servers.

Re: [time-nuts] Mini ovens packaging

Hoi Guillermo, On Mon, 15 Aug 2016 11:07:41 + Guillermo Sobreviela Falces wrote: > -Temperature stability of 0.1ºC, what means temperature control > included. As Bob already wrote, this value has little meaning without the temperature range at which

Re: [time-nuts] Lady Heather

If you start Lady Heather from a command line prompt, the cfg file should be in the directory you are in. If you start it clicking on an icon or the start menu, it should be in your My Documents folder (which depends upon the OS version you are running). You can find out for sure by typing ?