Harold Hallikainen wrote:
> Is CDC the most appropriate class to use in such an application? I'm
> just sending ascii commands and getting responses.

CDC will make your device look like a COM port.  It has the advantage that
the driver is built into the OS, but comes with hassles too.  The
application has to let the user chose the COM port, since there is no way to
know what it is ahead of time.  Then there's the hassle of figuring out
which COM port number the system picked for your device.

It would be nice if there was a standard USB device type that presented like
a bidirection stream of bytes to the application.  Until we have something
like that, I use my own conventions and driver to go with them.  Endpoints 0
are used for private communication with the driver and the OS, and endpoints
1 implement the application visible bidirection stream of bytes.  The
USBProg PIC programmer, for example, is layered on this mechanism.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist