Вы находитесь на странице: 1из 7

Capture and readout of on-board electrical system diagnostic data

Brief description of procedure for vehicles with discharged on-board electrical system battery:

vehicles with discharged on-board electrical system battery: A battery sensor (B95) is installed directly at the

A battery sensor (B95) is installed directly at the negative terminal of the battery. The battery sensor measures the voltage,

current, and temperature of the battery and thus rates its condition. The battery sensor has an extremely broad measurement range (1 mA to 1000 A) and a high resolution. This allows quiescent current monitoring to be implemented in the vehicle and Star Diagnosis (Xentry) to read out events. Quiescent current monitoring begins when switching the key in the electronic ignition switch (EZS) control unit to position "0" (ignition OFF, circuit 15C) or when removing the key.

Due to the lack of a time delay in the undervoltage state, be sure to read out the records immediately in case of a he undervoltage state, be sure to read out the records immediately in case of a breakdown and do not change the EZS key position too often.

If the ignition is switched frequently from OFF to ON, the record with important information on the cause of the breakdown can be overwritten.

on the cause of the breakdown can be overwritten. The following parameters lead to creation of

The following parameters lead to creation of a record for quiescent current monitoring:

Quiescent current greater than 50 mA after a run-on time of 75 minutes following ignition OFF, circuit 15C (designation: run- on time exceeded) Battery voltage less than 11.8 V following ignition OFF, circuit 15C (designation: battery voltage below threshold)

ci rcuit 15C (designation: battery voltage below threshold) Due to the extended run-on time (up to
ci rcuit 15C (designation: battery voltage below threshold) Due to the extended run-on time (up to
ci rcuit 15C (designation: battery voltage below threshold) Due to the extended run-on time (up to
ci rcuit 15C (designation: battery voltage below threshold) Due to the extended run-on time (up to
ci rcuit 15C (designation: battery voltage below threshold) Due to the extended run-on time (up to

Due to the extended run-on time (up to 60 minutes), the following special equipment items lead to a higher quiescent current limit value:

With Power tilting/sliding roof, glass version, code 414, quiescent current 125 mA With Tire pressure monitor, code 475, and USA version, code 494, quiescent current 175 mA With Tire pressure monitor, code 475, and USA version, code 494, and Power tilting/sliding roof, glass version, code 414, quiescent current 250 mA

roo f, glass version, code 414, quiescent current 250 mA In these vehicles, a corresponding notice

In these vehicles, a corresponding notice is displayed when initiating the Star Diagnosis (Xentry) function "Behavior of

quiescent current".

04.10.2010

– This printout will not be recorded by the update service. Status: 10 / 2010 –

Page 1 of 7

Check

 

In the XENTRY menu, read out "BSN - Battery sensor (B95)" (picture 3) (work steps 2, 3, and 4)

Entry via "Overall vehicle", "Power supply", "Open expert mode" (pictures 1, 2).

Entry via "Overall vehicle", "Power supply", "Open expert mode" (pictures 1, 2).

Picture 1

vehicle", "Power supply", "Open expert mode" (pictures 1, 2). Picture 1 Picture 2 Picture 3

Picture 2

vehicle", "Power supply", "Open expert mode" (pictures 1, 2). Picture 1 Picture 2 Picture 3

Picture 3

vehicle", "Power supply", "Open expert mode" (pictures 1, 2). Picture 1 Picture 2 Picture 3

04.10.2010

Page 2 of 7

– This printout will not be recorded by the update service. Status: 10 / 2010 –

Check the records in the "Behavior of quiescent current" menu

Entry via "BSN - Battery sensor (B95)", "Actual values", "Behavior of quiescent current" (pictures 4, 5).

Picture 4

of quiescent current" (pictures 4, 5). Picture 4   The last 5 records (picture 5) contain
 

The last 5 records (picture 5) contain important information concerning quiescent current, voltage, odometer reading, and consumer status.

Picture 5

voltage, odometer reading, and consumer status. Picture 5   For each cycle of the EZS key
 
For each cycle of the EZS key from "1" to "0" and back to "1",

For each cycle of the EZS key from "1" to "0" and back to "1", at most one record is created. The measurements in the record are updated every 6 minutes, however.

 

Rows 1 to 3 show the stored quiescent current values (when the wake-up event occurs, the maximum and minimum values for quiescent current).

 

Rows 4 and 5 show the stored voltage values (when the wake-up event occurs and after this behavior).

 

Row 6 shows the odometer reading at the time of the quiescent current event.

 

Rows 7 to 12 show the status for typical consumers.

04.10.2010

Page 3 of 7

– This printout will not be recorded by the update service. Status: 10 / 2010 –

 

Row 13 shows the number of times the quiescent current was exceeded (if the quiescent current varies above and below 50 mA, depending on the special equipment, the number of values exceeding 50 mA is counted).

 

Rows 14 and 15 show the reasons the record was created (If the battery voltage falls below 11.8 V or the run-on time exceeds 75 min with quiescent current exceeding 50 mA, depending on the special equipment).

Check the record applicable to the current odometer reading for the vehicle

Check the record for quiescent current, voltage, and the reason for creating the record (picture 5). In addition, check the consumer status. If a consumer such as low-beam headlights is indicated as "YES" and the battery voltage drops significantly, the customer might be responsible.

 
  Quiescent current > 1.5 A:

Quiescent current > 1.5 A:

Bus keepawake unit may be active. Check the bus keepawake unit detection

 
  Quiescent current < 1.5 A:

Quiescent current < 1.5 A:

Local control unit problem (no bus activity). Localize defective component

Check records in the menu "Bus keepawake unit detection"

Entry via "Control unit view", "CGW [ZGW] - Central gateway", "Actual values", "Bus

Entry via "Control unit view", "CGW [ZGW] - Central gateway", "Actual values", "Bus keepawake unit detection", (pictures 6, 7).

Picture 6

[ZGW] - Central gateway", "Actual values", "Bus keepawake unit detection", (pictures 6, 7). Picture 6

04.10.2010

Page 4 of 7

– This printout will not be recorded by the update service. Status: 10 / 2010 –

Picture 7

Picture 7   Bus keepawake unit detection is in tegrated into the CGW control unit and
 

Bus keepawake unit detection is integrated into the CGW control unit and can accommodate at most 2 entries (last and second-to-last).

 
During a bus idle phase, at most one entry can be created after the set

During a bus idle phase, at most one entry can be created after the set time has expired. A new entry is possible after a new ignition cycle and expiration of the set time.

 
The standard setting activates the bus keepawake unit detection starting 65 minutes after ignition OFF.

The standard setting activates the bus keepawake unit detection starting 65 minutes after ignition OFF. For diagnosis in the workshop, the bus keepawake unit detection can be reduced to 15 minutes, for example, since a bus idle state can be expected after this time.

 
Before the vehicle leaves the workshop, the standard time of 65 minutes must be entered.

Before the vehicle leaves the workshop, the standard time of 65 minutes must be entered.

 

The control unit identified as the bus keepawake unit is recorded in non-volatile memory with the following data:

Date and time of the entryis recorded in non-volatile memory with the following data: Control unit designation CAN bus system assignment

Control unit designationmemory with the following data: Date and time of the entry CAN bus system assignment Check

CAN bus system assignmentdata: Date and time of the entry Control unit designation Check the record applying to the

Check the record applying to the current date

Check the stored entry for the ignition state, consumer status (low beams, hazard warning system, diagnosis) and the listed control units with CAN bus assignment (picture 8).

 
If the listed control units with CAN bus assignment are the same in both entries,

If the listed control units with CAN bus assignment are the same in both entries, check the corresponding control units and replace them if necessary. The following special points must be noted when interpreting the bus keepawake unit:

 

If functions such as "low beams on" are active even after "ignition OFF", the responsible control unit, such as the driver-side SAM control unit, is recorded and the low-beams status set to "active".

 

If more than 4 control units have been recorded, the CAN bus system is extremely unstable and the information is of no use.

 

If there is no entry in the bus keepawake unit detection memory, continue with step 6.

Charge the battery

The battery voltage must exceed 12.2 V for the subsequent quiescent current test, in order to ensure that the quiescent current switch does not open prematurely.

04.10.2010

Page 5 of 7

– This printout will not be recorded by the update service. Status: 10 / 2010 –

Prepare vehicle for quiescent current test

It is possible to carry out a quiescent current test via the battery sensor in the vehicle.

Quiescent current test with current clamp on ground cable

Current clamp:

see GOTIS http://gotis.aftersales.mercedes-benz.com

 
Turn off all consumers. Close the latches for the doors, trunk lid, and engine hood.

Turn off all consumers. Close the latches for the doors, trunk lid, and engine hood. In Keyless-Go vehicles, the transmitter key must be outside the range of Keyless-Go antennas.

 
Quiescent current > 1.5 A to 2.0 A: bus keepawake unit. Identify the bus keepawake

Quiescent current > 1.5 A to 2.0 A: bus keepawake unit. Identify the bus keepawake control unit (for example, disconnect and connect the control units at the CAN potential distributor).

 
Quiescent current < 1.5 A to 2.0 A: local control unit problem (no bus activity).

Quiescent current < 1.5 A to 2.0 A: local control unit problem (no bus activity). Check all circuit 30 and 30g control units and fuses in the driver-side SAM control unit with fuse and relay module, rear SAM control unit with fuse and relay module, and the interior fuse box, by measuring the voltage drop across the fuses, for example.

Brief description of fault diagnosis: quiescent current

04.10.2010

Page 6 of 7

– This printout will not be recorded by the update service. Status: 10 / 2010 –

Brief description of fault diagnosis: quiescent current

START Access via “Overall vehicle", "Power supply", "Expert mode", "Battery sensor" yes
START
Access via “Overall vehicle", "Power supply",
"Expert mode", "Battery sensor"
yes
Record present
in “Behavior of quiescent
current?"
no
Check the saved records applying to the current odometer reading for active consumers (e.g. low-beam
Check the saved records applying to the
current odometer reading for active
consumers (e.g. low-beam headlights)
Negative charge balance (e.g. cabling,
alternator, short-distance driving)
Check in “Electrical
charge throughput”
menu
Is there a
customer error
(e.g. low beams
switched on)
yes
Charge battery
Vehicle is OK
no
Quiescent current
(min./max.) in saved
records > 1.5 A
yes
In the "Diagnosis“, “Control
unit view", "CGW" menu,
check actual values for bus
keepawake unit detection for
last and second-to-last entries
Do more than
two entries in the last or
next-to-last record match?
NOT in the case of
undervoltage
yes
no
no
Battery voltage
>12.2 V (quiescent
current switch
closed)?
no
Charge battery
Check faulty control units and
replace as necessary, to maximum of
4 control units
Vehicle is OK
yes
Run quiescent current test
on ground cable of on-board
electrical system battery
Locate faulty component
or control unit
If CAN system is active
remove control units from
CAN hubs individually
Quiescent current
present
(I > 50 mA)
In the case of a local
control unit problem, check
voltage drop across fuses
yes
Replace located faulty component (control unit)
no
Contact market
support
Vehicle is OK
04.10.2010
Page 7 of 7

– This printout will not be recorded by the update service. Status: 10 / 2010 –

Оценить