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

8.11.7 Node Verification Procedure.
Procedure 1:
1. Send a request to define a valid dynamic PID with one valid memory address (MS = $01) that is not
restricted, and non-secured. Verify the proper positive response. Verify that the correct data and number of
bytes for the defined PID are reported when requesting the PID with either a $22 or $AA request.
2. Send a request to define a valid dynamic PID with seven consecutive valid memory addresses (MS = $07)
that are not restricted, and non-secured. Verify the proper positive response. Verify that the correct data
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---
Page 155
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
and number of bytes for the defined PID are reported when requesting the PID with either a $22 or $AA
request.
3. If applicable, with the ECU manufacturers enable counter > $00, the vulnerability flag = $FF, and security
has been accessed (SecurityAccess ($27) request has been sent), send a request to define a valid
dynamic PID with an address range that is completely valid, not restricted, and includes secure locations.
Verify the proper positive response. Verify that the correct data and number of bytes for the defined PID
are reported when requesting the PID with either a $22 or $AA request.
Procedure 2:
1. Send a request with less than the required number of data bytes (4 + the number of bytes in the
memoryAddress parameter), verify negative response ($7F $2D $12).
2. Send a request with more than the required number of data bytes (4 + the number of bytes in the
memoryAddress parameter), verify negative response ($7F $2D $12).
3. Send a request with an invalid dynamic PID. Verify negative response ($7F $2D $31).
4. Define a valid dynamic PID with more than seven consecutive valid memory addresses (MS = $08) that
are not restricted, and non-secured. Verify negative response ($7F $2D $31).
5. Define a valid dynamic PID with a valid MA but with zero number of memory addresses (MS = $00). Verify
negative response ($7F $2D $31).
6. Define a valid dynamic PID with at least one invalid ECU address in the range of addresses specified by
MA and MS. Verify negative response ($7F $2D $31).
7. If applicable, define a valid dynamic PID with a valid range of non-secure addresses that includes at least
one restricted address. Verify negative response ($7F $2D $31).
8. If applicable, with the ECU manufacturers enable counter = $00, the vulnerability flag < $FF, and security
has not been accessed (SecurityAccess ($27) request has not been sent), define a valid dynamic PID with
a range of valid and non-restricted addresses that includes at least one secure address. Verify negative
response ($7F $2D $31).
9. If applicable, with the manufacturers enable counter > $00 or vulnerability flag = $FF and security has not
been accessed (SecurityAccess ($27) request has not been sent), define a valid dynamic PID with a range
of valid and non-restricted addresses that includes at least one secure address. Verify negative response
($7F $2D $31).
10. If applicable, with the manufacturers enable counter > $00 or vulnerability flag = $FF and security has

---

25.06.2020
WORLDWIDE ENGINEERING STANDARDS General Motors Local Area Network Enhanced Diagnostic Test Mode Specification
https://translate.googleusercontent.com/translate_f
138/298
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 155 of 336
been accessed (SecurityAccess ($27) request has been sent), define a valid dynamic PID with a range of
valid and non-restricted addresses that includes at least one secure address. Verify positive response.
11. If negative response code $78 is supported by the ECU, then create the conditions under which the ECU
should return the $7F $2D $78 response and verify that proper response is sent. Repeat for each possible
reason an ECU would send the negative response with response code $78.