Refine Your Search

Search Results

Viewing 1 to 16 of 16
Standard

MS-DOS™ INTERFACE FOR SAE J1708 COMMUNICATIONS

1997-02-01
HISTORICAL
J1683_199702
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 diagnostic (application) program sees no difference 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.
Standard

MS-DOS™ Interface for SAE J1708 Communications

2004-06-01
CURRENT
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.
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

Power Line Carrier Communications for Commercial Vehicles

2010-12-09
HISTORICAL
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.
Standard

Power Line Carrier Communications for Commercial Vehicles

2007-06-21
HISTORICAL
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.
Standard

Power Line Carrier Communications for Commercial Vehicles

2023-11-01
CURRENT
J2497_202311
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.
Standard

Power Line Carrier Communications for Commercial Vehicles

2002-10-31
HISTORICAL
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.
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

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

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

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

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

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

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

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

Electronic Data Interchange Between Microcomputer Systems in Heavy-Duty Vehicle Applications

2013-01-04
CURRENT
J1587_201301
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.
X