Search Results

Standard

Powertrain Control Interface for Electronic Controls Used in Medium- and Heavy-Duty Diesel On-Highway Vehicle Applications

2000-09-29

HISTORICAL

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.

Standard

SERIAL DATA COMMUNICATIONS BETWEEN MICROCOMPUTER SYSTEMS IN HEAVY DUTY VEHICLE APPLICATIONS

1990-10-01

HISTORICAL

J1708_199010

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.

Standard

SERIAL DATA COMMUNICATIONS BETWEEN MICROCOMPUTER SYSTEMS IN HEAVY DUTY VEHICLE APPLICATIONS

1989-11-01

HISTORICAL

J1708_198911

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.

Standard

SERIAL DATA COMMUNICATIONS BETWEEN MICROCOMPUTER SYSTEMS IN HEAVY DUTY VEHICLE APPLICATIONS

1986-01-01

HISTORICAL

J1708_198601

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.

Standard

SERIAL DATA COMMUNICATIONS BETWEEN MICROCOMPUTER SYSTEMS IN HEAVY DUTY VEHICLE APPLICATIONS

1987-06-01

HISTORICAL

J1708_198706

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.

Standard

SERIAL DATA COMMUNICATIONS BETWEEN MICROCOMPUTER SYSTEMS IN HEAVY-DUTY VEHICLE APPLICATIONS

1993-10-19

HISTORICAL

J1708_199310

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.

Standard

Serial Data Communications Between Microcomputer Systems in Heavy-Duty Vehicle Applications

2004-08-25

HISTORICAL

J1708_200408

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.

Standard

Serial Data Communications Between Microcomputer Systems in Heavy-Duty Vehicle Applications

2008-10-21

HISTORICAL

J1708_200810

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.

Standard

Serial Data Communications Between Microcomputer Systems in Heavy-Duty Vehicle Applications

2010-12-09

HISTORICAL

J1708_201012

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.

Standard

Serial Data Communications Between Microcomputer Systems in Heavy-Duty Vehicle Applications

2016-09-13

CURRENT

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.

Standard

Transport Area Network Cabling

2011-06-30

CURRENT

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.

Standard

Transport Area Network Cabling

2000-03-21

HISTORICAL

J2496_200003

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.

Standard

Transport Area Network Cabling

2007-02-21

HISTORICAL

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.

Standard

VEHICLE ELECTRONIC PROGRAMMING STATIONS (VEPS) SYSTEM SPECIFICATION FOR PROGRAMMING COMPONENTS AT OEM ASSEMBLY PLANTS

1997-02-01

HISTORICAL

J2214_199702

This system specification, SAE J2214, revises the requirements for Vehicle Electronics Programming Stations (VEPS) set forth in SAE J1924, OEM/Vendor Interface Specification for Vehicle Electronic Programming Stations. The requirements of SAE J2214 supersede the requirements defined by SAE J1924.

Standard

VENDOR COMPONENT PROGRAM DATA FILE INTERFACE FOR OEM ASSEMBLY OPERATIONS

1997-02-01

HISTORICAL

J2286_199702

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.

Standard

Vehicle Electronic Programming Stations (VEPS) System Specification for Programming Components at OEM Assembly Plants

2004-06-01

CURRENT

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.

Standard

Vehicle Electronic Programming Stations (VEPS) System Specification for Win32®

2022-11-22

HISTORICAL

J2461_202211

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.

Standard

Vehicle Electronic Programming Stations (VEPS) System Specification for Win32®

2013-09-23

HISTORICAL

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.

Standard

Vehicle Electronic Programming Stations (VEPS) System Specification for Win32®

2023-07-31

CURRENT

J2461_202307

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.

Standard

Vehicle Electronic Programming Stations (VEPS) System Specification for Win32™

1998-11-01

HISTORICAL

J2461_199811

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™ environment while maintaining the core VEPS architecture specified in SAE J2214.