Display:

Results

Viewing 1 to 30 of 671
CURRENT
2016-09-14
Standard
AS1145C
This specification covers minimum requirements for brake temperature monitoring equipment whenever used on any type and model of civil aircraft. It shall be the responsibility of the purchaser to determine the compatibility of these requirements with the application aircraft and to specify requirements in excess of these minimums as necessary.
2016-09-07
WIP Standard
J3005-1
SAE J3005-1 is being published as a new document which replaces J3005:20140602 ( Guidance for Remote I/M programs, Portable Emission Measurement Systems (PEMS), GPS, Wireless-LAN or Bluetooth interfaces and insurance devices.) The SAE J3005-1 devices are not intended to be used for SAE J1699-3 vehicle validation testing. The document focuses on OBD mandated communication protocols defined in SAE J1979.
2016-09-06
WIP Standard
J2819
This Technical Information Report defines the diagnostic communication protocol TP2.0. 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 ECU(s), in which a TP2.0 proprietary diagnostic communication protocol is implemented. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an SAE J2534 interface.
2016-09-06
WIP Standard
J2818
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.
2016-08-05
Magazine
Clearing the air Sensors, diagnostics and controls advance to help trap emissions. Bringing the heat on cooling technologies Electronic controls, variable-speed fans cool engines, heat aftertreatment systems. 3D printing machines can't be built fast enough In the additive manufacturing world, the costs of components are dropping, the technology is becoming more reliable and parts are fabricated faster, allowing industries beyond aerospace to adopt additive technologies, says Oak Ridge Lab's Ryan Dehoff.
CURRENT
2016-07-12
Standard
J1962_201607
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.
2016-06-03
Magazine
Executive viewpoints Industry leaders offer their insights on the state of the heavy-duty on- and off-highway industries in this annual series of opinion pieces. The executives share their views on the most pressing technologies and trends shaping their business and the industry moving forward. Annual Product Guide Top products from throughout the industry covering technologies such as Powertrain & Energy, Hydraulics, Electronics, and Testing & Simulation.
2016-05-20
Book
This is the electronic format of the Journal.
2016-04-05
Technical Paper
2016-01-0960
Arifumi Matsumoto, Kenji Furui, Makoto Ogiso, Toru Kidokoro
Abstract Urea selective catalytic reduction (SCR) systems are a promising technology for helping to lower NOx emissions from diesel engines. These systems also require on-board diagnostic (OBD) systems to detect malfunctioning catalysts. Conventional OBD methodology for a SCR catalyst involves the measurement of NOx concentration downstream of the catalyst. However, considering future OBD regulations, erroneous diagnostics may occur due to variations in the actual environment. Therefore, to enhance OBD accuracy, a new methodology was examined that utilizes NH3 slip as a new diagnostic parameter in addition to NOx. NH3 slip increases as the NOx reduction performance degrades, because both phenomena are based on deterioration in the capability of the SCR catalyst to adsorb NH3. Furthermore, NH3 can be measured by existing NOx sensors because NH3 is oxidized to NO internally. To make use of NH3 slip, an estimation model was developed.
2016-04-05
Technical Paper
2016-01-0044
Sung Yul Chu, Sung Eun Jo, Kyoungbok Lee, Kwang Chul Oh, Jong Rim Lee
Abstract On-board diagnostics (OBD) of diesel vehicles require various sensors to detect system malfunctions. The Particulate Matter (PM) sensor is one of OBD devices which gather information which could be critical in determining a crack in the diesel particulate filters (DPFs). The PM sensor detects PM which penetrates cracked DPFs and converts the amount of PM into electrical values. The PM sensor control unit (SCU) receives those analog signals and converts them to digital values through hardware and software solutions. A capacitive sensing method would be a stable solution because it detects not raw analog signals but electrical charges or a time constant going through the capacitive load. Therefore, amount of PM would be converted reasonable value of capacitance even though there is a little amount of PM.
2016-04-05
Technical Paper
2016-01-0072
Jihas Khan
Abstract Unified Diagnostic Service and On Board Diagnostics require a client side device with necessary software to implement certain specific algorithms. This paper proposes a highly optimized and generic model based architecture to implement client side algorithms used in Unified Diagnostic Service systems and with On Board Diagnostics which can be reused for any hardware target. The proposed method can implement particular algorithms which include flow control, timing control, database parsing, logging of messages, diagnostic database parsing, security unlock, intuitive HMI layer, DTC display with textual information, frame control, multi network - multi ECU support, software flashing, physical-functional message handling, and interfacing for multiple hardware host devices. Re-usability of this model based product ensures that it can be ported to the diagnostic tool used by a work shop engineer or by a diagnostics validation engineer working at OEM or Tier 1suppliers.
2016-04-05
Technical Paper
2016-01-0611
Dejan Kihas, Daniel Pachner, Lubomir Baramov, Michael Uchanski, Priya Naik, Nassim Khaled
Abstract The interest for NOx estimators (also known as virtual sensors or inferential sensors) has increased over the recent years due to benefits attributed to cost and performance. NOx estimators are typically installed to improve On-Board Diagnostics (OBD) monitors or to lower bill of material costs by replacing physical NOx sensors. This paper presents initial development results of a virtual engine-out NOx estimator planned for the implementation on an ECM. The presented estimator consists of an airpath observer and a NOx combustion model. The role of the airpath observer is to provide input values for the NOx combustion model such as the states of the gas at the intake and exhaust manifolds. It contains a nonlinear mean-value model of the airpath suitably transformed for an efficient and robust implementation on an ECM. The airpath model uses available sensory information in the vehicle to correct predictions of the gas states.
2016-04-05
Technical Paper
2016-01-0073
Peter Subke, Muzafar Moshref
Abstract Passenger cars are equipped with an OBD connector according to SAE J1962 / ISO 15031-3. Passenger cars that support ISO UDS on DoIP use the same connector with Ethernet pins according to ISO/DIS 13400-4 (Ethernet diagnostic connector). If external test equipment is connected to the Ethernet diagnostic connector via a 100BASE-TX cable with the RJ45 connector at the tester, a VCI is not necessary anymore. With a device that fits the Ethernet diagnostic connector physically and acts as a converter between the Ethernet signals and WLAN, external test equipment that supports wireless communication, can be connected to the vehicle. Examples for such wireless external test equipment include Android/iOS- based smart phones and tablets with purpose-made applications (APPs). The software components of external test equipment are standardized in ISO 22900 (MVCI). The MVCI D-Server processes data in ODX (ISO 22901) and sequences in OTX (ISO 13209).
2016-04-05
Technical Paper
2016-01-0633
Yichao Guo
Abstract Per California Air Resources Board (CARB) regulations, On-board diagnostic (OBD) of vehicle powertrain systems are required to continuously monitor key powertrain components, such as the circuit discontinuity of actuators, various circuit faults of sensors, and out-of-range faults of sensors. The maturing and clearing of these continuous monitoring faults are critical to simplification of algorithm design, save of engineering cost (i.e., calibration), and reduction of warranty issues. Due to the nature of sensors (to sense different physical quantities) and actuators (to output energy in desired ways), most of OEM and supplies tend to choose different fault maturing and clearing strategy for sensors and actuators with different physics nature, such as timer-based, counter-based, and other physical-quantity-based strategies.
2016-04-05
Journal Article
2016-01-1574
Matthew Schwall, Anmol Garg, Jason Shiverick, Matthew Conley
Abstract This paper presents findings based on the examination of time-series tire pressure data. Tire pressure is important to vehicle safety due to its effects on vehicle handling and stability, as well as the impact that inappropriate tire pressure has on tire wear and tire failures. Previous research such as NHTSA’s 2001 Tire Pressure Special Study sampled vehicle populations and recorded tire pressures at a single point in time. Such studies yield important insights into tire pressures on individual vehicles and across the vehicle populations, but cannot provide insights into the behavior of tire pressures over time. The data presented in this paper was measured using the tire pressure monitoring system (TPMS) data from Tesla Model S vehicles. Using Tesla’s on-board diagnostic data logging and remote data retrieval capabilities, the time history of each vehicle’s tire pressures was recorded and fleet-wide data was analyzed.
CURRENT
2016-03-30
Standard
J2735ASN_201603
This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.
CURRENT
2016-03-30
Standard
J2735SET_201603
This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.
2016-03-17
WIP Standard
ARP6412
The scope of the Landing Gear Integrity Programs (LGIP) Aerospace Recommended Practice (ARP) is intended to assist in the safe-life structural integrity management of the landing gear system and subsystems components. In addition, component reliability, availability, and maintainability is included in a holistic LGIP.
2016-03-15
WIP Standard
AIR6411
Provide information and guidance for landing gear operation in cold temperature environment. Covers all operational aspects on ground and in flight. Includes effects on: tires, wheels, brakes, shock strut, seals, and actuation.
2016-03-15
WIP Standard
AS5714
To assist the FAA with the technical update of TSO-C26d to address Electric Brake Actuation, standardize with TSO-C135a and address any remaining concerns with the current document.
2016-03-14
WIP Standard
AS6409
Provide specifications for hydraulic fluids used in landing gear shock struts. Some of this information was previously in AIR5358 however specifications should be in an AS. This new document will contain the appropriate specifications for premixed hydraulic fluid with additives believed to improve fluid performance and reduce friction.
2016-03-14
WIP Standard
AS6410
This document was requested by the FAA to provide a technical update of TSO-C26d to address Electric Brake Actuation, standardize with TSO-C135a and address any remaining concerns with the current technical requirements in AIR5381.
2016-03-11
WIP Standard
ARP6408
The purpose of this SAE Aerospace Recommended Practice (ARP) is to provide a reasonable definition of external hydraulic fluid leakage exhibited by landing gear shock absorbers. The definition will outline normal and excessive leakage that is measureable and routinely encountered in newly assembled refurbished/remanufactured components, leakage during acceptance flights, recently delivered and in-service aircraft.
2016-03-01
Book
Craig Smith
Modern cars are more computerized than ever, with the aim to make driving more convenient. But vehicle technologies haven’t kept pace with today’s more hostile security environment, leaving millions vulnerable to attack. This handbook will give you a deeper understanding of the computer systems and embedded software in modern vehicles. It begins by examining vulnerabilities and providing detailed explanations of communications over the CAN bus and between devices and systems. With an understanding of a vehicle’s communication network, you’ll learn how to intercept data and perform specific hacks to track vehicles, unlock doors, glitch engines, flood communication, and more.
2016-02-09
WIP Standard
J1939/84
The purpose of this Recommended Practice is to verify that vehicles and/or components are capable of communicating a required set of information, in accordance with the diagnostic messages specified in SAE J1939-73, to fulfill the off-board diagnostic tool interface requirements contained in the government regulations cited below. This document describes the tests, methods, and results for verifying diagnostic communications from an off board diagnostic tool (i.e., scan tool) to a vehicle and/or component. SAE members have generated this document to serve as a guide for testing vehicles for compliance with ARB and other requirements for emissions-related on-board diagnostic (OBD) functions for heavy duty engines used in medium and heavy duty vehicles. The development of HD OBD regulations by US EPA and California’s Air Resources Board (ARB) require that diagnostic message services are exercised to evaluate diagnostic communication standardization requirements on production vehicles.
2016-02-09
WIP Standard
J1939/73
SAE J1939-73 Diagnostics Application Layer defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc.
2016-02-01
WIP Standard
J2012
This document supersedes SAE J2012 DEC2007, and is technically equivalent to ISO 15031-6:2010 with the exceptions described in Section 1.2. This document is intended to define the standardized Diagnostic Trouble Codes (DTC) that On-Board Diagnostic (OBD) systems in vehicles are required to report when malfunctions are detected. SAE J2012 may also be used for decoding of enhanced diagnostic DTCs and specifies the ranges reserved for vehicle manufacturer specific usage. This document includes: a. Diagnostic Trouble Code format. b. A description of the standardized set of Diagnostic Trouble Codes and descriptions contained in SAE J2012-DA. The two most significant bytes of a DTC may be decoded according to two different lists; DTC Format Identifier 0x00 and 0x04. c. A description of the standardized set of Diagnostic Trouble Codes subtypes known as Failure Types contained in SAE J2012-DA (applies only when three byte DTCs are used).
CURRENT
2016-01-22
Standard
J1939/73_201601
SAE J1939-73 Diagnostics Application Layer defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc.
Viewing 1 to 30 of 671

Filter