sea J1939-81

5星 · 超过95%的资源需积分: 9 26 浏览量更新于2023-07-01 收藏 208KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

SURFACE J1939-81

VEHICLE

RECOMMENDED

PRACTICE

NETWORK MANAGEMENT

Issued 1997-07

Revised 2003-05

Superseding J1939-81 JUL1997

Forward

This series of SAE Recommended Practices has been developed by the Truck and Bus Control and

Communications Network Subcommittee of the Truck and Bus Electrical and Electronics Committee. The

objectives of the subcommittee are to develop information reports, recommended practices, and standards

concerned with the requirements, design, and usage of ECUs that transmit electronic signals and control

information among vehicle components. The usage of these recommended practices is not limited to truck

and bus applications. Other applications may be accommodated with immediate support being provided for

construction and agricultural equipment, and stationary power systems.

These documents are intended as a guide toward standard practice and are subject to change to keep pace

with experience and technical advances.

Network management in the SAE J1939 network 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 initialization processes, requirements for reaction to brief power outages and minimum

requirements for ECUs on the network.

TABLE OF CONTENTS

1. Scope .......................................................................................................................................4

2. References...............................................................................................................................4

2.1 Applicable Publications............................................................................................................4

2.1.1 SAE Publications .........................................................................................................4

3 Definitions ...............................................................................................................................4

3.1 Terminology used in network management ...........................................................................4

3.2 Controller Application (CA).....................................................................................................4

3.3 Address Configuration and Capability.....................................................................................4

3.3.1 Single Address Capable CA ..............................................................................................5

3.3.1.1 Non-Configurable Address CA ............................................................................................5

3.3.1.2 Service Configurable Address CA .......................................................................................5

3.3.1.3 Command Configurable Address CA ...................................................................................5

3.3.1.4 Self-Configurable Address CA ............................................................................................5

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 therefrom, 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.

recording, or otherwise, without the prior written permission of SAE.

TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada)

Tel: 724-776-4970 (outside USA)

Fax: 724-776-0790

Email: custsvc@sae.org

SAE WEB ADDRESS: http://www.sae.org

- 2 -

3.3.2 Arbitrary Address Capable CA ..........................................................................................6

3.4 Types of CAs......................................................................................................................6

3.4.1 Standard CAs...............................................................................................................6

3.4.2 Diagnostic/Development Tool CAs..............................................................................6

3.4.3 Network Interconnection CAs......................................................................................6

4. Technical Requirements ..........................................................................................................7

4.1 NAME and Address Requirements.........................................................................................7

4.1.1 NAME.................................................................................................................................8

4.1.1.1 NAME Fields ....................................................................................................................9

4.1.1.2 Arbitrary Address Capable Field ....................................................................................... 10

4.1.1.3 Industry Group Field........................................................................................................ 10

4.1.1.4 Vehicle System Instance Field......................................................................................... 10

4.1.1.5 Vehicle System Field ...................................................................................................... 10

4.1.1.6 Reserved Field................................................................................................................ 10

4.1.1.7 Function Field................................................................................................................. 10

4.1.1.8 Function Instance Field ................................................................................................... 10

4.1.1.9 ECU Instance Field ......................................................................................................... 11

4.1.1.10 Manufacturer Code Field ................................................................................................ 11

4.1.1.11 Identity Number Field..................................................................................................... 11

4.1.1.12 Dependencies in the NAME Fields .................................................................................. 11

4.1.2 Addresses ........................................................................................................................12

4.1.2.1 The 254 Address............................................................................................................. 12

4.1.2.2 The 255 Address............................................................................................................. 12

4.2 Network Management Procedure .........................................................................................13

4.2.1 Request Message (PGN 59904) for Address Claimed (PGN 60928) ............................13

4.2.2 Address Claimed / Cannot Claim (PGN 60928)..............................................................14

4.2.2.1 Address Claimed Message .............................................................................................. 15

4.2.2.2 NAME of Controller Application ........................................................................................ 15

4.2.2.3 Cannot Claim Address..................................................................................................... 15

4.2.3 Commanded Address (PGN 65240)................................................................................16

4.2.3.1 Commanded Address Message........................................................................................ 16

4.2.3.2 NAME of Commanded Address Target.............................................................................. 17

4.2.3.3 Address Assignment (new source address)....................................................................... 17

4.2.4 Working Sets....................................................................................................................17

4.2.4.1 Application Notes ............................................................................................................ 18

4.2.4.1.1 Message sequence ................................................................................................ 18

4.2.4.1.2 Working Set Member Message Spacing ................................................................... 18

4.2.4.1.3 Compatibility with Conventional Network Processes .................................................. 18

4.2.4.1.4 Constraints on Working Set Membership .................................................................. 19

4.2.4.1.5 Configuration Changes ............................................................................................ 19

4.2.4.1.6 Source Address Changes........................................................................................ 19

4.2.4.1.7 Missing Working Set Members ................................................................................ 19

4.2.4.2 Working Set Master Message – WSMSTR (PGN 65037) .................................................... 20

4.2.4.3 Number of Members ........................................................................................................ 20

4.2.4.4 Working Set Member Message – WSMEM (PGN 65036) .................................................... 20

4.2.4.5 NAME of Working Set Member......................................................................................... 21

4.3 Network Error Management..................................................................................................21

4.3.1 Cannot Claim Address.....................................................................................................21

4.4 Address Claim and CA Initialization procedure.....................................................................21

SAE J1939-81 May 2003

- 3 -

4.4.1 Address Claim Prioritization.............................................................................................22

4.4.2 Address Claim Requirements ..........................................................................................22

4.4.2.1 Requirements for Requests for Address Claimed ............................................................... 22

4.4.3 Address Claim Initialization Rules....................................................................................22

4.4.3.1 Response to a Request for Address Claimed sent to the global address .............................. 22

4.4.3.2 Response to a Request for Address Claimed sent to a specific address .............................. 22

4.4.3.3 Response to Address Claims of Own Address................................................................... 23

4.4.3.4 Contention for an Address................................................................................................ 23

4.4.4 Message Sequences for Initialization ..............................................................................23

4.4.4.1 Message sequences for initialization for all CAs on the network .......................................... 23

4.4.4.2 Potential Identical Identifiers in Network Management Messages ........................................ 23

4.4.4.3 Address Claim Bus Collision Management ........................................................................ 24

4.4.4.4 A CA which is Unable to Successfully Obtain an Address. ................................................. 24

4.4.5 Requests for Address Claimed for Self-Configurable Addressing CAs..........................24

4.4.5.1 Technical Note Regarding Multiple Self-Configurable Addressing CAs.................................. 25

4.4.5.2 CAs Not Permanently Connected to the Network. .............................................................. 25

4.4.6 Construction of Address to NAME Association Tables...................................................25

4.5 Minimum Network Management Functionality ......................................................................25

4.5.1 Reaction to Power Supply and Other Related ECU Disturbances .................................25

4.5.2 Minimum Network Management Capability......................................................................26

4.5.2.1 Request for Address Claimed Message............................................................................. 26

4.5.2.2 Address Claimed Message before Using a Source Address ................................................ 26

4.5.2.3 Disruption of the Network During Connection or Disconnection of an ECU ............................ 26

4.5.2.4 Continuity of Addresses Across Power-down and Power-up Cycles ..................................... 26

Appendix A: Initialization Sequence Timing Diagrams...........................................................27

FIGURE A1 - Initialization of A CA with Address Claim and No Contention...................................... 27

FIGURE A2 - Initialization of an ECU Where Two Single Address CAs Attempt To Claim the Same

Address But Not Simultaneously ................................................................................................. 27

FIGURE A3 - Initialization of a CA Where NAME A Is Less Than NAME B and CA B is Arbitrary

Address Capable........................................................................................................................ 28

FIGURE A4 - Initialization of a CA with Two CAs Attempting to Claim the Same Address

Simultaneously .......................................................................................................................... 28

Single Address CAs with addresses in the 0-127 and 248-253 ranges may omit the 250 ms delay. .. 29

FIGURE A5 - Initialization of an Arbitrary Address Capable CA with No Contention.......................... 29

FIGURE A6 - Initialization of an Arbitrary Address Capable CA with a Request for Address Claimed

Sent to the Global Address ......................................................................................................... 29

FIGURE A7 - Initialization of a Single Address CA with a Request for Address Claimed Where Address

Is In Use................................................................................................................................... 30

FIGURE A8 - Response to a Request for Address Claimed by a CA which has Been Earlier

Unsuccessful In Claiming an Address.......................................................................................... 30

FIGURE A9 - Commanding an Address of a CA which does not have an Address and Supports the

Commanded Address Message................................................................................................... 31

FIGURE A10 - Commanding an Address of a CA which does not have an Address and the

Commanded CA Does Not Support A Commanded Address Message ............................................ 31

Appendix B Summary of Requirements and Capabilities of CAs.........................................32

Appendix C NAME Examples.....................................................................................................33

C.1 NAME Examples .............................................................................................................33

C.1.1 A Single ECU with a CA Serving an Engine on an On-Highway Heavy-Duty Truck.33

C.1.2 Brakes on the second trailer of heavy-duty truck.........................................................33

SAE J1939-81 May 2003

- 4 -

C.1.3 Agricultural planters with separate Section Controls....................................................34

Appendix D: State Transition Diagrams for Address Claiming Processes..........................35

FIGURE D1 - State Transition Diagram for Initialization of Arbitrary Address Capable CAs ............... 36

FIGURE D2 - State Transition Diagram for Initialization of Single Address CAs ............................... 37

FIGURE D3 - State Transition Diagram for Response of a CA to the Commanded Address Message 38

1. Scope

These SAE Recommended Practices are intended for light and heavy duty vehicles used on or off road as

well as appropriate stationary applications which use vehicle derived components (e. g. generator sets).

Vehicles of interest include, but are not limited to on and off highway trucks and their trailers; construction

equipment; and agricultural equipment and implements.

The purpose of these documents is to provide an open interconnect system for electronic systems. It is the

intention of these documents to allow Electronic Control Units to communicate with each other by providing

a standard architecture.

Network management in the SAE J1939 network 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 initialization 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 Publications

Available from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.

2.1.1 SAE Publications

SAE J1939 - Recommended Practice for Serial Control and Communications Vehicle Network

SAE J1939-21 - Data Link Layer

SAE J1939-31 - Recommended Practice for Serial Control and Communications Vehicle Network - Part 31-

Network Layer

3 Definitions

See SAE J1939 top level document for definition of terms not defined in this document.

3.1 Terminology used in network management

Terms are defined in SAE J1939 for use in the context of this document.

3.2 Controller Application (CA)

For 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 and hence

may contain one or more CAs. Each CA will have one address and an associated NAME in order to

communicate on the J1939 network.

3.3 Address Configuration and Capability

SAE J1939-81 May 2003

- 5 -

Address configuration is the method by which a particular CA determines the source address it will 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 distinguished by the value in the Arbitrary Address

Capable field at the high-order position in the CA’s NAME. The terms and definitions follow:

3.3.1 Single Address Capable CA

Within the Single Address Capable group, there are several different methods by which the CA can have its

address changed. All but one involve an external agent. These CAs have no means to alter the address

they claim and use without intervention through some external process. These CAs include non-configurable

address, service configurable address, command configurable address and self-configurable address CAs.

The value in the Arbitrary Address Capable field is zero in the NAME of these CAs. Four classifications of

CAs are defined below to allow different methods of changing the targeted source address.

These classifications are not necessarily mutually exclusive. For example, an ECU that is a Self-

Configurable Address CA could simultaneously be a Service Configurable Address CA and a Command

Configurable Address CA. A designer may allow this just in case the CA is unable to claim any of the

addresses within its limited set.

3.3.1.1 Non-Configurable Address CA

A Non-Configurable Address CA is one which has a source address provided by its manufacturer. This

address is not alterable by any means in the field, including service procedures. (Note that a “Service

Procedure” that replaces the software that is executing in the ECU and thereby defining the CA may still

change the address used by the CA.)

3.3.1.2 Service Configurable Address CA

A Service Configurable Address CA is one whose source address may be changed in the field by a service

technician. The address may be altered by any one of a number of proprietary techniques or by using the

Commanded Address message, while in a "service" mode of operation. It is very likely that a service tool

would be involved.

3.3.1.3 Command Configurable Address CA

A Command Configurable Address CA is one whose source address can be altered using the Commanded

Address message. The change can take place as the ECUs on the vehicle power up, without the

intervention of a service tool or the requirement of a special service mode of operation. It does require the

presence on the vehicle of a CA that can send the appropriate command to cause the address change, and

code in the Command Configurable Address CA to recognize and authenticate that command.

3.3.1.4 Self-Configurable Address CA

This is a special case where the CA is capable of determining which one of a limited set of Source

Addresses it will use based on information it obtains from the vehicle’s configuration. A prime example of

this is a Trailer Bridge that determines that it is Trailer No. 2 in a vehicle. While it can change the Source

Address (SA) it will use based on this internal determination, it can use only that address while it is in that

particular position on the vehicle. If that trailer were moved to Trailer No. 1 position, the CA would use the

address specified for Trailer No. 1. Note that there is just one address that is appropriate for use at each

position: the CA first learns its position, then creates the new NAME using that position information, then

chooses the appropriate address. A device that uses information from a connector plug to determine

whether it is on the left or right side of the vehicle would also be in this class. Note that these CAs are

capable of changing their addresses solely on the basis of a change in NAME.

SAE J1939-81 May 2003

剩余38页未读，继续阅读

不空的杯子

粉丝: 0
资源: 13

会员权益专享

sae j1939 几个主要文件（中文pdf版）

J1939参数表(SPN/PGN/SOURCE ID)

SAE-2020-J3101-硬件安全标准.pdf

再来几条关于ROMS模式模拟沉积物过程的参考文献

写成英文引用形式：周军,陈守谦,甄政等.基于波前编码的大焦深弹载双色红外探测系统[J].红外与激光工程,2020,49(04):83-87.

海水声速经验公式matlab

不同形态的氮对植物生长和氮吸收、草地群落结构等有显著影响的参考文献

海鸥优化算法用java怎么实现

js双层for循环遍历数组

写出樽海鞘群算法-随机森林算法回归伪代码

js中的双层for循环

写一个冒泡排序

上面的matlab代码补充完整，增加位置、墙体、植物蒸腾、土壤温度等参数

先循环读取1993年到2020年每个月海表面高度数据adt,再用matlab画出1993年到2020年12个月27年同一个月的平均气候态的海表面高度,要求画成二维等值线图并且能够1到12月能循环出图的代码

用arduino uno开发板，30个ws2812b灯珠，微动按键。编程实现按键触发流星效果，每按一次按键，触发一次，支持同时触发多个流星。

jonswap仿真 代码

用arduino uno开发板，30个ws2812b灯珠，微动按键。编程实现按键触发流星流动效果，每按一次按键，流动一次，支持多个同时流动。

会员权益专享

最新资源

jonswap仿真代码