Cc: javax-usb-devel@lists.sourceforge.net
Subject: Re: [javax-usb-devel] bulk transfer device problem
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 emulate
sage-
> 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 th
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 corr
ber 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
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 ad
ing to hit; do I need to wrap my messaging in some
kind of rs232 header+checksum ?
thanks.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan
Streetman
Sent: November 12, 2007 8:21 PM
To: Todd White
Cc: javax-usb-devel@lists.sourceforge.net
Subject: R
There is nothing intrinsically wrong with the device sending back 2
bytes for each submitted buffer, but it most likely indicates you are
not correctly talking to the device. Do you know the protocol for
this device?
Also there is nothing wrong with non-zero data beyond the transferred length.
O
