This file contains important information about VeriStand 2019, including system requirements and installation instructions.
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 and a test manager you can use to configure and implement triggered multi-file data logging, stimulus generation and playback, and real-time test sequencing.
Refer to the following list to learn what's new in VeriStand 2019.
You can now use the VeriStand Editor to control aspects of your project. The UI Manager and Project Explorer windows from previous releases of VeriStand have been combined into one editor. Many of the features of the Project Explorer window can now be accessed through Project Files in the Navigation pane of the VeriStand Editor. The VeriStand Editor also contains the Mapping Diagram to help visualize channel mappings.
Note You can access the interface from previous versions of VeriStand by launching the VeriStand Project Explorer from the
x86\NI\VeriStand 2019 directory.
You can now visualize software mappable points within a VeriStand project with the Mapping Diagram. This graphical diagram allows you to see all VeriStand channels and the mappings between them.
Groups of mappings between two nodes are automatically bundled into a single wire by default to reduce clutter. If a wire represents multiple mappings, you can select the bundle to see more information in the Configuration pane.
Other features of the Mapping Diagram include the ability to:
You can now deploy System Definition Files to PXI NI Linux RT targets similarly to previously supported targets. Benefits of supporting the NI Linux RTOS include:
VeriStand 2019 officially supports custom devices. The following table displays custom devices that are supported in VeriStand.
|Engine Simulation Toolkit||Provides a configuration-based experience for validating engine control units (ECUs).|
|Scan Engine and EtherCAT||Supports easily read scanned I/O from C series modules in a CompactRIO or NI 914x EtherCAT chassis. This custom device also supports custom FPGA personalities to be used with a 914x chassis.|
|SLSC 12201 DIO Module Custom||Integrates the SLSC-12201 33 V Digital I/O Conditioning Module into VeriStand.|
|SLSC EDS Custom Device||Allows any generic SLSC Capabilities file to be used in VeriStand.|
|Synchronization Custom Device||Synchronizes RT system time and PXI chassis clocks.|
These custom devices can be downloaded with VeriStand 2019 using NI Package Manager. Check NI GitHub for updates and other custom devices.
VeriStand 2019 supports XNET implementation for the Controller Area Network Flexible Data-Rate (CAN FD) protocol. With a XNET implementation, you can now use databases that support CAN FD and CAN FD with Baud Rate Switching I/O modes. This implementation also allows calculating and using custom baud rates for a CAN interface. For more information on CAN FD, see Understanding CAN with Flexible Data-Rate (CAN FD).
VeriStand now has limited support for the Functional Mockup Interface (FMI) API standard on Windows and PXI LinuxRT. Use the FMI standard to create tool agnostic, portable solutions between modeling and simulation environments. VeriStand enables the configuration and execution of FMI 2.0 CoSimulation models on host and National Instruments Real-Time Linux64 systems.
Note This support requires the Functional Mockup Units (FMUs) to have the proper executable binaries available.
VeriStand has the following requirements:
|Windows 64-bit Operating System||Real-Time Targets|
|RAM/Processor|| || |
|Required Software|| ||VeriStand software, which you can install from NI Measurement & Automation Explorer (MAX)|
| 1 You can achieve higher Primary Control Loop rates by using targets with higher-performance specifications. |
2 Using custom devices, such as the Scan Engine Custom Device, will require at least 512MB of RAM.
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 2019 or later. 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 Systems1||Real-Time Targets|
| || |
Note In 2016, VeriStand dropped support for Windows Vista, Windows XP, Windows Server 2003, and installations of Windows 7 without any service packs. VeriStand 2019 will not install or run on an unsupported OS. You cannot deploy or distribute applications that use VeriStand 2019 to an unsupported OS. Additionally, after installing VeriStand 2019, you cannot use any installers built on this computer with any version of LabVIEW, LabWindows™/CVI™, NI TestStand™, or Measurement Studio on an unsupported OS.
For more information about the changes to our OS support for 2019, refer to KB 79UC78LS, Why Does my LabVIEW, LabWindows/CVI, Measurement Studio, or TestStand Built Installer Fail on Windows XP/Vista and Server 2003?.
1 NI software installs VC2015 Runtime and .NET 4.6.2. Windows 8.1 and Windows Server 2012 R2 require Microsoft updates to support these items. Refer to Microsoft KB2919442 and KB2919355 for more information about how to install these updates.
2 NI software is signed with a SHA-256 certificate. Windows 7 SP1 requires Microsoft updates to support SHA-256. Refer to Microsoft KB3033929 for more information about how to install this security update.
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 NI Package Manager or installation media.
NI automates LabVIEW NXG installation using NI Package Manager. Visit ni.com/info and enter the Info Code NIPMDownload to download NI Package Manager. 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 an NI Software Suite or NI Product Bundle, use the installation media that shipped with your purchase to install this product. Insert the VeriStand installation media and follow the instructions that appear on the screen.
The following sections describe issues to be aware of when you upgrade to VeriStand 2019.
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 2019. To access the documents, refer to the NI website at ni.com/info and enter the Info Code for the appropriate VeriStand version from the following list:
VeriStand 2019 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 2019. 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 2019:
The mutation tool is not available in VeriStand 2019. All rig files and in4 files must be migrated using VeriStand 2014 or earlier.
VeriStand 2019 can open projects from VeriStand 2010 and later using the Open Legacy Project option in the Welcome tab.
In VeriStand 2015 and later, you cannot add new instances of the Lambda Genesys and Pickering custom devices. Systems that already contain these custom devices can continue to use them.
Refer to the NI website for details on how to access the source code for the Lambda Genesys and Pickering custom devices.
You can access the software and documentation known issues list online. Refer to the NI website for an up-to-date list of known issues in VeriStand 2019.
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 Windows and 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.
The following items are the IDs and titles of a subset of issues fixed in VeriStand 2019. This is not an exhaustive list of issues fixed in the current version of VeriStand. If you have a CAR ID, you can search this list to validate that the issue has been fixed.
|581461||Importing a large number of mappings with the Import Mappings window may cause a .NET exception and fail to import mappings.|
|583754||Running and stopping a Stimulus Profile via the LabVIEW API causes a memory leak.|
|590854||When UI Manager is used in a VeriStand project, both UI Manager and the Workspace are launched at execution time. There is currently no way to disable this.|
|635055||When displaying multiple channels on a Waveform Chart, the chart may update slowly and possibly lose data.||651257||When using the Model Parameter Manager or Channel Data Viewer with a large number of channels, UI Manager may hang.||669410||Opening the System Configuration Mappings window may cause Error 1172 and cause all mappings in the window to disappear.||695368||The VeriStand Engine may crash when a channel in a Real-Time Sequence is faulted.||703244||Model Parameter Manager shows incorrect initial values for all models except the first model loaded in VeriStand.||703397||Parameters from LabVIEW clusters do not update when mapped to a UI Manger control.||704556||When a target is disabled in the System Definition, UI Manager charts may not update with new data.||712390||UI Manager does not automatically connect to deployed VeriStand projects.||717348||Initial model parameter values loaded from a file are only applied to the first model loaded in VeriStand.||717983||The Model Parameter Manager in UI Manager cannot update parameter arrays.||725381||Using several Waveform Charts in the same UI Manager Project may cause a memory leak.||726690||The Scan Engine EtherCAT Add-On Scan Interface encoder measurement does not change the timebase when selected.||728415||CPU Usage may increase when UI Manager is not the software in focus.||729116||A UI Manager Waveform Chart may not display data when mapped to a waveform task.||731368||Models do not compile when data types are shared between reference models from The MathWorks, Inc. Simulink© software.||735599||When using a custom device, values set from the UI Manager may be registered twice.||737393||The VeriStand Engine will crash when running models compiled from the The MathWorks, Inc. Simulink R2017b software or later.|
VeriStand includes the following documentation resources:
|VeriStand Help||Conceptual, how-to, and reference information for using VeriStand.||In software: Help»Show VeriStand Help... |
Windows Start menu: All Programs»National Instruments»VeriStand 2019 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 2019 .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:
Tip On Windows 7, 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.
When you install NI software on Microsoft Windows 8.1, you will notice a few additional tiles in the Apps view, including shortcuts to NI application software products such as NI LabVIEW, Measurement & Automation Explorer (NI MAX), and NI Launcher. For more information about NI support for Windows 8.1, visit ni.com/windows8.
© 2009–2019 National Instruments. 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.
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.
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.