Matthias,
We don't run XON/XOFF flow control, as our data stream are binary. That's
why I tried rts/cts and dtr/dsr.
In our case the data loss is inconsistent, that is, it is not the same
character every time and looses several characters each time. Therefore I
don't think this is the library filtering certain characters.
(off topic)
I'd hate to have to switch back to the ftdi supplied D2XX drivers, but that
may be the only solution. The readme for those drivers mention an required
bus reset on device insertion, cause an interruption of data to other
devices. Do you know if this corrupts the data transfer, or just delays it
somewhat?
Thanks.
Dave
> -----Original Message-----
> From: Matthias Janke [mailto:janke@xxxxxxxxxxxxxxxxxxxxxxx]
> Sent: Friday, March 20, 2009 2:39 AM
> To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: Release 0.15 and the ft2232 data loss.
>
> Hi,
>
> > It looks like a data overrun
> > or dropped data.
> >
> I had a similar Problem with a FT232 in serial mode with RTS/CTS
> (further details see
> http://developer.intra2net.com/mailarchive/html/libftdi/2009/msg00002.h
> tml)
> To me it seems that libftdi somehow filters CR on inbound. Due to time
> restrictions we switched to D2XX driver, which does not have this
> problem, so i didn't investigate any further. It also seems that
> running the same program(open/write/close) more than once seems to
> eat the first char (in our case a #) resetting the bus (replug device)
> does fix this.
>
> > Any ideas on where to look
> > next?
> I'd sugest somwhere in the reciving part. It might be in device
> initalisation part, since CR is the default XON/XOFF char.
>
> >Could this be an issue with libusb?
> I don't think so since D2XX and libftdi use the same libusb and the
> problem occures only with libftdi.
>
> Cheers,
> Matthias
>
>
> --
> libftdi - see http://www.intra2net.com/en/developer/libftdi for
> details.
> To unsubscribe send a mail to
> libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
