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

8.4.7 Node Verification Procedure.
Procedure 1:
1. Send a $1A message with each $dataIdentifier supported and verify proper response (test data
formatting).
Procedure 2: 
(Only applicable if ECU has secure DIDs).
1. Send a $1A message with a secure $dataIdentifier value when the device is the manufacturers enable
counter (MEC) = $00 and the vulnerability flag < $FF and verify the negative response ($31 - Request Out
Of Range).
2. Send a $1A message with a secure $dataIdentifier value when the manufacturers enable counter > $00 or
vulnerability flag = $FF and security has not been accessed (SecurityAccess ($27) request has not been
sent) and verify the negative response ($31 - Request Out Of Range).
3. Send a $1A message with a secure $dataIdentifier value when the manufacturers enable counter > $00 or
vulnerability flag = $FF and security has been accessed (SecurityAccess ($27) request has been sent) and
verify the appropriate positive response.
4. Repeats steps 1 through 3 for each secure DID.
Procedure 3:
1. Send a $1A message with an invalid $dataIdentifier parameter and verify the negative response ($31 -
Request Out Of Range).
2. Send a $1A message without a dataIdentifier included (e.g., request message ends after the service Id)
and verify the negative response ($12 - Invalid Format).
3. Send a $1A message with data bytes after the sub-parameter and verify the negative response ($12 -
Invalid Format).
4. Send a $1A message to the ECU with a dataIdentifier where the ECU needs more than P2
C 
ms to read
data bytes from memory and send the positive response (if applicable). Verify that the ECU sends the
negative response ($78 - RequestCorrectlyReceived-ResponsePending) within P2
C 
ms followed by a
positive response (reference application timing section of this specification).
Procedure 4: 
(Applicable if the ECU implements this return code).
1. Send a request for a valid dataIdentifier at a time when ECU internal conditions will not allow the data to
be retrieved (e.g., EEPROM failure) and verify that the ECU sends the correct negative response ($22
ConditionsNotCorrect).