Add RTM2000 channel display control - #9
Merged
Merged
Conversation
…cus-v2 Add RTM2000 transactional scope focus
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
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.
Depends on
Merge and release the Core change before releasing this plugin version.
Summary
scope.channel_display_configure_v2for analog channels 1 and 20.14.0and document the capability boundaryHardware validation
A controlled RTM2032 run exercised CH2 through the real Core service:
The real mutation was exercised on CH2; CH1 uses the same bounded command path and is covered offline. The first acceptance wrapper hit a local diagnostics
KeyErrorafter the Core operation had already completed, so the state was independently re-read before recovery; this was a harness issue, not an instrument-operation failure.Validation
186 passed1849 passed, 3 skippedpip check: passedgit diff --check: passed