Alarms Descriptions 1205
Alarms Descriptions 1205
Alarms Descriptions 1205
ACUXX
ACUXX_009904 Ch35,0099,Prop. Valve Test Set Poin->Suprv. Ch35,0099,Prop. Valve Test S
Description: MBD Special test purposes only
Cause: MBD special test equipment not connected
Effect: No effect on engine.
Alarm is only active in MPC test mode
Sugg. Action: No action required.
The alarm will disappear when MPC is rebooted in normal mode.
If “No command received..” from both ECU‟s: Manual start of startup pump and aux. blower is required
from local control panel.
If “No command received..” from both ECU‟s: Manual start of startup pump and aux. blower is required
from local control panel.
In case of mechanical pump failure: ECS may deliver low or no flow to the HPS.
Sugg. Action: Check cabling to and from:
- Proportional valve
- Proportional valve amplifier
- LVDT amplifier
- MPC
Go to 'Auxiliaries' -> 'Hydraulic System' -> 'Failed pump' to reset failure state.
Further troubleshooting:
1. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HPS'
2. Test failing pump swashplate operation.
3. Compare signals from failing pump to signals from a well functioning pump.
If two or more pumps fail: Engine may not be able to run astern.
Sugg. Action: Run HPS function test
Check:
- Cabling to and from amplifier, ACU and proportional valve
- MPC
- Amplifier
NOTE
If the pump inlet valve is closed, engine start will cause pump cavitation
Sugg. Action: Check:
- Pump inlet valve
- Pump inlet pressure sensor
NOTE
If the pump inlet valve is closed, engine start will cause pump cavitation
Sugg. Action: Check:
- Pump inlet valve
- Pump inlet pressure sensor
On systems with pressurized outer pipe this could be caused by a blocked line brake valve.
Effect: Hydraulic oil leaks from inner to outer pipe.
Sugg. Action: - Detect leaking seals by isolating each double pipe section one by one
- Check line break valves
else
check the signals from the TC cut out valve switches on ACU3, channel 27, 35, 36 and 37.
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check the cabling to the sensor, according to the installation drawings.
Check that the sensor has sufficient power supply (if it is a 2-wire sensor, the supply is integrated in
the signal).
Check the current into terminal "C" of the channel. It must be within 4 mA and 20 mA.
If the current is above or below the range, the current out of the sensor must be checked.
If the current into the MPC is within the range, while the alarm is present, the MPC may be damaged
and must be replaced.
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: - Check cabling to component
- Check that voltage to component is 24V
- Check that power connector voltage is 24V. If not: Check /replace fuse
- Check current in cable to the coil
- Test (or check?) relay
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: - Check cabling to component
- Check that voltage to component is 24V
- Check that power connector voltage is 24V. If not: Check /replace fuse
- Check current in cable to the coil
- Test (or check?) relay
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Actuator Power supply
- Relay channel operation
- Input channel (used for supervision)
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Actuator Power supply
- Relay channel operation
- Input channel (used for supervision)
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE:
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Insulation level by observing the display on the insulation monitor, or
-Insulation level by observing : Maintenance -> Troubleshooting -> Insulation
- Insulation level trend in CoCoS-EDS if applicable
- Individual insulation of ECS components (sensors, controllers, actuators, cabling) to determine the
cause of leakage
- Refer to ECS trouble shooting guide “test for earth failure in ECS system” for further trouble shooting
advise
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check the cabling to the sensor, according to the installation drawings.
Check that the sensor has sufficient power supply (if it is a 2-wire sensor, the supply is integrated in
the signal).
Check the current into terminal "C" of the channel. It must be within 4 mA and 20 mA.
If the current is above or below the range, the current out of the sensor must be checked.
If the current into the MPC is within the range, while the alarm is present, the MPC may be damaged
and must be replaced.
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
If MPC is switched off or power is lost: MPC will loose its time settings
Sugg. Action: Replace battery when convenient
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Switch off MPC immediately.
When MOP A or MOP B are available: Restart MPC
If only one CCU reports failure, check Connector J40-J43 on failing CCU
If OK: Replace CCU
If all CCUs and ECUs report tacho failure, check tacho signals on maintenance screen:
1. Turn the engine minimum one revolution (by turning gear)
2. On failing CCU maintenance screen: Check that channel 40-43 toggle correctly between true and
false
Channel 40 + 41: twice per revolution
Channel 42 + 43: multiple times per revolution (360)
Perform tacho test on MOP, go to 'Maintenance' -> 'Function Test' -> 'Tacho'
Follow tacho test instructions
If only one CCU reports failure, check Connector J44-J47 on failing CCU
If OK: Replace CCU
If all CCUs and ECUs report tacho failure, check tacho signals on maintenance screen:
1. Turn the engine minimum one revolution (by turning gear)
2. On failing CCU maintenance screen: Check that channel 44-47 toggle correctly between true and
false
Channel 44 + 45: twice per revolution
Channel 46 + 47: multiple times per revolution (360)
Perform tacho test on MOP, go to 'Maintenance' -> 'Function Test' -> 'Tacho'
Follow tacho test instructions
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram.
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram.
Fuel telegrams are sent once per revolution. Fuel telegrams contain injection and exhaust valve
operation commands.
Cause: If all CCUs report this failure:
- ECU failure.
Fuel telegrams are sent once per revolution. Fuel telegrams contain injection and exhaust valve
operation commands.
Cause: If all CCUs report this failure:
- ECU failure.
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check cabling
NOTE:
Unless IRM module is used, the location of a ECS component causing the alarm is NOT limited to the
MPC on which the alarm has appeared.
Effect: No immediate effect
The fault can generate other consequential alarms in the ECS system, e.g.
- Exh. Valve Closed Position Changed
- Exh. Valve closing/opening too fast/slow (4 alarms)
- Illegal ELFI/FIVA Position
- ELFI/FIVA Feedback Signal Failure
NOTE:
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Total noise pulse counter by observing : Maintenance -> Troubleshooting -> Insulation
- Cabling, sensors, actuators, MPCs for loose connections or intermittent and/or oscillating electric
leakages/short circuits to ground.
NOTE:
If a CCU is disconnected or stopped for more than 20 minutes, establishing of emergency lubrication
to the affected cylinder is recommended, by fitting of backup lubrication cables from ECU.
NOTE:
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Insulation level by observing the display on the insulation monitor, or
-Insulation level by observing : Maintenance -> Troubleshooting -> Insulation
- Insulation level trend in CoCoS-EDS if applicable
- Individual insulation of ECS components (sensors, controllers, actuators, cabling) to determine the
cause of leakage
- Refer to ECS trouble shooting guide “test for earth failure in ECS system” for further trouble shooting
advise
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
If FIVA movements and exhaust valve are OK: Perform one manual fuel injection attempt.
If manual attempt does not provide any fuel injection: Replace FIVA valve.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
If FIVA movements and exhaust valve are OK: Perform one manual fuel injection attempt.
If manual attempt does not provide any fuel injection: Replace FIVA valve
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate Fuel Plunger and Exhaust Valve to test failing unit
If FIVA movements and exhaust valve are OK: Perform one manual fuel injection attempt.
If manual attempt does not provide any fuel injection: Replace FIVA valve
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
Note:
This alarm also occurs as a consequence of these alarms:
- Illegal Fuel Plunger Movement
- Illegal ELFI/FIVA Position
- ELFI/FIVA Feedback Signal Failure
- Frozen IO Detected
Effect: Fuel injection stopped on affected cylinder
Slow-down is requested.
Sugg. Action: Check:
- Exhaust valve position sensor
- Accumulator pressure
- De-aerating orifice in exhaust valve top
- Non-return valves for exhaust valve actuator oil inlet
- Air spring supply pressure and perform drop-down test of exhaust valve spindle.
- ELFI / FIVA valve
NOTE
This alarm also occurs as a consequence of these alarms:
- Illegal Fuel Plunger Movement
- Illegal ELFI/FIVA Position
- ELFI/FIVA Feedback Signal Failure
- Frozen IO Detected
Effect: -Slow-down is requested.
If the parameter “Close Pos Changed Fuel Cut Out” is active then:
If the parameter “Close Pos Changed Fuel Cut Out” is passive then:
If the parameter “Close Pos Changed Fuel Cut Out” is active then:
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
Check:
- Low force Reduction Station spring Air
- Air spring
- Pressure sensor
Check:
- Air spring supply pressure
- Air spring
- Exhaust valve position sensor
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation
4. Compare signals from failing unit to signals from a well functioning unit.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
Until parameter adjustment is carried out, monitor exhaust gas temperature carefully:
- If temperature is OK: Continuous running is OK.
- If temperature NOT OK: Shut off affected cylinder. Reduce load and speed.
NOTE
In case of lubrication failure, ECS will not request slowdown
Sugg. Action: Check:
- Cabling
- Sensor
Until parameter adjustment is carried out, monitor exhaust gas temperature carefully:
- If temperature is OK: Continuous running is OK.
- If temperature NOT OK: Shut off affected cylinder. Reduce load and speed.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
NOTE
In case of „Exhaust Valve Open Stroke Low‟ alarm, ECS will not request slowdown
Sugg. Action: Check:
- Cabling (junction box)
- Sensor
- CCU input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
In case of lubrication failure, ECS will not request slowdown
Sugg. Action: Check:
- Cabling
- Sensor
NOTE
In case of lubrication failure, ECS will not request slowdown
Sugg. Action: Check:
- Cabling
- Sensor
If MPC is switched off or power is lost: MPC will loose its time settings
Sugg. Action: Replace battery when convenient
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Switch off MPC immediately.
When MOP A or MOP B are available: Restart MPC
Disconnect the failing input source or invalidate the input channel. Repair or replace the failing source
at first opportunity.
NOTE
Speed set point cannot be changed from the active control station!
Sugg. Action: To regain speed set control: Switch control station immediately
If all CCUs and ECUs report tacho failure, check tacho signals on maintenance screen:
1. Turn the engine minimum one revolution (by turning gear)
2. On failing CCU maintenance screen: Check that channel 40-43 toggle correctly between true and
false
Channel 40 + 41: twice per revolution
Channel 42 + 43: multiple times per revolution (360)
If all CCUs and ECUs report tacho failure, check tacho signals on maintenance screen:
1. Turn the engine minimum one revolution (by turning gear)
2. On failing CCU maintenance screen: Check that channel 40-43 toggle correctly between true and
false
Channel 44 + 45: twice per revolution
Channel 46 + 47: multiple times per revolution (360)
Perform tacho test on MOP, go to 'Maintenance' -> 'Function Test' -> 'Tacho'
Follow tacho test instructions
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram.
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram.
NOTE:
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Insulation level by observing the display on the insulation monitor, or
-Insulation level by observing : Maintenance -> Troubleshooting -> Insulation
- Insulation level trend in CoCoS-EDS if applicable
- Individual insulation of ECS components (sensors, controllers, actuators, cabling) to determine the
cause of leakage
- Refer to ECS trouble shooting guide “test for earth failure in ECS system” for further trouble shooting
advise
Disconnect the failing input source or invalidate the input channel. Repair or replace the failing source
at first opportunity.
Check for:
- Hydraulic pump related alarms
- Hydraulic leakages
- Failing bypass valves
Disconnect the failing input source or invalidate the input channel. Repair or replace the failing source
at first opportunity.
Disconnect the failing input source or invalidate the input channel. Repair or replace the failing source
at first opportunity.
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Start air distributor position switch
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Start air distributor position switch
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
If „Start‟ is initiated from ECR or LOP, engine will attempt to start even if no blowers are running.
Sugg. Action: 1. Check that the operation control switch at the switchboard is set to 'Remote'
2. Check switchboard, main breaker and overcurrent protection relay
3. Check cabling
NOTE
This alarm may occur during wind milling. In this case, this alarm can be ignored.
Effect: Engine performance and HPS pressure may be reduced.
Engine will shut down, if the HPS pressure drops below shutdown level.
Sugg. Action: Check:
- Hydraulic system for leaks
- Swash plate pumps for mechanical failures
- Proportional valves
NOTE
This alarm may occur during wind milling. In this case, this alarm can be ignored.
Effect: Engine performance and HPS pressure may be reduced.
Engine will shut down, if the HPS pressure drops below shutdown level.
Sugg. Action: Check:
- Hydraulic system for leaks
- Swash plate pumps for mechanical failures
- Proportional valves
In case of mechanical pump failure: ECS may deliver low or no flow to the HPS.
Sugg. Action: Check cabling to and from:
- Proportional valve
- Proportional valve amplifier
- LVDT amplifier
- MPC
Go to 'Auxiliaries' -> 'Hydraulic System' -> 'Failed pump' to reset failure state.
Further troubleshooting:
1. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HPS'
2. Test failing pump swashplate operation.
3. Compare signals from failing pump to signals from a well functioning pump.
NOTE
NEVER cancel pump torque limiter, unless one or more swash plate pumps do not deliver sufficient
flow.
Cause: Pump torque restriction has been cancelled manually (Chief-level access required).
Effect: No pump torque restrictions
Sugg. Action: Enable the torque limiter as soon as the problem is solved.
If hydraulic pressure can be maintained when both pumps are running, switch master pump:
'Auxiliaries' -> 'Hydraulic System'
NOTE
If the pump inlet valve is closed, engine start will cause pump cavitation
Sugg. Action: Check:
- Pump inlet valve
- Pump inlet pressure sensor
NOTE
If the pump inlet valve is closed, engine start will cause pump cavitation
Sugg. Action: Check:
- Pump inlet valve
- Pump inlet pressure sensor
NOTE
If the pump inlet valve is closed, engine start will cause pump cavitation
Sugg. Action: Check:
- Pump inlet valve
- Pump inlet pressure sensor
If b, c, and d:
No effect on engine performance.
Sugg. Action: Check:
a. Hydraulic pump
b. Cabling
c. MPC
d. Sensor
If b, c, or d:
Repair or replace failing part
If b, c, and d:
No effect on engine performance.
Sugg. Action: Check:
a. Hydraulic pump
b. Cabling
c. MPC
d. Sensor
If b, c, or d:
Repair or replace failing part
If b, c, and d:
No effect on engine performance.
Sugg. Action: Check:
a. Hydraulic pump
b. Cabling
c. MPC
d. Sensor
If b, c, or d:
Repair or replace failing part
NOTE
If system oil pressure drops below shutdown level:
Engine control system will request shutdown.
Sugg. Action: Check:
- Inlet pressure sensors
- Lubrication oil supply system(pumps, valves, etc)
Check:
- Hydraulic system for leaks
- Engine driven pump
In case of mechanical pump failure: ECS may deliver low or no flow to the HPS.
Sugg. Action: Check cabling to and from:
- Proportional valve
- Proportional valve amplifier
- LVDT amplifier
- MPC
Go to 'Auxiliaries' -> 'Hydraulic System' -> 'Failed pump' to reset failure state.
Further troubleshooting:
1. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HPS'
2. Test failing pump swashplate operation.
3. Compare signals from failing pump to signals from a well functioning pump.
If hydraulic pressure can be maintained when both pumps are running, switch master pump:
'Auxiliaries' -> 'Hydraulic System'
If MPC is switched off or power is lost: MPC will loose its time settings
Sugg. Action: Replace battery when convenient
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Switch off MPC immediately.
When MOP A or MOP B are available: Restart MPC
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Check:
- Input channel
- Cabling and connectors
If multiple 'Lock in last' alarms are raised: Check for loose connections in the serial connection
between ECS and AMS.
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
If problem persists:
- Restart EICU
Note: Analog handle Stop is ON when handle speed set is zero RPM!
Effect: Engine start can not be performed from current control station.
Sugg. Action: Check:
- Analog handle signal and stop switch signal at current control station
- Stop switch
- Analog handle signal and calibration
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Check:
- RCS signals
- Cabling
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
Running ahead:
No effect on engine performance.
Hydraulic pressure may increase.
Running astern:
Reversing the engine may not be possible due to insufficient hydraulic pressure.
Sugg. Action: Check:
- Other alarms to locate the root cause for the pump alarms
- That the MPC is in normal running mode
Running ahead:
No effect on engine performance.
Hydraulic pressure may increase.
Running astern:
Reversing the engine may not be possible due to insufficient hydraulic pressure.
Sugg. Action: Check:
- Other alarms to locate the root cause for the pump alarms
- That the MPC is in normal running mode
Running ahead:
No effect on engine performance.
Hydraulic pressure may increase.
Running astern:
Reversing the engine may not be possible due to insufficient hydraulic pressure.
Sugg. Action: Check:
- Other alarms to locate the root cause for the pump alarms
- That the MPC is in normal running mode
Running ahead:
No effect on engine performance.
Hydraulic pressure may increase.
Running astern:
Reversing the engine may not be possible due to insufficient hydraulic pressure.
Sugg. Action: Check:
- Other alarms to locate the root cause for the pump alarms
- That the MPC is in normal running mode
Running ahead:
No effect on engine performance.
Hydraulic pressure may increase.
Running astern:
Reversing the engine may not be possible due to insufficient hydraulic pressure.
Sugg. Action: Check:
- Other alarms to locate the root cause for the pump alarms
- That the MPC is in normal running mode
NOTE
If more than 3 pumps are installed, pump 4 and 5 are controlled by the ECUs
Effect: - High pressure pumps move to fail safe position (maximum flow in ahead direction)
- Reversing the engine may not be possible due to insufficient hydraulic pressure
Sugg. Action: Check other alarms to locate the root cause for the pump alarms
NOTE
NEVER ignore this alarm. Safe critical issues may arise!
Reselect Shop Test Mode or Not Shop Test Mode on the ECT screen
Changes 1 and 3 are only in effect when ECR is the active control station.
Sugg. Action: It is ok for this alarm to be active during shop test when the ECT is being used for engine
commissioning.
Before finishing shop test it is necessary to toggle Shop Test Mode to off via the ECT application.
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
NOTE:
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Insulation level by observing the display on the insulation monitor, or
-Insulation level by observing : Maintenance -> Troubleshooting -> Insulation
- Insulation level trend in CoCoS-EDS if applicable
- Individual insulation of ECS components (sensors, controllers, actuators, cabling) to determine the
cause of leakage
- Refer to ECS trouble shooting guide “test for earth failure in ECS system” for further trouble shooting
advise
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
Disconnect the failing input source or invalidate the input channel. At first opportunity: Repair or
replace the failing source.
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
Disconnect the failing input source or invalidate the input channel. At first opportunity: Repair or
replace the failing source.
EICUXX_2300- Ch22,2300-B,Inc Lim from Bridge Bac->Suprv. Ch22,2300-B,Inc Lim from Bri
Description: Sensor signal is out of range
Cause: - Cabling failure, or
- Sensor failure, or
- Supervision resistor across the switch is missing, or
- MPC input channel failure
Effect: If redundant cabling to EICUA and EICUB is fitted:
No effect on engine performance.
Disconnect the failing input source or invalidate the input channel. At first opportunity: Repair or
replace the failing source.
Deviation between:
- redundant input signals to EICU A and EICU B, or
- redundant input signals from RCS
Effect: Redundancy reduced
Sugg. Action: Check:
- EICU cabling
- RCS signals
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
NOTE
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Cabling
- Sensor
- Supervision resistor
- MPC input channel: 'Maintenance' -> 'System View I/O Test'
If MPC is switched off or power is lost: MPC will loose its time settings
Sugg. Action: Replace battery when convenient
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Switch off MPC immediately.
When MOP A or MOP B are available: Restart MPC
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because one of the EICU's report, that the MPC is not running in normal
mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because one of the EICU's report, that the MPC is not running in normal
mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because both EICU A and EICU B report, that the MPC is not running in
normal mode (App. not running on .. ). Other alarms in the group are raised as a consequence of this
condition. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MPC is restarting after power off/on, or
- MPC in test or configuration mode, or
- MPC failure
Effect: MPC not ready.
Redundancy reduced.
Sugg. Action: Check MPC mode status
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
This group alarm is raised because Amplifier has reached the current limit. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: - FIVA failure, or
- Cabling failure, or
- Amplifier failure, or
- CCU fuse (F9) for amplifier is blown
Effect: No fuel injection.
No exhaust valve operation.
Slowdown is requested
Sugg. Action: 1. Check FIVA cabling
2. Stop the engine at first opportunity
3. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
4. Test failing unit‟s injection and exhaust valve operation
5. Compare signals from failing unit to signals from a well functioning unit
6. Reduce 'Chief Index limit [%]' first and then Re-enable HCU:
In case of mechanical pump failure: ECS may deliver low or no flow to the HPS.
Sugg. Action: Check cabling to and from:
- Proportional valve
- Proportional valve amplifier
- LVDT amplifier
- MPC
Go to 'Auxiliaries' -> 'Hydraulic System' -> 'Failed pump' to reset failure state.
Further troubleshooting:
1. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HPS'
2. Test failing pump swashplate operation.
3. Compare signals from failing pump to signals from a well functioning pump.
In case of mechanical pump failure: ECS may deliver low or no flow to the HPS.
Sugg. Action: Check cabling to and from:
- Proportional valve
- Proportional valve amplifier
- LVDT amplifier
- MPC
Go to 'Auxiliaries' -> 'Hydraulic System' -> 'Failed pump' to reset failure state.
Further troubleshooting:
1. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HPS'
2. Test failing pump swashplate operation.
3. Compare signals from failing pump to signals from a well functioning pump.
This group alarm is caused by 'Delta Tacho B too big'. To view all alarms in the group: Press +/- at the
bottom of the MOP screen.
Cause: The angle between tacho set A and B marker signal exceeds the limit.
Effect: If the system switches from tacho set A to B, maximum pressure deviation may occur.
Sugg. Action: If the alarm 'Tacho set A failure' or 'Tacho set B failure' is active: Ignore this alarm.
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Activate 'Fuel Plunger' and 'Exhaust Valve' to test failing unit
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
This group alarm is caused by 'ELFI/FIVA feedback signal failure'. Other alarms in the group are raised
as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom of the
MOP screen.
Cause: - Loose connection.
- Internal ELFI/FIVA-feedback failure.
Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing unit
Further troubleshooting:
1. Stop the engine at first opportunity
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s injection and exhaust valve operation.
4. Compare signals from failing unit to signals from a well functioning unit.
Running ahead:
No effect on engine performance.
Hydraulic pressure may increase.
Running astern:
Reversing the engine may not be possible due to insufficient hydraulic pressure.
Sugg. Action: Check:
- Other alarms to locate the root cause for the pump alarms
- That the MPC is in normal running mode
Running ahead:
No effect on engine performance.
Hydraulic pressure may increase.
Running astern:
Reversing the engine may not be possible due to insufficient hydraulic pressure.
Sugg. Action: Check:
- Other alarms to locate the root cause for the pump alarms
- That the MPC is in normal running mode
Running ahead:
No effect on engine performance.
Hydraulic pressure may increase.
Running astern:
Reversing the engine may not be possible due to insufficient hydraulic pressure.
Sugg. Action: Check:
- Other alarms to locate the root cause for the pump alarms
- That the MPC is in normal running mode
Running ahead:
No effect on engine performance.
Hydraulic pressure may increase.
Running astern:
Reversing the engine may not be possible due to insufficient hydraulic pressure.
Sugg. Action: Check:
- Other alarms to locate the root cause for the pump alarms
- That the MPC is in normal running mode
Running ahead:
No effect on engine performance.
Hydraulic pressure may increase.
Running astern:
Reversing the engine may not be possible due to insufficient hydraulic pressure.
Sugg. Action: Check:
- Other alarms to locate the root cause for the pump alarms
- That the MPC is in normal running mode
Check:
- Hydraulic system for leaks
- Engine driven pump
If b, c, and d:
No effect on engine performance.
Sugg. Action: Check:
a. Hydraulic pump
b. Cabling
c. MPC
d. Sensor
If b, c, or d:
Repair or replace failing part
If b, c, and d:
No effect on engine performance.
Sugg. Action: Check:
a. Hydraulic pump
b. Cabling
c. MPC
d. Sensor
If b, c, or d:
Repair or replace failing part
If b, c, and d:
No effect on engine performance.
Sugg. Action: Check:
a. Hydraulic pump
b. Cabling
c. MPC
d. Sensor
If b, c, or d:
Repair or replace failing part
This group alarm is raised because both EICU A and EICU B report, that the "Handle Stop position
and Stop Switch Position" does not match. To view all alarms in this group: Press +/- at the bottom of
the MOP screen.
Cause: - Stop switch or signal failure, or
- Analog handle or signal failure, or
- Analog handle stop is ON and Stop Switch is OFF, or
- Analog handle stop is OFF and Stop Switch is ON
Note: Analog handle Stop is ON when handle speed set is zero RPM!
Effect: Engine start can not be performed from current control station.
Sugg. Action: Check:
- Analog handle signal and stop switch signal at current control station
- Stop switch
- Analog handle signal and calibration
This group alarm is raised because both ECU A and ECU B report, that 'Insufficient blowers capacity'
has occurred. To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: Less than half of the installed blowers are running.
Effect: Engine cannot be started from bridge control station.
NOTE
If „Start‟ is initiated from ECR or LOP, engine will attempt to start even if no blowers are running.
Sugg. Action: 1. Check that the operation control switch at the switchboard is set to 'Remote'
2. Check switchboard, main breaker and overcurrent protection relay
3. Check cabling
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Plunger position sensor or cable failure, or
- ELFI / FIVA valve failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
If the sensor is replaced, go to: 'Maintenance' -> 'Function Test' to recalibrate the sensor.
Reactivate fuel injection. Go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Further troubleshooting:
1. Stop the engine at first opportunity.
2. Go to: 'Maintenance' -> 'Troubleshooting' -> 'HCU'
3. Test failing unit‟s fuel plunger operation
NOTE
Alarm can be overridden by invalidating channel 31 on affected CCU and reactivating fuel injection on
'Maintenance' -> 'System View I/O Test'
NOTE
This alarm may occur during wind milling. In this case, this alarm can be ignored.
Effect: Engine performance and HPS pressure may be reduced.
Engine will shut down, if the HPS pressure drops below shutdown level.
Sugg. Action: Check:
- Hydraulic system for leaks
- Swash plate pumps for mechanical failures
- Proportional valves
Check for:
- Hydraulic pump related alarms
- Hydraulic leakages
- Failing bypass valves
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram.
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MOP is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen
Cause: - Cable failure, or
- Network failure, or
- MOP failure
Effect: No effect on engine performance.
No MOP redundancy.
Sugg. Action: If network A is the only failing network, check:
- Cabling
- MOP network connector
- MOP network card
This group alarm is raised because both EICU A and EICU B report, that the MOP is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen
Cause: - Cable failure, or
- Network failure, or
- MOP failure
Effect: No effect on engine performance.
No MOP redundancy.
Sugg. Action: If network A is the only failing network, check:
- Cabling
- MOP network connector
- MOP network card
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network A. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network A is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network A is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the MOP is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- Network failure, or
- MOP failure
Effect: No effect on engine.
No MOP redundancy.
Sugg. Action: If network B is the only failing network, check:
- Cabling
- MOP network connector
- MOP network card
This group alarm is raised because both EICU A and EICU B report, that the MOP is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- Network failure, or
- MOP failure
Effect: No effect on engine.
No MOP redundancy.
Sugg. Action: If network B is the only failing network, check:
- Cabling
- MOP network connector
- MOP network card
This group alarm is raised because both EICU A and EICU B report, that the MPC is disconnected
from network B. Other alarms in the group are raised as a consequence of this condition. To view all
alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - Cable failure, or
- MPC failure, or
- Network failure
Effect: If network B is the only failing network:
No effect on engine.
Redundancy reduced.
Sugg. Action: If network B is the only failing network, check:
- MPC
- Cabling and connectors
This group alarm is raised because both EICU A and EICU B report, that the ACU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - ACU is restarting after power off/on, or
- ACU power is off, or
- ACU failure, or
- Both networks are disconnected or failing
Effect: HPS performance affected.
Control of main hydraulic pump and start-up pump is lost.
Sugg. Action: Check:
- ACU power
- ACU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the ACU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - ACU is restarting after power off/on, or
- ACU power is off, or
- ACU failure, or
- Both networks are disconnected or failing
Effect: HPS performance affected.
Control of main hydraulic pump and start-up pump is lost.
Sugg. Action: Check:
- ACU power
- ACU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the ACU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - ACU is restarting after power off/on, or
- ACU power is off, or
- ACU failure, or
- Both networks are disconnected or failing
Effect: HPS performance affected.
Control of main hydraulic pump and start-up pump is lost.
Sugg. Action: Check:
- ACU power
- ACU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the CCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - CCU is restarting after power off/on, or
- CCU power is off, or
- CCU failure, or
- Both networks are disconnected or failing
Effect: No fuel injection.
Exhaust valve operation may stop.
Cylinder lubrication may stop.
Slowdown is requested.
Sugg. Action: Check:
- CCU power
- CCU mode (LED is green)
- Network cabling
This group alarm is raised because the EICU is disconnected from both network A and B. Other
alarms in the group are raised as a consequence of this condition. To view all alarms in this group:
Press +/- at the bottom of the MOP screen.
Cause: - EICU is restarting after power off/on, or
- EICU power is off, or
- EICU failure, or
- Both networks are disconnected or failing
Effect: No EICU redundancy
Sugg. Action: Check:
- EICU power
- EICU mode (LED is green)
- Network cabling
This group alarm is raised because the EICU is disconnected from both network A and B. Other
alarms in the group are raised as a consequence of this condition. To view all alarms in this group:
Press +/- at the bottom of the MOP screen.
Cause: - EICU is restarting after power off/on, or
- EICU power is off, or
- EICU failure, or
- Both networks are disconnected or failing
Effect: No EICU redundancy
Sugg. Action: Check:
- EICU power
- EICU mode (LED is green)
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the MOP is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MOP is restarting after power off/on, or
- MOP power is off, or
- MOP failure, or
- Both networks are disconnected or failing, or
- MOP network card failure
Effect: No effect on engine.
No MOP redundancy.
Sugg. Action: Check:
- MOP power
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the MOP is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - MOP is restarting after power off/on, or
- MOP power is off, or
- MOP failure, or
- Both networks are disconnected or failing, or
- MOP network card failure
Effect: No effect on engine.
No MOP redundancy.
Sugg. Action: Check:
- MOP power
- Network cabling
This group alarm is raised because both EICU A and EICU B report, that the SCU is disconnected
from both network A and B. Other alarms in the group are raised as a consequence of this condition.
To view all alarms in this group: Press +/- at the bottom of the MOP screen.
Cause: - SCU is restarting after power off/on, or
- SCU power is off, or
- SCU failure, or
- Both networks are disconnected or failing
Effect: Variable turbocharger/bypass valve moves to fully open position
Sugg. Action: Check:
- SCU power
- SCU mode (LED is green)
- Network cabling
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
This group alarm is caused by 'No cylinder lubrication', reported by both EICU A and EICU B. To view
all alarms in the group: Press +/- at the bottom of the MOP screen.
Cause: - Lubricator failure, or
- Cable failure (loose connection)
Effect: - No lubrication oil is injected
- Slowdown is requested
Sugg. Action: Check that lubricator solenoid LED is flashing
If problem persists:
- Restart EICU
NOTE
If system oil pressure drops below shutdown level:
Engine control system will request shutdown.
Sugg. Action: Check:
- Inlet pressure sensors
- Lubrication oil supply system(pumps, valves, etc)
NOTE
If the pump inlet valve is closed, engine start will cause pump cavitation
Sugg. Action: Check:
- Pump inlet valve
- Pump inlet pressure sensor
NOTE
If the pump inlet valve is closed, engine start will cause pump cavitation
Sugg. Action: Check:
- Pump inlet valve
- Pump inlet pressure sensor
NOTE
If the pump inlet valve is closed, engine start will cause pump cavitation
Sugg. Action: Check:
- Pump inlet valve
- Pump inlet pressure sensor
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
This group alarm is caused by 'Illegal ELFI/FIVA position'. Other alarms in the group are raised as a
consequence of this condition. To view all alarms in the group: Press +/- at the bottom of the MOP
screen.
Cause: - ELFI / FIVA position sensor signal failure, or
- ELFI / FIVA failure, or
- CCU failure
Effect: No fuel injection due to risk of untimed fuel injection.
Reactivate fuel injection, go to 'Engine' -> 'Chief Limiters' -> 'HCU Status and Reset' to reset failing
unit.
Do not reactivate fuel injection until the cylinder unit is considered to be OK.
Reactivation only possibly for speed below 'HCU ReEnable Max Speed'
NOTE
This alarm may occur during wind milling. In this case, this alarm can be ignored.
Effect: Engine performance and HPS pressure may be reduced.
Engine will shut down, if the HPS pressure drops below shutdown level.
Sugg. Action: Check:
- Hydraulic system for leaks
- Swash plate pumps for mechanical failures
- Proportional valves
If increased swash plate position is required: Cancel torque limitation, 'Auxiliaries' -> 'Hydraulic System'
This is a group alarm caused by a shutdown order from the safety system. Other alarms in the group
are raised as a consequence of this condition. To view all alarms in this group: Press +/- at the bottom
of the MOP screen.
Cause: 1. Requested by engine control system due to:
- Hydraulic leakages from HPS, or
- System oil inlet pressure too low, or
- Hydraulic high pressure too low
If hydraulic pressure can be maintained when both pumps are running, switch master pump:
'Auxiliaries' -> 'Hydraulic System'
If hydraulic pressure can be maintained when both pumps are running, switch master pump:
'Auxiliaries' -> 'Hydraulic System'
Changes 1 and 3 are only in effect when ECR is the active control station.
Sugg. Action: Check:
- EICU cabling
Reselect Shop Test Mode or Not Shop Test Mode on the ECT screen
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram
This group alarm is caused by multiple 'Tacho set A failure' alarms. Other alarms in the group are
raised as a consequence of this condition. To view the alarms in the group: Press +/- at the bottom of
the MOP screen.
Cause: - Cabling failure (loose connection etc.), or
- Flywheel marker sensor failure, or
- Encoder failure, or
- Tacho amplifier A failure, or
- Sensor support console failure, or
- Power failure (ECUA powers tacho set A)
If all CCUs and ECUs report tacho A failure, check tacho signals on maintenance screen and power to
tacho amplifier TCA-A:
1. Check power on the tacho amplifier TSA-A connector J5 pin (J,A) J=24V A=0V.
2. Turn the engine minimum one revolution (by turning gear)
3. On failing ECU or CCU maintenance screen: Check that channel 40-43 toggle correctly between
true and false
Channel 40 + 41: twice per revolution
Channel 42 + 43: multiple times per revolution (360)
NOTE
If encoder A is readjusted or replaced: Perform PMI measurement, and restore tacho offset settings
according to 0-diagram.
This group alarm is caused by multiple 'Tacho set B failure' alarms. Other alarms in the group are
raised as a consequence of this condition. To view the alarms in the group: Press +/- at the bottom of
the MOP screen.
Cause: - Cabling failure (loose connection etc.), or
- Encoder failure, or
- Tacho amplifier B failure, or
- Sensor support console failure, or
- Power failure (ECUB powers tacho set B)
If all CCUs and ECUs report tacho B failure, check tacho signals on maintenance screen and power to
tacho amplifier TCA-B:
1. Check power on the tacho amplifier TSA-B connector J5 pin (J,A) J=24V A=0V.
2. Turn the engine minimum one revolution (by turning gear)
3. On failing ECU or CCU maintenance screen: Check that channel 44-47 toggle correctly between
true and false
Channel 44 + 45: twice per revolution
Channel 46 + 47: multiple times per revolution (360)
NOTE
NEVER cancel pump torque limiter, unless one or more swash plate pumps do not deliver sufficient
flow.
Cause: Pump torque restriction has been cancelled manually (Chief-level access required).
Effect: No pump torque restrictions
Sugg. Action: Enable the torque limiter as soon as the problem is solved.
NOTE
If more than 3 pumps are installed, pump 4 and 5 are controlled by the ECUs
Effect: - High pressure pumps move to fail safe position (maximum flow in ahead direction)
- Reversing the engine may not be possible due to insufficient hydraulic pressure
Sugg. Action: Check other alarms to locate the root cause for the pump alarms
NOTE
NEVER ignore this alarm. Safe critical issues may arise!
This is an alarm caused by a shutdown order from the safety system and one or more MPC's does not
report shutdown.
Cause: - Shutdown feedback signal from affected MPC delayed or missing, or
- No shutdown signal from safety system
Effect: One or more MPC may try to keep engine running because it may not have received the shut down
signal from the safety system.
Sugg. Action: Check:
- MPCs, that have not confirmed the shutdown. Power off, if necessary.
- Cabling and signal from safety system to J32 for CCUs and J34 for ECUs.
NOTE:
Never ignore this alarm. Safety critical issues may arise.
Sugg. Action: Check:
- Insulation level by observing the display on the insulation monitor, or
-Insulation level by observing : Maintenance -> Troubleshooting -> Insulation
- Insulation level trend in CoCoS-EDS if applicable
- Individual insulation of ECS components (sensors, controllers, actuators, cabling) to determine the
cause of leakage
- Refer to ECS trouble shooting guide “test for earth failure in ECS system” for further trouble shooting
advise
If the problem persists, check actual variable turbocharger position/bypass valve position. If necessary,
open variable turbocharger/ bypass valve by local control or mechanically (refer to actuator manual).
If the problem persists: Open variable turbocharger/bypass valve by local control or mechanically (refer
to actuator manual).
If all is ok:
1. Switch to manual mode to reset alarm
2. Switch back to automatic control
If all is ok:
1. Switch to manual mode to reset alarm
2. Switch back to automatic control
Check:
- Actuator cabling
- If bypass valve can move
- Actuator end stop switches
NOTE
If bypass valve is stuck in closed or partly closed position, keep the engine load below 75%
Sugg. Action: 1. Reset bypass valve control on MOP. 'Auxiliaries' -> 'Scavenge Air' -> 'Variable Bypass' (requires
Chief level access and manual control)
2. Reset actuator on MOP
3. Power bypass valve off and on
If engine load above 75% is required, open bypass valve mechanically or via MOP.
If the valve is closed or partially closed, keep engine load below 75%.
Sugg. Action: Reset the bypass valve control on MOP, 'Auxiliaries' -> 'Scavenge Air' -> 'Variable Bypass' (requires
Chief level access and manual control)
If engine load above 75% is required, move bypass valve to fully open position.
Check:
- Network connection to SCU on MOP, Maintenance -> Network
- Scavenging air pressure cabling, signal must be within range (4-20mA)
Check:
- Network connection to SCU on MOP, Maintenance -> Network
- Scavenging air pressure cabling, signal must be within range (4-20mA)
NOTE
If engine load above 75% is required, open variable turbocharger/bypass valve mechanically or via
MOP
Check:
- Network connection to SCU on MOP, Maintenance -> Network
- Scavenging air pressure cabling, signal must be within range (4-20mA)
NOTE
If variable turbocharger is stuck in closed or partly closed position, keep the engine load below 75%
Sugg. Action: 1. Reset variable turbocharger control on MOP, 'Auxiliaries' -> 'Scavenge Air' -> 'Main' (requires chief
level and manual control)
2. Reset actuator on MOP
3. Power variable turbocharger cabinet off and on
NOTE
If engine load above 75% is required, move variable turbocharger to fully open position
NOTE
If variable turbocharger is stuck in closed or partly closed position, keep the engine load below 75%
Sugg. Action: If the variable turbocharger is closed or partially closed, keep engine load below 75%.
If engine load above 75% is required, move variable turbocharger to fully open position.
Reset actuator (on MOP or power variable turbocharger off and on).
NOTE
If variable turbocharger is stuck in closed or partly closed position, keep the engine load below 75%
Sugg. Action: 1. Reset variable turbocharger control on MOP, 'Auxiliaries' -> 'Scavenge Air' -> 'Main' (requires chief
level and manual control)
2. Reset actuator on MOP
3. Power variable turbocharger cabinet off and on
NOTE
If engine load above 75% is required, move variable turbocharger to fully open position
NOTE
If variable turbocharger is stuck in closed or partly closed position, keep the engine load below 75%
Sugg. Action: If the variable turbocharger is closed or partially closed, keep engine load below 75%.
If engine load above 75% is required, move variable turbocharger to fully open position.
Reset actuator (on MOP or power variable turbocharger off and on).
NOTE
If variable turbocharger is stuck in closed or partly closed position, keep the engine load below 75%
Sugg. Action: 1. Reset variable turbocharger control on MOP, 'Auxiliaries' -> 'Scavenge Air' -> 'Main' (requires chief
level and manual control)
2. Reset actuator on MOP
3. Power variable turbocharger cabinet off and on
NOTE
If engine load above 75% is required, move variable turbocharger to fully open position
NOTE
If variable turbocharger is stuck in closed or partly closed position, keep the engine load below 75%
Sugg. Action: If the variable turbocharger is closed or partially closed, keep engine load below 75%.
If engine load above 75% is required, move variable turbocharger to fully open position.
Reset actuator (on MOP or power variable turbocharger off and on).
NOTE
If variable turbocharger is stuck in closed or partly closed position, keep the engine load below 75%
Sugg. Action: 1. Reset variable turbocharger control on MOP, 'Auxiliaries' -> 'Scavenge Air' -> 'Main' (requires chief
level and manual control)
2. Reset actuator on MOP
3. Power variable turbocharger cabinet off and on
NOTE
If engine load above 75% is required, move variable turbocharger to fully open position
NOTE
If variable turbocharger is stuck in closed or partly closed position, keep the engine load below 75%
Sugg. Action: If the variable turbocharger is closed or partially closed, keep engine load below 75%.
If engine load above 75% is required, move variable turbocharger to fully open position.
Reset actuator (on MOP or power variable turbocharger off and on).
SCUXX_1950 Waste Heat Recovery 2->PT flow area above max. allowed
Description: Power Turbine control valve exceeds the Allowed Level for too long time.
Cause: Power Turbine has not reduced opening of the control valve to allowed level.
Signals -allowed and actual Power Turbine have wrong values.
The signal "PT Valve Actual Position" signal has a value above the signal "Available Exh. Energy"
Effect: Low scavenging air pressure - leading to low efficiency.
High exhaust and combustion chamber temperatures leading to increased wear on components.
Sugg. Action: Check:
- WHR/PMS system.
- signal levels on WHR and ECS systems.
Reduce Power Turbine control valve opening if possible.
If Power turbine control valve continues to operate significantly above allowed level, Power Turbine
should be disabled in the load ranges where it operates above limit
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move variable turbocharger/bypass valve to fully open position.
If only one Pscav sensor is used, or if both Pscav sensors are failing, variable turbocharger will use
last valid control value.
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move variable turbocharger/bypass valve to fully open position.
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move variable turbocharger/bypass valve to fully open position.
SCUXX_870104 Ch22,8701,TC Turb Inlet Temp (WHR2)->Suprv. Ch22,8701,TC Turb Inlet Temp
Description: Turbo Charger Turbine Inlet Temperature sensor signal is out o range (4-20mA)
Cause: - Cable failure, or
- Sensor failure
Effect: Temperature measurement is lost.
No effect on engine performance.
Sugg. Action: Check cabling
Check:
- Cabling
- Position measurement.
NOTE
If engine load above 75% is required, move bypass valve to fully open position
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move bypass valve to fully open position
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move variable turbocharger to fully open position
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move variable turbocharger to fully open position
Redundancy reduced
Redundancy reduced
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move variable turbocharger/bypass valve to fully open position.
If MPC is switched off or power is lost: MPC will loose its time settings
Sugg. Action: Replace battery when convenient
NOTE
Never ignore this alarm. Safety critical issues may arise!
Sugg. Action: Switch off MPC immediately.
When MOP A or MOP B are available: Restart MPC