SSF 14230Road Vehicles - Diagnostic Systems
Keyword Protocol 2000 - Part 2 - Data Link Layer
Swedish Implementation Standard
Based on ISO 14230-2 Data Link Layerca126
Status:Issue 1
Date: April 22, 1997
This document is based on the International
Standard ISO 14230 Keyword Protocol 2000 and
has been further developed to meet Swedish
automotive manufacturer's requirements by the
Swedish Vehicle Diagnostics Task Force.
It is based on mutual agreement between the
following companies:
•Saab Automobile AB
•SCANIA AB
•Volvo Car Corp.
•Volvo Bus Corp.
•Mecel AB
File: 14230-2s.DOC / Definition by “Samarbetsgruppen för Svensk Fordonsdiagnos” / Author: L. Magnusson Mecel AB
Document updates and issue history
This document can be revised and appear in several versions. The document will be classified in order to allow identification of updates and versions.
优化组织结构A. Document status classification The document is assigned the status Outline, Draft or Issue.
It will have the Outline status during the initial phase when parts of the document are not yet written.
The Draft status is entered when a complete document is ready, which can be submitted for reviews. The draft is not approved. The draft status can appear between issues, and will in that case be indicated together with the new issue Draft Issue 2.
An Issue is established when the document is reviewed, corrected and approved.
B. Version number and history procedure
Each issue is given a number and a date. A history record shall be kept over all issues.
Document in Outline and Draft status may also have a history record.
C. History
Issue #Date Comment
197 04 22Frst issue
Table of Content
1. SCOPE (1)
2. NORMATIVE REFERENCE (2)
3. PHYSICAL TOPOLOGY (3)
4. MESSAGE STRUCTURE (4)
4.1 Header (4)
4.1.1 Format byte (4)
4.1.2 Target address byte (5)
4.1.2.1 Physical addressing (5)
4.1.2.2 Functional addressing (5)
4.1.3 Source address byte (5)
4.1.4 Length byte (5)
4.1.5 Use of header bytes (6)
4.2 Data Bytes (6)
4.3 Checksum Byte (6)
4.4 Timing (7)
4.4.1 Timing Exceptions (9)
4.4.2 Periodic transmission (9)
4.4.3 Server (ECU) Response Data Segmentation (12)
4.5 End Of Message (12)
5. COMMUNICATION SERVICES (13)
5.1 StartCommunication Service (14)
5.1.1 Service Definition (14)
5.1.1.1 Service Purpose (14)
5.1.1.2 Service Table (14)
5.1.1.3 Service Procedure (14)
5.1.2 Implementation (14)
5.1.2.1 Key bytes (15)
5.1.2.2 Fast Initialisation (17)
5.2 StopCommunication Service (19)
5.2.1 Service Definition (19)
5.2.1.1 Service Purpose (19)
5.2.1.2 Service Table (19)
师东兵
5.2.1.3 Service Procedure (19)
5.2.2 Implementation (20)
5.3 AccessTimingParameter Service (21)
5.3.1 Service Definition (21)
5.3.1.1 Service Purpose (21)
5.3.1.2 Service Table (21)
5.3.1.3 Service Procedure (22)
5.3.2 Implementation (23)
5.4 SendData Service (25)
5.4.1 Service Definition (25)
5.4.1.1 Service Purpose (25)
航空装备表面处理技术
5.4.1.2 Service Table (25)
5.4.1.3 Service Procedure (25)
5.4.2 Implementation (26)
6. ERROR HANDLING (27)
6.1 Error handling during physical/functional Fast Initialisation (27)
6.1.1 Client (tester) Error Handling during physical/functional Fast Initialisation (27)
6.1.2 Server (ECU) Error Handling during physical Fast Initialisation (27)
6.1.3 Server (ECU) Error Handling during functional Fast Initialisation (28)
6.2 Error handling after Initialisation (28)
6.2.1 Client (tester) communication Error Handling (28)
6.2.2 Server (ECU) communication Error Handling. physical addressing (29)
6.2.3 Server (ECU) Error Handling, functional addressing (29)
APPENDIX A - ARBITRATION
1. DEFINITIONS (1)
1.1 Random response time (1)
1.2 Start bit detection (1)
1.3 Transmission latency (1)
1.4 Collision detection (1)
2. MAINSTREAM COMMUNICATION (1)
APPENDIX B - TIMING DIAGRAMS
1. PHYSICAL ADDRESSING (1)
1.1 Physical addressing - single positive response message (1)
1.2 Physical addressing - more than one positive response message (3)
1.3 Physical addressing - periodic transmission (5)
2. FUNCTIONAL ADDRESSING (7)
名与实
2.1 Functional addressing - single positive response message -
single server (ECU) addressed (7)
2.2 Functional addressing - more than one response message -
single server (ECU) addressed (9)
2.3 Functional addressing - single positive response message -
more than one server (ECU) (11)
百家讲坛周汝昌2.4 Functional addressing - more than one response message -
more than one server (ECU) (13)
APPENDIX C - MESSAGE FLOW EXAMPLES
1. PHYSICAL INITIALISATION - MORE THAN ONE SERVER (ECU) INITIALISED (1)
2. PERIODIC TRANSMISSION MODE (4)
2.1 Message Flow Example A (4)
2.2 Message Flow Example B (5)
Introduction
This document (The Swedish Keyword Protocol 2000 Implementation Standard) is based on the ISO 14230-2 International Standard. Changes are indicated by changing the font from "Arial" to "Times New Roman"!
It has been established in order to define common requirements for the implementation of diagnostic services for diagnostic systems.
To achieve this, the standard is based on the Open System Interconnection (O:S:I.) Basic Reference Model in accordance with ISO 7498 which structures communication systems into seven layers. When mapped on this model, the services used by a diagnostic tester and an Electronic Control Unit (ECU) are broken into:
- Diagnostic services (layer 7)
- Communication services (layers 1 to 6)
See figure 1 below.
豫公网安备41160202000603
站长QQ:729038198
关于我们
投诉建议