Open archerixx opened 5 months ago
Hmm, I fixed partly your flow so it works now:
Separated adding nodeIds and repeat readmultiple: OPCUA-ISSUE-690.json
OPC server was bugged, seems that timeout happens now only from time to time. It is probably server's fault.
Is there limit to how many requests at a time can be made towards one server?
If your server is made with all features that specification contains then it should have diagnostics (UaExpert can show). And the latest specification contains also server limits.
Hi,
Could you make this error/warning as one that can be caught with "Catch" node ?
Currently it keeps popping in debug and console and I can't do anything with it, so it would be great to catch it with Node-red's Catch node (so I can report in my system as device state)
Thanks
Sorry, but the error comes from the node-opcua... I expect that I cannot catch it.
After latest update, I am getting following error message: "Client node error on: error: [" error at active reading: Transaction has timed out ( timeout = 15000 ms , request = ReadRequest)"]"
This is example of my flow: opc_ua.json
Worked just fine before updates 2 weeks ago.