node-red-contrib-s7 icon indicating copy to clipboard operation
node-red-contrib-s7 copied to clipboard

checkbox for suppressing "Error: connect EHOSTUNREACH" in debug sidebar of NodeRed

Open digidax opened this issue 1 year ago • 10 comments

Is your feature request related to a problem? Please describe. When a PLC of a machine is not connected 24/7, it produces when requesting the IP of the PLC the "Error: connect EHOSTUNREACH". This is flooding the debug sidebar and also with the "catch node" the output can not be suppressed. So when working in Node Red on weekend, where over 90% of the PLCs are offline, it's terrible to read or monitor a message from a projected debug node.

Describe the solution you'd like A checkbox to disable / suppress this error messages.

Describe alternatives you've considered Was discussed here https://discourse.nodered.org/t/filter-errors-in-sidebar/71044 with no solution.

Additional context grafik

digidax avatar Nov 23 '22 05:11 digidax

As far as i know its possible to catch error messages with an CATCH node, but only if the error function is feeded with two arguments. node.error("Error : connect....",msg); Maybe this could be changed ?

1607David avatar May 19 '23 07:05 1607David

Hello @digidax ,

understand your concern, but the node was developed with machines that are operating 24/7 in mind, where any errors presented are of utmost importance, especially reconnection errors.

Adding a checkbox to suppress errors has a great potential for failure, as it would stop showing any errors that the PLC presents.

One solution would be for you to disable the endpoint when the PLC is not in operation.

fernandoamorim1703 avatar Jul 27 '23 19:07 fernandoamorim1703

There is another issue though: I changed the name and IP of my S7 node, and the error messages of the old name and IP dont stop. I then deleted all nodes, even uninstalled contrib-s7 from my nodered, and the error messages are still coming. Seems like some process is still there trying to make a connection.

ma-ze avatar Aug 03 '23 14:08 ma-ze

Hello @ma-ze Did you check the configuration nodes? Perhaps they are still instantiated.

fernandoamorim1703 avatar Aug 03 '23 15:08 fernandoamorim1703

Yes, after changing the configuration node (and then deleting it, and uninstalling the plugin) it still produces error messages.

ma-ze avatar Aug 03 '23 15:08 ma-ze

"Filter a node" to get the debug msg focus from a not connected S7 node doesn't solve the problem. EHOSTUNREACH error msg are everytime present an flooding the debug output. That is my problem. We have a lot of machines which are only temp. in use. So I don't really understand, why would it not possible to make a checkbox for disabling this EHOSTUNREACH error msg.

digidax avatar Aug 04 '23 04:08 digidax

+1 I've got the same issue. Due to energy savings we turn off varies control units, which do not produce parts leading to error messages spamming my debug view. Either a checkbox to suppress something or at least a field to change the interval of the node trying to reconnect to the plc would be helpful.

its-Zeke avatar Sep 14 '23 06:09 its-Zeke

Error: PLC error [0x8104]: This service is not implemented on the module or a frame error was reported

what is problem? image

AsepSubarkah avatar Dec 27 '23 09:12 AsepSubarkah

Hello @digidax ,

understand your concern, but the node was developed with machines that are operating 24/7 in mind, where any errors presented are of utmost importance, especially reconnection errors.

Adding a checkbox to suppress errors has a great potential for failure, as it would stop showing any errors that the PLC presents.

One solution would be for you to disable the endpoint when the PLC is not in operation.

If that is not an option, Could you point out how to turn off this error all together? Wich module do i need to edit, and what line of it?

My thanks image

Peturtjuhh avatar Jan 26 '24 14:01 Peturtjuhh