Open bilderbuchi opened 4 years ago
Thanks for the detailed report.
Since you figured out how to get pyvisa-info
to work could you post those details, now ?
Machine Details:
Platform ID: Windows-10-10.0.18362-SP0
Processor: Intel64 Family 6 Model 142 Stepping 9, GenuineIntel
Python:
Implementation: CPython
Executable: C:\Users\buchner\AppData\Local\Continuum\miniconda3\python.exe
Version: 3.7.7
Compiler: MSC v.1916 64 bit (AMD64)
Bits: 64bit
Build: May 6 2020 11:45:54 (#default)
Unicode: UCS4
PyVISA Version: 1.10.1
Backends:
ni:
Version: 1.10.1 (bundled with PyVISA)
#1: C:\WINDOWS\system32\visa32.dll:
found by: auto
bitness: 64
Vendor: National Instruments
Impl. Version: 19923456
Spec. Version: 5244928
#2: C:\WINDOWS\system32\visa64.dll:
found by: auto
bitness: 64
Vendor: National Instruments
Impl. Version: 19923456
Spec. Version: 5244928
On Windows 10, I have connected an USB-serial dongle. This shows as ususal as COM3 in the package manager, and also as
ASRL3::INSTR
in NI-MAX, and I can connect without problems:When using the pyvisa-py backend, it curiously gets listed as ASRLCOM3::INSTR, which is not what I expected from the docs.
I don't know what the usb exception is about.
I cannot connect with ASRL3::INSTR from pyvisa-py (expected, I guess)
but it works with ASRLCOM3::INSTR
So, I don't understand why pyvisa-py inserts this additional
COM
in the resource name?One last thing that would be great if it could be fixed/allowed is resource names like "COM3" only. NI-VISA allows this, but pyvisa-py not. It would be helpful for the Windows users in my lab -- who typically think in "COMx" port names -- if this would work with pyvisa-py, too.
Version information:
Output of
pyvisa-info
Sorry, this is currently not working for me, see #229