Products > Test Equipment

open source GPIB adapter

<< < (31/42) > >>

caiser01:

--- Quote from: alm on December 17, 2023, 10:09:16 am ---
--- Quote from: dazz1 on December 17, 2023, 09:52:45 am ---I would like to get my little old Linux Asus eeePC running pyvisa.  What do you suggest, and in what order should I install?  NI, R&S ?

--- End quote ---
I found installing a commercial VISA stack a pain on Linux. Especially maintaining it through OS upgrades. I'd also research what hardware they support. I know NI-VISA doesn't support NI GPIB-USB devices on Linux kernel versions from the last 15 years or so. I don't know about USBTMC.

I would use PyVISA-py as backend. This integrates much better with Linux and doesn't require any kernel modules or daemons to run.

--- End quote ---

I've been running R&S VISA on Linux on the Raspberry Pi with zero issues. Like the Windows version, the Linux version of R&S VISA is small, lightweight, and doesn't drag you into any sort of package dependency hell. The only quirk I've encountered is needing to explicitly reference the R&S VISA library in my Python scripts in order to keep pyvisa from automatically wanting to grab pyvisa-py as the backend, but it's pretty easy. I just have this at the top of all my Python scripts for GPIB:


--- Code: ---from sys import platform

if platform == "linux" or platform == "linux2":
    # Linux
    rm = pyvisa.ResourceManager("/usr/lib/librsvisa.so@ivi")
elif platform == "darwin":
    # macOS
    rm = pyvisa.ResourceManager("/Library/Frameworks/RsVisa.framework/RsVisa@ivi")
elif platform == "win32":
    # Windows
    rm = pyvisa.ResourceManager()
--- End code ---

alm:
What's the advantage of R&S VISA over PyVISA-py, which requires even less setup?

dazz1:

--- Quote from: alm on December 17, 2023, 04:58:02 pm ---What's the advantage of R&S VISA over PyVISA-py, which requires even less setup?

--- End quote ---

I had a look at your launchpad page.  I see you are maintaining GPIB firmware, kernel and user packages.
Can you please explain what each package is for (the use cases?)

alm:

--- Quote from: dazz1 on December 17, 2023, 06:47:39 pm ---I had a look at your launchpad page.  I see you are maintaining GPIB firmware, kernel and user packages.
Can you please explain what each package is for (the use cases?)

--- End quote ---
That isn't necessary to use with the adapter discussed in this topic, which uses USBTMC. As you can read in the PyVISA-py documentation, it just needs libusb for this.

The packages in my signature is for with commercial USB and PCI(e) GPIB interfaces like those made by Agilent, Keysight, NI etc. Also clones, as far as I know. There are kernel drivers, the user space libraries so native (C) applications can talk to them, and Python bindings so Python can talk to them. These packages would allow you to use for example an NI GPIB-USB-HS interface with PyVISA-py.

dazz1:

--- Quote from: alm on December 17, 2023, 07:11:36 pm ---
--- Quote from: dazz1 on December 17, 2023, 06:47:39 pm ---I had a look at your launchpad page.  I see you are maintaining GPIB firmware, kernel and user packages.
Can you please explain what each package is for (the use cases?)

--- End quote ---
That isn't necessary to use with the adapter discussed in this topic, which uses USBTMC. As you can read in the PyVISA-py documentation, it just needs libusb for this.

The packages in my signature is for with commercial USB and PCI(e) GPIB interfaces like those made by Agilent, Keysight, NI etc. Also clones, as far as I know. There are kernel drivers, the user space libraries so native (C) applications can talk to them, and Python bindings so Python can talk to them. These packages would allow you to use for example an NI GPIB-USB-HS interface with PyVISA-py.

--- End quote ---

OK so I should just follow the instructions for PyVISA-py. :-+

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod