Engine Telegraph and Bridge Remote Control Systems

The engine order telegraph (EOT) and bridge remote control system is the shipboard arrangement that allows the navigating bridge to command main-engine speed and direction and receive confirmation that the command has been accepted and executed. On a legacy electric or mechanical telegraph, the bridge moves a handle to a discrete position (Full Ahead, Half Astern, Stop, and so on), a bell or buzzer sounds in the engine room, and the engine room operator moves the matching lever to acknowledge and then acts on the command. On a modern ship with bridge remote control, the bridge maneuvering handle sets a speed demand directly into the engine control system; the engine room and a local-stand station remain alternative control positions available for transfer. Every movement of the handle, every transfer of control, and every alarm is time-stamped, logged, and fed to the Voyage Data Recorder (VDR) for casualty investigation.

Background: from voice pipes to electronic control

Steamship bridges of the mid-nineteenth century communicated engine commands by voice tube, shouted between a helmsman on the paddle-box and a stoker standing at the furnace door, or by a simple bell rope that rang a bell in the stokehold. The first engine telegraph patents appeared in the 1860s in Britain and the United States as steam engine power grew beyond what a voice-call could safely govern. Jesse Reno filed one of the early designs around 1870; by the 1880s Chadburn and Syren were the dominant British makers, and their brass-and-cast-iron designs, with a rotating pointer in a circular dial housing, became a fixture on warships and mail steamers.

The Chadburn design used a chain or shaft drive to link the bridge handle to an identical unit in the engine room, so that moving the bridge pointer physically moved the engine room pointer. The engine room attendant would then confirm by resetting their lever, completing an electrical circuit that rang a reply bell on the bridge. That confirm-and-acknowledge sequence is the ancestor of every modern control-position protocol. Chadburn supplied telegraphs to the Royal Navy through both World Wars; the RMS Titanic carried Chadburn mechanical telegraphs, and the “Half Ahead” bell-book entry at 23:40 on 14 April 1912 is preserved in the US Senate inquiry record.

Electric telegraphs, using bridge and engine room transmitter/receiver pairs linked by a low-voltage electrical circuit, became standard from the 1920s onward. The electrical link allowed bridge-wing telegraphs at the port and starboard bridge wings for maneuvering, so the officer could command the engine while watching the pier approach. A single master transmitter on the center console sent the ordered position; wing units sent the same signal. The engine room unit displayed the ordered position and the engine room attendant acknowledged by matching the lever.

Automated bridge remote control emerged in the 1960s alongside electronically governed medium-speed diesel installations. The first commercial direct bridge control systems appeared on tankers and bulk carriers with Kongsberg (then Norcontrol) and Woodward/DEUM governor-linked installations in the early 1970s. By the mid-1980s, SOLAS amendments had codified bridge remote control as a standard feature with explicit regulatory requirements, and the legacy electric telegraph had transitioned from primary control to mandatory backup.

The legacy electric telegraph: handle, dial, bell, and bell book

The electric telegraph in its developed form consists of two matched transmitter-receiver units, one at the bridge console and one in the engine control room, plus bridge-wing auxiliary units. Each unit carries:

• A mechanical handle (or lever) with detents at each command position
• A circular or arc-shaped dial face showing the ordered position by a pointer
• A bell or buzzer that sounds on both units when the bridge issues a new command
• A second pointer that tracks the engine room reply position
• A 24-volt DC battery-backed power circuit that survives main power failure

The bridge officer moves the handle to the desired position. The bridge unit sends an electrical signal; the engine room bell rings and the pointer swings. The engine room attendant moves the matching lever to acknowledge, completing a return circuit that rings a reply bell at the bridge and moves the reply pointer to match the ordered position. The bridge officer sees two aligned pointers and knows the command has been received. Only then does the engine room act on the command.

The bell book is the officer’s paper record of every telegraph movement during a maneuvering sequence: time, ordered position, and any remarks (such as engine room verbal report of main engine response). Port authorities in many jurisdictions require the bell book as documentary evidence during harbor investigations; the Panama Canal Authority and the Singapore MPA both require a legible bell book covering the transit.

On a modern ship, the bell book is partially replaced by the telegraph logger’s printed or electronic record, but the duty officer is still expected to annotate it with situational remarks that the electronic log does not capture.

Bridge-wing telegraphs

Maneuvering from the bridge wing is standard practice when berthing or unberthing, because the officer at the wing can see the pier distance directly. Wing telegraph units are electrically linked to the master console and send the same signal; only one unit at a time is the active command source (the officer selects center or wing via a wing-takeover switch). The wing unit typically also carries a helm control button so the officer can order a rudder movement without reaching the center console.

Wing telegraph units are required to show the ordered position locally and to ring the engine room bell when a new order is placed. Both the port and starboard wings carry independent units so the officer can move to whichever side gives the better view.

Modern bridge remote control: direct speed command

On a ship equipped with bridge remote control, the bridge maneuvering handle feeds an analog or digital speed demand directly into the engine control system. The handle is not a telegraph in the traditional sense: it sets a continuous speed setpoint rather than selecting a discrete position. The engine control system, acting through the engine governor, adjusts fuel injection to achieve the demanded speed.

The bridge handle on a modern mainline engine installation (such as a MAN B&W ME-C or a Wartsila RT-flex) typically spans approximately 270 degrees of rotation from Full Astern to Full Ahead, with an electronic detent at the Stop position and a physical stop at each end. The handle sends a 4-20 mA analog signal, or a CAN bus digital message, to the engine control module. Modern installations use digital communication throughout: the WinGD X-DF and the MAN B&W ME-GI engines communicate bridge handle position over a CANopen or EtherNet/IP network to the engine control module, which in turn commands the electronic injection and fuel-gas valve systems.

The bridge display shows actual shaft speed in rpm, propeller shaft direction (ahead or astern), and on electronically controlled engines, engine load percentage and the current limit imposed by the load program. Some installations also display the number of cylinder units running on fuel gas versus pilot oil (for dual-fuel engines), turbocharger speed, and exhaust temperature spread across cylinders, all routed from the engine room automation system to a bridge-side mimic panel.

Maneuvering console layout

A typical bridge maneuvering console on a post-2010 vessel carries:

The maneuvering console is separate from the main navigation consoles and is typically positioned at the forward centerline of the bridge or on the port-side bridge wing. On VLCC and large bulk carrier designs, a second maneuvering console at the bridge wing is standard for berthing operations.

Control positions: bridge, engine control room, and local stand

SOLAS Chapter II-1 Regulation 31 (remote control of propulsion machinery from the navigating bridge) requires, on ships to which the regulation applies, that at least three control positions be provided for the main engine:

1. The navigating bridge (primary remote control)
2. The engine control room (ECR) or equivalent enclosed engineering control station
3. The local stand on the engine itself (direct mechanical or electronic control at the machine)

The regulation requires that control can be transferred between these positions without loss of control and without the engine being left in an undetermined state. No arrangement is acceptable under which two positions hold simultaneous authority. The IACS Unified Requirement UR M65 (Bridge Control and Monitoring of Propulsion Machinery) expands on this requirement: transfer initiation at the requesting station must trigger a visual and audible request at the current controlling station, and the transfer completes only when the current controlling station explicitly releases control.

The following table sets out the roles of the three positions under normal and emergency conditions.

The local stand takes precedence over both remote stations when it is selected as the active position. This is the fail-safe: if the bridge-ECR network fails, the engine room can always revert to direct manual control at the engine. IACS UR M65 Section 4 specifies that the local stand must remain operable regardless of the state of the remote control network or power distribution, using a separate local control circuit.

Transfer protocol step-by-step

A typical bridge-to-ECR transfer sequence on a compliant installation:

1. Chief engineer requests transfer from the ECR transfer button. An “ECR REQUESTS CONTROL” lamp illuminates at the bridge console.
2. The bridge officer has sole discretion to accept or reject. If accepted, the officer presses the “TRANSFER TO ECR” button on the bridge console.
3. The transfer lamp changes from “ECR requests” to “ECR ACTIVE” at both stations simultaneously. The bridge-side handle is now advisory only.
4. The ECR engineer acknowledges with a separate lamp confirmation. The bridge still shows ordered and actual speed but cannot alter them until control is returned.
5. When the bridge wants control back, the officer presses “REQUEST CONTROL.” The ECR acknowledges, releases, and the bridge handle becomes active again.

At no step is there a moment when neither station holds control. Class rules (DNV Rules for Ships Part 4 Chapter 2 Section 2, Lloyd’s Register Machinery Rules Chapter 5) verify this protocol during type approval of the bridge control system and during commissioning trials. Survey records for the transfer protocol test are part of the delivery documentation set for newbuildings.

Telegraph logger, bell book, and VDR integration

The telegraph logger is a dedicated time-stamping unit that records every change of state of the bridge handle, every bridge-wing takeover, every ECR or local transfer event, and every acknowledged command, each tagged with UTC time from the ship’s master clock (GPS-disciplined on virtually all post-2005 installations). The logger writes to a non-volatile memory (EEPROM or flash) and optionally prints a continuous paper strip.

IMO Resolution MSC.333(90), the current VDR performance standard, requires engine order and response as mandatory parameters (parameter group “Rudder and engine order and response” in Annex 1 Table 1 of the standard). The IEC 61996-1 standard that implements it specifies the sampling rate (minimum once per second for engine order, minimum once per second for shaft speed response) and the data format. The VDR’s data acquisition unit reads the telegraph logger output over an NMEA 0183 or IEC 61162-1 serial link, or over a proprietary I/O bus, and writes it to the protected capsule alongside the radar image, bridge audio, ECDIS image, and GNSS position.

The practical consequence is that every major casualty investigation involving propulsion has access to a time-resolved record of what the bridge ordered, when it was acknowledged, and what the shaft actually did. The investigation of the container ship Rena grounding off New Zealand in October 2011 used the VDR telegraph log to confirm that no speed reduction was ordered before the grounding, contradicting initial crew statements. The investigation of the Sewol ferry capsize in April 2014 relied on VDR-recovered engine and rudder order data to reconstruct the sequence of maneuvers.

On ships where bridge remote control is the primary mode and the handle position itself is the “order,” the VDR records handle angle (as a speed demand) rather than a discrete telegraph position. The IMO has not yet updated MSC.333(90) to standardize the encoding of continuous-handle-angle data versus discrete telegraph positions, so individual class societies and flag states have issued supplementary circulars; the DNV Approval of Service Note TN-0513 (2019) addresses this gap for electronically governed two-stroke installations.

Alarms and safety interlocks

Wrong-way alarm

The wrong-way alarm (also called off-normal or reverse-direction alarm) is required by SOLAS II-1/31.3 on ships with bridge remote control of propulsion. It activates when the shaft rotation direction does not correspond to the ordered direction within a time limit set during commissioning (typically 30 to 90 seconds after the command, depending on engine type and the reversal sequence duration). The alarm sounds on the bridge and in the engine room simultaneously.

The alarm is particularly important on fixed-pitch propeller ships because an astern command requires the main engine to stop, reverse internal timing, and restart in the opposite direction, a sequence that takes 40 to 120 seconds on a large two-stroke engine. If a fault in the reversing system prevents the engine from completing the sequence, the alarm is the bridge’s first indication. On a controllable-pitch propeller (CPP) installation, pitch reversal is faster and the wrong-way alarm window is correspondingly shorter.

Off-normal alarm for remote control failure

If the automatic remote control system cannot maintain the ordered speed (for example because a governor fault has caused the engine to run at a different speed than commanded), an off-normal alarm sounds on the bridge. SOLAS II-1/31.4 requires this alarm. The alarm prompt varies: some systems alarm when actual speed deviates more than 10 rpm from ordered speed for more than 30 seconds; others use a percentage deviation threshold. The setpoints are class-approved during type approval.

Overload and safety cutout interlocks

The bridge remote control system is subordinate to the engine’s safety protection system. The engine emergency stop circuits operate independently of and above the bridge control system: a low lube-oil pressure trip, a high cooling-water temperature trip, or an overspeed trip cuts fuel regardless of the bridge handle position. These trips cannot be blocked from the bridge. The bridge sees a “SLOW DOWN” or “SHUT DOWN” alarm routed from the engine room alarm system; it cannot cancel the trip condition remotely.

In addition to trips, “slow-down” conditions (also called “reductions”) reduce engine speed to a safe level without shutting down. A high thrust-bearing temperature slow-down, for example, will limit the engine to a percentage of MCR until the bearing temperature drops. The bridge remote control system receives the slow-down command from the engine alarm system and caps the achievable speed demand accordingly; the bridge officer cannot command beyond the capped limit until the condition clears.

Load program and barred speed range avoidance

The load program

The load program (or load-up program) is a software module in the engine control system that limits the rate of increase of speed and load in response to bridge commands. Its purpose is to protect the engine during acceleration from conditions where thermal equilibrium has not been reached: cylinder liners, piston rings, and exhaust valves are more susceptible to scoring and thermal fatigue during rapid load swings.

A typical MAN B&W ME-C load program restricts acceleration from below 25% load to 100% load to a minimum ramp time of approximately 20 to 30 minutes in the standard cold-load-up profile. The same engine can execute a rapid full-load program (for maneuvering or emergency) that compresses this to 3 to 5 minutes, but at higher thermal stress. The bridge officer selects between “normal” and “maneuvering” load programs via the bridge console; the selection is logged.

During the load-up ramp, the bridge handle may be set to Full Ahead but the engine will not reach full rpm until the ramp completes. The bridge display shows a “LOAD PROGRAM ACTIVE” indication so the officer knows the engine is accelerating normally under program control and has not malfunctioned.

The load-down program (deceleration) is typically less restrictive than load-up because rapid deceleration has lower thermal consequences, though it still limits the rate to protect turbocharger surge margins on the way down.

Barred speed range avoidance

Two-stroke and some medium-speed four-stroke marine engines have barred speed ranges (also called critical speed ranges or prohibited speed zones) where torsional resonance between the crankshaft, propeller shaft, and propeller blade frequency would cause excessive vibration. Typical barred speed ranges for a large two-stroke engine lie between 40% and 65% MCR speed. The engine control system’s bridge remote control module includes a “jump-through” function that automatically accelerates through the barred range at the maximum permitted acceleration rate rather than holding speed within the range.

If the bridge orders a speed within the barred range, the bridge control system displays the ordered speed but passes a command to the governor that drives the engine through the barred range to the nearest boundary. If the officer orders below the lower boundary, the engine slows to the lower boundary and holds; if the officer orders above the upper boundary, the engine accelerates through to above the upper boundary. The bar range limits and the jump-through behavior are defined in the engine maker’s maker’s sea-trial acceptance document and in the class-approved operational manual.

IACS Unified Requirement M65 Section 7 requires that the bridge control system automatically enforce barred speed avoidance and that the bridge display indicate when automatic jump-through is in progress.

SOLAS Chapter II-1 requirements for bridge control of propulsion

SOLAS Chapter II-1 Part E (“Additional Requirements for Periodically Unattended Machinery Spaces”) and Chapter II-1 Regulation 31 (“Remote control of propulsion machinery and boilers from the navigating bridge”) together set the mandatory architecture for bridge propulsion control on ships subject to the convention.

Regulation 31 applies to ships on international voyages. It requires:

1. The main propulsion machinery and auxiliary equipment must be operable from the navigating bridge.
2. The navigating bridge must have an indicator of the speed and direction of the propeller shaft.
3. The engine must be stoppable from the navigating bridge in any circumstances.
4. Where remote control of propulsion from the bridge is provided, it must be possible to transfer to control from the engine room (and from the local stand), with means to ensure that only one control position is active at any time.
5. An audible and visual alarm on the bridge is required when the automatic bridge control system cannot maintain the ordered speed.
6. For ships that are also required to comply with the UMS requirements (Regulation 46 and Part E), additional bridge alarm requirements apply.

The regulation also requires that instructions on the operation of the remote control system be available at the bridge; in practice, this means a laminated instruction card at the maneuvering console.

The “stop from the bridge” requirement

Regulation 31.2.3 requires specifically that the engine can be stopped from the navigating bridge at any time. This requirement is not satisfied by the ability to order Stop via the telegraph alone; the regulation requires that a physical stop function exists at the bridge that cuts engine speed regardless of control position. On modern ships, this is implemented as a bridge-side “emergency slow down” or “engine stop” button that is wired directly to the engine safety system, bypassing the bridge control network. It is distinct from the maneuvering handle stop position.

The bridge emergency stop button is tested at every annual survey by the attending class surveyor. Survey records must show that the stop function operated within the specified time (class rules typically require engine speed to drop below a defined threshold within 60 seconds of the bridge stop command).

UMS implications: the bridge becomes the engine room

On ships certified for Unattended Machinery Space (UMS) operation under SOLAS Chapter II-1 Part E, the engine room runs without a watchkeeper for periods of up to 24 hours (for most class societies; DNV and Lloyd’s allow up to 24 hours continuously; some flag states allow 16 hours). During this time, the bridge is the effective watch-keeping station for the engine room. All alarms from the engine room alarm system are repeated to the bridge alarm panel, the duty officer responds to them, and the decision to call the engineer from standby rests with the duty officer.

The consequence for the bridge control and telegraph system is that the bridge console must display a more complete engine state than it would on a traditional attended-machinery-space ship. IACS UR M47 (Periodically Unattended Machinery Spaces) Section 8 specifies the minimum bridge alarm set:

• Main engine revolution counter (shaft speed)
• Main engine overload (actual load exceeding ordered load by more than a threshold)
• Main engine slow-down (any active slow-down condition)
• Main engine shut-down (any active emergency shut-down trip)
• Steering gear failure
• Bilge high-level alarms in the engine room, fore peak, and aft peak
• Fuel oil service tank low level
• Lubricating oil service tank low level
• Cooling water temperature high
• Starting air pressure low

On a UMS ship, all of these alarms arrive at the bridge console, typically integrated into the bridge alarm management system. The officer of the watch cannot “silence” an alarm without taking an action logged in the alarm system; a silent alarm can be escalated automatically to a backup alarm (typically in the officer-on-call cabin) if not acknowledged within a set period (5 minutes is a typical class-rule limit).

The engine telegraph system on a UMS ship is expected to be fully operational from the bridge at all times during unattended periods. A fault in the bridge control system that leaves the engine running but with no acknowledged active control position would require the OOW to call the duty engineer and restore manned control, terminating the UMS period. Class rules require that a bridge control system fault triggers an alarm at the bridge and in the duty engineer’s cabin.

Telegraph orders: standard positions and typical rpm

The traditional telegraph positions have never been standardized by an IMO resolution; the IMO leaves the exact positions to national administration and operator practice. However, the positions below are universal across the major maritime nations and are consistent with the wording in SOLAS, STCW, and class rules where telegraph orders appear:

The percentage figures are typical for a slow-speed two-stroke engine on a fixed-pitch propeller. CPP ships use different governor set-points because pitch control means the engine can run at constant speed while varying thrust. The manufacturer’s sea-trial protocol defines the exact rpm for each telegraph position, and those values are entered into the vessel’s bridge instruction card and the ship-specific maneuvering information booklet.

The “Emergency Full Astern” or “Crash Stop” command is distinct from “Full Astern.” Crash Stop combines an immediate Full Astern telegraph, maximum possible acceleration of the engine in reverse, and on some ships activation of an emergency reverse sequence that bypasses the load program. MAN Energy Solutions’ crash-stop documentation for the ME-C engine series defines the stopping distance and time from full sea speed as a function of engine type and displacement; for a VLCC at laden full speed, the stopping distance is typically 2.5 to 3.5 nautical miles.

Approved makers and type approval

Bridge remote control systems are type-approved by class societies before fitting on any vessel. The type approval covers the hardware (transmitters, receivers, handles, displays), the software (load program, barred-speed jump-through, transfer protocol), and the interface definitions (NMEA/IEC 61162 output for the VDR, I/O to the engine control module). Major suppliers whose systems hold current class approvals from all five major IACS member societies (DNV, Lloyd’s, ABS, BV, ClassNK) include:

• Kongsberg Maritime (Norway): K-Bridge integrated bridge and engine telegraph systems
• Wärtsilä (Finland): Nacos Platinum bridge and propulsion control, including telegraph emulation
• Rolls-Royce Marine / Kongsberg (Norway): integrated solutions for medium-speed diesel and LNG vessels
• Raytheon Anschütz (Germany): bridge control and telegraph for naval and commercial vessels
• Nakashima Propeller (Japan): CPP-integrated bridge control
• MAN Energy Solutions (Germany/Denmark): engine manufacturer’s own control system interface for ME-C and ME-GI engines

Class type approval for a bridge remote control system covers the complete functional test suite at the maker’s factory, including simulated wrong-way alarm, load-program behavior, transfer protocol under simulated network fault, and VDR data output validation. Commissioning trials on the newbuilding vessel then verify the same suite in the installed configuration before delivery.

Operational practice during port approach and departure

The sequence of control transitions during a typical port arrival reflects the layered authority of the bridge control system.

At the outer anchorage or pilot boarding ground, the ship is at sea-passage bridge control with autopilot engaged. The master transfers the autopilot to manual helm and notifies the engine room that maneuvering is about to begin. The engine room duty engineer confirms readiness and may switch to a maneuvering mode on the governor system (a faster load-response setting than the sea-passage governor setting). The ECR engineer stands by at the ECR panel.

When the pilot boards, the master briefs the pilot on engine characteristics: minimum ahead speed before steerageway is lost, maximum available astern thrust, expected time to first astern response (the engine reversal sequence time), and any temporary limitations (for example, a cylinder cut-out due to maintenance). The pilot takes the maneuvering handle but the master retains command responsibility and authority to intervene.

During the berth approach, the bridge officer (or pilot) uses the bridge maneuvering handle with frequent order changes. The telegraph logger is running continuously. The ECR duty engineer monitors engine parameters and is prepared to take manual ECR control if the bridge control system fails.

At the berth, after the mooring lines are secured, the main engine is typically set to Stop and the engine room confirmed as available for standby. The engine remains on standby, not shut down, until the harbor pilot disembarks or the port authority clears the vessel. At that point the OOW and chief engineer agree a “finished with engines” (FWE) signal, which some ships still exchange using the old telegraph (one ring, one ring in reply, then the telegraph moved to “finished with engines”), while others use a verbal exchange and the logger records the final handle position.

Limitations

Bridge remote control systems have operational and engineering limits that practitioners need to know.

Network dependency. Modern bridge control systems rely on shipboard ethernet or CAN bus networks to connect the bridge handle to the engine control module. A network fault (damaged cable, corrupted switch firmware, EMI from a poorly isolated high-current cable) can interrupt the control link. Class rules require a watchdog timer: if the engine control module does not receive a valid handle signal within 2 to 5 seconds, it defaults to a safe state (typically holding the last valid speed demand or reducing to a low-load position). But the bridge officer may not immediately know whether a network fault has occurred or whether the engine is simply responding slowly to a load program. The off-normal alarm is the primary indicator, but its 30-second delay means a ship at close quarters has limited maneuvering options during a network outage.

Load program versus maneuvering urgency. The load program is a protection function that cannot be easily overridden; even in maneuvering mode, minimum load-change ramp times apply. During a close-quarters situation requiring rapid deceleration, the bridge officer cannot demand more from the engine than the load program permits. Pilots and masters who have spent careers on steam turbine ships (where power response is almost instantaneous) sometimes underestimate the 40-to-90-second engine reversal time on a large two-stroke diesel.

Legacy telegraph battery life. The backup electric telegraph depends on a 24V DC battery that should be tested at each annual survey. In practice, battery condition on the backup telegraph is one of the deficiencies most frequently cited by port state control inspectors under Paris and Tokyo MOU inspections. A failed battery means the backup is inoperable precisely when the primary system has failed.

CPP interaction. On controllable-pitch propeller ships, the bridge control system manages both engine speed and pitch angle through a combined lever. The interaction between pitch and speed during rapid maneuvers is complex: a rapid pitch reversal at high engine speed can cause propeller cavitation, shaft vibration, and turbocharger surge. Class-approved pitch-speed combinators limit the combinations available, but the limits are not always intuitive to the bridge officer.

VDR time-stamping accuracy. The telegraph logger writes records with a UTC timestamp, but the accuracy of that timestamp depends on the GPS clock disciplining the ship’s master clock. If the GPS antenna has been blocked or the clock disciplining has failed, the telegraph log may carry an offset timestamp that complicates post-event reconstruction. This was a documented problem in the investigation of a collision in the Singapore Strait in 2018, where the VDR clock had drifted by 4 minutes and 12 seconds from UTC, requiring cross-reference with AIS records to establish the true timeline.

UMS period limitations. During unattended machinery space operation, the bridge officer is the sole watchkeeper for the engine room, but cannot carry out any hands-on intervention. A slowly developing fault (for example, a cylinder lube oil quill that is partially blocked, reducing cylinder oil delivery below optimal) may not trigger an alarm but can accumulate thermal damage. The bridge telegraph system gives the officer excellent speed-and-direction control but essentially no diagnostic capability for the engine’s internal condition beyond the alarms defined in IACS UR M47.

See also

• Engine Governor Systems on Marine Diesel Engines
• Engine Emergency Stop Circuits on Marine Engines
• Marine Engine Room Automation and Monitoring
• Marine Bridge Equipment and Integrated Bridge Systems
• Voyage Data Recorder (VDR + S-VDR)
• Engine Reversing System on Two-Stroke Marine Diesel Engines
• Engine Starting Air System on Marine Diesel Engines