ECU Multi Test Edit Tabs

Changing the Layout and Entering Data

Change the layout of the Tests table in the following ways:

• Use the buttons located to the right of the table to add, remove, or reorder tests.
• Drag column headers to reorder columns.

Enter data in the table in the following ways:

• Enter data when a cell is highlighted.
• Click in a cell when it is highlighted.
• Double-click a cell.
• Select a value from a drop-down menu.
• Drag a variable or property from the Variables pane to a text or expression cell.

Copying and Pasting Data

You can copy and paste data in the Tests table in the following ways:

• Press <Ctrl-C> to copy the contents of selected table rows, columns, or cells to the clipboard.
• Press <Ctrl-V> to insert data from the clipboard into the table starting from the top left selected cell. If the number of rows of data on the clipboard is greater than the number of tests in the Tests table, the paste command adds new tests to the step to match the clipboard data.
• You can copy data to tests on the same ECU Multi Test step, to tests on other ECU Multi Test or ECU Sequence Call steps, or to a Microsoft Excel spreadsheet.
• When you modify the data in Excel and paste it back to an ECU Multi Test step, the step returns an error if the modified data is invalid for a test.

Columns

The Tests table contains the following columns:

• Test Number—The test number. If you do not specify a test number, the step assigns the value 0. For tests that correspond to a pin in a pin group, the step sets the test number to a value that equals the sum of the test number specified for the pin group test and the zero-based index of the pin in the pin group.
• Test Name—A string that identifies or describes the test. For tests that correspond to a pin in a pin group, the step sets the test name to a string that consists of the test name specified for the pin group test concatenated with the pin name.
• Pin—The pin or pin group to test.

  When you specify a valid pin map file in the Test Program Editor, this cell contains a drop-down menu that includes the pin groups, DUT pins, and system pins the pin map defines. If the pin map file is invalid or if you do not specify a pin map file, this cell contains an editable string.

  If you specify a pin group, the Tests table inserts a test for each pin in the pin group. These inserted tests are not editable and are identical to the test that specifies a pin group, with the following exceptions:
  • The Pin column is set to the name of a pin in the pin group.
  • The Test Number column is computed by adding the test number specified for the pin group test to the zero-based index of the pin in the pin group.
  • The Test Name column is computed by appending the name of the pin in the pin group to the test name specified for the pin group test.
  Although the step does not save the inserted tests in the sequence file, at run time the step adds and performs tests identical to these inserted tests. The pin group test does not appear at run time or in log files or reports.
  Note To use a different numbering scheme for test numbers or a different naming scheme for the test name for pins in a pin group, copy the tests that were inserted for the pin group, delete the pin group test, and paste the copied tests into the Tests table. You can then edit the test numbers and test names directly.
• Published Data Id—(ECU Multi Test step) A string that identifies the measurement. This option is not available when you specify an expression in the Test Data Source cell. The published data ID string can be empty.
• Low Limit—A numeric expression that specifies the low limit. This option is available only when you select Numeric Limit in the Evaluation Type column.

  If you specify a low limit, you must also specify a high limit. Use the Evaluation Comparison Mode option on the Options tab to configure how the step evaluates the limits.

  If you do not specify a low limit and high limit, the step skips the comparison.

• High Limit—A numeric expression that specifies the high limit. This option is available only when you select Numeric Limit in the Evaluation Type column.

  If you specify a high limit, you must also specify a low limit. Use the Evaluation Comparison Mode option on the Options tab to configure how the step evaluates the limits.

  If you do not specify a low limit and high limit, the step skips the comparison.

• Scaling Factor—The scaling factor to use for the measurement and limit values. The step assumes that measurement values are in base units and that limit values are in scaled units. The Tests table displays all values in scaled units.
• Base Units—A string that specifies the base units associated with the limits and the measurement. This option is available only when you select Numeric Limit in the Evaluation Type column.
• Evaluation Type—The Numeric Limit, Pass/Fail, or None evaluation type. Use a Numeric Limit evaluation for a parametric test, and use a Pass/Fail evaluation for a functional test. Use the None evaluation type to publish data from a code module without evaluating the data.

  When you select the Pass/Fail or None evaluation type, the Low Limit, High Limit, and Base Units cells are not available.

• Test Data Source—Optional. An expression that specifies the measurement data to use for the test. When you specify an expression, the Pin and Published Data Id cells are not available.
• Export Data To—Optional. An expression that specifies a location to copy the measurement data from the test. Use this expression when you need to refer to the measurement in subsequent steps. For tests that refer to a pin group, use an array expression to copy the measurement data for each pin test to an element in the array. The step automatically adjusts the size of the array to have enough elements to contain the data for each pin in the pin group.

The following columns are available only in the Execution window for an ECU Multi Test step suspended at a breakpoint during an execution:

• Status—The status of the test.
• Data—The measurement data associated with the test.

Changing the scaling factor in the Scaling Factor column in the Tests table sets the same scaling factor for the limits and the measurement.

The ECU Multi Test step uses the scaling factors in the following ways:

• Measurement Value Scaling Factor—The steps assume the measurement values that code modules publish use base units. At run time, the steps use the measurement scaling factor to display the measurement value in scaled units in the Data column of the Tests table. The Debug Test Results Log result processing plug-in uses the measurement scaling factor to format the values and units in the Measurement Value column of the Debug Test Results Log.
• Limits Scaling Factors—The steps assume the limit values in the Low Limit and High Limit columns use scaled units. At run time, the steps use the limit scaling factors to convert the limit values to base units to compare the measurement value to the limit values. The Debug Test Results Log result processing plug-in uses the limit scaling factors to add units to the values in the Low Limit and High Limit columns of the Debug Test Results Log.

Supported Scaling Factors

The ECU Software Toolkit recognizes the following scaling factors:

The Options tab contains the following options:

• Stop Performing Tests after First Failure—When you enable this checkbox and a test fails, the ECU Multi Test does not evaluate any subsequent tests in the step and sets the remaining test results to Skip.
• Evaluation Comparison Mode—Select how the step compares limits for all tests the step specifies. This drop-down menu is available only when you specify at least one test with a low and high limit on the Tests tab.
• Test Numeric Display Format—Displays the TestStand numeric format associated with the limits and measurement data. The numeric format determines how the Tests tab displays numeric values and how the TestStand report generators display numeric values in reports. Click the Edit button to launch the Numeric Format dialog box, in which you can specify the numeric format.
• Multisite Option—Use this drop-down menu to specify how the step executes the step code module on multiple sites:
  • One thread per subsystem—Execute the code module for each subsystem in a separate thread. The ECU Multi Test step identifies subsystems by using the pin map and the pins and relays shown in PinMapContext Pins and Relays.
  • One thread only—Execute the code module for all sites in a single thread.
  • One thread per site—Execute the code module for each site in a separate thread. Use this option only when the code module does not use hardware shared among multiple sites.
  Note

  • ECU Software Toolkit does not synchronize executions when you use the Parallel process model
  • ECU Multi Test steps in the ProcessSetup and ProcessCleanup sequences always execute as if you specified One thread only in the Multisite Option drop-down menu.
• Multisite Execution Diagram—When you associate a pin map file with the sequence file, this diagram shows the threads the step uses to execute code modules when executing with the Batch process model using multiple sites. Each rectangle represents a single thread. The numbers within the rectangle represent the sites tested in the same thread. Each thread corresponds to one of the test socket threads. The step determines which test socket thread executes the code module at run time. This diagram is available only when you chose Select Manually from the Specify Pins and Relays drop-down menu.
• Specify Pins and Relays—Specifies which pins and relays are included in the PinMapContext. Specify pins and relays manually or by using an expression.
• PinMapContext Pins and Relays—Shows the list of pins and relays or specifies the expression that determines the pins and relays that the PinMapContext object contains at run time. By default, the PinMapContext object contains all DUT pins in the pin map file and no system pins. If your code module uses any system pins, you must manually select the Include System Pins checkbox or include the system pins in your expression. Code modules that use system pins execute in one thread for all sites. By default, the PinMapContext object contains no relays. If your code module uses any system relays, you must manually select the Include System Relays checkbox or include the system relays in your expression. If your code module uses site relays, you must manually select the Specify Site Relays checkbox and specify the relays or include the site relays in your expression. To specify the pins and relays manually, choose Select Manually from the Specify Pins and Relays drop-down menu and enable the options you want.
  • Include System Pins—Include all system pins.
  • Specify DUT Pins—Select the DUT pins or pin groups you want to include. When you select a pin group, the tab dims the DUT pins that belong to the pin group.
  • Include System Relays—Include all system relays.
  • Specify Site Relays—Select the relays, relay groups, or relay configurations you want to include. When you select a relay group or relay configuration, the tab dims the relays that belong to the relay group or configuration.
  Note If you choose One thread only or One thread per site in the Multisite Option drop-down menu, all pins and relays are included in the PinMapContext and the checkboxes are disabled.
  To specify the pins and relays using an expression, select Use Expression from the Specify Pins and Relays drop-down menu. At run time, the expression you use must evaluate to an array of DUT and system pin names, and site and system relay names.
  Note The PinMapContext object for steps in the ProcessSetup and ProcessCleanup sequences always contains all DUT and system pins and all site and system relays.