ISO 14229-1 道路车辆统一诊断服务简述

Saturday, 07 March 2020 16:17

ISO 14229-1 道路车辆统一诊断服务简述 ^Featured

ISO 14229-1 UDS在各种数据链路的未来实现

概述

定义诊断系统的通用需求-与数据链路无关的诊断服务

OSI各层	增强的诊断服务（与排放无关〉
应用层	ISO 14229-1I ISO 15765-3	ISO 14229-1I其它标准
表示层	．	．
会话层	ISO 15765-3	．
传输层	ISO 15765”2	．
网络层	ISO 15765-2	．
数据链路层	ISO 11898-1	．
物理层	ISO 11898	．

ISO 14229-1 UDS在各种数据链路的未来实现

ISO 14229-1统一诊断.规范和需求

ISO 15765-3

CAN 诊断

未来

无线诊断 LAN

Flexray诊断

...

应用层接口服务

.应用层服务概述

服务原语（6个）

请求 request
请求_确认 req_confirm
指示 indication
响应 response
响应一确认 rsp_confirm
确认 conf irm

有确认服务
无确认服务

有确认服务

客户端应用层 (Client) 服务器端应用层(Server)

service_name.request, service_name.req_confirm,service name.confirm,service name.indication,service_name.response,service_name.rsp_confirm

service name.request.confirm

无确认服务

service name.request.no confirm

服务原语的格式

All application layer services have the same general format. Service primitives are written in the form:

service_name.type (

parameter A,parameter B, parameter C

[,parameter 1, ...]

)

where:

⎯ “service_name” is the name of the diagnostic service (e.g. DiagnosticSessionControl);

⎯ “type” indicates the type of the service primitive (e.g. request);

⎯ “parameter A, ...” is the A_SDU as a list of values passed by the service primitive (addressinginformation);

⎯ “parameter A, parameter B, parameter C” are mandatory parameters that shall be included in all servicecalls;

⎯ “[,parameter 1, ...]” are parameters that depend on the specific service (e.g. parameter 1 can be thediagnosticSession for the DiagnosticSessionControl service). The brackets indicate that this part of theparameter list may be empty.

request

service_name.request (

SA,

TA,

TA_type,(枚举：用于描述功能还是物理寻址方式)

[RA,] （远程地址，可选〉

[,parameter 1, ...]

)

indication

service_name.indication (

SA,

TA,

TA_type,

[RA,] （远程地址，可选〉

[,parameter 1, ...]

)

service_name.request和service_name.indication中的[,parameter 1, ...]：原语中的数据单元内容一致。

Response

service_name.response (

SA,

TA,

TA_type,

[RA,] （远程地址，可选〉

Result

[,parameter 1, ...]

)

confirm

service_name.confirm (

SA,

TA,

TA_type,

[RA,] （远程地址，可选〉

Result

[,parameter 1, ...]

)

request-confirm

service_name.req_confirm (

SA,

TA,

TA_type,

[RA,] （远程地址，可选〉

Result

)

response-confirm

service_name.rsp_confirm (

SA,

TA,

TA_type,

[RA,] （远程地址，可选〉

Result

)

车辆系统需求

客户（Tester）和服务器 C ECU）统一编址
每一个Tester和ECU的地址是唯一的
RA C 远程地址〉独立分配

外部测试设备	241 200	网关	10 62	远程服务器
	主网络		远程网络

远程诊断示例1：Remote server example with remote network

The external test equipment sends a remote diagnostic request message with

⎯ SA = 241 (F1 hex),

⎯ TA = 200 (C8 hex),

⎯ RA = 62 (3E hex).

The gateway receives the message and sends it out on the remote network with

⎯ SA = 10 (0A hex),

⎯ TA = 62 (3E hex),

⎯ RA = 241 (F1 hex).

The remote server receives the message.

The remote server sends back a remote diagnostic response message with

⎯ SA = 62 (3E hex),

⎯ TA = 10 (0A hex),

⎯ RA = 241 (F1 hex).

The gateway receives the message and sends it out on the main network with

⎯ SA = 200 (C8 hex),

⎯ TA = 241 (F1 hex),

⎯ RA = 62 (3E hex).

The external test equipment receives the message.

test figure1

远程诊断示例2（上图）：Remote server example without remote network

The external test equipment sends a remote diagnostic request message with

⎯ SA = 241 (F1 hex),

⎯ TA = 200 (C8 hex),

⎯ RA = 62 (3E hex).

The gateway receives the message and passes it over to the remote server function. The remote serverreceives the message.

The remote server sends back a remote diagnostic response message by passing it to the gateway function.The gateway receives the message and sends it out on the main network with

⎯ SA = 200 (C8 hex),

⎯ TA = 241 (F1 hex),

⎯ RA = 62 (3E hex).

The external test equipment receives the message.

远程诊断示例2：Remote client example with remote network

test figure2

The external test equipment sends a remote diagnostic request message with

⎯ SA = 242 (F1 hex),

⎯ TA = 10 (0A hex),

⎯ RA = 18 (12 hex).

The gateway receives the message and sends it out on the main network with

⎯ SA = 200 dec,

⎯ TA = 18 dec,

⎯ RA = 242 dec.

The local server receives the message.

The local server sends back a remote diagnostic response message with

⎯ SA = 18 (12 hex),

⎯ TA = 200 (C8 hex),

⎯ RA = 242 (F1 hex).

The gateway receives the message and sends it out on the remote network with

⎯ SA = 10 (0A hex),

⎯ TA = 242 (F1 hex),

⎯ RA = 18 (12 hex).

The external test equipment receives the message.

应用层协议

A_SDU: 应用层服务数据单元

Application Layer Service Data Unit

SA, TA, TA_type [,RA] [,parameter1,...]

A_PDU : 应用层协议数据单元

Application Layer Protocol Data Unit SA, TA, TA_type [,RA],A_Data

A_Data=A_PCl+[parameter1,...]

A_PCI: 应用层协议控制信息

Application Layer Protocol Control Information

A_PUD = A_PCI+ A _SDU

应用层协议控制信息

2种不同的格式〈由服务原语和Result参数决定〉
A_PCI (SI)

SI: Service ID(Request服务和Result=positive的Response)

类型：1字节无符号整数

范围：00~FF

A_PCl(NR_Sl,SI)

NR_SI-Negative Service ID

类型：1字节无符号整数

范围：7F

服务标识符SI

服务标识Service identifier (hex value)

服务类型Service type (bit 6)

定义文档Where defined

00 – 0F

OBD service requests/ OBD 服务请求

ISO 15031-5

10 – 3E

ISO 14229 service requests/ ISO 14229服务请求

ISO 14229

Not applicable 未应用

Reserved by document保留

40 – 4F

OBD service responses/ OBD 服务响应

ISO 15031-5

50 – 7E

ISO 14229 positive service responses/ ISO 14229服务肯定响应

ISO 14229

Negative response service identifier 否定响应标识

ISO 14229

Not applicable未应用

Reserved by ISO 14229/ISO 14229保留

81 – 82

Not applicable未应用

Reserved by ISO 14230/ISO 14230保留

83 – 88

ISO 14229 service requests/ISO 14229服务请求

ISO 14229

89 – 9F

Service requests服务请求

Reserved for future expansion as needed为将来需求扩展保留

A0 – B9

Service requests服务请求

Defined by vehicle manufacturer汽车制造商定义

BA – BE

Service requests服务请求

Defined by system supplier 系统供应商定义

Not applicable未应用

Reserved by document保留

Not applicable未应用

Reserved by ISO 14229/ISO 14229保留

C1 – C2

Not applicable未应用

Reserved by ISO 14230/ISO 14230保留

C3 – C8

ISO 14229 positive service responses/ ISO 14229服务肯定响应

ISO 14229

C9 – DF

Positive service responses服务肯定响应

Reserved for future expansion as needed为将来需求扩展保留

E0 – F9

Positive service responses服务肯定响应

Defined by vehicle manufacturer汽车制造商定义

FA – FE

Positive service responses服务肯定响应

Defined by system supplier系统供应商定义

Not applicable未应用

Reserved by document 保留

请求服务标识符SI

类型：1字节无符号整数

范围：00~FF

请求服务的ID: X0XXXXXX（第6位为0)

示例：ReadDTClnformation服务Request 0x19 B00011001

肯定响应服务标识符SI

类型：1字节无符号整数

范围：00~FF

肯定响应服务的ID: X1XXXXXX （第6位为1)

肯定响应服务的ID =请求服务的ID+0x40

示例：ReadDTClnformation服务Response 0x59 B01011001

否定响应服务标识符NR_SI

类型：1字节无符号整数

范围：7F

Negative response A_PDU

Each diagnostic service has a negative response/negative confirmation message specified with messageEach diagnostic service has a negative response/negative confirmation message specified with messageA_Data bytes according to Table 3. The first A_Data byte (A_PCI.NR_SI) is always the specific negativeresponse service identifier. The second A_Data byte (A_PCI.SI) shall be a copy of the service identifier valuefrom the service request/indication message to which the negative response message corresponds.

A_PDU parameter

Parameter name

Cvt 约定

Hex value

Mnemonic

Source Address

M^a

Target Address

TA_type

Target Address type

TA_type

Remote Address (optional)

C^b

A_Data.A_PCI.NR_SI

Negative Response Service Id

SIDNR

A_Data.A_PCI.SI

Request Service Id

SIDRQ

A_Data.Parameter 1

responseCode

NRC_

a M (Mandatory): In case the negative response A_PDU is issued then those A_PDU parameters shall be present.
b C (Conditional): The RA (Remote Address) PDU parameter is only present in case of remote addressing.

Service description conventions

This clause defines how each diagnostic service is described in ISO 14229. It defines the general serviceThis clause defines how each diagnostic service is described in ISO 14229. It defines the general servicedescription format of each diagnostic service.This clause gives a brief outline of the functionality of the service. Each diagnostic service specification startswith a description of the actions performed by the client and the server(s) which are specific to each service.The description of each service includes a table which lists the parameters of its primitives: request/indication,response/confirmation for a positive or negative result. All have the same structure.For a given request/indication and response/confirmation A_PDU definition, the presence of each parameteris described by one of the following convention (Cvt) values given in Table 8

Table 8 A_PDU parameter conventions

Type

Name

Description

Mandatory

The parameter shall be present in the A_PDU.

Conditional

The parameter can be present in the A_PDU, based on certain criteria (e.g. sub- function/parameters within the A_PDU).

Selection

Indicates that the parameter is mandatory (unless otherwise specified) and is a selection from a parameter list.

User option

The parameter may or may not be present, depending on dynamic usage by the user.

NOTE The “ Request Service Id” marked as “M” (Mandatory) shall not imply that this service must be supported by the server. The “M” only indicates the mandatory presence of this parameter in the request A_PDU if the server supports the service.

Cvt:约定

M:强制

U:用户选择

C:是否使用依赖于其它参数

S:强制从参数列表中选择〈枚举类型〉

请求A_PDU

A_PDU parameter

Parameter name

Cvt

Hex value

Source Address

Target Address

TA_type

Target Address type

A_Data.A_PCI.SI

Request Service Identifier

A_Data.

Parameter 1
.
.

Parameter n

.
.

]

M/U/C/S

XX:[

.
.

XX]

请求示例〈带子功能〉Request A_PDU definition with sub-function

A_PDU parameter

Parameter name

Cvt

Hex value

Mnemonic

Source Address

Target Address

TA_type

Target Address type

TAT

Remote Address

A_Data.A_PCI.SI

Request Service Id

SIDRQ

A_Data. Parameter 1

sub-function = [
parameter]

LEV_ PARAM

Parameter 2
:
Parameter k

data-parameter#1
:
data-parameter#k-1

U
: U

xx
:
xx

DP_…#1
:
DP_…#k-1

C: The RA (Remote Address) PDU parameter is only present in case of remote addressing.

请求示例〈不带子功能〉Request A_PDU definition without sub-function

A_PDU parameter

Parameter name

Cvt

Hex value

Mnemonic

Source Address

Target Address

TA_type

Target Address type

TAT

Remote Address

A_Data.A_PCI.SI

Request Service Id

SIDRQ

A_Data. Parameter 1
:
Parameter k

data-parameter#1
:
data-parameter#k

U
: U

xx
:
xx

DP_…#1
:
DP_…#k

C: The RA (Remote Address) PDU parameter is only present in case of remote addressing.

服务描述约定

子功能参数$Level(LEV＿）的定义

1字节数据
Bit7: 禁止肯定响应指示位suppressPosRspMsglndicationBit

0: FALSE：需要肯定响应

1: TRUE：禁止肯定响应

Bit6: 子功能参数值（0x00~0x7F)

使用子功能参数字节，但仅支持

suppressPosRspMsglndicationBit 的服务必须支持0x0子功能

Request message sub-function parameter $Level (LEV_) definition

Request message sub-function parameter $Level (LEV_) definitionThis subclause defines the sub-function $levels (LEV_) parameter(s) defined for the request/indication of theservice .

This subclause does not contain any definition for cases where the described service does not use a subfunctionparameter value and does not utilize the suppressPosRspMsgIndicationBit (this implicitly indicatesthat a response is required).

The sub-function parameter byte is divided into two parts (on bit-level) as defined in Table 11.

Table 11 — Sub-function parameter structure

Bit position

Description

suppressPosRspMsgIndicationBit
This bit indicates if a positive response message shall be suppressed by the server.
'0' = FALSE, do not suppress a positive response message (a positive response message is required).
'1' = TRUE, suppress response message (a positive response message shall not be sent; the server being addressed shall not send a positive response message).
Independent of the suppressPosRspMsgIndicationBit, negative response messages are sent by the server(s) according to the restrictions specified in 7.5.

6-0

sub-function parameter value
The bits 0-6 of the sub-function parameter contain the sub-function parameter value of the service (00 - 7F hex).
Each service utilizing the sub-function parameter byte, but only supporting the suppressPosRspMsgIndicationBit has to support the zeroSubFunction sub-function parameter value (00 hex).

The sub-function parameter value is a 7-bit value (bits 6-0 of the sub-function parameter byte) that can haveThe sub-function parameter value is a 7-bit value (bits 6-0 of the sub-function parameter byte) that can havemultiple values to further specify the service behaviour.

Each service only supporting the suppressPosRspMsgIndicationBit has to support the zeroSubFunctionEach service only supporting the suppressPosRspMsgIndicationBit has to support the zeroSubFunction(00 hex).

Services supporting sub-function parameter values in addition to the suppressPosRspMsgIndicationBit shallServices supporting sub-function parameter values in addition to the suppressPosRspMsgIndicationBit shallsupport the sub-function parameter values as defined in the sub-function parameter value table.

Each service contains a table that defines values for the sub-function parameter values, taking into accountEach service contains a table that defines values for the sub-function parameter values, taking into accountonly the bits 0-6.

Table 12 — Request message sub-function parameter definition

Hex (bit 6-0)

Description

Cvt

Mnemonic

sub-function#1
description of sub-function parameter#1

M/U

SUBFUNC1

sub-function#m
description of sub-function parameter#m

M/U

SUBFUNCm

The convention (Cvt) column in the table above shall be interpreted as follows.The convention (Cvt) column in the table above shall be interpreted as follows.

Table 13 — Sub-function parameter conventions

Type

Name

Description

Mandatory

The sub-function parameter has to be supported by the server if the service is supported.

User option

The sub-function parameter may or may not be supported by the server, depending on the usage of the service.

The complete sub-function parameter byte value is calculated based on the value of theThe complete sub-function parameter byte value is calculated based on the value of thesuppressPosRspMsgIndicationBit and the sub-function parameter value chosen.

Table 14 — Calculation of the sub-function byte value

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Bit 0

SuppressPosRspMsg- IndicationBit

Sub-function parameter value as specified in the sub-function parameter value table of the service

Resulting sub-function parameter byte value (bit 7 - 0)

Request message data parameter definition

This subclause defines the data-parameter(s) $DataParam (DP_) for the request/indication of the serviceThis subclause defines the data-parameter(s) $DataParam (DP_) for the request/indication of the service. This subclause does not contain any definition if the described service does not use anydata parameter. The data parameter portion can contain multiple bytes. This subclause provides a genericdescription of each data parameter; detailed definitions can be found in the annexes of this document. Theannexes also specify whether a data parameter shall be supported or is user-optional to be supported if theserver supports the service.

Table 15 — Request message data parameter definition

Definition

data-parameter#1
description of data-parameter#1

data-parameter#n
description of data-parameter#n

肯定响应A_PDU Positive response A_PDU

A_PDU parameter

Parameter name

Cvt

Hex value

Mnemonic

Source Address

Target Address

TA_type

Target Address type

TAT

Remote Address

A_Data.A_PCI.SI

Response Service Id

SIDPR

A_Data.Parameter 1
:
A_Data.Parameter n

data-parameter#1
:
data-parameter#n

xx
:
xx

DP_…#1
:
DP_…#n

C: The RA (Remote Address) PDU parameter is only present in case of remote addressing.

否定响应A PDU

A_PDU parameter

Parameter name

Cvt

Hex value

Source Address

Target Address

TA_type

Target Address type

Remote Address

A_Data.A_PCI.NR_SI

NR_SI

A_Data.A_PCI.SI

A_Data.Parameter

Response Code

Request message flow example

Message direction:

client ® server

Message type:

Request

A_Data byte

Description (all values are in hexadecimal)

Byte value (hex)

Mnemonic

#1 (A_PCI)

request Service Id

SIDRQ

#2
:
#n

sub-function/data-parameter#1
:
data-parameter#m

xx xx
xx

LEV_/DP_ DP_
DP_

Positive response message flow example

Message direction:

server ® client

Message type:

Response

A_Data

Description (all values are in hexadecimal)

Byte value (hex)

Mnemonic

#1 (A_PCI)

response Service Id

SIDPR

#2
:
#n

data-parameter#1
:
data-parameter#n-1

xx
:
xx

DP_
:
DP_

Negative response message flow example

Message direction:

server ® client

Message type:

Response

A_Data

Description (all values are in hexadecimal)

Byte value (hex)

Mnemonic

#1 (A_PCI.NR_SI)

Negative Response Service Id

SIDRSIDNRQ

#2 (A_PCI.SI)

request Service Id

SIDRQ

responseCode

NRC_

Supported negative response codes (常见：11，12，13，31，78)

Hex

Description

Cvt

Mnemonic

Service not supported

服务器不支持客户端请求的诊断服务

SNS

subFunctionNotSupported

服务器不支持客户端请求服务的子功能

Send if the sub-function parameter in the request message is not supported.

SFNS

incorrectMessageLengthOrInvalidFormat

请求报文的数据长度（或者格式〉不符合标准
The length of the message is wrong.

IMLOIF

conditionsNotCorrect
This code shall be returned if the criteria for the request SecurityAccess are not met.

CNC

requestSequenceError
Send if the “sendKey” sub-function is received without first receiving a “requestSeed” request message.

RSE

requestOutOfRange

请求超出范围

This code shall be sent if the user-optional securityAccessDataRecord contains invalid data.

ROOR

invalidKey
Send if an expected “sendKey” sub-function value is received and the value of the key does not match the server's internally stored/calculated key.

exceededNumberOfAttempts
Send if the delay timer is active due to exceeding the maximum number of allowed false access attempts.

ENOA

requiredTimeDelayNotExpired
Send if the delay timer is active and a request is transmitted.

RTDNE

requestCorrectlyReceived-ResponsePending

服务器正忙，暂时无法处理客户端发出的请求

RCRRP

服务响应的执行规则Server response implementation rules

对带子功能参数的请求消息的响应

The following subclauses specify the behaviour of the server when executing a service. The server and theThe following subclauses specify the behaviour of the server when executing a service. The server and theclient shall follow these implementation rules.

Abbreviation	Description
suppressPosRspMsgIndicationBit	TRUE = server shall NOT send a positive response message FALSE = server shall send a positive or negative response message
PosRsp	positive response message
NegRsp	negative response message
NoRsp	NOT sending a positive or negative response message
NRC	negative response code
ALL	All of the requested data parameters (service without sub-function parameter) of the client request message are supported by the server
at least 1	At least 1 data parameter (service without sub-function parameter) of the client request
NONE	None of the requested data parameters (service without sub-function parameter) of the client request message is supported by the server

The server shall support its list of diagnostic services regardless of addressing mode (physical, functionalThe server shall support its list of diagnostic services regardless of addressing mode (physical, functionaladdressing type).

IMPORTANT — As required by the tables in the following subclauses, negative response messageswith negative response codes of SNS (serviceNotSupported), SFNS (subFunctionNotSupported) andROOR (requestOutOfRange) shall never be transmitted when functional addressing was used for therequest message.

Request message with sub-function parameter and server response behaviour

对物理寻址的客户端请求消息Physically addressed client request message

Server case #

服务器情况编号

Client request message 客户请求消息

Server capability 服务器能力

Server response

服务器的响应

Comments on server response

服务器的响应的注释

Addressin g
scheme

寻址方式

subFunction (suppress- PosRspMsg- Indication- Bit)

子功能〈禁止肯定响应消息指示位〉

Service ID supported

支持该服务标识符

Sub- function supported

支持该子功能

Data parameter supported (only if applicable)

Message

消息

Negative: NRC/
section

否定响应

码(NRC)

physical

物理寻址

FALSE
(bit = 0)

YES

At least 1

PosRsp

—

Server sends positive response 服务器发送肯定响应

—

NegRsp

NRC=xx

Server sends negative response because error occurred reading the data parameters of the request message 服务器发送否定响应，因为读请求消息的数据参数时发生错误

—

NRC=SNS

Negative response with NRC 11 hex 带NRC=0x11 的否定响应

YES

—

NRC=SFNS

Negative response with NRC 12 hex 带NRC=0x12 的否定响应

TRUE
(bit = 1)

YES

At least 1

NoRsp

—

Server does NOT send a response 服务器不发送响应

—

NegRsp

NRC=xx

Server sends negative response because error occurred reading the data parameters of the request message 服务器发送否定响应，因为读请求消息的数据参数时发生错误

—

NRC=SNS

Negative response with NRC 11 hex 带NRC=0x11 的否定响应

YES

—

NRC=SFNS

Negative response with NRC 12 hex 带NRC=0x12 的否定响应

Functionally addressed client request message

Server case #

Client request message

Server capability

Server response

Comments on server response

Addressing scheme

subFunction (suppress- PosRspMsg- Indication- Bit)

Service ID supported

Sub- function supported

Data parameter supported (only if applicable) 支持的参数

Message

Negative: NRC/
section

functional

功能寻址

FALSE
(bit = 0)

YES

At least 1至少一个

PosRsp

—

Server sends positive response 服务器发送肯定响应

At least 1至少一个

NegRsp

NRC=xx

Server sends negative response because error occurred reading the data parameters of the request message 服务器发送否定响应，因为读请求消息的数据参数时发生错误

None

NoRsp

—

Server does NOT send a response服务器不发送响应

—

Server does NOT send a response服务器不发送响应

YES

—

Server does NOT send a response服务器不发送响应

TRUE
(bit = 1)

YES

At least 1至少一个

NoRsp

—

Server does NOT send a response服务器不发送响应

At least 1至少一个

NegRsp

NRC=xx

Server sends negative response because error occurred reading the data parameters of the request message 服务器发送否定响应，因为读请求消息的数据参数时发生错误

None

NoRsp

—

Server does NOT send a response服务器不发送响应

—

Server does NOT send a response服务器不发送响应

YES

—

Server does NOT send a response服务器不发送响应

对不带子功能参数的请求消息的晌应Request message without sub-function parameter and server response behaviour

Physically addressed client request message

Server case #

Client request message

Server capability

Server response

Comments on server response 服务器的响应的注释

Addressing scheme

Service ID supported

Parameter supported

Message

Negative: NRC/section

physical

YES

ALL 所有参数

PosRsp

—

Server sends positive response 服务器发送肯定响应

At least 1 至少一个

—

Server sends positive response 服务器发送肯定响应

At least 1, more than 1, or ALL

至少一个参数，多于一个参数，或所有参数

NegRsp

NRC=xx

Server sends negative response because error occurred reading data parameters of request message

服务器发送否定响应，因为读请求消息的数据参数时发生错误

NONE

NRC=ROOR

Negative response with NRC 31 hex 带NRC=0x31的否定响应

—

NRC=SNS

Negative response with NRC 11 hex 带NRC=0x11的否定响应

Functionally addressed client request message

Server case #

Client request message

Server capability

Server response

Comments on server response 服务器的响应的注释

Addressing scheme

Service ID supported

支持该服务标识符

Parameter supported

支持的参数

Message

消息

Negative: NRC/section

否定：响应码/部分

functional

功能寻址

YES

YES 所有参数

PosRsp

—

Server sends positive response 服务器发送肯定响应

at least 1 至少一个

—

Server sends positive response 服务器发送肯定响应

At least 1,
more than 1, or ALL

至少一个参数，多于一个参数，或所有参数

NegRsp

NRC=xx

Server sends negative response because error occurred reading data parameters of request message

服务器发送否定响应，因为读请求消息的数据参数时发生错误

NONE

NoRsp

—

Server does NOT send a response 服务器不发送响应

—

Server does NOT send a response 服务器不发送响应

各功能单元具体服务描述

标准下载(英文版-2013):

ISO 14229-1-2013规格和要求.pdf

ISO 14229-2-2013会话层服务.PDF

ISO 14229-3-2012在CAN实施上的统一诊断服务.pdf

ISO 14229-4-2012在FlexRay实施上的统一诊断服务.pdf

ISO 14229-5_2013互联网协议实施上的统一诊断服务.pdf

ISO 14229-6-2013在K线上的诊断服务.pdf

Read 14551 times Last modified on Tuesday, 28 April 2020 01:01

Published in Automobile communication protocol

Tagged under

Download attachments:

ISO 14229-1-2013规格和要求.pdf (12862 Downloads)
ISO 14229-3-2012在CAN实施上的统一诊断服务_1588006799.pdf (13807 Downloads)
ISO 14229-2-2013会话层服务.PDF (13729 Downloads)
ISO 14229-4-2012在FlexRay实施上的统一诊断服务.pdf (13822 Downloads)
ISO 14229-5_2013互联网协议实施上的统一诊断服务.pdf (13669 Downloads)
ISO 14229-6-2013在K线上的诊断服务.pdf (13260 Downloads)

Blue Star

Latest from Blue Star

Related items

More in this category: « ISO14229-2006-2013 ISO11898 »

Sidebar