USB : Where's my Control Pipe ?

Hi,
I wrote an USB driver based on the PRN sample.
2 interfaces are reported.
I got 2 Pipes from the 2nd interface with 2 endpoints (Bulk-in & bulk-out).
Another interface was reported having 1 endpoint, but I was told this is the
interrupt-pipe.
I now need to set DTR, by using a control command.
I tried using lpIssueControlTransfer() on my BULK-OUT pipe, but that doesn't
work.

Where/How should I get my CONTROL-PIPE ?
From what I understand, this is some kind of default. ("endpoint 0")
Where do I find this endpoint 0 ? , (not beeing one of my bulk pipe's)
when found should I just create another PIPE from it myself ?

Greetings,
Rob.

Rob
Tue Jun 10 14:36:03 PDT 2008

Turns out that the control pipe is not explicitely present (visible) in the
driver.
You donot need to maintain your own PIPE * to the control pipe.
IssueVendorTransfer() writes to the control pipe....

My CDC Driver now works !
It's simple once you know everything... :-)

Greetings,
Rob.


"Rob" wrote:

> Hi,
> I wrote an USB driver based on the PRN sample.
> 2 interfaces are reported.
> I got 2 Pipes from the 2nd interface with 2 endpoints (Bulk-in & bulk-out).
> Another interface was reported having 1 endpoint, but I was told this is the
> interrupt-pipe.
> I now need to set DTR, by using a control command.
> I tried using lpIssueControlTransfer() on my BULK-OUT pipe, but that doesn't
> work.
>
> Where/How should I get my CONTROL-PIPE ?
> From what I understand, this is some kind of default. ("endpoint 0")
> Where do I find this endpoint 0 ? , (not beeing one of my bulk pipe's)
> when found should I just create another PIPE from it myself ?
>
> Greetings,
> Rob.
>
>
>
>
>