AUTOSARは自動車ソフトウェアの業界団体規格です。
業務で利用する場合には、会員になることを条件にしています。
2003年から20年経ち、当初の狙いの段階に近づいてきました。
MATLABでモデルさえ記述すれば、あとは自動生成だけでソフトが完成するところまで、あと一歩です。
Ethernet, UNIXが生まれて20年で大衆化したのと同じように考えると分かりやすいでしょう。
AUTOSARの上で動く、クラウド対応のミドルウェアが出て、開発も運用もクラウドになれば、一気にAUTOSARは大衆化するでしょう。
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.
一覧
R23-11
https://www.autosar.org/fileadmin/standards/23-11/FO/AUTOSAR_FO_RS_Diagnostics.pdf
R22-11のURLから、Rを削り、ファイル名に _FO を付け加えたのがR23-11のURL.
過去のURLは触っていないのはほっとした。過去に２度も全面的にURlを変更し、Web記事に何千というリンク切れを作ったAUTOSARの姿勢を疑問視していた。組織が相当混乱しているとみられても仕方がないだろう。
と書いたら、２０２３１２１６現在変更になっていた。やはりRを付け加えていた。１週間程度の修正のようだ。
2023年文書公開後、Rの文字が抜けていたのを訂正したため、一部の記事でURLがリンク切れになっています。ごめんなさい。文書名にFO,CP,APの区分をつけるようになった点は更新点です。過去の文書を見る場合は、URLの年を変更するだけでなく文書によってはFO,CP, APを削除してみてください。
R22-11
https://www.autosar.org/fileadmin/standards/R22-11/FO/AUTOSAR_RS_Diagnostics.pdf
https://qiita.com/kaizen_nagoya/items/592796bbf35d17bd8c8e
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
各分類ごとのRelease Overviewはこちら。
Classic Platform Release Overview, AUTOSAR No.0 ,R23-11, CP
https://qiita.com/kaizen_nagoya/items/8468435185e109189ead
Foundation Release Overview, AUTOSAR 781, R23-11, FO
https://qiita.com/kaizen_nagoya/items/f249bdb8c313d8bff883
Adaptive Platform Release Overview, AUTOSAR 782, R23-11, AP
https://qiita.com/kaizen_nagoya/items/13a104606a34fe24fcf7
DIAGNOSTICS -> ISO/TC 22/SC 31
Technical Committee : ISO/TC 22/SC 31 Data communication
https://www.iso.org/committee/5383568.html
ISO 14229-1:2020
Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer
https://www.iso.org/standard/72439.html
Requirements on Diagnostics
https://www.autosar.org/fileadmin/user_upload/standards/foundation/22-11/AUTOSAR_RS_Diagnostics.pdf
| 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 |
目的と成果(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
• Added further requirements for SOVD support (e.g. for SW Update and Logging)
用語(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 | 顧客 |
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
https://www.iso.org/standard/72439.html
ISO 14229-1:2020/Amd 1:2022
Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer — Amendment 1
https://www.iso.org/standard/81380.html
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さんの「自動車の故障診断に関連するプログラマーになりたての方が参照するとよさそうな情報」の読み方
https://qiita.com/kaizen_nagoya/items/0c6b8373f93ce52def33
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
AUTOSAR Abstract Platformへの道 R22-11
https://qiita.com/kaizen_nagoya/items/8ac2826635a8c536c7ec
Researchmap
補足資料（Additions）
2023 Countdown Calendar 主催・参加一覧
https://qiita.com/kaizen_nagoya/items/c4c2f08ac97f38d08543
CountDownCalendar月間 いいねをいただいた記事群 views 順
https://qiita.com/kaizen_nagoya/items/583c5cbc225dac23398a
<この項は書きかけです。順次追記します。>
This article is not completed. I will add some words and/or centences in order.
自己記事一覧
Qiitaで逆リンクを表示しなくなったような気がする。時々、スマフォで表示するとあらわっることがあり、完全に削除したのではなさそう。
４月以降、せっせとリンクリストを作り、統計を取って確率を説明しようとしている。
2025年２月末を目標にしている。
一覧の一覧( The directory of directories of mine.) Qiita(100)
https://qiita.com/kaizen_nagoya/items/7eb0e006543886138f39
仮説（0）一覧（目標100現在40）
https://qiita.com/kaizen_nagoya/items/f000506fe1837b3590df
Qiita(0)Qiita関連記事一覧（自分）
https://qiita.com/kaizen_nagoya/items/58db5fbf036b28e9dfa6
Error一覧 error(0)
https://qiita.com/kaizen_nagoya/items/48b6cbc8d68eae2c42b8
C++ 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
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
なぜdockerで機械学習するか 書籍・ソース一覧作成中 (目標100)
https://qiita.com/kaizen_nagoya/items/ddd12477544bf5ba85e2
プログラムちょい替え（0）一覧:4件
https://qiita.com/kaizen_nagoya/items/296d87ef4bfd516bc394
言語処理100本ノックをdockerで。python覚えるのに最適。:10+12
https://qiita.com/kaizen_nagoya/items/7e7eb7c543e0c18438c4
Python(0)記事をまとめたい。
https://qiita.com/kaizen_nagoya/items/088c57d70ab6904ebb53
安全（0）安全工学シンポジウムに向けて: 21
https://qiita.com/kaizen_nagoya/items/c5d78f3def8195cb2409
プログラマによる、プログラマのための、統計(0)と確率のプログラミングとその後
https://qiita.com/kaizen_nagoya/items/6e9897eb641268766909
転職(0)一覧
https://qiita.com/kaizen_nagoya/items/f77520d378d33451d6fe
技術士(0)一覧
https://qiita.com/kaizen_nagoya/items/ce4ccf4eb9c5600b89ea
Reserchmap(0) 一覧
https://qiita.com/kaizen_nagoya/items/506c79e562f406c4257e
物理記事 上位100
https://qiita.com/kaizen_nagoya/items/66e90fe31fbe3facc6ff
量子(0) 計算機, 量子力学
https://qiita.com/kaizen_nagoya/items/1cd954cb0eed92879fd4
数学関連記事１００
https://qiita.com/kaizen_nagoya/items/d8dadb49a6397e854c6d
coq(0) 一覧
https://qiita.com/kaizen_nagoya/items/d22f9995cf2173bc3b13
統計(0)一覧
https://qiita.com/kaizen_nagoya/items/80d3b221807e53e88aba
図(0) state, sequence and timing. UML and お絵描き
https://qiita.com/kaizen_nagoya/items/60440a882146aeee9e8f
色(0) 記事100書く切り口
https://qiita.com/kaizen_nagoya/items/22331c0335ed34326b9b
品質一覧
https://qiita.com/kaizen_nagoya/items/2b99b8e9db6d94b2e971
言語・文学記事 １００
https://qiita.com/kaizen_nagoya/items/42d58d5ef7fb53c407d6
医工連携関連記事一覧
https://qiita.com/kaizen_nagoya/items/6ab51c12ba51bc260a82
水の資料集(0) 方針と成果
https://qiita.com/kaizen_nagoya/items/f5dbb30087ea732b52aa
自動車 記事 １００
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/b6e5f42bbfe3bbe40f5d
「@kazuo_reve 新人の方によく展開している有益な情報」確認一覧
https://qiita.com/kaizen_nagoya/items/b9380888d1e5a042646b
鉄道（０）鉄道のシステム考察はてっちゃんがてつだってくれる
https://qiita.com/kaizen_nagoya/items/faa4ea03d91d901a618a
OSEK OS設計の基礎 OSEK(100)
https://qiita.com/kaizen_nagoya/items/7528a22a14242d2d58a3
coding (101) 一覧を作成し始めた。omake:最近のQiitaで表示しない5つの事象
https://qiita.com/kaizen_nagoya/items/20667f09f19598aedb68
官公庁・学校・公的団体（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
関連資料
' @kazuo_reve 私が効果を確認した「小川メソッド」
https://qiita.com/kazuo_reve/items/a3ea1d9171deeccc04da
' @kazuo_reve 新人の方によく展開している有益な情報
https://qiita.com/kazuo_reve/items/d1a3f0ee48e24bba38f1
' @kazuo_reve Vモデルについて勘違いしていたと思ったこと
https://qiita.com/kazuo_reve/items/46fddb094563bd9b2e1e
Engineering Festa 2024前に必読記事一覧
programの本質は計画だ。programは設計だ。
https://qiita.com/kaizen_nagoya/items/c8545a769c246a458c27
登壇直後版 色使い(JIS安全色) Qiita Engineer Festa 2023〜私しか得しないニッチな技術でLT〜 スライド編 0.15
https://qiita.com/kaizen_nagoya/items/f0d3070d839f4f735b2b
プログラマが知っていると良い「公序良俗」
https://qiita.com/kaizen_nagoya/items/9fe7c0dfac2fbd77a945
逆も真：社会人が最初に確かめるとよいこと。OSEK(69)、Ethernet(59)
https://qiita.com/kaizen_nagoya/items/39afe4a728a31b903ddc
統計の嘘。仮説（127）
https://qiita.com/kaizen_nagoya/items/63b48ecf258a3471c51b
自分の言葉だけで論理展開できるのが天才なら、文章の引用だけで論理展開できるのが秀才だ。仮説（136）
https://qiita.com/kaizen_nagoya/items/97cf07b9e24f860624dd
参考文献駆動執筆(references driven writing)・デンソークリエイト編
https://qiita.com/kaizen_nagoya/items/b27b3f58b8bf265a5cd1
「何を」よりも「誰を」。１０年後のために今見習いたい人たち
https://qiita.com/kaizen_nagoya/items/8045978b16eb49d572b2
Qiitaの記事に３段階または５段階で到達するための方法
https://qiita.com/kaizen_nagoya/items/6e9298296852325adc5e
出力(output)と呼ばないで。これは状態(state)です。
https://qiita.com/kaizen_nagoya/items/80b8b5913b2748867840
coding (101) 一覧を作成し始めた。omake:最近のQiitaで表示しない5つの事象
https://qiita.com/kaizen_nagoya/items/20667f09f19598aedb68
あなたは「勘違いまとめ」から、勘違いだと言っていることが勘違いだといくつ見つけられますか。人間の間違い(human error(125))の種類と対策
https://qiita.com/kaizen_nagoya/items/ae391b77fffb098b8fb4
プログラマの「プログラムが書ける」思い込みは強みだ。３つの理由。仮説（168）統計と確率(17) , OSEK(79)
https://qiita.com/kaizen_nagoya/items/bc5dd86e414de402ec29
出力(output)と呼ばないで。これは状態(state)です。
https://qiita.com/kaizen_nagoya/items/80b8b5913b2748867840
これからの情報伝達手段の在り方について考えてみよう。炎上と便乗。
https://qiita.com/kaizen_nagoya/items/71a09077ac195214f0db
ISO/IEC JTC1 SC7 Software and System Engineering
https://qiita.com/kaizen_nagoya/items/48b43f0f6976a078d907
アクセシビリティの知見を発信しよう！（再び）
https://qiita.com/kaizen_nagoya/items/03457eb9ee74105ee618
統計論及確率論輪講（再び）
https://qiita.com/kaizen_nagoya/items/590874ccfca988e85ea3
読者の心をグッと惹き寄せる7つの魔法
https://qiita.com/kaizen_nagoya/items/b1b5e89bd5c0a211d862
「@kazuo_reve 新人の方によく展開している有益な情報」確認一覧
https://qiita.com/kaizen_nagoya/items/b9380888d1e5a042646b
ソースコードで議論しよう。日本語で議論するの止めましょう（あるプログラミング技術の議論報告）
https://qiita.com/kaizen_nagoya/items/8b9811c80f3338c6c0b0
脳内コンパイラの3つの危険
https://qiita.com/kaizen_nagoya/items/7025cf2d7bd9f276e382
心理学の本を読むよりはコンパイラ書いた方がよくね。仮説（34）
https://qiita.com/kaizen_nagoya/items/fa715732cc148e48880e
NASAを超えるつもりがあれば読んでください。
https://qiita.com/kaizen_nagoya/items/e81669f9cb53109157f6
データサイエンティストの気づき!「勉強して仕事に役立てない人。大嫌い!!」『それ自分かも?』ってなった!!!
https://qiita.com/kaizen_nagoya/items/d85830d58d8dd7f71d07
「ぼくの好きな先生」「人がやらないことをやれ」プログラマになるまで。仮説（37）
https://qiita.com/kaizen_nagoya/items/53e4bded9fe5f724b3c4
なぜ経済学徒を辞め、計算機屋になったか（経済学部入学前・入学後・卒業後対応） 転職(1)
https://qiita.com/kaizen_nagoya/items/06335a1d24c099733f64
プログラミング言語教育のXYZ。 仮説（52）
https://qiita.com/kaizen_nagoya/items/1950c5810fb5c0b07be4
【24卒向け】9ヶ月後に年収１０００万円を目指す。二つの関門と三つの道。
https://qiita.com/kaizen_nagoya/items/fb5bff147193f726ad25
「【25卒向け】Qiita Career Meetup for STUDENT」予習の勧め
https://qiita.com/kaizen_nagoya/items/00eadb8a6e738cb6336f
大学入試不合格でも筆記試験のない大学に入って卒業できる。卒業しなくても博士になれる。
https://qiita.com/kaizen_nagoya/items/74adec99f396d64b5fd5
全世界の不登校の子供たち「博士論文」を書こう。世界子供博士論文遠隔実践中心 安全(99)
https://qiita.com/kaizen_nagoya/items/912d69032c012bcc84f2
小川メソッド 覚え（書きかけ）
https://qiita.com/kaizen_nagoya/items/3593d72eca551742df68
DoCAP（ドゥーキャップ）って何ですか？
https://qiita.com/kaizen_nagoya/items/47e0e6509ab792c43327
views 20,000越え自己記事一覧
https://qiita.com/kaizen_nagoya/items/58e8bd6450957cdecd81
Views１万越え、もうすぐ１万記事一覧 最近いいねをいただいた213記事
https://qiita.com/kaizen_nagoya/items/d2b805717a92459ce853
amazon 殿堂入りNo1レビュアになるまで。仮説(102)
https://qiita.com/kaizen_nagoya/items/83259d18921ce75a91f4
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 初稿 20231217
最後までおよみいただきありがとうございました。
いいね 💚、フォローをお願いします。
Thank you very much for reading to the last sentence.
Please press the like icon 💚 and follow me for your happy life.