[time-nuts] Question concerning ADEV measurements

[Magnus Danielson]

It can be a benefit or a cause of problem. In one end, it could lower
your noise. The DG535 actually has that as a recommendation, that the
signal source and the DG535 operate on the same clock.

Another aspect is that you keep banging the same little range of values,
and that may for that time-base to stop delay be systematically off in
an unfavourable fashion. The noise of a counter is not always linear
with that delay, so an asynchronous clock would sweep over the range.
Then again, if the delay is just right you can utilize the minimum.

Cheers,
Magnus

On 10/09/2013 11:42 PM, John Miles wrote:
> Not sure if there's anything to worry about, but I don't think there are any
> good reasons to do it.  The OCXO in the 5370 is an order of magnitude more
> stable from one second to the next than the counter's resolution would allow
> you to measure at t0=1s.  
>
> -- john, KE5FX
> Miles Design LLC
>
>> -----Original Message-----
>> From: time-nuts-bounces at febo.com [mailto:time-nuts-
>> bounces at febo.com] On Behalf Of Robert Darby
>> Sent: Wednesday, October 09, 2013 12:30 PM
>> To: time-nuts at febo.com
>> Subject: [time-nuts] Question concerning ADEV measurements
>>
>> Is there a methodological difficulty using the reference clock to also
>> clock a TIC?
>>
>> Specifically, I have a 5370B with the DUT on the start input and a 5065A
>> on both the stop input and the external clock input.
>>
>> Thanks,
>> Bob Darby
>> _______________________________________________
>> time-nuts mailing list -- time-nuts at febo.com
>> To unsubscribe, go to https://www.febo.com/cgi-
>> bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.