Search Results

This SAE Recommended Practice defines a recommended practice for implementing a bidirectional, serial communication link among modules containing microcomputers. This document defines those parameters of the serial link that relate primarily to hardware and basic software compatibility such as interface requirements, system protocol, and message format. The actual data to be transmitted by particular modules, which is an important aspect of communications compatibility, is not specified in this document. These and other details of communication link implementation and use should be specified in the separate application documents referenced in Section 2.

This interface document SAE J2286 revises the requirements for file formats as were originally described in SAE J1924. This document describes Interface 1 (I/F 1) in SAE J2461. This document does not imply the use of a specific hardware interface, but may be used with other hardware interfaces such as SAE J1939, ISO 15765 or ISO 14229. The requirements of SAE J2286 supersede the requirements defined by SAE J1924.

This series of SAE Recommended Practices was developed to provide an open architecture system for on-board electronic systems. It is the intention of these documents to allow electronic devices to communicate with each other by providing a standard architecture. This particular document describes the Network Interface and Cabling which defines the requirements needed for communicating between devices that are on different segments of the SAE J2496 Transport Area Network. While these recommended practices may be used in retrofitting older vehicles, the primary intent is for implementation in new bus procurements.

This SAE Recommended Practice defines a recommended practice for implementing a bidirectional, serial communication link among modules containing microcomputers. This document defines those parameters of the serial link that relate primarily to hardware and basic software compatibility such as interface requirements, system protocol, and message format. The actual data to be transmitted by particular modules, which is an important aspect of communications compatibility, is not specified in this document. These and other details of communication link implementation and use should be specified in the separate application documents referenced in Section 2.

This series of SAE Recommended Practices was developed to provide an open architecture system for on-board electronic systems. It is the intention of these documents to allow electronic devices to communicate with each other by providing a standard architecture. This particular document describes the Network Interface and Cabling which defines the requirements needed for communicating between devices that are on different segments of the SAE J2496 Transport Area Network. While these recommended practices may be used in retrofitting older vehicles, the primary intent is for implementation in new bus procurements.

This SAE Recommended Practice defines a recommended practice for implementing a bidirectional, serial communication link among modules containing microcomputers. This document defines those parameters of the serial link that relate primarily to hardware and basic software compatibility such as interface requirements, system protocol, and message format. The actual data to be transmitted by particular modules, which is an important aspect of communications compatibility, is not specified in this document. These and other details of communication link implementation and use should be specified in the separate application documents referenced in Section 2.

This document defines a recommended practice for implementing a bidirectional, serial communication link among modules containing microcomputers. This document defines those parameters of the serial link that relate primarily to hardware and basic software compatibility such as interface requirements, system protocol, and message format. The actual data to be transmitted by particular modules, which is an important aspect of communications compatibility, is not specified in this document. These and other details of communication link implementation and use should be specified in the separate application documents referenced in Section 2.

This document defines a recommended practice for implementing a bidirectional, serial communication link among modules containing microcomputers. This document defines those parameters of the serial link that relate primarily to hardware and basic software compatibility such as interface requirements, system protocol, and message format. The actual data to be transmitted by particular modules, which is an important aspect of communications compatibility, is not specified in this document. These and other details of communication link implementation and use should be specified in the separate application documents referenced in Section 2.

This document defines a document for the format of messages and data that is of general value to modules on the data communications link. Included are field descriptions, size, scale, internal data representation, and position within a message. This document also describes guidelines for the frequency of and circumstances in which messages are transmitted. In order to promote compatibility among all aspects of electronic data used in heavy-duty applications, it is the intention of the Data Format Subcommittee (in conjunction with other industry groups) to develop recommended message formats for: a Vehicle and Component Information - This includes all information that pertains to the operation of the vehicle and its components (such as performance, maintenance and diagnostic data). b Routing and Scheduling Information - Information related to the planned or actual route of the vehicle.

This document defines a recommended practice for the format of messages and data that is of general value to modules on the data communications link. Included are field descriptions, size, scale, internal data representation, and position within a message. The recommended practice also describes guidelines for the frequency of and circumstances in which messages are transmitted. In order to promote compatibility among all aspects of electronic data used in heavy duty applications, it is the intention of the Data Format Subcommittee (in conjunction with other industry groups) to develop recommended message formats for: a) Vehicle and Component Information - This includes all information that pertains to the operation of the vehicle and its components (such as performance, maintenance and diagnostic data). b) Routing and Scheduling Information - Information related to the planned or actual route of the vehicle.

This document defines a recommended practice for implementing a bi-directional, serial communication link among modules containing microcomputers. This document defines those parameters of the serial link which relate primarily to hardware and basic software compatibility such as interface requirements, system protocol, and message format. The actual data to be transmitted by particular modules, which is an important aspect of communications compatibility, is not specified in this Recommended Practice. These and other details of communication link implementation and use should be specified in the separate application documents referenced in Section 3.1.

This document defines a recommended practice for implementing a bi-directional, serial communication link among modules containing microcomputers. This document defines those parameters of the serial link which relate primarily to hardware and basic software compatibility such as interface requirements, system protocol, and message format. The actual data to be transmitted by particular modules, which is an important aspect of communications compatibility, is not specified in this Recommended Practice. These and other details of communication link implementation and use should be specified in the separate application documents referenced in Section 3.1.