Also check the sigma-1 estimate around the event. If you have a grazing reflection near the horizon, you may see the receiver latch onto the reflected signal, and then when the satelite comes into direct view, it will loose it, then recapture it and your step will happen here.

Estimate at least. Sorry, just thinking out loud. -GH Rasputin Novgorod wrote: > --- xaos wrote: > > >> 8-way splitters >> Make sure it passes DC. Your antenna will need it. >> Pass the DC from one port and block it from all others. >> > > What size, type block?

. > > There are, however, some subtle differences between a loop > optimized to make the best estimate of 10 MHz possible given the OCXO > used and one optimized to make the 1 PPS the best possible approximation > to UTC.

This is essentially what folks do to create an "eye" diagram for estimating high speed data link jitter. The difficulty with this approach is that the probability observing maximum jitter is quite low & the 'scope waveform tends to have very low intensity for these "rare" events, so it's tough to know where the outer edges of the jitter are.

The protocol includes an estimate of the quality so the client can pick the best clock. -- These are my opinions, not necessarily my employer's. I hate spam.

Seems that they will be as of V3.0 which I expect to pop up within a month or so (he actually said two weeks, but as allways multiply with Pi from what a software guy estimates in time). It already has PPS input, but there is a little bit of a hardware hack to make a proper 50 ohm terminated PPS.

The nav equations calculate (apparent) range and range rate from the known state vector of each satellite and the (estimated) state vector of the receiver.

Oh, when I described means to estimate drift parameters out if the frequency derivate, then again the need for zero dead time is there, between the frequency or time samples (whichever is used). Picket fence techniques should be used. The TADD-2 may come in handy. Oh, got to play some more with mine. Cheers, Magnus

I would estimate that the 5071A (and ONLY the 5071A > among commercial clocks) could get the job done provided that you could > compare its frequency to GPS to the stated accuracy. This would > be using the 5071 as a secondary standard. You still need to > deal with the short term stability of the 5071A, depending on > your system needs.

The thunderbolts produce status information and error estimates about how they are doing. If you are willing to trust that, you can remove the one that is falling out of tolerance. If you aren't willing to trust that, then I'm pretty sure you'll need a third frequency standard to compare each to.