Conversation
I did not add the close VI to some of the U3 Raw VIs or any of the UE9 Raw VIs since they are configured to be used as subVIs.
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.
Added LJUD_Close to the VI examples with the following note:
Note: The LabJack device connection is closed automatically when the owning process is killed. This is the preferred way to release the device connection. LJUD_Close is not recommended. When running VI examples in LabVIEW the device connection is owned by the main LabVIEW process, which is not killed until you exit LabVIEW completely. LJUD_Close is used in LabJack VI examples to ensure that the device connection is released from the LabVIEW process between examples.