August 2015
This file contains important information about NI VeriStand 2015, including system requirements and installation instructions.
Upgrade and Compatibility Issues
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 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.
The following sections describe support considerations for using VeriStand in various types of systems.
Windows Systems1 | Real-Time Targets | |
---|---|---|
Operating System |
|
|
RAM/Processor |
|
|
Required Software |
| VeriStand software (install from NI Measurement & Automation Explorer (MAX)) |
1 The following considerations apply to using VeriStand on Windows:
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.
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 2015. The LabVIEW functionality in VeriStand always requires like-numbered versions.
The VeriStand .NET APIs require the following Microsoft software:
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.
The VeriStand 2015 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.
For a list of new features in VeriStand 2015, refer to the following topic in the NI VeriStand 2015 Help posted on ni.com or installed on disk: What's New in NI VeriStand 2015.
The following sections describe issues to be aware of when you upgrade to VeriStand 2015.
Note National Instruments 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. To access the documents, refer to the National Instruments website at ni.com/info and enter the Info Code for the appropriate VeriStand version from the following list:
VeriStand 2015 does not support communication with uncompiled models.
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.
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 continuing to use the models in VeriStand 2015:
The example models included with the Model Framework are located at RootDrive:\VeriStand\version\ModelInterface\custom\examples.
The mutation tool is not available in VeriStand 2015. All rig files and in4 files must be migrated using a previous version of VeriStand.
In VeriStand 2015, 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 ni.com/info and enter Info Code exjpt3 to access a page that details how to access the source code for the Lambda Genesys and Pickering custom devices.
National Instruments posts information about critical updates and security notifications on ni.com
. Visit ni.com/info
and enter Info Code updates to access this information.
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 OR 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 the pull-down menu in LabVIEW, select Help»LabVIEW Help.
VeriStand includes several types of examples:
Tip On Windows 7/Vista, the default location of the <Public Documents> directory is C:\Users\Public\Public Documents.
You can access the software and documentation known issues list online. Visit ni.com/info and enter the Info Code NIVeriStand2015KI for an up-to-date list of known issues in VeriStand 2015.
The following items are the IDs and titles of a subset of issues fixed in VeriStand 2015. 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 |
---|---|
519509 | Compilation of a The MathWorks, Inc. Simulink® model with Data Store Memory fails for NI Linux Real-Time targets |
514054 | Referencing the same system definition channel with variables of different data types in a real-time sequence can cause unexpected behavior |
514005 | DIO lines created with the System Definition API's DAQDevice constructor are assigned incorrect physical addresses |
513819 | VeriStand does not set the Convert Late Errors To Warnings DAQmx and only Warmup Iterations for the DAQ timing master's AI tasks |
507923 | Compilation of The MathWorks, Inc. Simulink® model fails when using alias or fixed-point types in bus objects |
505010 | Default values are hidden for large array variables in real-time sequences |
498982 | VeriStand becomes unresponsive when loading Fibex files with "Reverse Incoming/Outgoing frames from database" set to TRUE |
495142 | Real-time sequence return values are limited to the 32-bit int data type |
490670 | FPGA initialization prevents the correct loading of XNET ports, resulting in Error -307719 |
486719 | Compilation of The MathWorks, Inc. Simulink® model fails when a referenced model uses tunable parameters |
481334 | Refreshing a model changes the default values back to zero |
481040 | Custom device tree operations within action VI on load fail with Error 1088 |
463995 | A disabled CAN frame will send zero values when CRC is present in that frame |
460515 | Expanding and contracting collapsible groups in real-time sequences can change the order of operations of the sequence |
456532 | Resetting a target with the System Command Channel stops the VeriStand Workspace from updating |
414593 | Adding sections to a custom device can throw Error 1088 |
408283 | An XNET Database cannot be refreshed using the System Definition API |
403806 | The System Definition API CreateMode method only creates one mode for a given multiplexer value |
403316 | The System Definition API creates unnecessary properties when adding XNET frames |
373810 | If a master DAQ device has both AI and AO out channels, disabling HWTSP for either AI or AO causes the device to lose its master timing status |
361241 | The System Definition API does not expose the model execution group property |
345604 | Adding frames to a disabled CAN port throws Error -307662 |
339518 | XNET Device Driver fails to deploy after formatting controller |
329546 | If DAQmx driver is installed on target after VeriStand, Error -88717 may occur on reboot |
319988 | XNET Database Editor throws error if there is a " . " in the name of the .dbc file |
309168 | Double-clicking a stimulus file on disk with an editor already open opens a brand new editor window |
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:
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.
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 in the Apps view. 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.x. You can launch NI MAX either from the Apps view or from within NI Launcher. |
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 Application | Icon Location | Pin to Action |
---|---|---|
Windows 8.x Desktop | Desktop Taskbar | Right-click application and select Pin to Taskbar |
Windows 8.x Desktop | Start screen | Right-click application and select Pin to Start |
Windows 8.x Start screen | Desktop Taskbar | Right-click application and select Pin to taskbar from the menu bar on the bottom of the screen |
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.com/windows8.
National Instruments VeriStand will drop support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 as of July 1, 2016. Versions of 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 ni.com/info and enter one of the following Info Codes:
Product | Info Code |
---|---|
LabVIEW | lifecycle |
LabWindows™/CVI™ | cvi_lifecycle |
Measurement Studio | mstudiolifecycle |
TestStand | tslcp |
DIAdem | ddlcp |
SignalExpress | selcp |
VeriStand | nivslifecycle |
Copyright
© 2009-2015 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.
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 National Instruments Patent Notice at ni.com/patents.
375380A-01