Products > Test Equipment
Flood of new Agilent 82357B GPIB-USB adaptors on eBay the real deal?
<< < (40/83) > >>
plesa:
Does anybody tried to load into the fake Agilent 82357B GPIB firmware measat_releaseX1.8.hex by fxload?
ManateeMafia:
Yes. I have been playing with the clone that looks like the Agilent original and linux-gpib. The clone worked with Benchvue but has been difficult/sporadic on a B+. It has been impossible, so far, to get working on a PI2.
I am typically getting timeouts when it is not working. There is a specific order to installing the software and I feel I am close to automating the whole thing, including modifying all files. I have an image file that is working, but I want the script working too.

It would be nice to get it working on a PI2, but I have ordered a second B+ so I can get the only functional one grabbing data on a 3458A.
MarkL:

--- Quote from: plesa on December 06, 2015, 07:43:02 pm ---Does anybody tried to load into the fake Agilent 82357B GPIB firmware measat_releaseX1.8.hex by fxload?

--- End quote ---

Yes, it works, but I had to change a couple of lines in the supplied script, /etc/hotplug/usb/agilent_82357a.  I had to export the PATH:

  export PATH=$PATH:/sbin:/usr/sbin:/usr/local/sbin:/bin:/usr/bin:/usr/local/bin

And add an explicit DEVNAME to fxload:

  $FXLOAD -D $DEVNAME $FXLOAD_OPTIONS -I $FIRMWARE

This is on CentOS 6.6, which is somewhat behind the times.  YMMV.
plesa:

--- Quote from: MarkL on December 06, 2015, 08:08:19 pm ---
--- Quote from: plesa on December 06, 2015, 07:43:02 pm ---Does anybody tried to load into the fake Agilent 82357B GPIB firmware measat_releaseX1.8.hex by fxload?

--- End quote ---

Yes, it works, but I had to change a couple of lines in the supplied script, /etc/hotplug/usb/agilent_82357a.  I had to export the PATH:

  export PATH=$PATH:/sbin:/usr/sbin:/usr/local/sbin:/bin:/usr/bin:/usr/local/bin

And add an explicit DEVNAME to fxload:

  $FXLOAD -D $DEVNAME $FXLOAD_OPTIONS -I $FIRMWARE

This is on CentOS 6.6, which is somewhat behind the times.  YMMV.

--- End quote ---

Thanks for sharing. And can you check adapter identification if it is H82357 or 82357B?
MarkL:

--- Quote from: plesa on December 06, 2015, 08:14:14 pm ---Thanks for sharing. And can you check adapter identification if it is H82357 or 82357B?

--- End quote ---
I don't have it anymore because it kept crashing (returned it to nettcy168), but here's the syslog from one of the moments when it did work plugging it in:


--- Code: ---Aug 17 16:15:58 localhost kernel: usb 2-3: new high speed USB device number 122 using ehci_hcd
Aug 17 16:15:58 localhost kernel: usb 2-3: New USB device found, idVendor=0957, idProduct=0718
Aug 17 16:15:58 localhost kernel: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Aug 17 16:15:58 localhost kernel: usb 2-3: Product: 82357B ()
Aug 17 16:15:58 localhost kernel: usb 2-3: Manufacturer: Agilent Technologies, Inc.
Aug 17 16:15:58 localhost kernel: usb 2-3: SerialNumber: MY49450490
Aug 17 16:15:58 localhost kernel: usb 2-3: configuration #1 chosen from 1 choice
Aug 17 16:15:58 localhost kernel: probe succeeded for path: usb-0000:00:1d.7-3
Aug 17 16:15:58 localhost kernel: gpib0: exiting autospoll thread
Aug 17 16:15:58 localhost kernel: agilent_82357a_detach: detached
Aug 17 16:15:58 localhost kernel: attached to bus interface 0, address 0xffff8802141c6000
Aug 17 16:15:58 localhost kernel: agilent_82357a_attach: attached

--- End code ---
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod