LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Changing VISA Libraries

Does anyone have an idea as to how I might
include a different VISA library (other than
NI's)? I have tried physically naming and
replacing the libraries and header files, but now
I get a miscellaneous system error message. If
you have any thoughts on this at all, please let
me know, Thanks!

Tim Thacher
KineticSystems Corporation


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
0 Kudos
Message 1 of 3
(4,796 Views)

What VISA library are you trying to change to?  We use the Agilent library, because all of our work is with the Agilent E5810A LAN / GPIB / RS232 unit.

Allen Cherry

0 Kudos
Message 2 of 3
(4,517 Views)
As for building your VISA app, simply include "visa.h" and link "visa32.lib".  Your app will simply search for VISA32.DLL that is currently installed in the target system.  The default is what placed in Windows/System32 but it follows Windows' PATH finding rules.  What you specially consider when writing/building your app are, do not use any VISA-vendor specific attributes.  In fact, NI-VISA has NI-specific attributes that can be passed to viGetAttribute/viSetAttribute but they generate an error when operating with other VISAs.  Plus, you must do the operation compatibility check with various kind of VISA versions that your target PCs may install.  All the VISA32.DLL from different vendors are ***BASICALLY*** equivalent and interchangeable each other, but not complete.  Some specific situations may show different behaviour.
 
As for VISA runtime environment, basically you should install only one VISA version.  For example, if a target PC installs Agilent, then NI-VISA should not be installed.  Although there are some special techniques for installing multiple VISA libraries on the same PC at a time, it may often corrupt.
0 Kudos
Message 3 of 3
(4,504 Views)