Criteria

Display:

Results

Viewing 1 to 19 of 19
CURRENT
2004-06-01
Standard
J1683_200406
The communication driver described in this SAE Recommended Practice resides on the PC between the SAE J1708 hardware and the individual application programs developed by each supplier. From the perspective of the application program, the SAE J1708 hardware is totally transparent. This means diagnostic programs can operate on any PC using any SAE J1708 adapter hardware. The diagnosic (application) program sees no different from one hardware base to the next. All hardware-specific tasks are handled by this document. This allows for complete portability of software programs. It also guarantees complete functionality from one hardware platform to the next. The standard presented applies to computer systems that use the MS-DOS operating system. Design standards that contain the same functionality may be defined in the future for other operating systems.
CURRENT
2000-08-28
Standard
J1924_200008
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.
CURRENT
2004-06-01
Standard
J2214_200406
The SAE J2214 specification describes the application of the MS-DOS(TM) computer between the OEM and component vendors, defines the required elements comprising a Vehicle Electronics Programming Station, and identifies software interfaces needed between OEM-supplied elements and vendor-supplied elements. The software interfaces are described in SAE J2286 and SAE J1683. By maintaining common elements with J1924, the orderly transition from vendor Communication Programs to Vendor Component Programs will be assured. Beyond clarification of the J1924 document, the changes to VEPS and Vendor Communications Programs are focused on the implementation of a common method for communicating with the vehicle's network for all vendor communications.
HISTORICAL
2007-02-21
Standard
J2496_200702
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.
CURRENT
2011-06-30
Standard
J2496_201106
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.
HISTORICAL
1997-02-01
Standard
J2286_199702
The 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, SAE J1708. 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.
CURRENT
2013-09-23
Standard
J2461_201309
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.
HISTORICAL
2010-02-05
Standard
J2461_201002
Identification 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 isno longer needed or relevant. Introduction SAE J2461 describes the application of the Win32™ environment to the customization of programmable components assembled in OEM vehicles, where components provide a communication API such as TMC RP1210B.
HISTORICAL
2002-08-29
Standard
J2461_200208
Identification This system specification, SAE J2461, revises 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. SAE J2461 specifies the recommended practices for a Win32 TM environment while maintaining the core VEPS architecture specified in SAE J2214. Introduction SAE J2461 describes the application of the Win32 TM environment to the customization of programmable components assembled in OEM vehicles, where components provide a communication API such as TMC RP1210. Because the customization is performed using both OEM-provided and vendor-provided software, the roles and responsibilities of the vendor and OEM elements must be defined to permit the development of common vendor software elements for all Original Equipment Manufacturers (OEMs).
HISTORICAL
2000-09-29
Standard
J1922_200009
This SAE Recommended Practice provides a development or possibly interim production communication protocol between engine, transmission, ABS/traction control, and retarder systems until higher speed communication links are established.
HISTORICAL
2008-12-04
Standard
J1922_200812
This SAE Recommended Practice provides a development or possibly interim production communication protocol between engine, transmission, ABS/traction control, and retarder systems until higher speed communication links are established.
CURRENT
2011-08-12
Standard
J1922_201108
This SAE Recommended Practice provides a development or possibly interim production communication protocol between engine, transmission, ABS/traction control, and retarder systems until higher speed communication links are established.
CURRENT
2016-09-13
Standard
J1708_201609
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.
HISTORICAL
2004-08-25
Standard
J1708_200408
This SAE Recommended Practice 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 communications link implementation and use should be specified in the separate application documents referenced in Section 2. Save money while getting up-to-date access to the standards you need! Subscribe to the SAE J1939 Standards Collection on the Web and get one year of anytime access and automatic updates to the J1939 family of documents, plus all cross-referenced and selected related documents.
CURRENT
2012-07-30
Standard
J2497_201207
This SAE Recommended Practice defines a method for implementing a bidirectional, serial communications link over the vehicle power supply line among modules containing microcomputers. This document defines those parameters of the serial link that relate primarily to hardware and software compatibility such as interface requirements, system protocol, and message format that pertain to Power Line Communications (PLC) between Tractors and Trailers. This document defines a method of activating the trailer ABS Indicator Lamp that is located in the tractor.
HISTORICAL
2010-12-09
Standard
J2497_201012
This SAE Recommended Practice defines a method for implementing a bidirectional, serial communications link over the vehicle power supply line among modules containing microcomputers. This document defines those parameters of the serial link that relate primarily to hardware and software compatibility such as interface requirements, system protocol, and message format that pertain to Power Line Communications (PLC) between Tractors and Trailers. This document defines a method of activating the trailer ABS Indicator Lamp that is located in the tractor.
HISTORICAL
2007-06-21
Standard
J2497_200706
This SAE Recommended Practice defines a method for implementing a bidirectional, serial communications link over the vehicle power supply line among modules containing microcomputers. This document defines those parameters of the serial link that relate primarily to hardware and software compatibility such as interface requirements, system protocol, and message format that pertain to Power Line Communications (PLC) between Tractors and Trailers. This document defines a method of activating the trailer ABS Indicator Lamp that is located in the tractor.
HISTORICAL
2002-10-31
Standard
J2497_200210
This SAE Recommended Practice defines a method for implementing a bidirectional, serial communications link over the vehicle power supply line among modules containing microcomputers. This document defines those parameters of the serial link that relate primarily to hardware and software compatibility such as interface requirements, system protocol, and message format that pertain to Power Line Communications (PLC) between Tractors and Trailers. This document defines a method of activating the trailer ABS Indicator Lamp that is located in the tractor.
HISTORICAL
2002-02-07
Standard
J1587_200202
This SAE Recommended Practice 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 SAE Truck and Bus Low Speed Communications Network Subcommittee (formerly 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.
Viewing 1 to 19 of 19