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 revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions. Copyright 2017 SAE International All rights reserved. No part of this p
3、ublication may 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-497
4、0 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/standards.sae.org/J1939/5_201710 SURFACE VEHICLE RECOMMENDED PRACTICE J1939-5 OCT2017 Issued 2008-02 Reaffirmed 2
5、012-04 Revised 2017-10 Superseding J1939-05 APR2012 Marine Stern Drive and Inboard Spark-Ignition Engine On-Board Diagnostics Implementation Guide RATIONALE Revised to provide updated references, to identify potential impact of SAE J1939-14, 500K data rate on communcation architectures, and to recog
6、nize recent changes in SAE J1939-73. TABLE OF CONTENTS 1. SCOPE . 2 1.1 Purpose 2 2. REFERENCES . 2 2.1 Applicable Documents . 2 2.1.1 SAE Publication . 2 2.1.2 ABYC Publication . 3 2.1.3 CARB Publication . 3 2.1.4 ISO Publication 3 3. DEFINITIONS 3 4. ABBREVIATIONS 3 5. TECHNICAL REQUIREMENTS . 3 5
7、.1 Physical Layer 3 5.1.1 Wire 4 5.1.2 Network Architecture 4 5.1.3 Termination 4 5.2 Marine Diagnostic Connector . 4 5.2.1 Data Link Connector Location 4 5.2.2 Connector Sealing and Cap . 4 5.2.3 Connector Labeling 4 5.2.4 Connect/Disconnect . 4 5.2.5 Physical Requirements 5 5.2.6 Current Handling
8、5 5.2.7 Mechanical Requirements 5 SAE INTERNATIONAL J1939-5 OCT2017 Page 2 of 12 5.3 Datalink Layer 5 5.3.1 Preferred Addresses 5 5.3.2 Request/Response System . 5 5.3.3 Transport Services . 6 5.4 Network Layer 6 5.4.1 Non SAE J1939 Communication . 6 5.5 Network Management 6 5.5.1 Source Addresses 6
9、 5.5.2 Engine Location . 6 5.6 Application Layer 6 5.6.1 Parametric Data Support 7 5.6.2 Diagnostic Service Support 7 5.7 Fault Code Storage and Erasure . 8 5.7.1 Pending Faults . 8 5.7.2 Active Faults . 8 5.7.3 Previously Active Faults . 8 5.8 Audio/Visual Alert Device . 9 5.8.1 Visual Alert Device
10、 . 9 5.8.2 Audio Alert Device 9 6. NOTES . 10 6.1 Revision Indicator . 10 1. SCOPE This document describes the application of the SAE J1939 recommended practices for compliance with on-board diagnostic malfunction detection system requirements for marine sterndrive and inboard spark ignition engines
11、, as mandated by the California Air Resources Board (CARB). These Otto-cycle engines are not derived from automotive diesel-cycle engines. 1.1 Purpose The purpose of this recommended practice is to provide a standard open interconnect architecture that allows a generic diagnostic tool to communicate
12、 with marine sterndrive and inboard spark ignition engines on board diagnostic system. These on-board diagnostic malfunction detection system requirements are referred to as OBD-M in this document. 2. REFERENCES 2.1 Applicable Documents The following publications form a part of this specification to
13、 the extent specified herein. Unless otherwise indicated, the latest issue of SAE publications shall apply. In general, all requirements of the SAE J1939 document apply to OBD-M applications, except as noted in this document. 2.1.1 SAE Publication Available from SAE International, 400 Commonwealth D
14、rive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Canada) or +1 724-776-4970 (outside USA), www.sae.org. SAE J1939 Serial Control and Communications Heavy Duty Vehicle Network - Top Level Document SAE J1939-14 Physical Layer, 500 Kbps SAE J1939-15 Physical Layer, 250 Kbps, Un-Shield
15、ed Twisted Pair (UTP) SAE J1939-21 Data Link Layer SAE J1939-31 Network Layer SAE INTERNATIONAL J1939-5 OCT2017 Page 3 of 12 SAE J1939-71 Vehicle Application Layer SAE J1939-73 Application Layer - Diagnostics SAE J1939-81 Network Management SAE J1939DA J1939 Digital Annex SAE/USCAR2-4 Performance Sp
16、ecification for Automotive Electrical Connector Systems 2.1.2 ABYC Publication Available from American Boat and Yacht Council, 613 Third Street, Suite 10, Annapolis, MD 21403, Tel: 410-990-4460, www.abycinc.org. ABYC E-11 2003-07 edition, AC and DC Electrical Systems on Boats 2.1.3 CARB Publication
17、Available from California Air Resources Board, 1001 “l” Street, P.O. Box 2815, Sacramento, CA 95812, Tel: 916-322-2990, www.arb.ca.gov. CALIFORNIA CODE OF REGULATIONS (CCR), effective December 13, 2006 TITLE 13. Motor Vehicles Chapter 9. Off-Road Vehicles and Engines Pollution Control Devices Articl
18、e 4.7. Spark-Ignition Marine Engines 2444.2. On-Board Engine Malfunction Detection System Requirements Model Year 2007 and Later Spark-Ignition Inboard and Sterndrive Marine Engines. 2.1.4 ISO Publication Copies of these documents are available online at http:/webstore.ansi.org/ ISO 2575 Seventh edi
19、tion 2004-05-01, Road Vehicles - Symbols for controls, indicators, and tell-tales 3. DEFINITIONS See Title 13 CCR 2441 and SAE J1939 for terms and definitions that are not defined in this document. In the event of conflicting definitions, those in Title 13 CCR 2441 shall take precedence. 4. ABBREVIA
20、TIONS ABYC American Boat and Yacht Council CARB California Air Resources Board DC Direct Current DLC Data Link Connector DM Diagnostic Message SPN Suspect Parameter Number See SAE J1939 for other abbreviations not defined in this document. 5. TECHNICAL REQUIREMENTS 5.1 Physical Layer The datalink ph
21、ysical layer shall be according to SAE J1939-15, except as noted. SAE J1939-14 shall not be used for connections to pins C and D in 5.2.5. SAE INTERNATIONAL J1939-5 OCT2017 Page 4 of 12 5.1.1 Wire Wire and insulation type, color, and size shall be compliant with ABYC recommended practices. Where dev
22、iations from SAE J1939-15 occur, implementation should be according to the engine manufacturers recommendation in order to ensure proper network functionality. 5.1.2 Network Architecture The network must work properly if the only nodes are the engine ECU and the diagnostic scan tool, connected via a
23、 5 m cable. If other integrated electronic control units perform OBD-M functions independent of the engine ECU, then it must be done according to the engine manufacturers recommendation in order to ensure compliance with Title 13 CCR 2444.2. If 500K communcations like those defined in SAE J1939-14 a
24、re used in the vessel, the communcations shall reside on separate network segments. 5.1.3 Termination Diagnostic tools intended to be connected to this network shall not include DC termination for the network segment backbone. 5.2 Marine Diagnostic Connector The connector supports the unshielded twi
25、sted pair physical layer of SAE J1939-15. It also includes battery + and - from the engine, intended to power a diagnostic tool, and two spare pins reserved for future specification. 5.2.1 Data Link Connector Location 5.2.1.1 Engine Manufacturer Responsibilities The OBD-M data link connector (DLC) s
26、hall be located on the engine in a spot that typically would be readily visible and accessible to a service technician after the engine has been installed in a boat. The DLC shall be constructed to withstand heat, vibration, and/or mechanical fatigue resulting from normal engine operation for a peri
27、od of at least 10 years. These requirements shall apply separately to each engine in a multiple engine configuration except for engines belonging to the same OBD-M network, in which case a single DLC would suffice for that network. 5.2.1.2 Vessel Manufacturer Responsibilities The DLC location may op
28、tionally be extended by the boat builder to reside within the passenger compartment of the vessel in a readily identifiable and accessible location. If the DLC location is hidden behind a removable panel or other obstruction, the panel or obstruction shall be clearly labeled to indicate the presence
29、 of the connector. If more than one DLC is present on a vessel, then each DLC shall be clearly labeled as to which engine it supports and/or shall be located relative to the other DLC(s) according to the corresponding relative locations of the engines using those DLCs. 5.2.2 Connector Sealing and Ca
30、p The connector shall be sealed to meet the environmental requirements in 5.6 of SAE/USCAR2-4 for temperature Class 2 (Figure 5.1.4) components. The connector shall be provided with a cap for sealing the front of the connector when not in use. The cap must have a method to retain it in order to prev
31、ent losing it when it is disconnected. 5.2.3 Connector Labeling The DLC shall be labeled “OBD-M” on or near the connector. 5.2.4 Connect/Disconnect The connector shall be rated for 200 connect/disconnect cycles. SAE INTERNATIONAL J1939-5 OCT2017 Page 5 of 12 5.2.5 Physical Requirements The pinout sh
32、all be: A - Vbatt + B - Vbatt gnd C - CAN-H D - CAN-L E - spare (reserved) F - spare (reserved) Unused pins shall be plugged. 5.2.6 Current Handling The Vbatt + and Vbatt gnd circuits shall be capable of carrying (source and sink, respectively) a minimum of 5 A current to the diagnostic tool. Tools
33、powered from this circuit shall not draw more than 5 A. 5.2.7 Mechanical Requirements The engine-side of the connector shall be a plug style housing with socket style pins. See Appendix A for mating connector detail of the receptical style connector to be used for an OBD-M inspection tool. 5.3 Datal
34、ink Layer The datalink layer shall conform to SAE J1939-21. 5.3.1 Preferred Addresses OBD-M engines and diagnostic tools shall use the preferred addresses defined for Industry Group 0 (Global) or Industry Group 4 (Marine Equipment). Note that more than one engine may be connected to the network at a
35、 time. 5.3.2 Request/Response System The diagnostic services described in SAE J1939-73 are implemented using the request response mechanism described in SAE J1939-21. 5.3.2.1 Request The request mechanism is described using PGN 59904. PGN 59904 supports both destination specific and global destinati
36、on requests. Using the global data request, all network nodes can be interrogated for selected diagnostic data in single request. The form of the request and the nature of the information to be provided determine which Transport Protocol facility is used when the data in the reply exceeds 8 bytes. 5
37、.3.2.2 Response The response to a request may either be the requested data, an acknowledgement, or not-acknowledgement. In one case, no response is provided for the request. 5.3.2.2.1 ACK/NACK PGN 59392 describes both a positive and negative acknowledgement facility. ACK and NACK responses indicate
38、the performance status of a request or command. Requests received for unsupported data are responded to with NACK. SAE J1939-73 discusses the use of ACK/NACK on many of its service requests. ACK/NACK requirements should be strictly adhered to ensure service tool compatibility. 5.3.2.2.2 Data Request
39、s for data shall be responded to as described in SAE J1939-21, 5.4. SAE INTERNATIONAL J1939-5 OCT2017 Page 6 of 12 5.3.2.2.3 No Response No response is commonly provided for global requests, where the PGN supported is not available from receiving ECU. This is described in SAE J1939-21, 5.4. Exceptio
40、ns to this policy is noted in Diagnostic Message (DM) descriptions in SAE J1939-73. 5.3.3 Transport Services Transport services are described in SAE J1939-21 for data that exceeds eight bytes in length. Two forms of transport services are provided. Managed connections support flow control between th
41、e sender and receiver. Broadcast Announce Messages are sent without flow control. Many of the replies, satisfying requests for diagnostic information, require ECUs to support the transport protocol mechanisms in SAE J1939-21, because they are longer than one data packet. Because diagnostic requests
42、may be requested using either global or destination specific methods described in SAE J1939-21, the ability to provide both forms of reply will be required. Refer to the Connection Management topic in SAE J1939-21 for full details. 5.4 Network Layer The Network Layer shall be according to SAE J1939-
43、31. 5.4.1 Non SAE J1939 Communication Non-J1939 protocols may exist on the network (e.g., proprietary 11-bit CAN, etc.), as long as they do not interfere with the OBD-M communication defined in this document, and are limited to 250K bps. 5.5 Network Management Network management shall be according t
44、o SAE J1939-81. 5.5.1 Source Addresses In applications with multiple engines communicating on the same network, the Source Addresses shall be as defined in SAE J1939 Tables B2 and B6. 5.5.2 Engine Location OBD-M compliant devices shall support broadcasting a description in PGN 64965, SPN 2903 (ECU L
45、ocation) of the relative location in the boat of the engine for which they are broadcasting fault codes. The description shall be a maximum of 16 characters long, intended to be displayed by the OBD-M scan tool (e.g., “PORT”, “STARBOARD”, etc.). OBD-M scan tools should request this SPN globally and
46、use it to help the technician relate the diagnostic data displayed with the appropriate engine in multiple engine applications. It is the vessel manufacturers responsibility to configure the engine location according to the engine manufacturers recommendations. 5.6 Application Layer There are two do
47、cuments that define application layer requirements for OBD-M. SAE J1939-71 and SAE J1939DA define parametric data such as engine speed and some component operating limits like high idle. Scaling (range/resolution) and data length for parameters communicated on the SAE J1939 network are defined in SA
48、E J1939-71. SAE J1939-73 defines the diagnostics services and data content for diagnostics messages on an SAE J1939 Network. SAE INTERNATIONAL J1939-5 OCT2017 Page 7 of 12 5.6.1 Parametric Data Support At a minimum, the following SPNs shall be broadcast or available on request according to SAE J1939
49、-71, if applicable: Table 1 - SPNS required for broadcast if available Parameter SPN Engine throttle position 51 Accelerator pedal position 1 91 Fuel level 96 Engine oil pressure 100 Engine intake manifold 1 temperature 105 Engine intake manifold #1 pressure (turbocharged applications only) 102 Engine air inlet pressure (normally aspirated applications) 106 Barometric pressure 108 Engine coolant temperature 110 Keys
