Re: [Libusb-devel] control message to rfid device: connection timeout

[Kevin P. <ke...@in...>]

On 16 May 2008, at 20:22, Tim Roberts wrote:

> Kevin Pinte wrote:
>> well, I'm figuring out the system manual. I was trying to send the
>> inventory command
>>
>> (see: http://infogroep.be/~kpinte/sysman.pdf pages 58 and 59)
>>
>> I'm trying to send an inventory command. I tried:
>>
>> unsigned char buf[255];
>> usb_control_msg(rfid->dev, USB_ENDPOINT_IN + USB_TYPE_VENDOR, 0xB0,
>> 0x0000, 0x0100, buf, sizeof(buf), TIMEOUT);
>>
>> and
>>
>> usb_control_msg(rfid->dev, USB_ENDPOINT_IN + USB_TYPE_VENDOR, 0xB0,
>> 0x0000, 0x01, buf, sizeof(buf), TIMEOUT);
>>
>> also:
>> dmesg tells me:
>> usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd test rqt 192 rq 176 len
>> 255 ret -110
>>
>> Thanks (and sorry if I'm searching for help in the wrong place)
>>
>
> The manual does not contain enough information to know how to do this.
> It does not say, for example, whether these commands are vendor  
> commands
> for the control pipe, or whether these are messages for an interrupt
> pipe.  There is an implication in here that this device acts like a  
> HID
> device (a keyboard), and if so, all of that protocol might be HID
> messages traveling over the interrupt pipe.
>
> On Windows, they only support use through their custom DLL.  Have you
> tried plugging this in to a Windows system and capturing the traffic  
> to
> see how it really works?

On a windows machine the command that is sent is:

07 FF B0 01 00 1C 56

returning

06 00 B0 01 5C 63   Reader: No Transponder in Reader Field
or something like:
11 00 B0 00 01 03 00 E0 04 01 00 01 A9 2D 3B 41 C1   OK
where E0 04 01 00 01 A9 2D 3B is the serial of a tag

The sent command is a ISO Host Command: [0xB0] ISO15693 Command:  
[0x01] Inventory

the last two bytes (1C 56) are a CRC, described on page 18 in: http://infogroep.be/~kpinte/sysman.pdf
the iso command is described on page 58


in attachment there is the output of an strace on my test-program. For  
what I can see the hex command being send is not correct, but I have  
no clue on how to send the correct hex-string or command. Also, is  
there a CRC-check being done by lib-usb before sending the commend?

Thanks a lot,

Kevin Pinte.