Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

VISA GPIB Class Restrictions

I have two questions about VISA classes. I have a control that is ALWAYS a GPIB VISA control. I set it to VISA class "GPIB Inst". However I cannot (and have not been able for awhile) to use certain functions that a GPIB control should have available.

For example, I can not use "VISA Lock Asynchronous", while I can use VISA lock. Should not the input to VISA lock Aysnchronous be adaptable to other valid VISA types? VISA Lock is! Do I need to build my own polymorphic VISA lock Asynchronous? Or am I the only one using VISA locking? I have been casting it to a more general VISA Instr type, but then ran across a crashing bug in LV changing types.

The second issue is a really useful property for GPIB VISA that seems to be missing. It would be great (and is very necesssary) to be able to get a refrence to the INTERFACE for a specific GPIB address. For example, if I am having an error on a GPIB instrument and I want to send an "Interface Clear", it would be nice to be able to get a reference to that interface.

Conversely the "Send Interface Clear" could accept an Instrument Class VISA input and act on the interface for the bus that Instrument is on.

At the moment, the only solution that I have found is to get the VISA Resource name, and hack it to be an interface name and then open it and send an interface clear. This seems a bit kludgy and should be handled within the VISA resource framework.

LabVIEW ChampionLabVIEW Channel Wires


Message 1 of 4
(3,762 Views)
Hi sth,

I have filed a report on the VISA Lock Asynchronous Issue to the appropriate group. For now, a workaround would be to make a copy of the "VISA Lock Async" VI, and change the  classes of the VISA resource name controls in it to "GPIB Instr".

For the second issue, I'll recommend you file a product suggestion here

Hope this helps. Thanks!

Regards,


Message Edited by _Belle on 11-01-2006 09:59 AM

Ebele O.
National Instruments
Message 2 of 4
(3,726 Views)
Thanks for the update Ébele,

Can you provide a CAR for this? I assume that is what you mean by a "report". This helps keep track of this issue for both myself and the auditing software that searches these forums for CARs.

I will file a product suggestion. It is always a fine line between a suggestion and a bug! 🙂

Cheers,
Scott

LabVIEW ChampionLabVIEW Channel Wires


0 Kudos
Message 3 of 4
(3,716 Views)
Hi Scott,

Sure, the CAR ID is 430BLPZL

Thanks!
Ebele O.
National Instruments
0 Kudos
Message 4 of 4
(3,688 Views)