B37574 - TM - Easygen 3100 3200 XT P1 - J PDF

easYgen-3000XT Series
Manual Genset Control
easYgen-3100XT-P1 / 3200XT-P1 / 3200XT-P1-LT
Software Version 2.10
Document ID: B37574, Revision: J - Build 47407

This is no translation but the original Technical Manual in English.
Designed in Germany and Poland.
Woodward GmbH
Handwerkstr. 29
70565 Stuttgart
Germany
Telephone: +49 (0) 711 789 54‑510
Fax: +49 (0) 711 789 54‑101
Email: stgt-info@woodward.com
Internet: http://www.woodward.com
© 2020 Woodward GmbH
2 easYgen-3000XT Series B37574

Brief Overview
Brief Overview
The easYgen-3000XT series are control units for engine-generator system management
applications.
The control units can be used in applications such as: co-generation, stand-by, AMF, peak
shaving, import/export or distributed generation.
The easYgen-3000XT series is also applicable for islanded, island parallel, mains parallel
and multiple unit mains parallel operations.
Scope of delivery
The following parts are included in the scope of delivery. Please check prior to the
installation that all parts are present.
Fig. 1: Scope of delivery
A Device easYgen-3200XT-P1 (sheet metal housing) or easYgen-3200XT-P1(-LT) genset

control (plastic housing). All screwable terminal connectors are delivered with plug and
jack.
B IPS (Installation Procedure Supplement) and printed QR Code sticker - 2 x
C Clamp fastener installation material - 4 x (only plastic housing)
D Screw kit installation material - 12 x (only plastic housing)
Configuration files and Technical Manual are available on device internal memory.
Opening USB connection to the easYgen-XT offers read access to the files listed below
but with status "delivery" -- please be aware that this files are not updated. The latest
versions are available at the Woodward web site.
Files stored at easYgen-XT device:
• Configuration
◦ msi-file (installing application files and ToolKit)
◦ eds-file (zipped)
• Technical Manual (PDF)
B37574 easYgen-3000XT Series 3

Brief Overview
QR Code
To get access to the complete product documentation, scan this QR code or use the
following link: ══▷ http://wwdmanuals.com/easygen-3200xt.
Sample application setup
Fig. 2: Sample application setup
A typical application mode for the control unit is the use for mains parallel operation in a
multi genset application.
• In this case, the easYgens-XT will function as an engine control with generator,
mains and engine protection.
• The control unit can open and close the generator circuit breaker (GCB) and the
mains circuit breaker (MCB).

Brief Overview
• The easYgens-XT are well prepared for system control and management, "talking"
with other easYgens-3100XT/3200XT and easYgens-3400XT/3500XT.
For a listing of all available application modes please refer to ╚═▷ “6 Application Field”.

Table of Contents
Table of Contents
1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25█

........
1.1 About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25█

.........
1.1.1 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25█

.........
1.1.2 Depiction Of Notes And Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35█

........
1.2 Copyright And Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36█

........
1.3 Service And Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37█

........
1.4 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37█

........
1.4.1 Intended Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37█

.........
1.4.2 Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38█

.........
1.4.3 General Safety Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39█

.........
1.4.4 Protective Equipment And Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42█

.........
2 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44█

.........
2.1 Display And Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44█

........
2.2 Application Modes Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44█

........
2.3 Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45█

.........
3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46█
........
3.1 Mount Unit (Sheet Metal Housing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46█

.........
3.2 Mount Unit (Plastic Housing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48█

........
3.2.1 Clamp Fastener Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49█

.........
3.2.2 Screw Kit Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51█

.........
3.3 Setup Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53█

.........
3.3.1 Terminal Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53█

.........
3.3.2 Wiring Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55█

........
3.3.3 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59█

.........
3.3.4 Charging Alternator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61█

.........
3.3.5 Voltage Measuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61█

.........
3.3.5.1 Generator Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61█

.........
3.3.5.1.1 Parameter Setting '3Ph 4W OD' (3-phase, 4-wire, Open delta) . . . . . . . . . . . . . . . . . . . . .62█
........
3.3.5.1.2 Parameter Setting '3Ph 4W' (3-phase, 4-wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63█

.........

.........

Table of Contents

.........

.........
3.3.5.2 Mains Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69█

........

.........

.........

.........

.........
3.3.5.3 Busbar Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76█

.........

.........
3.3.6 Current Measuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79█

.........
3.3.6.1 Generator Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79█

.........
3.3.6.1.1 Parameter Setting 'L1 L2 L3' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80█

........
3.3.6.1.2 Parameter Setting 'Phase L1' 'Phase L2' 'Phase L3' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81█
.........
3.3.6.2 Mains Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82█

........
3.3.6.2.1 Parameter Setting 'Phase L1' 'Phase L2' 'Phase L3' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83█
.........
3.3.6.3 Ground Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83█

........
3.3.7 Power Measuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85█

.........
3.3.8 Power Factor Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86█

........
3.3.9 Magnetic Pickup Unit (MPU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87█

.........
3.3.10 Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89█

.........
3.3.11 Relay Outputs (LogicsManager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91█

.........
3.3.11.1 Connecting 24 V Relays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92█

.........
3.3.12 Analog Inputs (0 to 2000 Ohm | 0/4 to 20 mA | 0 to 1 V) . . . . . . . . . . . . . . . . . . . . . . . . .94█

.........
3.3.13 Analog Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96█

........
3.3.13.1 Analog Outputs (±20 mA, ± 10 V, PWM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96█

.........
3.4 Setup Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97█

........
3.4.1 Interfaces overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97█

.........
3.4.2 RS-485 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97█

........
3.4.3 USB (2.0 slave) interface - Service Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99█

.........
3.4.4 CAN Bus Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100█

.........
3.4.5 Ethernet Interface (incl. Remote Panel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102█

..........
4 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107█
..........

Table of Contents
4.1 Front Panel Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110█

..........
4.1.1 Basic Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110█

.........
4.1.2 The HOME Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114█

.........
4.1.3 Customer Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117█

..........
4.1.4 Standard Menu Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119█

..........
4.1.4.1 Navigation Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119█

.........
4.1.4.2 Value Setting Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120█

.........
4.1.4.3 Status/Monitoring Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121█

..........
4.1.5 Specialized Menu Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122█

..........
4.1.5.1 HOME Screen Voltage Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122█

..........
4.1.5.2 Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123█

..........
4.1.5.3 Event History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124█

..........
4.1.5.4 Sequencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125█

.........
4.1.5.5 States easYgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126█

.........
4.1.5.6 Genset Parameter Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127█

..........
4.1.5.7 Diagnostic devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127█

..........
4.1.5.8 Setpoints generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128█

..........
4.1.5.9 Setpoints PID1 - PID3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129█

.........
4.1.5.10 Synchroscope (Generator/Busbar And Busbar/Mains) . . . . . . . . . . . . . . . . . . . . . . . . . . 131█

..........
4.1.5.11 LogicsManager Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132█

..........
4.1.5.12 LogicsManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133█

..........
4.1.5.13 Mains Decoupling Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134█

.........
4.1.5.14 Test Mains Decoupling (VDE AR-N 4105) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135█

..........
4.1.5.15 CAN Interface 1 State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136█

.........
4.1.5.16 CAN Interface 2 State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138█

.........
4.1.5.17 Ethernet Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140█

..........
4.1.5.18 USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142█

.........
4.1.5.19 RS-485 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143█

..........
4.1.5.20 J1939 Special . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143█

..........
4.1.5.21 J1939 Status miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144█

..........
4.1.5.22 Time Indication According To Operating Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146█

..........
4.2 Access Via PC (ToolKit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147█

..........

Table of Contents
4.3 Basic Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147█

.........
4.3.1 Configure Language/Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148█

..........
4.3.2 Configure HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154█

.........
4.3.2.1 Configure Customer Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154█

..........
4.3.2.2 Configure Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156█

.........
4.3.2.3 Screen configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157█

.........
4.3.3 Lamp Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160█

.........
4.3.4 Enter Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160█

.........
4.3.4.1 Password System - Parameter Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175█

..........
4.3.4.1.1 Random Number for Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176█

..........
4.3.4.1.2 Change/Reset Alphanumeric Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177█

.........
4.3.5 System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179█

..........
4.3.5.1 Reboot Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181█

..........
4.3.6 Configure Remote Panel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182█

..........
4.3.6.1 Configuration screen Remote Panel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182█

..........
4.3.6.2 General notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182█

.........
4.3.6.3 RP-3000XT in Full Mode with Password suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . .183█

.........
4.3.6.4 RP-3000XT in Full Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184█

..........
4.3.6.5 RP-3000XT in Annunciator Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185█

..........
4.3.6.6 RP-3000XT in Off Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186█

.........
4.3.6.7 Parameters of RP Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187█

.........
4.4 Configure Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188█

.........
4.4.1 Configure Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188█

..........
4.4.1.1 Configure Engine (general) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188█

.........
4.4.1.2 Engine Start/Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195█

..........
4.4.1.3 Magnetic Pickup Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208█

..........
4.4.1.4 Idle Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210█

..........
4.4.2 Inputs And Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212█

.........
4.4.2.1 Function Of Inputs And Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212█

..........
4.4.2.1.1 Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212█

..........
4.4.2.1.2 Discrete Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214█

.........
4.4.2.2 Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217█

..........

Table of Contents
4.4.2.3 Discrete Outputs (LogicsManager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222█

..........
4.4.2.4 Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224█

..........
4.4.2.4.1 Analog Inputs (general) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224█

..........
4.4.2.4.2 Analog Inputs 1 to 3 (0 to 2000 Ω | 0/4 to 20 m A | 0 to 1 V) . . . . . . . . . . . . . . . . . . . . .227█

..........
4.4.2.5 Analog Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234█

.........
4.4.2.5.1 Analog Outputs 1 and 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234█

..........
4.4.2.6 External Analog Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239█

..........
4.4.2.7 External Analog Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242█

.........
4.4.2.8 External Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245█

.........
4.4.2.9 External Discrete Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246█

.........
4.4.3 Configure Breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247█

.........
4.4.3.1 Good to know: Actions with Breakers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248█

..........
4.4.3.1.1 Dead Bus Closing GCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248█

..........
4.4.3.1.2 Synchronization GCB/MCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249█

..........
4.4.3.1.3 Dead Bus Closing MCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251█

..........
4.4.3.1.4 Open GCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252█

.........
4.4.3.1.5 Open MCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252█

.........
4.4.3.1.6 Transition Modes (Breaker Logic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253█

..........
4.4.3.2 General Breaker Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257█

..........
4.4.3.3 Configure Breakers: GCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261█

..........
4.4.3.4 Configure Breakers: MCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268█

..........
4.4.3.5 Configure Breakers: Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273█

..........
4.4.3.5.1 Independent Sync. Check Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275█

.........
4.4.3.6 Configure Breakers: Neutral Interlocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277█

..........
4.4.4 Configure Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277█

..........
4.4.4.1 Voltage Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280█

.........
4.4.4.2 Power Factor Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286█

.........
4.4.4.2.1 Control The Power Factor / Reactive Power At The Mains Interchange Point . . . . . . . . . .287█
.........
4.4.4.2.2 Configure Power Factor / kvar Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288█

..........
4.4.4.2.3 Power Factor Characteristic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294█

..........
4.4.4.2.4 Reactive Power / Power Factor setpoint filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299█

..........
4.4.4.2.5 Reactive Power Characteristic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301█

..........

Table of Contents
4.4.4.3 Load Share Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311█

.........
4.4.4.3.1 Mains Parallel Operation With Mains Interchange Real Power Control (Import/
Export) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312█
..........
4.4.4.3.2 Islanded Operation In Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313█

.........
4.4.4.3.3 Re-synchronization Of The Busbar To The Mains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313█

.........
4.4.4.3.4 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314█

.........
4.4.4.3.5 Load-Share Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314█

..........
4.4.4.3.6 Load Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314█

.........
4.4.4.3.7 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316█

.........
4.4.4.3.8 Load Share Control Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318█

..........
4.4.4.3.9 Droop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321█

..........
4.4.4.4 Frequency Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324█

.........
4.4.4.5 Load Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334█

.........
4.4.4.5.1 Configure: Load Control (general) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334█

.........
4.4.4.5.2 Configure: Load Setpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .340█

.........
4.4.4.5.3 Configure: Warm-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344█

..........
4.4.4.5.4 Derating And Uprating Of Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345█

..........
4.4.4.5.5 Active Power – Frequency Function P(f) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349█

..........
4.4.4.5.6 Photovoltaic (PV) load reduction regulated mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355█

.........
4.4.4.6 PID {x} Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359█

.........
4.4.4.7 Discrete Raise/Low Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362█

.........
4.4.5 Configure Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364█

..........
4.4.5.1 Operation Modes: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364█

..........
4.4.5.2 Operation Mode AUTO - Automatic Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366█

..........
4.4.5.3 Operation Mode TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368█

.........
4.4.5.4 Critical Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .370█

.........
4.4.5.4.1 Critical Operation At Busbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371█

.........
4.4.5.4.2 Critical Operation At The Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374█

..........
4.4.5.4.3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376█

.........
4.4.5.5 Load Dependent Start/Stop (LDSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377█

.........
4.4.5.5.1 Generator Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377█

.........
4.4.5.5.2 System Reserve Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379█

.........
4.4.5.5.3 Generator Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381█

..........

Table of Contents
4.4.5.5.4 Islanded Parallel Operation (IOP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387█

..........
4.4.5.5.5 Mains Parallel Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393█

.........
4.4.5.5.6 LDSS with predicted load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398█

..........
4.4.6 Emergency Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401█

..........
4.5 Configure Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403█

..........
4.5.1 Configure Generator Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .404█

.........
4.5.1.1 Generator Operating Ranges: Voltage / Frequency / Busbar . . . . . . . . . . . . . . . . . . . . . .404█

.........
4.5.1.2 Generator Voltage Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .406█

.........
4.5.1.2.1 Generator Overvoltage (Level 1 & 2) ANSI# 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406█

..........
4.5.1.2.2 Generator Undervoltage (Level 1 & 2) ANSI# 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408█

..........
4.5.1.2.3 Generator Voltage Asymmetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .410█

.........
4.5.1.3 Generator Frequency Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412█

..........
4.5.1.3.1 Plausibility Check of Voltages' AC Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412█

..........
4.5.1.3.2 Generator Overfrequency (Level 1 & 2) ANSI# 81O . . . . . . . . . . . . . . . . . . . . . . . . . . . .413█

.........
4.5.1.3.3 Generator Underfrequency (Level 1 & 2) ANSI# 81O . . . . . . . . . . . . . . . . . . . . . . . . . . .415█

.........
4.5.1.4 Generator Current Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .417█

.........
4.5.1.4.1 Generator Time-Overcurrent (Level 1, 2 & 3) ANSI# 50/51 . . . . . . . . . . . . . . . . . . . . . . 417█

..........
4.5.1.4.2 Generator Inverse Time-Overcurrent ANSI# IEC 255 . . . . . . . . . . . . . . . . . . . . . . . . . . . 419█

..........
4.5.1.4.3 Generator Voltage Restrained Overcurrent Monitoring - ANSI #51V . . . . . . . . . . . . . . . .423█

.........
4.5.1.5 Generator Power Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .425█

.........
4.5.1.5.1 Generator Overload IOP (Level 1 & 2) ANSI# 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425█

..........
4.5.1.5.2 Generator Overload MOP (Level 1 & 2) ANSI# 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427█

.........
4.5.1.5.3 Generator Reverse/Reduced Power (Level 1 & 2) ANSI# 32R/F . . . . . . . . . . . . . . . . . . . 429█

..........
4.5.1.5.4 Generator Unbalanced Load (Level 1 & 2) ANSI# 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . 431█

..........
4.5.1.5.5 Load sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .434█

.........
4.5.1.5.6 Engine/Generator Active Power Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437█

..........
4.5.1.5.7 Engine/Generator Unloading Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438█

..........
4.5.1.6 Other Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439█

..........
4.5.1.6.1 Power Factor - configure generator power factor monitoring . . . . . . . . . . . . . . . . . . . . .439█

..........
4.5.1.6.2 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .444█

.........
4.5.1.6.3 Pole Slip Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450█

..........
4.5.2 Configure Engine Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .452█

.........

Table of Contents
4.5.2.1 Engine Overspeed (Level 1 & 2) ANSI# 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .452█

.........
4.5.2.2 Engine Underspeed (Level 1 & 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .454█

.........
4.5.2.3 Engine/Generator Speed Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456█

..........
4.5.2.4 Engine Start Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458█

..........
4.5.2.5 Engine Shutdown Malfunction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459█

.........
4.5.2.6 Engine Unintended Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460█

..........
4.5.2.7 Engine Charge Alternator (D+) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .461█

.........
4.5.2.8 Cylinder Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .462█

.........
4.5.3 Mains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470█

..........
4.5.3.1 General Mains Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .470█

.........
4.5.3.2 Blocking of Mains Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .471█

.........
4.5.3.3 Mains Operating Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .472█

.........
4.5.3.3.1 General Mains Operating Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .472█

.........
4.5.3.3.2 Reconnecting Mains Operating Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474█

..........
4.5.3.4 Mains Decoupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .474█

.........
4.5.3.4.1 Setup Grid Code AR-–4105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .479█

..........
4.5.3.4.2 Setup Grid Code BDEW (medium voltage guideline) . . . . . . . . . . . . . . . . . . . . . . . . . . . 484█

..........
4.5.3.5 Mains Overfrequency (Level 1 & 2) ANSI# 81O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485█

..........
4.5.3.6 Mains Underfrequency (Level 1 & 2) ANSI# 81U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487█

..........
4.5.3.7 Mains Overvoltage (Level 1 & 2) ANSI# 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489█

..........
4.5.3.8 Mains Undervoltage (Level 1 & 2) ANSI# 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .491█

.........
4.5.3.9 Mains Voltage Increase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .493█

.........
4.5.3.10 Mains Time-Dependent Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495█

..........
4.5.3.10.1 Time Dependent Mains Voltage Monitor 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497█

..........

..........

..........
4.5.3.10.4 Time dependent voltage monitoring – Decoupling Function . . . . . . . . . . . . . . . . . . . . . .506█

.........
4.5.3.11 QV Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .506█

.........
4.5.3.12 Change Of Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .509█

.........
4.5.3.13 Mains Voltage Phase Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .514█

.........
4.5.3.14 Mains Import Power (Level 1 & 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .516█

.........
4.5.3.15 Mains Export Power (Level 1 & 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .518█

.........

Table of Contents
4.5.3.16 Engine/Mains Active Power Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .520█

.........
4.5.3.17 Mains Lagging Power Factor (Level 1 & 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521█

..........
4.5.3.18 Mains Leading Power Factor (Level 1 & 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524█

..........
4.5.4 Breaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .526█

.........
4.5.4.1 Configure GCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526█

..........
4.5.4.2 Configure GCB 50BF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .527█

.........
4.5.4.3 Synchronization GCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .529█

.........
4.5.4.4 Configure MCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530█

..........
4.5.4.5 Synchronization MCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .532█

.........
4.5.4.6 Configure MCB 50BF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .533█

.........
4.5.4.7 MCB plausibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534█

..........
4.5.4.8 Configure Neutral Contactor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .535█

.........
4.5.5 Flexible Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .536█

.........
4.5.6 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .542█

.........
4.5.6.1 General monitoring settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .542█

.........
4.5.6.2 Free Configurable Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .544█

..........
4.5.6.3 CAN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545█

..........
4.5.6.4 CAN Interface 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546█

..........
4.5.6.5 CAN Interface 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547█

..........
4.5.6.6 CAN Interface 2 - J1939 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .549█

.........
4.5.6.7 J1939 Interface - Red (Stop) Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .553█

.........
4.5.6.8 J1939 Interface - Amber Warning Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .555█

..........
4.5.6.9 J1939 Interface - Protect Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .556█

.........
4.5.6.10 J1939 Interface - Emission/Malfunction Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557█

..........
4.5.6.11 J1939 Interface – DM1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .559█

.........
4.5.6.12 Ethernet interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .559█

.........
4.5.6.13 Battery Overvoltage (Level 1 & 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561█

..........
4.5.6.14 Battery Undervoltage (Level 1 & 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562█

..........
4.5.6.15 Monitoring PV load reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .564█

..........
4.5.6.16 Multi-Unit Parameter Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .565█

..........
4.5.6.17 Multi-Unit Missing easYgen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .567█

.........
4.5.6.18 Multi-Unit System Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .568█

.........

Table of Contents
4.5.6.19 Operating Range Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .569█

.........
4.5.6.20 Load Share Interface Redundancy is Lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .571█

.........
4.6 Configure Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .572█

.........
4.6.1 General measurement settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573█

..........
4.6.2 Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .575█

.........
4.6.2.1 Configure transformer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578█

..........
4.6.3 Busbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580█

..........

..........
4.6.4 Mains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581█

..........

..........
4.6.4.2 External Mains Active Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .585█

.........
4.6.4.3 External Mains Reactive Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .586█

.........
4.6.5 Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587█

..........
4.7 Configure Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .588█

.........
4.7.1 USB (Service Port) Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .588█

.........
4.7.2 RS-485 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .589█

.........
4.7.3 Modbus Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .590█

.........
4.7.4 CAN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593█

..........
4.7.4.1 CAN Interface 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593█

..........
4.7.4.1.1 Additional Server SDOs (Service Data Objects) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597█

..........
4.7.4.1.2 Receive PDO {x} (Process Data Object) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .598█

.........
4.7.4.1.3 Transmit PDO {x} (Process Data Object) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601█

..........
4.7.4.2 CAN Interface 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606█

..........
4.7.4.2.1 Expansion Modules at CANopen Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606█

..........
4.7.4.2.2 J1939 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .615█

.........
4.7.5 Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .623█

.........
4.7.5.1 General notes “Network address” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624█

..........
4.7.5.2 Ethernet Network A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625█

..........
4.7.5.3 SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .627█

.........
4.7.6 Load Share Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .628█

.........
4.8 Configure LogicsManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .628█

.........
4.9 Configure AnalogManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633█

..........

Table of Contents
4.9.1 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633█

..........
4.9.2 AnalogManager Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646█

..........
4.10 Configure Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .647█

.........
4.10.1 Generator Preset Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .647█

.........
4.10.2 Service Reset Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .649█

.........
5 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .653█
..........
5.1 Power ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653█

..........
5.2 Change Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .654█

.........
5.2.1 Operating Mode STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .655█

.........
5.2.2 Operating Mode MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .656█

..........
5.2.3 Operating Mode AUTOMATIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658█

..........
5.2.4 Operating Mode TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .659█

.........
5.3 Restore Language Setting via HMI, Buttons and Softkeys . . . . . . . . . . . . . . . . . . . . . . . 661█
..........
6 Application Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .662█

.........
6.1 Basic Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .662█

.........
6.1.1 Application Mode A01 (None) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .662█

.........
6.1.2 Application Mode A02 (GCB open) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664█

..........
6.1.3 Application Mode A03 (GCB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .666█

.........
6.1.4 Application Mode A04 (GCB/MCB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .668█

.........
6.2 Multiple Genset Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671█

..........
6.2.1 Configuration Example: Multiple Genset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .671█

.........
6.2.1.1 Configuring Load-Dependent Start/Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .672█

.........
6.2.1.2 Configuring Automatic Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .675█

.........
6.2.1.3 Configuring Emergency Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .675█

..........
6.2.1.4 Configuring Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676█

..........
6.2.2 Communication Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .676█

.........
6.2.2.1 System Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .676█

.........
6.2.2.2 Diagnostic Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .678█

.........
6.2.2.3 Practicing the System Update Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .682█

.........
6.3 Special Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683█

..........
6.3.1 Generator Excitation Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683█

..........
6.3.2 Configuring A Setpoint Control Via Analog Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685█

..........

Table of Contents
6.3.3 Creating Self-Toggling (Pulsing) Relays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .688█

.........
6.3.4 Changing A Starter Battery Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689█

..........
6.3.5 Performing Remote Start/Stop And Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . .691█

.........
6.3.5.1 Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692█

..........
6.3.5.2 Setting Up A Test With Or Without Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .694█

..........
6.3.5.3 Remote Start/Stop, Shutdown, And Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . 696█

..........
6.3.6 Connecting IKD 1 on CAN Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .700█

.........
6.3.6.1 Configuring an IKD 1 Expansion Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .703█

.........
6.3.6.1.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703█

..........
6.3.6.1.2 Quick Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704█

..........
6.3.6.2 Configuration for a second IKD 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706█

..........
6.3.7 Configuring A PWM Duty Cycle For A CAT ADEM Controller . . . . . . . . . . . . . . . . . . . . . . 708█
..........
6.3.8 Wiring Self Powered Discrete Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .709█

.........
6.3.9 Connecting Analog Inputs In Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709█

..........
6.3.10 Setup Expansion Modules at CAN 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710█

..........
6.3.11 Phase Angle Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719█

..........
6.3.12 Start/Stop Logic Mode "Off" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722█

..........
6.3.13 Ripple Control Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725█

..........
6.3.14 Neutral Interlocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729█

..........
6.3.15 LDSS with predicted load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733█

..........
6.3.15.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733█

..........
6.3.15.2 Internal source mode (EG3500XT only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735█

..........
6.3.15.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .735█

.........
6.3.15.2.2 Example “Emergency power unit” with internal GGB control (only easYgen
3400XT/3500XT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .737█
.........
6.3.15.3 External source mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .739█

.........
6.3.15.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .739█

.........
6.3.15.3.2 LDSS PL CANopen Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741█

..........
6.3.15.3.3 Internally provided analog variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .743█

.........
6.3.15.4 Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .744█

..........
6.3.16 Derating And Uprating Of Power (Details) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745█

..........
6.3.16.1 Direct Derating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .745█

.........
6.3.16.2 Derating With Characteristic Curve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746█

..........

Table of Contents
6.3.16.3 J1939 (ECU) Derating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750█

..........
6.3.17 Examples timer configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .750█

.........
6.4 CANopen Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751█

..........
6.4.1 Remote Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .751█

.........

..........
6.4.1.1.1 RPDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752█

..........
6.4.1.1.2 Default SDO Communication Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753█

..........
6.4.1.2 Transmitting A Frequency Setpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .756█

.........
6.4.1.2.1 RPDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756█

..........

..........
6.4.1.3 Transmitting A Voltage Setpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .758█

..........
6.4.1.3.1 RPDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759█

..........

..........
6.4.1.4 Transmitting A Power Factor Setpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .761█

.........
6.4.1.4.1 RPDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761█

..........

..........
6.4.1.5 Transmitting A Power Setpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763█

..........
6.4.1.5.1 RPDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764█

..........

..........
6.4.1.6 Transmitting Multiple Setpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766█

..........
6.4.1.7 Remotely Changing The Setpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .767█

.........
6.4.1.7.1 RPDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768█

..........

..........
6.4.1.8 Transmitting A Remote Control Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769█

..........

..........
6.4.2 Sending A Data Protocol via TPDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771█

..........
6.4.3 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772█

..........
6.5 Modbus Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .773█

.........
6.5.1 Remote Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .773█

.........

..........
6.5.1.2 Setpoint Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777█

..........
6.5.1.3 Remotely Changing The Setpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .781█

.........

Table of Contents
6.5.2 Changing Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .783█

.........
6.5.2.1 Parameter Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .783█

.........
6.5.2.2 Configuration Of LogicsManager Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .784█

.........
6.5.2.3 Configuration Of LogicsManager Functions For Remote Access . . . . . . . . . . . . . . . . . . . 789█

..........
6.5.2.3.1 Basic remote control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .789█

.........
6.5.2.3.2 Configuration of the LogicsManager "Operation mode AUTO" . . . . . . . . . . . . . . . . . . . . 789█

..........
6.5.2.3.3 Configuration Of Remote Start/Stop, Shutdown, And Acknowledgment . . . . . . . . . . . . .791█

.........
6.5.2.3.4 Configuration Of LogicsManager Function "Start Request in AUTO" . . . . . . . . . . . . . . . .791█

.........
6.5.2.3.5 Configuration Of LogicsManager Function "External Acknowledge" . . . . . . . . . . . . . . . .793█

..........
6.5.2.3.6 Configuration Of LogicsManager Function "Start w/o Load" . . . . . . . . . . . . . . . . . . . . . .794█

..........
6.5.2.4 Remotely Acknowledge Single Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .796█

.........
6.5.2.5 Remotely Clearing The Event History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .796█

.........
6.5.2.6 Remotely Resetting The Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797█

..........
6.5.2.6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .797█
.........
6.5.3 Exception Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799█

..........
6.5.4 Modbus Telegram Mapper (Customer Written Data Protocols) . . . . . . . . . . . . . . . . . . . .800█

..........
6.5.4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800█

..........
6.5.4.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800█

..........
6.5.4.3 Status/diagnostic Modbus Telegram Mapper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801█

..........
6.5.5 Modbus master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .801█

.........
6.5.5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801█

..........
6.5.5.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802█

..........
6.5.5.3 Status/diagnostic Modbus master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .802█

.........
7 Interfaces And Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .806█

.........
7.1 CAN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806█

..........
7.1.1 CAN Interface 1 (Guidance level) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806█

..........
7.1.2 CAN Interface 2 (Engine level) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806█

..........
7.2 Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .807█

.........
7.3 Serial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .808█

..........
7.3.1 RS-485 Interface (Serial Interface 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808█

..........
7.3.2 USB interface (USB 2.0, slave) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .808█

..........
7.4 CANopen Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .808█

.........

Table of Contents
7.5 J1939 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .811█

.........
7.5.1 Displayed Messages (Visualization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811█

..........
7.5.2 Supported J1939 ECUs & Remote Control Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 816█

..........
7.5.3 Device Type Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .819█

.........
7.6 Modbus Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .821█

.........
7.7 Load Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .824█

.........
7.7.1 Load Share via CAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826█

..........
7.7.2 Load Share via UDP Broadcast Messages (Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . 827█

..........
8 Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828█

..........
8.1 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828█

..........
8.1.1 Measuring Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .829█

..........
8.1.2 Ambient Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .830█

.........
8.1.3 Inputs/Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830█

..........
8.1.4 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .832█

..........
8.1.5 Real Time Clock Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .834█

..........
8.1.6 Display (plastic housing variant, only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834█

..........
8.1.7 Housing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834█

..........
8.1.8 Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835█

..........
8.2 Environmental Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835█

..........
8.3 Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .836█

.........
8.4 Protection (ANSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839█

..........
9 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840█
..........
9.1 Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840█

..........
9.1.1 Triggering Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .840█

.........
9.1.2 VDO Inputs Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .845█

.........
9.1.2.1 VDO Input "Pressure" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .846█

.........
9.1.2.2 VDO Input "Temperature" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848█

..........
9.1.2.3 Pt100 RTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .851█

.........
9.1.2.4 Pt1000 RTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .852█

.........
9.1.2.5 NTC-Sender "AB_94099" (AB-Elektronik Sachsen GmbH) . . . . . . . . . . . . . . . . . . . . . . . .853█

.........
9.2 Data Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853█

..........
9.2.1 Protocol 5003 (Basic Visualization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .854█

.........

Table of Contents
9.2.2 Protocol 5004 (Generator Values Visualization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880█

..........
9.2.3 Protocol 5005 (Mains Values Visualization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .886█

.........

.........
9.2.5 Protocol 5011 (Alarm Values Visualization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .925█

.........
9.2.6 Protocol 5014 (Based on Protocol 5003 but with enhancements) . . . . . . . . . . . . . . . . . .945█
.........

.........
9.2.8 Protocol 5017 (Alarm Values Visualization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1015█

..........
9.2.9 Additional Data Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036█

...........
9.2.9.1 Receive Data (sent from remote control to the easYgen) . . . . . . . . . . . . . . . . . . . . . . .1036█
..........
9.2.9.2 Transmit Data (sent from easYgen to control external devices) . . . . . . . . . . . . . . . . . .1044█
..........
9.2.9.3 Data Receive (interconnectivity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046█

...........
9.2.9.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046█

...........
9.2.9.3.2 Analog variables CAN1 RPDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1046█

..........
9.2.9.3.3 Commnand variables CAN 1 RPDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1047█

..........
9.2.9.3.4 Free Analog Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1050█

..........
9.2.9.4 Data Identifiers in General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1051█

..........
9.3 LogicsManager Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1053█

..........
9.3.1 LogicsManager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053█

...........
9.3.2 Logical Command Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056█

...........
9.3.2.1 Group 01: Global alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1056█

..........
9.3.2.2 Group 02: System conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056█

...........
9.3.2.3 Group 03: Engine control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059█

...........
9.3.2.4 Group 04: Application conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1061█

...........
9.3.2.5 Group 05: Engine related alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063█

...........
9.3.2.6 Group 06: Generator related alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1064█

..........
9.3.2.7 Group 07: Mains related alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065█

...........
9.3.2.8 Group 08: Syst. related alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1066█

..........
9.3.2.9 Group 09: Alarms discrete inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1067█

..........
9.3.2.10 Group 10: Alarms analog inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1068█

..........
9.3.2.11 Group 11: Clock and timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068█

...........
9.3.2.12 Group 12: External discrete inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1068█

..........
9.3.2.13 Group 13: Discrete outputs (physical state) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1069█

..........

Table of Contents
9.3.2.14 Group 15: Flexible limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1070█

..........
9.3.2.15 Group 16: Free alarms latched . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1071█

...........
9.3.2.16 Group 17: System alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1072█

..........
9.3.2.17 Group 25: External analog inputs out of range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1072█

..........
9.3.2.18 Group 32: CAN1 Receive PDO1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1073█

..........

..........

..........

..........

..........
9.3.2.23 Group 54: Modbus Master flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075█

...........
9.3.2.24 Group 81: AnalogManager boolean results 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078█

...........
9.3.2.25 Group 82: AnalogManager boolean results 2 (Flexible Limits) . . . . . . . . . . . . . . . . . . . 1079█

...........
9.3.2.26 Group 86: LM Results 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1080█

..........
9.3.2.27 Group 87: LM Results 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1081█

..........
9.3.2.28 Group 88: LM Results 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1082█

..........
9.3.2.29 Group 90: AnalogManager Internal values 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1082█

..........
9.3.2.30 Group 91: AnalogManager Internal values 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1083█

..........
9.3.2.31 Group 93: AnalogManager Analog outputs 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084█

...........
9.3.2.32 Group 96: LM Internal flags 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1084█

...........
9.3.2.33 Group 98: LM External DOs 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1085█

...........
9.3.2.34 Group 99: LM Internal DOs 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086█

...........
9.3.3 Logical Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086█

...........
9.3.4 Logical Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1088█

..........
9.3.5 Factory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1095█

...........
9.4 AnalogManager Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103█

...........
9.4.1 AnalogManager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1103█

..........
9.4.2 Data Sources AM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104█

...........
9.4.2.1 Group 01: Generator values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1104█

..........
9.4.2.2 Group 02: Mains values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106█

...........
9.4.2.3 Group 03: Busbar 1 values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1109█

..........
9.4.2.4 Group 05: Controller setpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109█

...........
9.4.2.5 Group 06: DC analog inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1112█

...........

Table of Contents
9.4.2.6 Group 07: J1939 values 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1112█

...........
9.4.2.7 Group 08: External analog inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1115█

..........
9.4.2.8 Group 09: J1939 values 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1115█

...........
9.4.2.9 Group 10: Internal values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1116█

..........
9.4.2.10 Group 11: Engine values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1117█

..........
9.4.2.11 Group 13: Constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1118█

..........
9.4.2.12 Group 14: Controller values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1118█

...........
9.4.2.13 Group 15: Controller setpoints 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1118█

..........
9.4.2.14 Group 21: CAN1 Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1118█

..........
9.4.2.15 Group 24: Free analog values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1119█

..........
9.4.2.16 Group 81: Results 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119█

...........
9.4.2.17 Group 82: Results 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1120█

...........
9.4.2.18 Group 90: Internal Values 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1122█

...........
9.4.2.19 Group 91: Internal Values 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1122█

...........
9.4.2.20 Group 93: Analog Outputs 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1123█

..........
9.4.3 Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123█

...........
9.4.3.1 Generator Rated Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123█

...........
9.4.3.2 Mains Rated Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1123█

..........
9.4.3.3 Nominal Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1124█

..........
9.4.3.4 Generator/Mains rated active/reactive Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124█

...........
9.4.3.5 Generator/Mains Power Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1124█

..........
9.4.3.6 Generator Rated Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124█

...........
9.4.3.7 Mains rated Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125█

...........
9.4.3.8 Nominal Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1125█

..........
9.4.3.9 Battery Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1125█

..........
9.4.3.10 Fixed Value 10000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1125█

...........
9.4.3.11 Busbar 1 Rated Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1125█

..........
9.4.3.12 Display Value Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126█

...........
9.4.4 Factory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127█

...........
9.5 Status, Event And Alarm Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137█

...........
9.5.1 Status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137█

...........
9.5.2 Event History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1140█

...........

Table of Contents
9.5.3 Event Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1141█

...........
9.5.4 Alarm Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1142█

..........
9.5.5 Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1143█

...........
9.5.5.1 No alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1143█

..........
9.5.5.2 Generator monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1144█

..........
9.5.5.3 Busbar monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146█

...........
9.5.5.4 Mains monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146█

...........
9.5.5.5 Engine monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148█

...........
9.5.5.6 Operating Range Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1149█

..........
9.5.5.7 Breaker Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1151█

..........
9.5.5.8 CANopen Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1152█

..........
9.5.5.9 CAN J1939 (ECU) Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1152█

..........
9.5.5.10 Ethernet Communication Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152█

...........
9.5.5.11 Multi-unit Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153█

...........
9.5.5.12 Flexible Limits Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1153█

..........
9.5.5.13 Digital Inputs Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154█

...........
9.5.5.14 External Digital Inputs Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155█

...........
9.5.5.15 Wire Break Monitoring (of internal and external analog inputs) . . . . . . . . . . . . . . . . . .1156█
...........
9.5.5.16 Free Configurable Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1157█

...........
9.5.5.17 Miscellaneous Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1157█

..........
9.6 Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1158█

..........
9.6.1 Conversion Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1158█

..........
9.6.2 Load Dependent Start Stop (LDSS) Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1159█

...........
10 Glossary And List Of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1161█

..........
11 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1163█
..........

1 General Information
1.1 About This Manual
1.1 About This Manual
1.1.1 Revision History
Rev. Date Editor Changes
I 2020-04 TM
NEW Software Revision Release 2.10 or higher
NEW features & functions
• Introduction of a Modbus Master functionality. ╚═▷ “6.5.5 Modbus master”

• Introduction of a Photovoltaic (PV) inverter load reduction function including of a
monitor feature.╚═▷ “4.4.4.5.6 Photovoltaic (PV) load reduction regulated mode”
• Separate parmeters for mains over/under voltage and over/under frequency
hysteresis.
• Writing LDSS Reserve power into the device: The device allows now a remotely
frequently refreshed reserve power setting.
IOP: ╚═▷ “Remote LDSS IOP reserve power ”
MOP ╚═▷ “Remote LDSS MOP reserve power ”
• Providing of a monitoring function for Ethernet issues.╚═▷ “4.5.6.12 Ethernet

interfaces”
• LDSS: The current reserve power setting (Parameter, LM Parameter or from RAM
variable) is indicated in the ToolKit Status "States easYgen / Sequencing" screen.
• The easYgen provides a "Reboot" parameter in ToolKit and HMI. ╚═▷ “4.3.5.1
Reboot Function”
• Communication protocols 5014 and 5016 are updated with
◦ Negative energy counters
◦ Active and reactive power setpoints
◦ ISOCH information
• Improved System Interconnectivity by providing advanced CANopen and Modbus
access on Analog- and LogicsManager variables. ╚═▷ “9.2.9.3 Data Receive
(interconnectivity)”
• Redundant load share Ethernet A and CAN with alarm. indication is possible.
• The timer setting over the ToolKit screen is improved to make the configuration
more comfortable. There are some configuration examples added. ╚═▷ “6.3.17
Examples timer configuration”
Corrections/Repairs
• Breaker transition mode "Closed Transition": Being in island mode with multiple
running easYgens did not allow constant power control in the single easYgens.
This is fixed now.
• Phase shift (ROCOF) - Not possible to trigger in Decoupling Test Mode. This is fixed
now.
• The disabling of the maintenance call by configure maintenance hours and days to
zero is improved. In the past one last maintenance call was executed even the
hours and days were RESET. This is fixed now.
• Improvement Modbus TCP slave handling: Changed receive of Modbus to fix
occasional blocking of TCP port in multiple Modbus setups.
H 2019-04 PC NEW Software Revision Release 1.16 or higher
• The FRT mains monitoring is further expanded. (VDE-AR-N 4110). See ╚═▷
“4.5.1.3.2 Generator Overfrequency (Level 1 & 2) ANSI# 81O”


• The mains frequency measurement is optimized to reach faster and more reliable
response times regarding mains frequency monitoring. (VDE-AR-N 4110). See ╚═▷
“9.4.2.2 Group 02: Mains values”.
• Some min. and max. adjusting values for configure mains decoupling monitorings
are changed to match the newest grid code demands. (VDE-AR-N 4110)
• Introduction of special mains limits to maintain the resynchronization of the
genset back to mains after a mains failure. (VDE-AR-N 4110). See ╚═▷ “4.5.3.3.2
Reconnecting Mains Operating Range”.
• Introduction of a generator reactive power setpoint [kvar] including the capability
to serve it through interface connection or any free analog input. See ╚═▷
“Remote reactive power setpoint”.
• Introduction of different individually configurable reactive power setpoint filters
(PT1 characteristic). (VDE-AR-N 4110). See ╚═▷ “4.4.4.2.4 Reactive Power / Power
Factor setpoint filter”.
• Introduction of a Reactive power – Voltage curve Q(V). (VDE-AR-N 4110). See ╚═▷
“4.4.4.2.5.3 Reactive Power Q(V) limit”.
• Introduction of a Reactive power – Active power curve Q(P). (VDE-AR-N 4110). See
╚═▷ “4.4.4.2.5.2 Reactive Power Q(P)”.
• Introduction of a Reactive power – Voltage curve Q(V) including voltage limitation.
(VDE-AR-N 4110). See ╚═▷ “4.4.4.2.5 Reactive Power Characteristic”.
• Introduction of a special mains frequency value based on a 200ms gliding average
value to match an accuracy of 50mHz and better. (VDE-AR-N 4110). See ╚═▷
“9.4.2.2 Group 02: Mains values”.
• The over frequency -active power decrease function is expanded with under
frequency -active power increase function. (VDE-AR-N 4110). See ╚═▷ “4.4.4.5.5
Active Power – Frequency Function P(f)”.
• Providing a LogicsManager command variable in order to blocking ROCOF Monitor
during FRT-cases. (VDE-AR-N 4110). See ╚═▷ “9.3.2.7 Group 07: Mains related
alarms”.
• Providing of a configurable hysteresis for mains voltage and frequency monitoring
(VDE-AR-N 4110) in Rev. J changed again.
• Introduction of a pole-slip monitoring function in parallel to mains operation. (VDE-
AR-N 4110)╚═▷ “4.5.1.6.3 Pole Slip Monitoring”
• The generator negative reactive energy [kvar] is now available in the data
protocols 5014 and 5016.
• The AnalogManager provides now the analog variable "Number of starts". See ╚═▷
“9.4.2.10 Group 11: Engine values”.
• The frequency controller "PID analog" provides now a second parameter set. See
╚═▷ “4.4.4.4 Frequency Control”.
• The frequency controller can now alternatively be operated with a speed source.
See ╚═▷ “4.4.4.4 Frequency Control”.
• The device provides now free analog values, which can be set from remote by
communication interface. See ╚═▷ “9.4.2.15 Group 24: Free analog values”.
• The Windows Microsoft driver for USB interface is stored on the easYgen flash
drive.
Corrections/Repairs
• L1-N [%] and L3-N [%] are in AM with wrong percentage value when measurement
system = 1Ph3W. Percentage value is based on Un/sqrt(3). It should be based on
Un/2.
G 2018-12 PC NEW Software Revision Release 1.15 or higher
• To improve the handling of the AnalogManager, the following AM functions have

been changed:
◦ "Compare with Delay On" > C1 entry changed from = [ms] to [s]
◦ "Filter" > C1 entry changed from = [ms] to [s]
◦ "Timer" > C1 entry changed from = [ms] to [s]
◦ "Delay type A" > C1 entry changed from = [ms] to [s]
◦ "Delay type B" > A1 and A2 entries changed from = [ms] to [s]


◦ "Toggle" > A1 and A2 entries changed from = [ms] to [s]
◦ "One shot" > C1 entry changed from = [ms] to [s]
For details see ╚═▷ “The following AnalogManager operations are available:”.
• Rounding of 16Bit Integers in communication protocols 5010 and 5016. AC values

which are supported in a 16Bit integer format are rounded.
• The service tool ToolKit allows now also an Offline Mode (For details see ToolKit
Manual.)
• Different timers (e.g. Cooldown), usually indicated on display, are available as
AnalogManager variables and accessible by communication interface. See ╚═▷
“9.4.2.10 Group 11: Engine values”.
• Introduction of new AnalogManager variables regarding RTC, counter and timer
(For details see ╚═▷ “9.4.2.9 Group 10: Internal values”.)
• Introduction of a customer tool for translations. Makes individual language
translation of the easYgen HMI possible. For details, see ╚═▷ “Localization Tool (for
customized language”.
• Now, the device provides a flag in the LogicsManager that the mains decoupling
monitor is activated. See ╚═▷ “9.3.2.2 Group 02: System conditions”.
• The LDSS parameter alignment monitor is expanded with the settings:
◦ Delay
◦ Self acknowledge
◦ Enabled
For details see ╚═▷ “4.5.6.16 Multi-Unit Parameter Alignment”.
• Introduction of the CAN protocol 5017 with all relevant alarms of an EG3000XT. For
details see ╚═▷ “9.2.5 Protocol 5011 (Alarm Values Visualization)”.
• Change in AnalogManager: The setpoints for W and var are reworked to kW and
kvar for better configuration handling.
• Support of Diesel Particle Filter SPNs according to Deutz EMR4 ECU. Refer to ╚═▷
“7.5.2 Supported J1939 ECUs & Remote Control Messages” for details.
• The time span of excitation the charging alternator (D+) is now configurable. For
details, see ╚═▷ “3.3.4 Charging Alternator”.
• It is now possible to fade out decimals of analog values on the HMI customer
screens. For details see ╚═▷ “4.3.2.1 Configure Customer Screens”.
• The free AnalogManager output values 1-16 are now usable in the CANopen PDO
system. For details see ╚═▷ “9.4.2.14 Group 21: CAN1 Receive”.
• J1939 MTU ECU9: The device supports from now on the function "Rapid start" and
"droop". See ╚═▷ “7.5.2 Supported J1939 ECUs & Remote Control Messages”.
Refer to MTU ECU9 documentation for more details.
• Introduction of ECU (J1939) messages regarding diesel particle filter (DPF). See
╚═▷ “7.5.2 Supported J1939 ECUs & Remote Control Messages”.
• Inverse Time Overcurrent Tp monitor:
The setting Inverse time overcurrent Time constant Tp can now configured on up
to 5 seconds (Before 1.99s)
• Introduction of a new LDSS feature: LDSS with predicted load. For details see ╚═▷
“6.3.15 LDSS with predicted load”.
• Introduction of the J1939 handling for ECU Hatz EDC 17. For details see ╚═▷ “7.5.2
Supported J1939 ECUs & Remote Control Messages”.
• General additionally J1939 SPNs implemented concerning diese particel filter
(DPF). See ╚═▷ “7.5.2 Supported J1939 ECUs & Remote Control Messages” for
details.
• Introduction of a new monitor: Easygen monitors ECU malfunction (emission) and
protection alarm on J1939. See ╚═▷ “7.5.2 Supported J1939 ECUs & Remote
Control Messages” for details.
• The device easYgen3500XT-P2 provides now a dedicated phase rotation monitor
instead a LogicsManager command variable only.╚═▷ “4.5.1.6.2.2 Generator Phase
Rotation”
• Introduction of a new monitor in the easYgen: For multiple easYgen applications a
MCB plausibility alarm can be used. See ╚═▷ “4.4.4.5.4 Derating And Uprating Of
Power ” for details.


• Introduction of breaker monitors for GCB and MCB:
Breaker GCB open alarm 50BF.
Breaker MCB open alarm 50BF.
See ╚═▷ “4.5.4.1 Configure GCB” for details.
• Now, the event logger also provides the information that the "Emergency run" is
finished.
• Special ethernet communication UDP handling included to withstand "broadcast
storm".
• In all application modes with L-MCB the Homepage and submenu "busbar/System/
LS5" indicates now Mains (LS5) instead of LS5 only.
Corrections/Repairs
• The L-GGB feedback is under some circumstances wrong recognized and

accordingly wrong monitored. This is fixed now.
• The event logger got trouble with the entry "Emergency run" under special
circumstances. This is fixed now.
• The ground fault monitor based on the CT measurement was wrongly described in
the manual. This is fixed now. See ╚═▷ “4.5.1.6.2.1 Generator Ground Fault (Level
1 & 2)” for details.
• Improvements regarding Operating range monitoring included.
• Setpoint Ramp active power 2 was not executed in island parallel operation. This
is working correctly now.
• Power Factor setpoint could not be changed in MANUAL mode. This is working
correctly now.
• If "Generator/Busbar" is configured for Homescreen, and measurement for 1 Phase
measurement is set to "Phase-neutral", then the Busbar voltage on Homescreen is
always Zero (000 V), even when there is actually voltage measured. This is fixed
now.
• The issue (ERRATA sheet #25 is solved: Changing from Breaker transition mode
"Parallel" to "Interchange" being parallel to mains and running an export power
setpoint: The MCB is opened immediately without consider the power at the
interchange point. This is now fixed. See ╚═▷ “4.4.3.1.6 Transition Modes (Breaker
Logic)” for details.
• Falling into frequency and voltage droop during island operation (e.g. missing
member) and droop tracking is enabled. This can lead to troubles with frequency
and voltage control, if the MCB shall be synchronized. This is fixed now.
• Improved behavior during Ethernet network errors.
• Home screen engine (HMI) J1939 values. If a configured SPN is not available or
having a sensor defect, HMI indicates "---".
F 2017-09 GG NEW Software Revision Release 1.14-4 or higher
NEW Features & Functions
• The devices are CSA certified (For details see ╚═▷ “8.1.8 Approvals”).
• The device provides now the capability to create an own Modbus address point
list, beginning with address 50,000. For this purpose WW provides a
TelegramMapper software tool to create customer specific DataTelegrams. This self
created DataTelegrams can be used with easYgen-XT revision 1.14 or higher. For
details see ╚═▷ “4.7.3 Modbus Protocol”.
• The device offers the capability to disable the password protection for the
individual interface communication channels. If the password level is disabled the
access level is set on code level 5. For details see ╚═▷ 9126, ╚═▷ 9128, and ╚═▷
9129.
• For running the Remote Panel RP-3000XT with the easYgen-XT, the user can
dynamically switch the Remote Panel into an Full mode, Annunciator mode or Off
mode.
See menu [Parameter / Configuration/Configure HMI / Configure Remote Panel].
Corrections/Repairs


• Issue #19 described in the ERRATA sheet is solved:
Indication of red and amber alarm lamps of ADEC ECU7 in easYgen did not work
(ADEC ECU 7 is transmitting only one byte of DM1, eight are expected).
Restricted to application mode GCB/L-GGB and GCB/L-GGB/L-MCB only: The

feedback of the LS-5 installed over the GGB was always recognized as closed.
Application mode GCB/MCB together with “GCB auto unlock”: If emergency run
was active, “GCB auto unlock” could have caused simultaneous dead bus closure
of GCB and MCB if mains returned during the “GCB open pulse”. This could only
happen in parallel logic if the “GCB open time pulse” (5708) was configured higher
or same than 2 s. (This was because the mains settling time - which is shortened
to 2 s in emergency case - and the “GCB open time pulse” were mismatched.)
Generator power factor monitoring works now even if generator measurement is

configured to 3PH3W.
All visualization values of ADEC ECU7 are indicated now.
MCB plausibility alarm works fine now: If MCB was not enabled (12923 = FALSE)
and start without load was active and emergency run was active, the GCB no
longer will be frequently closed and opened.
• The active power setpoint can be changed now even in island mode and with load
control enabled.
• The event logger stores from now, when the engine has stopped. Until now only
the starting information was stored.
• GCB no longer opens and closes permanently if emergency and start without load
• Setpoint Ramp active power 2 is executed in island parallel operation, too
• Busbar display and voltage of busbar is correct now (HMI and ToolKit), even if
"Generator/Busbar" is configured for HOME screen, and measurement for 1 Phase
measurement is set to "Phase-Neutral".
The Busbar voltage on HOME screen is no longer always Zero (000 V) when there
is actually voltage measured.
• Mains decoupling screen: Text "Overfreq." is changed to "Overfreq.2" and text

"Underfreq." is changed to "Underfreq.2"
• Screens "Configure Breaker", "Monitor Breaker": Corrected hide/unhide of links and
buttons for GGB
• The buttons had no function and this is now corrected:
◦ "Test ON"/"Test OFF" under [Next Page / Diagnostic / Mains decoupling / Mains
decoupling thresholds]
◦ "Execute" under [Next Page / Diagnostic / Mains decoupling / Mains
decoupling test]
◦ [Measured values / Busbar]: Corrected jump at arrow down for non
configurable busbar with breaker mode with LS5
◦ [Measured values / BusbarMainsByLS5]: corrected jump at arrow up for non
configurable busbar with breaker mode with LS5
• MANual operation mode:
◦ The power factor setpoint is now adjustable, if the device runs power factor
control.
◦ In island- or mains parallel operation and when switching the device into
operation mode STOP, the unloading of the generator now is executed before
opening the GCB.
◦ If an analog output is configured to a discrete +/- setpoint (e.g. 05.64), the
value will be updated now.


• If emergency run is active (no mains) AND operating mode is fixed to AUTOmatic
via LogicsManager AND an alarm of class C .. F occurs, the Command
Variable »Emergency run« (04.09) no longer toggles for 2 s and so does not
generate lot of entries in the event history.
• CAN J1939 address claiming: Device did not answer on address claiming request.
• CAN: The baud rate handling in all CAN communication ports has been optimized.
• During cranking: Crank relay could have toggled if speed (measured via MPU)
jittered around firing speed.
Technical Manual updated
• Description, images, and tables updated according to the new features, functions,
and corrections listed above.
• The Ethernet port is named Ethernet #1 or Ethernet A which means the same.
• Two symbols "generator Add-on/Add-off" explained (see ╚═▷ “4.1.5.4
Sequencing”).
• Load Control example updated (see ╚═▷ ⇱).
• NOTE added: Use Pin 61 or (metal housing) protective earth, see ╚═▷ “6.3.8 Wiring
Self Powered Discrete Inputs”.
• More user-friendly description of remotely changing setpoints (see ╚═▷ “6.4.1.7
Remotely Changing The Setpoint” and ╚═▷ “6.5.1.3 Remotely Changing The
Setpoint”).
• Settings proposal for J1939 communication with Cummins ECU (see ╚═▷ “7.5.2
Supported J1939 ECUs & Remote Control Messages”).
• Product label with Unom (see ╚═▷ “8.1 Technical Data”).
• Data Protocols updated:
◦ 5003, start addr. 450066, ID 10149
◦ 5003, start addr. 450120, ID 10298
◦ 5010, start addr. 450111, ID8009
◦ 5014, start addr. 450066, ID 4087
◦ 5014, start addr. 450136, ID 4090
• LogicsManager References update:
◦ 07.xx: IDs changed
• Layout optimizations and typo corrections.
E 2016-12 GG NEW Software Revision Release 1.13 or higher
• A customer specific device name can be entered and will be used e.g. as device
name in Ethernet network. For more details refer to ╚═▷ “4.3.5 System
Management”.
• All monitoring functions in the device are from now on expanded with an
additional functionality:
◦ Each monitor can be individually enabled by an internal LogicsManager flag.
(For example refer to parameter »Enabled« ╚═▷ “4.5.1.3.2 Generator

Overfrequency (Level 1 & 2) ANSI# 81O”).
• Device identification via settings file: Serial number will be part of the .wset file
generated and saved via ToolKit. Device identification, file management, and
support request become much easier.
• AnalogManager became even more flexible:
◦ 16 free configurable and accessible constants enable pre-sets to be used as
AnalogManager input. For details refer to ╚═▷ “4.9.2 AnalogManager
Constants” and ╚═▷ “4.9.1 Operations”.


• »Generator Total AC Power« PGN 65029 is send to Scania S6 ECU via J1939
protocol. For details refer to ╚═▷ “7.5.3 Device Type Standard”.
• Power factor values display (generator and mains) enhanced: Three instead two
decimal places. Refer to ╚═▷ “8.3 Accuracy” for details.
• Fuel level monitoring offers two further SPN available via J1939 interface (refer to
╚═▷ “Standard visualization messages”) and ╚═▷ “9.2.7 Protocol 5016 (Basic
Visualization)”:
◦ SPN 96: Fuel level 1
◦ SPN 38: Fuel level 2
• The "Protection Lamp DM1" status of the J1939 communication is from now on
available as LM 03.44 command variable. Refer to ╚═▷ “9.3.2.3 Group 03: Engine
control” for details.
• Max number of logged events enhanced: 1000 events saved now instead of 300
before. Refer to ╚═▷ “9.5.2 Event History” for details.
• The frequency measurements based on phase-phase and phase-neutral voltages
are monitored on plausibility. For details refer to ╚═▷ “4.5.1.3.1 Plausibility Check
of Voltages' AC Wiring”.
• Both alarm class configuration parameters ╚═▷ 2601 for GCB and ╚═▷ 2621 for
MCB now additionally offer the possibility to select "Control".
• The device stores from now on the three generator current slave pointers in a non-
volatile memory.
• The breaker closed transition time in the mode GCB/MCB has been optimized to
match the <100 ms duration time. Refer to ╚═▷ “ Breaker logic "CLOSED
TRANSIT."” for details.
• The Node-ID of the device in a CAN bus network can be automatically pre-set with
the device number. Parameter ╚═▷ 1894 »Align device no. with Node-ID« must be
configured to "Yes". This will avoid same-number-mismatch.
• Load sharing interface can be switched between CAN and Ethernet. Refer to
parameter »Load share interface« ╚═▷ 9924 for details.
• Island mode:
◦ If - during warm-up - the genset becomes the single engine (by unexpected
drop-out of parallel genset), the warm-up is interrupted immediately to avoid
dead busbar.
• ECU J1939: The transmission rate of PGN 64913 has been changed. For details
refer to ╚═▷ “7.5 J1939 Protocol”.
• The readme.txt file in the device additionally informs, that the Technical Manual
saved in the device will not be updated when executing a firmware update. For
update information please refer to {? ID_9b15c8b26d9247c90a1f64133c80a5f8}.
Corrections/Repairs
PC/laptop with operating system Windows 8.1 and ToolKit running:
◦ USB connection handling is improved.

An additional PHOENIX CAN coupler device is supported:
◦ PHOENIX 27 02 23 0 (with firmware 101 or higher).

The easYgen-XT is not making a reboot procedure if a Modbus TCP write order is
executed on a password protected parameter just at that moment the password
level expires.
SPN 189 "Engine rated speed" is transmitted in time, so "Easygen 3000

communication timeout" J1939 E3 communication will not occur even if ECU
Device type (parameter 15102) is configured to "EGS Woodward".
If ECU Device type (parameter 15102) is configured to "EGS Woodward", it can

happen, that the easYgen is transmitting SPN 189 too slowly. This would cause an


"Easygen 3000 communication timeout" in the E3 and twinkling of the SPN 189
indication at the E3.
• Phase rotation (mismatch) measurement changed: Based now on phase-phase

voltages instead of phase-neutral voltages.
• Complete HMI/display text translated: English text fragments replaced by local
wording.
Technical Manual
• Description, images, and tables updated according to the new features and
functions listed above.
• Wrench button (softkey) explained. For details refer to ╚═▷ “4.1.4.3 Status/
Monitoring Screens”.
• Explained in more detail:
◦ ╚═▷ “6.5.1.3 Remotely Changing The Setpoint”
◦ ╚═▷ “6.4.1.7 Remotely Changing The Setpoint”
D 2016-08-31 GG NEW Software Revision Release 1.12-2 or higher
NO NEW features & functions
Corrections/Repairs
• Internal bugfixing.
Technical Manual
• Revision number updated to fit display/label.
In future the published revision number will be reduced to less details: "X.YY" but
without "-ZZ" e.g., "1.13".
C 2016-06 GG NEW Software Revision Release 1.12-0
• The Wago DI/DO expansion boards are directly configurable now. Refer to ╚═▷
“4.7.4.2.1 Expansion Modules at CANopen Interface” for details.
• The idle mode will be entered into the event logger from now on.
• MPU (Speed sensor): The configuration allows now a minimum rated rpm of 100
rpm. Refer to ╚═▷ “Magnetic pickup input (MPU)” for details.
• The Period of use counter value is from now on available in the AnalogManager
(11.58).
Corrections/Repairs
• Measured frequencies:
The frequency evaluation in the device differentiates between all frequencies for
monitoring and phase-phase frequency for logic purposes.
• TEST mode:
Now in TEST mode »OFF« it is not possible anymore to trigger the TEST button
LED, neither via button nor via LogicsManager.
• Relay 7:
It can now be used, if GCB open command is configured as "Not used".
• Power factor setpoint sent by interface (ID508): Works with negative values, too.
• RPDOs: Work even with short negative integers.
• External DI status: Can be reset in all situations.
• Phoenix expansion boards:
When the Phoenix terminals are powered off the configuration will not be lost.
• RS485 in full duplex mode: Multiple slaves are supported.


• Relay 1 indication in ToolKit is inverted now, like in first generation easYgen-3000.
Technical Manual
• Changes and additional features driven by software update described as listed

above.
• Chapter structure and sequence optimized like AnalogManager Reference. Refer to
╚═▷ “9.4 AnalogManager Reference” for details.
• Name of parameter ID ╚═▷ 2802 corrected.
• Range of LogicsManager command variables group 03, group 04, group 82, group
86, and group 99 corrected.
• AnalogManager variables group 04 deleted.
• AnalogManager variables groups corrected.
• AnalogManager reference value description updated for better alignment with
display/ToolKit.
B 2016-04-14 GG NEW Software Revision
• Describing device software release 1.11-0

• ToolKit Version 5.0 or higher required
• Remote control with Remote Panel RP-3000XT is possible
• WAGO expansion modules are supported now and selectable by parameter ╚═▷
15320 »Select external terminal«.
Refer to ╚═▷ “4.7.4.2.1 Expansion Modules at CANopen Interface” for

configuration details and ╚═▷ “6.3.10 Setup Expansion Modules at CAN 2” for
application related special configuration details.
• Password protection is enhanced:
Alphanumeric password can be changed by ToolKit via USB interface.
The basic code entry for the password got a disguise input.
Refer to ╚═▷ “4.3.4.1.2 Change/Reset Alphanumeric Password” for details.
• Data Protocol 5016 is fully supported.
Refer to ╚═▷ “9.2.7 Protocol 5016 (Basic Visualization)” chapter.
• Modbus TCP:
Instead of 1 connection, the Modbus supports now up to 5 connections running

simultaneously.
Corrections/Repairs
• Open transition mode is running correctly under all circumstances. Issue 1 of

ERRATA 37619 is solved.
• Wrong alarm when device got power cycled during load sharing via Ethernet A is
fixed. »System update« and »Missing easYgen« work correctly.
• Operating range monitoring check item 12 (Error 12) is corrected.
• Issue with changing IP addresses after power cycling is fixed.
• EDS file visualization is corrected.
• Issue with Upper limit for secondary voltage Pt is fixed.
• The RESET command for max. current values is provided.
• Application mode GCB open:
The issue with a short open command , when closing the GCB from external, is
fixed.
• Minor language issues are fixed.

• AnalogManager:
The "Unit" configurations in the Analog inputs were reworked.


Issue fixed with "HMI AnalogManagers" to be parametrized but not saved when no
Password was inserted.
Issue fixed with "AnalogManager handling in ToolKit" to be restarted, if the C1

constant is handled without password release.
Some pictures were corrected.
Refer to ╚═▷ “The following AnalogManager operations are available:” for details.
• Corrections regarding the Load share gateway indication in the HMI are made.
• Minor rework of synchroscope.
• Prevent an unintended parameter default setting if a parameter was changed and
shortly (less than 3 seconds) after the power supply was switched off.
•
Technical Manual
• Changes and additional features driven by software update described as listed

above.
• Description of using USB service port for ToolKit connection updated with more
details.
• Description of Firing Speed and Speed detection and configuration enhanced for
better understanding. Refer to ╚═▷ “4.4.1.2 Engine Start/Stop”.
• Data Telegram updated:
◦ Protocol 3005 (Basic Visualization).
A 2016-02-01 GG NEW ToolKit Software Revision
• Release 5.0
Technical Manual
• Parameter definition added:

◦ 7488 (Ethernet) »Transmission rate«, 7489 »Timeout cycles«,
7485 »Modbus/TCP Slave ID«. For details please refer to description ╚═▷
Chapter 4.7.5.2.
NEW 2016-01-15 GG Technical Manual - 1st issue
• Describing device software release 1.10-0
Notes
New device features & updates in comparison to easYgen-3000 series will be found in
the transition manual #37595. Please check availability at Woodward web site
www.woodward.com.
General data tables relevant for the easYgen-XT series will additionally be found in
Excel files.

1.1.2 Depiction Of Notes And Instructions
1.1.2 Depiction Of Notes And Instructions
Safety instructions
Safety instructions are marked with symbols. The safety instructions are always
introduced by signal words that express the severity of the danger.
DANGER!
This combination of symbol and signal word indicates an immediately dangerous

situation that can cause death or severe injuries if not avoided.
WARNING!
This combination of symbol and signal word indicates a possibly dangerous situation that
can cause death or severe injuries if it is not avoided.
CAUTION!
can cause slight injuries if it is not avoided.
NOTICE!
can cause property and environmental damage if it is not avoided.
Tips and recommendations
This symbol indicates useful tips and recommendations as well as information on

efficient and trouble-free operation.
Additional markings
To highlight instructions, results, lists, references, and other elements, the following
markings are used in these instructions:
Marking Explanation
__▶ Step-by-step instructions
⇨ Results of action steps
╚═▷ References to sections of these instructions and to other relevant

documents
• Listing without fixed sequence

1.2 Copyright And Disclaimer
Marking Explanation
»Buttons« Operating elements (e.g. buttons, switches), display elements (e.g.

signal lamps)
»Display« Screen elements (e.g. buttons, programming of function keys)
[Screen xx / Screen xy / Screen Menu path.

xz] ...
The following information and setting refer to a page on the HMI screen
or ToolKit located as described here.
Some parameters/settings/screens are available only either in ToolKit or

on the HMI/display.
Dimensions in Figures
All dimensions with no units specified are in mm.
1.2 Copyright And Disclaimer

Disclaimer
All information and instructions in this manual have been provided under due
consideration of applicable guidelines and regulations, the current and known state of the
art, as well as our many years of in-house experience. Woodward assumes no liability for
any damages due to:
• Failure to comply with the instructions in this manual
• Improper use / misuse
• Willful operation by non-authorized persons
• Unauthorized conversions or non-approved technical modifications
• Use of non-approved spare parts
The originator is solely liable for the full extent for damages caused by such conduct. The
obligations agreed-upon in the delivery contract, the general terms and conditions, the
manufacturer’s delivery conditions, and the statutory regulations valid at the time the
contract was concluded, apply.
Copyright
This manual is protected by copyright. No part of this manual may be reproduced in any
form or incorporated into any information retrieval system without written permission of
Woodward GmbH.
Delivery of this manual to third parties, duplication in any form - including excerpts - as
well as exploitation and/or communication of the content, are not permitted without a
written declaration of release by Woodward GmbH.
Actions to the contrary will entitle us to claim compensation for damages. We expressly
reserve the right to raise any further accessory claims.

1.3 Service And Warranty
1.3 Service And Warranty

Our Customer Service is available for technical information.
For regional support, please refer to: ══▷ http://www.woodward.com/Support_pgd.aspx.
In addition, our employees are interested in any information and experiences that arise
from usage and can be valuable for the improvement of our products.
Warranty terms
Please enquire with your nearest Woodward representative about the terms of warranty.
For our contact search webpage please go to: ══▷ http://www.woodward.com/

Directory.aspx
1.4 Safety
1.4.1 Intended Use
The genset control unit has been designed and constructed solely for the intended use
described in this manual.
The easYgen-... devices are available in two different enclosures. They are designed to be
installed either on the back plate of a switch gear cabinet (e.g. easYgen-x100.../...-
x400...) or on the front plate of a switch gear panel (e.g. easYgen-x200.../...-x500...).The
terminals are always located on the inner side of the housing.
The genset control unit must be used exclusively for engine-generator system management
applications.
• Intended use requires operation of the control unit within the specifications listed in ╚═▷ “8.1 Technical
Data”.
• All permissible applications are outlined in ╚═▷ “2.2 Application Modes Overview”.
• Intended use also includes compliance with all instructions and safety notes presented in this manual.
• Any use which exceeds or differs from the intended use shall be considered improper use!
• No claims of any kind for damage will be entertained if such claims result from improper use.
NOTICE!
Damage due to improper use!
Improper use of the genset control unit may cause damage to the control unit as well as
connected components.
Improper use includes, but is not limited to:
• Storage, transport, and operation outside the specified conditions.

1.4.2 Personnel
1.4.2 Personnel
WARNING!
Hazards due to insufficiently qualified personnel!
If unqualified personnel perform work on or with the control unit hazards may arise which
can cause serious injury and substantial damage to property.
• Therefore, all work must only be carried out by appropriately qualified personnel.
This manual specifies the personnel qualifications required for the different areas of work,
listed below:
• Well trained for electrical installations.
• Skilled and competent to be aware especially of the local safety regulations.
• Experienced in working on electronic measuring and control devices.
• Allowed to manage the controlled (engine/generator) system.
The workforce must only consist of persons who can be expected to carry out their work
reliably. Persons with impaired reactions due to, for example, the consumption of drugs,
alcohol, or medication are prohibited.
When selecting personnel, the age-related and occupation-related regulations governing

the usage location must be observed.

1.4.3 General Safety Notes
Electrical hazards
DANGER!
Life-threatening hazard from electric shock!
There is an imminent life-threatening hazard from electric shocks from live parts.
Damage to insulation or to specific components can pose a life-threatening hazard.
• Only a qualified electrician should perform work on the electrical equipment.

• Immediately switch off the power supply and have it repaired if there is damage to
the insulation.
• Before beginning work at live parts of electrical systems and resources, cut the
electricity and ensure it remains off for the duration of the work. Comply with the
five safety rules in the process:
◦ cut electricity;
◦ safeguard against restart;
◦ ensure electricity is not flowing;
◦ earth and short-circuit; and
◦ cover or shield neighboring live parts.
• Never bypass a fuse or render it inoperable. Always use the correct amperage when
changing a fuse.
• Keep moisture away from live parts. Moisture can cause short circuits.
Prime mover safety
WARNING!
Hazards due to insufficient prime mover protection
The engine, turbine, or other type of prime mover should be equipped with an overspeed
(over-temperature, or over-pressure, where applicable) shutdown device(s), that
operates totally independently of the prime mover control device(s) to protect against
runaway or damage to the engine, turbine, or other type of prime mover with possible
personal injury or loss of life should the mechanical-hydraulic governor(s) or electric
control(s), the actuator(s), fuel control(s), the driving mechanism(s), the linkage(s), or
the controlled device(s) fail.
Device implemented self test
this Woodward device has a self test check implemented. Permanently under control are:
• processor function and
• supply voltage.
The internal signal "self check" is aligned in series with the inverse signal »Ready for op.
OFF« parameter ╚═▷ 12580. Per default (factory settings) discrete output R01 is
energized/closed if device itself is OK.

LogicsManager (LM) equation parameter ╚═▷ 12580 allows to customize this safety relay.
You can use the result of this equation: LM command variable 99.01 .
Be careful in changing safety relevant settings!
CAUTION!
Uncontrolled operation due to faulty configuration
The discrete output "Ready for operation" must be wired in series with an emergency
stop function.
This means that it must be ensured that the generator circuit breaker is opened and the
engine is stopped if this discrete output is de-energized.
If the availability of the plant is important, this fault must be signaled independently from
the unit.
Modifications
WARNING!
Hazards due to unauthorized modifications
Any unauthorized modifications to or use of this equipment outside its specified

mechanical, electrical, or other operating limits may cause personal injury and/or
property damage, including damage to the equipment.
Any unauthorized modifications:
• constitute "misuse" and/or "negligence" within the meaning of the product warranty
thereby excluding warranty coverage for any resulting damage
• invalidate product certifications or listings.
Use of batteries/alternators
NOTICE!
Damage to the control system due to improper handling
Disconnecting a battery from a control system that uses an alternator or battery-

charging device whilst the charging device is still connected causes damage to the
control system.
• Make sure the charging device is turned off before disconnecting the battery from
the system.
Unit includes a lithium backup battery for Real Time Clock. Field replacement of the
battery is not allowed.
In case of battery replacement please contact your Woodward service partner.

Electrostatic discharge
ᐳ
• Protective equipment: ESD wrist band
NOTICE!
Damage from electrostatic discharge

All electronic equipment sensitive to damage from electrostatic discharge,
which can cause the control unit to malfunction or fail.
• To protect electronic components from static damage, take the

precautions listed below.
1. ▷ Avoid build-up of static electricity on your body by not wearing clothing made of
synthetic materials. Wear cotton or cotton-blend materials as much as possible because
these do not store static electric charges as easily as synthetics.
2. ▷ Before working on terminals on the control unit, ground yourself by touching
and holding a grounded metal object (pipes, cabinets, equipment, etc.) to
discharge any static electricity.
Alternatively wear an ESD wrist band connected to ground.
3. ▷ Before any maintenance work on the control unit, ground yourself by
touching and holding a grounded metal object (pipes, cabinets, equipment,
etc.) to discharge any static electricity.
Alternatively wear an ESD wrist band connected to ground.
4. ▷ Keep plastic, vinyl, and Styrofoam materials (such as plastic or Styrofoam cups,
cigarette packages, cellophane wrappers, vinyl books or folders, plastic bottles, etc.)
away from the control unit, modules and work area.
5. ▷ Opening the control cover may void the unit warranty. Do not remove the printed circuit
board (PCB) from the control cabinet unless instructed by this manual.
If instructed by this manual to remove the PCB from the control cabinet,
follow these precautions:
• Ensure that the device is completely voltage-free (all connectors have

to be disconnected).
• Do not touch any part of the PCB except the edges.
• Do not touch the electrical conductors, connectors, or components with
conductive devices or with bare hands.
• When replacing a PCB, keep the new PCB in the plastic antistatic
protective bag it comes in until you are ready to install it. Immediately
after removing the old PCB from the control cabinet, place it in the
antistatic protective bag.

1.4.4 Protective Equipment And Tools
For additional information on how to prevent damage to electronic components caused

by improper handling, read and observe the precautions in:
• "Woodward manual 82715, Guide for Handling and Protection of Electronic Controls,
Printed Circuit Boards, and Modules".
Notes on marine usage
Marine usage of the easYgen genset control requires additional precautions as listed
below:
The specified marine approvals are initially only valid for metal housing units. They are
only valid for plastic housing units, if they are installed using the screw kit .
• Use all 12 screws and tighten accordingly.
• The easYgen-3000(XT) Series has an internally isolated power supply.
Some additional, independent safety and protection devices are necessary to meet
safety requirements of Rules and Regulations of marine Classification Societies.
• Please refer to the corresponding documents issued by marine Classification

Societies for the applicable requirements.
The easYgen is type approved by LR Lloyd's Register.
• Please consider for final functional arrangements to comply with appropriate Lloyd's
Register Rules as subject of the Plan Approval process.
Protective gear
Personal protective equipment serves to protect risks to the safety and health of persons
as well as to protect delicate components during work.
Certain tasks presented in this manual require the personnel to wear protective
equipment. Specific required equipment is listed in each individual set of instructions.
The cumulative required personal protective equipment is detailed below:
Protective equipment: ESD wrist band
The ESD (electrostatic discharge) wrist band keeps the user's body set to ground
potential. This measure protects sensitive electronic components from damage due to
electrostatic discharge.
Tools
Use of the proper tools ensures successful and safe execution of tasks presented in this
manual.
Specific required tools are listed in each individual set of instructions.

The cumulative required tools are detailed below:
Special tool: Torque screwdriver
A torque-screwdriver allow fastening of screws to a precisely specified torque.
• Note the required torque range individually specified in the tasks listed in this
manual.

2 System Overview
2.1 Display And Status Indicators
2 System Overview
2.1 Display And Status Indicators
HMI and ToolKit are aligned for the same sequence and structure of functions and
parameters.
Restrictions
Full access to all parameters and settings with ToolKit only!
2.2 Application Modes Overview

The genset control provides the following basic functions via the application modes listed
below.
For detailed information on the application modes and special applications refer to ╚═▷
“Device status”.
Application Symbol Function

mode
None A01 No breaker control.
This application mode provides the following functions:
• Measuring of engine/generator parameters (i.e. voltage, frequency, current,

power, coolant temperature, oil pressure, etc.)
• Engine start/stop
GCB open A02 GCB control (open)

• Engine/generator protection (relay output to open GCB)
• Mains failure detection with mains decoupling (GCB)
GCB A03 GCB control (open/close)

• GCB operation (relay output to close GCB)
• Mains failure detection with mains decoupling (GCB)
GCB/MCB A04 GCB/MCB control (open/close)

2 System Overview
2.3 Operation Modes
Application Symbol Function

mode

• GCB operation (relay output to close GCB)
• MCB operation (relay outputs to open and close MCB)
• Mains failure detection with mains decoupling (GCB and/or MCB)
• Auto mains failure operation (AMF)
2.3 Operation Modes

The easYgen-3000XT offers four operation modes:
• AUTO
• MANUAL (MAN)
• TEST
• STOP
• ... and an internal (non) operating phase during starting the device itself
The plastic housing (HMI) version of the easYgen-3000XT enables to select an operation
mode by pressing the according button at the front panel - if current settings allow this
function.
For more information about the operation modes please see ╚═▷ “5.2 Change Operating
Modes”.

3 Installation
3.1 Mount Unit (Sheet Metal Housing)
3 Installation

Dimensions
Fig. 3: Sheet metal housing - dimensions
Mounting into a cabinet
ᐳ
• Special tool: Torque screwdriver
Proceed as follows to install the unit using the screw kit:

3 Installation
1. ▷
Fig. 4: Sheet metal housing - drill plan
Drill the holes according to the dimensions in ╚═▷ Fig. 4 (dimensions shown in mm).
Ensure sufficient clearance for access to the terminals (top and bottom) and
connectors located at the sides.
2. ▷ Mount the unit to the back panel and insert the screws.
3. ▷ Tighten the screws to a torque according to the quality class of the used screws.
Tighten the screws with a crosswise pattern to ensure even pressure

distribution.

3 Installation
3.2 Mount Unit (Plastic Housing)
3.2 Mount Unit (Plastic Housing)

Mount the unit either using the clamp fasteners (╚═▷ “3.2.1 Clamp Fastener Installation”)
or the screw kit (╚═▷ “3.2.2 Screw Kit Installation”).
• Don't drill holes if you want to use the clamp fasteners. If the holes are drilled into
the panel, the clamp fasteners cannot be used anymore.
• In order to enhance the protection to IP 66, fasten the unit with the screw kit instead
of the clamp fastener hardware.
Dimensions
Fig. 5: Plastic housing - dimensions

3 Installation
3.2.1 Clamp Fastener Installation
Panel cutout
Fig. 6: Cutout schematic
Measure Description Tolerance
H Height Total 216 mm —
h Panel cutout 183 mm + 1.0 mm
h' Housing dimension 181 mm
W Width Total 282 mm —
w Panel cutout 249 mm + 1.1 mm
w' Housing dimension 247 mm
Depth Total 96.3 mm —
The maximum permissible corner radius is 4 mm.
ᐳ For installation into a door panel with the fastening clamps, proceed as follows:
1. ▷ Cut out the panel according to the dimensions in ╚═▷ Fig. 6.
Don't drill the holes if you want to use the clamp fasteners. If the holes are
drilled into the panel, the clamp fasteners cannot be used anymore!

3 Installation
2. ▷
Fig. 7: Remove terminals
Loosen the wire connection terminal screws on the back of the unit and remove the wire
connection terminal strip if required.
3. ▷
Fig. 8: Insert screws in clamps
Insert the four clamping screws into the clamp inserts from the shown side (╚═▷ Fig. 8;
opposite the nut insert) until they are almost flush. Do not completely insert the screws
into the clamp inserts.
4. ▷ Insert the unit into the panel cutout. Verify that the unit fits correctly in the cutout. If the
panel cutout is not big enough, enlarge it accordingly.
5. ▷
Fig. 9: Attach clamp inserts
Re-install the clamp inserts by tilting the insert to a 45° angle. (╚═▷ Fig. 9/1) Insert the
nose of the insert into the slot on the side of the housing. (╚═▷ Fig. 9/2) Raise the clamp
insert so that it is parallel to the control panel.

3 Installation
3.2.2 Screw Kit Installation
6. ▷
Fig. 10: Tighten clamping screws
Tighten the clamping screws (╚═▷ Fig. 10/1) until the control unit is secured to the
control panel (╚═▷ Fig. 10/2). Over tightening of these screws may result in the clamp
inserts or the housing breaking. Do not exceed the recommended tightening torque of
0.1 Nm.
7. ▷
Fig. 11: Reattach terminals
Reattach the wire connection terminal strip (╚═▷ Fig. 11) and secure them with the side
screws.
The housing is equipped with 12 nut inserts (╚═▷ Fig. 12), which must all be tightened
properly to achieve the required degree of protection.

3 Installation
Fig. 12: Plastic housing - drill plan
ᐳ
• Special tool: Torque screwdriver
Proceed as follows to install the unit using the screw kit:

1. ▷ Cut out the panel and drill the holes according to the dimensions in ╚═▷ Fig. 12
(dimensions shown in mm).
2. ▷ Insert the unit into the panel cutout. Verify that the unit fits correctly in the cutout. If the
panel cutout is not big enough, enlarge it accordingly.
3. ▷ Insert the screws and tighten to 0.6 Nm (5.3 pound inches) of torque.
Tighten the screws with a crosswise pattern to ensure even pressure

distribution.
If the thickness of the panel sheet exceeds 2.5 mm, be sure to use screws
with a length exceeding the panel sheet thickness by 4 mm.

3 Installation
3.3 Setup Connections
3.3 Setup Connections
NOTICE!
Avoid electrostatic discharge!
Before working with terminals please read and follow the instructions of chapter ╚═▷
“Electrostatic discharge”.
For CAN and RS485 shielded cabling, no more than 25 mm wiring exposed without shield
coverage are allowed at terminal plug side.
General notes
NOTICE!
Malfunctions due to literal use of example values
All technical data and ratings indicated in this chapter are merely listed as examples.
Literal use of these values does not take into account all actual specifications of the
control unit as delivered.
• For definite values please refer to chapter ╚═▷ “8.1 Technical Data”.
Wire sizes
Field wiring shall be made with use of cables which have temperature rating not less
than 90 °C.
AWG mm² AWG mm² AWG mm² AWG mm² AWG mm² AWG mm²
30 0.05 21 0.38 14 2.5 4 25 3/0 95 600MCM 300
28 0.08 20 0.5 12 4 2 35 4/0 120 750MCM 400
26 0.14 18 0.75 10 6 1 50 300MCM 150 1000MCM 500
24 0.25 17 1.0 8 10 1/0 55 350MCM 185
22 0.34 16 1.5 6 16 2/0 70 500MCM 240
Tab. 1: Conversion chart - wire sizes
3.3.1 Terminal Allocation
The device terminals are allocated (similarly for all housing variants) as follows:
• Plastic housing - for easYgen-3200XT-P1 and easYgen-3200XT-P1-LT
• Sheet metal housing - for easYgen-3100XT-P1
The max. possible conductor cross-section of the terminals used is Amax = 2.5
mm2!

3 Installation
3.3.1 Terminal Allocation
LT Variant description
The temperature range is the only difference between standard plastic housing and LT
variant.
The manual is describing plastic housing and metal housing variant. Describing the
plastic housing means both standard and LT variant - if not, it is mentioned!
Fig. 13: Terminals easYgen-3000XT-P1(-LT) plastic housing

3 Installation
3.3.2 Wiring Diagram
Fig. 14: Terminals easYgen-3000XT-P1 sheet metal housing
The Protective Earth terminal 61 is not connected on the sheet metal housing.
• Use the protective earth (PE) connector located at the bottom center of the sheet
metal housing instead.
Common terminal for AC measurement voltages
Mains, generator, and busbar voltage measuring terminals no longer differentiate with
separate terminals for each voltage range.

3 Installation
General recommendations
Ensure appropriate cable cross sections following the local standards and restrictions.
The maximum cable cross section of the terminal blocks is 2.5 mm2.
For every type of signal lines like power supply, DI, DO, AI, AO, MPU:
• Return line has to be close to forward signal line.

• Use cables instead of single wires.
◦ In case of using single wires please do at least one twist per meter to keep
wires together closely.
Plastic housing variants:
• Rout all cables connected to terminal blocks away from back cover.

3 Installation
USB
terminals
USB Ethernet
Screw
Host
In Device #A
preparation
L2/N 480 Vac
40
41
*1
Relay [R01] isolated
[R01] Busbar voltage (system1)
Fixed to ready for operation
42
*1
Relay [R02] 480 Vac
38
L1
43
[R02]
Preconfigured to Centralized alarm
Busbar voltage (system1)
Relay [R03]*1
44
[R03]
Preconfigured to Starter
Relay [R04]*1 N 480 Vac
36
45
[R04]
Preconfigured to solenoid / gas valve
Generator voltage
46
480 Vac
34
47
*1 L3
[R05] Generator voltage
Preconfigured to Preglow
48
Terminals easYgen3100XT/3200X
L2 480 Vac
32
49
*1
[R06] Fixed to „Command close GCB“, Generator voltage
if GCB is activated.
50
*1
Relay [R07] isolated 480 Vac
30
L1
51
Fixed to „Command open GCB“,

[R07] Generator voltage
if GCB is activated otherwised to
52
preconfigured to "Mains decoupling"
480 Vac
28
53
*1
Relay [R08] isolated N
[R08] Fixed to „Command close MCB“, Mains voltage
if MCB is activated.
54
*1
L3 480 Vac
26
55
Fixed to „Command open MCB“,

[R09] if MCB is activated otherwise Mains voltage
preconfigured to „Mains decoupling"
56
*1
Relay [R10]
L2 480 Vac
24
57
[R10] Preconfigured to „Auxiliary services“

Mains voltage
58
*1
Relay [R11]
[R11] Preconfigured to Alarm class A or B
L1 480 Vac
22
59
[R12] *1 Mains voltage

Relay [R12]
60
Preconfigured to Alarm class C, D, E, F
20
61
Earth
Analog output [AO 02]
NC (+/−10Vdc / +/−20mA / PWM) +
19
62
[AO 02]
Voltage Biasing
Do not
+
18
63
Power supply connect!

*2
Isolated, 8 to 40 Vdc Analog output [AO 01]
− −
17
64
(+/−10Vdc / +/−20mA / PWM)

Auxiliary excitation D+ Speed Biasing +
16
[AO 01]
65
isolated
Engine
15
66
Common (terminals 67 to 78) GND

*1
Discrete Input [D01] isolated
[D01] +
14
67
Emergency Stop
*1 [AI 03]
[D02] −
13
68
Start in Auto
Discrete Input [D03] isolated*1 Analog Input Type 1
[D03] +
12
69
Low oil pressure (0 to 2000 Ohm /

[AI 02]
*1 0/4 to 20mA /
[D04] −
11
70
Coolant temperature 0 to 1V)

Discrete Input [D05] isolated*1
[D05] +
10
71
Alarm acknowledgement
*1 [AI 01]
[D06] −
72
Enable MCB
[D07] s1
73
Reply: MCB open

L3
[D08] s2
74
Reply: GCB open

[D09] Generator current s1
75
Alarm input
*1 (isolated) L2
[D10] 1A / 5A compatible s2
76
Alarm input
*1
[D11] Discrete Input [D11] isolated s1
77
Alarm input
L1
[D12] s2
78
Alarm input or Neutral Contactor
+ Mains s1
79
MPU input or Ground current (isolated) L1

− 1A / 5A compatible s2
80
1: RS485_A
terminals
CAN #3
terminals
1: CAN_GND 1: CAN_GND
RS485 #1 2: RS485_B
Screw
Screw
2: CAN_L 2: CAN_L 3: RS485_GND

3: CAN_SHIELD 3: CAN_SHIELD 4: RS485_SHIELD
4: CAN_H CAN #1 4: CAN_H
CAN #2 5: RS485_Y
6: RS485_Z
*1
Subject to technical modifications configurable via Logics Manager easYgen-3000XT Series Wiring Diagram PCB 1
Fig. 15: Wiring diagram easYgen-3100XT-P1/3200XT-P1(-LT)
1) Configurable by LogicsManager
2) Vnom = 12/24 V SELV

3 Installation
Fig. 16: Label/print easYgen-3100XT-P1/3200XT-P1(-LT) wiring

3 Installation
3.3.3 Power Supply
3.3.3 Power Supply
General notes
WARNING!
Risk of electric shock - plastic housing
• Connect Protective Earth (PE) to the unit to avoid the risk of electric shock.
Setup the connection using screw-plug-terminal 61.
• The conductor providing the connection must have a wire larger than or equal to
2.5 mm² (14 AWG). The connection must be performed properly.
WARNING!
Risk of electric shock - sheet metal housing
• Connect Protective Earth (PE) to the unit to avoid the risk of electric shock.
Use the protective earth (PE) connector located at the bottom center of the sheet
metal housing.
• The conductor providing the connection must have a wire larger than or equal to
2.5 mm² (14 AWG). The cable length should be as short as possible.
• The connection must be performed properly.
WARNING!
Permissible differential voltage
The maximum permissible differential voltage between terminal 64 (B-) and terminal 61
(PE) is 100 VRMS. On engines where a direct connection between battery minus and PE is
not possible, it is recommended to use an isolated external power supply if the
differential voltage between battery minus and PE exceeds 100 VRMS.
Woodward strictly recommends to use a power supply that is fulfilling the SELV
restrictions (SELV = separated or safety extra-low voltage, see IEC)
Woodward recommends to use one of the following slow-acting protective devices in the
supply line to terminal 63:
• Fuse NEOZED D01 6A or equivalent or

• Miniature Circuit Breaker 6A / Type C
(for example: ABB type: S271C6 or equivalent)

3 Installation
3.3.3 Power Supply
Power ON
With power ON the easYgen-3000XT device is monitoring self preparation by some

display on screen and button illumination. HOME screen shows the device is working.
Schematic and terminals
Fig. 17: Power supply – wiring
Terminal Description
A 61 PE (protective earth) - plastic housing ONLY
B 63 12/24Vdc (8 to 40.0 Vdc)
C 64 0 Vdc
Tab. 2: Power supply - terminal assignment
Characteristics
Fig. 18: Power supply – crank waveform

3 Installation
3.3.4 Charging Alternator
3.3.4 Charging Alternator
General notes
The charging alternator D+ acts as an pre-exciting output during the engine start-up.
During regular operation, it acts as an input for monitoring the charging voltage.
Fig. 19: Charging alternator - wiring
A 63 Battery B+ (8 to 40.0 Vdc SELV)
B 65 Auxiliary excitation (D+) output
Tab. 3: Charging alternator - terminal assignment
3.3.5 Voltage Measuring
General notes
Woodward recommends protecting the voltage measuring inputs with slow-acting fuses
rated for 2 to 6 A.
The wide range terminals allow several voltages. The current voltage (range) of the
application must be "told" to the genset controller device. Settings are described in
chapter ╚═▷ “4.6 Configure Measurement”.
3.3.5.1 Generator Voltage
General notes
The voltage measuring inputs for 120 V and 480 V are using the same terminals 30 to
36. The current voltage range must be selected by the corresponding settings via HMI
and/or ToolKit.
Parameter ╚═▷ 1800 ("Gen. PT secondary rated volt.") must be configured to the correct
value to ensure proper measurement.

3 Installation
3.3.5.1.1 Parameter Setting '3Ph 4W OD' (3-phase, 4-wire, Open delta)
Fig. 20: Voltage measuring - generator - wiring
Measuring input / Phase Terminal
Generator voltage - L1 A 30
Generator voltage - L2 B 32
Generator voltage - L3 C 34
Generator voltage - N D 36
Tab. 4: Voltage measuring - generator - terminal assignment
3.3.5.1.1 Parameter Setting '3Ph 4W OD' (3-phase, 4-wire, Open delta)
Generator windings
A generator system that is connected to the load through a 3-phase, 4-wire connection
but have the device wired for a 3-phase, 3-wire installation may have the L2 phase
grounded on the secondary side. In this application the device will be configured for 3-
phase, 4-wire OD for correct power measurement.
A L1 A L1 A L1
A1
A1 A2 A1 A5
A2 A5 A2 A6
A6
C2 B6
C6 B6
C1 B5
C2 B2 C5 B5
C1 B1 C2 B2
C1 B1
C B C B C B
L2 L2 C6 B2 L2
C5 B1
L3 L3 L3
Fig. 21: Generator windings - 3Ph 4W OD

3 Installation
3.3.5.1.2 Parameter Setting '3Ph 4W' (3-phase, 4-wire)
Measuring inputs
Fig. 22: Measuring inputs - 3Ph 4W OD
Terminal assignment
Generator voltage - N -/-
Tab. 5: Generator terminal assignment 3Ph 4W OD
Generator windings
A L1 A L1 A L1
A1
A1 A2 A1 A5
A2 A5 A2 A6
A6
C2 B6
N C6 N B6 N B5
C1
C2 B2 C5 B5
C1 B1 C2 B2
C1 B1
C B C B C B
L2 L2 C6 B2 L2
C5 B1
N N N
L3 L3 L3
Fig. 23: Generator windings - 3Ph 4W

3 Installation
Measuring inputs
Fig. 24: Measuring inputs - 3Ph 4W
Terminal assignment
Tab. 6: Generator terminal assignment 3Ph 4W
Generator windings
A L1 A L1
C6 A1
C5 A2
C2 A1
C1 A2
C2 A5
C1 A6
C B C B
L2 L2
B2 B1 B6 B5 B2 B1
L3 L3

3 Installation
Measuring inputs
Terminal assignment
-/- -/- 36

3 Installation
Generator windings
A L1
A1 A5
A2 A6
B6
B5
N
B5 C2 B1 C6 B2
B1
B6 C1 B2 C5
C2
C1
A C
L3
A1 A2
N A5 A6
C6
C C5
N L3
L1 N
Measuring inputs
Terminal assignment

3 Installation
B 32
The 1-phase, 2-wire measurement may be performed phase-neutral or phase-phase.
• Please note to configure and wire the easYgen consistently.
3.3.5.1.5.1 '1Ph 2W' Phase-Neutral Measuring
Generator windings
A
L1
A1 B6
A2 B6
A N
N
A1 A2 A5 A6
N
L1 N
Fig. 29: Generator windings - 1Ph 2W (phase-neutral)
Measuring inputs
Fig. 30: Measuring inputs - 1Ph 2W (phase-neutral)

3 Installation
3.3.5.1.5.2 '1Ph 2W' Phase-Phase Measuring
Terminal assignment
Generator voltage - N B 32
C 34
D 36
Tab. 9: Generator terminal assignment 1Ph 2W (phase neutral)
Never configure the busbar measurement for phase-neutral, if the other systems like
mains and generator are configured as 3ph 3W or 4ph 4W without being the neutral in
the middle of the triangle.
The phase angle for synchronization would be incorrect.
Generator windings
A
L1
A1 B6
A2 B6
A B
L2
A1 A2 A5 A6
B
L1 L2
Fig. 31: Generator windings - 1Ph 2W (phase-phase)

3 Installation
3.3.5.2 Mains Voltage
Measuring inputs
Fig. 32: Measuring inputs - 1Ph 2W (phase-phase)
Terminal assignment
Generator voltage - L3 -/-
-/- -/- 34, 36
Tab. 10: Generator terminal assignment 1Ph 2W (phase-phase)
General notes
and/or ToolKit.
Parameter ╚═▷ 1803 ("Mains PT secondary rated volt.") must be configured with the
correct value to ensure proper measurement.

3 Installation
If the easYgen is intended to be operated in parallel with the mains, the mains voltage
measuring inputs must be connected.
If an external mains decoupling is performed, jumpers between busbar and mains

voltage measuring inputs may be installed.
Fig. 33: Voltage measuring - mains - wiring
Mains voltage - L1 A 22
Mains voltage - L2 B 24
Mains voltage - L3 C 26
Mains voltage - N D 28
Tab. 11: Voltage measuring - mains - terminal assignment

3 Installation
Mains windings
A L1 A L1 A L1
A1
A1 A2 A1 A5
A2 A5 A2 A6
A6
C2 B6
N C6 N B6 N B5
C1
C2 B2 C5 B5
C1 B1 C2 B2
C1 B1
C B C B C B
L2 L2 C6 B2 L2
C5 B1
N N N
L3 L3 L3
Fig. 34: Mains windings - 3Ph 4W
Measuring inputs
Terminal assignment
Mains voltage - N D 28
Tab. 12: Mains terminal assignment 3Ph 4W

3 Installation
Mains windings
A L1 A L1
C6 A1
C5 A2
C2 A1
C1 A2
C2 A5
C1 A6
C B C B
L2 L2
B2 B1 B6 B5 B2 B1
L3 L3
Measuring inputs
Terminal assignment
-/- -/- 28

3 Installation
Mains windings
A L1
A1 A5
A2 A6
B6
B5
N
B5 C2 B1 C6 B2
B1
B6 C1 B2 C5
C2
C1
A C
L3
A1 A2
N A5 A6
C6
C C5
N L3
L1 N
Measuring inputs
Terminal assignment
Mains voltage - N B 24

3 Installation
D 28
Mains windings
A
L1
A1 B6
A2 B6
A N
N
A1 A2 A5 A6
N
L1 N
Fig. 40: Mains windings - 1Ph 2W (phase neutral)
Measuring inputs
Fig. 41: Measuring inputs - 1Ph 2W (phase neutral)

3 Installation
Terminal assignment
Mains voltage - N B 24
C 26
D 28
Tab. 15: Mains terminal assignment 1Ph 2W phase neutral
Mains windings
A
L1
A1 B6
A2 B6
A B
L2
A1 A2 A5 A6
B
L1 L2
Fig. 42: Mains windings - 1Ph 2W (phase-phase)
Measuring inputs

3 Installation
3.3.5.3 Busbar Voltage
Terminal assignment
Mains voltage - L3 -/- -/-
-/- -/- 26, 28
Tab. 16: Mains terminal assignment 1Ph 2W phase-phase
3.3.5.3 Busbar Voltage
General notes
and/or ToolKit.
Parameter ╚═▷ 1812 ("Busb1 PT secondary rated volt.") must be configured to the
correct value to ensure proper measurement.
Fig. 44: Voltage measuring - busbar - wiring
Measuring input / Phase Terminal Amax
Busbar voltage (system 1) - L1 A 38 2.5 mm²

3 Installation
Measuring input / Phase Terminal Amax
Busbar voltage (system 1) - L2/N B 40 2.5 mm²
Tab. 17: Voltage measuring - busbar - terminal assignment
Busbar windings
A
L1
A1 B6
A2 B6
A N
N
A1 A2 A5 A6
N
L1 N
Fig. 45: Busbar windings - 1Ph 2W (phase-neutral)
Measuring inputs
Fig. 46: Measuring inputs - 1Ph 2W (phase neutral)

3 Installation
Terminal assignment
Busbar voltage - phaseL1 A 38
Busbar voltage - N B 40
Tab. 18: Busbar terminal assignment 1Ph 2W phase neutral
Busbar windings
A
L1
A1 B6
A2 B6
A B
L2
A1 A2 A5 A6
B
L1 L2
Fig. 47: Busbar windings - 1Ph 2W (phase-phase)
Measuring inputs
Terminal assignment
Busbar voltage - phase L1 A 38

3 Installation
3.3.6 Current Measuring
Busbar voltage - phase L2 B 40
Busbar voltage - phase L3 -/-
Tab. 19: Busbar terminal assignment 1Ph 2W phase-phase
3.3.6 Current Measuring
3.3.6.1 Generator Current
General notes
WARNING!
Dangerous voltages due to missing load
• Before disconnecting the device, ensure that the current transformer (CT) is short-
circuited.
The current measuring inputs for 1 A and 5 A are using the same terminals 3 to 8. The
current range must be selected by the corresponding settings via HMI and/or ToolKit.
Generally, one line of the current transformers secondary must be grounded close to the
CT.
CAUTION!
External current transformers shall provide insulation adequate to system voltage to

which unit is connected.

3 Installation
3.3.6.1.1 Parameter Setting 'L1 L2 L3'
Fig. 49: Current measuring - generator - wiring
A 8 Generator current - L3 - transformer terminal s1 (k)
B 7 Generator current - L3 - transformer terminal s2 (l)
C 6 Generator current - L2 - transformer terminal s1 (k)
D 5 Generator current - L2 - transformer terminal s2 (l)
E 4 Generator current - L1 - transformer terminal s1 (k)
F 3 Generator current - L1 - transformer terminal s2 (l)
Tab. 20: Current measuring - generator - terminal assignment
3.3.6.1.1 Parameter Setting 'L1 L2 L3'
Fig. 50: Current measuring - generator, L1 L2 L3
Wiring terminals
F E D C B A
L1 L2 L3
Terminal 3 4 5 6 7 8
Phase s2 (l) L1 s1 (k) L1 s2 (l) L2 s1 (k) L2 s2 (l) L3 s1 (k) L3

3 Installation
3.3.6.1.2 Parameter Setting 'Phase L1' 'Phase L2' 'Phase L3'
Wiring terminals
Phase L1 and L3
Phase s2 (l) L1 s1 (k) L1 — — s2 (l) L3 s1 (k) L3
"Phase L1 and L3" applies if the generator voltage measurement is configured to 1Ph 3W
(╚═▷ “3.3.5.1 Generator Voltage”).
Fig. 51: Current measuring - generator, 'Phase L1' 'Phase L2' 'Phase L3'
Wiring terminals
F E D C B A
Phase L1
Phase s2 (l) L1 s1 (k) L1 — — — —
Phase L2
Phase — — s2 (l) L2 s1 (k) L2 — —
Phase L3
Phase — — — — s2 (l) L3 s1 (k) L3

3 Installation
3.3.6.2 Mains Current
3.3.6.2 Mains Current
General notes
WARNING!
circuited.
CT.
Fig. 52: Current measuring - mains - wiring
A 2 Mains current - transformer terminal s1 (k)
B 1 Mains current - transformer terminal s2 (l)
Tab. 21: Current measuring - mains - terminal assignment

3 Installation
Fig. 53: Current measuring - mains, 'Phase L1' 'Phase L2' 'Phase L3'
Wiring terminals
B A
Phase L1
Terminal 1 2
Phase s2 (l) - L1 s1 (k) - L1
Phase L2
Terminal 1 2
Phase s2 (l) - L2 s1 (k) - L2
Phase L3
Terminal 1 2
Phase s2 (l) - L3 s1 (k) - L3
3.3.6.3 Ground Current
General notes
WARNING!
circuited.
The mains current input can be configured to measure the mains current or ground
current. The parameter 'Mains current input' determines, if this input will measure the
mains current (default) or the ground current.

3 Installation
3.3.6.3 Ground Current
CT.
Fig. 54: Current measuring - ground current - wiring
A 2 Ground current - transformer terminal s1 (k)
B 1 Ground current - transformer terminal s2 (l)
Tab. 22: Current measuring - ground current - terminal assignment

3 Installation
3.3.7 Power Measuring
3.3.7 Power Measuring
Fig. 55: Power measuring - wiring
If the unit's current transformers are wired according to the diagram (╚═▷ Fig. 55), the
following values are displayed.
A 1 Mains or ground current
B 2
C 3 5 7 Generator current
D 4 6 8
Parameter Description Sign displayed
Generator real power Genset generating kW + Positive
Generator real power Genset in reverse power - Negative
Generator power factor Inductive / lagging + Positive
(cos φ)
Generator power factor Capacitive / leading - Negative
(cos φ)
Mains real power Plant exporting kW + + Positive
Mains real power Plant importing kW - - Negative
Mains power factor Inductive / lagging + Positive

3 Installation
3.3.8 Power Factor Definition
Parameter Description Sign displayed

(cos φ)
Mains power factor Capacitive / leading - Negative
(cos φ)
Measuring 3PH 3W
The values of single active power, reactive power, and power factor in L1, L2 and L3 are
not displayed. This values can not be determined through this connection type.
3.3.8 Power Factor Definition
Definition
Power Factor is defined as a ratio of the real power to apparent power. In a purely
resistive circuit, the voltage and current waveforms are instep resulting in a ratio or
power factor of 1.00 (often referred to as unity).
In an inductive circuit the current lags behind the voltage waveform resulting in usable
power (real power) and unusable power (reactive power). This results in a positive ratio or
lagging power factor (i.e. 0.85 lagging).
In a capacitive circuit the current waveform leads the voltage waveform resulting in
usable power (real power) and unusable power (reactive power). This results in a negative
ratio or a leading power factor (i.e. 0.85 leading).
Properties
Inductive Capacitive
Load type Electrical load whose current waveform lags Electrical load whose current waveform leads
the voltage waveform thus having a lagging the voltage waveform thus having a leading
power factor. Some inductive loads such as power factor. Some capacitive loads such as
electric motors have a large startup current capacitor banks or buried cable result in
requirement resulting in lagging power factors. leading power factors.
Different power factor i0.91 (inductive) c0.93 (capacitive)

display on the unit
lg.91 (lagging) ld.93 (leading)
Reactive power 70 kvar (positive) -60 kvar (negative)

display on the unit
Output of the + (positive) - (negative)

interface
Current relation to Lagging Leading

voltage
Generator state Overexcited Underexcited
Control signal If the control unit is equipped with a power factor controller while in parallel with the utility:
A voltage lower "-" signal is output as long as A voltage raise "+" signal is output as long as
the measured value is "more inductive" than the measured value is "more capacitive" than
the reference setpoint the reference setpoint
Example: measured = i0.91; setpoint = i0.95 Example: measured = c0.91; setpoint = c0.95

3 Installation
3.3.9 Magnetic Pickup Unit (MPU)
Phasor diagram
The phasor diagram is used from the generator's view.
692.8 VA 90° 692.8 VA 90°
U L3-E U L3-E
I L3
I L3
I L1
U L1-E U L1-E
180° 0° 180° 0°
I L1
I L2
I L2
U L2-E U L2-E
300.0 V −90° 1.0 A 300.0 V −90° 1.0 A
Fig. 56: Phasor diagram: capacitive load (left) and inductive load (right)
General notes
The shield of the MPU (Magnetic Pickup Unit) connection cable must be connected to a
single point ground terminal near the easYgen.
The shield must not be connected at the MPU side of the cable.
The number of teeth on the flywheel reference gear and the flywheel speed must be
configured so that the magnetic pickup input frequency does not exceed 14 kHz.

3 Installation
Overview
Fig. 57: MPU - overview
Fig. 58: MPU - input
A 79 MPU input - inductive/switching
B 80 MPU input - GND

3 Installation
3.3.10 Discrete Inputs
Characteristic
Fig. 59: MPU - characteristic
╚═▷ Fig. 59 shows the minimal necessary input voltage depending on frequency. It is
recommended to ensure input voltage greater than minimal necessary with a margin of 2
to 3 V (especially at high ambient temperature above +50 °C).
General notes
WARNING!
Hazards due to improper implementation of emergency stop
Discrete input [DI 01] "Emergency Stop" is only a signaling input. This input may only be
used to signal that an external emergency stop button has been actuated.
According to EN 60204, this input is not approved to be used as the emergency stop
function.
• The emergency stop function must be implemented external to the control and
cannot rely on the control to function properly.

3 Installation
The discrete inputs are electrically isolated which permits the polarity of the connections
to be either positive or negative.
• All discrete inputs must use the same polarity, either positive or negative signals,
due to the common ground.
Schematic and terminal assignment
Fig. 60: Discrete input - positive polarity signal
Fig. 61: Discrete input - negative polarity signal
A B
66 67 Discrete Input [DI 01] Preconfigured to "Emergency stop"1
GND 68 Discrete Input [DI 02] Preconfigured to "Start in AUTO"1

Common ground 69 Discrete Input [DI 03] Preconfigured to "Low oil pressure"1
70 Discrete Input [DI 04] Preconfigured to "Coolant

temperature"1
71 Discrete Input [DI 05] Preconfigured to "Alarm

acknowledge"1
72 Discrete Input [DI 06] Preconfigured to "Enable MCB"1
73 Discrete Input [DI 07] Fixed to "Reply: MCB open"
74 Discrete Input [DI 08] Fixed to "Reply: GCB open"
75 Discrete Input [DI 09] LogicsManager1
Preconfigured to "Alarm input or

Neutral Contactor"1
Tab. 23: DI 01-12
1 configurable via LogicsManager

3 Installation
3.3.11 Relay Outputs (LogicsManager)
Operation logic
Discrete inputs may be configured to normally open (N.O.) or normally closed (N.C.)
states.
Fig. 62: Discrete inputs - state N.O.
In the state N.O., no potential is present during normal operation; if an alarm is issued or
control operation is performed, the input is energized.
Fig. 63: Discrete inputs - state N.C.
In the state N.C., a potential is continuously present during normal operation; if an alarm
is issued or control operation is performed, the input is de-energized.
The N.O. or N.C. contacts may be connected to the signal terminal as well as to the
ground terminal of the discrete input (╚═▷ “Schematic and terminal assignment”).#
3.3.11 Relay Outputs (LogicsManager)
General notes
CAUTION!
The relay output "Ready for operation" must be wired in series with an emergency stop
function. This means that it must be ensured that the generator circuit breaker is opened
and the engine is stopped if this relay output is de-energize.
• We recommend to signal this fault independently from the unit if the availability of
the plant is important.
For information on interference suppressing circuits when connecting 24 V relays, please

refer to ╚═▷ “3.3.11.1 Connecting 24 V Relays”.
Fig. 64: Relay outputs - schematic

3 Installation
3.3.11.1 Connecting 24 V Relays
N.O. Common
A B Form A
42 41 Relay output [R 01] All Fixed to "Ready for operation"1
43 46 Relay output [R 02] All Preconfigured to "Centralized alarm"1
44 Relay output [R 03] All Preconfigured to "Starter"1
45 Relay output [R 04] All Preconfigured to "Fuel solenoid / gas valve"1
48 47 Relay output [R 05] All Preconfigured to "Preglow"1
50 49 Relay output [R 06] A01 LogicsManager1
A02
A03 Preconfigured to "Command: close GCB"1
A04
52 51 Relay output [R 07] A01 Preconfigured to "Mains decoupling"1
A02 Preconfigured to "Command: open GCB"1
A03
A04
54 53 Relay output [R 08] A01 LogicsManager1
A02
A03
A04 Preconfigured to "Command: close MCB"1
56 55 Relay output [R 09] A01 Preconfigured to "Mains decoupling"1
A02
A03
A04 Preconfigured to "Command: open MCB"1
57 60 Relay output [R 10] All Preconfigured to "Auxiliary services"1
58 Relay output [R 11] All Preconfigured to "Alarm class A and B"1
59 Relay output [R 12] All Preconfigured to "Alarm class C, D, E or F"1
1 configurable via LogicsManager
NOTICE!
Damage to adjacent electronic components due to induced voltages
• Implement protection circuits as detailed below.

3 Installation
Fig. 65: Protection circuit (example)
Interferences in the interaction of all components may affect the function of electronic
devices. One interference factor is disabling inductive loads, like coils of electromagnetic
switching devices.
When disabling such a device, high switch-off induced voltages may occur, which might
destroy adjacent electronic devices or result interference voltage pulses, which lead to
functional faults, by capacitive coupling mechanisms.
Since an interference-free switch-off is not possible without additional equipment, the

relay coil is connected with an interference suppressing circuit.
If 24 V (coupling) relays are used in an application, it is required to connect a protection

circuit to avoid interferences.
╚═▷ Fig. 65 shows the exemplary connection of a diode as an interference suppressing

circuit.

3 Installation
3.3.12 Analog Inputs (0 to 2000 Ohm | 0/4 to 20 mA | 0 to 1 V)
Advantages and disadvantages of different interference suppressing circuits are as

follows:
Connection diagram Load current / voltage Advantages Disadvantages

curve
Uncritical dimensioning High release delay
Lowest possible induced

voltage
Very simple and reliable
Uncritical dimensioning No attenuation below VVDR
High energy absorption
Very simple setup
Suitable for AC voltage
Reverse polarity protected
HF attenuation by energy Exact dimensioning

storage required
Immediate shut-off limiting
Attenuation below limiting

voltage
Very suitable for AC voltage
Reverse polarity protected
It is recommended to use two-pole analog senders for best possible accuracy.
Connect the resistive analog input's return wires (GND) always to Engine Ground
(terminal 15) and as close to the easYgen terminals as possible.
For two pole senders of 0/4 to 20 mA or 0 to 1 V sensors Engine Ground is no "must

have".
The following curves may be used for the analog inputs:
• Table A
• Table B
• Linear
• Pt100
• Pt1000
• AB 94099
• VDO 120° C
• VDO 150° C

3 Installation
• VDO 10 bar
• VDO 5 bar
The 9 setpoints of the free configurable Tables A and B can be selected for Type definition
(parameters 1000, 1050, and 1100).
A catalog of all available VDO sensors is available for download at the VDO homepage
(══▷ http://www.vdo.com)
Wiring senders
Fig. 66: Analog inputs - wiring senders
AI01 A 10 Analog input [AI 01 +]
B 9 Analog input [AI 01 -] ground, connect with Engine ground terminal 15
B 11 Analog input [AI 02 -]
B 13 Analog input [AI 03 -] ground, connect with Engine ground terminal 15

3 Installation
3.3.13 Analog Outputs
CAUTION!
Mixed senders
When both types resistive sender and single pole sender are connected to the device,
connection from minus (pins 9, 11, 13) should be made with short wire to the Engine
Ground (pin 15) on input connector.
Wiring single and two-pole senders simultaneously
It is possible to combine single- and two-pole senders but with the lower accuracy.
3.3.13 Analog Outputs
The easYgen offers current, voltage or PWM analog outputs for different applications.
Most commonly they are used for speed and voltage biasing.
Controller configuration can change the multifunction controller bias output signals. The
analog outputs are galvanically isolated.
3.3.13.1 Analog Outputs (±20 mA, ± 10 V, PWM)
Controller wiring - two wires
Fig. 67: Analog controller output - two wires
CAUTION!
Connecting external power sources to the analog outputs may damage the device.
In case that higher permanent insulation voltages are required than described in the
technical data, please install isolation equipment (isolation amplifier) for proper and safe
operation.
Type Terminal Description
I A 16 + Analog output [AO

01]
Current B 17 GND
or
V*
Voltage
(Don't connect terminal 18!)

3 Installation
3.4 Setup Interfaces
Type Terminal Description
I A 19 + Analog output [AO

02]
Current B 20 GND
or
V*
Voltage
*) Internal shunt (resistor) is managed automatically.
3.4 Setup Interfaces
NOTICE!
Before working with terminals please read and follow the instructions of chapter ╚═▷
“Electrostatic discharge”.
For CAN and RS485 shielded cabling, no more than 25 mm wiring exposed without shield
coverage are allowed at terminal plug side.
3.4.1 Interfaces overview
Unshielded cable length
For CAN and RS-485:
• Cabling without shield coverage should be less than 25 mm.
The following drawing shows all available interfaces of the device:
3.4.2 RS-485 Interface
General notes
The easYgen must be configured for half- or full-duplex configuration.

3 Installation
Pin assignment
For location of interface 7 see ╚═▷ “3.4.1 Interfaces overview”.
Fig. 68: screwable 6-terminal connector - RS-485
Terminal Description .. used for FULL duplex ... used for HALF duplex Amax
mode mode
1 A A (RxD+) 1.5 mm2
2 B B (RxD-) 1.5 mm2
3 GND GND - local galvanically isolated 1.5 mm2
4 SHLD Shield connected to earth via RC element 1.5 mm2
5 Y Y (TxD+) Y (TxD+ / RxD+) 1.5 mm2
6 Z Z (TxD-) Z (TxD- / RxD-) 1.5 mm2
Tab. 24: Pin assignment
RS-485 half-duplex
Fig. 69: RS-485 - connection for half-duplex operation (120 Ohms termination resistor
at both ends)

3 Installation
3.4.3 USB (2.0 slave) interface - Service Port
RS-485 full-duplex
Fig. 70: RS-485 - connection for full-duplex operation
Shielding
easYgen-3000XT is prepared for shielding: Terminal 4 and the connector housing are
internally grounded via an RC element. Therefore, they may either be grounded directly
(recommended) or also via an RC element on the opposite connection.
Fig. 71: Shielding preparation (internal RC element)
3.4.3 USB (2.0 slave) interface - Service Port
General notes
Avoid electrostatic discharge during USB cable connection to the unit.

3 Installation
3.4.4 CAN Bus Interfaces
To connect this USB 2.0 (slave) device a USB cable with USB Type A (PC/laptop side) and
Type B (Woodward device side) connectors is necessary.
USB cable length shall be limited up to 3 m. It is recommended to use professional (high

quality) USB cable: 28AWG/1P+24AWG/2C with good shielding.
Use USB service port for ToolKit connection
The USB interface is a service port and the preferred ToolKit connection!
'Read only' USB interface
For location see ╚═▷ “3.4.1 Interfaces overview”.
For others than ToolKit connection the USB interface is read-only!
It can be used for further service tasks from manufacturer's side.
Connecting it to a PC/laptop will display the USB interface available and all files prepared
from Woodward manufacturing side. Read/write attributes of this service port are
restricted to read only.
Avoid electrostatic discharge during cable connection to the unit.
Pin assignment
For location of interface 5 and 6 see ╚═▷ “3.4.1 Interfaces overview”.
Fig. 72: screwable 6-terminal connector - CAN bus
Terminal Description Amax
1 GND - local galvanically isolated 1.5 mm2

3 Installation
Terminal Description Amax
2 CAN-L 1.5 mm2
3 Shield 1.5 mm2
4 CAN-H 1.5 mm2
5 Not connected 1.5 mm2
6 Not connected 1.5 mm2
Topology
Please note that the CAN bus must be terminated with a resistor, which corresponds to
the impedance of the cable (e.g. 120 Ω, 1/4 W) at both ends.
The termination resistor is connected between CAN-H and CAN-L.
Fig. 73: CAN bus - termination
For very critical EMC conditions (many noise sources with high noise levels) and for high
transmission rates we recommend to use the 'Split termination concept' as shown.
• Divide the termination resistance into 2x60 Ohms with a center tap connected to
ground via a capacitor of 10 to 100 nF.
Maximum CAN bus length
The maximum length of the communication bus wiring is dependent on the configured
baud rate. Observe the maximum bus length.
(Source: CANopen; Holger Zeltwanger (Hrsg.); 2001 VDE VERLAG GMBH, Berlin und
Offenbach; ISBN 3-8007-2448-0).
Baud rate Max. length
1000 kbit/s 25 m
800 kbit/s 50 m
500 kbit/s 100 m
250 kbit/s 250 m

3 Installation
3.4.5 Ethernet Interface (incl. Remote Panel)
Baud rate Max. length
125 kbit/s 500 m
50 kbit/s 1000 m
20 kbit/s 2500 m
Bus shielding
All bus connections of the easYgen are internally grounded via an RC element. Therefore,
they may either be grounded directly (recommended) or also via an RC element on the
opposite bus connection.
A shielded cable with shielded plug is required.
Fig. 74: Bus shielding (internal RC element)
Troubleshooting
If there is no data transmission on the CAN bus, check for the following common CAN bus
communication problems:
• A T-structure bus is utilized

• CAN-L and CAN-H are switched
• Not all devices on the bus are using identical baud rates
• Termination resistor(s) are missing
• The configured baud rate is too high for wiring length
• The CAN bus cable is routed in close proximity with power cables
Woodward recommends the use of shielded, twisted-pair cables for the CAN bus (see
examples).
• Lappkabel Unitronic Bus CAN UL/CSA

• UNITRONIC-Bus LD 2×2×0.22
This Ethernet interface 10/100Base-T/-XT complies with the IEEE 802.3 specifications.

3 Installation
Avoid electrostatic discharge during Ethernet cable connection to the unit.
Pin assignment
For location of interface 8 see ╚═▷ “3.4.1 Interfaces overview”.
Fig. 75: RJ-45 connector - Ethernet
Pin Description 10Base-T 100Base-T
1 Transmit Data+ TX+ TX+
2 Transmit Data- TX- TX-
3 Receive Data+ RX+ RX+
4 Not connected NC NC
6 Receive Data- RX- RX-
Notes
NC: Not connected
Visualization
Two LEDs (green and yellow) indicate communication status as well known by the
standard.
• The green LED indicates the link activity: blinking during data transmission.
• The yellow LED indicates the link (speed) status:
◦ 10MB – LED switched-OFF
◦ 100MB – LED switched-ON

3 Installation
General notes
Ethernet category 5 (STP CAT 5) shielded cable is required with shielded plug RJ45. The
chosen switch shall support a transmission speed of 10/100 Mb/s with a network segment
expansion capability of 100 m.
Flexibility
The Ethernet port has auto MDI/MDI-X functionality what allows to connect straight-
through or crossover Ethernet cable.
The Ethernet port is named Ethernet #1 or Ethernet A which means the same.
Cable length / distance
The maximum length from connection to connection is 100 m. Some third party suppliers
offer technology to expand the connection.
Topology
Fig. 76: Application Example: Simple constellation with easYgen-3000XT and

RP-3000XT
Remote Control
The Woodward Remote Control is able to visualize the display of the remotely controlled
device and to make front button and soft key related functionality available.
Access via Remote Panel PR-3000XT is described in chapter ╚═▷ “4.3.6 Configure Remote
Panel Mode” and the Technical Manual »37593 RP-3000XT«.

3 Installation
Fig. 77: Application Example: Multiple Generator operation with a ToolKit access point
(A)

3 Installation
Fig. 78: Application Example: Multiple Generator operation with a ToolKit access point
(B)
Troubleshooting
Check first the power supply of the switches.
Check the IP addressed of the single devices. See chapter ╚═▷ “4.7.5 Ethernet Interfaces”
for details.

4 Configuration
4 Configuration
Parameter Numbers
All parameters are assigned a unique parameter identification number.
The parameter identification number may be used to reference individual parameters

listed in this manual.
This parameter identification number
• is also displayed in the ToolKit configuration screens next to the respective

parameter
• can be used with ToolKit "search" functionality
◦ to find all ToolKit screen this parameter appears
◦ to directly jump to the preferred ToolKit screen
Values of variables and parameters
This device is working with variables and values in FLOAT format. This allows to handle
values by number and exponent.
There is a need to convert FLOAT to INTEGER (32 bit) for common Data Protocols,
communication with some PLCs, and for some display restrictions.
Rounding error
Numbers higher than 8388608 come with an rounding error of 0.005% of the number
itself.
☼ Displayed restrictions sample
Values of user defined tables ([Parameter / Configuration / Configure Application /

Configure inputs/outputs / Configure analog inputs / General analog inputs / User
defined table A/B]) have an input range from -900000.000 to 900000.000.
Type 12345.678 and ...
• ToolKit display will immediately change to 12345.680 for rounding error

• HMI/display shows 12345.678
• ... independent from where value is typed in (ToolKit or HMI/display)
Handle value and unit separately
Some parameters have a separate definition of value and unit. This flexibility comes with
the need to take additional care for factorized units like "k..., M..., m..., µ..." multiplying or
dividing the number of the value.
Values and units must fit
Device and software offer a very flexible handling of values with well defined selectable
rules. It is on customers responsibility to combine what fits.
From device side it is neither restricted nor controlled to use values in a wrong way.

4 Configuration
Configuration and Rebooting
Wait before rebooting
Changing configuration/parameters becomes effective immediately. To be sure that

the changes have been saved internally, wait about 20 seconds before
rebooting or disconnecting the power.
Menu structure (menu tree)
The menu structure of HMI/display and ToolKit is aligned.
Exceptions
• The well introduced HMI/display softbutton »Next Page« is continued but in ToolKit
named »STATUS MENU«.
(In ToolKit »Next Page« is used to go to the next page.)
• Some monitoring parameters in HMI/display are in ToolKit placed directly with it's
settings e.g.: find 10341 »Freq. dep. derating of power« at
[Next page / Setpoints / Derating] in HMI/display but
[PARAMETER / Configure: Configure application / Configure controller: Load control /

General load control] in ToolKit
• »Sequencing« in HMI/display comes with a separate softbutton - ToolKit offers the

information together with others as part of the »States easYgen/
Sequencing« screen.
The following drawing shows the first three (major) levels of the easYgen-3100XT-
P1/3200XT-P1 menu structure:

4 Configuration
Fig. 79: Menu structure (menu tree) easYgen-3100XT-P1/3200XT-P1

4 Configuration
4.1 Front Panel Access
4.1 Front Panel Access
The following chapters only apply to model with front panel and display.
Front Panel / HMI / display
Buttons can be disabled by ToolKit with parameter ╚═▷ 12978 »Lock keypad«.
4.1.1 Basic Navigation
Main screen
After power-up the control unit displays the main screen / HOME screen (╚═▷ Fig. 80).
The main screen can be divided into the following basic sections:
Fig. 80: Main screen (shown with default settings for screen configuration)
1 Values
2 Status Messages
3 Alarm Messages
4 Single Line Diagram
5 Current Softkey Functions

4 Configuration
Values »1«
The "values" section (╚═▷ Fig. 80/1) of the screen illustrates all measured power related
information including voltages, currents, frequencies, power, and power factor values.
If the mains data display is disabled, the main screen will only show generator data with
bigger digits.
The section's content changes based on the selected sub-menu screen.
For information on specialized menu screens refer to ╚═▷ “4.1.5 Specialized Menu
Screens”
Status messages »2«
The "status message" section (╚═▷ Fig. 80/2) of the screen shows the actual operating
information.
For a list of all operation states refer to ╚═▷ “9.5.1 Status messages”.
Alarm messages »3«
The "alarm message" section (╚═▷ Fig. 80/3) of the screen shows the last alarm message
that is occurred and not yet acknowledged.
For a list of all alarm messages refer to ╚═▷ “9.5.5 Alarm Messages”.
Single line diagram »4«
The single line diagram (╚═▷ Fig. 80/4) shows the current status of the engine and power
circuit breakers.
This section is also used for manual operation of the genset.
For additional information refer to ╚═▷ “5.2.2 Operating Mode MANUAL”.
Softkeys »5«
The softkeys (╚═▷ Fig. 80/5) permit navigation between screens, levels and functions as
well as configuration and operation.
Group Softkey Caption Description
Display Display Mode Next step to display all measured (delta/wye) voltages one
after the other.
Customer configurable Change to "customer specific screen 1 (or 2)"

screen 1 (and 2)
Notes

4 Configuration
Group Softkey Caption Description

The name of this softbuttons is configurable, too.
CAN 1 Change to "CAN interface 1 state" screen.
CAN 2 Change to "CAN interface 2 state" screen.
Ext. I/O Change to external discrete I/Os screen.
Int. I/O Change to internal discrete I/Os screen.
Reset Value Display Reset the maximum value display.
Reset Maintenance Reset the maintenance counter.
Operation Increase Value Increase selected value.
Decrease Value Decrease selected value.
Confirm Input Confirm and store changed value.
Acknowledge Message Acknowledge/Delete message/event.
Open Breaker Open mains/generator breaker (MANUAL mode).
Close Breaker Close mains/generator breaker (MANUAL mode).
Code req. Request a blink code for one error message from the ECU.
Repeated pressing of this softkey displays all stored error

messages (J1939 Special Screen).
Reset Reset the blink code (J1939 Special Screen).
Navigation Move Up Select previous value/entry.
Move Down Select next value/entry.
Move Cursor Position Move cursor position
Return Return to previous menu.
Next Page Go to following page/screen of the current menu.
Parameter Screen Show parameter screen.
Alarm Screen Show alarm screen.
Status symbols
Menu screen Symbol Caption Description
Main Screen Voltage Display Mode The index of the symbol indicates whether delta or wye
voltage is displayed and which phases are displayed.
Single Line Rotating Field CW Generator, mains or busbar rotating field moves clockwise.
Diagram

4 Configuration
Menu screen Symbol Caption Description
Rotating Field CCW Generator, mains or busbar rotating field moves counter-
clockwise.
Power Detected Power is detected at the respective measuring point

(generator, busbar or mains).
Monitoring Enabled Indicates that the engine delayed monitoring has expired
and the monitoring functions are enabled.
Power Imported Power is imported (at mains interchange).
Power Exported Power is exported (at mains interchange).
Alarm List Alarm Condition Present Indicates that corresponding alarm condition is still present.
Alarm class A/B/C/D/E/F Symbol with "!" indicates that an alarm of class A/B/C/D/E/F
present is present.
Alarm class A/B/C/D/E/F not Symbol without "!" indicates that an alarm of class
present A/B/C/D/E/F is not present.
Setpoints Generator Power Indicates the generator power (actual value).
Mains Power Indicates the mains power (actual value).
Synchroscope Phase Angle Indicates the actual phase angle between busbar and
mains or busbar and generator.
Sequencing Breaker Closed GCB of respective genset in sequence is closed.
Breaker Open GCB of respective genset in sequence is open.
Add-on Generator is becoming "Add-on" to the (multiple) genset

system.
Add-off Generator is going "Add-off" from the (multiple) genset

system.
LogicsManager Delay ON Delay before output becomes TRUE.
Delay OFF Delay before output becomes FALSE.
TRUE/enabled Variable is TRUE (LogicsManager).
The bit is enabled (CAN Interface).
Relay activated (Discrete Outputs)
FALSE/disabled Variable is FALSE (LogicsManager).
The bit is disabled (CAN Interface).
Relay deactivated (Discrete Outputs)
The following chapters list notes related to the specific menu screens.
For information on standard softkeys and status symbols refer to ╚═▷ “4.1.1 Basic
Navigation”.

4 Configuration
4.1.2 The HOME Screen
General notes
Fig. 81: HOME page/screen
• The “Home” button is a one-click way back to the overview starting point: the HOME
page / HOME screen
• The “Home Screen” offers display alternatives via parameter ╚═▷ 4103» Home
screen data«
◦ Generator
◦ Generator/Mains
◦ Generator/Busbar
◦ Generator/Engine
• To display the single line diagram with/without mains is selectable via parameter
╚═▷ 4129 »Oneline diagram with mains«
• Two customizable buttons enable selection of indications to display engine and

auxiliary values (full access via ToolKit, name/description cannot be changed via
HMI)
Find menu: [Parameter / Configure HMI / Configure customer screen x]
• Two display brightness levels can be switched by LogicsManager. Can be used for
e.g.:
◦ Key activation determined
◦ Brightness reduction on navigation bridge (vessels)
◦ Saving energy
Find menu: [Parameter / Configure HMI / Configure display]
• Lock keypad function is determined by LogicsManager ╚═▷ 12978. Result is available

as logical command variable 86.30.

4 Configuration
Find menu (ToolKit only!): [Parameter / Configure HMI / Configure display]
Display alternatives
The HOME screen allows a number of pre-selectable and softbutton controlled display
variants.
• Generator
◦ Voltages (pp - pn) - selectable via softbutton »1«
◦ Power
◦ Power Factor PF
◦ Frequency
◦ Currents (L1, L2, L3)
• Generator/Mains
◦ Generator values as described above
and additionally for Mains
◦ Voltage
◦ Frequency
◦ Current
◦ Power
◦ Power factor
• Generator/Busbar
and additionally for Busbar
◦ Voltage
◦ Power
◦ Frequency
• Generator/Engines
and additionally for Engine
◦ Engine speed (rpm)
◦ Oil pressure (bar or psi)
◦ Water temperature (°C or °F)
◦ Operating hours (h)

4 Configuration
◦ Battery voltage (V)
◦ Fuel level (%)
Fig. 82: AnalogManagers for "Engine" values at Home Screen
"Engines" parameter selection
The values to be displayed at "Engines" can be selected via AnalogManager definition of

the parameters at [Parameter / Configure HMI / Screen configuration]. Menu texts and
symbols cannot be changed!

4 Configuration
4.1.3 Customer Screens
Fig. 83: Customer Screen sample: "Engine"
Available at HOME page, two softbuttons give one-click access to customer specific
(monitoring) screens.
Full functionality available via ToolKit. HMI allows access to the AnalogManager but not to
the text fields »Description« and »Unit«.
Find menu: [Parameter / Configure HMI / Configure customer screen x / AM Customer

screen x.x]

4 Configuration
How to customize screens via ToolKit?
Fig. 84: Customer screen: setting sample
Two customer specific named screens enable flexible configuration of up to 18 values.

Each displayed with Description (customer specific text), the result of a free configurable
AM, and (a customer specific text for) Unit.
Customize via Parameter Description
Configure homepage button names for screen 1 and screen 2:
Screen/button Name 14895, 14897 Button text, displayed at easYgen-XT HMI

homepage
Notes
The display allows two rows with five letters

each. Use <WBR> for row separator because
a blank is taken as one letter.
If the text is too long it will not be visible and

an "empty/clear button" will appear! We
propose to check input immediately by
refreshing home screen.
Configure each row of the customer screens with:
Description 7691, 7696, 7701, ..., 7776 Text displayed

4 Configuration
4.1.4 Standard Menu Screens
Customize via Parameter Description
Value AM 7690, 7695, 7700, ..., 7775 AnalogManager to select parameter for
display. Additionally available via , too.
Unit 7692, 7697, 7702, ..., 7777 Text displayed
4.1.4 Standard Menu Screens
The following chapters list standard menu screens, where all user input is handled
similarly.
For information on standard softkeys and status symbols refer to ╚═▷ “4.1.1 Basic
Navigation”.
For information on all other menu screens refer to ╚═▷ “4.1.5 Specialized Menu Screens”.
4.1.4.1 Navigation Screens
Fig. 85: Navigation screen (example)
Navigation screens offer access to sub-menu screens via the displayed softkey.
Navigation screens samples:
Parameter, Configuration, Measured values, Synchroscope, Engine (J1939), Diagnostic ...
1. ▷ Press the desired softkey to change to a sub-menu screen.

4 Configuration
4.1.4.2 Value Setting Screens
Sub-menu entries are only displayed if the code level needed to access
them is the same/or higher than the displayed code level in the center of the
navigation screen.
4.1.4.2 Value Setting Screens
Fig. 86: Value setting screen (example)
At value setting screens the settings of the parameters can be changed.
Value setting screens samples:
Configure language / clock, Configure display, Password, Configure application ...
1. ▷ Use the following softkeys in a value setting screen to select, change and confirm a
setting.
Softkey Description
Select previous value/entry.
Select next value/entry.
Increase selected value.
Decrease selected value.
Confirm and store changed value.

4 Configuration
4.1.4.3 Status/Monitoring Screens
4.1.4.3 Status/Monitoring Screens
Fig. 87: Status/Monitoring screen (example)
Status/Monitoring screens display monitored values or set parameters.
Status/Monitoring screen Notes
Generator Which values are shown in the display and whether they are correct
depends on the measurement type.
Busbar/System Which values are shown in the display and whether they are correct
Mains Which values are shown in the display and whether they are correct
Analog inputs/outputs The analog outputs are displayed as a percentage of the selected
hardware range, i.e. 50% of a 0 to 20 mA output refer to 10 mA or
alternatively as absolute values (depending on selected parameters).
Discrete inputs/outputs The configured logic for the discrete input "N.O./N.C." will determine
how the easYgen reacts to the state of the discrete input.
If the respective DI is configured to N.O., the unit reacts on the

energized state, if it is configured to N.C., it reacts on the de-energized
state.
Counters and service For additional information on setting/resetting counters refer to ╚═▷
“4.10 Configure Counters”.
Engine —
Engine (J1939) —
J1939 Analog values —
J1939 Status —
Actual date and time —
Version —
Load diagnostic —
Tab. 27: Status/Monitoring screens samples

4 Configuration
4.1.5 Specialized Menu Screens
4.1.5 Specialized Menu Screens
4.1.5.1 HOME Screen Voltage Display
Fig. 88: Monitoring screen 2nd page (example)
If a softkey appears with a wrench symbol it is possible to reset the peak hold
value(s).
The softkey »Display mode« on the main screen "HOME" changes the type of voltage
display.
The amount of information available from the system depends on how the measuring is
configured in the control unit.
The following tables illustrate what values are available depending on the configured
measurement type:
The displayed voltages ... Displayed at parameter setting
Press Symbol Type Measure 3Ph4W 3Ph3W 1Ph2W 1Ph3W
0× (6×) Delta L1-L2 Yes Yes Yes1 —
1× Delta L2-L3 Yes Yes — —
2× Delta L3-L1 Yes Yes — Yes
3× Wye L1-N Yes — Yes1 Yes
4× Wye L2-N Yes — — —
5× Wye L3-N Yes — — Yes
Tab. 28: Measuring point - generator

4 Configuration
4.1.5.2 Alarm List
1 Depends on setting of parameter ╚═▷ 1858.
The displayed voltages ... Displayed at parameter setting
Press Symbol Type Measure 3Ph4W 3Ph3W 1Ph2W 1Ph3W
0× (6×) Delta L1-L2 Yes Yes Yes1 —
1× Delta L2-L3 Yes Yes — —
2× Delta L3-L1 Yes Yes — Yes
3× Wye L1-N Yes — Yes1 Yes
4× Wye L2-N Yes — — —
5× Wye L3-N Yes — — Yes
Tab. 29: Measuring point - mains
1 Depends on setting of parameter ╚═▷ 1858.
4.1.5.2 Alarm List
Fig. 89: Alarm List screen
All alarm messages, which have not been acknowledged and cleared, are displayed. Each
alarm is displayed with the alarm message and the date and time of the alarm occurred
in the format yy-mon-dd hh:mm:ss.ss.
Self-acknowledging alarm messages get a new timestamp when initializing the unit
(switching on).

4 Configuration
4.1.5.3 Event History
Symbol/Softkey Description
Indicates that corresponding alarm condition (class A/B) is still present.
Indicates that corresponding alarm condition (class A/B) is no longer present.
Indicates that corresponding alarm condition (class C/D/E/F) is still present.
Indicates that corresponding alarm condition (class C/D/E/F) is no longer present.
Symbol with "!" indicates that an alarm of class A/B/C/D/E/F is present.
• Amber color = alarm class A/B

• Red color = alarm class C/D/E/F
Symbol without "!" indicates that an alarm of class A/B/C/D/E/F is not present.
Acknowledge the selected alarm message (displayed inverted).
Acknowledgment is only possible, if the alarm condition is no longer present. If the Alarm
LED is still flashing (an alarm is present, which has not yet been acknowledged as
'Seen'), this softkey resets the horn and acknowledges the alarm as 'Seen'.
4.1.5.3 Event History
Fig. 90: Event History screen
This screen displays system events. A date/time stamp is added to each entry!
+ Indicates when a condition was activated
- Indicates when a condition was de-activated

4 Configuration
4.1.5.4 Sequencing
4.1.5.4 Sequencing
Fig. 91: Sequencing screen
The sequencing screen shows all gensets participating in load sharing. The operation
mode of each genset as well as the state of its GCB is shown on this screen.
Symbol Description
AUTOMATIC Mode is active
MANUAL Mode is active
STOP Mode is active
TEST Mode is active
GCB of respective genset in sequence is closed.
GCB of respective genset in sequence is open.
Own easYgen device number
Sequence is running with respect to the settings e.g., the sequencing timing - see table below:
Generator is becoming "Add-on" to the (multiple) genset system.
Generator is going "Add-off" from the (multiple) genset system.
The remaining time is displayed on the upper right side on the grey bar "Sequencing ...",
see table below:
"..." text on the grey bar Description Parameter / ID
Sequencing Add-on delay ... s Shows the remaining time until the own Add-on delay:
generator is add-on
IOP ╚═▷ 5764
MOP ╚═▷ 5762
Sequencing Minimum run Shows the remaining time the own Minimum run time, ╚═▷ 5759
time ... s generator is running at minimum
Sequencing Add-off delay ...s Shows the remaining time until the own Add-off delay:
generator is add-off

4 Configuration
4.1.5.5 States easYgen
"..." text on the grey bar Description Parameter / ID

IOP ╚═▷ 5766
MOP ╚═▷ 5773
The bottom field displays the actual load sharing values. If this device is not participating
in load sharing, "LD start stop Off" is displayed here.
4.1.5.5 States easYgen
Fig. 92: States easYgen screen
The states of the easYgen devices are displayed. The operation mode of each genset as
well as the state of its GCB is shown on this screen.
AUTOMATIC Mode is active
MANUAL Mode is active
STOP Mode is active
TEST Mode is active
GCB of respective genset in sequence is closed.
GCB of respective genset in sequence is open.
Own easYgen device number
Other easYgen device numbers
Segment number

4 Configuration
4.1.5.6 Genset Parameter Alignment
4.1.5.6 Genset Parameter Alignment
Fig. 93: Genset parameter alignment screen
This screen displays easYgen devices configured differently than the LDSS setting of your
current device.
Symbol Description
The easYgen uses the same configuration as your current device.
The easYgen uses a different configuration than your current device.
4.1.5.7 Diagnostic devices
Fig. 94: Diagnostic screen example (HMI)
This screen displays the diagnostic status (the current communication state of the load
share and system bus) of the accepted easYgen devices. Refer to ╚═▷ “6.2.2.2 Diagnostic
Screens” for details.

4 Configuration
4.1.5.8 Setpoints generator
4.1.5.8 Setpoints generator
Fig. 95: Setpoints screen 1: P and PF/kvar
The setpoint is displayed on the left and the actual value is displayed on the right half of
the screen.
The source, which is used for setpoint 1 or setpoint 2, is displayed with the respective
AnalogManager function number.
The setpoints may only be adjusted if the respective controller is enabled. Frequency and
voltage may be adjusted within the configured operating limits.
Active power may be adjusted between 0 and the configured load control setpoint
maximum. The power factor may be adjusted between 0.71 leading and 0.71 lagging.
Fig. 96: Setpoints screen 2: V and f
Indicates the generator power (actual value).

4 Configuration
4.1.5.9 Setpoints PID1 - PID3
Indicates the mains power (actual value).
Raise the selected setpoint.
Lower the selected setpoint.
Manual mode and Auto mode do have separate setpoints. The Manual mode setpoints are
temporary and can be set via front panel softkeys only.
Setpoint for ... ... in AUTO mode ... in MANUAL mode ... in TEST mode
Load 5542 5529 5542
Reactive power 5646 5646
Power factor 5641 5623 5641
Voltage 5640 5605 5640
Frequency 5541 5509 5541
ToolKit's setpoint page "STATUS MENU | Setpoints" gives an overview.
Fig. 97: PID1(-3) screen 1
Menu path for configuration: [Parameter / Configuration / Configure application /

Configure controller / Miscellaneous / PID x control]
The PID screens enable direct access to PID control settings.

4 Configuration
Fig. 98: PID1(-3) screen 2
Fig. 99: PID1(-3) visualization screen
Menu path for visualization: [Next page / Setpoints / Setpoints PID 1-3]

4 Configuration
4.1.5.10 Synchroscope (Generator/Busbar And Busbar/Mains)
4.1.5.10 Synchroscope (Generator/Busbar And Busbar/Mains)
Fig. 100: Synchroscope screen (example)
The needle indicates the actual phase angle between busbar and generator or mains.
Please take care for compensation settings with parameters ╚═▷ 8825 »Phase angle
compensation GCB« and ╚═▷ 8824 »Phase angle GCB«.
If phase angle compensation ╚═▷ 8825 is active the compensated values are taken for
synchroscope display (and synchronization)!
WARNING!
Ensure correct synchronization configuration to avoid generator destructive power!
The 12 o'clock position on the top means 0° and the 6 o'clock position on the bottom
means 180°.
The actual phase angle is indicated on the bottom of the screen. The maximum positive
and negative phase angles are indicated 'green'. The length of the green part changes
according to the parameters.
The frequency and voltage differences are indicated on top of the bargraphs.
Operating mode MANUAL: Raise voltage/frequency.
Operating mode MANUAL: Lower voltage/frequency.

4 Configuration
4.1.5.11 LogicsManager Conditions
4.1.5.11 LogicsManager Conditions
Fig. 101: LogicsManager conditions screen
This screen displays the conditions of all LogicsManager command variables, which are
located in their respective groups.
Fig. 102: Command variables screen (example)
Symbol Description
Select the highlighted command variable group and display the state of the
command variables in this group.
Variable is TRUE.
Variable is FALSE.

4 Configuration
4.1.5.12 LogicsManager
4.1.5.12 LogicsManager
Fig. 103: LogicsManager screen
Some parameters of the easYgen are configured via the LogicsManager.
1. ▷ Configure a logical operation using various command variables, signs, logical operators,
and delay times to achieve the desired logical output.
Delay before output becomes TRUE.
Delay before output becomes FALSE.
State of the command variable is TRUE.
State of the command variable is FALSE.
Command variable selection field: Change the command variable group.
Time delay configuration field: Change the cursor position.
Help screen
Help screen (displays logical operators) can be found at [Parameter / Configuration /

Configure L/A Manager / General settings LM and AM / Help for ASA/IEC symbols]

4 Configuration
4.1.5.13 Mains Decoupling Threshold
4.1.5.13 Mains Decoupling Threshold
Fig. 104: Mains decoupling screen 1
Starts a special TEST mode which allows mains decoupling test independent
from breaker status (even if not mains parallel; GCB open, no rotation of prime
mover/generator).
Stops the TEST mode so mains decoupling is possible if system is mains parallel
only.
Notes:
TEST mode is deactivated not only by this button but too:
• ... if firing speed is reached
or
• ... automatically after 60 minutes
* Indicates parameters that are part of the mains decoupling configuration.

4 Configuration
4.1.5.14 Test Mains Decoupling (VDE AR-N 4105)
4.1.5.14 Test Mains Decoupling (VDE AR-N 4105)
Fig. 107: Test mains decoupling selection screen
VDE AR-N 4105 is asking for a test button.
Restricted Access
The function Mains Decoupling Test is available on Code level CL3. Code levels CL0 to
CL2 are intentionally not supported. Refer to ╚═▷ “4.3.4 Enter Password” for details.
Mains decoupling test is running after the warning is accepted.
The Mains decoupling test opens the selected breaker for mains decoupling (parameter
╚═▷ 3110).

4 Configuration
4.1.5.15 CAN Interface 1 State
Fig. 108: Security query mains decoupling test
CAUTION!
This function is independent from the breaker status and is active for 1 sec.
No thresholds are considered.
As long as the decoupling function is executed the »Execute« button and the warning text
are faded out.
Fig. 109: CAN interface state screen (example)

4 Configuration
Symbol Description
State is TRUE
State is false
Tab. 30: Graphic assignments
Section Description
Code level 00 Current code level of CAN1 connection
TPDO has incorrect mapping parameters State is TRUE/false
RPDO has incorrect mapping parameters /
TPDO has more than 8 bytes
RPDO has more than 8 bytes
TIME source double
Tab. 31: Bit assignments
Fig. 110: CAN interface 1 state screen (example)
Symbol State Description
State is TRUE PDO is missing
State is false PDO is NOT missing
Section Assignment
Missing Receive-PDO number: active {x} RPDO {x} is not received at the moment
Missing Receive-PDO number: latched {x} RPDO {x} has not been received
Notes
CAN 1 monitoring 3150 must be enabled

4 Configuration
Symbol Description
State is TRUE
State is false
Section Description
Code level 00 Current code level of CAN2 connection
(don’t care for the current applications)
TPDO has incorrect mapping parameters State is TRUE/FALSE
RPDO has incorrect mapping parameters / (The mapping is done automatically by the parameter ╚═▷ 15320
“Select external terminals”)
TPDO has more than 8 bytes
RPDO has more than 8 bytes
Text “4IKD_1.1_27347.seq” This example indicates the name of the current selected file for
the external terminals inclusive version.
If this line shows “---”, the file is missing on the device.
Notes
For the different selections of external terminals different files are

stored in the device.
Text “CANopen sequencer file error” 0000000 If the value indicated here is not equal “0000000” there is
something wrong with the file indicated above.
Tab. 34: (Bit) assignments
The next screen indicates missing Node-IDs of the external terminals.

4 Configuration
Symbol State Description
State is TRUE Node-ID is missing
State is false Node-ID is NOT missing
Section Assignment
Missing Node-ID number: active {x} Node {x} is not received at the moment
Missing Node-ID number: latched {x} Node {x} has not been received
Notes
CAN 2 monitoring 3150 must be enabled
J1939 state
Fig. 113: CAN interface 2 j1939 state screen (example)

4 Configuration
4.1.5.17 Ethernet Network
Section Description
Text "J1939 state" Screen title / Interface type
Text “J1939 sequencer file error” 0000000 If the value indicated here is not equal “0000000” there is
something wrong with the file indicated below.
Text “Standard_1.1_27347.ecu” This example indicates the name of the current selected file for
ECU inclusive version.
If this line shows “---”, the file is missing.
Notes
For the different selections of "Device type" different files are

stored in the device.
Tab. 36: Assignments
Fig. 114: Ethernet A state screen (example)
Current Ethernet state is displayed. Setting can be found under [Next Page / Diagnostic /
Interfaces / Ethernet].
In this menu select:
• »Ethernet A«
• »SNTP«
• »Servlink«
• »Modbus TCP/IP«
See chapter ╚═▷ “7.2 Ethernet Interfaces” for configuration.

4 Configuration
Fig. 115: Ethernet SNTP (example)
Fig. 116: Ethernet Servlink (example)

4 Configuration
4.1.5.18 USB
Fig. 117: HMI-XT_Interfaces_Ethernet-Modbus-TCP-IP_NEW
4.1.5.18 USB
Fig. 118: USB interface
Current USB state is displayed. Setting can be found under [Next Page / Diagnostic /
Interfaces / USB].
See chapter ╚═▷ Chapter 4.7.1 for configuration.

4 Configuration
4.1.5.19 RS-485
4.1.5.19 RS-485
Fig. 119: RS-485 interface
Current RS-485 interface state is displayed. Setting can be found under [Next Page /
Diagnostic / Interfaces / RS485].
See chapter ╚═▷ “4.7.2 RS-485 Interface” for configuration.
4.1.5.20 J1939 Special
Fig. 120: J1939 Special screen (example)
The status of the configured J1939 ECU error messages is displayed here if the unit is
configured accordingly. Some ECUs have a special screen for proprietary features. ╚═▷
Chapter 4.1.5.20 shows the special screen for Scania S6.

4 Configuration
4.1.5.21 J1939 Status miscellaneous
The following softkeys are only visible if parameter ╚═▷ 15127 is configured to "ON".
Request a blink code for one error message from the ECU.
Repeated pressing of this softkey displays all stored error messages.
This symbol/softkey is only visible if the ECU is configured to "Scania S6".
Scania S6: Reset the blink code. To do this, disable the ignition (terminal U15),
press this softkey, and enable the ignition again within 2 seconds.
Other ECU: Reset ECU failure codes.
Fig. 121: J1939 Status miscellaneous screen 1
SPN Description
1081: Eng. wait to start Engine Wait to Start Lamp: Lamp signal which indicates that the engine is too
lamp cold to start and the operator should wait until the signal becomes inactive
(turns off).
Values:
• Off
• On
• Missing
3697: DPF Lamp Diesel Particulate Filter Lamp Command: Command to control the diesel
particulate filter lamp.
Values:
• Off
• On solid
• On fast blink
• Missing
3698: Exh. Gas Command to control the exhaust system high temperature lamp: This lamp
temp.lamp indicates that the exhaust system temperature is high.

4 Configuration
SPN Description
Values:
• Off
• On solid
• Missing
3699: DPF Passive Diesel Particulate Filter Passive Regeneration Status: Indicates the state of diesel
regen. state particulate filter passive regeneration.
Values:
• Not active
• Active
• Missing
3700: DPF Active regen. Diesel Particulate Filter Active Regeneration Status: Indicates the state of diesel
status particulate filter active regeneration.
Values:
• Not active
• Active
• Missing
3701: DPF Regeneration Diesel Particulate Filter Status: Indicates the state of the diesel particulate filter
needed regeneration need and urgency.
Values:
• No (not needed)
• Lowest level
• Moderate level
• Highest level
• Missing
3702: DPF Diesel Particulate Filter Active Regeneration Inhibited Status: Indicates the state
Act.regen.inhibit of diesel particulate filter active regeneration inhibition.
Values:
• Not inhibited
• Inhibited
• Missing

4 Configuration
4.1.5.22 Time Indication According To Operating Condition
4.1.5.22 Time Indication According To Operating Condition
Fig. 122: Time indication according to operating condition
This screen element (on main screen) displays time indications according to the operating
condition of the easYgen device. The time indications of the events indicated in the table
below are shown in the display. The counter starts with the setting value of the related
event and counts down to zero. After that, the status change of another event is shown.
The sequence of the events is related on the configuration of the device.
Event Description
Auxiliary services prerun Refer to parameter ╚═▷ 3300 for details.
Crank protect Refer to parameter ╚═▷ 3326 for details (only half of the configured time is
used).
Preglow time Refer to parameter ╚═▷ 3308 for details.
Starter time Refer to parameter ╚═▷ 3306 for details.
Start pause time Refer to parameter ╚═▷ 3307 for details.
Ignition delay Refer to parameter ╚═▷ 3310 for details.
Gas valve delay Refer to parameter ╚═▷ 3311 for details.
Engine monitoring delay Refer to parameter ╚═▷ 3315 for details.

time
Generator stable time Refer to parameter ╚═▷ 3415 for details.
Cool down time Refer to parameter ╚═▷ 3316 for details.
Stop time of engine Refer to parameter ╚═▷ 3326 for details.
Auxiliary services Refer to parameter ╚═▷ 3301 for details.

postrun

4 Configuration
4.2 Access Via PC (ToolKit)
4.2 Access Via PC (ToolKit)

Version
Woodward’s ToolKit software is required to access the unit via PC
• Required version: 6.1.2 or higher

• Please use the latest available version!
• To obtain the latest version scan this QR code or use the following link: ══▷ https://
wss.woodward.com/manuals/PGC/SW_Tools/ToolKit.
NOTICE!
EXISTING wset Settings Files
wset file properties changed. easYgen-XT wset files are different from wset files of
easYgen Series.
• wset Settings files created with easYgen must be converted before use with
easYgen-XT!
• NEW ... .wset files are NOT BACKWARD COMPATIBLE!
• Please ask your Woodward sales support contact for conversion/update instruction
to use files created with easYgen.
4.3 Basic Setup

The "Basic Setup" describes a collection of configuration sub-menus:
• Configure language/clock
• Configure system management
• Password
• Configure HMI
◦ Configure customer screen 1
◦ Configure customer screen 2
◦ Configure display
◦ Screen configuration

4 Configuration
4.3.1 Configure Language/Clock
(Other configuration is "below" the sub-menu »Configuration«. See following chapters.
General notes
The following parameters are used to set the unit language, the current date and time,
and the daylight saving time feature.
If an Asian language is configured, some parameter screens may be displayed with an

empty space at the bottom of the parameter list, which may be interpreted as an end of
the list, although more parameters exist and are displayed when scrolling down.
This can easily be checked:
• The list display is a closed loop, so ...

• scrolling UP from first list entry goes to the end of the list and vice versa.
If a custom language is configured, the enumeration text in Toolkit displays "Reserve 1".
In the easYgen HMI, the enumeration text is the name of the current custom language.
If the language is set to "Reserve1" without a loaded custom language, the language of
the HMI will be set to English.
Update Clock
HMI/display and ToolKit differ in updating the clock settings
• HMI/displays the actual value and enables direct change of each parameter
• ToolKit displays the »Actual values« (ID 1690 to 1695) beside and the time values
and date values can be prepared each as a set before transfer
ID Parameter CL Setting range Description
[Default]
1700 Language 0 selectable languages The desired language for the unit
display text is configured here.
(Set language) [English]
Available languages are: English,
German, Dutch, Spanish, French,
Italian, Portugese, Japanese,
Chinese, Russian, Turkish, Polish,
Slovakian, Finnish, Swedish,
Reserve 1.
»Values to be set«
1710 Hour 0 hour 0 to 23 h

The hour of the clock time is set
[real-time clock] here.
Example
• 0 = 0th hour of the day

(midnight).

4 Configuration
[Default]
• 23 = 23rd hour of the day

(11 pm).
1709 Minute 0 0 to 59 min The minute of the clock time is set

here.
[real-time clock]
Example
• 0 = 0th minute of the hour

• 59 = 59th minute of the hour
1708 Second 0 0 to 59 s The second of the clock time is set

here.
[real-time clock]
Example
• 0 = 0th second of the minute

• 59 = 59th second of the
minute
1698 Transfer time to clock 2 Yes Yes transfers the time values to
the clock.
[No]
Notes
ALL values are transferred and

overwritten - even if you want to
change only one.
1711 Day 0 day 1 to 31 The day of the date is set here.
[real-time clock] Example
• 1 = 1st day of the month.

1712 Month 0 month 1 to 12 The month of the date is set here.
• 1 = 1st month of the year.

• 12 = 12th month of the year.
1713 Year 0 year 0 to 99 The year of the date is set here.
• 0 = Year 2000
• 99 = Year 2099
1699 Transfer data to clock 2 Yes Yes transfers the date values to
the clock.
[No]
Notes
ALL values are transferred and

overwritten - even if you want to
change only one.
4589 Time zone 2 -12 to 14 Time shift in hours between the

time zone in which the device is
[0.00] used compared to the absolutely
Greenwich Mean Time (GMT).
This information is needed to

transfer the general time signal

4 Configuration
[Default]
into the local real-time clock

setting.
»Daylight saving time«
4591 Daylight saving time 2 On On enables the Daylight saving

time.
[Off]
The daylight saving time feature
enables to automatically adjust
the real-time clock to local
daylight saving time (DST)
provisions. If daylight saving time
is enabled, the real-time clock will
automatically be advanced by one
hour when the configured DST
begin date and time is reached
and falls back again by one hour
when the configured DST end date
and time is reached.
If the unit is used in the southern

hemisphere, the DST function will
be inverted automatically, if the
DST begin month is later in the
year than the DST end month.
Notes
Do not change the time manually

during the hour of the automatic
time change if DST is enabled to
avoid a wrong time setting.
Events or alarms, which occur

during this hour might have a
wrong time stamp.
4594 DST begin time 2 0 to 23

The real-time clock will be
[0] advanced by one hour when this
time is reached on the DST begin
date.
Example

(midnight)
(11 pm)
Notes
This parameter is only displayed,

if Daylight saving time
(parameter ╚═▷ 4591) is set to
"On".
4598 DST begin weekday 2 Sunday to Saturday The weekday for the DST begin
date is configured here
[Sunday]
Notes

"On".

4 Configuration
[Default]
4592 DST begin nth. 2 The order number of the weekday

weekday for the DST begin date is
configured here.
[1st] DST starts on the 1st configured

weekday of the DST begin month.
2nd DST starts on the 2nd configured

3rd DST starts on the 3rd configured

4th DST starts on the 4th configured

Last DST starts on the last configured

LastButOne DST starts on the last but one

configured weekday of the DST
begin month.
LastButTwo DST starts on the last but two

begin month.
LastButThree DST starts on the last but three

begin month.
Notes

"On".
4593 DST begin month 2 1 to 12 The month for the DST begin date
is configured here.
[1]
Example
• 1 = 1st month of the year

• 12 = 12th month of the year
Notes

"On".
4597 DST end time 2 0 to 23 The real-time clock will fall back
by one hour when this time is
[0] reached on the DST end date
Example

(midnight).
(11 pm).
Notes


4 Configuration
[Default]

"On".
4599 DST end weekday 2 Sunday to Saturday The weekday for the DST end date
is configured here
[Sunday]
Notes

"On".
4595 DST end nth. 2 The order number of the weekday

weekday for the DST begin date is
configured here.
[1st] DST ends on the 1st configured

2nd DST ends on the 2nd configured

3rd DST ends on the 3rd configured

4th DST ends on the 4th configured

Last DST ends on the last configured

LastButOne DST ends on the last but one

begin month.
LastButTwo DST ends on the last but two

begin month.
LastButThree DST ends on the last but three

begin month.
Notes

"On".
4596 DST end month 2 1 to 12 The month for the DST begin date
is configured here.
[1]
Example
• 1 = 1st month of the year

• 12 = 12th month of the year
Notes

"On".
Tab. 37: Parameters Language/Clock Configuration

4 Configuration
Example
If daylight saving time starts at 2:00 am on the 2nd Sunday in March and ends at 2:00 am
on the 1st Sunday in November, the unit has to be configured like shown in ╚═▷ Tab. 38
to enable an automatic change to daylight saving time and back to standard time.
ID Parameter Setting
4591 Daylight saving time On
4594 DST begin time 2
4598 DST begin weekday Sunday
4592 DST begin nth weekday 2nd
4593 DST begin month 3
4597 DST end time 2
4599 DST end weekday Sunday
4595 DST end Sunday 1st
4596 DST end month 11
Tab. 38: Daylight saving time - configuration example
USA, Canada European Union
Year DST Begins 2 a.m. DST Ends 2 a.m. DST Begins 1 a.m. DST Ends 1 a.m.
(Second Sunday in (First Sunday in UTC=GMT (Last UTC=GMT (Last
March) November) Sunday in March) Sunday in October)
2008 March 9, 2008 November 2, 2008 March 30, 2008 October 26, 2008
Tab. 39: Daylight saving time - exemplary dates
Localization Tool (for customized language
☼ Create a customized localization of an easYgen 3000XT HMI
The LocalizationTool is a tool which allows the user to create a localization of an

easYgen3000XT HMI in a selected language and create from this a package which can
be updated to the device. Creating localized text is done using Excel which has to be
installed on the PC. The tool will create a basic Excel sheet. The user will translate in
Excel and then from the edited Excel sheet will create a resource file which can be
uploaded on the easYgen using the Woodward Toolkit tool.
Additionally the tool provides a simulation of the easYgen’s HMI to check the translation.
It also provides a way to re-use previously translated texts.
The Localization tool software is delivered as an “LocalizationToolInstaller.msi” file with
the product CD-ROM and needs to be installed before use at your PC/laptop. After
starting the program, the HELP file can guide through the required settings.

4 Configuration
4.3.2 Configure HMI
4.3.2 Configure HMI
4.3.2.1 Configure Customer Screens
easYgen-3000XT comes with two fully customizable screens - just one click (one
level) from home screen. Softbutton text and displayed name, values, and units can be
defined/selected. The new full-featured AnalogManager 1:1 parameter monitoring but
even math. function computing.
There are two configurable customer screens available.
Handling/set-up is similar so described one time only.
The (configurable) names of the customer screens are displayed at home page as
softbutton text. Pressing one of this softbuttons opens the screen with the configured
Names, Values, and Units.
Customer Screen Configuration
Numbering convention
Customer Screen X.Y: Screen #X (1 or 2); Row #Y (1 to 9)
[Default]
AM Customer screen 1.1
7691 Description 2 23 characters Name displayed in row 1
[Cust. Screen row 1] Notes
The max. number of characters is

higher but will not be displayed
correctly on HMI/display.
The row is hidden if description is

empty (no character, not even a
blank)!
7692 Unit 2 6 characters Unit displayed in row 1
[Unit] Notes

higher but will not be displayed
correctly on HMI/display.
Notes
If »°C« or »bar« is assigned the

unit will be converted into "°F" or
"psi" automatically if the
corresponding parameter for
conversion ╚═▷ 3630 and/or ╚═▷
3631 is configured to YES.
7690 AM Customer screen 2 Determined by AnalogManager For details see ╚═▷ Fig. 199.
1.1 90.01

4 Configuration
4.3.2.1 Configure Customer Screens
[Default]
[Pass Through, ...]
7934 Decimal points 2 0 to 2 Number of decimal points for the

value in row 1–9 of the
customizeable screen 1.
Tab. 40: Parameters Customer Screen 1.1 Configuration (sample)
AM Customer ID "Description" ID "Unit" ID "Decimal points" AnalogManager

screen #
1.1 7691 7692 7932 7690
1.2 7696 7697 7933 7695
1.3 7701 7702 7934 7700
1.4 7706 7707 7935 7705
1.5 7711 7712 7936 7710
1.6 7716 7717 7937 7715
1.7 7721 7722 7938 7720
1.8 7726 7727 7939 7725
1.9 7731 7732 7940 7730
2.1 7736 7737 7941 7735
2.2 7741 7742 7942 7740
2.3 7746 7747 7943 7745
2.4 7751 7752 7944 7750
2.5 7756 7757 7945 7755
2.6 7761 7762 7946 7760
2.7 7766 7767 7947 7765
2.8 7771 7772 7948 7770
2.9 7776 7777 7949 7775
Tab. 41: Overview Customer Screens/Rows IDs

4 Configuration
4.3.2.2 Configure Display
☼ Customer Screen Configuration
Fig. 123: Customer Screen sample: a set of interesting Engine values
Setting range
ID Parameter CL Description
[Default]
7701 Description 2 Oil Temperature (Defined by customer)
7702 Unit 2 °C (Defined by customer)
7700 AM Customer 2 Determined by (Defined by customer)

screen 1.3 AnalogManager 90.03: »Pass
Through« of »A1= 07.23
175:Oil Temperature 1«
7934 Decimal points 2 2 (Defined by customer)
Tab. 42: Parameters Customer Screen 1.3 Configuration sample
4.3.2.2 Configure Display
Display Configuration
[Default]
Display brightness 2 0 to 100% Color bar visualization for

immediately displayed selection
[35]%
7796 2nd display 2 1 to 100 Level of 2nd brightness.

brightness
[5]% Used if LM ╚═▷ 7794 is true.
4557 Key activation time 2 1 to 999 min If no soft key has been pressed for
the time configured here, the 2nd
[120 min] display brightness will be used.
Notes

4 Configuration
4.3.2.3 Screen configuration
[Default]
This parameter is only effective, if

LogicsManager 86.33 2nd disp.
bright. ╚═▷ 7794 is configured to
"04.64 Key activation".
7794 Enable 2nd display 2 Determined by LogicsManager Once the conditions of the
brightness 86.33 LogicsManager have been fulfilled,
the brightness level of the display
[(04.64 NOT& 1) & 1] switches to the 2nd brightness
level defined by parameter ╚═▷
= 11971 7796.
This can save energy and support

visualization of device/system
state.
For information on the

LogicsManager and its default
settings see ╚═▷ “4.8 Configure
LogicsManager”╚═▷ “9.3.1
LogicsManager Overview”.
7799 Enable front (panel) 2 Determined by LogicsManager If this parameter is TRUE and
heater 86.34 ambient temperature goes below
-10° C, the display (front panel)
[(1 & 1) & 1] will be heated for seven minutes
(and wait further 3minutes).
= 11972
Notes
This parameter is always visible in

HMI and ToolKit, even it is
implemented in "-LT" variants for
enhanced temperature use only.
12978 Lock keypad 2 Determined by LogicsManager Key pad can be locked remotely.
86.30
This parameter is intentionally not
[(0 & 1) & 1] available via HMI/display.
= 11924
Tab. 43: Parameters Display Configuration
Screen Configuration
[Default]

4 Configuration
4103 Home screen data 2

: Home screen can display
several pre-defined data
collections.
Generator Generator relevant information

are displayed.
[Generator/Mains] Home screen is splitted and

displays generator and mains
related information.
Generator/Busbar Home screen is splitted and

displays generator and busbar
Generator/Engine Home screen is splitted and

displays generator and engine
4129 Oneline diagram with 2 Off

: Display of oneline (single
mains
[On] line) diagram on home screen can
be reduced NOT to show mains
symbols.
Notes
Softbutton for MCB is (visible and)

valid only if this parameter is
TRUE.
General notes
The home screen data configuration "Generator/Engine" offers an engine value indication.
With the following AnalogManagers the according sources can be configured and scaled.
The according AnalogManager has to be configured as 'Pass Through'.
[Default]
8891 AM Engine speed 2 Determined by AnalogManager With this AnalogManager the

81.24 according speed source may be
selected from the available data
[A1 = 11.51 Engine speed sources.
[rpm]]
Even it is possible to select all
data sources╚═▷ “9.4.2 Data
Sources AM”), only the following
data source may be used:
11.51 Engine speed [rpm]
The indication is displayed in the

format 0000 rpm.
8892 Show engine speed 2 [Yes] Display of engine speed on home

screen.
No

4 Configuration
8893 AM Engine oil 2 Determined by AnalogManager With this AnalogManager the

pressure 81.25 according oil pressure source can
be configured and scaled. The
[A1 = 07.07 100:Engine Oil indication is displayed in the
Press.] (This default value is a format 00.0bar (000psi).
J1939 value.)
Notes
If »bar« is assigned the unit will be

converted into "psi" automatically
if the corresponding parameter for
conversion ╚═▷ 3630 is configured
to YES.
8894 Show oil pressure 2 Yes Display of engine oil pressure on

home screen.
[No]
8895 AM Engine hours 2 Determined by AnalogManager With this AnalogManager the

81.26 according operating hours source
can be configured and scaled. The
[A1 = 11.55 Eng.oper.hours indication is displayed in the
[h]] format 00000.00h .
8896 Show engine hours 2 [Yes] Display of engine running hours

on home screen.
No
8897 AM Engine fuel level 2 Determined by AnalogManager With this AnalogManager the
81.27 according fuel level source can be
configured and scaled. The
[A1 = 06.03 Analog input 3] indication is displayed in the
format 000.0% .
8898 Show engine fuel 2 Yes Display of engine fuel level on

level home screen.
[No]
8899 AM Engine 2 Determined by AnalogManager With this AnalogManager the

batt.voltage 81.28 according battery voltage source
can be configured and scaled. The
[A1 = 10.54 Battery voltage indication is displayed in the
[V]] format 00.0V .
8900 Show engine battery 2 [Yes] Display of engine battery voltage

voltage on home screen.
No
8901 AM Engine coolant 2 Determined by AnalogManager With this AnalogManager the

temp. 81.29 according coolant temperature
source can be configured and
[A1 = 07.15 110:Eng.Coolant scaled. The indication is displayed
Temp.] (This default value is a in the format 000°C (°F).
J1939 value.)
Notes
If »°C« is assigned the unit will be

converted into "°F" automatically
if the corresponding parameter for

4 Configuration
4.3.3 Lamp Test
conversion ╚═▷ 3631 is configured

to YES.
8902 Show engine coolant 2 [Yes] Display of engine coolant

temp. temperature on home screen.
No
4.3.3 Lamp Test
All lights on the controller may be tested for correct operation with this function.
[Parameter / Lamp test]
Lamp test is available via HMI/display, ToolKit, and parameter 10773 with logical
command variable 04.61.
4.3.4 Enter Password
General notes
The controller utilizes a password protected multi-level access hierarchy to prevent

unauthorized access to parameters, configuration and calibration items. This permits
varying degrees of access to the parameters being granted by assigning unique
passwords to designated personnel.
Password protection covers direct and remote access through all methods and interfaces
of interconnectivity of the device.
Personal security
Configure password security before handing over the device to the customer!
Note your password on a secure location. The next higher password level (2 and 4)
allows to reset the password of the level below (1 and 3).
To restore the according User Name Account needs support from Woodward (authorized
partner).
Access via channel ...
The following table and drawing provide an overview about the possible access channels
to the easYgen-XT.
Access to the easYgen-XT by a/an ... # used in drawing ╚═▷

“Access via
channel ...”below
HMI on the control directly ①
PC running ToolKit servlink, connected over USB ②

4 Configuration
Access to the easYgen-XT by a/an ... # used in drawing ╚═▷

“Access via
channel ...”below
Remote Panel with the Woodward screen share concept connected over Ethernet (HMI ③=①
simulation)
3rd party Remote Panel (i.e. Proface, Sütron, ...) running Modbus TCP ④
PLC running Modbus TCP ④
PC running ToolKit servlink, connected over Ethernet ⑤
Netbiter® Easy Connect gateway running Servlink TCP (ToolKit via internet) ⑤
PLC running Modbus RTU via RS-485 ⑥
PLC running CANopen ⑦
PLC running CANopen via Profibus DP ⑦
Each channel has its own independent access level.
The according password handling for each of this access is defined afterwards.

4 Configuration
Fig. 124: Access to the easYgen-XT device - Overview
Two login procedures cover all access channel variants: The ...
• Basic Code Entry
• User Account Entry
Hidden entry for more security
The currently selected entry number is visible only - all other numbers are hidden and a
"*" asterisk is displayed instead.
LOGIN procedure "Basic Code Entry"
The Basic Code Entry is valid for access ①, ③, ⑥, and ⑦.

4 Configuration
Fig. 125: Password entry: HMI
The Basic Code Entry asks for four numbers to open the related password level. It starts
with the default value of parameter ╚═▷ 10416 »Random number for password«.
LOGIN procedure "User Account Entry"
The User Account Entry is valid for access ②, ④, and ⑤.
Fig. 126: Password entry: HMI
The User Account Entry comes with more security as requested for internet access. It
asks for »Username:« and »Password:« ("Alphanumeric Password"). To open the related
password level, both rows entries need the correct alphanumeric strings.
The already existing User names cannot be changed. They are fixed for the desired code
level, which shall be entered.
Check you Password entry
View hidden password entry by pushing the symbol on the right side of
the »Password:« box.

4 Configuration
Enter Password for level ... (Overview)
A distinction is made between the access levels as follows:
Code User Account Entry Basic Code Entry Comment

Level
User Password Password
Name
(default) (default)
(fix)
5 CL05 CL0500 500 The Super Commissioning Level
Access to nearly all parameters and

configurations, except calibration and super
user items.
The firmware updating is released.
The own code level and the levels below can

be indicated and configured.
4 AC04 Algorithm Code Algorithm Code The temporary Super Commissioning

Level
The same access rights like in the Super

Commissioning Level but with the following
exceptions:
• The password for this level is not visible.

• The access is dismissed afterwards.
3 CL03 CL0003 3 The Commissioning Level
Access to well defined parameters and

configurations, which are usually needed on a
commissioning level.
The own code level and the levels below can

be indicated and configured.
2 AC02 Algorithm Code Algorithm Code The temporary Commissioning Level
The same access rights like in the Commission

Level.
The Code level is entered in an algorithm code.

The access is dismissed afterwards.
Only the code levels below can be indicated

and configured.
1 CL01 CL0001 1 The Basic Level
Access to a limited number of parameters and

configurations.
The own code level can be indicated and

configured.
0 No access rights to change, even viewed

information is restricted.

4 Configuration
Active Code Level
A code level always belongs to an access channel. Each access channel has its own
password level. This password level can be different to others (other channels) at the
same time.
The access related code level is available and visible beside the access related interface
settings.
No direct access as expected?
Please check: LogicsManager 86.30 Parameter ╚═▷ 12978 "Lock keypad 1" = TRUE?
The Algorithm Code
The "Algorithm Code" is an implemented procedure to give an external user temporarily

access to the device but without being able to see or change the according passwords.
This temporary access needs a random number produced by the device. The actual
password then is calculated from this random number using a secret formula. The secret
formula is provided by a higher instance.
Access Channels
Maximum Security
Each of these channels have their own independent access level. That has the advantage
that e.g. a HMI channel password level opens not automatically the access rights for the
other channels.
Maximum Flexibility
The device offers the capability to disable the password protection for the individual
interface communication channels RS485, Ethernet and CAN 1. If the password level is
disabled the access level is set on code level 5.
The device provides different access channels Remarks

via ...
HMI directly or by WW Remote Panel screen share concept
USB ToolKit Servlink
RS485 Modbus RTU
Ethernet Modbus TCP
ToolKit Servlink TCP, 8 sub channels are possible
Note: Each of the 8 sub channels has its own

independent password access level!
CAN1 CANopen
CAN2

4 Configuration
The different Password Code Levels
This chapter defines the properties of the single password code levels. The device
differentiates several password levels. Generally with a higher reached password level the
access rights increases.
Code Level 0
The Level 0 means there are no access rights enabled. All configurations are blocked.
Code Level 1 - The Basic Level CL01
• General:
This level releases the access to a limited number of parameters and configurations
• Basic Code entry:
In this and higher levels the password for the Basic Code Level CL01 can be changed
• User Account Entry:
This level is selected with the User Name CL01 and the according password can only
be changed being in code level CL01.
Being in code level AC02 or higher the password of the Basic Level CL01 can be
reset to its default by the Yes/No parameter ╚═▷ 10434.
Code Level User Account Entry Basic Code Entry
User Name Password Password
(fix) (default) (default)
1 CL01 CL0001 0001
Code Level 2 - The temporary Commissioning Level AC02
• General:
This Level allows temporary access to parameters of the Commission Level.
The access is dismissed automatically (see ╚═▷ “Automatic Logout from Password
level (Fall into level 0)”).
• Basic Code Entry:
In this and higher Levels, the password for the Basic Code Level CL01 can be
changed.
This level is selected with the User Name AC02 and the according algorithm for the
password can only be changed being in the Commissioning code level CL03.
Being in code level AC02 or higher the password of the Basic Level CL01 can be
reset to its default by the Yes/No parameter ╚═▷ 10434.

4 Configuration
Code Level User Account Entry Basic Code Entry
(fix)
2 AC02 The entry procedure: The entry procedure:
The operator connects ToolKit with the The operator navigates on the
device and closes the upcoming easYgen-XT HMI or on RP-3000XT to
security login window without the screen[Parameter / Password /
entering username and password Password display].
(Code level 0). The operator navigates
with ToolKit to the page [Parameter / The operator reads the indicated
Configure system management]. random number. He tells it to a higher
instance.
The operator reads on that page ╚═▷
10416 »Random number for The higher instance calculates:
password«. He tells it to a higher (10414 »Code temp.
instance. commissioning« + 10416 »Random
Number«) x 3.
The higher instance calculates:
(10414 »Code temp. The higher instance takes the lower
commissioning« + 10416 »Random four digits of the result and tells it the
Number«) x 3. operator. The operator enters the
result as password into the control.
The higher instance takes the lower
four digits of the result and puts the
according algorithm string
10437 »Alphanumeric code temp.
comm.« as prefix in front.
The higher instance tells the result to

the operator, who enters the result as
password into the control.
Code Level 3 - The Commissioning Level CL03
• General:
In this Level, the operator has access to all parameters and configurations, which are
usually needed on a commissioning level
In this and higher levels the password for the Commissioning Level CL03 can be
changed
This level is selected with the User name CL03 and the according password can only
be changed being in the Commissioning Level CL03
Being in code level AC04 or higher the password of the Commissioning Level CL03
can be reset to its default by the Yes/No parameter ID ╚═▷ 10435
Level User Account Entry Basic Code Entry
3 CL03 CL0003 0003

4 Configuration
Code Level 4 - The temporary Super Commissioning Level
• General:
This Level allows temporary access to nearly all parameters and configurations,
except calibration and super user items.
The access is dismissed automatically
In this and higher levels the passwords for the Commissioning Level CL04 can be
changed
This level is selected with the User name AC03 and the according algorithm for the
password can only be changed being in the Super Commissioning Level CL05
Being in code level AC04 or higher the password of the Commissioning Level CL03
4 AC04 The entry procedure: The entry procedure:
The operator connects The operator navigates on

ToolKit with the device and the easYgen-XT HMI or on
closes the upcoming RP-3000XT to the
security login window screen[Parameter /
without entering Password / Password
username and password display].
(Code level 0). The operator
navigates with ToolKit to the The operator reads the
page [Parameter / Configure indicated random number.
system management]. He tells it to a higher
instance.
The operator reads on that
page ╚═▷ 10416 »Random The higher instance
number for password«. He calculates: (10412 »Code
tells it to a higher instance. temp. commissioning« +
10416 »Random Number«)
The higher instance x 5.
calculates: (10412 »Code
temp. commissioning« + The higher instance takes
10416 »Random Number«) the lower four digits of the
x 5. result and tells it the
operator. The operator
The higher instance takes enters the result as
the lower four digits of the password into the control.
result and puts the
according algorithm string
10438 »Alphanumeric code
super temp. comm.« as
prefix in front.
The higher instance tells the

result to the operator, who
enters the result as
password into the control.
Code Level 5 - The Super Commissioning Level CL05
• General:

4 Configuration
In this Level, the operator has access to nearly all parameters and configurations,
except calibration items
The firmware updating is released
In this and higher Levels the password fro the Super Commissioning Level CL05 can
be changed
This level is selected with the User name CL05 and the according password can only
be changed being in the Super Commissioning Level CL05
Being in a higher level as CL05 the password of the Super Commissioning Level CL05
If you have forgotten your password for the Super Commissioning Level, please contact
Woodward or a representative for help.
5 CL05 CL0500 0500
Automatic Logout from Password level (Fall into level 0)
All basic code entry channels deny after 2h
The Modbus TCP access channel denies after 2h
Generally with power supply cycling the password level is denied.
The ToolKit Servlink access never logout
What forces the Logout from Password levels (Fall into level 0)
All basic code entry channels with »0« as password or a wrong password
The ToolKit Servlink access with logout function
The Modbus TCP (in all channels) with wrong password
Definition of the password
Numeric Password of the Basic Code entry
• The range of possible passwords is 1 to 9999
Alpha numeric Password of the User Account entry
• The maximum length of the alpha numeric password is 20 characters

4 Configuration
• The maximum length of the alpha numeric prefix (ID ╚═▷ 10437; ╚═▷ 10438) is 6
characters
The Random Number
Each time a password is entered, the random number is calculated at new. This
guarantees max. security.
Password handling on the HMI of the easYgen
The easYgen supports only the Basic Code entry.
The easYgen HMI password level shall be visible in the parameter menu screens.
A dynamic key symbol is visible and displays the currently entered code level number
inside:
• code level = 00: locked
• code level > 00: unlocked
In case of a password level time out during configuration over HMI, the HMI display
switches back to the main screen.
Password handling in ToolKit
The ToolKit supports the User Account entry and in case of CANopen connection the Basic
Code entry.
Ethernet Connection: The ToolKit password level is visible in the menu [STATUS MENU /
Diagnostic / Interfaces / Ethernet / Servlink]. Refer to your IP-address (PC).
USB Connection: The ToolKit password level is visible in the menu [STATUS MENU /
Diagnostic / Interfaces / USB].
CAN Connection: The ToolKit password level is visible in the menu [STATUS MENU /
Diagnostic / Interfaces / CAN / CANx].
Password handling via Modbus TCP using Ethernet connection
The easYgen must be a member of an Ethernet network and both user name and
password have to be transferred (from PLC) to the device.

4 Configuration
☼ Set easYgen-XT to code level CL05 via Modbus TCP
With factory settings username is expected to be "CL05" and password to be "CL0500"

for code level CL05. With setting the Code Level all five communication channels
(sockets) are released.
1. ▷ Write and transfer »CL05« as hex:

43-4C-30-35-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
for "User name" to parameter ╚═▷ 7490 (40 bytes).
2. ▷ Write and transfer »CL0500« as hex:
43-4C-30-35-30-30-00-00-00-00-00-00-00-00-00-00-00-00-00-00-
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
for "Password" to parameter 7491 (40 bytes).
▶ Code level can be read with parameter 10427
The password level is visible in the Ethernet interface diagnostic screen.
Password handling via Modbus using RS-485 connection
The easYgen must be a member of a RS-485 network and the password has to be
transferred (from PLC) to the device.
☼ Set easYgen-XT to code level 5 via Modbus RS-485
With factory settings the password is expected to be "500" for code level 5.
• Modbus address = 400000 + (Par. ID + 1) = 410431

• Modbus length = 1 (UNSIGNED 16)
Code level state can be read with parameter 10420.

Please find the password level in ToolKit: [STATUS MENU / Diagnostic/Interfaces / RS485].
Password handling via CAN using CANopen connection
The easYgen must be a member of a CANopen network and the password has to be
transferred (from PLC) to the device.
The easYgen provides several CAN ports and therefore each port has his own password
level. The password is written by a SDO Communication Channel.
☼ Set easYgen-XT to code level 5 via CANopen
With factory settings the password is expected to be "500" for code level 5.

4 Configuration
☼ Procedure for CAN 1
• CAN interface 1 Parameter ID = 10402 (dec) = 28A2 (hex)

• Incorporate the 2000 (hex) value: 28A2(hex) + 2000 (hex) = 48A2 (hex)
• Identifier: 600 (hex) + Node-ID
• Example Node-ID is 1
The following table shows exemplary send data for the device on the CANopen bus.
Identifier Description Data (hex)
601 (hex) Password 500 writing on Parameter ID 2B A2 48 01 F4 01 00 00

10402

Please find the password level in ToolKit: [STATUS MENU / Diagnostic/Interfaces / CAN /
CAN 1 state].
☼ Procedure for CAN 2
• CAN interface 2 Parameter ID = 10432 (dec) = 28C0 (hex)

• Incorporate the 2000 (hex) value: 28C0 (hex) + 2000 (hex) = 48C0 (hex)
• Identifier: 600 (hex) + Node-ID
• Example Node-ID is 1
601 (hex) Password 500 writing on Parameter ID 2B C0 48 01 F4 01 00 00

10432

Please find the password level in ToolKit: [STATUS MENU / Diagnostic/Interfaces / CAN /
CAN 2 state].
Code level display
The current code level is indicated by the lock symbol in the configuration menu screens.
The lock symbol indicates the number of the code level and appears as "locked" (in code
level CL00) or "unlocked" (in higher code levels).
Symbol Status
Locked
Unlocked (Code Level 01)

4 Configuration
[Default]
10400 Password display 0 0000 to 9999 The password for configuring the
control via the front panel must be
[random number] entered here.
10405 Code level display 0 (display only) This value displays the code level
which is currently enabled for
[0] access via the front panel display
or the Woodward Remote Panel
with screen share mode.
Code level interfaces
The password and/or User name for access via interface cannot be entered via HMI.
[Default]
10402 Password for CAN 0 0000 to 9999 The password for configuring the
interface 1 control via the CAN interface #1
[random number] must be entered here.
Not visible but can be accessed by

interface!
10407 Code level CAN 0 [0] This value displays the code level
interface 1 which is currently enabled for
access via the CAN interface #1.
10432 Password for CAN 0 0000 to 9999 The password for configuring the
interface 2 control via the CAN interface #2

interface!
10422 Code level CAN 0 [0] This value displays the code level,
interface 2 which is currently enabled for
access via the CAN interface #2.
7486 Code level for USB 0 [0] This value displays the code level,
access via the USB interface.
The password is entered via the

ToolKit login window.
10430 Password for serial 0 0000 to 9999 The password for configuring the
interface control via the RS485 interface

interface!

4 Configuration
10420 Code level for RS485 0 [0] This value displays the code level,
access via the RS485 interface.
7490 User name Modbus 0 The user name for configuring the
TCP control via the Modbus TCP/IP
interface must be entered here.

interface!
7491 Password Modbus 0 0000 to 9999 The password for configuring the
TCP/IP control via the Modbus TCP/IP
[random number] interface must be entered here.

interface!
10427 Code level Modbus 0 [0] This value displays the code level,
TCP/IP which is currently enabled for
access via the Modbus TCP/IP
interface.
7816 IP Servlink Master 1 0 [0] This is the IP address of the PC

that is connected via ToolKit with
the device as Servlink Master 1.
7824 Code level Servlink 0 [0] This value displays the code level,
Master 1 which is currently enabled for
access as Servlink Master 1.




4 Configuration
4.3.4.1 Password System - Parameter Overview




4.3.4.1 Password System - Parameter Overview
General notes
The following passwords grant varying levels of access to the parameters.
Each individual password can be used to access the appropriate configuration level
through multiple access methods and communication protocols (via the front panel, via
serial RS-485 interface, and via the CAN bus).
[Default]
10415 Password Basic 1 1 to 9999 The password for the code level
"Basic" is defined in this
[-] parameter.
Refer to ╚═▷ “4.3.4 Enter

Password” for default values.

4 Configuration
4.3.4.1.1 Random Number for Password
10413 Password 3 1 to 9999 The password for the code level

commissioning "Commissioning" is defined in this
[-] parameter.

10414 Code temp. 3 1 to 9999 The algorithm for calculating the

commissioning password for the code level
[200] "Temporary Commissioning" is
defined in this parameter.
10412 Code temp. super 5 1 to 9999 The algorithm for calculating the
commissioning password for the code level
[400] "Temporary Super commissioning"
is defined in this parameter.
10411 Password super 5 1 to 9999 The password for the code level
commissioning "Super commissioning" is defined
[500] in this parameter.

10437 Alphanumeric code 3 (up tp 6 characters) Alphanumeric code for temporary

temp. comm. commissioning level.
[a9t5]
This is the alphanumeric algorithm
value for the formula to reach the
temporary commissioning code
level (Level 02), entered as string
here.
10438 Alphan. code temp. 5 (up tp 6 characters) Alphanumeric code for temporary
super comm. super commissioning level
[xk38]
This is the alphanumeric algorithm
value for the formula to reach the
temporary commissioning code
level (Level 04), entered as string
here.
4.3.4.1.1 Random Number for Password
[Default]
10416 Random number for [(random four letters Random number generated by the
password number)] easYgen-XT device. Needed to get
an alphanumeric password by
Woodward support.

4 Configuration
4.3.4.1.2 Change/Reset Alphanumeric Password
[Default]
Change password basic level
10439 Old password basic level 1 ((empty)) Enter here your old alphanumeric
password to release the password
change for the basic code level
(CL01)
10440 New password basic 1 ((empty)) Enter here your new alphanumeric
level password string for the basic code
level (CL01)
10441 Confirm password basic 1 ((empty)) Repeat here your new

level alphanumeric password string for
the basic code level (CL01)
10442 Change password basic 1 [No] With switching this parameter to

level yes, the control checks the entries
Yes for changing the password and
executes the password change, if
the entries are correct. The
visualization 10443 indicates the
successful execution.
Notes
If the parameters 10439, 10440,

and 10441 are not correct, the
password change is not executed.
10443 Change passw. error 0 Flag: illuminated LED

basic level
[green] Password was not changed or
successfully changed
red Error: password could not be

changed
10434 Reset password basic 2 Yes The control resets the password of
level the basic level to "CL0001".
[No]
Change password commissioning level
10444 Old password commiss. 3 ((empty)) Enter here your old alphanumeric
level password to release the password
change for the commissioning
code level (CL03)
10445 New password commiss. 3 ((empty)) Enter here your new alphanumeric
level password string for the
commissioning code level (CL03)
10446 Confirm password 3 ((empty)) Repeat here your new

commiss.level alphanumeric password string for
the commiss. code level (CL03)
10447 Change password 3 [No] With switching this parameter

commiss. level to »Yes«, the control checks the
Yes entries for changing the password
and executes the password
change, if the entries are correct.
The visualization 1048 indicates
the successful execution.
Notes

4 Configuration
[Default]

10448 Change passw. error 0 Flag: illuminated LED

commiss. level

changed
10435 Reset password 4 Yes The control resets the password of

commiss. level the commissioning level to
"CL0003".
[No]
Change password super commissioning level
10449 Old passw. super comm. 5 ((empty)) Enter here your old alphanumeric
level password to release the password
change for the super comm. code
level (CL05)
10450 New passw. super 5 ((empty)) Enter here your new alphanumeric
comm. level password string for the super
comm. code level (CL05)
10451 Confirm passw.super 5 ((empty)) Repeat here your new

comm.level alphanumeric password string for
the super comm. code level
(CL05)
10452 Change passw.super 5 [No] With switching this parameter

comm. level to »Yes«, the control checks the
Yes entries for changing the password
and executes the password
change, if the entries are correct.
The visualization 1053 indicates
the successful execution.
Notes

10453 Change passw. super 0 Flag: illuminated LED

error comm. level

changed
10436 Reset passw. super 11 Yes The control resets the password of
comm. level the commissioning level to
"CL0005" e.g., if you forgot your
password.
Notes
The code level to execute the

password reset is provided by
your Woodward sales support
partner.

4 Configuration
4.3.5 System Management
[Default]
[No]
CAUTION!
Don't initiate »Set factory default settings« during controlling a genset! This
causes easYgen rebooting.
Parameter ╚═▷ 1701 »Set factory default values« causes a reboot of the control. During
this time the genset system is not controlled by the easYgen! An uncontrolled operation
can lead into life-threatening hazard or damage.
After settings changed: Please wait 30 seconds to be sure changes are saved before
power cycling the device.
[Default]
1702 Device number 2 1 to 32 A unique address is assigned to

the control though this parameter.
[1] This unique address permits the
controller to be correctly identified
on the CAN bus. The address
assigned to the controller may
only be used once.
All other bus addresses are

calculated on the number entered
in this parameter.
The device number is also

important for the device
assignment in load sharing and
load-dependent start/stop.
Notes
The unit must be rebooted after

changing the device number to
ensure proper operation.
For multiple genset applications

please make sure to change
parameter ╚═▷ 8950 as well
1889 Device name 2 [Device_name] After set with parameter

preset 1893 this customer specific
12 to 38 characters but device name is used e.g. as
varies on font device name in Ethernet
network.

4 Configuration
Notes
Recommended are 19 ASCII

characters max. Blanks and
special characters will be
replaced.
1890 Device name 2 ["displayable characters (Pre)view of device name.

of parameter 1889"]
up to 38 characters but
varies on font
1893 Set device name 2 [No] YES: Device name typed in

as value of parameter 1889
Yes taken, processed, and
displayable characters
saved as parameter 1890.
Note
Reboot device to apply

changed device name on
network!
10419 REBOOT 2 [No] Yes: Reboot will be

initiated.
Yes
Notes
Some parameters require a

reboot to take effect.
Reboot is only possible in

operation mode STOP!
10417 Factory default 0 Yes The following three parameters

settings are visible and restoring the
configured parameters to factory
default values is enabled.
[No] The following three parameters

are invisible and restoring the
configured parameters to factory
default values is not enabled.
1701 Set factory default 4 Yes All parameters, with the exception
values of customer defined passwords,
will be restored to factory default
values. If the default setting is
initiated the alarm LED starts
twinkling with a higher rate (ca. 5
Hz).
Notes
The device is power cycled and

rebooting after approx. 20
seconds!

4 Configuration
4.3.5.1 Reboot Function
In case of ToolKit connected via

USB service port: USB connection
will be lost!
[No] All parameters will remain as

currently configured.
Notes

if factory default settings
"Yes".
4.3.5.1 Reboot Function
The reboot of the device can be initiated by operating a Yes/No switch in ToolKit. This is
beneficial because some parameters, like
• 1893 Set device name,
• 3184 Modbus protocol number with Telegram mapper,
• 15320 Select external terminals
• or 15102 Device type
need a reboot procedure to become effective.
Please be careful with this setting because the device goes off and reboots at new with
all its consequences. It's the same like power off/on cycle.
The parameter is located on different ToolKit pages:
• Configure system management
• Modbus protocol
• CANOpen
• J1939

4 Configuration
4.3.6 Configure Remote Panel Mode
4.3.6 Configure Remote Panel Mode
4.3.6.1 Configuration screen Remote Panel Mode
Fig. 127: Configure Remote Panel
4.3.6.2 General notes
General notes
If the remote panel interacts with an easYgen, different use cases could be desired. So
the remote panel runs usually without any restrictions, if it is connected with an
easYgen-3100XT or easYgen-3400XT. This mode is called Full Access Mode.
But if the remote panel runs with an easYgen-3200XT or easYgen-3500XT, it is not always
allowed that both HMI have full control access rights to the genset. Here it is desired to
either restrict the control rights for the remote panel (Annunciator Mode) or for the local
HMI (Local Keylock). And finally it will be desired to switch off the remote panel
completely.
To maintain the different operating modes in the remote panel the easYgen has to
determine with LogicsManagers in which operation mode the Remote Panel RP-3000XT
shall run. If no LogicsManager is true, full mode with password suppression is active.
Following operation modes are defined (in order of the LogicsManager priority):
• RP-3000XT Full mode with password suppression (no LM true)
• RP-3000XT Full mode
• RP-3000XT Annunciator mode
• RP-3000XT Off mode (highest priority)

4 Configuration
4.3.6.3 RP-3000XT in Full Mode with Password suppression
4.3.6.3 RP-3000XT in Full Mode with Password suppression
Fig. 128: Remote Panel with display (plastic housing) variant of easYgen-XT
The RP-3000XT represents full the easYgen-3000XT (with Password suppression)
• All Operating Mode buttons are indicated and active
• The MAN Start Stop buttons are indicated and active
• The Acknowledge button is indicated and active
• The Alarm Symbol is indicated and active
• The “Home” button is indicated and active
• The Configuration capability is activated
• No suppress of any screen
• Password Screen is suppressed in the RP, if operated by easYgen-3000XT
• Password entry field of the Password Screen in the easYgen is suppressed, if

operated by RP-3000XT
The password suppressed Full Mode becomes active, if there is no mode selected via
LogicsManager.
If "Password display" entry field is operated in the RP-3000XT:
• "Password display" entry field in the easYgen is suppressed
• Buttons on the bottom (surrounded by blue dotted line) of the easYgen-3500XT

display are blocked
• Button BACK on the upper right is still active (leave password screen)

4 Configuration
4.3.6.4 RP-3000XT in Full Mode
Fig. 129: Password display on easYgen screen
If "Password display" entry field is operated in the easYgen-3000XT:
• Password Screen in the RP-3000XT (VNC viewer) is suppressed
• All buttons of the password screen in the RP-3000XT are blocked
4.3.6.4 RP-3000XT in Full Mode
Fig. 130: Remote Panel with non-display (metal housing) variant of easYgen-XT
The RP-3000XT represents full the easYgen-3000XT
• All Operating Mode buttons are indicated and active
• The MAN Start Stop buttons are indicated and active
• The Acknowledge button is indicated and active

4 Configuration
4.3.6.5 RP-3000XT in Annunciator Mode
• The Configuration capability is activated
• No suppress of any screen
• No suppress of Password Screen
The Full Mode becomes active, if the easYgen-XT is configured as follows:
• LM "RP-3000XT Full mode" is TRUE
AND
• LM "RP-3000XT Annunciator mode" is FALSE
AND
• LM "RP-3000XT Off mode" is FALSE
4.3.6.5 RP-3000XT in Annunciator Mode
The RP-3000XT shows measurement, condition, and alarm data of the easYgen-3000XT.
Data in regards to configuration and parameter are faded out and a "disabled" screen
(crossed out ╚═▷ Fig. 133) is displayed instead.
• All Operating Mode buttons are not visible, but the current operation is indicated
• The MAN Start/Stop buttons and the breaker soft key buttons are not indicated
• The Acknowledge button is not indicated
• The Configuration capability is deactivated (according soft key buttons are not
indicated or not active)
• All configuration screens of the easYgen are suppressed in the RP-3000XT (disabled
screen)
Fig. 131: RP in Annunciator mode - Home screen

4 Configuration
4.3.6.6 RP-3000XT in Off Mode
The Annunciator mode becomes active, if the easYgen-XT is configured as follows:
• LM "RP-3000XT Annunciator mode" is TRUE
AND
• LM "RP-3000XT Off mode" is FALSE
Fig. 132: RP in Annunciator mode - access to menu
Fig. 133: RP in Annunciator mode - "disabled"screen
4.3.6.6 RP-3000XT in Off Mode
The RP-3000XT supports no screen of the easYgen-3000XT.

4 Configuration
4.3.6.7 Parameters of RP Modes
Fig. 134: RP in OFF mode
The Off Mode becomes active, if the easYgen-XT is configured as follows
• LM "RP-3000XT Off mode" is TRUE
4.3.6.7 Parameters of RP Modes
Priority of RP Modes
»RP Off mode« higher than »RP Annunciator« higher than »RP Full mode«.
If no mode is selected via LogicsManager »Full mode with Password suppression« is

active!
[Default]
7857 RP Full mode 2 Determined by LogicsManager Once the conditions of the

86.43 LogicsManager have been fulfilled
the unit will empower the
[(02.01 LM FALSE & 02.02 LM RP-3000XT into Full mode
TRUE) & 02.02 LM TRUE] described above.
= 11994
7858 RP Annunciator 2 Determined by LogicsManager Once the conditions of the

the unit will empower the
[(02.01 LM FALSE & 02.02 LM RP-3000XT into Annunciator mode
TRUE) & 02.02 LM TRUE] described above.
= 11995
7859 RP Off mode 2 Determined by LogicsManager Once the conditions of the

the unit will downgrade the
[(02.01 LM FALSE & 02.02 LM RP-3000XT to Off mode described
TRUE) & 02.02 LM TRUE] above.

4 Configuration
4.4 Configure Application
[Default]
= 11996
4.4 Configure Application
4.4.1 Configure Engine
4.4.1.1 Configure Engine (general)
[Default]
3321 Start/Stop mode logic 2 Diesel or gas engine start/stop

logic must be selected.
[Diesel] Start sequence
The relay "Preglow" will be

energized for the preheating time
period ("Preglow" is displayed).
Following preheating, the fuel
solenoid is first energized and
then the starter is engaged
("Start" is displayed).
When the configured firing speed

is exceeded, the starter is
disengaged and the fuel solenoid
remains energized via the firing
speed. "Ramp to rated" is
displayed until the engine
monitoring delay timer expires
and the start sequence has
finished.
If the engine fails to start, a start

pause is initiated ("Start - Pause"
is displayed). If the number of
unsuccessful start attempts
reaches the configured value, an
alarm message will be issued
("Start fail" is displayed).
Stop sequence
After opening the GCB, the

coasting time starts and the
engine runs without load ("Cool
down" is displayed). On
termination of the coasting time,
the fuel solenoid is de-energized,
and the engine is stopped ("Stop
engine" is displayed). If the engine
cannot be stopped via the fuel
solenoid, the alarm message "Eng.
stop malfunct." is displayed.
Start/stop diagram

4 Configuration
The formula signs and indices

mean:
• tPRE Auxiliary services

prerun [s] (parameter ╚═▷
3300)
• tPH Preglow time [s]
(parameter ╚═▷ 3308)
• tST Starter time [s]
• tSP Start pause [s]
• tED Engine delayed
monitoring [s] (parameter
╚═▷ 3315)
• tPOST Auxiliary services
postrun [s] (parameter ╚═▷
3301)
• tCD Cool down time [s]
• tGS Generator stable time [s]
Refer to ╚═▷ “Diesel engine

diagrams”.
Gas Start sequence
The starter is engaged ("Turning"

is displayed). Following the
expiration of the firing delay time
and if the engine is rotating with
at least the configured "minimum
speed for ignition", the ignition is
switched on ("Ignition" is
displayed).
Following the expiration of the gas

valve delay, the gas valve is then
enabled ("Start" is displayed). If
the configured firing speed is
exceeded, the starter is
disengaged. The gas valve and
the ignition remain enabled via
the firing speed. "Ramp to rated"
is displayed until the engine
monitoring delay timer expires
and the start sequence has
finished.
If the configured "minimum speed

for ignition" is not reached, a start
pause is initiated ("Start - Pause"
is displayed) before the next start
attempt.
Stop sequence
After opening the GCB, the

coasting time starts and the
engine runs without load ("Cool
down" is displayed). On
termination of the coasting time,
the gas valve is closed or de-
energized, and the engine is
stopped ("Stop engine" is
displayed).
If the engine cannot be stopped,

the alarm message "Eng. stop
malfunct." is displayed. If no
speed is detected anymore, the
ignition remains active for

4 Configuration
5 seconds so that the remaining

gas is able to combust.
Start/stop diagram
The formula signs and indices

mean:
• tPRE Auxiliary services

prerun [s] (parameter ╚═▷
3300)
• tST Starter time [s]
• tSP Start pause [s]
• tID Ignition delay [s]
• tGD Gas delay [s]
• tED Engine delayed
monitoring [s] (parameter
╚═▷ 3315)
• tPOST Auxiliary services
postrun [s] (parameter ╚═▷
3301)
• tCD Cool down time [s]
• tIC Ignition coasting ("post
burning") [s] (fixed to
5 seconds)
• tGS Generator stable time [s]
Refer to ╚═▷ “Gas engine

diagrams” and ╚═▷ “Gas engine
diagrams”.
CAUTION
It is imperative to connect an
emergency stop circuit to discrete
input DI 1 to be able to perform an
emergency stop by disabling the
ignition in case the gas valve fails
to close.
External The start/stop sequence must be

done externally.
Off The start/stop sequence is

completely disabled.
The delayed engine monitoring is

dependent from LogicsManager
release engine monitoring ╚═▷
12999.
The GCB release is activated by

LogicsManager start request in
AUTO (parameter ╚═▷ 12120).
The controllers are deactivated in

operating mode STOP.
Please refer to ╚═▷ “6.3.12 Start/

Stop Logic Mode "Off"” for details.
Notes
All functions which are described

here, may be assigned by the
LogicsManager to any relay that is

4 Configuration
available via the LogicsManager

and not assigned to another
function.
3308 Preglow time [tPH] 2 1 to 999 s Notes
(Diesel engine) [5 s] The display indicates "Preglow".
3347 Preglow mode 2 This parameter dictates if and

under what conditions a diesel
(Diesel engine only) engine is preheated.
Off The diesel engine is never

preheated before a start attempt.
[Always] Before a start attempt the

"Preheating" relay is always
energized for the preglow time
(parameter ╚═▷ 3308). After that
a start attempt is initiated.
Analog A preglow sequence is initiated if

the monitored analog input
temperature (coolant
temperature) is below the
configured threshold
(parameter ╚═▷ 3309). The
preglow sequence is enabled for
the configured preglow time
(parameter ╚═▷ 3308). After that
a start attempt is initiated.
3309 Preglow temperature 2 -10 to 250 °C This is the temperature threshold,

threshold which must be exceeded to
[0 °C] prevent a preheating process, if
(Diesel engine only) parameter ╚═▷ 3347 has been set
to "Analog".
4057 Pre-excitation D+ 2 [On] When the engine is starting up, an

exciting current is issued.
Notes
The resulting voltage at terminal

65 can be monitored. Refer to
chapter ╚═▷ “4.5.2.7 Engine
Charge Alternator (D+)” for
details.
Off No exciting current is issued. The

input D+ can be used as analog
input which can be configured
freely e.g. for (firing) speed
detection.
Notes
This function is only working if the

battery voltage is below 27.5 V to
avoid overload of internal circuitry.
3346 AM Preglow criterion 2 Determined by AnalogManager The preglow criterion may be

81.01 selected from the available data
(Diesel engine only) sources.
[A1 = 10.01 ZERO]

4 Configuration
Usually, a temperature measuring

is selected here, which is
measured via a sensor.
Notes
Refer to ╚═▷ “4.9.1 Operations”

for explanation how to use the
AnalogManager.
Refer to ╚═▷ “9.4.2 Data Sources

AM” for a list of all data sources.
3310 Ignition delay [tID] 2 0 to 9999 s With gas engines often a purging
operation is desired before
(Gas Engine only) [5 s] starting.
With the engaging of the starter

the ignition delay is started. The
display indicates "Turning".
If the "Minimum speed for

ignition" is reached after the
expiration of this time, the ignition
is energized.
3311 Gas valve delay [tGD] 2 1 to 999 s By energizing the ignition relay
the gas valve delay is started
(Gas Engine only) [5 s] ("Ignition" is displayed).
After the time set here has

expired, and as long as the speed
is higher than the minimum speed
for ignition, the gas valve is
enabled for the time configured in
parameter ╚═▷ 3306 "Starter
time" ("Start" is displayed).
Once the ignition speed has been

reached, the gas valve remains
opened. If the speed falls below
ignition speed, the gas valve will
be closed and the "Ignition" relay
is de-energized 5 seconds later.
3312 Minimum speed for 2 10 to 1,800 rpm After expiration of the ignition
ignition delay the number of revolutions
[100 rpm] set here must be reached, so the
(Gas Engine only) "Ignition" relay will be energized.

4 Configuration
Diesel engine diagrams
Fig. 135: Start/Stop sequence - diesel engine

4 Configuration
Gas engine diagrams
Fig. 136: Start/Stop sequence - gas engine - failure

4 Configuration
4.4.1.2 Engine Start/Stop
Fig. 137: Start/Stop sequence - gas engine - success
Speed States
Firing speed and the speed detection is now managed by LogicsManager equations
named “Firing speed detection” and “Speed detection”. The default setting of them is
backward compatible!

4 Configuration
The possibility to arrange different sources to determine speed and firing speed comes
with more flexibility. Woodward recommends to spend some time to understand the
parameters and dependencies listed below or on ToolKit page [Parameter / Configuration /
Configure application / Configure engine / Configure start/stop].
Firing Speed detection
The “Firing Speed” detection is a basic function of the easYgen genset controls. This
information influences a lot of functions and therefore is to configure very carefully!
With the firing speed detection the device recognizes e.g. the engine as successfully
started, removes the starter immediately and triggers the timer »Monitoring delay
time« for engine speed relevant monitoring. The firing speed can be detected out of
different sources.
In comparison to the easYgen-3000 first generation, the firing speed is generated through
a LogicsManager equation always and allows all speed source combinations. By default
this LogicsManager is configured backward compatible: easYgen-XT behaves like the first
generation easYgen-3000.
Speed detection
With the “Speed” detection the device recognizes e.g. the engine as turning or as
successful stopped. The speed can be detected out of different sources.
In comparison to the easYgen-3000 first generation, the speed is generated through a

LogicsManager equation and allows all speed source combinations. By default the
LogicsManager is configured backward compatible: easYgen-XT behaves like the first
generation easYgen-3000.
The easYgen provides two LogicsManager command variables (LMCV) for detecting
speed:
• Electrical measured determined speed
• Speed sensor (rpm) determined speed

4 Configuration
Configuration of the Firing Speed Detection
Fig. 138: Internally determined firing speed flags
The electrical frequency measurement starts at 15 Hz. So 15 Hz is usually the lowest

firing speed limit. This corresponds for a 4-pole synchronous generator to 450 rpm at
50Hz.
The rpm measurement allows lower firing speed limits. With a speed sensor the firing
speed can be configured down to 5 Hz.

4 Configuration
☼ Firing speed configuration
Configuration A)
• Firing speed: 5 Hz
• Rated speed: 1800 rpm
Rated frequency: 60 Hz
Calculation
• Firing speed [rpm] = (Firing speed [Hz] * Rated speed [rpm]) / Rated frequency [Hz]
• Firing speed [rpm] = 5 Hz * 1800 rpm / 60 Hz = 150 rpm
Configuration B
• Firing speed: 5 Hz
• Rated speed: 1500 rpm
Rated frequency:50 Hz
Calculation
• Firing speed [rpm] = (Firing speed [Hz] * Rated speed [rpm]) / Rated frequency [Hz]
• Firing speed [rpm] = 5 Hz * 1500 rpm / 50 Hz = 150 rpm
Usually both command variables 02.34 and 02.35 are entered in the LogicsManager
equation for detecting firing speed.
Fig. 139: LogigsManager Firing speed detection
The result of the LM »Firing speed detection« goes directly into the start / stop logic and
other functions of the easYgen. Through the LogicsManager approach other sources can
be taken into account.

4 Configuration
Configuration of the Speed Detection
Fig. 140: Internally determined speed flags
The electrical frequency measurement starts at 15 Hz. So 15 Hz is usually the lowest

speed limit. This corresponds for a 4-pole synchronous generator to 450 rpm at 50Hz.
The rpm measurement allows lower speed limits. With a speed sensor the speed can be
configured down to 5 Hz.
Usually both command variables 02.36 and 02.37 are entered in the LogicsManager
equation for detecting speed.
Fig. 141: LogicsManager for detecting speed
The result of the LM »Speed detection« goes directly into the start / stop logic and other
functions of the easYgen. Through the LogicsManager approach other sources can be
taken into account.

4 Configuration
Firing speed and delayed monitoring
When the firing speed is reached, the starter is disengaged under one of the following
conditions:
• The measurement via MPU is enabled (On):

◦ Ignition speed measured via MPU is detected or
◦ Ignition speed measured via the generator voltage is detected or
◦ Ignition speed measured via ECU/J1939 or
◦ Conditions for "Ignition speed" (see LogicsManager) equal true.
• The measurement via MPU is disabled (Off):
◦ Ignition speed measured via the generator voltage is detected or
◦ Conditions for "Ignition speed" (see LogicsManager) equal true.
Fig. 142: Engine - firing speed
Auxiliary operations
The auxiliary operations start, as soon as the engine is to be started or a running engine
is detected.
At the same time, the discrete output for the auxiliary services (LogicsManager 03.01) will
be enabled. This discrete output remains enabled as long as speed is detected or if the
controller is in the MANUAL mode.

4 Configuration
Fig. 143: : Engine - auxiliary services timing

4 Configuration
Start/Stop logic (inhibit cranking)
Fig. 144: Engine - start/stop logic (inhibit cranking)
[Default]
3302 Start attempts 2 1 to 20 The control will attempt to start

the engine with this number of
[3] start attempts.
If the engine fails to start after the

configured number of attempts,
an alarm will be initiated.
An engine has been successfully

started if the ignition speed
reaches the configured firing
speed and the delayed engine
monitoring (set by release engine
monitoring) has expired.
4102 Start attempts 2 1 to 20 If a critical operation mode (╚═▷

critical mode “4.4.6 Emergency Run”) is
[10] initiated, the engine will continue
to attempt to start for the number
of starts configured here.
An engine has been successfully

started if the ignition speed
reaches the configured firing
speed and the delayed engine

4 Configuration
monitoring (set by release engine

monitoring) has expired.
3306 Starter time 2 1 to 99 s This is the maximum time that the

starter relay will remain energized
(Maximum starter delay [5 s] ("Start" display).
[tST])
If the LogicsManager output
"Ignition speed reached" = TRUE,
the speed/frequency have reached
firing speed, or the time has
expired, the relay will be de-
energized.
3307 Start pause time [tSP] 2 1 to 99 s This is the delay time between the
individual starting attempts.
[7 s]
This time is also used to protect
the starter relay. The message
"Start - Pause" is displayed.
4844 Inhibit cranking max. 2 1 to 999 s If the inhibit cranking (parameter

time ╚═▷ 4871 becomes active this
[60 s] counter starts.
Once the counter exceeds the

delay time, the message "Start
fail" is displayed.
The LogicsManager command

variable "Inhibit cranking" (03.38)
becomes TRUE as soon as the
inhibit cranking signal has been
issued and remains true until this
timer has expired.
3326 Stop time of engine 2 1 to 99 s During this time a restart of the

engine is blocked. This time
(Engine blocking) [10 s] should be configured so that the
engine is total shutdown to
protect the starting circuit.
Once speed from the engine is no

longer detected the time
configured in this parameter is
initiated. The message "Stop
engine" is displayed.
The LogicsManager command

variable "Stop solenoid" (03.27)
becomes TRUE as soon as the
stop signal has been issued and
remains true until this timer has
expired.
3313 Firing speed 2 5 to 60 Hz After firing speed has been

reached, the starter is
[15 Hz] disengaged.
The firing speed is to be

configured low enough that it is
always exceeded during regular
generator operation.
Notes

4 Configuration
The time counter for the engine

delayed monitoring is no longer
activated directly by firing speed
but by release engine monitoring
╚═▷ 12999.
Frequency measurement via the

generator voltage input is possible
beginning with 15 Hz or higher. If
the MPU measurement is enabled,
values down to 5 Hz can be
measured.
With this firing speed limit are

generated both the »firing speed
electric« flag 02.34 and the »firing
speed rpm« flag 02.35.
3315 Engine monitoring 2 1to 99 s Delay between reaching release

delay time engine monitoring and activation
[8 s] of the monitoring of engine speed
(Engine delayed delayed alarms (i.e. underspeed).
monitoring [tED])
After reaching the firing speed,
the engine delayed monitoring
timer is started. Upon expiration
of this timer all "engine delayed
monitoring" configured alarms and
discrete inputs will be enabled.
This timer should be configured in

such a manner that it corresponds
to the starting time of the engine
plus any possible startup
transients. A GCB closure may
take place after the expiration of
this timer.
Notes
The overall time engine

monitoring is delayed from firing
speed becoming TRUE (former
version's setup), Delay On and
Delay OFF of LM equation 11459
release engine monitoring must
be added.
The GCB closure can be initiated

prior to engine delayed monitoring
by configuring the LogicsManager
"Undelay close GCB"
(parameter ╚═▷ 12210).
3316 Cool down time [tCD] 2 1 to 9999 s Regular stop
[180 s] If the engine performs a normal

stop (start request is disabled or
change into STOP operating
mode) or a stop caused by an
alarm of alarm class C/D, a cool
down with an opened GCB is
carried out. This time is
programmable. The message
"Cool down" is displayed and the
LogicsManager command variable
04.10 becomes TRUE.
Stop by a class 'C' or 'D' alarm

4 Configuration
If the engine is stopped by an

alarm of this alarm class, a cool
down is carried out with an
opened GCB. This time is
programmable.
Stop by a class 'E' or 'F' alarm
If the engine is stopped by an

alarm of this alarm class, the
engine is shutdown without a cool
down immediately.
Notes
If a critical operation mode (╚═▷

“4.4.6 Emergency Run”) is
initiated, the time configured in
critical mode postrun
(parameter 4109) will be used
instead of the cool down time.
3319 Cool down in STOP 2 [Yes] A cool down will be performed if

mode the genset is changed to STOP
operation mode.
No No cool down will be performed if

the genset is changed to STOP
operation mode.
3322 Cool down without 2 This parameter may be used to

breaker perform a cool down if the
application mode (parameter ╚═▷
3444) is configured to "None" or
"GCB open".
Yes A cool down will be performed if a

start signal is disabled or a stop
signal is enabled.
[No] No cool down will be performed if

a start signal is disabled or a stop
signal is enabled.
Notes
This parameter only applies to

application mode A01 A02 .
3300 Auxiliary services 2 0 to 9999 s Prior to a start sequence being

prerun [tPRE] initiated, the discrete output for
[0 s] the auxiliary services prerun
(Prerun auxiliary (LogicsManager 03.30) remains
operation (start enabled for the configured
preparation)) amount of time to permit engine
related operations (i.e. open
louvers) to be performed.
While this discrete output is

enabled the control screen will
display the message
"Aux.serv.prerun" for the
configured time.
The auxiliary services discrete

output disables when the
operation mode is changed from
the MANUAL operation mode or, if
engine speed is no longer
detected, when the discrete

4 Configuration
output for the auxiliary services

postrun (LogicsManager 03.31) is
disabled.
CAUTION
During an emergency start this

delay time "auxiliary prerun" is
not initialized. The engine will be
started immediately.
3301 Auxiliary services 2 0 to 9999 s After each engine stop (the engine
postrun [tPOST] stop timer has expired), the
[0 s] discrete output for the auxiliary
(Coasting auxiliary services postrun (LogicsManager
operation (post 03.31) remains energized for an
operation)) adjustable time (i.e. operate a
cooling pump).
If the operating mode is changed

from MANUAL to STOP or
AUTOMATIC without a start
command the relay remains
energized for this period of time.
The message "Aux.serv.postrun"

will be displayed on the control
unit screen. In the "MANUAL"
operating mode this relay output
is not used.
4871 Inhibit cranking 2 Determined by LogicsManager Once the conditions of the

the cranking (03.38) is blocked.
[(0 & 1) & 1] The discrete output relay [R 03]
will be not energized.
= 11455
Notes

settings see ╚═▷ “9.3.1
Please refer to ╚═▷ Fig. 144 for

details.
12951 Firing speed 2 Determined by LogicsManager This LogicsManager allows

detection 87.68 different sources to generate the
general firing speed flag. This will
[(02.34 Firing speed electr. OR be taken into account for the
02.35 Firing speed rpm) & 1] START/STOP automatic and some
monitoring functions.
= 11457
Notes
The former easYgen was fixed to

the electrical frequency always
and allowed other sources
additionally. The default setting
here is backward compatible.
12989 Speed detection 2 Determined by LogicsManager This LogicsManager allows

87.69 different sources to generate the
general speed flag. This will be
[(02.36 Speed electr. OR 02.37 taken into account for some
Speed rpm) & 1] monitoring functions.

4 Configuration
= 11458
Notes
The former easYgen was fixed to

the electrical frequency always.
The default setting here is
backward compatible.
12970 MAN engine start 2 Determined by LogicsManager With the rising edge of this
87.50 LogicsManager equation an
engine start command in
[(0 & 1) &1] operating mode MANUAL is
initiated. The state TRUE of this
= 11439 LM inhibits the start command in
MANUAL.
12971 MAN engine stop 2 Determined by LogicsManager With the rising edge of this
87.59 LogicsManager equation an
engine stop command in
[(0 & 1) &1] operating mode MANUAL is
initiated. The state TRUE of this
=11448 LM inhibits the start command in
MANUAL.
12999 Release eng.mon. 2 Determined by LogicsManager Switch to activate the delayed

87.70 engine monitoring e.g., oil
pressure, under frequency, ...
[(02.34 Firing speed electr. &
02.35 Firing speed rpm) & Notes
03.28 Start/Gas]
For more details see description
tON = 0.00; tOFF = 0.00] below.
= 11459
Release Engine Monitoring
This LogicsManager equation (ID = 12999 with logical command variable 11459) enables
or blocks all monitoring functions, which are speed related by enabled setting: “Delayed
by engine speed”:
• Under/Over frequency
• Under speed
• Under voltage
• ...

4 Configuration
4.4.1.3 Magnetic Pickup Unit
Fig. 145: Release Engine Monitoring screen
In the default setting of the easYgen the engine start/stop is executed by the easYgen
directly. So the engine monitoring is released, if the control energizes the solenoid valve
(Start/Gas 11657) and the firing speed is reached. In the moment the easYgen removes
the solenoid valve the monitoring is disabled. This avoids wrong alarms during the engine
stopping procedure.
In cases the start/stop of the drive is executed from outside, the command variable 03.28
Start/Gas (11657) is replaced by a command from outside i.e. any discrete input (09.XX).
With starting the drive the operator gives the command for monitoring. With stopping the
drive the command has to be removed to avoid wrong alarms during the engine stopping
procedure.
The delayed engine monitoring can be seen with the upcoming “Eye” symbol in the
single line diagram.
To configure the MPU input, the number of teeth on the flywheel detected by the
magnetic pick up (MPU) or the number of pickup pulses per revolution of the engine must
be configured.
The table below shows the speed measuring range for various flywheel teeth numbers
(parameter ╚═▷ 1602) and rated speeds (parameter ╚═▷ 1601) for a minimum signal
voltage of 2 Vrms.
Fly wheel teeth Rated speed [rpm] Speed measuring range [rpm]
10 1500 1200 to 4500
10 1800 1200 to 5400
10 3000 1200 to 9000
10 3600 1200 to 10800

4 Configuration
25 750 480 to 2250
25 1500 480 to 4500
25 1800 480 to 5400
25 3000 480 to 9000
25 3600 480 to 10800
50 750 240 to 2250
50 1500 240 to 4500
50 1800 240 to 5400
50 3000 240 to 9000
50 3600 240 to 10800
100 750 120 to 2250
100 1500 120 to 4500
100 1800 120 to 5400
100 3000 120 to 6000
100 3600 120 to 6000
150 750 80 to 2250
150 1500 80 to 4000
150 1800 80 to 4000
150 3000 80 to 4000
150 3600 80 to 4000
200 750 60 to 2250
200 1500 60 to 3000
200 1800 60 to 3000
200 3000 60 to 3000
260 750 50 to 2250
260 1500 50 to 2300
260 1800 50 to 2300
280 750 45 to 2100
280 1500 45 to 2100
280 1800 45 to 2100
300 750 40 to 2000
300 1500 40 to 2000
300 1800 40 to 2000
400 750 30 to 1500
400 1500 30 to 1500
500 750 24 to 1200
600 750 20 to 1200
700 750 18 to 850

4 Configuration
4.4.1.4 Idle Mode
800 750 15 to 750
Tab. 44: MPU input - typical configurations
[Default]
1600 MPU input 2 [On] Speed monitoring of the engine is

carried out by the MPU or via ECU/
(Pickup) J1939.
Off Speed/frequency monitoring of

the generator set (the engine) is
performed by measuring the
frequency of the generator.
15155 Engine speed source 2 [Internal] The internal MPU input is used as
engine speed source.
ECU/J1939 An external ECU/J1939 signal is

used as speed source.
1602 Fly wheel teeth 2 2 to 800 Number of pulse per revolution/

teeth on the flywheel.
[118]
Notes
This parameter is only applicable

if parameter ╚═▷ 15155 is set to
"Internal".
4.4.1.4 Idle Mode
General notes
When the engine is operated at idle speed, undervoltage, underfrequency, and

underspeed monitoring as well as the monitoring of the flexible limits 33 through 40 are
not performed.
This function allows for a controlled operation of an engine without alarm messages at a
lower speed (below the configured underspeed monitoring values) for e.g. a warm-up
operation with low emission.
The frequency controller output does not control the idle speed; it will remain in initial
state position. The GCB cannot be closed in idle mode.
A message may be output to a relay here using the LogicsManager (Idle mode is active,
command variable 04.15), e.g. as a signal for a speed controller. The display indicates
"Idle run active" during idle mode.
The idle mode can be only used if the function is supported by the ECU or the frequency
controller.

4 Configuration
4.4.1.4 Idle Mode
The normal operation monitoring limits will be enabled again, if one of the following
conditions is fulfilled:
• Idle mode has ended and generator frequency has reached rated frequency -1 Hz.
(e.g. 49 Hz at 50 Hz rated)
• Idle mode has ended and engine delayed monitoring (parameter ╚═▷ 3315) has
expired.
The flexible limits 33 through 40 are disabled during idle mode operation (╚═▷ “4.5.5
Flexible Limits”).
[Default]
12570 Auto idle mode 2 Determined by LogicsManager Once the conditions of the
the engine will be operated in idle
[(0 & 1) ≥1 0] mode automatically for the
configured time during start-up.
= 15719 Monitoring is limited as described
above.
This function may always be

configured to "1" for example.
Notes

12550 Constant idle run 2 Determined by LogicsManager As long as the conditions of the
(Continuous idle mode) the engine will be continuously
[(0 & 1) & 0] operated in idle mode. Monitoring
is limited as described above. A
= 10713 key switch via a DI may be
configured here for example.
Notes
The idle mode is blocked if the

GCB is already closed.

3328 Automatic idle time 2 1 to 9999 s The automatic idle mode is active
for the time configured here.
(Time for automatic idle [30 s] Monitoring is limited as described
mode) above during this time.
3329 During emergency / 2 Yes If an emergency or critical

critical operation is enabled, the engine

4 Configuration
4.4.2 Inputs And Outputs
(Idle mode possible will go to rated speed only after

during emergency / completing the configured idle
critical operation) mode.
[No] If an emergency or critical

operation is enabled, no idle run
will be performed. The engine will
go directly to rated speed.
4.4.2 Inputs And Outputs
4.4.2.1 Function Of Inputs And Outputs
4.4.2.1.1 Discrete Inputs
The discrete inputs may be grouped into two categories:
• Programmable
◦ The discrete input has been assigned a default function using either the
LogicsManager or preconfigured alarms such as "emergency stop".
◦ The following sections describe how these functions are assigned.
◦ The function of a discrete input can be changed if required.
◦ The following description of the inputs, labeled with "programmable", refers to

the preconfiguration.
• Fixed
◦ The discrete input has a specific function that cannot be changed depending
upon the configured application mode.
Input Type/Preset Description
Discrete input [DI Programmable This discrete input is configured as alarm class F and is
01] not delayed by the engine speed.
Preconfigured to "Emergency STOP"
Discrete input [DI Programmable Enabled in the AUTOMATIC operation mode

02]
Preconfigured to "Startrequest in This discrete input is configured as a Control input in the
AUTO" alarm class and is not delayed by the engine speed.
• Energized
If the unit is in the AUTOMATIC operation mode

(selected with the operating mode selection push
button on the front panel) the controlled engine is
started automatically.
• De-energized
The engine is stopped.
Discrete input [DI Programmable This discrete input is configured as alarm class B and is
03] delayed by the engine speed.
Preconfigured to "Low oil pressure"
Discrete input [DI Programmable This discrete input is configured as alarm class B and is
04] not delayed by the engine speed.

4 Configuration
4.4.2.1.1 Discrete Inputs

Preconfigured to "Coolant
temperature"
Discrete input [DI Programmable This discrete input is used as a remote acknowledgment
05] for alarms. The input is normally de-energized. When an
Preconfigured to "External alarm is to be acknowledged the input is energized. The
acknowledgment" first time an alarm in acknowledged, the centralized
alarm/horn is silenced. When the input is energized a
second time, all alarms, which are no longer active, will
be acknowledged.
This discrete input is configured as a Control input in the

alarm class and is not delayed by the engine speed.
Discrete input [DI Programmable Only applicable for application mode A04
06]
Preconfigured to "Release MCB" This discrete input is configured as a Control input in the
alarm class and is not delayed by the engine speed.
• Energized
The MCB is enabled and closure of the breaker is

permitted.
• De-energized
The MCB is not enabled and closure of the breaker is

not permitted. This function permits a supervisory
control (i.e. a PLC) to allow the closure of the MCB by
the genset control.
Discrete input [DI Fixed to "MCB open reply" Only applicable for application mode A04
07]
This input implements negative function logic.
The controller utilizes the CB auxiliary (B) contacts into

this discrete input to reflect the state of the MCB.
This discrete input must be energized to show when the

breaker is open and de-energized to show when the MCB
is closed. The status of the MCB is displayed on the
screen.
This input is usually used in all breaker modes to change

between frequency/voltage and power/power factor
control (refer to note below).
Discrete input [DI Fixed to "GCB open reply" Only applicable for application modes A03 and A04
08]
This input implements negative function logic.
The controller utilizes the CB auxiliary (B) contacts into

this discrete input to reflect the state of the GCB. This
discrete input must be energized to show when the
breaker is open and de-energized to show when the GCB
is closed. The status of the GCB is displayed on the
screen.
This input is usually used in all breaker modes to enable

reverse power protection, overload MOP protection,
mains decoupling and the activation of the load sharing
(refer to note below).
Discrete input [DI Programmable Can be set-up with description, delay, operation, alarm
09] class, self acknowledgment, and enable.
"Discrete Input 9
Discrete input [DI Programmable

10]
"Discrete Input 10

4 Configuration
4.4.2.1.2 Discrete Outputs

11]
"Discrete Input 11

12]
"Discrete Input 12
The genset control usually decides whether it performs voltage and frequency (V/f)
control or power and power factor (P/PF) control using the reply of the circuit breakers,
i.e. the discrete inputs DI 7 and DI 8.
• If the GCB is open, only V/f control is performed

• If the GCB is closed and the MCB is open, V/f control as well as active and reactive
power load sharing is performed
• If the GCB is closed and the MCB is closed, P/PF control or import power control with
load sharing and PF control is performed.
A different configuration is possible and depends on the following LogicsManager

(parameter ╚═▷ 12940 "P control" and parameter ╚═▷ 12941 "Q control")
Alarm inputs
All discrete inputs, which are not assigned to a function, can be used as alarm or control
inputs. These discrete inputs can be freely configured as such (╚═▷ “4.4.2.2 Discrete
Inputs”).
• Programmable
◦ The discrete output has been assigned a default function using the
LogicsManager.
◦ The following text describes how these functions are assigned using the
LogicsManager.
◦ It is possible to change the function of the discrete output if required.
◦ The following description of the outputs, labeled with "programmable", refers to

the preconfiguration.
• Fixed
◦ The discrete output has a specific function that cannot be changed depending
upon the configured application mode.
◦ The discrete output cannot be viewed or changed in the LogicsManager.
◦ However, the discrete output may be programmable in some application

modes.

4 Configuration
The discrete outputs can be "programmable" or "fixed" depending on the application

mode (parameter ╚═▷ 3444).
For information on the function of the discrete outputs depending on the configured
application mode refer to ╚═▷ “4.4.2.3 Discrete Outputs (LogicsManager)”.
CAUTION!
stop function.
the unit.
CAUTION!
Uncontrolled operation due to unknown configuration
The circuit breaker commands must be checked before every commissioning because the
relays can be used for different applications and can be assigned to various functions.
• Make sure that all relay outputs are configured correctly.
Output Type/Preset Description
Relay output [R Programmable This discrete output is used to ensure that the internal
01] functions of the controller are operating properly.
Fixed to "Ready for operation"
It is possible to configure additional events, which cause
CAUTION! Only relay [R 01] has an the contacts of this discrete output to open, using the
inverse logic. The relay opens (all LogicsManager.
other relays close), if the logical
output of the LogicsManager becomes
TRUE.
Relay output [R Programmable When a centralized alarm is issued, this discrete output is
02] enabled.
Preconfigured to "Centralized alarm
(horn)" A horn or a buzzer maybe activated via this discrete output.
Pressing the button with the "✔" symbol will acknowledge
the centralized alarm and disable this discrete output.
The discrete output will re-enable if a new fault condition

resulting in a centralized alarm occurs. The centralized
alarm is initiated by class B alarms or higher.
Relay output [R Programmable The generator starting circuit is engaged when this discrete
03] output is enabled.
Preconfigured to "Starter"
This discrete output will enable depending on the start
sequence (refer to the start sequence description in ╚═▷
“4.4.1.1 Configure Engine (general)”) to energize the
starter for the configured starter time (parameter ╚═▷
3306).

4 Configuration
Relay output [R Programmable Fuel solenoid

04]
Preconfigured to "Start/Gas" The fuel solenoid for the diesel engine is energized when
this discrete output is enabled. If the engine is given a stop
command or engine speed drops below the configured
firing speed, this discrete output is disabled immediately.
Gas valve
The gas valve for the engine is energized when this discrete
output is enabled. If the engine is given a stop command or
engine speed drops below the configured firing speed, this
discrete output is disabled immediately.
Relay output [R Programmable Preglow

05]
Preconfigured to "Preglow" When this discrete output is enabled, the diesel engine's
glow plugs are energized. This function only occurs if the
control has been configured for diesel engine start/stop
logic.
Ignition
When this discrete output is enabled, the gas engine's

ignition is enabled. This function only occurs if the control
has been configured for gas engine start/stop logic.
Notes
Refer to ╚═▷ “4.4.1.1 Configure Engine (general)”
Relay output [R Fixed to "Command: close GCB" Only applicable for application modes A03 and A04 .
06]
The "Command: close GCB" output issues the signal for the
GCB to close. This relay may be configured as an impulse or
steady output signal depending on parameter ╚═▷ 3414.
Impulse
If the output is configured as "Impulse", the discrete output

will enable for the time configured in parameter ╚═▷ 3416).
An external holding coil and sealing contacts must be
installed into the GCB closing circuit if this discrete output
is configured for an impulse output signal.
Steady
If the relay is configured as "Steady", the relay will energize

and remain enabled as long as the discrete input "Reply
GCB" remains de-energized and the generator and busbar
voltages are identical. If a class C or higher alarm occurs,
this discrete will disable and the GCB will open immediately.
Relay output [R Fixed to "Command: open GCB" Not applicable for application mode A01
07]
The parameter ╚═▷ 3403 defines how this relay functions.
If this output is configured as "N.O.", the relay contacts

close resulting in the GCB opening circuit energizing.
If this output is configured as "N.C.", the relay contacts

open resulting in the GCB opening circuit de-energizing.
If this output is configured as "Not used", this relay is freely

configurable.
Application mode A02
The open GCB command remains enabled until the GCB is

manually closed and the discrete input "Reply GCB" is

4 Configuration
4.4.2.2 Discrete Inputs

energized. The open GCB command will be issued when a
fault condition or an engine shut down occurs.
Application mode A03 or A04
The controller enables the open GCB command when the

GCB is to be opened for switching operations. If the discrete
input "Reply GCB" is energized, the open GCB command
will be disabled.
Relay output [R Fixed to "Command: close MCB" Only applicable for application mode A04 .
08]
The discrete output "Command: close MCB" is an impulse
output signal.
This discrete output is enabled for the time configured in

parameter ╚═▷ 3417.
An external holding coil and sealing contacts must be

utilized with the MCB closing circuit.
Relay output [R Fixed to "Command: open MCB" Only applicable for application mode A04 .
09]
The controller enables this discrete output when the MCB is
to be opened for switching operations.
If the discrete input "Reply MCB" is energized, the discrete

output "Command: open MCB" is disabled.
Relay output [R Programmable The auxiliary services output (LogicsManager 03.01) will be
10] enabled with the start command (prior to the engine start
Preconfigured to "Auxiliary services" because of the prerun time) and remains enabled as long
as the engine is running.
It will be disabled after the engine has stopped and the

postrun time has expired (i.e. for operating a cooling
pump). ╚═▷ “Auxiliary operations” for this behavior.
The auxiliary services output (LogicsManager 03.01) is

always enabled in MANUAL operation mode.
Relay output [R Programmable This discrete output is enabled when a warning alarm (class
11] A or B alarm) is issued (╚═▷ “9.5.4 Alarm Classes”).
Preconfigured to "Warning alarm"
After all warning alarms have been acknowledged, this
discrete output will disable.
Relay output [R Programmable This discrete output is enabled when a shutdown alarm
12] (class C or higher alarm; refer to ╚═▷ “9.5.4 Alarm Classes”
Preconfigured to "Shutdown alarm" for more information) is issued.
After all shutdown alarms have been acknowledged, this

discrete output will disable.
LogicsManager All discrete outputs not assigned to a defined function, may

Relay be freely configured via the LogicsManager.
General notes
Discrete inputs may be configured to normally open (N.O.) or normally closed (N.C.)
states.

4 Configuration
Fig. 146: Discrete inputs - alarm/control inputs - operation logic (state N.O.)
In the state N.O.:
• No potential is present during normal operation.
• If an alarm is issued or control operation is performed, the input is energized.
Fig. 147: Discrete inputs - alarm/control inputs - operation logic (state N.C.)
In the state N.C.:
• A potential is continuously present during normal operation
• If an alarm is issued or control operation is performed, the input is de-energized.
All reply messages from breakers are evaluated as N.C.
Alarm inputs may also be configured as control inputs and then be used as command
variables in the LogicsManager.
The discrete inputs 1 to 6 are pre-configured to various functions and differ in their
default values. However, they may still be configured freely.
The discrete inputs 7 & 8 are always used for the circuit breaker replies and cannot be
configured.

4 Configuration
If a discrete input has been configured with a shut-down alarm that has been enabled to
self-acknowledge, and has been configured as engine delayed the following scenario may
happen:
• The discrete input shuts down the engine because of its alarm class.
• Due to the engine stopping, all engine delayed alarms are ignored.
• The alarm class is acknowledged automatically.
• The alarm will self-acknowledge and clear the fault message that shut the engine
down.
This prevents the fault from being analyzed.
• After a short delay, the engine will restart.

• After the engine monitoring delay expires, the fault that originally shut down the
engine will do so again. This cycle will continue to repeat until corrected.
Internal discrete inputs - terminal assignment
Number Terminal Assignment (all application modes)
[DI 01] 67 Pre-configured for Alarm input 'Emergency Stop'
[DI 02] 68 Pre-configured for Control input 'Start request in AUTO'
[DI 03] 69 Pre-configured for Alarm input 'Low oil pressure'
[DI 04] 70 Pre-configured for Alarm input 'Coolant temperature'
[DI 05] 71 Pre-configured for Control input 'External acknowledgment'
[DI 06] 72 Pre-configured for Control input 'Release MCB'
[DI 07] 73 Reply MCB
[DI 08] 74 Reply GCB
[DI 09] 75 Pre-configured for Alarm input
Parameter IDs
The following parameters are used to configure the discrete inputs 1 through 12. The
parameter IDs refer to discrete input 1.
• Refer to ╚═▷ Tab. 45 for the parameter IDs of the parameters DI 2 through
DI 12(23).
DI 1 DI 2 DI 3 DI 4 DI 5 DI 6 DI 7 DI 8 DI 9 DI 10 DI 11 DI 12
MCB GCB
open open
only only
Des‐ 1400 1410 1420 1430 1440 1450 1460 1480 1488 1496 1504
crip‐
tion

4 Configuration
DI 1 DI 2 DI 3 DI 4 DI 5 DI 6 DI 7 DI 8 DI 9 DI 10 DI 11 DI 12
MCB GCB
open open
only only
Delay 1200 1220 1240 1260 1280 1300 1320 1360 1380 1205 1225
Oper‐ 1201 1221 1241 1261 1281 1301 1321 1361 1381 1206 1226
ation
Alarm 1202 1222 1242 1262 1282 1302 1322 1362 1382 1207 1227
class
Self 1204 1224 1244 1264 1284 1304 1324 1364 1384 1209 1229
ack‐
now‐
ledg‐
ed
Enabled 1203 1223 1243 1263 1283 1303 1323 1363 1383 1208 1228
Tab. 45: Discrete inputs - parameter IDs
[Default]
1400 DI {x} Description 2 user defined (up to 39 characters)

for default see ╚═▷ Tab.
If the discrete input is enabled
with alarm class, this text is
displayed on the control unit
screen.
The event history will store this

text message as well.
Notes
This parameter may only be

configured using ToolKit. 19
characters are best for HMI
readability - text strings with 20
and more characters but without a
blank in between are NOT visible
as headline on DI {x} detail
screen. DI selection screen on
HMI/display works fine with up to
30 characters; others are
overwritten by mandatory screen
symbols. Please verify the length
on the display for best view.
If the DI is used as control input

with the alarm class "Control", you
may enter here its function (e.g.
external acknowledgment) for a
better overview within the
configuration.
1200 DI {x} Delay 2 0.08 to 650.00 s A delay time in seconds can be

assigned to each alarm or control
[0.20 s] input.
The discrete input must be

enabled without interruption for

4 Configuration
the delay time before the unit

reacts.
If the discrete input is used within

the LogicsManager this delay is
taken into account as well.
1201 DI {x} Operation 2 The discrete inputs may be

operated by an normally open
(N.O.) or normally closed (N.C.)
contact.
The idle circuit current input can

be used to monitor for a wire
break.
A positive or negative voltage

polarity referred to the reference
point of the DI may be applied.
[N.O.] The discrete input is analyzed as

"enabled" by energizing the input
(normally open).
N.C. The discrete input is analyzed as

"enabled" by de-energizing the
input (normally closed).
1202 DI {x} Alarm class 2 An alarm class may be assigned to

the discrete input.
The alarm class is executed when

the discrete input is enabled.
A/[B] Warning alarm classes
C/D/E/F Shutdown alarm classes
Control Signal to issue a control command

only.
If "control" has been configured,

there will be no entry in the event
history and a function out of the
LogicsManager (╚═▷ “9.3.1
LogicsManager Overview”) can be
assigned to the discrete input.
1204 DI {x} Self 2 Yes The control automatically clears

acknowledge the alarm if the fault condition is
no longer detected.
[No] The control does not automatically

reset the alarm when the fault
condition is no longer detected.
The alarm must be acknowledged

and reset by manually pressing
the appropriate buttons or by
activating the LogicsManager
output "External
acknowledgment" (via a discrete
input or via an interface).
Notes

4 Configuration
4.4.2.3 Discrete Outputs (LogicsManager)
If the DI is configured with the

alarm class "Control", self
acknowledgment is always active.
1203 DI {x} Enabled 2 [Always] Monitoring for this fault condition

is continuously enabled.
87.70 LM:Eng.mon Monitoring for fault conditions is

not performed until engine
monitoring is enabled. This is
determined through the
LogicsManager equation "Release
engine monitoring".
For xx = 1 to 32: The monitoring is executed, if the

LogicsManager "Flag {xx}" is
96.{xx} TRUE.
LM: Flag{xx} Example:
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
The discrete outputs are controlled via the LogicsManager.
For information on the LogicsManager and its default settings see ╚═▷ “9.3.1
Some outputs are assigned a function according to the application mode (see following
table).
Relay Application mode
No. Terminal None A01 GCB open A02 GCB A03 GCB/MCB A04
[R 01] 41/42 LogicsManager; pre-assigned with 'Ready for operation OFF
CAUTION! Only relay [R 01] has an inverse logic. The relay opens (all other relays close), if
the logical output of the LogicsManager becomes TRUE.
[R 02] 43/46 LogicsManager; pre-assigned with 'Centralized alarm (horn)'
[R 03] 44/46 LogicsManager; pre-assigned with 'Starter'
[R 04] 45/46 LogicsManager; pre-assigned with 'Diesel: Fuel solenoid, Gas: Gas valve'
[R 05] 47/48 LogicsManager; pre-assigned with 'Preglow'
[R 06] 49/50 LogicsManager Command: close GCB
[R 07] 51/52 LogicsManager Command: open GCB
[R 08] 53/54 LogicsManager Command: close

MCB
[R 09] 55/56 LogicsManager Command: open

MCB
[R 10] 57/60 LogicsManager; pre-assigned with 'Auxiliary services'
[R 11] 58/60 LogicsManager; pre-assigned with 'Alarm class A, B active'

4 Configuration
Relay Application mode
No. Terminal None A01 GCB open A02 GCB A03 GCB/MCB A04
[R 12] 59/60 LogicsManager; pre-assigned with 'Alarm class C, D, E, F active'
Tab. 46: Internal relay outputs - assignment
CAUTION!
stop function.
the unit.
[Default]
12580 Ready for op. Off 2 Determined by LogicsManager The "Ready for operation" relay is
99.01 energized by default if the power
(Ready for operation supply exceeds 8 V.
OFF) [(0 & 0) & 1]
Once the conditions of the Logics‐
= 11870 Manager have been fulfilled, the
relay will be de-energized. This
LogicsManager output may be
configured with additional
conditions, which may signal a
PLC an "out of operation"
condition by de-energizing the
relay on terminals 41/42, like
"shutdown alarm" or no "AUTO
mode" present.
Notes
For information on the Logics‐

Manager and its default settings
see ╚═▷ “9.3.1 LogicsManager
Overview”.
12110 Relay {x} 2 Determined by LogicsManager Once the conditions of the Logics‐
99.02 Manager have been fulfilled, the
(See ID For (pre-defined) relay will be energized.
table function see assignment [(03.05 Horn & 1) & 1]
below) table above) Notes
= 11871
For information on the Logics‐
Manager and its default settings
see ╚═▷ “9.3.1 LogicsManager
Overview”.

4 Configuration
4.4.2.4 Analog Inputs
Parameter IDs
The parameter IDs above refers to relay 2.
• Refer to ╚═▷ Tab. 47 for the parameter IDs of the parameters for relay 3 to relay 12.
R1 R2 R3 R4 R5 R6 R7 R8 R9 R 10 R 11 R 12
Parameter ID 12580 12110 12310 12320 12130 12140 12150 12160 12170 12180 12560 12590
Tab. 47: Discrete outputs - relay parameter IDs
4.4.2.4 Analog Inputs
4.4.2.4.1 Analog Inputs (general)
4.4.2.4.1.1 Displayed units
Conversion restricted to ...
The conversions described below are only active for parameters »Unit« of
• J1939 pressure and temperature values
and
• analog inputs which units are configured as »°C« or »bar«.
Exact string mandatory
Type in* the »Unit« string carefully!
For example:
• Temperature works with the exact string»°C« only but not with »°c« or »degC« or »°
C« ...
• Pressure needs the exact string »bar« only but don't work with »Bar« or »BAR« ... !
*) Parameters »Unit« are:
AI {x} 1034, 1084, ...; external AI{x} 16208, 16218, ...; PID {x} setpoint 7494, 7495, ...;
customer screens {x.y} 7692, 7697, ...
[Default]
3630 Convert bar to psi 1 [No] The pressure value is displayed in

Bar.
Yes The pressure value is converted

and then displayed in psi.

4 Configuration
4.4.2.4.1.2 User Defined Tables A/B (Characteristic Curves Setup)
3631 Convert °C to °F 1 [NO] The temperature is displayed in °C

(Celsius).
Yes The temperature is displayed in °F

(Fahrenheit).
General notes
The characteristic curves of "Table A" and "Table B" (freely configurable over 9 defined
points) are independently configurable and can be used among other predefined curves
for each of the analog inputs. Each point may be scaled to related values measured from
the analog input (0 to 250/500/2500 Ohms, 0 to 10 V, or 0 to 20 mA), so that the actual
display and monitoring reflects the corresponding values (e.g. 200 to 600 kW).
The created characteristic curves can be used for scaling the analog inputs.
Fig. 148: Characteristic curves (example table)
The X and Y junction may be moved within the range of values and the space between
setpoints can be nonuniform.
When configuring the X coordinates, ensure the coordinates always increase in scale
continuously.
In the following example the first set of x/y coordinates is correct and the second set of
x/y coordinates is wrong:
(correct)
X-coordinate 0 10 20 40 50 60 80 90 100
Y-coordinate -100 -95 -50 -10 +3 +17 +18 +100 +2000
wrong:
X-coordinate 0 10 20 60 20 30 80 40 100
Y-coordinate -100 -50 -95 +18 +17 +3 -10 +2000 +100

4 Configuration
If the first X coordinate is >0, all values smaller than the first X value will be output with
the first Y value.
If the last Y value is <100, all higher values will be output with the value of Y9.
All parameters used to configure the characteristic curve follow the samples listed below.
• Refer to ╚═▷ “Parameter IDs and default values for all scaling points” for the
parameter IDs of the individual parameters for all scaling points of tables 'A' and 'B'.
Scaling points settings
[Default]
3560 to Table {A/B} X-value 2 -900000.000 to 900000.000 The analog input is assigned to a
3568 {1..9} curve. This parameter defines the
[0, ...] actual value assigned to each of
or the nine points along the X-axis of
the total range of the selected
3610 to hardware for analog input.
3618
Example
If a 0 to 20 mA input is configured
and the X1-coordinate = 0, then
the value configured for Y1 is
output for an input of 0 mA.
3550 to Table {A/B} Y-value 2 -21000000.00 to 21000000.00 This parameter defines the Y-
3558 {1..9} coordinate (the displayed and
[0, ...] monitored value) at the
or corresponding X-coordinate.
3600 to Example
3608
If a 0 to 20 mA input is configured
and the X2-coordinate = 10, then
the value configured for the Y2-
coordinate is output for an input
of 10 mA.
Tab. 48: Scaling point sample
Parameter IDs and default values for all scaling points
Scaling point no. 1 2 3 4 5 6 7 8 9
Table A - X value 3560 3561 3562 3563 3564 3565 3566 3567 3568
[0] [2.5] [5] [7.5] [10] [12.5] [15] [17.5] [20]
Table A - Y value 3550 3551 3552 3553 3554 3555 3556 3557 3558
[0] [10] [20] [30] [45] [60] [70] [85] [100]
Table B - X value 3610 3611 3612 3613 3614 3615 3616 3617 3618
[0] [2.5] [5] [7.5] [10] [12.5] [15] [17.5] [20]
Table B - Y value 3600 3601 3602 3603 3604 3605 3606 3607 3608

4 Configuration
4.4.2.4.2 Analog Inputs 1 to 3 (0 to 2000 Ω | 0/4 to 20 m A | 0 to 1 V)
Scaling point no. 1 2 3 4 5 6 7 8 9

[0] [10] [20] [30] [45] [60] [70] [85] [100]
General notes
Monitoring of the analog inputs (overrun/underrun) must be configured manually to the

flexible limits (╚═▷ “4.5.5 Flexible Limits”).
[Default]
1025 Analog input {x}: 2 user-defined (up to 39 characters) The event history will store this
Description text message and it is also
1075 [Analog inp. {x}] displayed on the visualization
screen.
1125
If the programmed limit value of
the analog input has been
reached or exceeded this text is
displayed in the control unit
screen.
Notes

as headline on AI {x} detail
screen. AI selection screen on
HMI/display works fine with up to
30 characters; others are
overwritten by mandatory screen
symbols.
The max. number of characters

depends on the numbers of Bytes
for each character.
Please verify the length on the

display for best view.
1000 Analog input {x}: 2 According to the following

Type parameters different measuring
1050 ranges are possible at the analog
inputs.
1100
[Off] The analog input is switched off.
VDO 5 bar The value of the analog input is

interpreted with the VDO
characteristics 0 to 5 bar.
VDO 10 bar The value of the analog input is

characteristics 0 to 10 bar.

4 Configuration
[Default]
VDO 150 °C The value of the analog input is

characteristics 50 to 150 °C.
VDO 120 °C The value of the analog input is

characteristics 40 to 120 °C.
Pt100 The value of the analog input is

interpreted with a Pt100
characteristic.
Pt1000 The value of the analog input is

interpreted with a Pt1000
characteristic.
AB 94099 The value of the analog input is

interpreted with a AB 94099
characteristic.
Linear Each analog input may be

assigned to a linear characteristic
curve, which can be only used for
the respective defined input
[T{x}] (x = 1 to 3). The minimum
value refers to the value
configured as "Sender value at
display min." (parameter ╚═▷
1039, ╚═▷ 1089 or ╚═▷ 1139). The
maximum value refers to the
value configured as "Sender value
at display max." (parameter ╚═▷
1040, ╚═▷ 1090 or ╚═▷ 1140).
Table A The analog input is assigned to a

characteristic curve which is
Table B defined over 9 points (stored in a
table). Two independent tables
(table A and table B) may be
allocated to the analog inputs.
Notes
Points of these tables must be

programmed into the control unit
before use.
For the characteristic curves of

the inputs refer to ╚═▷ “9.1.2 VDO
Inputs Characteristics”.
1001 User defined min. 2 -21000000.00 to 21000000.00 The value (y-axis) to be displayed
display value for the minimum of the input
1051 [0] range must be entered here.
(User defined minimum
1101 display value) Notes
This parameter is only visible if

the parameter "Type" (╚═▷
1000/╚═▷ 1050/╚═▷ 1100) is
configured to "Linear".
1002 User defined max. 2 -21000000.00 to 21000000.00 The value (y-axis) to be displayed
display value for the maximum of the input
1052 [2000] range must be entered here.
(User defined maximum
1102 display value) Notes


4 Configuration
[Default]
1000/╚═▷ 1050/╚═▷ 1100) is

1039 Sender value at 2 0.000 to 2000.000 The value (x-axis) of the

display min. configured input range, which
1089 [0.000] shall correspond with the
(Sender value at display minimum value configured for the
1139 minimum) display, must be entered here.
This specifies the lower limit of
the hardware range to be
measured.
Example
If the input range is 0 to 20 mA

and the value configured here is
4, an analog input value of 4 mA
would correspond with the
minimum value configured for the
display.
Notes

1000/╚═▷ 1050/╚═▷ 1100) is
1040 Sender value at 2 0.000 to 2000.000 The value (y-axis) of the

display max. configured input range, which
1090 [20000.00] shall correspond with the
(Sender value at display maximum value configured for the
1140 maximum) display, must be entered here.
This specifies the upper limit of
the hardware range to be
measured.
Example
If the input range is 0 to 20 mA

and the value configured here is
20, an analog input value of 20
mA would correspond with the
maximum value configured for the
display.
Notes

1000/╚═▷ 1050/╚═▷ 1100) is
Tab. 49: Analog Inputs 1 to 3 settings

4 Configuration
☼ Example: Hardware range 4 to 20 mA mapped to 0 to 1000 display value
Fig. 149: Analog Input Mapping
[Default]
1020 Sender type 2 The software in the control unit

may be configured for various
1070 types of sensors. The configurable
ranges apply to the linear analog
1120 input.
[0 to 2000 Ohms] The measuring range of the

analog input is 0 to 2000 Ohms.
0 to 20 mA The measuring range of the

analog input is 0/4 to 20 mA.
0 to 1 V The measuring range of the

analog input is 0 to 1 V.
Notes
If parameter "Type" (╚═▷

1000/╚═▷ 1050/╚═▷ 1100) is set
to "VDO xx" or "Pt100", this
parameter must be configured to
"0 to 2000 Ohm"!
1046 Offset 2 -20.0 to 20.0 Ohms The resistive input (the "0 to 2000
Ohms" analog input) may be
1096 [0.0 Ohm] calculated with a permanent
offset to adjust for inaccuracies.
1146
If the offset feature is utilized, the
value configured in this parameter

4 Configuration
[Default]
will be added to/subtracted from

the measured resistive value.
This has the following effect to the

measured values (please note
tables in ╚═▷ “9.1.2 VDO Inputs
Characteristics”):
Notes

the parameter "Sender type" (╚═▷
1020/╚═▷ 1070/╚═▷ 1120) is
configured to "0 to 2000 Ohms".
VDO temperature and pressure

senders use the ± range in
different ways! Please take care
for sender documentation.
1035 Exponent for protocol 2 -2 to 3 This is the exponent to adapt the

decimal place of the actual value
1085 [0] (parameter 1033/1083/1133) for
the protocol format.
1135
Example
Exponent is 3:
value of analog input {½/3} x 103

= value of analog input {½/3} x
1000
1033 Analog input {X} (displayed only) Current scaled value of the AI {X}
1003 Monitoring wire 2 The respective analog input can

break be monitored for wire breaks.
1053
If this protective function is
1103 triggered, the display indicates
"Wb: {Text of Parameter
[Description]}" (parameter ╚═▷
1025/╚═▷ 1075/╚═▷ 1125).
The following configurations are

used to monitor for wire breaks:
[Off] No wire break monitoring is

performed.
High If the actual value rises over the

maximum value (overshoot), this
is identified as a wire break.
Low If the actual value falls below the

minimum value (undershoot), this
is identified as a wire break.
High/Low If the actual value rises over the

maximum value (overshoot) or
falls below the minimum value
(undershoot), this is identified as a
wire break.
Notes
Monitoring of the analog inputs

(overrun/underrun) must be
configured manually to the

4 Configuration
[Default]
flexible limits (╚═▷ “4.5.5 Flexible

Limits”).
If the control unit detects that the

measuring range for an analog
input has been exceeded and an
alarm is issued, the limit value
monitoring of this analog input is
disabled and an error message is
displayed.
The measuring range is

recognized as being exceeded and
an alarm is issued:
• 0 to 20 mA:
Minimum value 2 mA
Undershooting
Maximum value 20.5 mA

Overshooting
• 0 to 2000 Ohms:
Minimum value 20 Ohms

Undershooting (Offset =
0 Ohm)
Maximum value 2040 Ohms

Overshooting (Offset =
0 Ohm)
• 0 to 1 V:
No wire break monitoring
Resistive sender type only:
Depending on what was

configured for the offset value
(parameter ╚═▷ 1046/╚═▷
1096/╚═▷ 1146) the displayed
value may be shifted.
This may result in a broken wire

being recognized early or later
than the actual value being
measured. (An offset of +20 Ohms
will recognize a wire break at 40
Ohms instead of 20 Ohms.)
A wire break is indicated in ToolKit

by displaying an analog input
value "Error".
1004 Wire break alarm 2 Each limit may be assigned an

class independent alarm class that
1054 specifies what action should be
taken when the limit is surpassed.
1104
A/[B] Warning alarm classes
C/D/E/F Shutdown alarm classes
Control Signal to issue a control command

only
Notes

4 Configuration
[Default]

wire break monitoring (parameter
╚═▷ 1003/╚═▷ 1053/╚═▷ 1103) is
not set to "Off"
For additional information refer to

╚═▷ “9.5.4 Alarm Classes”.
1005 Self acknowledge 2 Yes The control automatically clears

wire break the alarm if the fault condition is
1055 no longer detected.
1105 [No] The control does not automatically

output "External
Notes
This parameter is only visible wire

break monitoring (parameter ╚═▷
1003/╚═▷ 1053/╚═▷ 1103) is not
set to "Off"
10113 Filter time constant 2 Off, 1 to 5 A low pass filter may be used to
for reduce the fluctuation of an
10114 analog input reading.
0/4 to 20 mA and 0 to
10116 1V The cut-off-frequency is defined as
usual with 63% (e-1).
Off The analog input is displayed

without filtering.
1 Cut-off-frequency = 7.96 Hz (filter

time constant = 0.02 s)

[3] Cut-off-frequency = 1.99 Hz (filter



Filter time constant 2 Off, 1 to 5 A low pass filter may be used to

for reduce the fluctuation of an
analog input reading.
0 to 2000 Ω
The cut-off-frequency is defined as
usual with 63% (e-1).
Off Cut-off-frequency = 0.64 Hz (filter



4 Configuration
4.4.2.5 Analog Outputs
[Default]

[3] Cut-off-frequency = 0.08 Hz (filter



time constant = 8.0s)
1034 Unit 2 up to 6 characters text This parameter is assigning a unit

text to the displayed analog value.
1084 [______]
Notes
1134
configured using ToolKit.
If »°C« or »bar« is assigned the

unit will be converted into "F" or
"psi" automatically if the
corresponding parameter for
conversion ╚═▷ 3630 and/or ╚═▷
3631 is configured to YES.

39 but depends on numbers of
Bytes for each character. The
Bytes/character are defined by the
font of the currently selected
language.
Up to six characters are

best for display/HMI; more will
override screen border/frame.
display for best view!
3632 Bargraph minimum 2 -21000000.00 to 21000000.00 The start value for the bar graph
display of the analog input is
3634 [0] defined here. The value must be
entered according to the display
3636 format, which refers to the analog
input type (parameter ╚═▷ 1000).
3633 Bargraph maximum 2 -21000000.00 to 21000000.00 The end value for the bar graph
display of the analog input is
3635 [2000] defined here. The value must be
entered according to the display
3637 format, which refers to the analog
input type (parameter ╚═▷ 1000).
Tab. 50: Analog Inputs 1 to 3 sender settings
4.4.2.5 Analog Outputs
4.4.2.5.1 Analog Outputs 1 and 2
The analog outputs AO 1 and AO 2 may either be configured as analog or PWM outputs.
The analog outputs are prepared for speed and voltage biasing signal for a speed
controller and voltage regulator.

4 Configuration
• The following table shows two configuration examples with parameters and default
values for the analog outputs 1 and 2.
• Example 1 at AO 1 is for a generator active power output at AO 1 with a range of

-20 kW to 220 kW via a 4 to 20 mA signal (generator rated power = 200 kW).
• Example 2 at AO 2 is assigning the speed bias signal (0 to 100%) to PWM signal (0 to

100%) with level 6 V.
☼ Configuration examples
Example 1 with AO 1 Example 2 with AO 2

Parameter / AnalogManager
ID ID Value
Selected hardware type 5201 mA 5215 PWM

(For details refer to ╚═▷ Tab. )
Minimum hardware level 5208 4 5222 0.00 (%)
Maximum hardware level 5209 20 (mA) 5223 100.00 (%)
PWM output level 5210 — 5224 6V

(visible only if »PWM« selected)
Source value at minimum level 5204 -20 (kW) 5218 0(%)
Source value at maximum level 5206 220 (kW) 5220 100 (%)
Filter time constant 5203 3 5217 Off
AM Data source AO1 5200 Type: Pass through 5214 Type: Pass through
A1 = 01.74 Gen. A1 = 11.03 Speed
act. power [W] bias [%]
Analog output 1 10310 Display of resulting 10311 Display of resulting

value value

4 Configuration
☼ Settings/setup example
The following drawing shows the relation between the value of the AO signal selected
and its corresponding values at the terminal pin. For settings see table below the
drawing.
Fig. 150: Example to setup AO for 0 to 1000 IN becomes OUT 4 to 20 mA
Example 3 with AO 1
Parameter / AnalogManager
ID
Selected hardware type 5201 mA

(For details refer to ╚═▷ Tab. )
Minimum hardware level 5208 4
Maximum hardware level 5209 20 mA
PWM output level 5210 —

(visible only if »PWM« selected)
Source value at minimum level 5204 0
Source value at maximum level 5206 1000
Filter time constant 5203 3
AM Data source AO1 5200 Type: Pass through

A1 = analog signal with range 0
to 1000
Analog output 1 10310 Display of resulting value
[Default]

4 Configuration
5200 AM Data source ... 2 Determined by AnalogManager The data source may be selected
93.01, 93.02 from the available data sources.
5214
AO1: [A1 = 11.03 Speed bias Notes
(%)]
AO2: [A1 = 11.02 Voltage bias AM” for a list of all data sources.
(%)]
5201 Selected hardware 2 This parameter is used to

type configure the appropriate type of
5215 analog controller signal. The range
of the analog output is configured
here.
PMW value is defined in %.
Off No analog output signal will be

issued.
[mA] Notes
V Because of different isolation

purposes the two biasing outputs
PWM must be clear labeled with their
function.
5208 Minimum hardware 2 -20.00 to 100.00 The value of the configured

level hardware range, which shall
5222 [0.00] correspond with the configured
(User defined minimum minimum source value, must be
output value) entered here (y-axis). This
specifies the minimum limit of the
hardware range.
Example
If the value configured here is 2.5,

the maximum output range of
+/-20 mA / +/-10 V has a lower
limit of 2.5 mA / 2.5 V.
Notes
Value »100« is possible only for

PWM.
5209 Maximum hardware 2 -20.00 to 100.00 The value of the configured

(User defined maximum maximum source value, must be
output value) entered here (y-axis). This
specifies the maximum limit of the
hardware range.
Example
f the value configured here is 7.5,

+/-20 mA / +/-10 V has a upper
Notes
Value »100« is possible only for

PWM.

4 Configuration
5210 PWM output level 2 0.00 to 10.00 V If PWM has been enabled in
parameter ╚═▷ 5203/╚═▷ 5217, is
5224 [10.00 V] defined in %, and the level of the
PWM signal (amplitude) may be
adjusted here.
5204 Source value at 2 -21000000.00 to 21000000.00 The value from the data source
minimum level must exceed the value configured
5218 [0] here to raise the output signal
above minimum hardware level.
Negative percentage values may
be used to change the sign, e.g.
for power.
The entry format of the value

depends on the selected data
source.
5206 Source value at 2 -21000000.00 to 21000000.00 If the value from the data source
maximum level reaches the value configured here,
5220 [10000] the output signal will reach
maximum hardware level.
Negative percentage values may
for power.

source.
5203 Filter time constant 2 Off, 1 to 7 A filter time constant may be used
to reduce the fluctuation of an
5217 analog output value.
[Off] The analog output is displayed

without filtering.







Notes
The filter is not applied to the

analog output display value, i.e.
the end value of the analog output
is displayed immediately.

4 Configuration
4.4.2.6 External Analog Inputs
General notes
Configuration of these external analog inputs is performed similarly to the internal analog
inputs.
If an external expansion board (e.g. Phoenix Contact or WAGO) is connected to the

easYgen via the CAN bus, it is possible to use 16 additional analog inputs.
• Refer to ╚═▷ Tab. for the parameter IDs of the parameters for external analog inputs
1 through 16.
Please note that the available options for the parameters "Type" and "Sender type" differ
from the internal analog inputs.
The parameters "Offset" and "Monitoring wire break" are not available for the external
analog inputs.
• Refer to the Parameter List for details.
A wire break or sender failure is indicated by a dedicated value sent via the CAN bus
(╚═▷ “4.7.4.1 CAN Interface 1”).
For an example for the configuration of external analog inputs refer to ╚═▷ “6.3.10 Setup
Expansion Modules at CAN 2”.
Monitoring of the analog inputs (overrun/underrun) must be configured manually to the

flexible limits (╚═▷ “4.5.5 Flexible Limits”).
External analog inputs - parameter IDs
Parameter AI 1 AI 2 AI 3 AI 4 AI 5 AI 6 AI 7 AI 8
external
Description 16203 16213 16223 16233 16243 16253 16263 16273
Type1 5851 5864 5877 5890 5903 5916 5929 5942
User 5852 5865 5878 5891 5904 5917 5930 5943

defined
min
display
value
User 5853 5866 5879 5892 5905 5918 5931 5944

defined
max
display
value
Sender 5857 5870 5883 5896 5909 5922 5935 5948

value at

4 Configuration
external
display
min.
Sender 5858 5871 5884 5897 5910 5923 5936 5949

value at
display
max.
Sender 5856 5869 5882 5895 5908 5921 5934 5947

type
Sender 5859 5872 5885 5898 5911 5924 5937 5950

connection
type
Filter time 5863 5876 5889 5902 5915 5928 5941 5954
constant
Exponent 16204 16214 16229 16234 16244 16254 16264 16274

for
protocol
Wire break 5854 5867 5880 5893 5906 5919 5932 5945
alarm
class
Self 5855 5868 5881 5894 5907 5920 5933 5946

acknowledge
wire break
Unit 16208 16218 16228 16238 16248 16528 16268 16278
Bargraph 5861 5874 5887 5900 5913 5926 5939 5952

minimum
Bargraph 5862 5875 5888 5901 5914 5927 5940 5953

maximum
external
Description 16283 16293 16303 16313 16323 16333 16343 16353
Type 5955 5968 5981 6930 6943 6956 6969 6982
User 5956 5969 5982 6931 6944 6957 6970 6983

defined
min
display
value
User 5957 5970 5983 6932 6945 6958 6971 6984

defined
max
display
value
Sender 5961 5974 5987 6936 6949 6962 6975 6988

value at
display
min.
Sender 5962 5975 5988 6937 6950 6963 6976 6989

value at
display
max.
Sender 5960 5973 5986 6935 6948 6961 6974 6987

type

4 Configuration
external
Sender 5963 5976 5989 6938 6951 6964 6977 6990

connection
type
Filter time 5967 5980 5993 6942 6955 6968 6981 6994
constant
Exponent 16284 16294 16304 16314 16324 16334 16344 16354

for
protocol
Wire break 5958 5971 5984 6933 6946 6959 6972 6985
alarm
class
Self 5959 5972 5985 6934 6947 6960 6973 6986

acknowledge
wire break
Unit 16288 16298 16308 16318 10390 10392 10394 10396
Bargraph 5965 5978 5991 6940 6953 6966 6979 6992

minimum
Bargraph 5966 5979 5992 6941 6954 6967 6980 6993

maximum
External analog inputs – example configuration analog input 1
Please make sure that the selected settings you are using are supported by your external
devices.
Available "Type"s
(parameters 5851, 5864, ...)
Off Table A Pt DIN(R0)
Linear Table B Pt SAMA(R0)
TC Type K Ni DIN(R0)
TC Type J Ni SAMA(R0)
TC Type E Cu10
TC Type R Cu50
TC Type S Cu53
TC Type T Ni 1000(Landis)
TC Type B Ni 500(Viessm.)
TC Type N KTY 81-110
TC Type U KTY 84
TC Type L
TC Type C
TC Type W
TC Type HK

4 Configuration
4.4.2.7 External Analog Outputs
Available "Sender type"s
(parameters 5856, 5869, ...)
0 - 10 V R0=100
±10 V R0=10
0 - 20 mA R0=20
±20 mA R0=30
4 - 20 mA R0=50
0 - 400 Ohms R0=120
0 - 4000 Ohms R0=150
Thermocouple R0=200
R0=240
R0=300
R0=400
R0=500
R0=1000
R0=1500
R0=2000
R0=3000
Available "Sender connection type"s
(parameters 5859, 5872, ...)
Two wire
Three wire
If an external expansion board (e.g. from Phoenix Contact or WAGO) is connected to the
easYgen via the CAN bus, it is possible to use 4 additional analog outputs.
The configuration of these external analog outputs is performed similarly to the internal
analog outputs.
Refer to ╚═▷ Tab. 51 for the parameter IDs of the parameters for external analog outputs
1 through 4.
Please note that the available options for the Selected hardware type are limited. Refer
to the Parameter List for details.
Parameter Ext. AO 1 Ext. AO 2 Ext. AO 3 Ext. AO 4
Data source ext. 10237 10247 10257 10267

AO {x}
AnalogManager: [Pass Through of 11.03 Speed bias (%)]

4 Configuration
Parameter Ext. AO 1 Ext. AO 2 Ext. AO 3 Ext. AO 4
Source value at 10240 10250 10260 10270

minimum level
Source value at 10241 10251 10261 10271

maximum level
Filter time 10239 10249 10259 10269

constant
Selected hardware 10238 10248 10258 10268

type
Setting range: [Off]; mA; V
Minimum hardware 10242 10252 10262 10272

level
Maximum 10243 10253 10263 10273

hardware level
Ext. analog output 10245 10255 10265 10275

{x}
(displayed in
ToolKit only: ON/
OFF)
Notes:
Refer to ╚═▷ Chapter 4.4.2.7 for details and definition of the parameters.
Tab. 51: External analog outputs {1 to 4} - parameter IDs
[Default]
10237 Data source ... 2 Determined by AnalogManager The data source may be selected
93.21 .. 93.24 from the available data sources.
10247
AO1 to AO 4: [A1 = 11.03 Speed Notes
10257 bias (%)]
10267 AM” for a list of all data sources.
10238 Selected hardware 2 This parameter is used to

type configure the appropriate type of
10248 analog controller signal. The range
of the analog output is configured
10258 here.
10268 Off No analog output signal will be

issued.
[mA]
10242 Minimum hardware 2 0.00 to 20.00 The value of the configured

(User defined minimum minimum source value, must be
10262 output value) entered here (y-axis). This
specifies the minimum limit of the
10272 hardware range.

4 Configuration
Example
If the value configured here is 2.5,

+/-20 mA / +/-10 V has a lower
10243 Maximum hardware 2 0.00 to 20.00 The value of the configured

(User defined maximum maximum source value, must be
10263 output value) entered here (y-axis). This
specifies the maximum limit of the
10273 hardware range.
Example
f the value configured here is 7.5,

+/-20 mA / +/-10 V has a upper
10240 Source value at 2 -21000000.00 to 21000000.00 The value from the data source
minimum level must exceed the value configured
10250 [0] here to raise the output signal
above minimum hardware level.
10260 Negative percentage values may
10270 for power.

source.
10241 Source value at 2 -21000000.00 to 21000000.00 If the value from the data source
maximum level reaches the value configured here,
10251 [10000] the output signal will reach
maximum hardware level.
10261 Negative percentage values may
10271 for power.

source.
10239 Filter time constant 2 Off, 1 to 7 A filter time constant may be used
to reduce the fluctuation of an
10249 analog output value.
10259 [Off] The analog output is displayed

without filtering.
10269





4 Configuration
4.4.2.8 External Discrete Inputs


Notes
The filter is not applied to the

analog output display value, i.e.
the end value of the analog output
is displayed immediately.
4.4.2.8 External Discrete Inputs
If a Woodward IKD 1 or other external expansion board (e.g. Phoenix Contact or WAGO) is
connected to the easYgen via the CAN bus, it is possible to use 32 additional discrete
inputs.
• The configuration of these external DIs is performed similarly to the internal DIs
(╚═▷ “4.4.2.2 Discrete Inputs”).
• Refer to ╚═▷ Tab. 52 for the parameter IDs of the parameters for external DIs 1
through 32.
External DI 1 DI 2 DI 3 DI 4 DI 5 DI 6 DI 7 DI 8
Description 16200 16210 16220 16230 16240 16250 16260 16270
Delay 16000 16010 16020 16030 16040 16050 16060 16070
Operation 16001 16011 16021 16031 16041 16051 16061 16071
Alarm class 16002 16012 16022 16032 16042 16052 16062 16072
Self acknowledge 16004 16014 16024 16034 16044 16054 16064 16074
Enabled 16003 16013 16023 16033 16043 16053 16063 16073
Tab. 52: External discrete inputs - parameter IDs 1..8
Description 16280 16290 16300 16310 16320 16330 16340 16350
Delay 16080 16090 16100 16110 16120 16130 16140 16150
Operation 16081 16091 16101 16111 16121 16131 16141 16151
Alarm class 16082 16092 16102 16112 16122 16132 16142 16152
Enabled 16083 16093 16103 16113 16123 16133 16143 16153
Description 16201 16211 16221 16231 16241 16251 16261 16271
Delay 16005 16015 16025 16035 16045 16055 16065 16075

4 Configuration
4.4.2.9 External Discrete Outputs
Operation 16006 16016 16026 16036 16046 16056 16066 16076
Alarm class 16007 16017 16027 16037 16047 16057 16067 16077
Enabled 16008 16018 16028 16038 16048 16058 16068 16078
Description 16281 16291 16301 16311 16321 16331 16341 16351
Delay 16085 16095 16105 16115 16125 16135 16145 16155
Operation 16086 16096 16106 16116 16126 16136 16146 16156
Alarm class 16087 16097 16107 16117 16127 16137 16147 16157
Enabled 16088 16098 16108 16118 16128 16138 16148 16158
4.4.2.9 External Discrete Outputs
If a Woodward IKD 1 or other external expansion board (e.g. Phoenix Contact or WAGO) is
connected to the easYgen via the CAN bus, it is possible to use 32 additional discrete
outputs.
The configuration of the external DOs is performed in a similar way like for the internal
DOs.
Refer to ╚═▷ Tab. 56 for the parameter IDs of the parameters for external discrete
outputs 1 through 32.
External DO 1 DO 2 DO 3 DO 4 DO 5 DO 6 DO 7 DO 8
Parameter 12330 12340 12350 12360 12370 12380 12390 12400

ID
Tab. 56: External discrete outputs - parameter IDs (1 to 8)
Parameter 12410 12420 12430 12440 12450 12460 12470 12480

ID
Parameter 12331 12332 12333 12334 12335 12336 12337 12338

ID

4 Configuration
4.4.3 Configure Breakers
Parameter 12339 12341 12342 12343 12344 12345 12346 12347

ID
4.4.3 Configure Breakers
General notes
The assignment of the defined relays to defined functions occurs by selection of the
application mode (i.e. function "Command: Close GCB" on relay [R 6], this relay can no
longer be operated via the LogicsManager).
The same way some relays are designated to specific functions, others may be assigned
to different functions. These are listed as "programmed" relays. If a relay is
"programmable" the function may be assigned to other relays via the LogicsManager by
configuration.
For additional information refer to ╚═▷ “4.4.2.3 Discrete Outputs (LogicsManager)”.
measuring inputs must be connected. If an external mains decoupling is performed,
jumpers between busbar and mains voltage measuring inputs may be installed.
Changing the application mode will not change other configured values in the
parameters. The application mode parameter is the only one.
Operation of the circuit breakers
The configuration of pulse switching takes place in the following screen and has the
described effect on the signal sequence (the MCB cannot be controlled by the continuous
pulse for security reasons, because otherwise, the MCB would be opened in case of a
failure/exchange of the easYgen).
The parameter "Enable MCB" allows/prevents the closing of the MCB. A closed MCB will
not be opened.
If the parameter "Auto unlock" is configured to YES, an open pulse will be issued prior to
each close pulse.
External breaker handling
In operation mode AUTO the easYgen operates its breakers automatically according to
the configured application and transition modes. Actually the breaker transition mode
“external” would only allow the breaker closure from external. On the other hand the
easYgen allows in special cases the closure of breaker from external, when the following
configurations and modes are fulfilled:

4 Configuration
4.4.3.1 Good to know: Actions with Breakers
External Breaker Synchronizat‐ Dead Bus Condition for the closure acceptance
Handling ion Mode Closure
GCB Synchronization Off -

• The start request in automatic is
GCB Dead bus closure - Off active
• The generator is in operating range
• The engine start procedure is expired
MCB Synchronization Off - The mains is in operating range
GCB Dead bus closure - Off
4.4.3.1 Good to know: Actions with Breakers
4.4.3.1.1 Dead Bus Closing GCB
The following applies to application modes A03 and A04 .
The unit closes the GCB without synchronization, if the following conditions are met. The
display indicates "GCB dead bus close".
Automatic operation
• The operating mode AUTOMATIC has been selected
• No class C alarm or higher is present
• The engine is running
• The engine delayed monitoring (parameter ╚═▷ 3315) as well as the generator
stable time (parameter ╚═▷ 3415) have been expired or the LogicsManager function
"Undelay close GCB" (parameter ╚═▷ 12210) is enabled
• The generator voltage and frequency are within the configured operating range (╚═▷
“4.5.1.1 Generator Operating Ranges: Voltage / Frequency / Busbar”)
• The MCB has been opened for at least the time configured in "Transfer time
GCB↔MCB" (parameter ╚═▷ 3400)
(Mode A04 with open transition mode only)
• The function "Start without load" (parameter ╚═▷ 12540) has been disabled through
the LogicsManager
• Only in critical mode: the parameter "Close GCB in override" (parameter ╚═▷ 4100)
is configured to "Yes"
• The busbar voltage is below the dead bus detection limit (parameter ╚═▷ 5820)
• There is no other GCB closed in the same segment
• There is no other device with a smaller device ID willing to close its GCB too (Dead
busbar closure negotiation)
Manual operation
• The operating mode MANUAL has been selected.

4 Configuration
4.4.3.1.2 Synchronization GCB/MCB
• No class C alarm or higher is present.
• The engine is running.
• The engine delayed monitoring (parameter ╚═▷ 3315) as well as the generator
stable time (parameter ╚═▷ 3415) have been expired.
• The generator voltage and frequency are within the configured operating range (╚═▷
“4.5.1.1 Generator Operating Ranges: Voltage / Frequency / Busbar”).
• The button "Close GCB" has been pressed.
• The MCB has been open for at least the time configured in "Transfer time GCB↔MCB"
(Mode A04 with open transition mode only)
• The busbar voltage is below the dead bus detection limit (parameter ╚═▷ 5820).
• There is no other GCB closed in the same segment.
• There is no other device with a smaller device ID willing to close its GCB too (Dead
busbar closure negotiation).
Dead Busbar Negotiation
Each easYgen, who intends to close its GCB on a dead busbar publishes a “Dead busbar
closure request” flag over CANbus and reads back whether there is any other easYgen
publishing the same intension:
If not, the unit waits an estimated time for security and then closes its breaker.
If yes, the unit compares its own device number with the smallest device number of all
others who also intend to close. If the own device number is smaller than the rest, the
unit will close its breaker - otherwise it blocks its own closure.
The easYgen removes its wish to close its GCB on a dead busbar, if the GCB closure
failure occurs in a multiple generator application. So the next easYgen with the higher
device number gets the permission for closure.
The load sharing messages are monitored. In case of a “missing member” alarm on the
load share bus, the single dead bus closures are delayed depending on the own
Generator number to avoid simultaneous closure. The delay time is Generator Number
multiplied with 500 ms.
The GCB dead busbar closure is realized faster, if LogicsManager "Undelayed close GCB"
ID 12210 is set to TRUE.
The dead busbar negotiation is going over segments.
The following applies to application modes A03 and A04 .
The synchronization is active, if the following conditions are met simultaneously.

4 Configuration
The display indicates "Synchronization GCB" or "Synchronization MCB".
Automatic operation
• The mains voltage is available and within the configured operating range (╚═▷
“4.5.3.3 Mains Operating Ranges”)
• The generator and busbar voltage are available and within the configured operating
range (╚═▷ “4.5.1.1 Generator Operating Ranges: Voltage / Frequency / Busbar”)
• The differential frequency/voltage is within the configured operating range
• Synchronizing the MCB
◦ The GCB is closed (or at least one GCB is closed in a multiple genset
application)
◦ The busbar voltage is within the configured operating range
◦ The "Enable MCB" (parameter ╚═▷ 12923) signal is present, for example
discrete input 6 is energized if configured as DI 6
• Synchronizing the GCB
◦ The MCB is closed
◦ Engine delayed monitoring (parameter ╚═▷ 3315) and generator stable time
(parameter ╚═▷ 3415) have expired or "Undelay close GCB" (parameter ╚═▷
12210) is enabled
Manual operation
• Operating mode MANUAL has been selected
• The generator and busbar voltage are available and within the configured operating
range (╚═▷ “4.5.1.1 Generator Operating Ranges: Voltage / Frequency / Busbar”)
• The differential frequency/voltage is within the configured operating range
• Synchronizing the MCB
◦ The GCB is closed (or at least one GCB is closed in a multiple genset
application)
◦ The "Enable MCB" (parameter ╚═▷ 12923) signal is present, for example
discrete input 6 is energized if configured as DI 6
◦ The button "Close MCB" has been pressed
• Synchronizing the GCB
◦ The MCB is closed

4 Configuration
4.4.3.1.3 Dead Bus Closing MCB
◦ Engine delayed monitoring (parameter ╚═▷ 3315) and generator stable time
(parameter ╚═▷ 3415) have expired or "Undelay close GCB" (parameter ╚═▷
12210) is enabled
◦ The button "Close GCB" has been pressed
4.4.3.1.3 Dead Bus Closing MCB
The following applies to application mode A04 .
The unit closes the MCB, if the following conditions are met simultaneously.
The display indicates "MCB dead bus close".
Automatic operation
• The parameter "Dead busbar closure MCB" (parameter ╚═▷ 3431) is configured On
• The GCB is open or has been opened for at least the "Transfer time GCB↔MCB"
(parameter ╚═▷ 3400) (open transition mode only)
• The "Enable MCB" (parameter ╚═▷ 12923) signal is present, for example discrete
input 6 is energized if configured as DI 6
Manual operation
• Operating mode MANUAL has been selected
• The parameter "Dead busbar closure MCB" (parameter ╚═▷ 3431) is configured "On"
• The GCB is open or has been opened for at least the "Transfer time GCB↔MCB"
(parameter ╚═▷ 3400) (open transition mode only)
• The "Enable MCB" (parameter ╚═▷ 12923) signal is present, for example discrete
input 6 is energized if configured so
• The button "Close MCB" has been pressed

4 Configuration
4.4.3.1.4 Open GCB
4.4.3.1.4 Open GCB
The following applies to application modes A02 , A03 and A04 .
The GCB will be opened when the "Command GCB open" is issued. The behavior of the
GCB open relay depends on the setting of parameter ╚═▷ 3403.
If this parameter is configured as "N.O.", the relay energizes to open the GCB, if it is
configured as "N.C.", the relay de-energizes to open the GCB.
The GCB will be opened under the following conditions:
• In STOP operating mode after unloading the generator
• In case of a class C alarm or higher
• By pressing the "GCB" or "MCB" softkey (depending on the CB logic which has been
set) in MANUAL operating mode
• By pressing the button "stop engine" in MANUAL operating mode
• In the event of an automatic stopping in the AUTOMATIC operating mode (the start
request has been terminated or a stop request has been initiated)
• In critical mode (Sprinkler operation), provided that an emergency power operation

is not active, and "Close GCB in override" (parameter ╚═▷ 4100) has been configured
to No
• If "Start without load" has been enabled through the LogicsManager and the breaker
was closed
• By pressing the "MCB" softkey (depending on the CB logic which has been set) in
MANUAL operating mode
The conditions above are only valid if the GCB is closed, whereas the following conditions
are valid regardless of the GCB is open or closed.
• Prior to the MCB closing onto the dead busbar (depending on the CB logic which has
been set)
• In case of an alarm of class D or F
4.4.3.1.5 Open MCB
The following only applies to application mode A04 .
The MCB will be opened when the relay "Command: MCB open" is energized.
The MCB will be opened under the following conditions if the MCB is closed:

4 Configuration
4.4.3.1.6 Transition Modes (Breaker Logic)
• If an emergency power operation is initiated (mains failure) once the generator

voltage is within the permissible limits
• Prior to the closure of the GCB (depending on the CB logic which has been set)
• Upon pressing the "MCB" or "GCB" softkey (dependent upon the configured CB logic)
in MANUAL operating mode
Breaker logic "PARALLEL"
Parallel operation is enabled by configuring parameter ╚═▷ 3411 to "PARALLEL".
Parallel breaker logic must be selected for the following operation modes:
• islanded operation
• Mains parallel operation
In the event of an engine start request the following occurs:
• The GCB is synchronized and closed
• The generator assumes load and the adjusted real power or reactive power setpoints
are controlled
Following the stop request the following occurs:
• The generator sheds load until real power has reached the "Unload limit"
• The generator power factor is controlled to "1.00" (unity)
• The GCB is opened
• The engine is shut down following the configured cool down period
When a stop command is issued to the engine, soft loading (power reduction) is carried
out before opening the GCB, except an alarm of class D or F is present.
Breaker logic "INTERCHANGE"

4 Configuration
For this breaker logic to function correctly, the mains power measurement must be
connected properly.
The following applies for the power display:
• Positive mains power = export power

• Negative mains power = import power
In the event of a start request, a change is made from mains to generator supply.
The following occurs:
• The GCB is synchronized and closed
• The generator assumes load until the imported mains interchange real power has
reached 5 % of the "Generator rated active power" (parameter ╚═▷ 1752)
• The MCB is opened
When a stop request has been issued, a change is made from generator to mains supply.
• The MCB is synchronized and closed
• The generator sheds load until real power has reached the "Unload limit"
• The generator power factor is controlled to "1.00" (unity)
The limit for opening the MCB during softloading (Unloading mains) is +/- 5% active
generator rated power without any delay. In multiple generator applications the 5% limit
is calculated out of the current nominal generator power in the system.
• One engine is running with 1000kW rated, the +/-5% limit is a power window at the
interchange point from 50kW import up to 50kW export.
• One engine is running with 500kW rated and another with 300kW rated, the +/-5%
limit is a power window at the interchange point from 40kW import up to 40kW
export.
Hint: The generator rated power is taken into account to find a good compromise
between bumpless power transfer and being not too long mains parallel.
Breaker logic "CLOSED TRANSIT."
Closed transition (make-before-break/overlap synchronization) is enabled by configuring

parameter ╚═▷ 3411 to "CLOSED TRANSITION".
In the event of an engine start request, a change is made from mains to generator supply.

4 Configuration
• The GCB is synchronized and closed.
• The MCB is opened and the generator assumes all loads.
After the engine stop request has been issued, a change is made from generator to mains
supply.
• The MCB is synchronized and closed.
• The GCB is opened and the mains assume all loads.
The circuit breakers are opened irrespective of the power.
For the application modes A04 , A06 and A12 , the breaker closed transition time matches
the duration time <100 ms.
The maximum time between the reply from the CB and the CB open command is 100 ms.
Breaker logic "OPEN TRANSIT."
Open transition (break-before-make/change over logic) is enabled via configuration of

parameter ╚═▷ 3411 to "OPEN TRANSITION".
In the event of an engine start request, a change is made from mains to generator supply.
• The MCB is opened
• The GCB is closed after the time configured in "Transfer time GCB<->MCB"
(parameter ╚═▷ 3400) has expired.
• The MCB is closed after the time configured in "Transfer time GCB<->MCB"
(parameter ╚═▷ 3400) has expired
Breaker logic "EXTERNAL"
External breaker logic is enabled via configuration of parameter ╚═▷ 3411 to "EXTERNAL".
All breaker control (especially the CB closing instructions) must be carried out via master
controller (e.g. a PLC).

4 Configuration
The easYgen controller always issues additionally the breaker open command under fault
conditions and in the breaker unloading states (Unloading GCB) if the stop request is
active.
Overview for application mode A04
STOP MANUAL AUTOMATIC
EXTERNAL: Breaker logic "External"
In a mains parallel operation, decoupling from the mains is carried out via the MCB or the GCB in the event of a mains
failure. The breakers will not automatically close in emergency power operation. Emergency power operation in
accordance with European Community Specification DIN VDE 0108 is not possible in this power circuit breaker logic.
The GCB is opened. The MCB and the GCB may be The GCB is opened if the genset is
manually opened. The circuit breakers stopped or if decoupling from the
are opened for decoupling from the mains, but will not close if the engine
mains. is started. The MCB is opened only if
decoupling from the mains, and is
never closed.
PARALLEL: Breaker logic "Mains parallel operation"
The MCB and GCB are synchronized to permit continuous mains parallel operation in this breaker logic mode.
The GCB is opened; the MCB is Mains parallel operation can be The GCB is synchronized via an add-on
operated depending on the setting of initiated by pressing the "GCB On" or request and a mains parallel operation
"Enable MCB" (parameter ╚═▷ 12923). "MCB On" push-button. is performed. When a shed-off request
is issued, the generator sheds load
and opens the GCB and the engine is
shut down following the configured
cool down period.
Emergency power: The emergency

power operation is terminated
following the expiration of the mains
settling time. The MCB is synchronized
and closed, putting the system back
into a mains parallel operation.
OPEN TRANSIT.: Breaker logic "Open transition / change-over / brake-before-make"
The MCB and GCB are never synchronized in this breaker logic mode.
The GCB is opened; the MCB is A change can be made to either A change is made to generator
operated depending on the setting of generator or mains operation by operation through an add-on request.
"Enable MCB" (parameter ╚═▷ 12923). pressing either the "GCB On" or "MCB Once the add-on request is
On" push-button. The "STOP" push- terminated, the system changes back
button opens the GCB and to mains operation. The MCB is closed
simultaneously stops the engine. when the busbar is dead, even if there
has not been an add-on request.
Emergency power operations are
terminated following the expiration of
the mains settling timer. The GCB
opens and the MCB closes,
transferring all loads to the mains.
CLOSED TRANSIT.: Breaker logic "Closed transition / make-before-brake / overlap synchronization"
The MCB and the GCB are synchronized, in order to avoid a dead busbar in this breaker logic mode. Immediately after the
synchronization of one breaker, the other is opened. Continuous mains parallel operation is not possible.
The GCB is opened; the MCB is Synchronization of either the The GCB is synchronized via an add-on
operated depending on the setting of generator or the mains can be request. After the GCB closes the MCB
"Enable MCB" (parameter ╚═▷ 12923). initiated by pressing the "GCB On" or is opened. Following the shed-off
"MCB On" push-button. request being issued, the MCB is
synchronized and closed. After the
MCB has closed the GCB is opened.


4 Configuration
4.4.3.2 General Breaker Settings

settling time and the MCB
synchronizing to the generator. The
MCB closes and the GCB opens
immediately afterwards.
INTERCHANGE: Breaker logic "Soft loading / interchange synchronization"
The MCB and the GCB are synchronized, in order to avoid a dead busbar in this breaker logic mode. The operation of a
breaker under load is avoided by utilizing the ability to soft load. Continuous mains parallel operation is not possible with
this breaker logic.
Following the shed-off request, the MCB synchronizes and closes, the generator soft unloads to the mains and the GCB
opens. After the GCB is open the engine is stopped following the expiration of the configured cool down period.
The GCB is opened; the MCB is Synchronization of either the Via an engine request, the GCB is
operated depending on the setting of generator or the mains can be synchronized and the generator power
"Enable MCB" (parameter ╚═▷ 12923). initiated by pressing the "GCB On" or is increased. The MCB is then opened.
"MCB On" push-button. Following the disabling of the engine
request, the MCB is reverse
synchronized and the GCB is then
opened.

settling time. The MCB closes, the load
is transferred, and the GCB opens.
Overview for application mode A03
PARALLEL: Breaker logic "Mains parallel"
This operation mode may be used both in the case of an islanded system, an islanded parallel system, and a system that
is operated in mains parallel.
The GCB is opened. Mains parallel operation can be The GCB is synchronized via an add-on
performed via the "GCB On" push- request and mains parallel operation
button. is performed.
When a shed-off request is issued, the

generator sheds load, the GCB is
opened, and the engine is shut down
following the configured cool down
period.
[Default]
3444 Application mode 2 The unit may be configured for

four different application modes.
The discrete inputs and relay
outputs are pre-defined
dependent upon the selected
application mode. Only the
screens and functions that pertain
to the application mode selected
are displayed. The single line

4 Configuration
diagram in the main screen will

change.
Refer to ╚═▷ “2.2 Application

Modes Overview” for additional
information.
None Application mode A01
The control unit will function as an

engine start/stop control with
generator and engine protection.
All necessary inputs and outputs
are assigned and pre-defined.
GCB open Application mode A02
The control unit will function as an

engine start/stop control with
The control unit can only open the
GCB. All necessary inputs and
outputs are assigned and pre-
defined.
GCB Application mode A03
The control unit will function as a

1 CB unit. The control unit
performs full control like
synchronizing, opening and
closing the GCB with generator
and engine protection. All
necessary inputs and outputs are
assigned and pre-defined.
[GCB/MCB] Application mode A04
The control unit will function as a

2 CB unit. The control unit
performs full control like
synchronizing, opening and
closing the GCB and the MCB with
The GCB/MCB perform also full
load transfer via open/closed
transition, interchange and
parallel mode. All necessary
inputs and outputs are assigned
and pre-defined.
3411 Breaker transition 2 The control unit automatically

mode controls the two breakers (MCB
and GCB).
External
Open Transition
Closed Transit.
Interchange
[Parallel]
Notes

application mode A04 .

4 Configuration
For a detailed explanation for

each mode refer to ╚═▷ “4.4.3.1.6
Transition Modes (Breaker Logic)”.
The unit provides two alternative

transition modes, which may be
activated temporarily via the
LogicsManager and override the
transition mode configured in this
parameter.

mode 1 controls the two breakers (MCB
and GCB).
External
Open Transition
Closed Transit.
Interchange
[Parallel]
Notes


12931 Transition mode 1 2 Determined by LogicsManager Once the conditions of the

86.93 LogicsManager have been fulfilled,
the transition mode configured in
[(0 & 1) & 1] parameter ╚═▷ 3412 will be used
instead of the standard transition
= 11922 mode configured in parameter
╚═▷ 3411.

Notes

Alternative transition mode 1 has

priority over alternative transition
mode 2, i.e. if both LogicsManager
functions (parameters ╚═▷ 12931
and ╚═▷ 12932) are TRUE, breaker
transition mode 1 (parameter ╚═▷
3412) will be used.

mode 2 controls the two breakers (MCB
and GCB).
External
Open Transition
Closed Transit.

4 Configuration
Interchange
[Parallel]
Notes


12932 Transition mode 2 2 Determined by LogicsManager Once the conditions of the

the transition mode configured in
[(0 & 1) & 1] parameter ╚═▷ 3412 will be used
instead of the standard transition
= 11923 mode configured in parameter
╚═▷ 3411.
Notes

Alternative transition mode 1 has

priority over alternative transition
mode 2, i.e. if both LogicsManager
functions (parameters ╚═▷ 12931
and ╚═▷ 12932) are TRUE, breaker
transition mode 1 (parameter ╚═▷
3412) will be used.

3400 Transfer time 2 1.00 to 99.99 s Switching from generator supply

GCB↔MCB to mains supply or from mains
[1.00 s] supply to generator supply occurs
automatically if the operating
conditions have been met.
The time between the reply

"power circuit breaker is open"
and a close pulse is set by this
parameter. This time applies for
both directions. During this time
the consumers are de-energized.
Notes

This is only valid, if parameter ╚═▷

3411 is configured to OPEN
TRANSITION

4 Configuration
4.4.3.3 Configure Breakers: GCB
General notes
Fig. 151: Normally Open contacts - schematic
Normally Open (N.O.) contacts
The relay (discrete output) must be energized to close the contact.
Fig. 152: Normally Closed contacts - schematic
Normally Closed (N.C.) contacts
The relay (discrete output) must be energized to open the contact.
[Default]
3403 GCB open relay 2 [N.O.] Normally open:
The relay "command: GCB open"

will be energized to open the GCB
and will be de-energized again
after the discrete input "Reply
GCB" is energized to signal the
control that the GCB is open.

4 Configuration
N.C. Normally closed:
The relay "command: GCB open"

will be de-energized to open the
GCB and will be energized again
after the discrete input "Reply
GCB" is energized to signal the
control that the GCB is open.
Not used A GCB open relay is not used and

relay R7 (Command: open GCB) is
freely programmable. In this case,
parameter ╚═▷ 3414 must be
configured to "Steady" to open the
breaker.
Notes

application mode A02 A03 A04 .
3414 GCB close command 2 Impulse The relay "Command: GCB close"
issues an add-on pulse. If the
relay is configured in this manner
a holding coil and sealing contacts
must be installed externally to the
control unit. The DI "Reply GCB" is
used to identify closed contacts.
[Steady] The relay "Command: close GCB"

may be wired directly into the
holding circuit for the power
circuit breaker. If this method is
utilized it is recommended that
isolation relays are used.
After the connect pulse has been

issued and the reply of the power
circuit breaker has been received,
the relay "Command: close GCB"
remains energized. If a class C
alarm or higher occurs or a GCB
open command is issued, this
relay de-energizes.
Notes
In both cases the relay

"Command: GCB open" energizes
to open the GCB if parameter ╚═▷
3403 is not configured as "Not
used".

application modes A03 and A04 .
3416 GCB time pulse 2 0.10 to 1.00 s The time of the pulse output may
be adjusted to the breaker being
[0.50 s] utilized.
Notes

5729 Synchronization GCB 2 [Slip frequency] The frequency controller adjusts

the frequency in a way, that the
frequency of the source

4 Configuration
(generator) is marginal greater

than the target (busbar). When
the synchronizing conditions are
reached, a close command will be
issued. The slipping frequency
depends on the setting of "Slip
frequency offset" (parameter ╚═▷
5502).
Phase matching The frequency controller adjusts

the phase angle of the source
(generator) to that of the target
(busbar), in view of turning the
phase difference to zero.
Notes

Notes
Regardless of breaker control, the values of 5700, 5701, 5702, 5703, 5704, 8824, and 8825 are important to
the sync-check relay function.
5700 Voltage differential 2 0.00 to 20.00% The maximum permissible voltage

GCB differential for closing the
[5.00%] generator circuit breaker is
configured here.
If the difference between

generator and busbar voltage
does not exceed the value
configured here and the generator
voltage is within the operating
voltage window (parameters ╚═▷
5800 and ╚═▷ 5801), the
"Command: GCB close" may be
issued.
Notes
This value refers to the generator

rated voltage (parameter ╚═▷
1766).

5701 Positive frequency 2 0.00 to 0.49 Hz The prerequisite for a close

differential GCB command being issued for the
[+0.18 Hz] GCB is that the differential
frequency is below the configured
differential frequency.
This value specifies the upper

frequency (positive value
corresponds to positive slip →
generator frequency is higher
than the busbar frequency).
Notes


4 Configuration
5702 Negative frequency 2 -0.49 to 0.00 Hz The prerequisite for a close

differential GCB command being issued for the
[-0.10 Hz] GCB is that the differential
frequency is above the configured
differential frequency.
This value specifies the lower

frequency limit (negative value
corresponds to negative slip →
generator frequency is less than
the busbar frequency).
Notes

5703 Maximum positive 2 0.0 to 60.0° The prerequisite for a close

phase angle GCB command being issued for the
[7.0°] GCB is that the leading phase
angle between generator and
busbar is below the configured
maximum permissible angle.
Notes


if parameter ╚═▷ 5729 is
configured to "Phase matching".
5704 Maximum negative 2 -60.0 to 0.0° The prerequisite for a close

phase angle GCB command being issued for the
[-7.0°] GCB is that the lagging phase
angle between generator and
busbar is below the configured
maximum permissible angle.
Notes


5707 Phase matching GCB 2 0.0 to 60.0 s This is the minimum time that the
dwell time generator voltage, frequency, and
[3.0 s] phase angle must be within the
configured limits before the
breaker will be closed.
Notes


8825 Phase angle 2 The phase angle between

compensation GCB generator voltage and generator
busbar voltage can be

4 Configuration
compensated according to an
installed power transformer
between generator and busbar.
On The compensation is active. The

phase will be compensated
according the value configured in
Notes
Measured values 181

'Ph.ang.busb1-gen.L12' and 184
'Ph.ang.mns.busb1 L12' are not
changed but the compensated
(╚═▷ 8824) values are taken for
synchronization control and
synchroscope display.
[Off] The compensation is inactive. The

phase angle is directly taken from
the measurement.
Notes
WARNING: Ensure the following

parameters are configured
correctly to prevent erroneous
synchronization settings. Incorrect
wiring of the system cannot be
compensated for with this
parameter!
Please check during initial

commissioning the phase angle
and the synchronization with a
zero voltmeter.
Recommendation: For safety

reasons, please mark the easYgen
with a label showing the
configured phase angle
compensation.
Refer to ╚═▷ “6.3.11 Phase Angle

Compensation” for details.
8824 Phase angle GCB 2 -180 to 180° The phase angle compensation
corrects the degree between
[0°] generator voltage and busbar
voltage. The configured degree is
added to the real measured phase
angle.
Visible only, if parameter 8825 is

"On".
Notes
Ensure correct configuration to

prevent erroneous synchronization
settings to avoid generator
destructive power. Incorrect
wiring cannot be compensated for
with this parameter!
3432 Dead bus closure GCB 2 [On] A dead busbar closure is allowed if
the required conditions are met.

4 Configuration
Off A GCB close command to a dead

busbar is prevented.
Synchronization is still possible.
Notes

15161 Inhibit dead bus 2 Determined by LogicsManager If active the dead bus closure of
closure GCB 87.74 the GCB can be inhibited.
[(0 & 1) & 1] Notes
= 11463 For information on the

3415 Generator stable 2 0 to 99 s The time configured here begins

time to count down once the »Engine
[2 s] monitoring delay timer« ╚═▷ 3315
has expired. This permits for an
additional delay time before the
breaker is closed in order to
ensure that none of the engine
delayed watchdogs trips.
It is possible to bypass this delay

time through the LogicsManager
(parameter ╚═▷ 12210) in the
event an emergency operation
condition (mains failure) occurs.
Unnecessary CB switching
operations and voltage
interruptions should be avoided by
utilizing this parameter.
Notes

After »Generator stable time« has

expired, then LM 03.08 »Breaker
del. exp. -Status« becomes TRUE.
12210 Undelay close GCB 2 Determined by LogicsManager Once the conditions of the
the GCB will be closed
[(04.09 Emergency mode & 1) immediately (without waiting for
& 1] engine speed delay and generator
stable timer to expire).
= 10711
When using the standard setting,
the GCB will be closed without
delay in emergency power
operation.
Notes

Usually the dead busbar

negotiation is started with
reaching the generator frequency

4 Configuration
and voltage operating window. But

during the function "undelayed
close GCB", the dead busbar
negotiation is executed from the
moment on the engine has
reached the firing speed.
Through starting the dead bus bar

negotiation earlier, the overall
time before closing the GCB can
be shorten.

12976 GCB open in MAN 2 Determined by LogicsManager With the rising edge of this
87.46 LogicsManager equation a GCB
open command in operating mode
[(0 & 1) & 1] MANUAL is initiated. The state
TRUE of this LM inhibits the GCB
= 11435 close command in MANUAL.
Notes


12977 GCB close in MAN 2 Determined by LogicsManager With the rising edge of this
87.47 LogicsManager equation a GCB
close command in operating mode
[(0 & 1) & 1] MANUAL is initiated.Precondition:
deactivated "GCB open in MAN"
= 11436
Notes


5705 Closing time GCB 2 40 to 300 ms The inherent closing time of the
GCB corresponds to the lead-time
[80 ms] of the close command.
The close command will be issued

independent of the differential
frequency at the entered time
before the synchronous point.
Notes

3405 GCB auto unlock 2 This is used for special circuit

breakers to put the GCB into a

4 Configuration
4.4.3.4 Configure Breakers: MCB
defined initial state or to enable

closing at all.
Yes Before every close-pulse, an open-

pulse is issued for defined
duration (parameter ╚═▷ 5708. A
CB close pulse is enabled only
after the open pulse is issued.
[No] The CB close pulse is enabled

without being preceded by a CB
open pulse.
Notes

5708 GCB open time pulse 2 1.00 to 10.00 s This time defines the length of the
GCB open time pulse, if the
[1.00 s] automatic switch unblocking GCB
is activated.
Notes

General notes
The following parameters are only applicable for application mode A04 .
[Default]
3417 MCB time pulse 2 0.10 to 0.50 s Breaker pulse duration to close
the MCB
[0.50 s]
The time of the pulse output may
be adjusted to the breaker being
utilized.
5730 Synchronization MCB 2 [Slip frequency] The frequency controller adjusts

the frequency in a way, that the
frequency of the source (busbar)
is marginal greater than the target
(mains). When the synchronizing
conditions are reached, a close
command will be issued. The
slipping frequency is positive to
avoid reverse power.
Phase matching The frequency controller adjusts

the phase angle of the source
(busbar) to that of the target

4 Configuration
(mains), in view of turning the

phase difference to zero.
Notes
Regardless of breaker control, the

values of 5710, 5711, 5712, 5713,
5714, 8841, and 8842 are
important to the sync-check relay
function.
5713 Max positive phase 2 0.0 to 60.0° The prerequisite for a connect
angle MCB command being issued for the
[7.0°] MCB is that the leading phase
(Maximum permissible angle between busbar and mains
positive phase angle is below the configured maximum
MCB) permissible angle.
Notes

5714 Max negative phase 2 -60.0 to 0.0° The prerequisite for a connect
angle MCB command being issued for the
[-7.0°] MCB is that the lagging phase
(Maximum permissible angle between busbar and mains
negative phase angle is below the configured maximum
MCB) permissible angle.
Notes

5710 Voltage differential 2 0.00 to 20.00% The maximum permissible voltage

MCB differential for closing the mains
[5.00%] circuit breaker is configured here.
Notes

1766) and mains rated voltage
If the difference between mains

and busbar voltage does not
exceed the value configured here
and the mains voltage is within
the operating voltage window
(parameters ╚═▷ 5810 and ╚═▷
5811), the "Command: MCB close"
may be issued.
5711 Pos. freq. differential 2 0.00 to 0.49 Hz The prerequisite for a connect
MCB command being issued for the
[0.18 Hz] MCB is that the differential
(Positive frequency frequency is below the configured
differential MCB) differential frequency.
This value specifies the upper

frequency (positive value
corresponds to positive slip →

4 Configuration
busbar frequency is higher than

the mains frequency).
5712 Neg. freq. differential 2 -0.49 to 0.00 Hz The prerequisite for a connect
MCB command being issued for the
[-0.10 Hz] MCB is that the differential
(Negative frequency frequency is above the configured
differential MCB) differential frequency.
This value specifies the lower

frequency limit (negative value
corresponds to negative slip →
busbar frequency is less than the
mains frequency).
5709 MCB sync. with 2 On The MCB is synchronized with an

separate slip individual slip frequency (also
negative).
Notes
The setting for the slipping

frequency (parameter ╚═▷ 5647)
via display is located under
'configure frequency control'.
[Off] The MCB is synchronized with the

same slip frequency like the GCB
Notes

5647 MCB slip freq. 2 -0.50 ... 0...50 Hz Individual frequency offset for the
setpoint offset MCB and LS5 synchronization. This
[-0.10 Hz] value can be a positive or
negative offset. The value is valid
as long as the parameter 'MCB
synchronization with separate slip'
On/Off' (parameter ╚═▷ 5709) is
set to 'On' .
8841 Phase angle 2 The phase angle between busbar

compensation MCB voltage and mains voltage can be
compensated according to an
installed power transformer
between busbar and mains.
On The compensation is active. The

phase will be compensated
according the value configured in
Notes
Measured values 181

'Ph.ang.busb1-gen.L12' and 184
'Ph.ang.mns.busb1 L12' are not
changed but the compensated
(╚═▷ 8842) values are taken for
synchronization control and
synchroscope display.

4 Configuration
[Off] The compensation is inactive. The

phase angle is directly taken from
the measurement.
Notes
WARNING: Ensure the following

parameters are configured
correctly to prevent erroneous
synchronization settings. Incorrect
wiring of the system cannot be
compensated for with this
parameter!
Please check during initial

commissioning the phase angle
and the synchronization with a
zero voltmeter.
Recommendation: For safety

reasons, please mark the easYgen
with a label showing the
configured phase angle
compensation.
Refer to ╚═▷ “6.3.11 Phase Angle

Compensation” for details.

8842 Phase angle MCB 2 -180 to 180° The phase angle compensation
corrects the degree between
[0°] busbar voltage and mains voltage.
The configured degree is added to
the real measured phase angle.
Notes

Ensure correct configuration to

prevent erroneous synchronization
settings to avoid generator
destructive power. Incorrect
wiring cannot be compensated for
with this parameter!
5717 Phase matching MCB 2 0.0 to 60.0 s This is the minimum time that the
dwell time generator/busbar voltage,
[3.0 s] frequency, and phase angle must
be within the configured limits
before the breaker will be closed.
Notes

3431 Dead bus closure 2 [On] A dead busbar closure is allowed if

MCB the required conditions are met.
Off An MCB close command to a dead

busbar is prevented.
Synchronization is still possible.

4 Configuration
5715 Closing time MCB 2 40 to 300 ms The inherent closing time of the
MCB corresponds to the lead-time
[80 ms] of the close command.
The close command will be issued

independent of the differential
frequency at the entered time
before the synchronous point.
3407 MCB auto unlock 2 This is used for special circuit

breakers to put the MCB into a
defined initial state or to enable
closing at all.
Yes Before every close-pulse, an open-

pulse is issued for defined
duration (parameter ╚═▷ 5718. A
CB close pulse is enabled only
after the open pulse is issued.
[No] The CB close pulse is enabled

without being preceded by a CB
open pulse.
12923 Enable MCB 2 Determined by LogicsManager Once the conditions of the

the MCB will be enabled.
[(09.06 DI06 & !08.07 MCB fail
to close) & !07.05 Mns. ph. Notes
rot. mismatch]
DI 6 is pre-assigned by default to
= 11914 this function, but may be
configured freely.

5718 MCB open time pulse 2 0.10 to 9.90 s This time defines the length of the
MCB open time pulse, if the
[1.00 s] automatic switch unblocking MCB
is activated.
12974 MCB open in MAN 2 Determined by LogicsManager With the rising edge of this
87.48 LogicsManager equation a MCB
open command in operating mode
[(0 & 1) & 1] MANUAL is initiated. The state
TRUE of this LM inhibits the MCB
= 11437 close command in MANUAL.
Notes


12975 MCB close in MAN 2 Determined by LogicsManager With the rising edge of this
87.49 LogicsManager equation a MCB
close command in operating mode
[(0 & 1) & 1] MANUAL is initiated.Precondition:
deactivated "MCB open in MAN"

4 Configuration
4.4.3.5 Configure Breakers: Synchronization
= 11438
Notes


General notes
The following parameters are only applicable for application modes A03 A04 .
[Default]
5728 Synchronization 2 Off The synchronization is disabled;

mode the frequency and voltage
adaptation for synchronization is
not active.
In operation mode AUTO the

easYgen allows the external GCB
closing in synchronization mode
“Off” if:
• Start request in automatic

active
• Generator is in operating
range
• The engine start procedure is
finished
In operation mode AUTO the

easYgen allows the external MCB
closing in synchronization mode
“Off” if:
• Mains is in the operating

range
Permissive The unit acts as a synch check

device. The unit will not issue
speed or voltage bias commands
to achieve a synchronization, but
if phase matching synchronization
conditions are matched
(frequency, phase, voltage and
phase angle), the control will issue
a breaker close command.
There are two different

functionalities of this option
depending on the setting of
parameter ╚═▷ 3414 (GCB close
command).

4 Configuration
• GCB close command set to

"Impulse":
The GCB close command is

pulsed as long as the
synchronization conditions
are matched.
• GCB close command set to

"Steady":
The GCB close command

remains enabled as long as
the synchronization
conditions are matched.
Check Used for checking a synchronizer

prior to commissioning.
The control actively synchronizes

generator(s) by issuing speed and
voltage bias commands, but does
not issue a breaker closure
command for synchronizing.
[Run] Normal operating mode. The

control actively synchronizes and
issues breaker closure commands.
Controlled by LM The synchronization mode may be

selected by enabling one of the
respective LogicsManager
functions (parameters ╚═▷ 12907,
╚═▷ 12906, or ╚═▷ 12908).
If none of these parameters is

enabled, the synchronization is
disabled.
If more than one of these

parameters is enabled, the
following priority is valid:
• 1. PERMISSIVE
• 2. CHECK
• 3. RUN
Notes
The device will still perform a

dead busbar closure if the
conditions are valid.
12907 Syn. mode PERMIS. 2 Determined by LogicsManager Once the conditions of the
(Synchronization mode the PERMISSIVE synchronization
PERMISSIVE) [(0 & 1) & 1] mode will be enabled.
= 11618 Notes

12906 Syn. mode CHECK 2 Determined by LogicsManager Once the conditions of the
(Synchronization mode the CHECK synchronization mode
CHECK) [(0 & 1) & 1] will be enabled.

4 Configuration
4.4.3.5.1 Independent Sync. Check Function
= 11617
Notes

12908 Syn. mode RUN 2 Determined by LogicsManager Once the conditions of the
(Synchronization mode the RUN synchronization mode will
RUN) [(0 & 1) & 1] be enabled.
= 11619 Notes

15157 Synchroscope autom. 2 On The synchroscope screen

to front automatically appears on the
main screen, when the
(Synchroscope synchronization becomes active.
automatic to front)
[Off] Functionality deactivated.
General notes
The device provides two independent "Sync Check" functions for the voltage comparisons
generator to busbar and busbar to mains. The criteria are the same like for the according
internal self-executed synchronization.
The easYgen provides two command variables available for the LogicsManager input:
• 02.29 Sync Check generator / busbar
• 02.32 Sync Check mains / busbar
WARNING!
No dead bus interlocking
Synch. Check is intended to be a redundant check function enhancing system security.

Don't use for MCB control!
The Sync. Check functionality is available in every application mode. The command
variables are independently calculated and depending on the same configurations, like
the self-executed GCB and MCB close commands. The sync. Check function has no
influence on any frequency or voltage biasing. There is no relationship to the Sync. Check
mode for the internal self-executed synchronization.

4 Configuration
The Synch. Check command variables do not care about:
• Possible dead busbar closure capabilities

• Internally calculated self-executed circuit breaker close orders
• Synchronization control conditions, like »mains settling time «
Variables and Parameters
»02.29 Sync.Check gen./busb« depends on
• Voltage
• Frequency
and
• Phase angle
The command variable »02.29 Sync.Check gen./busb« is true if the synchronization

conditions are matched according to (GCB) parameters:
• 5701: Pos. freq. differential
• 5702: Neg. freq. differential
• 5700: Voltage differential
• 8825, 8824: Phase angle compensation
• 5703: Max. positive phase angle
• 5704: Max. negative phase angle GCB
»02.32 Sync.Check mns/busb« depends on
• Voltage
• Frequency
and
• Phase angle
The command variable »02.32 Sync.Check mns/busb« is true, if the synchronization

conditions are matched according to parameters:
• 5711: Pos. freq. differential MCB
• 5712: Neg. freq. differential MCB
• 5710: Voltage differential MCB
• 8841,8842: Phase angle compensation MCB
• 5713: Max. positive phase angle MCB

4 Configuration
4.4.3.6 Configure Breakers: Neutral Interlocking
• 5714: Max. negative phase angle MCB
4.4.3.6 Configure Breakers: Neutral Interlocking
General Notes
The Neutral Interlocking feature controls a Neutral Contactor (NC) of each generator. The
rule is that only one neutral contactor of all running generators are closed. The Logic
ensures that with changing of generators the neutral link is passed over to another
running generator. Refer to ╚═▷ “6.3.14 Neutral Interlocking” for more information.
[Default]
1840 Neutral interlocking 2 On Neutral interlocking is enabled.

The command variable 03.39
Close neutral contactor is
activated and the DI 12 is used for
the NC feedback. The unit
monitors the NC feedback
according to the close order.
[Off] Neutral interlocking is disabled.

The NC monitoring is disabled.
1841 Priority 2 1 ... 32 The priority determines which NC

is closed, if multiple gens are
[1] running in the same segment.
Notes
The lower the configured number,

the higher the priority
To make use of the Close neutral interlocking contactor status, configure a discrete
output relay DO x to react for 03.39.
4.4.4 Configure Controller
WARNING!
Hazards due to incorrect settings
The following parameters dictate how the easYgen controls voltage, frequency, load and
power factor.
Failure to do so may lead to incorrect measurements and failures within the control unit
resulting in damage to or destruction of the generator and/or personal injury or death.
• Always ensure that the correct settings are entered in these parameters.

4 Configuration
The Real load, reactive load, and process control all utilize PID controllers. The response
of each control loop can be adjusted for optimum response, however it is important to
understand what a PID controller is and the effect of each controller adjustment has on
the controller response.
Proportional gain, integral gain (stability) and DR (speed derivative ratio) are the
adjustable and interacting parameters used to match the response of the control loop
with the response of the system.
They correspond to the P (proportional), I (integral), and D (derivative) terms, and are
displayed in the easYgen as follows:
P Proportional gain (%)
I Integral gain (%)
D Derivative gain (determined by DR and I)
Proportional control
Proportional response is directly proportional to a process change.
• Analogy: Setting hand throttle to keep constant speed on straight and level road.
Proportional control (using the same analogy) results in a certain speed as long as the car
is not subjected to any load change such as a hill. If a throttle is set to any particular
setting, the speed of the car will remain constant as long as the car remains straight and
level. If the car goes up a hill it will slow down. Of course, going down a hill the car would
gain speed.
Integral control
Integral compensates for process and setpoint load changes.
• Analogy: Cruise control maintains constant speed regardless of hills.
Integral, sometimes called reset, provides additional action to the original proportional
response as long as the process variable remains away from the setpoint. Integral is a
function of the magnitude and duration of the deviation. In this analogy the reset
response would keep the car speed constant regardless of the terrain.
Derivative
Derivative provides a temporary over-correction to compensate for long transfer lags and
reduce stabilization time on process upsets (momentary disturbances). The behavior of
the derivative parameter is shown in ╚═▷ Fig. 153.
• Analogy: Accelerating into high speed lane with merging traffic.

4 Configuration
Fig. 153: Behavior of the derivative parameter
Derivative, sometimes called "preact" of "rate", is very difficult to draw an accurate

analogy to, because the action takes place only when the process changes and is directly
related to the speed at which the process changes.
Merging into high speed traffic of a freeway from an "on" ramp is no easy task and
requires accelerated correction (temporary overcorrection) in both increasing and
decreasing directions. The application of brakes to fall behind the car in the first
continuous lane or passing gear to get ahead of the car in the first continuous lane is a
derivative action.
PID tuning example
If the system is unstable, make sure the governor is the cause. This can be checked by
closing the valve limiter until it has control of the actuator output. If the governor is
causing the oscillation, time the oscillation cycle time. A rule-of- thumb is, if the system’s
oscillation cycle time is less than 1 second, reduce the Proportional gain term. A rule-of-
thumb is, if the system’s oscillation cycle time is greater than 1 second, reduce the
Integral gain term (proportional gain may need to be increased also).
On an initial startup with the easYgen, all PID dynamic gain terms will require adjustment
to match the respective PID’s response to that of its control loop. There are multiple
dynamic tuning methods available that can be used with the easYgen’s PIDs to assist in
determining the gain terms that provide optimum control loop response times.
ᐳ The following method can be used to achieve PID gain values that are close to optimum:
1. ▷ Increase Derivative Ratio (DR) to 100.
2. ▷ Reduce integral gain to 0.01.
3. ▷ Increase proportional gain until system just starts to oscillate.
The optimum gain for this step is when the system just starts to oscillate
and maintains a self-sustaining oscillation that does not increase or decrease
in magnitude.
4. ▷ Record the control gain (Kc) and oscillation period (T) in seconds.
5. ▷ Set the dynamics as follows:

4 Configuration
4.4.4.1 Voltage Control
• For PI control G=P(I/s + 1) set:

◦ Proportional gain = 0.45*Kc
◦ Integral gain = 1.2/T
◦ Derivative ratio = 100
• For PID control G=P(I/s + 1 + Ds) set:
◦ Proportional gain = 0.60*Kc
◦ Integral gain = 2/T
◦ Deriv ratio = 8/(T*Integral Gain) for feedback dominant
◦ Deriv ratio = (T*Integral Gain)/8 for input dominant
▶ This method of tuning will get the gain settings close, they can be fine-tuned from this
point.
ToolKit: find settings screen
[Parameter / Configuration: Configure application / Configure controller: Configure

voltage control]
AnalogManagers to define input signal of voltage setpoint (1, 2) are available in ToolKit
by
• a click from screen/page "Configure voltage control"

◦ on the button "Analog manager" in the left sidebar (below permanent buttons)
or
◦ on two times "next page", or
• search for one of the AnalogManagers ╚═▷ 5618/╚═▷ 5619
ToolKit: Trend chart
ToolKit offers a trend visualization accessible by

◦ on the button "Trend chart" in the left sidebar (below permanent buttons) or
◦ on "next page", or
• search for one of the voltage controlled value shown at the status screen
[Default]
5607 Voltage Control 2 Off Voltage control is not carried out.
[PID analog] The voltage is controlled using an

analog PID controller.
3pos controller The voltage is controlled using a

three-step controller.
AVR The voltage is controlled by using

an internal AVR algorithm acting

4 Configuration
Note: (Accessible only in easYgen on the “easYgen | exciter-10”

3400XT/3500XT) (EX-10) module.
Note: With enabling the AVR

function the power factor control
(kvar control) is provided as well
over this algorithm. The setting
5625 Power factor control is faded
out.
5608 Voltage control initial 2 0.0 to 100.0% The value entered for this
state parameter is the start reference
[50.0%] point for the analog output to the
voltage controller.
If the output to the voltage control

has been disabled, the output will
act as a control position reference
point.
5610 Proportional gain 2 0.01 to 100.00 The proportional coefficient

specifies the gain. By increasing
[1.00] the gain, the response is
increased to permit larger
corrections to the variable to be
controlled. The farther out of
tolerance the process is the larger
the response action is to return
the process to the tolerance band.
If the gain is configured too high,
the result is excessive overshoot/
undershoot of the desired value.
Notes

voltage control (parameter ╚═▷
5607) is configured to "PID
analog".
5611 Integral gain 2 0.01 to 100.00 The integral gain identifies the I
part of the PID controller. The
[1.00] integral gain corrects for any
offset (between setpoint and
process variable) automatically
over time by shifting the
proportioning band. Reset
automatically changes the output
requirements until the process
variable and the setpoint are the
same. This parameter permits the
user to adjust how quickly the
reset attempts to correct for any
offset. The integral gain constant
must be greater than the
derivative time constant. If the
integral gain constant is too large,
the engine will continually
oscillate. If the integral gain
constant is too small, the engine
will take too long to settle at a
steady state.
Notes

analog".

4 Configuration
5612 Derivative ratio 2 0.01 to 100.00 The derivative ratio identifies the
D part of the PID controller. By
[0.01] increasing this parameter, the
stability of the system is
increased.
The controller will attempt to slow

down the action of the actuator in
an attempt to prevent excessive
overshoot or undershoot.
Essentially this is the brake for the

process. This portion of the PID
loop operates anywhere within the
range of the process unlike reset.
Notes

analog".
The default configured controller

acts like a PI controller what is the
valid D part setting for systems
with secondary controllers.
5650 Deadband 1 0.1 to 9.9% islanded operation
[1.0%] The generator voltage is

controlled in such a manner that
the measured voltage does not
deviate from the configured
setpoint by more than the value
configured in this parameter
without the controller issuing a
voltage raise/lower signal to the
voltage regulator. This prevents
unneeded wear on the voltage
bias output control or the raise/
lower relay contacts.
Synchronization
The generator voltage is

the measured voltage does not
deviate from the monitored
reference (mains or busbar)
voltage by more than the value
voltage raise/lower signal to the
voltage regulator.
This prevents unneeded wear on

the voltage bias output control or
the raise/lower relay contacts. The
value configured for this
parameter must be less than the
value configured for the dV max
(maximum voltage differential) for
synchronization (parameters ╚═▷
5700 or ╚═▷ 5710).
Notes


4 Configuration
5607) is configured to "3pos

controller".
5651 Time pulse minimum 1 0.01 to 2.00 s A minimum pulse on time must be
configured here. The shortest
[0.05 s] possible pulse time should be
configured to limit overshoot of
the desired voltage reference
point.
Notes

controller".
5652 Gain factor 1 0.1 to 10.0 The gain factor Kp influences the
operating time of the relays. By
[5.0] increasing the number configured
in this parameter, the operating
time of the relay will be in-creased
in response to a deviation from
the voltage reference.
By increasing the gain, the

response is increased to permit
larger corrections to the variable
to be controlled.
The farther out of tolerance the

process is the larger the response
action is to return the process to
the tolerance band. If the gain is
configured too high, the result is
excessive overshoot/undershoot
of the desired value.
Notes

controller".
5659 Cycle time factor 1 1.0 to 20.0 The cycle time factor adjusts the
time between the pulses (pause
[1.0] time).
By increasing the cycle time

factor, the time between the
pulses increases.
Notes

controller".
5653 Expand deadband 1 1.0 to 9.9 If the measured generator voltage

factor is within the deadband range
[1.0] (parameter ╚═▷ 5650) and the
configured delay expand
deadband time (parameter ╚═▷
5654) expires, the deadband will

4 Configuration
be multiplied with the factor

configured here.
Notes

controller".
5654 Delay expand 1 1.0 to 9.9 s The measured generator voltage

deadband must be within the deadband
[2.0 s] range for the time configured here
in order to multiply the deadband
with the factor configured in
Notes

controller".
5618 AM Voltage SP1 [V] 2 Determined by AnalogManager The voltage setpoint 1 source may
81.09 be selected from the available
data sources.
[A1 = 05.57 Internal v setp1
[V]] The internal voltage setpoint
05.57 can be changed manually at
the setpoint screen of the display.
Notes
The voltage setpoint may be

adjusted within the configured
operating limits (╚═▷ “4.5.1.1
Generator Operating Ranges:
Voltage / Frequency / Busbar”).
5600 Int.voltage control 2 50 to 650,000 V The internal generator voltage

setpoint 1 setpoint 1 is defined in this
[400 V] screen. This value is the reference
for the voltage controller when
performing islanded and/or no-
load operations.
5619 AM Voltage SP2 [V] 2 Determined by AnalogManager The voltage setpoint 2 source may
81.10 be selected from the available
data sources.
[A1 = 05.58 Internal v setp2
[V]] The internal voltage setpoint
Notes
The voltage setpoint may be

5601 Int.voltage control 2 50 to 650,000 V The internal generator voltage


4 Configuration
[400 V] screen. This value is the reference

for the voltage controller when
load operations.
12920 Setp. 2 voltage 2 Determined by LogicsManager If this LogicsManager condition is

86.83 TRUE, the voltage setpoint 2 will
be used instead of voltage
[(0 & 1) & 1] setpoint 1. The voltage (result of
AM) ╚═▷ 5619 instead of ╚═▷
= 11912 5618 will be taken into account.
Notes

Remotely switching the setpoint is

possible: Use the LogicsManager
command variable for input that is
correlating with the dedicated bit
of parameter ╚═▷ ⇱.
5616 Start value 1 0 to 100% The voltage controller is activated

when the monitored generator
[70%] voltage has exceeded the value
configured in this parameter. This
prevents the easYgen from
attempting to control the voltage
while the engine is completing its
start sequence.
Notes

voltage setpoint (parameter ╚═▷
5600 or ╚═▷ 5601).
5617 Start delay 1 0 to 999 s The voltage controller is enabled

after the configured time for this
[5 s] parameter expires.
5603 Voltage control 2 1.00 to 300.00 %/s The different setpoint values are
setpoint ramp supplied to the controller via this
[5.00 %/s] ramp. The slope of the ramp is
used to alter the rate at which the
controller modifies the setpoint
value. The faster the change in
the setpoint is to be carried out,
the greater the value entered here
must be.
5604 Voltage control droop 2 0.0 to 20.0% If this control is to be operated on

a generator in parallel with other
[5.0%] generators and voltage control is
enabled, a droop characteristic
curve must be used.
Each generator in the system will

require the same value to be
configured for the droop
characteristic, so that when the
system is stable the reactive
power will be distributed
proportionally among all

4 Configuration
4.4.4.2 Power Factor Control
generators in relation to their

rated reactive power.
12905 Volt. droop act. 2 Determined by LogicsManager If this LogicsManager condition is

86.26 TRUE, the voltage droop is
(Voltage droop active) enabled.
[(08.17 Missing member OR
08.06 GCB fail to open) & 1] Example
= 11605 • Rated reactive power:

400 kvar
• Rated voltage setpoint: 410 V
• Droop 5.0%
• Reactive power 0 kvar = 0%
of rated power
• Voltage is adjusted to (410 V
– [5.0% * 0.0 * 410 V]) =
410 V.
• Reactive power 400 kvar =
100% of rated reactive power
• Voltage is adjusted to (410 V
– [5.0% * 1.0 * 410 V]) =
410 V – 20.5 V = 389.5 V.
Notes

12938 Release V-control 2 Determined by LogicsManager This LogicsManager is used to

86.97 activate generally the voltage
biasing to the sub controller. If the
[(1 & 1) & 1] LogicsManager is false the output
will be on the initial state (see
= 11926 parameter ╚═▷ 5608).
The LogicsManager condition

status 'TRUE' is activating the
voltage or reactive power
regulation according to the
LogicsManager 'V/Q control' ID
╚═▷ 12941).
Notes

4.4.4.2 Power Factor Control
The easYgen cover a wide range of power factor control tasks:
• Controller type can be selected for an analog PID or a three-step controller (see
chapter ╚═▷ “4.4.4.2.2 Configure Power Factor / kvar Control”)
• PF(P) characteristic is available (see chapter ╚═▷ “4.4.4.2 Power Factor Control”)

4 Configuration
4.4.4.2.1 Control The Power Factor / Reactive Power At The Mains Interchange Point
• Beside PF(P) characteristic, Q(V) characteristic is available too (see chapter ╚═▷
“4.4.4.2 Power Factor Control”).
• Reactive power control at the interchange point offers another opportunity of power
factor control (see chapter ╚═▷ “4.4.4.2.1 Control The Power Factor / Reactive Power
At The Mains Interchange Point”).
4.4.4.2.1 Control The Power Factor / Reactive Power At The Mains Interchange Point
General notes
Being parallel to the utility, it is desired in some application to control either the power
factor or the amount of imported/exported inductive reactive power in kvar at the mains
interchange point. Similar to an import/export active power setpoint, all easYgens can be
programmed to the same setpoint and will share between each other the reactive power
to reach this setpoint.
The easYgen can work as reactive power control at the interchange point. In this mode
the gensets are monitored and restricted in reactive power flow (outcome and income;
respectively leading and lagging).
Generator Reactive Power Limitations
A reactive power control (kvar or power factor) can cause an overload or damage of the
generator. To avoid this the easYgen provides a 2-step protection:
1. ▷ The own absolute generator current is monitored with an percentage setting related to
rated current input (ID ╚═▷ 1754). The easYgen limits or controls down the excitation
that this given level (ID ╚═▷ 5791) is not exceeded.
2. ▷ The inductive reactive power outcome of the own generator is limited according to the
configuration of ID ╚═▷ 5792.
Or:
The inductive reactive power income of the own generator is limited according to the
configuration of ID ╚═▷ 5793.
Fig. 154: The kvar setpoint is limited to protect the generator

4 Configuration
4.4.4.2.2 Configure Power Factor / kvar Control
Tracking of the limitation
An active Limitation is
• indicated as 'Gen excitation lim.' on the display (HMI)
• driving the LogicsManager command variable 05.18 Gen excitation lim. from FALSE
to TRUE
• driving an event logger entry
[Default]
5625 Power factor Control 2 [PID analog] The power factor is controlled
using an analog PID controller.
3pos controller The power factor is controlled

using a three-step controller.
Off Power factor control is not carried

out.

controlled.

the tolerance band.
Notes


power factor control
(parameter ╚═▷ 5625) is
configured to "PID analog".
[1.000] integral gain corrects for any
proportioning band.
Reset automatically changes the

output requirements until the
process variable and the setpoint
are the same. This parameter
permits the user to adjust how
quickly the reset attempts to
correct for any offset. The integral

4 Configuration
gain constant must be greater

than the derivative time constant.
If the integral gain constant is too

large, the engine will continually
oscillate. If the integral gain
constant is too small, the engine
will take too long to settle at a
steady state.
Notes

increased.
The controller will attempt to slow

down the action of the actuator in
an attempt to prevent excessive
overshoot or undershoot.
Essentially this is the brake for the

process. This portion of the PID
loop operates anywhere within the
Notes


5660 Deadband 1 0.001 to 0.300 The generator power factor is

controlled in such a manner, when
[0.010] paralleled with the mains, so that
the monitored power factor does
not deviate from the configured
power factor setpoint by more
than the value configured in this
parameter without the controller
issuing a raise/lower signal to the
voltage regulator.

the raise/lower relay contacts.
Notes

configured to "3pos controller".
configured here.

4 Configuration
[0.05 s] The shortest possible pulse time

should be configured to limit
overshoot of the desired power
factor reference point.
Notes

power factor control (parameter
╚═▷ 5625) is configured to "3pos
controller".
operating time of the relays.
[5.0]
By increasing the number
configured in this parameter, the
operating time of the relay will be
in-creased in response to a
deviation from the power factor
reference.

to be controlled.

Notes

[1.0] time).

pulses increases.
Notes

controller".
5663 Expand deadband 1 1.0 to 9.9 If the measured generator power

factor factor is within the deadband
[1.0] range (parameter ╚═▷ 5660) and
the configured delay expand
configured here.
Notes

4 Configuration

5664 Delay expand 1 1.0 to 9.9 s The measured generator power

deadband factor must be within the
[2.0 s] deadband range for the time
configured here in order to
multiply the deadband with the
factor configured in
Notes

5791 Max. generator 2 0 to 150% This is the maximum generator

current current during reactive power
[100%] control. The percentage is related
to the rated current setting (ID
╚═▷ 1785).
5792 Max. react.inductive 2 0 to 150% This is the maximum accepted

pwr.gen generator reactive inductive load
[80%] (outcome) during reactive power
control at the interchange point.
The percentage is related to the
reactive power setting (ID ╚═▷
1746).
5793 Max. react.capacity 2 0 to 150% This is the maximum accepted

pwr.gen generator reactive capacitive load
[50%] (income) during reactive power
control at the interchange point.
The percentage is related to the
reactive power setting (ID ╚═▷
1746).
5638 AM PF/kvar SP1[-/ 2 Determined by AnalogManager The power factor / reactive power
kvar] 81.11 setpoint 1 source can be selected
from the available data sources.
[A1 = 05.10 Intern. PF setp1
[%]] The internal PF/var setpoint 05.10
can be changed manually at the
setpoint screen of the display.
5639 AM PF/kvar SP2[-/ 2 Determined by AnalogManager The power factor / reactive power
kvar] 81.05 setpoint 2 source can be selected
from the available data sources.
[A1 = 05.11 Intern. PF setp2
[%]] The internal PF/var setpoint 05.11
5743 PF/kvar setpoint 1 [Gen. PF] Determination of the reactive

mode power control argument (Modes)
Mns. Export kvar

4 Configuration
Mns. Import kvar Gen.PF: The value entered as PF/

kvar setpoint is a generator power
Mains PF factor setpoint.
Gen. kvar Mns.Export kvar: The value

entered as PF/kvar setpoint is a
mains export power setpoint in
kvar. Note: Even the value is also
configurable as negative value do
not enter a negative value in this
mode.
Mns.Import kvar: The value

mains import power setpoint in
mode.
Mains PF: The value entered as

PF/kvar setpoint is a mains power
factor setpoint at the interchange
point to mains.
Gen.kvar: The value entered as

PF/kvar setpoint is a generator
kvar power setpoint (-99999.9 to
99999.0 kvar). Note: A negative
value is accepted as a capacitive
kvar setpoint. A positive value is
accepted as inductive setpoint in
this mode.
5620 Int. power factor 2 -0.999 to +1.000 The desired power factor may be
setpoint 1 configured here so that the
[+1.000] reactive power is regulated in the
system.
The designations "+" and "-"

stand for inductive/lagging
(generator overexcited) and
capacitive/leading (generator
underexcited) reactive power.
This setpoint is active only in

mains parallel operation.
5744 PF/kvar setpoint 2 [Gen. PF] Determination of the reactive

mode power control argument (Modes)
Mns. Export kvar
Gen.PF: The value entered as PF/
Mns. Import kvar kvar setpoint is a generator power
factor setpoint.
Mains PF
Mns.Export kvar: The value
Gen. kvar entered as PF/kvar setpoint is a
mains export power setpoint in
mode.
Mns.Import kvar: The value

mains import power setpoint in
mode.
Mains PF: The value entered as

PF/kvar setpoint is a mains power
factor setpoint at the interchange
point to mains.

4 Configuration
Gen.kvar: The value entered as

PF/kvar setpoint is a generator
kvar power setpoint (-99999.9 to
99999.0 kvar). Note: A negative
value is accepted as a capacitive
kvar setpoint. A positive value is
accepted as inductive setpoint in
this mode.
5745 Int. kvar setpoint 1 -99999.9 to +99999.9 This setpoint is active only if PF/
kvar setpoint 1 is set to Mns.
[0.0] Export kvar or Mns. Import kvar.
5621 Int. power factor 2 -0.999 to +1.000 The desired power factor may be
setpoint 2 configured here so that the
[+1.000] reactive power is regulated in the
system.
The designations "–" and "+"

underexcited) reactive power. This
setpoint is active only in mains
parallel operation.
5746 Int. kvar setpoint 2 -0.999 to +99999.9 This setpoint is active only if PF/
kvar setpoint 2 is set to Mns.
[0.0] Export kvar or Mns. Import kvar.
12921 Setp. 2 pwr.factor 2 Determined by LogicsManager If this LogicsManager condition is

86.84 TRUE, the power factor setpoint 2
will be used instead of power
[(0 & 1) & 1] factor setpoint 1. The power factor
(result of AM) ╚═▷ 5639 instead of
= 11913 ╚═▷ 5638 will be taken into
account.
Notes

5622 React. pwr. ctrl 2 0.01 to 100.00 %/s The different setpoint values are
[3.00 %/s] ramp.
The slope of the ramp is used to

alter the rate at which the
must be.
Notes
This ramp is also used in islanded

operation for loading or unloading
an additional genset. An excessive
oscillation may occur if the ramp
is configured too high.
1884 Gen. PF setpoint 2 0.0 to 99.9 s The PT1-filter for the Gen PF or
filter Gen kvar setpoint mode can be
configured here. The parameter

4 Configuration
4.4.4.2.3 Power Factor Characteristic
[0s] stands for the 3 times tau value of

a PT1 element. (see drawing).
That means the configured time
defines when 95% of the original
setpoint jump is reached.
Notes
Input 0.0s disables the filter

influence.
12941 Q control 2 Determined by LogicsManager With LogicsManager can be

86.99 controlled if a voltage control or a
reactive power control should be
[(04.07 MCB closed & 04.06 performed. If this LogicsManager
GCB closed) & 1] condition is TRUE, the reactive
power control is performed.
= 11928
4.4.4.2.3 Power Factor Characteristic
General notes
This feature is related to the former BDEW grid code. For the VDE-AR-N 4110 / 4105 grid
code please refer the reactive power characteristics
The Power Factor Characteristic function is adapting the reactive power flow between
generator and mains to support a dynamic stabilization of the mains. Some network
provider prefer therefore a power factor control over real power PF(P) (see chapter╚═▷
“4.4.4.2.3.1 Power factor characteristic PF(P) ” for more details).
Other provider prefer power factor control over mains voltage Q(V) as described in
chapter ╚═▷ “4.4.4.2.3.2 Power factor characteristic Q(V) ”. Both methods are
configurable alternatively.
Enhanced according BDEW Requirements
Both power factor characteristic curves now offer four point settings.
Factory settings come with backward compatibility.
4.4.4.2.3.1 Power factor characteristic PF(P)
A method to support the mains is to feed different reactive power values into the grid in
relation to the own active power value. The reactive power is defined through a power
factor setpoint for the generator. This can be defined in characteristic curve.

4 Configuration
4.4.4.2.3.1 Power factor characteristic PF(P)
Fig. 155: Power factor characteristic (schematic)
The characteristic is defined by four points (① .. ④). The power factor corresponding to
this characteristic is available as data source 05.29 in the AnalogManager.
To use this function, the source (05.29) must be applied as source to one of the setpoints
e.g., "Power factor setpoint 1" (parameter ╚═▷ 5638).
[Default]
5786 Power factor 2 [PF(P)] A power factor setpoint is

characteristic determined according to the
characteristic curve: Power factor
in relation to the actual Generator
power.
Q(V) A power factor setpoint is

calculated according to the
characteristic curve: Generator
reactive power in relation to the
mains voltage.
5787 Point 1 power 2 0.0 to 150% The value entered into "Point 1
power" defines the cos phi (P)
[0%] characteristic.
5788 Point 1 cos phi 2 -0.999 to 1.000 The desired "Point 1 cos phi" may
be configured here which defines
[-0.950] the cos phi (P) characteristic.

4 Configuration
4.4.4.2.3.2 Power factor characteristic Q(V)

[0.950] the cos phi (P) characteristic.



Another method to support the mains is to feed different reactive power values into the
grid in relation to the mains voltage [parameter ╚═▷ 5786 = Q(V)]. The reactive power is
defined through the value Q/S rated over voltage. This can be defined in a characteristic
curve. The resulting outcome for the reactive power control is then a power factor
setpoint.

4 Configuration
Fig. 156: Power factor characteristic according to the relation Q/S rated over rated
voltage
The characteristic is defined by four points (① .. ④). The power factor corresponding to
this characteristic is available as data source 05.29 in the AnalogManager.
To use this function, the source (05.29) must be applied as source to one of the setpoints
e.g., "Power factor setpoint 1" (parameter ╚═▷ 5638).
[Default]
5778 Point 1 voltage 45.0 to 150.0% The value entered into "Point 1
Voltage" defines the x-coordinate
[98.0%] of point 1
5779 Point 1 Q/S rated -0.99 to +0.99 The value entered into "Point 1
Reactive power" defines the y-
[-0.31] coordinate of point 1

4 Configuration
[106.0%] of point 2
[+0.31] coordinate of point 2
[106.0%] of point 3
[106.0%] of point 4
5799 Q(V) response time 001 to 999 s The response with a new reactive
power setpoint acting on the
[10 s] analog command variable 05.29
PF characteristic can be delayed.
Q(V) response time is used to
calculate the power factor
characteristic Q(V), parameter
╚═▷ 5786.
Notes
The delay is realized with a PT-1

filter. Therefore the reaction times
are optimized for the range 10 s
until 60 s within a symmetrical
characteristic curve.
Accuracy of the setup Q(V)

response time is given within a
symmetrical characteristic curve.
5023 Q(V) Hysteresis 0 to 20% The hysteresis for the Q(V)

characteristic acts as a deadband
[0%] for the selected band. If the Mains
voltage is within the hysteresis
the resulting power factor
characteristic reference doesn't
change.

4 Configuration
4.4.4.2.4 Reactive Power / Power Factor setpoint filter
Introduction
The FNN VDE-AR-N 4105 / 4110 requests a reactive power control with a setpoint which is
leaded over a PT1-element. The PT1-element shall be adjustable with a 3 tau setting. The
3 tau setting defines at what time shall be reached 95% of the original setpoint change.
This 3 tau value is configurable.
Function
The reactive power controller PID is always receiving a reactive power setpoint even the
setpoint is entered as power factor or as power factor setpoint. The PT1 filter behavior is
always included (Refer to drawing) but the filter can configured so that it has no
influence.
Fig. 157: Setpoint Jump (standardized with height 1) and the resulting PT1 setpoint
Four reactive power setpoint filters are placed in the easYgen in regards to:
• Gen PF setpoint setting
• Reactive power characteristic Q(V)
• Reactive power characteristic Q(P)
• Reactive power characteristic Q(V) limit

4 Configuration
Fig. 158: The allocation of reactive power setpoints and their filters
Configuration
ID Parameter Setting range Description
[Default]
1884 Gen. PF setpoint filter 0 to 99.9s The PT1-filter for the Gen PF
setpoint mode can be configured
[0.0s] here. The parameter stands for
the 3 times tau value of a PT1
element. (see drawing). That
means the configured time
Note: Input 0.0s disables the filter

influence.
1897 Q(V) setpoint filter 0 to 99.9s The PT1-filter for the reactive
power characteristic Q(V) can be
[10.0s] configured here. The parameter
stands for the 3 times tau value of

influence.
1898 Q(P) setpoint filter 0 to 99.9s The PT1-filter for the reactive
power characteristic Q(P) can be

4 Configuration
4.4.4.2.5 Reactive Power Characteristic


influence.
1899 Q(V) limit setpoint filter 0 to 99.9s The PT1-filter for the reactive
power characteristic Q(V) limit can
[10.0s] be configured here. The
parameter stands for the 3 times
tau value of a PT1 element. (see
drawing). That means the
configured time defines when 95%
of the original setpoint jump is
reached.

influence.
4.4.4.2.5 Reactive Power Characteristic
4.4.4.2.5.1 Reactive power Q(V)
General notes
This feature is related to the VDE-AR-N 4110 / 4105 grid code. For BDEW related grid
code please refer to ╚═▷ “4.4.4.2 Power Factor Control”.
The FNN VDE-AR-N 4105 / 4110 requests different methods for reactive power control
during mains faults to stabilize the mains.
This method determines a reactive power setpoint deviation based on the mains voltage
deviation from a rated mains voltage value.
The slope follows the formula:

(Qmax / Pinst.)
Slope(QV) =
(Vmax / Vc) - (VQ0 / Vc)
The formula contains a factor which can shift the curve on the voltage axis. The shift itself
can be determined through an analog value “VQ0”. This gives the network provider the
capability to change the reactive power influence remotely.
Function
This procedure of running different reactive power values over the voltage is based on
two points:
Point 1 is defined as the reference voltage on which the reactive power shall be zero.
Point 2 is defined through the value pair (Vmax/VC ; Qmax/Pinst.). This point defines
finally the maximal reactive power, which is allowed to run for the generator. It is valid for
leading and lagging reactive power (Under-excitation/Over-excitation).
So if mains voltage exceeds the Vmax/VC point inductive power is absorbed and with
surpassed Vmax/VC inductive reactive power is delivered to mains.

4 Configuration
Furthermore the function provides the capability to shift point 1 on the x-axis from
outside. Through this it can be determined afterwards at what mains voltage level the
reactive power flow begins to work.
Through a dead band incorporation into the function the operator can determine to stay
on a last calculated reactive power. So as long the mains voltage deviates not again
around a dead band width the last setpoint is kept.
And finally through a test function the function gives the operator the opportunity to
simulate different mains voltages to observe whether the reactive power flow is
maintained properly.
Fig. 159: EGXT_Example_of_a_Q(V)_characteristic

4 Configuration
[Default]
5823 Vmax/Vc 1.00 to 1.2s The point 2 defines the maximal

allowed reactive power for the
[1.4s] generator. The point determines
the leading limit as also the
lagging limit. Refer to drawing.
This value determines the value 1

(Vmax/VC) of the point 2 value
pair. This is the maximum voltage
which can be transacted.
Maximum voltage in relation to

the supply voltage (Vc). Mostly
the supply voltage is similar to the
rated voltage in the system.
5824 Qmax/Pinst. 0 to 0.5s The point 2 defines the maximal

allowed reactive power for the
[0.33s] generator. The point determines
the leading limit as also the
lagging limit. Refer to drawing.
This value determines the value 2
(Qmax/Pinst.) of the point 2 value
pair.
Maximum reactive power in

relation to the installed active
power from the power generation
device. The installed active power
is usually the rated generator
power. The maximum reactive
power defines the positive and
negative reactive power as well.
5825 AM Reference VQ0 AnalogManager AnalogManager which provides

the shifting of the x-axis. It is
10.02 (ONE) named VQ0.
10.01 (ZERO) Through this value the reference

mains voltage level Point 1 can be
0.0 shifted. Refer to drawing.
02.01 (LM FALSE) The value determines the point

where the reactive power setpoint
02.01 (LM FALSE) matches 0 kvar.
Pass through Analog result of AnalogManager

81.31 AM Reference VQ0
Binary result of
AnalogManager81.31 AM
Reference VQ0
5827 Q(V) voltage dead band 0 to 10.00% The dead band for the mains
voltage relates to the calculation
[0%] of a new reactive power reference.
If the mains voltage is higher/
lower as the previous mains
voltage +/- hysteresis the “new
value” will be used for the
reactive power calculation.

4 Configuration
1897 Q(V) setpoint filter 0 to 99.9s The PT1-filter for the reactive
power characteristic Q(V) can be

influence.
Interface reference setpoint VQ0
AnalogManager variable “05.46 VQ0 reference”
No. Description Value Meaning
512 Control 10 INT16 Interface reference

value VQ0. Resolution
(1/100)
VQ0: The “starting”

value is 1.00.
The value is limited

according to the
configuration setting.
Analog source: Interface reference setpoint VQ0
This can be picked up with the AnalogManager variable “05.46 VQ0 reference”
Visualization Q(V) reactive power characteristic
Actual value V/Vc ID10353
Q/Pinst reference ID 10347
QV reference [kvar] ID 10359
Configuration Test possibility for reactive power Q(V) characteristic
For test purposes it is possible to configure a "Test mains voltage" which is passed to the
Q(V) characteristic instead of the real mains voltage measurement.
[Default]
5828 Enable mains test voltage On For test purposes, use the mains
test voltage instead of the
[Off] measured mains voltage. This
function is temporarily enabled.
On: The mains test voltage is

used for Q(V) reactive power
characteristic. This function is
reset after 1 hour automatically.
Off: The test voltage is disabled

and the measured mains voltage
is used.

4 Configuration
4.4.4.2.5.2 Reactive Power Q(P)
Note: Only in toolkit!
5829 Mains test voltage 50 to 150% The Q(V) function uses the mains
test voltage for the calculation of
[100%] the reactive power reference.
Note: Only in toolkit!
General notes
during mains faults to stabilize the mains. This method determines a reactive power
based on the actual power output of the generator. The reactive power is controlled in
relation to the actual active power. Maximal 10 reference points define the curve. The
space between the points are linear interpolated. The tolerance band for the configured
curve is +/- 2%
Function
Through the input of up to 10 points a reactive power characteristic can be formed.

4 Configuration
Fig. 160: Example of a Q(P) characteristic with 5 points
[Default]

4 Configuration
4.4.4.2.5.3 Reactive Power Q(V) limit
5831 P/Pinst point 1 0 Configuration points (reference

points 1 to 10 with relation active
5832 Q/Pinst point 1 0 power/active power installed (P/
Pinst) and rated reactive power in
5833 P/Pinst point 2 0.1 relation to active power installed
(Q/Pinst)
5834 Q/Pinst point 2 0
P:
5835 P/Pinst point 3 0.2
Range 0.00 .. 1.50
Format 0.00
5839 P/Pinst point 5 0
5844 Q/Pinst point 7 0.05
5847 P/Pinst point 9 1
1898 Q(P) setpoint filter 0 to 99.9s The PT1-filter for the reactive
power characteristic Q(P) can be

influence.
Visualization Q(P) reactive power characteristic
Actual value P/Pinst ID10354
Q/Pinst reference ID10349
QP reference [kvar] ID10350
Introduction
during mains faults to stabilize the mains.

4 Configuration
This method determines a reactive power setpoint deviation based on the mains voltage.
The curve here is defined with four points. The value pairs of point 2 and point 3 can be
influenced through an offset value remotely.
This is a way to shift the dead band into a reactive power flow zone. The network provider
can influence the basic reactive power flow remotely.
Function
This procedure of running different reactive power values over the voltage is based on
four point:
• Point 1 is defined as the reference voltage on which the lagging reactive power flow
shall be limited (max. over-excitation). Example in drawing [V/VC 0.94 ; Q/Pbinst
-0.33]
• Point 2 is defined as the lowest reference voltage at which the reactive power flow is
zero. Example in drawing [V/VC 0.96 ; Q/Pbinst 0.00]
• Point 3 is defined as the highest reference voltage at which the reactive power flow
is zero. Example in drawing [V/VC 1.04 ; Q/Pbinst 0.00]
• Point 4 is defined as the reference voltage on which the leading reactive power flow
shall be limited (max. under-excitation). Example in drawing [V/VC 1.06 ; Q/Pbinst
0.33]
Furthermore the function provides the capability to shift point 2 and point 3 so that the
dead band is shifted into a reactive power flow zone. With this setting the network
provider can relative simple shift the reactive power flow (leading or lagging) in the usual
voltage range. This helps to compensate any local situations from remote.
Finally, through a test function, the function gives the operator the chance to simulate
different mains voltages to observe if the reactive power flow is being maintained
properly.

4 Configuration
Fig. 161: Example of a Q(V) limit characteristic

4 Configuration
[Default]
6912 P/Pinst point 1 0.94 Configuration points (reference

points 1 to 4) with voltage level in
6913 Q/Pinst point 1 -0.33 relation to the supply voltage (Vc)
and the reactive power in relation
6914 P/Pinst point 2 0.96 to the installed active power from
the power generation device. The
6915 Q/Pinst point 2 0 installed active power is normally
the rated power.
V:
Range 0.00 to 1.50
Format 0.00
Q:
Range -0.5 to 0.50
Format 00.00
1899 Q(V) limit setpoint filter 0 to 99.9s The PT1-filter for the reactive
power characteristic Q(V) limit can
[10.0s] be configured here. The
parameter stands for the 3 times
tau value of a PT1 element. (see
drawing). That means the
configured time defines when 95%
of the original setpoint jump is
reached.

influence.
6908 Q/P reference offset AnalogManager AnalogManager for the source

selection from the reference offset
10.02 (ONE) from the energy provider. This
value defines the offset for the
10.01 (ZERO) reference points 2 and 3.
0.0 AM Q/P reference offset
02.01 (LM FALSE) 81.32
02.01 (LM FALSE) Analog result of AnalogManager
Pass through LM Q/P reference offset
81.32
Binary result of AnalogManager
Interface reference setpoint Q/P limit offset
AnalogManager variable “05.47 QP limit offset”
513 Control 10 INTEGER16 Interface reference

value Q/P offset.
Resolution (1/100)
Q/P offset: The

“starting” value is 0.

4 Configuration
4.4.4.3 Load Share Control

The value is limited
according to the
configuration setting.
Analog source: Interface reference setpoint Q/P offset
AnalogManager variable “05.47 QP limit offset”
Visualization Q(V) limit reactive power characteristic
Actual value V/VC ID10355
Q/Pinst reference ID 10351
QV reference [kvar] ID 10352
Configuration Test possibility for reactive power Q(V) limit characteristic
For test purposes it is possible to configure a "Test mains voltage" which is passed to the
Q(V) limit characteristic instead the real mains voltage measurement.
The parameter Ids are the same like for the Q(V) reactive power characteristic.
4.4.4.3 Load Share Control
CAUTION!
Load Share Communication
For correct load share communication all load sharing gensets in the system must
actively use the same load share communication interface (and network)!
Load share communication is defined by parameter »Load share interface « ╚═▷ 9924
(CAN or Ethernet) and others.
Please see settings at
• [Parameter / Configuration / Configure application / Configure controller / Configure

load share]
• Chapter ╚═▷ “4.4.4.3.7 Parameters”
The easYgen performs proportional load and/or var sharing. This means each generator
will share the load at the same percentage level of the generator rated power when
paralleled against the mains, in an islanded operation with multiple generators paralleled,
or when re-synchronizing the common bus to the mains.
Also in islanded operation the load ramp rate parameters ╚═▷ 5522 and ╚═▷ 5622 are
used to ramp a new generator onto the other.

4 Configuration
4.4.4.3.1 Mains Parallel Operation With Mains Interchange Real Power Control (Import/Export)
If not enough nominal power on the busbar is available, from now on the ramping of an
engine onto others will be interrupted but the load sharing will be executed immediately.
This is to avoid overloading of already online generators.
Proportional load/var sharing will not be performed when the easYgen has the GCB
closed and is in the constant power/base load mode.
A system can consist out of 32 gensets which are controlled by a single easYgen.
4.4.4.3.1 Mains Parallel Operation With Mains Interchange Real Power Control (Import/Export)
The easYgen controllers maintain the real load level on the individually controlled
generators at a level so that the real power setpoint at the mains interchange remains at
the configured setpoint. The real power setpoint for the mains interchange must be
configured identically for each easYgen.
The easYgen controller communicates with other controls in the system via a CAN bus.
This enables the controllers to adjust the real power generated by the generator while
remaining within the rated power of the generator. A smaller generator will contribute
less real power as compared to a large generator, but they will both be utilized to the
same capacity factor. An example of this would be a 100 kW generator with a configured
1000 kW generator and a mains interchange of 825 kW. The 100 kW generator would
contribute 75 kW and the 1000 kW generator would contribute 750 kW or both
generators would be at 75% of their rated capacity.
How the reactive power handling is executed depends the PF/kvar setpoint mode. Two
setpoints (╚═▷ 5743 and ╚═▷ 5744) are available. Each setpoint allows the modes:
• Gen PF
• Mains PF
• Mains Import kvar
• Mains export kvar
In PF modes the reactive load sharing is not performed when operating in parallel with
the mains. Reactive power control will be defined by the configured power factor
setpoints (╚═▷ 5620 or ╚═▷ 5621) of the individual controllers. If the power factor
controller setpoint is configured as +0.950, the easYgen will proportionally share the real
load with all generators in parallel with the mains while controlling the reactive power at
a 0.95 inductive (lagging) power factor regardless of the what power factor the mains is
operating at.
The parameter "Active power Load share gain" (parameter ╚═▷ 4522) can be used to
define the priority of the reference variable for real power sharing (real power at
interchange). A higher configured value influences the control more towards maintaining
the real power setpoint for the interchange. A lower configured value influences the
control more towards maintaining real power sharing between units.
The parameter "React. power Load share gain" (parameter ╚═▷ 4543) has no influence
here.

4 Configuration
4.4.4.3.2 Islanded Operation In Parallel
In kvar modes the reactive load sharing is performed when operating in parallel with the
mains. Mains import/export kvar control at the interchange point will be determined by
the configured int. kvar setpoints (╚═▷ 5745 or ╚═▷ 5746) of the individual controllers.
4.4.4.3.2 Islanded Operation In Parallel
The easYgen controllers maintain the voltage and frequency of the individually controlled
generators at a constant level. This makes it imperative that the voltage and frequency
setpoints are configured identically for each easYgen.
The easYgen controller communicates with other controls in the system via a CAN bus.
This enables the controllers to adjust the real power generated by the generator while
remaining within the rated power of the generator. A smaller generator will contribute
less real power as compared to a large generator, but they will both be utilized to the
same capacity factor.
☼ Example
An example of this would be a 100 kW generator and a 1000 kW generator with an

825 kW load. The 100 kW generator would contribute 75 kW and the 1000 kW generator
would contribute 750 kW or both generators would be at 75% of their rated capacity.
The reactive power will be shared proportionally among all generators involved.
define the priority of the reference variable for real power sharing. A higher configured
value influences the control more towards frequency control. A lower configured value
influences the control more towards real power sharing.
define the priority of the reference variable for real power sharing. A higher configured
value influences the control more towards frequency control. A lower configured value
influences the control more towards real power sharing.
4.4.4.3.3 Re-synchronization Of The Busbar To The Mains
The system is operating as an islanded system, for synchronization to be performed the

voltage and frequency differentials of the mains and bus must be within the configured
windows.
The bus frequency reference point is dictated by the measured mains frequency and the
configured frequency differential (+ slip frequency setpoint offset (parameter ╚═▷ 5502).
☼ Example
If + slip frequency setpoint offset = 0.2 Hz, the easYgen will calculate the bus frequency
reference point as:
• [measured mains frequency] + [slip frequency setpoint offset] = bus frequency

reference point
A practical example of this would be:
• The monitored mains frequency is 60 Hz

• Configured + slip frequency setpoint offset = 0.2 Hz
• [60 Hz] + [0.2 Hz] = 60.2 Hz bus frequency reference point

4 Configuration
4.4.4.3.4 Prerequisites
The differential voltage is configured as a window. The monitored voltage from the
potential transformers secondary for the mains and the bus must be within the configured
voltage differential limit in relation to the rated voltage configuration.
This means that the voltage window dV [%] is in relation to the rated voltage
configuration [%].
When the monitored bus frequency and voltage are within the configured differential
limits, the "Command: close MCB" relay will enable, closing the MCB, and the system will
be paralleled to the mains.
4.4.4.3.4 Prerequisites
All easYgen controllers connected to the system must have rated system frequencies and
breaker logic configured identically and the parameter "Active power load share"
(parameter ╚═▷ 5531) or "Reactive power load share" (parameter ╚═▷ 5631) must be
enabled.
4.4.4.3.5 Load-Share Interface
The easYgen utilizes a peer relationship between units to control the system. This permits
for parallel applications of up to 32 generators.
The current load-share interface is selected by parameters ╚═▷ 9924 and ╚═▷ 11986 LM
86.13.
For set-up of the load-share communication refer to ╚═▷ “3.4.5 Ethernet Interface (incl.
Remote Panel)” for information about the CAN bus connection or to ╚═▷ “4.7.5 Ethernet
Interfaces” for Ethernet
4.4.4.3.6 Load Sharing
The "Active/Reactive power load share" together with the "Active/Reactive power load
share gains" determine if and how a generator performs real power or frequency control
when paralleled with other generators in an islanded operation.
In the illustrated control system, it must be noted that each control calculates the mean
utilization factor of all controls from the data transmitted via the selected bus and then
compares this with its own utilization factor. The utilization factor is compared with the
reference variable and results in a new reference variable setpoint. Frequency and real
power control are carried out simultaneously in these controls (corresponding to the
reference variable).
Frequency control is carried out via the measured voltage/frequency of the voltage
system. The MPU is used merely for monitoring functions, or is available as a control
value to the secondary controller.

4 Configuration
4.4.4.3.6 Load Sharing
Fig. 162: Load sharing diagram

4 Configuration
4.4.4.3.7 Parameters
[Default]
9924 Load share 2 The interface, which is

Interface used for transmitting the
load share data is
configured here.
[CAN ] Use CAN interface 1.
Ethernet A Use Ethernet A interface.
CAN/EthA by LM Use CAN interface 1 but

switch to Ethernet A by
TRUE of LM 86.13
(described below).
CAN/Ethernet A Use CAN and Ethernet A

redundant
Off Deactivate load share

interface.
11986 LS interface Ethernet 2 Determined by LogicsManager Load share interface switch if

A 86.13 parameter ╚═▷ 9924 is configured
to "CAN/EthA by LM".
[(02.01 & 1) & 1]
TRUE: Use Ethernet A interface
= 11987
FALSE: Use CAN interface 1
5531 Active power load 2 [On] Active power load share is

share enabled. When multiple
generators are operating in
parallel, the real power is shared
proportionally.
Off Active power load share is

disabled
4522 Active power load 2 0.01 to 9.99 This parameter defines the impact
share gain of the active power load sharing
[1.25] error signal on the frequency/load
controller setpoint. The active
power load share gain can be
adjusted between 0.01 to 9.99.
The load controller setpoint is

considered, if an export import
power control to mains is
maintained. With a higher value
the active load sharing has a
higher correction factor in the
regulation.
Notes
This parameter replaces the

former existing weighting factor
on non-XT easYgen (ID 5530). The

4 Configuration
default gain 1.25 relates to the

50% value.
5631 Reactive power load 2 [On] Reactive power load share is

share enabled. When multiple
generators are operating in
parallel, the reactive power is
shared proportionally.
Off Reactive power load share is

disabled
4543 React. power load 2 0.01 to 9.99 This parameter defines the impact
share gain of the reactive power load sharing
[1.25] error signal on the voltage/
reactive load controller setpoint.
The reactive power load share
gain can be adjusted between
0.01 to 9.99.
The reactive load controller

setpoint is considered, if an
export/import reactive power
control to mains is maintained.
With a higher value the reactive

load sharing has a higher
correction factor in the regulation.
Notes
This parameter replaces the

former existing weighting factor of
non-XT easYgen (ID 5630). The
default gain 1.25 relates to the
50% value.
High data volume on communication ports can cause low HMI display operation dynamic.
Recommendation:
Reduce data transfer volume on CAN bus. This can be done with parameter ╚═▷
9921 »Transfer rate LS fast message«.
A general action to reduce data volume on CAN1 is disabling the TPDO1 data protocol if it
is not used. Therefore navigate to parameter ╚═▷ 9600 »COB-ID« and enter "80000000"
via front panel or "2147483648" via ToolKit.
For more information how to reduce bus load see ╚═▷ “4.4.4.3.6 Load Sharing”.
Relation "... factor" <> "... gain"
This ... gain parameter replaces the former existing (%) ... factor of non-XT easYgen. The
table below shows the relation between the old and new values.
The used defaults 1.25 / 50% ensure backward compatibility.
Weighting % LS Gain
10 2.25

4 Configuration
4.4.4.3.8 Load Share Control Grouping
Weighting % LS Gain
20 2
30 1.75
40 1.5
50 1.25
60 1
70 0.75
80 0.5
90 0.25
98 0.05
Load sharing with several gensets is possible for a supply of several split busbars. Each of
this individual groups is called a segment.
Up to four segments can be managed easily for load share by LogicsManager!
General
A group breaker splits the busbar in a way that some gensets supply one busbar and
some supply another one. However, it is necessary to group the gensets, which supply
the same busbar.
The designer of a busbar system gives all individual bus bars an own number: The
Segment Number for the easYgen is defined with ID 1723. Each easYgen is connected
with its GCB on one of these segments.
The configured segment number can be changed to one of three alternative segment
numbers by three LogicsManager equations. These LogicsManager equations stand for
the segment numbers 2, 3, or 4. They are usually controlled by circuit breaker reply
auxiliary contacts. This is finally the segment number the easYgens interacts with.

4 Configuration
☼ Example
Six gensets (G1 through G6) supply a system with two group breakers (A, B) as shown
in . All gensets have the same segment number configured #1 (parameter ╚═▷ 1723)
Fig. 163: Load sharing - grouping
Case I Group breakers A and B are closed and G1 through G6 supply the same
busbar. The same segment number is configured to each genset since
all gensets supply the same busbar.
Case II Group breaker A is closed and group breaker B is open (G1 through G4
supply a different busbar than G5 and G6). A different segment number
must be selected for G5 and G6 by enabling the LogicsManager
function "Segment no.2 act" (parameter ╚═▷ 12929320) in order to
change the segment number of G5 and G6 to #2.
Case III Group breakers A and B are open (G1 and G2, G3 and G4, as well as G5
and G6 supply different busbars).
A different segment number must be selected for G3 and G4
(LogicsManager function "Segment no.2 act" (parameter ╚═▷
12929320)) as well as to G5 and G6 (LogicsManager function "Segment
no.3 act" (parameter ╚═▷ 12928320)).
With this, the segment number of G3 and G4 is changed to #2 and the
segment number of G5 and G6 is changed to #3.
[Default]
1723 Segment number 2 1 to 32 The genset is assigned a load

share segment number with this
[1] parameter. This segment number
may be overridden by the
following parameters ╚═▷ 12929,
╚═▷ 12928, and ╚═▷ 12927.

4 Configuration
12929 Segment no.2 act 2 Determined by LogicsManager Once the conditions of the
this genset is assigned load share
segment number 2 (this
parameter has priority over
parameters ╚═▷ 12928 and ╚═▷
12927).
[(0 & 1) & 1] Notes

12928 Segment no.3 act 2 Determined by LogicsManager Once the conditions of the
segment number 3 (this
parameter has priority over
parameters ╚═▷ 12927).
[(0 & 1) & 1] Notes

12927 Segment no. 4 act 2 Determined by LogicsManager Once the conditions of the
segment number 4.
[(0 & 1) & 1] Notes

5568 Mode ext. load share 2 The operation mode for the
gateway external Woodward Load Share
Gateway (LSG) is configured here.
[0] Off
1 Woodward EGCP-2
RS-485 (P & Q)
2 Woodward SPM-D
R = 4.99k | P: 0 − 4 V (0 to 100%)
| Q: 0 − 5 V (-85% to +85%)
Woodward MFR 15
R = 4.99k | P: 0 − 4 V (0 to 100%)
3 Woodward 2301 A
R = 54.90k | P: 0 − 3 V (0 to
100%)
4 Caterpillar LSM

4 Configuration
4.4.4.3.9 Droop
R = 25.00k | P: 0 − 3 V (0 to
100%)
5 Cummins PCC 3100, 3200, 3201,

3300
R = 5.00k | P: 0 − 2.5 V (-14.1 to

121.9%) | Q: 0 − 2.5 V (-16.7% to
+125.3%)
6 POW-R-CON
R = 20.67k | P: 0 − 5 V (0 to
100%)
7 Prepared
R = 25.00k | P: -5 − +5 V (0 to
100%)
8 Prepared
R = 25.00k | P: 0 − 7 V (0 to
100%)
9 Woodward GCP/MFR
CAN (P & Q)1 − easYgens and

GCP/MFR share the same CAN bus
10 to 16 Not defined
Notes
Refer to the Load Share Gateway

(LSG) Manual 37442 for security
guidelines and detailed
information about the
configuration.
R: Internal resistance
P: Range for active power
Q: range for reactive power
4.4.4.3.9 Droop
The isochronous running frequency or voltage controllers keep the desired frequency or
voltage set point independent on the real or reactive power of the generator.
The frequency controller with activated droop behavior (LogicsManager ID╚═▷ 12904)
reduces the desired frequency setpoint dependent on the active power of the generator
(ID╚═▷ 1752). In case of a full loaded engine the frequency setpoint will be reduced with
the percentage value (ID╚═▷ 5504) related to rated frequency.

4 Configuration
4.4.4.3.9 Droop
freal
{
Frated
Droop
0.98 x Frated
P
0 Prated Prated
2
Frated: Rated Frequency Regulation: Isochronous

Prated: Rated Power Regulation: With droop
Fig. 164: Frequency controller - behavior with and without droop, diagram
The resulting frequency setpoint is calculated as follows: F'Set = FSet - (Preal * (Frated *
droop factor) / Prated)
The voltage controller with activated droop behavior (LogicsManager ID╚═▷ 12905)
reduces the desired voltage setpoint dependent on the reactive power of the generator
(ID╚═▷ 1758). In case of a full reactive loaded generator the voltage will be reduced with
the percentage value (ID╚═▷ 5604) of the rated frequency.

4 Configuration
4.4.4.3.9 Droop
Vreal
{
Vrated
Droop
0.98 x Vrated
Q
0 Qrated Qrated
2
Vrated: Rated Voltage Regulation: Isochronous

Qrated: Rated Reactive Power Regulation: With droop
Fig. 165: Voltage controller - behavior with and without droop, diagram
The resulting voltage setpoint is calculated as follows: V'Set = VSet - (Qreal * (Vrated *
droop factor) / Qrated)
Function Droop Tracking
The droop tracking for frequency/voltage control is implemented such that when the
control is switched to frequency/voltage control with droop the frequency/voltage real
value does not change at the current active/reactive load. This is provided by pre-
calculating a setpoint offset, which is needed to hold rated frequency/voltage at present
load.
This is a feature in applications where for example the load sharing over communication
interface gets lost and the number of generators remains the same.
Droop Tracking On/Off
The easYgen allows disabling the droop tracking for frequency and voltage generally. This
makes sense in applications where the number of generators can vary during running in
droop mode.
Load sharing in Droop mode On/Off
Multiple easYgens are load sharing under each other, if they run islanded from mains or
they control export/import power at a common interchange point. For dynamic reasons it
makes sense to disable the load sharing, when the easYgens running in droop or can fall
into droop mode (Missing member case).

4 Configuration
4.4.4.4 Frequency Control
ID Parameter CL Setting Range Description
[Default]
5747 Droop tracking 2 [On] The frequency and voltage setpoint offset is pre-
calculated to hold the frequency and voltage, when
control is switched into droop.
Off The setpoint offset is always zero.
5748 Load sharing in 2 [On] As long the load sharing function is enabled, it is
droop mode done in droop mode too.
Off The load sharing is generally disabled in droop

mode.
Tab. 60: Droop related parameters
Notes on kick impulse function
Frequency control provides a kick impulse function, which issues a pulse if the frequency
control deadband (parameter ╚═▷ 5550) is not exceeded and no synchronization could be
performed for 20 seconds. The function is enabled, if a synchronization is carried out.
• If the phase angle is between 0° and 180°, a "frequency lower" signal is issued.
• If the phase angle is between 180° and 360°, a "frequency raise" signal is issued.
The pulse duration is 100ms. If the synchronization still fails, another pulse will be issued
after 10 seconds.
The following conditions are required for the kick impulse function:
• Frequency control (parameter ╚═▷ 5507) is configured to "3pos controller"
• Synchronization mode (parameter ╚═▷ 5728) is configured to "RUN" or "CHECK" (or

"Controlled by LM" and RUN or CHECK enabled by the LogicsManager)
Analog Managers to define input signal of frequency setpoint (1, 2) are available in
ToolKit by
• a click from screen/page "Configure frequency control"

or
◦ on two times "next page", or
• search for one of the frequency controlled value shown at the status screen

4 Configuration
• a click from screen/page "Configure frequency control"

• search (for parameter)
[Default]
5090 Proportional gain 2 2 0.01 to 100.00 This parameter defines the

proportional coefficient that
[1.00] specifies the gain of the 2nd PID
controller. By increasing the gain,
the response is increased to
permit larger corrections to the
variable to be controlled. The
farther outside tolerances the
process is, the larger the response
the tolerance band.
5091 Integral gain 2 2 0.01 to 100.00 This parameter defines the

integral gain that identifies the I
[1.00] part of the 2nd PID controller. The
integral gain corrects for any
same.
This parameter permits the user

to adjust how quickly the reset
attempts to correct for any offset.
5092 Derivative ratio 2 2 0.01 to 100.00 This parameter defines the D part
of the 2nd PID controller. By
increased. The controller will
attempt to slow down the action
of the actuator in an attempt to
prevent excessive overshoot or
undershoot. Essentially this is the
brake for the process. This portion
of the PID loop operates anywhere
within the range of the process
unlike reset.
5097 Frequency control 2 Enum Determining the speed source for

with the frequency controller.
MPU
Enum: The rpm value is internally
[Gen. frequency] calculated to an Hz value and

4 Configuration
provided to the frequency

controller.
MPU: The source for the speed

control is the speed input. Usually
the connected MPU or the J1939
speed. Refer to ID 15155 Engine
speed source" for more
information.
Gen.frequency: The electrical

frequency in Hz is the source.
Note: If MPU is enabled check

carefully the relation ship rpm to
electrical frequency. Refer to
parameter "1601 Engine rated
speed" , "1600 Speed input" and
"1602 Fly wheel teeth".
5507 Frequency control 2 [PID analog] The frequency is controlled using

an analog PID controller.
3pos controller The frequency is controlled using

a three-step controller.
Off Frequency control is not carried

out.
5508 Freq. control initial 2 0.0 to 100.0% The value entered for this
[50.0%] point for the analog output to the
(Frequency control speed controller.
initial state)
Notes
If the output to the speed control

has been disabled, the output will
act as a control position reference
point.

controlled.
The farther outside tolerances the

process is, the larger the response
the tolerance band.
Notes


frequency control (parameter ╚═▷
analog".
part of the PID controller.
[1.00]

4 Configuration
The integral gain corrects for any

same.

Notes
The integral gain constant must

be greater than the derivative
time constant. If the integral gain
constant is too large, the engine
will continually oscillate.

small, the engine will take too
long to settle at a steady state.

analog".
D part of the PID controller.
[0.01]
By increasing this parameter, the
brake for the process.
This portion of the PID loop

operates anywhere within the
Notes

analog".

5550 Deadband 1 0.02 to 9.99 Hz islanded operation
[0.08 Hz] The generator frequency is

the measured frequency does not
deviate from the configured
setpoint by more than the value
frequency raise/lower signal to the
frequency control.

4 Configuration

the frequency bias output control
or the raise/lower relay contacts.
Example
• If the frequency setpoint is

50 Hz and a deadband of 0.5
Hz is configured, the
measured generator
frequency must exceed 50.5
Hz (50 + 0.5) to issue a lower
pulse or fall below 49.5 Hz
(50 - 0.5) to issue a raise
pulse.
Synchronization
The generator frequency is

the measured frequency does not
deviate from the monitored
reference (mains or busbar)
frequency by more than the value
frequency raise/lower signal to the
frequency control.

the frequency bias output control
or the raise/lower relay contacts.
The value configured for this
parameter must be less than the
value configured for the df max
(maximum frequency differential)
for synchronization.
Notes

controller".
configured here.
[0.05 s]
The shortest possible pulse time
overshoot of the desired speed
reference point.
Notes

controller".
[5.0]
deviation from the frequency
reference.

4 Configuration

to be controlled. The farther out of
Notes


controller".
[1.0] time).

pulses increases.
Notes

controller".
5553 Expand deadband 1 1.0 to 9.9 If the measured generator

factor frequency is within the deadband
[1.0] range (parameter ╚═▷ 5550) and
the configured delay expand
configured here.
Notes

controller".
5554 Delay expand 1 1.0 to 9.9 s The measured generator

deadband frequency must be within the
[2.0 s] deadband range for the time
configured here in order to
multiply the deadband with the
factor configured in parameter
╚═▷ 5553.
Notes

controller".

4 Configuration
5518 AM Frequency SP1 2 Determined by AnalogManager The Frequency setpoint 1 source

[Hz] 81.03 may be selected from the
available data sources.
[A1 = 05.51 Internal f setp1
[Hz]] The internal frequency setpoint
Notes
The frequency setpoint may be

5500 Int. freq. control 2 15.00 to 85.00 Hz The internal generator frequency
[50.00 Hz] screen.
(Internal frequency
control setpoint 1) This value is the reference for the
frequency controller when
load operations.
Generally 50 Hz or 60 Hz will be
the values entered into this
parameter. It is possible to enter a
different value here.
5519 AM Frequency SP2 2 Determined by AnalogManager The Frequency setpoint 2 source

[Hz] 81.04 may be selected from the
available data sources.
[A1 = 05.52 Internal f setp2
[Hz]] The internal frequency setpoint
Notes
The frequency setpoint may be

5501 Int. freq. control 2 15.00 to 85.00 Hz The internal generator frequency
[50.00 Hz] screen.
(Internal frequency
control setpoint 2) This value is the reference for the
frequency controller when
load operations.
Generally 50 Hz or 60 Hz will be
the values entered into this
parameter. It is possible to enter a
different value here.
5502 Slip frequency 2 0.00 to 0.50 Hz This value is the offset for the
setpoint offset synchronization to the busbar/
[0.10 Hz] utility.

4 Configuration
With this offset, the unit

synchronizes with a positive slip.
Example
If this parameter is configured to

0.10 Hz and the busbar/mains
frequency is 50.00 Hz, the
synchronization setpoint is
50.10 Hz.
Notes
The MCB can be synchronized with

an individual slip frequency (also
negative).
The activation of MCB sync. with

separate slip can be selected with
parameter ╚═▷ 5709 (HMI:
configuration | breakers | MCB)
hat comes with the MCB slip freq.
setpoint offset parameter ╚═▷
5647 (HMI: configuration |
application | controller |
frequency).
5505 Phase matching gain 2 1 to 99 The phase matching gain

multiplies the setting of the
[5] proportional gain (parameter ╚═▷
5510) for phase matching control.
5506 Phase matching df- 2 0.02 to 0.25 Hz Phase matching will only be
start enabled if the frequency
[0.05 Hz] difference between the systems to
be synchronized is below the
configured value.
12918 Setpoint 2 freq. 2 Determined by LogicsManager If this LogicsManager condition is

86.81 TRUE, the frequency setpoint 2
(Setpoint 2 frequency) will be used instead of frequency
[(0 & 1) & 1] setpoint 1. The frequency (result
of AM) ╚═▷ 5519 instead of ╚═▷
5518 will be taken into account.
Notes


5516 Start frequency 1 15.00 to 85.00 Hz The frequency controller is

control level activated when the monitored
[47.00 Hz] generator frequency has
exceeded the value configured in
this parameter.
This prevents the easYgen from

attempting to control the

4 Configuration
frequency while the engine is

completing its start sequence.
5517 Start frequency 1 0 to 999 s The frequency controller is

control delay enabled after the configured time
[5 s] for this parameter expires.
5503 Freq. control setpoint 2 0.10 to 60.00 Hz/s The different setpoint values are
ramp supplied to the controller via this
[2.50 Hz/s] ramp.
(Frequency control
setpoint ramp) The slope of the ramp is used to
value.
The faster the change in the

setpoint is to be carried out, the
greater the value entered here
must be.
5504 Frequency control 2 0.0 to 20.0% If this control is to be operated on

droop a generator in parallel with other
[2.0%] generators and frequency control
is enabled, a droop characteristic
curve must be used.
Notes
Each generator in the system will

require the same value to be
configured for the droop
characteristic, so that when the
system is stable the active power
will be distributed proportionally
among all generators in relation to
their rated power.
12904 Freq. droop act. 2 Determined by LogicsManager If this LogicsManager condition is

86.25 TRUE, the frequency droop is
(Frequency droop enabled.
active) [08.17 Missing member OR
08.06 GCB fail to open) & 1] Notes

The active droop will also be sent

to an ECU connected to the J1939
interface (CAN interface 2). This
information is independent from
the breaker states or active
controller (frequency or power
controller).
Example
• Rated power: 500 kW

• Rated frequency setpoint:
50.0 Hz
• Droop 5.0%
• Active power: 0 kW = 0% of
rated power

4 Configuration
Frequency is adjusted to:

(50.0 Hz – [5.0% * 0.0 *
50 Hz]) = 50.0 Hz.
• Active power: +250 kW =

+50% of rated power

(50.0Hz – [5% * 0.50 *
50 Hz]) = 50.0 Hz – 1.25 Hz
= 48.75 Hz.
• Active power: +500 kW =

+100% of rated power

(50.0Hz – [5% * 1.00 *
50 Hz]) = 50.0 Hz – 2.5 Hz =
47.50 Hz.
12909 Release f-control 2 Determined by LogicsManager This LogicsManager is used to

86.96 activate generally the frequency
biasing to the sub controller. If the
[(1 & 1) & 1] LogicsManager is false the output
will be on the initial state (see
parameter ╚═▷ 5508).
The LogicsManager condition

status 'TRUE' is activating the
frequency or power regulation
according to the LogigsManager
'F/P control' ID ╚═▷ 12940).
Notes

12990 2nd Frequency PIDl 2 [02.01 False And 02.01 True This LogicsManager is used to
And 02.01 True] activate the 2nd Frequency PID
controller parameter set. If the
LogicsManager output is false the
1st Frequency PID controller
parameter set is taken.
Notes


4 Configuration
4.4.4.5 Load Control
4.4.4.5 Load Control
A 2nd ramp is implemented to meet both BDEW and VDE AR-N 4105 decoupling
requirements
Additionally to the »Load control setpoint ramp« parameter ╚═▷ 5522 there is an
alternative (2nd) »Load control ramp decoupling« parameter ╚═▷ 5014 available for
ramping slower. So it is possible to follow the BDEW/VDE requirements
• after mains decoupling
and
• after »Frequency depending derating of power« (see chapter ╚═▷ “4.4.4.5.4

Derating And Uprating Of Power ”) becomes inactive.
Default ramping is backward compatible because parameter ╚═▷ 5015 per default comes
with zero.
NEW LogicsManager to disable all load ramps (BDEW)
With LogicsManager ╚═▷ 12853 It is possible to activate the fastest load ramp e.g., for
test.
4.4.4.5.1 Configure: Load Control (general)
Analog Managers to define input signal of load setpoint (1, 2, 3, 4) are available in ToolKit
by

or
• search for one of the load controlled value shown at the status screen
• a click from screen/page "General load control"

[Default]

4 Configuration
5525 Load Control 2 [PID analog] The generator load is controlled

using an analog PID controller.
3pos controller The generator load is controlled

using a three-step controller.
Off Load control is not carried out.

controlled.

the tolerance band.
Notes


load control (parameter ╚═▷ 5525)
is configured to "PID analog".
[1.00]
proportioning band.

are the same.

Notes

If the integral gain steady is too


[0.01]

4 Configuration


Notes


5560 Deadband 1 0.10 to 9.99% The generator load is controlled in

such a manner, when paralleled
[1.00%] with the mains, so that the
monitored load does not deviate
from the configured load setpoint
by more than the value configured
in this parameter without the
controller issuing a raise/lower
signal to the speed control.

the raise/lower relay contacts. The
configured percentage for the
dead band refers to the generator
rated active power
Notes

is configured to "3pos controller".
configured here.
[0.05 s]
The shortest possible pulse time
overshoot of the desired speed
reference point.
Notes

[5.0]

4 Configuration
deviation from the frequency

reference.

to be controlled. The farther out of
Notes


[1.0] time).

pulses increases.
Notes

controller".
5563 Expand deadband 1 1.0 to 9.9 If the measured generator load is

factor within the deadband range
[1.0] (parameter ╚═▷ 5560) and the
configured delay expand
configured here.
Notes

5564 Delay expand 1 1.0 to 9.9 s The measured generator load

deadband must be within the deadband
[2.0 s] range for the time configured here
in order to multiply the deadband
with the factor configured in
Notes

5522 Load control setpoint 2 0.10 to 100.0%/s The different setpoint values are
ramp 1 supplied to the controller via this
ramp. The slope of the ramp is

4 Configuration
[3.00%/s] used to alter the rate at which the

must be.
Notes

5014 Load control setpoint 2 0.01 to 100.0%/s The different setpoint values are
[0.15%/s] ramp. The slope of the ramp is
must be.
Notes

11978 2nd load control 2 Determined by LogicsManager The LogicsManager can be used to
setpoint ramp 87.77 switch from load ramp 1 to load
ramp 2 settings.
[(0 & 02.02) & 02.02]
If this LogicsManager condition is
TRUE and load ramp will be
performed, »Load control setpoint
ramp 2« will be used.
5015 Time until setpoint 2 0 to 9999 s The mains decoupling ramp (2nd
ramp reset load ramp) will be disabled after
[0 s] that time delay.
Notes
This parameter comes with

default zero for backward
compatibility (2nd load ramp
disabled). BDEW prefers 600 s.
5016 Load control setpoint 2 0.10 to 100.00 %/s The different setpoint values are
[3.00%/s] ramp. The slope of the ramp is
must be.
Notes


4 Configuration

11998 3rd load control 2 Determined by LogicsManger The LogicsManager can be used to
setpoint ramp 87.79 switch from load ramp 1 or load
ramp 2 to load ramp 3 settings. If
[(02.02 & 02.02) & 02.02] this LogicsManager condition is
performed, [Load control setpoint
ramp 3] will be used. (3rd load
control setpoint ramp has the
highest priority.)
12853 Disable load setpoint 2 Determined by LogicsManager The LogicsManager can be used to
ramp 87.76 perform fastest possible load
ramp independent from load ramp
[(02.01& 1) & 1] settings.

performed, e.g. a test with
different setpoint steps but
without any ramping is possible
like requested by BDEW.
5569 Load control 2 0.10 to 100.00 [%/sec] The ramp rate is used for the
unloading ramp unloading in parallel operation or
3.00 [%/sec] islanded operation.
5523 Load control setpoint 2 0 to 150% If the maximum generator load is

maximum to be limited, a percentage based
[100%] on the rated generator power
(parameter ╚═▷ 1752) must be
entered here. The controller
adjusts the generator in such a
manner that this value is not
exceeded. This parameter limits
the setpoint of the load controller
when the generator is in a mains
or island parallel operation.
3465 Min. Generator power 1 0 to 100% This is the minimum active power
setpoint. Any lower other active
[0%] power setpoint will be ignored!
Notes
For backward compatibility

reasons the default value is zero.
This min. value is also used for the

AnalogManager data sources ╚═▷
“9.4.2 Data Sources AM”
• 05.19 Used power setpoint

without ramp
and
• 05.20 Used power setpoint

with ramp
5524 Min. generator 2 0 to 100% If the minimum generator load is

import/export to be limited, a percentage based
on the rated generator power

4 Configuration
4.4.4.5.2 Configure: Load Setpoints
[0%] (parameter ╚═▷ 1752) must be

entered here. The controller will
not permit the load to drop below
the configured load limit value.
This parameter is only functional

when the generator is in a mains
parallel operation.
12940 P control 2 Determined by LogicsManager The LogicsManager can be used to

86.98 control whether frequency control
or active power control should be
[(04.07& 04.06) & 1] performed.

TRUE, the active power control is
performed.
Analog Managers to define input signal of load setpoint (1, 2, 3, 4) are available in ToolKit
by
• a click from screen/page "Load setpoints"

or
• search (for parameter)
[Default]
5526 Load setpoint 1 2 Import The value entered for the import
level shall always be supplied by
the utility. All load swings are
absorbed by the generator(s)
provided the load rating for the
generator(s) is not exceeded. The
generator will always start when
an import power operation is
enabled.
Export The value entered for the export

level shall always be supplied to
an export power operation is
enabled.
[Steady] The generator shall always supply

the value entered for the steady
power level. All load swings are
absorbed by the utility. The
generator will always start when a
steady power (base load)
operation is enabled.

4 Configuration
5520 Int. load control 2 0.0 to 99999.9 kW The load setpoint 1 is defined in
setpoint 1 this screen. This value is the
[100.0 kW] reference for the load controller
(Internal load control when performing parallel
setpoint 1) operations.
5539 AM ActPower SP1 2 Determined by AnalogManager The load setpoint 1 source may be
[kW] 81.05 selected from the available data
sources.
[A1 = 05.54 Internal P setp1
[kW]] The internal load setpoint 05.54
Notes
The load setpoint may be adjusted

between 0 and the configured
load control setpoint maximum
enabled.

enabled.

sources.
Notes


4 Configuration

12919 Setp. 2 load 2 Determined by LogicsManager If this LogicsManager condition is

86.82 TRUE, the ActPower setpoint 2 will
(Setpoint 2 load) be used instead of ActPower
[(0 & 1) & 1] setpoint 1. The ActPower (result of
AM) ╚═▷ 5540 instead of ╚═▷
5539 will be taken into account.
Notes


enabled.

enabled.

sources.
Notes

4 Configuration


87.67 TRUE and »Setp. 2 load« is not
(Setpoint 3 load) TRUE, the frequency setpoint 3
[(0 & 1) & 1] will be enabled., i.e. the setting of
parameter ╚═▷ 5606 overrides the
setting of parameter ╚═▷ 5539.

TRUE, the frequency setpoint 3
will be used instead of frequency
setpoint 2. The ActPower SP3
(result of AM) ╚═▷ 5606 instead of
╚═▷ 5539 will be taken into
account.
Notes


enabled.

enabled.


4 Configuration
4.4.4.5.3 Configure: Warm-up
sources.
Notes


87.75 TRUE and neither »Setp. 2
(Setpoint 4 load) load« nor »Setp. 3 load« is true,
[(0 & 1) & 1] the frequency setpoint 4 will be
enabled, i.e. the setting of
parameter ╚═▷ 5609 overrides the
Notes


4.4.4.5.3 Configure: Warm-up
[Default]
5532 Warm-up load limit 2 0 to 100% The maximum load is limited to

this percentage of the generator
[15%] rated power (parameter ╚═▷
1752) until the warm-up time
(parameter ╚═▷ 5534) has expired
or the warm-up temperature
threshold (parameter ╚═▷ 5546)
has been exceeded.
5534 Warm-up time 2 0 to 9999 s The maximum load is limited to

the value configured in
[0 s] parameter ╚═▷ 5532 for the time
configured here.
Notes
This parameter is only effective if

"Warm-up mode" (parameter ╚═▷
5533) is configured to "Time
controlled".

4 Configuration
4.4.4.5.4 Derating And Uprating Of Power
5533 Warm-up mode 2 Analog val contr The maximum load is limited to
the value configured in parameter
╚═▷ 5532 until the temperature
measured according to the setting
in parameter ╚═▷ 5538 has
exceeded the threshold configured
in parameter ╚═▷ 5546.
[Time controlled] The maximum load is limited to

the value configured in
parameter ╚═▷ 5532 until the
time configured in parameter ╚═▷
5534 has expired.
5546 Warm-up threshold 2 0 to 1000 °C The maximum load is limited to

the value configured in parameter
[80 °C] ╚═▷ 5532 until the temperature
has exceeded the threshold
configured here.
Notes

5533) is configured to "Analog val
contr".
5538 AM Warm-up 2 Determined by AnalogManager The engine warm-up criterion may

criterion 81.02 be selected from the available
data sources.
[A1 = 10.01 ZERO]
Notes

5533) is configured to "Analog val
contr".
General notes
The current active power setpoint can be derated to a defined value according to the
application.
To ensure high flexibility the easYgen-XT offer the following derating functions:
• Direct derating
(Derating to the value of an analog manager. Refer to ╚═▷ “6.3.16.1 Direct

Derating”.)
• Derating according to a characteristic curve
(Derating according to a configured e.g. temperature characteristic. Refer to ╚═▷

“6.3.16.2 Derating With Characteristic Curve”.)
• J1939 (ECU) derating
(Derating driven by ECU to prevent knocking of the engine. Refer to ╚═▷ “6.3.16.3
J1939 (ECU) Derating”.)
• Frequency depending derating

4 Configuration
(Requirement of some grid codes. Refer to ╚═▷ “4.4.4.5 Load Control”.)
Application fields
Derating examples:
• A fire pump is mechanically connected to an engine by a clutch. In this case the

engine shall provide a limited amount of electrical power for the load sharing.
• An asynchronous load sharing is required. It is possible to operate an engine with

limited power (e.g. if there is a new engine or after maintenance).
Uprating example:
• A single engine shall run with a higher load than the others e.g. for load test.
Block Diagram
This diagram shows the different paths of the selected derating sources:

4 Configuration
Fig. 166: Derating of Active Power
Derating priority
If more than one derating function is configured the one which calculates the lowest
setpoint becomes effective.

4 Configuration
Derating Parameters
[Default]
Tab. 61: Parameters
15149 Direct derating on/off 2 On Only the analog source is used for
the up-/derating. The parameters
15143, 15144, and 15145 are not
visible neither in the HMI nor in
ToolKit.
[Off] The free derating function uses

the parameters 15143, 15144,
and 15145 for the calculation from
the derating value. This
parameters are visible in the HMI
and ToolKit.
15143 Start derating at 2 -032000 to 032000 This parameter defines the

starting point when the derating
[1000] becomes active. The value applies
to the analog source (parameter
╚═▷ 15147).
Value of the analog source which

starts derating.
15144 Stop derating at 2 -032000 to 032000 This parameter defines (in

combination with parameter ╚═▷
[0] 15143) the ramp of the derating
function.
Value of the analog source which

ends derating.
15145 Max. power deviation 2 1.0 to 100.0% This parameter defines the
maximal power deviation of the
[100.0%] derating function. That means it
determines also the minimal
power while derating is active.
100% minus this value is the

lowest P value reachable by free
derating.
The configured percentage for the

max. power deviation refers to the
generator rated active power
15146 Free derating 2 Determined by LogicsManager This LogicsManager equation

87.60 releases the free derating
function.
[(02.01 & 1] & 1]
15147 AM Derating source 2 Determined by AnalogManager This parameter defines the analog
81.21 source »Analog input 1« which
controls the derating function.

4 Configuration
4.4.4.5.5 Active Power – Frequency Function P(f)
[A1 = 06.01 Analog input 1]
15142 J1939 derating 2 To prevent knocking in the engine,

(see some ECUs (Engine Control Unit)
chapter transmit a J1939 CAN message to
below derate the power (in percentage
too) of rated power). The easYgen is
able to accept this message and
to derate the power according to
this message. If derating is active,
the display shows the indication
“Derating”.
On The derate command issued from

the ECU via J1939 message is
accepted.
[Off] The derate command via ECU is

ignored.
Indication of derating
Where? What? Remarks
HMI "Derating active" ID 13281 (for protocols state indication)
"Uprating active" ID 13287 (for protocols state indication)
Value of derating The value is representing the derating in percent (not

the resulting setpoint). For this reason this value
becomes negative in case of uprating.
As LM command variable 05.16 for derating If derating is active “Derating active” is shown in the
status message and command variable 05.16
becomes active.
05.17 for uprating If uprating is active “Uprating active” is shown in the

status message and command variable 05.17
becomes active.
Event list entry
The value of derating is shown under [Status menu / Next page / Setpoints / Derating]. In
case of derating this value has positive in case of uprating has negative sign.
Introduction
The FNN VDE-AR-N 4105 / 4110 requests an active power control to stabilize the grid
during mains faults. To maintain this the easYgen can be configured to:
• f depending derating of power OR
• f depending uprating of power OR
• both.
The reference for the uprating or derating power can be calculated out of the actual
power or the rated power. This is differently treated in grid codes 4105 and 4110.

4 Configuration
Function
Fig. 167: De/Uprating of active power setpoint due mains stabilization
Derating:
If the mains frequency exceeds the f start value ID 5782 the device calculates a power
reduction in relation to the configured rate.
If the mains frequency exceeds the f stop value ID 5095 the calculation will be disabled
and the active power controller regulates its original active power setpoint. Should the
active power setpoint be changed meanwhile the mains failure power ramp will be
activated.

4 Configuration
Uprating
If the mains frequency underruns the f start value ID 5094 the device calculates a power
increase in relation to the configured rate. If the mains frequency exceeds the f stop value
ID 5095 the calculation will be disabled and the active power controller regulates its
original active power setpoint. Should the active power setpoint be changed meanwhile
the mains failure power ramp will be activated.
Frequency value for up/derating:
According to the VDE-AR-N 4110 a 200ms moving average mains frequency value is used.
The frequency can be picked up under ID 236 or is usable via the AnalogManager variable
“02.90 Mains freq.200ms [Hz]”.
[Default]
5807 Up/derating based on Rated power The reference for the active power
derating/uprating is adjustable with this
[Actual power] parameter.
Rated power: In the moment of up/

derating start the engine rated power is
taken and from this value the
percentage rating is calculated.
Actual power: In the moment of up/

derating start the actual power is stored
and from this value the percentage
rating is calculated.
Parameter Derating
[Default]
5781 Function On The f depending derating of power can

be enabled here.
[Off]
On: Active power derating is enabled.
Off: Active power derating is disabled
5782 f start value 15 to 85Hz If the mains frequency is higher than the
start value the frequency depending
[50.20Hz] derating function is enabled.
5783 f stop value 15 to 85Hz The frequency depending derating

function stops, if the mains frequency is
[50.15Hz] lower than the stop value.
5784 f dep.derating 1 to 100% Depending on the actual mains

frequency, the generator active power
[40%] decreases with the gradient value in
relation to the active power the
reference value.

4 Configuration
5785 Hold max. derating On It can be determined, whether the max.

calculated reduction value shall be hold.
[Off] In that case the last highest reduction
rate is kept until the the f-stop value is
underrun.
[Off]: The reduction is executed along

the reduction line.
[On]: The reduction is executed and

hold along the reduction line. With
underrun the F stop value the reduction
is reset.
Parameter Uprating
[Default]
5093 Function On The f depending uprating of power can

be enabled here.
[Off]
On: Active power uprating is enabled.
[Off]: Active power uprating is disabled
5094 f start value 15 to 85Hz If the mains frequency is lower than the
start value the frequency depending
[49.8Hz] uprating function is enabled.
5095 f stop value 15 to 85Hz The frequency depending uprating

function stops, if the mains frequency is
[49.85Hz] higher than the stop value.
5096 f dep.uprating 1 to 100% Depending on the actual mains

frequency, the generator active power
[40%] increases with the gradient value in
relation to the active power the
reference value.
Configuration Test possibility for f dependent up/derating
For test purposes it is possible to configure a "Mains voltage test frequency" which is
passed to the uprating and derating characteristics.
[Default]
5808 Enable mains test frequency On For test purposes it is possible to

configure a "Mains voltage test
[Off] frequency" which is passed to the
uprating and derating
characteristics.
On:The mains test frequency is

used for f- dependent up-/derating

4 Configuration
instead of the measured mains

frequency.
[Off]: The test frequency is

disabled and the measured mains
frequency is used.
Note:Enable mains test

frequency" is reset to Off
automatically after 1 hour.
5809 Mains test frequency 15 to 85Hz If parameter 5808 is “On” this

value is used for f- dependent up-/
[50.00Hz] derating instead of measured
mains frequency.
Start conditions
The power derating function becomes active, if the following conditions are true:
• Mains frequency > FStart (parameter ╚═▷ 5782) AND
• Mains parallel operation active (MCB and GCB are closed) AND
• easYgen is in AUTOMATIC mode AND
• The corresponding controller functions are switched "On"
Stop conditions
The power derating function becomes inactive and will be reset, if at least one of the
following conditions is true:
• Mains frequency < FStop (parameter ╚═▷ 5783) OR
• Mains parallel operation not active (MCB and GCB are open ) OR
• easYgen is not in AUTOMATIC mode OR
• The corresponding controller functions are switched "Off"
AnalogManager sources:
These analog variables indicate the derating respectively uprating percent value:
• 05.28 P derating(f) [%] (same value as 10341)
• 05.48 P uprating(f) [%] (same value as 10357)
Visualization
Values which indicate the actual active power stored when the derating respectively
uprating function has started:
• 4613 f dep. Uprating P reference [%]
• 10357 f dep. Uprating P reference [%]
Values which indicate the derating respectively uprating percent value:
• 10341 Freq. dep. derating of power [%]

4 Configuration
• 10356 Freq. dep. Uprating of power [%]
Values which indicate the resulting setpoint:
• 10358 Setpoint derating of power [kW]
• 10359 Setpoint uprating of power [kW]
Examples Power Derating
If the frequency increases the value FStart (Parameter ╚═▷ 5782), the momentary power
of the generator will be memorized by the controller as an internal value PM. (P
measured) and indicated at “4613 f dep. Derating P reference” [%]. Now, the power will
be derated with a gradient R [%/Hz](parameter ╚═▷ 5784).
All examples are using the following values:
• Prated = 200 kW
• PM = 130 kW
• R = 40%/Hz (parameter ╚═▷ 5784)
• FStart = 50.20 Hz (parameter ╚═▷ 5782)
• FMains = 50.50 Hz
The power derating ΔP may be calculated using the following formulas:
• ΔPkW = PM [kW] x R [%/Hz] x (FMains [Hz] - FStart [Hz]) / 100 [%]
• ΔP% = PM [%] x R [%/Hz] x (FMains [Hz] - FStart [Hz]) / 100 [%]
Example 1: Power derating with “5807 Up/derating based on" Actual power
• The power derating ΔPkW is calculated as follows:
◦ ΔPkW = 130 kW x 40 %/Hz x (50.50 Hz - 50.20 Hz] / 100% = 15.6 kW
◦ “10358 Setpoint derating of power” indicates 114.4 kW (130 kW – 15.6 kW)
• The power derating ΔP% is calculated as follows:
◦ ΔP% = 65 % x 40 %/Hz x (50.50 Hz - 50.20 Hz] / 100% = 7.8 %
◦ “10341 Freq. dep. derating of power” and “05.28 P derating(f) [%]” indicates
7.8 %
The derating becomes inactive, if the frequency becomes lower than FStop (Parameter
╚═▷ 5783) ). (If the frequency becomes too high, the frequency monitoring function trips.)
Example 2: Power derating with “5807 Up/derating based on" Rated power
• The power derating ΔP may be calculated using the following formulas: The power
derating ΔPkW is calculated as follows:
◦ ΔPkW = 200 kW x 40 %/Hz x (50.50 Hz - 50.20 Hz] / 100% = 24 kW
◦ “10358 Setpoint derating of power” indicates 104 kW (130 kW – 24 kW).

4 Configuration
4.4.4.5.6 Photovoltaic (PV) load reduction regulated mode
• The power derating ΔP% is calculated as follows:
◦ ΔP[%] = 100 % x 40 %/Hz x (50.50 Hz - 50.20 Hz] / 100 % = 12 %
◦ “10341 Freq. dep. derating of power” and “05.28 P derating(f) [%]” indicates 12
%
The derating becomes inactive, if the frequency becomes lower than FStop (Parameter
╚═▷ 5783). (If the frequency becomes too high, the frequency monitoring function trips.)
Example 3: Explanation of Parameter “5785 Hold max.derating”:
If the frequency decreases, while the derating is still active, the behavior depends on
parameter “Hold max.derating” (parameter ╚═▷ 5785)
The following assumptions are made:
• The corresponding parameters are set to default
• Derating has started with FStart = 50.20 Hz with PM = 130 kW
• The current frequency is 50.70 Hz → reduction ΔP = 26 kW current power = 104 kW
Now the measured frequency decreases to 50.50 Hz:
• Hold max. derating” (parameter ╚═▷ 5785) = Off
The derating ΔP decreases to 15.6 kW according to the gradient 40 %/Hz the power
is increasing to 114.4 kW.
• Hold max. derating” (parameter ╚═▷ 5785) = On
The derating still remains at 26 kW the power remains at 104 kW. During an active
derating process, the power will never increase again. The power can only increase
again if the derating becomes inactive, that means that the measured frequency has
reached FStop.
General notes
The easYgen offers a function to reduce the power output of photovoltaic inverter (PV
Inverter). This could be important in cases where Gensets running side by side with PV
inverter. Mainly in island applications where the consumer load can be so low that a fixed
PV power drives the Gensets into reverse power. But even in cases where a minimal
generator load output is underrun over longer time it is beneficial to reduce the PV power.
To maintain this, the easYgen offers a PV load reduction respectively a PV load setpoint to
send to the PV inverter.
The PV load reference function contains a monitor of generator reverse power. It can
be used e.g. to open the PV inverter breaker when the reverse power becomes critical.
(Refer to ╚═▷ “4.5.6.15 Monitoring PV load reference”).
Function
With knowing the system load the easYgen3000XT regulates the PV power so that a given
generator load level is kept.
The PV regulation output is PID control loop based on:

4 Configuration
• The generator real load [%]
• The configurable generator minimal load [%]╚═▷ 8914
To control the PV inverter, the easYgen3000XT calculates next:
• The AM variable 10.39 PV load ref. [%] (PV set-point value 0% - 100%, can be
transferred to the PV inverter over an analog output)
• LM command variables (in applications using discrete load steps these LMs can be
transferred to the PV inverter over several digital outputs):
◦ 04.74 PV load ref. 0%
◦ 04.75 PV load ref. 30%
◦ 04.76 PV load ref. 60%
◦ 04.77 PV load ref. 100%
In addition, the variable ”10.39 PV load ref. [%]“ (ID 9766) can be sent to the PV inverter
via MODBUS TCP using the MODBUS MASTER (╚═▷ “6.5.5 Modbus master”)function of the
easYgen3000XT. It is indicated also in ToolKit with a gauge.
The regulation output (analog or in steps) is treated as follows:
• If the Function is disabled (by parameter ╚═▷ 8911), the output 10.39 PV load ref.
[%] is 0%.
• If the Function is enabled and LM ”Release PV regulation“ (parameter ╚═▷ 8928) is

FALSE, the output 10.39 PV load ref. [%] is 100% and 04.77 PV load ref. 100% is
TRUE.
• If the Function is enabled and LM ”Release PV regulation“ (parameter ╚═▷ 8928) is

TRUE, the output 10.39 PV load ref. [%] shows the current PID value and the
corresponding LM "PV load ref." is TRUE.
To provide a proper function the PV reduction must be tracked slowly. Reverse power of
the generator must lead to an instant cut of the PV load.

4 Configuration
Overview PV load reduction regulated mode
Photovoltaic
Load Reduction
P PV load
EG3000XT 1(3) ph voltage
AC
measurement
3 Digital outputs
DI/DO
Breaker feedback
GCB
Logics & Com

3ph voltage
Analog- CANopen
Manager 0%; 30%; 60%; 100%
Genset power ~
control
algorithm
AO
3ph current
PV
0%...100% power =
Inverter
(+/-20mA; +/-10V)
0%...100% power
Com Modbus TCP
PID Modbus
Regulation Master
HMI
G
Fig. 168: Overview PV load reduction regulated mode
Parameter
Navigate to [Parameter / Configuration / Configure application / Configure Controller /

Miscellaneous / PV load reference].
[Default]
8911 PV load reference 2 [Off] The function is disabled. The

output value remains 0%.
Regulated The PV load reference function is

enabled. If LogicsManager 8928 is
true too, the PV function with the
minimum load setpoint configured
by AnalogManager 8914 becomes
active.
8928 Release PV 2 Determined by LogicsManager If this LogicsManager condition is

regulation 87.80 TRUE and 8911 is ”Regulated“,
the PV regulation becomes active.
[(0 & 1) & 1]
FALSE and 8911 is ”Regulated“,
the regulation output 10.39 PV
load ref. [%] goes on 100% and
the load step 04.77 PV load ref.
100% goes TRUE.


4 Configuration

controlled.

the tolerance band.
Notes

[1.00]
proportioning band.

are the same.

Notes

If the integral gain steady is too

[1.00]

8920 Sampling time 2 0.1 to 99s This is the time between two
consecutive samples.
[0.5s]
8916 Deadband 2 0.0 to 10.0% The dead band function can be

taken to minimize the interaction
between genset control and PV

4 Configuration
4.4.4.6 PID {x} Control
[2.00%] inverter when a tolerance window

is matched.
8930 Setpoint ramp 1 0.1 to 10.0%/s This is the setpoint ramp for the
actual generator minimal load if
[1.0%/s] the regulation is enabled.
8921 Delay load increase 1 0.1 to 999.0s In applications using discrete load
step steps the next increasing step can
[10.0s] be delayed here.
8922 Delay load decrease 1 0.1 to 999.0s In applications using discrete load
step steps the next decreasing step
[5.0s] can be delayed here.
8912 Int.setpoint gen.min 1 1.0 to 100.0% This is the generator load level
load which shall be preferably not
[30.0%] underrun by PV power. The value
configured here is available as
analog variable ”15.01 Int.SP
gen.load [%]“.
8914 AM Setpoint 2 Determined by AnalogManager With this AnalogManager the

gen.min.load generator setpoint minimal load
81.34: [A1 = 15.01 Int.SP can be dynamically determined.
gen.load [%]]
General notes
The easYgen provides three additional freely configurable PID controllers. These
controllers are intended and optimized for slow processes, like temperature control for
heating systems (CHPO applications). The controller can either operate as a PID analog
controller or a three-position controller.
[Default]
16338 Description 2 user-defined This text will be displayed on the

Setpoints screens. The text may
16339 [PID controller {x}] have 1 through 16 characters.
16348
Notes

5571 PID{x} control 2 On The PID controller is enabled.
5584 [Off] No control is carried out.
5670

4 Configuration
5580 PID{x} ctrl.release 2 If this LogicsManager condition is

PID{x} Determined by TRUE, the PID {x} controller will
5593 LogicsManager be released.
5679 87.17, 87.18, 87.19
[(0 & 1) & 1]
= 11406/11407/11408
Notes


5585 [1.000] the gain, the response is
5671 corrections to the variable to be
controlled.

5586 [0.100] integral gain corrects for any
5672 process variable) automatically
proportioning band.
The integral gain automatically

changes the output signal until
the process variable and the
setpoint are the same. The
integral gain constant must be
greater than the derivative time
constant.

large, the controlled value will
continually oscillate. If the integral
gain constant is too small, the
controlled value will take too long
to settle at a steady state.
5587 [0.001] increasing this parameter, the
5673 increased. The controller will

4 Configuration
configured here. The shortest
5588 [0.05 s] possible pulse time should be
configured, but the actuator
5674 should still react safe, to limit
overshoot of the desired value
reference point. (Only three-
position controller)
5576 Deadband 1 0 to 32000 Shows the adjust range around

the setpoint value when no
5589 [10] displace impulse is issued. This
avoids an unnecessary abrasion of
5675 relay contacts for higher/lower.
(Only three-position controller)
5578 PID{x} control actual 2 Determined by AnalogManager The PID {x} control actual value
value may be selected from the
5591 81.14, 81.16, 81.18: [A1 = 10.01 available analog data sources. It is
ZERO] possible to select all data sources
5677 (╚═▷ “9.4.2 Data Sources AM”).
5577 PID{x} control 2 Determined by AnalogManager The PID {x} control setpoint
setpoint source may be selected from the
5590 81.13, 81.15, 81.17: [A1 = available analog data sources. It is
05.75/76/77 Int. PID{x} possible to select all data sources
5676 setpoint] (╚═▷ “9.4.2 Data Sources AM”).
5579 Int. PID{x} control 1 -32000 to 32000 The internal setpoint is defined in
setpoint this screen. This value is the
5592 [0] reference for the PID {x}
controller.
5678
5581 PID{x} control initial 2 0 to 100% The value entered for this
5594 [50%] point for the analog output to the
controller as long as the
5680 LogicsManager is false. If the PID
controller has been disabled (e.g.
Parameter ╚═▷ 5571), the bias
output will change to 0 %.
5582 Sampling time 2 1 to 360 s The sampling time is configured

here. This is the time between two
5595 [1 s] consecutive samples.
5681 The sampling time shall be

configured high enough that the
actual value can react in case e.g.
a temperature just shifts slowly.
5692 Actuator run time 2 0.1 to 999.0 s The actuator run time is
configured here. This is the time
5693 [30.0 s] the actuator needs to move from
fully closed to fully open. This
5694 information is necessary because
the controller does not receive a
feedback of the actuator position
and needs this value to calculate
the desired actuator position.

4 Configuration
4.4.4.7 Discrete Raise/Low Function
5734 PID{x} control PI 1 0 to 32000 The PI band is configured here to

band encounter excessive overshoot of
5735 [2000] the process value when starting
up. The PI band defines the range
5736 around the setpoint, in which the I
portion of the PID controller is
active.
If the actual value is outside of

this band, the I portion is reduced
to a minimum value. The PI band
is not that important for three-
position controllers and should be
disabled by entering a high value
(e.g. default value).
5737 PID{x} control 2 1 to 32000 The different setpoint values are

5738 [10] ramp to prevent an overshoot of
the process value when enabling
5739 the controller.
The slope of the ramp is used to

must be.
7494 Unit 2 User-defined up to 6 characters This parameter is assigning a unit

text text to the displayed analog value.
7495
[______] Notes
7496

39 but depends on numbers of
Bytes for each character. The
Bytes/character are defined by the
font of the currently selected
language.
Up to six characters are

best for display/HMI; more will
override screen border/frame.
display for best view!
General notes
The frequency / load and voltage / reactive power setpoints may be raised and lowered
using the LogicsManager functionality, i.e. it is possible to use LogicsManager command
variables to raise and lower these setpoints. In this case the discrete raise/lower function
always starts with the rated value (frequency / load and voltage / reactive power).
Most commonly a button may be used to energize a discrete input on the control, which is
used again as a LogicsManager command variable to enable the respective
LogicsManager function to change the setpoint.

4 Configuration
Frequency and voltage may be adjusted within the configured operating limits (╚═▷
“4.5.1.1 Generator Operating Ranges: Voltage / Frequency / Busbar”). Active power may
be adjusted between 0 and the configured load control setpoint maximum
(parameter ╚═▷ 5523). The power factor may be adjusted between 0.71 leading and 0.71
lagging.
[Default]
12900 Discrete f/P + 2 Determined by LogicsManager Once the conditions of the

the frequency / load setpoint will
[(0 & 1) & 1] be raised.
Notes

12901 Discrete f/P - 2 Determined by LogicsManager Once the conditions of the

the frequency / load setpoint will
[(0 & 1) & 1] be lowered.
Notes

12902 Discrete V/PF + 2 Determined by LogicsManager Once the conditions of the

the voltage / reactive power
[(0 & 1) & 1] setpoint will be raised.
Notes

12903 Discrete V/PF - 2 Determined by LogicsManager Once the conditions of the

the voltage / reactive power
[(0 & 1) & 1] setpoint will be lowered.
Notes

5024 Discrete ramp f +/- 2 000.01 ... 100.00 %/s Configurable ramp rate for
frequency setpoint raise and lower
[000.07 %/s] commands.

4 Configuration
4.4.5 Configure Operation Modes
5025 Discrete ramp V +/- 2 000.01 ... 100.00 %/s Configurable ramp rate for voltage
setpoint raise and lower
5026 Discrete ramp P +/- 2 000.01 ... 100.00 %/s Configurable ramp rate for active
power setpoint raise and lower
5027 Discrete ramp Power 2 000.01 ... 100.00 %/s Configurable ramp rate for Power
Factor +/- Factor (PF) setpoint raise and
[007.50 %/s] lower commands.
4.4.5 Configure Operation Modes
4.4.5.1 Operation Modes: General
Priority of operation modes
The priority of operation modes is well defined from highest to lowest priority:
• »STOP« is higher than

• »MANUAL« is higher than
• »AUTOMATIC« is higher than
• »TEST«
[Default]
1795 Startup in mode 2 If the controller is powered down,

the unit will start in the following
(Operating mode after configured mode when it is
applying the power powered up again.
supply )
[STOP] The unit starts in the STOP
operating mode.
AUTO The unit starts in the AUTOMATIC

operating mode.
MAN The unit starts in the MANUAL

operating mode.
Last The unit starts in the last

operating mode the control was in
prior to being de-energized.
TEST The unit starts in the TEST

operating mode.
Notes
For the selection of the operating

mode via the LogicsManager (if
two different operating modes
have been selected
simultaneously) the control unit
will prioritize the modes as
follows:

4 Configuration
4.4.5.1 Operation Modes: General
• 1. STOP
• 2. MANUAL
• 3. AUTOMATIC
• 4. TEST
12510 Operat. mode AUTO 2 WARNING! In Operation mode AUTO

(intentionally):
(Activate operating
mode AUTOMATIC ) • the STOP button on front
panel is without function and
• the soft buttons for operation
mode selection are not
displayed.
Notes
If both Operation mode AUTO and

╚═▷ 12120 Start req in AUTO are
active the generator will start
automatically with
acknowledgment of the latest
failure.
Determined by LogicsManager Once the conditions of the

the unit will change into operating
[(0 & 1) & 1] mode AUTOMATIC.
= 10715 Notes

12520 Operat. mode MAN 2 Determined by LogicsManager Once the conditions of the
(Activate operating the unit will change into operating
mode MANUAL) [(0 & 1) & 1] mode MANUAL.
= 10716 If MANUAL mode is selected via

the LogicsManager it is not
possible to change operating
modes via the front panel.
Notes

12530 Operat. mode STOP 2 Determined by LogicsManager Once the conditions of the
mode STOP) [(0 & 1) & 1] mode STOP.
= 10717 If STOP mode is selected via the

LogicsManager it is not possible to
change operating modes via the
front panel.
Notes


4 Configuration
4.4.5.2 Operation Mode AUTO - Automatic Run

12271 Operat. mode TEST 2 Determined by LogicsManager Once the conditions of the
mode TEST) [(0 & 1) & 1] mode TEST.
= 12272 If TEST mode is selected via the

LogicsManager it is not possible to
change operating modes via the
front panel.
Notes

General notes
The start of the engine can be performed via the following different logical conditions.
• A discrete input
• A temperature level
• An interface start condition
• A start request from the LDSS function
• A timer
• Any logical combination
If this logical output becomes TRUE in AUTOMATIC operating mode, the generator starts
and the GCB will be closed. The simultaneous activation of other LogicsManager outputs
(e.g. Stop req. in Auto) may affect this function.
The breaker handling depends on the configured application mode and breaker logic.
Refer to ╚═▷ Fig. 169 and ╚═▷ “9.3.4 Logical Outputs” for the priority of the logical
outputs in case that more than one logical output is TRUE.

4 Configuration
Engine start conditions
Fig. 169: Automatic run - engine start conditions
[Default]
12120 Start req. in AUTO 2 Determined by LogicsManager Once the conditions of the
(Start request in the control issues a start request
operation mode [(09.02 Discrete input OR 0) in AUTOMATIC mode.
AUTOMATIC) OR 04.13 Remote request]
Notes
= 10708
≥1: math. "OR"
12190 Stop req. in AUTO 2 Determined by LogicsManager If this logical output becomes
86.10 TRUE, it inhibits all other start
(Stop request in processes (e.g. Start req. in Auto,
operation mode [(0 & 1) & 1] emergency power, etc.). Stopping
AUTOMATIC) of the engine can be initiated
= 10709 externally via a discrete input or
any logical combination.
Once the conditions of the

LogicsManager have been fulfilled,
the control issues a stop request
in AUTOMATIC mode.
Notes
It is possible to interrupt an
already activated emergency run.


4 Configuration
4.4.5.3 Operation Mode TEST

12540 Start w/o load 2 Determined by LogicsManager If this LogicsManager condition is

86.19 TRUE switching from mains to
(Start without assuming generator supply following an
load ) [(0 & 1) & 1] engine start is prevented (the GCB
close operation is blocked).
= 10718
This function may be used to
perform a test operation. If an
emergency power case occurs
meanwhile, it is still possible to
change to generator operation.
If this condition becomes TRUE in

islanded operation, the GCB
cannot be opened before the MCB
has been closed.
Notes

Fig. 170: TEST button
Operation mode TEST gives the opportunity to test the genset. It can be activated via HMI
button »TEST« or parameter 4672 »Test run mode«.
When the Test Run is time restricted:
• The remaining time is displayed on HMI.

• The device can change its operating mode after execution of the TEST mode.
In TEST mode the breakers are operated like in the application mode configured. The
handling in the setpoint screen is be the same like in the AUTOMATIC mode.
Emergency run (AMF) and sprinkler run -- if configured -- both are fully supported.
[Default]
4672 TEST run mode 2 [No load w/o time] With enabling the operation mode
TEST, the engine starts

4 Configuration
[Default]
automatically. The GCB remains

open.
OFF It is not possible to enable the

operation mode TEST.
No load w. time With enabling the operation mode

automatically. The GCB remains
open. After a configurable time
(╚═▷ 4679), the device switches to
the operation mode configured
with parameter ╚═▷
4680 »Operation mode after
TEST«.
Load w/o time With enabling the operation mode

automatically. The GCB will be
closed according to the
configured »Breaker transition
mode« (╚═▷ 3411).
If mains parallel operation is

configured, the current active and
reactive power setpoint is
controlled.
Load with time With enabling the operation mode

automatically. The GCB will be
closed according to the
configured »Breaker transition
mode« (╚═▷ 3411).
If mains parallel operation is

configured, the current active and
reactive power setpoint is
controlled. After a configurable
time (╚═▷ 4679), the device
switches to the operation mode
configured with parameter ╚═▷
4680 »Operation mode after
TEST«.
Breaker access With enabling the operation mode

automatically. From there on the
breakers can be operated
manually according to the
configured „Breaker transition
mode“ (╚═▷ 3411).
Notes
In breaker transition mode

“parallel” the MCB open and close
commands are not supported.
4679 TEST mode time 2 [60 s] This is the time duration for the
restriction time restricted TEST mode.
0..9999 s
4680 Operation mode after 2 This is the operation mode, on

TEST which the genset control changes
after the time restricted TEST run.
After the TEST run ...

4 Configuration
4.4.5.4 Critical Mode
[Default]
[STOP] ... the genset control switches

back to the STOP operation mode.
Last ... the genset control switches

back to the latest operation mode.
MAN ... the genset control switches

back to the MANUAL operation
mode.
AUTO ... the genset control switches

back to the AUTOMATIC operation
mode.
Control in TEST mode is application specific:
Breaker Transition Symbol Available functionality in TEST mode

Mode
Parallel
• The MCB is not active
• With the GCB button the load test can be started and
interrupted
• If the GCB trips the load test is interrupted
Interchange
• With the GCB button and the MCB button the load test can be
started and interrupted
• The load transfer is similar to the AUTOMATIC mode
• If the GCB trips the load test is interrupted and the MCB will
be closed if the condition matches:
◦ Release MCB
◦ Mains okay
(similar to the closing in AUTOMATIC mode)
Closed transition / Open

transition • With the GCB button and the MCB button the load test can be
started and interrupted
• If the GCB trips the load test is interrupted and the MCB will
be closed if the condition matches:
◦ Release MCB
◦ Mains okay
(similar to the closing in AUTOMATIC mode)
External
• The MCB button isn't active
• With the GCB button the load test can be started and
interrupted
• Only the GCB open logic is active similar to AUTOMATIC mode
• If the GCB trips the load test is interrupted
4.4.5.4 Critical Mode
The critical mode may be used to operate a fire engine pump or any other critical
operation which does not allow a shutdown of the genset under any alarm conditions.

4 Configuration
4.4.5.4.1 Critical Operation At Busbar
The LogicsManager is used to define the conditions that will enable the critical mode like
a discrete input (for conditions and explanation of programming refer to ╚═▷ “9.3.1
LogicsManager Overview”).
Alarm classes
When critical mode is enabled the alarm classes are reclassified as follows:
Alarm classes
Normal operation A B C D E F
Critical mode A B B B B B
During the postrun time all shutdown alarms become active again.
Critical mode "On"
A critical mode will be initiated/started once the critical mode operation LogicsManager
output becomes TRUE (logic "1"). The "Critical mode" message is displayed on the display
screen. If the engine is not already running, the controller will attempt to start the engine
as configured (parameter ╚═▷ 4102). All shutdown alarms become warning messages
(see above).
Critical mode "Off"
A critical mode will be interrupted/stopped once critical mode operation LogicsManager

output becomes FALSE (logic "0") and the postrun time has expired. During the postrun
time all shutdown alarms become active again.
If the operation mode changes to STOP, the postrun time will still be performed.
Refer to ╚═▷ “9.3.4 Logical Outputs” for more information about the priorities of the
logical outputs.
The fire engine pump mentioned before or other critical operation is connected to the
busbar, i.e. it requires a closed GCB to be supplied by the generator during critical
operation.
Parameter ╚═▷ 4100 (Close GCB in critical mode) should be configured to "Yes" and an
external provision for load reduction should be provided. This ensures the pump operation
of a sprinkler system.
Application and breaker transition mode remain as configured.
A mains parallel operation is possible.

4 Configuration
Fig. 171: Critical operation at busbar
The GCB will not be closed if the load is supplied by the mains until the mains fail and the
MCB remains closed because emergency run (parameter ╚═▷ 2802) is disabled.
Critical mode during mains supply
If critical mode is enabled during mains supply (MCB is closed), the generator will be
started (if not already running) and the GCB will be closed.
• The "Critical mode" message is displayed on the display screen. All shutdown alarms
become warning messages.
• If critical mode is disabled again, all shutdown alarms become active again.
If the genset was not running before critical mode has been enabled, it will be stopped
after the critical mode postrun time (parameter ╚═▷ 4102) has expired. MCB operation
will be performed according to the configured transition mode.
Emergency power during critical mode
If there is a mains failure during critical mode, the "Emerg/Critical" message is displayed
on the display screen after the mains fail delay time (parameter ╚═▷ 2800) has expired.
All shutdown alarms become warning messages.
• Critical mode ends before mains recovery:
◦ The emergency power operation will be continued and all shutdown alarms
become active again.
◦ If the mains returns, the unit transfers the load from generator supply to mains
supply after the mains settling delay expires.
• Emergency power operation ends before the end of the critical mode:
◦ The critical mode is maintained and the load is transferred from generator
supply to mains supply after the mains settling delay expires.
◦ If open transition mode is configured, the GCB will not be opened to prevent a
dead busbar.
◦ The engine remains running until the conditions for the critical mode are no
longer existent.

4 Configuration
◦ If the genset was not running before critical mode has been enabled, it will be
stopped after cool down time (parameter ╚═▷ 3316) has expired.
◦ The GCB will take the same state as it had before the critical mode has been
enabled.
Critical mode during emergency power
An emergency power operation is active (load is supplied by the generator, GCB is closed,
MCB is open). If critical mode is enabled now, the GCB remains closed and the "Emerg/
Critical" message is displayed on the display screen. All shutdown alarms become
warning messages.
◦ If the mains return, the unit transfers the load from generator supply to mains
supply after the mains settling delay expires, if Enable MCB (parameter ╚═▷
12923) has been enabled.
◦ The engine remains running until the conditions for the critical mode are no
longer existent.
enabled.
Start request during critical mode
The critical mode operation has a higher priority than the remote request (Start/Stop
request in AUTO). Therefore, the remote request cannot start or stop the engine and has
no effect on the breaker positions. The "Critical mode" message is displayed on the
display screen and all shutdown alarms become warning alarms.
• Critical mode ends before the start request is terminated:
◦ The engine continues running. All shutdown alarms will become active again.
◦ By resetting the start request the GCB will be opened and the engine will be
stopped.
• Start request will be terminated before the critical mode is terminated:
◦ The critical mode operation is continued.
◦ The engine keeps running until the conditions for the critical mode are no
longer fulfilled and all shutdown alarms will become active again.

4 Configuration
4.4.5.4.2 Critical Operation At The Generator
enabled.
The fire engine pump mentioned before or other critical operation is connected to the
generator, i.e. it does not require a closed GCB to be supplied by the generator during
critical operation.
Parameter ╚═▷ 4100 (Close GCB in critical mode) should be configured to "No". This
ensures an open GCB during critical mode. A closed GCB is possible in case of an
emergency operation.
Fig. 172: Critical operation at the generator
Critical mode during mains supply
If critical mode is enabled during mains supply (MCB is closed), the generator will be
started (if not already running) and operated with open GCB. The "Critical mode"
message is displayed on the display screen. All shutdown alarms become warning
messages.
If critical mode is disabled again, all shutdown alarms become active again. If the genset
was not running before critical mode has been enabled, it will be stopped after the critical
mode postrun time (parameter ╚═▷ 4102) has expired.
Emergency power during critical mode
If there is a mains failure during critical mode, the MCB will be opened after the mains fail
delay time (parameter ╚═▷ 2800) has expired and the GCB will be closed. It is not
necessary to configure parameter ╚═▷ 4101 (Break emerg. in critical mode) because the
critical operation is already supplied. The "Emerg/Critical" message is displayed on the
display screen and all shutdown alarms become warning messages.
◦ If the mains returns, the unit transfers the load from generator supply to mains

4 Configuration
◦ The GCB will be opened without unloading (transition mode interchange or

parallel).
◦ All shutdown alarms become active again.
Critical mode during emergency power
An emergency power operation is active (load is supplied by the generator, GCB is closed,
MCB is open). If critical mode is enabled now, the GCB will be opened dependent on the
setting of the parameter ╚═▷ 4101 (Break emerg. in critical mode) and a closure of the
GCB is prevented for this time. The "Emerg/Critical" message is displayed on the display
screen and all shutdown alarms become warning messages.
◦ If the mains return, the unit transfers the load from generator supply to mains
◦ The GCB will be opened without unloading (transition mode interchange or

parallel).
◦ All shutdown alarms become active again.
Start request during critical mode
The critical mode operation has a higher priority than the remote request (Start/Stop
request in AUTO). Therefore, the remote request cannot start or stop the engine and has
no effect on the breaker positions. The "Critical mode" message is displayed on the
display screen and all shutdown alarms become warning alarms.
◦ The engine continues running and a change to generator or parallel operation is

performed.
◦ All shutdown alarms will become active again.
◦ The critical mode operation is continued. The engine keeps running until the
conditions for the critical mode are no longer fulfilled and all shutdown alarms
will become active again.

4 Configuration
◦ The GCB will take on the same state as it has before the critical mode has been
enabled.
Critical mode during start request
The generator supplies the load and the GCB is closed. If critical mode is enabled, the
MCB will be operated according to the configured transition mode (parameter ╚═▷ 3411).
The GCB will be opened without unloading (transition mode interchange or parallel). The
"Critical mode" message is displayed on the display screen and all shutdown alarms
become warning alarms.
◦ The engine continues running and a change to generator or parallel operation is

performed.
◦ All shutdown alarms will become active again.
◦ The critical mode operation is continued.
◦ The engine keeps running until the conditions for the critical mode are no
longer fulfilled and all shutdown alarms will become active again.
Critical mode during islanded operation
The busbar is supplied by the generator and emergency run (parameter ╚═▷ 2802) is
disabled. If the critical mode is enabled, the GCB will be opened although the MCB is not
enabled. This will cause a dead busbar.
[Default]
12220 Critical mode 2 Determined by LogicsManager If this logical output becomes

86.28 TRUE in AUTOMATIC operating
mode, it starts the critical mode.
[(0 & !05.08 Start fail) & !
09.01 DI01] Notes

4109 Critical mode postrun 2 0 to 6000 s The critical mode operation is

continued for the time configured
[600 s] here after the critical mode
request has been terminated.
The message "Cool down" is

displayed and the LogicsManager
command variable 04.10 becomes
TRUE.

4 Configuration
4.4.5.5 Load Dependent Start/Stop (LDSS)
4100 Close GCB in critical 2 Yes If a critical mode operation is

mode detected the GCB will close.
[No] The GCB cannot be closed during

a critical mode operation.
Notes

application mode A03 A04 .
4105 Critical mode alarm 2 Yes The critical mode alarm classes
class MAN will override the normal operation
alarm classes when in MANUAL
(Critical mode alarm operation mode so alarm classes
classes active in become restricted to WARNING
MANUAL operating level - NO engine shut down.
mode ) LogicsManager output ╚═▷ 12220
becomes TRUE.
[No] The alarm classes will not be

changed in the MANUAL operating
mode e.g. engine shut down is
possible!
4.4.5.5 Load Dependent Start/Stop (LDSS)
General notes
Load-dependent start/stop may either be performed according to a system reserve power

or the generator load depending on the configuration of the "Start stop mode"
Refer to ╚═▷ “9.6.2 Load Dependent Start Stop (LDSS) Formulas” for all formulas related
to the LDSS function.
4.4.5.5.1 Generator Load
If the "Start stop mode" (parameter ╚═▷ 5752) is configured to »Generator load«, load-
dependent start stop is performed in a way that the next genset will be started if all
gensets in operation reach the maximum generator load (parameter ╚═▷ 5762 or ╚═▷
5770 "IOP/MOP Max. generator load"), a configured percentage (e.g. 80%) of the rated
power. In order to stop one generator, the load of all gensets in operation must fall below
the minimum generator load (parameter ╚═▷ 5763 or ╚═▷ 5771 "IOP/MOP Min. generator
load"), a configured percentage (e.g. 30%) of the rated power. There are different
setpoints for islanded and mains parallel operation.
The LDSS algorithm acting on »Generator load« offers different dynamic levels:
• With higher dynamic the efficiency can be increased, but the change of generators
becomes more frequent.
• With lower dynamic the efficiency can be lower for the first couple of engines, but
overall the change of generators becomes less frequent.
Three levels of Dynamic
High:

4 Configuration
4.4.5.5.1 Generator Load
• After removing of generator rated power the new generator load level shall not lay
higher than 75% within the Add-on / Add-off band.
Moderate:
over 50% within the Add-on / Add-off band.
Low:
over 25% within the Add-on / Add-off band
An additional dynamic parameter (parameter ╚═▷ 5757 or ╚═▷ 5758 "IOP/MOP Dynamic")
with levels "Low", Moderate", and "High" prevents the gensets from being started and
stopped continuously if only a few gensets are in operation.
This function provides an easy calculation for the start of the next genset.
• Refer to the description of the dynamic parameters for detailed information.
The following parameters need to configured for this operation:
Parameter ID Parameter text Note
5757 IOP Dynamic only for islanded operation
5758 MOP Dynamic only for mains parallel operation
5767 MOP Minimum load only for mains parallel operation
5769 MOP Hysteresis only for mains parallel operation
5770 MOP Max. generator load only for mains parallel operation
Tab. 62: Load-dependent start/stop - parameters for generator load operation
Islanded operation (IOP)
If the configured maximum generator capacity utilization is exceeded, another genset will
be added.
• PGNreal active > Pmax. load islanded
If the configured minimum generator capacity utilization has been fallen below, a genset
will be stopped depending on the dynamic setting (parameter ╚═▷ 5757).
• PGN real active < Pmin. load islanded
Mains parallel operation (MOP)
If the required generator load setpoint for the control at the mains interchange point
exceeds the MOP minimum load threshold (parameter ╚═▷ 5767), the first genset will be
added.
• PMNsetpoint – PMNreal > PMOPminimum

4 Configuration
4.4.5.5.2 System Reserve Power
If at least one genset is supplying the load in parallel with the mains and the total
generator load exceeds the MOP maximum generator load threshold (parameter ╚═▷
5770), another genset will be added.
• PGNreal active > Pmax. load parallel
If at least two gensets are supplying the load in parallel with the mains and the
configured minimum generator capacity utilization has been fallen below, a genset will be
stopped depending on the dynamic setting (parameter ╚═▷ 5758)
• PGNreal active < Pmin. load parallel
If one genset is supplying the load in parallel with the mains and the generator load
exceeds the MOP minimum load threshold (parameter ╚═▷ 5767) minus the hysteresis
(parameter ╚═▷ 5769), the genset will be stopped.
The hysteresis is intended to prevent frequent starting and stopping of gensets in case of
small load variations.
• PMNsetpoint – PMNreal + PGN real active < PMOP minimum – Physteresis MOP
If the "Start stop mode" (parameter ╚═▷ 5752) is configured to "Reserve power", load-
dependent start stop is performed in a way that a configured minimum reserve power is
maintained in the system. This means that there is always enough reserve power for load
swings on the busbar regardless of the generator load. The actual reserve power in the
system is the total rated power of all gensets on the busbar minus the actual total
generator real power.
This functionality provides high system reliability and is intended for applications that
require a dedicated reserve power on the busbar, independent of the number of gensets
on the busbar.
The following parameters need to configured for this operation:
Parameter ID Parameter text Note
5760 IOP Reserve power only for islanded operation
5761 IOP Hysteresis only for islanded operation
5767 MOP Minimum load only for mains parallel operation
5768 MOP Reserve power only for mains parallel operation
5769 MOP Hysteresis only for mains parallel operation
Tab. 63: Load-dependent start/stop - parameters for reserve power operation
Note:
It is also possible to change the effective reserve power via interface. Refer to:
• ╚═▷ “Remote LDSS IOP reserve power ”

• ╚═▷ “Remote LDSS MOP reserve power ”

4 Configuration
Islanded operation (IOP)
• PReserve = Prated active – P GN real active
• Prated active = PRatedGen[1] + PRatedGen [2] + … + PRatedGen [n]
(total rated power of all gensets on the busbar in the system)
• P GN real active = PActualGen [1] + PActualGen [2] + … + PActualGen [n]
(total actual load of all gensets on the busbar in the system)
If the reserve power falls below the IOP reserve power threshold (parameter ╚═▷ 5760),
another genset will be added.
• PReserve < PReserve IOP
If the reserve power exceeds the IOP reserve power threshold (parameter ╚═▷ 5760) plus
the hysteresis (parameter ╚═▷ 5761) plus the rated load of the genset, the genset will be
stopped.
• Preserve > Preserve islanded IOP + Physteresis IOP + PRatedGen
Mains parallel operation (MOP)
• Preserve = Prated active – PGN real active
• Prated active = PRatedGen [1] + PRatedGen [2] + … + PRatedGen [n]
(total rated power of all gensets on the busbar in the system)
• PGN real active = PActualGen [1] + PActualGen [2] + … + PActualGen [n]
(total actual load of all gensets on the busbar in the system)
If the required generator load setpoint for the control at the mains interchange point
exceeds the MOP minimum load threshold (parameter ╚═▷ 5767), the first genset will be
added.
• PMN setpoint – PMN real > PMOP minimum
If at least one genset is supplying the load in parallel with the mains and the reserve
power falls below the reserve power threshold (parameter ╚═▷ 5768), another genset will
be added.
• Preserve < Preserve parallel
If at least two gensets are supplying the load in parallel with the mains and the reserve
power exceeds the MOP reserve power threshold (parameter ╚═▷ 5768) plus the
hysteresis (parameter ╚═▷ 5769) plus the rated load of the genset, the genset will be
stopped.
• Preserve > Preserve parallel + Physteresis MOP + PRatedGen

4 Configuration
4.4.5.5.3 Generator Selection
If one genset is supplying the load in parallel with the mains and the generator load
exceeds the MOP minimum load threshold (parameter ╚═▷ 5767) minus the hysteresis
(parameter ╚═▷ 5769), the genset will be stopped.
• PMN setpoint – PMN real + PGN real active < PMOP minimum – Physteresis MOP
General notes
If a genset is to be started, the genset with the highest priority configured will be started.
If a genset is to be stopped, the genset with the lowest priority configured will be
stopped.
If all gensets have the same priority, the next genset is selected according to the size of
engine, i.e. the genset combination, which allows an optimum efficiency will be used.
If all gensets have the same rated load or this parameter is disabled, the remaining hours
until the next maintenance are considered. If these are also the same, the genset with
the lowest generator number will be started first or stopped last.
Priority order:
• 1. Priority (parameter ╚═▷ 5751)
• 2. Efficiency (size of engines) (parameter ╚═▷ 5754)
• 3. Service hours (parameter ╚═▷ 5755)
• 4. Generator (device) number (parameter ╚═▷ 1702)
The load-dependent start/stop function requires the following conditions have been met:
• The control has been placed in AUTOMATIC operating mode
• A start request (Start req. in AUTO, Emergency run) is active
• All LDSS parameters are configured identically for all members at the load share line
(╚═▷ “4.5.6.16 Multi-Unit Parameter Alignment”)
• The mains interchange load control (import/export power) has been enabled or the
gensets are in islanded operation
• The conditions of the LogicsManager function "Load-dependent start/stop" have

been fulfilled
[Default]
12930 LD start stop 2 Determined by LogicsManager Once the conditions of the

(Load-dependent start the load-dependent start/stop
stop) [(0 & 1) & 1] function is enabled.
= 11915 Notes

4 Configuration

5752 Start stop mode 2 [Reserve power] Load-dependent start stop is

performed in a way that a
configured minimum reserve
power is maintained in the
system. The reserve power is the
total generator rated power minus
the total actual generator power.
If the reserve power falls below

the threshold, another genset will
be started. If the reserve power is
sufficient to stop one genset
without falling below the
threshold, a genset will be
stopped.
Generator load Load-dependent start stop is

performed in a way that a
configured maximum generator
capacity utilization is not
exceeded.
If the generator capacity

utilization exceeds this threshold,
another genset will be started. If
the generator capacity utilization
is low enough to stop one genset
without exceeding the threshold
again, a genset will be stopped.
5753 Dead busbar start 2 [All] All available gensets will be

mode started in case of a dead busbar
and remain connected to the
busbar for the minimum running
time (parameter ╚═▷ 5759). Then
the gensets will be stopped
according to the configured LDSS
procedure. The start delay is
configured in parameter ╚═▷ 2800
(Mains fail delay time).
LDSS The start of the gensets will be

performed according to the
configured LDSS priority in case of
a dead busbar.
Notes
This function cannot be used as

an emergency power function in
mains parallel operations because
it cannot control the MCB
operation.
If the MCB should be operated,

the emergency run function
enabled.
5751 Base priority 2 1 to 32 The priority of the genset in the

load-dependent start/stop network
[5] is configured with this parameter
(╚═▷ “4.4.5.5.3 Generator
Selection”). The lower the number

4 Configuration
configured here, the higher the

priority.
This priority may be overridden by

the LDSS Priority parameters
(parameters ╚═▷ 12924, ╚═▷
12925, and ╚═▷ 12926).
12926 LDSS Priority 2 2 Determined by LogicsManager Once the conditions of the

the load-dependent start/stop
[(0 & 1) & 1] priority will be set to 2 (the
highest priority is valid).
= 111919
Notes


= 11920
Notes


= 11921
Notes

5754 Fit size of engine 2 This parameter defines whether

the start/stop priority order (╚═▷
“4.4.5.5.3 Generator Selection”)
considers the size of the engine
(generator rated power) or not. In
case of different sized gensets,
the control can start a genset
combination which results in
optimum efficiency.
The fuel efficiency may be

optimized when this parameter is
enabled. This parameter may be
disabled if all generators have the
same size.
Notes
The algorithm prefers one large

engine instead of multiple small

4 Configuration
engines, even if this does not

match the best possible efficiency.
If an engine selection yields a

condition, in which multiple small
engines with its rated power cover
exactly the rated power of an
possible bigger engine, the bigger
engine is preferred
Yes The priority order considers the

engine size for the start of the
next engine for gensets with the
same priority.
[No] The priority order does not

consider the rated power of the
engines to fit the best size of
engines.
5755 Fit service hours 2 With this parameter the LDSS

function can be configured to start
and stop redundant engines
according to their engine running
hours with different methods.
[Off] The engine running hours are not

considered when evaluating the
engines to be started for gensets
with same priority. The parameter
╚═▷ 5756 »Changes of
engines« has no influence and can
be ignored.
Staggered The remaining hours until the next

service is required are considered
when evaluating the engines to be
started for gensets with same
priority. The gensets are utilized in
a way that the maintenance may
be performed at different times to
ensure that not all gensets have a
downtime due to a maintenance
at the same time. The genset with
the lowest hours until the next
service will be started first.
Notes
To run this functionality properly

the maintenance call must be
acknowledged accordingly.
Equal The remaining hours until the next

service is required are considered
when evaluating the engines to be
a way that the maintenance may
be performed at the same time for
all gensets. The genset with the
highest hours until the next
service will be started first.
Notes
To run this functionality properly

the maintenance call must be
acknowledged accordingly.
Period of use The »period of use hours« (value

of ID 2580) are considered when
evaluating the engines to be

4 Configuration

a way that the period of use hours
are equalized over time for all
participating gensets. The genset
with the lowest period of use
hours will be started first.
5756 Changes of engine 2 Load dependent start stop:

Changes of engine
With setting "Off" no time slot is

considered and the change of
engine is related directly on the
passed engine hours. With a
configured time slot (32/64/128 h)
a minimum of passed engine
running hours is taken into
account before changing the
gensets.
If LDSS is configured to act on

best possible equal maintenance
hours or "period of use" hours, the
change of engines can be
determined by given time slots.
The LDSS therefore creates an
individual unit’s time group for
each engine. Refer to manual
chapter »Engine time groups« for
more details.
Notes
If the LDSS function »Fit service

hours« (parameter ╚═▷ 5755) is
enabled with "Equal" or "Period of
use" hours, this configuration gets
valid. Otherwise this parameter
can be ignored.
For more details go to chapter ╚═▷

“9.4.2.10 Group 11: Engine
values”.
[Off] No engine change will be

performed. The engines are
selected according to the setting
of parameter ╚═▷ 5755 (Fit
service hours) with 1 hour spacing
in case of load changes.
All 32/64/128 h All relevant engines are changed

with a 32/64/128 hour spacing.
Example 1
• "Changes of engines" is
configured to "All 64h"
• Generator 1 has 262
maintenance hours
remaining
maintenance hours
remaining
• The time group for generator
1 is calculated as: 262h/64h
= 4.09 = Time group 4

4 Configuration
• Both generators are in time

group 4.
Time group 4 consists of any

generator that the time
group calculation total
ranges from 4.00 through
4.99.
In this instance the assigned

generator number is used to
determine which generator is
brought online. Generator 1 will
be started.
Example 2
• "Changes of engines" is
configured to "All 64h"
maintenance hours
remaining
maintenance hours
remaining
maintenance hours
remaining
• Generators 1 and 3 are in
time group 4.
• Time group 4 consists of any
4.99.
• Generator 2 is in time group
5.
• Time group 5 consists of any
5.99.
In this instance the largest time

group will determine which
generator is brought online.
Generator 2 will be started
because it is in time group 5.
5777 LDSS sort priority 2 On The priority is considered in each

always moment.
The priority will be changed

depending on priority input and
running hours even with constant
load.
Notes

4 Configuration
4.4.5.5.4 Islanded Parallel Operation (IOP)
This parameter is only effective

if »Start stop mode« (parameter
╚═▷ 5752) is configured
to »Reserve power«.
This feature can cause more start

and stop sequences, even there is
only one additional generator
brought into the LDSS system.
[Off] The priority is depending on

priority input and running hours
but only considered, if the nominal
power in the system changes. The
nominal power changes when
another generator is to stop or to
start anyway.
Notes
This setting causes less generator

changes and brings more
calmness in the system.
5759 Minimum running 2 0 to 32000 s If a genset has been started by

time the LDSS function, it continues to
[180 s] operate at least for this time even
if it would have been stopped
before.
This timer is started with the

closure of the GCB. If an
emergency run is active (╚═▷
“4.4.6 Emergency Run”) and the
mains return, this timer will be
overridden and the load is
transferred back to the mains
after the mains settling time
(parameter ╚═▷ 2801) has
expired.
General notes
In case of an islanded parallel operation (MCB open), the first genset will be connected to
the de-energized busbar.
At least one genset must be in operation in islanded operation.
There are dedicated LDSS parameters for islanded parallel operation because the supply
of the load is important here.
[Default]
5760 IOP Reserve power 2 1 to 999999 kW The value configured for the
reserve power determines when
an additional generator will be

4 Configuration
[100 kW] started. The reserve power is the

desired spinning reserve of a
generator or generators. The
reserve power is usually
estimated as the largest load
swing that a power plant may
encounter during the time it takes
to bring an additional generator
online.
The available generator power is

calculated by adding up the
generator real power ratings of all
generators with closed GCBs. The
reserve generator power is
calculated by subtracting the
power currently being produced
by all generators with closed GCBs
from the total available generator
power.
If the actual reserve power of the

generators is less than the value
next generator will be started.
Currently available total generator
rated real power
‒ Currently available total generator

actual real power
= Reserve power
Notes

start stop mode (parameter ╚═▷
5752) is configured to "Reserve
power".
It is also possible to change the

effective reserve power via
interface (refer to ╚═▷ “Remote
LDSS IOP reserve power ”).
5648 IOP Reserve power 2 2 1 to 999999 kW The value configured for the
reserve power determines when
[200 kW] an additional generator will be
started. The reserve power is the
desired spinning reserve of a
generator or generators. The
reserve power is usually
estimated as the largest load
swing that a power plant may
encounter during the time it takes
to bring an additional generator
online.
The available generator power is

calculated by adding up the
generator real power ratings of all
generators with closed GCBs. The
reserve generator power is
calculated by subtracting the
power currently being produced
by all generators with closed GCBs
from the total available generator
power.
If the actual reserve power of the

generators is less than the value

4 Configuration

next generator will be started.
Currently available total generator

rated real power
‒ Currently available total generator

actual real power
= Reserve power
Notes

power".
12604 IOP Reserve power 2 2 Determined by LogicsManager Once the conditions of the
the 'IOP Reseve power 2'
[(0 & 1) & 1] (parameter ╚═▷ 5648) is used
instead of the 'IOP Reseve power'
= 11975 (parameter ╚═▷ 5760).
Notes

5761 IOP Hysteresis 2 1 to 65000 kW If the reserve power is sufficient to

stop one genset without falling
[20 kW] below the threshold and the
hysteresis configured here, a
genset will be stopped.
Notes

power".
5762 IOP Max. generator 2 0 to 100% If the generator load exceeds the
load threshold configured here, the
[70%] load-dependent start/stop function
will start another genset.
Notes

5752) is configured to "Generator
load".
The maximum generator load

must be configured higher then
the minimum generator load for
proper operation.
5763 IOP Min. generator 2 0 to 100% If the generator load falls below
load the threshold configured here, the
will stop a genset. If only a few
gensets are operating in a multi-

4 Configuration
genset application, the IOP

Dynamic (parameter ╚═▷ 5757)
will also be considered when
stopping a genset.
Notes

load".

proper operation.
5757 IOP Dynamic 2 The dynamic determines when to

start or stop the next genset and
shows the following behavior:
Starting genset
The control requests a certain

amount of additional load
depending on the dynamic. It may
start two or more gensets to
supply the required load. Also
refer to the following example.
Stopping genset
The dynamic determines how

soon a genset will be stopped. It
prevents continuous start and
stop if only a few gensets are in
operation. In this case, the
remaining gensets would not
reach the maximum limit if one
genset stops (if, for example, two
gensets with 100 kW rated load, a
minimum load of 40 % and a
maximum load of 70 % are
operated, the second genset will
be shut down if both reach 40 kW
and the remaining engine would
operate with 80 kW and request
the next engine and so on). The
more gensets are running, the less
the influence of this parameter.
Also refer to the following
example.
[Low] Starting genset
A larger genset is requested and it

will take longer until the next
change is required. The engines
are operated with more reserve
power. The requested load is
calculated so that the gensets will
be loaded with 25 % of the range
between minimum and maximum
generator load (parameters ╚═▷
5762 & ╚═▷ 5763) after the new
genset has been started.
Stopping genset
The genset will shut down at a

lower limit and be operated
longer. The number of gensets in
operation will remain constant for
a wider range of load. The load on

4 Configuration
the remaining gensets must not

exceed 25 % of the range
5762 & ╚═▷ 5763).
Moderate Starting genset
A medium genset is requested.

The requested load is calaculated
so that the gensets will be loaded
with 50 % of the range between
minimum and maximum
5762 & ╚═▷ 5763) after the new
Stopping genset
The load on the remaining gensets

must not exceed 50 % of the
range between minimum and
maximum generator load
(parameters ╚═▷ 5762 & ╚═▷
5763).
High Starting genset
A smaller genset is requested to

operate the engines with higher
efficiency. This may lead to more
frequent starts and stops. The
requested load is calaculated so
that the gensets will be loaded
minimum and maximum
5762 & ╚═▷ 5763) after the new
Stopping genset
The genset will be shut down

earlier. This may lead to more
load on the remaining gensets
(parameters ╚═▷ 5762 & ╚═▷
5763).
Notes

load".
Example (Starting genset)
A plant made up of several

gensets with a rated power of 50,
100, and 200 kW is configured to
a maximum generator load of
70 % and a minimum generator
load of 40 %. One genset with
200 kW is running and the actual
load reaches 140 kW. This is the
70 % maximum load limit of the
running genset and requires the
start of the next genset.

4 Configuration
• Low: a total generator rated

power of 294.7 kW is
requested and a 100 kW
genset will be started.
• Moderate: a total generator
rated power of 254.5 kW is
• High: a total generator rated
power of 224.0 kW is
Refer to ╚═▷ “9.6.2 Load

Dependent Start Stop (LDSS)
Formulas” for details about the
formulas used for calculation.
Example (Stopping genset)
Two gensets with the same rated

power are configured to a
maximum generator load of 70 %
and a minimum generator load of
40 %.
The following example shows the

load level before stopping the
second genset and the resulting
load level for the first genset
depending on the dynamic
setting.
• Low:
Load level before stopping:

23.75%
Resulting load level for

remaining engine:
47.5% (25% of the difference

between 70 and 40%)
• Moderate:

27.5%

remaining engine:
55% (50% of the difference

between 70 and 40%)
• High:

31.25%

remaining engine:
62.5% (75% of the difference

between 70 and 40%)
5764 IOP Add on delay 2 0 to 32000 s Load swings may exceed the
threshold momentarily. In order to
[10 s] prevent the engine from starting
due to short-term load swings, a
delay time may be configured.

4 Configuration
4.4.5.5.5 Mains Parallel Operation
The LDSS criterion for adding load

must be exceeded without
interruption for this delay time,
configured in seconds, prior to a
start command being issued.
If the LDSS criterion for adding

load is fallen below before the
delay time expires, the delay time
is reset and a start command is
not issued.
5765 IOP Add on delay at 2 0 to 32000 s The command to start the next
rated load genset in case a genset exceeds
[3 s] rated load will be issued after the
delay configured here has expired.
Notes
This parameter becomes only

effective in case a genset exceeds
rated load to achieve a faster start
and overrides parameter ╚═▷
5764.
5766 IOP Add off delay 2 0 to 32000 s Load swings may fall below the
[60 s] prevent the engine from stopping
The load must remain below the

hysteresis setpoint without
interruption for the delay time,
stop command being issued.
If the load exceeds the hysteresis

setpoint before the delay time
expires, the delay time is reset
and a stop command is not
issued.
General notes
In case of a mains parallel operation (MCB closed), load-dependent start stop is only
enabled, if the gensets participates in load sharing at the interchange point (all
participating gensets must be configured to the same setpoint).
A minimum load threshold must be exceeded to start the first genset, i.e. a genset will
only be started if a minimum load would be demanded from the generator.
There are dedicated LDSS parameters for mains parallel operation.
[Default]

4 Configuration
5767 MOP Minimum load 2 0 to 65000 kW For the mains interchange

(import/export) real power control
[10 kW] to function, a minimum generator
power setpoint value is required to
start the first genset.
In many cases, it is desirable that

the engine is prevented from
starting unless the generator will
operate at a specific kW level or
higher to ensure a reasonable
degree of efficiency.
Example
The mains interchange must reach

a level that will permit an 80 kW
generator to operate at a
minimum load of 40 kW prior to
the engine starting.
5769 MOP Hysteresis 2 0 to 65000 kW Start stop mode configured to

"Reserve power":
[10 kW]
If the reserve power is sufficient to
stop one genset without falling
below the reserve power threshold
and the hysteresis configured
here, a genset will be stopped.
If the generator load falls below

the minimum load threshold
minus the hysteresis configured
here, the last genset will be
stopped.
Notes
The importance of this parameter

depends on the setting of the start
stop mode (parameter ╚═▷ 5752).
It is also possible to change the

effective reserve power via
interface (refer to ╚═▷ “Remote
LDSS MOP reserve power ”).
5768 MOP Reserve power 2 0 to 999999 kW

The minimum reserve power in
[50 kW] mains parallel operation is
configured here. This is the
maximum expected load swing on
the busbar, which shall be
supported by the gensets.

this value, the load-dependent
start/stop function will start
another genset.
Notes

power".
5649 MOP Reserve power 2 2 0 to 999999 kW

4 Configuration
[100 kW] The minimum reserve power in

mains parallel operation is
configured here. This is the
maximum expected load swing on
the busbar, which shall be
supported by the gensets.

this value, the load-dependent
start/stop function will start
another genset.
Notes

power".
12605 MOP Reserve power 2 2 Determined by LogicsManager Once the conditions of the
the 'MOP Reseve power 2'
[(0 & 1) & 1] (parameter ╚═▷ 5649) is used
instead of the 'MOP Reseve power'
= 11976 (parameter ╚═▷ 5768).
Notes

5770 MOP Max. generator 2 0 to 100% If the generator load exceeds the
load threshold configured here, the
will start another genset.
Notes

load".

proper operation.
5771 MOP Min. generator 2 0 to 100% If the generator load falls below
load the threshold configured here, the
will stop a genset.
If only a few gensets are operating

in a multi-genset application, the
MOP Dynamic (parameter ╚═▷
5758) will also be considered
when stopping a genset.
Notes

load".

4 Configuration

proper operation.
5758 MOP Dynamic 2 The dynamic determines when to

start or stop the next genset and
shows the following behavior:
Starting genset
The Dynamic is only considered

for the start sequence if "Fit size
of engines" is enabled (refer to
The control requests a certain

amount of additional load
depending on the dynamic. It may
start two or more gensets to
supply the required load.
Stopping genset
The dynamic determines how

soon a genset will be stopped. It
prevents continuous start and
stop if only a few gensets are in
operation.
In this case, the remaining

gensets would not reach the
maximum limit if one genset stops
(if, for example, two gensets with
100 kW rated load, a minimum
load of 40 % and a maximum load
of 70 % are operated, the second
genset will be shut down if both
reach 40 kW and the remaining
engine would operate with 80 kW
and request the next engine and
so on).
The more gensets are running, the

less the influence of this
parameter. Also refer to the
following example.
[Low] Starting genset
A larger genset is requested and it

will take longer until the next
change is required. The engines
are operated with more reserve
power. The requested load is
calaculated so that the gensets
will be loaded with 25 % of the
(parameters ╚═▷ 5762 & ╚═▷
5763) after the new genset has
been started.
Stopping genset
The genset will shut down at a

lower limit and be operated
longer. The number of gensets in
operation will remain constant for
a wider range of load. The load on
the remaining gensets must not
exceed 25 % of the range

4 Configuration

5762 & ╚═▷ 5763).
Moderate Starting genset
A medium genset is requested.

The requested load is calaculated
so that the gensets will be loaded
minimum and maximum
5762 & ╚═▷ 5763) after the new
Stopping genset
The load on the remaining gensets

(parameters ╚═▷ 5762 & ╚═▷
5763).
High Starting genset
A smaller genset is requested to

operate the engines with higher
efficiency. This may lead to more
requested load is calaculated so
that the gensets will be loaded
minimum and maximum
5762 & ╚═▷ 5763) after the new
Stopping genset
The genset will be shut down

earlier. This may lead to more
load on the remaining gensets
(parameters ╚═▷ 5762 & ╚═▷
5763).
Notes

load".
Refer to parameter ╚═▷ 5757 for

examples on stating and stopping
a genset depending on the
dynamic setting.
5772 MOP Add on delay 2 0 to 32000 s Load swings may exceed the
[20 s] prevent the engine from starting
The LDSS criterion for adding load

must be exceeded without
interruption for this delay time,
start command being issued.

4 Configuration
4.4.5.5.6 LDSS with predicted load
If the LDSS criterion for adding

load is fallen below before the
is reset and a start command is
not issued.
5773 MOP Add on delay at 2 0 to 32000 s The command to start the next
rated load genset in case a genset exceeds
[3 s] rated load will be issued after the
delay configured here has expired.

5772.
Notes

5764.
5774 MOP Add off delay 2 0 to 32000 s Load swings may fall below the
[60 s] prevent the engine from stopping
The load must remain below the

hysteresis setpoint without
interruption for the delay time,
stop command being issued.
If the load exceeds the hysteresis

setpoint before the delay time
expires, the delay time is reset
and a stop command is not
issued.
For further information, please refer to application examples to ╚═▷ “6.3.15 LDSS with
predicted load”.
Introduction
In case of a mains failure, the usual LDSS function of the easYgen starts either one or all
generators. This is done so because during the mains failure the consumer load
information is lost. The LDSS with predicted load (LDSS PL) can start the correct amount
of generators based on the last mains power measurements (5-minutes average value).
The LDSS PL takes the 5-minutes average value as mains load into account and passes it
to the LDSS function as consumer load. The LDSS function can thereby start the correct
amount of gensets according to that predicted load. A prerequisite for this function is the
availability of a group breaker (GGB) in the application. The GGB allows to switch the
correct amount of generators onto the load.
• The LDSS PL differentiates two source modes as base for the predicted consumer
load calculation:

4 Configuration
◦ 1. Internal source mode: The mains power and breaker handling is provided by
the easYgenXT.
◦ 2. External source mode: The mains power, the MCB and GGB control is
provided by an external device (e.g. ATS), connected via CANopen with
easYgen.
General
To the time the engines are not started and the mains is feeding the load the LDSS PL
calculates a mains load with a 5-minute average value. This load value is passed to the
LDSS function as consumer load. So the LDSS can determine the correct amount of
engines which must be started if a start command becomes active. See ╚═▷ “General”:
Switches are in “Pos.1” and “Pos. A”.
In the moment the start request becomes active the average load calculation is frozen.
See ╚═▷ “General”: switches are in “Pos.2” and “Pos. A”.
If all requested engines are successful started and have closed their GCBs the LDSS PL
gives the release for closing the GGB. From this time on the 5-minute average load
calculation will be fed with the easYgen calculated generator load. See ╚═▷ “General”:
switches are in “Pos.3”; “Pos. B”
The LDSS function now does not differ anymore to the original function. There will be
started and stopped the correct generators according to the common LDSS parameters.
The External and Internal Source Mode
There is an external and an internal mode available:
The external source mode is dedicated for external installed ATS controls which measure
the mains power. The system allows up to 5 ATS controls at the Interchange point.
In this mode, external ATS controls send information via CANopen RPDO messages. The
easYgen provides information going to the ATS control.

4 Configuration
Fig. 173: External mode
The internal source mode is dedicated to use the own mains power measurement
assigned via Analogmanager .
Fig. 174: Internal mode
The external ATS control sends information in CANopen RPDO messages. The easYgen
provides information going to the ATS control.
[Default]

4 Configuration
4.4.6 Emergency Run
15026 LDSS with predicted 2 Determined by LogicsManager If the conditions of this

load 86.36 LogicsManager have been fulfilled
LDSS is working with predicted
[(0 & 1) & 1] load. Otherwise LDSS is working
normally.
9066 Predicted load source 2 internal Internal: LDSS with predicted load
is using internal data. (LM 86.09
[external] “Start req. in AUTO” and AM 81.30
“Consumer load [kW]”)
External: LDSS with predicted load

is expected data from external via
RPDOs
9059 AM Consumer load 2 AnalogManager The result (81.30) of this analog

[kW] manager provides the load for the
[╚═▷ “9.4.4 Factory Settings”] load prediction in internal source
mode
4.4.6 Emergency Run
General notes
The emergency power operation is possible only in application mode A04 (2 power circuit
breakers).
If the LogicsManager outputs 'Stop request in AUTO' or 'Inhibit emergency run' are TRUE,
an emergency power operation may be prevented or interrupted from an external
source.
Prerequisites
• The emergency power function can only be activated for synchronous generators
with parameter ╚═▷ 2802.
• Emergency power is carried out in operating mode AUTOMATIC regardless of the
status of the LogicsManager output 'Start request in AUTO' (LogicsManager).
The display indicates "Emergency run" during emergency power operation.
The following principles are observed in case of an emergency power operation:
• If an emergency power operation is initiated, the engine is started automatically,

unless the start sequence is interrupted via an alarm or prevented via the
LogicsManager or the operating mode is changed.
• The GCB can be closed regardless of the engine delay time if the generator
frequency and voltage are within the configured operating limits (╚═▷ “4.5.1.1
Generator Operating Ranges: Voltage / Frequency / Busbar”) if the parameter
"Undelay close GCB" (parameter ╚═▷ 12210) has been set accordingly (default
setting).

4 Configuration
4.4.6 Emergency Run
• If the mains return during an emergency power operation (GCB is closed), the mains
settling time (parameter ╚═▷ 2801) must expire before the load is transferred from
the generator to mains operation.
Activation of emergency power
If the mains are not within the configured frequency and voltage operating limits (╚═▷
“4.5.3.3 Mains Operating Ranges”) for at least the time configured in the parameter
"Mains fail delay time" (parameter ╚═▷ 2800), an emergency power operation is
activated.
MCB malfunction
An emergency power operation will be performed, if the control is not able to close or
recluse the MCB and the alarm "Fail to close MCB" occurs.
Mains rotation field alarm
If the mains returns after a mains failure with a reversed rotation direction the generator
remains in emergency power operation until the mains rotation matches the rotation of
the generator set.
The generator will not start upon a mains rotation field alarm, but it will keep on running
if it has already started.
The following parameters only apply to application mode A04 .
[Default]
2802 Emergency run 2 [On] If the unit is in the AUTOMATIC

operating mode and a mains fault
occurs according to the following
parameters, the engine is started
and an automatic emergency
operation is carried out.
Off No emergency operation is carried

out.
2800 Mains fail delay time 2 0.00 to 99.99 To start the engine and to carry
out an emergency operation the
(Mains failure start [3.00 s] monitored mains must be failed
delay) continuously for the minimum
period of time set with this
parameter.
Notes
This delay time starts only if the

easYgen is in AUTOMATIC

4 Configuration
4.5 Configure Monitoring
operating mode and emergency

power is activated.
This parameter is not valid in

A13 .
3408 Emerg. start with 2 [Yes]/No Emergency power operations may

MCB failure be configured with the failure of
the MCB in addition to a loss of
power on the mains supply.
Notes
An MCB breaker alarm is indicated

if parameter "MCB monitoring"
configured "On".

A13 .
12200 Inhibit emergency 2 Determined by LogicsManager Once the conditions of the

run 86.11 LogicsManager have been fulfilled
the emergency power operation
(Inhibit emerg. run) [(0 & 1) & 1] will be terminated or blocked.
= 10710 Notes
It is possible to interrupt an
already activated emergency run.


A13 .
4101 Break emerg. in 2 0 to 999 s The emergency power operations

critical mode are overridden for the configured
[5 s] time when the critical mode starts
(Override emergency in order to supply the complete
operations in critical generator power to the sprinkler
mode) pump.
4.5 Configure Monitoring
Replacement: "Delayed by engine speed" becomes "Enabled"
Formerly (non-XT easYgen) several monitoring functions could be delayed each by use of
parameter "Delayed by engine speed". Exchanging it by the new parameter "Enabled"
introduces the one-change-switch of all monitoring functions by LogicsManager 11459
LM 87.70 Release Engine Monitoring.
With software revision 1.13 or higher each monitoring LogicsManager can be enabled
alternatively by one of 32 Flags.
Factory settings ensure same behavior of each affected monitoring function as of non-XT
easYgen series before.

4 Configuration
4.5.1 Configure Generator Monitoring
4.5.1 Configure Generator Monitoring
4.5.1.1 Generator Operating Ranges: Voltage / Frequency / Busbar
The operating voltage/frequency/busbar parameters are used to check if the values are
in range when performing a dead bus closure and synchronization of the generator.
Busbar 1 must be within this ranges to synchronize the generator to the busbar.
It is recommended to configure the operating limits within the monitoring limits.
[Default]
5800 Upper voltage limit 2 100 to 150% The maximum permissible

positive deviation of the generator
(Generator maximum [110%] voltage from the generator rated
operating voltage limit) voltage (parameter ╚═▷ 1766) is
(Hysteresis: 1%) configured here.
This value may be used as a

voltage limit switch. The
conditional state of this switch
may be used as a command
variable for the LogicsManager
(02.03).
5801 Lower voltage limit 2 50 to 100% The maximum permissible

negative deviation of the
(Generator minimum [90%] generator voltage from the
operating voltage limit) generator rated voltage
(Hysteresis: 1%) (parameter ╚═▷ 1766) is
configured here.

(02.03).
5802 Upper frequency limit 2 100.0 to 150.0% The maximum permissible

positive deviation of the generator
(Generator maximum [105.0%] frequency from the rated system
operating frequency frequency (parameter ╚═▷ 1750)
limit) (Hysteresis: 0.05%) is configured here.

frequency limit switch. The
(02.04).
5803 Lower frequency limit 2 50.0 to 100.0% The maximum permissible

negative deviation of the
(Generator minimum [95.0%] generator frequency from the
operating frequency rated system frequency
limit) (Hysteresis: 0.05%) (parameter ╚═▷ 1750) is
configured here.


4 Configuration
4.5.1.1 Generator Operating Ranges: Voltage / Frequency / Busbar
[Default]

(02.04).
Tab. 64: Parameter settings: Voltage/frequency
Busbar monitoring
Busbar monitoring compares the actual voltage and frequency of the busbar with the
configured generator operating ranges. The voltage operating range is configured with
the "Upper voltage Limit" and "Lower voltage limit" parameter. The frequency operating
range is configured with the "Upper frequency limit" and "Lower frequency limit"
parameter. If the measured busbar voltage or frequency deviates from the operating
range for a time exceeding the configurable delay, an alarm will be issued.
[Default]
5118 Monitoring 2 On Monitoring is enabled
[Off] Monitoring is disabled
5122 Delay 2 0.02 to 99.99 s If one of the monitored values

exceeds the threshold value for
[10.00 s] the delay time configured here, an
alarm will be issued.
5119 Alarm class 2 Class A/B/C/D/E/F, Control Each limit may be assigned an
independent alarm class that
[B] specifies what action should be
Notes

╚═▷ “9.5.4 Alarm Classes”
5120 Self acknowledge 2 Yes The control unit automatically

clears the alarm if the fault
[No] The control unit does not

automatically reset the alarm
when the fault condition is no
longer detected.

output "External
Tab. 65: Parameter settings: Busbar

4 Configuration
4.5.1.2 Generator Voltage Monitoring
4.5.1.2 Generator Voltage Monitoring
[Default]
1770 Generator voltage 2 The unit can either monitor the

monitoring phase-neutral (wye) voltages or
the phase-phase (delta) voltages.
If the controller is used in a

compensated or isolated network,
voltage protection monitoring
should be configured as phase-
neutral to prevent earth-faults
resulting in tripping of the voltage
protections.
[Phase - phase] The phase-phase voltage will be

monitored and all subsequent
parameters concerning voltage
monitoring "generator" are
referred to this value (VL-L).
Phase - neutral The phase-neutral voltage will be

monitoring "generator" are
referred to this value (VL-N).
Notes
WARNING: This parameter defines

how the protective functions
operate.
Tab. 66: Settings: Generator Voltage Monitoring
4.5.1.2.1 Generator Overvoltage (Level 1 & 2) ANSI# 59
General notes
Voltage is monitored according to how the parameter "Generator voltage measuring"

(parameter ╚═▷ 1851) is configured. This controller provides the user with two alarm
levels for generator overvoltage. Both alarms are definite time alarms.
Monitoring for overvoltage faults is performed in two steps.
If this protective function is triggered, the display indicates "Gen. overvoltage 1" or
"Gen. overvoltage 2" and the logical command variable "06.05" or "06.06" will be
enabled.
Refer to ╚═▷ “9.1.1 Triggering Characteristics” for the triggering characteristic of this
monitoring function. The diagrams listed there show a frequency trend and the associated
pickup times and length of the alarms.
The parameter limits listed below have identical setting ranges. Each parameter may be
configured with different settings to create unique trip characteristics for specific
thresholds.

4 Configuration
4.5.1.2.1 Generator Overvoltage (Level 1 & 2) ANSI# 59
[Default]
2000 Monitoring 2 [On] Overvoltage monitoring is carried

out according to the following
2006 parameters. Monitoring is
performed at two levels. Both
values may be configured
independent from each
other (prerequisite: Level 1 limit
< limit 2).
Off Monitoring is disabled for Level 1

limit and/or Level 2 limit.
2004 Limit 2 50.0 to 150.0% The percentage values that are to

be monitored for each threshold
2010 2004: [108.0%] limit are defined here.
2010: [112.0%] If this value is reached or

exceeded for at least the delay
(Hysteresis: 0.7%) time without interruption, the
action specified by the alarm class
(Reset Delay: 80 ms) is initiated.
Notes
This value refers to the System

rated frequency (parameter ╚═▷
1766).
2005 Delay 2 0.02 to 99.99 s If the monitored generator voltage

value exceeds the threshold value
2011 2005: [5.00 s] for the delay time configured
here, an alarm will be issued.
2011: [0.30 s]
Notes
If the monitored generator voltage

falls below the threshold (minus
the hysteresis) before the delay
expires the time will be reset.
2007 2001: [B] specifies what action should be
2007: [F]
Notes


2008 condition is no longer detected.

longer detected.


4 Configuration
4.5.1.2.2 Generator Undervoltage (Level 1 & 2) ANSI# 27

output "External
2003 Enabled 2 [Always] Monitoring for this fault condition

2009
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
Voltage is monitored according to how the parameter "Generator voltage measuring"

(parameter ╚═▷ 1851) is configured. This controller provides the user with two alarm
levels for generator undervoltage. Both alarms are definite time alarms.
Monitoring for undervoltage faults is performed in two steps.
If this protective function is triggered, the display indicates "Gen. undervoltage 1" or
"Gen. undervoltage 2" and the logical command variable "06.07" or "06.08" will be
enabled.
thresholds.
This monitoring function is disabled when the idle mode (╚═▷ “4.4.1.4 Idle Mode”) is
active.
[Default]

4 Configuration
2050 Monitoring 2 [On] Undervoltage monitoring is carried

< limit 2).



Notes

1766).
2055 Delay 2 0.00 to 999 s If the monitored generator voltage

value falls below the threshold
2061 2055: [5.00 s] value for the delay time
configured here, an alarm will be
2061: [0.30 s] issued.
Notes

exceeds the threshold (plus the
hysteresis) before the delay
2057: [F]
Notes



longer detected.

output "External

4 Configuration
4.5.1.2.3 Generator Voltage Asymmetry

2053 Enabled 2 Always Monitoring for this fault condition

2059
[87.70 LM:Eng.mon] Monitoring for fault conditions is
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
The voltage asymmetry monitors absolute value of all three phase-phase voltage
difference: dV1=|V12- V23|, dV2=|V23- V31| and dV3=|V31- V12|. If one of measured dV1,
dV2 or dV3 exceeds a configured permissible asymmetrical limit, an alarm is issued.
The percentage of permissible asymmetrical limit refers to the generator rated voltage.
If this protective function is triggered, the display indicates "Gen. volt. asymmetry" and
the logical command variable "06.18" will be enabled.
monitoring function.
This monitoring function is only enabled if Generator voltage measuring (parameter ╚═▷
1851) is configured to "3Ph 4W" or "3Ph 3W".
[Default]
3900 Monitoring 2 [On] Voltage asymmetry monitoring is

carried out according to the
following parameters.
Off No monitoring is carried out.

[10.0%] limit are defined here.
(Hysteresis: 0.5%)

4 Configuration
(Reset Delay: 80 ms) If this value is reached or

time without interruption, the
is initiated.
Notes
This value refers to the Generator

1766).
3904 Delay 2 0.02 to 99.99 s If the monitored generator voltage

asymmetry exceeds the threshold
[5.00 s] value for the delay time
issued.
Notes

asymmetry falls below the
threshold (minus the hysteresis)
before the delay expires the time
will be reset
[F] specifies what action should be
Notes



longer detected.

output "External

[87.70 LM:Eng.mon] Monitoring for fault conditions is

engine monitoring".

96.{xx} TRUE.

4 Configuration
4.5.1.3 Generator Frequency Monitoring
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4.5.1.3 Generator Frequency Monitoring
4.5.1.3.1 Plausibility Check of Voltages' AC Wiring
General Notes
The easYgen-3000XT detects the frequency out of up to six voltages (L1-N, L2-N, L3-N,
L1-L2, L2-L3 and L3-L1). The frequency measurement (of all three systems) additionally
checks the values on plausibility. With this monitoring the easYgen can detect wrong
wiring issues.
Wrong Wiring Issue
It might occur that for example a generator frequency is measured even if the generator
is not running. This can happen e.g. if PE (terminal 61) is not connected, the generator
neutral connection is broken, and mains is energized with 1Ph2W connection. In this case
a potential shift occurs which could lead to "ghostly" voltages at the generator (or
busbar, or mains) phase-neutral system. This voltages lead to a frequency measurement
even if no voltage is detected in the generator phase-phase system.
The »Plausibility AC wiring « monitoring is introduced to indicate such situations at

generator, busbar, and mains measurement. These alarms are tripping if only "Phase-
Phase" or only "Phase-Neutral" frequency is detected. If such an alarm ("Gen. AC wiring",
"Busbar 1 AC wiring" or "Mains AC wiring" has tripped please check all "Phase-Phase" and
"Phase-Neutral" voltages via HMI or Toolkit to get more information and check the AC
wiring.
This »Plausibility AC wiring « monitoring function is only active if the wiring can provide
"Phase-Phase" and "Phase-Neutral" values.
The plausibility monitoring offers one setting for all three measurement systems. The
Monitor is placed under: [Parameter / Configure: Monitoring / Miscellaneous: Other
monitoring] .The alarm indications are called Gen. .../Busbar .../Mains AC wiring (see ╚═▷
“9.5.5 Alarm Messages”).
[Default]
1964 Monitoring 2 [On] Enabling Plausibility AC Wiring

monitoring.
Off Monitoring is disabled
1965 Delay 2 00.2 to 99.99 s If the monitored value

undershoots the threshold value
[00.30] for the delay time configured
1966 Alarm class 2 Class A, B, C, D, E, F, Control Each limit may be assigned an

[Class B ]

4 Configuration
4.5.1.3.2 Generator Overfrequency (Level 1 & 2) ANSI# 81O
[Default]
specifies what action should be

1967 Self acknowledge 2 [Yes] The control unit automatically

No The control unit does not

longer detected.


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
This controller provides the user with two alarm levels for generator overfrequency. Both
alarms are definite time alarms.
Monitoring for overfrequency faults is performed in two steps.
If this protective function is triggered, the display indicates "Gen. overfrequency 1" or
"Gen. overfrequency 2" and the logical command variable "06.01" or "06.02" will be
enabled.
thresholds.
[Default]
1900 Monitoring 2 [On]

4 Configuration
1906 Overfrequency monitoring is

following parameters. Monitoring
is performed at two levels. Both
< limit 2).



(Hysteresis: 0.05 Hz) time without interruption, the
Notes

1750).
1905 Delay 2 0.02 to 99.99 s If the monitored generator

frequency value exceeds the
1911 1905: [1.50 s] threshold value for the delay time
1911: [0.30 s] issued.
Notes
If the monitored generator

frequency falls below the
will be reset.
1907: [F]
Notes



longer detected.


4 Configuration
4.5.1.3.3 Generator Underfrequency (Level 1 & 2) ANSI# 81O
output "External

1909
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
This controller provides the user with two alarm levels for generator underfrequency. Both
Monitoring for underfrequency faults is performed in two steps.
If this protective function is triggered, the display indicates "Gen. underfrequency 1" or
"Gen. underfrequency 2" and the logical command variable "06.01" or "06.02" will be
enabled.
thresholds.
[Default]
1950 Monitoring 2 [On]

Underfrequency monitoring is
1956 carried out according to the
following parameters. Monitoring
< limit 2).

4 Configuration


1960: [84.0%] If this value is reached or lower for

at least the delay time without
(Hysteresis: 0.05 Hz) interruption, the action specified
by the alarm class is initiated.
(Reset Delay: 80 ms)
Notes

1750).
1955 Delay 2 0.02 to 99.99 s If the monitored generator

frequency value falls below the
1961 1955: [5.00 s] threshold value for the delay time
1961: [0.30 s] issued.
Notes
If the monitored generator

frequency falls below the
threshold (plus the hysteresis)
will be reset.
1957: [F]
Notes



longer detected.

output "External

1959

4 Configuration
4.5.1.4 Generator Current Monitoring
[ 87.70 LM:Eng.mon] Monitoring for fault conditions is

engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4.5.1.4 Generator Current Monitoring
4.5.1.4.1 Generator Time-Overcurrent (Level 1, 2 & 3) ANSI# 50/51
General notes
Current is monitored according to how the parameter "Generator current measuring"

(parameter ╚═▷ 1850) is configured. This controller provides the user with three definite
time alarm levels for generator overcurrent faults.
Monitoring of the maximum phase current is performed in three steps. Every step can be
provided with a delay time independent of the other steps.
If this protective function is triggered, the display indicates "Gen. overcurrent 1",
"Gen. overcurrent 2", or "Gen. overcurrent 3" and the logical command variable "06.09",
"06.10.", or "06.11" will be enabled.
[Default]
2200 Monitoring 2 [On] Overcurrent monitoring is carried

performed at three levels. All
2212 three values may be configured
other (prerequisite: Level 1
< Level 2 < Level 3).

limit, Level 2 limit, and/or Level 3
limit.

2216 2210: [150.0%] If this value is reached or

2216: [250.0%] time without interruption, the

4 Configuration
4.5.1.4.1 Generator Time-Overcurrent (Level 1, 2 & 3) ANSI# 50/51
(Hysteresis: 1%) action specified by the alarm class

is initiated.
(Reset Delay: 1 s)
Notes

1754).
2205 Delay 2 0.02 to 99.99 s If the monitored generator current

2211 2205: [30.00 s] the delay time configured here, an
2217 2211: [1.00 s]
Notes
2217: [0.40 s]
If the monitored generator current
2224 Voltage restraint 2 Yes The control provides voltage

monitoring restrained overcurrent relay
2225 according to ANSI 51 V
individually for each generator
2226 current monitoring function.
For details refer to ╚═▷ “4.5.1.4.3

Generator Voltage Restrained
Overcurrent Monitoring - ANSI
#51V”.
[No] Voltage restrained monitoring is

disabled.
2207 2201: [E] specifies what action should be
2213 2207: [F]
Notes
2213: [F]

2214 [No] The control unit does not

longer detected.

output "External

2209

4 Configuration
4.5.1.4.2 Generator Inverse Time-Overcurrent ANSI# IEC 255
2215
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
The current produced by the generator is monitored depending on how parameter

"Generator current measuring" (parameter ╚═▷ 1850) is configured. If an overcurrent
condition is detected, the fault recognition time is determined by the configured tripping
characteristic curve and the measured current.
The tripping time is faster as the measured current increases in magnitude according to a
defined curve. According to IEC 255 three different characteristics are available.
If this protective function is triggered, the display indicates "Inv. time overcurr." and the
logical command variable "06.22" will be enabled.
• "Normal inverse" characteristic:
t = 0.14 / (I/IP)0.02 - 1) * tP[s]
• "Highly inverse" characteristic:
t = 13.5 / (I/IP) - 1) * tP[s]
• "Extremely inverse" characteristic:
t = 80 / (I/IP)2 - 1) * tP[s]
Variables:
• t =tripping time
• tP = setting value time
• I = measured fault current
• IP = setting value current
Please take into account during configuration:
• for Istart:
Istart > In and Istart > IP
• for IP the smaller IP is, the steeper is the slope of the tripping curve

4 Configuration
The maximum tripping time is 327 s. If a tripping time greater than 327 s is configured,
an overcurrent fault condition will not be recognized.
Characteristics
Fig. 175: "Normal inverse" characteristic

4 Configuration
Fig. 176: "Highly inverse" characteristic
Fig. 177: "Extremely inverse" characteristic

4 Configuration
[Default]
4030 Monitoring 2 [On] Overcurrent monitoring is carried

parameters.
4034 Inverse time 2 Selection of the used overcurrent

characteristic characteristic.
[Normal] The "normal inverse" tripping

curve will be used
High The "highly inverse" tripping curve

will be used
Extreme The "extremely inverse" tripping

curve will be used.
4035 Inverse time 2 0.01 to 5.00 s Time constant Tp used to calculate

overcurrent Tp= the characteristics.
[0.06 s]
4036 Inverse time 2 10.0 to 300.0% Current constant IP used to

overcurr. IP = calculate the characteristics.
[100.0%]
4037 Inv time overcurr. 2 100.0 to 300.0% Lower tripping value for inverse
Istart = time-overcurrent protection. If the
[115.0%] monitored current is less than
Istart, the inverse time-overcurrent
(Hysteresis: 1%) protection does not trip. If Istart is
less than IP, IP is used as the lower
(Reset Delay: 1 s)
tripping value.
2227 Voltage restraint 2 Yes The control provides voltage

monitoring restrained inverse time
overcurrent monitoring.
For general information about

voltage restrained monitoring
refer to ╚═▷ “4.5.1.4.3 Generator
Voltage Restrained Overcurrent
Monitoring - ANSI #51V”.
[No] Voltage restrained monitoring is

disabled.
Notes


4 Configuration
4.5.1.4.3 Generator Voltage Restrained Overcurrent Monitoring - ANSI #51V


longer detected.

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General Notes
This function is an add-on to the over current monitoring and decreases the activation
limit dependent on the amount of voltage dip. Especially in near to generator located
over currents it can lead to situations, where the failure current remains under the
generator rated current. In this case a normal over current monitoring does not trip. The
voltage restraint over current monitoring considers this and decreases the configured
over current limit according to a modification factor, that it comes to a trip.
The considered voltages are either the single phase-phase or phase-neutral voltages.
(Refer to "Generator voltage monitoring" ╚═▷ 1770). The monitor takes always the lowest
considered voltage into account for calculating the modification factor.
Voltage restraint over current monitoring can be activated individually for “Generator
over current (limit 1-3)” and Generator inverse time over current, if the according
parameter 2227 “Voltage restraint monitoring” is switched to “Yes”.
The modification factor depends on the measured voltage in percent of rated voltage. It is
defined by a characteristic which is defined by three parameters (ID 2230, 2231, 2232 cf.
figure). This characteristic is taken into account for all over current monitoring functions,
if enabled.

4 Configuration
Fig. 178: Example for generator voltage restraint overcurrent characteristic
Beginning at a voltage dip of 95% rated voltage (configured by 2231), the modification
factor will be linearly reduced (cf. figure 86). If the voltage reaches 25% or less
(configured by 2230) the modification factor will remain at 25% (configured by 2232).
Now the effective limit is calculated as:
Effective limit [%] = Limit [%] * Modification Factor [%]/ 100[%]
Supposed the configured limit of an over current monitor is 110% and the measured
voltage is 25%:
Effective limit [%] =110% * 25%/100% = 27.5%
The V (voltage) start value configuration must be entered higher as the V stop value
configuration. Otherwise the function does not work properly!
ID Parameter CL Setting Description

range
[Default]
2231 V start current 2 5.0 ... 100.0% Voltage for starting current limitation reduction
lim. reduction
[95.0%]
2230 V stop current 2 5.0 ... 100.0% Voltage for stopping current limitation reduction
lim. reduction
[25.0%]

4 Configuration
4.5.1.5 Generator Power Monitoring
ID Parameter CL Setting Description

range
[Default]
2232 Min. factor 2 5.0 ... 100.0% Minimum factor limit for current limitation reduction
limit
overcurrent [25.0%]
4.5.1.5 Generator Power Monitoring
4.5.1.5.1 Generator Overload IOP (Level 1 & 2) ANSI# 32
General notes
IOP = islanded Operation in Parallel
The power produced by the generator is calculated from the voltage and current values
measured in accordance with how parameters "Generator voltage measuring" (parameter
╚═▷ 1851) and "Generator current measuring" (parameter ╚═▷ 1850) are configured. The
controller monitors if the system is in a mains parallel or an islanded operation.
When the controller detects that the system is operating islanded from the mains, the
Generator Overload MOP (refer to ╚═▷ “4.5.1.5.2 Generator Overload MOP (Level 1 & 2)
ANSI# 32”) monitoring is disabled. If the measured generator real power during an
islanded operation is above the configured limit an alarm will be issued.
If this protective function is triggered, the display indicates "Gen. Overload IOP 1" or
"Gen. Overload IOP 2" and the logical command variable "06.14" or "06.15" will be
enabled.
[Default]
2300 Monitoring 2 [On] Overload monitoring is carried out

according to the following
performed at two levels.
Both values may be configured

< Level 2 limit).


4 Configuration
4.5.1.5.1 Generator Overload IOP (Level 1 & 2) ANSI# 32


(Hysteresis: 1%) time without interruption, the
Notes

rated active power
2305 Delay 2 0.02 to 99.99 s If the monitored generator load

2311: [0.10 s]
Notes
If the monitored generator load

2307: [D]
Notes


the alarm if the fault condition is


output "External

2309
engine monitoring".

TRUE.

4 Configuration
4.5.1.5.2 Generator Overload MOP (Level 1 & 2) ANSI# 32
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
MOP = Mains Parallel Operation
measured in accordance with how parameters "Generator voltage measuring"
(parameter ╚═▷ 1851) and "Generator current measuring" (parameter ╚═▷ 1850) are
configured.
The controller monitors if the system is in a mains parallel or an islanded operation. When
the controller detects that the system is operating parallel with the mains, the Generator
Overload IOP (refer to ╚═▷ “4.5.1.5.1 Generator Overload IOP (Level 1 & 2) ANSI# 32”)
monitoring is disabled. If the measured generator real power during a mains parallel
operation is above the configured limit an alarm will be issued.
If this protective function is triggered, the display indicates "Gen. Overload MOP 1" or
"Gen. Overload MOP 2" and the logical command variable "06.23" or "06.24" will be
enabled.
[Default]
2350 Monitoring 2 [On] Overload monitoring is carried out

performed at two levels.

< Level 2 limit).




4 Configuration
Notes

rated active power
2355 Delay 2 0.02 to 99.99 s If the monitored generator load

2361: [0.10 s]
Notes
If the monitored generator load

2357: [D]
Notes




output "External

2359
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32

4 Configuration
4.5.1.5.3 Generator Reverse/Reduced Power (Level 1 & 2) ANSI# 32R/F
General notes
measured in accordance with how parameters "Generator voltage measuring"
(parameter ╚═▷ 1851) and "Generator current measuring" (parameter ╚═▷ 1850) are
configured.
The generator power limits may be configured for reduced power and/or reverse power
depending on the threshold values entered. The note below explains how a reduced or
reverse power limit is configured.
If the single-phase or three-phase measured real power is below the configured limit of
the reduced load or below the configured value of the reverse power, an alarm will be
issued.
If this protective function is triggered, the display indicates "Gen. rev./red. pwr.1" or
"Gen. rev./red. pwr.2" and the logical command variable "06.12" or "06.13" will be
enabled.
Definition
• Reduced power Fault initiated if the monitored real power falls below the configured
(positive) limit.
• Reverse power Fault initiated if the direction of the monitored real power reverses
and the configured (negative) limit is exceeded.
Configuration examples
The values for reverse /reduced power monitoring can be configured as follows:
• Level 1 limit = Positive and Level 2 limit = Positive
(whereas Level 1 limit > Level 2 limit > 0 %)
• Both limits are configured for reduced power monitoring.
☼ Example
• Rated power is 100 kW, Level 1 limit = 5 % > Level 2 limit = 3 %

• Tripping if real power falls below 5 kW (Level 1 limit) or 3 kW (Level 2 limit)
• Level 1 limit = Negative and Level 2 limit = Negative
(whereas Level 2 limit < Level 1 limit < 0%)
Both limits are configured for reverse power monitoring.

4 Configuration
☼ Example
• Rated power is 100 kW, Level 1 limit = -3 % > Level 2 limit = -5 %

• Tripping if real power falls below -3 kW (Level 1 limit) or -5 kW (Level 2 limit)
• Level 1 limit = Positive and Level 2 limit = Negative
(whereas Level 1 limit > 0 % > Level 2 limit)
• Level 1 is configured for reduced power monitoring and
• Level 2 is configured for reverse power monitoring.
☼ Example
• Rated power is 100 kW, Level 1 limit = 3 % > Level 2 limit = -5 %

• Tripping if real power falls below 3 kW (Level 1 limit) or -5 kW (Level 2 limit)
[Default]
2250 Monitoring 2 [On] Reverse/reduced power

monitoring is carried out
2256 according to the following
parameters.

independent from each other.

2254 Limit 2 -99.9 to 99.9% The percentage values that are to

2260 2254: [-3.0%] limit are defined here.
2260: [-5.0%] If this value is reached or fallen

below for at least the delay time
(Hysteresis: 1%) without interruption, the action
specified by the alarm class is
(Reset Delay: 80 ms) initiated.
Notes

rated active power (parameter
╚═▷ 1752).
2255 Delay 2 0.02 to 99.99 s If the monitored generator power

falls below the threshold value for
2261: [5.00 s]
Notes
If the monitored generator power

exceeds or falls below the

4 Configuration
4.5.1.5.4 Generator Unbalanced Load (Level 1 & 2) ANSI# 46
threshold (plus/minus the

hysteresis) again before the delay
2257: [F]
Notes



longer detected.

output "External

2259
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
Unbalanced load is monitored according to how the parameters "Generator voltage

measuring" (parameter ╚═▷ 1851) and "Generator current measuring" (parameter ╚═▷
1850) are configured. The unbalanced load alarm monitors the individual phase currents
of the generator. The percentage threshold value is the permissible variation of one phase
from the average measured current of all three phases.

4 Configuration
If this protective function is triggered, the display indicates "Unbalanced load 1" or
"Unbalanced load 2" and the logical command variable "06.16" or "06.17" will be
enabled.
This monitoring function is only enabled when Generator voltage measuring

(parameter ╚═▷ 1851) is configured to "3Ph 4W", "3Ph 4W OD", or "3Ph 3W" and
Generator current measuring (parameter ╚═▷ 1850) is configured to "L1 L2 L3".
Formulas
Phase L1 Phase L2 Phase L3
Exceeding IL1 ≥ (3 * IN * PA + IL2 + IL3) / 2 IL2 ≥ (3 * IN * PA + IL1 + IL3) / 2 IL3 ≥ (3 * IN * PA + IL1 + IL2) / 2
Falling below IL1 ≤ (IL2 + IL3- 3 * IN * PA) / 2 IL2 ≤ (IL1 + IL3- 3 * IN * PA) / 2 IL3 ≤ (IL1 + IL2- 3 * IN * PA) / 2
Examples
☼ Exceeding a limit value
• Current in phase L1 = current in phase L3

• Current in phase L2 has been exceeded
• PA = tripping value percentage (example 10 %)
• IN = rated current (example 300 A)
Tripping value for phase L2:
• IL2 ≥ (3 * IN * PA + IL1 + IL3) / 2

= (3 * 300 A * 10% + 300 A + 300 A) / 2
= ((3 * 300 A * 10) / 100 + 300 A + 300 A) / 2
= 345 A
☼ Falling below a limit value
• Current in phase L2 = current in phase L3

• Current in phase L1 has been undershot
• PA = tripping value percentage (example 10 %)
• IN = rated current (example 300 A)
Tripping value for phase L1:
• IL1 ≤ (IL2 + IL3- 3 * IN * PA) / 2

= (300 A + 300 A - 3 * 300 A * 10%) / 2
= (300 A + 300 A - (3 * 300 A * 10) / 100)) / 2
= 255 A

4 Configuration
[Default]
2400 Monitoring 2 [On] Unbalanced load monitoring is

2406 following parameters. Monitoring
is performed at two levels.

other (condition: Level 1
< Level 2).
Off No monitoring is carried out for

either Level 1 limit or Level 2 limit.


Notes
This value refers to the "Generator

rated current" (parameter ╚═▷
1754)
2405 Delay 2 0.02 to 99.99 s If the monitored current exceeds

the threshold value for the delay
2411 2405: [5.00 s] time configured here, an alarm
will be issued.
2411: [1.00 s]
Notes
If the monitored current falls

below the threshold (minus the
2407: [E]
Notes



longer detected.

4 Configuration
4.5.1.5.5 Load sharing

output "External

2409
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
Active power load sharing mismatch
[Default]
5100 Monitoring 2 On Load share monitoring is carried

parameters.
[Off] Monitoring is disabled.
4841 Limit 2 1.0 to 100.0% The percentage value that is to be

monitored for the threshold limit is
[30.0%] defined here.
If this value is reached or

is initiated.
Notes
This value is rated to the absolute

difference between generator
rated power (parameter ╚═▷
1752) and the percent average
power of the other devices. The
generator rated power is modified
by the derating factor if derating
is activated.

[10.0 s] for the delay time configured
Notes

4 Configuration
[Default]

Notes



longer detected.

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
Reactive power load sharing mismatch
[Default]
5106 Monitoring 2 On Load share monitoring is carried

parameters.
4842 Limit 2 1.0 to 100.0% The percentage value that is to be

monitored for the threshold limit is
[30.0%] defined here.

4 Configuration
[Default]

is initiated.
Notes
This value is rated to the absolute

difference between generator
rated reactive power
(parameter ╚═▷ 1758) and the
percent average reactive power of
the other devices. The generator
rated reactive power is modified
by the derating factor if derating
is activated.

[10.0 s] for the delay time configured
Notes

Notes



longer detected.

output "External


engine monitoring".

4 Configuration
4.5.1.5.6 Engine/Generator Active Power Mismatch
[Default]

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4.5.1.5.6 Engine/Generator Active Power Mismatch
General notes
If enabled, this monitoring function becomes only active if generator power control is
enabled (refer to ╚═▷ “4.4.4.5 Load Control”). If the measured generator power deviates
from the power setpoint by a value exceeding the limit configured in parameter ╚═▷ 2925
for a time exceeding the delay configured in parameter ╚═▷ 2923, an alarm will be
issued.
If this protective function is triggered, the display indicates "Gen act.pwr mismatch" and
[Default]
2920 Monitoring 2 [On] Monitoring of the generator active

power mismatch is carried out
parameters.
Off Monitoring is disabled.
2925 Limit 2 1.0 to 30.0% If the difference between the

measured generator power and
[5.0%] the power setpoint exceeds this
value for at least the delay time
(parameter ╚═▷ 2923) without
interruption, the action specified
Notes

╚═▷ 1752).
2923 Delay 2 3 to 9999 s If the monitored active power

mismatch exceeds the threshold
[30 s] value configured in
parameter ╚═▷ 2925 for the delay
time configured here, an alarm
will be issued.
Notes

4 Configuration
4.5.1.5.7 Engine/Generator Unloading Mismatch
If the monitored active power

mismatch falls below the
will be reset.
Notes



longer detected.

output "External
4.5.1.5.7 Engine/Generator Unloading Mismatch
General notes
This monitoring function is always enabled and becomes active when a stop command is
issued. Following a stop command, the controller tries to reduce the power before
opening the GCB. If the power falls below the unload limit (parameter ╚═▷ 3125) before
the delay (parameter ╚═▷ 3123) expires, a "GCB open" command will be issued. If the
controller fails to reduce the power to fall below the unload limit (parameter ╚═▷ 3125)
before the delay (parameter ╚═▷ 3123) expires, a "GCB open" command will be issued
together with an alarm.
If this protective function is triggered, the display indicates "Gen. unloading fault" and
[Default]
3120 Monitoring 2 [On] Monitoring of engine unloading is


4 Configuration
4.5.1.6 Other Monitoring
3125 Unload limit 2 0.5 to 99.9% If the monitored generator power

falls below this value, a "GCB
[3.0%] open" command will be issued.
Notes

╚═▷ 1752).
3123 Delay 2 3 to 999 s If the monitored generator power

does not fall below the limit
[60 s] configured in parameter ╚═▷ 3125
before the time configured here
expires, a "GCB open" command
will be issued together with an
alarm.
The GCB will be opened after this

time even if 3120 is configured
to OFF.
Notes



longer detected.

output "External
4.5.1.6 Other Monitoring
4.5.1.6.1 Power Factor - configure generator power factor monitoring
4.5.1.6.1.1 Generator Lagging Power Factor (Level 1 & 2)
General notes
The power factor is monitored for becoming more lagging (i.e. inductive) than an
adjustable limit. This limit may be a lagging or leading power factor limit. There are two
lagging power factor alarm levels available in the control. This monitoring function may

4 Configuration
be used for monitoring an overexcitation with a warning and a shutdown alarm level. Both
The power factor monitoring
• is activated,
if the generator current expires 5% rated Generator current and
• is blocked,
if the generator current underrun 3% rated Generator current.
╚═▷ Fig. 179 shows an example of a leading and a lagging power factor limit and the
power factor range, for which the lagging power factor monitoring issues an alarm.
If this protective function is triggered, the display indicates "Gen. PF lagging 1" or
"Gen. PF lagging 2" and the logical command variable "06.25" or "06.26" will be enabled.
Power Factor
Leading (capacitive) Lagging (inductive)
More lagging than a leading More lagging than a lagging

PF limit of -0.40 PF limit of +0.85
-0.40 +0.85
-0.50 -0.75 1.00 +0.75 +0.50
Import Inductive Power Export Inductive Power
Fig. 179: Generator lagging power factor
[Default]
2325 Monitoring 2 [On] Generator lagging power factor

parameters. Monitoring is

2329 Limit 2 -0.999 to 1.000 The values that are to be

monitored for each threshold limit
2335 2329 [+ 0.900] are defined here.
2335: [+ 0.700] Notes
(Hysteresis: 0.02%)

4 Configuration
(Reset Delay: 80 ms) If the power factor becomes more

lagging (i.e. inductive, ╚═▷
Fig. 179) than a lagging PF value
(positive) or a leading PF value
(negative) for at least the delay
time (parameters ╚═▷ 2330
or ╚═▷ 2336) without interruption,
the action specified by the alarm
class is initiated.

factor is more lagging than the
2336 2330: [30.00 s] configured limit for the delay time
2336: [10.00 s] issued.
Notes

factor returns within the limit
will be reset.
2332: [B]
Notes



longer detected.

output "External

2334
engine monitoring".

96.{xx} TRUE.

4 Configuration
4.5.1.6.1.2 Generator Leading Power Factor (Level 1 & 2)
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
The power factor is monitored for becoming more leading (i.e. capacitive) than an
adjustable limit. This limit may be a leading or lagging power factor limit. There are two
leading power factor alarm levels available in the control. This monitoring function may
be used for monitoring an under excitation with a warning and a shutdown alarm level.
Both alarms are definite time alarms.
Refer to ╚═▷ “6.3.1 Generator Excitation Protection” for a detailed description of this
The power factor monitoring
• is activated,
if the generator current expires 5% rated Generator current and
• is blocked,
if the generator current underruns 3% rated Generator current.
power factor range, for which the leading power factor monitoring issues an alarm.
If this protective function is triggered, the display indicates "Gen. PF leading 1" or
"Gen. PF leading 2" and the logical command variable "06.27" or "06.28" will be enabled.
Fig. 180: Generator leading power factor
[Default]
2375 Monitoring 2 [On] Generator leading power factor


4 Configuration



2385 2379: [- 0.900] are defined here.
2385: [- 0.700] Notes
(Hysteresis: 0.02%) If the power factor becomes more

leading (i.e. capacitive, ╚═▷
(Reset Delay: 80 ms) Fig. 180) than a leading PF value
(negative) or a lagging PF value
(positive) for at least the delay
time (parameters ╚═▷ 2380
or ╚═▷ 2386) without interruption,
class is initiated.

factor is more leading than the
2386: [10.00 s] issued.
Notes

will be reset.
2382: [B]
Notes



longer detected.

output "External

4 Configuration
4.5.1.6.2 Miscellaneous

2384
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4.5.1.6.2 Miscellaneous
4.5.1.6.2.1 Generator Ground Fault (Level 1 & 2)
General notes
The generator ground fault is determined differently depending on the following

configuration options:
• Mains current input is configured for mains current
(calculated ground fault)
• Mains current input is configured for ground current
(measured ground fault)
Refer to parameter ╚═▷ 1854.
Calculated ground fault
The current produced by the generator is monitored depending on how parameter

"Generator current measuring" (parameter ╚═▷ 1850) is configured. The measured three
conductor currents IGen-L1, IGen-L2 and IGen-L3 are vectorially totaled (IS = IGen-L1 +
IGen-L2 + IGen-L3) and compared with the configured fault limit (the calculated actual
value is indicated in the display). If the measured value exceeds the fault threshold limit,
a ground fault is present, and an alarm is issued.
Fig. 181: Generator ground fault - schematic

4 Configuration
If this protective function is triggered, the display indicates "Ground fault 1" or "Ground
fault 2" and the logical command variable "06.19" or "06.20" will be enabled.
The ground fault protection zone is determined by the location where the generator
current transformer are physically installed.
⚙ Test
1. ▷ Short-circuit one of the three generator current transformers while the generator is at
full load.
▶ The measured current should read 100% of rated on the two phases that do not have
their current transformers short-circuited.
The ground current calculation does not take current on the neutral conductor into
consideration. In order for the controller to be able to perform calculated ground fault
current protection accurately, the neutral conductor must not conduct current.
The fault threshold value is configured as a percentage. This percentage threshold refers
to the generator rated current (parameter ╚═▷ 1754). Due to unavoidable load
asymmetries, the minimum value for this parameter should be 10% or greater.
Calculation
Fig. 182: Generator ground fault - calculation
1 No ground fault
2 Ground fault (with vectorial calculation)
3 Ground fault (IS = ground fault current)
The ground current IS is calculated geometrically/vectorially. The pointers for phase

currents IL1 and IL2 are parallel shifted and lined up as shown in (╚═▷ Fig. 182/1).
The pointer between the neutral point and the point of the shifted pointer IL2' results is
the sum current IS as shown in (╚═▷ Fig. 182/2).

4 Configuration
In order to be able to add the pointers vectorially, these must be divided into their X- and
Y-coordinates (IL2X, IL2Y, IL3X and IL3Y).
The ground fault current may be calculated using the following formula:
• (IL1rated + IL2rated + IL3rated) - (IL1measured + IL2measured + IL3measured) / 1.73 = IS
• (7 A + 7 A + 7 A) – (7A + 6.5 A + 6 A) / 1.73 = 0.866 A
Results of a calculation example:
• Phase current IL1 = IRated = 7 A
• Phase current IL2 = 6.5 A
• Phase current IL3 = 6 A
Measured ground fault
Ground fault current is actively measured when the mains current input is configured to
monitor for ground current. The ground fault threshold is configured as a percentage of
the value entered for parameter "Generator rated current" (parameter ╚═▷ 1754).
The ground fault protection zone is determined by the physical installation location of the
generator current transformer.
[Default]
3250 Monitoring 2 On Ground current monitoring is

< Level 2).
[Off] Monitoring is disabled for Level 1

3254 Limit 2 0 to 300% The percentage values that are to

3260 3254: [10%] limit are defined here.
3260: [30%] If this value is reached or

Notes

rated current of the generator
(parameter ╚═▷ 1754), if the
ground current is calculated from
the generator current values.
It refers to the parameter

"Generator rated current"

4 Configuration
(parameter ╚═▷ 1754), if the

ground current is measured
directly.
The ground fault threshold must

not exceed the mains/ground
current measuring range (approx.
1.5 × Irated; ╚═▷ “8.1 Technical
Data”).
3255 Delay 2 0.02 to 99.99 s If the monitored ground fault

3261: [0.10 s]
Notes
If the monitored ground fault falls

below the threshold (minus the
3257: [F]
Notes



longer detected.

output "External

3259
engine monitoring".

96.{xx} TRUE.

4 Configuration
4.5.1.6.2.2 Generator Phase Rotation
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
NOTICE!
Damage to the control unit and/or generation equipment
• Ensure that the control unit is properly connected to phase voltages on both sides of
the circuit breaker(s) during installation.
Failure to do so may result in damage to the control unit and/or generation equipment
due to the breaker closing asynchronously or with mismatched phase rotations. Also
ensure that phase rotation monitoring is enabled at all connected components (engine,
generator, breakers, cable, busbars, etc.).
This function will block a connection of systems with mismatched phases only under the
following conditions:
• The voltages being measured are wired correctly with respect to the phase rotation
at the measuring points (i.e. the potential transformers in on both sides of the
circuit breaker)
• The voltages being measured are wired so that angular phase shifts or any
interruptions from the measuring point to the control unit do not exist
• The voltages being measured are wired to the correct terminals of the control unit
(i.e. L1 phase of the generator is connected with the terminal of the control unit
which is intended for the generator L1 phase)
• The configured alarm class is of class C, D, E, or F (shutdown alarm).
Correct phase rotation of the phase voltages ensures that damage will not occur during a
breaker closure to either the mains or the generator. The voltage phase rotation alarm
checks the phase rotation of the measured voltages and the configured phase rotation to
ensure they are identical.
The directions of rotation are differentiated as "clockwise" and "counter clockwise". With
a clockwise field the direction of rotation is "L1-L2-L3"; with a counter clockwise field the
direction of rotation is "L1-L3-L2". If the control is configured for a clockwise rotation and
the measured voltages are monitored as counterclockwise, the alarm will be initiated.
The direction of configured rotation being monitored by the control unit is displayed on
the screen.
If this protective function is triggered, the display indicates "Gen.ph.rot. mismatch" and
This monitoring function is only enabled if Generator voltage measuring (parameter ╚═▷
1851) is configured to "3Ph 4W", "3Ph 3W", or "3Ph 4W OD" and the measured voltage
exceeds 50 % of the rated voltage (parameter ╚═▷ 1766) or if Generator voltage
measuring (parameter ╚═▷ 1851) is configured to "1Ph 2W" (in this case, the phase
rotation is not evaluated, but defined by the 1Ph2W phase rotation (parameter ╚═▷
1859)).

4 Configuration
[Default]
3950 Monitoring 2 [On] Phase rotation monitoring is

Notes
The phase rotation monitor is

internally configured with a two
seconds delay, so that the
expected response time is less
than three seconds.
3954 Generator phase 2 [CW] The three-phase measured

rotation generator voltage is rotating CW
(clock-wise; that means the
voltage rotates in L1-L2-L3
direction; standard setting).
CCW The three-phase measured

generator voltage is rotating CCW
(counter clock-wise; that means
the voltage rotates in L1-L3-L2
direction).
Notes



longer detected.

output "External



4 Configuration
4.5.1.6.3 Pole Slip Monitoring

engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
There are different circumstances possible to bring a synchronous generator into a pole
slip situation. This monitor here is established for pole slip cases, when the genset is
running parallel to grid. Because in mains instability situations in conjunction with being
longer parallel to grid (VDE-AR-N 4105/4110) it can lead to situations that the
synchronous generator goes through pole-slips. These pole slips stress the genset
mechanically very hard and must be monitored. Finally the generator is to decouple from
mains, if the pole-slip rate reaches a scale which damages the genset.
Because the easYgenXT is connected on measurement CTs the device follows a

monitoring method based on power measurement in conjunction with other
circumstances.
Function
A pole slip situation is detected through observing the power output of the generator in a
special moment (refer to release pole slip). In this moment when the power changes from
positive to negative and back to positive one pole slip event is detected.
Release pole slip
• The monitoring is enabled (ON)
• The mains parallel operation is detected (GCB closed, MCB closed and “GGB closed”)
• The Generator active power is higher than a configurable “Min. active power
threshold”
• The difference between active power and active power set point is higher than the
threshold. If the active power controller is not active (external active power control),
the threshold must be set to 0%.
Trigger condition for a pole slip event
(Trigger the pole slip event counter +1)
• The active power has changed from positive to negative and back to positive.
AND (If Pole slip with current limit is enabled)
• The generator current has surpassed a configurable limit
AND (If Pole slip with pickup is enabled)

4 Configuration
• A configurable difference is detected between pickup speed and the measured

generator frequency.
Trigger pole slip alarm
If during released pole slip monitoring no pole slip event is encountered anymore for a
configurable time the event counter is reset.
Reset pole slip event counter
If, during released pole slip monitoring, no pole slip event is encountered anymore for a
configurable time, the event counter is reset.
[Default]
2416 Monitoring 2 On Enabling the pole slip monitoring.
On: Monitoring is enabled
[Off] Off: Monitoring is disabled
2417 Min. active power 2 0 to 150% With reaching once this minimum
active power in parallel operation
[10%] the pole slip monitoring is
released. The entry is related to
generator rated power.
2418 Limit act. power 2 0 to 150% This difference between real

difference power and set point triggers the
[10%] monitoring. If the difference is
higher than the configured
threshold the pole slip events are
taken into account.
2426 Pole slip with current 2 On Use additional the generator

limit current limit for detecting pole slip
events.
On: Current limit is additional

used for pole slip detection
[Off] Off: Current limit is not used
2427 Generator current 2 50 to 200% If the generator current is higher

limit than the threshold during active
[110%] power decreasing the current
condition for pole slip events is
matched.
2428 Pole slip with pickup 2 On Use additional the difference

between pickup and generator
frequency for detecting pole slip
events
On: Use the difference between

pickup and frequency
[Off] Off: Difference between pickup

and frequency is not used

4 Configuration
4.5.2 Configure Engine Monitor
2429 Speed/freq. 2 0.5 to 9.9Hz If the difference between speed

difference and frequency is higher than the
[2.0Hz] threshold the pickup condition for
pole slip events is matched. The
pickup speed is calculated to
frequency for the compare with
the generator frequency from the
AC measurement.
2419 Number of pole slip 2 1 to 10 This is the maximum allowed

events number of pole slips to trigger the
[2] alarm.
2420 Reset time pole slip 2 10 to 999s During released pole slip
events monitoring and with a pole slip
[60s] counter which is not increased
anymore for this time, the pole
slip counter will be reset.
2421 Alarm class 2 Class A-F/Control Pole slip alarm class Default alarm
class D opens the GCB and stops
[Class D] the engine after cooldown timer.
2422 Self-acknowledge 2 No/Yes Self-acknowledge pole slip alarm
[No]
2423 Mns. decoupling by 2 On Use pole slip monitoring for mains

pole slip decoupling
[Off]
Alarm
The device indicates and stores the text "Pole slip" (ID2425).
Visualization
The device indicates "Number of pole slip events" in ToolKit (ID2425).
LogicsManager
The device provides the LM command variable "LM 06.36 Gen pole slip" (10674).
AnalogManager
The device provides the AM variable "AM 01.86 Number pole slip" (9765).
4.5.2 Configure Engine Monitor
4.5.2.1 Engine Overspeed (Level 1 & 2) ANSI# 12
General notes
The speed measured by the magnetic pickup unit (MPU) is monitored for overspeed. If the
MPU is disabled, the speed may only be monitored using the generator overfrequency

4 Configuration
4.5.2.1 Engine Overspeed (Level 1 & 2) ANSI# 12
monitoring. If the MPU speed exceeds the overspeed limits the configured alarms will be
initiated.
If this protective function is triggered, the display indicates "Overspeed 1" or "Overspeed
2" and the logical command variable "05.01" or "05.02" will be enabled.
[Default]
2100 Monitoring 2 [On] Overspeed monitoring is carried

> Level 2).

2104 Limit 2 0 to 9,999 rpm The revolutions per minute (rpm)

values that are to be monitored
2110 2104: [1,850.0 rpm] for each threshold limit are
defined here.
2110: [1,900.0 rpm]
(Hysteresis: 50 rpm) exceeded for at least the delay
(Reset Delay: 1 s) action specified by the alarm class
is initiated.
2105 Delay 2 0.02 to 99.99 s If the monitored engine speed

2111: [0.10 s]
Notes
If the monitored engine speed

2107: [F]
Notes


4 Configuration
4.5.2.2 Engine Underspeed (Level 1 & 2)


longer detected.

output "External

2109
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
The speed measured by the magnetic pickup unit (MPU) is monitored for underspeed. If
the MPU is disabled or not available, the speed may only be monitored using the
generator underfrequency monitoring. If the MPU speed falls below the underspeed limits
the configured alarms will be initiated.
If this protective function is triggered, the display indicates "Underspeed 1" or

"Underspeed 2" and the logical command variable "05.03" or "05.04" will be enabled.
[Default]
2150 Monitoring 2 [On] Underspeed monitoring is carried


4 Configuration

> Level 2).

2154 Limit 2 0 to 9999 rpm The percentage values that are to

2160 2154: [1,300.0 rpm] limit are defined here.
2160: [1,250.0 rpm] If this value is reached or

(Hysteresis: 50 rpm) time without interruption, the
(Reset Delay: 1 s) is initiated.
2155 Delay 2 0.02 to 99.99 s If the monitored engine speed

2161: [0.10 s]
Notes
If the monitored engine speed

2157: [F]
Notes



longer detected.

output "External

2159
engine monitoring".

4 Configuration
4.5.2.3 Engine/Generator Speed Detection

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
Speed detection checks if the generator voltage frequency f (determined from the
measured generator voltage) differs from the measured engine speed n (determined from
the Pickup signal or the speed measured via ECU/J1939) and determines a difference (Δf-
n).
If the two frequencies are not identical (Δf-n ≠ 0) and the monitored frequency mismatch
reaches or exceeds the threshold, an alarm is output. Additionally the LogicsManager
output "Firing speed" is checked upon its logical status with respect to the measuring
values "generator frequency" and "Pickup speed".
If this protective function is triggered, the display indicates "Speed/freq. mismatch" and
Speed/frequency mismatch (n/f mismatch) is carried out if:
1. A MPU is connected to the control and parameter "Speed pickup" (parameter ╚═▷
1600), is configured On.
2. The speed is measured via ECU/J1939.
The following is valid:
The measurement via Pickup is enabled (On):
Mismatch monitoring is carried out using the engine speed from the Pickup and the
generator frequency. If the speed/frequency mismatch or the LogicsManager is enabled
and the frequency is outside of the configured limit, an alarm will be issued.
The measurement via Pickup is disabled (Off):
Mismatch monitoring is carried out using the generator frequency and the
LogicsManager. If the LogicsManager output is enabled and the frequency is outside of
the configured limit, an alarm will be issued.
[Default]
2450 Monitoring 2 [On] Monitoring of the speed/

frequency/LogicsManager
mismatch (n/f/LM mismatch) is

4 Configuration

2454 Speed/frequency 2 1.5 to 8.5 Hz The frequency mismatch that is to

mismatch limit be monitored is defined here.
[5.0 Hz]
If the monitored frequency
mismatch reaches or exceeds this
value for at least the delay time
without interruption, the action
initiated.
Notes
The LogicsManager is monitored

with respect to his status.
2455 Delay 2 1 to 99 s If the monitored frequency

[1.00 s] value for the delay time
issued.
Notes
If the monitored frequency

will be reset.
2453 Activation frequency 2 15 to 85 Hz The speed/frequency mismatch

monitoring is enabled at this
[20 Hz] generator frequency.
[E] specifies what action should be
Notes



longer detected.

output "External

4 Configuration
4.5.2.4 Engine Start Failure


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4.5.2.4 Engine Start Failure
General notes
If it is not possible to start the engine within a configured number of start attempts (refer
to ╚═▷ “4.4.1.2 Engine Start/Stop”), an alarm will be initiated.
If this protective function is triggered, the display indicates "Start fail" and the logical
command variable "05.08" will be enabled.
[Default]
3303 Monitoring 2 [On] Monitoring of the start sequence

is carried out according to the
Notes



longer detected.


4 Configuration
4.5.2.5 Engine Shutdown Malfunction

output "External
4.5.2.5 Engine Shutdown Malfunction
General notes
If it is not possible to stop the engine within a configured time, an alarm will be initiated.
If this protective function is triggered, the display indicates "Eng. stop malfunct." and the
We recommend to assign this monitoring function to a discrete output to be able to

shutdown the engine with an external device to provide a shutdown redundancy.
[Default]
2500 Monitoring 2 [On] Monitoring of the stop sequence is

2503 Maximum stop delay 2 3 to 999 s The maximum permissible time

between the output of a stop
[30 s] command and the reply that the
engine is stopped successfully is
defined here.
Notes
If the engine cannot be stopped

within this time (this means speed
via the Pickup, frequency via the
generator voltage, or the
LogicsManager is detected) the
is initiated.
Notes


4 Configuration
4.5.2.6 Engine Unintended Stop


longer detected.

output "External
4.5.2.6 Engine Unintended Stop
General notes
If an engine stop has been detected without a stop command being issued, an alarm will
be initiated.
If this protective function is triggered, the display indicates "Unintended stop" and the
[Default]
2650 Monitoring 2 [On] Monitoring of an unintended stop

Notes



longer detected.

output "External

4 Configuration
4.5.2.7 Engine Charge Alternator (D+)

4.5.2.7 Engine Charge Alternator (D+)
General notes
The charge alternator monitoring issues an alarm if the voltage measured at the auxiliary
excitation input D+ (terminal 65) falls below a fix limit.
The fix limit depends on the power supply voltage. If a power supply voltage exceeding
15 V is detected, the unit assumes a 24 V system and uses a limit of 20 V. If a power
supply voltage below 15 V is detected, the unit assumes a 12 V system and uses a limit of
9 V.
If this protective function is triggered, the display indicates "Charge alt. low volt" and the
[Default]
4050 Monitoring 2 On Monitoring of the charge

alternator is carried out according
to the following parameters.
4055 Delay 2 2 to 9999 s If the voltage measured at the

auxiliary excitation input D+ falls
[10 s] below a fixed limit for the time
defined here, an alarm will be
issued.
If the voltage returns within the

limit before the delay time
expires, the delay time will be
reset.
4051 Alarm class 2 Class A/B/C/D/E/F Each limit may be assigned an

Notes



longer detected.

4 Configuration
4.5.2.8 Cylinder Temperature

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General Notes
Up to 20 temperatures monitored!
Gas engines needs to be monitored for equal exhaust or cylinder head temperatures. If
one cylinder temperature deviates too much from the others, something must be wrong.
This could be for example a failed spark plug or a too hot combustion.
The easYgen-3000XT series provides a monitor which supervises the deviation of a single
temperature to the average temperature of a group. Whereby either one average
temperature exists (inline engine) or two average temperatures are available (V-engine
with two banks).

4 Configuration
Fig. 183: Cylinder Temperature Monitoring
The monitor is configurable for:
• overrun,
• underrun
• or both.
• Two monitoring levels per temperature measurement.
◦ The both levels can be individually activated by different power limits.
The temperatures could be provided by either CAN J1939 (SPN 1137 - 1156, 20 ports) for
example Axiomatic Thermocouple Scanner or by External Analog Inputs (AI1 - AI16, 16
ports) for example Phoenix Temperature Module.

4 Configuration
Monitoring Function
Fig. 184: Status Cylinder Temperature
The monitor compares the single temperature deviations from the average temperature
of the according bank. An inline engine has only one group (one bank), so all
temperatures are usually allocated to bank 1. A V-engine has two groups (two banks), so
the single temperatures are distributed to bank 1 and bank 2. The monitoring mode is
valid for all temperatures. The monitoring mode can be 'Off', 'Overrun', 'Underrun' or
'Overrun and Underrun'. The mode is valid for all banks.
The monitoring generally is released by a LogicsManager equation. Each monitoring level

(level 1 or 2) can be separately released by a configurable generator power.
A cylinder with sensor defect is removed from the average temperature calculation and
trips an independent alarm!
Alarm System / Eventlogger
The alarm system provides three alarm messages:
• Cylinder temperature level 1
• Cylinder temperature level 2
• Wire break

4 Configuration
Command Variables
The easYgen provides LogicsManager command variables:
• 87.71 LM: Release cyl. temp.
• 05.18 Cyl. temp. lev. 1
• 05.19 Cyl. temp. lev. 2
• 05.20 Cyl. temp.wire break
Analog Variables
The easYgen provides AnalogManager variables::
• 11.56 Average Cyl. Temp. Bank 1
• 11.57 Average Cyl. Temp. Bank 2
• The hysteresis for the temperature limit is 2°C.

• The hysteresis for the power limit is 1% rated generator power.
Alarm Screen
Fig. 185: Cylinder temperature screen

4 Configuration
• The square is dotted, if the according cylinder is not configured
• The square contains an arrow-up, if the limit is exceeded
• The square contains an arrow-down, if limit is below target
• The square contains a '!' exclamation point sign, if the sensor is missing (wire break)
or error was detected
• If an alarm occurs and the monitor is still active, the new alarm is linked by logic 'OR'
to the others
• The monitor ignores values of cylinders with wire break or sensor defect
• The alarm trip displaying is removed, if the alarm of the according level was
successful acknowledged
• The wire break trip has a higher priority as the limit monitoring. That means: with
up-coming wire break only the according trip bits are RESET. Other cylinders not
touched.
General monitoring
[Default]
15158 Release cyl.temp. 2 Determined by LogicsManager True: The temperature deviation

87.71 monitoring is released.
[(0 & 1) & 1; False: The temperature deviation

monitoring is blocked.
tON = 0.00; tOFF = 0.00]
= 11460
8876 Monitoring at 2 [Off] The monitoring is deactivated.

The alarm screen is not displayed.
Overrun The single temperatures are

monitored on maximum deviation
in direction of higher
temperatures.
Underrun The single temperatures are

in direction of lower temperatures.
Both The single temperatures are

in direction of lower and higher
temperatures.
8877 Source cylinder 2 Ext.AIN The temperatures are taken from

temperature external temperature module
(Phoenix, AI1 - AI16, 16 ports).
[J1939] The temperatures are taken from

the J1939 protocol. (SPN 1137 -
1156, 20 ports).
Notes
Parameter available only if

external sources for cylinder
temperature are connected.

4 Configuration
Level 1
[Default]
8878 Minimum generator 2 000.0 ... 150.0% When the generator power
power exceeds this value the level 1
[30.0%] monitoring is activated.
Respectively the level 1 is

deactivated, if the power level is
undershoot.
8879 Limit 2 0000 ... 9999° C Threshold level 1
[100° C]
8880 Delay 2 0000 ... 9999 s Time between *** exceeds limits
and *** is activated.
[60 s]
8881 Alarm class 2 Class A/B/C/D/E/F, Control Each limit may be assigned to an
[B] For additional information refer

to.╚═▷ “9.5.4 Alarm Classes”.


longer detected.

output "External
Level 2
[Default]
8883 Minimum generator 2 000.0 ... 150.0% When the generator power
power exceeds this value the level 2
[30.0%] monitoring is activated.
Respectively the level 2 is

deactivated, if the power level is
undershoot.
8884 Limit 2 0000 ... 9999° C Threshold level 2
[150° C]

4 Configuration
[Default]

[60 s]


longer detected.

output "External
Wirebreak Cylinder Temperature
[Default]
[2 s]



longer detected.

output "External

4 Configuration
Temperature X Bank
[Default]
8856 Bank selct cylinder 2 [Off] The temperature does not exist.
{x}
to Bank 1 The temperature exists and is
located in cylinder bank 1.
8875
Bank 2 The temperature exists and is
located in cylinder bank 2.
Cylinder status
Each cylinder is represented by a 2-bit combination that has the following meanings:
• 00 - OK
• 01 - Overrun
• 10 - Underrun
• 11 - Error/missing
These two bits are carried by parameters ID 3352 ..3354 for the cylinders of bank 1 and
ID 3355..3357 for the cylinders of bank 2:
Bank Cylinder ID Bits Bank Cylinder ID Bits
1 1 3352 0..1 2 1 3355 0..1
2 2..3 2 2..3
... ... ... ...
8 14..15 8 14..15
9 3353 0..1 9 3356 0..1
10 2..3 10 2..3
... ... ... ...
16 14..15 16 14..15
17 3354 0..1 17 3357 0..1
18 2..3 18 2..3
19 4..5 19 4..5
20 6..7 20 6..7
(not in 8..15 (not in 8..15

use) use)

4 Configuration
4.5.3 Mains
4.5.3 Mains
4.5.3.1 General Mains Monitoring
[Default]
1771 Mains voltage 2 The unit can either monitor the

monitoring wye voltages (phase-neutral) or
the delta voltages (phase-phase).
The monitoring of the wye voltage
is above all necessary to avoid
earth-faults in a compensated or
isolated network resulting in the
tripping of the voltage protection.
[Phase - phase] The phase-phase voltage will be

monitoring "mains" are referred to
this value (VL-L).
Phase - neutral The phase-neutral voltage will be

monitoring "mains" are referred to
this value (VL-N).
All The phase-phase and phase-

neutral voltage will be monitored
and all subsequent parameters
concerning voltage monitoring
"mains" are referred to this value
(VL-L & VL-N).
This setting is only effective if

"Mains voltage measuring"
configured to "3Ph 4W".
Notes
WARNING: This parameter

influences the protective
functions.
Please be aware that if "Mains

voltage monitoring" (parameter
╚═▷ 1771) is configured to "All"
and the function ╚═▷ “4.5.1.2.2
Generator Undervoltage (Level 1
& 2) ANSI# 27” is used, that this
function only monitors "Phase -
neutral".
2801 Mains settling time 2 0 to 9999 s To end the emergency operation,

the monitored mains must be
[20 s] within the configured operating
parameters without interruption
for the minimum period of time
set with this parameter without
interruption.
This parameter permits delaying

the switching of the load from the
generator to the mains.

4 Configuration
4.5.3.2 Blocking of Mains Protection
The display indicates "Mains

settling" during this time.
4.5.3.2 Blocking of Mains Protection
General notes
The operator can deactivate the mains monitoring features and the decoupling function.
A dedicated LogicsManager is installed to disable all mains monitoring and the decoupling
function.
Already latched alarms (self acknowledge = No) are not removed from the alarm list by
this function.
Following functions are blocked:
• Mains decoupling
• Mains over frequency 1&2
• Mains under frequency 1&2
• Mains over voltage 1&2
• Mains under voltage 1&2
• Mains voltage increase (10 minutes average value)
• Mains Time-dependent Voltage (FRT)
• Mains Q(V) Monitoring
• Mains phase shift
• Mains df/dt
[Default]
15159 Disable mains 2 Determined by LogicsManager Switch to disable

monitoring 87.72
• all mains monitoring
[(0 & 1) & 1] functions and
• the mains decoupling
tON = 0.00; tOFF = 0.00]
function.
= 11461

4 Configuration
4.5.3.3 Mains Operating Ranges
4.5.3.3 Mains Operating Ranges
4.5.3.3.1 General Mains Operating Range
General notes
The mains operating voltage/frequency parameters are used to trigger mains failure
conditions and activate an emergency run.
The mains values must be within this ranges to synchronize the mains circuit breaker. It
is recommended to configure the operating limits within the monitoring limits.
Example
If the mains rated voltage is 400 V, the upper voltage limit is 110 % (of the mains rated
voltage, i.e. 440 V), and the hysteresis for the upper voltage limit is 5 % (of the mains
rated voltage, i.e. 20 V), the mains voltage will be considered as being out of the
operating limits as soon as it exceeds 440 V and will be considered as being within the
operating limits again as soon as it falls below 420 V (440 V – 20 V).
If the rated system frequency is 50 Hz, the lower frequency limit is 90 % (of the rated
system frequency, i.e. 45 Hz), and the hysteresis for the lower frequency limit is 5 % (of
the rated system frequency, i.e. 2.5 Hz), the mains frequency will be considered as being
out of the operating limits as soon as it falls below 45 Hz and will be considered as being
within the operating limits again as soon as it exceeds 47.5 Hz (45 Hz + 2.5 Hz).
[Default]

positive deviation of the mains
[110%] voltage from the mains rated
voltage (parameter ╚═▷ 1768) is
configured here.

(02.09).
5814 Hysteresis upper 2 0 to 50% If the mains voltage has exceeded

voltage limit the limit configured in
[2%] parameter ╚═▷ 5810, the voltage
must fall below the limit and the
value configured here, to be
considered as being within the
operating limits again.

negative deviation of the mains
voltage (parameter ╚═▷ 1768) is
configured here.


4 Configuration
4.5.3.3.1 General Mains Operating Range

(02.09).
5815 Hysteresis lower 2 0 to 50% If the mains voltage has fallen

voltage limit below the limit configured in
[2%] parameter ╚═▷ 5811, the voltage
must exceed the limit and the
value configured here, to be
considered as being within the
5812 Upper frequency limit 2 66.7¹ to 150.0% The maximum permissible

[110.0%] frequency from the rated system
is configured here.

(02.10).
Notes
¹ The lowest measurable

frequency is 40 Hz.
66.7 % of 60 Hz is 40 Hz.
Equivalent for 50 Hz don't go
below 80 %.
5816 Hysteresis upper 2 0 to 50.0% If the mains frequency has

frequency limit exceeded the limit configured in
[0.5%] parameter ╚═▷ 5812, the
frequency must fall below the limit
and the value configured here, to
be considered as being within the
5813 Lower frequency limit 2 66.7¹ to 100.0% The maximum permissible

[90.0%] frequency from the rated system
is configured here. This value may
be used as a frequency limit
switch. The conditional state of
this switch may be used as a
command variable for the
LogicsManager (02.10).
Notes
¹ The lowest measurable

frequency is 40 Hz.
66.7 % of 60 Hz is 40 Hz.
Equivalent for 50 Hz don't go
below 80 %.
5817 Hysteresis lower 2 0 to 50.0% If the mains frequency has

frequency limit exceeded the limit configured in
[0.5%] parameter ╚═▷ 5813, the
frequency must raise above the
limit and the value configured

4 Configuration
4.5.3.3.2 Reconnecting Mains Operating Range
here, to be considered as being

within the operating limits again.
4.5.3.3.2 Reconnecting Mains Operating Range
Introduction
After mains decoupling from the power generation device, with under-/over frequency or
under-/over voltage, the automatic reconnection to the grid after the mains settling time
is only possible, if the mains is within the following operation ranges.
The operation ranges for mains reconnecting uses the voltages according to the
configured mains voltage monitoring (ID 1771 Mains voltage monitoring, phase-phase/
phase-neutral/All). Only if all considered voltages are back in band the synchronization to
mains will be executed.
[Default]

voltage after mains decoupling.

5821 Upper frequency limit 2 66,7 to 150% The maximum permissible

[100.2%] voltage from the mains rated
5822 Lower frequency limit 2 66.7to 100% The maximum permissible

[99.8%] voltage from the mains rated
4.5.3.4 Mains Decoupling
General notes
The mains decoupling function is intended for use in a mains parallel operation and
monitors a series of subordinate mains protection thresholds. If a threshold is exceeded,
the genset control initiates a breaker opening and separates the generator(s) from the
mains at the defined breaker.
The following thresholds are monitored:
• Overfrequency level 2 (╚═▷ “4.5.1.3.2 Generator Overfrequency (Level 1 & 2) ANSI#

81O”)

4 Configuration
• Underfrequency level 2 (╚═▷ “4.5.3.6 Mains Underfrequency (Level 1 & 2) ANSI#

81U”)
• Overvoltage level 2 (╚═▷ “4.5.1.2.1 Generator Overvoltage (Level 1 & 2) ANSI# 59”)
• Undervoltage level 2 (╚═▷ “4.5.1.2.2 Generator Undervoltage (Level 1 & 2) ANSI#

27”)
• Mains phase shift / df/dt (ROCOF) (╚═▷ “4.5.3.12 Change Of Frequency”)
If one of these protective functions is triggered, the display indicates "Mains decoupling"
(the logical command variable "07.25" will be enabled) and the active level 2 alarm.
The mains decoupling function is optimized on the both relay outputs "GCB open" and
"MCB open". In case of using a free relay output in conjunction with the command
variable 07.25 an additional delay time of up to 20 ms is to consider.
Managing Breaker Open alarm
When the mains decoupling function detects a breaker open failure, the according
breaker alarm will be triggered as long the monitoring function is activated. Additionally
in cases where the decoupling mode has to change over to the other breaker,
(GCB®MCB, MCB®GCB), the alarm text “Decoupling GCB«MCB“ is indicated. The breaker
open alarm already occurs after the mains decoupling feedback delay (refer to ID ╚═▷
3113).
[Default]
12922 Ext. mns. decoupl. 2 Determined by LogicsManager The unit may be configured to
86.27 decouple from the mains when
(External mains commanded by an external
decoupling) [(0 & 1) & 1] device.

LogicsManager have been fulfilled,
an external mains failure is issued.
Notes

12942 Enable mains 2 Determined by LogicsManager Once the conditions of the

decoupl. 87.31 LogicsManager have been fulfilled,
the mains decoupling function is
(Enable mains [(02.02 & 1) & 1] enabled.
decoupling)
Notes

3110 Mains decoupling 2 Off Mains decoupling monitoring is

disabled.

4 Configuration
[GCB] Mains decoupling is carried out

parameters. If one of the
subordinate monitoring functions
is triggered, the GCB will be
opened. If the unit is operated in
parallel with the mains and the
MCB opens, the GCB will be closed
again.
GCB->MCB Mains decoupling is carried out

is triggered, the GCB will be
opened. If the reply "GCB open" is
not present within the delay
configured in parameter ╚═▷
3113, the MCB will be opened as
well.
MCB Mains decoupling is carried out

is triggered, the MCB will be
opened.
MCB->GCB Mains decoupling is carried out

is triggered, the MCB will be
opened. If the reply "MCB open" is
not present within the delay
configured in parameter ╚═▷
3113, the GCB will be opened as
well.
GCB/MCB by LM Mains decoupling is carried out. If

one of the subordinate monitoring
functions is triggered, a breaker
will be opened, which is
determined by the LogicsManager
equation "╚═▷ 15160 LM mains
decoupling MCB". If it's status is
TRUE, the MCB will be opened. If
it's status is FALSE, the GCB will
be opened.
15160 Mains decoupling 2 Determined by LogicsManager FALSE: If the decoupling is

MCB 87.73 triggered, the GCB will be opened.
[(0 & 1) & 1] TRUE: If the decoupling is

triggered, the MCB will be opened.
Only available in Mains decoupling

mode "GCB/MCB by LM".
3113 Mains decoupling 2 0.2 to 99.9 s If the open signal from the
feedback delay respective circuit breaker cannot
[0.4 s] be detected within the time
configured here, the mains
decoupling function performs the
action as configured in

4 Configuration

Notes


no longer detected.


output "External
8848 Mns. decoupling by 2 The mains overvoltage 1 alarm

overfreq. 1 can be linked to the mains
decoupling function, if required.
On The mains overvoltage 1 trip is

linked to the mains decoupling
function with all its consequences.
[Off] The mains overvoltage 1 trip is

ignored in the mains decoupling
function.
Notes
It is recommended to configure
the operating limits (parameter
╚═▷ 5810 to ╚═▷ 5817) within the
monitoring limits.

overvolt. 1 can be linked to the mains


function.
Notes
╚═▷ 5810 to ╚═▷ 5817) within the
monitoring limits.
2423 Mains decoupling by 2 On The QV monitoring function is

pole slip linked to the mains decoupling
function with all its consequences
and is assigned to "Delay step 1"

4 Configuration
[Off] The QV monitoring function is

function.

QV linked to the mains decoupling

function.
4989 Mns. decoupl. by 2 On Time-dependent voltage

time-dep. volt. monitoring does cause a
decoupling.
[Off] Time-dependent voltage

monitoring does not cause a
decoupling.
8847 Mns. decoupling by 2 The mains undervoltage 1 alarm

underfreq. 1 can be linked to the mains
On The mains undervoltage 1 trip is

[Off] The mains undervoltage 1 trip is

function.
Notes
╚═▷ 5810 to ╚═▷ 5817) within the
monitoring limits.

undervolt. 1 can be linked to the mains


function.
Notes
╚═▷ 5810 to ╚═▷ 5817) within the
monitoring limits.
8808 Mns. decoupl. by 2 On Voltage increase monitoring does

volt. increase cause a decoupling.
[Off] Voltage increase monitoring does

not cause a decoupling.

4 Configuration
4.5.3.4.1 Setup Grid Code AR-–4105
1733 Test 2 On Activates a test mode which

allows a comfortable mains
decoupling test.
[Off] Deactivates the test mode. Mains

decoupling is working normal.
Notes
When the test mode is activated a

mains decoupling according to the
parametrization is triggered, once
a mains failure is detected.
Thereby the states of things of the
breaker reply are irrelevant.
A retriggering of the mains

decoupling can be performed after
0.5 s + "Mns. decoupling feedback
delay" (parameter ╚═▷ 3113)
without leaving the test mode. As
long as the codelevel is ≥ 2 it is
possible to switch-off the test
mode manually.
The test mode switches off

automatically after one hour since
having turned on or after
switching on the operation
magnet (engine should start).
General notes
The German Grid Code VDE-AR-N 4105 instructs the handling of electrical energy sources
running parallel to the low voltage grid. This rule has an impact with some items on the
genset control. A more detailed description relating to that VDE rule is done through the
separated application note “easYgen-3000_VDE-AR-N 4105” on the manual CD of this
product.
Here are some functions which have to be covered according to the 4105 rule:
• The mains decoupling is executed through following monitors:
◦ Mains under voltage V<
◦ Mains over voltage V>
◦ Mains under frequency f<
◦ Mains over frequency f>
• Recognizing isolation operation (other decoupling argument)
◦ Phase shift OR
◦ df/dt
• Button for Testing the Decoupling Facility
• Single-failure-security including self-monitoring
The VDE-AR-N 4105 demands a Single-failure-proof of the mains decoupling function. That
means that the decoupling of the generator from the mains must be always ensured,

4 Configuration
even if a single element in the system fails. So the system must contain two circuit
breakers with two independent monitoring functions acting individually on each breaker.
From the perspective of the network provider that rule pursuits the mains protection but
not the availability of the electrical source, so in case of doubt the generator should be
decoupled from mains.
Woodward solves this requirement with the use of a minimum of two units acting as a
system (for example two easYgens or an easYgen and an LS-5 with 4105 functionality).
The system allows incorporating more units, so that the availability of the generator can
still be increased.
The demanded two breakers in series are realized through the use of a GCB and a MCB. If
only a GCB is available, the customer must install another circuit breaker in addition.
An important item of the VDE-AR-N 4105 is the Single-Failure-Diagnostic, at which a

minimum of two units exchange their measurement data and settings over
communication interface (usually CANbus). This allows determining, if the Single-Failure-
Proof is lost and the unit can issue an alarm.
Using Ethernet?
To us Ethernet communication interface for Single-failure-proof it is mandatory that load-

share is using Ethernet, too. For interface selection refer to ╚═▷ “4.4.4.3.5 Load-Share
Interface”.
Enable 4105 monitoring
Monitoring according VDE AR-N 4105 per default is [Off]. It can be enabled via ToolKit
[Configure Monitoring / Mains: Other monitoring / Setup VDE-AR-N 4105] or via Menu (see
screen ╚═▷ Fig. 186).

4 Configuration
Fig. 186: Select mains decoupling 4105
Monitoring according AR-–4105
[Default]
3297 Monitoring 2 [Off] The diagnostic function is

disabled, no related monitoring is
executed.
CAN #1, Ethernet If the diagnostic function is

enabled, the related messages
can be received via CAN 1 or
Ethernet.
Notes
The following alarms can be

triggered:
• Missing member 4105

• Para. alignment 4105
• Meas.difference 4105
3298 Monitoring mode 2 Single The diagnostic function is related

to one partner unit.

4 Configuration
[Multi] The diagnostic function is

executed with according partner
units.
3299 Device number 2 [01] The device ID of the expected

partner partner unit. This configuration is
01 to 64 only valid, if the mode 'single' is
enabled.
1828 Voltage difference 2 [4.0%] This is the voltage measurement

tolerance for all participating 4105
2.0 to 9.9% partners relating to the mains
rated voltage measurement (refer
to ID╚═▷ 1768). This is a part
within the 4105 diagnostic.
1836 Frequency difference 2 [1.0%] This is the frequency

measurement tolerance for all
0.5 to 9.9% participating 4105 partners
relating to the system rated
frequency measurement. (refer to
ID╚═▷ 1750). This is a part within
the 4105 diagnostic.
Monitoring Missing Member AR-–4105
[Default]
5125 Alarm class 2 [C] The alarm class specifies what

action should be taken in case of
A to F, control missing communication with
devices(s) being member(s) of the
AR-–4105 system.
Notes


no longer detected.

longer detected.

output "External
Monitoring Parameter Alignment VDE AR-–4105
The following parameters are compared for monitoring its alignment:
Control Parameter ID Parameter
Mains Decoupling 3110 Mains Decoupling

4 Configuration
Control Parameter ID Parameter
Overfrequency level 2 2856 Monitoring
2860 Limit
2861 Delay
Underfrequency level 2 2906 Monitoring
2910 Limit
2911 Delay
Overvoltage level 2 2956 Monitoring
2960 Limit
2961 Delay
Undervoltage level 2 3006 Monitoring
3010 Limit
3011 Delay
Mains voltage increase 8806 Monitoring
8808 Mains decoupling volt.incr.
8807 Limit
Change of frequency 3058 Change of frequency
3054 Phase shift: Limit 1-phase
3055 Phase shift: Limit 3-phase
3104 Limit (df/dt)
3105 Delay (df/dt)
Disable mains monitoring 15159 Set TRUE
Tab. 67: VDE 4105 alignment: Supervised parameters
[Default]

action should be taken if the
A to F, control parameter alignment between the
communication devices(s) of the
AR-–4105 system is active.
Notes


no longer detected.

longer detected.


4 Configuration
4.5.3.4.2 Setup Grid Code BDEW (medium voltage guideline)
[Default]
output "External
Tab. 68: VDE 4105 alignment: Monitoring
Monitoring Measurement Difference AR-–4105
[Default]

action should be taken if the
A to F, control measurement difference
(frequency, ╚═▷ 1836 or voltage,
╚═▷ 1828) between the
communication devices(s) of the
AR-–4105 system differ more than
allowed.
Notes


no longer detected.

longer detected.

output "External
4.5.3.4.2 Setup Grid Code BDEW (medium voltage guideline)
The BDEW Grid Code instructs the handling of electrical energy sources running parallel
to the medium voltage grid. This rule has an impact with some items on the genset
control. A more detailed description relating to that BDEW technical guideline can be
ordered directly by the BDEW Germany. With easYgen-3000... genset control series
functions which have to be covered according to this BDEW rule are supported.
The mains decoupling is executed through following monitors:
• Mains under voltage V<
• Mains under voltage V<<
• Mains over voltage V>
• Mains over voltage V>>

4 Configuration
4.5.3.5 Mains Overfrequency (Level 1 & 2) ANSI# 81O
• Mains under frequency f<
• Mains over frequency f>
• Q(V) Monitoring
• Mains Time-Dependent Voltage (FRT)
The Change of frequency monitors (vector/phase shift or df/dt) is not directly required by
BDEW. These monitors are depending on the according network providers.
Other functions related to the BDEW guideline:
• Frequency Depending Derating Of Power. Refer to ╚═▷ “4.4.4.5.5 Active Power –

Frequency Function P(f)” for details.
• Reactive Power Control, alternatively:
◦ Power Factor Control. Refer to ╚═▷ “4.4.4.2 Power Factor Control” for details.
◦ Power Factor Characteristic. Refer to ╚═▷ “4.4.4.2 Power Factor Control” for
details.
General notes
There are two overfrequency alarm levels available in the control. Both alarms are
definite time alarms and are illustrated in the figure below. The figure diagrams a
frequency trend and the associated pickup times and length of the alarms. Monitoring of
the frequency is accomplished in two steps.
If this protective function is triggered, the display indicates "Mains overfreq. 1" or
"Mains overfreq. 2" and the logical command variable "07.06" or "07.07" will be enabled.
[Default]
2850 Monitoring 2 [On] Overfrequency monitoring is

other (prerequisite: limit 1
< Level 2 limit).


4 Configuration


(Reset Delay: 80 ms) time without interruption, the
is initiated.
Notes

1750).
2965 Hysteresis 2 0.00 to 10.00% If the mains frequency has

exceeded the configured limit ,
3016 2965: [0.10%] the frequency must fall below the
limit and the value configured
3016: [0.10%] here, to reset the alarm.
Notes

1750).
2855 Delay 2 0.00 to 99.99 s If the monitored mains frequency

2861 [0.06 s] for the delay time configured
Notes
If the monitored mains frequency

2857 2851: [A] specifies what action should be
2857: [B]
Notes



longer detected.

output "External

4 Configuration
4.5.3.6 Mains Underfrequency (Level 1 & 2) ANSI# 81U

2859
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
There are two underfrequency alarm levels available in the control. Both alarms are
the frequency is performed in two steps.
If this protective function is triggered, the display indicates "Mains underfreq. 1" or
"Mains underfreq. 2" and the logical command variable "07.08" or "07.09" will be
enabled.
[Default]
2900 Monitoring 2 [On] Underfrequency monitoring is

is performed at two levels.

> Level 2).
Off Monitoring is disabled for limit 1

and/or Level 2 limit.

2910: [98.0%] If this value is reached or fallen

below for at least the delay time
(Reset Delay: 80 ms) without interruption, the action
initiated.

4 Configuration
Notes

1750).
2998 Hysteresis 2 0.00 to 10.00% If the mains frequency has fallen

below the configured limit, the
3017 2998: [0.10%] frequency must exceed the limit
and the value configured here, to
3017: [0.10%] reset the alarm.
Notes

1750).
2905 Delay 2 0.00 to 99.99 s If the monitored mains frequency

value falls below the threshold
2911 2905: [1.50 s] value for the delay time
2911: [0.06 s] issued.
Notes
If the monitored mains frequency

2907: [B]
Notes



longer detected.

output "External

2909

4 Configuration
4.5.3.7 Mains Overvoltage (Level 1 & 2) ANSI# 59

engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
Voltage is monitored depending on parameter "Mains voltage measuring" (parameter ╚═▷

1853). There are two overvoltage alarm levels available in the control. Both alarms are
the voltage is done in two steps.
If this protective function is triggered, the display indicates "Mains overvoltage 1" or
"Mains overvoltage 2" and the logical command variable "07.10" or "07.11" will be
enabled.
[Default]
2950 Monitoring 2 [On] Overvoltage monitoring is carried

other (prerequisite: limit 1
< Level 2 limit).



is initiated.
Notes

4 Configuration
This value refers to the Mains

1768).
2964 Hysteresis 2 00.00 to 20.00 % If the mains voltage has exceeded

the configured limit , the voltage
3014 2964: [1.50 %] must fall below the limit and the
value configured here, to reset the
3014: [1.50 %] alarm.
Notes

1768).
2955 Delay 2 0.00 to 999.00 s If the monitored mains voltage

2961: [0.06 s]
Notes
If the monitored mains voltage

2957: [B]
Notes



longer detected.

output "External

2959
engine monitoring".

4 Configuration
4.5.3.8 Mains Undervoltage (Level 1 & 2) ANSI# 27

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32

overvolt. 1 can be linked to the mains


function.
Notes
╚═▷ 5810 to ╚═▷ 5817) within the
monitoring limits.
General notes
Voltage is monitored depending on parameter "Mains voltage measuring" (parameter ╚═▷

1853). There are two undervoltage alarm levels available in the control. Both alarms are
the voltage is done in two steps.
If this protective function is triggered, the display indicates "Mains undervoltage 1" or
"Mains undervoltage 2" and the logical command variable "07.12" or "07.13" will be
enabled.
Refer ╚═▷ “9.1.1 Triggering Characteristics” for the triggering characteristic of this
[Default]
3000 Monitoring 2 [On] Undervoltage monitoring is carried

< Level 2 limit).


4 Configuration


is initiated.
Notes
This value refers to the "Mains

rated voltage" (parameter ╚═▷
1768).
Minimum value follows BDEW

requirement.
2997 Hysteresis 2 00.00 to 20.00 % If the mains voltage has fallen

below the configured limit, the
3015 2997: [1.50 %] voltage must exceed the limit and
the value configured here, to reset
3015: [1.50 %] the alarm.
Notes

1768).
3005 Delay 2 0.00 to 99.99 s If the monitored mains voltage

3011: [0.06 s]
Notes
If the monitored mains voltage

3007: [B]
Notes



longer detected.

output "External

4 Configuration
4.5.3.9 Mains Voltage Increase


3009
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32

undervolt. 1 can be linked to the mains


function.
Notes
╚═▷ 5810 to ╚═▷ 5817) within the
monitoring limits.
General notes
Voltage is monitored depending on parameter "Monitoring" (parameter ╚═▷ 8806). This

function allows the monitoring of the voltage quality over a longer time period. It is
realized as a 10 minute moving average. The function is only active, if mains is within the
operating range. If "Mains voltage measuring" (parameter ╚═▷ 1853) is configured to a
three-phase measurement, the slow voltage increase alarm is monitoring the individual
three-phase voltages of the mains according to parameter “AND characteristics”
(parameter ╚═▷ 8849). The parameter "Mains decoupling volt. incr." (parameter ╚═▷
8808) determines if a voltage increase shall trigger a mains decoupling or not.
If this protective function is triggered, the display indicates "Mains volt. increase". The
alarm can be incorporated into the mains decoupling function.

4 Configuration
The average is set to "Mains rated voltage" (parameter ╚═▷ 1768) if:
• Frequency is not in the operating range OR

• Monitoring (parameter ╚═▷ 8806) is "Off" OR
• Monitoring is "Delayed by engine speed" (parameter ╚═▷ 8833) OR
• Monitoring is tripped AND the measured voltage is again in the operating range
Back synchronization is only possible if:
• The 10 minute average value is smaller than the defined limit AND
• The actual measured value is inside the operating range AND
• The mains settling time is over
Please be aware that if "Mains voltage monitoring" (parameter ╚═▷ 1771) is configured
to "All" and the mains voltage increase monitoring (parameter ╚═▷ 8806) is used, that
this function only monitors "Phase - neutral".
(In future releases (higher than 2.10-0) in this case ”Phase – neutral“ and ”Phase -
Phase“ will be monitored.)
[Default]
8806 Monitoring 2 On Voltage increase monitoring is

[Off] No monitoring is carried out.
8807 Limit 2 100 to 150% The percentage voltage value that

is to be monitored is defined here.
[110%]
If the average voltage over 10
minutes is higher, the action
initiated.
Notes

1768).
8849 AND characteristics 2 On If the 10 minute voltage averages

of all phases exceed the limit, the
monitoring is tripping.
[Off] If the 10 minute voltage average

of at least one phase exceeds
the limit, the monitoring is
tripping.

4 Configuration
4.5.3.10 Mains Time-Dependent Voltage

Notes



longer detected.

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
8808 Mns. decoupl. by 2 On Voltage increase monitoring does

volt. increase cause a decoupling.
[Off] Voltage increase monitoring does

not cause a decoupling.
8850 Volt. incr. average 0 — This visualization value shows the

current 10 minute average
voltage.
General notes
Two Time Dependent Mains Voltage Monitors Available
Both monitors behave similar but each with a separate Fault-Ride-Through (FRT) curve.

4 Configuration
☼ Example of a Time Dependent Mains Voltage Curve
Fig. 187: Time-dependent voltage monitoring curve

P1 0.00 s → 45.0%
P2 0.15 s → 45.0%
P3 0.15 s → 70.0%
P4 0.70 s → 70.0%
P5 1.50 s → 90.0%
P6 3.00 s → 90.0%
P7 4.00 s → 90.0%
Fallback 90.0%
threshold
Initial 80.0%
threshold
Fallback 1.00 s
time
General settings for Mains decoupling and Monitoring Voltage 1 - 3
Find parameters ...
Find parameters in two menus:
• [Configuration / Configure Monitoring / Mains decoupling / General ...]

• [Configuration / Configure Monitoring / Mains: Frequency / Voltage / ... time-
dependent voltage]

4 Configuration
4.5.3.10.1 Time Dependent Mains Voltage Monitor 1
[Default]
4989 Mns. decoupl. by 2 Mains decoupling by FRT

time-dep. volt. monitoring.
On Time-dependent voltage
monitoring does cause a
decoupling.

decoupling.
Notes



longer detected.

output "External
Tab. 69: Time Dependent Voltage Monitoring settings
This monitoring function is supporting a dynamic stabilization of mains. To maintain the

VDE-AR-N 4105 and VDE-AR-N 4110 grid code (2019) up to 3 FRT (Fault-Ride-Through)
curves can be defined.
The voltage is monitored depending on parameter "Mains voltage measuring" (parameter

╚═▷ 1853).
Furthermore it can be configured either as undervoltage or overvoltage monitoring

(»underrun« or »overrun« selected with parameter "Monitoring at ╚═▷ 4953). If the
measured voltage of at least N phase (N is defined with parameter 4960) falls below/
exceeds the configured "Initial threshold" (parameter ╚═▷ 4970), the time-dependent
voltage monitoring sequence starts and the voltage threshold will change in time
according to the configured threshold curve points (see ╚═▷ Fig. 187).
If the measured voltage falls below/exceeds this curve, the monitoring function triggers
and LogicsManager 07.28 becomes TRUE. The mains decoupling function is incorporated,
if configured. If the measured voltage falls below/exceeds the configured "Fallback
threshold" (parameter ╚═▷ 4978) for at least the configured "Fallback time" (parameter
╚═▷ 4968), the time-dependent voltage monitoring sequence will be reset.

4 Configuration
The threshold curve results from seven configurable points and a linear interpolation
between these points. ╚═▷ Fig. 187 shows an example of a Low-Voltage-Ride-Through
(LVRT) curve for time-dependent voltage monitoring. The curve is configured by default
according to a typical grid code requirement.
Rules for configuration
The time points should always have an ascending order. The fallback threshold
(parameter ╚═▷ 4978) should always be configured to a value higher/lower than the
initial threshold (parameter ╚═▷ 4970).
The monitoring on undervoltage over the undervoltage curve (or overvoltage or

overvoltage curve) is always active, if the »Monitoring« (parameter ╚═▷ 4950) is enabled.
A mains decoupling is only executed, if the generator runs parallel to mains.
The monitor behaves according to the configured »AND characteristic« (parameter 4960).
When the AND characteristic is configured to "On", all 3 phases are taken into account.
Only if all phases are below/above the configurable curve, the monitor will trip. When the
AND characteristic is configured to "Off", the single phases are taken into account. Even if
only one phase runs below/above the configurable curve, the monitor will trip.
The monitoring starts with passing the initial threshold. The tripping time is determined
by the voltage deviation and its according curve location. The monitoring is disabled, if
the voltage value (values) have crossed the fallback threshold. The monitor trips the
LogicsManager 07.28 command variable 10877.
FRT Monitoring Characteristic
The monitoring type influences the FRT:
Parameter "Mains voltage monitoring" ╚═▷ 1771 determines, if the Ph-Ph, Ph-N, or all
measurements are used.
If type "All" is available and configured, and 3Ph4W is configured, "Time dependent
Voltage Monitoring" is calculated with phase-phase and phase-neutral voltages. If All and
1Ph3W is configured, only PH-N values are used.
The mains time-dependent monitoring works with configurable FRT characteristics. In

conjunction with mains voltage measuring (ID1853) and mains voltage monitoring (see
section before) different monitoring procedures take place.
Bloking ROCOF Monitor During Dynamic Mains Stabilization
Due the higher prioritization of the Dynamic Mains Stabilization (FRT) as the ROCOF
monitor, the ROCOF monitor must be disabled for longest 5 seconds when any FRT curve
was initiated. Therefore each FRT (=Time-dependent voltage monitoring) function
provides a flag. The flag is set, if the particular initiation threshold is passed. The flag is
reset if all monitored voltages are back in band (parameter ╚═▷ 4978).
The 3 flags are OR’ed and results in one “FRT initiated” flag. This flag will be kept TRUE
for maximal 5 seconds. Finally this ROCOF blocking flag will be inverted and entered as
LM Command Variable “07.34 FRT ROCOF enable”.

4 Configuration
Time-dep. voltage 1
[Default]
4950 Monitoring 2 On Time-dependent voltage

parameters.
4960 Characteristics 2 The mains time-dependent

monitoring works with different
characteristics.
[1-phase] Uses the lowest/highest phase for

triggering the alarm. If "1771
Mains voltage monitoring" is
configured to “All”, the alarm will
be triggered if at least one phase
L-L or at least one phases L-N is
out of range and will be reset if all
phases of L-L and all phases of L-N
are in range.
2-phase Uses the two lowest/highest

phases for triggering the alarm. If
"1771 Mains voltage monitoring"
is configured to “All”, the alarm
will be triggered if at least two
phases L-L or at least two phases
L-N are out of range and will be
reset if at least two phases of L-L
and at least two phases of L-N are
in range.
3-phase Uses all three phases (symmetric

condition) for triggering the alarm.
If "1771 Mains voltage
monitoring" is configured to “All”,
the alarm will be triggered if all
phases L-L or all phases L-N are
out of range and will be reset if at
least one phase of L-L and at least
one phase of L-N is in range.
4953 Monitoring at 2 Selects whether the system shall

do over- or undervoltage
monitoring.
[Underrun] The undervoltage monitoring is

carried out (The monitoring
function triggers if the measured
voltage is below the curve).
Overrun The overvoltage monitoring is

voltage exceeds the curve).
4970 Init threshold 2 0.0 to 150.0% The time-dependent voltage

monitoring initial threshold is
[80.0%] configured here. If the measured
voltage falls below/exceeds this
threshold, the monitoring
sequence starts and the voltage
threshold will change in time
according to the configured
threshold curve points.
If the measured voltage falls

below/exceeds this curve, the

4 Configuration
[Default]
monitoring function triggers and

the configured relay will energize.
4978 Fallback threshold 2 0.0 to 150.0% The time-dependent voltage

monitoring fallback voltage is
voltage falls below/exceeds the
voltage configured here for at
least the configured "Fallback
time", the monitoring sequence
will be reset.
Notes
This parameter should always be

configured to a value higher/lower
than the "Init threshold"
(parameter ╚═▷ 4970) for proper
operation.
The parameter "Point 7 voltage"

(parameter ╚═▷ 4977) is used as
fallback threshold if it is
than the parameter "Fallback
threshold" (parameter ╚═▷ 4978).
4968 Fallback time 2 0.00 to 320.00 s The time-dependent voltage

monitoring fallback time is
[1.00 s] configured here. If the measured
configured "Fallback threshold"
(parameter ╚═▷ 4978) for at least
the time configured here, the
monitoring sequence will be reset.
4971 Point {x} voltage 2 0.0 to 150.0% The voltage values of time-
dependent voltage monitoring
4972 [x = 1 to 7] 4971: [45.0%] voltage points are configured
here.
4973 4972: [45.0%]
4974 4973: [70.0%]
4975 4974: [70.0%]
4976 4975: [90.0%]
4977 4976: [90.0%]
4977: [90.0%]
Notes
Please avoid a setting between

0.1% and 5.0%.
4961 Point {x} time 2 0.00 to 320.00 s The time values of time-
4962 [x = 1 to 7] 4961: [0.00 s] time points are configured here.
4963 4962: [0.15 s]
4964 4963: [0.15 s]
4965 4964: [0.70 s]
4966 4965: [1.50 s]
4966: [3.00 s]

4 Configuration
[Default]
4967 4967: [4.00 s]
The Time dependent voltage monitoring 2 is an additional independent FRT monitoring,

which behaves like the Time dependent voltage monitoring 1 described in the previous
chapter.
It serves a LogicsManager 07.31 command variable "Time-dep. voltage 2" 11750 to trip a
relay or to incorporate the monitoring into the mains decoupling feature of the device.
The alarm class and the self-acknowledge feature is taken from the original time
dependent voltage monitoring (see ╚═▷ “General settings for Mains decoupling and
Monitoring Voltage 1 - 3”.
Time-dep. voltage 2
[Default]
4954 Monitoring 2 On Time-dependent voltage 2

parameters.
Notes. It is an additional
independent FRT monitoring. It
serves a LogicsManager command
variable to trip a relay or to
incorporate the monitoring into
the mains decoupling function of
the device. The alarm class and
the self-acknowledge setting is
shared with the other time
dependent voltage monitoring. (Id
4951 and Id 4959)

monitoring.
[Underrun] The undervoltage monitoring is

Overrun The overvoltage monitoring is


characteristics.


4 Configuration
[Default]

are in range.

in range.

4990 Init threshold 2 0.0 to 200.0% The time-dependent voltage 2

threshold curve points.
If the measured voltage 2 falls

below/exceeds this curve, the
monitoring function triggers and
the configured relay will energize.
4998 Fallback threshold 2 0.0 to 200.0% The time-dependent voltage 2

time" (parameter ╚═▷ 4988), the
Notes

operation.

threshold" (parameter ╚═▷ 4998).
4988 Fallback time 2 0.00 to 320.00 s The time-dependent voltage 2

(parameter ╚═▷ 4998) for at least

4 Configuration
[Default]
the time configured here, the

4991 Point {x} voltage (2) 2 0.0 to 200.0% The voltage values of time-
dependent voltage 2 monitoring
here.
4993 4992: [10.0%]
4994 4993: [90.0%]
4995 4994: [90.0%]
4996 4995: [90.0%]
4997 4996: [90.0%]
4997: [90.0%]
Notes
Please avoid a setting between

0.1% and 5.0%.
dependent voltage 2 monitoring
4983 4982: [0.15 s]
4984 4983: [1.50 s]
4985 4984: [10.00 s]
4986 4985: [20.00 s]
4987 4986: [30.00 s]
4987: [40.00 s]
The Time dependent voltage monitoring 3 is an additional independent FRT monitoring,

which behaves like the Time dependent voltage monitoring 1 described in the previous
chapter.
It serves a LogicsManager 07.33 command variable "Time-dep. voltage 3" 11750 to trip a
relay or to incorporate the monitoring into the mains decoupling feature of the device.
The alarm class and the self-acknowledge feature is taken from the original time
dependent voltage monitoring (see ╚═▷ “General settings for Mains decoupling and
Monitoring Voltage 1 - 3”.
Time-dep. voltage 3
[Default]
9130 Monitoring 2 On Enabling the time-dependent

voltage monitoring 3. It is an
additional independent FRT
monitoring. It serves a

4 Configuration
[Default]
LogicsManager command variable

to trip a relay or to incorporate the
monitoring into the mains
decoupling function of the device.
The alarm class and the self-
acknowledge setting is shared
with the other time dependent
voltage monitoring. (Id 4951 and
Id 4959)
Notes. It is an additional
independent FRT monitoring. It
serves a LogicsManager command
variable to trip a relay or to
incorporate the monitoring into
the mains decoupling function of
the device. The alarm class and
the self-acknowledge setting is
shared with the other time
dependent voltage monitoring. (Id
4951 and Id 4959)

characteristics.

are in range.

in range.


monitoring.
Underrun The undervoltage monitoring is

[Overrun] The overvoltage monitoring is


4 Configuration
[Default]

9148 Init threshold 2 0.0 to 200.0% The time-dependent voltage

threshold curve points. If the
measured voltage falls below/
exceeds this curve, the monitoring
function triggers and the
configured alarm / decoupling will
be initiated.
Fallback threshold 2 0.0 to 200.0% The time-dependent voltage

time" (parameter ╚═▷ 9147), the
Notes

operation.

threshold" (parameter ╚═▷ ).
9147 Fallback time 2 0.00 to 320.00 s The time-dependent voltage

(parameter ╚═▷ ) for at least the
time configured here, the
9149 Point {x} voltage (2) 2 0.0 to 150.0% The voltage values of time-
here.
9151 9150: [125.0%]
9152 9151: [120.0%]
9153 9152: [120.0%]
9154 9153: [115.0%]
9155 9154: [115.0%]
9155: [110.0%]
Notes

4 Configuration
4.5.3.10.4 Time dependent voltage monitoring – Decoupling Function
[Default]
Avoid a setting between 0.1% and

5.0%.
9142 9141: [0.10 s]
9143 9142: [1.10 s]
9144 9143: [5.00 s]
9145 9144: [5.00 s]
9146 9145: [60.00 s]
9146: [60.00 s]
4.5.3.10.4 Time dependent voltage monitoring – Decoupling Function
The 3 Time dependent voltage monitorings can be allocated to the mains decoupling
function. With a configuration general all 3 FRT monitors are included.
[Default]
4989 Mns. decoupl. by 2 Mains decoupling by FRT

time-dep. volt. monitoring.
On Time-dependent voltage
monitoring does cause a
decoupling.

decoupling.
Tab. 70: Time Dependent Voltage Monitoring 1
Alarm flags (latched)
Time dependent voltage 1 (FRT1) is LM flag 07.28, ID10877
4.5.3.11 QV Monitoring
General notes
In case of mains undervoltage some grid codes require a special monitoring function to
avoid the import of inductive reactive power at the mains interchange point. The
monitoring function measures close to the generator. For this reason the QV monitoring is
a function of generator voltage and generator reactive power.

4 Configuration
QV monitoring is triggered if the following conditions are fulfilled: (Refer to ╚═▷ Fig. 188
for details)
• QV monitoring is configured to "On" (parameter ╚═▷ 3292)
• Measured reactive power is higher than the configured “Reactive power threshold”
• Measured voltages are below the configured “Limit undervoltage” (parameter ╚═▷
3285)
As a result Timer 1 and Timer 2 are starting. If the delay time "Delay step 1" (parameter
╚═▷ 3283) has exceeded, LogicsManager 07.29 becomes TRUE and the corresponding
alarm message "QV monitoring 1" is indicated. If the delay time "Delay step 2"
(parameter ╚═▷ 3284) has exceeded, LogicsManager 07.30 becomes TRUE and the
corresponding alarm message "QV monitoring 2" is indicated.
If parameter “Mains decoupling by QV” (parameter ╚═▷ 3296) is configured to "On" the
decoupling function is assigned to “Delay step 1” (parameter ╚═▷ 3283).
• The LogicsManager command flags 07.29 and 07.30 can be additionally used to
cause other actions according to the corresponding regulations of the grid.
• The QV Monitoring function according the German grid code VDE-AR-N 4105
depends on the parameter ╚═▷ 1770 "phase-phase/phase-neutral monitoring".
Fig. 188: QV monitoring - schematic

4 Configuration
[Default]
3292 Monitoring 2 On QV monitoring is carried out

parameters.
3285 Limit undervoltage 2 45 to 150% The percentage voltage value that

is to be monitored is defined here.
[85%]
If the voltages of all phases (one
phase in 1Ph 2W system) are
below this limit, the voltage
condition for tripping the
monitoring function is TRUE.
Notes
This value refers to the "Generator

1766).
3291 Reactive power 2 2 to 100% The percentage reactive value

threshold that is to be monitored is defined
[5%] here.
If the absolute value of reactive

power Q is higher than this
threshold, the reactive power
condition for tripping the
monitoring function is TRUE.
Notes
This value refers to the "Gen.

rated react. power [kvar]"
3283 Delay step 1 2 0.10 to 99.99 s If the QV monitoring conditions

are met, for the delay time
[0.50 s] configured here, an alarm "QV
monitoring 1" will be issued and
LogicsManager 07.29 becomes
TRUE.
Notes
The decoupling function is only

activated if "Mains decoupling by
QV" (parameter ╚═▷ 3296) is
configured to "On".
3284 Delay step 2 2 0.10 to 99.99 s If the QV monitoring conditions

are met, for the delay time
[1.50 s] configured here, an alarm "QV
monitoring 2" will be issued and
LogicsManager 07.30 becomes
TRUE.

4 Configuration
4.5.3.12 Change Of Frequency
3280 Alarm class 2 Class A/B/C/D/E/F, Control The alarm class specifies what
action should be taken when at
[B] least one delay has been
exceeded.
Notes
The alarm class is valid for

parameter ╚═▷ 3283 and ╚═▷
3284.



longer detected.

output "External
Notes
The self acknowledge is valid for

parameter ╚═▷ 3283 and ╚═▷
3284.

QV linked to the mains decoupling

function.
Phase shift
A vector/phase shift is defined as the sudden variation of the voltage curve which may be
caused by a major generator load change. It usually occurs, if the utility opens the MCB,
which causes a load change for the genset.
The genset control measures the duration of a cycle, where a new measurement is
started with each voltage passing through zero. The measured cycle duration will be
compared with an internal quartz-calibrated reference time to determine the cycle
duration difference of the voltage signal.

4 Configuration
The phase shift monitoring is a very sensitive functionality and reacts according to the
settings on each sinus wave constellation.
Please be aware that under special circumstances it may come to a phase shift trip,
when switching elements are taken into the mains measurement lines because mains
voltage sensing lines are switched nearby the genset control.
Fig. 189: Phase shift
A vector/phase shift as shown in ╚═▷ Fig. 189 causes a premature or delayed zero
passage. The determined cycle duration difference corresponds with the occurring phase
shift angle.
The monitoring may be carried out three-phased or one/three-phased. Different limits

may be configured for one-phase and three-phase monitoring. The vector/phase shift
monitor can also be used as an additional method to decouple from the mains. Vector/
phase shift monitoring is only enabled after the monitored voltage exceeds 50% of the PT
secondary rated voltage.
Function "Voltage cycle duration not within the permissible range"
The voltage cycle duration exceeds the configured limit value for the phase/vector shift.
The result is, that the power circuit breaker that disconnects from the mains, is opened,
the message "Mains phase shift" is displayed, and the logical command variable "07.14"
is enabled.
The prerequisite for phase/vector shift monitoring is that the generator is operating in a
mains parallel operation (the MCB and GCB are both closed).
df/dt (ROCOF)
df/dt (rate of change of frequency) monitoring measures the stability of the frequency.
The frequency of a source will vary due to changing loads and other effects. The rate of
these frequency changes due to the load variances is relatively high compared to those of
a large network.
Function "Rate of change of frequency not within permissible limits"
The control unit calculates the unit of measure per unit of time. The df/dt is measured
over 4 sine waves to ensure that it is differentiated from a phase shift. This results in a
minimum response time of approximately 100 ms (at 50 Hz).

4 Configuration
[Default]
3058 Change of frequency 2 Off Monitoring is disabled.
[Phase shift] Phase shift monitoring is carried

out according to the parameters
described in ╚═▷ “Phase shift”.
df/dt df/dt monitoring is carried out

according to the parameters
described in ╚═▷ “df/dt (ROCOF)”.
Phase shift df/dt Phase shift monitoring and df/dt

monitoring is carried out. Tripping
occurs if phase shift or df/dt is
triggered.
3053 Phase shift: 2 [1- and 3 phase] During single-phase voltage

Monitoring phase/vector shift monitoring,
tripping occurs if the phase/vector
shift exceeds the configured
threshold value (parameter ╚═▷
3054) in at least one of the three
phases.
3 phase During three-phase voltage phase/

vector shift monitoring, tripping
occurs only if the phase/vector
shift exceeds the specified
threshold value (parameter ╚═▷
3055) in all three phases within
2 cycles.
Notes
If a phase/vector shift occurs in

one or two phases, the single-
phase threshold value
(parameter ╚═▷ 3054) is taken
into consideration; if a phase/
vector shift occurs in all three
phases, the three-phase threshold
value (parameter ╚═▷ 3055) is
taken into consideration. Single
phase monitoring is very sensitive
and may lead to nuisance tripping
if the selected phase angle
settings are too small.
3 phase mains phase shift

monitoring is only enabled if
Mains voltage measuring
configured to "3Ph 4W" or "3Ph
3W".
3054 Phase shift: Limit 1 2 3 to 30° If the electrical angle of the mains
phase voltage shifts more than this
[20°] configured value in any single
phase, an alarm with the class
is initiated.
Depending on the configured

mains decoupling procedure
(parameter ╚═▷ 3110), the GCB,

4 Configuration
MCB, or an external CB will be

opened.
3055 Phase shift: Limit 3 2 3 to 30° If the electrical angle of the mains
phase voltage shifts more than this
[8°] configured value in all three
phases, an alarm with the class
is initiated.
Depending on the configured

opened.
3051 Phase shift: Alarm 2 Class A/B/C/D/E/F, Control Each limit may be assigned an
class independent alarm class that
Notes

3052 Phase shift: Self 2 [Yes] The control automatically clears

no longer detected.
No The control does not automatically

output "External
3056 Phase shift: Enabled 2 [Always] Monitoring for this fault condition

engine monitoring".
For xx = 1 to 32: Defining of an own release flag

through Logicsmanager equations.
96.{xx}
LM: Flag{xx}
FRT ROCOF enable The dynamic mains stabilization

according to VDE-AR-N 4110/4105
requires a temporary blocking of
the ROCOF monitor. Please refer
to the according VDE-AR-N rule.
3104 df/dt: df/dt Limit 2 0.1 to 9.9 Hz/s The df/dt threshold is defined
here. If this value is reached or

4 Configuration
[2.6 Hz/s] time without interruption, an

alarm with the class configured in
(Hysteresis: 0.1 Hz/s) parameter ╚═▷ 3101 is initiated.
(Reset Delay: 80 ms) Depending on the configured

opened.
3105 df/dt: Delay 2 0.10 to 2.00 s If the monitored rate of df/dt

If the monitored df/dt exceeds the

again before the delay expires the
time will be reset.
3101 df/dt: Alarm class 2 Class A/B/C/D/E/F, Control Each limit may be assigned an
Notes

3102 df/dt: Self 2 Yes The control automatically clears

no longer detected.

output "External
3103 df/dt: Enabled 2 [Always] Monitoring for this fault condition


engine monitoring".
For xx = 1 to 32: Defining of an own release flag

through Logicsmanager equations.
96.{xx}
LM: Flag{xx}
FRT ROCOF enable The dynamic mains stabilization

according to VDE-AR-N 4110/4105
requires a temporary blocking of

4 Configuration
4.5.3.13 Mains Voltage Phase Rotation
the ROCOF monitor. Please refer

to the according VDE-AR-N rule.
General notes
NOTICE!
Damage to the control unit and/or generation equipment
• Please ensure during installation that all voltages applied to this unit are wired
correctly to both sides of the circuit breaker.
Failure to do so may result in damage to the control unit and/or generation equipment
due to closing the breaker asynchronous or with mismatched phase rotations and phase
rotation monitoring enabled at all connected components (engine, generator, breakers,
cable, busbars, etc.).
This function will block a connection of systems with mismatched phases only under the
following conditions:
• The voltages being measured are wired correctly with respect to the phase rotation
at the measuring points (i.e. the voltage transformer in front and behind the circuit
breaker)
• The measuring voltages are wired without angular phase shift or interruption from
the measuring point to the control unit
• The measuring voltages are wired to the correct terminals of the control unit (i.e. L1
of the generator is connected with the terminal of the control unit which is intended
for the L1 of the generator)
• The LogicsManager function "Enable MCB" (refer to parameter ╚═▷ 12923) is false in
case of a incorrect rotation field
Correct phase rotation of the phase voltages ensures that damage will not occur during a
breaker closure to either the mains or the generator. The voltage phase rotation alarm
checks the phase rotation of the voltages and the configured phase rotation to ensure
they are identical.
The directions of rotation are differentiated as "clockwise" and "counter clockwise". With
a clockwise field the direction of rotation is "L1-L2-L3"; with a counter clockwise field the
direction of rotation is "L1-L3-L2".
If the control is configured for a clockwise rotation and the voltages into the unit are
calculated as counterclockwise the alarm will be initiated. The direction of configured
rotation being monitored by the control unit is displayed on the screen.
If this protective function is triggered, the display indicates "Mns.ph.rot. mismatch" and

4 Configuration
This monitoring function is only enabled if Mains voltage measuring (parameter ╚═▷
1853) is configured to "3Ph 4W" or "3Ph 3W" and the measured voltage exceeds 50 % of
the rated voltage (parameter ╚═▷ 1768) or if Mains voltage measuring (parameter ╚═▷
1853) is configured to "1Ph 2W" (in this case, the phase rotation is not evaluated, but
defined by the 1Ph2W phase rotation (parameter ╚═▷ 1859)).
[Default]
3970 Monitoring 2 [On] Phase rotation monitoring is

3974 Mains phase rotation 2 [CW] The three-phase measured mains

voltage is rotating CW (clock-wise;
that means the voltage rotates in
L1-L2-L3 direction; standard
setting).
CCW The three-phase measured mains

voltage is rotating CCW (counter
clock-wise; that means the
voltage rotates in L1-L3-L2
direction).
Notes
CAUTION: If an alarm class that

leads to an engine shutdown
(alarm class C or higher) is
configured into this parameter, a
main phase rotation alarm may
lead to a genset shutdown due to
an alarm of class C or higher.



longer detected.

output "External

4 Configuration
4.5.3.14 Mains Import Power (Level 1 & 2)


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
It is possible to monitor two independently configurable mains import power limit values.
This function makes it possible to initiate external load shedding.
If this protective function is triggered, the display indicates "Mains import power 1" or
"Mains import power 2" and the logical command variable "07.21" or "07.22" will be
enabled.
[Default]
3200 Monitoring 2 On Mains import power monitoring is

< Level 2 limit).

3215 Monitoring at 2 [Overrun] The monitored value must exceed

the limit to be considered as out
3216 of limits.
Underrun The monitored value must fall

below the limit to be considered
as out of limits.
3204 Limit 2 0 to +150.00% If this threshold value has been

exceeded or fallen below
3210 3204: [80.00%] (depending on the setting of
parameter ╚═▷ 3215 or ╚═▷ 3216)
3210: [100.00%] for at least the delay time
(parameter ╚═▷ 3205 or ╚═▷
3211), the action specified by the
alarm class is initiated.

4 Configuration
Notes

╚═▷ 1748).
3213 Hysteresis 2 0 to 99.99% The monitored mains power level

must return within the limits
3214 [0.01%] configured in parameter ╚═▷ 3204
or ╚═▷ 3210 plus or minus
(Reset Delay: 80 ms) (depending on the setting of
parameter ╚═▷ 3215 or ╚═▷ 3216)
the alarm.
3205 Delay 2 0.02 to 99.99 s If the monitored mains import

power falls below or exceeds
3211 [1.00 s] (depending on the setting of
parameter ╚═▷ 3215 or ╚═▷ 3216)
will be issued.
Notes
If the monitored mains import

power exceeds or falls below the
threshold (plus or minus the
hysteresis configured in
parameter ╚═▷ 3213 or ╚═▷ 3214)
will be reset.
3207: [B]
Notes

3202 Self acknowledge 2 3202: [Yes] The control unit automatically

3208: [No] The control unit does not

longer detected.

output "External

3209

4 Configuration
4.5.3.15 Mains Export Power (Level 1 & 2)

engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
It is possible to monitor two independently configurable mains export power limit values.
This function makes it possible to initiate external load shedding.
If this protective function is triggered, the display indicates "Mains export power 1" or
"Mains export power 2" and the logical command variable "07.23" or "07.24" will be
enabled.
[Default]
3225 Monitoring 2 On Mains export power monitoring is

< Level 2 limit).


the limit to be considered as out
3240 of limits.

below the limit to be considered
as out of limits.
3229 Limit 2 0 to +150.00% If this threshold value has been

exceeded or fallen below
3237 3229: [80.00%] (depending on the setting of
parameter ╚═▷ 3232 or ╚═▷ 3240)
3237: [100.00%] for at least the delay time
(parameter ╚═▷ 3230 or ╚═▷
3238), the action specified by the
alarm class is initiated.
Notes

╚═▷ 1748).

4 Configuration
3231 Hysteresis 2 0 to 99.99% The monitored mains power level

must return within the limits
3239 [0.01%] configured in parameter ╚═▷ 3229
or ╚═▷ 3237 plus or minus
(Reset Delay: 80 ms) (depending on the setting of
parameter ╚═▷ 3232 or ╚═▷ 3240)
the alarm.
3230 Delay 2 0.02 to 99.99 s If the monitored mains export

power falls below or exceeds
3238 [1.00 s] (depending on the setting of ns
export power falls below or
exceeds (depending on the setting
of parameter ╚═▷ 3232 or ╚═▷
3240) the threshold value for the
delay time configured here, an
Notes
If the monitored mains import

power exceeds or falls below the
threshold (plus or minus the
hysteresis configured in
parameter ╚═▷ 3231 or ╚═▷ 3239)
will be reset.
3234: [B]
Notes

3227 Self acknowledge 2 3227: [Yes] The control unit automatically

3235: [No] The control unit does not

longer detected.

output "External

3236
engine monitoring".

4 Configuration
4.5.3.16 Engine/Mains Active Power Mismatch

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4.5.3.16 Engine/Mains Active Power Mismatch
General notes
If enabled, this monitoring function becomes only active if generator power control is
enabled and the active power setpoint is configured to "Import" or "Export" (refer to ╚═▷
“4.4.4.5 Load Control”). If the measured import or export power deviates from the power
setpoint by a value exceeding the limit configured in parameter ╚═▷ 2935 for a time
exceeding the delay configured in parameter ╚═▷ 2933, an alarm will be issued.
If this protective function is triggered, the display indicates "Mns act.pwr mismatch" and
[Default]
2930 Monitoring 2 [On] On Monitoring of the mains active

power mismatch is carried out
parameters.
2935 Limit 2 1.0 to 99.9% If the difference between the

measured import or export power
[5.0%] and the power setpoint exceeds
this value for at least the delay
time (parameter ╚═▷ 2933)
without interruption, the action
initiated.
Notes
This value refers to the mains

╚═▷ 1748).
2933 Delay 2 3 to 9999 s If the monitored active power

[30 s] value configured in
parameter ╚═▷ 2935 for the delay
will be issued.
Notes
If the monitored active power


4 Configuration
4.5.3.17 Mains Lagging Power Factor (Level 1 & 2)

will be reset.
Notes



longer detected.

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
The power factor is monitored for becoming more lagging (i.e. inductive) than an
adjustable limit. This limit may be a lagging or leading power factor limit. There are two
lagging power factor alarm levels available in the control. This monitoring function may
be used for monitoring or controlling the power factor compensation. Both alarms are
definite time alarms.

4 Configuration
Power Factor
Leading (capacitive) Lagging (inductive)
More lagging than a leading More lagging than a lagging

PF limit of -0.40 PF limit of +0.85
-0.40 +0.85
-0.50 -0.75 1.00 +0.75 +0.50
Import Inductive Power Export Inductive Power
Fig. 190: Mains lagging power factor
power factor range, for which the lagging power factor monitoring issues an alarm.
If this protective function is triggered, the display indicates "Mains PF lagging 1" or
"Mains PF lagging 2" and the logical command variable "07.17" or "07.18" will be
enabled.
[Default]
2975 Monitoring 2 On Mains lagging power factor



2983 2978: [+ 0.900] are defined here.
2983: [+ 0.800] Notes
If the power factor becomes more

lagging (i.e. inductive, ╚═▷
Fig. 190) than a lagging PF value
(pos.) or a leading PF value (neg.)
for at least the delay time
(parameters ╚═▷ 2979 or ╚═▷
2984) without interruption, the
logical command variables 07.17
(level 1) or 07.18 (level 2) are
enabled and the action specified
2989 Hysteresis 2 0.0 to 0.99 The monitored power factor must

return within the limits configured
2990 [0.02] in parameter ╚═▷ 2978 or ╚═▷
2983 minus the value configured
here, to reset the alarm.

4 Configuration
(Reset Delay: 80 ms)

factor is more lagging than the
2984: [1.00 s] issued.
Notes

(minus the Hysteresis configured
in parameter ╚═▷ 2989 or ╚═▷
2990) before the delay expires the
time will be reset.
2988 [B] specifies what action should be
Notes



longer detected.

output "External

2982
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32

4 Configuration
4.5.3.18 Mains Leading Power Factor (Level 1 & 2)
General notes
The power factor is monitored for becoming more leading (i.e. capacitive) than an
adjustable limit. This limit may be a leading or lagging power factor limit. There are two
leading power factor alarm levels available in the control. This monitoring function may
be used for monitoring or controlling the power factor compensation. Both alarms are
definite time alarms.
Fig. 191: Mains leading power factor
power factor range, for which the leading power factor monitoring issues an alarm.
If this protective function is triggered, the display indicates "Mains PF leading 1" or
"Mains PF leading 2" and the logical command variable "07.19" or "07.20" will be
enabled.
[Default]
3025 Monitoring 2 On Mains leading power factor



3033 3028: [- 0.900] are defined here.
3033: [- 0.800] Notes
If the power factor becomes more

leading (i.e. inductive, ╚═▷
Fig. 191) than a leading PF value
(pos.) or a leading PF value (neg.)
for at least the delay time
(parameters ╚═▷ 3029 or ╚═▷
3034) without interruption, the

4 Configuration
logical command variables 07.17

(level 1) or 07.18 (level 2) are
enabled and the action specified
3039 Hysteresis 2 0.0 to 0.99 The monitored power factor must

return within the limits configured
3040 [0.02] in parameter ╚═▷ 3028 or ╚═▷
3033 minus the value configured
(Reset Delay: 80 ms) here, to reset the alarm.

factor is more leading than the
3034: [1.00 s] issued.
Notes

(minus the Hysteresis configured
in parameter ╚═▷ 3039 or ╚═▷
3033) before the delay expires the
time will be reset.
Notes



longer detected.

output "External

3032
engine monitoring".

TRUE.

4 Configuration
4.5.4 Breaker
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4.5.4 Breaker
4.5.4.1 Configure GCB
General notes
Circuit breaker monitoring contains two alarms: A "breaker reclose" alarm and a "breaker
open" alarm.
"Breaker reclose alarm"
If the control initiates a close of the breaker and the breaker fails to close after the
configured number of attempts the monitoring CB alarm will be initiated (refer to
parameter "GCB maximum closing attempts", parameter ╚═▷ 3418).
If this protective function is triggered, the display indicates "GCB fail to close" and the
"Breaker open alarm"
If the control is attempting to open the circuit breaker and it fails to see that the CB is
open within the configured time in seconds after issuing the breaker open command then
the monitoring CB alarm will be initiated (refer to parameter "GCB open monitoring",
NOTICE!
If load-dependent start/stop (refer to ╚═▷ “4.4.5.5 Load Dependent Start/Stop (LDSS)”) is

enabled, this monitoring function must be configured with a shutdown alarm class C, D,
E, or F) or disable load-dependent start/stop if triggered to ensure that the next engine
will be started.
If this protective function is triggered, the display indicates "GCB fail to open" and the
[Default]
2600 Monitoring 2 [On] Monitoring of the GCB is carried

parameters.
2601 GCB Alarm class 2 Class A/B/C/D/E/F/Control Each limit may be assigned an

4 Configuration
4.5.4.2 Configure GCB 50BF

Notes

3418 GCB maximum 2 1 to 10 The maximum number of breaker

closing attempts closing attempts is configured in
[5] this parameter (relay output
"Command: close GCB").
When the breaker reaches the

configured number of attempts, a
"GCB fail to close" alarm is issued.
The counter for the closure

attempts will be reset as soon as
the "Reply GCB" is de-energized
for at least 5 seconds to signal a
closed GCB.
3420 GCB open monitoring 2 0.10 to 5.00 s If the "Reply GCB" is not detected
as energized once this timer
[2.00 s] expires, a "GCB fail to open" alarm
is issued. This timer initiates as
soon as the "open breaker"
sequence begins. The alarm
is issued.
General notes
50BF is a breaker monitoring function which is tripping if the breaker reply is indicating an
open breaker but there is still a current measured which is exceeding a configurable
threshold. It is a kind of plausibility check between breaker reply and measurement.
This monitoring function is only working if the measured current is below 320% of rated
current.
[Default]
1929 Monitoring 2 [On] Monitoring of the GCB 50BF is

1930 Limit 2 2 to 100 % If the average generator current

has reached or exceeded this limit
[2.00 %] for at least the delay time without
interruption and the breaker reply
indicates open, the action

4 Configuration

initiated.
1931 Delay 2 0.02 to 99.90 s If the conditions are fullfilled for

the time configured here, an
[0.20 s] alarm will be issued.
The message "GCB failure 50BF"

is issued and the logical command
variable "08.46" will be enabled.
1932 Alarm class 2 Class A/B/C/D/E/F/Control Each limit may be assigned an

Notes



longer detected.

output "External


engine monitoring".
For xx = 1 to 32: 96.{xx} LM: The monitoring is executed, if the

Flag{xx} LogicsManager "Flag {xx}" is
TRUE. Example: 96.01 LM: Flag1,
96.02 LM: Flag2, ..., 96.32 LM:
Flag32

4 Configuration
4.5.4.3 Synchronization GCB
4.5.4.3 Synchronization GCB
General notes
NOTICE!

will be started.
[Default]
3060 Monitoring 2 [On] Monitoring of the GCB

synchronization is carried out
parameters.
3063 Delay 2 3 to 999 s If it was not possible to

synchronize the GCB within the
[60 s] time configured here, an alarm
will be issued.
The message "GCB syn. timeout"

Notes



longer detected.

output "External

4 Configuration
4.5.4.4 Configure MCB
General notes
If an alarm is detected when attempting to close the MCB, an emergency power

operation will be carried out if the "Emergency start with MCB failure" is "On".
If an alarm class higher than 'B' class has been selected it will not be possible to start the
engine with the setting "Emergency start with MCB failure" (parameter ╚═▷ 3408) =
configured as "On" in an emergency power condition.
All parameters listed below only apply to application mode A04 .
Circuit breaker monitoring contains two alarms: A breaker reclose alarm and a breaker
open alarm.
"Breaker reclose alarm"
If the control unit initiates a close of the breaker and the breaker fails to close after the
configured number of attempts the monitoring CB alarm will be initiated.
• Refer to parameter "MCB maximum closing attempts", parameter ╚═▷ 3419.
If this protective function is triggered, the display indicates "MCB fail to close" and the
"Breaker open alarm"
If the control unit is attempting to open the circuit breaker and it fails to see that the CB is
open within the configured time in seconds after issuing the breaker open command then
the monitoring CB alarm will be initiated.
• Refer to parameter "MCB open monitoring", parameter ╚═▷ 3421.
If this protective function is triggered, the display indicates "MCB fail to open" and the
Fault at 'closing the MCB'
Alarm classes A & B
• Parameter ╚═▷ 2802 "Emergency run" = Off;
If the MCB cannot be closed, the busbar remains without voltage, until the MCB
breaker fault is acknowledged.
The control continues attempting to close the MCB.

4 Configuration
• Parameter ╚═▷ 2802 "Emergency run" = On, parameter ╚═▷ 3408 "Emergency start
with MCB failure" = Off;
If the MCB cannot be closed, the busbar remains without voltage, until the MCB
breaker fault is acknowledged.
The control continues attempting to close the MCB.
• Parameter ╚═▷ 2802 "Emergency run" = On, parameter ╚═▷ 3408 "Emergency start
with MCB failure" = On;
If the MCB cannot be closed, an emergency power operation is initiated (the engine
is started and the GCB is closed; the busbar is supplied by the generator).
If the alarm is acknowledged and if the MCB can be closed, the load is switched to
mains supply and the emergency power operation terminates.
Fault at 'opening the MCB'
This alarm class has the following influence to the function of the unit:
• This fault is processed according to the action described within the alarm classes. As
long as the reply is present that the MCB is still closed, the GCB cannot be closed.
[Default]
2620 MCB monitoring 2 [On] Monitoring of the MCB is carried

parameters.
2621 MCB Alarm class 2 Class A/B/C/D/E/F/Control Each limit may be assigned an
Notes

3419 MCB maximum 2 1 to 10 The maximum number of breaker

closing attempts closing attempts is configured in
[5] this parameter (relay output
"Command: close MCB").
When the breaker reaches the

configured number of attempts,
an "MCB fail to close" alarm is
issued.
The counter for the closure

attempts will be reset as soon as
the "Reply MCB" is de-energized
for at least 5 seconds to signal a
closed MCB.
3421 MCB open monitoring 2 0.10 to 5.00 s If the "Reply MCB" is not detected
as energized once this timer

4 Configuration
4.5.4.5 Synchronization MCB
[2.00 s] expires, an "MCB fail to open"

alarm is issued.
This timer initiates as soon as the

"open breaker" sequence begins.
The alarm configured in
parameter ╚═▷ 2621 is issued.
4.5.4.5 Synchronization MCB
[Default]
3070 Monitoring 2 [On] Monitoring of the MCB

synchronization is carried out
parameters.
3073 Timeout 2 3 to 999 s If it was not possible to

synchronize the MCB within the
[60 s] time configured here, an alarm
will be issued.
The message "MCB syn. timeout"

Notes



longer detected.

output "External

4 Configuration
4.5.4.6 Configure MCB 50BF
4.5.4.6 Configure MCB 50BF
50BF is a breaker monitoring function which is tripping if the breaker reply is indicating an
open breaker but there is still a current measured which is exceeding a configurable
threshold. It is a kind of plausibility check between a breaker reply and a measurement.
This monitoring function is only working if the measured current is below 320% of rated
current!
[Default]
1934 Monitoring 2 [Off] Monitoring is disabled.
On Monitoring of the MCB 50BF is

1935 Limit 2 2 to 100 % If the mains current has reached

or exceeded this limit for at least
[2.00 %] the delay time without
interruption and the breaker reply
indicates open, the action
initiated.
1936 Delay 2 3 to 999 s If the conditions are fulfilled for

the time configured here, an
[60 s] alarm will be issued.
The message "MCB failure 50BF"


Notes



longer detected.

output "External

4 Configuration
4.5.4.7 MCB plausibility



engine monitoring".

96.02 LM: Flag2, ..., 96.32 LM:
Flag32
4.5.4.7 MCB plausibility
If breaker mode GCB/MCB is configured, this alarm trips (according to the monitor
settings) if the number of closed MCBs is different to the number of easYgen devices in
the same segment.
[Default]
1941 Monitoring 2 [Off] Monitoring is disabled.
On Monitoring of the MCB plausibility

1942 Delay 2 0.02 to 99.90 s If the conditions are fulfilled for

this time the alarm "MCB
[0.20 s] plausibility" will trip and the
command variable 08.48 becomes
active.
1943 Alarm class 2 Class A/B/C/D/E/F, Control An alarm can be assigned that
[B] taken when the conditions are
fulfilled.
Notes



longer detected.

4 Configuration
4.5.4.8 Configure Neutral Contactor

output "External


engine monitoring".

96.02 LM: Flag2, ..., 96.32 LM:
Flag32
4.5.4.8 Configure Neutral Contactor
General notes
The monitoring of the Neutral Contactor (NC) feedback "Neutral contactor reply
mismatch" 17.09 is performed always, if the Neutral Interlocking (parameter ╚═▷ 1840)
and the Monitoring function are enabled (parameter ╚═▷ 5148). The monitor checks, if
the feedback behaves according to the NC command. With a configurable delay time, the
alarm is activated with a general alarm text. Open failure or closure failure are not
differentiated.
Please refer to ╚═▷ “6.3.14 Neutral Interlocking” for more details.
[Default]
5148 Monitoring 2 On Monitoring of the Neutral

Contactor is carried out according
to the following parameters, if the
Neutral Interlocking function
(parameter ╚═▷ 1840) is enabled .
5152 Delay 2 0.10 ... 5.00 s Period of continuous failure signal

before tripping a failure.
[2.00 s]
5149 Alarm class 2 Class A/B/C/D/E/F/CONTROL This function may be assigned an

taken when this function triggers
an alarm.
Notes

4 Configuration
4.5.5 Flexible Limits


no longer detected.

output "External
5153 Alarm text - [N-cont. reply mism.] Text is visible in display during
alarm is detected.
General notes
CAUTION!
Hazards due to improper configuration of protective functions
Flexible Limits must not be used for protective functions, because the monitoring
function is not guaranteed beyond an exceeding of 320 %.
It is not possible to monitor temperature values in Degree Fahrenheit and pressure

values in psi. Although parameters ╚═▷ 3631 or ╚═▷ 3630 are configured to a value
display in °F or psi, flexible limit monitoring always refers to the value in Degree Celsius
or bar (J1939 protocol: kPa).
This control unit offers 40 flexible limits. They may be used for "limit switch" functions of
all measured analog values. It is possible to choose between alarm (warning and
shutdown) and control operation via the LogicsManager.
If an alarm class is triggered, the display indicates "Flexible limit {x}", where {x}
indicates the flexible limit 1 to 40, or the text configured using ToolKit and the logical
command variable "15.{x}" will be enabled.
The flexible limits 25 through 32 are configurable additionally with a 'Fallback time' e.g.,
for load shedding.
The flexible limits 33 through 40 are disabled during idle mode operation (refer to ╚═▷
“4.4.1.4 Idle Mode”).

4 Configuration
The following parameter description refers to flexible limit 1. The flexible limits 2 through
40 are configured accordingly. The parameter IDs of the flexible limits 2 through 40 are
listed below.
[Default]
4208 Description 2 user defined (up to 39 characters)
[Flex. limit {x}]

A description for the respective
flexible limit may be entered here.
The description may have 4
through 20 characters and is
displayed instead of the default
text if this limit is exceeded.
Notes

as headline on detail screen.
Selection screen on HMI/display
works fine with up to 30
characters; others are overwritten
by mandatory screen symbols.

for each character.

4200 Monitoring 2 On Monitoring of the limit {x} is


the threshold limit for a fault to be
recognized.

below the threshold limit for a
fault to be recognized.
4205 Limit 2 -21000000.00 to 21000000.00 The threshold limit of the value to

be monitored is defined by this
[100] parameter. If this value is reached
or exceeded / fallen below
(dependent on parameter ╚═▷
4207) for at least the delay time
class is initiated after the
configured delay expires.

4 Configuration
The entry format of the threshold

depends on the respective analog
value.
If the monitored analog value has

a reference value, the threshold is
expressed as a percentage of this
reference value (-320.00 % to
320.00 %). If an analog input is
monitored, the threshold refers to
the display value format (refer to
╚═▷ “9.4.3.12 Display Value
Format”).
Notes
Refer to ╚═▷ “Examples” for

examples on how to configure the
limit.
4216 Hysteresis 2 0 to 21000000.00 During monitoring, the actual

value must exceed or fall below
[1.00] one of the limits defined in
parameter ╚═▷ 4205 to be
recognized as out of permissible
limits. For a value to register as
having returned to the permissible
limits, the monitored value must
rise above or fall below this value
for the hysteresis.
The format for entering the

hysteresis depends on the
monitored analog input and
corresponds with the one of the
threshold listed in parameter ╚═▷
4205.
4207 Delay 2 0.02 to 99999.99 s If the monitored value exceeds or

alarm will be issued. If the
monitored value falls below the
threshold (plus/minus the
hysteresis, dependent on
parameter ╚═▷ 4204) before the
delay expires the time will be
reset.
Beginning: For flexible limit 25 ... 32 only; sample refers to flexible limit #25.
6646 Fallback time 2 00.02 to 327.00 s If the monitored value exceeds or

falls below the threshold value, a
[1.00 s] counter will start and finally
disable the alarm. If the monitored
value comes back into the
threshold value (plus/minus the
hysteresis) before the fallback
time expires the time will be reset.
End: For flexible limit 25 ... 32 only; sample referred to flexible limit #25.
Notes

4 Configuration



longer detected.

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4206 AM FlexLim 1 source 2 Determined by AnalogManager Any possible data sources may be
82.01 selected. Analog and digital OUT
value/signal are available as
[A1 = 10.01 ZERO] sources for AnalogManager and
LogicsManager.

Parameter IDs
Flexible Descrip‐ Monitor‐ Monitor‐ Monitor‐ Limit Hyster‐ Delay Alarm Self Enabled
limit # tion ing ed ing at esis class acknow‐
analog Fallback ledge
value
1 4208 4200 4206 4204 4205 4216 4207 4201 4202 4203
2 4225 4217 4223 4221 4222 4233 4224 4218 4219 4220
3 4242 4234 4240 4238 4239 4250 4241 4235 4236 4237
4 4259 4251 4257 4255 4256 4267 4258 4252 4253 4254
5 7108 4270 4276 4274 4275 4278 4277 4271 4272 4273
6 7116 4280 4286 4284 4285 4288 4287 4281 4282 4283

4 Configuration
value
7 7124 4290 4296 4294 4295 4298 4297 4291 4292 4293
8 7132 6000 6006 6004 6005 6008 6007 6001 6002 6003
9 7140 6010 6016 6014 6015 6018 6017 6011 6012 6013
10 7148 6020 6026 6024 6025 6028 6027 6021 6022 6023
11 7156 6030 6036 6034 6035 6038 6037 6031 6032 6033
12 7164 6040 6046 6044 6045 6048 6047 6041 6042 6043
13 7172 6050 6056 6054 6055 6058 6057 6051 6052 6053
14 7180 6060 6066 6064 6065 6068 6067 6061 6062 6062
15 7188 6070 6076 6074 6075 6078 6077 6071 6072 6073
16 7196 6080 6086 6084 6085 6088 6087 6081 6082 6083
17 7204 6090 6096 6094 6095 6098 6097 6091 6092 6093
18 7212 6100 6106 6104 6105 6108 6107 6101 6102 6103
19 7220 6110 6116 6114 6115 6118 6117 6111 6112 6113
20 7228 6120 6126 6124 6125 6128 6127 6121 6122 6123
21 7236 6130 6136 6134 6135 6138 6137 6131 6132 6133
22 7244 6140 6146 6144 6145 6148 6147 6141 6142 6143
23 7252 6150 6156 6154 6155 6158 6157 6151 6152 6153
24 7260 6160 6166 6164 6165 6168 6167 6161 6162 6163
25 7268 6170 6176 6174 6175 6178 6177 6171 6172 6173
6646
26 7276 6180 6186 6184 6185 6188 6187 6181 6182 6183
6647
27 7284 6190 6196 6194 6195 6108 6197 6191 6192 6193
6648
28 7292 6200 6206 6204 6205 6208 6207 6201 6202 6203
6649
29 7300 6210 6216 6214 6215 6218 6217 6211 6212 6213
6650
30 7308 6220 6226 6224 6225 6228 6227 6221 6222 6223
6651
31 7316 6230 6236 6234 6235 6238 6237 6231 6232 6233
6652
32 7324 6240 6246 6244 6245 6248 6247 6241 6242 6243
6653
33 7332 6250 6256 6254 6255 6258 6257 6251 6252 6253
34 7340 6260 6266 6264 6265 6268 6267 6261 6262 6263

4 Configuration
value
35 7348 6270 6276 6274 6275 6278 6277 6271 6272 6273
36 7356 6280 6286 6284 6285 6288 6287 6281 6282 6283
37 7364 6290 6296 6294 6295 6298 6297 6291 6292 6293
38 7372 6300 6306 6304 6305 6308 6307 6301 6302 6303
39 7380 6310 6316 6314 6315 6318 6317 6311 6312 6313
40 7388 6320 6326 6324 6325 6328 6327 6321 6322 6323
Tab. 71: Flexible limits - parameter IDs
Examples
Example value Desired limit Reference value / display Limit entry format
value
01.24 Total generator real 160 kW Generator rated real power 8000 (= 80.00%)
power in % (parameter ╚═▷ 1752) =
200 kW
01.09 Generator frequency 51.5 Hz Rated frequency 10300 (= 103.00%)

in % (parameter ╚═▷ 1750) = 50
Hz
11.01 Engine speed 1256 rpm Rated speed 08373 (= 83.73%)

(parameter ╚═▷ 1601) =
1500 rpm
06.03 Analog input 3 4.25 bar Display in 0.01 bar 00425 (= 4.25 bar)
(configured to VDO 5 bar)
06.02 Analog input 2 123 °C Display in °C 00123 (= 123 °C)

(configured to VDO 150 °C)
06.03. Analog input 3 10 mm Display in 0.000 m 00010 (= 0.010 mm)

(configured to Linear, Value
at 0% = 0, Value at 100% = (parameter ╚═▷ 1035
1000) configured to 0.000 m)
Tab. 72: Flexible limits - analog value examples
The flexible limits must be used to monitor analog inputs like oil pressure or coolant
temperature for example. We recommend to change the flexible limit description
accordingly.
The table below gives some configuration examples. The analog inputs must be
configured accordingly.
Parameter Example for low oil pressure Example for high coolant
monitoring temperature monitoring
Description Oil pressure Coolant temp.
Monitoring On On
Monitored data source 06.01 Analog input 1 06.02 Analog input 2
Monitoring at Underrun Overrun
Limit 200 (2.00 bar) 80 (80 °C)

4 Configuration
4.5.6 Miscellaneous
Parameter Example for low oil pressure Example for high coolant
monitoring temperature monitoring
Hysteresis 10 2
Delay 0.50 s 3s
Alarm class F B
Self acknowledgment No No
Delayed by engine speed Yes No
Tab. 73: Flexible limits - configuration examples
4.5.6 Miscellaneous
4.5.6.1 General monitoring settings
[Default]
1756 Time until horn reset 0 0 to 1,000 s After each alarm of alarm class B
through F occurs, the alarm LED
[180 s] flashes and the horn (command
variable 03.05) is enabled. After
the delay time "time until horn
reset" has expired, the horn
(command variable 03.05) is
disabled. The alarm LED flashes
until the alarm has been
acknowledged either via the push
button, the LogicsManager, or the
interface.
Notes

0, the horn will remain active until
it will be acknowledged.
12490 Ext. acknowledge 2 Determined by LogicsManager It is possible to acknowledge all

86.15 alarms simultaneously from
(External remote, e.g. with a discrete input.
acknowledgment of [(09.05 Discrete input 5 & 1) The logical output of the
alarms) OR 04.14 Remota LogicsManager has to become
acknowledge] TRUE twice.
= 10714 The first time is for acknowledging

the horn, the second for all alarm
messages. The On-delay time is
the minimum time the input
signals have to be "1". The Off-
delay time is the time how long
the input conditions have to be
"0" before the next high signal is
accepted.

LogicsManager have been fulfilled
the alarms will be acknowledged.

4 Configuration
4.5.6.1 General monitoring settings
The first high signal into the

discrete input acknowledges the
command variable 03.05 (horn).
The second high signal

acknowledges all inactive alarm
messages.
Notes

1849 Stop mode with 2 If operating mode is not fixed via LogicsManager (see chapter ╚═▷
stopping alarm “6.3.5 Performing Remote Start/Stop And Acknowledgment” for details)
with this parameter it can be decided if the operation mode changes to
STOP mode when a shutdown alarm of class C, D, E, F occurs.
No A shut down alarm does not cause

an operating mode change.
This can be useful in applications

with remote control, where the
operator wants to acknowledge
alarms and restart the engine
without the need to change
operating mode in the easYgen.
Notes
If the shut down alarm disappears,

generator can start automatically!
[Yes] Each shut down alarm (class C, D,

E, F) will change operating mode
to STOP.
Notes
LM ╚═▷ 12510, ╚═▷ 12520, ╚═▷

12530 do have priority.
5775 IOP Delayed unload. 2 0 to 9999 s This parameter gives a load

Alarm C,E sharing participant the
[0 s] opportunity to delay the unload if
an shutdown alarm of alarm class
C or E occurs. The time gained
gives another generator the
chance to participate in the load
sharing network.
The time configured here delays

the triggering of alarm class C and
E. A setting of 0 s deactivates this
function.
Notes


4 Configuration
4.5.6.2 Free Configurable Alarms
General Notes
The easYgen-XT provides 16 freely configurable alarms.
Each alarm is configurable by:
• A LogicsManager equation
• Alarm text/description (configurable with ToolKit only)
• Delay time
• Alarm class
• Self acknowledgment
• Being enabled depending on Engine Monitoring LM 87.70 (selectable)
Free Alarm 1 for example
[Default]
8120 Free alarm 1 2 Determined by LogicsManager This LogicsManager is used to

88.01 select the source of monitoring.
[02.01 FALSE & 1 & 1] Notes

8121 Alarm class 2 Class A/B/C/D/E/F, Control The assigned independent alarm
class specifies what action should
[Class B] be taken when the alarm becomes
TRUE.
8122 Self acknowledge 2 Yes/No The control automatically clears

no longer detected.

output "External


engine monitoring".

4 Configuration
4.5.6.3 CAN Interfaces

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
8236 Delay 2 0.02 to 99999.99 s Period before alarm becomes

TRUE.
[1.00 s]
6680 Description 2 [Free alarm 1] Text is configurable by ToolKit.
...((30 characters))* Notes
*) The max. number of characters

is 48 but 30 characters can be
read on easYgen HMI without
restrictions.
Parameter IDs
Free alarm # Description Logics‐ Alarm class Self acknow‐ Enabled Delay
Manager ledge
1 6680 8120 8121 8122 8123 8236
2 6681 8124 8125 8126 8127 8237
3 6682 8128 8129 8130 8131 8238
4 6683 8132 8133 8134 8135 8239
5 6688 8136 8137 8138 8139 8240
6 6689 8140 8141 8142 8143 8241
7 6690 8144 8145 8146 8147 8242
8 6691 8148 8149 8152 8153 8243
9 6692 8154 8155 8156 8157 8244
10 6693 8158 8159 8161 8163 8245
11 6694 8165 8167 8168 8169 8246
12 6695 8170 8171 8172 8173 8247
13 6696 8174 8175 8176 8177 8248
14 6697 8178 8179 8180 8181 8249
15 6698 8182 8183 8184 8185 8250
16 6699 8186 8187 8188 8189 8251
Tab. 74: Free alarms - parameter IDs
4.5.6.3 CAN Interfaces
• CAN Interface 1: See ╚═▷ “4.5.6.4 CAN Interface 1”.
• CAN Interface 2: See ╚═▷ “4.5.6.5 CAN Interface 2”.

4 Configuration
4.5.6.4 CAN Interface 1
General notes
The CANopen interface 1 is monitored. If the interface does not receive a Receive Process
Data Object (RPDO) before the delay expires, an alarm will be initiated.
If this protective function is triggered, the display indicates "CANopen interface 1" and
[Default]
3150 Monitoring 2 On CANopen interface 1 monitoring is

3154 Delay 2 0.01 to 650.00 s The maximum receiving break is

configured with this parameter.
[0.20 s]
If the interface does not receive
an RPDO within this time, the
is initiated. The delay timer is re-
initialized after every message is
received.

Notes



longer detected.

output "External


4 Configuration

engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
Fig. 192: CAN2 state
The CANopen interface 2 is monitored. If the interface does not receive a message from
the external expansion board (Node-ID) before the delay expires, an alarm will be
initiated. This is indicated in menu [Next Page/STATUS MENU / Diagnostic / Interfaces /
CAN / CAN 2 state]
If this protective function is triggered, the display indicates "CANopen interface 2" and
If you are not using the exact amount of external I/O modules you have defined, the
monitoring function does not work correctly.

4 Configuration
[Default]
16187 Monitoring 2 On CANopen interface 2 monitoring is

16186 Delay 2 0.01 to 650.00 s The maximum receiving break is

[0.20 s]
If the interface does not receive
message from the external
expansion board (Node-ID) within
this time, the action specified by
the alarm class is initiated. The
delay timer is re-initialized after
every message is received.

Notes



longer detected.

output "External


engine monitoring".

96.{xx} TRUE.

4 Configuration
4.5.6.6 CAN Interface 2 - J1939 Interface
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
This monitor function can monitor messages of up to 4 different J1939 devices separately
by their source addresses.
If the easYgen doesn’t receive any message from the corresponding device within the
configured time the command variable 08.10 “CAN fault J1939” becomes active.
Additionally a specific alarm 08.37: “J1939 ECU timeout”, 08.38: “J1939 dev. 1 timeout”,
08.39: “J1939 dev. 2 timeout”, or 08.40: “J1939 dev. 3 timeout” will be triggered.
ECU settings
[Default]
15172 Monitoring 2 On Monitoring of the ECU's CAN

messages is carried out according
to the following parameters. The
address of the ECU is taken from
parameter “Engine control
address” (╚═▷ 15107)
15176 Delay 2 0.02 to 999 s The delay is configured with this

parameter. If the interface does
[1 s] not receive a CAN message from
the ECU within this delay time, the
is initiated.
The delay timer is re-initialized if

any message from the ECU is
received.
15173 Alarm class 2 Class A/B/C/D/E/F/Control Each limit may be assigned to an

Notes



longer detected.

output "External

4 Configuration
[Default]



engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
Tab. 75: J1939 Monitoring
Device 1 settings
[Default]
15177 Monitoring 2 On Monitoring of the CAN messages

of device 1 is carried out
parameters.
15178 Address 2 0 to 255 s This device address is monitored.
[1 s]

device 1 within this delay time,
class is initiated.

any message from the device 1 is
received.

Notes



4 Configuration
[Default]

longer detected.

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
Tab. 76: J1939 Monitoring: Device 1
Device 2 settings
[Default]

parameters.
15184 Address 2 0-255 s This device address is monitored.
[1 s]

class is initiated.

received.


4 Configuration
[Default]
Notes



longer detected.

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
Device 3 settings
[Default]

parameters.
15190 Address 2 0 to 255 s This device address is monitored.
[1 s]

class is initiated.

4 Configuration
4.5.6.7 J1939 Interface - Red (Stop) Alarm
[Default]

received.

Notes



longer detected.

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
This monitor monitors, whether a specific alarm bit is received from the CAN J1939
interface. This enables to configure the easYgen in a way that a reaction is caused by this
bit (e.g. warning, shutdown).

4 Configuration
If this protective function is triggered, the display indicates "Red stop lamp" and the
[Default]
15115 Monitoring 2 On Monitoring of the Red Stop Lamp

message from the ECU is carried
parameters.
15119 Delay 2 0 to 999 s The red stop lamp delay is

[2 s]
If the ECU sends the Red Stop
Lamp On message, the action
initiated after the delay configured
here expires.

[A] specifies what action should be
Notes



longer detected.

output "External


engine monitoring".

4 Configuration
4.5.6.8 J1939 Interface - Amber Warning Alarm

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4.5.6.8 J1939 Interface - Amber Warning Alarm
General notes
If this protective function is triggered, the display indicates "Amber warning lamp" and
[Default]
15120 Monitoring 2 On Monitoring of the Amber Warning

Lamp message from the ECU is
15124 Delay 2 0 to 999 s The amber warning lamp delay is

[2 s]
If the ECU sends the Amber
Warning Lamp On message, the
is initiated after the delay
configured here expires.

[A] specifies what action should be
Notes




4 Configuration
4.5.6.9 J1939 Interface - Protect Alarm

longer detected.

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4.5.6.9 J1939 Interface - Protect Alarm
General notes
If this protective function is triggered, the display indicates "Protection lamp DM1" and
[Default]
1914 Monitoring 2 On Monitoring of the protection Lamp

message from the ECU is carried
parameters.
1915 Delay 2 0 to 999 s The protection lamp delay is

[2 s]
If the ECU sends the Protection
Lamp On message, the action
initiated after the delay configured
here expires.

4 Configuration
4.5.6.10 J1939 Interface - Emission/Malfunction Alarm
1916 Alarm class 2 Class A/B/C/D/E/F/Control An alarm can be assigned, that

[A] taken when the conditions are
fulfilled.
Notes



longer detected.

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
If this protective function is triggered, the display indicates "Emission lamp DM1" and the
[Default]

4 Configuration
1919 Monitoring 2 On Monitoring of the Emission

Warning Lamp message from the
ECU is carried out according to the
1920 Delay 2 0 to 999 s The Emission warning lamp delay

is configured with this parameter.
[2 s]
If the ECU sends the Emission
Warning Lamp On message, the
is initiated after the delay
configured here expires.
1921 Alarm class 2 Class A/B/C/D/E/F/Control An alarm can be assigned, that

[A] taken when the conditions are
fulfilled.
Notes



longer detected.

output "External


engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32

4 Configuration
4.5.6.11 J1939 Interface – DM1 Alarms
4.5.6.11 J1939 Interface – DM1 Alarms
This monitor is a switch to transfer the content of the DM1 alarm message onto the alarm
screen of the easYgen. The event log is as well considered.
[Default]
15156 Monitoring 2 Most of the J1939 devices release

a standardized DM1 message as
an error message on the CAN bus.
These messages can be entered
into the alarm list of the easYgen.
The alarm class is fixed to alarm
class A.
A J1939 device CAN monitor the

states of his inputs. When a error
occurs a DM1 message is
released.
[On] DM1 messages will be recorded in

the alarm list.
Off DM1 messages will be not

recorded in the alarm list.
Notes
Only known SPNs can be recorded

in the alarm list. These are J1939
Standard SPNs which also can be
visualized. Manufacturer specific
SPNs will be ignored.


longer detected.

output "External
4.5.6.12 Ethernet interfaces
General notes
The devices reacts on an abnormal rate of Ethernet UDP-messages per time scale e.g.
“broadcast storm”. If a maximal allowed number of messages is received, the device
closes all Ethernet ports to give the own device more calculation time. After about 100ms
the Ethernet ports are opened again to recheck the UDP message traffic. As long the
traffic is still high the device remains in this protection state.

4 Configuration
4.5.6.12 Ethernet interfaces
If this protective function is triggered, after the configured delay time the display
indicates the alarm “Ethernet issue” and the logical command variable “08.62 Ethernet
issue” will be enabled.
[Default]
3174 Monitoring 2 [On] Ethernet UDP message monitoring

is enabled.
3175 Delay 2 0.02 to 99.00 s If the issue contiunoes for the

[2.0 s] will be issued.

Notes



longer detected.

output "External


engine monitoring".

96.{xx} TRUE.

4 Configuration
4.5.6.13 Battery Overvoltage (Level 1 & 2)
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4.5.6.13 Battery Overvoltage (Level 1 & 2)
General notes
There are two battery overvoltage alarm levels available in the control. Both alarms are
definite time alarms and. Monitoring of the voltage is done in two steps.
If this protective function is triggered, the display indicates "Bat. overvoltage 1" or
"Bat. overvoltage 2" and the logical command variable "08.01" or "08.02" will be
enabled.
[Default]
3450 Monitoring 2 3450: [On] Overvoltage monitoring of the

battery voltage is carried out
3456 3456: [Off] according to the following
parameters. Both values may be
(Hysteresis: 0.1 V) configured independent from each
(Reset Delay: 1s) > Level 2).
Monitoring is disabled for Level 1

3454 Limit 2 8.0 to 42.0 V The threshold values that are to

be monitored are defined here.
3460 3454: [32.0 V]
If the monitored battery voltage
3460: [35.0 V] reaches or exceeds this value for
at least the delay time without
interruption, the action specified
3455 Delay 2 0.02 to 99.99 s If the monitored battery voltage

3461: [1.00 s]
Notes


4 Configuration
4.5.6.14 Battery Undervoltage (Level 1 & 2)
Notes



longer detected.

output "External

3459
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
General notes
There are two battery undervoltage alarm levels available in the control. Both alarms are
definite time alarms. Monitoring of the voltage is done in two steps.
If this protective function is triggered, the display indicates "Bat. undervoltage 1" or
"Bat. undervoltage 2" and the logical command variable "08.03" or "08.04" will be
enabled.
[Default]

4 Configuration
3500 Monitoring 2 [On] Undervoltage monitoring of the

battery voltage is carried out
parameters. Both values may be
configured independent from each
> Level 2).

3504 Limit 2 8.0 to 42.0 V The threshold values that are to

be monitored are defined here.
3510 3504: [24.0 V]
3510: [20.0 V] reaches or falls below this value
for at least the delay time without
(Hysteresis: 0.1 V) interruption, the action specified
(Reset Delay: 1s)
Notes
The default monitoring limit for

battery undervoltage is 24 Vdc
after 60 seconds.
This is because in normal

operation the terminal voltage is
approximately 26 Vdc (alternator
charged battery).
3505 Delay 2 0.02 to 99.99 s If the battery voltage falls below

3511 3505: [60.00 s] time configured here, an alarm
will be issued.
3511: [10.00 s]
Notes
If the battery voltage exceeds the

again before the delay expires the
time will be reset.
Notes



longer detected.

output "External

4 Configuration
4.5.6.15 Monitoring PV load reference


3509
engine monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
4.5.6.15 Monitoring PV load reference
General notes
The PV load reference function contains a monitor for generator reverse power. It is
enabled if parameter ╚═▷ 8911) is configured to ”Regulated“. The monitor observes the
system generator load and trips the alarm ”08.71 PV disconnect“ if the real generator
load underruns the configured disconnect level e.g. in case of reverse power. Then the PV
power can be cut. This can be maintained if the LogicsManager ”08.71 PV disconnect“ is
assigned to a relay output.
Parameter
Navigate to [Parameter / Configuration / Configure monitoring / Miscellaneous / Other

monitoring / PV load reference].
[Default]
8923 PV disconnect level 2 -20 to 20 % This is the system generator load

level on which the PV is
[-2 %] immediately to cut.
(Hysteresis is 0.5%.)
8924 Delay 2 0.1 to 999.0 s If the system generator load level

underruns the disconnect level for
[5 s] the delay time the alarm is
tripped.
(The delay off time is 0.08s.)


4 Configuration
4.5.6.16 Multi-Unit Parameter Alignment
Notes



longer detected.

output "External
General notes
The multi-unit parameter alignment functionality requires that the relevant parameters
are all configured identically at all participating units.
If at least one of these parameters is configured different in at least one of the units, the
display indicates "Parameter alignment" on all units and the logical command variable
"08.16" will be enabled. To identify different configured units, please use the diagnostic
screen "Genset parameter alignment": [Next Page / Status Menu / System Overview /
Multi-unit / Genset parameter alignment]
This alarm is always self-acknowledging, i.e. the control automatically clears the alarm if
it is no longer valid.
The setting of the following parameters will be monitored:
Parameter ID
Start stop mode ╚═▷ 5752
Dead busbar start mode ╚═▷ 5753
Fit size of engine ╚═▷ 5754
Fit service hours ╚═▷ 5755
Changes of engines ╚═▷ 5756
IOP Reserve power 1 ╚═▷ 5760
IOP Hysteresis ╚═▷ 5761
IOP Max. generator load ╚═▷ 5762
IOP Min. generator load ╚═▷ 5763
IOP Dynamic ╚═▷ 5757
IOP Add on delay ╚═▷ 5764
IOP Add on delay at rated load ╚═▷ 5765

4 Configuration
Parameter ID
IOP Add off delay ╚═▷ 5766
MOP Minimum load ╚═▷ 5767
MOP Reserve power ╚═▷ 5768
MOP Hysteresis ╚═▷ 5769
MOP Max. generator load ╚═▷ 5770
MOP Min. generator load ╚═▷ 5771
MOP Dynamic ╚═▷ 5758
MOP Add on delay ╚═▷ 5772
MOP Add on delay at rated load ╚═▷ 5773
MOP Add off delay ╚═▷ 5774
LDSS sort priority always ╚═▷ 5777
Transfer rate LS fast message ╚═▷ 9921
Tab. 79: Multi-unit parameter alignment - monitored parameters
[Default]
4070 Monitoring 2 [On] Multi-unit parameter alignment

monitoring is carried out.
4071 Alarm class 2 Alarm class Class A/B/C/D/E/F, This function may be assigned an
Control independent alarm class that
[B] taken when this function triggers
an alarm.
Notes

4076 Delay 2 Yes The control automatically clears

no longer detected.

output "External
4078 Enabled 2 87.70 LM:Eng.mon Monitoring for fault conditions is

monitoring is enabled.

4 Configuration
4.5.6.17 Multi-Unit Missing easYgen
This is determined through the

engine monitoring". For xx = 1 to
32: 96.{xx} LM: Flag{xx}
The monitoring is executed, if the

TRUE.
Example: 96.01 LM: Flag1, 96.02

LM: Flag2, ..., 96.32 LM: Flag32
[Always] Monitoring for this fault condition

4077 Self acknowledge 2 0.02 to 999.99 s Parameter alignment monitoring

delay
3.00
If a parameter alignment error
occurs, the alarm will be delayed
by a basic delay time (depending
on the communication method)
plus the delay time defined here.
4.5.6.17 Multi-Unit Missing easYgen
General notes
The multi-unit missing easYgen monitoring function checks whether all participating units
are available (sending data on the load share line).
If the number of available units is less than the number of displayed "Monitored easYgen"
╚═▷ 9925 (initiated by parameter ╚═▷ 13356 System update) for at least the delay time,
the display indicates "Missing easYgen" and the logical command variables "08.17" and
"08.27" will be enabled.
After energizing the easYgen, a delay is started, which allows a possible "Missing
easYgen" alarm to become active.
For using only a CAN bus connection, this delay depends on the Node-ID of the easYgen
(parameter ╚═▷ 8950) and the transfer rate of a load share fast message (parameter ╚═▷
9921) and may last for approx. 140 seconds for a high Node-ID (e.g. 127). This delay
serves for detecting the Master of the CAN bus* connection. Approximately two minutes
after energizing the easYgen, the alarm delay will be set to a fix time, which depends on
the setting of parameter ╚═▷ 9921 (Transfer rate LS fast message) and is in the range
between 3 to 12 seconds.
For Ethernet connections, this delay time is 12 seconds. Approximately 12 seconds after
energizing the easYgen, the alarm delay will be set to 1 second.
During »System update« the alarm is disabled.
For more information see ╚═▷ “6.2.2 Communication Management”
[Default]

4 Configuration
4.5.6.18 Multi-Unit System Update
4060 Monitoring 2 On Multi-unit missing members

monitoring is carried out.
4061 Alarm class 2 Class A/B/C/D/E/F, Control This function may be assigned an
taken when this function triggers
an alarm.
Notes


no longer detected.

output "External
4.5.6.18 Multi-Unit System Update
General notes
The multi-unit system update monitoring function checks whether only the participating
units are available (sending data on the load share line).
If the number of available easYgen units is more than the number of displayed "Monitored
easYgen" ╚═▷ 9925 (initiated by parameter ╚═▷ 13356 System update), the display
indicates "System Update easYgen" and the logical command variables "08.43" and
"08.65" will be enabled.
For more information see ╚═▷ “6.2.2 Communication Management”
[Default]
7832 Monitoring 2 [On] Enabling to monitor the system if

there are more devices against
latest updated system
configuration.
Notes
To detect less easYgen devices

against latest updated system
configuration use missing member
monitor ╚═▷ 4060.

4 Configuration
4.5.6.19 Operating Range Failure
[Default]
Notes

7834 Self acknowledge -/- Yes The control unit automatically


longer detected.

output "External
Tab. 80: Parameter setting: Monitoring system update
General notes
The operating range failure monitoring issues an Operating Range Failure Alarm
"Oper.range failed XX" (where XX is the number of Check 01 to 12) if one of the following
conditions is fulfilled. Example: Check 4 failed causes »Oper.range failed 4«.
Only the first incoming operation range failure will tripp an alarm. Because in most cases
this will be the root cause for eventually incoming further operating range alarms. Any
other operating range alarm can only be tripped if there is no active or latched operating
range alarm.
If there are more than one failures only the first incoming failure will be indicated and is
available at protocol 5014.
If there is no alarm this number is 0.
• Check 1: The easYgen tries to close the GCB, but the generator is not within its
operating range (parameters ╚═▷ 5800, ╚═▷ 5801, ╚═▷ 5802, or ╚═▷ 5803).
• Check 2: The easYgen tries to synchronize the GCB, but the busbar is not within the
generator operating range (parameters ╚═▷ 5800, ╚═▷ 5801, ╚═▷ 5802, or ╚═▷
5803).
• Check 3: The easYgen tries close the GCB in breaker transition mode "Open
transition" with GCB and MCB open status. In this condition the busbar is expected

4 Configuration
as dead, but the busbar voltage is NOT below the dead busbar detection limit
• Check 4: The easYgen wants to close the GCB onto a dead busbar, but the device
cannot close the breaker because there is at least one neighbor device recognized
with a closed GCB.
• Check 5: The easYgen tries to synchronize the GCB, the MCB is closed, but mains
and/or bussbar are not within its operating range (parameters ╚═▷ 5810, ╚═▷ 5811,
╚═▷ 5812, or ╚═▷ 5813).
• (Checks 6 to 10 are intentionally NOT available in easYgen-3100XT/3200XT.)
• Check 11: The easYgen checks the plausibility of generator and busbar, if GCB is
closed and the engine runs without run-up synchronization, but the operating range
of generator OR busbar is not matched.
• Check 12: The easYgen checks the phase rotation of generator, busbar, and mains
and a synchronisation shall be executed, but the phase rotation of all systems does
not match. (Synchronisation is blocked.)
No alarm will be issued in idle mode. This monitoring function is disabled below firing
speed.
NOTICE!

will be started.
If this protective function is triggered, the display indicates "Operat. range failed" /
("Operating Range failed") and the logical command variable "06.31" will be enabled.
[Default]
2660 Monitoring 2 [On] Monitoring of the operating range

2663 Delay 2 1 to 999 s If one of the above mentioned

conditions for an operating range
[30 s] failure is fulfilled, an alarm will be
issued. If the respective condition
is not fulfilled anymore before the
will be reset.
Notes


4 Configuration
4.5.6.20 Load Share Interface Redundancy is Lost
[Default]


longer detected.

output "External
Tab. 81: Operating Range Failure settings
4.5.6.20 Load Share Interface Redundancy is Lost
General
Beside the automatic handling of redundant load share line messages the easYgen can
inform the operator if a redundant load share communication line get lost. Preassumption
for that is an enabled redundant load share line like CAN/Ethernet A in conjunction with a
successful system update procedure.
If the according alarm has occurred the operator usually checks the "Diagnostic devices"
screen. Available on device display or over ToolKit. There he will be informed which
channel is affected. Refer to system update for more information.
Function
If the parameter "9924 Load share interface" is configured to "CAN/Ethernet A" and the
system update was executed, the monitoring becomes active. The monitor needs
minimum
The devices observes if the both load share messages are correctly receipt. If a channel
fails the alarm "LS interf. redundancy" is triggered.
[Default]
5017 Monitoring 2 The monitoring of the load share

communication line redundancy
can be enabled here.
On On: Monitoring is enabled
[Off] Off: Monitoring is disabled
5018 Alarm Class 2 A/B/C/D/E/F, Control Each limit may be assigned an

[Class B] specifies what action should be

4 Configuration
4.6 Configure Measurement
[Default]
5019 Delay 2 0.2 to 999.9s The redundancy lost error can be

delayed according to the
[3.0s] application.
5020 Self Acknowledge 2 No No: The control unit does not

longer detected.
[Yes] Yes: The control unit automatically

5021 Enabled 2 [Always] Always: Monitoring for this fault

condition is continuously enabled.
87.70 87.70 LM:Eng.mon: Monitoring for

fault conditions is not performed
LM:Eng.mon until engine monitoring is
enabled. This is determined
through the LogicsManager
equation "Release engine
monitoring".

96.{xx} TRUE.
96.01 LM: Flag1, 96.02 LM:

Flag2, ..., 96.32 LM: Flag32
Tab. 82: Parameter: Monitoring
4.6 Configure Measurement

General notes
If the genset control is intended to operate a genset in parallel to the mains, the mains
voltage measuring inputs must be connected.

4 Configuration
4.6.1 General measurement settings
Dependencies
S
Q
PF=cosφ
1 φ
Fig. 193: AC power triangle
PF Power Factor
P Active Power [kW]
S Apparent power [kVA]
Q Reactive Power [kvar]
The AC power triangle illustrates the dependencies between active power, apparent
power, reactive power and power factor.
• PF = P/S = cos Φ
• Q = √(S2-P2)
• S = √(P2+Q2)
• P = S * PF
[Default]
1750 System rated 2 50 / 60 Hz The rated frequency of the system

frequency is used as a reference figure for all
[50 Hz] frequency related functions, which
use a percentage value, like
frequency monitoring, breaker
operation windows or the
AnalogManager.
1825 System rated active 2 0.5 to 99999.9 This value specifies 100% of the
power [kW] system rated power, which is used
[200.0 kW] for system related indications and
calculations.
The AnalogManager 10.11

"System active nominal power"
and 10.12 "System total real
power" are related to this value or
setting.

4 Configuration
1858 1Ph2W voltage 3 [Phase - phase] The unit is configured for

measuring measuring phase-phase voltages
if 1Ph 2W measuring is selected.
Phase - neutral The unit is configured for

measuring phase-neutral voltages
if 1Ph 2W measuring is selected.
Notes
For information on measuring

principles refer to ╚═▷ “3.3.5.1
Generator Voltage”.
Never configure the busbar

measurement for phase-neutral, if
the other systems like mains and
generator are configured as 3Ph
3W or 3Ph 4W. The phase angle
for synchronization would be not
correct.
1859 1Ph2W phase 3 [CW] A clockwise rotation field is

rotation considered for 1Ph 2W
measuring .
CCW A counter-clockwise rotation field

is considered for 1Ph 2W
measuring.
Notes

1854 Additional CT input 2 [Mains current] / Ground This parameter configures

current / Off whether ground or mains current
is measured on terminals ½ or the
input is disabled.
1835 Ground current range 2 1A Application specific ground current

range must be selected e.g. for
[5A] rated values.
1810 Gnd. CT primary 2 [500 A/x] CT ground current measuring

rated current primary rated value.
1..3200 A/x
Notes
Available if parameter »1854

Additional CT input «is set
to »Ground current«.
»A/x«: "/x" shows the relation to

the current range which can be
selected (1 A or 5 A).

4 Configuration
4.6.2 Generator
4.6.2 Generator
[Default]
235 Generator type 2 The genset control supports two

types of generators:
• synchronous generators
• asynchronous generators
(induction generators)
[Synchronous] The unit provides all functions

which are needed for synchronous
generator applications. islanded
and mains parallel operation is
supported.
Asynchronous The unit provides the special

function of the asynchronous
generator with:
• The speed is regulated with

the speed signal from the
MPU or J1939/CAN input (as
long as the GCB is open).
• The closing of the GCB is
executed, if the speed is
within the corresponding
frequency range of the
generator operating window.
The voltage and phase angle
is ignored in this case.
• The generator monitoring
(under/over frequency and
under/overvoltage/
asymmetry) is switched off,
until the generator breaker is
closed.
• After opening the GCB,
under/over frequency and
under/overvoltage and
asymmetry monitoring is
switched on again.
• The Frequency/MPU speed
plausibility monitoring is only
active, if the GCB is closed.
• The synchroscope is not
displayed in the
asynchronous modus.
Notes
The asynchronous mode is used in

slip synchronization only
(Synchronization GCB (parameter
╚═▷ 5729) = Slip frequency.
Recommended settings
The asynchronous modus is

normally used in mains parallel
operation. Please consider the
following settings:
• Application mode (parameter

╚═▷ 3444) = GCB

4 Configuration
4.6.2 Generator
• Mains decoupling (parameter

╚═▷ 3110) = GCB
• MPU input (parameter ╚═▷
1600) = On
• Generator operating
frequency (parameter ╚═▷
5802, ╚═▷ 5803)
Notes
The asynchron mode is not

recommended for emergency
power applications.
1766 Generator rated 2 50 to 650000 V This value refers to the rated

voltage voltage of the generator
[400 V] (generator voltage on data plate)
and is the voltage measured on
the potential transformer primary.
The generator rated voltage is

used as a reference figure for all
generator voltage related
functions, which use a percentage
value, like generator voltage
monitoring, breaker operation
windows or the AnalogManager.
1752 Gen. rated active 2 0.5 to 99999.9 kW This value specifies the generator
power [kW] real power rating, which is used as
[200.0 kW] a reference figure for related
functions. The generator rated
active power is the generator
apparent power multiplied by the
generator power factor (typically
~0.8). These values are indicated
in the generator data plate (╚═▷
“Dependencies”).
1758 Gen. rated react. 2 0.5 to 99999.9 kvar This value specifies the generator
power [kvar] reactive power rating, which is
[200.0 kvar] used as a reference figure for
related functions. The generator
rated reactive power also depends
on the generator values (╚═▷
“Dependencies”).
1754 Generator rated 2 1 to 32000 A This value specifies the generator

current rated current, which is used as a
[300 A] reference figure for related
functions.
1851 Generator voltage 2 3Ph 4W OD Measurement is performed Line-

measuring Neutral (Open Delta connected
system). The voltage is connected
via transformer with 3 Wire.
Phase voltages and the neutral

must be connected for proper
calculation.
Measurement, display and

protection are adjusted according
to the rules for Open Delta
connected systems.

4 Configuration
4.6.2 Generator
Monitoring refers to the following

voltages:
• VL12, VL23 and VL31
1Ph 3W Measurement is performed Line-

Neutral (WYE connected system)
and Line-Line (Delta connected
system). The protection depends
on the setting of parameter ╚═▷
1770.
Measurement, display, and

to the rules for single-phase
systems.

voltages:
• VL13 (parameter ╚═▷ 1770

configured to "Phase-phase")
• VL1N, VL3N (parameter ╚═▷
1770 configured to "Phase-
neutral")

Neutral (WYE connected system) if
parameter ╚═▷ 1858 is configured
to "Phase - neutral" and Line-Line
(Delta connected system) if
to "Phase - phase".

to the rules for phase-phase
systems.

voltages:
• VL1N, VL12

Line (Delta connected system).
Phase voltages must be
connected for proper calculation.

to the rules for Delta connected
systems.

voltages:
• VL12, VL23, VL31
[3Ph 4W] Measurement is performed Line-

1770.

calculation. Measurement, display
and protection are adjusted
according to the rules for WYE
connected systems.

4 Configuration
4.6.2.1 Configure transformer

voltages:

(parameter ╚═▷ 1770
• VL1N, VL2N and VL3N
configured to "Phase-
neutral")
Notes

1Ph 3W, the generator and mains
rated voltages (parameters ╚═▷
1766 and ╚═▷ 1768) must be
entered as Line-Line (Delta) and
the busbar 1 rated voltage
entered as Line-Neutral (WYE).

1850 Generator current 2 [L1 L2 L3 ] All three phases are monitored.

measuring Measurement, display and
to the rules for 3-phase
measurement. Monitoring refers
to the following currents: IL1, IL2,
IL3
Phase L{1/2/3} Only one phase is monitored.

measurement.
Monitoring refers to the selected

phase.
Notes

generator voltage measuring
3W".

Generator Current”.
General notes
The setpoints for specific parameters will differ depending upon the setting of
parameter »Generator current range«╚═▷ 1830.
• 1830 = "1A": Current transformer with ../1 A rated current

4 Configuration
[Default]
1801 Gen. PT primary 2 50 to 650000 V Some generator applications may

rated voltage require the use of potential
[400 V] transformers to facilitate
(Generator potential measuring the voltages produced
transformer primary by the generator. The rating of the
voltage rating) primary side of the potential
transformer must be entered into
this parameter.
If the application does not require

potential transformers (i.e. the
measured voltage is 480 V or
less), then the measured voltage
will be entered into this
parameter.
1800 Gen. PT secondary 2 50 to 480 V Some generator applications may

rated volt. require the use of potential
[400 V] transformers to facilitate
(Generator potential measuring the voltages produced
transformer secondary by the generator. The rating of the
voltage rating ) secondary side of the potential
transformer must be entered into
this parameter.

parameter.
1806 Gen. CT primary 2 1 to 32000 A/x The input of the current

rated current transformer ratio is necessary for
[500 A/x] the indication and control of the
(Generator current actual monitored value.
transformer primary
rating) Notes
The current transformers ratio

should be selected so that at least
60% of the secondary current
rating can be measured when the
monitored system is at 100% of
operating capacity (i.e. at 100% of
system capacity a 5 A CT should
output 3 A).
If the current transformers are

sized so that the percentage of
the output is lower, the loss of
resolution may cause inaccuracies
in the monitoring and control
functions and affect the
functionality of the control.
»A/x«: "/x" shows the relation to

the current range which can be
selected (1 A or 5 A).
1830 Generator current 2 1A The input range of the current

range transformer must be selected/
defined.

4 Configuration
4.6.3 Busbar
[5 A]
4.6.3 Busbar
The busbar parameters in the device are often named with the affix "1". This preparation
is done to avoid confusion e.g., if a model with a second busbar measurement is
introduced.
[Default]
1781 Busbar 1 rated 2 50 to 650000 V This value refers to the rated

voltage voltage of busbar 1 and is the
[400 V] voltage measured on the potential
transformer primary.
If voltage measuring is configured

to 1Ph 3W, the WYE voltage
(VL1N) must be entered here.
The busbar 1 potential

transformer primary voltage is
entered in this parameter. The
busbar rated voltage is used as a
reference figure for all busbar
voltage related functions, which
use a percentage value, like
synchronization.
5820 Dead bus detection 2 0 to 30% If the busbar voltage falls below
max. volt. this percentage of the busbar 1
[10%] rated voltage (parameter ╚═▷
1781), a dead bus condition is
detected and the logical command
variable 02.21 (Busbar 1 is dead)
becomes TRUE.
[Default]
1813 Busb1 PT primary 2 50 to 650000 V Some applications may require

rated voltage the use of potential transformers
[400 V] to facilitate measuring the
(Busbar 1 potential voltages to be monitored. The
transformer primary rating of the primary side of the
voltage rating ) potential transformer must be
entered into this parameter.
Notes


4 Configuration
4.6.4 Mains

parameter.
1812 Busb1 PT secondary 2 50 to 480 V Some applications may require

rated volt. the use of potential transformers
[400 V] to facilitate measuring the busbar
(Busbar 1 potential voltages. The rating of the
transformer secondary secondary side of the potential
voltage rating ) transformer must be entered into
this parameter.

parameter.
4.6.4 Mains
[Default]
1768 Mains rated voltage 2 50 to 650000 V This value refers to the rated
voltage of the mains and is the
[400 V] voltage measured on the potential
transformer primary.
The mains potential transformer

primary voltage is entered in this
parameter. The mains rated
voltage is used as a reference
figure for all mains voltage related
functions, which use a percentage
value, like mains voltage
monitoring, breaker operation
windows or the AnalogManager.
1748 Mains rated active 2 0.5 to 99999.9 kW This value specifies the mains real
power [kW] power rating, which is used as a
[200.0 kW] reference figure for related
functions. The mains rated active
power is a reference value used
by several monitoring and control
functions (╚═▷ “Dependencies”).
1746 Mains rated react. 2 0.5 to 99999.9 kvar This value specifies the mains
pwr. [kvar] reactive power rating, which is
[200.0 kvar] used as a reference figure for
related functions.
The mains rated reactive power is

a reference value used by several
monitoring and control
functions(╚═▷ “Dependencies”).
1785 Mains rated current 2 1 to 32000 A This value specifies the mains
rated current, which is used as a

4 Configuration
4.6.4 Mains
[300 A] reference figure for related

functions.
1853 Mains voltage 2 [3Ph 4W] Measurement is performed Line-

measuring Neutral (WYE connected system)
1771.

calculation. Measurement, display
and protection are adjusted
according to the rules for WYE
connected systems.

voltages:

• VL1N, VL2N and VL3N
configured to "Phase-
neutral")
• VL12, VL23, VL31, VL1N,
VL2N and VL3N (parameter
╚═▷ 1771 configured to "All")

Line (Delta connected system).
Phase voltages must be
connected for proper calculation.

to the rules for Delta connected
systems.

voltages:
• VL12, VL23, VL31

Neutral (WYE connected system) if
to "Phase - neutral" and Line-Line
(Delta connected system) if
to "Phase - phase".

to the rules for phase-phase
systems.

voltages:
• VL1N, VL12

system).
The protection depends on the

Measurement, display, and

4 Configuration

systems.

voltages:
• VL13 (parameter ╚═▷ 1771

1771 configured to "Phase-
neutral")
1771 configured to "All")
Notes

1Ph 3W, the generator and mains
rated voltages (parameters ╚═▷
1766 and ╚═▷ 1768) must be
entered as Line-Line (Delta) and
the busbar 1 rated voltage
entered as Line-Neutral (WYE).
1852 Mains current 2 [Phase L1] / Phase L2 / Phase L3 Phase L{1/2/3} Measurement is
measuring performed for the selected phase
only. The measurement and
display refer to the selected
phase.
The configured phase CT must be

connected to perform current
measurement.
Notes

Mains Current”.

mains voltage measuring
3W".
General notes
The setpoints for specific parameters will differ depending upon the setting of
parameter »Mains current range«╚═▷ 1832.
[Default]
1804 Mains PT primary 2 50 to 650000 V Some applications may require

rated voltage the use of potential transformers
to facilitate measuring the

4 Configuration
(Mains potential [400 V] voltages to be monitored. The

transformer primary rating of the primary side of the
voltage rating potential transformer must be
entered into this parameter.
Notes

parameter.
1803 Mains PT secondary 2 50 to 480 V Some applications may require

rated volt. the use of potential transformers
[400 V] to facilitate measuring the mains
(Mains potential voltages. The rating of the
transformer secondary secondary side of the potential
voltage rating) transformer must be entered into
this parameter.

parameter.
1807 Mains CT primary 2 1 to 32000 A/x The input of the current

rated current transformer ratio is necessary for
[500 A/x] the indication and control of the
(Mains current actual monitored value.
transformer primary
rating) The current transformers ratio
should be selected so that at least
60% of the secondary current
rating can be measured when the
monitored system is at 100% of
operating capacity (i.e. at 100% of
system capacity a 5 A CT should
output 3 A).
If the current transformers are

sized so that the percentage of
the output is lower, the loss of
resolution may cause inaccuracies
in the monitoring and control
functions and affect the
functionality of the control.
Notes
This screen is only visible if

as Mains.
1832 Mains current range 2 1A The input range of the current

transformer must be selected/
[5 A] defined.
Notes
This screen is only visible if

as Mains.

4 Configuration
4.6.4.2 External Mains Active Power
4.6.4.2 External Mains Active Power
[Default]
2966 External mains active 2 Yes The mains active power is coming
power from an external source.
The following measurement

values of the external mains
active power depend on the
external mains reactive power
measurement. So there is to
differentiate between two cases:
Case 1: External mains reactive

power measurement (parameter
╚═▷ 2969) is disabled:
• The mains power factor is

assumed as "1".
• The mains power factor
monitoring is switched off.
• The mains power factor is not
displayed.
• The mains total reactive
power is not displayed.
Case 2: External mains reactive

╚═▷ 2969) is enabled:

calculated.
displayed.
• The mains total apparent
power is calculated and
displayed.
Notes
Mains power monitoring is not

available.
Please make sure to assign the

external mains active power to
the corresponding analog data
source (parameter ╚═▷ 5780). The
same data source must be used if
the mains active power is
requested via interface.
[No] The mains active power is

internally measured.
5780 AM Ext.mains act.pwr 2 Determined by AnalogManager Typically an analog input is

selected as data source which is
81.19: [A1 = 06.01 Analog connected to an external
input 1] transducer.

4 Configuration
4.6.4.3 External Mains Reactive Power
2967 Mains power meas. 2 This parameter controls the

resolution resolution and the format.
(Mains power Selected resolution Power at 100 % analog value

measurement
resolution) 0.01 kW 10.00 kW
0.1 kW 100.0 kW
[1 kW] 1000 kW
0.01 MW 10.00 MW
0.1 MW 100.0 MW
4.6.4.3 External Mains Reactive Power
[Default]
2969 External mains 2 Yes The mains reactive power is

reactive power coming from an external source.
This power is displayed and used
for control purposes. The source is
taken via AnalogManager.
The following measurement

values depend on the external
mains active power measurement.
So there is to differentiate
between two cases:
Case 2: External mains active

╚═▷ 2966) is disabled:

assumed as "1".
• The mains active power
displayed.
• The mains total active power
is not displayed.
Case 1: External mains active

2966) is enabled:

calculated.
displayed.
• The mains total apparent
power is calculated and
displayed.
Notes

4 Configuration
4.6.5 Engine
Mains power monitoring is not

available.
Please make sure to assign the

external mains reactive power to
the corresponding analog data
source (parameter ╚═▷ 5794). The
same data source must be used if
the mains active power is
requested via interface.
[No] The mains reactive power is

internally measured.
5794 AM Ext.mains RPower 2 Determined by AnalogManager Typically an analog input is

selected as data source (kvar
81.20: [A1 = 06.02 Analog value) which is connected to an
input 2] external transducer.
2970 Mains react. power 2 This parameter controls the

meas. resolution resolution and the format.
(Mains reactive power Selected resolution: Power at 100 % analog value:

measurement
resolution) 0.01 kvar 10.00 kvar
0.1 kW 100.0 kvar
[1 kvar] 1000 kvar
0.01 Mvar 10.00 Mvar
0.1 Mvar 100.0 Mvar
4.6.5 Engine
[Default]
1601 Engine rated speed 2 100 to 4,000 rpm Number of revolutions per minute
of the engine at rated engine
[1,500 rpm] speed. The speed control with an
ECU via J1939 CAN bus refers to
this value.

4 Configuration
4.7 Configure Interfaces
4.7 Configure Interfaces

Interfaces / Communication easYgen-3400XT/3500XT-P1
Fig. 194: easYgen-3400XT/3500XT-P1 communication interfaces
4.7.1 USB (Service Port) Interface
There is no configuration to do for the USB Service Port but the driver installer .exe from
CD-ROM must be proceeded: [Software / USB driver / Click here]

4 Configuration
USB Service Port
The USB service port is restricted for ToolKit communication, Woodward service
communication, and - if provided by factory side - read only files.
The »Automatic Reconnection« over USB is not possible.
If connection over USB is lost, please reconnect manually:
• 1. Wait until the easYgen-XT is recognized again through the PC (as an external hard
drive)
• 2. Start via ToolKit at new by "Disconnect" and then "Connect" again
[Default]
3170 Baudrate 2 2.4 / 4.8 / 9.6 / [19.2] / 38.4 / 56 / This parameter defines the baud
115 kBaud rate for communications. Please
note, that all participants on the
bus must use the same baud rate.
3171 Parity 2 [No] / Even / Odd The used parity of the interface is
set here.
3172 Stop bits 2 [One] / Two The number of stop bits is set
here.
3173 Full-, half-duplex 2 [Fullduplex] Fullduplex mode is enabled.

mode
Half-duplex Half-duplex mode is enabled.
Modbus Interface
3188 ModBus Slave ID 2 0 to 255 The Modbus device address, which

is used to identify the device via
[1] Modbus, is entered here.
If "0" is configured here, the

Modbus is disabled.
3189 Reply delay time 2 0.00 to 2.55 s This is the minimum delay time
between a request from the
[0.00 s] Modbus master and the sent
response of the slave. This time is
required in half-duplex mode.
9128 Password protection 5 Off Password protection for Modbus

RS 485 is not active.
Notes
Take care for a protected access!
[On] Password protection for Modbus

RS 485 is active.

4 Configuration
4.7.3 Modbus Protocol
[Default]
3184 Modbus protocol 2 0 to 65535 A Modbus protocol may be

number selected by entering the data
protocol ID here. If an unknown
data protocol ID is configured
here, nothing will be transmitted.
Possible data protocol IDs
(existing protocols) are listed in
this Technical Manual.
Instead of a Woodward protocol, a

customer specific data protocol
can be selected. Such a protocol
must have been uploaded onto
the device and its file name must
fit the reserved range from
protocol number 65100 to 65199.
Use Woodward "TelegramMapper"
PC software to create your own
Data Telegrams (refer to ╚═▷
“6.5.4 Modbus Telegram Mapper
(Customer Written Data
Protocols)”).
Notes
Another protocol can be used after

a reboot of the control:
Change Modbus protocol number

first, then reboot ╚═▷ 10419!
[5010] Number of the Data Telegram to

be used for communication
(corresponds to the file name
[xxxx].scp).
Notes
All Date Telegrams described in

this Technical Manual are device
implemented: no separate scp-file
(e.g. "5010.scp") needed.
3179 Detect a gap in a 2 [On] If a received Modbus command

Modbus frame has a gap between its byte of
more than 5 ms, this command is
ignored.
Off The Modbus message is not

checked.
3181 Power [W] exponent 2 2 to 5 This setting adjusts the format of

10^x the 16 bit power values in the
[3] data telegram.
Notes
Valid for data telegram 5010 only!

4 Configuration
Refer to ╚═▷ “Power measurement

example” for examples.
3182 Voltage [V] exponent 2 -1 to 2 This setting adjusts the format of

10^x the 16 bit voltage values in the
[0] data telegram.
Notes
Refer to ╚═▷ “Voltage

measurement example” for
examples.
3183 Current [A] exponent 2 -1 to 0 This setting adjusts the format of

10^x the 16 bit current values in the
[0] data telegram.
Notes
Refer to ╚═▷ “Power measurement

example” for examples.
3219 Modbus master 2 [0ff] The Modbus master function is

disabled and no Modbus master
requests are sent.
[0n] The Modbus master function is

requesting data according to the
control file.
Note
Take care that a modbus master

control file is already load into the
device. For details refer to
chapter╚═▷ “6.5.5 Modbus
master”).

4 Configuration
Power measurement example
☼ How to use Power exponent 3181
Power measurement:
• The measurement range is 0…250 kW

• Momentary measurement value = 198.5 kW (198.500 W)
Setting Possible
Transfer value
value Meaning Calculation display
(16 Bit, max. 32767) format
3181
2 102 198500 W / 102 W 1985 198.5 kW
3 103 198500 W / 103 W 198 198 kW
4 104 198500 W / 104 W 19 N/A
5 105 198500 W / 105 W 1 N/A
Tab. 83: Power measurement example
Voltage measurement example
☼ How to use Voltage exponent 3182
Voltage measurement:
• The measurement range is 0…480 V

• Momentary measurement value = 477.8 V
Transfer value Possible

Setting Meaning Calculation display
-1 10-1 477.8 V / 10-1 W 4778 477.8 V
0 100 477.8 V / 100 V 477 477 V
1 101 477.8 V / 101 V 47 N/A
2 102 477.8 V / 102 V 4 N/A
Tab. 84: Voltage measurement example

4 Configuration
4.7.4 CAN Interfaces
Current measurement example
☼ How to use Current exponent 3183
Current measurement:
• The measurement range is 0…500 A

• Momentary measurement value = 345.4 A
Transfer value Possible

Setting Meaning Calculation display
-1 10-1 345.4 A / 10-1 A 3454 345.4 A
0 100 345.4 A / 100 A 345 345 A
Tab. 85: Current measurement example
4.7.4 CAN Interfaces
General notes
The CAN bus is a field bus and subject to various disturbances. Therefore, it cannot be
guaranteed that every request will be answered. We recommend to repeat a request,
which is not answered within reasonable time.
COB-ID of SYNC/TIME messages
Parameters ╚═▷ 9100 and ╚═▷ 9101 use synchronization and time messages that adhere
to the following structure.
Bit number Value Meaning
31 (MSB) 0 Unit does not apply TIME message
1 Unit applies TIME message
30 0 Unit does not generate SYNC/TIME message
1 Unit generates SYNC/TIME message
29 X N/A
28-11 0 Always
10-0 (LSB) X Bits 10-0 of SYNC/TIME COB-ID
TIME synchronization message
CANopen master COB-ID TIME Time applied Time transmitted
Off Bit 30 = 0; Bit 31 = 0 No No

4 Configuration
CANopen master COB-ID TIME Time applied Time transmitted
Bit 30 = 1; Bit 31 = 0 Yes No
Bit 30 = 0; Bit 31 = 1 Yes No
Bit 30 = 1; Bit 31 = 1 Yes Yes
Default Bit 30 = 0; Bit 31 = 0 No No
Bit 30 = 1; Bit 31 = 0 No Yes
Bit 30 = 0; Bit 31 = 1 Yes No1
Bit 30 = 1; Bit 31 = 1 Yes Yes1
On Bit 30 = 0; Bit 31 = 0 No No
Bit 30 = 1; Bit 31 = 0 No Yes
Bit 30 = 0; Bit 31 = 1 Yes No
Bit 30 = 1; Bit 31 = 1 Yes Yes
1 If CANopen master (lowest Node-ID).
[Default]
3156 Baudrate 2 20 / 50 / 100 / 125 / 250 / 500 / This parameter defines the used
800 / 1000 kBaud baud rate. Please note, that all
participants on the CAN bus must
[250 kBd] use the same baud rate.
1894 Align device no. with 2 No If this parameter is configured to

Node-ID "Yes" the parameter »Node-ID
[Yes] CAN bus 1« ╚═▷ 8950 will be
overwritten with the value of
the »Device number «╚═▷ 1702
and is not visible.
If configured to "No",
parameter »Device number
« 1702 is visible and will not be
overwritten.
Notes
This is to avoid CAN ID conflict in

multi unit systems if using the
same ID more than one time. This
can cause CAN "Bus-Off" failure.
8950 Node-ID CAN bus 1 2 1 to 127 (dec) A number that is unique to the
control must be set in this
[1] parameter so that this control unit
can be correctly identified on the
CAN bus.
This address number may only be

used once on the CAN bus. All

4 Configuration
additional addresses are

calculated based on this unique
device number.
Notes
We recommend to configure the

Node-IDs for units, which
participate in load sharing, as low
as possible to facilitate
establishing of communication.
8993 CANopen Master 2 One bus participant must take

over the network management
and put the other participants into
"operational" mode. The easYgen
is able to perform this task.
[Default Master] The unit starts up in "operational"

mode and sends a
"Start_Remote_node" message
after a short delay (the delay is
the Node-ID (parameter ╚═▷
8950) in seconds, i.e. if the Node-
ID is configured to 2, the message
will be sent after 2 seconds). If
more than one easYgen is
configured to Default Master, the
unit with the lower Node-ID will
take over control. Therefore, the
CAN bus devices, which are
intended to act as Default Master
should be assigned a low Node-ID.
No other device on the CAN bus
(except the easYgens) may
operate as Master).
On The unit is the CANopen Master

and automatically changes into
operational mode and transmits
data.
Off The unit is a CANopen Slave. An

external Master must change into
operational mode.
Notes

"Off", the Master controller (for
example a PLC) must send a
"Start_Remote_node" message to
initiate the load share message
transmission of the easYgen.
If no "Start_Remote_node"
message would be sent, the
complete system would not be
operational.
9120 Producer heartbeat 2 0 to 65500 ms Independent from the CANopen

time Master configuration, the unit
[2000 ms] transmits a heartbeat message
with this configured heartbeat
cycle time.
If the producer heartbeat time is

equal 0, the heartbeat will only be
sent as response to a remote
frame request. The time

4 Configuration
configured here will be rounded

up to the next 20 ms step.
9100 COB-ID SYNC 2 1 to FFFFFFFF hex This parameter defines whether

Message the unit generates the SYNC
[80 hex] message or not.
The message complies with

CANopen specification: object
1005 hex; subindex 0 defines the
COB-ID of the synchronization
object (SYNC).
Notes
The structure of this object is

shown in ╚═▷ “COB-ID of SYNC/
TIME messages”
8940 Producer SYNC 2 0 to 65000 ms This is the cycle time of the SYNC
Message time message. If the unit is configured
[20 ms] for this function (parameter ╚═▷
9100) it will send the SYNC
message with this interval. The
time configured here will be
rounded up to the next 10 ms
step.
9101 COB-ID TIME Message 2 1 to FFFFFFFF hex This parameter defines whether
the unit generates the TIME
[100 hex] message or not.
Complies with CANopen

specification: object 1012 hex,
subindex 0; defines the COB-ID of
the time object (TIME).
Notes

shown in ╚═▷ “COB-ID of SYNC/
TIME messages”
9102 Cycle of TIME sync. 2 1.0 to 6500.0 s This is the cycle time of the TIME
message message. If the unit is configured
[10.0 s] for this function (parameter ╚═▷
9101) it will send the TIME
message with this interval.
Notes

shown in ╚═▷ “TIME
synchronization message”
9126 Password protection 5 Off Password protection for CAN 1 is

not active.
Notes
[On] Password protection for CAN 1 is

active.

4 Configuration
4.7.4.1.1 Additional Server SDOs (Service Data Objects)
4.7.4.1.1 Additional Server SDOs (Service Data Objects)
General notes
The CAN bus is a field bus and subject to various disturbances. Therefore, it cannot be
guaranteed that every request will be answered. We recommend to repeat a request,
which is not answered within reasonable time.
The first Node-ID is the standard Node-ID of CAN interface 1 (parameter ╚═▷ 8950).
[Default]
12801 2. Node-ID 2 0 to 127 (dec) In a multi-master application,

each Master needs its own
[0] identifier (Node-ID) from the unit.
in order to send remote signals
(i.e. remote start, stop, shutdown,
or acknowledge) to the unit.
The additional SDO channel will be

made available by configuring this
Node-ID to a value different than
zero. This is the additional CAN ID
for the PLC.


for the PLC.


for the PLC.



4 Configuration
4.7.4.1.2 Receive PDO {x} (Process Data Object)

for the PLC.
General notes
RPDO mapping is carried out as shown in (╚═▷ Fig. 195).
Fig. 195: RPDO mapping principle
Parameters ╚═▷ 9300/╚═▷ 9310/╚═▷ 9320/╚═▷ 12805/╚═▷ 12806 use communication

parameters that adhere to the following structure.
RPDO Objects can be remote signals (parameter 503; please refer to╚═▷ “Remote control
word 1” for details), DI states and AI measured values.
31 (MSB) 0 PDO exists / is valid
1 PDO does not exist / is not valid
30 X N/A
29 X N/A
28-11 0 Always
10-0 (LSB) X Bits 10-0 of COB-ID
PDO valid / not valid allows to select, which PDOs are used in the operational state.

4 Configuration
[Default]
9300 COB-ID 2 1 to FFFFFFFF hex This parameter contains the

communication parameters for
9310 [80000000 hex] the PDOs, the device is able to
receive.
9320
12805 specification: object 1400 hex (for
RPDO 1, 1401 hex for RPDO 2,
12806 1402 hex for RPDO 3, 1403 hex
for RPDO 4, and 1404 hex for
RPDO 5), subindex 1.
Notes

shown in ╚═▷ Chapter 4.7.4.1.2.
Do not configure an RPDO or

TPDO with a COB-ID higher than
580 hex or lower than 180 hex.
These IDs are reserved for internal
purposes.
9121 Event-timer 2 0 to 65500 ms This parameter configures the

time, from which this PDO is
9122 [2000 ms] marked as "not existing". The time
configured here will be rounded
9123 up to the next 5 ms step.
Received messages are processed
9124 by the control unit every 20 ms.
Messages, which are sent faster,
9125 will be discarded. We recommend
to configure ten times the cycle
time of the received data here.
Notes

specification: object 1400 hex (for
1402 hex for RPDO 3, 1403 hex
for RPDO 4, and 1404 for RPDO 5),
subindex 5
8970 Selected Data 2 0 to 65535 A data protocol may be selected

Protocol by entering the data protocol ID
8971 [0] here. If 0 is configured here, the
message assembled by the
8972 mapping parameters is used. If an
unknown data protocol ID is
8973 configured here, a failure is
indicated by the CAN status bits.
8974 Possible data protocol IDs are:
65000 IKD 1 – external DIs/DOs 1 through

8

16
65002
65003

4 Configuration
9910 Number of Mapped 2 0 to 4 This parameter defines the

Objects number of valid entries within the
9915 [0] mapping record. This number is
also the number of the application
9905 variables, which shall be received
with the corresponding PDO.
12821
Notes
12831
RPDO 5), subindex 0
9911 1. Mapped Object 2 0 to 65535 This parameter contains the

information about the mapped
9916 [0] application variables. These
entries describe the PDO contents
9906 by their index. The sub-index is
always 1. The length is
12822 determined automatically.
12832 Notes

1602 hex for RPDO 3,1603 hex for
RPDO 4, and 1604 hex for

12833 Notes


12834 Notes


4 Configuration
4.7.4.1.3 Transmit PDO {x} (Process Data Object)

12835 Notes

General notes
TPDO mapping is carried out as shown in (╚═▷ Fig. 196).
Fig. 196: TPDO mapping

4 Configuration
CANopen allows to send 8 byte of data with each Transmit PDO. These may be defined
separately if no pre-defined data protocol is used.
All data protocol parameters with a parameter ID may be sent as an object with a
CANopen Transmit PDO.
The data length will be taken from the data byte column (see ╚═▷ “9.2 Data Protocols”):
• 1,2 UNSIGNED16 or SIGNED16

• 1,2,3,4 UNSIGNED32 or SIGNED32
• 3,4,5,6 UNSIGNED32 or SIGNED32
• etc.
The object ID is identical with the parameter ID when configuring via front panel or
ToolKit.
Parameters ╚═▷ 9600/╚═▷ 9610/╚═▷ 9620/╚═▷ 9630/╚═▷ 12792 use communication

parameters that adhere to the following structure.
31 (MSB) 0 PDO exists / is valid
1 PDO does not exist / is not valid
30 X N/A
29 X N/A
28-11 0 Always
10-0 (LSB) X Bits 10-0 of COB-ID
PDO valid / not valid allows to select, which PDOs are used in the operational state.
Transmission types
Parameters ╚═▷ 9602/╚═▷ 9612/╚═▷ 9622/╚═▷ 9632/╚═▷ 12793 are used to select one of
the following transmission types.
Transmission PDO transmission

type
Cyclic Acyclic Synchronous Asynchronous RTR only
0 Will not be sent
1-240 X X

4 Configuration
Transmission PDO transmission

type
Cyclic Acyclic Synchronous Asynchronous RTR only
241-251 Will not be sent
252 Will not be sent
253 Will not be sent
254 X
255 X
A value between 1 and 240 means that the PDO is transferred synchronously and
cyclically. The transmission type indicating the number of SYNC messages, which are
necessary to trigger PDO transmissions.
Transmit PDOs are always triggered by the following SYNC upon reception of data
independent of the transmission types 0 to 240. For TPDOs, transmission type 254 and
255 means, the application event is the event timer.
[Default]
9600 COB-ID 2 1 to FFFFFFFF hex This parameter contains the

9610 [80000000 hex] the PDOs the unit is able to
transmit. The unit transmits data
9620 (i.e. visualization data) on the CAN
ID configured here.
9630
12792 specification: object 1800 hex for
(TPDO 1, 1801 hex for TPDO 2,
1802 hex for TPDO 3, 1803 hex for
TPDO 4, and 1804 hex for
TPDO 5), subindex 1.
Notes

shown in ╚═▷ Chapter 4.7.4.1.3
Do not configure an RPDO or

TPDO with a COB-ID higher than
580 hex or lower than 180 hex.
These IDs are reserved for internal
purposes.
In case a LSG is part of CAN 1, do

not configure COB-IDs 181 - 18E
hex because legacy devices are
using same IDs but cannot be
switched.
9602 Transmission type 2 0 to 255 This parameter contains the

9612 [255] the PDOs the unit is able to
transmit. It defines whether the
9622 unit broadcasts all data
automatically (value 254 or 255)
9632 or only upon request with the

4 Configuration
12793 configured address of the COB-ID

SYNC message (parameter ╚═▷
9100).
Notes

TPDO 1, 1801 hex for TPDO 2,
TPDO 5), subindex 2.
The description of the

transmission type is shown in ╚═▷
“Transmission types”.
9604 Event timer 2 0 to 65535 ms This parameter contains the

9614 [20 ms] the PDOs the unit is able to
transmit. The broadcast cycle for
9624 the transmitted data is configured
here. The time configured here
9634 will be rounded up to the next
5 ms step.
12794
Notes

TPDO 1, 1801 hex for TPDO 2,
TPDO 5), subindex 5
8962 Selected Data 2 0 to 65535 A data protocol may be selected

Protocol by entering the data protocol ID
8963 8962: [5003] here. If 0 is configured here, the
message assembled by the
8964 8963: [5008] mapping parameters is used. If an
unknown data protocol ID is
8965 8964: [0] configured here, a failure is
indicated by the CAN status bits.
8966 8965: [0]
Possible data protocol IDs are:
8966: [0]

8

16
65002 IKD 1 – external DIs/DOs 17

through 24
65003 IKD 1 – external DIs/DOs 25

through 32
5003 Data telegram (CAN and MODBUS)
5005 Data telegram (CAN mains values)
5010 Data telegram (MODBUS)
5011 Data telegram (CAN alarm

values )
9609 Number of Mapped 2 0 to 4 This parameter contains the

Objects mapping for the PDOs the unit is
9619

4 Configuration
9629 [0] able to transmit. This number is

also the number of the application
9639 variables, which shall be
transmitted with the
12799 corresponding PDO.
Notes

specification: object 1A00 hex (for
TPDO 1, 1A01 hex for TPDO 2,
1A02 hex for TPDO 3, 1A03 hex
for TPDO 4, and 1A04 hex for
TPDO 5), subindex 0

12795 Notes

TPDO 5), subindex 1

12796 Notes

TPDO 5), subindex 2

12797 Notes

TPDO 5), subindex 3


4 Configuration

12798 Notes

TPDO 5), subindex 4
General notes
This CAN Interface is dedicated to
• J1939 devices and

• external CANopen devices with analog and/or digital terminals.
General Settings
[Default]
3157 Baudrate 2 20 / 50 / 100 / 125 / 250 kBaud This parameter defines the used
baud rate.
[250 kBd]
Notes
All participants on the CAN bus

must use the same baud rate.
4.7.4.2.1 Expansion Modules at CANopen Interface
The CANopen interface at CAN 2 is very flexible.
The configuration of the expansion modules is split into two parts:
• One part is located at the CAN2 interface pages and defines the Node IDs and the
types of external devices and is described here.
An application description explains the setup in detail (refer to ╚═▷ “6.3.10 Setup
Expansion Modules at CAN 2”).
• One other part is located at the external analog/digital inputs/outputs pages and
defines how many inputs/outputs are used and the scaling of the analog types. Refer
to chapters ╚═▷ “4.4.2.4 Analog Inputs” for reference.
• Six Node-IDs can be selected to be used with different combinations of external

terminals ("# Node-ID", parameters 9930-9935)

4 Configuration
• A number of well defined combinations is available for Woodward IKD and/or third
party expansion modules from Phoenix and WAGO: ("Select external terminals",
parameter ╚═▷ 15320)
This parameter defines the type and the maximal number of DI, DO, AI, AO
combinations.
• Alternatively new combinations can be implemented by selecting "Ext.term.file" and

define this separate file by "Sequencer filename", parameter ╚═▷ 15318.
Such files can be prepared by Woodward. Please ask you local Woodward partner for
an offer.
How to read the table ...
• "2 IKD: 16 X DI/DO": 2 devices with 8 DI/DO each (2 x 8 = 16 DI/DO together)

• "P": Phoenix
• "W": Wago
• "_": separator for combinations with different headers
For basic configuration see ╚═▷ “6.3.10 Setup Expansion Modules at CAN 2” - especially
the flow charts of ╚═▷ “Configuration process help”ff.
Assignment of selectable Combinations CAN 2 (Node 1-6) used for DI/DO – Only Digital
Inputs and Digital Outputs:
Combination selected Terminal assigned to ...

by ...
Select # of 1st Node- 2nd Node- 3rd Node- 4th Node- 5th Node- 6th Node-
external ID ID ID ID ID ID
terminals terminals:
I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
DI/DO: Digital Inputs and Digital Outputs, only
1IKD 1 IKD: 8 x IKD1

DI/DO
DI/DO 1-8
2IKD 2 IKD: 16 x IKD1 IKD2

DI/DO
DI/DO 1-8 DI/DO 9-16
3IKD 3 IKD: 24 x IKD1 IKD2 IKD3

DI/DO
DI/DO 1-8 DI/DO 9-16 DI/DO 17-24
4IKD 4 IKD: 32 x IKD1 IKD2 IKD3 IKD4

DI/DO
DI/DO 1-8 DI/DO 9-16 DI/DO 17-24 DI/DO 25-32
P16D 1 Phoenix: P16DIDO

16 x DI/DO
DI/DO 1-16
W16D 1 WAGO: 16 W16DIDO

x DI/DO

4 Configuration

by ...
I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
DI/DO 1-16
P32D 1 Phoenix: P32DIDO

32 x DI/DO
DI/DO 1-32
W32D 1 WAGO: 32 W32DIDO

x DI/DO
DI/DO 1-32
P16D_ 16D 2 Phoenix: P16DIDO P16DIDO

32 x DI/DO
DI/DO 1-16 DI/DO 17-32
Assignment of selectable Combinations CAN 2 (Node 1-6) used for AI/AO – Only Analog
Inputs and Analog Outputs:

by ...
I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
AI/AO: Analog Inputs and Analog Outputs, only
P 16AI 4AO 1 Phoenix: P16AI4AO
16 x AI / 4 x AI 1-16
AO
AO 1-4
W 16AI 4AO 1 WAGO: W16AI4AO
16 x AI / 4 x AI 1-16
AO
AO 1-4
Assignment of selectable Combinations CAN 2 (Node 1-6) used for DI/DO/AI/AO:

Combinations of the expansion modules:

by ...
I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
DI/DO/AI/AO: Combinations of the expansion modules IKD and/or Phoenix
1IKD_ P 1 IKD: IKD1 P16AI4AO

16AI 4AO
8 x DI/DO DI/DO 1-8 AI 1-16
1 Phoenix: AO 1-4

4 Configuration

by ...
I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
16 x AI / 4 x
AO
2IKD_ P 2 IKD: IKD1 IKD2 P16AI4AO

16AI 4AO
16 x DI/DO DI/DO 1-8 DI/DO 9-16 AI 1-16
1 Phoenix: AO 1-4
16 x AI / 4 x
AO
3IKD_ P 3 IKD: IKD1 IKD2 IKD3 P16AI4AO

16AI 4AO
24 x DI/DO DI/DO 1-8 DI/DO 9-16 DI/DO 17-24 AI 1-16
1 Phoenix: AO 1-4
16 x AI / 4 x
AO
4IKD_ P 4 IKD: IKD1 IKD2 IKD3 IKD4 P16AI4AO

16AI 4AO
32 x DI/DO DI/DO 1-8 DI/DO 9-16 DI/DO 17-24 DI/DO 25-32 AI 1-16
1 Phoenix: AO 1-4
16 x AI / 4 x
AO
P 16D_ 16AI 1 Phoenix:: P16DIDO P16AI4AO

4AO
16 x DI/DO DI/DO 1-16 AI 1-16
1 Phoenix: AO 1-4
16 x AI / 4 x
AO
P 16D 16AI 1 Phoenix: P16DIDO

4AO
16 x DI/DO DI/DO 1-16
16 x AI / 4 x P16AI4AO
AO
AI 1-16
AO 1-4
W 16D 16AI 1 WAGO: W16DIDO

4AO
16 x AI / 4 x W16AI4AO
AO
AI 1-16
AO 1-4
P 32D 16AI 1 Phoenix,: P32DIDO

4AO
P16AI4AO

4 Configuration

by ...
I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
16 x AI / 4 x AI 1-16
AO
AO 1-4
W 32D 16AI 1 WAGO,: W32DIDO
4AO
16 x AI / 4 x W16AI4AO
AO
AI 1-16
AO 1-4
2P 16D_ 2 Phoenix: P16DIDO P16DIDO P16AI4AO

16AI 4AO
1 Phoenix: AO 1-4
16 x AI / 4 x
AO
P32 D_ 16AI 1 Phoenix: P32DIDO P16AI4AO

4AO
32 x DI/DO DI/DO 1-32 AI 1-16
1 Phoenix: AO 1-4
16 x AI / 4 x
AO
DI/DO/AI/AO: Combinations of the expansion modules IKD and/or WAGO
W 16AI 4AO 1 Wago: W16AI4AO
16 x AI / 4 x AI 1-16
AO
AO 1-4
1IKD_ W 1 IKD: IKD1 W16AI4AO

16AI 4AO
8 x DI/DO DI/DO 1-8 AI 1-16
1 Wago: AO 1-4
16 x AI / 4 x
AO
2IKD_ W 2 IKD: IKD1 IKD2 W16AI4AO

16AI 4AO
1 Wago: AO 1-4
16 x AI / 4 x
AO
3IKD_ W 3 IKD: IKD1 IKD2 IKD3 W16AI4AO

16AI 4AO
24 x DI/DO DI/DO 1-8 DI/DO 9-16 DI/DO 17-24 AI 1-16
1 Wago: AO 1-4

4 Configuration

by ...
I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
16 x AI / 4 x
AO
4IKD_ W 4 IKD: IKD1 IKD2 IKD3 IKD4 W16AI4AO

16AI 4AO
32 x DI/DO DI/DO 1-8 DI/DO 9-16 DI/DO 17-24 DI/DO 25-32 AI 1-16
1 Wago: AO 1-4
16 x AI / 4 x
AO
If you need only four analog inputs, select “P16AI4AO” and configure only four inputs to
ON at the configuration for the external analog inputs.
CANopen Settings and Procedure
Proceed as follows to configure an external device:
• Connect external device(s)
• Check that WAGO devices are configured to default.
This is the case if the WAGO CAN-Coupler is new or if there was any change in
number or kind of WAGO modules.
• Configure and check parameters at the easYgen (Select external terminals, Node-ID,
DI/DOs, AI/AOs)
Reboot the device that the setting (15320 ) becomes effective
• If WAGO terminals are connected and the configuration of the external AIs and/or
AOs is done, the easYgen must send a configuration string to the WAGO coupler one
time. This can be done by setting parameter »Configure external devices« ╚═▷
15134 to "YES". This must be repeated if there is any change in number or kind of
WAGO modules.
• If you have changed parameter »Select external terminals « ╚═▷ 15320: reboot the
device
• Set parameter »Configure external devices« ╚═▷ 15134 to "Yes"
• Verify the successful configuration of the external device(s)
Update WAGO After Any Change!
The update procedure described above must be repeated if there is any change in
number or kind of Wago modules.

4 Configuration
[Default]
9940 This device 2 Node-ID 1-126 The Node-ID for the control unit
(this device) is configured here.
[Node-ID 7]
9930 1st Node-ID 2 Node-ID 1-126 This Node-ID's are used for the
communication with CANopen
[Node-ID 1] devices.
Parameter ╚═▷ 15320 "Select

9931 2nd Node-ID 2 Node-ID 1-126
external terminals" offers often
[Node-ID 2] used pre-settings and the
possibility to point to a file
containing customer specific
9932 3rd Node-ID 2 Node-ID 1-126 settings.
[Node-ID 3]
9933 4th Node-ID 2 Node-ID 1-126
[Node-ID 4]
[Node-ID 5]
[Node-ID 6]
15320 Select external 2 Notes

terminals
A change of this parameter
becomes only effective if the
device is rebooted! and:
the external devices itself must be

configured with the correct node
ID.
[Off] No external CANopen device is

supported on CAN2
Ext. term file File defined with parameter ╚═▷

15318 is active.
1IKD Selection of the combination of

terminal(s) at the six pre-set
2IKD Node-IDs.
3IKD For terminal description see table

╚═▷ Tab. above.
4IKD
P16D
P32D
P16D_16D
P16AI4AO
1IKD_ P16AI4AO
2IKD_ P16AI4AO
3IKD_ P16AI4AO
4IKD_ P16AI4AO

4 Configuration
[Default]
P16D_16AI4AO
P16D16AI4AO
P32D16AI4AO
2P16D_16AI4AO
P32D_16AI4AO
W16AI4AO
1IKD_W16AI4AO
2IKD_W16AI4AO
3IKD_W16AI4AO
4IKD_W16AI4AO
W16D
W32D
W16D16AI4AO
W32D16AI4AO
15318 Sequencer filename 2 [Filename.seq] Filename of a special additional

file to define external devices (see
NOTE ╚═▷ Chapter 4.7.4.2.1).
Notes
This parameter takes only effect if

parameter ╚═▷ 15320 is
configured to “Ext.term.file”.
Please ask your Woodward partner

for support / an offer.
15134 Configure external 2 Yes This parameter starts the

devices configuration of external Phoenix
[No] expansion boards.
Notes
This parameter can only be used

to configure Phoenix or Wago
expansion boards as describe
above.
Refer to the IKD 1 Manual 37135

for configuring the IKD 1
expansion boards.
Changing the Node ID
Changing the Node ID of a Wago terminal which is still configured:
• Set the new NODE-ID via DIP switches
• Load default values (via a temporary change in number or kind of Wago modules-run
configuration again.

4 Configuration
4.7.4.2.1.1 Configurable Wago devices
4.7.4.2.1.1 Configurable Wago devices
If configurable WAGO devices are used, the mode of the terminal must be configured via
the PC software WAGO I/O Check. These configuration cannot be done via the easYgen
parameters. Be aware that the easYgen parameters for the corresponding channels must
be consistent with the Wago configuration done with the WAGO I/O Check.
RTD device (750-451)
To use the 8 channel RTD device (750-451) the following process image must be
configured via the Wago I/O-Check.
The following types are not supported: Ni1000 (high resolution), Ni1000 (TK5000),
Pt1000 (EN 60751 high resolution), and 1200 Ohm.
Typ Expected format
Pt100 (EN 60751) default
Ni100 (EN 60751) default
Ni1000 (TK6180, DN 43760) default
Ni120 (Minco) default
5000 Ohm S5-FB250
Thermocouple device (750-458) for voltage measurement
There is no intuitive setting in the easYgen-XT if a channel of the Thermocouple (TC)

device (750-458) is configured for voltage measurement. But nevertheless it is possible.
Therefore a special scaling of the easYgen-XT parameters “Sender value at display min.”
and “Sender value at display max” is required like described in the table below:
Voltage measuring range “Sender value at display “Sender value at display max.”
min.”
+/- 30 mV -614.4 614.4
+/- 60 mV -307.2 307.2
+/- 120 mV -153.6 153.6

4 Configuration
4.7.4.2.2 J1939 Interface
General notes
For additional information refer to ╚═▷ “7.5 J1939 Protocol”.
Parameter 15102 »Device type « allows to select an ECU either by name or - for even
more flexibility - via an ECU file; then the name of the preferred ECU file must be entered
into parameter 15167 »ECU file name«. Please ask your local Woodward partner for
further information.
[Default]
15166 J1939 2 Off The J1939 interface is disabled. No

messages will be received or
transmitted.
[On] The J1939 interface is enabled.
The J1939 interface of this device

may be operated with different
engine control units or analog
input devices. J1939 values (e.g.
from an ECU) can be received and
indicated
15102 Device type 2 The J1939 interface of this device

may be operated with different
engine control units or analog
input devices.
This parameter determines the

type of the used ECU or that a
special ECU file designed for an
ECU which is not listed here shall
be used.
Notes
A change of this parameter takes

only effect after reboot ╚═▷ 10419
the device!
ECU file This is to support ECUs which are

not represented by the selection.
Enter file name with parameter
15167 »ECU file name« below.
[Standard] Standard J1939 coupling is

enabled: J1939 data is displayed
according to the SAE J1939
standard.
This setting must be configured

for all J1939 ECUs, which cannot
be selected here (e.g. Deutz
(EMR3 & EMR4), John Deere,
Daimler, Perkins, Iveco,
Caterpillar, Liebherr, etc.).
Please refer to ╚═▷ “7.5 J1939

Protocol” for details and/or ask
your local Woodward partner for
an offer.

4 Configuration
[Default]
S6 Scania The Scania EMS/S6, S8 ECU is

enabled: J1939 data according to
the SAE J1939 standard and some
S6-specific data are considered.
EMR2 Deutz The Deutz EMR2 ECU is enabled:

J1939 data according to the
SAE J1939 standard and some
EMR2-specific data are
considered.
This setting is also recommended

for Volvo EDC4.
EMS2 Volvo The Volvo EMS2 ECU is enabled:

EMS2-specific data are
considered.

for Volvo EDC3 and EMS1.
ADEC ECU7 MTU The MTU ADEC ECU7 with SAM is

ADEC-specific data are
considered.
EGS Woodward The Woodward EGS ECU or E3-

series or E6-series are enabled:
J1939 data according to the SAE
J1939 standard and some
EGS/E3/E6-specific data are
considered.
MFR/EDC7 MAN The MAN MFR/EDC7 ECU is

EDC-specific data are considered.
EEM SISU The SISU EEM2/3 ECU is enabled:

EEM2/3-specific data are
considered.
Cummins The Cummins ECU is enabled:

Cummins-specific data are
considered.

for Cummins CM570 and CM850.
Notes
Some Cummins setups need a

special value for “Governor Gain”
otherwise they will shut down. In
this cases please set the
“Governor Gain” of the ECU
to »Internal« instead of »J1939«.
ADEC ECU8/ECU9 MTU The MTU ADEC ECU8 with

SmartConnect or the MTU ADEC
ECU9 is enabled: J1939 data
according to the SAE J1939

4 Configuration
[Default]
standard and some ADEC-specific

data are considered.
HATZ EDC17 The BOSCH ECU HATZ EDC17 is

enabled.
If "VGA (Preglow)" is active, then

LogicsManager Variable 03.17
becomes TRUE; if "Maintenance"
becomes activ, then
LogicsManager Variable 03.18
becomes TRUE.
15167 ECU file name 2 [Filename.ecu] If »Device type« ID15102 is »ECU

file«, the easYgen can
communicate with further ECUs.
The correct file name with
extension must be typed in and
this xxx.ecu file must be available
"inside" the easYgen (flashed).
Notes
Please contact your local

Woodward partner to enable
communication with your ECU
(xxx.ecu file and ECU specific
settings).
15106 J1939 own address 2 0 to 255 The easYgen sends J1939 request
and control messages with this
[234] source address. It must be
changed for different ECU types
according to the following table.
The ECU listens only to control
messages, if they are sent to the
correct address.
• S6 Scania: 39
• EMR2 Deutz: 3
• EMS2 Volvo: 17
• ADEC ECU7 MTU: 1
• EGS Woodward: 234
• MFR/EDC7 MAN: 253
• EEM SISU: N/A
• Cummins: 220
• ADEC ECU8/ECU9 MTU: 234
• Hatz EDC17: 3
• Standard: Please refer to ╚═▷
“7.5 J1939 Protocol” and to
the manual of your J1939
ECU manufacturer.
Details may be found in the

manual of the genset control and
in ╚═▷ “7.5 J1939 Protocol”.
15107 Engine control 2 0 to 255 Configures the address of the

address J1939 device, which is controlled.
[0] The easYgen sends J1939 request
and control messages with this
destination address.
• S6 Scania: 0
• EMR2 Deutz: 0

4 Configuration
[Default]
• EMS2 Volvo: 0
• ADEC ECU7 MTU: 128
• EGS Woodward: 0
• MFR/EDC7 MAN: 39
• EEM SISU: 0/(1)
• Cummins: 0
• ADEC ECU8/ECU9 MTU: 0
• Hatz EDC17: 0
• Standard: Please refer to ╚═▷
“7.5 J1939 Protocol” and to
the manual of your J1939
ECU manufacturer.
Details may be found in the

manual of the genset control and
in ╚═▷ “7.5 J1939 Protocol”.
15108 Reset previous act. 2 Yes If this parameter is set to "Yes", a

DTCs - DM3 DM3 message "Acknowledge
[No] passive faults" is sent. After that
this parameter is reset
automatically to "No".
As a result the alarms DTCs

(Diagnostic Trouble Codes) of
(DM2) which no longer apply are
cleared.
15133 Reset act. DTCs - 2 Yes If this parameter is set to "Yes", a

DM11 DM11 message "Acknowledge
[No] active faults" is sent. After that
this parameter is reset
automatically to "No".
As a result the alarms DTCs

(Diagnostic Trouble Codes) of
(DM1) which no longer apply are
cleared.
15103 SPN version 2 Version 1 / 2 / 3 The J1939 protocol provides 4

different versions for the
[Version 1] conversion method of the Suspect
Parameter Number (SPN). This is
important for a correct
interpretation of the alarm
messages (DM1 & DM2).
This parameter defines the

version of the conversion method:
Version 1, Version 2 or Version 3.
Version 4 is detected
automatically.
For details please refer to the

manual of your J1939 ECU
manufacturer.
15127 ECU remote 2 On The unit sends J1939 control

controlled messages to the ECU. Depending
on the selected device type
(parameter ╚═▷ 15102), contains
a specific selection of commands.
[Off] The ECU remote control via the

J1939 protocol will be disabled.

4 Configuration
[Default]
Notes
The unit sends J1939 control

messages to the ECU. Depending
on the selected device type
(parameter ╚═▷ 15102), it
contains a specific selection of
commands. Available messages
are speed deviation and droop for
ECUs as well as engine start/stop,
enable idle mode, rated speed
switch and preglow for some
ECUs.
Refer to ╚═▷ “7.5 J1939 Protocol”

for more detailed information.
5537 Speed deviation ECU 2 0 to 1,400 rpm This parameter adjusts the range
of the speed deviation around the
[120 rpm] rated speed, which is sent to the
ECU.
It relates to the engine rated

speed (parameter ╚═▷ 1601).
There are two methods of sending

the speed setpoint to the ECU:
With a speed offset and a speed
setpoint. The frequency and
power control must be configured
to "PID".
Speed offset
(S6 Scania, EMS2 Volvo, EGS

Woodward, Cummins)
The easYgen sends a speed offset

with a range of 0 to 100% (every
20 ms). 50% = rated speed.
There is also an internal speed

offset configured in the ECU, this
parameter determines what
corresponds with 0% or 100%. If
there is a positive and a negative
speed offset, they should be
symmetrical in the ECU.
We recommend to have the same

speed offset configured in the ECU
and in this parameter here. A
different setting will result in an
additional "controller gain".
How to test this parameter during

commissioning:
Islanded operation
Disable the frequency controller

and change parameter ╚═▷ 5508
for the initial state between 0 and
100%, the engine should change
the speed as follows:
• 0 = rated speed – negative

speed offset from ECU
• 50 = rated speed

4 Configuration
[Default]
• 100 = rated speed + positive

speed offset from ECU
Mains parallel operation
Check with the setpoint in the

display if the engine is able to
deliver the full power.
Speed setpoint
(EMR2 Deutz, ADEC MTU, EGS

Woodward, EEM SISU, Standard)
The easYgen sends a speed

setpoint in rpm (every 10 ms) that
varies around the rated speed in
the range of +/- the speed
deviation.
How to test this parameter during

commissioning:
Islanded operation
Disable the frequency controller

and change parameter ╚═▷ 5508
for the initial state between 0 and
100%, the engine should change
the speed as follows:
• 0 = rated speed – speed

deviation ECU
e.g.: 1,500 – 120 = 1,380

rpm
• 50 = rated speed
e.g.: = 1,500 rpm
• 100 = rated speed + speed

deviation ECU
e.g.: 1,500 + 120 = 1,620

rpm
Mains parallel operation
Check with the setpoint in the

display if the engine is able to
deliver the full power.
Keep this value as small as

possible, i.e. do not enter a speed
deviation of 500, if the engine
varies only between 1,400 and
1,600 rpm.
Notes
The Woodward EGS ECU supports

both types of speed deviation
control and may be configured
either to "Speed offset" or "Speed
setpoint".
In mains parallel operation, the

EGS can be configured to receive
a real power setpoint from the
easYgen to control the power. In

4 Configuration
[Default]
this case, real power control must

be disabled in the easYgen.

ECU remote controlled
configured to "On".
4843 ECU Application 2 [Continuous] Prepared for MTU - 3B mode
Emergency Prepared for MTU - 3D mode
Notes

manufacturer.

"Device type" (parameter ╚═▷
15102) is configured to "ADEC
ECU8 MTU" and "ECU remote
controlled" (parameter ╚═▷
15127) is configured to "On".
12939 ECU Power Mode 2 [Low power mode] Prepared for MTU - Low mode
High power mode Prepared for MTU - High mode
Notes

manufacturer.

"Device type" (parameter ╚═▷
15102) is configured to "ADEC
ECU8 MTU" and "ECU remote
controlled" (parameter ╚═▷
15127) is configured to "On".
15164 ECU seq. B_IN_1 2 Determined by LogicsManager This LogicsManager is prepared to

86.31 pass binary information to the
ECU. Right now it is only used for:
[(0 & 1) & 1]
ADEC ECU 9 "Rapid Engine
= 11647 Start"
If the easYgen is transmitting a

start command and the result of
“86.31 LM: ECU seq. B_IN_1 is:
False, the ECU9 will start with

"Normal Engine Start"
True, the ECU9 will start with

"Rapid Engine Start"
EMS2 Volvo “Override” (Engine

restored operation)
If the result of “86.31 LM ECU seq.

B_IN_1 is:
False: The Volvo override flag is

only active if LM “04.27 Critical
mode is active”

4 Configuration
[Default]
True: The Volvo override flag is

active independent of LM “04.27
Critical mode is active”
Notes

15165 ECU seq. B_IN_2 2 Determined by LogicsManager This LogicsManager is prepared to

ECU. Right now it is not used.
[(0 & 1) & 1]
Notes
= 11648
15162 AM ECU seq. A_IN_1 2 Determined by AnalogManager This LogicsManager is prepared to

ECU. Right now, it is not used.
[A1 = 10.01 ZERO]
mtu ECU9 “Alternate Droop
Accelerator 1 Select”
If the result of AM 81.22 is:
-0, the ECU9 is running with

“Normal droop”
-has a value 1 – 13, the ECU9 is

running with an alternative droop
- is > 13 or negative, the ECU9 is

running with “Normal droop”
Please be aware that the values

assigned to this function must be
whole-numbers. If not, the
decimals will be cut.
Notes

AnalogManager.

15163 AM ECU seq. A_IN_2 2 Determined by AnalogManager This AnalogManager is prepared to

81.23 pass analog information to the
ECU via J1939.
[A1 = 10.01 ZERO]
If this AnalogManager is used by
an ECU its function will be
described in the manual of the
corresponding J1939 ECU. For
more information please see
J1939 ECU description.
Notes

4 Configuration
4.7.5 Ethernet Interfaces
[Default]

AnalogManager.

Tab. 86: J1939 Settings
4.7.5 Ethernet Interfaces
General notes
The Ethernet network provides a fast communication capability to different devices, like
remote panel, PLC or SCADA systems. The common protocol Modbus TCP is there for the
preferred communication protocol. Additionally the Ethernet connection supports the
Woodward protocol Servlink for ToolKit and other Woodward own monitoring tools (like
remote panel and SCADA visualization tool). At least the easYgen provides a UDP protocol
for system relevant and time discrete information exchange.
Do not connect the easYgen with the internet as long the security aspects are not
considered. Consider an IP responsible person to discuss proper security procedures like
placing routers and fire walls.
If the easYgen (or -system) shall be connected to an already existing Ethernet network, a
network responsible person must arrange and allocate the IP Addresses. He takes care
about IP-Address, the subnet mask, and when needed the gateway IP Address.

[Default]
7488 (Time needed to 12 "7488" x "7489" Notes

and detect
7489 "connection Should not be changed - otherwise please ask your
missing") Woodward sales support partner for a temporary code
level access.
Visible in ToolKit only.
The "Transmission rate" (ID 7488) multiplied with the

number of "Timeout cycles" (ID 7489) is the time it
needs to detect a"connection missing".
7488 Transmission rate [80 ms] The transmission rate defines the refresh rate (time) of
the UDP messages, for example load share messages.
80 to 400 ms
7489 Timeout cycles [5] The control monitors the expected amount of received
UDP messages. This entry is the number of LDSS
2 to 10 messages that can be lost before it is detected as
"connection missing".

4 Configuration
4.7.5.1 General notes “Network address”

[Default]
7485 Modbus/TCP 2 [1] Your local Modbus device address, which is used to
Slave ID identify the device via Modbus/TCP (Ethernet), must be
1 to 255 entered here.
9129 Password 5 Off Password protection for Ethernet is not active.

protection
Notes
[On] Password protection for Ethernet is active.
4.7.5.1 General notes “Network address”
A network address is basically calcutated of an IP address and a subnet mask. The

network address is the result of a binary AND connection of the IP address and the subnet
mask:
Example network address calculation
decimal binary
IP address 192.168.002.001 11000000 10101000 00000010 00000001
Subnet mask 255.255.255.224 11111111 11111111 11111111 11100000
Network address = IP address AND Subnet mask 192.168.002.000 11000000 10101000 00000010 00000000
The device (host) part is the individual part of the network address for a dedicated
device. The device part is the result of the binary AND connection of the IP address and
the inverted subnet mask:
Example device part (host) calculation
decimal binary
IP address 192.168.002.001 11000000 10101000 00000010 00000001
Subnet mask 255.255.255.224 11111111 11111111 11111111 11100000
Subnet mask inverted 00000000 00000000 00000000 00011111
Device part = IP address AND Subnet mask 000.000.000.001 00000000 00000000 00000000 00000001
inverted

4 Configuration
4.7.5.2 Ethernet Network A
Fig. 197: Ethernet Network A screen
The actual IP address, subnet mask, gateway IP address (all hex values) can be viewed
under Next Page (Status Menu) / Diagnostic / Interfaces / Ethernet / Ethernet A.
IP address
Each port within the Ethernet network must have its own network address. As long the
Ethernet network is only used by the easYgen-XT system, the address range is free
configurable. For better troubleshooting use the default Ethernet address range and
configure the single IP addresses according to their device numbers.
Device part: Restrictions
The "device part" is the logical result of »IP Address« AND NOT »Network Mask«. The bits
(dual system 02/12) of the device part must be different from being all the same - neither
all zero 02 nor all 12 (broadcast).
Please select your IP address accordingly.

4 Configuration
Gateway IP address
Fig. 198: Ethernet IP and gateway addresses
The gateway IP address defines a node within a local area network (LAN), which is
directed to external networks. It is usually not needed in an easYgen Ethernet network.
Refer to your network responsible contact person, if a gateway capability is required.
HEX values
The addresses and subnet masks are known as hex values but are displayed in HMI and
ToolKit as decimal values.

[Default]
5330 IP address 2 [10, 31, 140, 0] Field 1,2,3,4 for IP address Ethernet port A. This setting
will be not valid automatically. The »Set IP
5331 address« parameter must be set to »ON« for enabling.
5332 Notes
5333 Device part bits are not allowed to be either all 00...2
or all 11...2 (broadcast).
7412 Set IP address 2 Off Set IP-Address Ethernet port A.
5334 Subnet mask 2 [255, 255, 240, 0] Set byte 1,2,3,4 of the subnet mask Ethernet port A.
This setting will be not valid automatically. The »Set
5335 subnet mask« parameter must be set to »ON« for
enabling.
5336
5337
7413 Set subnet mask 2 Off Set subnet mask Ethernet port A.
5338 Gateway IP 2 [0, 0, 0, 0] Field 1,2,3,4 for gateway IP-Address for Ethernet port A.
This setting will be not valid automatically. The »Set IP
5339 address« parameter must be set to »ON« for enabling.
If 0.0.0.0 is set, the gateway's functionality is switched
5340 off.
5341

4 Configuration
4.7.5.3 SNTP

[Default]
5342 Set Gateway IP 2 Off Set Gateway IP Address for Ethernet port A
address
4.7.5.3 SNTP
SNTP feature
The Simple Network Time Protocol (SNTP) is a common procedure to synchronize clocks in
computer systems via packaged based communication networks. In this manner, the
easYgen-XT can be configured as a SNTP client. The easYgen-XT is also usable as a SNTP
server within the local area network by its own IP address.
The SNTP functionality can be configured for three modes:
• External SNTP mode
The easYgen-XT requests time and date information from an external SNTP server,
marked with an own IP address.
• Load sharing mode
The easYgen-XT requests time and date information from the easYgen with the
smallest device number, if the load sharing over Ethernet is enabled.
• Internal clock mode
The SNTP client mechanism is disabled. The own real time clock determines clock
and date.
HEX values
The addresses and subnet masks are known as hex values but are displayed in HMI and
ToolKit as decimal values.

[Default]
7780 SNTP address 2 [10, 14, 128, 128] Set byte 1,2,3,4 of the IP address of the external SNTP-
Server.
7781 0 to 255 (4x)
7782
7783
7784 Rate 2 [1200s] Set the time rate of the SNTP-Server request.
60 to 6000
7785 Timeout 2 [60s] Set the timeout of the SNTP-Server. This feature is
prepared for the future and has currently no influence
30 to 600 on the function.
7786 Mode 2 [Internal clock] The device provides different SNTP modes.
External SNTP Internal clock: The clock information comes from the
internal clock. The SNTP function is disabled.
Load share

4 Configuration
4.7.6 Load Share Parameters

[Default]
External SNTP-Server: The clock information is
receipt by an external SNTP-Server.
Load share: The clock information is generated within

the easYgen system. A master (usually the device with
the smallest device number) serves all easYgens with
time and date information according to their request
rate.
4.7.6 Load Share Parameters
[Default]
9921 Transfer rate LS fast 2 0.10 to 0.30 s The transfer rate defines the time
message delay between two fast CAN
[0.10 s] messages.
(CAN)
In case of CAN systems with a
high bus load (e.g. long distance
between the units with low baud
rate), a shorter transfer rate
(higher time setting) helps to
reduce the bus load.
9920 Load Share CAN-ID 2 2xx hex / 3xx hex / 4xx hex / 5xx The first digit of the CAN ID or the
hex range (i.e. 2xx means 200 through
2FF hex) is configured here.
[5xx hex]
The last two digits will be assigned
by the control with the settings
from the device number
4.8 Configure LogicsManager

Logical symbols
The easYgen LogicsManager screens show logical symbols according to the IEC standard
by default. However, it is also possible to change the LogicsManager screens to ASA
standard.
[Default]
4117 Use ASA symbols 2 Yes Symbols according to the ASA

standard are used in
LogicsManager screens.
[No] Symbols according to the IEC

standard are used in
LogicsManager screens.

4 Configuration
Refer to ╚═▷ “9.3.3 Logical Symbols” for a table of symbols according to the different
standards.
Refer to ╚═▷ “9.3.1 LogicsManager Overview”for an introduction how a LogicsManager

works.
Internal flags
Internal flags within the LogicsManager logical outputs may be programmed and used for
multiple functions.
Flag {x} Flag 1 Flag 2 Flag 3 Flag 4 Flag 5 Flag 6 Flag 7 Flag 8
Parameter 12230 12240 12250 12260 12270 12280 12290 12300

ID
{yyyyy}
Result 10700 10701 10702 10702 10704 10705 10706 10707
Tab. 87: Flag parameter IDs (1 to 8)
Parameter 12910 12911 12912 12913 12914 12915 12916 12917

ID
{yyyyy}
Result 11609 11610 11611 11612 11613 11614 11615 11616
Parameter 12231 12233 12235 12237 12241 12243 12245 12247

ID
{yyyyy}
Result 12232 12234 12236 12238 12242 12244 12246 12248
Parameter 12251 12253 12255 12257 12261 12263 12265 12267

ID
{yyyyy}
Result 12252 12254 12256 12258 12262 12264 12266 12268
[Default]
{yyyyy} Flag {x} 2 Determined by LogicsManager The flags may be used as auxiliary
{XX.XX} flags for complex combinations by
using the logical output of these
[(0 & 1) & 1] flags as command variable for
other logical outputs.
= {nnnnn}
Notes

4 Configuration
[Default]
Flag 1 is also used as placeholder

in other logical combinations.
Flag 8 is preset with a timer start

and shows different default
values.
{XX.XX} is a placeholder for the

LogicsManager number
{nnnnn} is a placeholder for the

parameter ID of the logical output
of the LogicsManager equation
For conditions and explanation of programming please refer to ╚═▷ “9.3.1 LogicsManager
Overview”.
LogicsManager Timers: Set timers
Daily time setpoints - Timer 1, 2
Utilizing the LogicsManager it is possible to establish specific times of the day that
functions (i.e. generator test run or or engine pre-lubrication) can be enabled.
The two daily time flags are activated each day at the configured time. The both flags
will be RESET at the end of the day on exact 23h.59m.59s. The both timer flags are
independent of each other and are considered as intermediate flags to create a special
control flag or function. Using the LogicsManager, the flags can be configured individually
or both flags can be combined to create a time range. Refer to chapter example to
understand their meaning better. Refer to ╚═▷ “6.3.17 Examples timer configuration”).
Note:
If the RTC time is within the configured time (with hour, minute and second), a latch with
the corresponding LM Timer flag (11.01, 11.02) becomes TRUE. This latch and the LM
flags will be reset each day at the time the RTC time 23:59:59 is reached. It is very
important to consider that, when testing the function. For a complete test of the
configuration it is recommended to let the RTC pass the configured time (even the
23.59.29 reset time).
Active time setpoint
Utilizing the LogicsManager it is possible to establish specific days (and/or hours,

minutes, seconds) that functions (i.e. generator exerciser) can be enabled. The active
switching point is activated only on a specified day (and/or hour, minute, second).
The setpoints may be configured individually or combined via the LogicsManager. You
may configure for each month: daily, hourly, minutely, and/or even secondly time
setpoints depending on how you combine the setpoints in the LogicsManager.

4 Configuration
Active week days - weekly time setpoint
Utilizing the LogicsManager it is possible to establish specific days of the week that
functions (i.e. generator exerciser) can be enabled.
The weekly time setpoint is enabled during the indicated day from 0:00:00 hours to
23:59:59 hours.
For examples refer to ╚═▷ “6.3.17 Examples timer configuration”
Daily time setpoints - Timer 1, 2
[Default]
1652 Timer {x}: Hour 2 0 to 23 h Enter the hour of the daily time
setpoint here.
1657 1652: [8 h]
Example
1657: [17 h]
(midnight).
(11pm).
1651 Timer {x}: Minute 2 0 to 59 min Enter the minute of the daily time
setpoint here.
1656 [0 min]
Example
• 0 = 0th minute of the hour.

1650 Timer {x}: Second 2 0 to 59 s Enter the second of the daily time
setpoint here.
1655 [0 s]
Example

minute.
minute.
Active time setpoint
[Default]
1663 Active day 2 Day 1 to 31 Enter the day of the active switch
point here.
[1]
The active time setpoint is
enabled during the indicated day
from 0:00:00 hours to 23:59:59
hours.
Example

4 Configuration
[Default]

1662 Active hour 2 0 to 23 h Enter the hour of the active switch

point here.
[12 h]
enabled every day during the
indicated hour from minute 0 to
minute 59.
Example
• 0 = 0th hour of the day.

• 23 = 23rd hour of the day.
1661 Active minute 2 0 to 59 min Enter the minute of the active

switch point here.
[0 min]
enabled every hour during the
indicated minute from second 0 to
second 59.
Example

1660 Active second 2 0 to 59 s Enter the second of the active

switch point here.
[0 s]
enabled every minute during the
indicated second.
Example

minute.
minute.
Active week days - weekly time setpoint
[Default]
Please select each of the

active weekdays.
1670 Monday active 2 [Yes] The switch point is enabled every

Monday.
No The switch point is disabled every

Monday.
1671 Tuesday active 2 [Yes] The switch point is enabled every

Tuesday.

Tuesday.

4 Configuration
4.9 Configure AnalogManager
[Default]
1672 Wednesday active 2 [Yes] The switch point is enabled every

Wednesday.

Wednesday
1673 Thursday active 2 [Yes] The switch point is enabled every

Thursday.

Thursday.
1674 Friday active 2 [Yes] The switch point is enabled every

Friday.

Friday.
1675 Saturday active 2 Yes The switch point is enabled every

Saturday.
[No] The switch point is disabled every

Saturday.
1676 Sunday active 2 Yes The switch point is enabled every

Sunday.
[No] The switch point is disabled every

Sunday.
4.9 Configure AnalogManager
4.9.1 Operations
An AnalogManager (AM) is a flexible sub-system to process and/or generate both an

analog output signal and a related digital output. It offers a set of functions (Type) to
select the preferred signal processing. According to the selected function the AM
computes up to two analog inputs and one constant for result. Up to two digital inputs
enable to control the process (internal logic allows to adjust boolean signal).
Inputs:
• Up to 2 analog variables (A1, A2) and
• 1 direct configurable constant (C1)
in conjunction with
• up to 2 Boolean information (L1, L2)*.
The AM processes the inputs listed above depending on the selected "Type". The result
is always provided in form of
• an analog value (AR) and
• a Boolean (BR).
There are two types of AnalogManagers:
• Freely usable AM to process signals and use the results for output as control.

4 Configuration
4.9.1 Operations
• Dedicated AM which analog result is directly accepted by (fixed to) an according

function (e.g. AO01).
For both freely and dedicated AM is valid:
• The analog result is accessible via the AnalogManager command variable pool.
• The resulting Boolean is accessible via the LogicsManager command variable pool.
⚙ Preferred AM Definition Procedure
1. ▷ Start with "Type"

▶ Select AM type first to get the picture and the visual understanding of available inputs,
outputs, function, and results.
2. ▷ Select analog inputs and set constant.
Besides internal and measured values there are 16 »Free

constants« available for more flexibility. Refer to ╚═▷ “4.9.2 AnalogManager
Constants”for details.
3. ▷ Prepare each digital input by selecting source (parameter) and logical function.
4. ▷ Enter with "Apply"
▶ Press »Apply« button to send current settings to device.
5. ▷ Use analog and boolean result for intended (re)action.
Fig. 199: Display (HMI) AM14

4 Configuration
4.9.1 Operations
Fig. 200: ToolKit AM14
*) Please be aware that the boolean information passes an operator. So the input for the
AnalogManager function block is the result of this!
AnalogManager Description
Acronym Name Value
A1 Analog input 1 (variable) coming from selected analog parameter
A2 Analog input 2 (variable) coming from selected analog parameter
C1 Analog Constant input (constant) defined via HMI, ToolKit, or other (remote) interface
Notes
ToolKit can display input values between -9.9999e9 and

+9.9999e9. Other values will be handled correctly by the
device but display will be cropped
L1 Boolean (Logic) input 1 coming from selected digital parameter
L2 Boolean (Logic) input 2 coming from selected digital parameter
O1 Operator 1 (Operators-Unary 1) selected via HMI, ToolKit, or other (remote) interface
O2 Operator 2 (Operators-Unary 2) selected via HMI, ToolKit, or other (remote) interface
Type AnalogManager type (operation) selected via HMI, ToolKit, or other (remote) interface
BR Boolean result result/output of the boolean operation
Notes

4 Configuration
4.9.1 Operations
Acronym Name Value

Available as LogicsManager Variable ("result") e.g. as AM/LM
input
AR Analog result result/output of the analog operation
Notes
Available as AnalogManager "result" e.g. as AM input
AnalogManager Internal Values 1 to 16
Internal values within the AnalogManager analogue and logical outputs may be
programmed and used for multiple functions.
Flag {x} Value 1 Value 2 Value 3 Value 4 Value 5 Value 6 Value 7 Value 8
Parameter 9640 9644 9648 9652 9656 9660 9664 9668

ID
{yyyyy}
Description 9641 9645 9649 9653 9657 9661 9665 9669
Tab. 91: Internal Values parameter IDs (1 to 8)
Value Value 9 Value 10 Value 11 Value 12 Value 13 Value 14 Value 15 Value 16

{x}
Parameter 9672 9676 9680 9684 9688 9692 9696 9700

ID
{yyyyy}
Description 9673 9677 9681 9685 9689 9683 9697 9701
Tab. 92: Internal Values parameter IDs (9 to 16)
Default values
Factory settings of the internal values come with Type = "Pass Through" so the analog
result AR is same as analog input A1 (Default: A1 = 10.01 ZERO). The boolean result BR
is "FALSE".
[Default]
{yyyyy} AM Internal Value 2 Determined by AnalogManager The data source may be selected
{x} from the available data sources.
[A1 = 10.01 ZERO]
Notes

[Default]
{yyyyy} Internal value {x}: 2 user-defined (up 22 to characters) The text may have 0 through 22
Description characters.
[AM Internal Value {x}]

4 Configuration
4.9.1 Operations
[Default]
Notes


for each character.

The analog and/or logic result can be used via command variable 91.{x} AM Internal
value {x}.

4 Configuration
4.9.1 Operations
Examples
☼ Calculating with an AnalogManager
Fig. 201: screen shot HMI: AM subtraction sample
Acronym Name Value
A1 Analog input 1 Number: 06.01
Name: Analog Input 1
Value: 65.1252
Name: Analog Input 2
Value: 25.2360
C1 Analog constant input Value: 0
L1 Boolean input 1 Number: 02.01
Name: LM FALSE
Value: 0
Name: LM FALSE
Value: 0
O1 Operator 1 NOT [input will be inverted]
O2 Operator 2 NOT [input will be inverted]
Type Operation type SUBTRACTION
BR Boolean result (A1 - A2) x C1 > 0

(available as boolean result »91.01 AM Internal value 1«)
AR Analog result (A1 - A2) x C1

(available as analog result »91.01 AM Internal value 1«)

4 Configuration
4.9.1 Operations
☼ Incrementing and comparing with an AnalogManager
Fig. 202: screen shot HMI: AM increment sample
Acronym Name Value
Name: Internal value 3
Value: 25.0000
Name: ZERO
Value: 0
C1 Analog constant input Value: 1.000
Name: Time dependent voltage
Value: Result of LM 07.28
Name: Discrete input 7
Value: Result of LM 09.07
O1 Operator 1 L1 [passed]
O2 Operator 2 L2 [passed]
Type Operation type INCREMENT
BR Boolean result A1≧ A2 + (n[L1] x C1)*

*) Reset if L2 = TRUE
(available as boolean result »91.02 AM Internal value 2«)
AR Analog result A2 + (n[L1] x C1)*

*) Reset if L2 = TRUE
(available as analog result »91.02 AM Internal value 2«)

4 Configuration
4.9.1 Operations
The following AnalogManager operations are available:
New AnalogManager "Type" selected? Then: ...
Please be aware that the input values stay "as is" (are NOT changed) if a new Type is
selected. Check all input settings A1, A2, C1, L1, L2, O1, O2 before applying!
Example:
If C1 = 0 and you select Type »Division«, you would ask the AnalogManager to divide by
zero ...
AnalogManager Bitmap Function (Output)

Operation (Type)
Pass through Analog Result = A1
Boolean Result = L1
Constant Analog Result = C1
Boolean Result = L1
Summation Analog Result = (A1 + A2) * C1
Boolean Result goes TRUE, if Analog Result > 0
Subtraction Analog Result = (A1 - A2) * C1

4 Configuration
4.9.1 Operations

Operation (Type)
Limit Switch Analog Result = (A1 - A2)
L1 = FALSE -> Overrun mode: Boolean Result goes

TRUE, if A1 > A2 Boolean Result goes FALSE, if A1 <= (A2 -
C1)
L1 = TRUE -> Underrun mode: Boolean Result goes

TRUE, if A1 < A2 Boolean Result goes FALSE, if A1 >= (A2
+ C1)
C1 = Hysteresis
L1 = TRUE = Underrun mode, otherwise Overrun mode
L2 = Resets Hysteresis.
Compare with delay Analog Result = (A1 - A2)

on
Boolean Result goes TRUE, if A1 > A2 for the duration of C1
time [s], otherwise FALSE
C1 = Time Delay to switch on [s]
L2 = Reset Time Delay. Absolute value of C1 is taken as

time [s] (no negative time).
Notes
Time is not latched, so C1 changes can be done during

delay cycle.
Multiply Type A Analog Result = (A1 * A2) + C1
Multiply Type B Analog Result = A1 + (A2 * C1)
Multiply Type C Analog Result = A1 * A2 * C1

4 Configuration
4.9.1 Operations

Operation (Type)
Divide Analog Result = (A1 / A2) * C1
Switch Analog Result = A1, if L1 = TRUE
Analog Result = A2, if L1 = FALSE AND L2 = TRUE
Analog Result = C1, if L1 = FALSE AND L2 = FALSE
Notes
Icon shows switch positions L1/L2 as FALSE.
Common use could be to switch between A1 and A2: Set L2

= TRUE; use L1 to switch.
Maximum Analog Result = MAX(A1 , A2)
Boolean Result goes TRUE, if A1 > A2
Minimum Analog Result = MIN(A1, A2)
Boolean Result goes TRUE, if A1 < A2
In Band Analog Result = ABS(A1 - A2)
Boolean Result goes TRUE, if (ABS(A1 - A2) <= C1)
C1 = maximum tolerance for being "in band"

4 Configuration
4.9.1 Operations

Operation (Type)
Ramp Analog Result = Ramp value
Boolean Result goes TRUE, if Ramp value equal end

position
C1 determines rate/second. Absolute value of C1 is taken -

no negative rate allowed
L1 holds ramp: If L1 goes TRUE, the current ramp output is

stopped
L2 determines end value: If L2 goes TRUE, the end position

is value A2, otherwise it is A1.
Notes
Rate/second is not latched, so C1 changes can be done

during ramp cycles.
Common use could be ramp up and down: Start ramping

from A1 to A2 with gradient C1 if L1 goes TRUE; then switch
to ramping down back to A1 with the same gradient if L2
goes TRUE.
Filter Analog Result = Filtered value of A1
Boolean Result = FALSE.
A1 = Value, which is to filter. A2 not used.
C1 is filter time (time constant) in [s]
L1 switches the filter. If L1 goes TRUE, the filter function is

enabled, otherwise the filter function is disabled and the
Analog Result = A1
L2 not used. Absolute value of C1 is taken
Notes
Time constant is not latched, so C1 changes can be done

during filter cycles.
Filter formula: OUT[i] = a*IN[i] + (1-a)*OUT[i-1] , where

OUT[i] is current output, IN[i] is current input, and OUT[i-1]
is previous output. a = (dT / (C1 + dT)), where dT is interval
of input/output change (== RATEGROUP)
Increment Analog Result = Analog Result + C1 on every L1 rising edge
Boolean Result goes TRUE, if Analog Result > = Value A1

(Limit)
A1 = Limit
A2 = Start Value after RESET
C1 = Increment per Step
L1 = Trigger for Increment
L2 = Reset to Start Value

4 Configuration
4.9.1 Operations

Operation (Type)
Latch Analog Result = A1 on every L1 rising edge
A1 = Value 1
L1 = Saves Analog Result with rising edge
L2 = Resets Analog Result to 0 with rising edge
Timer Analog Result = Elapsed time [s]
Boolean Result goes TRUE, if Analog Result > = C1
C1 = Timer Compare [s]
L1 = If L1 goes TRUE, timer starts or continues to run,

otherwise timer is stopped
L2 = Resets Analog Result to 0 with rising edge
Notes
Could be used e.g., for reading out values when a defined

(failure) situation occurs
Maxtrack Analog Result = If A1 > Analog Result, the new result is A1
Boolean Result goes TRUE, if Analog Result > = C1
A1 = Tracked Value
A2 not used
C1 = Limit
L2 = Resets Analog Result to A2 with rising edge.
Mintrack Analog Result = If A1 < Analog Result, the new result is A1
Boolean Result goes TRUE, if Analog Result < = C1
A1 = Tracked Value
C1 = Limit
L2 = Resets Analog Result to A2 with rising edge.
Delay Type A Mode "Delay On":
Analog Result = Remaining time [s] for Boolean Result to go

to TRUE
Boolean Result goes TRUE, if L1 = TRUE for at least C1[s]

time.
Mode "Delay Off:
Analog Result = Remaining time [s] for Boolean Result to go

to FALSE
Boolean Result goes FALSE, if L1 = FALSE for at least

C1[ms] time
C1 = Absolute value of C1 is taken as time in [s] (no

negative time allowed)

4 Configuration
4.9.1 Operations

Operation (Type)
L1 = Switching signal. The boolean result is delayed
according to the mode in L2
L2 = TRUE = Mode "Delay Off"; = FALSE = Mode "Delay

On"
Notes

delay cycle.
Delay Type B Analog Result = Remaining time [s] to switch Boolean

Result
Boolean Result = TRUE, if L1 was TRUE for at least A1 time

[s]
Boolean Result = FALSE, if L1 was FALSE for at least A2

time [s]
A1 = Delay-On time [s], no negative time allowed
A2 = Delay-Off time [s], no negative time allowed
L1 = Switching signal. The boolean result is delayed

according to the time A1 and A2
L2 = Resets Boolean result with rising edge
Notes
A1/A2 Time is not latched, so changes can be done during

delay cycle.
Toggle Analog Result = Remaining time to switch Boolean Result
Boolean Result = Toggles with ON time = A1[ms] and OFF

time = A2[s]
A1 = Delay-On time [ms], no negative time allowed
A2 = Delay-Off time [ms], no negative time allowed
L1 = Activates toggling, if TRUE. L2 = Resets remaining

time to toggle with rising edge
Notes
A1/A2 Time is not latched, so changes can be done during

delay cycle.
One Shot Analog Result = Remaining time to fall back to FALSE [s]
Boolean Result = L1 rising edge forces TRUE state for C1

time [s]
C1 = Absolute value of C1 is taken as time in [s] (no

negative time allowed)
L1 = Activates boolean result to TRUE with rising edge
L2 = Resets remaining time for fall back with rising edge
Notes

monoflop cycle.

4 Configuration
4.9.2 AnalogManager Constants
4.9.2 AnalogManager Constants
General note
For even more flexibility and use of "self explaining" parameters 16 constants can be
defined. These constants are available as AnalogManager input AM 13.01 to AM 13.16.
Each parameter can be named individually and its value can be defined in a wide range:
AnalogManager Constants 1 to 16
AnalogManager values may be used for multiple functions.
AM 1 2 3 4 5 6 7 8
Constant
#
Description 15567 15568 15569 15570 15571 15572 15572 15574
Value 15551 15552 15553 15554 15555 15556 15557 15558
AM AM 13.01 AM 13.02 AM 13.03 AM 13.04 AM 13.05 AM 13.06 AM 13.07 AM 13.08

{xx.yy}
Tab. 93: AM Constant IDs (1 to 8)
AM 9 10 11 12 13 14 15 16
Constant
#
Description 15575 15576 15577 15578 15003 15004 15005 15006

{mmmmm}
Value 15559 15560 15561 15562 15563 15564 15565 15566

{nnnnn}
AM AM 13.09 AM 13.10 AM 13.11 AM 13.12 AM 13.13 AM 13.14 AM 13.15 AM 13.16

{xx.yy}
Tab. 94: AM Constant IDs (9 to 16)
Constant's name
The AM inputs selectable for A1 or A2 come with the predefined name of the Constant
e.g. "13.01 Free constant 1" but not with the customizable AM Description e.g. the value
of 15567 Description constant 1.
[Default]
{mmm} Description constant 2 user-defined (up 22 to characters) The text may have 0 through 22
{#} characters.
[13.yy Free constant {#}]
Notes


for each character.

4 Configuration
4.10 Configure Counters
[Default]

{nnnnn} 13.yy Free constant 2 -21000.00 e3 to 21000.00 e3 Preset value to be used as AM

{#} 13.yy.
[1]
4.10 Configure Counters

General notes
The following chapters describe all available and configurable counters of the device.
The standard/basic counters - available in all devices of this product family - are
described in the chapter ╚═▷ “4.10.1 Generator Preset Values”. For special counters
please see the chapters following.
4.10.1 Generator Preset Values
General notes
Maintenance call
A maintenance call will be issued if the configured number of maintenance hours has
expired or the configured number of days has expired since the last maintenance.
In case of a maintenance call, the display indicates "Mainten. days exceeded" or

"Mainten. hours exceeded".
[Default]
2521 Gen.pos.active 2 000000.00 to 999999.00 MWh This parameter defines the

energy preset number of MWh of the counter.
[0 MWh] The number entered here will
overwrite the current displayed
value after confirming with
2510 Gen.pos.active 2 Yes The current value of this counter

energy set is overwritten with the value
configured in "Gen.pos.active
energy preset" (parameter ╚═▷
2521). After the counter has been
(re)set, this parameter changes
back to "No" automatically.
[No] The value of this counter is not

changed.

4 Configuration
4.10.1 Generator Preset Values
2523 Gen.pos.react.energy 2 000000.00 to 999999.00 Mvarh This parameter defines the

preset number of positive Mvarh of the
[0 Mvarh] counter. The number entered here
will overwrite the current
displayed value after confirming
2511 Gen.pos.react.energy 2 Yes The current value of this counter

set is overwritten with the value
configured in
"Gen.pos.react.energy preset"
(parameter ╚═▷ 2523). After the
counter has been (re)set, this
parameter changes back to "No"
automatically.

changed.
2527 Gen.neg.react.energy 2 000000.00 to 999999.00 Mvarh This parameter defines the

preset number of negative Mvarh of the
[0 Mvarh] counter. The number entered here
will overwrite the current
displayed value after confirming
2513 Gen.neg.react.energy 2 Yes The current value of this counter

set is overwritten with the value
configured in
"Gen.neg.react.energy preset"
(parameter ╚═▷ 2527). After the
counter has been (re)set, this
parameter changes back to "No"
automatically.

changed.
2541 Number of starts 2 0 to 65535 This parameter defines the

preset number of times the control unit
[0] registers a start of the generator
set. The number entered here will
overwrite the current displayed
value after confirming with
2542 Number of starts set 2 Yes The current value of the start
counter is overwritten with the
value configured in "Number of
starts preset" (parameter ╚═▷
2541). After the counter has been
(re)set, this parameter changes
back to "No" automatically.

changed.

4 Configuration
4.10.2 Service Reset Values
General notes
Maintenance call
A maintenance call will be issued if the configured number of maintenance hours has
expired or the configured number of days has expired since the last maintenance.
In case of a maintenance call, the display indicates "Mainten. days exceeded" or

"Mainten. hours exceeded".
Displaying hours: operation / period of use
The easYgen device handles operating hours internally in floating format. To indicate the
operating hours on a display or to provide it in the data protocol the value is transferred
into an integer variable. This can cause display errors within 4*10-6 % in relation to the
absolute value.
[Default]
2550 Maintenance hours 2 0 to 9,999 h This parameter defines the

remaining hours until the next
[300 h] maintenance call occurs. Once the
generator has been operated for
the number of hours configured
here, a maintenance message is
displayed.
If this value is changed, the

counter is reset to the new value.
If the maintenance counter is

reset by the push-buttons at the
front panel (refer to ╚═▷ “2.1
Display And Status Indicators”), or
by configuring the parameter
"Reset maintenance period hrs" to
"Yes" (parameter ╚═▷ 2562), the
maintenance counter is reset to
the configured value.
Notes
To disable the "maintenance

hours" counter configure "0" for
this entry.
2562 Reset maintenance 2 Yes / No If this parameter is configured to

period hrs "Yes" the maintenance "hours"
[No] counter is reset to the configured
value. Once the counter
"maintenance hours" has been
reset, the control unit changes
this parameter to "No".
Notes

4 Configuration
When using a specific code level

in parameter ╚═▷ 2567 to reset
maintenance hours this parameter
can be blocked.
Notes
- menu path:
[Next page / Configure counters /
(symbol: wrench)]
2551 Maintenance days 2 0 to 999 d This parameter defines the

remaining days until the next
[365 d] maintenance call occurs. Once the
configured number of days has
expired since the last
maintenance, a maintenance
message is displayed.
If this value is changed, the

counter is reset to the new value.
If the maintenance counter is

reset by the push-buttons at the
front panel (refer to ╚═▷ “2.1
Display And Status Indicators”), or
by configuring the parameter
"Reset maintenance period days"
to "Yes" (parameter ╚═▷ 2563),
the maintenance counter is reset
to the configured value.
Notes
To disable the "maintenance days"

counter configure "0" for this
entry.
2563 Reset maintenance 2 Yes / No If this parameter is configured to

period days "Yes" the "maintenance days"
[No] counter is reset to the configured
value. Once the counter has been
reset, the control unit changes
this parameter to "No".
Notes
When using a specific code level

in parameter ╚═▷ 2567 to reset
maintenance days this parameter
can be blocked.
Notes
- menu path:
[Next page / Configure counters /
(symbol: wrench)]

4 Configuration
2567 Code level for reset 2 This parameter determines the

maint. required code level for resetting
the counter "Maintenance call
in...". User with a lower code level
may not access this function.
The following code levels exist:
0 Operator
1 Service level
[2] Temporary commissioner
3 Commissioner
Notes
The code level defined here only

affects the access via the front
panel (HMI).
15154 Operation hours 2 This parameter configures the

source source for the operation hours.
[Internal]
The operation hours are counted
internal from the easYgen
ECU/J1939 The operation hours are assumed

from the connected ECU (via
J1939 CAN protocol).
2509 Operation hours 0 0 to 999,999.99 When setting the operating hours

preset counter (refer to parameter ╚═▷
[0] 2574), the counter always will be
set up to the value configured
here.
2574 Operation hours set 01 Yes The current value of this counter
is overwritten with the value
configured in "Operation hours
preset" (parameter ╚═▷ 2509).
After the counter has been (re)set,
this parameter changes back to
"No" automatically.

changed.
Notes
1 The code level can be configured

with "Codelevel set operation
hours" (parameter ╚═▷ 2573). If
your current code level does not
match, this parameter is not
visible.
2573 Code level set 5 0 to 5 This parameter defines which

operation hours codelevel is necessary to set the
[2] operation hours (parameter ╚═▷
2574).

4 Configuration
2515 Period of use preset 2 0 to 999,999.99 When setting the period of use
hours counter (refer to parameter
[0] ╚═▷ 2579), the counter always will
be set up to the value configured
here.
2579 Period of use set 01 Yes The current value of this counter
is overwritten with the value
configured in "Period of use
preset" (parameter ╚═▷ 2515).
After the counter has been (re)set,
this parameter changes back to
"No" automatically.

changed.
Notes
1 The code level can be configured

with "Code level f. set period of
use" (parameter ╚═▷ 2581). If
your current code level does not
match, this parameter is not
visible.
2581 Code level f. set 5 0 to 5 This parameter defines which

period of use codelevel is necessary to set the
[2] period of use hours (parameter
╚═▷ 2579).

5 Operation
5 Operation
In operation the genset controller can be manually or remote controlled.
Front panel access is described in chapter ╚═▷ “4.1 Front Panel Access”.
Access via ToolKit is described in the ToolKit Manual.
Access via Remote Panel PR-3000XT is described in chapter ╚═▷ “4.3.6 Configure Remote
Panel Mode” and the Technical Manual »37593 RP-3000XT«.
Access via PLC depends on the interface and the data telegram used for communication.
For menu structure/menu tree see ╚═▷ “Menu structure (menu tree)”.
5.1 Power ON
Behavior during starting easYgen-3000XT
The start-up procedure of the easYgen-XT device can be caused by the following reasons:
• Power ON
• Power cycling e.g. by ╚═▷ 1701» Set factory default values«
• Power is back after voltage drop
This process is visualized by the HMI of the plastic housing version or the LEDs of the
metal housing version.
Using the USB Service Port
With power ON and a PC/laptop connected via USB service port it can happen that the
USB window that pops up doesn't show all files and/or the correct available free memory
at the device: Please unplug/plug the USB connection after the easYgen finished starting.
With power ON and connected USB service port it can happen that a connected USB
device is not detected correctly: Please unplug/plug the USB connection after the
easYgen finished starting.
With power cycle or reboot of the easYgen-XT the USB connection is lost: Please unplug/
plug and/or start USB connection again after the easYgen finished starting.
... starting plastic housing (HMI) version
Power ON from zero power
• Buttons are illuminated
• Start-up screen appears
◦ the red bar at the bottom monitors the degree of fulfillment
• HOME screen appears with measured values and state information

5 Operation
5.2 Change Operating Modes
◦ Illumination of buttons is disabled according to the default settings STOP button

still might be illuminated
◦ WARNING triangle is blinking if there are unacknowledged alarm messages
Power cycling
• Warning LED is twinkling in a high frequency
• (afterwards the standard process of Power ON is executed:)
• Buttons are illuminated
• Start-up screen appears
◦ the red bar at the bottom monitors the degree of fulfillment
• HOME screen appears with the same measured values and state information as
before power cycling
... starting metal housing version
Power ON from zero power
• LEDs are twinkling
• LEDs are illuminated according to the state of the genset control
Power cycling
• Warning LED is twinkling in a high frequency
• (afterwards the standard process of Power ON is executed:)
• LEDs are twinkling
• LEDs are illuminated according to the state of the genset control
5.2 Change Operating Modes

Startup
The genset controls starts in the operating mode defined by parameter 1795 »Startup in
mode«. Refer to ╚═▷ “4.4.5 Configure Operation Modes” for details.
Select Operation Mode
Operation modes can be selected via
• front panel buttons (plastic housing variant or Remote Panel RP-3000XT or VNC
client),
• HMI configuration (plastic housing variant or Remote Panel RP-3000XT or VNC client),
• remote settings via interfaces, or
• ToolKit
The following chapters describe the manually front panel access.

5 Operation
5.2.1 Operating Mode STOP
5.2.1 Operating Mode STOP
Usage
1. ▷ Use the STOP button to activate operating mode STOP.
Observe the notes on the system's reaction upon activation of operating

mode STOP as listed below.
▶ STOP LED is illuminated at the front panel; ToolKit home page shows STOP icon left
beside the prime mover.
System reaction
In operating mode STOP neither the engine nor the GCB can be operated. Dependent on
the application mode the power circuit breakers cannot be operated.
CAUTION!
Hazards due to improper use of operating mode STOP
Selecting the operating mode STOP is not the same as an EMERGENCY STOP.
In some cases the easYgen will perform additional logic functions, such as an engine cool
down period, before the engine is stopped.
• For emergency stop functionality use an EMERGENCY STOP discrete input,

programmed as an F class alarm.
If the operating mode STOP is selected while the engine was already stopped the
following applies:
• The GCB will not be closed.
• The fuel solenoid relay will not be enabled.
• The start request is ignored.
• The start push buttons (softkeys) are disabled.
• The engine/generator monitoring remains activated (exception: all monitoring that is

delayed by the engine speed).
If the operating mode STOP is selected while the engine was running the following
applies:
• Dependent on the current application mode a soft shut down will be executed.
• Pressing the STOP button again opens the GCB.
• If the STOP button is pressed again, the cool down will be interrupted.

5 Operation
5.2.2 Operating Mode MANUAL
If the operating mode STOP is selected while the engine performs a cool down the
following applies:
• Pressing the STOP button again causes an immediate stop of the cool down and
stops the engine.
If the conditions of the LogicsManager function "Enable MCB" (parameter ╚═▷ 12923) are
TRUE, the MCB will be closed again if it is open in STOP operating mode.
General usage
In the MANUAL operating mode (mode button »MAN« illuminated) both the engine circuit
breaker and the power circuit breaker can be operated via the push buttons along the
bottom of the display (softkeys). Additionally the Start(I)/Stop(O) buttons can be used to
start or stop the engine.
Fig. 203: XT_MAN-buttons
1 Mode button: MAN
2 START button: Engine
3 STOP button: Engine
4, 6 Soft buttons: Breaker OPEN/CLOSE
5 Soft button not used

5 Operation
1. ▷ Use the mode button »MAN« to activate operating mode MANUAL.
▶ The MAN button is illuminated
NOTICE!
The breakers will open immediately without power reduction.
To open the breaker in a no-load condition, reduce the load manually in the setpoints
screen (╚═▷ “4.1.5 Specialized Menu Screens”).
Example for application mode A01
ᐳ To start the engine:

1. ▷ Press the button »I« below the MAN button.
▶ Success: The engine starts and the circular arrow and the eye symbol appear.
Failure: No change in the display until the "start failure" message appears.
ᐳ To stop the engine:

1. ▷ Press the button »0« right below the MAN button.
▶ Success: The engine stops and the circular arrow and the eye symbol disappear.
Failure: No change in the display until the "stop failure" message appears.
Overview
Function Status Symbol Available in application mode
A01 A02 A03 A04
Start the engine ✔ ✔ ✔ ✔
Stop the engine ✔ ✔ ✔ ✔
Breaker open command ✔

is issued or a closure of
the breaker is blocked
No defined breaker ✔
state

5 Operation
5.2.3 Operating Mode AUTOMATIC
Function Status Symbol Available in application mode
A01 A02 A03 A04
Open the GCB ✔ ✔
Close the GCB ✔ ✔
Open the MCB ✔
Close the MCB ✔
Symbol Description
Generator or mains rotating field moves clockwise.
Generator or mains rotating field moves counter-clockwise.
Power is detected at the respective measuring point (generator, busbar, or

mains).
Indicates that the engine delayed monitoring has expired and the monitoring
functions are enabled.
Power is imported (at mains interchange).
Power is exported (at mains interchange).
Tab. 95: Status symbols
5.2.3 Operating Mode AUTOMATIC
General usage
In the AUTOMATIC operating mode (»AUTO«), all engine, GCB, and/or MCB functions are
operated via an interface, or automatically by the control unit (i.e. a mains failure).
The function of the easYgen depends on the configuration of the unit and how the
external signals are used.
1. ▷ Use the button »AUTO« to activate operating mode AUTOMATIC.
▶ If mode change was successful the button »AUTO« is illuminated.
For a more detailed description of the start/stop sequence of the engine and the
associated parameters refer to ╚═▷ “4.4.5.2 Operation Mode AUTO - Automatic Run”.
The main functions are briefly described in the following sections.

5 Operation
5.2.4 Operating Mode TEST
Start engine
The engine is started via a remote start signal.
Prerequisites:
• The AUTOMATIC operating mode is enabled.
• The start request is enabled by the LogicsManager "Start req. in AUTO".
• No shut down alarm is present. (for explanation of the alarm classes refer to ╚═▷
“9.5.4 Alarm Classes”).
• The engine is ready for operation.
• The GCB is open.
Auto mains failure operation (AMF)
Auto mains failure operation is only available in application mode A04 .
If the AUTOMATIC operating mode is enabled and the mains fail, the engine and the
power circuit breakers will be operated according to the current application mode.
Prerequisites:
• The AUTOMATIC operating mode is enabled.
• The parameter "Emergency power" is configured to "On".
• The configured mains failure limits are reached.
• The configured delay times have expired.
• No shut down alarm is present. (for explanation of the alarm classes refer to ╚═▷
“9.5.4 Alarm Classes”).
• The engine is ready for operation.
General usage
The operating mode (»TEST«) usually is a temporary operating mode. The idea is to test
the genset.
TEST operating mode always starts the engine, when changing into this mode
independent on an AUTOMATIC start order. Additionally the TEST operating mode
supports the emergency and critical run as well (if a mains failure occurs during the test
run). The operating mode TEST supports different sub modes so the operator can choose
if the breakers shall be closed during test run or whether the operating mode is changed
after the test run.

5 Operation
The function of the easYgen depends on the configuration of the unit and how the
external signals are used.
1. ▷ Use the button »TEST« to activate operating mode TEST.
▶ If mode change was successful the button »TEST« is illuminated.
The illumination of the button becomes twinkling a short time before TEST
run is over.
For a more detailed description of the start/stop sequence of the engine and the
associated parameters refer to ╚═▷ “4.4.5.3 Operation Mode TEST”.
The main functions are briefly described in the following sections.

5 Operation
5.3 Restore Language Setting via HMI, Buttons and Softkeys
5.3 Restore Language Setting via HMI, Buttons and Softkeys
ᐳ In order to change the language setting via HMI, press the (soft)keys in the following
order:
Language parameter is on code level "0", so the instruction will work with
each code level.
Fig. 204: Front panel and display
1. ▷ Press button »HOME« once to return to the start screen

2. ▷ Press softkey »6« once to access the "Parameter" screen
3. ▷ Press softkey »3« once to access the "Configure language / clock" screen
4. ▷ Press softkey »7« once to edit the language setting
5. ▷ Press softkeys »11« or »12« to select the desired language.
6. ▷ Press softkey »7« once to commit the language setting.
▶ The desired display language is restored.

6 Application Field
6 Application Field
Device status
The following applications are described for devices with status "factory settings". This is
mandatory because parameters not changed during sample setup may have influence to
the devices' behavior!
Live test requirement
If you want to use the same setup as described with the sample, please ensure factory
settings status of the device before changing it.
Otherwise you have to take care that the changes you did before do not "disturb" sample
settings!
Application Modes
For application modes overview see chapter ╚═▷ “2.2 Application Modes Overview”.
6.1 Basic Applications
6.1.1 Application Mode A01 (None)
This application mode ( A01 ) may be used, where the breaker control is done external. In
this case, the easYgen will function as an engine control with generator and engine
protection. The control does not operate any breaker. Emergency mode (AMF operation) is
not supported in this application mode.

6 Application Field
6.1.1 Application Mode A01 (None)
Fig. 205: Application mode A01 (schematic)
The easYgen requires the feedback reply from GCB and MCB in this application mode.
These replies are used to define, whether the easYgen controls frequency, shares the
load with other gensets or performs active load control.
The following feedback signals are used in this application mode and fixed to the
respective discrete inputs:
• DI 7 "Reply MCB" (mains parallel)
• DI 8 "Reply GCB" (normally closed (break) contact)

Engine operation in AUTOMATIC (basic function)
Engine starts, if
• The LogicsManager "Start req. in AUTO" is fulfilled (TRUE) AND
• A shut down alarm is not present AND

6 Application Field
6.1.2 Application Mode A02 (GCB open)
• The engine is ready for operation
Engine stops, if
• The reply GCB is open AND the LogicsManager "Start req. in AUTO" is not fulfilled
(FALSE) OR
• A shut down alarm occurs
Being parallel to mains or to other generator, the generator power will be reduced before.
Refer to ╚═▷ “4.4.5.2 Operation Mode AUTO - Automatic Run” for details.
This application mode ( A02 ) may be used for islanded operation applications.
In this case, the easYgen will function as an engine control with generator and engine
protection. The control unit can only open the GCB. Emergency mode (AMF operation) is
not supported in this application mode.

6 Application Field

6 Application Field
6.1.3 Application Mode A03 (GCB)
The following feedback signals and commands are used in this application mode and
fixed to the respective discrete inputs and outputs:
• DO 7 "Command: GCB open"

Engine starts, if
With successful start the GCB closure is released.
Engine stops, if
• The reply GCB is open AND the LogicsManager "Start req. in AUTO" is not fulfilled
(FALSE) OR
Being parallel to mains or to other generator, the generator power will be reduced before.
This application mode ( A03 ) may be used in applications, where only the GCB is operated
by the easYgen.
If it is used for islanded or mains parallel operations, mains decoupling should be

performed by the GCB or an external provision.
The easYgen will function as an engine control with generator and engine protection. The
control unit can open and close the GCB. Emergency mode (AMF operation) is not
supported in this application mode.

6 Application Field
• DO 6 "Command: GCB close"

6 Application Field
6.1.4 Application Mode A04 (GCB/MCB)
• DO 7 "Command: GCB open" (optionally)

Engine starts, if
With successful start the GCB closure is executed.
• If the voltage of generator and generator busbar is in range, the GCB will be
synchronized
If the voltage of generator is in range, and the generator busbar is dead, and no other
GCB is closed, and the MCB is closed the GCB will not be closed but an »operating
range failure« occurs.
Engine stops, if
• The LogicsManager "Start req. in AUTO" is not fulfilled (FALSE) OR
Being parallel to mains or to other generator, the generator power will be reduced, before
the GCB will be opened.
This application mode ( A04 ) may be used for mains parallel operation. In this case, the
easYgen will function as an engine control with generator, mains and engine protection.
The control unit can open and close the GCB and the MCB. The breaker transition modes
“Open Transition”, “Closed Transition”, “Interchange” and “Parallel” are possible.
The Emergency mode (AMF operation) is supported in this application mode.

6 Application Field
The easYgen requires the feedback reply from both circuit breakers in this application
mode. These replies are used to define, whether the easYgen controls frequency, shares
the load with other gensets or performs active load control.
• DO 6 "Command: GCB close"

6 Application Field
• DO 7 "Command: GCB open" (optionally)
• DO 8 "Command: MCB close"
• DO 9 "Command: MCB open"
Engine starts, if
According to the current active breaker transition mode the GCB and MCB will be
operated.
Engine stops, if
• The LogicsManager "Start req. in AUTO" is not fulfilled (FALSE) OR
operated.
Auto mains failure operation (AMF) in AUTOMATIC (basic function)
Engine starts, if
• The configured mains failure limits are reached AND
With successful start the MCB will be opened and the GCB will be closed.
Engine stops, if
• The mains values are back in range AND
• The mains settling time is expired
operated.

6 Application Field
6.2 Multiple Genset Applications
6.2 Multiple Genset Applications

Overview
In a multiple-unit mains parallel application, all easYgens need the same signals for:
• Mains voltage and current
• Reply and release signal of the MCB
The open and close contacts from all controls must be wired in parallel.
MCB Control
Voltage (3Ph)
Voltage (3Ph)
Voltage (3Ph)
Current (1Ph)
Current (1Ph)
Current (1Ph)
Open/Close
Open/Close
Open/Close
LOAD LOAD
Optional
Voltage (3Ph) Voltage (3Ph) Voltage (3Ph)
PLC GCB Control

easYgen-3000XT
GCB Control
easYgen-3000XT
GCB Control
easYgen-3000XT
Current (3Ph) Current (3Ph) Current (3Ph)
Voltage (3Ph) Voltage (3Ph) Voltage (3Ph)
MPU/ECU MPU/ECU MPU/ECU
Dis./Analog Inputs Dis./Analog Inputs Dis./Analog Inputs
Engine Start/Stop Engine Start/Stop Engine Start/Stop

Modbus RTU/Ethernet
CAN bus / Modbus TCP
Fig. 209: Multiple genset application (schematic)
6.2.1 Configuration Example: Multiple Genset
Configuration example
The following example describes the configuration of a typical mains parallel operation
with import/export power control at the interchange point and load-dependent start/stop.

6 Application Field
6.2.1.1 Configuring Load-Dependent Start/Stop
Multiple generators are to be operated in parallel to the mains maintaining a stable power
at the interchange point. The generators shall be started depending on the momentary
load at the plant. An emergency operation in case of a mains failure is also intended.
The load dependent start/stop function (LDSS) shall be enabled with a remote start
request. LDSS shall depend on the reserve power on the busbar. In case of a dead busbar
(caused by a mains failure) all capable generators shall be started and operated with
their minimum running time.
No generator priority is considered. Generator selection shall be performed depending on

the operating hours.
The following assumptions are valid for the example:
• 3 generators, each with 80 kW rated power, are available.
• The recommended minimum load for the generators is 40 kW.
• The minimum running time is 180 s.
1. ▷ Either on the front panel or using ToolKit navigate to menu [ Parameter / Configuration /
Configure application / Configure application modes / Load dependent start/stop /
General LDSS settings].
2. ▷ Configure the parameters below.
ID Parameter Value Comment
5752 Start stop Reserve The reserve power at the interchange point is to be
mode power considered for LDSS
5753 Dead All All generators shall start in case of a dead busbar (mains
busbar failure)
start mode
5751 Base 5 The base priority for the genset is 5

priority
5754 Fit size of No The generator rated power is not considered for LDSS
engine
5755 Fit service Equal The remaining hours until next service are considered for
hours LDSS
5756 Changes of Off No engine change will be performed

engines
5777 LDSS sort Off LDSS priority follows settings without permanently
priority refreshing.
always
5759 Minimum 180 s The minimum running time is 180 seconds

running
time
12930 LD start LM 86.86: Enables function LDSS

stop TRUE
Tab. 96: General LDSS parameters

6 Application Field
3. ▷
Fig. 210: LogicsManager function "LD start stop"
Configure the LogicsManager 86.86 function »12930 LD start stop« as shown in (╚═▷
“6.2 Multiple Genset Applications”) to enable LDSS if a start request in automatic
operating mode or emergency mode are enabled.
LDSS parameters for mains parallel operation
Additional assumptions are valid for mains parallel operation (MOP):
• The first generator is only started if it is able to operate at a minimum load of 40 kW.
• A hysteresis of 20 kW is required to avoid frequent starts and stops.
• A reserve power of 10 kW on the busbar shall be maintained, i.e. at least 10 kW of

generator capacity are available for short load peaks.
Higher load peaks are supported by the mains.
• The delay for adding another generator shall be 30 seconds.
• The delay for adding another generator shall be reduced to 10 seconds if a

generator at the busbar is operating above its rated load (accelerated start of the
next generator).
• The delay for removing a generator from the busbar shall be 60 seconds.
1. ▷ Either on the front panel or using ToolKit navigate to menu [ Load dependent start/stop /
Mains parallel operation].
2. ▷ Configure the parameters listed below.
5767 MOP 40 kW The minimum load in mains parallel operation is 40 kW

Minimum
load
5769 MOP 20 kW The reserve power hysteresis in mains parallel operation is

Hysteresis 20 kW
5768 MOP 10 kW The reserve power in mains parallel operation is 10 kW

Reserve
power
5772 MOP Add 30 s The add on delay in mains parallel operation is 20 seconds
on delay
5773 MOP Add 10 s The add on delay at rated load in mains parallel operation
on delay at is 10 seconds
rated load

6 Application Field
5774 MOP Add 60 s The add off delay in mains parallel operation is 60 seconds
off delay
Tab. 97: Parameter configuration for LDSS (MOP)
LDSS parameters for islanded operation
Additional assumptions are valid for islanded operation (IOP), i.e. in case of an mains
failure (emergency) operation:
• A reserve power of 80 kW on the busbar shall be maintained, i.e. at least 2

generators are available in islanded operation for redundancy because no supporting
mains are present.
• A hysteresis of 20 kW is required to avoid frequent starts and stops.
• The delay for adding another generator shall be 10 seconds.
• The delay for adding another generator shall be reduced to 3 seconds if a generator
at the busbar is operating above its rated load (accelerated start of the next
generator).
• The delay for removing a generator from the busbar shall be 180 seconds.
1. ▷ Either on the front panel or using ToolKit navigate to menu [Parameter / Configuration /
Configure application / Configure application modes / Load dependent start/stop /
islanded operation].
5760 IOP 80 kW The reserve power in islanded operation is 80 kW

Reserve
power
5761 IOP 20 kW The reserve power hysteresis in islanded operation is 20

Hysteresis kW
5764 IOP Add on 10 s The add on delay in islanded operation is 10 seconds

delay
5765 IOP Add on 3s The add on delay at rated load in islanded operation is 3
delay at seconds
rated load
5766 IOP Add off 180 s The add off delay in islanded operation is 180 seconds
delay
Tab. 98: Parameter configuration for LDSS (IOP)

6 Application Field
6.2.1.2 Configuring Automatic Operation
6.2.1.2 Configuring Automatic Operation
1. ▷ Either on the front panel or using ToolKit navigate to menu [PARAMETER / Configuration /
Configure application / Configure operation modes / Operation mode AUTO].
2. ▷
Fig. 211: LogicsManager function "Start req in AUTO"
Configure the LogicsManager 86.90 function »12120 Start req in AUTO« as shown in
(╚═▷ Fig. 211) to start the generator in Automatic operating mode if discrete input [DI
02] ("09.02 Discrete input 2") is energized or a remote start request ("04.13 Remote
request" = start via interface) is issued.
6.2.1.3 Configuring Emergency Operation
Configure emergency operation to be initiated if the mains fails for at least 3 seconds or
the MCB cannot be closed.

2802 On/Off On Emergency operation is enabled
2800 Mains fail 3.00 s Emergency operation is initiated if the mains fail for a t
delay time least 3 seconds
3408 Emerg. Yes Emergency operation is initiated if the MCB fails to close
start with
MCB failure
Tab. 99: Parameter configuration for emergency run
See ╚═▷ “4.4.6 Emergency Run” for further settings possibilities.

6 Application Field
6.2.1.4 Configuring Power Control
6.2.1.4 Configuring Power Control
Configure the power controller to use the internal power setpoint 1, which must be set to
0 kW import power.
1. ▷ Either on the front panel or using ToolKit navigate to menu [Configure load control].
2. ▷ Configure the parameters listed below .
5539 AM Determined The internal power setpoint 1 is used as load setpoint 1

ActPower by
SP1 [kW] AnalogManager
81.05: [A1
= 05.54.
Internal P
setp1
[kW]]
5526 Load Import The internal power setpoint 1 is a import power value
setpoint 1
5520 Int. load 0 kW The internal power setpoint 1 is configured to 0 kW

control
setpoint 1
Tab. 100: Parameter configuration for import/export power control
6.2.2 Communication Management
6.2.2.1 System Update
General notes
The Communication Management gives an overview of all devices on the load share bus
in the system with regard to their different interfaces (Ethernet and CAN). See screen ╚═▷
Fig. 213).
Additionally it provides functions to monitor the communication members and the

interface. The monitor not only detects missing members, it also monitors a defined and
stored constellation with the current constellation for deviations. This function is
called »System Update«.
For a better understanding some expressions needs to be explained.
System update expressions and their meaning:
• »System Update« or »System Update function«:
Is the overall procedure that, if triggered, saves after 30 seconds the actual
constellation of members.
• »System Update order«:
Triggers the System Update function. ╚═▷ “How to initiate a system update”

6 Application Field
6.2.2.1 System Update
• »System Update delay timer«:
A timer of 30 second that starts after the System Update order was triggered.
• »System Update active«:
This flag is active while the System Update delay timer is running.
• »System Update monitoring«:
After the System Update function was triggered and is finished, the saved
constellation is monitored in regards of any change.
• »System Update alarm«:
Occurs if an additional device is recognized that does not exist in the actual saved
constellation. See Alarmlist for more details.
• »Missing Member alarm«:
Occurs if a device is not recognized but exists in the actual saved constellation. See
Alarmlist for more details.
With the System Update order, a delay timer of 30 seconds is triggered and will be sent to
all other members on the load share and control bus. During this time the System Update
and missing member monitoring is disabled to not interrupt a well working plant by
upcoming alarm messages and control reactions on them due to shutting down a device
for maintenance. Short before the delay timer ends, the System Update function saves
the actual constellation of recognized devices.
During the delay time the LogicsManager flag 04.65 System update active is active.
NOTICE!
A change of the device ID or of parameter »9924 Load share interface« will reset the
saved constellation and a new System Update order needs to be triggered.
After the System Update function is finished, the saved constellation will be monitored.
Any deviation to this constellation will be recognized and noticed by an alarm that
describes the type of change.
A missing member alarm is shown if a device, of the saved constellation, is not

recognized anymore. If an additional device is recognized, that does not exist in the
saved constellation, a System Update alarm is shown, see ╚═▷ “System update
expressions and their meaning:”
Each Alarm is also available as flag for the LogicsManager system.
To configure the »System update« Monitoring see ╚═▷ “4.5.6.18 Multi-Unit System
Update”:
By default the Missing Member alarm is incorporated into the frequency droop
LogicsManager ╚═▷ 12904.

6 Application Field
6.2.2.2 Diagnostic Screens
Diagnostic screens
The easYgen-XT provides several overview screens to check all members on the load
share and control bus to help trouble shooting. These screens should be watched, before
the system update order is executed. They are located under [Status Menu / Next page /
Multi-unit / Diagnostic devices].
For more details see ╚═▷ “6.2.2.2 Diagnostic Screens”.
Availability
The system update function is available for all choices of »9924 Load share interface«:
• Communication over CAN 1 bus
• Communication over Ethernet network A
• Communication over redundant CAN 1 bus and Ethernet network A
How to initiate a system update
The system update order can be initiated with the following options:
• By Softkey button »Syst. upd.« in the HMI. Navigate to [Next page / Multi-unit /
Diagnostic Devices]
• By ToolKit switch ╚═▷ 13356 »System update«. Navigate to [Status Menu / Multi-
unit / Diagnostic easYgen]
• By LogicsManager 86.35 with parameter ╚═▷ 7801 »System update«. Navigate to

[Parameter / Configure Monitoring / Multi-unit functions]
NOTICE!
Please ensure, if you are using the LogicsManager »7801 System update« or the
parameter »13356 Syst. upd«., that the signal goes false after executing. Otherwise, all
buttons relating to system update are locked.
The actual constellation of all members on the load share and control bus is displayed on
the according diagnostic screens in HMI and ToolKit.
The diagnostic screens are helping the operator to recognize the current communication
state of the load share and control bus. These screens should be reviewed before
executing a system update order. It is highly recommended to review the diagnostic
screen of each device that is participating on the load share/control bus. The system
update function will save exactly the states which are displayed in these screens.
In case of a missing member or system update alarm, these screens will also help the
operator to detect the root cause and for general troubleshooting.
The status of each device in the system will be indicated by a status ”LED“ in conjunction
with a status text.

6 Application Field
Load Share Gateways (LSG) will be shown in the diagnostic screens as easYgen devices.
Diagnostic Screen Parameter
[Default]
7801 System update 2 Determined by LogicsManager To select logical input(s) to cause

86.35 a system update.
[(0 & 1) & 1]
= 11974
13356 System update 2 Yes Network is checked for members

and its states. Updated results
(HMI: Syst. upd.) become new status.
[No] Check and update is disabled.
9925 Monitored easYgen -/- Latest result of members count Result of members count driven
by system update parameter
13356.
9951 Valid easYgen -/- Actual count of valid devices Actual count of devices that has
devices sent valid data.
Tab. 101: Parameter: Diagnostic Screens
All Diagnostic Screen Parameters are accessible via communication interfaces. The
system update command can be initiated through a free control flag.
Diagnostic screens in the HMI
Fig. 212: Diagnostic screen example (HMI)
The HMI diagnostic screen shows, additional to the Status of each device, the number of
Monitored devices and the »System Update« Button to activate the System Update order,

6 Application Field
see ╚═▷ Tab. 101. While the System Update is active, the Event indication will
show »System Update«.
Because of space restrictions on the display, the status text of each device is realized
with symbols. Use ToolKit for text indications.
Diagnostic screens in ToolKit
Fig. 213: Diagnostic screen example (ToolKit)
The ToolKit diagnostic screen shows, additional to the Status of each device, the number
of »Monitored devices«, the number of »Valid devices« and the ╚═▷ 13356 »System
update« to activate the System Update order, see ╚═▷ Tab. 101. While the System
Update is active, the remaining time will be shown. An active System Update Alarm is
also shown by the »System Update Layer 1« LED.

6 Application Field
It is possible, that several system status messages are active at same time. So the
indication is prioritized:
• Unit not recognized (highest priority)

• Add device
• Only NW X
• Not installed
It is possible, that several system status are causing different LED messages. So the
indication is prioritized:
• Red LED (highest priority)

• Yellow LED
• Black (off) LED
Diagnostic symbolic for single bus topology
Single bus topology means there is no redundant bus topology in use. Single bus
topologies are load share over CAN bus or a single Ethernet network.
System and Control bus
(CAN or single Ethernet)
LED ToolKit: easYgen: Explanation
displayed text HMI
Unit available This device is recognized and monitored with the missing
member monitor according to the latest System Update
GREEN order.
Add Device This device is recognized but not registered according to the
latest system update order. Therefore, the missing member
YELLOW monitoring does not observe the device.
System update is required!
Unit not recognized This device is not recognized according to the latest system
update order. (Missing Member Alarm)
RED
Not installed This device is neither recognized nor registered through the
latest system update order.
BLACK
Unit not recognized / This only applies to the own device. There is no other device
( / )
Not installed recognized according to the latest system update. Therefore
this unit is suspected to have an interface error as it does not
RED / BLACK
(twinkling) (twinkling) see any device on the bus.
(twinkling)
Diagnostic symbolic for redundant bus topologies
Redundant bus topology like CAN/Ethernet A to provide more safety in regards of load
share communication.

6 Application Field
6.2.2.3 Practicing the System Update Functionality
System and Control bus
(Redundant CAN/EthernetA)
LED ToolKit: easYgen: Explanation
displayed text HMI
Unit available This device is recognized and monitored with the missing
member monitor according to the latest System Update
GREEN order.
Add Device This device is recognized but not registered according to the
latest system update order. Therefore, the missing member
YELLOW monitoring does not observe the device.
System update is required!
Only NW CAN This device is not recognized on the Ethernet A bus according
to the latest system update. Therefore, a Redundancy Lost
YELLOW Alarm is triggered.
Only NW CAN / Not This only applies to the own device. There is no other device
installed recognized on the Ethernet A bus according to the latest
YELLOW / system update. Therefore this unit is suspected to have an
(twinkling) (twinkling) interface Ethernet A error as it does not see any device on
BLACK
Ethernet A. A Redundancy Lost Alarm is triggered.
(twinkling)
Only NW A This device is not recognized on the CAN bus according to

the latest system update. Therefore, a Redundancy Lost
YELLOW Alarm is triggered.
Only NW A / Not This only applies to the own device. There is no other device
installed recognized on the CAN bus according to the latest system
YELLOW / update. Therefore this unit is suspected to have a CAN
(twinkling) (twinkling) interface error as it does not see any device on the CAN. A
BLACK
Redundancy Lost Alarm is triggered.
(twinkling)
Unit not recognized This device is not recognized according to the latest system
update order. (Missing Member Alarm)
RED
Not installed This device is neither recognized nor registered through the
latest system update order.
BLACK
Unit not recognized / This only applies to the own device. There is no other device
( / )
Not installed recognized according to the latest system update. Therefore
this unit is suspected to have an interface Ethernet A and
RED / BLACK
(twinkling) (twinkling) CAN error as it does not see any device on the bus. A
(twinkling) Redundancy Lost Alarm is triggered.
6.2.2.3 Practicing the System Update Functionality
⚙ Commissioning
1. ▷ If the devices are connected to a network system, during the first commissioning it is to
observe in the diagnostic screens, whether all devices are recognized. Additional to that

6 Application Field
6.3 Special Applications
the sum of all easYgens devices must match the number shown at parameter »9951
Valid easYgens devices«, see ╚═▷ Tab. 101.
If all these conditions are fulfilled the system update order can be executed. If any
condition is not fulfilled do trouble shooting before you hit any system update order.
NOTICE!
It is highly recommended to verify the diagnostic screen of each device in

the system.
2. ▷ Executing system update order

▶ After 30 seconds all devices must be indicated with a green lamp in the diagnostic
screens. The sum of all easYgens devices must match the number shown at
parameter »9925 Monitored easYgens« and »9951 Valid easYgens devices«.
⚙ Adding a device to an already running and commissioned network
1. ▷ Connect the additional device onto the network.

2. ▷ Check the availability in the diagnostic screen. The new device is indicated by a yellow
LED and with status text »Add device«.
3. ▷ Execute the system update order
▶ After 30 seconds all devices must be indicated with a green lamp in the diagnostic
screens. The sum of all easYgens devices must match the number shown at
parameter »9925 Monitored easYgens« and »9951 Valid easYgens devices«.
⚙ Removing a device from an already running and commissioned network
1. ▷ Execute the system update order
If you are removing the device before you hit the system update order, it is
important to know that it will come to a missing member alarm with the
consequence that the system goes into a droop function (if configured). If
that has happened, this issue can be solved by a system update order. But
do not forget to make a system check via the diagnostic screens.
2. ▷ You have now 30 seconds time to remove the device, without getting any consequences
on the system
6.3 Special Applications
6.3.1 Generator Excitation Protection
The easYgen controller provides the user with power factor monitoring. These monitoring
functions permit for protection of the generator over- and under-excitation. The power
factor monitoring consists of a warning alarm and/or a shutdown alarm when enabled.

6 Application Field
6.3.1 Generator Excitation Protection
An alarm and the specified action will be initiated if the monitored power factor surpasses
the defined limits. Typically the generator is monitored for loss of excitation and/or over
excitation in a mains parallel application.
When a generator plant is paralleled against a utility, it is possible to control the power
factor at a desired reference. When the plant is operated in an island mode or islanded
parallel application, it is not possible to control the power factor. The load will dictate
what the power factor is due to the reactive nature of the load.
Fig. 214: Example - generator excitation protection
╚═▷ Fig. 214 shows a typical power factor (generator excitation) protection range, where
the desired range of operation (green area) is from 0.7 lagging (inductive) to 0.8 leading
(capacitive).
When the power factor exceeds either of these limits by entering the yellow shaded areas
starting at 0.7 lagging or 0.8 leading for more than 30 seconds, a class B warning alarm is
initiated.
If the power factor exceeds the desired range further and enters the red shaded areas
starting at 0.5 lagging or 0.6 leading for 1 second, a class E alarm is initiated and the
generator is shut down.
Configuration
1. ▷ In order to achieve the described protection, the power factor monitoring parameters
(╚═▷ “4.5.1.6.1.1 Generator Lagging Power Factor (Level 1 & 2)” or ╚═▷ “4.5.1.6.1.1
Generator Lagging Power Factor (Level 1 & 2)”) have to be configured as shown below.
Generator power factor lagging level 1 Generator power factor lagging level 2
ID Text Setting ID Text Setting
2325 Monitoring On 2331 Monitoring On
2329 Limit +0.700 2335 Limit +0.500
2330 Delay 30.00 s 2336 Delay 1.00 s
2326 Alarm class B 2332 Alarm class E
2327 Self acknowledge No 2333 Self acknowledge No
2328 87.70 LM:Eng.mon Yes 2334 87.70 LM:Eng.mon Yes

6 Application Field
6.3.2 Configuring A Setpoint Control Via Analog Input
Generator power factor leading level 1 Generator power factor leading level 2
ID Text Setting ID Text Setting
2375 Monitoring On 2381 Monitoring On
2379 Limit -0.800 2385 Limit -0.600
2380 Delay 30.00 s 2386 Delay 1.00 s
2376 Alarm class B 2382 Alarm class E
2377 Self acknowledge No 2383 Self acknowledge No
2378 87.70 LM:Eng.mon Yes 2384 87.70 LM:Eng.mon Yes
The following example illustrates how to configure an easYgen to use an external load
setpoint via analog input [AI 03].
The external setpoint may be enabled using a switch, wired to discrete input [DI 09].
An analog 0 to 20 mA input is to be used where 4 mA corresponds with 0 % power

(0 MW), 12 mA corresponds with 50 % power (1 MW), and 20 mA corresponds with 100 %
power (2 MW).
Configuring the rated generator power
1. ▷ Either on the front panel or using ToolKit navigate to menu [Configure measurement].
2. ▷ Configure the parameter listed in ╚═▷ Tab. 102.
1752 Gen. rated 2000 Generator rated power of 2 MW

active
power [kW]
Tab. 102: Parameters for rated generator power
Configuring the analog input for real power setpoint
1. ▷ Either on the front panel or using ToolKit navigate to menu [Configure analog inputs /
Analog input 3].
1100 Type Linear A user-defined linear characteristic curve is to be used
1101 User +0.00e0 A value of 0.00 is displayed at the minimum of the input
defined range

6 Application Field

min display
value
1102 User +2000.00e3 A value of 2000.00e3 is displayed at the maximum of the

defined input range
max
display
value
1139 Sender 4 The sender value at minimum display is 4 mA

value at
display
min.
1140 Sender 20 The sender value at maximum display is 20 mA

value at
display
max.
1120 Sender 0 - 20 mA A 0 to 20 mA sender is used on the analog input

type
10116 Filter time Off No filter time constant is applied to the analog signal
constant
1135 Exponent 0 The value of the analog input 3 is multiplied by 100=1.

for protocol
1103 Monitoring Low If the analog signal falls below 2 mA, a wire break is
wire break indicated
1104 Wire break Class B An alarm of class B will be issued in case of a wire break
alarm class
1105 Self No A wire break is not automatically cleared after it has been
acknowledge repaired
wire break
3636 Bargraph +0.00 The start value for the bargraph display of the analog input
minimum is 0.00
3637 Bargraph +2000.00 The end value for the bargraph display of the analog input
maximum is 2000.00
3. ▷
Configure the following parameters using ToolKit. They facilitate a more detailed display
of the analog value.
1125 Description ActivePower Analog input [AI 03] is labeled with "ActivePower SP (%)" on
SP the display
1134 Unit % The unit "%" is shown on the display.
Configuring the load controller
The load controller is to be configured that it uses a fixed load setpoint 1 of 2 MW unless
a switch energizes discrete input [DI 04] for enabling a variable load setpoint 2, which is
controlled by analog input [AI 03].
1. ▷ Either on the front panel or using ToolKit navigate to menu [Configure load control].

6 Application Field
5539 AM Determined The internal power setpoint 1 is used as load setpoint 1

ActPower by
SP1 [kW] AnalogManager
81.05
[A1 =
05.54.
Internal P
setp1
[kW]]
5526 Load Import The internal power setpoint 1 is a import power value
setpoint 1
5520 Int. load 2000.0 kW The internal power setpoint 1 is configured to 2 MW

control
setpoint 1
5540 AM Path Analog input 3 is used as load setpoint 2

ActPower Through of:
SP2 [kW] 06.03
Analog
input 3
5527 Load Steady The internal power setpoint 1 is a import power value
setpoint 2
5521 Int. load 1000.0 kW The internal power setpoint 1 is configured to 1 MW

control
setpoint 2
12919 Setp. 2 FALSE LogicsManager is not enabling load setpoint 2

load
3. ▷
Fig. 215: LogicsManager function "Setp. 2 load"
Configure the LogicsManager function 12919 "Setp. 2 load" as shown in (╚═▷ Fig. 215) to
enable load setpoint 2 if discrete input [DI 09] is energized.
4. ▷ Continue similarly with setpoint 3 and setpoint 4
Viewing the load setpoint on the easYgen

6 Application Field
6.3.3 Creating Self-Toggling (Pulsing) Relays
1. ▷
Fig. 216: Screen "Setpoint"
After the unit is configured as described above, the "Setpoint" screen may be viewed
from the main screen by selecting [Next page / Setpoints / Setpoints generator].
2. ▷
Fig. 217: Screen "Analog inputs"
The "Analog inputs" screen may be viewed from the main screen by selecting [Next
page / Measured values / Analog inputs/outputs].
6.3.3 Creating Self-Toggling (Pulsing) Relays
This function is set up with the LogicsManager.
This is a simple example of a relay output that toggles from energized to de-energized in
automatic mode with adjustable on and off time.

6 Application Field
6.3.4 Changing A Starter Battery Set
This pulsing relay may be combined with a flexible limit, which can be programmed with a
function like low battery voltage to get a blinking warning light.
• Relay 2 is the discrete output [DO 2] and Flag 5 is used as an auxiliary flag.
• Relay 2 will be ON (energized) for 2 seconds and then OFF (de-energized) for 2
seconds as long as the easYgen is in automatic mode.
Configuring "Flag 5" for a pulsing relay
1. ▷
Fig. 218: LogicsManager function "Flag 5"
Configure the LogicsManager function "Flag 5" as shown in (╚═▷ Fig. 218).
▶ In this example is the Delay ON time in the LogicsManager of Flag 5 indicates how long
the pause is. The Delay OFF time of Relay 2 is the pulse duration.
Configuring "Relay 2" for a pulsing relay
1. ▷
Fig. 219: LogicsManager function "Relay 2"
Configure the LogicsManager function "Relay 2" as shown in (╚═▷ Fig. 219).
This function is set up with the LogicsManager.

6 Application Field
The following programming example shows how two relay outputs are energized in turns
when discrete input 9 is energized.
At first discrete output 11 will be energized, then, discrete output 12 will be energized,
then discrete output 11 and so on.
This logic may be used to change between two starter battery sets for each starting
cycle.
Configuration
Configure Relay 11 and Relay 12 as well as the Flags 2, 3, 4, and 5 as shown in the
following example.
You may also use the discrete input, which starts the engine by default [DI 02] or any
other input command instead of discrete input 9; for example the command variable
03.06 "Engine released".
1. ▷
2. ▷
3. ▷

6 Application Field
6.3.5 Performing Remote Start/Stop And Acknowledgment
4. ▷
5. ▷
6. ▷
6.3.5 Performing Remote Start/Stop And Acknowledgment
The easYgen controller may be configured to perform start/stop/shutdown/

Acknowledgment functions remotely through the CAN bus or Modbus. The required
procedure is detailed in the following steps.

6 Application Field
6.3.5.1 Operating Modes
Refer to ╚═▷ “4.1.1 Basic Navigation” for a detailed description of the navigation through
the various display screens.
A detailed description of the individual parameters may be found in ╚═▷ “4.4.5.2

Operation Mode AUTO - Automatic Run”.
Be sure to enter the password for code level 2 or higher to be able to access the required
configuration screens.
Refer to ToolKit Manual for a description of the installation, configuration and usage of
the ToolKit visualization and configuration application.
Preliminary Conditions
We recommend to reset the unit to factory settings before proceeding.
Refer to ╚═▷ “4.3.5 System Management” for reference.
The LogicsManager factory settings are shown in ╚═▷ “9.3.5 Factory Settings”.
Two operating modes may be used with remote control:
• AUTOMATIC
• STOP
It is possible to fix the operating mode using the LogicsManager function 86.16 "Operat.
mode AUTO" (parameter ╚═▷ 12510).

6 Application Field
AUTOMATIC
1. ▷
Fig. 226: LogicsManager function "Operat. mode AUTO"
The LogicsManager function "Operat. mode AUTO" (parameter ╚═▷ 12510) can be
configured as shown in (╚═▷ Fig. 226).
▶ AUTOMATIC operation mode is always enabled.
If an alarm of alarm class C through F occurs in AUTOMATIC operating mode, the control
does not return to STOP operating mode. If the alarm is cleared after Acknowledgment a
restart is initiated.
It is also possible to configure a discrete input for controlling the operating mode using
the LogicsManager function 86.16 "Operat. mode AUTO" (parameter ╚═▷ 12510) and
86.18 "Operat. mode STOP" (parameter ╚═▷ 12530).
1. ▷
Fig. 227: LogicsManager function "Operat. mode AUTO"
The LogicsManager function "Operat. mode AUTO" (parameter ╚═▷ 12510) can be
▶ AUTOMATIC operation mode is enabled as soon as discrete input 9 is energized.

6 Application Field
6.3.5.2 Setting Up A Test With Or Without Load
STOP
1. ▷
Fig. 228: LogicsManager function "Operat. mode STOP"
The LogicsManager function "Operat. mode STOP" (parameter ╚═▷ 12530) can be
▶ STOP operation mode is enabled as soon as discrete input 9 is de-energized.
There are a lot of different opinions of the behavior of a proper test mode. The easYgen
controller is supporting the following two modes:
• Test with load
• Test without load
Alternatives to the operation mode TEST
In cases the dedicated TEST operation mode shall be not taken, the following procedure
can be taken to execute an TEST run in the operation mode AUTOMATIC.
Test with load
This is the LogicsManager function "Start req. in AUTO" (parameter ╚═▷ 12120). No
special message appears on the display.
If the mains fail during start in auto, the unit keeps running until the mains return and the
mains settling time is expired or the conditions for "Start req. in AUTO" are FALSE again.
The result depends on which condition is active longer.

6 Application Field
Test without load
This is the LogicsManager function "Start w/o load" (parameter ╚═▷ 12540). If the
conditions for this LogicsManager function are TRUE, the engine will provide an automatic
starting sequence and keep the generator running until this function is FALSE again.
Then the unit will perform an automatic stop sequence and remain in standby in auto
mode.
The message "Start w/o load" is displayed during the test without load. If the mains fails
during test without load and the emergency mode is enabled, the unit will take over the
load.
The unit will open the MCB and close the GCB. When the mains return, it will transfer the
load back to the mains according to the configured breaker transition mode after the
mains settling timer has expired. The engine will keep running until the conditions for
"Start w/o load" are FALSE again.

6 Application Field
6.3.5.3 Remote Start/Stop, Shutdown, And Acknowledgment
Example for test without load
The engine shall start once a month and run for one hour without overtaking the load.
The test day shall be every fifteenth of a month (with flag 2). A relay output can be
configured to indicate if this test is running, e.g. for a signal lamp.
1. ▷ Configure the parameters listed below to set up the timer.

1663 Active day 15 The active day is enabled every fifteenth of the month
1662 Active hour 10 The active hour is enabled between 10:00 and 11:00 am
every day
Tab. 103: Timer configuration

2. ▷
Configure the LogicsManager function "Flag 2" (parameter ╚═▷ 10701) as shown in (╚═▷
Fig. 229).
▶ Flag 2 becomes TRUE as soon as the configured active day and active time is reached.
3. ▷
Fig. 230: LogicsManager function "Start without load"
The LogicsManager function "Start without load" (parameter ╚═▷ 12540) can be
▶ Start without load mode is enabled as soon as Flag 2 becomes TRUE.
The easYgen may be start, stop, shut down, or acknowledged alarms with Modbus or CAN
protocol via the interface.
Therefore, two logical command variables (04.13 and 04.14) have to be configured with
the LogicsManager. 03.40 can handle Remote shutdown only.

6 Application Field
• 04.13 Remote request
• 04.14 Remote acknowledge
• 03.40 Remote shutdown
A Remote shutdown 03.40 can be configured via LogicsManager internal flag (e.g.12230
Flag 1) combined with a free alarm LogicsManager (e.g. Free alarm 1) configured with
shutdown alarm class.
How to handle a Remote request 04.13 and a Remote acknowledge 04.14 is described
below in detail.
Start request in AUTOMATIC operating mode
1. ▷ Either on the front panel or using ToolKit navigate to menu [PARAMETER: /
Configuration / Configure application / Configure operation modes / Operation mode
AUTO].
2. ▷ Open the LogicsManager 12120 for entry "Start req in AUTO".
3. ▷
Fig. 231: LogicsManager function "Start req in AUTO"
Configure the LogicsManager function "Start req in AUTO" as shown in (╚═▷ Fig. 231).
▶ With this setting, the "Start req in AUTO" LogicsManager output becomes TRUE as soon
as the remote request signal is enabled.
The LogicsManager commands 2 and 3 may be used to configure additional conditions

like discrete inputs, which must be energized to be able to issue the remote start
request.

6 Application Field
External Acknowledgment
1. ▷ Either on the front panel or using ToolKit navigate to menu [PARAMETER / Configuration /
Configure monitoring / Miscellaneous / General monitoring settings].
2. ▷ Open the LogicsManager 86.15 for entry "Ext. acknowledge".
3. ▷
Fig. 232: LogicsManager function "Ext. acknowledge"
Configure the LogicsManager function "Ext. acknowledge" as shown in (╚═▷ Fig. 232).
▶ With this setting, the "Ext. acknowledge" LogicsManager output becomes TRUE as soon
as the remote acknowledge signal is enabled.
The LogicsManager commands 2 and 3 may be used to configure additional conditions

like discrete inputs, which must be energized to be able to issue the remote acknowledge
command.
Please refer to ╚═▷ “6.5 Modbus Applications” for a description of how to configure the
LogicsManager functions via Modbus.
All interfaces access the same bits. The command variable "04.13 Remote request"
remains enabled in the easYgen until a new command is sent or the power supply failed
or is removed.
Remote start:
• The command variable "04.13 Remote request" changes to "1" (high) if the start bit
(ID 503, bit 0) changes from "0" to "1".
• The command variable "04.13 Remote request" changes to "0" (low) if the stop bit
(ID 503, bit 1) changes from "0" to "1" (╚═▷ Fig. 233).
Acknowledgment:
• The command variable "04.14 Remote acknowledge" reflects the Acknowledgment

bit (ID 503, bit 4).
• An Acknowledgment is generally performed twice:
◦ 1st change of the logical output "External acknowledge" from "0" to "1":
Silence horn
◦ 2nd change of the logical output "External acknowledge" from "0" to "1":
Acknowledges all inactive alarms

6 Application Field
System reaction
The easYgen does NOT react on the disabling of the start bit, but only on the enabling of
the stop bit.
This has the advantage that it is not required to maintain the connection established for
the whole time in case of a remote start.
The following figure shows the reaction of the command variable on the various changes
of the bits:
Fig. 233: Command variable
Enabling the bits may be performed with the following methods:
• Bit Enabling via Modbus Protocol and RS-485 Interface
• Bit Enabling via CANopen Protocol and CAN Interface 1
Bit enabling via Modbus protocol and RS-485 interface
The parameter Modbus Slave ID must be configured.
The control bits are sent on address 503 for a start via Modbus:
• Bit 0: Start
• Bit 1: Stop
• Bits 2 and 3: must be "0" (for the watchdog).
• Bit 4: Acknowledgment
• Bit 9: Shutdown command
Please refer to ╚═▷ “6.5 Modbus Applications” for a description of how to enable control
bits via Modbus.

6 Application Field
6.3.6 Connecting IKD 1 on CAN Bus
Bit enabling via CANopen protocol and CAN interface 1
For further information on the CANopen protocol refer to ╚═▷ “7.4 CANopen Protocol” and
the CANopen file *.eds, which is delivered with the unit.
Please refer to ╚═▷ “6.5 Modbus Applications” for a description of how to enable control
bits via Modbus.
Remote Shutdown
For controlling the device with Remote Shutdown 03.40 please run setup as described
above but with 03.40 instead of 04.14 and using Bit 9 instead of Bit 0, 1, and 4.
Additionally
• define a free LM flag for 03.40 Remote Shutdown and
• take it as input for a Free alarm
• with a shutdown alarm class.
We recommend to connect external expansion boards, like the Woodward IKD 1 to CAN
bus 2. This CAN bus offers preconfigured settings for operating several expansion boards
including the IKD 1.
However, it is also possible to connect an IKD 1 to CAN bus 1.
Refer to the ╚═▷ “4.7.4.1.2 Receive PDO {x} (Process Data Object)” and ╚═▷ “4.7.4.1.2
Receive PDO {x} (Process Data Object)” for the configuration of the parameters
concerned.
Refer also to ╚═▷ “7.4 CANopen Protocol” for a description of the data objects.
The easYgen may either be configured directly using the front panel or externally using
the ToolKit software.
Transmit PDO
The easYgen must be configured for sending to data protocol 65000 (external DOs 1 to 8)
and CAN ID 181 (hex) every 20 ms on TPDO1.
LSG connected on CAN 1
The upper described ID 181 (hex) can not be used if a LSG and a legacy device like GCP
30, GCP 20, MFR-2 are connected on CAN 1! The legacy devices are using IDs 181 - 18E
(hex) but can not be switched to another ID.
TPDO is used to send messages to an external device.

6 Application Field
1. ▷ Configure TPDO1 as shown below.

9600 COB-ID 181 (hex) / The COB-ID is configured to 181 (hex) or 385 (dec)
385 (dec)
9602 Transmission 255 Data is automatically broadcasted (transmission type 255)

type
9604 Event timer 20 ms The event timer is configured to 20 ms
8962 Selected 65000 Data protocol 65000 is selected

Data
Protocol
Tab. 104: TPDO1 configuration

▶
Fig. 234: TPDO configuration for IKD 1 (example HMI)
Fig. 235: TPDO configuration for IKD 1 (example ToolKit)

6 Application Field
╚═▷ Fig. 234 and ╚═▷ Tab. 104 display the example TPDO configuration for IKD 1.
Receive PDO
The easYgen must be configured for receiving data on an RPDO. The data received on
CAN ID 201h is interpreted as data protocol 65000 (external DIs 1 to 8).
1. ▷ Configure RPDO1 as shown below.

9300 COB-ID 201 (hex) / The COB-ID is configured to 201 (hex) or 513 (dec)
513 (dec)
9121 Event timer 2000 ms The event timer is configured to 2000 ms
8970 Selected 65000 Data protocol 65000 is selected

Data
Protocol
Tab. 105: RPDO1 configuration

▶
Fig. 236: RPDO configuration for IKD 1 (example HMI)

6 Application Field
6.3.6.1 Configuring an IKD 1 Expansion Module
Fig. 237: RPDO configuration for IKD 1 (example ToolKit)
╚═▷ Fig. 236 and ╚═▷ Tab. 105 display the example RPDO configuration for IKD 1.
6.3.6.1 Configuring an IKD 1 Expansion Module
General notes
The IKD 1 is a Woodward I/O expansion board. It can be connected via CAN bus to
Woodward easYgen generator controllers or DTSC 200 Automatic Transfer Switch
Controllers. The configuration of the IKD 1 can be done with the IKD Configuration Tool
running on a PC/laptop, connected via serial interface to the IKD 1.
IKD Configuration Tool (P/N: 9927-2094) is a tool to quickly configure an IKD for
connection with the easYgen series or DTSC 200. It will check the parametrization of the
IKD 1 and allows to set it to one of the four different connection modes. The IKD
Configuration Tool replaces the LeoPC configuration tool.
6.3.6.1.1 Installation
Prerequisites
The following items are necessary before installing the software:
• PC with Windows operating system
• To connect the IKD to a serial port (RS232) on the PC
◦ Woodward DPC cable RS-232 (P/N: 5417-557)
• To connect the IKD to a USB port on the PC
◦ USB/RS-232 adaptor and a Woodward DPC cable RS-232 (P/N: 5417-557)
◦ Woodward DPC cable USB/RS-232 (P/N: 5417-1251)
⚙ Installation
ᐳ The following steps needs to be performed for installing the IKD Configuration Tool
1. ▷ Uninstall any previous installation of IKD Configuration Tool
2. ▷ If software is not available on product CD-ROM: Please download from Woodward web
site

6 Application Field
6.3.6.1.2 Quick Configuration
3. ▷ Unzip the *.zip file on your PC

▶ You should get a directory named “publish”
4. ▷ Run the “setup.exe” from this directory
5. ▷ Follow the instructions given during installation
6. ▷ After installation the directory “publish” can be deleted
⚙ How to use Configuration Tool
ᐳ The following steps allow push-button configuration of IKD 1

1. ▷ Connect the IKD 1 to the PC/laptop as described above and power it
2. ▷ Start the already installed IKD Configuration Tool
3. ▷ Select the COM port IKD 1 is connected to the PC/laptop
4. ▷ Press button “Connect” to connect to the IKD 1
5. ▷ Select CAN baud rate
6. ▷ Press one of the four preconfigured mode buttons (“IKD 1 on Node-ID x”)
▶ Settings will be transferred to the IKD 1

6 Application Field
The Program Dialog Box
On start of the configuration software, you should get the following screen with fields,
buttons and selectors available:
⚙ Configuring an IKD
1. ▷
Fig. 238: IKD Configuration Tool
»COM port«
▶ Select between all serial ports your PC is providing. If there is no serial port available,
then this field is empty. Select the COM port to which the IKD is connected. (“COM1” for
example)
2. ▷ »Connect«
▶ Opens the selected serial port and tries to connect to the IKD. If successful, it will read
out the data from the IKD but it won’t change any data on the IKD. It will populate the
“CAN Baud rate” field with the CAN baud rate the IKD is currently configured. If the IKD
is already configured to one of the four different CAN node-IDs usable for an easYgen,
the corresponding button “IKD 1 on Node-ID x” will be colored green.
3. ▷ »Disconnect«
▶ Closes the serial port if it was opened. Must be used, if accidentally the wrong COM port
was selected and connected
4. ▷ »Status field« (yellow background)
▶ Shows messages about the status of the connection
5. ▷ »IKD on Node-ID X«
▶ Each of these four buttons has two functionalities:
1) After connecting, if the IKD 1 is already configured to one of the four different CAN
node-IDs usable for an easYgen, the corresponding button will be colored green.
2) By pressing the button the program will configure the IKD 1 to the selected node-ID
and CAN baud rate. After that it will read it out for check.
6. ▷ »CAN Baud rate«
B37574 ▶ This button has two functionalities:

easYgen-3000XT Series 705
1) After connecting it shows the currently configured CAN baud rate of the IKD.
6 Application Field
6.3.6.2 Configuration for a second IKD 1
ᐳ To connect a second IKD 1 to the easYgen:

1. ▷
Fig. 239: TPDO configuration for 2nd IKD 1 (example HMI)
Set up TPDO2 for the easYgen on the front panel as shown in (╚═▷ “ Transmit PDO”).
▶
Fig. 240: TPDO configuration for 2nd IKD 1 (example ToolKit)
Set up TPDO2 for the easYgen in ToolKit as shown in (╚═▷ “ Transmit PDO”).

6 Application Field
2. ▷
Fig. 241: RPDO configuration for 2nd IKD 1 (example HMI)
Set up RPDO2 for the easYgen on the front panel as shown in (╚═▷ “Receive PDO”).
▶
Fig. 242: RPDO configuration for 2nd IKD 1 (example ToolKit)
Set up RPDO2 for the easYgen in ToolKit as shown in (╚═▷ “Receive PDO”).

6 Application Field
6.3.7 Configuring A PWM Duty Cycle For A CAT ADEM Controller
6.3.7 Configuring A PWM Duty Cycle For A CAT ADEM Controller
If a PWM signal shall be used with a CAT ADEM speed controller, the duty cycle must be
limited between 10% and 85%.
For this, the following settings must be made to the respective analog output
The following parameter IDs and figures refer to analog output 1.
Note, that another analog output may also be used.
1. ▷ Configure the parameters as shown below.

5200 Data [11.03] A speed signal will be output

source Speed bias
%
5201 Selected PWM A PWM hardware type will be used

hardware
type
5208 Minimum 10.00% The minimum output value is 10%

hardware
level
5209 Maximum 85.00% The minimum output value is 85%

hardware
level
5210 PWM 10.00 V The PWM output level is configured to 10 V

output
level
Tab. 106: PWM duty cycle configuration

▶ The finished configuration in ToolKit is shown in (╚═▷ Fig. 243).

6 Application Field
6.3.8 Wiring Self Powered Discrete Inputs
6.3.8 Wiring Self Powered Discrete Inputs
ᐳ In order to create self-powered discrete inputs with plastic housing variant:

1. ▷ Connect battery negative (B-) to ground and PE (terminal 61).
2. ▷
Fig. 244: Wiring self-powered discrete inputs
Connect DI common (terminal 66) to power supply 12/24 V (terminal 63, minimum wire
size 0.5 mm² (20 AWG)).
▶ This enables to energize the discrete inputs against ground.
The Protective Earth terminal 61 is not connected on the sheet metal housing.
• Use the protective earth (PE) connector located at the bottom center of the sheet
metal housing instead.
6.3.9 Connecting Analog Inputs In Series
The analog inputs of the easYgen-3000XT series are galvanically isolated to the power
supply. This allows for example to share a power setpoint 0/4 to 20 mA with up to three
devices.
Make sure that the source can drive the resulting burden.

6 Application Field
6.3.10 Setup Expansion Modules at CAN 2
Fig. 245: Connecting analog inputs in series
The graphic above shows the terminal numbers for the analog input 3, but in principle it
works for all analog inputs which support a 0/4 to 20 mA signal.
General notes
The easYgen is supporting several expansion modules for external analog and digital
terminals. It is possible to connect up to four Woodward IKDs for digital inputs and
outputs and some third party devices e.g. from Phoenix or WAGO for analog and digital
inputs and outputs. Also a combination of the devices listed is possible.
Configuring easYgen for expansion modules is split in two parts:
• One part is located at the external analog/digital inputs/outputs pages and defines
how many inputs/outputs are used and the scaling of the analog types. Refer to
chapters ╚═▷ “4.4.2.4 Analog Inputs” for reference.
• The other part is located at the CAN2 interface pages and defines the Node IDs and
the types of external devices. Refer to chapter ╚═▷ “4.7.4.2.1 Expansion Modules at
CANopen Interface” for reference.
Additionally the external device must be configured to the correct baud rate and Node ID.
This could be done via DIP switches at Phoenix and WAGO, for the IKD with a Woodward
IKD configuration tool.
Supported external modules
Phoenix ...
Bus coupler Discrete outputs Discrete inputs Analog outputs Analog inputs
IL CAN BK IB IL 24 DO 2 IB IL 24 DI 2 IB IL AO 2/SF (only) IB IL AI 2/SF (only)
IB IL 24 DO 8 IB IL 24 DI 4 IB IL TEMP 2 UTH
(only)
IB IL 24 DO 16 IB IL 24 DI 8 IB IL TEMP 2 RTD
(only)
IB IL 24 DO 32 (only) IB IL 24 DI 16
IB IL 24/230 DOR4/W IB IL 24 DI 32 (only)

6 Application Field
Phoenix ...
Bus coupler Discrete outputs Discrete inputs Analog outputs Analog inputs
IB IL 24 DI 32 (only)
ILB CO 24 DI 16 DO ILB CO 24 DI 16 DO
16 16
There is a maximum of three Phoenix bus couplers on the CAN bus. There is also a
maximum of 16AI 4AO 32DI and 32DO, which must not exceeded in all possible
combinations.
WAGO …
Field bus coupler for CAN Interface/Connector
750-337 (MCS) Terminals/clamps
750-338 (SUB-D ) SUB-D
WAGO Analog Inputs (2 x AI or 4 x AI)
Type P/N two channel P/N four "Wire break" detection TYPE: Settings
version channel
version
(SE = Single ended, Diff = Differential)
Pt100 750-461 750-460/0001 T >849 °C: Overrun Pt DIN(R0)
T < -200 °C: Underrun Sender type: R0 = 100
Pt 1000 750-461/0003 750-460/0003 T >849 °C: Overrun Pt DIN(R0)
Ni 100 750-461/0004 T >250 °C: Overrun Ni DIN(R0)
Ni 1000 TK6180 750-461/0005 T >250 °C Overrun Ni DIN(R0)
10-1200 750-461/000-002 no Linear or table Sender

type: 0-1200 Ohm
10-5000 Ohms 750-461/000-007 no Linear or table Sender

type: 0-5000 Ohms
4-20 mA (SE) 750-466 750-455 Underrun Linear or table Sender

type: 4-20 mA
0-20 mA (SE) 750-465 750-453 no Linear or table Sender

type: 0-20 mA
0-20 mA (Diff) 750-452 no Linear or table Sender

type: 0-20 mA
4-20 mA (Diff) 750-454 Underrun Linear or table Sender

type: 4-20 mA
+/-10 V (Diff) 750-456 no Linear or table Sender

type: +/-10 V
0-10 V (SE) 750-467 750-468 no Linear or table Sender

type: 0..10 V

6 Application Field
WAGO Analog Inputs (2 x AI or 4 x AI)
Type P/N two channel P/N four "Wire break" detection TYPE: Settings
version channel
version
Thermocouple 750-469xxx Overrun TC Type x Sender type:

Thermocouple
(K, T, J, E, S, L) (standard format) Underrun: (approx. -49.8
°C) Notes
If adjustable variant
(750-469/003-000) is used:
use “Wago-I/O-CHECK” to
adjust (default Type is "K").
For details refer to ╚═▷
“Configurable WAGO
devices”
+/- 120 mV 750-469/000-003 no Linear or table Sender

type: Thermocouple
WAGO Analog Inputs (8 x AI)
Type P/N eight channel "Wire break" detection TYPE: Settings

version
RTD 750-451 depends on the configured TYPE and Sender type: according to the type
type configured by “Wago-I/O-CHECK”
Use “Wago-I/O-CHECK ” to configure the

different channels (Default type is PT100). For
details refer to ╚═▷ “Configurable WAGO
devices”.
0/4 – 20 mA 750-496 4-20 mA: underrun TYPE: Linear or table Sender type: 4-20 mA or
0-20 mA
0-20 mA: no detection
Use “Wago-I/O-CHECK ” to configure the
different channels (Default type is 4-20 mA).
For details refer to ╚═▷ “Configurable WAGO
devices”.
Thermocouple 750-458 Overrun TYPE: depends on the configured type Sender

type: depends on the configured type
Underrun (approx. -49.8
°C) Note: if adjustable variant (750-469/003-000) is
used use “Wago-I/O-CHECK ” to adjust (Default
type is K). For details refer to ╚═▷
“Configurable WAGO devices”.
WAGO Analog Outputs (2 x AO or 4 x AO)
Type P/N two channel P/N four Comments Settings

version channel
version
0-20 mA 750-552 750-553 Selected Hardware type =

mA
0-10 V 750-560, 750-559 Selected Hardware type =

"V"
[10 bit (100 mW)]
750-550
WAGO Digital Inputs/Outputs (2 ... 16 x DI/DO)
# of DIs 2 x DI 4 x DI 8 X DI 16 X DI

6 Application Field
WAGO Digital Inputs/Outputs (2 ... 16 x DI/DO)
P/N 750-400 750-402 750-430 750-1405
# of DOs 2 x DO 4 x DO 8 X DO 16 X DO
P/N 750-501 750-504 750-530 750-1504
There is a maximum of 16 WAGO analog inputs and up to 4 WAGO analog outputs with
up to 32 WAGO digital inputs and 32 WAGO digital outputs or up to 4 IKDs.
For all configurations with WAGO devices at least one WAGO CANopen fieldbus
coupler 750-337 is required!
Configurable WAGO devices
If configurable WAGO devices are used, the mode of the terminal must be configured via
the PC software »Wago I/O Check«. This configuration cannot be done via easYgen
parameters. The easYgen parameters for the corresponding channels must be consistent
with the Wago configuration!
RTD device (750-451)
Configure this 8 channel device RTD (750-451) via the »Wago I/O-Check« with the
following process image:
The following types are not supported: Ni1000 (high resolution), Ni1000 (TK5000),
Pt1000 (EN 60751 high resolution), and 1200 Ohms.
Typ Expected format
Ni100 (EN 60751) default
Ni1000 (TK6180, DN 43760) default
Ni120 (Minco) default
5000 Ohms S5-FB250
Thermocouple device (750-458) for voltage measurement
There is no intuitive setting in the easYgen if a channel of the TC device (750-458) is

configured for voltage measurement. A special scaling of the easYgen parameters
“Sender value at display min.” and “Sender value at display max” like in the table below
is required.
WAGO device Configure the according easYgen parameter
Voltage range “Sender value at display “Sender value at display

min.” max.”
+/- 30 mV -614.4 614.4
+/- 60 mV -307.2 307.2

6 Application Field
WAGO device Configure the according easYgen parameter
Voltage range “Sender value at display “Sender value at display

min.” max.”
+/- 120 mV -153.6 153.6
Combinations of modules
All combinations of external terminals up to the maximum of 16AI, 4AO, 32DI, and 32DO
are possible.
Selection is done by parameter »Select external terminals «╚═▷ 15320.
There is a maximum of three bus couplers on the CAN bus for PHOENIX modules but (for
the moment) only one bus coupler on the CAN bus for WAGO modules.
So WAGO devices must use one and the same CAN address only.
The following table shows the possible configuration combination of the "Type" settings
(parameter ╚═▷ 5851) and the "Sender type" setting (parameter ╚═▷ 5856) for Phoenix
devices.
Fig. 246: Supported Phoenix sender types

6 Application Field
If Thermocouple is configured together with “Table A”, “Table B“, or “Linear” the input
works with a range from -15 mV to 85mV. In this case the values for parameters “Sender
value at display min./max.” must be entered in [mV] (e.g.: min: 0.00, max: 85.00).
Configuration process help
The following flow charts step-by-step guide you through the configuration of external
CANopen devices.
Configuration is the same for Phoenix/WAGO
The flow charts below use "P..." for Phoenix external interfaces but it works similar with
"W..." for WAGO devices.
Fig. 247: Configure expansion boards part 1

6 Application Field

6 Application Field

6 Application Field

6 Application Field
6.3.11 Phase Angle Compensation
WARNING!
Check parameters!
Erroneous synchronization settings can destroy the generator with destructive

power!
Ensure the parameters are configured correctly! Incorrect wiring of the system cannot be
compensated for with this parameter.

6 Application Field
General notes
This feature allows the easYgen to adapt the phase angle measurement system according
to the transformer type. The phase angle of the "generator to busbar" and the "busbar to
mains" measurement can be compensated . The phase angle compensation is activated
with the parameters "Phase angle compensation GCB" (parameter ╚═▷ 8825) and "Phase
angle compensation MCB" (parameter ╚═▷ 8841) .
The controller provides an adjustment for a phase angle deviation in a range of +/-180.0°.
The range can be configured with the parameters "Phase angle GCB" (parameter ╚═▷
8824) and "Phase angle MCB" (parameter ╚═▷ 8842). This parameters compensate the
phase angle deviation, which can be caused by transformers (i.e. a delta to wye
transformer) located within the electrical system.
Example – phase angle compensation GCB
Fig. 252: Phase angle compensation GCB
The easYgen generator voltage is connected to the low voltage side of a transformer with
the vector group Dyn5. The easYgen busbar voltage is connected to the high voltage
side. Because of the transformer, the phase angles between generator and busbar differs
due the closed GCB. The synchronization function of the easYgen can be compensated by
a configurable phase angle deviation.

6 Application Field
Using vector group 5 (Dyn5) implies: α = 5 x 30° = 150°. Since 150° < 180° and the
easYgen busbar measurement is connected to the high voltage side, this results into "α"
to be used as phase difference. Configure parameter "Phase angle GCB" (parameter ╚═▷
8824) to "150°" to compensate the phase difference between generator/busbar.
Example – phase angle compensation MCB
Fig. 253: Phase angle compensation MCB
The easYgen mains voltage is connected to the high voltage side of a transformer with
the vector group Yd11. The easYgen busbar voltage is connected to the low voltage side.
Because of the transformer, the phase angles between mains and busbar differs due the
closed MCB. The synchronization function of the easYgen can be compensated by a
configurable phase angle deviation.
Using vector group 11 (Yd11) implies: α = 11 x 30° = 330°. Since 330° > 180° and the
easYgen mains measurement is connected to the high voltage side, this results into
"-360° - α" to be used as phase difference. Configure parameter "Phase angle MCB"
(parameter ╚═▷ 8842) to "-30°" to compensate the phase difference between mains/
busbar.

6 Application Field
6.3.12 Start/Stop Logic Mode "Off"
General notes
The start/stop sequence in the easYgen is completely disabled. This function is needed in
applications where the control of the start/stop logic is completely done by an external
device (e.g. PLC).
The LogicsManager “Release engine monitoring” (parameter ╚═▷ 12999) has a special
function, if the "Start/stop logic mode" (parameter ╚═▷ 3321) is configured to “Off”.
When the LogicsManager becomes TRUE, the delayed monitoring function alarms are
triggered, which are delayed by the engine speed. If they become FALSE all engine speed
related monitoring functions are switched off. The LogicsManager "Start req. in AUTO"
(parameter ╚═▷ 12120) gets a special function if the "Start/stop logic mode" (parameter
╚═▷ 3321) is configured to “Off”. When the LogicsManager becomes TRUE the
operational mode begins. With becoming FALSE the operational mode will be left.
To operate the easYgen in this configuration correctly, the following needs to be done:
• The easYgen requires an external feedback, that the drive system will be started.
That is the precondition for the easYgen to trigger the delayed monitoring function,
which activates, after a delay time, the speed related monitoring functions.
(underspeed, underfrequency, undervoltage, etc.)
• The easYgen requires an external feedback, that the drive system will be stopped.
That is the precondition for the easYgen to deactivate the speed related monitoring
functions. This avoids upcoming alarms due the drive system is stopped.
• The easYgen must be directed to switch into the active operational mode or to exit
this operational mode. The operational mode proceeds with the actions according to
the configured application and transition modes.
Example
Fig. 254: LogicsManager function "Firing speed"

6 Application Field
Fig. 255: LogicsManager function "Release engine monitoring"
The following section shows a practical example, to explain in detail the described above
configuration.
╚═▷ Fig. 255 shows the LogicsManager “Release engine monitoring” (parameter ╚═▷
12999). The LogicsManager could be configured as follows:
• The external start/stop device gives an feedback to the easYgen via discrete input
[DI 02] ("09.02 Discrete input 2") that the drive system will be started or already is
started.
• Firing speed ("87.68 LM: Firing speed") must be reached.
• Additionally the reply GCB closed ("04.06 GCB closed") must be true to get the result
true.

6 Application Field
Fig. 256: Start/Stop sequence - LogicsManager "Firing speed"
The drawing above shows the following:
• The frequency controller is triggered, if the engine speed (generator frequency)

reaches the "Start frequency control level" (parameter ╚═▷ 5516) and after the
expired "Start frequency control delay" (parameter ╚═▷ 5517) time. The frequency
controller is switched off, if the engine speed (generator frequency) falls below the
“Release engine monitoring” (parameter ╚═▷ 12999) level.
• The voltage controller is triggered, if the generator reaches the "Start value"
(parameter ╚═▷ 5616) and after the expired "Start delay" (parameter ╚═▷ 5617)
time. The voltage controller is switched off, if the engine speed (generator
frequency) falls below the “Release engine monitoring” (parameter ╚═▷ 12999)
level.
• The delayed monitoring function is triggered when LogicsManager "Release engine

monitoring" (parameter ╚═▷ 12999) becomes TRUE and after the "Engine monitoring
delay time" (parameter ╚═▷ 3315). The delayed monitoring function is switched off
when LogicsManager "Release engine monitoring" (parameter ╚═▷ 12999) becomes
FALSE.

6 Application Field
6.3.13 Ripple Control Receiver
Fig. 257: LogicsManager function "Start req. in AUTO"
To activate the operational mode in the easYgen, discrete input [DI 02] ("09.02 Discrete
input 2") is used in the LogicsManager "Start req. in AUTO" (parameter ╚═▷ 12120) .
With removing the start request in AUTOMATIC the operational mode will be left.
Fig. 258: Start/Stop sequence - LogicsManager "Start req. in AUTO"
╚═▷ Fig. 258 shows the following:
• The closing (synchronization) of the GCB is triggered when LogicsManager "Start req.
in AUTO" (parameter ╚═▷ 12120) becomes TRUE.
• The opening (including power down ramping) of the GCB is triggered when
LogicsManager "Start req. in AUTO" (parameter ╚═▷ 12120) becomes FALSE.
General notes
Decentralized energy producers can be obliged by power supply companies to equip

plants with a technical and operational provision for remote-controlled reduction of the

6 Application Field
feed-in power to stabilize mains. Ripple control is one form of power limitation and is used
in many countries around the world.
Functionality
The energy supply company provides a signal to the ripple control receiver to reduce the
feed-in power of the generating plant. The ripple control receiver switches four relay
contacts according to the required energy power level. This relay contacts correspond for
example to the following energy power levels:
• 100% (full feed-in) - Step 1
• 60% - Step 2
• 30% - Step 3
• 0% (no feed-in) - Step 4
The respective contact is closed for the duration of the reduction.
The reduction of the feed-in power must be established within a certain time frame
(depending on national regulations).
Derating of power
The power reduction is realized by using the LogicsManager "Free derating" (parameter
╚═▷ 15146). This function is using an analog signal. For this reason the relay outputs of
the ripple control receiver must be converted into a corresponding analog signal. We
recommend a resistor array like shown in ╚═▷ Fig. 259 to convert the relay outputs into a
analog signal (0 to 500 Ohms).
Fig. 259: Ripple control receiver wiring
R1 = 500 Ohms (or 560 parallel 4.7 k)
R2 = 300 Ohms (or 330 parallel 3.3 k)
R3 = 150 Ohms

6 Application Field
Max. power Switched relay ripple Corresponding analog Derating

control receiver value
[% of rated] [% of rated]
100% Relay - Step 1 500 Ohms 0%
Configuring the analog input for a ripple control receiver
1. ▷ Either on the front panel or using ToolKit navigate to menu [Configure analog inputs /
Analog input 1].
1000 Type Linear A user-defined linear characteristic curve is to be used
1001 User +100.00 A value of 100 is displayed at the minimum of the input
defined range
min display
value
1002 User +0.00 A value of 0 is displayed at the maximum of the input

defined range
max
display
value
1039 Sender 0.000 The sender value at minimum display is 0 Ohms

value at
display
min.
1040 Sender 500.000 The sender value at maximum display is 500 Ohms
value at
display
max.
1020 Sender 0 - 2000 A 0 to 2000 Ohms sender is used on the analog input
type Ohm
10113 Filter time 3 Filter time depending on the ambient conditions

constant
3632 Bargraph +0.00 The start value for the bargraph display of the analog input
minimum is 0
3633 Bargraph +100.00 The end value for the bargraph display of the analog input
maximum is 100 and indicates the derating
3. ▷ Configure the following parameters using ToolKit. They facilitate a more detailed display
of the analog value.
1025 Description Derating Analog input [AI 01] is labeled with "Derating" on the
display
1034 Unit % Text "%" is displayed for the unit

6 Application Field
1035 Exponent 0 Value displayed "as is" (without exponent)

for protocol
Configuring the derating of power
1. ▷ Either on the front panel or using ToolKit navigate to menu [Configure load control /
Derating of power].
15149 Direct On Only the analog source is used for the derating
derating
15147 AM Determined Defines »06.01 Analog Input AI 1« as the analog source

Derating by which controls the derating function
source AnalogManager Select "Pass through"
81.21
[A1 =
06.01
Analog
input 1]
15142 J1939 Off The derate command via ECU is ignored

derating
3. ▷
Fig. 260: LogicsManager function "Free derating"
Configure the LogicsManager function »87.60 Free derating« as shown in (╚═▷ Fig. 260)
to enable derating of power if discrete input [DI 09] is energized.
Please configure "Alarm class" (parameter ╚═▷ 1362) of discrete input [DI 09] to
"Control".
Maximal power setpoint
After the unit is configured as described above, the maximal power setpoint looks like
shown in ╚═▷ Fig. 261.

6 Application Field
6.3.14 Neutral Interlocking
Fig. 261: Maximal power setpoint
General Notes
The Neutral Interlocking function controls in multiple-gen applications the Neutral

Contactor (NC) of each generator. The contactor bridges the Neutral with the PE. The rule
is that only one neutral of the running generators in the same segment are bridged to
earth.
The Logic ensures that with changing of generators or a lacking neutral breaker the
neutral link is passed over to another active running generator. This requires information
exchange between the genset controls. The load share protocol in the easYgen provides
the according information.

6 Application Field
Application Examples
L3
L2
L1
N
GCB 1 GCB 2
L1 L2 L3 L1 L2 L3
G G
N N
NC 1 NC 2
Fig. 262: Wiring neutral Interlocking: GCB 3-pole
Fig. 263: Wiring neutral Interlocking: GCB 4-pole
Function
Start and operating
The genset control closes principally after each successful start (firing speed reached) the
NC. The genset control proceeds with closing the GCB, if the NC has been closed
successfully. If the NC closure was not successful the easYgen issues an alarm. The NC
and GCB closure procedure is blocked from now on, until the alarm is acknowledged.

6 Application Field
When the GCB is closed the genset control begins to figure out, whether the own NC can
remain closed or must be opened. This monitoring is done continuously.
As long the GCB is closed, the NC remains closed or is closed, if:
• No connection to mains is active
AND
• one of the following is TRUE
◦ the own NC is the only closed NC in the same segment
OR
◦ there is minimum one other NC in the same segment closed but the own
generator has a higher neutral interlocking priority
OR
◦ there is minimum one other NC in the same segment closed which has the
same neutral interlocking priority but the own genset control has a lower device
number
In all other cases the NC is opened!
Running Generator without closed GCB
As long the engine/generator is running and the GCB is open the NC will be closed or
remains closed until the engine/generator is stopped.
Neutral Contactor (NC) Feedback
The discrete input 12 (DI 12) is used as feedback of the Neutral contactor and cannot be
configured onto another discrete input. If the input is energized, the neutral contactor is
recognized as closed.
Monitoring NC Feedback
The monitoring of the NC feedback is performed always, if the Neutral Interlocking is

enabled. The monitor checks, if the feedback behaves according to the NC command.
With a configurable delay time the alarm is activated with a general alarm text. Open or
closure failure are not differentiated. The issued Alarm text is: "N-cont. reply mism."
(Neutral contactor has a reply mismatch).
Event logger and NC Feedback
If the Neutral Interlocking is enabled, following event entries shall take place:
• Neutral cont. opened (with +)
• Neutral cont. closed (with +)
Priority for Closing NC
The priority for closing GCB is configurable. This priority is independent from the LDSS
priority. The customer can freely decide which generator shall get which priority.

6 Application Field
The advantage of this determination is that the application is not fixed with rated power
settings. Maybe there are other circumstances which shall determine the neutral
interlocking priority.
Two LogicsManager variables give further information:
• 03.39 Close neutral contactor - status
• 08.37 Neutral contactor reply mismatch

6 Application Field
6.3.15 LDSS with predicted load
Fig. 264: Flow Chart Neutral-Interlocking
6.3.15 LDSS with predicted load
6.3.15.1 Introduction
Please read the ╚═▷ “4.4.5.5.6 LDSS with predicted load” first, before you continue. The
chapter here shall give you additional information to dedicated application.
Be aware of the two possible modes:

6 Application Field
• Predict load source “Internal”:
The easYgen is autarkic handling the function. The easYgen serves the GGB and the
MCB.
• Predict load source “External”:
The easYgen cooperates with an external ATS control (e.g. Woodward DTSC-200).
The ATS control measures the mains power and serves the MCB and GGB. The ATS
device communicates over CANopen with the easYgen.
We recommend to ask Woodward for a dedicated application note with configuration

examples, if you want go for the external mode.
For parameter refer to ╚═▷ “4.4.5.5.6 LDSS with predicted load”. The easYgen informs the
user with AnalogManager variables and LogicsManager command variables about their
content.
For the relevant analog variables (10.73-10.78, 81.30 and group 21) refer to ╚═▷ “9.4
AnalogManager Reference”.
For the relevant logic variables 04.68, 04.69, 86.36, groups 32 – 36 refer to ╚═▷ “9.3.2
Logical Command Variables”.

6 Application Field
6.3.15.2 Internal source mode (EG3500XT only)
6.3.15.2 Internal source mode (EG3500XT only)
6.3.15.2.1 General
Fig. 265: Example of an application with predicted load source „internal“
Pre-assumption:
The LM ID12930 “LD start stop” is TRUE.
The Parameter ID9066 "Predicted load source” is configured as “Internal”.
The LM ID15026 “LDSS with predicted load” is TRUE.
The AnalogManager ID9059 "Consumer load [kW]" passes the mains active power (02.74
Mains active power [W] * -0.001) to the LDSS PL function.

6 Application Field
6.3.15.2.1 General
Fig. 266: Configuration AM Consumer load
Fig. 267: Schematic of a predicted load with „internal“ source handling
The Procedure:
As long as LM ID12120 “Start req in AUTO” is FALSE, the value of the AM ID9059
"Consumer load [kW]" goes into the 5-minute average power calculation which is passed
to the LDSS.
In that moment the LM ID12120 “Start req in AUTO” becomes TRUE, the last result of the
5-minute average calculation will be kept.
So following procedure is started:
• The configuration ID5752 “Start stop mode” is ignored and forced to “Reserve
power”.
• The GGB close release will be internally blocked in the easYgen and the “Inhibit ATS
flag” LM 04.69 becomes true.

6 Application Field
6.3.15.2.2 Example “Emergency power unit” with internal GGB control (only easYgen 3400XT/3500XT)
• The easYgen(s) starts in dead busbar start mode "LDSS", the according amount of
engines which are required to maintain the consumer load. (The parameter ID5753
is ignored in that moment).
If the rated power on the generator busbar is higher than the 5-minute average value
plus the active reserve power,
• the internal GGB close will be released and the “Inhibit ATS flag” 04.69 becomes
false.
◦ The GGB will be closed
• The generator load measurement easYgen is passed to the LDSS. So the LDSS is now
working like in the original mode.
• The configuration ID5752 “Start stop mode” is considered again. So the start stop
argue could change now.
• The 5-minute average value is now supplied by the real busbar load. Thus the 5-
minute average value is still tracked with the consumer load.
The procedure is stopped from that moment on the LM ID12120 “Start req in AUTO”
becomes FALSE. The generators will go into cooldown and stop.
6.3.15.2.2 Example “Emergency power unit” with internal GGB control (only easYgen 3400XT/
3500XT)
The example here shows what is to do if the easYgen shall start the correct amount of
engines in emergency mode. The GGB and MCB is operated by the easYgen. The breaker
transition mode is “Open transition”.
To incorporate the easYgen emergency mode into the procedure, the flag 04.09
“Emergency mode” is to include in the LM ID12120 “Start req in AUTO”.
Fig. 268: Including the emergency mode as starting argue.

6 Application Field
6.3.15.2.2 Example “Emergency power unit” with internal GGB control (only easYgen 3400XT/3500XT)
Fig. 269: Example - GGB breaker handling with open transition.
The minimum generator power is set according to the largest expected load. The GGB is
released with the signal 04.69 “Inhibit ATS”. Minimum generator power (ID3440) is set to
the maximum expected load.
Fig. 270: Bypass minimum Pgen. (12936) becomes active if “Inhibit ATS” is false. That is
the case if there is enough generator rated power on busbar.

6 Application Field
6.3.15.3 External source mode
6.3.15.3 External source mode
6.3.15.3.1 General
The external source mode is basically running like the internal source mode but the mains
measurement, the MCB and GGB control is provided by an external control. This control,
usually an ATS control (e.g. DTSC-200), sends the mains power and required condition
flags as CANopen TPDO messages to the easYgen device. Through configuration of the
RPDO in the easYgen the mains power and the condition flags are appearing
automatically in the LDSS PL function. The system allows to connect up to 5 ATS controls.
We recommend to ask Woodward for a dedicated application note with configuration

examples, if you want go for the external mode.
The external mode contains up to 5 independent “5-minute average value [kW]”

calculations. Out of these values an “Average load sum [kW]” is provided.
Fig. 271: The principle of the LDSS PL in external source mode
Pre-assumption
The explanation here is performed for an application with one ATS control. The principle is
expandable on up to 5 ATS controls.
The LM ID12930 “LD start stop” is TRUE.
In the external mode the Parameter ID9066 "Predicted load source” is configured as
“External”.
The LM ID15026 “LDSS with predicted load” is TRUE.

6 Application Field
6.3.15.3.1 General
The ATS control sends:
• The mains load 1 [kW]
• The MCB condition
• The mains condition
• The GGB condition
• An ATS Start signal
The ATS start signal 04.68 is entered in the LM ID12120 “Start req in AUTO”.
Fig. 272: Example of an application with predicted load source „external“. Additionally,
there is a hardwired inhbit signal from easYgens to the ATS".
Inhibit Signal
To inhibit the switching over of the ATS (e.g. DTCSs) before the nominal power on bus
matches the predicted load plus the active reserve power the easYgens activate an
inhibit signal.
For this reason every easYgen must have a relay configured with the command variable
04.69 “Inhibit ATS”. These signals must be hardwired as OR and connected to the ATS
inhibit input.

6 Application Field
6.3.15.3.2 LDSS PL CANopen Handling
The procedure
As long as LM ID12120 “Start req in AUTO” is FALSE and the MCB is closed, the RPDO1
Word2 (ID3372) load 1 [kW] goes into the individual 5-minute average power calculation.
In the moment the mains fails [see RPDO1 Word1 (ID3371)] the feeding of the 5-minute
average value is stopped. So the last result of average calculation will be kept. If the GGB
is open [see RPDO1 Word1 (ID3371)] the value will be passed over as consumer load to
the LDSS function.
The ATS start signal from extern [see RPDO1 Word1 (ID3371)] sets the LM command
variable “ATS Start request” 04.68 on TRUE. So the LM ID12120 “Start req in AUTO”
becomes TRUE.
• So following procedure is started:
◦ The configuration ID5752 “Start stop mode” is ignored and forced to “Reserve
power”.
◦ The “Inhibit ATS flag” LM 04.69 becomes true.
◦ The easYgen(s) starts in dead busbar start mode "LDSS", the according amount
of engines which are required to maintain the consumer load. (The parameter
ID5753 is ignored in that moment).
If the rated power on the generator busbar is higher than the 5-minute average value
plus the active reserve power,
• the “Inhibit ATS flag” 04.69 becomes false.
◦ The ATS closes the GGB
• The generator load measurement easYgen is passed to the LDSS. So the LDSS is now
working like in the original mode.
• The configuration ID5752 “Start stop mode” is considered again. So the start stop
argue could change now.
The procedure is stopped from that moment on the LM ID12120 “Start req in AUTO”
becomes FALSE. The generators will go into cooldown and stop.
The easYgen emergency mode ID2802 must be disabled. The control over the start of the
engines is maintained by the ATS control.
The following chapter summarize the CANopen analog and binary variables within the
LDSS PL function. If the RPDO mapping is configured the LDSS PL function is supported.
Parallel to that the easYgen makes the binary and analog variables available via the
Logics- and AnalogManager. (see table below). These values can be taken for visualization
or additional logical purposes.
Each ATS must send a transmit PDO with minimal two words (INT16):
• “Word 1” with binary flags
◦ a. Bit 1-12 empty (0)

6 Application Field
◦ b. Bit 13 GGB closed
◦ c. Bit 14 MCB closed
◦ d. Bit 15 Mains okay flag
◦ e. Bit 16 ATS start signal
• “Word 2” with the mains power [0.1 kW resolution] signed.
These two words are mapped inside the easYgen to according database identifiers.
Binary flags from ATS (Word 1)
The word with the binary flags is filled up on the last 4 bits. This word is mapped in the
easYgen to the according database index. (According to the ATS number)
CAN LogicsManager Bit ID Function ID
Command Variable LDSS PL De‐

script‐
ion
Field
ATS1: 32.13 CAN1 RPDO1.1.13 13 11509 GGB closed 11573

RPDO 1
“Word 1” 32.14 CAN1 RPDO1.1.14 14 11510 MCB closed 11574
is
mapped 32.15 CAN1 RPDO1.1.15 15 11511 Mains OK 11575
to ID
3371 32.16 CAN1 RPDO1.1.16 16 11512 ATS Start signal 11576

script‐
ion
Field

RPDO 2
is
to ID

RPDO 3
is
to ID

RPDO 4
is
to ID

RPDO 5
is

6 Application Field
6.3.15.3.3 Internally provided analog variables

script‐
ion
Field
to ID 36.16 CAN1 RPDO3.1.16 16 11528 ATS Start signal 11592

3387
Tab. 107: If further ATS are in use:
Mains power [kW] from ATS (Word 2)
The word with mains power is an 16INT signed. This word is mapped in the easYgen to
the according database index.
CAN AnalogManager Function
variable LDSS PL
ATS 1: 21.02 CAN1 RPDO1.2 Real power 1 [0.1kW]
RPDO 1 “Word 2” is mapped to ID

3372
If further ATS are in use:
CAN AnalogManager Function
variable LDSS PL

3376

3380

3384

3388
6.3.15.3.3 Internally provided analog variables
These values can be assigned to the analog

variables of the Customer screens for
visualization.
10.73 Average load 1 [kW] 5 min average of “21.02 CAN1 RPDO1.2 “

6 Application Field
6.3.15.4 Tables
These values can be assigned to the analog

variables of the Customer screens for
visualization.
10.78 Average load sum [kW] If LDSS PL external is active, 10.78 is the load value
which is passed to the LDSS. It is the sum of all
averages (10.73 – 10.77) which have “Mains not
okay” and “GGB not closed”. In internal mode it is
the value of the 5 min. average of the AM
“Consumer load”.
81.30 AM Consumer load [kW] This analog variable provides the load for the LDDS
with load prediction in internal source mode.
6.3.15.4 Tables
RPDO Summary
RPDO configuration to get data from ATS 1:
Receive PDO Database Index AnalogManager variable Comment
RPDO1 Word1 3371 21.01 CAN1 RPDO1.1 Binary information
RPDO1 Word2 3372 21.02 CAN1 RPDO1.2 Real power [0.1kW]
RPDO Summary
RPDO Summary
RPDO Summary
RPDO Summary

6 Application Field
6.3.16 Derating And Uprating Of Power (Details)
Internally provided LM Command Variables
ID Function
LMCV
04.68 ATS start request 11983 If this variable is true, LDSS PL

wants to start the engines. This
command variable is incorporated
in the LM “Start request in AUTO”.
04.69 Inhibit ATS 11984 This variable is true if “04.68 ATS

start request” is true and the
rated power on the bus bar is
lower than the predicted load (+
active reserve power ). It is
usually passed internally to
release the GGB or external to
release the ATS control.
86.36 LM: LDSS predicted 12606 Result of the LM LDSS with load
prediction.
6.3.16 Derating And Uprating Of Power (Details)
6.3.16.1 Direct Derating
General notes
The idea of direct derating of power is that the user can control with an analog value,
usually from outside, the amount of reduction. For this purposes mainly an analog input
would be taken. Additionally in some applications are uprating desired, for example
during load sharing procedures, which can be as well executed in determined
circumstances.
Derating
If parameter Direct Derating (ID15149) is enabled, the output value of the

AnalogManager AM Derating source (ID15147) determines the derating directly. This
derating value is also provided as AnalogManager variable under "81.21 AM Derating
source". For derating the active power setpoint, the value shall vary between 100% (no
derating) and 0% (full derating). The derating function parameters 15143, 15144, 15145
are not in use.
Uprating
If parameter Direct Derating (ID ╚═▷ 15149) is enabled, the output value of the
AnalogManager AM Derating source (ID15147) determines the uprating directly. This
value is also provided as AnalogManager variable under "81.21 AM Derating source". For
uprating the value shall vary between 100% (no uprating) and higher (uprating begins).
The scaling with parameters 15143, 15144, 15145 is not in use.

6 Application Field
6.3.16.2 Derating With Characteristic Curve
Combined Derating and Uprating
If parameter Direct Derating (ID15149) is enabled, the output value of the

AnalogManager AM Derating source (ID ╚═▷ 15147) determines the derating/uprating
directly. This value is also provided as AnalogManager variable under "81.21 AM Derating
source".
For derating the active power setpoint goes under 100%, for uprating the value goes over
100%, and with exact value of 100% the normal setpoint becomes active.
General notes
Some application require a functionality to reduce the active power dependent on a well
defined measured value. This could be for example a temperature measurement: The
load should decrease with higher temperatures according to a configured characteristic.
If parameter "Direct derating" (ID ╚═▷ 15149) is OFF, the LogicsManager “Free derating"
(ID ╚═▷ 15146) becomes TRUE and the analog value of power exceeds the value “Start
derating at” (ID ╚═▷ 15143), the unit begins to reduce the present active power setpoint.
The grade of reducing depends on the value “Stop derating at” (ID ╚═▷ 15144) and the
value of “Max. power deviation” (ID ╚═▷ 15145) which are configurable.
If the LogicsManager "Free derating" becomes FALSE, the unit ramps back to its original
setpoint. If derating/uprating is active, the display shows the indication
“Derating”/"Uprating".
The derating/uprating function can be used in islanded operation, too. The available rated
power from an engine can be reduced (derated) or increased (uprated) with an analog
value without adjusting a parameter value. With this function the engine can be
individually loaded within of an multiple gen islanded operation (asynchronous load
sharing).
Freely scalable derating characteristic
The easYgen-XT offers a characteristic which is linearly decreasing the momentary active
power setpoint according to the value offered by the AnalogManager ╚═▷ 15147.
The characteristic is defined by the following parameters:
• 15143: “Start derating at”
• 15144: “Stop derating at”
• 15145: “Maximal power deviation”
When the LogicsManager "Free derating" becomes active and the analog value crosses
the reducing start value, the configured derating line becomes active. If the derating line
falls below the active power setpoint the derating becomes effective. The grade of
reduction depends on the reducing stop value and the power deviation freely
configurable. If the LogicsManager "Power Reduction" becomes FALSE, the unit shall ramp
back to its original setpoint.
To become more familiar please look at the examples below:

6 Application Field
☼ Example 1: Mains Parallel Operation (setpoint = below rated power)
• Rated generator power = 200 kW

• Current power setpoint of the generator = 150 kW (75%)
• Start derating at = 80 °C water temperature (i.e. analog input AI 01 is defined as
free derating source by parameter 15147)
• Stop derating at = 90 °C water temperature
• Max. power deviation = 40% (80 kW)
Fig. 273: Derating: Mains parallel operation; setpoint below rated power
If the engine is running and the LogicsManager "Free derating" is TRUE, the unit
monitors the water temperature. If the water temperature remains below the value
“Start derating at”, the reduction becomes not active and remains on 0%. If the water
temperature increases and so exceeds the value “Start derating at” the reduction
becomes active (the unit starts to derate the current active power setpoint). The rate of
reduction (slope) is determined by the values of “Start derating at”, “Stop derating at”,
and "Max. power deviation" ("Max. power deviation" also defines the minimum power).
In this example the power reduction would increase and so reduce power from 75% at
86.5 °C down to 60% = 120 kW at 90 °C. Temperature over 90 °C would cause the same
reduction of 40% in this example. So it is guaranteed that the engine is not running with
too less load.
A Setpoint below the Minimum (e.g. 55%) would not run into reduction.
With a smaller Maximum deviation (e.g. 20%) Minimum would be higher than Setpoint
and so not cause reduction.

6 Application Field
☼ Example 2: Mains Parallel Operation (setpoint = rated power)

• Current power setpoint of the generator = 200 kW (100%)
• Max. power deviation = 40% (80 kW)
Fig. 274: Derating: Mains parallel operation; setpoint = rated power
If the engine is running and the LogicsManager "Free derating" is TRUE, the unit
monitors the water temperature. If the water temperature remains below the value
“Start derating at”, the reduction becomes not active and remains on 0%. If the water
temperature increases and so exceeds the value “Start derating at” the reduction
becomes active (the unit starts to derate the current active power setpoint). The rate of
reduction (slope) is determined by the values of “Start derating at”, “Stop derating at”,
and "Max. power deviation" ("Max. power deviation" also defines the minimum power).
The power reduction would increase and so reduce power from 100% at 80 °C down to
60% = 120 kW at 90 °C. Temperature over 90 °C would cause the same reduction of
40% in this example. So it is guaranteed that the engine is not running with too less
load.

6 Application Field
☼ Example 3: Islanded Parallel Operation (IOP)

• Current average utilization of all generators = 95%
• Max. power deviation = 40%
Fig. 275: Derating: Islanded parallel operation
In islanded parallel operation the derating factor is correlated to the utilization factor of
all engines! This becomes the new Maximum for derating.
The engine is running with 95% (190 kW). If the LogicsManager is enabled and
temperature has reached 80 °C the derating becomes effective (the unit starts to derate
the current active power setpoint). If the temperature is 90 °C or higher the maximum
reduction value of 40% becomes active. The current power of 95% will be reduced by
40% to 60%.
95% x 0.6 = 57% ≙ 0.57
This engine will run now with 200 kW x 0.57 = 114 kW.
In islanded parallel operation the derating is limited to 50%. It is not possible to get the
utilization factor lower than 50% by derating function.
If the derating signals are digital (e.g. different relay outputs from a ripple control
receiver; refer to ╚═▷ “6.3.13 Ripple Control Receiver”), the digital signals can be
transformed to an analog signal with a simple set of resistors.
The derating of power has an impact on the Load-Dependent Start/Stop functionality

(refer to ╚═▷ “6.2.1.1 Configuring Load-Dependent Start/Stop”): The start of the next
generator will be shifted.

6 Application Field
6.3.16.3 J1939 (ECU) Derating
6.3.16.3 J1939 (ECU) Derating
General notes
In some conditions -- for example when knocking of the engine is detected -- the ECU
(Engine Control Unit) is requesting a load reduction via J1939 standard message SPN
3644. This message is only supported by some ECUs e.g. Woodward EGS.
To allow J1939 ECU derating parameter 15142 »J1939 derating « must be configured
to »ON«. The derating value of SPN 3644 is defined as a percentage value related to
rated power, with 0% = no derating and 100% = maximum derating (= no load).
If parameter 15142 »J1939 derating «is on and the power P is limited to:
Plim = (100% - derating value) x Prated/ 100%
In islanded parallel operation this behavior does not meet exactly the derating required
by the ECU. Because of the influence of load share, in the first moment the derating is
stronger than required by the ECU.
6.3.17 Examples timer configuration
Example 1:
Each day a function shall be activated from 8.12am to 6.48pm (18:48)
• Configure Timer 1: Hour (ID1652) to 8
• Configure Timer 1: Minute (ID1651) to 12
• Configure Timer 1: Second (ID1650) to 0
• Configure Timer 2: Hour (ID1657) to 18
• Configure Timer 2: Minute (ID1656) to 48
• Configure Timer 2: Second (ID1655) to 0
• Take a LogicsManager equation i.e. Internal flag and configure:
◦ 11.01 Timer 1 AND
◦ 11.02 Timer 2 NOT
• Incorporate this internal flag into the LogicsManager equation which enables the
desired function.
Example 2:
Each working day (Monday to Friday) a function shall be activated at 10.15am for the
duration of 1 minute
• Configure active hour (ID1662) to 10
• Configure active minute (ID1661) to 15
• Configure the active weekdays (ID1670, 1671,1672,1673,1674) to YES

6 Application Field
6.4 CANopen Applications
• Configure the active weekdays (ID1675, 1676) to NO
◦ 11.05 Active hour AND
◦ 11.06 Active minute AND
◦ 11.03 Active weekdays
desired function.
Example 3:
Each day a function shall be activated at 7am for the duration of 1 hour
• Configure active hour (ID1662) to 7
◦ 11.05 Active hour
desired function.
6.4 CANopen Applications
6.4.1 Remote Control
Refer to ╚═▷ “6.3.5 Performing Remote Start/Stop And Acknowledgment” for detailed
information.
The easYgen may start, stop, shut down, or acknowledge alarms with CAN/Modbus.
A Remote Shutdown 03.40 can be configured via LogicsManager internal flag (e.g.12230
Flag 1) combined with a free alarm LogicsManager (e.g. Free alarm 1) configured with
shutdown alarm class.
Two different methods to perform a remote start/stop/Acknowledgment using 04.13

Remote request and 04.14 Remote acknowledge are detailed in the below.
These are "Remote start/stop/Acknowledgment via RPDO" and "Remote start/stop/

Acknowledgment via default SDO communication channel". The advantages and the
disadvantages of these two methods are as follows.

6 Application Field
6.4.1.1.1 RPDO
RPDO Default SDO communication channel
Classical communication for CANopen devices Configuration process
One message Two messages
No validation of the received answer Validation answer, if message has been received by the
unit
Only working in operational mode May take longer in case of communication with two
messages
Tab. 108: Comparison
6.4.1.1.1 RPDO
Configure CAN interface 1
CANopen Master (parameter ╚═▷ 8993) must be enabled, if there is no PLC taking over
the master function.
1. ▷ Either on the front panel or using ToolKit navigate to menu [Configure CAN interface /
Configure CAN interface 1].
2. ▷ Configure the parameter listed below.
8993 CANopen On CANopen Master is enabled.

Master
Configure RPDO
1. ▷ Either on the front panel or using ToolKit navigate to menu [Configure CAN interface 1 /
Receive PDO 1].
9300 COB-ID 00000201 COB-ID set to 00000201.

(hex)
9910 Number of 1 One mapped object is configured

Mapped
Objects
9911 1. Mapped 00503 The 1st mapped object is set to control parameter 503.
Object
▶ Setting the COB-ID to 201 (hex) is exemplary; usually, the PDOs are in the
range of 181 (hex) to 57F (hex).

6 Application Field
6.4.1.1.2 Default SDO Communication Channel
With this setting, the Receive PDO is configured to overtake the received data coming in
by COB-ID 201 into the ID 503. The number of mapped objects is here 1.
Refer to ╚═▷ “9.2.9 Additional Data Identifier” for a list of additional

parameter groups.
CANopen message
The following table shows four data examples the device is receiving on the CANopen
bus. These data are sent as TPDO to the device (COB-ID 201). The settings above map
the received data to the easYgen address ID 503.
ID (hex) Description Data (hex)
201 Remote Start 01 00
201 Remote Stop 02 00
201 Remote Acknowledge sequence of:
0000, 10 00; 0000, 1000
Notes
The message 1000hex must be sent

twice to acknowledge an alarm
completely. The first rising edge
(0000hex followed by 1000hex) disables
the horn and the second rising edge
resets the alarm.
201 Remote Shutdown 00 02
Another possibility for a remote start/stop/Acknowledgment is to send the request via

default SDO communication channel. The device listens to the CAN ID 600 (hex) + Node-
ID internally to perform the desired control, the reply is on CAN ID 580 (hex) + Node-ID.
The following examples show the request format on CANopen with different Node-IDs.
The request on the bus is sent via the control parameter ID 503 of the device.
The value 2000 (hex) is calculated internally:
• 503 (dec) -- 1F7 (hex)
• 1F7+2000 (hex) = 21F7 (hex)
Please note that high and low bytes are exchanged in the sent address. The data (hex)
shows the state of parameter 503 to achieve the required control.
Node-ID 1 (standard value)
The following table shows exemplary request data for the device on the CANopen bus.

6 Application Field
601 Remote Start 2B F7 21 01 01 00 00 00
601 Remote Stop 2B F7 21 01 02 00 00 00
2B F7 21 01 00 00 00 00, 2B F7 21 01 10
00 00 00; 2B F7 21 01 00 00 00 00, 2B F7
21 01 10 00 00 00;
Notes
The message 2B F7 21 01 10 00 00 00
must be sent twice to acknowledge an
alarm completely. The first rising edge
(2B F7 21 01 00 00 00 00 followed by 2B
F7 21 01 10 00 00 00) disables the horn
and the second rising edge resets the
alarm.
601 Remote Shutdown 2B F7 21 01 00 02 00 00
Node-ID (not standard value)
If the Node-ID of the device is intended to be different from the standard value, the
parameter "Node-ID CAN bus 1" (parameter ╚═▷ 8950) must be configured accordingly.
Node-ID 2 is used in the following example.
8950 Node-ID 002 (hex) Node-ID set to 002.

CAN bus 1
▶ With this setting, the Node-ID of the CAN interface 1 is set to 002.
The request on the bus is sent via the control parameter 503 of the device.
The hexadecimal value 2000 is calculated internally:
• 503 (dec) -- 1F7 (hex)
• 1F7 (hex) + 2000 (hex) = 21F7 (hex)
Please note that high and low bytes are exchanged in the sent address.
The data (hex) shows the state of parameter 503 to achieve the required control.

6 Application Field
602 Remote Start 2B F7 21 01 01 00 00 00
602 Remote Stop 2B F7 21 01 02 00 00 00
2B F7 21 01 00 00 00 00, 2B F7 21 01 10
00 00 00; 2B F7 21 01 00 00 00 00, 2B F7
21 01 10 00 00 00;
Notes
The message 2B F7 21 01 10 00 00 00
must be sent twice to acknowledge an
alarm completely. The first rising edge
(2B F7 21 01 00 00 00 00 followed by 2B
F7 21 01 10 00 00 00) disables the horn
and the second rising edge resets the
alarm.
602 Remote Shutdown 2B F7 21 01 00 02 00 00
Additional SDO communication channels
It is also possible to allow several PLCs to start/stop/acknowledge the unit in addition to

the default SDO communication channel. Four additional SDO communication channels
are provided for this. The additional SDO 127 (dec) is used in the following example.
Additional Server SDOs].
12801 2. Node-ID 127 (dec) SDO communication channel is configured to 127

= 7F (hex)
▶ With this setting, an additional SDO communication channel is configured to 127.
The control request is equal to the request via default SDO communication channel, but
the device will listen to messages including the configured address as well.
The device listens to the CAN ID 600 (hex) + 2. Node-ID internally to perform the desired
control, the reply from the easYgen is sent on CAN ID 580 (hex) + 2. Node-ID.
• Receive CAN ID 67F (hex) (600 (hex) + 7F (hex))
• Receive CAN ID 5FF (hex) (580 (hex) + 7F (hex))
The same is valid for the additional SDO communication channels 3, 4, and 5.
67F Remote Start 2B F7 21 01 01 00 00 00
67F Remote Stop 2B F7 21 01 02 00 00 00

6 Application Field
6.4.1.2 Transmitting A Frequency Setpoint
67F Remote Acknowledge 2B F7 21 01 10 00 00 00
67F Remote Shutdown 2B F7 21 01 00 02 00 00
If parameters are written or read via two or more SDO communication channels at the
same time (before the first has answered), the second one will be refused.
6.4.1.2 Transmitting A Frequency Setpoint
It is possible to transmit a frequency setpoint value via the CANopen protocol.

Prerequisite for the use of a frequency setpoint via an interface is the configuration of the
frequency setpoint sources with AnalogManager ╚═▷ 5518 for frequency setpoint 1 or
AnalogManager ╚═▷ 5519 for frequency setpoint 2. Refer to ╚═▷ “4.4.4.4 Frequency
Control” for detailed information.
The respective frequency setpoint source is to be configured to 05.53 "Interface f setp

[Hz]".
Two different methods to transmit a frequency setpoint via CANopen are detailed below.
These are "Transmitting a frequency setpoint via RPDO" and "Transmitting a frequency
setpoint via default SDO communication channel". The advantages and the
unit
messages
6.4.1.2.1 RPDO

6 Application Field
6.4.1.2.1 RPDO

Master
Configure RPDO
Receive PDO 1].

(hex)

Mapped
Objects
Object
With this setting, the Receive PDO is set to the address, for which the device is listening
on the bus. The number of mapped objects is 1 since 1 mapped object is used. The
request on the bus is sent with the control parameter 509 of the device as mapped
object 1.

parameter groups.
CANopen message
A frequency setpoint of 50.60 Hz is transmitted:
• 5060 (dec) = 13C4 (hex) → C4 13 according to the CANopen protocol
321 Remote F setpoint C4 13

6 Application Field
Another possibility for transmitting a frequency setpoint is to send the value via default
SDO communication channel. The device listens to the CAN ID 600 (hex) + Node-ID
internally to perform the desired control, the reply is on CAN ID 580 (hex) + Node-ID.
The following example shows the send format on CANopen with Node-ID 1.
The value is sent on the bus via the control parameter 509 of the device.
• 509 (dec) -- 1FD (hex)
• 1FD (hex) + 2000 (hex) = 21FD (hex)
Please note that high and low bytes are exchanged in the sent value.
601 Remote F setpoint 2B FD 21 01 C4 13 00 00
6.4.1.3 Transmitting A Voltage Setpoint
It is possible to transmit a voltage setpoint value via the CANopen protocol. Prerequisite
for the use of a voltage setpoint via an interface is the configuration of the voltage
setpoint sources with AnalogManager ╚═▷ 5618 for voltage setpoint 1 or AnalogManager
╚═▷ 5619 for voltage setpoint 2 .
Refer to ╚═▷ “4.4.4.1 Voltage Control” for detailed information.
The respective voltage setpoint source is to be configured to 05.59 "Interface V setp [V]".
Using absolute values but NOT % values
With "...-XT" the former used parameters 5618 and 5619 became AnalogManagers with
the same ID but changed from »%« to »V«. AnalogManagers whose Analog result is an
absolute value need absolute input(s). For this example, both »Analog
input« and »Analog result« must be the same type: »Hz«.
With "...-XT" the former used 05.09 "Interface volt.setp." became a % value 05.09
"Interface v setp [%]" and so cannot be used for setpoint transmission because an
absolute value is mandatory! The parameter of the absolute value of the interface
frequency setpoint is 05.59 "Interface v setp [V]".
Two different methods to transmit a voltage setpoint setpoint via CANopen are detailed
below.

6 Application Field
6.4.1.3.1 RPDO
These are "Transmitting a voltage setpoint via RPDO" and "Transmitting a voltage setpoint
via default SDO communication channel". The advantages and the disadvantages of
these two methods are as follows.
unit
messages
6.4.1.3.1 RPDO

Master
Configure RPDO
Receive PDO 1].

(hex)

Mapped
Objects
Object

6 Application Field
object 1.

parameter groups.
CANopen message
The following table shows exemplary send data for the device on the CANopen bus in line
1.
A voltage setpoint of 412 V is transmitted:
• 412 (dec) = 019C (hex) → 9C 01 according to the CANopen protocol
321 Remote V setpoint 9C 01 00 00
Another possibility for transmitting a voltage setpoint is to send the value via default SDO
communication channel. The device listens to the CAN ID 600 (hex) + Node ID internally
to perform the desired control, the reply is on CAN ID 580 (hex) + Node ID.
The following example shows the send format on CANopen with Node ID 1.
• 510 (dec) - 1FE (hex)
• 1FE (hex) + 2000 (hex) = 21FE (hex)
601 Remote V setpoint 23 FE 21 01 9C 01 00 00

6 Application Field
6.4.1.4 Transmitting A Power Factor Setpoint
6.4.1.4 Transmitting A Power Factor Setpoint
It is possible to transmit a power factor setpoint value via the CANopen protocol.
Prerequisite for the use of a power factor setpoint via an interface is the configuration of
the power factor setpoint source (parameter ╚═▷ 5638 for power factor setpoint 1 source
or parameter ╚═▷ 5639 for power factor setpoint 2 source)
Refer to ╚═▷ “4.4.4.2 Power Factor Control” for detailed information.
The respective power factor setpoint source is to be configured to 05.12 "Interface PF

setp.".
Two different methods to transmit a power factor setpoint via CANopen are detailed
below.
These are "Transmitting a power factor setpoint via RPDO" and "Transmitting a power
factor setpoint via default SDO communication channel". The advantages and the
unit
messages
6.4.1.4.1 RPDO

Master

6 Application Field
6.4.1.4.1 RPDO
Configure RPDO
Receive PDO 1].

(hex)

Mapped
Objects
Object
object 1.

parameter groups.
CANopen message
The following table shows exemplary send data for the device on the CANopen bus. A
power factor setpoint of 0.85 capacitive/leading is transmitted (64689 (dec) [65536-850]
= FCAE (hex) → AE FC according to the CANopen protocol) in line 1. Please note that
negative (capacitive or leading) power factor values are deducted from 65536 (dec) or
FFFF (hex).
A power factor setpoint of 0.9 inductive/lagging is transmitted in line 2:
• 900 (dec) = 0384 (hex) → 84 03 according to the CANopen protocol.
A power factor setpoint of 1.0 is transmitted in line 3:
• 1000 (dec) = 03E8 (hex) → E8 03 according to the CANopen protocol
321 Remote PF Ld 085 AE FC
321 Remote PF LG 090 84 03

6 Application Field
321 Remote PF 1.00 E8 03
Another possibility for transmitting a power factor setpoint is to send the value via default
SDO communication channel. The device listens to the CAN ID 600 (hex) + Node-ID
internally to perform the desired control, the reply is on CAN ID 580 (hex) + Node-ID.
• 508 (dec) -- 1FC (hex)
• 1FC (hex) + 2000 (hex) = 21FC (hex)
601 Remote PF Ld 085 2B FC 21 01 AE FC 00 00
601 Remote PF LG 090 2B FC 21 01 84 03 00 00
601 Remote PF 1.00 2B FC 21 01 E8 03 00 00
6.4.1.5 Transmitting A Power Setpoint
It is possible to transmit a power setpoint value via the CANopen protocol. Prerequisite for
the use of a power setpoint via an interface is the configuration of the power setpoint
sources with AnalogManager ╚═▷ 5539 for power setpoint 1 or AnalogManager ╚═▷ 5540
for power setpoint 2.
Refer to ╚═▷ “4.4.4.5 Load Control” for detailed information).
The respective power setpoint source is to be configured to 05.56 "Interface P setp [kW]".

6 Application Field
6.4.1.5.1 RPDO
Using absolute values but NOT % values
With "...-XT" the former used parameters 5539 and 5540 became AnalogManagers with
the same ID but changed from »%« to »W«. AnalogManagers whose Analog result is an
absolute value need absolute input(s). For this example, both »Analog
input« and »Analog result« must be the same type: »W«.
With "...-XT" the former used 05.06 "Interface pow. setp." became a % value 05.06
"Interface P setp [%]" and so cannot be used for setpoint transmission because an
absolute value is mandatory! The parameter of the absolute value of the interface power
setpoint is 05.56 "Interface P setp [kW]".
Please note that the type of the power setpoint (Steady, Import, or Export) must also be
defined (parameter ╚═▷ 5526 for load setpoint 1 or parameter ╚═▷ 5527 for load setpoint
2).
Two different methods to transmit a power setpoint via CANopen are detailed below.
These are "Transmitting a power setpoint via RPDO" and "Transmitting a power setpoint
via default SDO communication channel". The advantages and the disadvantages of
these two methods are as follows.
unit
messages
6.4.1.5.1 RPDO

Master

6 Application Field
Configure RPDO
Receive PDO 1].

(hex)

Mapped
Objects
Object
object 1.

parameter groups.
CANopen message
1.
A power setpoint of 1000.0 kW is transmitted:
• 10000 (dec) = 2710 (hex) → 10 27 according to the CANopen protocol
321 Remote P setpoint 10 27 00 00
Another possibility for transmitting a power setpoint is to send the value via default SDO
communication channel. The device listens to the CAN ID 600 (hex) + Node-ID internally
to perform the desired control, the reply is on CAN ID 580 (hex) + Node-ID.

6 Application Field
6.4.1.6 Transmitting Multiple Setpoints
• 507 (dec) -- 1FB (hex)
• 1FB (hex) + 2000 (hex) = 21FB (hex)
601 Remote P setpoint 23 FB 21 01 10 27 00 00
The table above shows exemplary send data for the device on the CANopen bus in line 2.
6.4.1.6 Transmitting Multiple Setpoints
A single RPDO can transmit multiple objects. The receive PDO can be used for four
objects with 16 bits (2 bytes).
If larger objects - for example 32 bits (4 bytes), like for voltage and power setpoints - are
used, the maximum number of objects is reduced.
Configure RPDO
Receive PDO 1].

(hex)
9910 Number of 3 Three mapped objects are configured

Mapped
Objects
Object
9912 2. Mapped 00507 The 2nd mapped object is set to control parameter 507.
Object
9913 3. Mapped 00508 The 3rd mapped object is set to control parameter 508.
Object

6 Application Field
6.4.1.7 Remotely Changing The Setpoint
request on the bus is sent with the control parameters 509, 507, and 508 of the device
as mapped object 1.

parameter groups.
CANopen message
1. The following setpoints are transmitted:
• Frequency 50.6 Hz (5060 (dec) = 13C4 (hex) → C4 13 according to the CANopen

protocol)
• Power 1000 kW (10000 (dec) = 2710 (hex) → 10 27 according to the CANopen

protocol)
• Power factor 0.9 lagging (900 (dec) = 0384 (hex) → 84 03 according to the CANopen
protocol)
321 Remote F P PF setpoint C4 13 10 27 00 00 84 03
Additionally/alternatively to remotely changing the control setpoints, it is possible to use

"remote" setpoints (values) defined via interface instead of the internal setpoints as data
source in the respective controller. For example, use data source "05.53 Interface f setp
[Hz]" instead of "05.51 Internal f setp1 [Hz]" in AnalogManager ╚═▷ 5518 (Freq. setpoint
1) to transmit a frequency setpoint via interface.
Two different methods for remotely switch between setpoints via CANopen are detailed
below.
These are switching between setpoints via »RPDO« or »Default SDO communication
channel«. The advantages and the disadvantages of these two methods are as follows:
unit

6 Application Field
6.4.1.7.1 RPDO
messages
Tab. 113: Comparison CANopen methods
6.4.1.7.1 RPDO

Master
Configure RPDO
Receive PDO 1].

(hex)

Mapped
Objects
Object
object 1.

6 Application Field
CANopen message
The following table shows exemplary send data for the device on the CANopen bus. The
respective bits are enabled by sending the data of the respective lines.
321 Remote P setpoint 2 80 00
321 Remote PF setpoint 2 40 00
321 Remote F setpoint 2 20 00
321 Remote V setpoint 2 10 00
Another possibility for changing a setpoint is to enable the bit via default SDO
to perform the desired control, the reply is on CAN ID 580 (hex) + Node-ID.
The value is sent on the bus via the control parameter ID 504 of the device.
• 504 (dec) -- 1F8 (hex)
• 1F8 (hex) + 2000 (hex) = 21F8 (hex)
601 Remote P setpoint 2 2B F8 21 01 80 00 00 00
601 Remote PF setpoint 2 2B F8 21 01 40 00 00 00
601 Remote F setpoint 2 2B F8 21 01 20 00 00 00
601 Remote V setpoint 2 2B F8 21 01 10 00 00 00
6.4.1.8 Transmitting A Remote Control Bit
It is possible to transmit a remote control bit via the CANopen protocol. Such a remote
control bit can be sent by a PLC to remotely control the easYgen if this remote control bit
is used as a command variable in a LogicsManager function.

6 Application Field
Configure RPDO
Receive PDO 1].

(hex)

Mapped
Objects
Object
object 1.

parameter groups.
CANopen message
Remote control bit 1 is set:
• 1 (dec) = 0001 (hex) → 01 00 according to the CANopen protocol
334 Remote Control Bit 1 (PDO) 01 00
Another possibility for transmitting a power setpoint is to send the value via default SDO
to perform the desired control, the reply is on CAN ID 580 hex) + Node-ID.

6 Application Field
6.4.2 Sending A Data Protocol via TPDO
• 249 (dec) -- 1F9 (hex)
• 1FB (hex) + 2000 (hex) = 21F9 (hex)
601 Remote Control Bit 1 (SDO) 2B F9 21 01 01 00 00 00
The table above shows exemplary sends data for the device on the CANopen bus in line
2.
6.4.2 Sending A Data Protocol via TPDO
This is a configuration example for sending an object (data protocol 5003) on CAN ID 2AE
(hex) every 20 ms on TPDO1. For this, TPDO1 must be configured as follows:
Transmit PDO 1].
9600 COB-ID 000002AE COB-ID set to 000002AE.

(hex)
9602 Transmission 255 The number of required sync messages is set to 255.
type
9604 Event timer 20 ms Object is sent every 20 ms.
8962 Selected 5003 Data protocol 5003 is used.

data
protocol
9609 Number of 0 No mapped object is configured

Mapped
Objects
The data to be sent (Mapped Objects) may be provided on request by configuring the
Sync Message (parameter ╚═▷ 9100) and the Transmission Type (parameter ╚═▷ 9602,
╚═▷ 9612, ╚═▷ 9622, ╚═▷ 9632, or ╚═▷ 12793) of a TPDO. The unit is requested to send
its data by sending a Sync Message.
The number of required Sync Messages is determined by the setting of the Transmission
Type.

6 Application Field
6.4.3 Troubleshooting
If the data is to be sent on request, Bit 30 of the Sync Message (parameter ╚═▷ 9100)
must be configured to "0" and the CANopen Master (parameter ╚═▷ 8993) function must
be configured to "Off".
Additional example
The Transmission Type of TPDO 1 (parameter ╚═▷ 9602) is configured to "2" in the
following example. This means that a message of the configured TPDO is sent by the unit
after two Sync Messages have been sent to the unit.
Transmit PDO 1].
9600 COB-ID 000002AE COB-ID set to 000002AE.

(hex)
9602 Transmission 2 The number of required sync messages is set to 2.

type
9604 Event timer 20 ms Object is sent every 20 ms.
8962 Selected 5003 Data protocol 5003 is used.

data
protocol
9609 Number of 0 No mapped object is configured

Mapped
Objects
The recorded data shows that the data of the Mapped Object (in this example Mux 5) is
sent (╚═▷ Tab. 114) after sending the Sync Message twice (╚═▷ Tab. 115).
80 - -
Tab. 114: Cyclical sending of data - sync message request
No. Count ID (hex) Data (hex)
1 2 80 -
2 1 2AE 8B 13
Tab. 115: Cyclical sending of data - reply
6.4.3 Troubleshooting
General diagnosis
Error Possible diagnosis
Connected device (Phoenix I/O board) Are all LEDs at the expansion modules illuminated green (i.e. correctly
cannot be configured connected)?

6 Application Field
6.5 Modbus Applications
Are all modules detected (i.e. no blinking expansion module)?
CAN interface 1 (guidance level) diagnosis
No data is sent by the Woodward Is the unit in operational mode (heartbeat - CAN ID 700 (hex) + Node-ID has the
controller content 5 (hex)?
Are the TPDOs correctly configured (CAN ID, mapping, parameter)?
No data is received by the Woodward Is the unit in operational mode (heartbeat - CAN ID 700 (hex) + Node-ID has the
controller content 5 (hex)?
Are the RPDOs correctly configured (CAN ID, mapping, parameter)?
No monitoring bit data is received on Is the CAN bus connected correctly?

the RPDO
Is the baud rate configured correctly?
Is the CAN ID assigned more than once?
Is the unit in operational mode? If not, start it via another device or put in NMT
Master (parameter ╚═▷ 8993).
No SDOs (configuration messages) are received by the unit
No SDOs (configuration messages) are Is the CAN ID assigned more than once?
received by the unit
Is the CAN ID 600 (hex) + Node-ID of the easYgen already used in a PDO (COB-
ID)?
Are RPDOs or TPDOs higher then 580 (hex) or lower than 180 (hex) used?
6.5 Modbus Applications
Data Format(s)
Modbus registers are read and written according to the Modbus standard as Big-endian.
Composite data types like LOGMAN, ANALOGMANAGER, and TEXT use separate
descriptions.
6.5.1 Remote Control
The Woodward controller may be configured to perform start/stop/Acknowledgment

functions remotely through the Modbus protocol. The required procedure is detailed in the
following steps.
Please find remote control parameter 505 described at: ╚═▷ “ Remote control word 3”. It
works similar like 503 described below.

6 Application Field
The following descriptions refer to the remote control parameter 503 as described in ╚═▷
“9.2.9 Additional Data Identifier”.
It may be necessary to shift the address by 1 depending on the used PC software. In this
case, the address would be 504 for example.
Be sure to check both possibilities in case of remote control problems.
ID Parameter Setting range Data type
503 Remote control word 1 0 to 65535 UNSIGNED 16
• Modbus address = 40000 + (Par. ID +1) = 40504
In order to issue a command, the respective bit of object 21F7 (hex), i.e. parameter 503,
must be enabled. The following bits are used for this:
• Bit 0 Start bit:
This bit activates the LogicsManager command variable 04.13 "Remote request" and
enables a remote start.
• Bit 1 Stop bit:
This bit deactivates the LogicsManager command variable 04.13 "Remote request"
and disables a remote start.
• Bit 4 Acknowledgment bit:
This bit activates the LogicsManager command variable 04.14 "Remote

acknowledge". This bit must be set and reset twice to acknowledge an alarm
completely. The first rising edge disables the horn and the second rising edge resets
the alarm.
• Bit 9 Shutdown Command bit:
This bit activates the LogicsManager command variable 03.40 "Remote Shutdown-
Status". With this function the engine is immediately shut down without auxiliary
service and cool down. This works independent from beaker conditions.
The following Modscan32 screenshot (╚═▷ Fig. 276) shows the configurations made to
remote control parameter 503. It is possible to set the format to binary to view single bits
using the "display options".
Fig. 276: Modbus - remote control parameter 503

6 Application Field
Example 1: Start Request
Fig. 277: Modbus - write register - start request
By double-clicking the address, a Write Register command may be issued.
╚═▷ Fig. 277 shows how bit 0 is set using the ModScan32 Software.
Example 2: Stop Request
Fig. 278: Modbus - write register - stop request
Example 3: External Acknowledge
Fig. 279: Modbus - write register - external acknowledge
Example 4: Shutdown Command

6 Application Field
Fig. 280: Modbus - write register - shutdown command
Sample for Free alarm 1
This (remote) shutdown request can be taken by LogicsManager equation 12230 to set
Flag 1 (see ╚═▷ Fig. 281). To perform an immediately shutdown, the free alarm has to be
configured as alarm class F. Free alarm 1 configuration ╚═▷ Fig. 282 shows how the
Monitoring source LM ╚═▷ 8120 »Free alarm 1« is set to Flag 1 and the Alarm class 8121
is set to Class F.
Fig. 281: LM 12230 Flag1

6 Application Field
6.5.1.2 Setpoint Setting
Fig. 282: LM Free-Alarms
Fig. 283: Setpoint source selection
For a remote setting of the control setpoints, it is necessary to use the interface setpoints
instead of the internal setpoints.
For example, use data source 05.56 "Interface P setp [kW]" in AnalogManager ╚═▷ 5539
(AM ActPower SP1 [kW]) to transmit a load setpoint via interface. No password is required
to write this value.
Screen shots beside show an exemplary configuration of the load setpoint 1 source. All
other setpoint sources are configured accordingly.

6 Application Field
Fig. 284: Setpoint configuration
The interface setpoints may be set using the objects for active power, power factor,
frequency, and voltage (refer to ╚═▷ “9.2.9 Additional Data Identifier” for detailed
information).
ID Parameter Setting range Unit Data type Data source
507 Active Power Setpoint 0 to 999999 1/10 kW INTEGER 32 05.56
508 Power Factor Setpoint -710 to 1000 to - INTEGER 16 05.12

710
509 Frequency Setpoint 0 to 7000 1/100 Hz UNSIGNED 16 05.53
510 Voltage Setpoint 50 to 650000 V UNSIGNED 32 05.59
☼ Example 1: Active power interface setpoint
The active power setpoint value must be written to object 21FB (hex), i.e. parameter
507.
A power value of 50 kW = 500 (dec) = 01F4 (hex) is to be transmitted.

• Modbus length = 2 (INTEGER 32)
The high word must be written to the lower address and the low word must be written to
the higher address.
ᐳ To set the parameter address in ModScan32:

1. ▷
Fig. 285: Modscan32 at address 40508

6 Application Field
Open the "Preset Multiple Registers" dialog by selecting [Setup / Extended / Preset Regs]
from the menu.
2. ▷
Fig. 286: "Preset Multiple Registers" dialog 1
Select »OK« and enter the desired values.

3. ▷
Fig. 287: "Preset Multiple Registers" dialog 2
Select »Update« to confirm the entered values.

▶ The dialog closes and the values are changed.
☼ Example 2: Power factor interface setpoint
The power factor setpoint value must be written to object 21FC (hex), i.e. parameter
508.
A power factor of 1 = 1000 (dec) = 03E8 (hex) is to be transmitted.


6 Application Field
1. ▷
Analogous to ╚═▷ Chapter 6.5.1.2 set the parameter address as shown in ╚═▷ Fig. 289.
☼ Example 3: Frequency interface setpoint
The frequency setpoint value must be written to object 21FD (hex), i.e. parameter 509.
A frequency value of 50.00 Hz = 5000 (dec) = 1388 (hex) is to be transmitted.


1. ▷
☼ Example 4: Voltage interface setpoint
The voltage setpoint value must be written to object 21FE (hex), i.e. parameter 510.
A voltage value of 400 V = 400 (dec) = 0190 (hex) is to be transmitted.

The high word must be written to the lower address and the low word must be written to
the higher address.

6 Application Field

1. ▷
☼ Example
Fig. 292: Remotely switch Setp. 2 load
The active power setpoint 2 is to be enabled. Therefore LM 12919 is prepared using

04.40 (see beside).
The switching signal than comes remotely e.g. as described below:

ᐳ To set the bits in ModScan32:

1. ▷
Fig. 293: ModScan32 single bit view
Using the "display options" set the format to binary to view single bits (╚═▷ Fig. 293).

6 Application Field
2. ▷ Double-click the address to issue a Write Register command.

▶
Fig. 294: Active power setpoint
╚═▷ Fig. 294 shows how bit 7 is set to enable the active power setpoint 2.
Fig. 295: Power factor setpoint
╚═▷ Fig. 295 shows how bit 6 would be set to enable the power factor setpoint 2.
Fig. 296: Frequency setpoint
╚═▷ Fig. 296 shows how bit 5 would be set to enable the frequency setpoint 2.
Fig. 297: Voltage setpoint
╚═▷ Fig. 297 shows how bit 4 would be set to enable the voltage setpoint 2.
Additionally/alternatively to remotely changing the control setpoints, it is possible to use

"remote" setpoints (values) defined via interface instead of the internal setpoints as data
source in the respective controller. For example, use data source "05.53 Interface f setp
[Hz]" instead of "05.51 Internal f setp1 [Hz]" in AnalogManager ╚═▷ 5518 (Freq. setpoint
1) to transmit a frequency setpoint via interface.

6 Application Field
6.5.2 Changing Parameter Settings
6.5.2 Changing Parameter Settings
6.5.2.1 Parameter Setting
The example tables below are excerpts. Refer to the following chapters for the complete
parameter lists:
• ╚═▷ “4.3.4 Enter Password”

• ╚═▷ “4.6 Configure Measurement”
Be sure to enter the password for the code level that is needed to get access for
changing parameter settings via the preferred interface.
The new entered value must comply with the parameter setting range when changing
the parameter setting.
Example 1: Addressing the generator rated voltage
1766 Generator rated voltage 50 to 650000 V UNSIGNED 32
☼ Example

1. ▷
Set the configuration to address parameter 1766 as shown in ╚═▷ Fig. 298.

6 Application Field
6.5.2.2 Configuration Of LogicsManager Functions
Example 2: Addressing the generator voltage measuring
1851 Generator voltage measuring 3Ph 4W UNSIGNED 16
3Ph 3W
1Ph 2W
1Ph 3W
☼ Example

If the setting range contains a list of parameter settings like in this example, the
parameter settings are numbered and start with 0 for the first parameter setting. The
number corresponding with the respective parameter setting must be configured.
1. ▷
Set the configuration to address parameter 1851 as shown in (╚═▷ Fig. 299).
▶ The parameter is configured to "3Ph 4W".
Next to HMI and ToolKit, LogicsManager can also be configured via Modbus.
• The complete LogicsManager instruction set is available for Modbus control.
• Hex code equivalents are defined for all LogicsManager settings.
• The Modbus definition for a LogicsManager equation consists of 7 data words

following a well defined sequence.

6 Application Field
Word 0 Word 1 Word 2 Word 3 Word 4 Word 5 Word 6
Delay ON Delay OFF Logic Logic equation Command 1 Command 2 Command 3

equation 1 2
Tab. 116: 7 words Modbus message
To send a LogicsManager function via Modbus follow these steps:
1. ▷ Define your LogicsManager equation

2. ▷ Describe the LogicsManager equation as "command chain" in hex code
3. ▷ Send the message via Modbus
Describe the LogicsManager equation as "command chain" in hex code (step 2)
The LogicsManager screens below show parts of the command chain. How to generate
hex code words is described for each part of the Modbus message.
Fig. 300: LogicsManager command chain words 0 and 1
Word 0 and word 1 contain the hex code of the Delay times but in the reverse order of
double-byte words, i.e. low byte before high byte.

6 Application Field
Fig. 301: LogicsManager command chain words 4, 5, and 6
Words 4, 5, and 6 contain the hex codes of the respective command variable ID's decimal
value but in the reverse order of double-byte words, i.e. low byte before high byte.
The command variable prefix e.g., "04.13" is the number of the command variable not
it's ID.
Refer to ╚═▷ “9.3.2 Logical Command Variables” for the command variable IDs.

6 Application Field
Fig. 302: LogicsManager command chain words 2 and 3
Words 2 and 3 contain a sequence of nibbles each representing a sign or operator of the
equation.
The Data words table below shows the sequence how to arrange the LogicsManager
setting that build the command chain.
Word 2 Word 3
Sign 1 Operator 1 Sign 2 Operator 2 Sign 3 not used not used not used
Tab. 117: Data words 2 and 3 - details of the logic equations
Please find the hex code equivalents on the table below:
Signs Operators
"NOT" 0 "AND" 0
"—" 1 "NAND" 1
"TRUE" 2 "OR" 2
"FALSE" 3 "NOR" 3
"XOR" 4
"NOT-XOR" 5
Tab. 118: Hex code equivalents of the logic equations' nibbles
The hex code of words 2 and 3 is taken "as is" ¾ don't swap high byte and low byte.

6 Application Field
Write the Modbus message (step 3)
It may be necessary to shift the address by 1 depending on the software you use for
Modbus communication.
1. ▷ Copy the complete message of 7 words to the address [parameter number +1] in one
step.
Delay ON Delay OFF Logic equation 1 Logic equation 2 Command Command Command
1 2 3
low high low high Sign Ope‐ Sign Ope‐ Sign 0x00 0x00 0x00 low high low high low high
byte byte byte byte 1 rator 2 rator 3 byte byte byte byte byte byte
1 2
Tab. 119: 7 words Modbus message in detail
Example
Fig. 303: LogicsManager command chain sample 12120
Delay ON Delay OFF Logic equation 1 Logic equation 2 Command Command Command
1 2 3

6 Application Field
6.5.2.3 Configuration Of LogicsManager Functions For Remote Access
3.00 sec 10.00 sec ¾ Or False Or ¾ -/- -/- -/- No. 09.02 No. 00.08 No. 04.13
ID = ID = ID =
520 dec, 7 dec, 251 dec,

0208 hex 0007 hex 00FB hex
low high low high Sign Ope‐ Sign Ope‐ Sign 0x00 0x00 0x00 low high low high low high
byte byte byte byte 1 rator 2 rator 3 byte byte byte byte byte byte
1 2
2C 01 E8 03 1 2 3 2 1 0 0 0 08 02 07 00 FB 00
Tab. 120: 7 words Modbus message sample 12120 in detail
The Modbus message for the LogicsManager equation used for description above is
2C01 / E803 / 1232 / 1000 / 0802 / 0700 / FB00 (hex).
6.5.2.3 Configuration Of LogicsManager Functions For Remote Access
6.5.2.3.1 Basic remote control functions
The following chapters describe how to parametrize the LogicsManager via Modbus for
the following basic remote control functions:
• Change to AUTOMATIC mode: 12510 Operat. mode AUTO
• Remote request start/stop: 12120 Start req. in AUTO
• Remote acknowledge: 12490 Ext. acknowledge
• Remote shutdown: 11669 Remote Shutdown-status
• Start without load: 12540 Start w/o load
6.5.2.3.2 Configuration of the LogicsManager "Operation mode AUTO"
To fix the operating mode use the LogicsManager function 86.16 "Operat. mode AUTO"
The operating mode AUTO LogicsManager function (parameter ╚═▷ 12510) can be
configured in two different ways:
• 1. Automatic operating mode is always enabled
• 2. Automatic operating mode is enabled via discrete input
Refer to ╚═▷ “6.3.5 Performing Remote Start/Stop And Acknowledgment” for a detailed
configuration of the LogicsManager via HMI or ToolKit.

6 Application Field
6.5.2.3.2 Configuration of the LogicsManager "Operation mode AUTO"
Example
Fig. 304: LogicsManager function sample 12510
To configure the "Operat. mode AUTO" LogicsManager function (parameter ╚═▷ 12510)
as indicated in (╚═▷ Fig. 304) the following Modbus message must be sent to the
easYgen:
See table ╚═▷ Tab. 121 below
* see ╚═▷ Tab. 118 for reference
1. ▷
Copy the complete message of 7 words to address 12511 ff (12510+1) in one step.
This is shown in ╚═▷ Fig. 305 using the ModScan32 software.
Delay ON Delay OFF Logic equation 1* Logic equation 2* Command Command Command
1 2 3
Sign Op. Sign Op. Sign -/- -/- -/-
1 1 2 2 3
0.00 sec 0.00 sec ¾ And True And True 00 00 00 No. 09.09 No. 96.01 No. 96.01
ID = ID = ID =
527 dec 0 dec 0 dec
0000 (hex) 0000 (hex) 1 0 2 0 2 0 0 0 020F (hex) 0000 (hex) 0000 (hex)
low high low high "as is" "as is" low high low high low high
byte byte byte byte byte byte byte byte byte byte

6 Application Field
6.5.2.3.3 Configuration Of Remote Start/Stop, Shutdown, And Acknowledgment
0000 (hex) 0000 (hex) 1020 (hex) 2000 (hex) 0F02 (hex) 0000 (hex) 0000 (hex)
Tab. 121: "Operat. mode AUTO" message
If an shutdown alarm of alarm class C through F occurs in AUTOMATIC operating mode,

the control does not return to STOP operating mode if the alarm is cleared after
acknowledgment. This means that a restart is initiated.
6.5.2.3.3 Configuration Of Remote Start/Stop, Shutdown, And Acknowledgment
The easYgen may start, stop, shut down, or acknowledge alarms with CAN/Modbus.
6.5.2.3.4 Configuration Of LogicsManager Function "Start Request in AUTO"
The "Start req. in AUTO" LogicsManager function (parameter ╚═▷ 12120) can be
configured in a way that a start request in AUTOMATIC operating mode is enabled as soon
as a remote request is issued.
The remote request may be enabled by setting bit 0 (start) of the remote control word
503 to HIGH and may be disabled by setting bit 1 (stop) of the remote control word 503 to
HIGH (refer to ╚═▷ “9.2.9 Additional Data Identifier”).

6 Application Field
6.5.2.3.4 Configuration Of LogicsManager Function "Start Request in AUTO"
Example
To configure the "Start req. in AUTO" LogicsManager function (parameter ╚═▷ 12120) as
indicated in (╚═▷ Fig. 306) the following Modbus message must be sent to the easYgen:
See table ╚═▷ Tab. 122 below.
1. ▷
This is shown in (╚═▷ Fig. 307) using the ModScan32 software.
Word Word 1 Word 2 Word 3 Word 4 Word 5 Word 6

1 2 3
6 Application Field
6.5.2.3.5 Configuration Of LogicsManager Function "External Acknowledge"
6.5.2.3.5 Configuration Of LogicsManager Function "External Acknowledge"
The "Ext. acknowledge" LogicsManager function (parameter ╚═▷ 12490) can be

configured in a way that an external acknowledgment is performed as soon as the remote
acknowledge signal is enabled.
External acknowledge may be enabled by setting bit 4 (external acknowledge) of the

remote control word 503 to HIGH (refer to ╚═▷ “9.2.9 Additional Data Identifier”).
Example
To configure the "External acknowledge" LogicsManager function (parameter ╚═▷

12490) as indicated in (╚═▷ Fig. 308) the following Modbus message must be sent to the
easYgen:
1. ▷
1 2 3
1 1 2 2 3
0.00 sec 0.00 sec ¾ Or ¾ Or False 00 00 00 No. 09.05 No. 04.14 No. 96.01
ID = ID = ID =
252 dec 0 dec

6 Application Field
6.5.2.3.6 Configuration Of LogicsManager Function "Start w/o Load"

523 dec
0000 (hex) 0000 (hex) 1 2 1 2 3 0 0 0 020B 00FC (hex) 0000 (hex)

(hex)
low high low high "as is" "as is" low high low high low high
byte byte byte byte byte byte byte byte byte byte
0000 (hex) 0000 (hex) 1212 (hex) 3000 (hex) 0B02 FC00 (hex) 0000 (hex)
(hex)
Tab. 123: "Ext. acknowledge" message
The Start w/o load LogicsManager function (parameter ╚═▷ 12540) can be configured in a
way that it is always enabled.

6 Application Field
Example
To configure the "Start w/o Load" LogicsManager function (parameter ID ╚═▷ 12540) as
indicated in ╚═▷ Fig. 310 the following Modbus message must be sent to the easYgen:
1. ▷
1 2 3
1 1 2 2 3
0.00 sec 0.00 sec False And True And True 00 00 00 No. 00.01 No. 96.01 No. 96.01
ID = ID = ID =
B37574 easYgen-3000XT Series 0 dec 0 dec 0 dec 795

6 Application Field
6.5.2.4 Remotely Acknowledge Single Alarm Messages
6.5.2.4 Remotely Acknowledge Single Alarm Messages
Single alarm messages can be acknowledged remotely through the Modbus by sending
the respective parameter ID of the alarm to be acknowledged on parameter 522. The
required procedure is detailed in the following steps.
522 Reset alarm list 0 to 65535 UNSIGNED 16
The parameter ID of the alarm to be acknowledged must be written to object 220A (hex),
i.e. parameter 522.
Example
A "Mains undervoltage 1" alarm (ID 3012) shall be acknowledged (refer to ╚═▷ “9.5.5
Alarm Messages”).
Fig. 312: ModScan32 at address 40523
1. ▷ Use the "display options" to set the format to decimal view.
▶
Fig. 313: Write register - acknowledge alarm message
╚═▷ Fig. 313 shows how the parameter ID of the alarm to be acknowledged is written
using the ModScan32 Software.
6.5.2.5 Remotely Clearing The Event History
The event history can be cleared remotely through the Modbus. The required procedure is
detailed in the following steps.

6 Application Field
6.5.2.6 Remotely Resetting The Default Values
1706 Clear eventlog Yes / No UNSIGNED 16
In order to clear the event history, bit 0 of object 26AA (hex), i.e. parameter 1706, must
be enabled.
☼ Remotely clearing event history

1. ▷ Use the "display options" to set the value format to binary.
Fig. 315: Write register - clear event history
╚═▷ Fig. 315 shows how bit 0 is enabled using the ModScan32 Software.
6.5.2.6 Remotely Resetting The Default Values
6.5.2.6.1
10417 Factory settings Yes / No UNSIGNED 16
1701 Reset factory default values Yes / No UNSIGNED 16
In order to enable the resetting procedure, parameter 10417 must be enabled.

6 Application Field
6.5.2.6.1
Example 1 (enable resetting)
The resetting procedure shall be enabled.
1. ▷ Use the "display options" to set the value format to decimal.
▶
Fig. 317: Write register - enable the resetting procedure
╚═▷ Fig. 317 shows how the parameter is enabled using the ModScan32 Software. The
value must be set to "1" to enable the parameter.
Example 2 (reset to default)
In order to reset the default values, parameter ╚═▷ 1701 must be enabled.
CAUTION!
Set factory default settings causes easYgen power cycle!
Don't run ╚═▷ 1701 »Set factory default values« during controlling a genset because it
causes a power cycle of the easYgen control.
The default values shall be reset.

6 Application Field
6.5.3 Exception Responses
1. ▷ Use the "display options" to set the value format to decimal.
▶
Fig. 319: Write register - resetting the default values
╚═▷ Fig. 319 shows how the parameter is enabled using the ModScan32 Software. The
value must be set to "1" to enable the parameter.
6.5.3 Exception Responses
The Modbus protocol has multiple exception responses to show that a request could not
be executed. Exception responses can be recognized if the response telegram contains
the request function code with an offset of 128 (0x80 hex).
╚═▷ Tab. 125 explains possible reasons for an exception response that occurred.
Modbus exception responses
Code Name Reason
01 ILLEGAL FUNCTION The sent request function code is not supported by the Modbus
protocol.
02 ILLEGAL ADDRESS Permission to read/write the parameter is denied.
The amount of requested registers is wrong to read/write this

registers.
03 ILLEGAL DATA VALUE The data value exceeds the min. and max. limitations of the
parameter upon a write request.

6 Application Field
6.5.4 Modbus Telegram Mapper (Customer Written Data Protocols)
Modbus exception responses
Code Name Reason

There is no parameter on the requested address.
Tab. 125: Modbus - exception responses
6.5.4 Modbus Telegram Mapper (Customer Written Data Protocols)
The Modbus Telegram Mapper offers the possibility to generate customer defined Modbus
protocols. It is possible to create individual Modbus Address Point lists for Modbus RTU
and TCP. Therefore the address range (4)50000 can be taken. The user will be able to
arrange contents from the easYgen database (Index No.), AnalogManager Variables and
LogicsManager Command Variables to a customer specific protocol.
6.5.4.2 Configuration
Woodward offers the TelegramMapper PC software for free and enables easYgen-XT to
import, make accessible, and proceed customer specific Modbus protocols. The
TelegramMapper software can be installed separately from other Woodward software.
After starting the program the HELP file can guide through the required settings
Data of the particular easYgen model will be available/selectable:
• AnalogManager variables
• LogicsManager variables
• the easYgen database (ID based)
The according data types must be defined and each address entry can be commented.
There is a maximum length of 300 addresses.
The final protocol can be saved with a protocol number from 65100 to 65199 used
as file name(!) as an
• SCP-file for import into the easYgen device
• HTML-file for easy to read documentation of the (self) created data protocol
• MAP-file for further edits with the TelegramMapper software
To load your created Data Protocol(s) - the scp-file(s) - into your easYgen device use
ToolKit.
To switch to your Data Protocol and use it for communication: Configure parameter ╚═▷
3184 »Modbus protocol number« to your customer specific protocol number and reboot
╚═▷ 10419 the control.
Summary: The self-mappable address range is defined with a protocol number from
65100 to 65199 and has a maximum length of 300 addresses. Communication using
customer specific data protocols is configurable similar to other already existing protocols

6 Application Field
6.5.4.3 Status/diagnostic Modbus Telegram Mapper
5003, 5011 etc. Navigate to “Parameter/Configuration/Configure interfaces/Modbus

protocol”.
6.5.4.3 Status/diagnostic Modbus Telegram Mapper
The easYgen provides an information whether the Modbus TelegramMapper mapping file
could be successful parsed and interpreted. Navigate to “Status Menu/Interfaces/
Ethernet/Modbus TCP/IP” to get an error code.
Fig. 320: Status Modbus mapping table error
Modbus: Mapping table error (12259):
Error codes:
• 0: No error
• 100000 + error line: There is a syntax error -- for any misformatted line
• 200000: File not found -- when file corresponding to selected protocol does not exist
• 300000: Too complex command discovered
• 700000: Too many analog/logic manager indices (i.e. > 32)
• 800000: Memory for the table exhausted (file too big)
6.5.5 Modbus master
The device can act as a configurable Modbus master, for Modbus/TCP. Up to 5

independent slaves can be accessed simultaneously.
The Modbus Master does not work with the serial interface (RS-485, Modbus RTU).

6 Application Field
Up to 99 analog values can be read into AnalogManager group 54 (“54.01 Mapped AM

value 1” to “54.99 Mapped AM value 99” ) and and up to 99 boolean values can be read
into LogicsManager group 54 (“54.01 Mapped LM flag 1” to “54.99 Mapped LM flag
99” ).
All analog values which are present in the device as AnalogManager values and all flags
which are present as LogicsManager values can be written. Boolean flags can be grouped
into 16 bit values. Reading and writing each can be combined to read/write multiple
values in one command. Different variable types and Modbus modes are supported.
Multiple write and read rates can be defined, in order to access some datapoints more
often than others.
Woodward offers a ModbusMasterMapper PC software to configure the Modbus Master

behavior for free and enables the device to import, make accessible, and proceed
customer specific settings. The ModbusMasterMapper software can be installed
separately from other Woodward software. After starting the program the HELP file can
guide through the required settings.
Data of the particular easYgen model will be available/selectable:
• AnalogManager variables
• LogicsManager variables
• the easYgen database (ID based)
The according data types, addresses, rates must be defined and each read/write entry
can be commented.
Note: Modbus master has for read and write a limitation of maximum about 120 words.
The ModbusMasterMapper PC software detects an overrun and will issue a warning.
The final protocol can be saved as a mapping file (*.mmap) file for further processing.The
tool creates a *.SCP-file for uploading the Modbus Master control file into the device using
Toolkit. After uploading and restarting the Modbus Master process can be started via
configuring parameter 3219 to “On”. Now the configured communication will be
executed.
3219 Modbus master 2 [0ff] The Modbus master function is

disabled and no Modbus master
requests are sent.
[0n] The Modbus master function is

requesting data according to the
control file.
Note
Take care that a modbus master

control file is already load into the
device. Refer to chapter Modbus
“Modbus master”.
6.5.5.3 Status/diagnostic Modbus master
Toolkit is providing a screen for some Modbus master diagnostics.

6 Application Field
Fig. 321: Status Modbus
File name (16613):
This field shows the "Description" from the loaded Modbus Master config file. This will be
read in at start-up.
File parsing error code (16614):
File parsing error codes (16614)
Code Meaning
0 No error
1 File error: File was not found or could not be opened
2 Not a mapping file: The file is not a Modbus master mapping file or a malformed
one.
4 Wrong version of mapping file: The version of the mapping file does not match. This
can appear when the file was generated by an older version of the PC tool.
8 Mapping file has wrong check-sum: The mapping file was corrupted and is invalid. It
has to be newly created.
16 Wrong SIZES statement: This is an internal file error, this shall not happen when the
file was correctly created by the PC tool.
32 APPLICATION line wrong in file. The file was created for an application which does
not match to the application running on the device. It has to be newly created for
this application.

6 Application Field
File parsing error codes (16614)
Code Meaning
64 RELEASE line wrong in file. The file was created for a software release which does
not match to the application running on the device. It has to be newly created for
this release.
Select debug line (16615):
This “parameter” activates a debug mode when a number is entered higher than 0. This
function enables the user to test the connections to different devices separately.
Valid values are:
• 0: Debug mode off (default)
• 1000+x: WRITE line 1000+x will be executed
• 2000+x: READ line 2000+x will be executed
Only the selected WRITE or READ line of the mapping file will be executed. All other reads
and writes are suppressed.
Select debug line (16615)
Indication Meaning
16616 This output shows the device number [1..] as defined in the mapping file of the
Debug selected debug line command. It is 0, if “Select debug line” set to 0.
device
16617 This output shows the rate in [s] of the selected debug line command. It is 0, if
Debug rate “Select debug line” set to 0.
16618 This output shows the Modbus address of the selected debug line command. It is 0,
Debug if “Select debug line” set to 0.
address
16619 This output shows the read or wrote value for the selected Debug line command.
Debug When multiple read or multiple write was selected, it shows the first value. It is 0, if
value “Select debug line” set to 0.
16620 This output is TRUE (LED is green), if the selected Debug line command was a read,
Debug line otherwise FALSE. It is FALSE too if “Select debug line” set to 0.
is READ
Modbus Slave Devices 1-5 timeouts:
The LED s of LM variables 08.72 to 08.76 “Modbus dev.x timeout” inform about time outs
of the corresponding slave devices.
Timeouts can happen e.g. in this cases:
• The slave is not answering at all
• The slave is answering but in a rate slower than defined in the mapping file. This can
happen, when the slave is inherently slow or when the mapping was set up in a way
that too many requests were scheduled in the scheduled rate time.

6 Application Field
One Modbus read or write command to one slave will take at least 50 msec. The
minimum permitted rate group is 100 msec. If now a mapping is configured in a way that
it requires more writes to a device than fits into the required rate, or the slave has very
long answer times, there will be a timeout error. The device will still read/write but it will
not do it as quickly as required. This issue can be mitigated by defining slower rate
groups or reducing the number of read/write commands.

7 Interfaces And Protocols

For interfaces terminal overview refer to╚═▷ “3.4 Setup Interfaces”
7.1 CAN Interfaces
7.1.1 CAN Interface 1 (Guidance level)
The CAN interface 1 is a freely configurable CANopen interface with 5 RPDOs (receive
messages), 5 TPDOs (send messages) and 4 additional Server SDOs.
CAN interface 1 is also used for load sharing.
Fig. 322: CAN interface 1
7.1.2 CAN Interface 2 (Engine level)
The CAN interface 2 supports the CANopen and J1939 protocol simultaneously. It supports
the connection of a wide range of engine control units (ECUs) and J1939 analog input
extension modules, which comply with the J1939 standard (e.g. Axiomatic). CANopen
extension modules are also supported.

7.2 Ethernet Interfaces
Fig. 323: CAN interface 2
CAN interface 2 is pre-configured for several expansion units. These include the I/O
expansion boards Woodward IKD 1, several combinations of the expansion boards of the
Phoenix Inline Modular (IL) series, and the support of Wago terminals.
It is possible to connect several combinations of up to four Woodward IKD 1s and/or

Phoenix Inline Modular (IL) modules and/or WAGO modules with up to
7.2 Ethernet Interfaces

General notes
The Ethernet network provides a fast communication capability to different devices, like
remote panel, PLC or SCADA systems. The common protocol Modbus TCP is there for the
preferred communication protocol. Additionally the Ethernet connection supports the
Woodward protocol Servlink for ToolKit and other Woodward own monitoring tools (like
remote panel and SCADA visualization tool). At least the easYgen provides a UDP protocol
for system relevant and time discrete information exchange.

7.3 Serial Interfaces
Fig. 324: Ethernet Network A screen
The actual IP address in Network A, subnet mask and gateway IP address can be viewed
under Next Page (Status Menu) / Diagnostic / Interfaces / Ethernet / Ethernet A.
7.3 Serial Interfaces
7.3.1 RS-485 Interface (Serial Interface 2)
A freely configurable RS-485 Modbus RTU Slave interface is provided to add PLC
connectivity. It is also possible to configure the unit, visualize measured data and alarm
messages, and control the unit remotely.
Fig. 325: RS-485 interface
7.3.2 USB interface (USB 2.0, slave)
Service port
The USB interface follows the USB 2.0 standard but is - as a service port - reserved for
ToolKit and special Woodward usage.
7.4 CANopen Protocol

CANopen is a communication protocol and device profile specification for embedded
systems used in automation. The CANopen standard consists of an addressing scheme,
several small communication protocols and an application layer defined by a device
profile. The communication protocols have support for network management, device

monitoring and communication between nodes, including a simple transport layer for
message segmentation/de-segmentation.
Protocol description
If a data protocol is used, a CAN message looks like this:
Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7
MUX Data byte Data byte Data byte Data byte Data byte Data byte Internal
The MUX byte is counted up, the meaning of the data byte changes according to the
value of the MUX byte.
In the protocol tables is listed which parameter at which MUX on which position is
transmitted. The meaning of the parameter can be taken by means of the number of the
parameter description (For details refer to ╚═▷ “9.2 Data Protocols”).
☼ Example
MUX Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7
1 118 147 Internal
In MUX 1 (byte 0 has got value 1) the value of parameter 118 is included in the byte 1
up to byte 4 (mains voltage 1-2). In byte 6 up to byte 6 the value of parameter 147 is
included (mains frequency). Byte 7 includes internal definitions and can be ignored.
Data format "Unsigned Integer"
UNSIGNED type data has positive integers as values. The range is between 0 and 2n-1.
The data is shown by the bit sequence of length n.
• Bit sequence:
b = b0 to b–1
• Value shown:
UNSIGNEDn(b) = b–1 * 2–1 + ... + b1 * 21 + b0 * 20
Please note that the bit sequence starts on the left with the least significant byte.
Example: Value 266 = 10A hex of type UNSIGNED16 is transmitted on the bus in two
octets, first 0A hex and then 01 hex.
The following UNSIGNED data types are transmitted as follows:
Octet Number 1. 2. 3. 4. 5. 6. 7. 8.
UNSIGNED8 b7 to b0
UNSIGNED16 b7 to b0 b15 to b8
UNSIGNED24 b7 to b0 b15 to b8 b23 to b16
UNSIGNED32 b7 to b0 b15 to b8 b23 to b16 b31 to b24
UNSIGNED40 b7 to b0 b15 to b8 b23 to b16 b31 to b24 b39 to b32

Octet Number 1. 2. 3. 4. 5. 6. 7. 8.
UNSIGNED48 b7 to b0 b15 to b8 b23 to b16 b31 to b24 b39 to b32 b47 to b40
UNSIGNED56 b7 to b0 b15 to b8 b23 to b16 b31 to b24 b39 to b32 b47 to b40 b55 to b48
UNSIGNED64 b7 to b0 b15 to b8 b23 to b16 b31 to b24 b39 to b32 b47 to b40 b55 to b48 b63 to b56
Tab. 126: Transfer syntax for data type UNSIGNEDn
Data format "Signed Integer"
SIGNED type data has integers as values. The range is between 0 and 2–1. The data is
shown by the bit sequence of length n.
• Bit sequence:
b = b0 to b–1
• Value shown:
SIGNEDn(b) = b–2 * 2–2 + ... + b1 * 21 + b0 * 20
if b–1 = 0
• And with two’s complement:
SIGNEDn(b) = SIGNEDn(^b)-1
if b–1 = 1
Please note that the bit sequence starts on the left with the least significant byte.
Example: The value -266 = FEF6 hex of type SIGNED16 is transmitted in two octets, first
F6 hex and then FE hex.
Octet Number 1. 2. 3. 4. 5. 6. 7. 8.
SIGNED8 b7 to b0
SIGNED16 b7 to b0 b15 to b8
SIGNED24 b7 to b0 b15 to b8 b23 to b16
SIGNED32 b7 to b0 b15 to b8 b23 to b16 b31 to b24
SIGNED40 b7 to b0 b15 to b8 b23 to b16 b31 to b24 b39 to b32
SIGNED48 b7 to b0 b15 to b8 b23 to b16 b31 to b24 b39 to b32 b47 to b40
SIGNED56 b7 to b0 b15 to b8 b23 to b16 b31 to b24 b39 to b32 b47 to b40 b55 to b48
SIGNED64 b7 to b0 b15 to b8 b23 to b16 b31 to b24 b39 to b32 b47 to b40 b55 to b48 b63 to b56
Tab. 127: Transfer syntax for data type INTEGER

7.5 J1939 Protocol
7.5 J1939 Protocol

The J1939 protocol is using an extended CAN identifier and can be used via CAN bus
interface parallel to the CANopen protocol and ToolKit. All devices connected to the CAN
bus interface must use the same baud rate independent of the selected protocol.
Most of the J1939 data is standardized and has a SPN (Suspect Parameter Number), which
describes the data (e.g. SPN 110 is representing the value of the current “Engine Coolant
Temperature”). The SPNs are packed in different PGNs (Parameter Group Numbers). The
PGN is a part of the CAN ID and is representing one CAN message (e.g. SPN 110 is packed
in PGN 65263). J1939 defines several hundred SPNs. However, only a small part is
important for most of the applications. For this reason only a part of the SPNs is
supported by the J1939 devices and by the easYgen.
'SAE J1939' also allows manufacturer-specific data areas, so called proprietary data,
which are not defined in the standard. In most cases, these proprietary data is used for
remote control purposes (like start/stop, speed set point) of ECUs (Engine Control Unit).
Some manufacturers also issue specific error messages using manufacturer-specific data.
Besides important standardized data, the easYgen is also supporting some proprietary
data for the different ECUs. Please refer to ╚═▷ “7.5.2 Supported J1939 ECUs & Remote
Control Messages” for details.
7.5.1 Displayed Messages (Visualization)
Visualization messages like "Engine Coolant Temperature" of a device (for example an

ECU) are received on the CAN bus according to J1939 protocol and are shown on the
device display and the ToolKit configuration software. In most cases the visualization
works with standard messages.
The easYgen is able to display all values listed in the table ╚═▷ “Standard visualization
messages” if they are supported by the connected device as well.
If a message is used but its sensor/signal is damaged HMI and ToolKit display »ERROR«.
Unused messages/SPN are monitored by ToolKit with »Missing« but HMI doesn't display
unused messages/SPN (neither message/SPN nor status).
Diagnostic trouble codes (DM1/DM2)
In the J1939 status screen the first 10 active alarm messages (Active Diagnostic Trouble
Codes - DM1) and the first 10 unacknowledged alarm messages (Previously Active
Diagnostic Trouble Codes - DM2) with text, SPN, FMI, and OC are displayed.
Additionally, the state of the lamps (amber/red) is always displayed.
• SPN (= Suspect Parameter Number) indicates the measured value that the alarm
code is referring (e.g. SPN = 100 corresponds to oil pressure).
• FMI (= Failure Mode Indicator) specifies the alarm more precisely (e.g. FMI = 3
means: value is above predefined limits)
• OC (Occurrence Count) indicates how often an alarm occurred.

The indication of fault texts for DM1 and the entry in the respective alarm list is only
possible for SPNs which are listed in the SPN list (refer to ╚═▷ “Standard visualization
messages”)!
For SPNs without text: Refer to the J1939 specification for a list of all SPNs.
Standard visualization messages
In case of ...
• ... defective sensor: "Error" is displayed.

• ... missing sensor: "Missing" is displayed.
SPN PGN Description Resol. Data range J1939 Index
38 65276 Fuel level 2 0.1 % 0 to 100 % 12017
52 65262 Engine inter cooler temperature 1 °C -40 to 210 °C 15217
91 61443 Throttle position 0.1 % 0 to 100 % 15207
92 61443 Load at current speed 1% 0 to 250 % 15208
94 65263 Fuel delivery pressure 1 kPa 0 to 1000 kPa 15218
95 65276 Fuel filter difference pressure 1 kPa 0 to 500 kPa 15219
96 65276 Fuel level 1 0.1 % 0 to 100 % 12016
98 65263 Engine oil level 0.1 % 0 to 100 % 15210
100 65263 Engine oil pressure 1 kPa 0 to 1000 kPa 15205
101 65263 Crankcase pressure 1 kPa -250 to 251 kPa 15220
102 65270 Boost pressure 1 kPa 0 to 500 kPa 15214
105 65270 Intake manifold temperature 1 °C -40 to 210 °C 15215
106 65270 Turbo air inlet pressure 1 kPa 0 to 500 kPa 15221
107 65270 Air filter 1 difference pressure 0.01 kPa 0 to 12.5 kPa 15222
108 65269 Barometric pressure 0.1 kPa 0 to 125 kPa 15212
109 65263 Coolant pressure 1 kPa 0 to 500 kPa 15223
110 65262 Engine coolant temperature 1 °C -40 to 210 °C 15202
111 65263 Coolant level 0.1 % 0 to 100 % 15206
127 65272 Transmission oil pressure 1 kPa 0 to 4000 kPa 15224
157 65243 Fuel rail pressure 0.1 MPa 0 to 251 MPa 15225
158 65271 Battery potential switched 0.1 V 0 to 3212.75 V 15312
171 65269 Ambient air temperature 0.1 °C -273 to 1735 °C 15226
172 65269 Air inlet temperature 1 °C -40 to 210 °C 15213
173 65270 Exhaust gas temperature 0.1 °C -273 to 1735 °C 15216
174 65262 Fuel temperature 1 °C -40 to 210 °C 15203
175 65262 Engine oil temperature 0.1 °C -273 to 1735 °C 15309
176 65262 Turbo oil temperature 0.1 °C -273 to 1735 °C 15227

177 65272 Transmission oil temperature 0.1 °C -273 to 1735 °C 15228
183 65266 Fuel rate 0.1 l/h 0 to 3212.75 l/h 15307
190 61444 Engine speed 1 rpm 0 to 8031.875 rpm 15308
247 65253 Total engine hours1 1h 0 to 210554060 h 15201
250 65257 Total fuel used 0.5 l 0 to 2105540608 l 15319
441 65164 Auxiliary temperature 1 1 °C -40 to 210 °C 15229
442 65164 Auxiliary temperature 2 1 °C -40 to 210 °C 15230
513 61444 Actual engine torque 1% -125 to 125 % 15209
1081 65284 Engine Wait To Start Lamp
1122 65191 Alternator bearing 1 temperature 1 °C -40 to 210 °C 15231
1123 65191 Alternator bearing 2 temperature 1 °C -40 to 210 °C 15232
1124 65191 Alternator winding 1 temperature 1 °C -40 to 210 °C 15233
1131 65189 Intake manifold 2 temperature 1 °C -40 to 210 °C 15236
1134 65262 Engine thermostat 0.1 % 0 to 100 % 15239
1135 65188 Engine oil temperature 2 0.1 °C -273 to 1735 °C 15240
1136 65188 Engine ECU temperature 0.1 °C -273 to 1735 °C 15241
1137 65187 Exhaust gas port 1 temperature 0.1 °C -273 to 1735 °C 15242

1157 65182 Main bearing 1 temperature 0.1 °C -273 to 1735 °C 15262
1172 65178 Turbo 1 compressor inlet temperature 0.1 °C -273 to 1735 °C 15273
1176 65177 Turbo 1 compressor inlet pressure 1 kPa -250 to 251 kPa 15277
1180 65176 Turbo 1 inlet temperature 0.1 °C -273 to 1735 °C 15281
1184 65175 Turbo 1 outlet temperature 0.1 °C -273 to 1735 °C 15285
1203 65172 Engine auxiliary coolant pressure 1 kPa 0 to 1000 kPa 15289
1208 65170 Pre-filter oil pressure 1 kPa 0 to 1000 kPa 15290
1212 65172 Engine auxiliary coolant temperature 1 °C -40 to 210 °C 15291
1382 65130 Fuel filter difference pressure 1 kPa 0 to 500 kPa 15292
1761 65110 Aftertreatment 1 Exhaust Tank1 Level 0.1% 0 to 100% 15313
1800 65104 Battery 1 temperature 1 °C -40 to 210 °C 15293
1801 65104 Battery 2 temperature 1 °C -40 to 210 °C 15294

2433 65031 Right exhaust gas temperature 0.1 °C -273 to 1735 °C 15297
2434 65031 Left exhaust gas temperature 0.1 °C -273 to 1735 °C 15298
2629 64979 Turbo 1 compr. outlet tmp. 0.1 °C -273 to 1736 °C 15310
3031 65110 Aftertreatment 1 Exhaust Tank1 Temperature 1 °C -40 to 210 °C 15314
3644 64914 Engine derate request 0.1% 0 to 100% 15311
3719 6489 DPF 1 Soot Load 1% 0 to 250 % 12018
3720 64891 DPF 1 Ash Load 1% 0 to 250 % 12019
3251 64946 DPF Differential press. 0.1 kPa 0 to 6,425.5 kPa 15550
4151 64851 Exhaust Gas Temp. Avr. 0.1 °C -273 to 1734 °C 12807
4152 64851 Exh. Gas Temp. Avr. B2 0.1 °C -273 to 1734 °C 12812
4153 64851 Exh. Gas Temp. Avr. B1 0.1 °C -273 to 1734 °C 12809
4367 64829 Aftertreatment 1 Exhaust Tank2 Level 0.1% 0 to 100% 15315
4368 64829 Aftertreatment 1 Exhaust Tank2 Temperature 1 °C -40 to 210 °C 15316
1If the total engine hours sent by the ECU exceed 419,000 hrs, the display in the unit is
not correct anymore.
Data transmission engine control unit (ECU)
• If the sent values exceed the limits of the specification, the displayed value is not
defined.
• If a value of the ECU is not sent or sent as not available or defective, the value will
be displayed as indicated in the table before.
Special Deutz EMR2/Volvo EDC4 messages
Suspect parameter number Parameter group number Description
Engine stop 65301 (FF15h) 0 to 250
Please refer to the ECU manual for the engine specific stop codes.
Special Scania S6 messages
Suspect Parameter Description Display in unit Display in

parameter group number ToolKit
number
DLN2-Proprietary 65409 (FF81h) Assessed messages:
No No
• Low engine oil level
Missing Missing
• High engine oil level
Yes Yes
• Low oil pressure

7.5.2 Supported J1939 ECUs & Remote Control Messages
Suspect Parameter Description Display in unit Display in

parameter group number ToolKit
number
• High coolant temperature
The following table lists all ECUs, which are supported by the easYgen beyond the J1939
standard with the appropriate settings. We recommend device type (parameter ╚═▷
15102) "Standard" for all ECUs, which are not listed here. All other parameters shall be
clarified with the ECU manufacturer.
ECU Device type J1939 Engine SPN Comment

own control version
(15102) address address
(15103)
(15106) (15107)
Standard ECUs Standard N/A N/A N/A Please refer to ╚═▷ “7.5.3 Device Type
Standard” for more details.
Woodward EGS EGS Woodward 234 0 N/A
MTU ADEC ECU7 ADEC ECU7 MTU 1 128 N/A The easYgen is connected with the
SAM via CAN. The SAM communicates
with the ADEC using an own bus.
Deutz EMR2 EMR2 Deutz 3 0 Version 1
Volvo EDC4
Deutz EMR3 Standard 3 0 N/A
Deutz EMR4
(EDC 17)
Volvo EMS2 EMS2 Volvo 17 0 N/A The rated speed of the EMS1 and
EDC3 cannot be switched via the
Volvo EMS1 easYgen.
Volvo EDC3
Scania S6 S6 Scania 39 0 N/A
MAN MFR/EDC7 MFR/EDC7 MAN 253 39 N/A The easYgen is connected with the
MFR via CAN. The MFR communicates
with the EDC7 using an own bus.
SISU EEM2/3 EEM SISU N/A 0 / (1) N/A
Cummins Cummins 220 0 N/A Notes
Some Cummins setups need a special

value for “Governor Gain” otherwise
they will shut down. In this cases
please set the “Governor Gain” of the
ECU to »Internal« instead of »J1939«.
MTU ADEC ECU8/ ADEC ECU8 MTU 234 0 N/A The easYgen is connected with the
ECU9 MTU system: ADEC ECU8 &
SmartConnect or ADEC ECU9.
ECU file N/A This is to support ECUs which are not

represented by the selection. Enter file

ECU Device type J1939 Engine SPN Comment

own control version
(15102) address address
(15103)
(15106) (15107)
name with parameter 15167 “ECU file

name”
Hatz EDC 17 3 0 N/A
The addresses listed here are only valid, if the ECU is not configured to other values. In
case of doubt, please check the corresponding settings of the ECU with the service tool.
The following data is only transmitted to the corresponding ECU, if parameter "ECU
remote controlled" is configured to "On", and parameter "Device type" is configured to
one of the available ECU modes (if "Off" is configured, no J1939 remote control messages
will be sent as well).
Please note that some ECU manufacturers require that this functionality must be enabled
first. In some cases, this is only possible by the manufacturer. Please consider this when
ordering the ECU.
1 Woodward EGS
2 Scania S6
3 Deutz EMR2/EMR3 / Volvo EDC4
4 Volvo EMS2
5 Volvo EMS1/EDC3
6 MTU ADEC ECU7
7 MAN MFR/EDC7
8 Standard
9 SISU EEM 2/3
10 Cummins
11 MTU ADEC ECU8/ECU9
12 Hatz EDC 17
Remote Availability with supported ECU number ... Comment
control
parameter 1 2 3 4 5 6 7 8 9 10 11 12
Engine No Yes No Yes Yes Yes Yes No No / Yes Yes Yes If an engine start command
Start Yes is initiated by the easYgen,
this information is
transmitted in the form of a
J1939 message bit to an
ECU. If ignition speed is
reached, this bit will be
reset (LogicsManager
command variable 03.02.
"Starter").


control
parameter 1 2 3 4 5 6 7 8 9 10 11 12
Engine Yes Yes No Yes Yes Yes Yes Yes No / Yes Yes Yes This J1939 bit information is
Stop Yes set, if a "Stop" command in
automatic or manual mode
is present in the easYgen.
The "Stop" bit information
remains set, until ignition
speed is fallen below. After
ignition speed has been
fallen below, the "Stop" bit
will be reset
(LogicsManager command
variable 03.27. "Stop
solenoid").
Droop Yes Yes No Yes Yes Yes Yes Yes Yes Yes No No This J1939 bit information is
mode set, if a "Start" command in
automatic or manual mode
is initiated by the easYgen.
The bit remains set until the
engine has been stopped.
Notes
This message is only sent, if

the LogicsManager output
86.25 "Frequency droop
active" is TRUE.
Idle No Yes No1 Yes Yes No No1 No1 No Yes Yes No This J1939 bit information is
Mode set, if "Idle" mode is active
variable 04.15. "Idle run
active" is TRUE).
The bit will be reset, if "Idle"

mode is no longer active
variable 04.15. "Idle run
active" is FALSE).
50/60 Hz Yes Yes No Yes2 No Yes No1 No No Yes Yes No The J1939 information for
switch 50 or 60 Hz mode is sent to
the ECU depending on the
"Rated system frequency"
parameter setting (╚═▷
1750) within the easYgen .
Speed Yes3 Yes4 Yes3 Yes4 Yes3 Yes3 Yes3 Yes3 Yes3 Yes4 Yes3 Yes3 Refer to parameter ╚═▷
bias 5537 for detailed
information.
Notes
Analog signal only
Preglow No No No Yes Yes No No No No No No No This J1939 bit information is

set, if the easYgen is in
"Preglow" mode
variable 03.04. "Preglow/
Ignition" is TRUE).
The bit will be reset, if the

"Preglow" phase has been
expired or aborted.
Override No Yes No Yes No Yes No Yes No Yes Yes No This J1939 bit information is
set, if the easYgen is in
critical mode

7.5.3 Device Type Standard

control
parameter 1 2 3 4 5 6 7 8 9 10 11 12
variable 04.27. "Critical
mode" is TRUE).
The bit will be reset, if the

critical mode has been
expired or aborted.
Engine No No No No No No No No No No Yes No This message is generated

power according to parameter
mode "ECU power mode"
Engine No No No No No No No No No No Yes No This message is generated

selected according to parameter
application "ECU application"
1Please contact manufacturer to clarify whether both frequencies (50/60 Hz) may be
controlled by the speed bias.
2 In case the rated speed of the easYgen and the ECU don't match, please make sure
that the CAN connections works and change parameter ╚═▷ 1750 of the easYgen once.
3 Speed biasing signal is transmitted as absolute value.
4 Speed biasing signal is transmitted as offset value.
General notes
If the used ECU is not specific listed in the chapter ╚═▷ “7.5 J1939 Protocol” (e.g. Deutz
(EMR3 & EMR4), John Deere, Daimler, Perkins, Iveco, Caterpillar, Liebherr, etc.) we
recommend to configure the "Device type" (parameter ╚═▷ 15102) to the setting
“Standard”. Visualization via J1939 is working with every J1939 ECU. Concerning remote
control most ECUs are also supporting the speed offset via J1939 standard message TSC1.
This chapter supplies you with the details of the device type standard, to help you to
clarify with the manufacturer how the ECU is supported.
Displayed messages (visualization)
In standard mode, the easYgen is able to display all values listed in the table ╚═▷
“Standard visualization messages” if they are supported by the connected ECU.
Diagnostic trouble codes (DM1/DM2)
In standard mode, the easYgen diagnostic messages DM1 (Active Diagnostic Trouble
Codes) and DM2 (Previously Active Diagnostic Trouble Codes) are displayed. It is also
possible to reset DM1 and DM2 failure codes via DM3 and DM11 messages.
Remote control messages
The following table shows the transmitted remote control messages. These messages are
only transmitted if the parameter "ECU remote controlled" (parameter ╚═▷ 15127) is
configured to "On".

All listed messages are according to J1939 standard protocol.
Not all SPNs of the supported PGNs are listed here, in such case the easYgen transmits
“Not available”.
PGN Acronym Name SPN Description Rate

[ms]
Dec Hex
0 0000 TSC1 Torque/Speed Control 695 Engine Override Control Mode 10

1 (fixed to “Speed Control”)
696 Requested Speed Control

Conditions (fixed to “Transient
Optimized”)
897 Override Control Mode Priority

(fixed to “Highest Priority”)
898 Engine Requested Speed/Speed

Limit
61441 F001 EBC1 Electronic Brake 970 Engine Auxiliary Shutdown Switch 100
Controller 1
61470 F01E GC2 Generator Control 2 3938 Generator Governing Bias 20
65029 FE05 GTACP Generator Total AC 2452 Generator Total Real Power 100
Power
64913 FD91 ACS AC Switching Device 3545 Generator Circuit Breaker Status 250
Status
3546 Utility Circuit Breaker Status
64971 FDCB OHECS Off-Highway Engine 2881 Engine Alternate Droop 500
Control Selection Accelerator 1 Select
Notes
If droop shall be active

(LogicsManager 86.25 = TRUE)
the easYgen is transmitting
“Normal Droop” else “Alternate
Droop Setting 1".
65265 FEF1 CCVS Cruise Control/Vehicle 1237 Engine Shutdown Override Switch 100
Speed
59904 EA00 — Request (specific) 247 Engine Total Hours of Operation 10,000
(at PGN FEE5)
— DM11 Diagnostic Data Clear/Reset

For Active DTCs (at PGN FED3)

Of Previously Active DTCs (at PGN
FECE)
Notes
DM3 and DM11 are only

transmitted if triggered.
59904 EA(FF) — Request (global) — DM2 Previously diagnostic trouble 2,000

codes (at PGN FECB)

For Active DTCs (at PGN FED3)

7.6 Modbus Protocol
PGN Acronym Name SPN Description Rate

[ms]
Dec Hex

Of Previously Active DTCs (at PGN
FECE)
441 Auxiliary Temperature 1 (at PGN

FE8C)
442 Auxiliary Temperature 2 (at PGN

FE8C)
Notes
DM3 and DM11 are only

transmitted if triggered.
Configure J1939 addresses
For the visualization the “J1939 own address” (parameter ╚═▷ 15106) and the “Engine
control address” (parameter ╚═▷ 15103) are not relevant. But for remote control e.g.
speed biasing these addresses must be configured correctly. Please refer to your ECU
manual for the correct address. Normally the “Engine control address” (parameter ╚═▷
15103) is “0” and the “J1939 own address” (parameter ╚═▷ 15106) is often "234" or "3".
7.6 Modbus Protocol

Modbus is a serial communications protocol published by Modicon in 1979 for use with its
programmable logic controllers (PLCs). It has become a de facto standard
communications protocol in industry, and is now the most commonly available means of
connecting industrial electronic devices.
The Woodward controller supports
• a Modbus RTU Slave module for RS-485 connections
and
The Modbus RTU Slave expects that a Master node polls the controller slave node.
Modbus RTU can also be multi-dropped, or in other words, multiple Slave devices can
exist on one Modbus RTU network, assuming that the serial interface is a RS-485.
The Modbus/TCP Server fulfills the same role as Modbus client for RTU mode. Also here it
is possible to have one client connected to many servers.
Temporary restriction
With the current easYgen-XT one server can handle only one client at a time.
Detailed information about the Modbus protocol is available on the following website:
• ══▷ http://www.modbus.org/specs.php
There are also various tools available on the internet. We recommend using ModScan32
which is a Windows application designed to operate as a Modbus Master device for
accessing data points in a connected Modbus Slave device. It is designed primarily as a
testing device for verification of correct protocol operation in new or existing systems.

7.6 Modbus Protocol
A trial version download is available from the following website:
• ══▷ http://www.win-tech.com/html/modscan32.htm
Address range
The controller Modbus Slave module distinguishes between visualization data and
configuration & remote control data. The different data is accessible over a split address
range and can be read via the "Read Holding Register" function.
Furthermore, controller parameters and remote control data can be written with the
"Preset Single Registers" function or "Preset Multiple Registers" (╚═▷ Fig. 326)
Fig. 326: Address range
All addresses in this document comply with the Modicon address convention. Some PLCs
or PC programs use different address conventions depending on their implementation.
Then the address must be increased and the leading 4 may be omitted.
Please refer to your PLC or program manual for more information. This determines the
address sent over the bus in the Modbus telegram. The Modbus starting address 450001
of the visualization data may become bus address 50000 for example.
Visualization
The visualization over Modbus is provided in a very fast data protocol where important
system data like alarm states, AC measurement data, switch states and various other
information may be polled.

7.6 Modbus Protocol
According to the Modbus addressing range, the visualization protocol can be reached on
addresses starting at 450001. On this address range it is possible to do block reads from
1 up to 128 Modbus registers at a time.
Modbus read Description Multiplier Units

addresses
450001 Protocol-ID, always 5010 –
450002 Scaling Power (16 bits) Exponent 10x W

(5;4;3;2)
............ ......... ..... .....
............
............ ......... ..... .....
450445 Total engine hours (j1939-HOURS) 1 h
Tab. 128: Address range block read
╚═▷ “4.7.3 Modbus Protocol” is only an excerpt of the data protocol. It conforms to the
data protocol 5010.
The easYgen has an additional combined CANopen/Modbus protocol 5003.
Please refer to the Data Protocols chapter, ╚═▷ “9.2 Data Protocols”
The following ModScan32 screenshot shows the configurations made to read the
visualization protocol with a block read of 128 registers.
Fig. 327: Visualization configurations
Configuration
The Modbus interface can be used to read/write parameters. According the Modbus
addressing range for the configuration addresses, the range starts at 40001 and ends at
450000. You can always access only one parameter of the system in this address range.
The Modbus address can be calculated depending on the parameter ID as illustrated
below:

7.7 Load Sharing
Parameter ID < 10,000 Parameter ID >= 10,000
Modbus address = 40000 + (Par. ID+1) 400000 + (Par. ID+1)
Tab. 129: Address calculation
Block reads in this address range depend on the data type of the parameter. This makes
it important to set the correct length in Modbus registers which depends on the data type
(UNSIGNED 8, INTEGER 16, etc.).
Refer to ╚═▷ Tab. 130 for more information.
Types Modbus Remarks

registers
UNSIGNED 8 1
UNSIGNED 16 1
INTEGER 16 1
UNSIGNED 32 2
INTEGER 32 2
LOGMAN 7 Little-endian is used for LogicsManager to be compatible

with (non-XT) easYgen series
ANALOGMANAGER 7 Big-endian is used for AnalogManager because it is the

regular format for Modbus
TEXT/X X/2
Tab. 130: Data types
The Modbus RTU response time can increase under certain conditions (display versions /
plastic housing only):
• without CAN (J1939 protocol) connected -> max. 2 seconds

• with CAN (J1939 protocol) connected -> max. 3 seconds
Woodward recommends to make a break time of 10 ms after receiving the data of the
last Modbus request.
7.7 Load Sharing

General information
The maximum number of participating easYgen-3000XT Series devices for load sharing is
32. Both CAN and Ethernet interfaces can handle load share. Load share via Ethernet
interface uses UDP broadcast messages.
Multi-master principle
It is important to know that the load share and load-dependent start/stop functionality is
subject to a multi-master principle. This means that there is no dedicated master and
slave function. Each easYgen decides for itself how it has to behave.

7.7 Load Sharing
The benefit is that there is no master control, which may cause a complete loss of this
functionality in case it fails. Each control is also responsible for controlling common
breakers like a mains circuit or generator group breaker.
Load share monitoring
The easYgen provides LDSS parameters for monitoring load sharing:
• Multi-unit parameter alignment
The multi-unit parameter alignment functionality requires that the relevant

parameters are all configured identically at all participating units. For additional
information refer to ╚═▷ “4.5.6.16 Multi-Unit Parameter Alignment”.
• Multi-unit missing members
The multi-unit missing members monitoring function checks whether all participating
units are available (sending data on the load share line). For additional information
refer to ╚═▷ “4.5.6.17 Multi-Unit Missing easYgen”.
Load share communication
The following parameters allows to select the interface for load share communication.
Refer to ╚═▷ “4.4.4.3.5 Load-Share Interface” for detailed information.
ID Text Setting range Default value
9924 Load share Interface CAN CAN
Off
Ethernet A
CAN/EthA by LM*
CAN/Ethernet A
Notes
* CAN or Ethernet A depending on ╚═▷

11986 (described below)
11986 LS interface Ethernet A FALSE FALSE
(LM 86.13: LS interf. EthA = 11987) TRUE
Notes
Switches the load share interface

between
• FALSE: CAN
• TRUE: Ethernet A
Woodward recommends to configure the Node-IDs (parameter ╚═▷ 8950) for units, which
participate in load sharing, as low as possible to facilitate a fast establishing of
communication.

7.7.1 Load Share via CAN
7.7.1 Load Share via CAN
Bus load
The bus load increases with the number of units participating in load sharing.
The following parameters affect the bus load:
• Number of CAN participants
• Baud rate
• Transfer rate of load share messages
• Transfer rate of visualization protocols
We recommend to consider whether all data has to be sent on the CAN bus when
planning the CAN bus. It is also possible to send visualization data via RS-485 for
example.
Measures to reduce the bus load
If you need to reduce the bus load of the load share CAN bus, the following methods may
be used:
• Increase the baud rate (parameter ╚═▷ 3156) under consideration of the bus length
(refer to ╚═▷ “3.4.4 CAN Bus Interfaces”).
• Reduce the transfer rate of the load share message (parameter ╚═▷ 9921).
• Reduce the transfer rate of the visualization message, i.e. the event timer
• Disable the transmission visualization data on the CAN bus and use the RS-485
interface to transmit visualization data.
• Disable SYNC message (parameter ╚═▷ 9100) and/or TIME message (parameter ╚═▷
9101) and/or the producer heartbeat time SYNC message (parameter ╚═▷ 9120), if
possible.
CAN load share configuration
The following parameters are available for configuring the CAN bus interfaces. Refer to
╚═▷ “4.7.6 Load Share Parameters” for detailed information.
Open menu path [Parameter / Configuration / Configure interfaces / Configure CAN

interfaces / Configure CAN load share]. Refer to ╚═▷ “4.4.4.3.6 Load Sharing”.
ID Text Setting range Default value
9921 Transfer rate LS fast message 0.10 to 0.30 s 0.10 s
9920 Load Share CAN-ID 2xx Hex / 3xx Hex / 5xx Hex
4xx Hex / 5xx Hex

7.7.2 Load Share via UDP Broadcast Messages (Ethernet)
7.7.2 Load Share via UDP Broadcast Messages (Ethernet)
Load Share UDP
Load share and other system relevant messages are handled with UDP messages. The
construction of the UDP messages allows (load share) communication with other
Woodward devices.
For configuration of the Ethernet interface see chapters ╚═▷ “4.7.5 Ethernet Interfaces”
and ╚═▷ “7.2 Ethernet Interfaces”.

8 Technical Specifications
8.1 Technical Data
8.1 Technical Data

Product label
Fig. 328: Product label
Number Name Description
1 Address Manufacturer and manufacturing addresses
2 S/N Serial number (numerical)
3 S/N Serial number (barcode)
4 P/N Item number
5 Type Description Description (product name)
6 Details Technical data
7 S/N Date of production (year-month)
8 REV Item revision number
9 Approval Approvals
10 Environment Separate collection symbol
Battery inside
Fig. 329: Waste Disposal
This device contains a battery, and therefore it is labeled with the symbol shown beside
according to the EU Directive 2006/66/EC.

8.1.1 Measuring Values
WARNING!
Batteries can be harmful to the environment. Damaged or unusable batteries must be

disposed of in a container specially reserved for this purpose.
In general, appropriate local guidelines and regulations must be followed when disposing
of electrical devices and batteries.
8.1.1 Measuring Values
Voltages
Measuring values, voltages
Measuring voltages / 277/480 VAC
: Range rated value (VLLrated) 100 VAC up to 480 VAC
: Maximum value (VLLmax) max. 624 VAC
: Rated voltage phase – ground 300 VAC
: Rated surge voltage 4.0 kV
Input resistance per path 2 MΩ
Maximum power consumption per path < 0.05 W
Linear measuring range 1.25 × Vrated
Measuring frequency 50/60 Hz (30.0 to 85.0 Hz)
Currents
With External CT
For correct measuring with external CT the input has to be one side grounded by the
customer.
Measuring values, currents Galvanically isolated
Measuring current Rated value (Irated) ../1 A or ../5 A
Linear measuring range Generator 3.0 × Irated
Mains/ground current approx. 1.5 × Irated
Maximum power consumption per < 0.10 VA

path
Rated short-time current (1 s) 50.0 A
Battery Voltage
Measuring values, battery voltage Galvanically isolated
Input voltage range 8 to 40 VDC

8.1.2 Ambient Variables
8.1.2 Ambient Variables
CAUTION!
Device Operating Voltage
Connect the unit only to a DC power source that complies with the safety extra-low
voltage (SELV) requirements.
Power supply 12/24 VDC (8 to 40.0 VDC), SELV
Intrinsic consumption max. 24 W
Degree of pollution 2
Maximum elevation 2,000 m ASL
Insulation voltage 100 VDC
Marine applications: 40 VDC
Overvoltage (≤ 2 min) 80 VDC
Reverse voltage protection Over the full supply range
Input capacitance 5,000 µF
Unit Power Supply Negative potential grounded or positive potential

grounded or ungrounded
8.1.3 Inputs/Outputs
Discrete inputs 'DI xx'
Discrete inputs Galvanically isolated
Input range (Vcont. dig. input) Rated voltage
12/24 VDC (8 to 40.0 VDC)
Input resistance approx. 20 kΩ
Discrete outputs 'R xx' (relay outputs)
Discrete/relay outputs Potential free Galvanically isolated
Configurable via
LogicsManager
Contact material AgNi
General purpose (GP) (Vcont, relays) AC 2.00 AAC@250 VAC
DC 2.00 ADC@24 VDC
0.36 ADC@125 VDC
Not suitable for USA and Canada

applications. Not evaluated by UL.
0.18 ADC@250 VDC

8.1.3 Inputs/Outputs
Not suitable for USA and Canada

applications. Not evaluated by UL.
Pilot Duty AC B300
Analog inputs 'AI 01-03' (Type 1: 0/4 to 20 mA | 0 to 2000 Ω | 0 to 1 V)
Analog inputs FlexInTM Freely scalable
Maximum permissible voltage against 9V

Engine Ground
Maximum permissible voltage between 100 V

Engine Ground & PE
Resolution 16 Bit
0/4 to 20 mA input Internal load ~50 Ω
0 to 2000 Ω input Load current ≤ 2.3 mA
0 to 1V input Input resistance approx. ~91 kΩ
Analog outputs 'AO 01' "Speed Biasing" (Type 1: ±20 mA | ±10 V | PWM)
Analog output Freely scalable Galvanically

isolated
Pre-configured to "11.03 Speed bias [%]"
Resolution min. 12 bit
Configurable as (bipolar) ±20 mA, ±10 VDC
PWM output ±10 VDC, 500 Hz

duty cycle
Shunt resistor max. 500 Ω
Galvanically isolation to PE min. 100 VAC
Analog outputs 'AO 02' "Voltage Biasing" (Type 1: ±20 mA | ±10 V | PWM)
Analog output Freely scalable Galvanically

isolated
Pre-configured to "11.02 Voltage bias
[%]"
Resolution min. 12 bit
Configurable as (bipolar) ±20 mA, ±10 VDC
PWM output ±10 VDC, 500 Hz

duty cycle
Shunt resistor max. 500 Ω
Basic isolation to PE 500 VRMS
Reinforced isolation to PE 300 VRMS
Auxiliary excitation (D+) input/output
Auxiliary excitation (D+) input/output Galvanically isolated
Output current approx. 100 mA@12/24 VDC

8.1.4 Interfaces
Voltage monitoring range (input) 8 to 40 VDC
Magnetic pickup input (MPU)
Magnetic pickup input Capacitively isolated
Input impedance min. 17 kΩ
(decoupled by capacitors)
Voltage range (input) 800 mVpp to 100 Vpp
Refer to ╚═▷ Fig. 330
Proximity Probe Leakage Current ≤100 µA
Response time ≤1000 rpm per second
(max. unloaded engine acceleration)
Minimum rated rpm 100 (rpm)
Fig. 330: MPU - characteristic
8.1.4 Interfaces
USB (slave)
USB 2.0 interface Galvanically isolated
Type USB 2.0 standard; slave (Type B)
Data rate max. 12 Mbit/s

8.1.4 Interfaces
Insulation Galvanically isolated
Bus Voltage 5V
Current consumption approx. 10 mA
RS-485 interface
RS-485 interface Galvanically isolated
Insulation voltage (continuously) 100 VAC
Insulation test voltage (1 s) 1700 VDC
Version RS-485 Standard
CAN bus interface
CAN bus interface Galvanically isolated
Version CAN bus
Internal line termination Not available
Ethernet interface
Ethernet bus interface Galvanically isolated
Only one MAC ID is required
Version Ethernet 10/100Base-T/TX
Ethernet plug socket RJ45 standard, shielded
2 LEDs to indicate communication.
Ethernet cable CAT 5 or 5e (class D)
Shielding: F/UTP according to ISO/IEC

11801 (foil overall shielding, pairs
unshielded)
Green LED Indicates link activity (blinking during

data transmission)
Yellow LED Indicates link status (regarding speed):
10 Mb/s: LED switched-off
100 Mb/s: LED switched-on
Internal shield termination Available

8.1.5 Real Time Clock Battery
8.1.5 Real Time Clock Battery
Type Lithium
Life span (operation without power supply) approx. 5 years
Battery field replacement Not allowed.
Please contact your Woodward service partner.
8.1.6 Display (plastic housing variant, only)
Type LCD display
Size Diagonal: 5,7’’ (144.8 mm)
Resolution 320 x 240 pixel
Picture quality up to 8 bad dots allowed
Backlight luminance 550 cd/m2 (max)
Temperature threshold -20 °C ambient ( for "...-LT" variants, only)
(Heater ON/OFF)
8.1.7 Housing
Housing type
Type Plastic Sheet metal
easYpack Custom
Dimensions (W × H × D) 282 × 216 × 96.3 mm 250 × 227 × 50 mm
Front cutout (W × H) 249 [+1.1] × 183 [+1.0] mm -/-
Weight approx. 1880 g approx. 1600 g
Wiring Screw-plug-terminals
2.5 mm²
Recommended locked torque 4 inch pounds / 0.5 Nm.
Use 90 °C copper wire or better.
Use class 1 wire only or equivalent.
Protection
Protection system Plastic IP54 in the front with clamp fasteners
IP66 in the front with screw kit
IP20 on the rear side
Sheet metal IP20

8.1.8 Approvals
Front foil (plastic housing) Insulating surface
8.1.8 Approvals
EMC test (CE) Tested according to applicable EMC standards. Refer to ╚═▷ “8.2
Environmental Data” for details
Listings CE marking
UL, Ordinary Locations, File No.: E231544
UL recognized component, category FTPM2/8, File No.: E347132
cUL
CSA
EAC
BDEW (Dynamic mains stabilization)
VDE-AR-N 4105 (Mains decoupling and single failure proof feature)
Marine Type approval Lloyds Register (LR)
Type approval American Bureau of Shipping (ABS)
8.2 Environmental Data

Vibration
Frequency range - sine sweep 5 Hz to 100 Hz
Acceleration 4G
Standards IEC 60068-2-6, Fc
Lloyd’s Register, Vibration Test2
SAEJ1455 Chassis Data
Frequency range - random 10 Hz to 2000 Hz
Power intensity 0.04 G²/Hz
RMS value 8.2 Grms
Standards MIL-STD 202F, M214A, SAE J1455
Shock
Shock 40 G, Saw tooth pulse, 11 ms
Standards MIL-STD 810F, M516.5, Procedure 1
Temperature
Housing »...-LT« version, only

type
Plastic Cold, Dry Heat (storage) -30 °C (-22 °F) / 80 °C (176 -30 °C (-22 °F) / 80 °C (176
°F) °F)

8.3 Accuracy
Cold, Dry Heat (operating) -20 °C (-4 °F) / 70 °C (158 -40 °C (-40 °F) / 70 °C (158
°F) °F)
Sheet metal Cold, Dry Heat (storage) -40 °C (-40 °F) / 80 °C (176 °F)
Cold, Dry Heat (operating) -40 °C (-40 °F) / 70 °C (158 °F)
Standards IEC 60068-2-2, Test Bb and Bd
IEC 60068-2-1, Test Ab and Ad
Humidity
Humidity 60 °C, 95% RH, 5 days
Standards IEC 60068-2-30, Test Db
Marine environmental categories
Marine environmental categories Lloyd’s Register of Shipping (LRS):
ENV1, ENV2, ENV3 and ENV4
Electromagnetic Compatibility
EN 61000-6-2 2005 - Electromagnetic compatibility (EMC). Generic

standards.
Immunity for industrial environment
EN 61000-6-4 2007 + A1: 2011 - Electromagnetic compatibility

(EMC). Generic standards.
Emission standard for industrial environments
EN 61326-1 2013 - Electrical equipment for measurement,

control and laboratory use.
EMC requirements. General requirements (according

to industrial electromagnetic environment)
8.3 Accuracy
The accuracy declaration is defined by the according measurement ranges. The rated
maximum of the single ranges are taken as 100%.
This results in the definitions:
• Range 1: 69/120 V rated = 100%
• Range 2: 277/480 V rated = 100%
Measuring value Display Accuracy Measuring start Notes
Frequency
Generator 15.0 to 85.0 Hz 0.1% (of 85 Hz) 5% (of PT secondary

voltage setting)1
Mains 30.0 to 85.0 Hz

8.3 Accuracy
Voltage
Wye generator / 0 to 650 kV 0.5% Class 0.5 2 1.5% (of PT

mains / busbar secondary voltage
related to: setting)1
Delta generator / 69/277 V (Wye) 2% (of PT secondary

mains / busbar voltage setting)1
120/480 V (Delta)
Power supply/Battery 0 to 40 VDC ±0.5% related to 40 Related on the 0.5% equals 0.2 V
V measurement range (±0.2 V)
8 to 40 V
Current
Generator 0 to 32,000 A 0.5% (of 1/5 A)3 Class 1% (of 1.3/6.5 A)3
0.5
Max. value
Mains/ground current
Real power
Actual total real -2 to 2 GW 1% (of 69/277 V x 1/5 Measuring starts with

power value A) 2/3 detecting the zero
passage of current/
voltage
Reactive power
Actual value in L1, L2, -2 to 2 Gvar 1% (of 69/277 V x 1/5 Measuring starts with
L3 A) 2/3 detecting the zero
passage of current/
voltage
Power factor
Actual value power lagging 0.000 to 1% 1% (of 1.3/6.5 A)3 1.000 is displayed for
factor L1 1.000 to measuring values
leading 0.000 below the measuring
start
Miscellaneous
Real energy 0 to 4,200 GWh 0.36% (of 1.3/6.5 A)3 Not calibrated
Operating hours Max. 1 × 106 h
Maintenance call 0 to 9,999 h

hours
Maintenance call 0 to 999 d

days
(Engine) Start 0 to 65,535

counter
Battery voltage 8 to 40 V ±0.5% (of input

voltage range 0 to
40 VDC)
Auxiliary excitation (D 1% (of input voltage

+) input/output range 0 to 40 VDC)
Pickup speed frated +/- 40% 0,1% of frated +/- 1

rpm
Phase angle -180 to 180° ± 1 degree 1.25% (of PT 180° is displayed for
secondary volt. measuring values
setting) below measuring
start

8.3 Accuracy
Analog Inputs
0 to 20 mA Freely scalable ±0.5% related to 20 2 wire input.

mA
0.5% equals 0.1 mA
⇒ +/- 0.1 mA)
0 to 2000 Ω Freely scalable ±0.5% related to 1 wire input (related

2000 Ω to engine ground)4
0 to 1 V Freely scalable ±0.5% related to 1 V 2 wire input.
0.5% equals 0.005

V⇒ +/- 0.005 V)
Analog Outputs
Type 1: ±20 mA | ±10 Freely scalable ≤1%

V | PWM
1 Setting of the parameter for the PT secondary rated voltage
2 Depending on the used measuring range (120/480 V)
3Depending on the CT input definition (1/5 A) by customer settings. easYgen-XT

hardware covers both 1 A and 5 A ranges.
4 Some senders, like the VDO senders, are operating in the working range 0 to 200
Ohms. For sure, the 0.5% accuracy cannot be directly assigned to these senders.
Therefore the accuracy percentage tolerance will be expanded accordingly. On the other
hand, measurements have shown that under usual circumstances (at 20°C, no EMC
surge or burst present) an accuracy of 1% for such senders can be kept.
Reference conditions
The reference conditions for measuring the accuracy are listed below.
Input voltage Sinusoidal rated voltage
Input current Sinusoidal rated current
Frequency Rated frequency
Power supply Rated voltage ± 2%
Power factor (cos φ) 1.000
Ambient temperature 23 °C ± 2 K
Warm-up period 20 minutes

8.4 Protection (ANSI)
8.4 Protection (ANSI)

"ANSI Code" related Protection Functions
Protection related ANSI #
Generator: Voltage / frequency 59 / 27 / 81O / 81U
Overload, reverse/reduced power 32 / 32R / 32F
Unbalanced load 46
Synch Check 25
Instantaneous overcurrent 50
Time-overcurrent (IEC 255 compliant) 51 / 51 V
Ground fault (measured ground current) 50G
Power factor 55
Rotation field
Engine: Overspeed / underspeed 12 / 14
Speed / frequency mismatch
D+ auxiliary excitation failure
Cylinder temperature
Mains: Voltage / frequency 59 / 27 / 81O /

81U /25
Phase shift / rotation field / ROCOF (df/dt) 78

9 Appendix
9.1 Characteristics
9 Appendix
9.1 Characteristics
9.1.1 Triggering Characteristics
Time-dependent overshoot monitoring
This triggering characteristic is used for time-dependent overcurrent monitoring.
Fig. 331: Three-level time-dependent overshoot monitoring

9 Appendix
Two-level overshoot monitoring
This triggering characteristic is used for generator, mains and battery overvoltage,
generator and mains overfrequency, overload IOP and MOP and engine overspeed
monitoring.
Fig. 332: Two-level overshoot monitoring

9 Appendix
Two-level undershoot monitoring
This triggering characteristic is used for generator, mains and battery undervoltage,
generator and mains underfrequency, and engine underspeed monitoring.
Fig. 333: Two-level undershoot monitoring

9 Appendix
Two-level reversed/reduced load monitoring
This triggering characteristic is used for generator reversed/reduced load monitoring.
Fig. 334: Two-level reversed/reduced load monitoring

9 Appendix
Two-level unbalanced load monitoring
This triggering characteristic is used for generator unbalanced load monitoring.
Fig. 335: Two-level unbalanced load monitoring

9 Appendix
9.1.2 VDO Inputs Characteristics
One-level asymmetry monitoring
This triggering characteristic is used for generator voltage asymmetry monitoring.
Fig. 336: One-level asymmetry monitoring
9.1.2 VDO Inputs Characteristics
Since VDO sensors are available in different types, the index numbers of the
characteristic curve tables are listed.
1. ▷ Always order VDO sensors with the correct characteristic curve. Manufacturers of VDO
sensors usually list these tables in their catalogs.

9 Appendix
9.1.2.1 VDO Input "Pressure"
0 to 5 bar/0 to 72 psi - Index "III"
Fig. 337: Characteristics diagram VDO 0 to 5 bar, Index "III"
P [bar] 0 0.5 1 1.5 2 2.5 3 3.5 4 4.5 5
P [psi] 0 7.25 14.50 21.76 29.00 36.26 43.51 50.76 58.02 65.27 72.52
R 11 29 47 65 82 100 117 134 151 167 184

[Ohm]

9 Appendix
0 to 10 bar/0 to 145 psi - Index "IV"
Fig. 338: Characteristics diagram VDO 0 to 10 bar, Index "IV"
P 0 0.5 1 1.5 2 3 4 5 6 7 8 8.5 9 10

[bar]
P 0 7.25 14.50 21.76 29.00 43.51 58.02 72.52 87.02 101.53 116.03 123.28 130.53 145.04
[psi]
R 10 21 31 42 52 71 90 107 124 140 156 163 170 184

[Ohm]

9 Appendix
9.1.2.2 VDO Input "Temperature"
40 to 120 °C/104 to 248 °F - Index "92-027-004"
Fig. 339: Characteristics diagram VDO 40 to 120 °C - detail, Index "92-027-004"

9 Appendix
Fig. 340: Characteristics diagram VDO -40 to 120 °C - full range, Index "92-027-004"
Temp. -40 -35 -30 -25 -20 -15 -10 -5 0 5 10

[°C]
Temp. -40 -31 -22 -13 -4 5 14 23 32 41 50

[°F]
R 17162.4 12439.5 9134.5 6764.5 5067.6 3833.9 2929.9 2249.4 1743.1 1364.0 1075.6
[Ohm]
... continued with further points:
Temp. 15 20 25 30 35 40 45 50 55 60 65
[°C]
Temp. 59 68 77 86 95 104 113 122 131 140 149

[°F]
R 850.1 677.0 543.5 439.3 356.6 291.5 239.6 197.3 161.5 134.0 114.0
[Ohm]
... continued with further points:
Temp. 70 75 80 85 90 95 100 105 110 115 120

[°C]
Temp. 158 167 176 185 194 203 212 221 230 239 248
[°F]
R 97.1 82.4 70.1 59.7 51.2 44.3 38.5 33.4 29.1 25.5 22.4
[Ohm]
... and finally continued with further points:
Temp. 125 130 135 140 145 150

[°C]
Temp. 257 266 275 284 293 302

[°F]

9 Appendix
R 19.75 17.44 15.46 13.75 12.26 10.96

[Ohm]
50 to 150 °C/122 to 302 °F - Index "92-027-006"
Fig. 341: Characteristics diagram VDO 50 to 150 °C - detail, Index "92-027-006"
Fig. 342: Characteristics diagram VDO 0 to 120 °C - full range, Index "92-027-006"

9 Appendix
9.1.2.3 Pt100 RTD
Temp. 0 5 10 15 20 25 30 35 40 45 50
[°C]
Temp. 32 41 50 59 68 77 86 95 104 113 122

[°F]
R 3240.18 2743.6 1905.87 1486.65 1168.64 926.71 739.98 594,9 481,53 392.57 322.17
[Ohm]
Temp. 55 60 65 70 75 80 85 90 95 100 105

[°C]
Temp. 131 140 149 158 167 176 185 194 203 212 221
[°F]
R 266.19 221.17 184.72 155.29 131.38 112.08 96.40 82.96 71.44 61.92 54.01
[Ohm]
Temp. 110 115 120 125 130 135 140 145 150
[°C]
Temp. 230 239 248 257 266 275 284 293 302
[°F]
R 47.24 41.42 36.51 32.38 28.81 25.70 23.00 20.66 18.59

[Ohm]
9.1.2.3 Pt100 RTD
Fig. 343: Characteristics diagram Pt100

9 Appendix
9.1.2.4 Pt1000 RTD
Temp. -200 -150 -100 -50 0 10 20 30 40 50 60

[°C]
Temp. -328 -238 -148 -58 32 50 68 86 104 122 140

[°F]
R 18.5 39.7 60.25 80.7 100 103.9 107.8 111.7 115.5 119.4 123.2
[Ohm]
Temp. 70 80 90 100 125 150 175 200 225 250 300

[°C]
Temp. 158 176 194 212 257 302 347 392 437 482 572
[°F]
R 127.1 130.9 134.7 138.5 147.9 157.3 166.6 175.8 188.6 194.1 212.0
[Ohm]
Temp. 350 400 450 500 550 600 650 700 750 800 850
[°C]
Temp. 662 752 842 932 1022 1112 1202 1292 1382 1472 1562
[°F]
R 229.7 247.0 264.1 280.9 297.4 313.6 329.5 345.1 360.5 375.5 390.25
[Ohm]
9.1.2.4 Pt1000 RTD
The characteristic of the Pt1000 temperature sender accords the characteristic diagram
Pt100 at which the R value is to multiply with 10. Refer to ╚═▷ “9.1.2.3 Pt100 RTD” for
details.

9 Appendix
9.1.2.5 NTC-Sender "AB_94099" (AB-Elektronik Sachsen GmbH)
9.1.2.5 NTC-Sender "AB_94099" (AB-Elektronik Sachsen GmbH)
Fig. 344: Characteristic diagram "AB_94099"
9.2 Data Protocols

General note
The following data protocols / data telegrams are describing the currently defined full set
of data for each protocol. Please ignore data your device does not support.
The following data protocols are implemented to be used
CANopen/Modbus
• 5003: Basic Visualization
supported for easYgen-3000 series compatibility
• 5014: Basic Visualization (based on 5003)

9 Appendix
9.2.1 Protocol 5003 (Basic Visualization)
CANopen
• 5004: Generator Values Visualization
• 5005: Mains Values Visualization
• 5011: Alarm Values Visualization
• 5018: Special data 1
• 6000: Load Share Message
• 65000: External Discrete I/O 1 to 8
• 65001: External Discrete I/O 9 to 16
Modbus
• 5010: Basic Visualization
• 5016: Basic Visualization (based on 5010)
Modbus- CAN CAN Size Index Description Unit Scale Model

Address Mux Byte
50000 0 1-2 int16 Protocoll-ID, allways 5003 All
50001 0 3-4 int16 10100 Pickup speed rpm *1 All
50002 0 5-6 BITLIST
Control mode (STOP/AUTO/MANUAL/ Mask:000Fh All

TEST)
1=AUTO - 04.01 Operation Mode Auto
2=STOP - 04.02 Operation Mode Stop
4=MANUAL - 04.03 Operation Mode Man
8=TEST - 04.03 Operation Mode Test
50003 1 1-2 int16 160 Gen. powerfactor *1000 All
50004 1 3-6 int32 170 Av. Gen. Wye-Voltage V *10 All
50006 2 1-2 int16 144 Gen. frequency Hz *100 All
50007 2 3-6 int32 171 Av. Gen. Delta-Voltage V *10 All

9 Appendix

Address Mux Byte
50009 3 1-2 int16 147 Mains frequency Hz *100 All
50010 3 3-6 int32 173 Av. Mains Wye-Voltage V *10 All
50012 4 1-2 int16 208 Mains power factor *1000 All
50013 4 3-6 int32 174 Av. Mains Delta-Voltage V *10 All
50015 5 1-2 int16 209 Busbar 1: Frequency Hz *100 All
50016 5 3-6 int32 216 Av. Busbar 1 Delta-Voltage V *10 All
50018 6 1-2 int16 Internal
50021 7 1-2 int16 10110 Battery voltage V *10 All
50022 7 3-6 int32 207 Av. Mains Current A *1000 All
50024 8 1-2 int16 10111 Analog input 1 configurable All
50025 8 3-6 int32 185 Av. Gen. Current A *1000 All
50028 9 3-6 int32 161 Meas. ground current A *1000 All
50031 10 3-6 int32 159 Calculated ground current A *1000 All
50033 11 1-2 int16 10117 Analog input 4 configurable EG3500XT-

P2
50034 11 3-6 int32 111 Gen. current 1 A *1000 All

P2

P2

P2
50043 14 3-6 int32 134 Mains current L1 A *1000 All

P2

P2

P2
50052 17 3-6 int32 135 Total gen. power W *1 All

9 Appendix

Address Mux Byte
50055 18 3-6 int32 140 Total mains power W *1 All
50058 19 3-6 int32 136 Total gen. reactive power var *1 All
50060 20 1-2 int16 10159 AI Auxiliary excitation D+ V *10 All
50061 20 3-6 int32 150 Total mains reactive power var *1 All
50063 21 1-2 uint16 10133 BITLIST
08.18 LM CANopen error at CAN Mask: 0001h All

Interface 1
05.10 LM Maintenance hours exceeded Mask: 0002h All

latched
05.09 LM Maintenance days exceeded Mask: 0004h All

latched
05.08 LM Start fail detected latched Mask: 0008h All
08.10 LM General CAN-J1939 fault Mask: 0010h All

latched
08.08 LM MCB fail to open latched Mask: 0020h All
08.07 LM MCB fail to close latched Mask: 0040h All
08.06 LM GCB fail to open latched Mask: 0080h All
08.05 LM GCB fail to close latched Mask: 0100h All
05.06 LM Shutdown malfunction Mask: 0200h All

detected latched
05.07 LM Speed detection alarm latched Mask: 0400h All
05.05 LM Unintended stop detected Mask: 0800h All

latched
05.04 LM Engine under speed 2 latched Mask: 1000h All
05.02 LM Engine Over speed 2 latched Mask: 4000h All
50064 21 3-6 182 Busbar 1: voltage L1-L2 V *10 All
50066 22 1-2 10149 BITLIST
08.30 GCB syn. timeout latched Mask: 8000h All
08.31 MCB syn. timeout latched Mask: 4000h All
08.32 GGB Timeout latched Mask: 2000h EG3500XT-

P1
EG3500XT-
P2
05.11 Charge alt. low voltage (D+) Mask: 1000h All

latched
operating range failure 12 Mask: 0800h All
08.45 CPU overload R1 trip Mask: 0400h All
08.47 MCB failure 50BF latched Mask: 0200h All

9 Appendix

Address Mux Byte
08.46 GCB failure 50BF latched Mask: 0100h All
05.22 ECU Protect alarm latched Mask: 0080h All
05.23 ECU Emission alarm latched Mask: 0040h All
08.19 CANopen error at CAN Interface 2 Mask: 0020h All
08.16 Parameter Alignment latched Mask: 0010h All
08.27 Missing easYgen latched Mask: 0008h All
08.48 MCB plausibility latched Mask: 0004h All
05.13 Red stop lamp latched Mask: 0002h All
05.14 Amber warning lamp latched Mask: 0001h All
50069 23 1-2 uint16 10286 BITLIST
08.53 LS interf.redundancy latched Mask: 8000h EG3500XT-

P1
EG3500XT-
P2
Internal Mask: 4000h All
16.04 Free alarm 4 latched Mask: 2000h All
05.21 Max. starts per time Mask: 0200h K36
17.09 Neutral contactor reply mismatch Mask: 0100h All

latched
17.08 Decoupling GCB<->MCB latched Mask: 0080h All
17.07 Meas.difference 4105 VDE-AR-N Mask: 0040h All

4105 latched
17.06 Parameter alignment VDE-AR-N Mask: 0020h All

4105 latched
17.05 Missing member VDE-AR-N 4105 Mask: 0010h All

latched
08.22 Busbar monitoring latched Mask: 0008h All
08.21 Feedback GCB mismatch latched Mask: 0004h MARINE
17.02 Reactive load share mismatch Mask: 0002h All

latched
17.01 Active load share mismatch Mask: 0001h All

latched
50072 24 1-2 uint16 10134 BITLIST Alarms Generator latched

(unacknowledged)

9 Appendix

Address Mux Byte
06.01 Generator over frequency 1 Mask: 8000h All

latched

latched
06.03 Generator under frequency 1 Mask: 2000h All

latched

latched
06.05 Generator over voltage 1 latched Mask: 0800h All
06.07 Generator under voltage 1 Mask: 0200h All

latched

latched
06.09 Generator over current 1 latched Mask: 0080h All
06.12 Reverse / reduced power 1 Mask: 0010h All

latched

latched
06.14 Generator overload IOP 1 latched Mask: 0004h All
06.34 Busbar phase rotation mismatch Mask: 0001h EG3500XT-

P2
50073 24 3-6 int32 108 Gen. voltage L1-L2 V *10 All
50075 25 1-2 uint16 10138 BITLIST Alarms Generator 1 latched

(unacknowledged)
06.16 Generator unbalanced load 1 Mask: 8000h All

latched

latched
06.18 Generator voltage asymmetry Mask: 2000h All

latched
06.19 Ground fault 1 latched Mask: 1000h All
06.21 Gen. Phase Rotation mismatch Mask: 0400h All

Latched
06.29 Gen. active power mismatch Mask: 0200h All

Latched
06.30 Generator unloading mismatch Mask: 0100h All

Latched
06.22 Inverse time over current Latched Mask: 0080h All
06.31 Operating Range failed latched Mask: 0040h All

9 Appendix

Address Mux Byte
06.23 Generator overload MOP 1 Mask: 0020h All

latched

latched
06.25 Gen.Power Factor lagging 1 Mask: 0008h All

latched

latched
06.27 Gen.Power Factor leading 1 Mask: 0002h All

latched

latched
50076 25 3-6 int32 114 Gen. voltage L1-N V *10 All
50078 26 1-2 uint16 10135 BITLIST
07.06 Mains over frequency 1 latched Mask: 8000h All
07.08 Mains under frequency 1 latched Mask: 2000h All
07.10 Mains over voltage 1 latched Mask: 0800h All
07.12 Mains under voltage 1 latched Mask: 0200h All
07.14 Mains Phase shift latched Mask: 0080h All
07.25 Mains decoupling latched Mask: 0040h All
Internal Mask: 0020h
07.05 Mains Phase rotation mismatch Mask: 0004h All

latched
50081 27 1-2 uint32 10278 BITLIST
07.21 Mains import power 1 latched Mask: 8000h All
07.23 Mains export power 1 latched Mask: 2000h All
07.17 Mains PF lagging 1 latched Mask: 0800h All
07.19 Mains PF leading 1 latched Mask: 0200h All

9 Appendix

Address Mux Byte
07.15 Mains df/dt latched Mask: 0080h All
07.16 Mains active power mismatch Mask: 0040h All

latched
07.28 Mains Time-dep. Voltage (FRT) Mask: 0020h All

latched
07.27 Mains slow voltage increase (10 Mask: 0008h All

min)
07.29 QU Monitoring step 1 tripped Mask: 0002h All
50084 28 1-2 uint16 10132 BITLIST
09.01 Discrete input 1 latched Mask: 8000h All
50087 29 1-2 uint32 10283 BITLIST
09.13 Discrete input 13 latched Mask: 8000h EG3500XT-

P2

P2

P2

P2

P2

9 Appendix

Address Mux Byte

P2

P2

P2

P2

P2

P2
50090 30 1-2 uint16 16377 BITLIST
12.16 External discrete input 16 latched Mask: 8000h All
50091 30 3-6 int32 118 Mains voltage L1-L2 V *10 All
50093 31 1-2 uint16 10279 BITLIST
15.16 Flexible limit 16 latched Mask: 8000h All

9 Appendix

Address Mux Byte
50094 31 3-6 int32 121 Mains voltage L1-N V *10 All
50096 32 1-2 uint16 10280 BITLIST
50099 33 1-2 uint16 10281 BITLIST

9 Appendix

Address Mux Byte
50102 34 1-2 uint16 10136 BITLIST
08.02 Battery over voltage 2 latched Mask: 0008h All
08.04 Battery under voltage 2 latched Mask: 0004h All
50105 35 1-2 uint16 10131 BITLIST
01.11 New Alarm triggered Mask: 8000h All

9 Appendix

Address Mux Byte
01.06 Alarm class F latched Mask: 0020h All
01.05 Alarm class E latched Mask: 0010h All
01.04 Alarm class D latched Mask: 0008h All
01.03 Alarm class C latched Mask: 0004h All
01.02 Alarm class B latched Mask: 0002h All
01.01 Alarm class A latched Mask: 0001h All
50108 36 1-2 uint16 10137 BITLIST
10.01 Analog input 1 wire break Mask: 0002h All
10.04 Analog input 4 wire break Mask: 0010h EG3500XT-

P2

P2

P2

P2

P2

P2

P2
50109 36 3-4 int16 15310 Turbocharger 1 Compressor Outlet °C *10 All

Temperature
50110 36 5-6 uint16 10285 BITLIST
25.01 Ext. analog input 1 wire break Mask: 0001h All

9 Appendix

Address Mux Byte
50111 37 1-2 uint16 10107 BITLIST
13.01 Relay-Output 1 (Self-test-relay) Mask: 8000h All
13.02 Relay-Output 2 Mask: 4000h All
50112 37 3-4 uint16 10109 BITLIST
13.13 Relay-Output 13 Mask: 8000h EG3500XT-

P2

P2

P2

9 Appendix

Address Mux Byte

P2

P2

P2

P2

P2

P2

P2
13.34 Transistor output 2 Mask: 0002h EG3500XT-

P2

P2
50113 37 5-6 uint16 8005 BITLIST
98.16 LM External DO 16 Mask: 8000h All
50114 38 1-2 int16 10310 Analog output 1 configurable All

9 Appendix

Address Mux Byte
50116 38 5-6 int16 10317 Analog output 3 configurable EG3500XT-

P2

P2

P2

P2
50120 40 1-2 uint16 10202 Status message. This is an index All

number. Refer to manual chapter State
messages for more information.
50121 40 3-6 int32 2520 Gen. real energy MWh *100 All
50123 41 1-2 int16 2540 Engine, number of startrequests *1 All
50124 41 3-6 int32 2522 Gen. positive reactive energy Mvarh *100 All
50126 42 1-2 int16 2558 Hours until next maintenance h *100 All
50127 42 3-6 int32 2568 Gen. hours of operation h *1 All
50129 43 1-2 int16 5541 Setpoint frequency Hz *100 All
50130 43 3-6 int32 5542 Setpoint active power kW *10 All
50132 44 1-4 int32 5640 Setpoint voltage V *1 All
50134 44 5-6 int16 5641 Setpoint power factor *1000 All
50135 45 1-2 uint16 4153 BITLIST
Idle mode monitoring OR ramp to rated Mask: 8000h All

state is active
04.15 Idle run is active Mask: 4000h All
04.12 Start without closing GCB Mask: 2000h All
A manual START has been requested Mask: 0800h All
A manual STOP has been requested Mask: 0400h All
04.10 Cooldown is active Mask: 0200h All
03.01 Auxiliary Services is active Mask: 0100h All
03.07 Engine monitoring delay expired Mask: 0080h All
03.08 Breaker delay timer has expired Mask: 0040h All
03.25 Engine shall run Mask: 0020h All
04.27 Critical mode is active Mask: 0010h All
03.06 Engine release is active Mask: 0008h All
03.30 Auxiliary services prerun is active Mask: 0004h All
03.31 Auxiliary services postrun is Mask: 0002h All

active
04.61 Lamp test request Mask: 0001h All
50136 45 3-4 uint16 4154 BITLIST
03.02 Starter / Crank is active Mask: 8000h All

9 Appendix

Address Mux Byte
03.28 Operating Magnet / Gasrelay is Mask: 4000h All

active
03.04 Preglow or Ignition is active Mask: 2000h All
04.11 Mains settling timer is running Mask: 1000h All
04.09 Emergency mode is currently Mask: 0800h All

active
03.40 Remote Shutdown (ID503, Bit9) Mask: 0400h All
03.37 Free PID Controller 3: Lower Mask: 0200h All

Command
03.36 Free PID Controller 3: Raise Mask: 0100h All

Command

Command

Command
03.27 Stop solenoid is active Mask: 0020h All
03.24 Excitation AVR (Run-up Mask: 0010h All

Synchronization)
The genset runs mains parallel Mask: 0008h All

Command

Command
Increment Engine Start Counter (pulse 1 Mask: 0001h All

second)
50137 45 5-6 uint16 4155 BITLIST
03.20 3-Pos. Controller Freq./Power raise Mask: 8000h All
03.21 3-Pos. Controller Freq./Power Mask: 4000h All

lower
03.22 3-Pos. Controller Volt./ReactPow Mask: 2000h All

raise

lower
04.06 GCB is closed Mask: 0800h All
04.07 MCB is closed Mask: 0400h All
05.16 Derating active (J1939 or freely) Mask: 0200h All
04.18 Synchronisation GCB procedure is Mask: 0100h All

active
04.19 Opening GCB relay is active Mask: 0080h All
04.20 Close command GCB is active Mask: 0040h All
04.21 Synchronisation MCB procedure is Mask: 0020h All

active
04.22 Open command MCB is active Mask: 0010h All
04.23 Close command MCB is active Mask: 0008h All

9 Appendix

Address Mux Byte
04.28 Unloading generator is active Mask: 0004h All
04.29 Unloading mains is active Mask: 0002h All
04.30 Power limited prerun Mask: 0001h All
50138 46 1-2 uint16 4156 BITLIST
04.16 GGB is closed Mask: 8000h EG3500XT-

P1
EG3500XT-
P2
04.17 GGB is released Mask: 4000h EG3500XT-

P1
EG3500XT-
P2
04.24 Synchronisation GGB procedure is Mask: 2000h EG3500XT-

active P1
EG3500XT-
P2
04.25 Open command GGB is active Mask: 1000h EG3500XT-

P1
EG3500XT-
P2
04.26 Close command GGB is active Mask: 0800h EG3500XT-

P1
EG3500XT-
P2
Dead busbar closure requ. for GCB,MCB Mask: 0400h All

or GGB
4.62 Active power load share is active Mask: 0200h All
4.63 Reactive power load share is active Mask: 0100h All
Generator with a closed GCB is Mask: 0080h All

requested
LDSS: The Engine shall start Mask: 0040h All
LDSS: The Engine shall stop Mask: 0020h All
LDSS: The Engine shall stop, if possible Mask: 0010h All
LDSS: Minimum Running Time is active Mask: 0008h All
04.43 The LDSS function is active Mask: 0004h All
04.60 Critical mode postrun Mask: 0002h All
AUTOMATIC Run: Switch to Operating Mask: 0001h All

Mode STOP
50139 46 3-4 uint16 4150 BITLIST ControlBits5
04.13 Remote Start request Mask: 8000h All
04.14 Remote acknowledge Mask: 4000h All
05.17 Uprating active Mask: 2000h All

9 Appendix

Address Mux Byte
86.25 LM Frequency Droop active Mask: 1000h All
86.26 LM Voltage Droop active Mask: 0800h All
Synchronization mode Check active Mask: 0400h All
Synchronization mode Permissive active Mask: 0200h All
Synchronization mode Run active Mask: 0100h All
86.85 LM Enable MCB Mask: 0080h All
86.41 LDSS IOP Reserve power 2 ready Mask: 0040h All
86.42 LDSS MOP Reserve power 2 ready Mask: 0020h All
02.39 Mains decoubling enabled Mask: 0010h All
04.70 Opening GCB active Mask: 0008h All
Parameter set 1-7 selection Bit 3 Bit Mask: 0004h Rental
50140 46 5-6 uint16 10284 BITLIST Alarm Ext. DI 2 latched

(unacknowledged)
50141 47 1-2 uint16 8009 BITLIST Relay Outputs 4

9 Appendix

Address Mux Byte
50142 47 3-4 int16 10170 External Analog input 1 configurable All
50158 52 5-6 int16 10245 External Analog Output 1 % *100 All
50163 54 3-6 int32 2580 Period of use counter h *100 All
50165 55 1-2 uint16 10190 BITLIST Alarms 3 latched

(unacknowledged)
08.34 GGB fail to close latched Mask: 8000h EG3500XT-

P1
EG3500XT-
P2

9 Appendix

Address Mux Byte
08.35 GGB fail to open latched Mask: 4000h EG3500XT-

P1
EG3500XT-
P2
08.27 Missing easYgen Mask: 2000h All
08.28 Missing LSx Mask: 1000h EG3500XT-

P1
EG3500XT-
P2
05.18 Cylinder temperature level 1 Mask: 0800h All
05.20 Cylinder temperature wire break Mask: 0200h All
6.35 Pole slip Mask: 0100h All
08.44 Syst.update LSx Mask: 0080h EG3500XT-

P1
EG3500XT-
P2
08.43 Syst.update easYgen Mask: 0040h All
06.32 Gen.AC Wiring Mask: 0020h All
06.33 Busbar1 AC Wiring Mask: 0010h EG3500XT-

P1
EG3500XT-
P2
50166 55 3-6 int32 219 Nominal active power in system (in own kW *1 All
segment)
50168 56 1-2 uint16 4157 BITLIST ControlBits6
28.01 Command 1 to LSx (OR) Mask: 8000h EG3500XT-

P1
EG3500XT-
P2

P1
EG3500XT-
P2

P1
EG3500XT-
P2

9 Appendix

Address Mux Byte

P1
EG3500XT-
P2

P1
EG3500XT-
P2

P1
EG3500XT-
P2
02.38 Gen excitation limit active Mask: 0200h All
03.39 Neutral interlocking - Closed NC Mask: 0100h All
Extended Busbar F okay Mask: 0040h Marine
Extended Busbar V okay Mask: 0020h Marine
Extended Busbar F/V okay Mask: 0010h Marine
Extended Busbar is dead Mask: 0008h Marine
Phaseangle MNS/BUS okay Mask: 0004h Marine
Phaseangle GEN/BUS okay Mask: 0002h Marine
03.38 Inhibit cranking Mask: 0001h All
50169 56 3-6 int32 218 Active real power in system (in own kW *1 All
segment)
50172 57 3-6 int32 217 Active power reserve in system (in own kW *1 All
segment)
50174 58 1-2 int16 15109 J1939 MTU ADEC ECU Failure Codes *1 All
50175 58 3-4 int16 239 System act.nom.pwr. % *100 All
50176 58 5-6 int16 240 Syst.total real pwr. % *100 All
50177 59 1-2 uint16 15304 J1939 EMR Engine Stop Information All
(refer to DEUTZ-specific J1939-Message)
"Missing" Value="65535"
"Error" Value="65279"
"Type 9" Value="9"
"Type 8" Value="8"
"Type 7" Value="7"
"Type 6" Value="6"
"Type 5" Value="5"
"Type 4" Value="4"

9 Appendix

Address Mux Byte
"Type 3" Value="3"
"Type 2" Value="2"
"Type 1" Value="1"
"Type 0" Value="0"
50178 59 3-4 int16 241 Syst.res.real power % *100 All
50179 59 5-6 int16 15311 Engine Derate Request % *10 All
50180 60 1-2 uint16 15305 BITLIST J1939 DLN2-Message Scania S6
Engine Coolant Temperature Mask F000h
J1939-Message not available Mask 8000h All
Sensor fault Mask 4000h All
High Temperature. Mask 2000h All
NOT High Temperature Mask 1000h All
Engine Oil Pressure Mask 0F00h
Low Pressure Mask 0200h All
NOT Low Pressure Mask 0100h All
High Engine Oil Level Mask 00F0h
High Level Mask 0020h All
NOT High Level Mask 0010h All
Low Engine Oil Level Mask 000Fh
Low Level Mask 0002h All
NOT Low Level Mask 0001h All
50181 60 3-4 int16 15313 Aftertreatment 1 Diesel Exhaust Fluid % *10 All
Tank Level
50182 60 5-6 int16 15312 Battery Potential, Switched V *10 All
1. Active Diagnostic Trouble Code (DM1)
50183 61 1-4 uint32 15400 SPN All
50185 61 5-6 uint16 BITLIST
15401 FMI Mask FF00h All
15402 OC Mask 00FFh All
50186 62 1-4 uint32 15403 SPN All

9 Appendix

Address Mux Byte
50189 63 1-4 uint32 15406 SPN All
50192 64 1-4 uint32 15409 SPN All
50195 65 1-4 uint32 15412 SPN All
50198 66 1-4 uint32 15415 SPN All
50201 67 1-4 uint32 15419 SPN All
50203 67 5-6 uint16 15420 BITLIST
FMI Mask FF00h All
50204 68 1-4 uint32 15422 SPN All
50206 68 5-6 uint16 15423 BITLIST
FMI Mask FF00h All
50207 69 1-4 uint32 15425 SPN All

9 Appendix

Address Mux Byte
50210 70 1-4 uint32 15428 SPN All
1. Previously Active Diagnostic Trouble Code (DM2)
50213 71 1-4 uint32 15450 SPN low 16 bits All

of 19 bits of
SPN

of 19 bits of
SPN

of 19 bits of
SPN
50222 74 1-4 uint32 15459 SPN All
50225 75 1-4 uint32 15462 SPN All
50228 76 1-4 uint32 15465 SPN All

9 Appendix

Address Mux Byte
50231 77 1-4 uint32 15468 SPN All
50234 78 1-4 uint32 15471 SPN All
50237 79 1-4 uint32 15474 SPN All
50240 80 1-4 uint32 15477 SPN All
50243 81 1-2 uint16 15395 BITLIST J1939 Lamp Status DM1
Malfunction Lamp
Internal Mask 8000h
Internal Mask 4000h
On Mask 2000h All
Off Mask 1000h All
Red Stop Lamp
Internal Mask 0800h
Internal Mask 0400h
On Mask 0200h All
Off Mask 0100h All
Amber Warning Lamp
Internal Mask 0080h
Internal Mask 0040h
On Mask 0020h All
Off Mask 0010h All

9 Appendix

Address Mux Byte
Protect Lamp
Internal Mask 0008h
Internal Mask 0004h
On Mask 0002h All
Off Mask 0001h All
50244 81 3-4 uint16 15445 BITLIST J1939 Lamp Status DM2
Malfunction Lamp
Internal Mask 8000h
Internal Mask 4000h
On Mask 2000h All
Off Mask 1000h All
Red Stop Lamp
Internal Mask 0800h
Internal Mask 0400h
On Mask 0200h All
Off Mask 0100h All
Amber Warning Lamp
Internal Mask 0080h
Internal Mask 0040h
On Mask 0020h All
Off Mask 0010h All
Protect Lamp
Internal Mask 0008h
Internal Mask 0004h
On Mask 0002h All
Off Mask 0001h All
50245 81 5-6 int16 15314 Aftertreatment 1 Diesel Exhaust Fluid °C *1 All

Tank Temperature
50246 82 1-4 int32 15200 Engine Speed (j1939-EEC1) rpm *10 All
Value for Error indicator: FFFFFFFEh
Value for Not available: FFFFFFFFh
50248 82 5-6 int16 15202 Engine Coolant Temperature (J1939-ET1) °C *1 All
Value for Error indicator: FFFEh
Value for Not available: FFFFh
50249 83 1-4 int32 15201 Total engine hours (j1939-HOURS) h *1 All

9 Appendix

Address Mux Byte
50251 83 5-6 int16 15203 Fuel temperature (j1939-ET1) °C *1 All
50252 84 1-4 int32 15204 Engine Oil Temperature (j1939-ET1) °C *100 All
50254 84 5-6 int16 15205 Engine Oil Pressure (j1939-EFL/P1) kPa *1 All
50255 85 1-4 int32 15211 Fuel Rate (j1939-LFE) L/h *100 All
50257 85 5-6 int16 15206 Coolant Level (j1939-EFL/P1) % *10 All
50258 86 1-2 int16 15207 Throttle position (j1939-EEC2) % *10 All
50259 86 3-4 int16 15208 Load at current Speed (j1939-EEC2) % *1 All
50260 86 5-6 int16 15210 Engine oil level (j1939-EFL/P1) % *10 All
50261 87 1-2 int16 15214 Boost pressure (j1939-IC1) kPa *1 All
50262 87 3-4 int16 15215 Intake Manifold Temp (j1939-IC1) °C *1 All
50263 87 5-6 int16 15212 Barometric Pressure (j1939-AMB) kPa *10 All
50264 88 1-2 int16 15213 Air inlet temperature (j1939-AMB) °C *1 All

9 Appendix
9.2.2 Protocol 5004 (Generator Values Visualization)

Address Mux Byte
50265 88 3-4 int16 15209 Actual engine torque (j1939-EEC1) % *1 All
50266 88 5-6 int16 15315 Aftertreatment 1 Diesel Exhaust Fluid % *10 All
Tank 2 Level
50267 89 1-4 int32 15216 Exhaust Gas Temp.(J1939-IC1) °C *100 All
50269 89 5-6 int16 15316 Aftertreatment 1 Diesel Exhaust Fluid °C *1 All

Tank 2 Temperature
CAN CAN Size Index Description Unit Scale Model

Mux Byte
0 1-2 uint16 Telegram-ID, allways 5004
0 3-4 int16 10100 Pickup speed rpm *1 All
0 5-6 int16 - Internal All
1 1-2 int16 160 Gen. powerfactor *1000 All
1 3-6 int32 170 Av. Gen. Wye-Voltage V *10 All
2 1-2 int16 144 Gen. frequency Hz *100 All
2 3-6 int32 171 Av. Gen. Delta-Voltage V *10 All
3 1-2 int16 10310 Analog output 1 % configurable All
3 3-6 int32 185 Av. Gen. Current A *1000 All
4 1-2 int16 10311 Analog output 2 % configurable All
4 3-6 int32 161 Meas. ground current A *1000 All
5 1-2 uint16 10133 BITLIST Alarms 1 latched (unacknowledged)
05.01 Engine Over speed 1 latched Mask: 8000h All
05.03 Engine under speed 1 latched Mask: 2000h All
05.05 Unintended stop detected latched Mask: 0800h All
05.07 Speed detection alarm latched Mask: 0400h All
05.06 Shutdown malfunction detected Mask: 0200h All

latched
08.05 GCB fail to close latched Mask: 0100h All

9 Appendix

Mux Byte
08.06 GCB fail to open latched Mask: 0080h All
08.07 MCB fail to close latched Mask: 0040h All
08.08 MCB fail to open latched Mask: 0020h All
08.10 General CAN-J1939 fault latched Mask: 0010h All
05.08 Start fail detected latched Mask: 0008h All
05.09 Maintenance days exceeded latched Mask: 0004h All
05.10 Maintenance hours exceeded latched Mask: 0002h All
5 3-6 int32 159 Calculated ground current A *1000 All
08.30 Timeout Synchronisation GCB latched Mask: 8000h All
08.31 Timeout Synchronisation MCB latched Mask: 4000h All
08.32 Timeout Synchronisation GGB latched Mask: 2000h EG3500XT-P1
EG3500XT-P2
05.11 Charge fail (D+ functionality) latched Mask: 1000h All
Operating range failure 12 latched Mask: 0800h All
08.45 CPU overload R1 trip latched Mask: 0400h All
08.47 MCB failure 50BF Mask: 0200h All
08.46 GCB failure 50BF Mask: 0100h All
05.22 ECU Protect alarm Mask: 0080h All
05.23 ECU Emission alarm Mask: 0040h All
08.16 Parameter Alignment LDSS Mask: 0010h All
08.17 Missing members Mask: 0008h All
08.48 MCB plausibility Mask: 0004h All
05.13 ECU red lamp alarm latched Mask: 0002h All
05.14 ECU yellow (amber) lamp alarm latched Mask: 0001h All
6 3-6 int32 111 Gen. current 1 A *1000 All
7 5-6 int16 Internal All
8 5-6 int16 Internal All
9 1-4 int32 135 Total gen. power W *1 All
9 5-6 uint16 10134 BITLIST Alarms Gen latched

(unacknowledged)
06.01 Generator over frequency 1 latched Mask: 8000h All

9 Appendix

Mux Byte
06.03 Generator under frequency 1 latched Mask: 2000h All
06.07 Generator under voltage 1 latched Mask: 0200h All
06.12 Reverse / reduced power 1 latched Mask: 0010h All
06.34 Busbar phase rotation mismatch Mask: 0001h EG3500XT-P2

latched
10 1-4 int32 136 Total gen. reactive power var *1 All
10 5-6 uint16 10138 BITLIST Alarms Gen 1 latched

(unacknowledged)
06.16 Generator unbalanced load 1 latched Mask: 8000h All
06.18 Generator voltage asymmetry latched Mask: 2000h All
06.21 Gen. Phase Rotation mismatch Latched Mask: 0400h All
06.29 Gen. active power mismatch Latched Mask: 0200h All
06.30 Generator unloading mismatch Latched Mask: 0100h All
06.23 Generator overload MOP 1 latched Mask: 0020h All
06.25 Gen.Power Factor lagging 1 latched Mask: 0008h All
06.27 Gen.Power Factor leading 1 latched Mask: 0002h All
11 1-4 int32 108 Gen. voltage L1-L2 V *10 All
11 5-6 uint16 10131 BITLIST Alarm General

9 Appendix

Mux Byte
12 1-2 uint16 4153 BITLIST ControlBits1
Idle mode OR Ramp to rated active Mask: 8000h All
04.64 Key activation Mask: 1000h All
03.31 Auxiliary services postrun is active Mask: 0002h All
12 3-6 int32 114 Gen. voltage L1-N V *10 All
14 1-4 int32 115 Gen. voltage L2-N V *10 All

9 Appendix

Mux Byte
16 1-4 int32 116 Gen. voltage 3-N V *10 All
17 1-4 int32 2522 Positive reactive gen energy Mvarh *100 All
18 1-2 int16 5541 Frequency setpoint Hz *100 All
18 3-6 int32 5542 Active Power setpoint kW *10 All
19 1-4 int32 5640 Voltage setpoint V *1 All
19 5-6 int16 5641 Power Factor setpoint *1000 All
03.28 Operating Magnet / Gasrelay is active Mask: 4000h All
04.09 Emergency mode is currently active Mask: 0800h All
03.33 Free PID Controller 3: Lower Command Mask: 0200h All
03.32 Free PID Controller 3: Raise Command Mask: 0100h All
03.24 Excitation AVR (Run-up Mask: 0010h EG3500XT-P1

Synchronization)
EG3500XT-P2
Increment Engine Start Counter Mask: 0001h All
03.21 3-Pos. Controller Freq./Power lower Mask: 4000h All
03.22 3-Pos. Controller Volt./ReactPow raise Mask: 2000h All
03.23 3-Pos. Controller Volt./ReactPow lower Mask: 1000h All

active

9 Appendix

Mux Byte

active
04.16 GGB is closed Mask: 8000h EG3500XT-P1
EG3500XT-P2
04.17 GGB is released Mask: 4000h EG3500XT-P1
EG3500XT-P2
04.24 Synchronisation GGB procedure is Mask: 2000h EG3500XT-P1

active
EG3500XT-P2
04.25 Open command GGB is active Mask: 1000h EG3500XT-P1
EG3500XT-P2
04.26 Close command GGB is active Mask: 0800h EG3500XT-P1
EG3500XT-P2
Dead busbar closure requ. for GCB,MCB or Mask: 0400h All

GGB
Generator with a closed GCB is requested Mask: 0080h All
AUTOMATIC Run: Switch to Operating Mode Mask: 0001h All

STOP

9 Appendix
9.2.3 Protocol 5005 (Mains Values Visualization)
9.2.3 Protocol 5005 (Mains Values Visualization)

Mux Byte
0 1-2 int16 Protocoll-ID (allways 5005) All
0 3-4 int16 10100 Pickup speed rpm *1 All
0 5-6 int16 - Internal
1 1-2 int16 147 Mains frequency Hz *100 All
1 3-6 int32 173 Av. Mains Wye-Voltage V *10 All
2 1-2 int16 208 Mains power factor *1000 All
2 3-6 int32 174 Av. Mains Delta-Voltage V *10 All
3 1-4 int32 207 Av. Mains Current V *10 All
4 1-2 int16 10111 Analog input 1 configurable All
4 3-6 int32 134 Mains current L1 A *1000 All
5 3-6 int32 140 Total mains power W *1 All
6 3-6 int32 150 Total mains reactive power var *1 All
7 1-2 uint16 10135 BITLIST Alarms Mains latched

(unacknowledged)
07.32 Mains AC Wiring Mask: 0020h All
07.05 Mains Phase rotation mismatch latched Mask: 0004h All
7 3-4 uint16 10278 BITLIST Alarms Mains 1 latched

(unacknowledged)

9 Appendix

Mux Byte
07.16 Mains active power mismatch latched Mask: 0040h All
07.28 Mains Time-dep. Voltage 1 (FRT) Mask: 0020h All

latched

latched
07.27 Mains slow voltage increase (10 min) Mask: 0008h All

latched
07.29 Mains QV Monitoring step 1 latched Mask: 0002h All
7 5-6 int16 Internal
8 1-4 int32 118 Mains voltage L1-L2 V *10 All
9 1-4 int32 121 Mains voltage L1-N V *10 All
Modbus- Size Index Description Unit Scale Model

Address
50000 int16 Protocoll-ID, always 5010 All
50001 int16 3181 Skaling Power (16 bits) Exponent 10* W All
(5;4;3;2)

9 Appendix

Address
50002 int16 3182 Skaling Volts (16 bits) Exponent 10* V All
(2;1;0;-1)
50003 int16 3183 Skaling Amps (16 bits) Exponent 10* A (0;-1) All
50004 Internal
50005 Internal
50006 Internal
50007 Internal
50008 Internal
Topic AC Generator and Busbar values
50009 int16 144 Generator frequency Hz *100 All
50010 int16 246 Total generator power W format All

defined by
index 3181
(Modbus-
Address
50001)
50011 int16 247 Total generator reactive power var format All
defined by
index 3181
(Modbus-
Address
50001)
50012 int16 160 Generator power factor *1000 All
50013 int16 248 Generator voltage L1-L2 V format All

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)
50016 int16 251 Generator voltage L1-N V format All

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182

9 Appendix

Address
(Modbus-
Address
50002)
50019 int16 255 Generator current 1 A format All

defined by
index 3183
(Modbus-
Address
50003)

defined by
index 3183
(Modbus-
Address
50003)

defined by
index 3183
(Modbus-
Address
50003)
50022 int16 209 Busbar 1: Frequency Hz *100 All
50023 int16 254 Busbar 1: Voltage L1-L2 V format All

defined by
index 3182
(Modbus-
Address
50002)
50024 int16 279 Busbar 1: Voltage L2-L3 V format EG3500XT-P2

defined by
index 3182
(Modbus-
Address
50002)
50025 int16 280 Busbar 1: Voltage L3-L1 V format EG3500XT-P2

defined by
index 3182
(Modbus-
Address
50002)
50026 int16 Internal
50028 int16 5541 Setpoint frequency Hz *1 All
50029 int16 5641 Setpoint power factor (cosphi) *1 All
Topic AC Mains values
50030 int16 147 Mains frequency Hz *100 All
50031 int16 258 Total mains power W format All

defined by
index 3181
(Modbus-
Address
50001)
50032 int16 259 Total mains reactive power var format All
defined by
index 3181
(Modbus-
Address
50001)

9 Appendix

Address
50033 int16 208 Mains power factor *1000 All
50034 int16 260 Mains voltage L1-L2 V format All

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)
50037 int16 263 Mains voltage L1-N V format All

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)
50040 int16 266 Mains current L1 A format All

defined by
index 3183
(Modbus-
Address
50003)
50043 int16 267 Average LSx Delta Mains voltage L-L V format EG3500XT-P1
defined by
index 3182 EG3500XT-P1
(Modbus-
Address
50002)
50044 int16 268 Average LSx Wye Mains voltage L-N V format EG3500XT-P1
defined by
(Modbus-
Address
50002)
Topic AC System values
50045 int16 239 Nominal real power in system % *100 All

9 Appendix

Address
50046 int16 240 Real power in system % *100 All
50047 int16 241 Reserve real power in system % *100 All
50048 int16 269 Active power LSx W format EG3500XT-P1

defined by
(Modbus-
Address
50001)
50049 int16 270 Reactive power LSx var format EG3500XT-P1

defined by
(Modbus-
Address
50001)
50050 int16 4608 Average LSx Mains delta frequency L-L Hz *100 EG3500XT-P1
EG3500XT-P1
Topic DC Analogue Values (Engine Values)
50051 int16 10100 Engine Pickup speed rpm *1 All
50052 int16 10110 Battery voltage V *10 All
50053 int16 10159 AI Auxiliary excitation D+ V *10 All
50054 int16 2540 Engine, number of startrequests *1 All
50055 int16 2558 Hours until next maintenance h *1 All
50056 int16 10111 Analog input 1 configurable All
50059 int16 10117 Analog input 4 configurable EG3500XT-P2
50066 int16 10157 Analog input 11
50068 int16 10310 Analog output 1 % configurable All
50070 int16 10317 Analog output 3 % configurable EG3500XT-P2
50074 int16 10170 External Analog input 1 configurable All

9 Appendix

Address
50090 int16 10245 External Analog Output 1 % configurable All
50094 int16 2556 Days until next maintenance days *1 All
Topic Control and Status
50099 int16 BITLIST
Control mode (STOP/AUTO/MANUAL/TEST) Mask: 000Fh All
50100 int16 10202 Status message. This is an index number. All

Refer to manual chapter State messages for
more information.
50102 int16 4153 BITLIST ControlBits1

9 Appendix

Address
03.24 Excitation AVR (Run-up Synchronization) Mask: 0010h EG3500XT-P1
EG3500XT-P2

9 Appendix

Address
04.18 Synchronisation GCB procedure is active Mask: 0100h All
04.21 Synchronisation MCB procedure is active Mask: 0020h All
EG3500XT-P2
EG3500XT-P2
04.24 Synchronisation GGB procedure is active Mask: 2000h EG3500XT-P1
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2

GGB

STOP

9 Appendix

Address
Parameter set 1-7 selection Bit 3 Mask: 0004h Rental
Topic Discrete Outputs
50108 int16 10107 BITLIST Relay Outputs 1
13.13 Relay-Output 13 Mask: 8000h EG3500XT-P2

9 Appendix

Address
13.34 Transistor output 2 Mask: 0002h EG3500XT-P2

9 Appendix

Address
28.01 Command 1 to LSx (OR) Mask: 8000h EG3500XT-P1
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2
Topic Alarm Management

9 Appendix

Address
Subtopic General
50114 int16 10131 BITLIST Alarm General
50115 int16 10149 BITLIST Alarms 2 latched (unacknowledged)
EG3500XT-P2
50116 int16 4169 Alarms 2 active (reserved)

9 Appendix

Address
08.34 GGB fail to close latched Mask: 8000h EG3500XT-P1
EG3500XT-P2
08.35 GGB fail to open latched Mask: 4000h EG3500XT-P1
EG3500XT-P2
08.28 Missing LS5 Mask: 1000h EG3500XT-P1
EG3500XT-P2
08.44 Syst.update LS5 Mask: 0080h EG3500XT-P1
EG3500XT-P2
06.33 Busbar1 AC Wiring Mask: 0010h EG3500XT-P1
EG3500XT-P2

9 Appendix

Address
Subtopic Engine
05.06 Shutdown malfunction detected latched Mask: 0200h All

9 Appendix

Address
50122 int16 10136 BITLIST Alarms AI 1 latched (unacknowledged)
05.11 Failure Charging Alternator (D+) Mask: 0010h All
50123 int16 4171 Alarms Analog Inputs 1 active (reserved)

9 Appendix

Address
Subtopic Generator
50126 int16 10134 BITLIST Alarms Gen latched (unacknowledged)
06.34 Busbar phase rotation mismatch latched Mask: 0001h EG3500XT-P2
50127 int16 4161 Alarms Generator active (reserved)

9 Appendix

Address
50128 int16 10138 BITLIST Alarms Gen 1 latched

(unacknowledged)
50129 int16 4163 Alarms Generator 1 active (reserved)

9 Appendix

Address
Subtopic Mains
50132 int16 10135 BITLIST Alarms Mains latched

(unacknowledged)
50133 int16 4188 BITLIST Alarms Mains active
Mains over frequency 1 Mask: 8000h All
Mains under frequency 1 Mask: 2000h All

9 Appendix

Address
Mains over voltage 1 Mask: 0800h All
Mains under voltage 1 Mask: 0200h All
Mains Phase shift Mask: 0080h All
Mains decoupling Mask: 0040h All
Mains AC Wiring Mask: 0020h All
Mains Phase rotation mismatch Mask: 0004h All
50134 int16 10278 BITLIST Alarms Mains 1 latched

(unacknowledged)
07.28 Mains Time-dep. Voltage 1 (FRT) latched Mask: 0020h All
50135 int16 4187 Alarms Mains 1 active (reserved)

9 Appendix

Address
Subtopic Digital Inputs
50138 int16 10132 BITLIST Alarms DI 1 latched (unacknowledged)
50139 int16 4181 Alarms Digital Inputs 1 active (reserved)

9 Appendix

Address
50140 int16 16377 BITLIST Alarms Ext. DI 1 latched

(unacknowledged)
50141 int16 4185 Alarms External Digital Inputs active

(reserved)

9 Appendix

Address
50142 int16 10284 BITLIST Alarm Ext. DI 2 latched

(unacknowledged)
50143 int16 4195 Alarm External Digital Inputs 1 active

(reserved)

9 Appendix

Address
50144 int16 10283 BITLIST Alarms DI 2 latched (unacknowledged)
09.13 Discrete input 13 latched Mask: 8000h EG3500XT-P2
50145 int16 4183 Alarms Digital Inputs 2 active (reserved)

9 Appendix

Address
Subtopic Flexible Thresholds
50150 int16 10279 BITLIST Alarms Flex.Thresholds 1-16 latched
50151 int16 4175 Alarms Flexible thresholds 1-16 active

(reserved)

9 Appendix

Address

(reserved)

9 Appendix

Address

(reserved)

9 Appendix

Address
Subtopic DC Analogue Values Wirebreak
50159 int16 10137 BITLIST Alarms AI Wire Break latched
10.04 Analog input 4 wire break Mask: 0010h EG3500XT-P2
50160 int16 4173 Alarms Analog Inputs Wire Break active

(reserved)
50161 int16 10285 BITLIST Alarms Ext.AI Wire Break latched

9 Appendix

Address
50162 int16 4196 Alarms External Analog Inputs Wire Break

active (reserved)
Subtopic GAP Alarms

9 Appendix

Address
50165 int16 10286 BITLIST Other Alarms 1 latched

(unacknowledged)
08.53 LS interface redundancy latched Mask: 8000h EG3500XT-P1
EG3500XT-P2
Free alarm 4 Mask: 2000h All
17.09 Neutral interl. reply mismatch latched Mask: 0100h All
17.08 Decoupling GCB-MCB latched Mask: 0080h All
17.07 Measurement difference 4105 latched Mask: 0040h All
17.06 Parameter alignment 4105 latched Mask: 0020h All
17.05 Missing member 4105 latched Mask: 0010h All
08.22 Busbar v/f not ok latched Mask: 0008h All
17.02 Reactive load share mismatch latched Mask: 0002h All
17.01 Active load share mismatch latched Mask: 0001h All
50166 int16 5197 Alarms GAP active (reserved)

9 Appendix

Address
Topic Engine Management
Subtopic Active Diagnostic Trouble Code (DM1) 1-10 (SPN Range 0…65535)full SPN value at 450425-450444
50171 int16 15400 SPN of 1. entry low 16 bits of All

19 bits of SPN
50172 uint16 BITLIST

19 bits of SPN

19 bits of SPN

19 bits of SPN

19 bits of SPN

19 bits of SPN

9 Appendix

Address

19 bits of SPN
50184 uint16 15420 BITLIST
FMI Mask FF00h All

19 bits of SPN
FMI Mask FF00h All

19 bits of SPN

19 bits of SPN
Subtopic DM1 Lamp Status
50191 int16 15395 BITLIST J1939 Lamp Status DM1
Internal Mask 8000h
Internal Mask 4000h
On Malfunction Lamp Mask 2000h All
Off Malfunction Lamp Mask 1000h All
Internal Mask 0800h
Internal Mask 0400h
On Red Stop Lamp Mask 0200h All
Off Red Stop Lamp Mask 0100h All
Internal Mask 0080h
Internal Mask 0040h
On Amber Warning Lamp Mask 0020h All
Off Amber Warning Lamp Mask 0010h All

9 Appendix

Address
Internal Mask 0008h
Internal Mask 0004h
On Protect Lamp Mask 0002h All
Off Protect Lamp Mask 0001h All
50192 int16 15445 BITLIST J1939 Lamp Status DM2
Internal Mask 8000h
Internal Mask 4000h
Internal Mask 0800h
Internal Mask 0400h
Internal Mask 0080h
Internal Mask 0040h
Internal Mask 0008h
Internal Mask 0004h
Subtopic Especially Failure Codes
50193 int16 15109 J1939 MTU ADEC ECU Failure Codes *1 All
50195 uint16 15304 J1939 EMR Engine Stop Information All
"Type 9" Value="9"
"Type 8" Value="8"
"Type 7" Value="7"
"Type 6" Value="6"
"Type 5" Value="5"
"Type 4" Value="4"
"Type 3" Value="3"
"Type 2" Value="2"

9 Appendix

Address
"Type 1" Value="1"
"Type 0" Value="0"
50197 int16 15305 BITLIST J1939 DLN2-Message Scania S6
Engine Coolant Temperature
Engine Oil Pressure
High Engine Oil Level
Low Engine Oil Level
Subtopic Values
50201 int16 15308 Engine Speed (SPN 190) rpm *1 All
50202 int16 15202 Engine Coolant Temperature (SPN 110) °C *1 All
50203 int16 15203 Fuel temperature (SPN 174) °C *1 All
50204 int16 15309 Engine Oil Temperature 1 (SPN 175) °C *10 All
50205 int16 15205 Engine Oil Pressure (SPN 100) kPa *1 All
50206 int16 15307 Fuel Rate (SPN 183) L/h *10 All
50207 int16 15206 Coolant Level (SPN 111) % *10 All
50208 int16 15207 Throttle position (SPN 91) % *10 All
50209 int16 15208 Load at current Speed (SPN 92) % *1 All

9 Appendix

Address
50210 int16 15210 Engine oil level (SPN 98) % *10 All
50211 int16 15214 Boost pressure (SPN 102) kPa *1 All
50212 int16 15215 Intake Manifold 1 Temp (SPN 105) °C *1 All
50213 int16 15212 Barometric Pressure (SPN 108) kPa *10 All
50214 int16 15213 Air inlet temperature (SPN 172) °C *1 All
50215 int16 15209 Actual engine torque (SPN 513) % *1 All
50216 int16 15299 Exhaust Gas Temp.(SPN 173) °C *10 All
50217 int16 15217 Engine Intercooler Temp (SPN52) °C *1 All
50218 int16 15218 Fuel Delivery Pressure (SPN94) kPa *1 All
50219 int16 15219 Fuel Filter Differential Pressure (SPN95) kPa *1 All
50220 int16 15220 Crankcase Pressure (SPN101) kPa *1 All
50221 int16 15221 Turbo Air Inlet Pressure (SPN106) kPa *1 All
50222 int16 15222 Air Filter 1 Differential Pressure (SPN107) kPa *100 All
50223 int16 15223 Coolant Pressure (SPN109) kPa *1 All
50224 int16 15224 Transmission Oil Pressure (SPN127) kPa *1 All
50225 int16 15225 Fuel Rail Pressure (SPN157) MPa *10 All
50226 int16 15226 Ambient Air Temperature (SPN171) °C *10 All
50227 int16 15227 Turbo Oil Temperature (SPN176) °C *10 All
50228 int16 15228 Transmission Oil Temperature (SPN177) °C *10 All
50229 int16 15229 Auxiliary Temperature 1 (SPN441) °C *1 All
50232 int16 15231 Alternator Bear. 1 Temperature (SPN1122) °C *1 All
50234 int16 15233 Alternator Wind. 1 Temperature (SPN1124) °C *1 All
50237 int16 15236 Intake Manifold 2 Temperature (SPN1131) °C *1 All
50240 int16 15239 Engine Intercooler Thermostat Opening % *10 All

(SPN1134)
50241 int16 15240 Engine Oil Temperature 2 (SPN1135) °C *10 All
50242 int16 15241 Engine ECU Temperature (SPN1136) °C *10 All
50243 int16 15242 Exhaust Gas Port 1 Temperatures (SPN1137) °C *10 All

9 Appendix

Address
50263 int16 15262 Main Bearing 1 Temperatures (SPN1157) °C *10 All
50274 int16 15273 Turbo 1 Compressor Inlet Temperatures °C *10 All

(SPN1172)

(SPN1173)

(SPN1174)

(SPN1175)
50278 int16 15277 Turbo 1 Compressor Inlet Pressure (SPN1176) kPa *1 All

9 Appendix

Address
50282 int16 15281 Turbo 1 Turbine Inlet Temperature (SPN1180) °C *10 All
50283 int16 15282 Turbo 2 Turbine Inlet Temperature (SPN 1181) °C *10 All
50286 int16 15285 Turbo 1 Turbine Outlet Temperature (SPN1184) °C *10 All
50288 int16 15287 Turbo 3 Turbine Outlet Temperature (SPN °C *10 All
1186)
50290 int16 15289 Engine Aux. Coolant Pressure (SPN1203) kPa *1 All
50291 int16 15290 Pre-filter Oil Pressure (SPN1208) kPa *1 All
50292 int16 15291 Engine Aux. Coolant Temperature (SPN1212) °C *1 All
50294 int16 15293 Battery 1 Temperature (SPN1800) °C *1 All
50298 int16 15297 Right Exhaust Gas Temperature (SPN2433) °C *10 All
50299 int16 15298 Left Exhaust Gas Temperature (SPN2434) °C *10 All
50300 int16 15310 Turbo 1 Compr. Outlet Temperature (SPN2629) °C *10 All
50301 int16 15311 Engine derate request (SPN3644) % *10 All
50302 int16 15312 Batterie Potential (SPN0158) V *10 All
50303 int16 15313 Aftertreatment 1 Diesel Exhaust Fluid Tank 1 % *10 All
Level (SPN1761)
50304 int16 15314 Aftertreatment 1 Diesel Exhaust Fluid Tank 1 °C *1 All

Temperature (SPN3031)
Level (SPN4367)

50307 int16 12807 Exhaust Gas Temperature Average(SPN 4151) °C *10 All
50308 int16 12809 Exhaust Gas Temperature Average Bank 1 °C *10 All
(SPN 4153)
(SPN 4152)

9 Appendix

Address
Int32 (Long)
50322 int32 135 Total gen. power W *1 All
50324 int32 136 Total gen. reactive power var *1 All
50326 int32 137 Total gen. apparent power VA *1 All
50328 int32 170 Av. Gen. Wye-Voltage V *10 All
50330 int32 171 Av. Gen. Delta-Voltage V *10 All
50332 int32 216 Av. Busbar 1 Delta-Voltage V *10 All
50334 int32 185 Av. Gen. Current A *1000 All
50336 int32 111 Gen. current 1 A *1000 All
50342 int32 161 Meas. ground current A *1000 All
50344 int32 159 Calculated ground current A *1000 All
50346 int32 108 Gen. voltage L1-L2 V *10 All
50352 int32 114 Gen. voltage L1-N V *10 All
50358 int32 125 Gen. active power 1-N W *1 All
50364 int32 182 Busbar 1: voltage L1-L2 V *10 All
50366 int32 2520 Gen. real energy MWh *100 All
50368 int32 2522 Gen. positive reactive energy Mvarh *100 All
50370 int32 2568 Gen. hours of operation h *100 All
50372 int32 5542 Setpoint active power kW *10 All
50374 int32 5640 Setpoint voltage V *1 All
50376 int32 234 Average Busbar Wye-Voltage V *10 All
50378 int32 189 Busbar 1: voltage L2-L3 V *10 EG3500XT-P1

9 Appendix

Address
EG3500XT-P2
EG3500XT-P2
50384 int32 140 Total mains power W *1 All
50386 int32 150 Total mains reactive power var *1 All
50388 int32 173 Av. Mains Wye-Voltage V *10 All
50390 int32 174 Av. Mains Delta-Voltage V *10 All
50392 int32 207 Av. Mains Current A *1000 All
50394 int32 134 Mains current L1 A *1000 All
50400 int32 118 Mains voltage L1-L2 V *10 All
50406 int32 121 Mains voltage L1-N V *10 All
50412 int32 217 Reserve real power in system (valid if LDSS is kW *1 All
on)
50414 int32 218 Real power in system (vaild if LDSS is on) kW *1 All
50416 int32 219 Nominal real power in system (vaild if LDSS is kW *1 All
on)
Subtopic Active Diagnostic Trouble Code (DM1) 1-10 (All SPNs)
50424 int32 15400 SPN of 1. entry full 19 bits of All

SPN

SPN

SPN

SPN

SPN

9 Appendix
9.2.5 Protocol 5011 (Alarm Values Visualization)

Address

SPN

SPN

SPN

SPN

SPN
Subtopic Values
50444 uint32 15201 Total engine hours (j1939-HOURS) h *1 All
50446 uint32 2580 Period of use counter EG3500XT-P1
EG3500XT-P2
Topic LSx
50454 int32 267 Average LSx Delta Mains voltage L-L V *10 EG3500XT-P1
EG3500XT-P2
50456 int32 268 Average LSx Wye Mains voltage L-N V *10 EG3500XT-P1
EG3500XT-P2
50458 int32 269 Active power LSx W *1 EG3500XT-P1
EG3500XT-P2
50460 int32 270 Reactive power LSx var *1 EG3500XT-P1
EG3500XT-P2

Mux Byte
0 1-2 uint16 Protocol-ID, always 5011
Subtopic Generator
0 3-4 uint16 4161 BITLIST Alarms Generator active
Gen.overfreq. 1 Mask: 8000h All
Gen.underfreq. 1 Mask: 2000h All
Gen.overvolt. 1 Mask: 0800h All

9 Appendix

Mux Byte
Gen.undervolt. 1 Mask: 0200h All
Gen. overcurr. 1 Mask: 0080h All
Gen. Rv/Rd pow.1 Mask: 0010h All
Gen. Overload IOP 1 Mask: 0004h All
Busbar phase rotation mismatch Mask: 0001h EG3500XT-P2
0 5-6 uint16 10134 BITLIST Alarms Generator latched

(unacknowledged)
1 1-2 uint16 4163 BITLIST Alarms Generator 1 active (reserved)
Unbal. load 1 Mask: 8000h All
Gen. Asymmetry Mask: 2000h All
Ground fault 1 Mask: 1000h All
Gen. phase rot. misw. Mask: 0400h All
Gen act.pwr mismatch Mask: 0200h All
Gen. unloading fault Mask: 0100h All

9 Appendix

Mux Byte
Inv.time ov.curr. Mask: 0080h All
Operating range failed, Mask: 0040h All
Gen. Overload MOP 1 Mask: 0020h All
Gen.Power Factor lagging 1 Mask: 0008h All
Gen.Power Factor leading 1 Mask: 0002h All
1 3-4 uint16 10138 BITLIST Alarms Generator 1 latched

(unacknowledged)
1 5-6 uint16 10131 BITLIST Alarm classes latched

(unacknowledged)

9 Appendix

Mux Byte
Subtopic Mains
2 1-2 uint16 4188 BITLIST Alarms Mains active
Mains ov.freq. 1 Mask: 8000h All
Mains un.freq. 1 Mask: 2000h All
Mains ov.volt. 1 Mask: 0800h All
Mains un.volt. 1 Mask: 0200h All
Mains phaseshift Mask: 0080h All

(unacknowledged)

9 Appendix

Mux Byte
2 5-6 uint16 Internal
3 1-2 uint16 4187 BITLIST Alarms Mains 1 active
Mains import power 1 Mask: 8000h All
Mains export power 1 Mask: 2000h All
Mains overexcited 1 Mask: 0800h All
Mains underexcited 1 Mask: 0200h All
Mains df/dt Mask: 0080h All
Mns act.pwr mismatch Mask: 0040h All
Mains. Time dep. Voltage Mask: 0020h All
Mains slow voltage increase (10 min) Mask: 0008h All
Mains QV Monitoring step 1 Mask: 0002h All

(unacknowledged)
07.28 Mains Time-dep. Voltage (FRT) latched Mask: 0020h All

9 Appendix

Mux Byte
Subtopic Engine
4 1-2 uint16 4167 BITLIST Alarms 1 active
Overspeed 1 Mask: 8000h All
Underspeed 1 Mask: 2000h All
Unintended stop Mask: 0800h All
Speed det. Alarm Mask: 0400h All
Shutdwn malfunct. Mask: 0200h All
GCB fail to close Mask: 0100h All
GCB fail to open Mask: 0080h All
MCB fail to close Mask: 0040h All
MCB fail to open Mask: 0020h All
CAN-Fault J1939 Mask: 0010h All
Start fail Mask: 0008h All
Mainten. days exceeded Mask: 0004h All
Mainten. hours exceeded Mask: 0002h All
CANopen error at CAN Interface 1 Mask: 0001h All

9 Appendix

Mux Byte
GGB fail to close Mask: 8000h EG3500XT-P1
EG3500XT-P2
GGB fail to open Mask: 4000h EG3500XT-P1
EG3500XT-P2
Missing easYgen Mask: 2000h All
Missing LSx Mask: 1000h EG3500XT-P1
EG3500XT-P2
Cylinder temperature level 1 Mask: 0800h All
Cylinder temperature wire break Mask: 0200h All
Pole slip Mask: 0100h All
Syst.update LSx Mask: 0080h EG3500XT-P1
EG3500XT-P2
Syst.update easYgen Mask: 0040h All
Gen.AC Wiring Mask: 0020h All
Busbar1 AC Wiring Mask: 0010h EG3500XT-P1
EG3500XT-P2
GCB sync. Timeout Mask: 8000h All
MCB sync. Timeout Mask: 4000h All
GGB sync. Timeout Mask: 2000h EG3500XT-P1
EG3500XT-P2
Charge alt. low voltage (D+) Mask: 1000h All
Phase rotation mismatch Mask: 0800h All
CPU overload R1 trip Mask: 0400h All
MCB failure 50BF Mask: 0200h All
GCB failure 50BF Mask: 0100h All
ECU Protect alarm Mask: 0080h All
ECU Emission alarm Mask: 0040h All

9 Appendix

Mux Byte
Parameter Alignment Mask: 0010h All
MCB plausibility Mask: 0004h All
Red stop lamp DM1 Mask: 0002h All
Amber warning lamp DM1 Mask: 0001h All
08.32 GGB Timeout latched Mask: 2000h EG3500XT-P1
EG3500XT-P2
05.11 Charge alt. low voltage (D+) latched Mask: 1000h All
EG3500XT-P2
EG3500XT-P2
08.28 Missing LSx Mask: 1000h EG3500XT-P1
EG3500XT-P2
08.44 Syst.update LSx Mask: 0080h EG3500XT-P1

9 Appendix

Mux Byte
EG3500XT-P2
EG3500XT-P2
Subtopic GAP Alarms
6 1-2 uint16 5197 BITLIST Alarms GAP active
LS interf.redundancy Mask: 8000h EG3500XT-P1
EG3500XT-P2
Max. starts per time Mask: 0200h K36
Neutral contactor failure Mask: 0100h All
Decoupling GCB<->MCB Mask: 0080h All
Meas.difference 4105 VDE-AR-N 4105 Mask: 0040h All
Parameter alignment VDE-AR-N 4105 Mask: 0020h All
Missing member VDE-AR-N 4105 Mask: 0010h All
Busbar monitoring Mask: 0008h All
Plausibility GCB feedback Mask: 0004h MARINE
Reactive load sharing mismatch Mask: 0002h All
Active load sharing mismatch Mask: 0001h All
6 3-4 uint16 10286 BITLIST Alarms GAP latched

(unacknowledged)
08.53 LS interf.redundancy latched Mask: 8000h EG3500XT-P1
EG3500XT-P2

9 Appendix

Mux Byte

latched
17.07 Meas.difference 4105 VDE-AR-N 4105 Mask: 0040h All

latched
17.06 Parameter alignment VDE-AR-N 4105 Mask: 0020h All

latched

latched
7 1-2 uint16 4175 BITLIST Alarms Flexible thresholds 1-16 active
Alarm flexible limit 16 Mask: 8000h All
7 3-4 uint16 10279 BITLIST Alarms Flexible thresholds 1-16

latched (unacknowledged)

9 Appendix

Mux Byte

active


9 Appendix

Mux Byte

active


9 Appendix

Mux Byte
9 5-6 uint16 0 (reserve)
10 1-2 uint16 4194 BITLIST Free Alarms active
Free alarm 4 (same as Mux 6) Mask: 0008h All
10 3-4 uint16 10282 BITLIST Free Alarms latched

(unacknowledged)

9 Appendix

Mux Byte
16.04 Free alarm 4 latched (same as Mux 6) Mask: 0008h All
Subtopic Internal DC Analogue Values Wirebreak
11 1-2 uint16 4171 BITLIST Alarms Analog Inputs 1 active
Failure Charging Alternator (D+) Mask: 0010h All
Battery over voltage 2 Mask: 0008h All
Battery under voltage 2 Mask: 0004h All
11 3-4 uint16 10136 Alarms Analog Inputs 1 latched

(unacknowledged)

9 Appendix

Mux Byte
12 1-2 uint16 4173 Alarms Analog Inputs Wire Break active
Analog inp. 1, wire break Mask: 0002h All
Analog inp. 4, wire break or shortcut Mask: 0010h EG3500XT-P2
12 3-4 uint16 10137 Alarms Analog Inputs Wire Break latched

(unacknowledged)

9 Appendix

Mux Byte
Subtopic Internal Digital Inputs
13 1-2 uint16 4181 Alarms Digital Inputs 1 active
Discrete input 1 Mask: 8000h All
13 3-4 uint16 10132 Alarms Digital Inputs 1 latched

(unacknowledged)

9 Appendix

Mux Byte
14 1-2 uint16 4183 AlarmsDigital Inputs 2 active
Digital Input 13 Mask: 8000h EG3500XT-P2

(unacknowledged)

9 Appendix

Mux Byte
Subtopic External Digital Inputs
15 1-2 uint16 4185 Alarms External Digital Inputs active
external Digital Input 16 Mask: 8000h All
15 3-4 uint16 16377 Alarms External Digital Inputs latched

(unacknowledged)

9 Appendix

Mux Byte
16 1-2 uint16 4195 Alarm External Digital Inputs 1 active
16 3-4 uint16 10284 Alarm External Digital Inputs 1 latched

(unacknowledged)
Subtopic External DC Analogue Values Wirebreak

9 Appendix

Mux Byte
17 1-2 uint16 4196 Alarms External Analog Inputs Wire Break

active
Ext. analog inp. 1, wire break Mask: 0001h All


9 Appendix
9.2.6 Protocol 5014 (Based on Protocol 5003 but with enhancements)

Address Mux Byte
50000 0 1-2 int16 Protocoll-ID, always 5014 All
50001 0 3-4 int16 10100 Engine speed rpm *1.0 All
Control mode (STOP/AUTO/MANUAL/ Mask: 000Fh All

TEST)
50003 1 1-2 int16 160 Gen. Powerfactor *1000 All
50004 1 3-6 int32 170 Average Gen. Wye-Voltage V *10 All
50006 2 1-2 int16 144 Gen. Frequency Hz *100 All
50007 2 3-6 int32 171 Average Gen. Delta-Voltage V *10 All
50009 3 1-2 int16 147 Mains frequency Hz *100 All
50010 3 3-6 int32 173 Average Mains Wye-Voltage V *10 All
50012 4 1-2 int16 208 Mains power factor *1000 All
50013 4 3-6 int32 174 Average Mains Delta-Voltage V *10 All
50015 5 1-2 int16 209 Busbar Frequency Hz *100 All
50016 5 3-6 int32 216 Average Busbar Delta-Voltage V *10 All
50018 6 1-2 uint16 4085 BITLIST
96.01 Internal Flag 1 Mask: 0001h All

9 Appendix

Address Mux Byte
50019 6 3-6 int32 234 Average Busbar Wye-Voltage V *10 EG3500XT-

P2
50021 7 1-2 int16 10110 Battery voltage V *10 All
50022 7 3-6 int32 207 Av. Mains Current A *1000 All
50025 8 3-6 int32 185 Av. Gen. Current A *1000 All
50028 9 3-6 int32 161 Meas. ground current A *1000 All
50031 10 3-6 int32 159 Calculated ground current A *1000 All

P2

P2

P2

P2
50043 14 3-6 int32 134 Mains current L1 A *1000 All

P2
50046 15 3-6 int32 231 Busbar Voltage L1-N V *1000 EG3500XT-

P2

P2
50049 16 3-6 int32 232 Busbar Voltage L2-N V *1000 EG3500XT-

P2

P2
50052 17 3-6 int32 135 Total Generator power W *1 All
50054 18 1-2 Internal
50055 18 3-6 int32 140 External total mains power W *1 All
50057 19 1-2 int16 4086 BITLIST All
Operating Range Monitoring Code Mask FF00h All

Number
Operating range Error-Code ("0" means

no failure)
The current segment number Mask 00FFh All
(One of 64 Segments possible)

9 Appendix

Address Mux Byte
50058 19 3-6 int32 136 Total Generator reactive power var *1 All
50060 20 1-2 int16 10159 AI Auxiliary excitation D+ V *10 All
50061 20 3-6 int32 150 External total mains reactive power var *1 All
50063 21 1-2 int16 10133 BITLIST
08.18 LM CANopen error at CAN Mask: 0001h All

Interface 1
05.10 LM Maintenance hours exceeded Mask: 0002h All

latched
05.09 LM Maintenance days exceeded Mask: 0004h All

latched
05.08 LM Start fail detected latched Mask: 0008h All
08.10 LM General CAN-J1939 fault Mask: 0010h All

latched
08.08 LM MCB fail to open latched Mask: 0020h All
08.07 LM MCB fail to close latched Mask: 0040h All
08.06 LM GCB fail to open latched Mask: 0080h All
08.05 LM GCB fail to close latched Mask: 0100h All
05.06 LM Shutdown malfunction Mask: 0200h All

detected latched
05.07 LM Speed detection alarm latched Mask: 0400h All
05.05 LM Unintended stop detected Mask: 0800h All

latched
50064 21 3-6 int32 182 Busbar: Voltage L1-L2 V *1 All
50066 22 1-2 int16 4087 BITLIST
08.30 Timeout Synchronisation GCB Mask: 8000h All

latched
08.31 Timeout Synchronisation MCB Mask: 4000h All

latched
08.32 Timeout Synchronisation GGB Mask: 2000h EG3500XT-

latched P1
EG3500XT-
P2
05.11 Charge fail (D+ functionality) Mask: 1000h All

latched
Operating range failure 12 Mask: 0800h All
08.47 MCB failure 50BF Mask: 0100h

9 Appendix

Address Mux Byte
08.29 CANopen error at CAN Interface 3 Mask: 0040h EG3500XT-

P1
EG3500XT-
P2
05.14 ECU yellow (amber) lamp alarm Mask: 0001h All

latched
50067 22 3-6 int32 189 Busbar: Voltage L2-L3 V *1 EG3500XT-

P2
50069 23 1-2 int16 10286 BITLIST
08.53 LS interf.redundancy latched Mask: 8000h EG3500XT-

P1
EG3500XT-
P2
Free alarm 4 Mask: 2000h EG3000
17.09 Neutral interl. reply mismatch Mask: 0100h All

latched
17.07 Measurement difference 4105 Mask: 0040h All

latched
17.06 Parameter alignment 4105 Mask: 0020h All

latched
17.02 Reactive load share mismatch Mask: 0002h All

latched
17.01 Active load share mismatch Mask: 0001h All

latched
50070 23 3-6 int32 193 Busbar: Voltage L3-L1 V *1 EG3500XT-

P2
50072 24 1-2 int16 10134 BITLIST

9 Appendix

Address Mux Byte

latched

latched

latched

latched

latched

latched

latched

latched
06.34 Busbar phase rotation mismatch Mask: 0001h EG3500XT-

P2
50073 24 3-6 int32 108 Gen. voltage L1-L2 V *1
50075 25 1-2 int16 10138 BITLIST

latched

latched
06.18 Generator voltage asymmetry Mask: 2000h All

latched
06.21 Gen. Phase Rotation mismatch Mask: 0400h All

Latched
06.29 Gen. active power mismatch Mask: 0200h All

Latched
06.30 Generator unloading mismatch Mask: 0100h All

Latched

latched

9 Appendix

Address Mux Byte

latched

latched

latched

latched

latched
50078 26 1-2 int16 10135 BITLIST
07.05 Mains Phase rotation mismatch Mask: 0004h All

latched
50081 27 1-2 int16 10278 BITLIST

9 Appendix

Address Mux Byte
07.16 Mains active power mismatch Mask: 0040h All

latched
07.28 Mains Time-dep. Voltage (FRT) Mask: 0020h All

latched
07.27 Mains slow voltage increase (10 Mask: 0008h All

min)
50084 28 1-2 int16 10132 BITLIST
50085 28 3-6 int32 110 Gen. voltage L3-L1 V *1 EG3000
50087 29 1-2 int16 10283 BITLIST

P2

P2

P2

P2

P2

P2

9 Appendix

Address Mux Byte

P2

P2

P2

P2

P2
50090 30 1-2 int16 16377 BITLIST
50093 31 1-2 int16 10279 BITLIST

9 Appendix

Address Mux Byte
50096 32 1-2 int16 10280 BITLIST
50099 33 1-2 int16 10281 BITLIST

9 Appendix

Address Mux Byte
50102 34 1-2 int16 4088 BITLIST
50105 35 1-2 int16 4089 BITLIST

9 Appendix

Address Mux Byte
50108 36 1-2 int16 10137 BITLIST

P2

P2

P2

P2

P2

P2

P2
50109 36 3-4 int16 15310 SPN 2629 Turbo Charger 1 temp °C *1 All
50110 36 5-6 int16 10285 BITLIST

9 Appendix

Address Mux Byte
50111 37 1-2 int16 10107 BITLIST
50112 37 3-4 int16 10109 BITLIST

P2

P2

P2

P2

P2

9 Appendix

Address Mux Byte

P2

P2

P2

P2

P2

P2

P2
50113 37 5-6 int16 8005 BITLIST

P2

P2

9 Appendix

Address Mux Byte

P2

P2
50120 40 1-2 int16 10202 Status message. This is an index All

number. Refer to manual chapter State
messages for more information.
50121 40 3-6 uint32 2520 Gen. real energy MWh *100 All
50123 41 1-2 uint16 2540 Engine, number of start requests *1 All
50124 41 3-6 uint32 2522 Gen. positive reactive energy Mvarh *100 All
50126 42 1-2 int16 2558 Hours until next maintenance h *10 All
50127 42 3-6 uint32 2568 Gen. hours of operation h *100 All
50129 43 1-2 int16 5541 Setpoint frequency Hz *100 All
50130 43 3-6 int32 5542 Setpoint active power kW *10 All
50132 44 1-4 int32 5640 Setpoint voltage V *1 All
50134 44 5-6 int16 5641 Setpoint power factor *1000 All
50135 45 1-2 int16 4090 BITLIST
Idle mode OR Ramp to rated Mask: 8000h All
03.31 Auxiliary services postrun is Mask: 0002h All

active
50136 45 3-4 int16 4091 BITLIST
03.28 Operating Magnet / Gasrelay is Mask: 4000h All

active

9 Appendix

Address Mux Byte
04.09 Emergency mode is currently Mask: 0800h All

active

Command

Command

Command

Command
03.24 Excitation AVR (Run-up Mask: 0010h All

Synchronization)

Command

Command
50137 45 5-6 int16 4155 BITLIST
03.21 3-Pos. Controller Freq./Power Mask: 4000h All

lower

raise

lower

active

active
50138 46 1-2 int16 4156 BITLIST

9 Appendix

Address Mux Byte
04.16 GGB is closed Mask: 8000h EG3500XT-

P1
EG3500XT-
P2
04.17 GGB is released Mask: 4000h EG3500XT-

P1
EG3500XT-
P2
04.24 Synchronisation GGB procedure is Mask: 2000h EG3500XT-

active P1
EG3500XT-
P2
04.25 Open command GGB is active Mask: 1000h EG3500XT-

P1
EG3500XT-
P2
04.26 Close command GGB is active Mask: 0800h EG3500XT-

P1
EG3500XT-
P2
Dead busbar closure requ. for GCB,MCB Mask: 0400h All

or GGB
Generator with a closed GCB is Mask: 0080h All

requested
AUTOMATIC Run: Switch to Operating Mask: 0001h All

Mode STOP
50139 46 3-4 int16 4092 BITLIST

9 Appendix

Address Mux Byte
50140 46 5-6 int16 10284 BITLIST
50141 47 1-2 int16 8009 BITLIST

9 Appendix

Address Mux Byte
50162 54 1-2 Internal
50163 54 3-6 uint32 2580 Period of use counter h *100 All
50165 55 1-2 int16 4093 BITLIST
08.34 GGB fail to close latched Mask: 8000h EG3500XT-

P1
EG3500XT-
P2
08.35 GGB fail to open latched Mask: 4000h EG3500XT-

P1
EG3500XT-
P2
08.27 Missing EG3000 Mask: 2000h All

9 Appendix

Address Mux Byte
08.28 Missing LS5 Mask: 1000h EG3500XT-

P1
EG3500XT-
P2
08.44 Syst.update LS5 Mask: 0080h EG3500XT-

P1
EG3500XT-
P2
06.33 Busbar1 AC Wiring Mask: 0010h EG3500XT-

P1
EG3500XT-
P2
Load share diagnostic: Own Unit is Mask: 0001h All

suspected
50166 55 3-6 uint32 219 Nominal active power in system (in own *1 All
segment)
50168 56 1-2 int16 4157 BITLIST
28.01 Command 1 to LS5 (OR) Mask: 8000h EG3500XT-

P1
EG3500XT-
P2

P1
EG3500XT-
P2

P1
EG3500XT-
P2

P1
EG3500XT-
P2

P1

9 Appendix

Address Mux Byte
EG3500XT-
P2

P1
EG3500XT-
P2
Gen excitation limit active Mask: 0200h EG3500XT-

P1
EG3500XT-
P2
05.17 Uprating active Mask: 0080h
50169 56 3-6 int32 218 Active real power in system (in own kW *1 All
segment)
50171 57 1-2 Internal
50172 57 3-6 int32 217 Active power reserve in system (in own kW *1 All
segment)
50174 58 1-2 Internal
50175 58 3-4 int16 239 System actual nominal power % *100 All
50176 58 5-6 int16 240 System total real power % *100 All
50177 59 1-2 Internal
50178 59 3-4 int16 241 System reserve active power % *100 All
50179 59 5-6 int16 15311 Engine Derate Request % *1 All
50180 60 1-2 Internal
50181 60 3-4 Internal
50182 60 5-6 Internal
50183 61 1-2 int16 2556 Days until next maintenance d *1 All
50184 61 3-6 int32 233 Busbar: Voltage L3-N V *1 EG3500XT-

P1
EG3500XT-
P2
50186 62 1-2 int16 4094 BITLIST
02.03 Generator voltage in range Mask: 8000h All
02.06 Busbar voltage in range Mask: 4000h All

9 Appendix

Address Mux Byte
02.11 Mains voltage and frequency in Mask: 2000h All

range
02.21 Busbar is dead Mask: 1000h All
86.27 LM External mains decoupling Mask: 0800h All
87.70 LM Release engine monitoring Mask: 0400h All
87.72 LM Disable mains monitoring Mask: 0200h All
87.73 LM Mains decoupling MCB Mask: 0100h All
87.74 LM Inhibit dead bus GCB Mask: 0080h All
XX.XX LDSS IOP Reserve power 3 ready Mask: 0020h
XX.XX LDSS IOP Reserve power 4 ready Mask: 0010h
XX.XX LDSS MOP Reserve power 3 ready Mask: 0004h
XX.XX LDSS MOP Reserve power 4 ready Mask: 0002h
02.45 Mains release breaker Mask: 0001h All
50187 62 3-6 int32 5642 Setpoint reactive power kvar *10 All
50189 63 1-2 int16 4095 BITLIST
96.32 LM Internal Flag 32 Mask: 8000h All
Internal Mask: F000h
Engine state number: Mask: 0F00h All
0,1 : internal

9 Appendix

Address Mux Byte
2: Off
3: Preglow
4: Crank
5: Run
6: Cool down
7: Spin down
8: Start pause
9: Idle
10: Run-up synchr. mode active
11: Run-up synchr. Wait on excitation
Reactive load control state number: Mask: 00F0h All
2: Static
3: Isochronous
4: Reactive load control
0, 1, 5, 6, 7, 8, 9, 10, 11, … : internal
Real load control state number: Mask: 000Fh All
2: Static
3: Isochronous
4: Base load control
5: Export/import control
0, 1, 6, 7, 8, 9, 10, 11, … : internal
50191 63 5-6 int16 9642 Free AnalogManager Value 1 All
50205 68 3-6 int32 9698 Free AnalogManager Value 15 (long) All
50207 69 1-2 Internal

9 Appendix

Address Mux Byte
50208 69 3-6 int32 9702 Free AnalogManager Value 16 (long) All
50210 70 1-2 int16 8908 81.29 Engine Coolant Temperature °C 1 All

[°C] (HMI)
°F
8910
[°F]
50211 70 3-4 int16 8904 81.25 Engine Oil Pressure (HMI) bar *1 bar All
[0.1bar]
psi 1 psi
8909
[psi]
50212 70 5-6 int16 4096 BITLIST
Monitored Number of easYgen Mask: FF00h All

communicating
Number of easYgens currently Mask: 00FFh All

communicating
50213 71 1-2 int16 4097 BITLIST
Monitored Number of LS5 Mask: FF00h EG3500XT-

communicating P1
EG3500XT-
P2
Number of LS5 currently communicating Mask: 00FFh EG3500XT-

P1
EG3500XT-
P2
50214 71 3-4 int16 4098 BITLIST
Device number of missing LSx (33-48) Mask FFFFh EG3500XT-

P1
EG3500XT-
P2
LSx Device Nr. 48 Mask 8000h

9 Appendix

Address Mux Byte
50215 71 5-6 int16 4099 BITLIST
Device number of missing LSx (49-64) Mask FFFFh EG3500XT-

P1
EG3500XT-
P2
50216 72 1-2 int16 10282 BITLIST

9 Appendix

Address Mux Byte
50217 72 3-4 int16 10313 BITLIST
07.33 FRT Time-dep. voltage 3 Mask: 0800h All
07.31 FRT Time-dep. voltage 2 Mask: 0100h All
08.40 CAN J1939 device 3 timeout Mask: 0010h All
08.37 CAN J1939 ECU timeout Mask: 0002h All
08.29 CANopen error interface 3 Mask: 0001h All
50219 73 1-4 int32 2526 Generator negative reactive energy Mvarh *100 All
50222 74 1-4 int32 05.70 Active power set point ramped kW *1 All
50225 75 1-4 int32 05.92 Reactive power set point ramped kvar *1 All
75 Mux x 20ms = 1.5s refresh rate

Address
50000 int16 Protocoll-ID, always 5016
50001 int16 3181 Skaling Power (16 bits) Exponent 10x W All
(5;4;3;2)
50002 int16 3182 Skaling Volts (16 bits) Exponent 10x V All
(2;1;0;-1)
50003 int16 3183 Skaling Amps (16 bits) Exponent 10x A (0;-1) All
50004 Internal

9 Appendix

Address
50005 Internal
50006 Internal
50007 Internal
50008 int16 283 Busbar Voltage L3-N V format EG3500XT-P2

defined by
index 3182
(Modbus-
Address
50002)
50009 int16 144 Generator frequency Hz *100 All
50010 int16 246 Total generator power W format All

defined by
index 3181
(Modbus-
Address
50001)
50011 int16 247 Total generator reactive power var format All
defined by
index 3181
(Modbus-
Address
50001)
50012 int16 160 Generator power factor *1000 All

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-

9 Appendix

Address
Address
50002)
50019 int16 255 Generator current L1 A format All

defined by
index 3183
(Modbus-
Address
50003)

defined by
index 3183
(Modbus-
Address
50003)

defined by
index 3183
(Modbus-
Address
50003)
50022 int16 209 Busbar Frequency Hz *100 All
50023 int16 254 Busbar Voltage L1-L2 V format All

defined by
index 3182
(Modbus-
Address
50002)
50024 int16 279 Busbar Voltage L2-L3 V format EG3500XT-P2

defined by
index 3182
(Modbus-
Address
50002)
50025 int16 280 Busbar Voltage L3-L1 V format EG3500XT-P2

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)
50028 int16 5541 Setpoint frequency Hz *100 All
50029 int16 5641 Setpoint power factor (cosphi) *1000 All
50030 int16 147 Mains frequency Hz *100 All
50031 int16 258 Total mains active power W format All

defined by
index 3181
(Modbus-

9 Appendix

Address
Address
50001)
50032 int16 259 Total mains reactive power var format All
defined by
index 3181
(Modbus-
Address
50001)
50033 int16 208 Mains power factor *1000 All

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)

defined by
index 3182
(Modbus-
Address
50002)
50040 int16 266 Mains current L1 A format All

defined by
index 3183
(Modbus-
Address
50003)
50041 0 (prepared mains current L2) A
50042 0 (prepared mains current L3) A
50043 int16 267 Average LSx Delta Mains voltage L-L V format EG3500XT-P1
defined by
(Modbus-
Address
50002)

9 Appendix

Address
50044 int16 268 Average LSx Wye Mains voltage L-N V format EG3500XT-P1
defined by
(Modbus-
Address
50002)
50045 int16 239 Nominal real power in system % *100 All
50046 int16 240 Real power in system % *100 All
50047 int16 241 Reserve real power in system % *100 All
50048 int16 269 Active power LSx W format EG3500XT-P1

defined by
(Modbus-
Address
50001)
50049 int16 270 Reactive power LSx var format EG3500XT-P1

defined by
(Modbus-
Address
50001)
50050 int16 4608 Average LSx Mains delta frequency L-L Hz *100 EG3500XT-P1
EG3500XT-P2
Topic DC Analogue Values (Engine Values)
50051 int16 10100 Engine Pickup speed rpm *1 All
50052 int16 10110 Battery voltage V *10 All
50053 int16 10159 AI Auxiliary excitation D+ V *10 All
50054 uint16 2540 Engine, number of start requests *1 All
50055 int16 2558 Hours until next maintenance h *1 All

9 Appendix

Address
50094 int16 2556 Days until next maintenance days *1 All
50095 Internal
50096 int16 Engine Coolant Temperature °C *1 All
(HMI Analogmanager 8901) °F
50097 int16 Engine Oil Pressure bar *10 bar All
(HMI Analogmanager 8893) psi *1 psi
50098 Internal
Topic Control and Status
Control mode (STOP/AUTO/MANUAL/TEST) Mask: 000Fh All

9 Appendix

Address
50100 int16 10202 Status message. This is an index number. All

Refer to manual chapter State messages for
more information.
50101 Internal
50102 uint16 4153 BITLIST ControlBits1
03.24 Excitation AVR (Run-up Synchronization) Mask: 0010h EG3500XT-P1
EG3500XT-P2

9 Appendix

Address
04.18 Synchronisation GCB procedure is active Mask: 0100h All
04.21 Synchronisation MCB procedure is active Mask: 0020h All
EG3500XT-P2
EG3500XT-P2
04.24 Synchronisation GGB procedure is active Mask: 2000h EG3500XT-P1
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2

GGB

9 Appendix

Address

STOP
50107 uint16 4084 BITLIST ControlBits 21
02.03 Generator voltage in range Mask: 8000h All
02.06 Busbar voltage in range Mask: 4000h All
02.11 Mains voltage and frequency in range Mask: 2000h All
02.21 Busbar is dead Mask: 1000h All
86.27 LM Mains failure by external device Mask: 0800h All
87.70 LM Release engine monitoring Mask: 0400h All
87.72 LM Disable mains monitoring Mask: 0200h All
87.73 LM Mains decoupling MCB Mask: 0100h All
87.74 LM Inhibit dead bus GCB Mask: 0080h All
Load share diagnostic: Own Unit is suspected Mask: 0040h All
02.45 Mains release breaker Mask: 0020h All

9 Appendix

Address
Topic Discrete Outputs
50108 uint16 10107 BITLIST Relay Outputs 1

9 Appendix

Address

9 Appendix

Address
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2
Topic Alarm Management
Subtopic General
50114 uint16 10131 BITLIST Alarm General

9 Appendix

Address
50115 uint16 10149 BITLIST Alarms 2 latched (unacknowledged)
EG3500XT-P2
50116 uint16 4169 BITLIST Alarms 2 active
Timeout Synchronisation GCB Mask: 8000h All
Timeout Synchronisation MCB Mask: 4000h All
Timeout Synchronisation GGB Mask: 2000h EG3500XT-P1
EG3500XT-P2
Charge fail (D+ functionality) Mask: 1000h All
Gen/Busbar/Mains phase rotat. Mask: 0800h EG3500XT-P1
EG3500XT-P2

9 Appendix

Address
Parameter Alignment LDSS Mask: 0010h All
Missing members Mask: 0008h All
ECU red lamp alarm Mask: 0002h All
ECU yellow (amber) lamp alarm Mask: 0001h All
EG3500XT-P2
EG3500XT-P2
08.28 Missing LS5 Mask: 1000h EG3500XT-P1
EG3500XT-P2
08.44 Syst.update LS5 Mask: 0080h EG3500XT-P1
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2
EG3500XT-P2

9 Appendix

Address
Missing LS5 Mask: 1000h EG3500XT-P1
EG3500XT-P2
Temperature deviation level 1 Mask: 0800h All
Temperature deviation level 2 Mask: 0400h All
Temperature deviation wire break Mask: 0200h All
Pole slip Mask: 0100h
Syst.update LS5 Mask: 0080h EG3500XT-P1
EG3500XT-P2
EG3500XT-P2
Operating Range Monitoring Code Number Mask: FF00h All
The current segment number Mask: 00FFh All
Subtopic Engine

9 Appendix

Address
Engine Over speed 1 Mask: 8000h All
Engine Over speed 2 Mask: 4000h All
Engine under speed 1 Mask: 2000h All
Engine under speed 2 Mask: 1000h All
Unintended stop detected Mask: 0800h All
Speed detection alarm Mask: 0400h All
Shutdown malfunction detected Mask: 0200h All
General CAN-J1939 fault Mask: 0010h All
Start fail detected Mask: 0008h All
Maintenance days exceeded Mask: 0004h All
Maintenance hours exceeded Mask: 0002h All
50122 uint16 10136 BITLIST Alarms AI 1 latched (unacknowledged)
50123 uint16 4171 BITLIST Alarms Analog Inputs 1 active

9 Appendix

Address
Subtopic Generator
50126 uint16 10134 BITLIST Alarms Gen latched (unacknowledged)
06.34 Busbar phase rotation mismatch latched Mask: 0001h EG3500XT-P2
50127 uint16 4161 BITLIST Alarms Generator active
Generator over frequency 1 Mask: 8000h All

9 Appendix

Address
Generator over frequency 2 Mask: 4000h All
Generator under frequency 1 Mask: 2000h All
Generator under frequency 2 Mask: 1000h All
Generator over voltage 1 Mask: 0800h All
Generator over voltage 2 Mask: 0400h All
Generator under voltage 1 Mask: 0200h All
Generator under voltage 2 Mask: 0100h All
Generator over current 1 Mask: 0080h All
Reverse / reduced power 1 Mask: 0010h All
Reverse / reduced power 2 Mask: 0008h All
Generator overload IOP 1 Mask: 0004h All
Generator overload IOP 2 Mask: 0002h All
Busbar phase rotation mismatch Mask: 0001h
50128 uint16 10138 BITLIST Alarms Gen 1 latched

(unacknowledged)
50129 uint16 4163 BITLIST Alarms Generator 1 active
Generator unbalanced load 1 Mask: 8000h All
Generator unbalanced load 2 Mask: 4000h All
Generator voltage asymmetry Mask: 2000h All

9 Appendix

Address
Gen. Phase Rotation mismatch Mask: 0400h All
Gen. active power mismatch Mask: 0200h All
Generator unloading mismatch Mask: 0100h All
Inverse time over current Mask: 0080h All
Operating Range failed Mask: 0040h All
Generator overload MOP 1 Mask: 0020h All
Generator overload MOP 2 Mask: 0010h All
Subtopic Mains
50132 uint16 10135 BITLIST Alarms Mains latched

(unacknowledged)
50133 uint16 4188 BITLIST Alarms Mains active

9 Appendix

Address
Mains Phase shift Mask: 0080h All
50134 uint16 10278 BITLIST Alarms Mains 1 latched

(unacknowledged)
50135 uint16 4187 BITLIST Alarms Mains 1 active
Mains PF lagging 1 Mask: 0800h All
Mains PF lagging 2 Mask: 0400h All
Mains PF leading 1 Mask: 0200h All

9 Appendix

Address
Mains PF leading 2 Mask: 0100h All
Mains active power mismatch Mask: 0040h All
Mains Time-dep. Voltage 1 (FRT) Mask: 0020h All
QV Monitoring 1 tripped Mask: 0002h All
QV Monitoring 2 tripped Mask: 0001h All
Internal Mask: F000h
Engine state Mask: 0F00h All
2: Off
3: Preglow
4: Crank
5: Run
6: Cool down
7: Spin down
8: Start pause
9: Idle
10: Run-up synchr. mode active
11: Run-up synchr. wait on excitation
0, 1 12, 13… : internal
Reactive load control state Mask: 00F0h All
2: Static
3: Isochronous
4: Reactive load control
0, 1, 5, 6, 7, 8, 9, 11, … : internal
Real load control state Mask: 000Fh All
2: Static
3: Isochronous
4: Base load control
5: Export/import control
0, 1, 6, 7, 8, 9, 10, 11, … : internal
50137 Internal
Subtopic Digital Inputs

9 Appendix

Address
50138 uint16 10132 BITLIST Alarms DI 1 latched (unacknowledged)
50139 uint16 4181 BITLIST Alarms DI 1 active
50140 uint16 16377 BITLIST Alarms Ext. DI 1 latched

(unacknowledged)

9 Appendix

Address
50141 uint16 4185 BITLIST Alarms Ext. DI 1 active
External discrete input 16 Mask: 8000h All
50142 uint16 10284 BITLIST Alarm Ext. DI 2 latched

(unacknowledged)

9 Appendix

Address
50143 uint16 4195 BITLIST Alarm Ext. DI 2 active
50144 uint16 10283 BITLIST Alarms DI 2 latched (unacknowledged)

9 Appendix

Address
50145 uint16 4183 BITLIST Alarms DI 2 active
Discrete input 13 Mask: 8000h EG3500XT-P2
50150 uint16 10279 BITLIST Alarms Flex.Thresholds 1-16 latched

9 Appendix

Address
50151 uint16 4175 BITLIST Alarms Flex.Thresholds 1-16 active
Flexible limit 16 Mask: 8000h All

9 Appendix

Address

9 Appendix

Address
50156 Internal
50157 Internal
50158 Internal
Subtopic DC Analogue Values Wirebreak
50159 uint16 10137 BITLIST Alarms AI Wire Break latched

9 Appendix

Address
50160 uint16 4173 BITLIST Alarms AI Wire Break active
Analog input 1 wire break Mask: 0002h All
Analog input 4 wire break Mask: 0010h EG3500XT-P2
50161 uint16 10285 BITLIST Alarms Ext.AI Wire Break latched

9 Appendix

Address
50162 uint16 4196 BITLIST Alarms Ext.AI Wire Break active
Ext. analog input 1 wire break Mask: 0001h All
50163 Internal
50164 Internal
Subtopic Other Alarms
50165 uint16 10286 BITLIST Other Alarms 1 latched

(unacknowledged)
08.53 LS interface redundancy latched Mask: 8000h EG3500XT-P1
EG3500XT-P2
17.09 Neutral interl. reply mismatch latched Mask: 0100h All
17.07 Measurement difference 4105 latched Mask: 0040h All
17.06 Parameter alignment 4105 latched Mask: 0020h All

9 Appendix

Address
50166 uint16 5197 BITLIST Other Alarms 1 active
LS interface redundancy active Mask: 8000h EG3500XT-P1
EG3500XT-P2
Free alarm 4 active Mask: 2000h All
Neutral contactor failure active Mask: 0100h All
Decoupling GCB-MCB active Mask: 0080h All
Meas.difference 4105 VDE-AR-N 4105 active Mask: 0040h All
Parameter alignment VDE-AR-N 4105 active Mask: 0020h All
Missing member VDE-AR-N 4105 active Mask: 0010h All
Busbar monitoring latched active Mask: 0008h All
Reactive load sharing mismatch latched Mask: 0002h All
Active load sharing mismatch latched Mask: 0001h All
50167 uint16 4085 BITLIST Internal Flags 1-16

9 Appendix

Address
50168 uint16 4095 BITLIST Internal Flags 17-32
50169 uint16 10282 BITLIST Free Alarms 1 latched

(unacknowledged)
50170 uint16 4194 BITLIST Free Alarms 1 active

9 Appendix

Address
Subtopic Active Diagnostic Trouble Code (DM1) 1-10 (SPN Range 0…65535)full SPN value at 450425-450444

19 bits of SPN

19 bits of SPN

19 bits of SPN

19 bits of SPN

9 Appendix

Address

19 bits of SPN

19 bits of SPN

19 bits of SPN
FMI Mask FF00h All

19 bits of SPN
FMI Mask FF00h All

19 bits of SPN

19 bits of SPN

9 Appendix

Address
50191 uint16 15395 BITLIST J1939 Lamp Status DM1
Internal Mask 8000h
Internal Mask 4000h
Internal Mask 0800h
Internal Mask 0400h
Internal Mask 0080h
Internal Mask 0040h
Internal Mask 0008h
Internal Mask 0004h
50192 uint16 15445 BITLIST J1939 Lamp Status DM2
Internal Mask 8000h
Internal Mask 4000h
Internal Mask 0800h
Internal Mask 0400h
Internal Mask 0080h
Internal Mask 0040h
Internal Mask 0008h
Internal Mask 0004h
Subtopic Especially Failure Codes
50193 int16 15109 J1939 MTU ADEC ECU Failure Codes *1 All

9 Appendix

Address
50195 uint16 15304 J1939 EMR Engine Stop Information All
"Type 9" Value="9"
"Type 8" Value="8"
"Type 7" Value="7"
"Type 6" Value="6"
"Type 5" Value="5"
"Type 4" Value="4"
"Type 3" Value="3"
"Type 2" Value="2"
"Type 1" Value="1"
"Type 0" Value="0"
50197 uint16 15305 BITLIST J1939 DLN2-Message Scania S6
Engine Coolant Temperature Mask F000h
Engine Oil Pressure Mask 0F00h
High Engine Oil Level Mask 00F0h
Low Engine Oil Level Mask 000Fh

9 Appendix

Address
50198 Internal
50199 Internal
50200 Internal
Subtopic Values
50201 int16 15308 Engine Speed (SPN 190) rpm *1 All
50202 int16 15202 Engine Coolant Temperature (SPN 110) °C *1 All
50203 int16 15203 Fuel temperature (SPN 174) °C *1 All
50204 int16 15309 Engine Oil Temperature 1 (SPN 175) °C *10 All
50205 int16 15205 Engine Oil Pressure (SPN 100) kPa *1 All
50206 int16 15307 Fuel Rate (SPN 183) L/h *10 All
50207 int16 15206 Coolant Level (SPN 111) % *10 All
50208 int16 15207 Throttle position (SPN 91) % *10 All
50209 int16 15208 Load at current Speed (SPN 92) % *1 All
50210 int16 15210 Engine oil level (SPN 98) % *10 All
50211 int16 15214 Boost pressure (SPN 102) kPa *1 All
50212 int16 15215 Intake Manifold 1 Temp (SPN 105) °C *1 All
50213 int16 15212 Barometric Pressure (SPN 108) kPa *10 All
50214 int16 15213 Air inlet temperature (SPN 172) °C *1 All
50216 int16 15299 Exhaust Gas Temp.(SPN 173) °C *10 All
50217 int16 15217 Engine Intercooler Temp (SPN52) °C *1 All
50218 int16 15218 Fuel Delivery Pressure (SPN94) kPa *1 All
50220 int16 15220 Crankcase Pressure (SPN101) kPa *1 All
50221 int16 15221 Turbo Air Inlet Pressure (SPN106) kPa *1 All
50222 int16 15222 Air Filter 1 Differential Pressure (SPN107) kPa *100 All
50223 int16 15223 Coolant Pressure (SPN109) kPa *1 All
50224 int16 15224 Transmission Oil Pressure (SPN127) kPa *1 All
50225 int16 15225 Fuel Rail Pressure (SPN157) MPa *10 All
50226 int16 15226 Ambient Air Temperature (SPN171) °C *10 All
50227 int16 15227 Turbo Oil Temperature (SPN176) °C *10 All
50228 int16 15228 Transmission Oil Temperature (SPN177) °C *10 All

9 Appendix

Address
50240 int16 15239 Engine Intercooler Thermostat Opening % *10 All

(SPN1134)
50241 int16 15240 Engine Oil Temperature 2 (SPN1135) °C *10 All
50242 int16 15241 Engine ECU Temperature (SPN1136) °C *10 All

9 Appendix

Address

(SPN1172)

(SPN1173)

(SPN1174)

(SPN1175)
50288 int16 15287 Turbo 3 Turbine Outlet Temperature (SPN °C *10 All
1186)
50290 int16 15289 Engine Aux. Coolant Pressure (SPN1203) kPa *1 All
50291 int16 15290 Pre-filter Oil Pressure (SPN1208) kPa *1 All
50292 int16 15291 Engine Aux. Coolant Temperature (SPN1212) °C *1 All
50298 int16 15297 Right Exhaust Gas Temperature (SPN2433) °C *10 All
50299 int16 15298 Left Exhaust Gas Temperature (SPN2434) °C *10 All
50300 int16 15310 Turbo 1 Compr. Outlet Temperature (SPN2629) °C *10 All
50301 int16 15311 Engine derate request (SPN3644) % *10 All
50302 int16 15312 Batterie Potential (SPN0158) V *10 All
Level (SPN1761)


9 Appendix

Address
Level (SPN4367)

50307 int16 12807 Exhaust Gas Temperature Average(SPN 4151) °C *10 All
(SPN 4153)
(SPN 4152)
50310 int16 12016 Fuel level 1 (SPN 96) % *10 All
50311 int16 12017 Fuel level 2 (SPN 38) % *10 All

9 Appendix

Address
Topic Miscellenous
50370 int16 9202 91.01 AM Internal value 1 All

9 Appendix

Address
Monitored Number of easYgen communicating Mask FF00h All
Number of easYgens currently communicating Mask 00FFh All
Monitored Number of LS5 communicating Mask FF00h EG3500XT-P1
EG3500XT-P2
Number of LS5 currently communicating Mask 00FFh EG3500XT-P1
EG3500XT-P2
Device number of missing LS-5 (33-48) Mask FFFFh EG3500XT-P1
EG3500XT-P2
LS-5 Device Nr. 48 Mask 8000h

9 Appendix

Address
Device number of missing LS-5 (49-64) Mask FFFFh EG3500XT-P1
EG3500XT-P2
50389 int16 181 Phase angle busbar1-generator L1-L2 ° *10 All
50390 int16 184 Phase angle mains-busbar1 L1-L2 ° *10 All
50391 int16 4641 Delta voltage busbar1-generator % *10 All
50392 int16 4640 Delta frequency busbar1-generator Hz *100 All
50393 int16 4607 Phase angle compensated generator-busbar1 ° *10 All

L1-L2
50394 int16 139 Generator power factor L1 *1000 All
50397 int16 8850 Voltage increase monitored value % *100 All
50398 int16 Phase angle compensated mains-busbar1 L1- ° *10 All

L2

9 Appendix

Address
Int32 (Long)
50410 int32 135 Total gen. active power W *1 All
50412 int32 136 Total gen. reactive power var *1 All
50414 int32 137 Total gen. apparent power VA *1 All
50416 int32 170 Average Gen. Wye-Voltage V *10 All
50418 int32 171 Average Gen. Delta-Voltage V *10 All
50420 int32 216 Average Busbar Delta-Voltage V *10 All
50422 int32 185 Av. Gen. Current A *1000 All
50424 int32 111 Gen. current L1 A *1000 All
50430 int32 161 Meas. ground current A *1000 All
50432 int32 159 Calculated ground current A *1000 All
50446 int32 125 Gen. active power L1 W *1 All
50452 int32 182 Busbar 1: voltage L1-L2 V *10 All
50454 int32 2520 Gen. real energy MWh *100 All
50456 int32 2522 Gen. positive reactive energy Mvarh *100 All
50458 int32 2568 Gen. hours of operation h *100 All
50460 int32 5542 Setpoint active power kW *10 All
50462 int32 5640 Setpoint voltage V *1 All
50464 int32 234 Average Busbar Wye-Voltage V *10 All
EG3500XT-P2

9 Appendix

Address
EG3500XT-P2
50470 int32 2526 Gen. negative reactive energy Mvarh *100 All
50472 int32 140 Total mains active power W *1 All
50474 int32 150 Total mains reactive power var *1 All
50476 int32 173 Average Mains Wye-Voltage V *10 All
50478 int32 174 Av. Mains Delta-Voltage V *10 All
50480 int32 207 Av. Mains Current A *1000 All
50482 int32 134 Mains current L1 A *1000 All
50500 int32 217 Reserve real power in system (valid if LDSS is kW *1 All
on)
50502 int32 218 Real power in system (vaild if LDSS is on) kW *1 All
50504 int32 219 Nominal real power in system (vaild if LDSS is kW *1 All
on)
50506 int32 - 05.70 Active power set point ramped kW *10 All
50508 int32 - 05.92 Reactive power set point ramped kvar *10 All
Subtopic Active Diagnostic Trouble Code (DM1) 1-10 (All SPNs)

SPN

SPN

SPN

SPN

SPN

SPN

9 Appendix

Address

SPN

SPN

SPN

SPN
Subtopic Values
50532 int32 15201 Total engine hours (j1939-HOURS, SPN 247) h *1 All
50534 uint32 2580 Period of use counter h *100 All
50536 int32 15319 Engine Total Fuel Used (SPN250) L *10 All
Topic LS5
50542 uint32 267 Average LSx Delta Mains voltage L-L V *10 EG3500XT-P1
EG3500XT-P2
50544 uint32 268 Average LSx Wye Mains voltage L-N V *10 EG3500XT-P1
EG3500XT-P2
50546 int32 269 Active power LSx W *1 EG3500XT-P1
EG3500XT-P2
50548 int32 270 Reactive power LSx var *1 EG3500XT-P1
EG3500XT-P2
Topic Miscellenous
50562 int32 231 Busbar Voltage L1-N V *10 EG3500XT-P2
50568 int32 5646 Setpoint reactive power kvar *10 All
50570 int32 9698 91.15 AM Internal value 15 (long) All
50572 int32 9702 91.16 AM Internal value 16 (long) All
50574 int32 155 Generator current slave pointer L1 A *1000 All

9 Appendix

Address
50580 int32 128 Generator reactive power L1 var *1 All
50586 int32 131 Generator apparent power L1 VA *1 All
50592 int32 152 Mains total apparent power VA *1 All
50594 int32 158 Mains current slave pointer L1 A *1000 All
50596 int32 0 (prepared Mains current slave pointer L2)
50598 int32 0 (prepared Mains current slave pointer L3)
50600 int32

Mux Byte
0 1-2 uint16 Protocol-ID, always 5017
Subtopic Generator
0 3-4 uint16 4161 BITLIST Alarms Generator active
Busbar phase rotation mismatch Mask: 0001h EG3500XT-P2
0 5-6 uint16 10134 BITLIST Alarms Generator latched

(unacknowledged)

9 Appendix

Mux Byte
1 1-2 uint16 4163 BITLIST Alarms Generator 1 active (reserved)
Gen. Asymmetry Mask: 2000h All
Gen. phase rot. misw. Mask: 0400h All
Gen act.pwr mismatch Mask: 0200h All
Gen. unloading fault Mask: 0100h All
Inv.time ov.curr. Mask: 0080h All
Operating range failed, Mask: 0040h All
1 3-4 uint16 10138 BITLIST Alarms Generator 1 latched

(unacknowledged)

9 Appendix

Mux Byte
1 5-6 uint16 10131 BITLIST Alarm classes latched

(unacknowledged)
internal Mask: 4000h
Subtopic Mains
2 1-2 uint16 4188 BITLIST Alarms Mains active

9 Appendix

Mux Byte
Mains phaseshift Mask: 0080h All

(unacknowledged)
3 1-2 uint16 4187 BITLIST Alarms Mains 1 active

9 Appendix

Mux Byte
Mns act.pwr mismatch Mask: 0040h All
Mains. Time dep. Voltage Mask: 0020h All

(unacknowledged)
07.28 Mains Time-dep. Voltage (FRT) latched Mask: 0020h All
Subtopic Engine
Unintended stop Mask: 0800h All
Speed det. Alarm Mask: 0400h All
Shutdwn malfunct. Mask: 0200h All

9 Appendix

Mux Byte
CAN-Fault J1939 Mask: 0010h All
Start fail Mask: 0008h All
Mainten. days exceeded Mask: 0004h All
Mainten. hours exceeded Mask: 0002h All
05.06 Shutdown malfunction detected Mask: 0200h All

latched
EG3500XT-P2
EG3500XT-P2
Missing LSx Mask: 1000h EG3500XT-P1
EG3500XT-P2
Cylinder temperature wire break Mask: 0200h All

9 Appendix

Mux Byte
Pole slip Mask: 0100h All
Syst.update LSx Mask: 0080h EG3500XT-P1
EG3500XT-P2
EG3500XT-P2
GCB sync. Timeout Mask: 8000h All
MCB sync. Timeout Mask: 4000h All
GGB sync. Timeout Mask: 2000h EG3500XT-P1
EG3500XT-P2
Charge alt. low voltage (D+) Mask: 1000h All
Phase rotation mismatch Mask: 0800h All
Parameter Alignment Mask: 0010h All
Red stop lamp DM1 Mask: 0002h All
Amber warning lamp DM1 Mask: 0001h All
08.32 GGB Timeout latched Mask: 2000h EG3500XT-P1
EG3500XT-P2
05.11 Charge alt. low voltage (D+) latched Mask: 1000h All

9 Appendix

Mux Byte
EG3500XT-P2
EG3500XT-P2
08.28 Missing LSx Mask: 1000h EG3500XT-P1
EG3500XT-P2
08.44 Syst.update LSx Mask: 0080h EG3500XT-P1
EG3500XT-P2
EG3500XT-P2
Subtopic GAP Alarms
6 1-2 uint16 5197 BITLIST Alarms GAP active
LS interf.redundancy Mask: 8000h EG3500XT-P1

9 Appendix

Mux Byte
EG3500XT-P2
Neutral contactor failure Mask: 0100h All
Decoupling GCB<->MCB Mask: 0080h All
Meas.difference 4105 VDE-AR-N 4105 Mask: 0040h All
Parameter alignment VDE-AR-N 4105 Mask: 0020h All
Missing member VDE-AR-N 4105 Mask: 0010h All
Busbar monitoring Mask: 0008h All
Plausibility GCB feedback Mask: 0004h MARINE
Reactive load sharing mismatch Mask: 0002h All
Active load sharing mismatch Mask: 0001h All
6 3-4 uint16 10286 BITLIST Alarms GAP latched

(unacknowledged)
08.53 LS interf.redundancy latched Mask: 8000h EG3500XT-P1
EG3500XT-P2

latched
17.07 Meas.difference 4105 VDE-AR-N 4105 Mask: 0040h All

latched
17.06 Parameter alignment VDE-AR-N 4105 Mask: 0020h All

latched

latched

9 Appendix

Mux Byte
7 1-2 uint16 4175 BITLIST Alarms Flexible thresholds 1-16 active


9 Appendix

Mux Byte

active


active

9 Appendix

Mux Byte

9 5-6 uint16 0 (reserve)
10 1-2 uint16 4194 BITLIST Free Alarms active

9 Appendix

Mux Byte
10 3-4 uint16 10282 BITLIST Free Alarms latched

(unacknowledged)
Subtopic Internal DC Analogue Values Wirebreak
11 1-2 uint16 4171 BITLIST Alarms Analog Inputs 1 active

9 Appendix

Mux Byte
11 3-4 uint16 10136 Alarms Analog Inputs 1 latched

(unacknowledged)
12 1-2 uint16 4173 Alarms Analog Inputs Wire Break active

9 Appendix

Mux Byte
12 3-4 uint16 10137 Alarms Analog Inputs Wire Break latched

(unacknowledged)
Subtopic Internal Digital Inputs
13 1-2 uint16 4181 Alarms Digital Inputs 1 active

9 Appendix

Mux Byte

(unacknowledged)
14 1-2 uint16 4183 AlarmsDigital Inputs 2 active

9 Appendix

Mux Byte

(unacknowledged)
Subtopic External Digital Inputs
15 1-2 uint16 4185 Alarms External Digital Inputs active

9 Appendix

Mux Byte
15 3-4 uint16 16377 Alarms External Digital Inputs latched

(unacknowledged)
16 1-2 uint16 4195 Alarm External Digital Inputs 1 active

9 Appendix

Mux Byte
16 3-4 uint16 10284 Alarm External Digital Inputs 1 latched

(unacknowledged)
Subtopic External DC Analogue Values Wirebreak

active

9 Appendix

Mux Byte

17 5 1 Operating Range Monitoring Code Number All

byte
6 1 Internal
byte
18 1.2 uint16 10313 Alarms 4 latched (unacknowledged)
Internal Bit Mask: 8000h
06.36 Pole slip Bit Mask: 1000h All
07.33 FRT Time-dep. voltage 3 Bit Mask: 0800h All

9 Appendix

Mux Byte
08.40 CAN J1939 device 3 timeout Bit Mask: 0010h All
08.37 CAN J1939 ECU timeout Bit Mask: 0002h All
08.29 CANopen error interface 3 Bit Mask: 0001h EG3500XT-P1
EG3500XT-P2
18 3.4 uint16 10314 Alarms 4 active
Pole slip Bit Mask: 1000h All
FRT Time-dep. voltage 2 Bit Mask: 0100h All
CAN J1939 device 3 timeout Bit Mask: 0010h All
CAN J1939 ECU timeout Bit Mask: 0002h All
CANopen error interface 3 Bit Mask: 0001h EG3500XT-P1
EG3500XT-P2
18 5.6 uint16 Internal
21 Mux x 20ms = 0.42s refresh rate

9 Appendix
9.2.9 Additional Data Identifier
9.2.9 Additional Data Identifier
9.2.9.1 Receive Data (sent from remote control to the easYgen)
General notes
The device accepts receive data from outside. These data are usually remote control
data, with which the genset control starts and stops the operation or runs different
setpoints.
These data do not require a password level to be accepted. They are overtaken into a
non-volatile memory and are lost, if the device is powered down.
Ensure Security!
Transmitting data from outside of the remote control needs secure (network)
communication. Do not connect the easYgen with the internet as long the security
aspects are not considered! Consider an IP responsible person to discuss proper security
procedures like placing routers and fire walls.
Take care for sufficient protection of Ethernet communication.
Remote control word 1
Object 21F7h (Parameter 503)
This object is required for remote control. The data type is UNSIGNED16.
The internal parameter 503 of the easYgen must be set to react on the remote control
instructions. This is performed by sending rising signals for the respective bits (refer to
╚═▷ Fig. 345 for the priority of start and stop signals).
Para‐ Object Name Unit Data Note

meter ID type
no.
503 21F7h Control word 1 Bit field unsigned16
Bit 15 Not used
Bit 14 Not used
Bit 13 Not used
Bit 12 Not used
Bit 11 Not used
Bit 10 Not used
Bit 9 Shutdown command To shut down, a "0" must be

written and then a "1"
Bit 8 Not used
Bit 7 Not used
Bit 6 Not used
Bit 5 Not used
Bit 4 Ext. Acknowledge To acknowledge, a 0 must be

(rising edge) Must be written and then a 1

9 Appendix
Para‐ Object Name Unit Data Note

meter ID type
no.
set twice to
acknowledge
Bit 3 Must always be set to

0
Bit 2 Must always be set to

0
Bit 1 Stop bit (rising edge) To stop, a 0 must be written and

then a 1
Bit 0 Start bit (rising edge) To start, a 0 must be written and

then a 1
Tab. 131: Remote control telegram
Bit 0 With the rising edge of the bit, the easYgen activates the remote request command
(LogicsManager input command variable 04.13).
Start bit
The condition of the start command will be stored and may be used as command variable
for the LogicsManager.
Bit 1 With the rising edge of the bit, the easYgen deactivates the remote request command
(LogicsManager input command variable 04.13).
Stop bit
The condition of the start command will be stored and may be used as command variable
for the LogicsManager.
Bit 4 This bit controls the LogicsManager input command variable 04.14. The remote
acknowledge bit must be set and reset twice to acknowledge an alarm completely. The first
"Reset alarms" rising edge disables the horn and the second rising edge resets the alarm.
Bit 9 This bit is directly influencing the LogicsManager command variable: “03.40 Remote
Shutdown“ and can be taken to create an engine shut down and/or an alarm over an
"Shutdown command" internal flag.
Remote start /stop The command variable "04.13 Remote request" changes to "1" (high) if the start bit is
enabled and changes back to "0" (low) if the stop bit is enabled.
Ext. acknowledge The command variable "04.14 Remote acknowledge" is the reflection of the control bit. The
easYgen deactivates the horn with the first change from "0" to "1" of the logical output
"External acknowledge", and acknowledges all alarm messages, which have occurred and
are no longer active, with the second change from "0" to "1".

9 Appendix
Fig. 345: Remote control - start/stop priority
╚═▷ Fig. 345 shows the reaction of the command variable on the various status changes
of the bits.
The easYgen does not react on the disabling of the start bit, but only on the enabling of
the stop bit. This has the advantage that it is not required to maintain the connection
established for the whole time in case of a remote start via a modem.
This object is required for remote control. The data type is UNSIGNED16.
Bit 15 = 1
Bit 14 = 1
Bit 13 = 1
Bit 12 = 1
Bit 11 = 1
Bit 10 = 1
Bit 9 = 1
Bit 8 = 1
Bit 7 = 1 Request active power setpoint 2 – this bit activates the LogicsManager command variable
[04.40] "Remote power setpoint 2" and is dedicated for switching from active power
setpoint 1 to active power setpoint 2
Bit 6 = 1 Request power factor setpoint 2 – this bit activates the LogicsManager command variable
[04.39] "Remote PF setpoint 2" and is dedicated for switching from power factor setpoint 1
to power factor setpoint 2
Bit 5 = 1 Request frequency setpoint 2 – this bit activates the LogicsManager command variable
[04.38] "Remote frequency setpoint 2" and is dedicated for switching from frequency
setpoint 1 to frequency setpoint 2

9 Appendix
Bit 4 = 1 Request voltage setpoint 2 – this bit activates the LogicsManager command variable
[04.37] "Remote voltage setpoint 2" and is dedicated for switching from voltage setpoint 1
to voltage setpoint 2
Bit 3 = 1
Bit 2 = 1
Bit 1 = 1
Bit 0 = 1
This object is required for remote control. These remote control bits can be used by a PLC
to send control signals via SDO or PDO, which can then be used as command variables in
the LogicsManager to control the easYgen. The data type is UNSIGNED16.
Bit 15 = 1 (ID 541) Remote control bit 16 (command variable 04.59)

9 Appendix
Remote active power setpoint
Object 21FBh (Parameter 507)
This value may be used as data source "[05.56] Interface P setp [kW]" via the
AnalogManager. No password is required to write this value.
This object is required to transmit the active power setpoint for active power control.
The data type is INTEGER32.
The value is scaled in [kW * 10].
Example
• 100 kW = 1000 = 03E8h
Remote power factor setpoint
Object 21FCh (Parameter 508)
This value may be used as data source "[05.12] Interface PF sp [%]" via the
This object is required to transmit the power factor setpoint for power factor control.
The valid range for this value is [-710 to 1000 to 710].
Example
• PF (cosphi) = c0.71 (capacitive) = -710 = FD3Ah PF (cosphi) = 1.00 = 1000 =

03E8h PF (cosphi) = i0.71 (inductive) = 710 = 02C6h Remote Frequency Setpoint -
Object 21FDh
Remote frequency setpoint
Object 21FDh (Parameter 509)
This value may be used as data source "[05.53] Interface f setp [Hz]" via the
This object is required to transmit the frequency setpoint for frequency control.
The valid range for this value is [Hz * 100].
Example
• 50.00 Hz = 5000 = 1388h

9 Appendix
Remote voltage setpoint
Object 21FEh (Parameter 510)
This value may be used as data source "[05.59] Interface V setp [V]" via the
This object is required to transmit the voltage setpoint for voltage control.
The data type is UNSIGNED32.
The value is scaled in [V].
Example
• 400 V » 400 = 190h

• 10000 V » 10000 = 2710h
Remote reactive power setpoint
Object 21FFh (Parameter 511)
This value may be used as data source "[05.83] Interf.kvar sp [kvar]" via the
AnalogManager. No password is required to write this value. This object is required to
transmit the reactive power setpoint for the kvar control.
The data type is signed INTEGER32.
The value is scaled in [kvar*10].
Examples:
• 100.0 kvar » 1000 = 3E8h

• 100.2 kvar » 1002 = 3EAh
Q(V) voltage shift VQ0
Object 2200h (Parameter 512)
This is the Setpoint for the reactive power - voltage function Q(V). [VDE-AR-N 4110]
Interface reference value VQ0 has the resolution of (1/100) steps. The “starting” value is
1.00. A value limitation is included.

9 Appendix
Remote LDSS IOP reserve power
This value may be used to modify LDSS reserve power value [kW] for island operation via
interface.
Notes:
• Parameters “5760 IOP Reserve power”, “5648 IOP Reserve power 2” and LM
“120604 IOP Reserve power 2” are not overwritten by this write command.
• The last change either via interface or via the parameter selected with the LM is
effective.
• If there is no change anymore, the last change will be kept until power cycling the
device.
• After power cycling, the parameter value is used until the easYgen receives a
different value via interface.
• The parameter alignment is still done with the active parameter value.
Remote LDSS MOP reserve power
This value may be used to modify LDSS reserve power value [kW] for parallel to mains
operation via interface.
Notes:
• Parameter “5768 MOP Reserve power”, “5649 MOP Reserve power 2” and LM
“120605 MOP Reserve power 2” are not overwritten by this write command.
• The last change either via interface or via the parameter selected with the LM is
effective.
• If there is no change anymore, the last change will be kept until power cycling the
device.
• After power cycling, the parameter value is used until the easYgen receives a
different value via interface.
• The parameter alignment is still done with the active parameter value.
Free analog values
The device provides identifier “Free analog values” for receiving 16 bit signed integers for
free purposes. The values are available in the AnalogManager group 24. Refer to ╚═▷
“9.2.9.3.4 Free Analog Values”
External DI request (1 to 16)
Object 3F4Eh (Parameter 8014)
This object is required to receive the state of the external discrete inputs 1 to 16 (e.g. of
a Phoenix expansion card). The data type is UNSIGNED16.

9 Appendix
Bit 15 External discrete input 16 [DIex16]
External DI request (17 to 32)
Object 3F4Fh (Parameter 8015)
This object is required to receive the state of the external discrete inputs 17 to 32 (e.g. of
a Phoenix expansion card). The data type is UNSIGNED16.

9 Appendix
9.2.9.2 Transmit Data (sent from easYgen to control external devices)
External Analog Inputs
Object 4008h ff, Subindex 1 (Parameter 8200 ff)
This unscaled value is transmitted by the external expansion board. The easYgen must
be configured to format this value accordingly. The data type is UNSIGNED16.
The external analog inputs 1 to 16 have the following parameter IDs:
AI # 1 2 3 4 5 6 7 8
Object 4008 4009 400A 400B 400C 400D 400E 400F
ID 8200 8201 8202 8203 8204 8205 8206 8207
AI # 9 10 11 12 13 14 15 16
Object 4010 4011 4012 4013 4014 4015 4016 4017
ID 8208 8209 8210 8211 8212 8213 8214 8215
The device sends data out which are receipt by external devices. These data usually are
commands to control expansion boards or annunciators running CANopen.
External DO control (1 to 16)
This object is required to control the external outputs (relays) 1 to 16 (e.g. of a Phoenix
expansion card). The data type is UNSIGNED16.
Bit 15 External discrete output 16 [Rex16]

9 Appendix
External DO control (17 to 32)
This object is required to control the external outputs (relays) 17 to 32 (e.g. of a Phoenix
expansion card). The data type is UNSIGNED16.
External Analog Outputs
Object 4806h ff, Subindex 1 (Parameter ID 10246 ff)
This unscaled value is transmitted by the external expansion board. The easYgen must
be configured to format this value accordingly. The data type is UNSIGNED16.
The external analog outputs 1 to 4 have the following parameter IDs:
AI # 1 2 3 4
Object 4806hex 4810hex 481Ahex 4824hex
ID 10245 10255 10265 10275

9 Appendix
9.2.9.3 Data Receive (interconnectivity)
9.2.9.3 Data Receive (interconnectivity)
9.2.9.3.1 Introduction
The easYgen provides different possibilities to receive data from other CAN or Modbus
devices. The received data are available in the AnalogManager or LogicsManager system.
There are:
• Analog variables called CAN1 RPDO...
• Command variables (single bits of some Analog variables)
• Free analog values
9.2.9.3.2 Analog variables CAN1 RPDO
The table below shows data which can be received via CAN RPDO or Modbus from any
other devices. These data are available as analog variables (of group 21) and can be
assigned to analog manager equations e.g. for free alarms or setpoints. For usage with
CAN the corresponding indices must be mapped to the RPDOs. It is also possible to write
via Modbus to these indices.
If “LDSS with predicted load” is used in “External” mode, RPDOx Word1 and RPDOx
Word2 are used for LDSS and are not available for other functions. (Refer to ╚═▷ “6.3.15
LDSS with predicted load”).
Analog variable Receive PDO Index
21.01 CAN1 RPDO1.1 RPDO1 Word1 (signed short) 3371

9 Appendix
9.2.9.3.3 Commnand variables CAN 1 RPDO
Analog variable Receive PDO Index
The single bits 1-16 of RPDO1 Word1 (3371), RPDO2 Word1 (3375), RPDO3 Word1 (3379),
RPDO4 Word1 (3383) and RPDO5 Word1 (3387) are available as command variables of
groups 32 to 36 which can be assigned to LogicsManagers.
LogicsManager variable Index
32.01 CAN1 RPDO1.1.01 3371
32.02 CAN1 RPDO1.1.02
32.03 CAN1 RPDO1.1.03
32.04 CAN1 RPDO1.1.04
32.05 CAN1 RPDO1.1.05
32.06 CAN1 RPDO1.1.06
32.07 CAN1 RPDO1.1.07
32.08 CAN1 RPDO1.1.08
32.09 CAN1 RPDO1.1.09
32.10 CAN1 RPDO1.1.10
32.11 CAN1 RPDO1.1.11
32.12 CAN1 RPDO1.1.12
32.13 CAN1 RPDO1.1.13
32.14 CAN1 RPDO1.1.14
32.15 CAN1 RPDO1.1.15
32.16 CAN1 RPDO1.1.16
33.01CAN1 RPDO2.1.01 3375
33.02 CAN1 RPDO2.1.02
33.03 CAN1 RPDO2.1.03
33.04 CAN1 RPDO2.1.04
33.05 CAN1 RPDO2.1.05
33.06 CAN1 RPDO2.1.06
33.07 CAN1 RPDO2.1.07
33.08 CAN1 RPDO2.1.08
33.09 CAN1 RPDO2.1.09
33.10 CAN1 RPDO2.1.10
33.11 CAN1 RPDO2.1.11
33.12 CAN1 RPDO2.1.12
33.13 CAN1 RPDO2.1.13
33.14 CAN1 RPDO2.1.14

9 Appendix
33.15 CAN1 RPDO2.1.15
33.16 CAN1 RPDO2.1.16
34.01 CAN1 RPDO3.1.01 3379
34.02 CAN1 RPDO3.1.02
34.03 CAN1 RPDO3.1.03
34.04 CAN1 RPDO3.1.04
34.05 CAN1 RPDO3.1.05
34.06 CAN1 RPDO3.1.06
34.07 CAN1 RPDO3.1.07
34.08 CAN1 RPDO3.1.08
34.09 CAN1 RPDO3.1.09
34.10 CAN1 RPDO3.1.10
34.11 CAN1 RPDO3.1.11
34.12 CAN1 RPDO3.1.12
34.13 CAN1 RPDO3.1.13
34.14 CAN1 RPDO3.1.14
34.15 CAN1 RPDO3.1.15
34.16 CAN1 RPDO3.1.16
35.01 CAN1 RPDO4.1.01 3383
35.02 CAN1 RPDO4.1.02
35.03 CAN1 RPDO4.1.03
35.04 CAN1 RPDO4.1.04
35.05 CAN1 RPDO4.1.05
35.06 CAN1 RPDO4.1.06
35.07 CAN1 RPDO4.1.07
35.08 CAN1 RPDO4.1.08
35.09 CAN1 RPDO4.1.09
35.10 CAN1 RPDO4.1.10
35.11 CAN1 RPDO4.1.11
35.12 CAN1 RPDO4.1.12
35.13 CAN1 RPDO4.1.13
35.14 CAN1 RPDO4.1.14
35.15 CAN1 RPDO4.1.15
35.16 CAN1 RPDO4.1.16
36.01 CAN1 RPDO5.1.01 3387
36.02 CAN1 RPDO5.1.02
36.03 CAN1 RPDO5.1.03
36.04 CAN1 RPDO5.1.04

9 Appendix
36.05 CAN1 RPDO5.1.05
36.06 CAN1 RPDO5.1.06
36.07 CAN1 RPDO5.1.07
36.08 CAN1 RPDO5.1.08
36.09 CAN1 RPDO5.1.09
36.10 CAN1 RPDO5.1.10
36.11 CAN1 RPDO5.1.11
36.12 CAN1 RPDO5.1.12
36.13 CAN1 RPDO5.1.13
36.14 CAN1 RPDO5.1.14
36.15 CAN1 RPDO5.1.15
36.16 CAN1 RPDO5.1.16
The figure below shows how the name of these Command Variables are composed. (The
naming of the variables was chosen with regard to their usage as CAN1 RPDOs.)
Naming CANopen Receive PDO

LogicsManager Command Variables
CAN Receive PDO

Channel PDO no. Word no.
LogicsManager
Word
Command variable
Bit
Group No.
32.16 CAN1 RPDO1.1.16
Fig. 346: Naming of the Command Variables.
The figure below shows an example of how CAN 1 RPDOs can be configured for
interconnectivity. The 4 data words received at
• COB-ID 1026 (dec) are assigned to the Analog Variables 21.01, 21.02, 21.03 and
21.04 via configuration. The bits of 21.01 are assigned internally to the Command
Variables 32.01 - 32.16.
• COB-ID 1030 (dec) are assigned to the Analog Variables 21.17, 21.18, 21.19 and
21.20 via configuration. The bits of 21.17 are assigned internally to the Command
Variables 36.01 - 36.16.
These Analog Variables and Command Variables can be used in AnalogManagers and
LogicsManagers equations to control different functions.

9 Appendix
9.2.9.3.4 Free Analog Values
CANopen CAN 1 Receive PDO
LogicsManager
Receive PDO1
AnalogManager Command
9300 COB-ID 1026 dec Analog Variables Variables
9121 Event timer 2000 ms
Group 32
8970 Selected Data Protocol 0
Group 21 Index 32.01 CAN1 RPDO1.1.1
9910 Number of mapped Objects 4 32.02 CAN1 RPDO1.1.2
21.01 CAN1 RPDO1.1 3371
9911 1. Mapped Object 3371 21.02 CAN1 RPDO1.2 3372 32.03 CAN1 RPDO1.1.3
9912 2. Mapped Object 3372 21.03 CAN1 RPDO1.3 3373 32.04 CAN1 RPDO1.1.4
21.04 CAN1 RPDO1.4 3374 32.05 CAN1 RPDO1.1.5

9913 3. Mapped Object 3373
21.05 CAN1 RPDO2.1 3375 32.06 CAN1 RPDO1.1.6
32.07 CAN1 RPDO1.1.7
21.06 CAN1 RPDO2.2 3376
32.08 CAN1 RPDO1.1.8
21.07 CAN1 RPDO2.3 3377
32.09 CAN1 RPDO1.1.9
21.08 CAN1 RPDO2.4 3378
32.10 CAN1 RPDO1.1.10
RPDO RPDO RPDO RPDO
RPDO1 1.1 1.2 1.3 1.4 32.11 CAN1 RPDO1.1.11
32.12 CAN1 RPDO1.1.12
32.13 CAN1 RPDO1.1.13
32.14 CAN1 RPDO1.1.14
32.15 CAN1 RPDO1.1.15
32.16 CAN1 RPDO1.1.16
Receive PDO5
12806 COB-ID 1030 dec Group 33
9125 Event timer 2000 ms 33.01 CAN1 RPDO2.1.1
8974 Selected Data Protocol 0
12831 Number of mapped Objects 4

21.17 CAN1 RPDO5.1 3387
12834 1. Mapped Object 3387 33.16 CAN1 RPDO2.1.16
21.18 CAN1 RPDO5.2 3388
21.19 CAN1 RPDO5.3 3389
12836 3. Mapped Object 3389 21.20 CAN1 RPDO5.4 3390
Group 36
36.01 CAN1 RPDO5.1.1
RPDO RPDO RPDO RPDO

RPDO5 5.1 5.2 5.3 5.4
36.16 CAN1 RPDO5.1.16
Fig. 347: Example of a CAN 1 RPDO configuration for interconnectivity.
9.2.9.3.4 Free Analog Values
Additionally the device provides “Free analog values” for receiving data for free
purposes. These indices can be mapped to RPDOs or can be written via Modbus. The
values are available in the AnalogManager group 24.
In future releases (higher than 2.10-0) the variables 24.05-24.08 will be write-protected
with code level CL1.
Index Name Format Usable as
587 Free analog value 1 INT16 signed AnalogManager 24.01

9 Appendix
9.2.9.4 Data Identifiers in General
Index Name Format Usable as
The communication interface programmer needs often for single data transfer the
identifier of the easYgen variable. To figure that out he has here some tips.
Data Protocol Document: Identifier Information in Column "Parameter ID"
The data protocol document shows usually in the column “Parameter ID” the identifier for
a single use. Please check the type. Usually it is a signed INT16 (Short) variable but
depending on the function it can also be a signed INT32 (Long). Typical values for long are
voltages, currents and power measurement values.
Fig. 348: Data Protocol Document in Columns "Parameter ID"
ToolKit: Identifier in front of the parameter or visualization
Nearly each parameter in ToolKit shows the according identifier in front of the data. The
data type is to check. Usually it is a signed INT16 (Short) variable but depending on the
function it can also be a signed INT32 (Long). Typical values for long are voltages,
currents and power measurement values.

9 Appendix
Fig. 349: ToolKit page with generator visualization data
With a few minor exceptions the reading of parameter are always possible. Writing of
parameter is only accepted if the correct code level was passed for the according
interface channel.
Fig. 350: ToolKit page with configuration data
The access on AnalogManager variables is provided as a signed 4 byte float value without
decimals.

9 Appendix
9.3 LogicsManager Reference
Fig. 351: ToolKit page with Analog manager data
9.3 LogicsManager Reference
9.3.1 LogicsManager Overview
The LogicsManager is used to customize the sequence of events in the control unit such
as the start command of the engine or the operation of control unit relay outputs. For
example, the start routine may be programmed so that it requires the closing of a
discrete input or a preset time of day.
Depending on the application mode of the unit, the number of available relays that may
be programmed with the LogicsManager will vary.
Two independent time delays are provided for the configured action to take place and be
reset.
Please do not use the output of an equation as input at the same time. Such a
configuration could decrease the performance of the interface.

9 Appendix
Structure and description of the LogicsManager
Fig. 352: LogicsManager - function overview
• Command (variable)
A list of over 400 parameters and functions is provided for the command inputs.
Examples of the parameters that may be configured into these commands are
generator undervoltage thresholds 1 and 2, start fail, and cool down.
These command variables are used to control the output function or relay.
Refer to ╚═▷ “9.3.2 Logical Command Variables” for a complete list of all command
variables.
• Sign
The sign field can be used to invert the state of the command or to fix its output to a
logical true or false if the command is not needed. Setting the sign to the NOT state
changes the output of the command variable from true to false or vice versa.
• Operator
A logical device such as AND or OR.
• (Logical) output
The action or control sequence that occurs when all parameters set into the
LogicsManager are met.
For a complete list of all logical outputs refer to ╚═▷ “9.3.4 Logical Outputs”.
[Sx] - Sign {x}
Value {[Cx]} The value [Cx] is passed 1:1.
NOT Value {[Cx]} The opposite of the value [Cx] is passed.
0 [False; always "0"] The value [Cx] is ignored and this logic path will
always be FALSE.
1 [True; always "1"] The value [Cx] is ignored and this logic path will
always be TRUE.
Tab. 132: Signs
[Ox] - Operator {x}
AND Logical AND

9 Appendix
[Ox] - Operator {x}
NAND Logical negated AND
OR Logical OR
NOR Logical negated OR
XOR Exclusive OR
NXOR Exclusive negated OR
Tab. 133: Operators
For the various display formats of the corresponding logical symbols refer to ╚═▷ “9.3.3
Logical Symbols”.
Configuration of the command chain
Using the values specified in the above table, the chain of commands of the
LogicsManager (for example: operating the relays, setting the flags, specification of the
automatic functions) is configured as follows:
[Ax] = ( ( [C1] & [S1] ) & [O1] & ( [C2] & [S2] ) ) & [O2] & ( [C3] & [S3] )
☼ Programming example for the LogicsManager
Fig. 353: Programming example (ToolKit)
• Relay [R2] shall energize, whenever "Discrete input [DI 02]" is energized "AND" the
control does "NOT" have a fault that is "Alarm class C" "AND" does "NOT" have a
fault that is "Alarm class D"
The logical command variables are grouped into different categories.
Part 1: LM variables (1 to 39)
Cascading: Use digital results
This digital results of AnalogManagers and LogicsManagers are available as

LogicsManager Variables additionally. Like the other LM Variables they can be used as
input signal for (further) AnalogManagers or LogicsManagers.
Part 2: AM and LM results (80 to 99)

9 Appendix
9.3.2 Logical Command Variables
9.3.2 Logical Command Variables
9.3.2.1 Group 01: Global alarms
For the description of the alarm classes refer to chapter 'Alarm classes'.
No. HMI Text Note
01.01 Alarm class A TRUE as long as an alarm of alarm class A is active or
latched.
01.02 Alarm class B TRUE as long as an alarm of alarm class B is active or
latched.
01.03 Alarm class C TRUE as long as an alarm of alarm class C is active or
latched.
01.04 Alarm class D TRUE as long as an alarm of alarm class D is active or
latched.
01.05 Alarm class E TRUE as long as an alarm of alarm class E is active or
latched.
01.06 Alarm class F TRUE as long as an alarm of alarm class F is active or
latched.
01.07 All alarm classes TRUE as long as at least one alarm of the alarm classes
A / B / C / D / E / F is active or latched.
01.08 Warning alarm TRUE as long as at least one alarm of the alarm classes A / B
is active or latched.
01.09 Shutdown alarm TRUE as long as at least one alarm of the alarm classes
C / D / E / F is active or latched.
01.10 Centralized alarm TRUE as long as at least one alarm of the alarm classes
B / C / D / E / F is active or latched.
01.11 New alarm triggered TRUE if any alarm of the Alarm classes B / C / D / E / F has been
triggered until it is acknowledged.
9.3.2.2 Group 02: System conditions
No. HMI Text Note
02.01 FALSE Fixed value - often used for default setting
02.02 TRUE Fixed value - often used for default setting
02.03 Gen. voltage ok TRUE as long as the generator voltage is within the
operating range.

9 Appendix
No. HMI Text Note
02.04 Gen. frequency ok TRUE as long as the generator frequency is within the
operating range.
02.05 Gen. volt. / freq. ok TRUE as long as the generator voltage and frequency
are within the operating ranges (02.03. and 02.04 are
TRUE).
02.06 Busbar 1 voltage ok TRUE as long as the busbar 1 voltage is within the
generator voltage operating range.
02.07 Busbar 1 freq. ok TRUE as long as the busbar 1 frequency is within the
generator frequency operating range.
02.08 Busb1 volt. / freq. ok TRUE as long as the busbar 1 voltage and frequency
are within the generator operating ranges
(02.06. and 02.07 are TRUE).
02.09 Mains voltage ok TRUE as long as the mains voltage is within the operating range.
This command variable is derived from the easYgen
mains measuremend, not from the LS5 !
02.10 Mains frequency ok TRUE as long as the mains frequency is within the operating range.
02.11 Mains volt. / freq. ok TRUE as long as the mains voltage and frequency are within the operating ranges
(02.09. and 02.10 are
TRUE).
02.12 Gen. rotation CCW TRUE as long as the respective rotation field is
detected in case of a three-phase voltage measurement
at the respective measuring location.
02.13 Gen. rotation CW TRUE as long as the respective rotation field is
02.14 Mains rotation CCW TRUE as long as the respective rotation field is
These command variables are derived from the
easYgen mains measuremend, not from the LS5 !
02.15 Mains rotation CW TRUE as long as the respective rotation field is

9 Appendix
No. HMI Text Note

These command variables are derived from the
easYgen mains measuremend, not from the LS5 !
02.16 Busb.1 rotation CCW TRUE as long as the respective rotation field is
02.17 Busb.1 rotation CW TRUE as long as the respective rotation field is
02.21 Dead busbar1 TRUE as long as the busbar voltage is below the value configured in parameter
5820 (Dead
bus detection max. volt.)
02.29 Sync.Check gen. / busb Synchronize Check Relay:
Generator / Busbar (ANSI 25)
TRUE, if all of the following ranges matches:
• voltage
• frequency
• phase angle
• acceleration range
• lead angle
02.32 Sync.Check mns / busb Synchronize Check Relay:
Mains / Busbar (ANSI 25)
TRUE, if all of the following ranges matches:
• voltage
• frequency
• phase angle
• acceleration range
• lead angle
02.34 Firing speed electr. True if generator frequency value matches firing speed.
02.35 Firing speed rpm True if rpm (via MPU or J1939) value matches firing speed.
02.36 Speed electr. True if generator frequency value matches speed detected.
02.37 Speed rpm True if rpm (via MPU or J1939) value matches speed detected.
02.38 Gen excitation lim. TRUE if generator excitation
limit has exceeded.
02.39 Mains decoupl.enabl. TRUE if "3110 Mains decoupling" is

9 Appendix
9.3.2.3 Group 03: Engine control
No. HMI Text Note

not Off and "87.31 LM: Enable Mns
dec." is TRUE
02.45 Mns.release breaker TRUE if mains breaker reconnection is released.
02.46 f dep.power change True if frequency depending up- or derating is active
No. HMI Text Note
03.01 Auxiliary services TRUE if an auxiliary services prerun or postrun is enabled.
03.02 Starter TRUE if the starter relay is energized.
03.04 Preglow / Ignition TRUE if
Preglow (Diesel engine) or
Ignition (Gas engine) is active.
03.05 Horn True if a new alarm (higher A) is triggered and time (parameter
1756) for horn reset has not exceeded.
03.06 Engine released TRUE if the engine is requested and the start is released.
03.07 Engine delay expired TRUE after expiration of the "delayed engine monitoring" timer
until the fuel relay is de-energized.
03.08 Break. delay expired TRUE after expiration of the Generator Stable Time until the fuel
relay is de-energized.
(Breaker actions are not permitted anymore.)
03.13 Blinking lamp ECU TRUE as soon as the ECU activates the diagnosis light (only
for Scania S6 ECU). This command variable is only active if
remote control of the ECU via easYgen is activated.
03.14 ECU special ignition TRUE as long as a reset or read-out of the Scania S6 ECU
blink code is requested (only for S6 Scania ECU). This command
variable is only active if remote control of the ECU via
easYgen is activated.
03.15 ECU seq. B_OUT_1 This flag is for special ECU indications:
Scania S8: "Power Lost Due to High Temperature"
Scania S8: "Low Urea Level"
03.20 Governor raise TRUE if the "Three Position Controller Frequency / Active Power" raise pulse is
active.

9 Appendix
No. HMI Text Note
03.21 Governor lower TRUE if the "Three Position Controller Frequency / Active Power" lower pulse is
active.
03.22 AVR raise TRUE if the "Three Position Controller Output Voltage / Reactive Power" raise pulse
is active.
03.23 AVR lower TRUE if the "Three Position Controller Output Voltage / Reactive Power" lower pulse
is active.
03.24 Excitation AVR TRUE if excitation is released.
03.25 Engine shall run TRUE if engine start conditions are fulfilled.
03.27 Stop solenoid TRUE if a stop signal is issued until the stop time of engine
expires
03.28 Start / Gas TRUE if the fuel solenoid (Diesel) or gas valve (gas) is released.
03.30 Aux. serv. prerun TRUE if "Auxiliary services prerun" is active
03.31 Aux. serv. postrun TRUE if "Auxiliary services postrun" is active
03.32 + PID1 controller TRUE if the "Free PID 1" raise pulse is active.
03.33 - PID1 controller TRUE if the "Free PID 1" lower pulse is active.
03.38 Inhibit cranking TRUE if inhibit cranking is activated
03.39 Close neutral cont. TRUE if neutral contactor close command is active.
03.40 Remote Shutdown TRUE if remote shutdown (ID 503, Bit 9) is acitve.
03.41 Aux. excit. 12V act. TRUE if auxilliary excitation D + 12 V is active.
03.42 Aux. excit. 24V act. TRUE if auxilliary excitation D + 24 V is active.
03.44 Protection lamp DM1 TRUE if ECU Protection lamp DM1 (SPN 987) is active.
03.45 Emission lamp DM1 TRUE if ECU Emission lamp DM1 (SPN 1213) is active.
03.46 DPF lamp solid on TRUE if ECU Diesel Particulate Filter Lamp Command: ON solid
(SPN 3697) is active.
03.47 DPF lamp fast blink TRUE if ECU Diesel Particulate Filter Lamp Command: fast blinking (SPN 3697) is
active.
03.48 DPF regenerat.active TRUE if ECU Diesel Particulate Filter Active Regeneration Status: active (SPN 3700)
is active.
03.49 DPF regenerat.needed TRUE if ECU Diesel Particulate Filter Active Regeneration Status: regeneration
needed (SPN 3700) is active.
03.50 DPF reg. needed low TRUE if ECU Diesel Particulate Filter Status: Regeneration needed: lowest level
03.51 DPF reg. needed mod. TRUE if ECU Diesel Particulate Filter Status: Regeneration needed: moderate level
03.52 DPF reg. needed high TRUE if ECU Diesel Particulate Filter Status: Regeneration needed: highest level
03.53 Exh. temp. lamp on TRUE if ECU Exhaust System High Temperature Lamp Command: on (SPN 3698) is
active.

9 Appendix
9.3.2.4 Group 04: Application conditions
No. HMI Text Note
03.54 Wait to start lamp TRUE if ECU Engine Wait to Start Lamp: on (SPN 1081) is active.
(In Deutz EMR mode: Preheat active.)
03.57 DPF: Pass.regeneration TRUE if ECU Diesel Particulate Filter Passive Regeneration Status: Active (SPN
3699) is active.
03.58 DPF: Act.reg.inhibit TRUE if ECU Diesel Particulate Filter Active Regeneration Inhibited Status: Inhibited
No. HMI Text Note
04.01 Operat. mode AUTO TRUE if operating mode AUTOMATIC is active.
04.02 Operat. mode STOP TRUE if operating mode STOP is active.
04.03 Operat. mode MAN TRUE if operating mode MANUAL is active.
04.04 Operat. mode TEST TRUE if operating mode TEST is active.
04.05 Acknowledge TRUE if "Acknowledge" push button has
been pressed or an external
acknowledgment via LogicsManager is active.
(This condition is TRUE for approx. 40 ms and must be extended utilizing a delay
time.)
04.06 GCB closed TRUE if DI 8 (Reply GCB) is de-energized.
04.07 MCB closed TRUE if DI 7 (Reply MCB) is de-energized.
04.09 Emergency mode TRUE if the emergency "Mains fail delay time" has exceed.
False if the MCB is closed after the mains settling time.
04.10 Cool down TRUE as long as the cool down time is running.
04.11 Mains settling TRUE if a mains failure detected.
FALSE if the mains settling timer has expired.
04.12 Start w / o load TRUE if start without closing GCB is active.
04.13 Remote request TRUE if a remote start request is active (Control word 503)
04.14 Remote acknowledge TRUE if a remote acknowledge is active (Control word 503)
04.15 Idle run active TRUE if the idle mode is active. This may be used to issue an "Idle" command to a
speed controller.
04.18 Synchron. GCB active TRUE if the GCB shall be synchronized.
04.19 Opening GCB relay act TRUE if the GCB open relay is energized.
04.20 Closing GCB active TRUE if the GCB close relay is energized.
04.21 Syn. MCB is active TRUE if the MCB shall be synchronized.
04.22 Opening MCB active TRUE if an MCB open command is active.
04.23 Closing MCB active TRUE if an MCB close command is active.
04.27 Critical mode TRUE if critical mode is enabled
04.28 Generator unloading TRUE if generator is unloading.

9 Appendix
No. HMI Text Note
04.29 Mains unloading TRUE if mains unloading is active.
04.30 Limited prerun TRUE if prerun with warm up load limitation is active.
04.31 Segment no.2 act. TRUE if the result LM "12929 segment number 2" is true.
(LM 12929 has priority.)
(LMs 12929, 12928 have priority.)
04.34 LDSS Priority 2 TRUE if the result of LM "12926 LDSS Priority 2" is true.
(LMs 12926, 12925 have priority.)
04.37 Remote volt. setp. 2 TRUE if "Request Voltage Setpoint 2" is set via interface (control word 504).
04.38 Remote freq. setp. 2 TRUE if "Request Frequency Setpoint 2" is set via interface (control word 504).
04.39 Remote PF setp. 2 TRUE if "Request Power Factor Setpoint 2" is set via interface (control word 504).
04.40 Remote pwr. setp. 2 TRUE if "Request Active Power Setpoint 2" is set via interface (control word 504).
04.41 Transition mode 1 TRUE if the result LM "12931 Transition mode
1" is true.
04.42 Transition mode 2 TRUE if the result LM "12932 Transition mode
2" is true.
04.43 LD start stop TRUE if the result LM "12930 Load dependent
start / stop" is true.
04.44 RemoteControl Bit 1 TRUE if remote control bit 1 is activated. (Control word 505)

9 Appendix
9.3.2.5 Group 05: Engine related alarms
No. HMI Text Note
04.60 Crit. mode postrun TRUE as long as the critical mode postrun time is running.
04.61 Lamp test TRUE if lamp test is active.
04.62 Act.pwr.LS active TRUE if load share of active power is active.
04.63 React.pwr.LS active TRUE if load share of reactive power is active.
04.64 Key activation TRUE as long as the "Key activation time" is running.
Only relevant for versions with front panel (HMI).
04.65 System update active TRUE if System Update (teach in process) is active.
04.66 Mains failure ended TRUE if "Mains Settling Time" is triggered OR mains frequency dependent power
up- / derating becomes deactive.
Reset if
power setpoint after resynchronization is reached OR
GCB is opened OR
mains is ok again for the time cofigured with parameter 5015.
04.67 Reserve power avail. TRUE if reserve power is available.
04.68 ATS start request TRUE if LDSS with predicted load wants to start the engines. This command
variable
can be assigned to the LM "Start request in
AUTO"
04.69 Inhibit ATS TRUE if "04.68 ATS start request"
is true and the rated power on the bus bar is
lower than the predicted load. It shall be passed to a relay to inhibit the ATS
control to switch load in any direction.
04.70 Opening GCB active TRUE if the GCB is to be opened. (Independent of the relay NC / NO.)
04.74 PV load ref. 0% TRUE if the PV inverter shall be limited to 0 % of rated.
04.77 PV load ref. 100% TRUE if the PV inverter shall provide up to 100 % of rated.
9.3.2.5 Group 05: Engine related alarms
TRUE if the alarm is active or latched.
No. HMI Text Note
05.01 Overspeed 1 Engine Over speed threshold 1
05.02 Overspeed 2 Engine Over speed threshold 2
05.03 Underspeed 1 Engine Under speed threshold 1

9 Appendix
9.3.2.6 Group 06: Generator related alarms
No. HMI Text Note
05.04 Underspeed 2 Engine Under speed threshold 2
05.05 Unintended stop Unintended shutdown
05.06 Eng. stop malfunction Shutdown malfunction
05.07 Speed / freq. mismatch Pickup speed / Frequeny mismatch
05.08 Start fail Start failure
05.09 Maint. days exceeded Maintenance days exceeded
05.10 Maint. hrs exceeded Maintenance hours exceeded
05.11 Charge alt. low volt Charge Alternator D + low voltage
05.13 Red stop lamp ECU red stop lamp
05.14 Amber warning lamp ECU amber / yellow stop lamp
05.16 Derating active Free derating or J1939 derating (event, no alarm)
05.17 Uprating active Uprating active (event, no alarm)
05.18 Cyl.tmp.lev.1 Cylinder temperature level 1
05.19 Cyl.tmp.lev.2 Cylinder temperature level 2
05.20 Cyl.tmp.wire brk. Cylinder temperature wire break
05.22 ECU Protect lamp AL ECU protect lamp
05.23 ECU Emission lamp AL ECU emission (malfunction) lamp
9.3.2.6 Group 06: Generator related alarms
No. HMI Text Note
06.01 Gen. overfrequency 1 Generator over frequency threshold 1
06.02 Gen. overfrequency 2 Generator over frequency threshold 2
06.03 Gen.underfrequency 1 Generator under frequency threshold 1
06.04 Gen.underfrequency 2 Generator under frequency threshold 2
06.05 Gen. overvoltage 1 Generator over voltage threshold 1
06.06 Gen. overvoltage 2 Generator over voltage threshold 2
06.07 Gen. undervoltage 1 Generator under voltage threshold 1
06.08 Gen. undervoltage 2 Generator under voltage threshold 2
06.09 Gen. overcurrent 1 Generator over current threshold 1
06.12 Gen. rev. / red. pwr.1 Reverse / reduced power threshold 1
06.13 Gen. rev. / red. pwr.2 Reverse / reduced power threshold 2
06.14 Gen. overload IOP 1 Generator overload IOP threshold 1
06.15 Gen. overload IOP 2 Generator overload IOP threshold 2
06.16 Unbalanced load 1 Generator unbalanced load threshold 1

9 Appendix
9.3.2.7 Group 07: Mains related alarms
No. HMI Text Note
06.17 Unbalanced load 2 Generator unbalanced load threshold 2
06.18 Gen. volt. asymmetry Generator voltage asymmetry
06.19 Ground fault 1 Ground fault threshold 1
06.20 Ground fault 2 Ground fault threshold 2
06.21 Gen.ph.rot. mismatch Generator Phase Rotation mismatch
06.22 Inv. time overcurr. Inverse time over current
06.23 Gen. overload MOP 1 Generator overload MOP threshold 1
06.24 Gen. overload MOP 2 Generator overload MOP threshold 2
06.25 Gen. PF lagging 1 Generator Power Factor lagging 1
06.26 Gen. PF lagging 2 Generator Power Factor lagging 2
06.27 Gen. PF leading 1 Generator Power Factor leading 1
06.28 Gen. PF leading 2 Generator Power Factor leading 2
06.29 Gen act.pwr mismatch Generator active power mismatch
06.30 Gen. unload.mismatch Generator unloading mismatch
06.31 Operat. range failed Operating Range failed
06.32 Gen. AC wiring Generator AC wiring plausibility
06.33 Busbar 1 AC wiring Busbar 1 AC wiring plausibility
06.36 Pole slip Gen pole slip monitoring
9.3.2.7 Group 07: Mains related alarms
No. HMI Text Note
07.05 Mns.ph.rot. mismatch Mains Phase rotation mismatch
07.06 Mains overfreq. 1 Mains over frequency threshold 1
07.07 Mains overfreq. 2 Mains over frequency threshold 2
07.08 Mains underfreq. 1 Mains under frequency threshold 1
07.09 Mains underfreq. 2 Mains under frequency threshold 2
07.10 Mains overvoltage 1 Mains over voltage threshold 1
07.11 Mains overvoltage 2 Mains over voltage threshold 2
07.12 Mains undervoltage 1 Mains under voltage threshold 1
07.13 Mains undervoltage 2 Mains under voltage threshold 2
07.14 Mains phase shift Mains Phase shift
07.15 Mains df / dt Mains df / dt
(Change of frequency)
07.16 Mns. act.pwr mismatch Mains active power mismatch
07.17 Mains PF lagging 1 Mains Power Factor inductive 1
07.18 Mains PF lagging 2 Mains Power Factor inductive 2

9 Appendix
9.3.2.8 Group 08: Syst. related alarms
No. HMI Text Note
07.19 Mains PF leading 1 Mains Power Factor capacitive 1
07.20 Mains PF leading 2 Mains Power Factor capacitive 2
07.21 Mains import power 1 Mains import power threshold 1
07.22 Mains import power 2 Mains import power threshold 2
07.23 Mains export power 1 Mains export power threshold 1
07.24 Mains export power 2 Mains export power threshold 2
07.25 Mains decoupling Mains decoupling
07.27 Mains volt. incr. Mains slow voltage (10 minutes moving average)
07.28 Time-dep. voltage 1 Time-dependent voltage monitoring 1 (FRT)
07.29 QV monitoring 1 QV Monitoring step 1
07.30 QV monitoring 2 QV Monitoring step 2
07.32 Mains AC wiring Mains AC wiring plausibility
07.34 FRT ROCOF enable This flag is FALSE if any "Time-dependent voltage monitoring" (FRT) is initialized.
Otherwise it is TRUE.
It can be used to block temporary "Phase shift" and "df / dt" monitoring if FRT is
initialized. . (This is no alarm, only a LM.)
9.3.2.8 Group 08: Syst. related alarms
No. HMI Text Note
08.01 Bat. overvoltage 1 Battery over voltage threshold 1
08.02 Bat. overvoltage 2 Battery over voltage threshold 2
08.03 Bat. undervoltage 1 Battery under voltage threshold 1
08.04 Bat. undervoltage 2 Battery under voltage threshold 2
08.05 GCB fail to close GCB close not successful
08.06 GCB fail to open GCB open not successful
08.07 MCB fail to close MCB close not successful
08.08 MCB fail to open MCB open not successful
08.10 CAN fault J1939 CAN J1939 communication alarm
(Becomes true if at least one of the CVs 08.37-08.40 becomes true.)
08.16 Parameter alignment Parameter Alignment LDSS
08.17 Missing members Number of members mismatched
08.18 CANopen Interface 1 CANopen error interface 1
08.22 Busbar v / f not ok Busbar voltage or frequency is not ok.

9 Appendix
9.3.2.9 Group 09: Alarms discrete inputs
No. HMI Text Note
08.27 Missing easYgen At least one easYgen is missing.
08.30 Synchron. time GCB Timeout Synchronization GCB
08.31 Synchron. time MCB Timeout Synchronization MCB
08.37 J1939 ECU timeout CAN J1939 ECU timeout
08.38 J1939 dev. 1 timeout CAN J1939 device 1 timeout
08.43 Syst.update easYgen System update easYgen
There is an easYgen detected in the communication network which is not taught in
(A system update is required)
08.44 System update LSx System update LSx
There is a LSx detected in the communication network which is not taught in.
(A system update is required)
08.45 CPU overload R1 trip CPU overload R1 trip
(alarm class B, not selfackn.) becomes active if CPU overload is longer than 10s,
08.46 GCB failure 50BF GCB failure 50BF
08.47 MCB failure 50BF MCB failure 50BF
08.48 MCB plausibility MCB plausibility
08.50 Syst.upd.r / y twinkle System update red or yellow LED twinkling
Red twinkle: if there is no device recognized according to the last system update.
Yellow twinkle: if there is no device detected according to the last system update
on one redundant interface. (This is no alarm, only a LM.)
08.62 Ethernet issue Ethernet issue
(E.g. broadcast storm)
08.70 CAN1 EthA redundancy Load share interface redundancy CAN1 / Ethernet A lost
08.71 PV disconnect PV disconnect level under run
08.72 Modbus dev.1 timeout Modbus Master communication timeout device 1 (This is no alarm, only a LM.)
9.3.2.9 Group 09: Alarms discrete inputs

9 Appendix
9.3.2.10 Group 10: Alarms analog inputs
No. HMI Text Note
09.01 Discrete input 1
9.3.2.10 Group 10: Alarms analog inputs
No. HMI Text Note
10.01 AI 1 wire break Analogue Input 1 out of range
9.3.2.11 Group 11: Clock and timer
No. HMI Text Note
11.01 Timer 1 TRUE if Timer 1 overrun
11.02 Timer 2 TRUE if Timer 2 overrun
11.03 Active weekday TRUE if configured weekday is active.
11.04 Active day TRUE if configured day in month is active.
11.05 Active hour TRUE if configured hour is active.
11.06 Active minute TRUE if configured minute is active.
11.07 Active second TRUE if configured second is active.
11.08 Engine 1h Running hours 1h over (toggles every running hour)
11.09 Engine 10h Running hours 10h over (toggles every 10 running hours)
11.10 Engine 100h Running hours 100h over (toggles every 100 running hours)
9.3.2.12 Group 12: External discrete inputs

9 Appendix
9.3.2.13 Group 13: Discrete outputs (physical state)
No. HMI Text Note
12.1 External DI 1 External discrete input 1
9.3.2.13 Group 13: Discrete outputs (physical state)
TRUE if relay / transitor is energized
No. HMI Text Note
13.01 Discrete output 1 Relay 1 (ready for operation)

9 Appendix
9.3.2.14 Group 15: Flexible limits
No. HMI Text Note
13.02 Discrete output 2 Relay 2
9.3.2.14 Group 15: Flexible limits
No. HMI Text Note
15.01 Flexible limit 1

9 Appendix
9.3.2.15 Group 16: Free alarms latched
No. HMI Text Note
9.3.2.15 Group 16: Free alarms latched
No. HMI Text Note
16.01 Free alarm latch 1

9 Appendix
9.3.2.16 Group 17: System alarms
No. HMI Text Note
9.3.2.16 Group 17: System alarms
No. HMI Text Note
17.01 Act. load shar.mism. Monitor Active load share mismatch
17.02 React.load shar.mism Monitor Reactive load share mismatch
17.05 Missing member 4105 Missing member 4105
17.06 Para.alignment 4105 Parameter alignment VDE 4105
17.07 Meas.difference 4105 Meas.difference VDE 4105
17.08 Decoupling GCB < - > Tripping according to parameter 3110.

MCB
17.09 N-cont. reply mism. Neutral interlocking reply mismatch
9.3.2.17 Group 25: External analog inputs out of range
TRUE, if "out of range" or "wire break" of the external analog input is detected. (Only if
this function is supported by the external device.)
No. HMI Text Note
25.01 Ext AI 1 wire break

9 Appendix
9.3.2.18 Group 32: CAN1 Receive PDO1
Bits of CAN RPDO1 WORD 1 (ID 3371)
No. HMI Text Note
32.01 CAN1 RPDO1.1.1 CAN1 RPDO1 Word1 Bit1
No. HMI Text Note

9 Appendix
No. HMI Text Note
No. HMI Text Note
No. HMI Text Note

9 Appendix
No. HMI Text Note
No. HMI Text Note
9.3.2.23 Group 54: Modbus Master flags
TRUE if the flag is active
No. HMI Text Note
54.01 Mapped LM flag 1 Modbus Master mapped flag 1

9 Appendix
No. HMI Text Note

9 Appendix
No. HMI Text Note

9 Appendix
9.3.2.24 Group 81: AnalogManager boolean results 1
No. HMI Text Note
9.3.2.24 Group 81: AnalogManager boolean results 1
TRUE if the boolean result of the corresponding AnalogManager equation is true.
No. HMI Text Note
81.01 AM Preglow criterion AM Preglow criterion
81.02 AM Warm-up criterion AM Engine Warm-up criterion
81.03 AM Freq.source SP1 AM Frequency setpoint 1 source
81.04 AM Freq.source SP2 AM Frequency setpoint 2 source
81.05 AM Pwr.source SP1 AM Active power setpoint 1 source
81.09 AM Volt.source SP1 AM Voltage setpoint 1 source
81.10 AM Volt.source SP2 AM Voltage setpoint 2 source
81.11 AM RPwr.source SP1 AM Reactive power setpoint 1 source
81.12 AM RPwr.source SP2 AM Reactive power setpoint 2 source
81.13 AM PID1 setpoint AM PID 1 control setpoint
81.14 AM PID1 actual value AM PID 1 control actual value

9 Appendix
9.3.2.25 Group 82: AnalogManager boolean results 2 (Flexible Limits)
No. HMI Text Note
81.19 AM Ext.mains power AM External measured mains active power
81.20 AM Ext.mains RPower AM External measured mains reactive power
81.21 AM Derating source AM Free derating source
81.22 AM ECU seq.A_IN_1 AM ECU sequencer analog input 1
81.23 AM ECU seq.A_IN_2 AM ECU sequencer analog input 2
81.24 AM Engine speed AM Engine speed
81.25 AM Engine oil press. AM Engine oil pressure
81.26 AM Engine hours AM Engine hours
81.27 AM Engine fuel level AM Engine fuel level
81.28 AM Engine batt.volt. AM Engine battery voltage
81.29 AM Engine coolant T AM Engine coolant water temperature
81.30 AM Consumer load kW AM Consumer load [kW]
81.31 AM Reference VQ0 AM Reference VQ0
81.32 AM Q / P ref. offset AM Q / P reference offset
9.3.2.25 Group 82: AnalogManager boolean results 2 (Flexible Limits)
No. HMI Text Note
82.01 AM Flexible limit 1 AM Monitored flexible limit 1

9 Appendix
9.3.2.26 Group 86: LM Results 1
No. HMI Text Note
TRUE if the result of the corresponding LogicsManager equation is true.
No. HMI Text Note
86.09 LM: Start req in AUTO LM Start request in automatic mode
86.10 LM: Stop req. in AUTO LM Stop request in automatic mode
86.11 LM: Inhibit emerg.run LM Inhibit or interrupt emergency run
86.12 LM: Undelay close GCB LM Undelayed close GCB
86.13 LM: LS interf. EthA LM Load share interface Ethernet A
86.14 LM: Constant idle run LM Constant Idle Run is requested
86.15 LM: Ext. acknowledge LM External acknowledge
86.16 LM: Operat. mode AUTO LM External "Set mode Auto"
86.81 LM: Setpoint 2 freq. LM Setpoint 2 Frequency
86.82 LM: Setp. 2 load LM Setpoint 2 Active Power

9 Appendix
No. HMI Text Note
86.83 LM: Setp. 2 voltage LM Setpoint 2 Voltage
86.84 LM: Setp. 2 pwr.factor LM Setpoint 2 Reactive Power
86.85 LM: Enable MCB LM Enable MCB
86.86 LM: LDSS enabled LM activate load dependend start stop
86.87 LM: Segment no.2 act. LM set group / node number to 2 for load share
86.90 LM: LDSS Priority 2 LM load dependend start / stop priority 2
86.93 LM: Transition mode 1 LM Breaker Transition Mode Alternative 1
86.94 LM: Transition mode 2 LM Breaker Transition Mode Alternative 2
86.96 LM: Release f-control LM Release Frequency control
86.97 LM: Release V-control LM Release Voltage control
86.98 LM: P-control active LM Active power control active
86.99 LM: Q-control active LM React.power control active
No. HMI Text Note
87.17 LM: PID1 ctrl.release LM Free PID 1 Control Release
87.31 LM: Enable Mns dec. LM Enable Mains Decoupling
87.46 LM: GCB open in MAN LM Open GCB in Manual
87.47 LM: GCB close in MAN LM Close GCB in Manual
87.48 LM: MCB open in MAN LM Open MCB in Manual
87.49 LM: MCB close in MAN LM Close MCB in Manual
87.50 LM: MAN engine start LM Start Engine in Manual
87.59 LM: MAN engine stop LM Stop Engine in Manual
87.60 LM: Free derating LM Enable freely derating
87.66 LM: Inhibit cranking LM: Inhibit cranking
87.68 LM: Firing speed LM Firing speed detection
87.69 LM: Speed detected LM Speed detection
87.70 LM: Release eng.mon. LM Release engine monitoring
87.71 LM: Release cyl.temp. LM Release cylinder temperature deviation monitoring

9 Appendix
No. HMI Text Note
87.72 LM: Disable mns. mon. LM Disable mains monitoring
87.73 LM: Mains decoupl.MCB LM Mains decoupling MCB
87.74 LM: Inh.dead bus GCB LM Inhibit dead bus GCB
87.76 LM: Disable load ramp LM Disable load control ramp
87.77 LM: 2nd load SP ramp LM Enable 2nd load setpoint ramp
87.78 LM: 2nd frequency PID LM Enable 2nd Frequency PID
87.79 LM: 3rd load SP ramp LM Enable 3rd load setpoint ramp
87.80 LM: Rel. PV regulated LM Release PV load regulation
No. HMI Text Note
88.01 LM: Free alarm 1 LM Free alarm 1 active
9.3.2.29 Group 90: AnalogManager Internal values 0
No. HMI Text Note
90.01 AM customer screen 1.1 AM Customer screen 1 row 1

9 Appendix
No. HMI Text Note
No. HMI Text Note
91.01 AM Internal value 1

9 Appendix
9.3.2.31 Group 93: AnalogManager Analog outputs 1
9.3.2.31 Group 93: AnalogManager Analog outputs 1
No. HMI Text Note
93.01 AM Data source AO1 AM Analog output 1 data source
93.02 AM Data source AO2 AM Analog output 2 data source
93.21 AM Data s. ext. AO1 AM External Analog output 1 data source
9.3.2.32 Group 96: LM Internal flags 1
No. HMI Text Note
96.01 LM: Flag 1 LM Internal flag 1

9 Appendix
9.3.2.33 Group 98: LM External DOs 1
No. HMI Text Note
9.3.2.33 Group 98: LM External DOs 1
No. HMI Text Note
98.01 LM: External DO 1

9 Appendix
9.3.2.34 Group 99: LM Internal DOs 1
No. HMI Text Note
9.3.2.34 Group 99: LM Internal DOs 1
No. HMI Text Note
99.01 LM: Ready for op. OFF LM Relay 1 ready for operation
(This flag has negative logic: if the LM flag is true, the relay is not energized.)
99.02 LM: Relay 2
99.03 LM: Relay 3
99.04 LM: Relay 4
99.05 LM: Relay 5
99.06 LM: Relay 6
99.07 LM: Relay 7
99.08 LM: Relay 8
99.09 LM: Relay 9
99.10 LM: Relay 10
99.11 LM: Relay 11
99.12 LM: Relay 12
9.3.3 Logical Symbols
The following symbols are used for the graphical programming of the LogicsManager. The
easYgen displays symbols according to the IEC standard by default.
• Use parameter ╚═▷ 4117 to change display mode to ASA standard.

9 Appendix
9.3.3 Logical Symbols
Fig. 354: Logical symbols
Row ... according to standard:
A easYgen (default: IEC)
B DIN 40 700
C ASA
US MIL (configurable)
D IEC617-12
Meaning of the columns
1 2 3 4 5 6
AND OR NAND NOR NXOR XOR
AND OR NAND NOR NXOR XOR
x1 x2 y x1 x2 y x1 x2 y x1 x2 y x1 x2 y x1 x2 y
0 0 0 0 0 0 0 0 1 0 0 1 0 0 1 0 0 0
0 1 0 0 1 1 0 1 1 0 1 0 0 1 0 0 1 1
1 0 0 1 0 1 1 0 1 1 0 0 1 0 0 1 0 1
1 1 1 1 1 1 1 1 0 1 1 0 1 1 1 1 1 0
Tab. 134: Truth table

9 Appendix
9.3.4 Logical Outputs
The logical outputs or combinations may be grouped into three categories:
• Internal logical flags
• Internal functions
• Relay outputs
The numbers of the logical outputs in the third column may again be used as input
variable for other outputs in the LogicsManager.
Internal flags
32 internal logical flags may be programmed to activate/deactivate functions. This

permits more than 3 commands to be included in a logical function. They may be used
like "auxiliary flags".
Name Function Number ID
LM: Flag 1 Internal flag 1 96.01 10700

9 Appendix
Internal functions
The following logical functions may be used to activate/deactivate functions.
LM: Start req in AUTO Start in AUTOMATIC operating mode (parameter ╚═▷ 12120) 86.09 10708
LM: Stop req. in AUTO Stop in AUTOMATIC operating mode (parameter ╚═▷ 12190) 86.10 10709
LM: Inhibit emerg.run Blocking or interruption of an emergency power operating in 86.11 10710
AUTOMATIC operating mode (parameter ╚═▷ 12200)
LM: Undelay close Immediately closing of the GCB after engine start without waiting for the 86.12 10711
GCB engine delayed monitoring and generator stable timer to expire
LM: LS interf. EthA Enables to switch load share interface between CAN and Ethernet A 86.13 11987
LM: Constant idle run Enables idle/rated speed modes (parameter ╚═▷ 12550). 86.14 10713
LM: Ext. acknowledge The alarm acknowledgement is performed from an external source 86.15 10714
LM: Operat. mode Activation of the AUTOMATIC operating mode (parameter ╚═▷ 12510 ) 86.16 10715
AUTO
LM: Operat. mode Activation of the MANUAL operating mode (parameter ╚═▷ 12520) 86.17 10716
MAN
LM: Operat. mode Activation of the STOP operating mode (parameter ╚═▷ 12530) 86.18 10717
STOP
LM: Start w/o load Starting the engine without closing the GCB (parameter ╚═▷ 12540) 86.19 10718
LM: Auto idle mode Automatic idle mode (blocks the undervoltage, underfrequency, and 86.20 10719
underspeed monitoring for a configured time automatically,
parameter ╚═▷ 12570)
LM: Discrete f/P + Raise frequency / real power setpoint (parameter ╚═▷ 12900) 86.21 11600
LM: Discrete f/P - Lower frequency / real power setpoint (parameter ╚═▷ 12901) 86.22 11601
LM: Discrete V/PF + Raise voltage / power factor setpoint (parameter ╚═▷ 12902) 86.23 11602
LM: Discrete V/PF - Lower voltage / power factor setpoint (parameter ╚═▷ 12903) 86.24 11603
LM: Freq. droop act. Activation of the frequency droop (parameter ╚═▷ 12904) 86.25 11604
LM: Volt. droop act. Activation of the voltage droop (parameter ╚═▷ 12905) 86.26 11605
LM: Ext. mns.decoupl. Activation of the mains decoupling function (parameter ╚═▷ 12922) 86.27 11606
LM: Critical mode Activation of critical mode operation (parameter ╚═▷ 12220) 86.28 11607

9 Appendix
LM: Operat. mode Activation of the TEST operating mode (parameter ╚═▷ 12271) 86.29 12272
TEST
LM: Lock keypad 1 Activation of the Lock keypad 1 (parameter ╚═▷ 12978) 86.30 11924
LM: ECU seq. B_IN_1 Activation of a special ECU function (parameter ╚═▷ 15164) depending 86.31 11647
on the selected ECU
LM: ECU seq. B_IN_2 Activation of a special ECU function (parameter ╚═▷ 15165) depending 86.32 11648
on the selected ECU
LM: 2nd disp.bright. Enabling of the 2nd display brightness (parameter ╚═▷ 7794) 86.33 11971
LM: Enable heater Enabling of the front foil heater (parameter ╚═▷ 7799) 86.34 11972
LM: Syst. update Trigger system update (parameter ╚═▷ 7801) 86.35 11974
LM: Syn. mode Activation of CHECK synchronization mode (parameter ╚═▷ 12906) 86.38 11617
CHECK
LM: Syn. mode Activation of PERMISSIVE synchronization mode (parameter ╚═▷ 12907) 86.39 11618
PERMIS.
LM: Syn. mode RUN Activation of RUN synchronization mode (parameter ╚═▷ 12908) edge 86.40 11619
controlled
LM: IOP Res.power 2 Select IOP Reserve power 2 (parameter ╚═▷ 12604) 86.41 11975
LM: MOP Res.power 2 Select MOP Reserve power 2 (parameter ╚═▷ 12605) 86.42 11976
LM: RP Full mode Select remote panel full mode (parameter ╚═▷ 7857) 86.43 11994
LM: RP Annunciator Select remote panel annunciator mode (parameter ╚═▷ 7858) 86.44 11995
LM: RP Off mode Select remote panel off mode (parameter ╚═▷ 7859) 86.45 11996
LM: AVR V(f) enabled Enable AVR V(f) characteristic (only easYgen-3400XT and -3500XT) 86.46 10848
LM: Setpoint 2 freq. Activates the frequency setpoint 2 (parameter ╚═▷ 12918) 86.81 11910
LM: Setp. 2 load Activates the load setpoint 2 (parameter ╚═▷ 12919) 86.82 11911
LM: Setp. 2 voltage Activates the voltage setpoint 2 (parameter ╚═▷ 12920) 86.83 11912
LM: Setp.2 pwr.factor Activates the power factor setpoint 2 (parameter ╚═▷ 12921) 86.84 11913
LM: Enable MCB Enables the MCB (parameter ╚═▷ 12923) 86.85 11914
LM: LDSS enabled Activation of load-dependent start/stop (parameter ╚═▷ 12930) 86.86 11915
LM: Segment no.2 Assigns the genset to load share segm. #2 (parameter ╚═▷ 12929) 86.87 11916
act.
act.
act.
LM: LDSS Priority 2 Sets the LDSS priority to 2 (parameter ╚═▷ 12926) 86.90 11919
LM: Transition mode 1 Activates breaker transition mode 1 (parameter ╚═▷ 12931) 86.93 11922
LM: Transition mode 2 Activates breaker transition mode 2 (parameter ╚═▷ 12932) 86.94 11923
LM: Release f-control Release frequency control (parameter ╚═▷ 12909) 86.96 11925
LM: Release V-control Release voltage control (parameter ╚═▷ 12938) 86.97 11926
LM: P-control active Activates P-control (parameter ╚═▷ 12940) 86.98 11927

9 Appendix
LM: Q control active Activates Q-control (parameter ╚═▷ 12941) 86.99 11928
LM: PID1 ctrl.release Release PID1 control (parameter ╚═▷ 5580) 87.17 11406
Reserved 87.23
Reserved 87.24
Reserved 87.25
Reserved 87.26
Reserved 87.27
Reserved 87.28
Reserved 87.29
Reserved 87.30
LM: Enable Mns dec. Enables mains decoupling (parameter ╚═▷ 12942) 87.31 11420
LM: GCB open in MAN Opens GCB in manual (parameter ╚═▷ 12976) 87.46 11435
LM: GCB close in MAN Closes GCB in manual (parameter ╚═▷ 12977) 87.47 11436
LM: MCB open in MAN Opens MCB in manual (parameter ╚═▷ 12974) 87.48 11437
LM: MCB close in MAN Closes MCB in manual (parameter ╚═▷ 12975) 87.49 11438
LM: MAN engine start Starts the engine in manual (parameter ╚═▷ 12970) 87.50 11439
LM: MAN engine stop Stops the engine in manual (parameter ╚═▷ 12971) 87.59 11448
LM: Free derating Activates free derating (parameter ╚═▷ 15146) 87.60 11449
Reserved 87.61
Reserved 87.62
LM: Inhibit cranking Inhibits cranking (parameter ╚═▷ 4871) 87.66 11455
LM: Firing speed Activate firing speed detected flag (parameter ╚═▷ 12951) 87.68 11457
LM: Speed detected Activate speed detected flag (parameter ╚═▷ 12989) 87.69 11458
LM: Release eng.mon. Release engine monitoring (parameter ╚═▷ 12999) 87.70 11459
LM: Release cyl.temp. Release cylinder temperature deviation monitoring (parameter ╚═▷ 87.71 11460
15158)
LM: Disable mns.mon. Disables mains monitoring (parameter ╚═▷ 15159) 87.72 11461
LM: Mains Enables mains decoupling via MCB (parameter ╚═▷ 15160) 87.73 11462
decoupl.MCB
LM: Inh.dead bus GCB Inhibit dead bus closure GCB (parameter ╚═▷ 15161) 87.74 11463
LM: Disable load Disable load setpoint ramp (parameter ╚═▷ 12853) 87.76 11465
ramp
LM: 2nd load SP ramp Select 2nd load control setpoint ramp (parameter ╚═▷ 11978) 87.77 11979
LM: 3rd load SP ramp Select 3rd load control setpoint ramp (parameter ╚═▷ 11998) 87.79 11999
LM: PV regulation Release PV regulation (parameter ╚═▷ 8928) 87.80 8929

9 Appendix
LM: Free alarm 1 Select source of free alarm 1 (parameter ╚═▷ 8120) 88.01 11550
Priority hierarchy of the logical outputs
The following table contains the priority relationships between the start conditions of the
logical outputs in the LogicsManager:
Prioritized function Overrides Reaction
Critical mode Stop req. in Auto A start will still be performed.
Start req. in Auto The behavior of the system depends on the configuration of
the related parameters.
Stop req. in Auto Start req. in Auto No start will be performed.
Emergency power No start will be performed.
Idle mode No start will be performed.
Start w/o load Start req. in Auto The GCB remains open / will be opened.
Emergency power Start w/o load The GCB will be closed nevertheless.
Critical mode The GCB will be closed nevertheless. The alarm class
management is still performed like for the critical mode. If
emergency power is already enabled and the critical mode
will be enabled then, a pause time may be configured for
the emergency power operation.
Inhibit emergency run Emergency power No start will be performed.
Emergency power during The generator keeps on running without taking over load.
Start w/o load
Relay outputs
All relays may be controlled directly by the LogicsManager depending on the respective
application mode.

9 Appendix
Name LM: Function Number ID
Relay 1 If this logical output becomes true, the relay output 1 will 99.01 11870
be activated
(Ready for
operation OFF)
be activated
be activated
be activated
be activated
be activated
be activated
be activated
be activated
be activated
be activated
be activated
External DO 1 If this logical output becomes true, the external relay 98.01 11892
output 1 will be activated

9 Appendix
Relay Application mode (parameter ╚═▷ 3444)
No. Term. None A01 GCB open A02 GCB A03 GCB/MCB A04
Internal relay outputs, board #1
[R 01] 41/42 'Ready for operation'; additionally programmable with LogicsManager

9 Appendix
9.3.5 Factory Settings
Relay Application mode (parameter ╚═▷ 3444)
No. Term. None A01 GCB open A02 GCB A03 GCB/MCB A04
CAUTION! Only relay [R 01] has an inverse logic. The relay opens (all other
relays close), if the logical output of the LogicsManager becomes TRUE.
[R 02] 43/46 LogicsManager; pre-assigned with 'Centralized alarm (horn)'
[R 03] 44/46 LogicsManager; pre-assigned with 'Starter'
[R 04] 45/46 LogicsManager; pre-assigned with 'Diesel: Fuel solenoid, Gas: Gas valve'
[R 05] 47/48 LogicsManager; pre-assigned with 'Diesel: Preglow, Gas: Ignition'
[R 06] 49/50 LogicsManager Command: close GCB
[R 07] 51/52 LogicsManager Command: open GCB
[R 08] 53/54 LogicsManager Command: close

MCB
[R 09] 55/56 LogicsManager Command: open

MCB
[R 10] 57/60 LogicsManager; pre-assigned with 'Auxiliary services'
[R 11] 58/60 LogicsManager; pre-assigned with 'Alarm class A, B active'
[R 12] 59/60 LogicsManager; pre-assigned with 'Alarm class C, D, E, F active'
LogicsManager's default definition
ID Name Function
4871 Inhibit cranking (02.01 LM FALSE And True) And True
5580 PID1 ctrl.release (False And True) And True
7794 Enable 2nd display brightness (Not 04.64 Key activation And True) And True
7799 Enable front foil heater (True And True) And True
7801 System update (False And True) And True
7857 RP Full mode (02.01 LM FALSE And True) And True
7858 RP Annunciator (02.01 LM FALSE And True) And True
7859 RP Off mode (02.01 LM FALSE And True) And True
8120 Free alarm 1 (02.01 LM FALSE And True) And True

9 Appendix
ID Name Function
8928 Release PV regulation (False And True) And True
11978 2nd load control setpoint ramp (False And 02.02 LM TRUE) And 02.02 LM TRUE
11986 LS interface Ethernet A (02.01 LM FALSE And True) And True
11988 3rd load control setpoint ramp (02.01 LM FALSE And True) And True
12037 Reserved
12110 Relay 2 (03.05 Horn And True) And True
12120 Start req in AUTO (09.02 Discrete input 2 Or False) Or 04.13 Remote request
12130 Relay 5 (03.04 Preglow / Ignition And True) And True
12140 Relay 6 (False And True) And True
12180 Relay 10 (03.01 Auxiliary services And True) And True
12190 Stop req. in AUTO (False And True) And True
12200 Inhibit emerg.run (False And True) And True
12210 Undelay close GCB (04.09 Emergency mode And True) And True
12220 Critical mode (False And Not 05.08 Start fail) And Not 09.01 Discrete input 1
12230 Flag 1 (02.01 LM FALSE And True) And True

9 Appendix
ID Name Function
12269 Setp. 4 load (False And True) And True
12271 Operat. mode TEST (False And True) And True
12310 Relay 3 (03.02 Starter And True) And True
12320 Relay 4 (03.28 Start/Gas And True) And True
12330 External DO 1 (False And True) And True

9 Appendix
ID Name Function
12490 Ext. acknowledge (09.05 Discrete input 5 And True) Or 04.14 Remote acknowledge
12510 Operat. mode AUTO (False And True) And True
12520 Operat. mode MAN (False And True) And True
12530 Operat. mode STOP (False And True) And True
12540 Start w/o load (False And True) And True
12540 Start w/o load (False And True) And True
12550 Constant idle run (False And True) And True
12560 Relay 11 (01.08 Warning alarm And True) And True
12570 Auto idle mode (False And True) And True
12580 Ready for op. OFF (False And False) And True
12590 Relay 12 (01.09 Shutdown alarm And True) And True
12604 IOP Reserve power 2 (False And True) And True
12605 MOP Reserve power 2 (False And True) And True
12853 Disable load setpoint ramp (02.01 LM FALSE And True) And True
12900 Discrete f/P + (False And True) And True
12901 Discrete f/P - (False And True) And True
12902 Discrete V/PF + (False And True) And True
12903 Discrete V/PF - (False And True) And True
12904 Freq. droop act. (08.17 Missing members Or 08.06 GCB fail to open) And True
12905 Volt. droop act. (08.17 Missing members Or 08.06 GCB fail to open) And True
12906 Syn. mode CHECK (False And True) And True
12907 Syn. mode PERMIS. (False And True) And True
12908 Syn. mode RUN (False And True) And True
12909 Release f-control (True And True) And True

9 Appendix
ID Name Function
12918 Setpoint 2 freq. (False And True) And True
12920 Setp. 2 voltage (False And True) And True
12921 Setp.2 pwr.factor (False And True) And True
12922 Ext. mns.decoupl. (False And True) And True
12923 Enable MCB (09.06 Discrete input 6 And Not 08.07 MCB fail to close) And Not
07.05 Mns.ph.rot. mismatch
12924 LDSS Priority 4 (02.01 LM FALSE And True) And True
12927 Segment no.4 act. (02.01 LM FALSE And True) And True
12930 LD start stop (False And True) And True
12931 Transition mode 1 (False And True) And True
12932 Transition mode 2 (False And True) And True
12936 Reserved
12937 Reserved
12938 Release V-control (True And True) And True
12940 P control (04.07 MCB closed And 04.06 GCB closed) And True
12941 Q control (04.07 MCB closed And 04.06 GCB closed) And True
12942 Enable mains decoupl. (02.02 LM TRUE And True) And True
12951 Firing speed detection (02.34 Firing speed electr. Or 02.35 Firing speed rpm) And True
12970 MAN engine start (False And True) And True
12971 MAN engine stop (False And True) And True
12972 Reserved
12973 Reserved
12974 MCB open in MAN (False And True) And True
12975 MCB close in MAN (False And True) And True
12976 GCB open in MAN (False And True) And True
12977 GCB close in MAN (False And True) And True
12978 Lock keypad 1 (False And True) And True
12979 Reserved
12980 Reserved
12981 Reserved

9 Appendix
ID Name Function
12982 Reserved
12983 Reserved
12984 Reserved
12989 Speed detection (02.36 Speed electr. Or 02.37 Speed rpm) And True
12990 2nd Frequency PID (False And True) And True
12999 Release eng.mon. (02.34 Firing speed electr. Or 02.35 Firing speed rpm) And 03.28
Start/Gas
15026 LDSS with predicted load (False And True) And True
15146 Free derating (02.01 LM FALSE And True) And True
15158 Release cyl.temp. (02.01 LM FALSE And True) And True
15159 Disable mns.mon. (False And True) And True
15160 Mains decoupl.MCB (False And True) And True
15161 Inh.dead bus GCB (False And True) And True
15164 ECU seq. B_IN_1 (False And True) And True
15165 ECU seq. B_IN_2 (False And True) And True
Tab. 135: Factory settings by ID: LogicsManager
Relay outputs
Simple (function) Extended (configuration) Result
[99.01] Relay 1 [R01] - Ready for FALSE

operation OFF
Relay will be de-energized if unit is not

ready for operation or the logics manager
output is TRUE.
Deactivated by default
Note: This function is pre-configured and

may be activated by passing through the
command variables [01.09] Shutdown
alarm or [04.01] Operating mode AUTO or
[00.01] LM: Flag 1 ('―' instead of '0').
The unit is only ready for operation after an

start-up delay following the power supply
connection.
[99.02] Relay 2 [R02] - Centralized dependent

alarm (horn) / freely configurable on Logics
Command
Relay energizes if the internal condition Variable
"Horn" is TRUE [03.05]

9 Appendix
[99.03] Relay 3 [R03] - Starter / freely dependent

configurable on Logics
Command
"Starter" is TRUE [03.02]
[99.04] Relay 4 [R04] - Start/Gas / dependent

freely configurable on Logics
Command
"Start/Gas" is TRUE to energize the start [03.28]
(Diesel) or gas (Gas) solenoid
[99.05] Relay 5 [R05] - Preglow/ dependent

Ignition / freely configurable on Logics
Command
"Preglow/Ignition" is TRUE to preglow the [03.04]
Diesel engine or enabling the ignition of the
gas engine
[99.06] Relay 6 [R06] - Free / FALSE

Command: close GCB
In application mode
A01 and A02 = freely configurable relay

(unassigned)
In application mode A03 to A13

"Command: close GCB"
[99.07] Relay 7 [R07] - Mains dependent

decoupling / freely configurable / on
Command: open GCB application
mode and
In application mode A01 pre-configured to Logics
mains decoupling. Relay energizes if the Command
internal condition "Mains decoupling" is Variable
TRUE to decouple the genset from the [07.25]
mains.
In application mode A02 to A13

"Command: open GCB"
[99.08] Relay 8 [R08] - Free / FALSE

Command: close MCB
In application mode A01 , A02 , A03 , A05 ,

A07 , A08 , A09 , A10 and A11 to A13
freely configurable relay (unassigned)
In application mode A04 and A06

"Command: close MCB"

9 Appendix
[99.09] Relay 9 [R09] - Mains dependent

decoupling / freely configurable / on
Command: open MCB application
mode and
In application mode A01 , A02 , A03 , A05 , Logics
A07 , A08 , A09 , A10 and A11 to A13 pre- Command
configured to mains decoupling. Relay Variable
energizes if the internal condition "Mains [07.25]
decoupling" is TRUE to decouple the genset
from the mains.
In application mode A04 and A06

"Command: open MCB"
[99.10] Relay 10 [R10] - Auxiliary dependent

services / freely configurable on Logics
Command
In application mode A01 , A02 , A03 , A04 , Variable
A07 , A08 , A10 and A11 to A13 pre- [03.01]
configured to auxiliary services. Relay
energizes if the internal condition "Aux.
services" is TRUE to activate the auxiliary
services (it energizes prior to an engine
start and de-energizes with the engine
stop)
In application mode A05 , A06 and A09

"Command: close GGB"
[99.11] Relay 11 [R11] - Warning alarm dependent

class active / freely configurable on Logics
Command
In application mode A01 , A02 , A03 , A04 , Variable
A07 , A08 , A10 and A11 to A13 pre- [01.08]
configured to alarm class A or B. Relay
energizes if one of the alarm classes A or B
is active
In application mode A05 , A06 and A09

"Command: open GGB"
[99.12] Relay 12 [R12] - Shutdown dependent

alarm class active / freely configurable on Logics
Command
Relay energizes if one of the alarm classes Variable
C, D, E or F is active [01.09]
[98.xx] External discrete output {y} - FALSE

{xx} = 01 to 32 ; {y} = 1 to 32)
Control of the external relay {y}, if this is

connected
Prepared for:

9 Appendix
9.4 AnalogManager Reference
[98.xx] External discrete output {y} - FALSE

Free (external expansion card, if
connected; {xx} = 01 to 16 ; {y} = 17
to 32).
Control of the external relay {y}, if this is

connected
Prepared for:
Discrete inputs
Number LM ID Alarm class Pre-assigned to
DI 01 09.01 10900 F freely EMERGENCY STOP

configurable
DI 02 09.02 10901 CONTROL freely LogicsManager Start in AUTO

configurable
DI 03 09.03 10902 B freely Low oil pressure

configurable
DI 04 09.04 10903 B freely Coolant temperature

configurable
DI 05 09.05 10904 CONTROL freely LogicsManager External

configurable acknowledgment
DI 06 09.06 10905 CONTROL freely LogicsManager Enable MCB

configurable
DI 07 09.07 10906 fixed Reply MCB
DI 08 09.08 10907 fixed Reply GCB
DI 09 09.09 10908 B freely unassigned

configurable

configurable

configurable

configurable
9.4 AnalogManager Reference
9.4.1 AnalogManager Overview
To enhance flexibility of programming the functions of the easYgen-3000XT series, an

AnalogManager is used.
All analog values may be used as data sources for the analog outputs (refer to ╚═▷
“4.4.2.5 Analog Outputs”), the flexible limit monitoring (refer to ╚═▷ “4.5.5 Flexible
Limits”), and the controller setpoints (refer to ╚═▷ “4.4.4 Configure Controller”).

9 Appendix
9.4.2 Data Sources AM
• Every data source is indicated by a group number and a sub-number.

• Some values are percentage values and relate to reference values.
AnalogManager Variables
Groups 1 to 79 make available even more than the already arranged analog variables out
of the easYgen system.
AnalogManager Results
Cascading: Use analog results
This analog results of an AnalogManager is available as AnalogManager input

additionally. Like the other AnalogManager inputs they can be used as input signal for
(further) AnalogManagers.
The groups 80.xx to 89.xx contain analog outputs (results) of function-related

AnalogManagers.
The description/name of these analog variables starts always with 'AM ...'.
'Internal'/Fixed AnalogManager Values
The groups 90.xx to 99.xx contain analog outputs of fixed AnalogManagers.
The description/name of these analog variables starts always with 'AM ...'.
9.4.2 Data Sources AM
9.4.2.1 Group 01: Generator values
The percentage value is related on the following values:
• generator rated voltage
• system rated frequency
• generator rated current
• power factor 1
• generator rated active power
• generator rated reactive power
• generator rated active and generator rated reactive power
No. HMI Text Note
01.01 Gen.volt.L-N [%] Generator voltage wye average
01.02 Gen.volt.L1-N [%] Generator voltage L1-N

9 Appendix
9.4.2.1 Group 01: Generator values
No. HMI Text Note
01.05 Gen.volt.L-L [%] Generator voltage delta average
01.06 Gen.volt.L1-L2 [%] Generator voltage L1-L2
01.09 Gen.frequency [%] Generator frequency
01.10 Gen.freq.L1-L2 [%] Generator frequency L1-L2
01.13 Gen.current [%] Generator average current
01.14 Gen.current L1 [%] Generator current L1
01.17 Gen.curr.max. L1 [%] Dragged generator current L1
01.20 Gen. PF [%] Generator power factor
01.21 Gen. PF L1 [%] Generator power factor L1
01.24 Gen. act. power [%] Total generator active power
01.25 Gen.act.pwr. L1 [%] Generator active power L1-N
01.28 Gen.react.pwr. [%] Total generator reactive power
01.29 Gen.react.pwr.L1 [%] Generator reactive power L1-N
01.32 Gen.app.power [%] Total generator apparent power
01.33 Gen.app.pwr. L1 [%] Generator apparent power L1-N
01.37 Gen.ext.act.pwr. [%] Generator external measured active power by AI
01.51 Gen.volt.L-N [V] Generator voltage wye average
01.52 Gen.volt.L1-N [V] Generator voltage L1-N
01.55 Gen.volt.L-L [V] Generator voltage delta average

9 Appendix
9.4.2.2 Group 02: Mains values
No. HMI Text Note
01.56 Gen.volt.L1-L2 [V] Generator voltage L1-L2
01.59 Gen.frequency [Hz] Generator frequency
01.60 Gen.freq.L1-L2 [Hz] Generator frequency L1-L2
01.63 Gen.current [A] Generator average current
01.64 Gen.current L1 [A] Generator current L1
01.67 Gen.curr.max. L1 [A] Dragged generator current L1
01.70 Gen. PF Generator power factor
01.71 Gen. PF L1 Generator power factor L1
01.74 Gen. act. power [W] Total Generator active power
01.75 Gen.act.pwr. L1 [W] Generator active power L1-N
01.78 Gen. react.pwr. [var] Total generator reactive power
01.79 Gen.react.pwr.L1[var] Generator reactive power L1-N
01.82 Gen.app.power [VA] Total generator apparent power
01.83 Gen.app.pwr. L1 [VA] Generator apparent power L1-N
01.86 Number pole slip Actual number of pole slip events for the analog manager.
• mains rated voltage

9 Appendix
• mains rated current
• power factor 1
• mains rated active power
• mains rated reactive power
• mains rated active and mains rated reactive power
No. HMI Text Note
02.01 Mains volt.L-N [%] Mains voltage wye average
02.02 Mains volt.L1-N [%] Mains voltage 1-N
02.05 Mains volt.L-L [%] Mains voltage delta average
02.06 Mains volt.L1-L2 [%] Mains voltage 1-2
02.09 Mains frequency [%] Mains frequency
02.10 Mains freq.L1-L2 [%] Mains frequency 1-2
02.13 Mains current [%] Mains average current
02.14 Mains current L1 [%] Mains current 1
02.17 Mns.curr.max.L1 [%] Dragged mains current 1
02.20 Mains PF [%] Mains power factor
02.21 Mains PF L1 [%] Mains power factor 1
02.24 Mains act. power [%] Total mains active power
02.25 Mns.act.pwr.L1 [%] Mains power 1-N
02.28 Mns.react. pwr. [%] Total mains reactive power
02.29 Mns.react.pwr.L1 [%] Mains reactive power 1-N
02.32 Mns.app.power [%] Total mains apparent power

9 Appendix
No. HMI Text Note
02.33 Mns.app.pwr.L1 [%] Mains apparent power 1-N
02.36 Mns.ext.act.pwr. [%] Mains external measured active power by AI
02.37 Mns.ext.react.pwr[%] Mains external measured reactive power by AI
02.38 Mains ext. PF [%] Mains calculated Power Factor by AI
02.40 Mains freq.200ms [%] Mains frequency average 200ms
02.51 Mains volt L-N [V] Mains voltage wye average
02.52 Mains volt L1-N [V] Mains voltage 1-N
02.55 Mains volt L-L [V] Mains voltage delta average
02.56 Mains volt L1-L2 [V] Mains voltage 1-2
02.59 Mains frequency [Hz] Mains frequency
02.60 Mains freq.L1-L2 [Hz] Mains frequency 1-2
02.63 Mains current [A] Mains average current
02.64 Mains current L1 [A] Mains current 1
02.67 Mns.curr.max.L1 [A] Mains dragged current 1
02.70 Mains PF Mains power factor
02.71 Mains PF L1 Mains power factor 1
02.74 Mains act. power [W] Total mains active power
02.75 Mns.act.pwr. L1 [W] Mains active power 1-N
02.78 Mns.react.pwr. [var] Total mains reactive power
02.79 Mns.react.pwr.L1[var] Mains reactive power 1-N

9 Appendix
9.4.2.3 Group 03: Busbar 1 values
No. HMI Text Note
02.82 Mns.app.power [VA] Total mains apparent power
02.83 Mns.app.pwr. L1 [VA] Mains apparent power 1-N
02.86 Mns.ext.act.pwr. [W] Mains external measured active power by AI
02.87 Mns.ext.reac.pwr[var] Mains external measured reactive power by AI
02.88 Mains ext. PF Mains calculated Power Factor by AI
02.89 Mains settl.time [s] Mains settling time
02.90 Mains freq.200ms [Hz] Mains frequency average 200ms
9.4.2.3 Group 03: Busbar 1 values
• busbar 1 rated voltage
No. HMI Text Note
03.01 Busb1 volt. L-L [%] Busbar 1: voltage delta average [%]
03.02 Busb1 volt.L1-L2 [%] Busbar 1: voltage L1-L2 [%]
03.05 Busb1 frequency [%] Busbar 1: frequency [%]
03.06 Busb1 freq.L1-L2 [%] Busbar 1: frequency L1-L2 [%]
03.51 Busb1 volt.L-L [V] Busbar 1: voltage delta average [V]
03.52 Busb1 volt.L1-L2 [V] Busbar 1: voltage L1-L2 [V]
03.55 Busb1 frequency [Hz] Busbar 1: frequency [Hz]
03.56 Busb1 freq.L1-L2 [Hz] Busbar 1: frequency L1-L2 [Hz]
9.4.2.4 Group 05: Controller setpoints
• generator rated voltage
• generator rated current
• power factor 1
• generator rated active power
• generator rated reactive power

9 Appendix
• generator rated active and generator rated reactive power
No. HMI Text Note
05.01 Internal f setp1 [%] Internal frequency setpoint 1
05.02 Internal f setp2 [%] Internal frequency setpoint 2
05.03 Interface f setp [%] Interface frequency setpoint
05.04 Internal P setp1 [%] Internal power setpoint 1
05.05 Internal P setp2 [%] Internal power setpiont 2
05.06 Interface P setp [%] Interface power setpoint
05.07 Internal v setp1 [%] Internal voltage setpoint 1
05.08 Internal v setp2 [%] Internal voltage setpoint 2
05.09 Interface v setp [%] Interface voltage setpoint
05.10 Intern. PF setp1 [%] Internal power factor setpoint 1
05.11 Intern. PF setp2 [%] Internal power factor setpoint 2
05.12 Interface PF sp [%] Interface power factor setpoint
05.13 Discrete f + / - [%] Digital poti frequency
05.14 Discrete P + / - [%] Digital poti power
05.15 Discrete v + / - [%] Digital poti voltage
05.16 Discrete PF + / - [%] Digital poti power factor
05.17 Used f setp. [%] Used frequency setpoint
05.18 Used f setp.ramp [%] Used frequency setpoint ramp
05.19 Used P setp. [%] Used power setpoint
05.20 Used P setp.ramp [%] Used power setpoint ramp
05.21 Used v setp. [%] Used voltage setpoint
05.22 Used v setp.ramp [%] Used voltage setpoint ramp
05.23 Used PF setp [%] Used power factor setpoint
05.24 Used PF sp ramp [%] Used power factor setpoint ramp
05.28 P derating (f) [%] Generator acive power derating dependent on mains ferquency, value of reduction
05.29 PF characteristic % Power factor corresponding to characteristic
05.31 Int. kvar setp1 [%] Internal kvar setpoint 1
05.32 Int. kvar setp2 [%] Internal kvar setpoint 2
05.33 Interf. kvar sp [%] Interface kvar setpoint
05.35 F / P control setp [%] F / P controller setpoint
05.36 V / Q control setp [%] V / Q controller setpoint
05.37 Manual f setp. [%] Manual setpoint frequency
05.38 Manual P setp. [%] Manual setpoint real power
05.39 Manual V setp. [%] Manual setpoint voltage
05.40 Manual PF setp. [%] Manual setpoint power factor

9 Appendix
No. HMI Text Note
05.41 Used kvar setp. [%] Used kvar setpoint
05.42 Used kvar setp.ramp [%] Used kvar setpoint ramp
05.43 QV reference [%] Reactive power characteristic QV
05.44 QP reference [%] Reactive power characteristic QP
05.45 QV lim. reference [%] Reactive power characteristic QV limit
05.46 VQ0 reference Reactive power characteristic reference VQ0
05.47 Interface QP offset Offset to Q / P characteristic curve, received by interface
05.48 P uprating (f) [%] P uprating (F)
05.51 Internal f setp1 [Hz] Internal frequency setpoint 1
05.52 Internal f setp2 [Hz] Internal frequency setpoint 2
05.53 Interface f setp [Hz] Interface frequency setpoint
05.54 Internal P setp1 [kW] Internal power setpoint 1
05.56 Interface P setp [kW] Interface power setpoint
05.57 Internal v setp1 [V] Internal voltage setpoint 1
05.58 Internal v setp2 [V] Internal voltage setpoint 2
05.59 Interface v setp [V] Interface voltage setpoint
05.63 Discrete f + / - [Hz] Digital poti frequency
05.64 Discrete P + / - [kW] Digital poti power
05.65 Discrete v + / - [V] Digital poti voltage
05.67 Used f setp. [Hz] Used frequency setpoint
05.68 Used f setp.ramp [Hz] Used frequency setpoint ramp
05.69 Used P setp. [kW] Used power setpoint
05.70 Used P setp.ramp [kW] Used power setpoint ramp
05.71 Used v setp. [V] Used voltage setpoint
05.72 Used v setp.ramp [V] Used voltage setpoint ramp
05.75 Int. PID 1 setpoint Internal PID 1 setpoint
05.80 Internal P setp3 [W] Internal power setpoint 3
05.81 Int.kvar setp1 [kvar] Internal kvar setpoint 1
05.82 Int.kvar setp2 [kvar] Internal kvar setpoint 2
05.83 Interf.kvar sp [kvar] Interface kvar setpoint
05.87 Manual f setp. [Hz] Manual setpoint frequency
05.88 Manual P setp. [W] Manual setpoint real power
05.89 Manual V setp. [V] Manual setpoint voltage

9 Appendix
9.4.2.5 Group 06: DC analog inputs
No. HMI Text Note
05.91 Used kvar setp. [var] Used kvar setpoint
05.92 Used kvar setp.ramp Used kvar setpoint ramp

[var]
05.93 QV reference [var] Reactive power charateristic QV
05.94 QP reference [var] Reactive power charateristic QP
05.95 QV lim.reference [var] Reactive power charateristic QV limit
9.4.2.5 Group 06: DC analog inputs
No. HMI Text Note
06.01 Analog input 1 Analog input 1
9.4.2.6 Group 07: J1939 values 1
The leading number is the SPN number of the value.
No. HMI Text Note
07.01 52: Eng. Interc.Temp. 52: Engine Intercooler Temperature
07.02 91: Accel.Pedal Pos.1 91: Accelerator Pedal Position 1
07.03 92: Load at Speed 92: Load At Current Speed
07.04 94: Fuel Deliv.Press. 94: Fuel Delivery Pressure
07.05 95: Fuel Filt.Diff. Pr. 95: Fuel Filter Differential Pressure
07.06 98: Engine Oil Level 98: Engine Oil Level
07.07 100: Engine Oil Press. 100: Engine Oil Pressure
07.08 101: Crankcase Press. 101: Crankcase Pressure
07.09 102: Int.Manif.1 Pr. 102: Intake Manifold 1 Pressure
07.10 105: Int.Manif.1 Temp. 105: Intake Manifold 1 Temperature
07.11 106: Air Intake Press. 106: Turbo Air Inlet Pressure
07.12 107: Air Filt1 Diff.Pr 107: Air Filter 1 Differential Pressure
07.13 108: Barometric Press. 108: Barometric Pressure
07.14 109: Coolant Pressure 109: Coolant Pressure
07.15 110: Eng.Coolant Temp. 110: Engine Coolant Temperature
07.16 111: Coolant Level 111: Coolant Level
07.17 127: Transm.Oil Press. 127: Transmission Oil Pressure
07.18 157: Inj.Met.Rail1 Pr. 157: Injector Metering Rail 1 Pressure
07.19 171: Ambient Air Temp. 171: Ambient Air Temperature
07.20 172: Air Intake Temp. 172: Air Inlet Temperature

9 Appendix
9.4.2.6 Group 07: J1939 values 1
No. HMI Text Note
07.21 173: Exhaust Gas Temp. 173: Exhaust Gas Temperature
07.22 174: Fuel Temp. 1 174: Fuel Temperature 1
07.23 175: Oil Temperature 1 175: Engine Oil Temperature 1
07.24 176: Turbo Oil Temp. 176: Turbo Oil Temperature
07.25 177: Transm.Oil Temp.1 177: Transmission Oil Temperature 1
07.26 183: Fuel Rate 183: Fuel Rate
07.27 190: Engine Speed 190: Engine Speed
07.28 441: Auxiliary Temp.1 441: Auxiliary Temperature 1
07.29 442: Auxiliary Temp.2 442: Auxiliary Temperature 2
07.30 513: Actual Eng.Torque 513: Actual Engine Torque
07.31 1122: Altern.Bear.1 T 1122: Alternator Bearing 1 Temperature
07.32 1123: Altern.Bear.2 T 1123: Alternator Bearing 2 Temperature
07.33 1124: Altern.Wind.1 T 1124: Alternator Winding 1 Temperature
07.36 1131: Int.Manif.2 Temp 1131: Intake Manifold 2 Temperature
07.39 1134: Cooler Therm.Op. 1134: Engine Charge Air Cooler Thermostat Opening
07.40 1135: Oil Temp. 2 1135: Engine Oil Temperature 2
07.41 1136: ECU Temperature 1136: Engine ECU Temperature
07.42 1137: Exh.Gas P.1 Temp 1137: Exhaust Gas Port 1 Temperature
07.51 1146: Exh.Gas P.10 T 1146: Exhaust Gas Port 10 Temperature

9 Appendix
9.4.2.6 Group 07: J1939 values 1
No. HMI Text Note
07.62 1157: Main Bear.1 Temp 1157: Main Bearing 1 Temperature
07.71 1166: Main Bear.10 T 1166: Main Bearing 10 Temperature
07.72 1167: Main Bear.11 T 1167: Main Bearing 11 Temperature
07.73 1172: Tb1 Compr.Int.T 1172: Turbocharger 1 Compressor Intake Temperature
07.77 1176: Tb1 Compr.Int.Pr 1176: Turbocharger 1 Compressor Intake Pressure
07.81 1180: Turbo1 Int.Temp 1180: Turbocharger 1 Intake Temperature
07.85 1184: Turbo1 Outl.Temp 1184: Turbocharger 1 Outlet Temperature
07.89 1203: Aux.Coolant Pr. 1203: Engine Auxiliary Coolant Pressure
07.90 1208: Pre-filt.Oil Pr. 1208: Pre-filter Oil Pressure
07.91 1212: Aux.Coolant Temp 1212: Engine Auxiliary Coolant Temperature
07.92 1382: Fuel Filt.DiffPr 1382: Fuel Filter Differential Pressure
07.93 1800: Battery 1 Temp. 1800: Battery 1 Temperature
07.94 1801: Battery 2 Temp. 1801: Battery 2 Temperature

9 Appendix
9.4.2.7 Group 08: External analog inputs
No. HMI Text Note
07.97 2433: Right Exh.Gas T 2433: Right Exhaust Gas Temperature
07.98 2434: Left Exh.Gas T 2434: Left Exhaust Gas Temperature
07.99 2629: Tb1 Compr.Outl.T 2629: Turbocharger 1 Compressor Outlet Temperature
9.4.2.7 Group 08: External analog inputs
No. HMI Text Note
08.01 Ext. analog input 1 External analog input 1
9.4.2.8 Group 09: J1939 values 2
The leading number is the SPN number of the value.
No. HMI Text Note
09.01 3644: Derate Request 3644: Engine Derate Request
09.02 158: Keysw.Batt.Pot. 158: Keyswitch Battery Potential
09.03 4151: Exh.Gas T Avr. 4151: Exhaust Gas Temperature average
09.04 4153: Exh.Gas T Avr.B1 4153: Exhaust Gas Temperature average Bank 1
09.05 4152: Exh.Gas T Avr.B2 4152: Exhaust Gas Temperature average Bank 2
09.06 ECU seq. A_OUT_1 ECU sequencer analog output 1
09.07 ECU seq. A_OUT_2 ECU sequencer analog output 2
09.08 1761: Aft1Exh.Tank1Lev 1761: Aftertreatment 1 Diesel Exhaust Fluid Tank 1 Level
09.09 3031: Aft1 Exh.Tank1 T 3031: Aftertreatment 1 Diesel Exhaust Fluid Tank 1 Temperature
09.10 4367: Aft1Exh.Tank2Lev 4367: Aftertreatment 1 Diesel Exhaust Fluid Tank 2 Level

9 Appendix
9.4.2.9 Group 10: Internal values
No. HMI Text Note
09.11 4368: Aft1Exh.Tank2 T 4368: Aftertreatment 1 Diesel Exhaust Fluid Tank 2 Temperature
09.12 250: Total fuel used 250: Engine Total Fuel Used
09.13 247: Engine hours 247: Engine hours
09.14 96: Fuel level 1 96: Fuel level 1
09.15 38: Fuel level 2 38: Fuel level 2
09.16 3719: DPF 1 Soot Load 3719: Diesel Particulate Filter 1 Soot Load Percent
09.17 3720: DPF 1 Ash Load 3720: Diesel Particulate Filter 1 Ash Load Percent
09.18 3251: DPF Diff. P 3251: Aftertreatment 1 Diesel Particulate Filter Differential Pressure
9.4.2.9 Group 10: Internal values
No. HMI Text Note
10.01 ZERO Zero
10.02 ONE One
10.04 Battery voltage [%] Battery voltage (percentage value related on battery voltage 24V)
10.06 Calc.ground curr.[%] Calculated ground current
10.07 Meas.ground curr.[%] Direct measured ground current
10.08 AM PID1 bias Free PID 1 analog output (PID1 bias)
10.11 System nominal P [%] Active nominal power in system (percentage value related on system rated active
power)
10.12 System real P [%] Total real power in system (percentage value related on system rated active
power)
10.13 Syst.res.real P [%] Reserve real power in system (percentage value related on system rated active
power)
10.39 PV load ref. [%] PV load reference
10.40 Generator load [%] Generator load (value index 237)
10.54 Battery voltage [V] Battery voltage
10.56 Calc.ground curr.[A] Calculated ground current
10.57 Meas.ground curr.[A] Direct measured ground current
10.61 System nominal P [W] Active nominal power in system [W]
10.62 System real P [W] Total real power in system [W]
10.63 Syst.res.real P [W] Reserve real power in system [W]
10.64 Act. power LSx [W] Active power LSx
(Active mains power in own segment)
10.65 React. power LSx [var] Reactive power LSx (Reactive mains power in own segment)
10.66 Syst.react.pwr.[var] Total reactive power in system [var]
10.70 LSx freq. L-L [Hz] LSx frequency L-L

9 Appendix
9.4.2.10 Group 11: Engine values
No. HMI Text Note

Mains frequency of the LSx with the smallest device number OR frequency of the
LSx with a close wish to the own segment.
10.71 LSx volt.L-L [V] LSx voltage L-L
Mains delta voltage of the LSx with the smallest device number
10.72 LSx volt.L-N [V] LSx voltage L-N
Mains wye voltage of the LSx with the smallest device number
10.73 Average load 1 [kW] Average load 1
10.78 Average load sum [kW] Average load sum
10.79 RTC Year RTC Year
10.80 RTC Month RTC Month
10.81 RTC Day RTC Day
10.82 RTC Hour RTC Hour
10.83 RTC Minute RTC Minute
10.84 RTC Second RTC Second
10.85 RTC Weekday RTC Weekday
10.90 Generator load [kW] Generator load from the generators with closed GCB [kW]
9.4.2.10 Group 11: Engine values
No. HMI Text Note
11.01 Engine speed [%] Engine speed (percentage value related on engine rated speed)
11.02 Voltage bias [%] Biasing Voltage / P reactive
11.03 Speed bias [%] Biasing Frequency / P active
11.04 Analog input D + [%] Analog input D + (percentage value related on battery voltage 24V)
11.51 Engine speed [rpm] Engine speed
11.54 Analog input D + [V] Analog input D +
11.55 Eng.oper.hours [h] Engine operating hours
11.56 Cyl.temp.bank 1 [°C] Average cylinder temperature bank 1
11.57 Cyl.temp.bank 2 [°C] Average cylinder temperature bank 2
11.58 Period of use [h] Period of use hours
11.59 Cooldown time [s] Cooldown time
11.60 Preglow time [s] Preglow time
11.61 Eng. monit. delay [s] Engine monitoring delay time
11.62 Auxil.serv.prerun [s] Auxiliary services prerun time

9 Appendix
9.4.2.11 Group 13: Constants
No. HMI Text Note
11.63 Auxil.serv.postr. [s] Auxiliary services postrun time
11.64 Stop engine [s] Stop time of the engine
11.66 Number of starts Number of starts
9.4.2.11 Group 13: Constants
No. HMI Text Note
13.01 Free constant 1 Free constant 1
9.4.2.12 Group 14: Controller values
No. HMI Text Note
14.01 Excitation AVR [%] Excitation AVR [%]
14.02 Volt. setp. V(f) [%] Voltage setpoint V(f) [%]
14.52 Volt. setp. V(f) [V] Voltage setpoint V(f) [V]
9.4.2.13 Group 15: Controller setpoints 2
No. HMI Text Note
15.01 Int. SP gen.load [%] Internal setpoint generator load
9.4.2.14 Group 21: CAN1 Receive

9 Appendix
9.4.2.15 Group 24: Free analog values
No. HMI Text Note
21.01 CAN1 RPDO1.1 CAN1 RPDO1.1 (value index 3371, signed short)
9.4.2.15 Group 24: Free analog values
Note: In future releases (higher than 2.10-0) the variables 24.05-24.08 will be write-
protected with code level CL1.
No. HMI Text Note
24.01 Free analog value 1 Free analog value 1 (value index 587, signed short)
9.4.2.16 Group 81: Results 1
Analog outputs of function-related AnalogManagers.

9 Appendix
No. HMI Text Note
81.01 AM Preglow criterion Preglow criterion
81.02 AM Warm-up criterion Engine warm-up criterion
81.03 AM Frequency SP1[Hz] Frequency setpoint 1 source [Hz]
81.04 AM Frequency SP2[Hz] Frequency setpoint 2 source [Hz]
81.05 AM ActPower SP1 [W] Active power setpoint 1 source [W]
81.09 AM Voltage SP1 [V] Voltage setpoint 1 source [V]
81.10 AM Voltage SP2 [V] Voltage setpoint 2 source [V]
81.11 AM PF / var SP1[- / var] PF / var setpoint 1 source [- / var]
81.12 AM PF / var SP2[- / var] PF / var setpoint 2 source [- / var]
81.13 AM PID1 setpoint PID 1 control setpoint
81.14 AM PID1 actual value PID 1 control actual value
81.19 AM Ext.mains act.pwr. External measured mains active power
81.20 AM Ext.mains RPower External measured mains reactive power
81.21 AM Derating source Free derating source
81.22 AM ECU seq.A_IN_1 ECU sequencer analog input 1
81.23 AM ECU seq.A_IN_2 ECU sequencer analog input 2
81.24 AM Engine speed Engine speed [rpm]
81.25 AM Engine oil press. Engine oil pressure
81.26 AM Engine hours Engine hours
81.27 AM Engine fuel level Engine fuel level [%]
81.28 AM Engine batt.volt. Engine battery voltage [V]
81.29 AM Engine coolant T Engine coolant water temperature
81.30 AM Consumer load [kW] Consumer load [kW]
81.31 AM Reference VQ0 Reference VQ0
81.32 AM Q / P refer.offset Q / P reference offset
81.34 AM Setpoint gen.load Setpoint generator load

9 Appendix
No. HMI Text Note
82.01 AM FlexLim 1 source Flexible Limit 1 data source
82.27 AM FlexLim 27source Flexible Limit 27 data source

9 Appendix
9.4.2.18 Group 90: Internal Values 0
No. HMI Text Note
No. HMI Text Note
90.01 AM Cust.screen 1.1 Customer defined screen 1 row 1
No. HMI Text Note
91.01 AM Internal value 1 Internal value 1

9 Appendix
9.4.2.20 Group 93: Analog Outputs 1
No. HMI Text Note
9.4.2.20 Group 93: Analog Outputs 1
No. HMI Text Note
93.01 AM Data source AO1 Analog output 1 data source
93.21 AM Data s. ext. AO1 External Analog output 1 data source
9.4.3 Reference Values
9.4.3.1 Generator Rated Voltage
Generator voltage values
(Wye and Delta and average values)
User defined max. output value = 100% means, that the 100% refer to the generator
rated voltage. If parameter “Source value at maximal output” is set to “+100.00%” this
will result in that the Analog output delivers its maximum output value if for example
400V Phase-phase are the nominal value and 400V are measured. If only 200 V are
measured this will result in an analog output value of 50% end scale.
9.4.3.2 Mains Rated Voltage
Mains voltage values

9 Appendix
9.4.3.3 Nominal Frequency
(Wye, Delta, Average, and dragged values)
User defined max. output value = 100% means, that the 100% refer to the mains rated
voltage. If parameter “Source value at maximal output” is set to “+100.00%” this will
result in that the Analog output delivers its maximum output value if for example 400V
are the nominal value and 400V are measured. If only 200 V are measured this will result
in an analog output value of 50% end scale.
9.4.3.3 Nominal Frequency
Generator, Mains,Busbar1,Busbar2 frequency values
User defined max. output value = 100% means, that the 100% refer to the nominal
frequency. If parameter “Source value at maximal output” is set to “+100.00%” this will
result in that the Analog output delivers its maximum output value if a for example 50Hz
are the nominal value and 50V are measured.
9.4.3.4 Generator/Mains rated active/reactive Power
Generator and Mains active/ reactive/ apparent power values
User defined max. output value = 100% means, that the 100% refer to the rated active
power value. If parameter “Source value at maximal output” is set to “+100.00%” this
will result in that the Analog output delivers its maximum output value if a for example
1000kW are the nominal value and 1000kW are measured. If only 200kW are measured
this will result in an Analog output value of 20% end scale.
9.4.3.5 Generator/Mains Power Factor
Mains and Generator Power factors
User defined max. output value = 100% means, that 50% refers to power factor 1.00.
If the power factor moves to lagging (inductive) the output goes to 100%. If the power
factor goes to leading (capacitive), the output goes to 0%.
Examples:
0,05% = -0,001(capacitive)
99,95% = 0,001(inductive)
100% = 0% = cosphi 0
9.4.3.6 Generator Rated Current
Generator current values
(Wye,Delta,Average and dragged values)
User defined max. output value = 100% means, that the 100% refer to the rated
generator current. If parameter “Source value at maximal output” is set to “+100.00%”
this will result in that the Analog output delivers its maximum output value if a for

9 Appendix
9.4.3.7 Mains rated Current
example 1000A are the nominal value and 1000A are measured. If only 200A are
measured this will result in an Analog output value of 20% end scale.
9.4.3.7 Mains rated Current
Mains current values
(Wye,Delta,Average and dragged values)
User defined max. output value = 100% means, that the 100% refer to the rated mains
current. If parameter “Source value at maximal output” is set to “+100.00%” this will
result in that the Analog output delivers its maximum output value if a for example 1000A
are the nominal value and 1000A are measured. If only 200A are measured this will result
in an Analog output value of 20% end scale.
9.4.3.8 Nominal Speed
Pickup speed
User defined max. output value = 100% means, that the 100% refer to the parametrized
nominal speed. If parameter “Source value at maximal output” is set to “+100.00%” this
will result in that the Analog output delivers its maximum output value if a for example
1500 RPM are the nominal value and 1500 RPM are measured. If only 750 RPM are
measured this will result in an Analog output value of 50% end scale.
9.4.3.9 Battery Voltage
Battery voltage and Auxiliary excitation
User defined max. output value = 100% means, that the 100% refer to a voltage of 24.0
Volts . If parameter “Source value at maximal output” is set to “+100.00%” this will result
in that the Analog output delivers its maximum output value if a for example 24.0 Volts
are the nominal value and 24.0 Volts are measured. If only 12.0 Volts are measured this
will result in an Analog output value of 50% end scale.
9.4.3.10 Fixed Value 10000
Analog inputs, GAP values
User defined max. output value = 100% means, that the 100% refer to a fixed value of
10000. If parameter “Source value at maximal output” is set to “+100.00%” this will
result in that the Analog output delivers its maximum output value if a for example
“10000” is delivered by GAP.
9.4.3.11 Busbar 1 Rated Voltage
Busbar 1 voltages ( delta values)
User defined max. output value = 100% means, that the 100% refer to the nominal
busbar 1 voltage. If parameter “Source value at maximal output” is set to “+100.00%”

9 Appendix
9.4.3.12 Display Value Format
this will result in that the Analog output delivers its maximum output value if a for
example 400V are the nominal value and 400V are measured.
9.4.3.12 Display Value Format
The analog input values refer to the display value format (refer to parameter ╚═▷ 1035).
Delimiters like decimal points or commas are ignored. If the display value format is 0.01
bar for example, a value of 5 bar corresponds with 00500.
☼ Analog output example
• An analog input is configured to VDO 120 °C characteristic.

• The source value at maximum output is configured to 00100 (i.e. 100 °C).
• The source value at minimum output is configured to 00020 (i.e. 20 °C).
• The analog output range is configured to 0 to 20 mA.
• If a value of 20 °C (or below) is measured, the analog output issues its lower limit
(i.e. 0 mA).
• If a value of 100 °C (or above) is measured, the analog output issues its upper limit
(i.e. 20 mA).
• If a value of 60 °C is measured, the analog output issues 50% of its upper limit (i.e.
10 mA).
• If a value of 84 °C is measured, the analog output issues 80% of its upper limit (i.e.
16 mA).
☼ Flexible limit example
• An analog input is configured to VDO 10 bar characteristic.

• If the flexible limit is to be configured to 5.23 bar, it must be entered as 00523.
See the fixed display value formats below:
Analog input type Display value format Example value Example format
VDO 5 bar 0.01 bar 5.0 bar 500
VDO 10 bar 0.01 bar 6.6 bar 660
VDO 120 °C 1 °C 69 °C 69
VDO 150 °C 1 °C 73 °C 73
Pt100 1 °C 103 °C 103
Tab. 136: Display value format

9 Appendix
AnalogManager's default settings
ID Name Operator Default setting/value
5518 AM Frequency SP1[Hz] Analog1 ("A1 =") 05.51 Internal f setp1 [Hz]
Analog2 ("A2 =") 10.01 ZERO
Constant1 ("C1 =") 0
Function Type ("Type =") Pass through
Logic1 "L1" 02.01 LM FALSE
Operators
Operators-Unary1 —————
5519 AM Frequency SP2[Hz] Analog1 ("A1 =") 05.52 Internal f setp2 [Hz]
Operators
15147 AM Derating source Analog1 ("A1 =") 06.01 Analog input 1
Analog2 ("A2 =") 06.01 Analog input 1
Operators
5539 AM ActPower SP1 [kW] Analog1 ("A1 =") 05.54 Internal P setp1 [kW]
Operators

9 Appendix
Operators
5606 AM ActPower SP3 [kW] Analog1 ("A1 =") 05.80 Internal P setp3 [W]
Operators
Operators
5538 AM Warm-up criterion Analog1 ("A1 =") 10.01 ZERO
Operators
5638 AM PF/var SP1[-/kvar] Analog1 ("A1 =") 05.10 Intern. PF setp1 [%]

9 Appendix
Operators
5639 AM PF/var SP2[-/kvar] Analog1 ("A1 =") 05.11 Intern. PF setp2 [%]
Operators
3346 AM Preglow criterion Analog1 ("A1 =") 10.01 ZERO
Operators
5618 AM Voltage SP1 [V] Analog1 ("A1 =") 05.57 Internal V setp1 [V]
Operators
5619 AM Voltage SP2 [V] Analog1 ("A1 =") 05.58 Internal V setp2 [V]

9 Appendix
Operators
5577 AM PID1 setpoint Analog1 ("A1 =") 05.75 Int. PID1 setpoint
Operators
5578 AM PID1 actual value Analog1 ("A1 =") 10.01 ZERO
Operators
Operators

9 Appendix
Operators
Operators
Operators
3346 AM Preglow criterion Analog1 ("A1 =") 10.01 ZERO
Operators
5200 AM Data source AO1 Analog1 ("A1 =") 11.03 Speed bias [%]
Operators

9 Appendix
5214 AM Data source AO2 Analog1 ("A1 =") 11.02 Voltage bias [%]
Operators
10237 AM Data source ext.AO1 Analog1 ("A1 =") 11.03 Speed bias [%]
Operators
Operators
Operators 5

9 Appendix
Operators 5
15162 AM ECU seq.A_IN_1 Analog1 ("A1 =") 10.01 ZERO
Operators 5
15163 AM ECU seq.A_IN_2 Analog1 ("A1 =") 10.01 ZERO
Operators 5
9640 AM Internal value 1 Analog1 ("A1 =") 10.01 ZERO
9644 AM Internal value 2 Analog2 ("A2 =") 10.01 ZERO
9648 AM Internal value 3 Constant1 ("C1 =") 0
9652 AM Internal value 4 Function Type ("Type =") Pass through
9656 AM Internal value 5 Logic1 "L1" 02.01 LM FALSE
9660 AM Internal value 6 Logic2 "L2" 02.01 LM FALSE
9664 AM Internal value 7 Operators 5
9668 AM Internal value 8 Operators-Unary1 —————
9672 AM Internal value 9 Operators-Unary2 —————
9676 AM Internal value 10

9 Appendix

5780 AM Ext.mains act.pwr Analog1 ("A1 =") 06.01 Analog input 1
Operators 5
5794 AM Ext.mains RPower Analog1 ("A1 =") 06.02 Analog input 2
Operators 5
4206 AM FlexLim 1 source Analog1 ("A1 =") 10.01 ZERO
4240 AM FlexLim 3 source Constant1 ("C1 =") 0
4257 AM FlexLim 4 source Function Type ("Type =") Pass through
4276 AM FlexLim 5 source Logic1 "L1" 02.01 LM FALSE
4286 AM FlexLim 6 source Logic2 "L2" 02.01 LM FALSE
4296 AM FlexLim 7 source Operators 5
6026 AM FlexLim 10 source Constant1 ("C1 =") 0
6026 + (N x AM FlexLim 10 + N source ((N = Function Type ("Type =") Pass through
(+10)) 1, 2, ...))
... ...

9 Appendix

6326 AM FlexLim 40 source Operators 5
7690 AM Customer screen 1.1 Analog1 ("A1 =") 10.01 ZERO
7695 AM Customer screen 1.2 Analog2 ("A2 =") 10.01 ZERO
7700 AM Customer screen 1.3 Constant1 ("C1 =") 0
7705 AM Customer screen 1.4 Function Type ("Type =") Pass through
7710 AM Customer screen 1.5 Logic1 "L1" 02.01 LM FALSE
7715 AM Customer screen 1.6 Logic2 "L2" 02.01 LM FALSE
7720 AM Customer screen 1.7 Operators —————
7725 AM Customer screen 1.8 Operators-Unary1 —————
7730 AM Customer screen 2.9 Operators-Unary2
7735 AM Customer screen 2.1
8891 AM Engine speed Analog1 ("A1 =") 11.51 Engine speed [rpm]
Analog2 ("A2 =") 10.02 ONE
Operators 5
8893 AM Engine oil pressure Analog1 ("A1 =") 07.07 100:Engine Oil Press.
Analog2 ("A2 =") 10.02 ONE
Operators 5

9 Appendix
8895 AM Engine hours Analog1 ("A1 =") 11.55 Eng.oper.hours [h]
Analog2 ("A2 =") 10.02 ONE
Operators 5
8897 AM Engine fuel level Analog1 ("A1 =") 06.03 Analog input 3
Analog2 ("A2 =") 10.02 ONE
Operators 5
8899 AM Engine batt.voltage Analog1 ("A1 =") 10.54 Battery voltage [V]
Analog2 ("A2 =") 10.02 ONE
Operators 5
8901 AM Engine coolant temp. Analog1 ("A1 =") 07.15 110:Eng.Coolant Temp.
Analog2 ("A2 =") 10.02 ONE
Operators 5

9 Appendix
9.5 Status, Event And Alarm Reference
9059 AM Consumer load [kW] Analog1 ("A1 =") 02.74 Mains act.power [W]
Analog2 ("A2 =") 10.02 ONE
Constant1 ("C1 =") -0.001
Function Type ("Type =") Multiply type C
Operators 5
Tab. 137: Factory settings: AnalogManager
9.5 Status, Event And Alarm Reference
9.5.1 Status messages
Message text ID Meaning
STOP mode 14354 Operation mode STOP is active
Operation mode TEST 4685 Operation mode TEST is active
The unit is running a test procedure according to the configuration.
MAN mode 14355 Operation mode MANUAL is active
AUTO mode 14353 Operation mode AUTOMATIC is active
AUTO mode ready 13253 Automatic mode ready for start
The unit is waiting for a start signal in Automatic operating mode and no alarm of
class C, D, E, or F is present.
Aux. services prerun 13201 Prerun of the auxiliary operation is active
Before the engine is started the signal "aux. services prerun" is enabled, so that all
required equipment which is necessary for the operation of the engine can be
initialized, started or switched.
Cool down 13204 Coasting of the engine is active
The no load operation is performed prior to the stopping of the engine. The no load
operation is utilized to cool the engine.
Crank protect 13214 Starter protection
To prevent the starter from being damaged by an engine that is rotating, a crank
protection delay is active to ensure that the engine has time to stop rotating.
Idle run active 13216 The control is in idle mode
No undervoltage, underfrequency, and underspeed monitoring is performed in idle

mode. The flexible limits 33 through 40 are not monitored.
Gen. stable time 13250 Generator stable time is active

9 Appendix

If the engine monitoring delay timer has expired, the generator settling time
starts. This permits for an additional delay time before the breaker is closed in
order to ensure that none of the engine delayed watchdogs trips.
Aux. serv. postrun 13200 Postrun of the auxiliary operation is active
After the engine has stopped, auxiliary operations are enabled. These operations
ensure that required equipment which is necessary for the operation of the engine
continues to run (i.e. electric cooling fan).
In operation 13251 The genset is in regular operation
The genset is in regular operation and is ready for supplying load.
Start - Pause 13207 Start pause while starting the engine is active
If the engine could not be started, the controller will pause for the configured time
prior to attempting to issuing a start command again.
Stop engine 13203 Engine will be stopped
The engine will be stopped. The engine stop delay will be started when ignition
speed has been fallen below. A restart is only possible if the engine stop delay has
been expired.
Start 13206 Start engine is active
After the "Prerun auxiliary operation" expires, the engine is started according to
the configured start logic (Diesel or gas engine). When the start sequence is
active, various relays are enabled and representative signals are passed via the
CAN bus to a secondary engine control.
Ramp to rated 13254 Engine is accelerating to rated speed
After firing speed has been exceeded, the engine monitoring delay timer starts.
This message is displayed during this period.
Power limited prerun 13252 Active power limited prerun is active
The real power setpoint is limited to the warm up power limit for the configured
warm up time.
Ignition 13213 Enable the ignition (Gas engine)
After the purging operation and before the fuel solenoids opened.
Preglow 13208 Preglow of the engine is active (Diesel engine)
The diesel engine is preheated prior to starting.
Turning 13212 Purging operation is active (Gas engine)
Before the fuel solenoid opens and the ignition of the gas engine is energized the
remaining fuel, that may be present in the combustion chamber, will be removed
by a purging operation. The starter turns the engine without enabling the ignition
for a specified time to complete the purging operation. After the purging process,
the ignition is energized.
Start w / o Load 13263 Start without load is active
A regular engine start is performed. The GCB operation is blocked to prevent a

change from mains to generator supply.
Emergency run 13211 Emergency power operation
After the control unit detects that a mains fault has occurred, the engine is started
after the emergency delay timer expires. The MCB is opened, the GCB is closed,
and the generator set assumes the load. If the generator set is already running,

9 Appendix

operations continue until the emergency power operation conditions no longer
exist. If the mains return, the mains settling timer becomes active first.
Run-up Synchron. 13271 Run-up Synchronization
The run-up synchronization mode is active.
Derating active 13281 Derating active
As long as the derating function is activated, this text message is shown.
Inhibit cranking 13284 Inhibit cranking
The cranking is blocked.
Uprating active 13287 Uprating active
As long as the uprating function is activated, this text message is shown.
Gen excitation lim. 13288 Generator excitation limit is reached
During regulation kvar at the interchange point the maximum allowed excitation
current is reached.
P(V) derating 13309 P(V) derating is active
System update 14763 System update is active
The system update procedure is ongoing.
Keypad locked 14775 The keypad easYgen is locked
Loading generator 13258 The generator power will be increased to the setpoint
The generator power will be increased to the configured setpoint with a rate
defined by the power control setpoint ramp.
Unloading mains 13264 The mains power will be decreased
The real power setpoint is increased with the configured rate after synchronizing
the generator in interchange transition mode. After the mains have been
unloaded, the MCB will be opened.
Unloading generator 13256 The generator power will be decreased
The generator power will be decreased after a stop command has been issued
with a rate defined by the power control setpoint ramp before the GCB will be
opened.
GCB - > MCB Delay 13261 GCB - MCB delay time is active
If the breaker logic is configured to Open Transition and a transfer from generator
to mains supply is initiated, the transfer time delay will start after the replay "GCB
is open" is received. The MCB close command will be issued after the transfer time
has expired.
MCB dead bus close 13210 Dead bus closing of the MCB
The MCB is closed onto the de-energized busbar. The measured busbar voltage is
below the configured dead bus detection limit.
MCB - > GCB Delay 13262 MCB - GCB delay time is active
If the breaker logic is configured to Open Transition and a transfer from mains to
generator supply is initiated, the transfer time delay will start after the reply "MCB
is open" is received. The GCB close command will be issued after the transfer time
has expired.

9 Appendix
9.5.2 Event History
Synchronization GCB 13259 The GCB will be synchronized
The control tries to synchronize the GCB.
Synchronization MCB 13260 The MCB will be synchronized
The control tries to synchronize the MCB.
Mains settling 13205 Mains settling time is active
When the control unit detects that the mains fault is no longer present and power
has been restored, the mains settling timer begins counting down. If the mains are
stable after the expiration of the timer (the mains voltage has not fallen below or
risen over the configured monitoring limits), the load is transferred from the
generator supply to the mains supply.
Open GCB 13255 The GCB is being opened
A GCB open command has been issued.
Open MCB 13257 The MCB is being opened
An MCB open command has been issued.
Critical mode 13202 Critical mode (Sprinkler operation) is active
The sprinkler operation is activated.
Emergency / Critical 13215 Emergency operation during active critical operation
Both Critical mode and Emergency run are activated.
GCB dead bus close 13209 Dead bus closing of the GCB
The GCB is closed onto the de-energized busbar. The measured busbar voltage is
below the configured dead bus detection limit.
Synch. PERMISSIVE 13265 Synchronization mode PERMISSIVE.
The frequency / voltage regulation for synchronization is disabled. The according

breaker close pulse is enabled.
Synch. CHECK 13266 Synchronization mode CHECK
The frequency / voltage regulation for synchronization is enabled. The according

breaker close pulse is disabled.
Synch. OFF 13267 Synchronization mode OFF
The frequency / voltage regulation for synchronization is disabled. The close pulse
is disabled.
Inh.dead bus closure 13311 Inhibit dead bus closure
The dead busbar closure is inhibited.
9.5.2 Event History
General notes
The event history is a 1000 entry FIFO (First In/First Out) memory for logging alarm events
and operation states of the unit. As new event messages are entered into the history, the
oldest messages are deleted once 1000 events have occurred.

9 Appendix
9.5.3 Event Message
For additional information refer to ╚═▷ “5 Operation”.
Resetting event history
Make sure to have set the appropriate code level to reset the event history.
If you have not entered the correct password for the required code level, the parameters
for resetting the event history are not available (for additional information refer to ╚═▷
“4.3.4.1 Password System - Parameter Overview”).
Three ways to reset Event History
• ToolKit: Click the »Clear all « button at [STATUS MENU / Diagnostic: Event History].
(Read Event History at the same page)
• HMI/display: Go to [Parameter / Configure system management / Factory default

settings] and select »Yes«, then »Clear eventlog« appears. Select »Yes« for »Clear
event log«
(To read Event History go to: [Next Page / Diagnostic / Event History])
• Parameter/remote:Set parameter ╚═▷ 1706»Clear eventlog« ) to "TRUE" (1)
• The complete event history is now being cleared
9.5.3 Event Message
AUTO mode 14353 The unit is switched to AUTO mode
STOP mode 14354 The unit is switched to STOP mode
MAN mode 14355 The unit is switched to MANUAL mode
No load test 4683 Test mode started without load
Load test 4684 Test mode started with load
Operation mode TEST 4685 The unit is switched to TEST mode
MCB opened 14700 The MCB reply signals MCB is open
MCB closed 14701 The MCB reply signals MCB is closed
GCB opened 14702 The GCB reply signals GCB is open
GCB closed 14703 The GCB reply signals GCB is closed
Mains failure 14704 Mains frequency or voltage is not ok
Emergency run 14705 The emergency run is initiated
Engine is running 14706 The engine is started
Critical mode 14707 The critical mode is initiated
Open command GCB 14718 Control commands GCB open
Close command GCB 14719 Control commands GCB close
Open command MCB 14720 Control commands MCB open
Close command MCB 14721 Control commands MCB close

9 Appendix
9.5.4 Alarm Classes
Engine Idle run 14762 The engine is running in idle
System update 14763 System update is active
Start up power 14778 Start up power supply
Power derating act. 16192 Power derating is activated
Power uprating act. 16193 Power uprating is activated
Neutral cont. opened 1842 Neutral contactor is opened
Neutral cont. closed 1843 Neutral contactor is closed
Gen excitation lim. 13288 The limit of the generator's excitation is exceeded
9.5.4 Alarm Classes
The control functions are structured in the following alarm classes:
Alarm class Visible in the LED "Alarm" Relay Shut-down Engine blocked
display "Command: engine until ack.
& horn open GCB" sequence has
been
performed
A Yes No No No No
Warning Alarm This alarm does not interrupt the unit operation. A message output without a centralized alarm
occurs:
• Alarm text.
B Yes Yes No No No
Warning Alarm This alarm does not interrupt the unit operation. An output of the centralized alarm occurs and the
command variable 3.05 (horn) is issued.
• Alarm text + flashing LED "Alarm" + Relay centralized alarm (horn).
C Yes Yes Soft unloading Cool down time Yes
Shutdown Alarm With this alarm the GCB is opened and the engine is stopped. Coasting occurs.
• Alarm text + flashing LED "Alarm" + Relay centralized alarm (horn) + GCB open + Coasting +
Engine stop.
D Yes Yes Immediately Cool down time Yes
Shutdown Alarm With this alarm the GCB is opened and the engine is stopped. Coasting occurs.
• Alarm text + flashing LED "Alarm" + Relay centralized alarm (horn) + GCB open + Coasting +
Engine stop.
E Yes Yes Soft unloading Immediately Yes
Shutdown Alarm With this alarm the GCB is opened immediately and the engine is stopped.
• Alarm text + flashing LED "Alarm" + Relay centralized alarm (horn) + GCB open + Engine stop.
F Yes Yes Immediately Immediately Yes

9 Appendix
9.5.5 Alarm Messages
Alarm class Visible in the LED "Alarm" Relay Shut-down Engine blocked
display "Command: engine until ack.
& horn open GCB" sequence has
been
performed
Shutdown Alarm With this alarm the GCB is opened immediately and the engine is stopped.
• Alarm text + flashing LED "Alarm" + Relay centralized alarm (horn) + GCB open + Engine stop.
Control No No No No No
Control Signal This signal issues a control command only. It may be assigned to a discrete input for example to get a
control signal, which may be used in the LogicsManager. No alarm message and no entry in the alarm
list or the event history will be issued. This signal is always self-acknowledging, but considers a delay
time and may also be configured with an engine delay.
In manual mode all stopping alarms are without cool down.
CAUTION!
If an alarm of class C, D, or E is present and the GCB cannot be opened, the engine will
not be stopped. This can only be achieved by enabling GCB monitoring (parameter ╚═▷
2600) with the alarm class configured to "F" (parameter ╚═▷ 2601).
If an alarm has been configured with a shutdown alarm that has been enabled to self-
acknowledge, and has been configured as engine delayed the following scenario may
happen:
• The alarm shuts down the engine because of its alarm class.
• Due to the engine stopping, all engine delayed alarms are ignored.
• The alarm class is acknowledged automatically.
• The alarm will self-acknowledge and clear the fault message that shut the engine
down.
This prevents the fault from being analyzed. After a short delay, the engine will
restart.
• After the engine monitoring delay expires, the fault that originally shut down the
engine will do so again.
This cycle will continue to repeat until corrected.
9.5.5 Alarm Messages
9.5.5.1 No alarm
No alarm active 13328 There is no alarm active.

9 Appendix
9.5.5.2 Generator monitoring
Gen. overfrequency 1 1912 Generator overfrequency, limit value 1
The generator frequency has exceeded the limit value 1 for generator
overfrequency.
Gen. overfrequency 2 1913 Generator overfrequency, limit value 2
The generator frequency has exceeded the limit value 2 for generator
overfrequency.
Gen. underfrequency 1 1962 Generator underfrequency, limit value 1
The generator frequency has fallen below the limit value 1 for generator
underfrequency.
Gen. underfrequency 2 1963 Generator underfrequency, limit value 2
The generator frequency has fallen below the limit value 2 for generator
underfrequency.
Gen. overvoltage 1 2012 Generator overvoltage, limit value 1
The generator voltage has exceeded the limit value 1 for generator overvoltage.
Gen. overvoltage 2 2013 Generator overvoltage, limit value 2
The generator voltage has exceeded the limit value 2 for generator overvoltage.
Gen. undervoltage 1 2062 Generator undervoltage, limit value 1
The generator voltage has fallen below the limit value 1 for generator
undervoltage.
Gen. undervoltage 2 2063 Generator undervoltage, limit value 2
The generator voltage has fallen below the limit value 2 for generator
undervoltage.
Gen. overcurrent 1 2218 Generator overcurrent, limit value 1
The generator current has exceeded the limit value 1 for the generator
overcurrent.
overcurrent.
overcurrent.
Inv. time overcurr. 4038 Generator inverse time-overcurrent
The generator current has exceeded the limit based on the inverse time
overcurrent setting.
Gen. rev / red. pwr.1 2262 Generator reverse power, limit value 1 / Generator reduced power, limit value 1
The generator power has exceeded the limit value 1 for generator reverse power /
generator reduced power.
Gen. rev / red. pwr.2 2263 Generator reverse power, limit value 2 / Generator reduced power, limit value 2

9 Appendix

The generator power has exceeded the limit value 2 for generator reverse power /
generator reduced power.
Gen. overload IOP 1 2314 Generator overload IOP, limit value 1
The generator power has exceeded the limit value 1 for generator overload in
islanded operation (MCB is open).
Gen. overload IOP 2 2315 Generator overload IOP, limit value 2
islanded operation (MCB is open).
Gen. overload MOP 1 2362 Generator overload MOP, limit value 1
Gen. overload MOP 2 2363 Generator overload MOP, limit value 2
Unbalanced load 1 2412 Generator unbalanced load, limit value 1
The generator current has exceeded the limit value 1 for generator unbalanced
load.
Unbalanced load 2 2413 Generator unbalanced load, limit value 2
The generator current has exceeded the limit value 2 for generator unbalanced
load.
Gen. volt. asymmetry 3907 Voltage asymmetry
The generator phase-to-phase voltages have higher differences between each

other than the configured limit value.
Ground fault 1 3263 Generator ground current, limit value 1
The measured or calculated ground current has exceeded the limit value 1 for the
generator ground current.
Ground fault 2 3264 Generator ground current, limit value 2
The measured or calculated ground current has exceeded the limit value 2 for the
generator ground current.
Gen. ph. rot. mismatch 3955 Generator rotating field mismatch
The generator rotating field does not correspond with the configured direction.
Gen. PF lagging 1 2337 Generator overexcited, limit value 1
The power factor limit 1 has been exceeded at the generator towards inductive.
Gen. PF lagging 2 2338 Generator overexcited, limit value 2
The power factor limit 2 has been exceeded at the generator towards inductive.
Gen. PF leading 1 2387 Generator underexcited, limit value 1
The power factor limit 1 has fallen below at the generator towards capacitive.
Gen. PF leading 2 2388 Generator underexcited, limit value 2
The power factor limit 2 has fallen below at the generator towards capacitive.

9 Appendix
9.5.5.3 Busbar monitoring
Gen act. pwr mismatch 2924 Generator active power mismatch
The deviation between the generator power and the active power setpoint has
exceeded the limit.
Gen unloading fault 3124 Generator unloading mismatch
The easYgen failed to reduce the generator power below the configured unload
limit.
Pole Slip 2424 Pole slip Monitoring Alarm active
A pole slip was detected during running the generator mains parallel.
9.5.5.3 Busbar monitoring
Busbar v / f not ok 5123 Busbar voltage or frequency is not ok
Busbar voltage and frequency are not in range according to the configured limits.
9.5.5.4 Mains monitoring
Mains overfreq. 1 2862 Mains overfrequency, limit value 1
The mains frequency has exceeded the limit value 1 for mains overfrequency.
Mains overfreq. 2 2863 Mains overfrequency, limit value 2
The mains frequency has exceeded the limit value 2 for mains overfrequency.
Mains underfreq. 1 2912 Mains underfrequency, limit value 1
The mains frequency has fallen below the limit value 1 for mains underfrequency.
Mains underfreq. 2 2913 Mains underfrequency, limit value 2
The mains frequency has fallen below the limit value 2 for mains underfrequency.
Mains overvoltage 1 2962 Mains overvoltage, limit value 1
The mains voltage has exceeded the limit value 1 for mains overvoltage.
Mains overvoltage 2 2963 Mains overvoltage, limit value 2
The mains voltage has exceeded the limit value 2 for mains overvoltage.
Mains undervoltage 1 3012 Mains undervoltage, limit value 1
The mains voltage has fallen below the limit value 1 for mains undervoltage.
Mains undervoltage 2 3013 Mains undervoltage, limit value 2
The mains voltage has fallen below the limit value 2 for mains undervoltage.
Mains phase shift 3057 Mains phase shift

9 Appendix
9.5.5.4 Mains monitoring

A mains phase shift, which has exceeded the configured limit, has occurred.
Mains df / dt 3106 Mains df / dt (ROCOF)
A mains df / dt, which has exceeded the configured limit, has occurred. Triggering
this monitoring function causes the mains decoupling function to trigger.
Mains decoupling 3114 Mains decoupling is initiated
One or more monitoring function(s) considered for the mains decoupling

functionality has triggered.
Decoupling GCB < - > 5147 Decoupling GCB < - > MCB
MCB
During decoupling there was a change over from the preferred breaker to the
other.
Mns. ph. rot. mismatch 3975 Mains rotating field mismatch
The mains rotating field does not correspond with the configured direction.
Mains import power 1 3217 Mains import power, limit value 1
The mains import power has exceeded or fallen below the limit value 1 for mains
import power.
Mains import power 2 3218 Mains import power, limit value 2
The mains import power has exceeded or fallen below the limit value 2 for mains
import power.
Mains export power 1 3241 Mains export power, limit value 1
The mains export power has exceeded or fallen below the limit value 1 for mains
export power.
Mains export power 2 3242 Mains export power, limit value 2
The mains export power has exceeded or fallen below the limit value 2 for mains
export power.
Mains PF lagging 1 2985 Mains power factor lagging exceeded, limit value 1
The power factor limit 1 has been exceeded at the mains interchange point
towards inductive.
Mains PF lagging 2 2986 Mains power factor lagging exceeded, limit value 2
The power factor limit 2 has been exceeded at the mains interchange point
towards inductive.
Mains PF leading 1 3035 Mains power factor leading exceeded, limit value 1
The power factor limit 1 has fallen below at the mains interchange point towards
capacitive.
Mains PF leading 2 3036 Mains power factor leading exceeded, limit value 2
The power factor limit 1 has fallen below at the mains interchange point towards
capacitive.
Mns act. pwr mismatch 2934 Mains active power mismatch
The deviation between the import / export power and the active import / export
power setpoint has exceeded the limit.
Mains volt. incr. 8834 Mains voltage increase monitor has tripped

9 Appendix
9.5.5.5 Engine monitoring

The mains voltage has exceeded for a longer time period the voltage increase
criteria.
QV monitoring 1 3288 QV monitoring, delay time 1
The generator reactive power has exceeded the limit with delay time 1.
QV monitoring 2 3289 QV monitoring, delay time 2
The generator reactive power has exceeded the limit with delay time 2.
Time dep. voltage 1 4958 Time-dependent voltage, limit value 1
The measured voltage falls below / exceeds the configured criteria.
9.5.5.5 Engine monitoring
Overspeed 1 2112 Engine overspeed, limit value 1
The engine speed has exceeded the limit value 1 for engine overspeed.
Overspeed 2 2113 Engine overspeed, limit value 2
The engine speed has exceeded the limit value 2 for engine overspeed.
Underspeed 1 2162 Engine underspeed, limit value 1
The engine speed has fallen below the limit value 1 for engine underspeed.
Underspeed 2 2163 Engine underspeed, limit value 2
The engine speed has fallen below the limit value 2 for engine underspeed.
Unintended stop 2652 Unintended Stop
The easYgen expects the generator to be running but a sudden underrun of the
ignition speed has been detected.
Speed / freq. mismatch 2457 Difference in frequency / speed measurement
The speed differential between the generator frequency (ascertained by the

generator voltage measurement) and the engine speed (measured by the MPU)
has exceeded the configured limit.
Eng. stop malfunct. 2504 Engine cannot be stopped
There is still recognized a turning engine (by electrical frequency or speed signal)
even the engine is stopped.
Start fail 3325 Failure of engine to start
The generator set has failed to start after the configured number of attempts.
Charge alt. low volt 4056 Charging alternator voltage low

9 Appendix
9.5.5.6 Operating Range Monitoring

The charging alternator voltage has fallen below the critical limit.
Cylinder temp.lev.1 14575 Cylinder temperature Level 1
The cylinder temperature difference exceeded level 1.
Cylinder temp.lev.2 14576 Cylinder temperature Level 2
The cylinder temperature difference exceeded level 2.
Cyl.tmp.wire brk. 14584 Cylinder temperature monitoring has detected sensor wire as broken
Active LS mismatch 5105 Active power loadsharing mismatch.
The percentage load value of this device is different to the others.
Reactive LS mismatch 5111 Reactive power loadsharing mismatch
The percentage load value of this device is different to the others.
Maint. days exceeded 2560 Maintenance days exceeded
The generator run time has exceeded the configured number of days since the last
maintenance call RESET.
Maint. hrs exceeded 2561 Maintenance hours exceeded
The generator run time has exceeded the configured number of operating hours
since the last maintenance call RESET.
Operating range monitoring alarm. The device stocks because of a logical

circumstance. The operating range monitor indicates an alarm with an error
number. The number stands for a failed check procedure. For more information
refer to chapter "Operating Range Failure".
Oper. range failed 1 2665 Check 1: The easYgen wants close the GCB, but the generator is not within its
operating range.
• (GCB shall be closed OR Emergency run is active) AND
• Firing speed is reached AND
• GCB is open AND
• Generator is not okay AND
• Idle monitoring is expired
Oper. range failed 2 2666 Check 2: The easYgen wants close the GCB, but the busbar is not within the
generator operating range.
• (GCB shall be closed OR Emergency run is active) AND
• Firing speed reached AND
• GCB is open AND
• Generator is okay AND
• Busbar is undefined (Busbar not dead AND not within the operation range)

9 Appendix
Oper. range failed 3 2667 Check 3: The easYgen wants close the GCB in breaker transistion mode "Open
transition" with GCB and MCB open status. In this condition the busbar is expected
as dead, but there is still voltage on busbar measured.
• GCB shall be closed AND
• GCB is open AND
• Breaker mode "open transition" is active AND
• MCB is open AND
• Busbar is okay AND
• No GCB in the system is closed
Oper. range failed 4 2668 Check 4: The easYgen wants close the GCB onto a dead busbar. The device cannot
close the breaker onto busbar, because there is minimum one neighbor device
recognized with a GCB closed.
• GCB is open AND
• Generator is okay AND
• Busbar is dead AND
• Minimum one GCB in the system is closed
Oper. range failed 5 2669 Check 5: The easYgen wants synchronize the GCB, the MCB is closed, but the
mains or busbar is not within its operating range.
• GCB is open AND
• MCB is closed AND
• Idle monitoring is expired AND
• Breaker mode with GGB is not active AND
• Mains OR Busbar is not okay
Oper. range failed 6 2670 Check 6: The easYgen wants close the GGB, but the generator minimum power is
not reached.
• GGB shall be closed with deadbus closure AND
• GGB request minimum power is not available AND
• LM Bypass min. power for closing GGB is not active
Oper. range failed 7 2671 Check 7: The easYgen wants close the GGB in the Open Transition Mode, but the
generator minimum power is not reached.
• GGB shall be closed in breaker mode "open transition" AND
• GGB request minimum power isn't available AND
• LM Bypass min. power for closing GGB isn't active
Oper. range failed 12 2676 Check 12: The easYgen checks the phase rotation of generator, busbar and mains.
If the phase rotation of all systems does not match and a synchronisation shall be
executed this will occur. (Synchronisation is blocked)

9 Appendix
9.5.5.7 Breaker Monitoring

• Synchronisation (GCB, GGB or MCB) shall be executed AND
• Phase rotation of all systems does not match
9.5.5.7 Breaker Monitoring
GCB fail to close 2603 GCB failed to close
The easYgen has attempted to close the GCB the configured maximum number of
attempts and failed.
GCB fail to open 2604 GCB failed to open
The easYgen has attempted to open the GCB within the configured time and
failed.
GCB syn. timeout 3064 GCB synchronization time exceeded
The easYgen has failed to synchronize the GCB within the configured
synchronization time.
GCB failure 50BF 10668 GCB failure 50BF
Generator current is measured even if the mains repliy signals GCB open.
MCB fail to close 2623 MCB failed to close
The easYgen has attempted to close the MCB the configured maximum number of
attempts and failed. Depending on the configuration, the easYgen will continue to
attempt to close the GCB as long as the conditions for closing the MCB are
fulfilled.
MCB fail to open 2624 Failed MCB open
The easYgen is still receiving the reply MCB closed" after the MCB open monitoring
timer has expired.
MCB syn. timeout 3074 MCB synchronization time exceeded
The easYgen has failed to synchronize the MCB within the configured
synchronization time.
MCB failure 50BF 10670 MCB failure 50BF
There is a mains current measured even the MCB reply signals MCB open.
MCB plausibility 10672 MCB plausibility
The number of closed MCBs is different to the number of easYgen devices in the
same segment.
N-cont. reply mism. 5153 Neutral contactor reply mismatch
Neutral contactor reply mismatch to the NC command.

9 Appendix
9.5.5.8 CANopen Monitoring
9.5.5.8 CANopen Monitoring
CANopen Interface 1 10087 Interface alarm CANopen on CAN bus 1
No Receive Process Data Object ( RPDO) is received within the configured time.
No message is received from the external expansion board (Node-ID) within the
configured time.
No Receive Process Data Object ( RPDO) is received within the configured time.
9.5.5.9 CAN J1939 (ECU) Monitoring
J1939 dev. 1 timeout 10059 J1939 device 1 timeout
Messages from the J1939 device 1 are missing. (CAN2)
J1939 ECU timeout 10058 J1939 ECU timeout
Messages from the J1939 ECU are missing. (CAN2)
Red stop lamp 15125 Red stop lamp, J1939 interface
The ECU sends a red stop lamp signal. There is a critical failure detected in the
ECU.
Amber warning lamp 15126 Amber warning lamp, J1939 interface
The ECU sends a amber warning lamp signal. There is a warning failure detected in
the ECU.
J1939 Emission lamp 10663 J1939 Emission lamp
ECU has an Emission / Malfunction alarm.
J1939 Protect lamp 10662 J1939 Protect lamp
ECU has a protect alarm.
9.5.5.10 Ethernet Communication Monitoring
Ethernet issue 11852 Abnormal rate of Ethernet messages.

9 Appendix
9.5.5.11 Multi-unit Monitoring

The easYgen detects an abnormal high rate of Ethernet UDP-messages per time
scale.
9.5.5.11 Multi-unit Monitoring
Parameter alignment 4073 LDSS parameter mismatch detected
The easYgen has detected that not all LDSS parameters are configured identically
at all participating units.
Refer in the manual to the chapter "Multi-unit Parameter Alignment" to see the
relevant LDSS parameter.
Missing easYgen 4059 Missing easYgen
At least one easYgen is missing. Check the status of the communication

diagnostic.
Syst.update easYgen 4074 System update easYgen
The communication topology of easYgens have changed. Check the

communication easYgen.
Syst.update Layer1 4197 System update Layer 1
The communication topology within of communication layer 1 has changed. Check

the communication easYgen respectively LSx devices in layer 1.
CAN EthA redundancy 2439 The Load share interface CAN / Ethernet A redundancy is lost.
The device warns that the Ethernet redundancy CAN / EthA is lost. Check the
communication diagnostic screen of the layer 1.
9.5.5.12 Flexible Limits Monitoring
40 flexible limits. This text may be assigned customer defined. The Indication here
is the default text.
Flex. limit 1 10018
Flex. limit 2 10019
Flex. limit 3 10020
Flex. limit 4 10021
Flex. limit 5 10022
Flex. limit 6 10023
Flex. limit 7 10024
Flex. limit 8 10025
Flex. limit 9 10026
Flex. limit 10 10027

9 Appendix
9.5.5.13 Digital Inputs Monitoring
Flex. limit 40 . 10057
9.5.5.13 Digital Inputs Monitoring
Discrete input x Discrete input 1-12, energized / de-energized
The actual state of the monitored discrete input is energized / de-energized

(depending on the configuration) for at least the configured time. This text may be
assigned customer defined. The Indication here is the default text.
Discrete input 1 10600

9 Appendix
9.5.5.14 External Digital Inputs Monitoring
9.5.5.14 External Digital Inputs Monitoring
Ext. Discrete input x External discrete input 1-32, energized / de-energized
The actual state of the monitored discrete input is energized / de-energized

(depending on the configuration) for at least the configured time. This text may be
assigned customer defined. The Indication here is the default text.
Ext. Discrete input 1 16360

9 Appendix
9.5.5.15 Wire Break Monitoring (of internal and external analog inputs)
9.5.5.15 Wire Break Monitoring (of internal and external analog inputs)
Analog input x Wb: Analog input 1-3, wire break (internal analog inputs)
Wb: External Analog input 1-16, wire break (external analog inputs)
During the measurement of the analog input a wire break was detected. The text
begins with Wb: for wire break. The second part of the text may be assigned
customer defined. The Indication here is the default text.
Wb: Analog input 1 10014
Wb: External Analog 10221

input 1

input 2

input 3

input 4

input 5

input 6

input 7

input 8

input 9

9 Appendix

input 10

input 11

input 12

input 13

input 14

input 15

input 16
16 free configurable Alarms. The alarm text is configurable. The indication here is
the default text.
Free alarm 1 8120
Free alarm 2 8124
Free alarm 3 8128
Free alarm 4 8132
Free alarm 5 8136
Free alarm 6 8140
Free alarm 7 8144
Free alarm 8 8148
Free alarm 9 8154
Free alarm 10 8158
Free alarm 11 8165
Free alarm 12 8170
Free alarm 13 8174
Free alarm 14 8178
Free alarm 15 8182
Free alarm 16 8186
9.5.5.17 Miscellaneous Monitoring
Bat. overvoltage 1 10007 Battery overvoltage, limit value 1

9 Appendix
9.6 Formulas

The battery voltage has exceeded the limit value 1 for battery overvoltage.
Bat. overvoltage 2 10008 Battery overvoltage, limit value 2
The battery voltage has exceeded the limit value 2 for battery overvoltage.
Bat. undervoltage 1 10005 Battery undervoltage, limit value 1
The battery voltage has fallen below the limit value 1 for battery undervoltage.
Bat. undervoltage 2 10006 Battery undervoltage, limit value 2
The battery voltage has fallen below the limit value 2 for battery undervoltage.
Gen. AC wiring 10093 AC wiring issue of Generator voltages
One or more of the generator voltages are wrong wired (detected by plausibility
checking of frequencies).
Busbar 1 AC wiring 10094 AC wiring issue of Busbar voltages
One or more of the busbar voltages are wrong wired (detected by plausibility
Mains AC wiring 10095 AC wiring issue of Mains voltages
One or more of the mains voltages are wrong wired (detected by plausibility
PV disconnect level 8927 The PV source level drives generator into revers power.
The generator power has reached a reverse power with a critical rate. The PV
source penetration is interrupted.
CPU overload R1 trip 14799 An easYgen CPU overload has occured
With the CPU overload the self-test relais R1 was tripped.
Meas.difference 4105 5141 Measurement difference 4105
The own 4105 relevant mains measurement is different to the 4105 partner.
Missing member 4105 5129 Missing 4105 diagnostic partner
The easYgen finds no partner anymore to do 4105 diagnostic.
Para.alignment 4105 5135 Parameter alignment 4105 failure
The own 4105 relevant parameter are different to the 4105 partner.
9.6 Formulas
9.6.1 Conversion Factors
Temperature
°C → °F T [°F] = (T [°C] x 1.8) + 32
°F → °C T [°C] = (T [°F] – 32) / 1.8

9 Appendix
9.6.2 Load Dependent Start Stop (LDSS) Formulas
Pressure
bar → psi P [psi] = P [bar] x 14.503
psi → bar P [bar] = P [psi] / 14.503
The following formulas are used by the load-dependent start/stop function to determine
whether a genset is to be started or stopped.
Abbreviations
Abbreviation Parameter
PGN real active Momentary active generator real power on the busbar
Prated active Momentary active generator rated power on the busbar
Preserve Prated active – PGN real active
Preserve islanded 5760 Minimum permissible reserve power on busbar in islanded operation
Physteresis IOP 5761 hysteresis in islanded operation
PMN setpoint Export / import power control setpoint
PMN real Momentary active power at the interchange point
PMOP minimum 5767 Minimum requested generator load
Preserve parallel 5768 Minimum permissible reserve power on busbar in mains parallel
operation
Physteresis MOP 5769 Physteresis in mains parallel operation
Pmax. load islanded 5762 Maximum permissible generator load in islanded operation
Pmin. load islanded 5763 Minimum permissible generator load in islanded operation
Pmax. load parallel 5770 Maximum permissible generator load in mains parallel operation
Pmin. load parallel 5771 Minimum permissible generator load in mains parallel operation
LDSS mode "Reserve Power"
Task Formula
Islanded Operation
Changing the Engine Combination to Increase Rated Power PGNreal active + Preserve islanded > Prated active
Changing the Engine Combination to Reduce Rated Power PGN real active + Preserve islanded + Physteresis IOP < Prated
active
Mains Parallel Operation (Import/Export Control)
Starting the First Engine Combination (no engine supplies PMNsetpoint – PMN real + PGN real active > PMOP minimum
the busbar)
Changing the Engine Combination to Increase Rated Power PMNsetpoint – PMN real + PGN real active + Preserve parallel >
Prated active
Changing the Engine Combination to Reduce Rated Power PMNsetpoint – PMNreal + PGNreal active + Preserve parallel +
Physteresis MOP < Prated active

9 Appendix
Task Formula
Stopping the Last Engine Combination (load close to PMN setpoint – PMN real + PGN real active < PMOPminimum –
minimum load) Physteresis MOP
LDSS mode "Generator Load"
Task Formula
Islanded Operation
Changing the Engine Combination to Increase Rated Power PGN real active > Pmax. load islanded
Changing the Engine Combination to Reduce Rated Power PGN real active < Pmin. load islanded
(except dynamic setpoint is not matched)
Mains Parallel Operation (Import/Export Control)
Starting the First Engine Combination PMNsetpoint – PMN real + PGN real active > PMOPminimum
(no engine supplies the busbar)
Changing the Engine Combination to Increase Rated Power PGNreal active > Pmax. load parallel
Changing the Engine Combination to Reduce Rated Power PGN real active < Pmin. load parallel
(except dynamic setpoint is not matched)
Stopping the Last Engine Combination (load close to PMN setpoint – PMN real + PGN real active < PMOPminimum –
minimum load) Physteresis MOP
LDSS dynamic
Dynamic characteristic = [(max. generator load – min. generator load) * dynamic] + (min. generator
load)
Dynamic power level = (dynamic characteristic) * (generator rated power)
Constants Low dynamic = 25 %
Moderate = 50 %
dynamic
High dynamic = 75 %
☼ Example for moderate dynamic
• Dynamic characteristic = [(80 % – 40 %) * 50 %] + (40 %) = 60 %

• Dynamic power level = (60 %) * (200 kW) = 120 kW

10 Glossary And List Of Abbreviations

AM AnalogManager
BDEW German community of 1,800 companies represented by the

German Association of Energy and Water Industries
(Bundesverband der Energie- und Wasserwirtschaft)
SPN Suspect Parameter Number
FMI Failure Mode Indicator
OC Occurrence Count
CB Circuit Breaker
CL Code Level
CT Current Transformer
DI Discrete Input
DO Discrete (Relay) Output
ECU Engine Control Unit
EX-10 Woodward excitation module “easYgen | exciter 10"
GAP Graphical Application Programming (GAP™)
GC Group Controller
GCB Generator Circuit Breaker
GCP Woodward device series (Genset Control) - not preferred for new
design!
GGB Generator Group Breaker
GOV (speed) Governor; rpm regulator
HMI Human Machine Interface e.g., a front panel with display and
buttons for interaction
IOP Islanded Operation in Parallel ("Islanded Parallel Operation")
LM LogicsManager©
LSG Woodward device: Load Share Gateway (communication

converter)
MFR Woodward device series (multifunctional relays) - not preferred

for new design!
Operation In (general) operation.

State when the genset is running according to the selected
mode, all parameters are in allowed values and ranges, and
without OPEN requests or alarms. Somehow "waiting for next
occurrence".
S/N Serial Number
PT Potential (Voltage) Transformer

P/N Part Number
PLC Programmable Logic Control
PID Proportional Integral Derivative controller
PF Power Factor
PV Photovoltaic
N.O. Normally Open (make) contact
N.C. Normally Closed (break) contact
NC Neutral Contactor
MPU Magnetic Pickup Unit
MOP Mains Operation in Parallel
MCB Mains Circuit Breaker
LDSS Load-Dependent Start/Stop operation
V Voltage
I Current
P Real power
Q Reactive power
S Apparent power
Sequencer A sequencer file is carrying specific settings e.g. to enable

communication with and/or control of an expansion module.
Such files can be prepared by Woodward.

Index
Index
A
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542█
...........
Free configurable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544█

...........
AnalogManager sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638,

. . . . 639█
...........
BDEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484█
..........
Battery
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561,
. . . . 562█
...........
CAN
J1939 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549█

..........
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546,
. . . . 547█
...........
Contact person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37█

.........
Critical Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370█

...........
Customer Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37█

.........
Data Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051█

............
Droop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321█
..........
Engine
Overspeed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452█
...........
Shutdown Malfunction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459█

...........
Speed Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456█

..........
Start Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458█

...........
Underspeed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454█
...........
Unintended Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460█

...........
Engine/Generator

Index
Active Power Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437█

..........
Unloading Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438█

..........
Engine/Mains
Active Power Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520█

..........
Ethernet
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559█
...........
GCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526█
...........
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261█
...........
Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529█
...........
GCB 50BF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527█

..........
Generator
Ground Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444█

..........
Inverse Time-Overcurrent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419█

..........
Lagging Power Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439█

..........
Overfrequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413█
...........
Overvoltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406█
...........
Phase Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448█

...........
Pole Slip Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450█

...........
Reverse/Reduced Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429█

..........
Speed Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456█

..........
Unbalanced Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431█

...........
Underfrequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415█
...........
Undervoltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408█
...........
Voltage asymmetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410█

...........
Grid Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484█

..........
HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44█
.........
Translation Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153█

..........
Home Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114█

...........

Index
IOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387█
..........
Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37█

..........
islanded Parallel Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387█

...........
J1939 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549,

. . . . 553,
. . . . . 555,
. . . . 556,
. . . . . 557█
..........
LDSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377█
...........
Load Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334█

..........
Load Dependent Start Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377█

...........
Load Share Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311█

..........
Localization Tool (for customized 153█

language) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530█
...........
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268█
...........
MOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393█
...........
Mains
Blocking protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471█

..........
Change Of Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509█

..........
Decoupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474█
..........
Export Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518█

...........
General Mains Operating Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472█

..........
Import Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516█

...........
Lagging Power Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521█

..........
Leading Power Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524█

...........
QV Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506█

..........
Reconnecting Mains Operating Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474█

...........
Time-Dependent Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495█

...........
Underfrequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487█
...........

Index
Undervoltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491█
...........
Voltage Increase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493█

..........
Voltage Phase Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514█

..........
Mains Parallel Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393█

...........
Measurement
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572█
..........
Modbus
Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801█
...........
Modbus Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590█

..........
Telegram Mapper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800█

...........
Operating Range Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569█

..........
PID Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359█

..........
PV Photovoltaic
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355█
...........
Monitoring load reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564█

..........
Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38█
.........
Power Factor Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286█

...........
Reactive Power Q(P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305█

..........
Reactive Power Q(V) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301█

..........
Protective equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42█

.........
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37█
.........
Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35█
.........
System Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676█

...........
Diagnostic Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678█

..........
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568█
...........

Index
Temperature
Cylinder Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462█

..........
Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147█
..........
Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37█
.........
VDE-AR-N 4105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479█

...........
Voltage Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280█

...........
Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37█
..........

Woodward GmbH
Handwerkstraße 29 — 70565 Stuttgart — Germany
Phone +49 (0) 711 789 54-510
Fax +49 (0) 711 789 54-101
stgt-info@woodward.com

B37574 - TM - Easygen 3100 3200 XT P1 - J PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

B37574 - TM - Easygen 3100 3200 XT P1 - J PDF

Caricato da

Copyright:

Formati disponibili

easYgen-3000XT Series

Manual Genset Control

easYgen-3100XT-P1 / 3200XT-P1 / 3200XT-P1-LT

Software Version 2.10

Document ID: B37574, Revision: J - Build 47407

Designed in Germany and Poland.

Telephone: +49 (0) 711 789 54‑510

Fax: +49 (0) 711 789 54‑101

© 2020 Woodward GmbH

2 easYgen-3000XT Series B37574

Fig. 1: Scope of delivery

A Device easYgen-3200XT-P1 (sheet metal housing) or easYgen-3200XT-P1(-LT) genset

B IPS (Installation Procedure Supplement) and printed QR Code sticker - 2 x

C Clamp fastener installation material - 4 x (only plastic housing)

D Screw kit installation material - 12 x (only plastic housing)

Files stored at easYgen-XT device:

B37574 easYgen-3000XT Series 3

Sample application setup

Fig. 2: Sample application setup

4 easYgen-3000XT Series B37574

B37574 easYgen-3000XT Series 5

1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25█

1.1 About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25█

1.1.1 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25█

1.1.2 Depiction Of Notes And Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35█

1.2 Copyright And Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36█

1.3 Service And Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37█

1.4 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37█

1.4.1 Intended Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37█

1.4.2 Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38█

1.4.3 General Safety Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39█

1.4.4 Protective Equipment And Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42█

2 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44█

2.1 Display And Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44█

2.2 Application Modes Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44█

2.3 Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45█

3.1 Mount Unit (Sheet Metal Housing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46█

3.2 Mount Unit (Plastic Housing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48█

3.2.1 Clamp Fastener Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49█

3.2.2 Screw Kit Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51█

3.3 Setup Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53█

3.3.1 Terminal Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53█

3.3.2 Wiring Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55█

3.3.3 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59█

3.3.4 Charging Alternator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61█

3.3.5 Voltage Measuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61█

3.3.5.1 Generator Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61█

3.3.5.1.2 Parameter Setting '3Ph 4W' (3-phase, 4-wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63█

3.3.5.1.3 Parameter Setting '3Ph 3W' (3-phase, 3-wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64█

6 easYgen-3000XT Series B37574

3.3.5.1.4 Parameter Setting '1Ph 3W' (1-phase, 3-wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66█

3.3.5.1.5 Parameter Setting '1Ph 2W' (1-phase, 2-wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67█

3.3.5.2 Mains Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69█

3.3.5.2.1 Parameter Setting '3Ph 4W' (3-phase, 4-wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71█

3.3.5.2.2 Parameter Setting '3Ph 3W' (3-phase, 3-wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72█

3.3.5.2.3 Parameter Setting '1Ph 3W' (1-phase, 3-wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73█

3.3.5.2.4 Parameter Setting '1Ph 2W' (1-phase, 2-wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74█

3.3.5.3 Busbar Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76█

3.3.5.3.1 Parameter Setting '1Ph 2W' (1-phase, 2-wire) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77█

3.3.6 Current Measuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79█

3.3.6.1 Generator Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79█

3.3.6.1.1 Parameter Setting 'L1 L2 L3' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80█

3.3.6.2 Mains Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82█