Scania Truck Transmission Fault Codes


General System Information

The control unit operates quickly and accurately, in accordance with a specific algorithm.

He has no imagination and does not reason. If the control unit detects a failure or any other violation, which is interpreted by it as a deviation from the norm, it immediately responds and generates the appropriate trouble codes. The warning system can generate up to 70 different DTCs. Despite the perfect software, there may be such faults that the control unit will not be able to distinguish from the normal functioning of the system.

In such cases, a fault code is not generated. There is always a certain limit on the completeness of the control system.

The above applies to all types of control units.

Restrictions

Not only real faults generate fault codes. To do this, it is enough to disconnect the electrical plug. wires with electr.

nutrition. This is quite a typical case. The control unit interprets the disconnection of the wire as a fault.

In case of violation of electr. connections may malfunction spontaneously.

However, this fault code will be stored in the memory of the control unit until it is erased. Even if the malfunction is gone, it allows you to later find out which electr. the circuit was malfunctioning and rectified. the cause of this malfunction.

Faults that do not generate DTCs

The following malfunctions do not cause the generation of fault codes: blown fuse (power supply through terminal 15), a gap in the electric. chains of the button of diagnostics, rupture in floor switch circuit break in electr. circuit or a constant signal from the diagnostic scanner, the gap in electr. chains of a motor retarder control unit

(sometimes fault code 14 may be generated, but not necessarily), a break in the electr. circuit of the indicator of the selected gear, blown lamp in the indicator of the selected gear.

TROUBLESHOOTING CODES

DTC 1

Malfunction:

Failure of the memory control unit.

Cause:

The checksum of the contents of the FLASH memory cells does not match the result expected by the block

management.

Notes:

FLASH memory also contains the base program of the control unit.

When the control unit checks whether the FLASH memory is working properly, it does the following.

All addresses of memory cells are added to 1 amount. This amount is then used in the calculation of the control, which should lead to the correct answer. If this is not the case, this DTC will be generated.

Debugg:

Replace the control unit.

 

DTC 2

Malfunction:

Failure of the memory control unit.

Cause:

The checksum of the contents of the EEPROM memory cells does not match the result expected by the block

management.

Notes:

The EERROM memory contains information about the configuration of the control unit.

The configuration determines which parts of the base program will be used for the corresponding vehicle. When the control unit checks whether the EERROM memory is working properly, it does the following.

All values that are important for configuration are added together to a single amount. This amount is then used in the calculation of the control, which should lead to the correct answer. If this is not the case, this DTC will be generated.

Debugg:

Set up the correct configuration in the control unit using a PC. Replace control box

if that doesn't help.

 

DTC 3

Malfunction:

Failure of the memory control unit.

Cause:

The RAM check in the control unit showed that one of the memory cells was malfunctioning.

Notes:

RAM is also the real memory of the control unit.

In it, the control unit performs all its calculations. When the control unit checks whether the RAM memory is working properly, the following occurs.

First, the control unit writes some values to the RAM and then reads the same

values to make sure that they are not confused. If the control unit interprets

any value; as a deviation, a fault code is generated.

Debugg:

Replace the control unit.

 

DTC 4

Malfunction:

Open or short in UX power circuit. Reason: The control unit noticed

that the current consumed on pin 36 (“power and UX”, +24 V) of the control unit is either too low or too high.

Notes:

Sensors, controls and a display receive voltage (“UX power”) from control unit pin 36.

The control unit can detect an electrical break. circuit and short circuit through the power supply circuit UX, as the current consumption will be abnormal. This is an abnormal current on pin 36, which leads to the generation of fault code 4.

Gap in electr. chains: In electr. circuit current is not consumed. Short circuit: In electr. The circuit consumes high amperage.

In order for a malfunction code to be generated, the power consumption must suddenly change, for example, due to loosening the connection. If the fault persists, a fault code is generated every time the control unit tries to activate the UX power supply. High current in electr. UX circuits can be caused by things like short circuits.

in sensors.

Debugg:

Check electr. UX circuit, its wiring and elements.

DTC 5

Malfunction:

Supply failure power supply inside the control unit

Cause:

The control unit was unable to confirm its own internal U15 power supply when the driver turned on the ignition.

Notes:

The control unit began to operate when the power was turned on, even though the U15 power supply could not be confirmed in the control circuit that controls this. When arises

this fault, EEPROM can not save new information. This means that the control unit “forgets” any newly programmed start of the transfer and all newly generated fault codes.

The number of faults is displayed as 1, even if there are several faults. You can operate the car, but it should be repaired as soon as possible, since some

safety features may not be entirely effective.

Debugg:

Replace the control unit.

 

DTC 6

Malfunction:

Failure of the monitoring function inside the control unit.

Cause:

The built-in alarm relay does not work when the control unit starts to work, or the relay in question has already been activated when the driver has switched on the voltage supply to the starter.

(this should not have been).

Notes:

Intervention in one of the built-in security features was detected by the control unit. Each such intervention causes the security relay to initiate an alarm so that fault code 7 is generated. If the security relay is not activated, the power supply is interrupted. supply to all outputs of the control unit. Even the transfer of starting can not be included, making

a / m useless.

Debugg:

Replace the control unit.

 

DTC 14

Malfunction:

The engine speed could not adapt to the correct revs at the moment of switching.

nepredach.

Cause:

The control unit received a message from the EOC, indicating the wrong reaction from the engine, via the data circuit (pins 20 and 38). The engine brakes may have been activated when shifting gears. despite the fact that it was unsolicited by the system

Opticruise.

Notes:

The requested torque exceeds the allowable value for gear changes performed under the control of the engine when the gearbox is in the confirmed neutral position.

This could occur if the transfer is activated when the control unit does not expect it. In this case, the cause could be a break in the selector finger in gearbox. If this fault occurs, the driver will have to use the clutch for each shift.

gears. The text CLU_MODE appears on the display.

Debugg:

First check the sensor signals for the gear positions and then the gearbox itself.

 

DTC 15

Malfunction:

EDC indicates the actual torque, which does not coincide with the requested.

Cause:

When the Opticruise control unit requested a certain torque through the data link circuit (pins 20 and 38), the EDC responded with a confirmation message, which Opticruise would consider as an indication of implausible values.

Notes: The torque requested by the Opticruise system is thus converted into the actual position of the rail in the high pressure pump. The Opticruise control unit continuously checks that each such acknowledgment message from the EDC matches the expected result.

If this fault occurs, the driver will have to use the clutch for each gear change. The text CLU_MOEE appears on the display.

Debugg:

Check if the EDC computer generated any error codes. Check whether the control unit has

EDC is the correct part number. Check electr. connectors and wiring.

Finally, check the position of the control rod in the injection pump.

DTC 5

Malfunction:

Supply failure power supply inside the control unit

Cause:

The power unit turned on the ignition.

Notes:

It was confirmed that the control unit had been turned on. When arises

this fault, EEPROM can not save new information. This is what the generated fault codes have been.

The number of faults is displayed 1, even if there are several faults. You can operate the car, but it should not be repaired as soon as possible, since some

safety features may not be entirely effective.

Debugg:

Replace the control unit.

 

DTC 6

Malfunction:

Failure of the control function.

Cause:

It has been activated for alarm.

(this should not have been).

Notes:

Intervention in one of the control units. So that the fault code 7 is generated. If the security is not activated, the power supply is interrupted. supply to all control units. Can not be included

a / m useless.

Debugg:

Replace the control unit.

 

DTC 14

Malfunction:

At the moment of switching, the engine speed couldn’t be adapted.

nepredach.

Cause:

Received message from the EOC, indicating the wrong reaction from the engine, via the data circuit (pins 20 and 38). The engine brakes may have been activated when shifting gears. despite the fact that it was unsolicited by the system

Opticruise.

Notes:

If the gearbox is in the confirmed position.

It could not be expected. In this case, the finger in the gearbox. If this fault occurs, the driver for each shift occurs.

gears. The text CLU_MODE appears on the display.

Debugg:

Check the gearbox itself.

 

DTC 15

Malfunction:

EDC indicates the actual torque, which does not coincide with the requested.

Cause:

The EDC responded with a confirmation message.

Notes: This has been converted to the high pressure pump. This type of acknowledgment message is received from the EDC.

If this fault occurs, it will be a problem. The text CLU_MOEE appears on the display.

Debugg:

Check if the EDC computer generated any error codes. Check whether the control unit has

EDC is the correct part number. Check electr. connectors and wiring.

Finally, check the position of the injection pump.

DTC 26

Malfunction:

Constant signal from the floor switch for the engine braking program.

Cause:

The control unit has registered that the signal was present on pin 27 for too long.

Notes:

The floor switch cannot remain closed for as long as during normal movement. When this switch is activated, it closes on the +24 V circuit. Keep in mind that

The signal to pin 27 does not always come from the floor switch. The same signal can also be sent by the retarder control unit. If this fault occurs, the control unit is forced to use the engine braking program.

Debugg:

Check floor switch, electr. connectors and wiring. Check saved

Are there any malfunctions in the retarder control unit (if the vehicle is equipped with a retarder)?

 

DTC 27

Malfunction:

Permanent signal from the diagnostics button.

Cause:

The control unit has registered that the signal was present on pin 30 for too long.

Notes:

The diagnostics button cannot remain pressed as long as during normal use. When this button is activated, it is closed to system ground (0 V). If this fault

occurs when the driver turns on the ignition; all fault codes that can be shown on the display will be erased. It may also be impossible to launch a verification program.

Debugg:

Check the diagnostics button, electr. connectors and wiring.

 

DTC 28

Malfunction:

Implausible difference between the speed of the car and the tachograph.

Cause:

The control unit has registered that the difference in frequency between the signals going to the pins 31 and 49 (which together form the frequency inside the control unit) and the signal going to the pin

32 was too big.

Notes:

The difference between the signal from the inductive speed sensor on the KP secondary shaft and the tachograph signal from the instrument panel was more than acceptable.

Debugg:

Check the speed sensor on the KP secondary shaft, tachograph signal, electr. connectors and

electrical wiring.

 

DTC 31

Malfunction:

Bad contact or loss of signal, frequency sensor for vehicle speed.

Cause:

The control unit has registered that the signals on pin 31 and / or on pin 49 were too irregular.

Notes:

The speed signal from the inductive speed sensor on the secondary shaft of the gearbox has changed more than is allowed. In order for the control unit to register this fault, the frequency

rotation must exceed a certain limit value.

Debugg:

Check the speed sensor on the KP secondary shaft, electr. connectors and wiring.

 

DTC 34

Malfunction:

Open or short circuit in electr. circuit frequency sensor for speed and / m.

Cause:

The current strength is too low or too high outside pin 31 and / or pin 49.

Notes:

The fault may be due to an open circuit in the wiring or directly in the sensor

or due to a short circuit of the wire to earth of the chassis or a +24 V circuit. The control unit does not detect that the sensor in question is connected.

Debugg:

Check the speed sensor on the KP secondary shaft, electr. connectors and wiring.

 

DTC 36

Malfunction:

Moving forward on the left side when shifting gears is requested but not confirmed.

Cause:

The lack of confirmation of the longitudinal advance (pin 43) on the left side (pin 42), despite several attempts to activate the email. magn. valves that let in compressed air.

Notes:

The control unit counts own attempts of a gear change, and also attempts of the driver.

Debugg:

First inspect the air hoses connected to the el. magn. valves, and make sure the valves get air at the right pressure. Then verify that the confirmation signals from the Hall sensor have arrived as directed. Check email magn. longitudinal valves forward and transverse to the left, as well as electr. connectors and wiring.

DTC 37

Malfunction:

Moving back on the left side when shifting gears is requested but not confirmed.

Cause:

The lack of confirmation of the longitudinal course back (pin 6) on the left side (pin 42), despite several attempts to activate the email. magn. valves that let in compressed air.

Notes:

The control unit counts own attempts of a gear change, and also attempts of the driver.

Debugg:

First inspect the air hoses connected to the el. magn. valves, and make sure the valves get air at the right pressure. Then verify that the confirmation signals from the Hall sensor have arrived as directed. Check email magn. longitudinal backward and transverse left valves, atazh e electr. connectors and wiring.

 

Fault code 38

Malfunction:

Moving forward in a central position when shifting gears is requested but not confirmed.

Cause:

The lack of confirmation of the longitudinal advance (pin 43), despite several attempts to activate the email. magn. valves that let in compressed air.

Notes:

The control unit counts own attempts of a gear change, and also attempts of the driver.

Debugg:

First inspect the air hoses connected to the el. magn. valves and make sure

that the valves get air at the right pressure. Then verify that the confirmation signals from the Hall sensor have arrived as directed. Check email magn. valve longitudinal forward, electr. connectors and wiring.

 

DTC 39

Malfunction:

Moving back to the center position when shifting gears requested but not confirmed.

Cause:

The lack of confirmation of the longitudinal course back (pin 6), despite several attempts to activate the email. magn. valves that let in compressed air.

Notes:

The control unit counts own attempts of a gear change, and also attempts of the driver.

Debugg:

First inspect the air hoses connected to the el. magn. valves and make sure

that the valves get air at the right pressure. Then verify that the confirmation signals from the Hall sensor have arrived as directed. Check email magn. valve backwards, electr. connectors and wiring.

 

DTC 40

Malfunction:

Moving forward on the right side when shifting gears is requested but not confirmed.

Cause:

The lack of confirmation of the longitudinal advance (pin 43) on the right side (pin 24), despite several attempts to activate the email. magn. valves that let in compressed air.

Notes:

The control unit counts own attempts of a gear change, and also attempts of the driver.

Debugg:

First inspect the air hoses connected to the el. magn. valves, and make sure the valves get air at the right pressure. Then verify that the confirmation signals from the Hall sensor have arrived as directed. Check email magn. longitudinal forward and lateral valves to the right, as well as electr. connectors and wiring.

 

DTC 41

Malfunction:

Moving back on the right side when shifting gears is requested but not confirmed.

Cause:

The lack of confirmation of the longitudinal movement back (pin 6) on the right side (pin 24), despite several attempts to activate the email. magn. valves that let in compressed air.

Notes:

The control unit counts own attempts of a gear change, and also attempts of the driver.

Debugg:

First inspect the air hoses connected to the el. magn. valves and make sure

that the valves get air at the right pressure. Then verify that the confirmation signals from the Hall sensor have arrived as directed. Check email magn. longitudinal backward and lateral valve to the right, as well as electr. connectors and wiring.

 

DTC 42

Malfunction:

Moving left when shifting gears requested but not confirmed.

Cause:

The lack of confirmation of the lateral course to the left (pin 42), despite several attempts to activate the email. magn. valves that let in compressed air.

Notes:

The control unit counts own attempts of a gear change, and also attempts of the driver.

Debugg:

First inspect the air hoses connected to the el. magn. valves and make sure

that the valves get air at the right pressure. Then verify that the confirmation signals from the Hall sensor have arrived as directed. Check email magn. the valve of the cross course to the left, and also elektr. connectors and wiring.

DTC 43

Malfunction:

Moving to the right when shifting gears requested but not confirmed.

Cause:

The lack of confirmation of the lateral course to the right (pin 24), despite several attempts to activate the email. magn. valves that let in compressed air.

Notes:

The control unit counts own attempts of a gear change, and also attempts of the driver.

Debugg:

First inspect the air hoses connected to the el. magn. valves and make sure

that the valves get air at the right pressure. Then verify that the confirmation signals from the Hall sensor have arrived as directed. Check email magn. valve of the cross course to the right, its electr. connectors and wiring.

 

DTC 44

Malfunction:

Movement in the transverse direction towards the center position when shifting gears is requested but not confirmed.

Cause:

The control unit has detected that a confirmation signal for a lateral stroke to the left (pin 42) or a lateral stroke to the right (pin 24) is retained.

Notes:

When the confirmation signal for the neutral position in the longitudinal course exceeds 10 V and no electric. magn. the valve is not activated, the timer starts and runs until the signals

Confirmations for lateral travel do not disappear. A fault code is generated if the timer does not stop within a predetermined period.

Debugg:

First inspect the air hoses connected to the el. magn. valves and make sure

that the valves get air at the right pressure. Then verify that the confirmation signals from the Hall sensor have arrived as directed. Check email issue magn. valves of the cross course to the left and to the right, and also returnable springs, elektr. connectors and wiring.

 

Fault code 45

Malfunction:

Loss of confirmation for a move ahead.

Cause:

The control unit has registered that a confirmation signal on pin 43 has suddenly disappeared.

Notes:

In order for the control unit to check whether the signal has been lost, you must perform a complete gear shift sequence. 5 seconds after the control unit has received

acknowledging that the gear shift in question has been completed, it begins to determine whether the acknowledgment signal continues to be received as directed. The control unit checks this as long as it requests the KP to perform the next gear shift.

A fault code will be generated if the gear is popping up mechanically.

Debugg:

Check Hall sensor, electr. connectors and wiring.

 

DTC 46

Malfunction:

Loss of confirmation for a move back.

Cause:

The control unit has registered that a confirmation signal on pin 6 has suddenly disappeared.

Notes:

In order for the control unit to check whether the signal has been lost, you must perform a complete gear shift sequence. 5 seconds after the control unit has received

acknowledging that the gear shift in question has been completed, it begins to determine whether the acknowledgment signal continues to be received as directed. The control unit checks this as long as it requests the KP to perform the next gear shift.

A fault code will be generated if the gear is popping up mechanically.

Debugg:

Check Hall sensor, electr. connectors and wiring.

 

Fault code 47

Malfunction:

Loss of lateral confirmation to the right.

Cause:

The control unit has registered that a confirmation signal on pin 24 has suddenly disappeared.

Notes:

In order for the control unit to check whether the signal has been lost, you must perform a complete gear shift sequence. 5 seconds after the control unit has received

acknowledging that the gear shift in question has been completed, it begins to determine whether the acknowledgment signal continues to be received as directed. The control unit checks this as long as it requests the KP to perform the next gear shift.

A fault code will be generated if the gear is popping up mechanically.

Debugg:

Check Hall sensor, electr. connectors and wiring.

DTC 48

Malfunction:

Loss of confirmation of the lateral course to the left.

Cause:

The control unit has registered that a confirmation signal on pin 42 has suddenly disappeared.

Notes:

In order for the control unit to check whether the signal has been lost, you must perform a complete gear shift sequence. 5 seconds after the control unit has received

acknowledging that the gear shift in question has been completed, it begins to determine whether the acknowledgment signal continues to be received as directed. The control unit checks this as long as it requests the KP to perform the next gear shift.

A fault code will be generated if the gear is popping up mechanically.

Debugg:

Check Hall sensor, electr. connectors and wiring.

 

DTC 49

Malfunction:

Loss of confirmation of neutral position.

Cause:

The control unit has registered that the confirmation signal on pin 7 has suddenly disappeared.

Notes:

In order for the control unit to check whether the signal has been lost, you must perform a complete gear shift sequence. 5 seconds after the control unit has received

acknowledging that the gear shift in question has been completed, it begins to determine whether the acknowledgment signal continues to be received as directed. The control unit checks this as long as it requests the KP to perform the next gear shift.

A fault code will be generated if the gear is popping up mechanically.

Debugg:

Check Hall sensor, electr. connectors and wiring.

 

DTC 50

Malfunction:

No confirmation of a neutral position.

Cause:

The control unit did not receive a confirmation signal on pin 7, confirming that the requested relocation of the gear change was executed.

Notes:

When email is activated magn. valve for neutral position; a timer is started, which stops when the confirmation signal voltage for the neutral position exceeds

10 V. A fault code is generated if the timer does not stop within a predefined period.

This DTC can be generated only when the speed of the vehicle exceeds 5 km / h or when the clutch pedal is fully depressed.

Debugg:

Check the control cylinders, el. magn. valve for neutral position, line is compressed,

air, Hall sensor, electr. connectors and wiring.

 

DTC 51

Malfunction:

Permanent signal to confirm the neutral position.

Cause:

The control unit has registered that a confirmation signal was present on pin 7 for too long.

Notes:

The confirmation signal should not be stored for too long after a request has been made for a longitudinal advance or a longitudinal reverse. This DTC may not be generated when a gearbox is jammed; this can occur in very cold weather.

Debugg:

Check the control cylinders, el. magn. valves, compressed air lines, Hall sensor, electr. connectors and wiring.

DTC 52

Malfunction:

Uncharacteristic acknowledgment (improbable gear selection).

Cause:

Simultaneous confirmation from multiple programs.

Notes:

The signals are implausible because the Hall sensor and the confirmation switch should only be capable of acknowledging one shift movement at the same time.

Any of the following confirmations arrived at the same time. Time: confirmation of neutral position and moving forward (pin 7 and pin 43), confirmation of neutral position and moving back (pin 7 and pin 6), confirmation of moving forward and backward (pin 43 and pin 6), confirmation of movement to the right and left (pin 24 and pin 42), confirmation of the lower and upper rows of the multiplicator (pin 41 and pin 5), confirmation of the lower and upper rows of the divider (pin 4 and pin 23).

Debugg:

Check the Hall sensor, confirmation switches, electr. connectors and wiring.

 

DTC 53

Malfunction:

Movement in the direction of the upper range of the range dial during gear changes requested but not confirmed.

Cause:

No signal on pin 41.

Notes:

No confirmation

the bottom row of the demultiplicator, despite several attempts to activate email. magn. valves that let in compressed air. Each shift attempt, in order for it to be calculated, should take a certain amount of time.

Debugg:

Check control cylinders, contact confirmation, email. magn. valve of the lower row of the range multiplier, line compressed, air, electr. connectors and wiring.

 

DTC 54

Malfunction:

Movement in the direction of the upper range of the range dial during gear changes requested but not confirmed.

Cause:

No signal on pin 5.

Notes:

Lack of confirmation of the top row of the range-switch, despite several attempts to activate email. magn. valves that let in compressed air. Every attempt to switch

transmission, in order for it to be calculated, must take a certain amount of time.

Debugg:

Check the control cylinders, confirmation switch, email. magn. top row valve

range, line compressed, air, electr. connectors and wiring.

 

DTC 55

Malfunction:

Moving in the direction of the lower stage of the divider when shifting gears requested but not

confirmed.

Cause:

No signal on pin 4.

Notes:

The lack of confirmation of the lower stage of the divider, despite several attempts to activate the email. magn. valves that let in compressed air.

Each shift attempt, in order for it to be calculated, should take a certain amount of time.

Debugg:

Check the control cylinders, confirmation switch, email. magn. bottom stage valve

divider, line compressed, air, electr. connectors and wiring.

 

Trouble code 56

Malfunction:

Movement in the direction of the upper divider stage when changing gears is requested but not

confirmed.

Cause:

No signal on pin 23.

Notes:

Lack of confirmation of the upper divider stage, despite several attempts to activate the email. magn. valves that let in compressed air.

Each shift attempt, in order for it to be calculated, should take a certain amount of time.

Debugg:

Check control cylinders, contact confirmation, email. magn. valve top stage divider, line compressed, air, electr. connectors and wiring.

 

DTC 57

Malfunction:

The lack of confirmation of the bottom row of the range.

Cause:

The control unit has registered that a confirmation signal on pin 41 has suddenly disappeared.

Notes:

In order for the control unit to check whether the signal has been lost, you must perform a complete gear shift sequence. 5 seconds after the control unit has received

acknowledging that the gear shift in question has been completed, it begins to determine whether the acknowledgment signal continues to be received as directed. The control unit checks this as long as it requests the KP to perform the next gear shift.

A fault code will be generated if the gear is popping up mechanically.

Debugg:

Check the confirmation switch, electr. connectors and wiring.

DTC 58

Malfunction:

No confirmation of the upper range of the range.

Cause:

The control unit has registered that a confirmation signal on pin 5 has suddenly disappeared.

Notes:

In order for the control unit to check whether the signal has been lost, you must complete a complete gearshift sequence. 5 seconds after the control unit has received

acknowledging that the gear shift in question has been completed, it begins to determine whether the acknowledgment signal continues to be received as directed. The control unit checks this as long as it requests the KP to perform the next gear shift.

A fault code will be generated if the gear is popping up mechanically.

Debugg:

Check the confirmation switch, electr. connectors and wiring.

 

DTC 59

Malfunction:

The lack of confirmation of the lower stage divider.

Cause:

The control unit has registered that a confirmation signal on pin 4 has suddenly disappeared.

Notes:

In order for the control unit to check whether the signal has been lost, you must perform a complete gear shift sequence. 5 seconds after the control unit has received

acknowledging that the gear shift in question has been completed, it begins to determine whether the acknowledgment signal continues to be received as directed. The control unit checks this as long as it requests the KP to perform the next gear shift.

A fault code will be generated if the gear is popping up mechanically.

Debugg:

Check the confirmation switch, electr. connectors and wiring.

 

DTC 60

Malfunction:

Lack of confirmation of the upper divider.

Cause:

The control unit has registered that a confirmation signal on pin 23 has suddenly disappeared.

Notes:

In order for the control unit to check whether the signal has been lost, you must perform a complete gear shift sequence. 5 seconds after the control unit has received

acknowledging that the gear shift in question has been completed, it begins to determine whether the acknowledgment signal continues to be received as directed. The control unit checks this as long as it requests the KP to perform the next gear shift.

A fault code will be generated if the gear is popping up mechanically.

Debugg:

Check the electronic confirmation switch. connectors and wiring.

 

DTC 61

Malfunction:

On el. magn. longitudinal valve forward voltage is applied when this should not be.

Cause:

The voltage was applied to the output of the control unit for PLN. magn. longitudinal valve forward, although the control unit did not request it.

Notes:

A fault code will be generated if the output of the control unit for the email in question. magn. The valve received a voltage for an incorrect reason, such as a short circuit on a +24 V circuit (for example, in electrical wiring).

Otherwise, there is a fault directly in the control unit.

Debugg:

Disconnect the wire from pin 3 and measure the signal voltage with a multimeter. Then

check the condition of the electr. connectors and electrical wiring.

 

DTC 62

Malfunction:

On el. magn. longitudinal valve back pressure enters when this should not be.

Cause:

The voltage was applied to the output of the control unit for el. magn. longitudinal valve back, although the control unit did not request it.

Notes:

A fault code will be generated if the output of the control unit for the email in question. magn. The valve received a voltage for an incorrect reason, such as a short circuit on a +24 V circuit (for example, in electrical wiring).

Otherwise, there is a fault directly in the control unit.

Debugg:

Disconnect the wire from pin 22 and measure the signal voltage with a multimeter. So

check the condition of the electr. connectors and electrical wiring.

 

DTC 63

Malfunction:

In the chain email. magn. the neutral valve has voltage, while it must be

absent.

Cause:

The voltage was applied to the output of the control unit for el. magn. neutral valve, although the control unit did not request this.

Notes:

A fault code will be generated if the output of the control unit for the email in question. magn. The valve received a voltage for an incorrect reason, such as a short circuit on a +24 V circuit (for example, in electrical wiring).

Otherwise, there is a fault directly in the control unit.

Debugg:

Disconnect the wire from pin 40 and use a multimeter to measure the signal voltage. So

check the condition of the electr. connectors and electrical wiring.

Trouble code 64

Malfunction:

In the chain email. magn. The valve of the lower range of the demultiplicator has voltage, while it must be absent.

Cause:

The voltage was applied to the output of the control unit for el. magn. lower range valve range valve, although the control unit did not request this.

Notes:

A fault code will be generated if the output of the control unit for the email in question. magn. The valve received a voltage for an incorrect reason, such as a short circuit on a +24 V circuit (for example, in electrical wiring).

Otherwise, there is a fault directly in the control unit.

Debugg:

Disconnect

wire from pin 39 and use a multimeter to measure the signal voltage. Then check the condition of the electr. connectors and electrical wiring.

 

DTC 65

Malfunction:

Open or short circuit in electr. chain e. magn. valve longitudinal advance.

Cause:

The current on the control unit pin 3 is too low or too high.

Notes:

When activated email. magn. longitudinal valve forward, the control unit can register the following: The rupture in electr. chains: In electr. circuit current is not consumed. Short circuit:

current too high in electr. chains.

In order for a malfunction code to be generated, the power consumption must suddenly change, for example, due to loosening the connection. If the fault persists, a fault code is generated every time the control unit tries to activate the corresponding email. magn. valve. High power can be caused by such things as a short circuit in the winding of the electric coil. magn. valve.

Debugg:

Check email magn. valve longitudinal forward, electr. connectors and wiring.

 

DTC 66

Malfunction:

Open or short circuit in electr. chain e. magn. longitudinal valve back.

Cause:

Too low or too high current on the pin 22 of the control unit.

Notes:

When activated email. magn. valve longitudinal back, the control unit can register the following: The gap in the electr. chains: In electr. circuit current is not consumed. Short circuit:

current too high in electr. chains. In order for a fault code to be generated,

power consumption should suddenly change, for example, due to weakening of the connection. If the fault persists, a fault code is generated every time the control unit tries to activate the corresponding email. magn. valve. High power can be caused by such things as a short circuit in the winding of the electric coil. magn. valve.

Debugg:

Check email magn. valve backwards, electr. connectors and wiring.

 

DTC 67

Malfunction:

Open or short circuit in electr. chain e. magn. valve lateral to the right.

Cause:

Too low or too high current on the pin 17 of the control unit.

Notes:

When activated email. magn. valve of the lateral stroke to the right; the control unit can register the following: Gap in electr. chains: In electr. circuit current is not consumed. Short circuit:

current too high in electr. chains.

In order for a malfunction code to be generated, the power consumption must suddenly change, for example, due to loosening the connection. If the fault persists, a fault code is generated every time the control unit tries to activate the email again. magn. valve.

High power can be caused by such things as a short circuit in the winding of the electric coil. magn. valve.

Debugg:

Check email magn. valve of the cross course to the right, its electr. connectors and wiring.

 

DTC 68

Malfunction:

Open or short circuit in electr. chain e. magn. valve of the cross course to the left.

Cause:

Too low or too high current on the pin 53 of the control unit.

Notes:

When activated email. magn. valve of the lateral course to the left; the control unit can register the following: Gap in electr. chains: In electr. circuit current is not consumed. Short circuit:

current too high in electr. chains.

In order for a malfunction code to be generated, the power consumption must suddenly change, for example, due to loosening the connection. If the fault persists, a fault code is generated every time the control unit tries to activate the corresponding email. magn. valve. High power can be caused by such things as a short circuit in the winding of the electric coil. magn. valve.

Debugg:

Check email magn. valve of the cross course to the left, its electr. connectors and wiring.


DTC 69

Malfunction:

Open or short circuit in electr. chain e. magn. neutral valve.

Cause:

Too low or too high current on the control unit pin 40.

Notes:

When activated email. magn. neutral valve, the control unit can register the following:

Gap in electr. chains: In electr. circuit current is not consumed. Short circuit: current too high in electr. chains. In order for a fault code to be generated, the power consumption must

suddenly change, for example due to weakening of the joint. If the fault persists, a fault code is generated every time the control unit tries to activate the corresponding email. magn. valve. High power can be caused by such things as a short circuit in the winding of the electric coil. magn. valve.

Debugg:

Check email magn. neutral valve, its electr. connectors and wiring.

 

DTC 70

Malfunction:

Open or short circuit in electr. chain e. magn. valve bottom row range.

Cause:

Too low or too high current on the pin 39 of the control unit.

Notes:

When activated email. magn. valve of the lower range of the range-changer, the control unit can register the following: Gap in electr. chains: In electr. circuit current is not consumed. A short

short circuit: current too high in electr. chains. In order for a malfunction code to be generated, the power consumption must suddenly change, for example, due to loosening the connection.

If the fault persists, a fault code is generated every time the control unit tries to activate the corresponding email. magn. valve. High power can be caused by such things as a short circuit in the winding of the electric coil. magn. valve.

Debugg:

Check email magn. bottom range valve, electr. connectors and wiring.

 

DTC 71

Malfunction:

Open or short circuit in electr. chain e. magn. valve top row range.

Cause:

Too low or too high current on the pin 54 of the block

management.

Notes:

When activated email. magn. valve of the upper row of the range-converter, the control unit can register the following: Gap in electr. chains: In electr. circuit current is not consumed. A short

short circuit: current too high in electr. chains. In order for a malfunction code to be generated, the power consumption must suddenly change, for example, due to loosening the connection.

If the fault persists, a fault code is generated every time the control unit tries to activate the corresponding email. magn. valve. High power can be caused by such things as a short circuit in the winding of the electric coil. magn. valve.

Debugg:

Check email magn. top range valve range, electr. connectors and wiring.

 

DTC 72

Malfunction:

Open or short circuit in electr. chain e. magn. valve bottom stage divider.

Cause:

Too low or too high current on the pin 2 of the control unit.

Notes:

When activated email. magn. valve lower stage divider control unit can register

the following: Gap in electr. chains: In electr. circuit current is not consumed. Short circuit: current too high in electr. chains. In order for a malfunction code to be generated, the power consumption must suddenly change, for example, due to loosening the connection.

If the fault persists, a fault code is generated every time the control unit tries to activate the corresponding email. magn. valve. High power can be caused by such things as a short circuit in the winding of the electric coil. magn. valve.

Debugg:

Check email magn. valve lower stage divider, electr. connectors and wiring.

 

DTC 73

Malfunction:

Open or short circuit in electr. chain e. magn. valve top stage divider.

Cause:

Too low or too high current on the pin 18 of the control unit.

Notes:

When activated email. magn. valve top stage divider, the control unit can register

the following: Gap in electr. chains: In electr. circuit current is not consumed. Short circuit: current too high in electr. chains. In order for a malfunction code to be generated, the power consumption must suddenly change, for example, due to loosening the connection.

If the fault persists, a fault code is generated every time the control unit tries to activate the corresponding email. magn. valve. High power can be caused by such things as a short circuit in the winding of the electric coil. magn. valve.

Debugg:

Check email magn. valve top stage divider, electr. connectors and wiring.

DTC 75

Malfunction:

Malfunction in the power supply to the control unit.

Cause:

The control unit has found that the supply of electr. There was no power supply at the terminal when the driver turned off the ignition.

Notes:

The control unit was turned off sequentially several times, not having the ability to store this data in EEPRОМ. This may be due to the fact that the control unit was turned off without connecting to it the supply of power through terminal 1) 30. This may also be because the control unit was subjected to serious interference, which caused its built-in security functions to switch and re-launch it again.

Debugg:

Check fuse for electr. power supply circuit for Opticruise control unit, electr. connectors and wiring.

 

DTC 76

Malfunction:

EDC can not give a reliable value for the position of the gas pedal.

Cause:

The control unit received a message from the EDC via the data exchange circuit (pins 20 and 38), indicating that the value from the potentiometer of the gas pedal position sensor is not typical.

Notes:

It is unlikely that the data exchange circuit is faulty. Otherwise, the control unit would generate another fault code (fault code 82 or 83).

Debugg:

Check for the presence of fault codes stored in the memory of the EEC control unit.

 

DTC 77

Malfunction:

EDC cannot give a reliable value for the current engine speed.

Cause:

The control unit received a message from EDC via the data exchange circuit (pins 20 and 38), indicating that the value from the engine speed sensor is not typical.

Notes:

It is unlikely that the data exchange circuit is faulty. Otherwise, the control unit would generate another fault code (fault code 82 or 83).

Debugg:

Check for the presence of the DTCs stored in the memory of the EDC control unit.

 

Fault code 78

Malfunction:

The EDC cannot give a valid value for the current vehicle speed.

Cause:

The control unit received a message from the EDC via the data exchange circuit (pins 20 and 38), indicating that the value of the engine speed sender is unusual.

Notes:

It is unlikely that the data exchange circuit is faulty. Otherwise, the control unit would generate another fault code (fault code 82 or 83).

Debugg:

Check for the presence of the DTCs stored in the memory of the EDC control unit.

 

Fault code 79

Malfunction:

The EDC cannot give a valid value for the brake pedal position.

Cause:

The control unit received a message from the EDC via the data exchange circuit (pins 20 and 38), indicating that the value from the brake pedal position sensor is not typical.

Notes:

It is unlikely that the data exchange circuit is faulty. Otherwise, the control unit would generate another fault code (fault code 82 or 83).

Debugg:

Check for the presence of the DTCs stored in the EDC.

 

DTC 80

Malfunction:

EDC cannot give a reliable value for coolant temperature.

Cause:

The control unit received a message from the EDC, via a data circuit (pins 20 and 38), indicating that the value from the temperature sensor is not typical.

Notes:

It is unlikely that the data exchange circuit is faulty. Otherwise, the control unit would generate another fault code (fault code 82 or 83).

Debugg:

Check for the presence of the DTCs stored in the memory of the EDC control unit.

 

DTC 81

Malfunction:

Failure of the memory control unit.

Cause:

Checking the memory for the communication circuit in the control unit showed that one of the memory cells was malfunctioning.

Notes:

Memory for the communication circuit is used as a buffer for storing information from neighboring systems (such as EDC and ABS). Then the information is sorted before the system

Opticruise will take advantage of it. The control unit first writes some values to the memory of the communication circuit and then reads the same values to make sure that they are not distorted. If the control unit interprets a value as a deviation, it generates

trouble code.

Debugg:

Replace the control unit.

Comments: 0