tyx corporation page 1 © copyright tyx corporation 2006 tyx testbase development of diagnostics...

TYX CORPORATIONTYX CORPORATION

© Copyright TYX Corporation 2006

TYX TestBaseTYX TestBase

Development of Diagnostics with Development of Diagnostics with

DSI DSI eXpresseXpress and TYX TestBase and TYX TestBase

For For eXpresseXpress versions 5.10.x. versions 5.10.x.

DSI eXpress User Group MeetingSept 22, 2006Presented by: Brian LennoxWestern Regional Sales Manager TYX CorporationT: 661-296-1451E-Mail: [email protected]


© Copyright TYX CORPORATION 2006

DSI DSI eXpresseXpress

Model-Based Diagnostics Engineering and System Model-Based Diagnostics Engineering and System

Governing toolGoverning tool Provides an object-oriented approach to full-system designProvides an object-oriented approach to full-system design Supports analysis and optimization throughout all phases of Supports analysis and optimization throughout all phases of

developmentdevelopment

FunctionalityFunctionality Development of dependency modelsDevelopment of dependency models Modeling of system test strategiesModeling of system test strategies Diagnostic analysis (fault detection and fault isolation)Diagnostic analysis (fault detection and fault isolation) Failure Mode Effects and Criticality Assessment (FMECA)Failure Mode Effects and Criticality Assessment (FMECA)



TYX TestBaseTYX TestBase

Test ExecutiveTest Executive Open architecture enables integration betweenOpen architecture enables integration between

Diagnostic development toolsDiagnostic development tools Test languages and environmentsTest languages and environments User interface modulesUser interface modules Storage of test resultsStorage of test results

FunctionalityFunctionality Visual development of test strategies Visual development of test strategies Import of test strategies from third-party toolsImport of test strategies from third-party tools Execution of test strategies using third-party test environmentsExecution of test strategies using third-party test environments Collection of test resultsCollection of test results Statistical analysis of test resultsStatistical analysis of test results



eXpresseXpress – TestBase Integration – TestBase Integration

Integrated “Design-to-Test” ProcessIntegrated “Design-to-Test” Process

Test Strategy Execution

Diagnostic Model

Development

SystemDesign

TestBase

eXpress

Third-party software

Diagnostic Analysis,FMECA

Test Strategy Development

Test Results Collection

Test Results Analysis

System Designers

Diagnostic Developers

Test Developers

Operator / User

System Under Test



eXpresseXpress – TestBase Integration… – TestBase Integration…

Integration ArchitectureIntegration Architecture

TestBase

eXpress

DiagML

eXpress Model File

Test Results

Database

SystemUnder Test

Test Environments

Available/Evolving Design Data

TestBase Database

TestBase

Data storage

Third-party software

TestBaseReports

Data AnalysisSoftware

eXpress

eXpress Import/Export mechanisms



eXpresseXpress – TestBase Integration… – TestBase Integration…

DiagML:DiagML: ““Diagnostic Modeling Language”Diagnostic Modeling Language” Based on XMLBased on XML Developed by a consortium of companies as an open specificationDeveloped by a consortium of companies as an open specification After a trial period, open to membership by other companiesAfter a trial period, open to membership by other companies BenefitsBenefits

Explicit extensibilityExplicit extensibility ParsabilityParsability TransformabilityTransformability Wide industry acceptanceWide industry acceptance Human readableHuman readable

Details at Details at http://www.diag-ml.comhttp://www.diag-ml.com



Integrated Diagnostic Development Integrated Diagnostic Development

1. 1. Build Diagnostic ModelBuild Diagnostic Model



Integrated Diagnostic Development…Integrated Diagnostic Development…

2. 2. Build Test SetBuild Test Set




2. 2. Build Test Set (cont’d)Build Test Set (cont’d)




3. 3. Generate Diagnostic StrategyGenerate Diagnostic Strategy




3. 3. Generate Diagnostic Strategy (cont’d)Generate Diagnostic Strategy (cont’d)




3. Generate Diagnostic Strategy (cont’d)3. Generate Diagnostic Strategy (cont’d)




4. 4. Import Diagnostic Strategy in TestBaseImport Diagnostic Strategy in TestBase




5. 5. Develop TestBase Test ProceduresDevelop TestBase Test Procedures One TestBase test procedure for each Test defined in One TestBase test procedure for each Test defined in eXpresseXpress

Implementation must be consistent with the characterization of the test procedure, Implementation must be consistent with the characterization of the test procedure,

in the Test Database where DiagML was imported.in the Test Database where DiagML was imported. Property “Adapter ProgID” indicates the test language/environment to be usedProperty “Adapter ProgID” indicates the test language/environment to be used Property “Locator” indicates the location of the test procedure code (ex. DLL name and Property “Locator” indicates the location of the test procedure code (ex. DLL name and

function name)function name) Input parameter “TestPoint” indicates the location of the measurement; use for switching Input parameter “TestPoint” indicates the location of the measurement; use for switching

(if applicable)(if applicable) All other input parameters originate from All other input parameters originate from eXpresseXpress Test attributes; implement as designed Test attributes; implement as designed

Recommended: for test procedures that have identical functionality but different parameter Recommended: for test procedures that have identical functionality but different parameter

values and/or test point, delegate to a unique underlying functionvalues and/or test point, delegate to a unique underlying function

The special test procedure “DisplayMaintenanceAction” The special test procedure “DisplayMaintenanceAction” Displays or implements the required maintenance actionDisplays or implements the required maintenance action




6. 6. Execute Test StrategyExecute Test Strategy Move TestBase databases to production or embedded environmentMove TestBase databases to production or embedded environment Configure run-time optionsConfigure run-time options

Assign MTI database, for collection of test resultsAssign MTI database, for collection of test results

Execute test strategyExecute test strategy Execution reports/remediates “diagnosed faults”; to enable statistical Execution reports/remediates “diagnosed faults”; to enable statistical

assessment of diagnostic performance, enter the “actual faults” in the MTI assessment of diagnostic performance, enter the “actual faults” in the MTI

Database (ex. via the MTI Database GUI)Database (ex. via the MTI Database GUI)

Evaluate diagnostic performanceEvaluate diagnostic performance Performed off-line, after a sufficient amount of test results was accumulatedPerformed off-line, after a sufficient amount of test results was accumulated Generate statistic reports from MTI Database GUI (new feature in TestBase 2.6)Generate statistic reports from MTI Database GUI (new feature in TestBase 2.6) Use third-party software to retrieve and process test results from the MTI Use third-party software to retrieve and process test results from the MTI

databasedatabase



Integrated Diagnostic Development…Integrated Diagnostic Development…Mapping of Design EntitiesMapping of Design Entities

eXpresseXpress TestBaseTestBase

Diagnostic strategyDiagnostic strategy Set of test procedures, in a Test DatabaseSet of test procedures, in a Test DatabaseTest strategy with one/more diagnostic procedures, in a Diagnostic DatabaseTest strategy with one/more diagnostic procedures, in a Diagnostic Database

Test nodeTest node Test procedureTest procedure““Test” block in the diagnostic procedureTest” block in the diagnostic procedure

Test LocationTest Location Test procedure input parameter “TestPoint”Test procedure input parameter “TestPoint”Test input parameter valueTest input parameter value

Test attribute Test attribute

“ExecutionEnvironment”“ExecutionEnvironment”

Test procedure property “Execution Environment” (i.e., Adapter ProgID)Test procedure property “Execution Environment” (i.e., Adapter ProgID)

Test attribute “Locator”Test attribute “Locator” Test procedure property “Locator” (ex. DLL name, function name)Test procedure property “Locator” (ex. DLL name, function name)

Other test attributesOther test attributes Test procedure input parameterTest procedure input parameterTest input parameter valueTest input parameter value

Fault Group nodeFault Group node Test procedure “DisplayMaintenanceAction”Test procedure “DisplayMaintenanceAction”““Test” blockTest” block““End” blockEnd” block

Fault Group objectsFault Group objects Value of input parameter “MaintenanceAction” of “Test” blockValue of input parameter “MaintenanceAction” of “Test” blockDiagnostic procedure outcome assigned to “End” blockDiagnostic procedure outcome assigned to “End” block




eXpresseXpress Design Rules Design Rules Tests shall have only one LocationTests shall have only one Location Each test shall have the following attributes:Each test shall have the following attributes:

““ExecutionEnvironment” – indicates the test language/environment to be used ExecutionEnvironment” – indicates the test language/environment to be used

for executionfor execution ““Locator” – indicates the location of the test procedure codeLocator” – indicates the location of the test procedure code

Tests shall not have attributes named “TestPoint”Tests shall not have attributes named “TestPoint”




TestBase Design RulesTestBase Design Rules Test procedures implementingTest procedures implementing eXpress eXpress Tests Tests

All test procedures shall support the input parameter “TestPoint” and use it to All test procedures shall support the input parameter “TestPoint” and use it to

determine the location of the measurementdetermine the location of the measurement All test procedures shall support input parameters corresponding to the Test All test procedures shall support input parameters corresponding to the Test

attributes defined in attributes defined in eXpresseXpress (excepting attributes “ExecutionEnvironment” and (excepting attributes “ExecutionEnvironment” and

“Locator”)“Locator”) All test procedures shall support the Outcome values “PASS” and “FAIL”All test procedures shall support the Outcome values “PASS” and “FAIL”

Special test procedure “DisplayMaintenanceAction”Special test procedure “DisplayMaintenanceAction” Shall support the input parameter “MaintenanceAction”, of type stringShall support the input parameter “MaintenanceAction”, of type string May display the string to the user, or may implement a remediation action (if May display the string to the user, or may implement a remediation action (if

applicable)applicable) Is not required to return an Outcome valueIs not required to return an Outcome value A default implementation is available in <TestBase installation directory>\Samples\A default implementation is available in <TestBase installation directory>\Samples\

TPs\CVI\Demo_CVI\Demo_CVI.prjTPs\CVI\Demo_CVI\Demo_CVI.prj



ExampleExample

Fault IsolationFault Isolation eXpresseXpress model: <TestBase installation directory>\Samples\Importers\DiagML\ model: <TestBase installation directory>\Samples\Importers\DiagML\

Demo UUT.exdDemo UUT.exd Test strategy in DiagML format: <TestBase installation directory>\Samples\Test strategy in DiagML format: <TestBase installation directory>\Samples\

Importers\DiagML\Demo UUT.xmlImporters\DiagML\Demo UUT.xml Test strategy imported in TestBase:Test strategy imported in TestBase:

Test Database: <TestBase installation directory>\Samples\Projects\Test Database: <TestBase installation directory>\Samples\Projects\

DemoTPs.ttdDemoTPs.ttd Diagnostic Database: <TestBase installation directory>\Samples\Projects\Diagnostic Database: <TestBase installation directory>\Samples\Projects\

Demo.tddDemo.tdd UUT Model: “UUT”UUT Model: “UUT” Test Strategy: “DiagML import”Test Strategy: “DiagML import”

Test procedures (LabWindows/CVI): <TestBase installation directory>\Samples\Test procedures (LabWindows/CVI): <TestBase installation directory>\Samples\

TPs\CVI\Demo_CVI\Demo_CVI.prjTPs\CVI\Demo_CVI\Demo_CVI.prj



Future enhancementsFuture enhancements

Optimization of Export and Import, to Reduce:Optimization of Export and Import, to Reduce: The number of test proceduresThe number of test procedures The size of test strategies The size of test strategies The duration of importThe duration of import

tyx corporation page 1 © copyright tyx corporation 2006 tyx testbase development of diagnostics...

Documents