logo资料库

UDS协议:基于CAN.pdf

第1页 / 共31页
第2页 / 共31页
第3页 / 共31页
第4页 / 共31页
第5页 / 共31页
第6页 / 共31页
第7页 / 共31页
第8页 / 共31页
资料共31页,剩余部分请下载后查看
Testing Expo North America 2008 Introduction to Standardized Diagnostic Communication: UDS on CAN (ISO 15765) with MVCI (ISO 22900) and ODX (ISO 22901) Dipl.-Ing. Peter Subke Key Account Manager Automotive Electronics Softing AG, Germany sub@softing.com
Onboard Communication 2 ECU # 1 ECU # 2 Input Info Output Info Input Info Output Info in-vehicle network (e.g. CAN bus) onboard communication ECUs convert input information from sensors to output information for actuators. ECUs send information to other ECUs and receice information from other ECUs (onboard communication). For onboard communication, ECUs are interconnected via an in-vehicle network (e.g. CAN)
Diagnostic Communication 3 ECU # 1 ECU # 2 Input Info Output Info Input Info Output Info For diagnostic communication, a TESTER is connected to the in-vehicle network. TESTER The TESTER (client) sends a request to a specific ECU (e.g. #1) and the ECU (server) answers the request with a response.
Diagnostic Services 4 Diagnostic communication requires a diagnostic protocol. A diagnostic protocol contains a set of communication parameters and diagnostic services (request / response). Typical examples for diagnostic protocols include KWP2000 and UDS. ISO 14229-1(2006) : Road vehicles –Unified diagnostic services (UDS) specifies a diagnostic protocol on layer 7 of the OSI model. Examples for diagnostic services of ISO 14229 include: 11hex = ECU reset 86hex = response on event 19hex = read DTC information 23hex = read memory by address 31hex = routine control 36hex = transfer data
UDS on CAN 5 Today, diagnostic communication uses the existing in-vehicle network to transport requests and responses. The transport protocol for UDS on CAN is specified in ISO 15765-3 (2004): Road vehicles – Diagnostics on controller area network (CAN) – Part 3: Implementation of unified diagnostic services (UDS on CAN) ISO 14229-1:2006 (UDS) and ISO 15765-3:2004 (Diagnostics on CAN) are complementary standards that together specify the diagnostic protocol “UDS on CAN”.
Communication system 6 Tester Applications (e.g. MONACO, INCA, LabView, AD Databases (EDF, ODX, FBX,CANdb, A2L) D-Server (EDIABAS, ETESTER, COS, MVCI) PC-to-ECU interface software e.g. EIDBSS, Vecom, D-PDU API PC-to-ECU interface hardware e.g. ETK, EDIC, DCDI, VCI Onboard communication CAN, LIN, FlexRay, MOST Diagnostic communication Diagnostic protocols KWP 2000, UDS on CAN UDS on FlexRay ECU software (e.g. AUTOSAR)
Components of a PC-based Tester 7 Editor Application Database Basesystem PC-to-ECU-Interface in-vehicle network (e.g. CAN) PC hardware e r a w t f o s C P ECU
OEM-specific PC-based Tester (examples) 8 Editor TST CBF E-TESTER 6 Basesystem DCDI BEST/2 VAS 5163 EDF EDIABAS EDIC
分享到:
收藏