Vehicle Communication Information, Phone Module (PHM)

Vehicle Communication Information, Phone Module (PHM)

Description of reading off of extended diagnostic trouble code (DTC) information

Contents
Select type of description:

- Description of frozen values
- Description of status identifier
- Description of counter

DESCRIPTION OF FROZEN VALUES

Explanation
Frozen values are parameter values that are stored when a diagnostic trouble code (DTC) is stored.

Not all parameters can be read off for all diagnostic trouble codes (DTCs). The parameter values can only be read off where they can provide more information about the prevailing circumstances when the diagnostic trouble code (DTC) was stored.

Parameters, value

Global time
The value shows the actual time in minutes when the diagnostic trouble code was generated. The Phone module (PHM) obtains the value from the central electronic module (CEM) via the controller area network (CAN).

Total mileage (km/miles)
The value indicates the total distance the vehicle had travelled when the diagnostic trouble code was generated. The Phone module (PHM) receives the value from the central electronic module (CEM) via the CAN network.

MECU power supply
Measurement range 0 - 63 V.
Normal range: 12.0 - 14.5 V.

The value indicates the supply voltage to the central electronic module (CEM) when the diagnostic trouble code (DTC) was stored.

Passenger compartment temperature
Measurement range: -40 to +215°C.

The value indicates the passenger compartment temperature when the diagnostic trouble code (DTC) was stored.

Engine running
Indicates whether the engine was running when the Diagnostic Trouble Code (DTC) was generated.
No = engine was not running.
Yes = engine was running.

DESCRIPTION OF STATUS IDENTIFIER

Status identifier
There are different status identifiers that can be read out for each diagnostic trouble code (DTC). The control module tests each connection more or less continuously. By reading out the diagnostic trouble code (DTC) and the associated status identifier (which detects the malfunction and stores the DTC), information about the test is obtained. Not all status identifiers need to be implemented in one control module, this varies from system to system. All status identifiers are reset and start counting again each time the control module is powered up and when erasing diagnostic trouble codes (DTCs). The possible status identifiers are described below.

Status identifier: Explanation

SI#01: The malfunction is validated now. Shows if the control module detects the malfunction right now. It is only when the test is in progress that the control module can detect malfunction and generate diagnostic trouble code.

SI#02: The malfunction is validated in the current operating cycle. Shows if the control module has detected the malfunction any time during this operating cycle.

SI#03: Intermittent not yet confirmed diagnostic trouble code.

SI#04: Confirmed diagnostic trouble code.

SI#05: Test status in current and/or earlier operating cycle. Shows if control module has performed test for this diagnostic trouble code in current and/or earlier operating cycle.

SI#06: The malfunction is validated in an earlier operating cycle. Shows if the control module has detected the malfunction any time during an earlier operating cycle.

SI#07: Test status in current operating cycle. Shows if control module has performed test for this diagnostic trouble code in current operating cycle.

SI#08: Request activate warning light/text message. Information about the diagnostic trouble code activates a warning light or text message.

DESCRIPTION OF COUNTER

Counter
There are eight different counters that are stored individually for each diagnostic trouble code (DTC). For an intermittent malfunction, the values of the different counters can be studied to determine how intermittent the malfunction is. All counters do not need to be implemented in one control module, this varies from system to system. The possible counters are described below.

Counter: Function

C#1: Counts the number of operating cycles since the malfunction was last validated. This information can be used to determine whether the malfunction is active during the current operating cycle or not. The malfunction is present now if the value is zero.

C#2: Counts the number of operating cycles since the malfunction was last validated, where test for the diagnostic trouble code was performed without the malfunction being detected and validated. When a test is performed, no malfunction is detected, the counter will count up by 1 for each operating cycle.

C#3: Counts the number of operating cycles since the malfunction was validated the first time . For each completed operating cycle the counter will count up by 1.

C#4: Counts the number of operating cycles in which the malfunction was validated since it was first validated. Counts the number of times the malfunction has occurred since the first time.

C#5: Counts the number of warm-up cycles since the MIL-light has gone off.

C#6: The counter counts the number of internal detections of the malfunction that have been performed for the diagnostic trouble code. When this counter reaches +127, the control module considers that the malfunction is active right now. When counter is at value -127 the malfunction is not active. The value is reset to zero at each new operating cycle. If the value increases toward +127 the control module has detected a malfunction and, for each internal test, the value counts up. When the malfunction is not active, the control module counts down to minimum -127. Value can only be changed when the control module has started the test for the diagnostic trouble code. The increments with which the control module counts up or down the value may vary between control modules.

C#7: Shows maximum value for current operating cycle.

C#8: Shows maximum value for current and/or earlier operating cycle.

Graphs: