Коды ошибок New Holland

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V ) as measured inside armrest by the module

Возможные причины отказа:

1. Неисправностьy hand throttle

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside armrest by the module.

Возможные причины отказа:

1. Неисправностьy hand throttle

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Message from multi function handle is not received properly by the armrest control module.

Возможные причины отказа:

1. Неисправностьy multi function handle

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside armrest by the module.

Возможные причины отказа:

1. Неисправностьy throttle

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside armrest by the module.

Возможные причины отказа:

1. Неисправностьy hand throttle

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside armrest by the module.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy position control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured at armrest контроллер.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy hitch position control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured at armrest контроллер.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy draft control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured at armrest контроллер.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy draft control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured at armrest контроллер.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy height limit control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured at armrest контроллер.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy height limit control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured at armrest контроллер.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy drop rate control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured at armrest контроллер.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy drop rate control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured at armrest контроллер.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy draft sensitivity control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured at armrest контроллер.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy draft sensitivity control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. Неисправностьy hitch control panel

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured at armrest контроллер.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy slip control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured at armrest контроллер.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy slip control potentiometer

3. Неисправностьy harness

4. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy remote клапан 5 lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy remote lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy remote lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy remote lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module.

Причина:

Возможные причины отказа:

1. Неисправностьy remote клапан 1 lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy remote клапан 2 lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy remote клапан 2 lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy remote клапан3 lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy remote клапан 3 lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Переключатель or connection is неисправен.

Возможные причины отказа:

1. Неисправностьy EHR float control переключатель

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy remote клапан4 lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy remote клапан 4 lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module

Возможные причины отказа:

1. Неисправностьy джойстик 1

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy джойстик 1

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module

Возможные причины отказа:

1. Неисправностьy джойстик 1

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy джойстик 1

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module

Возможные причины отказа:

1. Неисправностьy джойстик 1

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy джойстик 1

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module

Возможные причины отказа:

1. Неисправностьy джойстик 2

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy джойстик 2

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module

Возможные причины отказа:

1. Неисправностьy джойстик 2

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy джойстик 2

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком низкий (beнизкий 0.2 V) as measured inside the armrest by the control module

Возможные причины отказа:

1. Неисправностьy джойстик 2

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage from датчик слишком высокий (above 4.8 V) as measured inside the armrest by the control module.

Возможные причины отказа:

1. Неисправностьy джойстик 2

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage reference used within the armrest is слишком низкий.

Возможные причины отказа:

1. Неисправностьy connector or wiring

2. Swapped connectors

3. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltage reference used within the armrest is слишком высокий.

Возможные причины отказа:

1. Неисправностьy connector or wiring

2. Swapped connectors

3. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Memory error in the control module

Возможные причины отказа:

1. некорректный programming of the armrest контроллер

2. Неисправностьy armrest контроллер

18064 – MFH (multi-function handle) communication error

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Ошибка in communication link between the multi function handle and the control module in the armrest

Возможные причины отказа:

1. Неисправностьy multi function handle

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Multi function handle failed its self-test.

Возможные причины отказа:

1. Неисправностьy multi function handle

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltages from the dual track potentiometers inside lever 1 do not match

Возможные причины отказа:

1. Неисправностьy дистанционное управление lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltages from the dual track potentiometers inside lever 2 do not match

Возможные причины отказа:

1. Неисправностьy дистанционное управление lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltages from the dual track potentiometers inside lever3 do not match

Возможные причины отказа:

1. Неисправностьy дистанционное управление lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltages from the dual track potentiometers inside lever 4 do not match

Возможные причины отказа:

1. Неисправностьy дистанционное управление lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltages from the dual track potentiometers inside lever 5 do not match

Возможные причины отказа:

1. Неисправностьy дистанционное управление lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Voltages from the dual track potentiometers inside lever 6 do not match

Возможные причины отказа:

1. Неисправностьy дистанционное управление lever

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Mis-match of redundant переключатель contacts

Возможные причины отказа:

1. Неисправностьy hitch mouse raise/work переключатель

2. некорректный armrest configuration

3. Неисправностьy connector

4. Swapped connectors

5. Неисправностьy armrest контроллер

Причина: The ATC контроллер detects an обрыв цепи or short to power at the cab temperature датчик.

Возможные причины отказа:

.1. Cab temperature датчик failed.

.2. Harness damage.

.3. ATC контроллер отказ

Причина: The ATC контроллер has detected a короткое замыкание на массу condition at the cab temperature датчик.

Возможные причины отказа:

.1. Cab temperature датчик failed.

.2. Harness damage.

.3. ATC control module отказ

Причина: The ATC control module has detected an open or short to power condition at the evaporator temperature датчик

(evaporator temperature sender).

Возможные причины отказа:

.1. Evaporator temperature датчик failed.

.2. Harness damage.

.3. ATC контроллер отказ

Причина: The ATC control module has detected a короткое замыкание на массу condition at the evaporator temperature датчик (evaporator

temperature sender) .

Возможные причины отказа:

.1. Evaporator temperature датчик (evaporator temperature sender) failed.

.2. Harness damage.

.3. ATC контроллер отказ

Причина: The ATC control module has detected an open or short to power condition at bнизкийer speed potentiometer.

Возможные причины отказа:

.1. Bнизкийer speed selector failed.

.2. Harness damage.

.3. ATC контроллер отказ

Причина: The ATC контроллер has detected an open or short to power condition at temperature control potentiometer.

Возможные причины отказа:

.1. Temperature select potentiometer failed.

.2. Harness damage.

.3. ATC контроллер отказ

Причина: The ATC контроллер has detected a short to power condition on (+) side of pressure переключатель. Since the переключатель is normally

closed the short could be on either wire to the переключатель.

Возможные причины отказа:

.1. Wiring harness or connector damage.

.2. ATC контроллер отказ

Причина: The ATC контроллер has detected a короткое замыкание на массу condition on (+) side of pressure переключатель. Since the переключатель is normally closed, the short could be on either wire to the переключатель.

Возможные причины отказа:

.1. Wiring harness or connector damage.

.2. ATC контроллер отказ

Причина: The ATC контроллер has detected a short to power condition on (-) side of pressure переключатель. Since the переключатель is normally closed, the short could be on either wire to the переключатель.

Возможные причины отказа:

.1. Wiring harness or connector damage.

.2. ATC контроллер отказ

Причина: The ATC контроллер has detected a короткое замыкание на массу condition on (-) side of pressure переключатель. Since the переключатель is normally closed, the short could be on either wire to the переключатель.

Возможные причины отказа:

.1. Wiring harness or connector damage.

.2. ATC контроллер отказ

Примечание: If fault codes 125, 126, 127 or 128 are active with this code, folнизкий the troubleshooting for that code.

Причина: The ATC контроллер has detected a cycling error (2 times in 1 minute).

Возможные причины отказа:

.1. некорректный charge on system.

.2. Wiring issue or bad переключатель.

Причина: The ATC контроллер has detected a short to power at the низкий pressure переключатель.

Возможные причины отказа:

.1. Wire harness or connector problem.

.2. ATC контроллер отказ.

Возможные причины отказа:

.1. Wire harness or connector problem.

.2. ATC контроллер отказ.

Причина: The ATC контроллер has detected a short to power at the низкий pressure переключатель.

Возможные причины отказа:

.1. Wire harness or connector problem.

.2. ATC контроллер отказ.

Причина: The ATC контроллер has detected a короткое замыкание на массу at the низкий pressure переключатель.

Возможные причины отказа:

.1. Wire harness or connector problem.

.2. ATC module отказ.

Причина: The ATC контроллер has detected that the низкий pressure переключатель has been open for more than 1 minute.

Возможные причины отказа:

.1. некорректный charge on system.

.2. Wiring issue or bad переключатель.

Возможные причины отказа:

1. Problem battery or charging system.

2. Denox module/supply module internal отказ.

Решение:

1. With the tractor running, use the tractor display to check the напряжение аккумулятора.

A. Напряжение аккумулятора is above 15 V. test the alternator and the battery.

B. Напряжение аккумулятора is 12 – 14 V, continue to step 2

2. Delete fault code. If the fault code continually reoccurs replace the denox module/supply module.

Возможные причины отказа:

1. Problem with battery or charging system.

2. Denox module/supply module internal отказ.

Решение:

1. With the tractor running, use the tractor display to check the напряжение аккумулятора.

A. Напряжение аккумулятора is beнизкий 11 V. Test the alternator and the battery.

B. Напряжение аккумулятора is 12 – 14 V, continue to step 2

2. Delete fault code. If the fault code continually reoccurs replace the denox module/supply module.

Context: A second temperature датчик is used downstream of the selective catalytic reduction (SCR) muffler to monitor muffler operating efficiency. This error will occur when the сигнал voltage is высокийer than 2.2 V for more than 0.7 s.

Причина: There is an short circuit in the downstream temperature датчик circuit.

Возможные причины отказа:

1. Неисправностьy датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy denox module/supply module.

Context: A second temperature датчик is used downstream after the catalyst is injected to monitor operating efficiency. This error occurs when the сигнал voltage is less than 0.71 V for more than 0.7 s.

Причина: There is a short circuit in the downstream temperature датчик circuit.

Возможные причины отказа:

1. Неисправностьy датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy supply module.

Context: This is the first temperature датчик used upstream of the selective catalytic reduction (SCR) muffler to monitor muffler operating efficiency. This error will occur when the сигнал voltage is высокийer than 2.2 V for more than 0.7 s.

Причина: There is a short circuit in the upstream temperature датчик circuit.

Возможные причины отказа:

1. Неисправностьy датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy denox module/supply module.

Context: This is the first temperature датчик used upstream of the selective catalytic reduction (SCR) muffler to monitor muffler operating efficiency. This error will occur when the сигнал voltage is less than 0.71 V for more than 0.7 s.

Причина: There is a short circuit in the upstream temperature датчик circuit.

Возможные причины отказа:

1. Неисправностьy датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy denox module/supply module.

Context: The denox module/supply module has detected a высокий напряжение питания for urea pressure датчикs, located inside the denox module/supply module. Attempt to clear the code. If this code reoccurs, there is a problem with the напряжение питания internal to denox module/supply module. Replace the denox module/supply module.

Context: The denox module/supply module has detected a низкий напряжение питания for urea pressure датчикs, located inside the denox module/supply module. Attempt to clear the code. If this code reoccurs, there is a problem with the напряжение питания internal to denox module/supply module. Replace the denox module/supply module.

Context: The denox module/supply module has detected a отказ of the urea pressure датчик, located inside the denox module/ supply module. This error occurs when the датчик сигнал level has reached its internal limit. This error is corrected if датчик returns to its normal output. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/supply module.

Context: The denox module/supply module has detected a отказ of the urea pressure датчик, located inside the denox module/ supply module. The датчик сигнал level is above 5.0 V for over 700 ms. This fault will reset if the raw сигнал level goes beнизкий 5.0 V for over 1000 ms. Attempt to clear the code. If this code reoccurs, the датчик is defective and the denox module/supply module should be replaced.

Context: The denox module/supply module has detected a отказ of the urea pressure датчик, located inside the denox module. This error occurs when the датчик сигнал level is beнизкий 0.152 V for over 700 ms. This error is corrected if датчик returns to normal output for greater than 1.0 s. Ensure all connectors are secured properly on the denox module/ supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/ supply module.

Context: The denox module/supply module has detected a отказ of the urea temperature датчик, located inside the denox module/supply module. The датчик сигнал level is above 5.0 V for over 700 ms. This fault will reset if the raw сигнал level goes beнизкий 5.0 V for over 1000 ms. If the датчик is defective the denox module/supply module should be replaced.

Context: The denox module/supply module has detected a отказ of the urea temperature датчик, located inside the denox module/supply module. This error occurs when the датчик сигнал level is beнизкий 0.283 V for over 700 ms. This error is corrected if датчик returns to normal output for greater than 1.0 s. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/supply module.

Context: The denox module/supply module has sensed a fault with the voltage supply for the internal heaters, located in the supply module. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the supply module.

Context: The denox module/supply module has sensed a fault with the voltage supply for the internal heaters, located in the supply module. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the supply module.

Context: The denox module/supply module has sensed a fault with the voltage supply for the internal heaters, located in the denox module/supply module. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/supply module.

Context: The denox module/supply module has sensed a fault with the voltage supply for the internal heaters, located in the denox module/supply module. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/supply module.

Context: The denox module/supply module has sensed a fault with the voltage supply for the internal heaters, located in the denox module/supply module. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/supply module.

Context: The denox module/supply module has sensed a fault with the voltage supply for the coolant control клапан and the reverting клапан, located in the denox module/supply module. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/supply module.

Context: The denox module/supply module has sensed a fault with the voltage supply for the coolant control клапан and the reverting клапан, located in the denox module/supply module. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/supply module.

Context: If this error has occurred, there is a отказ in denox module/supply module. Ensure all connectors are ensured properly on the denox module/supply module and all lines are in operable condition. If fault does not reset or reoccurs, replace denox module/supply module.

Возможные причины отказа:

1. Problem with battery or charging system.

2. Denox module/supply module internal отказ.

Решение:

1. Tractor running, use the tractor display to check the напряжение аккумулятора.

A. Напряжение аккумулятора is beнизкий 11 V. Test the alternator and the battery.

B. Напряжение аккумулятора is 12 – 14 V, continue to step 2

2. Delete fault code. If the fault code continually reoccurs replace the denox module/supply module.

Возможные причины отказа:

1. Problem battery or charging system.

2. Denox module/supply module internal отказ.

Решение:

1. Tractor running, use the tractor display to check the напряжение аккумулятора.

A. Напряжение аккумулятора is above 15 V. Test the alternator and the battery.

B. Напряжение аккумулятора is 12 – 14 V, continue to step 2

2. Delete fault code. If the fault code continually reoccurs replace the denox module/supply module.

Context: The dosing control unit (DCU) has detected a отказ of the Internal level датчик, located inside the DCU. This error occurs when there is a short circuit or broken supply wire inside the denox module/supply module. Ensure all connectors are secured properly on the DCU and all lines are in operable condition. If the fault does not reset or reoccurs, replace the DCU.

Context: The dosing control unit has sensed the level of AdBlue™/Def drops beнизкий a predetermined level. If the сигнал is высокийer than 4.7 V for 0.5 s.

Причина: There is an short circuit in the AdBlue™/Def level датчик circuit.

Возможные причины отказа:

1. Неисправностьy Датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy DCU.

Context: The Dosing Control Unit (DCU) has sensed the level of AdBlue™/Def has dropped beнизкий a predetermined level. If the сигнал is низкийer than 0.2 V for 0.5 s this error will occur.

Причина: There is an короткое замыкание на массу in the AdBlue™/Def level датчик circuit.

Возможные причины отказа:

1. Неисправностьy датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy DCU.

Возможные причины отказа:

1. Неисправностьy wiring

2. DEF/AdBlue® tank temperature датчик is неисправен.

Возможные причины отказа:

1. Неисправностьy wiring

2. DEF/AdBlue® tank temperature датчик is неисправен.

Возможные причины отказа:

1. Dosing клапан harness short to power.

2. Denox module/supply module is неисправен

Возможные причины отказа:

1. Dosing клапан harness короткое замыкание на массу.

2. Denox module/supply module is неисправен

Примечание: After the repair has been completed, the code will still be present and active until it has been determined that the selective catalytic reduction (SCR) system is operating properly. The двигатель must be brought to normal operating temperature and run under load until the fault clears. If the code is still present and active after running the двигатель for 30 minutes, further diagnostics is necessary.

Возможные причины отказа:

1. Dosing клапан harness обрыв цепи.

2. Dosing клапан соленоид обрыв цепи.

3. Denox module/supply module is неисправен.

Возможные причины отказа:

1. Dosing клапан неисправен.

2. Denox module/supply module is неисправен

Context: The supply module/denox module has detected a urea pump speed датчик fault. This error occurs when the supply module/denox module has sensed all three hall датчикs outputs are высокий for greater than 7 s. This error is corrected if all three датчикs return to normal output for greater than 1 s. Ensure all connectors are secured properly on the supply module/denox module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the supply module/denox module.

Context: The denox module/supply module has detected this отказ because the averaged pump fнизкий is less than a predetermined fнизкий rate, and pump control duty cycle is greater than expected as determined by the denox module/supply module. The pump is blocked internally because of contamination, frozen DEF/AdBlue®, damaged pump motor, or damaged pump fнизкий measurement. Ensure all connectors are secured properly to the denox module/supply module and all lines are in operable condition. If fault does not reset, replace the denox module/supply module.

Context: The denox module/supply module has detected this отказ because the averaged pump fнизкий is greater than a predetermined value for over 7.0 s. Проверить hose from DEF/AdBlue® tank to pump module. If hose is detached, reconnect hose and secure to pump. If hose is defective, replace the hose. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. Replace denox module/supply module if fault reoccurs.

Context: The supply module/denox module has detected a urea pump speed датчик fault. This error occurs when the supply module/denox module has sensed all three hall датчик outputs are низкий for greater than 7 s. This error is corrected if all three датчикs return to normal output for greater than 1 s. If the fault does not reset or reoccurs, replace the supply module/denox module.

Context: The dosing control unit (DCU) has detected a отказ of the SCR Coolant control клапан. If this error is detected, the power stage is переключательed OFF and ON again and the check is repeated for ten times. Failure is reported if test fails each time. Ensure all connectors are secured properly on the DCU and all lines are in operable condition. If fault does not reset or reoccurs, replace the DCU.

Context: The dosing control unit (DCU) has detected a отказ of the SCR Coolant control клапан. If this error is detected, there is a short internal to the pump module. Ensure all connectors are secured properly on the DCU and all lines are in operable condition. If fault does not reset or reoccurs, replace the DCU.

Context: The dosing control unit (DCU) has detected a отказ of the SCR Coolant control клапан. If this error is detected, there is a internal отказ to the pump module. Ensure all connectors are secured properly on the DCU and all lines are in operable condition. If fault does not reset or reoccurs, replace the DCU.

Context: The denox module/supply module has detected a отказ of the reverting клапан, located inside the denox module/ supply module. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/supply module.

Context: The dosing control unit (DCU) has detected a отказ of the reverting клапан, located inside the supply module. Ensure all connectors are secured properly on the DCU and all lines are in operable condition. If the fault does not reset or reoccurs, replace the supply module.

Context: The denox module/supply module has detected a отказ of the reverting клапан, located inside the denox module/ supply module. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/supply module.

Context: A клапан remote from the storage tank is used to control coolant to prevent DEF/AdBlue® from freezing in cold temperatures. The клапан will respond to a сигнал from the denox module/supply module based on temperature сигналs from the temperature датчик.

Причина: A обрыв цепи has been detected in the tank heater control клапан circuit.

Возможные причины отказа:

1. Неисправностьy tank heating клапан/coolant fнизкий соленоид

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy denox module/supply module.

Context: A клапан remote from the storage tank is used to control coolant to prevent AdBlue™/DEF from freezing in cold temperatures. The клапан will respond to a сигнал from the DCU based on temperature сигналs from the temperature датчик.

Причина: A short circuit has been detected in the tank heater control клапан (coolant fнизкий соленоид клапан) circuit.

Возможные причины отказа:

1. Неисправностьy tank heater control клапан

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy DCU.

Context: A клапан remote from the storage tank is used to control coolant to prevent DEF/AdBlue® from freezing in cold temperatures. The клапан will respond to a сигнал from the denox module/supply module based on temperature сигналs from the temperature датчик.

Причина: A обрыв цепи has been detected in the tank heater control клапан (coolant fнизкий соленоид клапан) circuit.

Возможные причины отказа:

1. Неисправностьy tank heating клапан/coolant fнизкий соленоид

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy denox module/supply module.

Context: A клапан remote from the storage tank is used to control coolant to prevent DEF/AdBlue® from freezing in cold temperatures. The клапан will respond to a сигнал from the denox module/supply module based on temperature сигналs from the temperature датчик.

Причина: A short circuit has been detected in the tank heater control клапан circuit.

Возможные причины отказа:

1. Неисправностьy tank heating клапан/coolant fнизкий соленоид

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy denox module/supply module.

Context: The denox module/supply module has detected the DEF/AdBlue® pressure has not reached 500 kPa within 2.5 min. Manually check DEF/AdBlue® level is filled to operating level. Проверить feeding tubes, connectors and O-rings in connectors for any air leaks. If error is still present, use the electronic service tool (EST) to run urea dosing system test (UDST) to troubleshoot the system further.

Примечание: After the repair has been completed, the code will still be present and active until it has been determined that the selective catalytic reduction (SCR) system is operating properly. The двигатель must be brought to normal operating temperature and run under load until the fault clears. If the code is still present and active after running the двигатель for 30 minutes, further diagnostics is necessary.

Context: The denox module/supply module has detected the DEF/AdBlue® pressure exceeds 6.5 bar for 30 s. Reasons for отказ could be internal control клапан blocked or pump speed to высокий. These are indications of internal отказ of supply module. Use the electronic service tool (EST) to run the urea dosing system test (UDST) to monitor the DEF/AdBlue® pressure and pump speed. DEF/AdBlue® pressure should not exceed 500 kPa, and the pump speed should not exceed 6000 RPM. Replace denox module/supply module if values are вне диапазона.

Context: The denox module/supply module has detected the DEF/AdBlue® temperature in module box is less than 75 °C (167 °F) or greater than 9 °C (48 °F), and system is not in defreezing mode. This error occurs if, in the previous driving cycle, box temperature was less than 85 °C (185 °F) and in shutdown mode. If during the actual driving cycle the box temperature remains less than 70 °C (158 °F)for more than 10.0 s, the system goes into emergency shutdown and will not start until EEPROM is cleared. Use the electronic service tool (EST) to clear code. Verify tank heater codes are not present, and there is no temperature plausibility errors. If other errors are present, correct as well.

Context: The DEF/AdBlue® temperature in tank is greater than 75.0 °C (167.0 °F)for 300 s and system is not in defreezing mode. This code will heal when the temperature returns beнизкий 75.0 °C (167.0 °F)for 1.0 s.

Причина: The DEF/AdBlue® tank temperature вне диапазона.

Возможные причины отказа:

1. Tank heating клапан stuck open.

2. Проверить for other tank heating клапан/coolant fнизкий соленоид related error codes.

Context: The denox module/supply module has detected this отказ when ambient temperature is beнизкий 17.0 °F at system start up. If DEF/AdBlue® pressure does not reach 390 kPa within 2.5 min the inlet line is frozen. This отказ is stored after 30 repetitions with 2.5 min heating phases between the checks.

Причина: The denox module/supply module has detected this error because of no DEF/AdBlue® pressure.

Возможные причины отказа:

1. AdBlue™/DEF tank empty.

2. Inlet line broken.

3. Pump does not feed.

4. DEF/AdBlue® box heater does not work correctly.

Context: The denox module/supply module has detected this отказ when ambient temperature is beнизкий 17.0 °F at system start up, and inlet line is detected open. If DEF/AdBlue® pressure does not drop to 350 kPa within 40 s with the dosing клапан open to 99.0 %, the pressure line is frozen. This отказ is stored after 28 repetitions with 2.5 min heating phases between the checks.

Причина: The denox module/supply module has detected this error because of no DEF/AdBlue® injection.

Возможные причины отказа:

1. Dosing клапан does not open

2. Pressure line blocked

3. Injection nozzle blocked

4. Неисправностьy box heater

Context: The dosing control unit (DCU) has detected this отказ when ambient temperature is beнизкий 17.0 °F at system start up. The pressure line and inlet line is detected open. If DEF/AdBlue® pressure does not reach 390 kPa within 40 s with full pump speed, the system is not unfrozen. This отказ is stored after 26 repetitions with 2.5 min heating phases between the checks. Проверить if the internal heater is working correctly.

Context: The denox module/supply module has detected this отказ when ambient temperature is beнизкий 17.0 °F at system start up. The inlet and pressure line is detected open and pressure build up was OK. If DEF/AdBlue® pressure does not drop to 140 kPa within 50 s with the vent клапан open to 100 %, the back fнизкий line is frozen. This отказ is stored after 24 repetitions with 2.5 min heating phases between the checks.

Причина: The denox module/supply module has detected this error because of no DEF/AdBlue® back fнизкий line is frozen.

Возможные причины отказа:

1. DEF/AdBlue® tank ventilation clogged

2. Back fнизкий line clogged

3. Ventilation клапан does not open

4. Back fнизкий line frozen

Context:

The dosing control unit (DCU) has detected a short circuit. If at normal operating speed the AdBlue™/DEF pressure is greater than 450 kPa, and the cooling клапан is closed from 100 – 0 %, the AdBlue™/DEF pressure must rise at least 15 kPa within 2 s. Ensure all connections and connectors are secured to the DCU properly. If error is still present, there is an internal отказ of the box. Replace the DCU.

Context:

The dosing control unit (DCU) has detected a обрыв цепи. If at normal operating speed the AdBlue™/DEF pressure is greater than 450 kPa, and the cooling клапан is open from 0 – 100 %, the AdBlue™/DEF pressure must drop at least 15 kPa within 2 s. Ensure all connections and connectors are secured to the DCU properly. If error is still present, there is an internal отказ of the box. Replace the DCU.

Возможные причины отказа:

1. Клапан is mechanically stuck

2. System was empty, needs primed

Возможные причины отказа:

1. Problem with battery or charging system.

2. Denox module/supply module internal отказ.

Возможные причины отказа:

1. Problem battery or charging system.

2. Denox module/supply module internal отказ.

Context: During operation, the ventilation клапан is fully opened, the pump is then set to 100 % operation until DEF/AdBlue® pressure has reached 500 kPa. The ventilation клапан is then closed. If DEF/AdBlue® pressure does not reach 500 kPa within 2.5 min, this error occurs.

Причина: The denox module/supply module has detected the pump motor is not delivering.

Возможные причины отказа:

1. No DEF/AdBlue® in tank

2. System was empty, needs primed

3. Неисправностьy pump

4. Неисправностьy feeding line

Context: The denox module/supply module has detected the temperatures are not correct within 30 min of operation. The module box temperature is less than -9 °C (16 °F) or greater than 75 °C (167 °F), or the DEF/AdBlue® tank is less than -17 °C (2 °F) or greater than 75 °C (167 °F). Bring temperature to a normal level, between 0 – 30 °C (32 – 86 °F). Возможные причины отказа:

1. Extreme cold ambient conditions.

2. DEF/AdBlue® tank temperature датчик is неисправен.

Context: The AdBlue™/Def tank contains the AdBlue™/Def fluid.

Причина: The dosing control unit (DCU) has detected the AdBlue™/Def level is constantly less than 0.1 % for more than 25 s.

Возможные причины отказа:

1. Tank is empty

2. Неисправностьy level датчик

Context: The denox module/supply module has generated this fault because it has sensed the back fнизкий line is clogged. This fault occurs when the denox module/supply module performs the a test and determines: DEF/AdBlue® pressure is greater than 345 kPa (50 psi), pump speed greater than 300 RPM (300 RPM), downstream temperature is greater than 60 °C (140 °F), and dosing is greater than 6 % (6 %) for 20 s (20 s). If these parameters are met, the cooling клапан is closed, the DEF/AdBlue® pump is stopped and the dosing клапан is fully opened and the pressure is rechecked by the denox module/supply module. If the pressure is less than 30 kPa (4.35 psi), the back fнизкий line is clogged. Ensure the lines are open and free fнизкийing. If the lines are free of blockage, replace the denox module/supply module.

Context: The denox module/supply module has detected at start up , after opening the coolant control клапан for 40 s, DEF/ AdBlue® pressure is less than 150 kPa. First check that pressure and back fнизкий line are not frozen or clogged. If all lines are open and in proper operation, the denox module/supply module has failed. Replace the denox module/supply module.

Примечание: After the repair has been completed, the code will still be present and active until it has been determined that the selective catalytic reduction (SCR) system is operating properly. The двигатель must be brought to normal operating temperature and run under load until the fault clears. If the code is still present and active after running the двигатель for 30 minutes, further diagnostics is necessary.

Возможные причины отказа:

1. Dosing nozzle blocked.

2. Crimped , or collapsed supply line to dosing nozzle.

Решение:

1. Verify error is still present and in an active state.

A. If error is still present and active, inspect for crimped , or collapsed supply line. If supply line is good inspect and clean out dosing nozzle..

B. If the error is no longer present or inactive, return unit to field operation..

Context: The denox module/supply module has detected низкий DEF/AdBlue® level. This error occurs when the DEF/AdBlue® fluid level is слишком низкий or level датчик has faults present. Ensure the heated level датчик is connected properly. Проверить DEF/AdBlue® tank level is full. If fluid level is низкий, fill tank to proper capacity. Проверить for any other errors that may be present. Correct those errors first, then recheck original error has been corrected. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/supply module.

Context: The denox module/supply module has detected низкий DEF/AdBlue® level. This error occurs when the DEF/AdBlue® fluid level is слишком низкий or level датчик has faults present. Ensure the heated level датчик is connected properly. Проверить DEF/AdBlue® tank level is full. If fluid level is низкий, fill tank to proper capacity. Проверить for any other errors that may be present. Correct those errors first, then recheck original error has been corrected. Ensure all connectors are secured properly on the denox module/supply module and all lines are in operable condition. If the fault does not reset or reoccurs, replace the denox module/supply module.

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Контроллер communication error

Причина: There was an обрыв цепи detected in the DEF/AdBlue® level датчик circuit.

Возможные причины отказа:

1. Неисправностьy Датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy DCU.

Причина: There was a short to power detected in the DEF/AdBlue® level датчик circuit.

Возможные причины отказа:

1. Неисправностьy Датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy DCU.

Причина: There was a короткое замыкание на массу detected in the DEF/AdBlue® level датчик circuit.

Возможные причины отказа:

1. Неисправностьy Датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy DCU.

Context: The denox module/supply module has detected this отказ because the ambient air temperature has timed out. Ensure all connectors are secured properly to the denox module/supply module and all lines are in operable condition. If fault does not reset, replace the denox module/supply module.

Context: The denox module/supply module has detected this отказ because the ambient air temperature has неисправен can bus сигнал. Ensure all connectors are secured properly to the denox module/supply module and all lines are in operable condition. If fault does not reset, replace the denox module/supply module.

Context: The denox module/supply module has suffered a detection error. This error indicates a defect in the dataset that is presently loaded in the denox module/supply module. If this error is present and active, reload the software dataset. If this error then reoccurs, replace the denox module/supply module.

Context: The denox module/supply module has an internal cycle counter to check if the afterrun is correctly finished. This cycle counter data is then stored in the EEPROM memory. This error indicates the denox module/supply module has attempted to store this data in a protected area of memory. If this error is present and active, first verify the denox module/supply module and other components have not been tampered with and reload the software. If this error reoccurs replace the denox module/supply module.

Context: The denox module/supply module memory in EEPROM is not correct or a SPI communication error has occurred. This error indicates an internal denox module/supply module error. If this error is present and active, ensure all electrical connectors are secure and reload the denox module/supply module software. If this error reoccurs, replace the denox module/supply module.

Context: The denox module/supply module has an internal error in software. If the code is present and active, reload the software. If this error reoccurs, replace the denox module/supply module.

Context: The denox module/supply module has the некорректный EEPROM installed. This error would only occur during initial startup when the denox module/supply module has previously been replaced. Replace the denox module/supply module.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy ignition переключатель

3. Неисправностьy12/24 volt converter

Context: The denox module/supply module has detected the main relay is not переключательed off within 2 s.

Причина: The main relay is shutting off too late.

Возможные причины отказа:

1. Неисправностьy relay

2. Неисправностьy electrical wiring or connection

3. Denox module/supply module error

Причина: Переключательed power relay control circuit open..

Возможные причины отказа:

1. Неисправностьy relay

2. Неисправностьy electrical wiring or connection

3. Denox module/supply module error

Причина: Переключательed power relay control circuit высокий.

Возможные причины отказа:

1. Неисправностьy relay

2. Неисправностьy electrical wiring or connection

3. Denox module/supply module error

Причина: Переключательed power relay control circuit open.

Возможные причины отказа:

1. Неисправностьy relay

2. Неисправностьy electrical wiring or connection

3. Denox module/supply module error

Причина: Высокий urea temperature in pump module.

Возможные причины отказа:

1. Tank heating клапан stuck open.

2. Проверить for other tank heating клапан/coolant fнизкий соленоид related error codes.

Причина: Высокий urea temperature in pump module.

Возможные причины отказа:

1. Tank heating клапан stuck open.

2. Проверить for other tank heating клапан/coolant fнизкий соленоид related error codes.

Context: The dosing control unit (DCU) has activated this fault due to other fault codes associated with the DEF / AdBlue® injection control being active. Diagnose those fault codes to clear this fault. If this fault is active without any other codes active, reload the software in the DCU or replace the DCU.

Context: The dosing control unit (DCU) has activated this fault due to other fault codes associated with the DEF / AdBlue® injection control being active. Diagnose those fault codes to clear this fault. If this fault is active without any other codes active, reload the software in the DCU or replace the DCU.

Context: The dosing control unit (DCU) has activated this fault due to other fault codes associated with the DEF / AdBlue® injection temperature being active. Diagnose those fault codes to clear this fault. If this fault is active without any other codes active, reload the software in the DCU or replace the DCU.

Context: The dosing control unit (DCU) has activated this fault due to other fault codes associated with the DEF / AdBlue® injection control being active. Diagnose those fault codes to clear this fault. If this fault is active without any other codes active, reload the software in the DCU or replace the DCU.

Context: The dosing control unit (DCU) has activated this fault due to other fault codes associated with the DEF / AdBlue® system urea низкий tank level. Confirm the urea tank is full. Diagnose those fault codes to clear this fault. If this fault is active without any other codes active, reload the software in the DCU or replace the DCU.

Context: The denox module/supply module has detected the urea tank temperature and denox module/supply module temperature are not in agreement.

Возможные причины отказа:

1. Can communication error.

2. DEF/AdBlue® tank temperature датчик is неисправен.

Context: The denox module/supply module has detected the urea tank temperature and denox module/supply module temperature are not in agreement.

Возможные причины отказа:

1. Extreme cold ambient conditions.

2. DEF/AdBlue® tank temperature датчик is неисправен.

Context: The denox module/supply module has detected the urea tank temperature and denox module/supply module temperature are not in agreement.

Возможные причины отказа:

1. Extreme cold ambient conditions.

2. DEF/AdBlue® tank temperature датчик is неисправен.

Context: The denox module/supply module has detected the urea tank temperature and denox module/supply module temperature are not in agreement.

Возможные причины отказа:

1. Extreme hot ambient conditions.

2. DEF/AdBlue® tank temperature датчик is неисправен.

Context: The denox module/supply module has detected the urea tank temperature and denox module/supply module temperature are not in agreement.

Возможные причины отказа:

1. Extreme cold ambient conditions.

2. DEF/AdBlue® tank temperature датчик is неисправен.

Context: The denox module/supply module has detected the urea tank temperature and denox module/supply module temperature are not in agreement.

Возможные причины отказа:

1. Extreme hot ambient conditions.

2. DEF/AdBlue® tank temperature датчик is неисправен.

Context: The denox module/supply module has detected the urea tank temperature and denox module/supply module temperature are not in agreement.

Возможные причины отказа:

1. Extreme cold ambient conditions.

2. DEF/AdBlue® tank temperature датчик is неисправен.

Context: During operation, the ventilation клапан is fully opened, the pump is then set to 100 % operation until DEF/AdBlue® pressure has reached 500 kPa. The ventilation клапан is then closed. If DEF/AdBlue® pressure does not reach 500 kPa within 2.5 min, this error occurs.

Причина: The denox module/supply module has detected the pump motor is not delivering.

Возможные причины отказа:

1. No DEF/AdBlue® in tank

2. System was empty, needs primed

3. Неисправностьy pump

4. Неисправностьy feeding line

Context: The denox module/supply module has detected the DEF/AdBlue® pressure exceeds 6.5 bar for 30 s. Reasons for отказ could be internal control клапан blocked, blocked dosing клапан nozzle or слишком высокий a pump speed. These are indications of internal отказ of supply module. Use the electronic service tool (EST) to run the Urea dosing system test (UDST) to monitor the DEF/AdBlue® pressure and pump speed. DEF/AdBlue® pressure should not exceed 500 kPa, and the pump speed should not exceed 6000 RPM. Replace denox module/supply module if values are вне диапазона.

Context: The denox module/supply module has detected leakage. Visual inspect all urea lines and connections for leakage. These are indications of internal leakage of supply module. Use the electronic service tool (EST) to run the urea dosing system test (UDST) to monitor the DEF/AdBlue® pressure and pump speed. DEF/AdBlue® pressure should not exceed 500 kPa , and низкийer values can indicate leakage, and the pump speed should not exceed 6000 RPM. Replace denox module/supply module if values are вне диапазона.

Context: The denox module/supply module has detected leakage. Visual inspect all urea lines and connections for leakage. These are indications of internal leakage of supply module. Use the electronic service tool (EST) to run the urea dosing system test (UDST) to monitor the DEF/AdBlue® pressure and pump speed. DEF/AdBlue® pressure should not exceed 500 kPa , and низкийer values can indicate leakage, and the pump speed should not exceed 6000 RPM. Replace denox module/supply module if values are вне диапазона.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: This fault occurs if the высокий side driver duty cycle is 0 and the высокий side driver is off and its output is greater than 0.125 A.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy electronic draft control (EDC) клапан raise соленоид

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: This fault occurs if the высокий side driver duty cycle is greater than 20 % or the высокий side driver is full on and its output is less than 0.125 A.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy electronic draft control (EDC) клапан raise соленоид

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: This fault occurs if the высокий side driver duty cycle is 0 and the высокий side driver is off and its output is greater than 0.125 A.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy electronic draft control (EDC) клапан низкийer соленоид

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: This fault occurs if the высокий side driver duty cycle is greater than 20 % or the высокий side driver is full on and its output is less than 0.125 A.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy electronic draft control (EDC) клапан низкийer соленоид

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: Низкий side driver is beнизкий the calculated voltage limit for 10 milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy electronic draft control (EDC) клапан низкийer or raise соленоид

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: Self test failed

Возможные причины отказа:

1. Tractor control unit (TCU) harness not wired correctly

2. Software issue

Причина: This fault occurs if the низкий side EDC raise hitch соленоид is grounded for 250 milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy electronic draft control (EDC) клапан raise соленоид

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: Низкий side driver is off but высокий side driver does not detect an обрыв цепи.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy electronic draft control (EDC) клапан низкийer соленоид

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: Tractor control unit is disconnected from the CAN data bus for ten milliseconds.

Возможные причины отказа:

1. Контроллер communication error.

2. Loose connection or damaged can bus wiring.

3. Bad terminator.

Причина: This fault occurs if the armrest control units is not present for 10 milliseconds.

Возможные причины отказа:

1. Bad connection between th tractor control unit (TCU) and the armrest контроллер.

2. Контроллер отказ.

Причина: This fault occurs if the instrument cluster is not present for 10 milliseconds.

Возможные причины отказа:

1. Bad connection between the tractor control unit (TCU) and the instrument cluster (ICU).

2. Контроллер отказ.

Причина: The 5 V reference voltage is monitored and is consistently greater than 5.8 V .

Возможные причины отказа:

1. Short circuit to 8 V or 12 V power source.

Причина: The 5 V reference voltage is monitored and is consistently less than 4.2 V .

Возможные причины отказа:

1. Short circuit to ground or an обрыв цепи.

2. No power or ground to tractor control unit (TCU). Other низкий voltage fault codes will be recorded on контроллерs.

Причина: The data bus сигналed that the hitch position command potentiometer has failed. The tractor control unit (TCU) received the сигнал directly from potentiometer.

Возможные причины отказа:

1. The hitch position command potentiometer has failed.

Причина: The hitch position feedback is outside the expected hitch pot range (60 to 1000 counts) for 100 milliseconds.

Возможные причины отказа:

1. Potentiometer linkage problem.

2. Rock shaft (hitch position) potentiometer has failed.

3. Harness damage.

Причина: The data bus сигналed that the upper limit potentiometer has failed. The tractor control unit (TCU) received the сигнал from the armrest контроллер.

Возможные причины отказа:

1. The upper limit potentiometer has failed.

2. Software execution error in armrest контроллер.

Причина: Test received CAN data for the load command for ten milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy draft sensitivity control potentiometer

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: Draft pin outside the expected voltage range (50 to 992 counts) for ten milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy load sensing pin

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: Two draft pins outside the expected voltage range (50 to 992 counts) for ten milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy load sensing pin

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: The tractor control unit (TCU) lost communication with the instrument cluster (ICU) for 700 milleseconds.

Возможные причины отказа:

1. Bad connection between the tractor control unit (TCU) and the instrument cluster (ICU).

2. Контроллер отказ.

Причина: The data bus сигналed that the hitch up/down переключатель has failed. The tractor control unit (TCU) received the сигнал from the armrest control module.

Возможные причины отказа:

1. The hitch up/down переключатель has failed.

2. Software execution error in armrest контроллер.

Причина: Either both remote переключательes are simultaneously on or one of the переключательes is on before startup (stuck on condition) for ten milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Remote three point hitch (TPH) переключатель sticking

3. Неисправностьy remote TPH переключатель

4. Неисправностьy harness

5. Неисправностьy tractor control unit (TCU)

Причина: Travel range potentiometer value received from CAN data bus indicates отказ condition.

Возможные причины отказа:

1. The travel range potentiometer has failed.

Причина: Drop rate value received over the CAN data bus indicates the potentiometer has failed. The tractor control unit (TCU) received the сигнал from the armrest control module.

Возможные причины отказа:

1. The drop rate command potentiometer has failed.

2. Software execution error in armrest контроллер.

Причина: Правый draft pin outside the expected voltage range (50 to 992 counts) for ten milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy load sensing pin

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: Левый draft pin outside the expected voltage range (50 to 992 counts) for ten milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy load sensing pin

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: The data bus сигналed that the radar ground speed датчик has failed.

Возможные причины отказа:

1. Radar ground speed датчик has failed.

2. Wiring problem between the TCU контроллер and the radar ground speed датчик.

Причина: Slip limit set point received over the CAN data bus indicates the control has failed.

Возможные причины отказа:

1. Failed slip limit control переключатель.

Причина: Slip enable переключатель data received over the CAN data bus indicates the button has failed.

Возможные причины отказа:

1. Failed slip enable переключатель.

Причина: The percent wheel slip is determined by the difference between the wheel speed value and the ground speed value. The tractor control unit (TCU) receives the information from the instrument контроллер through the data bus.

Возможные причины отказа:

1. Wheel slip sensing failed. (Either radar gun or wheel speed датчик).

2. Wiring problem between instrument контроллер, or tractor control unit (TCU) and датчикs.

Причина: The data bus сигналed that the hitch inching up переключатель has failed. The tractor control unit (TCU) received the сигнал from the armrest control module.

Возможные причины отказа:

1. The inching up переключатель has failed.

2. Software execution error in armrest контроллер.

Причина: The data bus сигналed that the hitch inching down переключатель has failed. The tractor control unit (TCU) received the сигнал from the armrest control module.

Возможные причины отказа:

1. The inching down переключатель has failed.

2. Software execution error in armrest контроллер.

Причина: Draft pins were detected on a hitch position only tractor (as defined by armrest control module) for ten milliseconds.

Возможные причины отказа:

1. Tractor is not properly configured.

Причина: During hitch низкийer calibration, the двигатель speed must be above 1500 RPM If the двигатель speed is низкийer than 1500

RPM, this fault code is recorded.

Возможные причины отказа:

1. Низкий двигатель RPM.

Причина: The specified tractor has draft control but no draft pin(s) are detected.

Возможные причины отказа:

1. Проверить draft pin harness connections.

2. Tractor is not properly configured.

Примечание: In rare cases, external electromagnetic interference may affect the hitch calibration process. When this is suspected, move the vehicle away from высокий electromagnetic interference devices such as welding machines, высокий voltage transformers, radio broadcast towers, etc.

Причина: Calibration was aborted due to the tractor moving.

Возможные причины отказа:

1. Tractor moved during calibration.

2. Minor chance that the tractor speed датчик has failed.

Причина: Hitch system calibration was attempted while the двигатель was not running or the двигатель speed датчик failed.

Возможные причины отказа:

1. Двигатель was not running during calibration.

2. Двигатель speed датчик failed.

Причина: During hitch system calibration, the PWM threshold to start hitch raising was above the limit (55%).

Возможные причины отказа:

1. Raise соленоид coil resistance is слишком высокий.

2. Wiring harness or connector problem between the hitch raise соленоид and the tractor control unit (TCU).

3. Напряжение аккумулятора is очень низкий.

4. Hitch клапан raise portion stuck closed.

Причина: During hitch system calibration, the PWM threshold to start hitch raising was beнизкий the limit (6%).

Возможные причины отказа:

1. Напряжение аккумулятора is very высокий.

2. Raise соленоид coil resistance is слишком низкий.

3. Клапан отказ.

Причина: During hitch calibration, the сигнал from the hitch rockshaft potentiometer is not within specification at the maximum raise position. Be advised that:

1. Sнизкий hitch up and down movement is NOT caused by the hitch position pot.

2. Always clear stored fault codes and attempt to recalibrate the hitch before replacing any electronic components.

Возможные причины отказа:

1. Mechanical interference is preventing the hitch from moving fully down.

2. Potentiometer linkage problem.

3. Rockshaft potentiometer has failed.

4. Harness damage.

Причина: During hitch system calibration, the PWM threshold to start hitch низкийering was above the limit (55%).

Возможные причины отказа:

1. Низкийer соленоид coil resistance is слишком высокий.

2. Wiring harness or connector problem between the hitch низкийer соленоид and the tractor control unit (TCU).

3. Напряжение аккумулятора is очень низкий.

4. Hitch клапан низкийer portion stuck closed.

Причина: During hitch system calibration, the PWM threshold to start hitch низкийering was beнизкий the limit (6%).

Возможные причины отказа:

1. Напряжение аккумулятора is very высокий.

2. Низкийer соленоид coil resistance is слишком низкий.

3. Клапан отказ.

Примечание: This is a non fault. Clear the fault code from the контроллер.

Причина: The operator did not acknowledge (within 6 minutes) when the hitch was fully низкийered during the calibration procedure. Clear the fault code and calibrate the hitch system.

Причина: During hitch calibration, the сигнал from the hitch rockshaft potentiometer is not within specification at the maximum raise position. Be advised that:

1. Sнизкий hitch up and down movement is NOT caused by the hitch position pot.

2. Always clear stored fault codes and attempt to recalibrate the hitch before replacing any electronic components.

Возможные причины отказа:

1. Mechanical interference is preventing the hitch from moving fully down.

2. Potentiometer linkage problem.

3. Rockshaft potentiometer has failed.

4. Harness damage.

Причина: During hitch calibration, the сигнал from the hitch rockshaft potentiometer is not within specification at the maximum raise position. Be advised that:

1. Sнизкий hitch up and down movement is NOT caused by the hitch position pot.

2. Always clear stored fault codes and attempt to recalibrate the hitch before replacing any electronic components.

Возможные причины отказа:

1. Mechanical interference is preventing the hitch from moving fully down.

2. Potentiometer linkage problem.

3. Rockshaft potentiometer has failed.

4. Harness damage.

Причина: During calibration, the ratio of rock shaft position range to position command potentiometer is not within specifications.

Возможные причины отказа:

1. Mechanical interference.

2. Rock shaft potentiometer has failed.

3. Harness damage.

4. Potentiometer linkage problem.

Причина: Правый draft pin offset voltage is outside the expected voltage range.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy load sensing pin

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: Левый draft pin offset voltage is outside the expected voltage range.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy load sensing pin

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: Левый and правый draft pin offset voltage is outside the expected voltage range.

Возможные причины отказа:

Причина: If no pins are installed, the operator will be prompted to choose 0, 1 or 2 pins. If two draft pins are installed, the calibration will start automatically and the operator will not be prompted for number of pins. Tractors are not sold with one pin, but the choice is still available if one pin is неисправен and the operator wants to run with a single pin. See configuration and calibration section in manual to properly setup the hitch system.

Причина: The tractor control unit (TCU) requires calibration. New tractor control unit (TCU) was installed and needs to be calibrated.

Возможные причины отказа:

1. Tractor control unit (TCU) was не откалиброван.

Причина: The tractor control unit (TCU) is not communicating with the performance monitor on the tractor instrumentation.

Возможные причины отказа:

1. Bad connection between the tractor control unit (TCU) and the instrument cluster (ICU).

2. Контроллер отказ.

Причина: This fault occurs when the 8-volt reference is above 8.8 volts for 300 milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy load sensing pin

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: This fault occurs when the 8-volt reference is above 7.2 volts for 300 milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy load sensing pin

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: The 12VH voltage is monitored and is consistently less than 8 V.

Возможные причины отказа:

1. Напряжение аккумулятора is низкийer than 8.0 V.

2. Контроллер power or ground problem.

3. Alternator regulator is неисправностьing.

Причина: This fault occurs when the top link переключатель is on at power up.

Возможные причины отказа:

1. Electronic draft control was not configured properly.

Причина: This fault occurs when both top link raise and низкийer переключательes are on.

Возможные причины отказа:

1. Electronic draft control was not configured properly.

Причина: This fault occurs when the lift link переключатель is on at power up.

Возможные причины отказа:

1. Electronic draft control was not configured properly.

Причина: This fault occurs when both side link extend and retract переключательes are on.

Возможные причины отказа:

1. Electronic draft control was not configured properly.

Причина: The 12VU voltage is monitored and is consistently less than 8 V.

Возможные причины отказа:

1. Напряжение аккумулятора is низкийer than 8.0 V.

2. Контроллер 12VU1 power or ground problem.

3. Alternator regulator is неисправностьing.

Причина:

Возможные причины отказа:

1. Напряжение аккумулятора is низкийer than 8.0 V.

2. Контроллер 12VU2 power or ground problem.

3. Alternator regulator is неисправностьing.

Причина:

Возможные причины отказа:

1. Напряжение аккумулятора is низкийer than 8.0 V.

2. Контроллер 12VH1 power or ground problem.

3. Alternator regulator is неисправностьing.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:Соленоид failed for ten milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy MFD соленоид

3. Неисправностьy harness

4. Неисправностьy tractor control module (TCU)

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Context: Rear diff lock disabled.

Причина: Rear differential lock соленоид failed for ten milliseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy rear differential lock соленоид

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: Brake light relay fault occurs for ten milliseconds.

Возможные причины отказа:

1. Bнизкийn fuse

2. Неисправностьy brake переключатель relay

3. Неисправностьy harness/wiring

4. Неисправностьy tractor control unit (TCU

Причина: CAN-bus indicates переключатель отказ for ten milliseconds.

Возможные причины отказа:

1. Неисправностьy rear differential переключатель

2. Неисправностьy harness/wiring

3. Неисправностьy tractor control unit (TCU)

Причина: The CAN-шина сигналed that the differential lock переключатель is in an illogical state, indicating переключатель отказ.

Возможные причины отказа:

1. The differential lock переключатель failed in the armrest контроллер.

2. Software execution error in the armrest контроллер.

Решение:

1. If the differential lock переключатель fails, fault code 6004 should be active. Проверить for fault code 6004 through the armrest контроллер.

A. Неисправность code 6004 is active. Use the troubleshooting for fault code 6004 to resolve this problem.

B. Неисправность code 6004 is not active. The problem is still in the armrest. Use the troubleshooting for fault code 6004 to resolve this problem.

Причина: CAN-bus indicates переключатель отказ for ten milliseconds.

Возможные причины отказа:

1. Неисправностьy MFD переключатель

2. Неисправностьy harness/wiring

3. Неисправностьy tractor control unit (TCU)

CAN-шина сигналed that the MFD переключатель is in an illogical state, indicating переключатель отказ.

Возможные причины отказа:

1. MFD переключатель failed in the armrest контроллер.

2. Software execution error in the armrest контроллер.

Решение:

1. If the MFD переключатель fails, fault code 6006 should be active. Проверить for fault code 6006 through the armrest контроллер.

A. Неисправность code 6006 is active. Use the troubleshooting for fault code 6006 to resolve this problem.

B. Неисправность code 6006 is not active. The problem is still in the armrest контроллер. Use the troubleshooting for fault code 6006 to resolve this problem.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Steering angle датчик above maximum voltage limit of 4.98 V volts for one second.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy steering angle датчик

3. Неисправностьy harness

4. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Steering angle датчик beнизкий minimum voltage limit of 0.2 V for one second.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy steering angle датчик

3. Неисправностьy harness

4. Неисправностьy контроллер

Причина: Voltage is beнизкий 5.0 V for 400 milliseconds.

Возможные причины отказа:

1. Bнизкийn fuse

2. Неисправностьy tractor control unit (TCU)

Причина: Voltage is beнизкий 5.0 V for 400 milliseconds.

Возможные причины отказа:

1. Bнизкийn fuse

2. Неисправностьy tractor control unit (TCU)

Причина: Front hitch position voltage is greater than 4.7 V for 2 seconds.

Возможные причины отказа:

1. The front axle position датчик failed.

2. The front axle position датчик wiring is shorted to power.

Причина: Front hitch position voltage is less than 0.2 V for 2 seconds.

Возможные причины отказа:

1. The front axle position potentiometer failed.

2. The front axle position potentiometer wiring is замкнуто на массу.

Причина:

1. Both common and external front hitch up debounced переключательes are simultaneously on for 1 second.

2. All three переключательes are simultaneously on for 0.5 seconds.

Возможные причины отказа:

1. Неисправностьy front hitch common переключатель.

2. Неисправностьy external up переключатель отказ.

Решение:

1. Replace both переключательes. Test operation of the front axle system.

A. Неисправность code re-displays. Reinstall the original переключательes, and submit a concern to ASIST.

B. Неисправность code does not re-display. Clear all fault codes, and return unit to field operation.

Причина:

1. Both common and external front hitch down debounced переключательes are simultaneously on for 1 second.

2. All three переключательes are simultaneously on for 0.5 seconds.

Возможные причины отказа:

1. Неисправностьy front hitch common переключатель.

2. Неисправностьy external down переключатель отказ.

Решение:

1. Replace both переключательes. Test operation of the front axle system.

A. Неисправность code re-displays. Reinstall the original переключательes, and submit a concern to ASIST.

B. Неисправность code does not re-display. Clear all fault codes, and return unit to field operation.

Причина: The front hitch common, external front hitch down, and external front hitch up debounced переключательes are simultaneously off for 1 second.

Возможные причины отказа:

1. Неисправностьy front hitch common переключатель.

Решение:

1. Replace front hitch common переключатель. Test operation of the front axle system.

A. Неисправность code re-displays. Reinstall the original переключательes, and submit a concern to ASIST.

B. Неисправность code does not re-display. Clear all fault codes, and return unit to field operation.

Примечание: Front hitch calibration is required to properly display hitch position on the tractor instrumentation.

Причина: Front hitch calibration is required.

Возможные причины отказа:

1. Front hitch не откалиброван

2. Неисправностьy контроллер

Решение:

1. Calibrate the front hitch. If the front hitch was не откалиброван after a change of a контроллер or a front hitch component, calibrate the front hitch calibration. If the front hitch was calibrated, repeat front hitch calibration.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Submit a concern to ASIST.

Причина: Tractor speed exceeded 0.5 km/h (0.3 mph) during front hitch calibration.

Возможные причины отказа:

1. Front hitch не откалиброван, tractor moved during calibration procedure.

2. Неисправностьy контроллер

Решение:

1. Repeat front hitch calibration.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Submit a concern to ASIST.

Причина: Двигатель speed for front hitch calibration is valid if it is greater than or equal to 600 RPM, otherwise it is not valid – that is, if двигатель speed is less than or equal to 550 RPM ( 50 RPM hysteresis).

Возможные причины отказа:

1. Front hitch не откалиброван, низкий двигатель speed detected during calibration procedure.

2. Неисправностьy контроллер

Решение:

1. Repeat the front hitch calibration.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Submit a concern to ASIST.

Причина: Front hitch, during calibration, detected reversed front hitch position minimum and maximum position values.

Возможные причины отказа:

1. Front hitch не откалиброван correctly.

2. Неисправностьy контроллер

Решение:

1. Проверить the front hitch wiring and hitch position potentiometer installation. Repeat the front hitch calibration procedure.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Submit a concern to ASIST.

Причина: Front hitch calibration exceeded the two minute calibration time limit. The front hitch did not move or moved too sнизкийly during calibration.

Возможные причины отказа:

1. Front hitch не откалиброван, calibration exceeded the two minute calibration time limit.

2. Неисправностьy контроллер

Решение:

1. Repeat the front hitch calibration.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Submit a concern to ASIST.

Причина: Front PTO cab переключатель is on during power up for more than 10 milliseconds.

Возможные причины отказа:

1. Front PTO переключатель is on

2. Software execution error.

Решение:

1. Move front PTO переключатель to the off position. Clear all fault codes. Проверить if the fault condition is still active.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Go to Step 2.

2. Replace the front PTO переключатель in the armrest console. Clear all fault codes. Test operation of the PTO переключатель.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Submit a concern to ASIST.

Причина: Front PTO cab normally open and normally closed переключательes are both open for more than 30 seconds.

Возможные причины отказа:

1. Неисправностьy front PTO cab переключатель

Решение:

1. Проверить if the fault condition is still active. Erase all fault codes. Test front PTO operation.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Replace the front PTO переключатель.

Причина: Front PTO cab normally open and normally closed переключательes are both closed for more than 30 seconds.

Возможные причины отказа:

1. Неисправностьy front PTO cab переключатель

Решение:

1. Проверить if the fault condition is still active. Erase all fault codes. Test front PTO operation.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Replace the front PTO переключатель.

Причина: The соленоид coil, the высокий side driver, or the низкий side driver may be замкнуто на массу for 150 milliseconds.

Возможные причины отказа:

1. 12VU2 voltage to tractor control unit (TCU) is низкий.

2. Front PTO соленоид has an internal обрыв цепи.

3. Wiring from the tractor control unit (TCU) to the front PTO соленоид has an обрыв цепи or is замкнуто на массу.

Причина: The соленоид coil, the высокий side driver, or the низкий side driver may be shorted to B+ for 150 milliseconds.

Возможные причины отказа:

1. Front PTO соленоид is shorted to B+.

Причина: Driver is beнизкий the BSP calculated voltage limit for 10 milliseconds.

Возможные причины отказа:

1. Неисправностьy harness

2. Неисправностьy tractor control unit (TCU)

Решение:

1. Проверить if the fault condition is still active. Erase all fault codes. Test front PTO operation.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Continue to step 2.

2. Проверить if other fault codes related to the низкий side driver are active.

A. Other низкий side driver fault codes active. Resolve the other fault codes first.

B. No other низкий side driver fault codes active. Submit a concern to ASIST. The низкий side driver is in the tractor control unit (TCU).

Причина: Front PTO переключатель is in the on state with the двигатель off for up to 500 milliseconds.

Возможные причины отказа:

1. Front PTO переключатель is on

2. Software execution error.

Решение:

1. Проверить if the fault condition is still active. Move the front PTO переключатель to off position. Clear all fault codes.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Go to step 2.

2. Replace the front PTO переключатель in the armrest console. Clear all fault codes. Test operation of the front PTO переключатель.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Submit a concern to ASIST.

Причина: If the низкий side front PTO соленоид is grounded for 250 milliseconds.

Возможные причины отказа:

1. Неисправностьy harness

2. Неисправностьy tractor control unit (TCU)

Решение:

1. Проверить if the fault condition is still active. Erase all fault codes. Test front PTO operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor for continuing problem.

B. Неисправность code re-displays. Continue to step 2.

2. Проверить if other fault codes related to the низкий side driver are active.

A. Other низкий side driver fault codes active. Resolve the other fault codes first.

B. No other низкий side driver fault codes active. Submit a concern to ASIST. The низкий side driver is in the tractor control unit (TCU).

Причина: The низкий side front PTO соленоид is grounded for 250 milliseconds.

Возможные причины отказа:

1. The front PTO низкий side of the соленоид is замкнуто на массу.

2. The PTO wiring to the низкий side соленоид is замкнуто на массу.

Причина: Voltage is beнизкий 5 V for 400 milliseconds

Возможные причины отказа:

1. Bнизкийn fuse

2. Неисправностьy tractor control unit (TCU)

Решение:

1. Проверить if other низкий voltage supply faults codes are active.

A. Other низкий power supply fault codes active. Resolve the other voltage supply related fault codes first.

B. Other низкий power supply fault codes not active. Continue to step 2.

2. Проверить if the fault condition is still active. Erase all fault codes. Test front PTO operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor for continuing problem.

B. Неисправность code re-displays. Continue to step 3.

3. Проверить fuse #28.

A. Fuse #28 is bнизкийn. Replace fuse #28. Erase fault code and return unit to field operation.

B. Fuse #28 is okay. Contact ASIST before replacing tractor control unit (TCU).

Причина: The front suspension pump-not-tank соленоид or the wiring to the соленоид has an обрыв цепи or is замкнуто на массу.

Возможные причины отказа:

1. Front suspension pump/not tank соленоид has an internal обрыв цепи.

2. Wiring from the tractor control unit (TCU) to the front suspension pump/not tank соленоид has an обрыв цепи or is замкнуто на массу.

Причина: The front suspension rod соленоид or the wiring to the соленоид has an обрыв цепи or is замкнуто на массу.

Возможные причины отказа:

1. Front suspension rod соленоид has an internal обрыв цепи.

2. Wiring from the tractor control unit (TCU) to the front suspension rod соленоид has an обрыв цепи or is замкнуто на массу.

Причина: The front suspension piston соленоид or the wiring to the соленоид has an обрыв цепи or is замкнуто на массу.

Возможные причины отказа:

1. Front suspension piston соленоид has an internal обрыв цепи.

2. Wiring from the tractor control unit (TCU) to the front suspension piston соленоид has an обрыв цепи or is замкнуто на массу.

Причина: Front axle potentiometer is above the высокий limit threshold continuously for more than one second. Возможные причины отказа:

1. The front suspension position is above the absolute limit.

2. The front axle position датчик failed.

3. The front axle position датчик wiring is shorted to power.

Причина: Front axle potentiometer is beнизкий the низкийer limit threshold continuously for more than 1 second.

Возможные причины отказа:

1. The front suspension position is beнизкий the absolute limit.

2. The front axle position датчик failed.

3. The front axle position датчик wiring is shorted to power.

Примечание: If any other 10000 series front suspended axle fault codes are displayed, folнизкий the fault code troubleshooting for these fault codes first.

Причина: After the pressure drops in the rod side, the piston соленоид and pump соленоид are commanded on, but the suspension will not raise.

Возможные причины отказа:

1. Tractor PFC pump system problem.

2. Excessive load or mechanical obstruction.

3. Suspended axle pump/not tank соленоид failed or stuck

4. Suspended axle piston соленоид failed or stuck

5. Suspended axle lockout соленоид failed or stuck

6. Wiring problem.

7. Tractor control unit (TCU) failed.

Примечание: If any other 10000 series front suspended axle fault codes are displayed, folнизкий the fault code troubleshooting for these fault codes first.

Причина: After the pressure drops in the piston side, the rod соленоид and the pump соленоид are commanded on, but the suspension will not низкийer.

Возможные причины отказа:

1. Excessive load or mechanical obstruction.

2. Rod соленоид failed or stuck

3. Piston соленоид failed or stuck

4. Lockout соленоид failed or stuck

5. Wiring problem.

6. Tactor control unit (TCU) failed.

Причина: Piston pressure датчик is greater than 25000 kPa (3626 psi) continuously for more than 250 milliseconds.

Возможные причины отказа:

1. Pressure датчик or wiring shorted to power.

2. Pressure датчик failed.

Причина: Piston pressure датчик is less than 1514 kPa (220 psi) contiguously for more than 150 milliseconds

Возможные причины отказа:

1. Pressure датчик wiring has обрыв цепи or wiring замкнуто на массу.

2. Pressure датчик failed.

Причина: Rod pressure датчик is greater than 25000 kPa (3626 psi) continuously for more than 250 milliseconds.

Возможные причины отказа:

1. Pressure датчик or wiring shorted to power.

2. Pressure датчик failed.

Причина: Rod pressure датчик is less than 1514 kPa (220 psi) continuously for more than 150 milliseconds

Возможные причины отказа:

1. Pressure датчик wiring has обрыв цепи or wiring замкнуто на массу.

2. Pressure датчик failed.

Причина: For 4500 milliseconds, the rod side клапан and the pump клапан are on, but the rod side pressure is not increasing.

Возможные причины отказа:

1. Electrical fault in system

2. Неисправностьy wiring

3. Rod соленоид клапан неисправность

Причина: For 4500 milliseconds, the piston side клапан and the pump клапан are on, but the piston side pressure is not increasing.

Возможные причины отказа:

1. Electrical fault in system

2. Неисправностьy wiring

3. Piston соленоид клапан неисправность

Возможные причины отказа:

1. Suspended front axle не откалиброван.

Причина: The front suspension lock клапан соленоид or the wiring to the соленоид has an обрыв цепи or is замкнуто на массу.

Возможные причины отказа:

1. Front suspension lock клапан соленоид has an internal обрыв цепи.

2. Wiring from the tractor control unit (TCU) to the front suspension lock клапан соленоид has an обрыв цепи or is замкнуто на массу.

Причина: The front suspension переключатель is in the error state for 10 seconds.

Возможные причины отказа:

1. Неисправностьy front suspension переключатель

2. некорректный armrest configuration

3. Неисправностьy connector

Причина: The front suspension переключатель CAN data is set to not available state for 10 milliseconds.

Возможные причины отказа:

1. CAN-шина communication error

2. Неисправностьy front suspension переключатель

3. Неисправностьy connector

Причина: Front suspension rod side соленоид is in an over current condition: driver is замкнуто на массу or coil is shorted.

Возможные причины отказа:

1. Front suspension rod соленоид coil is shorted.

2. Wiring from the tractor control unit (TCU) to the front suspension rod соленоид has a короткое замыкание на массу.

Причина: Front suspension piston side соленоид is in an over current condition: driver is замкнуто на массу or coil is shorted.

Возможные причины отказа:

1. Front suspension piston соленоид coil is shorted.

2. Wiring from the tractor control unit (TCU) to the front suspension piston соленоид has a короткое замыкание на массу.

Причина: Front suspension lockout соленоид is in an over current condition: driver is замкнуто на массу or coil is shorted.

Возможные причины отказа:

1. Front suspension lock соленоид coil is shorted.

2. Wiring from the tractor control unit (TCU) to the front suspension lockout соленоид has a короткое замыкание на массу.

Причина: Voltage is beнизкий 5.0 volts for 400 milliseconds

Возможные причины отказа:

1. Bнизкийn fuse

2. Неисправностьy tractor control unit (TCU)

Причина: Voltage is beнизкий 5.0 volts for 400 milliseconds.

Возможные причины отказа:

1. Bнизкийn fuse

2. Неисправностьy tractor control unit (TCU)

Причина: Voltage is beнизкий 5.0 volts for 400 milliseconds.

Возможные причины отказа:

1. Bнизкийn fuse

2. Неисправностьy tractor control unit (TCU)

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Keyпереключатель is on, двигатель RPM is greater than 500 and the трансмиссия oil filter переключатель is closed to ground during the first 5 seconds.

Возможные причины отказа:

1. Неисправностьy трансмиссия oil filter restriction переключатель

2. Short in переключатель wiring harness

3. Неисправностьy instrument cluster (ICU)

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Keyпереключатель is on, двигатель speed is greater than 500 RPM, and the гидравлический oil filter переключатель is closed to ground during the first 5 seconds.

Возможные причины отказа:

1. Неисправностьy гидравлический oil filter restriction переключатель

2. Short in переключатель wiring harness

3. Неисправностьy instrument cluster (ICU).

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: PTO shaft speed data is “ERROR” or “NOT AVAILABLE” state from PTO for 3 seconds. PTO disabled.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy PTO shaft speed датчик

3. Неисправностьy harness

4. Неисправностьy tractor control unit (TCU)

Причина: GOV двигатель speed data is “ERROR” or “NOT AVAILABLE” state for 3 seconds.

Возможные причины отказа:

1. Контроллер communication error

2. Неисправностьy двигатель speed датчик

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Двигатель overspeed has been detected. Overspeed can occur both without a defect in a component (for example, when downhill driving) and with a defect (for example, when the двигатель контроллер has an error.) This fault code does not necessarily indicate an error condition but is used more for information purposes and to inhibit handling.

Возможные причины отказа:

1. Information code indicating that двигатель overspeed has been detected

Причина: Двигатель давление масла data is “ERROR” or “NOT AVAILABLE” state from the GOV for 3 seconds.

Возможные причины отказа:

1. Контроллер communication error

2. Неисправностьy двигатель давление масла датчик

Context: The loss of valid двигатель hours can indicate a неисправен instrument cluster (ICU). If the loss of valid двигатель hours is the only indication of a problem with instrument cluster (ICU), continue field operation. Двигатель hours will accumulate from this point forward. Contact ASIST regarding recovery of lost valid двигатель hours.

Примечание: When the cause of the error code has been rectified, clear the error code and test for normal operation.

Причина: PTO CAN data bus fault

Возможные причины отказа:

1. CAN-шина communication problem

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Communication lost with vehicle data bus and all other контроллерs.

Возможные причины отказа:

1. CAN-шина communication problem

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: TRANSMISSION CAN data bus fault

Возможные причины отказа:

1. CAN-шина communication problem

Причина: Двигатель температура охлаждающей жидкости data is “ERROR” or “NOT AVAILABLE” from GOV for 5 seconds.

Возможные причины отказа:

1. Контроллер communication error

2. Неисправностьy двигатель температура охлаждающей жидкости датчик

Причина: Двигатель intake manifold temperature data is “ERROR” or “NOT AVAILABLE” state from GOV for 5 seconds.

Возможные причины отказа:

1. Контроллер communication error

2. Неисправностьy двигатель intake air temperature датчик

Context: This is an informational fault code. A 30 second or 5 second timer expired and двигатель is shutdown. The tractor display will show a message for the problem system. Проверить active fault codes for the identified system.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: Сигнал beнизкий 0.125 V for 15 seconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy fuel tank level sender

3. Неисправностьy harness

4. Неисправностьy instrument cluster

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: GOV CAN data bus fault for 2 seconds

Возможные причины отказа:

1. CAN-шина communication problem

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: ATC CAN data bus fault

Возможные причины отказа:

1. CAN-шина communication problem

Причина: Loss of communication with tractor control unit (TCU), which controls the secondary steering system.

Возможные причины отказа:

1. Контроллер communication error

Причина: Loss of communication with tractor control unit (TCU), which controls the secondary steering system.

Возможные причины отказа:

1. Контроллер communication error

Причина: Возможные причины отказа:

1. Контроллер communication error

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy EHR клапан section

Примечание: When the cause of the error code is corrected, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR lever не откалиброван

2. Неисправностьy контроллер

Решение:

1. Проверить if the EHR levers were calibrated.

If the EHR lever was не откалиброван after a change of a контроллер or a EHR control unit, perform the EHR lever calibration procedure.

If the EHR lever was calibrated, repeat the EHR lever calibration procedure.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Submit a concern to ASIST.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. CAN-шина communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. Неисправностьy connector

2. CAN-шина interference

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. Other EHR error code(s) detected.

2. Неисправностьy EHR клапан

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy harness

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. External power supply connected

2. Неисправностьy charging system

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Remote клапан manually operated

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. Неисправностьy spool position potentiometer

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. A клапан section was recently replaced and the tie bolts over torqued

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Ignition переключательed off during EHR клапан operation

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. CAN Bus communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. Неисправностьy connector

2. Can bus interference

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. Other EHR error code(s) detected.

2. Неисправностьy EHR клапан

Решение:

1. Проверить for other EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy harness

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. External power supply connected

2. Неисправностьy charging system

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Remote клапан manually operated

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. Неисправностьy spool position potentiometer

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. A клапан section was recently replaced and the tie bolts over torqued

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Ignition переключательed off during EHR клапан operation

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. CAN Bus communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. Неисправностьy connector

2. CAN-шина interference

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. Other EHR error code(s) detected.

2. Неисправностьy EHR клапан

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy harness

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. External power supply connected

2. Неисправностьy charging system

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. Remote клапан manually operated

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. Неисправностьy spool position potentiometer

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. A клапан section was recently replaced and the tie bolts over torqued

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Ignition переключательed off during EHR клапан operation

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. CAN Bus communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. Неисправностьy connector

2. Can bus interference

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. Other EHR error code(s) detected.

2. Неисправностьy EHR клапан

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy harness

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. External power supply connected

2. Неисправностьy charging system

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Remote клапан manually operated

2. Неисправностьy EHR клапан

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. Неисправностьy spool position potentiometer

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. A клапан section was recently replaced and the tie bolts over torqued

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Ignition переключательed off during EHR клапан operation

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Возможные причины отказа:

1. CAN Bus communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. Неисправностьy connector

2. Can bus interference

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other EHR error code(s).

A. Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

B. If the fault is still present, continue to step 2

2. Download the correct level of software and configure the EHR клапан.

A. System operation normal. No fault codes recorded. Troubleshooting is complete.

B. If the fault reoccurs, remove, replace, and configure the EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина:

Возможные причины отказа:

1. Other EHR error code(s) detected.

2. Неисправностьy EHR клапан

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy harness

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. External power supply connected

2. Неисправностьy charging system

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Remote клапан manually operated

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. Неисправностьy spool position potentiometer

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. A клапан section was recently replaced and the tie bolts over torqued

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. Ignition переключательed off during EHR клапан operation

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code is corrected, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR lever не откалиброван

2. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR lever не откалиброван

2. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR lever не откалиброван

2. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR lever не откалиброван

2. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. CAN-шина communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. CAN-шина communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. CAN-шина communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. CAN-шина communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. CAN-шина communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. EHR клапан не откалиброван

2. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR клапан не откалиброван

2. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR клапан не откалиброван

2. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR клапан не откалиброван

2. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR клапан не откалиброван

2. Неисправностьy контроллер

Возможные причины отказа:

1. CAN Bus communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Возможные причины отказа:

1. Неисправностьy connector

2. CAN-шина interference

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. Other EHR error code(s) detected.

2. Неисправностьy EHR клапан

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy harness

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. External power supply connected

2. Неисправностьy charging system

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: See above.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. некорректный гидравлический pressure

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. Remote клапан manually operated

2. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EEPROM error

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. Неисправностьy spool position potentiometer

2. Неисправностьy EHR клапан section

Решение:

1. Проверить for other active EHR error code(s).

Make a note of the error code(s), clear the error code(s) and test the system for normal operation.

A. Неисправность code does not re-display. Return unit to field operation and monitor.

B. Неисправность codes re-displays. Continue to step 2.

2. Download the correct level of software and configure the EHR клапан.

A. System operates normally: no fault codes display. Return unit to field operation.

B. Неисправность codes re-displays. Install and configure a new EHR клапан section.

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. A клапан section was recently replaced and the tie bolts over torqued

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Примечание: Folнизкий the maintenance schedules in operator manual for гидравлический fluid and filter change intervals. Improper maintenance can lead to sticking клапан spools.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. Ignition переключательed off during EHR клапан operation

2. Stuck spool due to contamination

3. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR lever не откалиброван

2. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR lever не откалиброван

2. Неисправностьy контроллер

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. CAN-шина communication problem

2. Неисправностьy connector

3. Неисправностьy harness

4. Неисправностьy EHR клапан

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Возможные причины отказа:

1. EHR клапан не откалиброван

2. Неисправностьy контроллер

Причина: Датчик feedback voltage was greater than 4.5 V.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy harness

3. Неисправностьy implement pot

Причина: Датчик feedback voltage was less than 0.25 V.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy harness

3. Неисправностьy implement pot

Причина: Датчик feedback voltage was greater than 4.5 V.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy harness

3. Неисправностьy implement pot

Причина: Датчик feedback voltage was less than 0.25 V.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy harness

3. Неисправностьy implement pot

Причина: Низкийer delta depth is greater than 10% for more than 25 seconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Mis-adjusted or damaged linkage

3. Неисправностьy implement pot

Причина: Raise delta depth is greater than 10% for more than 25 seconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Mis-adjusted or damaged linkage

3. Неисправностьy implement pot

Причина: PTO clutch frequency is less than the PTO shaft size frequency and both frequencies are positive for 200 milliseconds.

Возможные причины отказа:

1. Wiring is swapped between shaft size and speed датчикs.

Решение:

1. Проверить датчик wiring.

A. Wiring is swapped. Correct wiring. Clear all fault codes, and return unit to field operation.

B. Wiring is correct. Submit a concern to ASIST.

Причина: The data bus сигналed that the PTO переключатель is on during power up.

Возможные причины отказа:

1. PTO переключатель is on

2. Software execution error.

Решение:

1. Move PTO переключатель to off position. Clear all fault codes. Проверить if the fault condition is still active.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Go to step 2.

2. Replace the PTO переключатель in the armrest console. Clear all fault codes. Test operation of the PTO переключатель.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays. Submit a concern to ASIST.

Причина: If the PTO переключатель and the remote PTO fender переключатель are engaged on within 2 seconds apart, the PTO will default to the off condition.

Возможные причины отказа:

1. Operational cause.

Решение:

1. Move both the PTO переключатель and the remote PTO fender переключатель the off position for 10 seconds. Erase fault code and test system operation.

A. Неисправность code does not redisplay. Return unit to field operation.

B. Неисправность code redisplays. Submit a concern to ASIST.

Причина: If the received CAN data for the Auto PTO переключатель is in the error state for ten milliseconds.

Возможные причины отказа:

1. CAN data received for the Auto PTO переключатель is in error for ten milliseconds.

Решение:

1. Shutdown the двигатель. Restart двигатель and raise hitch. Erase the fault code. Press and release the Auto PTO переключатель for one second after the PTO is переключательed on and wheel speed is above 0.5 km/h (0.3 mph) to start the Auto PTO . Проверить system operation.

A. Auto PTO has resumed normal operation. Неисправность code does not redisplay.Return unit to field operation.

B. Неисправность code redisplays. Submit a concern to ASIST.

Причина: The Auto PTO переключатель is on for more than 10 seconds (after power up).

Возможные причины отказа:

1. The Auto PTO переключатель is on for more than 10 seconds (after power up).

Решение:

1. Shutdown the двигатель. Restart двигатель and raise hitch. Erase the fault code. Press and release the Auto PTO переключатель for one second after the PTO is переключательed on and wheel speed is above 0.5 km/h (0.3 mph) to start the Auto PTO. Проверить system operation.

A. Auto PTO has resumed normal operation. Неисправность code does not redisplay.Return unit to field operation.

B. Неисправность code redisplays. Submit a concern to ASIST.

Причина: See beнизкий.

Возможные причины отказа:

1. This fault will occur when the remote PTO fender normally open (NO) and normally closed (NC) переключательes are both closed for more than 150 ms.

Причина: See beнизкий.

Возможные причины отказа:

1. This fault will occur when the remote PTO fender normally open (NO) and normally closed (NC) переключательes are both open for more than 5.0 s .

Решение:

1. Use the monitor screen function on the electronic service tool (EST) to check the PTO fender переключатель and PTO system status. Refer to the EST user guide.

A. PTO fender переключатель not operating correctly. Replace the PTO fender переключатель. Return unit to field operation.

B. PTO fender переключатель operating correctly. Return unit to field operation and monitor for recurring problem. If the error reoccurs, submit concern to ASIST.

Причина: See beнизкий.

Возможные причины отказа:

1. This fault occurs when the remote PTO fender переключатель is on for more than 10 s.

Решение:

1. Use the monitor screen function in the electronic service tool (EST) to check the PTO fender переключатель and PTO system status. Refer to the EST user guide.

A. PTO fender переключатель not operating correctly. Replace the PTO fender переключатель. Return unit to field operation.

B. PTO fender переключатель operating correctly.Return unit to field operation and monitor for recurring fault. If the fault code reoccurs, submit a concern to ASIST.

Причина: See beнизкий.

Возможные причины отказа:

1. This fault occurs when the remote PTO fender normally open (NO) and normally closed (NC) переключательes are both open for more than 150 ms.

Решение:

1. Use the monitor screen function in the electronic service tool (EST) to check the PTO fender переключатель and PTO system status. Refer to the EST user guide.

A. PTO fender переключатель not operating correctly. Replace the PTO fender переключатель. Return unit to field operation.

B. PTO fender переключатель operating correctly.Return unit to field operation and monitor fort recurring problem. If the fault code reoccurs, submit a concern to ASIST.

Причина: The tractor control unit (TCU) has detected a короткое замыкание на массу at the PTO соленоид.

Возможные причины отказа:

1. The PTO соленоид is замкнуто на массу.

2. The PTO wiring to the соленоид is замкнуто на массу.

Примечание: When the cause of the error code has been rectified, clear the error code and test the system for normal operation.

Причина: The соленоид coil, the высокий side driver, or the низкий side driver may be shorted to B+ for 150 milliseconds.

Возможные причины отказа:

1. Неисправностьy соленоид

2. Неисправностьy harness

3. Неисправностьy tractor control unit (TCU)

Причина: The tractor control unit (TCU) is not sensing current at the PTO соленоид and the driver is on.

Возможные причины отказа:

1. The PTO соленоид has обрыв цепи.

2. Bad PTO соленоид

Причина: The tractor control unit (TCU) monitors the PTO clutch input and output speed. This fault code is recorded when the difference between the input and output speed are beyond a preset limit: the tractor control unit (TCU) detects excessive slip.

Возможные причины отказа:

1. PTO load is too heavy.

2. PTO clutch pressure is слишком низкий.

3. PTO speed датчик or wiring to speed датчик has отказ.

4. некорректный двигатель RPM сигнал from the alternator.

Причина: The двигатель speed is at 0 RPM and the PTO is in the On state.

Возможные причины отказа:

1. Двигатель is either stalled out or has been shutdown.

Решение:

1. Place the PTO переключатель in the off position. Restart the двигатель.

Erase all fault codes. Test operation of the PTO.

A. Неисправность code does not re-display. Return unit to field operation.

B. Неисправность code re-displays with the двигатель running. Submit a concern to ASIST.

Причина: The tractor contro unit (TCU) monitors the PTO clutch input and output speed. This fault code is recorded if the tractor control unit (TCU) detects PTO shaft rotation after the PTO переключатель has been in the off position for 45 seconds.

Возможные причины отказа:

1. Implement attached to PTO shaft is causing the PTO to turn.

2. Гидравлический pressure still present due to sticking клапан spool.

3. PTO brake friction plates and disc springs require replacement.

Причина: The tractor control unit (TCU) monitors the PTO clutch input and output speed. This fault code is recorded if the tractor control unit (TCU) does not detect PTO shaft rotation after the PTO переключатель has been in the on position for 3.6 seconds.

Возможные причины отказа:

1. Implement attached to PTO shaft has the shaft locked.

2. PTO соленоид is not energized.

3. PTO клапан spool is stuck.

4. PTO clutch pressure слишком низкий.

5. PTO speed датчик or wiring harness отказ.

Причина: The tractor control unit (TCU) monitors the PTO clutch output speed. This fault code is recorded if the tractor control unit (TCU) detects PTO shaft rotation with the PTO переключатель in the Off position and no двигатель RPM.

Возможные причины отказа:

1. Implement attached to PTO shaft is causing the PTO to turn.

2. Гидравлический pressure still present due to sticking клапан spool.

3. PTO brake friction plates and disc springs require replacement.

Причина: The tractor control unit (TCU) monitors the PTO clutch input speed. This fault code is recorded when the PTO does not reach lock up speed within 6 seconds of being turned On.

Возможные причины отказа:

1. PTO load is too heavy.

2. PTO clutch pressure is слишком низкий.

3. PTO соленоид is not energized.

4. PTO speed датчик or wiring to speed датчик has отказ.

5. некорректный двигатель RPM сигнал.

Причина: PTO is in the on state and is configured as a two speed and no shaft size frequency is detected for 10 seconds.

Возможные причины отказа:

1. The PTO configuration is некорректный.

Решение:

1. Change the PTO configuration to single speed PTO.

Test PTO system operation.

A. Неисправность code does not redisplay. Return unit to field operation.

B. Неисправность code redisplays. Submit a concern to ASIST.

Причина: PTO is in the on state and is configured as one speed and the shaft size frequency was detected for 1 second.

Возможные причины отказа:

1. The PTO configuration is некорректный.

Решение:

1. Change the PTO configuration to two speed PTO.

Test PTO system operation.

A. Неисправность code does not redisplay. Return unit to field operation.

B. Неисправность code redisplays. Submit a concern to ASIST.

Примечание: This is an informational fault code.

Причина: The Auto PTO function is cancelled if any of the folнизкийing conditions are present:

– The tractor is stopped for more than 10 seconds with the hitch in the raised position.

– The operator leaves the seat for 2 seconds or more.

– The PTO is переключательed off.

– The tractor is moving (wheel speed) faster than 0.5 km/h (0.3 mph) and the hitch is in the raised position for more than 2 minutes.

Причина: PTO переключатель is in the on state with the двигатель off for ten milliseconds.

Возможные причины отказа:

1. PTO переключатель in on position when двигатель is off.

Решение:

1. Move PTO переключатель to off position.

Test PTO system operation.

A. Неисправность code does not redisplay. Return unit to field operation.

B. Неисправность code redisplays. Submit a concern to ASIST.

Причина: 12VS2 voltage supply to tractor control unit is низкий.

Возможные причины отказа:

1. Battery низкое напряжение

2. Alternator regulator неисправность

3. Bad connection at контроллер

Причина: The tractor control unit (TCU) has detected a короткое замыкание на массу at the PTO соленоид низкий side.

Возможные причины отказа:

1. The PTO соленоид is замкнуто на массу.

2. The PTO wiring to the соленоид is замкнуто на массу.

Причина: Voltage above 4.5 V for 0.3 sec when there is no frequency.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy PTO shaft speed датчик

3. Неисправностьy harness

Причина: Voltage beнизкий 0.5 V for 0.3 second when there is no frequency.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy PTO shaft speed датчик

3. Неисправностьy harness

Причина: Voltage above 4.5 V for 0.3 s when there is no frequency.

Возможные причины отказа:

1. Damaged harness or connector.

Причина: Voltage beнизкий 0.5 V for 0.3 second when there is no frequency.

Возможные причины отказа:

1. Damaged harness or connector.

Причина: 12VF3 voltage supply to tractor control unit is низкий. If the voltage is beнизкий 5.0 V for 400 milliseconds.

Возможные причины отказа:

1. Battery низкое напряжение

2. Alternator regulator неисправность

3. Bad connection at контроллер

Context: This is an informational fault code. The primary steering pressure dropped низкий enough to cause the secondary steering system to be activated. If the fault code is recorded multiple times the primary steering system pressure needs to be checked. See steering system pressure specifications in service manual.

Причина: Primary steering pressure is less than 2068 kPa (300 psi), and the secondary steering system is running.

Причина: The secondary steering pressure is greater than 5 bar (72 psi) and the secondary steering pump is not running. It is possible the pressure is not leaking down completely in amount of time allotted for secondary pressure check. Неисправность code for informational purposes, no action required.

Причина: Primary steering pressure is less than 2068 kPa (20.7 bar) and the secondary steering system is not available.

Возможные причины отказа:

1. Неисправностьy connection.

Причина: Primary steering pressure датчик voltage is greater than 4.75 V volts for 150 msec

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy primary steering датчик

3. Неисправностьy harness

Причина: Primary steering pressure датчик voltage is greater than 0.25 V for 150 msec.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy primary steering pressure датчик

3. Неисправностьy harness

Причина: Secondary steering pump pressure is less than 1380 kPa (200 psi) after the secondary steering pump has run in test mode for 10 sec.

Возможные причины отказа:

1. Loss of pump drive

2. Failed pump

3. Excessive external leakage

4. Excessive internal leakage

Решение:

1. The secondary steering system is not building and maintaining adequate гидравлический pressure. See the service manual for secondary steering operation.

Причина: Secondary steering pressure датчик voltage is greater than 4.75 V for 150 msec. Short to power on the secondary steering датчик.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy secondary steering датчик

3. Неисправностьy harness

Причина: Secondary steering pressure датчик voltage is less than 0.25 V for 150 msec. Open circuit or короткое замыкание на массу on the secondary steering pressure датчик.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy secondary steering pressure датчик

3. Неисправностьy harness

Причина: Driver is on and no current fнизкийing, or driver is off and load not detected. Open circuit or короткое замыкание на массу on the bypass соленоид.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy bypass соленоид

3. Неисправностьy harness

Причина: Voltage at the высокий side driver pin is высокий when the driver is commanded off. Short to power on the bypass клапан соленоид.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy bypass клапан соленоид

3. Неисправностьy harness

Причина: Secondary steering system bypass соленоид circuit is короткое замыкание на массу or is низкий resistance. Short to ground on the bypass клапан соленоид.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy bypass клапан соленоид

3. Неисправностьy harness

Причина: Secondary steering relay driver built in test (self test). Short to power on the secondary pump relay.

Возможные причины отказа:

1. Short to power in secondary pump relay circuit

2. Неисправностьy secondary pump relay

3. Неисправностьy tractor control unit (TCU)

Причина: Secondary steering relay driver built in test (self test). Open circuit on the pump driver relay.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy pump driver relay

3. Неисправностьy harness

Причина: Secondary steering system pump relay driver circuit is короткое замыкание на массу or is низкий resistance. Short to ground on the pump driver relay.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy pump driver relay

3. Неисправностьy harness

Причина: Voltage at the VF2 input is less than 9 V while not cranking the двигатель. Supply voltage is низкий to tractor control unit (TCU).

Возможные причины отказа:

1. Bнизкийn fuse

2. Неисправностьy connector

Решение:

1. Проверить for other error codes being displayed, that are related to низкий voltage

A. If any other error code is being displayed, continue to these tests.

B. If no other error code is displayed, continue to step 2

2. Проверить fuse number 44.

A. Fuse is bнизкийn, replace fuse.

B. Fuses are good. Examine all the tractor control unit (TCU) connectors. Make sure the connectors are properly connected and not damaged. Проверить wiring harness for damage. If no damage is located submit a concern to ASIST

Причина: System переключательed to the secondary operational mode and the secondary steering pressure will not rise above 3447 kPa (500 psi). Secondary steering system pressure is низкий.

Возможные причины отказа:

1. Loss of pump drive

2. Failed pump

3. Excessive external leakage

4. Excessive internal leakage

Решение:

1. Проверить for other error codes being displayed, that are related to secondary steering system.

A. If any other error code is being displayed, continue to these tests.

B. If no other error code is displayed, continue to step 2

2. The secondary steering system is not building and maintaining adequate гидравлический pressure. See the service manual for secondary steering operation.

Причина: NVM indicates the secondary steering system is not installed and any of the two components are detected. Bypass соленоид not обрыв цепи. Primary pressure датчик voltage is greater than 0.25 V. Secondary pressure датчик is greater than 0.25 V.

Возможные причины отказа:

1. Secondary steering system not configured properly

2. Tractor control unit (TCU) replaced and not configured with electronic service tool (EST) for secondary steering system.

Решение:

1. Secondary steering system not configured after replacement of tractor control unit (TCU). See calibration and configuration section of manual.

Причина: 12 V monitor detects less than 9 V (disabled during crank).

Возможные причины отказа:

1. Battery or alternator problem

2. Неисправностьy connector

Причина: 12 V monitor detects less than 9 V (disabled during crank).

Возможные причины отказа:

1. Battery or alternator problem

2. Неисправностьy connector

Решение:

1. Test battery and alternator systems before proceeding with troubleshooting.

A. Problem found with battery power, or charging circuit.

B. Battery is good and charging circuits are operating correctly.

2. Проверить all secondary steering circuit connections. Make sure connections are tight, not damaged or corroded.

A. Problem with secondary steering connections located and repaired.

B. The secondary steering connections look good. See service manual secondary steering service information.

Причина: 5 V reference monitor voltage is greater than 5.5 V or reference monitor is less than 4.5 V.

Возможные причины отказа:

1. Short circuit to ground or power source.

Причина: The двигатель is running and the crank input is высокий for 10 seconds.

Возможные причины отказа:

1. Неисправностьy ignition переключатель

2. Short to power in starting circuit

Причина: Foot throttle idle validation переключатель is closed and foot throttle position is < 0.7 V for 50 milleseconds, or foot throttle idle validation переключатель is open and the foot throttle position > 0.8 V for 50 milleseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy foot throttle pedal

3. Неисправностьy harness

4. Неисправностьy контроллер

Причина: Foot throttle position is > 4.5 V for 50 milleseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy foot throttle pedal

3. Неисправностьy harness

4. Неисправностьy контроллер

Причина: Foot throttle position is < 0.25 V for 50 milleseconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy foot throttle pedal

3. Неисправностьy harness

4. Неисправностьy контроллер

Причина: Hand throttle position received over the CAN-шина >250 or the hand throttle message has not been received from the armrest for 2.5 seconds.

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy foot throttle pedal

3. Неисправностьy harness

4. Неисправностьy контроллер

Context: The Двигатель Control Unit (ECU) generated an error from a fault associated with the Coolant temp датчик. This error could result from a сигнал вне диапазона or a сигнал that is either erratic or intermittent. When the ECU determines that the Coolant temp датчик temperature value is not valid, it will substitute another value to be used. In case of a defective Coolant temp датчик during двигатель warm-up, a default температура охлаждающей жидкости value is derived from the ramp of the currently logged датчик data. If an error would occur during normal двигатель operation, the oil temperature is used as the default value. If the Oil temp / press датчик is defective, 85 °C (185 °F) is substituted as the default value.

Причина: The Coolant temp датчик сигнал to the ECU is either erratic or intermittent.

Возможные причины отказа:

1. Неисправностьy Coolant temp датчик.

2. Неисправностьy electrical wiring or intermittent connection between Coolant temp датчик and ECU.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) generated an error from a fault associated with the Coolant temperature датчик. This error could result from a сигнал вне диапазона or a сигнал that is either erratic or intermittent. When the ECU determines that the Coolant temperature датчик temperature value is not valid, it will substitute another value to be used. In case of a defective Coolant temperature датчик during двигатель warm-up, a default температура охлаждающей жидкости value is derived from the ramp of the currently logged датчик data. If an error would occur during normal двигатель operation, the oil temperature is used as the default value. If the Oil temperature / pressure датчик is defective, 85 °C (185 °F) is substituted as the default value.

Причина: The Coolant temperature датчик сигнал to the ECU вне диапазона of the upper threshold limit.

Возможные причины отказа:

1. Неисправностьy Coolant temperature датчик.

2. Неисправностьy electrical wiring, short to высокий source or обрыв цепи condition.

3. Неисправностьy ECU, напряжение питанияs or grounds.

The Двигатель Control Unit (ECU) generated an error from a fault associated with the Coolant temperature датчик. This error could result from a сигнал вне диапазона or a сигнал that is either erratic or intermittent. When the ECU determines that the Coolant temperature датчик temperature value is not valid, it will substitute another value to be used. In case of a defective Coolant temperature датчик during двигатель warm-up, a default температура охлаждающей жидкости value is derived from the ramp of the currently logged датчик data. If an error would occur during normal двигатель operation, the oil temperature is used as the default value. If the Oil temperature / pressure датчик is defective, 85 °C (185 °F) is substituted as the default value.

Причина: The Coolant temperature датчик сигнал to the ECU вне диапазона of the низкийer threshold limit.

Возможные причины отказа:

1. Неисправностьy Coolant temperature датчик.

2. Неисправностьy electrical wiring, short to низкий source condition.

3. Неисправностьy ECU, напряжение питанияs.

Context: The Двигатель Control Unit (ECU) generated a fault when monitoring the temperature rise of the двигатель температура охлаждающей жидкости during a warm-up cycle. During the monitoring process, the start temp and the current coolant temp are compared against a warm-up cycle curve in the ECU. The fault is generated after a timer expires and the температура охлаждающей жидкости does not match the warm-up cycle curve. This test is carried out once per driving cycle and is stopped when the двигатель is in after-run mode.

Причина: The ECU has determined that the rise in температура охлаждающей жидкости is низкийer than expected during the двигатель warm-up cycle.

Возможные причины отказа:

1. Неисправностьy or inaccurate Coolant temp датчик.

2. Неисправностьy wiring, высокий resistance.

3. Very низкий ambient temperature.

4. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) generated an error from a fault associated with the Boost Pressure датчик. The Boost Pressure датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the temperature sensing function of the device. This error could result from a сигнал вне диапазона or a сигнал that is either erratic or intermittent. When the ECU determines that the Boost Pressure датчик value is not valid, it will substitute a default value of 29.96 °C (86 °F).

Причина: The Boost Pressure датчик сигнал to the ECU вне диапазона of the upper threshold limit.

Возможные причины отказа:

1. Неисправностьy датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) generated an error from a fault associated with the Boost Pressure датчик. The Boost Pressure датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the temperature sensing function of the device. This error could result from a сигнал вне диапазона or a сигнал that is either erratic or intermittent. When the ECU determines that the Boost Pressure датчик value is not valid, it will substitute a default value of 29.96 °C (86 °F).

Причина: The Boost Pressure датчик сигнал to the ECU вне диапазона of the низкийer threshold limit.

Возможные причины отказа:

1. Неисправностьy датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) generated an error from a fault associated with the Boost Pressure датчик. The Boost Pressure датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the temperature sensing function of the device. This error could result from a сигнал вне диапазона or a сигнал that is either erratic or intermittent. When the ECU determines that the Boost Pressure датчик value is not valid, it will substitute a default value of 29.96 °C (86 °F).

Причина: The Boost Pressure датчик сигнал to the ECU is either erratic or intermittent.

Возможные причины отказа:

1. Неисправностьy датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) has detected a fault associated with fuel temperature датчик. This error typically results from a сигнал that вне диапазона. When the ECU determines that the Fuel temperature датчик temperature value is недействительный, it will substitute the current температура охлаждающей жидкости value, or in the case of a defective Coolant temperature датчик , the value 19.96 ° C (67.9 °F) will be substituted.

Причина: The fuel temperature датчик сигнал to the ECU is out of the range of the upper threshold limit.

Возможные причины отказа:

1. Неисправностьy fuel temperature датчик.

2. Неисправностьy electrical wiring or short to высокий source or обрыв цепи condition.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) has generated a fault associated with Fuel temperature датчик . This error typically results from a сигнал that вне диапазона. When the ECU determines that the fuel temperature датчик temperature value is недействительный, it will substitute the current “Температура охлаждающей жидкости” value, or in the case of a defective Coolant temperature датчик , the value 19.96 °C (67.9 °F) will be substituted.

Причина: The Fuel temperature датчик сигнал to the ECU is out of the range of the низкийer threshold limit.

Возможные причины отказа:

1. Неисправностьy Fuel temperature датчик .

2. Неисправностьy electrical wiring or short to низкий source (ground).

3. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) generated an error from a fault associated with the Boost Pressure датчик. The Boost Pressure датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the pressure sensing function of the device. This error could result from a сигнал вне диапазона or a сигнал that is either erratic or intermittent. When the ECU determines that the Boost Pressure датчик value is not valid, it will substitute a default value of 270 kPa (39 psi).

Причина: The Boost Pressure датчик сигнал to the ECU вне диапазона of the upper threshold limit.

Возможные причины отказа:

1. Неисправностьy датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy ECU, напряжение питанияs or grounds.

The Двигатель Control Unit (ECU) generated an error from a fault associated with the Boost Pressure датчик. The Boost Pressure датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the pressure sensing function of the device. This error could result from a сигнал вне диапазона or a сигнал that is either erratic or intermittent. When the ECU determines that the Boost Pressure датчик value is not valid, it will substitute a default value of 270 kPa (39 psi).

Причина: The Boost Pressure датчик сигнал to the ECU and the Atmospheric Pressure Датчик (APS) internal to the ECU do not agree on двигатель startup.

Возможные причины отказа:

1. Неисправностьy датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy ECU with integrated APS, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) generated a fault associated with the Oil temp / press датчик. The Oil temp / press датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the pressure sensing function of the device. This fault is a result of a plausibility check of the двигатель running чрезвычайно низкий давление масла. All subsequent двигатель error states are frozen in case there is a датчик power supply ( 5 volts dc) error. The ECU only starts the plausibility check if there are no датчик power supply ( 5 volts dc) or Analog to Digital Converter (ADC) сигнал or CAN message processing errors detected.

Причина: The Oil temp / press датчик pressure сигнал to the ECU is operating at the extreme низкий end of the сигнал range.

Возможные причины отказа:

1. Неисправностьy Oil temp / press датчик.

2. Неисправностьy electrical wiring.

3. Неисправностьy ECU, напряжение питанияs or grounds.

4. Неисправностьy двигатель lubrication system.

5. Низкий двигатель oil level.

Context: The Двигатель Control Unit (ECU) generated a fault associated with the Oil temp / press датчик. The Oil temp / press датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the pressure sensing function of the device. This error could result from a сигнал вне диапазона or a plausibility check (давление масла слишком высокий). The plausibility check is only started if there are no датчик power supply ( 5 volts dc) or Analog to Digital Converter (ADC) сигнал errors detected.

Причина: The Oil temp / press датчик сигнал to the ECU вне диапазона of the upper threshold limit.

Возможные причины отказа:

1. Неисправностьy Oil temp / press датчик.

2. Неисправностьy electrical wiring, сигнал short to высокий source or обрыв цепи condition.

3. Неисправностьy ECU, напряжение питанияs or grounds.

4. Неисправностьy двигатель lubrication system.

Context: The двигатель control unit (ECU) generated a fault associated with the oil temperature/pressure датчик. The датчик senses both temperature and pressure. This fault concerns the pressure sensing function of the device. This error could result from a сигнал вне диапазона or a plausibility check (давление масла слишком высокий). The plausibility check is only started if there are no датчик power supply ( 5 volts dc) or Analog to Digital Converter (ADC) сигнал errors detected.

Причина: The Oil temp / press датчик сигнал to the ECU вне диапазона of the низкийer threshold limit.

Возможные причины отказа:

1. Неисправностьy Oil temp / press датчик.

2. Неисправностьy electrical wiring, сигнал short to низкий source condition.

3. Неисправностьy ECU, напряжение питанияs or grounds.

4. Неисправностьy двигатель lubrication system.

5. Низкий двигатель oil level.

Context: The Двигатель Control Unit (ECU) generated a fault associated with the Oil temp / press датчик. The Oil temp / press датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the pressure sensing function of the device. This error could result from a сигнал вне диапазона or a plausibility check (давление масла слишком высокий). The plausibility check is only started if there are no датчик power supply ( 5 volts dc) or Analog to Digital Converter (ADC) сигнал errors detected.

Причина: The Oil temp / press датчик сигнал to the ECU is either erratic or intermittent.

Возможные причины отказа:

1. Неисправностьy Oil temp / press датчик.

2. Неисправностьy electrical wiring or intermittent connection between Oil temp / press датчик and ECU.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) generated a fault associated with the Oil temp / press датчик. The Oil temp / press датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the pressure sensing function of the device. This error could result from a сигнал вне диапазона or a plausibility check (давление масла слишком высокий). The plausibility check is only started if there are no датчик power supply ( 5 volts dc) or Analog to Digital Converter (ADC) сигнал errors detected.

Причина: The Oil temp / press датчик сигналs to the ECU are both operating in the extreme upper portion of сигнал range.

Возможные причины отказа:

1. Неисправностьy Oil temp / press датчик.

2. Неисправностьy electrical wiring.

3. Неисправностьy ECU, напряжение питанияs or grounds.

4. Неисправностьy двигатель lubrication system.

5. Низкий двигатель oil level.

Context: The Двигатель Control Unit (ECU) generated a fault associated with the Oil temp / press датчик. The Oil temp / press датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the temperature sensing function of the device. This error could result from a сигнал вне диапазона or a plausibility check against the Coolant temp датчик or CAN message processing. The ECU prohibits any plausibility check if there are any Analog to Digital Converter (ADC) сигнал errors detected on the Oil temp / press or the Coolant temp датчик.

Причина: The Oil temp / press and Coolant temp датчик сигналs to the ECU are вне диапазона with respect to each other.

Возможные причины отказа:

1. Неисправностьy Oil temp / press датчик (inaccurate).

2. Неисправностьy Coolant temp датчик (inaccurate).

3. Неисправностьy electrical wiring, высокий resistance connections.

4. Неисправностьy ECU, напряжение питанияs or grounds.

5. Неисправностьy oil lubrication or coolant system.

Context: The Двигатель Control Unit (ECU) generated a fault associated with the Oil temp / press датчик. The Oil temp / press датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the temperature sensing function of the device. This error could result from a сигнал вне диапазона or a plausibility check against the Coolant temp датчик or CAN message processing. The ECU prohibits any plausibility check if there are any Analog to Digital Converter (ADC) сигнал errors detected on the Oil temp / press or the Coolant temp датчик.

Причина: The Oil temp / press датчик сигнал to the ECU вне диапазона of the upper threshold limit.

Возможные причины отказа:

1. Неисправностьy Oil temp / press датчик.

2. Неисправностьy electrical wiring, сигнал short to высокий source or обрыв цепи condition.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) generated a fault associated with the Oil temp / press датчик. The Oil temp / press датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the temperature sensing function of the device. This error could result from a сигнал вне диапазона or a plausibility check against the Coolant temp датчик or CAN message processing. The ECU prohibits any plausibility check if there are any Analog to Digital Converter (ADC) сигнал errors detected on the Oil temp / press or the Coolant temp датчик.

Причина: The Oil temp / press датчик сигнал to the ECU вне диапазона of the низкийer threshold limit.

Возможные причины отказа:

1. Неисправностьy Oil temp / press датчик.

2. Неисправностьy electrical wiring, сигнал short to низкий source condition.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) generated an error from a fault associated with the Boost Pressure датчик. The Boost Pressure датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the pressure sensing function of the device. This error could result from a сигнал вне диапазона or a сигнал that is either erratic or intermittent. When the ECU determines that the Boost Pressure датчик value is not valid, it will substitute a default value of 270 kPa (39 psi).

Причина: The Boost Pressure датчик сигнал to the ECU вне диапазона of the низкийer threshold limit.

Возможные причины отказа:

1. Неисправностьy датчик.

2. Неисправностьy electrical wiring or connection.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The двигатель control unit (ECU) has determined that an unclassifiable отказ exists in the Cylinder #1 injector circuit. A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of a отказ in the Cylinder #1 injector circuit that is unclassifiable over 8 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан.

2. Неисправностьy electrical wiring (damaged connector or conductor).

3. Неисправностьy ECU, hardware or software.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Context: The Двигатель Control Unit (ECU) generated an error associated with the injector power driver stage. The power stage component of the ECU energizes the injection system transistors and simultaneously observes the current fнизкий (sense resistors) in the высокий-side and низкий-side переключательing branches. If there is a deviation from the expected current fнизкий, the driver circuitry detects the specific error and reports it back to the ECU. The ECU will process the error message so that it records information on performed injections, cylinder bank specific errors and cylinder specific errors. The error message is then compared to applicable error patterns and if there is a match, a fault code is generated. If an error message doesn’t match any pattern, the error is treated as unclassifiable. This monitoring function is performed once per camshaft revolution.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short to высокий source or damaged wiring harness.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Примечание: This diagnostic procedure requires a good quality multi-meter to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms (typical injector соленоид coil resistance is 0.4 – 0.5 Ω) and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Примечание: Make sure that the multi-meter’s test lead resistance is taken into account when resistance measurements are taken. Record the multi-meter’s test lead resistance by touching the leads together on the низкийest Ohms scale and mentally recording the resistance value. Subtract this value from the actual resistance measurement taken.

Context: The двигатель control unit (ECU) has determined that a short circuit exists in the высокий side injector circuit for cylinder 1. A power stage component energizes the unit injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU . This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassified error. Monitoring is performed once per camshaft revolution. This error is the result of a short circuit of the высокий side to the низкий side or ground over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU . Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy cylinder 1 соленоид windings.

2. Неисправностьy electrical wiring, short высокий side to низкий side or ground (damaged wiring harness).

3. Неисправностьy ECU, ECU hardware or software.

Context: The двигатель control unit (ECU) has determined that an unclassifiable отказ exists in the Cylinder #5 injector circuit. A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of a отказ in the Cylinder #5 injector circuit that is unclassifiable over 8 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан.

2. Неисправностьy electrical wiring (damaged connector or conductor).

3. Неисправностьy ECU, hardware or software.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Context: The Двигатель Control Unit (ECU) generated an error associated with the injector power driver stage. The power stage component of the ECU energizes the injection system transistors and simultaneously observes the current fнизкий (sense resistors) in the высокий-side and низкий-side переключательing branches. If there is a deviation from the expected current fнизкий, the driver circuitry detects the specific error and reports it back to the ECU. The ECU will process the error message so that it records information on performed injections, cylinder bank specific errors and cylinder specific errors. The error message is then compared to applicable error patterns and if there is a match, a fault code is generated. If an error message doesn’t match any pattern, the error is treated as unclassifiable. This monitoring function is performed once per camshaft revolution.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short to высокий source or damaged wiring harness.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms (typical injector соленоид coil resistance is 0.4 – 0.5 Ω) and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Примечание: Make sure that the multi-meter’s test lead resistance is taken into account when resistance measurements are taken. Record the multi-meter’s test lead resistance by touching the leads together on the низкийest Ohms scale and mentally recording the resistance value. Subtract this value from the actual resistance measurement taken.

Context: The двигатель control unit (ECU) has determined that a short circuit exists in the высокий side injector circuit for cylinder 5. A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of a short circuit of the высокий side to the низкий side or ground over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short высокий side to низкий side or ground (damaged wiring harness).

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an unclassifiable отказ exists in the Cylinder #3 injector circuit. A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of a отказ in the Cylinder #3 injector circuit that is unclassifiable over 8 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан.

2. Неисправностьy electrical wiring (damaged connector or conductor).

3. Неисправностьy ECU, hardware or software.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Context: The Двигатель Control Unit (ECU) generated an error associated with the injector power driver stage. The power stage component of the ECU energizes the injection system transistors and simultaneously observes the current fнизкий (sense resistors) in the высокий-side and низкий-side переключательing branches. If there is a deviation from the expected current fнизкий, the driver circuitry detects the specific error and reports it back to the ECU. The ECU will process the error message so that it records information on performed injections, cylinder bank specific errors and cylinder specific errors. The error message is then compared to applicable error patterns and if there is a match, a fault code is generated. If an error message doesn’t match any pattern, the error is treated as unclassifiable. This monitoring function is performed once per camshaft revolution.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short to высокий source or damaged wiring harness.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms (typical injector соленоид coil resistance is 0.4 – 0.5 Ω) and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Примечание: Make sure that the multi-meter’s test lead resistance is taken into account when resistance measurements are taken. Record the multi-meter’s test lead resistance by touching the leads together on the низкийest Ohms scale and mentally recording the resistance value. Subtract this value from the actual resistance measurement taken.

Context: The двигатель control unit (ECU) has determined that a short circuit exists in the высокий side injector circuit for cylinder 3. A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message does not match any pattern the defect is treated as an unclassified error. Monitoring is performed once per camshaft revolution. This error is the result of a short circuit of the высокий side to the низкий side or ground over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present) and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short высокий side to низкий side or ground (damaged wiring harness).

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an unclassifiable отказ exists in the Cylinder #6 injector circuit. A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of a отказ in the Cylinder #6 injector circuit that is unclassifiable over 8 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан.

2. Неисправностьy electrical wiring (damaged connector or conductor).

3. Неисправностьy ECU, hardware or software.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Context: The Двигатель Control Unit (ECU) generated an error associated with the injector power driver stage. The power stage component of the ECU energizes the injection system transistors and simultaneously observes the current fнизкий (sense resistors) in the высокий-side and низкий-side переключательing branches. If there is a deviation from the expected current fнизкий, the driver circuitry detects the specific error and reports it back to the ECU. The ECU will process the error message so that it records information on performed injections, cylinder bank specific errors and cylinder specific errors. The error message is then compared to applicable error patterns and if there is a match, a fault code is generated. If an error message doesn’t match any pattern, the error is treated as unclassifiable. This monitoring function is performed once per camshaft revolution.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short to высокий source or damaged wiring harness.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms (typical injector соленоид coil resistance is 0.4 – 0.5 Ω) and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Примечание: Make sure that the multi-meter’s test lead resistance is taken into account when resistance measurements are taken. Record the multi-meter’s test lead resistance by touching the leads together on the низкийest Ohms scale and mentally recording the resistance value. Subtract this value from the actual resistance measurement taken.

Context: The двигатель control unit (ECU) has determined that a short circuit exists in the высокий side injector circuit for cylinder 6. A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of a short circuit of the высокий side to the низкий side or ground over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short высокий side to низкий side or ground (damaged wiring harness).

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an unclassifiable отказ exists in the Cylinder #2 injector circuit. A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of a отказ in the Cylinder #2 injector circuit that is unclassifiable over 8 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан.

2. Неисправностьy electrical wiring (damaged connector or conductor).

3. Неисправностьy ECU, hardware or software.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Context: The Двигатель Control Unit (ECU) generated an error associated with the injector power driver stage. The power stage component of the ECU energizes the injection system transistors and simultaneously observes the current fнизкий (sense resistors) in the высокий-side and низкий-side переключательing branches. If there is a deviation from the expected current fнизкий, the driver circuitry detects the specific error and reports it back to the ECU. The ECU will process the error message so that it records information on performed injections, cylinder bank specific errors and cylinder specific errors. The error message is then compared to applicable error patterns and if there is a match, a fault code is generated. If an error message doesn’t match any pattern, the error is treated as unclassified. This monitoring function is performed once per camshaft revolution.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short to высокий source or damaged wiring harness.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms (typical injector соленоид coil resistance is 0.4 – 0.5 Ω) and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Примечание: Make sure that the multi-meter’s test lead resistance is taken into account when resistance measurements are taken. Record the multi-meter’s test lead resistance by touching the leads together on the низкийest Ohms scale and mentally recording the resistance value. Subtract this value from the actual resistance measurement taken.

Context: The двигатель control unit (ECU) has determined that a short circuit exists in the высокий side injector circuit for cylinder 2. A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message does not match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of a short circuit of the высокий side to the низкий side or ground over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present) and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short высокий side to низкий side or ground (damaged wiring harness).

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an unclassifiable отказ exists in the Cylinder #4 injector circuit. A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of a отказ in the Cylinder #4 injector circuit that is unclassifiable over 8 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан.

2. Неисправностьy electrical wiring (damaged connector or conductor).

3. Неисправностьy ECU, hardware or software

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Context: The Двигатель Control Unit (ECU) generated an error associated with the injector power driver stage. The power stage component of the ECU energizes the injection system transistors and simultaneously observes the current fнизкий (sense resistors) in the высокий-side and низкий-side переключательing branches. If there is a deviation from the expected current fнизкий, the driver circuitry detects the specific error and reports it back to the ECU. The ECU will process the error message so that it records information on performed injections, cylinder bank specific errors and cylinder specific errors. The error message is then compared to applicable error patterns and if there is a match, a fault code is generated. If an error message doesn’t match any pattern, the error is treated as unclassifiable. This monitoring function is performed once per camshaft revolution.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short to высокий source or damaged wiring harness.

3. Неисправностьy ECU, напряжение питанияs or grounds.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to be able to take accurate resistance measurements. The meter should be able to measure to a resolution of 0.1 ohms. Some of the measurements required to be taken, could be as низкий as 0.4 ohms (typical injector соленоид coil resistance is 0.4 – 0.5 Ω) and any inaccuracies in the DMM could cause a technician to take the wrong diagnostic path.

Примечание: Make sure that the multi-meter’s test lead resistance is taken into account when resistance measurements are taken. Record the multi-meter’s test lead resistance by touching the leads together on the низкийest Ohms scale and mentally recording the resistance value. Subtract this value from the actual resistance measurement taken.

Context: The двигатель control unit (ECU) has determined that a short circuit exists in the высокий side injector circuit for cylinder 4. A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message does not match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of a short circuit of the высокий side to the низкий side or ground over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present) and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short высокий side to низкий side or ground (damaged wiring harness).

3. Неисправностьy ECU, hardware or software.

Context: The Двигатель Control Unit (ECU) has reported an error with the monitoring of the Increment speed (Crankshaft speed) датчик. If the двигатель has a defective Crankshaft speed датчик it can run off the Segment speed (Camshaft speed) датчик. This is referred to as BACKUP mode. Diagnostics of the SIG отказ is only active if voltage is present at terminal 15 (Ignition ON) and no errors are active for the датчик напряжение питания. .

Причина: The ECU has determined that there is нет сигнала from the Crankshaft speed датчик. The двигатель is now operating in BACKUP mode.

Возможные причины отказа:

1. Неисправностьy Crankshaft speed датчик.

2. Неисправностьy electrical wiring and/or connections.

3. Неисправностьy ECU, or ECU напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) has reported an error with the monitoring of the Crankshaft speed датчик. If the двигатель has a defective Crankshaft speed датчик it can run off the Camshaft speed датчик. This is referred to as BACKUP mode. Diagnostics of the FMI=3 отказs is only active if terminal 40 is on (KEY ON) and no errors are reported in the датчик напряжение питания. For the FMI=4 отказs, additional conditions for active diagnostics are included, such as the двигатель must be in startup mode and the двигатель speed must be above 450 RPM.

Причина: The ECU has determined that there are errors in the сигнал from the Crankshaft speed датчик.

Возможные причины отказа:

1. Неисправностьy Crankshaft speed датчик.

2. Неисправностьy electrical wiring and/or connections.

3. Неисправностьy ECU, напряжение питанияs or ground paths.

Context: The Двигатель Control Unit (ECU) has reported an error with the monitoring of the Segment speed датчик (Camshaft speed датчик). If the двигатель has a defective Camshaft speed датчик it can run off the Increment speed датчик (Crankshaft speed датчик). Diagnostics is active if voltage is present at terminal 15 (Ignition On),, the current двигатель speed is above 50 RPM, no error in the Crankshaft speed датчик is present and the датчик напряжение питания ( 5 volts DC) is not defective.

Причина: The ECU has determined that there is нет сигнала from the Camshaft speed датчик.

Возможные причины отказа:

1. Неисправностьy Camshaft speed датчик.

2. Camshaft speed датчик is not mechanically installed correctly.

3. Неисправностьy electrical wiring and/or connections.

4. Неисправностьy ECU, or ECU напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) has reported an error with the monitoring of the Segment speed датчик (Camshaft speed датчик). If the двигатель has a defective Camshaft speed датчик it can run off the Increment speed датчик (Crankshaft speed датчик). Diagnostics is active if voltage is present at terminal 40 (Ignition On), the current двигатель speed is above 50 RPM, no error in the Crankshaft speed датчик is present and the датчик напряжение питания ( 5 volts DC) is not defective.

Причина: The ECU has determined that there is a plausibility error between the phasing of the Crankshaft speed датчик and the Camshaft speed датчик сигналs. The сигнал from the Camshaft speed датчик is either intermittent or does not exist.

Возможные причины отказа:

1. Неисправностьy Camshaft speed датчик.

2. Camshaft speed датчик is not mechanically installed correctly.

3. Неисправностьy electrical wiring and/or connections.

4. Неисправностьy ECU or ECU напряжение питанияs or ground.

Context: The Двигатель Control Unit (ECU) has reported an error with the phase relationship between the Increment speed датчик (Crankshaft speed датчик) and the Segment speed датчик (Camshaft speed датчик). The двигатель will alternatively use a redundant angular system which is based on the Crankshaft speed датчик. Diagnostics is active under these conditions: 1) terminal 40 (Key On) is active, 2) current двигатель speed is above 50 RPM, 3) no error is reported for the Crankshaft speed датчик and 4) датчик напряжение питания ( 5 volts DC) is not defective .

Причина: The ECU has determined that there is a phase relationship error between the Crankshaft speed датчик and the Camshaft speed датчик.

Возможные причины отказа:

1. Неисправностьy Camshaft speed датчик or Crankshaft speed датчик.

2. Camshaft speed датчик or Crankshaft speed датчик are not mechanically installed correctly.

3. Неисправностьy electrical wiring and/or connections.

4. Неисправностьy ECU, or ECU напряжение питанияs or ground.

Context: The Двигатель Control Unit (ECU) has reported an error with the monitoring of the Increment speed датчик (Crankshaft speed датчик). In the case of a defective Crankshaft speed, датчик the двигатель can also be run alone with the Segment speed датчик (Camshaft speed датчик) in a BACKUP mode. This operation, however, imposes a lot of restrictions on the system since the precise position of the crankshaft can only be roughly estimated by the camshaft information. In case the двигатель enters this BACKUP operation due to a crankshaft датчик error the fault path at hand is set.

Причина: The ECU has determined that there are errors in the сигнал from the Crankshaft speed датчик and is currently operating in BACKUP mode. The двигатель is operating with input from only the Camshaft speed датчик.

Возможные причины отказа:

1. Неисправностьy Crankshaft speed датчик.

2. Неисправностьy electrical wiring and/or connections.

3. Неисправностьy ECU, or ECU напряжение питанияs or grounds.

Context: The двигатель control unit (ECU) has sensed that the Давление топлива датчик сигнал is слишком низкий. The test frequency of the датчик is every 10 ms and if the сигнал is beнизкий 0.25 V for over 200 ms, the error is set. Once set the ECU will, instead of using the peak rail pressure value of the last 10 ms and the current rail pressure, output a substitute value from a curve (MAP) in the ECU depending on двигатель speed and injection quantity.

Причина: The Rail Pressure датчик сигнал is слишком низкий.

Возможные причины отказа:

1. Неисправностьy Rail Pressure датчик.

2. Неисправностьy circuit wiring, shorted to низкий source.

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that the Pressure Relief Клапан (PRV) is open. Normally the давление топлива in the rail is regulated by the metering unit of the высокий pressure pump. However, if this component is неисправностьing the rail pressure can rise to critical levels. For this reason the common rail has a Pressure Relief Клапан (PRV) which is a mechanical safety клапан (no electrical connectors) that opens at a certain pressure level. An opening of the PRV is detected by evaluating the gradient of the rail pressure (calculated by the ECU). If the PRV does not open on its own after exceeding the pressure threshold it can also be forced open by a so-called ‘kickoff’ or pressure shock when the metering клапан of the высокий pressure fuel pump is set to maximum possible quantity. Once the PRV has been opened it will remain open as long as the двигатель is running. A defective common rail pressure датчик, as judged by the ECU, which evokes a kickoff (pressure shock) or a defect in an injection relevant component (small leak) can cause this error to occur. This fault will only be cleared after an ECU reset.

Возможные причины отказа:

1. Неисправностьy Rail Pressure датчик, сигнал not plausible.

2. Неисправностьy common rail fuel system, small leak.

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that the Pressure Relief Клапан (PRV) is open. Normally the давление топлива in the rail is regulated by the metering unit of the высокий pressure pump. However, if this component is неисправностьing the rail pressure can rise to critical levels. For this reason the common rail has a Pressure Relief Клапан (PRV) which is a mechanical safety клапан (no electrical connectors) that opens at a certain pressure level. An opening of the PRV is detected by evaluating the gradient of the rail pressure (calculated by the ECU). If the PRV does not open on its own after exceeding the pressure threshold it can also be forced open by a so-called ‘kickoff’ or pressure shock when themetering клапан of the высокий pressure fuel pump is set to maximum possible quantity. Once the PRV has been opened it will remain open as long as the двигатель is running. A defective common rail pressure датчик, as judged by the ECU, which evokes a kickoff (pressure shock) or a defect in an injection relevant component (small leak) can cause this error to occur. This fault will only be cleared after an ECU reset.

Возможные причины отказа:

1. Неисправностьy Rail Pressure датчик, сигнал not plausible.

2. Неисправностьy common rail fuel system, small leak.

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that the Pressure Relief Клапан (PRV) did not open after a pressure shock (kickoff). Normally the давление топлива in the rail is regulated by the metering unit of the высокий pressure pump. However, if this component is неисправностьing the rail pressure can rise to critical levels. For this reason the common rail has a Pressure Relief Клапан (PRV) which is a mechanical safety клапан (no electrical connectors) that opens at a certain pressure level. An opening of the PRV is detected by evaluating the gradient of the rail pressure (calculated by the ECU). If the PRV does not open on its own after exceeding the pressure threshold it can also be forced open by a so-called ‘kickoff’ or pressure shock when the metering клапан of the высокий pressure fuel pump is set to maximum possible quantity. Rail pressure in excess of 148500 kPa (21538.1 psi) for 1 s evokes a kickoff (pressure shock) request by the ECU. If the pressure shock (kickoff) request is present longer than 2 s and did not immediately open the PRV, this error will occur. This fault will only be cleared after an ECU reset.

Возможные причины отказа:

1. Неисправностьy ECU, improper data set.

2. Неисправностьy PRV, mechanical клапан does not function.

Решение:

1. Use the EST to flash the ECU with the appropriate data set.

A. If the error reoccurs, replace the PRV.

B. If the error does not reoccur, return the combine to service.

Context: The двигатель control unit (ECU) has determined that a short to высокий source circuit condition exists in the fuel высокий pressure pump низкий side circuit. The metering unit of the fuel высокий pressure pump regulates the pressure in the common rail. The metering unit is closed-loop controlled by both main relay 1 (высокий side) and a низкий side power stage (Main Relay 1 is an electronic control circuit within the ECU, providing source voltage to devices external to the ECU. The низкий side power stage works in conjunction with the Main Relay 1 source, providing sensing and current limiting for the circuit). The monitoring at низкий side is stopped if a short circuit to ground at the высокий side (main relay 1) is detected or it is переключательed off for some reason. Failure detection of is only possible if the низкий side power stage is переключательed on. With the current settings, the monitoring is shut off during after-run. This error is the result of the power stage hardware report of ‘short circuit to battery’ (on the низкий side of the metering unit) longer than 0.0 (zero) milliseconds and once the permanent error is detected the power stage is переключательed off.

Причина: Fuel высокий pressure pump circuit is shorted to a высокий source.

Возможные причины отказа:

1. Неисправностьy fuel высокий pressure pump control circuit, shorted to a высокий source.

2. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that a short to низкий source circuit condition exists in the fuel высокий pressure pump низкий side circuit. The metering unit of the fuel высокий pressure pump regulates the pressure in the common rail. The metering unit is closed-loop controlled by both main relay 1 (высокий side) and a низкий side power stage (Main Relay 1 is an electronic control circuit within the ECU, providing source voltage to devices external to the ECU. The низкий side power stage works in conjunction with the Main Relay 1 source, providing sensing and current limiting for the circuit). The monitoring at низкий side is stopped if a short circuit to ground at the высокий side (main relay 1) is detected or it is переключательed off for some reason. Failure detection of is only possible if the низкий side power stage is переключательed off. With the current settings, the monitoring is shut off during after-run. This error is the result of the power stage hardware report of ‘short circuit to ground’ (on the низкий side of the metering unit) longer than 0.28 seconds and the power stage has most likely переключательed off.

Причина: Fuel высокий pressure pump circuit is shorted to a низкий source.

Возможные причины отказа:

1. Неисправностьy fuel высокий pressure pump control circuit, shorted to a низкий source.

2. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has sensed that the Rail Pressure датчик offset сигнал is слишком высокий. This test is performed during after-run and is aborted if the Key переключатель is переключательed “On” during after-run. During after-run the measured raw value of the Rail Pressure датчик is compared to the atmospheric pressure датчик within the ECU. To ensure that the rail pressure has depressurized sufficiently to atmospheric levels after двигатель shutoff, the monitoring is released only if the delay time determined by the rail pressure dependent curve (ECU pre-запрограммирован data) has elapsed and the fuel temperature is above -0.04 °C (31.93 °F). If the raw value of the rail pressure датчик exceeds 0.65 V over 100 milliseconds during after-run, this error is set and will reset if the value goes beнизкий the limit for over 100 milliseconds.

Причина: The Rail Pressure датчик after-run сигнал is слишком высокий.

Возможные причины отказа:

1. Неисправностьy circuit wiring or electrical connection.

2. Неисправностьy датчик.

Context: The двигатель control unit (ECU) has sensed that the Rail Pressure датчик offset сигнал is слишком низкий. This test is performed during after-run and is aborted if the Key переключатель is переключательed “On” during after-run. During after-run the measured raw value of the Rail Pressure датчик is compared to the atmospheric pressure датчик within the ECU. To ensure that the rail pressure has depressurized sufficiently to atmospheric levels after двигатель shutoff, the monitoring is released only if the delay time determined by the rail pressure dependent curve (ECU pre-запрограммирован data) has elapsed and the fuel temperature is above -0.04 °C (31.93 °F). If the raw value of the rail pressure датчик is beнизкий 0.35 V over 100 milliseconds during after-run, this error is set and will reset if the value goes above the limit for over 100 milliseconds.

Причина: The Rail Pressure датчик after-run сигнал is слишком низкий.

Возможные причины отказа:

1. Неисправностьy circuit wiring or electrical connection.

2. Неисправностьy датчик.

Context: The двигатель control unit (ECU) has sensed that the Давление топлива датчик сигнал is слишком высокий. The test frequency of the датчик is every 10 ms and if the сигнал is in excess of 4.86 V for over 200 ms, the error is set. Once set the ECU will, instead of using the peak rail pressure value of the last 10 ms and the current rail pressure, output a substitute value from a curve (MAP) in the ECU depending on двигатель speed and injection quantity.

Причина: The Давление топлива датчик сигнал is слишком высокий.

Возможные причины отказа:

1. Неисправностьy Давление топлива датчик.

2. Неисправностьy circuit wiring, shorted to высокий source.

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an обрыв цепи condition exists in the Pump control клапан (Metering Unit – Высокий Pressure Pump Regulator соленоид/клапан) circuit. The metering unit of the fuel высокий pressure pump regulates the pressure in the common rail. The metering unit is controlled by both main relay 1 высокий side and a низкий side power stages (Main Relay 1 is an electronic control circuit within the ECU used to provide fixed and variable control сигналs to devices external to the ECU). The monitoring at низкий side is stopped if a short circuit to ground at the высокий side (main relay 1) is detected or it is переключательed off for some reason. Failure detection of an over current condition is only possible if the низкий side power stage is переключательed on and the обрыв цепи condition only if it is переключательed off. With the current settings, the monitoring is shut off during after-run. This error is the result of the power stage hardware report of an ‘open load’ in the metering unit longer than 200 milliseconds.

Причина: Pump control клапан circuit is open.

Возможные причины отказа:

1. Неисправностьy Pump control клапан, open соленоид coil.

2. Неисправностьy circuit, open conductor.

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit has determined that a short circuit condition exists in the fuel высокий pressure pump circuit. The metering unit of the fuel высокий pressure pump regulates the pressure in the common rail. The metering unit is controlled by both main relay 1 высокий side and a низкий side power stages (Main Relay 1 is an electronic control circuit within the ECU used to provide fixed and variable control сигналs to devices external to the ECU. The monitoring at низкий side is stopped if a short circuit to ground at the высокий side (main relay 1) is detected or it is переключательed off for some reason. Failure detection of an over current condition is only possible if the низкий side power stage is переключательed on and the обрыв цепи condition only if it is переключательed off. With the current settings, the monitoring is shut off during after-run. This error is the result of the power stage hardware report of ‘excess temperature’ (высокий current) in the metering unit circuit longer than 200 milliseconds.

Причина: Fuel высокий pressure pump circuit is shorted.

Возможные причины отказа:

1. Неисправностьy fuel высокий pressure pump, shorted соленоид coil.

2. Неисправностьy control circuit, short circuit.

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that there is either Fuel System Leakage or the Metering Unit (Высокий Pressure Pump Regulator соленоид/клапан) is jammed in closed position. The rail pressure is monitored by various fault paths during active pressure control by the metering unit. The fault path at hand detects a leakage of fuel by monitoring the set-point current used to control the metering unit. The monitoring is only active if the высокий pressure governor (Высокий Pressure Pump Regulator соленоид/клапан) is operating in closed loop control, the rail pressure governor deviation is within the range +/- 5000 kPa (725.2 psi) and the monitoring has not been inhibited by other faults. If the metering unit current control set-point current is beнизкий a calculated minimum limit over 2.5 seconds this error will occur. [This limit is calculated from various curves, maps and correction factors established by the ECU]. This error is the result of an inaccurate Rail pressure датчик or defective высокий pressure pump in the высокий pressure system or Metering unit reflux слишком низкий, fuel system leakage, or metering unit jammed in the closed position in the низкий pressure system.

Context: The двигатель control unit (ECU) has acknowledged that the ‘Высокий Pressure Test’ is running. The ‘Высокий Pressure Test’ is a test procedure used to evaluate the performance of the fuel высокий pressure unit (pump, rail pressure control клапан, etc.) and is executed via a diagnostic tester request. If this test is running the rail pressure monitoring has to be deactivated, which is done by setting this fault path. Therefore, this отказ path is used more for information purposes and inhibit handling than as an actual error status.

Context: The Двигатель Control Unit (ECU) generated a fault associated with the Oil temp / press датчик. The Oil temp / press датчик is an integrated sensing device used to sense both temperature and pressure. This fault is related to the temperature sensing function of the device. This error resulted from a plausibility check against the oil temperature being слишком высокий. The ECU will prohibit the any plausibility check when there are Analog to Digital Converter (ADC) сигнал errors detected on the Oil temp / press датчик.

Причина: The Oil temp / press датчик is reporting an abnormally высокий oil temperature to the ECU.

Возможные причины отказа:

1. Неисправностьy Oil temp / press датчик.

2. Неисправностьy electrical wiring and / or connections.

3. Неисправностьy ECU, напряжение питанияs or grounds.

4. Неисправностьy oil lubrication or coolant system.

Context: The Двигатель Control Unit (ECU) generated a fault when monitoring the temperature rise of the двигатель температура охлаждающей жидкости during a warm-up cycle. During the monitoring process, the start temp and the current coolant temp are compared against a warm-up cycle curve in the ECU. The fault is generated after a timer expires and the температура охлаждающей жидкости does not match the warm-up cycle curve. This test is carried out once per driving cycle and is stopped when the двигатель is in after-run mode.

Причина: The ECU has determined that the rise in температура охлаждающей жидкости is низкийer than expected during the двигатель warm-up cycle.

Возможные причины отказа:

1. Неисправностьy or inaccurate coolant temp датчик.

2. Неисправностьy wiring, высокий resistance.

3. Very низкий ambient temperature.

4. Неисправностьy ECU, напряжение питанияs or grounds.

Причина: Двигатель контроллер configuration took longer than 4 minutes

Возможные причины отказа:

1. Двигатель контроллер configuration timed out

Решение: 1. The configuration process was not started within the 4 minute time out period. Erase fault and proceed with configuration.

Причина: Двигатель configuration does not match the TCU двигатель configuration stored.

Возможные причины отказа:

1. Configuration error

Решение: 1. Двигатель configuration does not match the tractor control unit (TCU) двигатель configuration stored. Correct configuration error.

Причина: Loss of all CAN communication from the governor for 2.5 seconds

Возможные причины отказа:

1. Неисправностьy connector

2. Неисправностьy harness

3. CAN BUS interference

4. Неисправностьy двигатель контроллер

Context: The двигатель control unit (ECU) has determined that the Metering Unit (Высокий Pressure Pump Regulator соленоид/клапан) has excessively opened to reach the desired Rail pressure. The rail pressure is monitored by various fault paths during active pressure control by the metering unit. The fault path at hand detects an excessive leakage of fuel by monitoring the set-point value of the fuel volume fнизкий through the metering unit during overrun. The monitoring is only active if the высокий pressure governor (Высокий Pressure Pump Regulator соленоид/клапан) is operating in closed loop control, the двигатель is in overrun condition, the fuel injection quantity is zero and the monitoring has not been inhibited by other faults. If the set-point value of the rail pressure governor for the fuel volume fнизкий through the metering unit exceeds an upper limit over 2.5 seconds this error will occur. [This limit is interpolated from the rail pressure dependent curve, established by the ECU]. This error is the result of leakage in the высокий pressure section; injection nozzle stuck in open position, worn or defective высокий pressure pump, worn injector, leaking pressure relief клапан. or leakage in the низкий pressure system; ‘Zero delivery’ is not active in metering unit (excessive leakage in metering unit).

Context: The Двигатель Control Unit (ECU) has detected an двигатель over-speed condition. An двигатель over-speed can occur both during certain двигатель operating conditions without any defect in a component, for example downhill driving, or as a result of, for example another ECU error. This error is for information purposes and is initiated by двигатель speed in excess of 2800 RPM for over 5 seconds and is reset once the двигатель speed is beнизкий the threshold for over 2 seconds. Though this error by itself does not require any action, the over-speed state can cause an injection shutoff request within the ECU. If this error reoccurs frequently, check driving conditions of the vehicle, двигатель speed acquisition and injection system for quantity set-point and actual value during fault recognition, check also for other ECU errors.

Context: The Двигатель control unit (ECU) has determined that an обрыв цепи condition exists in the Cylinder 1 injector circuit. A power stage component energizes the unit injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of an обрыв цепи отказ being present for over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present) and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель control unit (ECU) has determined that there is a fault associated with the current monitoring of the Cylinder 1 injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy Cylinder 1 injector соленоид windings.

2. Неисправностьy electrical wiring, обрыв цепи (damaged wiring).

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an обрыв цепи condition exists in the Cylinder 2 injector circuit. A power stage component energizes the unit injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of an обрыв цепи отказ being present for over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the Cylinder 2 injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or open соленоид windings.

2. Неисправностьy electrical wiring, обрыв цепи (damaged wiring).

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an обрыв цепи condition exists in the Cylinder 3 injector circuit. A power stage component energizes the unit injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of an обрыв цепи отказ being present for over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the Cylinder 3 injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or open соленоид windings.

2. Неисправностьy electrical wiring, обрыв цепи (damaged wiring).

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an обрыв цепи condition exists in the Cylinder 4 injector circuit. A power stage component energizes the unit injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of an обрыв цепи отказ being present for over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the Cylinder 4 injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or open соленоид windings.

2. Неисправностьy electrical wiring, обрыв цепи (damaged wiring).

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an обрыв цепи condition exists in the Cylinder 5 injector circuit. A power stage component energizes the unit injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of an обрыв цепи отказ being present for over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the Cylinder 5 injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or open соленоид windings.

2. Неисправностьy electrical wiring, обрыв цепи (damaged wiring).

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an обрыв цепи condition exists in the Cylinder 6 injector circuit. A power stage component energizes the unit injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of an обрыв цепи отказ being present for over 3 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the Cylinder 6 injector output power driver stage.

Возможные причины отказа:

1. Неисправностьy injection клапан or open соленоид windings.

2. Неисправностьy electrical wiring, обрыв цепи (damaged wiring).

3. Неисправностьy ECU, hardware or software.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to accurately measure resistance . The DMM must measure to a resolution of 0.1 ohms. The required measurements are as низкий as 0.4 ohms (typical injector соленоид coil resistance is 0.4 – 0.5 Ω) and any DMM inaccuracies will cause the technician to inaccurately troubleshoot.

Примечание: Ensure the DMM’s test lead resistance is considered when measuring resistance. Touch the leads together on the низкийest Ohms scale and record the resistance measurement. Subtract this value from all future resistance measurements.

Context: The Двигатель Control Unit (ECU) has determined a short circuit exists in an injector cable in Bank 1 (Group A, Cylinders 1, 2, & 3). A power stage component energizes the injection system transistors while observing the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. Deviations from the expected current fнизкий are detected as specific errors by the component and reported to the ECU. Ошибка messages are configured to contain information on performed injections, same bank cylinder errors, bank specific errors and cylinder specific errors. The configured error message is compared to applicable error patterns, and the отказ matching the pattern is output. If an error message doesn’t match a pattern the defect becomes an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is a result of a general short circuit of the высокий side to battery or ground over 4 camshaft revolutions. This error shuts off an individual cylinder or bank, based on ECU parameters. Certain parameters, as currently applied, are permanent; there is no healing possibility after testing: переключательing on the component to ascertain the defect’s presence. Others evoke an irreversible or reversible двигатель shut off.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of an injector output power driver stage in Bank 1.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short высокий side to высокий source, низкий side or ground (damaged wiring harness).

3. Неисправностьy ECU, hardware or software.

Context: The Двигатель Control Unit (ECU) has determined a short circuit exists in an injector cable in Bank 1 (Group A, Cylinders 1, 2, & 3). A power stage component energizes the injection system transistors while observing the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. Deviations from the expected current fнизкий are detected as specific errors by the component and reported to the ECU. Ошибка messages are configured to contain information on performed injections, same bank cylinder errors, bank specific errors and cylinder specific errors. The configured error message is compared to applicable error patterns, and the отказ matching the pattern is output. If an error message doesn’t match a pattern the defect becomes an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is a result of a general short circuit of the высокий side to battery or ground over 4 camshaft revolutions. This error shuts off an individual cylinder or bank, based on ECU parameters. Certain parameters, as currently applied, are permanent; there is no healing possibility after testing: переключательing on the component to ascertain the defect’s presence. Others evoke an irreversible or reversible двигатель shut off.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage in Bank 1.

Возможные причины отказа:

1. Неисправностьy injection клапан (соленоид coil замкнуто на массу).

2. Неисправностьy electrical wiring, short низкий side to ground (damaged wiring).

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an unclassified error exists in an injector cable in Bank 1 (Group A, Cylinders 1, 2, & 3). A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of an unclassified error being present over 9 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present), and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the injector output power driver stage in Bank 1.

Возможные причины отказа:

1. Неисправностьy electrical wiring (damaged connector or conductor).

2. Неисправностьy ECU, hardware or software.

Примечание: This diagnostic procedure requires a good quality Digital Multi-meter (DMM) to accurately measure resistance . The DMM must measure to a resolution of 0.1 ohms. The required measurements are as низкий as 0.4 ohms (typical injector соленоид coil resistance is 0.4 – 0.5 Ω) and any DMM inaccuracies will cause the technician to inaccurately troubleshoot.

Примечание: Ensure the DMM’s test lead resistance is considered when measuring resistance. Touch the leads together on the низкийest Ohms scale and record the resistance measurement. Subtract this value from all future resistance measurements.

Context: The Двигатель Control Unit (ECU) has determined a short circuit exists in an injector cable in Bank 2 (Group B, Cylinders 4, 5, & 6). A power stage component energizes the injection system transistors while observing the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. Deviations from the expected current fнизкий are detected as specific errors by the component and reported to the ECU. Ошибка messages are configured to contain information on performed injections, same bank cylinder errors, bank specific errors and cylinder specific errors. The configured error message is compared to applicable error patterns, and the отказ matching the pattern is output. If an error message doesn’t match a pattern the defect becomes an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is a result of a general short circuit of the высокий side to battery or ground over 4 camshaft revolutions. This error shuts off an individual cylinder or bank, based on ECU parameters. Certain parameters, as currently applied, are permanent; there is no healing possibility after testing: переключательing on the component to ascertain the defect’s presence. Others evoke an irreversible or reversible двигатель shut off.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of an injector output power driver stage in Bank 2.

Возможные причины отказа:

1. Неисправностьy injection клапан or shorted соленоид windings.

2. Неисправностьy electrical wiring, short высокий side to высокий source, низкий side or ground (damaged wiring harness).

3. Неисправностьy ECU, hardware or software.

Context: The Двигатель Control Unit (ECU) has determined a short circuit exists in an injector cable in Bank 2 (Group B, Cylinders 4, 5, & 6). A power stage component energizes the injection system transistors while observing the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. Deviations from the expected current fнизкий are detected as specific errors by the component and reported to the ECU. Ошибка messages are configured to contain information on performed injections, same bank cylinder errors, bank specific errors and cylinder specific errors. The configured error message is compared to applicable error patterns, and the отказ matching the pattern is output. If an error message doesn’t match a pattern the defect becomes an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is a result of a general short circuit of the высокий side to battery or ground over 4 camshaft revolutions. This error shuts off an individual cylinder or bank, based on ECU parameters. Certain parameters, as currently applied, are permanent; there is no healing possibility after testing: переключательing on the component to ascertain the defect’s presence. Others evoke an irreversible or reversible двигатель shut off.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the current monitoring of the injector output power driver stage in Bank 2.

Возможные причины отказа:

1. Неисправностьy injection клапан (соленоид coil замкнуто на массу).

2. Неисправностьy electrical wiring, short низкий side to ground (damaged wiring).

3. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has determined that an unclassified error exists in an injector cable in Bank 2 (Group B, Cylinders 4, 5, & 6). A power stage component energizes the injection system transistors and simultaneously observes the current fнизкий in the высокий-side and низкий-side переключательing branch by sensing resistors. If there is a deviation from the expected current fнизкий the component detects specific errors and reports them to the ECU. This error message is then rearranged so it holds information on performed injections, errors of cylinders on the same bank, bank specific errors and cylinder specific errors. The rearranged error message is then compared to applicable error patterns and if there is a match the отказ corresponding to the matched pattern is output. If an error message doesn’t match any pattern the defect is treated as an unclassifiable error. Monitoring is performed once per camshaft revolution. This error is the result of an unclassified error being present over 9 camshaft revolutions. As a result of this error an individual cylinder or bank is shut off, based on parameters established in the ECU. Certain parameters, as currently applied, are permanent (without a healing possibility, once tested by переключательing on the component to see if the defect is still present). and others evoke an irreversible or reversible shut off of the двигатель to be executed.

Причина: The Двигатель Control Unit (ECU) has determined that there is a fault associated with the injector output power driver stage in Bank 2.

Возможные причины отказа:

1. Неисправностьy electrical wiring (damaged connector or conductor).

2. Неисправностьy ECU, hardware or software.

Context: The двигатель control unit (ECU) has sensed a problem with the internal напряжение питания for Fuel Injector Group “A”, the fault path for errors in the power stage component of the unit injection system. The power stage monitors itself and reports detected errors to the ECU. Monitoring is performed once per camshaft revolution. If an internal reset or parity error is present longer than 3 camshaft revolutions , this error will occur. As a result of this error an individual cylinder or bank is shut off. This shut off is currently applied to be permanent without a healing possibility by переключательing on the component to see if the defect is still present. With either an irreversible or reversible shut off of the двигатель being executed. The reason for this отказ is a defective ECU. If the fault doesn’t reset or reoccurs, replace the ECU.

Context: The двигатель control unit (ECU) has sensed a problem with the internal напряжение питания for Fuel Injector Group “A”, the fault path for errors in the power stage component of the unit injection system. The power stage monitors itself and reports detected errors to the ECU. Monitoring is performed once per camshaft revolution. If an internal program fнизкий error exists for longer than 3 camshaft revolutions , this error will occur. As a result of this error an individual cylinder or bank is shut off. This shut off is currently applied to be permanent without a healing possibility by переключательing on the component to see if the defect is still present. With either an irreversible or reversible shut off of the двигатель being executed. The reason for this отказ is a defective ECU. If the fault doesn’t reset or reoccurs, replace the ECU.

Context: The двигатель control unit (ECU) has sensed a problem with the internal напряжение питания for Fuel Injector Group “A”, the fault path for errors in the power stage component of the unit injection system. The power stage monitors itself and reports detected errors to the ECU. Monitoring is performed once per camshaft revolution. If the YSEL сигнал is not inverted as requested during injection for longer than 3 camshaft revolutions , this error will occur. As a result of this error an individual cylinder or bank is shut off. This shut off is currently applied to be permanent without a healing possibility by переключательing on the component to see if the defect is still present. With either an irreversible or reversible shut off of the двигатель being executed. The reason for this отказ is a defective ECU. If the fault doesn’t reset or reoccurs, replace the ECU.

Context: The двигатель control unit (ECU) has sensed a problem with the internal напряжение питания for Fuel Injector Group “A”, the fault path for errors in the power stage component of the unit injection system. The power stage monitors itself and reports detected errors to the ECU. Monitoring is performed once per camshaft revolution. If the power stage component On Time-out is present for at least one cylinder for longer than 3 camshaft revolutions , this error will occur. As a result of this error an individual cylinder or bank is shut off. This shut off is currently applied to be permanent without a healing possibility by переключательing on the component to see if the defect is still present. With either an irreversible or reversible shut off of the двигатель being executed. The reason for this отказ is a defective ECU. If the fault doesn’t reset or reoccurs, replace the ECU.

Context: The двигатель control unit (ECU) has sensed a problem with the internal напряжение питания for Fuel Injector Group “B”, the fault path for errors in the power stage component of the unit injection system. The power stage monitors itself and reports detected errors to the ECU. Monitoring is performed once per camshaft revolution. An internal reset or parity error present longer than 3 camshaft revolutions, will produce this error. As a result of this error an individual cylinder or bank is shut off. This shut off is currently applied to be permanent without a healing possibility by переключательing on the component to see if the defect is still present. With either an irreversible or reversible shut off of the двигатель being executed. The reason for this отказ is a defective ECU. If the fault doesn’t reset or reoccurs, replace the ECU.

Context: The двигатель control unit (ECU) has sensed a problem with the internal напряжение питания for Fuel Injector Group “B”, the fault path for errors in the power stage component of the unit injection system. The power stage monitors itself and reports detected errors to the ECU. Monitoring is performed once per camshaft revolution. If an internal program fнизкий error exists for longer than 3 camshaft revolutions , this error will occur. As a result of this error an individual cylinder or bank is shut off. This shut off is currently applied to be permanent without a healing possibility by переключательing on the component to see if the defect is still present. With either an irreversible or reversible shut off of the двигатель being executed. The reason for this отказ is a defective ECU. If the fault doesn’t reset or reoccurs, replace the ECU.

Context: The двигатель control unit (ECU) has sensed a problem with the internal supply for Fuel Injector Group “B”, the fault path for errors in the power stage component of the unit injection system. The power stage monitors itself and reports detected errors to the ECU. Monitoring is performed once per camshaft revolution. If the power stage component On Time-out is present for at least one cylinder for longer than 3 camshaft revolutions , this error will occur. As a result of this error an individual cylinder or bank is shut off. This shut off is currently applied to be permanent without a healing possibility by переключательing on the component to see if the defect is still present. With either an irreversible or reversible shut off of the двигатель being executed. The reason for this отказ is a defective ECU. If the fault doesn’t reset or reoccurs, replace the ECU.

Context: The двигатель control unit (ECU) has detected that injection time is too long. The sum of all torque-forming energizing times of an individual cylinder exceeds the limit, calculated from the map (depending on the двигатель speed and the time since the overrun monitoring is active) for more than 100 test events (test frequency every 10 ms). When the двигатель is in overrun operation the monitoring becomes active and the current injection energizing time is compared with a maximum permissible time limit. If the limit is exceeded an ECU recovery (reset ) is triggered and if the error reoccurs in the same driving cycle, the torque-determining power stages are irreversibly shut off. The basic idea is that the operator reacts to an unintentional torque increase, caused by a неисправность of the ECU, by releasing the accelerator pedal (reducing двигатель speed) which causes the двигатель to enter the overrun operation mode. Overrun monitoring is only released if various conditions are met, such as no accelerator pedal activation, no activated cruise control, no intervention of the vehicle dynamic control or gearbox control is present, etc. This отказ could be the result of electronic disturbances, a requested torque increase via tester, the wrong application of injection relevant parameters, or a defective ECU. If this отказ persists, the ECU may need to be replaced.

Context: The двигатель control unit (ECU) has detected an internal communications error. Internal communications between the micro-контроллер and each CJ940 module (peripheral integrated circuit) via the SPI bus is monitored cyclically every 20 milliseconds by evaluating the corresponding communication error flag which is provided by the hardware encapsulation. For every test an error counter is increased or decreased in steps of one. If the error counter for defective SPI buss communications reaches or exceeds a value of 5 this error becomes active and will reset once the error counter is equal to or beнизкий the value of 0 (zero). This error is caused by electrical disturbances or an internal defect of the ECU. If отказ remains present, replace the ECU.

Context: The двигатель control unit (ECU) has detected an error during the last EEPROM read operation. The hardware encapsulation of the ECU checks each data block of the EEPROM and sets a status flag depending on if an error is found or not found. These flags are processed every 20 milliseconds by the Diagnostic System Management (DSM) and depending on their value a отказ or no отказ is detected. If a отказ is detected this error sets and should reset immediately if the EEPROM operates correctly. This отказ can be the result of wrong programming / flashing of the ECU or an internal defect. Try to flash the ECU correctly with the proper data set. If the error persists, replace the ECU.

Context: The двигатель control unit (ECU) has detected an error during the last EEPROM write operation. The hardware encapsulation of the ECU checks each data block of the EEPROM and sets a status flag depending on if an error is found or not found. These flags are processed every 20 milliseconds by the Diagnostic System Management (DSM) and depending on their value a отказ or no отказ is detected. If a отказ is detected this error sets and should reset immediately if the EEPROM operates correctly. This отказ can be the result of wrong programming / flashing of the ECU or an internal defect. Try to flash the ECU correctly with the proper data set. If the error persists, replace the ECU.

Context: The двигатель control unit (ECU) has detected that substitute values for the EEPROM values are used. This happens if a checksum error (CRC) is registered during reading. The hardware encapsulation of the ECU checks each data block of the EEPROM and sets a status flag depending on if an error is found or not found. These flags are processed every 20 milliseconds by the Diagnostic System Management (DSM) and depending on their value a отказ or no отказ is detected. If a отказ is detected this error sets and should reset immediately if the EEPROM operates correctly. This отказ can be the result of wrong programming / flashing of the ECU or an internal defect. Try to flash the ECU correctly with the proper data set. If the error persists, replace the ECU.

Context: The двигатель control unit (ECU) has detected, during system start up, a hardware or configuration problem. This triggers an ECU recovery (reset of the CPU – Central Processing Unit) that is stored as protected. During a fresh ECU start up different hardware tests are performed. If the error remains present even after reset, the software remains in the boot-block and the driving software is not processed. If three recoveries are triggered within 4 seconds an irreversible shut off of the system is carried out and the ECU is classified as permanently defective. In this case no error entry is possible. If, however, the error leading to recovery is not detected repeatedly and the system is alнизкийed to start up, one of three recovery errors becomes active depending on the visibility of the recovery. This error can be the result of electronic disturbances, various hardware defects (ECU internal) or configuration problems. If this error occurs repeatedly, reprogram the ECU and if the error remains, replace the ECU.

Context: The двигатель control unit (ECU) has detected, during system start up, a hardware or configuration problem. This triggers an ECU recovery (reset of the CPU – Central Processing Unit) that is not stored. During a fresh ECU start up different hardware tests are performed. If the error remains present even after reset, the software remains in the boot-block and the driving software is not processed. If three recoveries are triggered within 4 seconds an irreversible shut off of the system is carried out and the ECU is classified as permanently defective. In this case no error entry is possible. If, however, the error leading to recovery is not detected repeatedly and the system is alнизкийed to start up, one of three recovery errors becomes active depending on the visibility of the recovery. This error can be the result of electronic disturbances, various hardware defects (ECU internal) or configuration problems. If this error occurs repeatedly, reprogram the ECU and if the error remains, replace the ECU.

Context: The двигатель control unit (ECU) has detected, during system start up, a hardware or configuration problem. This triggers an ECU recovery (reset of the CPU – Central Processing Unit) that is visible in the error memory. During a fresh ECU start up different hardware tests are performed. If the error remains present even after reset, the software remains in the boot-block and the driving software is not processed. If three recoveries are triggered within 4 seconds an irreversible shut off of the system is carried out and the ECU is classified as permanently defective. In this case no error entry is possible. If, however, the error leading to recovery is not detected repeatedly and the system is alнизкийed to start up, one of three recovery errors becomes active depending on the visibility of the recovery. This error can be the result of electronic disturbances, various hardware defects (ECU internal) or configuration problems. If this error occurs repeatedly, reprogram the ECU and if the error remains, replace the ECU.

Context: The двигатель control unit (ECU) has detected a fault in the internal monitoring circuitry. The ECU contains a CPU (central processing unit) and other microprocessor based circuitry one of which serves as a monitoring module (watchdog). These two components communicate via the internal communications network (SPI-Bus). Both devices mutually monitor one another for correct functioning. The watchdog initiates a query / response communication with the CPU, which responds by starting a “command test” (test of the correct functioning of important processor commands) and “program fнизкий control” (monitors the correct execution of code segments of the monitoring). From the results of these two procedures the response to the watchdog is composed. If this response does not correspond to the expected value, an error counter is incremented. The CPU periodically sends некорректный responses (regarding response time and value, respectively) as result of the watchdog query / response. The CPU then monitors if the above mentioned counter is incremented or decremented in accordance with the некорректный or correct response. If the behavior of the counter is implausible, a second counter is incremented. This monitoring process is executed every 80 ms. This error is the result of one of the counters exceeding a count of 5 and will reset if both counters contain a value less than 5. If the error exists only temporarily, it can be ignored and deleted in the fault memory. If the error is permanent, двигатель injection will not be alнизкийed and the ECU must be replaced.

Context: The двигатель control unit (ECU) has detected an internal watchdog error. The ECU comprises redundant shutoff paths (SOP) which deactivate all power stages relevant to injection if certain internal ECU errors are detected. The defects which trigger SOP are the watchdog, over voltage and under voltage errors. In order to test the correct functioning of the SOP procedure, every path is activated during ECU initialization and folнизкийed by activation of the fuel injection power stage. Since the SOP is active, no injection should occur as it is blocked if the SOP procedure functions properly. During a successful redundant SOP test an обрыв цепи (no current fнизкий) should be detected. The SOP test can only be carried out if no errors, such as short circuits of the injection power stage, have been detected previously. This fault is detected if injection occurred although internal SOP of the watchdog was active. If the отказ remains after ECU initialization, replace the ECU.

Context: The двигатель control unit (ECU) has detected that the internal напряжение питания is слишком высокий. The ECU comprises redundant shut-off paths (SOP) which deactivate all power stages relevant to injection if certain internal ECU errors are detected. The defects which trigger SOP are the watchdog, over voltage and under voltage errors. In order to test the correct functioning of the SOP procedure, every path is activated during ECU initialization and folнизкийed by activation of the fuel injection power stage. Since the SOP is active, no injection should occur as it is blocked if the SOP procedure functions properly. During a successful redundant SOP test an обрыв цепи (no current fнизкий) should be detected. The SOP test can only be carried out if no errors, such as short circuits of the injection power stage, have been detected previously. This fault is detected if injection occurred although internal SOP of the over-voltage was active. If the отказ remains after ECU initialization, replace the ECU.

Context: The двигатель control unit (ECU) has detected that the internal напряжение питания is слишком низкий. The ECU comprises redundant shutoff paths (SOP) which deactivate all power stages relevant to injection if certain internal ECU errors are detected. The defects which trigger SOP are the watchdog, over voltage and under voltage errors. In order to test the correct functioning of the SOP procedure, every path is activated during ECU initialization and folнизкийed by activation of the fuel injection power stage. Since the SOP is active, no injection should occur as it is blocked if the SOP procedure functions properly. During a successful redundant SOP test an обрыв цепи (no current fнизкий) should be detected. The SOP test can only be carried out if no errors, such as short circuits of the injection power stage, have been detected previously. This fault is detected if injection occurred although internal SOP of the under-voltage was active. If the отказ remains after ECU initialization, replace the ECU.

Context: The двигатель control unit (ECU) has detected that the TPU (time processing unit) and CPU (central processing unit) have operated outside the established parameters more than 4 times since last ECU recovery (initialization). As the time base of the CPU is checked according to a query / response communication with the monitoring module (watchdog) it should be correct if no error has been detected and therefore can be used to check the time base of the TPU. For this purpose the time basis of the TPU and CPU are compared every 10 ms. After 100 ms the maximum and the minimum value together with the absolute value of the sum of the time differences are evaluated. If the maximum time difference between the TPU and CPU time base exceeds the threshold of 81 ms or the minimum time difference is beнизкий the limit of 81 ms or the absolute value of the sum of the time differences is above 81 msan error counter is incremented. If this counter exceeds the value of 4, this fault is set and initiates an ECU recovery (reset). If this отказ persists, the ECU will need to be replaced.

Context: The двигатель control unit (ECU) has detected an internal (SPI Bus) communication отказ. The central processing unit (CPU) and monitoring module (watchdog) contained with in the ECU, communicate with each other via the SPI bus. Both devices mutually monitor each other for correct functioning. If, however, the SPI communication between them fails this monitoring is impaired and an error counter is incremented. If the error counter exceeds 2 over two 20 ms (two tests) checks, this fault is activated. Communication status is checked autonomously by the SPI driver component every 20 ms and reports a detected error to the ECU. This error initiates ECU recovery (reset). If the ECU functions correctly after recovery, the SPI error is temporary and can be ignored and deleted from fault memory. If the SPI error is permanent and the ECU does not leave boot-block, the ECU needs to be replaced.

Context: The двигатель control unit (ECU) has detected that injection time is too long. The sum of all torque-forming energizing times of an individual cylinder exceeds the limit, calculated from the map (depending on the двигатель speed and the time since the overrun monitoring is active) for more than 100 test events (test frequency every 10 ms). When the двигатель is in overrun operation the monitoring becomes active and the current injection energizing time is compared with a maximum permissible time limit. If the limit is exceeded an ECU recovery (reset ) is triggered and if the error reoccurs in the same driving cycle, the torque-determining power stages are irreversibly shut off. The basic idea is that the operator reacts to an unintentional torque increase, caused by a неисправность of the ECU, by releasing the accelerator pedal (reducing двигатель speed) which causes the двигатель to enter the overrun operation mode. Overrun monitoring is only released if various conditions are met, such as no accelerator pedal activation, no activated cruise control, no intervention of the vehicle dynamic control or gearbox control is present, etc. This отказ could be the result of electronic disturbances, a requested torque increase via tester, the wrong application of injection relevant parameters, or a defective ECU. If this отказ persists, the ECU may need to be replaced.

Context: The двигатель control unit (ECU) has determined that the speed сигнал is not plausible. In order to execute an overrun monitoring, which checks if the injection energizing time is beнизкий a certain limit during overrun, the information of the current двигатель speed is required. As the overrun monitoring is executed in layer 2 of the ECU monitoring concept (i.e. function monitoring) in order to monitor the safety-relevant сигнал paths of the operational layer (layer 1, application software) a redundant двигатель speed is additionally calculated in layer 2, independent of the двигатель speed information of layer 1. If the absolute value of the deviation between двигатель speed (layer 1) and redundant segment speed (layer 2) exceeds 320 RPM over 800 ms (test frequency is every 40 ms), while the redundant segment speed is above 1000 RPM this error is activated, which triggers an ECU recovery (reset). If this отказ persists after ECU re-initialization, replace the ECU.

Context: The rail pressure is monitored by various fault paths during active pressure control by the metering unit. The fault path at hand detects высокий positive rail pressure governor deviations in combination with a высокий set-point value of the fuel volume fнизкий through the metering unit. The monitoring is only active if the высокий pressure governor is operating in closed loop control and the monitoring has not been inhibited by other faults. If the positive rail pressure governor deviation exceeds the двигатель speed dependent limit from a curve established by the ECU and the rail pressure governor set-point value of the fuel volume fнизкий is above the двигатель speed dependent limit from a curve established by the ECU for over 2.5 seconds this error will occur. This error is the result of a leak in the высокий or низкий pressure side of the fuel rail system. On the высокий pressure side check for worn or stuck open injector, worn высокий pressure pump or leaking pressure relief клапан. On the низкий pressure side check for низкий давление топлива before or after the gear pump, clogged fuel filter or leakage.

Context: The двигатель control unit (ECU) has determined that the Fuel Rail/System Pressure is слишком высокий with a closed Metering Unit (Высокий Pressure Pump Regulator – соленоид клапан). The rail pressure is monitored by various fault paths during active pressure control by the metering unit. The fault path at hand detects an excessive negative rail pressure governor deviation (слишком высокий rail pressure) at zero delivery of fuel volume fнизкий through the metering unit. The monitoring is only active if the высокий pressure governor is operating in closed loop control, the двигатель is not in overrun, the fuel system temperature is above 29.96 °C (85.93 °F), the current injection quantity is above 0.0 g (0.00 oz) per cycle and the monitoring has not been inhibited by other faults. If the negative rail pressure governor deviation is beнизкий the двигатель speed dependent limit from a curve established by the ECU and the rail pressure governor set-point value of the fuel volume fнизкий is beнизкий threshold (parameter established by the ECU) over 8 seconds, this error will occur.

Причина:

Возможные причины отказа:

1. Неисправностьy высокий pressure pump regulator соленоид/клапан, stuck open.

2. Pressure слишком высокий, низкий pressure side.

Решение:

1. Проверить for высокий pressure pump regulator (соленоид/клапан) errors.

A. If высокий pressure pump regulator (соленоид/клапан) errors exist, folнизкий troubleshooting procedure for existing высокий pressure pump regulator (соленоид/клапан) error.

B. If no высокий pressure pump regulator (соленоид/клапан) errors exist, locate and repair высокий pressure condition in низкий pressure side of fuel system.

Context: The двигатель control unit (ECU) has determined that the Fuel Rail/System Pressure is слишком низкий. The rail pressure is monitored by various fault paths during active pressure control by the metering unit. The fault path at hand detects if the rail pressure has fallen beнизкий a minimum pressure threshold. The monitoring is only active if the высокий pressure governor is operating in closed loop control and the monitoring has not been inhibited by other faults. If the rail pressure is beнизкий the двигатель speed dependent limit from a curve, established by the ECU, over 2.5 seconds this error will occur. This error is the result of a leak in the высокий or низкий pressure side of the fuel rail system. On the высокий pressure side check for worn or stuck open injector, worn высокий pressure pump or leaking pressure relief клапан. On the низкий pressure side check for низкий давление топлива before or after the gear pump, clogged fuel filter or leakage.

Context: The двигатель control unit (ECU) has determined that the Fuel Rail/System Pressure is слишком высокий. The rail pressure is monitored by various fault paths during active pressure control by the metering unit. The fault path at hand detects if the rail pressure has exceeded a maximum pressure threshold. The monitoring is only active if the высокий pressure governor is operating in closed loop control and the monitoring has not been inhibited by other faults. If the rail pressure exceeds the maximum pressure 150000 kPa (21755.7 psi) over 1 second, this error will occur.

Причина: The Fuel Rail/System Pressure is слишком высокий.

Возможные причины отказа:

1. Неисправностьy высокий pressure pump regulator соленоид/клапан, stuck open.

2. Pressure слишком высокий, низкий pressure side.

Решение:

1. Проверить for высокий pressure pump regulator (соленоид/клапан) errors.

A. If высокий pressure pump regulator (соленоид/клапан) errors exist, folнизкий troubleshooting procedure for existing высокий pressure pump regulator (соленоид/клапан) error.

B. If no высокий pressure pump regulator (соленоид/клапан) errors exist, locate and repair высокий pressure condition in низкий pressure side of fuel system.

Context: The двигатель control unit (ECU) has determined that the Rail Pressure Drop Rate is высокийer than expected. The rail pressure is monitored by various fault paths during active pressure control by the metering unit. The fault path at hand detects if the rail pressure decreases faster during overrun than expected. The monitoring is only active if the высокий pressure governor (Высокий Pressure Regulator Pump соленоид/клапан) is operating in closed loop control, the двигатель is in overrun condition, the fuel injection quantity is zero, the set-point value of the fuel volume fнизкий through the metering клапан is equal or beнизкий the threshold (parameter established by the ECU) and the monitoring has not been inhibited by other faults. If the current rail pressure is beнизкий a certain minimum pressure limit over 2.5 seconds this error will occur. [This pressure limit is calculated from the rail pressure at the last function call (t-20 milliseconds) minus the maximum admissible pressure drop determined from a curve, established by the ECU, multiplied by the function call cycle (20 milliseconds)]. This error is the result of leakage in the высокий pressure section; injection nozzle stuck in open position, worn высокий pressure pump, worn injector, leaking pressure relief клапан, or injector reflux слишком высокий.

Context: The двигатель control unit (ECU) has determined that the minimum number of injections was not reached. The injector shutoff function (within the ECU) can переключатель off a single injector клапан or an entire injection bank if a defect has been detected in a component (monitoring is performed in other fault paths). The shutoff procedure is performed either for an individual cylinder or for an entire bank. However, if too many cylinders are shut down by the shutoff function it is no longer possible to run the двигатель securely and it has to be shut down entirely. In this case the fault path at hand is set. It is possible for the двигатель to continue running on two cylinders. The test frequency is once per injection. If this error occurs, see individual injector and injection-bank errors which have triggered the shutoff or error in the component.

Context: The Двигатель Control Unit (ECU) generated a fault when monitoring the temperature rise of the двигатель температура охлаждающей жидкости during the warm-up cycle. The start температура охлаждающей жидкости is acquired after 60 seconds since двигатель start. After a valid acquisition of the start temperature, a test timer runs as long as the двигатель speed is greater than 1200 RPM and injection quantity is greater than .028 g (0.00099 oz) per stroke. During the monitoring process, the start temp and the current coolant temp are compared against a warm-up cycle curve in the ECU. The fault is generated after the test timer expires and the температура охлаждающей жидкости does not reach the minimum threshold. This test is carried out once per driving cycle and is stopped when the двигатель is in after-run mode.

Причина: The ECU has determined that the rise in температура охлаждающей жидкости is низкийer than expected during the двигатель warm-up cycle.

Возможные причины отказа:

1. Неисправностьy or inaccurate Coolant temp датчик.

2. Неисправностьy wiring (высокий resistance).

3. Very низкий ambient temperature.

4. Неисправностьy ECU, напряжение питанияs or grounds.

Context: The Двигатель Control Unit (ECU) has detected an active power reduction due to the OBD performance limiter. This error is for informational purposes and is initiated by a power reduction due to the OBD performance limiter because of inhibited injection being active causing a torque limitation greater than 25 % of the desired torque for longer than 60 seconds and is reset once the torque limitation due to the OBD performance limiter because of inhibited injection is less than 25 % of the desired torque over 10 seconds. Though no action is necessary due to this error, if the power reduction occurred due to an actual defect, the error triggering the torque limitation should also be in fault memory. Folнизкий the troubleshooting procedure for that error.

Context: The Двигатель Control Unit (ECU) has detected an active power reduction due to smoke limitation. This error is for informational purposes and is initiated by a power reduction due to smoke limitation being active causing a torque limitation greater than 25 % of the desired torque for longer than 60 seconds and is reset once the torque limitation due to smoke limitation is less than 25 % of the desired torque over 10 seconds. Though no action is necessary due to this error, if the power reduction occurred due to an actual defect, the error triggering the torque limitation should also be in fault memory. Folнизкий the troubleshooting procedure for that error.

Context: The Двигатель Control Unit (ECU) has detected an active power reduction due to двигатель mechanics protection. This error is for informational purposes and is initiated by a power reduction due to двигатель mechanics protection being active causing a torque limitation greater than 25 % of the desired torque for longer than 60 seconds and is reset once the torque limitation due to двигатель mechanics protection is less than 25 % of the desired torque over 10 seconds. Though no action is necessary due to this error, if the power reduction occurred due to an actual defect, the error triggering the torque limitation should also be in fault memory. Folнизкий the troubleshooting procedure for that error.

Context: The Двигатель Control Unit (ECU) has detected an active power reduction due to limiting fuel quantity. This error is for informational purposes and is initiated by a power reduction due to limiting fuel quantity being active causing a torque limitation greater than 25 % of the desired torque for longer than 60 seconds and is reset once the torque limitation due to limiting fuel quantity is less than 25 % of the desired torque over 10 seconds. Though no action is necessary due to this error, if the power reduction occurred due to an actual defect, the error triggering the torque limitation should also be in fault memory. Folнизкий the troubleshooting procedure for that error.

Причина: Open or short circuit or short to B+ detected in the viscous fan driver circuit

Возможные причины отказа:

1. Неисправностьy connector or harness damage

2. Неисправностьy viscous fan assembly

Причина: Open or short circuit or short to B+ detected in the viscous fan driver circuit

Возможные причины отказа:

1. Неисправностьy connector or harness damage

2. Неисправностьy viscous fan assembly

Причина: Open or short circuit, or short to B+ detected in the viscous fan driver circuit

Возможные причины отказа:

1. Неисправностьy connector or harness damage

2. Неисправностьy viscous fan assembly

Причина: Open or короткое замыкание на массу detected in the viscous fan driver circuit

Возможные причины отказа:

1. Неисправностьy connector or harness damage

2. Неисправностьy viscous fan assembly

Причина: Short to B+ detected in the viscous fan driver circuit

Возможные причины отказа:

1. Неисправностьy connector or harness damage

2. Неисправностьy viscous fan assembly

Причина: The viscous fan control driver has detected an обрыв цепи or короткое замыкание на массу.

Возможные причины отказа:

1. Неисправностьy connector or harness damage

2. Неисправностьy viscous fan assembly

Причина: Open or короткое замыкание на массу in the viscous fan driver circuit.

Возможные причины отказа:

1. Неисправностьy connector or harness damage

2. Неисправностьy viscous fan assembly

Причина: Open or short circuit, or short to B+ detected in the viscous fan driver circuit

Возможные причины отказа:

1. Неисправностьy connector or harness damage

2. Неисправностьy viscous fan assembly

Причина: Voltage is beнизкий 5.0 V for 400 milleseconds.

Возможные причины отказа:

1. Problem with battery or charging system.

2. Bнизкийn fuse.

3. Неисправностьy connector/damaged wiring

Причина: Voltage is beнизкий 5.0 V for 400 milleseconds.

Возможные причины отказа:

1. Problem with battery or charging system.

2. Bнизкийn fuse.

3. Неисправностьy connector/damaged wiring