Re: How to open two USB pipes (0x81 - 0x02) in USB - vendor HID devi

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



HIDclass will not expose that endpoint for you to use since ti does not
comply to any HID spec

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"gerard_z" <gerard_z@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:17F4A187-CE22-4C21-A687-FB7899D42218@xxxxxxxxxxxxxxxx
Hi,

I have a vendor HID device with two additional endpoints, 0x81 (input) and
the optional endpoint 0x02. With only one endpoint (0x81) everything is
ok.
I can get a handle with CreateFile and I can send messages with
HidD_SetOutputReport and with WriteFile.

Now I have introduced a second endpoint (0x02 - output). I can still
discover the device and I can get a device handle. I even can send
messages
over the control pipe with HidD_SetOutputReport. However if I try to write
via WriteFile then I get an error 1784. I guess that I have to use another
handle which is pointing to the pipe with endpoint 0x02. But how???


Thanks


.



Relevant Pages

  • Re: How to open two USB pipes (0x81 - 0x02) in USB - HID devic
    ... I have a vendor HID device with two additional endpoints, ... With only one endpoint everything is ok. ... HidD_SetOutputReport and with WriteFile. ... over the control pipe with HidD_SetOutputReport. ...
    (comp.arch.embedded)
  • Re: Are endpoints and pipes unidirectional?
    ... The explanation of direction of endpoint and pipe on the specification ... Message pipes allow communication flow in both directions. ... is called the Default Control Pipe. ...
    (comp.os.linux.hardware)
  • Re: Cannot open USB control pipe in CE .NET
    ... WinCE 3.0 allowed opening of control pipe to device's endpoint #0. ... This does not meet the requirements of USB specification, ...
    (microsoft.public.windowsce.embedded.vc)