I was exposed to HPIL back in the '80's and, while there were some fancy
instruments, e.g. 6-digit DVM, I've not seen it used since then. In fact,
the GPIB is something I've seen surprisingly little, except on equipment
that was for sale. My TEK logic analyzer supports serial, parallel, and
GPIB interfaces, and I was hoping the GPIB would be a mite faster than the
serial interface. Unfortunately, since I got a portable logic analyzer
(model 1240) the three interfaces are mutually exclusive, so you can't talk
to the instrument over two paths, which might be nice.
The LabView is not irrelevant, but only because there are people willing to
pay to have it used in their installations. I'm perfectly satisfied to use
the GPIB command set as part of a program I write myself. I've found that
approach quite satisfactory, and there's certainly a shorter learning curve
than with some GUI-thingie that I can't manipulate comfortably because
someone else designed it.
Because I've had so little experience with the GPIB, and because I've got no
doc's on the National Instruments GPIB card I have, I'm at the mercy of
those who may have and be willing to "share" whatever details and drivers
they have. I'm open to any suggestions and your "spiritual guidance" is
always welcome.
Dick
----- Original Message -----
From: Tony Duell <ard_at_p850ug1.demon.co.uk>
To: <classiccmp_at_classiccmp.org>
Sent: Wednesday, April 12, 2000 12:00 PM
Subject: Re: HPIB to HPIL adapter
> > > Forget about Labview and its drivers...
> > >
> > That's my inclination as well. It's just that numerous local companies
use
> > it in their testing and are willing to pay almost excessive (if it's
what
> > they pay me it's not excessive) rates for people to write scripts and
> > drivers for Labview to drive their instruments. Many of them are
already
> > supported, but the new drivers are worth something.
>
> Ah, so there are other constraints on this :-)
>
> Personnaly, I've always done this because I wanted it for myself (not
> necessarily for home hacking, but perhaps for some official work I was
> doing). So I could use what languages and what user interface I like.
>
> [GPIB commands]
>
> > Yes, that's described in the manuals. I expect there'll be plenty of
> > surprises, though.
>
> Actually, I've found most instruments do behave as documented!.
>
> > > You do realise that you're going to need a controller (== computer
most
> > > of the time) on the GPIB. Linking the 'scope to the HP drive box
without
> > > also linking in a controller won't do anything. I know for a fact that
HP
> > > disk drives never operate as controllers and I doubt very much in
'scopes
> > > do either.
> > Oh, yes. The PC will do that, but at some point in the future, I might
want
> > to make up a little controller board with the necessary firmware to make
it
> > able to initialize and poll, etc, and then do some specific task. I
still
> > have a couple of those 9114's from T.I.
> ^^^^
> You mean 9914 I think. The HP9114 is almost-relevant to this -- it's the
> HPIL disk drive which can be useful for such data logging...
>
> > >
> > > And if you have a computer on the GPIB, you might as well log the data
to
> > > its disk drive.
> > >
> > It's not as portable, but if portability isn't a factor, that would be
my
> > choice.
>
> Oh, I don't know. An HP71B + HP82169 (the unit that started this
> discussion) is pretty small and can work as HPIB controller. Add a 9114
> disk drive on the HPIL loop if you want mass storage.
>
> -tony
>
Received on Wed Apr 12 2000 - 17:42:08 BST