开云体育

-----Original Message-----
From: hp_agilent_equipment@...
[mailto:hp_agilent_equipment@...] On Behalf Of jdtckr
Sent: Tuesday, August 23, 2011 11:51 AM
To: hp_agilent_equipment@...
Subject: [hp_agilent_equipment] GPIB communications with HP 5334A, HP
5316A Counters

I have been struggling with harvesting data from the two mentioned meters,
and am hoping that some experience in the group can come to my rescue, or
at least enlightenment.
I am using an Agilent 82357B USB GPIB adaptor, with IOLibSuite 15.5 (or
16.1) under Windows XP Pro (and Windows 7 Pro) to communicate with my
test equipment quite nicely. My problem seems to be that the HP counters
act differently that my other test equipment, and I am trying to

what is happening, and what to do about it.
I can send commands, like IN or RE, and they respond, and I can get data
back from them after a fashion, but *not* the way I get it from other
instruments. When addressed to talk, both counters send out a stream of
readings, until they are made to shut up (presumably by an UNTALK message
of some kind). I am much more used to a device issuing a single reading,
and exerting EOI during the last character, generally a CR or LF, which

counters do *not* seem to do. Whatever commands are issued when IOLib
times out will cause them to stop sending. I have also discovered that if

artificially induce EOI before the IOLib timeout, I can read all the data
accumulated before the EOI (albeit, the CRs and LFs are presented to me as
"<0d>" and "<0a>", as if they were un-decoded bytes, rather than

as with other instruments.)
First, is this the normal behavior for these counters? Is it possible

has been damaged, and just not being exerted on the bus at the proper

How are these devices normally read with IOLib? I know that, at least for

5334A, there is a high-speed binary reading mode, which I am *not* using.
Second, is there a way around this behavior? I've read through the
programming sections of both of the manuals, and have not seen any
reference that I consider helpful in this area.
Third, is there a way to get IOLib to retrieve just one reading, and give

to me? For this, I have tried telling IOLib that, for this device (the

should terminate a read on an LF (actually, on a byte = 10, or 0x0A), but

does not seem to have any effect. Am I doing it wrong? Do I need to do
something specific to enable it after setting it?
Eventually, I expect to be writing C code to control and read my GPIB
equipment; does anyone have suggestions on where to start? I have `scopes,
counters, DMVs, and generators, and will be characterizing some timing
issues.
TIA,
JimT