Well, I guess I'll have to look at the NI web site. I've looked for a means
of deteriming basic requirements for LABVIEW drivers for instruments (like
mine) which they don't support themselves. I have a TEK 'scope and logic
analyzer, both GPIB capable, but for which there have apparently not been
drivers written. I've also got a GPIB HDC and one of those common HP dual
3-1/2" floppy drive boxes, either of which would probably serve well as
listener/loggers. It would be nice to be able to use that setup to monitor
bursty events via the LA or 'scope.
Is there anything worthwhile that doesn't involve National Instruments?
Dick
----- Original Message -----
From: Tony Duell <ard_at_p850ug1.demon.co.uk>
To: <classiccmp_at_classiccmp.org>
Sent: Tuesday, April 11, 2000 11:57 AM
Subject: Re: HPIB to HPIL adapter
> >
> > I'd be interested in knowing what support there is for GPIB on the ISA
bus
> > in a PC. I've got a National Instruments GPIB interface card, yet have
> > never seen fit to lay out the dough for their GUI-based software. Is
there
> > anything out there other than LabView? I have some equipment that might
> > like the GPIB, but have not had need to use it since Windows became the
> > de-facto standard. Labview doesn't have drivers for the 'scope and
logic
> > analyzer that I'd be wanting to use.
> >
> > Any suggestions, preferably from someone who's actually used the stuff?
>
>
> I've never used GPIB on a PC, but I've used it often enough on PERQs and
> HP machines. And I believe that PCs can be similar.
>
> There is a library of subroutines (and I know that National Instruments
> sells (or at least used to sell) them for common MS-DOS languages) that
> allow you to do things like select a particular listener/talker on the
> bus, send/receive strings to/from a device on the bus, etc. And often
> allows you to do lower level things like sending particular controller
> messages, do a parallel poll, etc.
>
> You then need the documentation on the instrument you're using. It'll
> tell you want strings to send it, what commands it responds to, etc.
>
> Then you write a program (which in my case was always command-line based)
> that calls the appropriate library routines to send/receive the right
> things from the instrument.
>
> -tony
>
Received on Tue Apr 11 2000 - 14:41:58 BST