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

T = Frame Sent By Tester, N = Frame Sent By Node; shaded region indicates PCI
Frame Type CAN Id
#1
#2
#3
#4
#5
#6
#7
#8
T(USDT-SF)
$241
$02
$12
$01
---
---
---
---
---
N(USDT-SF)
$641
$03
$52
$01
$00
---
---
---
---
8.3.6 Node Interface Function.
8.3.6.1 Node Interface Data Dictionary (Table 67).
Table 67: Node Interface Data Dictionary of ReadFailureRecordData Service Pseudo Code
Variable/Meaning
Values
message_data_length
Reference Common/Global
Pseudo Code Data
Dictionary For Definition Of
These Flags/Variables
record_index
This is a local variable used in the pseudo code when searching through the
failure records to find the record that matches the request message.
$00 thru $FF
num_records
This is a variable used in the pseudo code to indicate the maximum number of
failure records that a node will store.
$00 thru $FF
record_array
For the purposes of the pseudo code, it is assumed that the failure record data
is stored as an array of data structures. Each data structure contains the
following elements:
1. record_number_stored
2. DTC_Number
3. DTC_FailureType
4. Data
The data referenced in element 4 above is the first byte of DTC specific data
stored in the failure record.
To access an element of the data structure, the following nomenclature is used:
record_array[record_index].element
Where: 
record_index is described above in the data dictionary and element is
one of the four types listed here.
The values are described
below for each data type of
the record:
1. $00 thru $255 (node
specific)
2. A 2-byte value is used to
indicate the DTC set.
Reference mode $A9 for
more details on DTC
format.
3. A 1-byte value used to
describe the FailureType
of a stored DTC.
4. This field can be multiple
bytes long and contain
data which must be
specified in a CTS or
supplemental diagnostic
specification.