Athira

also when connected to windows the hs+ showsamber light. But whenconnected to same raspberrypi(raspbian) it blinks between amber and green. Still the gpib_config command works andlooks like it is up. do you know if this is a matter of concern ?

well then would it be not possible to connect the device to linux for first time ?

Hi frank I connected a newHS+ device first time to windows and have capturedthe following attached. We can see here that device id changes fro 761e to 7618.

Hello Frank The lsusb -v gives the following : Bus 001 Device 004: ID 3923:7618 National Instruments Corp. Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x3923 National Instruments Corp. idProduct 0x7618 bcdDevice 1.00 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x004c bNumInterfaces...

So after connecting towindows , I disconnected it and connected to raspberry pi (raspbian ) and looks like th edriver is up. this means the firmware was already loaded to it from Windows sidewhen it was connected ?

Hi Frank I just captured the belowusing wireshark. Does this help ?

Hi Frank From the device manager in windows, the following id appeared for GPIB adaptor. Does it mean firmware loading for the device ? USB\VID_3923&PID_7618&REV_0100&MI_00

Hi Frank Do you know how to check in windows driver if the firmware is loaded? I cant find the device ID like in linux in windows except for the serial number. regards, Athira On Thu, Apr 9, 2020 at 12:35 AM Frank Mori Hess fmhess@users.sourceforge.net wrote: I have a new theory about your device id. Rather than a new version of the gpib-usb-hs, you might have an old version which requires a firmload upload before it is usable (this is how the gpib-usb-b worked). Try using your adapter under Windows...