This document contains the VeriStand known issues that were discovered before and since the release of VeriStand 2020 R6. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 1181886 |
System Definition File created with (ECUMC) System Definition API uses invalid "SupportedTarget" entryUsing the System Definition API to create a system definition file which includes an ECUMC Custom Device fails to deploy on Windows.
Workaround: Edit the system definition file to use "PharLap & Windows" in the "Driver VI Path_X" node. The source distribution is found and deployment is successful.
|
Reported Version: VeriStand 2020 R4 Resolved Version: N/A Added: Apr 16, 2021 |
|
| 115349 | 602639 |
Triggers to start DAQ counter output tasks are not usableDAQ counter output
channels start without waiting for a start trigger, preventing the counters
from being synchronized with the rest of the system.
Workaround: Make a backup copy of the DAQ plugin XML file at %ProgramData%\National Instruments\NI VeriStand 2015\System Explorer\DAQ Plugins. In the copied file, change "true" to "True" in each of the property setting sections where lowercase “true” appears. Afterwards, move the backup XML out of the DAQ Plugins directory to prevent an error from occurring.
|
Reported Version: VeriStand 2015 SP1 Resolved Version: N/A Added: Jul 26, 2021 |
| 116062 | 638101 |
Alarm groups are difficult to assign with more than 13 alarms in the system definition fileWhen there are more than 13 alarms in a system definition, the System Explorer Alarms configuration page may not show all alarms. For alarms that do not appear, users will be unable to assign alarm groups through System Explorer.
Workaround: Edit the system definition XML file by hand to set alarm groups.
|
Reported Version: VeriStand 2016 Resolved Version: N/A Added: Jul 26, 2021 |
| 116076 | 650143 |
Model parameter files do not import correctly when Windows localization settings specify "," as the decimal separatorParameters included
in the Stimulus Profile Editor shipping example fail to import because model parameter
files generally do not support commas as a delimiter.
Workaround: Change the Windows system language to English before importing model parameter files.
|
Reported Version: VeriStand 2016 Resolved Version: N/A Added: Jul 26, 2021 |
| 1505083 |
Error 363504 returned when restarting the VeriStand engine on a password-protected RT TargetThe Restart VeriStand
Engine button found in the Document pane of the Mapping Diagram generates an
error when the connected RT target is
password-protected. Workaround: Set a blank password for the RT controller.
|
Reported Version: VeriStand 2019 R3 Resolved Version: N/A Added: Jul 26, 2021 |
Issues found in this section will not be listed in future known issues documents for this product.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 115960 | 572887 |
Setting the Frame Type Option in the Raw Data Frame Configuration Page Has no EffectAs the frame type is pulled from the XNET database, the system definition setting does not affect the XNET configuration.
Workaround: Set the frame type in the XNET database. Do not use the Raw Data Frame Type Configuration option in the system definition.
|
Reported Version: VeriStand 2014 Resolved Version: N/A Added: Apr 16, 2021 |
Explore Support Content and Product Documentation
Ask the NI Community
Request Support from an Engineer
A valid service agreement may be required, and support options vary by country