ISO Diagnostics(14) 用語定義(Terms and Definition) 短縮名(short name)集め

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

もうすぐ20文献になりそう。そこで、補助資料を作り始める。

一つは、

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

もう一つは、ISO Diagnostics 用語定義(Terms and Definition)と短縮名(short name)集め。つまりこの記事。

<この項は書きかけです。順次追記します。>
This article is not completed. I will add some words in order.
# 3. 用語定義
## 3.1
3.1 diagnostic power mode
abstract vehicle internal power supply state, which affects the diagnostic capabilities of all servers on the in-vehicle networks and which identifies the state of all servers of all gateway sub-networks that allow diagnostic communication
Note 1 to entry: The intent is to provide information to the client DoIP entity about whether diagnostics can be performed on the connected vehicle or whether the vehicle needs to be put into a different diagnostic power mode (i.e. technician interaction required). In this document, the following states are relevant: Not Ready (not all servers accessible via DoIP can communicate), Ready (all servers accessible via DoIP can communicate) and Not Supported (the Diagnostic Information Power Mode Information Request message is not supported).
3.2 DoIP edge node
host (3.4) inside the vehicle, where an Ethernet activation line in accordance with ISO 13400-3 is terminated and where the link from the first node/host in the external network is terminated
[SOURCE:ISO 13400‑3:2011, 3.1.2, modified — definition editorially revised.]
3.3 DoIP entity certificate
certificate issued by an intermediate CA (3.5)to the DoIP entity presented during the TLS handshake to the client DoIP entity to verify the authenticity of this DoIP entity
3.4 host
node connected to the IP-based network
3.5 intermediate certificate authority
intermediate CA
authority, which issues subordinal certificates to another intermediate CA or DoIP entities
3.6 intermediate certificate
certificate either stored in the client DoIP entity or is presented during authentication together with the end node certificate to complete the chain of trust
3.7 invalid source address
address outside the reserved range for client(s) DoIP entity
3.8 logical address
address identifying a diagnostic application layer entity
3.9 network node
device connected to the IP-based network (e.g. Ethernet) and which communicates using Internet protocol but does not implement the DoIP protocol
Note 1 to entry: Some network nodes might also be connected to a vehicle sub-network (3.14), but they are not DoIP gateways as they don’t implement the DoIP protocol. Consequently, these network nodes do not interact with (e.g. respond to) DoIP-compliant client DoIP entity.
3.10 root certificate authority
authority, which acts as the root of trust
Note 1 to entry: Typically issues intermediate certificates (3.6) to allow an intermediate CA (3.5) to further submit certificates.
3.11 root certificate
certificate created by the root certificate authority (3.10) and used as the trust anchor
Note 1 to entry: It is securely stored and used by all entities that wants to validate end node certificates (e.g. from the DoIP entity) together with all necessary intermediate certificates (3.6) in the chain of trust.
3.12 socket
unique identification, as defined in IETF RFC 147, to or from which information is transmitted in the network
3.13 unknown source address
address not listed in the connection table entry
3.14 vehicle sub-network
network not directly connected to the IP-based network
Note 1 to entry: Data can only be sent to and from a vehicle sub-network through the connecting DoIP gateway.

## 3.2 
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.

## 3.3
3.1.1 connection
two mated connectors (3.1.2) or contacts (3.1.3)
3.1.2connector
assembly of contact (3.1.3) and housing, which terminates conductors for the purpose of providing connection (3.1.1) and disconnection to a suitable mating connector
3.1.3 contact
conductive element in a connector (3.1.2) (including means for cable attachment), which mates with a corresponding element to provide an electrical path
3.1.4 female contact
electrical contact (3.1.3) (including means for cable attachment) intended to make electrical engagement on its inner surface and to accept entry of a male contact (3.1.5), thus forming an electrical connection (3.1.1)
EXAMPLE:Receptacle, sleeve.
3.1.5 male contact
electrical contact (3.1.3) (including means for cable attachment) intended to make electrical engagement on its outer surface and to enter a female contact (3.1.4), thus forming an electrical connection (3.1.1)
EXAMPLE:Tab, pin, blade.
## 3.4
3.1 boot memory partition
area of the server (3.18) memory in which the boot software (3.2) is located
3.2 boot software
software which is executed in a special part of server (3.18) memory which is used primarily to boot the ECU (3.9) and perform server programming
Note 1 to entry: This area of memory is not erased during a normal programming sequence and executes when the server application is missing or otherwise deemed invalid to always ensure the capability to reprogram the server.
Note 2 to entry: See 0 and 17.3.1.1.
3.3 client
function that is part of the tester (3.20) and that makes use of the diagnostic services (3.6)
Note 1 to entry: A tester normally makes use of other functions such as data base management, specific interpretation, human-machine interface.
3.4 diagnostic channel
dedicated transmission path from client (3.3) to server (3.18) for diagnostic communication
Note 1 to entry: Several simultaneously connected clients to one server can be differentiated by an individual tester (3.20) source address.
3.5 diagnostic data
data that is located in the memory of an electronic control unit (3.9) which may be inspected and/or possibly modified by the tester (3.20)
Note 1 to entry: Diagnostic data includes analogue inputs and outputs, digital inputs and outputs, intermediate values and various status information.
Note 2 to entry: Examples of diagnostic data are vehicle speed, throttle angle, mirror position, system status, etc. Three types of values are defined for diagnostic data:
— the current value: the value currently used by (or resulting from) the normal operation of the electronic control unit;
— a stored value: an internal copy of the current value made at specific moments (e.g. when a malfunction occurs or periodically); this copy is made under the control of the electronic control unit;
— a static value: e.g. VIN.
The server (3.18) is not obliged to keep internal copies of its data for diagnostic purposes, in which case the tester may only request the current value.
Note 3 to entry: Defining a repair shop or development testing session selects different server functionality (e.g. access to all memory locations may only be allowed in the development testing session).
3.6 diagnostic service
information exchange initiated by a client (3.3) in order to require diagnostic information from a server (3.18) or/and to modify its behaviour for diagnostic purpose
3.7 diagnostic session
state within the server (3.18) in which a specific set of diagnostic services (3.6) and functionality is enabled
3.8 diagnostic trouble code, DTC
numerical common identifier for a fault condition identified by the on-board diagnostic system
3.9 ECU, electronic control unit
unit providing information regarding the connected sensor and control network
Note 1 to entry: Systems considered as electronic control units include anti-lock braking system (ABS) and engine management system.
3.10 functional unit
set of functionally close or complementary diagnostic services (3.6)
3.11 local server
server (3.18) that is connected to the same local network as the client (3.3) and is part of the same address space as the client
3.12 permanent DTC
diagnostic trouble code (3.8) that remains in non-volatile memory, even after a clear DTC request, until other criteria (typically regulatory) are met (e.g. the appropriate monitors for each DTC have successfully passed)
Note 1 to entry: Refer to the relevant legislation for all necessary requirements.
3.13 record
one or more diagnostic data (3.5) elements that are referred to together by a single means of identification
Note 1 to entry: A snapshot including various input/output data and trouble codes is an example of a record.
3.14 remote server
server (3.18) that is not directly connected to the main diagnostic network
Note 1 to entry: A remote server is identified by means of a remote address. Remote addresses represent an own address space that is independent from the addresses on the main network.
Note 2 to entry: A remote server is reached via a local server (3.11) on the main network. Each local server on the main network can act as a gate to one independent set of remote servers. A pair of addresses therefore always identifies a remote server: one local address that identifies the gate to the remote network and one remote address identifying the remote server itself.
3.15 remote client
client (3.3) that is not directly connected to the main diagnostic network
Note 1 to entry: A remote client is identified by means of a remote address.
Note 2 to entry: Remote addresses represent an own address space that is independent from the addresses on the main network.
3.16 reprogramming software
part of the boot software (3.2) that allows for reprogramming of the electronic control unit (3.9)
3.17 security
mechanism for protecting vehicle modules from "unauthorized" intrusion through a vehicle diagnostic data (3.5) link
3.18 server
function that is part of an electronic control unit (3.9) and that provides the diagnostic services (3.6)
Note 1 to entry: This document differentiates between the server (i.e. the function) and the electronic control unit to ensure independence from implementation.
3.19 supported DTC
diagnostic trouble code (3.8) which is currently configured/calibrated and enabled to execute under predefined vehicle conditions.
3.20 tester
system that controls functions such as test, inspection, monitoring, or diagnosis of an on-vehicle electronic control unit (3.9) and can be dedicated to a specific type of operator (e.g. an off-board scan tool dedicated to garage mechanics, an off-board test tool dedicated to assembly plants, or an on-board tester)
Note 1 to entry: The tester is also referenced as the client (3.3).
## 3.5
3.1 gateway
networking device that transfers the PDU on different OSI layers
EXAMPLE:A network device that enables communication between control module networks that uses different communication protocols, different communication rates, etc. and that includes, but is not limited to, gateway functionalities like bridge, switch (3.3), router (3.2) or application layer routing.
3.2 router
networking device that transfers the PDU on OSI layers 3 and 4
3.3 switch
networking device that transfers the PDU on OSI layer 2

## 3.6
no terms.

## 3.7
3.1 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 14229-2, ISO 14230-2, ISO 15031-2, and ISO 15765-2 and the following apply.
3.1.1 absolute throttle position sensor

value intended to represent the throttle opening
Note 1 to entry: For systems where the output is proportional to the input voltage, this value is the percent of maximum input signal. For systems where the output is inversely proportional to the input voltage, this value is 100 % minus the percent of maximum input signal. Throttle position at idle usually indicates greater than 0 % and throttle position at wide open throttle usually indicates less than 100 %.
3.1.2 bank

土手
specific group of cylinders sharing a common control sensor
共通制御センサーを共有するシリンダの特定グループ
Note 1 to entry: Bank 1 always contains cylinder number 1 and bank 2 the opposite bank.
Note 2 to entry: If there is only one bank, the DTCs for bank #1 DTCs are used and the word bank may be omitted. 
With a single “bank” system utilizing multiple sensors, bank #1 DTCs are used in identifying the sensors as #1, #2, and #3 in order as they move further away from the cylinder.
3.1.3 base fuel schedule

fuel calibration schedule programmed into the powertrain control module or PROM when manufactured or when updated by an off-board source, prior to any learned on-board correction
3.1.4 calculated load value

typically an indication of the current airflow divided by peak airflow at wide open throttle as a function of rpm, where airflow is corrected for altitude and ambient temperature
Note 1 to entry: Both spark ignition and compression ignition vehicles can use an alternate definition that substitutes engine torque in place of airflow in the calculation.
Note 2 to entry: This definition provides a number (without unit) and provides the service technician with an indication of the percent engine capacity that is being used.
3.1.5 client

function that is part of the tester and that makes use of the diagnostic services
Note 1 to entry: A tester normally makes use of other functions such as database management, specific interpretation, and man-machine interface.
3.1.6 continuous monitoring

sampling at a rate no fewer than two samples per second
Note 1 to entry: If, for control purposes, a computer input is sampled less frequently, the signal of the component may instead be evaluated each time sampling occurs.
3.1.7 convention, Cvt

column integrated in each message table which marks each parameter included
Note 1 to entry: The following conventions are used: C = Conditional: the parameter marked “C” in a request/response message is present only under a condition specified in the bottom row of the message table; M = Mandatory: the parameter marked “M” in a request/response message table is always present; U = User (optional): the parameter marked “U” in a request/response message table is supplied depending on dynamic usage by the manufacturer. The convention recommends a mnemonic, which might be used for implementation. In no case is the specified mnemonic ever a mandatory requirement for any implementation.
3.1.8 electronic control unit, ECU

generic term for any electronic control unit
3.1.9 emissions-related DTC

DTC which is set when a malfunction causes vehicle emissions to exceed legislated emission thresholds or is otherwise required to be set as specified by on-board diagnostics legislation (e.g. disables another part of the diagnostic system)
Note 1 to entry: Normally, the malfunction indicator (MI) is illuminated at the same time as the emissions-related DTC is set. The determination of which DTCs are emissions-related is made by the vehicle manufacturer for each vehicle, as specified by on-board diagnostic legislation.
3.1.10 fuel trim, FT

feedback adjustments to the base fuel schedule
Note 1 to entry: Short-term fuel trim refers to dynamic or instantaneous adjustments. Long-term fuel trim refers to much more gradual adjustments to the fuel calibration schedule than short-term trim adjustments. These long-term adjustments compensate for vehicle differences and gradual changes that occur over time.
3.1.11 negative numbers

signed binary, the most significant bit (MSB) of the binary number used to indicate positive (0)/negative (1)
Note 1 to entry: 2's complement: negative numbers are represented by complementing the binary number and then adding 1.
EXAMPLE:–0,99 = 800116 = 1000 0000 0000 00012
0 = 000016 = 0000 0000 0000 00002
+0,99 = 7FFF16 = 0111 1111 1111 11112
Note 2 to entry: (–0,99) + (+0,99) = 0.
3.1.12 number

expressed by this symbol “#”
3.1.13 P2, P3 timing parameter

application timing parameters for the ECU(s) and the external test equipment
3.1.14 P2CAN_min timing parameter

CAN application timing parameter with the minimum value for the ECU(s) and the external test equipment to start the response message
3.1.15 P2CAN_max timing parameter

CAN application timing parameter with the maximum value for the ECU(s) and the external test equipment to indicate a response message
3.1.16 P2reload timing parameter

CAN application timing parameter with the maximum value (P2CAN_max) for external test equipment only
3.1.17 server

function that is part of an ECU that provides the diagnostic services
Note 1 to entry: This part of ISO 15031 differentiates between the server, i.e. the function, and the electronic control unit so that it remains independent from the implementation.
3.1.18 service

information exchange initiated by a client (external test equipment) in order to require diagnostic information from a server (ECU) and/or to modify its behavior for diagnostic purposes
Note 1 to entry: This is also the equivalent of test mode or mode.
## 3.8
3.1 OBDonEDS
on-board diagnostics on emission diagnostic service
application protocol request and response messages defined in ISO 15031-5/SAE J1979[4] dedicated to the diagnostics of emissions-related systems
3.2 OBDonUDS
on-board diagnostics on unified diagnostic service application protocol request and response messages defined in the ISO 14229 series and in ISO 27145-3 or SAE J1979-2[5] dedicated to the diagnostics of emissions-related systems
## 3.9
3.1 OBDonEDS
on-board diagnostics on emission diagnostic service[4] application protocol request and response messages defined in ISO 15031-5/SAE J1979 dedicated tothe diagnostics of emissions-related systems
3.2 OBDonUDS
on-board diagnostics on unified diagnostic service application protocol request and response messages defined in the ISO 14229 series and in ISO 27145-3[5] or SAE J1979-2 dedicated to the diagnostics of emissions-related systems

## 3.10
3.1.1 calibration identifier: CALID
identification code for the software installed in the electronic control unit
3.1.2 calibration verification number: CVN
server/ECU calculated verification number used to verify the integrity of the software in the electronic control unit
3.1.3 central gateway: CGW
electronic control unit that connects in-vehicle communication networks
3.1.4 data identifier: DID
indicator making reference to a data item in the server
3.1.5 diagnostic trouble code: DTC
value making reference to a specific fault in a system implemented in the server
Note 1 to entry: It is defined in SAE J2012-DA or as SPN and FMI as defined in SAE J1939 Companion Spreadsheet and SAE J1939-73:2010, Appendix A.
3.1.6 info type identifier: ITID
indicator making reference to identification information
EXAMPLE:Calibration identifier in the server.
Note 1 to entry: The ITIDs are defined in SAE J1979-DA.
3.1.7 malfunction indicator: MI
display or gauge that clearly informs the driver of the vehicle in the event of a malfunction/failure
Note 1 to entry: Additional details are included in the WWH-OBD GTR.
3.1.8 monitor identifier: MID
indicator making reference to an OBD monitor function
Note 1 to entry: An example of an OBD monitor function is a misfire monitor in the server. The MID is defined in SAE J1979-DA.
3.1.9 standard/manufacturer monitor test identifier: SMTID
OBD identifier which is defined in SAE J1979-DA or by the vehicle manufacturer
3.1.10 parameter identifier: PID
unique identifier used to refer to a specific data value within a server
3.1.11 routine identifier: RID
identifier making reference to a routine function
Note 1 to entry: An example of a routine function is an evaporation monitor routine in the server.
Note 2 to entry: Routine identifiers are defined in SAE J1979-DA.
3.1.12 suspect parameter number: SPN
numeral that identifies a particular element, a fault associated with a component, such as a sensor, or a parameter associated with an ECU
3.1.13 uniform resource locator: URL
uniform resource identifier which, in addition to identifying a resource, provides a means of locating the resource by describing its primary access mechanism
Note 1 to entry: An example of primary access mechanism is its network location.

## 3.11
3.1.1 global technical regulation: GTR
agreement establishing global technical regulations for wheeled vehicles and equipment and parts that can be fitted and/or used on wheeled vehicles
## 3.12
No Terms and Definitions
## 3.13
未確認
## 3.14
No Terms and Definitions
## 3.15
3.1.1 calibration identifier, CALID
identification code for a specific software/calibration contained in a server/ECU
Note 1 to entry: If regulations require calibration identifications for emissions-related software, these are reported in a standardized format as specified in ISO 27145-2.
3.1.2 class A, B1, B2, C malfunction
attribute of a DTC, which characterizes the impact of a failure on emissions or on the OBD system's monitoring capability according to the requirements of the WWH-OBD GTR
3.1.3continuous malfunction indicator, continuous-MI
malfunction indicator showing a steady indication at all times while the key is in the on (run) position with the engine running [ignition ON - engine ON]
3.1.4 continuous malfunction indicator counter, continuous-MI counter
conveys the amount of time the OBD system was operational during the time a continuous-MI was last activated
Note 1 to entry: For a detailed definition, see GTR No. 5.
3.1.5 confirmed and active DTC
DTC status, which is detected during two consecutive operation cycles, in which the DTC is still present and commands the MI to be on if the DTC class is A, B1 or B2
Note 1 to entry: For a DTC of class C, the MI is not illuminated.
3.1.6 cumulative continuous malfunction indicator counter, cumulative continuous-MI counter
cumulated operating hours with a continuous-MI activated
Note 1 to entry: The cumulative continuous-MI counter counts up to the maximum value provided in a 2-byte counter with 1 h resolution and holds that value. The cumulative continuous-MI counter is not reset to zero by the engine system, a scan tool or a disconnection of a battery. 
The cumulative continuous-MI counter operates in the following manner:
a) the cumulative continuous-MI counter begins counting once the continuous-MI is activated;
b) the cumulative continuous-MI counter halts and holds its existing value once the continuous-MI is no longer activated;
c) the cumulative continuous-MI counter continues counting from the point at which it had been held when a continuous-MI was activated.
3.1.7 calibration verification number, CVN
server/ECU calculated verification number used to verify the integrity of the software/calibration contained in a server/ECU
Note 1 to entry: If regulations require calibration identifications for emissions-related software, those are reported in a standardized format as specified in ISO 27145- 2.
3.1.8 discriminatory display
requires the MI to be activated according to the class in which a malfunction has been classified
3.1.9 malfunction
failure or deterioration of a vehicle or engine system or component, including the OBD system, during which the WWH-OBD GTR specifically identifies the conditions which are considered to be failures
3.1.10 malfunction indicator, MI
display or gauge that clearly informs the driver of the vehicle in the event of a malfunction/failure
Note 1 to entry: Additional details are included in the WWH-OBD GTR.
3.1.11 malfunction indicator counter, MI counter
conveys the amount of time during which the OBD system operates while a failure/breakdown is active
3.1.12 non-discriminatory display
indicator requiring only a single type of MI activation
3.1.13 on-board diagnostics, OBD
system that monitors some or all computer input and control signals
Note 1 to entry: Signal(s) outside of the predetermined limits imply a fault in the system or in a related system.
3.1.14 previously active DTC
DTC status that is first detected during two consecutive operation cycles but later detection shows that the fault is no longer present
3.1.15 vehicle identification number, VIN
numeral identifying and specific and unique to each vehicle according to the applicable legal provisions of each national/regional authority
3.1.16 vehicle on-board diagnostics
providing a single access point for external test equipment to retrieve all data of the OBD system

## 3.16
No Terms and Definitions

## 3.17

## 3.18

## 3.19
3.1 inspection
See ISO 4092.
3.2 test
See ISO 4092.
3.3 diagnosis
See ISO 4092.
3.4 diagnostic tester
See ISO 4092.
This non-built-in equipment may be used in the vehicle.
3.5 system
Assemblage of components performing a specific function, for example an assemblage of an ECU with its associated sensors, actuators and interconnections.
3.6 ECU
Abbreviation of Electronic Control Unit.
3.7 bus
One or more conductors connecting two or more ECUs together with the purpose of communicating with the test equipment.
3.8 NRZ
Abbreviation of Non-Retum-to Zero — a method of representing binary signals in which there is no change of signal levels between two successive bits of the same logic level.
3.9 baud rate
Number of binary elements of information transmitted per second on one line.
3.10 LSB
Abbreviation of Least Significant Bit.
3.11 MSB
Abbreviation of Most Significant Bit.
3.12 initialization
Process to activate an ECU for starting communication.
3.13 key words
Identifier of a set of specifications for the subsequent serial communication.
This set of specifications defines:
— the specific function of each communication line;
— the format of the digital information such as the protocol, number and meaning of each of the words exchanged; and
— if a redefinition is desired, the format of data such as baud rate, data coding, word length.
3.14 header
First group of serial data transmitted to the diagnostic tester after initialization (if required) before further data exchange commences.
The header consists of
— baud rate synchronization pattern;
— key words.
3.15 bit time
Duration of one unit of information.
## 3.20

## 3.21
3.1.1 CAN frame data length, CAN_DL
physical length of CAN frame data/payload in bytes
Note 1 to entry: See Table 3.
3.1.2 transmit data link layer data length, TX_DL
configures the maximum usable payload length in bytes of the data link layer in the transmitter for the application that implements the network layer as defined in this part of ISO 15765
Note 1 to entry: The TX_DL is a fixed configuration value on the sender side for the PDU transmission.
3.1.3 Received data link layer data length, RX_DL
retrieved maximum usable payload length in bytes of the data link layer in the receiver for the application that implements the network layer as defined in this part of ISO 15765
Note 1 to entry: The RX_DL value is retrieved from the FirstFrame (FF) CAN_DL of a segmented PDU and is used to verify the correct data length of ConsecutiveFrames (CF).

## 3.22
No terms.

# 4. 短縮名(short name)

## 4.1 
未確認

## 4.2
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

## 4.3
100BaseTX Fast Ethernet
CAN Controller Area Network
CAT5 Category 5 cable (two wire-pairs cable)
DC Direct current
GND Ground
PHY Physical layer
MAC Media Access Control
Rx Receiver
Tx Transmitter
xMII Cross wire media independent interface
VBAT Battery voltage
WWH-OBD Worldwide Harmonized On-Board Diagnostics
XFRM Ethernet transformer
## 4.4 
.con service primitive .confirmation
.ind  service primitive .indication 
.req service primitive .request
A_PCI application layer protocol control information 
ACR Authentication with Challenge-Response
APCE Authentication with PKI Certificate Exchange 
BER Basic Encoding Rules according to ITU-T X.690 
CMAC Cipher-based Message Authentication Code 
CVC Card Verifiable Certificate
ECU electronic control unit
EDR event data recorder
GMAC Galois Message Authentication Code
HMAC Hash-based Message Authentication Code 
N/A not applicable
NR_SI negative response service identifier
NRC negative response code
OID Object Identifier according to ISO/IEC 9834-1 
OSI open systems interconnection
PKCS Public-Key Cryptography Standards
PKI Public-Key Infrastructure
POWN Proof of Ownership
RA remote address
SA source address
SI service identifier
TA target address
TA_type target address type
X.509 PKI standard according to ISO/IEC 9594-8
## 4.5
Diag diagnostics
ECU electronic control unit
N/A not applicable
OSI open systems interconnection
RDiag remote diagnostics
S_AE session layer address extension
S_Data session layer data transfer service name
S_Length session layer length of data
S_Mtype session layer message type
S_PDU session layer protocol data unit
S_SA session layer source address
S_TA session layer target address
S_TAtype session layer target address type
SecureDiag secure diagnostics
SecureRDiag secure remote diagnostics
SI service identifier
SOM start of message
SPP service primitive parameter
## 4.6
DID data identifier
DoIP diagnostic communication over Internet Protocol
DoIP_AI DoIP address information
IP Internet Protocol
OSI Open System Interconnection
pDID periodic data identifier
UDS unified diagnostic services
VM vehicle manufacturer

## 4.7 
.con confirmation
.ind indication
.req request
CRC cyclic redundancy check
CVN calibration verification number
DTC diagnostic trouble code
ECM engine control module
ERR error detection byte
EWMA exponential weighted moving average
FF first frame
ISR interrupt service routine
LSB least significant bit
MI malfunction indicator
MIL malfunction indicator light
MSB most significant bit
N_PDU network protocol data unit
N/A not applicable
NRC negative response code
NVRAM non-volatile memory
OBDMID OBD monitor identifier
PID parameter identifier
PCI protocol control information
RSP in-frame response
SF single frame
SOM start of message
T_AE virtual transport interface address extension
T_Data [ ] virtual transport interface data field
T_Mtype virtual transport interface message type
T_Length virtual transport interface length information
T_PDU virtual transport interface protocol data unit
T_Result virtual transport interface result
T_SA virtual transport interface source address
T_TA virtual transport interface target address
T_TAtype virtual transport interface target address type
TCM transmission control module
TID test identifier
UASID unit and scaling identifier
VIN vehicle identification number
## 4.8
CAN controller area network
CBFF Classical Base Frame Format
DID data identifier
DLC data length code
DoCAN diagnostic communication over CAN
ECU electronic control unit
ECM engine control module
ETE external test equipment
OBD on-board diagnostics
PID parameter identifier
PhaseSeg1 phase segment 1
PhaseSeg2 phase segment 2
PropSeg propagation segment
SA source address
SJW synchronisation jump width
SP nominal sample point
SyncSeg synchronization segment
TA target address
TCM transmission control module

## 4.10
CALID calibration identification
CAN controller area network
CGW central gateway
CM conversion method
CVN calibration verification number
DID data identifier
DoCAN diagnostics communication over controller area network
DoIP diagnostics communication over internet protocol
DP data parameter
DP_DB data parameter data byte
DTC diagnostic trouble code
ECM engine control module
ECU electronic control unit
ECUNAME electronic control unit name
EVAP evaporative system
FMI failure mode indicator
FTB failure type byte
GTR global technical regulation
ITID info type identifier
IUPT in-use performance tracking
ITP info type parameter
ITP_DB info type parameter data byte
MI malfunction indicator
MID monitor identifier
Mod module
MP monitor parameter
MP_DB monitor parameter data byte
N/A not applicable
OC occurrence count
Param parameter
PID parameter identifier
req requirement
RID routine identifier
RP_DB routine parameter data byte
SF sub-function
SID service identifier
SMTID standard/manufacturer monitor test identifier
SPN suspect parameter number
URL uniform resource locator
VIN vehicle identification number
VOBD vehicle on-board diagnostics
WWH-OBD world-wide harmonized on-board diagnostics
## 4.11
ASCII American standard code for information interchange
CDTC confirmed DTC
DID diagnostic data identifier
DoCAN diagnostic communication over controller area network
DoIP diagnostic communication over internet protocol
DTC diagnostic trouble code
DTCHB DTC high byte
DTCLB DTC low byte
DTCMB DTC middle byte
DTCS DTC severity
ECM engine control module
ECU electronic control unit
FMI failure mode indicator
FTB failure type byte
GTR global technical regulations
MI malfunction indicator
N/A not applicable
PDTC pending DTC
PDU protocol data unit
RID routine identifier
SFID sub-function identifier
SID service identifier
SODTC status of DTC
SPN suspect parameter number
TNCSLC test not completed since last clear
TNCTOC test not completed this operation cycle
UDS unified diagnostic services
VIN vehicle identification number
WUC warm-up cycle
WWH-OBD world-wide harmonized on-board diagnostics
## 4.12
CAN Controller area network
DHCP Dynamic host configuration protocol
DID Data identifier
DoCAN Diagnostic communication over CAN
DoIP Diagnostic communication over internet protocol
DTC Diagnostic trouble code
ECU Electronic control unit
FMI Failure mode indicator
FTB Failure type byte
GTR Global technical recommendation
IP Internet protocol
N_PDU Network layer protocol data unit
NRC Negative response code
OBD On-board diagnostics
OSI Open systems interconnection
SA Source address
SPN Suspect parameter number
T_PDU Transport/network layer protocol data unit
TA Target address
TCP Transmission control protocol
WWH-OBD World-wide harmonized on-board diagnostics
VOBD Vehicle on-board diagnostics

## 4.13
未確認
## 4.14
ACL additional communication line
CAN Controller Area Network
RHD right-hand-driven
## 4.15
CALID calibration identification
CVN calibration verification number
DTC diagnostic trouble code
DID diagnostic data identifier
DLL data link layer
ECM engine control module
ECU electronic control unit
FMI failure mode indicator
FTB failure type byte
GTR global technical regulations
HS high speed
HS-LPM high speed - low power mode
MI malfunction indicator
SPN suspect parameter number
UDS unified diagnostic services
VIN vehicle identification number
VOBD vehicle on-board diagnostics
WLAN wireless local area network
WWH-OBD world-wide harmonized on-board diagnostics
WWH-OBDonCAN world-wide harmonized on-board diagnostics on controller area network
WWH-OBDonIP world-wide harmonized on-board diagnostics on internet protocol

## 4.16
B1S1 Bank 1 Sensor 1
B1S2 Bank 1 Sensor 2
B1S3 Bank 1 Sensor 3
B2S1 Bank 2 Sensor 1
B2S2 Bank 2 Sensor 2
B2S3 Bank 2 Sensor 3
BARO barometric atmospheric pressure
CVN calibration verification number
DTC diagnostic trouble code
ECM engine control module
ISR interrupt service routine
LSB least significant bit
MAF mass air flow
MAP manifold absolute pressure
MIL malfunction indicator light
MSB most significant bit
OBD On-Board Diagnostics
OSI Open Systems Interconnection
PCM powertrain control module
SI international system of units
TCM transmission control module
## 4.17
## 4.18
## 4.19

## 4.20
DSO Digital storage oscilloscope
DUT Device under test
NA Not applicable
NAD Network access device
PC Personal computer
PID Parameter identifier
PS Power supply

## 4.21
BRS bit rate switch
BS BlockSize
CAN controller area network
CAN_DL CAN frame data link layer data length in bytes
CAN FD controller area network with flexible data rate and larger payload as defined in ISO 11898-1
CLASSICAL CAN controller area network with static data rate and up to 8 data bytes as defined in ISO 11898-1
CF ConsecutiveFrame
CTS continue to send
DLC CAN frame data link layer data length code
DoCAN diagnostic communication over CAN
ECU electronic control unit
FC FlowControl
FF FirstFrame
FF_DL FirstFrame data length in bytes
FMI failure mode indicator
FS FlowStatus
Mtype message type
N/A not applicable
N_AE network address extension
N_AI network address information
N_Ar network layer timing parameter Ar
N_As network layer timing parameter As
N_Br network layer timing parameter Br
N_Bs network layer timing parameter Bs
N_ChangeParameter network layer service name
N_Cr network layer timing parameter Cr
N_Cs network layer timing parameter Cs
N_Data network data
N_PCI network protocol control information
N_PCItype network protocol control information type
N_PDU network protocol data unit
N_SA network source address
N_SDU network service data unit
N_TA network target address
N_TAtype network target address type
N_USData network layer unacknowledged segmented data transfer service name
NW network
NWL network layer
OBD on-board diagnostics
OSI Open Systems Interconnection
PCI protocol control information
RX_DL received data link layer data length in bytes
SF SingleFrame
SF_DL SingleFrame data length in bytes
SN SequenceNumber
SPN suspect parameter number
STmin SeparationTime minimum
TX_DL transmit data link layer data length in bytes
UDS unified diagnostic services
WWH-OBD world-wide harmonized OBD
## 4.22
CF consecutive frame
DA destination address
DLC data length code
FF first frame
FC flow control
ID identifier
NA network address
SA source address
SF single frame
SM subnet mask
SOM start of message
STRT serviceToRespondTo
TA target address
UDS unified diagnostic services
USDT unacknowledged segmented data transfer
UUDT unacknowledged unsegmented data transfer

## 4.25
ASE application-service-element
AS0 application-service-object
OS1 Open Systems Interconnection

## 4.26
AE address extension
APP application
C conditional
Cvt convention
GW gateway
M mandatory
ID identifier
N/A not applicable
NAD node address for slave nodes
P2 server response time
SA source address
SF single frame
TA target address
U user optional

# 対象規格一覧
## 1
ISO 13400-2:2019 Road vehicles - Diagnostic communication over Internet Protocol (DoIP) - Part 2: Transport protocol and network layer services
https://qiita.com/kaizen_nagoya/items/2f7798df491c0b5d9546

## 2 
ISO 13400-3, Road vehicles - Diagnostic communication over Internet Protocol (DoIP) - Part 3: Wired vehicle interface based on IEEE 802.3
https://qiita.com/kaizen_nagoya/items/b8f0a5852c253458051f

## 3
ISO 13400-4:2016 Road vehicles - Diagnostic communication over Internet Protocol (DoIP) - Part 4: Ethernet-based high-speed data link connector
https://qiita.com/kaizen_nagoya/items/517da0535386bcbec62b

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

## 5
ISO 14229-2:2021 Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
https://qiita.com/kaizen_nagoya/items/4aa6aba600354d49fe29

## 6
ISO 14229-5:2013 Road vehicles - Unified diagnostic services (UDS) - Part 5: Unified diagnostic services on Internet Protocol implementation (UDSonIP)
https://qiita.com/kaizen_nagoya/items/aed3b0c16299a9725729

## 7
ISO 15031-5:2015 Road vehicles - Communication between vehicle and external equipment for emissions-related diagnostics - Part 5: Emissions-related diagnostic services
https://qiita.com/kaizen_nagoya/items/2eb9216380ef81729b06

## 8
ISO 15765-4:2021 Road vehicles - Diagnostic communication over Controller Area Network (DoCAN) - Part 4: Requirements for emissions-related systems
https://qiita.com/kaizen_nagoya/items/ddfc1cc36eda753b1d86
## 9
ISO 15765-5:2021 Road vehicles - Diagnostic communication over Controller Area Network (DoCAN) - Part 5: Specification for an in-vehicle network connected to the diagnostic link connector
https://qiita.com/kaizen_nagoya/items/fcb9626f10d3c43bfd4f

## 10
ISO 27145-2:2012 Road vehicles - Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements - Part 2: Common data dictionary
https://qiita.com/kaizen_nagoya/items/11ed6a5bd614e183de34

## 11
ISO 27145-3 ISO 27145-3:2012 Road vehicles - Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements - Part 3: Common message dictionary
https://qiita.com/kaizen_nagoya/items/2d2a00fcb6f6aba8636e

## 12
ISO 27145-4 ISO 27145-4:2016 Road vehicles - Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements - Part 4: Connection between vehicle and test equipment
https://qiita.com/kaizen_nagoya/items/9b762f04aa17e361d9fd
## 13
ISO 15031-2:2010, Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 2: Guidance on terms, definitions, abbreviations and acronyms
https://qiita.com/kaizen_nagoya/items/e96aabf3983f33b884db

## 14
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
https://qiita.com/kaizen_nagoya/items/88bc27aa82710c8a2376

## 15
ISO 27145-1:2012 Road vehicles - Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements - Part 1: General information and use case definition
https://qiita.com/kaizen_nagoya/items/023fd88dc56e2041f08f
##16

ISO 15031-6:2015 Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics — Part 6: Diagnostic trouble code definitions
https://qiita.com/kaizen_nagoya/items/9db02028c8e8c2858411

## 18
ISO 7639:1985 Road vehicles - Diagnostic systems - Graphical symbols
https://qiita.com/kaizen_nagoya/items/4f4020898944653f93e3

## 19
ISO 9141:1989 Road vehicles - Diagnostic systems - Requirements for interchange of digital information
https://qiita.com/kaizen_nagoya/items/7d6300044916763a58c7

## 20
ISO 9141-3:1998 Road vehicles - Diagnostic systems - Part 3: Verification of the communication between vehicle and OBD II scan tool
https://qiita.com/kaizen_nagoya/items/914c7dc263d907af6c63

## 21
ISO 15765-2, Road vehicles - Diagnostic communication over Controller Area Network (DoCAN) - Part 2: Transport protocol and network layer services
https://qiita.com/kaizen_nagoya/items/8f885abf5ff6edbd4bbe
## 22
ISO 14229-3:2012 Road vehicles - Unified diagnostic services (UDS) - Part 3: Unified diagnostic services on CAN implementation (UDSonCAN)
https://qiita.com/kaizen_nagoya/items/d409b29b0b5d4037d4e8

## 23
California Code of Regulation, Title 13, 1968.1, Malfunction and Diagnostic Systems Requirements.
https://qiita.com/kaizen_nagoya/items/4bda8e174a4c394feb34

# 24
SEA J1850 Class B Data Communications Network Interface
https://qiita.com/kaizen_nagoya/items/9aa118008a0528a2c93c

## 25
ISO/IEC 10731:1994, Information technology - Open Systems Interconnection - Basic Reference Model - Conventions for the definition of OSI services
https://qiita.com/kaizen_nagoya/items/dc8a0240b8982ac28dc8
## 26
ISO 14229-8:2020 Road vehicles - Unified diagnostic services (UDS) - Part 8: UDS on Clock eXtension Peripheral Interface (UDSonCXPI)
https://qiita.com/kaizen_nagoya/items/6d546e91830e3c52688e

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

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

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

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

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

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

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

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

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

# 関連資料
' @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 初稿 20220206

### 最後までおよみいただきありがとうございました。
いいね　💚、フォローをお願いします。
#### Thank you very much for reading to the last sentence.
Please press the like icon 💚　and follow me for your happy life.