Browse Topic: Electronic control systems
This SAE Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On- and Off-Road Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features). The Physical Layer parameters are specified as they would be detected on the network media, not within any particular module or integrated circuit implementation. Although devices may be
The SAE J1962 diagnostic connector consists of two mating connectors, the vehicle connector (see Figure 1) and the test equipment connector (see Figure 2). This document: a Defines the functional requirements for the vehicle connector. These functional requirements are separated into four principal areas: connector location/access, connector design, connector terminal assignments, and connector electrical interface requirements. b Defines the functional requirements for the test equipment connector. These functional requirements are separated into three principal areas: connector design, connector terminal assignments, and connector electrical interface requirements. The scope of this document does not include the needs of long-term retention, such as in-flight recorder type applications. To ensure long-term retention, additional steps outside of the scope of this document must be taken.
This SAE Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On- and Off-Road Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features). The Physical Layer parameters are specified as they would be detected on the network media, not within any particular module or integrated circuit implementation. Although devices may be
This SAE Recommended Practice provides the framework to allow reprogramming software applications from all vehicle manufacturers the flexibility to work with multiple vehicle data link interface tools from multiple tool suppliers. This system enables each vehicle manufacturer to control the programming sequence for electronic control units (ECUs) in their vehicles, but allows a single set of programming hardware and vehicle interface to be used to program modules for all vehicle manufacturers. This document does not limit the hardware possibilities for the connection between the PC used for the software application and the tool (e.g., RS-232, RS-485, USB, Ethernet…). Tool suppliers are free to choose the hardware interface appropriate for their tool. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with hardware supplied by any tool manufacturer. U.S. Environmental Protection Agency (EPA) and the California Air Resources
The purpose of this SAE Information Report is to specify the requirements necessary to fully define the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in Fiat Chrysler Automobiles (FCA) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding “pass-thru programming” of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are necessary to provide independent automotive service organizations and after-market scan tool suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles. Specifically, this document details the SCI physical layer and SCI data link layer requirements necessary to establish communications between a diagnostic tester and an ECU. It further specifies additional
This SAE Recommended Practice describes a standardized interface that connects between a standard personal computer (PC) and vehicle. The purpose of this interface is to enable the reprogramming of emission-related control modules, in 2004 and later model year vehicles. The interface shall consist of the necessary hardware and/or software to support the requirements defined in this document. It is expected that vehicle manufacturers will provide the software application that will control the Pass-Thru Interface, to perform the actual reprogramming. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with interface supplied by any tool manufacturer. A common interface for all vehicle manufacturers reduces the tool costs for aftermarket garages, while allowing each vehicle manufacturer to control the programming sequence for the electronic control units (ECUs) in their vehicles. Aftermarket garages will be able to obtain a
This document supersedes SAE J1962 200204, and is technically equivalent to ISO/DIS 15031-3: December 14, 2001. This document is intended to satisfy the requirements of an OBD connector as required by U.S. On-Board Diagnostic (OBD) regulations. The diagnostic connection specified in this document consists of two mating connectors, the vehicle connector and the external test equipment connector. This document specifies: a The functional requirements for the vehicle connector. These functional requirements are separated into four principal areas: connector location/access, connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits, b The functional requirements for the external test equipment connector. These functional requirements are separated into three principal areas: connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits.
The purpose of this SAE Information Report is to specify the requirements necessary to fully define the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in Fiat Chrysler Automobiles (FCA) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding “pass-thru programming” of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are necessary to provide independent automotive service organizations and after-market scan tool suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles. Specifically, this document details the SCI physical layer and SCI data link layer requirements necessary to establish communications between a diagnostic tester and an ECU. It further specifies additional
This SAE Recommended Practice establishes the requirements for a Class B Data Communication Network Interface applicable to all on and off-road land based vehicles. This document defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Although this document addresses all seven layers of the OSI model, it primarily focuses on the Network, Data Link and Physical Layers. Taken in total, the requirements contained in this document specify a data communications network philosophy that satisfies the needs of automotive manufacturers. Although the higher layer OSI requirements are essentially identical for all networks defined by this document (see Section 3.3, Figure 1), differing data rate requirements necessitate the use of different physical layers. Therefore, one physical layer is optimized for a data rate of 10.4 Kbps while the other physical layer is optimized
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
This SAE Recommended Practice defines the requirements of OBD II Scan Tools, i.e., test equipment that will interface with vehicle modules in support of the OBD II diagnostic requirements. It covers the required capabilities of and conformance criteria for OBD II Scan Tools.
This SAE Recommended Practice defines the test conditions, procedures, and performance specifications for 6- and 12-v stop lamp switches intended for use on motorcycles.
This SAE Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On- and Off-Road Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features). The Physical Layer parameters are specified as they would be detected on the network media, not within any particular module or integrated circuit implementation. Although devices may be
This SAE Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On-and OffRoad Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features). The Physical Layer parameters are specified as they would be detected on the network media, not within any particular module or integrated circuit implementation. Although devices may be
This SAE Standard specifies the ESD test methods and procedures necessary to evaluate electronic modules intended for vehicle use. It describes test procedures for evaluating electronic modules in complete vehicles. A procedure for verifying the simulator that is used to generate the electrostatic discharges is given in Appendix A. Functional status classifications for immunity to ESD are given in Appendix B.
SAE J1978/ISO 15031-4 specifies a complementary set of functions to be provided by an OBD-II scan tool. These functions provide complete, efficient, and safe access to all regulated OBD (on-board diagnostic) services on any vehicle which is compliant with SAE J1978/ISO 15031-4. The SAE J1978 content of this document is intended to satisfy the requirements of an OBD-II scan tool as required by current U.S. on-board diagnostic (OBD) regulations. The ISO 15031-4 content of this document is intended to satisfy the requirements of OBD requirements in countries other than the U.S., and includes functionality not required or not allowed in the U.S. This document specifies: A means of establishing communications between an OBD-equipped vehicle and an OBD-II scan tool. A set of diagnostic services to be provided by an OBD-II scan tool in order to exercise the services defined in SAE J1979/ISO 15031-5. SAE J1978/ISO 15031-4 does not preclude the inclusion of additional capabilities or functions
This SAE Recommended Practice provides the framework to allow reprogramming software applications from all vehicle manufacturers the flexibility to work with multiple vehicle data link interface tools from multiple tool suppliers. This system enables each vehicle manufacturer to control the programming sequence for electronic control units (ECUs) in their vehicles, but allows a single set of programming hardware and vehicle interface to be used to program modules for all vehicle manufacturers. This document does not limit the hardware possibilities for the connection between the PC used for the software application and the tool (e.g., RS-232, RS-485, USB, Ethernet…). Tool suppliers are free to choose the hardware interface appropriate for their tool. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with hardware supplied by any tool manufacturer. U.S. Environmental Protection Agency (EPA) and the California Air Resources
This Technical Information Report defines the General Motors UART Serial Data Communications Bus, commonly referred to as GM UART. This document should be used in conjunction with SAE J2534-2 in order to enhance an SAE J2534 interface to also provide the capability to program ECUs with GM UART. SAE J2534-1 includes requirements for an interface that can be used to program certain emission-related Electronic Control Units (ECUs) as required by U.S. regulations, and SAE J2534-2 defines enhanced functionality required to program additional ECUs not mandated by current U.S. regulations. The purpose of this document is to specify the requirements necessary to implement GM UART in an enhanced SAE J2534 interface intended for use by independent automotive service facilities to program GM UART ECUs in General Motors vehicles.
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
The SAE J1962 diagnostic connector consists of two mating connectors, the vehicle connector (see Figure 1) and the test equipment connector (see Figure 2). This document: a Defines the functional requirements for the vehicle connector. These functional requirements are separated into three principal areas: connector location/access, connector design, and connector terminal assignments. b Defines the functional requirements for the test equipment connector. These functional requirements are separated into two principal areas: connector design and connector terminal assignments. The scope of this document does not include the needs of long-term retention, such as in-flight recorder type applications. To ensure long-term retention, additional steps outside of the scope of this document must be taken.
This SAE Recommended Practice supersedes SAE J1978 FEB1998, and is technically equivalent to ISO/DIS 15031-4:December 14, 2001. This document is intended to satisfy the requirements of an OBD scan tool as required by U.S. On-Board Diagnostic (OBD) regulations. The document specifies: a A means of establishing communications between an OBD-equipped vehicle and external test equipment, b A set of diagnostic services to be provided by the external test equipment in order to exercise the services defined in SAE J1979, c Conformance criteria for the external test equipment.
This SAE Recommended Practice will define the Physical Layer and portions of the Data Link Layer of the Open Systems Interconnection model (ISO 7498) for a 500 kbps High-Speed CAN (HSC) protocol implementation. Both ECU and media design requirements for networks will be specified. Requirements will primarily address the CAN physical layer implementation. Requirements will focus on a minimum standard level of performance from the HSC implementation. All ECUs and media shall be designed to meet certain component level requirements in order to ensure the HSC implementation system level performance at 500 kbps. The minimum performance level shall be specified by system level performance requirements or characteristics described in detail in Section 5 of this document. This document is designed such that if the Electronic Control Unit (ECU) requirements defined in Section 6 are met, then the system level attributes should be obtainable. This document will address only requirements which may
This SAE Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On-and OffRoad Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features). The Physical Layer parameters are specified as they would be detected on the network media, not within any particular module or integrated circuit implementation. Although devices may be
This Technical Information Report defines the proprietary diagnostic communication protocol for ABS or VSA ECU (Electronic Control Unit) implemented on some Honda vehicles. This protocol does not apply to all Honda vehicles. This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an enhanced SAE J2534 interface. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an enhanced SAE J2534 interface.
Vehicle electrical/electronic systems may be affected when immersed in an electromagnetic field generated by sources such as radio and TV broadcast stations, radar and communication sites, mobile transmitters, cellular phones, etc. This part of SAE J551 specifies off-vehicle radiated source test methods and procedures for testing passenger cars and commercial vehicles within a Reverberation Chamber. The method is used to evaluate the immunity of vehicle mounted electronic devices in the frequency range of 80 MHz to 2 GHz, with possible extensions 20 MHz to 10 GHz, depending upon chamber size and construction. Three methods for calibrating and applying electromagnetic fields are described in the document: 1) Mode Tuned Reverberation Chamber method, 2) Mode Stir (Standard) Reverberation Chamber method and 3) Mode Stir (Hybrid) Reverberation Chamber method. Optional pulse modulation testing at HIRF (High Intensity Radiated Fields) test levels, based upon currently known environmental
The scope of this recommended practice encompasses the range of environments which influence the performance and reliability of the electronic equipment designed for heavy duty on and off road vehicles, as well as any appropriate stationary applications which also use these vehicle derived components. A few examples of such vehicles are on and off highway trucks, trailers, buses, construction equipment and agricultural equipment including implements.
This SAE Aerospace Recommended Practice (ARP) outlines the functional and design requirements for a battery powered, self-propelled belt conveyor for handling baggage and cargo at aircraft bulk cargo holds.
This SAE Aerospace Recommended Practice (ARP) outlines the functional and design requirements for a battery powered, self-propelled belt conveyor for handling baggage and cargo at aircraft bulk cargo holds. Additional considerations and requirements may legally apply in other countries. As an example, for operation in Europe (E.U. and E.F.T.A.), the applicable EN standards shall be complied with.
This SAE Recommended Practice provides definitions of common terms used in SAE Documents pertaining to motor vehicle lighting. It covers not only basic lighting terms but also terms which identify major segments of technical reports.
The methods included in this document are: a Voltage-Temperature Design Margins. b Voltage Interruptions and Transients. c Voltage Dropouts and Dips. d Current Draw Under a Number of Conditions. e Switch Input Noise These methods are best applied during the Development stage but can be used at all stages (e.g., Pre-Qualification, Qualification or Conformity).
This Technical Information Report defines the diagnostic communication protocol Keyword Protocol 1281 (KWP1281). This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an SAE J2534 interface. Some Volkswagen of America and Audi of America vehicles are equipped with ECUs, in which a KWP1281 proprietary diagnostic communication protocol is implemented. The purpose of this document is to specify the KWP1281 protocol in enough detail to support the requirements necessary to implement the communication protocol in an SAE J2534 interface device.
Vehicle electrical/electronic systems may be affected when immersed in an electromagnetic field generated by sources such as radio and TV broadcast stations, radar and communication sites, mobile transmitters, cellular phones, etc. The reverberation method is used to evaluate the immunity of electronic devices in the frequency range of 500 MHz to 2.0 GHz, with possible extensions to 200 MHz and 10 GHz, depending upon chamber size and construction. Optional pulse modulation testing at HIRF (High Intensity Radiated Fields) test levels, based upon currently known environmental threats, has been added to this revision of the standard. This document addresses the Mode Stir (Continuous Stirring) Reverberation testing method which has been successfully utilized as a design and production stage development tool for many years. The Mode Tuned (Stepped Tuner) Reverberation testing method is covered in the SAE J1113-28 document.
This SAE Standard provides a general method for defining the acceptable function performance status classification for the functions of automotive electronic devices upon application of the test conditions specified as described in appropriate EMC immunity test standards (for example, SAE J1113 and SAE J551). Testing of devices could be performed either on or off vehicles. Appropriate test signal and methods, Function Performance status, and test signal severity level would have to be specified in the individual cases.
Vehicle electrical/electronic systems may be affected when immersed in an electromagnetic field generated by sources such as radio and TV broadcast stations, radar and communication sites, mobile transmitters, cellular phones, etc. The reverberation method is used to evaluate the immunity of electronic devices in the frequency range of 500 MHz to 2.0 GHz, with possible extensions to 200 MHz and 10 GHz, depending upon chamber size and construction. Optional pulse modulation testing at HIRF (High Intensity Radiated Fields) test levels, based upon currently known environmental threats, has been added to this revision of the standard. This document addresses the Mode Stir (Continuous Stirring) Reverberation testing method which has been successfully utilized as a design and production stage development tool for many years. The Mode Tuned (Stepped Tuner) Reverberation testing method is covered in the SAE J1113-28 document.
This SAE Information Report defines a procedure for indicating the severity of narrowband emissions from an electronic system-component.
This SAE Standard defines the test conditions, procedures, and performance specifications for 6 V and 12 V stop lamp switches intended for use on motorcycles.
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
Items per page:
50
1 – 50 of 4093