Thanks to all who responded on this issue. With some more help from
Russ Winsper at Apple, we eventually got our device and comm port
working OK. For the benefit of any archive browsers with similar
problems, the final solution was to change our descriptors like this:
1. In the Communication Class Interface Descriptor, we find we need to
set bInterfaceProtocol=0x01 (Hayes modem command-compatible)
2. In the ACM Functional Descriptor, we set bmCapabilities=0x0F (all
commands)
3. In the Call Management Functional Descriptor, bmCapabilities=0x03
(can do command management, but commands multiplexed into data
channel).
Now, in point of fact we don't handle any commands of any sort in any
fashion (the device isn't *actually* a modem...) but this way things
work. Russ tells us that in a future release the first requirement is
likely to be relaxed, and that we could probably have set the second
field to just 0x02: but we haven't tested that.
Once again, thanks to everyone who offered us help
-- Dave
- Dave
- Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/usb/email@hidden
This email sent to email@hidden
