search

st-one-io / node-red-contrib-s7

A Node-RED node to interact with Siemens S7 PLCs
GNU General Public License v3.0
112 stars 58 forks source link

S7 error is not propagated #98

Open mhechthz opened 3 years ago

mhechthz commented 3 years ago

Hi,

with the 2.2.1 version I get a read error from an S7 (probably something wrong there).

The node shows a yellow light and the info "fehlerhaft" (faulty). On the debug console I get at every flow (even if on "display only active workflow") the message "Fehler (ungültige Werte)" (Error - invalid values). I'm not sure if the German writing is from my system or from the SPS configuration or from else where.

The catch node in the workflow doesn't catch anything.

Any suggestions?

At least the expected behaviour is to send the error message from the node to the following node to be able to process the message and not to print the error at every workflow.

thermseekr commented 2 years ago

Hello all. The config node should propagate the error to the visible node so the catch node could... catch it. Here is another user having the same problem:

https://discourse.nodered.org/t/how-to-catch-config-node-error/52573

I'm currently not skilled enough to do it, maybe someone with the right skills could fix this and propose a PR?

ajeschmec commented 2 years ago

I experienced the same behavior, and also other error messages as "Error: connect ECONNREFUSED .. " are not propagated to catch nodes. The error remains after updating to version 3.1.0. Could someone fix this issue, please? It will be very helpful.

matteo-fantin commented 1 year ago

I would like to know if this feature will be implemented. Meanwhile I'll fork the project to have something to work with.

Updated

I just see that in code this is already doing. Is NodeRed problems? 🧐

image
OriolFM commented 1 year ago

Any updates on this? I'm having exactly the same issue. The visible node (s7 in) shows the offline status, which means the endpoint node is propagating the error to the visible node, but it does not generate any error message (on the s7 in node side of things).

The errors, in the meantime, are still uncatchable.