Unified Diagnostic Services (UDS) is a diagnostic communication protocol used in electronic control units (ECUs) within automotive electronics, which is specified in the ISO 14229-1.[1] It is derived from ISO 14230-3 (KWP2000) and the now obsolete ISO 15765-3 (Diagnostic Communication over Controller Area Network (DoCAN)[2]). 'Unified' in this context means that it is an international and not a company-specific standard. By now this communication protocol is used in all new ECUs made by Tier 1 suppliers of Original Equipment Manufacturer (OEM), and is incorporated into other standards, such as AUTOSAR. The ECUs in modern vehicles control nearly all functions, including electronic fuel injection (EFI), engine control, the transmission, anti-lock braking system, door locks, braking, window operation, and more.
ISO 14229-3 also describes a set of mappings between ISO 14229-2 and ISO 15765-2 (ISO-TP) and describes requirements related to 11-bit and 29-bit CAN IDs when these are used for UDS and legislated OBD as per ISO 15765-4.
iso 15765 2 pdf 28
For UDS on CAN, ISO 15765-2 describes how to communicate diagnostic requests and responses. In particular, the standard describes how to structure CAN frames to enable communication of multi-frame payloads. As this is a vital part of understanding UDS on CAN, we go into more depth in the next section.
However, part of the confusion may arise because ISO 14229-3 also provides an OSI model where DoCAN is both used in relation to ISO 15765-2 and as an overlay across OSI model layers 2 to 7. In ISO 14229-2, DoCAN is referred to as the communication protocol on which UDS (ISO 14229-1) is implemented. This is in sync with the illustration from ISO 14229-3. In this context, DoCAN can be viewed as a more over-arching term for the implementation of UDS on CAN, whereas UDSonCAN seems consistently to refer to ISO 14229-3 only.
On a separate note, ISO 15765-4 states that enhanced diagnostics requests/responses may utilize the legislated OBD2 CAN ID range as long as it does not interfere - which is what we are seeing in this specific Hyundai Kona example where the IDs 0x7EC/0x7E4 are used for proprietary data.
This standard contributes to the following Sustainable Development Goal: 9 Industry, Innovation and Infrastructure Buy this standard en Format Language std 1 187 PDF + ePub English std 2 187 Paper English CHF187 Buy
Buy this standard Life cycle Previously Withdrawn ISO 15765-2:2011 Now Published ISO 15765-2:2016 A standard is reviewed every 5 yearsStage: 90.92 (To be revised) 00 Preliminary 10 Proposal 10.99 2014-09-09 New project approved 20 Preparatory 30 Committee 30.99 2014-09-09 CD approved for registration as DIS 40 Enquiry 40.00 2014-12-22 DIS registered 40.20 2015-03-19 DIS ballot initiated: 12 weeks 40.60 2015-06-21 Close of voting 40.99 2015-12-11 Full report circulated: DIS approved for registration as FDIS 50 Approval 50.00 2016-02-09 Final text received or FDIS registered for formal approval 50.20 2016-02-12 Proof sent to secretariat or FDIS ballot initiated: 8 weeks 50.60 2016-02-22 Close of voting. Proof returned by secretariat 60 Publication 60.00 2016-02-22 International Standard under publication 60.60 2016-04-12 International Standard published 90 Review 90.20 2021-04-15 International Standard under systematic review 90.60 2021-09-03 Close of review 90.92 2021-11-19 International Standard to be revised 90.93 International Standard confirmed 90.99 Withdrawal of International Standard proposed by TC or SC 95 Withdrawal 95.99 Withdrawal of International Standard Will be replaced by Under development ISO/DIS 15765-2 Got a question?Check out our FAQs
2ff7e9595c
Comments