COUNTERS, DESCRIPTION
| Counter |
|---|
| A useful fault-tracing tool is the Diagnostic Trouble Code (DTC) counter. The control module stores 6 different counters for each Diagnostic Trouble Code (DTC), which describes the occurrence. The counters can be used to determine when and how often a fault has been detected. Using the counters for the Diagnostic Trouble Code (DTC) it is possible to, see if the fault has only been registered during the current operating cycle or whether it has been detected previously. If a fault is intermittent it is possible to determine how intermittent the fault is by studying the values of the different counters. Example: Counter 1 = 15 Counts the number of operating cycles since the fault was last validated. Counter 3 = 69 Counts the number of operating cycles since the fault was first validated. Counter 4 = 1 Counts how many times the fault has occurred since the first time the fault was first validated. Counter 5 = 91764 The counter adds the time in seconds for which the control module has been operating since the fault was first validated and the diagnostic trouble code (DTC) was stored. Counter 6 = 0 The counter adds the time in seconds for which the test, the diagnostic, has run since the fault was first validated and the diagnostic trouble code (DTC) was stored. Counter 7 = 0 The counter adds the time in seconds for which the fault has been validated since the fault was first validated and the diagnostic trouble code (DTC) was stored. In the examples given above, counter 1 gives the number of operating cycles where the diagnostic was run without a fault being detected. Counting takes place from when the fault was last detected. Counter 3 is the total number of operating cycles regardless of whether the diagnostic was run or not. Counter 4 shows the number of operating cycles where the diagnostic detected a fault. Counters 3 and 4 start to count from the first operating cycle after the operating cycle when the fault was first detected. In the example, counter 4 = 1, which means that the fault was detected twice. One can, see that no fault was detected during the relevant operating cycle. Depending on the number of operating cycles and the customer's driving pattern, it can assist in ruling out this control module from the customer's current problems. The counters can help us understand how intermittent the fault can be. If the counters 1 = 0, 3 = 0 and 4 = 0 it indicates that there have not been any operating cycles since the fault was detected and that the fault was probably generated in the workshop. For an operating cycle to be recognized certain requirements may be necessary, for example, increasing the engine coolant temperature. In certain cases ignition on, ignition off and ignition on again are counted as an operating cycle. Counter 5 can be useful if the fault was detected in this operating cycle. The time can be used to determine more exactly when the fault occurred. NOTE: Not all counters need be implemented in a control module, this varies from system to system. The possible counters are described below. |
| NOTE |
|---|
| Not all counters need be implemented in a control module, this varies from system to system. The possible counters are described below. |
| Counter | Function |
|---|
| A (see the graph in (Scheme 803)) Counter 1 | The graph in (Scheme 803)illustrates the time at which a fault occurs. In the illustration the control module has detected a fault in the second cycle. This fault has then occurred a total of 5 times. The counter can be read off for each diagnostic trouble code (DTC) in the control module in which this is implemented. Operating cycles are marked with vertical lines. An operating cycle usually begins at ignition on and finishes when the ignition is switched off. |
| C#1 (see the graph in (Scheme 803)) Counter 2 | Counts the number of operating cycles since the fault was last validated. This information can be used to determine whether the fault is active during the current operating cycle or not. The fault is present now if the value is zero. This counter is also used for most systems to give "Permanent fault" and " Intermittent fault" text messages in VIDA when reading off a diagnostic trouble code (DTC). |
| C#3 (see the graph in (Scheme 803)) Counter 3 | Counts the number of operating cycles since the fault was first validated. When a fault has been validated, the counter will count up by 1 for each subsequent operating cycle. The same as counter C#1 but monitors the number of cycles since the first fault occurred. |
| C#4 (see the graph in (Scheme 803)) Counter 4 | Counts the number of operating cycles in which the fault was validated since it was first validated. Counts the number of times the fault has occurred since the first time. |
| C#5 Counter 5 | The counter assesses the number of seconds the control module has been operating since the fault was first validated and the diagnostic trouble code (DTC) was stored. The time the control module has been operating is only counted when it is active, not in "sleep mode". |
| C#6 Counter 6 | The counter assesses the number of seconds the test (the diagnosis) has been operating since the fault was first validated and the diagnostic trouble code (DTC) was stored. |
| C#7 Counter 7 | The counter assesses the number of seconds the fault has been valid since it was first validated and the diagnostic trouble code (DTC) was stored. |
Scheme 803
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. |
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. |
