disable Máximum failed session count en 4.5

[jeeslo]

Hi!
I made the upgrade from version 4.4 to version 4.5 with this last problem that I have with the Scada communicator is Modbus, is that with this new parameter “Device request retries count on error” that varies from 1-100 when the network is stuffy or for any other reason the communicator has many mistakes me for the process completely, with version 4.4 I had no problem. As I can disable “Device request retries count on error” comm. session errors in the Line?

I want the line active continue to work with or without network errors

• This topic was modified 8 years, 5 months ago by jeeslo.
• This topic was modified 8 years, 5 months ago by jeeslo.
• This topic was modified 8 years, 5 months ago by jeeslo.

[Mikhail]

Hi,
Please post here a part of communication line log. I recommend to leave Device request retries count on error unmodified and equal to 3.

[jeeslo]

Hi Mikhail!!!

This is what happens when such (Requests (total / errors): 142/3) when it reaches the number 3, the communicator device is disconnected. To resolve I have to restart the whole Scada-Comunicator ver.4.5.0.2
I’ve tried changing “Device request parameter count retries on error” to the maximum that is always reaching 99 error number for all communication.

With version 4.4 everything worked perfectly.

File Line001 LOG:
2015-11-19 10:30:59 Establish a TCP connection with 172.16.182.24:502
Error establishing TCP connection: Once the socket has been disconnected, you can only reconnect again asynchronously, and only to a different EndPoint. BeginConnect must be called on a thread that won’t exit until the operation has been completed.

2015-11-19 10:30:59 Unable to communicate with the device because connection is not established

2015-11-19 10:30:59 Establish a TCP connection with 172.16.190.111:502
Error establishing TCP connection: Once the socket has been disconnected, you can only reconnect again asynchronously, and only to a different EndPoint. BeginConnect must be called on a thread that won’t exit until the operation has been completed.

2015-11-19 10:30:59 Unable to communicate with the device because connection is not established

2015-11-19 10:30:59 Establish a TCP connection with 172.16.182.26:502
Error establishing TCP connection: Once the socket has been disconnected, you can only reconnect again asynchronously, and only to a different EndPoint. BeginConnect must be called on a thread that won’t exit until the operation has been completed.

2015-11-19 10:30:59 Unable to communicate with the device because connection is not established

2015-11-19 10:30:59 Establish a TCP connection with 172.16.182.151:502
Error establishing TCP connection: Once the socket has been disconnected, you can only reconnect again asynchronously, and only to a differ

Scada-Comunicator Comunicator Line Log:
2015-11-19 10:35:49 Establish a TCP connection with 172.16.182.24:502
Attempt to establish TCP connection can not be earlier than 5 seconds after the previous.

[Mikhail]

You have found a major bug. Thanks!
I’ve sent you a fix. Please try it and post a result here.

Do not forget to return Device request retries count on error back to 3.

[jeeslo]

Mikhail Hello!

I have good news!! I tried the .dll received and worked perfectly.

I thank you very much for your help.

Good day!!

[Mikhail]

Hi,
Good news 🙂
Thank you for your help in finding the cause.
I’ll include the fix in the distributive within a few days.

[Author]

Posts