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 2015 Evaluation Win32Eng PC版完整版及运行版NIVS2015评估版包含驱动5.69GB
NI VeriStand 2015 Evaluation和标准版的NI VeriStand 2015比较,多了如DAQ、VISA等驱动程序。因此体积也大了不少。请根据实际情况考虑是不是需要带驱动版的,如不需要,则下载标准版的即可。
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 2015 Evaluation Win32Eng PC版完整版及运行版NIVS2015评估版包含驱动5.69GB
http://pcmv.cn/thread-24500-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
NI VeriStand 2015 Readme
Overview
System Requirements
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. |
Simulation Models
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.
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 ni.com/info and enter the Info Code exxymi for a list of compilers that are tested and supported.
The VeriStand Model Framework only supports 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.
LabVIEW
.NET
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 2014.
Installation Instructions
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 VeriStand, install the like-numbered version of LabVIEW on the host computer.
Insert the 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 VeriStand when prompted by the installer, or activate at a later time using the NI License Manager.
Evaluating NI DIAdem
New Features
Upgrade and Compatibility Issues
VeriStand 2010 readme—NIVeriStand2010RM
VeriStand 2011 readme—NIVeriStand2011RM
VeriStand 2011 SP1 readme—NIVeriStand2011SP1RM
VeriStand 2012 readme—NIVeriStand2012RM
VeriStand 2013 readme—NIVeriStand2013RM
VeriStand 2013 SP1 readme—NIVeriStand2013SP1RM
VeriStand 2014 readme—NIVeriStand2014RM
Uncompiled Models
Models Created from LabVIEW VIs
Models Compiled for Previous Versions
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:VeriStandersionModelInterfacecustomsrcobsolete. 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:
This file is installed on disk at <custom>src i_modelframework.c rather than in the <custom> directory.
USER_TakeOneStep() now 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.
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.h contains the following differences from NIVERISTAND_API.h:
ni_modelframework.c contains the following differences from codegen.c:
New Location for VeriStand Model Framework Examples
Migrating Files from VeriStand 2009 and Earlier
Select Built-In Custom Devices Not Included
VeriStand Updates and Notifications
Accessing the Help
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:VeriStandxxxxModelInterfacecustom 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. |
Finding 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 InstrumentsNI VeriStandProjectsExample directory.
Stimulus Profile Editor—VeriStand Stimulus Profile Editor examples are located in the <;Public Documents>National InstrumentsNI VeriStandExamples directory.
LabVIEW API—LabVIEW examples that use the VeriStand API are located in the <;Program Files>National InstrumentsLabVIEW 2015examplesNI Veristand directory.
Known Issues
Bug Fixes
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 |
Automating the Installation of NI Products
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
Using NI Launcher
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. |
Pinning Frequently Used Applications
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 |
Finding All Programs
VeriStand Drops Support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 in 2016
Product | Info Code |
LabVIEW | lifecycle |
LabWindows™/CVI™ | cvi_lifecycle |
Measurement Studio | mstudiolifecycle |
TestStand | tslcp |
DIAdem | ddlcp |
SignalExpress | selcp |
VeriStand | nivslifecycle |
Legal Information
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.