Hi Effectively you only have one signal into the counter. It’s simply measuring the 1/tau measurement floor of the 5370. If your objective is to measure the ADEV of the measurement floor of the counter, that’s fine. Your plot looks a lot like the one half way down on:
http://www.febo.com/pages/hp5370b/ It’s in the “Time Interval Measurement” section. ================ ADEV of a standard is done by comparing two references against each other. With a 5370 typically one source starts a reading and the other source stops the reading. There are many different ways to set this up. A lot depends on the sources you have. One common way is: Set the counter to start / stop time interval mode. Let a PPS start the reading and a 10 MHz stop the reading. You will get data once a second. The time difference between start and stop will be the phase of the 10 MHz sampled once a second. The tricky part of this is getting all the buttons and knobs on the 5370 set to the right mode. It’s a fairly complex device. A quick way to debug the time mode on the counter: Feed the PPS to both inputs and have one trigger positive and the other trigger negative. You will read the pulse width (either high or low) of the PPS signal. The plot you will get will still be limited by the counter measurement floor at short time periods. Past 100 seconds or so you should be seeing the combined ADEV of your two sources. If the ADEV of each source is at the same level, then the sources are better than the reading by the square root of 2. If one source is much better than the other, the reading is essential the ADEV of the poorer source. Bob > On Jan 18, 2015, at 9:37 AM, Stéphane Rey <steph....@wanadoo.fr> wrote: > > Hello, > > First, please do apologize for the confusion answering in the bad email. > That's things I'm absolutely able to do when replying at 3 am ! Again, sorry > for that and thanks Magnus for having corrected this. > > Back to my setup : > > There is indeed nothing on the STOP input of the HP5370a. The standard 10 MHz > comes from the GPSDO HP-58503B and feeds the HP5370a Standard input. Its ADEV > is given on page 240 of that document : > http://www.leapsecond.com/museum/hp58503a/097-58503-13-iss-1.pdf We see that > the shape is starting at about 2E-12 at 1s, increase to 2E-11 at 100s before > decreasing again down to E-13 for above 10E3s... > > The setup #1 was using the Racal DANA Rb connected on the START input which > is specified at E-9 / E-10, given on page 16 of the manual : > http://bee.mif.pg.gda.pl/ciasteczkowypotwor/Racal/9470-9479.pdf > The EXT input receives the 1PPS from the HP58503b. It apparently drives both > the START and the STOP of the acquisition (the two lights are blinking and > the time between two measurement is no longer adjustable from the front panel > RATE potentiometer and the period between two samples is 1.0s (detected by > Timelab). > > But yes, the ADEV plot sounds really strange as it goes incredibly low after > few seconds which is not consistent with the stability of the sources I'm > using which is why I felt something was wrong > > On Setup #2 I've only replaced the Racal Dana Rb with the GPSDO to test. I've > not made this design and not checked yet anything on it. Could these > oscillations be from power supply noise ? To be checked. But how can it > follow the ADEV plot of the Racal Dana Rb ? mmm.... Coincidence is not > something I like too much and I believe something is clearly wrong in my > measurement > > But what ??? > > On the Timelab setup screen before launching the acquisition I've left all > the parameters as it without touching them. I've just seize 10E6 in the > frequency field. > > Ah, by thay Magnus, for the downmixed test I've forgotten to change this > value, I will check on monday when back at the office. > > > Stephane > > > > > -----Message d'origine----- > De : time-nuts [mailto:time-nuts-boun...@febo.com] De la part de Bob Camp > Envoyé : dimanche 18 janvier 2015 14:44 > À : Discussion of precise time and frequency measurement > Objet : Re: [time-nuts] question Alan deviation measured with Timelab and > counters > > Hi > > Ok, I didn’t think I’d seen the plots before. > > I agree that the plots look like “counter limited” data. That’s a fine > explanation at the shorter Tau’s. I also agree that some sort of periodic > “stuff” is getting into one of the signals and creating the ripple. What I’m > wondering about (and what makes me question the setup) is the fact that the > data is still “counter limited” at the mid to low parts in 10^-13 level at > just a bit over 100 seconds. A telecom Rb is doing pretty well to be at > 1x10^-12 at 100 seconds. Most GPSDO’s are doing well to be mid parts in > 10^-12 at that tau. Simply put, the data continues to be counter limited to a > pretty low point. > > Bob > >> On Jan 18, 2015, at 7:13 AM, Magnus Danielson <mag...@rubidium.dyndns.org> >> wrote: >> >> Hi Bob, >> >> On 01/18/2015 04:25 AM, Bob Camp wrote: >>> Hi >>> >>> I’m a little concerned about the measurement setup here. Based on the >>> quoted text, there have been a few messages in the thread that have not >>> showed up here. >> >> The messages got accidentally posted in the wrong thread. >> >>> ========= >>> >>> The “start” input on the counter is defined below. The “stop” input is not >>> defined. Is the counter running in time interval mode or in frequency mode? >>> >>> IF it’s in time mode - what is the stop hooked to? >>> >>> IF it’s in frequent mode - what is the gate time set to ? >>> >>> Is the “standard input” the missing front panel input or is it the external >>> reference input on the back panel? >> >> I was also considering the setup strange in this regard. Common switched in? >> >>> ========= >>> >>> I’m looking at the data on the link: >>> >>> http://www.ptp-images.com/affiche-directement-l-image-kccsz71c9a.html >>> >>> In both cases the slope is roughly 1/tau. Both plots end up in the 3 to 4 x >>> 10^-13 range at 100 to 300 seconds. That’s suspiciously good performance >>> for a rubidium or a GPSDO. Which is what makes me wonder about the setup. >>> >>> The Blue plot (1 pps?) ran for 18 minutes and has 1,114 points in it. The >>> Pink plot ran for about 9 minutes and has a bit over 500 points in it. Both >>> seem reasonable for a 1 pps to 10 MHz sort of setup. That may explain part >>> of my confusion above. >>> >>> Again - I apologize if this all got explained in a post that went missing >>> here. >> >> Not really. The plots looks to me like measurement setup baseline plots, >> with some sine noise in them. >> >> Cheers, >> Magnus >> _______________________________________________ >> time-nuts mailing list -- time-nuts@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@febo.com To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > > > > --- > L'absence de virus dans ce courrier électronique a été vérifiée par le > logiciel antivirus Avast. > http://www.avast.com > > _______________________________________________ > time-nuts mailing list -- time-nuts@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@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
