Network connectivity issues can cause frequent packet loss forcing MCL to resend packets. As the communication degrades, application (i.e. MCL Client) performance declines. In some cases, the application may fail.
Situation and Symptoms
- MCL Client throws errors and sometime fails
- MCL-Net log records warnings such as status_repetitionblock, incorrect sequence received, and RETRY
Problems in the network can cause packet loss or packet latency (arriving too late). MCL efforts to retry and resend information will eventually fail if it loses too many packets or the retries take too long.
Assuming the user cannot avoid the network connectivity issues, using smaller packet size may help. In our experience, it’s best to use a lower block size. 512K often works best for both the device and MCL-Net. To successfully reduce packet size, you must change settings both in MCL-Net and the MCL-Clients. Doing so, will ensure that packets are smaller and can be sent quickly.
MCL-Client Block Size Setting: Setup Menu> Host Setup > Application> Communication Mode > Details
Idle and Retry Timeout
Otherwise, you could also try increasing the Idle Timeout and the retry timeout. This might help elevate problems occurring after inactivity by the terminal itself.