Agilent 82357b Usb/gpib Driver

• Agilent 82357a Driver
• Agilent 82357b Usb/gpib Driver Windows 10

Yesterday I installed the latest 'Agilent Connection Expert' software and tried to use an Agilent 82357B USB IEEE488/GPIB Adapter. But the USB device driver seems to have a bug. I tried on different systems (with Win 7 32 and 64 bit and XP) and it worked for a short time (on the 64bit OS). But when I repeated the instalation it showed the Problem again. According to the user guide troubleshooting information (see att.) it is not a hardware problem (only FAIL LED is on). Does anyone use this gear and has a hint?

In the device manager I remember 'GPIB Interfaces' entry showed up when it worked. But in the Failed LED Status it is missing. At least the agt357run.sys is in windows/system32/Drivers folder. The strange thing is, that the driver seems to be within the agilent connection expert and only be activated when the Adapter is pluged in and recognized correctly. I think if I could manually install/reinstall the driver that should solve the problem. Also I do not have an agilent DMM and therefore do not even need the Agilent Connection Expert for what I want to do.

Can you confirm whether this is software of hardware by testing it on another computer? It sounds like a Windows/driver issue to me. I wonder if uninstalling really removes every trace of the driver. You may be able to find something about removing old USB drivers, I don't have step-by-step instructions on hand. Another not very elegant solution would be to install another copy of Windows (eg. The Windows XP + VirtualPC solution shipped with Win7 Pro/Ultimate) in a virtual machine and install the Agilent software in there. This should give you a fresh Windows installation.

Thanks for your replies. According to the Agilent user guide it is a Software/Driver problem. I installed the Agilent Software already on three different PC and different OS. I changed also between diffent USB ports. It only worked on the System with Win 7 64bit, but not direct after the install, but after deleting Driver and rescan for new Hardware in the device manager.

Unfortunatey I have not managed to repeat this. I will build up a new PC system with new XP and SP3 Installation, so I am sure nothing is installed that could possibly make trouble. A fresh install is a good idea, the three systems might have something in common (virus scanner, configuration) that interferes with the Agilent software. Does Agilent offer older versions of their drivers for download? Anything special about USB power management that might cause troubles?

I wouldn't plug the GPIB interface in the computer before installing the driver, that can sometimes cause trouble. If Agilent offers installation instructions, then I would try to follow them step by step. It might be something stupid like it being touchy about connecting the device before installing the driver. I tend to use NI GPIB hardware because if the presumably better software. A fresh install is a good idea, the three systems might have something in common (virus scanner, configuration) that interferes with the Agilent software. Does Agilent offer older versions of their drivers for download?

Agilent 82357a Driver

Anything special about USB power management that might cause troubles? I wouldn't plug the GPIB interface in the computer before installing the driver, that can sometimes cause trouble. If Agilent offers installation instructions, then I would try to follow them step by step. It might be something stupid like it being touchy about connecting the device before installing the driver. I tend to use NI GPIB hardware because if the presumably better software. For anyone interested, I had good experience with the Agilent support.

Very kind and helpful. What I learned and found out myself, is: - Installation seems to be somehow tricky - if there is an older Agilent IO Lib. Version on the PC, it needs to be deinstalled first and you need to manually check in 'Program Files' and clean it if necessary - after restart no other program should be running - then install as Administrator - after finish, plugin the 82357B USB2 Adapter, but watch out it seems to be critical with the amps that a USB port is able to deliever (I now use a hub with power supply, just to be sure) I checked and repeated the procedure several times (just to be sure it really works). Now it works with the latest Agilent IO Lib.

Agilent 82357b Usb/gpib Driver Windows 10

Version 16.3 on Win 7 64 bit and XP Prof. Here are my notes on building linux-gpib for a debian (ubuntu) variant 1: sudo apt-get install linux-headers-$(uname -r) 2: svn co 3: cd trunk/linux-gpib 4:./bootstrap (this extra step should be done if using svn version) 5:./configure (now do like normal build) 6: make 7: sudo make install 8: depmod -a 9: ldconfig 10 sudo apt-get install fxload Done building. My notes says i have to do this, on every boot (genuine Agilent adapter).

Note the modprobe (where the module is loaded) Steps (on every boot) 1: modprobe agilent82357a (You could put agilent82357a in the file /etc/modules, then it should load automatic) 2: lsusb Bus 001 Device 008: ID 0957:0518 Agilent Technologies, Inc. 82357B GPIB Interface 3: fxload -t fx2 -D /dev/bus/usb/001/008 -I /usr/share/usb/agilent82357a/measatreleaseX1.8.hex 4: lsusb Bus 001 Device 008: ID 0957:0518 Agilent Technologies, Inc. 82357B GPIB Interface 5: fxload -t fx2 -D /dev/bus/usb/001/009 -I /usr/share/usb/agilent82357a/measatreleaseX1.8.he 6: sudo gpibconfig Now only light in Green 'Ready' on USB dongle, and ready Config is in: /etc/gpib.conf - Maybe adapt. Hope this helps /Bingo. It's correct that linux-gpib prob never will go into the kernel. And that the current maintainer would like a replacement.

But that said. I'm running (building linux-gpib from scratch) and the SVN version is quite easy to get working on the distros i use, Linux Mint 14 and Debian 7. It's a bit annoying to have to rebuild it every time you install a newer kernel, but i have automated it with a buildscript.

And have not had any problems yet. I'd rather do that, than having to boot up M$, even though i have considered to run XP in a VBOX. But for now i haven't had any problems with the SVN code.

Agilent Technologies 82357b now has a special edition for these Windows versions: Windows 7, Windows 7 64 bit, Windows 7 32 bit, Windows 10, Windows 10 64 bit, Windows 10 32 bit, Windows 8,Windows 7 Service Pack 1 (Microsoft Windows NT) 32bit, Windows 10 Mobile 64bit, Windows Vista Home Basic 64bit, Windows 10 Home 64bit, Windows 10 Education 64bit, Windows 7 Starter 32bit, Windows 10 Pro Education 64bit, Windows Vista Ultimate 64bit, Windows 10 32bit, Windows 10 IoT 64bit, Windows 10 Pro 64bit. Please Note: There are particular operating systems known to have problems with Agilent Technologies 82357b:. Windows 10 Team. Windows 10 Mobile Enterprise. Windows Vista Starter.

Windows 10 Education. Windows XP Home Edition, for home desktops and laptops. Windows Vista Home Basic. Windows XP Professional. Windows 7 Home BasicIf you encounter problems with the direct download for these operating systems, please consult the driver download manager for the specific Agilent Technologies 82357b model.