# Node-red-contrib-cip-st-ethernet-ip

**URL:** <https://discourse.nodered.org/t/node-red-contrib-cip-st-ethernet-ip/81530>\
**Category:** General\
**Tags:** uibuilder\
**Created:** [24 September 2023 06:44 UTC](https://discourse.nodered.org/t/node-red-contrib-cip-st-ethernet-ip/81530 "2023-09-24T06:44:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thahamp](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thahamp/32/82149_2.png) [@thahamp](https://discourse.nodered.org/u/thahamp)\
**Post date:** [24 September 2023 06:44 UTC](https://discourse.nodered.org/t/node-red-contrib-cip-st-ethernet-ip/81530/1 "2023-09-24T06:44:54Z")

</div>

Hi. I am using **node-red-contrib-cip-st-ethernet-ip** to connect with ControlLogix PLC. It is a very nice node and thanks to the contributor. I am trying to use this node in my manufacturing environment as a POC. Unfortunately now I am facing an issue which is described below:

> When a PLC is disconnected from the LAN for a known reason (like maintenance, firmware upgrade or software upload), it does not always automatically reconnect - I have to manually restart the flow.

Can you help me solve this issue? It needs to reconnect automatically, otherwise it is not useful for an industrial environment.

@machadotiago @gfcittolin and others.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [24 September 2023 08:10 UTC](https://discourse.nodered.org/t/node-red-contrib-cip-st-ethernet-ip/81530/2 "2023-09-24T08:10:05Z")

</div>

This has already been reported against the node's github repository, but it has not been addressed by the author, which suggests that the node is no longer supported. You may have to find an alternative solution or fork the repository and fix it yourself (or contract someone to do that).

> <https://github.com/st-one-io/node-red-contrib-cip-ethernet-ip/issues/39>
>
> \### Describe the bug
> When a plc, for a known reason (like maintenance, firmware… upgrade or software upload), is disconnected from the lan, sometimes it does not automatically reconnect : I have to restart flow manually.
> 
> \### Expected behavior
> I expect that the plc is reconnected, in all case, automatically
> 
> \### Logs
> This is the log (after this plc is disconnected)
> 26 Jun 08:03:27 - \[error\] \[eth-ip endpoint:Plc\] Error communicating with the PLC: {"generalStatusCode":4,"extendedStatus":\[0\]}
> 
> \### Environment
> - node-red-contrib-cip-st-ethernet-ip 2.0.0-beta.3
> - Node red 2.2.2
> - Node.JS 14.21.1
> - Plc Rockwell 1756L81ES
> - Windows 10 professional 21H2

---

<div class="post-metadata">

**Author:** ![thahamp](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thahamp/32/82149_2.png) [@thahamp](https://discourse.nodered.org/u/thahamp)\
**Post date:** [24 September 2023 15:45 UTC](https://discourse.nodered.org/t/node-red-contrib-cip-st-ethernet-ip/81530/3 "2023-09-24T15:45:49Z")

</div>

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/a/ca6d95db6096e9736bb5c4447263a52175051c1f.png)

With this setup, my issue solved. I have checked in the original code and noted, reconnection logic already implemented.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [8 October 2023 15:46 UTC](https://discourse.nodered.org/t/node-red-contrib-cip-st-ethernet-ip/81530/4 "2023-10-08T15:46:28Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.