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 2009 Win32Eng PC版完整版及运行版NIVS2009
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 2009 Win32Eng PC版完整版及运行版NIVS2009
http://pcmv.cn/thread-27355-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
NI VeriStand 2009 Readme
June 2009
This file contains important information about NI VeriStand 2009, including system requirements and installation instructions.
Overview
Supported Platforms
System Requirements
Installation Instructions
Migrating from NI Dynamic Testing Software 1.0
Accessing the Help
Known Issues
Bug Fixes
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.
Supported Platforms
NI VeriStand supports Windows Vista/XP. NI VeriStand runs as a 32-bit application on Windows Vista 64-bit operating system. NI VeriStand does not support Windows 2000.
System Requirements
To configure and run a simulation using your existing model DLL, you need only NI VeriStand installed. To develop a model and convert it into a model DLL 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 and The MathWorks, Inc Simulinkо application software release 14.x, 2006a, 2006b, 2007a, 2007b, 2008a, 2008b, or 2009a
The MathWorks, Inc. Real-Time Workshopо software release 14.x, 2006a, 2006b, 2007a, 2007b, 2008a, 2008b, or 2009a
Microsoft Visual C++ 6.0, .NET 2003, 2005 (Professional or Express), or 2008 (Professional or Express)
To develop a model and convert it into a model DLL using other modeling environments, contact your model vendor for requirements.
To create custom devices, menu items, workspace controls and indicators, timing and sync devices, or Stimulus Profile Editor headers, you must have LabVIEW 2009 installed.
To import CAN channels from a .dbc or .ncd file, you must have the following NI-CAN driver software installed on the host computer.
Refer to the National Instruments Web site to download the NI-CAN Frame Channel Conversion Library.
To run a simulation on a real-time (RT) target, the target must have NI VeriStand installed. You can install software on the target using Measurement & Automation Explorer (MAX). NI VeriStand only supports RT targets running the Ardence Phar Lap Embedded Tool Suite (ETS) operating system. The RT target must meet the following minimum system requirements:
256 MB of memory
LabVIEW 2009 Real-Time Module
You also must install the following driver software versions, even if you are not using the associated hardware types:
National Instruments Hardware | Driver Software Version Required |
National Instruments FPGA Devices | NI-RIO 3.2 or later |
National Instruments CAN Interfaces | NI-CAN 2.6.3 or later NI-CAN Frame Channel Conversion Library 1.0.3 or later |
National Instruments DAQ Devices | NI-DAQmx 8.9.5 or later |
Installation Instructions
Complete the following steps to install NI VeriStand.
Note 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.
Log on as an administrator or as a user with administrator privileges.
Insert the NI VeriStand 2009 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.
Search the KnowledgeBase for information about installation order if you are using NI TestStand or LabVIEW with NI VeriStand.
Migrating from NI Dynamic Testing Software 1.0Mapping Directories
You can use files you created using NI Dynamic Testing Software 1.0 in NI VeriStand 2009. You must move your NI Dynamic Testing Software files to the corresponding NI VeriStand folders. NI Dynamic Testing Software folders correspond to NI VeriStand folders as follows:
NI Dynamic Testing Software | NI VeriStand |
Configurations | System Definitions |
Rig Setups | Workspace Files |
Test Setup | Stimulus Profiles |
Mutating Files
When you load your NI Dynamic Testing Software .rig and .in4 files in NI VeriStand for the first time, NI VeriStand mutates the files for compatibility with NI VeriStand. As part of the conversion process, NI VeriStand moves aliases from the .rig file to the .in4 file. If you load multiple .rig files that share the same .in4 file, aliases might be overwritten. National Instruments recommends that you take the following precautions before loading NI Dynamic Testing Software files in NI VeriStand:
Using Real-Time Engines
If you install NI VeriStand on a computer that already has NI Dynamic Testing Software installed, the NI Dynamic Testing Software RT engine appears to be unavailable in the LabVIEW Real-Time Software Wizard in Measurement & Automation Explorer. In the LabVIEW Real-Time Software Wizard, set the VeriStand Engine version to 1.0 to install the NI Dynamic Testing Software RT engine. You cannot have both the VeriStand Engine and the NI Dynamic Testing Software engine installed at the same time on the RT target. Refer to the Measurement & Automation Explorer Help for more information about using the Real-Time Software Wizard.
Maintaining Behavior
NI Dynamic Testing Software automatically set the value of a Stimulus Profile Generator and a mapped channel to zero at the end of a test. NI VeriStand does not exhibit this same behavior. NI VeriStand leaves the channel at the last set value. To maintain the behavior of NI Dynamic Testing Software, add a step at the end of the test to ramp the channel to zero in zero seconds.
Accessing the Help
Refer to the NI VeriStand Help, accessible by selecting Help»Search the NI VeriStand Help from the pull-down menu in NI VeriStand.
Known Issues
You can access the software and documentation known issues list online. Refer to the National Instruments Web site for an up-to-date list of known issues in NI VeriStand 2009.
Bug Fixes
The following items are the IDs and titles of a subset of issues fixed between NI Dynamic Testing Software 1.0 and NI VeriStand 2009. 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 |
115727 | Improve error handling and reporting |
116674 | User access levels are not always enforced |
117174 | Parameters committed each time in RT engine, should be committed at end of each set |
121114 | In Test Profile Editor, using Point Play, the graph is always interpolated |
121117 | System Explorer window is not the same when opened in stand-alone form versus from Getting Started window |
123576 | CAN ports are always configured in pairs, even if you only need one port |
127468 | FPGA support is limited to pre-determined configurations |
127718 | Channel names, aliases, alternative name, and so on is not consistent in the system |
127787 | Closing Workspace window while profile is running leaves profile editor in disabled state when Workspace window reopened |
128021 | Browsing for a relative path does not work and results in a blank relative path |
128376 | When changing between .rig files, user login is not consistent |
128513 | Custom device does not correctly handle unconfigured inputs or outputs |
128606 | System Explorer window: The number of streamed channels seems to be tied to the number of Max Profile Steps |
128612 | Need ability to assign specific CPU for all high priority loops |
129143 | Creating (or renaming) a screen named after a menu item (e.g. Screen) disables the menu item. |
130582 | Add support for vector inports and vector outports |
133101 | Parameter import list is ignored, and all parameters are always imported |
134032 | Model did not start with multiple custom devices |
134200 | Model import definition allows duplicate subsystem names in the same group |
135697 | Step-based GENs have unit delay for applying values |
136512 | Mappings in Table-based Test Profile tool can interfere with mappings from System Explorer window |
150058 | Sometimes when resizing a graph, it will start moving off the Workspace window and disappear |
153096 | Parsing issue with model inputs and output that are vectors |
157684 | Clicking on an empty parameter folder in the System Explorer window causes error |
157716 | Timeout error with large .in4 file |
158004 | Clicking the Enter button in a text field of a procedure step dialog box cancels, even though the OK button is highlighted |
158208 | TDMS File Viewer displays the wrong panel on the right side |
170168 | Incoming CAN message does not correctly link to CAN1 |
Copyright
© 2009 National Instruments Corporation. 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.
Trademarks
NI VeriStand, NI TestStand, National Instruments, NI, ni.com, NI-RIO, NI-CAN, NI-DAQmx, and LabVIEW are trademarks of National Instruments. Refer to the Terms of Use section on ni.com/legal for more information about National Instruments trademarks.
MATLABо, Real-Time Workshopо, and Simulinkо are registered trademarks of The MathWorks, Inc.
Other product and company names mentioned herein are trademarks or trade names of their respective companies.
Only Licensed Use is Permitted
You are only permitted to use this product in accordance with the accompanying license agreement. All rights not expressly granted to you in the license agreement accompanying the product are reserved to NI. Further, and without limiting the forgoing, no license or any right of any kind (whether by express license, implied license, the doctrine of exhaustion or otherwise) is granted under any NI patents or other intellectual property right of NI with respect to any other product(s) of NI or of anyone else (including without limitation, the MATLAB, Simulink and or the Real-Time Workshop software of The MathWorks, Inc.), including without limitation, the right to use any of these other products. 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.
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.