ISO 15765-3: 诊断控制器局域网（CAN）统一诊断服务实施

需积分: 10 74 浏览量更新于2024-07-25 收藏 6.75MB PDF 举报

"ISO 15765-3标准是关于道路车辆在控制器区域网络（Controller Area Network, CAN）上的诊断规范，旨在统一CAN网络上的诊断服务。该标准主要涉及车辆诊断的实施，特别是统一的诊断服务（Unified Diagnostic Services, UDS）在CAN上的应用。" ISO 15765-3标准是ISO 15765系列的一部分，该系列标准定义了道路车辆电子控制系统进行通信和诊断的协议。2004年首次发布，它规定了如何在CAN网络上实现标准化的诊断服务，以确保不同制造商的设备之间具有互操作性。在汽车行业中，CAN网络是一种广泛使用的通信协议，允许不同车辆模块之间的数据交换。ISO 15765-3则为这个网络提供了一个框架，以便于执行故障检测、修复和维护。这个标准涵盖了多个关键领域： 1. **诊断消息结构**：ISO 15765-3定义了诊断消息的格式，包括数据包的长度、标识符、数据字段和校验和，以确保信息传输的准确性和可靠性。 2. **传输层**：标准中包含了传输层的详细规定，如帧分段和重组，以处理CAN网络的带宽限制，尤其是对于较长的诊断消息。 3. **错误检测与恢复机制**：它规定了在网络出现错误时如何恢复通信，以保证诊断过程的连续性。 4. **统一诊断服务**（UDS）：UDS是一套标准化的服务集，用于执行各种车辆诊断任务，如读取故障代码、清除故障码、读取数据流等。ISO 15765-3描述了如何在CAN环境中实现这些服务。 5. **兼容性与互操作性**：标准的实施确保了不同制造商的诊断工具和车辆系统能够顺利地交换信息，简化了维修流程并降低了成本。 6. **安全考虑**：考虑到汽车诊断可能对车辆安全的影响，ISO 15765-3还涵盖了安全性方面的要求，防止未经授权的访问和潜在的安全威胁。 7. **软件更新**：标准还涵盖了通过CAN网络进行软件更新的过程，这对于现代汽车中不断增长的软件依赖性至关重要。 ISO 15765-3标准为汽车行业的诊断和维修提供了标准化的方法，促进了汽车电子系统的可靠性和可维护性，同时也有助于提高整个行业的效率和安全性。

ISO 15765-3:2004(E)

6.3.5.1.2 Physical communication during defaultSession with enhanced response timing

Figure 4 graphically depicts the timing handling in the client and the server for a physically addressed request

message during the default session and the request of the server for an enhanced response timing (negative

response code 78 hex handling).

The diagnostic application of the client starts the transmission of the request message by issuing a N_USData.req to

its network layer. The network layer transmits the request message to the server. The request message can either be a

single-frame or multi-frame message.

In the case of a multi-frame message, the start of the request is indicated in the server via N_USDataFF.ind that is

issued by its network layer.

The completion of the request message is indicated in the client via N_Usdata.con. When receiving the

N_USData.con, the client starts its P2

CAN_Client

timer, using the default reload value P2

CAN_Client

. The value of the

CAN_Client

timer shall consider any latency that is involved based on the vehicle network design (e.g. communication

over gateways, bus bandwidth, etc.). For simplicity, the figure assumes that the client and the server are located on the

same network.

The completion of the request message is indicated in the server via N_USData.ind.

B55EB1B3C7662F79D1B59483A53B9F2F82C98BEEB7939EA95CF14FFEE5FB13B925D84A2690B319CCC3FB33EC1A0EE19ACE32C3AD48AA2003E27076E26B823E886461F4EB146348E75A2E06040CBB18

Normen-Download-Beuth-MOWAG GmbH-KdNr.2337322-LfNr.2988619001-2005-11-07 16:16

ISO 15765-3:2004(E)

The server is required to start with its response message within P2

CAN_Server

after the reception of N_USData.ind.

This means that, in the case of a multi-frame response message, the FirstFrame shall be sent within P2

CAN_Server

and, for

single-frame response messages, that the SingleFrame shall be sent within P2

CAN_Server

In case the server cannot provide the requested information within the P2

CAN_Server

response timing, it can request an

enhanced response timing window by sending a negative response message including response code 78 hex. Upon

reception of the negative response message within the client, the client network layer generates a N_USData.ind. The

reception of a negative response message with response code 78 hex causes the client to restart its P2

CAN_Client

timer,

but using the enhanced reload value P2*

CAN_Client

The server is required to start with its response message within the enhanced P2

CAN_Server

(P2*

CAN_Server

) following

the N_USData.con of the transmitted negative response message. In case the server can still not provide the requested

information within the enhanced P2*

CAN_Server

, then a further negative response message including response code 78 hex

can be sent by the server. This will cause the client to restart its P2

CAN_Client

timer, using the enhanced reload value

P2*

CAN_Client

. For simplicity, the figure only shows a single negative response message with response code 78 hex.

Once the server can provide the requested information (positive or negative response other than response code 78

hex), it starts with its final response message.

In the case of a multi-frame final response message, the reception of the FirstFrame is indicated in the client via the

N_USDataFF.ind of the network layer. When receiving the FirstFrame indication, the client stops its P2

CAN_Client

timer.

The network layer of the client will generate a final N_USData.ind in case the complete message is received or an

error occurred during the reception. In the case of a single-frame response message, the reception of the SingleFrame is

indicated in the client via a single N_USData.ind. When receiving this single-frame indication, the client stops its

CAN_Client

timer.

The completion of the transmission will also be indicated in the server via N_USData.con.

Figure 4 — Physical communication during non-default session — Enhanced response timing

6.3.5.1.3 Physical communication during a non-default session

6.3.5.1.3.1 Functionally addressed TesterPresent (3E hex) message

Figure 5 graphically depicts the timing handling in the client and the server when performing physical

communication during a non-default session (e.g. programmingSession) and using a functionally addressed,

periodically transmitted TesterPresent (3E hex) request message that does not require a response message

from the server.

The handling of the P2

CAN_Client

and P2

CAN_Server

timing is identical to the handling as described in 6.3.5.1.1

and 6.3.5.1.2. The only exception is that the reload values on the client side and the resulting time where the

server shall send its final response time might differ. This is based on the transition into a session other than

the default session where different P2

CAN_Client

timing parameters might apply (see DiagnosticSessionControl

(10 hex) service in 9.2.1 for details on how the timing parameters are reported to the client).

B55EB1B3C7662F79D1B59483A53B9F2F82C98BEEB7939EA95CF14FFEE5FB13B925D84A2690B319CCC3FB33EC1A0EE19ACE32C3AD48AA2003E27076E26B823E886461F4EB146348E75A2E06040CBB18

Normen-Download-Beuth-MOWAG GmbH-KdNr.2337322-LfNr.2988619001-2005-11-07 16:16

ISO 15765-3:2004(E)

The diagnostic application of the client starts the transmission of the DiagnosticSessionControl (10 hex) request

message by issuing a N_USData.req to its network layer. The network layer transmits the request message to the server.

The request message is a single-frame message. Its completion is indicated in the client via the N_USData.con. Now

the response timing as described in 6.3.5.1.1 and 6.3.5.1.2 applies. The generated N_USData.con in the client causes the

start of the S3

Client

timer (session timer).

The completion of the request message is indicated in the server via the N_USData.ind. Now the response timing as

described in 6.3.5.1.1 and 6.3.5.1.2 applies.

For the figure given, it is assumed that the client requires a response from the server. The server shall transmit the

DiagnosticSessionControl (10 hex) positive response message.

The completion of the transmission of the response message is indicated in the server via N_USData.con. Now the

server starts its S3

Server

timer, which keeps the activated non-default session active as long as it does not time out. It is

the client's responsibility to ensure that the S3

Server

timer is reset prior to its timeout to keep the server in the non-default

session.

Once the S3

Client

timer is started in the client, this causes the transmission of a functionally addressed TesterPresent

(3E hex) request message, which does not require a response message, each time the S3

Client

timer times out.

Upon the indication of the completed transmission of the TesterPresent (3E hex) request message via N_USData.con

of its network layer, the client once again starts its S3

Client

timer. This means that the functionally addressed TesterPresent

(3E hex) request message is sent on a periodic basis every time S3

Client

times out.

Any time the server is in the process of handling any diagnostic service, it stops its S3

Server

timer.

When the diagnostic service is completely processed, then the server restarts its S3

Server

timer. This means that any

diagnostic service, including TesterPresent (3E hex), resets the S3

Server

timer. A diagnostic service is meant to be in

progress any time between the start of the reception of the request message (N_USDataFF.ind or N_USData.ind receive)

and the completion of the transmission of the final response message, where a response message is required, or the

completion of any action that is caused by the request, where no response message is required (point in time reached that

would cause the start of the response message).

Any TesterPresent (3E hex) request message that is received during processing another request message can be

ignored by the server, because it has already stopped its S3

Server

timer and will restart it once the service that is in

progress is processed completely.

Figure 5 — Physical communication during non-default session – functionally addressed

TesterPresent

6.3.5.1.3.2 Physically addressed TesterPresent (3E hex) message

Figure 6 graphically depicts the timing handling in the client and the server when performing physical

communication during a non-default session (e.g. programmingSession) and using a physically addressed

TesterPresent (3E hex) request message that requires a response message from the server to keep the

diagnostic session active in case of the absence of any other diagnostic service.

B55EB1B3C7662F79D1B59483A53B9F2F82C98BEEB7939EA95CF14FFEE5FB13B925D84A2690B319CCC3FB33EC1A0EE19ACE32C3AD48AA2003E27076E26B823E886461F4EB146348E75A2E06040CBB18

Normen-Download-Beuth-MOWAG GmbH-KdNr.2337322-LfNr.2988619001-2005-11-07 16:16

剩余99页未读，继续阅读

ernieskaggs

粉丝: 0
资源: 1

ISO 15765-3: 诊断控制器局域网（CAN）统一诊断服务实施

ISO15765-3中文版

ISO15765-3车载诊断标准-详细中文版.pdf

ISO15765-3.pdf

iso15765-3

iso15765-1-2-3-4pdf.zip

can应用层协议ISO 15765-3

iso15765-1-2-3-4全套中英文版本

iso_15765-3

ISO 15765-2 (中文)

iso15765-4 2016

最新资源