Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Explore our global offerings or select your country from one of our five regions.Global
Découvrez nos offres globales ou sélectionnez votre pays dans l’une de nos cinq régions.
Goals and Symptoms
READ_VAR or WRITE_VAR does not re-establish communications after re-connecting cable.
Causes and Fixes
The READ_VAR or WRITE_VAR does not re-establish communications after re-connecting the
Ethernet TCP/IP cable.
This will occur if the communications timeout is left at the default value of zero (0). A timeout value of
zero 0) will cause the function block to never timeout. This results in the The READ_VAR and
WRITE_VAR block to never close the TCP/IP connection when the Ethernet cable is disconnected
and re-connected. The PLC will need to be stopped and re-started after the Ethernet TCP/IP cable
To resolve the issue, define a timeout value in the '%MW+2' management word of the READ_VAR
or WRITE_VAR block.
Sign up for all the latest solutions, offers and best practices straight to your inbox.
We are excited that you have joined the group. You will receive your welcome email soon describing the program and what to expect in the upcoming weeks. Enjoy!