REPLACING A COMPONENT
The headlamp control module (HCM) has registered an internal fault.
If the fault is intermittent, it has been registered previously but is no longer present. Intermittent faults can be caused by interference upon start of the headlamp control module (HCM) or may be a different type of fault that occurs on different occasions. The fault is evaluated depending on how it occurs. If the problem recurs, replace the headlamp control module (HCM).
In the event of a permanent fault, replace the headlamp control module (HCM).
Remedy as necessary.
- Continue Refer to «INFORMATION»(ref-476788-S12210663422012060500000)
FAULT-TRACING INFORMATION
In case of this defect, troubleshooting is not followed by verification.
The information can be displayed again or the fault-tracing for this fault can be interrupted.
Use the following information and general checks during fault-tracing.
Note. Check that the fuses are intact. For locations, see the instruction manual, cover for fuse box, fuse ratings or similar.
- Check, if possible, relevant functions in the vehicle using buttons/controls/test drives to determine the status of the fault. NOTE: If the vehicle does not show any of the given symptoms in the diagnostic trouble code information (DTC), this may mean that the fault is intermittent or that the control module is not detecting the fault at this moment.
- Use the diagnostic trouble code's frozen values , status identifiers and counter to determine the operating conditions when the fault was detected, the fault's current status and any degree of intermittence of the fault.
- Check and fault-trace according to the fault causes that are specified in the diagnostic trouble code (DTC) information .
- Use VIDA Vehicle communication . Read off the parameters, activate components and functions, carry out quick tests and checking routines for the diagnostic trouble codes to identify the fault.
- Check relevant components according to Component specifications .
- Check relevant signals using wiring diagram , signal specification and breakout box .
Note. More information is available in Design and function .
Remedy as necessary.
Other information
- see «DESCRIPTION OF FROZEN VALUES, HEADLAMP CONTROL MODULE (HCM)»(ref-476788-S07783423882012072600000)
- see «STATUS IDENTIFIER, DESCRIPTION»(ref-494781-S03442634392012081600000)
- see «COUNTERS, DESCRIPTION»(ref-494840-S13893453352012081600000)
- see «DESCRIPTION OF PARAMETERS»(ref-476789-S14036892042012060500000)
- see «LOCATION OF COMPONENTS»(ref-476790-S25565113152012060500000)
- see «SIGNAL SPECIFICATION»(ref-476702-S01175184962012060500000)
- see «CHECKING THE POWER SUPPLY AND GROUND TERMINAL»(ref-476701-S15178040922012060500000)
- see «CHECKING WIRING AND TERMINALS»(ref-476689-S17655503092012060500000)
Repair
- see «HEADLAMP CONTROL MODULE (HCM)»(ref-476710-S36246629092012060500000)
Scheme 6
Scheme 7
Scheme 8
- Continue Refer to «INFORMATION»(ref-476788-S10608941212012060500000)
EXPLANATION
Frozen values are parameter values that are stored when a diagnostic trouble code is generated. Not all parameters can be read out for all diagnostic trouble codes. The parameter values can only be read if they can provide additional information on the prevailing conditions when the code was generated.
TOTAL MILEAGE, VALUE
Measurement range: 0-1,000,000 km
The value indicates the vehicle's total mileage when the Diagnostic Trouble Code (DTC) was generated.
MECU POWER SUPPLY, VALUE
Measurement range: 0 - 63 V
Normal range: 12.0 - 14.5 V
The value indicates the power supply to the central electronic module (CEM) when the diagnostic trouble code was generated.
PASSENGER COMPARTMENT TEMPERATURE, VALUE
Measurement range: -40 till +215 °C
The value indicates the passenger compartment temperature when the diagnostic trouble code was generated.
OUTSIDE TEMPERATURE, VALUE
Measurement range: -40 till +215 °C
The value indicates the outside temperature when the diagnostic trouble code was generated.
POWER SUPPLY MODE, STATUS
The value indicates the status of the power supply mode when the diagnostic trouble code was generated.
Key removed
Key recently removed
Key approved
Ignition off after Accessory position
Accessory position
Accessory position after Ignition on
Ignition on
Running
Start attempt
Signal missing
SPEED, VALUE
Measurement range: 0 to 255 km/h (158 mph).
Indicates speed when the diagnostic trouble code was generated.
STEERING WHEEL ANGLE, VALUE
Measurement range: -780 to +780 °.
Indicates current steering wheel angle.
The normal value when the steering wheel and front wheels point straight ahead is approx. 0°.
In case of this defect, troubleshooting is not followed by verification.
The information can be displayed again or the fault-tracing for this fault can be interrupted.
FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
Use the following information and general checks during fault-tracing.
Note. Check that the fuses are intact. For locations, see the instruction manual, cover for fuse box, fuse ratings or similar.
- Check, if possible, relevant functions in the vehicle using buttons/controls/test drives to determine the status of the fault. NOTE: If the vehicle does not show any of the given symptoms in the diagnostic trouble code information (DTC), this may mean that the fault is intermittent or that the control module is not detecting the fault at this moment.
- Use the diagnostic trouble code's frozen values , status identifiers and counter to determine the operating conditions when the fault was detected, the fault's current status and any degree of intermittence of the fault.
- Check and fault-trace according to the fault causes that are specified in the diagnostic trouble code (DTC) information .
- Use VIDA Vehicle communication . Read off the parameters, activate components and functions, carry out quick tests and checking routines for the diagnostic trouble codes to identify the fault.
- Check relevant components according to Component specifications .
- Check relevant signals using wiring diagram , signal specification and breakout box .
Note. More information is available in Design and function .
Remedy as necessary.
Other information
- see «DESCRIPTION OF FROZEN VALUES, HEADLAMP CONTROL MODULE (HCM)»(ref-476788-S07783423882012072600000)
- see «DESCRIPTION OF STATUS IDENTIFIER»(ref-494840-S18263369932012081600000)
- see «DESCRIPTION OF COUNTER»(ref-494840-S28429254232012081600000)
- see «DESCRIPTION OF PARAMETERS»(ref-476789-S12512746922012060500000)
- see «LOCATION OF COMPONENTS»(ref-476790-S25565113152012060500000)
- see «SIGNAL SPECIFICATION»(ref-476702-S01175184962012060500000)
- see «CHECKING THE POWER SUPPLY AND GROUND TERMINAL»(ref-476701-S15178040922012060500000)
- see «CHECKING WIRING AND TERMINALS»(ref-476689-S17655503092012060500000)
Repair
- see «HEADLAMP CONTROL MODULE (HCM)»(ref-476710-S36246629092012060500000)
- Continue Refer to «INFORMATION»(ref-476788-S03970871252012060500000)
In case of this defect, troubleshooting is not followed by verification.
The information can be displayed again or the fault-tracing for this fault can be interrupted.
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
The headlamp control module (HCM) has registered an internal fault.
If the fault is intermittent, it has been registered previously but is no longer present. Intermittent faults can be caused by interference upon start of the headlamp control module (HCM) or may be a different type of fault that occurs on different occasions. The fault is evaluated depending on how it occurs. If the problem recurs, replace the headlamp control module (HCM).
In the event of a permanent fault, replace the headlamp control module (HCM).
Remedy as necessary.
- Continue Refer to «INFORMATION»(ref-476788-S33656448842012060500000)
In case of this defect, troubleshooting is not followed by verification.
The information can be displayed again or the fault-tracing for this fault can be interrupted.
see FAULT-TRACING
see FAULT-TRACING
IDENTIFYING A CONTROL MODULE IN THE CAN-NETWORK
If the load on the CAN network is too high, this may be due to a control module sending incorrect messages on the CAN network (known as a disruptive control module). The malfunction may also be due to an intermittent short-circuit to voltage or ground in one of the CAN-cables. This results in the control modules on the CAN-network starting to send incorrect messages. The malfunctions can occur without a diagnostic trouble code (DTC) being stored by the control modules. The voltage can be measured between the CAN-cables in order to check the load on the CAN-network.
Note. It is not necessarily the control module(s) that stored the diagnostic trouble code (DTC) that is communicating incorrectly. Incorrect messages can come from any control module in the same section of the CAN-network. However, incorrect communication in one network cannot affect the communication on the other network. In other words, incorrect communication on the LS-CAN cannot disrupt communication on the HS-CAN, and vice versa.
Check the communication/load on the CAN-network by measuring the voltage between #B45 (#C45) and #B58 (#C58). The average value of the voltage shall be approx. 0.5 V (0.4-0.6 V). In case of malfunctioning communication, the voltage is at approx. 0.7 V and above.
To identify which control module is responsible for the incorrect communication, one can disconnect the voltage feed to each control module in turn and re-check the voltage on the CAN-cables. The voltage feed is most easily disconnected by removing the fuse/fuses for the particular control module. Continue until the voltage between the CAN-cables drops to about 0.5 V.
Note. When connecting and disconnecting individual control modules, other diagnostic trouble codes (DTCs) may be stored in certain control modules.
HINT: When a suspected control module is identified, connect and disconnect the voltage feed several times to verify that the malfunction appears and disappears. Turn off the ignition between each check.
Note. Do not cut the voltage to the central electronic module (CEM) unless it is the last control module left to check.
A control module which communicates incorrectly must be replaced. See Repair and installation/Removal, replacement and installation.
Note. Following a malfunction involving control modules that disrupt communication, other control modules may remain in Limp-Home mode (that is, they work but with limited functionality) even after the ignition has been turned off and on a number of times. To remedy this, disconnect and reconnect the battery's minus terminal to restore the control modules to normal function.
- Continue Refer to «VERIFICATION»(ref-476788-S00315390052012060500000)
Scheme 9
- Erase diagnostic trouble codes via Vehicle communication service under function group 0.
- Start the engine and let it run for 10 minutes.
- Read out diagnostic trouble codes via Vehicle communication service under function group 3. Check to, see if the communication diagnostic trouble code has been stored again.
Did the trouble code(s) return?
- YES Refer to «INFORMATION»(ref-476788-S17564108972012060500000)
- NO OKAY: Troubleshooting has been completed.
Verification shows that the fault is no longer present. The diagnostic trouble code (DTC) was probably caused by an intermittent fault.
Fault-tracing for this diagnostic trouble code (DTC) is not followed by a verification.
You can view the information again or exit fault-tracing for this diagnostic trouble code (DTC).
The fault should have been detected and remedied. As this is not the case fault-tracing has failed.
Exit fault-tracing for this diagnostic trouble code (DTC) or make another attempt.
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING
see FAULT-TRACING