Update README to reflect new SW requirements.#22
Conversation
Signed-off-by: Michael Johansen <michael.johansen@emerson.com>
… confusing. Signed-off-by: Michael Johansen <michael.johansen@emerson.com>
|
|
||
| 1. LabVIEW 2026 Q1 Patch 1 (or newer) | ||
| 2. NI Measurement Data Services 26Q1 Patch 1 | ||
| - NI Measurement Data Services is installed as a recommended install when installing LabVIEW. |
There was a problem hiding this comment.
Hunter and I had a conversation about this. I think it is best to remove the line about MDS being installed with LV because it could lead to customer confusion.
Undesirable Scenario: User installs LabVIEW 2026 Q1 and elects to install MDS via LabVIEW. In this case, the examples will open broken because MDS 2026 Q1 will be installed which doesn't have the read poly VI updates.
So installing with LV is OK only if they are installing LabVIEW 2026 Q3.
I think the simplest way to allow the user to get these examples running on their machine is to have them:
- Install LV 26Q1 or later
- Install MDS 26Q3
If they happen to find out how to install MDS with LV, we still have the bullet that states that the examples won't work with older versions of MDS, so they will know to upgrade.
Part of the rationale here is that it's easier to upgrade MDS than it is to upgrade LabVIEW.
Let me know if you have any objections to this wording change.
There was a problem hiding this comment.
The alternative here is to increase the minimum required LV version to 2026 Q3, but as I stated in the first comment, upgrading LV isn't always an easy option.
2 participants
What does this Pull Request accomplish?
Since we updated the examples to use the new Read Data Value and Read Condition Value nodes, they now require MDS 26Q3. This PR updates the README to reflect this new requirement.
Why should this Pull Request be merged?
AB#3962861
What testing has been done?
None