Valid

T/CSAE 42-2015Electric vehicles - unified diagnostic services specification over CAN bus (English PDF)

电动汽车CAN总线故障诊断规范

Preview PDF

This is a limited preview

Buy now to download the full PDF (35 pages)

Need quotation for your management?

Get a formal quotation for T/CSAE 42-2015 in 30 minutes.

Issued by

China Society of Automotive Engineers

Level / Type

National · Mandatory

Issue date

November 5, 2015

Implementation date

November 5, 2015

Scope

T/CSAE 42-2015 is the English-translated version of 电动汽车CAN总线故障诊断规范.

T/CSAE 42-2015 — This specification stipulates that the electric vehicle diagnostic equipment and the electric vehicle controller (not limited to the vehicle controller) are connected by CAN line.

Diagnostic abbreviations and diagnostic application layer services. This specification is applicable to online diagnosis of pure electric passenger vehicles. Wireless diagnosis can be used for reference.

Found what you need?

Document preview — T/CSAE 42-2015

National Standard of the People's Republic of China

ICS
43.040.01
Classification
T 47

Issued by: China Society of Automotive Engineers

Contents

  • Foreword
  • 1 Scope
  • 2 Normative references
  • 3 Abbreviations
  • 3.1 BS Block Size block size
  • 3.2 CF Consecutive Frame Subsequent Frame
  • 3.3 DA Destination Address
  • 3.4 DLC Data Length Code data field length
  • 3.5 DTC Diagnostic Trouble Code DTC
  • 3.6 Controller Vehicle Control Unit
  • 3.7 EOL End Of Line Offline Diagnosis
  • 3.8 FC Flow Control Flow Control
  • 3.9 FF First Frame first frame
  • 3.10 ID Identifier
  • 3.11 NA Network Address
  • 3.12 PCI Protocol Control Information Protocol Control Information
  • 3.13 PID Parameter Identifier Parameter Identifier
  • 3.14 SA Source Address Source Address
  • 3.15 SF Single Frame Single Frame
  • 3.16 SID Service Identifier Service Identifier
  • 3.17 ST Separation Time Interval
  • 5.1 Data transmission
  • 5.2 Message Type
  • 5.3 Addressing mode
  • 5.4 Diagnostic session
  • 5.5 Overview of Timing Requirements for the Application Layer and Diagnostic Session Layer

Foreword

"Electric Vehicle CAN Bus Fault Diagnosis Service Specification" introduces the basic functions and extended functions of the CAN bus of electric vehicles.

It also stipulates the basic norms of hardware interfaces, in order to provide a basis for the development of enterprise electric vehicles, and is also conducive to China's electric vehicle industry.

Form a unified diagnostic and maintenance standards.

-- Part 1. Scope of application of the document;

-- Part 2. Normative references;

-- Part 3. Abbreviations;

-- Part 4. Introduction to diagnostic system functions;

-- Part 5. Diagnostic communication protocol;

-- Part 6. Definition of diagnostic services.

This specification was proposed by the Electric Vehicle Industry Technology Innovation Alliance.

This specification is under the jurisdiction of the China Automotive Engineering Society.

1 Scope

This specification stipulates that the electric vehicle diagnostic equipment and the electric vehicle controller (not limited to the vehicle controller) are connected by CAN line.

Diagnostic abbreviations and diagnostic application layer services.

This specification is applicable to online diagnosis of pure electric passenger vehicles. Wireless diagnosis can be used for reference.

2 Normative references

The terms in the following documents become the terms of this specification by reference to this specification. Any dated reference document, followed by Some amendments (not including errata content) or revisions do not apply to this specification, however, agreements that are agreed upon in accordance with this specification are encouraged.

The parties studied whether the latest version of these documents could be used. For undated references, the latest edition applies to this specification.

ISO 14229 Road Vehicle Unified Diagnostic Repair Equipment (UDS). Specifications and Requirements ISO 15765-2 Road Vehicles - CAN Diagnostics. Network Layer Services ISO 15765-3 Road Vehicles - CAN Diagnostics. Application Layer Services

3 Abbreviations

The following terms and abbreviations apply to this specification.

3.1 BS Block Size block size

3.2 CF Consecutive Frame Subsequent Frame

3.3 DA Destination Address

3.4 DLC Data Length Code data field length

3.5 DTC Diagnostic Trouble Code DTC

3.6 Controller Vehicle Control Unit

3.7 EOL End Of Line Offline Diagnosis

3.8 FC Flow Control Flow Control

3.9 FF First Frame first frame

3.10 ID Identifier

3.11 NA Network Address

3.12 PCI Protocol Control Information Protocol Control Information

3.13 PID Parameter Identifier Parameter Identifier

3.14 SA Source Address Source Address

3.15 SF Single Frame Single Frame

3.16 SID Service Identifier Service Identifier

3.17 ST Separation Time Interval

4 CAN diagnostic system function introduction CAN line-based diagnostics provide the ability to quickly access information and the ability to run control units without disconnecting cables.

The diagnostic services provided are.

Communication management. setting the connection status and management information when starting communication, end, and communication test;

Permission settings. provide numerous diagnostic services and different diagnostic information for different customers;

Data monitoring. including reading of information, and obtaining some real-time information, statistical data, etc.;

b) Data calibration. modify or optimize internal parameters according to the performance requirements of the controller or the performance requirements of the vehicle;

c) Input/Output Control. Trigger some predetermined test tasks to obtain the status of the entire vehicle or vehicle component or subsystem;

d) Read the internal information of the controller, such as the contents of the fault storage.

5 CAN diagnostic communication protocol

5.1 Data transmission

5.1.1 Classification of data transmission

The CAN diagnostic message is supported using the multi-packet data transfer unit (USDT) specified in ISO 15765-2:2004. That is, two types are supported.

CAN data transmission - single packet data transmission and multi-packet data transmission.

5.1.2 Single Packet Data Transmission

Single packet data transmission consists of a single frame (SF). Its use condition is. single frame length does not exceed 7 or extended search in normal addressing mode in the address mode, the single frame length does not exceed 6. An example of a single packet data transfer is shown in Figure 1.

Figure 1 Single packet data transmission example

5.1.3 Multi-packet data transmission

Multi-packet data transmission consists of multi-frame segmented CAN messages. Its use condition is. the data length is greater than 7 in the normal addressing mode.

Or the data length is greater than 6 when the addressing mode is extended. The data transmission includes a first frame (FF) and a plurality of subsequent frames (CF). Receiving end A flow control frame (FC) must be sent after receiving the first frame (FF). The information contained in the flow control frame is. block size (BS) and interval Time (ST). The block size (BS) indicates the maximum number of subsequent frames that the receiver allows the transmitter to send. Interval (STmin) Indicates the minimum time that the sender must wait between two subsequent frames. An example of a multi-packet data transfer is shown in Figure 2.

Figure 2 Multi-package data transfer example

5.2 Message Type

5.2.1 Data frame structure

Single frame (SF), first frame (FF), subsequent frame (CF) or flow control frame (FC) contain an 8-byte data field, the number the data field consists of the following two parts. Table 1 shows the structure of the PCI bytes of various CAN messages.

a) Protocol Control Information (PCI) indicating the frame type, frame number, data length, etc.

b) Transfer data, including the data being sent.

Sender recipient

Single frame

Sender recipient

First frame

Flow control

Subsequent frame

STmin

Subsequent frame

Subsequent frame

Subsequent frame

Subsequent frame

Flow control

Block size (BS)

Terminating block (<=BS)

Table 1 Structure of PCI bytes of various CAN messages

Data domain structure Frame type Byte 1 Byte 2 bytes 3 bytes 4-8 Bit 7-4 Bit 3-0 Single frame (SF) 0000 SF_DL data 1 data 2 data 3-7 First frame (FF) 0001 FF_DL data 1 data 2-6 Subsequent frame (CF) 0010 SN data 1 data 2 data 3-7 Flow Control (FC) 0011 FS BS Stmin N/A Note. SF_DL represents the 4-frame single-frame data length; FF_DL represents the 12-bit first frame data length; SN represents the sequence number; FS represents the data stream State; BS indicates block size; Stmin indicates minimum interval time.

5.2.2 Single frame

In normal addressing mode, the maximum data length of a single frame message type is 7 bytes, where the high nibble of PCI is set to 0000b.

The lower nibble of PCI indicates the data length of a single frame.

5.2.3 First frame

In normal addressing mode, the first frame message type has a data length greater than 7 bytes and is used in conjunction with one or more subsequent frames. PCI the upper nibble of the first byte is set to 0001b, and the lower nibble and second byte of the first byte represent the data length of the first frame. first the data length FF_DL of the frame is calculated as shown in Table 2.

Table 2 First frame data length FF_DL Description

Hexadecimal value data length FF_DL description 000h-007h reserved 008h-FFFh the first frame data length (FF_DL) contains the number of data bytes. 12-bit FF_DL theoretically supports sending up to 4096 data words Section. However, the current example does not need to support a maximum of 4096 data bytes.

5.2.4 Subsequent frames

Subsequent frames are after the first frame, where the high nibble of the PCI is set to 0010b. Its lower nibble is a sequence number (SN), the value of SN is calculated according to the following rules.

a) the SN value of the first frame is 0;

b) the SN value of the first subsequent frame is 1;

c) the SN value is incremented by "1" for each subsequent frame added;

d) that the transmission of the flow control frame affects the calculation of the SN value;

e) When the SN value reaches 15, the SN of the next subsequent frame is set to 0 again.

The definition of the sequence number (SN) value is shown in Table 3.

Table 3 Definition of sequence number (SN) values

Protocol Data Name FF CF CF CF CF CF CF CF CF SN (hexadecimal) 0h 1h 2h Eh Fh 0h 1h

5.2.5 Flow Control Frame
5.2.5.1 Introduction to Flow Control Frames

After the first frame or the last subsequent frame of the data block, when more subsequent frames (CF) are needed to complete the packet transmission, the reception the node must send a flow control frame message with the high nibble of the first byte of PCI set to 0011b. Flow control frame PCI the second byte represents the size of the largest message block (BSmax) between the two flow control frames, and the third byte represents between the two subsequent frames.

Time (minimum interval, Stmin). The lower nibble of the first byte of the flow control PCI is a flow control state (FS), data the flow state (FS) is defined as shown in Table 4.

Table 4 Definition of data flow state (FS)

Hexadecimal description 0h Continue to send (CTS). Receiver is ready and waiting for BS time 1h Wait (WT). The flow control wait parameter is encoded by setting the lower nibble of N_PCI byte #1 to "1".

It causes the sender to continue waiting for a new flow control N_PDU and restart its N_BS timer.

Overload flow (OVFLW). The flow control overload flow parameter is set to "2" by setting the lower nibble of N_PCI byte #1.

coding. It causes the sender to abort the transmission of the segmented message and make a N_USData.confirm service Response, the response band parameter \u003cN_Result\u003e =N_BUFFER_OVFLW. This N_PCI stream state parameter value is only it is transmitted in the flow control N_PDU. This flow control N_PDU follows the first frame N_PDU and is only received it is used when the message length FF_DL of the first frame N_PDU exceeds the buffer size of the receiving entity.

5.2.5.2 Flow Control Frame - Block Size

The block size (BSmax) represents the maximum number of subsequent frames between the two flow control messages that the receiver allows the transmitter to send.

The meaning is shown in Table 5.

Table 5 Definition of block size (BSmax)

Hexadecimal description Block size (Bsmax) the flow control frame will no longer be sent during the transmission of the segmentation message. The transmission of all subsequent frames will not be stalled due to the insertion flow control.

01h-FFh

Block size (Bsmax)

Define the maximum number of subsequent frames between two flow controls.

5.2.5.3 Flow Control Frame - Interval

The interval time (STmin) represents the minimum time allowed between two subsequent frames, which is defined as shown in Table 6.

Table 6 Definition of interval time (STmin)

Hexadecimal description 00h-7Fh indicates that the range of STmin is. 0ms-127ms 80h-F0h reserved undefined F1-F9 means that the STmin range is. 100us-900us FAh-FFh reserved undefined

5.3 Addressing mode

5.3.1 Physical Addressing Mode

All physical addressing messages are received at the physical address of the controller. When the diagnostic device uses physical addressing mode to request service at this point, the controller can perform the services supported by the currently active diagnostic session. The response from the controller is determined by the corresponding diagnostic instrument Receive.

5.3.2 Functional Addressing Mode

When the information requested by the diagnostics is not sent to a particular controller, the request message should be requested in a functional addressing mode.

5.4 Diagnostic session

The following diagnostic sessions are supported. (taking the vehicle controller as an example)

a) default session

The controller initiates a default diagnostic session when the electric car is powered up. In this session, both the controller function and the diagnostic service are activated.

However, diagnostic services supported by EOL and customer-specified diagnostic sessions are not allowed.

b) Non-default diagnostic session Non-default diagnostic sessions define two diagnostic sessions, the Controller Programming Session and the Controller Extended Diagnostic Session.

5.5 Overview of Timing Requirements for the Application Layer and Diagnostic Session Layer

5.5.1 Differences between application layer and diagnostic session layer timing requirements

a) The default session period and non-default session period for physical addressing communication.

b) The default session period and non-default period for functional addressing communication.

Based on the above two points of judgment, it is also considered that the controller may send a 78h code negative response message to request the extended response time.

Happening.

5.5.2 Timing definition of the application layer and diagnostic session layer
5.5.2.1 Application Layer Timing Value Definition During Default Diagnostic Session

The application layer timing values defined during the default diagnostic session are shown in Table 7.

Table 7 Application layer timing value definition during default diagnostic session

Timing Parameter Description Type Min Max P2CAN_Client Successfully transmitted request message and start response message Client wait time Timer re Load value P2CAN_Server_max deltaP2CAN N/A P2*CAN_Client Received a negative response message with code 78h and...

......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 35 pages — is available in the English PDF.

Referenced standards

Normative references

ISO 14229 · ISO 15765

How to Download T/CSAE 42-2015

  1. 1

    Add to cart

    Click "Download PDF" on this page and choose "Buy this standard". You can add more standards before checkout.

  2. 2

    Checkout

    Enter your email and billing details. Payment is processed securely by Stripe (cards or bank transfer). Prefer bank details? Request a quotation (min. order $300).

  3. 3

    Fast delivery

    After payment you'll receive an email confirmation. The English PDF is sent to the same address, usually within minutes and at the latest within 1 business day.

  4. 4

    Invoice included

    A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.

Related Standards

English PDF
35 pages
Fast delivery
Invoice included
View Cart

Secure payment via Stripe

Payments accepted

VisaMastercardAmerican ExpressApple PayGoogle PayStripe

T/CSAE 42-2015

$540.00