Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活，以下链接可下载：
NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本
http://pcmv.cn/thread-490-1-1.html
视觉论坛的各种资源，除了视觉相关的模块有使用外，大部分的都不会使用，所以仅提供资源不能提供技术支持。资源的下载地址一般会同时提供NI官方地址和百度网盘的下载地址。某些工具包NI的地址失效或没有NI的下载地址，那视觉论坛也没有办法，只能尝试使用百度网盘地址下载；如果百度网盘的下载地址失效过期，可联系论坛客服更新。现在NI的下载服务器对我国IP地址不是很友好，有些时候速度很慢或大的资源下载很容易出错，这样会造成安装过程各种类型报错而无法安装。建议在下载完成后，对下载资源做校验和验证（NI一般会提供MD5或SHA256等），与官方或视觉论坛提供的校验和对比，一致就可以安装，如果不一致，则需要重新下载。视觉论坛早期下载的资源，那时候NI没有这么多限制，基本上都是正常下载的资源；后期下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘，所以百度网盘的资源基本上是正确的。校验和工具下载地址：
文件Hash计算器FHash,文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算
http://pcmv.cn/thread-26524-1-1.html
NI VeriStand 2012 Win32Eng PC版完整版及运行版NIVS2012
VeriStand是一款用于激励生成、数据采集和计算通道等实时测试应用且具有自定义通道换算功能的软件。
VeriStand应用软件可帮助您为NI实时硬件配置I/O通道、数据记录、激励生成和主机通信。您还可以导入仿真模型和控制算法，通过可配置的警报来响应事件，并通过宏录制、TestStand、.NET和其他软件实现测试自动化。您可以使用运行时可编辑的用户界面，监测应用程序数据、警报状态和系统执行指标，并进行交互。虽然使用VeriStand不需要掌握编程知识，但您也可以使用各种编程软件环境（如LabVIEW、ANSI C/C ++、Python和ASAM XIL）来为VeriStand添加自定义功能。
VeriStand2018SP1及以前的早期版本，为32位版本。VeriStand2019及以后更新版本，为64位版本。但是同一年代并不能同时具有32/64位版本。
百度网盘下载地址（限速，请开会员或使用破解限速工具）：
链接: 请注册视觉论坛用户，登陆后购买附件下载查看，充值请联系在线客服 提取码: 请注册登陆视觉论坛会员，购买附件查看
NI官方下载地址（可能无效或无法下载完成）：
请注册登陆视觉论坛会员，购买附件查看
NI VeriStand 2012 Win32Eng PC版完整版及运行版NIVS2012
http://pcmv.cn/thread-24459-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
NI VeriStand 2012 Readme
March 2013
This file contains important information about NI VeriStand 2012, including system requirements and installation instructions.
Overview
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
Overview
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 Systems1 | Real-Time Targets |
| Operating System | Windows 8 (32-bit and 64-bit) Windows 7 (32-bit and 64-bit) Windows Vista (32-bit and 64-bit) Windows XP Service Pack 3 (32-bit) Windows Server 2003 R2 (32-bit) Windows Server 2008 R2 (64-bit)
| |
| RAM/Processor | 2 GB of RAM Multi-core processor
| |
| Required Software | (Required) NI-DAQmx driver software (Required) NI-VISA software (Recommended) NI-RIO driver software, used by NI FPGA targets (Recommended) NI-XNET 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 ni.com/info 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 only the 64-bit versions of the MATLAB or Simulink software starting in R2010b and continuing in the versions listed in the KnowledgeBase on ni.com.
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 KnowledgeBase on ni.com 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.
LabVIEW
To create custom devices, menu items, workspace controls and indicators, or timing and sync devices, you must have LabVIEW 2012 or 2012 SP1 installed. The LabVIEW functionality in NI VeriStand always requires like-numbered versions.
.NET
The NI VeriStand .NET APIs require the following Microsoft software:
Microsoft .NET Framework 3.5 SP1, which uses Microsoft .NET Common Language Runtime (CLR) 2.0.
A .NET environment capable of interacting with .NET Framework 3.5 based assemblies, such as Microsoft Visual Studio 2008 SP1 or LabVIEW 2012.
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.
Log on as an administrator or as a user with administrator privileges.
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.
(Optional) To use LabVIEW with NI VeriStand, install the like-numbered version of LabVIEW on the host computer.
Insert the NI VeriStand installation media and follow the instructions that appear on the screen.
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.
(Optional) If using NI-XNET, insert the NI-XNET installation media and follow the instructions that appear on the screen.
(Optional) Activate NI VeriStand when prompted by the installer, or activate at a later time using the NI License Manager.
New Features
For a list of new features in NI VeriStand 2012, refer to the following topic in the NI VeriStand 2012 Help posted on ni.com or installed on disk: What's New in NI VeriStand 2012.
Upgrade and Compatibility Issues
The following sections describe issues to be aware of when you upgrade to NI VeriStand 2012.
Models Created from LabVIEW VIs
Models compiled from LabVIEW VIs (.lvmodel files) using LabVIEW 2011 SP1 or earlier must be recompiled using LabVIEW 2012. The LabVIEW functionality in NI VeriStand always requires like-numbered versions.
Models Created with the NI VeriStand Model Framework
In NI VeriStand 2012, if you recompile a model created with the NI VeriStand Model Framework from NI VeriStand 2011 SP1 or earlier and the model contains a signal(s) with a / character in its name, mappings to the signal(s) might be broken when you reload the model in a system definition file. You must correct the broken mappings before you can deploy and run the system definition file.
PXI_Trig0 Configuration
NI VeriStand 2012 automatically routes and reserves PXI_Trig0 lines on the backplanes of PXI chassis that contain a DAQ or FPGA chassis master hardware synchronization device. When you upgrade, complete the following steps to clear any existing manual routes or reservations of PXI_Trig0:
Open Measurement & Automation Explorer (MAX) and select the chassis.
On the Triggers pane for the chassis, clear any reservation for PXI_Trig0 on the appropriate bus and set routing for PXI_Trig0 to Dynamic.
Note If you use a Timing & Sync custom device as your chassis master hardware synchronization device, you do not need to reconfigure any settings.
You also can minimize the delay that multiplexing causes by selecting Maximum in the Conversion Rate drop-down menu on the System Explorer configuration page for the DAQ device. Note that using the maximum possible Convert Clock rate reduces the accuracy of measurements.
Updates and Notifications
National Instruments releases critical software updates after product release using the NI Update Service. Visit ni.com/info and enter updates to view a list of all currently available updates.
National Instruments provides notification of certain critical issues at install time. Visit ni.com/info and enter notifications to view a list of current product notifications.
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
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 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. |
| Using the NI VeriStand Model Framework | 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 xxxModelInterfacecustom directory, where xxx is the directory you specified when you installed the NI VeriStand Model Framework.
Note You must explicitly select NI VeriStand Model Framework when you run the NI VeriStand installer. By default, it does not install. |
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 InstrumentsNI VeriStandProjectsExample directory.
Stimulus Profile Editor—NI VeriStand Stimulus Profile Editor examples are located in the <;Public Documents>National InstrumentsNI VeriStandExamples directory.
Tip On Windows 7/Vista, the default location of the <;Public Documents> directory is C:UsersPublicPublic Documents.
LabVIEW API—LabVIEW examples that use the NI VeriStand API are located in the <;Program Files>National InstrumentsLabVIEW 2012examplesNI 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 2012.
Bug Fixes
The following items are the IDs and titles of a subset of issues fixed in NI VeriStand 2012. 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 |
| 189658 | MAX custom scales cannot be used in NI VeriStand |
| 197250 | Model Count system channel does not tell you which model is late |
| 289947 | VeriStand does not reserve RTSI0 in FPGA timing mode to prevent others from using it |
| 311161 | .NET Model API incorrectly creates the .NET tree structure if the named signal has forward slashes |
| 316421 | A system using a SMIO X Series board will hang when during undeployment |
| 318323 | Opening a VI with a .NET indicator or control in a newer version of LabVIEW picks the old assembly from GAC |
| 318644 | Cannot choose from more than 16 ports for NI-XNET devices |
| 326902 | CJC readings from SCXI thermocouples are incorrect with multiple SCXI modules |
| 331299 | NI VeriStand transmits triggered XNET frames on deployment despite the lack of a trigger |
| 337662 | Decimated host-side logs can have phase change if list of channels being streamed changes |
| 338321 | The fault function in a real-time sequence doesn't completely fault the channel |
| 338837 | TDMS logs have nonstandard and inconsistent unit definitions |
| 343926 | NI VeriStand does not set up PXI_Trig0 routing for multiple PXI bus segments |
| 351622 | FPGA and DAQ devices don't slave to RTSI 0 when timing and sync device is specified as master timing device |
| 353025 | Changing the XNET database for one port deletes frames on all ports that reference the same database |
| 357744 | Workspace stops updating if one target throws an error |
| 360883 | NI VeriStand experiences significant delay when loading under a network connection without Internet access |
| 361329 | Embedded Data Logger: Operation 1 (close & open new file) doesn't flush buffer correctly |
| 363424 | Excluded/included frames do not save for Data Replay files |
| 364013 | Running .csv file as real-time sequence in NI VeriStand stimulus profile causes memory leak |
| 368357 | NI VeriStand Model Framework fails to register with MATLAB R2010a software and later |
| 381942 | Units in TDMS log files of alias channels are not set correctly |
| 371918 | XNET automatic frame processing does not allow single bit offsets |
| 372900 | CSV playback does not load files as read-only |
| 373564 | Stimulus Profile Editor ribbon drop-down menu does not contain icons |
| 373610 | Clicking white space in the channel browse dialog in Stimulus Profile Editor closes the dialog |
| 373807 | Creating DAQ analog input output channels in specific order causes deployment hang |
| 373896 | Streaming more than 1021 channels to the Stimulus Profile Editor results in bad data |
| 379042 | Information channels added to XNET frame can cause frame data to be incorrect |
| 381942 | Units in TDMS log files for alias channels are not set correctly |
| 382674 | NI VeriStand can hang when undeploying from Project Explorer |
| 384169 | Data logging does not report if data was lost |
| 385802 | CAN data replay feature replays excluded frames |
| 386870 | TDMS logs created by Embedded Data Logger have nonstandard and inconsistent unit definitions |
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:
For more information on silent installations of individual NI products, refer to KB 4CJDP38M, Automating the Installation of a Single Installer.
For more information on silent installations of suited NI products, such as NI Developer Suite, refer to KB 4GGGDQH0, Automating the Installation of a Suited Installer.
To determine what version of NI Installers your product contains, refer to KB 4CJDR18M, How Can I Determine the Type and Version of My National Instruments Installer?.
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 and Measurement & Automation Explorer (MAX).
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 Application | Icon Location | Pin to Action |
| Windows 8 Desktop | Desktop Taskbar | Right-click application and select Pin to Taskbar |
| Windows 8 Desktop | Start screen | Right-click application and select Pin to Start |
| Windows 8 Start screen | Desktop Taskbar | Right-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.com/windows8.
Important Information
Copyright
© 2009-2013 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>SharedMDFLegallicense directory.
Review <National Instruments>_Legal Information.txt for information on including legal information in installers built with NI products.
Trademarks
Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on National Instruments trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.
Patents
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 ni.com/patents.
