You are on page 1of 84

Alarms Reference

CCUXX
CCUXX_010103

Tacho set A->Tacho set A failure

Description: Faulty or missing Tacho signals.


Cause: - Wiring, sensors or encoders are faulty, or
- Damaged tacho amplifier (loose connections in box, or.
- Loose connections in cable ends, or
- Damaged sensor support console, or
- Damaged teeth on tacho wheel (if fitted) , or
- Power failure (CCU1 powers Tacho Set A and CCU2 powers Tacho Set B).
Effect: The MPC had to change active set of tacho sensors.
If both tacho sensor set A and B fail on one CCU:
- Injection is stopped on one or two cylinders.
- Cylinder lubrication is stopped on affected cylinders!
Sugg. Action:

If all CCUs report tacho failure:


- Fault is most likely found in encoder/trigger ring sensors, amplifier or amplifier related cabling.
- If Tacho A reports the problem: Check flywheel sensor.
If only one CCU reports tacho failure:
- Check diode flash pattern (Ch40-Ch47) on MPC and compare to normally working CCU. This will
verify CCU and cable connections.
If both Tacho Set A and B reports tacho failure:
- Backup lubrication cables MUST be mounted on affected cylinders.
If all signals on one tacho stay low:
- Check tacho sensor power.
Hint: All sensor signals toggle between zero and high at least once per revolution.
To troubleshoot the problem: Perform tacho test on MOP:
- Navigate to Maintenance -> Function Test screen.
- Perform Tacho tests and follow instruction.

CCUXX_010104

Tacho set B->Tacho set B failure

Description: Faulty or missing Tacho signals.


Cause: - Wiring, sensors or encoders are faulty, or
- Damaged tacho amplifier (loose connections in box, or.
- Loose connections in cable ends, or
- Damaged sensor support console, or
- Damaged teeth on tacho wheel (if fitted) , or
- Power failure (CCU1 powers Tacho Set A and CCU2 powers Tacho Set B).
Effect: The MPC had to change active set of tacho sensors.
If both tacho sensor set A and B fail on one CCU:
- Injection is stopped on one or two cylinders.
- Cylinder lubrication is stopped on affected cylinders!
Sugg. Action:

If all CCUs report tacho failure:


- Fault is most likely found in encoder/trigger ring sensors, amplifier or amplifier related cabling.
- If Tacho A reports the problem: Check flywheel sensor.
If only one CCU reports tacho failure:
- Check diode flash pattern (Ch40-Ch47) on MPC and compare to normally working CCU. This will
verify CCU and cable connections.
If both Tacho Set A and B reports tacho failure:
- Backup lubrication cables MUST be mounted on affected cylinders.
If all signals on one tacho stay low:
- Check tacho sensor power.
Hint: All sensor signals toggle between zero and high at least once per revolution.
To troubleshoot the problem: Perform tacho test on MOP:
- Navigate to Maintenance -> Function Test screen.
- Perform Tacho tests and follow instruction.

rsn / 2010-03-10 09:00:52

Page 1 of 84

CCUXX
CCUXX_010119

Tacho->Delta Tacho B too big

Description: The two tacho systems are not aligned within allowed tolerance.
Cause: The distance between the tacho marker signals does not correspond to the values set in the ECS
parameters.
Effect: Maximum pressure may vary due to minor mistiming if other events force the ECS to change from
active tacho set (A to input B or vice versa).
Sugg. Action:

CCUXX_010122

This alarm is not valid if "Tacho set A failure" or "Tacho set B failure" is present.
If above alarms are not present:
- Check Pmax. Adjust if required. Normal engine operation can be continued without further action.
- Check or correct adjustment of tacho A & B at next engine overhaul or engine stop. Follow by a PMI
measurement to achieve correct engine Pmax balance.
Tacho->Tacho Alignment Err

Description: One or both tachos are out of adjustment.


Cause: Encoder drive slipping or encoder mount out of adjustment.
Effect: Maximum pressure may vary due to minor mistiming if other events force the ECS to change from
active tacho set (A to input B or vice versa).
Sugg. Action:

CCUXX_010127

This alarm is not valid if "Tacho set A failure" or "Tacho set B failure" is present.
If above alarms are not present:
- Check Pmax. Adjust if required. Normal engine operation can be continued without further action.
- Check or correct adjustment of tacho A & B at next engine overhaul or engine stop. Follow by a PMI
measurement to achieve correct engine Pmax balance.
Tacho->Tacho Input A slip

Description: Tacho A signal is out of alignment compared to Tacho B and flywheel sensor.
Cause: All signals are turning on/off in the correct sequence, but the position of the tacho does not match the
other tacho and the signal from the turning wheel sensor.
Effect: The ECS system will continue operation on the other Tacho System. Note that tacho redundancy is
lost.
Sugg. Action:

CCUXX_010128

This alarm is not valid if "Tacho set A failure" or "Tacho set B failure" is present.
If above alarms are not present:
- Stop engine as soon as possible.
- Inspect encoder mounting.
- Verify correct adjustments on MOP: Maintenance-> Function Test screen (Tacho tests).
Tacho->Tacho Input B slip

Description: Tacho B position signal is wrong.


Cause: All signals are turning on/off in the correct sequence, but the position of the tacho does not match the
other tacho and the signal from the turning wheel sensor.
Effect: The ECS system will continue operation on the other Tacho System. Note that tacho redundancy is
lost.
Sugg. Action:

CCUXX_010129

This alarm is not valid if "Tacho set A failure" or "Tacho set B failure" is present.
If above alarms are not present:
- Stop engine as soon as possible.
- Inspect encoder mounting.
- Verify correct adjustments on MOP: Maintenance-> Function Test screen (Tacho tests).
Tacho->Marker A Input slip

Description: Tacho A Marker Slave signal (flyweel sensor) is out of alignment compared to encoder A and B.
Cause: Marker Slave A signal (flyweel sensor) comes on a crankshaft angle which is different from those
reported by tacho A and tacho B.
Effect: A warning that the marker slave signal from the flyweel sensor is faulty.
Sugg. Action:

This alarm is not valid if "Tacho set A failure" or "Tacho set B failure" are present.
If above alarms are not present:
- Normal engine operation can be continued without further action.
- Check or correct adjustment of flyweel sensor (Marker Slave A) at next engine overhaul or engine
stop.

rsn / 2010-03-10 09:00:52

Page 2 of 84

CCUXX
CCUXX_010135

Tacho set C->Tacho set C failure

Description: Faulty or missing Tacho signals.


Cause: Defect wiring, sensors, encoders or sensor support console.
Effect: The MPC had to change active set of tacho sensors. If both sensor set C and D fail dual tacho function
will be lost.
Sugg. Action:

If all CCUs report tacho failure:


- Fault is most likely found in encoder/trigger ring sensors, amplifier or amplifier related cabling.
- If Tacho A reports the problem: Check flywheel sensor.
If only one CCU reports tacho failure:
- Check diode flash pattern (Ch40-Ch47) on MPC and compare to normally working CCU. This will
verify CCU and cable connections.
If both Tacho Set A and B reports tacho failure:
- Backup lubrication cables MUST be mounted on affected cylinders.
If all signals on one tacho stay low:
- Check tacho sensor power.
Hint: All sensor signals toggle between zero and high at least once per revolution.
To troubleshoot the problem: Perform tacho test on MOP:
- Navigate to Maintenance -> Function Test screen.
- Perform Tacho tests and follow instruction.

CCUXX_010136

Tacho set D->Tacho set D failure

Description: Faulty or missing Tacho signals.


Cause: Defect wiring, sensors, encoders or sensor support console.
Effect: The MPC had to change active set of tacho sensors. If both sensor set C and D fail dual tacho function
will be lost.
Sugg. Action:

If all CCUs report tacho failure:


- Fault is most likely found in encoder/trigger ring sensors, amplifier or amplifier related cabling.
- If Tacho A reports the problem: Check flywheel sensor.
If only one CCU reports tacho failure:
- Check diode flash pattern (Ch40-Ch47) on MPC and compare to normally working CCU. This will
verify CCU and cable connections.
If both Tacho Set A and B reports tacho failure:
- Backup lubrication cables MUST be mounted on affected cylinders.
If all signals on one tacho stay low:
- Check tacho sensor power.
Hint: All sensor signals toggle between zero and high at least once per revolution.
To troubleshoot the problem: Perform tacho test on MOP:
- Navigate to Maintenance -> Function Test screen.
- Perform Tacho tests and follow instruction.

CCUXX_0109A

IO Terminals->Suprv. Ch31,2002-A,Shut Down

Description: Cable failure.


Note that the shutdown signal is routed through the ELFI pilot valve.
The signal from the switch connected to the specified channel is out of range. The cabling and the
connection to the switch are supervised by an 18 kOhm resistor mounted across the switch in the
safety system (Relay in safety system).
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: - No shutdown. ELFI valve will not respond to shut down from safety system.
- If the CCU is controlling 2 cylinders the fuel injection on both cylinders will be stopped when required
as long as it receives correct redundant shut down signal from safety system.
- Note: Stop signals can still be used to stop fuel injection.
Sugg. Action:

- Check cabling and 18 kOhm supervision resistor.


- Check ELFI pilot valve.
- Check MPC input.

rsn / 2010-03-10 09:00:52

Page 3 of 84

CCUXX
CCUXX_0109B

IO Terminals->Shut Down B

Description: Shut down has been ordered from the external safety system.
Cause: See external safety system panel.
Effect: Fuel injections are stopped on cylinders controlled by this CCU.
Sugg. Action:

CCUXX_0109B

The shut down must be reset via the safety system.


To see which cylinders are controlled by a particular CCU: Check Maintenance -> System View I/O
screen.
Shut down can normally be reset by setting active control station handle in stop position.
IO Terminals->Suprv. Ch34,2002-B,Shut Down

Description: Cable failure.


Note that the shutdown signal is routed through the ELFI pilot valve.
The signal from the switch connected to the specified channel is out of range. The cabling and the
connection to the switch are supervised by an 18 kOhm resistor mounted across the switch in the
safety system (Relay in safety system).
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: - No shutdown. ELFI valve will not respond to shut down from safety system.
- If the CCU is controlling 2 cylinders the fuel injection on both cylinders will be stopped when required
as long as it receives correct redundant shut down signal from safety system.
- Note: Stop signals can still be used to stop fuel injection.
Sugg. Action:

CCUXX_0109A

- Check cabling and 18 kOhm supervision resistor.


- Check ELFI pilot valve.
- Check MPC input.
IO Terminals->Shut Down A

Description: Shut down has been ordered from the external safety system.
Cause: See external safety system panel.
Effect: Fuel injections are stopped on cylinders controlled by this CCU.
Sugg. Action:

CCUXX_011228

The shut down must be reset via the safety system.


To see which cylinders are controlled by a particular CCU: Check Maintenance -> System View I/O
screen.
Shut down can normally be reset by setting active control station handle in stop position.
EICU Commands->EICU Failed or No Telegram Received

Description: CCU's receive commands from the EICU at regular intervals. The commands have been missing a
number of times.
Cause: If all CCU's report this alarm
- EICU Failure.
If alarm is released randomly from different CCU's:
- Network failure.
Effect: - Engine remains operative. No load reduction required.
- Both ECR and RCS Control stations are no longer available. Only ESC can be used in this situation.
- Loss of remote control will be displayed on the RCS.
- Set point to and supervision of HPS is lost. The HPS will go to failsafe pressure level (if EIUC power
is lost).
- Connection to alarm system is no longer available. Alarms are still displayed on MOP.
- Cylinder lubrication will be set to fail safe amount and lubrication will be speed proportional.
- Several values on the MOP display will be unavailable.
- HPS Slave pump is started (J80 = OFF) regardless of engine load, untill the alarm condition is
removed.
Sugg. Action:

If all CCU's permanently report this alarm: Check EICU:


- Check that the EICU is in normal mode (green LED on MPC)
- Replace EICU with new MPC.
If CCU's randomly report this alarm:
- Check network status on MOP maintenance screen.
- Check for ground failure.
- Check all network cabling including terminating resistors.
- Check cable diagram for location of resistors.

rsn / 2010-03-10 09:00:53

Page 4 of 84

CCUXX
CCUXX_0116

IO Terminals->Inconsistent Stop Signals

Description: The two redundant Stop signals used by the CCU do not have the same value.
Cause: CCU Hard Wired and CCU from control network have transmitted inconsistent stop signals
Effect: Engine remains operative. No load reduction required.
Effects:
- Stop signals redundancy is lost.
Sugg. Action:

If Engine Running on Fuel:


- All stop sensors must measure a pressure less than 0.5 bar. This can be checked on the MOP:
Maintenance -> System View I/O screen Ch36 (Cable ID = 1101-x, where x=CCU Number).
If Engine Stopped (No Fuel):
- All stop sensors must measure a pressure above 4 bar. This can be checked on the MOP:
Maintenance -> System View I/O screen Ch36 (Cable ID = 1101-x, where x=CCU Number).
- Cut out faulty sensor.
- Replace faulty sensor
- If pressure level is low near sensors: Check pipes and fittings for leaks
Notice redundant stop sensor arrangement:
CCU1, CCU3, CCU5: Redundant STOP from CCU2 Ch36
CCU2, CCU4, CCU6: Redundant STOP from CCU1 Ch36

CCUXX_0304

Cylinder Lubrication->No Cyl. Oil (Tacho) SlowDown Req.

Description: Failure on Tacho A and Tacho B. CCU cannot lubricate affected cylinders
Cause: Failure on Tacho system A and B.
Effect: - No Cylinder lubrication via this CCU.
- Slow down request is ordered.
Sugg. Action:

If the engine has to be operated in spite of this failure condition:


- Backup lubricator cables must be mounted on the affected cylinders. See instruction manual for
details.
If engine can be stopped immediately:
- See tacho alarms for details about how to correct failures.

CCUXX_039020

Alpha Lubricator A->LubeA: Feedback (SlowDownReq)

Description: The actuator piston is not moving as expected.


Cause: - Lubricator pilot valve failure, or
- Activation signal to solinoide missing, or
- Internal lubricator failure, or
- Feedback sensor not working, or
- Hydraulic pressure lost. Valve(s) 560 are closed.
Effect: - Slowdown request is send from ECS.
- No cylinder lubrication on the affected cylinder.
- ECS will keep attempting to activate the injector electrically.
Sugg. Action:

LED in lubricator solinoide plug flashes:


- Check that valve(s) 560 are open.
- Replace lubricator with a spare.
If the problem persists:
- Check cable between lubricator and MPC.
- If cable path OK: Replace MPC.
LED in lubricator solinoide plug don't flash:
- Check cable path from MPC to solinoide plug.
- If cable path OK: Replace MPC

rsn / 2010-03-10 09:00:53

Page 5 of 84

CCUXX
CCUXX_039021

Alpha Lubricator A->LubeA: No Cyl. Oil (SlowDownReq)

Description: Cylinder lubrication no flow sensor reports missing cylinder oil.


Cause: If lubricator actuator piston feedback alarm is present this alarm can be ignored.
Most likely causes:
- Cylinder lubrication oil supply blocked, or
- Sensor malfunction, or
- Electric trace heater off.
Effect: - No cylinder lubrication oil on the affected cylinder.
- Slowdown request is ordered from ECS.
Sugg. Action:

- Check that individual shut off valves are not closed.


- Check cylinder lubrication oil tank level.
- Check that heat tracer is on.
- Disassemble pipes and check if cylinder oil still flows.
If the problem persists:
- Replace lubricator unit.
- Replace lubricator no flow sensor.

CCUXX_0390B

Alpha Lubricator A->LubeA: Flow Sensor (SlowDownReq)

Description: No flow sensor has an illegal value when engine is stopped.


Cause: Sensor is broken.
Effect: Supervision of cylinder lubrication oil supply is no longer provided.
Sugg. Action:
CCUXX_039120

Replace no flow sensor.


Alpha Lubricator B->LubeB: Feedback (SlowDownReq)

Description: The actuator piston is not moving as expected.


Cause: - Lubricator pilot valve failure, or
- Activation signal to solinoide missing, or
- Internal lubricator failure, or
- Feedback sensor not working, or
- Hydraulic pressure lost. Valve(s) 560 are closed.
Effect: - Slowdown request is send from ECS.
- No cylinder lubrication on the affected cylinder.
- ECS will keep attempting to activate the injector electrically.
Sugg. Action:

LED in lubricator solinoide plug flashes:


- Check that valve(s) 560 are open.
- Replace lubricator with a spare.
If the problem persists:
- Check cable between lubricator and MPC.
- If cable path OK: Replace MPC.
LED in lubricator solinoide plug don't flash:
- Check cable path from MPC to solinoide plug.
- If cable path OK: Replace MPC

CCUXX_039121

Alpha Lubricator B->LubeB: No Cyl. Oil (SlowDownReq)

Description: Cylinder lubrication no flow sensor reports missing cylinder oil.


Cause: If lubricator actuator piston feedback alarm is present this alarm can be ignored.
Most likely causes:
- Cylinder lubrication oil supply blocked, or
- Sensor malfunction, or
- Electric trace heater off.
Effect: - No cylinder lubrication oil on the affected cylinder.
- Slowdown request is ordered from ECS.
Sugg. Action:

- Check that individual shut off valves are not closed.


- Check cylinder lubrication oil tank level.
- Check that heat tracer is on.
- Disassemble pipes and check if cylinder oil still flows.
If the problem persists:
- Replace lubricator unit.
- Replace lubricator no flow sensor.

rsn / 2010-03-10 09:00:53

Page 6 of 84

CCUXX
CCUXX_0391B

Alpha Lubricator B->LubeB: Flow Sensor (SlowDownReq)

Description: No flow sensor has an illegal value when engine is stopped.


Cause: Sensor is broken.
Effect: Supervision of cylinder lubrication oil supply is no longer provided.
Sugg. Action:
CCUXX_040138

Replace no flow sensor.


Speed Controller->Cyl. A Running on Backup Telegram

Description: The Governor is calculating a Fuel Index based on a backup telegram. This will occur in case of CCU
failure.
Cause: The CCU which should send the primary telegram is not on the control network or has stopped
running, or
Control Network problems caused prolonged transfer times.
Effect: No immediate effect, but Mean Indicated Pressure may drift on affected cylinder.
Sugg. Action:

- Measure Mean Indicated Pressure using a PMI system to ensure that the cylinders are balanced. If
necessary, adjust mean indicated pressure on MOP.
- Check that all CCUs are running and on the control network. Look for related alarms on MOP.
If the alarm persists during normal running note Engine RPM and direction and contact MAN Diesel
when convenient

CCUXX_040139

Speed Controller->Cyl. B Running on Backup Telegram

Description: The Governor is calculating a Fuel Index based on a backup telegram. This will occur in case of CCU
failure.
Cause: The CCU which should send the primary telegram is not on the control network or has stopped
running, or
Control Network problems caused prolonged transfer times.
Effect: No immediate effect, but Mean Indicated Pressure may drift on affected cylinder.
Sugg. Action:

- Measure Mean Indicated Pressure using a PMI system to ensure that the cylinders are balanced. If
necessary, adjust mean indicated pressure on MOP.
- Check that all CCUs are running and on the control network. Look for related alarms on MOP.
If the alarm persists during normal running note Engine RPM and direction and contact MAN Diesel
when convenient

CCUXX_040207

Hydraulic Supply Pressure Limiter->Low Hydraulic Pressure

Description: The hydraulic supply pressure has dropped. To compensate for insufficient pump flow maximum
allowed fuel index is reduced. Fuel index reduction leads to lower hydraulic oil consumption.
Cause: - Hydraulic supply Pump failure, or
- Hydraulic leakage or failing bypass valves in the hydraulic supply system, or
- One or more hydraulic supply pumps stopped.
Effect: Engine load might be reduced and engine might run with unstable speed and fuel index.
- If the pressure drops below a predefined level fuel injection is stopped.
Sugg. Action:

While locating the failure that causes the pressure drop: Reduce engine load to avoid unstable
running.
- Check for hydraulic pump related alarms.
- Check for hydraulic leakages, pressure relief valve and failing bypass valves. Typically a failing
bypass valve increases significantly in temperature.
Engine Stopped:
- Cut out individual HCU's to determine the location of the leakage.
- Check the hydraulic pressure decay times on Auxiliaries -> Hydraulic System screen. Compare to
reference.

rsn / 2010-03-10 09:00:53

Page 7 of 84

CCUXX
CCUXX_0432

Governor->STOP Low While Engine Not Running

Description: Pneumatic STOP signals are off while the engine is stopped.
STOP signals are measured by one pressure sensor on each CCU.
The pressure sensors are activated by control air supply and connected to CCUs Channel 36.
Cause: - Loss of control air pressure, or
- Engine stopped unexpectedly.
Effect: If a start attempt is made while this alarm is present air and fuel may be applied simultaneously. This
might damage the starting air bursting cap. Avoid Engine start.
Sugg. Action:

On the Maintenance -> System View I/O screen: Compare pressure measurements on all CCUs
(channel 36).
STOP is on when pressure is above approximately 2 bar.
If only one CCU reports this failure:
- Check for pipe leakages near pressure sensor.
- Check pressure sensor.
If all CCUs reports this failure:
- Check control air supply pressure according to instruction manual.
- Check double non return valve at engine side. This valve is located in Engine Side Console.
- Check for leakages in the control air system.
If engine stopped unexpectedly: Move handle to stop position to clear the alarm.

CCUXX_060106

ELFI Valve A->ELFIA Feedback Failure

Description: The position feedback on the specific injection controlling valve has shown movements that are not
physically realistic.
Cause: Typically loose connection in cabling. Malfunction of internal ELF-feedback electronics can cause out
of range feedback signals.
Effect: When the fault is detected injections are stopped until valve is reactivated via the Engine -> Chief
Limiters MOP screen.
This alarm is a trigger member for the HCU Events screen (Maintaince->TroubleShooting). A log of the
incident has been recorded and can be used to further analyse the alarm.
Sugg. Action:

Fuel injection is reactivated by toggling invalidation of CCU channel 30 (Maintenance -> System View
I/O screen), re-enabling fuel injection on the Engine -> Chief Limiters screen, or CCU power off/on.
Before doing any of the above check the following due to danger of Cover Lift:
- Check that Maintenance -> System View I/O -> CCUx-Ch30 -> Electrical Value never is out of range
(3.5-20.5 mA)
- Inspect entire cabling from CCU to ELFI Valve.
- If cabling is OK and reactivation does not solve the problem: Replace CCU,
- If CCU replacement does not solve the problem: Replace ELFI Valve and reactivate as described.
During reactivation: Try to feel the dither on the valve (pressure must be sufficiently high, above
approx. 180 bar.

CCUXX_060114

ELFI Valve A->ELFIA Illegal Position

Description: The ELFI spool position has moved to unexpected position during the no injection period of the
crankshaft revolution.
Cause: ELFI Valve did not return to specified position in due time because:
- Dirty oil causes valve to stick to fuel port side.
- Parker Valve failure.
- MPC malfunction.
Effect: ELFI Control is stopped and causes fuel injection stop.
This alarm is a trigger member for the HCU Events screen (Maintaince->TroubleShooting). A log of the
incident has been recorded and can be used to further analyse the alarm.
Sugg. Action:

Fuel injection is reactivated by toggling invalidation of CCU channel 30 (Maintenance -> System View
I/O screen), re-enabling fuel injection on the Engine -> Chief Limiters screen, or CCU power off/on.
Before doing any of the above check the following due to danger of Cover Lift:
- Check that Maintenance -> System View I/O -> CCUx-Ch30 -> Electrical Value never is out of range
(3.5-20.5 mA)
- Inspect entire cabling from CCU to ELFI Valve.
- If cabling is OK and reactivation does not solve the problem: Replace CCU,
- If CCU replacement does not solve the problem: Replace ELFI Valve and reactivate as described.
During reactivation: Try to feel the dither on the valve (pressure must be sufficiently high, above
approx. 180 bar.

rsn / 2010-03-10 09:00:53

Page 8 of 84

CCUXX
CCUXX_060115

ELFI Valve A->ELFIA Illegal Set Point

Description: The internal position set point to the ELFI Valve has an unexpected value during the no injection
period of the crankshaft revolution.
Cause: Internal errors on MPC
Effect: ELFI Control is stopped and causes fuel injection stop.
This alarm is a trigger member for the HCU Events screen (Maintaince->TroubleShooting). A log of the
incident has been recorded and can be used to further analyse the alarm.
Sugg. Action:

CCUXX_060206

- Contact B&W. Inform Speed, Active Eng Mode, Approximate Load and manoeuvring condition.
- If the alarm appears during normal running: Replace the MPC.
- Fuel-injection is reactivated by MPC power off/on (Reset MPC).
ELFI Valve B->ELFIB Feedback Failure

Description: The position feedback on the specific injection controlling valve has shown movements that are not
physically realistic.
Cause: Typically loose connection in cabling. Malfunction of internal ELF-feedback electronics can cause out
of range feedback signals.
Effect: When the fault is detected injections are stopped until valve is reactivated via the Engine -> Chief
Limiters MOP screen.
This alarm is a trigger member for the HCU Events screen (Maintaince->TroubleShooting). A log of the
incident has been recorded and can be used to further analyse the alarm.
Sugg. Action:

Fuel injection is reactivated by toggling invalidation of CCU channel 33 (Maintenance -> System View
I/O screen), re-enabling fuel injection on the Engine -> Chief Limiters screen, or CCU power off/on.
Before doing any of the above check the following due to danger of Cover Lift:
- Check that Maintenance -> System View -> CCUx-Ch33-> Electrical Value never is out of range (3.520.5 mA)
- Inspect entire cabling from CCU to ELFI Valve.
- If cabling is OK and reactivation does not solve the problem: Replace CCU,
- If CCU replacement does not solve the problem: Replace ELFI Valve and reactivate as described.
During reactivation: Feel the dither on the valve (pressure must be sufficiently high, above approx. 180
bar.

CCUXX_060214

ELFI Valve B->ELFIB Illegal Position

Description: The ELFI spool position has moved to unexpected position during the no injection period of the
crankshaft revolution.
Cause: ELFI Valve did not return to specified position in due time because:
- Dirty oil causes valve to stick to fuel port side.
- Parker Valve failure.
- MPC malfunction.
Effect: ELFI Control is stopped and causes fuel injection stop.
This alarm is a trigger member for the HCU Events screen (Maintaince->TroubleShooting). A log of the
incident has been recorded and can be used to further analyse the alarm.
Sugg. Action:

Fuel injection is reactivated by toggling invalidation of CCU channel 33 (Maintenance -> System View
I/O screen), re-enabling fuel injection on the Engine -> Chief Limiters screen, or CCU power off/on.
Before doing any of the above check the following due to danger of Cover Lift:
- Check that Maintenance -> System View -> CCUx-Ch33-> Electrical Value never is out of range (3.520.5 mA)
- Inspect entire cabling from CCU to ELFI Valve.
- If cabling is OK and reactivation does not solve the problem: Replace CCU,
- If CCU replacement does not solve the problem: Replace ELFI Valve and reactivate as described.
During reactivation: Feel the dither on the valve (pressure must be sufficiently high, above approx. 180
bar.

CCUXX_060215

ELFI Valve B->ELFIB Illegal Set Point

Description: The internal position set point to the ELFI Valve has an unexpected value during the no injection
period of the crankshaft revolution.
Cause: Internal errors on MPC
Effect: ELFI Control is stopped and causes fuel injection stop.
This alarm is a trigger member for the HCU Events screen (Maintaince->TroubleShooting). A log of the
incident has been recorded and can be used to further analyse the alarm.
Sugg. Action:

- Contact B&W. Inform Speed, Active Eng Mode, Approximate Load and manoeuvring condition.
- If the alarm appears during normal running: Replace the MPC.
- Fuel-injection is reactivated by MPC power off/on (Reset MPC).

rsn / 2010-03-10 09:00:53

Page 9 of 84

CCUXX
CCUXX_060315

Injection Profile 1->Max. Time in Pos. Table Reached

Description: Fuel index ordered has resulted in an ELFI close time that is not supported for the current injection
profile.
Cause: - Engine running excessively heavy.
- Fuel quality is poor
- Profile shaping causing very long delays.
Effect: Maximum time in position table for current injection profile is used. This means that regardless of how
much Fuel index is increased Fuel amount into cylinders does not increase.
Sugg. Action:

CCUXX_060415

Contact MAN B&W for the following adjustments:


- Increase maximum time in position table
- Injection Profile is too 'weak'. Make injection profile more aggressive.
- Freeze times are too long resulting in large close times.
Injection Profile 2->Max. Time in Pos. Table Reached

Description: Fuel index ordered has resulted in an ELFI close time that is not supported for the current injection
profile.
Cause: - Engine running excessively heavy.
- Fuel quality is poor
- Profile shaping causing very long delays.
Effect: Maximum time in position table for current injection profile is used. This means that regardless of how
much Fuel index is increased Fuel amount into cylinders does not increase.
Sugg. Action:

CCUXX_060701

Contact MAN B&W for the following adjustments:


- Increase maximum time in position table
- Injection Profile is too 'weak'. Make injection profile more aggressive.
- Freeze times are too long resulting in large close times.
Shadow Injection Supervision->ELFIA/B Injections Too Close

Description: Some cylinders controlled by the same CCU have to inject fuel very close to each other. The
predefined limits has been exceeded.
Cause: Longer injection Periods can have increased due to:
- Very long Freeze periods.
- Fuel quality is poor.
- Injection Profile too 'weak'.
Effect: Typically there is no noticeable effect but previous injections may be affected by new injections.
Sugg. Action:

CCUXX_060702

Contact MAN B&W for the following adjustments:


- Decrease injection delay time
- Recable CCU's having two activations right after each other can be moved to other CCU's.
- Measure if disturbance has any noticeable affect and If not: Disable alarm.
PSP Too Late Supervision->Too Late PSP Setup

Description: Internal ECS fault situation. An internal calculation was completed too late.
Cause: Very uncertain. A partly failing network can cause significantly increased CPU load on the MPCs
leading to unacceptable delays on some calculations.
Effect: Difficult to predict. Often no effect, in other situations unstable operation of fuel injection and lubrication
on some cylinders.
Sugg. Action:

Contact MAN B&W. Parameter adjustment may be required.


In the meantime: Monitor exhaust gas temperature:
- If temperature OK: Continue running.
- If temperature not OK: Shut off that cylinder and continue with reduced load and speed.

rsn / 2010-03-10 09:00:53

Page 10 of 84

CCUXX
CCUXX_060703

ELFIA Feedback Supervision->ELFIA Fault:Main Spool at Drain Pos

Description: ELFI main spool is at Tank position when it should not be.
Cause: Can occur if:
- Loose connection on ELFI pilot valve set point.
- Mechanically stuck ELFI pilot valve.
- ELFI Main Spool is stuck at tank position.
- ELFI pilot valve recieves a Shut Down but CCU does not.
- CCU Ch70 (ELFIA) or Ch71 (ELFIB) always has an output less than 12 mA.
Effect: Injection will not occur as long as this situation is present. However injection will automatically start
again when cause of alarm is removed.
Sugg. Action:

Check the following:


- Ch 70 Parker pilot Valve cabeling (Cable ID = 4107-A).
- Ch30 ELFI Spool position is reading out valid mA.
- Check if the ELFI main spool can be moved hydraulically
- Dithering on the ELFI Valve when pressure is sufficiently high to move ELFI Main Spool (make sure
pressure is above 180 bar).
ELFI Valve Test Procedure: (FUEL INJECTION CAN OCCUR)
- Engine stopped
- Hydraulic pressure must be sufficiently high to move ELFI Main Spool.
- Go to MOP: Maintenance -> System View I/O screen.
- Set MPC that reports the problem in test mode.
- Set Ch70 to 20 mA.
- ELFI Main Spool must go to Injection side.
- Set Ch70 to 4 mA.
- ELFI Main Spool must go to Tank position.
If nothing is wrong with the cables try to replace:
- Parker pilot Valve.
- CCU reporting the problem.
- ELFI Valve on affected Cylinder.

CCUXX_060703

ELFIA Feedback Supervision->ELFIA Fault:Main Spool at Inj. Pos.

Description: ELFI main spool is at Injection position when it should not be.
Cause: Can occur if:
- Mechanically stuck ELFI pilot valve.
- ELFI Main Spool is stuck at Injection position.
- CCU Ch70 (ELFIA) or Ch71 (ELFIB) always has an output more than 12 mA.
Effect: Injection will not occur as long as this situation is present. However injection will automatically start
again when cause of alarm is removed.
Sugg. Action:

Check the following:


- Ch 70 Parker pilot Valve cabeling (Cable ID = 4107-A).
- Ch30 ELFI Spool position is reading out valid mA.
- Dithering on the ELFI Valve when pressure is sufficiently high to move ELFI Main Spool (make sure
pressure is above 180 bar).
- Check if the ELFI main spool can be moved when hydraulic pressure is low. If this is the case the
ELFI main spool is NOT Stuck.
ELFI Valve Test Procedure: (FUEL INJECTION CAN OCCUR)
- Engine stopped
- Hydraulic pressure must be sufficiently high to move ELFI Main Spool.
- Go to MOP: Maintenance -> System View I/O screen.
- Set MPC that reports the problem in test mode.
- Set Ch70 to 20 mA.
- ELFI Main Spool must go to Injection side.
- Set Ch70 to 4 mA.
- ELFI Main Spool must go to Tank position.
If nothing is wrong with the cables try to replace:
- Parker pilot Valve.
- CCU reporting the problem.
- ELFI Valve on affected Cylinder.

rsn / 2010-03-10 09:00:53

Page 11 of 84

CCUXX
CCUXX_060703

ELFIA Feedback Supervision->ELFIA Integrator Saturation

Description: The ELFI controller integrator has compensated more than allowed.
Cause: Can occur if:
- Loose connection on ELFI pilot valve set point.
- Mechanically stuck ELFI pilot valve.
- ELFI Main Spool is stuck at tank or Injection position.
- ELFI pilot valve recieves a Shut Down but CCU does not.
- CCU Ch70 (ELFIA) or Ch71 (ELFIB) always has an output more than 12 mA or always less than 12
mA.
Effect: ELFI Controller on CCU can no longer compensate completely for position errors. This will most likely
affect mean pressure.
Sugg. Action:

Most likely the Parker Pilot valve is not calibrated precisely to compensate for zero overlap differences.
Check the following:
- Ch 70 Parker pilot Valve cabeling (Cable ID = 4107-A).
- Ch30 ELFI Spool position is reading out valid mA.
- Check that the parker pilot Valve is not stuck or sticking
- Check if the ELFI main spool can be moved hydraulically.
- Testing the pilot valve and ELFI Valve can be checked using Engine stopped procedure, feeling
dithering movement when pressure is above approx. 180 bar.

If nothing is wrong with the cables try to replace:


- Parker pilot Valve.
- CCU reporting the problem.
- ELFI Valve on affected Cylinder.
CCUXX_060704

ELFIB Feedback Supervision->ELFIB Fault:Main Spool at Drain Pos

Description: ELFI main spool is at Tank position when it should not be.
Cause: Can occur if:
- Loose connection on ELFI pilot valve set point.
- Mechanically stuck ELFI pilot valve.
- ELFI Main Spool is stuck at tank position.
- ELFI pilot valve recieves a Shut Down but CCU does not.
- CCU Ch70 (ELFIA) or Ch71 (ELFIB) always has an output less than 12 mA.
Effect: Injection will not occur as long as this situation is present. However injection will automatically start
again when cause of alarm is removed.
Sugg. Action:

Check the following:


- Ch 71 Parker pilot Valve cabeling (Cable ID = 4107-B).
- Ch33 ELFI Spool position is reading out valid mA.
- Check if the ELFI main spool can be moved hydraulically
- Dithering on the ELFI Valve when pressure is sufficiently high to move ELFI Main Spool (make sure
pressure is above 180 bar).
ELFI Valve Test Procedure: (FUEL INJECTION CAN OCCUR)
- Engine stopped
- Hydraulic pressure must be sufficiently high to move ELFI Main Spool.
- Go to MOP: Maintenance -> System View I/O screen.
- Set MPC that reports the problem in test mode.
- Set Ch71 to 20 mA.
- ELFI Main Spool must go to Injection side.
- Set Ch71 to 4 mA.
- ELFI Main Spool must go to Tank position.
If nothing is wrong with the cables try to replace:
- Parker pilot Valve.
- CCU reporting the problem.
- ELFI Valve on affected Cylinder.

rsn / 2010-03-10 09:00:53

Page 12 of 84

CCUXX
CCUXX_060704

ELFIB Feedback Supervision->ELFIB Fault:Main Spool at Inj. Pos.

Description: ELFI main spool is at Injection position when it should not be.
Cause: Can occur if:
- Mechanically stuck ELFI pilot valve.
- ELFI Main Spool is stuck at Injection position.
- CCU Ch70 (ELFIA) or Ch71 (ELFIB) always has an output more than 12 mA.
Effect: Injection will not occur as long as this situation is present. However injection will automatically start
again when cause of alarm is removed.
Sugg. Action:

Check the following:


- Ch 71 Parker pilot Valve cabeling (Cable ID = 4107-B).
- Ch33 ELFI Spool position is reading out valid mA.
- Dithering on the ELFI Valve when pressure is sufficiently high to move ELFI Main Spool (make sure
pressure is above 180 bar).
- Check if the ELFI main spool moves to tank position when hydraulic pressure is lowered. If this is the
case the ELFI main spool is NOT Stuck.
ELFI Valve Test Procedure: (FUEL INJECTION CAN OCCUR)
- Engine stopped
- Hydraulic pressure must be sufficiently high to move ELFI Main Spool.
- Go to MOP: Maintenance -> System View I/O screen.
- Set MPC that reports the problem in test mode.
- Set Ch71 to 20 mA.
- ELFI Main Spool must go to Injection side.
- Set Ch71 to 4 mA.
- ELFI Main Spool must go to Tank position.
If nothing is wrong with the cables try to replace:
- Parker pilot Valve.
- CCU reporting the problem.
- ELFI Valve on affected Cylinder.

CCUXX_060704

ELFIB Feedback Supervision->ELFIB Integrator Saturation

Description: The ELFI controller integrator has compensated more than allowed.
Cause: Can occur if:
- Loose connection on ELFI pilot valve set point.
- Mechanically stuck ELFI pilot valve.
- ELFI Main Spool is stuck at tank or Injection position.
- ELFI pilot valve recieves a Shut Down but CCU does not.
- CCU Ch70 (ELFIA) or Ch71 (ELFIB) always has an output more than 12 mA or always less than 12
mA.
Effect: ELFI Controller on CCU can no longer compensate completely for position errors. This will most likely
affect mean pressure.
Sugg. Action:

Most likely the Parker Pilot valve is not calibrated precisely enough to compensate for zero overlap
differences or wear in service..
Check the following:
- Ch 71 Parker pilot Valve cabeling (Cable ID = 4107-B).
- Ch33 ELFI Spool position is reading out valid mA.
- Check that the parker pilot Valve is not stuck or sticking.
- Check if the ELFI main spool can be moved hydraulically.
- Testing the pilot valve and ELFI Valve can be checked using Engine stopped procedure, feeling
dithering movement when pressure is above approx. 180 bar.
If nothing is wrong with the cables try to replace:
- Parker pilot Valve.
- CCU reporting the problem.
- ELFI Valve on affected Cylinder.

CCUXX_0623

Fuel Injection->Test Profile Active on Cylinder A

Description: Test Profile active on Cylinder A.


Cause: The parameter for activating the test profile is enabled.
Effect: Engine running mode output is still used based on the active selection on MOP. However test profile is
used instead injection profile normally used for current engine running mode.
Sugg. Action:

When test of injection profile is finished set parameter for test profile to off.

rsn / 2010-03-10 09:00:53

Page 13 of 84

CCUXX
CCUXX_0624

Fuel Injection->Test Profile Active on Cylinder B

Description: Test Profile active on Cylinder B.


Cause: The parameter for activating the test profile is enabled.
Effect: Engine running mode output is still used based on the active selection on MOP. However test profile is
used instead injection profile normally used for current engine running mode.
Sugg. Action:
CCUXX_062515

When test of injection profile is finished set parameter for test profile to off.
Injection Profile For TEST ONLY->Max. Time in Pos. Table Reached

Description: Fuel index ordered has resulted in an ELFI close time that is not supported for the current injection
profile.
Cause: - Engine running excessively heavy.
- Fuel quality is poor
- Profile shaping causing very long delays.
Effect: Maximum time in position table for current injection profile is used. This means that regardless of how
much Fuel index is increased Fuel amount into cylinders does not increase.
Sugg. Action:

CCUXX_0901

Contact MAN B&W for the following adjustments:


- Increase maximum time in position table
- Injection Profile is too 'weak'. Make injection profile more aggressive.
- Freeze times are too long resulting in large close times.
EngineSide/Remote Control Selection->Inconsistent Control Stat. Request

Description: The Control Station Switch Logic has detected inconsistent control signal requests. Cabling seem to
be ok but values are inconsistent.
Cause: The control station switch logic expected a high/low combination of the control station request signals.
One of two events has occurred:
- Local Control Request and Remote Control Request both low.
- Local Control Request and Remote Control Request both high.
Effect: The ECS retains its manoeuvre place.
Sugg. Action:

CCUXX_1101-x

- Check Ch23 CCU1 (Cable ID = 1118 for Local Control).


- Check Ch23 CCU2 (Cable ID = 1130 for Remote Control).
- Check Pressure Switches to see if sensors are stuck High or Low. Replace faulty switch or cut out
faulty sensor.
- If everything is OK: Replace CCU1 or CCU2.
Ch36,1101-x,STOP (No Fuel) (bar)->Suprv. Ch36,1101-x,STOP (No Fuel) (

Description: Invalid input, so MPC uses the last valid value.


Cause: Wire break.
Effect: Stop signals are evaluated in pairs. This signal is no longer included in the evaluation of Stop Signal
state. ECS uses valid redundant sensor instead via network.
Sugg. Action:

CCUXX_1118-0

- Check cable from CCU Ch36 to stop sensor.


- Replace stop signal sensor.
- Replace MPC.
Ch23,1118-,Engine Side Control Acti->Suprv. Ch23,1118-,Engine Side Contr

Description: Channel input is out of range.


Cause: Channel input is out of range.
Effect: Local control station can not be selected by using normal change over procedure.
If active control station is Local control station is locked in last.
Sugg. Action:

- Check cable from CCU1 Ch23 to Sensor (Cable ID = 1118).


- Verify that cable is ok and supervision resistor is mounted with 6k8 Ohm.
- If Local Control Station needs to be selected: Pull out Ch23 on CCU2 to force control to ESC.
- Verify speedset before changeover.

rsn / 2010-03-10 09:00:53

Page 14 of 84

CCUXX
CCUXX_1130-0

Ch23,1130-,Remote Control Active->Suprv. Ch23,1130-,Remote Control Ac

Description: The signal from the switch connected to the specified channel is out of legal range. The cabling and
the connection to the switch are supervised by a 6.8kOhm resistor mounted across the switch.
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: Lock in last of latest valid value.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

CCUXX_2002-A

Ch31,2002-A,Shut Down A->Suprv. Ch31,2002-A,Shut Down A

Description: Cable failure.


Note that the shutdown signal is routed through the ELFI pilot valve.
The signal from the switch connected to the specified channel is out of range. The cabling and the
connection to the switch are supervised by an 18 kOhm resistor mounted across the switch in the
safety system (Relay in safety system).
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: Shut Down is no longer evaluated on the CCU that reported the supervision failure.
Sugg. Action:

CCUXX_2002-B

Check the Following:


- The cabling and the resistor of the switch.
- Check the current into terminal "C" of the channel. It must be within 0.3 mA and 35 mA. If it is while
the alarm is present, the MPC may be damaged and must be replaced.
Ch34,2002-B,Shut Down B->Suprv. Ch34,2002-B,Shut Down B

Description: Cable failure.


Note that the shutdown signal is routed through the ELFI pilot valve.
The signal from the switch connected to the specified channel is out of range. The cabling and the
connection to the switch are supervised by an 18 kOhm resistor mounted across the switch in the
safety system (Relay in safety system).
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: Shut Down is no longer evaluated on the CCU that reported the supervision failure.
Sugg. Action:

CCUXX_215004

Check the Following:


- The cabling and the resistor of the switch.
- Check the current into terminal "C" of the channel. It must be within 0.3 mA and 35 mA. If it is while
the alarm is present, the MPC may be damaged and must be replaced.
Ch20,2150,Engine Side Speed Set->Suprv. Ch20,2150,Engine Side Speed

Description: Invalid input, so MPC uses the last valid value.


Cause: Channel input is out of range.
Effect: The input value is fixed to last valid input and ESC is not possible.
Sugg. Action:

- Check ESC speed handle cable to CCU1 (Ch20).


- If active control station is ESC: Change control station.

rsn / 2010-03-10 09:00:53

Page 15 of 84

CCUXX
CCUXX_215204

Ch22,2152,Engine Side Increase Limi->Suprv. Ch22,2152,Engine Side Increa

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: The input value is fixed to last valid input and cannot be changed.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

CCUXX_215604

Ch20,2156,Engine Side Speed Increas->Suprv. Ch20,2156,Engine Side Speed

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: The input value is fixed to last valid input and ESC is not possible.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

CCUXX_215704

Ch21,2157,Engine Side Speed Decreas->Suprv. Ch21,2157,Engine Side Speed

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: The input value is fixed to last valid input and may affect the engine running.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

CCUXX_4102-A

Ch30,4102-A,ELFI A Spool Position->Suprv. Ch30,4102-A,ELFI A Spool Pos

Description: The signal from the sensor connected to the specified channel is out of range. The sensor should give
a signal between 4 mA to 20 mA.
Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: Valve control is stopped, causing no injections to the cylinder.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

rsn / 2010-03-10 09:00:53

Page 16 of 84

CCUXX
CCUXX_4102-B

Ch33,4102-B,ELFI B Spool Position->Suprv. Ch33,4102-B,ELFI B Spool Pos

Description: The signal from the sensor connected to the specified channel is out of range. The sensor should give
a signal between 4 mA to 20 mA.
Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: Valve control is stopped, causing no injections to the cylinder.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

CCUXX_8283-A

Ch26,8283-A,Lub. A Flow Missing->Suprv. Ch26,8283-A,Lub. A Flow Miss

Description: The signal from the switch connected to the specified channel is out of legal range. The cabling and
the connection to the switch are supervised by a 6.8kOhm resistor mounted across the switch.
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: Supervision of cylinder lubrication oil supply is no longer provided.
Sugg. Action:

CCUXX_8283-B

- Check the cabling and the resistor of the switch.


- Check the voltage between terminal B and C on the MPC plug. It must be above 1.6 Vdc.
If the signal is ok while the alarm is present, the MPC may be damaged and must be replaced.
Ch27,8283-B,Lub. B Flow Missing->Suprv. Ch27,8283-B,Lub. B Flow Miss

Description: The signal from the switch connected to the specified channel is out of legal range. The cabling and
the connection to the switch are supervised by a 6.8kOhm resistor mounted across the switch.
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: Supervision of cylinder lubrication oil supply is no longer provided.
Sugg. Action:

CCUXX_8285-A

- Check the cabling and the resistor of the switch.


- Check the voltage between terminal B and C on the MPC plug. It must be above 1.6 Vdc.
If the signal is ok while the alarm is present, the MPC may be damaged and must be replaced.
Ch26,8285-A,Lube A Oil Supply Missi->Suprv. Ch26,8285-A,Lube A Oil Suppl

Description: The signal from the switch connected to the specified channel is out of legal range. The cabling and
the connection to the switch are supervised by a 6.8kOhm resistor mounted across the switch.
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: Supervision of cylinder lubrication oil supply is no longer provided.
Sugg. Action:

CCUXX_8285-B

- Check the cabling and the resistor of the switch.


- Check the voltage between terminal B and C on the MPC plug. It must be above 1.6 Vdc.
If the signal is ok while the alarm is present, the MPC may be damaged and must be replaced.
Ch27,8285-B,Lube B Oil Supply Missi->Suprv. Ch27,8285-B,Lube B Oil Suppl

Description: The signal from the switch connected to the specified channel is out of legal range. The cabling and
the connection to the switch are supervised by a 6.8kOhm resistor mounted across the switch.
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: Supervision of cylinder lubrication oil supply is no longer provided.
Sugg. Action:

- Check the cabling and the resistor of the switch.


- Check the voltage between terminal B and C on the MPC plug. It must be above 1.6 Vdc.
If the signal is ok while the alarm is present, the MPC may be damaged and must be replaced.

rsn / 2010-03-10 09:00:53

Page 17 of 84

CCUXX
CCUXX_860104

Ch24,8601,Scavenge Air Pressure->Suprv. Ch24,8601,Scavenge Air Press

Description: The signal from the sensor connected to the specified channel is out of range. The sensor should give
a signal between 4 mA to 20 mA.
Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: Scavenge air pressure signal is no longer available.
- Fuel injection timing is now based on a predefined angle.
Sugg. Action:
CCUXX_9980-A

Use PMI equipment to verify compression and maximum pressure while running on fixed angle.
Ch26,9980-A,Lub. A Flow Missing->Suprv. Ch26,9980-A,Lub. A Flow Miss

Description: The signal from the switch connected to the specified channel is out of legal range. The cabling and
the connection to the switch are supervised by a 6.8kOhm resistor mounted across the switch.
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: Supervision of cylinder lubrication oil supply is no longer provided.
Sugg. Action:

CCUXX_9980-B

- Check the cabling and the resistor of the switch.


- Check the voltage between terminal B and C on the MPC plug. It must be above 1.6 Vdc.
If the signal is ok while the alarm is present, the MPC may be damaged and must be replaced.
Ch27,9980-B,Lub. B Flow Missing->Suprv. Ch27,9980-B,Lub. B Flow Miss

Description: The signal from the switch connected to the specified channel is out of legal range. The cabling and
the connection to the switch are supervised by a 6.8kOhm resistor mounted across the switch.
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: Supervision of cylinder lubrication oil supply is no longer provided.
Sugg. Action:

CCUXX_9990-A

- Check the cabling and the resistor of the switch.


- Check the voltage between terminal B and C on the MPC plug. It must be above 1.6 Vdc.
If the signal is ok while the alarm is present, the MPC may be damaged and must be replaced.
Ch26,9990-A,Lube A Oil Supply Missi->Suprv. Ch26,9990-A,Lube A Oil Suppl

Description: The signal from the switch connected to the specified channel is out of legal range. The cabling and
the connection to the switch are supervised by a 6.8kOhm resistor mounted across the switch.
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: Supervision of cylinder lubrication oil supply is no longer provided.
Sugg. Action:

CCUXX_9990-B

- Check the cabling and the resistor of the switch.


- Check the voltage between terminal B and C on the MPC plug. It must be above 1.6 Vdc.
If the signal is ok while the alarm is present, the MPC may be damaged and must be replaced.
Ch27,9990-B,Lube B Oil Supply Missi->Suprv. Ch27,9990-B,Lube B Oil Suppl

Description: The signal from the switch connected to the specified channel is out of legal range. The cabling and
the connection to the switch are supervised by a 6.8kOhm resistor mounted across the switch.
Cause: - Failure in the cabling to the switch, or
- Missing supervision resistor across the switch, or
- MPC input failure
Effect: Supervision of cylinder lubrication oil supply is no longer provided.
Sugg. Action:

CCUXX_badBa

- Check the cabling and the resistor of the switch.


- Check the voltage between terminal B and C on the MPC plug. It must be above 1.6 Vdc.
If the signal is ok while the alarm is present, the MPC may be damaged and must be replaced.
System->Non standard baud rate

Description: Baud rate for service terminal is not 9600 Bd.


Cause: Non standard rate selected.
Effect: No, or unreadable output to service terminal.
Sugg. Action:

Reset blue DIP, and reboot MPC when appropriate.

rsn / 2010-03-10 09:00:53

Page 18 of 84

CCUXX
CCUXX_IDKEY

System->ID Key corrupt

Description: At system in operation an ongoing ID-key test is made.


The alarm is set when a read byte in the ID-key is not equal to the corresponding value saved in the
CPU-RAM.
The alarm is reset as soon a read byte in the ID-key is equal to the corresponding value saved in the
CPU-RAM.
I. e. a problem also exists with the ID-key when the alarm are not set while it has not been
acknowledged.
One byte is tested for each second. If the alarm does not reappear in a test cycle of 256 seconds, the
fail on the ID-key is not steady.
Cause: The ID-key is defect, is not plugged correct or is missing.
Effect: No operational effect until the next restart.
If the ID-key is plugged correct, the persistent data is lost.
Sugg. Action:

CCUXX_SBAT

Ensure the ID-key is plugged correct in the system.


If plugged correctly and a system restart fails because of problems with the ID-key, replace the ID-key
with a new.
System->Battery Level Low

Description: MPC battery level low.


Cause: Battery discharged.
Effect: If MPC remains switched on, there is no effect. If the MPC is switched off or power is lost, the MPC will
loose its time settings. Time settings will be automatically retrieved at next power on.
Sugg. Action:

CCUXX_SFuse

At next engine stop:


1) Remove power supply on MPC.
2) Replace battery.
3) Reconnect power supply.
24V power supervision->Fuse F12 failure

Description: Fuse 12 is blown. Fuse 12 protects the sensor power supply, terminal "D", of the analogue inputs,
channels 20 to 37, of the MPC.
Cause: Electrical overload or wear of the fuse.
Effect: A number of the sensors and signals connected to channels 20 to 37 may give wrong values, and a
number of supervision alarms may occur simultaneously.
Sugg. Action:
CCUXX_SFuse

Check for failures in the external cabling to channels 20 to 37. Replace the fuse.
24V power supervision->Fuse F13 failure

Description: Fuse 13 is blown. Fuse 13 protects the power outlets of:


channels 40 to 47, terminal "D",
channels 48 to 53, terminal "E",
channels 60 and 61, terminal "H".
Cause: Electrical overload or wear of the fuse.
Effect: A number of the signals related to channels 40 to 61 may be wrong. Effect on engine behaviour is
unknown.
Sugg. Action:
CCUXX_SFuse

Check for possible failures in the external cabling to channels 40 to 61. Replace the fuse.
24V power supervision->Fuse F14 failure

Description: Fuse 14 is blown. Fuse 14 protects the power supply for the analog output, channels 70 and 71, of the
MPC.
Cause: Electrical overload or wear of the fuse.
Effect: Injections will not occur on cylinders controlled by this MPC.
Sugg. Action:

CCUXX_SFuse

Check for failures in the external cabling to channels 70 and 71. Replace the fuse. If the fuse blows
again: Replaced the MPC.
24V power supervision->Fuse F9 failure

Description: Fuse 9 is blown. Fuse 9 protects power supply connector 9 of the MPC.
Cause: Electrical overload or wear of the fuse.
Effect: Injections will not occur on cylinders controlled by this MPC.
Sugg. Action:

Check for failures in the external cabling to connector 9. Replace the fuse.

rsn / 2010-03-10 09:00:53

Page 19 of 84

CCUXX
CCUXX_SInvPa

System->Invalid parameters

Description: Invalid MPC parameters. The MPC cannot start with incorrect parameters.
Cause: The alarm appears when the MPC automatically loads the wrong parameter set after MPC
replacement.
Effect: The behaviour of the application in the MPC is not correct. The exact effect is unknown and care
should be taken.
Sugg. Action:

CCUXX_SInvS

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System->Invalid software

Description: The MPC is running an incorrect application program


Cause: MPC is replaced while both MOP A and MOP B are unavailable.
Effect: The ECS may be seriously affected if MPC is runs incorrect software. The exact behaviour is unknown
since it also depends on which MPC is involved.
Sugg. Action:

CCUXX_SIPF

Switch off MPC immediately. When either MOP A or MOP B is operating again, the MPC can be
switched on again. When the automatic preparation of the MPC is finished the MPC will operate
correctly again.
System->Invalid Parameter Flash

Description: The Parameter flash is corrupt.


Cause: The CRC check when reading the parameters from flash failed.
Effect: Parameters from flash cannot be used.
Sugg. Action:
CCUXX_SPow2

Write a new parameter set to flash. If problem persist, the unit may be defect.
24V power supervision->24V power A failure, connector 1B

Description: No power on the MPC power inlet, connector J1, terminal B.


Cause: - The breaker of power supply A for the specified MPC is turned off.
- 24V power supply A is turned off.
- Power cabling is faulty.
Effect: No immediate effect, as the MPC is supplied by power supply B.
Sugg. Action:
CCUXX_SPow2

Check for the causes.


24V power supervision->24V power B failure, connector 1C

Description: No power on theMPC power inlet, connector J1, terminal C.


Cause: - The breaker of power supply B for the specified MPC is turned off.
- 24V power supply B is turned off.
- Power cabling is faulty.
Effect: No immediate effect, as the MPC is supplied by power supply A.
Sugg. Action:
CCUXX_SWDo

Check for the causes.


System->Watchdogs deactivated

Description: The watchdog on the MPC has been disabled.


Cause: Wrong setting of the orange DIP-switch on the MPC.
Effect: No immediate effect, but with watchdogs disabled the MPC may not respond correctly to software and
hardware failures.
Sugg. Action:

Check that MPC DIP-switch is enabled (orange switch must be ON).

rsn / 2010-03-10 09:00:53

Page 20 of 84

EICUXX
EICUXX_01010

Governor Mode Selector->ECS Speed Mode Command

Description: ECS has overruled the active governor mode (Fixed Index) selected on MOP.
Cause: The speed set point and the actual speed does not follow.
E.g. due to load variations.
Effect: The ECS has selected Speed Mode automatically
Sugg. Action:
EICUXX_02J

No Action
Cylinder Lubrication->Nominel Parameterset not Valid

Description: Invalid MPC parameters. The MPC cannot start with incorrect parameters.
Cause: The combination of S%, FeedRateFactor and Adjust factor is too high, or the lubricator(s) are too small
for the engine.
Effect: The cylinder lubricator will be activated with the highest frequency possible (once per revolution).
Sugg. Action:

EICUXX_02K

Check that the parameter is set (S%, FeedRateFactor and Adjustfactor) according to MAN B&W
specification. Check that lubricator size is according to specification and that the parameter
"Mass/Injection per Cylinder" is correct.
Cylinder Lubrication->Max Limiter Parameterset not Valid

Description: Invalid MPC parameters. The MPC cannot start with incorrect parameters.
Cause: The parameter for normal max level is too high or the lubricators are too small for the engine.
Effect: The cylinder lubricator will be activated with the highest frequency possible (once per revolution).
Sugg. Action:

EICUXX_02L

Check that the parameter for max is according to MBD specification. Check that lubricator size is
according to specification and that the parameter "Mass/Injection per Cylinder" is correct.
Cylinder Lubrication->Run In Parameterset not Valid

Description: Invalid MPC parameters. The MPC cannot start with incorrect parameters.
Cause: The parameter for run in max level is too high or the lubricators are too small for the engine.
Effect: The cylinder lubricator will be activated with the highest frequency possible (once per revolution).
Sugg. Action:

EICUXX_0345

Check if the parameter for run in max is according to MBD specification. Check that lubricator size is
according to specification and that the parameter "Mass/Injection per Cylinder" is correct.
Hydraulic Power Supply->Hydraulic Pressure fell too quickly

Description: Hydraulic pressure fell too quickly after all pumps were stopped.
Cause: Hydraulic leakage or failing accumulator(s).
Effect: Hydraulic leakage or failing accumulators may cause problems when the engine is started again.
Correct these failures before attempting normal running.
Sugg. Action:

EICUXX_0347

Check for Hydraulic leakage and check accumulator pressure.


- Investigate all HCU's by cutting off relevant valves. Do this one HCU at a time and evaluate leakage
result.
Hydraulic Power Supply->Hydr. Press. Regulator High Fail

Description: The automatic pressure control could not achieve correct pressure. Hydraulic pressure lower than
desired.
Cause: HPS pumps do not deliver as high pressure as expected or leakage has increased or electrical
connection to HPS is failing.
Effect: Too low pressure may reduce injections and slow down the engine - in extreme cases stop the engine.
Sugg. Action:

Check cabling to HPS (e.g. using manual control).


Check pressure sensor.
Check for hydraulic leakages.
Check Swash Plate Indicators.
Check that there are no other alarms for Pumps missing.
Check switch settings on HPS starter cabinets are in normal position.
Check EICU J80 relay:
a) Off then "Slave" pump should be running.
b) ON then "Slave" pump should be stopped.
If all checks above are ok, the HPS proportional valve may need to be recalibrated.
NOTE:
The HPS switch setting on starter cabinet should be set to "Pump 1 Master" or "Pump 2 Master". If the
switch is in "Pump 1 & 2" then both HPS pumps should run.

rsn / 2010-03-10 09:00:53

Page 21 of 84

EICUXX
EICUXX_0348

Hydraulic Power Supply->Hydr. Press. Regulator Low Fail

Description: The automatic pressure control could not achieve correct pressure. Hydraulic pressure higher than
desired.
Cause: - HPS pumps deliver higher pressure than expected, or
- Leakage has decreased.
Effect: Too high pressure can result in excessive electrical power consumption.
Sugg. Action:

Check cabling to HPS (e.g. using manual control).


Check pressure sensor.
Check for hydraulic leakages.
Check Swash Plate Indicators.
Check that there are no other alarms for Pumps missing.
Check switch settings on HPS starter cabinets are in normal position.
Check EICU J80 relay:
a) Off then "Slave" pump should be running.
b) ON then "Slave" pump should be stopped.
If all checks above are ok, the HPS proportional valve may need to be recalibrated.
NOTE:
The HPS switch setting on starter cabinet should be set to "Pump 1 Master" or "Pump 2 Master". If the
switch is in "Pump 1 & 2" then both HPS pumps should run.

EICUXX_0353

Hydraulic Power Supply->Hydr. Press. too high

Description: Hydraulic pressure is higher than alarm limit.


Cause: HPS oil flow too high resulting in too high pressure.
Effect: Too high pressure can result in excessive electrical power consumption.
Sugg. Action:

EICUXX_0354

Check cabling to HPS (e.g. using manual control).


Check pressure sensor.
Check position of manual override valve on the HPS.
Check Swash Plate Indicators.
Hydraulic Power Supply->Hydr. Press. too low

Description: Hydraulic pressure is lower than alarm limit.


Cause: - Hydraulic supply Pump failure, or
- Hydraulic leakage or failing bypass valves in the hydraulic supply system, or
- One or more hydraulic supply pumps stopped.
Effect: Too low pressure may reduce injections and slow down the engine - in extreme cases stop the engine.
Sugg. Action:

Check cabling to HPS (e.g. using manual control).


Check pressure sensor.
Check for hydraulic leakages.
Check Swash Plate Indicators.
Check that there are no other alarms for Pumps missing.
Check switch settings on HPS starter cabinets are in normal position.
Check EICU J80 relay:
a) Off then "Slave" pump should be running.
b) ON then "Slave" pump should be stopped.
If all checks above are ok, the HPS proportional valve may need to be recalibrated.
NOTE:
The HPS switch setting on starter cabinet should be set to "Pump 1 Master" or "Pump 2 Master". If the
switch is in "Pump 1 & 2" then both HPS pumps should run.

EICUXX_0361

Hydraulic Power Supply->Pump 1 not Running

Description: The hydraulic pump should run because the engine is running.
Cause: The pump does not give a "Running" signal.
Effect: - Maximum engine load is limited if pump is not running.
- The Engine Control System (ECS) have ordered the HPS slave pump to start (J80 = OFF). The slave
pump will be running until both Pump running signals have been detected On.
Sugg. Action:

- Check if the pump is running.


- if it is running check the cable giving a "Running" signal to ECS.
- In case the Pump running signal turns On/Off and triggers the slave pump to start/stop go to the HPS
starter cabinets and move switch to "Pump 1 & 2". This will disable control of the slave pump by the
ECS. Move the switch to "Pump 1 Master" or "Pump 2 Master" after the problem has been solved.

rsn / 2010-03-10 09:00:53

Page 22 of 84

EICUXX
EICUXX_0362

Hydraulic Power Supply->Pump 2 not Running

Description: The hydraulic pump should run because the engine is running.
Cause: The pump does not give a "Running" signal.
Effect: - Maximum engine load is limited if pump is not running.
- The Engine Control System (ECS) have ordered the HPS slave pump to start (J80 = OFF). The slave
pump will be running until both Pump running signals have been detected On.
Sugg. Action:

EICUXX_0370

- Check if the pump is running.


- if it is running check the cable giving a "Running" signal to ECS.
- In case the Pump running signal turns On/Off and triggers the slave pump to start/stop go to the HPS
starter cabinets and move switch to "Pump 1 & 2". This will disable control of the slave pump by the
ECS. Move the switch to "Pump 1 Master" or "Pump 2 Master" after the problem has been solved.
Hydraulic Power Supply->Manual Hydr. Press Control

Description: HPS pressure control is manual


Cause: Manual Activated
Effect: The HPS will "bumpless" change to Manual operation. The pressure setpoint can be overruled by the
operator by manually altering the pressure setpoint. The new pressure setpoint will be used until the
operator either selects a new setpoint, or returns to Automatic mode.
NOTE:
A large increase in setpoint could trigger the HPS slave pump to start. Therefore it is recommended to
limit the steps to about 20 bar.
Sugg. Action:

Switch to Automatic operation when manual operation is ended.


NOTE:
In case the ECS setpoint in automatic operation is more than 20 bar above the manual setpoint,
increase the manual pressure setpoint, before switching out of manual operation.

EICUXX_03810

Slave Pump Run/Stop->Master/Slave Pump Not Running

Description: The Engine Control System (ECS) expects more pumps to run but only zero or one "Running" signal is
currently present.
Cause: - Could be caused by wrong running signal or failed pump(s).
- Could be wrong switch settings on the HPS starter cabinet.
Effect: - No effect if both HPS pumps are running.
- If only one pump is running the maximum obtainable load will be limited depending on engine
configuration. Normally minimum 55% engine load should be possible.
- If no pumps are running the engine will stop.
Sugg. Action:

- Move the HPS Slave pump control switch to "Pump 1 & 2" on the HPS starter cabinet, while
troubleshooting. This will prevent the ECS from starting/stopping the slave pump untill the error has
been identified and corrected. In case this is not desirable repeated start/stop of the slave pump can
be expected.
- Check switch settings on HPS starter cabinets are in normal position. Position are either
1) Pump 1 Master (Pump 2 controlled by EICU J80 On = STOP)
2) Pump 1 & 2 (Both Pumps running)
3) Pump 2 Master (Pump 1 controlled by EICU J80 On = STOP)
- Check the HPS pumps and verify that both pumps are not running. If they are both running a failure in
one of the running signal is present. Check cabling to Pump 1 and Pump 2 running signals.
(EICU J31 Pump 1 Running signal)
(EICU J34 Pump 2 Running signal).
- Check cabling for EICU J80 relay:
a) Off then "Slave" pump should be running.
b) ON then "Slave" pump should be stopped.
NOTE:
The HPS switch setting on starter cabinet should be set to Pump 1 Master or Pump 2 Master. If the
switch is in "Pump 1 & 2" position then both HPS pumps should always run.

rsn / 2010-03-10 09:00:53

Page 23 of 84

EICUXX
EICUXX_03810

Slave Pump Run/Stop->Slave Pump Started Due to Error(s)

Description: Normally the ECS only starts the Slave pump when the engine load is above a certain limit. In case of
certain errors the Slave pump is ordered started (EICU J80 Off)
Cause: - Hydraulic Pressure is not valid
- Internal load calculation is not valid (CCU1 failure?).
- Setpoint too high compared to actual pressure (Alarm for "Hydr. Press. Regulator High Fail" could
also be present!)
- Missing Pump (Master/Slave pump switched off or missing valid running signals.)
Effect: - No effect if both HPS pumps are running.
- If only one pump is running the maximum obtainable load will be limited depending on engine
configuration. Normally minimum 55% engine load should be possible.
- If no pumps are running the engine will stop.
Sugg. Action:

- Move the HPS Slave pump control switch to "Pump 1 & 2" on the HPS starter cabinet, while
troubleshooting. This will prevent the ECS from starting/stopping the slave pump untill the error has
been identified and corrected. In case this is not desirable repeated start/stop of the slave pump can
be expected.
- Check switch settings on HPS starter cabinets are in normal position. Position are either
1) Pump 1 Master (Pump 2 controlled by EICU J80 On = STOP)
2) Pump1 & 2 (Both Pumps running)
3) Pump 2 Master (Pump 1 controlled by EICU J80 On = STOP)
- Depending on the type of error that caused this alarm to be raised check the following:
a) Cabling to Hydraulic pressure sensor EICU J30.
b) Network or tacho alarms on MOP from CCU1.
c) Hydraulic Pressure Setpoint deviation too large compared to measured pressure.
d) Missing pump running signals.
- Check the HPS pumps and verify that both pumps are not running. If they are both running a failure in
one or both running signals ares present. Check cabeling to Pump 1 and Pump 2 running signals.
(EICU J31 Pump 1 Running signal)
(EICU J34 Pump 2 Running signal).
- Check cabling for EICU J80 relay:
a) Off then "Slave" pump should be running.
b) ON then "Slave" pump should be stopped.
NOTE:
The HPS switch setting on starter cabinet should be set to Pump 1 as slave or Pump 2 as slave. If the
switch is in No Slave position then both HPS pumps should always run.

EICUXX_0601

ECR/RCS Control Selection->Inconsistent Control Stat. Request

Description: The Control Station Switch Logic has detected inconsistent control signal requests. Cabling seem to
be ok but values are inconsistent.
Cause: The control station switch logic expected a high/low combination of the control station request signals.
One of two events has occurred:
- ECR Request and RCS Request both low.
- ECR Request and RCS Request both high.
Effect: The ECS retains its manoeuvre place.
Sugg. Action:

EICUXX_0704

Check cabling between EICU and manoeuvre places.


- Ch22 on EICU is ECR Control (Cable ID = 2121)
- Ch25 on EICU is RCS Control (Cable ID = 2122)
- Replace faulty switch or cut out faulty sensor.
If the problem persists: Replace EICU.
ECS Slow Down Request->No Cyl. Lube Oil due to CCU Failure

Description: No cylinder lubrication for the affected cylinder(s).


Cause: - The Cylinder Control Unit is not in normal running mode.
- The ECS control networks are not connected properly or not working.
Effect: - Probably no cylinder lubrication oil is injected to the cylinder(s).
- Slow Down request is send from ECS to the slow down system.
Sugg. Action:

Check that the LED is green on affected CCU.


- If the LED is NOT green: Rreboot the CCU.
If the problem persists: Replace the MPC.
- If the LED IS green: Use MOP Network status screen to check for network status. Often the only way
to find and correct network problems is to inspect entire network cabling and check for ground failure
on ECS power supply.

rsn / 2010-03-10 09:00:53

Page 24 of 84

EICUXX
EICUXX_0705

ECS Slow Down Request->Slow Down Request

Description: Slow Down Request


Cause: ECS requested Slow Down due to failing cylinder oil lubrication or VT/Bypass problems.
Effect: - No cylinder lubricator oil injected. This will lead to excessive liner wear.
- Too High Pscav can damage Engine or Turbocharger.
Sugg. Action:
EICUXX_1201-1

Check alarm list and follow suggested action.


Ch30,1201-1,P2-A Pressure->Suprv. Ch30,1201-1,P2-A Pressure

Description: The signal from the sensor connected to the specified channel is out of range. The sensor should give
a signal between 4 mA to 20 mA.
Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: - In case engine load changes significantly hydraulic pressure may deviate from setpoint.
- Supervision of hydraulic pressure is no longer possible.
- HPS Slave pump is automatically orderd started (J80 = OFF). The pump is not stopped before the
Hydraulic pressure sensor has ok status (except engine stopped or shutdown).
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

EICUXX_1219-1

Ch31,1219-1,Pump 1 Running->Suprv. Ch31,1219-1,Pump 1 Running

Description: The signal from the sensor connected to the specified channel is out of range. The sensor should give
a signal between 4 mA to 20 mA.
Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: The Engine Control System uses the latest valid value.
Any changes of the input will have no effect while this alarm is active.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

EICUXX_1219-2

Ch34,1219-2,Pump 2 Running->Suprv. Ch34,1219-2,Pump 2 Running

Description: The signal from the sensor connected to the specified channel is out of range. The sensor should give
a signal between 4 mA to 20 mA.
Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: The Engine Control System uses the latest valid value.
Any changes of the input will have no effect while this alarm is active.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

rsn / 2010-03-10 09:00:53

Page 25 of 84

EICUXX
EICUXX_20100

Ch36,2010,Slow Down Command->Suprv. Ch36,2010,Slow Down Command

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: - The input value is fixed to last valid input.
- Automatic slow down will not occur while this signal is bad.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

EICUXX_21030

Ch27,2103,Pitch Actual->Suprv. Ch27,2103,Pitch Actual

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: In case of fast pitch changes the governors ability to maintain constant speed will be reduced.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

EICUXX_21210

Ch25,2121,RCS Control->Suprv. Ch25,2121,RCS Control

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: Detection of inconsistent control station selection (ECR and RCS) is no longer possible.
Normal engine operation is still possible.
Switching between ECR and RCS control is still possible.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

rsn / 2010-03-10 09:00:53

Page 26 of 84

EICUXX
EICUXX_21400

Ch20,2140,ECR Speed Set Point->Suprv. Ch20,2140,ECR Speed Set Poin

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: The Engine Control System uses the latest valid value.
Any changes of the input will have no effect while this alarm is active.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

EICUXX_21420

Ch21,2142,ECR Increase Limit->Suprv. Ch21,2142,ECR Increase Limit

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: The Engine Control System uses the latest valid value.
Any changes of the input will have no effect while this alarm is active.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

EICUXX_21430

Ch22,2143,ECR Control->Suprv. Ch22,2143,ECR Control

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: Detection of inconsistent control station selection (ECR and RCS) is no longer possible.
Normal engine operation is still possible.
Switching between ECR and RCS control is still possible.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

rsn / 2010-03-10 09:00:53

Page 27 of 84

EICUXX
EICUXX_21480

Ch26,2148,Pitch Set Point->Suprv. Ch26,2148,Pitch Set Point

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: LCD (Load Change Dependent Lubrication) is now only based on Speed Set Point.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

EICUXX_21600

Ch23,2160,RCS Speed Set Point->Suprv. Ch23,2160,RCS Speed Set Poin

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: Speed set point from this control station is now fixed to last valid value. In case this is the currently
active control station modification of engine speed is no longer possible. To change engine speed
setpoint switch to another control station.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

EICUXX_21620

Ch24,2162,RCS Increase Limit->Suprv. Ch24,2162,RCS Increase Limit

Description: Channel input is out of range.


Cause: - Failure in the cabling to the sensor, or
- Sensor failurer, or missing sensor power supply, or
- MPC input failure, or
- For On/Off type sensors the cause can be a missing or wrong supervision resistor (typically 6.8
kOhm).
Effect: The Engine Control System uses the latest valid value.
Any changes of the input will have no effect while this alarm is active.
Sugg. Action:

- Check for fuse alarms on MOP Alarm screen. If no fuse alarms then:
- Check cabling to the sensor, according to the installation drawings.
- Check power supply to the sensor (measure voltage between A (negative) and D (positive)). If voltage
is OK (18-32 Vdc): Replace sensor.
- Try to Invalidate the signal on the MPC that has raised the alarm. This could force the input signal to
obtain a different value if this is needed.
If the problem persists: The MPC may be damaged and must be replaced.

EICUXX_badBa

System->Non standard baud rate

Description: Baud rate for service terminal is not 9600 Bd.


Cause: Non standard rate selected.
Effect: No, or unreadable output to service terminal.
Sugg. Action:

Reset blue DIP, and reboot MPC when appropriate.

rsn / 2010-03-10 09:00:53

Page 28 of 84

EICUXX
EICUXX_IDKEY

System->ID Key corrupt

Description: At system in operation an ongoing ID-key test is made.


The alarm is set when a read byte in the ID-key is not equal to the corresponding value saved in the
CPU-RAM.
The alarm is reset as soon a read byte in the ID-key is equal to the corresponding value saved in the
CPU-RAM.
I. e. a problem also exists with the ID-key when the alarm are not set while it has not been
acknowledged.
One byte is tested for each second. If the alarm does not reappear in a test cycle of 256 seconds, the
fail on the ID-key is not steady.
Cause: The ID-key is defect, is not plugged correct or is missing.
Effect: No operational effect until the next restart.
If the ID-key is plugged correct, the persistent data is lost.
Sugg. Action:

EICUXX_SAR-C

Ensure the ID-key is plugged correct in the system.


If plugged correctly and a system restart fails because of problems with the ID-key, replace the ID-key
with a new.
System Status->App. not running on CCU1

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 1 or 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 1 or 2 cylinders.
Tacho signal set A unavailable in case of power failure.
ESC control station unavailable.
Scavenge Air pressure sensor signal unavailable which can cause change in injection timing.
Several values on the MOP display unavailable.
Sugg. Action:

EICUXX_SAR-C

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System Status->App. not running on CCU2

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 2 cylinders.
Tacho signal set B unavailable in case of power failure.
Sugg. Action:

EICUXX_SAR-C

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System Status->App. not running on CCU3

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 2 cylinders.
Sugg. Action:

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.

rsn / 2010-03-10 09:00:53

Page 29 of 84

EICUXX
EICUXX_SAR-C

System Status->App. not running on CCU4

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 2 cylinders.
Sugg. Action:

EICUXX_SAR-C

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System Status->App. not running on CCU5

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 2 cylinders.
Sugg. Action:

EICUXX_SAR-C

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System Status->App. not running on CCU6

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 2 cylinders.
Sugg. Action:

EICUXX_SAR-E

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System Status->App. not running on EICU

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: Ch70:
- Missing HPS Pressure Setpoint (4-20mA). Control of Hydraulic High Pressure is now only possible
manually at the Pump station.
Ch71:
- Missing Fuel Index or Fuel Index Margain output (4-20 mA). FPP plants use Fuel Index and CPP
plants use Fuel Index Margain to the Pitch Contol system.
Sugg. Action:

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.

rsn / 2010-03-10 09:00:53

Page 30 of 84

EICUXX
EICUXX_SAR-E

System Status->App. not running on ESU

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 1 or 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 1 or 2 cylinders.
Tacho signal set A unavailable in case of power failure.
ESC control station unavailable.
Scavenge Air pressure sensor signal unavailable which can cause change in injection timing.
Several values on the MOP display unavailable.
Sugg. Action:

EICUXX_SAR-H

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System Status->App. not running on HSU1

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: - Unable to simulate feedback for ELFIA and ELFIB
- Unable to simulate feedbacksignals for Lubricator A and B
Sugg. Action:

EICUXX_SAR-H

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System Status->App. not running on HSU2

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: - Unable to simulate feedback for ELFIA and ELFIB
- Unable to simulate feedbacksignals for Lubricator A and B
Sugg. Action:

EICUXX_SAR-H

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System Status->App. not running on HSU3

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: - Unable to simulate feedback for ELFIA and ELFIB
- Unable to simulate feedbacksignals for Lubricator A and B
Sugg. Action:

EICUXX_SAR-H

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System Status->App. not running on HSU4

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: - Unable to simulate feedback for ELFIA and ELFIB
- Unable to simulate feedbacksignals for Lubricator A and B
Sugg. Action:

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.

rsn / 2010-03-10 09:00:53

Page 31 of 84

EICUXX
EICUXX_SAR-H

System Status->App. not running on HSU5

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: - Unable to simulate feedback for ELFIA and ELFIB
- Unable to simulate feedbacksignals for Lubricator A and B
Sugg. Action:

EICUXX_SAR-H

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System Status->App. not running on HSU6

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: - Unable to simulate feedback for ELFIA and ELFIB
- Unable to simulate feedbacksignals for Lubricator A and B
Sugg. Action:

EICUXX_SAR-S

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System Status->App. not running on SCU1

Description: The MPC is not in normal running mode. The EICU monitors all MPCs.
Cause: Power loss or MPC reboot.
The alarm appears shortly after MPC power up. It disappears automatically when MPC is in normal
mode.
Effect: Control of the following functions are lost (based on configuration):
- On off bypass control failure
- Variable bypass control failure
- VT actuator control failure
Sugg. Action:

EICUXX_SBAT

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System->Battery Level Low

Description: MPC battery level low.


Cause: Battery discharged.
Effect: If MPC remains switched on, there is no effect. If the MPC is switched off or power is lost, the MPC will
loose its time settings. Time settings will be automatically retrieved at next power on.
Sugg. Action:

EICUXX_SEICU

At next engine stop:


1) Remove power supply on MPC.
2) Replace battery.
3) Reconnect power supply.
System->Global Params. inconsist

Description: The ECS consists of multiple parameters some of which normally needs to be identical. If these
parameters are not identical this alarm is given.
Cause: Changes in ECS parameters have not been updated on all units. This might happen if an MPC was
unavailable during parameter adjustments.
Effect: The ECS might not function optimally.
Sugg. Action:

EICUXX_SFuse

- Readjust the parameter that caused the trouble if possible.


- Check that the EICU and CCU units are running in normal mode. Check this on MOP screen:
Maintenance->System View I/O Test.
- Use ArcEdit-> Analyse Globals to locate parameter inconsistencies.
- Cut Out the alarm and report the problem whenever convenient.
24V power supervision->Fuse F12 failure

Description: Fuse 12 is blown. Fuse 12 protects the sensor power supply, terminal "D", of the analogue inputs,
channels 20 to 37, of the MPC.
Cause: Electrical overload or wear of the fuse.
Effect: A number of the sensors and signals connected to channels 20 to 37 may give wrong values, and a
number of supervision alarms may occur simultaneously.
Sugg. Action:

Check for failures in the external cabling to channels 20 to 37. Replace the fuse.

rsn / 2010-03-10 09:00:53

Page 32 of 84

EICUXX
EICUXX_SFuse

24V power supervision->Fuse F13 failure

Description: Fuse 13 is blown. Fuse 13 protects the power outlets of:


channels 40 to 47, terminal "D",
channels 48 to 53, terminal "E",
channels 60 and 61, terminal "H".
Cause: Electrical overload or wear of the fuse.
Effect: A number of the signals related to channels 40 to 61 may be wrong. Effect on engine behaviour is
unknown.
Sugg. Action:
EICUXX_SFuse

Check for possible failures in the external cabling to channels 40 to 61. Replace the fuse.
24V power supervision->Fuse F14 failure

Description: Fuse 14 is blown. Fuse 14 protects the power supply for the analog output, channels 70 and 71, of the
MPC.
Cause: Electrical overload or wear of the fuse.
Effect: Ch70:
- Missing HPS Pressure Setpoint (4-20mA). Control of Hydraulic High Pressure is now only possible
manually at the Pump station.
Ch71:
- Missing Fuel Index or Fuel Index Margain output (4-20 mA). FPP plants use Fuel Index and CPP
plants use Fuel Index Margain to the Pitch Contol system.
Sugg. Action:

EICUXX_SFuse

Check for failures in the external cabling to channels 70 and 71. Replace the fuse. If the fuse blows
again: Replaced the MPC.
24V power supervision->Fuse F9 failure

Description: Fuse 9 is blown. Fuse 9 protects power supply connector 9 of the MPC.
Cause: Electrical overload or wear of the fuse.
Effect: Loss of Hydraulic Pressure Setpoint.
Sugg. Action:
EICUXX_SInvP

Check for failures in the external cabling to connector 9. Replace the fuse.
System->Invalid parameters

Description: Invalid MPC parameters. The MPC cannot start with incorrect parameters.
Cause: The alarm appears when the MPC automatically loads the wrong parameter set after MPC
replacement.
Effect: The behaviour of the application in the MPC is not correct. The exact effect is unknown and care
should be taken.
Sugg. Action:

EICUXX_SInvS

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.
System->Invalid software

Description: The MPC is running an incorrect application program


Cause: MPC is replaced while both MOP A and MOP B are unavailable.
Effect: The ECS may be seriously affected if MPC is runs incorrect software. The exact behaviour is unknown
since it also depends on which MPC is involved.
Sugg. Action:

EICUXX_SIPF

Switch off MPC immediately. When either MOP A or MOP B is operating again, the MPC can be
switched on again. When the automatic preparation of the MPC is finished the MPC will operate
correctly again.
System->Invalid Parameter Flash

Description: The Parameter flash is corrupt.


Cause: The CRC check when reading the parameters from flash failed.
Effect: Parameters from flash cannot be used.
Sugg. Action:

Write a new parameter set to flash. If problem persist, the unit may be defect.

rsn / 2010-03-10 09:00:53

Page 33 of 84

EICUXX
EICUXX_SN0-C

System Status->Net A not connected to CCU1

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 34 of 84

EICUXX
EICUXX_SN0-C

System Status->Net A not connected to CCU2

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 35 of 84

EICUXX
EICUXX_SN0-C

System Status->Net A not connected to CCU3

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 36 of 84

EICUXX
EICUXX_SN0-C

System Status->Net A not connected to CCU4

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 37 of 84

EICUXX
EICUXX_SN0-C

System Status->Net A not connected to CCU5

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 38 of 84

EICUXX
EICUXX_SN0-C

System Status->Net A not connected to CCU6

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 39 of 84

EICUXX
EICUXX_SN0-EI System Status->Net A not connected to EICU
Description: Controlling unit not connected to network segment A.
Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 40 of 84

EICUXX
EICUXX_SN0-E

System Status->Net A not connected to ESU

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 41 of 84

EICUXX
EICUXX_SN0-H

System Status->Net A not connected to HSU1

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 42 of 84

EICUXX
EICUXX_SN0-H

System Status->Net A not connected to HSU2

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 43 of 84

EICUXX
EICUXX_SN0-H

System Status->Net A not connected to HSU3

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 44 of 84

EICUXX
EICUXX_SN0-H

System Status->Net A not connected to HSU4

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 45 of 84

EICUXX
EICUXX_SN0-H

System Status->Net A not connected to HSU5

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 46 of 84

EICUXX
EICUXX_SN0-H

System Status->Net A not connected to HSU6

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 47 of 84

EICUXX
EICUXX_SN0-M

System Status->Net A not connected to MOPA

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 48 of 84

EICUXX
EICUXX_SN0-M

System Status->Net A not connected to MOPB

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 49 of 84

EICUXX
EICUXX_SN0-S

System Status->Net A not connected to SCU1

Description: Controlling unit not connected to network segment A.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 50 of 84

EICUXX
EICUXX_SN1-C

System Status->Net B not connected to CCU1

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 51 of 84

EICUXX
EICUXX_SN1-C

System Status->Net B not connected to CCU2

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 52 of 84

EICUXX
EICUXX_SN1-C

System Status->Net B not connected to CCU3

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 53 of 84

EICUXX
EICUXX_SN1-C

System Status->Net B not connected to CCU4

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 54 of 84

EICUXX
EICUXX_SN1-C

System Status->Net B not connected to CCU5

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 55 of 84

EICUXX
EICUXX_SN1-C

System Status->Net B not connected to CCU6

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 56 of 84

EICUXX
EICUXX_SN1-EI System Status->Net B not connected to EICU
Description: The controlling unit is not connected to network segment B.
Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 57 of 84

EICUXX
EICUXX_SN1-E

System Status->Net B not connected to ESU

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 58 of 84

EICUXX
EICUXX_SN1-H

System Status->Net B not connected to HSU1

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 59 of 84

EICUXX
EICUXX_SN1-H

System Status->Net B not connected to HSU2

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 60 of 84

EICUXX
EICUXX_SN1-H

System Status->Net B not connected to HSU3

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 61 of 84

EICUXX
EICUXX_SN1-H

System Status->Net B not connected to HSU4

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 62 of 84

EICUXX
EICUXX_SN1-H

System Status->Net B not connected to HSU5

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 63 of 84

EICUXX
EICUXX_SN1-H

System Status->Net B not connected to HSU6

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 64 of 84

EICUXX
EICUXX_SN1-M

System Status->Net B not connected to MOPA

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 65 of 84

EICUXX
EICUXX_SN1-M

System Status->Net B not connected to MOPB

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

rsn / 2010-03-10 09:00:53

Page 66 of 84

EICUXX
EICUXX_SN1-S

System Status->Net B not connected to SCU1

Description: The controlling unit is not connected to network segment B.


Cause: Network cabling problems.
Effect: If only one network segment alarm is raised: No change in engine behaviour.
If both network segment A and B are affected: No or faulty MPC operation.
Sugg. Action:

If alarm(s) indicates missing connection to one network segment on one MPC:


1) Check that network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems found in the network connection: Replace the unit.
If alarms indicate missing connection on both network segments on the same MPC:
1) Check if the unit is turned on:
1.A) MPC: Indicator LED lamp is illuminated.
1.B) MOP: Graphic application pictures on the screen.
If the unit is turned off: Check for power failure. Otherwise:
MPC related:
1) If the indicator LED lamp of the MPC is green: Check the network connections and connectors of
the unit for cabling failures.
2) Restart the controller, e.g. by turn off turn on power.
3) If the controller does not start up, indicated by the LED changing from red to yellow and to green,
and the network alarms does not disappear: Replace MPC.
MOP Related:
1) If the display of the MOP is active with normal application pictures, but process values are missing:
Check the network connections and connectors of the unit for cabling failures.
2) Restart the MOP (Ctrl Esc, then press Stop MOP and Quit. Wait a bit and press Ctrl Ecs, then Start
MOP). If the MOP does not show application pictures, and the network alarm persists: Repair MOP.
If alarms indicate that several units are not connected on one network segment: Inspect the cabling
and all connectors of the specified network segment.The fault is likely related to:
1) A loose wire in a connector
2) A short circuit between the 2 wires, or between a wire and the cable screen.
3) In each end of the network line a resistor shall be mounted in the network connector. One of them
may be loose or missing.
4) Short circuit between a network wire and ship ground - any metal parts.
5) Network cable damaged.

EICUXX_SNA-C

System Status->MPC CCU1 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 1 or 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 1 or 2 cylinders.
Tacho signal set A unavailable in case of power failure.
ESC control station unavailable.
Scavenge Air pressure sensor signal unavailable which can cause change in injection timing.
Several values on the MOP display unavailable.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

rsn / 2010-03-10 09:00:53

Page 67 of 84

EICUXX
EICUXX_SNA-C

System Status->MPC CCU2 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 2 cylinders.
Tacho signal set B unavailable in case of power failure.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNA-C

System Status->MPC CCU3 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 2 cylinders.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNA-C

System Status->MPC CCU4 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 2 cylinders.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

rsn / 2010-03-10 09:00:53

Page 68 of 84

EICUXX
EICUXX_SNA-C

System Status->MPC CCU5 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 2 cylinders.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNA-C

System Status->MPC CCU6 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: Slow down is requested.
Fuel and cylinder lubrication injections are lost on 2 cylinders.
When running longer periods with faulty CCU backup activation signals for cylinder lubricators are
available on the other CCUs.
On some engines start performance might be reduced due to loss of injections on 2 cylinders.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNA-E

System Status->MPC EICU unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: MOPA and/or MOPB:
- If either MOPA or MOPB are missing on the network it will not affect the running of the engine.
CCU's:
- If a CCU is disconnected from the network:
Fuel injection is stopped immediately.
EICU:
- Loss of Remote Control.
- Speed set command is only possible from ESC (Engine Side Console).
- MOP display limited and unable to request engine running mode and performance adjustments.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

rsn / 2010-03-10 09:00:53

Page 69 of 84

EICUXX
EICUXX_SNA-E

System Status->MPC ESU unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: MOPA and/or MOPB:
- If either MOPA or MOPB are missing on the network it will not affect the running of the engine.
CCU's:
- If a CCU is disconnected from the network:
Fuel injection is stopped immediately.
EICU:
- Loss of Remote Control.
- Speed set command is only possible from ESC (Engine Side Console).
- MOP display limited and unable to request engine running mode and performance adjustments.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNA-H

System Status->MPC HSU1 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: No effect.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNA-H

System Status->MPC HSU2 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: No effect.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNA-H

System Status->MPC HSU3 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: No effect.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

rsn / 2010-03-10 09:00:53

Page 70 of 84

EICUXX
EICUXX_SNA-H

System Status->MPC HSU4 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: No effect.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNA-H

System Status->MPC HSU5 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: No effect.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNA-H

System Status->MPC HSU6 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: No effect.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNA-M System Status->MPC MOPA unavailable


Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: No effect on engine operation and load.
No MOP adjustments, commands and alarms available from that MOP. General M/E alarm signal
available.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

rsn / 2010-03-10 09:00:53

Page 71 of 84

EICUXX
EICUXX_SNA-M System Status->MPC MOPB unavailable
Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: No effect on engine operation and load.
No MOP adjustments, commands and alarms available from that MOP. General M/E alarm signal
available.
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNA-S

System Status->MPC SCU1 unavailable

Description: EICU cannot detect unit on either of the networks (segment A and B).
Cause: - No power to the unit, or
- Network cables are disconnected from the unit, or
- Network cables to the unit are damaged, or
- Terminating resistor missing.
Effect: In case any of the following systems are present scavenging air control will be limited.
- On off bypass valve
- Variable bypass
- VT turbocharger
Sugg. Action:

MOPA and/or MOPB:


- Check that the unit(s) are turned on and that the control network is properly connected.
MPC (EICU, SCU or CCU's):
- Check that the LED indication on MPC is on and NOT Red. If LED is Red: Reset MPC.
- Check that the control network is properly connected and cables not damaged.

EICUXX_SNET

System Status->Controlnetwork is crossconnected

Description: The network is cross-connected on one or more Multi Purpose Controllers (MPC's) or the Main
Operating Panel(s) (MOP)
Cause: One or both of the following two events have occurred:
1) Network cable A has been connected to network channel B.
2) Network cable B has been connected to network channel A.
Effect: No effect.
Sugg. Action:

Go to the Network Status screen on the MOP-A or MOP-B (Maintenance -> Network Status)
Cross-connected nodes can be viewed on Network Status screen. Check cabling to MPC's and MOP's.
MPC's Network Cable A should be connected to terminal J65. Network Cable B should be connected
to terminal J66.
MOP the connectors are marked A and B.

EICUXX_SPow2 24V power supervision->24V power A failure, connector 1B


Description: No power on the MPC power inlet, connector J1, terminal B.
Cause: - The breaker of power supply A for the specified MPC is turned off.
- 24V power supply A is turned off.
- Power cabling is faulty.
Effect: No immediate effect, as the MPC is supplied by power supply B.
Sugg. Action:

Check for the causes.

EICUXX_SPow2 24V power supervision->24V power B failure, connector 1C


Description: No power on theMPC power inlet, connector J1, terminal C.
Cause: - The breaker of power supply B for the specified MPC is turned off.
- 24V power supply B is turned off.
- Power cabling is faulty.
Effect: No immediate effect, as the MPC is supplied by power supply A.
Sugg. Action:

Check for the causes.

rsn / 2010-03-10 09:00:53

Page 72 of 84

EICUXX
EICUXX_SWDo

System->Watchdogs deactivated

Description: The watchdog on the MPC has been disabled.


Cause: Wrong setting of the orange DIP-switch on the MPC.
Effect: No immediate effect, but with watchdogs disabled the MPC may not respond correctly to software and
hardware failures.
Sugg. Action:

Check that MPC DIP-switch is enabled (orange switch must be ON).

rsn / 2010-03-10 09:00:53

Page 73 of 84

SCUXX
SCUXX_110120

ECS Commands->No Commands Received from EICU

Description: No control values received from EICU


Cause: - EICU failure, or
- Network failure
Effect: SCU does not receive a set point. Last valid value will be used.
Sugg. Action:
SCUXX_110121

Switch to manual scavenging air pressure control


ECS Commands->No Commands Received from EICU

Description: No control values received from EICU


Cause: - EICU failure, or
- Network failure
Effect: SCU does not receive a set point. Last valid value will be used.
Sugg. Action:
SCUXX_1180

Switch to manual scavenging air pressure control


IO Terminals->Slow Down Request (TC Overspeed)

Description: Turbocharger speed is too high


Cause: - Variable turbocharger/ bypass valve is closed AND current engine load is high, or
- Measurement equipment failure
Effect: Slowdown request is issued to the safety system.
Sugg. Action:

1. Keep engine load below 75%


2. Reset slowdown
3. Set the variable turbocharger/bypass valve to fully open (MOP: Auxiliaries -> Scavenge Air and
select Manual control, requires chief level)
4. Resume normal engine operation.
If the problem persists, check actual variable turbocharger/bypass valve position
If the problem persists, open variable turbocharger/bypass valve by local control or mechanically (refer
to actuator manual).

SCUXX_1181

IO Terminals->Slow Down Request (high Pscav)

Description: Scavenging air pressure (Pscav) is too high


Cause: - Variable turbocharger/ bypass valve is closed AND current engine load is high, or
- Measurement equipment failure
Effect: Slowdown request is issued to the safety system.
Sugg. Action:

1. Keep engine load below 75%


2. Reset slowdown
3. Set the variable turbocharger/bypass valve to fully open (MOP: Auxiliaries -> Scavenge Air and
select Manual control, requires chief level)
4. Resume normal engine operation.
If the problem persists, check:
- Pscav measurement equipment. Compare to other Pscav measurements.
- Mechanical position of variable turbocharger/bypass valve
If the problem persists:
Open variable turbocharger/bypass valve by local control or mechanically (refer to actuator manual).

SCUXX_120201

Amplifier->Bypass Amp. Current Supervision

Description: Amplifier current deviates from set point


Cause: - Bypass valve failure, or
- Amplifier failure, or
- MPC failure, or
- Cable failure
Effect: Exhaust bypass valve cannot be controlled by engine control system.
Engine performance may be affected.
Sugg. Action:

Check:
- Bypass valve
- Amplifier
- MPC, including MPC fuse for amplifier
Reset amplifier (switch MPC power off and on)
If the problem persists replace, one unit at a time :
- Amplifier
- MPC
rsn / 2010-03-10 09:00:53

Page 74 of 84

SCUXX
SCUXX_120201

Amplifier->Bypass Amp. thermal protect. act.

Description: Actuator failure. Amplifier has shut down.


Cause: - Sensor cable failure, or
- Sensor failure, or
- No power supply to sensor, or
- MPC input failure, or
- Amplifier failure, or
- Amplifier power supply failure
Effect: The amplifier automatically resets. Bypass control is disabled for 5 seconds.
Sugg. Action:

Check:
- Cabling
- Amplifier fuse
If fuse and cabling is OK: Replace amplifier

SCUXX_120281

Controllable Variable Bypass->Var. Byp. Position ctrl. fail

Description: No or insufficient bypass valve movement


Cause: - Bypass valve is stuck, or
- Valve position feedback signal failure
Effect: Bypass will move to failsafe position (open (most likely), closed or last valid position)
Sugg. Action:

Check:
- Cabling
- Position feedback signal
- Bypass valve movement
If valve movement is ok:
1. Switch to manual bypass valve control to reset the alarm (MOP: Auxiliaries -> Scavenging Air. Chief
mode required)
2. Switch back to automatic control

SCUXX_120282

Controllable Variable Bypass->Var. Byp. Pot. signal failed

Description: Actuator position feedback failure


Cause: - Cable failure, or
- Potentiometer failure
Effect: Bypass valve moves to failsafe position
Sugg. Action:

Check:
- Cabling
- Potentiometer. MPC must receive 4-20mA signal from potentiometer
- Bypass valve movement
If valve movement is ok:
1. Switch to manual bypass valve control to reset the alarm (MOP: Auxiliaries -> Scavenging Air. Chief
mode required)
2. Switch back to automatic control

SCUXX_120283

Controllable Variable Bypass->Var. Byp. Open switch failed

Description: Bypass valve open switch signal and valve position feedback signal do not match.
Cause: - Cabling failure, or
- Switch failure, or
- Switches and/or potentiometer are misaligned, or
- Potentiometer failure
Effect: Position feedback signal control has switched to failsafe mode
Sugg. Action:

Check:
- Cabling
- Switch
- Potentiometer
If all is ok:
1. Switch to manual mode to reset alarm
2. Switch back to automatic control

rsn / 2010-03-10 09:00:53

Page 75 of 84

SCUXX
SCUXX_120284

Controllable Variable Bypass->Var. Byp. Closed switch failed

Description: Bypass close switch signal and valve position feedback signal do not match.
Cause: - Cabling failure, or
- Switch failure, or
- Switches and/or potentiometer are misaligned, or
- Potentiometer failure
Effect: Position feedback signal control has switched to failsafe mode.
Sugg. Action:

Check:
- Cabling
- Switch
- Potentiometer
If all is ok:
1. Switch to manual mode to reset alarm
2. Switch back to automatic control

SCUXX_120380

On/Off Bypass->On/Off Bypass Control Failure

Description: On/off bypass valve position control failure


Cause: - On/off bypass valve is stuck, or
- End stop switch failure
Effect: If only feedback is damaged, the valve will continue to function. Else the valve will have no or limited
movement, and be in an undefined position.
Sugg. Action:

If on/off bypass valve is stuck:


Keep engine load below 75% until the problem is solved or it is verified that the valve is in the correct
position.
Check:
- Actuator cabling
- If bypass valve can move
- Actuator end stop switches

SCUXX_120381

On/Off Bypass->No Air for On/Off Bypass Actuator

Description: Insufficient control air pressure to actuate on/off exhaust gas bypass
Cause: - Control air pressure is being vented, or
- Air control system failure
Effect: On/off bypass valve is forced open
Sugg. Action:

SCUXX_120680

Check:
- Air pressure sensors
- Control air system
Selfcontr. Manual Control->Local Control (service term.)

Description: MPC Service Terminal controls bypass valve (local control)


Cause: User has enabled service terminal control
Effect: No automatic bypass valve control.
No MOP control.
Sugg. Action:
SCUXX_120681

Disable service terminal control as soon as service terminal operation is completed.


Selfcontr. Manual Control->Manual Control (MOP)

Description: Main Operating Panel (MOP) controls the bypass valve


Cause: Manual control has been activated on MOP: Auxiliaries -> Scavenging Air screen.
Effect: No automatic scavenging air pressure control
Sugg. Action:

Switch back to automatic mode when manual operation is completed: Auxiliaries -> Scavenging Air
(Chief level access required)

rsn / 2010-03-10 09:00:53

Page 76 of 84

SCUXX
SCUXX_120780

Selfcontr. Setpoint Deviation->Position deviates from Setp.

Description: Bypass valve position deviates from the set point


Cause: - Bypass valve stiction, or
- Bypass actuator failure, or
- Cable failure, or
- MPC failure
Effect: No bypass valve control.
Last valid bypass valve position set point is used.
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 -> Scavenging Air -> Variable bypass (requires chief
level and manual control)
2. Reset actuator on MOP
3. Power bypass valve off and on.
If the problem persists:
- Check cabling and mechanics
- Recalibrate bypass valve

SCUXX_120880

Var. Valve Overspeed Handling->TC Overspeed

Description: Turbocharger speed is too high


Cause: - Bypass valve is too open for the current engine load, or
- Measurement equipment failure, or
- Mechanical turbocharger failure
Effect: Bypass valve automatically attempts to open fully to reduce the turbocharger speed.
If this attempt reduces the speed sufficiently, the alarm is cancelled, bypass valve control will switch
back to normal control.
Sugg. Action:

Reduce engine load to below 75%


If engine load above 75% is required, open bypass valve mechanically or via MOP.

SCUXX_120980

Selfcontr. Actuator Fail. Handl.->Actuator Reports Fault

Description: Bypass valve actuator is not ready


Cause: - Actuator power failure, or
- Cabling failure (ch 21), or
- Control air failure, or
- Actuator control failure, or
- Bypass valve stiction
Effect: Bypass valve does not move.
If the valve is closed or partially closed, keep engine load below 75%.
Sugg. Action:

Reset the bypass valve control on MOP: Auxiliaries -> Scavenging Air -> Variable bypass (requires
chief level and manual control)
If the problem persists, check:
- Control air pressure
- Actuator power
- Cabling
- If bypass valve is stuck
If engine load above 75% is required, move bypass valve to fully open position.

SCUXX_1280

Exhaustgas Bypass->Variable Bypass Command Failed

Description: No valid bypass valve set point


Cause: - No connection to engine control system (ECS), or
- Scavenging air pressure measurement failure, or
- Load estimation failure.
Effect: No automatic scavenge air control.
Switch to manual control, MOP: Auxiliaries -> Scavenging Air
Sugg. Action:

Check:
- Network connection to SCU on MOP: Maintenance -> Network Status
- Scavenging air pressure cabling, signal must be within range (4-20mA)

rsn / 2010-03-10 09:00:53

Page 77 of 84

SCUXX
SCUXX_1281

Exhaustgas Bypass->On/Off Bypass Command Failed

Description: No valid on/off bypass input


Cause: - No connection to engine control system (ECS), or
- Scavenging air pressure measurement failure, or
- Load estimation failure.
Effect: No automatic scavenge air control.
Switch to manual control, MOP: Auxiliaries -> Scavenging Air
Sugg. Action:

SCUXX_1283

Check:
- Network connection to SCU on MOP: Maintenance -> Network Status
- Scavenging air pressure cabling, signal must be within range (4-20mA)
Exhaustgas Bypass->Bypass Manual

Description: Bypass valve control has switched to manual


Cause: User has switched to manual control on MOP
Effect: No automatic bypass valve position control
Sugg. Action:
SCUXX_1690

Switch back to automatic control as soon as manual operation is completed.


Scavenge Air Controller->Too High Pscav

Description: Scavenging air pressure (Pscav) is too high


Cause: - Variable turbocharger/ bypass valve is closed AND current engine load is high, or
- Pscav measurement failure
Effect: Variable turbocharger / bypass valve automatically moves to open position until pressure is reduced.
Sugg. Action:

Switch to manual control.


NOTE
If engine load above 75% is required, open variable turbocharger/bypass valve mechanically or via
MOP.

SCUXX_1691

Scavenge Air Controller->Automatic control not possible

Description: No automatic scavenge air control


Cause: - No connection to engine control system (ECS), or
- Scavenging air pressure measurement failure, or
- Load estimation failure.
Effect: No automatic scavenge air control.
Switch to manual control, MOP: Auxiliaries -> Scavenging Air
Sugg. Action:

SCUXX_170104

Check:
- Network connection to SCU on MOP: Maintenance -> Network Status
- Scavenging air pressure cabling, signal must be within range (4-20mA)
Manual Control->Local Control (service term.)

Description: MPC Service Terminal controls variable turbocharger (Local control)


Cause: User has enabled service terminal control
Effect: No automatic variable turbocharger control.
No MOP control.
Sugg. Action:
SCUXX_170104

Disable service terminal control as soon as service terminal operation is completed.


Manual Control->Manual Control (MOP)

Description: Main Operating Panel (MOP) controls the variable turbocharger


Cause: Manual control has been activated on MOP: Auxiliaries -> Scavenging Air screen.
Effect: No automatic scavenging air pressure control
Sugg. Action:

Switch back to automatic control when manual operation is completed. Auxiliaries -> Scavenging Air
(Chief level access required)

rsn / 2010-03-10 09:00:53

Page 78 of 84

SCUXX
SCUXX_170201

Setpoint Deviation->Position deviates from Setp.

Description: Variable turbocharger position deviates from the set point


Cause: - Mechanical failure, or
- Actuator calibration failure, or
- Electrical failure, or
- Actuator failure, or
- Cable failure
Effect: No variable turbocharger control.
Last valid variable turbocharger set point is used.
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 -> Scavenging Air -> TC (requires chief
level and manual control)
2. Reset actuator on MOP
3. Power variable turbocharger cabinet off and on.
If the problem persists:
Check cabling and mechanics.
Recalibrate variable turbocharger

SCUXX_170202

Overspeed Handling->TC Overspeed

Description: Turbocharger speed is too high


Cause: - Variable turbocharger is closed AND current engine load is high, or
- Measurement equipment failure, or
- Mechanical turbocharger failure
Effect: Variable turbocharger automatically attempts to open fully to reduce the turbocharger speed.
If this reduces the speed sufficiently, the alarm is cancelled, and variable turbocharger control will
switch back to normal control.
Sugg. Action:

Reduce engine load to below 75%


NOTE
If engine load above 75% is required, move variable turbocharger to fully open position

SCUXX_170203

Torque Limits->VT actuator torque high

Description: Actuator torque is too high


Cause: - Mechanical failure, or
- Actuator failure, or
- Insufficient variable turbocharger actuator scaling
Effect: SCU attempts full variable turbocharger opening (failsafe position)
Sugg. Action:

SCUXX_170203

Reset unit
Check variable turbocharger
Torque Limits->VT actuator torque high high

Description: Actuator torque is too high


Cause: - Mechanical failure, or
- Actuator failure, or
- Insufficient variable turbocharger actuator scaling
Effect: SCU attempts full variable turbocharger opening (failsafe position)
Sugg. Action:

Check:
- Variable turbocharger
- Actuator temperature
If the problem persist and continued operation is necessary:
Reset actuator on MOP: Auxiliaries -> Scavenge Air or power off/on variable turbocharge.

rsn / 2010-03-10 09:00:53

Page 79 of 84

SCUXX
SCUXX_170204

Actuator Failure Handling->Actuator Reports Fault

Description: Variable turbocharger is not ready


Cause: - No power on actuator/control cabinet, or
- Control cabinet fuse is blown, or
- Cable failure (MPC ch. 40), or
- Actuator failure, or
- Torque too high
Effect: Variable turbocharger does not move.
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).
If the problem persists, check:
- Cabling
- Actuator power
- Variable turbocharger

SCUXX_800004

Ch30,8000,Engine Speed->Suprv. Ch30,8000,Engine Speed

Description: Engine speed input signal is out of range (4-20mA)


Cause: - Cable failure, or
- Sensor failure
Effect: Alarm: 'Automatic control not possible'
SCU will order actuator to lock in last position
Sugg. Action:

Switch to manual variable turbocharger/bypass valve position control until the problem is solved.
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move variable turbocharger/bypass valve to fully open position.

SCUXX_800104

Ch31,8001,Fuel Index->Suprv. Ch31,8001,Fuel Index

Description: Fuel index input signal is out of range (4-20mA)


Cause: - Cable failure, or
- Sensor failure
Effect: If no torquemeter is applied, the variable turbocharger/bypass valve will stay in last valid position.
Alarm: 'Automatic control not possible'
Sugg. Action:

Switch to manual variable turbocharger/bypass valve position control until the problem is solved.
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move variable turbocharger/bypass valve to fully open position.

SCUXX_800304

Ch32,8003,PscavSensor #1 (bar)->Suprv. Ch32,8003,PscavSensor #1 (ba

Description: Pscav input signal is out of range (4-20mA)


Cause: - Cable failure, or
- Sensor failure
Effect: Alarm: Automatic control not possible
If only one Pscav sensor is used, or if both Pscav sensors are failing: Variable turbocharger will use
last valid control value.
Otherwise: Redundancy reduced
Sugg. Action:

Switch to manual variable turbocharger/bypass valve position control until the problem is solved.
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move variable turbocharger/bypass valve to fully open position.

rsn / 2010-03-10 09:00:53

Page 80 of 84

SCUXX
SCUXX_800404

Ch33,8004,PscavSensor #2 (bar)->Suprv. Ch33,8004,PscavSensor #2 (ba

Description: Pscav sensor is out of range (4-20mA)


Cause: - Cable failure, or
- Sensor failure
Effect: If only one Pscav sensor is used, or if both Pscav sensors are failing, variable turbocharger will use
last valid control value.
Otherwise: Redundancy reduced
Sugg. Action:

Switch to manual variable turbocharger/bypass valve position control until the problem is solved.
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move variable turbocharger/bypass valve to fully open position.

SCUXX_872104

Ch21,8721,Var. Bypass Position->Suprv. Ch21,8721,Var. Bypass Positi

Description: Pscav sensor is out of range (4-20mA)


Cause: - Cabling failure
- Sensor/actuator failure
Effect: Bypass valve moves to failsafe position
Sugg. Action:

Switch to manual bypass valve position control until the problem is solved.
Check:
- Cabling
- Position measurement.
NOTE
If engine load above 75% is required, move bypass valve to fully open position

SCUXX_875104

Ch21,8751,Var. Bypass Position->Suprv. Ch21,8751,Var. Bypass Positi

Description: Bypass valve position signal is out of range (4-20mA)


Cause: - Cable failure, or
- Sensor failure
Effect: Bypass valve will use last valid value
Sugg. Action:

Switch to manual bypass valve position control until the problem is solved.
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move bypass valve to fully open position

SCUXX_881804

Ch34,8818,VT Position (External For->Suprv. Ch34,8818,VT Position (Exter

Description: Variable turbocharger position signal is out of range (4-20mA)


Cause: - Cable failure, or
- Sensor failure
Effect: Variable turbocharger will use last valid value.
Sugg. Action:

Switch to manual variable turbocharger position control until the problem is solved.
Check:
- Cabling
- Sensor
NOTE
If engine load above 75% is required, move variable turbocharger to fully open position

rsn / 2010-03-10 09:00:53

Page 81 of 84

SCUXX
SCUXX_881904

Ch35,8819,TC Speed->Suprv. Ch35,8819,TC Speed

Description: Turbocharger speed signal is out of range (4-20mA)


Cause: - Cable failure, or
- Sensor failure
Effect: No turbocharger speed supervision
Sugg. Action:

Check:
- Cabling
- Sensor
Redundancy reduced.

SCUXX_882504

Ch37,8825,Measured Torque (mA)->Suprv. Ch37,8825,Measured Torque (m

Description: Measured torque signal is out of range (4-20mA)


Cause: - Cable failure, or
- Sensor failure
Effect: Engine torque estimate will be based on fuel index only.
Sugg. Action:

SCUXX_badBa

Check:
- Cabling
- Sensor
System->Non standard baud rate

Description: Baud rate for service terminal is not 9600 Bd.


Cause: Non standard rate selected.
Effect: No, or unreadable output to service terminal.
Sugg. Action:
SCUXX_IDKEY

Reset blue DIP, and reboot MPC when appropriate.


System->ID Key corrupt

Description: At system in operation an ongoing ID-key test is made.


The alarm is set when a read byte in the ID-key is not equal to the corresponding value saved in the
CPU-RAM.
The alarm is reset as soon a read byte in the ID-key is equal to the corresponding value saved in the
CPU-RAM.
I. e. a problem also exists with the ID-key when the alarm are not set while it has not been
acknowledged.
One byte is tested for each second. If the alarm does not reappear in a test cycle of 256 seconds, the
fail on the ID-key is not steady.
Cause: The ID-key is defect, is not plugged correct or is missing.
Effect: No operational effect until the next restart.
If the ID-key is plugged correct, the persistent data is lost.
Sugg. Action:

SCUXX_SBAT

Ensure the ID-key is plugged correct in the system.


If plugged correctly and a system restart fails because of problems with the ID-key, replace the ID-key
with a new.
System->Battery Level Low

Description: MPC battery level low.


Cause: Battery discharged.
Effect: If MPC remains switched on, there is no effect. If the MPC is switched off or power is lost, the MPC will
loose its time settings. Time settings will be automatically retrieved at next power on.
Sugg. Action:

SCUXX_SFuse

At next engine stop:


1) Remove power supply on MPC.
2) Replace battery.
3) Reconnect power supply.
24V power supervision->Fuse F12 failure

Description: Fuse 12 is blown. Fuse 12 protects the sensor power supply, terminal "D", of the analogue inputs,
channels 20 to 37, of the MPC.
Cause: Electrical overload or wear of the fuse.
Effect: A number of the sensors and signals connected to channels 20 to 37 may give wrong values, and a
number of supervision alarms may occur simultaneously.
Sugg. Action:

Check for failures in the external cabling to channels 20 to 37. Replace the fuse.

rsn / 2010-03-10 09:00:53

Page 82 of 84

SCUXX
SCUXX_SFuse

24V power supervision->Fuse F13 failure

Description: Fuse 13 is blown. Fuse 13 protects the power outlets of:


channels 40 to 47, terminal "D",
channels 48 to 53, terminal "E",
channels 60 and 61, terminal "H".
Cause: Electrical overload or wear of the fuse.
Effect: A number of the signals related to channels 40 to 61 may be wrong. Effect on engine behaviour is
unknown.
Sugg. Action:
SCUXX_SFuse

Check for possible failures in the external cabling to channels 40 to 61. Replace the fuse.
24V power supervision->Fuse F14 failure

Description: Fuse 14 is blown. Fuse 14 protects the power supply for the analog output, channels 70 and 71, of the
MPC.
Cause: Electrical overload or wear of the fuse.
Effect: Unable to control VT and Bypass valves.
Sugg. Action:

SCUXX_SFuse

Check for failures in the external cabling to channels 70 and 71. Replace the fuse. If the fuse blows
again: Replaced the MPC.
24V power supervision->Fuse F9 failure

Description: Fuse 9 is blown. Fuse 9 protects power supply connector 9 of the MPC.
Cause: Electrical overload or wear of the fuse.
Effect: No effect.
Sugg. Action:
SCUXX_SInvPa

Check for failures in the external cabling to connector 9. Replace the fuse.
System->Invalid parameters

Description: Invalid MPC parameters. The MPC cannot start with incorrect parameters.
Cause: The alarm appears when the MPC automatically loads the wrong parameter set after MPC
replacement.
Effect: The behaviour of the application in the MPC is not correct. The exact effect is unknown and care
should be taken.
Sugg. Action:

If the MPC has just been replaced: Wait for automatic software download to complete.
Check MPC power supply and fuse.

SCUXX_SInvSw System->Invalid software


Description: The MPC is running an incorrect application program
Cause: MPC is replaced while both MOP A and MOP B are unavailable.
Effect: The ECS may be seriously affected if MPC is runs incorrect software. The exact behaviour is unknown
since it also depends on which MPC is involved.
Sugg. Action:

SCUXX_SIPF

Switch off MPC immediately. When either MOP A or MOP B is operating again, the MPC can be
switched on again. When the automatic preparation of the MPC is finished the MPC will operate
correctly again.
System->Invalid Parameter Flash

Description: The Parameter flash is corrupt.


Cause: The CRC check when reading the parameters from flash failed.
Effect: Parameters from flash cannot be used.
Sugg. Action:
SCUXX_SPow2

Write a new parameter set to flash. If problem persist, the unit may be defect.
24V power supervision->24V power A failure, connector 1B

Description: No power on the MPC power inlet, connector J1, terminal B.


Cause: - The breaker of power supply A for the specified MPC is turned off.
- 24V power supply A is turned off.
- Power cabling is faulty.
Effect: No immediate effect, as the MPC is supplied by power supply B.
Sugg. Action:

Check for the causes.

rsn / 2010-03-10 09:00:53

Page 83 of 84

SCUXX
SCUXX_SPow2

24V power supervision->24V power B failure, connector 1C

Description: No power on theMPC power inlet, connector J1, terminal C.


Cause: - The breaker of power supply B for the specified MPC is turned off.
- 24V power supply B is turned off.
- Power cabling is faulty.
Effect: No immediate effect, as the MPC is supplied by power supply A.
Sugg. Action:

Check for the causes.

SCUXX_SWDog System->Watchdogs deactivated


Description: The watchdog on the MPC has been disabled.
Cause: Wrong setting of the orange DIP-switch on the MPC.
Effect: No immediate effect, but with watchdogs disabled the MPC may not respond correctly to software and
hardware failures.
Sugg. Action:

Check that MPC DIP-switch is enabled (orange switch must be ON).

rsn / 2010-03-10 09:00:53

Page 84 of 84

You might also like