Incorrect PID/VID for USB-GPIB-HS

[ShaunHall2]

Relevant info from ni488.inf:

%UsbHSDesc%       =  USB_INTERFACE,USB\VID_3923&PID_709B

While info from 'unknown device' in device manager shows the following:

USB\VID_04B4&PID_8613\6&39BBC440&0&2

There is therefore a mismatch between the PID and VID values expected in the driver inf and those that are presented by the hardware.  As such, the hardware is not recognized and I am unable to install the driver.

I have managed to successfully hack the .inf file by changing the expected PID and VID values and install the driver, however this leaves me with an unsigned driver issue making the USB-GPIB-HS invisible to all NI Programs (NI-MAX, Interactive Control). 

Anyone dealt with this?  I'm running on Windows 10.  NI says this device is still supported and it is still present in the driver inf... just with the wrong identifiers.

 - Shaun

[Gaheel17]

Hello Shaun,

There are two instances of %UsbHSDesc% = USB_INTERFACE,USB\VID_3923&PID_709B in the file and two of this files: one located at C:\Windows\System32\DriverStore\FileRepository\ni488.inf_amd64_84931954411e0cba and the second one at C:\Program Files (x86)\National Instruments\NI-488.2\Staging\ni488_win64. Did you change both instances in both paths?

The driver you mention is NI 488.2? What version did you install?

Regards,

Gaheel17

[ShaunHall2]

Dear Gaheel,

Thanks for your response.

I actually attempted everything using versions 17.6 (latest) and 7.0 (came on a CD with the USB-GPIB-HS) of NI 488.2.  Had exactly the same problem with each of them. 

I did catch both instances of the %UsbHSDesc% = USB_INTERFACE,USB\VID_3923&PID_709B in each of the file locations you mentioned.  I may have been unclear in my original post but doing this DID actually cause the driver to be installed.  However, doing this only got the device to show up properly in Device Manager (as GPIB Instrument --> USB-GPIB-HS) but not to show up in NI-MAX or Interactive Control or really be usable in any way. 

Appreciated.

 - Shaun

[Gaheel17]

Hi Shaun,

Take a look at this forum. It reports a similar issue and it seems that the cause was that the NI GPIB Enumeration Service was not started.

Regards,

Gaheel17