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

Page 93
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
Send ($7F $12 $78) /*for RequestCorrectlyReceived-ResponsePending */
…..
Send ($52 $02 ….) /* positive response message */
ENDIF
ENDIF
OTHERWISE
Send negative response ($7F $12 $12) /*for SubFunctionNotSupported-InvalidFormat */
ENDSELECT
ENDFUNCTION
8.3.7 Node Verification Procedure.
Procedure 1:
1. Send a request message with no data bytes following the service identifier and verify the $7F $12 $12
response.
2. Send a readFailureRecordIdentifiers request message with more than 1 data byte following the service
identifier and verify the $7F $12 $12 response.
3. Send a readFailureRecordParameters request message with more than 5 data bytes following the service
identifier and verify the $7F $12 $12 response.
4. Repeat step 3 using less than 5 data bytes following the service identifier and verify the $7F $12 $12
response.
5. Send a request message with an invalid sub-function parameter value and verify the $7F $12 $12
response.

---

25.06.2020
WORLDWIDE ENGINEERING STANDARDS General Motors Local Area Network Enhanced Diagnostic Test Mode Specification
https://translate.googleusercontent.com/translate_f
83/298
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 93 of 336
Procedure 2:
1. Send a valid readFailureRecordIdentifiers request message when the device has no failure records stored
and verify the proper response which contains no data following the failureRecordDataStructureIdentifier.
2. Send a valid readFailureRecordIdentifiers request message when the device has at least one failure
record stored and verify proper response.
3. Send a valid readFailureRecordParameters request message and verify proper response which includes
data parameters for the failure record identifier.
Procedure 3:
1. Send a readFailureRecordParameters request message for a failure record with a failure record identifier
(failure record number + DTC identifier) that does not correspond to a single unique failure record in the
node and verify the $7F $12 $31 response.
Procedure 4:
1. If negative response code $78 is supported by the ECU, then create the conditions under which the ECU
should return the $7F $12 $78 response and verify that proper response is sent.
2. Repeat previous step of this procedure for each possible reason an ECU would send the negative
response with response code $78. Verify this for each applicable supported sub-function parameter.
Procedure 5:
1. If negative response code $22 is supported by the ECU, then create the conditions under which the ECU
should return the $7F $12 $22 response and verify that proper response is sent.
2. Repeat previous step of this procedure for each possible reason an ECU would send the negative
response with response code $22. Verify this for each applicable supported sub-function parameter.