09-30-2009 02:34 AM
10-02-2009 08:07 AM
Hello 7even,
IVI drivers are based on an attribute model, but it is highly recommended that you call the high-level API functions to control the instrument. Get/Set should be used only if there is not a function that meets your needs.
Most IVI Specific Drivers use VISA to communicate with the instrument because it abstracts out the instrument control bus, but you can use other communication methods.
What type of instrument is your IOLink device?
Cheers,
NathanT
10-05-2009 03:39 AM
10-05-2009 04:53 AM
10-05-2009 08:55 AM
Hello 7even,
I am by no means a VISA expert, so hopefully someone who is can answer your question about VISA passports; however, I don't think that creating a custom VISA passport is the best approach. Please take a look at these two online IVI documents:
How IVI-C Instrument Driver Technology Enables System Longevity and Platform Portability
Using IVI Drivers to Build Hardware-Independent Test Systems with LabVIEW and LabWindows/CVI
The IVI Engine does not directly call into VISA, it is at the IVI Specific Driver level that the Instrument I/O calls are made, and most (but not all) IVI Specific Drivers use VISA.
Cheers,
NathanT
10-05-2009 12:17 PM
7even,
What sth said in his/her post is correct. We do not make the VISA spec readily available for general public to implement custom passports. Obviously, if someone wants to make a passport that makes business sense for NI, we can certain consider sharing the spec.
In your particular case, it doesn't sound like a custom passport is necessary. For one, as Nathan has pointed out, you do not need to go through VISA to make an IVI driver. Also, It seems that the IOLink is connected via the serial port. Is there anything missing in the existing VISA Serial passport?
10-07-2009 07:33 AM