NI VeriStand 2015 SP1 Readme

April 2016

This file contains important information about NI VeriStand 2015 SP1, including system requirements and installation instructions.


System Requirements

Installation Instructions

Evaluating NI DIAdem

New Features

Upgrade and Compatibility Issues

Accessing the Help

Finding Examples

Known Issues

Bug Fixes

Automating the Installation of NI Products

How to Use NI Software with Microsoft Windows 8

Important Information


NI 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 easily customized and extended with LabVIEW, NI TestStand, and other software tools.

VeriStand includes a run-time editable user interface as well as a test manager you can use to configure and implement triggered multi-file data logging, real-time test sequencing, stimulus generation and playback, and model calibration.

System Requirements

The following sections describe support considerations for using VeriStand in various types of systems.

Windows Systems1Real-Time Targets
Operating System
  • Windows 10/8.1/7/Vista (32-bit and 64-bit)
  • Windows XP Service Pack 3 (32-bit)
  • Windows Server 2008 R2 (64-bit)
  • Windows Server 2003 R2 (32-bit)
  • Phar Lap ETS
  • VxWorks
  • NI Linux Real-Time
  • 2 GB of RAM
  • Multi-core processor
  • PXI controller/desktop PC—At least 256 MB of RAM2
  • CompactRIO/Single-Board RIO—At least 128 MB of RAM2
Required Software
  • (Required) NI-DAQmx software 15.0
  • (Required) NI-VISA software 15.0 or later
  • (Recommended) NI-RIO 15.0 or later driver software, used by NI FPGA targets
  • (Recommended) NI-XNET 15.0 or later driver software, used by NI-XNET vehicle bus interface cards
VeriStand software, which you can install from NI Measurement & Automation Explorer (MAX)
1 The following considerations apply to using VeriStand on Windows:
  • VeriStand runs as a 32-bit application on all operating systems.
  • VeriStand does not support Windows 2000/NT/Me/98/95, Windows XP x64, Windows XP Service Pack 1 and 2, or the Windows Server non-R2 editions.
  • Support for Windows Server 2003 R2 may require disabling physical address extensions (PAE). To learn how this might affect your use of Windows Server 2003 and what actions you might have to take, visit and enter the info code PAESupport.

2 You can achieve higher Primary Control Loop rates by using targets with higher-performance specifications.

Note  The following sections describe system requirements that apply if you use models, LabVIEW functionality, and .NET APIs in your system.

Simulation Models

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:

  • To develop a model using The MathWorks, Inc. Simulink® application software, you must be a licensed user of and have the following software installed on the host computer: The MathWorks, Inc. MATLAB® software (32-bit or 64-bit version) and The MathWorks, Inc. Simulink software.
  • To compile a model developed using The MathWorks, Inc. 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: The MathWorks, Inc. Real-Time Workshop® (Simulink Coder®). Visit and enter the Info Code exxymi for a list of compilers that are tested and supported.
  • The VeriStand Model Framework supports only certain versions of The MathWorks, Inc. Simulink® software. If the VeriStand Model Framework is used with an unsupported version of The MathWorks, Inc. Simulink®, VeriStand cannot initialize it.

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 2015 or later. The LabVIEW functionality in VeriStand always requires like-numbered versions.


The VeriStand .NET APIs require the following Microsoft software:

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

Installation Instructions

Complete the following steps to install VeriStand.

Note  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.

  1. Log on as an administrator or as a user with administrator privileges.
  2. Some virus detection programs interfere with the installer. Disable any automatic virus detection programs before you install. After installation, check your computer for viruses and enable any virus detection programs you disabled.
  3. (Optional) To use LabVIEW with VeriStand, install the like-numbered version of LabVIEW on the host computer.
  4. Insert the VeriStand installation media and follow the instructions that appear on the screen.
  5. Install the NI-DAQmx driver software from the NI Device Drivers DVD or any NI-DAQmx driver DVD.

    Note  The NI-DAQmx driver software is required to deploy a system definition to any platform, including the localhost running Windows.
  6. (Optional) If using NI-XNET, insert the NI-XNET installation media and follow the instructions that appear on the screen.
  7. (Optional) Activate VeriStand when prompted by the installer, or activate at a later time using the NI License Manager.

Evaluating NI DIAdem

The VeriStand 2015 SP1 media kit includes an evaluation version of NI DIAdem. NI DIAdem is a software tool you can use to locate, load, visualize, analyze, and report measurement data from real-time tests. You can use VeriStand with DIAdem to automate the post-processing of data collected in VeriStand, view trend data across multiple files and file types, and generate custom reports.

New Features

For a list of new features in VeriStand 2015 SP1, refer to the following topic in the NI VeriStand 2015 SP1 Help posted on or installed on disk: What's New in NI VeriStand 2015 SP1.

Upgrade and Compatibility Issues

The following sections describe issues to be aware of when you upgrade to VeriStand 2015 SP1.

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 2015 SP1. To access the documents, refer to the NI website at and enter the Info Code for the appropriate VeriStand version from the following list:

Uncompiled Models

VeriStand 2015 SP1 does not support communication with uncompiled models.

Models Created from LabVIEW VIs

Models compiled from LabVIEW VIs (.lvmodel files) using LabVIEW 2014 or earlier must be recompiled using LabVIEW 2015. The LabVIEW functionality in VeriStand always requires like-numbered versions.

Models Compiled for Previous 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 for to continue to use the models in VeriStand 2015 SP1:

  • If you do not need to update your model or deploy it to Intel x64-based Linux targets that run NI Linux Real-Time, you can continue to use the model as-is.
  • If you need to update functionality of your model that does not require the changes in the latest version of the Model Framework, you can recompile the model against the deprecated Model Framework files. These files are installed at RootDrive:\VeriStand\version\ModelInterface\custom\src\obsolete. However, you cannot deploy the recompiled model to Intel x64-based targets that run NI Linux Real-Time.
  • To take advantage of the new features in the latest version of the Model Framework, or if you need to deploy the model to Intel x64-based targets that run NI Linux Real-Time, update and recompile the models using the 2015 version of the Model Framework. Update your models according to the following differences between new files in the Model Framework and the deprecated files they replace:
    • ni_modelframework.h contains the following differences from NIVERISTAND_API.h:
      • Implements fixed-width data types from the C99 standard, such as replacing int with int32_t where applicable.
      • Replaces use of the long data type with int32_t or uint32_t where applicable to achieve cross-platform compatibility.
    • ni_modelframework.c contains the following differences from codegen.c:
      • This file is installed on disk at <custom>\src\ni_modelframework.c rather than in the <custom> directory.
      • USER_TakeOneStep() returns an int32_t value rather than void. If the function completes successfully, it returns NI_OK. If an error occurs, this function returns NI_ERROR.
      • The USER_ModelName global variable is a const char and replaces the ModelName variable.
      • The USER_Builder global variable is a const char and replaces the build variable.
      • The USER_BaseRate global variable is a const char and replaces the baserate variable.

New Location for VeriStand Model Framework Examples

The example models included with the Model Framework are located at RootDrive:\VeriStand\version\ModelInterface\custom\examples.

Migrating Files from VeriStand 2009 and Earlier

The mutation tool is not available in VeriStand 2015 SP1. All rig files and in4 files must be migrated using VeriStand 2014 or earlier.

Select Built-In Custom Devices Not Included

In VeriStand 2015 SP1, 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.

Visit and enter the Info Code exjpt3 to access a page that details how to access the source code for the Lambda Genesys and Pickering custom devices.

VeriStand Updates and Notifications

National Instruments posts information about critical updates and security notifications on Visit and enter the Info Code updates to access this information.

Accessing the Help

VeriStand includes the following documentation resources:

Resource Contents Access Instructions
NI Veristand Help Conceptual, how-to, and reference information for using VeriStand. In software: Help»Search the NI VeriStand Help


Windows Start menu: All Programs»National Instruments»NI VeriStand»VeriStand Help
NI 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»NI VeriStand»VeriStand .NET API Help.
NI 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 NI 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 NI VeriStand Help, including information about the VeriStand VIs and extending VeriStand functionality with LabVIEW, from the LabVIEW Help. From LabVIEW, select Help»LabVIEW Help.

Finding Examples

VeriStand includes several types of examples:

  • NI 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.

    Tip  On Windows 7/Vista, 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 2015\examples\NI Veristand directory.

Known Issues

You can access the software and documentation known issues list online. Visit and enter the Info Codes NIVeriStand2015SP1KI and NIVeriStand2015KI for an up-to-date list of known issues in VeriStand 2015 and VeriStand 2015 SP1.

Known Conflict with .NET 4.5 and MSVC 2010

To run the NI VeriStand UI Manager, the .NET Framework 4.5 must be installed. However, installing the .NET Framework 4.5 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.

Bug Fixes

The following items are the IDs and titles of a subset of issues fixed in VeriStand 2015 SP1. 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 the issue has been fixed.

ID Fixed Issue
574824 Passing the Model Interface Toolkit's Unload an empty model constant breaks other MIT sessions.
573162 VeriStand 2015 systems using DAQ devices exhibited lower maximum PCL rates due to a CPU assignment bug
572529 Refreshing modified models in a system definition does not correctly update the model's inports and outports
571818 The Primary Control Loop only runs on CPU 0, regardless of manual assignment
571779 Users are not notified when alarms are triggered due to a channel initializing outside of an alarm's range
571468 The VeriStand engine can error after deployment due to setting the NumOfWarmUpIters DAQmx RT property for uneligible DAQ tasks
567397 The last signal value for a decimated model does not update at run time
562245 Exceptionally large XNET databases fail to deploy unless their corresponding frames are run inline with the PCL
553945 VeriStand projects with DAQ devices in Slow Background Conversion mode can fail to deploy

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. However, starting with the August 2012 releases (products using NI Installers version 3.1 or later), you may need to perform additional steps before or during a silent installation of NI software.

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, 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

Using NI Software with Microsoft Windows 8.1

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 VeriStand Drops Support for Microsoft Windows 7 RTM, Windows Vista, Windows XP, and Windows Server 2003 in 2016

NI VeriStand will drop support for Microsoft Windows 7 RTM (with no service pack), Windows Vista, Windows XP, and Windows Server 2003 as of July 1, 2016. Versions of NI VeriStand that ship after July 1, 2016 will not install or run on Windows 7 RTM (with no service pack), Windows Vista, Windows XP, or Windows Server 2003. For detailed information about NI application software product life cycles, visit and enter one of the following Info Codes:

Product Info Code
Measurement Studiomstudiolifecycle

Legal Information


© 2009-2016 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:

  • 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.


Refer to the NI Trademarks and Logo Guidelines at 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 National Instruments Patent Notice at