NI VeriStand 2013 SP1 Readme

March 2013

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


System Requirements

Installation Instructions

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


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

NI 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 NI VeriStand in various types of systems.

Windows Systems1Real-Time Targets
Operating System
  • Windows 8.1/8/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
  • 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 9.7.5 or later driver software
  • (Required) NI-VISA software 5.4.0 or later
  • (Recommended) NI-RIO 13.0 or later driver software, used by NI FPGA targets
  • (Recommended) NI-XNET 1.8.0 or later driver software, used by NI-XNET vehicle bus interface cards
NI VeriStand software (install from MAX)
1 The following considerations apply to using NI VeriStand on Windows:
  • NI VeriStand runs as a 32-bit application on all operating systems.
  • NI 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 NI 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 versions) and The MathWorks, Inc. Simulink software.

    Note  NI VeriStand supports the 64-bit versions of the MATLAB or Simulink software starting in R2010b and continuing in the versions listed in the NI KnowledgeBase document titled NI VeriStand Version Compatibility on
  • 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®).
  • For deploying a compiled model to a LabVIEW real-time target, refer to the NI KnowledgeBase document titled NI VeriStand Version Compatibility on for a list of compilers that are tested and supported.

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


The NI 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 2013.

Installation Instructions

Complete the following steps to install NI 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 NI VeriStand, install the like-numbered version of LabVIEW on the host computer.
  4. Insert the NI 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 NI VeriStand when prompted by the installer, or activate at a later time using the NI License Manager.

New Features

NI VeriStand 2013 SP1 contains the following new features.

Microsoft Visual C++ 2010 Support

NI VeriStand 2013 SP1 supports compiling models with the Microsoft Visual C++ 10.0 compiler. You can now use Microsoft Visual Studio 2010 C++ Express, Microsoft Visual Studio 2010 Professional or Microsoft Windows SDK for Windows 7 and .NET Framework 4 to compile The MathWorks, Inc. Simulink® and other models.

Upgrade and Compatibility Issues

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

Note  National Instruments recommends that you also review the Upgrade and Compatibility Issues in the readme files for each NI VeriStand version between the version from which you are upgrading and NI VeriStand 2013 SP1. To access the documents, refer to the National Instruments website at and enter the Info Code for the appropriate NI VeriStand version from the following list:

Models Created from LabVIEW VIs

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

NI VeriStand Updates and Notifications

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

Accessing the Help

NI VeriStand includes the following documentation resources:

Resource Contents Access Instructions
NI VeriStand Help Conceptual, how-to, and reference information for using NI 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 NI 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 NI VeriStand Model Framework to compile your existing C and C++ model code so you can load your models in NI 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 NI VeriStand version number.

Note  You must explicitly select NI VeriStand Model Framework when you run the NI VeriStand installer.

Note  If you install NI VeriStand with the compatible version of LabVIEW, you also can access a subset of the NI VeriStand Help, including information about the NI VeriStand VIs and extending NI VeriStand functionality with LabVIEW, from the LabVIEW Help. From the pull-down menu in LabVIEW, select Help»LabVIEW Help.

Finding Examples

NI VeriStand includes several types of examples:

  • NI VeriStand Project—An example NI 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—NI 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 NI VeriStand API are located in the <Program Files>\National Instruments\LabVIEW 2013\examples\NI Veristand directory.

Known Issues

You can access the software and documentation known issues list online. Refer to the National Instruments website for an up-to-date list of known issues in NI VeriStand 2013 and NI VeriStand 2013 SP1.

Bug Fixes

The following items are the IDs and titles of a subset of issues fixed in NI VeriStand 2013 SP1. This is not an exhaustive list of issues fixed in the current version of NI VeriStand. If you have a CAR ID, you can search this list to validate the issue has been fixed.

ID Fixed Issue


CAN data replay does not work if the trigger channel is not specified
430662 Embedded Data Logger cannot log alias channels
432828 When importing a list of ten thousand mappings, the progress bar goes backwards
433777 Loading an NI-XNET database of unsupported format freezes NI VeriStand 2013
444555 Hardware Discovery Wizard cannot find DAQ cards in target systems with DAQmx 9.8 and NI System Configuration 5.5.1
445193 Reloading a .txt file saved by Model Parameter Manager results in an issue with arrays
448469 Stimulus profiles produce an invalid ATML file if Stop Logging step does not produce log files
449833 NI VeriStand does not save changes to the numerical format of workspace controls
450159 NI VeriStand System Definition API does not have functionality for disabling XNET ports
425731 Multi-rate model tasks do not update correctly at high loop rates.
431001 Loading an XNET Database with an unsupported format causes NI VeriStand to freeze.
431038 Hardware Discovery Wizard does not detect all DAQ devices.
403405 Multi-rate models do not work if there is a timing offset.
432660 NI VeriStand 2013 does not properly recognize the Visual Studio 2008 compiler as a supported compiler.
433428 NI VeriStand is unable to set some FPGA boards as master timing sources.
433157 NI VeriStand 2013 incorrectly returns Error 1026 at Call By Reference when calling Get Item Property in a Custom Device.
434519 NI VeriStand improperly sets the Chassis parameter Export start trigger on line to None.
432134 Error -307702 thrown incorrectly when importing model into NI VeriStand.

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:

How to Use NI Software with Microsoft Windows 8

When you install National Instruments software on Microsoft Windows 8, you will notice a few additional tiles on the Start screen, including shortcuts to NI application software products such as NI LabVIEW, Measurement & Automation Explorer (MAX), and the new NI Launcher.

Using NI Launcher

NI Launcher helps you find and launch installed NI products. It provides you with a method of finding NI products similar to the Start menu in previous versions of Microsoft Windows. To use NI Launcher, click the NI Launcher tile on the Start screen. NI Launcher launches the desktop and opens a menu containing a list of NI products. Click any NI product to launch it.

Note  NI MAX does not appear as a desktop shortcut when installed on Microsoft Windows 8. You can launch MAX either from the Start screen or from within NI Launcher.

Pinning Frequently Used Applications

For convenience, you can pin your most-used NI applications, such as MAX, to either the Start screen or the Taskbar on the desktop, as necessary:

Current ApplicationIcon LocationPin to Action
Windows 8 DesktopDesktop TaskbarRight-click application and select Pin to Taskbar
Windows 8 Desktop Start screenRight-click application and select Pin to Start
Windows 8 Start screenDesktop TaskbarRight-click application and select Pin to taskbar from the menu bar on the bottom of the screen

Finding All Programs

If you want to find a particular application or related files, such as documentation files, from the Start screen, you can access all installed files by right-clicking anywhere on the Start screen and selecting All apps. A list of all installed software and related files appears, in alphabetical order by creator or type.

For more information about NI support for Windows 8, visit

NI VeriStand Drops Support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 in 2016

National Instruments NI VeriStand will drop support for Microsoft 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 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
NI LabVIEWlifecycle
NI LabWindows™/CVI™cvi_lifecycle
NI Measurement Studiomstudiolifecycle
NI TestStandtslcp
NI DIAdemddlcp
NI SignalExpressselcp
NI VeriStandnivslifecycle

Important Information


© 2009-2014 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.

National Instruments 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.


Refer to the NI Trademarks and Logo Guidelines at for information on National Instruments trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.


For patents covering the National Instruments 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