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 ther
2、efrom, 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 2016 SAE International All rights reserved. No part of this
3、publication 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-49
4、70 (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/81_201703 SURFACE VEHICLE RECOMMENDED PRACTICE J1939-81 MAR2017 Issued 1997-07 Revised 2
5、017-03 Superseding J1939-81 FEB2016 Network Management RATIONALE Repaired broken cross reference links. FOREWORD The SAE J1939 communications network is defined using a collection of individual SAE J1939 documents based upon the layers of the Open System Interconnect (OSI) model for computer communi
6、cations architecture. The SAE J1939-81 document defines the address arbitration process and messages required by all ECUs to acquire and maintain a network address on an SAE J1939 communication network. The SAE J1939 communications network is a high speed ISO 11898-1 CAN based communications network
7、 that supports real-time closed loop control functions, simple information exchanges, and diagnostic data exchanges between Electronic Control Units (ECUs) physically distributed throughout the vehicle. The SAE J1939 communications network is developed for use in heavy-duty environments and suitable
8、 for horizontally integrated vehicle industries. The SAE J1939 communications network is applicable for light-duty, medium-duty, and heavy-duty vehicles used on-road or off-road and for appropriate stationary applications which use vehicle derived components (e.g., generator sets). Vehicles of inter
9、est include, but are not limited to, on-highway and off-highway trucks and their trailers, construction equipment, and agricultural equipment and implements. The physical layer aspects of SAE J1939 reflect its design goal for use in heavy-duty environments. Horizontally integrated vehicles involve t
10、he integration of different combinations of loose package components, like as engine and transmissions that are sourced from many different component suppliers. The SAE J1939 common communication architecture strives to offer an open interconnect system that allows the ECUs associated with different
11、 component manufacturers to communicate with each other. SAE INTERNATIONAL J1939-81 MAR2017 Page 2 of 60 TABLE OF CONTENTS 1. SCOPE 4 2. REFERENCES 4 2.1 Applicable Documents 4 2.1.1 SAE Publications . 4 3. DEFINITIONS . 4 3.1 Terminology Used in Network Management . 4 3.1.1 Additional Terms and Def
12、initions 4 4. TECHNICAL REQUIREMENTS 5 4.1 General 5 4.2 NAME and Address Requirements . 6 4.2.1 NAME (SPN 2848) 6 4.2.2 Addresses . 14 4.3 Address Configuration and Capability . 15 4.3.1 Arbitrary Address Capable CA 15 4.3.2 Single Address Capable CA . 15 4.4 Types of CAs . 16 4.4.1 Standard CAs 16
13、 4.4.2 Diagnostic/Development Tool CAs . 17 4.4.3 Network Interconnection CAs . 17 4.5 Network Management Procedures - Required . 18 4.5.1 Address Claim Prioritization 18 4.5.2 Address Claim Requirements . 18 4.5.3 Address Claim Initialization Rules . 19 4.5.4 Message Sequences for Initialization .
14、20 4.5.5 Requests for Address Claimed for Self-Configurable Addressing CAs 21 4.5.6 Construction of Address to NAME Association Tables . 21 4.5.7 Request Message (PGN 59904) for Address Claimed (PGN 60928) . 22 4.5.8 Address Claimed/Cannot Claim (PGN 60928) . 22 4.6 Network Management Procedures - O
15、ptional . 24 4.6.1 Commanded Address (PGN 65240) . 24 4.6.2 NAME Management 26 4.6.3 Working Sets . 40 4.7 Network Error Management 44 4.7.1 Cannot Claim Address 44 4.7.2 Address Violation 44 4.8 Minimum Network Management Functionality 44 4.8.1 Reaction to Power Supply and Other Related ECU Disturb
16、ances . 44 4.8.2 Minimum Network Management Capability 45 5. NOTES 46 5.1 Revision Indicator 46 SAE INTERNATIONAL J1939-81 MAR2017 Page 3 of 60 APPENDIX A INITIALIZATION SEQUENCE TIMING DIAGRAMS 47 APPENDIX B SUMMARY OF REQUIREMENTS AND CAPABILITIES OF CAS . 54 APPENDIX C NAME EXAMPLES . 55 APPENDIX
17、 D STATE TRANSITION DIAGRAMS FOR ADDRESS CLAIMING PROCESSES 57 FIGURE 1 FIELDS OF NAME 7 FIGURE 2 EXAMPLE OF NAME MAPPING TO DATA BYTES 8 FIGURE 3 DEPENDENCIES IN THE NAME FIELDS 13 TABLE 1 NAME FIELDS INFORMATION 7 TABLE 2 NETWORK MANAGEMENT MESSAGES 22 TABLE 3 NM MESSAGE FIELDS 27 TABLE 4 PARAMETE
18、R USE BY MODE 28 TABLE 5 SUMMARY OF REQUIREMENTS AND CAPABILITIES OF CAS . 54 SAE INTERNATIONAL J1939-81 MAR2017 Page 4 of 60 1. SCOPE SAE J1939-81 Network Management defines the processes and messages associated with managing the source addresses of applications communicating on an SAE J1939 networ
19、k. Network management is concerned with the management of source addresses and the association of those addresses with an actual function and with the detection and reporting of network related errors. Due to the nature of management of source addresses, network management also specifies initializat
20、ion processes, requirements for reaction to brief power outages and minimum requirements for ECUs on the network. 2. REFERENCES General information regarding this series of recommended practices is found in SAE J1939. 2.1 Applicable Documents The following publications form a part of this specificat
21、ion 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-7323 (inside USA and Canada) or +1 724-776-4970 (outside USA), ww
22、w.sae.org. SAE J1939 Serial Control and Communications Heavy Duty Vehicle Network - Top Level Document SAE J1939/21 Data Link Layer SAE J1939/31 Network Layer SAE J1939/71 Vehicle Application Layer SAE J1939/73 Application Layer - Diagnostics SAE J1939DA Digital Annex of Serial Control And Communica
23、tion Heavy Duty Vehcile Network Data 3. DEFINITIONS See SAE J1939 document for definition of terms not defined in this document. 3.1 Terminology Used in Network Management 3.1.1 Additional Terms and Definitions 3.1.1.1 Address Configuration and Capability Address configuration is the method by which
24、 a particular Controller Application (CA) determines the source address it shall use for Address Claim. For the purposes of the Address Claim process, there are two capabilities: Single Address Capable and Arbitrary Address Capable. These are described in detail in 4.3. For the purposes of network m
25、anagement, there are three types of CAs: Standard, Diagnostic/Development Tools, and Network Interconnection CAs. Each of these types has a specific role in a SAE J1939 network, and therefore has different rules and responsibilities. These are detailed in 4.4. 3.1.1.2 Controller Application (CA) For
26、 the purposes of this document, a controller is made up of the software and the hardware within an Electronic Control Unit (ECU) that performs a particular control function. The software within a particular controller is the “Controller Application” (CA). An ECU may serve as one or more controllers
27、and hence may contain one or more CAs. Each CA shall have one address and an associated NAME in order to communicate on the SAE J1939 network. SAE INTERNATIONAL J1939-81 MAR2017 Page 5 of 60 3.1.1.3 Current NAME The NAME of a CA that is transmitted in its address claim message. This term is used in
28、association with the NAME Management capability to distinguish the NAME a CA is presently using from the new or Pending NAME about to be adopted. See Pending NAME. 3.1.1.4 NAME An 8 byte value which shall uniquely identify the primary function of a CA and its instance in a given vehicle network. 3.1
29、.1.5 Pending NAME The NAME that a particular CA has temporarily stored as a result of NAME Management messages received from a qualified source. This NAME can be requested and provided as part of the NAME management process. It does not become the current NAME of the CA until the CA receives a prope
30、rly formatted and qualified “adopt” message such as discussed in 4.6.2.2.10.8. 3.1.1.6 Task Controller Electronic control unit on the mobile implement control system that is responsible for the sending, receiving and logging of process data. Reference ISO 11783 part 10. 3.1.1.7 Virtual Terminal Virt
31、ual Terminal (VT) electronic control unit consisting of a graphical display and input controls providing the capability to display information to and retrieve data from an operator for a connected implement or working set. 3.1.1.8 Working Set Group of NAMEs in one or more ECUs that collectively prov
32、ide a control function or group of control functions. The source address of the working-set master is used to identify the working set and, for others, to communicate with the working set. The working-set master is identified by a specific control function within a specific electronic control unit.
33、3.1.1.9 Working Set Master The one and only member of a working set that is the coordinator of the communications of a working set. 3.1.1.10 Working Set Member One of a number of CAs that collectively form the working set in addition to the working set master. 4. TECHNICAL REQUIREMENTS 4.1 General T
34、he Network Management layer in an SAE J1939 network provides the definitions and procedures necessary to uniquely identify CAs on the network, manage the assignment of addresses, and manage network errors. x Each CA shall be capable of providing its unique 64-bit NAME. The rules for creating this NA
35、ME, associating it with an address and the ability or non-ability to change that address are presented in 4.2. x CAs shall successfully claim an address according to the procedures explained in 4.5 prior to sending any other messages on the network. Multiple ECUs and/or CAs can work together as work
36、ing sets to perform functions but shall follow the rules in 4.6.3. SAE INTERNATIONAL J1939-81 MAR2017 Page 6 of 60 x The inability to successfully claim an address according to the procedure shall be handled and reported to the network in a standard way expressed in 4.7. x A minimum set of network m
37、anagement requirements, including required responses to power interruptions are listed in 4.8. 4.2 NAME and Address Requirements Every CA that transmits messages on a SAE J1939 network shall have a NAME and successfully acquire an address before the CA may transmit normal network traffic. The NAME s
38、erves two purposes, first, to provide a functional description of the CA (e.g., Engine Number 1, Engine Number 2, Transmission Number 1, Anti-Lock Brake System 1) and second, to provide a numerical value that may be used in address arbitration. An address is used within SAE J1939 networks to provide
39、 uniqueness to message identifiers and to allow the source of a message to be determined. (Addresses are sometimes referred to as “Source Addresses” indicating the latter use). Address claim messages, which contain both a source address and a NAME, are used to associate a NAME with a particular addr
40、ess on the network. The association of an address with a unique NAME (4.2.1) also provides means to associate an address with a CA. Manufacturers of ECUs and integrators of networks shall assure that the NAMEs of all CAs intended to transmit on a particular network are unique. 4.2.1 NAME (SPN 2848)
41、NAME is a 64 bit identifier for a CA and is composed of 10 fields. The values for five of these fields are derived from assignment lists managed by SAE J1939. They are: x Industry Group x Vehicle System x Reserve x Function x Manufacturer Code The remaining five values are either derived from charac
42、teristics of the network and vehicle architecture or under direct control of the manufacturer. They are: x Arbitrary Address Capable x Vehicle System Instance x Function Instance x ECU Instance x Identity Number The NAME associated with a CA provides the primary identification of the CA and the func
43、tion that the CA has on the network. Source addresses in the SAE J1939 network serve as a convenient 8-bit shortcut or alias to identify a particular CA. Address management procedures in the network management protocol allow the association of individual source addresses with the NAME of the CA, and
44、 the annunciation of that association onto the network. Appendix C provides examples of the construction of NAMEs for SAE J1939 ECUs. SAE INTERNATIONAL J1939-81 MAR2017 Page 7 of 60 4.2.1.1 Using NAME Each CA on a network shall have one NAME so the CA may be uniquely identified by its primary functi
45、on. A CAs NAME is also used in arbitration when multiple CAs attempt to claim the same address, reinforcing the need for unique identification. In turn, each CA on the network shall have a single address which is unique; so that it can properly arbitrate CAN Data Frames with other ECUs. NAME is an 8
46、 byte numerical value composed of 10 fields. The numeric value of NAME is used for comparing NAMEs to determine higher priority for claim to the same address (see 4.5.1). The NAME fields are prioritized from left to right as shown in Figure 1. When the NAME is placed into the data field of a CAN mes
47、sage, the 8 bytes are arranged in least significant byte first ordering in accordance with the SAE J1939-71 rules for data byte order for multiple byte numerical values. The byte ordering of the NAME fields in a CAN message is shown in Table 1. The definitions for each of the 10 fields are provided
48、in 4.2.1.4.1 through 4.2.1.4.10 . Figure 1 - Fields of NAME Table 1 - NAME fields information Start Position Length Parameter Name SPN Ability to be set to “Not Available” Reference 1-3.1 21 bits Identity Number 2837 NO 4.2.1.4.10 3.6-4 11 bits Manufacturer Code 2838 NO 4.2.1.4.9 5.1 3 bits ECU Inst
49、ance 2840 NO 4.2.1.4.8 5.4 5 bits Function Instance 2839 NO 4.2.1.4.7 6 8 bits Function 2841 YES 4.2.1.4.6 7.1 1 bit Reserved N/A N/A N/A7.2 7 bits Vehicle System 2842 YES 4.2.1.4.4 8.1 4 bits Vehicle System Instance 2843 NO 4.2.1.4.3 8.5 3 bits Industry Group 2846 NO 4.2.1.4.2 8.8 1 bit Arbitrary Address Capable 2844 NO 4.2.1.4.1 Listings of numerical values for Industry Groups, Vehicle Systems, Functions, and Manuf
