Getting Started With ECU Toolkit
- 更新日2023-02-17
- 7分で読める
Getting Started With ECU Toolkit
This example demonstrates several features of the ECU Software Toolkit in a test program that takes common measurements with the ECU Toolkit Measurement Control step types to test a simulated ECU. This example can serve as a starting point for your test programs.
This example can be located at <TestStand Public>\Examples\NI_ECUToolkit\Getting Started with ECU Toolkit.seq.
Highlighted Features
- Pin map
- Multisites
- Limits files
- Virtual pins
Prerequisites
Pin Map
button on the ECU Software
Toolkit toolbar to open the Getting Started with ECU
Toolkit pin map file in the Pin Map Editor. The pin map file defines
the following information:- Four NI Switch Executive virtual devices named
J5_MATRIX_VD, J7_MATRIX_VD,
J12-FIU-1-VD, and J12-FIU-2-VD.
- J5_MATRIX_VD is created with a Matrix Switch named J5_MATRIX, which is used to build the connections between the instrument channels and DUT pins on Site 0.
- J7_MATRIX_VD is created with a Matrix Switch named J7_MATRIX, which is used to build the connections between the instrument channels and DUT pins on Site 1.
- J12-FIU-1-VD is created with an SLSC FIU device named J12-FIU-1, which is used to build the connection between the J24_PPS_1 channel and the DUT pin LOAD on Site 0.
- J12-FIU-2-VD is created with an SLSC FIU device named J12-FIU-2, which is used to build the connection between the J24_PPS_2 channel and the DUT pin LOAD on Site 1.
- Two NI-DCPower instruments named J18_SMU and
J20_SMU.Note These instruments belong to two different groups, so they can be controlled by different NI-DCPower sessions. Each site has an independent NI-DCPower instrument.
- J18_SMU can be connected to the DUT pins on Site 0 using J5_MATRIX_VD.
- J20_SMU can be connected to the DUT pins on Site 1 using J7_MATRIX_VD.
- One NI-DMM instrument named J5_DMM which is shared across
two sites.
- J5_DMM can be connected to the DUT pins on Site 0 through J5_MATRIX_VD, and connected to the DUT pins on Site 1 through J7_MATRIX_VD.
- Two NI-SCOPE instruments named J22_SCOPE_1 and
J22_SCOPE_2.Note These instruments belong to two different groups, so they can be controlled by different NI-SCOPE sessions. Each site has an independent NI-SCOPE instrument.
- J22_SCOPE_1 can be connected to the DUT pins on Site 0 using J5_MATRIX_VD.
- J22_SCOPE_2 can be connected to the DUT pins on Site 1 using J7_MATRIX_VD.
- Four NI-RMX power supplies named J24_PPS_1,
J24_PPS_2, J24_PPS_3, and
J24_PPS_4.
- J24_PPS_3 is connected directly to the DUT pin POWER on Site 0.
- J24_PPS_4 is connected directly to the DUT pin POWER on Site 1.
- Eleven DUT pins named POWER, A_SMU,
A_DMM, B, C,
D, E_SMU,
E_SCOPE, F_SMU,
F_SCOPE, and LOAD are defined in
the pin map.
- The defined DUT pins A_SMU and A_DMM are virtual pins that refer to a single physical DUT pin A. They are used to build connections between the physical DUT pin A and NI-DCPower or NI-DMM instruments using Switch Executive devices.
- The defined DUT pins E_SMU and E_SCOPE are virtual pins that refer to a single physical DUT pin E. They are used to build connections between the physical DUT pin E and NI-DCPower or NI-SCOPE instruments using Switch Executive devices.
- The defined DUT pins F_SMU and F_SCOPE are virtual pins that refer to a single physical DUT pin F. They are used to build connections between the physical DUT pin F and NI-DCPower or NI-SCOPE instruments using Switch Executive devices.
- Two pin groups named AnalogPins and DigitalPins.
- Two sites on the tester.
- A series of connections for each site. Each connection specifies a DUT pin,
a site number, an instrument, and an instrument channel. There are two types
of connections in this pin map file:
- Connection—A connection between a DUT pin and an instrument channel on one or more sites.
- Switch Executive Connection—A switched connection between a DUT pin and an instrument channel for one site through a Switch Executive virtual device. You must specify a Switch Executive virtual device for Switch Executive Connections.
Test Program Configurations
- Select or click the Edit Test Program
button on the ECU
Software Toolkit toolbar. - Select the Configuration panel to review the test program configuration.
MainSequence, ProcessSetup, and ProcessCleanup Sequences
- On the Sequences pane, select the
MainSequence sequence and review the objectives each
step performs. You can also review the low-level sequence called by each
step. The module adapter for each step listed below is configured as
Sequence:
- The Pin Impedance Test step runs a pin impedance test on all pins in the AnalogPins and DigitalPins pin groups. This step is an instance of the ECU Multi Test step type.
- The Power On ECU step turns on power to the DUT. This step is an instance of the ECU Action step type.
- The Pin A 5V Check step verifies that the output voltage on DUT pin A is 5V. This step is an instance of the ECU Multi Test step type.
- The Pin LOAD Current Check step tests the current value on the path from an RMX-410x power supply and DUT pin LOAD. This step is an instance of the ECU Multi Test step type.
- The Pin E and F Signal Check step tests the amplitude, frequency, and crosspoint voltage characteristics of the signals on DUT pins E and F. This step is an instance of the ECU Multi Test step type.
- The Power Off ECU step turns off power to the DUT. This step is an instance of the ECU Action step type.
- On the Sequences pane, select the ProcessSetup sequence. TestStand calls this sequence once before starting testing. The steps in this sequence initialize the instruments and store the instrument sessions in the Pin Map Context object.
- On the Sequences pane, select the ProcessCleanup sequence. TestStand calls this sequence once after testing completes. The steps in this sequence close instrument sessions and reset the instruments.
External Limits File
Use a text editor or spreadsheet software to open and review the test limits file for the Production configuration of this test program, located at <TestStand Public>\Examples\NI_ECUToolkit\Getting Started with ECU Toolkit\ProductionLimits.txt. The test limits file is loaded at run time based on the current test configuration, and specifies the values to use to evaluate whether a measurement passes or fails. The test program stores the limits loaded from the test limits file with the results.
Switch Executive Virtual Device Configuration Files
Use a text editor or spreadsheet software to open and review the virtual device configuration files located in the <TestStand Public>\Examples\NI_ECUToolkit\Getting Started with ECU Toolkit\Switch Executive Virtual Device Configuration folder. There are four files in this folder, which correspond to the NI Switch Executive virtual devices J5_MATRIX_VD, J7_MATRIX_VD, J12-FIU-1-VD, and J12-FIU-2-VD. These files contain the defined alias for the Channel IVI name, as well as route and route group information. The route and route group names used in this test program follow the recommended naming scheme.
InstrumentStudio Files
- Select or click the Edit Test Program
button on the ECU Software Toolkit toolbar. - Select the InstrumentStudio Project panel to see the specified InstrumentStudio project file name and path.
- Select or click the Launch InstrumentStudio
button on the ECU
Software Toolkit toolbar to open the specified InstrumentStudio
project file. - See that the Getting Started with ECU Toolkit.instudioproj file includes the Getting Started with ECU Toolkit.pinmap and Getting Started with ECU Toolkit.sfp files.
- Double-click Getting Started with ECU Toolkit.sfp to see the soft front panels. The layout in this file consists of one large Oscilloscope panel, one small SMU/Power Supply panel, one small Digital Multimeter panel, and two small RMX Power Supply panels. You can review the device configuration from these soft front panels.
- Use a text editor to open and review the measurement configuration file exported from InstrumentStudio, located at <TestStand Public>\Examples\NI_ECUToolkit\Getting Started with ECU Toolkit\GettingStartedWithECUToolkit.measconfig. The measurement configuration file is used by the Apply Pin Configuration step and Scope - Read Measurements step.