Roger is right. Do not use javax.usb. Linux will create a "fake" serial port for you automatically, it probably will be called "/dev/ttyUSB0". Use javax.comm to talk to this emulated serial port.
On Nov 13, 2007 11:02 PM, Todd White <[EMAIL PROTECTED]> 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. > > - todd. > > > -----Original Message----- > From: Roger Lindsjö [mailto:[EMAIL PROTECTED] > Sent: November 13, 2007 12:31 AM > To: Todd White > Cc: javax-usb-devel@lists.sourceforge.net > Subject: Re: [javax-usb-devel] bulk transfer device problem > > > Todd White wrote: > > I have all the details of the protocol for the device. However, what's > > coming back is a total mismatch -- not at all part of their defined > > protocol. > > > > At this stage, I'm not trying to talk to the device at all -- all I was > > trying to do was submit a receive buffer, in advance of sending a message > > per the vendor protocol. > > > > A lot of things are working ok, in the sense that I am able to read the > > interface, pipe info, etc. thus the USB interface on the device is > > communicating. > > > > One point: the "device" target is a USB-RS232 converter in front of the > > physical device I'm trying to hit; do I need to wrap my messaging in some > > kind of rs232 header+checksum ? > > > So basically you have two devices you are trying to communicate with, > first the usb->rs232 (1) and then your actual device (2) (which is not a > usb device at all?). The protocol you are talking about, is that for > device 1 or device 2? If it is for device 2, then I don't think you > should use javax.usb at all, but instead talk the serial protocol > through javacomm or /dev/stty0 (or similar) since device 1 it probably > already handled by linux. > > However, it should be possible to talk to device 1 directly if you also > have the protocol for that device and the protocol could be simple but > my guess is that you also have to configure it with baud rate, parity > bits etc. Also, presending a receive buffer would probably not work, > device 1 should have an internal buffer that fills up as device 2 sends > data, and that data can be fetched from device 1, the protocol might > even be as simple as the one you are trying to use. > > //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 > ------------------------------------------------------------------------- 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
