The clock-correction seemed a bit crude. I expected to find a PI-filter
and a phase-accumulator to steer the 300 MHz to 37 MHz synthesis.
Actually I do use a phase accumulator, in Fig. 26 it's inside the binary
search block. The phase is accumulated during several seconds (longer for
a noisy
Hello Hui,
I found that I needed:
Ag488Wrap.ibeos(devDesc, 0x040A); // 04 = terminate read when 0A = /n is
detected
as part of the initialization. Without this, the communication with my
5384A timed out.
Also, see what happens when you press the reset button when you get
error 52 while you
In message 00bf01cd4d12$f83a41d0$e8aec570$@pop.net, John Miles writes:
Hi John,
Congratulations on a good design.
Why the 78 MHz sample frequency ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since
Hi
At least with 60 Hz power (which may indeed behave differently than 50 Hz)
everything I have seen so far has been in the OCXO's I'm testing. The
TimePod it's self seems to be very immune to the usual ground loops and
power supply noise issues.
As you play with phase noise testing - be sure to
I have seen that others had a communication problem with the HP5386A. When
I use the Agilent IOLibrarySuite, this counter generates ghost sessions and
can't enumerate correctly. I thought it was a faulty GPIB port at first but
after reading all this I suspect it is the strange behaviour of the
Hi John,
Congratulations on a good design.
Thanks!
Why the 78 MHz sample frequency ?
Long story: it's mostly arbitrary, but at least with some ADCs, it's
beneficial to spur performance if the first few dozen harmonics of the ADC
clock rate and the most commonly-used test frequencies don't
Hello Mike:
Many thanks for useful information. The problem is I have no more
information of my USB-GPIB controller, so I don't know any command of this
device. I used stupid way to send my command, if I want send DI to increase
the display digis, I will convert DI to HEX code, it's 0x44
Hello Ton:
Thanks for your reply. I tried to send 0x040A to HP5386, but I did not
receive any response. I pressed RESET button when I got 52 error message, the
error message disappeared and frequency reading displayed in the receive buffer
area of my Serial port Assitant software.
Hui
On Mon, 18 Jun 2012 09:29:07 +0200, Ton wrote:
Hello Hui,
I found that I needed:
Ag488Wrap.ibeos(devDesc, 0x040A); // 04 = terminate read when 0A = /n is
detected
as part of the initialization. Without this, the communication with my
5384A timed out.
That matches my findings on my
Hui,
It sounds like the issue is with your OEM GPIB controller. Why don't you
post some pictures of it and see if any of the Time Nuts can identify
it? It probably is a generic version of some common interface.
Mike
On 6/18/2012 8:43 AM, Hui Zhang wrote:
Hello Mike:
Many thanks for
10 matches
Mail list logo
