DynamicCalculator: Adapter command to assist troubleshooting #398
Conversation
This file contains hidden or 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
f4a7c57 to
d3cb58a
Compare
Source/Libraries/Adapters/DynamicCalculator/DynamicCalculator.cs
Outdated
Show resolved
Hide resolved
d3cb58a to
d9fc6f0
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.
This PR implements adapter commands to view the actual values of measurements received by the adapter as well as the values of variables used in the calculation of a given result. This is intended to assist with troubleshooting adapter configuration when the result of the calculation doesn't match expectations.
Here is a recommended approach for enabling these messages in a remote console application.
Once the console has captured some of the output, you can disable the messages again with these commands.
Here is some example output from an adapter using the following calculation:
If(freq >= 45 and freq <= 55 and volt >= 10000, 1, 0)FYI, the
xvariable is only included for timing and is not used in the calculation. In this case, the input device is providing frequency/voltage data at half the expected framerate, so the second result includes NaN values as input.