The following items are notable issues fixed between the release of LabVIEW PDM Acquisition Toolkit 2020 and LabVIEW PDM Acquisition Toolkit 2021 Q2, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of LabVIEW PDM Acquisition Toolkit.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 1198173 |
Examples take a while to load on first launchThe first time you launch the LabVIEW PDM Acquisition Toolkit examples, the examples take a while to load because LabVIEW must search for the files. This occurs because the examples expect the API in the examples folder but must search and find them in the vi.lib folder.
Workaround: After launching the first time, save the example to retain links to the API in the correct folder.
|
Reported Version: LabVIEW PDM Acquisition Toolkit 2020 Resolved Version: LabVIEW PDM Acquisition Toolkit 2021 Q2 Added: Dec 11, 2020 |
|
| 1195323 |
LabVIEW returns error -63195 when one of the timing engines is stoppedAlthough two timing engines can run in parallel in two separate VIs, when the timing engine that runs first is stopped, the second timing engine (i.e. the VI
that runs after the first timing engine has started running) also stops and returns error code -63195. ![]() This issue does not happen when the second timing engine is stopped.
The second timing engine can be stopped and started again multiple
times without affecting the first engine that is still running.
Workaround: There is currently no known workaround for this issue. |
Reported Version: LabVIEW PDM Acquisition Toolkit 2020 Resolved Version: LabVIEW PDM Acquisition Toolkit 2021 Q2 Added: Dec 11, 2020 |
Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.
These patches currently do not have any special instructions.