asynchronous GPIB calls

[Olivier Zimmermann]

Hi,

I have a program that processes several tasks, using GPIB instruments
that are reached through a single controller card.

Operations that involve GPIB are synchronized by passing the usual error
cluster from one to the next.

It is rather obvious that complementary operations at instrument level,
such as "asking for a measurement" and "reading the value", should lock
access to this instrument when called. But is there any reason why GPIB
ops on different instruments should be forced to sequential execution ?
Do LabVIEW GPIB functions support asynchronous calls ?

oz

[LesHammer]

> But is there any reason why GPIB ops on different instruments should be forced
> to sequential execution ? Do LabVIEW GPIB functions support asynchronous calls ?

The IEEE 488.1 standard says it should work. But there's no guarantee that
"Joe's Garage Shop" follows the standard, so it may depend upon your instruments.

Les.Hammer@CompleteTest.com

[Gary Lindgren]

Oliver,
I believe you can do this with Visa commands in VCI.
Gary


"Olivier Zimmermann" wrote in message
news:3DE5006D.6000202@isn.in2p3.fr...
> Hi,
>
> I have a program that processes several tasks, using GPIB instruments
> that are reached through a single controller card.
>
> Operations that involve GPIB are synchronized by passing the usual error
> cluster from one to the next.
>
> It is rather obvious that complementary operations at instrument level,
> such as "asking for a measurement" and "reading the value", should lock
> access to this instrument when called. But is there any reason why GPIB
> ops on different instruments should be forced to sequential execution ?
> Do LabVIEW GPIB functions support asynchronous calls
?
>
> oz
>