1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
|
.. _faq-faq:
Miscellaneous questions
=======================
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 <hernan.grecco@gmail.com>.
It is currently maintained by Matthieu Dartiailh <m.dartiailh@gmail.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::
pyvisa-info
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 find 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 creating a configuration
file as described in :ref:`intro-configuring` (recommended) or by providing the
library path to the ``VisaLibrary`` or ``ResourceManager`` constructor::
>>> visalib = VisaLibrary('/path/to/library')
or::
>>> rm = ResourceManager('Path to library')
.. note::
If you get this error while trying to create a ``ResourceManager`` in Python built
for Cygwin (https://www.cygwin.com/) on Windows:
1. Check you are running the Cygwin build of Python by running ``python -VV``. If not, follow
the troubleshooting steps for Windows::
$ python -VV
Python 3.9.10 (main, Jan 20 2022, 21:37:52)
[GCC 11.2.0]
2. Specify the location of the ``visa32.dll`` or ``visa64.dll`` using the ``linux`` syntax
and Cygwin paths by creating a `.pyvisarc` (:ref:`intro-configuring`) file::
$ cat ~/.pyvisarc
[Paths]
VISA library: /cygdrive/c/Windows/System32/visa64.dll
or::
rm = pyvisa.ResourceManager('/cygdrive/c/Windows/System32/visa64.dll')
or::
rm = pyvisa.ResourceManager('/cygdrive/c/Windows/System32/visa32.dll')
Error: No matching architecture
-------------------------------
This error occurs when you the Python architecture does not match the VISA
architecture.
.. note:: 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::
pyvisa-info
You will see the architecture the Python interpreter was compiled for, and at the end you will
see the list of VISA libraries that PyVISA was able to find.
The solution is to:
1. Install and use a VISA library matching your Python architecture
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 :ref:`intro-configuring`.
If there is no VISA library with the correct bitness available, try
solution 2.
or
2. Install and use a Python matching your VISA library architecture
In Windows and Linux: Download and install Python with the matching
bitness. Run your script again using the new Python
In macOS, Python is usually delivered as universal binary (x86_64 and arm).
You can run it in x86_64 mode by running::
arch -x86_64 python myscript.py
or in arm mode by running::
arch -arm64 python myscript.py
You can create an alias by adding the following line
alias pythonx86="arch -x86_64 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 :ref:`intro-configuring`.
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]
Where can I get more information about VISA?
--------------------------------------------
* The original VISA docs:
- `VISA specification`_ (scroll down to the end)
- `VISA library specification`_
- `VISA specification for textual languages`_
* The very good VISA manuals from `National Instruments's VISA`_:
- `NI-VISA User Manual`_
- `NI-VISA Programmer Reference Manual`_
- `NI-VISA help file`_ in HTML
.. _`VISA specification`:
http://www.ivifoundation.org/Downloads/Specifications.htm
.. _`VISA library specification`:
http://www.ivifoundation.org/Downloads/Class%20Specifications/vpp43.doc
.. _`VISA specification for textual languages`:
http://www.ivifoundation.org/Downloads/Class%20Specifications/vpp432.doc
.. _`National Instruments's VISA`: http://ni.com/visa/
.. _`NI-VISA Programmer Reference Manual`:
http://digital.ni.com/manuals.nsf/websearch/87E52268CF9ACCEE86256D0F006E860D
.. _`NI-VISA help file`:
http://digital.ni.com/manuals.nsf/websearch/21992F3750B967ED86256F47007B00B3
.. _`NI-VISA User Manual`:
http://digital.ni.com/manuals.nsf/websearch/266526277DFF74F786256ADC0065C50C
.. _`AUTHORS`: https://github.com/pyvisa/pyvisa/blob/main/AUTHORS
.. _`Issue Tracker`: https://github.com/pyvisa/pyvisa/issues
.. _`virtual environment`: http://www.virtualenv.org/en/latest/
.. _`https://docs.python.org/3/whatsnew/3.8.html#bpo-36085-whatsnew`:
https://docs.python.org/3/whatsnew/3.8.html#bpo-36085-whatsnew
|
