Search Results

The purpose of the SAE Information Report is to address the method of loading vehicle electronic controllers with chassis and customer specific parameters. This specification shall establish an interface definition. The interface definition must be mutually agreeable to truck OEMs and vendors. The purpose of this specification is not to answer the large protocol issues raised by systems such as GM's MAP. SAE Standard In the future, SAE may use this specification as a basis for an OEM/Vendor interface specification standard.

SAE J2461 specifies the recommended practices of a Vehicle Electronics Programming Stations (VEPS) architecture.in a Win32® environment. This system specification, SAE J2461, was a revision of the requirements for Vehicle Electronics Programming Stations (VEPS) set forth in SAE J2214, Vehicle Electronics Programming Stations (VEPS) System Specification for Programming Components at OEM Assembly Plants (Cancelled Jun 2004). The J2214 standard has been cancelled indicating that it is no longer needed or relevant.

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

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