tverst Posted January 22, 2021 Report Share Posted January 22, 2021 To provide background, I'm just an IT guy trying to help out a department. I came upon the V350s while attempting to do a corporate network migration to a new Ethernet core and have been studying their characteristics to enable a successful migration. We have 9 v350 PLCs that controllers are used to regulate and monitor environmentals of aquatic tanks. Once the controllers lose network connectivity, it takes sourced Ethernet frames from the v350s to restore connectivity. This can be accomplished by sourcing an Email or initiating an alarm to restore their network connection. So I am able to restore their connection to our new Ethernet network. But I'd like for the v350s to be able to rejoin (w/o intervention) in the event of a network disconnect, power failure, etc.... I've experimented with the Auto Reconnect Parameters within the Info Mode. It works great. I set the counter keep alive for socket 0, which has been pre-set as the TCP Master. The other sockets are set as TCP slave or UDP and I do not have the same success when I set the counter keep alive for those sockets. But I'm extremely happy and content with how the controller behaves when I set socket 0. The only problem is that the socket defaults back when the system reboots. I can communicate with the controllers via HTTP., but see no configuration parameters. Do you have a recommendation for me to remote into the controllers to set the counter keep alive such that it does not default back after a reboot? Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.