Loading ...
Loading ...
Loading ...
the driver or vehicle owner, for instance, via the
ConnectedDrive account that is used.
Operating data in the vehicle
Control units process data to operate the vehicle.
For example, this includes:
▷ Status messages for the vehicle and its indi‐
vidual components, e.g., wheel rotational
speed, wheel speed, deceleration, transverse
acceleration, engaged safety belt indicator.
▷ Ambient conditions, e.g., temperature, rain
sensor signals.
The processed data is only processed in the ve‐
hicle itself and generally volatile. The data is not
stored beyond the operating period.
Electronic components, e.g. control units and ig‐
nition keys, contain components for storing tech‐
nical information. Information about the vehicle
condition, component usage, maintenance re‐
quirements events or faults can be stored tem‐
porarily or permanently.
This information generally records the state of a
component, a module, a system, or the environ‐
ment, for instance:
▷ Operating states of system components, for
instance, fill levels, tire inflation pressure, bat‐
tery status.
▷ Malfunctions and faults in important system
components, for instance lights and brakes.
▷ Responses by the vehicle to special situa‐
tions such as airbag deployment or engage‐
ment of the driving stability control systems.
▷ Information on vehicle-damaging events.
The data is required to perform the control unit
functions. Furthermore, it also serves to recog‐
nize and correct malfunctions, and helps the ve‐
hicle manufacturer to optimize vehicle functions.
The majority of this data is volatile and is only
processed within the vehicle itself. Only a small
share of data is stored in event or fault memories
based on an event.
When servicing, for instance during repairs, serv‐
ice processes, warranty cases, and quality assur‐
ance measures, this technical information can be
read out from the vehicle together with the vehi‐
cle identification number.
A dealer’s service center or another qualified
service center or repair shop can read out the in‐
formation. The socket for OBD Onboard Diagno‐
sis required by law in the vehicle is used to read
out the data.
The data is collected, processed, and used by
the relevant organizations in the service network.
The data documents technical conditions of the
vehicle, helps with the identification of the fault,
compliance with warranty obligations and quality
improvement.
Furthermore, the manufacturer has product
monitoring duties to meet in line with product lia‐
bility law. To fulfill these duties, the vehicle man‐
ufacturer needs technical data from the vehicle.
The data from the vehicle can also be used to
check customer claims for warranty and guar‐
anty.
Fault and event memories in the vehicle can be
reset when a dealer’s service center or another
qualified service center or repair shop performs
repair or servicing work.
Data entry and data transfer into
the vehicle
General information
Depending on the vehicle equipment, comfort
and individual settings can be stored in the vehi‐
cle and modified or reset at any time.
For example, this includes:
▷ Settings for the seat and steering wheel posi‐
tions.
▷ Suspension and climate control settings.
If necessary, data can be transferred to the en‐
tertainment and communication system of the
vehicle, for instance via smartphone.
Seite 12
NOTES
Information
12
Online Edition for Part no. 01402666865 - VI/19
Loading ...
Loading ...
Loading ...