Hey,
thank you for your hints.
I used libftdi 0.x so far but also tried version 1.x today. Unfortunately with
no success. It's the same problem with both versions.
Since the board I'm using is custom made, it might not even be the libraries
fault but there might be a problem with the board.
Interestingly I did find a workaround that seems to always work:
I am now sending my command byte per byte and always pausing for a second in
between each write.
So far I was successful with this workaround even though it's really not a
pretty solution :( Could it have something todo with the (low) baudrate of only
9600 of the chip?
Since I am only sending the command once (on startup) I think I can live with
the solution I found, still if you have any more hints, I'd be glad to find a
better solution.
Thank you
Tim
Am 21.03.2012 um 10:28 schrieb Matthias Janke:
> Hi Tim,
>
> Am Wed, 21 Mar 2012 09:24:52 +0100
> schrieb Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>:
>>> My device periodically sends sensor data across the usb interface once it
>>> received the start command, which is just the word "start" send in ascii
>>> letters to the device. Unfortunately the sending of the start command
>>> somehow fails.
>>
>> We had trouble back in the days with the first write command
>> getting lost. When we tried to track it down, the problem vanished.
>
> I had this problem where the first byte of the first write got lost only with
> the
> 0.x branch. I'm now using the 1.x branch and never lost any byte in sending or
> reading, even though it takes usually more than one read to get all bytes of a
> transmission.
>
> 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
|
