Refine Your Search

Topic

Search Results

Standard

Agricultural and Forestry Off-Road Machinery Control and Communication Network

2013-03-11
HISTORICAL
J1939/2_201303
SAE J1939-02 Agricultural and Forestry Off-Road Machinery Network specifies the requirements for application of SAE J1939 in agricultural and forestry equipment. This document specifies the series of documents within the set of SAE J1939 documents that are applicable to agricultural and forestry equipment and provides further requirements for this industry. The SAE and ISO groups have cooperated to define agricultural and forestry networks in a manner to allow compatibility of ECUs and messaging protocols between the A&F and the T&B networks.
Standard

Agricultural and Forestry Off-Road Machinery Control and Communication Network

2019-01-14
CURRENT
J1939/2_201901
SAE J1939-2 specifies the requirements for application of SAE J1939 in agricultural and forestry equipment. This document specifies the series of documents within the set of SAE J1939 documents that are applicable to agricultural and forestry equipment and provides further requirements for this industry. The SAE and ISO groups have cooperated to define agricultural and forestry networks in a manner to allow compatibility of ECUs and messaging protocols between the A&F and the T&B networks.
Standard

Application Layer - Diagnostics

2022-08-05
CURRENT
J1939/73_202208
SAE J1939-73 defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc. California-, EPA-, or EU-regulated OBD requirements are satisfied with a subset of the specified connector and the defined messages.
Standard

Application Layer - Diagnostics

2017-05-12
HISTORICAL
J1939/73_201705
SAE J1939-73 Diagnostics Application Layer defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc.
Standard

Application Layer - Diagnostics

2016-01-22
HISTORICAL
J1939/73_201601
SAE J1939-73 Diagnostics Application Layer defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc.
Standard

Application Layer - Diagnostics

2019-01-31
HISTORICAL
J1939/73_201901
SAE J1939-73 Diagnostics Application Layer defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc.
Standard

Application Layer - Diagnostics

2020-06-09
HISTORICAL
J1939/73_202006
SAE J1939-73 defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc. California-, EPA-, or EU-regulated OBD requirements are satisfied with a subset of the specified connector and the defined messages.
Standard

Application Layer - Diagnostics

2015-08-28
HISTORICAL
J1939/73_201508
SAE J1939-73 Diagnostics Application Layer defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc.
Standard

Application Layer - Diagnostics

2013-07-24
HISTORICAL
J1939/73_201307
SAE J1939-73 Diagnostics Application Layer defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc.
Standard

Application Layer - Generator Sets and Industrial

2021-07-15
CURRENT
J1939/75_202107
SAE J1939-75 defines the set of data parameters (SPs) and messages (PGs) for information predominantly associated with monitoring and control generators and driven equipment in electric power generation and industrial applications. The data parameters (SPs) and messages (PGs) previously published within this document are published in SAE J1939DA. Applications using the SAE J1939-75 document must refer to SAE J1939DA for the SAE J1939 parameters and messages for monitoring and controlling the power units, e.g., engines and turbines, that power the generators and driven industrial equipment.
Standard

Application Layer—Generator Sets and Industrial

2011-05-16
HISTORICAL
J1939/75_201105
SAE J1939-75 Generator Sets and Industrial Applications defines the set of data parameters (SPNs) and messages (PGNs) for information predominantly associated with monitoring and control generators and driven equipment in electric power generation and industrial applications. Applications using the SAE J1939-75 document may need to reference SAE J1939-71 for the SAE J1939 parameters and messages for monitoring and controlling the power units, e.g. engines and turbines, that power the generators and driven industrial equipment.
Standard

Compliance

2015-06-04
HISTORICAL
J1939/82_201506
SAE J1939-82 Compliance describes the compliance tests and procedures to verify an SAE J1939 ECU will operate correctly on a SAE J1939 network. The purpose of these compliance procedures is to generate one or more test documents that outline the tests needed to assure that an ECU that is designed to operate as a node on a SAE J1939 network would do so correctly. SAE does not certify devices and these tests and their results do not constitute endorsement by SAE of any particular device. These tests are presented to allow testing of a device to determine self-compliance by the manufacturer of a device. The manufacturer can use its record of what procedures were run successfully to show the level of compliance with SAE J1939.
Standard

Compliance—Truck and Bus

2008-08-11
HISTORICAL
J1939/82_200808
The purpose of these compliance procedures is to generate one or more test documents that outline the tests needed to assure that an ECU that is designed to operate as a node on a SAE J1939 network would do so correctly. SAE does not certify devices and these tests and their results do not constitute endorsement by SAE of any particular device. These tests are presented to allow testing of a Device to determine self-compliance by the manufacturer of a device. The manufacturer can use its record of what procedures were run successfully to show the level of compliance with SAE J1939.
Standard

J1939 Digital Annex

2013-08-07
J1939DA_4Q2012
The J1939 Digital Annex The J1939 Digital Annex, introduced in August 2013, offers key J1939 technical data in an Electronic Spreadsheet that can be easily searched, sorted, and adapted to other formats. J1939DA contains all of the SPNs (parameters), PGNs (messages), and other J1939 data previously published in the SAE J1939 top level document. J1939DA also contains all of the SLOTs, Manufacturer ID Codes, NAME Functions, and Preferred Addresses previously published in the SAE J1939 top level and the J1939-71 document. J1939DA contains the complete technical details for all of the SPNs and PGNs previously published in the SAE J1939-71 document. For all other SPNs and PGNs which are published in a document other than SAE J1939-71, J1939DA lists only basic details along with a reference to the document that contains the complete technical details. J1939DA replaces, and expands upon, the 1939 Companion Spreadsheet (CS1939), which was last published through November 2012.
Standard

Network Management

2018-07-23
WIP
J1939/81
SAE J1939-81 Network Management defines the processes and messages associated with managing the source addresses of applications communicating on an SAE J1939 network. 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 initialization processes, requirements for reaction to brief power outages and minimum requirements for ECUs on the network.
Standard

Network Management

2017-03-09
CURRENT
J1939/81_201703
SAE J1939-81 Network Management defines the processes and messages associated with managing the source addresses of applications communicating on an SAE J1939 network. 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 initialization processes, requirements for reaction to brief power outages and minimum requirements for ECUs on the network.
Standard

Network Management

2016-02-18
HISTORICAL
J1939/81_201602
SAE J1939-81 Network Management defines the processes and messages associated with managing the source addresses of applications communicating on an SAE J1939 network. 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 initialization processes, requirements for reaction to brief power outages and minimum requirements for ECUs on the network.
Standard

Network Management

2011-06-30
HISTORICAL
J1939/81_201106
SAE J1939-81 Network Management defines the processes and messages associated with managing the source addresses of applications communicating on an SAE J1939 network. 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 initialization processes, requirements for reaction to brief power outages and minimum requirements for ECUs on the network.
Standard

OBD Communications Compliance Test Cases for Heavy Duty Components and Vehicles

2017-10-18
HISTORICAL
J1939/84_201710
The purpose of this Recommended Practice is to verify that vehicles and/or components are capable of communicating a required set of information, in accordance with the diagnostic messages specified in SAE J1939-73, to fulfill the off-board diagnostic tool interface requirements contained in the government regulations cited below. This document describes the tests, methods, and results for verifying diagnostic communications from an off board diagnostic tool (i.e., scan tool) to a vehicle and/or component. SAE members have generated this document to serve as a guide for testing vehicles for compliance with ARB and other requirements for emissions-related on-board diagnostic (OBD) functions for heavy duty engines used in medium and heavy duty vehicles. The development of HD OBD regulations by US EPA and California’s Air Resources Board (ARB) require that diagnostic message services are exercised to evaluate diagnostic communication standardization requirements on production vehicles.
Standard

OBD Communications Compliance Test Cases for Heavy Duty Components and Vehicles

2012-06-11
HISTORICAL
J1939/84_201206
The purpose of this Recommended Practice is to verify that vehicles and/or components are capable of communicating a required set of information, in accordance with the diagnostic test messages specified in SAE J1939-73, to fulfill the off-board diagnostic tool interface requirements contained in the government regulations cited below. This document describes the tests, test methods, and results for verifying diagnostics communication from an off board diagnostic tool (i.e. scan tool) to a vehicle and/or component. SAE members have generated this document to serve as a guide for testing vehicles for compliance with ARB and other requirements for emissions-related on-board diagnostic (OBD) functions for heavy duty engines used in medium and heavy duty vehicles.
X