Modern vehicles have multiple electronic control units (ECU) to control various subsystems such as the engine, brakes, steering, air conditioning, and infotainment. These ECUs are networked together to share information directly with each other. This in-vehicle network provides a data opportunity for improved maintenance, fleet management, warranty and legal issues, reliability, and accident reconstruction. Data Acquisition from LD Vehicles Using OBD and CAN is a guide for the reader on how to acquire and correctly interpret data from the in-vehicle network of light-duty (LD) vehicles. The reader will learn how to determine what data is available on the vehicle’s network, acquire messages and convert them to scaled engineering parameters, apply more than 25 applicable standards, and understand 15 important test modes. Topics featured in this book include: • Calculated fuel economy • Duty cycle analysis • Capturing intermittent faults Written by two specialists in this field, Richard P. Walter and Eric P. Walter of HEM Data, the book provides a unique roadmap for the data acquisition user. The authors give a clear and concise description of the CAN protocol plus a review of all 19 parts of the SAE International J1939 standard family. Data Acquisition from LD Vehicles Using OBD and CAN is a must-have reference for product engineers, service technicians fleet managers and all interested in acquiring data effectively from the SAE J1939-equipped vehicles.
Created to elevate expertise in testing, verification, and validation with industry-specific terminology, readers are empowered to navigate the complex world of quality assurance. From foundational concepts to advanced principles, each entry provides clarity and depth, ensuring the reader becomes well-versed in the language of precision. This dictionary is an indispensable companion for both professionals and students seeking to unravel the nuances of testing methodologies, verification techniques, and validation processes. Readers will be equipped with the tools to communicate effectively, make informed decisions, and excel in projects. In addition, references to SAE Standards are included to direct the read to additional information beyond a practical definition. (ISBN 9781468605907, ISBN 9781468605914, ISBN 9781468605921, DOI 10.4271/9781468605914)
Diagnostic Communication with Road-Vehicles and Non-Road Mobile Machinery examines the communication between a diagnostic tester and E/E systems of road-vehicles and non-road mobile machinery such as agricultural machines and construction equipment. The title also contains the description of E/E systems (control units and in-vehicle networks), the communication protocols (e.g. OBD, J1939 and UDS on CAN / IP), and a glimpse into the near future covering remote, cloud-based diagnostics and cybersecurity threats.
This book addresses the various challenges and open questions relating to CAN communication networks. Opening with a short introduction into the fundamentals of CAN, the book then examines the problems and solutions for the physical layout of networks, including EMC issues and topology layout. Additionally, a discussion of quality issues with a particular focus on test techniques is presented. Each chapter features a collection of illuminating insights and detailed technical information supplied by a selection of internationally-regarded experts from industry and academia. Features: presents thorough coverage of architectures, implementations and application of CAN transceiver, data link layer and so-called higher layer software; explains CAN EMC characteristics and countermeasures, as well as how to design CAN networks; demonstrates how to practically apply and test CAN systems; includes examples of real networks from diverse applications in automotive engineering, avionics, and home heating technology.
Battery Fires: Why They Happen and How They Happen was written to assist those interested in this type of incident understand how automotive fires develop, spread and the damage they cause, using both deductive and inductive reasoning. The main focus of the book resides in looking at differences in failure modes between DC and AC systems, general types of battery and electrical failure modes leading to fire, how to interpret electrical fire, determination of the primary failed part, and other skills the investigating engineer will require to perform technical failure mode analysis. However, some fires have consumed the evidence to the point where a determination cannot be made with any degree of certainty. In this instance, evidence will be quite limited, and the analysis will have its limitations and should be included in the discussion as such. In some cases, a “cause undetermined” report is all the evidence will support. Battery Fires: Why They Happen and How They Happen is a unique title which brings together the theory and the practice of correctly evaluating the root causes of unexpected and dangerous automobile fires.
Modern vehicles have electronic control units (ECUs) to control various subsystems such as the engine, brakes, steering, air conditioning, and infotainment. These ECUs (or simply ‘controllers’) are networked together to share information, and output directly measured and calculated data to each other. This in-vehicle network is a data goldmine for improved maintenance, measuring vehicle performance and its subsystems, fleet management, warranty and legal issues, reliability, durability, and accident reconstruction. The focus of Data Acquisition from HD Vehicles Using J1939 CAN Bus is to guide the reader on how to acquire and correctly interpret data from the in-vehicle network of heavy-duty (HD) vehicles. The reader will learn how to convert messages to scaled engineering parameters, and how to determine the available parameters on HD vehicles, along with their accuracy and update rate. Written by two specialists in this field, Richard (Rick) P. Walter and Eric P. Walter, principals at HEM Data, located in the United States, the book provides a unique road map for the data acquisition user. The authors give a clear and concise description of the CAN protocol plus a review of all 19 parts of the SAE International J1939 standard family. Pertinent standards are illuminated with tables, graphs and examples. Practical applications covered are calculating fuel economy, duty cycle analysis, and capturing intermittent faults. A comparison is made of various diagnostic approaches including OBD-II, HD-OBD and World Wide Harmonized (WWH) OBD. Data Acquisition from HD Vehicles Using J1939 CAN Bus is a must-have reference for those interested to acquire data effectively from the SAE J1939 equipped vehicles.
Diesel Engine System Design links everything diesel engineers need to know about engine performance and system design in order for them to master all the essential topics quickly and to solve practical design problems. Based on the author's unique experience in the field, it enables engineers to come up with an appropriate specification at an early stage in the product development cycle. - Links everything diesel engineers need to know about engine performance and system design featuring essential topics and techniques to solve practical design problems - Focuses on engine performance and system integration including important approaches for modelling and analysis - Explores fundamental concepts and generic techniques in diesel engine system design incorporating durability, reliability and optimization theories
In the early part of the 21st century, we find our lives intertwined with a maze of technological wonders. From cell-phones to personal computers, no human being today can escape it. Automobiles are no exception to this rule. With the ever changing emission laws of today, the one constant in the automotive industry is that things always change and will continue to do so. OBD II was designed from the beginning to do so as well. Late model vehicle systems are much more demanding, in both the amount of technology they posses and in the knowledge necessary to repair them. This work was designed to just that, a step-by step diagnostic approach to OBD II systems. It is also written with the State Inspections in mind. This is in direct response to the increasing adoption of OBD II inspections by most States throughout the country. OBD II repair don’t have to be difficult or cumbersome and knowledge is the key to successful OBD II diagnostics and repair. About the Author Mandy Concepcion has worked in the automotive field for over 21 years. He holds a Degree in Applied Electronics Engineering as well as an ASE Master & L1 certification. For the past 16 years he has been exclusively involved in the diagnosis of all the different electronic systems found in today's vehicles. It is here where he draws extensive practical knowledge from his experience and hopes to convey it in his books. Mandy also designs and builds his own diagnostic equipment, DVD-Videos and repair software. Edition 4.0, Table of Contents, Copyright 2004, 2011, All rights reserved TABLE OF CONTENTS Section 1 - Basics of OBD II - What is OBD II? - Why do we need it? The Federal Test Procedure (FTP) - Technical aspects of OBD II. (FF, Monitors, Pending & Current Codes, The Drive Cycle, Re-setting Monitors, etc) - The data link connector - Diagnostic Trouble Code implementation - Resetting Monitors - What are Freeze Frames and how are they useful in diagnostics - A word about misfires - Do I need an OEM scanner or can I get by with an aftermarket scan tool? - Generic vs. Enhanced. What's the difference? why do you need to pull-out both codes? - The vehicle failed OBD II-State Inspection, but is passing a 5 gas emissions test. Why is it? - Resetting fuel trims. It’s not the same procedure for every system - The Diagnostic Executive or Task Manager. What is it? - Bi-Directional control capabilities are revolutionizing the diagnostic process - Diagnosing EVAP leaks. It doesn’t have to be complicated Section 2 - Base-lining the system includes retrieving FF, codes, & monitor status - Freeze Frames information gathering - Monitor status flag - Code Setting Criteria. How and why was the code set? - Freeze Frame and Code Setting Criteria comparison - Dividing the diagnostic process into systems and using the codes to detect system faults - First rule of diagnostics—Know the system you’re working on - System by System outlook - Which Monitors are Incomplete. The need to prove each system without having to run a drive cycle by using the scanner, saving time & money - General Idle PID Snap-Shot Section 3 - INTRODUCTION - OBD-2 Generic PID list - OBD I and OBD II, and general PID analysis - FUEL DELIVERY FAULT DETECTION - TEST # 1 - TEST #2 - TEST #3 - TEST #4 - TEST #5 - RUNNING THE MONITORS IN YOUR MIND USING THE SCANNER Section 4 - Putting it all together. - Principles of diagnostics - Basic Scope Testing and Bi-Directional Control - No-Start, General Diagnostics - The correct decision making process to a sound repair - Don't assume anything or get caught in a particular mind set - Taking all the facts into account
