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

Page 246
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 246 of 336
request_DeviceControl_exit ←
NO
Dev_Cntrl_Active ←
NO
set all the individual device control status flags to FALSE
ENDIF
ENDFUNCTION
8.20.7 Node Verification Procedure.
Procedure 1:
1. Send a $AE message with less than two data bytes (no CPID in request) and verify the $7F $AE $12
response.
2. Send a multiple frame $AE message and verify $7F $AE $12 response.
3. Send a $AE message with an invalid number of control bytes for a given CPID and verify the $7F $AE $12
response.
4. Send a $AE message with an unsupported CPID and verify $7F $AE $31 response.
5. Send a $AE message with a secure CPID (if applicable) with with the manufacturers enable counter = $00
or vulnerability flag < $FF and security has not been accessed (SecurityAccess ($27) request has not been
sent) and verify $7F $AE $31 response.
6. Send a $AE message with a secure CPID (if applicable) 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 $7F $AE $31 response.
7. Send a $AE message with a secure CPID (if applicable) 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.
8. Send a $AE message with a security code required CPID (if applicable) with the security code (as defined
in the Vehicle Theft Deterrent SSTS) has not been entered and verify $7F $AE $31 response.
9. Send a $AE message with a security code required CPID (if applicable) when the security code has been
entered and verify the appropriate positive response.
Procedure 2:
1. Send a $AE message with a valid CPID and data and verify the activation of device control. Repeat this
step for each device control function supported.
Procedure 3:
1. Send a $AE message with CPID of $00 while device control is active, verify that active device control
function(s) are cancelled.
2. Repeat Item 1 for each device control supported.
3. Activate a device control function and then verify that the control function is cancelled after P3
Cmax 
ms
without any TesterPresent ($3E) messages sent on the bus.
4. Repeat Item 3 for each device control supported.
Procedure 4:
1. Send a $AE message with a valid CPID and data, cause a device control limit to be exceeded, verify $7F
$AE $E3 $xx $yy (limit exceeded) response. Verify that the values of $xx and $yy are correct for the limit
which was exceeded.
2. Repeat step 1 for each possible device control restriction.
Procedure 5:
1. Send a valid device control command without the InitiateDiagnosticOperation ($10) service active. Create
a fault condition and verify that no DTC is set (via the $A9 service) for the fault condition created.
2. Send the appropriate InitiateDiagnosticOperation ($10) request (if applicable) to allow DTC algorithms to
run while DeviceControl is active. Activate a device control and then create a fault condition and verify that
the appropriate DTC is logged (via the $A9 service).

---

25.06.2020
WORLDWIDE ENGINEERING STANDARDS General Motors Local Area Network Enhanced Diagnostic Test Mode Specification
https://translate.googleusercontent.com/translate_f
219/298