|
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 230 of 336
8.19.6.3.1 Example #1 - Single DPID Schedule Rates.
In this example, four DPIDs ($01, $02, $03, and $04)
are scheduled at the medium rate. At t = 0.0 ms, the tool begins sending the request to schedule the four
DPIDs at the medium rate. For the purposes of this example, the ECU receives the request and executes the
PDS code for the first time t = 25.0 ms. See Figure 34 and Table 206.
Tester
ECU
0 ms
25 ms
37.5 ms
225 ms
237.5 ms
Tim e ( t )
Act ual
schedule
rat e
Mode $AA
request
DPID #1
DPID #2
62.5 ms
50 ms
DPID #3
DPID #4
262.5 ms
250 ms
DPID #1
DPID #2
DPID #3
DPID #4
Figure 34: Example #1 - Four DPIDs at Medium Rate (200 ms) with 12.5 ms AA_Msg_Rate Rate
CameraLoops.com
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 231 of 336
Table 206: Example #1 - Four DPIDs at Medium Rate (200 ms) with 12.5 ms AA_Msg_Rate Rate
t (ms)
PDS
Xmit
Index
DPID
Sent
PDS
Loop #
PDS[0]
Transmit
Count
PDS[1]
Transmit
Count
PDS[2]
Transmit
Count
PDS[3]
Transmit
Count
25.0
0
1
1
0 to 16
0
0
0
37.5
1
2
2
15
0 to 16
0
0
50.0
2
3
3
14
15
0 to 16
0
62.5
3
4
4
13
14
15
0 to 16
75.0
0
None
5
12
13
14
15
87.5
0
None
6
11
12
13
14
100.0
0
None
7
10
11
12
13
112.5
0
None
8
9
10
11
12
125.0
0
None
9
8
9
10
11
137.5
0
None
10
7
8
9
10
150.0
0
None
11
6
7
8
9
162.5
0
None
12
5
6
7
8
175.0
0
None
13
4
5
6
7
187.5
0
None
14
3
4
5
6
200.0
0
None
15
2
3
4
5
212.5
0
None
16
1
2
3
4
225.0
0
1
17
0 to 16
1
2
3
237.5
1
2
18
15
0 to 16
1
2
250.0
2
3
19
14
15
0 to 16
1
262.5
3
4
20
13
14
15
0 to 16
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---
CameraLoops.com
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 232 of 336
8.19.6.3.2 Example #2 - Mixed DPID Schedule Rates.
In this example, three DPIDs ($01, $02, $03) are
scheduled at the fast rate and then another request is sent for a single DPID ($04) to be scheduled at the
medium rate. For the purposes of this example, the ECU receives the first mode $AA request and executes the
PDS code for the first time t = 25.0 ms. The second mode $AA request is received and processed just prior to
the device executing the Process_AA_Msgs() function at t = 50.0 ms. See Figure 35 and Table 207.
Tester
ECU
0 ms
25 ms
37.5 ms
325 ms
337.5 ms
Time ( t )
Mode $AA request
fast rate
DPID #1
DPID #2
Mode $AA request
medium rate
50 ms
62.5 ms
DPID #4
DPID #3
300 ms
312.5 ms
375 ms
387.5 ms
350 ms
362.5 ms
412.5 ms
425 ms
400 ms
Medium
rate =
312.5 ms
Fast
rate =
37.5 ms
Fast
rate =
50 ms
Fast
rate =
37.5 ms
DPID #1
DPID #2
DPID #3
DPID #1
DPID #2
DPID #3
DPID #4
DPID #1
DPID #2
DPID #3
DPID #1
Figure 35: Example #2 - Mixture of DPID Schedule Rates
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---
CameraLoops.com
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 233 of 336
Table 207: Example #2 - Three DPIDs at Fast Rate (25 ms) and 1 DPID at Medium Rate (300 ms)
t (ms)
PDS
Xmit
Index
DPID
Sent
PDS
Loop #
PDS[0]
Transmit
Count
PDS[1]
Transmit
Count
PDS[2]
Transmit
Count
PDS[3]
Transmit
Count
25.0
0
1
1
0 to 2
0
0
N/A
37.5
1
2
2
1
0 to 2
0
N/A
50.0
2
3
3
0
1
0 to 2
0
62.5
3
4
4
0
0
1
0 to 24
75.0
0
1
5
0 to 2
0
0
23
87.5
1
2
6
1
0 to 2
0
22
100.0
2
3
7
0
1
0 to 2
21
112.5
3
1
8
0 to 2
0
1
20
125.0
1
2
9
1
0 to 2
0
19
137.5
2
3
10
0
1
0 to 2
18
150.0
3
1
11
0 to 2
0
1
17
162.5
1
2
12
1
0 to 2
0
16
175.0
2
3
13
0
1
0 to 2
15
187.5
3
1
14
0 to 2
0
1
14
200.0
1
2
15
1
0 to 2
0
13
212.5
2
3
16
0
1
0 to 2
12
225.0
3
1
17
0 to 2
0
1
11
237.5
1
2
18
1
0 to 2
0
10
250.0
2
3
19
0
1
0 to 2
9
262.5
3
1
20
0 to 2
0
1
8
275.0
1
2
21
1
0 to 2
0
7
287.5
2
3
22
0
1
0 to 2
6
300.0
3
1
23
0 to 2
0
1
5
312.5
1
2
24
1
0 to 2
0
4
325.0
2
3
25
0
1
0 to 2
3
337.5
3
1
26
0 to 2
0
1
2
350.0
1
2
27
1
0 to 2
0
1
362.5
2
3
28
0
1
0 to 2
0
375.0
3
4
29
0
0
1
0 to 24
387.5
0
1
30
0 to 2
0
0
23
CameraLoops.com
GM WORLDWIDE ENGINEERING STANDARDS
GMW3110
© Copyright 2010 General Motors All Rights Reserved
February 2010
Page 234 of 336
8.19.7 Node Verification Procedure.
Procedure 1:
All $AA requests for this procedure are with $Level = LEV_SOR ($01).
1. Send a request (including only valid DPIDs) with the total number of DPIDs less than the maximum
number supported by the ECU for this $Level. Verify the proper response(s).
2. Send a request (including only valid DPIDs) with the total number of DPIDs requested equal to the
maximum number supported by the ECU for this $Level. Verify the proper responses.
3. Send a request (including only valid DPIDs) with the total number of DPIDs requested greater than the
maximum number supported by the ECU for this $Level. Verify negative response ($7F $AA $12).
4. Send A request with no DPIDs. Verify negative response ($7F $AA $12).
5. Send a request with an invalid DPID. Verify negative response ($7F $AA $31).
6. Send a request with at least one valid and one invalid DPID. Verify that the only response to this request is
the negative response ($7F $AA $31).
7. Verify that it is possible to retrieve all supported DPIDs in the ECU with one or more requests of this
service.
Procedure 2:
1. Request a periodic (valid) DPID. Verify proper response, and proper response timing. Repeat this test for
each supported periodic rate.
2. After completing step 1 of this procedure, verify that the periodic DPID data stops after P3
Cmax
ms (with no
additional diagnostic requests).
3. With the periodic scheduler inactive, request the maximum number of DPIDs (all items) at one of the
supported periodic rates. Verify proper responses and response timing for each scheduled DPID. Send
$3E messages at least once every P3
C
ms and verify that the responses continue to be properly sent for
five minutes.
4. Repeat step 3 of this procedure for each additional supported periodic rate.
5. Send a single periodic request with more DPIDs than the ECU can schedule. Verify the negative response
($7F $AA $12).
6. Request a number of DPIDs to be sent periodically at one supported rate. Request additional DPIDs to be
sent at another supported rate (not equal to the first rate) until DPIDs are sent with all supported rates
simultaneously (If the number of DPIDs the PDS supports is less than the number of supported periodic
rates, then repeat this step for all possible combinations of supported data rates). Verify proper responses
and response timing. Send $3E messages at least once every P3
C
ms and verify that the responses
continue to be properly sent for five minutes.
7. Request an additional (valid) DPID to be scheduled when the DPID scheduler is already full and verify the
proper negative response ($7F $AA $81). Verify that the previously scheduled DPIDs continue to be sent
at the rates scheduled prior to the last request.
8. Send a periodic request containing a DPID which is already in the PDS, using a sub-function parameter
which will result in a change to the data rate of the requested DPID. Perform this test while the scheduler
is full. Verify that the requested DPID changes data rates, that the data rate of the other DPIDs in the PDS
do not change, and that no negative response for scheduler full is sent.
9. Send a periodic request containing both valid and invalid DPIDs (with the total number of DPIDs in the
request less than the maximum number of periodic DPIDs allowed in the PDS). Verify the negative
response ($7F $AA $31). Repeat this step for each supported periodic rate.
10. Verify that it is possible to periodically schedule all supported DPIDs in the ECU.
11. Send a periodic request with no DPIDs, verify negative response ($7F $AA $12). Repeat for each periodic
rate supported.
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---
CameraLoops.com
Do'stlaringiz bilan baham: |
