LoginSignup
0
0

More than 1 year has passed since last update.

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

Last updated at Posted at 2022-02-06

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

2 Normative references

ISO 14229-1, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements
ISO 14229-2, Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
ISO 27145-2, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 2: Common data dictionary
ISO 27145-3, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 3: Common message dictionary
ISO 27145-4, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements — Part 4: Connection between vehicle and test equipment

Terms and Definitions

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.2 Abbreviated terms

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

Bibliography

[1] ISO 11898-1, Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical signalling
[2] ISO 11898-2, Road vehicles — Controller area network (CAN) — Part 2: High-speed medium access unit
[3] ISO 13400 (all parts), Road vehicles — Diagnostic communication over Internet Protocol (DoIP)
[4] ISO 15031 (all parts), Road vehicles — Communication between vehicle and external equipment for emissions-related diagnostics
[5] ISO 15765-2, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services
[6] ISO 15765-4, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 4: Requirements for emissions-related systems
[7] ISO/IEC 7498-1, Information technology — Open Systems Interconnection — Basic Reference Model: The Basic Model
[8] ISO/IEC 10731, Information technology — Open Systems Interconnection — Basic Reference Model — Conventions for the definition of OSI services
[9] IEEE 802.3, IEEE Standard for Information technology — Specific requirements — Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications
[10] SAE J1930-DA, Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms Web Tool Spreadsheet
[11] SAE J1939-73, Recommended Practice for a Serial Control and Communications Vehicle Network — Application Layer Diagnostics
[12] SAE J1939, Companion Spreadsheet
[13] SAE J1979-DA, Digital Annex of E/E Diagnostic Test Modes
[14] SAE J2012-DA, Diagnostic Trouble Code Definitions
[15] CCR 1968.2 Title 13, California Code Regulations, Section 1968.2, Malfunction and Diagnostic System Requirements for 2004 and Subsequent Model-Year Passenger Cars, Light-Duty Trucks, and Medium-Duty Vehicles and Engines (OBD II), available at: http://www.arb.ca.gov/msprog/obdprog/obdregs.htm
[16] CCR 1971.1 Title 13, California Code Regulations, Section 1971.1, On-Board Diagnostic System Requirements for 2010 and Subsequent Model-Year Heavy-Duty Engines (HD OBD), available at: http://www.arb.ca.gov/msprog/obdprog/hdobdreg.htm
[17] Global Technical Regulation No. 5, Technical Requirements for On-Board Diagnostic Systems (OBD) for Road Vehicles. United Nations Economic and Social Council, 15 November 2006, document: ECE/TRANS/180/Add.5 dated 23 January 2007, available at: http://www.unece.org/trans/main/wp29/wp29wgs/wp29gen/wp29registry/gtr5.html

参考資料

@kazuo_reve 自動車の故障診断に関連するプログラマーになりたての方が参照するとよさそうな情報

@kazuo_reve AUTOSARのClassic PlatformとAdaptive PlatformにおけるDiagnosticsの違いを整理

自己参照

ISO Road vehicles Diagnostics 規格調査中 100規格、100記事をめざして。

ISO Diagnostics 文献(Normative Reference and Bibliography)集め

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

ISO/IEC OSIに学ぶ

ISO 14229-1:2020 Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer

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

@kazuo_reve「AUTOSARのClassic PlatformとAdaptive PlatformにおけるDiagnosticsの違いを整理」で慌てて

<この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。>

文書履歴

ver. 0.01 初稿 20220206

0
0
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
0
0