April 2021
This file contains installation instructions and compatibility information for VeriStand 2020 R5.
You can find more release information on ni.com.
Product Security and Critical Updates
Upgrade and Compatibility Issues
Automating the Installation of NI Products
Using NI Software with Microsoft Windows 10
VeriStand is configuration-based testing software, allowing you to develop, prototype, and test control systems using hardware I/O and your simulation models. The VeriStand software framework enables you to perform real-time or PC-based test configuration and execution that can be customized and extended with LabVIEW, NI TestStand, and other software tools. VeriStand includes a run-time editable user interface you can use to configure and implement triggered multi-file data logging, stimulus generation and playback, and real-time test sequencing.
VeriStand 2020 R5 has the following requirements:
Windows 64-bit Operating System | Real-Time Targets | |
---|---|---|
Required Software |
| VeriStand software, which you can install from NI Measurement & Automation Explorer (MAX) |
Note The following sections describe system requirements that apply if you use models, LabVIEW functionality, and .NET APIs in your system.
To configure and run a simulation using your existing compiled model, you need only VeriStand installed. You need additional software to perform other tasks with models, as the following list describes:
If you use other modeling environments, contact your model vendor for requirements for developing a model and converting it into a compiled model.
To create custom devices, menu items, workspace controls and indicators, or timing and sync devices, you must have LabVIEW 2020. The LabVIEW functionality in VeriStand always requires like-numbered versions.
The VeriStand .NET APIs require the following Microsoft software:
VeriStand supports the following operating systems:
Windows Systems | Real-Time Targets |
---|---|
|
|
1 NI software installs VC2015 Runtime and .NET 4.6.2. 2 Releases after 2021 will no longer include support for Phar Lap ETS. For more information, refer to the Phar Lap RT OS EOL Road Map. |
Note In 2021, VeriStand dropped support for Windows 7, Windows 8.1, Windows Server 2012, Windows Server 2008, and all Windows 32-bit systems. VeriStand 2020 R5 will not install or run on an unsupported OS. You cannot deploy or distribute applications that use VeriStand 2020 R5 to an unsupported OS. For more information about the changes to our OS support for 2021, refer to National Instruments Support for Windows 7, Windows Server 2008 R2, and All 32-Bit Windows.
When formatting a disk with a PXI Linux RT system image for VeriStand 2020 R5, select Linux RT System Image 20.7 and enable support for the LabVIEW 2020 programming environment. This feed contains the same driver versions included with the VeriStand 2020 R5 installer and avoids driver version conflicts while deploying XNET to a real-time target.
To install VeriStand, you must log on as an administrator or as a user with administrator privileges. You can activate VeriStand when prompted by the installer or activate later using NI License Manager. To use LabVIEW with VeriStand, install the like-numbered version of LabVIEW on the host computer.
You should also disable any automatic virus detection programs before you install. Some virus detection programs interfere with the installer. Be sure to check your computer for viruses and enable your virus detection programs after installing VeriStand.
You can install VeriStand with either the online installer or with installation media.
Download the VeriStand installer from ni.com/downloads. NI software includes NI Package Manager to handle the installation. Refer to the NI Package Manager Manual for more information about installing, removing, and upgrading NI software using NI Package Manager.
If you purchased this product with media, insert the VeriStand installation media and follow the instructions that appear on the screen.
Visit ni.com/security to view and subscribe to receive security notifications about NI products. Visit ni.com/critical-updates for information about critical updates from NI.
The following sections describe issues to be aware of when you upgrade to VeriStand 2020 R5.
Note NI recommends that you also review the Upgrade and Compatibility Issues in the readme files for each VeriStand version between the version from which you are upgrading and VeriStand 2020 R5. To access the documents, refer to the VeriStand Release Notes.
To run the VeriStand editor, the .NET Framework 4.6.2 must be installed. However, installing the .NET Framework 4.6.2 can break the Microsoft Visual C++ 2010 compilers, which are used to compile models for PharLap VeriStand targets. Using broken compilers results in error LNK1123. To resolve this Microsoft compiler issue, apply all service packs and updates for your version of Microsoft Visual Studio or Windows SDK. Refer to Microsoft Support Article 2757355 for more information.
VeriStand 2020 R5 does not support communication with uncompiled models.
Models compiled from LabVIEW VIs (.lvmodel or .lvmodelso files) using earlier versions of LabVIEW must be recompiled using LabVIEW 2020. The LabVIEW functionality in VeriStand requires like-numbered versions.
The VeriStand Model Framework contains changes to the files you use to develop and compile models in C/C++ and third-party modeling environments. If your system contains models compiled with previous versions of the Model Framework, choose from the following options to continue to use the models in VeriStand 2020 R5:
VeriStand Model Framework 2019 R3 to 2020 R4 does not support updates to tunable parameters if all the following are true:
NI recommends recompiling this type of model with Model Framework 2020 R5. You can use the VeriStand suite installer to separately download the Model Framework. Models compiled with Model Framework 2020 R5 are compatible with VeriStand 2019 R3 to 2020 R5.
VeriStand 2020 R5 can open projects from VeriStand 2010 to 2018 SP1 using the Open Legacy Project option in the Welcome tab.
In VeriStand 2020 and later, built-in Custom Devices, including the Embedded Data Logger, are no longer included when installing from offline media. Use NI Package Manager to include all supported Custom Devices during installation. To install Custom Devices separately, see the release page for each Custom Device on the VeriStand Add-ons support page
VeriStand includes the following documentation resources:
Resource | Contents | Access Instructions |
---|---|---|
VeriStand Help | Conceptual, how-to, and reference information for using VeriStand. | In software: Help»Show VeriStand Help... OR Windows Start menu: All Programs»National Instruments»VeriStand 2020 R5 Help |
VeriStand .NET API Help | Reference information for the .NET APIs included with VeriStand. You can access these assemblies from any .NET-compatible programming language or environment, including NI LabVIEW™ and NI TestStand™. | Windows Start menu: All Programs»National Instruments»VeriStand 2020 R5 .NET API Help. |
VeriStand Model Framework Introduction | Information about how to use the VeriStand Model Framework to compile your existing C and C++ model code so you can load your models in VeriStand. | You can access this guide from the <RootDrive>\VeriStand\<xxxx>\ModelInterface\custom directory, where RootDrive is the drive where NI software installs and xxxx is the VeriStand version number. Note You must explicitly select VeriStand Model Framework when you run the VeriStand installer. |
Note If you install VeriStand with the compatible version of LabVIEW, you also can access a subset of the VeriStand Help, including information about the VeriStand VIs and extending VeriStand functionality with LabVIEW, from the LabVIEW Help. From LabVIEW, select Help»LabVIEW Help.
VeriStand includes the following types of examples:
Note On the Windows OS, the default location of the <Public Documents> directory is C:\Users\Public\Public Documents.
You can automate the installation of most NI products using command-line arguments to suppress some or all of the installer user interface and dialog boxes.
If the NI product you are installing uses Microsoft .NET 4.0, the .NET installer may run before any NI software installs and may require a reboot before the installation of NI software begins. To avoid a .NET reboot, install .NET 4.0 separately before you install NI software.
For more information about automating the installation of NI products, refer to the following KnowledgeBase articles:
Microsoft Windows 10 is the latest version of the Windows operating system and features significant changes compared to previous versions. Windows 10 introduces several new capabilities and also combines features from both Windows 7 and Windows 8. For more information about NI support for Windows 10, visit ni.com/windows10.
Copyright
© 2009–2021 National Instruments Corporation. All rights reserved.
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.
NI respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction.
End-User License Agreements and Third-Party Legal Notices
You can find end-user license agreements (EULAs) and third-party legal notices in the following locations after installation:
U.S. Government Restricted Rights
If you are an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the technical data included in this manual is governed by the Restricted Rights provisions under Federal Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for military agencies.
IVI Foundation Copyright Notice
Content from the IVI specifications reproduced with permission from the IVI Foundation.
The IVI Foundation and its member companies make no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The IVI Foundation and its member companies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Trademarks
Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on NI trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.
Patents
For patents covering the NI products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the NI Patent Notice at ni.com/patents.
375380U-01