Loading Profile...
EM202 serial flow control problem
Hi there again,
we are pushing some data (about 100bytes at a time) though serial port with 38 400 bps., then we forward it over UDP broadcast. Time to send 100bytes at this speed is about 30ms. So, when sending every 50-60ms, everything goes ok, no data loss occurs. But then sending every 30-35ms, with uart flow control enabled and in full-duplex mode, something strange happen: after a while, when flow control needs to be used (probably due to buffer filling), data sent through uart is constantly repeated and no new data is beeing received. It just keeps sending the same data on and on.
I can't find any reason why this is happening.
thanks in advance
chris
we are pushing some data (about 100bytes at a time) though serial port with 38 400 bps., then we forward it over UDP broadcast. Time to send 100bytes at this speed is about 30ms. So, when sending every 50-60ms, everything goes ok, no data loss occurs. But then sending every 30-35ms, with uart flow control enabled and in full-duplex mode, something strange happen: after a while, when flow control needs to be used (probably due to buffer filling), data sent through uart is constantly repeated and no new data is beeing received. It just keeps sending the same data on and on.
I can't find any reason why this is happening.
thanks in advance
chris
1 person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?Could you send the problem over to Tibbo Tech Support? support@tibbo.com
This "could" be a bug, so please be more detailed on how to reproduce the problem, thanks. -
Inappropriate?it's not a bug in Tibbo, it was entirely our fault: polarisation on CTS/RTS pins was reversed.
However, there is still a problem with speed 115200 with flow control on. We are processing data with TIOS platform. Data is being received from serial and then passed to UDP broadcast socket. Even when data is simply "pushed" from serial to UDP socket (no processing occurs, except for ser.getdata and sock.setdata), UDP socket seems to contain truncated data. On 34800 everything seems to be ok. Data (about 100bytes) passed through serial is sent with 1 second interval, so it shouldn't be throughput problem. -
Inappropriate?I'm just wondering -- if you send just 100 bytes once every second, why do you have to use 115200 baud?
(Sorry I don't have any useful advice at the moment, but I just saw this in the forum and got curious...) -
Inappropriate?Well, generally we will send this data more frequently, say every 30-50ms. One second interval is just for testing purposes only, to check 115200 baudrate.
-
Inappropriate?I see...
I guess maybe writing Support directly would be a good idea for this one. Of course, you can leave it in the forum, but using Support directly would probably get you faster results.
If you do get this resolved, I would love to hear about it in the forum. :)
EMPLOYEE
EMPLOYEE
