Exporting Individual Troubleshooting Procedures to DiagML
When exporting a diagnostic sequence to DiagML, there is an option that allows you to create a separate diagnostic procedure for each detection test.
On the DiagML Options dialog, you can select whether the detection test should be included in the exported test sequence, or whether the procedure should contain only the tests used for isolation.
These options do not require that the Maintenance Module be licensed. They are available whenever no functions or failure modes are proven good by any of the tests in the detection order. Cases of this include: fault detection generated in independent mode, fault detection that uses only tests based on fault templates, and fault detection that uses only asymmetric tests.
When this option is enabled, then a separate <DiagnosticProcedure> will be created for each detection test in the exported DiagML file. When the selected option indicates that detection should be omitted, then the first step in the procedure will be the first isolation test (or fault group) for that detection test.
When the selected option indicates that detection is included, then the first step in the procedure will be the detection test itself.
To support this new capability, the following changes were made to the DiagML schema:
1) Two enumerated values—“Separate” and “Omitted”—can be assigned to the <DiagnosticProcedure><Detection_Approach> element (as alternatives to the existing values “Sequence” and “Independent”). These new values correspond to the two new settings, with the detection test included or omitted, respectively.
2) An optional <DiagnosticProcedure><DetectionTest_ID> field is now used to store the Test_ID associated with a diagnostic procedure when the detection test is omitted. This field can be used to look up the corresponding <TestProcedure> or <Test> element in the <TestData> section of the exported DiagML file.
