Todd White wrote: > While I agree that it would be simpler to communicate via javacomm, I need > to use USB because the host that I am programming does not have an > accessible rs232 port. > > The device itself has a physical console where the parity bits / baud rate > etc are set. > > You are correct: the protocol I know is that of device (2). It sounds like > I need to discover the protocol for the usb->rs232 converter (device 1) to > move forward on this project. I will research in that direction. Thanks > for your advice. > Maybe I'm still misunderstanding, but you should be able to use javacomm even though it is a usb->rs232 converter. I think linux comes with drivers for several converters, see http://www.mjmwired.net/kernel/Documentation/usb/usb-serial.txt
It sounds interesting implementing a usb->serial "driver" for javax.usb, but I don't think it is necessary. //Roger Lindsjö ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ javax-usb-devel mailing list javax-usb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
