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.