石鑫华视觉
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 TestStand 4.0 and Patch 美国国家仪器测试序列管理软件TS4.0及补丁
TestStand是一款旨在帮助测试和验证工程师快速构建和部署自动化测试系统的应用软件。TestStand是一款可立即运行的测试管理软件，可帮助您快速开发自动化测试和验证系统。您可以使用TestStand来开发、执行和部署测试系统软件。还可以通过在TestStand中开发测试序列来扩展系统的功能，这些测试序列可集成使用任何编程语言编写的代码模块。TestStand还为报告生成、数据库记录以及与其他企业系统的连接提供了可扩展的插件。您可以使用易用的操作界面将测试系统部署到生产环境中。
百度网盘下载：TestStand4.0
链接: 请注册视觉论坛会员登陆后购买附件下载查看 提取码: 请购买附件下载查看
TestStand4.0Patch_atml_4.0补丁
链接: 请注册视觉论坛会员登陆后购买附件下载查看 提取码: 请购买附件下载查看
TestStand4.0watchpatch补丁
链接: 请注册视觉论坛会员登陆后购买附件下载查看 提取码: 请购买附件下载查看
NI官方下载地址（可能无效或无法下载完成）：
TestStand4.0
请购买附件下载查看
TestStand4.0Patch_atml_4.0
补丁请购买附件下载查看
TestStand4.0watchpatch
补丁请购买附件下载查看
NI TestStand 4.0 and Patch 美国国家仪器测试序列管理软件TS4.0及补丁
http://pcmv.cn/thread-22907-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
NI TestStand™ 4.0 Readme
Known Issues
Installation
You cannot install TestStand using a network path or a mapped network path. You must install TestStand on a local computer.
If TestStand fails to uninstall, reinstall TestStand and then uninstall it.
When you uninstall TestStand 2.0 on a computer where you also installed TestStand 4.0, the TestStand 2.0 uninstaller might incorrectly remove the National Instruments Session Manager 4.0 files. Run the repair utility on NI Session Manager by using the National Instruments Software maintenance utility located in Add/Remove Programs in the Windows Control Panel to restore these files.
Do not install the IVI components from the TestStand 2.0 CD after you install the IVI Compliance Package (ICP) from the NI Device Driver CD included with TestStand 4.0.
If you installed ICP 2.2 or later from the NI Device Driver CD before you installed TestStand 2.0, do not install the IVI components from the TestStand 2.0 CD. Disable the Basic IVI Class Drivers feature within the IVI Engine and Drivers feature during the installation of TestStand 2.0.
If you installed the TestStand 2.0 IVI components after you installed ICP 2.2 or later from the NI Device Driver CD, run the repair utility on the ICP product by using the National Instruments Software maintenance utility located in Add/Remove Programs in the Windows Control Panel to correct this incompatibility.
If you attempt to install TestStand 2.0.1 on a system where you also installed the LabWindows™/CVI™ 8.1 Run-Time Engine (RTE), which TestStand 4.0 installs, the TestStand 2.0.1 installer displays an error while installing the engine. After the installation, TestStand 2.0.1 does not work properly, and if installed, TestStand 4.0 no longer works properly even if you repair the TestStand 4.0 installation. To restore the TestStand 4.0 installation after failing to install TestStand 2.0.1, you must perform a repair operation on the LabWindows/CVI RTE by using the National Instruments Software maintenance utility located in Add/Remove Programs in the Windows Control Panel and then use the TestStand Version Selector application to reselect TestStand 4.0 as the active version.
Complete the following steps if you want to install TestStand 2.0.1 on a system where you also installed the LabWindows/CVI 8.1 RTE.
Use Add/Remove Programs in the Windows Control Panel to uninstall the LabWindows/CVI 8.1 RTE. You must uninstall any software that is dependent on the run-time engine before you attempt to uninstall the LabWindows/CVI 8.1 RTE.
Confirm that the following files and subdirectory were removed from the WindowsSystem32 directory: cvirt.dll, cvirte.dll, cvi95vxd.vxd, and cvirte. If the files still exist, manually remove them. If you cannot delete the cvirte subdirectory, delete the .dll files first, restart the system, and then try to delete the subdirectory.
Install TestStand 2.0.1.
You can now reinstall the LabWindows/CVI 8.1 RTE.
Sequence Editor
By default, the TestStand Sequence Editor caches execution windows to work around an issue where the operating system occasionally leaks objects when you close windows. As a result of this caching, the sequence editor process holds on to Windows USER objects and GDI objects. The Windows Task Manager reports that the sequence editor does not release USER and GDI objects when you close execution windows, which is expected behavior because the sequence editor re-uses the USER and GDI objects in subsequent executions. By default, TestStand caches all execution windows until the number of available USER objects or GDI objects in the TestStand process is less than 1,000.
Typically, you do not need to change this limit, but you can specify the maximum number of windows in the cache by creating a DWORD registry value named SeqeditExeDocCacheSize under the HKEY_LOCAL_MACHINESOFTWARENational InstrumentsTestStand.0 key. The recommended value is the number of execution windows you typically have open concurrently when running executions in the sequence editor. For example, if you typically run a batch process with 8 test sockets, specify a value of 9, which includes 8 executions that correspond to the test sockets and one controlling execution. You might leak USER objects and GDI objects when the number of concurrent execution windows you create is greater than the number you specify in the registry. The registry entry is an unsigned integer. A value of 0 disables the cache.
When the sequence editor attempts to open a new document and finds that there are fewer than 500 USER objects or GDI objects available, it clears the cache and displays a warning message.
The TestStand Sequence Editor occasionally reports property object leaks when you use the Close item from the taskbar context menu to close the application and you enabled the Report Object Leaks option in the Debug Options dialog box that you access from the Station Options dialog box.
The TestStand Sequence Editor can hang when you select Show Differences on a file in the Workspace pane and the difference and merge utilities specified by your source code control provider are not installed.
The Variables View pane incorrectly highlights an expression property in red when you select multiple steps and the expression contains references to variables in locals, parameters, or file globals.
Sorting messages by clicking the Time Stamp column in the Output Messages pane does not chronologically order messages posted within the same minute.
The TestStand Sequence Editor incorrectly prompts you to unlock a file before displaying the Sequence Properties or Sequence File Properties dialog boxes.
Changing the step selection in the Steps pane of the sequence editor is slow when you select an element of a large array in the Variables pane.
The LabVIEW Module tab incorrectly displays the Create Custom Data Type dialog box multiple times when you select multiple steps and you click the Create Custom Data Type button. Instead, select only one step before clicking the button.
Using Watch pane expressions that modify the structure of objects, such as delete subproperties or change size of an array, can prevent the Variables pane from refreshing properly, or can cause the Variables pane to error.
User Interface (UI) Controls
If you click a TestStand UI control hosted in a .NET user control in the designer of Visual Studio 2005, Visual Studio might crash. Microsoft has a hotfix for this Visual Studio 2005 limitation. Refer to the Microsoft Knowledge Base Article ID 916495, located at http://support.microsoft.com/?kbid=916495, for more information.
The Variables View control can leak a USER object when you use the keyboard to change the value of a Boolean value.
The Sequence View and ListBar controls can leak memory when you quickly display and dismiss the context menu multiple times.
If you place a ReportView control on a LabWindows/CVI panel that does not have a title bar, the control hangs when you click it after running a sequence.
You cannot use the keyboard to navigate to the adapter buttons within the Insertion Palette control for non-.NET applications.
The CheckBox.Forecolor and CheckBox.BackColor properties do not change the appearance of a control when you set CheckBox.Style to CheckBoxStyle_Button.
LabVIEW
TestStand supports Sequence File Translators built only with LabVIEW 8.2 and later.
If you uninstall LabVIEW 8.0 from a computer where you also installed LabVIEW 7.1.1, TestStand might return an error when executing a VI that uses a waveform data type. The error states that TestStand fails to find a waveform interface. Run the repair utility on LabVIEW 7.1.1 by using the National Instruments Software maintenance utility located in Add/Remove Programs in the Windows Control Panel to correct this issue.
TestStand does not support calling VIs on remote computers if you save a VI without the block diagram and the version of the VI is different than the active version of LabVIEW 8.0 installed on the computer.
LabVIEW User Interface executables that do not use the TestStand ActiveX User Interface Controls might hang when launched. The hang occurs when TestStand loads the LabWindows/CVI Run-Time Engine and both LabVIEW and the run-time engine access computer resources at the same time. You can prevent the hang by using a Call Library Function VI to invoke a function in the run-time engine to force LabVIEW to synchronously load the run-time engine into memory before creating the TestStand engine.
A LabVIEW Run-Time Engine cannot load a top-level VI when the LabVIEW Run-Time Engine finds a subVI with the same name and the subVI was saved with a different version of LabVIEW. This behavior can occur when you try to run a VI that you save in the <TestStand>API and <TestStand>Examples directories and the directories contain VIs with the same names as the subVIs that the VI uses and the VIs were saved with a different version of LabVIEW. To avoid this behavior, save VIs in a working directory instead of using the NI directories under TestStand.
Normally, the LabVIEW Run-Time Engine can execute top-level VIs only when you save the VI with the entire VI hierarchy or if the subVIs can be located using the LabVIEW search directories. By default, the LabVIEW Run-Time Engine does not search for required subVIs from the LabVIEW development system, such as files in vi.lib. However, when TestStand loads a LabVIEW Run-Time Engine on a computer where you also installed the LabVIEW development system, TestStand automatically adds directories from the development system to the search paths for the LabVIEW Run-Time Engine. Thus, when TestStand executes a top-level VI saved without its hierarchy, the LabVIEW Run-Time Engine attempts to find subVIs by first searching the directory of the top-level VI and then searching the directories TestStand added. If a subVI saved by a different version of LabVIEW is found first, the LabVIEW Run-Time Engine cannot load the subVI and fails to load the top-level VI.
TestStand cannot call a LabVIEW 8.2 or earlier Express VI that has a RealMatrix control wired to its connector pane.
LabVIEW does not call PreTranslateAccelerator for ActiveX controls, which prevents TestStand UI controls in LabVIEW User Interfaces from processing some key strokes, such as using <Tab> to autocomplete expressions or navigate within controls, using <Ctrl-Shift> to perform an operation, or using <Shift-Arrow> to select multiple items.
A TestStand 3.5 operator interface built with LabVIEW 7.0 can fail to launch or can display a misleading error message if the LabVIEW 7.0 Run-Time Engine is not installed. TestStand 4.0 does not install the LabVIEW 7.0 Run-Time Engine.
The Help»Help Topic menu item is disabled in the LabVIEW User Interface after using the command the first time. Use the Ctrl-F1 shortcut key instead.
LabVIEW applications, such as a TestStand LabVIEW User Interface, can hang when calling a function in a LabVIEW-built DLL from the UI thread. For example, a TestStand LabVIEW User Interface can hang when creating the TestStand Engine and the engine loads a Sequence File Translator DLL built with LabVIEW. To workaround this issue, create the TestStand Engine in a non-UI thread, such as Other 2.
The Debug Warnings dialog box is not modal and launches behind the LabVIEW Simple UI front panel when you exit the application and the process did not properly release TestStand objects.
Microsoft Visual Studio
Visual Studio 2005 for C# might crash on exit when an inactive tab page on an open form in the designer includes certain ActiveX controls, such as when you exit Visual Studio with the main form open in the designer for the example in <TestStand>UserInterfacesNIFull-FeaturedCSharp. The crash is harmless, and you can avoid it by closing the form in the designer before you exit Visual Studio.
TestStand might cause Visual Studio to generate an access violation when you use TestStand to generate C++ code and then exit Microsoft Visual Studio before you exit TestStand.
Visual Studio 2005 might crash when you rebuild a solution that uses the TestStand UI controls and you try to view a Microsoft Windows Form in Design view. When you do this, Design view might not show the Windows Form, and you might receive error messages. Refer to Microsoft Knowledge Base Article 912019, located at http://support.microsoft.com/kb/912019/en-us?spid=3041, for more information about this issue.
Visual Studio 2005 displays the error message "Parameter is not valid" when you attempt to select an icon file as the image for a TestStand UI Button control at design time. This error occurs if the icon file contains only a 16-bit color image. You can work around this limitation by setting the icon image programmatically at run-time or by loading an icon file that contains a 256-color image.
MFC-based applications, such as TestStand User Interfaces, can leak GDI objects on computers running Windows XP SP2 when the applications create and destroy child windows. Refer to the Microsoft Knowledge Base Article 319740, located at http://support.microsoft.com/kb/319740, for information about how to resolve this known Microsoft bug.
MFC-based TestStand User Interfaces can crash when using the Workspace Browser dialog box with the Microsoft Team Foundation Server SCC provider.
Deployment Utility
The LabVIEW development system can crash when the Deployment Utility attempts to deploy VIs that call into LabVIEW DLLs. The LabVIEW error message contains the text "Fatal Internal Error: "menuPrivate.cpp". To prevent this problem, you must prevent the LabVIEW development system from unloading the DLLs from memory by creating a new project in LabVIEW, adding the VIs to the project, and opening the VIs from the project.
Building a deployment fails when you include any VI that uses NI_AALPro.lvlib in its hierarchy and you previously installed LabVIEW 8.2.1 on top of LabVIEW 8.2. The Deployment Utility fails to load broken VIs that the library might use. To fix these broken VI files, run the repair utility on LabVIEW 8.2.1 by using the National Instruments Software maintenance utility located in Add/Remove Programs in the Windows Control Panel. You can also uninstall and reinstall LabVIEW 8.2.1.
Miscellaneous
Applications that create and destroy the Microsoft Internet Explorer (IE) control might leak GDI memory, making the application and the computer unstable. The memory leak occurs when you run the application on Windows XP Service Pack 2 and you installed the Handwriting feature (version 1.0.1038 of the Skchui.dll file) for a Microsoft Office product on the computer. For TestStand, the sequence editor creates new instances of the IE control for each new execution document, and each ReportView User Interface control creates a new instance of the IE control. To prevent this GDI memory leak, uninstall the Handwriting feature for any Microsoft Office product and for any other product that uses this shared feature. Refer to the Microsoft Knowledge Base Article 896429, located at http://support.microsoft.com/default.aspx?scid=kb;en-us;896429, for more information about this issue.
The Microsoft IE control that TestStand applications use to display XML reports can leak handles or crash if the control cannot find the style sheet you specify in the Report Options dialog box and the control displays XML report files using the default XML style sheet.
The Allow All Users Access from Remote Machines checkbox in the Station Options dialog box does not work on some non-English Windows XP SP2 operating systems, such as German Windows XP. The checkbox adds the built-in account name "ANONYMOUS LOGON" to the DCOM access permissions, but the account name "ANONYMOUS LOGON" is incorrect for some non-English operating systems. If you use a non-English Windows XP SP2 or later, refer to the Setting up TestStand as a Server for Remote Sequence Execution section of Chapter 5, Adapters, of the NI TestStand Reference Manual for information about configuring Windows system security to allow users to access and launch the TestStand server remotely.
XML reports might show a table of measurement data instead of a graph in the following situations:
The TSGraphControl.ocx ActiveX control located in the <TestStand>ComponentsNIToolsGraphControl directory is not installed or registered on your computer.
Internet Explorer security settings can prevent Web pages from using scripting to create and use an ActiveX control. When you view Web pages located on your computer, Internet Explorer uses the My Computer zone setting on the Security tab of the Internet Options dialog box. By default for Windows XP SP2, the security level for the My Computer zone is set to High, which prevents scripting from running locally. By default, the settings for the My Computer zone are not visible in the Internet Options dialog box of Internet Explorer. Refer to the Microsoft Knowledge Base Article 315933, located at http://support.microsoft.com/?id=315933, for information about altering the Windows registry to make the My Computer zone visible in the Internet Options dialog box of Internet Explorer. When you have access to the My Computer zone settings in the Internet Options dialog box, enable scripting for the zone or change the My Computer security zone level to Medium.
Under certain circumstances, in-process (DLL) ActiveX automation servers created with Microsoft Visual Basic that are used from a multithreaded client application, such as TestStand, might fail with an access violation. This type of server failure might cause TestStand to hang or crash when freeing resources in the DLL. Out-of-process (EXE) servers do not have this problem.
Refer to the Microsoft Knowledge Base Article 186273, located at http://support.microsoft.com/kb/186273 (previously published as Article Q186273), for information about how to resolve this known Microsoft bug. If you are using Microsoft Visual Basic 6.0, you must also enable the Unattended Execution and Retain In Memory project properties.
This workaround forces the DLL to remain in memory after an execution finishes, which requires you to close the sequence editor before you can recreate the DLL. While you are developing, you can disable this code by commenting out the body of Sub Main() (mentioned in Article 186273) so you can recreate your server without exiting TestStand. When your server is ready for release, enable the code to prevent a run-time crash.
ActiveX EXE servers that display a dialog box and call any TestStand API function that launches a second dialog box while the first dialog box is still active must create the first dialog box in a thread initialized as single-threaded apartment for the TestStand dialog box to function correctly. Otherwise, TestStand might hang.
When executing sequences using a custom process model, TestStand might return an error when the custom process model appends data to an existing XML report but fails to correctly fix the root tags. Before the custom process model calls Report.Save, add a sequence call to "Remove Root Tags From XML Report" in ReportGen_XML.seq. After the custom process model Report.Save, add a sequence call to "Add Root Tags To XML Report" in ReportGen_XML.seq.
The execution arrow can appear in the wrong location after interactively executing steps if you previously suspended an execution on a step because of a watch breakpoint, post action breakpoint, or run-time error breakpoint. In addition, a run-time error can occur if you also set the next step to another step in a different step group and the step index of the step you originally suspended at exceeds the number of steps in the new step group. When this error occurs, you must restart TestStand.
The TestStand File dialog boxes can leak a USER object when used.
TestStand can crash after unloading a DLL built by an evaluation copy of LabWindows/CVI. The DLL does not properly remove a timer callback that executes after the DLL is unloaded.
TestStand 4.0 supports XML files, which are larger in size than INI files. TestStand might fail to save an XML file if the file is very large and the computer does not have enough memory. Change the file format to Binary or INI before you attempt to save the file to work around this issue.
When TestStand unloads a DLL built with LabWindows/CVI 8.1 or earlier and the DLL uses the ActiveX Automation Library, the DLL leaks a handle. For example, the leak occurs each time you select Tools»Sequence File Documentation, which runs a sequence that calls into a LabWindows/CVI DLL. The next release of LabWindows/CVI will correct this issue. You must recompile the DLL to prevent the DLL from leaking the handle.
McAfee ePolicy can cause TestStand to leak memory when you display XML reports in the sequence editor or a user interface that uses the ReportView control and your computer contains scriptproxy.dll, version 8.0.0.992, located in the C:Program FilesNetwork AssociatesVirusScan directory. Install a later version of this DLL, such as version 8.0.0.955, to fix this issue.
Database logging and on-the-fly report generation slowly leak memory when executions use a Sequence Call step to create new threads.
On-the-fly report generation incorrectly indents step results that follow a Sequence Call step that creates a new thread.
TestStand reports property object leaks if you call a remote sequence and a run-time error occurred because you passed extra parameters to the sequence. To see this problem, you must enable the Report Object Leaks options in the Debug Options dialog box that you access from the Station Options dialog box.
TestStand does not call the SequenceFilePreInteractive and SequenceFilePostInteractive callbacks when running a step interactively using a process model. This problem also occurred in previous versions of TestStand.
TestStand watch expressions do not suspend the execution if the expression returns a reference object and the previous value of the object returned Nothing. Instead, use an expression that returns a Boolean value, such as "Locals.Reference != Nothing".
TestStand prompts you to reload files when source code control providers, such as MKS Source Integrity, Serena PVCS, and IBM Rational ClearCase, change the timestamp of files when you add the files to source control or check the files in or out of source control. TestStand might display errors for some operations when you reload the files.
When you check out a project file, TestStand incorrectly attempts to check out files under the project file in the workspace that are not under source code control. TestStand displays an error if you do not exclude these files from the check out operation.
When you import a waveform while configuring a Configure operation of an IVI FGen step, the dialog box can fail to store the waveform data with the step. You can work around this problem by immediately closing the dialog box after importing the data. In addition, if you browse to a file to configure the step to load the waveform from a file, the filename is not stored with the step. You must edit the filename in the path control to ensure that step saves the changes to the filename setting.
A configure operation for an IVI FGen step can return an error if the step specifies a waveform that is stored in the step. You can work around this problem by configuring the step to load the waveform from a file.
The Differ window in the sequence editor and the differ application do not display differences between strings with different preceding and/or trailing quote characters.
The .NET Adapter generates a run-time error when a step passes an empty array as a parameter. You must pass a non-empty array.
TestStand suspends an execution in a process model callback instead of suspending in the model entry point sequence when you step out of a client sequence file.
Corrections to Documentation
The NI TestStand 4.0 Quick Start Guide, the NI TestStand Release Notes, and the NI TestStand Reference Manual incorrectly state that TestStand integrates with Microsoft Visual Studio .NET 2003 if you install Measurement Studio 7.1 (or later) Enterprise Edition. TestStand can call DLLs and .NET assemblies that you create with Visual Studio .NET 2003, however, you must use Visual Studio 2005 to create and edit code directly from TestStand and to initiate debugging directly from TestStand. The incorrect statements are located on the following document pages:
NI TestStand 4.0 Quick Start Guide - Page 2
NI TestStand Release Notes - Page 2
NI TestStand Reference Manual - Page 5-3
Bug Fixes
Additional Information
For additional information about TestStand, refer to the support section of the National Instruments Web site at http://www.ni.com/support/teststandsupp, which also includes an email-based TestStand technical discussion forum.
Copyright
Trademarks
Patents