Skip to main content

Event Data Recorder (EDR) in Atomotive

Event Data Recorder (EDR)


What is EDR ?

Event data recorder (EDR) means a functionality to record data captured prior to, during, and after an Event.

example : event means any event like crash ,deployment of air bag, or sudden break ect .
Event Data Recorder (EDR) will record the set of sensor data during the event or after or prior event.Set Senor data will vary from one event to other event.




Purpose of EDR?

Storage of specified data in non volatile memory in order to analyse and reconstruct events (no deployment/ deployment events) and also required by Regulation like NHTSA.

  • Analysis necessary for liability reasons concerning the car manufacturer or restraint system supplier or to solve statement contradictions of accident opponents.
  • Collection of statistical crash data for effective crash investigations and
      analysis of safety equipment performance to improve traffic safety.

Event Definitions:

  • Event Start (T0) : Point at which first algorithm is active.
  • Event End (Tend) : Point at which all algorithms are reset and fire sequence is completed.
  • Airbag Deployment (AD) :An Event which causes deployment of an airbag or any inflatable restraint devices.
  • Non-Airbag Deployment Event (NAD) : An Event which causes deployment of one or several restraint devices which do not qualify the Event as Airbag-Deployment.
  • No-Deployment Event (ND): An Event which does not cause deployment of any restraint device.

Event Types 

EDR event type

Event data :

Data elements stored by EDR can be categorised in :

  • Header :  (control-)information about all events stored in NVM (type of event, write protection, record completion status)
Data in Record/Telegram:
  • Environment data:     environment data at start of event (switch states, speed, ignition cycle etc.)
  • Algorithm data:     internal data for all algorithm parts (e.g. Front, Side, Rear, Rollover, ...)
  • Fire control data:     data concerning deployment times and restraint components (fire times, fire counter  etc.)
  •  General data:     general data (disable line status during event, completeness of storage, download time, etc.)
  • ingbuffer data:     data captured during a certain time period (pre/post) (e.g. for sensors (longitudinal, lateral, roll angle), environmental data)

Abbreviations:

  • EDC     - Event Data Controller
  • EDI    - EDR Diagnosis Interface (optional)
  • EDS    - Event Data Storage Manager
  • RGB    - Ringbuffer Module (optional)
  • AIDA    - AB10 Algorithm
  • EDP     - Environment Data Precalculation
  • SEM     - Sensor Management
  • FCL     - Firecontrol Logical
  • SQF     - Squib Firing
  • EEM    - EEPROM Management
  • NVM  - Non Volatile Memory (EEPROM/Data Flash) 

Deployment chain and EDR:

 Event handling:

 

Event data storage:


Event data reporting:

On request of diagnosis service:
EDRDiagnosisInterface (EDI) collects data from according NVM buffer
- w/o filtering
- w/o rearrangement
- w/o recalculation
and dumps in to output buffer.

Comments

Popular posts from this blog

CAN INTERVIEW QUESTIONS

Qualifiers and Modifier in C

RTOS Real time operating system interview questions

CAN INTERVIEW QUESTIONS 2

What is UDS protocol

Memory mapping in c

TOP IOT PLATFORMS