Open amrelk opened 5 years ago
Since you know the address of your instrument, can you try to directly open the resource ? I would like to understand if the issue is limited to list_resources
or is wider.
Also note that currently, pyvisa-py assumes that the board number is 0 which may break with your adapter. If you have a good solution to determine the proper board number to scan from linux-gpib feel free to open a PR.
After some probing with strace, it appears that pyvisa-py looks for gpib.conf at /usr/etc/gpib.conf instead of /etc/gpib.conf where it is installed. Making a symlink fixed the issue. Not sure if this counts as a bug or not.
Thanks for the update. Could you detail a bit more how you reached that conclusion ? Pyvisa-py specifies nowhere where to look for gpib.conf so I am curious to understand where that erroneous value is coming from.
My NI GPIB-USB-HS can communicate with my devices just fine with
ibtest
but not with pyvisa-py.Here are the steps to reproduce (with my system info at the end):