Deadband filter #159
Open
Deadband filter #159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dirk-zimoch
force-pushed
the
deadbandFilter
branch
from
b52eeaa
to
b63d50c
Compare
|
Rebased onto the latest master. |
dirk-zimoch
force-pushed
the
deadbandFilter
branch
from
b63d50c
to
68d76fb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New link option
deadband=<value>.See https://reference.opcfoundation.org/Core/Part4/v104/docs/7.17.2.
Currently, only absolute deadbands are supported.
Numeric items with
deadband > 0will send monitors only if the absolute change is equal or greater than the deadband value. In case of arrays, one element exceeding the deadband value is sufficient to send an update of the whole array.Non-numeric types like String cannot have a deadband. Setting up the monitored item may fail in this case with the error
BadFilterNotAllowed, so that no updates are ever sent.