Step 2 - Capture Diagnostic Profiler diagnostic information
The second step in developing an Operator Debrief application is the correlation of the tests and measurements defined in a Diagnostic Profiler project to the logged anomaly data. To accomplish this, define the Diagnostic Profiler project to be identified. All measurements defined in the Profiler project will be listed in the Measurement column. They can then be correlated to logged data fields defined in Step 1, if optional measurement pass/fail should be determined automatically for additional Diagnostician fault isolation.NOTE: THE CORRELATION DONE HERE IS NOT FOR LOGGED DATA, BUT RATHER FOR OTHER TEST OR MEASUREMENTS CONTAINED IN THE DIAGNOSTIC KNOWLEDGE BASE. TYPICAL OPERATOR DEBRIEF APPLICATIONS DO NOT REQUIRE THIS STEP. IT IS RECOMMENDED THAT AFTER IDENTIFYING THE PROFILER PROJECT, THAT THE USER PROCEED TO STEP 3.
- Identify the Profiler project and candidate to correspond with the Operator Debrief application.
You can type in the full path and name or use the Browse function to locate the appropriate file. The
file must be a DiagInfo.000 file.
Optionally, you can define the specific "fail" criteria for this measurement as follows:
- Select a measurement that will be included in the logged data file.
- Identify which field the measurement data will be logged in.
- Identify how, in the data log, the measurement will be indicated as failed.
 | If a fail is indicated when a measured parameters falls outside a certain range, then enter the high and low values of that range. |
| If a fail is indicated by a discrete value, then enter that value. |
| If a fail is indicated by a character or text tag, then enter that tag. |
Go to Step 3