Saturday, 28 April 2018

AUTOSAR Architecture

   No comments     
categories: 
AUTOSAR Architecture
Hello all , AUTOSAR stands for AUTomotive Open System Architecture. Autosar architecture is an open source layered software architecture this mainly used automotive Electronic Control Unit(ECU) software development.
AUTOSAR gives a layered top-down structure for software with the relation between the software components.

Autosar Architecture is divided into 3 core layers
1.BSW(basic software )
2.RTE(Runtime Environment)
3.Application/Software Component layer.
The main concept of the standardized ECU software Autosar architecture is the separation of hardware-independent application software and hardware-oriented basic software (BSW) by means of the software abstraction layer RTE (runtime environment). On the upper side of the RTE, this abstraction layer enables the development of OEM-specific and competitive software applications. On the lower side of the RTE, it enables the standardization and OEM-independence of basic software. Further characteristics of the AUTOSAR architecture are the scalability of ECU software for several car lines and variants, the possibility to distribute applications (functional software modules) across ECUs, and the ability to integrate software modules from different sources.
The basic software within the AUTOSAR architecture is further divided into the following layers:
1.Services layers
2.ECU abstraction layers
3.Micro-controller abstraction layers
The separation of the application layer from the basic software, realized by the RTE, includes the control of the data exchange between these layers. This forms the basis for a component-oriented, hardware-independent software structure on the application level, with software components (SWCs) as individual units. Because of their hardware independence, it is thus possible to develop SWCs without specific knowledge of the hardware used or planned, as well as to flexibly relocate existing SWCs to ECUs during development.
Layers  Autosar Architecture

1.Services layers
Services layer is the highest layer of the Basic Software, mostly independent of the microcontroller hardware, responsible for providing the basic BSW functionality to the application software.
Main functions:
Operating system functionality
Vehicle network communication and management service
Memory service (NVRM management )
Diagnostic Service
ECU state management ,mode management
Ect
Task: Provided basic service for application ,RTE and Basic software modules
Properties :
Implementation is uC and ECU independent.
2.ECU abstraction layers
ECU Abstraction Layer is the layer above the MCAL layer which houses the interface components.It mainly contains drivers for external devices.
It offers an API for access to peripheral and devices regardless of their location and their connection to the uC  the drivers for the hardware components outside the micro-controller on the ECU. Its basic responsibility is to make the layer above it independent of the hardware available on the ECU. Its lower interfaces are hardware dependent and the upper interfaces are hardware independent.
Task: Make higher software layers independent of ECU hardware layout.
Properties :
Implementation is uC independent  ,ECU hardware dependent
Upper interface is standardised and uC and ECU hardware independent .
3.Micro-controller abstraction layers
Micro-controller Abastraction layer(MCAL) is the lowest layer in the layered AUTOSAR architecture.
It contains internal drivers, which are software modules with direct access to the uC and internal peripherals, it communicates with the hardware directly. Its basic responsibility is to make the layer above it independent of hardware.
Task: Make higher software layers independent of micro controller .
Properties :
Implementation is uC dependent
Upper interface is standardised and uC independent .


AUTOSAR Introduction

   No comments     
categories: 
AUTOSAR Introduction
Hello all, This my first post related to the Autosar introduction, AUTOSAR (AUTmotive Open System ARchitecture) is a revolutionary milestone in the development of Automotive E/E Systems. The development partnership established by leading OEM’s and Suppliers had defined an open reference architecture for ECU software.

The idea behind AUTOSAR initiative is found in 2003 by Automotive OEM’s and Suppliers to avoid re-developing of similar software components.

Hardware- and software will be widely independent of each other.
Development processes will be simplified. This reduces development time and costs.
Reuse of software increases at OEM as well as at suppliers.This enhances also quality and efficiency.
In traditional software development only two layer one is software other one is hardware as shown in above image, in this method we have to write the software as per OEM requirements and we have to deliver the software to the customer.In this method, rework is more and time for software development also more because  of here we are not following any standard.  After Autosar introduced they  made different layers according to their function.
Uniform Producer Independent System Platform which enables Shorter time to market, Less development effort, More products out of one set of components, Improved quality
AUTOSAR layer model offers
Modular Components with defined interfaces
Hardware Independent Software layer
Transferability of modules
Decoupled Basic Software and Application Components using RTE
AUTOSAR Premium Member 

Conclusion: Above all points are indicating towards a module wise abstracted and robust software which can be reused by any ECU. That is the reason why AUOTSAR has been introduced automotive software development life cycle so that one team has a responsibility to write the specification for the development of ECU and other teams of different expertise can follow these specifications and will develop their software as per standards.
Benefits: Reusability, Choice to get software from different vendors, reduction in complexity, Quality assurance etc

This is the blog you can learn all automotive software and Autosar Architecture , below link to learn Autosar Architecture

Sunday, 5 February 2017

Diagnostic Communication

Diagnostic Communication

 

Communication in Automobiles: 

In-Vehicle Communication is achieved through various means by using different protocols like Communication Manager (COM) etc

Tester Communication could be used for Diagnostics, Application/Calibration, Measurement, Flash Programming .









Friday, 13 January 2017

Vehicle Diagnostics or Automotive Diagnostics

Vehicle Diagnostics or Automotive Diagnostics 

The automobile as we know it was not invented in a single day or a single man. It is a complex machine that has over a century of innovation.
Detecting a failure in this complex machine would be a difficult task. However, most of the vehicles today include ECU (Electronic Control Unit (ECU)), which connected several sensors, it will always monitor the sensor value, located throughout the engine, fuel and wheel speed, exhaust systems. When the ECU in the vehicle detects a fault or a problem, First, a warning light on the dashboard is set, to inform the driver that some problem is there in the vehicle. Second, the code is recorded in the ECUs memory EEPROM so that it can later be retrieved by a technician for repair,That code are DTC codes,


What is Vehicle Diagnostics

Diagnostics, as the word suggests, is to identify the problem or a situation of the vehicle. Whenever the ECU finds a problem, it stores that problem as a Diagnostics Trouble Code (DTC) in the EEPROM for later retrieval. Diagnostic Tools are used to read data (DTC’s) from the EEPROM to analyse the cause of failure

Automotive Diagnostics : 

  • Diagnostics Protocol
  • Diagnostics Session 
  • Diagnostic Service  
 
Diagnostics Protocol :
Protocol refers to a set of rules for communication used to communicate with ECU to diagnostic tool .The protocols which are used for Diagnostics purposes are known as Diagnostics Protocol.
Example :
CAN (Control Area Network),
K-Line,
UDS (Unified Diagnostics Services), 
KWP (Keyword Protocol).


Diagnostics Session:
Each diagnostics service have different timing property,means $22 service Read data by identifier have different timing property,it have limitation of time of work.Different types of diagnostics sessions like Default Session, Extended Diagnostic Session and ECU Programming Session.

When ECU is Switched ON that time ECU is in Default Session,$22 will work only Extended Session that time you have to go Extended Session By sending $10 $03.But  Extended Session has time limit of 100ms after that it will come to Default Session.
 Like this  ECU Programming Session also have time limit and engineering session also have time limits.


 Diagnostic Service:

 Diagnostic Service are different type of service that helps technician to read the diffrent type of data and write the data and analyses the data.It will tell what’s wrong with the vehicle if it is not running or behaving improperly. Diagnosing a vehicle's problem in order to fix or repair a car can be done through a professional automobile diagnostic centre. Diagnostic Service uses the read command for retrieving the information/data from ECU and the write command to write/program the data to the ECU.

Diagnostic addressing:

When communicating with the ECU, the diagnostic tool uses either Physical addressing or Functional addressing method. 

Physical addressing  
Physical addressing  is the kind of addressing where the Diagnostics tool communicates with a single ECU which address you have.

 Functional addressing  is where the Diagnostics tool communicates with multiple ECUs.Hear you will use Massage ID as a address.

 

Thursday, 12 January 2017

What is UDS protocol

   No comments     
categories: 

What is UDS protocol

UDS protocol is the one of the diagnostic protocol.It is widely used in automotive industry.It is codified in ISO 14229-1 standard.UDS protocol helps technician,manufactures,service center,programmers diagnose the problem in ECU.

What is the use of UDS protocol

  • UDS protocol is used to repair the vehicle and get the DTC code.
  • Analysis of vehicle while running and after manufacturing 
  • Research on vehicle systems like ABS,airbag etc
  • Reprogramming the ECU
  • Change the configuration of the ECU.
  • Change the NVM configured values.

 

UDS protocol Service 

Diagnostic and Communications Management

                                                  Request  Response
                                                       ID          ID

Diagnostic Session Control             $10    $50
ECU Reset                                       $11    $51
Security Access                               $27    $67
Communication Control                  $28    $68
Tester Present                                 $3E    $7E
Access Timing Parameters              $83    $C3
Secured Data Transmission            $84    $C4
Control DTC Settings                      $85    $C5
Response On Event                         $86    $C6
Link Control                                    $87    $C7

Data Transmission

Read Data By Identifier                    $22    $62
Read Memory By Address                $23    $63
Read Scaling Data By Identifier       $24    $64
Read Data By Identifier Periodic      $2A    $6A
Dynamically Define Data Identifier  $2C    $6C
Write Data By Identifier                    $2E    $6E
Write Memory By Address                $3D    $7D

Stored Data Transmission

Clear Diagnostic Information           $14    $54
Read DTC Information                      $19    $59


Input / Output Control

Input Output Control By Identifier    $2F    $6F


Remote Activation of Routine

Routine Control                                  $31    $71


Upload / Download

Request Download                             $34    $74
Request Upload                                  $35    $75
Transfer Data                                     $36    $76
Request Transfer Exit                         $37    $77
Request File Transfer                          $38    $78

Sunday, 8 January 2017

On-board diagnostics 2 or OBD2

   No comments     
categories: 

On-board diagnostics 2 or OBD2

    In my previous post i have explained what is ODB? OBD is nothing but it helps the owner and technician to find out the what is problem in vehicle.OBD2 is the advance version of OBD1, OBD-II is the protocol used by all cars built after 1996



   In OBD2 lot of improvement is done compared to OBD1 ,improvement is like standardization,signaling,diagnostics protocols ect. 
 
OBD 2 connector are standardized:
 In OBD 1 Each manufacturer used their own diagnostic link connector (DLC), DLC location, DTC definitions, and procedure to read the DTCs from the vehicle. DTCs from OBD-I cars are often read through the blinking patterns of the 'Check Engine Light' (CEL) or 'Service Engine Soon' (SES) light. By connecting certain pins of the diagnostic connector, the 'Check Engine' light will blink out a two-digit number that corresponds to a specific error condition.
OBD1
OBD1



but OBD2 connector is stanardized all the manufacturer using the same connector .We an use any ODB2 scaning tool to scan the CAR.

OBD2
OBD2


OBD 2 Signal standardization

SAE J1850






ISO 14230 KWP2000


ISO 14230 KWP2000

ISO 14230 KWP2000





ISO 15765 CAN


ISO 15765 CAN

ISO 15765 CAN

  


Standardization on OBD2 protocol: 

  1. UDS unified diagnostic service(CAN-BUS) 

    • ISO 15765-4 CAN (11 bit ID,500 Kbaud)
    • ISO 15765-4 CAN (29 bit ID,500 Kbaud)
    • ISO 15765-4 CAN (11 bit ID,250 Kbaud)
    • ISO 15765-4 CAN (29 bit ID,250 Kbaud) 


  2. ISO14230-4 (KWP2000) 

  3. ISO9141-2 

  4.SAE J1850 VPW 

 5.SAE J1850 PWM

 

 

Sunday, 1 January 2017

What is OBD?

   No comments     
categories: 

What is OBD?

OBD is On-board diagnostic means self-diagnosing and self-reporting problems in the car or vehicle.



When you’re purchasing a vehicle or car , two terms that will come one is OBD1 and OBD2.Nowadays day OBD1 is not coming its in only old vehicle.

For example, if your vehicle have a high-end OBD system(OBD2), and it has a problem, the OBD system will do self-diagnose, or ‘tell’ the car driver or repair technician that what problem is in the car.


The difference between OBD1 and OBD2. With OBD1, the goal was to develop a diagnostics system which focuses on the emission control systems of a vehicle means it will tell emission related information to a requester.

OBD2 is a  improvement to the OBD1. OBD2 has better signalling protocols and messaging formats.It will support all diagnostic protocol like UDS ,KWP2000, SAE J1939.

Feature of OBD2:
  1. 1.standardised trouble codes
  2. 2.Supports diagnostic protocol
  3. 3.portable
  4. 4.plug and play
  5. 5.compact
  6. 6.customizable