Connectivity issues to certain PLC over VPN

[Bolt]

I have a customer site with multiple PLC's behind a single StrideLinx VPN router. Each PLC is hardwired to the router, which is connected to customer's internet, which hops over several wireless bridges. I can connect to all of my PLC's, however, the results are mixed. Some connect well, others are continually dropping the connection. Same PLC, same program, similar > 100' length of Ethernet cable through same steel conduit, etc. See screenshots for further detail. What can I do to further troubleshoot? Is it just cable related?

[BobO]

I have a customer site with multiple PLC's behind a single StrideLinx VPN router. Each PLC is hardwired to the router, which is connected to customer's internet, which hops over several wireless bridges. I can connect to all of my PLC's, however, the results are mixed. Some connect well, others are continually dropping the connection. Same PLC, same program, similar > 100' length of Ethernet cable through same steel conduit, etc. See screenshots for further detail. What can I do to further troubleshoot? Is it just cable related?

There isn't much magic to PLC programming comms. Request packet, response packet. Response must come within the link timeout (defaults to 250ms). If it doesn't, we retry up to the configured number, then fail the request.

You can check the Timeout and Retries under the Advanced Settings button of the Port tab in the Link Editor. Longer might help.

Just to check the basic stability of the connection, you might try pinging the PLC from the programming PC. That'll give you can idea of the packet loss and turnaround time.

And we're always happy to look at Wireshark traces to see what's going on.