I spent a couple frustrating hours debugging a test setup with
programmable power supplies and counters (to make automated measurements
of freq/Vtune on some VCOs, as well as Vsupply pushing)
I'm using something hacked from the sample Python code and the Prologix
Ethernet device (which has
27, 2013 8:16 AM
To: Discussion of precise time and frequency measurement
Subject: [time-nuts] GPIB, Proloigix, cables
I spent a couple frustrating hours debugging a test setup with programmable
power supplies and counters (to make automated measurements of freq/Vtune on
some VCOs, as well
On 01/27/2013 05:15 PM, Jim Lux wrote:
I spent a couple frustrating hours debugging a test setup with
programmable power supplies and counters (to make automated measurements
of freq/Vtune on some VCOs, as well as Vsupply pushing)
I'm using something hacked from the sample Python code and the
: [time-nuts] GPIB, Proloigix, cables
I spent a couple frustrating hours debugging a test setup with programmable
power supplies and counters (to make automated measurements of freq/Vtune on
some VCOs, as well as Vsupply pushing)
I'm using something hacked from the sample Python code
-nuts-boun...@febo.com [mailto:time-nuts-boun...@febo.com] On
Behalf Of Jim Lux
Sent: Sunday, January 27, 2013 8:16 AM
To: Discussion of precise time and frequency measurement
Subject: [time-nuts] GPIB, Proloigix, cables
I spent a couple frustrating hours debugging a test setup
jim...@earthlink.net said:
Connectivity to the prologix from host isn't the problem.The challenge
is on the gpib side. It was almost working, so I was wondering if there was
a systematic way to test.
How about a simple utility/hack that read/checks the device ID strings?
Plan 1 would be
I don't know if it would work on the Prologix adapter, but when you
install the drivers for the NI controller, they include a program called
'Measurement Automation Explorer' that includes the ability to scan
the bus, eavesdrop on the bus, send low-level commands and get
responses, etc.
Ed
