《SAE J2178-4-1999 Class B Data Communication Network Messages--Part 4 Message Definitions for Three Byte Headers.pdf》由会员分享，可在线阅读，更多相关《SAE J2178-4-1999 Class B Data Communication Network Messages--Part 4 Message Definitions for Three Byte Headers.pdf（37页珍藏版）》请在三一文库上搜索。
1、SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising therefr
2、om, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions. QUESTIONS REGARDING THIS DOCUMENT: (724) 772-8512 FAX: (724) 776-0243 TO PLACE A DOCU
3、MENT ORDER; (724) 776-4970 FAX: (724) 776-0790 SAE WEB ADDRESS http:/www.sae.org Copyright 1999 Society of Automotive Engineers, Inc. All rights reserved.Printed in U.S.A. SURFACE VEHICLE 400 Commonwealth Drive, Warrendale, PA 15096-0001 RECOMMENDED PRACTICE Submitted for recognition as an American
4、National Standard J2178-4 REV. MAR1999 Issued1995-02 Revised1999-03 Superseding J2178/4 FEB95 (R) Class B Data Communication Network Messages Message Definitions for Three Byte Headers TABLE OF CONTENTS 1.Scope . 3 2.References. 4 2.1Related Publications. 4 2.1.1SAE Publications 4 2.1.2ANSI Publicat
5、ion 4 3.Terms and Definitions. 4 4Abbreviations and Acronyms 5 5.General Information 6 6.Functional Target Address Assignments (Primary ID) . 7 7.Function Read Target Address Assignments. 10 8.Message Assignments . 10 8.1Engine Torque 12 8.2Engine Air Intake 12 8.3Throttle . 13 87.4Air Conditioning
6、Clutch. 13 8.5Engine RPM . 13 8.6Wheels . 14 8.7Vehicle Speed 14 8.8Traction Control 14 8.9Brakes 15 8.10Steering/Steering Wheel 15 8.11Transmission/Transaxle/PRNDL 16 8.12Engine Sensors - Other 16 8.13Engine Coolant. 17 8.14Engine Oil. 17 8.15Engine Systems - Other . 18 SAE J2178-4 Revised MAR1999
7、-2- 8.16Suspension.18 8.17Vehicle Speed Control19 8.18Charging System 19 8.19Charging System 20 8.20Electrical Energy Management.21 8.21Odometer21 8.22Fuel System21 8.23Ignition Switch/Starter.22 8.24Tell Tales 22 8.25Climate Control (HVAC)23 8.26Window Wiper/Washer .23 8.27Mirrors.24 8.28Door Locks
8、24 8.29External Access25 8.30Seat Motion/Control25 8.31Windows .26 8.32Steering Column.26 8.33Seat Switches.27 8.34Restraints27 8.35Exterior Lamps Outage.28 8.36Exterior Lamps29 8.37Interior Lamps Outage30 8.38Interior Lamps.30 8.39Tires31 8.40Defrost 31 8.41Displays 31 8.42Exterior Environment 31 8
9、.43Interior Environment .32 8.44Time/Date .32 8.45Vehicle Identification.33 8.46Network Control33 9.Extended Address Assignments.33 9.1Brakes, Tires, and Wheels33 9.2HVAC Zones.34 9.3Window Wiper/Washer, Defrost, and Photocell34 9.4Mirrors.34 9.5Doors and Door Locks34 9.6Seats and Restraints 35 9.7W
10、indows .35 9.8External Lamps.35 9.9Internal Lamps36 10.Notes 21 10.1Marginal Indicia.21 标准分享网 w w w .b z f x w .c o m 免费下载 SAE J2178-4 Revised MAR1999 -3- 1.Scope This SAE Recommended Practice defines the information contained in the header and data fields of non-diagnostic messages for automotive s
11、erial communications based on SAE J1850 Class B networks. This document describes and specifies the header fields, data fields, field sizes, scaling, representations, and data positions used within messages. The general structure of a SAE J1850 message frame without in-frame response is shown in Fig
12、ure 1. The structure of a SAE J1850 message with in-frame response is shown in Figure 2. Figures 1 and 2 also show the scope of frame fields defined by this document for non-diagnostic messages. Refer to SAE J1979 for specifications of emissions related diagnostic message header and data fields. Ref
13、er to SAE J2190 for the definition of other diagnostic data fields. The description of the network interface hardware, basic protocol definition, the electrical specifications, and the CRC byte are given in SAE J1850. FIGURE 1 SCOPE OF SAE J2178 FOR A SAE J1850 FRAME WITHOUT IN-FRAME RESPONSE (IFR)
14、FIGURE 2 SCOPE OF SAE J2178 FOR A SAE J1850 FRAME WITH IN-FRAME RESPONSE (IFR) SAE J1850 defines two and only two formats of message headers. They are the Single Byte header format and the Consolidated header format. The Consolidated header format has two forms, a Single Byte form and a three byte f
15、orm. This document covers all of these formats and forms to identify the contents of messages which could be sent on a SAE J1850 network. This document consists of four parts, each published separately. SAE J2178-1 (Titled: Detailed Header Formats and Physical Address Assignments) describes the two
16、allowed forms of message header formats, single byte and consolidated. It also contains the physical node address range assignments for the typical sub-systems of an automobile. SAE J2178-2 (Titled: Data Parameter Definitions) defines the standard parametric data which may be exchanged on SAE J1850
17、(Class B) networks. The parameter scaling, ranges, and transfer functions are specified. Messages that refer to these parametric definitions shall always adhere to these parametric definitions. It is intended that at least one of the definitions for each parameter in this part match the SAE J1979 de
18、finition. SAE J2178-3 (Titled: Frame IDs for Single Byte Forms of Headers) defines the message assignments for the single byte header format and the one byte form of the consolidated header format. SAE J2178-4 (this part, Titled: Message Definition for Three Byte Headers) defines the message assignm
19、ents for the three byte form of the consolidated header format. SAE J2178-4 Revised MAR1999 -4- 2.References 2.1Related Publications The following publications are provided for information purposes only and are not a required part of this document. 2.1.1SAE PUBLICATIONS Available from SAE, 400 Commo
20、nwealth Drive, Warrendale, PA 15096-0001. SAE J1213/1 JUN91 Glossary of Vehicle Networks for Multiplex and Data Communication SAE J1850 AUG91 Class B Data Communication Network Interface SAE J1930 SEP91 Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms SAE J197
21、9 DEC91 E/E Diagnostic Test Modes SAE J2190 JUN93 Enhanced E/E Diagnostic Test Modes 2.1.2ANSI PUBLICATION Available from ANSI, 11 West 42nd Street, New York, NY 10036-8002. ANSI/IEEE Std 754-1985, August 12, 1985 IEEE Standard for Binary Floating-Point Arithmetic 3.Terms and Definitions 3.1Data Dat
22、a Field Data and data field are used interchangeably in this document and they both refer to a field within a frame that may include bytes with parameters pertaining to the message and/or secondary ID and/or extended addresses and/or test modes which further defines a particular message content bein
23、g exchanged over the network. 3.2Extended Address The extended address is a means to allow a message to be addressed to a specific geographical location or zone of the vehicle, independent of any nodes physical address. 3.3Frame A frame is one complete transmission of information which may or may no
24、t include an In-Frame Response. The frame is enclosed by the start of frame and end of frame symbols. For Class B networks, each frame contains one and only one message (see “message“ definition below). 3.4Frame ID The Frame ID is the header byte for the Single Byte Header format and the one byte fo
25、rm of the Consolidated header format. The definition of the frame ID is found in SAE J2178/3. This header byte defines the target and source and content of the frame. 3.5Functional Addressing Functional addressing allows a message to be addressed or sent to one or more nodes on the network intereste
26、d in that function. Functional addressing is intended for messages that may be of interest to more than a single node. For example, an exterior lamp “off“ message could be sent to all nodes controlling the vehicle exterior lamps by using a functional address. The functional address consists of a pri
27、mary ID and may include a secondary ID and may also include an extended address. 3.6Header Header Field The header (or header field, used interchangeably) is a one or three byte field within a frame that contains information about the message priority, message source and target addressing, message t
28、ype, and in-frame response type. 3.7In-Frame Response (IFR) Type The IFR type identifies the form of the in-frame response which is expected within that message. 3.8Load The load command indicates the operation of directly replacing the current/existing value of a parameter with the parameter value(
29、s) contained in the message. 3.9Message A message consists of all of the bytes of a frame excluding the delimiter symbols (SOF, EOD, EOF, NB). 标准分享网 w w w .b z f x w .c o m 免费下载 SAE J2178-4 Revised MAR1999 -5- 3.10 Modify The modify command indicates the operation of using the message data parameter
30、 value to change (e.g., increment, decrement, or toggle) the current/existing value. 3.11 Parameter A parameter is the variable quantity included in some messages. The parameter value, scaling, offset, units, transfer function, etc., are unique to each particular message. (The assigned parameters ar
31、e contained herein.) 3.12 Physical Addressing Physical addressing allows a message to be addressed to a specific node or to all nodes or to a non-existent, null node. The information in this message is of relevance only to a particular node, so the other nodes on the bus should ignore the message, e
32、xcept for the case of the “all nodes“ address. 3.13 Primary ID The primary ID identifies the target for this functional message. This is the primary discriminator used to group functions into main categories. 3.14 Priority The priority describes the rank order and precedence of a message. Based upon
33、 the SAE J1850, Class B arbitration process, the message with the highest priority will win arbitration. 3.15 Report A report indicates the transmission of parametric data values, based on: a change of state; a change of value; on a periodic rate basis; or as a response to a specific request. 3.16 R
34、equest A request is a command to, or a query for data, or action from another node on the network. 3.17 Response Data The response data is the information from a node on the network in response to a request from another node on the network. This may be an in-frame response or a report type of messag
35、e. 3.18 Secondary ID The secondary ID (along with the primary ID or Frame ID) identifies the functional target node for a message. The purpose of the secondary ID field within the frame is to further define the function or action being identified by the primary ID. 4.Abbreviations and Acronyms A/C-
36、Air Conditioning ASC- ASCII Encoded SLOT BCD- Binary Coded Decimal (BCD) SLOT BMM- Bit Mapped with Mask SLOT BMP- Bit Mapped without Mask SLOT CRC- Cyclic Redundancy Check CS- Checksum DTC- Diagnostic Trouble Code EOD- End of Data EOF- End of Frame ERR- Error Detection EV-ETS - Electric Vehicle Ener
37、gy Transfer System EVSE- Electric Vehicle Supply Equipment HVAC- Heating, Ventilation, Air Conditioning ID- Identifier IFR- In-Frame Response LSB- Least Significant Bit/Byte MSB- Most Significant Bit/Byte NB- Normalization Bit PID- Parameter IDentification (number, NOT the primary ID, (see Section 7
38、) PKT- Multiple Parameter Packet SLOT PRN- Parameter Reference Number SED- State Encoded SLOT SAE J2178-4 Revised MAR1999 -6- SFP- Signed Floating Point (Scientific Notation) SLOT SLOT- Scaling, Limit, Offset, and Transfer Function (see Section 8) SNM- 2s Complement Signed Numeric SLOT SOF- Start of
39、 Frame UNM- Unsigned Numeric SLOT VIN- Vehicle Identification Number 5.General Information The messages defined by this four part document are specified for networks using one byte headers or consolidated one and three byte headers as specified in SAE J1850. This part focuses on the message definiti
40、on for the three byte form of the consolidated header format. Section 5 consists of the list of functional target addresses for all of the functionally addressed SAE J1850 messages except Type #3, Function Read. The SAE J1850 Type #3 messages have a separate address assignment because this message t
41、ype does not support any secondary addressing. Functional target addresses (Primary IDs) are shown in Section 5 and secondary message definitions are shown in Section 7. Section 6 shows the valid extended address assignments which are referenced in the message definition tables. The information in t
42、he header field contains target, source, priority and message type information, while the data field contains additional addressing and parametric information. This information is explicitly defined in some headers and implicitly defined in others. Messages can be classified generally into two types
43、: a.Requests, that is, commands (load or modify) or queries for data, and b.Responses, that is, reports or acknowledgments. When a node generates a request, the target node(s) which is/are responsible for the requested data or function must respond by sending the requested information or by performi
44、ng the requested function. For responses (that is, reports or acknowledgments), data information that a node responds with may be requested by another node, or reported by the node when the desired information has changed, or reported by the node on a periodic basis. This document defines a great nu
45、mber of specific messages which are expected to have wide application. Designers are required to use the defined messages on SAE J1850 networks in the exact way that they are defined here. There are a large number of message codes which are reserved for each manufacturer to define. If the user canno
46、t find a needed message, he or she is expected to define a manufacturer specific message in these reserved codes. Therefore, messages on different manufacturers products using these “Manufacturer Reserved“ codes will have meaning only for that manufacturer or specific vehicle. These will most likely
47、 be different between manufacturers. The codes that are defined here, however, shall always carry the same meaning from one manufacturer to another and from one model and year to the next. 6.Functional Target Address Assignments (Primary ID) Primary IDs are used to address a generic function. The se
48、cond byte of the three byte header contains this primary ID. Each target function has a separate ID for command and status messages. The command ID is used to control a function while the status ID is used to report a condition or report that a command has been executed. Each primary ID pair then co
49、ntains a secondary address, optional geographical extended address, and optional parametric data. Table 1 below lists the primary ID assignments, command and status, and a description. Those IDs labeled as “Reserved - SAE“ are reserved for the SAE to define at a later time while those labeled “Reserved - MFG“ are left for the individual manufacturers to use. 标准分享网 w w w .b z f x w .c o m 免费下载 SAE J2178-4 Revised MAR1999 -7- TABLE 1 PRIMARY ID ASSIGNMENTS BYTE 2 OF MESSAGE TYPES 0, 1, 2, 8, 9, 10, 11 CommandStatusFunction 0001Reserved - SAE 0203Reserved