In article
<iintbeumtnbfkcpntohw__NOSP-253591.13315130082003@[EMAIL PROTECTED]
>,
Maarten Sneep <iintbeumtnbfkcpntohw__NOSP@[EMAIL PROTECTED]
> wrote:
> Graham Hinton wrote:
> > Maarten Sneep wrote:
> >> Worse still: Only GPIB _over_ Ethernet, normal GPIB-PCI cards are not
> >> even sup****ted. (Which is what most people in a lab are using I
> >> think).
> >
> > I checked this recently too. NI are only "sup****ting" the Ethernet
product
> > on OS X (at double the cost) precisely because they do not want to
debug
> > hardware cards on a system with no proper real time debugging tools.
> >
> > NI also claim that the PCI-GPIB card does not work past OS 9.1
although I
> > have one running under 9.2 - which shows the depth of their Mac
knowledge.
>
> Which is a shame really, given the history of labview, and the fact that
> LabVIEW is already running on three unix systems (GNU/Linux, Solaris and
> HP-UX) all with drivers for PGIB-PCI hardware.
>
> Of course the IOKit is a different beast, but other companies are doing
> fine in this respect.
>
> > Which begs the question of why use GPIB at all, it is an extremely
> > expensive solution. What type of signal generator is required? I could
> > build an audio one of similar spec to an HP 8903 with RS232/422 or
MIDI
> > control. Give me a spec and I'll give you a price.
>
> GPIB is expensive, and the fact that NI has cornered the market
> certainly doesn't help. Agilent (or the company formerly known as HP)
> has some GPIB cards, but they don't sup****t the mac either.
Which is ironic when you think about it, since GPIB arose from HPIB (at
least, as far as I understand it.) So, do Agilent now refer to their
IEEE 488(.2) products as "AIB"s now?
|
