Specification of Diagnostics,  AUTOSAR 723, R21-11 AP

Diagnostics関連のAUTOSARの資料を順に確認中AUTOSAR R21-11(3) Requirements on Diagnostics

AUTOSAR Advent Calendar 2021
https://qiita.com/advent-calendar/2021/autosar

12/15日の投稿です。

AUTOSARが、12/7 今年の版、R21-11を公開しました。
https://www.autosar.org/news-events/details/release-event-2021-2021-dec-07/

文書は検索してダウンロードできます。

https://www.autosar.org/nc/document-search/

AUTOSAR R21-11(0)公開　Specificationをダウンロード
https://qiita.com/kaizen_nagoya/items/9b3a1b9b8d1e8d7e288e

# Specification of Diagnostics(Adaptive Platform)
 No.723,  2021-11
https://www.autosar.org/fileadmin/standards/R21-11/AP/AUTOSAR_SWS_Diagnostics.pdf

|Document Title |Specification of Diagnostics|
|:--|:--|
|Document Owner |AUTOSAR|
|Document Responsibility |AUTOSAR|
|Document Identification No |723|
|Document Status| published|
|Part of AUTOSAR Standard |Adaptive|
|Part of Standard Release |R21-11|

## Document Change  R21 - 11 
>• Document quality improvement and fixing bugs
• Incorporated Quality Scope Review Findings
• Introduced UDS service 29
• Introduced Event Combination in
chapter 7

# Diagnosticsを中心に。

今年は、Diagnosticsを中心に
CAN,Ethernet
OSEK,POSIX/LINUX
セキュリティ、不揮発性メモリ
という４段階に分けて整理する。

C言語、C+＋について言及できるところまで具体化する予定。

|platform|Title|number|URL|Qiita|
|:--|:--|:--|:--|:--|
|F|Requirements on Diagnostics|4|https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_RS_Diagnostics.pdf|3 https://qiita.com/kaizen_nagoya/items/fce079cfd7ce9f6ee4ca|
|C|Specification of Diagnostic Communication Manager|18|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_DiagnosticCommunicationManager.pdf| |
|C|Specification of Diagnostic Event Manager|19|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_DiagnosticEventManager.pdf| |
|F|Main Requirements|54|https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_RS_Main.pdf|2 https://qiita.com/kaizen_nagoya/items/54a9d90272d901ecc089|
|F|Glossary|55|https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_TR_Glossary.pdf|1 https://qiita.com/kaizen_nagoya/items/9eaf0c2a82a39c356f92|
|F|Requirements on Log and Trace|350|https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_RS_LogAndTrace.pdf|4 https://qiita.com/kaizen_nagoya/items/98fde7ffbef358fcf2ed|
|C|Specification of Diagnostic Log and Trace|351|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_DiagnosticLogAndTrace.pdf| |
|C|Specification of Diagnostic over IP|418|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_DiagnosticOverIP.pdf| |
|C|Specification of a Diagnostic Communication Manager for SAE J1939|610|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_SAEJ1939DiagnosticCommunicationManager.pdf| |
|C|Acceptance Test Specification of Diagnostic Services|627|https://www.autosar.org/fileadmin/user_upload/standards/tests/1-2/AUTOSAR_ATS_DiagnosticServices.pdf| |
|C|Diagnostic Extract Template|673|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_TPS_DiagnosticExtractTemplate.pdf| |
|C|Requirements on Diagnostic Extract Template|681|https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_RS_DiagnosticExtractTemplate.pdf| |
|A|Specification of Manifest AUTOSAR_TPS_ManifestSpecification|713|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_TPS_ManifestSpecification.pdf| |
|A|Specification of Execution Management AUTOSAR_SWS_ExecutionManagement|721|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_ExecutionManagement.pdf| |
|A|Specification of Diagnostics|723|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_Diagnostics.pdf|6 https://qiita.com/kaizen_nagoya/items/ed65d04518231c2df96d|
|A|Log and Trace Protocol Specification|787|https://qiita.com/kaizen_nagoya/items/724143aa4e529e3fd079|5 https://qiita.com/kaizen_nagoya/items/724143aa4e529e3fd079|
|A|Specification of Log and Trace|853|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_LogAndTrace.pdf| |
|A|Specification of Persistency AUTOSAR_SWS_Persistency|858|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_Persistency.pdf| |
|A|Specification of Adaptive Platform Core AUTOSAR_SWS_AdaptivePlatformCore
|903|https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_AdaptivePlatformCore.pdf
| |

# 用語(term)

|Term|Description|
|:--|:--|
|AA |AUTOSAR Adaptive Application
|AP |AUTOSAR Adaptive Platform
|Channel |An abstraction of a network specific communication channel. In CAN networks a Channel can be identified via CAN identifier. In Ethernet networks a Channel might be defined by the quadruple Src-IP, Src-Port, Target-IP, Target-Port.
|CP| AUTOSAR Classic Platform
|DEXT| AUTOSAR Diagnostic Extract[3], describing diagnostic configuration of an ECU
|DM |AUTOSAR Adaptive Diagnostic Management
|DTC| Diagnostic Trouble Code according to ISO 14229-1[1]
|DDID |Dynamically Defined Data Identifier according to ISO 14229-1[1].
|DID| Data Identifier according to ISO 14229-1[1]. This 16 bit value uniquely defines one ore more data elements (parameters) that can are used in diagnostics to read, write or control data.
|ECU| Electronic control unit
|EDR| Extended Data Record
|Execution Management| Functional cluster Execution Management
|FDC |Fault Detection Counter according to 14229-1[1]. Has always the value range from -128 = FDCmin = "FinallyHealed" to +127 = FDCmax = "FinallyDefective"
|GID| Group identifier as used in DoIP
|MetaInfo| Meta-Information in the form of a key-value map, which is given from DM to external service processors.
|NRC |Negative Response Code used by UDS in the diagnostic response to indicate the tester that a certain failure has occurred and the diagnostic request was not processed.
|OBD| "On-Board Diagnostics"; Generally: A vehicles ability for self diagnosis and reporting to external test tools. Specifically here, the protocol is meant, as defined in SAE J1979, ISO 15031, ISO 27145 and others.
|OEM |"Original Equipment Manufacturer", but in this document herein, it is used for "Vehicle Manufacturer".
|PDID |Periodic Data Identifier according to ISO 14229-1[2].
|PowerMode| Vehicle basic status information retrieval of DoIP
|SA| SourceAddress of a UDS request
|SID |Service Identifier, identifying a diagnostic service according to UDS, such as 0x14 ClearDiagnosticInformation
|TA| TargetAddress of a UDS request
|UDS| Unified Diagnostic Services
|VIN |Vehicle Identification Number according to ISO-3779
|Dcm| Diagnostic Communication Manager (Module of the AUTOSAR Classic Platform)
|DoIP| Diagnostics over Internet Protocol (Communication protocol of automotive electronics according to ISO-13400[5])
|Aging| Unlearning/deleting of a no longer failed event/DTC after a defined number of operation cycles from event memory.
|Diagnostic Client| A Diagnostic Client is a diagnostic service requester, i.e. sends a UDS request to the Diagnostic Server. Usually the Diagnostic Client is an external tester equipment but can also be another vehicle internal ECU.
|Diagnostic Communication Management|Diagnostic Communication Management is the part of the Diagnostic Management which belongs to tester communication and the processing of UDS services.
|Diagnostic Conversation| Diagnostic Conversation represents a conversation between Diagnostic Client (Tester) and Diagnostic Server.
|Diagnostic Event Management| Diagnostic Event Management is the part of the Diagnostic Management which belongs to processing and storing of diagnostic events and associated data.
|Diagnostic Management| Diagnostic Management is a placeholder for the complete functionality of diagnostic communication and event handling.
|Diagnostic Server instance| Diagnostic Server (DM) is intended to support an own Diagnostic Server instance per installed SoftwareCluster, see section 7.5 for a detailed description. Each of those Server instances has and manages its own resources and is responsible for dispatching and processing of diagnostic services.
|Diagnostic Service instance| A diagnostic service instance implements a concrete use of a diagnostic service in a given context. It refers to a DiagnosticServiceClass and the DiagnosticAccessPermission , see 7.5.1.5.3 for a detailed description.
|Displacement| In case of an Event memory overflow: Replacing the most insignificant stored event memory entry by a reported event which needs to be stored and is more significant.
|DTC group| Uniquely identifies a set of DTCs. A DTC group is mapped to the range of valid DTCs. By providing a group of DTCs it is expressed that a certain operation is requested on all DTCs of that group. The DTC group definition is provided by ISO 14229-1[1] and OEM/supplier-specific.
|DTCStatusAvailabilityMask| The DTCStatusAvailabilityMask - byte is used in UDS responses to requests for certain sub-functions of service 0x19. It express which of the UDS DTC status bits are supported by the DM for masking purposes.
|Enable Conditions| The criteria / conditions under which the test results from the monitors in the AA’s are valid and shall be processed by DM. Configuration is done per event.
|Extended Data Records| Contains statistical data for a DTC. Extended data records are assigned to DTCs and maintained and stored by the DM.
|Event |An event (also diagnostic event) uniquely identifies a fault path of the system. An application monitors the system and reports events to the DM.
|Event memory |The DM stores information about events in the event memory. There can be multiple event memories, each keeping information independently from each other. Examples of the event memory is the UDS primary event memory or the up to 256 user-defined event memories.
|Event memory overflow |An event memory overflow occurs, if this specific event memory is full and the next event occurs to be stored in this event memory.
|Event status| Bit-packed status information based on Event level. Contains the following bits: Nr. Definition: • 0 testFailed • 1 testFailedThisOperationCycle • 6 testNotCompletedThisOperationCycle Compare UDS DTC status bit
|Fail-safe reaction| (Sometimes also called "limp home mode"): Reaction to avoid or minimize harm or damage in case of a failure.
|GroupOfAllDTCs |Identifies a special DTC group that contains all DTCs. This DTC group is identified by the DTC value 0xFFFFFF in 14229-1[1] and contains by default all DTCs of a fault memory. It is present by default in the DM and requires no configuration.
|Internal, External| Classifies if a DiagnosticDataElement is either managed internally inside DM or by an external adaptive applications, see 7.5.4.1 for the precise definition.
|Internally, Externally| Definition of the support type of a SID by the DM. Internally means processing is done by DM itself, Externally means an external service processor is used.
|internal data element| A DiagnosticDataElement which is provided by the DM itself. See also 7.5.4.1.
|Monitor| A monitor (also diagnostic monitor) is a piece of software running within an application, monitoring the correct functionality of a certain system part. The result of such a function check is reported to the DM in form of a diagnostic event.
|Operation cycle| A new operation cycle is the start of a new monitoring cycle. This is reflected in a reset of the testFailedThisOperationCycle and testNotCompletedThisOperationCycle bits in the DTC status and optional notification to the monitor to restart the monitoring.
|Primary event memory| The primary event memory is used to store events and event related data. It is typically used by OEMs for after sales purposes, containing information to repair the vehicle.
|Snapshot Record |Set of measurement values stored in the fault memory at a certain point of time during fault detection. It is used to gain environmental data information for occurred faults.
|SoftwareCluster| A SoftwareCluster groups all AUTOSAR artifacts which are relevant to deploy software on a machine. This includes the definition of applications, i.e. their executables, application manifests, communication and diagnostics. In the context of diagnostics a SoftwareCluster can be addressed individually by its own set of diagnostic addresses.
|SourceAddress| A Source Address is used to encode client and server identifiers. In a UDS request the source address encodes the Diagnostic Client whereas the source address in a UDS response encodes the Diagnostic Server.
|TargetAddress |A Target Address is used to encode client and server identifiers. In a UDS request the target address encodes the Diagnostic Server whereas the target address in a UDS response encodes the Diagnostic Client.
|Transport Protocol Handler |A subcomponent of DM implementing a particular Transport Protocol (either DoIP or any other proprietary UDS Transport Layer).
|Transport Protocol Manager| Link between UDS Transport Layer and Application Layer.
|UDS service| A diagnostic service as defined in ISO 14229-1[1].
|UDS DTC status bit |UDS DTC status bit as defined in ISO 14229-1[1] Annex D.2; Each single bit position represents and documents a certain status information for the connected DTC. The following eight bits are defined: Nr: Definition: 0 testFailed 1 testFailedThisOperationCycle 2 pendingDTC 3 confirmedDTC 4 testNotCompletedSinceLastClear 5 testFailedSinceLastClear 6 testNotCompletedThisOperationCycle 7 warningIndicatorRequested All eight bits constitute the UDS DTC status byte. Compare Event status 
|UDS DTC status byte |Bit-packed DTC status information byte as defined in ISO 14229- 1[1], based on DTC level. Contains the UDS DTC status bits.
|User-defined event memory |The user-defined event/fault memory is used by the UDS service 0x19 with subfunctions 0x17, 0x18 and 0x19. It behaves as the primary event memory but contains data independent from the primary fault memory. It is used to store information that are relevant for different purposes such as warranty or development.
|Non-volatile Memory |In the context of DM, Non-volatile Memory refers to the persistent information over the shutdown of the DM process. This does not depend on HW details.


# 英日単語帳
日本語は仮訳

|no.|count|word|日本語|
|:----|:----|:----|:----|
|1|4807|the|その|
|2|4776|sws_dm_|sws_dm_|
|3|3295|of|の|
|4|2821|diag|diagnostic(短縮名）|
|5|2304|uds|uds|
|6|2248|to|に|
|7|2020|diagnostic|診断|
|8|1610|ara|AUTOSAR Runtime for Adaptive Applications(短縮名|
|9|1418|a|一つの|
|10|1217|x|x|
|11|1143|nrc|Negative Response Code（短縮名）|
|12|1135|rs_diag_|rs_diag_|
|13|1101|in|の|
|14|1076|is|です|
|15|1017|draft|下男|
|16|1015|for|にとって|
|17|945|c|c|
|18|937|data|与件|
|19|874|class|級|
|20|866|error|誤り|
|21|845|return|戻る|
|22|809|according|によると|
|23|796|event|行事|
|24|792|function|働き|
|25|769|code|符号|
|26|769|iso|International Organization for Standardization(短縮名）|
|27|761|domain|領域|
|28|750|this|これ|
|29|749|and|と|
|30|749|service|奉仕|
|31|714|d|d|
|32|705|shall|しなければならない|
|33|682|negative|否定的|
|34|675|autosar|AUTomotive Open System Architecture(短縮名)|
|35|615|errc|error code(短縮名）|
|36|605|dtc|Diagnostic Trouble Code(短縮名）|
|37|590|id|identifier, 識別子(短縮名）|
|38|583|instance|実例|
|39|566|interface|界面|
|40|552|dm|diagnostic message(短縮名）|
|41|536|specification|仕様|
|42|529|if|もし|
|43|522|r|r|
|44|517|kind|親切|
|45|516|by|に|
|46|516|diagnostics|診断|
|47|516|document|資料|
|48|515|identifier|識別子|
|49|513|on|の上|
|50|498|ap|adaptive platform(短縮名)|
|51|480|autosar_sws_diagnostics|autosar_sws_diagnostics|
|52|469|be|です|
|53|468|description|説明|
|54|460|type|型|
|55|459|value|価値|
|56|453|element|要素|
|57|440|header|見出し|
|58|440|symbol|像|
|59|432|an|と|
|60|432|status|状態|
|61|431|scope|範囲|
|62|429|core|芯|
|63|427|file|紙ばさみ|
|64|418|include|含む|
|65|413|h|h|
|66|412|syntax|構文|
|67|401|with|と|
|68|398|request|要求|
|69|388|server|奉仕者|
|70|374|transport|輸送|
|71|365|response|応答|
|72|354|message|伝言|
|73|354|meta|超|
|74|333|atp|AUTOSAR Template Profile(短縮名）|
|75|324|or|または|
|76|319|not|ない|
|77|309|no|いいえ|
|78|286|name|名前|
|79|284|conversation|会話|
|80|284|rs_ap_|rs_ap_|
|81|282|as|なので|
|82|278|security|あんしん|
|83|275|processing|処理|
|84|271|info|information(短縮名）|
|85|267|memory|記憶装置|
|86|264|information|情報|
|87|264|note|覚書|
|88|264|port|港|
|89|261|std|standard(短縮名）|
|90|260|uds_transport|uds_transport|
|91|257|set|設定する|
|92|250|that|それ|
|93|244|from|から|
|94|244|tags|札|
|95|236|cancellation|取り消し|
|96|234|monitor|監視|
|97|229|handler|扱う人|
|98|225|space|空間|
|99|218|application|応用|
|100|217|session|節|


pdftotextが、[ifをdifと認識。

# Reference 

参照の仕方が駄々草。国際規格の番号を記載していない。なにしてくれちゃうんだAUTOSAR。

AUTOSAR文書の番号を記載していない。

[1] Unified diagnostic services (UDS) – Part 1: Specification and requirements (Release 2013-03) http://www.iso.org
[2] Unified diagnostic services (UDS) – Part 1: Application layer (Release 2020-02) http://www.iso.org
[3] Diagnostic Extract Template, AUTOSAR_TPS_DiagnosticExtractTemplate
[4] Glossary, AUTOSAR_TR_Glossary
https://www.autosar.org/fileadmin/standards/foundation/21-11/AUTOSAR_TR_Glossary.pdf
[5] Road vehicles – Diagnostic communication over Internet Protocol (DoIP), http://www.iso.org
[6] Specification of Adaptive Platform Core, AUTOSAR_SWS_AdaptivePlatformCore
[7] Specification of Execution Management, AUTOSAR_SWS_ExecutionManagement
[8] Specification of Log and Trace, AUTOSAR_SWS_LogAndTrace
[9] Specification of Persistency, AUTOSAR_SWS_Persistency
[10] Requirements on Diagnostics, AUTOSAR_RS_Diagnostics
[11] Road vehicles – Diagnostics on Controller Area Networks (CAN) – Part2: Network layer services
[12] Road vehicles – Diagnostic communication over Internet Protocol (DoIP) – Part 2: Network and transport layer requirements and services, http://www.iso.org
[13] Specification of Manifest, AUTOSAR_TPS_ManifestSpecification
[14] Unified diagnostic services (UDS) - Part 2: Session layer services (Release 2013-03), http://www.iso.org

### [1] 
Unified diagnostic services (UDS) – Part 1: Specification and requirements (Re- lease 2013-03)
http://www.iso.org

ISO 14229-1:2013
Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements
https://www.iso.org/standard/55283.html

### [2] 
Unified diagnostic services (UDS) – Part 1: Application layer (Release 2020-02) http://www.iso.org

ISO 14229-1:2020
Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer
https://www.iso.org/standard/72439.html 

### [3] 
Diagnostic Extract Template AUTOSAR_TPS_DiagnosticExtractTemplate
https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_TPS_DiagnosticExtractTemplate.pdf

### [4] 
Glossary AUTOSAR_TR_Glossary
https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_TR_Glossary.pdf

### [5] 
Road vehicles – Diagnostic communication over Internet Protocol (DoIP) http://www.iso.org

Partを記載しない場合は、全Partを意味する。しかし、

ISO 13400-1:2011
Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 1: General information and use case definition

は、すでに廃止している。これを含むか、含まないかの注記をしないのは不親切かも。

ISO 13400-2:2019/CD AMD 1
Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 2: Transport protocol and network layer services — Amendment 1
https://www.iso.org/standard/84208.html

ISO 13400-3:2016
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

ISO 13400-4:2016
Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 4: Ethernet-based high-speed data link connector
https://www.iso.org/standard/57317.html

### [6] 
Specification of Adaptive Platform Core AUTOSAR_SWS_AdaptivePlatformCore
903
https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_AdaptivePlatformCore.pdf

### [7] 
Specification of Execution Management AUTOSAR_SWS_ExecutionManagement
721
https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_ExecutionManagement.pdf

### [8] 
Specification of Log and Trace AUTOSAR_SWS_LogAndTrace
853
https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_LogAndTrace.pdf

### [9] 
Specification of Persistency AUTOSAR_SWS_Persistency
858
https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_SWS_Persistency.pdf

### [10] 
Requirements on Diagnostics AUTOSAR_RS_Diagnostics
4
https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_RS_Diagnostics.pdf

### [11] 
Road vehicles – Diagnostics on Controller Area Networks (CAN) – Part2: Network layer services

ISO 15765-2:2004
Road vehicles — Diagnostics on Controller Area Networks (CAN) — Part 2: Network layer services
https://www.iso.org/standard/33616.html

標題かすると上記。７年後に改定している。どっちのつもりか不明。

ISO 15765-2:2011
Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services
https://www.iso.org/standard/54499.html

### [12] 
Road vehicles – Diagnostic communication over Internet Protocol (DoIP) – Part 2: Network and transport layer requirements and services
http://www.iso.org

この文字列の国際規格は検索で出て来ない。ひょうっとしたら

ISO 13400-2:2012
Road vehicles - Diagnostic communication over Internet Protocol (DoIP) — Part 2: Transport protocol and network layer services
https://www.iso.org/standard/53766.html

ISO 13400-2:2019
Road vehicles — Diagnostic communication over Internet Protocol (DoIP) — Part 2: Transport protocol and network layer services
https://www.iso.org/standard/74785.html

### [13] 
Specification of Manifest AUTOSAR_TPS_ManifestSpecification
713

https://www.autosar.org/fileadmin/user_upload/standards/adaptive/21-11/AUTOSAR_TPS_ManifestSpecification.pdf

### [14] 
Unified diagnostic services (UDS) - Part 2: Session layer services (Release 2013- 03)
http://www.iso.org

ISO 14229-2:2013 
Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
https://www.iso.org/standard/45763.html

なんで2021を参照しないんだろう。

ISO 14229-2:2021
Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
https://www.iso.org/standard/77322.html

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

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

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


<この項は書きかけです。順次追記します。>
This article is not completed. I will add some words and/or centences in order.
Este artículo no está completo. Agregaré algunas palabras en orden.

## 知人資料
' @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

## 自己記事一覧
Qiitaで逆リンクを表示しなくなったような気がする。時々、スマフォで表示するとあらわることがあり、完全に削除したのではなさそう。2024年４月以降、せっせとリンクリストを作り、統計を取って確率を説明しようとしている。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

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

祝休日・謹賀新年 2025年の目標
https://qiita.com/kaizen_nagoya/items/dfa34827932f99c59bbc

Qiita 1年間をまとめた「振り返りページ」＠2024
https://qiita.com/kaizen_nagoya/items/ed6be239119c99b15828

2024 参加・主催Calendarと投稿記事一覧 Qiita(248)
https://qiita.com/kaizen_nagoya/items/d80b8fbac2496df7827f

主催Calendar2024分析 Qiita(254)
https://qiita.com/kaizen_nagoya/items/15807336d583076f70bc

Calendar 統計
https://qiita.com/kaizen_nagoya/items/e315558dcea8ee3fe43e

LLM 関連 Calendar 2024 
https://qiita.com/kaizen_nagoya/items/c36033cf66862d5496fa

Large Language Model Related Calendar 
https://qiita.com/kaizen_nagoya/items/3beb0bc3fb71e3ae6d66

博士論文 Calendar 2024 を開催します。 
https://qiita.com/kaizen_nagoya/items/51601357efbcaf1057d0

博士論文(0)関連記事一覧
https://qiita.com/kaizen_nagoya/items/8f223a760e607b705e78

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

日本のプログラマが世界で戦える16分野。仮説(53),統計と確率(25) 転職(32)、Ethernet(58)
https://qiita.com/kaizen_nagoya/items/a7e634a996cdd02bc53b

小川メソッド　覚え（書きかけ）
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

水道局10年(1976,4-1986,3)を振り返る
https://qiita.com/kaizen_nagoya/items/707fcf6fae230dd349bf

小川清最終講義、最終講義（再）計画, 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.
Este artículo es una impresión personal basada en mi experiencia personal. No tiene nada que ver con la organización o empresa a la que pertenezco actualmente.
### 文書履歴(document history)
ver. 0.01 初稿
ver. 0.02 一覧更新、Document Change/参考資料追記
### 最後までおよみいただきありがとうございました。
いいね　💚、フォローをお願いします。
#### Thank you very much for reading to the last sentence.
Please press the like icon 💚　and follow me for your happy life.
#### Muchas gracias por leer hasta la última oración.
Por favor, haz clic en el ícono Me gusta 💚 y sígueme para tener una vida feliz.