AUTOSAR CountdownAdvent Calendar 2022

ISO 14229-3:2012 Road vehicles - Unified diagnostic(1) services (UDS) - Part 3: Unified diagnostic services on CAN implementation (UDSonCAN)

Last updated at 2024-08-10Posted at 2022-02-07

ISO 14229-3:2012 Road vehicles — Unified diagnostic services (UDS) — Part 3: Unified diagnostic services on CAN implementation (UDSonCAN)
https://www.iso.org/standard/55284.html

<この項は書きかけです。順次追記します。>
This article is not completed. I will add some words in order.

2 Normative references

ISO 14229-1, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements
ISO 14229-2, Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
ISO 15765-1, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 1: General information and use case definition
ISO 15765-2, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services
ISO 15765-4, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 4: Requirements for emissions-related systems

3.2 Abbreviated terms

CF consecutive frame
DA destination address
DLC data length code
FF first frame
FC flow control
ID identifier
NA network address
SA source address
SF single frame
SM subnet mask
SOM start of message
STRT serviceToRespondTo
TA target address
UDS unified diagnostic services
USDT unacknowledged segmented data transfer
UUDT unacknowledged unsegmented data transfer

Bibliography

[1] ISO/IEC 7498-1, Information technology — Open Systems Interconnection — Basic Reference Model — The Basic Mode
[2] ISO/IEC 10731:1994, Information technology — Open Systems Interconnection — Basic Reference Model — Conventions for the definition of OSI services
[3] ISO 11898-1, Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical signalling
[4] ISO 11898-2, Road vehicles — Controller area network (CAN) — Part 2: High-speed medium access unit
[5] ISO 11898-3, Road vehicles — Controller area network (CAN) — Part 3: Low-speed, fault-tolerant, medium dependent interface
[6] ISO 11898-5, Road vehicles — Controller area network (CAN) — Part 5: High-speed medium access unit with low-power mode
[7] ISO 13400 (all parts), Road vehicles — Communication between test equipment and vehicles over Internet Protocol
[8] SAE J1930-DA, Digital Annex of Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms Web Tool Spreadsheet
[9] SAE J1939, Companion Spreadsheet (CS1939)
[10] SAE J1939-73:2010, Recommended Practice for a Serial Control and Communication Vehicle Network — Application layer — Diagnostics
[11] SAE J1979-DA, Digital Annex of E/E Diagnostic Test Modes
[12] SAE J2012-DA, Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions

6 Unified diagnostic services implementation on CAN

6.1 General

This clause defines how the diagnostic services as defined in ISO 14229-1 apply to DoCAN. For each
applicable service, the applicable sub-function and data parameters are defined.
NOTE The sub-function parameter definitions take into account that the most significant bit is used for the
suppressPosRspMsgIndicationBit parameter as defined in ISO 14229-1.

6.2 UDS on CAN services overview

The purpose of Table 2 is to reference all ISO 14229-1 and ISO 14229-2 services as they are applicable
for an implementation in ISO 14229-3, UDSonCAN. Table 2 contains the sum of all applicable services.
Certain applications using this part of ISO 14229 to implement UDSonCAN may restrict the number
of useable services and may categorize them in certain application areas/diagnostic sessions (default
session, programming session, etc.).
Services in Table 2 that are marked “No CAN specific requirements” shall be implemented as defined
in ISO 14229-1 and ISO 14229-2 with no additional restrictions. Services that are marked “CAN specific
requirements” shall be implemented as defined by the subclause listed in the Table 2 entry.
Table 2 — Overview of applicable ISO 14229-1, Unified diagnostic services and data ranges
Diagnostic service name Comment Reference in this
(ISO 14229-1) document
Diagnostic and Communication Management Functional Unit
DiagnosticSessionControl No CAN specific requirements —
ECUReset No CAN specific requirements —
SecurityAccess No CAN specific requirements —
CommunicationControl No CAN specific requirements —
TesterPresent No CAN specific requirements —
SecuredData-Transmission No CAN specific requirements —
ControlDTCSetting No CAN specific requirements —
ResponseOnEvent CAN specific requirements see 6.3
LinkControl No CAN specific requirements —
Data Transmission Functional Unit
ReadDataByIdentifier No CAN specific requirements —
ReadMemoryByAddress No CAN specific requirements —
ReadScalingDataByIdentifier No CAN specific requirements —
ReadDataByPeriodicIdentifier CAN specific requirements see 6.4
DynamicallyDefineDataIdentifier No CAN specific requirements —
WriteDataByIdentifier No CAN specific requirements —
WriteMemoryByAddress No CAN specific requirements —
ReadDTCInformation No CAN specific requirements —
ClearDiagnosticInformation No CAN specific requirements —
Data Transmission Functional Unit
ReadDTCInformation No CAN specific requirements —
ClearDiagnosticInformation No CAN specific requirements —
Input/Output Control Functional Unit
InputOutputControlByIdentifier No CAN specific requirements —
Remote Activation Of Routine Functional Unit
RoutineControl No CAN specific requirements —
Upload/Download Functional Unit
RequestDownload No CAN specific requirements —
RequestUpload No CAN specific requirements —
TransferData No CAN specific requirements —
RequestTransferExit No CAN specific requirements —
RequestFileTransfer No CAN specific requirements —

6.3 ResponseOnEvent (0x86) service DoCAN implementation requirements

In addition to the generic implementation requirements stated in ISO 14229-1 the following additional CAN specific implementation requirements shall apply.
While the ResponseOnEvent service is active, the server shall be able to process concurrent diagnostic request and response messages accordingly. This should be accomplished with a different serviceToRespondTo CAN Identifiers. If the same diagnostic request/response CAN Identifiers are used for
diagnostic communication and the serviceToRespondTo-responses, the following restrictions shall apply:
a) The server may ignore an incoming diagnostic request issued by the client that initiated the event, after an event has occurred and the serviceToRespondTo-response is in progress, until the serviceToRespondTo-response is completed. If another client issued the request, the server may or may not ignore the request, depending on the server’s capabilities.
b) When the client receives any response after sending a diagnostic request, the response shall be classified according to the possible serviceToRespondTo-responses and the expected diagnostic
responses to the previously sent request.

If the response is a serviceToRespondTo-response (one of the possible responses set up with ResponseOnEvent-service), the client shall repeat the request after the serviceToRespondTo-response has been received completely.
If the response is ambiguous (i.e. the response could originate from the serviceToRespondTo initiated by an event or from the response to a diagnostic request), the client shall present the response both as a serviceToRespondTo-response and as the response to the diagnostic request. The client shall not repeat the request with the exception of NegativeResponseCode busyRepeatRequest (0x21) (see the negative response code definitions in ISO 14229-1.
c) When the specified event is detected, the server shall respond immediately with the appropriate serviceToRespondTo-response message. The immediate serviceToRespondTo-response message shall not disrupt any other diagnostic request or response transmission already in progress (i.e. the
serviceToRespondTo-response shall be delayed until the current message transmission has been completed, see Figure 3).

参考資料

@kazuo_reve 自動車の故障診断に関連するプログラマーになりたての方が参照するとよさそうな情報
https://qiita.com/kazuo_reve/items/f773b320dcbf2ab316da

@kazuo_reve AUTOSARのClassic PlatformとAdaptive PlatformにおけるDiagnosticsの違いを整理
https://qiita.com/kazuo_reve/items/05c179d705c69286b94a

私のAdvent Calendar 2022 ーーはじめたきっかけ、1月のふりかえり、今後の展望
https://qiita.com/torifukukaiou/items/891db4e40a7f6194af56

自己参照

今 Calendar2021を書いている理由
https://qiita.com/kaizen_nagoya/items/dca73e903785bea2a106

ISO Road vehicles Diagnostics 規格調査中　100規格、100記事をめざして。
https://qiita.com/kaizen_nagoya/items/51e29d318585a4219985

ISO Diagnostics 文献（Normative Reference and Bibliography）集め
https://qiita.com/kaizen_nagoya/items/535a0144a343df2c99df

ISO Diagnostics 用語定義(Terms and Definition)と短縮名(short name)集め
https://qiita.com/kaizen_nagoya/items/83cae62d1cb528c3c816

ISO/IEC OSIに学ぶ
https://qiita.com/kaizen_nagoya/items/89562c52f37d6bf0a80d

ISO 14229-1:2020 Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer
https://qiita.com/kaizen_nagoya/items/3231d9fea536d1b9b1f7

国際規格のNormative Reference
https://qiita.com/kaizen_nagoya/items/b94b6055997119ac2d9a

@kazuo_reveさんの「自動車の故障診断に関連するプログラマーになりたての方が参照するとよさそうな情報」の読み方
https://qiita.com/kaizen_nagoya/items/3231d9fea536d1b9b1f7

@kazuo_reve「AUTOSARのClassic PlatformとAdaptive PlatformにおけるDiagnosticsの違いを整理」で慌てて
https://qiita.com/kaizen_nagoya/items/d3ff6aba9b7402e8bde8

自己記事一覧

Qiitaで逆リンクを表示しなくなったような気がする。時々、スマフォで表示するとあらわっることがあり、完全に削除したのではなさそう。

４月以降、せっせとリンクリストを作り、統計を取って確率を説明しようとしている。
2025年２月末を目標にしている。

物理記事　上位100
https://qiita.com/kaizen_nagoya/items/66e90fe31fbe3facc6ff

量子(0) 計算機, 量子力学
https://qiita.com/kaizen_nagoya/items/1cd954cb0eed92879fd4

数学関連記事１００
https://qiita.com/kaizen_nagoya/items/d8dadb49a6397e854c6d

統計(0)一覧
https://qiita.com/kaizen_nagoya/items/80d3b221807e53e88aba

図(0) state, sequence and timing. UML and お絵描き
https://qiita.com/kaizen_nagoya/items/60440a882146aeee9e8f

品質一覧
https://qiita.com/kaizen_nagoya/items/2b99b8e9db6d94b2e971

言語・文学記事　１００
https://qiita.com/kaizen_nagoya/items/42d58d5ef7fb53c407d6

医工連携関連記事一覧
https://qiita.com/kaizen_nagoya/items/6ab51c12ba51bc260a82

自動車　記事　１００
https://qiita.com/kaizen_nagoya/items/f7f0b9ab36569ad409c5

通信記事１００
https://qiita.com/kaizen_nagoya/items/1d67de5e1cd207b05ef7

日本語（０）一欄
https://qiita.com/kaizen_nagoya/items/7498dcfa3a9ba7fd1e68

英語(0) 一覧
https://qiita.com/kaizen_nagoya/items/680e3f5cbf9430486c7d

転職(0)一覧
https://qiita.com/kaizen_nagoya/items/f77520d378d33451d6fe

仮説（0）一覧（目標100現在40）
https://qiita.com/kaizen_nagoya/items/f000506fe1837b3590df

音楽　一覧(0)
https://qiita.com/kaizen_nagoya/items/b6e5f42bbfe3bbe40f5d

「@kazuo_reve 新人の方によく展開している有益な情報」確認一覧
https://qiita.com/kaizen_nagoya/items/b9380888d1e5a042646b

Qiita(0)Qiita関連記事一覧（自分）
https://qiita.com/kaizen_nagoya/items/58db5fbf036b28e9dfa6

鉄道（０）鉄道のシステム考察はてっちゃんがてつだってくれる
https://qiita.com/kaizen_nagoya/items/26bda595f341a27901a0

安全（0）安全工学シンポジウムに向けて: 21
https://qiita.com/kaizen_nagoya/items/c5d78f3def8195cb2409

一覧の一覧( The directory of directories of mine.) Qiita(100)
https://qiita.com/kaizen_nagoya/items/7eb0e006543886138f39

Ethernet 記事一覧　Ethernet(0)
https://qiita.com/kaizen_nagoya/items/88d35e99f74aefc98794

Wireshark 一覧 wireshark(0)、Ethernet(48)
https://qiita.com/kaizen_nagoya/items/fbed841f61875c4731d0

線網（Wi-Fi）空中線(antenna)(0) 記事一覧(118/300目標)
https://qiita.com/kaizen_nagoya/items/5e5464ac2b24bd4cd001

OSEK OS設計の基礎　OSEK(100)
https://qiita.com/kaizen_nagoya/items/7528a22a14242d2d58a3

Error一覧 error(0)
https://qiita.com/kaizen_nagoya/items/48b6cbc8d68eae2c42b8

++ Support(0)　
https://qiita.com/kaizen_nagoya/items/8720d26f762369a80514

Coding(0) Rules, C, Secure, MISRA and so on
https://qiita.com/kaizen_nagoya/items/400725644a8a0e90fbb0

coding (101) 一覧を作成し始めた。omake:最近のQiitaで表示しない5つの事象
https://qiita.com/kaizen_nagoya/items/20667f09f19598aedb68

プログラマによる、プログラマのための、統計(0)と確率のプログラミングとその後
https://qiita.com/kaizen_nagoya/items/6e9897eb641268766909

なぜdockerで機械学習するか書籍・ソース一覧作成中 (目標100)
https://qiita.com/kaizen_nagoya/items/ddd12477544bf5ba85e2

言語処理100本ノックをdockerで。python覚えるのに最適。:10+12
https://qiita.com/kaizen_nagoya/items/7e7eb7c543e0c18438c4

プログラムちょい替え（0）一覧:4件
https://qiita.com/kaizen_nagoya/items/296d87ef4bfd516bc394

Python(0)記事をまとめたい。
https://qiita.com/kaizen_nagoya/items/088c57d70ab6904ebb53

官公庁・学校・公的団体（NPOを含む）システムの課題、官（０）
https://qiita.com/kaizen_nagoya/items/04ee6eaf7ec13d3af4c3

「はじめての」シリーズ　ベクタージャパン　
https://qiita.com/kaizen_nagoya/items/2e41634f6e21a3cf74eb

AUTOSAR(0)Qiita記事一覧, OSEK(75)
https://qiita.com/kaizen_nagoya/items/89c07961b59a8754c869

プログラマが知っていると良い「公序良俗」
https://qiita.com/kaizen_nagoya/items/9fe7c0dfac2fbd77a945

LaTeX(0) 一覧　
https://qiita.com/kaizen_nagoya/items/e3f7dafacab58c499792

自動制御、制御工学一覧（０）
https://qiita.com/kaizen_nagoya/items/7767a4e19a6ae1479e6b

Rust(0) 一覧　
https://qiita.com/kaizen_nagoya/items/5e8bb080ba6ca0281927

100以上いいねをいただいた記事16選
https://qiita.com/kaizen_nagoya/items/f8d958d9084ffbd15d2a

小川清最終講義、最終講義（再）計画, Ethernet(100) 英語(100) 安全(100)
https://qiita.com/kaizen_nagoya/items/e2df642e3951e35e6a53

＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
This article is an individual impression based on my individual experience. It has nothing to do with the organization or business to which I currently belong.

文書履歴(document history)

ver. 0.01 初稿 20220207

最後までおよみいただきありがとうございました。

いいね　💚、フォローをお願いします。

Thank you very much for reading to the last sentence.

Please press the like icon 💚　and follow me for your happy life.

You get articles that match your needs
You can efficiently read back useful information
You can use dark theme

What you can do with signing up