Is PyVISA endorsed by National Instruments?¶
No. PyVISA is developed independently of National Instrument as a wrapper for the VISA library.
Who makes PyVISA?¶
PyVISA was originally programmed by Torsten Bronger and Gregor Thalhammer. It is based on earlier experiences by Thalhammer.
It was maintained from March 2012 to August 2013 by Florian Bauer. It was maintained from August 2013 to December 2017 by Hernan E. Grecco <firstname.lastname@example.org>. It is currently maintained by Matthieu Dartiailh <email@example.com>
Take a look at AUTHORS for more information
Is PyVISA thread-safe?¶
Yes, PyVISA is thread safe starting from version 1.6.
I have an error in my program and I am having trouble to fix it¶
PyVISA provides useful logs of all operations. Add the following commands to your program and run it again:
import pyvisa pyvisa.log_to_screen()
I found a bug, how can I report it?¶
Please report it on the Issue Tracker, including operating system, python version and library version. In addition you might add supporting information by pasting the output of this command:
Error: Image not found¶
This error occurs when you have provided an invalid path for the VISA library. Check that the path provided to the constructor or in the configuration file
Error: Could not found VISA library¶
This error occurs when you have not provided a path for the VISA library and
PyVISA is not able to find it for you. You can solve it by providing the
library path to the
>>> visalib = VisaLibrary('/path/to/library')
>>> rm = ResourceManager('Path to library')
or creating a configuration file as described in Configuring the backend.
Error: visa module has no attribute ResourceManager¶
The https://github.com/visa-sdk/visa-python provides a visa package that can
visa module provided by PyVISA, which is why the
visa module is deprecated and it is preferred to import
pyvisa instead of
visa. Both modules provides the
same interface and no other changes should be needed.
Error: No matching architecture¶
This error occurs when you the Python architecture does not match the VISA architecture.
PyVISA tries to parse the error from the underlying foreign function library to provide a more useful error message. If it does not succeed, it shows the original one.
In Mac OS X the original error message looks like this:
OSError: dlopen(/Library/Frameworks/visa.framework/visa, 6): no suitable image found. Did find: /Library/Frameworks/visa.framework/visa: no matching architecture in universal wrapper /Library/Frameworks/visa.framework/visa: no matching architecture in universal wrapper
In Linux the original error message looks like this:
OSError: Could not open VISA library: Error while accessing /usr/local/vxipnp/linux/bin/libvisa.so.7:/usr/local/vxipnp/linux/bin/libvisa.so.7: wrong ELF class: ELFCLASS32
First, determine the details of your installation with the help of the following debug command:
You will see the ‘bitness’ of the Python interpreter and at the end you will see the list of VISA libraries that PyVISA was able to find.
The solution is to:
Install and use a VISA library matching your Python ‘bitness’
Download and install it from National Instruments’s VISA. Run the debug command again to see if the new library was found by PyVISA. If not, create a configuration file as described in Configuring the backend.
If there is no VISA library with the correct bitness available, try solution 2.
Install and use a Python matching your VISA library ‘bitness’
In Windows and Linux: Download and install Python with the matching bitness. Run your script again using the new Python
In Mac OS X, Python is usually delivered as universal binary (32 and 64 bits).
You can run it in 32 bit by running:arch -i386 python myscript.py
or in 64 bits by running:arch -x86_64 python myscript.py
You can create an alias by adding the following line
alias python32=”arch -i386 python”
into your .bashrc or .profile or ~/.bash_profile (or whatever file depending on which shell you are using.)
You can also create a virtual environment for this.
OSError: Could not open VISA library: function ‘viOpen’ not found¶
Starting with Python 3.8, the .dll load behavior has changed on Windows (see https://docs.python.org/3/whatsnew/3.8.html#bpo-36085-whatsnew). This causes some versions of Keysight VISA to fail to load because it cannot find its .dll dependencies. You can solve it by creating a configuration file and setting dll_extra_paths as described in Configuring the backend.
VisaIOError: VI_ERROR_SYSTEM_ERROR: Unknown system error:¶
If you have an issue creating a pyvisa.ResourceManager object, first enable screen logging (pyvisa.log_to_screen()) to ensure it is correctly finding the dll files. If it is correctly finding the dlls, you may see an error similar to: * viOpenDefaultRM(‘<ViObject object at 0x000002B6CA4658C8>’,) -> -1073807360 This issue was resolved by reinstalling python. It seems that something within the ctypes may have been corrupted. [https://github.com/pyvisa/pyvisa/issues/538]