Alarmlist 0510 41 PDF
Alarmlist 0510 41 PDF
Alarmlist 0510 41 PDF
ACUXX
009904 Ch35,0099,Prop. Valve Test Set Poin->Suprv. Ch35,0099,Prop. Valve Test S
Description: MBD Special test purposes only
Cause: MBD special test equipment not connected
Effect: No effect on engine. Alarm is only present in MPC Test mode.
Sugg. Action: None. Alarm will disappear when MPC is rebooted into Normal mode
009904
gls / 14-07-2006 10:31:06 Page 1 of 124
02020104
ACUXX
02020105 Amplifier->Bypass Amp. Reports Internal Fault
Description: Amplifier for swashplate pump proportional valve has shut down due to too high current consumption
by the valve
Cause: Most probably a failure in the cabling to the sensor, or
failure of the sensor, or missing sensor power supply, or
failure of the input of the MPC.
Effect: Control of swashplate on actual pump is stopped since the amplifier cannot deliver the required current
before it has been reset. If possible, the swashplate will be set in fail-safe position corresponding to full
flow in AH direction.
Sugg. Action: Inspect entire cabling to and from amplifier. Notice this includes several connections to the ACU and to
the proportional valve. If cabling is OK replace ACU, check/replace proportional valve, or check/replace
amplifier.
1. Closes
2. Opens
3. Stops (Log in Last)
Sugg. Action: Inspect cables to encoder/switches.
Inspect encoders/switches.
1. Closes
2. Opens
3. Stops (Log in Last)
Sugg. Action: Inspect cables to encoder/switches.
Inspect encoders/switches.
1. Closes
2. Opens
3. Stops (Log in Last)
Sugg. Action: Inspect cables to encoder/switches.
Inspect encoders/switches.
02020105
gls / 14-07-2006 10:31:08 Page 2 of 124
020283
ACUXX
020284 Var. Bypass->Var. Byp. Closed switch failed
Description: Close switch of the variable bypass servo is faulty according to the actual encoder position.
Cause: Wiring to switch defect, switch defect, misalignment of switches or wrong encoder feedback
Effect: The Bypass system state goes into failsafe mode and either:
1. Closes
2. Opens
3. Stops (Log in Last)
Sugg. Action: Inspect cables to encoder/switches.
Inspect encoders/switches.
1. Closes
2. Opens
3. Stops (Log in Last)
Sugg. Action: Inspect cables to encoder/switches.
Inspect encoders/switches.
1. Closes
2. Opens
3. Stops (Log in Last)
Sugg. Action: Inspect cables to encoder/switches.
Inspect encoders/switches.
020284
gls / 14-07-2006 10:31:08 Page 3 of 124
0283
ACUXX
0310 Blower Ctrl. 2->Blower 2 Ctrl
Description: The el. motor cannot be controlled by the ECS.
Cause: Can be caused by manually forcing the el. motor to "Local" control or "Off" position on the el. motor
switchboard or electrical malfunctions inside the el. motor switchboard or alternatively the cabling
between the el. motor switchboard and the blower controlling MPC.
Effect: The el. motor will either stop when it is commanded to run by the ECS or run when it is commanded to
stop by the ECS.
Sugg. Action: Check the blower operation control switch at the blower switchboard. The ECS expect the switch to be
in the "Remote" control position. Check the cabling of the signal ID's 8620-x, 8621-x, and 8623-x
between the MPC and the blower switchboard. Check the relays inside the blower switchboard. If all
above seems OK, set the switch in "Off" position and wait a few seconds. Set the switch back in
"Remote" position.
0310
gls / 14-07-2006 10:31:08 Page 4 of 124
0610
ACUXX
070119 Hydraulic Power Supply->Swash
Description: The engine driven swashplate pump that delivers the high hydraulic pressure cannot be controlled by
the MPC.
Cause: Can be caused by loss of the proportional valve position feedback signal from the proportional valve on
the swashplate pump. Alternatively, by loss of the swashplate position feedback signal. Other causes
are failing proportional valve amplifier and mechanical pump related faults
Effect: The pump will try to swivel its swashplate to deliver full flow in the engine AH direction. Hence, the
pump will most likely deliver more in this fault situation, than during normal situations. In case of
reversing the engine, this pump cannot contribute with flow to the HPS. This corresponds to loss of 1
pump. If a mechanical pump related fault have occurred it is unknown if the pump will contribute at all
with flow to the HPS (e.g. broken pump shaft).
Sugg. Action: Check cabling of power out connector J09 to proportional valve amplifier. Check the cabling of
proportional amplifier OK signal, ID 1224-x. Check the cabling of the proportional valve position
feedback signal, 1238-x, from the LVDT amplifier to the MPC and to the proportional valve. Check the
cabling of the swasplate position feedback signal, ID 1222-x, between the pump and the LVDT
amplifier and from the amplifier to the MPC. Check the cabling of the proportional valve amplifier
enable signal, ID 1223-x, from the MPC to the amplifier. Check the cabling of swashplate command
setpoint signal, ID 1240-x, from the MPC to the proportional valve amplifier. Check the current cabling
from this amplifier to proportional valve. Check the pump and proportional valve for mechanical faults
and replace spare parts if necessary.
070119
gls / 14-07-2006 10:31:08 Page 5 of 124
070210
ACUXX
0706 Hydraulic Power Supply->Hydra
Description: Minor leakage from the drip pan below the HPS is detected.
Cause: A minor hydraulic leakage from one or more engine driven swashplate pumps and/or the startup pump
sets is detected by the leakage sensor, ID 1235.
Effect: Hydraulic leakage
Sugg. Action: Find and repair the cause to the hydraulic leak.
0706
gls / 14-07-2006 10:31:08 Page 6 of 124
0719
ACUXX
0722 Hydraulic Power Supply->Hyd.
Description: The minor leakage detected in the drain box, connected to the drip pan, will cause a timed cancellable
shutdown.
Cause: A minor hydraulic leakage from one or more engine driven swashplate pumps and/or the startup pump
sets is detected by the leakage sensor, ID 1235.
Effect: Hydraulic leakage
Sugg. Action: Find and repair the cause to the hydraulic leak.
0722
gls / 14-07-2006 10:31:09 Page 7 of 124
1109-B04
ACUXX
1110-304 I/O Configuration->Ch22,1110-
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: Reduced supervision quality. Redundancy lost.
Sugg. Action: Check the cabling and the resistor of the switch. Check the current into terminal "C" of the channel. It
must be within 1 and 18 mA. If it is while the alarm is present, the MPC may be damaged and must be
replaced.
1110-304
gls / 14-07-2006 10:31:09 Page 8 of 124
1111-A04
ACUXX
1111-B04 I/O Configuration->Ch21,1111-
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: Reduced supervision quality. Redundancy lost.
Sugg. Action: Check the cabling and the resistor of the switch. Check the current into terminal "C" of the channel. It
must be within 1 and 18 mA. If it is while the alarm is present, the MPC may be damaged and must be
replaced.
1111-B04
gls / 14-07-2006 10:31:09 Page 9 of 124
1116-304
ACUXX
1116-A04 I/O Configuration->Ch25,1116-
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: Reduced supervision quality. Redundancy lost.
Sugg. Action: Check the cabling and the resistor of the switch. Check the current into terminal "C" of the channel. It
must be within 1 and 18 mA. If it is while the alarm is present, the MPC may be damaged and must be
replaced.
1116-A04
gls / 14-07-2006 10:31:09 Page 10 of 124
1201-204
ACUXX
1201-304 I/O Configuration->Ch31,1201-
Description: The alarm indicates that the signal from the sensor connected to the specified channel is outside the
legal range. The sensor should give a signal between 4 mA to 20 mA.
Cause: Most probably a failure in the cabling to the sensor, or
failure of the sensor, or missing sensor power supply, or
failure of the input of the MPC.
Effect: Reduced supervision quality, 1 sensor out of 3 is unavailable.
Sugg. Action: Check the cabling to the sensor, according to the installation drawings.
Check that the sensor has sufficient power supply (if it is a 2-wire sensor, the supply is integrated in the
signal).
Check the current into terminal "C" of the channel. It must be within 4 mA and 20 mA.
If the current is above or below the range, the current out of the sensor must be checked.
If the current into the MPC is within the range, while the alarm is present, the MPC may be damaged
and must be replaced.
1201-304
gls / 14-07-2006 10:31:09 Page 11 of 124
1204-104
ACUXX
1204-204 Ch32,1204-2,Lube oil pressure (bar)->Suprv. Ch32,1204-2,Lube oil pressur
Description: The alarm indicates that the signal from the sensor connected to the specified channel is outside the
legal range. The sensor should give a signal between 4 mA to 20 mA.
Cause: Most probably a failure in the cabling to the sensor, or
failure of the sensor, or missing sensor power supply, or
failure of the input of the MPC.
Effect: Reduced supervision quality, 1 sensor out of 3 is unavailable.
Sugg. Action: Check the cabling to the sensor, according to the installation drawings.
Check that the sensor has sufficient power supply (if it is a 2-wire sensor, the supply is integrated in the
signal).
Check the current into terminal "C" of the channel. It must be within 4 mA and 20 mA.
If the current is above or below the range, the current out of the sensor must be checked.
If the current into the MPC is within the range, while the alarm is present, the MPC may be damaged
and must be replaced.
1204-204
gls / 14-07-2006 10:31:09 Page 12 of 124
1204-504
ACUXX
1222-104 I/O Configuration->Ch34,1222-
Description: The alarm indicates that the signal from the sensor connected to the specified channel is outside the
legal range. The sensor should give a signal between 4 mA to 20 mA.
Cause: Most probably a failure in the cabling to the sensor, or
failure of the sensor, or missing sensor power supply, or
failure of the input of the MPC.
Effect: This will lead to pump ctrl. fault. If the pump only suffers from electrical faults, then the pump will
deliver full flow in the engine rotation direction.
Sugg. Action: Check the cabling to the sensor, according to the installation drawings.
Check that the sensor has sufficient power supply (if it is a 2-wire sensor, the supply is integrated in the
signal).
Check the current into terminal "C" of the channel. It must be within 4 mA and 20 mA.
If the current is above or below the range, the current out of the sensor must be checked.
If the current into the MPC is within the range, while the alarm is present, the MPC may be damaged
and must be replaced.
1222-104
gls / 14-07-2006 10:31:09 Page 13 of 124
123304
ACUXX
123404 I/O Configuration->Ch21,1234,
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: Flow in outer pipe of double pipe construction cannot be detected.
Sugg. Action: Check the cabling and the resistor of the switch. Check the current into terminal "C" of the channel. It
must be within 1 and 18 mA. If it is while the alarm is present, the MPC may be damaged and must be
replaced.
123404
gls / 14-07-2006 10:31:09 Page 14 of 124
1238-104
ACUXX
1238-204 I/O Configuration->Ch30,1238-
Description: The alarm indicates that the signal from the sensor connected to the specified channel is outside the
legal range. The sensor should give a signal between 4 mA to 20 mA.
Cause: Most probably a failure in the cabling to the sensor, or
failure of the sensor, or missing sensor power supply, or
failure of the input of the MPC.
Effect: This will lead to pump ctrl. fault. If the pump only suffers from electrical faults, then the pump will
deliver full flow in the engine rotation direction.
Sugg. Action: Check the cabling to the sensor, according to the installation drawings.
Check that the sensor has sufficient power supply (if it is a 2-wire sensor, the supply is integrated in the
signal).
Check the current into terminal "C" of the channel. It must be within 4 mA and 20 mA.
If the current is above or below the range, the current out of the sensor must be checked.
If the current into the MPC is within the range, while the alarm is present, the MPC may be damaged
and must be replaced.
1238-204
gls / 14-07-2006 10:31:09 Page 15 of 124
8501-A04
ACUXX
8501-B04 I/O Configuration->Ch37,8501-
Description: The alarm indicates that the signal from the sensor connected to the specified channel is outside the
legal range. The sensor should give a signal between 4 mA to 20 mA.
Cause: Most probably a failure in the cabling to the sensor, or
failure of the sensor, or missing sensor power supply, or
failure of the input of the MPC.
Effect: Reduced supervision quality. Redundancy lost.
Sugg. Action: Check the cabling to the sensor, according to the installation drawings.
Check that the sensor has sufficient power supply (if it is a 2-wire sensor, the supply is integrated in the
signal).
Check the current into terminal "C" of the channel. It must be within 4 mA and 20 mA.
If the current is above or below the range, the current out of the sensor must be checked.
If the current into the MPC is within the range, while the alarm is present, the MPC may be damaged
and must be replaced.
8501-B04
gls / 14-07-2006 10:31:09 Page 16 of 124
8503-B04
ACUXX
875104 Ch21,8751,Var. Bypass Position->Suprv. Ch21,8751,Var. Bypass Positi
Description: The alarm indicates that the signal from the sensor connected to the specified channel is outside the
legal range. The sensor should give a signal between 4 mA to 20 mA.
Cause: Most probably a failure in the cabling to the sensor, or
failure of the sensor, or missing sensor power supply, or
failure of the input of the MPC.
Effect: The Bypass system state goes into failsafe mode and either:
1. Closes
2. Opens
3. Stops (Log in Last)
Sugg. Action: Check the cabling to the sensor, according to the installation drawings.
Check that the sensor has sufficient power supply (if it is a 2-wire sensor, the supply is integrated in the
signal).
Check the current into terminal "C" of the channel. It must be within 4 mA and 20 mA.
If the current is above or below the range, the current out of the sensor must be checked.
If the current into the MPC is within the range, while the alarm is present, the MPC may be damaged
and must be replaced.
875104
gls / 14-07-2006 10:31:09 Page 17 of 124
SFuseF13
ACUXX
SFuseF14 System->24V power supervision
Description: The alarm indicates that Fuse 14 of the specified MPC is blown. Fuse 14 protects the power supply for
the analog outputs, channels 70 and 71, of the MPC.
Cause: Electrical overload or wear of the fuse.
Effect: The setpoint to the high pressure hydraulic pump's proportional valve is lost (Ch. 70). The pump will
swivel its swashplate to +100% and deliver full flow corresponding to engine rotation direction AH, and
no flow AS. Other alarms will indicate pump control failure. If this pump is the only failing pump, there
will not be an immediate effect on the engine operation. Ch.71 indicates the hydraulic pressure to the
ECR, this will be lost as well.
Sugg. Action: Check for possible failures in the external cabling to channels 70 and 71. Replace the fuse. If it blows
again the MPC must be replaced.
SFuseF14
gls / 14-07-2006 10:31:09 Page 18 of 124
SPow24VB
ACUXX
SWDogDact System->Watchdogs deactivated
Description: The watchdog on the MPC has been disabled.
Cause: Typically caused by wrong setting of the watchdog DIP-switch on the CPU board.
Effect: There is no immediate effect, but with watchdogs disabled the MPC may not respond correctly to
extreme software and hardware failures.
Sugg. Action: The MPC CPU board DIP-switch should be checked and corrected if it is disabled
SWDogDa
gls / 14-07-2006 10:31:09 Page 19 of 124
SWDogDac
CCUXX
01010328 Tacho set A->Tacho set A failure
Description: Inconsistent or missing Tacho signals recorded.
Cause: Defect wiring, sensors or encoders. Damaged teeth on tacho wheel (if fitted). Damaged sensor support
console.
Effect: The MPC had to change active set of tacho sensors. If both sensor set A and B fail on one CCU control
of injection, exhaust and start air valves are stopped.
Sugg. Action: If all signals on one tacho stay low: Check that the tacho sensor power is OK. Hint: All sensor signal
toggle between zero and high at least once per revolution.
01010328
gls / 14-07-2006 10:31:09 Page 20 of 124
010129
CCUXX
010130 Tacho->Marker A Input slip
Description: Tacho A Marker Slave signal (crankshaft) is wrong
Cause: Marker Slave A signal comes on a crankshaft different position than reported by tacho A and tacho B
Effect: A warning that the encoders or the marker slave signal from the crankshaft are unsteady.
Sugg. Action: Correct adjustment at next engine overhaul or engine stop.
010130
gls / 14-07-2006 10:31:09 Page 21 of 124
0227
CCUXX
030116 Fuel Injection->Fuel Plunger Not Returned
Description: Fuel plunger did not return to below expected position before next injection was about to start.
Cause: Fuel oil inlet pressure low, fuel pump suction valve failure, ELFI valve spool stuck failure, fuel plunger
stuck, injection valve(s) failure
Effect: Fuel injections can be significantly affected causing exhaust gas temperature to deviate between the
cylinders. General cylinder conditions can also be affected if fault is not corrected.
Sugg. Action: Check fuel suction valve, Fuel supply pressure and then ELFI/FIVA main spool stiction.
030116
gls / 14-07-2006 10:31:09 Page 22 of 124
03023313
CCUXX
03023314 Exhaust Valve Timing Controller->Exhaust Valve Opening Too Fast
Description: Exhaust valve takes longer or shorter time to open than the automatically compensation in the control
system is willing to accept.
Cause: Too low or high air spring pressure. Too cold hydraulic supply oil temperature. After having
disassembled the exhaust valve house it can take a few hours before the air spring is fully functioning
again.
Effect: Correct exhaust valve close timing cannot be expected while this alarm is active. This can cause a
compression and maximum pressure that deviates from the desired values.
Sugg. Action: Check cylinder PMI balance, hydraulic supply pressure and air spring.
03023314
gls / 14-07-2006 10:31:09 Page 23 of 124
03031104
CCUXX
03031105 Amplifier->ELFI Amp. Reports Internal Fault
Description: Amplifier for ELFI/FIVA valve has shut down due to too high current consumption by the valve.
Cause: Cabling between CCU and amplifier, cabling from amplifier to valve spool. ELFI pilot spool friction.
Amplifier failure (fuse).
Effect: Injections are stopped since the amplifier cannot deliver the required current before it has been reset.
In case of FIVA exhaust valve operation is also stopped.
Sugg. Action: Inspect entire cabling to and from amplifier. Notice this includes several connections to the CCU and to
the ELFI/FIVA valve. If cabling OK replace CCU, check, replace ELFI/FIVA valve, check and finally
replace amplifier.
03031105
gls / 14-07-2006 10:31:09 Page 24 of 124
030511
CCUXX
0309 Cylinder->Suprv. Ch32,2002,Local: Shut Down
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: Latest valid signal value is used. CCU will shut down when required as long as ECU receives correct
shut down signal from safety system. It will however not stop an already initiated injection if shut down
occurs.
Sugg. Action: Check the cabling and the resistor of the switch. Check the current into terminal "C" of the channel. It
must be within 1 and 18 mA. If it is while the alarm is present, the MPC may be damaged and must be
replaced.
0309
gls / 14-07-2006 10:31:09 Page 25 of 124
200204
CCUXX
2002-04 Ch32,2002-,Shut Down Safety System->Suprv. Ch32,2002-,Shut Down Safety
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: Latest valid signal value is used. CCU will shut down when required as long as ECU receives correct
shut down signal from safety system. It will however not stop an already initiated injection if shut down
occurs.
Sugg. Action: Check the cabling and the resistor of the switch. Check the current into terminal "C" of the channel. It
must be within 1 and 18 mA. If it is while the alarm is present, the MPC may be damaged and must be
replaced.
2002-04
gls / 14-07-2006 10:31:09 Page 26 of 124
411104
CCUXX
411204 Ch27,4112,Leakage->Suprv. Ch27,4112,Leakage
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: Supervision of leakage in high pressure injection pipes is no longer provided.
Sugg. Action: Check the cabling and the resistor of the switch. Check the current into terminal "C" of the channel. It
must be within 1 and 18 mA. If it is while the alarm is present, the MPC may be damaged and must be
replaced.
411204
gls / 14-07-2006 10:31:10 Page 27 of 124
SALOG
CCUXX
SBAT System->Battery Level Low
Description: Onboard battery level low on MPC.
Cause: Battery wears.
Effect: As long as the MPC remains switched on, there is no effect. But if the MPC is switched off or power is
lost, the MPC will loose its time settings.
Sugg. Action: Replace battery.
SBAT
gls / 14-07-2006 10:31:10 Page 28 of 124
SInvSw
CCUXX
SPow24VA 24V power supervision->24V power A failure, connector 1B
Description: The alarm indicates that power inlet, connector 1, terminal B, is powerless.
Cause: The breaker of power supply A for the specified MPC is turned off. 24V power supply A is turned off.
The power cabling is defect.
Effect: No immediate effect, as the MPC is supplied by power supply B.
Sugg. Action: Check for the causes.
SPow24VA
gls / 14-07-2006 10:31:10 Page 29 of 124
SWDogDac
ECUXX
0100601 IO->Ch26,1006, Deviation Supervision (
Description: This value deviates more than allowed from its corresponding value on the redundant MPC. This is the
A/B units.
Cause: Due to too large difference between 2 redundant sensors.
Effect: One of 2 redundant MPCs are getting incorrect sensor readings. Unfortunately it is not 'invalid enough'
for actual sensor alarm and therefore the MPCs will typically have difficulties selecting the most correct
sensor value to use.
Sugg. Action: Verify sensor value from each of the 2 redundant sensors. Compare with a third measurement in order
to determine which of the 2 sensors that is failing. Cut out the failing sensor in order to assist the ECS
with selection of the best value. Cut out sensor via MOP or by actually unplugging the faulty sensor on
the specific MPC.
0100601
gls / 14-07-2006 10:31:10 Page 30 of 124
010114
ECUXX
010115 EICU Commands->Speed Set Locked
Description: Current speed setpoint has been locked due to invalid setpoint signal.
Cause: Electrical problem with speed setpoint from active control station. Problems with status of EICU A&B.
Control network problem.
Effect: While failure exists changes in speed setpoint are only possible by changing active control station.
Sugg. Action: Change active control station for regaining speed set control. Then locate what caused a bad speed
setpoint. Normally other active alarms will indicate where to look.
010115
gls / 14-07-2006 10:31:10 Page 31 of 124
010229
ECUXX
011422 ACUs Feedback->No HPS & blower feedback from ACU1
Description: Commanded control values from commanding MPC cannot be received over the control network.
Cause: Typically caused from a failed MPC. Could also be caused by performance loss on the control network.
Effect: The ECU cannot receive control values from the involved ACU. The control values involves the HPS &
blower operation signals. If the ECU that cannot receive the control values is the Master ECU, then the
HPS & blower control will not operate correctly. If, on the other hand, it is the Slave ECU, then the
engine will continue to operate without changes.
Sugg. Action: Combined with other active alarms this should be used for diagnostics purpose, and thereby as a guide
for finding the actual cause of the problem.
011422
gls / 14-07-2006 10:31:10 Page 32 of 124
011441
ECUXX
011442 ACUs Feedback->Turngear diseng. disagree ACU 1/2
Description: Turning gear disengaged signal disagree on ACU1 and ACU2.
Cause: Turning gear disengaged switch is ON on 1 ACU and OFF on another ACU.
Effect: Could prevent engine from start. Could also allow an engine start when the turning gear is not
disengaged.
Sugg. Action: Care must be taken. Check the turning gear position and position switches before attempting to start
the engine.
011442
gls / 14-07-2006 10:31:10 Page 33 of 124
020102060
ECUXX
02010211 Start/Stop Logic->Running Failed
Description: The engine rpm dropped below acceptable limit for fuel injections. Injections are therefore omitted and
the engine stops.
Cause: During low speed running a sudden torque increase can cause the speed to drop below acceptable
limit.
Effect: Injections are omitted and the engine stops.
Sugg. Action: Start the engine again from the active control station. Typically that reuqire to first order stop and then
a new start. If the engine repeatedly stop with this alarm avoid ordering quite so low engine speed
while strong load torque variation can occur.
02010211
gls / 14-07-2006 10:31:10 Page 34 of 124
020122442
ECUXX
020125J Cylinder Lubrication->Nominel Parameterset not Valid
Description: The ordered Cylinder Lubrication oil amount at MCR can not be supplied. The current parameter set
will cause ECS to demand activation more than one time per revolution, which is not possible.
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, which is one time per
revolution.
Sugg. Action: Check if the parameter set (S%, FeedRateFactor and Adjustfactor) are according to MBD specification.
Check that lubricator size is according to specification and that the parameter "Mass/Injection per
Cylinder" is correct.
020125J
gls / 14-07-2006 10:31:10 Page 35 of 124
020202070
ECUXX
0202020710 Hydraulic Supply Pressure Limiter->Low Hydraulic Pressure Shut Down
Description: Hydraulic pressure is so low that ECS must make shut down in order to avoid damage to hydraulic
accumulators
Cause: A major leakage or faults in the hydraulic power supply
Effect: Shut down is carried out
Sugg. Action: Check for leakages and faults on the hydraulic power supply
020202071
gls / 14-07-2006 10:31:10 Page 36 of 124
100604
ECUXX
100904 Ch33,1009,Local: BackUp Reversing->Suprv. Ch33,1009,Local: BackUp Reve
Description: The input on this channel exceeds allowable limits
Cause: The input on this input channel exceeds allowable limits
Effect: Backup reversing can no longer be ordered from LOP via this ECU.
Sugg. Action:
100904
gls / 14-07-2006 10:31:10 Page 37 of 124
2114-A04
ECUXX
2114-B04 Ch23,2114-B,Local: Air Run->Suprv. Ch23,2114-B,Local: Air Run
Description: The input on this channel exceeds allowable limits
Cause: The input on this input channel exceeds allowable limits
Effect: Air run command can no longer be ordered from LOP via this ECU.
Sugg. Action:
2114-B04
gls / 14-07-2006 10:31:10 Page 38 of 124
2153-B04
ECUXX
2155-A04 Ch30,2155-A,Local: Start->Suprv. Ch30,2155-A,Local: Start
Description: The input on this channel exceeds allowable limits
Cause: The input on this input channel exceeds allowable limits
Effect: Engine start can no longer be ordered from LOP via this ECU.
Sugg. Action:
2155-A04
gls / 14-07-2006 10:31:10 Page 39 of 124
50215
ECUXX
50216 Aux. Blower Command->Insufficient blowers
Description: The number of blowers is insufficient for a normal start of the engine.
Cause: Less than half of the installed blowers are operating.
Effect: The engine is not allowed to be started from Bridge. It can though be started from ECR and LOP, but
care should be taken since the engine will attempt to start even if the blowers will not operate.
Sugg. Action: Check the blower operation control switch at the blower switchboard. The ECS expect the switch to be
in the "Remote" control position. Check the cabling of the signal ID's 8620-x, 8621-x, and 8623-x
between the MPC and the blower switchboard. Check the relays inside the blower switchboard. If all
above seems OK, set the switch in "Off" position and wait a few seconds. Set the switch back in
"Remote" position.
50216
gls / 14-07-2006 10:31:10 Page 40 of 124
50327
ECUXX
51010113 Pump Model Curve->Large dev. from model curve
Description: Large swashplate setpoint deviation from follow-mode pump model curve.
Cause: Can be caused by a hydraulic leak, or mechanical pump fault such as a broken pump shaft.
Effect: In case of a hydraulic leak, all pumps will deliver as much as needed to keep up the pressure. Hence, if
the pumps cannot compensate for the leak, all pumps will swivel their swashplates towards full flow
running AH or AS. In case of a mechanical fault, the non-faulty pumps will try to keep up the pressure
by swivelling their swashplates to values higher than normally needed. If the faulty pump is the
pressure controlling, an automatic change of pressure pump will occur.
Sugg. Action: Inspect the engine driven pumps for mechanical faults, and check for hydraulic leaks and
malfunctioning valves. If this has been investigated without finding any faults, use other alarms to help
analysing the situation for solving the real problem.
51010113
gls / 14-07-2006 10:31:10 Page 41 of 124
510116
ECUXX
510118 Driven Pumps Command->Changing press. ctrl. pump
Description: Automatic change of pressure controlling pump.
Cause: Can be caused by loss of the proportional valve position feedback signal from the proportional valve on
the swashplate pump. Alternatively, by loss of the swashplate position feedback signal. Other causes
are failing proportional valve amplifier and mechanical pump related faults
Effect: The pump will try to swivel its swashplate to deliver full flow in the engine AH direction. Hence, the
pump will most likely deliver more in this fault situation, than during normal situations. In case of
reversing the engine, this pump cannot contribute with flow to the HPS. This corresponds to loss of 1
pump. If a mechanical pump related fault have occurred it is unknown if the pump will contribute at all
with flow to the HPS (e.g. broken pump shaft).
Sugg. Action: Check cabling of power out connector J09 to proportional valve amplifier. Check the cabling of
proportional amplifier OK signal, ID 1224-x. Check the cabling of the proportional valve position
feedback signal, 1238-x, from the LVDT amplifier to the MPC and to the proportional valve. Check the
cabling of the swasplate position feedback signal, ID 1222-x, between the pump and the LVDT
amplifier and from the amplifier to the MPC. Check the cabling of the proportional valve amplifier
enable signal, ID 1223-x, from the MPC to the amplifier. Check the cabling of swashplate command
setpoint signal, ID 1240-x, from the MPC to the proportional valve amplifier. Check the current cabling
from this amplifier to proportional valve. Check the pump and proportional valve for mechanical faults
and replace spare parts if necessary.
510118
gls / 14-07-2006 10:31:10 Page 42 of 124
510131030
ECUXX
51020801 Startup Pumps Command->Startup pump cmd state (Deviation)
Description: This value deviates more than allowed from its corresponding value on the redundant MPC. This is the
A/B units.
Cause: Typically due to deviations between redundant inputs signals to ECS. Input signals from either sensors
or serial connections.
Effect: During this situation smooth control take over between redundant A/B MPC's cannot be guaranteed. In
worst case the engine might stop when control is transferred between 2 redundant MPC's. Control
transfer only occurs in fault situations.
Sugg. Action: Combined with other active alarms this should be used for diagnostics purpose, and thereby as a guide
for finding the actual cause of the problem. If the cause is temporary it typically helps to stop and then
restart the engine.
51020801
gls / 14-07-2006 10:31:10 Page 43 of 124
5115
ECUXX
5116 HPS Command->Hyd. press. sensor ACU 1 deviates
Description: Hydraulic oil pressure sensor (1201-x) on this ACU deviates from the hydraulic oil pressure sensors on
the two other ACUs.
Cause: The sensor is either dead or drifting.
Effect: The ECS will use the two other sensors for hydraulic pressure evaluation. If the sensor is dead and this
ACU controls the pressure controlling pump, the ECS will automatically change pressure controlling
pump. If the sensor is drifting and this ACU is pressure controlling, the ECS will encounter pressure
changes according to the sensor.
Sugg. Action: Make sure this ACU is not controlling the pressure controlling engine driven pump. Follow mode control
is OK. Replace the drifting or dead sensor.
5116
gls / 14-07-2006 10:31:10 Page 44 of 124
5131
ECUXX
51330113 Pump Model Curve->Large dev. from model curve
Description: Large swashplate setpoint deviation from follow-mode pump model curve.
Cause: Can be caused by a hydraulic leak, or mechanical pump fault such as a broken pump shaft.
Effect: In case of a hydraulic leak, all pumps will deliver as much as needed to keep up the pressure. Hence, if
the pumps cannot compensate for the leak, all pumps will swivel their swashplates towards full flow
running AH or AS. In case of a mechanical fault, the non-faulty pumps will try to keep up the pressure
by swivelling their swashplates to values higher than normally needed. If the faulty pump is the
pressure controlling, an automatic change of pressure pump will occur.
Sugg. Action: Inspect the engine driven pumps for mechanical faults, and check for hydraulic leaks and
malfunctioning valves. If this has been investigated without finding any faults, use other alarms to help
analysing the situation for solving the real problem.
51330113
gls / 14-07-2006 10:31:10 Page 45 of 124
513316
ECUXX
513318 El HPS Pump Command->Changing press. ctrl. pump
Description: Automatic change of pressure controlling pump.
Cause: Can be caused by loss of the proportional valve position feedback signal from the proportional valve on
the swashplate pump. Alternatively, by loss of the swashplate position feedback signal. Other causes
are failing proportional valve amplifier and mechanical pump related faults
Effect: The pump will try to swivel its swashplate to deliver full flow in the engine AH direction. Hence, the
pump will most likely deliver more in this fault situation, than during normal situations. In case of
reversing the engine, this pump cannot contribute with flow to the HPS. This corresponds to loss of 1
pump. If a mechanical pump related fault have occurred it is unknown if the pump will contribute at all
with flow to the HPS (e.g. broken pump shaft).
Sugg. Action: Check cabling of power out connector J09 to proportional valve amplifier. Check the cabling of
proportional amplifier OK signal, ID 1224-x. Check the cabling of the proportional valve position
feedback signal, 1238-x, from the LVDT amplifier to the MPC and to the proportional valve. Check the
cabling of the swasplate position feedback signal, ID 1222-x, between the pump and the LVDT
amplifier and from the amplifier to the MPC. Check the cabling of the proportional valve amplifier
enable signal, ID 1223-x, from the MPC to the amplifier. Check the cabling of swashplate command
setpoint signal, ID 1240-x, from the MPC to the proportional valve amplifier. Check the current cabling
from this amplifier to proportional valve. Check the pump and proportional valve for mechanical faults
and replace spare parts if necessary.
513318
gls / 14-07-2006 10:31:10 Page 46 of 124
51333710
ECUXX
5136 HPS Command->P
Description: Pump inlet pressure has reached shutdown level, or hydraulic high pressure has fallen below shutdown
level.
Cause: Lube oil- or hydraulic high- pressure build-up prevented.
Effect: The ECS will carry out a non-cancellable shutdown.
Sugg. Action: Check the lubrication oil supply system for faults (pumps, valves etc.). Check for leaks in the high
pressure system.
5136
gls / 14-07-2006 10:31:10 Page 47 of 124
8601-A04
ECUXX
8601-B04 Ch35,8601-B,Scavenge Air Pressure (->Suprv. Ch35,8601-B,Scavenge Air Pre
Description: The input on this channel exceeds allowable limits
Cause: The input on this input channel exceeds allowable limits
Effect: Scavenge air pressure signal is no longer available. Redundant sensor value is then used (other ECU).
If both sensors fail a model curve is used for controlling compression and maximum pressure.
Sugg. Action: Use PMI equipment to verify compression and maximum pressure while running on model curve.
8601-B04
gls / 14-07-2006 10:31:11 Page 48 of 124
SFuseF9
ECUXX
SInvParm System->Invalid parameters
Description: The MPC holds invalid parameters. The MPC cannot start its application without the correct
parameters.
Cause: The alarm is caused from the MPC automatically loads the wrong parameter set after a replacement of
the MPC.
Effect: The behaviour of the application in the MPC is not correct. The precise effect of this situation is
unknown and care should be taken.
Sugg. Action: If the involved MPC just have been repalced, wait for the automatic preparation to complete. If this
takes more than 10 minutes, the LED colour signalling for fault indication should be inspected. If this
proves unhelpful, reset the MPC unit. If it still does not help, contact MAN B&W Diesel.
SInvParm
gls / 14-07-2006 10:31:11 Page 49 of 124
SWDogDac
EICUXX
010280 ECU Data->No Commands Received from ECU A
Description: Commanded control values from commanding MPC cannot be received over the control network.
Cause: Typically caused from a failed MPC. Could also be caused by performance loss on the control network.
Effect: Except for LOP the control stations are 'frozen'. If both EICU A&B signals alarm for missing ECU A&B
commands it is therefore required to change to LOP for controlling the engine speed
Sugg. Action: Combined with other active alarms this should be used for diagnostics purpose, and thereby as a guide
for finding the actual cause of the problem.
010280
gls / 14-07-2006 10:31:11 Page 50 of 124
0154
EICUXX
0155 I/O Configuration->Lock in Last 'Slow Down Cmd'
Description: The input is invalid, so instead the MPC uses the last valid value.
Cause: The MPC communicated with the surroundings through input variables. The actual input is invalid and
instead the software uses the last valid value.
Effect: The input value is fixed to last valid input and may affect the engine running.
Sugg. Action: Check the input channel / serial connection. It is possible to change to hot standby MPC on the Main
Operation Panel's System screen
0155
gls / 14-07-2006 10:31:11 Page 51 of 124
0161
EICUXX
0162 I/O Configuration->Sensor Fail 'Take Cmd ECR'
Description: Both Force Take ECR input signals on EICUA and EICUB respectively, are failing.
Cause: Bad status on both inputs due to failing switch, broken wires or MPC not running normally.
Effect: There is not Force Take ECR anymore.
Sugg. Action: 1.Check that the MPC is in normal running mode on MOP -> Maintenance screen. If not restart in
normal mode.
2.Check that input signal is okay on MOP -> Maintenance screen. if not rectify failure
0162
gls / 14-07-2006 10:31:11 Page 52 of 124
018401
EICUXX
02012401 Bridge Control Station->Bridge Station State (Deviation)
Description: This value deviates more than allowed from its corresponding value on the redundant MPC. This is the
A/B units.
Cause: Typically due to deviations between redundant inputs signals to ECS. Input signals from either sensors
or serial connections.
Effect: During this situation smooth control take over between redundant A/B MPC's cannot be guaranteed. In
worst case the engine might stop when control is transferred between 2 redundant MPC's. Control
transfer only occurs in fault situations.
Sugg. Action: Combined with other active alarms this should be used for diagnostics purpose, and thereby as a guide
for finding the actual cause of the problem. If the cause is temporary it typically helps to stop and then
restart the engine.
02012401
gls / 14-07-2006 10:31:11 Page 53 of 124
065801
EICUXX
0660 Ctrl Station Selection->No Ctrl Station Selected
Description: None of the manoeuvre places: Bridge, ECR or LOP can be chosen by the RCS.
Cause: Lose of communication between RCS and ECS prevent change of manoeuvre place.
Effect: The ECS retain its manoeuvre place.
Sugg. Action: Change of manouvre place can in this case only be done by a forced take request.
Check the connections between the RCS and the ECS. An often seen follow alarm is "Modbus timeout"
which occure in case of temporar lose of the RCS and ECR communication.
Check that the Blowers are not in Manual mode or Local Mode. If the Blowers are in manual mode
change it back to Automatic mode. If the blowers are in Local mode change it back to remote.
Reattempt a start to see if the problem has disappeared.
If the problem is still present press Prepare start on the MOP to see if the blowers can be started.
If blowers will not start the engine can be started from LOP without blowers running.
0660
gls / 14-07-2006 10:31:11 Page 54 of 124
0669
EICUXX
0670 Ctrl Station Selection->Handle Stop & Stop Switch Deviation
Description: The ECS (Engine Control System) has detected that the Handle Stop position and Stop Switch
Position does not match the expected at the current selected control station.
Cause: The following list exemplifies possible causes of the alarm:
1. Signal error on either Handle or stop switch regardless of Handle Stop and Stop Switch signal.
2. Handle Stop signal is on but Stop Switch signal is off.
3. Handle Stop signal is off but Stop Switch signal is on.
If there is a supervision error rectify the problem and check that the alarm disappears.
If the alarm is still present check that when the handle is in stop position that the stop switch is On
(Main Operating Panel (MOP-A) or Back Up Operating Panel (MOP-B) (see MOP-A/MOP-B ->
Maintenance…-> System View I/O - EICUA and EICUB) J30 or J32 depending on control position). If
both EICU’s stop switches are on check that the Handle Position on the MOP picture “Engine-
>Operation” show 0 RPM. If this is not the case then the handle needs to be rescaled or the Stop
Switch has slipped.
If the problem can not be solved and the engine needs to be started change control station and start
the engine.
0670
gls / 14-07-2006 10:31:11 Page 55 of 124
0752
EICUXX
08023101 Speed Ramp Filter->Speed Ramp SpeedSet (Deviation)
Description: This value deviates more than allowed from its corresponding value on the redundant MPC. This is the
A/B units.
Cause: Typically due to deviations between redundant inputs signals to ECS. Input signals from either sensors
or serial connections.
Effect: During this situation smooth control take over between redundant A/B MPC's cannot be guaranteed. In
worst case the engine might stop when control is transferred between 2 redundant MPC's. Control
transfer only occurs in fault situations.
Sugg. Action: Combined with other active alarms this should be used for diagnostics purpose, and thereby as a guide
for finding the actual cause of the problem. If the cause is temporary it typically helps to stop and then
restart the engine.
NOTE: If a standby request is needed for the ECS then press any forced take commands (pitch back
up mode on Bridge for CPP plants). On the Main Operating Panel (MOP) this results in a Forced
Standby indication.
To generate a FWE request the signals FWE, Standby, At Sea has to work according to specification
(only one signal high at a time).
08023101
gls / 14-07-2006 10:31:11 Page 56 of 124
0931
EICUXX
111101 MOP command interface->Engine Mode Command (Deviation)
Description: This value deviates more than allowed from its corresponding value on the redundant MPC. This is the
A/B units.
Cause: Typically due to deviations between redundant inputs signals to ECS. Input signals from either sensors
or serial connections.
Effect: During this situation smooth control take over between redundant A/B MPC's cannot be guaranteed. In
worst case the engine might stop when control is transferred between 2 redundant MPC's. Control
transfer only occurs in fault situations.
Sugg. Action: Combined with other active alarms this should be used for diagnostics purpose, and thereby as a guide
for finding the actual cause of the problem. If the cause is temporary it typically helps to stop and then
restart the engine.
111101
gls / 14-07-2006 10:31:11 Page 57 of 124
130140
EICUXX
130141 Slow Down Supervision->Cyl 2. No Cylinder lubrication
Description: No cylinder lubrication for the affected cylinder.
Cause: 1) The lubricator or lubrication oil supply system is not working properly.
2) The Cylinder Control Unit is not in normal running mode.
3) The ECS control networks are not connected properly or not working.
Effect: 1) No cylinder lubrication oil is injected to the cylinder
2) Or lubricator sensor feedback signal is failing but lubrication oil is still injected in the cylinder.
3) Slow Down request is send from ECS to Safety System
Sugg. Action: Check Alarmlist for: Failing Lubricator FeedBack, No Cylinder Lube Oil or Cylinder Lube Flow Sensor
fault alarms from the Cylinder Control Unit.
Check on the MOP screen Maintenance: System view I/O Test that the Cylinder Control Unit is up
running. If not, check on the MOP Network Status screen the control network to the Cylinder Control
Unit. The control networks are connected to J65 and J66 on the MPC.
If the alarm is still present try to replace the Cylinder Control Unit MPC.
130141
gls / 14-07-2006 10:31:11 Page 58 of 124
130144
EICUXX
130145 Slow Down Supervision->Cyl 6. No Cylinder lubrication
Description: No cylinder lubrication for the affected cylinder.
Cause: 1) The lubricator or lubrication oil supply system is not working properly.
2) The Cylinder Control Unit is not in normal running mode.
3) The ECS control networks are not connected properly or not working.
Effect: 1) No cylinder lubrication oil is injected to the cylinder
2) Or lubricator sensor feedback signal is failing but lubrication oil is still injected in the cylinder.
3) Slow Down request is send from ECS to Safety System
Sugg. Action: Check Alarmlist for: Failing Lubricator FeedBack, No Cylinder Lube Oil or Cylinder Lube Flow Sensor
fault alarms from the Cylinder Control Unit.
Check on the MOP screen Maintenance: System view I/O Test that the Cylinder Control Unit is up
running. If not, check on the MOP Network Status screen the control network to the Cylinder Control
Unit. The control networks are connected to J65 and J66 on the MPC.
If the alarm is still present try to replace the Cylinder Control Unit MPC.
130145
gls / 14-07-2006 10:31:11 Page 59 of 124
130148
EICUXX
130149 Slow Down Supervision->Cyl 10. No Cylinder lubrication
Description: No cylinder lubrication for the affected cylinder.
Cause: 1) The lubricator or lubrication oil supply system is not working properly.
2) The Cylinder Control Unit is not in normal running mode.
3) The ECS control networks are not connected properly or not working.
Effect: 1) No cylinder lubrication oil is injected to the cylinder
2) Or lubricator sensor feedback signal is failing but lubrication oil is still injected in the cylinder.
3) Slow Down request is send from ECS to Safety System
Sugg. Action: Check Alarmlist for: Failing Lubricator FeedBack, No Cylinder Lube Oil or Cylinder Lube Flow Sensor
fault alarms from the Cylinder Control Unit.
Check on the MOP screen Maintenance: System view I/O Test that the Cylinder Control Unit is up
running. If not, check on the MOP Network Status screen the control network to the Cylinder Control
Unit. The control networks are connected to J65 and J66 on the MPC.
If the alarm is still present try to replace the Cylinder Control Unit MPC.
130149
gls / 14-07-2006 10:31:11 Page 60 of 124
130152
EICUXX
130153 Slow Down Supervision->Cyl 14. No Cylinder lubrication
Description: No cylinder lubrication for the affected cylinder.
Cause: 1) The lubricator or lubrication oil supply system is not working properly.
2) The Cylinder Control Unit is not in normal running mode.
3) The ECS control networks are not connected properly or not working.
Effect: 1) No cylinder lubrication oil is injected to the cylinder
2) Or lubricator sensor feedback signal is failing but lubrication oil is still injected in the cylinder.
3) Slow Down request is send from ECS to Safety System
Sugg. Action: Check Alarmlist for: Failing Lubricator FeedBack, No Cylinder Lube Oil or Cylinder Lube Flow Sensor
fault alarms from the Cylinder Control Unit.
Check on the MOP screen Maintenance: System view I/O Test that the Cylinder Control Unit is up
running. If not, check on the MOP Network Status screen the control network to the Cylinder Control
Unit. The control networks are connected to J65 and J66 on the MPC.
If the alarm is still present try to replace the Cylinder Control Unit MPC.
130153
gls / 14-07-2006 10:31:11 Page 61 of 124
130160
EICUXX
130210 Pump Control Supervision->Hydraulic HP Pump Failed on ACU1
Description: The ECS (Engine Control System) has detected that the HP pump is not working properly.
Cause: The following list exemplifies possible causes of the alarm:
1. The HP pump is failing.
2. The MPC controlling the HP pump might not be in normal mode.
3. The network cables to the MPC is damaged or not connected.
Effect: The swash plate is directed to its fail safe position which is full delivery in Ahead direction. For
manoeuvring in Ahead direction no loss of control will be experienced though higher hydraulic pressure
might be experienced.
Sugg. Action: 1. Look for alarms related to the failing HP pump
2. On MOP screen: Maintenance check that the ACU is operating in normal running mode or check it
by taking a look at LED (Light Emitting Diode) at the top left corner of the MPC. It has to be green.
130210
gls / 14-07-2006 10:31:11 Page 62 of 124
130213
EICUXX
130214 Pump Control Supervision->Hydraulic HP Pump Failed on ECUB
Description: The ECS (Engine Control System) has detected that the HP pump is not working properly.
Cause: The following list exemplifies possible causes of the alarm:
1. The HP pump is failing.
2. The MPC controlling the HP pump might not be in normal mode.
3. The network cables to the MPC is damaged or not connected.
Effect: The swash plate is directed to its fail safe position which is full delivery in Ahead direction. For
manoeuvring in Ahead direction no loss of control will be experienced though higher hydraulic pressure
might be experienced.
Sugg. Action: 1. Look for alarms related to the failing HP pump
2. On MOP screen: Maintenance check that the ECU is operating in normal running mode or check it
by taking a look at LED (Light Emitting Diode) at the top left corner of the MPC. It has to be green.
130214
gls / 14-07-2006 10:31:11 Page 63 of 124
214001
EICUXX
2140-A04 Ch27,2140-A,Speed Set ECR->Suprv. Ch27,2140-A,Speed Set ECR
Description: The alarm indicates that the signal from the sensor connected to the specified channel is outside the
legal range. The sensor should give a signal between 4 mA to 20 mA.
Cause: Most probably a failure in the cabling to the sensor, or
failure of the sensor, or missing sensor power supply, or
failure of the input of the MPC.
Effect: If there is redundant cabling to the redundant EICU:
the engine running is not affected. The corresponding input on the redundant EICU is used on both
EICU's.
2140-A04
gls / 14-07-2006 10:31:11 Page 64 of 124
2141-A04
EICUXX
2141-B04 Ch32,2141-B,Stop Cmd ECR->Suprv. Ch32,2141-B,Stop Cmd ECR
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: If there is redundant cabling to the redundant EICU:
The corresponding input on the redundant EICU is used on both EICU's.
2141-B04
gls / 14-07-2006 10:31:11 Page 65 of 124
2143-A04
EICUXX
2143-B04 Ch34,2143-B,Take command ECR->Suprv. Ch34,2143-B,Take command ECR
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: If there is redundant cabling to the redundant EICU:
The corresponding input on the redundant EICU is used on both EICU's.
2143-B04
gls / 14-07-2006 10:31:11 Page 66 of 124
2145-A04
EICUXX
2145-B04 Ch33,2145-B,Start Cmd ECR->Suprv. Ch33,2145-B,Start Cmd ECR
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: If there is redundant cabling to the redundant EICU:
The corresponding input on the redundant EICU is used on both EICU's.
2145-B04
gls / 14-07-2006 10:31:11 Page 67 of 124
2149-A04
EICUXX
2149-B04 Ch37,2149-B,Aux. System Ready->Suprv. Ch37,2149-B,Aux. System Read
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: Reduced supervision quality. Redundancy lost.
Sugg. Action: Check the cabling and the resistor of the switch. Check the current into terminal "C" of the channel. It
must be within 1 and 18 mA. If it is while the alarm is present, the MPC may be damaged and must be
replaced.
2149-B04
gls / 14-07-2006 10:31:11 Page 68 of 124
2160-A04
EICUXX
2160-B04 Ch26,2160-B,Speed Set Bridge->Suprv. Ch26,2160-B,Speed Set Bridge
Description: The alarm indicates that the signal from the sensor connected to the specified channel is outside the
legal range. The sensor should give a signal between 4 mA to 20 mA.
Cause: Most probably a failure in the cabling to the sensor, or
failure of the sensor, or missing sensor power supply, or
failure of the input of the MPC.
Effect: If there is redundant cabling to the redundant EICU:
the engine running is not affected. The corresponding input on the redundant EICU is used on both
EICU's.
2160-B04
gls / 14-07-2006 10:31:12 Page 69 of 124
2162-A04
EICUXX
2162-B04 Ch22,2162-B,Increase Limiter from B->Suprv. Ch22,2162-B,Increase Limiter
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: If there is redundant cabling to the redundant EICU:
The corresponding input on the redundant EICU is used on both EICU's.
2162-B04
gls / 14-07-2006 10:31:12 Page 70 of 124
2164-A04
EICUXX
2164-B04 Ch21,2164-B,Restart switch->Suprv. Ch21,2164-B,Restart switch
Description: The alarm indicates that the signal from the switch connected to the specified channel is outside the
legal range. The cabling and the connection to the switch are supervised by mean of a 6.8kOhm
resistor that is mounted across the switch.
Cause: Most probably a failure in the cabling to the switch, or
missing supervision resistor across the switch, or failure of the input of the MPC.
Effect: If there is redundant cabling to the redundant EICU:
The corresponding input on the redundant EICU is used on both EICU's.
2164-B04
gls / 14-07-2006 10:31:12 Page 71 of 124
216P-A04
EICUXX
216P-B04 Ch26,216P-B,Potentiometer Speed Set->Suprv. Ch26,216P-B,Potentiometer Sp
Description:
Cause:
Effect: If there is redundant cabling to the redundant EICU:
the engine running is not affected. The corresponding input on the redundant EICU is used on both
EICU's.
216P-B04
gls / 14-07-2006 10:31:12 Page 72 of 124
ModbusTA
EICUXX
RCSVarAA IO Variant A->RCS communication failure
Description: The communication between the EICU and the remote control system (RCS) is failing.
Cause: See the description of the "RCS communication failure" (ID:EICU*-SMBsTOAl) alarm if this is also
raised.
Otherwise there is a malfunction in the RCS.
During commissioning a EICU wrong parameter configuration in the EICU may also cause this problem.
Effect: If this alarm comes from both EICUs at the same time then serial communication between the RCS
and ECS has been lost. Only hardwired control and monitoring will work.
Sugg. Action: Restart the RCS.
RCSVarAA
gls / 14-07-2006 10:31:12 Page 73 of 124
SAR-ACU3
EICUXX
SAR-ACU4 System Status->App. not running on ACU4
Description: The specified MPC is not properly executing its application program. The EICU's monitor execution of
the application programs on all MPCs . The EICU raises this alarm when it detects that the specified
MPC is not executing the application program correctly. Since there are two EICU's in the system,
these alarms will normally occur two by two.
Cause: The alarm comes shortly after power up of an MPC, which is normal. The alarm occurs just after
replacement of an MPC unit. The alarm should return to normal after the automatic preparation of a
replacement MPC has completed. The alarm is present while the MPC is in any test mode.
Effect: The MPC does not control the tasks that it is meant to.
Example: "App. not running on CCU1" means that cylinder 1 can not operate.
Sugg. Action: If the observed MPC has just been replaced, wait for the automatic preparation to complete. If this
takes more than ten minutes, look at the LED lamp of the MPC to see if it shows a failure code. . If this
proves unhelpful, reset the MPC unit.
SAR-ACU4
gls / 14-07-2006 10:31:12 Page 74 of 124
SAR-CCU1
EICUXX
SAR-CCU11 System Status->App. not running on CCU11
Description: The specified MPC is not properly executing its application program. The EICU's monitor execution of
the application programs on all MPCs . The EICU raises this alarm when it detects that the specified
MPC is not executing the application program correctly. Since there are two EICU's in the system,
these alarms will normally occur two by two.
Cause: The alarm comes shortly after power up of an MPC, which is normal. The alarm occurs just after
replacement of an MPC unit. The alarm should return to normal after the automatic preparation of a
replacement MPC has completed. The alarm is present while the MPC is in any test mode.
Effect: The MPC does not control the tasks that it is meant to.
Example: "App. not running on CCU1" means that cylinder 1 can not operate.
Sugg. Action: If the observed MPC has just been replaced, wait for the automatic preparation to complete. If this
takes more than ten minutes, look at the LED lamp of the MPC to see if it shows a failure code. . If this
proves unhelpful, reset the MPC unit.
SAR-CCU1
gls / 14-07-2006 10:31:12 Page 75 of 124
SAR-CCU1
EICUXX
SAR-CCU15 System Status->App. not running on CCU15
Description: The specified MPC is not properly executing its application program. The EICU's monitor execution of
the application programs on all MPCs . The EICU raises this alarm when it detects that the specified
MPC is not executing the application program correctly. Since there are two EICU's in the system,
these alarms will normally occur two by two.
Cause: The alarm comes shortly after power up of an MPC, which is normal. The alarm occurs just after
replacement of an MPC unit. The alarm should return to normal after the automatic preparation of a
replacement MPC has completed. The alarm is present while the MPC is in any test mode.
Effect: The MPC does not control the tasks that it is meant to.
Example: "App. not running on CCU1" means that cylinder 1 can not operate.
Sugg. Action: If the observed MPC has just been replaced, wait for the automatic preparation to complete. If this
takes more than ten minutes, look at the LED lamp of the MPC to see if it shows a failure code. . If this
proves unhelpful, reset the MPC unit.
SAR-CCU1
gls / 14-07-2006 10:31:12 Page 76 of 124
SAR-CCU3
EICUXX
SAR-CCU4 System Status->App. not running on CCU4
Description: The specified MPC is not properly executing its application program. The EICU's monitor execution of
the application programs on all MPCs . The EICU raises this alarm when it detects that the specified
MPC is not executing the application program correctly. Since there are two EICU's in the system,
these alarms will normally occur two by two.
Cause: The alarm comes shortly after power up of an MPC, which is normal. The alarm occurs just after
replacement of an MPC unit. The alarm should return to normal after the automatic preparation of a
replacement MPC has completed. The alarm is present while the MPC is in any test mode.
Effect: The MPC does not control the tasks that it is meant to.
Example: "App. not running on CCU1" means that cylinder 1 can not operate.
Sugg. Action: If the observed MPC has just been replaced, wait for the automatic preparation to complete. If this
takes more than ten minutes, look at the LED lamp of the MPC to see if it shows a failure code. . If this
proves unhelpful, reset the MPC unit.
SAR-CCU4
gls / 14-07-2006 10:31:12 Page 77 of 124
SAR-CCU7
EICUXX
SAR-CCU8 System Status->App. not running on CCU8
Description: The specified MPC is not properly executing its application program. The EICU's monitor execution of
the application programs on all MPCs . The EICU raises this alarm when it detects that the specified
MPC is not executing the application program correctly. Since there are two EICU's in the system,
these alarms will normally occur two by two.
Cause: The alarm comes shortly after power up of an MPC, which is normal. The alarm occurs just after
replacement of an MPC unit. The alarm should return to normal after the automatic preparation of a
replacement MPC has completed. The alarm is present while the MPC is in any test mode.
Effect: The MPC does not control the tasks that it is meant to.
Example: "App. not running on CCU1" means that cylinder 1 can not operate.
Sugg. Action: If the observed MPC has just been replaced, wait for the automatic preparation to complete. If this
takes more than ten minutes, look at the LED lamp of the MPC to see if it shows a failure code. . If this
proves unhelpful, reset the MPC unit.
SAR-CCU8
gls / 14-07-2006 10:31:12 Page 78 of 124
SAR-ECUB
EICUXX
SAR-EICUA System Status->App. not running on EICUA
Description: The specified MPC is not properly executing its application program. The EICU's monitor execution of
the application programs on all MPCs . The EICU raises this alarm when it detects that the specified
MPC is not executing the application program correctly. Since there are two EICU's in the system,
these alarms will normally occur two by two.
Cause: The alarm comes shortly after power up of an MPC, which is normal. The alarm occurs just after
replacement of an MPC unit. The alarm should return to normal after the automatic preparation of a
replacement MPC has completed. The alarm is present while the MPC is in any test mode.
Effect: The MPC does not control the tasks that it is meant to.
Example: "App. not running on CCU1" means that cylinder 1 can not operate.
Sugg. Action: If the observed MPC has just been replaced, wait for the automatic preparation to complete. If this
takes more than ten minutes, look at the LED lamp of the MPC to see if it shows a failure code. . If this
proves unhelpful, reset the MPC unit.
SAR-EICU
gls / 14-07-2006 10:31:12 Page 79 of 124
SEICU
EICUXX
SFuseF12 24V power supervision->Fuse F12 failure
Description: The alarm indicates that Fuse 12 of the specified MPC is blown. Fuse 12 protects the sensor power
supply, terminal "D", of the analog 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 have occurred at the same time.
Sugg. Action: Check for possible failures in the external cabling to channels 20 to 37. Replace the fuse.
SFuseF12
gls / 14-07-2006 10:31:12 Page 80 of 124
SInvSw
EICUXX
SMBsTOAl RCS Interface->RCS serial communication fail
Description: The EICU is not receiving data from the remote control system (RCS).
Cause: This alarm is probably caused by a fault in the serial modbus cable connection between the RCS and
the EICU.
During commissioning a EICU parameter misconfiguration in the EICU may also cause this problem.
Other causes may be a malfunction in the RCS or EICU.
Effect: If this alarm comes from both EICUs at the same time then serial communication between the RCS
and ECS has been lost. Only hardwired control and monitoring will work.
Sugg. Action: If both EICU's has this alarm first check the RCS for power loss or other malfunction. Otherwise follow
check list below.
Check list:
1) Check Serial Cabel and connector J68 on EICU
2) Check connection on RCS side
3) If possible switch connector J68 on EICUA and EICUB to see if it follows the connector or stays at
the same EICU
4) If communication failure alarm is still active from the same EICU when performing test 3), try replace
the failing EICU with spare MPC.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SMBsTOAl
gls / 14-07-2006 10:31:12 Page 81 of 124
SN0-ACU1
EICUXX
SN0-ACU2 System Status->Net A not connected to ACU2
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-ACU2
gls / 14-07-2006 10:31:12 Page 82 of 124
SN0-ACU3
EICUXX
SN0-ACU4 System Status->Net A not connected to ACU4
Description: The controlling unit is not connected to network segment 0.
Cause: Defective network connection or cabling. A MPC is out of function. Failure in the network electronics of
a unit.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-ACU4
gls / 14-07-2006 10:31:12 Page 83 of 124
SN0-ACU4
EICUXX
SN0-AXU1 System Status->Net A not connected to AXU1
Description: The controlling unit is not connected to network segment 0.
Cause: Defective network connection or cabling. A MPC is out of function. Failure in the network electronics of
a unit.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-AXU1
gls / 14-07-2006 10:31:12 Page 84 of 124
SN0-AXU1
EICUXX
SN0-CCU1 System Status->Net A not connected to CCU1
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-CCU1
gls / 14-07-2006 10:31:12 Page 85 of 124
SN0-CCU1
EICUXX
SN0-CCU11 System Status->Net A not connected to CCU11
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-CCU1
gls / 14-07-2006 10:31:12 Page 86 of 124
SN0-CCU1
EICUXX
SN0-CCU13 System Status->Net A not connected to CCU13
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-CCU1
gls / 14-07-2006 10:31:12 Page 87 of 124
SN0-CCU1
EICUXX
SN0-CCU15 System Status->Net A not connected to CCU15
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-CCU1
gls / 14-07-2006 10:31:12 Page 88 of 124
SN0-CCU1
EICUXX
SN0-CCU2 System Status->Net A not connected to CCU2
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-CCU2
gls / 14-07-2006 10:31:12 Page 89 of 124
SN0-CCU3
EICUXX
SN0-CCU4 System Status->Net A not connected to CCU4
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-CCU4
gls / 14-07-2006 10:31:12 Page 90 of 124
SN0-CCU5
EICUXX
SN0-CCU6 System Status->Net A not connected to CCU6
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-CCU6
gls / 14-07-2006 10:31:13 Page 91 of 124
SN0-CCU7
EICUXX
SN0-CCU8 System Status->Net A not connected to CCU8
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-CCU8
gls / 14-07-2006 10:31:13 Page 92 of 124
SN0-CCU9
EICUXX
SN0-ECUA System Status->Net A not connected to ECUA
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-ECUA
gls / 14-07-2006 10:31:13 Page 93 of 124
SN0-ECUB
EICUXX
SN0-EICUA System Status->Net A not connected to EICUA
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-EICU
gls / 14-07-2006 10:31:13 Page 94 of 124
SN0-EICU
EICUXX
SN0-ESU System Status->Net A not connected to ESU
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-ESU
gls / 14-07-2006 10:31:13 Page 95 of 124
SN0-MOP
EICUXX
SN0-MOPB System Status->Net A not connected to MOPB
Description: The controlling unit is not connected to network segment 0.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN0-MOP
gls / 14-07-2006 10:31:13 Page 96 of 124
SN1-ACU1
EICUXX
SN1-ACU2 System Status->Net B not connected to ACU2
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-ACU2
gls / 14-07-2006 10:31:13 Page 97 of 124
SN1-ACU3
EICUXX
SN1-ACU4 System Status->Net B not connected to ACU4
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-ACU4
gls / 14-07-2006 10:31:13 Page 98 of 124
SN1-AXU1
EICUXX
SN1-CCU1 System Status->Net B not connected to CCU1
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-CCU1
gls / 14-07-2006 10:31:13 Page 99 of 124
SN1-CCU1
EICUXX
SN1-CCU11 System Status->Net B not connected to CCU11
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-CCU1
gls / 14-07-2006 10:31:13 Page 100 of 124
SN1-CCU1
EICUXX
SN1-CCU13 System Status->Net B not connected to CCU13
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-CCU1
gls / 14-07-2006 10:31:13 Page 101 of 124
SN1-CCU1
EICUXX
SN1-CCU15 System Status->Net B not connected to CCU15
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-CCU1
gls / 14-07-2006 10:31:13 Page 102 of 124
SN1-CCU1
EICUXX
SN1-CCU2 System Status->Net B not connected to CCU2
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-CCU2
gls / 14-07-2006 10:31:13 Page 103 of 124
SN1-CCU3
EICUXX
SN1-CCU4 System Status->Net B not connected to CCU4
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-CCU4
gls / 14-07-2006 10:31:13 Page 104 of 124
SN1-CCU5
EICUXX
SN1-CCU6 System Status->Net B not connected to CCU6
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-CCU6
gls / 14-07-2006 10:31:13 Page 105 of 124
SN1-CCU7
EICUXX
SN1-CCU8 System Status->Net B not connected to CCU8
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-CCU8
gls / 14-07-2006 10:31:13 Page 106 of 124
SN1-CCU9
EICUXX
SN1-ECUA System Status->Net B not connected to ECUA
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-ECUA
gls / 14-07-2006 10:31:13 Page 107 of 124
SN1-ECUB
EICUXX
SN1-EICUA System Status->Net B not connected to EICUA
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-EICU
gls / 14-07-2006 10:31:13 Page 108 of 124
SN1-EICU
EICUXX
SN1-ESU System Status->Net B not connected to ESU
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-ESU
gls / 14-07-2006 10:31:13 Page 109 of 124
SN1-MOP
EICUXX
SN1-MOPB System Status->Net B not connected to MOPB
Description: The controlling unit is not connected to network segment 1.
Cause: This is normally caused by network cabling problems.
Effect: When only an alarm related to one network segment is raised, there is no change in engine behaviour.
But if both network segment 0 and 1 is affected, the controlling unit is not operating correctly or not
operating at all.
Sugg. Action: If alarm(s) indicates missing connection to one network segment on one MPC:
1) Check if the network connector is mounted on the unit.
2) Replace the network connector.
3) If no problems can be found in the network connection, replace the unit.
If alarms indicates 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, it must be checked for power failure. Otherwise:
MPC-1) If the indicator LED lamp of the MPC is green, check the network connections and connectors
of the unit for cabling failures.
MPC-2) Restart the controller, e.g. by turn off – turn on of the power.
MPC-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 the MPC.
MOP-1) If the display of the MOP is active with normal application pictures, though with missing
process values: Check the network connections and connectors of the unit for cabling failures.
MOP-2) Restart the MOP, e.g. by turn off – turn on of the power. If the MOP does not start up ending
up with application pictures, and the network alarm does not disappear, it must be repaired.
If alarms indicates 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) A loose network termination resistor. 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) A damaged network cable.
SN1-MOP
gls / 14-07-2006 10:31:14 Page 110 of 124
SNA-ACU1
EICUXX
SNA-ACU2 System Status->MPC ACU2 unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-ACU2
gls / 14-07-2006 10:31:14 Page 111 of 124
SNA-ACU3
EICUXX
SNA-ACU4 System Status->MPC ACU4 unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-ACU4
gls / 14-07-2006 10:31:14 Page 112 of 124
SNA-AXU1
EICUXX
SNA-CCU1 System Status->MPC CCU1 unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-CCU1
gls / 14-07-2006 10:31:14 Page 113 of 124
SNA-CCU1
EICUXX
SNA-CCU11 System Status->MPC CCU11 unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-CCU1
gls / 14-07-2006 10:31:14 Page 114 of 124
SNA-CCU1
EICUXX
SNA-CCU13 System Status->MPC CCU13 unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-CCU1
gls / 14-07-2006 10:31:14 Page 115 of 124
SNA-CCU1
EICUXX
SNA-CCU15 System Status->MPC CCU15 unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-CCU1
gls / 14-07-2006 10:31:14 Page 116 of 124
SNA-CCU1
EICUXX
SNA-CCU2 System Status->MPC CCU2 unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-CCU2
gls / 14-07-2006 10:31:14 Page 117 of 124
SNA-CCU3
EICUXX
SNA-CCU4 System Status->MPC CCU4 unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-CCU4
gls / 14-07-2006 10:31:14 Page 118 of 124
SNA-CCU5
EICUXX
SNA-CCU6 System Status->MPC CCU6 unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-CCU6
gls / 14-07-2006 10:31:14 Page 119 of 124
SNA-CCU7
EICUXX
SNA-CCU8 System Status->MPC CCU8 unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-CCU8
gls / 14-07-2006 10:31:14 Page 120 of 124
SNA-CCU9
EICUXX
SNA-ECUA System Status->MPC ECUA unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-ECU
gls / 14-07-2006 10:31:14 Page 121 of 124
SNA-ECUB
EICUXX
SNA-EICUA System Status->MPC EICUA unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-EICU
gls / 14-07-2006 10:31:14 Page 122 of 124
SNA-EICU
EICUXX
SNA-ESU System Status->MPC ESU unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
SNA-ESU
gls / 14-07-2006 10:31:14 Page 123 of 124
SNA-MOP
EICUXX
SNA-MOPB System Status->MPC MOPB unavailable
Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICU’s. Special
case: One of the EICU’s are disconnected both control network results in alarms form this EICU that all
other MPC’s are unavailable.
Cause: The following list exemplifies possible causes of the alarm:
1. The MPC is not in a normal running mode.
2. There is no power to the unit.
3. The network cables are disconnected from the unit (MPC’s connector J65 and J66 )
4. The network cables to the unit are damaged.
Effect: If one or two MOP’s are missing on the network it will not affect the running of the engine.
For redundant units i.e. EICU’s and ECU’s:
The redundant unit takes over and engine operation is not affected.
If a CCU is disconnected the network:
Fuel injection is stopped immediately and exhaust valve operation will stop after few seconds. If the
CCU is powered down or not in normal running mode fuel injection and exhaust valve operation stops
immediately.
If network is disconnected to an ACU:
The engine driven pump will go to 100% delivery and startup pump and blower controlled by the unit
remain unchanged i.e. either stopped or running.
If an ACU is powered down or not in normal running mode the engine driven pump will go to 100%
delivery and startup pump and blower will stop.
Sugg. Action: If the alarm is either about MOP-A or MOP-B make sure that the unit is turned on and that the control
network is properly connected.
The Network Status Screen wil indicate which Nodes are affected/cross connected. Go to the MPC's
and check cabling.
SNA-MOP
gls / 14-07-2006 10:31:14 Page 124 of 124
SWDogDac