|
GM WORLDWIDE ENGINEERING STANDARDS
|
Pdf ko'rish
bet | 184/406 | Sana | 03.04.2022 | Hajmi | 8,35 Mb. | | #525939 |
| Bog'liq gmw3110
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 147 of 336
send Negative Response ($7F $2C $31) /* RequestOutOfRange */
valid_request
NO
ELSE IF (total_length > 7)
send Negative Response ($7F $2C $12) /* InvalidFormat */
valid_request
NO
ENDIF
ENDIF
/* process the request if it is valid */
IF (valid_request = YES)
Assign PIDs to requested DPID for further use with $AA service
store length of DPID for further use with $AA service
Send ($6C $DPID#) response message
ENDIF
ENDFUNCTION
8.10.7 Node Verification Procedure.
Procedure 1:
1. Define a valid dynamic DPID with a single PID, verify that the correct parameter and length are reported
with an $AA request.
2. Define a valid dynamic DPID using PIDs that will result in seven data bytes in the report message. Verify
that the correct parameters are reported with a $AA request.
3. After step 2, send a $20 request and verify the positive response. Then send a request for the DPID
defined in step 2 using the $AA service. Verify that the contents of the dynamic DPID were not lost by
verifying the data in the $AA UUDT response message.
Procedure 2:
1. Define a valid dynamic DPID using PIDs that will result in more than seven data bytes in the report
message. Verify the $7F $2C $12 response.
2. Send a request which attempts to define a dynamic DPID which the node under test does not support and
verify the $7F $2C $31 response.
3. Send a request which attempts to define a dynamic DPID with a PID that the node under test does not
support and verify the $7F $2C $31 response.
4. Send a request message to define a valid dynamic DPID with and include only one byte of data after the
DPID number. Verify the $7F $2C $12 response.
5. Send a request message to define a valid dynamic DPID with and include an odd number of bytes (more
than two, with the first two being a valid PID#) after the DPID#. Verify the $7F $2C $12 response.
6. Send a request message with no data bytes after the service identifier and verify the $7F $2C $12
response.
7. If applicable, send a request which attempts to define a dynamic DPID with a secure PID. Ensure that this
is done at a time when security access has not been granted. Verify the $7F $2C $31 response.
8. If applicable, send a request which attempts to define a dynamic DPID with a secure PID. Ensure that this
is done at a time when security access has been granted. Verify that the correct parameter and length are
reported with an $AA request.
9. If applicable, send a request which attempts to define a dynamic DPID with a security code (as defined in
the Vehicle Theft Deterrent SSTS) required PID. Ensure that this is done at a time when the security code
has not been entered. Verify the $7F $2C $31 response.
10. If applicable, send a request which attempts to define a dynamic DPID with a security code required PID.
Ensure that this is done at a time when the security code has been entered. Verify that the correct
parameter and length are reported with an $AA request.
CameraLoops.com
Do'stlaringiz bilan baham: |
|
|