Fix P-733 AutoZero call #24
Open
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
1 participant
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.
...and add some spaces to error messages for nicer formatting.
There was a mismatch between the function call automatically generated by LabView and the actual PI call.
Generated call:
True call:
Fix:
Note that, once fixed, the pdLowVoltageArray input had to have constant values filled in (in this case I put -5 in entries 0-4), despite the fact that we explicitly tell the API to ignore this array in pbUseDefaultArray. If you just right click and add a constant without then manually updating the first few entries (at least enough to account for the number of axes you plan to AutoZero), the call will still fail even with a 1 in pbUseDefaultArray.