Re: Strange errors with NI GPIB-USB-HS

> Hi Jakub,
> The suspicious entry is:
>       bEndpointAddress 0x81 EP 1 IN
>         bmAttributes 3
>           Transfer Type Interrupt
>           Synch Type None
>           Usage Type Data
>         wMaxPacketSize 0x0010 1x 16 bytes
>         bInterval 0
> A genuine card sets the poll interval for the interrupt endpoint to 2 ms: bInterval 2
> We have seen this before a couple of times.
> For the fake cards in the syslog you would see a message from the USB core similar to this:
> usb 2-1.1: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing to 7
> We have not figured out how the adapter is initialised in windows. For that a trace of the initialisation with usbmon would be required. As you are running windows in qemu this should be relatively easy to do,
> cheers,
> -Dave

Hi Dave,
I have already taken the snapshots of the usb communication with 
wireshark. Both for linux-gpib and for qemu+win10+ni driver.

The files are in the attached archive.

Thank you for looking at it.

Jakub

K tomuto e-mailu je připojen 1 soubor:
* usb-gpib-hs-capture.tar.bz2 (211 KB) uložen na Dropbox: 
https://www.dropbox.com/s/1k2n5acu801toqy/usb-gpib-hs-capture.tar.bz2?dl=0

_______________________________________________
Linux-gpib-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general