[warn] StatusCode: BadNoCommunication (0x80310000)

[Ispeack]

[ You can tag that as a question ]

Hello ,
I have several OPCUA ITEM nodes linked to an OPCUA Client node in Read like this ( I can't show the real flow for confidentiality reasons )

each OPCUA ITEM node belongs to a separate PLC which is connected to an OPCUA server and I request a read from this OPCUA server by the OPCUA Client node every second but some PLCs are under maintenance and I get this error message

" great drawing on the picture 🧐"

my question is: is it possible to exclude the reading of a certain OPCUA ITEM node that is causing “problems” after a defined number of attempts, and to restart the reading after a certain time in order to time out bad communication errors?

thanks for your help ,
have a good holiday too I saw on another post that you were on vacation ;) think of relaxing

[mikakaraila]

No this kind of feature is not possible by OPC UA stack. Instead you should build flow that will remove items that are not valid.

One idea could be first test items one by one and collect valid ones that you will use then finally.

[Ispeack]

Do you know how I could test each element independently? My PLCs are all connected to the same OPCUA server and have a common trigger ?

[wyplzx]

I think you can use UaExpert to check whether you can read every item from OPCUA server firstly.

[Ispeack]

I think you can use UaExpert to check whether you can read every item from OPCUA server firstly.

yes, that's already been done as part of a feasibility study. All my variables are accessible, but as I have several PLCs on an IOT gateway, some PLCs are under maintenance and therefore inaccessible, while others are, for example:

PLC 1 : ok
PLC 2 : ok
PLC 3 : NOK

obviously the variables of PLC N°3 are no longer accessible and this creates a bad communication error message because node-red manages to establish an OPCUA connection to my gateway but the frame stops there and I wanted to know if there was a way to disable variable reading in my message without having to rebuild a temporary gateway program.

perhaps by using a function in the OPCUA ITEM node, but I'd have to do some more tests on the subject