Refine Your Search

Date

Date

Topic

Topic

Truck and Bus Low Speed Communication Network Committee Electrical, Electronics, and Avionics Manufacturing processes

Search Results

Viewing 1 to 20 of 41
123Next >Last >>
Sort by relevance
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

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

Vehicle Electronic Programming Stations (VEPS) System Specification for Win32™
2010-02-05
HISTORICAL
J2461_201002
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™
2002-08-29
HISTORICAL
J2461_200208
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.
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

Vendor Component Program Data File Interface for OEM Assembly Operations
2015-07-08
CURRENT
J2286_201507
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.
Standard

Vendor Component Program Data File Interface for OEM Assembly Operations
2010-05-03
HISTORICAL
J2286_201005
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.
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 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.
123Next >Last >>
X