PyVisa | Trouble I identifying Resources | Rigol DS1054 | Keithly 2200-20-5

You need to create a udev rule for USBTMC devices.

echo 'SUBSYSTEM=="usb", MODE="0666", GROUP="usbusers"' >> 99-com.rules sudo mv 99-com.rules /etc/udev/rules.d/99-com.rules

Make sure you're in "usbusers" and do a reboot after that. (And really, reboot. I'm not certain what service has to restart to make it work.) pyVISA may be able to see them then.

Also, the license for R&S's VISA driver is not very restrictive. My interpretation is that you can use it with anyone's hardware/software. I also know they use pyVISA quite a bit, so it works really well with pyVISA. There are builds for various linux versions on their site.

No this just my desktop in my office. There is no other lab equipment attached. In fact right now the only thing that is attached is the Rigol Oscope.

Also also, "python-usbtmc" (via pip) can give you some troubleshooting information.

I see.. In that case, your PC cannot see the instrument at all, since there's no instrument name beginning with USB in your screenshot. It's likely a Linux issue, as @baldengineer describes.

Do I need to create the 99-com.rules file. My system had 99-nivisia_usbraw.rules file in the udev directory? Similar but not the same I can try both out until you reply.

I cannot say for sure. The udev rule may only apply when you're using the pyvisa-py VISA driver.

I do not own any NI software or hardware, so I am not able to use NI-VISA (it's against their license to use it unless it is with their tools, even though it is "free.")

I don't have it installed on any of the machines I've used with pyvisa. I either use pyvisa-py, R&S VISA, or Keysight's IO Connect. (But I have only used IO Connect on Windows, not Linux.)

If you have a VISA driver installed, such as NI-VISA, I would use their connection tools to verify what is connected and troubleshoot it. pyvsia's ResouceManager talks to it. For example, if NI-VISA's connection tool does not see the USB instruments, then pyvisa's ResourceManager won't either.

Remember, pyvisa talks to a VISA driver. If you don't have one installed, then it can use its own "pyvisa-py" driver.

Yeah I went down the NI-VISA path because that is where the Keithely ( Tecktonix) site took me.  I can try to uninstall it and use pyvisapy as the backend.  To be clear that pyvisa acts like visa drive giving me the usbtmc backend then I use pyvisa for scripiting?

Yes so it would seem. I am using the NI-VISA driver so I guess I am going try switching to pyvisapy. All this is little confusing, I must admit.

baldengineer 

Ok so switching to the pyvisapy backend seemed to do the trick. It now shot the usb address as detailed in the manual. Many thanks to everyone in the thread for help. See output belowl.

Python 3.10.10 (main, Mar  5 2023, 22:26:53) [GCC 12.2.1 20230201] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import visa
/usr/lib/python3.10/site-packages/visa.py:13: FutureWarning: The visa module provided by PyVISA is being deprecated. You can replace `import visa` by `import pyvisa as visa` to achieve the same effect.

The reason for the deprecation is the possible conflict with the visa package provided by the https://github.com/visa-sdk/visa-python which can result in hard to debug situations.
  warnings.warn(
>>> import pyvisa as visa
>>> rm =visa.ResourceManager('@py')
>>> rm.list_resources()
('USB0::1510::8704::9201747::0::INSTR',)
>>> 

I would still caution you on hosting devices on a computer connected to a corporate network. I have investigated cases of AC units upload 5G of data to a foreign site because someone thought it would be a good idea to automate making data available internally. Once the device is compromised internally and externally become the same place.