Configurable inizialization timeout for transfers #49
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
- debug print still included
…stand-data-sharing-framework-custom-device-plugins into dev/addInitTimeout # Conflicts: # Components/Transceivers/RDMA/Transceiver/Initialize Plugin.vi # Components/Transceivers/RDMA/Transceiver/Initialize Transfers.vi
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.
What does this Pull Request accomplish?
Exported initialization timeout s (30) as a control from
Components\Transceivers\RDMA\Transceiver\Initialize Transfers.vito make it configurable from system explorer. Modified all upstream VIs and ctls to export this property up to the corresponding page VIIMPORTANT : we bumped code of plugin VIs to 2021, to match DSF custom device version. Furthermore, one commit has many modified VIs from 5565 plugin that are not really involved into this feature development.
Why should this Pull Request be merged?
Configuration of this property avoids deployment errors with high channel count RDMA setups that span accross multiple chassis
What testing has been done?
Manual testing of custom device configuration, import, export of configuration files and field testing with beta customer