Страница 1 мировой engineering стандарты общая спецификация

8.1.7 Node Verification Procedure.
Procedure 1:
1. Create various normal operating conditions as well as fault conditions which allow on-board diagnostic
routines to execute (thus resulting in changes to the supported status bits of each supported DTC). Verify

---

25.06.2020
WORLDWIDE ENGINEERING STANDARDS General Motors Local Area Network Enhanced Diagnostic Test Mode Specification
https://translate.googleusercontent.com/translate_f
67/298
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 75 of 336
the status of each supported DTC via the ReadDiagnosticInformation ($A9) service. Continue to exercise
the component (including creating fault conditions) to allow all supported status bits for all DTCs to change
from their power on initialization value. If a device supports freeze frame or failure record data, verify that
freeze frame and or failure record data is present in the node. (Use ReadFailureRecordData ($12) service
to verify freeze frames and/or failure record data is present in the node.)
2. Send a ClearDiagnosticInformation ($04) service request and verify the positive response.
3. Wait 1 s (or the time value specified in a CTS, SSTS, or supplemental diagnostic specification referenced
by one of the preceding documents) and then read the status of DTCs with the $A9 service. Verify that the
appropriate status flags have reset.
Note: 
It is possible that some DTC algorithms may execute within the 1 s wait time described in this
procedure. This must be taken into account when verifying that the status bits reset.
Procedure 2:
1. If certain operating conditions can exist which would inhibit a diagnostic information reset, then place the
device in those conditions.
2. Use the ReadDiagnosticInformation ($A9) service to verify the status of all DTCs.
3. Send a ClearDiagnosticInformation ($04) service request, verify negative response ($7F $04 $22).
4. Use the ReadDiagnosticInformation ($A9) service to verify the status of all DTCs. Verify that the DTC
status bits have NOT been reset.
Procedure 3:
1. Use the ReadDiagnosticInformation ($A9) service to verify the status of all DTCs.
2. Send a ClearDiagnosticInformation ($04) service request with extra data bytes and verify negative
response ($7F $04 $12).
3. Use the ReadDiagnosticInformation ($A9) service to verify the status of all DTCs. Verify that the DTC
status bits have NOT been reset.
Procedure 4: 
(to be checked only if negative response code $78 is supported by the node).
1. Perform step 1 of Procedure 1, then send a ClearDiagnosticInformation ($04) service request message
and verify the $7F $04 $78 response. After receiving the final positive response, verify that the node is
capable of performing additional diagnostics by requesting a different diagnostic service and verifying the
proper response. If the ClearDiagnosticInformation positive response is sent after 1 s (or a maximum value
specified in the CTS, SSTS, or supplemental diagnostic specification referenced by the CTS or SSTS),
send a ReadDiagnosticInformation ($A9) service and verify that the status of each DTC has been reset.
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---