PLC Genset Engine Control I/O Design, Networking, Field

James Nishida24 min read
Best PracticesMotor ControlOmron
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

PLC Genset Engine Control: I/O Design, Networking, and Field Reliability

Backup generator control has shifted decisively from electromechanical relay panels, cranking timers, and discrete voltage relays to networked PLC-based systems with dedicated engine controllers, digital power monitoring, and SCADA. The transition is not driven by novelty but by lifecycle cost, observability, and the practical limits of hard-wired relay logic when a facility grows to 50+ switchboards, multiple prime movers, synchronised load sharing, and soft transfer. This reference consolidates field-proven practices for engineers designing, commissioning, or troubleshooting PLC-based genset engine control, with particular emphasis on output topology, Modbus RTU and DeviceNet integration, manual bypass architecture, battery maintenance, and component selection.

1. Architecture of a PLC-Based Genset Control System

A modern genset control system is rarely a single PLC loop. It is layered:

  1. Engine Controller – A dedicated unit (Woodward EGCP-2, Si-TEC, ComAp, DEIF) that handles the time-critical tasks of cranking, governing, synchronisation, and load sharing. These are designed for sub-cycle engine protection and are not replaced by a general-purpose PLC.
  2. Supervisory PLC – A standard industrial PLC (Omron CP1, CJ, or CS series; Allen-Bradley CompactLogix or ControlLogix; Siemens S7-1500) that runs the application logic: AMF (auto mains failure) sequencing, load shedding, capacity control, auto-load-bank control, base-load dispatch, co-generation, soft transfer, and SCADA comms.
  3. Distributed I/O – DeviceNet (legacy), EtherNet/IP, or PROFIBUS remote I/O blocks at the switchboards, eliminating thousands of home-run control cables in a high-rise or campus installation.
  4. SCADA / HMI – AVEVA Plant SCADA (formerly Citect), FactoryTalk View, WinCC, or iFIX providing the operator interface, trending, and alarm management.
  5. Manual Backup – Hard-wired auto-return and emergency-start hardware that allows the building to return to normal operation when the SCADA PC fails. This is non-negotiable for any safety-critical or hospital-grade system.
Field rule: The PLC is the brain. The engine controller is the reflex arc. The SCADA is the dashboard. Never collapse all three into one PC-based platform, because the failure mode of a Windows OS is not the same as the failure mode of an engine needing to start in a blackout.

2. Output Design: Transistor Outputs Driving External Relays

One of the most consistent and well-documented field practices in genset control is to never switch DC inductive loads directly with PLC relay outputs. The reasons are specific:

  • DC has no zero-crossing, so contact wear on a relay switching 24 VDC inductive is dramatically worse than on 230 VAC.
  • Internal PLC relay sockets are small, with minimal contact gap, and they fail open or fail welded. Replacing a relay output card in a live panel at 03:00 during a mains outage is not a pleasant exercise.
  • External relays have larger physical contacts, larger contact gap, and standard socket-mount form factors that any technician can replace in under a minute with a screwdriver.

Standard implementation:

  1. PLC transistor output (sink or source, typically 0.5 A per point, 24 VDC) drives an external relay coil.
  2. A flyback diode (1N4007 or similar) is wired across every relay coil, cathode to +24 V.
  3. The relay contact then switches the actual load: starter solenoid, fuel solenoid, preheat, ACB close coil, ACB trip coil, alarm horn, or indicator lamp.
  4. Status LED indicators on the panel are also driven from the same transistor output, either in parallel with the relay coil or via a separate output – both are bi-directionally diode-protected to prevent sneak paths through the LED.

2.1 Recommended Relay: Omron G2R Series

The Omron G2R general-purpose relay has become a de-facto standard in industrial genset panels because of its availability, contact rating, and the existence of a near-identical Allen-Bradley re-badge. Key specifications:

Parameter Value
Coil voltage 24 VDC (also 12, 110, 230 VAC variants)
Contact form SPDT (G2R-1) or DPDT (G2R-2)
Contact rating (resistive) 10 A at 250 VAC; 10 A at 30 VDC
Contact rating (inductive) 7.5 A at 250 VAC; 5 A at 30 VDC
Mechanical life 10 million operations
Electrical life (rated load) 100,000 operations
Socket P2RF-08 (DIN-rail / panel mount, finger-safe)
Operating temperature -40 °C to +70 °C

Use a finger-safe socket (P2RF-08-E) with retention springs. Document the relay type on the schematic and silkscreen next to the socket. A well-labelled panel turns a 4-hour fault-find into a 15-minute relay swap.

Warning: Avoid PCB-mount relay output cards as the only path for starter or fuel solenoids. The relay is the cheapest component in the panel; do not let a relay failure take down a generator start sequence. Always provide diode suppression and a field-replaceable external relay.

3. Input Design and Signal Conditioning

All discrete I/O in a genset panel is 24 VDC. This is non-negotiable in modern designs because 24 VDC is also the engine controller I/O level, the DeviceNet bus power level, and the standard for instrumentation. Mixing 110 VAC and 24 VDC in the same panel is asking for field failures.

3.1 Standard Inputs by Function

Signal Source Type Notes
Mains healthy Mains contactor or ATS logic DI 24 VDC Use a dedicated mains monitoring relay (e.g., ABB CM-ENS or Siemens 3UG) feeding back a single health contact. Do not infer from individual phase voltages.
Mains breaker status (MCB) Aux contacts on ACB/MCCB DI 24 VDC, 2 points (open + closed) Both states required; never rely on a single contact.
Generator breaker status (GCB) Aux contacts on ACB/MCCB DI 24 VDC, 2 points Same as above. For ACBs, the spring-charge and ready-to-close are additional mandatory signals.
Engine running (oil pressure) Engine low oil pressure switch (NO) DI 24 VDC Used as the engine-running flag for the start sequence. Must be debounced 1-2 s.
Engine running (magnetic pickup) MPU on engine High-speed pulse to engine controller Routes to the engine controller, not the PLC. The PLC reads RPM via Modbus.
Emergency stop Mushroom button, hard-wired DI 24 VDC, NC with safety relay Must latch and require manual reset. Hard-wired to engine controller shutdown input AND the ACB trip. Do not depend on the PLC to action an E-stop.
Auto-return / SCADA bypass Keyswitch or pushbutton on cubicle door DI 24 VDC Hard-wired; see Section 11.
Coolant temperature, oil pressure, fuel level 4-20 mA transmitters or Pt100 AI 4-20 mA or RTD module Use the PLC AI module rather than engine controller analog inputs if SCADA must display engineering values.

3.2 First Three Things to Check

When called to a genset fault, the diagnostic order is not the laptop. It is:

  1. Get up-to-date drawings. A panel without drawings is a stranger's house without a map.
  2. Ask the operator: "What is happening? What did you see before it tripped?"
  3. Multimeter – confirm all three phases are present on the mains and generator sides. A single blown control fuse will look like a PLC fault if you do not start at the supply.

Only after those three, plug in the laptop. The fastest way to waste four hours is to load the program first and try to debug a problem that is actually a missing phase or a tripped control MCB.

4. Engine Controllers: EGCP, Si-TEC, and Modern Equivalents

The PLC does not govern the engine. A dedicated engine controller does. This is not a PLC bashing; it is a separation-of-concerns decision. Governing, synchronisation, and VAR sharing require sub-cycle update rates and have safety implications (anti-motoring, dead-bus permission, sync-check) that should not ride on a general-purpose processor.

4.1 Woodward EGCP-2

The Woodward EGCP-2 (Engine Generator Control Panel) is a legacy workhorse for multi-engine paralleling. It provides synchronisation, kW load sharing, kVAR/VAR sharing, and Modbus communication. The successor EGCP-3 has been on the market for some time but has a reputation in the field for being less well-debugged in the first production runs; the EGCP-2 remains the conservative choice for retrofits and critical sites.

Field incident: On a multi-engine installation, two EGCP-2 units were set up by a commissioning engineer, and immediately after closing the generator ACB the system reported 100 A per phase with no connected load. Root cause: the analog inputs (current transformers) had not been calibrated in the controller. The PLC read the data as true and the SCADA confirmed it. Calibrate every analog input on every controller during commissioning. Document the calibration in the O&M manual.

4.2 Si-TEC (Dawson Technologies)

Australian-designed digital generator controllers (Si-TEC) cover diesel, gas, and turbine prime movers with built-in synchroniser, load share, and AMF logic. They expose Modbus RTU, three analog outputs (commonly used for kW, kVA, true-RMS power factor) for re-transmission to panel meters, and configurable PID for idle / run-no-load / synchronised / on-line-with-mains operating modes. They are roughly 3-4× the price of an equivalent Woodward unit but offer a higher level of onboard diagnostics.

4.3 The Bypass Imperative

Even with the most reliable engine controller, the genset must be startable in manual if both the PLC and the controller fail. The minimum manual path is:

  • A key-switch position "Manual" that energises the fuel solenoid, crank solenoid, and preheat directly, with a stop button to drop them out.
  • Mechanical or electrical interlock to the ACB close coil so the operator can close the breaker onto the bus when the synchroniser is offline.
  • Local ammeter and voltmeter fed from instrument CTs / PTs – independent of the engine controller's analog outputs.

5. Modbus RTU Integration with the Engine Controller

Every modern engine controller exposes a Modbus RTU (RS-485) interface that carries status, alarms, measured values, and configuration. The Modbus Organization specification defines the protocol; the Omron CP1L and CJ-series PLCs ship with built-in Modbus RTU master function blocks, eliminating the need for a third-party gateway.

5.1 Typical Modbus Map Excerpt

Register (4x) Description Units / Scale FC
40001 Generator voltage L-L avg V, integer 03
40002 Generator frequency 0.01 Hz 03
40003 Engine RPM RPM 03
40004 Generator current (avg) A 03
40005 Active power total kW, signed 03
40006 Reactive power total kVAR, signed 03
40007 Power factor 0.001, signed 03
40010 Engine state code 0=stopped, 1=starting, 2=running, 3=cooling, 4=stopping, 5=fault 03
40011 Active alarm word 1 Bitmask 03
40012 Active alarm word 2 Bitmask 03
00020 Remote start/stop command 0=stop, 1=start 06
00021 Active power setpoint 0.1 % of rated 06
00022 Power factor setpoint 0.001, signed 06
Note on register maps: The register layout above is generic; always obtain the engine controller's official Modbus map from the manufacturer (Woodward, ComAp, DEIF, Siemens, or Si-TEC) and enter it in the PLC's data block. Never assume cross-vendor compatibility.

5.2 Modbus Wiring and Termination

  • RS-485 2-wire multidrop, daisy-chain topology. Maximum 32 unit loads on a single segment without repeater.
  • Baud 19200, 8N1, slave ID 1, 100 ms inter-frame delay is a robust default for engine controllers.
  • 120 Ω termination resistors at each end of the bus. Do not place in the middle.
  • Shield grounded at one end only (controller end is conventional).
  • Use twisted-pair shielded cable, e.g., Belden 3106A or equivalent.

6. DeviceNet for Distributed I/O at Scale

For multi-switchboard installations (a 50-floor building, a hospital, a campus), running home-run control cables from a central PLC to every switchboard is no longer viable. DeviceNet (CIP on CAN, defined by ODVA) was the de-facto industrial fieldbus for this application through the 2000s and into the 2010s; many existing installations still use it. EtherNet/IP is the modern equivalent.

6.1 Reference Architecture for a High-Rise Installation

A representative installation of 11 networked PLCs, 92 DeviceNet I/O blocks, and 23 Allen-Bradley PowerMonitor 3000 devices on a single supervisory PLC has been operated continuously for over a decade with no PLC-related downtime. The architecture is:

  • One supervisory PLC per building or per fire cell, in a star topology over Ethernet.
  • Each supervisory PLC owns multiple DeviceNet scanners on its backplane (the reference design used 9 scanners to fan out 92 I/O blocks and 23 PowerMonitor 3000 units).
  • Each PowerMonitor 3000 is addressed by explicit messaging (CIP connection) rather than polled I/O, to keep the implicit-connection bandwidth for I/O.
  • SCADA (Citect) reads the data from each supervisory PLC over an Omron / Modbus TCP / EtherNet/IP gateway as required; updates from each device to the SCADA are better than 2 per second.

6.2 DeviceNet Cabling Rules

Parameter Value
Baud rate options 125 kbps, 250 kbps, 500 kbps
Trunk length (max, 125 kbps) 500 m
Trunk length (max, 500 kbps) 100 m
Drop length (max) 6 m (any baud)
Number of nodes (max) 64
Bus power 24 VDC, 8 A max from a single supply
Cable types Thick (round, 11.8 mm), Mid (flat or round, 7.9 mm), Thin (flat, 6.1 mm)

7. PowerMonitor 3000 on DeviceNet

The Allen-Bradley PowerMonitor 3000 (1408 series) measures voltage, current, active/reactive/apparent power, power factor, frequency, and energy on the mains and generator sides of every switchboard. Mounted in the switchboard compartment, it eliminates the long transducer runs back to the control panel and provides 0.5 % accuracy metering on the same wire that carries DeviceNet comms.

7.1 Key Specifications

Parameter Value
Voltage input 0-600 VAC, three-phase or single-phase
Current input 0-5 A (from external CTs, e.g., 800/5, 1500/5)
Active / reactive / apparent power True RMS, signed
Frequency 45-65 Hz
Accuracy 0.5 % of reading (energy: 1 % per ANSI C12.20 class 1)
Comms options DeviceNet, EtherNet/IP, ControlNet, Modbus TCP
Update rate 100 ms typical for measured values; 1 s for energy

7.2 Sizing Example (Unambiguous Phase Topology)

Three-phase apparent power on a 415 V switchboard at 360 A line current:

kVA = sqrt(3) × V_LL × I_line / 1000 = 1.732 × 415 × 360 / 1000 = 258.7 kVA

Three-phase apparent power on a 415 V switchboard at 360 A per phase (same as line current in a balanced three-phase system):

kVA = sqrt(3) × 415 × 360 / 1000 = 258.7 kVA

Calculation discipline: In a three-phase system, line current equals per-phase current only for a delta or balanced wye load. If a single-phase 360 A load is on a three-phase bus, it should be carried by one phase and the apparent power is kVA = V_phase × I / 1000 = 240 × 360 / 1000 = 86.4 kVA. Always confirm whether the stated current is per-phase or line, RMS or peak, before sizing transformers and busbars.

8. Synchronisation, Soft Transfer, and Load Sharing

Soft transfer (sometimes called SCTT – Static-Continuity-Transfer or Closed-Transition Transfer) briefly parallels the generator with the mains to avoid a break in supply to the load. This is mandatory for sites where the UPS battery has only seconds of autonomy (e.g., 15 s at full load, 2 s loss of mains before generator start) and is standard in European installations.

8.1 Implementation Outline

  1. Mains failure detected; generator is started and brought to rated voltage and frequency by the engine controller.
  2. Generator controller synchronises the GCB to the live mains bus: voltage match (<5 %), frequency match (<0.1 Hz), phase angle match (<10°).
  3. Sync-check relay permits closure of the mains-parallel contactor for a preset dwell (typically 100-500 ms).
  4. Load is transferred to the generator; mains breaker is then opened, breaking the parallel connection.
  5. Reverse sequence is used for re-transfer to mains, again with a brief parallel to avoid an interruption.

8.2 Why a Dedicated Sync Module

Synchronisation, kW load sharing, and kVAR sharing should not be done in the supervisory PLC. The PLC bypass approach is well documented: the synchroniser / load-share module is a separate unit (Woodward SPM-D, ComAp InteliMains, or integrated into the EGCP-2). The supervisory PLC only enables the sync module and reads the result. If the supervisory PLC or the SCADA PC fail, the engine controller and sync module keep operating.

9. SCADA Integration: AVEVA Plant SCADA (formerly Citect)

AVEVA Plant SCADA (formerly Citect SCADA, before that Citect for Windows) is widely used in Australian and European high-rise, hospital, and base-load power-station installations. It runs on Windows and is therefore a known-failure target; the engineering discipline is to make every critical control function operable without it.

9.1 Functions in the SCADA

  • Mimic diagrams of every switchboard with live breaker status, bus voltage, and load.
  • Engine mimic for every generator with start, stop, fault reset, duty order selection, and load setpoint.
  • Trending of kW, kVAR, voltage, current, frequency, coolant temperature, oil pressure, battery voltage.
  • Alarm summary with filter, acknowledgement, and audit trail.
  • Historical data export to CSV for monthly reports and battery discharge-test trending.

9.2 PLC-to-SCADA Tag Mapping

PLC Tag (e.g., CP1L D1000) Description SCADA Tag Update
D0100 MCB1 closed MCB1_CLOSED On change
D0101 GCB1 closed GCB1_CLOSED On change
D0200 Engine 1 state code ENG1_STATE 500 ms
D0201 Engine 1 alarm word ENG1_ALARM 500 ms
D0300 Mains kW MAINS_KW 1 s
D0301 Gen 1 kW GEN1_KW 1 s
D0302 Gen 1 kVAR GEN1_KVAR 1 s
D0303 Gen 1 PF GEN1_PF 1 s
D0304 Gen 1 Hz GEN1_HZ 1 s

10. Battery Systems and Quarterly Discharge Testing

Every genset control panel, every DC-driven ACB, every engine controller, and every PLC is powered from a stationary lead-acid battery, typically 24 V nominal (12 × 2 V cells) for a 24 VDC system, or 110 V / 240 V for a higher-voltage DC system. Battery failure is the most common root cause of a genset failing to start, and it is almost always preventable.

10.1 Recommended Maintenance Procedure

  1. Every 3 months, perform a discharge test on every battery bank.
  2. Discharge to 80 % of rated capacity or to a termination voltage of 1.85 V per cell (22.2 V for a 24 V bank).
  3. Record: start voltage, end voltage, discharge current, duration, ambient temperature.
  4. Enter the data into an Excel spreadsheet, one sheet per battery bank.
  5. Chart the discharge curve over time. A battery that previously delivered 60 minutes to the cutoff but now delivers 45 minutes is degraded; replace it before it fails.
Field data point: A 24 V cranking battery can have a fully-charged open-circuit voltage of 25.6 V and a low-voltage setpoint of around 22 VDC. A standing voltage below 24 V on a fully rested battery indicates a sulphated or failed cell. A common genset controller alarm threshold is < 23 VDC for the DC supply. Calibrate this threshold to match the battery manufacturer's recommended end-of-discharge voltage.

10.2 Battery Charger Sizing

Float voltage for a VRLA lead-acid cell is 2.27 V/cell at 25 °C (27.2 V for a 24 V bank). Boost voltage is 2.40 V/cell (28.8 V). Charger current capacity should be at least 0.1 C10 of the battery capacity, plus the standing load of the panel (typically 2-5 A for a control panel with PLC, HMI, and engine controller).

11. Auto-Return Button and Manual Bypass

This is the single most important design decision in a PLC-based genset control system that the SCADA team can ruin. The "auto-return" input is a hard-wired pushbutton or keyswitch on the control cubicle door that, when pressed, allows the PLC to revert the building to its normal operating state (e.g., return to mains) without any input from the SCADA.

11.1 Why It Exists

SCADA PCs fail. Operating systems crash. Hard drives die. Networks drop out. If the operator is standing in front of the panel at 02:00 with the building on generator and the mains restored, they must be able to command the PLC to transfer the load back to mains, reclose the MCB, and shut down the set, with a single button press. Asking them to log into a Windows VM and click a button on a Citect screen is unrealistic.

11.2 Implementation Rules

  • Wired to a dedicated DI on the PLC, not multiplexed through the SCADA.
  • Labelled clearly on the cubicle door: AUTO RETURN – PRESS TO REVERT TO NORMAL OPERATION.
  • Logged in the PLC event log with timestamp for audit.
  • Does not bypass the engine controller, the ACB protection, or the sync-check relay. It only commands the PLC to execute the normal return sequence; the engine controller and protection relays still have full authority.

11.3 Related Manual Controls

Control Hardware Function
Auto-return PB on cubicle door Force PLC to revert to normal state
Manual start Keyswitch to "Manual" Crank and run engine, bypass PLC start logic
Manual close (ACB) Mechanical close lever or pushbutton Close ACB with sync-check bypassed (operator responsibility)
Manual trip (ACB) Mechanical trip lever or shunt trip pushbutton Open ACB from panel, independent of PLC
Emergency stop Mushroom button, hard-wired to engine controller and ACB shunt trip Stop engine, trip ACB, require manual reset

12. Field Commissioning and Troubleshooting

12.1 Commissioning Procedure

  1. Pre-energisation check: confirm 24 VDC supply, 415 V mains, generator voltage, all ground connections.
  2. I/O checkout before program load. For every DI, force the field device and verify the PLC input LED. For every DO, force the PLC output and verify the external relay picks up. For every AI, inject 4-20 mA and verify the PLC value. Document every point.
  3. Load the program, go to Stop, verify all interlocks and permissives.
  4. Simulate mains failure by opening the MCB. Verify engine start, run-up, breaker closure, load pickup within the design time (typically < 30 s).
  5. Simulate mains return. Verify soft transfer (if applicable) and engine cool-down / stop sequence.
  6. Force each engine alarm and verify the SCADA display, the panel annunciator, and the shutdown action (where applicable).
  7. Trip each ACB locally and remotely; verify the engine continues to run and reclose on demand.
  8. Battery test: perform a full discharge test before handover.

12.2 Common Field Faults and Diagnostic Steps

Symptom Likely Root Cause First Check
Engine does not crank on mains failure 24 VDC supply missing; emergency stop latched; E-stop circuit open; relay socket failed; PLC output dead 24 VDC at the PLC output; fuse; E-stop; relay socket retention
Engine cranks but does not start Fuel solenoid not energised; air in fuel line; pre-heat not active; run coil of the key switch off Fuel solenoid voltage; preheat lamp; fuel pressure
Generator starts, ACB does not close Voltage or frequency out of band; sync-check disabled; GCB close coil not energised; interlocking Generator voltage and frequency on the panel meter; sync-check LED; GCB close coil voltage
Generator runs but takes no load GCB closed feedback missing; load shed not released; capacity control in shed GCB aux contact wiring; SCADA load-shed tag; capacity control setpoint
SCADA shows wrong power CT polarity reversed; CT ratio wrong in PowerMonitor; calibration missing; scaling in PLC wrong PowerMonitor calibration log; CT orientation; PLC scaling constants
Modbus comms intermittently failing Termination resistor missing; shield grounded both ends; baud rate mismatch; duplicate slave ID Termination at both ends; oscilloscope on the bus; scan slave IDs 1-247
Engine trips on over/under-speed on first run MPU gap too large or too small; MPU wiring routed with power cables; MPU not configured in engine controller MPU gap 0.5-1.0 mm; reroute cable; check MPU input config in controller

12.3 Software Update Discipline

Password-protect the engine controller configuration. The most common cause of a misbehaving generator is an unauthorised technician who has gone into the password-protected area of the engine controller and changed a parameter that they did not understand. The PLC should be locked; the engine controller should be locked. The SCADA should be operator-level only. The commissioning engineer should be the only one with the password, and the password should be in a sealed envelope in the O&M manual.

13. Component Selection Reference

13.1 PLC Selection

Platform Typical Use I/O Count Network
Omron CP1L / CP1E Single-genset, single-switchboard 14-60 Modbus RTU, Modbus TCP, serial
Omron CJ2M Multi-genset, mid-size building 160-2,560 EtherNet/IP, Modbus TCP, DeviceNet, PROFIBUS
Allen-Bradley CompactLogix 5380 Multi-genset with EtherNet/IP Up to 250 nodes EtherNet/IP, DeviceNet, ControlNet, Modbus TCP
Siemens S7-1500 European high-rise, co-generation Up to 32 modules PROFINET, PROFIBUS, Modbus TCP

13.2 Relay Selection

Load Recommended Relay Diode
Starter solenoid (24 VDC, 30-50 A inrush) G2R-1-S 24 VDC + slave contactor (e.g., S-P11 24 VDC coil) 1N4007 across coil
Fuel solenoid (24 VDC, 5-10 A) G2R-1-S 24 VDC 1N4007 across coil
Pre-heat (24 VDC, 10-20 A) G2R-1-S 24 VDC + thermal fuse 1N4007 across coil
ACB close coil (24/110/220 VDC, 5-15 A inrush) G2R-2-S 24 VDC + slave contactor 1N4007 across coil
Alarm horn (24 VDC, 1-2 A) G2R-1-S 24 VDC 1N4007 across coil

14. Heat Recovery, Co-Generation, and Base-Load Operation

For a base-load power station or a hospital with a heat-recovery system, the generator is not a standby asset; it is a primary mover, and the control system must reflect that. Three operating modes to design for:

  1. Standby / AMF – Mains healthy; generator stopped; automatic start on mains failure.
  2. Peak-Shaving / Co-Generation – Mains healthy; generator running in parallel with the utility, exporting excess kW to the grid or capturing exhaust heat for a hospital hot-water system or a swimming pool. Maintain generator at > 50 % load to avoid wet-stacking; target 80-90 % load for best thermal efficiency of the heat-recovery boiler.
  3. Base-Load – Generator(s) supply the entire site, utility disconnected. Multiple units share load via kW load sharing on the engine controllers; PLC coordinates start / stop / duty order.

For co-generation in a hospital, the standard design runs the generator at > 90 % load to maximise the heat-recovery return, with the engine jacket water and exhaust gas feeding plate heat exchangers. The PLC must include a permissive that allows the engine to run only when the heat-recovery circuit is in demand or when the generator is in the standby role. Running the engine at < 30 % for extended periods causes incomplete combustion, carbon build-up in the exhaust, oil contamination, and eventual engine damage.

15. Standards and Verification

The following standards and manufacturer documents should be on the engineer's desk for any genset control design or audit:

  • IEEE 141 (Red Book) – Electric Power Distribution for Industrial Plants
  • IEEE 446 (Orange Book) – Emergency and Standby Power Systems for Industrial and Commercial Applications
  • NFPA 110 – Standard for Emergency and Standby Power Systems
  • AS 3000 (Australia) / BS 7671 (UK) / NEC (USA) – Wiring rules, applicable per jurisdiction
  • Manufacturer engine manuals – Cummins, Caterpillar, MTU, MAN, Perkins, Wärtsilä

Always confirm that the chosen standard permits the specific overload or fault-clearance time claimed in the design. Standards documents are the legal source; manufacturer brochures are not.

Frequently Asked Questions

Why do PLC-controlled gensets use transistor outputs with external relays instead of PLC relay outputs?

DC switching arcs longer than AC at the same voltage and current. Internal PLC relay sockets have small contacts and minimal contact gap, so they fail open or welded when switching 24 VDC inductive loads such as starter or fuel solenoids. Transistor outputs switching the relay coil (with a 1N4007 flyback diode) keep the DC arc out of the PLC, and the external G2R-type relay can be replaced in under a minute without touching the PLC output card.

What is the auto-return button, and why is it hard-wired instead of a SCADA button?

The auto-return button is a physical pushbutton or keyswitch on the control cubicle that commands the PLC to revert the building to its normal operating state (typically return-to-mains and shut down the set) without any input from the SCADA. It is hard-wired to a dedicated PLC digital input because the SCADA PC is the most likely component to fail (OS crash, network drop, power supply); the operator must always be able to command the building back to normal from the panel door.

How should the engine controller and the supervisory PLC be connected?

Use Modbus RTU (RS-485, 19200 8N1) between the engine controller (Woodward EGCP-2, Si-TEC, ComAp, DEIF) and the supervisory PLC as the primary data path. Poll the engine state, measured values, and alarm words every 100-500 ms; write setpoints and start / stop commands on change. Keep the synchroniser, kW load-share, and kVAR share on the engine controller or a dedicated module; the supervisory PLC only enables and reads them.

How often should the starting battery be tested, and to what voltage?

Discharge-test every 3 months. For a 24 V VRLA battery (12 cells), terminate the test at 1.85 V per cell (22.2 V) or at 80 % of rated capacity, whichever comes first. Log the start voltage, end voltage, discharge current, duration, and ambient temperature in a spreadsheet, and chart the duration over time. A battery whose runtime to the cutoff has dropped 20 % from the previous test is a candidate for replacement, not for a waiting period.

What is the difference between a sync-check relay and a synchroniser module?

A sync-check relay is a permissive: it closes a contact only when voltage, frequency, and phase angle across an open breaker are within limits, allowing the breaker to close. A synchroniser module actively adjusts the engine governor and AVR to bring the generator into match with the running bus, then issues a close command. The PLC does neither. The engine controller or a dedicated SPM-D-class module is the synchroniser; the sync-check relay is a backstop in case the synchroniser module fails.

Why is the engine controller password-protected, and who should know it?

Engine controller configuration changes (governor gain, sync window, kW share slope, alarm thresholds) by an untrained operator are the most common cause of unexplained generator behaviour in the field. The commissioning engineer should be the only one with the password, and the password should be recorded in a sealed envelope inside the O&M manual. Any change must be logged with the parameter name, old value, new value, and reason.

Back to blog