USER INTERFACE HELP

ABOUT THE IMPERIAL TEST EXECUTIVE

The Imperial Test Executive is an exceptional add on package for developing & executing test programs in the LabVIEW environment. The test programs the Test Executive runs are LabVIEW VI's. The Imperial software provides the following features:

Provides a first class platform for executing LabVIEW VI's or LabView executable.

Allows operator to run individual, group of tests, or all tests. Individual Test can be run by simply clicking on the test in the menu. Group of tests can be run by pressing the 'Ctrl' key and selecting the tests to be run from the test menu.

Complete Data Logging and storage to a database file with utilities (F12 key) to view, sort, and create reports on past data.

User Programmable menu buttons to execute LabVIEW VI's.

Looping for all tests, single tests or group of tests.

Three operating modes, (Operator, Technician, Engineering).

Print options Automatic Pass Fail Ticket, Full Data Log, Failures only, On Failures Only, Manual Print, No Printer, No Cover Sheet, and Change Font.

Password Protection for each user with for modes, Operator, Technician, Engineering, and Manager.

Test Information window, Provides test descriptions through testing cycle.

Utilities that come with the Test Executive.

By using the Imperial Test Executive Software to develop your test programs, your LabVIEW VI's can be developed separately, away from the Test Executive, or if you currently have the Test Executive running, you can minimize the Test Executive (Engineering mode only) and debug your VI's simultaneously. Just simply drop in an one of the Imperial Test Executive VI's, wire up the data and let the Test Executive do all the work for you! A Status box is provided to keep the user informed of what is going on during the whole test execution.

INSTALLATION

Before you install: The Imperial Test Executive comes on CD ROM or Floppy Disk. Installing the Test Executive requires approximately 4.0MB. Some virus detection programs may interfere with the installer program. Check the distribution disks for viruses before you begin installation. Then, turn off the automatic virus checker and run the installer. After installation, check your hard disk for viruses again and turn on the virus checker.

INSTALLING UNDER WINDOWS

You can install the Test Executive from the Windows File Manager, or with the Run. command from the File menu of the Program Manager.

1. Insert the first Test Executive disk into the disk drive and run the SETUP.EXE using one of the following two methods.
a) From Windows, select Run... from the File menu of the Program Manager. A dialog box appears. Type X:\ SETUP (where X is the proper drive designation).
b) From Windows, launch the File Manager. Click on the drive icon that contains the installation disk. Find SETUP.EXE in the list of files on that disk and double click on it.

2. After you choose an installation option, follow the instructions that appear on the screen.

LAUNCHING THE TEST EXECUTIVE

To launch the Imperial Test Executive simply select the icon from the Imperial Test Executive Program Group. You will be prompted to select the appropriate path for the .TES file. This file is the actual link to the UUT specific test program, and must have been correctly developed using the .TES Editor supplied with the Imperial Test Executive. Once This file is selected you will be asked to login to the Test Exec. Enter the information requested in the default format shown (note: the syntax must match the .TES file exactly!).

RUNTIME ENVIRONMENT

This is the main user interface screen. All test selections, run options and environment preferences are set here. The tests can be individually chosen from the test selection window. Test descriptions will be displayed in the Test Information window, all test data will be displayed in the data logging grid. There are also 12 function keys below the grid and their functionality will be described later in this document.

Figure 1

Test List box:
This window displays all of the tests for testing the UUT. You may select individual tests by using the Cntrl key and highlighting the specific test. You may also use the Shift key to select Groups of Tests.
Test Information box:
This window is used by the Test Programmer to display information to the operator during execution of the test.
Data Logging box:
This window will display all data logging postings as the test is executed. By highlighting a specific test in the Test List Box, you will see the most recent data logging information in the Data Logging Box.

Soft Key Descriptions

Test Hardware Configuration

After successfully logging on a dialog box will be displayed with Test Station and Test Fixture choices. These values are user programmable and are imported from the 'equipment.txt' file located under the 'imperial/labview' directory. The file must be formatted as shown:

Test Station 1, Test Fixture 1
Test Station 2, Test Fixture 2

Figure 2

Login/Work Ticket

The login work ticket is where the information about the currently tested product is setup. This information is logged to the database with all the test data and is available for future reporting. These fields are also customizable and can be designated by modifing the text file named "login.txt" under the imperial/labview dirctory.(note if you are using Visual Basic or CVI, this file will be under the appropriate environment folder. . It must be formated with each line item on a single line, as shown below:

Tag #
Assy. Dwg. Rev.
Traveler #

Figure 3

(F1) RUN ALL:
Selecting F1 or Run will run all of the tests from the test selection window.

(F2) RUN:
Selecting F2 or Run will run the currently highlighted test from the test selection window. If multiple tests are highlighted it will run each of the tests.

(F3) Loop:
Selecting F3 will display the loop count selection window then it will loop the currently selected tests in the test selection window

(F4) Loop All

More text goes here:
This function will loop all the tests

Figure 4

(F5)(F6) & (F7)
Programmable buttons, function specified in TES file. This functionality allows the programmer the ability to customize the Imperial Test Executive environment and provide unique tasks to these 3 keys.

(F8) CHANGE SETTINGS

The Change Settings[F8] key is used to modify the Runtime Settings & Print Modes. This mode also allows you to change from three different modes, Operator, Technician, and Engineering.

Figure 5

Test Modes

There are three test modes in the Imperial Test Executive. You may set any of the following test modes, and you are also given the ability to turn on or off the diagnostics.

Test Mode:
1. End to End (default).
2. Pause on Failure.
3. Stop on Failure.

Diagnostic Mode:
1. Off (default)
2. On

Printer Data Log Configuration

This window allows the user to setup the printing options for the test executive. You can disable printing if there is no printer available. Or you may chose the type of data you would like diplayed on your pass or fail ticket. The software can be setup to print on every run, or can be set to 'manual print' which would mean the operator would have to hit the print button (F10) after each run. Enabling Cover Pages and setting up lines per page are some of the other features that can be modified in this window.

Figure 6

Printer Setup

If you select the change font option you will be given the choice to select fonts and font sizes for your printer:

Figure 7

User Modes

There are four modes of users. They can be set in the 'Change Settings' Window and are Operator, Manager, Technician & Engineering

Operator Mode:

In the Operator Mode the operator may execute all of the options of the Runtime window with as well as set the following settings:

Manager Mode:

In the Manager Mode you may modify following settings, and by selecting the Default Key, it will save the current setups as the default mode. Note: this actually modifies the TES file for this Test Program, so selecting the Default Key will effect all future executions of this TPS. The engineer can click on the Information Window Label to Icon the Test Executive.When the engineer selects 'F12' in the runtime window the runtime window will be iconed and a utility option window will open. There are two sections of this window. The top section sets up the information for storing QMS (Quality Management Software) data and identifying where and what tester this test executive is running on. The QMS data is sent to the directory specified after each test run.
The bottom section is the option to view the data logged on station. This option actual launches a utility called report. Report allows the engineer to view data in a number of different ways, and to print or save to file reports on the testers data.

Technician Mode:

In the Technician Mode the technician may execute all of the options of the Runtime window, as well as the following settings:

Engineering Mode:

In the Engineering Mode you may modify following settings, and by selecting the Default Key, it will save the current setups as the default mode. Note: this actually modifies the TES file for this Test Program, so selecting the Default Key will effect all future executions of this TPS. The engineer can click on the Information Window Label to Icon the Test Executive. When the engineer selects f12 in the runtime window the runtime window will be iconed and a utility option window will open. There are two sections of this window. The top section sets up the information for storing QMS (Quality Managment Software) data and identifying where and what tester this test executive is running on. The QMS data is sent to the directory specified after each test run.

Print Options

If you have selected 'Manual Print' in the 'Print Data Log Configuration' under the 'Change Settings Window. You will be prompted after hitting the Manual Print key (F10) to pick the type of data log ticket you would like printed.

Figure 8

Change Password

This screen allows a person with managment privileges to add login names, assign security levels and setup passwords for all users of the test executive. This window also allows the manager to edit or delete existing users.

Figure 9

(F9) Diagnosed Parts

Parts that have been identified in a suspected parts list, will be diplayed here. They are listed in order of most suspect to least suspect. Users can use this feature to help in troublshooting.

Figure 10

(F10) Utility Options

Selecting this option allows the operator to chose either the Comment Log Utility or the Report Generator

Figure 11

Comment Log

The Comment Log Utility will allow the user to log comments about particular tests stations, Fixtures and Programs to a Microsoft Access Database. You can also go back and view previous comments that have been saved. This path to the database is stored in the root directory under a file 'C:\Imperialcmts.txt'

Figure 12

Report Generation

The report generator will create Crystal Reports that display all test data and statistics. All modes of sorting,filtering & date selection have been implemented and databases are dynamically chosen by the user so multiple databases can be used. Outputs can also be chosen, allowing the user to direct the output to a printer, file or the window.

Figure 13

ADVANCED HELP

PRINT ALL

EXIT HELP