Error: read ECONNRESET about node-red-contrib-s7 HOT 6 CLOSED

Hello,

The TCP connection to the PLC is handled by the underlying plcpeople/nodeS7 library. Therefore, we probably need to check the code there. Do you have the full stack trace of this exception?

But, aside of that, an ECONNRESET usually means that the other side (here the PLC) has closed the connection. Are you maybe reaching the limit of the connections to the PLC? Are you connecting to the CPU or to a CP? Which model?

from node-red-contrib-s7.

Hello,
i am pretty sure the issue comes from the latest node-red v0.16.2 upgrade. What i did is that i clone a new mmc card with the node-red 0.15.3 and run it for a night without any issue. I upgrade the node-red to the latest and on the same overall system running the same code the problem appear. I did notice thought that during upgrade some errors about glyp appear that seemed the installer took care.
How i could produce a full stack trace?
I just have the output from the log of node-red.
It is connected to the CPU (S71200), i am thinking that the issue is not from the PLC side.
Thank you in advance

from node-red-contrib-s7.

I am also experiencing the error message "Error connecting to PLC: Error: read ECONNRESET". This has only started since the latest node-red v0.16.2. As trinity noted above, node-red v0.15.3 and v0.14.x did not exibit this issue. Any help is appreciated.

from node-red-contrib-s7.

I'm currently on a business trip and I'll be back by the weekend. so can check this only next week. Meanwhile, could one of you provide me the flow you're using for me to simulate your configuration?

Note: Since v0.2.4 you can enable the debugging output of the underlying nodes7 library by passing -v when running node-red, or by setting verbose: true on settings.js. Would be also interesting to see the library's output when the error happens

from node-red-contrib-s7.

Hi,

Updating the node-red-contrib-s7 then appears a timeout field that I set it to 4000 milleseconds.
When I do this the error ECON Reset stops.
A important note: When you are working with S7 node you have to use Deploy a modified flows.

from node-red-contrib-s7.

I'm closing this issue, since the only possibility of throwing this has been fixed upstream. If any of you still has such problems after upgrading to the latest versions of node-red-contrib-s7 (currently 1.1.2) and nodes7 (currently 0.1.15), please let me know and I reopen it

from node-red-contrib-s7.