Alarms Reference

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 010106 ECU Commands->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: This will force the ACU to accept commanded control values from the redundant ECU. These control values involves the HPS and the blower control. If there is no alarm for missing telegrams from the redundant ECU, there would normally not be any change in engine behaviour. If, on the other hand, alarms are claiming that both control commands from ECU A and ECU B are missing, then the ACU cannot receive new control commands from the ECUs 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. 010107 ECU Commands->No Commands Received from ECU B

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: This will force the ACU to accept commanded control values from the redundant ECU. These control values involves the HPS and the blower control. If there is no alarm for missing telegrams from the redundant ECU, there would normally not be any change in engine behaviour. If, on the other hand, alarms are claiming that both control commands from ECU A and ECU B are missing, then the ACU cannot receive new control commands from the ECUs 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. 010110 I/O Configuration->ACU Comman

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: This will force the ACU to accept commanded control values from the redundant ECU. These control values involves the HPS and the blower control. If there is no alarm for missing telegrams from the redundant ECU, there would normally not be any change in engine behaviour. If, on the other hand, alarms are claiming that both control commands from ECU A and ECU B are missing, then the ACU cannot receive new control commands from the ECUs 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. 010111 I/O Configuration->ACU Comman

Description: Commanded control values from commanding MPC cannot be received over the control network. Cause: Typically due to deviations between redundant inputs signals to ECS. Input signals from either sensors or serial connections. Effect: This will force the ACU to accept commanded control values from the redundant ECU. These control values involves the HPS and the blower control. If there is no alarm for missing telegrams from the redundant ECU, there would normally not be any change in engine behaviour. If, on the other hand, alarms are claiming that both control commands from ECU A and ECU B are missing, then the ACU cannot receive new control commands from the ECUs 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. 02020104 Amplifier->Bypass Amp. Current Supervision

Description: Amplifier Current for bypass valve not within range Cause: Amplifier failure Effect: Bypass controll is not possible Sugg. Action: Check cabling and fuse of amplifier

009904 02020104

gls / 14-07-2006 10:31:06

Page 1 of 124

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. 020281 Var. Bypass->Var. Byp. Travel Feedback failed

Description: The Travel Feedback signal was not received. Cause: Failure in Wiring or variable bypass encoder. 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. If the problem is not resolved, Change to manual control. 020282 Var. Bypass->Var. Byp. Pot. signal failed

Description: Potentionmeter encoder signal from the variable bypass valve is sick. Cause: Failure in Wiring or variable bypass encoder. 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. If the problem is not resolved, Change to manual control. 020283 Var. Bypass->Var. Byp. Open switch failed

Description: Open 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. If the problem is not resolved, Change to manual control.

02020105 020283

gls / 14-07-2006 10:31:08

Page 2 of 124

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. If the problem is not resolved, Change to manual control. 0210 Blower Ctrl. 1->Blower 1 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. 0281 Gas Bypass->On/Off Bypass Control Failure Description: Unspecified control failure of the bypass system. Cause: Variable Bypass or On/Off bypass components defect or wrong adjustment 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. If the problem is not resolved, Change to manual control. 0282 Gas Bypass->ECU Command Failed Description: ECU command is not valid. Cause: ECU malfunction or no connection to ECU 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. If the problem is not resolved, Change to manual control. 0283 Gas Bypass->Bypass Manual Description: Bypass system is in manual mode. Cause: Bypass changed into manual mode Effect: Bypass Valve may be controlled manually Sugg. Action: Change to Automatic when finished manual operation

020284 0283

gls / 14-07-2006 10:31:08

Page 3 of 124

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. 0410 Blower Ctrl. 3->Blower 3 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. 0510 Blower Ctrl. 4->Blower 4 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. 0610 Blower Ctrl. 5->Blower 5 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 0610

gls / 14-07-2006 10:31:08

Page 4 of 124

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. 07013604 Amplifier->PV_AMP Amp. Current Supervision

Description: This alarm is not in use Cause: This alarm is not in use Effect: This alarm is not in use Sugg. Action: This alarm is not in use. If you see this, please contact MAN B&W Diesel 07013605 Amplifier->PV_AMP Amp. Reports Internal Fault

Description: Amplifier for swashplate pump proportional valve has shut down due to too high current consumption by the valve Cause: Cabling between ACU and amplifier, cabling from amplifier to proportional valve. Proportional valve spool friction. Amplifier failure (fuse). 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. 07013910 El motor->Pump motor ctrl failed

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 el. motor operation control switch at the el. motor switchboard. The ECS expect the switch to be in the "Remote" control position. Check the cabling of the signal ID's 1217-x, 1218-x, and 1219-x between the MPC and the el. motor switchboard. Check the relays inside the switchboard. If all above seems OK, set the switch in "Off" position and wait a few seconds. Set the switch back in "Remote" position. 070210 Hydraulic Power Supply->Start

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 startup pump operation control switch at the startup pump switchboard. The ECS expect the switch to be in the "Remote" control position. Check the cabling of the signal ID's 1210-x, 1212-x, and 1213-x between the MPC and the startup pump switchboard. Check the relays inside the startup pump switchboard. 070119 070210

gls / 14-07-2006 10:31:08

Page 5 of 124

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. 0708 Hydraulic Power Supply->Hydra Description: Major leakage from the drip pan below the HPS is detected. Cause: A major hydraulic leakage from one or more engine driven swashplate pumps and/or the startup pump sets is detected by the leakage sensor, ID 1236. Effect: The ECS will generate an engine shutdown request (cancellable) to the safety-system. Sugg. Action: Find and repair the cause to the hydraulic leak. 0709 Hydraulic Power Supply->Low inlet pump 4 pressure Description: Lubrication oil pressure is too low. Cause: Lube oil- or hydraulic high- pressure build-up prevented. Effect: No effect. Sugg. Action: Check the lubrication oil supply system for faults (pumps, valves etc.). Check for leaks in the high pressure system. 0710 Hydraulic Power Supply->Low inlet pump 5 pressure Description: Lubrication oil pressure is too low. Cause: Lube oil- or hydraulic high- pressure build-up prevented. Effect: No effect. Sugg. Action: Check the lubrication oil supply system for faults (pumps, valves etc.). Check for leaks in the high pressure system. 0711 Hydraulic Power Supply->Inlet pump 4 pressure deviation Description: Lubrication oil pressure sensor (1204-x) on this ACU deviates from the lubrication oil pressure sensors on the two other ACUs. Cause: The sensor is either dead, is drifting, or the valve before the inlet to the engine driven pump is closed. Effect: The ECS will use the two other sensors for lubrication pressure evaluation. If the valve for lubrication oil inlet to the engine driven pump is closed, there is a risk that the pump will cavitate if the fault is not corrected before engine start. Sugg. Action: Check the sensors to find the drifting sensor and replace the faulty sensor. 0712 Hydraulic Power Supply->Inlet pump 5 pressure deviation Description: Lubrication oil pressure sensor (1204-x) on this ACU deviates from the lubrication oil pressure sensors on the two other ACUs. Cause: The sensor is either dead, is drifting, or the valve before the inlet to the engine driven pump is closed. Effect: The ECS will use the two other sensors for lubrication pressure evaluation. If the valve for lubrication oil inlet to the engine driven pump is closed, there is a risk that the pump will cavitate if the fault is not corrected before engine start. Sugg. Action: Check the sensors to find the drifting sensor and replace the faulty sensor. 0719 Hydraulic Power Supply->Doubl Description: Double pipe leak. Cause: Flow is detected in the outer pipe. Effect: There is a leak from the inner pipe to the outer pipe. Sugg. Action: Search and repair the hydraulic leak. Check seals in double pipe, valves (e.g. pos. 333).

0706 0719

gls / 14-07-2006 10:31:08

Page 6 of 124

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. 0724 Hydraulic Power Supply->Doubl Description: Double pipe pressure high. Cause: Pressure has been detected in the outer pipe of the double pipe. Effect: There is a leak from the inner pipe to the outer pipe. Sugg. Action: Search and repair the hydraulic leak. Check seals in double pipe, valves (e.g. pos. 333). 0725 Hydraulic Power Supply->Double pipe press. low Description: Double pipe pressure low. Cause: Pressure lower than specified has been detected in the outer pipe of the double pipe. Effect: Too low pressure in outer pipe of double pipe construction Sugg. Action: Check valve 333 in the accumulator block. Check valve 431, drain valve from double pipe, on the HCUs. 1109-304 I/O Configuration->Ch23,1109-

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. 1109-A04 I/O Configuration->Ch23,1109-

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. 1109-B04 I/O Configuration->Ch23,1109-

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.

0722 1109-B04

gls / 14-07-2006 10:31:09

Page 7 of 124

ACUXX
1110-304 I/O Configuration->Ch22,1110Description: 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-A04 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-B04 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. 1111-304 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-A04 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.

1110-304 1111-A04

gls / 14-07-2006 10:31:09

Page 8 of 124

ACUXX
1111-B04 I/O Configuration->Ch21,1111Description: 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. 1112-304 I/O Configuration->Ch24,1112-

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. 1112-A04 I/O Configuration->Ch24,1112-

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. 1112-B04 I/O Configuration->Ch24,1112-

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-304 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.

1111-B04 1116-304

gls / 14-07-2006 10:31:09

Page 9 of 124

ACUXX
1116-A04 I/O Configuration->Ch25,1116Description: 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-B04 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. 1201-104 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-204 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.

1116-A04 1201-204

gls / 14-07-2006 10:31:09

Page 10 of 124

ACUXX
1201-304 I/O Configuration->Ch31,1201Description: 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. 1202-A03 I/O Configuration->Ch80,1202-

Description: The alarm indicates that the supervision current for supervision of the cabling and connection is outside the legal range. The specified channel has a relay contact for activation of a component. The current to the component is too passing an input channel for supervision, and the signal measured by this channel is outside the legal range. Cause: Most probably: A failure in the cabling to the component. A blown fuse in the supply plug. Failure of the output or input of the MPC. Effect: Reduced supervision quality. Redundancy lost. Sugg. Action: Check the cabling to the component, according to the installation drawings. Check that the voltage of the power connector is 24V. If not, the fuse may be blown. Check that there is current in the cable to the coil. Check the operation of the relay contact is correct. Check that the controlled component gets the 24V signal and functions correctly. If the function is OK and the supervision current is present, while the alarm is present, the MPC may be damaged and must be replaced. 1202-B03 I/O Configuration->Ch80,1202-

Description: The alarm indicates that the supervision current for supervision of the cabling and connection is outside the legal range. The specified channel has a relay contact for activation of a component. The current to the component is too passing an input channel for supervision, and the signal measured by this channel is outside the legal range. Cause: Most probably: A failure in the cabling to the component. A blown fuse in the supply plug. Failure of the output or input of the MPC. Effect: Reduced supervision quality. Redundancy lost. Sugg. Action: Check the cabling to the component, according to the installation drawings. Check that the voltage of the power connector is 24V. If not, the fuse may be blown. Check that there is current in the cable to the coil. Check the operation of the relay contact is correct. Check that the controlled component gets the 24V signal and functions correctly. If the function is OK and the supervision current is present, while the alarm is present, the MPC may be damaged and must be replaced. 1204-104 Ch32,1204-1,Lube oil pressure (bar)->Suprv. Ch32,1204-1,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. 1201-304 1204-104 gls / 14-07-2006 10:31:09 Page 11 of 124

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-304 Ch32,1204-3,Lube oil pressure (bar)->Suprv. Ch32,1204-3,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-404 Ch33,1204-4,Lube oil pressure, pump->Suprv. Ch33,1204-4,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: Supervision of pump inlet pressure is missing. Make sure that the pump has inlet oil supply. 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-504 Ch33,1204-5,Lube oil pressure, pump->Suprv. Ch33,1204-5,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: Supervision of pump inlet pressure is missing. Make sure that the pump has inlet oil supply. 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 1204-504

gls / 14-07-2006 10:31:09

Page 12 of 124

ACUXX
1222-104 I/O Configuration->Ch34,1222Description: 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-204 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-304 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: 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. 123304 I/O Configuration->Ch22,1233,

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: Supervision of pressure in the outer pipe of double pipe 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.

1222-104 123304

gls / 14-07-2006 10:31:09

Page 13 of 124

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. 123504 I/O Configuration->Ch27,1235,

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. A small hydraulic leakage from the HPS is no longer possible to detect. If this becomes large a shutdown can occur. 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. 123604 I/O Configuration->Ch27,1236,

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. A large hydraulic leakage from the HPS is no longer possible to detect. 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. 1238-104 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.

123404 1238-104

gls / 14-07-2006 10:31:09

Page 14 of 124

ACUXX
1238-204 I/O Configuration->Ch30,1238Description: 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-304 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. 8501-304 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-A04 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.

1238-204 8501-A04

gls / 14-07-2006 10:31:09

Page 15 of 124

ACUXX
8501-B04 I/O Configuration->Ch37,8501Description: 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. 8503-304 I/O Configuration->Ch36,8503-

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. 8503-A04 I/O Configuration->Ch36,8503-

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. 8503-B04 I/O Configuration->Ch36,8503-

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 8503-B04

gls / 14-07-2006 10:31:09

Page 16 of 124

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. SALOG System->AssertLog Stopped

Description: The built-in event log in the MPC has stopped. This event log is used for diagnosis only. Cause: The event log stops when used storage has become invalid. Effect: There is no immediate effect, but diagnostic capabilities in case of hard- or software failures will be limited. Sugg. Action: Contact MAN B&W Diesel 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. SFuseF12 System->24V power supervision

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. SFuseF13 System->24V power supervision

Description: The alarm indicates that Fuse 13 of the specified MPC is blown. Fuse 13 protects the power outlets of: channels 40 to 47, terminal "D", channels 48 to 53, terminal "E", channels 60 and 61, terminal "H". Cause: Electrical overload or wear of the fuse. Effect: A number of the signals related to channels 40 to 61 may be wrong. Effect on engine behaviour is unknown. Sugg. Action: Check for possible failures in the external cabling to channels 40 to 61.Replace the fuse.

875104 SFuseF13

gls / 14-07-2006 10:31:09

Page 17 of 124

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. SFuseF9 System->24V power supervision

Description: The alarm indicates that Fuse 9 of the specified MPC is blown. Fuse 9 protects power supply connector 9 of the MPC. Cause: Electrical overload or wear of the fuse. Effect: J9 powers the high pressure hydraulic pump's proportional valve. If fuse F9 is blown, 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. Sugg. Action: Check for possible failures in the external cabling to connector 9. Replace the fuse. 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. SInvSw System->Invalid software

Description: The MPC is running an incorrect application program Cause: Can be caused by replacing an MPC when both MOP A and MOP B are unavailable. Effect: The ECS could seriously be affected by having the MPC running incorrect software. The exact behaviour is unknown since it also depends on which MPC is involved. Sugg. Action: Switch off the involved MPC immediately. When either MOP A or MOP B is operating again, the MPC can be switched on again. When this is done, wait for the automatic preparation of the MPC to finish before the MPC will operate correctly again. SPow24VA System->24V power supervision

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. SPow24VB System->24V power supervision

Description: The alarm indicates that power inlet, connector 1, terminal C, is powerless. Cause: The breaker of power supply B for the specified MPC is turned off. 24V power supply B is turned off. The power cabling is defect. Effect: No immediate effect, as the MPC is supplied by power supply A. Sugg. Action: Check for the causes.

SFuseF14 SPow24VB

gls / 14-07-2006 10:31:09

Page 18 of 124

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 SWDogDac

gls / 14-07-2006 10:31:09

Page 19 of 124

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. 01010428 Tacho set B->Tacho set B 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. 010119 Tacho->Delta Tacho B too big

Description: The two tacho inputs are not aligned within tolerance. Cause: The distance between the tacho marker signals does not correspond to the values set in the service terminal. Effect: Engine may run unsteady if the tacho system changes from input A to input B or vice versa. Sugg. Action: Correct adjustment at next engine overhaul or engine stop. 010122 Tacho->Tacho Alignment Err

Description: One or both tachos are out of adjustment. Cause: Encoder drive slipping or encoder mount out of adjustment Effect: Engine may run unsteady if the tacho system changes from input A to input B or vice versa. Sugg. Action: Correct adjustment at next engine overhaul or engine stop. 010127 Tacho->Tacho Input A slip

Description: Tacho A position signal is wrong Cause: All signals are turning on/off in the correct sequence, but the position of the tacho does not match the other tacho and the signal from the turning wheel sensor. Effect: The MPC had to change active set of tacho sensors. If both sensor set A and B fail on one ECU control is taken over by redundant ECU. If both set A and B fail on both ECU A and B the engine will stop. Sugg. Action: Correct adjustment at next engine overhaul or engine stop. 010128 Tacho->Tacho Input B slip

Description: Tacho B position signal is wrong Cause: All signals are turning on/off in the correct sequence, but the position of the tacho does not match the other tacho and the signal from the turning wheel sensor. Effect: The MPC had to change active set of tacho sensors. If both sensor set A and B fail on one ECU control is taken over by redundant ECU. If both set A and B fail on both ECU A and B the engine will stop. Sugg. Action: Correct adjustment at next engine overhaul or engine stop. 010129 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.

01010328 010129

gls / 14-07-2006 10:31:09

Page 20 of 124

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. 010414 Fuel Telegram Handler->No Telegram Received from ECU A

Description: Once per revolution a CCU must receive a network message with commands for activation of injection and exhaust valves. Both ECU A and B send a copy of these commands. For some reason the commands were not received from the specified ECU. Cause: Typically this is caused by control network problems or malfunctioning ECU. Effect: If commands are only missing from 1 ECU the engine is not affected by it. It is however a significant indication that something is not right. When commands are not received from both ECU A and B on the same CCU fuel injection is stopped while exhaust valve activation is continued with latest received timing. Sugg. Action: If the alarm is only from one CCU verify its network cabling and/or replace CCU. If multiple CCUs report the alarm from the same ECU verify the ECUs network cabling and/or replace ECU. If that does not help verify complete network cabling and contact MAN B&W. 010415 Fuel Telegram Handler->No Telegram Received from ECU B

Description: Once per revolution a CCU must receive a network message with commands for activation of injection and exhaust valves. Both ECU A and B send a copy of these commands. For some reason the commands were not received from the specified ECU. Cause: Typically this is caused by control network problems or malfunctioning ECU. Effect: If commands are only missing from 1 ECU the engine is not affected by it. It is however a significant indication that something is not right. When commands are not received from both ECU A and B on the same CCU fuel injection is stopped while exhaust valve activation is continued with latest received timing. Sugg. Action: If the alarm is only from one CCU verify its network cabling and/or replace CCU. If multiple CCUs report the alarm from the same ECU verify the ECUs network cabling and/or replace ECU. If that does not help verify complete network cabling and contact MAN B&W. 0109A IO Configuration->Shut Down

Description: A shut down has been ordered. Cause: Unknown Effect: Fuel injections are stopped and exhaust valve operation is continued as long as hydraulic supply pressure is available. Sugg. Action: The shut down must be reset in safety system. Then a stop command must be issued from active control station before a new start is allowed by ECS. 0109B IO Configuration->Suprv. Ch32,2002,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 cabling and verify if 1 or all CCU's report the failure. If only 1 check CCU cabling. If all check safety system side. 0227 Command Handler->HCU Oil Leakage Description: Leakage has been detected at the specified HCU. Cause: A leakage is detected in the high pressure fuel pipe. Effect: High pressure fuel is in the outer pipe. A leakage in the outer pipe will result in fuel spray onto engine components and maybe even on personnel. The control system provides an option (set by MAN B&W) for stopping fuel injections on the specific cylinder during this situation. Sugg. Action: If automatic fuel cut out is not performed by ECS, manually cut of fuel to that specific cylinder via the chief limiter on MOP. Reduce engine load to ecceptable level with 1 cylinder cut out. Stop engine when possible and repair high pressure pipe. 010130 0227

gls / 14-07-2006 10:31:09

Page 21 of 124

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. 030117 Fuel Injection->Fuel Plunger Stroke Too High

Description: Fuel plunger moves more than expected with the current fuel index. Cause: Failing suction valve in fuel pump or failing injection valve(s). Faults on CCU hardware can also cause this. 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 pump suction valve, injection valves. If no result replace CCU. 030118 Fuel Injection->Fuel Plunger Stroke Too Low

Description: Fuel plunger moves less than expected with the current fuel index. Cause: Failing injection valves, hydraulic supply pressure or ELFI/FIVA valve 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: Inspect hydraulic supply, reduced injection nozzle area and pressure booster 03023209 Exhaust Valve Supervision->Exhaust Valve Open Stroke Low

Description: The exhaust valve spindle did not move sufficiently for the control system to be sure that the scavenge process has been carried out as required for further injections. Cause: Cabling between CCU and ELVA/FIVA valve, failing ELVA/FIVA valve, missing oil supply to hydraulic pushrod, missing air supply to exhaust valve air spring. Effect: The injections are stopped and Slowdown request are ordered. Attempts to open exhaust valve remain. Sugg. Action: Verify cabling, oil supply and air supply the exhaust valve. If all OK replace ELVA/FIVA valve. 03023210 Exhaust Valve Supervision->Exh. Valve Closed Position Changed

Description: The measurement on the exhaust valve spindle indicates that the valve moved during a period where it should have been fully closed all the time. Cause: Failing air spring, failing ELVA valve, too high hydraulic oil tank return pressure, failing exhaust valve actuator and/or dampers. Effect: The exhaust valve might not be fully closed when it should causing a risk for reduced compression pressure, increased temperatures on valve seat and exhaust gas and reduced air excess ratios (smoke). Sugg. Action: Verify air spring pressure and return pressure. If OK replace ELVA. If still no good result verify exhaust valve actuator and top dampers. 03023313 Exhaust Valve Timing Controller->Exhaust Valve Opening Too Slow

Description: Exhaust valve takes longer time to open than the automatic compensation in the control system is willing to accept. Cause: Too high cylinder pressure when exhaust valve opening is initiated. Too low hydraulic pressure giving too little power when opening exhaust valve. Effect: Correct exhaust valve open timing cannot be expected while this alarm is active. Opening might be later than desired causing a minor increase in blow back. Sugg. Action: Check cylinder PMI balance, hydraulic supply pressure and air spring.

030116 03023313

gls / 14-07-2006 10:31:09

Page 22 of 124

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. 03023315 Exhaust Valve Timing Controller->Exhaust Valve Closing Too Slow

Description: Exhaust valve takes longer or shorter time to close than the automatic 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: Verify cylinder compression, maximum and mean pressure with PMI equipment. If deviations from desired values are too large correct them adjust via MOP. When this alarm dissapears undo the adjustments. 03023316 Exhaust Valve Timing Controller->Exhaust Valve Closing Too Fast

Description: Exhaust valve takes longer or shorter time to close than the automatic 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. 030306 ElFi Valve->Position Feedback Signal Failure

Description: The position feedback on the specific injection controlling valve has shown movements that are not physically realistic. Cause: Typically loose connection in cabling. On some early ELFI valves wire breakage has been seen internally in the valve. Effect: When the fault is detected injections are stopped for a period of a few seconds and Slowdown request are ordered. Then injections are re-attempted until the fault is detected again. 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. 03031104 Amplifier->ELFI Amp. Current Supervision

Description: The CCU constantly orders an appropriate current for controlling the ELFI/FIVA valve. The current is delivered by the ELFI/FIVA amplifier located in the CCU box. For supervision purpose the amplifier also measures the actual delivered current. When the delivered current is not equal to the ordered this alarm is released. Cause: Typically the cause is faulty cabling to or from the amplifier. More seldom the actual amplifier or the CCU has been seen to cause the fault. Effect: The injections are stopped for a few seconds before trying to inject again. This will obviously lead to large exhaust temperature deviations between the cylinders. Sugg. Action: Check cabling between CCU and amplifier and check cabling between amplifier and ELFI/FIVA spool. Reset amplifier by switching power to the CCU off and then back on. If alarm re-appears just after power up check amplifier fuse. Replace amplifier if fuse OK. If cylinder works OK some minutes before the alarm comes back replace ELFI valve.

03023314 03031104

gls / 14-07-2006 10:31:09

Page 23 of 124

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. 030406 FIVA Valve->Position Feedback Signal Failure

Description: The position feedback on the specific injection controlling valve has shown movements that are not physically realistic. Cause: Typically loose connection in cabling. On some early ELFI valves wire breakage has been seen internally in the valve. Effect: When the fault is detected injections are stopped for a period of a few seconds and Slowdown request are ordered. Then injections are re-attempted until the fault is detected again. 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. 03041104 Amplifier->FIVA Amp. Current Supervision

Description: The CCU constantly orders an appropriate current for controlling the ELFI/FIVA valve. The current is delivered by the ELFI/FIVA amplifier located in the CCU box. For supervision purpose the amplifier also measures the actual delivered current. When the delivered current is not equal to the ordered this alarm is released. Cause: Typically the cause is faulty cabling to or from the amplifier. More seldom the actual amplifier or the CCU has been seen to cause the fault. Effect: The injections are stopped for a few seconds before trying to inject again. This will obviously lead to large exhaust temperature deviations between the cylinders. Sugg. Action: Check cabling between CCU and amplifier and check cabling between amplifier and ELFI/FIVA spool. Reset amplifier by switching power to the CCU off and then back on. If alarm re-appears just after power up check amplifier fuse. Replace amplifier if fuse OK. If cylinder works OK some minutes before the alarm comes back replace ELFI valve. 03041105 Amplifier->FIVA 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. 030502 ElVa Valve->Too Late PSP Setup

Description: Internal ECS fault situation. An internal calculation was completed too late. Cause: Very uncertain. A partly failing network can cause significantly increased cpu load on the MPCs leading to unacceptable delays on some calculations. Effect: The exhaust valve operation will probably be affected leading to cancellation of some injections also. Sugg. Action: Contact MAN B&W. Monitor exhaust gas temperature. If temperature is OK continues running is OK. If not shut off that cylinder and continue with reduced load. 030511 ElVa Valve->ELVA Valve Status

Description: The ELVA valve, which activates the exhaust valve, indicates an internal fault. Cause: An internal failure in the ELVA valve. Effect: If the ELVA valve is failing exhaust valve will not be activated, which then again causes the injections on that cylinder also to be stopped. Sugg. Action: Check cabling between CCU and ELVA. If OK replace ELVA.

03031105 030511

gls / 14-07-2006 10:31:09

Page 24 of 124

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. 031220 Cylinder Lubrication->Failing Lubricator FeedBack

Description: Feedback from the cylinder lubricator main piston movement is failing. Cause: No stroke or no full stroke. Effect: No cylinder lubrication on the affected cylinder. ECS will still try to activate the injector electrically. Slowdown request is send from ECS. Sugg. Action: Replace the injector. 031221 Cylinder Lubrication->No Cylinder Lube Oil

Description: Cylinder lubrication oil detector reports no lubrication oil. Cause: Cylinder lubrication oil supply could be blocked. Effect: No cylinder lubrication oil on the affected cylinder. Slowdown request is ordered from ECS. Sugg. Action: Check that the individual shutoff valves is not closed. Check the cylinderlubrication oil tank level. 0312B Cylinder Lubrication->Cylinder Lube Flow Sensor fault

Description: Flow sensor has illegal value when engine is stopped. Cause: Flow sensor is not adjusted correct, or sensor is bad. Effect: Supervision of cylinder lubrication oil supply is no longer provided. Sugg. Action: Try to adjust sensor or change sensor. 0312C Cylinder Lubrication->No Cyl. lubrication (Tacho fault)

Description: Failure on Tacho A and Tacho B. It is no longer possible for the CCU to perform cylinder lubrication. Cause: Failure on both Tacho sets. Effect: Cylinder lubrication is no longer possible. Sugg. Action: Check tachosignal cabling to the affected CCU. 1002 Burst IO Handler->Too Late PSP Setup Description: Internal ECS fault situation. An internal calculation was completed too late. Cause: Very uncertain. A partly failing network can cause significantly increased cpu load on the MPCs leading to unacceptable delays on some calculations. Effect: Difficult to predict. Often no effect, in other situations unstable operation of fuel injection and exhaust valve on that cylinder. Sugg. Action: Contact MAN B&W. Monitor exhaust gas temperature. If temperature is OK continues running is OK. If not shut off that cylinder and continue with reduced load. 200204 Ch32,2002,Shut Down Safety System->Suprv. Ch32,2002,Shut Down Safety S

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 200204

gls / 14-07-2006 10:31:09

Page 25 of 124

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. 410204 Ch30,4102,Prop. Valve Position Feed->Suprv. Ch30,4102,Prop. Valve 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: Control of the valve is stopped causing no injections on that cylinder. 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. 410604 Ch33,4106,Valve Amplifier Actual Cu->Suprv. Ch33,4106,Valve Amplifier Ac

Description: The CCU constantly orders an appropriate current for controlling the ELFI/FIVA valve. The current is delivered by the ELFI/FIVA amplifier located in the CCU box. For supervision purpose the amplifier also measures the actual delivered current. When the delivered current is not equal to the ordered this alarm is released. Cause: Typically the cause is faulty cabling to or from the amplifier. More seldom the actual amplifier or the CCU has been seen to cause the fault. Effect: Supervision of cabling to ELFI valve spool is no longer provided. 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. 411104 Ch34,4111,Exh. Valve Position->Suprv. Ch34,4111,Exh. Valve Positio

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: Supervision of exhaust valve movement is no longer available. This can cause 'minor' problems with obtaining the correct pcomp/pscav and blowback. Further more injections will continued as long as the ELVA valve does not signal valve failure. Normally the exhaust valve movement is also evaluated before injection is allowed. 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.

2002-04 411104

gls / 14-07-2006 10:31:09

Page 26 of 124

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. 411404 Ch31,4114,Plunger Position Mean->Suprv. Ch31,4114,Plunger Position M

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 fuel plunger movement is no longer supervised. 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. 998004 Ch21,9980,Lube Oil Flow Missing->Suprv. Ch21,9980,Lube Oil Flow Miss

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 cylinder lubrication oil supply 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. 999004 Ch21,9990,Lube Oil Supply Missing->Suprv. Ch21,9990,Lube Oil Supply Mi

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 cylinder lubrication oil supply 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. 999904 Description: Cause: Effect: Sugg. Action: SALOG System->AssertLog Stopped Ch37,9999,Prop. Valve Test Set Poin->Suprv. Ch37,9999,Prop. Valve Test S

Description: The built-in event log in the MPC has stopped. This event log is used for diagnosis only. Cause: The event log stops when used storage has become invalid. Effect: There is no immediate effect, but diagnostic capabilities in case of hard- or software failures will be limited. Sugg. Action: Contact MAN B&W Diesel

411204 SALOG

gls / 14-07-2006 10:31:10

Page 27 of 124

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. 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: Sugg. Action: Check for possible failures in the external cabling to channels 20 to 37. Replace the fuse. SFuseF13 24V power supervision->Fuse F13 failure

Description: The alarm indicates that Fuse 13 of the specified MPC is blown. Fuse 13 protects the power outlets of: channels 40 to 47, terminal "D", channels 48 to 53, terminal "E", channels 60 and 61, terminal "H". Cause: Electrical overload or wear of the fuse. Effect: A number of the signals related to channels 40 to 61 may be wrong. Effect on engine behaviour is unknown. Sugg. Action: Check for possible failures in the external cabling to channels 40 to 61.Replace the fuse. SFuseF14 24V power supervision->Fuse F14 failure

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: 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. SFuseF9 24V power supervision->Fuse F9 failure

Description: The alarm indicates that Fuse 9 of the specified MPC is blown. Fuse 9 protects power supply connector 9 of the MPC. Cause: Electrical overload or wear of the fuse. Effect: Sugg. Action: Check for possible failures in the external cabling to connector 9. Replace the fuse. 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. SInvSw System->Invalid software

Description: The MPC is running an incorrect application program Cause: Can be caused by replacing an MPC when both MOP A and MOP B are unavailable. Effect: The ECS could seriously be affected by having the MPC running incorrect software. The exact behaviour is unknown since it also depends on which MPC is involved. Sugg. Action: Switch off the involved MPC immediately. When either MOP A or MOP B is operating again, the MPC can be switched on again. When this is done, wait for the automatic preparation of the MPC to finish before the MPC will operate correctly again.

SBAT SInvSw

gls / 14-07-2006 10:31:10

Page 28 of 124

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. SPow24VB 24V power supervision->24V power B failure, connector 1C

Description: The alarm indicates that power inlet, connector 1, terminal C, is powerless. Cause: The breaker of power supply B for the specified MPC is turned off. 24V power supply B is turned off. The power cabling is defect. Effect: No immediate effect, as the MPC is supplied by power supply A. Sugg. Action: Check for the causes. 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

SPow24VA SWDogDac

gls / 14-07-2006 10:31:10

Page 29 of 124

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. 01010301 EICU Commands->Speed Setpoint (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. 01010501 EICU Commands->Engine Mode User Req. (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. 010112 EICU Commands->No Commands Received from EICU 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 ECU A&B signals alarm for missing EICU 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. 010113 EICU Commands->No Commands Received from EICU B

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 ECU A&B signals alarm for missing EICU 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. 010114 EICU Commands->Local Control Take Command Active

Description: Engine control has been taken at LOP. Cause: User has pressed the take command at LOP. Effect: No other control stations can take over engine control before the take command is removed on LOP. Sugg. Action: None, untill engine control is required to be given to another control station. Depress the take button on the LOP.

0100601 010114

gls / 14-07-2006 10:31:10

Page 30 of 124

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. 01020328 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 ECU control is taken over by redundant ECU. If both set A and B fail on both ECU A and B the engine will stop. 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. 01020428 Tacho set B->Tacho set B 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 ECU control is taken over by redundant ECU. If both set A and B fail on both ECU A and B the engine will stop. 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. 010219 Tacho->Delta Tacho B too

Description: The two tacho inputs are not aligned within tolerance. Cause: The distance between the tacho marker signals does not correspond to the values set in the service terminal. Effect: Engine may run unsteady if the tacho system changes from input A to input B or vice versa. Sugg. Action: Correct adjustment at next engine overhaul or engine stop. 010222 Tacho->Tacho Alignment Er

Description: One or both tachos are out of adjustment. Cause: Encoder drive slipping or encoder mount out of adjustment Effect: Engine may run unsteady if the tacho system changes from input A to input B or vice versa. Sugg. Action: Correct adjustment at next engine overhaul or engine stop. 010227 Tacho->Tacho Input A slip

Description: Tacho A position signal is wrong Cause: Tacho A is reporting a different position signal than Tacho B and Marker Slave A (crankshaft). Effect: Engine may run unsteady if the tacho system changes from input A to input B or vice versa. Sugg. Action: Correct adjustment at next engine overhaul or engine stop. 010228 Tacho->Tacho Input B slip

Description: Tacho B position signal is wrong Cause: Tacho B is reporting a different position signal than Tacho A and Marker Slave A (crankshaft). Effect: Engine may run unsteady if the tacho system changes from input A to input B or vice versa. Sugg. Action: Correct adjustment at next engine overhaul or engine stop. 010229 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.

010115 010229

gls / 14-07-2006 10:31:10

Page 31 of 124

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. 011423 ACUs Feedback->No HPS & blower feedback from ACU2

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. 011424 ACUs Feedback->No HPS & blower feedback from ACU3

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. 011425 ACUs Feedback->No AuxReady feedback from ACU 1

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 involve the Auxiliary Ready logic. If the ECU that cannot receive the control values is the Master ECU, then the Auxiliary Ready logic 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. 011426 ACUs Feedback->No AuxReady feedback from ACU 2

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 involve the Auxiliary Ready logic. If the ECU that cannot receive the control values is the Master ECU, then the Auxiliary Ready logic 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. 011441 ACUs Feedback->Turngear eng. disagree ACU 1/2

Description: Turning gear engaged signal disagree on ACU1 and ACU2. Cause: Turning gear engaged switch is ON on one ACU and OFF on another ACU. Effect: It is not known whether the turning gear is engaged or not. Sugg. Action: Check the two turning gear engaged switches.

011422 011441

gls / 14-07-2006 10:31:10

Page 32 of 124

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. 011443 ACUs Feedback->Start vlv. blk. disagree ACU 1/2

Description: Main start valve blocked signal disagree on ACU1 and ACU2. Cause: Main start valve blocked switch is ON on one ACU and OFF on another ACU. Effect: Can prevent the engine from start, if a faulty indication of main start valve blocked signal is set. Sugg. Action: Check the main start valve position and main start valve blocked switches. 011444 ACUs Feedback->Start vlv. serv. disagree ACU 1/2

Description: Main start valve in service signal disagree on ACU1 and ACU2. Cause: Main start valve in service switch is ON on 1 ACU and OFF on another ACU. Effect: Could lead to incorrect indication of Engine Not Ready condition. Sugg. Action: Check the main start valve position and main start valve in service switches. 011445 ACUs Feedback->Start air serv. disagree ACU 1/2

Description: Start air distribution system in service signal disagree on ACU1 and ACU2. Cause: Start air distribution system in service switch is ON on one ACU and OFF on another ACU. Effect: Could lead to incorrect indication of Engine Not Ready condition. Sugg. Action: Check the start air distribution system position and start air distribution system in service switches. 011448 ACUs Feedback->Start air blk. disagree ECU A/B

Description: Start air distribution system blocked signal disagree on ECUA and ECUB. Cause: Start air distribution system blocked switch is ON on one ECU and OFF on another ECU. Effect: Can prevent the engine from start, if a faulty indication of start air distribution system blocked signal is set. Sugg. Action: Check the start air distribution system position and start air distribution system blocked switches. 0201010501 Crankshaft->Speed (Filtered) (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. 0201020601 Start/Stop Logic->Start/Stop Logic 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.

011442 020102060

gls / 14-07-2006 10:31:10

Page 33 of 124

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. 02010212 Start/Stop Logic->Starting Failed

Description: 3 start attempts were executed but none led to acceptable engine speed. Cause: Heavy running or failing start air system. Effect: A new engine stop command and then start are required for retrying engine start. Sugg. Action: Perform an air run while comfirming that the engine runs steady on air achiving at least 20rpm. If so, verify the manually operated valves positions on each HCU. Finally attempt a new start. 02010213 Start/Stop Logic->Turning Failed

Description: Slow turning of the engine was not succesfull. A complete revolution was not completed in due time. Cause: Heavy running or failing start air system. Effect: A manual slow turn should be carried out (or retried) before new engine start. Sugg. Action: Perform manual slow turn while verifying that the engine runs steady on air (by listening) while obtaining at least 10rpm. If that is not the case verify start air pressure and start air valves including solonoides. 02010214 Start/Stop Logic->Shut Down

Description: A shut down has been ordered. Cause: A shut down order was generated either by safety system or be ECS itself. Effect: Fuel injections are immediately stopped. Exhaust valve operation is maintained as long as possible. Sugg. Action: The shut down must be reset in safety system. Then a stop command must be issued from active control station before a new start is allowed by ECS. 02012233 Engine Running Modes->Engine Running Mode Calculation

Description: An internal calculation has resulted in an invalid result. Cause: Unknown Effect: Engine control is automatically changed over to the redundant ECU. Therefore redundancy no longer exists for the ECUs. Sugg. Action: Reset the ECU that reported the alarm. 02012240 Engine Running Modes->No Valid Pscav Sensor Available

Description: The scavenge air pressure is vital for calculating the desired cycle process values like maximum cylinder pressure etc. If no sensor is valid a model curve is used. Cause: Both redundant scavenge air pressure sensors have failed. Effect: A model curve is used for controlling the engine cycle process. Sugg. Action: Check sensor and cabling. Untill failure has been located and repaired extra attention must be paid to verifying engine cycle process. For instance by using a PMI tool for verifying obtained cylinder pressures. 0201224421 Gas Bypass->Too High Pscav

Description: Scavenge air pressure exceeds maximum allowed level. Cause: Malfunctioning bypass valve, extreme ambient conditions or very fast engine load changes. Effect: The bypass valve is ordered to full opening in order to compensate for the high scavenge air pressure. Sugg. Action: Inspect bypass valve.

02010211 020122442

gls / 14-07-2006 10:31:10

Page 34 of 124

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. 020125K Cylinder Lubrication->Max Limiter 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 parameter for normal max level is to high or the lubricators are to 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 for run in max is according to MBD specification. Check that lubricator size is according to specification and that the parameter "Mass/Injection per Cylinder" is correct. 020125L Cylinder Lubrication->Run In 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 parameter for run in max level is too high or the lubricators are too small for the engine. Effect: The cylinder lubricator will be activated with the highest frequency possible, which is one time per revolution. Sugg. Action: Check if the parameter for run in max is according to MBD specification. Check that lubricator size is according to specification and that the parameter "Mass/Injection per Cylinder" is correct. 0202011301 Speed Controller->Fuel Index Integrator (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. 02020135 Speed Controller->'Lock In Last' Fuel Index

Description: An internal calculation has resulted in an invalid result. Cause: Unknown Effect: Engine control is automatically changed over to the redundant ECU. Therefore redundancy no longer exists for the ECUs. Sugg. Action: Reset the ECU that reported the alarm. 0202020709 Hydraulic Supply Pressure Limiter->Low Hydraulic Pressure

Description: The hydraulic supply pressure has dropped to a level where it was necessary to reduce maximum allowed fuel index to less than 100%. The eventual load reduction that leads to serves the purpose of reducing the required flow and therefore might recover from the pressure drop. Cause: Pump failure, hydraulic leakage or failing bypass valves in the hydraulic supply system. Effect: Engine load might be reduced and engine might run with unstable speed and fuel index. If the pressure at some point drops too far a shut down is carried out. Sugg. Action: While locating the failure that causes the pressure drop reduce engine load in order to avoid unstable running. Check for hydraulic pump related alarms. Check for hydraulic leakages and failing bypass valves. Typically a failing bypass valve increases significantly in temperature.

020125J 020202070

gls / 14-07-2006 10:31:10

Page 35 of 124

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 02020308 Governor Mode Selector->ECS Speed Mode Command

Description: It became necessary for the ECS to overrule the active governor mode selected on MOP. Cause: Typically due to speed variations larger that acceptable by shaft generator. Effect: A stronger engine speed control has been applied leading to smaller deviations between speed setpoint and actual speed. Another result is larger fuel index variations leading to less economical fuel consumption during some running conditions. Sugg. Action: Verify that speed variations do not indicate unstable engine running due to other things than external load variations. Change back to desired governor mode when more stable engine speed has been obtained again. 02021101 Governor->Fuel Index Setpoint (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. 0210301 IO->Ch31,2103, Deviation Supervision (

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: 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. 0860101 IO->Ch35,8601, Deviation Supervision (

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: 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. 100604 Ch26,1006,Local: Speed Set->Suprv. Ch26,1006,Local: Speed Set

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: The engine speed set can no longer be set from the LOP. Sugg. Action:

020202071 100604

gls / 14-07-2006 10:31:10

Page 36 of 124

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: 1117-A04 Ch32,1117-A,Blocked Start Air Distr->Suprv. Ch32,1117-A,Blocked Start Ai

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Reduced supervision quality. Redundancy lost. Sugg. Action: 1117-B04 Ch32,1117-B,Blocked Start Air Distr->Suprv. Ch32,1117-B,Blocked Start Ai

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Reduced supervision quality. Redundancy lost. Sugg. Action: 2001-A04 Ch34,2001-A,Shut Down->Suprv. Ch34,2001-A,Shut Down

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: This ECU will no longer react on shut down signal from safety system. If shut down signals to CCUs are OK the engine will stop injecting fuel if safety system makes shut down. Sugg. Action: 2001-B04 Ch34,2001-B,Shut Down->Suprv. Ch34,2001-B,Shut Down

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: This ECU will no longer react on shut down signal from safety system. If shut down signals to CCUs are OK the engine will stop injecting fuel if safety system makes shut down. Sugg. Action: 2103-A04 Ch31,2103-A,Prop. Pitch->Suprv. Ch31,2103-A,Prop. Pitch

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Pitch signal is no longer available which can cause reduced governor performance during pitch changes. If the pitch signal is not OK on both ECU A and B it might be required to overruled zero pitch blocking in start situations. Sugg. Action: 2103-B04 Ch31,2103-B,Prop. Pitch->Suprv. Ch31,2103-B,Prop. Pitch

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Pitch signal is no longer available which can cause reduced governor performance during pitch changes. If the pitch signal is not OK on both ECU A and B it might be required to overruled zero pitch blocking in start situations. Sugg. Action: 2114-A04 Ch23,2114-A,Local: Air Run->Suprv. Ch23,2114-A,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:

100904 2114-A04

gls / 14-07-2006 10:31:10

Page 37 of 124

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: 2115-A04 Ch24,2115-A,Local: Slow Turn->Suprv. Ch24,2115-A,Local: Slow Turn

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Manual slow turn can no longer be ordered from LOP via this ECU. Automatic slow will be executed as normal. Sugg. Action: 2115-B04 Ch24,2115-B,Local: Slow Turn->Suprv. Ch24,2115-B,Local: Slow Turn

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Manual slow turn can no longer be ordered from LOP via this ECU. Automatic slow will be executed as normal. Sugg. Action: 2151-A04 Ch22,2151-A,Local: Stop->Suprv. Ch22,2151-A,Local: Stop

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Engine stop can no longer be ordered from LOP via this ECU. Sugg. Action: 2151-B04 Ch22,2151-B,Local: Stop->Suprv. Ch22,2151-B,Local: Stop

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Engine stop can no longer be ordered from LOP via this ECU. Sugg. Action: 2152-A04 Ch21,2152-A,Local: Increace Limiter->Suprv. Ch21,2152-A,Local: Increace

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Increase limit can no longer be ordered from LOP via this ECU. Sugg. Action: 2152-B04 Ch21,2152-B,Local: Increace Limiter->Suprv. Ch21,2152-B,Local: Increace

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Increase limit can no longer be ordered from LOP via this ECU. Sugg. Action: 2153-A04 Ch25,2153-A,Local: Take CMD->Suprv. Ch25,2153-A,Local: Take CMD

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Take command can no longer be ordered on LOP via this ECU. Sugg. Action: 2153-B04 Ch25,2153-B,Local: Take CMD->Suprv. Ch25,2153-B,Local: Take CMD

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Take command can no longer be ordered on LOP via this ECU. Sugg. Action:

2114-B04 2153-B04

gls / 14-07-2006 10:31:10

Page 38 of 124

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-B04 Ch30,2155-B,Local: Start->Suprv. Ch30,2155-B,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: 2156-A04 Ch26,2156-A,Local: SpeedSet Up Butt->Suprv. Ch26,2156-A,Local: SpeedSet

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Engine speed set can no longer be increased from LOP via this ECU. Sugg. Action: 2156-B04 Ch26,2156-B,Local: SpeedSet Up Butt->Suprv. Ch26,2156-B,Local: SpeedSet

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Engine speed set can no longer be increased from LOP via this ECU. Sugg. Action: 2157-A04 Ch27,2157-A,Local: SpeedSet Down Bu->Suprv. Ch27,2157-A,Local: SpeedSet

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Engine speed set can no longer be decreased from LOP via this ECU. Sugg. Action: 2157-B04 Ch27,2157-B,Local: SpeedSet Down Bu->Suprv. Ch27,2157-B,Local: SpeedSet

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Engine speed set can no longer be decreased from LOP via this ECU. Sugg. Action: 5020901 Aux. Blower Command->Blower cmd state no. (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. 50215 Aux. Blower Command->Manual blower operation demanded

Description: Operator has commanded manual operation of blowers. Cause: Caused by pressing the "Manual" button on the MOP. Effect: The blowers will "bumpless" change to Manual operation. Hence operating blowers will continue to operate in Manual mode. In Manual mode, the operator is responsible for starting and stopping the blowers. It is not allowed to start the engine from Bridge control station if the blowers are in Manual mode. Sugg. Action: Automatic mode is considered safe, so when Manual mode operations are finished switch back to Automatic mode.

2155-A04 50215

gls / 14-07-2006 10:31:10

Page 39 of 124

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. 50321 Auxiliary Ready/Not Ready->Start air press. sensor deviation

Description: The pressure sensors are deviating. Cause: At least one sensor is drifting. Effect: If sensors deviate, lowest pressure value is assumed the correct value. Sugg. Action: Check the sensors to find the drifting sensor and replace the faulty sensor. 50322 Auxiliary Ready/Not Ready->Ctrl. air press. sensor deviation

Description: The pressure sensors are deviating. Cause: At least one sensor is drifting. Effect: If sensors deviate, lowest pressure value is assumed the correct value. Sugg. Action: Check the sensors to find the drifting sensor and replace the faulty sensor. 50323 Auxiliary Ready/Not Ready->Start air press low

Description: Start air pressure is too low. Cause: Starter air pressure compressor is not working. A valve in the starter air system might be open. Effect: If the starter air pressure is too low, it is not allowed to start the engine from Bridge. Sugg. Action: Correct the starter air pressure problem. 50324 Auxiliary Ready/Not Ready->Ctrl air press low

Description: Control air pressure is too low. Cause: Some fault in the control air system has occurred. Effect: The Engine Not Ready sign will be ON. Sugg. Action: Correct the control air pressure problem. 50325 Auxiliary Ready/Not Ready->Start valve pos inconsistency

Description: Main start valve position inconsistence. Cause: Switches indicating "Blocked" and "In-Service" are both ON or OFF at the same time. Effect: "Engine Blocked", "Engine Not Ready", and "Start Blocked" indications may be based on faulty information, and cannot be trusted before the inconsistence have been fixed. Sugg. Action: Inspect the switches indicating "Blocked" and "In-Service" and correct the fault. 50326 Auxiliary Ready/Not Ready->Start air dist pos inconsistency

Description: Start air distribution system position inconsistence. Cause: Switches indicating "Blocked" and "In-Service" are both ON or OFF at the same time. Effect: "Engine Blocked", "Engine Not Ready", and "Start Blocked" indications may be based on faulty information, and cannot be trusted before the inconsistence have been fixed. Sugg. Action: Inspect the switches indicating "Blocked" and "In-Service" and correct the fault. 50327 Auxiliary Ready/Not Ready->Turning gear pos inconsistency

Description: Turning gear position inconsistency Cause: Switches indicating "Engaged" and "Disengaged" are both ON or OFF at the same time. Effect: "Engine Not Ready", and "Start Blocked" indications may be based on faulty information, and cannot be trusted before the inconsistence have been fixed. Sugg. Action: Care must be taken. Check the turning gear position and position switches before attempting to start the engine.

50216 50327

gls / 14-07-2006 10:31:10

Page 40 of 124

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. 5101012101 HPS Command->D

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: 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: 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. 51010123 Pump Model Curve->Pump Torque Limiter Reached

Description: Pump torque limiter reached. Cause: Could be caused by a hydraulic leakage, or lack of hydraulic delivery from swashplate pumps. Effect: Engine load can be limited due to maximum swashplate pump delivery has been reached (in normal operation of these). Sugg. Action: Check for leaks in the hydraulic system. Check drain valve valves on the HCU (421 from inner pipe to drain, and 431 from double pipe to drain). Check swashplate pumps for broken shafts. Check if HP sensors are drifting. 51010501 Driven Pumps Command->Driven 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. 510116 Driven Pumps Command->Manual HPS operation demanded

Description: Operator has commanded manual operation of HPS (Chief-level access). Cause: Caused by pressing the "Manual" button on the MOP. Effect: The HPS will "bumpless" change to Manual operation. Hence operating startup pumps will continue to operate in Manual mode. The automatic pressure control is still active in Manual mode and is using the pressure setpoint computed by the ECS. This pressure setpoint can be overruled by the operator by manually altering the pressure setpoint. When doing so, the new pressure setpoint will be used until the operator either chooses a new setpoint, or returns to Automatic mode. Sugg. Action: Automatic mode is considered safe, so when Manual mode operations are finished switch back to Automatic mode.

51010113 510116

gls / 14-07-2006 10:31:10

Page 41 of 124

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. 51012201 Driven Pumps Command->Press ctrl pump cmd (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: First, try to change pressure controlling pump from MOP A or MOP B using the Pressure Control buttons on the HPS page of Auxiliaries. If unsuccessful then, 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. 51013101 TorqueRestriction->Torque limiter cancelled

Description: Swashplate pump torque limiter cancelled. Cause: HMI button for release (Chief-level access) of torque restriction has been activated. Effect: Cancelling the Torque Limiter function is intended to be done only if one or more swashplate pumps are malfunctioning and does not deliver flow (e.g. broken pump shaft), since the cancelling the function causes any electric max. swivel restrictions to the pumps to be overridden. If, on the other hand, all pumps are delivering their normal amount of flow, then the Torque Limiter should not be cancelled. Sugg. Action: Find the cause for why the pump(s) are not delivering and repair/replace. The cause could be broken pump shaft. 5101310301 HPS Command->D

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: 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: Reset the ECU that reported the alarm.

510118 510131030

gls / 14-07-2006 10:31:10

Page 42 of 124

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. 510212 Startup Pumps Command->Standby pump started

Description: The Standby startup pump has been started. Cause: This can be caused by the Master startup pump cannot either build-up the hydraulic pressure for engine start within an acceptable time, or cannot maintain the hydraulic pressure. Effect: The Master startup pump may be defect. There might be a defect valve so that the startup pumps cannot build up hydraulic pressure for engine start. Sugg. Action: Check for a hydraulic leak or a defect valve. If the hydraulic pressure can be maintained while the Standby pump is running, the problem could be related to either a small hydraulik leakage or a defectiv Master startup pump. The alarm will disappear again when the other startup pump is chosen as Master. 5113 HPS Command->Lube press. sensor ACU 1 deviates Description: Lubrication oil pressure sensor (1204-x) on this ACU deviates from the lubrication oil pressure sensors on the two other ACUs. Cause: The sensor is either dead, is drifting, or the valve before the inlet to the engine driven pump is closed. Effect: The ECS will use the two other sensors for lubrication pressure evaluation. If the valve for lubrication oil inlet to the engine driven pump is closed, there is a risk that the pump will cavitate if the fault is not corrected before engine start. Sugg. Action: Inspect the valve position in front of the lubrication oil pressure sensor. If this valve is open, the sensor is likely to be malfunctioning. Replace the sensor. 5114 HPS Command->Lube press. sensor ACU 2 deviates Description: Lubrication oil pressure sensor (1204-x) on this ACU deviates from the lubrication oil pressure sensors on the two other ACUs. Cause: The sensor is either dead, is drifting, or the valve before the inlet to the engine driven pump is closed. Effect: The ECS will use the two other sensors for lubrication pressure evaluation. If the valve for lubrication oil inlet to the engine driven pump is closed, there is a risk that the pump will cavitate if the fault is not corrected before engine start. Sugg. Action: Inspect the valve position in front of the lubrication oil pressure sensor. If this valve is open, the sensor is likely to be malfunctioning. Replace the sensor. 5115 HPS Command->Lube press. sensor ACU 3 deviates Description: Lubrication oil pressure sensor (1204-x) on this ACU deviates from the lubrication oil pressure sensors on the two other ACUs. Cause: The sensor is either dead, is drifting, or the valve before the inlet to the engine driven pump is closed. Effect: The ECS will use the two other sensors for lubrication pressure evaluation. If the valve for lubrication oil inlet to the engine driven pump is closed, there is a risk that the pump will cavitate if the fault is not corrected before engine start. Sugg. Action: Inspect the valve position in front of the lubrication oil pressure sensor. If this valve is open, the sensor is likely to be malfunctioning. Replace the sensor.

51020801 5115

gls / 14-07-2006 10:31:10

Page 43 of 124

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. 5117 HPS Command->Hyd. press. sensor ACU 2 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. 5118 HPS Command->Hyd. press. sensor ACU 3 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. 5121 HPS Command->Lube press. low Description: Lubrication oil pressure is too low. Cause: Lube oil- or hydraulic high- pressure build-up prevented. Effect: The effect for the ECS is only an alarm. If the lube oil pressure decreases further, a non-cancellable shutdown could be carried out to protect the engine driven pumps from cavitation. Sugg. Action: Check the lubrication oil supply system for faults (pumps, valves etc.). Check for leaks in the high pressure system. 5131 HPS Command->Hyd. press. deviates from setpoint Description: The hydraulic pressure deviates too much from the hydraulic pressure setpoint computed by the ECS. Cause: If the hydraulic pressure is above the pressure setpoint it could be caused by too low hydraulic oil consumption. If it is lower than expected, it could be a hydraulic leakage. Another possibility is that it could be caused by either one or more malfunctioning engine driven pumps or incorrect calibration of these during connection test. Effect: If the hydraulic pressure is lower than the ECS computed setpoint and it continues to decrease, the hydraulic pumps cannot deliver enough oil to maintain the pressure. If the pressure drops below 145 150 bar, the ECS is likely to carry out a shutdown. If the pressure is too high, it could lead to increased injection pressure. Sugg. Action: Check the hydraulic pressure and the pressure setpoint at the HPS page on the MOP. Check the swashplate positions on the engine driven pumps. If all swashplates are closed to +100% running AH (or -100% running AS) on the MOP, then lower the engine load to avoid a shutdown. If there is a large hydraulic leakage it may not be possible to avoid. If the pressure is too high, inspect the oil supply line to the exhaust valves and the fuel injection for malfunctioning valves.

5116 5131

gls / 14-07-2006 10:31:10

Page 44 of 124

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. 5133012101 Pump Model Curve->Model curve integrator (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: 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: 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. 51330123 Pump Model Curve->Pump Torque Limiter Reached

Description: Pump torque limiter reached. Cause: Could be caused by a hydraulic leakage, or lack of hydraulic delivery from swashplate pumps. Effect: Engine load can be limited due to maximum swashplate pump delivery has been reached (in normal operation of these). Sugg. Action: Check for leaks in the hydraulic system. Check drain valve valves on the HCU (421 from inner pipe to drain, and 431 from double pipe to drain). Check swashplate pumps for broken shafts. Check if HP sensors are drifting. 51330501 El HPS Pump Command->El HPS 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. 513316 El HPS Pump Command->Manual HPS operation demanded

Description: Operator has commanded manual operation of HPS (Chief-level access). Cause: Caused by pressing the "Manual" button on the MOP. Effect: The HPS will "bumpless" change to Manual operation. Hence operating startup pumps will continue to operate in Manual mode. The automatic pressure control is still active in Manual mode and is using the pressure setpoint computed by the ECS. This pressure setpoint can be overruled by the operator by manually altering the pressure setpoint. When doing so, the new pressure setpoint will be used until the operator either chooses a new setpoint, or returns to Automatic mode. Sugg. Action: Automatic mode is considered safe, so when Manual mode operations are finished switch back to Automatic mode.

51330113 513316

gls / 14-07-2006 10:31:10

Page 45 of 124

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. 51332201 El HPS Pump Command->Press ctrl pump cmd (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: First, try to change pressure controlling pump from MOP A or MOP B using the Pressure Control buttons on the HPS page of Auxiliaries. If unsuccessful then, 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. 51333610 El. motor, pump 4->Startup Pump Ctrl Failed

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 startup pump operation control switch at the startup pump switchboard. The ECS expect the switch to be in the "Remote" control position. Check the cabling of the signal ID's 1217-x, 1218-x, and 1219-x between the MPC and the startup pump switchboard. Check the relays inside the startup pump switchboard. 51333710 El. motor, pump 5->Startup Pump Ctrl Failed

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 startup pump operation control switch at the startup pump switchboard. The ECS expect the switch to be in the "Remote" control position. Check the cabling of the signal ID's 1217-x, 1218-x, and 1219-x between the MPC and the startup pump switchboard. Check the relays inside the startup pump switchboard.

513318 51333710

gls / 14-07-2006 10:31:10

Page 46 of 124

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. 5138 HPS Command->No pump inlet sensors Description: No pump inlet sensors available Cause: Sensors out of signal range or cabling is malfunctioning Effect: Engine will shut down Sugg. Action: Inspect sensors and their cabling according to electrical wiring diagram 51430801 Combined HPS Cmd->Combined HPS 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. 514312 Combined HPS Cmd->Standby pump started

Description: The Standby startup pump has been started. Cause: This can be caused by the Master startup pump cannot either build-up the hydraulic pressure for engine start within an acceptable time, or cannot maintain the hydraulic pressure. Effect: The Master startup pump may be defect. There might be a defect valve so that the startup pumps cannot build up hydraulic pressure for engine start. Sugg. Action: Check for a hydraulic leak or a defect valve. If the hydraulic pressure can be maintained while the Standby pump is running, the problem could be related to either a small hydraulik leakage or a defectiv Master startup pump. The alarm will disappear again when the other startup pump is chosen as Master. 600104 Ch36,6001,Dual Fuel Limit->Suprv. Ch36,6001,Dual Fuel Limit

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Dual fuel running can no longer be used via this ECU. Sugg. Action: 600204 Ch37,6002,Prop. Clutch->Suprv. Ch37,6002,Prop. Clutch

Description: The input on this channel exceeds allowable limits Cause: The input on this input channel exceeds allowable limits Effect: Clutch status is no longer available. Can cause reduced governor performance on this ECU. Sugg. Action: 8601-A04 Ch35,8601-A,Scavenge Air Pressure (->Suprv. Ch35,8601-A,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.

5136 8601-A04

gls / 14-07-2006 10:31:10

Page 47 of 124

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. SALOG System->AssertLog Stopped

Description: The built-in event log in the MPC has stopped. This event log is used for diagnosis only. Cause: The event log stops when used storage has become invalid. Effect: There is no immediate effect, but diagnostic capabilities in case of hard- or software failures will be limited. Sugg. Action: Contact MAN B&W Diesel 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. 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: Sugg. Action: Check for possible failures in the external cabling to channels 20 to 37. Replace the fuse. SFuseF13 24V power supervision->Fuse F13 failure

Description: The alarm indicates that Fuse 13 of the specified MPC is blown. Fuse 13 protects the power outlets of: channels 40 to 47, terminal "D", channels 48 to 53, terminal "E", channels 60 and 61, terminal "H". Cause: Electrical overload or wear of the fuse. Effect: A number of the signals related to channels 40 to 61 may be wrong. Effect on engine behaviour is unknown. Sugg. Action: Check for possible failures in the external cabling to channels 40 to 61.Replace the fuse. SFuseF14 24V power supervision->Fuse F14 failure

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: 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. SFuseF9 24V power supervision->Fuse F9 failure

Description: The alarm indicates that Fuse 9 of the specified MPC is blown. Fuse 9 protects power supply connector 9 of the MPC. Cause: Electrical overload or wear of the fuse. Effect: Sugg. Action: Check for possible failures in the external cabling to connector 9. Replace the fuse.

8601-B04 SFuseF9

gls / 14-07-2006 10:31:11

Page 48 of 124

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. SInvSw System->Invalid software

Description: The MPC is running an incorrect application program Cause: Can be caused by replacing an MPC when both MOP A and MOP B are unavailable. Effect: The ECS could seriously be affected by having the MPC running incorrect software. The exact behaviour is unknown since it also depends on which MPC is involved. Sugg. Action: Switch off the involved MPC immediately. When either MOP A or MOP B is operating again, the MPC can be switched on again. When this is done, wait for the automatic preparation of the MPC to finish before the MPC will operate correctly again. 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. SPow24VB 24V power supervision->24V power B failure, connector 1C

Description: The alarm indicates that power inlet, connector 1, terminal C, is powerless. Cause: The breaker of power supply B for the specified MPC is turned off. 24V power supply B is turned off. The power cabling is defect. Effect: No immediate effect, as the MPC is supplied by power supply A. Sugg. Action: Check for the causes. 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

SInvParm SWDogDac

gls / 14-07-2006 10:31:11

Page 49 of 124

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. 010281 ECU Data->No Commands Received from ECU B

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. 0150 I/O Configuration->Sensor Fail 'Take Cmd Bridge' Description: Both Force Take Bridge 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 Bridge 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 0151 I/O Configuration->Lock in Last 'Restart Bridge' 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 0152 I/O Configuration->Sensor Fail 'Increase Lim Bridge' Description: Both Increase Limit form Bridge 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 Increase Limit form Bridge 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 0153 I/O Configuration->Sensor Fail 'Increase Lim ECR' Description: Both Increase Limit form 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 Increase Limit form 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 0154 I/O Configuration->Lock in Last 'Slow Down PreWarn' 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

010280 0154

gls / 14-07-2006 10:31:11

Page 50 of 124

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 0156 I/O Configuration->Lock in Last 'Speed Set Bridge' 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 0157 I/O Configuration->Lock in Last 'Speed Set ECR' 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 0158 I/O Configuration->Lock in Last 'Stop Cmd Bridge' 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 0159 I/O Configuration->Lock in Last 'Start Cmd Bridge' 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 0160 I/O Configuration->Lock in Last 'Stop Cmd ECR' 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 0161 I/O Configuration->Lock in Last 'Start Cmd ECR' 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 0161

gls / 14-07-2006 10:31:11

Page 51 of 124

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 0163 I/O Configuration->Lock in Last 'Astern ECR' 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 0164 I/O Configuration->Lock in Last 'Pitch Set' 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 0165 I/O Configuration->Lock in Last 'Aux Sys Ready' 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 0166 I/O Configuration->Start Failed' 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 018401 I/O Configuration->Engine Mode Request (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.

0162 018401

gls / 14-07-2006 10:31:11

Page 52 of 124

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. 03012401 ECR - Combinator Control Station->ECR - Combinator Station State (De

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. 04012401 ECR Control Station->ECR 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. 05012401 LOP Control Station->LOP 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. 065801 Ctrl Station Selection->Control station selection (Deviati

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 065801

gls / 14-07-2006 10:31:11

Page 53 of 124

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. 0661 Ctrl Station Selection->ECR-Combinator Ctrl. Station Forced Description: Engine control has been taken for ECR-Combinator control station. Cause: Forced take has been taken for ECR-Combinator. Only ECR and LOP forced take can override this command. Effect: The manouvre place is forced to ECR-Combinator and if the engine is running the speed will smoothly transit to the ECR-Combinator Handle speed setpoint. Sugg. Action: No Action 0662 Ctrl Station Selection->ECR Control Station Forced Description: Engine control has been taken in the ECR. Cause: Manual take in the ECR. Effect: The manouvre place is forced to ECR and if the engine is running the speed will smoothly transit to the ECR Handle speed setpoint. Sugg. Action: No Action 0663 Ctrl Station Selection->Bridge Control Station Forced Description: Back up control from bridge forces control to the bridge. Cause: Manual back up control from bridge. Effect: Speed set from bridge is fixed and independent of handle position on the bridge. Sugg. Action: No Action 0669 Ctrl Station Selection->Start Order Timer Out Description: The ECS (Engine Control System) has detected that the latest start attempt from the active control station has timed out. Cause: In case the Auxiliary Blowers was not running before the start attempt an automatic start of the blowers were performed. If the Blowers did not communicate back to the EICUs that they did start or never started before a predefined start interval this alarm will be given. Effect: The engine will not start and handle has to be put in stop position before a new start attempt. Sugg. Action: Check if other alarms related to the Auxiliary Blowers are currently active in the alarm list. If so rectify the problems related to the alarms. 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 0669

gls / 14-07-2006 10:31:11

Page 54 of 124

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. Note: Handle Stop on is when Handle Speed Set is zero RPM! Effect: If the engine is stopped a start from the current control position will not be possible. If the engine is running and then stopped the engine can not be started again. Sugg. Action: Check that no supervision alarms are present for either Handle stop or stop switch from the selected control station (If Bridge check J26 and J30 or if ECR check J27 and J32). 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 EICUs 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. 073501 Power Management System->Generator 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. 0750 Power Management System->Wait for Generator Conditions Description: A timer has timed out while waiting for conditions for connecting the shaft generator. Cause: The engine speed has been outside the acceptable range for connecting the shaft generator (SG) for too long after a SG connect request. Effect: No effect. Sugg. Action: Adjust speed set to be in the shaft generator (SG) speed range to make the PTO connect the SG or choose not to connect the SG 0751 Power Management System->Generator Disconnection Fail Description: A timer has timed out while waiting for a shaft generator disconnection request Cause: The conditions for running with shaft generator (SG) is not present i.e. either the actual speed is outside the acceptable SG speed range or the speed set point has been outside the acceptable SG speed range for too long or due to a Slow Down Prewarning Effect: If no action is taken the ECS will carry out a cancellable shut down request in a while. Sugg. Action: Request a disconnection of the shaft generator. 0752 Power Management System->Speed Outside PMS Range Description: Actual speed exceeds the acceptable shaft generator speed range. Cause: the speed handle is set outside the range of the shaft generator (SG) range Effect: If the speed set remains outside the shaft generator speed range it will in a certain time results in a cancellable shut down. Sugg. Action: Adjust the handle so that the speed set point comes back into the shaft generator speed range.

0670 0752

gls / 14-07-2006 10:31:11

Page 55 of 124

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. 080440 Barred Speed Range No.1->In Barred Range Alarm

Description: The actual speed has been in the barred speed range for too long. Cause: The speed set point and the actual speed does not follow. E.g. due to heavy running of the engine. Effect: No effect. Sugg. Action: Move speed handle so that actual engine speed leaves the barred speed range. 08053001 Load Program->Load Limit Integrator (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. 080640 Barred Speed Range No.2->In Barred Range Alarm

Description: The actual speed has been in the barred speed range for too long. Cause: The speed set point and the actual speed does not follow. E.g. due to heavy running of the engine. Effect: No effect. Sugg. Action: Move speed handle so that actual engine speed leaves the barred speed range. 0931 FWE - Ready->FWE-STANDBY-AT_SEA Inconsistency Description: The signals FWE, Standby or At Sea received from the Remote Control System are inconsistent. Either none or more than one of the above signals are active at the same time. Cause: The RCS using a Serial Communication line to the EICUs (J68) is not working properly or the hardwired inputs Ch41, Ch42 or Ch46 on EICU are faulty. Effect: The ECS keeps the last valid FWE, Standby or At Sea request as displayed on the MOP. Sugg. Action: 1) First try change between FWE, Standby, At Sea 2) If FWE, Standby, At Sea is hardwired to both EICUs check on MOP that one and only one of the EICU inputs Ch41, Ch42 and Ch46 are high. If not check cabling. 3) If FWE, Standby, At Sea is send by serial connection from RCS to ECS check for serical commonication alarms. 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 0931

gls / 14-07-2006 10:31:11

Page 56 of 124

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. 111201 MOP command interface->Slow Turn / Air Run Cmd (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. 112101 MOP command interface->Pitch Start Block Cancel Cmd (Devi

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. 1124 MOP command interface->Pitch Start Block Cancel Cmd Alarm Description: Start blocking due to non-zero pitch position of propeller has been cancelled. Cause: Operator has requested cancel of non-zero pitch start blocking on MOP screen Status. Effect: Disables the non zero pitch start blocking and consequently the engine start attempt is accepted at any propeller pitch. Sugg. Action: If the pitch control system is working properly move the pitch to zero position by putting active handle in neutral position, deactivate the zero pitch start blocking from the HMI and then check on MOP Status screen that there is no non-zero pitch start blocking. If start blocking is still active check the input channels regarding actual pitch to the ECS. The inputs is located on the two ECUs. If possible check pitch set point on the RCS. 130140 Slow Down Supervision->Cyl 1. 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.

111101 130140

gls / 14-07-2006 10:31:11

Page 57 of 124

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. 130142 Slow Down Supervision->Cyl 3. 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. 130143 Slow Down Supervision->Cyl 4. 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. 130144 Slow Down Supervision->Cyl 5. 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 130144

gls / 14-07-2006 10:31:11

Page 58 of 124

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. 130146 Slow Down Supervision->Cyl 7. 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. 130147 Slow Down Supervision->Cyl 8. 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. 130148 Slow Down Supervision->Cyl 9. 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 130148

gls / 14-07-2006 10:31:11

Page 59 of 124

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. 130150 Slow Down Supervision->Cyl 11. 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. 130151 Slow Down Supervision->Cyl 12. 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. 130152 Slow Down Supervision->Cyl 13. 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 130152

gls / 14-07-2006 10:31:11

Page 60 of 124

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. 130154 Slow Down Supervision->Cyl 15. 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. 130155 Slow Down Supervision->Cyl 16. 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. 130160 Slow Down Supervision->Slow Down Request due to Misfire

Description: Misfire on one or more cylinders due to absence of fuel injection. Cause: One or more CCU's are missing on the network or not in normal running mode. Effect: ME-ECS send a slow down request to the safety system. A Slow Down will subsequently be performed. Sugg. Action: 1) Check on MOP screen: Maintenance -> System View which CCU's are missing or not operating in normal mode. 2) Check for problems with the network on MOP: Maintenance -> Network Status 3) It can also be seen from the alarm list which CCU's cause the alarm.

130153 130160

gls / 14-07-2006 10:31:11

Page 61 of 124

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. 130211 Pump Control Supervision->Hydraulic HP Pump Failed on ACU2

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. 130212 Pump Control Supervision->Hydraulic HP Pump Failed on ACU3

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. 130213 Pump Control Supervision->Hydraulic HP Pump Failed on ECUA

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.

130210 130213

gls / 14-07-2006 10:31:11

Page 62 of 124

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. 130219 Pump Control Supervision->Too many HP Pump Failures

Description: The ECS (Engine Control System) has detected that two or more HP pumps are not working properly. See alarm list for information about which pumps. Cause: Two or more pumps are not working properly due to failing HP pumps (See Alarm Descriptions for failing pumps) or failing MPCs controlling the HP pumps i.e. not operating in normal running mode or disconnected both networks. Note: for installations with more than three HP pumps, pump four and five are controlled by the ECUs. Effect: Because more than one HP pump is not working properly, reversing the engine might not be possible due to the fail safe position of the HP pumps. Ship manoeuvres in Astern direction can make the ship loose engine power resulting in loss of engine control. Sugg. Action: See Alarm Descriptions for failing pumps. Check on MOP screen Maintenance that the MPCs controlling the HP pumps are operating in normal mode and connected the control network. 2010-A04 Ch25,2010-A,Slow Down->Suprv. Ch25,2010-A,Slow 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: 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. 2010-B04 Ch25,2010-B,Slow Down->Suprv. Ch25,2010-B,Slow 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: 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. 214001 I/O Configuration->Ch27,2140, Deviation Supervision (

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: 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.

130214 214001

gls / 14-07-2006 10:31:11

Page 63 of 124

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. Else if not redundant cabling: The EICU uses lock in of the last valid value i.e. It is not possible to adjust the Engine Speed from the ECR. 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. 2140-B04 Ch27,2140-B,Speed Set ECR->Suprv. Ch27,2140-B,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. Else if not redundant cabling: The EICU uses lock in of the last valid value i.e. It is not possible to adjust the Engine Speed from the ECR. 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. 2141-A04 Ch32,2141-A,Stop Cmd ECR->Suprv. Ch32,2141-A,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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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.

2140-A04 2141-A04

gls / 14-07-2006 10:31:11

Page 64 of 124

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2142-A04 Ch23,2142-A,Increase Limiter from E->Suprv. Ch23,2142-A,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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2142-B04 Ch23,2142-B,Increase Limiter from E->Suprv. Ch23,2142-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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2143-A04 Ch34,2143-A,Take command ECR->Suprv. Ch34,2143-A,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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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.

2141-B04 2143-A04

gls / 14-07-2006 10:31:11

Page 65 of 124

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2144-A04 Ch35,2144-A,Astern ECR->Suprv. Ch35,2144-A,Astern 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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2144-B04 Ch35,2144-B,Astern ECR->Suprv. Ch35,2144-B,Astern 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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2145-A04 Ch33,2145-A,Start Cmd ECR->Suprv. Ch33,2145-A,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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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.

2143-B04 2145-A04

gls / 14-07-2006 10:31:11

Page 66 of 124

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2148-A04 Ch36,2148-A,PitchSet for Lubricator->Suprv. Ch36,2148-A,PitchSet for Lub

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 corresponding input on the redundant EICU is used on both EICU's. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2148-B04 Ch36,2148-B,PitchSet for Lubricator->Suprv. Ch36,2148-B,PitchSet for Lub

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 corresponding input on the redundant EICU is used on both EICU's. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2149-A04 Ch37,2149-A,Aux. System Ready->Suprv. Ch37,2149-A,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.

2145-B04 2149-A04

gls / 14-07-2006 10:31:11

Page 67 of 124

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. 214P-A04 Description: Cause: Effect: Sugg. Action: 214P-B04 Description: Cause: Effect: Sugg. Action: 216001 I/O Configuration->Ch26,2160, Deviation Supervision ( Ch27,214P-B,Potentiometer Speed Set->Suprv. Ch27,214P-B,Potentiometer Sp Ch27,214P-A,Potentiometer Speed Set->Suprv. Ch27,214P-A,Potentiometer Sp

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: 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. 2160-A04 Ch26,2160-A,Speed Set Bridge->Suprv. Ch26,2160-A,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. Else if not redundant cabling: The EICU uses lock in of the last valid value i.e. It is not possible to adjust the Engine Speed from the Bridge. 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.

2149-B04 2160-A04

gls / 14-07-2006 10:31:11

Page 68 of 124

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. Else if not redundant cabling: The EICU uses lock in of the last valid value i.e. It is not possible to adjust the Engine Speed from the Bridge. 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. 2161-A04 Ch30,2161-A,Stop Cmd Bridge->Suprv. Ch30,2161-A,Stop Cmd Bridge

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2161-B04 Ch30,2161-B,Stop Cmd Bridge->Suprv. Ch30,2161-B,Stop Cmd Bridge

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2162-A04 Ch22,2162-A,Increase Limiter from B->Suprv. Ch22,2162-A,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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2160-B04 2162-A04 gls / 14-07-2006 10:31:12 Page 69 of 124

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2163-A04 Ch20,2163-A,Fixed RPM Command->Suprv. Ch20,2163-A,Fixed RPM Comman

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2163-B04 Ch20,2163-B,Fixed RPM Command->Suprv. Ch20,2163-B,Fixed RPM Comman

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2164-A04 Ch21,2164-A,Restart switch->Suprv. Ch21,2164-A,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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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.

2162-B04 2164-A04

gls / 14-07-2006 10:31:12

Page 70 of 124

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2165-A04 Ch31,2165-A,Start Cmd Bridge->Suprv. Ch31,2165-A,Start Cmd Bridge

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2165-B04 Ch31,2165-B,Start Cmd Bridge->Suprv. Ch31,2165-B,Start Cmd Bridge

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 216P-A04 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. Else if not redundant cabling: The EICU uses lock in of the last valid value i.e. It is not possible to adjust the Engine Speed from the Bridge. Sugg. Action: Ch26,216P-A,Potentiometer Speed Set->Suprv. Ch26,216P-A,Potentiometer Sp

2164-B04 216P-A04

gls / 14-07-2006 10:31:12

Page 71 of 124

EICUXX
216P-B04 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. Else if not redundant cabling: The EICU uses lock in of the last valid value i.e. It is not possible to adjust the Engine Speed from the Bridge. Sugg. Action: 2205-A04 Ch24,2205-A,Slow Down Pre-warning->Suprv. Ch24,2205-A,Slow Down Pre-wa Ch26,216P-B,Potentiometer Speed Set->Suprv. Ch26,216P-B,Potentiometer Sp

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 2205-B04 Ch24,2205-B,Slow Down Pre-warning->Suprv. Ch24,2205-B,Slow Down Pre-wa

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. Else if not redundant cabling: The EICU uses lock in of the last valid value. 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. 40 EICU->Modbus-RCS Connection Test Active Description: In EICU configuration mode, the modbus is chosen to be in connection test Cause: In EICU configuration mode the parameter is set to Yes: I/O Configuration -> Configuration Options -> Non or Old Application Options -> Modbus-RCS Connection Test -> Yes Effect: It is not possible to have normal operation via serial connection. Sugg. Action: After serial connection test, the parameter described in cause should be set to No ModbusTA Modbus-RCS->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.

216P-B04 ModbusTA

gls / 14-07-2006 10:31:12

Page 72 of 124

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. SALOG System->AssertLog Stopped

Description: The built-in event log in the MPC has stopped. This event log is used for diagnosis only. Cause: The event log stops when used storage has become invalid. Effect: There is no immediate effect, but diagnostic capabilities in case of hard- or software failures will be limited. Sugg. Action: Contact MAN B&W Diesel SAR-ACU1 System Status->App. not running on ACU1

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-ACU2 System Status->App. not running on ACU2

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-ACU3 System Status->App. not running on ACU3

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.

RCSVarAA SAR-ACU3

gls / 14-07-2006 10:31:12

Page 73 of 124

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-AXU1 System Status->App. not running on AXU1

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 System Status->App. not running on CCU1

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-CCU10 System Status->App. not running on CCU10

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 SAR-CCU1

gls / 14-07-2006 10:31:12

Page 74 of 124

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-CCU12 System Status->App. not running on CCU12

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-CCU13 System Status->App. not running on CCU13

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-CCU14 System Status->App. not running on CCU14

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 SAR-CCU1

gls / 14-07-2006 10:31:12

Page 75 of 124

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-CCU16 System Status->App. not running on CCU16

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-CCU2 System Status->App. not running on CCU2

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-CCU3 System Status->App. not running on CCU3

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 SAR-CCU3

gls / 14-07-2006 10:31:12

Page 76 of 124

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-CCU5 System Status->App. not running on CCU5

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-CCU6 System Status->App. not running on CCU6

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-CCU7 System Status->App. not running on CCU7

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 SAR-CCU7

gls / 14-07-2006 10:31:12

Page 77 of 124

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-CCU9 System Status->App. not running on CCU9

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-ECUA System Status->App. not running on ECUA

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-ECUB System Status->App. not running on ECUB

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 SAR-ECUB

gls / 14-07-2006 10:31:12

Page 78 of 124

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-EICUB System Status->App. not running on EICUB

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-ESU System Status->App. not running on ESU

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. 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. SEICU System->Global Params. inconsist

Description: The ECS consists of multiple parameters some of which normally needs to be exactly alike. If these parameters values are not equal this alarm is given. Cause: Parameters changed on the MOP and send to redundant units are not received and accepted on both units resulting in diverging global parameter values. Effect: The ECS might not function optimally due to inconsistent parameters. Sugg. Action: 1. Readjust the parameter that caused the trouble 2. Make sure that the ECU and CCU units are not halted. Check this on MOP screen: Maintenance: System view I/O Test

SAR-EICU SEICU

gls / 14-07-2006 10:31:12

Page 79 of 124

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. SFuseF13 24V power supervision->Fuse F13 failure

Description: The alarm indicates that Fuse 13 of the specified MPC is blown. Fuse 13 protects the power outlets of: channels 40 to 47, terminal "D", channels 48 to 53, terminal "E", channels 60 and 61, terminal "H". Cause: Electrical overload or wear of the fuse. Effect: A number of the signals related to channels 40 to 61 may be wrong. Effect on engine behaviour is unknown. Sugg. Action: Check for possible failures in the external cabling to channels 40 to 61.Replace the fuse. SFuseF14 24V power supervision->Fuse F14 failure

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: No effect. 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. SFuseF9 24V power supervision->Fuse F9 failure

Description: The alarm indicates that Fuse 9 of the specified MPC is blown. Fuse 9 protects power supply connector 9 of the MPC. Cause: Electrical overload or wear of the fuse. Effect: No effect. Sugg. Action: Check for possible failures in the external cabling to connector 9. Replace the fuse. 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. SInvSw System->Invalid software

Description: The MPC is running an incorrect application program Cause: Can be caused by replacing an MPC when both MOP A and MOP B are unavailable. Effect: The ECS could seriously be affected by having the MPC running incorrect software. The exact behaviour is unknown since it also depends on which MPC is involved. Sugg. Action: Switch off the involved MPC immediately. When either MOP A or MOP B is operating again, the MPC can be switched on again. When this is done, wait for the automatic preparation of the MPC to finish before the MPC will operate correctly again.

SFuseF12 SInvSw

gls / 14-07-2006 10:31:12

Page 80 of 124

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. SN0-ACU1 System Status->Net A not connected to ACU1

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.

SMBsTOAl SN0-ACU1

gls / 14-07-2006 10:31:12

Page 81 of 124

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. SN0-ACU3 System Status->Net A not connected to ACU3

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. SN0-ACU2 SN0-ACU3 gls / 14-07-2006 10:31:12 Page 82 of 124

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 SN0-ACU4

gls / 14-07-2006 10:31:12

Page 83 of 124

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 SN0-AXU1

gls / 14-07-2006 10:31:12

Page 84 of 124

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. SN0-CCU10 System Status->Net A not connected to CCU10

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. SN0-CCU1 SN0-CCU1 gls / 14-07-2006 10:31:12 Page 85 of 124

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. SN0-CCU12 System Status->Net A not connected to CCU12

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. SN0-CCU1 SN0-CCU1 gls / 14-07-2006 10:31:12 Page 86 of 124

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. SN0-CCU14 System Status->Net A not connected to CCU14

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. SN0-CCU1 SN0-CCU1 gls / 14-07-2006 10:31:12 Page 87 of 124

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. SN0-CCU16 System Status->Net A not connected to CCU16

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. SN0-CCU1 SN0-CCU1 gls / 14-07-2006 10:31:12 Page 88 of 124

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. SN0-CCU3 System Status->Net A not connected to CCU3

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. SN0-CCU2 SN0-CCU3 gls / 14-07-2006 10:31:12 Page 89 of 124

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. SN0-CCU5 System Status->Net A not connected to CCU5

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. SN0-CCU4 SN0-CCU5 gls / 14-07-2006 10:31:12 Page 90 of 124

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. SN0-CCU7 System Status->Net A not connected to CCU7

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. SN0-CCU6 SN0-CCU7 gls / 14-07-2006 10:31:13 Page 91 of 124

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. SN0-CCU9 System Status->Net A not connected to CCU9

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. SN0-CCU8 SN0-CCU9 gls / 14-07-2006 10:31:13 Page 92 of 124

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. SN0-ECUB System Status->Net A not connected to ECUB

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. SN0-ECUA SN0-ECUB gls / 14-07-2006 10:31:13 Page 93 of 124

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. SN0-EICUB System Status->Net A not connected to EICUB

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. SN0-EICU SN0-EICU gls / 14-07-2006 10:31:13 Page 94 of 124

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. SN0-MOPA System Status->Net A not connected to MOPA

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. SN0-ESU SN0-MOP gls / 14-07-2006 10:31:13 Page 95 of 124

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. SN1-ACU1 System Status->Net B not connected to ACU1

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. SN0-MOP SN1-ACU1 gls / 14-07-2006 10:31:13 Page 96 of 124

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. SN1-ACU3 System Status->Net B not connected to ACU3

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-ACU2 SN1-ACU3 gls / 14-07-2006 10:31:13 Page 97 of 124

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. SN1-AXU1 System Status->Net B not connected to AXU1

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-ACU4 SN1-AXU1 gls / 14-07-2006 10:31:13 Page 98 of 124

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. SN1-CCU10 System Status->Net B not connected to CCU10

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-CCU1 SN1-CCU1 gls / 14-07-2006 10:31:13 Page 99 of 124

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. SN1-CCU12 System Status->Net B not connected to CCU12

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-CCU1 SN1-CCU1 gls / 14-07-2006 10:31:13 Page 100 of 124

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. SN1-CCU14 System Status->Net B not connected to CCU14

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-CCU1 SN1-CCU1 gls / 14-07-2006 10:31:13 Page 101 of 124

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. SN1-CCU16 System Status->Net B not connected to CCU16

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-CCU1 SN1-CCU1 gls / 14-07-2006 10:31:13 Page 102 of 124

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. SN1-CCU3 System Status->Net B not connected to CCU3

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-CCU2 SN1-CCU3 gls / 14-07-2006 10:31:13 Page 103 of 124

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. SN1-CCU5 System Status->Net B not connected to CCU5

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-CCU4 SN1-CCU5 gls / 14-07-2006 10:31:13 Page 104 of 124

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. SN1-CCU7 System Status->Net B not connected to CCU7

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-CCU6 SN1-CCU7 gls / 14-07-2006 10:31:13 Page 105 of 124

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. SN1-CCU9 System Status->Net B not connected to CCU9

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-CCU8 SN1-CCU9 gls / 14-07-2006 10:31:13 Page 106 of 124

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. SN1-ECUB System Status->Net B not connected to ECUB

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-ECUA SN1-ECUB gls / 14-07-2006 10:31:13 Page 107 of 124

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. SN1-EICUB System Status->Net B not connected to EICUB

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-EICU SN1-EICU gls / 14-07-2006 10:31:13 Page 108 of 124

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. SN1-MOPA System Status->Net B not connected to MOPA

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-ESU SN1-MOP gls / 14-07-2006 10:31:13 Page 109 of 124

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. SNA-ACU1 System Status->MPC ACU1 unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SN1-MOP SNA-ACU1

gls / 14-07-2006 10:31:14

Page 110 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-ACU3 System Status->MPC ACU3 unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-ACU2 SNA-ACU3

gls / 14-07-2006 10:31:14

Page 111 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-AXU1 System Status->MPC AXU1 unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-ACU4 SNA-AXU1

gls / 14-07-2006 10:31:14

Page 112 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-CCU10 System Status->MPC CCU10 unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-CCU1 SNA-CCU1

gls / 14-07-2006 10:31:14

Page 113 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-CCU12 System Status->MPC CCU12 unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-CCU1 SNA-CCU1

gls / 14-07-2006 10:31:14

Page 114 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-CCU14 System Status->MPC CCU14 unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-CCU1 SNA-CCU1

gls / 14-07-2006 10:31:14

Page 115 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-CCU16 System Status->MPC CCU16 unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-CCU1 SNA-CCU1

gls / 14-07-2006 10:31:14

Page 116 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-CCU3 System Status->MPC CCU3 unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-CCU2 SNA-CCU3

gls / 14-07-2006 10:31:14

Page 117 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-CCU5 System Status->MPC CCU5 unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-CCU4 SNA-CCU5

gls / 14-07-2006 10:31:14

Page 118 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-CCU7 System Status->MPC CCU7 unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-CCU6 SNA-CCU7

gls / 14-07-2006 10:31:14

Page 119 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-CCU9 System Status->MPC CCU9 unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-CCU8 SNA-CCU9

gls / 14-07-2006 10:31:14

Page 120 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-ECUB System Status->MPC ECUB unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-ECU SNA-ECUB

gls / 14-07-2006 10:31:14

Page 121 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-EICUB System Status->MPC EICUB unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-EICU SNA-EICU

gls / 14-07-2006 10:31:14

Page 122 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNA-MOPA System Status->MPC MOPA unavailable

Description: The affected unit can not be seen on either of the networks (segment A and B) by the EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare.

SNA-ESU SNA-MOP

gls / 14-07-2006 10:31:14

Page 123 of 124

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 EICUs. Special case: One of the EICUs are disconnected both control network results in alarms form this EICU that all other MPCs 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 (MPCs connector J65 and J66 ) 4. The network cables to the unit are damaged. Effect: If one or two MOPs are missing on the network it will not affect the running of the engine. For redundant units i.e. EICUs and ECUs: 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. If the alarm is due to a missing MPC on the network: 1. Check that the unit is in normal running mode (LED indication on MPC is green). If the unit is in test mode then restart the unit in normal mode. 2. Make sure that the control network is properly connected and not damaged 3. Replace the MPC with spare. SNETX System Status->Controlnetwork is crossconnected

Description: The network is cross connected on one or more Multi Purpose Controllers (MPC's) Cause: One or both of the following two possibilities have occurred: 1) Network cable A has been connected to network channel B. 2) Network cable B has been connected to network channel A. Effect: No effect. Sugg. Action: Go to the Newtork Status Screen on the MOP-A or MOP-B (Maintainence -> Network Status) The Network Status Screen wil indicate which Nodes are affected/cross connected. Go to the MPC's and check cabling. 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. SPow24VB 24V power supervision->24V power B failure, connector 1C

Description: The alarm indicates that power inlet, connector 1, terminal C, is powerless. Cause: The breaker of power supply B for the specified MPC is turned off. 24V power supply B is turned off. The power cabling is defect. Effect: No immediate effect, as the MPC is supplied by power supply A. Sugg. Action: Check for the causes. 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

SNA-MOP SWDogDac

gls / 14-07-2006 10:31:14

Page 124 of 124