How to catch config node error

General
1

Hi all,
I'm using the library node-red-contrib-s7 that have a config node where is stored the configuration of the comunication.
I need to catch this error that derive from the config node
image
If I catch the error in this way it don't works

image
image1127Ă—270 10 KB

there is a method to catch this error?

2

Does it appear if you connect a debug node to the S7 node? Set it to output complete message in case it is not in the payload.

1 Like
3

The debug node is alredy set to complete message object.
I think this error is generated by the node s7endpoint and not by the s7 in node
This is the library to be more exhaustive.
node-red-contrib-s7

4

You haven't got a debug node connected to the S7 node, it is connected to the Catch node.
Errors in the config node may be propagated up to the visible node.

1 Like
5

image
image1178Ă—395 13 KB

Do you mean it like this?
I still don't catch the error

6

Does it show anything?

7

No only the old error (PLC II is the name of s7 endpoint node)

8

What old error?

9


This only in the debug console

10

I notice that there is a similar issue already reported against the node and that this has not been responded to. It may be that the node is no longer supported.

1 Like
11

Ok I understand, so the error generated from this library is not catchable :confused:

12

It is up to the author of the node to pass the error to node-red so that it can be caught by a Catch node. Currently it looks as if it is just logging it.

1 Like
13

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