新能源系统诊断规范文档格式.docx

1、故障诊断码BS Block sizeSTminMinimum Separation Time C有条件的M强制性执行U用户选用TBD待定义SID服务标识符DID数据标识符NRC负响应码UDS统一的诊断服务Server服务器Client客户端ECU电控单元1. 参考文献NO.参考文档题目1 ISO11898-1: 2003 Road vehicles - Controller area network （CAN） Part 1:Data link layer and physical signaling 2 ISO11898-2:Part 2: High-speed medium access

2、unit 3 ISO11898-5: 2007 Part 5: High-speed medium access unit with low-power mode 4 ISO15765-2: 2004 Road Vehicle - Diagnostic on CAN Networking Layer Services 5 ISO15765-3:Part 3: Application Layer Services 6 ISO14229-1: 2006 Road Vehicle - Diagnostic Systems Diagnostic Services Specification 7 ISO

3、15031-6: 2005 Road vehicles - Communication between vehicle and external equipment for emission-related diagnostic Part 6: Diagnostic trouble code definitions 2. 网络拓扑“由网络工程师统一发布网络拓扑”Fig 1. C70GB-2014整车网络拓扑结构3. 诊断接口Fig 2. OBD诊断接口管脚描述1EVBUS CAN_H2/34接地56789EVBUS CAN_L10111213141516电源Tab 1. OBD 诊断接口针脚定

4、义“由线束工程师统一发布OBD接口定义”4. 诊断需求4.1. 诊断协议4.1.1. 物理层物理层应满足ISO11898-2要求及北京新能源汽车股份有限公司企业标准新能源汽车高速 CAN 网络节点级电子控制单元（ ECU）技术要求要求。4.1.2. 数据链路层数据链路层应满足ISO11898-1要求。所有诊断请求和应答帧的数据长度应为8字节，否则电控单元将忽略该诊断请求帧。当诊断响应长度不足8字节时，空余的字节应用0xAA填充。4.1.3. 网络层网络层应满足ISO15765-2要求和下述要求：4.1.3.1. 寻址方式可以支持物理寻址和功能寻址。诊断消息ID描述见下表：控制器名称简称物理寻址

5、诊断请求ID（Hex）诊断响应ID（Hex）功能寻址诊断请求ID（Hex）实施网段驱动电机控制器MCU0x7E00x7E80x7DFEVBUSTab 2. 诊断 ID列表“由网络工程师统一发布所有诊断ID分配，各系统填写各自的诊断ID至上表”4.1.3.2. 网络层时间参数ParameterValueUnit - STmin 20msTimeout Performance Requirement N_As/N_Ar 70 n/a ms N_Br N_Bs 150 N_Cs N_Cr Tab 3. 网络层时间参数需求4.1.4. 应用层时间参数Min Max P2server 0 50 P2cl

6、ient P2*server 2000 P2* clientn/a5000P3client_phys2 P3client_func P2server_max Nominal S3server 5000 S3client 4000 Tab 4. 应用层时间参数需求4.2. Diagnostic Services（ISO14229-1）Services shall be implemented according to ISO14229-1. Additional details are specified in this section.4.2.1. Supported Diagnostic S

7、ervicesThe overview of ECU supported diagnostic services is described in the following table.Table 5 Supported diagnostic services of ECUDiagnostic Services ListSessionSecurityAccessAddressingSID （Hex）Service NameDefaultExtendedProgrammingPhysical AddressFunction AddressDiagnosticSessionControl EcuR

8、eset27SecurityAccess28CommunicationControl3ETesterPresent85ControlDTCSetting22ReadDataByIdentifier2EWriteDataByIdentifier132FInputOutputControlByIdentifierClearDiagnosticInformation19ReadDTCInformation31RoutineControl34RequestDownLoad36TransferData37RequestTransferExit说明：访问权限1表示需要扩展安全级权限，3表示需要编程安全级权

9、限。The services need to support suppressPositveResponseBit （SPRS） are showed in following table.Tab 5. Services supported SPRS bitSupportSPRS bit（Hex）DiagnosticSessionControlInputOutputContorlByIdentifierRequestDownloadThe negativeResponseCodes （NRC） used by ECU are defined as follows:Tab 6. Negative

10、 Response CodesNRC（Hex）Description11HserviceNotSupported12HsubFunctionNotSupported13HincorrectMessageLengthOrInvalidFormat22HconditionsNotCorrect24HrequestSequenceError36HexceededNumberOfAttempts31HrequestOutOfRange33HsecurityAccessDenied37HrequiredTimeDelayNotExpired35HInvalidKey72HgeneralProgrammi

11、ngFailure78HresponsePending7FHserviceNotSupportedInActiveSession92H/93HVoltageTooHigh / voltageTooLow7EHsubFunctionNotSupportedInActiveSessionIf two or more NRCs are reasonable, the ECU could send the negative response message according to the following priority rules： The 7Fh NRC have the highest p

12、riority; For others, the NRC with smaller number has higher priority.4.2.2. DiagnosticSessionControl（10H）This service is used by the client to enable different diagnostic sessions in the server（s）. A diagnostic session enables a specific set of diagnostic services in the server（s）.4.2.2.1. Message F

13、ormatRequest：ByteNameCvtValue（hex）#1RequestServiceIdentifier#2Sub-function = DefaultSession ProgrammingSessionExtendedDiagnosticSession 010203Positive Response：PositiveResponseServiceIdentifier50Sub-Function=DefaultSessionProgrammingSessionP2server =#3byte#100-FF#4byte#2P2*server =#5#6Timing P2serve

14、r value is provided in 1ms resolution.Timing P2*server value is provided in 10ms resolution.Negative Response：NegativeResponseServiceIdentifier7FNegativeResponseCodeSub-function Parameter DefinitionHEXDescription 01 This diagnostic session enables the default diagnostic session in the server（s）and d

15、oes not support any diagnostic application timeout handling provisions. . no TesterPresent service is necessary to keep the session active）.This diagnostic session enables all diagnostic services required to supported the memory programming of a server.03 ExtendedDiagnosticSessionThis diagnostic ses

16、sion can . be used to enable all diagnostic services required to support the adjustment of functions like “Idle Speed, CO Value, etc.” in the servers memory. It can also be used to enable diagnostic services, which are not specifically tied to the adjustment of functions.Negative Response Codes （NRC

17、）12 The sub-function parameter in the request message is not supported.13 The length of the message is wrong.22 The ECUcurrent conditions do not allow the change ofdiagnostic Session.4.2.2.2. Implementation RulesThis service is used by the diagnostic tool to enable different types of diagnostic sess

18、ions in a server. In order to execute a diagnostic service the appropriate session has to be started shall be only one diagnostic session active at a time.Normal/Default Session （01h） shall be enabled automatically by the ECU if no diagnostic session has been requested at power up.The ECU shall retu

19、rn to Normal/Default Session （01h） after timeout of ExtendedDiagnostic Session.The ECU shall be capable of providing all diagnostic functionality defined for the default diagnostic session under normal operating conditions.The ECU shall first send a DiagnosticSessionControl Positive Response （50h xx

20、） message before the new session becomes active in the ECU.A DiagnosticSessionControl Positive Response （50h xx） message shall be returned by an ECU if the diagnostic tool requests a session that is already running. If the ECU has already received the same request message previously and performed th

21、e requested operation, the ECU shall continue to perform the current operation . it is not a change of the session）.The ECU shall remain in its current diagnostic session if it is not able to switch into the requested diagnostic session.The TesterPresent （3Eh） service shall be used to keep the non-d

22、efault diagnostic sessions active by retriggering S3server. Also any other service request shall retrigger S3server.A functional TesterPresent （3Eh） request without response may be sent at any time, even regardless of any other service in progress.When receiving or transmitting any diagnostic messag

23、es, including 3Eh service, the S3servertimer will reset.Fig 3. Session transition diagram4.2.3. ECUReset （11H）This service requests the server to effectively perform an ECU reset based on the content of the ResetType parameter value （suppressPosRspMsgIndicationBit （bit 7） not shown）.4.2.3.1. Message FormatSub-Function= ResetType: HardResetSoftReset51Sub-Function= ResetType: