Building a TestStand UI with Native Controls - LabVIEW NXG

TestStand 2017 Help

Edition Date: November 2017

Part Number: 370052W-01

»View Product Info

Download Help (Windows Only)
NI TestStand 2014 Help
NI TestStand 2014 SP1 Help
TestStand 2016 Help
TestStand 2016 SP1 Help
TestStand 2017 Help

Purpose

This example shows how to create a TestStand user interface using only LabVIEW NXG controls. The UI uses the TestStand UI manager controls to manage the application.

Example File Location


Open Example in LabVIEW NXG

<TestStand Public>\Examples\Modifying User Interfaces\Building a TestStand UI with Native Controls\LabVIEWNXG\TestStand UI with Native Controls.lvproject

Highlighted Features

TestStand User Interface API

Major API

Prerequisites

You must have the LabVIEW NXG Development System installed to execute this example.

How to Use This Example

Complete the following steps to review the code in this example:

  1. In TestStand UI with Native Controls.lvproject, open BasicUIwithNativeControls.gvi.
  2. Select the Initialize case. In this case, references to the manager controls and the LabVIEW controls are stored in the UI data cluster, and this application is set as the main TestStand window.
  3. Select the Register Event Callbacks case. This case specifies callback VIs that will execute when a TestStand event occurs. Refer to the in-line comments for more information.
  4. Select the Handle Events case. This case handles user interaction. Within the event cases, the GetCommand and Command.Execute methods are called to implement TestStand-specific functionality.
  5. Select the Shutdown case. This case closes all references and closes the panel.

Complete the following steps to run the example:

  1. Click Run to start the user interface.
  2. Select Open Sequence File to open a sequence file, then select Execute to run it using the first entry point in the current process model.
  3. Once the execution completes, the report file path is added to the table control. This functionality is implemented in the EndExecution event callback.

WAS THIS ARTICLE HELPFUL?

Not Helpful