Skip to main content

Automotive Diagnostics : An Introduction

Need of Automotive Diagnostics


Diagnostics is not a inevitable part of the vehicle. A vehicle can run and work even if Diagnostic is not present in any of the ECUs. What makes Diagnostics important is it is quite helpful for the modern process of building, configuring, updating vehicles and making them fail safe in case of failures. We are making vehicle to express and talk about them to external world. 
 Diagnostics is giving easy, secured and universally standardized  access to complex electronic and mechanical system for various purposes.  Below are the different functions which are executed smoothly with the help of Automotive Diagnostics implementation in an ECU. 

Programming, Calibrations :
o   Vehicle has too many Software driven Electronic and mechanical Components nowadays.
o   Some components are configured and  calibrated thorough software after a vehicle is built. Hence an external interface is required to program any Programmable ECU inside already integrated vehicle.
o    ECUs are needed to be Programmable to adapt the SW changes over the time even after vehicle is sold out.

·        Diagnostics :

o   A  Vehicle is being a more Complex  Electro-mechanical system. It has in Vehicle network of physical media connecting ECUs, Sensors , Actuator, HW and Mechanical components. 
o    It can happen when vehicle is moving or stationary. It may or may not be diagnosed and rectified mechanically.
o   Failure of any of components could be fatal.
o   Hence there are ways to  diagnose these fatalities by Self Diagnostics, Off Board Diagnostics, OBD.
o   It may or may not be visual or noticeable to User.
o   To know if system has any failures , every instance shall be kept under check for failures and should be acted upon by electronic systems.
o   A moment of failure shall be meaningfully captured by system.  It shall be capable of capturing Vehicle conditions, In vehicle Network conditions, Electronic and mechanical component information, Occurrences of faults and timestamps at the time of failure.
o   This data can be analyzed by experts for fault rectification. This is part of Off Board Diagnostics.   
   
o   In case of failures Vehicle electronics should be capable of avoiding fatalities by taking fail safe actions.
o   Vehicle shall be made safe by fail safe actions by ECUs if the failures are worth to live with. 
o   User should be made aware if anything fails and system shall not to proceed in case failure at fatal.

·        Off Board Diagnostics :
o   Some failures are hidden and cannot be re-covered or identified by system itself.
o   Hence there is a need to interact with them to gather relevant data for problem analysis and rectification of failures.
o   There is a need to control components externally rather than the from vehicle SW and HW for failure  analysis.
o   Need an interface to electronic components inside a vehicle when in case of failure of HW or SW components.


·        On board Diagnostics :
o   Vehicle Power train systems need to follow Government regulations.
o   Continuous monitoring of the power train related systems is mandate by these regulations.
o   Some parameters shall be able to retrieve from vehicle for OBD
o   This is the basic system available in all the vehicles from Model year onward.
o   This can be said a mother of Diagnostic.


Comments

Popular posts from this blog

What is UDS on CAN or Diagnostic on CAN ?

OSI Model and Diagnostics : OSI model has 7 layers and each layer has defined functionality. To understand this you can refer this excellent IEEE  publication. It explains OSI Model for CAN , Ethernet, flexray and MOST.  External reference : http://www.ieee802.org/1/files/public/docs2013/new-tsn-diarra-osi-layers-in-automotive-networks-0313-v01.pdf   So let us understand,  what is this UDS on CAN  ? When a Diagnostic Message formatted  as per ISO 14229 -1 i.e UDS Standard is sent over Controller Network we say Diagnostics Communication is happening as per UDS on CAN. So as per this : Below layers participate in Diagnostic Communication Over CAN :  1. Application Layer :  ISO 14229-1:2013 ROAD VEHICLES — UNIFIED DIAGNOSTIC SERVICES (UDS) — PART 1: SPECIFICATION AND REQUIREMENTS  ISO 14229-3:2012 ROAD VEHICLES — UNIFIED DIAGNOSTIC SERVICES (UDS) — PART 3: UNIFIED DIAGNOSTIC SERVICES ON CAN IMPLEMENTATION (UDSON...

Diagnostic Session : Function 5 - Session Oriented Access to Services

  There are multiple users those need to use UDS protocol for various purposes like Garage person for fault detection, ECU manufacture for Testing activities and development purpose. Also  OEM needs  access to ECU memory for flashing purposes.   UDS services can be categorized in different groups like few services will just read some Data from memory,a few will write or update the data to memory, some will erase/update ECU sw itself , some will control Inputs outs of ECU directly.  So there are chances that any improper usage of UDS service may result in safety issues , security breaches or damage to ECU resources. Hence, it doesn't make sense to give access to all services to everyone. To achieve this UDS has designed some mechanisms like Sessions, Security Authentication, Preconditions. I hope you are aware about what a Diagnostic Session is. Please visit :  https://thevehiclediagnostics.blogspot.com/2020/01/what-is-diagnostic-session.html   if you ...

Diagnostic Session : Function 4 - Synchronize different Diagnostic Processes.

A diagnostic session enables a specific set of diagnostic services and/or functionalities in the server(s). Along with this, we need to focus on the services which are synchronized tightly with the session. Any change in the session is directly interlinked with the functionality of diagnostic services.  As these services are linked to ECU processes (like message transmission, DTC setting and fail safe actions, Security Access) along with session change, these processes need to be aligned. Session change does not have an impact on non-volatile memory.  Lets dive in-depth : Below are the services which are impacted majorly due to session changes in server.  Communication Control - 0x28 Control DTC Setting - 0x85 Response on Event - 0x86 Security Access - 0x27 Let us take an example of Communication Control service (0x28). Communication Control (0x28) service is used for enabling and disabling the normal communication and network management messages of an ECU. It is one...