# Node-red is not letting me work with Simatic Manager online

**URL:** <https://discourse.nodered.org/t/node-red-is-not-letting-me-work-with-simatic-manager-online/76845>\
**Category:** Industrial\
**Created:** [23 March 2023 00:38 UTC](https://discourse.nodered.org/t/node-red-is-not-letting-me-work-with-simatic-manager-online/76845 "2023-03-23T00:38:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![romenger](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/romenger/32/77979_2.png) [@romenger](https://discourse.nodered.org/u/romenger)\
**Post date:** [23 March 2023 00:38 UTC](https://discourse.nodered.org/t/node-red-is-not-letting-me-work-with-simatic-manager-online/76845/1 "2023-03-23T00:38:20Z")

</div>

While connected with Node-red on my PLC s7-300, I cannot connect with the simatic manager on this plc (192.168.9.30) but I can connect to another plc (192.168.9.12) on the same network and it is using the one flow different on the same server as node red Node-red. The network is very unstable and accessing the server via a client terminal is not always possible. Now if I stop the Node-red server everything works again.

---

<div class="post-metadata">

**Author:** ![romenger](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/romenger/32/77979_2.png) [@romenger](https://discourse.nodered.org/u/romenger)\
**Post date:** [26 March 2023 02:21 UTC](https://discourse.nodered.org/t/node-red-is-not-letting-me-work-with-simatic-manager-online/76845/2 "2023-03-26T02:21:51Z")

</div>

The application is developed using the Node-red contrib s7 package I believe there is a problem in the code that may be causing it to not interrupt the connection after finishing the acquisition and when the function node receives a new payload it creates a new connection until that it is impossible for me to connect with the clp again

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [26 March 2023 07:48 UTC](https://discourse.nodered.org/t/node-red-is-not-letting-me-work-with-simatic-manager-online/76845/3 "2023-03-26T07:48:52Z")

</div>

Are you making lots of flow changes & deploying?

Are you using Full Deploy mode?

I suspect [this issue](https://github.com/st-one-io/node-red-contrib-s7/issues/102) is related.

Until that is fixed, change your node-red deploy method to "modified nodes" - it may reduce the amount of additional connections.

![deploying-flows](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/6/26bba7417811d0ee0d94b11c67187a48de79925d.jpeg)

---

<div class="post-metadata">

**Author:** ![romenger](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/romenger/32/77979_2.png) [@romenger](https://discourse.nodered.org/u/romenger)\
**Post date:** [7 April 2023 13:45 UTC](https://discourse.nodered.org/t/node-red-is-not-letting-me-work-with-simatic-manager-online/76845/4 "2023-04-07T13:45:20Z")

</div>

it interrupts or crashes. in fact, there are no alarms running on the prompt until it loses communication.  
I noticed that this is only on one of the streams so I'm looking into code which may have some kind of inconsistency leading to this issue.

---

<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:** [6 June 2023 13:45 UTC](https://discourse.nodered.org/t/node-red-is-not-letting-me-work-with-simatic-manager-online/76845/5 "2023-06-06T13:45:45Z")

</div>

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