August 2012
This document contains information about bugs fixed in NI TestStand 2012. Refer to the NI TestStand Version 2012 Release Notes for an overview of new features and information about getting started with TestStand, such as system requirements, installation instructions, and descriptions of the TestStand licenses. If you do not activate a TestStand license, TestStand operates in Evaluation Mode.
Refer to the What's New in TestStand topics for TestStand 2012 in the NI TestStand Help for detailed information about other changes since TestStand 2010 SP1, including new features. Refer to the What's New in TestStand topics for previous versions of TestStand in the NI TestStand Help for information about new features, compatibility and known issues, and bug fixes for those versions.
Upgrading TestStand 2010 SP1 to TestStand 2012
Installing TestStand 2012 Deployment Software
Use the Microsoft operating systems and service packs described in the following table with TestStand 2012:
| Operating System | Recommended Service Pack | Required Service Pack | Comments |
|---|---|---|---|
| Windows 7 (32- and 64-bit), including Starter Edition | Service Pack 1 | — |
Refer to the TestStand and Windows 7/Vista section of the NI TestStand Version 2012 Release Notes for more information about using TestStand on Windows 7/Vista. |
| Windows Vista (32- and 64-bit) Business, Enterprise, or Ultimate | Service Pack 2 | Service Pack 1 | |
| Windows XP | — |
Service Pack 3 | — |
| Windows Server 2008 R2 (64-bit) | — |
Service Pack 2 | TestStand supports only R2 editions of Windows Server. |
| Windows Server 2003 R2 (32-bit) | — |
Service Pack 2 |
TestStand does not support Guest user accounts on Windows. TestStand supports Administrator and Limited accounts on Windows 7/Vista and Administrator, Power Users, and Users accounts on Windows XP.
Refer to the NI TestStand Version 2012 Release Notes for additional recommended system requirements.
Refer to the National Instruments KnowledgeBase article 50O9851O, Does TestStand support calling VIs using LabVIEW 64-Bit? on the National Instruments website for information about LabVIEW 64-bit support.
You can install TestStand without viewing any installation dialog boxes. Refer to the National Instruments KnowledgeBase article 4CJDP38M, Automating the Installation of a Single Installer, on the National Instruments website for information about installing National Instruments software silently. Refer to the NI TestStand Version 2012 Release Notes for more information about installing TestStand.
TestStand relies on licensing activation. You must activate a valid TestStand license before you can run TestStand. To activate TestStand, use the serial number you received as part of your installation package. Refer to the NI TestStand Version 2012 Release Notes for more information about licensing in TestStand.
You can install TestStand 2010 SP1 and TestStand 2012 on the same computer and run applications in both versions, or you can upgrade an existing TestStand 2010 SP1 installation to TestStand 2012. TestStand 2010 SP1 and TestStand 2012 use separate directories for the <TestStand>, <TestStand Public>, and <TestStand Application Data> directories. You cannot install TestStand 2012 over a previous TestStand version, and you cannot install TestStand 2012 in the default installation directory for a previous version of TestStand. If you installed a previous version of TestStand in a non-default directory, you can uninstall the previous version of TestStand and install TestStand 2012 to that directory.
If you are upgrading from TestStand 2010 SP1 or TestStand 2010, you can use the TestStand 2012 Migration Utility to migrate customizations and configuration settings from the earlier version of TestStand. You can also upgrade manually. Refer to the Migrating from TestStand 2010 SP1 or TestStand 2010 Using the TestStand Migration Utility section of the NI TestStand Version 2012 Release Notes for information about using the utility.
If you are upgrading from TestStand 4.2.1 or earlier, you must manually migrate customizations and configuration settings to TestStand 2012. Refer to the Manually Migrating from Any Version of TestStand section of the NI TestStand Version 2012 Release Notes for information about the tasks you need to perform to upgrade manually.
You can install deployments for TestStand 2010 SP1 and TestStand 2012 on the same computer. Use the TestStand Version Selector to select the active version of TestStand before you launch the deployed TestStand application. National Instruments does not support running applications that use two different versions of TestStand at the same time.
Refer to the List of Known Issues in TestStand 2012 on the National Instruments website for a list of known issues in TestStand 2012. You can also view this list by date.
The following sections list the bugs that existed in TestStand 2010 SP1 or earlier and have been fixed in TestStand 2012. This is not an exhaustive list of issues fixed in TestStand 2012. If you reported an issue to National Instruments and were given a CAR ID to track the issue, you can search for the CAR ID in the ID or Legacy ID column to determine whether the issue has been fixed.
TestStand Engine
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 235098 | Performing a Step Into operation on a step might step into subsequences that pre-step or post-step Engine callbacks call | If a pre-step or post-step Engine callback, such as SequenceFilePostStep, calls a subsequence, performing a Step Into operation on a step steps into the subsequence the callback calls. If the callback does not call a subsequence, performing a Step Into operation on a step executes the step and moves on to the next step. | |
| 251806 | TestStand attempts to step into the Determine Report File Path C/C++ DLL step after stepping out of a PreUUT callback | If you are debugging a PreUUT callback sequence and you try to step out of the sequence, TestStand attempts to step into the Determine Report File Path C/C++ DLL step in the Test UUTs Execution entry point. If you had originally traced into the Test UUTs sequence, this behavior would not occur. | |
| 283247 | Viewing expression steps with a large number of comma-separated statements can cause TestStand to stop responding | Viewing expression steps with a large number of comma-separated statements can cause TestStand to crash or stop responding. | |
| 305733 | Performing a Flush or GetStatus operation on a global TestStand queue might return error -17500 | Performing a Flush or GetStatus operation on a global TestStand queue might return error -17500 if you configure the operation to store the queue elements in an array, such as by specifying the Location to Store Array of Queue Elements option. This issue exists for global TestStand queues, which are queues with names that start with an asterisk (*), but not for local TestStand queues. | |
| 316288 | Using the <Esc> key or closing the Run-Time Error dialog box causes the execution to pause | Closing the Run-Time Error dialog box using the <Esc> key or by closing the window causes the execution to pause. This behavior might be a problem for users with operator privileges because these users do not have sufficient privileges to resume the execution. | |
| 335596 | Passing a value of 0 for the subProperty parameter of the PropertyObject.InsertSubProperty method causes TestStand to stop responding | After you execute a sequence that calls the PropertyObject.InsertSubProperty method from an ActiveX/COM step and you pass a value of 0 or nothing for the subProperty parameter, TestStand stops responding when you use autocomplete while editing an expression. You must restart TestStand to recover from this state. | |
| 349971 | Boolean logic might return an incorrect result when you use constant values for both operands | The Boolean logic operators && and || might return an incorrect result when you use constants for both operands, such as, 'False && True'. This issue does not occur if either operand contains a variable value. |
TestStand Sequence Editor
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 153495 | Syncing files with a source code control system from the TestStand File/Diff Merge application in the sequence editor returns an error | If you try to diff files in the sequence editor with a workspace file open, TestStand prompts you to edit the current files, sync the files with a source code control (SCC) system first, or cancel the operation. If you choose to sync the files first, TestStand returns the One or more errors have occurred. Please save your work and restart the application. |
|
| 193751 | Using a LabVIEW Edit substep to remove an element from a TestStand array while elements of that array are visible on the Variables pane causes an error on the Variables pane | When you enable the Show VI Front Panel When Called option for a LabVIEW Edit substep and use that substep to remove an element from a TestStand array while elements of that array are visible on the Variables pane, the Variables pane returns an error under certain screen resolution or color quality settings. You must restart TestStand in this situation. | |
| 253099 | The Watch View pane might not refresh all watch expressions | In some cases, the Watch View pane might not refresh all current watch expressions after you make an edit to an expression. | |
| 313685 | The RunState.IsEditor property evaluates to False in the SequenceFileLoad callback of a process model when launching the sequence editor | When you launch the sequence editor, the RunState.IsEditor property evaluates to False in the SequenceFileLoad callback of a process model. | |
| 314101 | An error can occur when you change the run mode for multiple selected Sequence Call steps | When you select multiple Sequence Call steps and you change the run mode step setting, you might encounter error -17325 if any of the Sequence Call steps contain one or more multi-dimensional array parameters. | |
| 315092 | The Parameters Table for a Sequence Call step might crash when you use the navigation buttons while a parameter is selected | If you click the Back or Forward navigation buttons while you have a parameter selected in the Parameters Table on the Sequence Call Module tab, the Parameters Table might crash and require a restart of the sequence editor. This error occurs only if you modified the selected parameter before clicking the navigation button. | |
| 316107 | Errors occur when you save or modify a TestStand Sequence Analyzer project while a TestStand workspace is open | If you modify or save a TestStand Sequence Analyzer project while a TestStand workspace file is open, TestStand returns the Object reference is not set to an instance of an object error. This error can also occur when you shut down the sequence editor while a TestStand workspace and sequence analyzer project are open because shutting down TestStand saves the sequence analyzer project. |
|
| 337449 | Sequence Hierarchy window cannot open with certain security policy settings | If the System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing policy setting is enabled in the Microsoft Windows security policy settings, the Sequence Hierarchy window fails to launch and returns an error that indicates that the GoView license is invalid or expired. | |
| 344948 | Deleting rows or columns of a multi-dimensional array terminal of a LabVIEW front panel can cause the VI Parameter Table to stop functioning | When you configure the parameters for a LabVIEW step, you delete rows or columns of a multi-dimensional array terminal in LabVIEW, and then you configure the current value to be the default value in the VI Parameter Table on the LabVIEW Module tab, the VI Parameter Table might stop functioning in TestStand. This issue occurs only if you expanded the elements of the deleted rows or columns before you deleted the rows or columns. |
TestStand Deployment Utility
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 207845 | Using the horizontal scrollbar in the deployment utility prevents you from selecting files | You cannot select or deselect files on the Distributed Files tab of the deployment utility when you use the horizontal scrollbar. | |
| 277685 | The deployment utility returns an incorrect error when the path to a LabVIEW packed project library source file is too long | If the path for a LabVIEW packed project library source file is too long, the deployment utility returns the following error: The build was aborted because LabVIEW is missing one or more files. The Deployment Utility is now determining which VIs reference the missing file(s). Internal error code 7 Processing VIs.... |
|
| 301234 | The deployment utility might encounter errors when deploying locked VIs when you enable the Apply New Password option | When you enable the Apply New Password option in the LabVIEW VI Options dialog box of the deployment utility and any VIs you include in the deployment call a subVI with the Locked (No Password) setting enabled, the deployment fails. | |
| 312382 | Errors can occur when you set VI destinations to LLBs and you enable the Output VIs to a Packed Project Library option | When you create a deployment that includes VIs, an error occurs in the build process under the following conditions:
|
|
| 317336 | The Specify Configuration Directory option does not function in the TestStand 2010 SP1 Deployment Utility | The Specify Configuration Directory option in the Advanced Installer Options dialog box does not function in the TestStand 2010 SP1 Deployment Utility. The deployment utility uses the default configuration directory on the deployment target computer even when you enable this option. | |
| 333714 | TestStand User Interfaces might contain blank VariablesView controls or return an unhandled error on the computer to which you deployed the test system | If you create a TestStand deployment with the following conditions, TestStand might return an error when you attempt to edit sequences on the computer to which you deployed the test system:
TSDotNetSupport.dll failed to register. error. |
TestStand User Interfaces
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 37001 | 49GDNHG0 | Modifying the run mode of a step in a user interface in Operator Mode does not mark the sequence file as modified | Modifying the run mode of a step in a user interface in Operator Mode does not mark the sequence file as modified, even after you change the user interface to Editor Mode. This change does not have any effect in Operator Mode because you cannot save files. |
TestStand User Interface (UI) Controls
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 54115 | 3BDELTRA | Navigating back or using links in the Report control might error | The sequence editor and user interfaces that include the Report control might return an error or reach an unusable state when you aggressively click links and navigate back on the Microsoft Internet Explorer control. This Internet Explorer issue is more likely to occur when the application runs more slowly, such as while debugging the application with LabWindows/CVI or another debugger. |
LabVIEW
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 191678 | When you use LabVIEW 2009 to build the LabVIEW Simple User Interface, the user interface remains open if you do not move the mouse after closing the user interface | If you rebuild the LabVIEW Simple User Interface with LabVIEW 2009 and then run the executable, failing to move the mouse after clicking the close button on the titlebar or clicking the Exit button causes the user interface to remain open. When you move the mouse, the user interface closes successfully. This behavior does not exist with the LabVIEW Full-Featured User Interface. LabVIEW 2012 fixed this behavior. | |
| 206259 | The LabVIEW Adapter does not coerce out-of-range values you pass to an enumeration parameter in a LabVIEW code module | When you pass a value to an enumeration parameter in a LabVIEW code module, the LabVIEW Adapter does not modify values that are out of range to a valid item index. | |
| 233755 | Loading a VI that calls a .NET assembly fails when using Turkish regional settings | Loading a VI that calls a .NET assembly fails in TestStand on a computer configured to use Turkish regional settings. If you configure the LabVIEW Adapter to use the LabVIEW Development System, TestStand returns the error An error occurred accessing the LabVIEW ActiveX automation server. If you use the LabVIEW Run-Time Engine for the LabVIEW Adapter, TestStand hangs. LabVIEW 2011 fixed this behavior. |
|
| 284675 | The LabVIEW Adapter ignores the code and message fields of an error out parameter of a substep when the occurred field is set to False | If a substep module modifies the code and message fields within the Step.Result.Error error container for a step but the occurred field is set to False, the changes do not persist. This behavior does not occur when you make a similar change for the code module of the step. |
|
| 290616 | The LabVIEW Adapter might exhibit unexpected edit-time issues if the most recent installation of LabVIEW is a version TestStand no longer supports | If the most recent version of LabVIEW you install is a version that TestStand does not support, such as installing LabVIEW 7.1.1 and using TestStand 2010, you might encounter unexpected edit-time issues when you create or modify LabVIEW steps in TestStand. | |
| 290991 | When you use LabVIEW or .NET code modules, the additional results feature does not log all elements | When you select to include an array output parameter of a code module as an additional result, TestStand might not log some elements of the array under the following conditions:
|
|
| 290994 | TestStand does not include LabVIEW code module parameters with the Default option enabled in additional results | When you call a LabVIEW code module, TestStand does not log any top-level input parameter you select to include as an additional result when you also enable the Default option in the Parameters Table. | |
| 307558 | Timestamps returned from a LabVIEW code module might specify incorrect values | If a timestamp returned from a LabVIEW code module is noon (12:00:00 PM) or midnight (12:00:00 AM), TestStand stores the values as 00:00:00 PM and 00:00:00 AM, respectively. | |
| 310030 | Passing a binary string to TestStand from a LabVIEW code module results in different behavior based on the configuration of the LabVIEW Adapter | When you pass a binary string to TestStand from a LabVIEW code module, TestStand stores the string differently depending on whether you execute the code module in the LabVIEW Development Environment or in the LabVIEW Run-Time Engine (RTE). TestStand uses the correct binary representation for the string when you execute the code module with the LabVIEW RTE but uses the incorrect ASCII representation for the string when you execute the code module with the LabVIEW Development Environment. | |
| 310671 | Unable to load a LabVIEW .NET interop assembly when TestStand loads the .NET CLR 4.0 | When you call a LabVIEW-built assembly from an application targeted to the .NET Common Language Runtime (CLR) 4.0, the assembly fails to load and returns the Failed to call init lv client function error. This error occurs because of a change in the .NET CLR 4.0 in which the LoadLibrary function, defined in kernel32.dll, is not called when loading an assembly. LabVIEW 2012 fixed this behavior. |
|
| 316995 | TestStand hangs when executing a VI that uses shared variables and when you configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine | TestStand hangs when executing a VI that uses shared variables and when you configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine (RTE). This issue occurs only under the following conditions:
|
|
| 317305 | LabVIEW code modules with an input parameter with a default value of INF or NaN can cause a module load error | LabVIEW code modules with an input parameter with a default value of INF or NaN can cause a module load error. This behavior only occurs with TestStand 2010 SP1 and LabVIEW 2011 or later. | |
| 341219 | You cannot use a Wait step to access the results for a Run VI Asynchronously step | When you use a Run VI Asynchronously step to call a VI, you can configure a Wait step later in the sequence to wait until the asynchronous VI has completed. However, the results from the VI do not populate in the Wait step as expected. | |
| 41665 | 4DQCFCB8 | LabVIEW 8.5 or later returns a warning when you load the LabVIEW Simple User Interface example | When you load the LabVIEW Simple User Interface example using LabVIEW 8.5 or later, LabVIEW returns a warning that indicates that LabVIEW changed a constant wired to a Case structure to maintain compatibility with LabVIEW 7.1 or earlier. |
.NET Adapter
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 290991 | When you use LabVIEW or .NET code modules, the additional results feature does not log all elements | When you select to include an array output parameter of a code module as an additional result, TestStand might not log some elements of the array under the following conditions:
|
|
| 298630 | The .NET Adapter does not display static methods an inherited class defines | When you define a derived class in a .NET assembly that inherits from a base class, the base class contains a static function, and you use the .NET Adapter to select the derived class, the .NET Adapter does not show the inherited static method. | |
| 322670 | .NET steps might encounter a deadlock when the constructor uses the TestStand API in a parameter expression | Executing a .NET step might cause a deadlock under the following conditions:
|
|
| 334136 | TestStand does not release .NET object references you pass as parameters to new executions until the execution is destroyed | TestStand does not release .NET object references you pass as parameters to new executions until the execution completes. This behavior causes the .NET assembly to remain loaded if any such executions remain open, even if you select File»Unload All Modules to unload all modules. |
TestStand File Diff/Merge Application
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 253897 | Closing multiple TestStand File Diff/Merge application instances on Windows 7 with the Close All Windows taskbar option sometimes results in an error | Closing multiple TestStand File Diff/Merge application instances on Windows 7 with the Close All Windows taskbar option might cause the following error: Error writing to file '<TestStand Application Directory>\Cfg\FileDiffer.ini'. |
|
| 299368 | The TestStand File/Diff Merge application does not support diffing station global variables | The TestStand File/Diff Merge application does not support diffing station global variables and instead returns a Value invalid or out of range error. |
Reports
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 242364 | TestStand incorrectly formats the report for a post action of a step that calls a sequence | When you enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box and an execution calls a sequence as a post action for a step, TestStand incorrectly formats the report. | |
| 244953 | TestStand incorrectly formats reports when Sequence Call steps loop and you enable the On-The-Fly Reporting option | When you configure multiple Sequence Call steps to loop, disable the Record Result of Each Iteration option on the Looping panel of the Step Settings pane, and enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box, the report displays the first Sequence Call step with a status of Running and displays all the steps the sequence executes under the first sequence. | |
| 250975 | The XML report header incorrectly displays Test Socket Index for sequential execution when you set the Numeric Format report option to Hexadecimal, Octal, or Binary | The XML report header incorrectly displays Test Socket Index for sequential execution when you set the Numeric Format report option to Hexadecimal, Octal, or Binary. | |
| 301515 | On-the-fly reports do not contain a failure chain section | Reports that you generate on-the-fly do not contain details about the steps in the failure chain. | |
| 305551 | Question mark characters appear in ATML reports instead of indentation spaces when you use the TR_horizontal.xsl style sheet | Question mark characters appear in ATML reports instead of indentation spaces when you use the TR_horizontal.xsl style sheet. This issue occurs only under the following conditions:
|
|
| 316633 | The Expand/Collapse All Loop Indices button does not function for XML reports that use the report.xsl style sheet | The Expand/Collapse All Loop Indices button does not function for XML reports that use the report.xsl style sheet. This button exists only when you configure a step in the sequence to loop. In this case, you might also encounter an Object expected error when clicking the button in Microsoft Internet Explorer. |
|
| 357253 | Results do not display in an ATML report for a post action of a step that calls a sequence | When all of the following conditions are true, a report does not display results:
|
|
| 35009 | 47FEKD00 | On-the-fly reporting leaks memory when an execution repeatedly creates new threads | Generating a report on-the-fly slowly leaks memory when executions repeatedly use a Sequence Call step to create new threads. |
| 35106 | 47FE0BG0 | Incorrect indentation might occur when you generate a report on-the-fly | When you enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box to generate a report on-the-fly, the report incorrectly indents step results that follow a Sequence Call step that creates a new thread. |
| 41730 | 4DQDAQYL | Generating reports on-the-fly with asynchronous threads might cause an error | When you enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box to generate a report on-the-fly, TestStand returns a run-time error when the asynchronous thread continues to execute after the process model entry point completes. |
| 43782 | 4GGCQA00 | Module execution times are not included in an XML report | TestStand XML reports that use the horizontal style sheet do not reflect the setting of the Include Execution Times option on the Contents tab of the Report Options dialog box. |
| 46782 | 314DQ9MT | TestStand does not call the ModifyReportHeader and ModifyReportFooter callbacks when you generate reports on-the-fly | When you enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box to generate a report on-the-fly, TestStand does not call the ModifyReportHeader and ModifyReportFooter callbacks because the ProcessOTFStepResult sequence in the report generation sequences does not call these callbacks. Note: This issue has been fixed only in the TestStand 2012 process models. |
Database Logging
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 341273 | On-the-fly database logging might return an error when you execute a sequence that uses a Sequence Call step to create a new thread that collects results | An error can occur when you use on-the-fly database logging and TestStand attempts to log the first result from a new thread that a Sequence Call step created. |
Miscellaneous
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| 302929 | The Update VI Calls tool fails when you update the Report Express VI | When you use the Update VI Calls tool to update the Report Express VI, TestStand launches a dialog box that indicates that the VI path is invalid. When you close the dialog box, the Update VI Calls tool times out. | |
| 35081 | 47DD4PIA | An incorrect prompt to reload files might appear when you use source code control | TestStand prompts you to reload files when source code control (SCC) 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 return errors for some operations when you reload the files. |
| 35172 | 482KEHIA | Selecting the Undo Check Out option from the Workspace pane context menu to revert a workspace does not prompt you to reload modified projects | If you make changes to a TestStand project in a workspace and then select Undo Check Out from the Workspace pane context menu, TestStand does not prompt you to reload modified projects within the workspace. This modified project remains in memory does not match the project on disk. |
| 37637 | 3T9BCN6I | When you select Save All after you add a file to a TestStand project, the project does not save | Adding a file to a TestStand project changes the project, and you must save the project to preserve the changes. However, when you select Save All after you add a file to a project, the project does not appear in the Save All file list. Additionally, TestStand marks the workspace as modified, even if you did not modify the workspace file. This issue can cause problems with source-code-controlled project files. TestStand requests that you check out the project file when you add a file but indicates that no changes were made to the project when checking in the changes. |
| 48066 | 3PIA7EYL | Automatically setting up a remote execution does not work for non-English Windows XP SP2 operating systems | Enabling the Allow All Users Access from Remote Machines option on the Remote Execution tab of the Station Options dialog box does not work on some non-English Windows XP SP2 operating systems, such as German Windows XP. The option 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. |
National Instruments releases critical software updates after product release using the NI Update Service. Visit ni.com/info and enter the Info Code 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 the Info Code notifications to view a list of current product notifications.
Refer to the Technical Support page at ni.com/support and search for TestStand to access the TestStand Support website, which contains online documentation, KnowledgeBase articles, tutorials, example code, discussion forums, and other resources.
Copyright
© 2000–2012 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:
Trademarks
CVI, LabVIEW, National Instruments, NI, ni.com, NI TestStand, the National Instruments corporate logo, and the Eagle logo are trademarks of National Instruments Corporation. Refer to the Trademark Information at ni.com/trademarks for other National Instruments trademarks.
The mark LabWindows is used under a license from Microsoft Corporation. Windows is a registered trademark of Microsoft Corporation in the United States and other countries.
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.