Fixes for Agilent DSO-X 2022A #1015
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The Agilent DSO-X 2022A with MSO extension features 8 digital channels rather than 16. Querying for >8 results in
Query UNTERMINATEDnotices on the oscilloscope and freezes the application for ~26 seconds on startup. Leaving the channels enabled breaks the normal acquisition mode as it will not retrigger after one cycle.The second commit addresses a weird situation where my scope replies with
+0in response to:WAV:PRE?. This only happens on the 1st channel once the scope has finished acquiring data, the 2nd channel didn't present the same issue. Retrying the same command once if the string is unexpectedly small fixes this behavior.