extended the capabilities of the 'custom routes' functionality to all…#69
Open
efranke83 wants to merge 1 commit into
Open
extended the capabilities of the 'custom routes' functionality to all…#69efranke83 wants to merge 1 commit into
efranke83 wants to merge 1 commit into
Conversation
…ow setting routes on additional nisync hardware modules by using the syntax "\<HW module>\<terminal>"
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.
…ow setting routes on additional nisync hardware modules by using the syntax "<HW module><terminal>"
What does this Pull Request accomplish?
This pull request will add the capability to set (and clear) custom routes to additional nisync modules that are not set in the main page of the CD as Timekeeper or SyncMod.
Why should this Pull Request be merged?
This was done to accomplish the standard use case of a PXI-6683H module disciplining the PXI Clock through the System Timing slot of the chassis with a nisync module such as the PXIe-6674T.
What testing has been done?
Testing has confirmed disciplining the PXI Clock through IRIGB -> PXI-6683H -> PXIe-6674T.
The IRIG and 6683H used existing capabilities of the CD. The new custom routes feature was used to connect the 6674T ClkIn to the PXI_Clk10_In.