Fault-tracing Information
Fault-tracing information
Fault-tracing information
Frozen values and counter for diagnostic trouble codes.
Use the diagnostic trouble codes' frozen values as well as the counters, to determine the driving conditions when the problem was detected the first time and how often the problem has occurred. The values show the problem's current status and how intermittent the problem is. Driving conditions may be, e.g., if the engine was running, what speed the vehicle had, or how long the driving distance was.
Counter
The counters are used to determine the problem's status. For general information about the counters, see: Counters, description Description of Counter
Counter 1 indicates the number of drive cycles without fault since the fault was last validated.
If counter 1 is the same as 0, this means that the fault has been detected in this operating cycle (permanent fault). If no troubleshooting or repair has been performed in the vehicle in this driving cycle, the problem is probably in the vehicle.
If counter 1 is over 0, this indicates that the problem has not been detected in this driving cycle (intermittent problem). The problem has existed earlier but is not active right now.
Then check counter 4. Counter 4indicates number of driving cycles with problem since the problem was validated for the first time.
If the number of driving cycles with problems is high, this indicates an intermittent recurring problem, which means greater possibility of regenerating the problem in the workshop.
If the number of driving cycles with problems is low, this indicates an intermittent temporary problem, which means small possibility of regenerating the problem.
Hint: Counter 3 indicates number of driving cycles since first time that the problem occurred. If the value for counter 3 is divided by the value for counter 4, the intensity of the problem is obtained. The higher the value, the higher the problem intensity. A high problem intensity indicates that the malfunction recurs often.
Counter 5 can be used for more exact determination of when the problem occurred. To compare counter 5 for diagnostic trouble codes indicates in which order the diagnostic trouble codes were stored.
5-cyl. non-turbo engines
For model year 1999, only counter 1 and 2 are available.
Frozen values
The frozen values show the driving conditions when the control module detected the problem the first time. Check using the frozen values that the diagnostic trouble code has not been caused accidentally during troubleshooting of the vehicle. If the driving distance is 0 km/miles, this indicates that the problem has occurred at the control modules' start-up of the CAN-net, when reception of a relevant value has not been possible. This also applies to other values that come via the CAN-network. In these cases, counter 5 can be used to determine when the problem was generated.
If the diagnostic trouble code has been caused during this troubleshooting, it may be due to, e.g., disconnected component, too low or high battery voltage, or that some control module has been disconnected.
If the diagnostic trouble code has been stored since before, there has likely been a problem or interference, which has resulted in the control module detecting a problem.
For general information about frozen value, see: Information Information
For information about frozen values.
- Turbo engines and 6-cyl. non-turbo engines: Description of frozen values Me7 Description of Frozen Values Me7
- 5-cyl. non-turbo engines: Frozen values DENSO, description Frozen Values DENSO, Description
Read off the diagnostic trouble code's counter and frozen values by clicking on the symbol for VCT2000. Choose diagnostic trouble code in question.
Continue - DONE
------------------------
DONE - Checking components
-------------------------------------------------
Checking components
Check if other control modules have diagnostic trouble codes (DTCs) for control area network (CAN) faults. If so, perform all troubleshooting according to these diagnostic trouble codes first. Otherwise, continue as follows.
ECM-928C is stored if the engine control module (ECM) does not receive steering wheel module (SWM) information on the cruise control buttons via the CAN network. The diagnostic trouble code is also generated if the information received by the engine control module (ECM) does not match that sent by the steering wheel module (SWM).
- Using VIDA vehicle communication, check that the parameters "Cruise control resume", "Cruise control SET-" and "Cruise control SET+" indicate the correct values. If the buttons work and the information can be read out in the engine control module (ECM), the fault is intermittent. Otherwise the fault is permanent.
Permanent fault
Check whether the steering wheel module (SWM) has stored any diagnostic trouble codes that indicate a fault in the cruise control buttons. Any diagnostic trouble codes that are stored should be fault traced first.
Check whether any other control modules have stored diagnostic trouble codes that indicate that the steering wheel module (SWM) was not transmitting on the CAN network. Any diagnostic trouble codes that are stored should be fault traced first.
Intermittent fault
Check whether the steering wheel module (SWM) has stored any diagnostic trouble codes that indicate a fault in the cruise control buttons. Any diagnostic trouble codes that are stored should be fault traced first.
Check whether any other control modules have stored diagnostic trouble codes that indicate that the steering wheel module (SWM) was not transmitting on the CAN network. Any diagnostic trouble codes that are stored should be fault traced first.
Use the diagnostic trouble codes' frozen values as well as the counters, to determine the driving conditions when the problem was detected the first time and how often the problem has occurred. The values show the problem's current status and how intermittent the problem is. If the trouble code was stored when battery voltage was low and engine speed was close to 0 rpm when the fault occurred, it could indicate that the fault arose when the vehicle was stationary with the ignition on for a long period, thereby draining the battery, or that the fault arose due to battery voltage becoming low when the customer started the engine. At start, battery voltage may be low if the battery has been poorly charged. Check the speed at which the vehicle was travelling when the trouble code was stored as cruise control can only be activated at speeds above 30 km/h (18.6 mph).
For markets where the upgraded software, released during 2006 or later, is available, the solution may be to load the upgraded software. If the frozen values indicate that the diagnostic trouble code was generated due to low battery voltage during or just after engine start, new software is the solution. This is because the new software requires vehicle speed to be greater than 25 km/h (15 mph) for the test to be active.
If upgraded software is not available and the frozen values indicate that the fault occurred when battery voltage was low and engine speed was close to 0 rpm, fault tracing should focus on checking the vehicle's power supply, especially battery charge status.
Hint: Using VIDA vehicle communication, check that the parameters "Cruise control resume", "Cruise control SET-" and "Cruise control SET+" indicate the correct values. To aid fault tracing, use Component specifications when measuring and checking relevant components and use Wiring diagram, Signal descriptionand Breakout boxto measure and control signals to and front the control module or its components.
Remedy as necessary.
Other information
- Checking wiring and terminals Checking Wiring And Terminals
Warning! In order for Electronic throttle module (ETM) to reset any reconfigurations as well as delete internally stored problems, the following must be performed:
- Ignition off, wait three minutes so that the main relay / system relay releases the voltage feed to, among other, Electronic throttle module (ETM).
- Then turn on the ignition and turn it off again.
- Wait another three minutes, but if the electric cooling fan is running you have to wait another two minutes after the cooling fan has stopped, to ensure that Electronic throttle module (ETM) is shut off correctly.
If this is not done correctly, diagnostic trouble codes may remain even after deletion of diagnostic trouble codes as well as any reconfiguration, despite the problem being fixed.
Continue - Verification
-------------------------------------------------
Verification
FAULT FOUND - Fault Found
Attempt New Test - Fault-tracing information
-------------------------------------------------