Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: Watermark_JS on May 15, 2019, 03:19:48 PM
-
The PLC's I work with are all at remote sites and I connect to them over a VPN.
Ping times are typically around 130 but every so often will bounce up to 1200 or so for a few seconds.
I am trying to figure out how to optimize my Links so could use some advice about setting up the following values:
- Port: Advanced Settings: Timeout
- Port: Advanced Settings: Application Timeout
- Port: Advanced Settings: Scan Delay
- Protocol: Advanced Settings: Timeout
If there is a document that describes the difference between the various timeouts, please provide a link. When I called AutomationDirect Technical Support, the technician was unable to provide clarity or documentation.
-
The PLC's I work with are all at remote sites and I connect to them over a VPN.
Ping times are typically around 130 but every so often will bounce up to 1200 or so for a few seconds.
I am trying to figure out how to optimize my Links so could use some advice about setting up the following values:
- Port: Advanced Settings: Timeout
- Port: Advanced Settings: Application Timeout
- Port: Advanced Settings: Scan Delay
- Protocol: Advanced Settings: Timeout
If there is a document that describes the difference between the various timeouts, please provide a link. When I called AutomationDirect Technical Support, the technician was unable to provide clarity or documentation.
Yeah...it's confusing. This is legacy due to layered design. When we originally developed the comm server, everything was serial and the timeouts were protocol layer. When we added Ethernet, the layers skewed a bit, and the device layer started handling timing. The most relevant timeout for your purposes is the Advanced Settings: Timeout which is the device layer. The application timeout at that level is long and slow and shouldn't matter. Don't think the protocol level timeout is even used for Ethernet, only serial (and perhaps USB).