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 there
2、from, 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. Copyright 2010 SAE International All rights reserved. No part of this publication m
3、ay be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-4970 (outside U
4、SA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.orgSAE values your input. To provide feedbackon this Technical Report, please visit http:/www.sae.org/technical/standards/J2728_201006SURFACEVEHICLERECOMMENDEDPRACTICEJ2728 JUN2010 Issued 2010-06 Heavy Vehicle Event D
5、ata Recorder (HVEDR) Standard - Tier 1 RATIONALE Not applicable. INTRODUCTION This Recommended Practice (RP) describes a common set of performance requirements for recording, storing, and retrieving data surrounding well-defined events that can occur during the operation of a heavy vehicle. Ultimate
6、ly, three tiers of performance levels for HVEDRs will be developed: Tier 1, which represents the basic functionality of an HVEDR; Tier 2, which includes non-proprietary data available on the vehicle communication network(s), and Tier 3, which addresses relevant proprietary data, as technologies and
7、practices further develop. This document represents the minimum performance specification for a Tier 1 HVEDR. TABLE OF CONTENTS 1. SCOPE 41.1 Purpose . 42. REFERENCES 42.1 Applicable Publications . 42.1.1 SAE Publications . 42.1.2 Other Applicable Publications . 52.2 Related Publications . 53. GLOSS
8、ARY OF TERMS . 53.1 Event . 53.2 Event Trigger . 53.3 Event Record 53.4 Electronic Control Unit (ECU) . 53.5 Vehicle Speed Sensor (VSS) 53.6 Heavy Vehicle . 53.7 Heavy Vehicle Event Data Recorder (HVEDR) 53.8 Tier 1 HVEDR . 63.9 Tier 2 HVEDR . 63.10 Tier 3 HVEDR . 63.11 Data Port . 63.12 Data Extrac
9、tion Tool 63.13 Data Format Conversion . 63.14 MID / PID (Message Identification / Parameter Identification) 63.15 PGN / SPN / SA (Parameter Group Number / Suspect Parameter Number / Source Address) 6SAE J2728 Issued JUN2010 Page 2 of 484. TECHNICAL REQUIREMENTS 74.1 Event Trigger . 74.2 Data Elemen
10、ts . 74.2.1 Data Element Recommended Sources . 104.2.2 HVEDR Data Sampling and Write Rates 114.2.3 Recording of Available Data . 124.3 HVEDR Event Record Duration 124.3.1 Data Element Buffers 124.4 Data File Format . 134.4.1 HVEDR Data File Format Overview 134.4.2 Header Block . 164.4.3 Body Block 2
11、04.4.4 Footer Block 215. SYSTEM PERFORMANCE RECOMMENDATIONS 255.1 Electrical / Environmental Performance and Crash Survivability 255.1.1 Electrical Performance 255.1.2 Environmental Performance . 255.1.3 Crash Survivability 265.2 Power Capacity . 265.3 Data Volatility 275.4 Physical Interface betwee
12、n Vehicle and Data Extraction Tool . 275.4.1 Overview . 275.4.2 Physical Interface 296. DATA EXTRACTION 296.1 Data Extraction Use Cases . 306.2 Data Extraction Procedure 306.2.1 Data Extraction Messages Using J1939 . 326.2.2 Data Extraction Messages Using SAE J1708/1587 366.2.3 Primary Extraction Me
13、thod (On-vehicle Data Extraction) . 396.2.4 Secondary Extraction Method Capability (Off-vehicle Data Extraction) . 476.2.5 Alternative Extraction Methods . 476.2.6 Checksum Validator 487. NOTES 487.1 Marginal Indicia . 48FIGURE 1 HVEDR EVENT RECORD 12FIGURE 2 OVERVIEW OF THE HVEDR OUTPUT FILE CSV FO
14、RMAT, INDICATING BLOCK STRUCTURE 14FIGURE 3 HVEDR HEADER BLOCK IN CSV FORMAT STATIC VEHICLE, EVENT, AND EXTRACTION INFORMATION . 16FIGURE 4 HVEDR HEADER BLOCK TABULAR REPRESENTATION STATIC VEHICLE, EVENT, AND EXTRACTION INFORMATION . 18FIGURE 5 HVEDR BODY BLOCK IN CSV FORMAT DATA ELEMENT TIME HISTOR
15、Y . 20FIGURE 6 HVEDR BODY BLOCK TABULAR REPRESENTATION DATA ELEMENT TIME HISTORY . 21FIGURE 7 HVEDR FOOTER BLOCK IN CSV FORMAT DATA ELEMENT SOURCE, UNIT, AND RANGE INFORMATION . 22FIGURE 8 HVEDR FOOTER BLOCK TABULAR REPRESENTATION DATA ELEMENT SOURCE, UNIT, AND RANGE INFORMATION 23FIGURE 9 EXAMPLE O
16、F DATA EXTRACTION FROM HVEDR VIA VEHICLE DATABUS . 28FIGURE 10 EXAMPLE OF DIRECT DATA EXTRACTION FROM HVEDR 29FIGURE 11 DATA EXTRACTION PROCESS OVERVIEW . 31FIGURE 12 OBTAINING VIN VIA J1939 32FIGURE 13 OBTAINING COMPONENT IDS VIA SAE J1939 . 33FIGURE 14 OBTAINING HVEDR EVENT COUNT DATA VIA SAE J193
17、9 . 34FIGURE 15 OBTAINING HVEDR EVENT DATA VIA SAE J1939 . 35FIGURE 16 OBTAINING VIN VIA SAE J1587 . 36FIGURE 17 OBTAINING COMPONENT IDS VIA SAE J1587 . 36SAE J2728 Issued JUN2010 Page 3 of 48FIGURE 18 OBTAINING HVEDR EVENT COUNT DATA VIA SAE J1587 . 37FIGURE 19 OBTAINING HVEDR EVENT DATA VIA SAE J1
18、587 . 38FIGURE 20 EXTRACTION TOOL ACTION CODE MESSAGE FORMAT . 42FIGURE 21 HVEDR RESPONSE CODE MESSAGE FORMAT 43TABLE 1 LIST OF DATA ELEMENTS . 8TABLE 2 DATA ELEMENT REFERENCE . 10TABLE 3 DATA ELEMENT RECOMMENDED SOURCES . 11TABLE 4 HEADER BLOCK ORDER AND DETAILED DESCRIPTION . 19TABLE 5 FOOTER ORDE
19、R. HERE, SHOWING THE ELEMENT NAME AND THE STRING TO BE ENTERED IN THE FILE FOR EACH RANGE 24TABLE 6 EXTRACTION METHODS MATRIX . 30TABLE 7 ACTION AND RESPONSE CODES REFERENCE 41SAE J2728 Issued JUN2010 Page 4 of 481. SCOPE This Recommended Practice (RP) document applies to Heavy Vehicle Event Data Re
20、corders (HVEDR) for heavy-duty (HD) ground wheeled vehicles over 4545 kg (10 000 US pounds), commonly referred to as Class 3-8, which are intended to be compliant with current Federal Motor Vehicle Safety Standards (FMVSS) and/or Federal Motor Carrier Safety Regulations (FMCSR). In the context of th
21、e J2728 RP, the term heavy vehicle refers to motor vehicles equipped with one or both of the following vehicle communication networks: SAE J1708/J1587 or SAE J1939. This document is focused primarily on wheeled vehicles with standard on-board power supplies (e.g.,batteries). It is intended to addres
22、s the needs of OEM original, OEM modified/additive, and aftermarket systems. It does not specifically exclude trailers and similar non-engine powered vehicles, even though the current lack of standardized methodologies and processes for inter-vehicular communication and power supply interconnections
23、 remain unresolved. 1.1 Purpose This document provides design and performance recommendations needed to develop a “Tier 1” (i.e., minimum capabilities) HVEDR. It is not intended to prevent, constrain, or limit additional capabilities which could be combined or contained in any current or future Tier
24、 1 HVEDR as long as the minimum design and performance capabilities described herein are maintained. Subsequent documents are envisioned, which may significantly expand on recommended capabilities. These devices will be referred to as “Tier 2” and “Tier 3” devices. 2. REFERENCES 2.1 Applicable Publi
25、cations The following publications form a part of this specification to the extent specified herein. Unless otherwise indicated, the latest issue of SAE publications shall apply. 2.1.1 SAE Publications Available from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-
26、7323 (inside USA and Canada) or 724-776-4970 (outside USA), www.sae.org.SAE J670 Vehicle Dynamics Terminology SAE J1455 Recommended Environmental Practices for Electronic Equipment Design in Heavy-Duty Vehicle Applications SAE J1587 Electronic Data Interchange Between Microcomputer Systems in Heavy-
27、Duty Vehicle Applications SAE J1708 Serial Data Communications Between Microcomputer Systems in Heavy-Duty Vehicle Applications SAE J1939-13 Off-Board Diagnostic Connector SAE J1939-71 Vehicle Application Layer SAE J1939-73 Application Layer Diagnostics SAE J2728 Issued JUN2010 Page 5 of 482.1.2 Oth
28、er Applicable Publications The following publications form a part of this specification to the extent specified herein. Unless otherwise indicated, the latest version of these publications shall apply. IETF RFC 4180, Common Format and MIME Type for Comma-Separated Values (CSV) Files, Internet Engine
29、ering Task Force (IETF) Request for Comments (RFC) 4180, http:/tools.ietf.org/html/rfc4180, October, 2005, accessed December 2007. TMC RP1210 A/BWindows Communication API 2.2 Related Publications The following publications are provided for information purposes only and are not a required part of thi
30、s SAE Technical Report.SAE J1698-0 Vehicle Event Data Interface - Vehicular Output Data Definition SAE J1698-1 Vehicle Event Data Interface - Output Data Definition SAE J1698-2 Vehicle Event Data Interface - Vehicular Data Extraction 3. GLOSSARY OF TERMS 3.1 Event An event is a point in time, during
31、 the operation of a heavy vehicle, in which one or more threshold trigger criteria are met causing the HVEDR to log data surrounding the event. 3.2 Event Trigger An event trigger is a set of criteria which, if met, initiates the capture of an Event Record. 3.3 Event Record An event record is the com
32、plete set of data collected by an HVEDR for a given event, comprised of pre-trigger data and post-trigger data. 3.4 Electronic Control Unit (ECU) An electronic control unit (ECU) is an electronic subsystem that manages the functions of a vehicle system or components. ECUs are often called electronic
33、 control modules, or ECMs, or simply modules. 3.5 Vehicle Speed Sensor (VSS) The vehicle speed sensor (VSS) is a sensor that determines the approximate longitudinal velocity (see SAE J670e, Section 10.4) of a vehicle while in operation. 3.6 Heavy Vehicle Heavy Vehicle (also known as Heavy-Duty Vehic
34、le), for the purposes of this recommended practice, includes all motor vehicles equipped with one or both of the following vehicle communication networks: SAE J1708/J1587 or SAE J1939. 3.7 Heavy Vehicle Event Data Recorder (HVEDR) The Heavy Vehicle Event Data Recorder (HVEDR) is an electronic system
35、 that captures and records electronic information related to an event during vehicle operation. SAE J2728 Issued JUN2010 Page 6 of 483.8 Tier 1 HVEDR A Tier 1 HVEDR is an HVEDR which meets the requirements of SAE J2728 as defined herein. It provides the minimum-level functionality for an HVEDR. 3.9
36、Tier 2 HVEDR An envisioned Tier 2 HVEDR will be an HVEDR which meets all of the requirements of the Tier 1 Heavy Vehicle Event Data Recorder Recommended Practice, and offers the ability to incorporate additional non-proprietary or non-manufacturer-specific data available on the vehicles data network
37、(s) as defined by the SAE J1587 and SAE J1939 vehicle communication network protocols. 3.10 Tier 3 HVEDR An envisioned Tier 3 HVEDR will be an HVEDR which meets the requirements of the Tier 1 and Tier 2 HVEDR RPs and, in addition, will include additional relevant proprietary data, as technologies an
38、d practices further develop. 3.11 Data Port The data port is the physical connector through which the data extraction tool offloads HVEDR data. For heavy vehicles, the data port is the “Off-Board Diagnostic” (OBD) electrical connector as defined by SAE J1939-13. Note the HVEDR may use either the SAE
39、 J1708/J1587 or SAE J1939 data network for communication, both of which may be present on the OBD connector, for the transfer of HVEDR data. 3.12 Data Extraction Tool The data extraction tool comprises the hardware and software used to extract event data from the HVEDR. The main functions of the dat
40、a extraction tool are to: (1) establish a communication link with the HVEDR memory device (typically using the SAE J1939-13 OBD connector, or directly to a specific ECU), (2) extract event data from the HVEDR, and (3) convert the event data into the SAE J2728-specified format. 3.13 Data Format Conve
41、rsion Data format conversion is a process performed by the data extraction tool to convert native event data stored in an ECU into standardized SAE J2728-specified event data output. 3.14 MID / PID (Message Identification / Parameter Identification) Refer to SAE J1587 for additional detailed and spe
42、cific information. 3.15 PGN / SPN / SA (Parameter Group Number / Suspect Parameter Number / Source Address) Refer to SAE J1939 for additional detailed and specific information. SAE J2728 Issued JUN2010 Page 7 of 484. TECHNICAL REQUIREMENTS 4.1 Event Trigger The Event Trigger is a set of criteria whi
43、ch, if met, cause an HVEDR Event Record to be saved to non-volatile memory. The HVEDR must save an event record if any of the following sets of conditions occur: Acceleration Trigger - Vehicle Speed changes at a rate higher than the programmable threshold set between 8.0 km/h/s (5.0 mph/s) and 22.5
44、km/h/s (14.0 mph/s). The Vehicle Speed change can be either positive or negative, and persists beyond that threshold for at least 0.5 s. The acceleration event start will be the time that the threshold is crossed. The recommended default threshold setting is 11.3 km/h/s (7.0 mph/s). Last Stop Trigge
45、r - Vehicle Speed falls below 3.0 km/h (1.9 mph) for 15 s or more. The last stop event start will be the time the threshold is crossed. To prevent Last Stop events from being overwritten due to the movement of the vehicle after an incident of interest, the Last Stop Trigger cannot reoccur until the
46、vehicle speed reaches a speed of 24.0 km/h (14.9 mph) or more for a minimum of 6 s. The act of turning the ignition off will not directly trigger a last stop event. See also the discussion in 4.3.1 regarding the last stop event buffer. Safety Restraint System (SRS) Trigger - Any vehicle airbag or ot
47、her active passenger restraint system is deployed (if installed and reporting to the SAE J1587 and/or SAE J1939 vehicle communications networks). The SRS trigger event start will be the time the HVEDR receives the SRS message. NOTE: The recommended default 11.3 km/h/s (7.0 mph/s) Acceleration Trigge
48、r is specified for typical on-highway heavy truck applications. Recognizing that other vehicle configurations, applications, or vocations may require adjustment to the Event Trigger vehicle speed rate of change, the rate may be programmable within the range per the above specifications. The 0.5 s pe
49、rsistence requirement remains in effect over the allowable range of the programmable Event Trigger. The HVEDR must include appropriate filtering to avoid triggering extraneous events due to ABS cycling. NOTE: The VSS is not always an accurate representation of the velocity of the chassis relative to the ground. 4.2 Data Elements When an event trigger occurs, an HVEDR must record, at a minimum, and if available, all data e
