Search Results

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

These Recommended Practices are intended for light, medium, 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 Recommended Practices is to provide an open interconnect system for electronic systems. It is the intention of these Recommended Practices to allow Electronic Control Units to communicate with each other by providing a standard architecture.

These Recommended Practices are intended for light, medium, 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 Recommended Practices is to provide an open interconnect system for electronic systems. It is the intention of these Recommended Practices to allow Electronic Control Units to communicate with each other by providing a standard architecture.

These Recommended Practices are intended for light, medium, 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 Recommended Practices is to provide an open interconnect system for electronic systems. It is the intention of these Recommended Practices to allow Electronic Control Units to communicate with each other by providing a standard architecture.

These Recommended Practices are intended for light, medium, 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 Recommended Practices is to provide an open interconnect system for electronic systems. It is the intention of these Recommended Practices to allow Electronic Control Units to communicate with each other by providing a standard architecture.

This top level document provides a general overview of the SAE J1939 network and describes the subordinate document structure. This document includes definitions of terms and abbreviations which are used among the various SAE J1939 subordinate documents. The SAE J1939DA Digital Annex spreadsheet replaces the Appendices of this document for the publication of the list of all SPN assignments, PGN assignments, NAME Function assignments, Manufacturer Code assignments, and Preferred Address assignments. This document has been updated to reflect the change to discontinue publishing the content of Table A2, Tables B1 through B12, and Table C1 in Appendix A, Appendix B, and Appendix C; instead, this content is now published in the SAE J1939DA Digital Annex spreadsheet.

The SAE J1939 communications network is developed for use in heavy-duty environments and suitable 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 interest include, but are not limited to, on-highway and off-highway trucks and their trailers, construction equipment, and agricultural equipment and implements. SAE J1939-71 Vehicle Application Layer is the SAE J1939 reference document for the conventions and notations that specify parameter placement in PGN data fields, the conventions for ASCII parameters, and conventions for PGN transmission rates. This document previously contained the majority of the SAE J1939 data parameters and messages for information exchange between the ECU applications connected to the SAE J1939 communications network.