search

mikakaraila / node-red-contrib-opcua

A Node-RED node to communicate OPC UA. Uses node-opcua library.
Other
208 stars 191 forks source link

Issue With Data Change Filter in OpcUa-Client Node #712

Open ParkMartins opened 2 days ago

ParkMartins commented 2 days ago

When using the 'MONITOR' action in the 'OpcUa-Client' node of the node-red-contrib-opcua package, I have encountered an issue with the configuration of the deadband in 'Absolute' or 'Percentage' mode. Upon initial deployment, both deadband configurations function as expected for the first subscription. However, subsequent subscriptions do not maintain this functionality, leading to the deadbands becoming inactive for all monitored value changes.

I have tried to define the configuration directly in the 'Opc Ua-Client' node and also on a function node. Both implementations work exactly the same way, like described above.

image

Expected Behavior: The 'Absolute' and 'Percentage' deadband configurations should consistently remain active for every monitored item. This is crucial for reliable data change monitoring.

mikakaraila commented 2 days ago

Hmm, I expect root cause could be without seeing your address space that variable should contain EURange that it could calculate from the min & max the percentage.

I need example flow to check & repeat problem, can you provide it?