NI VeriStand 2015f1Patch Win32Eng PC版完整版及运行版NIVS2015f1补丁

石鑫华视觉

Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活：NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本http://visionbbs.com/thread-490-1-1.html

视觉论坛的各种NI资源，除了视觉相关的模块有使用外，大部分的都不会使用，仅提供资源不提供技术支持。资源的下载地址一般会同时提供NI官方和百度网盘的地址。某些工具包NI地址失效或没有NI地址，只能使用百度网盘地址；如果百度网盘地址失效过期，可联系论坛客服更新。NI的服务器在美国，有时候速度很慢或下载容易出错，这样会造成安装时各种错误而无法安装。建议在下载完成后，对下载资源做校验和(NI一般会提供MD5或SHA256等)验证，与官方或视觉论坛提供的校验和对比，一致就可以安装；如不一致，则需要重新下载。视觉论坛早期下载上传的资源，基本上都是正常下载的资源；2019后下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘。校验和工具下载地址：文件Hash计算器FHash，文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://visionbbs.com/thread-26524-1-1.html

NI VeriStand 2015f1Patch Win32Eng PC版完整版及运行版NIVS2015f1补丁

安装该补丁前请先安装VERISTAND2015
NI VeriStand 2015 Win32Eng PC版完整版及运行版NIVS2015
http://visionbbs.com/thread-24465-1-1.html

VeriStand是一款用于激励生成、数据采集和计算通道等实时测试应用且具有自定义通道换算功能的软件。
VeriStand应用软件可帮助您为NI实时硬件配置I/O通道、数据记录、激励生成和主机通信。您还可以导入仿真模型和控制算法，通过可配置的警报来响应事件，并通过宏录制、TestStand、.NET和其他软件实现测试自动化。您可以使用运行时可编辑的用户界面，监测应用程序数据、警报状态和系统执行指标，并进行交互。虽然使用VeriStand不需要掌握编程知识，但您也可以使用各种编程软件环境（如LabVIEW、ANSI C/C ++、Python和ASAM XIL）来为VeriStand添加自定义功能。

VeriStand2018SP1及以前的早期版本，为32位版本。VeriStand2019及以后更新版本，为64位版本。但是同一年代并不能同时具有32/64位版本。

百度网盘下载地址（限速，请开会员或使用破解限速工具）：
链接: 请注册视觉论坛用户，登录后购买附件下载查看，充值请联系在线客服 提取码: 请注册登录视觉论坛会员，购买附件查看

NI官方下载地址（可能无效或无法下载完成）：
下载地址1：
请注册登录视觉论坛会员，购买附件查看

下载地址2：
请注册登录视觉论坛会员，购买附件查看


VS2015f1.txt (248 Bytes, 下载次数: 0, 售价: 1 元)

2020-7-25 00:24 上传

点击文件名下载附件
VS2015f1

NI VeriStand 2015 Readme

August 2015

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

Overview

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

---

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 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 Systems1	Real-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 NI Linux Real-Time
RAM/Processor	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 (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 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 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.
• 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.
  

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

.NET

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

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.

• 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

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.

New Features

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.

Upgrade and Compatibility Issues

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

VeriStand 2015 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 continuing to use the models in VeriStand 2015:

• 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 \src\ni_modelframework.c rather than in the 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.
      
    
    
  
  

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. All rig files and in4 files must be migrated using a previous version of VeriStand.

Select Built-In Custom Devices Not Included

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.

VeriStand Updates and Notifications

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.

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

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 ni.com/info and enter the Info Code NIVeriStand2015KI for an up-to-date list of known issues in VeriStand 2015.

Bug Fixes

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

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

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

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.

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

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

---

Legal Information

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:

• Notices are located in the \_Legal Information and directories.
• EULAs are located in the \Shared\MDF\Legal\license directory.
• Review \_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.

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.