VeriStand 2020 R6 Readme

July 2021

This file contains installation instructions and compatibility information for VeriStand 2020 R6.

You can find more release information on ni.com.


Overview

System Requirements

Supported Operating Systems

Installation Instructions

Product Security and Critical Updates

Upgrade and Compatibility Issues

Accessing the Help

Finding Examples

Automating the Installation of NI Products

Using NI Software with Microsoft Windows 10

Legal Information


Overview

VeriStand is configuration-based testing software, allowing you to develop, prototype, and test control systems using hardware I/O and 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. Use VeriStand's run-time editable user interface to implement triggered multi-file data logging, stimulus generation and playback, and real-time test sequencing.

System Requirements

VeriStand 2020 R6 installs with the following:

  • NI-DAQmx 21.0
  • NI-VISA 21.0
  • NI-SLSC 20.0.1
  • NI-XNET 21.0
  • NI R Series Multifunction RIO 20.7

Refer to the following sections for system requirements that apply if you use models, LabVIEW functionality, and .NET APIs.

Simulation Models

To configure and run a simulation using your existing compiled model, you need only VeriStand installed. You need the following additional software to perform other tasks with models:

  • To develop a model using MathWorks Simulink® software, you must be a licensed user and have MathWorks MATLAB® software (32-bit or 64-bit version) and MathWorks Simulink software installed on the host computer.
  • To compile a model developed using MathWorks Simulink software for use on a Microsoft Windows or LabVIEW real-time target, you must be a licensed user of and have the following software installed on the host computer: MathWorks Real-Time Workshop® (Simulink Coder®). Refer to the NI website for a list of compilers that are tested and supported.
  • The VeriStand Model Framework supports only certain versions of MathWorks Simulink software. If the VeriStand Model Framework is used with an unsupported version of MathWorks Simulink®, VeriStand cannot initialize it.

If you use other modeling environments, contact your model vendor for specific requirements.

LabVIEW

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.

.NET

The VeriStand .NET APIs require the following Microsoft software:

  • Microsoft .NET Framework 4.6.2, which uses Microsoft .NET Common Language Runtime (CLR) 4.6.2.
  • A .NET environment capable of interacting with .NET Framework 4.6.2-based assemblies, such as Microsoft Visual Studio 2015 or later.

Supported Operating Systems

VeriStand 2020 R6 supports the following operating systems:

Windows Systems Real-Time Targets
  • Windows 10 64-bit version 20H21
  • Windows Server 2016
  • Windows Server 2019
  • Phar Lap ETS2
  • NI Linux Real-Time

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  VeriStand will not install or run on an unsupported OS. You cannot deploy or distribute applications that use VeriStand 2020 R6 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.

Recommended PXI Linux RT System Image

When formatting a disk with a PXI Linux RT system image for VeriStand 2020 R6, select Linux RT System Image 21.0 and enable support for the LabVIEW 2020 programming environment. Doing so prevents driver version conflicts while deploying XNET to a real-time target.

Installation Instructions

Install VeriStand with either the online installer or with installation media.

  1. Log on as an administrator or as a user with administrator privileges.
  2. Disable automatic virus detection programs.
    Note   Some virus detection programs interfere with the installer.
  3. Activate VeriStand when prompted by the installer or activate later with NI License Manager.
  4. To use LabVIEW with VeriStand, install the like-numbered version of LabVIEW on the host computer.
  5. Check your computer for viruses and enable your virus detection.

Online Installer

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.

Installation Media

If you purchased this product with media, insert the VeriStand installation media and follow the instructions that appear on the screen.

Product Security and Critical Updates

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.

Upgrade and Compatibility Issues

The following sections describe issues to be aware of when you upgrade to VeriStand 2020 R6.

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 R6. To access the documents, refer to the VeriStand Release Notes.

Known Conflict with .NET 4.6.2 and MSVC 2010

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.

Uncompiled Models

VeriStand does not support communication with uncompiled models.

Models Created from LabVIEW VIs

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.

Models Compiled for Previous Versions

The VeriStand Model Framework contains changes to the files used 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 R6:

  • If you do not need to modify your model, continue to use the model as-is.
  • If you need to modify model functionality, and do not require the latest Model Framework version updates, recompile the model against the deprecated Model Framework files. These files are installed at <RootDrive>\VeriStand\version\ModelInterface\custom\src\obsolete.

Models with Tuneable Parameters

VeriStand Model Framework 2019 R3 to 2020 R4 does not support updates to tunable parameters if all the following are true:

  • The model uses tunable parameters.
  • The model uses model references to call subsystems.
  • The tunable parameter is not used or referenced in the top-level model.

NI recommends recompiling this type of model with Model Framework 2020 R6. Use the VeriStand suite installer to separately download the Model Framework. Models compiled with Model Framework 2020 R6 are compatible with VeriStand 2019 R3 to 2020 R6.

Migrating Files from VeriStand 2010 to 2018 SP1

VeriStand 2020 R6 can open projects from VeriStand 2010 to 2018 SP1 using the Open Legacy Project option in the Welcome tab.

VeriStand Custom Devices Not Included

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

Accessing the Help

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 R6 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 LabVIEW and NI TestStand. Windows Start menu: All Programs»National Instruments»VeriStand 2020 R6 .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. 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  Select VeriStand Model Framework when you run the VeriStand installer.

Note  If you install VeriStand with a compatible version of LabVIEW, you can access a subset of VeriStand related materials in the LabVIEW Help. This includes information about VeriStand VIs and extending VeriStand functionality. To access this help from LabVIEW, select Help»LabVIEW Help.

Finding Examples

VeriStand includes the following types of examples:

  • VeriStand Project—An example VeriStand project, including related items such as a system definition, a Workspace screen file, compiled models, and NI-XNET files, are located in the <Public Documents>\National Instruments\NI VeriStand\Projects\Example directory.
  • Stimulus Profile Editor—VeriStand Stimulus Profile Editor examples are located in the <Public Documents>\National Instruments\NI VeriStand\Examples directory.

    Note  On the Windows OS, the default location of the <Public Documents> directory is C:\Users\Public\Public Documents.

  • LabVIEW API—LabVIEW examples that use the VeriStand API are located in the <Program Files>\National Instruments\LabVIEW 2020\examples\NI Veristand directory.

Automating the Installation of NI Products

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:

Using NI Software with Microsoft Windows 10

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.


Legal Information

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:

  • Notices are located in the <National Instruments>\_Legal Information and <National Instruments> directories.
  • EULAs are located in the <National Instruments>\Shared\MDF\Legal\license directory.
  • Review <National Instruments>\_Legal Information.txt for information on including legal information in installers built with NI products.

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.

375380V-01