AUTOSARは自動車ソフトウェアの業界団体規格です。
業務で利用する場合には、会員になることを条件にしています。
2002年から20年経ち、当初の狙いの段階に近づいてきました。
MATLABでモデルさえ記述すれば、あとは自動生成だけでソフトが完成するところまで、あと一歩です。
Ethernet, UNIXが生まれて20年で大衆化したのと同じように考えると分かりやすいでしょう。
AUTOSARの上で動く、クラウド対応のミドルウェアが出て、開発も運用もクラウドになれば、一気にAUTOSARは大衆化するでしょう。
AUTOSAR Abstract Platformへの道 R22-11
AUTOSARは、ISO、IEC、ITUと情報交換契約を結んでいません。
AUTOSAR文書には、ISO、IEC,ITU記述を全文引用することはできません。
WTO/TBT協定に基づき、国際的な調達は国際規格との差異を記述することにより文化依存しない仕様を目指します。
ISO、IEC、ITU文書を合わせて読むと技術内容は理解できます。
CAN、OSEK/VDX OS、DIAGは、ISO定義を先に確認しましょう。
OSEK COM、OSEK NMなどはISOの規定から、基本的な部分でAUTOSARでは定義を変えています。
AUTOSARで変更している部分を仕様等で明記するか、ISOを改定するとよいでしょう。
AUTOSARの参考文献欄の改定が進んでいません。
Glossary用語定義の網羅性が低いです。
本文を読む前に確認するとよいかもしれません。
本文を読んでから確認してもよいかもしれません。
＜この記事は書きかけです。順次追記します。＞
This article is not completed. I will add some words in order.
2023年4月URL変更
この項は2023年4月21日、AUTOSARの文書のURLが変更になった。
/classic/22-11/
が
/R22-11/CP/
過去記事で、URLでエラーが出たら書き換えてみてください。
/adaptive/22-11/
は
/R22-11/AP/
/foundation/22-11/
は
/R22-11/FO/
です。
2022年11月URL変更
2022年11月にもAUTOSAR文書のURLが変更になっている。
/user_upload/standards/classic/22-11/
を
/standards/R22-11/CP/
などに書き換えてください。
/user_upload/standards/adaptive/22-11/
を
/standards/R22-11/AP/
/user_upload/standards/foundation/23-11/
を
/standards/R22-11/FO/
お手数をおかけします。
１年に２度URLを変更するなんて、新しい記事が書ける。とても嬉しい。
一覧
R22-11
https://www.autosar.org/fileadmin/standards/R22-11/FO/AUTOSAR_RS_Diagnostics.pdf
R21-11
https://www.autosar.org/fileadmin/standards/R21-11/FO/AUTOSAR_RS_Diagnostics.pdf
R20-11
https://www.autosar.org/fileadmin/standards/R20-11/FO/AUTOSAR_RS_Diagnostics.pdf
R19-11
https://www.autosar.org/fileadmin/standards/R19-11/FO/AUTOSAR_RS_Diagnostics.pdf
この記事の表題の最後に「20230421」を加えます。
お手数をおかけします。
１年に２度URLを変更するなんて、新しい記事が書ける。とても嬉しい。
<この項は書きかけです。順次追記します。>
Requirements on Diagnostics AUTOSAR 4 R22-11, FO
AUTOSARは、ISO、IEC、ITUと情報交換契約を結んでいません。
AUTOSAR文書には、ISO、IEC,ITU記述を全文引用することはできません。
WTO/TBT協定に基づき、国際的な調達は国際規格との差異を記述することにより文化依存しない仕様を目指します。
ISO、IEC、ITU文書を合わせて読むと技術内容は理解できます。
CAN、OSEK/VDX OS、DIAGは、ISO定義を先に確認しましょう。
OSEK COM、OSEK NMなどはISOの規定から基本的な部分で定義を変えています。
変更している部分を仕様等で明記するか、ISOを改定するとよいでしょう。
AUTOSARの参考文献欄の改定が進んでいません。
Glossary用語定義の網羅性が低いです。
本文を読む前に確認するとよいかもしれません。
本文を読んでから確認してもよいかもしれません。
AUTOSARが、2022年の版、R22-11公開しました。公開行事の模様は
AUTOSAR R22-11 Release Event 20221208
AUTOSAR R22-11 Foundation 一覧はこちら。
Foundation Release Overview, No.781, FO, AUTOSAR 22-11(2)
文書は検索してダウンロードできます。
R20-11, R21-11、R22-11しか検索
AUTOSAR R22-11 Qiita記事一覧 20230421
AUTOSAR R22-11 Qiita記事一覧 20230421(2)
https://qiita.com/kaizen_nagoya/items/b3b992ec1885ad29801a
Abstract Platform との関係
より抽象的な表現を明確にして、CP, AP, AUTOSAR以外での生成を可能にするとよい。
背景
現状のAUTOSARを捉えるには、まず３つの起源を知っているとよいでしょう。
1 排ガス規制をクリアした電子制御
honda 語り継ぎたいこと> Hondaのチャレンジングスピリット> CVCCエンジン発表 1972
https://www.honda.co.jp/50years-history/challenge/1972introducingthecvcc/
2 Controller Area Network(CAN)
物理的に調停して、時間の無駄と電力の無駄を省くことができる通信規約。
配線が軽く、引き回ししやすい。CAN,CAN FDは国際規格になっている。国際規格になる頃の公開文書。
Bosch specification
http://esd.cs.ucr.edu/webres/can20.pdf
Bosch CAN FD Specification Version 1.0
https://web.archive.org/web/20151211125301/http://www.bosch-semiconductors.de/media/ubk_semiconductors/pdf_1/canliteratur/can_fd_spec.pdf
3 ISO OSEK/VDX
OSの機能を利用する割り込みと、OSの機能を利用しない割り込みを分類し、電子制御の邪魔をせず、CAN通信を助けるOS。国際規格になる頃の公開文書。
OSEK/VDX Operating System Specification 2.2.3 https://www.irisa.fr/alf/downloads/puaut/TPNXT/images/os223.pdf
Foundation/Abstrace Platformの読み方
Adaptive PlatformとClassic Platform の共通部分をFoundation/Abstract Platformとして定義し直そうとしています。
その際に、重要なAUTOSAR以外での３つの標準化が大切になります。
これらの３つの標準化を、うまくFoundation/Abstract Platformとして取り込めば、AUTOSARのDiagnosticsは、国際規格にも、デファクトスタンダードにも、オープンソースにも調和した、真の意味での公開仕様になるかもしれません。
POSIX -> COVESA, Automotive Grade Linux
今現在は、Adaptive Platformは、Classic Platformの上位互換のようには見えません。
実際には、Adaptive Platformのマルチコアの一つのコアでClassic Platformを動かす努力をしている人たちはいます。
Adaptive PlatformはPOSIX OSを利用しています。POSIX OSが動くC言語をHosted Environmentと言います。Classic Platformで動くOSEK OSのC言語をFreestanding Environmentと言います。
Hosted Environmentは、Freestanding Environmentの上位互換です。
そのため、OS, Platform自体も上位互換に設計することが可能です。設計方法はいろいろあり、かつ、CPUの機能によってその設計方法は一つとは限りません。
それらの土台となるOSに、Linuxがあります。車載Linuxは、Linux Foundationでも検討しています。
COVESA
Automotive Grade Linux
Ethernet -> Open Alliance
CANがEthernetよりすぐれていた点は、物理的な調停と線のひきまわしでした。
各NodeがEther Switchであるか、Ether Switchの分岐であれば、CANに近いほぼ物理的な調停を可能にできなくもないかもしれません。
線のひきまわしは、車載Ethernetでは、CANに近くなりました。
Open Alliance
DIAGNOSTICS -> ISO/TC 22/SC 31
Technical Committee : ISO/TC 22/SC 31 Data communication
ISO 14229-1:2020
Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer
Requirements on Diagnostics
| Document Title | Requirements on Diagnostics |
|---|---|
| Document Owner | AUTOSAR |
| Document Responsibility | AUTOSAR |
| Document Identification No | 4 |
| Document Status | published |
| Part of AUTOSAR Standard | Foundation |
| Part of Standard Release | R21-11 |
Document Change R21 - 11
• New requirements for CP and AP
• Correction of requirement
assignment to CP and AP
• Additional requirement for SW
Cluster support in AUTOSAR Classic
目的と成果(Purpose and Outcome)
| item | description |
|---|---|
| who | Diagnostics designer |
| what | Concept 636 "Security Extensions" |
| importance | high |
| others | |
| comment | Please read v.2 or v.3, there are initiaters. |
文書変更(Document Change)
• New requirements for CP and AP
• Correction of requirement
assignment to CP and AP
• Additional requirements for SOVD
support
用語(terms)
| Term | Description |
|---|---|
| CAN | Controller Area Network (communication bus) |
| Dem | Diagnostic Event Manager |
| DID | Diagnostic Identifier |
| DM | Diagnostic Management |
| DoIP | Diagnostic over IP - transport protocol for diagnostic services standardized as ISO 13400 |
| DTC | Diagnostic Trouble Code |
| ECU | Electronic Control Unit |
| IDL | Interface Description Language |
| OBD | On-board Diagnostic (standardized as ISO 15031) |
| RTE | Runtime Environment |
| SA | Source Address (diagnostics address of the tester) |
| SID | Service Identifier (hexa number to uniquely identify UDS services) 0x22 for Read Data by Identifier service, 0x2E for Write to Non-Volatile memory service |
| SWC | Software Component (could refer either to Classic Platform SWC or to Adaptive Platform SW-C) |
| TA | Target Address (diagnostic address of the ECU) |
| UDS | Unified Diagnostic Specification standardized as ISO 14229 |
英日
日本語は仮訳
| no. | count | word | 日本語 |
|---|---|---|---|
| 1 | 753 | the | その |
| 2 | 491 | rs_diag_ | rs_diag_ |
| 3 | 475 | of | の |
| 4 | 418 | to | に |
| 5 | 329 | diagnostic | 診断 |
| 6 | 324 | in | の中に |
| 7 | 280 | and | と |
| 8 | 262 | autosar | AUTomotive Open System Architecture(短縮名) |
| 9 | 254 | shall | しなければならない |
| 10 | 223 | for | にとって |
| 11 | 218 | a | 一つの |
| 12 | 211 | be | です |
| 13 | 192 | rs_main_ | rs_main_ |
| 14 | 172 | service | 奉仕 |
| 15 | 171 | support | 対応 |
| 16 | 165 | case | 場合 |
| 17 | 165 | use | 使う |
| 18 | 155 | description | 説明 |
| 19 | 153 | c | c |
| 20 | 153 | d | d |
| 21 | 152 | is | です |
| 22 | 151 | event | 行事 |
| 23 | 145 | cp | classic platform(短縮名） |
| 24 | 145 | dependencies | 依存関係 |
| 25 | 144 | applies | 適用する |
| 26 | 143 | rationale | 根拠 |
| 27 | 139 | on | の上 |
| 28 | 127 | uds | Unified Diagnostic Specification（短縮名） |
| 29 | 124 | iso | International Organization for Standardization(短縮名） |
| 30 | 122 | material | 材料 |
| 31 | 121 | supporting | 対応 |
| 32 | 119 | data | 与件 |
| 33 | 119 | diagnostics | 診断 |
| 34 | 116 | ap | adaptive platform(短縮名) |
| 35 | 116 | requirements | 要件 |
| 36 | 97 | by | に |
| 37 | 95 | x | x |
| 38 | 94 | document | 文書 |
| 39 | 89 | or | または |
| 40 | 85 | services | 奉仕 |
| 41 | 84 | memory | 記憶装置 |
| 42 | 84 | provide | 提供 |
| 43 | 80 | fault | 障害 |
| 44 | 79 | id | identifier, 識別子(短縮名） |
| 45 | 77 | r | r |
| 46 | 73 | an | 一つの |
| 47 | 73 | autosar_rs_diagnostics | autosar_rs_diagnostics |
| 48 | 73 | fo | foundation(短縮名） |
| 49 | 69 | status | 状態 |
| 50 | 69 | with | と |
| 51 | 62 | access | 接続 |
| 52 | 61 | information | 情報 |
| 53 | 60 | not | いいえ |
| 54 | 60 | this | これ |
| 55 | 58 | specific | 明確 |
| 56 | 56 | are | です |
| 57 | 55 | application | 応用 |
| 58 | 55 | ecu | Electronic Control Unit（短縮名） |
| 59 | 52 | can | できる |
| 60 | 52 | that | それ |
| 61 | 51 | applications | 応用 |
| 62 | 51 | events | 行事 |
| 63 | 51 | management | 管理 |
| 64 | 49 | as | なので |
| 65 | 49 | related | 関連している |
| 66 | 48 | according | によると |
| 67 | 47 | defined | 定義済み |
| 68 | 47 | dtc | Diagnostic Trouble Code（短縮名） |
| 69 | 47 | obd | On-board Diagnostic （短縮名） |
| 70 | 47 | session | 節 |
| 71 | 46 | which | どの |
| 72 | 45 | dtcs | Diagnostic Trouble Codes(短縮名） |
| 73 | 39 | handling | 取り扱い |
| 74 | 39 | it | それ |
| 75 | 38 | security | 安心 |
| 76 | 37 | about | 約 |
| 77 | 37 | only | それだけ |
| 78 | 37 | tester | 試験器 |
| 79 | 36 | communication | 通信 |
| 80 | 35 | dm | Diagnostic Management（短縮名） |
| 81 | 34 | all | すべて |
| 82 | 34 | certificate | 証明する |
| 83 | 34 | configurable | 構成可能 |
| 84 | 34 | different | 違う |
| 85 | 34 | from | から |
| 86 | 33 | configuration | 構成 |
| 87 | 32 | j | j |
| 88 | 31 | identifier | 識別子 |
| 89 | 30 | e | e |
| 90 | 30 | if | もし |
| 91 | 30 | storage | 記録 |
| 92 | 29 | processing | 処理 |
| 93 | 29 | software | ソフトウェア |
| 94 | 29 | time | 時間 |
| 95 | 29 | vehicle | 車両 |
| 96 | 28 | each | 各 |
| 97 | 28 | external | 外部の |
| 98 | 28 | parallel | 平行 |
| 99 | 28 | release | 公開 |
| 100 | 27 | client | 顧客 |
Common Diagnostic requirements for Classic and Adaptive Platform
[RS_Diag_04115] The optional parameter DTCSettingControlOptionRecord as
part of UDS service ControlDTCSetting shall be limited to GroupOfDTC
[RS_Diag_04150] Support the primary fault memory defined by ISO 14229-1
[RS_Diag_04214] Support the user defined fault memories defined by ISO 14229-1
[RS_Diag_04033] Support the upload/download services for reading/writing data in an ECU in an extended and manufacturer specific diagnostic session
[RS_Diag_04068] The diagnostic in AUTOSAR shall support event specific de- bounce counters to improve signal quality internally (According to ISO 14229-1 Appendix D)
[RS_Diag_04180] Process all UDS Services related to diagnostic fault memoryofISO14229-1internally .
[RS_Diag_04196] UDS Service handling for all diagnostic services de-
finedinISO14229-2.
[RS_Diag_04224] Support the UDS service 0x31 (RoutineControl) ac-
cordingtoISO14229-1
[RS_Diag_04218] Support of UDS service 0x2F InputOutputControlByIDentifier
[RS_Diag_04224] Support the UDS service 0x31 (RoutineControl) according to
ISO 14229-1
[RS_Diag_04020] Suppress responses to diagnostic tool requests
[RS_Diag_04119] Handle the execution of diagnostic services according to the assigned diagnostic session
[RS_Diag_04016] Support ”Busy handling” by sending a negative response 0x78
[RS_Diag_04244] Support sub-function 0x04 of UDS service 0x19.
[RS_Diag_04245] Support sub-function 0x06 of UDS service 0x19.
[RS_Diag_04160] ResponseOnEvent according to ISO 14229-1
[RS_Diag_04246] Support of UDS service DynamicallyDefineDataIdentifier
(0x2C) with subfunction 0x01 (defineByIdentifier)
[RS_Diag_04215] Support of UDS service ReadDataByPeriodicIdentifier (0x2A)
[RS_Diag_04249] Support of session layer service
The diagnostic in AUTOSAR shall support the session layer services defined by ISO-14229-2.
4.2 Diagnostic requirements for the Classic Platform
この文書に入れることが適切かどうか。
4.3 Diagnostic requirements for the Adaptive Platformx
この文書に入れることが適切かどうか。
Reference
6.1
[1] Main Requirements AUTOSAR_RS_Main
6.1 Deliverables of AUTOSAR
[1] General Requirements of Basic Software Modules:
AUTOSAR_SRS_BSWGeneral.pdf
[2] Specification of the Virtual Functional Bus : AUTOSAR_EXP_VFB.pdf
[3] Software Standardization Template : AUTOSAR_TPS_StandardizationTemplate.pdf
6.2 Related standards and norms
6.2.1 ITEA-EAST
[1]. D1.5-General Architecture; ITEAEAST-EEA, Version 1.0; chapter 3, page 72 et seq.
[2]. D2.1-Embedded Basic Software Structure Requirements; ITEAEAST-EEA, Ver- sion 1.0 or higher
[3]. D2.2-Description of existing solutions; ITEA/EAST-EEA, Version 1.0 or higher.
6.2.2 ISO
[1]. ISO 14229-1 Unified diagnostic services (UDS)
Part 1: Specification and Requirements (v.2013)
ISO 14229-1:2020
Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer
ISO 14229-1:2020/Amd 1:2022
Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer — Amendment 1
2 Normative references
ISO 14229-2, Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
ISO 7816-8, Identification cards — Integrated circuit cards — Part 8: Commands and mechanisms for security operations
ISO/IEC 9594-8, Information technology — Open Systems Interconnection — The Directory — Part 8: Public-key and attribute certificate frameworks
IEEE 754-2008, IEEE Standard for Floating-Point Arithmetic
IEEE 1609.2, Standard for Wireless Access in Vehicular Environments — Security Services for Applications and Management Messages
X.509, Information technology — Open Systems Interconnection — The Directory: Public-key and attribute certificate frameworks
RFC 5280, Internet Engineering Task Force — Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
RFC 5755, Internet Engineering Task Force — An Internet Attribute Certificate Profile for Authorization
Bibliography
[1] ISO 4092:1988/Cor.1:1991, Road vehicles — Diagnostic systems for motor vehicles — Vocabulary — Technical Corrigendum 1
[2] ISO/IEC 7498-1, Information technology — Open Systems Interconnection — Basic Reference Model: The Basic Model
[3] ISO/IEC 7618-8:2006, Identification cards — Integrated circuit cards
[4] ISO/TR 8509:1987, Information processing systems — Open Systems Interconnection — Service conventions
[5] ISO/IEC 9798-2, IT Security techniques — Entity authentication — Part 2: Mechanisms using authenticated encryption
[6] ISO/IEC 9798-3, IT Security techniques — Entity authentication — Part 3: Mechanisms using digital signature techniques
[7] ISO/IEC 9798-4, Information technology — Security techniques — Entity authentication — Part 4: Mechanisms using a cryptographic check function
[8] ISO/IEC 10731, Information technology — Open Systems Interconnection — Basic Reference Model — Conventions for the definition of OSI services
[9] ISO 11992-4, Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 4: Diagnostics
[10] ISO 14229-3, Road vehicles — Unified diagnostic services (UDS) — Part 3: Unified diagnostic services on CAN implementation (UDSonCAN)
[11] ISO 14229-4, Road vehicles — Unified diagnostic services (UDS) — Part 4: Unified diagnostic services on FlexRay implementation (UDSonFR)
[12] ISO 14229-5, Road vehicles — Unified diagnostic services (UDS) — Part 5: Unified diagnostic services on Internet Protocol implementation (UDSonIP)
[13] ISO 14229-6, Road vehicles — Unified diagnostic services (UDS) — Part 6: Unified diagnostic services on K-Line implementation (UDSonK-Line)
[14] ISO 14229-7, Road vehicles — Unified diagnostic services (UDS) — Part 7: UDS on local interconnect network (UDSonLIN)
[15] ISO 14229-8, Road vehicles — Unified diagnostic services (UDS) — Part 8: Unified diagnostic services on clock extension peripheral interface implementation (UDSonCXPI)
[16] ISO 15031-2, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 2: Guidance on terms, definitions, abbreviations and acronyms
[17] ISO 15031-6, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 6: Diagnostic trouble code definitions
[18] ISO 15765-4, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 4: Requirements for emissions-related systems
[19] ISO 22901-1, Road vehicles — Open diagnostic data exchange (ODX) — Part 1: Data model specification
[20] ISO 26021-2, Road vehicles — End-of-life activation of on-board pyrotechnic devices — Part 2: Communication requirements
[21] ISO 27145-2, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (VOBD) communication requirements — Part 2: Common data dictionary
[22] ISO 27145-3, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (VOBD) communication requirements — Part 3: Common message dictionary
[23] SAE J1939:2011, Serial Control and Communications Heavy Duty Vehicle Network — Top Level Document
[24] SAE J1939-73:2010, Application Layer — Diagnostics
[25] ISO 10681-2, Road vehicles — Communication on FlexRay — Part 2: Communication layer services
[26] ISO 11898-1, Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical signalling
[27] ISO 11898-2, Road vehicles — Controller area network (CAN) — Part 2: High-speed medium access unit
[28] ISO 13400-2, Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 2: Transport protocol and network layer services
[29] ISO 13400-3, Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 3: Wired vehicle interface based on IEEE 802.3
[30] ISO 14230-1, Road vehicles — Diagnostic communication over K-Line (DoK-Line) — Part 1: Physical layer
[31] ISO 14230-2, Road vehicles — Diagnostic communication over K-Line (DoK-Line) — Part 2: Data link layer
[32] ISO 15031-4, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 4: External test equipment
[33] ISO 15031-5, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 5: Emissions-related diagnostic services
[34] ISO 15765-2, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services
[35] ISO 16844-7, Road vehicles — Tachograph systems — Part 7: Parameters
[36] ISO 17458-2, Road vehicles — FlexRay communications system — Part 2: Data link layer specification
[37] ISO 17458-4, Road vehicles — FlexRay communications system — Part 4: Electrical physical layer specification
[38] ISO 17987-2, Road vehicles — Local Interconnect Network (LIN) — Part 2: Transport protocol and network layer services
[39] ISO 17987-3, Road vehicles — Local Interconnect Network (LIN) — Part 3: Protocol specification
[40] ISO 17987-4, Road vehicles — Local Interconnect Network (LIN) — Part 4: Electrical physical layer (EPL) specification 12 V/24 V
[41] ISO 20794-3, Road vehicles — Clock extension peripheral interface (CXPI) — Part 3: Transport and network layer
[42] ISO 20794-4, Road vehicles — Clock extension peripheral interface (CXPI) — Part 4: Data link layer and physical layer
[43] ISO 26021-2, Road vehicles — End-of-life activation of on-board pyrotechnic devices — Part 2: Communication requirements
[44] ISO 27145-4, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 4: Connection between vehicle and test equipment
[45] IEEE 802.3, IEEE Standard for Ethernet
[46] SAE J1978, OBD II Scan Tool — Equivalent to ISO/DIS 15031-4:December 14, 2001
[47] SAE J1979, E/E Diagnostic Test Modes
[48] SAE J1979-2, Compliant OBDII Scan Tool
[49] SAE J1979-DA, Digital Annex of E/E Diagnostic Test Modes
[50] SAE J2012, Diagnostic Trouble Code Definitions
[51] SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming (STABILIZED Jul 2019)
[52] ISO 15765-5, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 5: Specification for an in-vehicle network connected to the diagnostic link connector
1 Under preparation. Stage at the time of publication: ISO/FDIS 14229-8:2020.
2 Under preparation. Stage at the time of publication: ISO/FDIS 20794-3:2020.
3 Under preparation. Stage at the time of publication: ISO/FDIS 20794-4:2020.
[2]. ISO 15031-5 Communication between vehicle and external equipment for emis- sions related diagnostics Part 5:
Emissions related diagnostic services (2005-01- 13)
ISO 15031-5:2015
Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 5: Emissions-related diagnostic services
2 Normative references
ISO 9141-2:1994, Road vehicles — Diagnostic systems — Part 2: CARB requirements for interchange of digital information
ISO 14229-2, Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
ISO 14230-2, Road vehicles — Diagnostic communication over K-Line (DoK-Line) — Part 2: Data link layer
ISO 14230-4:2000, Road vehicles — Diagnostic systems — Keyword Protocol 2000 — Part 4: Requirements for emission-related systems
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
ISO 15031-2, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 2: Guidance on terms, definitions, abbreviations and acronyms
SAE J1930-DA, Digital Annex of Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms
SAE J1979-DA, Digital Annex of E/E Diagnostic Test Modes
SAE J2012-DA, Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions
Bibliography
[1] ISO 11898-1, Road vehicles Controller area network (CAN) — Part 1: Data link layer and physical signalling
[2] ISO 11898-2, Road vehicles — Controller area network (CAN) — Part 2: High-speed medium access unit
[3] ISO 14230-1, Road vehicles — Diagnostic communication over K-Line (DoK-Line) — Part 1: Physical layer
[4] ISO 15031-3, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 3: Diagnostic connector and related electrical circuits, specification and use
[5] ISO 15031-1, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 1: General information and use case definition
[6] ISO 15031-4, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 4: External test equipment
[7] ISO 15031-6, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 6: Diagnostic trouble code definitions
[8] ISO/IEC 7498-1, Information technology — Open Systems Interconnection — Basic Reference Model: The Basic Model — Part 1
[9] ISO/IEC 10731, Information technology — Open Systems Interconnection — Basic Reference Model — Conventions for the definition of OSI services
[10] SAE J1850, Class B Data Communications Network Interface
[11] SAE J1978, OBD II Scan Tool
[3]. ISO 15765-3 Diagnostics on controller area network (CAN) Part 3:
Implementa- tion of unified diagnostic services (UDS on CAN) (2004-10-06)
ISO 15031-3:2016
Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 3: Diagnostic connector and related electrical circuits: Specification and use
2 Normative references
SAE J1962:2015, Diagnostic connector
Bibliography
[1] ISO 6722-3:19931, Road vehicles — Unscreened low-tension cables — Part 3: Conductor sizes and dimensions for thick-wall insulated cables
[2] ISO 6722-4:19932, Road vehicles — Unscreened low-tension cables — Part 4: Conductor sizes and dimensions for thin-wall insulated cables
[3] ISO 9141-2, Road vehicles — Diagnostic systems — Part 2: CARB requirements for interchange of digital information
[4] ISO 13400-3, Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 3: IEEE 802.3 based wired vehicle interface
[5] ISO 13400-43, Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 4: Ethernet-based high-speed data link connector
[6] ISO 14230-4, Road vehicles — Diagnostic systems — Keyword Protocol 2000 — Part 4: Requirements for emission-related systems
[7] ISO 15031-1, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 1: General information and use case definition
[8] ISO 15031-4, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 4: External test equipment
[9] ISO 15765-4, Road vehicles — Diagnostics on Controller Area Network (CAN) — Part 4: Requirements for emissions-related systems
[10] ISO 26021-4, Road vehicles — End-of-life activation of on-board pyrotechnic devices — Part 4: Additional communication line with bidirectional communication
[11] ISO 26021-5, Road vehicles — End-of-life activation of on-board pyrotechnic devices — Part 5: Additional communication line with pulse width modulated signal
[12] SAE J1850, Class B Data Communications Network Interface
[13] IEEE 802.3, IEEE Standard for Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Specific requirements — Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications
1 Withdrawn.
2 Withdrawn.
3 To be published.
[4]. ISO 15765-4 Diagnostics on controller area network (CAN) Part 4:
Requirements for emissions-related systems (2005-01-04)
ISO 15765-4:2021
Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 4: Requirements for emissions-related systems
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 7498-1, Information technology — Open Systems Interconnection — Basic Reference Model: The Basic Model
ISO 11898-1, Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical signalling
ISO 11898-2, Road vehicles — Controller area network (CAN) — Part 2: High-speed medium access unit
ISO 14229-2, Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
ISO 15031-3, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 3: Diagnostic connector and related electrical circuits: Specification and use
ISO 15765-2, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services
Bibliography
[1] ISO/IEC 10731, Information technology — Open Systems Interconnection — Basic Reference Model — Conventions for the definition of OSI services
[2] ISO 15031-5, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 5: Emissions-related diagnostic services
[3] ISO 27145-3, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 3: Common message dictionary
[4] SAE J1979, E/E Diagnostic Test Modes — OBDonEDS
[5] SAE J1979-2, E/E Diagnostic Test Modes — OBDonUDS
[6] SAE J1979-DA, Digital Annex of E/E Diagnostic Test Modes
[7] SAE J2178-1, Class B data communication network messages detailed header formats and physical address assignments
参考資料
AUTOSARのClassic PlatformとAdaptive PlatformにおけるDiagnosticsの違いを整理 @kazuo_reve
https://qiita.com/kazuo_reve/items/05c179d705c69286b94a
自動車の故障診断に関連するプログラマーになりたての方が参照するとよさそうな情報 @kazuo_reve
https://qiita.com/kazuo_reve/items/f773b320dcbf2ab316da
自己参照
@kazuo_reveさんの「自動車の故障診断に関連するプログラマーになりたての方が参照するとよさそうな情報」の読み方
AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成
https://qiita.com/kaizen_nagoya/items/9b3a1b9b8d1e8d7e288e
資料一覧
F: Foundation
C: Classic Platform(CAN/OSEK)
A: Adaptive Platform(POSIX/Ethernet/TCP/IP)
<この項は書きかけです。順次追記します。>
参考資料
@kazuo_reve 新人の方によく展開している有益な情報
https://qiita.com/kaizen_nagoya/items/b9380888d1e5a042646b
@kazuo_reve 私が効果を確認した「小川メソッド」
https://qiita.com/kazuo_reve/items/a3ea1d9171deeccc04da
自己参照
「ぼくの好きな先生」「人がやらないことをやれ」プログラマになるまで。仮説（37）
https://qiita.com/kaizen_nagoya/items/53e4bded9fe5f724b3c4
小川メソッド 覚え（書きかけ）
https://qiita.com/kaizen_nagoya/items/3593d72eca551742df68
DoCAP（ドゥーキャップ）って何ですか？
https://qiita.com/kaizen_nagoya/items/47e0e6509ab792c43327
「@kazuo_reve 新人の方によく展開している有益な情報」確認一覧
https://qiita.com/kaizen_nagoya/items/b9380888d1e5a042646b
全世界の不登校の子供たち「博士論文」を書こう。世界子供博士論文遠隔実践中心
https://qiita.com/kaizen_nagoya/items/912d69032c012bcc84f2
Views１万越え、もうすぐ１万記事一覧
https://qiita.com/kaizen_nagoya/items/d2b805717a92459ce853
Researchmap
＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞
文書履歴(document history)
ver. 0.01 初稿 20230501
最後までおよみいただきありがとうございました。
いいね 💚、フォローをお願いします。
Thank you very much for reading to the last sentence.
Please press the like icon 💚 and follow me for your happy life.