ISO 13400-3, Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 3: Wired vehicle interface based on IEEE 802.3
https://www.iso.org/standard/68424.html

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

2 Normative references

IEC 60950-1, Information technology equipment — Safety — Part 1: General requirements

IEEE 802.3-2015, IEEE Standard for Ethernet

3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 13400-1 and ISO 14229-1 and the following apply.

3.1 automatic medium-dependent interface crossover

Auto-MDI(X)
device that allows the Ethernet hardware to decide whether a cross-linked cable or a one-to-one connected (patch) cable is used for the connection between two Ethernet ports and which configures the physical layer transceiver (PHY) according to the type of cable in order to correctly connect Tx and Rx linesterm

3.2 DoIP Edge Node

host inside the vehicle, where an Ethernet activation line in accordance with this part of ISO 13400 is terminated and where the link from the first node/host in the external network is terminated

3.3 link segment

twisted-pair link for connecting two physical layers (PHYs) for 100BASE-TX
Note 1 to entry: Adapted from IEEE 802.3:2008, 1.4.355.

4 Abbreviations

Cat5 category 5 cable as specified in TIA/EIA-568-B
DoIP diagnostics over Internet Protocol
DoEth diagnostics over Internet Protocol on Ethernet
FMI failure mode indicator
MAC media access control
MDI medium-dependent interface
PE protective earth conductor
PHY physical layer transceiver
Rx receive
SPN suspect parameter number
Tx transmit

Bibliography

[1] ISO 13400-1, Road vehicles - Diagnostic communication over Internet Protocol (DoIP) — Part 1: General information and use case definition
[2] ISO 13400-2, Road vehicles - Diagnostic communication over Internet Protocol (DoIP) — Part 2: Transport protocol and network layer services
[3] ISO 13400-4, Road vehicles - Diagnostic communication over Internet Protocol (DoIP) — Part 4: Ethernet diagnostic connector
[4] ISO 14229-1, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and Requirements
[5] ISO 14229-2, Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
[6] ISO 14229-5, Road vehicles — Unified diagnostic services (UDS) — Part 5: Unified diagnostic services on Internet Protocol implementation (UDSonIP)
[7] ISO 27145-2, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 2: Common data dictionary
[8] ISO 27145-3, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 3: Common message dictionary
[9] ISO/IEC 7498-1, Information technology — Open Systems Interconnection — Basic Reference Model: The Basic Model — Part 1
[10] ISO/IEC 10731, Information technology — Open Systems Interconnection — Basic Reference Model — Conventions for the definition of OSI services
[11] SAE J1930-DA, Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms Web Tool Spreadsheet
[12] SAE J1939DA, Digital Annex (SPNs)
[13] SAE J1939-73:2010, Application Layer — Diagnostics
[14] SAE J1962, Diagnostic Connector
[15] SAE J1979-DA, Digital Annex of E/E Diagnostic Test Modes
[16] SAE J2012-DA, Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions
[17] TIA/EIA-568-B, Commercial Building Telecommunications Cabling Standard

Content

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviated terms
5 Conventions
6 Document overview.
7 Ethernet physical and data link layer requirements
7.1 General information
7.2 Ethernet physical layer requirements
7.3 Ethernet data link layer requirements
7.4 Ethernet PHY and MAC requirements
7.5 Ethernet activation line requirements
7.5.1 Vehicle activation line requirements
7.5.2 Vehicle activation line circuit example – Option 1 requirements
7.5.3 Vehicle activation line circuit example – Option 2 requirements
7.5.4 Principles of activation line operation
7.5.5 External test equipment activation line requirements
7.5.6 Vehicle manufacturers activation line requirements
7.6 Spice simulation of activation line options
7.7 Process to determine Options 1, 2 or non-ISO 13400
7.8 Cable definitions
Bibliography

Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment,
as well as information about ISO’s adherence to the World Trade Organization (WTO) principles in the
Technical Barriers to Trade (TBT) see the following URL: www.iso.org/iso/foreword.html.
The committee responsible for this document is ISO/TC 22, Road vehicles, Subcommittee SC 31, Data
communication.
This second edition cancels and replaces the first edition (ISO 13400-3:2011), which has been
technically revised.
A list of all parts in the ISO 13400 series can be found on the ISO website.

Introduction

Vehicle diagnostic communication has been developed starting with the introduction of the first
legislated emissions-related diagnostics and has evolved over the years, now covering various use
cases ranging from emission-related diagnostics to vehicle-manufacturer-specific applications like calibration or electronic component software updates.
With the introduction of new in-vehicle network communication technologies, the interface between the vehicle’s electronic control units and the test equipment has been adapted several times to address the specific characteristics of each new network communication technology requiring optimized data link layer definitions and transport protocol developments in order to make the new in-vehicle networks usable for diagnostic communication.
With increasing memory size of electronic control units, the demand to update this increasing amount
of software and an increasing number of functions provided by these control units, technology of the connecting network and buses has been driven to a level of complexity and speed similar to computer networks.
New applications (x-by-wire, infotainment) require high band-width and real-time networks
(like FlexRay, MOST), which cannot be adapted to provide the direct interface to a vehicle. This requires gateways to route and convert messages between the in-vehicle networks and the vehicle interface to
test equipment.
The intent of ISO 13400 (all parts) is to describe a standardized vehicle interface which
— separates in-vehicle network technology from the external test equipment vehicle interface
requirements to allow for a long-term stable external vehicle communication interface,
— utilizes existing industry standards to define a long-term stable state-of-the-art communication
standard usable for legislated diagnostic communication, as well as for manufacturer-specific use
cases, and
— can easily be adapted to new physical and data link layers, including wired and wireless connections,
by using existing adaptation layers.
To achieve this, all parts of ISO 13400 are based on the Open Systems Interconnection (OSI) Basic
Reference Model specified in ISO/IEC 7498-1 and ISO/IEC 10731, which structures communication
systems into seven layers. When mapped on this model, the services specified by ISO 14229-1,
ISO 14229-2 and ISO 14229-5 are divided into
a) unified diagnostic services (layer 7), specified in ISO 14229-1, ISO 14229-5, ISO 27145-3,
b) presentation (layer 6):

for enhanced diagnostics, specified by the vehicle manufacturer,
for WWH-OBD (World-Wide Harmonized On-Board Diagnostics), specified in ISO 27145-2,
SAE J1930-DA, SAE J1939-DA (SPNs), SAE J1939-73:2010, Appendix A (FMI), SAE J1979-DA,
SAE J2012-DA,
c) session layer services (layer 5), specified in ISO 14229-2,
d) transport protocol (layer 4), specified in ISO 13400-2,
e) network layer (layer 3) services, specified in ISO 13400-2, and
f) physical and data link services (layers 1 and 2), specified in this document,
in accordance with Table 1.
Table 1 — Enhanced and legislated WWH-OBD diagnostic specifications applicable to the
OSI layers
OSI 7 layers Vehicle manufacturer enhanced WWH-OBD document reference
diagnostics
Application (layer 7) ISO 14229-1/ISO, 14229 ISO 14229-1/ISO, 27145
Presentation (layer 6) Vehicle manufacturer specific ISO 27145-2, SAE J1930-DA,
SAE J1939-DA (SPNs),
SAE J1939–73:2010, Appendix A
(FMIs), SAE J1979-DA, SAE J2012-
Session (layer 5) ISO 14229-2 ISO 14229-2
Transport (layer 4) ISO 13400-2 DoIP TCP and IP
Network (layer 3)
Data link (layer 2) ISO 13400-3 DoIP, IEEE 802.3
Physical (layer 1)
Seven layers according to ISO/IEC 7498-1 and ISO/IEC 10731.
The application layer services covered by ISO 14229-5 have been defined in compliance with diagnostic services established in ISO 14229-1, but are not limited to use only with them.
The transport and network layer services covered by ISO 13400-2 have been defined to be independent of the physical layer implemented.
For other application areas, this document can be used with any Ethernet physical layer.
Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 3: Wired vehicle interface based on IEEE 802.3
1 Scope
This document specifies the vehicle communication interface and test equipment requirements for a physical and data link layer based on IEEE 802.3 100BASE-TX.
This interface serves as the physical basis for IP-based communication between the vehicle and test equipment. This document specifies the following aspects:
— requirements for signal and wiring schematics in order to ensure physical layer compatibility of the vehicle interface and Ethernet networks and test equipment communication interfaces;
— discovery/identification of the in-vehicle diagnostic Ethernet interface;
— activation and deactivation of the in-vehicle diagnostic Ethernet interface;
— mechanical and electrical diagnostic connector requirements;
— this edition has been modified to include the identification of two Ethernet pin assignments.

4 Abbreviated terms

Cat5 category 5 cable as specified in TIA/EIA-568-B
DoIP diagnostics over Internet Protocol
DoEth diagnostics over Internet Protocol on Ethernet
FMI failure mode indicator
MAC media access control
MDI medium-dependent interface
PE protective earth conductor
PHY physical layer transceiver
Rx receive
SPN suspect parameter number
Tx transmit

5 Conventions

ISO 13400 is based on the conventions discussed in the OSI Service Conventions (ISO/IEC 10731) as they apply to diagnostic services.

6 Document overview

ISO 13400 is applicable to vehicle diagnostic systems implemented on an IP communication network.
ISO 13400 has been established in order to define common requirements for vehicle diagnostic systems implemented on an IP communication link.
Although primarily intended for diagnostic systems, ISO 13400 has been developed to also meet requirements from other IP-based systems needing a transport protocol and network layer services.
Figure 1 illustrates the most applicable application implementations utilizing DoIP.
Figure 1 — DoIP document reference according to the OSI model

7 Ethernet physical and data link layer requirements

7.1 General information

Ethernet is a collection of several standards for different transmission technologies and speeds
contained in IEEE 802.3 and is a frame-based networking technology for wired local area networks.
Frames are defined as the format of data packets on the wire. The Internet Protocol (IPv4) theoretically
allows for a maximum IP packet length of 64 Kbytes. This size is limited by the Ethernet specification,
which defines a 16-bit-length field and requires a minimum packet length of 64 bytes, as well as allowing for a maximum payload length of 1 500 bytes. Consequently, IP packets can have a maximum length of only 1 500 bytes on Ethernet. However, IP allows for fragmentation of IP packets over multiple Ethernet frames to work around this limitation.
The rules for fragmentation of IP packets differ between IPv6 and IPv4 and are not specified in this document.
The Ethernet connection of a vehicle works with four transmission lines in accordance with IEEE 802.3
100BASE-TX, as well as using an additional activation line.
The Ethernet controller in the DoIP Edge Node can be switched on and off via the activation line when the test equipment is connected to, or disconnected from, the vehicle.
There are two types of Ethernet patch cables available:
— one-to-one (1:1) connection, which is usually used to connect an end-node (e.g. a computer) with a network hub or switch. In this case, the pins of each RJ45 connector of the patch cable or the cable to
the vehicle connector are directly connected to each other (e.g. Rx+ on the source port is connected to Rx+ on the destination port).
— cross-linked connection, which is usually used to connect two end nodes directly with each other

参考資料

Diagnostics over Internet Protocol
https://qiita.com/sorairowill/items/0c6189c84c934c8a64a4

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

自己参照

ISO 13400 Diagnostic communication over Internet Protocol (DoIP) ISO 13400-2:2019
https://qiita.com/kaizen_nagoya/items/9c06788ca312b770631c

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

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

関連資料

' @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前に必読記事一覧

登壇直後版色使い(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

自己記事一覧

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初稿　20220202
ver. 0.02 ありがとう追記　20230725

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

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

Thank you very much for reading to the last sentence.

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