한국어 English Chinese Russian
bannerbar

Q&A



Your information is protected by SSL.
No. 717 Re: CSE-M53 sio buffer 2013-02-01

Hello.

This is a technical support team of Sollae systems.
Data loss might occur because of the a difference between LAN and Serial speed.
I recommend you use the flow control.
Here are answers.

1. SIO RX buffer?
-> 2048 bytes

2. Is there a way to visualise errors such as buffer overflows ? to visualise the actual number of bytes in this buffer ?
-> if you click the [Status] button at ezManager, you can see the count of sio_rx.
Please check the sio_rx count and send data size. If it is not the same, data loss might occur.. And you can see the net_tx count, it is the actual number of bytes.


3. flow control mechanism
-> nearly full. when the empty space less than 1/4(512bytes) in RX buffer, RTS pin will be active.
And then if empty space remain over 3/4 of buffer size, RTS pin will be inactive.

4. would the module continue to accept data for a while?
-> yes, buffer has a empty space, if not data loss might occur too.


Have a nice day.
Thank you.


> Jean Taeymans wrote:
> ------------------------------------
> Dear,
>
> I am using the CSE-M53 in TCP-server mode with a almost continuous stream of data at 230kbaud (some 17.5kbytes/s, 75% of the theoretical capacity) and no flow control over a 100Mbit/s LAN.
> I notice that entire data chuncks are fairly often lost, without any TCP error at the client side. Can somebody comment about the depth of the sio rx buffer ? Is there a way to visualise errors such as buffer overflows ? to visualise the actual number of bytes in this buffer ?
> Is there a description of the flow control mechanism (in the non Telnet RFC2217 mode), i.o.w. when is the RTS asserted ? : when the rx buffer is full ? nearly full ? would the module continue to accept data for a while ?
>
> Best regards,
> Jean.

Writer Sollae Systems Company