Technical Manual EasYgen-3100XT - 3200XT-P1 (-LT), 7, en - US
Technical Manual EasYgen-3100XT - 3200XT-P1 (-LT), 7, en - US
Technical Manual EasYgen-3100XT - 3200XT-P1 (-LT), 7, en - US
easYgen-3000XT Series
Manual Genset Control
easYgen-3100XT-P1/3200XT-P1/3200XT-P1-LT
Release 1.14
37574F
Released
Woodward GmbH
Handwerkstrasse 29
70565 Stuttgart
Germany
Telephone: +49 (0) 711 789 54-510
Fax: +49 (0) 711 789 54-101
E-mail: [email protected]
Internet: http://www.woodward.com
© 2017
Brief Overview
Scope of delivery The following parts are included in the scope of delivery. Please
check prior to the installation that all parts are present.
Table of contents
1 General Information................................................................................................................ 19
2 System Overview..................................................................................................................... 35
3 Installation............................................................................................................................... 37
4 Configuration........................................................................................................................... 89
5 Operation............................................................................................................................... 467
9 Appendix................................................................................................................................ 607
11 Index....................................................................................................................................... 907
1 General Information
1.1 About This Manual
1.1.1 Revision History
n The devices are CSA certified (For details see Ä Chapter 8.1.8 “Approvals” on page 601).
n The device provides now the capability to create an own Modbus address point list, begin‐
ning 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 Ä Chapter 4.7.3 “Modbus Pro‐
tocol” on page 421.
n The device offers the capability to disable the password protection for the individual inter‐
face communication channels. If the password level is disabled the access level is set on
code level 5. For details see 9126 Ä p. 426, 9128 Ä p. 420, and 9129 Ä p. 445.
n 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
n Description, images, and tables updated according to the new features, functions, and cor‐
rections listed above.
n The Ethernet port is named Ethernet #1 or Ethernet A which means the same.
n Two symbols "generator Add-on/Add-off" explained (see Ä Chapter 4.1.5.4 “Sequencing”
on page 103).
n Load Control example updated (see Ä “Example 3: Islanded Parallel Operation (IOP)”
on page 269).
n NOTE added: Use Pin 61 or (metal housing) protective earth, see Ä Chapter 6.3.8 “Wiring
Self Powered Discrete Inputs” on page 506.
n More user-friendly description of remotely changing setpoints (see Ä Chapter 6.4.1.7
“Remotely Changing The Setpoint” on page 543 and Ä Chapter 6.5.1.3 “Remotely
Changing The Setpoint” on page 556).
n Settings proposal for J1939 communication with Cummins ECU (see Ä Chapter 7.6.2
“Supported J1939 ECUs & Remote Control Messages” on page 582).
n Product label with Unom (see Ä Chapter 8.1 “Technical Data” on page 595).
n 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
n LogicsManager References update:
– 07.xx: IDs changed
– 09.xx: IDs changed
– 10.xx: IDs changed
– 11.xx: IDs changed
– 13.xx: IDs changed
– 15.xx: IDs changed
n Layout optimizations and typo corrections.
n 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 Ä Chapter 4.3.5 “System Management”
on page 155.
n All monitoring functions in the device are from now on expanded with an additional func‐
tionality:
– Each monitor can be individually enabled by an internal LogicsManager flag.
(For example refer to parameter “Enabled” Ä Chapter 4.5.1.3.2 “Generator Overfre‐
quency (Level 1 & 2) ANSI# 81O” on page 308).
n 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.
n AnalogManager became even more flexible:
– 16 free configurable and accessible constants enable pre-sets to be used as Analog‐
Manager input. For details refer to Ä Chapter 4.9.2 “AnalogManager Constants”
on page 461 and Ä Chapter 4.9.1 “Operations” on page 452.
n Description, images, and tables updated according to the new features and functions listed
above.
n Wrench button (softkey) explained. For details refer to Ä Chapter 4.1.4.3 “Status/Moni‐
toring Screens” on page 100.
n Explained in more detail:
Corrections/Repairs
n Internal bugfixing.
Technical Manual
n The Wago DI/DO expansion boards are directly configurable now. Refer to Ä Chapter
4.7.5.1 “Expansion Modules at CANopen Interface” on page 432 for details.
n The idle mode will be entered into the event logger from now on.
n MPU (Speed sensor): The configuration allows now a minimum rated rpm of 100 rpm.
Refer to Ä “Magnetic pickup input (MPU)” on page 598 for details.
n The Period of use counter value is from now on available in the AnalogManager (11.58).
Refer to Ä Chapter 9.3.2.11 “Group 11: Clock And Timer” on page 826 for details.
Corrections/Repairs
n Measured frequencies:
The frequency evaluation in the device differentiates between all frequencies for moni‐
toring and phase-phase frequency for logic purposes.
n TEST mode:
Now in TEST mode [OFF] it is not possible anymore to trigger the TEST button LED, nei‐
ther via button nor via LogicsManager.
n Relay 7:
It can now be used, if GCB open command is configured as "Not used".
n Power factor setpoint sent by interface (ID508): Works with negative values, too.
n RPDOs: Work even with short negative integers.
n External DI status: Can be reset in all situations.
n Phoenix expansion boards:
When the Phoenix terminals are powered off the configuration will not be lost.
n RS485 in full duplex mode: Multiple slaves are supported.
n Relay 1 indication in ToolKit is inverted now, like in first generation easYgen-3000.
Technical Manual
n Changes and additional features driven by software update described as listed above.
n Chapter structure and sequence optimized like AnalogManager Reference. Refer to
Ä Chapter 9.4 “AnalogManager Reference” on page 856 for details.
n Layout optimizations and typo corrections.
n Name of parameter ID 2802 Ä p. 301 corrected.
n Range of LogicsManager command variables group 03, group 04, group 82, group 86, and
group 99 corrected.
n AnalogManager variables group 04 deleted.
n AnalogManager variables groups corrected.
n AnalogManager reference value description updated for better alignment with display/
ToolKit.
n Open transition mode is running correctly under all circumstances. Issue 1 of ERRATA
37619 is solved.
n Wrong alarm when device got power cycled during load sharing via Ethernet A is fixed.
“System update” and “Missing easYgen” work correctly.
n Operating range monitoring check item 12 (Error 12) is corrected.
n Issue with changing IP addresses after power cycling is fixed.
n EDS file visualization is corrected.
n Issue with Upper limit for secondary voltage Pt is fixed.
n The RESET command for max. current values is provided.
n Application mode GCB open:
The issue with a short open command , when closing the GCB from external, is fixed.
n Minor language issues are fixed.
n AnalogManager:
The "Unit" configurations in the Analog inputs were reworked.
Issue fixed with "HMI AnalogManagers" to be parametrized but not saved when no Pass‐
word 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:” on page 457 for
details.
n Corrections regarding the Load share gateway indication in the HMI are made.
n Minor rework of synchroscope.
n Prevent an unintended parameter default setting if a parameter was changed and shortly
(less than 3 seconds) after the power supply was switched off.
n
Technical Manual
n Changes and additional features driven by software update described as listed above.
n Description of using USB service port for ToolKit connection updated with more details.
Refer to Ä Chapter 4.2.4 “Connect ToolKit via USB Service Port” on page 122.
n Description of Firing Speed and Speed detection and configuration enhanced for better
understanding. Refer to Ä Chapter 4.4.1.2 “Engine Start/Stop” on page 163.
n Data Telegram updated:
– Protocol 3005 (Basic Visualization). For details please refer to description Ä Chapter
9.2.1 “Protocol 5003 (Basic Visualization)” on page 620.
n Layout optimizations and typo corrections.
n Release 5.0
Technical Manual
Notes
New device features & updates in comparison to easYgen-3000 series will be found in the tran‐
sition 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.
Up to date documentation?
Please check Woodward web site for latest revi‐
sion of this Technical Manual (search for: "37574")
and if there is an Errata Sheet with latest informa‐
tion (search for: "37619").
The Technical Manual saved inside the device
WILL NOT be automatically updated with a device
update but manual update can be done on custom‐
er's side using the USB connection.
DANGER!
This combination of symbol and signal word indi‐
cates an immediately-dangerous situation that
could cause death or severe injuries if not avoided.
WARNING!
This combination of symbol and signal word indi‐
cates a possibly-dangerous situation that could
cause death or severe injuries if it is not avoided.
CAUTION!
This combination of symbol and signal word indi‐
cates a possibly-dangerous situation that could
cause slight injuries if it is not avoided.
NOTICE!
This combination of symbol and signal word indi‐
cates a possibly-dangerous situation that could
cause property and environmental damage if it is
not avoided.
Additional markings To emphasize instructions, results, lists, references, and other ele‐
ments, the following markings are used in these instructions:
Marking Explanation
Step-by-step instructions
Marking Explanation
Dimensions in Figures
All dimensions shown with no units specified are in
mm.
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.
Warranty terms
Please enquire about the terms of warranty from
your nearest Woodward representative.
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.
n Intended use requires operation of the control unit within the specifications
listed in Ä Chapter 8.1 “Technical Data” on page 595.
n All permissible applications are outlined in Ä Chapter 2.2 “Application Modes
Overview” on page 35.
n Intended use also includes compliance with all instructions and safety notes
presented in this manual.
n Any use which exceeds or differs from the intended use shall be considered
improper use!
n 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
WARNING!
Hazards due to insufficiently qualified per‐
sonnel!
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.
Device implemented self test this Woodward device has a self test check implemented. Perma‐
nently under control are:
n processor function and
n supply voltage.
The internal signal "self check" is aligned in series with the inverse
signal “Ready for op. OFF” parameter 12580 Ä p. 183/Ä p. 184/
Ä p. 852. Per default (factory settings) discrete output R01 is ener‐
gized/closed if device itself is OK.
CAUTION!
Uncontrolled operation due to faulty configura‐
tion
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 gener‐
ator 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, elec‐
trical, 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.
Electrostatic discharge
Protective equipment: n ESD wrist band
NOTICE!
Damage from electrostatic discharge
All electronic equipment sensitive to damage from
electrostatic discharge, which can cause the con‐
trol unit to malfunction or fail.
– To protect electronic components from static
damage, take the precautions listed below.
5. Opening the control cover may void the unit warranty. Do not
remove the printed circuit board (PCB) from the control cab‐
inet unless instructed by this manual.
Notes on marine usage Marine usage of the easYgen genset control requires additional
precautions as listed below:
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 instruc‐
tions.
The cumulative required tools are detailed below:
Torque screwdriver
A torque-screwdriver allow fastening of screws to a precisely speci‐
fied torque.
n Note the required torque range individually specified in the
tasks listed in this manual.
2 System Overview
2.1 Display And Status Indicators
Restrictions
Full access to all parameters and settings with
ToolKit only!
3 Installation
NOTICE!
Avoid electrostatic discharge!
Before working with terminals please read and
follow the instructions of chapter Ä “Electrostatic
discharge” on page 32.
For CAN and RS485 shielded cabling, no more
than 25 mm wiring exposed without shield cov‐
erage are allowed at terminal plug side.
2. Mount the unit to the back panel and insert the screws.
Dimensions
Panel cutout
Measure Description Tolerance
3. Insert the four clamping screws into the clamp inserts from
the shown side (Fig. 10; 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.
Fig. 10: Insert screws in clamps
6. Tighten the clamping screws (Fig. 12/1) until the control unit
is secured to the control panel (Fig. 12/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.
NOTICE!
Avoid electrostatic discharge!
Before working with terminals please read and
follow the instructions of chapter Ä “Electrostatic
discharge” on page 32.
For CAN and RS485 shielded cabling, no more
than 25 mm wiring exposed without shield cov‐
erage 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 deliv‐
ered.
– For definite values please refer to chapter
Ä Chapter 8.1 “Technical Data” on page 595.
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²
AWG mm² AWG mm² AWG mm² AWG mm² AWG mm² AWG mm²
NOTICE!
Avoid electrostatic discharge!
Before working with terminals please read and
follow the instructions of chapter Ä “Electrostatic
discharge” on page 32.
For CAN and RS485 shielded cabling, no more
than 25 mm wiring exposed without shield cov‐
erage are allowed at terminal plug side.
The device terminals are allocated (similarly for all housing var‐
iants) as follows:
n Plastic housing - for easYgen-3200XT-P1 and
easYgen-3200XT-P1-LT
n Sheet metal housing - for easYgen-3100XT-P1
The max. possible conductor cross-section of the terminals
used is Amax = 2.5 mm2!
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!
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.
USB
terminals
USB Ethernet
Screw
Host
In Device #A
preparation
480 Vac
40
41
*1
Relay [R02] isolated
[R01] Busbar voltage (system1) L2/N
Fixed to Ready for operation
42
*1
Relay [R02] 480 Vac
38
43
[R02]
Preconfigured to Centralized alarm
*1
Busbar voltage (system1) L1
Relay [R03]
44
[R03]
Preconfigured to Starter
*1
Relay [R04] 480 Vac
36
45
[R04]
Preconfigured to fuel solenoid / gas valve
Generator voltage N
46
480 Vac
34
47
*1
Relay [R05] isolated
[R05] Generator voltage L3
Preconfigured to Preglow
48
*1 480 Vac
32
49
*1
Relay [R07] isolated 480 Vac
30
51
Terminals easYgen3100XT/3200XT
[R07] activated otherwise preconfigured to
52
„Mains decoupling“
*1 480 Vac
28
53
*1
Relay [R09] isolated
480 Vac
26
55
*1
Relay [R10]
480 Vac
24
57
*1
Relay [R11]
[R11] Preconfigured to Alarm class A or B
480 Vac
22
59
20
61
Earth
Analog output [AO 02]
(+/-10Vdc / +/-20mA / PWM) +
19
NC
62
[AO 02]
Voltage Biasing
Do not
+
18
63
17
64
16
65
[AO 01]
isolated
Engine
15
66
Emergency Stop
*1 [AI 03]
Discrete Input [D02] isolated
[D02] -
13
68
Start in Auto
*1 Analog Input Type 1
Discrete Input [D03] isolated
[D03] +
12
69
Alarm acknowledgement
*1 [AI 01]
Discrete Input [D06] isolated
[D06] -
72
Enable MCB
Discrete Input [D07] isolated
[D07] s1
73
Alarm input
*1 (isolated) L2
Discrete Input [D10] isolated
[D10] 1A / 5A compatible s2
76
Alarm input
1
Discrete Input [D11] isolated *
[D11] s1
77
Alarm input
L1
Discrete Input [D12] isolated *1
[D12] s2
78
+ Mains s1
79
1: RS485_A
1: CAN_GND CAN#3 1: CAN_GND RS485#1 2: RS485_B
terminals
terminals
Screw
Screw
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.
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.
Terminal Description
C 64 0 Vdc
Characteristics
Terminal Description
Generator voltage - L1 A 30
Generator voltage - L2 B 32
Generator voltage - L3 C 34
Generator voltage - N D 36
Measuring inputs
Terminal assignment
Measuring input / Phase Terminal
Generator voltage - L1 A 30
Generator voltage - L2 B 32
Generator voltage - L3 C 34
Measuring inputs
Terminal assignment
Measuring input / Phase Terminal
Generator voltage - L1 A 30
Generator voltage - L2 B 32
Generator voltage - L3 C 34
Generator voltage - N D 36
Measuring inputs
Terminal assignment
Measuring input / Phase Terminal
Generator voltage - L1 A 30
Generator voltage - L2 B 32
Generator voltage - L3 C 34
-/- -/- 36
Measuring inputs
Terminal assignment
Measuring input / Phase Terminal
Generator voltage - L1 A 30
Generator voltage - L3 C 34
Generator voltage - N D 36
B 32
Measuring inputs
Terminal assignment
Measuring input / Phase Terminal
Generator voltage - L1 A 30
Generator voltage - N B 32
C 34
D 36
Measuring inputs
Terminal assignment
Measuring input / Phase Terminal
Generator voltage - L1 A 30
Generator voltage - L2 B 32
Mains voltage - L1 A 22
Mains voltage - L2 B 24
Mains voltage - L3 C 26
Mains voltage - N D 28
Measuring inputs
Mains voltage - L1 A 22
Mains voltage - L2 B 24
Mains voltage - L3 C 26
Mains voltage - N D 28
Measuring inputs
Mains voltage - L1 A 22
Mains voltage - L2 B 24
Mains voltage - L3 C 26
-/- -/- 28
Measuring inputs
Mains voltage - L1 A 22
Mains voltage - L3 C 26
Mains voltage - N B 24
D 28
Measuring inputs
Mains voltage - L1 A 22
Mains voltage - N B 24
C 26
D 28
Measuring inputs
Mains voltage - L1 A 22
Mains voltage - L2 B 24
Measuring inputs
Busbar voltage - N B 40
Measuring inputs
Terminal Description
Terminal Description
F E D C B A
L1 L2 L3
Terminal 3 4 5 6 7 8
Terminal 3 4 5 6 7 8
Fig. 40: Current measuring - generator, 'Phase L1' 'Phase L2' 'Phase L3'
Wiring terminals
F E D C B A
Phase L1
Terminal 3 4 5 6 7 8
Wiring terminals
Phase L2
Terminal 3 4 5 6 7 8
Phase L3
Terminal 3 4 5 6 7 8
Terminal Description
Fig. 42: Current measuring - mains, 'Phase L1' 'Phase L2' 'Phase L3'
Wiring terminals
B A
Phase L1
Terminal 1 2
Phase L2
Terminal 1 2
Phase L3
Terminal 1 2
Terminal Description
Terminal Description
B 2
C 3 5 7 Generator current
D 4 6 8
Measuring 3PH 3W
The values of single active power, reactive power,
and power factor in L1, L2 and L3 are not dis‐
played. This values can not be determined through
this connection type.
Properties
Inductive Capacitive
Load type Electrical load whose current waveform lags the Electrical load whose current waveform leads the
voltage waveform thus having a lagging power voltage waveform thus having a leading power
factor. Some inductive loads such as electric motors factor. Some capacitive loads such as capacitor
have a large startup current requirement resulting in banks or buried cable result in leading power fac‐
lagging power factors. tors.
Inductive Capacitive
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 the A voltage raise "+" signal is output as long as the
measured value is "more inductive" than the refer‐ measured value is "more capacitive" than the refer‐
ence setpoint ence setpoint
Example: measured = i0.91; setpoint = i0.95 Example: measured = c0.91; setpoint = c0.95
Phasor diagram
The phasor diagram is used from the generator's
view.
Inductive Capacitive
Diagram
Overview
Terminal Description
Characteristic
Terminal Description
A B
Terminal Description
A B
Operation logic Discrete inputs may be configured to normally open (N.O.) or nor‐
mally closed (N.C.) states.
Terminal Description
N.O. Common
A B Form A
Notes
– LogicsManager: Using the function Logi‐
csManager it is possible to freely program the
relays for all application modes.
– : no breaker mode;
: GCB open
: GCB
: GCB/MCB
– N.O.: normally open (make) contact
NOTICE!
Damage to adjacent electronic components
due to induced voltages
– Implement protection circuits as detailed
below.
Wiring senders
Terminal Description
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 It is possible to combine single- and two-pole senders but with the
simultaneously lower accuracy.
CAUTION!
Connecting external power sources to the analog
Fig. 55: Analog controller output - two outputs may damage the device.
wires
I A 16 + Analog output
[AO 01]
Current B 17 GND
or
V*
Voltage
I A 19 + Analog output
[AO 02]
Current B 20 GND
or
V*
Voltage
NOTICE!
Avoid electrostatic discharge!
Before working with terminals please read and
follow the instructions of chapter Ä “Electrostatic
discharge” on page 32.
For CAN and RS485 shielded cabling, no more
than 25 mm wiring exposed without shield cov‐
erage are allowed at terminal plug side.
Pin assignment For location of interface 7 see Ä Chapter 3.4.1 “Interfaces over‐
view” on page 81.
Ter‐ Descrip‐ .. used for FULL ... used for HALF Amax
mina tion duplex mode duplex mode
l
RS-485 half-duplex
RS-485 full-duplex
'Read only' USB interface For location see Ä Chapter 3.4.1 “Interfaces overview” on page 81.
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 avail‐
able and all files prepared from Woodward manufacturing side.
Read/write attributes of this service port are restricted to read only.
Pin assignment For location of interface 5 and 6 see Ä Chapter 3.4.1 “Interfaces
overview” on page 81.
Topology
Please note that the CAN bus must be terminated
with a resistor, which corresponds to the impe‐
dance of the cable (e.g. 120 Ω, 1/4 W) at both
ends.
The termination resistor is connected between
CAN-H and CAN-L.
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).
1000 kbit/s 25 m
800 kbit/s 50 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 (rec‐
ommended) or also via an RC element on the opposite bus con‐
nection.
A shielded cable with shielded plug is required.
Troubleshooting
If there is no data transmission on the CAN bus,
check for the following common CAN bus commu‐
nication 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
Pin assignment For location of interface 8 see Ä Chapter 3.4.1 “Interfaces over‐
view” on page 81.
Pin Description 10Base-T 100Base-T
4 Not connected NC NC
5 Not connected NC NC
7 Not connected NC NC
Fig. 65: RJ-45 connector - Ethernet 8 Not connected NC NC
Notes
NC: Not connected
General notes Ethernet category 5 (STP CAT 5) shielded cable is required with
shielded plug RJ45. The chosen switch shall support a transmis‐
sion 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 cross‐
over 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 connec‐
tion.
Topology
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 and the Technical Manual “37593
RP-3000XT” .
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.
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.
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.
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 sep‐
arate softbutton - ToolKit offers the information
together with others as part of the
[States easYgen/Sequencing] screen.
Front Panel / HMI / display Please see chapter for detailed description of the front panel with
display and buttons.
Values [1] The "values" section (Fig. 70/1) of the screen illustrates all meas‐
ured power related information including voltages, currents, fre‐
quencies, power, and power factor values.
Status messages [2] The "status message" section (Fig. 70/2) of the screen shows the
actual operating information.
Alarm messages [3] The "alarm message" section (Fig. 70/3) of the screen shows the
last alarm message that is occurred and not yet acknowledged.
Single line diagram [4] The single line diagram (Fig. 70/4) shows the current status of the
engine and power circuit breakers.
Softkeys [5] The softkeys (Fig. 70/5) permit navigation between screens, levels
and functions as well as configuration and operation.
Display Display Mode Next step to display all measured (delta/wye) voltages one after
the other.
Code req. Request a blink code for one error message from the ECU.
Repeated pressing of this softkey displays all stored error mes‐
sages (J1939 Special 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 Dia‐ Rotating Field CW Generator, mains or busbar rotating field moves clockwise.
gram
Rotating Field CCW Generator, mains or busbar rotating field moves counter-clock‐
wise.
Monitoring Enabled Indicates that the engine delayed monitoring has expired and the
monitoring functions are enabled.
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 is
present present.
Alarm class A/B/C/D/E/F not Symbol without "!" indicates that an alarm of class A/B/C/D/E/F is
present not present.
Synchroscope Phase Angle Indicates the actual phase angle between busbar and mains or
busbar and generator.
Display alternatives The HOME screen allows a number of pre-selectable and soft‐
button controlled display variants.
n Generator
– Voltages (pp - pn) - selectable via softbutton [1]
– Power
– Power Factor PF
– Frequency
– Currents (L1, L2, L3)
n Generator/Mains
– Generator values as described above
and additionally for Mains
– Voltage
– Frequency
– Current
– Power
– Power factor
n Generator/Busbar
– Generator values as described above
and additionally for Busbar
– Voltage
– Power
– Frequency
n Generator/Engines
– Generator values as described above
and additionally for Engine
– Engine speed (rpm)
– Oil pressure (bar or psi)
– Water temperature (°C or °F)
– Operating hours (h)
– Battery voltage (V)
– Fuel level (%)
Softkey Description
Status/Monitoring Notes
screen
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.
Engine (J1939) —
J1939 Status —
Version —
Load diagnostic —
Symbol/Softkey Description
4.1.5.4 Sequencing
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
Sequence is running with respect to the settings e.g., the sequencing timing - see
table below:
The remaining time is displayed on the upper right side on the grey
bar "Sequencing ...", see table below:
Sequencing Minimum Shows the remaining time the Minimum run time,
run time ... s own generator is running at 13276 Ä p. 892
minimum
Symbol/Softkey Description
Segment number
Symbol Description
Symbol/Softkey Description
Setpoint for ... ... in AUTO ... in MANUAL ... in TEST mode
mode mode
The 12 o'clock position on the top means 0° and the 6 o'clock posi‐
tion 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.
Symbol/Softkey Description
Symbol Description
Variable is TRUE.
Variable is FALSE.
4.1.5.12 LogicsManager
Some parameters of the easYgen are configured via the Logi‐
csManager.
Symbol/Softkey Description
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”
Notes:
TEST mode is deactivated not only by this button but too:
Restricted Access
The function Mains Decoupling Test is available on
Code level CL3. Code levels CL0 to CL2 are inten‐
tionally not supported. Refer to Ä Chapter 4.3.4
“Enter Password” on page 140 for details.
CAUTION!
This function is independent from the breaker
status and is active for 1 sec.
No thresholds are considered.
State is TRUE
Symbol Description
State is false
Section Description
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
State is TRUE
State is false
Section Description
RPDO has incorrect mapping parameters / (The mapping is done automatically by the parameter 15320 Ä p. 437
“Select external terminals”)
TPDO 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.
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
Section Description
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.
4.1.5.18 USB
Current USB state is displayed. Setting can be found under
“Next Page è Diagnostic è Interfaces è USB”.
4.1.5.19 RS-485
Current RS-485 interface state is displayed. Setting can be found
under “Next Page è Diagnostic è Interfaces è RS485”.
Scania S6: Reset the blink code. To do this, disable the igni‐
tion (terminal U15), press this softkey, and enable the igni‐
tion again within 2 seconds.
Other ECU: Reset ECU failure codes.
Event Description
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 con‐
tact for conversion/update instruction to use
files created with easYgen.
Minimum system requirements n Microsoft Windows® 10, 8.1, 7, Vista (32- & 64-bit)
n Microsoft .NET Framework 4.5.1 or higher
n 1 GHz or faster x86 or x64 processor
n 1 GB of RAM
n Screen
– Resolution: 800 by 600 pixels
– Colors: 256
n If using USB service port of the easYgen for ToolKit communi‐
cation:
– USB port
– USB 2.0 cable (with type A and type B connector)
n If using Ethernet port of the easYgen for ToolKit communica‐
tion
– Appropriate Ethernet cable
n To install ToolKit and manage configuration files
– CD-ROM drive
Installation
To install ToolKit:
Hidden folder?
Depending on the (version of your) operating
system, the preferred folder for installation
"C:/ProgramData" can be hidden by default
WINDOWS settings. Installation will work
properly but installed sub-folders might not
be visible.
Two possible solutions:
– Change WINDOWS settings to see
hidden files (e.g. in Windows explorer tab
“Extras” , “Folder options” , tab “View” ,
check box "...show.." below “Hidden files
and folders” )
– Select another (not hidden) directory/
folder for installation when asked for
during installation.
ToolKit files
*.WTOOL
File name composition: [P/N1]1-[Revision]_[Language ID]_[product name short form]_[# of Release]-[# hotfix]_[#
of build].WTOOL
File content: Display screens and pages for online configuration, which are associated with the
respective *.SID file.
*.SID
File name composition: [Product name short form]_[# of Release]-[# hotfix]__[# of build].].SID
*.WSET
File content: Default settings of the ToolKit configuration parameters provided by the SID file or user-
defined settings read from the unit.
Notes
New settings DON'T override Ethernet address!
Local ports
The number of the COM port used for USB con‐
nection depends on your configuration. This
sample is using COM4.
2. Check
3. Start easYgen and wait for "normal operation"
4. Connect the Woodward device and the PC/laptop ToolKit is
running on with the USB cable
ð USB drive will be automatically detected: WINDOWS
offers pre-selected next step e.g., open in explorer what
would display files on the easYgen-XT device but is not
needed now
5. Open ToolKit
ð wtool selection window opens
6. Select the .wtool file for your device by double click
Fig. 120: USB device @ COM4 ð ToolKit Home Page (empty) opens
7. Click on “Connect”
ð Network selection window opens
8. Select COM4 - the USB port
9. Click on “Connect”
ð Connection will be established
Security Login window opens
Network restrictions
Both the easYgen control and your ToolKit running
computer/laptop (PC) must be in the same IP
address range. For example if the IP address of
easYgen is 10.31.140.20, the IP address of the PC
must be 10.31.140.xxx.
It is as well recommended to use an isolated/dedi‐
cated network for ToolKit communication (Anti-
virus software sometimes may interfere with the
Ethernet network). Please consult your IT team for
adjustment help.
Fig. 122: IP-address: Ethernet A
7. Click on “Connect”
ð Connection will be established
Security Login window opens
8. Log in with your “Username” and “Password”
Fig. 123: Select TCP/IP for ToolKit
ð ToolKit is opened and homepage is displaying current
connection states and values
CAUTION!
Avoid using the same IP address twice!
By mistake it is possible to assign the same IP
address twice to two different devices e.g. for
Remote Panel RP-3000XT as in the system is con‐
figured for the easYgen-3000XT so far.
In this case the last configured device
(RP-3000XT) will work properly but the so far con‐
figured device (easYgen-XT) will be invisible on
the Ethernet: Load Share and ToolKit do not
work on this device! ... and cannot be found for
remote connection.
Solution:
– Apply again properly IP addresses for devices
A and B
or
– reset easYgen-XT (power cycle)
Network mismatch using the same IP address
twice with other devices can be handled similarly.
Buttons “Previous visited page” and Go to the previous/next visited page (as
“Next (already) visited page” ordered in the list)
Visualization
Values displayed by visualization graphical ele‐
ments cannot be changed.
Search
[Ctrl][F]
The short cut ctrl-F works to open ToolKit search
window.
Value trending The value trending view can chart up to eight values over time.
Viewed range!
The range to be exported depends on the view and
the start position of the time bar but is always
reported 'til the end of charting.
To export all (complete report) time marker must
be at start position or the complete graph must be
Fig. 126: Trending screen viewed.
Details ... of connection The bottom of the ToolKit screen comes with information about
connection and a button for more “Details ...” .
With a click on “Details ...” a list of all current connections will be
displayed and further buttons appear:
4.2.8 How to use (and prepare/update) non-XT easYgen ... .wset files
4. Click [OK]
ð Window “Setting Differences ” appears
5. Click on button “Resolve Differences” for details
6. Go through the left hand side list and select settings found
ð If possible, ToolKit offers you to “Map” the setting for
easYgen-XT
Every mapped setting is listed below
7. Close mapping with a click on “OK” button and - back on
“Settings Differences” screen - with “Next >” button
ð “Settings Conversion Finished” screen lists all Errors and
Warnings
8. Click “Next >” to finalize settings loading
9. Define location/folder and name of the updated ... .wset file
10. Click [OK]
ð New updated ... .wset file is saved and ready for usage
with easYgen-XT
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
1700 Language 0 selectable lan‐ The desired language for the unit display text is configured here.
guages
(Set language) Available languages are: English, German, Dutch, Spanish, French, Italian,
[English] Portugese, Japanese, Chinese, Russian, Turkish, Polish, Slovakian, Finnish,
Swedish.
“Values to be set”
1710 Hour 0 hour 0 to 23 h
The hour of the clock time is set here.
1709 Minute 0 0 to 59 min The minute of the clock time is set here.
[real-time Example
clock]
n 0 = 0th minute of the hour
n 59 = 59th minute of the hour
1698 Transfer time 2 Yes Yes transfers the time values to the clock.
to clock
[No] Notes
ALL values are transferred and overwritten - even if you want to change only
one.
1699 Transfer data 2 Yes Yes transfers the date values to the clock.
to 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 used com‐
pared to the absolutely Greenwich Mean Time (GMT).
[0.00]
This information is needed to transfer the general time signal into the local
real-time clock setting.
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.
Example
Notes
This parameter is only displayed, if Daylight saving time (param‐
eter 4591 Ä p. 132) is set to "On".
4598 DST begin 2 Sunday to Sat‐ The weekday for the DST begin date is configured here
weekday urday
Notes
[Sunday]
This parameter is only displayed, if Daylight saving time (param‐
eter 4591 Ä p. 132) is set to "On".
4592 DST begin nth. 2 The order number of the weekday for the DST begin date is configured here.
weekday
[1st] DST starts on the 1st configured weekday of the DST begin month.
2nd DST starts on the 2nd configured weekday of the DST begin month.
3rd DST starts on the 3rd configured weekday of the DST begin month.
4th DST starts on the 4th configured weekday of the DST begin month.
Last DST starts on the last configured weekday of the DST begin month.
LastButOne DST starts on the last but one configured weekday of the DST begin month.
LastButTwo DST starts on the last but two configured weekday of the DST begin month.
LastButThree DST starts on the last but three configured weekday of the DST begin month.
Notes
This parameter is only displayed, if Daylight saving time (param‐
eter 4591 Ä p. 132) is set to "On".
4593 DST begin 2 1 to 12 The month for the DST begin date is configured here.
month
[1] Example
Notes
This parameter is only displayed, if Daylight saving time (param‐
eter 4591 Ä p. 132) is set to "On".
4597 DST end time 2 0 to 23 The real-time clock will fall back by one hour when this time is reached on the
DST end date
[0]
Example
Notes
This parameter is only displayed, if Daylight saving time (param‐
eter 4591 Ä p. 132) is set to "On".
4599 DST end 2 Sunday to Sat‐ The weekday for the DST end date is configured here
weekday urday
[Sunday]
Notes
This parameter is only displayed, if Daylight saving time (param‐
eter 4591 Ä p. 132) is set to "On".
4595 DST end nth. 2 The order number of the weekday for the DST begin date is configured here.
weekday
[1st] DST ends on the 1st configured weekday of the DST begin month.
2nd DST ends on the 2nd configured weekday of the DST begin month.
3rd DST ends on the 3rd configured weekday of the DST begin month.
4th DST ends on the 4th configured weekday of the DST begin month.
Last DST ends on the last configured weekday of the DST begin month.
LastButOne DST ends on the last but one configured weekday of the DST begin month.
LastButTwo DST ends on the last but two configured weekday of the DST begin month.
LastButThree DST ends on the last but three configured weekday of the DST begin month.
Notes
This parameter is only displayed, if Daylight saving time (param‐
eter 4591 Ä p. 132) is set to "On".
4596 DST end 2 1 to 12 The month for the DST begin date is configured here.
month
[1] Example
Notes
This parameter is only displayed, if Daylight saving time (param‐
eter 4591 Ä p. 132) is set to "On".
ID Parameter Setting
Notes
The max. number of characters is 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" auto‐
matically if the corresponding parameter for conversion 3630 Ä p. 184 and/or
3631 Ä p. 184 is configured to YES.
Display bright‐ 2 0 to 100% Color bar visualization for immediately displayed selection
ness
[35]%
4557 Key activation 2 1 to 999 min If no soft key has been pressed for the time configured here, the 2nd display
time brightness will be used.
[120 min]
Notes
This parameter is only effective, if LogicsManager 86.33 2nd disp.
bright. 11971 Ä p. 834/Ä p. 845 is configured to "Key activation".
7794 Enable 2nd 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the brightness
display bright‐ LogicsManager level of the display switches to the 2nd brightness level defined by parameter
ness 86.33 7796 Ä p. 137.
[(04.64 NOT& This can save energy and support visualization of device/system state.
1) & 1]
[(0 & 1) & 1] For information on the LogicsManager and its default settings see Ä Chapter
4.8 “Configure LogicsManager” on page 448Ä Chapter 9.3.1 “LogicsManager
= 11924 Overview” on page 811.
4103 Home screen 2 : Home screen can display several pre-defined data collections.
data
Generator Generator relevant information are displayed.
[Generator/ Home screen is splitted and displays generator and mains related informa‐
Mains] tion.
Generator/ Home screen is splitted and displays generator and busbar related informa‐
Busbar tion.
Generator/ Home screen is splitted and displays generator and engine related informa‐
Engine tion.
4129 Oneline dia‐ 2 Off : Display of oneline (single line) diagram on home screen can be
gram with reduced NOT to show mains symbols.
mains [On]
Notes
Softbutton for MCB is (visible and) valid only if this parameter is TRUE.
8891 AM Engine 2 Determined by With this AnalogManager the according speed source may be selected from
speed AnalogManager the available data sources.
81.24
Even it is possible to select all data sources Ä Chapter 9.4.1 “Data Sources
[A1 = 11.51 AM” on page 856), only the following data source may be used:
Engine speed
[rpm]] 11.51 Engine speed [rpm]
The indication is displayed in the format 0000 rpm.
8893 AM Engine oil 2 Determined by With this AnalogManager the according oil pressure source can be configured
pressure AnalogManager and scaled. The indication is displayed in the format 00.0bar (000psi).
81.25
[A1 = 07.07
100:Engine Oil
Press.]
Notes
If “bar” is assigned the unit will be converted into "psi" automatically if the
corresponding parameter for conversion 3630 Ä p. 184 is configured to YES.
8894 Show oil pres‐ 2 Yes Display of engine oil pressure on home screen.
sure
[No]
8895 AM Engine 2 Determined by With this AnalogManager the according operating hours source can be con‐
hours AnalogManager figured and scaled. The indication is displayed in the format 00000.00h .
81.26
[A1 = 11.55
Eng.oper.hour
s [h]]
8896 Show engine 2 [Yes] Display of engine running hours on home screen.
hours
No
8897 AM Engine fuel 2 Determined by With this AnalogManager the according fuel level source can be configured
level AnalogManager and scaled. The indication is displayed in the format 000.0% .
81.27
[A1 = 06.03
Analog input 3]
8898 Show engine 2 Yes Display of engine fuel level on home screen.
fuel level
[No]
8899 AM Engine 2 Determined by With this AnalogManager the according battery voltage source can be config‐
batt.voltage AnalogManager ured and scaled. The indication is displayed in the format 00.0V .
81.28
[A1 = 10.54
Battery voltage
[V]]
8900 Show engine 2 [Yes] Display of engine battery voltage on home screen.
battery voltage
No
8901 AM Engine 2 Determined by With this AnalogManager the according coolant temperature source can be
coolant temp. AnalogManager configured and scaled. The indication is displayed in the format 000°C (°F).
81.29
Notes
[A1 = 07.15
110:Eng.Coola If “°C” is assigned the unit will be converted into "°F" automatically if the cor‐
nt Temp.] responding parameter for conversion 3631 Ä p. 184 is configured to YES.
8902 Show engine 2 [Yes] Display of engine coolant temperature on home screen.
coolant temp.
No
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.
Remote Panel with the Woodward screen share concept connected over Ethernet (HMI simula‐ ③=①
tion)
3rd party Remote Panel (i.e. Proface, Sütron, ...) running Modbus TCP ④
Netbiter® Easy Connect gateway running Servlink TCP (ToolKit via internet) ⑤
Two login procedures cover all access channel variants: The ...
n Basic Code Entry
n User Account Entry
LOGIN procedure "Basic Code The Basic Code Entry is valid for access ①, ③, ⑥, and ⑦.
Entry"
The Basic Code Entry asks for four numbers to open the related
password level. It starts with the default value of parameter
10416 Ä p. 153 “Random number for password” .
LOGIN procedure "User Account The User Account Entry is valid for access ②, ④, and ⑤.
Entry"
The User Account Entry comes with more security as requested for
internet access. It asks for “Username:” and “Password:” ("Alpha‐
numeric Password"). To open the related password level, both
rows entries need the correct alphanumeric strings.
Enter Password for level ... (Over‐ A distinction is made between the access levels as follows:
view)
4 AC04 Algorithm Code Algorithm Code The temporary Super Commissioning Level
The same access rights like in the Super Commis‐
sioning Level but with the following exceptions:
Access Channels
Maximum Security
Each of these channels have their own inde‐
pendent access level. That has the advantage that
e.g. a HMI channel password level opens not auto‐
matically 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.
CAN1 CANopen
CAN2
The different Password Code This chapter defines the properties of the single password code
Levels 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 configu‐
rations are blocked.
The operator reads on that page The higher instance calculates: (10414
10416 Ä p. 153 “Random number for “Code temp. commissioning” + 10416
password” . He tells it to a higher instance. “Random Number” ) x 3.
The higher instance calculates: (10414 The higher instance takes the lower four
“Code temp. commissioning” + 10416 digits of the result and tells it the operator.
“Random Number” ) x 3. 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 pass‐
word into the control.
Automatic Logout from Password All basic code entry channels deny after 2h
level (Fall into level 0)
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 Pass‐ All basic code entry channels with [0] as password or a wrong
word levels (Fall into level 0) password
The ToolKit Servlink access with logout function
The Modbus TCP (in all channels) with wrong password
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 supports only the Basic Code entry.
the easYgen
Password handling in ToolKit The ToolKit supports the User Account entry and in case of CAN‐
open 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 The easYgen must be a member of an Ethernet network and both
TCP using Ethernet connection user name and password have to be transferred (from PLC) to the
device.
Set easYgen-XT to code level With factory settings username is expected to be "CL05" and
CL05 via Modbus TCP 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-0
0-00-00-00
for "User name" to parameter 7490 Ä p. 151 (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-0
0-00-00-00
for "Password" to parameter 7491 (40 bytes).
ð Code level can be read with parameter 10427
Password handling via Modbus The easYgen must be a member of a RS-485 network and the
using RS-485 connection password has to be transferred (from PLC) to the device.
Set easYgen-XT to code level 5 With factory settings the password is expected to be "500" for
via Modbus RS-485 code level 5.
n Modbus address = 400000 + (Par. ID + 1) = 410431
n 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 The easYgen must be a member of a CANopen network and the
CANopen connection 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 With factory settings the password is expected to be "500" for
via CANopen code level 5.
Procedure for CAN 1 n CAN interface 1 Parameter ID = 10402 (dec) = 28A2 (hex)
n Incorporate the 2000 (hex) value: 28A2(hex) + 2000 (hex) =
48A2 (hex)
n Identifier: 600 (hex) + Node-ID
n Example Node-ID is 1
The following table shows exemplary send data for the device on
the CANopen bus.
Procedure for CAN 2 n CAN interface 2 Parameter ID = 10432 (dec) = 28C0 (hex)
n Incorporate the 2000 (hex) value: 28C0 (hex) + 2000 (hex) =
48C0 (hex)
n Identifier: 600 (hex) + Node-ID
n Example Node-ID is 1
The following table shows exemplary send data for the device on
the CANopen bus.
Code level display The current code level is indicated by the lock symbol in the config‐
uration 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
10400 Password dis‐ 0 0000 to 9999 The password for configuring the control via the front panel must be entered
play here.
[random
number]
10405 Code level dis‐ 0 (display only) This value displays the code level which is currently enabled for access via
play the front panel display or the Woodward Remote Panel with screen share
[0] mode.
Code level interfaces The password and/or User name for access via interface cannot be
entered via HMI.
10402 Password for 0 0000 to 9999 The password for configuring the control via the CAN interface #1 must be
CAN interface entered here.
1 [random
number] Not visible but can be accessed by interface!
10407 Code level 0 [0] This value displays the code level which is currently enabled for access via
CAN interface the CAN interface #1.
1
10432 Password for 0 0000 to 9999 The password for configuring the control via the CAN interface #2 must be
CAN interface entered here.
2 [random
number] Not visible but can be accessed by interface!
10422 Code level 0 [0] This value displays the code level, which is currently enabled for access via
CAN interface the CAN interface #2.
2
7486 Code level for 0 [0] This value displays the code level, which is currently enabled for access via
USB the USB interface.
The password is entered via the ToolKit login window.
10430 Password for 0 0000 to 9999 The password for configuring the control via the RS485 interface must be
serial interface entered here.
[random
number] Not visible but can be accessed by interface!
10420 Code level for 0 [0] This value displays the code level, which is currently enabled for access via
RS485 the RS485 interface.
7490 User name 0 The user name for configuring the control via the Modbus TCP/IP interface
Modbus TCP must be entered here.
Not visible but can be accessed by interface!
7491 Password 0 0000 to 9999 The password for configuring the control via the Modbus TCP/IP interface
Modbus TCP/IP must be entered here.
[random
number] Not visible but can be accessed by interface!
10427 Code level 0 [0] This value displays the code level, which is currently enabled for access via
Modbus TCP/IP the Modbus TCP/IP interface.
7816 IP Servlink 0 [0] This is the IP address of the PC that is connected via ToolKit with the device
Master 1 as Servlink Master 1.
7824 Code level 0 [0] This value displays the code level, which is currently enabled for access as
Servlink Servlink Master 1.
Master 1
7817 IP Servlink 0 [0] This is the IP address of the PC that is connected via ToolKit with the device
Master 2 as Servlink Master 2.
7825 Code level 0 [0] This value displays the code level, which is currently enabled for access as
Servlink Servlink Master 2.
Master 2
7818 IP Servlink 0 [0] This is the IP address of the PC that is connected via ToolKit with the device
Master 3 as Servlink Master 3.
7826 Code level 0 [0] This value displays the code level, which is currently enabled for access as
Servlink Servlink Master 3.
Master 3
7819 IP Servlink 0 [0] This is the IP address of the PC that is connected via ToolKit with the device
Master 4 as Servlink Master 4.
7827 Code level 0 [0] This value displays the code level, which is currently enabled for access as
Servlink Servlink Master 4.
Master 4
7820 IP Servlink 0 [0] This is the IP address of the PC that is connected via ToolKit with the device
Master 5 as Servlink Master 5.
7828 Code level 0 [0] This value displays the code level, which is currently enabled for access as
Servlink Servlink Master 5.
Master 5
7821 IP Servlink 0 [0] This is the IP address of the PC that is connected via ToolKit with the device
Master 6 as Servlink Master 6.
7829 Code level 0 [0] This value displays the code level, which is currently enabled for access as
Servlink Servlink Master 6.
Master 6
7822 IP Servlink 0 [0] This is the IP address of the PC that is connected via ToolKit with the device
Master 7 as Servlink Master 7.
7830 Code level 0 [0] This value displays the code level, which is currently enabled for access as
Servlink Servlink Master 7.
Master 7
7823 IP Servlink 0 [0] This is the IP address of the PC that is connected via ToolKit with the device
Master 8 as Servlink Master 8.
7831 Code level 0 [0] This value displays the code level, which is currently enabled for access as
Servlink Servlink Master 8.
Master 8
10415 Password 1 1 to 9999 The password for the code level "Basic" is defined in this parameter.
Basic
[-] Refer to Ä Chapter 4.3.4 “Enter Password” on page 140 for default values.
10413 Password 3 1 to 9999 The password for the code level "Commissioning" is defined in this param‐
commissioning eter.
[-]
Refer to Ä Chapter 4.3.4 “Enter Password” on page 140 for default values.
10414 Code temp. 3 1 to 9999 The algorithm for calculating the password for the code level "Temporary
commissioning Commissioning" is defined in this parameter.
[200]
10412 Code temp. 5 1 to 9999 The algorithm for calculating the password for the code level "Temporary
super commis‐ Super commissioning" is defined in this parameter.
sioning [400]
10411 Password 5 1 to 9999 The password for the code level "Super commissioning" is defined in this
super commis‐ parameter.
sioning [500]
Refer to Ä Chapter 4.3.4 “Enter Password” on page 140 for default values.
10437 Alphanumeric 3 (up tp 6 charac‐ Alphanumeric code for temporary commissioning level.
code temp. ters)
comm. This is the alphanumeric algorithm value for the formula to reach the tempo‐
[a9t5] rary commissioning code level (Level 02), entered as string here.
10438 Alphan. code 5 (up tp 6 charac‐ Alphanumeric code for temporary super commissioning level
temp. super ters)
comm. This is the alphanumeric algorithm value for the formula to reach the tempo‐
[xk38] rary commissioning code level (Level 04), entered as string here.
10416 Random [(random four Random number generated by the easYgen-XT device. Needed to get an
number for letters alphanumeric password by Woodward support.
password number)]
10439 Old password 1 ((empty)) Enter here your old alphanumeric password to release the password change
basic level for the basic code level (CL01)
10440 New password 1 ((empty)) Enter here your new alphanumeric password string for the basic code level
basic level (CL01)
10441 Confirm pass‐ 1 ((empty)) Repeat here your new alphanumeric password string for the basic code level
word basic level (CL01)
10442 Change pass‐ 1 [No] With switching this parameter to yes, the control checks the entries for
word basic level changing the password and executes the password change, if the entries are
Yes 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.
10434 Reset pass‐ 2 Yes The control resets the password of the basic level to "CL0001".
word basic
level [No]
10444 Old password 3 ((empty)) Enter here your old alphanumeric password to release the password change
commiss. level for the commissioning code level (CL03)
10445 New password 3 ((empty)) Enter here your new alphanumeric password string for the commissioning
commiss. level code level (CL03)
10446 Confirm pass‐ 3 ((empty)) Repeat here your new alphanumeric password string for the commiss. code
word com‐ level (CL03)
miss.level
10447 Change pass‐ 3 [No] With switching this parameter to “Yes” , the control checks the entries for
word commiss. changing the password and executes the password change, if the entries are
level Yes correct. The visualization 1048 indicates the successful execution.
Notes
If the parameters 10444, 10445, and 1046 are not correct, the password
change is not executed.
10435 Reset pass‐ 4 Yes The control resets the password of the commissioning level to "CL0003".
word commiss.
level [No]
10449 Old passw. 5 ((empty)) Enter here your old alphanumeric password to release the password change
super comm. for the super comm. code level (CL05)
level
10450 New passw. 5 ((empty)) Enter here your new alphanumeric password string for the super comm. code
super comm. level (CL05)
level
10451 Confirm 5 ((empty)) Repeat here your new alphanumeric password string for the super comm.
passw.super code level (CL05)
comm.level
10452 Change 5 [No] With switching this parameter to “Yes” , the control checks the entries for
passw.super changing the password and executes the password change, if the entries are
comm. level Yes correct. The visualization 1053 indicates the successful execution.
Notes
If the parameters 10449, 10450, and 1051 are not correct, the password
change is not executed.
10436 Reset passw. 11 Yes The control resets the password of the commissioning level to "CL0005" e.g.,
super comm. if you forgot your password.
level
Notes
The code level to execute the password reset is provided by your Woodward
sales support partner.
[No]
CAUTION!
Don't initiate “Set factory default settings”
during controlling a genset! This causes
easYgen rebooting.
Parameter 1701 Ä p. 156 “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.
1702 Device number 2 1 to 32 A unique address is assigned to the control though this parameter. This
unique address permits the controller to be correctly identified on the CAN
[1] bus. The address assigned to the controller may only be used once.
All other bus addresses are calculated on the number entered in this param‐
eter.
The device number is also important for the device assignment in load
sharing and load-dependent start/stop.
Notes
The unit must be restarted after changing the device number to ensure proper
operation.
For multiple genset applications please make sure to change parameter
8950 Ä p. 425 as well
1889 Device name 2 [Device_name] After set with parameter 1893 this customer specific device name is used e.g.
preset as device name in Ethernet network.
12 to 38 charac‐
ters but varies
on font
Notes
Recommended are 19 ASCII characters max. Blanks and special characters
will be replaced.
1893 Set device 2 [No] YES: Device name typed in as value of parameter 1889 taken, processed,
name and displayable characters saved as parameter 1890.
Yes
10417 Factory default 0 Yes The following three parameters are visible and restoring the configured
settings 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 4 Yes All parameters, with the exception of customer defined passwords, will be
default values 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!
In case of ToolKit connected via USB service port: USB connection will be
lost!
Notes
This parameter is only displayed, if factory default settings (parameter
10417 Ä p. 156/Ä p. 570) is set to "Yes".
Notes
All functions which are described here, may be assigned by the LogicsMan‐
ager to any relay that is available via the LogicsManager and not assigned to
another function.
3347 Preglow mode 2 This parameter dictates if and under what conditions a diesel engine is pre‐
heated.
3309 Preglow tem‐ 2 -10 to 250 °C This is the temperature threshold, which must be exceeded to prevent a pre‐
perature heating process, if parameter 3347 Ä p. 158 has been set to "Analog".
threshold [0 °C]
(Diesel engine
only)
4057 Pre-excitation 2 [On] When the engine is starting up, an exciting current is issued.
D+
Notes
The resulting voltage at terminal 65 can be monitored. Refer to chapter
Ä Chapter 4.5.2.7 “Engine Charge Alternator (D+)” on page 340 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 2 Determined by The preglow criterion may be selected from the available data sources.
criterion AnalogManager
81.01 Usually, a temperature measuring is selected here, which is measured via a
(Diesel engine sensor.
only) [A1 = 10.01
ZERO] Notes
Refer to Ä Chapter 4.9 “Configure AnalogManager” on page 452 for explana‐
tion how to use the AnalogManager.
Refer to Ä Chapter 9.4.1 “Data Sources AM” on page 856 for a list of all data
sources.
3310 Ignition delay 2 0 to 9999 s With gas engines often a purging operation is desired before starting.
[tID]
[5 s] With the engaging of the starter the ignition delay is started. The display indi‐
(Gas Engine cates "Turning".
only)
If the "Minimum speed for ignition" is reached after the expiration of this time,
the ignition is energized.
3311 Gas valve 2 1 to 999 s By energizing the ignition relay the gas valve delay is started ("Ignition" is dis‐
delay [tGD] played).
[5 s]
(Gas Engine After the time set here has expired, and as long as the speed is higher than
only) the minimum speed for ignition, the gas valve is enabled for the time config‐
ured in parameter 3306 Ä p. 168 "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 2 10 to 1,800 rpm After expiration of the ignition delay the number of revolutions set here must
speed for igni‐ be reached, so the "Ignition" relay will be energized.
tion [100 rpm]
(Gas Engine
only)
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 rel‐
evant 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 the 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:
n Electrical measured determined speed
n Speed sensor (rpm) determined speed
3302 Start attempts 2 1 to 20 The control will attempt to start the engine with this number of start attempts.
[3] 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 ( Ä Chapter 4.4.6 “Emergency Run” on page 299)
critical mode is initiated, the engine will continue to attempt to start for the number of starts
[10] configured here.
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.
3306 Starter time 2 1 to 99 s This is the maximum time that the starter relay will remain energized ("Start"
display).
(Maximum [5 s]
starter delay If the LogicsManager output "Ignition speed reached" = TRUE, the speed/
[tST]) frequency have reached firing speed, or the time has expired, the relay will be
de-energized.
3307 Start pause 2 1 to 99 s This is the delay time between the individual starting attempts.
time [tSP]
[7 s] This time is also used to protect the starter relay. The message "Start -
Pause" is displayed.
4844 Inhibit 2 1 to 999 s If the inhibit cranking (parameter 4871 Ä p. 170 becomes active this counter
cranking max. starts.
time [60 s]
Once the counter exceeds the delay time, the message "Start fail" is dis‐
played.
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 2 1 to 99 s During this time a restart of the engine is blocked. This time should be config‐
engine ured so that the engine is total shutdown to protect the starting circuit.
[10 s]
(Engine Once speed from the engine is no longer detected the time configured in this
blocking) 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 disengaged.
[15 Hz] The firing speed is to be configured low enough that it is always exceeded
during regular generator operation.
Notes
The time counter for the engine delayed monitoring is no longer activated
directly by firing speed but by release engine monitoring 12999 Ä p. 170/
Ä p. 853.
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 moni‐ 2 1to 99 s Delay between reaching release engine monitoring and activation of the mon‐
toring delay itoring of engine speed delayed alarms (i.e. underspeed).
time [8 s]
After reaching the firing speed, the engine delayed monitoring timer is started.
(Engine delayed Upon expiration of this timer all "engine delayed monitoring" configured
monitoring [tED]) 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 clo‐
sure 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 con‐
figuring the LogicsManager "Undelay close GCB" (param‐
eter 12210 Ä p. 217/Ä p. 850).
Notes
If a critical operation mode ( Ä Chapter 4.4.6 “Emergency Run” on page 299)
is initiated, the time configured in critical mode postrun (parameter 4109) will
be used instead of the cool down time.
3319 Cool down in 2 [Yes] A cool down will be performed if the genset is changed to STOP operation
STOP mode mode.
3322 Cool down 2 This parameter may be used to perform a cool down if the application mode
without (parameter 3444 Ä p. 212) is configured to "None" or "GCB open".
breaker
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 .
3300 Auxiliary serv‐ 2 0 to 9999 s Prior to a start sequence being initiated, the discrete output for the auxiliary
ices prerun services prerun (LogicsManager 03.30) remains enabled for the configured
[tPRE] [0 s] amount of time to permit engine related operations (i.e. open louvers) to be
performed.
(Prerun auxiliary
operation (start While this discrete output is enabled the control screen will display the mes‐
preparation)) sage "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 output for the auxiliary services postrun (Logi‐
csManager 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 serv‐ 2 0 to 9999 s After each engine stop (the engine stop timer has expired), the discrete
ices postrun output for the auxiliary services postrun (LogicsManager 03.31) remains ener‐
[tPOST] [0 s] gized for an adjustable time (i.e. operate a cooling pump).
(Coasting auxil‐ If the operating mode is changed from MANUAL to STOP or AUTOMATIC
iary operation without a start command the relay remains energized for this period of time.
(post operation))
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 2 Determined by Once the conditions of the LogicsManager have been fulfilled the cranking
cranking LogicsManager (03.38) is blocked. The discrete output relay [R 03] will be not energized.
87.66
Notes
[(0 & 1) & 1]
For information on the LogicsManager and its default settings see Ä Chapter
= 11455 9.3.1 “LogicsManager Overview” on page 811.
Please refer to Fig. 141 for details.
12951 Firing speed 2 Determined by This LogicsManager allows different sources to generate the general firing
detection LogicsManager speed flag. This will be taken into account for the START/STOP automatic
87.68 and some monitoring functions.
[(02.34 Firing Notes
speed electr.
OR 02.35 Firing The former easYgen was fixed to the electrical frequency always and allowed
speed rpm) & other sources additionally. The default setting here is backward compatible.
1]
= 11457
12989 Speed detec‐ 2 Determined by This LogicsManager allows different sources to generate the general speed
tion LogicsManager flag. This will be taken into account for some monitoring functions.
87.69
Notes
[(02.36 Speed
electr. OR The former easYgen was fixed to the electrical frequency always. The default
02.37 Speed setting here is backward compatible.
rpm) & 1]
= 11458
12970 MAN engine 2 Determined by With the rising edge of this LogicsManager equation an engine start com‐
start LogicsManager mand in operating mode MANUAL is initiated. The state TRUE of this LM
87.50 inhibits the start command in MANUAL.
[(0 & 1) &1]
= 11439
12971 MAN engine 2 Determined by With the rising edge of this LogicsManager equation an engine stop com‐
stop LogicsManager mand in operating mode MANUAL is initiated. The state TRUE of this LM
87.59 inhibits the start command in MANUAL.
[(0 & 1) &1]
=11448
12999 Release 2 Determined by Switch to activate the delayed engine monitoring e.g., oil pressure, under fre‐
eng.mon. LogicsManager quency, ...
87.70
Notes
[(02.34 Firing
speed electr. & For more details see description below.
02.35 Firing
speed rpm) &
03.28 Start/
Gas]
tON = 0.00; tOFF
= 0.00]
= 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”:
n Under/Over frequency
n Under speed
n Under voltage
n ...
1600 MPU input 2 [On] Speed monitoring of the engine is carried out by the MPU.
(Pickup) Off Speed/frequency monitoring of the generator set (the engine) is performed by
measuring the frequency of the generator. There is no MPU wired to this unit.
15155 Engine speed 2 [Internal] The internal MPU input is used as engine speed source.
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 Ä p. 172 is set to
"Internal".
12570 Auto idle mode 2 Determined by Once the conditions of the LogicsManager have been fulfilled the engine will
LogicsManager be operated in idle mode automatically for the configured time during start-up.
86.20 Monitoring is limited as described above.
[(0 & 1) ≥1 0] This function may always be configured to "1" for example.
= 15719 Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12550 Constant idle 2 Determined by As long as the conditions of the LogicsManager have been fulfilled the engine
run LogicsManager will be continuously operated in idle mode. Monitoring is limited as described
86.14 above. A key switch via a DI may be configured here for example.
(Continuous idle
mode) [(0 & 1) & 0] Notes
= 10713 The idle mode is blocked if the GCB is already closed.
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
3328 Automatic idle 2 1 to 9999 s The automatic idle mode is active for the time configured here. Monitoring is
time limited as described above during this time.
[30 s]
(Time for auto‐
matic idle mode)
3329 During emer‐ 2 Yes If an emergency or critical operation is enabled, the engine will go to rated
gency / critical speed only after completing the configured idle mode.
(Idle mode pos‐ [No] If an emergency or critical operation is enabled, no idle run will be performed.
sible during The engine will go directly to rated speed.
emergency /
critical opera‐
tion)
Discrete input [DI 01] Programmable This discrete input is configured as alarm class F and is not
delayed by the engine speed.
Preconfigured to "Emergency STOP"
Discrete input [DI 02] Programmable Enabled in the AUTOMATIC operation mode
Preconfigured to "Startrequest in AUTO" This discrete input is configured as a Control input in the alarm
class and is not delayed by the engine speed.
n 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.
n De-energized
The engine is stopped.
Discrete input [DI 03] Programmable This discrete input is configured as alarm class B and is
delayed by the engine speed.
Preconfigured to "Low oil pressure"
Discrete input [DI 04] Programmable This discrete input is configured as alarm class B and is not
delayed by the engine speed.
Preconfigured to "Coolant temperature"
Discrete input [DI 05] Programmable This discrete input is used as a remote acknowledgment for
alarms. The input is normally de-energized. When an alarm is
Preconfigured to "External acknowledg‐ to be acknowledged the input is energized. The first time an
ment" 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 06] Programmable Only applicable for application mode
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.
n Energized
The MCB is enabled and closure of the breaker is per‐
mitted.
n 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 con‐
trol.
Discrete input [DI 07] Fixed to "MCB open reply" Only applicable for application mode
This input implements negative function logic.
The controller utilizes the CB auxiliary (B) contacts into this dis‐
crete 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 08] Fixed to "GCB open reply" Only applicable for application modes and
This input implements negative function logic.
The controller utilizes the CB auxiliary (B) contacts into this dis‐
crete 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 09] Programmable Can be set-up with description, delay, operation, alarm class,
self acknowledgment, and enable.
"Discrete Input 9
Alarm inputs
All discrete inputs, which are not assigned a func‐
tion, can be used as alarm or control inputs. These
discrete inputs can be freely configured as such
( Ä Chapter 4.4.2.2 “Discrete Inputs”
on page 179).
CAUTION!
Uncontrolled operation due to faulty configura‐
tion
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 gener‐
ator 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.
CAUTION!
Uncontrolled operation due to unknown config‐
uration
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.
Relay output [R 01] Programmable This discrete output is used to ensure that the internal functions
of the controller are operating properly.
Fixed to "Ready for operation"
It is possible to configure additional events, which cause the con‐
CAUTION! Only relay [R 01] has an tacts of this discrete output to open, using the LogicsManager.
inverse logic. The relay opens (all other
relays close), if the logical output of the
LogicsManager becomes TRUE.
Relay output [R 02] Programmable When a centralized alarm is issued, this discrete output is ena‐
bled.
Preconfigured to "Centralized alarm (horn)"
A horn or a buzzer maybe activated via this discrete output.
Pressing the button with the "3" 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 03] Programmable The generator starting circuit is engaged when this discrete
output is enabled.
Preconfigured to "Starter"
This discrete output will enable depending on the start sequence
(refer to the start sequence description in Ä Chapter 4.4.1.1
“Configure Engine (general)” on page 157) to energize the starter
for the configured starter time (parameter 3306 Ä p. 168).
Notes
Refer to Ä Chapter 4.4.1.1 “Configure Engine (general)”
on page 157
Relay output [R 06] Fixed to "Command: close GCB" Only applicable for application modes and .
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 Ä p. 215.
Impulse
If the output is configured as "Impulse", the discrete output will
enable for the time configured in parameter 3416 Ä p. 215). 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 dis‐
able and the GCB will open immediately.
Relay output [R 07] Fixed to "Command: open GCB" Not applicable for application mode
The parameter 3403 Ä p. 215 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 con‐
figurable.
Application mode
The open GCB command remains enabled until the GCB is man‐
ually closed and the discrete input "Reply GCB" is energized. The
open GCB command will be issued when a fault condition or an
engine shut down occurs.
Application mode or
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 08] Fixed to "Command: close MCB" Only applicable for application mode .
The discrete output "Command: close MCB" is an impulse output
signal.
This discrete output is enabled for the time configured in param‐
eter 3417 Ä p. 219.
An external holding coil and sealing contacts must be utilized with
the MCB closing circuit.
Relay output [R 09] Fixed to "Command: open MCB" Only applicable for application mode .
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 10] Programmable The auxiliary services output (LogicsManager 03.01) will be ena‐
bled with the start command (prior to the engine start because of
Preconfigured to "Auxiliary services" 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” on page 166 for this behavior.
The auxiliary services output (LogicsManager 03.01) is always
enabled in MANUAL operation mode.
Relay output [R 11] Programmable This discrete output is enabled when a warning alarm (class A or
B alarm) is issued ( Ä Chapter 9.5.1 “Alarm Classes”
Preconfigured to "Warning alarm" on page 888).
After all warning alarms have been acknowledged, this discrete
output will disable.
Relay output [R 12] Programmable This discrete output is enabled when a shutdown alarm (class C
or higher alarm; refer to Ä Chapter 9.5.1 “Alarm Classes”
Preconfigured to "Shutdown alarm" on page 888 for more information) is issued.
After all shutdown alarms have been acknowledged, this discrete
output will disable.
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 Ä Table 58 “Discrete inputs - param‐
eter IDs” on page 181 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
Descrip 1400 1410 1420 1430 1440 1450 1460 1480 1488 1496 1504
tion
Delay 1200 1220 1240 1260 1280 1300 1320 1360 1380 1205 1225
Opera‐ 1201 1221 1241 1261 1281 1301 1321 1361 1381 1206 1226
tion
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
acknowl
edged
Ena‐ 1203 1223 1243 1263 1283 1303 1323 1363 1383 1208 1228
bled
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 input.
[0.20 s] The discrete input must be enabled without interruption for 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} Opera‐ 2 The discrete inputs may be operated by an normally open (N.O.) or normally
tion 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 (nor‐
mally closed).
1202 DI {x} Alarm 2 An alarm class may be assigned to the discrete input.
class
The alarm class is executed when the discrete input is enabled.
[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 appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
Notes
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 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
[R 04] 45/46 LogicsManager; pre-assigned with 'Diesel: Fuel solenoid, Gas: Gas valve'
CAUTION!
Uncontrolled operation due to faulty configura‐
tion
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 gener‐
ator 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.
12580 Ready for op. 2 Determined by The "Ready for operation" relay is energized by default if the power supply
Off LogicsManager exceeds 8 V.
99.01
(Ready for oper‐ Once the conditions of the LogicsManager have been fulfilled, the relay will
ation OFF) [(0 & 0) & 1] be de-energized. This LogicsManager output may be configured with addi‐
tional conditions, which may signal a PLC an "out of operation" condition by
= 11870 de-energizing the relay on terminals 41/42, like "shutdown alarm" or no
"AUTO mode" present.
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12110 Relay {x} 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the relay will
LogicsManager be energized.
(See ID For (pre- 99.02
table defined) func‐ Notes
below) tion see assign‐ [(03.05 Horn &
ment table 1) & 1]
above) For information on the LogicsManager and its default settings see Ä Chapter
= 11871 9.3.1 “LogicsManager Overview” on page 811.
Parameter IDs
The parameter IDs above refers to relay 2.
– Refer to Ä Table 60 “Discrete outputs - relay
parameter IDs” on page 184 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
(correct)
X-coordinate 0 10 20 40 50 60 80 90 100
wrong:
X-coordinate 0 10 20 60 20 30 80 40 100
3560 to Table {A/B} X- 2 -900000.000 to The analog input is assigned to a curve. This parameter defines the actual
3568 value {1..9} 900000.000 value assigned to each of the nine points along the X-axis of the total range of
the selected hardware for analog input.
or [0, ...]
3610 to Example
3618
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- 2 -21000000.00 to This parameter defines the Y-coordinate (the displayed and monitored value)
3558 value {1..9} 21000000.00 at the corresponding X-coordinate.
or [0, ...]
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.
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
[0] [10] [20] [30] [45] [60] [70] [85] [100]
1025 Analog input 2 user-defined (up The event history will store this text message and it is also displayed on the
{x}: Descrip‐ to 39 charac‐ visualization screen.
1075 tion ters)
If the programmed limit value of the analog input has been reached or
1125 [Analog inp. exceeded this text is displayed in the control unit screen.
{x}]
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 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 2 According to the following parameters different measuring ranges are pos‐
{x}: Type sible at the analog inputs.
1050
[Off] The analog input is switched off.
1100
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 interpreted with the VDO characteristics 0 to
10 bar.
VDO 150 °C The value of the analog input is interpreted with the VDO characteristics 50 to
150 °C.
VDO 120 °C The value of the analog input is interpreted with the VDO 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." (param‐
eter 1039 Ä p. 187, 1089 Ä p. 187 or 1139 Ä p. 187). The maximum value
refers to the value configured as "Sender value at display max." (param‐
eter 1040 Ä p. 188, 1090 Ä p. 188 or 1140 Ä p. 188).
Table A The analog input is assigned to a characteristic curve which is defined over
9 points (stored in a table). Two independent tables (table A and table B) may
Table B 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 Ä Chapter 9.1.2 “VDO
Inputs Characteristics” on page 612.
1001 User defined 2 -21000000.00 to The value (y-axis) to be displayed for the minimum of the input range must be
min. display 21000000.00 entered here.
1051 value
[0] Notes
1101 (User defined
minimum dis‐ This parameter is only visible if the parameter "Type" (1000 Ä p. 187/
play value) Ä p. 193/1050 Ä p. 187/1100 Ä p. 187) is configured to "Linear".
1002 User defined 2 -21000000.00 to The value (y-axis) to be displayed for the maximum of the input range must
max. display 21000000.00 be entered here.
1052 value
[2000] Notes
1102 (User defined
maximum dis‐ This parameter is only visible if the parameter "Type" (1000 Ä p. 187/
play value) Ä p. 193/1050 Ä p. 187/1100 Ä p. 187) is configured to "Linear".
1039 Sender value 2 0.000 to The value (x-axis) of the configured input range, which shall correspond with
at display min. 2000.000 the minimum value configured for the display, must be entered here. This
1089 specifies the lower limit of the hardware range to be measured.
[0.000]
1139
Notes
This parameter is only visible if the parameter "Type" (1000 Ä p. 187/
Ä p. 193/1050 Ä p. 187/1100 Ä p. 187) is configured to "Linear".
1040 Sender value 2 0.000 to The value (y-axis) of the configured input range, which shall correspond with
at display max. 2000.000 the maximum value configured for the display, must be entered here. This
1090 specifies the upper limit of the hardware range to be measured.
(Sender value at [20000.00]
1140 display max‐ Example
imum)
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
This parameter is only visible if the parameter "Type" (1000 Ä p. 187/
Ä p. 193/1050 Ä p. 187/1100 Ä p. 187) is configured to "Linear".
1020 Sender type 2 The software in the control unit may be configured for various types of sen‐
sors. The configurable ranges apply to the linear analog input.
1070
[0 to 2000 The measuring range of the analog input is 0 to 2000 Ohms.
1120
Ohms]
Notes
If parameter "Type" (1000 Ä p. 187/Ä p. 193/1050 Ä p. 187/1100 Ä p. 187)
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 The resistive input (the "0 to 2000 Ohms" analog input) may be calculated
Ohms with a permanent offset to adjust for inaccuracies.
1096
[0.0 Ohm] If the offset feature is utilized, the value configured in this parameter will be
1146 added to/subtracted from the measured resistive value.
This has the following effect to the measured values (please note tables in
Ä Chapter 9.1.2 “VDO Inputs Characteristics” on page 612):
Notes
This parameter is only visible if the parameter "Sender type"
(1020 Ä p. 189/1070 Ä p. 189/1120 Ä p. 189) 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 2 -2 to 3 This is the exponent to adapt the decimal place of the actual value (parameter
protocol 1033/1083/1133) for the protocol format.
1085 [0]
Example
1135
Exponent is 3:
value of analog input {½/3} x 103 = value of analog input {½/3} x 1000
1033 Analog input (displayed only) Current scaled value of the AI {X}
{X}
1003 Monitoring 2 The respective analog input can be monitored for wire breaks.
wire break
1053 If this protective function is triggered, the display indicates "Wb: {Text of
Parameter [Description]}" (parameter
1103 1025 Ä p. 187/1075 Ä p. 187/1125 Ä p. 187).
The following configurations are used to monitor for wire breaks:
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 identi‐
fied 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 man‐
ually to the flexible limits ( Ä Chapter 4.5.5 “Flexible Limits” on page 386).
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:
n 0 to 20 mA:
Minimum value 2 mA Undershooting
Maximum value 20.5 mA Overshooting
n 0 to 2000 Ohms:
Minimum value 20 Ohms Undershooting (Offset = 0 Ohm)
Maximum value 2040 Ohms Overshooting (Offset = 0 Ohm)
n 0 to 1 V:
No wire break monitoring
1004 Wire break 2 Each limit may be assigned an independent alarm class that specifies what
alarm class action should be taken when the limit is surpassed.
1054
A/[B] Warning alarm classes
1104
C/D/E/F Shutdown alarm classes
Notes
This parameter is only visible if wire break monitoring (parameter
1003 Ä p. 189/1053 Ä p. 189/1103 Ä p. 189) is not set to "Off"
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
1005 Self acknowl‐ 2 Yes The control automatically clears the alarm if the fault condition is no longer
edge wire detected.
1055 break
[No] The control does not automatically reset the alarm when the fault condition is
1105
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
This parameter is only visible wire break monitoring (parameter
1003 Ä p. 189/1053 Ä p. 189/1103 Ä p. 189) is not set to "Off"
10113 Filter time con‐ 2 Off, 1 to 5 A low pass filter may be used to reduce the fluctuation of an analog input
stant for reading.
10114
0/4 to 20 mA The cut-off-frequency is defined as usual with 63% (e-1).
10116 and 0 to 1 V
Off The analog input is displayed without filtering.
Filter time con‐ 2 Off, 1 to 5 A low pass filter may be used to reduce the fluctuation of an analog input
stant for reading.
0 to 2000 Ω The cut-off-frequency is defined as usual with 63% (e-1).
1034 Unit 2 up to 6 charac‐ This parameter is assigning a unit text to the displayed analog value.
ters text
1084 Notes
[______]
1134 This parameter may only be configured using ToolKit.
If “°C” or “bar” is assigned the unit will be converted into "F" or "psi" auto‐
matically if the corresponding parameter for conversion 3630 Ä p. 184 and/or
3631 Ä p. 184 is configured to YES.
The max. number of characters is 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. Please verify the length on the display for best view!
3632 Bargraph min‐ 2 -21000000.00 to The start value for the bar graph display of the analog input is defined here.
imum 21000000.00 The value must be entered according to the display format, which refers to
3634 the analog input type (parameter 1000 Ä p. 187/Ä p. 193).
[0]
3636
3633 Bargraph max‐ 2 -21000000.00 to The end value for the bar graph display of the analog input is defined here.
imum 21000000.00 The value must be entered according to the display format, which refers to
3634 the analog input type (parameter 1000 Ä p. 187/Ä p. 193).
[2000]
3637
Configuration examples
Parameter / AnalogManager Example 1 with AO 1 Example 2 with AO 2
ID ID Value
Source value at maximum level 5206 220 (kW) 5220 100 (%)
AM Data source AO1 5200 Type: Pass through 5214 Type: Pass through
A1 = 01.74 Gen. act. A1 = 11.03 Speed bias
power [W] [%]
Analog output 1 10310 Display of resulting value 10311 Display of resulting value
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.
ID
5200 AM Data 2 Determined by The data source may be selected from the available data sources.
source ... AnalogManager
5214 93.01, 93.02 Notes
AO1: [A1 = Refer to Ä Chapter 9.4.1 “Data Sources AM” on page 856 for a list of all data
11.03 Speed sources.
bias (%)]
AO2: [A1 =
11.02 Voltage
bias (%)]
5201 Selected hard‐ 2 This parameter is used to configure the appropriate type of analog controller
ware type signal. The range of the analog output is configured here.
5215
PMW value is defined in %.
[mA] Notes
V Because of different isolation purposes the two biasing outputs must be clear
labeled with their function.
PWM
5208 Minimum hard‐ 2 -20.00 to 100.00 The value of the configured hardware range, which shall correspond with the
ware level configured minimum source value, must be entered here (y-axis). This speci‐
5222 [0.00] fies the minimum limit of the hardware range.
(User defined
minimum output Example
value)
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 2 -20.00 to 100.00 The value of the configured hardware range, which shall correspond with the
hardware level configured maximum source value, must be entered here (y-axis). This speci‐
5223 [20.00] fies the maximum limit of the hardware range.
(User defined
maximum Example
output value)
f the value configured here is 7.5, the maximum output range of +/-20 mA /
+/-10 V has a upper limit of 7.5 mA / 7.5 V.
Notes
Value [100] is possible only for PWM.
5210 PWM output 2 0.00 to 10.00 V If PWM has been enabled in parameter 5203 Ä p. 194/5217 Ä p. 192/
level Ä p. 194, is defined in %, and the level of the PWM signal (amplitude) may be
5224 [10.00 V] adjusted here.
5204 Source value 2 -21000000.00 to The value from the data source must exceed the value configured here to
at minimum 21000000.00 raise the output signal above minimum hardware level. Negative percentage
5218 level values may be used to change the sign, e.g. for power.
[0]
The entry format of the value depends on the selected data source.
5206 Source value 2 -21000000.00 to If the value from the data source reaches the value configured here, the
at maximum 21000000.00 output signal will reach maximum hardware level. Negative percentage values
5220 level may be used to change the sign, e.g. for power.
[10000]
The entry format of the value depends on the selected data source.
5203 Filter time con‐ 2 Off, 1 to 7 A filter time constant may be used to reduce the fluctuation of an analog
stant output value.
5217
[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.
User defined 5852 5865 5878 5891 5904 5917 5930 5943
min display
value
User defined 5853 5866 5879 5892 5905 5918 5931 5944
max display
value
Sender type 5856 5869 5882 5895 5908 5921 5934 5947
Sender con‐ 5859 5872 5885 5898 5911 5924 5937 5950
nection type
Filter time 5863 5876 5889 5902 5915 5928 5941 5954
constant
Exponent for 16204 16214 16229 16234 16244 16254 16264 16274
protocol
Wire break 5854 5867 5880 5893 5906 5919 5932 5945
alarm class
Parameter AI 9 AI 10 AI 11 AI 12 AI 13 AI 14 AI 15 AI 16
external
User defined 5956 5969 5982 6931 6944 6957 6970 6983
min display
value
User defined 5957 5970 5983 6932 6945 6958 6971 6984
max display
value
Sender type 5960 5973 5986 6935 6948 6961 6974 6987
Parameter AI 9 AI 10 AI 11 AI 12 AI 13 AI 14 AI 15 AI 16
external
Sender con‐ 5963 5976 5989 6938 6951 6964 6977 6990
nection type
Filter time 5967 5980 5993 6942 6955 6968 6981 6994
constant
Exponent for 16284 16294 16304 16314 16324 16334 16344 16354
protocol
Wire break 5958 5971 5984 6933 6946 6959 6972 6985
alarm class
Available "Type"s
(parameters 5851, 5864, ...)
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 U KTY 84
TC Type L
TC Type C
TC Type W
TC Type HK
0 - 10 V R0=100
±10 V R0=10
0 - 20 mA R0=20
±20 mA R0=30
4 - 20 mA R0=50
Thermocouple R0=200
R0=240
R0=300
R0=400
R0=500
R0=1000
R0=1500
R0=2000
R0=3000
Two wire
Three wire
Notes:
Refer to for details and definition of the parameters.
10237 Data source ... 2 Determined by The data source may be selected from the available data sources.
AnalogManager
10247 93.21 .. 93.24 Notes
10257 AO1 to AO 4: Refer to Ä Chapter 9.4.1 “Data Sources AM” on page 856 for a list of all data
[A1 = 11.03 sources.
10267
Speed bias
(%)]
10238 Selected hard‐ 2 This parameter is used to configure the appropriate type of analog controller
ware type signal. The range of the analog output is configured here.
10248
Off No analog output signal will be issued.
10258
10268 [mA]
10242 Minimum hard‐ 2 0.00 to 20.00 The value of the configured hardware range, which shall correspond with the
ware level configured minimum source value, must be entered here (y-axis). This speci‐
20252 [0.00] fies the minimum limit of the hardware range.
(User defined
10262 minimum output Example
10272 value)
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.
10243 Maximum 2 0.00 to 20.00 The value of the configured hardware range, which shall correspond with the
hardware level configured maximum source value, must be entered here (y-axis). This speci‐
10253 [20.00] fies the maximum limit of the hardware range.
(User defined
10263 maximum Example
10273 output value)
f the value configured here is 7.5, the maximum output range of +/-20 mA /
+/-10 V has a upper limit of 7.5 mA / 7.5 V.
10240 Source value 2 -21000000.00 to The value from the data source must exceed the value configured here to
at minimum 21000000.00 raise the output signal above minimum hardware level. Negative percentage
10250 level values may be used to change the sign, e.g. for power.
[0]
10260 The entry format of the value depends on the selected data source.
10270
10241 Source value 2 -21000000.00 to If the value from the data source reaches the value configured here, the
at maximum 21000000.00 output signal will reach maximum hardware level. Negative percentage values
10251 level may be used to change the sign, e.g. for power.
[10000]
10261 The entry format of the value depends on the selected data source.
10271
10239 Filter time con‐ 2 Off, 1 to 7 A filter time constant may be used to reduce the fluctuation of an analog
stant output value.
10249
[Off] The analog output is displayed without filtering.
10259
10269 1 Cut-off-frequency = 3.98 Hz (filter time constant = 0.04 s)
Notes
The filter is not applied to the analog output display value, i.e. the end value
of the analog output is displayed immediately.
External DI 1 DI 2 DI 3 DI 4 DI 5 DI 6 DI 7 DI 8
Alarm class 16002 16012 16022 16032 16042 16052 16062 16072
External DI 1 DI 2 DI 3 DI 4 DI 5 DI 6 DI 7 DI 8
Self acknowledge 16004 16014 16024 16034 16044 16054 16064 16074
External DI 9 DI 10 DI 11 DI 12 DI 13 DI 14 DI 15 DI 16
Alarm class 16082 16092 16102 16112 16122 16132 16142 16152
Self acknowledge 16084 16094 16104 16114 16124 16134 16144 16154
External DI 17 DI 18 DI 19 DI 20 DI 21 DI 22 DI 23 DI 24
Alarm class 16007 16017 16027 16037 16047 16057 16067 16077
Self acknowledge 16009 16019 16029 16039 16049 16059 16069 16079
External DI 25 DI 26 DI 27 DI 28 DI 29 DI 30 DI 31 DI 32
Alarm class 16087 16097 16107 16117 16127 16137 16147 16157
Self acknowledge 16089 16099 16109 16119 16129 16139 16149 16159
External DO 1 DO 2 DO 3 DO 4 DO 5 DO 6 DO 7 DO 8
External DO 9 DO 10 DO 11 DO 12 DO 13 DO 14 DO 15 DO 16
External DO 17 DO 18 DO 19 DO 20 DO 21 DO 22 DO 23 DO 24
External DO 25 DO 26 DO 27 DO 28 DO 29 DO 30 DO 31 DO 32
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 rea‐
sons, 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 auto‐
matically 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:
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 applica‐
tion. 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 clo‐
sures 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.
n The generator and busbar voltage are available and within the
configured operating range ( Ä Chapter 4.5.1.1 “ Generator
Operating Ranges: Voltage / Frequency / Busbar”
on page 302)
n The differential frequency/voltage is within the configured oper‐
ating range
n Synchronizing the MCB
– The GCB is closed (or at least one GCB is closed in a mul‐
tiple genset application)
– The busbar voltage is within the configured operating range
– The "Enable MCB" (parameter 12923 Ä p. 220/Ä p. 853)
signal is present, for example discrete input 6 is energized
if configured as DI 6
n Synchronizing the GCB
– The MCB is closed
– The busbar voltage is within the configured operating range
– Engine delayed monitoring (parameter 3315 Ä p. 168) and
generator stable time (parameter 3415 Ä p. 217) have
expired or "Undelay close GCB" (param‐
eter 12210 Ä p. 217/Ä p. 850) is enabled
Manual operation
n Operating mode MANUAL has been selected
n The generator and busbar voltage are available and within the
configured operating range ( Ä Chapter 4.5.1.1 “ Generator
Operating Ranges: Voltage / Frequency / Busbar”
on page 302)
n The differential frequency/voltage is within the configured oper‐
ating range
n Synchronizing the MCB
– The GCB is closed (or at least one GCB is closed in a mul‐
tiple genset application)
– The busbar voltage is within the configured operating range
– The "Enable MCB" (parameter 12923 Ä p. 220/Ä p. 853)
signal is present, for example discrete input 6 is energized
if configured as DI 6
– The button "Close MCB" has been pressed
n Synchronizing the GCB
– The MCB is closed
– The busbar voltage is within the configured operating range
– Engine delayed monitoring (parameter 3315 Ä p. 168) and
generator stable time (parameter 3415 Ä p. 217) have
expired or "Undelay close GCB" (param‐
eter 12210 Ä p. 217/Ä p. 850) is enabled
– The button "Close GCB" has been pressed
The unit closes the MCB, if the following conditions are met simul‐
taneously.
The display indicates "MCB dead bus close".
Automatic operation
n The operating mode AUTOMATIC has been selected
n The parameter "Dead busbar closure MCB" (parameter
3431 Ä p. 220) is configured On
n The mains voltage is available and within the configured oper‐
ating range ( Ä Chapter 4.5.3.3 “Mains Operating Ranges:
Voltage / Frequency” on page 347)
n The GCB is open or has been opened for at least the "Transfer
time GCB↔MCB" (parameter 3400 Ä p. 214) (open transition
mode only)
n The "Enable MCB" (parameter 12923 Ä p. 220/Ä p. 853)
signal is present, for example discrete input 6 is energized if
configured as DI 6
n The busbar voltage is below the dead bus detection limit
(parameter 5820 Ä p. 415)
Manual operation
n Operating mode MANUAL has been selected
n The parameter "Dead busbar closure MCB" (parameter
3431 Ä p. 220) is configured "On"
n The mains voltage is available and within the configured oper‐
ating range ( Ä Chapter 4.5.3.3 “Mains Operating Ranges:
Voltage / Frequency” on page 347)
n The GCB is open or has been opened for at least the "Transfer
time GCB↔MCB" (parameter 3400 Ä p. 214) (open transition
mode only)
n The "Enable MCB" (parameter 12923 Ä p. 220/Ä p. 853)
signal is present, for example discrete input 6 is energized if
configured so
n The button "Close MCB" has been pressed
n The busbar voltage is below the dead bus detection limit
(parameter 5820 Ä p. 415)
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:
n If an emergency power operation is initiated (mains failure)
once the generator voltage is within the permissible limits
n Prior to the closure of the GCB (depending on the CB logic
which has been set)
n Upon pressing the "MCB" or "GCB" softkey (dependent upon
the configured CB logic) in MANUAL operating mode
Breaker logic "EXTERNAL" External breaker logic is enabled via configuration of parameter
3411 Ä p. 213 to "EXTERNAL".
All breaker control (especially the CB closing instructions) must be
carried out via master controller (e.g. a PLC).
The GCB is opened. The MCB and the GCB may be manually The GCB is opened if the genset is
opened. The circuit breakers are opened stopped or if decoupling from the mains,
for decoupling from the mains. but will not close if the engine is started.
The MCB is opened only if decoupling
from the mains, and is never closed.
The GCB is opened; the MCB is operated Mains parallel operation can be initiated by The GCB is synchronized via an add-on
depending on the setting of "Enable MCB" pressing the "GCB On" or "MCB On" push- request and a mains parallel operation is
(parameter 12923 Ä p. 220/Ä p. 853). button. 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 expi‐
ration of the mains settling time. The MCB
is synchronized and closed, putting the
system back into a mains parallel opera‐
tion.
The GCB is opened; the MCB is operated A change can be made to either generator A change is made to generator operation
depending on the setting of "Enable MCB" or mains operation by pressing either the through an add-on request. Once the add-
(parameter 12923 Ä p. 220/Ä p. 853). "GCB On" or "MCB On" push-button. The on request is terminated, the system
"STOP" push-button opens the GCB and changes back to mains operation. The
simultaneously stops the engine. MCB is closed 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.
The GCB is opened; the MCB is operated Synchronization of either the generator or The GCB is synchronized via an add-on
depending on the setting of "Enable MCB" the mains can be initiated by pressing the request. After the GCB closes the MCB is
(parameter 12923 Ä p. 220/Ä p. 853). "GCB On" or "MCB On" push-button. opened. Following the shed-off request
being issued, the MCB is synchronized
and closed. After the MCB has closed the
GCB is opened.
Emergency power: The emergency power
operation is terminated following the expi‐
ration of the mains settling time and the
MCB synchronizing to the generator. The
MCB closes and the GCB opens immedi‐
ately afterwards.
The GCB is opened; the MCB is operated Synchronization of either the generator or Via an engine request, the GCB is
depending on the setting of "Enable MCB" the mains can be initiated by pressing the synchronized and the generator power is
(parameter 12923 Ä p. 220/Ä p. 853). "GCB On" or "MCB On" push-button. increased. The MCB is then opened. Fol‐
lowing the disabling of the engine request,
the MCB is reverse synchronized and the
GCB is then opened.
Emergency power: The emergency power
operation is terminated following the expi‐
ration of the mains settling time. The MCB
closes, the load is transferred, and the
GCB opens.
The GCB is opened. Mains parallel operation can be performed The GCB is synchronized via an add-on
via the "GCB On" push-button. request and mains parallel operation 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.
3444 Application 2 The unit may be configured for four different application modes. The discrete
mode inputs and relay outputs are pre-defined dependent upon the selected appli‐
cation mode. Only the screens and functions that pertain to the application
mode selected are displayed. The single line diagram in the main screen will
change.
Refer to Ä Chapter 2.2 “Application Modes Overview” on page 35 for addi‐
tional information.
3411 Breaker transi‐ 2 The control unit automatically controls the two breakers (MCB and GCB).
tion mode
External
Open Transition
Closed Transit.
Interchange
[Parallel]
Notes
This parameter only applies to application mode .
For a detailed explanation for each mode refer to Ä Chapter 4.4.3.1.6 “Tran‐
sition Modes (Breaker Logic)” on page 208.
The unit provides two alternative transition modes, which may be activated
temporarily via the LogicsManager and override the transition mode config‐
ured in this parameter.
3412 Breaker transi‐ 2 The control unit automatically controls the two breakers (MCB and GCB).
tion mode 1
External
Open Transition
Closed Transit.
Interchange
[Parallel]
Notes
This parameter only applies to application mode .
For a detailed explanation for each mode refer to Ä Chapter 4.4.3.1.6 “Tran‐
sition Modes (Breaker Logic)” on page 208.
12931 Transition 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the transition
mode 1 LogicsManager mode configured in parameter 3412 Ä p. 213 will be used instead of the
86.93 standard transition mode configured in parameter 3411 Ä p. 213.
[(0 & 1) & 1] For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
= 11922
Notes
This parameter only applies to application mode .
Alternative transition mode 1 has priority over alternative transition mode 2,
i.e. if both LogicsManager functions (parameters 12931 Ä p. 213/Ä p. 853
and 12932 Ä p. 214/Ä p. 853) are TRUE, breaker transition mode 1 (param‐
eter 3412 Ä p. 213) will be used.
3413 Breaker transi‐ 2 The control unit automatically controls the two breakers (MCB and GCB).
tion mode 2
External
Open Transition
Closed Transit.
Interchange
[Parallel]
Notes
This parameter only applies to application mode .
For a detailed explanation for each mode refer to Ä Chapter 4.4.3.1.6 “Tran‐
sition Modes (Breaker Logic)” on page 208.
12932 Transition 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the transition
mode 2 LogicsManager mode configured in parameter 3412 Ä p. 213 will be used instead of the
86.94 standard transition mode configured in parameter 3411 Ä p. 213.
[(0 & 1) & 1] Notes
= 11923 This parameter only applies to application mode .
Alternative transition mode 1 has priority over alternative transition mode 2,
i.e. if both LogicsManager functions (parameters 12931 Ä p. 213/Ä p. 853
and 12932 Ä p. 214/Ä p. 853) are TRUE, breaker transition mode 1 (param‐
eter 3412 Ä p. 213) will be used.
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
3400 Transfer time 2 1.00 to 99.99 s Switching from generator supply to mains supply or from mains supply to gen‐
GCB↔MCB erator supply occurs automatically if the operating conditions have been met.
[1.00 s]
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 parameter only applies to application mode .
This is only valid, if parameter 3411 Ä p. 213 is configured to OPEN TRANSI‐
TION
Not used A GCB open relay is not used and relay R7 (Command: open GCB) is freely
programmable. In this case, parameter 3414 Ä p. 215 must be configured to
"Steady" to open the breaker.
Notes
This parameter only applies to application mode .
3414 GCB close 2 Impulse The relay "Command: GCB close" issues an add-on pulse. If the relay is con‐
command figured 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 cir‐
cuit 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 ener‐
gized. 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 Ä p. 215 is not configured as "Not used".
This parameter only applies to application modes and .
3416 GCB time 2 0.10 to 1.00 s The time of the pulse output may be adjusted to the breaker being utilized.
pulse
[0.50 s] Notes
This parameter only applies to application mode .
5729 Synchroniza‐ 2 [Slip fre‐ The frequency controller adjusts the frequency in a way, that the frequency of
tion GCB quency] the source (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" (param‐
eter 5502 Ä p. 251).
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
This parameter only applies to application mode .
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 differ‐ 2 0.00 to 20.00% The maximum permissible voltage differential for closing the generator circuit
ential GCB breaker is configured here.
[5.00%]
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 Ä p. 302 and 5801 Ä p. 302), the "Com‐
mand: GCB close" may be issued.
Notes
This value refers to the generator rated voltage (parameter 1766 Ä p. 412).
This parameter only applies to application modes and .
5701 Positive fre‐ 2 0.00 to 0.49 Hz The prerequisite for a close command being issued for the GCB is that the
quency differ‐ differential frequency is below the configured differential frequency.
ential GCB [+0.18 Hz]
This value specifies the upper frequency (positive value corresponds to posi‐
tive slip → generator frequency is higher than the busbar frequency).
Notes
This parameter only applies to application modes and .
5702 Negative fre‐ 2 -0.49 to 0.00 Hz The prerequisite for a close command being issued for the GCB is that the
quency differ‐ differential frequency is above the configured differential frequency.
ential GCB [-0.10 Hz]
This value specifies the lower frequency limit (negative value corresponds to
negative slip → generator frequency is less than the busbar frequency).
Notes
This parameter only applies to application modes and .
5703 Maximum posi‐ 2 0.0 to 60.0° The prerequisite for a close command being issued for the GCB is that the
tive phase leading phase angle between generator and busbar is below the configured
angle GCB [7.0°] maximum permissible angle.
Notes
This parameter only applies to application modes and .
This parameter is only displayed, if parameter 5729 Ä p. 215 is configured to
"Phase matching".
5704 Maximum neg‐ 2 -60.0 to 0.0° The prerequisite for a close command being issued for the GCB is that the
ative phase lagging phase angle between generator and busbar is below the configured
angle GCB [-7.0°] maximum permissible angle.
Notes
This parameter only applies to application modes and .
This parameter is only displayed, if parameter 5729 Ä p. 215 is configured to
"Phase matching".
5707 Phase 2 0.0 to 60.0 s This is the minimum time that the generator voltage, frequency, and phase
matching GCB angle must be within the configured limits before the breaker will be closed.
dwell time [3.0 s]
Notes
This parameter only applies to application modes and .
This parameter is only displayed, if parameter 5729 Ä p. 215 is configured to
"Phase matching".
8825 Phase angle 2 The phase angle between generator voltage and generator busbar voltage
compensation can be compensated according to an installed power transformer between
GCB generator and busbar.
Notes
Measured values 181 'Ph.ang.busb1-gen.L12' and 184 'Ph.ang.mns.busb1
L12' are not changed but the compensated (8824 Ä p. 217) 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 pre‐
vent 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 synchroni‐
zation with a zero voltmeter.
Recommendation: For safety reasons, please mark the easYgen with a label
showing the configured phase angle compensation.
Refer to Ä Chapter 6.3.11 “Phase Angle Compensation” on page 516 for
details.
8824 Phase angle 2 -180 to 180° The phase angle compensation corrects the degree between generator
GCB voltage and busbar voltage. The configured degree is added to the real meas‐
[0°] ured 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 clo‐ 2 [On] A dead busbar closure is allowed if the required conditions are met.
sure GCB
Off A GCB close command to a dead busbar is prevented. Synchronization is still
possible.
Notes
This parameter only applies to application modes and .
15161 Inhibit dead 2 Determined by If active the dead bus closure of the GCB can be inhibited.
bus closure LogicsManager
GCB 87.74 Notes
[(0 & 1) & 1] For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
= 11463
3415 Generator 2 0 to 99 s The time configured here begins to count down once the engine monitoring
stable time delay timer has expired. This permits for an additional delay time before the
[2 s] breaker is closed in order to ensure that none of the engine delayed watch‐
dogs trips.
It is possible to bypass this delay time through the LogicsManager (param‐
eter 12210 Ä p. 217/Ä p. 850) 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
This parameter only applies to application mode .
12210 Undelay close 2 Determined by Once the conditions of the LogicsManager have been fulfilled the GCB will be
GCB LogicsManager closed immediately (without waiting for engine speed delay and generator
86.12 stable timer to expire).
[(04.09 Emer‐ When using the standard setting, the GCB will be closed without delay in
gency mode & emergency power operation.
1) & 1]
= 10711
Notes
This parameter only applies to application modes and .
Usually the dead busbar negotiation is started with reaching the generator fre‐
quency 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.
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12976 GCB open in 2 Determined by With the rising edge of this LogicsManager equation a GCB open command
MAN LogicsManager in operating mode MANUAL is initiated. The state TRUE of this LM inhibits
87.46 the GCB close command in MANUAL.
[(0 & 1) & 1] Notes
= 11435 This parameter only applies to application modes and .
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12977 GCB close in 2 Determined by With the rising edge of this LogicsManager equation a GCB close command
MAN LogicsManager in operating mode MANUAL is initiated.Precondition: deactivated "GCB open
87.47 in MAN"
[(0 & 1) & 1] Notes
= 11436 This parameter only applies to application modes and .
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
5705 Closing time 2 40 to 300 ms The inherent closing time of the GCB corresponds to the lead-time of the
GCB close command.
[80 ms]
The close command will be issued independent of the differential frequency at
the entered time before the synchronous point.
Notes
This parameter only applies to application modes and .
3405 GCB auto 2 This is used for special circuit breakers to put the GCB into a defined initial
unlock state or to enable closing at all.
[No] The CB close pulse is enabled without being preceded by a CB open pulse.
Notes
This parameter only applies to application modes and .
5708 GCB open time 2 1.00 to 10.00 s This time defines the length of the GCB open time pulse, if the automatic
pulse switch unblocking GCB is activated.
[1.00 s]
Notes
This parameter only applies to application modes and .
3417 MCB time 2 0.10 to 0.50 s Breaker pulse duration to close the MCB
pulse
[0.50 s] The time of the pulse output may be adjusted to the breaker being utilized.
5730 Synchroniza‐ 2 [Slip fre‐ The frequency controller adjusts the frequency in a way, that the frequency of
tion MCB quency] 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 (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 2 0.0 to 60.0° The prerequisite for a connect command being issued for the MCB is that the
phase angle leading phase angle between busbar and mains is below the configured max‐
MCB [7.0°] imum permissible angle.
(Maximum per‐ Notes
missible positive
phase angle This parameter is only displayed, if parameter 5730 Ä p. 219 is configured to
MCB) "Phase matching".
5714 Max negative 2 -60.0 to 0.0° The prerequisite for a connect command being issued for the MCB is that the
phase angle lagging phase angle between busbar and mains is below the configured max‐
MCB [-7.0°] imum permissible angle.
(Maximum per‐ Notes
missible nega‐
tive phase angle This parameter is only displayed, if parameter 5730 Ä p. 219 is configured to
MCB) "Phase matching".
5710 Voltage differ‐ 2 0.00 to 20.00% The maximum permissible voltage differential for closing the mains circuit
ential MCB breaker is configured here.
[5.00%]
Notes
This value refers to the generator rated voltage (parameter 1766 Ä p. 412)
and mains rated voltage (parameter 1768 Ä p. 415).
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 Ä p. 348 and 5811 Ä p. 348), the "Command:
MCB close" may be issued.
5711 Pos. freq. dif‐ 2 0.00 to 0.49 Hz The prerequisite for a connect command being issued for the MCB is that the
ferential MCB differential frequency is below the configured differential frequency.
[0.18 Hz]
(Positive fre‐ This value specifies the upper frequency (positive value corresponds to posi‐
quency differen‐ tive slip → busbar frequency is higher than the mains frequency).
tial MCB)
5712 Neg. freq. dif‐ 2 -0.49 to 0.00 Hz The prerequisite for a connect command being issued for the MCB is that the
ferential MCB differential frequency is above the configured differential frequency.
[-0.10 Hz]
(Negative fre‐ This value specifies the lower frequency limit (negative value corresponds to
quency differen‐ negative slip → busbar frequency is less than the mains frequency).
tial MCB)
5709 MCB sync. 2 On The MCB is synchronized with an individual slip frequency (also negative).
with separate
slip Notes
The setting for the slipping frequency (parameter 5647 Ä p. 219) via display
is located under 'configure frequency control'.
[Off] The MCB is synchronized with the same slip frequency like the GCB (param‐
eter 5502 Ä p. 251).
Notes
This parameter only applies to application mode .
5647 MCB slip freq. 2 -0.50 ... 0...50 Individual frequency offset for the MCB and LS5 synchronization. This value
setpoint offset Hz can be a positive or negative offset. The value is valid as long as the param‐
eter 'MCB synchronization with separate slip' On/Off' (parameter
[-0.10 Hz] 5709 Ä p. 219) is set to 'On' .
8841 Phase angle 2 The phase angle between busbar voltage and mains voltage can be compen‐
compensation sated according to an installed power transformer between busbar and mains.
MCB
On The compensation is active. The phase will be compensated according the
value configured in parameter 8842 Ä p. 220.
Notes
Measured values 181 'Ph.ang.busb1-gen.L12' and 184 'Ph.ang.mns.busb1
L12' are not changed but the compensated (8842 Ä p. 220) 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 pre‐
vent 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 synchroni‐
zation with a zero voltmeter.
Recommendation: For safety reasons, please mark the easYgen with a label
showing the configured phase angle compensation.
Refer to Ä Chapter 6.3.11 “Phase Angle Compensation” on page 516 for
details.
This parameter only applies to application mode .
8842 Phase angle 2 -180 to 180° The phase angle compensation corrects the degree between busbar voltage
MCB and mains voltage. The configured degree is added to the real measured
[0°] phase angle.
Notes
This parameter only applies to application mode .
Ensure correct configuration to prevent erroneous synchronization settings to
avoid generator destructive power. Incorrect wiring cannot be compensated
for with this parameter!
5717 Phase 2 0.0 to 60.0 s This is the minimum time that the generator/busbar voltage, frequency, and
matching MCB phase angle must be within the configured limits before the breaker will be
dwell time [3.0 s] closed.
Notes
This parameter is only displayed, if parameter 5730 Ä p. 219 is configured to
"Phase matching".
3431 Dead bus clo‐ 2 [On] A dead busbar closure is allowed if the required conditions are met.
sure MCB
Off An MCB close command to a dead busbar is prevented. Synchronization is
still possible.
5715 Closing time 2 40 to 300 ms The inherent closing time of the MCB corresponds to the lead-time of the
MCB close command.
[80 ms]
The close command will be issued independent of the differential frequency at
the entered time before the synchronous point.
3407 MCB auto 2 This is used for special circuit breakers to put the MCB into a defined initial
unlock state or to enable closing at all.
[No] The CB close pulse is enabled without being preceded by a CB open pulse.
12923 Enable MCB 2 Determined by Once the conditions of the LogicsManager have been fulfilled the MCB will be
LogicsManager enabled.
86.85
[(09.06 DI06 & !
08.07 MCB fail
to close) & !
07.05 Mns. ph.
rot. mismatch]
12974 MCB open in 2 Determined by With the rising edge of this LogicsManager equation a MCB open command
MAN LogicsManager in operating mode MANUAL is initiated. The state TRUE of this LM inhibits
87.48 the MCB close command in MANUAL.
[(0 & 1) & 1] Notes
= 11437 This parameter only applies to application mode .
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12975 MCB close in 2 Determined by With the rising edge of this LogicsManager equation a MCB close command
MAN LogicsManager in operating mode MANUAL is initiated.Precondition: deactivated "MCB open
87.49 in MAN"
[(0 & 1) & 1] Notes
= 11438 This parameter only applies to application mode .
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
5728 Synchroniza‐ 2 Off The synchronization is disabled; the frequency and voltage adaptation for
tion mode synchronization is not active.
In operation mode AUTO the easYgen allows the external GCB closing in
synchronization mode “Off” if:
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 Ä p. 215 (GCB close command).
[Run] Normal operating mode. The control actively synchronizes and issues breaker
closure commands.
Controlled by The synchronization mode may be selected by enabling one of the respective
LM LogicsManager functions (parameters 12907 Ä p. 222/Ä p. 852,
12906 Ä p. 222/Ä p. 852, or 12908 Ä p. 222/Ä p. 852).
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:
n 1. PERMISSIVE
n 2. CHECK
n 3. RUN
Notes
The device will still perform a dead busbar closure if the conditions are valid.
12907 Syn. mode 2 Determined by Once the conditions of the LogicsManager have been fulfilled the PERMIS‐
PERMIS. LogicsManager SIVE synchronization mode will be enabled.
86.39
(Synchroniza‐ Notes
tion mode PER‐ [(0 & 1) & 1]
MISSIVE) For information on the LogicsManager and its default settings see Ä Chapter
= 11618 9.3.1 “LogicsManager Overview” on page 811.
12906 Syn. mode 2 Determined by Once the conditions of the LogicsManager have been fulfilled the CHECK
CHECK LogicsManager synchronization mode will be enabled.
86.38
(Synchroniza‐ Notes
tion mode [(0 & 1) & 1]
CHECK) For information on the LogicsManager and its default settings see Ä Chapter
= 11617 9.3.1 “LogicsManager Overview” on page 811.
12908 Syn. mode 2 Determined by Once the conditions of the LogicsManager have been fulfilled the RUN syn‐
RUN LogicsManager chronization mode will be enabled.
86.40
(Synchroniza‐ Notes
tion mode RUN) [(0 & 1) & 1]
For information on the LogicsManager and its default settings see Ä Chapter
= 11619 9.3.1 “LogicsManager Overview” on page 811.
15157 Synchroscope 2 On The synchroscope screen automatically appears on the main screen, when
autom. to front the synchronization becomes active.
(Synchroscope [Off] Functionality deactivated.
automatic to
front)
WARNING!
No dead bus interlocking
Synch. Check is intended to be a redundant check
function enhancing system security. Don't use for
MCB control!
1840 Neutral inter‐ 2 On Neutral interlocking is enabled. The command variable 03.39 Close neutral
locking contactor is activated and the DI 12 is used for the NC feedback. The unit
monitors the NC feedback according to the close order.
1841 Priority 2 1 ... 32 The priority determines which NC is closed, if multiple gens are running in the
same segment.
[1]
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 measure‐
ments 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.
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 (deriva‐
tive) terms, and are displayed in the easYgen as follows:
P - Proportional gain (%)
I - Integral gain (%)
D - Derivative gain (determined by DR and I)
Integral control Integral compensates for process and setpoint load changes.
n 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 magni‐
tude and duration of the deviation. In this analogy the reset
response would keep the car speed constant regardless of the ter‐
rain.
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 (propor‐
tional 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.
4. Record the control gain (Kc) and oscillation period (T) in sec‐
onds.
5. Set the dynamics as follows:
n For PI control G=P(I/s + 1) set:
– Proportional gain = 0.45*Kc
– Integral gain = 1.2/T
– Derivative ratio = 100
n 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 domi‐
nant
– 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.
5607 Voltage Con‐ 2 [PID analog] The voltage is controlled using an analog PID controller.
trol
3pos controller The voltage is controlled using a three-step controller.
5608 Voltage control 2 0.0 to 100.0% The value entered for this parameter is the start reference point for the analog
initial state output to the voltage controller.
[50.0%]
If the output to the voltage control has been disabled, the output will act as a
control position reference point.
5610 Proportional 2 0.01 to 100.00 The proportional coefficient specifies the gain. By increasing the gain, the
gain response is increased to permit larger corrections to the variable to be con‐
[1.00] trolled. 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
This parameter is only visible if voltage control (parameter 5607 Ä p. 227) 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 integral gain
corrects for any offset (between setpoint and process variable) automatically
[1.00] 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
This parameter is only visible if voltage control (parameter 5607 Ä p. 227) is
configured to "PID analog".
5612 Derivative ratio 2 0.01 to 100.00 The derivative ratio identifies the D part of the PID controller. By increasing
this parameter, the stability of the system is increased.
[0.01]
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 oper‐
ates anywhere within the range of the process unlike reset.
Notes
This parameter is only visible if voltage control (parameter 5607 Ä p. 227) is
configured to "PID analog".
The default configured controller acts like a PI controller what is the valid D
part setting for systems with secondary controllers.
Notes
This parameter is only visible if voltage control (parameter 5607 Ä p. 227) is
configured to "3pos controller".
5651 Time pulse 1 0.01 to 2.00 s A minimum pulse on time must be configured here. The shortest possible
minimum pulse time should be configured to limit overshoot of the desired voltage refer‐
[0.05 s] ence point.
Notes
This parameter is only visible if voltage control (parameter 5607 Ä p. 227) is
configured to "3pos controller".
5652 Gain factor 1 0.1 to 10.0 The gain factor Kp influences the operating time of the relays. By increasing
the number configured in this parameter, the operating time of the relay will
[5.0] 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
This parameter is only visible if voltage control (parameter 5607 Ä p. 227) is
configured to "3pos controller".
5659 Cycle time 1 1.0 to 20.0 The cycle time factor adjusts the time between the pulses (pause time).
factor
[1.0] By increasing the cycle time factor, the time between the pulses increases.
Notes
This parameter is only visible if voltage control (parameter 5607 Ä p. 227) is
configured to "3pos controller".
5653 Expand dead‐ 1 1.0 to 9.9 If the measured generator voltage is within the deadband range (param‐
band factor eter 5650 Ä p. 228) and the configured delay expand deadband time (param‐
[1.0] eter 5654 Ä p. 229) expires, the deadband will be multiplied with the factor
configured here.
Notes
This parameter is only visible if voltage control (parameter 5607 Ä p. 227) is
configured to "3pos controller".
5654 Delay expand 1 1.0 to 9.9 s The measured generator voltage must be within the deadband range for the
deadband time configured here in order to multiply the deadband with the factor config‐
[2.0 s] ured in parameter 5653 Ä p. 229.
Notes
This parameter is only visible if voltage control (parameter 5607 Ä p. 227) is
configured to "3pos controller".
5618 AM Voltage 2 Determined by The voltage setpoint 1 source may be selected from the available data
SP1 [V] AnalogManager sources.
81.09
The internal voltage setpoint 05.57 can be changed manually at the setpoint
[A1 = 05.57 screen of the display.
Internal v setp1
[V]] Notes
The voltage setpoint may be adjusted within the configured operating limits
( Ä Chapter 4.5.1.1 “ Generator Operating Ranges: Voltage / Frequency /
Busbar” on page 302).
5600 Int.voltage 2 50 to 650,000 V The internal generator voltage setpoint 1 is defined in this screen. This value
control set‐ is the reference for the voltage controller when performing islanded and/or no-
point 1 [400 V] load operations.
5619 AM Voltage 2 Determined by The voltage setpoint 2 source may be selected from the available data
SP2 [V] AnalogManager sources.
81.10
The internal voltage setpoint 05.58 can be changed manually at the setpoint
[A1 = 05.58 screen of the display.
Internal v setp2
[V]] Notes
The voltage setpoint may be adjusted within the configured operating limits
( Ä Chapter 4.5.1.1 “ Generator Operating Ranges: Voltage / Frequency /
Busbar” on page 302).
5601 Int.voltage 2 50 to 650,000 V The internal generator voltage setpoint 2 is defined in this screen. This value
control set‐ is the reference for the voltage controller when performing islanded and/or no-
point 2 [400 V] load operations.
12920 Setp. 2 voltage 2 Determined by If this LogicsManager condition is TRUE, the voltage setpoint 2 will be used
LogicsManager instead of voltage setpoint 1. The voltage (result of AM) 5619 Ä p. 229/
86.83 Ä p. 881 instead of 5618 Ä p. 229/Ä p. 881 will be taken into account.
[(0 & 1) & 1] Notes
= 11912 For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
Remotely switching the setpoint is possible: Use the LogicsManager com‐
mand variable for input that is correlating with the dedicated bit of parameter
504 Ä p. 543/Ä p. 556.
5616 Start value 1 0 to 100% The voltage controller is activated when the monitored generator voltage has
exceeded the value configured in this parameter. This prevents the easYgen
[70%] from attempting to control the voltage while the engine is completing its start
sequence.
Notes
This value refers to the generator voltage setpoint (parameter 5600 Ä p. 229
or 5601 Ä p. 229).
5617 Start delay 1 0 to 999 s The voltage controller is enabled after the configured time for this parameter
expires.
[5 s]
5603 Voltage control 2 1.00 to The different setpoint values are supplied to the controller via this ramp. The
setpoint ramp 300.00 %/s 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
[5.00 %/s] greater the value entered here must be.
5604 Voltage control 2 0.0 to 20.0% If this control is to be operated on a generator in parallel with other generators
droop and voltage control is enabled, a droop characteristic curve must be used.
[5.0%]
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 generators in relation to their rated
reactive power.
12905 Volt. droop act. 2 Determined by If this LogicsManager condition is TRUE, the voltage droop is enabled.
LogicsManager
(Voltage droop 86.26 Example
active)
[(08.17 Missing n Rated reactive power: 400 kvar
member OR
n Rated voltage setpoint: 410 V
08.06 GCB fail
to open) & 1] n Droop 5.0%
= 11605 n Reactive power 0 kvar = 0% of rated power
n Voltage is adjusted to (410 V – [5.0% * 0.0 * 410 V]) = 410 V.
n Reactive power 400 kvar = 100% of rated reactive power
n Voltage is adjusted to (410 V – [5.0% * 1.0 * 410 V]) = 410 V – 20.5 V =
389.5 V.
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12938 Release V-con‐ 2 Determined by This LogicsManager is used to activate generally the voltage biasing to the
trol LogicsManager sub controller. If the LogicsManager is false the output will be on the initial
86.97 state (see parameter 5608 Ä p. 227).
[(1 & 1) & 1] The LogicsManager condition status 'TRUE' is activating the voltage or reac‐
tive power regulation according to the LogicsManager 'V/Q control' ID
= 11926 12941 Ä p. 234/Ä p. 853).
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
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 con‐
trol 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 inter‐
change point. In this mode the gensets are monitored and
restricted in reactive power flow (outcome and income; respectively
leading and lagging).
Generator Reactive Power Limita‐ A reactive power control (kvar or power factor) can cause an over‐
tions load or damage of the generator. To avoid this the easYgen pro‐
vides a 2-step protection:
1. The own absolute generator current is monitored with an per‐
centage setting related to rated current input (ID
1754 Ä p. 413). The easYgen limits or controls down the
excitation that this given level (ID 5791 Ä p. 233) is not
exceeded.
2. The inductive reactive power outcome of the own generator
is limited according to the configuration of ID 5792 Ä p. 233.
Or:
The inductive reactive power income of the own generator is
limited according to the configuration of ID 5793 Ä p. 233.
5625 Power factor 2 [PID analog] The power factor is controlled using an analog PID controller.
Control
3pos controller The power factor is controlled using a three-step controller.
5613 Proportional 2 0.01 to 100.00 The proportional coefficient specifies the gain. By increasing the gain, the
gain response is increased to permit larger corrections to the variable to be con‐
[1.00] trolled.
The farther out of tolerance the process is the larger the response action is to
return the process to the tolerance band.
Notes
If the gain is configured too high, the result is excessive overshoot/undershoot
of the desired value.
This parameter is only visible if power factor control (param‐
eter 5625 Ä p. 231) is configured to "PID analog".
5614 Integral gain 2 0.01 to 100.00 The integral gain identifies the I part of the PID controller. The integral gain
corrects for any offset (between setpoint and process variable) automatically
[1.00] over time by shifting the proportioning band.
Reset automatically changes the output requirements until the process vari‐
able 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 con‐
stant 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
This parameter is only visible if power factor control (param‐
eter 5625 Ä p. 231) is configured to "PID analog".
5615 Derivative ratio 2 0.01 to 100.00 The derivative ratio identifies the D part of the PID controller. By increasing
this parameter, the stability of the system is increased.
[0.01]
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 oper‐
ates anywhere within the range of the process unlike reset.
Notes
This parameter is only visible if power factor control (param‐
eter 5625 Ä p. 231) is configured to "PID analog".
The default configured controller acts like a PI controller what is the valid D
part setting for systems with secondary controllers.
5660 Deadband 1 0.001 to 0.300 The generator power factor is controlled in such a manner, when paralleled
with the mains, so that the monitored power factor does not deviate from the
[0.010] 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.
This prevents unneeded wear on the raise/lower relay contacts.
Notes
This parameter is only visible if power factor control (param‐
eter 5625 Ä p. 231) is configured to "3pos controller".
5661 Time pulse 1 0.01 to 2.00 s A minimum pulse on time must be configured here.
minimum
[0.05 s] The shortest possible pulse time should be configured to limit overshoot of
the desired power factor reference point.
Notes
This parameter is only visible if power factor control (parameter
5625 Ä p. 231) is configured to "3pos controller".
5662 Gain factor 1 0.1 to 10.0 The gain factor Kp influences the 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.
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
This parameter is only visible if power factor control (param‐
eter 5625 Ä p. 231) is configured to "3pos controller".
5667 Cycle time 1 1.0 to 20.0 The cycle time factor adjusts the time between the pulses (pause time).
factor
[1.0] By increasing the cycle time factor, the time between the pulses increases.
Notes
This parameter is only visible if voltage control (parameter 5625 Ä p. 231) is
configured to "3pos controller".
5663 Expand dead‐ 1 1.0 to 9.9 If the measured generator power factor is within the deadband range (param‐
band factor eter 5660 Ä p. 232) and the configured delay expand deadband time (param‐
[1.0] eter 5664 Ä p. 233) expires, the deadband will be multiplied with the factor
configured here.
Notes
This parameter is only visible if power factor control (param‐
eter 5625 Ä p. 231) is configured to "3pos controller".
5664 Delay expand 1 1.0 to 9.9 s The measured generator power factor must be within the deadband range for
deadband the time configured here in order to multiply the deadband with the factor con‐
[2.0 s] figured in parameter 5663 Ä p. 233.
Notes
This parameter is only visible if power factor control (param‐
eter 5625 Ä p. 231) is configured to "3pos controller".
5791 Max. generator 2 0 to 150% This is the maximum generator current during reactive power control. The
current percentage is related to the rated current setting (ID 1785 Ä p. 416).
[100%]
5792 Max. 2 0 to 150% This is the maximum accepted generator reactive inductive load (outcome)
react.inductive during reactive power control at the interchange point. The percentage is
pwr.gen [80%] related to the reactive power setting (ID 1746 Ä p. 416).
5793 Max. 2 0 to 150% This is the maximum accepted generator reactive capacitive load (income)
react.capacity during reactive power control at the interchange point. The percentage is
pwr.gen [50%] related to the reactive power setting (ID 1746 Ä p. 416).
5638 AM PF/var 2 Determined by The power factor / reactive power setpoint 1 source can be selected from the
SP1[-/var] AnalogManager available data sources.
81.11
The internal PF/var setpoint 05.10 can be changed manually at the setpoint
[A1 = 05.10 screen of the display.
Intern. PF
setp1 [%]]
5639 AM PF/var 2 Determined by The power factor / reactive power setpoint 2 source can be selected from the
SP2[-/var] AnalogManager available data sources.
81.05
The internal PF/var setpoint 05.11 can be changed manually at the setpoint
[A1 = 05.11 screen of the display.
Intern. PF
setp2 [%]]
5743 PF/kvar set‐ Mns. Export Selection of the mode for PF/kvar setpoint 1.
point 1 mode kvar
Mns. Import
kvar
Mains PF
[Gen. PF]
5620 Int. power 2 -0.999 to +1.000 The desired power factor may be configured here so that the reactive power
factor setpoint is regulated in the system.
1 [+1.000]
The designations "+" and "-" stand for inductive/lagging (generator overex‐
cited) and capacitive/leading (generator underexcited) reactive power.
This setpoint is active only in mains parallel operation.
5744 PF/kvar set‐ Mns. Export Selection of the mode for PF/kvar setpoint 2.
point 2 mode kvar
Mns. Import
kvar
Mains PF
[Gen. PF]
5745 Int. kvar set‐ 0.0 to +99999.9 This setpoint is active only if PF/kvar setpoint 1 is set to Mns. Export kvar or
point 1 Mns. Import kvar.
[0.0]
5621 Int. power 2 -0.999 to +1.000 The desired power factor may be configured here so that the reactive power
factor setpoint is regulated in the system.
2 [+1.000]
The designations "–" and "+" stand for inductive/lagging (generator overex‐
cited) and capacitive/leading (generator underexcited) reactive power. This
setpoint is active only in mains parallel operation.
5746 Int. kvar set‐ 0.0 to +99999.9 This setpoint is active only if PF/kvar setpoint 2 is set to Mns. Export kvar or
point 2 Mns. Import kvar.
[0.0]
12921 Setp. 2 2 Determined by If this LogicsManager condition is TRUE, the power factor setpoint 2 will be
pwr.factor LogicsManager used instead of power factor setpoint 1. The power factor (result of AM)
86.84 5639 Ä p. 233/Ä p. 881 instead of 5638 Ä p. 233/Ä p. 880 will be taken into
account.
[(0 & 1) & 1]
Notes
= 11913
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
5622 React. pwr. ctrl 2 0.01 to The different setpoint values are supplied to the controller via this ramp.
setpoint ramp 100.00 %/s
The slope of the ramp is used to alter the rate at which the controller modifies
[3.00 %/s] the setpoint value. The faster the change in the setpoint is to be carried out,
the greater the value entered here must be.
Notes
This ramp is also used in islanded operation for loading or unloading an addi‐
tional genset. An excessive oscillation may occur if the ramp is configured too
high.
12941 Q control 2 Determined by With LogicsManager can be controlled if a voltage control or a reactive power
LogicsManager control should be performed. If this LogicsManager condition is TRUE, the
86.99 reactive power control is performed.
[(04.07 MCB
closed & 04.06
GCB closed) &
1]
= 11928
5786 Power factor 2 [PF(P)] A power factor setpoint is determined according to the characteristic curve:
characteristic Power factor in relation to the actual Generator power.
5787 Point 1 power 2 0.0 to 150% The value entered into "Point 1 power" defines the cos phi (P) characteristic.
[0%]
5788 Point 1 cos phi 2 -0.999 to 1.000 The desired "Point 1 cos phi" may be configured here which defines the cos
phi (P) characteristic.
[-0.950]
The designations "+" and "-" stand for inductive/lagging (generator overex‐
cited) and capacitive/leading (generator underexcited) reactive power.
5789 Point 2 power 2 0.0 to 150% The value entered into "Point 2 power" defines the cos phi (P) characteristic.
[100%]
5790 Point 2 cos phi 2 -0.999 to 1.000 The desired "Point 2 cos phi" may be configured here which defines the cos
phi (P) characteristic.
[0.950]
The designations "+" and "-" stand for inductive/lagging (generator overex‐
cited) and capacitive/leading (generator underexcited) reactive power.
5028 Point 3 power 2 0.0 to 150% The value entered into "Point 3 power" defines the cos phi (P) characteristic.
[100%]
5029 Point 3 cos phi 2 -0.999 to 1.000 The desired "Point 3 cos phi" may be configured here which defines the cos
phi (P) characteristic.
[0.950]
The designations "+" and "-" stand for inductive/lagging (generator overex‐
cited) and capacitive/leading (generator underexcited) reactive power.
5030 Point 4 power 2 0.0 to 150% The value entered into "Point 4 power" defines the cos phi (P) characteristic.
[100%]
5031 Point 4 cos phi 2 -0.999 to 1.000 The desired "Point 4 cos phi" may be configured here which defines the cos
phi (P) characteristic.
[0.950]
The designations "+" and "-" stand for inductive/lagging (generator overex‐
cited) and capacitive/leading (generator underexcited) reactive power.
5778 Point 1 voltage 45.0 to 150.0% The value entered into "Point 1 Voltage" defines the x-coordinate of point 1
[98.0%]
5779 Point 1 Q/S -0.99 to +0.99 The value entered into "Point 1 Reactive power" defines the y-coordinate of
rated point 1
[-0.31]
5797 Point 2 voltage 45.0 to 150.0% The value entered into "Point 2 Voltage" defines the x-coordinate of point 2
[106.0%]
5798 Point 2 Q/S -0.99 to +0.99 The value entered into "Point 2 Reactive power" defines the y-coordinate of
rated point 2
[+0.31]
5032 Point 3 voltage 0.0 to 150.0% The value entered into "Point 3 Voltage" defines the x-coordinate of point 3
[106.0%]
5033 Point 3 Q/S -0.99 to +0.99 The value entered into "Point 3 Reactive power" defines the y-coordinate of
rated point 3
[+0.31]
5034 Point 4 voltage 0.0 to 150.0% The value entered into "Point 4 Voltage" defines the x-coordinate of point 4
[106.0%]
5035 Point 4 Q/S -0.99 to +0.99 The value entered into "Point 4 Reactive power" defines the y-coordinate of
rated point 4
[+0.31]
5799 Q(V) response 001 to 999 s The response with a new reactive power setpoint acting on the analog com‐
time mand variable 05.29 PF characteristic can be delayed. Q(V) response time is
[10 s] used to calculate the power factor characteristic Q(V), parameter
5786 Ä p. 236.
Notes
The delay is realized with a PT-1 filter. Therefore the reaction times are opti‐
mized 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 char‐
acteristic curve.
5023 Q(V) Hyste‐ 0 to 20% The hysteresis for the Q(V) characteristic acts as a deadband for the selected
resis band. If the Mains voltage is within the hysteresis the resulting power factor
[0%] characteristic reference doesn't change.
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 param‐
eter [Load share interface ] 9924 Ä p. 243/
Ä p. 591 (CAN or Ethernet) and others.
Please see settings at
– “Parameter è Configuration
è Configure application
è Configure controller
è Configure load share”
– Chapter Ä Chapter 4.4.4.3.7 “Parameters”
on page 243
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 individ‐
ually 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.
Example If + slip frequency setpoint offset = 0.2 Hz, the easYgen will calcu‐
late the bus frequency reference point as:
n [measured mains frequency] + [slip frequency setpoint
offset] = bus frequency reference point
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" (param‐
eter 5531 Ä p. 243) or "Reactive power load share" (param‐
eter 5631 Ä p. 243) must be enabled.
4.4.4.3.7 Parameters
ID Parameter CL Setting range Description
[Default]
9924 Load share 2 The interface, which is used for transmitting the load share data is configured
Interface here.
11986 LS interface 2 Determined by Load share interface switch if parameter 9924 Ä p. 243/Ä p. 591 is config‐
Ethernet A LogicsManager ured to "CAN/EthA by LM".
86.13
TRUE: Use Ethernet A interface
[(02.01 & 1) &
1] FALSE: Use CAN interface 1
= 11987
5531 Active power 2 [On] Active power load share is enabled. When multiple generators are operating
load share in parallel, the real power is shared proportionally.
4522 Active power 2 0.01 to 9.99 This parameter defines the impact of the active power load sharing error
load share gain signal on the frequency/load controller setpoint. The active power load share
[1.25] 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 default gain 1.25 relates to the 50% value.
5631 Reactive power 2 [On] Reactive power load share is enabled. When multiple generators are oper‐
load share ating in parallel, the reactive power is shared proportionally.
4543 React. power 2 0.01 to 9.99 This parameter defines the impact of the reactive power load sharing error
load share gain signal on the voltage/reactive load controller setpoint. The reactive power
[1.25] 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.
Weighting % LS Gain
10 2,25
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
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 inter‐
acts with.
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 Ä p. 245)
Case - Group breakers A and B are closed and G1 through
I G6 supply the same busbar. The same segment
number is configured to each genset since all gen‐
sets supply the same busbar.
Case - Group breaker A is closed and group breaker B is
II 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 LogicsMan‐
ager function "Segment no.2 act" (param‐
eter 12929 Ä p. 245/Ä p. 853) in order to change
the segment number of G5 and G6 to #2.
Case - Group breakers A and B are open (G1 and G2, G3
III and G4, as well as G5 and G6 supply different bus‐
bars).
A different segment number must be selected for G3
and G4 (LogicsManager function "Segment no.2
act" (parameter 12929 Ä p. 245/Ä p. 853)) as well
as to G5 and G6 (LogicsManager function "Segment
no.3 act" (parameter 12928 Ä p. 245/Ä p. 853)).
With this, the segment number of G3 and G4 is
Fig. 155: Load sharing - grouping changed to #2 and the segment number of G5 and
G6 is changed to #3.
1723 Segment 2 1 to 32 The genset is assigned a load share segment number with this parameter.
number This segment number may be overridden by the following parameters
[1] 12929 Ä p. 245/Ä p. 853, 12928 Ä p. 245/Ä p. 853, and 12927 Ä p. 245/
Ä p. 853.
12929 Segment no.2 2 Determined by Once the conditions of the LogicsManager have been fulfilled, this genset is
act LogicsManager assigned load share segment number 2 (this parameter has priority over
86.87 parameters 12928 Ä p. 245/Ä p. 853 and 12927 Ä p. 245/Ä p. 853).
[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
R = 25.00k | P: 0 − 3 V (0 to 100%)
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 (Logi‐
csManager ID12904 Ä p. 252/Ä p. 852) reduces the desired fre‐
quency setpoint dependent on the active power of the generator
(ID1752 Ä p. 412). In case of a full loaded engine the frequency
setpoint will be reduced with the percentage value
(ID5504 Ä p. 252) related to rated frequency.
Fig. 157: Voltage controller - behavior with and without droop, dia‐
gram
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 genera‐
tors 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).
5747 Droop tracking 2 [On] The frequency and voltage setpoint offset is pre-calcu‐
lated to hold the frequency and voltage, when control is
switched into droop.
5748 Load sharing in 2 [On] As long the load sharing function is enabled, it is done in
droop mode droop mode too.
5507 Frequency con‐ 2 [PID analog] The frequency is controlled using an analog PID controller.
trol
3pos controller The frequency is controlled using a three-step controller.
5508 Freq. control 2 0.0 to 100.0% The value entered for this parameter is the start reference point for the analog
initial state output to the speed controller.
[50.0%]
(Frequency con‐ Notes
trol initial state)
If the output to the speed control has been disabled, the output will act as a
control position reference point.
5510 Proportional 2 0.01 to 100.00 The proportional coefficient specifies the gain. By increasing the gain, the
gain response is increased to permit larger corrections to the variable to be con‐
[1.00] trolled.
The farther outside tolerances the process is, the larger the response action
is to return the process to the tolerance band.
Notes
If the gain is configured too high, the result is excessive overshoot/undershoot
of the desired value.
This parameter is only visible if frequency control (parameter 5507 Ä p. 249)
is configured to "PID analog".
5511 Integral gain 2 0.01 to 100.00 The integral gain identifies the I part of the PID controller.
[1.00] The integral gain corrects for any offset (between setpoint and process vari‐
able) automatically over time by shifting the proportioning band. Reset auto‐
matically 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.
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.
If the integral gain constant is too small, the engine will take too long to settle
at a steady state.
This parameter is only visible if frequency control (parameter 5507 Ä p. 249)
is configured to "PID analog".
5512 Derivative ratio 2 0.01 to 100.00 The derivative ratio identifies the D part of the PID controller.
[0.01] By 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
This parameter is only visible if frequency control (parameter 5507 Ä p. 249)
is configured to "PID analog".
The default configured controller acts like a PI controller what is the valid D
part setting for systems with secondary controllers.
Synchronization
The generator frequency is controlled in such a manner that the measured
frequency does not deviate from the monitored reference (mains or busbar)
frequency by more than the value configured in this parameter without the
controller issuing a frequency raise/lower signal to the frequency control.
This prevents unneeded wear on 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 differen‐
tial) for synchronization.
Notes
This parameter is only visible if frequency control (parameter 5507 Ä p. 249)
is configured to "3pos controller".
5551 Time pulse 1 0.01 to 2.00 s A minimum pulse on time must be configured here.
minimum
[0.05 s] The shortest possible pulse time should be configured to limit overshoot of
the desired speed reference point.
Notes
This parameter is only visible if frequency control (parameter 5507 Ä p. 249)
is configured to "3pos controller".
5552 Gain factor 1 0.1 to 10.0 The gain factor Kp influences the 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 frequency ref‐
erence.
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.
Notes
If the gain is configured too high, the result is excessive overshoot/undershoot
of the desired value.
This parameter is only visible if frequency control (parameter 5507 Ä p. 249)
is configured to "3pos controller".
5636 Cycle time 1 1.0 to 20.0 The cycle time factor adjusts the time between the pulses (pause time).
factor
[1.0] By increasing the cycle time factor, the time between the pulses increases.
Notes
This parameter is only visible if voltage control (parameter 5507 Ä p. 249) is
configured to "3pos controller".
5553 Expand dead‐ 1 1.0 to 9.9 If the measured generator frequency is within the deadband range (param‐
band factor eter 5550 Ä p. 250) and the configured delay expand deadband time (param‐
[1.0] eter 5554 Ä p. 251) expires, the deadband will be multiplied with the factor
configured here.
Notes
This parameter is only visible if frequency control (parameter 5507 Ä p. 249)
is configured to "3pos controller".
5554 Delay expand 1 1.0 to 9.9 s The measured generator frequency must be within the deadband range for
deadband the time configured here in order to multiply the deadband with the factor con‐
[2.0 s] figured in parameter 5553 Ä p. 251.
Notes
This parameter is only visible if frequency control (parameter 5507 Ä p. 249)
is configured to "3pos controller".
5518 AM Frequency 2 Determined by The Frequency setpoint 1 source may be selected from the available data
SP1 [Hz] AnalogManager sources.
81.03
The internal frequency setpoint 05.51 can be changed manually at the set‐
[A1 = 05.51 point screen of the display.
Internal f setp1
[Hz]] Notes
The frequency setpoint may be adjusted within the configured operating limits
( Ä Chapter 4.5.1.1 “ Generator Operating Ranges: Voltage / Frequency /
Busbar” on page 302).
5500 Int. freq. con‐ 2 15.00 to 85.00 The internal generator frequency setpoint 1 is defined in this screen.
trol setpoint 1 Hz
This value is the reference for the frequency controller when performing
(Internal fre‐ [50.00 Hz] islanded and/or no-load operations.
quency control
setpoint 1) 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 2 Determined by The Frequency setpoint 2 source may be selected from the available data
SP2 [Hz] AnalogManager sources.
81.04
The internal frequency setpoint 05.52 can be changed manually at the set‐
[A1 = 05.52 point screen of the display.
Internal f setp2
[Hz]] Notes
The frequency setpoint may be adjusted within the configured operating limits
( Ä Chapter 4.5.1.1 “ Generator Operating Ranges: Voltage / Frequency /
Busbar” on page 302).
5501 Int. freq. con‐ 2 15.00 to 85.00 The internal generator frequency setpoint 2 is defined in this screen.
trol setpoint 2 Hz
This value is the reference for the frequency controller when performing
(Internal fre‐ [50.00 Hz] islanded and/or no-load operations.
quency control
setpoint 2) 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 synchronization to the busbar/utility.
setpoint offset
[0.10 Hz] 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 nega‐
tive).
The activation of MCB sync. with separate slip can be selected with param‐
eter 5709 Ä p. 219 (HMI: configuration | breakers | MCB) hat comes with the
MCB slip freq. setpoint offset parameter 5647 Ä p. 219 (HMI: configuration |
application | controller | frequency).
5505 Phase 2 1 to 99 The phase matching gain multiplies the setting of the proportional gain
matching gain (parameter 5510 Ä p. 249) for phase matching control.
[5]
5506 Phase 2 0.02 to 0.25 Hz Phase matching will only be enabled if the frequency difference between the
matching df- systems to be synchronized is below the configured value.
start [0.05 Hz]
12918 Setpoint 2 freq. 2 Determined by If this LogicsManager condition is TRUE, the frequency setpoint 2 will be
LogicsManager used instead of frequency setpoint 1. The frequency (result of AM)
(Setpoint 2 fre‐ 86.81 5519 Ä p. 251/Ä p. 879 instead of 5518 Ä p. 251/Ä p. 879 will be taken into
quency) account.
[(0 & 1) & 1]
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
Remotely switching the setpoint is possible: Use the LogicsManager com‐
mand variable for input that is correlating with the dedicated bit of parameter
504 Ä p. 543/Ä p. 556.
5516 Start frequency 1 15.00 to 85.00 The frequency controller is activated when the monitored generator frequency
control level Hz has exceeded the value configured in this parameter.
[47.00 Hz] This prevents the easYgen from attempting to control the frequency while the
engine is completing its start sequence.
5517 Start frequency 1 0 to 999 s The frequency controller is enabled after the configured time for this param‐
control delay eter expires.
[5 s]
5503 Freq. control 2 0.10 to 60.00 The different setpoint values are supplied to the controller via this ramp.
setpoint ramp Hz/s
The slope of the ramp is used to alter the rate at which the controller modifies
(Frequency con‐ [2.50 Hz/s] the setpoint value.
trol setpoint
ramp) The faster the change in the setpoint is to be carried out, the greater the value
entered here must be.
5504 Frequency con‐ 2 0.0 to 20.0% If this control is to be operated on a generator in parallel with other generators
trol droop and frequency control is enabled, a droop characteristic curve must be used.
[2.0%]
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 2 Determined by If this LogicsManager condition is TRUE, the frequency droop is enabled.
act. LogicsManager
86.25 Notes
(Frequency
droop active) [08.17 Missing For information on the LogicsManager and its default settings see Ä Chapter
member OR 9.3.1 “LogicsManager Overview” on page 811.
08.06 GCB fail
to open) & 1] 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
12909 Release f-con‐ 2 Determined by This LogicsManager is used to activate generally the frequency biasing to the
trol LogicsManager sub controller. If the LogicsManager is false the output will be on the initial
86.96 state (see parameter 5508 Ä p. 249).
[(1 & 1) & 1] The LogicsManager condition status 'TRUE' is activating the frequency or
power regulation according to the LogigsManager 'F/P control' ID
12940 Ä p. 256/Ä p. 853).
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
5525 Load Control 2 [PID analog] The generator load is controlled using an analog PID controller.
5513 Proportional 2 0.01 to 100.00 The proportional coefficient specifies the gain. By increasing the gain, the
gain response is increased to permit larger corrections to the variable to be con‐
[1.00] trolled.
The farther out of tolerance the process is the larger the response action is to
return the process to the tolerance band.
Notes
If the gain is configured too high, the result is excessive overshoot/undershoot
of the desired value.
This parameter is only visible if load control (parameter 5525 Ä p. 254) is
configured to "PID analog".
5514 Integral gain 2 0.01 to 100.00 The integral gain identifies the I part of the PID controller.
[1.00] The integral gain corrects for any offset (between setpoint and process vari‐
able) automatically over time by shifting the proportioning band.
Reset automatically changes the output requirements until the process vari‐
able and the setpoint are the same.
This parameter permits the user to adjust how quickly the reset attempts to
correct for any offset.
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.
If the integral gain steady is too small, the engine will take too long to settle at
a steady state.
This parameter is only visible if load control (parameter 5525 Ä p. 254) is
configured to "PID analog".
5515 Derivative ratio 2 0.01 to 100.00 The derivative ratio identifies the D part of the PID controller.
[0.01] By 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
This parameter is only visible if load control (parameter 5525 Ä p. 254) is
configured to "PID analog".
The default configured controller acts like a PI controller what is the valid D
part setting for systems with secondary controllers.
5560 Deadband 1 0.10 to 9.99% The generator load is controlled in such a manner, when paralleled with the
mains, so that the monitored load does not deviate from the configured load
[1.00%] setpoint by more than the value configured in this parameter without the con‐
troller issuing a raise/lower signal to the speed control.
This prevents unneeded wear on the raise/lower relay contacts. The config‐
ured percentage for the dead band refers to the generator rated active power
(parameter 1752 Ä p. 412).
Notes
This parameter is only visible if load control (parameter 5525 Ä p. 254) is
configured to "3pos controller".
5561 Time pulse 1 0.01 to 2.00 s A minimum pulse on time must be configured here.
minimum
[0.05 s] The shortest possible pulse time should be configured to limit overshoot of
the desired speed reference point.
Notes
This parameter is only visible if load control (parameter 5525 Ä p. 254) is
configured to "3pos controller".
5562 Gain factor 1 0.1 to 10.0 The gain factor Kp influences the 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 frequency ref‐
erence.
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.
Notes
If the gain is configured too high, the result is excessive overshoot/undershoot
of the desired value.
This parameter is only visible if load control (parameter 5525 Ä p. 254) is
configured to "3pos controller".
5637 Cycle time 1 1.0 to 20.0 The cycle time factor adjusts the time between the pulses (pause time).
factor
[1.0] By increasing the cycle time factor, the time between the pulses increases.
Notes
This parameter is only visible if voltage control (parameter 5525 Ä p. 254) is
configured to "3pos controller".
5563 Expand dead‐ 1 1.0 to 9.9 If the measured generator load is within the deadband range (param‐
band factor eter 5560 Ä p. 255) and the configured delay expand deadband time (param‐
[1.0] eter 5564 Ä p. 255) expires, the deadband will be multiplied with the factor
configured here.
Notes
This parameter is only visible if load control (parameter 5525 Ä p. 254) is
configured to "3pos controller".
5564 Delay expand 1 1.0 to 9.9 s The measured generator load must be within the deadband range for the time
deadband configured here in order to multiply the deadband with the factor configured in
[2.0 s] parameter 5563 Ä p. 255.
Notes
This parameter is only visible if load control (parameter 5525 Ä p. 254) is
configured to "3pos controller".
5522 Load control 2 0.10 to The different setpoint values are supplied to the controller via this ramp. The
setpoint ramp 100.0%/s slope of the ramp is used to alter the rate at which the controller modifies the
1 setpoint value. The faster the change in the setpoint is to be carried out, the
[3.00%/s] greater the value entered here must be.
Notes
This ramp is also used in islanded operation for loading or unloading an addi‐
tional genset. An excessive oscillation may occur if the ramp is configured too
high.
5014 Load control 2 0.01 to The different setpoint values are supplied to the controller via this ramp. The
setpoint ramp 100.0%/s slope of the ramp is used to alter the rate at which the controller modifies the
2 setpoint value. The faster the change in the setpoint is to be carried out, the
[0.15%/s] greater the value entered here must be.
Notes
This ramp is also used in islanded operation for loading or unloading an addi‐
tional genset. An excessive oscillation may occur if the ramp is configured too
high.
11978 2nd load con‐ 2 Determined by The LogicsManager can be used to switch from load ramp 1 to load ramp 2
trol setpoint LogicsManager settings.
ramp 87.77
If this LogicsManager condition is TRUE and load ramp will be performed,
[(0 & 02.02) & [Load control setpoint ramp 2] will be used.
02.02]
5015 Time until set‐ 2 0 to 9999 s The mains decoupling ramp (2nd load ramp) will be disabled after that time
point ramp delay.
reset [0 s]
Notes
This parameter comes with default zero for backward compatibility (2nd load
ramp disabled). BDEW prefers 600 s.
12853 Disable load 2 Determined by The LogicsManager can be used to perform fastest possible load ramp inde‐
setpoint ramp LogicsManager pendent from load ramp settings.
87.76
If this LogicsManager condition is TRUE and load ramp will be performed,
[(02.01& 1) & 1] 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 The ramp rate is used for the unloading in parallel operation or islanded oper‐
unloading [%/sec] ation.
ramp
3.00 [%/sec]
5523 Load control 2 0 to 150% If the maximum generator load is to be limited, a percentage based on the
setpoint max‐ rated generator power (parameter 1752 Ä p. 412) must be entered here. The
imum [100%] 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 2 0 to 100% If the load controller is active, the generator operates with the configured min‐
power imum generator power, even if the actual active power setpoint is lower than
[0%] that parameter value.
This parameter isn't used during the unloading sequence.
5524 Min. generator 2 0 to 100% If the minimum generator load is to be limited, a percentage based on the
import/export rated generator power (parameter 1752 Ä p. 412) must be entered here. The
[0%] 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 The LogicsManager can be used to control whether frequency control or
LogicsManager active power control should be performed.
86.98
If this LogicsManager condition is TRUE, the active power control is per‐
[(04.07& 04.06) formed.
& 1]
12998 Setp. 3load 2 Determined by If this LogicsManager condition is TRUE, the frequency setpoint 3 will be ena‐
LogicsManager bled, i.e. the setting of parameter 5606 Ä p. 261/Ä p. 880 overrides the set‐
(Setpoint 3 load) 87.67 ting of parameter 5539 Ä p. 260/Ä p. 879 but setpoint 2 becomes priority.
[(0 & 1) & 1] Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
5796 Load setpoint 2 Import The value entered for the import level shall always be supplied by the utility.
3 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 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
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.
5795 Int. load con‐ 0 0.0 to 9999.9 The load setpoint 3 is defined in this screen. This value is the reference for
trol setpoint 3 kW the load controller when performing parallel operations.
(Internal load [200.0 kW]
control setpoint
3)
3465 Min. Generator 1 0 to 100% This is the minimum active power setpoint. Any lower other active power set‐
power point will be ignored!
[0%]
Notes
For backward compatibility reasons the default value is zero.
This min. value is also used for the AnalogManager data sources Ä Chapter
9.4.1 “Data Sources AM” on page 856
n 05.19 Used power setpoint without ramp
and
n 05.20 Used power setpoint with ramp
Function
Example The power derating ΔP may be calculated using the following for‐
mula:
ΔP = PM [kW] x R [%/Hz] x (FMains [Hz] - FStart [Hz]) / 100 [%]
The example uses the following values:
n PM = 130 kW
n R = 40%/Hz (parameter 5784 Ä p. 259)
n FStart = 50.20 Hz (parameter 5782 Ä p. 259)
n FMains = 50.50 Hz
The power derating ΔP is calculated as follows:
n ΔP = 130 kW x 40 %/Hz x (50.50 Hz - 50.20 Hz] / 100% = 15.6
kW
n The assumed frequency increases to 50.70 Hz:
n ΔP = 130 kW x 40 %/Hz x (50.70 Hz - 50.20 Hz] / 100% = 26.0
kW
The derating becomes inactive, if the frequency becomes lower
than FStop (Parameter 5783 Ä p. 259). (If the frequency becomes
too high, the frequency monitoring function trips.)
Start conditions The power derating function becomes active, if the following condi‐
tions are true:
n Mains frequency > FStart (parameter 5782 Ä p. 259) AND
n Mains parallel operation active (MCB and GCB are closed)
AND
n easYgen is in AUTOMATIC mode AND
n 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:
n Mains frequency < FStop (parameter 5783 Ä p. 259) OR
n Mains parallel operation not active (MCB and GCB are open )
OR
n easYgen is not in AUTOMATIC mode OR
n The corresponding controller functions are switched "Off"
Function behavior If the frequency decreases, while the derating is still active, the
behavior depends on parameter “Hold max.derating” (parameter
5785 Ä p. 259).
Example
The following assumptions are made:
n The corresponding parameters are set to default
n Derating has started with FStart = 50.20 Hz with PM = 130 kW
n The current frequency is 50.70 Hz → reduction ΔP = 26 kW →
current power = 104 kW
Now the measured frequency decreases to 50.50 Hz:
n “Hold max. derating” (parameter 5785 Ä p. 259) = Off - The
derating ΔP decreases to 15.6 kW according to the gradient
40 %/Hz → the power is increasing to 114.4 kW.
n “Hold max. derating” (parameter 5785 Ä p. 259) = On - The
derating still remains at 26 kW → the power remains at 104 kW.
During a 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.
5781 Function 2 On F/P load derating is switched on. The power will be derated, if the frequency
becomes higher than “f start value” (parameter 5782 Ä p. 259).
5782 f start value 2 15.00 to 85.00 The derating function becomes active if the measured frequency becomes
Hz higher than this value.
[50.20 Hz]
5783 f stop value 2 15.00 to 85.00 The derating function becomes inactive if the measured frequency becomes
Hz lower than this value.
[50.15 Hz]
5784 f dep. derating 2 1 to 100%/Hz This function works with the derating gradient defined here, if the derating
function is active. The higher this value, the higher the derating.
[40 %/Hz]
5785 Hold max. 2 On While the derating is still active, the power never increases again.
derating
[Off] While the derating is still active, the power can increase according to the
defined gradient, if the measured frequency becomes lower. (Even if the fre‐
quency is still higher than “f stop value” (parameter 5783 Ä p. 259))
5526 Load setpoint 2 Import The value entered for the import level shall always be supplied by the utility.
1 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 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
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.
5520 Int. load con‐ 2 0.0 to 99999.9 The load setpoint 1 is defined in this screen. This value is the reference for
trol setpoint 1 kW the load controller when performing parallel operations.
(Internal load [100.0 kW]
control setpoint
1)
5539 AM ActPower 2 Determined by The load setpoint 1 source may be selected from the available data sources.
SP1 [W] AnalogManager
81.05 The internal load setpoint 05.54 can be changed manually at the setpoint
screen of the display.
[A1 = 05.54
Internal P Notes
setp1 [W]]
The load setpoint may be adjusted between 0 and the configured load control
setpoint maximum (parameter 5523 Ä p. 256).
5527 Load setpoint 2 Import The value entered for the import level shall always be supplied by the utility.
2 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 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
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.
5521 Int. load con‐ 2 0.0 to 99999.9 The load setpoint 2 is defined in this screen. This value is the reference for
trol setpoint 2 kW the load controller when performing parallel operations.
(Internal load [200.0 kW]
control setpoint
2)
5540 AM ActPower 2 Determined by The load setpoint 2 source may be selected from the available data sources.
SP2 [W] AnalogManager
81.06 The internal load setpoint 05.55 can be changed manually at the setpoint
screen of the display.
[A1 = 05.55
Internal P Notes
setp2 [W]]
The load setpoint may be adjusted between 0 and the configured load control
setpoint maximum (parameter 5523 Ä p. 256).
12919 Setp. 2 load 2 Determined by If this LogicsManager condition is TRUE, the ActPower setpoint 2 will be used
LogicsManager instead of ActPower setpoint 1. The ActPower (result of AM) 5540 Ä p. 260/
(Setpoint 2 load) 86.82 Ä p. 490/Ä p. 879 instead of 5539 Ä p. 260/Ä p. 879 will be taken into
account.
[(0 & 1) & 1]
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
Remotely switching the setpoint is possible: Use the LogicsManager com‐
mand variable for input that is correlating with the dedicated bit of parameter
504 Ä p. 543/Ä p. 556.
5596 Load setpoint 2 Import The value entered for the import level shall always be supplied by the utility.
3 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 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
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.
5795 Int. load con‐ 2 0.0 to 99999.9 The load setpoint 3 is defined in this screen. This value is the reference for
trol setpoint 3 kW the load controller when performing parallel operations.
(Internal load [150.0 kW]
control setpoint
2)
5606 AM ActPower 2 Determined by The load setpoint 3 source may be selected from the available data sources.
SP3 [W] AnalogManager
81.07 The internal load setpoint 05.80 can be changed manually at the setpoint
screen of the display.
[A1 = 05.80
Internal P Notes
setp3 [W]]
The load setpoint may be adjusted between 0 and the configured load control
setpoint maximum (parameter 5523 Ä p. 256).
12998 Setp. 3 load 2 Determined by If this LogicsManager condition is TRUE and [Setp. 2 load] is not TRUE, the
LogicsManager frequency setpoint 3 will be enabled., i.e. the setting of parameter
(Setpoint 3 load) 87.67 5606 Ä p. 261/Ä p. 880 overrides the setting of parameter 5539 Ä p. 260/
Ä p. 879.
[(0 & 1) & 1]
If this LogicsManager condition is TRUE, the frequency setpoint 3 will be
used instead of frequency setpoint 2. The ActPower SP3 (result of AM)
5606 Ä p. 261/Ä p. 880 instead of 5539 Ä p. 260/Ä p. 879 will be taken into
account.
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
Remotely switching the setpoint is possible: Use the LogicsManager com‐
mand variable for input that is correlating with the dedicated bit of parameter
504 Ä p. 543/Ä p. 556.
5999 Load setpoint 2 Import The value entered for the import level shall always be supplied by the utility.
4 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 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
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.
5998 Int. load con‐ 2 0.0 to 99999.9 The load setpoint 4 is defined in this screen. This value is the reference for
trol setpoint 3 kW the load controller when performing parallel operations.
(Internal load [50.0 kW]
control setpoint
4)
5609 AM ActPower 2 Determined by The load setpoint 4 source may be selected from the available data sources.
SP4 [W] AnalogManager
81.08 The internal load setpoint 05.84 can be changed manually at the setpoint
screen of the display.
[A1 = 05.84
Internal P Notes
setp4 [W]]
The load setpoint may be adjusted between 0 and the configured load control
setpoint maximum (parameter 5523 Ä p. 256).
12269 Setp. 4 load 2 Determined by If this LogicsManager condition is TRUE and neither [Setp. 2 load] nor
LogicsManager [Setp. 3 load] is true, the frequency setpoint 4 will be enabled, i.e. the setting
(Setpoint 4 load) 87.75 of parameter 5609 Ä p. 261/Ä p. 880 overrides the setting of param‐
eter 5539 Ä p. 260/Ä p. 879.
[(0 & 1) & 1]
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
Remotely switching the setpoint is possible: Use the LogicsManager com‐
mand variable for input that is correlating with the dedicated bit of parameter
504 Ä p. 543/Ä p. 556.
5532 Warm-up load 2 0 to 100% The maximum load is limited to this percentage of the generator rated power
limit (parameter 1752 Ä p. 412) until the warm-up time (parameter 5534 Ä p. 262)
[15%] has expired or the warm-up temperature threshold (parameter 5546 Ä p. 262)
has been exceeded.
5534 Warm-up time 2 0 to 9999 s The maximum load is limited to the value configured in param‐
eter 5532 Ä p. 262 for the time configured here.
[0 s]
Notes
This parameter is only effective if "Warm-up mode" (param‐
eter 5533 Ä p. 262) is configured to "Time controlled".
5533 Warm-up mode 2 Analog val contr The maximum load is limited to the value configured in parameter
5532 Ä p. 262 until the temperature measured according to the setting in
parameter 5538 Ä p. 262/Ä p. 880 has exceeded the threshold configured in
parameter 5546 Ä p. 262.
[Time con‐ The maximum load is limited to the value configured in param‐
trolled] eter 5532 Ä p. 262 until the time configured in parameter 5534 Ä p. 262 has
expired.
5546 Warm-up 2 0 to 1000 °C The maximum load is limited to the value configured in parameter
threshold 5532 Ä p. 262 until the temperature has exceeded the threshold configured
[80 °C] here.
Notes
This parameter is only effective if "Warm-up mode" (param‐
eter 5533 Ä p. 262) is configured to "Analog val contr".
5538 AM Warm-up 2 Determined by The engine warm-up criterion may be selected from the available data
criterion AnalogManager sources.
81.02
Notes
[A1 = 10.01
ZERO] This parameter is only effective if "Warm-up mode" (param‐
eter 5533 Ä p. 262) is configured to "Analog val contr".
Block Diagram
Derating priority
If more than one derating function is configured the
one which calculates the lowest setpoint becomes
effective.
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 reduc‐
tion. 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.
Combined Derating and Uprating If parameter Direct Derating (ID15149) is enabled, the output value
of the AnalogManager AM Derating source (ID 15147 Ä p. 270/
Ä p. 879) 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.
Freely scalable derating character‐ The easYgen-XT offers a characteristic which is linearly
istic decreasing the momentary active power setpoint according to the
value offered by the AnalogManager 15147 Ä p. 270/Ä p. 879.
The characteristic is defined by the following parameters:
n 15143: “Start derating at”
n 15144: “Stop derating at”
n 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 devi‐
ation 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:
Fig. 160: 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 tem‐
perature 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 reduc‐
tion 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 min‐
imum 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.
Derating Parameters
ID Parameter CL Setting range Description
[Default]
15149 Direct derating 2 On Only the analog source is used for the up-/derating. The parameters 15143,
on/off 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 2 -032000 to This parameter defines the starting point when the derating becomes active.
at 032000 The value applies to the analog source (parameter 15147 Ä p. 270/Ä p. 879).
[1000] Value of the analog source which starts derating.
15144 Stop derating 2 -032000 to This parameter defines (in combination with parameter 15143 Ä p. 270) the
at 032000 ramp of the derating function.
[0] Value of the analog source which ends derating.
15145 Max. power 2 1.0 to 100.0% This parameter defines the maximal power deviation of the derating function.
deviation That means it determines also the minimal power while derating is active.
[100.0%]
100% minus this value is the lowest P value reachable by free derating.
The configured percentage for the max. power deviation refers to the gener‐
ator rated active power (parameter 1752 Ä p. 412).
15146 Free derating 2 Determined by This LogicsManager equation releases the free derating function.
LogicsManager
87.60
[(02.01 & 1] &
1]
15147 AM Derating 2 Determined by This parameter defines the analog source [Analog input 1] which controls the
source AnalogManager derating function.
81.21
[A1 = 06.01
Analog input 1]
15142 J1939 derating 2 To prevent knocking in the engine, some ECUs (Engine Control Unit) transmit
(see a J1939 CAN message to derate the power (in percentage of rated power).
chapter The easYgen is able to accept this message and to derate the power
below according to this message. If derating is active, the display shows the indica‐
too) tion “Derating”.
On The derate command issued from the ECU via J1939 message is accepted.
15142 J1939 derating 2 To prevent knocking in the engine, some ECUs (Engine Control Unit) transmit
a J1939 CAN message to derate the power (in percentage 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 indica‐
tion “Derating”.
On The derate command issued from the ECU via J1939 message is accepted.
16338 Description 2 user-defined This text will be displayed on the Setpoints screens. The text may have 1
through 16 characters.
16339 [PID controller
{x}]
16348
Notes
This parameter may only be configured using ToolKit.
5580 PID{x} 2 If this LogicsManager condition is TRUE, the PID {x} controller will be
ctrl.release PID{x} Deter‐ released.
5593 mined by Logi‐
csManager
5679
87.17, 87.18,
87.19
[(0 & 1) & 1]
=
11406/11407/11
408
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
5572 Proportional 2 0.001 to 65.000 The proportional coefficient specifies the gain. By increasing the gain, the
gain response is increased to permit larger corrections to the variable to be con‐
5585 [1.000] trolled.
5671 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.
5573 Integral gain 2 0.010 to 10.000 The integral gain identifies the I part of the PID controller. The integral gain
corrects for any offset (between setpoint and process variable) automatically
5586 [0.100] over time by shifting the proportioning band.
5672 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.
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.
5574 Derivative ratio 2 0.001 to 10.000 The derivative ratio identifies the D part of the PID controller. By increasing
this parameter, the stability of the system is increased. The controller will
5587 [0.001] attempt to slow down the action of the actuator in an attempt to prevent
5673 excessive overshoot or undershoot. Essentially this is the brake for the
process.
5575 Time pulse 1 0.01 to 2.00 s A minimum pulse on time must be configured here. The shortest possible
minimum pulse time should be configured, but the actuator should still react safe, to
5588 [0.05 s] limit overshoot of the desired speed reference point. (Only three-position con‐
5674 troller)
5576 Deadband 1 0 to 32000 Shows the adjust range around the setpoint value when no displace impulse
is issued. This avoids an unnecessary abrasion of relay contacts for higher/
5589 [10] lower. (Only three-position controller)
5675
5578 PID{x} control 2 Determined by The PID {x} control actual value may be selected from the available analog
actual value AnalogManager data sources. It is possible to select all data sources ( Ä Chapter 9.4.1 “Data
5591 Sources AM” on page 856).
81.14, 81.16,
5677 81.18: [A1 =
10.01 ZERO]
5577 PID{x} control 2 Determined by The PID {x} control setpoint source may be selected from the available analog
setpoint AnalogManager data sources. It is possible to select all data sources ( Ä Chapter 9.4.1 “Data
5590 Sources AM” on page 856).
81.13, 81.15,
5676 81.17: [A1 =
05.75/76/77 Int.
PID{x} set‐
point]
5579 Int. PID{x} con‐ 1 -32000 to 32000 The internal setpoint is defined in this screen. This value is the reference for
trol setpoint the PID {x} controller.
5592 [0]
5678
5581 PID{x} control 2 0 to 100% The value entered for this parameter is the start reference point for the analog
initial state output to the controller as long as the LogicsManager is false. If the PID con‐
5594 [50%] troller has been disabled (e.g. Parameter 5571 Ä p. 271), the bias output will
5680 change to 0 %.
5582 Sampling time 2 1 to 360 s The sampling time is configured here. This is the time between two consecu‐
tive samples.
5595 [1 s]
The sampling time shall be configured high enough that the actual value can
5681 react in case e.g. a temperature just shifts slowly.
5692 Actuator run 2 0.1 to 999.0 s The actuator run time is configured here. This is the time the actuator needs
time to move from fully closed to fully open. This information is necessary because
5693 [30.0 s] the controller does not receive a feedback of the actuator position and needs
5694 this value to calculate the desired actuator position.
5734 PID{x} control 1 0 to 32000 The PI band is configured here to encounter excessive overshoot of the
PI band process value when starting up. The PI band defines the range around the
5735 [2000] setpoint, in which the I portion of the PID controller is active.
5736 If the actual value is outside of this band, the I portion is reduced to a min‐
imum 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 supplied to the controller via this ramp to
setpoint ramp prevent an overshoot of the process value when enabling the controller.
5738 [10]
The slope of the ramp is used to alter the rate at which the controller modifies
5739 the setpoint value. The faster the change in the setpoint is to be carried out,
the greater the value entered here must be.
7494 Unit 2 User-defined up This parameter is assigning a unit text to the displayed analog value.
to 6 characters
7495 text Notes
7496 [______] This parameter may only be configured using ToolKit.
The max. number of characters is 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. Please verify the length on the display for best view!
12900 Discrete f/P + 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the frequency /
LogicsManager load setpoint will be raised.
86.21
[(0 & 1) & 1]
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12901 Discrete f/P - 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the frequency /
LogicsManager load setpoint will be lowered.
86.22
[(0 & 1) & 1]
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12902 Discrete V/PF + 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the voltage /
LogicsManager reactive power setpoint will be raised.
86.23
[(0 & 1) & 1]
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12903 Discrete V/PF - 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the voltage /
LogicsManager reactive power setpoint will be lowered.
86.24
[(0 & 1) & 1]
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
5024 Discrete ramp f 2 000.01 ... Configurable ramp rate for frequency setpoint raise and lower commands.
+/- 100.00 %/s
[000.07 %/s]
5025 Discrete ramp 2 000.01 ... Configurable ramp rate for voltage setpoint raise and lower commands.
V +/- 100.00 %/s
[000.70 %/s]
5026 Discrete ramp 2 000.01 ... Configurable ramp rate for active power setpoint raise and lower commands.
P +/- 100.00 %/s
[003.00 %/s]
5027 Discrete ramp 2 000.01 ... Configurable ramp rate for Power Factor (PF) setpoint raise and lower com‐
Power Factor 100.00 %/s mands.
+/-
[007.50 %/s]
1795 Startup in 2 If the controller is powered down, the unit will start in the following configured
mode mode when it is powered up again.
(Operating [STOP] The unit starts in the STOP operating mode.
mode after
applying the AUTO The unit starts in the AUTOMATIC operating mode.
power supply )
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.
Notes
For the selection of the operating mode via the LogicsManager (if two dif‐
ferent operating modes have been selected simultaneously) the control unit
will prioritize the modes as follows:
n 1. STOP
n 2. MANUAL
n 3. AUTOMATIC
n 4. TEST
Determined by Once the conditions of the LogicsManager have been fulfilled the unit will
LogicsManager change into operating mode AUTOMATIC.
86.16
Notes
[(0 & 1) & 1]
For information on the LogicsManager and its default settings see Ä Chapter
= 10715 9.3.1 “LogicsManager Overview” on page 811.
12520 Operat. mode 2 Determined by Once the conditions of the LogicsManager have been fulfilled the unit will
MAN LogicsManager change into operating mode MANUAL.
86.17
(Activate oper‐ If MANUAL mode is selected via the LogicsManager it is not possible to
ating mode [(0 & 1) & 1] change operating modes via the front panel.
MANUAL)
= 10716 Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12530 Operat. mode 2 Determined by Once the conditions of the LogicsManager have been fulfilled the unit will
STOP LogicsManager change into operating mode STOP.
86.18
(Activate oper‐ If STOP mode is selected via the LogicsManager it is not possible to change
ating mode [(0 & 1) & 1] operating modes via the front panel.
STOP)
= 10717 Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12271 Operat. mode 2 Determined by Once the conditions of the LogicsManager have been fulfilled the unit will
TEST LogicsManager change into operating mode TEST.
86.29
(Activate oper‐ If TEST mode is selected via the LogicsManager it is not possible to change
ating mode [(0 & 1) & 1] operating modes via the front panel.
TEST)
= 12272 Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12120 Start req. in 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the control
AUTO LogicsManager issues a start request in AUTOMATIC mode.
86.09
(Start request in Notes
operation mode [(09.02 Dis‐
AUTOMATIC) crete input OR For information on the LogicsManager and its default settings see Ä Chapter
0) OR 04.13 9.3.1 “LogicsManager Overview” on page 811.
Remote
request] ≥1: math. "OR"
= 10708
12190 Stop req. in 2 Determined by If this logical output becomes TRUE, it inhibits all other start processes (e.g.
AUTO LogicsManager Start req. in Auto, emergency power, etc.). Stopping of the engine can be initi‐
86.10 ated externally via a discrete input or any logical combination.
(Stop request in
operation mode [(0 & 1) & 1] Once the conditions of the LogicsManager have been fulfilled, the control
AUTOMATIC) issues a stop request in AUTOMATIC mode.
= 10709
Notes
It is possible to interrupt an already activated emergency run.
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12540 Start w/o load 2 Determined by If this LogicsManager condition is TRUE switching from mains to generator
LogicsManager supply following an engine start is prevented (the GCB close operation is
(Start without 86.19 blocked).
assuming load )
[(0 & 1) & 1] 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.
= 10718
If this condition becomes TRUE in islanded operation, the GCB cannot be
opened before the MCB has been closed.
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
Fig. 164: TEST button 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.
4672 TEST run 2 [No load w/o With enabling the operation mode TEST, the engine starts automatically. The
mode time] GCB remains open.
No load w. time With enabling the operation mode TEST, the engine starts automatically. The
GCB remains open. After a configurable time (4679 Ä p. 278), the device
switches to the operation mode configured with parameter 4680 Ä p. 278
“Operation mode after TEST” .
Load w/o time With enabling the operation mode TEST, the engine starts automatically. The
GCB will be closed according to the configured “Breaker transition mode”
(3411 Ä p. 213).
If mains parallel operation is configured, the current active and reactive power
setpoint is controlled.
Load with time With enabling the operation mode TEST, the engine starts automatically. The
GCB will be closed according to the configured “Breaker transition mode”
(3411 Ä p. 213).
If mains parallel operation is configured, the current active and reactive power
setpoint is controlled. After a configurable time (4679 Ä p. 278), the device
switches to the operation mode configured with parameter 4680 Ä p. 278
“Operation mode after TEST” .
Breaker access With enabling the operation mode TEST, the engine starts automatically.
From there on the breakers can be operated manually according to the con‐
figured „Breaker transition mode“ (3411 Ä p. 213).
Notes
In breaker transition mode “parallel” the MCB open and close commands are
not supported.
4679 TEST mode 2 [60 s] This is the time duration for the time restricted TEST mode.
time restriction
0..9999 s
4680 Operation 2 This is the operation mode, on which the genset control changes after the
mode after time restricted TEST run.
TEST
After the TEST run ...
[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.
Interchange n With the GCB button and the MCB button the
load test can be started and interrupted
n The load transfer is similar to the AUTO‐
MATIC mode
n 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 / n With the GCB button and the MCB button the
Open transition load test can be started and interrupted
n 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)
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 oper‐
ation LogicsManager output becomes TRUE (logic "1"). The "Crit‐
ical 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 Ä p. 168). All shutdown
alarms become warning messages (see above).
Critical mode "Off" A critical mode will be interrupted/stopped once critical mode oper‐
ation 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.
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.
n The "Critical mode" message is displayed on the display
screen. All shutdown alarms become warning messages.
n If critical mode is disabled again, all shutdown alarms become
active again.
If the genset was not running before critical mode has been ena‐
bled, it will be stopped after the critical mode postrun time (param‐
eter 4102 Ä p. 168) has expired. MCB operation will be performed
according to the configured transition mode.
Emergency power during critical If there is a mains failure during critical mode, the "Emerg/Critical"
mode message is displayed on the display screen after the mains fail
delay time (parameter 2800 Ä p. 301) has expired.
All shutdown alarms become warning messages.
n 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 gener‐
ator supply to mains supply after the mains settling delay
expires.
n 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 set‐
tling 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 crit‐
ical mode are no longer existent.
– If the genset was not running before critical mode has been
enabled, it will be stopped after cool down time (param‐
eter 3316 Ä p. 169) has expired.
– The GCB will take the same state as it had before the crit‐
ical mode has been enabled.
Critical mode during emergency An emergency power operation is active (load is supplied by the
power 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.
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.
n 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.
n Start request will be terminated before the critical mode is ter‐
minated:
– 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.
– If the genset was not running before critical mode has been
enabled, it will be stopped after cool down time (param‐
eter 3316 Ä p. 169) has expired.
– The GCB will take the same state as it had before the crit‐
ical mode has been enabled.
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 dis‐
play 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 Ä p. 168) has expired.
Emergency power during critical If there is a mains failure during critical mode, the MCB will be
mode opened after the mains fail delay time (parameter 2800 Ä p. 301)
has expired and the GCB will be closed. It is not necessary to con‐
figure parameter 4101 Ä p. 301 (Break emerg. in critical mode)
because the critical operation is already supplied. The "Emerg/Crit‐
ical" message is displayed on the display screen and all shutdown
alarms become warning messages.
n 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 gener‐
ator supply to mains supply after the mains settling delay
expires.
n 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 set‐
tling delay expires.
– The GCB will be opened without unloading (transition mode
interchange or parallel).
– All shutdown alarms become active again.
– If the genset was not running before critical mode has been
enabled, it will be stopped after cool down time (param‐
eter 3316 Ä p. 169) has expired.
Critical mode during emergency An emergency power operation is active (load is supplied by the
power 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 Ä p. 301 (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.
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.
n Critical mode ends before the start request is terminated:
– The engine continues running and a change to generator or
parallel operation is performed.
– All shutdown alarms will become active again.
n Start request will be terminated before the critical mode is ter‐
minated:
– 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.
– If the genset was not running before critical mode has been
enabled, it will be stopped after cool down time (param‐
eter 3316 Ä p. 169) has expired.
– 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 config‐
ured transition mode (parameter 3411 Ä p. 213). 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.
Critical mode during islanded oper‐ The busbar is supplied by the generator and emergency run
ation (parameter 2802 Ä p. 301) is disabled. If the critical mode is ena‐
bled, the GCB will be opened although the MCB is not enabled.
This will cause a dead busbar.
Parameters
ID Parameter CL Setting range Description
[Default]
12220 Critical mode 2 Determined by If this logical output becomes TRUE in AUTOMATIC operating mode, it starts
LogicsManager the critical mode.
86.28
Notes
[(0 & !05.08
Start fail) & ! For information on the LogicsManager and its default settings see Ä Chapter
09.01 DI01] 9.3.1 “LogicsManager Overview” on page 811.
= 11607
4109 Critical mode 2 0 to 6000 s The critical mode operation is continued for the time configured here after the
postrun critical mode request has been terminated.
[600 s]
The message "Cool down" is displayed and the LogicsManager command
variable 04.10 becomes TRUE.
4100 Close GCB in 2 Yes If a critical mode operation is detected the GCB will close.
critical mode
[No] The GCB cannot be closed during a critical mode operation.
Notes
This parameter only applies to application mode .
4105 Critical mode 2 Yes The critical mode alarm classes will override the normal operation alarm
alarm class classes when in MANUAL operation mode so alarm classes become
MAN restricted to WARNING level - NO engine shut down. LogicsManager output
12220 Ä p. 285/Ä p. 850 becomes TRUE.
(Critical mode
alarm classes [No] The alarm classes will not be changed in the MANUAL operating mode e.g.
active in engine shut down is possible!
MANUAL oper‐
ating mode )
Generator Load
If the "Start stop mode" (parameter 5752 Ä p. 290) 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 Ä p. 294 or
5770 Ä p. 298 "IOP/MOP Max. generator load"), a configured per‐
centage (e.g. 80%) of the rated power. In order to stop one gener‐
ator, the load of all gensets in operation must fall below the min‐
imum generator load (parameter 5763 Ä p. 295 or 5771 Ä p. 298
"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:
n With higher dynamic the efficiency can be increased, but the
change of generators becomes more frequent.
n With lower dynamic the efficiency can be lower for the first
couple of engines, but overall the change of generators
becomes less frequent.
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 Ä p. 297), the first genset will be added.
n PMNsetpoint – PMNreal > PMOPminimum
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 Ä p. 298), another
genset will be added.
n 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 Ä p. 298)
n 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 Ä p. 297) minus the hysteresis (param‐
eter 5769 Ä p. 297), the genset will be stopped.
The hysteresis is intended to prevent frequent starting and stop‐
ping of gensets in case of small load variations.
n PMNsetpoint – PMNreal + PGN real active < PMOP minimum – Physteresis
MOP
Mains parallel operation (MOP) n Preserve = Prated active – PGN real active
n Prated active = PRatedGen [1] + PRatedGen [2] + … + PRatedGen [n]
(total rated power of all gensets on the busbar in the system)
n 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 Ä p. 297), the first genset will be added.
n 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 Ä p. 297), another genset will be
added.
n 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 Ä p. 297) plus the hysteresis (param‐
eter 5769 Ä p. 297) plus the rated load of the genset, the genset
will be stopped.
The hysteresis is intended to prevent frequent starting and stop‐
ping of gensets in case of small load variations.
n Preserve > Preserve parallel + Physteresis MOP + PRatedGen
If one genset is supplying the load in parallel with the mains and
the generator load exceeds the MOP minimum load threshold
(parameter 5767 Ä p. 297) minus the hysteresis (param‐
eter 5769 Ä p. 297), the genset will be stopped.
The hysteresis is intended to prevent frequent starting and stop‐
ping of gensets in case of small load variations.
n PMN setpoint – PMN real + PGN real active < PMOP minimum – Physteresis MOP
Generator Selection
General notes If a genset is to be started, the genset with the highest priority con‐
figured 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 disa‐
bled, the remaining hours until the next maintenance are consid‐
ered. If these are also the same, the genset with the lowest gener‐
ator number will be started first or stopped last.
Priority order:
n 1. Priority (parameter 5751 Ä p. 290)
n 2. Efficiency (size of engines) (parameter 5754 Ä p. 291)
n 3. Service hours (parameter 5755 Ä p. 291)
n 4. Generator (device) number (parameter 1702 Ä p. 155)
The load-dependent start/stop function requires the following con‐
ditions have been met:
n The control has been placed in AUTOMATIC operating mode
n A start request (Start req. in AUTO, Emergency run) is active
n All LDSS parameters are configured identically for all members
at the load share line ( Ä Chapter 4.5.6.11 “Multi-Unit Param‐
eter Alignment” on page 402)
12930 LD start stop 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the load-
LogicsManager dependent start/stop function is enabled.
(Load- 86.86
dependent start Notes
stop) [(0 & 1) & 1]
For information on the LogicsManager and its default settings see Ä Chapter
= 11915 9.3.1 “LogicsManager Overview” on page 811.
5752 Start stop 2 [Reserve Load-dependent start stop is performed in a way that a configured minimum
mode power] 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 2 [All] All available gensets will be started in case of a dead busbar and remain con‐
start mode nected to the busbar for the minimum running time (param‐
eter 5759 Ä p. 292). Then the gensets will be stopped according to the con‐
figured LDSS procedure. The start delay is configured in
parameter 2800 Ä p. 301 (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 par‐
allel operations because it cannot control the MCB operation.
If the MCB should be operated, the emergency run function (parameter
2802 Ä p. 301) must be enabled.
5751 Base priority 2 1 to 32 The priority of the genset in the load-dependent start/stop network is config‐
ured with this parameter ( Ä Chapter 4.4.5.1.5.3 “Generator Selection”
[5] on page 289). The lower the number configured here, the higher the priority.
This priority may be overridden by the LDSS Priority parameters (parameters
12924 Ä p. 290/Ä p. 853, 12925 Ä p. 290/Ä p. 853, and 12926 Ä p. 290/
Ä p. 853).
12926 LDSS Priority 2 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the load-
LogicsManager dependent start/stop priority will be set to 2 (the highest priority is valid).
86.90
Notes
[(0 & 1) & 1]
For information on the LogicsManager and its default settings see Ä Chapter
= 111919 9.3.1 “LogicsManager Overview” on page 811.
12925 LDSS Priority 3 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the load-
LogicsManager dependent start/stop priority will be set to 3 (the highest priority is valid).
86.91
Notes
[(0 & 1) & 1]
For information on the LogicsManager and its default settings see Ä Chapter
= 11920 9.3.1 “LogicsManager Overview” on page 811.
12924 LDSS Priority 4 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the load-
LogicsManager dependent start/stop priority will be set to 4 (the highest priority is valid).
86.92
Notes
[(0 & 1) & 1]
For information on the LogicsManager and its default settings see Ä Chapter
= 11921 9.3.1 “LogicsManager Overview” on page 811.
5754 Fit size of 2 This parameter defines whether the start/stop priority order ( Ä Chapter
engine 4.4.5.1.5.3 “Generator Selection” on page 289) 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 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 2 With this parameter the LDSS function can be configured to start and stop
hours 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 Ä p. 291
“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 gen‐
sets 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 started for gensets with same priority. The gen‐
sets are utilized in 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” (parameters 15723 Ä p. 870) are considered when
evaluating the engines to be started for gensets with same priority. The gen‐
sets are utilized in 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.
Notes
If the LDSS function “Fit service hours” (parameter 5755 Ä p. 291) is ena‐
bled with "Equal" or "Period of use" hours, this configuration gets valid. Other‐
wise this parameter can be ignored.
For more details go to chapter Ä Chapter 9.4.1.10 “Group 11: Engine Values”
on page 870.
[Off] No engine change will be performed. The engines are selected according to
the setting of parameter 5755 Ä p. 291 (Fit service hours) with 1 hour spacing
in case of load changes.
All 128 h All relevant engines are changed with a 128 hour spacing.
Notes
This parameter is only effective if [Start stop mode] (parameter
5752 Ä p. 290) 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 consid‐
ered, 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 run‐ 2 0 to 32000 s If a genset has been started by the LDSS function, it continues to operate at
ning time least for this time even if it would have been stopped before.
[180 s]
This timer is started with the closure of the GCB. If an emergency run is
active ( Ä Chapter 4.4.6 “Emergency Run” on page 299) 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 Ä p. 346) has expired.
5760 IOP Reserve 2 1 to 999999 kW The value configured for the reserve power determines when an additional
power generator will be started. The reserve power is the desired spinning reserve
[100 kW] 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 configured
in this parameter, the next generator will be started.
= Reserve power
Notes
This parameter is only effective if start stop mode (parameter 5752 Ä p. 290)
is configured to "Reserve power".
5648 IOP Reserve 2 1 to 999999 kW The value configured for the reserve power determines when an additional
power 2 generator will be started. The reserve power is the desired spinning reserve
[200 kW] 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 configured
in this parameter, the next generator will be started.
= Reserve power
Notes
This parameter is only effective if start stop mode (parameter 5752 Ä p. 290)
is configured to "Reserve power".
12604 IOP Reserve 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the 'IOP
power 2 LogicsManager Reseve power 2' (parameter 5648 Ä p. 294) is used instead of the 'IOP
86.41 Reseve power' (parameter 5760 Ä p. 294).
[(0 & 1) & 1] Notes
= 11975 For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
5761 IOP Hysteresis 2 1 to 65000 kW If the reserve power is sufficient to stop one genset without falling below the
threshold and the hysteresis configured here, a genset will be stopped.
[20 kW]
Notes
This parameter is only effective if start stop mode (parameter 5752 Ä p. 290)
is configured to "Reserve power".
5762 IOP Max. gen‐ 2 0 to 100% If the generator load exceeds the threshold configured here, the load-
erator load dependent start/stop function will start another genset.
[70%]
Notes
This parameter is only effective if start stop mode (parameter 5752 Ä p. 290)
is configured to "Generator load".
The maximum generator load must be configured higher then the minimum
generator load for proper operation.
5763 IOP Min. gener‐ 2 0 to 100% If the generator load falls below the threshold configured here, the load-
ator load dependent start/stop function will stop a genset. If only a few gensets are
[30%] operating in a multi-genset application, the IOP Dynamic (param‐
eter 5757 Ä p. 295) will also be considered when stopping a genset.
Notes
This parameter is only effective if start stop mode (parameter 5752 Ä p. 290)
is configured to "Generator load".
The maximum generator load must be configured higher then the minimum
generator load for 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 con‐
tinuous 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 run‐
ning, the less the influence of this parameter. Also refer to the following
example.
Notes
This parameter is only effective if start stop mode (parameter 5752 Ä p. 290)
is configured to "Generator load".
n Low:
Load level before stopping: 23.75%
Resulting load level for remaining engine:
47.5% (25% of the difference between 70 and 40%)
n Moderate:
Load level before stopping: 27.5%
Resulting load level for remaining engine:
55% (50% of the difference between 70 and 40%)
n High:
Load level before stopping: 31.25%
Resulting load level for remaining engine:
62.5% (75% of the difference between 70 and 40%)
5764 IOP Add on 2 0 to 32000 s Load swings may exceed the threshold momentarily. In order to prevent the
delay engine from starting due to short-term load swings, a delay time may be con‐
[10 s] figured.
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 2 0 to 32000 s The command to start the next genset in case a genset exceeds rated load
delay at rated will be issued after the delay configured here has expired.
load [3 s]
Notes
This parameter becomes only effective in case a genset exceeds rated load
to achieve a faster start and overrides parameter 5764 Ä p. 296.
5766 IOP Add off 2 0 to 32000 s Load swings may fall below the threshold momentarily. In order to prevent the
delay engine from stopping due to short-term load swings, a delay time may be con‐
[60 s] figured.
The load must remain below the hysteresis setpoint without interruption for
the delay time, configured in seconds, prior to a 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.
5767 MOP Minimum 2 0 to 65000 kW For the mains interchange (import/export) real power control to function, a
load minimum generator power setpoint value is required to start the first genset.
[10 kW]
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 reason‐
able 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 Hyste‐ 2 0 to 65000 kW Start stop mode configured to "Reserve power":
resis
[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 hyste‐
resis 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 Ä p. 290).
Notes
This parameter is only effective if start stop mode (parameter 5752 Ä p. 290)
is configured to "Reserve power".
Notes
This parameter is only effective if start stop mode (parameter 5752 Ä p. 290)
is configured to "Reserve power".
12605 MOP Reserve 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the 'MOP
power 2 LogicsManager Reseve power 2' (parameter 5649 Ä p. 297) is used instead of the 'MOP
86.42 Reseve power' (parameter 5768 Ä p. 297).
[(0 & 1) & 1] Notes
= 11976 For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
5770 MOP Max. gen‐ 2 0 to 100% If the generator load exceeds the threshold configured here, the load-
erator load dependent start/stop function will start another genset.
[70%]
Notes
This parameter is only effective if start stop mode (parameter 5752 Ä p. 290)
is configured to "Generator load".
The maximum generator load must be configured higher then the minimum
generator load for proper operation.
5771 MOP Min. gen‐ 2 0 to 100% If the generator load falls below the threshold configured here, the load-
erator load dependent start/stop function will stop a genset.
[30%]
If only a few gensets are operating in a multi-genset application, the MOP
Dynamic (parameter 5758 Ä p. 298) will also be considered when stopping a
genset.
Notes
This parameter is only effective if start stop mode (parameter 5752 Ä p. 290)
is configured to "Generator load".
The maximum generator load must be configured higher then the minimum
generator load for 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 parameter 5754 Ä p. 291).
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 con‐
tinuous 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.
Notes
This parameter is only effective if start stop mode (parameter 5752 Ä p. 290)
is configured to "Generator load".
Refer to parameter 5757 Ä p. 295 for examples on stating and stopping a
genset depending on the dynamic setting.
5772 MOP Add on 2 0 to 32000 s Load swings may exceed the threshold momentarily. In order to prevent the
delay engine from starting due to short-term load swings, a delay time may be con‐
[20 s] figured.
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.
5773 MOP Add on 2 0 to 32000 s The command to start the next genset in case a genset exceeds rated load
delay at rated will be issued after the delay configured here has expired.
load [3 s]
This parameter becomes only effective in case a genset exceeds rated load
to achieve a faster start and overrides parameter 5772 Ä p. 299.
Notes
This parameter becomes only effective in case a genset exceeds rated load
to achieve a faster start and overrides parameter 5764 Ä p. 296.
5774 MOP Add off 2 0 to 32000 s Load swings may fall below the threshold momentarily. In order to prevent the
delay engine from stopping due to short-term load swings, a delay time may be con‐
[60 s] figured.
The load must remain below the hysteresis setpoint without interruption for
the delay time, configured in seconds, prior to a 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.
Prerequisites
– The emergency power function can only be
activated for synchronous generators with
parameter 2802 Ä p. 301.
– Emergency power is carried out in operating
mode AUTOMATIC regardless of the status of
the LogicsManager output 'Start request in
AUTO' (LogicsManager).
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.
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.
2800 Mains fail 2 0.00 to 99.99 To start the engine and to carry out an emergency operation the monitored
delay time mains must be failed continuously for the minimum period of time set with this
[3.00 s] parameter.
(Mains failure
start delay) Notes
This delay time starts only if the easYgen is in AUTOMATIC operating mode
and emergency power is activated.
3408 Emerg. start 2 [Yes]/No Emergency power operations may be configured with the failure of the MCB
with MCB in addition to a loss of power on the mains supply.
failure
Notes
An MCB breaker alarm is indicated if parameter "MCB monitoring" (param‐
eter 2620 Ä p. 384) is configured "On".
12200 Inhibit emer‐ 2 Determined by Once the conditions of the LogicsManager have been fulfilled the emergency
gency run LogicsManager power operation will be terminated or blocked.
86.11
(Inhibit emerg. Notes
run) [(0 & 1) & 1]
It is possible to interrupt an already activated emergency run.
= 10710
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
4101 Break emerg. 2 0 to 999 s The emergency power operations are overridden for the configured time
in critical mode when the critical mode starts in order to supply the complete generator power
[5 s] to the sprinkler pump.
(Override emer‐
gency opera‐
tions in critical
mode)
5800 Upper voltage 2 100 to 150% The maximum permissible positive deviation of the generator voltage from the
limit generator rated voltage (parameter 1766 Ä p. 412) is configured here.
[110%]
(Generator max‐ This value may be used as a voltage limit switch. The conditional state of this
imum operating (Hysteresis: 1%) switch may be used as a command variable for the LogicsManager (02.03).
voltage limit)
5801 Lower voltage 2 50 to 100% The maximum permissible negative deviation of the generator voltage from
limit the generator rated voltage (parameter 1766 Ä p. 412) is configured here.
[90%]
(Generator min‐ This value may be used as a voltage limit switch. The conditional state of this
imum operating (Hysteresis: 1%) switch may be used as a command variable for the LogicsManager (02.03).
voltage limit)
5802 Upper fre‐ 2 100.0 to 150.0% The maximum permissible positive deviation of the generator frequency from
quency limit the rated system frequency (parameter 1750 Ä p. 411) is configured here.
[105.0%]
(Generator max‐ This value may be used as a frequency limit switch. The conditional state of
imum operating (Hysteresis: this switch may be used as a command variable for the LogicsManager
frequency limit) 0.05%) (02.04).
5803 Lower fre‐ 2 50.0 to 100.0% The maximum permissible negative deviation of the generator frequency from
quency limit the rated system frequency (parameter 1750 Ä p. 411) is configured here.
[95.0%]
(Generator min‐ This value may be used as a frequency limit switch. The conditional state of
imum operating (Hysteresis: this switch may be used as a command variable for the LogicsManager
frequency limit) 0.05%) (02.04).
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 oper‐
ating 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.
5122 Delay 2 0.02 to 99.99 s If one of the monitored values exceeds the threshold value for the delay time
configured here, an alarm will be issued.
[10.00 s]
5119 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
5120 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
1770 Generator 2 The unit can either monitor the phase-neutral (wye) voltages or the phase-
voltage moni‐ phase (delta) voltages.
toring
If the controller is used in a compensated or isolated network, voltage protec‐
tion monitoring should be configured as phase-neutral to prevent earth-faults
resulting in tripping of the voltage protections.
[Phase - The phase-phase voltage will be monitored and all subsequent parameters
phase] concerning voltage monitoring "generator" are referred to this value (VL-L).
Phase - neutral The phase-neutral voltage will be monitored and all subsequent parameters
concerning voltage monitoring "generator" are referred to this value (VL-N).
Notes
WARNING: This parameter defines how the protective functions operate.
2000 Monitoring 2 [On] Overvoltage monitoring is carried out according to the following parameters.
Monitoring is performed at two levels. Both values may be configured inde‐
2006 pendent from each other (prerequisite: Level 1 limit < limit 2).
2004 Limit 2 50.0 to 150.0% The percentage values that are to be monitored for each threshold limit are
defined here.
2010 2004: [108.0%]
If this value is reached or exceeded for at least the delay time without inter‐
2010: [112.0%] ruption, the action specified by the alarm class is initiated.
(Hysteresis:
Notes
0.7%)
This value refers to the System rated frequency (parameter 1766 Ä p. 412).
(Reset Delay:
80 ms)
2005 Delay 2 0.02 to 99.99 s If the monitored generator voltage value exceeds the threshold value for the
delay time configured here, an alarm will be issued.
2011 2005: [5.00 s]
Notes
2011: [0.30 s]
If the monitored generator voltage falls below the threshold (minus the hyste‐
resis) before the delay expires the time will be reset.
2001 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2007 Control
Notes
2001: [B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2007: [F] on page 888
2002 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2008
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2003 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
2009 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2050 Monitoring 2 [On] Undervoltage monitoring is carried out according to the following parameters.
Monitoring is performed at two levels. Both values may be configured inde‐
2056 pendent from each other (prerequisite: Level 1 limit < limit 2).
2054 Limit 2 50.0 to 150.0% The percentage values that are to be monitored for each threshold limit are
defined here.
2060 2054: [92.0%]
If this value is reached or exceeded for at least the delay time without inter‐
2060: [88.0%] ruption, the action specified by the alarm class is initiated.
(Hysteresis:
Notes
0.7%)
This value refers to the System rated frequency (parameter 1766 Ä p. 412).
(Reset Delay:
80 ms)
2055 Delay 2 0.02 to 99.99 s If the monitored generator voltage value falls below the threshold value for the
delay time configured here, an alarm will be issued.
2061 2055: [5.00 s]
Notes
2061: [0.30 s]
If the monitored generator voltage exceeds the threshold (plus the hysteresis)
before the delay expires the time will be reset.
2051 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2057 Control
Notes
2051: [B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2057: [F] on page 888
2052 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2058
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2053 Enabled 2 Always Monitoring for this fault condition is continuously enabled.
2059
[87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon] bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
3900 Monitoring 2 [On] Voltage asymmetry monitoring is carried out according to the following
parameters.
3903 Limit 2 0.5 to 15.0% The percentage values that are to be monitored for each threshold limit are
defined here.
[10.0%]
If this value is reached or exceeded for at least the delay time without inter‐
(Hysteresis: ruption, the action specified by the alarm class is initiated.
0.5%)
Notes
(Reset Delay:
80 ms) This value refers to the Generator rated voltage (parameter 1766 Ä p. 412).
3904 Delay 2 0.02 to 99.99 s If the monitored generator voltage asymmetry exceeds the threshold value for
the delay time configured here, an alarm will be issued.
[5.00 s]
Notes
If the monitored generator voltage asymmetry falls below the threshold (minus
the hysteresis) before the delay expires the time will be reset
3901 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
Notes
[F]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3902 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3905 Enabled 2 Always Monitoring for this fault condition is continuously enabled.
[87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon] bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
The plausibility monitoring offers one setting for all three measure‐
ment systems. The Monitor is placed under: “Parameter
è Configure: Monitoring è Miscellaneous: Other monitoring” .The
alarm indications are called Gen. .../Busbar .../Mains AC wiring
(see Ä Chapter 9.5.3 “Status Messages” on page 889).
1965 Delay 2 00.2 to 99.99 s If the monitored value undershoots the threshold value for the delay time con‐
figured here, an alarm will be issued.
[00.30]
1966 Alarm class 2 Class A, B, C, Each limit may be assigned an independent alarm class that specifies what
D, E, F, Control action should be taken when the limit is surpassed.
[Class B ]
1967 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
1968 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
1904 Limit 2 50.0 to 140.0% The percentage values that are to be monitored for each threshold limit are
defined here.
1910 1904: [110.0%]
If this value is reached or exceeded for at least the delay time without inter‐
1910: [115.0%] ruption, the action specified by the alarm class is initiated.
(Hysteresis:
Notes
0.05 Hz)
This value refers to the System rated frequency (parameter 1750 Ä p. 411).
(Reset Delay:
80 ms)
1905 Delay 2 0.02 to 99.99 s If the monitored generator frequency value exceeds the threshold value for
the delay time configured here, an alarm will be issued.
1911 1905: [1.50 s]
1911: [0.30 s]
Notes
If the monitored generator frequency falls below the threshold (minus the hys‐
teresis) before the delay expires the time will be reset.
1901 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
1907 Control
1901: [B]
1907: [F]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
1902 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
1908
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
1903 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
1909 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
1954 Limit 2 50.0 to 130.0% The percentage values that are to be monitored for each threshold limit are
defined here.
1960 1954: [90.0%]
If this value is reached or lower for at least the delay time without interruption,
1960: [84.0%] the action specified by the alarm class is initiated.
(Hysteresis:
Notes
0.05 Hz)
This value refers to the System rated frequency (parameter 1750 Ä p. 411).
(Reset Delay:
80 ms)
1955 Delay 2 0.02 to 99.99 s If the monitored generator frequency value falls below the threshold value for
the delay time configured here, an alarm will be issued.
1961 1955: [5.00 s]
1961: [0.30 s]
Notes
If the monitored generator frequency falls below the threshold (plus the hyste‐
resis) before the delay expires the time will be reset.
1951 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
1957 Control
1951: [B]
1957: [F]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
1952 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
1958
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
1953 Enabled 2 Always Monitoring for this fault condition is continuously enabled.
1959 [ 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon] bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2200 Monitoring 2 [On] Overcurrent monitoring is carried out according to the following parameters.
Monitoring is performed at three levels. All three values may be configured
2206 independent from each other (prerequisite: Level 1 < Level 2 < Level 3).
2212
Off Monitoring is disabled for Level 1 limit, Level 2 limit, and/or Level 3 limit.
2204 Limit 2 50.0 to 300.0% The percentage values that are to be monitored for each threshold limit are
defined here.
2210 2204: [110.0%]
If this value is reached or exceeded for at least the delay time without inter‐
2216 2210: [150.0%] ruption, the action specified by the alarm class is initiated.
2216: [250.0%]
Notes
(Hysteresis: 1%)
This value refers to the System rated frequency (parameter 1754 Ä p. 413).
(Reset Delay: 1
s)
2205 Delay 2 0.02 to 99.99 s If the monitored generator current exceeds the threshold value for the delay
time configured here, an alarm will be issued.
2211 2205: [30.00 s]
Notes
2217 2211: [1.00 s]
If the monitored generator current falls below the threshold (minus the hyste‐
2217: [0.40 s]
resis) before the delay expires the time will be reset.
2224 Voltage 2 Yes The control provides voltage restrained overcurrent relay according to ANSI
restraint moni‐ 51 V individually for each generator current monitoring function.
2225 toring
For details refer to Ä Chapter 4.5.1.4.3 “Generator Voltage Restrained Over‐
2226 current Monitoring - ANSI #51” on page 315.
[No] Voltage restrained monitoring is disabled.
2201 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2207 Control
Notes
2213 2201: [E]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2207: [F] on page 888
2213: [F]
2202 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2208
2214
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2203 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
2209 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. This is determined through the LogicsManager equation "Release
2215
engine monitoring".
For xx = 1 to 32: The monitoring is executed, if the LogicsManager "Flag {xx}" is TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
Characteristics
4030 Monitoring 2 [On] Overcurrent monitoring is carried out according to the following parameters.
4035 Inverse time 2 0.01 to 1.99 s Time constant Tp used to calculate the characteristics.
overcurrent
Tp= [0.06 s]
4036 Inverse time 2 10.0 to 300.0% Current constant IP used to calculate the characteristics.
overcurr. IP =
[100.0%]
4037 Inv time over‐ 2 100.0 to 300.0% Lower tripping value for inverse time-overcurrent protection. If the monitored
curr. Istart = current is less than Istart, the inverse time-overcurrent protection does not trip.
[115.0%] If Istart is less than IP, IP is used as the lower tripping value.
(Hysteresis: 1%)
(Reset Delay: 1
s)
2227 Voltage 2 Yes The control provides voltage restrained inverse time overcurrent monitoring.
restraint moni‐
toring For general information about voltage restrained monitoring refer to
Ä Chapter 4.5.1.4.3 “Generator Voltage Restrained Overcurrent Monitoring -
ANSI #51” on page 315.
[No] Voltage restrained monitoring is disabled.
4031 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
4033 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
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%]
2232 Min. factor limit 2 5.0 ... 100.0% Minimum factor limit for current limitation reduction
overcurrent
[25.0%]
2300 Monitoring 2 [On] Overload monitoring is carried out according to the following parameters.
Monitoring is performed at two levels.
2306
Both values may be configured independent from each other (prerequisite:
Level 1 limit < Level 2 limit).
2304 Limit 2 50.0 to 300.00% The percentage values that are to be monitored for each threshold limit are
defined here.
2310 2304: [110.0%]
If this value is reached or exceeded for at least the delay time without inter‐
2310: [120.0%] ruption, the action specified by the alarm class is initiated.
(Hysteresis: 1%)
Notes
(Reset Delay:
This value refers to the Generator rated active power (param‐
80 ms)
eter 1752 Ä p. 412).
2305 Delay 2 0.02 to 99.99 s If the monitored generator load exceeds the threshold value for the delay time
configured here, an alarm will be issued.
2311 2305: [11.00 s]
Notes
2311: [0.10 s]
If the monitored generator load falls below the threshold (minus the hyste‐
resis) before the delay expires the time will be reset.
2301 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2307 Control
Notes
2301: [B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2307: [D] on page 888
2302 Self acknowl‐ 2 Yes The control automatically clears the alarm if the fault condition is no longer
edge detected.
2308
[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 appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2303 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
2309 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2350 Monitoring 2 [On] Overload monitoring is carried out according to the following parameters.
Monitoring is performed at two levels.
2356
Both values may be configured independent from each other (prerequisite:
Level 1 limit < Level 2 limit).
2354 Limit 2 50.0 to 300.00% The percentage values that are to be monitored for each threshold limit are
defined here.
2360 2354: [105.0%]
If this value is reached or exceeded for at least the delay time without inter‐
2360: [110.0%] ruption, the action specified by the alarm class is initiated.
(Hysteresis: 1%)
Notes
(Reset Delay:
This value refers to the Generator rated active power (param‐
80 ms)
eter 1752 Ä p. 412).
2355 Delay 2 0.02 to 99.99 s If the monitored generator load exceeds the threshold value for the delay time
configured here, an alarm will be issued.
2361 2355: [5.00 s]
Notes
2361: [0.10 s]
If the monitored generator load falls below the threshold (minus the hyste‐
resis) before the delay expires the time will be reset.
2351 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2357 Control
Notes
2351: [B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2357: [D] on page 888
2352 Self acknowl‐ 2 Yes The control automatically clears the alarm if the fault condition is no longer
edge detected.
2358
[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 appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2353 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
2359 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
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 config‐
ured as follows:
n Level 1 limit = Positive and Level 2 limit = Positive
(whereas Level 1 limit > Level 2 limit > 0 %)
n Both limits are configured for reduced power monitoring.
Example n Rated power is 100 kW, Level 1 limit = 5 % > Level 2 limit =
3%
n Tripping if real power falls below 5 kW (Level 1 limit) or 3 kW
(Level 2 limit)
Example n Rated power is 100 kW, Level 1 limit = -3 % > Level 2 limit =
-5 %
n Tripping if real power falls below -3 kW (Level 1 limit)
or -5 kW (Level 2 limit)
Example n Rated power is 100 kW, Level 1 limit = 3 % > Level 2 limit =
-5 %
n Tripping if real power falls below 3 kW (Level 1 limit)
or -5 kW (Level 2 limit)
2250 Monitoring 2 [On] Reverse/reduced power monitoring is carried out according to the following
parameters.
2256
Both values may be configured independent from each other.
2254 Limit 2 -99.9 to 99.9% The percentage values that are to be monitored for each threshold limit are
defined here.
2260 2254: [-3.0%]
If this value is reached or fallen below for at least the delay time without inter‐
2260: [-5.0%] ruption, the action specified by the alarm class is initiated.
(Hysteresis: 1%)
2255 Delay 2 0.02 to 99.99 s If the monitored generator power falls below the threshold value for the delay
time configured here, an alarm will be issued.
2261 2255: [5.00 s]
Notes
2261: [5.00 s]
If the monitored generator power exceeds or falls below the threshold (plus/
minus the hysteresis) again before the delay expires the time will be reset.
2251 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2257 Control
Notes
2251: [B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2257: [F] on page 888
2252 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2258
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2253 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
2259 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
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
2400 Monitoring 2 [On] Unbalanced load monitoring is carried out according to the following parame‐
ters. Monitoring is performed at two levels.
2406
Both values may be configured independent from each other (condition:
Level 1 < Level 2).
Off No monitoring is carried out for either Level 1 limit or Level 2 limit.
2404 Limit 2 0.0 to 100.0% The percentage values that are to be monitored for each threshold limit are
defined here.
2410 2404: [10.0%]
If this value is reached or exceeded for at least the delay time without inter‐
2410: [15.0%] ruption, the action specified by the alarm class is initiated.
(Hysteresis:
0.5%)
2405 Delay 2 0.02 to 99.99 s If the monitored current exceeds the threshold value for the delay time config‐
ured here, an alarm will be issued.
2411 2405: [5.00 s]
Notes
2411: [1.00 s]
If the monitored current falls below the threshold (minus the hysteresis)
before the delay expires the time will be reset.
2401 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2407 Control
Notes
2401: [B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2407: [E] on page 888
2402 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2408
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2403 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
2409 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
5100 Monitoring 2 On Load share monitoring is carried out according to the following parameters.
4841 Limit 2 1.0 to 100.0% The percentage value that is to be monitored for the threshold limit is defined
here.
[30.0%]
If this value is reached or exceeded for at least the delay time without inter‐
ruption, the action specified by the alarm class is initiated.
Notes
This value is rated to the absolute difference between generator rated power
(parameter 1752 Ä p. 412) and the percent average power of the other
devices. The generator rated power is modified by the derating factor if
derating is activated.
5104 Delay 2 1.0 to 999.9 s If the monitored generator power value exceeds the threshold value for the
delay time configured here, an alarm will be issued.
[10.0 s]
Notes
If the monitored generator power falls below the threshold (minus the hyste‐
resis) before the delay expires the time will be reset.
5101 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
5102 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
5103 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
5106 Monitoring 2 On Load share monitoring is carried out according to the following parameters.
4842 Limit 2 1.0 to 100.0% The percentage value that is to be monitored for the threshold limit is defined
here.
[30.0%]
If this value is reached or exceeded for at least the delay time without inter‐
ruption, the action specified by the alarm class is initiated.
Notes
This value is rated to the absolute difference between generator rated reac‐
tive power (parameter 1758 Ä p. 413) 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.
5110 Delay 2 1.0 to 999.9 s If the monitored generator power value exceeds the threshold value for the
delay time configured here, an alarm will be issued.
[10.0 s]
Notes
If the monitored generator power falls below the threshold (minus the hyste‐
resis) before the delay expires the time will be reset.
5107 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
5108 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
5109 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2920 Monitoring 2 [On] Monitoring of the generator active power mismatch is carried out according to
the following parameters.
2925 Limit 2 1.0 to 30.0% If the difference between the measured generator power and the power set‐
point exceeds this value for at least the delay time (parameter 2923 Ä p. 325)
[5.0%] without interruption, the action specified by the alarm class is initiated.
Notes
This value refers to the generator rated active power (parameter
1752 Ä p. 412).
2923 Delay 2 3 to 9999 s If the monitored active power mismatch exceeds the threshold value config‐
ured in parameter 2925 Ä p. 325 for the delay time configured here, an alarm
[30 s] will be issued.
Notes
If the monitored active power mismatch falls below the threshold (minus the
hysteresis) before the delay expires the time will be reset.
2921 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
2922 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3120 Monitoring 2 [On] Monitoring of engine unloading is carried out according to the following
parameters.
3125 Unload limit 2 0.5 to 99.9% If the monitored generator power falls below this value, a "GCB open" com‐
mand will be issued.
[3.0%]
Notes
This value refers to the generator rated active power (parameter
1752 Ä p. 412).
3123 Delay 2 3 to 999 s If the monitored generator power does not fall below the limit configured in
parameter 3125 Ä p. 326 before the time configured here expires, a "GCB
[60 s] open" command will be issued together with an alarm.
3121 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3122 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2325 Monitoring 2 [On] Generator lagging power factor monitoring is carried out according to the fol‐
lowing parameters. Monitoring is performed at two levels. Both values may be
2331 configured independent from each other.
2329 Limit 2 -0.999 to 1.000 The values that are to be monitored for each threshold limit are defined here.
2335 2329 [+ 0.900] Notes
2335: [+ 0.700] If the power factor becomes more lagging (i.e. inductive, Fig. 171) than a lag‐
ging PF value (positive) or a leading PF value (negative) for at least the delay
(Hysteresis:
time (parameters 2330 Ä p. 327 or 2336 Ä p. 327) without interruption, the
0.02%)
action specified by the alarm class is initiated.
(Reset Delay:
80 ms)
2330 Delay 2 0.02 to 99.99 s If the monitored generator power factor is more lagging than the configured
limit for the delay time configured here, an alarm will be issued.
2336 2330: [30.00 s]
2326 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2332 Control
Notes
2326: [B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2332: [B] on page 888
2327 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2333
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2328 Enabled 2 Always Monitoring for this fault condition is continuously enabled.
2334 [ 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon] bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2375 Monitoring 2 [On] Generator leading power factor monitoring is carried out according to the fol‐
lowing parameters. Monitoring is performed at two levels. Both values may be
2381 configured independent from each other.
2379 Limit 2 -0.999 to 1.000 The values that are to be monitored for each threshold limit are defined here.
2385 2379: [- 0.900] Notes
2385: [- 0.700] If the power factor becomes more leading (i.e. capacitive, Fig. 172) than a
leading PF value (negative) or a lagging PF value (positive) for at least the
(Hysteresis:
delay time (parameters 2380 Ä p. 329 or 2386 Ä p. 329) without interruption,
0.02%)
the action specified by the alarm class is initiated.
(Reset Delay:
80 ms)
2380 Delay 2 0.02 to 99.99 s If the monitored generator power factor is more leading than the configured
limit for the delay time configured here, an alarm will be issued.
2386 2380: [30.00 s]
Notes
2386: [10.00 s]
If the monitored generator power factor returns within the limit before the
delay expires the time will be reset.
2376 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2382 Control
Notes
2376: [B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2382: [B] on page 888
2377 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2383
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2378 Enabled 2 Always Monitoring for this fault condition is continuously enabled.
2384 [ 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon] bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
4.5.1.6.2 Miscellaneous
Generator Ground Fault (Level 1 & 2)
General notes
The generator ground fault is determined differ‐
ently depending on the following configuration
options:
– Mains current input is configured for mains cur‐
rent
(calculated ground fault)
– Mains current input is configured for ground
current
(measured ground fault)
Refer to parameter 1854 Ä p. 411.
Calculated ground fault The current produced by the generator is monitored depending on
how parameter "Generator current measuring" (parameter
1850 Ä p. 414) is configured. The measured three conductor cur‐
rents 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. 173: Generator ground fault - The ground fault protection zone is determined by
schematic the location where the generator current trans‐
former are physically installed.
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 per‐
centage threshold refers to the generator rated current (param‐
eter 1754 Ä p. 413). Due to unavoidable load asymmetries, the
minimum value for this parameter should be 10% or greater.
Calculation
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 "Ground current transformer" (parameter
1810 Ä p. 412).
3250 Monitoring 2 On Ground current monitoring is carried out according to the following parame‐
ters. Monitoring is performed at two levels. Both values may be configured
3256 independent from each other (prerequisite: Level 1 < Level 2).
3254 Limit 2 0 to 300% The percentage values that are to be monitored for each threshold limit are
defined here.
3260 3254: [10%]
If this value is reached or exceeded for at least the delay time without inter‐
3260: [30%] ruption, the action specified by the alarm class is initiated.
(Hysteresis: 1%)
Notes
(Reset Delay:
This value refers to the Generator rated current of the generator (param‐
80 ms)
eter 1754 Ä p. 413), if the ground current is calculated from the generator
current values.
It refers to the parameter "Ground current transformer" (parame‐
terr 1810 Ä p. 412), if the ground current is measured directly.
The ground fault threshold shall not exceed the mains/ground current meas‐
uring range (approx. 1.5 × Irated; Ä Chapter 8.1 “Technical Data”
on page 595).
3255 Delay 2 0.02 to 99.99 s If the monitored ground fault exceeds the threshold value for the delay time
configured here, an alarm will be issued.
3261 3255: [0.20 s]
Notes
3261: [0.10 s]
If the monitored ground fault falls below the threshold (minus the hysteresis)
before the delay expires the time will be reset.
3251 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
3257 Control
Notes
3251: [B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
3257: [F] on page 888
3252 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
3258
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3253 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
3259 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
3950 Monitoring 2 [On] Phase rotation monitoring is carried out according to the following parame‐
ters.
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 2 [CW] The three-phase measured generator voltage is rotating CW (clock-wise; that
phase rotation 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).
3951 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[F]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3952 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3953 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2100 Monitoring 2 [On] Overspeed monitoring is carried out according to the following parameters.
Monitoring is performed at two levels. Both values may be configured inde‐
2106 pendent from each other (prerequisite: Level 1 > Level 2).
2104 Limit 2 0 to 9,999 rpm The revolutions per minute (rpm) values that are to be monitored for each
threshold limit are defined here.
2110 2104: [1,850.0
rpm] If this value is reached or exceeded for at least the delay time without inter‐
ruption, the action specified by the alarm class is initiated.
2110: [1,900.0
rpm]
(Hysteresis: 50
rpm)
(Reset Delay: 1
s)
2105 Delay 2 0.02 to 99.99 s If the monitored engine speed exceeds the threshold value for the delay time
configured here, an alarm will be issued.
2111 2105: [1.00 s]
Notes
2111: [0.10 s]
If the monitored engine speed falls below the threshold (minus the hysteresis)
before the delay expires the time will be reset.
2101 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2107 Control
Notes
2101: [B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2107: [F] on page 888
2102 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2108
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2103 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
2109
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2150 Monitoring 2 [On] Underspeed monitoring is carried out according to the following parameters.
Monitoring is performed at two levels. Both values may be configured inde‐
2156 pendent from each other (prerequisite: Level 1 > Level 2).
2154 Limit 2 0 to 9999 rpm The percentage values that are to be monitored for each threshold limit are
defined here.
2160 2154: [1,300.0
rpm] If this value is reached or exceeded for at least the delay time without inter‐
ruption, the action specified by the alarm class is initiated.
2160: [1,250.0
rpm]
(Hysteresis: 50
rpm)
(Reset Delay: 1
s)
2155 Delay 2 0.02 to 99.99 s If the monitored engine speed falls below the threshold value for the delay
time configured here, an alarm will be issued.
2161 2155: [1.00 s]
Notes
2161: [0.10 s]
If the monitored engine speed exceeds the threshold (plus the hysteresis)
again before the delay expires the time will be reset.
2151 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2157 Control
Notes
2151: [B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2157: [F] on page 888
2152 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2158
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2153 Enabled 2 Always Monitoring for this fault condition is continuously enabled.
2159 [ 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon] bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2454 Speed/ 2 1.5 to 8.5 Hz The frequency mismatch that is to be monitored is defined here.
frequency mis‐
match limit [5.0 Hz] If the monitored frequency mismatch reaches or exceeds this value for at
least the delay time without interruption, the action specified by the alarm
class is initiated.
Notes
The LogicsManager is monitored with respect to his status.
2455 Delay 2 1 to 99 s If the monitored frequency mismatch exceeds the threshold value for the
delay time configured here, an alarm will be issued.
[1.00 s]
Notes
If the monitored frequency mismatch falls below the threshold (minus the hys‐
teresis) before the delay expires the time will be reset.
2453 Activation fre‐ 2 15 to 85 Hz The speed/frequency mismatch monitoring is enabled at this generator fre‐
quency quency.
[20 Hz]
2451 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[E]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
2452 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2458 Enabled 2 Always Monitoring for this fault condition is continuously enabled.
[ 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon] bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
3303 Monitoring 2 [On] Monitoring of the start sequence is carried out according to the following
parameters.
3304 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[F]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3305 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2500 Monitoring 2 [On] Monitoring of the stop sequence is carried out according to the following
parameters.
2503 Maximum stop 2 3 to 999 s The maximum permissible time between the output of a stop command and
delay the reply that the engine is stopped successfully is defined here.
[30 s]
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 action specified by the alarm class is initiated.
2501 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[F]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
2502 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2650 Monitoring 2 [On] Monitoring of an unintended stop is carried out according to the following
parameters.
2651 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[F]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
2657 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
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 below a fixed
limit for the time defined here, an alarm will be issued.
[10 s]
If the voltage returns within the limit before the delay time expires, the delay
time will be reset.
4051 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F action should be taken when the limit is surpassed.
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
4052 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
4053 Enabled 2 Always Monitoring for this fault condition is continuously enabled.
[ 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon] bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
Monitoring Function
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 allo‐
cated 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 equa‐
tion. Each monitoring level (level 1 or 2) can be separately
released by a configurable generator power.
Alarm System / Eventlogger The alarm system provides three alarm messages:
n Cylinder temperature level 1
n Cylinder temperature level 2
n Wire break
Alarm Screen
n The square is dotted, if the according cylinder is not configured
n The square contains an arrow-up, if the limit is exceeded
n The square contains an arrow-down, if limit is below target
n The square contains a '!' exclamation point sign, if the sensor is
missing (wire break) or error was detected
n If an alarm occurs and the monitor is still active, the new alarm
is linked by logic 'OR' to the others
n The monitor ignores values of cylinders with wire break or
sensor defect
n The alarm trip displaying is removed, if the alarm of the
according level was successful acknowledged
Fig. 177: Cylinder temperature screen n 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
ID Parameter CL Setting range Description
[Default]
8876 Monitoring at 2 [Off] The monitoring is deactivated. The alarm screen is not displayed.
8877 Source cyl‐ 2 Ext.AIN The temperatures are taken from external temperature module (Phoenix, AI1
inder tempera‐ - AI16, 16 ports).
ture
[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 con‐
nected.
Level 1
ID Parameter CL Setting range Description
[Default]
8878 Minimum gen‐ 2 000.0 ... 150.0% When the generator power exceeds this value the level 1 monitoring is acti‐
erator power vated.
[30.0%]
Respectively the level 1 is deactivated, if the power level is undershoot.
[100° C]
8880 Delay 2 0000 ... 9999 s Time between *** exceeds limits and *** is activated.
[60 s]
8881 Alarm class 2 Class Each limit may be assigned to an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B] For additional information refer to. Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
8882 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
Level 2
ID Parameter CL Setting range Description
[Default]
8883 Minimum gen‐ 2 000.0 ... 150.0% When the generator power exceeds this value the level 2 monitoring is acti‐
erator power vated.
[30.0%]
Respectively the level 2 is deactivated, if the power level is undershoot.
[150° C]
8886 Alarm class 2 Class Each limit may be assigned to an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B] For additional information refer to. Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
8885 Delay 2 0000 ... 9999 s Time between *** exceeds limits and *** is activated.
[60 s]
8887 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
8890 Delay 2 0000 ... 9999 s Time between *** exceeds limits and *** is activated.
[2 s]
8888 Alarm class 2 Class Each limit may be assigned to an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B] For additional information refer to. Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
8889 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
Temperature X Bank
ID Parameter CL Setting range Description
[Default]
8856 Bank selct cyl‐ 2 [Off] The temperature does not exist.
inder {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:
n 00 - OK
n 01 - Overrun
n 10 - Underrun
n 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:
2 2..3 2 2..3
8 14..15 8 14..15
10 2..3 10 2..3
16 14..15 16 14..15
18 2..3 18 2..3
19 4..5 19 4..5
20 6..7 20 6..7
4.5.3 Mains
4.5.3.1 General Mains Monitoring
ID Parameter CL Setting range Description
[Default]
1771 Mains voltage 2 The unit can either monitor the wye voltages (phase-neutral) or the delta vol‐
monitoring tages (phase-phase). The monitoring of the wye voltage is above all neces‐
sary to avoid earth-faults in a compensated or isolated network resulting in
the tripping of the voltage protection.
[Phase - The phase-phase voltage will be monitored and all subsequent parameters
phase] concerning voltage monitoring "mains" are referred to this value (VL-L).
Phase - neutral The phase-neutral voltage will be monitored and all subsequent parameters
concerning voltage monitoring "mains" are referred to this value (VL-N).
All The phase-phase and phase-neutral voltage will be monitored and all subse‐
quent parameters concerning voltage monitoring "mains" are referred to this
value (VL-L & VL-N).
This setting is only effective if "Mains voltage measuring" (parameter
1853 Ä p. 416) is configured to "3Ph 4W".
Notes
WARNING: This parameter influences the protective functions.
Please be aware that if "Mains voltage monitoring" (parameter
1771 Ä p. 346) is configured to "All" and the function Ä Chapter 4.5.3.9
“Mains Voltage Increase” on page 361 is used, that this function only monitors
"Phase - neutral".
2801 Mains settling 2 0 to 9999 s To end the emergency operation, the monitored mains must be within the
time configured operating parameters without interruption for the minimum period
[20 s] of time set with this parameter without interruption.
This parameter permits delaying the switching of the load from the generator
to the mains.
The display indicates "Mains settling" during this time.
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).
5810 Upper voltage 2 100 to 150% The maximum permissible positive deviation of the mains voltage from the
limit mains rated voltage (parameter 1768 Ä p. 415) is configured here.
[110%]
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.09).
5814 Hysteresis 2 0 to 50% If the mains voltage has exceeded the limit configured in param‐
upper voltage eter 5810 Ä p. 348, the voltage must fall below the limit and the value config‐
limit [2%] ured here, to be considered as being within the operating limits again.
5811 Lower voltage 2 50 to 100% The maximum permissible negative deviation of the mains voltage from the
limit mains rated voltage (parameter 1768 Ä p. 415) is configured here.
[90%]
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.09).
5815 Hysteresis 2 0 to 50% If the mains voltage has fallen below the limit configured in param‐
lower voltage eter 5811 Ä p. 348, the voltage must exceed the limit and the value config‐
limit [2%] ured here, to be considered as being within the operating limits again.
5812 Upper fre‐ 2 66.7¹ to 150.0% The maximum permissible positive deviation of the mains frequency from the
quency limit rated system frequency (parameter 1750 Ä p. 411) is configured here.
[110.0%]
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 %.
5816 Hysteresis 2 0 to 50.0% If the mains frequency has exceeded the limit configured in param‐
upper fre‐ eter 5812 Ä p. 348, the frequency must fall below the limit and the value con‐
quency limit [0.5%] figured here, to be considered as being within the operating limits again.
5813 Lower fre‐ 2 66.7¹ to 100.0% The maximum permissible negative deviation of the mains frequency from the
quency limit rated system frequency (parameter 1750 Ä p. 411) is configured here. This
[90.0%] 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 2 0 to 50.0% If the mains frequency has exceeded the limit configured in param‐
lower fre‐ eter 5813 Ä p. 348, the frequency must raise above the limit and the value
quency limit [0.5%] configured here, to be considered as being within the operating limits again.
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 Ä p. 350).
12922 Ext. mns. 2 Determined by The unit may be configured to decouple from the mains when commanded by
decoupl. LogicsManager an external device.
86.27
(External mains Once the conditions of the LogicsManager have been fulfilled, an external
decoupling) [(0 & 1) & 1] mains failure is issued.
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
12942 Enable mains 2 Determined by Once the conditions of the LogicsManager have been fulfilled, the mains
decoupl. LogicsManager decoupling function is enabled.
87.31
(Enable mains
decoupling) [(02.02 & 1) &
1]
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
3110 Mains decou‐ 2 Off Mains decoupling monitoring is disabled.
pling
[GCB] Mains decoupling is carried out according to the following 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 according to the following parameters. If one
of the subordinate monitoring functions is triggered, the GCB will be opened.
If the reply "GCB open" is not present within the delay configured in param‐
eter 3113 Ä p. 350, the MCB will be opened as well.
MCB Mains decoupling is carried out according to the following parameters. If one
of the subordinate monitoring functions is triggered, the MCB will be opened.
MCB->GCB Mains decoupling is carried out according to the following parameters. If one
of the subordinate monitoring functions is triggered, the MCB will be opened.
If the reply "MCB open" is not present within the delay configured in param‐
eter 3113 Ä p. 350, the GCB will be opened as well.
GCB/MCB by Mains decoupling is carried out. If one of the subordinate monitoring functions
LM is triggered, a breaker will be opened, which is determined by the LogicsMan‐
ager equation "15160 Ä p. 350/Ä p. 853 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 decou‐ 2 Determined by FALSE: If the decoupling is triggered, the GCB will be opened.
pling MCB LogicsManager
87.73 TRUE: If the decoupling is triggered, the MCB will be opened.
[(0 & 1) & 1] Only available in Mains decoupling mode "GCB/MCB by LM".
3113 Mains decou‐ 2 0.2 to 99.9 s If the open signal from the respective circuit breaker cannot be detected
pling feedback within the time configured here, the mains decoupling function performs the
delay [0.4 s] action as configured in parameter 3110 Ä p. 349.
3111 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
3112 Self acknowl‐ 2 Yes The control automatically clears the alarm if the fault condition is no longer
edge 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 appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
8845 Mns. decou‐ 2 The mains overvoltage 1 alarm can be linked to the mains decoupling func‐
pling by over‐ tion, if required.
volt. 1
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 Ä p. 348
to 5817 Ä p. 348) within the monitoring limits.
8844 Mns. decou‐ 2 The mains undervoltage 1 alarm can be linked to the mains decoupling func‐
pling by under‐ tion, if required.
volt. 1
On The mains undervoltage 1 trip is linked to the mains decoupling function with
all its consequences.
[Off] The mains undervoltage 1 trip is ignored in the mains decoupling function.
Notes
It is recommended to configure the operating limits (parameter 5810 Ä p. 348
to 5817 Ä p. 348) within the monitoring limits.
3296 Mains decou‐ 2 On The QV monitoring function is linked to the mains decoupling function with all
pling by QV its consequences and is assigned to "Delay step 1" (parameter
3283 Ä p. 369).
1733 Test 2 On Activates a test mode which allows a comfortable mains decoupling test.
Notes
When the test mode is activated a mains decoupling according to the para‐
metrization 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 Ä p. 350) 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).
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
Ä Chapter 4.4.4.3.5 “Load-Share Interface”
on page 241.
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. 178).
3297 Monitoring 2 [Off] The diagnostic function is disabled, no related monitoring is executed.
CAN #1, If the diagnostic function is enabled, the related messages can be received
Ethernet via CAN 1 or Ethernet.
Notes
The following alarms can be triggered:
3298 Monitoring 2 Single The diagnostic function is related to one partner unit.
mode
3299 Device number 2 [01] The device ID of the expected partner unit. This configuration is only valid, if
partner the mode 'single' is enabled.
01 to 64
1828 Voltage differ‐ 2 [4.0%] This is the voltage measurement tolerance for all participating 4105 partners
ence relating to the mains rated voltage measurement (refer to ID1768 Ä p. 415).
2.0 to 9.9% This is a part within the 4105 diagnostic.
1836 Frequency dif‐ 2 [1.0%] This is the frequency measurement tolerance for all participating 4105 part‐
ference ners relating to the system rated frequency measurement. (refer to
0.5 to 9.9% ID1750 Ä p. 411). This is a part within the 4105 diagnostic.
5125 Alarm class 2 [C] The alarm class specifies what action should be taken in case of missing
communication with devices(s) being member(s) of the AR-–4105 system.
A to F, control
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
5126 Self acknowl‐ 2 Yes The control automatically clears the alarm if the fault condition is no longer
edge detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
Monitoring Parameter Alignment The following parameters are compared for monitoring its align‐
VDE AR-–4105 ment:
2860 Limit
2861 Delay
2910 Limit
2911 Delay
2960 Limit
2961 Delay
3010 Limit
3011 Delay
8807 Limit
5131 Alarm class 2 [C] The alarm class specifies what action should be taken if the parameter align‐
ment between the communication devices(s) of the AR-–4105 system is
A to F, control active.
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
5132 Self acknowl‐ 2 Yes The control automatically clears the alarm if the fault condition is no longer
edge detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
5137 Alarm class 2 [C] The alarm class specifies what action should be taken if the measurement dif‐
ference (frequency, 1836 Ä p. 353 or voltage, 1828 Ä p. 353) between the
A to F, control communication devices(s) of the AR-–4105 system differ more than allowed.
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
5138 Self acknowl‐ 2 Yes The control automatically clears the alarm if the fault condition is no longer
edge detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2850 Monitoring 2 [On] Overfrequency monitoring is carried out according to the following parame‐
ters. Monitoring is performed at two levels. Both values may be configured
2856 independent from each other (prerequisite: limit 1 < Level 2 limit).
2854 Limit 2 100.0 to 140.0% The percentage values that are to be monitored for each threshold limit are
defined here.
2860 2854: [100.4%]
If this value is reached or exceeded for at least the delay time without inter‐
2860: [102.0%] ruption, the action specified by the alarm class is initiated.
(Hysteresis:
Notes
0.05 Hz)
This value refers to the System rated frequency (parameter 1750 Ä p. 411).
(Reset Delay:
80 ms)
2855 Delay 2 0.02 to 99.99 s If the monitored mains frequency value exceeds the threshold value for the
delay time configured here, an alarm will be issued.
2861 [0.06 s]
Notes
If the monitored mains frequency falls below the threshold (minus the hyste‐
resis) before the delay expires the time will be reset.
2851 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2857 Control
Notes
2851: [A]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2857: [B] on page 888
2852 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2858
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2853 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
2859
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2900 Monitoring 2 [On] Underfrequency monitoring is carried out according to the following parame‐
ters. Monitoring is performed at two levels.
2906
Both values may be configured independent from each other (prerequisite:
Level 1 > Level 2).
2904 Limit 2 50.0 to 140.0% The percentage values that are to be monitored for each threshold limit are
defined here.
2910 2904: [99.6%]
If this value is reached or fallen below for at least the delay time without inter‐
2910: [98.0%] ruption, the action specified by the alarm class is initiated.
(Hysteresis:
Notes
0.05 Hz)
This value refers to the System rated frequency (parameter 1750 Ä p. 411).
(Reset Delay:
80 ms)
2905 Delay 2 0.02 to 99.99 s If the monitored mains frequency value falls below the threshold value for the
delay time configured here, an alarm will be issued.
2911 2905: [1.50 s]
Notes
2911: [0.06 s]
If the monitored mains frequency exceeds the threshold (plus the hysteresis)
again before the delay expires the time will be reset.
2901 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2907 Control
2903 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
2909 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2950 Monitoring 2 [On] Overvoltage monitoring is carried out according to the following parameters.
Monitoring is performed at two levels. Both values may be configured inde‐
2956 pendent from each other (prerequisite: limit 1 < Level 2 limit).
2954 Limit 2 50.0 to 150.0% The percentage values that are to be monitored for each threshold limit are
defined here.
2960 2954: [108.0%]
If this value is reached or exceeded for at least the delay time without inter‐
2960: [110.0%] ruption, the action specified by the alarm class is initiated.
(Hysteresis:
0.7%)
2955 Delay 2 0.02 to 99.99 s If the monitored mains voltage exceeds the threshold value for the delay time
configured here, an alarm will be issued.
2961 2955: [1.50 s]
Notes
2961: [0.06 s]
If the monitored mains voltage falls below the threshold (minus the hysteresis)
before the delay expires the time will be reset.
2951 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2957 Control
Notes
2951: [A]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
2957: [B] on page 888
2952 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2958
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2953 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
2959 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
8845 Mns. decou‐ 2 The mains overvoltage 1 alarm can be linked to the mains decoupling func‐
pling by over‐ tion, if required.
volt. 1
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 Ä p. 348
to 5817 Ä p. 348) within the monitoring limits.
3000 Monitoring 2 [On] Undervoltage monitoring is carried out according to the following parameters.
Monitoring is performed at two levels. Both values may be configured inde‐
3006 pendent from each other (prerequisite: Level 1 limit < Level 2 limit).
3004 Limit 2 10.0 to 150.0% The percentage values that are to be monitored for each threshold limit are
defined here.
3010 3004: [92.0%]
If this value is reached or exceeded for at least the delay time without inter‐
3010: [90.0%] ruption, the action specified by the alarm class is initiated.
(Hysteresis:
Notes
0.7%)
This value refers to the "Mains rated voltage" (parameter 1768 Ä p. 415).
(Reset Delay:
80 ms) Minimum value follows BDEW requirement.
3005 Delay 2 0.02 to 99.99 s If the monitored mains voltage falls below the threshold value for the delay
time configured here, an alarm will be issued.
3011 3005: [1.50 s]
Notes
3011: [0.06 s]
If the monitored mains voltage exceeds the threshold (plus the hysteresis)
again before the delay expires the time will be reset.
3001 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
3007 Control
Notes
3001: [A]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
3007: [B] on page 888
3002 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
3008
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3003 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
3009 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
8844 Mns. decou‐ 2 The mains undervoltage 1 alarm can be linked to the mains decoupling func‐
pling by under‐ tion, if required.
volt. 1
On The mains undervoltage 1 trip is linked to the mains decoupling function with
all its consequences.
[Off] The mains undervoltage 1 trip is ignored in the mains decoupling function.
Notes
It is recommended to configure the operating limits (parameter 5810 Ä p. 348
to 5817 Ä p. 348) within the monitoring limits.
8806 Monitoring 2 On Voltage increase monitoring is carried out according to the following parame‐
ters.
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 specified by the
alarm class is initiated.
Notes
This value refers to the "Mains rated voltage" (parameter 1768 Ä p. 415).
8849 AND character‐ 2 On If the 10 minute voltage averages of all phases exceed the limit, the moni‐
istics toring is tripping.
[Off] If the 10 minute voltage average of at least one phase exceeds the limit, the
monitoring is tripping.
8831 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
8832 Self acknowl‐ 4 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
8833 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
8850 Volt. incr. 0 — This visualization value shows the current 10 minute average voltage.
average
4951 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
4959 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
FRT Monitoring type Parameter "Mains voltage monitoring" 1771 Ä p. 346 determines,
if the Ph-Ph or Ph-N measurement is used.
If type "All" is available and configured, and 3Ph4W is configured,
"Time dependent Voltage Monitoring" is calculated from both vol‐
tages. If All and 1Ph3W is configured, only PH-N values are used.
Time-dep. voltage 1
ID Parameter CL Setting range Description
[Default]
4950 Monitoring 2 On Time-dependent voltage monitoring is carried out according to the following
parameters.
4952 AND character‐ 2 On Each phase falls below/exceeds the threshold for tripping.
istics
[Off] At least one phase falls below/exceeds the threshold for tripping.
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 carried out (The monitoring function triggers if
the measured voltage exceeds the curve).
4970 Init threshold 2 0.0 to 150.0% The time-dependent voltage monitoring initial threshold is configured here. If
the measured voltage falls below/exceeds this threshold, the monitoring
[80.0%] 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 monitoring func‐
tion triggers and the configured relay will energize.
4978 Fallback 2 0.0 to 150.0% The time-dependent voltage monitoring fallback voltage is configured here. If
threshold the measured voltage falls below/exceeds the voltage configured here for at
[90.0%] least the configured "Fallback time" (parameter 4968 Ä p. 366), the moni‐
toring sequence will be reset.
Notes
This parameter should always be configured to a value higher/lower than the
"Init threshold" (parameter 4970 Ä p. 365) for proper operation.
The parameter "Point 7 voltage" (parameter 4977 Ä p. 366) is used as fall‐
back threshold if it is configured to a value higher/lower than the parameter
"Fallback threshold" (parameter 4978 Ä p. 365).
4968 Fallback time 2 0.00 to 320.00 s The time-dependent voltage monitoring fallback time is configured here. If the
measured voltage falls below/exceeds the configured "Fallback threshold"
[1.00 s] (parameter 4978 Ä p. 365) for at least the time configured here, the moni‐
toring sequence will be reset.
4971 Point {x} 2 0.0 to 150.0% The voltage values of time-dependent voltage monitoring voltage points are
voltage configured here.
4972 4971: [45.0%]
[x = 1 to 7]
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-dependent voltage monitoring time points are config‐
ured here.
4962 [x = 1 to 7] 4961: [0.00 s]
4963 4962: [0.15 s]
4964 4963: [0.15 s]
4965 4964: [0.70 s]
4966 4965: [1.50 s]
4967 4966: [3.00 s]
4967: [4.00 s]
Time-dep. voltage 2
ID Parameter CL Setting range Description
[Default]
4954 Monitoring 2 On Time-dependent voltage 2 monitoring is carried out according to the following
parameters.
4956 AND character‐ 2 On Each phase falls below/exceeds the threshold for tripping.
istics
[Off] At least one phase falls below/exceeds the threshold for tripping.
4957 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 carried out (The monitoring function triggers if
the measured voltage exceeds the curve).
4990 Init threshold 2 0.0 to 200.0% The time-dependent voltage 2 monitoring initial threshold is configured here.
If the measured voltage falls below/exceeds this threshold, the monitoring
[80.0%] sequence starts and the voltage threshold will change in time according to the
configured threshold curve points.
If the measured voltage 2 falls below/exceeds this curve, the monitoring func‐
tion triggers and the configured relay will energize.
4998 Fallback 2 0.0 to 200.0% The time-dependent voltage 2 monitoring fallback voltage is configured here.
threshold If the measured voltage falls below/exceeds the voltage configured here for at
[90.0%] least the configured "Fallback time" (parameter 4988 Ä p. 367), the moni‐
toring sequence will be reset.
Notes
This parameter should always be configured to a value higher/lower than the
"Init threshold" (parameter 4990 Ä p. 367) for proper operation.
The parameter "Point 7 voltage" (parameter 4997 Ä p. 367) is used as fall‐
back threshold if it is configured to a value higher/lower than the parameter
"Fallback threshold" (parameter 4998 Ä p. 367).
4988 Fallback time 2 0.00 to 320.00 s The time-dependent voltage 2 monitoring fallback time is configured here. If
the measured voltage falls below/exceeds the configured "Fallback threshold"
[1.00 s] (parameter 4998 Ä p. 367) for at least the time configured here, the moni‐
toring sequence will be reset.
4991 Point {x} 2 0.0 to 200.0% The voltage values of time-dependent voltage 2 monitoring voltage points are
voltage (2) configured here.
4992 4991: [10.0%]
[x = 1 to 7]
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%.
4981 Point {x} time 2 0.00 to 320.00 s The time values of time-dependent voltage 2 monitoring time points are con‐
figured here.
4982 [x = 1 to 7] 4981: [0.00 s]
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]
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 func‐
tion of generator voltage and generator reactive power.
QV monitoring is triggered if the following conditions are fulfilled:
(Refer to Fig. 180 for details)
3285 Limit under‐ 2 45 to 150% The percentage voltage value that is to be monitored is defined here.
voltage
[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 rated voltage" (parameter 1766 Ä p. 412).
3291 Reactive power 2 2 to 100% The percentage reactive value that is to be monitored is defined here.
threshold
[5%] 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]" (parameter
1758 Ä p. 413).
3283 Delay step 1 2 0.10 to 99.99 s If the QV monitoring conditions are met, for the delay time configured here, an
alarm "QV monitoring 1" will be issued and LogicsManager 07.29 becomes
[0.50 s] TRUE.
Notes
The decoupling function is only activated if "Mains decoupling by QV" (param‐
eter 3296 Ä p. 369) 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 configured here, an
alarm "QV monitoring 2" will be issued and LogicsManager 07.30 becomes
[1.50 s] TRUE.
3280 Alarm class 2 Class The alarm class specifies what action should be taken when at least one
A/B/C/D/E/F, delay has been exceeded.
Control
[B]
Notes
The alarm class is valid for parameter 3283 Ä p. 369 and 3284 Ä p. 369.
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3293 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
Notes
The self acknowledge is valid for parameter 3283 Ä p. 369 and
3284 Ä p. 369.
3296 Mains decou‐ 2 On The QV monitoring function is linked to the mains decoupling function with all
pling by QV its consequences and is assigned to "Delay step 1" (parameter
3283 Ä p. 369).
df/dt (ROCOF) df/dt (rate of change of frequency) monitoring measures the sta‐
bility 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.
3053 Phase shift: 2 [1- and 3 During single-phase voltage phase/vector shift monitoring, tripping occurs if
Monitoring phase] the phase/vector shift exceeds the configured threshold value (param‐
eter 3054 Ä p. 371) 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 (param‐
eter 3055 Ä p. 371) 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 Ä p. 371) is taken into consideration; if a
phase/vector shift occurs in all three phases, the three-phase threshold value
(parameter 3055 Ä p. 371) is taken into consideration. Single phase moni‐
toring 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 meas‐
uring (parameter 1853 Ä p. 416) is configured to "3Ph 4W" or "3Ph 3W".
3054 Phase shift: 2 3 to 30° If the electrical angle of the mains voltage shifts more than this configured
Limit 1 phase value in any single phase, an alarm with the class configured in param‐
[20°] eter 3051 Ä p. 371 is initiated.
Depending on the configured mains decoupling procedure (param‐
eter 3110 Ä p. 349), the GCB, MCB, or an external CB will be opened.
3055 Phase shift: 2 3 to 30° If the electrical angle of the mains voltage shifts more than this configured
Limit 3 phase value in all three phases, an alarm with the class configured in param‐
[8°] eter 3051 Ä p. 371 is initiated.
Depending on the configured mains decoupling procedure (param‐
eter 3110 Ä p. 349), the GCB, MCB, or an external CB will be opened.
3051 Phase shift: 2 Class Each limit may be assigned an independent alarm class that specifies what
Alarm class A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
3052 Phase shift: 2 [Yes] The control automatically clears the alarm if the fault condition is no longer
Self acknowl‐ detected.
edge
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).
3056 Phase shift: 2 [Always] Monitoring for this fault condition is continuously enabled.
Enabled
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
3104 df/dt: df/dt 2 0.1 to 9.9 Hz/s The df/dt threshold is defined here. If this value is reached or exceeded for at
Limit least the delay time without interruption, an alarm with the class configured in
[2.6 Hz/s] parameter 3101 Ä p. 372 is initiated.
(Hysteresis: 0.1 Depending on the configured mains decoupling procedure (param‐
Hz/s) eter 3110 Ä p. 349), the GCB, MCB, or an external CB will be opened.
(Reset Delay:
80 ms)
3105 df/dt: Delay 2 0.10 to 2.00 s If the monitored rate of df/dt exceeds the threshold value for the delay time
configured here, an alarm will be issued.
[0.10 s]
If the monitored df/dt exceeds the threshold (plus the hysteresis) again before
the delay expires the time will be reset.
3101 df/dt: Alarm 2 Class Each limit may be assigned an independent alarm class that specifies what
class A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
3102 df/dt: Self 2 Yes The control automatically clears the alarm if the fault condition is no longer
acknowledge 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).
3103 df/dt: Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
3970 Monitoring 2 [On] Phase rotation monitoring is carried out according to the following parame‐
ters.
3974 Mains phase 2 [CW] The three-phase measured mains voltage is rotating CW (clock-wise; that
rotation 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).
3971 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B]
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.
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3972 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3973 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
3200 Monitoring 2 On Mains import power monitoring is carried out according to the following
parameters. Monitoring is performed at two levels. Both values may be con‐
3206 figured independent from each other (prerequisite: Level 1 limit < Level 2
limit).
3215 Monitoring at 2 [Overrun] The monitored value must exceed the limit to be considered as out of limits.
3216 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 (depending on the
setting of parameter 3215 Ä p. 375 or 3216 Ä p. 375) for at least the delay
3210 3204: [80.00%] time (parameter 3205 Ä p. 375 or 3211 Ä p. 375), the action specified by the
3210: alarm class is initiated.
[100.00%]
Notes
This value refers to the Mains rated active power (parameter 1748 Ä p. 415).
3213 Hysteresis 2 0 to 99.99% The monitored mains power level must return within the limits configured in
parameter 3204 Ä p. 375 or 3210 Ä p. 375 plus or minus (depending on the
3214 [0.01%] setting of parameter 3215 Ä p. 375 or 3216 Ä p. 375) the value configured
(Reset Delay: here, to reset the alarm.
80 ms)
3205 Delay 2 0.02 to 99.99 s If the monitored mains import power falls below or exceeds (depending on the
setting of parameter 3215 Ä p. 375 or 3216 Ä p. 375) the threshold value for
3211 [1.00 s] the delay time configured here, an alarm 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 Ä p. 375 or
3214 Ä p. 375) before the delay expires the time will be reset.
3201 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
3207 Control
Notes
3201: [A]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
3207: [B] on page 888
3202 Self acknowl‐ 2 3202: [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
3208
3208: [No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3203 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
3209 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
3225 Monitoring 2 On Mains export power monitoring is carried out according to the following
parameters. Monitoring is performed at two levels. Both values may be con‐
3233 figured independent from each other (prerequisite: Level 1 limit < Level 2
limit).
3232 Monitoring at 2 [Overrun] The monitored value must exceed the limit to be considered as out of limits.
3240 Underrun The monitored value must fall 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 (depending on the
setting of parameter 3232 Ä p. 376 or 3240 Ä p. 376) for at least the delay
3237 3229: [80.00%] time (parameter 3230 Ä p. 376 or 3238 Ä p. 376), the action specified by the
3237: alarm class is initiated.
[100.00%]
Notes
This value refers to the Mains rated active power (parameter 1748 Ä p. 415).
3231 Hysteresis 2 0 to 99.99% The monitored mains power level must return within the limits configured in
parameter 3229 Ä p. 376 or 3237 Ä p. 376 plus or minus (depending on the
3239 [0.01%] setting of parameter 3232 Ä p. 376 or 3240 Ä p. 376) the value configured
(Reset Delay: here, to reset the alarm.
80 ms)
3230 Delay 2 0.02 to 99.99 s If the monitored mains export power falls below or exceeds (depending on the
setting of ns export power falls below or exceeds (depending on the setting of
3238 [1.00 s] parameter 3232 Ä p. 376 or 3240 Ä p. 376) the threshold value for the delay
time configured here, an alarm will be issued.
Notes
If the monitored mains import power exceeds or falls below the threshold
(plus or minus the hysteresis configured in parameter 3231 Ä p. 376 or
3239 Ä p. 376) before the delay expires the time will be reset.
3226 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
3234 Control
Notes
3226: [A]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
3234: [B] on page 888
3227 Self acknowl‐ 2 3227: [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
3235
3235: [No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3228 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
3236
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2930 Monitoring 2 [On] On Monitoring of the mains active power mismatch is carried out according to
the following parameters.
2935 Limit 2 1.0 to 99.9% If the difference between the measured import or export power and the power
setpoint exceeds this value for at least the delay time (param‐
[5.0%] eter 2933 Ä p. 377) without interruption, the action specified by the alarm
class is initiated.
Notes
This value refers to the mains rated active power (parameter 1748 Ä p. 415).
2933 Delay 2 3 to 9999 s If the monitored active power mismatch exceeds the threshold value config‐
ured in parameter 2935 Ä p. 377 for the delay time configured here, an alarm
[30 s] will be issued.
Notes
If the monitored active power mismatch falls below the threshold (minus the
hysteresis) before the delay expires the time will be reset.
2931 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
2932 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2936 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
2975 Monitoring 2 On Mains lagging power factor monitoring is carried out according to the following
parameters. Monitoring is performed at two levels. Both values may be con‐
2980 figured independent from each other.
2978 Limit 2 -0.999 to 1.000 The values that are to be monitored for each threshold limit are defined here.
2983 2978: [+ 0.900]
2983: [+ 0.800]
Notes
If the power factor becomes more lagging (i.e. inductive, Fig. 182) than a lag‐
ging PF value (pos.) or a leading PF value (neg.) for at least the delay time
(parameters 2979 Ä p. 379 or 2984 Ä p. 379) without interruption, the logical
command variables 07.17 (level 1) or 07.18 (level 2) are enabled and the
action specified by the alarm class is initiated.
2989 Hysteresis 2 0.0 to 0.99 The monitored power factor must return within the limits configured in param‐
eter 2978 Ä p. 378 or 2983 Ä p. 378 minus the value configured here, to
2990 [0.02] reset the alarm.
(Reset Delay:
80 ms)
2979 Delay 2 0.02 to 99.99 s If the monitored generator power factor is more lagging than the configured
limit for the delay time configured here, an alarm will be issued.
2984 2979: [30.00 s]
Notes
2984: [1.00 s]
If the monitored generator power factor returns within the limit (minus the
Hysteresis configured in parameter 2989 Ä p. 379 or 2990 Ä p. 379) before
the delay expires the time will be reset.
2987 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
2988 Control
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
2976 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
2981
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
2977 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
2982 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
3025 Monitoring 2 On Mains leading power factor monitoring is carried out according to the following
parameters. Monitoring is performed at two levels. Both values may be con‐
3030 figured independent from each other.
3028 Limit 2 -0.999 to 01.000 The values that are to be monitored for each threshold limit are defined here.
3033 3028: [- 0.900] Notes
3033: [- 0.800] If the power factor becomes more leading (i.e. inductive, Fig. 183) than a
leading PF value (pos.) or a leading PF value (neg.) for at least the delay time
(parameters 3029 Ä p. 380 or 3034 Ä p. 380) without interruption, the logical
command variables 07.17 (level 1) or 07.18 (level 2) are enabled and the
action specified by the alarm class is initiated.
3039 Hysteresis 2 0.0 to 0.99 The monitored power factor must return within the limits configured in param‐
eter 3028 Ä p. 380 or 3033 Ä p. 380 minus the value configured here, to
3040 [0.02] reset the alarm.
(Reset Delay:
80 ms)
3029 Delay 2 0.02 to 99.99 s If the monitored generator power factor is more leading than the configured
limit for the delay time configured here, an alarm will be issued.
3034 3029: [10.00 s]
Notes
3034: [1.00 s]
If the monitored generator power factor returns within the limit (minus the
Hysteresis configured in parameter 3039 Ä p. 380 or 3033 Ä p. 380) before
the delay expires the time will be reset.
3037 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
3038 Control
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3026 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
3031
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3027 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
3032 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
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 Ä p. 382).
NOTICE!
If load-dependent start/stop (refer to Ä Chapter
4.4.5.1.5 “Load Dependent Start/Stop (LDSS)”
on page 285) 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.
2600 Monitoring 2 [On] Monitoring of the GCB is carried out according to the following parameters.
2601 GCB Alarm 2 Class Each limit may be assigned an independent alarm class that specifies what
class A/B/C/D/E/F/ action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3418 GCB maximum 2 1 to 10 The maximum number of breaker closing attempts is configured in this
closing parameter (relay output "Command: close GCB").
attempts [5]
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 2 0.10 to 5.00 s If the "Reply GCB" is not detected as energized once this timer expires, a
monitoring "GCB fail to open" alarm is issued. This timer initiates as soon as the "open
[2.00 s] breaker" sequence begins. The alarm configured in parameter 2601 Ä p. 382
is issued.
3060 Monitoring 2 [On] Monitoring of the GCB synchronization is carried out according to the fol‐
lowing parameters.
3063 Timeout 2 3 to 999 s If it was not possible to synchronize the GCB within the time configured here,
an alarm will be issued.
[60 s]
The message "GCB syn. timeout" is issued and the logical command variable
"08.30" will be enabled.
3061 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3062 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
Fault at 'opening the MCB' This alarm class has the following influence to the function of the
unit:
n 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.
2620 MCB moni‐ 2 [On] Monitoring of the MCB is carried out according to the following parameters.
toring
Off Monitoring is disabled.
2621 MCB Alarm 2 Class Each limit may be assigned an independent alarm class that specifies what
class A/B/C/D/E/F/ action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3419 MCB maximum 2 1 to 10 The maximum number of breaker closing attempts is configured in this
closing parameter (relay output "Command: close MCB").
attempts [5]
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 2 0.10 to 5.00 s If the "Reply MCB" is not detected as energized once this timer expires, an
monitoring "MCB fail to open" alarm is issued.
[2.00 s]
This timer initiates as soon as the "open breaker" sequence begins. The
alarm configured in parameter 2621 Ä p. 384 is issued.
3070 Monitoring 2 [On] Monitoring of the MCB synchronization is carried out according to the fol‐
lowing parameters.
3073 Timeout 2 3 to 999 s If it was not possible to synchronize the MCB within the time configured here,
an alarm will be issued.
[60 s]
The message "MCB syn. timeout" is issued and the logical command variable
"08.31" will be enabled.
3071 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3072 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
5148 Monitoring 2 On Monitoring of the Neutral Contactor is carried out according to the following
parameters, if the Neutral Interlocking function (parameter 1840 Ä p. 224) 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 This function may be assigned an independent alarm class that specifies
A/B/C/D/E/F/ what action should be taken when this function triggers an alarm.
CONTROL
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
5150 Self acknowl‐ 2 Yes The control automatically clears the alarm if the fault condition is no longer
edge 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).
5153 Alarm text - [N-cont. reply Text is visible in display during alarm is detected.
mism.]
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 config‐
ured using ToolKit and the logical command variable "15.{x}" will
be enabled.
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 detail screen. Selection
screen on HMI/display works fine with up to 30 characters; others are over‐
written 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.
4200 Monitoring 2 On Monitoring of the limit {x} is carried out according to the following parameters.
4204 Monitoring at 2 [Overrun] The monitored value must exceed the threshold limit for a fault to be recog‐
nized.
Underrun The monitored value must fall below the threshold limit for a fault to be recog‐
nized.
4205 Limit 2 -21000000.00 to The threshold limit of the value to be monitored is defined by this parameter.
21000000.00 If this value is reached or exceeded / fallen below (dependent on param‐
eter 4207 Ä p. 387) for at least the delay time configured in param‐
[100.00] eter 4207 Ä p. 387 the action specified by the alarm class is initiated after the
configured delay expires.
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 Ä Chapter 9.4.2.12 “Display Value Format” on page 878).
Notes
Refer to Ä “Examples” on page 389 for examples on how to configure the
limit.
4216 Hysteresis 2 0 to During monitoring, the actual value must exceed or fall below one of the limits
21000000.00 defined in parameter 4205 Ä p. 387 to be recognized as out of permissible
limits. For a value to register as having returned to the permissible limits, the
[1.00] 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 param‐
eter 4205 Ä p. 387.
4207 Delay 2 0.02 to If the monitored value exceeds or falls below the threshold value for the delay
99999.99 s time configured here, an alarm will be issued. If the monitored value falls
below the threshold (plus/minus the hysteresis, dependent on param‐
[1.00 s] eter 4204 Ä p. 387) 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 If the monitored value exceeds or falls below the threshold value, a counter
s 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
[1.00 s] expires the time will be reset.
End: For flexible limit 25 ... 32 only; sample referred to flexible limit #25.
4201 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
4202 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
4203 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
4206 AM FlexLim 1 2 Determined by Any possible data sources may be selected. Analog and digital OUT value/
source AnalogManager signal are available as sources for AnalogManager and LogicsManager.
82.01
Refer to Ä Chapter 9.4.1 “Data Sources AM” on page 856 for a list of all data
[A1 = 10.01 sources.
ZERO]
Parameter IDs
Flexible Descrip‐ Moni‐ Moni‐ Moni‐ Limit Hyste‐ Delay Alarm Self Enabled
limit # tion toring tored toring at resis class acknowl‐
analog Fallback edge
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
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
Flexible Descrip‐ Moni‐ Moni‐ Moni‐ Limit Hyste‐ Delay Alarm Self Enabled
limit # tion toring tored toring at resis class acknowl‐
analog Fallback edge
value
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
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
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 Ä p. 412) =
200 kW
11.01 Engine speed 1256 rpm Rated speed (param‐ 08373 (= 83.73%)
eter 1601 Ä p. 419) = 1500
rpm
06.03 Analog input 3 (config‐ 4.25 bar Display in 0.01 bar 00425 (= 4.25 bar)
ured to VDO 5 bar)
Example value Desired limit Reference value / display Limit entry format
value
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 monitoring Example for high coolant temperature
monitoring
Monitoring On On
Hysteresis 10 2
Delay 0.50 s 3s
Alarm class F B
Self acknowledgment No No
4.5.6 Miscellaneous
4.5.6.1 General monitoring settings
1756 Time until horn 0 0 to 1,000 s After each alarm of alarm class B through F occurs, the alarm LED flashes
reset and the horn (command variable 03.05) is enabled. After the delay time "time
[180 s] 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
If this parameter is configured to 0, the horn will remain active until it will be
acknowledged.
12490 Ext. acknowl‐ 2 Determined by It is possible to acknowledge all alarms simultaneously from remote, e.g. with
edge LogicsManager a discrete input. The logical output of the LogicsManager has to become
86.15 TRUE twice.
(External
acknowledg‐ [(09.05 Dis‐ The first time is for acknowledging the horn, the second for all alarm mes‐
ment of alarms) crete input 5 & sages. The On-delay time is the minimum time the input signals have to be
1) OR 04.14 "1". The Off-delay time is the time how long the input conditions have to be
Remota "0" before the next high signal is accepted.
acknowledge]
Once the conditions of the LogicsManager have been fulfilled the alarms will
= 10714 be acknowledged.
The first high signal into the discrete input acknowledges the command vari‐
able 03.05 (horn).
The second high signal acknowledges all inactive alarm messages.
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
1849 Stop mode 2 If operating mode is not fixed via LogicsManager (see chapter Ä Chapter 6.3.5 “Performing
with stopping Remote Start/Stop And Acknowledgment” on page 493 for details) with this parameter it can be
alarm decided if the operation mode changes to STOP mode when a shutdown alarm of class C, D, E,
F occurs.
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 Ä p. 275/Ä p. 852, 12520 Ä p. 275/Ä p. 852, 12530 Ä p. 276/
Ä p. 852 do have priority.
5775 IOP Delayed 2 0 to 9999 s This parameter gives a load sharing participant the opportunity to delay the
unload. Alarm unload if an shutdown alarm of alarm class C or E occurs. The time gained
C,E [0 s] 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 set‐
ting of 0 s deactivates this function.
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
8120 Free alarm 1 2 Determined by This LogicsManager is used to select the source of monitoring.
LogicsManager
88.01 Notes
[02.01 FALSE For information on the LogicsManager and its default settings see Ä Chapter
& 1 & 1] 9.3.1 “LogicsManager Overview” on page 811.
= 11550
8121 Alarm class 2 Class The assigned independent alarm class specifies what action should be taken
A/B/C/D/E/F, when the alarm becomes TRUE.
Control
[Class B]
8122 Self acknowl‐ 2 Yes/No The control automatically clears the alarm if the fault condition is no longer
edge detected.
[No] The control does not automatically clears the alarm if 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).
8123 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
[1.00 s]
Parameter IDs
Free alarm # Description LogicsManager Alarm class Self acknowl‐ Enabled Delay
edge
Free alarm # Description LogicsManager Alarm class Self acknowl‐ Enabled Delay
edge
3150 Monitoring 2 On CANopen interface 1 monitoring is carried out according to the following
parameters.
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 action specified
by the alarm class is initiated. The delay timer is re-initialized after every mes‐
sage is received.
3151 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F/ action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3152 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3153 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
Fig. 184: CAN2 state If you are not using the exact amount of external
I/O modules you have defined, the monitoring
function does not work correctly.
16187 Monitoring 2 On CANopen interface 2 monitoring is carried out according to the following
parameters.
16186 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 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.
16188 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F/ action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
16190 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
16189 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
ECU settings
ID Parameter CL Setting range Description
[Default]
15172 Monitoring 2 On Monitoring of the ECU's CAN messages is carried out according to the fol‐
lowing parameters. The address of the ECU is taken from parameter “Engine
control address” (15107 Ä p. 441)
15176 Delay 2 0.02 to 999 s The delay is configured with this parameter. If the interface does not receive a
CAN message from the ECU within this delay time, the action specified by the
[1 s] alarm class is initiated.
The delay timer is re-initialized if any message from the ECU is received.
15173 Alarm class 2 Class Each limit may be assigned to an independent alarm class that specifies what
A/B/C/D/E/F/ action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
15174 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
15175 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
Device 1 settings
ID Parameter CL Setting range Description
[Default]
15177 Monitoring 2 On Monitoring of the CAN messages of device 1 is carried out according to the
following parameters.
15182 Delay 2 0.02 to 999 s The delay is configured with this parameter. If the interface does not receive a
CAN message from device 1 within this delay time, the action specified by the
[1 s] alarm class is initiated.
The delay timer is re-initialized if any message from the device 1 is received.
15179 Alarm class 2 Class Each limit may be assigned to an independent alarm class that specifies what
A/B/C/D/E/F/ action should be taken when the limit is surpassed.
Control
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
15180 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
15181 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
Device 2 settings
ID Parameter CL Setting range Description
[Default]
15183 Monitoring 2 On Monitoring of the CAN messages of device 2 is carried out according to the
following parameters.
15188 Delay 2 0.02 to 999 s The delay is configured with this parameter. If the interface does not receive a
CAN message from device 2 within this delay time, the action specified by the
[1 s] alarm class is initiated.
The delay timer is re-initialized if any message from the device 2 is received.
15185 Alarm class 2 Class Each limit may be assigned to an independent alarm class that specifies what
A/B/C/D/E/F/ action should be taken when the limit is surpassed.
Control
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
15186 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
15187 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
Device 3 settings
ID Parameter CL Setting range Description
[Default]
15189 Monitoring 2 On Monitoring of the CAN messages of device 3 is carried out according to the
following parameters.
15194 Delay 2 0.02 to 999 s The delay is configured with this parameter. If the interface does not receive a
CAN message from device 3 within this delay time, the action specified by the
[1 s] alarm class is initiated.
The delay timer is re-initialized if any message from the device 3 is received.
15191 Alarm class 2 Class Each limit may be assigned to an independent alarm class that specifies what
A/B/C/D/E/F/ action should be taken when the limit is surpassed.
Control
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
15192 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
15193 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
15115 Monitoring 2 On Monitoring of the Red Stop Lamp message from the ECU is carried out
according to the following parameters.
15119 Delay 2 0 to 999 s The red stop lamp delay is configured with this parameter.
[2 s] If the ECU sends the Red Stop Lamp On message, the action specified by
the alarm class is initiated after the delay configured here expires.
15116 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F/ action should be taken when the limit is surpassed.
Control
[A]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
15117 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
15118 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
15120 Monitoring 2 On Monitoring of the Amber Warning Lamp message from the ECU is carried out
according to the following parameters.
15124 Delay 2 0 to 999 s The amber warning lamp delay is configured with this parameter.
[2 s] If the ECU sends the Amber Warning Lamp On message, the action specified
by the alarm class is initiated after the delay configured here expires.
15121 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F/ action should be taken when the limit is surpassed.
Control
[A]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
15122 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
15123 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
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.
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.
9947 Self acknowl‐ 2 [Yes] The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
No The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3450 Monitoring 2 3450: [On] Overvoltage monitoring of the battery voltage is carried out according to the
following parameters. Both values may be configured independent from each
3456 3456: [Off] other (prerequisite: Level 1 > Level 2).
(Hysteresis: 0.1
Monitoring is disabled for Level 1 limit and/or Level 2 limit.
V)
(Reset Delay:
1s)
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 reaches or exceeds this value for at least the
delay time without interruption, the action specified by the alarm class is initi‐
3460: [35.0 V] ated.
3455 Delay 2 0.02 to 99.99 s If the monitored battery voltage exceeds the threshold value for the delay time
configured here, an alarm will be issued.
3461 3455: [5.00 s]
3461: [1.00 s]
Notes
If the monitored battery voltage falls below the threshold (minus the hyste‐
resis) before the delay expires the time will be reset.
3451 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
3457 Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3452 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
3458
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3453 Enabled 2 [Always] Monitoring for this fault condition is continuously enabled.
3459 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
3500 Monitoring 2 [On] Undervoltage monitoring of the battery voltage is carried out according to the
following parameters. Both values may be configured independent from each
3506 other (prerequisite: Level 1 > 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] If the monitored battery voltage reaches or falls below this value for at least
the delay time without interruption, the action specified by the alarm class is
3510: [20.0 V] initiated.
(Hysteresis: 0.1
Notes
V)
The default monitoring limit for battery undervoltage is 24 Vdc after 60 sec‐
(Reset Delay:
onds.
1s)
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 the threshold value for the delay time config‐
ured here, an alarm will be issued.
3511 3505: [60.00 s]
Notes
3511: [10.00 s]
If the battery voltage exceeds the threshold (plus the hysteresis) again before
the delay expires the time will be reset.
3501 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
3507 Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
3502 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
3508
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
3503 Enabled 4 [Always] Monitoring for this fault condition is continuously enabled.
3509 87.70 Monitoring for fault conditions is not performed until engine monitoring is ena‐
LM:Eng.mon bled. 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 TRUE.
96.{xx} Example:
LM: Flag{xx} 96.01 LM: Flag1, 96.02 LM: Flag2, ..., 96.32 LM: Flag32
Parameter ID
Parameter ID
4071 Alarm class 2 Alarm class This function may be assigned an independent alarm class that specifies
Class what action should be taken when this function triggers an alarm.
A/B/C/D/E/F,
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
4061 Alarm class 2 Class This function may be assigned an independent alarm class that specifies
A/B/C/D/E/F, what action should be taken when this function triggers an alarm.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888.
4062 Self acknowl‐ 2 Yes The control automatically clears the alarm if the fault condition is no longer
edge 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).
Diagnostic screen
The easYgen-XT provides an overview screen to
check all members on the load share bus and
helps trouble shooting. This screen “easYgen
diagnostic” should be watched, when the system
update is executed. It is located under
“Status Menu / Next page è Multi-unit
è Diagnostic devices” .
How to initiate a system update Navigate to “Next page (Status Menu) è Multi-unit
è Diagnostic Devices”
The system update can be initiated by
n softkey button [Syst. upd.] in the HMI,
n ToolKit switch 13334 Ä p. 406 “System update” , or
n LogicsManager 86.35 with parameter 7801 Ä p. 406 “System
update” .
NOTICE!
Please ensure, if you are using the LogicsManager
“7801 System update” or the parameter “13334
Syst. upd” ., that the signal goes false after exe‐
cuting. Otherwise, all buttons relating to system
update are locked.
7801 System update 2 Determined by To select logical input(s) to cause a system update.
LogicsManager
86.35
[(0 & 1) & 1]
= 11974
13334 System update 2 Yes Network is checked for members and its states. Updated results become new
status.
9925 Monitored -/- Latest result of Result of members count driven by system update parameter 13334.
easYgen members count
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 Ä p. 404.
7833 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
Notes
[B]
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
7834 Self acknowl‐ -/- Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
The device at which the system update has been initiated sends a
System update request for 30 seconds to all members on the load
share (system) bus.
During this time all members (including missing LS-5 and missing
easYgen) disable their missing member monitoring function and
observing which members are momentarily actively participating.
This condition will be fixed for this 30 seconds period and the
number of members will be stored in the missing member monitor
in all easYgens short before the 30 seconds are ending. Then the
missing member monitoring will be enabled again in all easYgens.
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 over
Ethernet network A. The occurring cases here are restricted and
will be treated therefore separately.
Unit available This device is recognized and monitored with the missing member
monitor according to the latest System Update order.
GREEN
Add Device This device is recognized but not registered according to the latest
system update order. Therefore, the missing member monitoring
does not observe the device.
YELLOW
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 There is no device recognized according to the latest system
update. Communication error on network.
RED / BLACK
This unit is suspected.
(twinkling)
Notes
This is only displayed in the affected easYgen.
Removing a device If a device shall be removed from an already running and commis‐
sioned network, proceed as follows:
n Check 1: The easYgen tries to close the GCB, but the gener‐
ator is not within its operating range (parame‐
ters 5800 Ä p. 302, 5801 Ä p. 302, 5802 Ä p. 302, or
5803 Ä p. 302).
n Check 2: The easYgen tries to synchronize the GCB, but the
busbar is not within the generator operating range (parame‐
ters 5800 Ä p. 302, 5801 Ä p. 302, 5802 Ä p. 302, or
5803 Ä p. 302).
n Check 3: The easYgen tries close the GCB in breaker transi‐
tion mode "Open transition" with GCB and MCB open status. In
this condition the busbar is expected as dead, but the busbar
voltage is NOT below the dead busbar detection limit (param‐
eter 5820 Ä p. 415).
n 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.
n 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 Ä p. 348, 5811 Ä p. 348,
5812 Ä p. 348, or 5813 Ä p. 348).
n (Checks 6 to 10 are intentionally NOT available in
easYgen-3100XT/3200XT.)
NOTICE!
If load-dependent start/stop (refer to Ä Chapter
4.4.5.1.5 “Load Dependent Start/Stop (LDSS)”
on page 285) 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.
2660 Monitoring 2 [On] Monitoring of the operating range is carried out according to the following
parameters.
2663 Delay 2 1 to 999 s If one of the above mentioned conditions for an operating range failure is ful‐
filled, an alarm will be issued. If the respective condition is not fulfilled any‐
[30 s] more before the delay time expires, the delay time will be reset.
2661 Alarm class 2 Class Each limit may be assigned an independent alarm class that specifies what
A/B/C/D/E/F, action should be taken when the limit is surpassed.
Control
[B]
Notes
For additional information refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888
2662 Self acknowl‐ 2 Yes The control unit automatically clears the alarm if the fault condition is no
edge longer detected.
[No] The control unit does not automatically reset the alarm when the fault condi‐
tion is no longer detected.
The alarm must be acknowledged and reset by manually pressing the appro‐
priate buttons or by activating the LogicsManager output "External acknowl‐
edgment" (via a discrete input or via an interface).
Dependencies
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.
n PF = P/S = cos Φ
n Q = √(S2-P2)
n S = √(P2+Q2)
n P = S * PF
Fig. 187: AC power triangle
1750 System rated 2 50 / 60 Hz The rated frequency of the system is used as a reference figure for all fre‐
frequency quency related functions, which use a percentage value, like frequency moni‐
[50 Hz] toring, breaker operation windows or the AnalogManager.
1825 System rated 2 0.5 to 99999.9 This value specifies 100% of the system rated power, which is used for
active power system related indications and calculations.
[kW] [200.0 kW]
The AnalogManager 10.11 "System active nominal power" and 10.12
"System total real power" are related to this value or setting.
1858 1Ph2W voltage 3 [Phase - The unit is configured for measuring phase-phase voltages if 1Ph 2W meas‐
measuring phase] uring is selected.
Phase - neutral The unit is configured for measuring phase-neutral voltages if 1Ph 2W meas‐
uring is selected.
Notes
For information on measuring principles refer to Ä Chapter 3.3.5.1 “Generator
Voltage” on page 51.
Never configure the busbar measurement for phase-neutral, if the other sys‐
tems 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 considered for 1Ph 2W measuring .
rotation
CCW A counter-clockwise rotation field is considered for 1Ph 2W measuring.
Notes
For information on measuring principles refer to Ä Chapter 3.3.5.1 “Generator
Voltage” on page 51.
1854 Additional CT 2 [Mains cur‐ This parameter configures whether ground or mains current is measured on
input rent] / Ground terminals ½ or the input is disabled.
current / Off
1835 Ground current 2 1A Application specific ground current range must be selected e.g. for rated
range values.
[5A]
1810 Gnd. CT pri‐ 2 [500 A/x] CT ground current measuring primary rated value.
mary rated cur‐
rent 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.6.2 Generator
ID Parameter CL Setting range Description
[Default]
235 Generator type 2 The genset control supports two types of generators:
n synchronous generators
n 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:
n The speed is regulated with the speed signal from the MPU or
J1939/CAN input (as long as the GCB is open).
n The closing of the GCB is executed, if the speed is within the corre‐
sponding frequency range of the generator operating window. The
voltage and phase angle is ignored in this case.
n The generator monitoring (under/over frequency and under/overvoltage/
asymmetry) is switched off, until the generator breaker is closed.
n After opening the GCB, under/over frequency and under/overvoltage and
asymmetry monitoring is switched on again.
n The Frequency/MPU speed plausibility monitoring is only active, if the
GCB is closed.
n The synchroscope is not displayed in the asynchronous modus.
Notes
The asynchronous mode is used in slip synchronization only (Synchronization
GCB (parameter 5729 Ä p. 215) = Slip frequency.
Recommended settings
The asynchronous modus is normally used in mains parallel operation.
Please consider the following settings:
Notes
The asynchron mode is not recommended for emergency power applications.
1766 Generator 2 50 to 650000 V This value refers to the rated voltage of the generator (generator voltage on
rated voltage data plate) and is the voltage measured on the potential transformer primary.
[400 V]
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 2 0.5 to 99999.9 This value specifies the generator real power rating, which is used as a refer‐
active power kW ence figure for related functions. The generator rated active power is the gen‐
[kW] erator apparent power multiplied by the generator power factor (typically
[200.0 kW] ~0.8). These values are indicated in the generator data plate ( Ä “Dependen‐
cies” on page 411).
1758 Gen. rated 2 0.5 to 99999.9 This value specifies the generator reactive power rating, which is used as a
react. power kvar reference figure for related functions. The generator rated reactive power also
[kvar] depends on the generator values ( Ä “Dependencies” on page 411).
[200.0 kvar]
1754 Generator 2 1 to 32000 A This value specifies the generator rated current, which is used as a reference
rated current figure for related functions.
[300 A]
1851 Generator 2 3Ph 4W OD Measurement is performed Line-Neutral (Open Delta connected system). The
voltage meas‐ voltage is connected via transformer with 3 Wire.
uring
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.
Monitoring refers to the following voltages:
n VL1N, VL12
[3Ph 4W] Measurement is performed Line-Neutral (WYE connected system) and Line-
Line (Delta connected system). The protection depends on the setting of
parameter 1770 Ä p. 303.
Phase voltages and the neutral must be connected for proper calculation.
Measurement, display and protection are adjusted according to the rules for
WYE connected systems.
Monitoring refers to the following voltages:
Notes
If this parameter is configured to 1Ph 3W, the generator and mains rated vol‐
tages (parameters 1766 Ä p. 412 and 1768 Ä p. 415) must be entered as
Line-Line (Delta) and the busbar 1 rated voltage (parameter 1781 Ä p. 415)
must be entered as Line-Neutral (WYE).
For information on measuring principles refer to Ä Chapter 3.3.5.1 “Generator
Voltage” on page 51.
1850 Generator cur‐ 2 [L1 L2 L3 ] All three phases are monitored. Measurement, display and protection are
rent measuring adjusted according 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, display and protection are
adjusted according to the rules for single-phase measurement.
Monitoring refers to the selected phase.
Notes
This parameter is only effective if generator voltage measuring (param‐
eter 1851 Ä p. 413) is configured to "3Ph 4W" or "3Ph 3W".
For information on measuring principles refer to Ä Chapter 3.3.6.1 “Generator
Current” on page 66.
1801 Gen. PT pri‐ 2 50 to 650000 V Some generator applications may require the use of potential transformers to
mary rated facilitate measuring the voltages produced by the generator. The rating of the
voltage [400 V] primary side of the potential transformer must be entered into this parameter.
(Generator If the application does not require potential transformers (i.e. the measured
potential trans‐ voltage is 480 V or less), then the measured voltage will be entered into this
former primary parameter.
voltage rating)
1800 Gen. PT secon‐ 2 50 to 480 V Some generator applications may require the use of potential transformers to
dary rated volt. facilitate measuring the voltages produced by the generator. The rating of the
[400 V] secondary side of the potential transformer must be entered into this param‐
(Generator eter.
potential trans‐
former secon‐ If the application does not require potential transformers (i.e. the measured
dary voltage voltage is 480 V or less), then the measured voltage will be entered into this
rating ) parameter.
1806 Gen. CT pri‐ 2 1 to 32000 A/x The input of the current transformer ratio is necessary for the indication and
mary rated cur‐ control of the actual monitored value.
rent [500 A/x]
Notes
(Generator cur‐
rent transformer The current transformers ratio should be selected so that at least 60% of the
primary rating) 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 cur‐ 2 1A The input range of the current transformer must be selected/defined.
rent range
[5 A]
4.6.3 Busbar
1781 Busbar 1 rated 2 50 to 650000 V This value refers to the rated voltage of busbar 1 and is the voltage measured
voltage on the potential transformer primary.
[400 V]
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 param‐
eter. 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 2 0 to 30% If the busbar voltage falls below this percentage of the busbar 1 rated voltage
detection max. (parameter 1781 Ä p. 415), a dead bus condition is detected and the logical
volt. [10%] command variable 02.21 (Busbar 1 is dead) becomes TRUE.
1813 Busb1 PT pri‐ 2 50 to 650000 V Some applications may require the use of potential transformers to facilitate
mary rated measuring the voltages to be monitored. The rating of the primary side of the
voltage [400 V] potential transformer must be entered into this parameter.
(Busbar 1 Notes
potential trans‐
former primary If the application does not require potential transformers (i.e. the measured
voltage rating ) voltage is 480 V or less), then the measured voltage will be entered into this
parameter.
1812 Busb1 PT sec‐ 2 50 to 480 V Some applications may require the use of potential transformers to facilitate
ondary rated measuring the busbar voltages. The rating of the secondary side of the poten‐
volt. [400 V] tial transformer must be entered into this parameter.
(Busbar 1 If the application does not require potential transformers (i.e. the measured
potential trans‐ voltage is 480 V or less), then the measured voltage will be entered into this
former secon‐ parameter.
dary voltage
rating )
4.6.4 Mains
ID Parameter CL Setting range Description
[Default]
1768 Mains rated 2 50 to 650000 V This value refers to the rated voltage of the mains and is the voltage meas‐
voltage ured on the potential transformer primary.
[400 V]
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 moni‐
toring, breaker operation windows or the AnalogManager.
1748 Mains rated 2 0.5 to 99999.9 This value specifies the mains real power rating, which is used as a reference
active power kW figure for related functions. The mains rated active power is a reference value
[kW] used by several monitoring and control functions ( Ä “Dependencies”
[200.0 kW] on page 411).
1746 Mains rated 2 0.5 to 99999.9 This value specifies the mains reactive power rating, which is used as a refer‐
react. pwr. kvar ence figure for related functions.
[kvar]
[200.0 kvar] The mains rated reactive power is a reference value used by several moni‐
toring and control functions( Ä “Dependencies” on page 411).
1785 Mains rated 2 1 to 32000 A This value specifies the mains rated current, which is used as a reference
current figure for related functions.
[300 A]
1853 Mains voltage 2 [3Ph 4W] Measurement is performed Line-Neutral (WYE connected system) and Line-
measuring Line (Delta connected system). The protection depends on the setting of
parameter 1771 Ä p. 346.
Phase voltages and the neutral must be connected for proper calculation.
Measurement, display and protection are adjusted according to the rules for
WYE connected systems.
Monitoring refers to the following voltages:
n VL1N, VL12
Notes
If this parameter is configured to 1Ph 3W, the generator and mains rated vol‐
tages (parameters 1766 Ä p. 412 and 1768 Ä p. 415) must be entered as
Line-Line (Delta) and the busbar 1 rated voltage (parameter 1781 Ä p. 415)
must be entered as Line-Neutral (WYE).
1852 Mains current 2 [Phase L1] / Phase L{1/2/3} Measurement is performed for the selected phase only. The
measuring Phase L2 / measurement and display refer to the selected phase.
Phase L3
The configured phase CT must be connected to perform current measure‐
ment.
Notes
For information on measuring principles refer to Ä Chapter 3.3.6.2 “Mains
Current” on page 68.
This parameter is only effective if mains voltage measuring (param‐
eter 1853 Ä p. 416) is configured to "3Ph 4W" or "3Ph 3W".
1804 Mains PT pri‐ 2 50 to 650000 V Some applications may require the use of potential transformers to facilitate
mary rated measuring the voltages to be monitored. The rating of the primary side of the
voltage [400 V] potential transformer must be entered into this parameter.
(Mains potential Notes
transformer pri‐
mary voltage If the application does not require potential transformers (i.e. the measured
rating voltage is 480 V or less), then the measured voltage will be entered into this
parameter.
1803 Mains PT sec‐ 2 50 to 480 V Some applications may require the use of potential transformers to facilitate
ondary rated measuring the mains voltages. The rating of the secondary side of the poten‐
volt. [400 V] tial transformer must be entered into this parameter.
(Mains potential If the application does not require potential transformers (i.e. the measured
transformer sec‐ voltage is 480 V or less), then the measured voltage will be entered into this
ondary voltage parameter.
rating)
1807 Mains CT pri‐ 2 1 to 32000 A/x The input of the current transformer ratio is necessary for the indication and
mary rated cur‐ control of the actual monitored value.
rent [500 A/x]
The current transformers ratio should be selected so that at least 60% of the
(Mains current secondary current rating can be measured when the monitored system is at
transformer pri‐ 100% of operating capacity (i.e. at 100% of system capacity a 5 A CT should
mary rating) 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 parameter 1854 Ä p. 411 is configured as Mains.
1832 Mains current 2 1A The input range of the current transformer must be selected/defined.
range
[5 A] Notes
This screen is only visible if parameter 1854 Ä p. 411 is configured as Mains.
2966 External mains 2 Yes The mains active power is coming from an external source.
active power
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 Ä p. 419) is disabled:
Notes
Mains power monitoring is not available.
Please make sure to assign the external mains active power to the corre‐
sponding analog data source (parameter 5780 Ä p. 418/Ä p. 885). The same
data source must be used if the mains active power is requested via interface.
5780 AM Ext.mains 2 Determined by Typically an analog input is selected as data source which is connected to an
act.pwr AnalogManager external transducer.
81.19: [A1 =
06.01 Analog
input 1]
2967 Mains power 2 This parameter controls the resolution and the format.
meas. resolu‐
tion Selected resolu‐ Power at 100% analog value
tion
(Mains power
measurement 0.01 kW 10.00 kW
resolution)
0.1 kW 100.0 kW
[1 kW] 1000 kW
0.01 MW 10.00 MW
0.1 MW 100.0 MW
2969 External mains 2 Yes The mains reactive power is coming from an external source. This power is
reactive power displayed and used for control purposes. The source is taken via AnalogMan‐
ager.
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 power measurement (parameter
2966 Ä p. 418) is disabled:
Notes
Mains power monitoring is not available.
Please make sure to assign the external mains reactive power to the corre‐
sponding analog data source (parameter 5794 Ä p. 419/Ä p. 885). The same
data source must be used if the mains active power is requested via interface.
5794 AM Ext.mains 2 Determined by Typically an analog input is selected as data source (kvar value) which is con‐
RPower AnalogManager nected to an external transducer.
81.20: [A1 =
06.02 Analog
input 2]
2970 Mains react. 2 This parameter controls the resolution and the format.
power meas.
resolution Selected resolu‐ Power at 100% analog value:
tion:
(Mains reactive
power measure‐ 0.01 kvar 10.00 kvar
ment resolution)
0.1 kW 100.0 kvar
4.6.5 Engine
ID Parameter CL Setting range Description
[Default]
1601 Engine rated 2 100 to 4,000 Number of revolutions per minute of the engine at rated engine speed. The
speed rpm speed control with an ECU via J1939 CAN bus refers to this value.
[1,500 rpm]
3170 Baudrate 2 2.4 / 4.8 / 9.6 / This parameter defines the baud rate for communications. Please note, that
[19.2] / 38.4 / all participants on the bus must use the same baud rate.
56 / 115 kBaud
3171 Parity 2 [No] / Even / The used parity of the interface is set here.
Odd
3172 Stop bits 2 [One] / Two The number of stop bits is set here.
Modbus Interface
3188 ModBus Slave 2 0 to 255 The Modbus device address, which is used to identify the device via Modbus,
ID is entered here.
[1]
If "0" is configured here, the Modbus is disabled.
3189 Reply delay 2 0.00 to 2.55 s This is the minimum delay time between a request from the Modbus master
time and the sent response of the slave. This time is required in half-duplex mode.
[0.00 s]
9128 Password pro‐ 5 Off Password protection for Modbus RS 485 is not active.
tection
Notes
Take care for a protected access!
Data Format(s)
Modbus registers are read and written according to
the Modbus standard as Big-endian.
Composite data types like LOGMAN, ANALOG‐
MANAGER, and TEXT use separate descriptions.
3184 Modbus pro‐ 2 0 to 65535 A Modbus protocol may be selected by entering the data protocol ID here. If
tocol number 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” software to create your own Data Tele‐
grams.
Notes
Another protocol can be used after power-cycle of the control:
Change Modbus protocol number first, then power cycle!
Notes
All Date Telegrams described in this Technical Manual are device imple‐
mented: no separate scp-file (e.g. "5010.scp") needed.
3179 Detect a gap in 2 [On] If a received Modbus command has a gap between its byte of more than 5
a Modbus ms, this command is ignored.
frame
Off The Modbus message is not checked.
3181 Power [W] 2 2 to 5 This setting adjusts the format of the 16 bit power values in the data telegram.
exponent 10^x
[3]
Notes
Valid for data telegram 5010 only!
Refer to Ä “Power measurement example” on page 423 for examples.
3182 Voltage [V] 2 -1 to 2 This setting adjusts the format of the 16 bit voltage values in the data tele‐
exponent 10^x gram.
[0]
Notes
Valid for data telegram 5010 only!
Refer to Ä “Voltage measurement example” on page 423 for examples.
3183 Current [A] 2 -1 to 0 This setting adjusts the format of the 16 bit current values in the data tele‐
exponent 10^x gram.
[0]
Notes
Valid for data telegram 5010 only!
Refer to Ä “Power measurement example” on page 423 for examples.
Select standard or customized In many applications customers ask for self-definable protocols.
Data Protocol with parameter That means they want to create individual Modbus Address Point
3184 “Modbus protocol number” lists for Modbus RTU, TCP, and UDP. 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. Therefore Woodward offers the Telegram‐
Mapper software for free and enables easYgen-XT to import,
make accessible, and proceed customer specific Modbus proto‐
cols.
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 from ...
n the AnalogManager variables,
n the LogicsManager command variables,
n and the easYgen database ...
of the particular easYgen model will be available/selectable.
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
n SCP-file for import into the easYgen device
n HTML-file for easy to read documentation of the (self) cre‐
ated data protocol
n 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 Ä p. 421 “Modbus protocol number”
to your customer specific protocol number and power cycle 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
5003, 5011 etc. (“Parameter
è Configuration/Configure interfaces è Modbus protocol”).
29 X N/A
28-11 0 Always
TIME synchronization message CANopen COB-ID TIME Time applied Time trans‐
master mitted
On Bit 30 = 0; Bit 31 = 0 No No
3156 Baudrate 2 20 / 50 / 100 / This parameter defines the used baud rate. Please note, that all participants
125 / 250 / 500 / on the CAN bus must use the same baud rate.
800 / 1000
kBaud
[250 kBd]
1894 Align device 2 No If this parameter is configured to "Yes" the parameter “Node-ID CAN bus 1”
no. with Node- 8950 Ä p. 425 will be overwritten with the value of the “Device
ID [Yes] number ” 1702 Ä p. 155 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 2 1 to 127 (dec) A number that is unique to the control must be set in this parameter so that
bus 1 this control unit can be correctly identified on the CAN bus.
[1]
This address number may only be used once on the CAN bus. All 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 2 One bus participant must take over the network management and put the
Master other participants into "operational" mode. The easYgen is able to perform
this task.
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 opera‐
tional mode.
Notes
If this parameter is configured to "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 2 0 to 65500 ms Independent from the CANopen Master configuration, the unit transmits a
heartbeat time heartbeat message with this configured heartbeat cycle time.
[2000 ms]
If the producer heartbeat time is equal 0, the heartbeat will only be sent as
response to a remote frame request. The time configured here will be
rounded up to the next 20 ms step.
9100 COB-ID SYNC 2 1 to FFFFFFFF This parameter defines whether the unit generates the SYNC message or
Message hex not.
[80 hex] The message complies with CANopen specification: object 1005 hex; sub‐
index 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”
on page 424
8940 Producer 2 0 to 65000 ms This is the cycle time of the SYNC message. If the unit is configured for this
SYNC Message function (parameter 9100 Ä p. 425) it will send the SYNC message with this
time [20 ms] interval. The time configured here will be rounded up to the next 10 ms step.
9101 COB-ID TIME 2 1 to FFFFFFFF This parameter defines whether the unit generates the TIME message or not.
Message hex
Complies with CANopen specification: object 1012 hex, subindex 0; defines
[100 hex] the COB-ID of the time object (TIME).
Notes
The structure of this object is shown in Ä “COB-ID of SYNC/TIME messages”
on page 424
9102 Cycle of TIME 2 1.0 to 6500.0 s This is the cycle time of the TIME message. If the unit is configured for this
sync. message function (parameter 9101 Ä p. 426) it will send the TIME message with this
[10.0 s] interval.
Notes
The structure of this object is shown in Ä “TIME synchronization message”
on page 424
9126 Password pro‐ 5 Off Password protection for CAN 1 is not active.
tection
Notes
Take care for a protected access!
12801 2. Node-ID 2 0 to 127 (dec) In a multi-master application, each Master needs its own identifier (Node-ID)
from the unit. in order to send remote signals (i.e. remote start, stop, shut‐
[0] down, 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.
12802 3. Node-ID 2 0 to 127 (dec) In a multi-master application, each Master needs its own identifier (Node-ID)
from the unit. in order to send remote signals (i.e. remote start, stop, shut‐
[0] down, 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.
12803 4. Node-ID 2 0 to 127 (dec) In a multi-master application, each Master needs its own identifier (Node-ID)
from the unit. in order to send remote signals (i.e. remote start, stop, shut‐
[0] down, 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.
12804 5. Node-ID 2 0 to 127 (dec) In a multi-master application, each Master needs its own identifier (Node-ID)
from the unit. in order to send remote signals (i.e. remote start, stop, shut‐
[0] down, 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.
Parameters
9300 Ä p. 428/9310 Ä p. 428/9320 Ä p.
428/12805 Ä p. 428/12806 Ä p. 428 use commu‐
nication parameters that adhere to the following
structure.
RPDO Objects can be remote signals (parameter
503; please refer to Ä “Remote control word 1”
on page 804 for details), DI states and AI meas‐
ured values.
30 X N/A
29 X N/A
28-11 0 Always
9300 COB-ID 2 1 to FFFFFFFF This parameter contains the communication parameters for the PDOs, the
hex device is able to receive.
9310
[80000000 hex] Complies with CANopen specification: object 1400 hex (for RPDO 1, 1401
9320 hex for RPDO 2, 1402 hex for RPDO 3, 1403 hex for RPDO 4, and 1404 hex
12805 for RPDO 5), subindex 1.
12806 Notes
The structure of this object is shown in Ä Further information on page 427.
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 marked as "not
existing". The time configured here will be rounded up to the next 5 ms step.
9122 [2000 ms] Received messages are processed by the control unit every 20 ms. Mes‐
9123 sages, which are sent faster, will be discarded. We recommend to configure
ten times the cycle time of the received data here.
9124
Notes
9125
Complies with CANopen specification: object 1400 hex (for RPDO 1, 1401
hex for RPDO 2, 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 by entering the data protocol ID here. If 0 is
Protocol configured here, the message assembled by the mapping parameters is
8971 [0] used. If an unknown data protocol ID is configured here, a failure is indicated
8972 by the CAN status bits. Possible data protocol IDs are:
65002
65003
9910 Number of 2 0 to 4 This parameter defines the number of valid entries within the mapping record.
Mapped This number is also the number of the application variables, which shall be
9915 Objects [0] received with the corresponding PDO.
9905
Notes
12821
Complies with CANopen specification: object 1600 hex (for RPDO 1, 1601
12831 hex for RPDO 2, 1602 hex for RPDO 3, 1603 hex for RPDO 4, and 1604 hex
for RPDO 5), subindex 0
9911 1. Mapped 2 0 to 65535 This parameter contains the information about the mapped application varia‐
Object bles. These entries describe the PDO contents by their index. The sub-index
9916 [0] is always 1. The length is determined automatically.
9906
Notes
12822
Complies with CANopen specification: object 1600 hex (for RPDO 1, 1601
12832 hex for RPDO 2, 1602 hex for RPDO 3,1603 hex for RPDO 4, and 1604 hex
for RPDO 5), subindex 1.
9912 2. Mapped 2 0 to 65535 This parameter contains the information about the mapped application varia‐
Object bles. These entries describe the PDO contents by their index. The sub-index
9917 [0] is always 1. The length is determined automatically.
9907
Notes
12823
Complies with CANopen specification: object 1600 hex (for RPDO 1, 1601
12833 hex for RPDO 2, 1602 hex for RPDO 3, 1603 hex for RPDO 4, and 1604 hex
for RPDO 5), subindex 2.
9913 3. Mapped 2 0 to 65535 This parameter contains the information about the mapped application varia‐
Object bles. These entries describe the PDO contents by their index. The sub-index
9918 [0] is always 1. The length is determined automatically.
9908
Notes
12824
Complies with CANopen specification: object 1600 hex (for RPDO 1, 1601
12834 hex for RPDO 2, 1602 hex for RPDO 3, 1603 hex for RPDO 4, and 1604 hex
for RPDO 5), subindex 3.
9914 4. Mapped 2 0 to 65535 This parameter contains the information about the mapped application varia‐
Object bles. These entries describe the PDO contents by their index. The sub-index
9919 [0] is always 1. The length is determined automatically.
9909
Notes
12825
Complies with CANopen specification: object 1600 hex (for RPDO 1, 1601
12835 hex for RPDO 2, 1602 hex for RPDO 3, 1603 hex for RPDO 4, and 1604 hex
for RPDO 5), subindex 4.
Parameters
9600 Ä p. 430/9610 Ä p. 430/9620 Ä p.
430/9630 Ä p. 430/12792 Ä p. 430 use communi‐
cation parameters that adhere to the following
structure.
30 X N/A
29 X N/A
28-11 0 Always
Transmission types
Parameters
9602 Ä p. 431/9612 Ä p. 431/9622 Ä p.
431/9632 Ä p. 431/12793 Ä p. 431 are used to
select one of the following transmission types.
1-240 X X
254 X
255 X
9600 COB-ID 2 1 to FFFFFFFF This parameter contains the communication parameters for the PDOs the unit
hex is able to transmit. The unit transmits data (i.e. visualization data) on the CAN
9610 ID configured here.
[80000000 hex]
9620 Complies with CANopen specification: object 1800 hex for (TPDO 1, 1801
9630 hex for TPDO 2, 1802 hex for TPDO 3, 1803 hex for TPDO 4, and 1804 hex
for TPDO 5), subindex 1.
12792
Notes
The structure of this object is shown in Ä Further information on page 429
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 2 0 to 255 This parameter contains the communication parameters for the PDOs the unit
type is able to transmit. It defines whether the unit broadcasts all data automati‐
9612 [255] cally (value 254 or 255) or only upon request with the configured address of
9622 the COB-ID SYNC message (parameter 9100 Ä p. 425).
9632 Notes
12793 Complies with CANopen 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 2.
The description of the transmission type is shown in Ä “Transmission types”
on page 430.
9604 Event timer 2 0 to 65535 ms This parameter contains the communication parameters for the PDOs the unit
is able to transmit. The broadcast cycle for the transmitted data is configured
9614 [20 ms] here. The time configured here will be rounded up to the next 5 ms step.
9624
Notes
9634
Complies with CANopen specification: object 1800 hex (for TPDO 1, 1801
12794 hex for TPDO 2, 1802 hex for TPDO 3, 1803 hex for TPDO 4, and 1804 hex
for TPDO 5), subindex 5
8962 Selected Data 2 0 to 65535 A data protocol may be selected by entering the data protocol ID here. If 0 is
Protocol configured here, the message assembled by the mapping parameters is
8963 8962: [5003] used. If an unknown data protocol ID is configured here, a failure is indicated
8964 8963: [5008] by the CAN status bits.
9609 Number of 2 0 to 4 This parameter contains the mapping for the PDOs the unit is able to
Mapped transmit. This number is also the number of the application variables, which
9619 Objects [0] shall be transmitted with the corresponding PDO.
9629
Notes
9639
Complies with CANopen specification: object 1A00 hex (for TPDO 1, 1A01
12799 hex for TPDO 2, 1A02 hex for TPDO 3, 1A03 hex for TPDO 4, and 1A04 hex
for TPDO 5), subindex 0
9605 1. Mapped 2 0 to 65535 This parameter contains the information about the mapped application varia‐
Object bles. These entries describe the PDO contents by their index. The sub-index
9615 [0] is always 1. The length is determined automatically.
9625
Notes
9635
Complies with CANopen specification: object 1A00 hex (for TPDO 1, 1A01
12795 hex for TPDO 2, 1A02 hex for TPDO 3, 1A03 hex for TPDO 4, and 1A04 hex
for TPDO 5), subindex 1
9606 2. Mapped 2 0 to 65535 This parameter contains the information about the mapped application varia‐
Object bles. These entries describe the PDO contents by their index. The sub-index
9616 [0] is always 1. The length is determined automatically.
9626
Notes
9636
Complies with CANopen specification: object 1A00 hex (for TPDO 1, 1A01
12796 hex for TPDO 2, 1A02 hex for TPDO 3, 1A03 hex for TPDO 4, and 1A04 hex
for TPDO 5), subindex 2
9607 3. Mapped 2 0 to 65535 This parameter contains the information about the mapped application varia‐
Object bles. These entries describe the PDO contents by their index. The sub-index
9617 [0] is always 1. The length is determined automatically.
9627
Notes
9637
Complies with CANopen specification: object 1A00 hex (for TPDO 1, 1A01
12797 hex for TPDO 2, 1A02 hex for TPDO 3, 1A03 hex for TPDO 4, and 1A04 hex
for TPDO 5), subindex 3
9608 4. Mapped 2 0 to 65535 This parameter contains the information about the mapped application varia‐
Object bles. These entries describe the PDO contents by their index. The sub-index
9618 [0] is always 1. The length is determined automatically.
9628
Notes
9638
Complies with CANopen specification: object 1A00 hex (for TPDO 1, 1A01
12798 hex for TPDO 2, 1A02 hex for TPDO 3, 1A03 hex for TPDO 4, and 1A04 hex
for TPDO 5), subindex 4
General Settings
ID Parameter CL Setting range Description
[Default]
3157 Baudrate 2 20 / 50 / 100 / This parameter defines the used baud rate.
125 / 250 kBaud
Notes
[250 kBd]
All participants on the CAN bus must use the same baud rate.
Select # of 1st Node-ID 2nd Node-ID 3rd Node-ID 4th Node-ID 5th Node-ID 6th Node-ID
external ter‐
minals terminals: I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
Select # of 1st Node-ID 2nd Node-ID 3rd Node-ID 4th Node-ID 5th Node-ID 6th Node-ID
external ter‐
minals terminals: I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
Table 97: Assignment of selectable Combinations CAN 2 (Node 1-6) used for DI/DO: Digital Inputs and Dig‐
ital Outputs, only
Select # of 1st Node-ID 2nd Node-ID 3rd Node-ID 4th Node-ID 5th Node-ID 6th Node-ID
external ter‐
minals terminals: I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
Table 98: Assignment of selectable Combinations CAN 2 (Node 1-6) used for AI/AO: Analog Inputs and
Analog Outputs, only
Select # of 1st Node-ID 2nd Node-ID 3rd Node-ID 4th Node-ID 5th Node-ID 6th Node-ID
external ter‐
minals terminals: I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
Select # of 1st Node-ID 2nd Node-ID 3rd Node-ID 4th Node-ID 5th Node-ID 6th Node-ID
external ter‐
minals terminals: I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
Select # of 1st Node-ID 2nd Node-ID 3rd Node-ID 4th Node-ID 5th Node-ID 6th Node-ID
external ter‐
minals terminals: I/O ID 9930 ID 9931 ID 9932 ID 9933 ID 9934 ID 9935
ID 15320
Table 99: Assignment of selectable Combinations CAN 2 (Node 1-6) used for DI/DO/AI/AO: Combinations of
the expansion modules
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 devices.
[Node-ID 1] Parameter 15320 Ä p. 437 "Select external terminals" offers often used pre-
settings and the possibility to point to a file containing customer specific set‐
9931 2nd Node-ID 2 Node-ID 1-126 tings.
[Node-ID 2]
Ext. term file File defined with parameter 15318 Ä p. 438 is active.
4IKD
P16D
P32D
P16D_16D
P16AI4AO
1IKD_
P16AI4AO
2IKD_
P16AI4AO
3IKD_
P16AI4AO
4IKD_
P16AI4AO
P16D_16AI4AO
P16D16AI4AO
P32D16AI4AO
2P16D_16AI4A
O
P32D_16AI4AO
W16AI4AO
1IKD_W16AI4A
O
2IKD_W16AI4A
O
3IKD_W16AI4A
O
4IKD_W16AI4A
O
W16D
W32D
W16D16AI4AO
W32D16AI4AO
15318 Sequencer file‐ 2 [Filename.seq] Filename of a special additional file to define external devices (see NOTE
name Ä Further information on page 432).
Notes
This parameter takes only effect if parameter 15320 Ä p. 437 is configured to
“Ext.term.file”.
Please ask your Woodward partner for support / an offer.
15134 Configure 2 Yes This parameter starts the configuration of external Phoenix expansion boards.
external
devices [No] 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:
n Set the new NODE-ID via DIP switches
n Load default values (via a temporary change in number or kind
of Wago modules-run configuration again.
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.
Thermocouple device (750-458) for There is no intuitive setting in the easYgen-XT if a channel of the
voltage measurement 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:
15166 J1939 2 Off The J1939 interface is disabled. No messages will be received or transmitted.
15102 Device type 2 The J1939 interface of this device may be operated with different engine con‐
trol 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 repowering the devices!
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, Cat‐
erpillar, Liebherr, etc.).
Please refer to Ä Chapter 7.6 “ J1939 Protocol” on page 578 for details
and/or ask your local Woodward partner for an offer.
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: J1939 data according to the SAE J1939
standard and some EMS2-specific data are considered.
This setting is also recommended for Volvo EDC3 and EMS1.
ADEC ECU7 MTU The MTU ADEC ECU7 with SAM is enabled: J1939 data according to the
SAE J1939 standard and some 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 enabled: J1939 data according to the
SAE J1939 standard and some EDC-specific data are considered.
EEM SISU The SISU EEM2/3 ECU is enabled: J1939 data according to the SAE J1939
standard and some EEM2/3-specific data are considered.
Cummins The Cummins ECU is enabled: J1939 data according to the SAE J1939
standard and some Cummins-specific data are considered.
This setting is also recommended 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/ The MTU ADEC ECU8 with SmartConnect or the MTU ADEC ECU9 is ena‐
ECU9 MTU bled: J1939 data according to the SAE J1939 standard and some ADEC-spe‐
cific data are considered.
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 2 0 to 255 The easYgen sends J1939 request and control messages with this source
address address. It must be changed for different ECU types according to the fol‐
[234] lowing table. The ECU listens only to control messages, if they are sent to the
correct address.
n S6 Scania: 39
n EMR2 Deutz: 3
n EMS2 Volvo: 17
n ADEC ECU7 MTU: 1
n EGS Woodward: 234
n MFR/EDC7 MAN: 253
n EEM SISU: N/A
n Cummins: 220
n ADEC ECU8/ECU9 MTU: 234
n Standard: Please refer to Ä Chapter 7.6 “ J1939 Protocol” on page 578
and to the manual of your J1939 ECU manufacturer.
Details may be found in the manual of the genset control and in Ä Chapter
7.6 “ J1939 Protocol” on page 578.
Notes
Changing this parameter becomes only effective after restarting the unit.
15107 Engine control 2 0 to 255 Configures the address of the J1939 device, which is controlled. The
address easYgen sends J1939 request and control messages with this destination
[0] address.
n S6 Scania: 0
n EMR2 Deutz: 0
n EMS2 Volvo: 0
n ADEC ECU7 MTU: 128
n EGS Woodward: 0
n MFR/EDC7 MAN: 39
n EEM SISU: 0/(1)
n Cummins: 0
n ADEC ECU8/ECU9 MTU: 0
n Standard: Please refer to Ä Chapter 7.6 “ J1939 Protocol” on page 578
and to the manual of your J1939 ECU manufacturer.
Details may be found in the manual of the genset control and in Ä Chapter
7.6 “ J1939 Protocol” on page 578.
15108 Reset previous 2 Yes If this parameter is set to "Yes", a DM3 message "Acknowledge passive
act. DTCs - faults" is sent. After that this parameter is reset automatically to "No".
DM3 [No]
As a result the alarms DTCs (Diagnostic Trouble Codes) of (DM2) which no
longer apply are cleared.
15133 Reset act. 2 Yes If this parameter is set to "Yes", a DM11 message "Acknowledge active
DTCs - DM11 faults" is sent. After that this parameter is reset automatically to "No".
[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 conversion method of
the Suspect Parameter Number (SPN). This is important for a correct inter‐
[Version 1] pretation of the alarm messages (DM1 & DM2).
This parameter defines the version of the conversion method: Version 1, Ver‐
sion 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 messages to the ECU. Depending on the
controlled selected device type (parameter 15102 Ä p. 440), contains a specific selec‐
tion of commands.
[Off] The ECU remote control via the J1939 protocol will be disabled.
Notes
The unit sends J1939 control messages to the ECU. Depending on the
selected device type (parameter 15102 Ä p. 440), it contains a specific selec‐
tion 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 Ä Chapter 7.6 “ J1939 Protocol” on page 578 for more detailed infor‐
mation.
5537 Speed devia‐ 2 0 to 1,400 rpm This parameter adjusts the range of the speed deviation around the rated
tion ECU speed, which is sent to the ECU.
[120 rpm]
It relates to the engine rated speed (parameter 1601 Ä p. 419).
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 Ä p. 249 for the
initial state between 0 and 100%, the engine should change the speed as fol‐
lows:
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 Ä p. 249 for the
initial state between 0 and 100%, the engine should change the speed as fol‐
lows:
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 this case, real
power control must be disabled in the easYgen.
This parameter is only visible if ECU remote controlled (param‐
eter 15127 Ä p. 442) is configured to "On".
Notes
For details please refer to the manual of your J1939 ECU manufacturer.
This parameter is only visible if "Device type" (parameter 15102 Ä p. 440) is
configured to "ADEC ECU8 MTU" and "ECU remote controlled" (parameter
15127 Ä p. 442) is configured to "On".
12939 ECU Power 2 [Low power Prepared for MTU - Low mode
Mode mode]
Notes
For details please refer to the manual of your J1939 ECU manufacturer.
This parameter is only visible if "Device type" (parameter 15102 Ä p. 440) is
configured to "ADEC ECU8 MTU" and "ECU remote controlled" (parameter
15127 Ä p. 442) is configured to "On".
15164 ECU seq. 2 Determined by This LogicsManager is prepared to pass binary information to the ECU via
B_IN_1 LogicsManager J1939.
86.31
If this LogicsManager is used by an ECU its function will be described in the
[(0 & 1) & 1] manual of the corresponding J1939 ECU. For more information please see
J1939 ECU description.
= 11647
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
15165 ECU seq. 2 Determined by This LogicsManager is prepared to pass binary information to the ECU via
B_IN_2 LogicsManager J1939.
86.32
If this LogicsManager is used by an ECU its function will be described in the
[(0 & 1) & 1] manual of the corresponding J1939 ECU. For more information please see
J1939 ECU description.
= 11648
Notes
For information on the LogicsManager and its default settings see Ä Chapter
9.3.1 “LogicsManager Overview” on page 811.
15162 AM ECU seq. 2 Determined by This AnalogManager is prepared to pass analog information to the ECU via
A_IN_1 AnalogManager J1939.
81.22
If this AnalogManager is used by an ECU its function will be described in the
[A1 = 10.01 manual of the corresponding J1939 ECU. For more information please see
ZERO] J1939 ECU description.
Notes
Refer to Ä Chapter 4.9 “Configure AnalogManager” on page 452 for explana‐
tion how to use the AnalogManager.
Refer to Ä Chapter 9.4.1 “Data Sources AM” on page 856 for a list of all data
sources.
15163 AM ECU seq. 2 Determined by This AnalogManager is prepared to pass analog information to the ECU via
A_IN_2 AnalogManager J1939.
81.23
If this AnalogManager is used by an ECU its function will be described in the
[A1 = 10.01 manual of the corresponding J1939 ECU. For more information please see
ZERO] J1939 ECU description.
Notes
Refer to Ä Chapter 4.9 “Configure AnalogManager” on page 452 for explana‐
tion how to use the AnalogManager.
Refer to Ä Chapter 9.4.1 “Data Sources AM” on page 856 for a list of all data
sources.
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 messages that
2 to 10 can be lost before it is detected as "connection missing".
7485 Modbus/TCP Slave ID 2 [1] Your local Modbus device address, which is used to identify
the device via Modbus/TCP (Ethernet), must be entered
1 to 255 here.
9129 Password protection 5 Off Password protection for Ethernet is not active.
Notes
Take care for a protected access!
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 num‐
bers.
Gateway IP address
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.
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 address” parameter
5331 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).
5334 Subnet mask 2 [255, 255, 240, 0] Set byte 1,2,3,4 of the subnet mask Ethernet port A. This set‐
ting will be not valid automatically. The “Set subnet mask”
5335 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 address”
5339 parameter must be set to [ON] for enabling. If 0.0.0.0 is set,
5340 the gateway's functionality is switched off.
5341
5342 Set Gateway IP 2 Off Set Gateway IP Address for Ethernet port A
address
4.7.6.2 SNTP
SNTP feature The Simple Network Time Protocol (SNTP) is a common proce‐
dure 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.
HEX values
The addresses and subnet masks are known as
hex values but are displayed in HMI and ToolKit as
decimal values.
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 on the function.
30 to 600
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
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.
9921 Transfer rate 2 0.10 to 0.30 s The transfer rate defines the time delay between two fast CAN messages.
LS fast mes‐
sage [0.10 s] 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
(CAN) reduce the bus load.
9920 Load Share 2 2xx hex / 3xx The first digit of the CAN ID or the range (i.e. 2xx means 200 through 2FF
CAN-ID hex / 4xx hex / hex) is configured here.
5xx hex
The last two digits will be assigned by the control with the settings from the
[5xx hex] device number (parameter 1702 Ä p. 155).
4117 Use ASA sym‐ 2 Yes Symbols according to the ASA standard are used in LogicsManager screens.
bols
[No] Symbols according to the IEC standard are used in LogicsManager screens.
Internal flags Internal flags within the LogicsManager logical outputs may be pro‐
grammed and used for multiple functions.
Flag {x} Flag 1 Flag 2 Flag 3 Flag 4 Flag 5 Flag 6 Flag 7 Flag 8
Flag {x} Flag 9 Flag 10 Flag 11 Flag 12 Flag 13 Flag 14 Flag 15 Flag 16
Flag {x} Flag 17 Flag 18 Flag 19 Flag 20 Flag 21 Flag 22 Flag 23 Flag 24
Flag {x} Flag 25 Flag 26 Flag 27 Flag 28 Flag 29 Flag 30 Flag 31 Flag 32
{yyyyy} Flag {x} 2 Determined by The flags may be used as auxiliary flags for complex combinations by using
LogicsManager the logical output of these flags as command variable for other logical out‐
{XX.XX} puts.
[(0 & 1) & 1] Notes
= {nnnnn} 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 Logi‐
csManager equation
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] n 0 = 0th hour of the day (midnight).
n 23 = 23rd hour of the day (11pm).
1651 Timer {x}: 2 0 to 59 min Enter the minute of the daily time setpoint here.
Minute
1656 [0 min] Example
1650 Timer {x}: 2 0 to 59 s Enter the second of the daily time setpoint here.
Second
1655 [0 s] Example
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
1662 Active hour 2 0 to 23 h Enter the hour of the active switch point here.
[12 h] The active time setpoint is enabled every day during the indicated hour from
minute 0 to minute 59.
Example
1661 Active minute 2 0 to 59 min Enter the minute of the active switch point here.
[0 min] The active time setpoint is 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] The active time setpoint is enabled every minute during the indicated second.
Example
1670 Monday active 2 [Yes] The switch point is enabled every Monday.
1671 Tuesday active 2 [Yes] The switch point is enabled every Tuesday.
1674 Friday active 2 [Yes] The switch point is enabled every Friday.
1676 Sunday active 2 Yes The switch point is enabled every Sunday.
AnalogManager Description
Acronym Name Value
C1 Analog Constant input (constant) defined via HMI, ToolKit, or other (remote) interface
Notes
Type AnalogManager type (operation) selected via HMI, ToolKit, or other (remote) interface
Notes
Available as LogicsManager Variable ("result") e.g. as AM/LM input
Notes
Available as AnalogManager "result" e.g. as AM input
AnalogManager Internal Values 1 to Internal values within the AnalogManager analogue and logical
16 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
Value {x} Value 9 Value 10 Value 11 Value 12 Value 13 Value 14 Value 15 Value 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".
{yyyyy} AM Internal 2 Determined by The data source may be selected from the available data sources.
Value {x} AnalogManager
Notes
[A1 = 10.01
ZERO] Refer to Ä Chapter 9.4.1 “Data Sources AM” on page 856 for a list of all data
sources.
{yyyyy} Internal value 2 user-defined (up The text may have 0 through 22 characters.
{x}: Descrip‐ 22 to charac‐
tion ters) Notes
[AM Internal This parameter may only be configured using ToolKit.
Value {x}]
The max. number of characters depends on the numbers of Bytes for each
character.
Please verify the length on the display for best view.
Examples
Value: 65.1252
Value: 25.2360
Name: LM FALSE
Value: 0
Name: LM FALSE
Value: 0
Value: 25.0000
Name: ZERO
Value: 0
O1 Operator 1 L1 [passed]
O2 Operator 2 L2 [passed]
Notes
Time is not latched, so C1 changes can be done during delay cycle.
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.
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.
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)
Notes
Could be used e.g., for reading out values when a defined (failure) situation occurs
Notes
Time is not latched, so C1 changes can be done during delay cycle.
Notes
A1/A2 Time is not latched, so changes can be done during delay cycle.
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 [ms]
Boolean Result = L1 rising edge forces TRUE state for C1 time [ms]
C1 = Absolute value of C1 is taken as time in [ms] (no negative time allowed)
L1 = Activates boolean result to TRUE with rising edge
L2 = Resets remaining time for fall back with rising edge
Notes
Time is not latched, so C1 changes can be done during monoflop cycle.
AM Con‐ 1 2 3 4 5 6 7 8
stant #
AM Con‐ 9 10 11 12 13 14 15 16
stant #
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.
{mmmm Description 2 user-defined (up The text may have 0 through 22 characters.
m} constant {#} 22 to charac‐
ters) Notes
[13.yy Free This parameter may only be configured using ToolKit.
constant {#}]
The max. number of characters depends on the numbers of Bytes for each
character.
Please verify the length on the display for best view.
2521 Gen.pos.active 2 000000.00 to This parameter defines the number of MWh of the counter. The number
energy preset 999999.00 MWh entered here will overwrite the current displayed value after confirming with
parameter 2510 Ä p. 463.
[0 MWh]
2510 Gen.pos.active 2 Yes The current value of this counter is overwritten with the value configured in
energy set "Gen.pos.active energy preset" (parameter 2521 Ä p. 463). After the counter
has been (re)set, this parameter changes back to "No" automatically.
2523 Gen.pos.react. 2 000000.00 to This parameter defines the number of positive Mvarh of the counter. The
energy preset 999999.00 number entered here will overwrite the current displayed value after con‐
Mvarh firming with parameter 2511 Ä p. 463.
[0 Mvarh]
2511 Gen.pos.react. 2 Yes The current value of this counter is overwritten with the value configured in
energy set "Gen.pos.react.energy preset" (parameter 2523 Ä p. 463). After the counter
has been (re)set, this parameter changes back to "No" automatically.
2527 Gen.neg.react. 2 000000.00 to This parameter defines the number of negative Mvarh of the counter. The
energy preset 999999.00 number entered here will overwrite the current displayed value after con‐
Mvarh firming with parameter 2513 Ä p. 463.
[0 Mvarh]
2513 Gen.neg.react. 2 Yes The current value of this counter is overwritten with the value configured in
energy set "Gen.neg.react.energy preset" (parameter 2527 Ä p. 463). After the counter
has been (re)set, this parameter changes back to "No" automatically.
2541 Number of 2 0 to 65535 This parameter defines the number of times the control unit registers a start of
starts preset the generator set. The number entered here will overwrite the current dis‐
[0] played value after confirming with parameter 2542 Ä p. 463.
2542 Number of 2 Yes The current value of the start counter is overwritten with the value configured
starts set in "Number of starts preset" (parameter 2541 Ä p. 463). After the counter has
been (re)set, this parameter changes back to "No" automatically.
2550 Maintenance 2 0 to 9,999 h This parameter defines the remaining hours until the next maintenance call
hours occurs. Once the generator has been operated for the number of hours con‐
[300 h] figured here, a maintenance message is displayed.
If the maintenance counter is reset either by the push-buttons at the front
panel (refer to Ä Chapter 2.1 “Display And Status Indicators” on page 35), or
by configuring the parameter "Reset maintenance period hrs" to "Yes"
(parameter 2562 Ä p. 464), the maintenance counter is reset to the config‐
ured value.
Notes
To disable the "maintenance hours" counter configure "0" for this entry.
2562 Reset mainte‐ 2 Yes / No If this parameter is configured to "Yes" the maintenance "hours" counter is
nance period reset to the configured value. Once the counter "maintenance hours" has
hrs [No] been reset, the control unit changes this parameter to "No".
Notes
When using a specific code level in parameter 2567 Ä p. 465 to reset mainte‐
nance hours this parameter can be blocked.
Notes
- menu path:
Notes
To disable the "maintenance days" counter configure "0" for this entry.
2563 Reset mainte‐ 2 Yes / No If this parameter is configured to "Yes" the "maintenance days" counter is
nance period reset to the configured value. Once the counter has been reset, the control
days [No] unit changes this parameter to "No".
Notes
When using a specific code level in parameter 2567 Ä p. 465 to reset mainte‐
nance days this parameter can be blocked.
Notes
- menu path:
0 Operator
1 Service level
3 Commissioner
Notes
The code level defined here only affects the access via the front panel (HMI).
15154 Operation 2 This parameter configures the source for the operation hours.
hours source
[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 0 0 to 999,999.99 When setting the operating hours counter (refer to parameter 2574 Ä p. 465),
hours preset the counter always will be set up to the value configured here.
[0]
2574 Operation 01 Yes The current value of this counter is overwritten with the value configured in
hours set "Operation hours preset" (parameter 2509 Ä p. 465). After the counter has
been (re)set, this parameter changes back to "No" automatically.
Notes
1 The code level can be configured with "Codelevel set operation hours"
(parameter 2573 Ä p. 465). 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 codelevel is necessary to set the operation
operation hours (parameter 2574 Ä p. 465).
hours [2]
2515 Period of use 2 0 to 999,999.99 When setting the period of use hours counter (refer to parameter
preset 2579 Ä p. 465), the counter always will be set up to the value configured
[0] here.
2579 Period of use 01 Yes The current value of this counter is overwritten with the value configured in
set "Period of use preset" (parameter 2515 Ä p. 465). After the counter has been
(re)set, this parameter changes back to "No" automatically.
Notes
1 The code level can be configured with "Code level f. set period of use"
(parameter 2581 Ä p. 465). If your current code level does not match, this
parameter is not visible.
2581 Code level f. 5 0 to 5 This parameter defines which codelevel is necessary to set the period of use
set period of hours (parameter 2579 Ä p. 465).
use [2]
5 Operation
In operation the genset controller can be manually or remote con‐
trolled.
Front panel access is described in chapter Ä Chapter 4.1 “Front
Panel Access” on page 92.
Access via ToolKit is described in chapter Ä Chapter 4.2.6 “View
And Set Values In ToolKit” on page 125.
Access via Remote Panel PR-3000XT is described in chapter and
the Technical Manual “37593 RP-3000XT” .
Access via PLC depends on the interface and the data telegram
used for communication.
5.1 Power ON
Behavior during starting The start-up procedure of the easYgen-XT device can be caused
easYgen-3000XT by the following reasons:
n Power ON
n Power cycling e.g. by 1701 Ä p. 156 “ Set factory default
values”
n 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.
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, pro‐
grammed as an F class alarm.
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
( Ä Chapter 4.1.5 “Specialized Menu Screens”
on page 101).
Overview
Function/Status Symbol Available in application mode
Symbol Description
Symbol Description
Prerequisites:
n The AUTOMATIC operating mode is enabled.
n The parameter "Emergency power" is configured to "On".
n The configured mains failure limits are reached.
n The configured delay times have expired.
n No shut down alarm is present. (for explanation of the alarm
classes refer to Ä Chapter 9.5.1 “Alarm Classes”
on page 888).
n The engine is ready for operation.
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!
Application Modes
For application modes overview see chapter
Ä Chapter 2.2 “Application Modes Overview”
on page 35.
Engine stops, if
n The LogicsManager "Start req. in AUTO" is not fulfilled
(FALSE) OR
n A shut down alarm occurs
Being parallel to mains or to other generator, the generator power
will be reduced, before the GCB will be opened.
5752 Start stop mode Reserve power The reserve power at the interchange point is to be considered for LDSS
5753 Dead busbar All All generators shall start in case of a dead busbar (mains failure)
start mode
5754 Fit size of engine No The generator rated power is not considered for LDSS
5755 Fit service hours Equal The remaining hours until next service are considered for LDSS
5777 LDSS sort pri‐ Off LDSS priority follows settings without permanently refreshing.
ority always
5759 Minimum run‐ 180 s The minimum running time is 180 seconds
ning time
LDSS parameters for mains parallel Additional assumptions are valid for mains parallel operation
operation (MOP):
n The first generator is only started if it is able to operate at a
minimum load of 40 kW.
n A hysteresis of 20 kW is required to avoid frequent starts and
stops.
n 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.
n The delay for adding another generator shall be 30 seconds.
n 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).
n The delay for removing a generator from the busbar shall be 60
seconds.
5769 MOP Hysteresis 20 kW The reserve power hysteresis in mains parallel operation is 20 kW
5772 MOP Add on 30 s The add on delay in mains parallel operation is 20 seconds
delay
5773 MOP Add on 10 s The add on delay at rated load in mains parallel operation is 10 seconds
delay at rated
load
5774 MOP Add off 60 s The add off delay in mains parallel operation is 60 seconds
delay
LDSS parameters for islanded Additional assumptions are valid for islanded operation (IOP), i.e.
operation in case of an mains failure (emergency) operation:
n 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.
n A hysteresis of 20 kW is required to avoid frequent starts and
stops.
n The delay for adding another generator shall be 10 seconds.
n 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).
n 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”.
2. Configure the parameters listed below.
ID Parameter Value Comment
5765 IOP Add on 3s The add on delay at rated load in islanded operation is 3 seconds
delay at rated
load
5766 IOP Add off 180 s The add off delay in islanded operation is 180 seconds
delay
2800 Mains fail delay 3.00 s Emergency operation is initiated if the mains fail for a t least 3 seconds
time
3408 Emerg. start with Yes Emergency operation is initiated if the MCB fails to close
MCB failure
5539 AM ActPower Determined by The internal power setpoint 1 is used as load setpoint 1
SP1 [W] AnalogManager
81.05: [A1 =
05.54. Internal P
setp1 [W]]
5526 Load setpoint 1 Import The internal power setpoint 1 is a import power value
Configuration
In order to achieve the described protection, the power factor
monitoring parameters ( Ä Chapter 4.5.1.6.1.1 “Generator
Lagging Power Factor (Level 1 & 2)” on page 327 or
Ä Chapter 4.5.1.6.1.2 “Generator Leading Power Factor
(Level 1 & 2)” on page 328) have to be configured as shown
below.
Generator power factor lagging level 1 Generator power factor lagging level 2
Generator power factor leading level 1 Generator power factor leading level 2
1101 User defined min +0.00e0 A value of 0.00 is displayed at the minimum of the input range
display value
1102 User defined +2000.00e3 A value of 2000.00e3 is displayed at the maximum of the input range
max display
value
10116 Filter time con‐ Off No filter time constant is applied to the analog signal
stant
1135 Exponent for 0 The value of the analog input 3 is multiplied by 100=1.
protocol
1103 Monitoring wire Low If the analog signal falls below 2 mA, a wire break is indicated
break
1104 Wire break alarm Class B An alarm of class B will be issued in case of a wire break
class
1105 Self acknowl‐ No A wire break is not automatically cleared after it has been repaired
edge wire break
3636 Bargraph min‐ +0.00 The start value for the bargraph display of the analog input is 0.00
imum
3637 Bargraph max‐ +2000.00 The end value for the bargraph display of the analog input is 2000.00
imum
1125 Description ActivePower SP Analog input [AI 03] is labeled with "ActivePower SP (%)" on the display
Configuring the load controller The load controller is to be configured that it uses a fixed load set‐
point 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].
5539 AM ActPower Determined by The internal power setpoint 1 is used as load setpoint 1
SP1 [W] AnalogManager
81.05
[A1 = 05.54.
Internal P setp1
[W]]
5526 Load setpoint 1 Import The internal power setpoint 1 is a import power value
5520 Int. load control 2000.0 kW The internal power setpoint 1 is configured to 2 MW
setpoint 1
5540 AM ActPower Path Through of: Analog input 3 is used as load setpoint 2
SP2 [W]
06.03 Analog
input 3
5527 Load setpoint 2 Steady The internal power setpoint 1 is a import power value
5521 Int. load control 1000.0 kW The internal power setpoint 1 is configured to 1 MW
setpoint 2
Preliminary Conditions
We recommend to reset the unit to factory settings
before proceeding.
Refer to Ä Chapter 4.3.5 “System Management”
on page 155 for reference.
The LogicsManager factory settings are shown in
Ä Chapter 9.3.5 “Factory Settings” on page 850.
AUTOMATIC
The LogicsManager function "Operat. mode AUTO" (param‐
eter 12510 Ä p. 275/Ä p. 852) can be configured as shown
in (Fig. 217).
ð AUTOMATIC operation mode is always enabled.
STOP
The LogicsManager function "Operat. mode STOP" (param‐
eter 12530 Ä p. 276/Ä p. 852) can be configured as shown
in (Fig. 219).
ð STOP operation mode is enabled as soon as discrete
input 9 is de-energized.
Test with load This is the LogicsManager function "Start req. in AUTO" (param‐
eter 12120 Ä p. 277/Ä p. 850). 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 condi‐
tions for "Start req. in AUTO" are FALSE again. The result
depends on which condition is active longer.
Test without load This is the LogicsManager function "Start w/o load" (param‐
eter 12540 Ä p. 277/Ä p. 852/Ä p. 852). If the conditions for this
LogicsManager function are TRUE, the engine will provide an auto‐
matic 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.
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.
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
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. Configure the LogicsManager function "Ext. acknowledge" as
shown in (Fig. 223).
ð With this setting, the "Ext. acknowledge" LogicsManager
output becomes TRUE as soon as the remote acknowl‐
edge signal is enabled.
Remote start:
n The command variable "04.13 Remote request" changes to "1"
(high) if the start bit (ID 503, bit 0) changes from "0" to "1".
n 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. 224).
Acknowledgment:
n The command variable "04.14 Remote acknowledge" reflects
the Acknowledgment bit (ID 503, bit 4).
n 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
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.
Bit enabling via Modbus protocol The parameter Modbus Slave ID must be configured.
and RS-485 interface
The control bits are sent on address 503 for a start via Modbus:
n Bit 0: Start
n Bit 1: Stop
n Bits 2 and 3: must be "0" (for the watchdog).
n Bit 4: Acknowledgment
n Bit 9: Shutdown command
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
n define a free LM flag for 03.40 Remote Shutdown and
n take it as input for a Free alarm
n with a shutdown alarm class.
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.
9600 COB-ID 181 (hex) / 385 The COB-ID is configured to 181 (hex) or 385 (dec)
(dec)
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).
9300 COB-ID 201 (hex) / 513 The COB-ID is configured to 201 (hex) or 513 (dec)
(dec)
6.3.6.1.1 Installation
Prerequisites The following items are necessary before installing the software:
n PC with Windows operating system
n To connect the IKD to a serial port (RS232) on the PC
– Woodward DPC cable RS-232 (P/N: 5417-557)
n 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
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
The Program Dialog Box On start of the configuration software, you should get the following
screen with fields, buttons and selectors available:
1. “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 con‐
nected
Fig. 229: IKD Configuration Tool
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”
ð This button has two functionalities:
1) After connecting it shows the currently configured CAN
baud rate of the IKD.
2) It can also be used to select the CAN baud rate. For
the easYgen configuration only 125 kBaud, 250 kBaud
and 500 kBaud is permissible.
Fig. 234: PWM duty cycle for a CAT ADEM controller (example
ToolKit)
Bus coupler Discrete outputs Discrete inputs Analog outputs Analog inputs
IB IL 24 DO 32 (only) IB IL 24 DI 16
IB IL 24 DI 32 (only)
ILB CO 24 DI 16 DO 16 ILB CO 24 DI 16 DO 16
WAGO …
Type P/N two channel ver‐ P/N four channel "Wire break" detection TYPE: Settings
sion version
Type P/N two channel ver‐ P/N four channel "Wire break" detection TYPE: Settings
sion version
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 Ä “Config‐
urable WAGO devices”
on page 510
+/- 120 mV 750-469/000-003 no Linear or table Sender type:
Thermocouple
Type P/N eight channel ver‐ "Wire break" detection TYPE: Settings
sion
RTD 750-451 depends on the configured TYPE and Sender type: according to the type con‐
type figured 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” on page 510.
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” on page 510.
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” on page 510.
Type P/N two channel ver‐ P/N four channel Comments Settings
sion version
# of DIs 2 x DI 4 x DI 8 X DI 16 X DI
# of DOs 2 x DO 4 x DO 8 X DO 16 X DO
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 con‐
sistent 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:
Configuration process help The following flow charts step-by-step guide you through the con‐
figuration of external CANopen devices.
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 compen‐
sated for with this parameter.
General notes This feature allows the easYgen to adapt the phase angle meas‐
urement system according to the transformer type. The phase
angle of the "generator to busbar" and the "busbar to mains" meas‐
urement can be compensated . The phase angle compensation is
activated with the parameters "Phase angle compensation GCB"
(parameter 8825 Ä p. 216) and "Phase angle compensation MCB"
(parameter 8841 Ä p. 220) .
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 Ä p. 217) and
"Phase angle MCB" (parameter 8842 Ä p. 220). 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
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:
Derating of power The power reduction is realized by using the LogicsManager "Free
derating" (parameter 15146 Ä p. 270/Ä p. 853). 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. 250 to convert the relay outputs into a analog signal (0 to 500
Ohms).
1001 User defined min +100.00 A value of 100 is displayed at the minimum of the input range
display value
1002 User defined +0.00 A value of 0 is displayed at the maximum of the input range
max display
value
1039 Sender value at 0.000 The sender value at minimum display is 0 Ohms
display min.
1040 Sender value at 500.000 The sender value at maximum display is 500 Ohms
display max.
1020 Sender type 0 - 2000 Ohm A 0 to 2000 Ohms sender is used on the analog input
10113 Filter time con‐ 3 Filter time depending on the ambient conditions
stant
3632 Bargraph min‐ +0.00 The start value for the bargraph display of the analog input is 0
imum
3633 Bargraph max‐ +100.00 The end value for the bargraph display of the analog input is 100 and indi‐
imum cates the derating
1025 Description Derating Analog input [AI 01] is labeled with "Derating" on the display
15149 Direct derating On Only the analog source is used for the derating
15147 AM Derating Determined by Defines [06.01 Analog Input AI 1] as the analog source which controls the
source AnalogManager derating function
81.21
Select "Pass through"
[A1 = 06.01
Analog input 1]
15142 J1939 derating Off The derate command via ECU is ignored
Maximal power setpoint After the unit is configured as described above, the maximal power
setpoint looks like shown in Fig. 252.
Application Examples
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:
n No connection to mains is active
AND
n 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 inter‐
locking 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!
Monitoring NC Feedback
The monitoring of the NC feedback is performed always, if the
Neutral Interlocking is enabled. The monitor checks, if the feed‐
back 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).
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
6.4.1.1.1 RPDO
Configure CAN interface 1 CANopen Master (parameter 8993 Ä p. 425) 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.
ID Parameter Value Comment
Configure RPDO
1. Either on the front panel or using ToolKit navigate to menu
“Configure CAN interface 1 è Receive PDO 1”.
2. Configure the parameters listed below.
ID Parameter Value Comment
9911 1. Mapped 00503 The 1st mapped object is set to control parameter 503.
Object
ð
Setting the COB-ID to 201 (hex) is exem‐
plary; usually, the PDOs are in the range
of 181 (hex) to 57F (hex).
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.
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.
Node-ID 1 (standard value) The following table shows exemplary request data for the device
on the CANopen bus.
Notes
The message 2B F7 21 01 10
00 00 00 must be sent twice to
acknowledge an alarm com‐
pletely. The first rising edge
(2B F7 21 01 00 00 00 00 fol‐
lowed by 2B F7 21 01 10 00 00
00) disables the horn and the
second rising edge resets the
alarm.
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" (param‐
eter 8950 Ä p. 425) must be configured accordingly. Node-ID 2 is
used in the following example.
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.
ID Parameter Value Comment
The request on the bus is sent via the control parameter 503 of the
device.
The data (hex) shows the state of parameter 503 to achieve the
required control.
The following table shows exemplary request data for the device
on the CANopen bus.
Notes
The message 2B F7 21 01 10
00 00 00 must be sent twice to
acknowledge an alarm com‐
pletely. The first rising edge
(2B F7 21 01 00 00 00 00 fol‐
lowed by 2B F7 21 01 10 00 00
00) disables the horn and the
second rising edge resets the
alarm.
The control request is equal to the request via default SDO com‐
munication 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.
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
6.4.1.2.1 RPDO
Configure CAN interface 1 CANopen Master (parameter 8993 Ä p. 425) 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.
ID Parameter Value Comment
Configure RPDO
1. Either on the front panel or using ToolKit navigate to menu
“Configure CAN interface 1 è Receive PDO 1”.
2. Configure the parameters listed below.
ID Parameter Value Comment
9911 1. Mapped 00509 The 1st mapped object is set to control parameter 509.
Object
ð
Setting the COB-ID to 321 (hex) is exem‐
plary; usually, the PDOs are in the range
of 181 (hex) to 57F (hex).
CANopen message The following table shows exemplary send data for the device on
the CANopen bus.
A frequency setpoint of 50.60 Hz is transmitted:
n 5060 (dec) = 13C4 (hex) → C4 13 according to the CANopen
protocol
The data (hex) shows the state of parameter 509 to achieve the
required control.
The following table shows exemplary send data for the device on
the CANopen bus.
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
6.4.1.3.1 RPDO
Configure CAN interface 1 CANopen Master (parameter 8993 Ä p. 425) 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.
ID Parameter Value Comment
Configure RPDO
1. Either on the front panel or using ToolKit navigate to menu
“Configure CAN interface 1 è Receive PDO 1”.
2. Configure the parameters listed below.
ID Parameter Value Comment
9911 1. Mapped 00510 The 1st mapped object is set to control parameter 510.
Object
ð
Setting the COB-ID to 321 (hex) is exem‐
plary; usually, the PDOs are in the range
of 181 (hex) to 57F (hex).
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:
n 412 (dec) = 019C (hex) → 9C 01 according to the CANopen
protocol
The data (hex) shows the state of parameter 510 to achieve the
required control.
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
6.4.1.4.1 RPDO
Configure CAN interface 1 CANopen Master (parameter 8993 Ä p. 425) 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.
ID Parameter Value Comment
Configure RPDO
1. Either on the front panel or using ToolKit navigate to menu
“Configure CAN interface 1 è Receive PDO 1”.
2. Configure the parameters listed below.
ID Parameter Value Comment
9911 1. Mapped 00508 The 1st mapped object is set to control parameter 508.
Object
ð
Setting the COB-ID to 321 (hex) is exem‐
plary; usually, the PDOs are in the range
of 181 (hex) to 57F (hex).
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:
n 900 (dec) = 0384 (hex) → 84 03 according to the CANopen pro‐
tocol.
A power factor setpoint of 1.0 is transmitted in line 3:
n 1000 (dec) = 03E8 (hex) → E8 03 according to the CANopen
protocol
The data (hex) shows the state of parameter 508 to achieve the
required control.
The following table shows exemplary send data for the device on
the CANopen bus.
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
6.4.1.5.1 RPDO
Configure CAN interface 1 CANopen Master (parameter 8993 Ä p. 425) 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.
ID Parameter Value Comment
Configure RPDO
1. Either on the front panel or using ToolKit navigate to menu
“Configure CAN interface 1 è Receive PDO 1”.
2. Configure the parameters listed below.
ID Parameter Value Comment
9911 1. Mapped 00507 The 1st mapped object is set to control parameter 507.
Object
ð
Setting the COB-ID to 321 (hex) is exem‐
plary; usually, the PDOs are in the range
of 181 (hex) to 57F (hex).
CANopen message The following table shows exemplary send data for the device on
the CANopen bus in line 1.
A power setpoint of 1000.0 kW is transmitted:
n 10000 (dec) = 2710 (hex) → 10 27 according to the CANopen
protocol
The data (hex) shows the state of parameter 507 to achieve the
required control.
The table above shows exemplary send data for the device on the
CANopen bus in line 2.
Configure RPDO
1. Either on the front panel or using ToolKit navigate to menu
“Configure CAN interface 1 è Receive PDO 1”.
2. Configure the parameters listed below.
ID Parameter Value Comment
9911 1. Mapped 00509 The 1st mapped object is set to control parameter 509.
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
ð
Setting the COB-ID to 321 (hex) is exem‐
plary; usually, the PDOs are in the range
of 181 (hex) to 57F (hex).
CANopen message The following table shows exemplary send data for the device on
the CANopen bus in line 1. The following setpoints are transmitted:
n Frequency 50.6 Hz (5060 (dec) = 13C4 (hex) → C4 13
according to the CANopen protocol)
n Power 1000 kW (10000 (dec) = 2710 (hex) → 10 27 according
to the CANopen protocol)
n Power factor 0.9 lagging (900 (dec) = 0384 (hex) → 84 03
according to the CANopen protocol)
Bit "x" of ... remotely requests to ... is available as LogicsManager command ... uses LogicsManager "y" to
Parameter switch to variable switch
504 ...
Bit 4 Voltage setpoint 2 04.37 "Remote voltage setpoint 2" 12920; 86.86 LM: "Setp. 2 voltage"
Bit 5 Frequency setpoint 2 04.38 "Remote frequency setpoint 2" 12918; 86.81 LM: "Setpoint 2 freq."
Bit 6 Power factor setpoint 2 04.39 "Remote PF setpoint 2" 12921: 86.84 LM: "Setp. 2
pwr.factor"
Bit 7 Active power setpoint 2 04.40 "Remote power setpoint 2" 12919; 86.82 LM: "Setp. 2 load"
Notes
This LogicsManager command vari‐
able can be used to switch to each
available load setpoint.
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
6.4.1.7.1 RPDO
Configure CAN interface 1 CANopen Master (parameter 8993 Ä p. 425) 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.
ID Parameter Value Comment
Configure RPDO
1. Either on the front panel or using ToolKit navigate to menu
“Configure CAN interface 1 è Receive PDO 1”.
2. Configure the parameters listed below.
ID Parameter Value Comment
9911 1. Mapped 00504 The 1st mapped object is set to control parameter 504.
Object
ð
Setting the COB-ID to 321 (hex) is exem‐
plary; usually, the PDOs are in the range
of 181 (hex) to 57F (hex).
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.
The data (hex) shows the state of parameter 504 to achieve the
required control.
The following table shows exemplary send data for the device on
the CANopen bus.
Configure RPDO
1. Either on the front panel or using ToolKit navigate to menu
“Configure CAN interface 1 è Receive PDO 1”.
2. Configure the parameters listed below.
ID Parameter Value Comment
9911 1. Mapped 00505 The 1st mapped object is set to control parameter 505.
Object
ð
Setting the COB-ID to 334 (hex) is exem‐
plary; usually, the PDOs are in the range
of 181 (hex) to 57F (hex).
CANopen message The following table shows exemplary send data for the device on
the CANopen bus.
Remote control bit 1 is set:
The data (hex) shows the state of parameter 249 to achieve the
required control.
The table above shows exemplary sends data for the device on the
CANopen bus in line 2.
9602 Transmission 255 The number of required sync messages is set to 255.
type
The recorded data shows that the data of the Mapped Object (in
this example Mux 5) is sent ( Ä Table 127 “Cyclical sending of
data - sync message request” on page 549) after sending the
Sync Message twice ( Ä Table 128 “Cyclical sending of data -
reply” on page 549).
80 - -
1 2 80 -
2 1 2AE 8B 13
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 connected)?
cannot be configured
Are all modules detected (i.e. no blinking expansion module)?
No data is sent by the Woodward con‐ Is the unit in operational mode (heartbeat - CAN ID 700 (hex) + Node-ID has the content
troller 5 (hex)?
No data is received by the Woodward con‐ Is the unit in operational mode (heartbeat - CAN ID 700 (hex) + Node-ID has the content
troller 5 (hex)?
No monitoring bit data is received on the Is the CAN bus connected correctly?
RPDO
Is the baud rate configured correctly?
Is the unit in operational mode? If not, start it via another device or put in NMT Master
(parameter 8993 Ä p. 425).
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?
Data Format(s)
Modbus registers are read and written according to
the Modbus standard as Big-endian.
Composite data types like LOGMAN, ANALOG‐
MANAGER, and TEXT use separate descriptions.
Fig. 263: Setpoint source selection Screen shots beside show an exemplary configuration of the load
setpoint 1 source. All other setpoint sources are configured accord‐
ingly.
The interface setpoints may be set using the objects for active
power, power factor, frequency, and voltage (refer to Ä Chapter
9.2.16 “Additional Data Identifier” on page 803 for detailed infor‐
mation).
Example 1: Active power inter‐ The active power setpoint value must be written to object 21FB
face setpoint (hex), i.e. parameter 507.
A power value of 50 kW = 500 (dec) = 01F4 (hex) is to be trans‐
mitted.
n Modbus address = 40000 + (Par. ID + 1) = 40508
n 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.
Example 2: Power factor inter‐ The power factor setpoint value must be written to object 21FC
face setpoint (hex), i.e. parameter 508.
A power factor of 1 = 1000 (dec) = 03E8 (hex) is to be trans‐
mitted.
n Modbus address = 40000 + (Par. ID + 1) = 40509
n Modbus length = 1 (UNSIGNED 16)
Example 3: Frequency interface The frequency setpoint value must be written to object 21FD
setpoint (hex), i.e. parameter 509.
A frequency value of 50.00 Hz = 5000 (dec) = 1388 (hex) is to be
transmitted.
n Modbus address = 40000 + (Par. ID + 1) = 40510
n Modbus length = 1 (UNSIGNED 16)
Example 4: Voltage interface set‐ The voltage setpoint value must be written to object 21FE (hex),
point i.e. parameter 510.
A voltage value of 400 V = 400 (dec) = 0190 (hex) is to be trans‐
mitted.
n Modbus address = 40000 + (Par. ID + 1) = 40511
n Modbus length = 2 (UNSIGNED 32)
The high word must be written to the lower address and the low
word must be written to the higher address.
Bit "x" of ... remotely requests to ... is available as LogicsManager command ... uses LogicsManager "y" to
Parameter switch to variable switch
504 ...
Bit 4 Voltage setpoint 2 04.37 "Remote voltage setpoint 2" 12920; 86.86 LM: "Setp. 2 voltage"
Bit 5 Frequency setpoint 2 04.38 "Remote frequency setpoint 2" 12918; 86.81 LM: "Setpoint 2 freq."
Bit 6 Power factor setpoint 2 04.39 "Remote PF setpoint 2" 12921: 86.84 LM: "Setp. 2
pwr.factor"
Bit 7 Active power setpoint 2 04.40 "Remote power setpoint 2" 12919; 86.82 LM: "Setp. 2 load"
Notes
This LogicsManager command vari‐
able can be used to switch to each
available load setpoint.
Example
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:
n Modbus address = 40000 + (Par. ID + 1) = 40505
n Modbus length = 1 (UNSIGNED 16)
Fig. 272: Remotely switch Setp. 2
load
Fig. 276 shows how bit 5 would be set to enable the fre‐
quency setpoint 2.
Delay ON Delay OFF Logic equation 1 Logic equation 2 Command 1 Command 2 Command 3
Describe the LogicsManager equa‐ The LogicsManager screens below show parts of the command
tion as "command chain" in hex chain. How to generate hex code words is described for each part
code (step 2) of the Modbus message.
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.
Word 2 Word 3
Signs Operators
"NOT" 0 "AND" 0
"—" 1 "NAND" 1
"TRUE" 2 "OR" 2
"FALSE" 3 "NOR" 3
"XOR" 4
"NOT-XOR" 5
Delay ON Delay OFF Logic equation 1 Logic equation 2 Command 1 Command 2 Command 3
low high low high Sign Oper‐ Sign Oper‐ Sign 0x00 0x00 0x00 low high low high low high
byte byte byte byte 1 ator 1 2 ator 2 3 byte byte byte byte byte byte
Example
Delay ON Delay OFF Logic equation 1 Logic equation 2 Command 1 Command 2 Command 3
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, 0007 251 dec,
0208 hex hex 00FB hex
low high low high Sign Oper‐ Sign Oper‐ Sign 0x00 0x00 0x00 low high low high low high
byte byte byte byte 1 ator 1 2 ator 2 3 byte byte byte byte byte byte
2C 01 E8 03 1 2 3 2 1 0 0 0 08 02 07 00 FB 00
Example
Delay ON Delay OFF Logic equation 1* Logic equation 2* Command Command Command
1 2 3
Sig Oper‐ Sign Oper‐ Sig -/- -/- -/-
n1 ator 1 2 ator 2 n 3
0.00 sec 0.00 sec ¾ And True And Tru 00 00 00 No. 09.09 No. 96.01 No. 96.01
e 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
byt byte byt byte byt byte byt byte byt byte
e e e e e
0000 (hex) 0000 (hex) 1020 (hex) 2000 (hex) 0F02 (hex) 0000 (hex) 0000 (hex)
Example
Delay ON Delay OFF Logic equation 1* Logic equation 2* Command Command Command
1 2 3
Sig Oper‐ Sign Oper‐ Sig -/- -/- -/-
n1 ator 1 2 ator 2 n 3
3.00 sec 10.00 sec ¾ Or False Or ¾ 00 00 00 No. 09.02 No. 96.08 No. 04.13
ID = ID = ID =
520 dec 7 dec 251 dec
012c (hex) 03E8 (hex) 1 2 3 2 1 0 0 0 0208 (hex) 0007 (hex) 00FB (hex)
low high low high "as is" "as is" low high low high low high
byt byte byt byte byt byte byt byte byt byte
e e e e e
2C01 (hex) E803 (hex) 1232 (hex) 1000 (hex) 0802 (hex) 0700 (hex) FB00 (hex)
Example
Delay ON Delay OFF Logic equation 1* Logic equation 2* Command Command Command
1 2 3
Sig Oper‐ Sign Oper‐ Sig -/- -/- -/-
n1 ator 1 2 ator 2 n 3
0.00 sec 0.00 sec ¾ Or ¾ Or Fal 00 00 00 No. 09.05 No. 04.14 No. 96.01
se ID = ID = ID =
523 dec 252 dec 0 dec
0000 (hex) 0000 (hex) 1 2 1 2 3 0 0 0 020B (hex) 00FC (hex) 0000 (hex)
low high low high "as is" "as is" low high low high low high
byt byte byt byte byt byte byt byte byt byte
e e e e e
0000 (hex) 0000 (hex) 1212 (hex) 3000 (hex) 0B02 (hex) FC00 (hex) 0000 (hex)
Example
Delay ON Delay OFF Logic equation 1* Logic equation 2* Command Command Command
1 2 3
Sig Oper‐ Sign Oper‐ Sig -/- -/- -/-
n1 ator 1 2 ator 2 n 3
0.00 sec 0.00 sec Fal And True And Tru 00 00 00 No. 00.01 No. 96.01 No. 96.01
se e ID = ID = ID =
0 dec 0 dec 0 dec
0000 (hex) 0000 (hex) 3 0 2 0 2 0 0 0 0000 (hex) 0000 (hex) 0000 (hex)
low high low high "as is" "as is" low high low high low high
byt byte byt byte byt byte byt byte byt byte
e e e e e
0000 (hex) 0000 (hex) 3020 (hex) 2000 (hex) 0000 (hex) 0000 (hex) 0000 (hex)
In order to clear the event history, bit 0 of object 26AA (hex), i.e.
parameter 1706, must be enabled.
Example 2 (reset to default) In order to reset the default values, parameter 1701 Ä p. 156 must
be enabled.
CAUTION!
Set factory default settings causes easYgen
power cycle!
Don't run 1701 Ä p. 156 “Set factory default
values” during controlling a genset because it
causes a power cycle of the easYgen control.
01 ILLEGAL FUNCTION The sent request function code is not supported by the Modbus protocol.
03 ILLEGAL DATA VALUE The data value exceeds the min. and max. limitations of the parameter
upon a write request.
There is no parameter on the requested address.
Service port
The USB interface follows the USB 2.0 standard
but is - as a service port - reserved for ToolKit and
special Woodward usage.
Protocol description If a data protocol is used, a CAN message looks like this:
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 Ä Chapter 9.2 “Data Protocols” on page 619).
Example
MUX Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7
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.
n Bit sequence:
b = b0 to b–1
n Value shown:
UNSIGNEDn(b) = b–1 * 2–1 + ... + b1 * 21 + b0 * 20
Octet Number 1. 2. 3. 4. 5. 6. 7. 8.
UNSIGNED8 b7 to b0
UNSIGNED16 b7 to b0 b15 to b8
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
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.
n Bit sequence:
b = b0 to b–1
n Value shown:
SIGNEDn(b) = b–2 * 2–2 + ... + b1 * 21 + b0 * 20
if b–1 = 0
n And with two’s complement:
SIGNEDn(b) = SIGNEDn(^b)-1
if b–1 = 1
Octet Number 1. 2. 3. 4. 5. 6. 7. 8.
SIGNED8 b7 to b0
SIGNED16 b7 to b0 b15 to b8
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
Diagnostic trouble codes (DM1/ In the J1939 status screen the first 10 active alarm messages
DM2) (Active Diagnostic Trouble Codes - DM1) and the first 10 unac‐
knowledged alarm messages (Previously Active Diagnostic
Trouble Codes - DM2) with text, SPN, FMI, and OC are displayed.
The state of the lamps (amber/red) is always displayed.
n SPN (= Suspect Parameter Number) indicates the measured
value that the alarm code is referring (e.g. SPN = 100 corre‐
sponds to oil pressure).
n FMI (= Failure Mode Indicator) specifies the alarm more pre‐
cisely (e.g. FMI = 3 means: value is above predefined limits)
n OC (Occurrence Count) indicates how often an alarm occurred.
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
157 65243 Fuel rail pressure 0.1 MPa 0 to 251 Mpa 15225
1137 65187 Exhaust gas port 1 temperature 0.1 °C -273 to 1735 °C 15242
1138 65187 Exhaust gas port 2 temperature 0.1 °C -273 to 1735 °C 15243
1139 65187 Exhaust gas port 3 temperature 0.1 °C -273 to 1735 °C 15244
1140 65187 Exhaust gas port 4 temperature 0.1 °C -273 to 1735 °C 15245
1141 65186 Exhaust gas port 5 temperature 0.1 °C -273 to 1735 °C 15246
1142 65186 Exhaust gas port 6 temperature 0.1 °C -273 to 1735 °C 15247
1143 65186 Exhaust gas port 7 temperature 0.1 °C -273 to 1735 °C 15248
1144 65186 Exhaust gas port 8 temperature 0.1 °C -273 to 1735 °C 15249
1145 65185 Exhaust gas port 9 temperature 0.1 °C -273 to 1735 °C 15250
1146 65185 Exhaust gas port 10 temperature 0.1 °C -273 to 1735 °C 15251
1147 65185 Exhaust gas port 11 temperature 0.1 °C -273 to 1735 °C 15252
1148 65185 Exhaust gas port 12 temperature 0.1 °C -273 to 1735 °C 15253
1149 65184 Exhaust gas port 13 temperature 0.1 °C -273 to 1735 °C 15254
1150 65184 Exhaust gas port 14 temperature 0.1 °C -273 to 1735 °C 15255
1151 65184 Exhaust gas port 15 temperature 0.1 °C -273 to 1735 °C 15256
1152 65184 Exhaust gas port 16 temperature 0.1 °C -273 to 1735 °C 15257
1153 65183 Exhaust gas port 17 temperature 0.1 °C -273 to 1735 °C 15258
1154 65183 Exhaust gas port 18 temperature 0.1 °C -273 to 1735 °C 15259
1155 65183 Exhaust gas port 19 temperature 0.1 °C -273 to 1735 °C 15260
1156 65183 Exhaust gas port 20 temperature 0.1 °C -273 to 1735 °C 15261
1172 65178 Turbo 1 compressor inlet temperature 0.1 °C -273 to 1735 °C 15273
1173 65178 Turbo 2 compressor inlet temperature 0.1 °C -273 to 1735 °C 15274
1174 65178 Turbo 3 compressor inlet temperature 0.1 °C -273 to 1735 °C 15275
1175 65178 Turbo 4 compressor inlet temperature 0.1 °C -273 to 1735 °C 15276
1176 65177 Turbo 1 compressor inlet pressure 1 kPa -250 to 251 kPa 15277
1177 65177 Turbo 2 compressor inlet pressure 1 kPa -250 to 251 kPa 15278
1178 65177 Turbo 3 compressor inlet pressure 1 kPa -250 to 251 kPa 15279
1179 65177 Turbo 4 compressor inlet pressure 1 kPa -250 to 251 kPa 15280
1203 65172 Engine auxiliary coolant pressure 1 kPa 0 to 1000 kPa 15289
1382 65130 Fuel filter difference pressure 1 kPa 0 to 500 kPa 15292
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
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
Data transmission engine control n If the sent values exceed the limits of the specification, the dis‐
unit (ECU) played value is not defined.
n 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.
Please refer to the ECU manual for the engine specific stop codes.
ECU Device type J1939 own Engine con‐ SPN ver‐ Comment
address trol address sion
(15102)
(15106) (15107) (15103)
Standard ECUs Standard N/A N/A N/A Please refer to Ä Chapter 7.6.3 “Device
Type Standard” on page 585 for more
details.
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.
ECU Device type J1939 own Engine con‐ SPN ver‐ Comment
address trol address sion
(15102)
(15106) (15107) (15103)
Volvo EMS2 EMS2 Volvo 17 0 N/A The rated speed of the EMS1 and EDC3
cannot be switched via the easYgen.
Volvo EMS1
Volvo EDC3
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.
MTU ADEC ECU8/ ADEC ECU8 MTU 234 0 N/A The easYgen is connected with the MTU
ECU9 system: ADEC ECU8 & SmartConnect or
ADEC ECU9.
Supported ECUs
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
Engine Start No Yes No Yes Yes Yes Yes No No / Yes Yes Yes If an engine start command is initi‐
ated by the easYgen, this informa‐
tion is transmitted in the form of a
J1939 message bit to an ECU. If
ignition speed is reached, this bit
will be reset (LogicsManager com‐
mand variable 03.02. "Starter").
Engine Stop Yes Yes No Yes Yes Yes Yes Yes No / Yes Yes Yes This J1939 bit information is set, if
a "Stop" command in automatic or
manual mode is present in the
easYgen. The "Stop" bit informa‐
tion remains set, until ignition
speed is fallen below. After igni‐
tion speed has been fallen below,
the "Stop" bit will be reset (Logi‐
csManager command variable
03.27. "Stop solenoid").
Droop mode Yes Yes No Yes Yes Yes Yes Yes Yes / Yes No This J1939 bit information is set, if
Yes 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 "Fre‐
quency droop active" is TRUE.
Idle Mode No Yes No1 Yes Yes No No1 No1 No / No Yes Yes This J1939 bit information is set, if
"Idle" mode is active (LogicsMan‐
ager command variable 04.15.
"Idle run active" is TRUE).
The bit will be reset, if "Idle" mode
is no longer active (LogicsMan‐
ager command variable 04.15.
"Idle run active" is FALSE).
50/60 Hz Yes Yes No Yes2 No Yes No1 No No / No Yes Yes The J1939 information for 50 or
switch 60 Hz mode is sent to the ECU
depending on the "Rated system
frequency" parameter setting
(1750 Ä p. 411) within the
easYgen .
Speed bias Yes Yes Yes Yes Yes Yes Yes Yes Yes / Yes Yes Refer to parameter 5537 Ä p. 442
Yes for detailed information.
offse abso offse abso abso abso abso offse offse
t lute t lute lute lute lute absolute t t
Override No Yes No Yes No Yes No Yes No / No Yes Yes This J1939 bit information is set, if
the easYgen is in critical mode
(LogicsManager command vari‐
able 04.27. "Critical mode" is
TRUE).
The bit will be reset, if the critical
mode has been expired or
aborted.
Displayed messages (visualization) In standard mode, the easYgen is able to display all values listed in
the table Ä “Standard visualization messages” on page 579 if they
are supported by the connected ECU.
Diagnostic trouble codes (DM1/ In standard mode, the easYgen diagnostic messages DM1 (Active
DM2) 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 mes‐
sages. These messages are only transmitted if the parameter
"ECU remote controlled" (parameter 15127 Ä p. 442) is configured
to "On".
Dec Hex
0 0000 TSC1 Torque/Speed Control 1 695 Engine Override Control Mode (fixed 10
to “Speed Control”)
61441 F001 EBC1 Electronic Brake Con‐ 970 Engine Auxiliary Shutdown Switch 100
troller 1
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 Accelerator 1 500
Control Selection Select
Notes
If droop shall be active (LogicsMan‐
ager 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 (at 10,000
PGN FEE5)
Notes
DM3 and DM11 are only transmitted if
triggered.
Dec Hex
Notes
DM3 and DM11 are only transmitted if
triggered.
Configure J1939 addresses For the visualization the “J1939 own address” (parameter
15106 Ä p. 441) and the “Engine control address” (parameter
15103 Ä p. 442) 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 Ä p. 442) is “0” and the “J1939
own address” (parameter 15106 Ä p. 441) is often "234" or "3".
Temporary restriction
With the current easYgen-XT one server can
handle only one client at a time.
Address range The controller Modbus Slave module distinguishes between visual‐
ization 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 Mul‐
tiple Registers" (Fig. 306)
Visualization The visualization over Modbus is provided in a very fast data pro‐
tocol where important system data like alarm states, AC measure‐
ment data, switch states and various other information may be
polled.
............
Data Format(s)
Modbus registers are read and written according to
the Modbus standard as Big-endian.
Composite data types like LOGMAN, ANALOG‐
MANAGER, and TEXT use separate descriptions.
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 Ä Table 140 “Data types” on page 590 for more informa‐
tion.
UNSIGNED 8 1
UNSIGNED 16 1
INTEGER 16 1
UNSIGNED 32 2
INTEGER 32 2
TEXT/X X/2
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.
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 cir‐
cuit or generator group breaker.
Load share monitoring The easYgen provides LDSS parameters for monitoring load
sharing:
n Multi-unit parameter alignment
The multi-unit parameter alignment functionality requires that
the relevant parameters are all configured identically at all par‐
ticipating units. For additional information refer to Ä Chapter
4.5.6.11 “Multi-Unit Parameter Alignment” on page 402.
n 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
Ä Chapter 4.5.6.12 “Multi-Unit Missing easYgen” on page 403.
Load share communication The following parameters allows to select the interface for load
share communication. Refer to Ä Chapter 4.4.4.3.5 “Load-Share
Interface” on page 241 for detailed information.
Notes
* CAN or Ethernet A depending
on 11986 Ä p. 243/Ä p. 592
(described below)
Notes
Switches the load share inter‐
face between
n FALSE: CAN
n TRUE: Ethernet A
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:
n Increase the baud rate (parameter 3156 Ä p. 425) under con‐
sideration of the bus length (refer to Ä Chapter 3.4.4 “CAN Bus
Interfaces” on page 83).
n Reduce the transfer rate of the load share message (param‐
eter 9921 Ä p. 448).
n Reduce the transfer rate of the visualization message, i.e. the
event timer (parameter 9604 Ä p. 431).
n Disable the transmission visualization data on the CAN bus
and use the RS-485 interface to transmit visualization data.
n Disable SYNC message (parameter 9100 Ä p. 425) and/or
TIME message (parameter 9101 Ä p. 426) and/or the producer
heartbeat time SYNC message (parameter 9120 Ä p. 425), if
possible.
CAN load share configuration The following parameters are available for configuring the CAN bus
interfaces. Refer to Ä Chapter 4.7.7 “Load Share Parameters”
on page 448 for detailed information.
Open menu path “Parameter è Configuration
è Configure interfaces è Configure CAN interfaces
è Configure CAN load share”. Refer to Ä Chapter 4.4.4.3.6 “ Load
Sharing” on page 241.
8 Technical Specifications
8.1 Technical Data
Product label
9 Approval Approvals
Battery inside
This device contains a battery, and therefore it is labeled with the
symbol shown beside according to the EU Directive 2006/66/EC.
WARNING!
Batteries can be harmful to the environment. Dam‐
aged or unusable batteries must be disposed of in
Fig. 309: Waste Disposal a container specially reserved for this purpose.
In general, appropriate local guidelines and regula‐
tions must be followed when disposing of electrical
devices and batteries.
Currents
With External CT
For correct measuring with external CT the input
has to be one side grounded by the customer.
CAUTION!
Device Operating Voltage
Connect the unit only to a DC power source that
complies with the safety extra-low voltage (SELV)
requirements.
Degree of pollution 2
8.1.3 Inputs/Outputs
Discrete inputs 'DI xx' Discrete inputs Galvanically isolated
Discrete outputs 'R xx' (relay out‐ Discrete/relay outputs Potential free Galvanically isolated
puts)
Configurable
via Logi‐
csManager
Analog inputs 'AI 01-03' (Type 1: Analog inputs FlexInTM Freely scal‐
0/4 to 20 mA | 0 to 2000 Ω | 0 to 1 V) able
Resolution 16 Bit
Analog outputs 'AO 01' "Speed Analog output Freely scalable Galvanically
Biasing" (Type 1: ±20 mA | ±10 V | isolated
Pre-configured to "11.03
PWM) Speed bias [%]"
Analog outputs 'AO 02' "Voltage Analog output Freely scalable Galvanically
Biasing" (Type 1: ±20 mA | ±10 V | isolated
Pre-configured to "11.02
PWM) Voltage bias [%]"
Auxiliary excitation (D+) input/ Auxiliary excitation (D+) input/output Galvanically isolated
output
Output current approx. 100 mA@12/24 VDC
8.1.4 Interfaces
USB (slave) USB 2.0 interface Galvanically isolated
Bus Voltage 5V
8.1.7 Housing
Housing type Type Plastic Sheet metal
easYpack Custom
Wiring Screw-plug-terminals
2.5 mm²
Protection Protection system Plastic IP54 in the front with clamp fas‐
teners
8.1.8 Approvals
EMC test (CE) Tested according to applicable EMC standards. Refer to
Ä Chapter 8.2 “Environmental Data” on page 601 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)
Acceleration 4G
Plastic Cold, Dry Heat -30 °C (-22 °F) / -30 °C (-22 °F) /
(storage) 80 °C (176 °F) 80 °C (176 °F)
Cold, Dry Heat (oper‐ -20 °C (-4 °F) / 70 °C -40 °C (-40 °F) /
ating) (158 °F) 70 °C (158 °F)
Marine environmental categories Marine environmental categories Lloyd’s Register of Shipping (LRS):
ENV1, ENV2, ENV3 and ENV4
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:
n Range 1: 69/120 V rated = 100%
n Range 2: 277/480 V rated = 100%
n
Frequency
Voltage
Wye generator / mains / 0 to 650 kV 0.5% Class 0.5 2 1.5% (of PT secondary
busbar voltage setting)1
related to:
Delta generator / mains / 2% (of PT secondary
69/277 V (Wye)
busbar voltage setting)1
120/480 V (Delta)
Power supply/Battery 0 to 40 VDC ±0.5% related to 40 V Related on the measure‐ 0.5% equals 0.2 V (±0.2
ment range 8 to 40 V 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 power -2 to 2 GW 1% (of 69/277 V x 1/5 A) Measuring starts with
value 2/3 detecting the zero pas‐
sage of current/voltage
Reactive power
Actual value in L1, L2, -2 to 2 Gvar 1% (of 69/277 V x 1/5 A) Measuring starts with
L3 2/3 detecting the zero pas‐
sage of current/voltage
Power factor
Actual value power lagging 0.000 to 1.000 to 1% 1% (of 1.3/6.5 A)3 1.000 is displayed for
factor L1 leading 0.000 measuring values below
the measuring start
Miscellaneous
Real energy 0 to 4,200 GWh 0.36% (of 1.3/6.5 A)3 Not calibrated
Phase angle -180 to 180° ± 1 degree 1.25% (of PT secondary 180° is displayed for
volt. setting) measuring values below
measuring start
Analog Inputs
Analog Outputs
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 oper‐
ating 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 accord‐
ingly. 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 accu‐
racy are listed below.
Ambient temperature 23 °C ± 2 K
Unbalanced load 46
Synch Check 25
Instantaneous overcurrent 50
Power factor 55
Rotation field
Cylinder temperature
9 Appendix
9.1 Characteristics
9.1.1 Triggering Characteristics
Time-dependent overshoot moni‐ This triggering characteristic is used for time-dependent overcur‐
toring rent monitoring.
Two-level overshoot monitoring This triggering characteristic is used for generator, mains and bat‐
tery overvoltage, generator and mains overfrequency, overload
IOP and MOP and engine overspeed monitoring.
Two-level undershoot monitoring This triggering characteristic is used for generator, mains and bat‐
tery undervoltage, generator and mains underfrequency, and
engine underspeed monitoring.
Two-level reversed/reduced load This triggering characteristic is used for generator reversed/
monitoring reduced load monitoring.
Two-level unbalanced load moni‐ This triggering characteristic is used for generator unbalanced load
toring monitoring.
One-level asymmetry monitoring This triggering characteristic is used for generator voltage asym‐
metry monitoring.
P [psi] 0 7.25 14.50 21.76 29.00 36.26 43.51 50.76 58.02 65.27 72.52
P [psi] 0 7.25 14.50 21.76 29.00 43.51 58.02 72.52 87.02 101.5 116.0 123.2 130.5 145.0
3 3 8 3 4
Fig. 320: Characteristics diagram VDO -40 to 120 °C - full range, Index "92-027-004"
R [Ohm] 17162.4 12439.5 9134.5 6764.5 5067.6 3833.9 2929.9 2249.4 1743.1 1364.0 1075.6
Temp. 15 20 25 30 35 40 45 50 55 60 65
[°C]
R [Ohm] 850.1 677.0 543.5 439.3 356.6 291.5 239.6 197.3 161.5 134.0 114.0
Temp. 158 167 176 185 194 203 212 221 230 239 248
[°F]
R [Ohm] 97.1 82.4 70.1 59.7 51.2 44.3 38.5 33.4 29.1 25.5 22.4
Fig. 322: Characteristics diagram VDO 0 to 120 °C - full range, Index "92-027-006"
Temp. 0 5 10 15 20 25 30 35 40 45 50
[°C]
R [Ohm] 3240.18 2743.6 1905.87 1486.65 1168.64 926.71 739.98 594,9 481,53 392.57 322.17
Temp. 131 140 149 158 167 176 185 194 203 212 221
[°F]
R [Ohm] 266.19 221.17 184.72 155.29 131.38 112.08 96.40 82.96 71.44 61.92 54.01
Temp. 110 115 120 125 130 135 140 145 150
[°C]
Temp. 230 239 248 257 266 275 284 293 302
[°F]
R [Ohm] 47.24 41.42 36.51 32.38 28.81 25.70 23.00 20.66 18.59
R [Ohm] 18.5 39.7 60.25 80.7 100 103.9 107.8 111.7 115.5 119.4 123.2
Temp. 158 176 194 212 257 302 347 392 437 482 572
[°F]
R [Ohm] 127.1 130.9 134.7 138.5 147.9 157.3 166.6 175.8 188.6 194.1 212.0
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 [Ohm] 229.7 247.0 264.1 280.9 297.4 313.6 329.5 345.1 360.5 375.5 390.25
CANopen
n 5004: Generator Values Visualization
supported for easYgen-3000 series compatibility
n 5005: Mains Values Visualization
supported for easYgen-3000 series compatibility
n 5011: Alarm Values Visualization
supported for easYgen-3000 series compatibility
n 5018: Special data 1
n 5019: Special data 2
n 5020: Special data 3
n 5021: Special data 4
n 6000: Load Share Message
n 65000: External Discrete I/O 1 to 8
n 65001: External Discrete I/O 9 to 16
Modbus
n 5010: Basic Visualization
supported for easYgen-3000 series compatibility
n 5016: Basic Visualization (based on 5010)
450059 450058 3,4,5, 136 Total gen. reactive power 1 var EG300
6 0
450062 450061 3,4,5, 150 Total mains reactive power 1 var EG300
6 0
450064 450063 21 1,2 10133 Overspeed 1 latched Mask: 8000h Bit EG300
0
450067 450066 22 1,2 10149 GCB syn. timeout latched Mask: 8000h Bit EG300
0
Charge alt. low voltage (D+) latched Mask: 1000h Bit EG300
0
Idle mode OR Ramp to rated active (suppresses Mask: 0800h Bit EG300
undervolt., underfrequ., ...) 0 not
EG300
0XT
450070 450069 23 1,2 10286 GAP alarm set 1 alarm 16 latched Mask: 8000h Bit reserve
d
450073 450072 24 1,2 10134 Gen.overfreq. 1 latched Mask: 8000h Bit EG300
0
450076 450075 25 1,2 10138 Unbal. load 1 latched Mask: 8000h Bit EG300
0
450079 450078 26 1,2 10135 Mains ov.freq. 1 latched Mask: 8000h Bit EG300
0
450082 450081 27 1,2 10278 Mains import power 1 latched Mask: 8000h Bit EG300
0
450085 450084 28 1,2 10132 State Digital Input 1 latched Mask: 8000h Bit EG300
0
450088 450087 29 1,2 10283 State Digital Input 13 latched Mask: 8000h Bit EG350
0 P2
450091 450090 30 1,2 16377 State external Digital Input 16 latched Mask: 8000h Bit EG300
0
450094 450093 31 1,2 10279 Alarm flexible limit 16 latched Mask: 8000h Bit EG300
0
450097 450096 32 1,2 10280 Alarm flexible limit 32 latched Mask: 8000h Bit EG300
0
450103 450102 34 1,2 10136 Batt.overvolt.2 latched Mask: 0008h Bit EG300
0
Analog inp. 4, wire break or shortcut latched Mask: 0010h Bit EG350
0 P2
Analog inp. 5, wire break or shortcut latched Mask: 0020h Bit EG350
0 P2
Analog inp. 6, wire break or shortcut latched Mask: 0040h Bit EG350
0 P2
Analog inp. 7, wire break or shortcut latched Mask: 0080h Bit EG350
0 P2
Analog inp. 8, wire break or shortcut latched Mask: 0100h Bit EG350
0 P2
Analog inp. 9, wire break or shortcut latched Mask: 0200h Bit EG350
0 P2
Analog inp. 10, wire break or shortcut latched Mask: 0400h Bit EG350
0 P2
450110 450109 3,4 15310 Turbocharger 1 Compressor Outlet Temperature 0.1 °C EG300
0
450111 450110 5,6 10285 Ext. analog inp. 16, wire break Mask: 8000h Bit
450114 450113 5,6 8005 Output to external CAN-I/O Relay 16 Mask: 8000h Bit EG300
0
450122 450121 3,4,5, 2520 Gen. real energy 0.01 MWh EG300
6 0
450125 450124 3,4,5, 2522 Gen. positive reactive energy 0.01 Mvarh EG300
6 0
450136 450135 45 1,2 4153 Idle mode monitoring (suppresses undervolt, Mask: 8000h Bit EG300
underfreq,...) 0
Engine Monitoring delay timer has expired Mask: 0080h Bit EG300
0
450137 450136 3,4 4154 Crank (Starter) is active Mask: 8000h Bit EG300
0
450138 450137 5,6 4155 3-Position Controller Freq./Power raise Mask: 8000h Bit EG300
0
450139 450138 46 1,2 4156 GGB is closed Mask: 8000h Bit EG350
0
Dead busbar closure request for GCB or MCB or Mask: 0400h Bit EG300
GGB 0
LDSS: The Engine shall stop, if possible Mask: 0010h Bit EG300
0
450141 450140 5,6 10284 State external Digital Input 32 latched Mask: 8000h Bit EG320
0 P2
EG350
0 P1
EG300
0XT
450142 450141 47 1,2 8009 Output to external CAN-I/O Relay 32 Mask: 8000h Bit EG320
0 P2
EG350
0 P1
EG300
0XT
450166 450165 55 1,2 10190 GGB fail to close latched Mask: 8000h Bit EG350
0
450167 450166 3,4,5, 219 Nominal active power in system (in own segment) 1 kW EG300
6 0
450169 450168 56 1,2 4157 Command to CB-control 1 (OR) Mask: 8000h Bit EG300
0
450170 450169 3,4,5, 218 Active real power in system (in own segment) 1 kW EG300
6 0
450173 450172 3,4,5, 217 Active power reserve in system (in own segment) 1 kW EG300
6 0
450175 450174 58 1,2 15109 J1939 MTU ADEC ECU Failure Codes 1 EG300
0
450178 450177 59 1,2 15304 Engine Stop Information (extracted from DEUTZ- 1 (enum. EG300
specific J1939-Message) ) 0
Notes
Please see Deutz documentation for correct data!
We know ...
Motorstopinformation:
0 = Keine Abschaltung
1 = Motorschutz
2 = CAN Botschaft Engine Stop Request
3 = Öldruck zu niedrig
4 = Ölstand zu niedrig
5 = Kühlmitteltemperatur zu hoch
6 = Kühlmittelstand zu niedrig
7 = Ladelufttemperatur
8 = reserviert (Abstellung über SAE-J1587)
9 = reserviert (Abstellung über VP2)
FEFFh = Sensorfehler
FFFFh = Nicht erreichbar
450182 450181 3,4 15313 Aftertreatment 1 Diesel Exhaust Fluid Tank Level 0.1 % EG300
0
Malfunction Lamp
Protect Lamp
Malfunction Lamp
Protect Lamp
450246 450245 5,6 15314 Aftertreatment 1 Diesel Exhaust Fluid Tank Tem‐ 1 °C EG300
perature 0
450247 450246 82 1,2,3, 15200 Engine Speed (j1939-EEC1) 0.1 rpm EG300
4 0
Notes
Value for Error indicator: 429496729,4
Value for Not available: 429496729,5
450253 450252 84 1,2,3, 15204 Engine Oil Temperature (j1939-ET1) 0.01 °C EG300
4 0
Notes
Value for Error indicator: 21474836,46
Value for Not available: 21474836,47 signed
450255 450254 5,6 15205 Engine Oil Pressure (j1939-EFL/P1) 1 kPa EG300
0
Notes
Value for Error indicator: 65534
Value for Not available: 65535
450256 450255 85 1,2,3, 15211 Fuel Rate (j1939-LFE) 0.01 L/h EG300
4 0
Notes
Value for Error indicator: 42949672,94
Value for Not available: 42949672,95
Notes
Value for Error indicator: 6553,4
Value for Not available: 6553,5
450261 450260 5,6 15210 Engine oil level (j1939-EFL/P1) 0.1 % EG300
0
Notes
Value for Error indicator: 6553,4
Value for Not available: 6553,5
450264 450263 5,6 15212 Barometric Pressure (j1939-AMB) 0.1 kPa EG300
0
Notes
Value for Error indicator: 6553,4
Value for Not available: 6553,5
450267 450266 5,6 15315 Aftertreatment 1 Diesel Exhaust Fluid Tank 2 0.1 % EG300
Level 0
450270 450269 5,6 15316 Aftertreatment 1 Diesel Exhaust Fluid Tank 2 1 °C EG300
Temperature 0
0 5,6 - internal
10086 no data receive at RPDO2 (function 1) at CAN Interface 2 Mask: 0080h Bit
10085 no data receive at RPDO1 (function 1) at CAN Interface 2 Mask: 0040h Bit
7 5,6 - internal
8 5,6 - internal
12 1,2 4153 Idle mode OR Ramp to rated state is active Mask: 8000h
(suppresses undervolt, underfreq, ...)
13 5,6 - internal
14 5,6 - internal
15 5,6 - internal
16 5,6 - internal
17 5,6 - internal
0 5,6 - internal
3 5,6 - internal
7 5,6 - internal
8 5,6 - internal
9 5,6 - internal
10 5,6 - internal
11 5,6 - internal
12 5,6 - internal
13 5,6 - internal
450012 450011 247 Total generator reactive power scaled defined by index var
3181 (modicon Address
450002)
AC Mains Values
450033 450032 259 Total mains reactive power scaled defined by index var
3181 (modicon Address
450002)
450044 450043
450045 450044
AC System Values
450049 450048
450050 450049
450051 450050
Discrete Outputs
Alarm Management
General
Engine
Generator
Mains
Digital Inputs
reserved
reserved
reserved
reserved
reserved
reserved
reserved
reserved
reserved
reserved
reserved
Flexible Thresholds
Alarms
Engine Management
450190 450189 15428 SPN of 10. entry low 16 bits of 19 bits of SPN
450191 450190 15429 15430 FMI / OC of 10. entry Hi-Byte: FMI Lo-Byte: OC
450196 450195 15304 J1939 Engine Stop Information (e.g., "Missing" Value="65535"
DEUTZ-specific EMR2 J1939-Message).
Please refer to specific ECU documentation "Error" Value="65279"
for details. Engine stop information
value is 0 to 250
Values
450223 450222 15222 Air Filter 1 Differential Pressure (SPN107) 0,01 kPa
Values
450455 450454
450457 450456
450459 450458
450461 450460
Generator
Mains
2 5,6 reserved
3 5,6 reserved
Engine
Alarms
Plausibility GCB feedback latched, Marine version only Mask: 0004h Bit
Reactive load sharing mismatch latched, Marine version only Mask: 0002h Bit
Active load sharing mismatch latched, Marine version only Mask: 0001h Bit
Plausibility GCB feedback latched (Marine version only) Mask: 0004h Bit
Reactive load sharing mismatch latched, Marine version only Mask: 0002h Bit
Active load sharing mismatch latched, Marine version only Mask: 0001h Bit
6 5,6 reserved
Flexible Thresholds
7 5,6 reserved
8 5,6 reserved
9 5,6 0 (reserve)
Free Alarm 4 (is also at MUX 5 to be compatibel to release 8) Mask: 0008h Bit
Free Alarm 3 (is also at MUX 5 to be compatibel to release 8) Mask: 0004h Bit
Free Alarm 2 (is also at MUX 5 to be compatibel to release 8) Mask: 0002h Bit
Free Alarm 1 (is also at MUX 5 to be compatibel to release 8) Mask: 0001h Bit
Free Alarm 4 (is also at MUX 5 to be compatibel to release 8) Mask: 0008h Bit
Free Alarm 3 (is also at MUX 5 to be compatibel to release 8) Mask: 0004h Bit
Free Alarm 2 (is also at MUX 5 to be compatibel to release 8) Mask: 0002h Bit
Free Alarm 1 (is also at MUX 5 to be compatibel to release 8) Mask: 0001h Bit
10 5,6 reserved
11 5,6 reserved
12 5, 6 reserved
13 5,6 0 (reserve)
14 5,6 reserved
15 5,6 reserved
16 5,6 reserved
17 3,4 10285 Alarms External Analog Inputs Wire Break latched (unac‐
knowledged)
17 5,6 reserved
Timing The time interval between two fast messages (TFast , i.e. the time
for refreshing a fast message) is configured with the parameter
"Transfer rate LS fast message" (parameter 9921 Ä p. 448). The
time intervals between refreshing a normal or slow messages
depend on this parameter as well according to the following
sequence:
n S0 – F – N0 – F – N1 – F – S1 – F – N0 – F – N1 – F – S2 – F –
N0 – F – N1 – F – S3 – F – N0 – F – N1 – F
n TFast = time interval between refreshing the fast message
n TNormal = time interval between refreshing a normal message =
3 x TFast
n TSlow = time interval between refreshing a slow message = 12 x
TFast
Time [ms] 0 50 100 150 200 250 300 350 400 450 500 550
Sent message S0 F N0 F N1 F S1 F N0 F N1 F
MUX # 0 3 1 3 2 3 4 3 1 3 2 3
Time [ms] 600 650 700 750 800 850 900 950 1000 1050 1100 1150
Sent message S2 F N0 F N1 F S3 F N0 F N1 F
MUX # 5 3 1 3 2 3 6 3 1 3 2 3
The maximum length of the CAN bus load share line depends on
"Transfer rate LS fast message" (parameter 9921 Ä p. 448).
The values in Ä Table 141 “ Load share line - max. length (32 par‐
ticipants)” on page 710 are valid for 32 participants and a bus
load of approx. 40 %.
F 0 3 MUX identifier
1 Generator real load capacity utilization rate, L-Byte Integer [‰], signed
2 GCB is closed
3 MCB is closed
4 Reserved
5 Not used
7 Not used
N0 0 1 Mux identifier
7 Not used
7 Not used
N1 0 2 MUX identifier
4 Not used
5 Not used
6 Not used
7 Not used
6 0 Command 1 to CB control
1 Command 2 to CB control
2 Command 3 to CB control
3 Command 4 to CB control
4 Command 5 to CB control
5 Command 6 to CB control
7 Not used
S0 0 0 MUX identifier
1 Protocol-Identifier
7 Not used
S1 0 4 MUX identifier
6 0-4 Priority Up to 32
7 Not used
S2 0 5 MUX identifier
7 Not used
7 Not used
S3 0 6 MUX identifier
7 Not used
1 1 - Discrete Inputs/Outputs 9 to 16 --
2 - internal
3,4,5,6 - internal
1 1 - Discrete Inputs/Outputs 17 to 24 --
2 - internal
3,4,5,6 - internal
1 1 - Discrete Inputs/Outputs 25 to 32 --
2 - internal
3,4,5,6 - internal
450017 450016 5 3,4,5, 216 Average Busbar Delta- 0.1 V 3000X New
6 Voltage T
450019 450018 6 1,2 4085 96.16 LM Internal Flag 16 Mask: 8000h Bit 3000X New
T
450020 450019 6 3,4,5, 234 Average Busbar Wye- 0.1 V 3500X New
6 Voltage T-P2
450047 450046 15 3,4,5, 231 Busbar Voltage L1-N 0.1 V 3500X New
6 T-P2
450050 450049 16 3,4,5, 232 Busbar Voltage L2-N 0.1 V 3500X New
6 T-P2
External Mains kW value can be picked up through the according Analog Input.
450058 450057 19 1,2 4086 Operating Range Monitoring Mask FF00h 3000X New
Code Number T
450059 450058 19 3,4,5, 136 Total gen. reactive power 1 var 3000X
6 T
450062 450061 20 3,4,5, 150 Total mains reactive power 1 var 3000X
6 T
External Mains kW value can be picked up through the according Analog Input.
450064 450063 21 1,2 10133 05.01 Engine Over speed 1 Mask: 8000h Bit 3000X
latched T
450067 450066 22 1,2 4087 08.30 Timeout Synchronisa‐ Mask: 8000h Bit 3000X
tion GCB latched T
17.01 Active load share mis‐ Mask: 0001h Bit 3000X New
match latched T
450071 450070 23 3,4,5, 193 Busbar: Voltage L3-L1 0.1 V 3500X New
6 T-P2
450073 450072 24 1,2 10134 06.01 Generator over fre‐ Mask: 8000h Bit 3000X
quency 1 latched T
450076 450075 25 1,2 10138 06.16 Generator unbalanced Mask: 8000h Bit 3000X
load 1 latched T
450079 450078 26 1,2 10135 07.06 Mains over frequency Mask: 8000h Bit 3000X
1 latched T
450082 450081 27 1,2 10278 07.21 Mains import power 1 Mask: 8000h Bit 3000X
latched T
450085 450084 28 1,2 10132 09.01 Discrete input 1 Mask: 8000h Bit 3000X
latched T
450088 450087 29 1,2 10283 09.13 Discrete input 13 Mask: 8000h Bit 3500X
latched T-P2
450091 450090 30 1,2 16377 12.16 External discrete input Mask: 8000h Bit 3000X
16 latched T
450094 450093 31 1,2 10279 15.16 Flexible limit 16 Mask: 8000h Bit 3000X
latched T
450097 450096 32 1,2 10280 15.32 Flexible limit 32 Mask: 8000h Bit 3000X
latched T
450106 450105 35 1,2 4089 01.11 New Alarm triggered Mask: 8000h Bit 3000X New
T
450111 450110 36 5,6 10285 25.16 Ext. analog input 16 Mask: 8000h Bit 3000X
wire break T
450112 450111 37 1,2 10107 13.01 Relay-Output 1 (Self- Mask: 8000h Bit 3000X
test-relay) T
450113 450112 37 3,4 10109 13.13 Relay-Output 13 Mask: 8000h Bit 3500X
T-P2
450114 450113 37 5,6 8005 98.16 LM External DO 16 Mask: 8000h Bit 3000X
T
450122 450121 40 3,4,5, 2520 Gen. real energy 0,01 MWh 3000X
6 T
450125 450124 41 3,4,5, 2522 Gen. positive reactive 0,01 Mvarh 3000X
6 energy T
450127 450126 42 1,2 2558 Hours until next mainte‐ 0,1 h 3000X
nance T
450136 450135 45 1,2 4090 Idle mode OR Ramp to rated Mask: 8000h Bit 3000X
active (suppresses under‐ T
volt., underfreq., ...)
450137 450136 45 3,4 4091 03.02 Starter / Crank is Mask: 8000h Bit 3000X
active T
450138 450137 45 5,6 4155 03.20 3-Pos. Controller Mask: 8000h Bit 3000X
Freq./Power raise T
450139 450138 46 1,2 4156 04.16 GGB is closed Mask: 8000h Bit 3500X
T
450140 450139 46 3,4 4092 04.13 Remote Start request Mask: 8000h Bit 3000X New
T
450141 450140 46 5,6 10284 12.32 External discrete input Mask: 8000h Bit 3000X
32 latched T
450142 450141 47 1,2 8009 98.32 LM External DO 32 Mask: 8000h Bit 3000X
T
450166 450165 55 1,2 4093 08.34 GGB fail to close Mask: 8000h Bit 3500X
latched T
The Load share Diagnostic function suspects the own device as not working
properly
450169 450168 56 1,2 4157 28.01 Command 1 to LS5 Mask: 8000h Bit 3500X
(OR) T
450177 450176 58 5,6 240 System total real power 0.01 % 3000X
T
450184 450183 61 1,2 2556 Days until next maintenance 1 d 3000X rees‐
T tab‐
lished
450185 450184 61 3,4,5, 233 Busbar: Voltage L3-N 0.1 V 3500X rees‐
6 T-P2 tab‐
lished
450187 450186 62 1,2 4094 02.03 Generator voltage in Mask: 8000h Bit 3000X rees‐
range T tab‐
lished
02.11 Mains voltage and fre‐ Mask: 2000h Bit 3000X rees‐
quency in range T tab‐
lished
450188 450187 62 3,4,5, 5642 Setpoint reactive power 0,1 kvar 3000X rees‐
6 T tab‐
lished
450190 450189 63 1,2 4095 96.32 LM Internal Flag 32 Mask: 8000h Bit 3000X rees‐
T tab‐
lished
450192 450191 63 5,6 9642 Free AnalogManager Value 3000X 9642 rees‐
1 T is long tab‐
(for lished
single
acces
s)
450193 450192 64 1,2 9646 Free AnalogManager Value 3000X 9646 rees‐
2 T is long tab‐
(for lished
single
acces
s)
450194 450193 64 3,4 9650 Free AnalogManager Value 3000X 9650 rees‐
3 T is long tab‐
(for lished
single
acces
s)
450195 450194 64 5,6 9654 Free AnalogManager Value 3000X 9654 rees‐
4 T is long tab‐
(for lished
single
acces
s)
450196 450195 65 1,2 9658 Free AnalogManager Value 3000X 9658 rees‐
5 T is long tab‐
(for lished
single
acces
s)
450197 450196 65 3,4 9662 Free AnalogManager Value 3000X 9662 rees‐
6 T is long tab‐
(for lished
single
acces
s)
450198 450197 65 5,6 9666 Free AnalogManager Value 3000X 9666 rees‐
7 T is long tab‐
(for lished
single
acces
s)
450199 450198 66 1,2 9670 Free AnalogManager Value 3000X 9670 rees‐
8 T is long tab‐
(for lished
single
acces
s)
450200 450199 66 3,4 9674 Free AnalogManager Value 3000X 9674 rees‐
9 T is long tab‐
(for lished
single
acces
s)
450201 450200 66 5,6 9678 Free AnalogManager Value 3000X 9678 rees‐
10 T is long tab‐
(for lished
single
acces
s)
450202 450201 67 1,2 9682 Free AnalogManager Value 3000X 9682 rees‐
11 T is long tab‐
(for lished
single
acces
s)
450203 450202 67 3,4 9686 Free AnalogManager Value 3000X 9686 rees‐
12 T is long tab‐
(for lished
single
acces
s)
450204 450203 67 5,6 9690 Free AnalogManager Value 3000X 9690 rees‐
13 T is long tab‐
(for lished
single
acces
s)
450205 450204 68 1,2 9694 Free AnalogManager Value 3000X 9694 rees‐
14 T is long tab‐
(for lished
single
acces
s)
450211 450210 70 1,2 8908 81.29 Engine Coolant Tem‐ 1 °C/°F 3000X rees‐
[°C] / perature (HMI) T tab‐
8910 [°F] lished
450212 450211 70 3,4 8904 81.25 Engine Oil Pressure 0.1bar/1psi bar/ps 3000X rees‐
[0.1bar] / (HMI) i T tab‐
8909 lished
[psi]
Unit depends on parameter 3630 (bar/psi).
450213 450212 70 5,6 4096 Monitored Number of Mask FF00h 3000X Load rees‐
easYgen communicating T share tab‐
Diag‐ lished
nostic
450214 450213 71 1,2 4097 Monitored Number of LS5 Mask FF00h 3500X LS-5 rees‐
communicating T Diag‐ tab‐
nostic lished
450215 450214 71 3,4 4098 Device number of missing Mask FFFFh 3500X LS-5 rees‐
LS-5 (33-48) T Diag‐ tab‐
nostic lished
450216 450215 71 5,6 4099 Device number of missing Mask FFFFh 3500X LS-5 rees‐
LS-5 (49-64) T Diag‐ tab‐
nostic lished
450217 450216 72 1,2 10282 16.16 Free alarm 16 latched Mask: 8000h Bit 3000X rees‐
T tab‐
lished
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450011 450010 16 bits signed 246 Total generator power format defined by W EG3000X
index 3181 (mod‐ T
icon Adress
450002)
450012 450011 16 bits signed 247 Total generator reactive format defined by var EG3000X
power index 3181 (mod‐ T
icon Adress
450002)
450013 450012 16 bits signed 160 Generator power factor 0.001 EG3000X
T
450014 450013 16 bits signed 248 Generator voltage L1-L2 format defined by V EG3000X
index 3182 (mod‐ T
icon Adress
450003)
450015 450014 16 bits signed 249 Generator voltage L2-L3 format defined by V EG3000X
index 3182 (mod‐ T
icon Adress
450003)
450016 450015 16 bits signed 250 Generator voltage L3-L1 format defined by V EG3000X
index 3182 (mod‐ T
icon Adress
450003)
450017 450016 16 bits signed 251 Generator voltage L1-N format defined by V EG3000X
index 3182 (mod‐ T
icon Adress
450003)
450018 450017 16 bits signed 252 Generator voltage L2-N format defined by V EG3000X
index 3182 (mod‐ T
icon Adress
450003)
450019 450018 16 bits signed 253 Generator voltage L3-N format defined by V EG3000X
index 3182 (mod‐ T
icon Adress
450003)
450020 450019 16 bits signed 255 Generator current L1 format defined by A EG3000X
index 3183 (mod‐ T
icon Adress
450004)
450021 450020 16 bits signed 256 Generator current L2 format defined by A EG3000X
index 3183 (mod‐ T
icon Adress
450004)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450022 450021 16 bits signed 257 Generator current L3 format defined by A EG3000X
index 3183 (mod‐ T
icon Adress
450004)
450024 450023 16 bits signed 254 Busbar Voltage L1-L2 format defined by V EG3000X
index 3182 (mod‐ T
icon Adress
450003)
450025 450024 16 bits signed 279 Busbar Voltage L2-L3 format defined by V EG3500X
index 3182 (mod‐ T-P2
icon Adress
450003)
450026 450025 16 bits signed 280 Busbar Voltage L3-L1 format defined by V EG3500X
index 3182 (mod‐ T-P2
icon Adress
450003)
450027 450026 16 bits signed 281 Busbar Voltage L1-N format defined by V EG3500X
index 3182 (mod‐ T-P2
icon Adress
450003)
450028 450027 16 bits signed 282 Busbar Voltage L2-N format defined by V EG3500X
index 3182 (mod‐ T-P2
icon Adress
450003)
AC Mains values
450032 450031 16 bits signed 258 Total mains active power format defined by W 3000XT
index 3181 (mod‐
icon Address
450002)
450033 450032 16 bits signed 259 Total mains reactive power format defined by var 3000XT
index 3181 (mod‐
icon Address
450002)
450034 450033 16 bits signed 208 Mains power factor 0.001 3000XT
450035 450034 16 bits signed 260 Mains voltage L1-L2 format defined by V 3000XT
index 3182 (mod‐
icon Address
450003)
450036 450035 16 bits signed 261 Mains voltage L2-L3 format defined by V 3000XT
index 3182 (mod‐
icon Address
450003)
450037 450036 16 bits signed 262 Mains voltage L3-L1 format defined by V 3000XT
index 3182 (mod‐
icon Address
450003)
450038 450037 16 bits signed 263 Mains voltage L1-N format defined by V 3000XT
index 3182 (mod‐
icon Address
450003)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450039 450038 16 bits signed 264 Mains voltage L2-N format defined by V 3000XT
index 3182 (mod‐
icon Address
450003)
450040 450039 16 bits signed 265 Mains voltage L3-N format defined by V 3000XT
index 3182 (mod‐
icon Address
450003)
450041 450040 16 bits signed 266 Mains current L1 format defined by A 3000XT
index 3183 (mod‐
icon Address
450004)
450044 450043 16 bits signed 267 Average LS5 Delta Mains format defined by V 3500XT
voltage L-L index 3182
450045 450044 16 bits signed 268 Average LS5 Wye Mains format defined by V 3500XT
voltage L-N index 3182
AC System values
450046 450045 16 bits signed 239 Nominal real power in 0.01 % 3000XT
system
450047 450046 16 bits signed 240 Real power in system 0.01 % 3000XT
450048 450047 16 bits signed 241 Reserve real power in 0.01 % 3000XT
system
450049 450048 16 bits signed 269 Active power LS5 format defined by W 3500XT
index 3181
450050 450049 16 bits signed 270 Reactive power LS5 format defined by var 3500XT
index 3181
450051 450050 16 bits signed 4608 Average LS5 Mains delta 0.01 Hz 3500XT
frequency L-L
450052 450051 16 bits signed 10100 Engine Pickup speed 1 rpm 3000XT
450056 450055 16 bits signed 2558 Hours until next mainte‐ 1 h 3000XT
nance
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450071 450070 16 bits signed 10317 Analog output 3 changeable % 3000XT New
450075 450074 16 bits signed 10170 External Analog input 1 changeable 3000XT
450076 450075 16 bits signed 10171 External Analog input 2 changeable 3000XT
450077 450076 16 bits signed 10172 External Analog input 3 changeable 3000XT
450078 450077 16 bits signed 10173 External Analog input 4 changeable 3000XT
450079 450078 16 bits signed 10174 External Analog input 5 changeable 3000XT
450080 450079 16 bits signed 10175 External Analog input 6 changeable 3000XT
450081 450080 16 bits signed 10176 External Analog input 7 changeable 3000XT
450082 450081 16 bits signed 10177 External Analog input 8 changeable 3000XT
450083 450082 16 bits signed 10178 External Analog input 9 changeable 3000XT
450084 450083 16 bits signed 10179 External Analog input 10 changeable 3000XT
450085 450084 16 bits signed 10180 External Analog input 11 changeable 3000XT
450086 450085 16 bits signed 10181 External Analog input 12 changeable 3000XT
450087 450086 16 bits signed 10182 External Analog input 13 changeable 3000XT
450088 450087 16 bits signed 10183 External Analog input 14 changeable 3000XT
450089 450088 16 bits signed 10184 External Analog input 15 changeable 3000XT
450090 450089 16 bits signed 10185 External Analog input 16 changeable 3000XT
450091 450090 16 bits signed 10245 External Analog Output 1 0.01 % 3000XT
450092 450091 16 bits signed 10255 External Analog Output 2 0.01 % 3000XT
450093 450092 16 bits signed 10265 External Analog Output 3 0.01 % 3000XT
450094 450093 16 bits signed 10275 External Analog Output 4 0.01 % 3000XT
450095 450094 16 bits signed 2556 Days until next mainte‐ 1 days 3000XT
nance
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450097 450096 16 bits signed "_" Engine Coolant Tempera‐ 1 °C/°F 3000XT New
ture (HMI)
The
same
Value
as
shown
in HMI
450098 450097 16 bits signed "-" Engine Oil Pressure (HMI) 0.1bar/psi bar/p 3000XT New
si
The
same
Value
as
shown
in HMI
450100 450099 16 bits bit array "-" Control mode (STOP/ Mask:000Fh enum 3000XT New
AUTO/MANUAL/TEST) 1=AUTO .
2=STOP TEST
4=MANUAL include
8=TEST d
450101 450100 16 bits bit array 10202 State Display Id description see enum 3000XT
operation manual .
status messages
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Discrete Outputs
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Alarm Management
General
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
4056 05.11 Charge fail (D+ func‐ Mask: 1000h Bit 3000XT
tionality) latched
15125 05.13 ECU red lamp alarm Mask: 0002h Bit 3000XT
latched
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450120 450119 16 bits 4086 Operating Range Moni‐ Mask: FF00h 3000XT New
toring Code Number
Oper‐
ating
range
Error-
Code
Alarm Management
Engine
2112 05.01 Engine Over speed 1 Mask: 8000h Bit 3000XT Only
latched rename
d
accordi
ng to
LM
system
2113 05.02 Engine Over speed 2 Mask: 4000h Bit 3000XT Only
latched rename
d
accordi
ng to
LM
system
2162 05.03 Engine under speed Mask: 2000h Bit 3000XT Only
1 latched rename
d
accordi
ng to
LM
system
2163 05.04 Engine under speed Mask: 1000h Bit 3000XT Only
2 latched rename
d
accordi
ng to
LM
system
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
2603 08.05 GCB fail to close Mask: 0100h Bit 3000XT Only
latched rename
d
accordi
ng to
LM
system
2604 08.06 GCB fail to open Mask: 0080h Bit 3000XT Only
latched rename
d
accordi
ng to
LM
system
2623 08.07 MCB fail to close Mask: 0040h Bit 3000XT Only
latched rename
d
accordi
ng to
LM
system
2624 08.08 MCB fail to open Mask: 0020h Bit 3000XT Only
latched rename
d
accordi
ng to
LM
system
3325 05.08 Start fail detected Mask: 0008h Bit 3000XT Only
latched rename
d
accordi
ng to
LM
system
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Alarm Management
Generator
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Alarm Management
Mains
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
3975 Mains Phase rotation mis‐ Mask: 0004h Bit 3000XT New
match
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Alarm Management
Digital Inputs
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Alarm Management
Flexible Thresholds
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Alarm Management
DC Analogue Values Wirebreak
450160 450159 16 bits bit array 10137 Alarms Analog Inputs Wire
Break latched (unacknowl‐
edged)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450161 450160 16 bits bit array 4173 Alarms Analog Inputs Wire
Break active
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Alarm Management
Other Alarms
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
5153 16.09 Free alarm 9 latched Mask: 0100h Bit 3000XT New
5147 16.08 Free alarm 8 latched Mask: 0080h Bit 3000XT New
5141 16.07 Free alarm 7 latched Mask: 0040h Bit 3000XT New
5135 16.06 Free alarm 6 latched Mask: 0020h Bit 3000XT New
5129 16.05 Free alarm 5 latched Mask: 0010h Bit 3000XT New
5123 16.04 Free alarm 4 latched Mask: 0008h Bit 3000XT New
5117 16.03 Free alarm 3 latched Mask: 0004h Bit 3000XT New
5111 16.02 Free alarm 2 latched Mask: 0002h Bit 3000XT New
5105 16.01 Free alarm 1 latched Mask: 0001h Bit 3000XT New
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Engine Management
Active Diagnostic Trouble Code (DM1) 1-10 (SPN Range 0…65535)full SPN value at 450425-450444
450172 450171 16 bits signed 15400 SPN of 1. entry low 16 bits of 19 3000XT
bits of SPN
450173 450172 16 bits byte 15401 FMI / OC of 1. entry Hi-Byte: FMI Lo- 3000XT
array 15402 Byte: OC
450174 450173 16 bits signed 15403 SPN of 2. entry low 16 bits of 19 3000XT
bits of SPN
450175 450174 16 bits byte 15404 FMI / OC of 2. entry Hi-Byte: FMI Lo- 3000XT
array 15405 Byte: OC
450176 450175 16 bits signed 15406 SPN of 3. entry low 16 bits of 19 3000XT
bits of SPN
450177 450176 16 bits byte 15407 FMI / OC of 3. entry Hi-Byte: FMI Lo- 3000XT
array 15408 Byte: OC
450178 450177 16 bits signed 15409 SPN of 4. entry low 16 bits of 19 3000XT
bits of SPN
450179 450178 16 bits byte 15410 FMI / OC of 4. entry Hi-Byte: FMI Lo- 3000XT
array 15411 Byte: OC
450180 450179 16 bits signed 15412 SPN of 5. entry low 16 bits of 19 3000XT
bits of SPN
450181 450180 16 bits byte 15413 FMI / OC of 5. entry Hi-Byte: FMI Lo- 3000XT
array 15414 Byte: OC
450182 450181 16 bits signed 15415 SPN of 6. entry low 16 bits of 19 3000XT
bits of SPN
450183 450182 16 bits byte 15416 FMI / OC of 6. entry Hi-Byte: FMI Lo- 3000XT
array 15418 Byte: OC
450184 450183 16 bits signed 15419 SPN of 7. entry low 16 bits of 19 3000XT
bits of SPN
450185 450184 16 bits byte 15420 FMI / OC of 7. entry Hi-Byte: FMI Lo- 3000XT
array 15421 Byte: OC
450186 450185 16 bits signed 15422 SPN of 8. entry low 16 bits of 19 3000XT
bits of SPN
450187 450186 16 bits byte 15423 FMI / OC of 8. entry Hi-Byte: FMI Lo- 3000XT
array 15424 Byte: OC
450188 450187 16 bits signed 15425 SPN of 9. entry low 16 bits of 19 3000XT
bits of SPN
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450189 450188 16 bits byte 15426 FMI / OC of 9. entry Hi-Byte: FMI Lo- 3000XT
array 15427 Byte: OC
450190 450189 16 bits signed 15428 SPN of 10. entry low 16 bits of 19 3000XT
bits of SPN
450191 450190 16 bits byte 15429 FMI / OC of 10. entry Hi-Byte: FMI Lo- 3000XT
array 15430 Byte: OC
Engine Management
DM1 Lamp Status
450192 450191 16 bits bit array 15395 J1939 Lamp Status DM1
Engine Management
DM2 Lamp Status
450193 450192 16 bits bit array 15445 J1939 Lamp Status DM2
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Engine Management
Especially Failure Codes
450194 450193 16 bits bit array 15109 J1939 MTU ADEC ECU 1 3000XT
Failure Codes
450196 450195 16 bits bit array 15304 J1939 EMR2 Engine Stop "Missing" enum 3000XT
Information (extracted from Value="65535" .
DEUTZ-specific J1939- "Error"
Message) 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"
"Type 3"
Value="3" "Type
2" Value="2"
"Type 1"
Value="1" "Type
0" Value="0"
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Engine Management
Values
450202 450201 16 bits signed 15308 Engine Speed (SPN 190) 1 rpm 3000XT
450205 450204 16 bits signed 15309 Engine Oil Temperature 1 0.1 °C 3000XT
(SPN 175)
450206 450205 16 bits signed 15205 Engine Oil Pressure (SPN 1 kPa 3000XT
100)
450207 450206 16 bits signed 15307 Fuel Rate (SPN 183) 0.1 L/h 3000XT
450208 450207 16 bits signed 15206 Coolant Level (SPN 111) 0.1 % 3000XT
450209 450208 16 bits signed 15207 Throttle position (SPN 91) 0.1 % 3000XT
450211 450210 16 bits signed 15210 Engine oil level (SPN 98) 0.1 % 3000XT
450212 450211 16 bits signed 15214 Boost pressure (SPN 102) 1 kPa 3000XT
450214 450213 16 bits signed 15212 Barometric Pressure (SPN 0.1 kPa 3000XT
108)
450215 450214 16 bits signed 15213 Air inlet temperature (SPN 1 °C 3000XT
172)
450216 450215 16 bits signed 15209 Actual engine torque (SPN 1 % 3000XT
513)
450217 450216 16 bits signed 15299 Exhaust Gas Temp.(SPN 0.1 °C 3000XT
173)
450219 450218 16 bits signed 15218 Fuel Delivery Pressure 1 kPa 3000XT
(SPN94)
450220 450219 16 bits signed 15219 Fuel Filter Differential Pres‐ 1 kPa 3000XT
sure (SPN95)
450222 450221 16 bits signed 15221 Turbo Air Inlet Pressure 1 kPa 3000XT
(SPN106)
450223 450222 16 bits signed 15222 Air Filter 1 Differential Pres‐ 0.01 kPa 3000XT
sure (SPN107)
450224 450223 16 bits signed 15223 Coolant Pressure (SPN109) 1 kPa 3000XT
450225 450224 16 bits signed 15224 Transmission Oil Pressure 1 kPa 3000XT
(SPN127)
450226 450225 16 bits signed 15225 Fuel Rail Pressure 0.1 MPa 3000XT
(SPN157)
450227 450226 16 bits signed 15226 Ambient Air Temperature 0.1 °C 3000XT
(SPN171)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450228 450227 16 bits signed 15227 Turbo Oil Temperature 0.1 °C 3000XT
(SPN176)
450229 450228 16 bits signed 15228 Transmission Oil Tempera‐ 0.1 °C 3000XT
ture (SPN177)
450232 450231 16 bits signed 15209 Actual engine torque (SPN 1 % 3000XT
513)
450241 450240 16 bits signed 15239 Engine Intercooler Thermo‐ 0.1 % 3000XT
stat Opening (SPN1134)
450242 450241 16 bits signed 15240 Engine Oil Temperature 2 0.1 °C 3000XT
(SPN1135)
450243 450242 16 bits signed 15241 Engine ECU Temperature 0.1 °C 3000XT
(SPN1136)
450244 450243 16 bits signed 15242 Exhaust Gas Port 1 Tem‐ 0.1 °C 3000XT
peratures (SPN1137)
450245 450244 16 bits signed 15243 Exhaust Gas Port 2 Tem‐ 0.1 °C 3000XT
peratures (SPN1138)
450246 450245 16 bits signed 15244 Exhaust Gas Port 3 Tem‐ 0.1 °C 3000XT
peratures (SPN1139)
450247 450246 16 bits signed 15245 Exhaust Gas Port 4 Tem‐ 0.1 °C 3000XT
peratures (SPN1140)
450248 450247 16 bits signed 15246 Exhaust Gas Port 5 Tem‐ 0.1 °C 3000XT
peratures (SPN1141)
450249 450248 16 bits signed 15247 Exhaust Gas Port 6 Tem‐ 0.1 °C 3000XT
peratures (SPN1142)
450250 450249 16 bits signed 15248 Exhaust Gas Port 7 Tem‐ 0.1 °C 3000XT
peratures (SPN1143)
450251 450250 16 bits signed 15249 Exhaust Gas Port 8 Tem‐ 0.1 °C 3000XT
peratures (SPN1144)
450252 450251 16 bits signed 15250 Exhaust Gas Port 9 Tem‐ 0.1 °C 3000XT
peratures (SPN1145)
450253 450252 16 bits signed 15251 Exhaust Gas Port 10 Tem‐ 0.1 °C 3000XT
peratures (SPN1146)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450254 450253 16 bits signed 15252 Exhaust Gas Port 11 Tem‐ 0.1 °C 3000XT
peratures (SPN1147)
450255 450254 16 bits signed 15253 Exhaust Gas Port 12 Tem‐ 0.1 °C 3000XT
peratures (SPN1148)
450256 450255 16 bits signed 15254 Exhaust Gas Port 13 Tem‐ 0.1 °C 3000XT
peratures (SPN1149)
450257 450256 16 bits signed 15255 Exhaust Gas Port 14 Tem‐ 0.1 °C 3000XT
peratures (SPN1150)
450258 450257 16 bits signed 15256 Exhaust Gas Port 15 Tem‐ 0.1 °C 3000XT
peratures (SPN1151)
450259 450258 16 bits signed 15257 Exhaust Gas Port 16 Tem‐ 0.1 °C 3000XT
peratures (SPN1152)
450260 450259 16 bits signed 15258 Exhaust Gas Port 17 Tem‐ 0.1 °C 3000XT
peratures (SPN1153)
450261 450260 16 bits signed 15259 Exhaust Gas Port 18 Tem‐ 0.1 °C 3000XT
peratures (SPN1154)
450262 450261 16 bits signed 15260 Exhaust Gas Port 19 Tem‐ 0.1 °C 3000XT
peratures (SPN1155)
450263 450262 16 bits signed 15261 Exhaust Gas Port 20 Tem‐ 0.1 °C 3000XT
peratures (SPN1156)
450264 450263 16 bits signed 15262 Main Bearing 1 Tempera‐ 0.1 °C 3000XT
tures (SPN1157)
450265 450264 16 bits signed 15263 Main Bearing 2 Tempera‐ 0.1 °C 3000XT
tures (SPN1158)
450266 450265 16 bits signed 15264 Main Bearing 3 Tempera‐ 0.1 °C 3000XT
tures (SPN1159)
450267 450266 16 bits signed 15265 Main Bearing 4 Tempera‐ 0.1 °C 3000XT
tures (SPN1160)
450268 450267 16 bits signed 15266 Main Bearing 5 Tempera‐ 0.1 °C 3000XT
tures (SPN1161)
450269 450268 16 bits signed 15267 Main Bearing 6 Tempera‐ 0.1 °C 3000XT
tures (SPN1162)
450270 450269 16 bits signed 15268 Main Bearing 7 Tempera‐ 0.1 °C 3000XT
tures (SPN1163)
450271 450270 16 bits signed 15269 Main Bearing 8 Tempera‐ 0.1 °C 3000XT
tures (SPN1164)
450272 450271 16 bits signed 15270 Main Bearing 9 Tempera‐ 0.1 °C 3000XT
tures (SPN1165)
450273 450272 16 bits signed 15271 Main Bearing 10 Tempera‐ 0.1 °C 3000XT
tures (SPN1166)
450274 450273 16 bits signed 15272 Main Bearing 11 Tempera‐ 0.1 °C 3000XT
tures (SPN1167)
450275 450274 16 bits signed 15273 Turbo 1 Compressor Inlet 0.1 °C 3000XT
Temperatures (SPN1172)
450276 450275 16 bits signed 15274 Turbo 2 Compressor Inlet 0.1 °C 3000XT
Temperatures (SPN1173)
450277 450276 16 bits signed 15275 Turbo 3 Compressor Inlet 0.1 °C 3000XT
Temperatures (SPN1174)
450278 450277 16 bits signed 15276 Turbo 4 Compressor Inlet 0.1 °C 3000XT
Temperatures (SPN1175)
450279 450278 16 bits signed 15277 Turbo 1 Compressor Inlet 1 kPa 3000XT
Pressure (SPN1176)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450280 450279 16 bits signed 15278 Turbo 2 Compressor Inlet 1 kPa 3000XT
Pressure (SPN1177)
450281 450280 16 bits signed 15279 Turbo 3 Compressor Inlet 1 kPa 3000XT
Pressure (SPN1178)
450282 450281 16 bits signed 15280 Turbo 4 Compressor Inlet 1 kPa 3000XT
Pressure (SPN1179)
450283 450282 16 bits signed 15281 Turbo 1 Turbine Inlet Tem‐ 0.1 °C 3000XT
perature (SPN1180)
450284 450283 16 bits signed 15282 Turbo 2 Turbine Inlet Tem‐ 0.1 °C 3000XT
perature (SPN 1181)
450285 450284 16 bits signed 15283 Turbo 3 Turbine Inlet Tem‐ 0.1 °C 3000XT
perature (SPN 1182)
450286 450285 16 bits signed 15284 Turbo 4 Turbine Inlet Tem‐ 0.1 °C 3000XT
perature (SPN1183)
450287 450286 16 bits signed 15285 Turbo 1 Turbine Outlet 0.1 °C 3000XT
Temperature (SPN1184)
450288 450287 16 bits signed 15286 Turbo 2 Turbine Outlet 0.1 °C 3000XT
Temperature (SPN1185)
450289 450288 16 bits signed 15287 Turbo 3 Turbine Outlet 0.1 °C 3000XT
Temperature (SPN 1186)
450290 450289 16 bits signed 15288 Turbo 4 Turbine Outlet 0.1 °C 3000XT
Temperature (SPN1187)
450291 450290 16 bits signed 15289 Engine Aux. Coolant Pres‐ 1 kPa 3000XT
sure (SPN1203)
450292 450291 16 bits signed 15290 Pre-filter Oil Pressure 1 kPa 3000XT
(SPN1208)
450293 450292 16 bits signed 15291 Engine Aux. Coolant Tem‐ 1 °C 3000XT
perature (SPN1212)
450294 450293 16 bits signed 15292 Fuel Filter Differential Pres‐ 1 kPa 3000XT
sure (SPN1382)
450299 450298 16 bits signed 15297 Right Exhaust Gas Temper‐ 0.1 °C 3000XT
ature (SPN2433)
450300 450299 16 bits signed 15298 Left Exhaust Gas Tempera‐ 0.1 °C 3000XT
ture (SPN2434)
450301 450300 16 bits signed 15310 Turbo 1 Compr. Outlet 0.1 °C 3000XT
Temperature (SPN2629)
450302 450301 16 bits signed 15311 Engine derate request 0.1 % 3000XT
(SPN3644)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450308 450307 16 bits signed 12807 Exhaust Gas Temperature 0.1 °C 3000XT
Average(SPN 4151)
450309 450308 16 bits signed 12809 Exhaust Gas Temperature 0.1 °C 3000XT
Average Bank 1 (SPN
4153)
450310 450309 16 bits signed 12812 Exhaust Gas Temperature 0.1 °C 3000XT
Average Bank 2 (SPN
4152)
450311 450310 16 bits signed 12016 Fuel level 1 (SPN 96) 0.1 % with rees‐
release tab‐
1.13 lished
450312 450311 16 bits signed 12017 Fuel level 2 (SPN 38) 0.1 % with rees‐
release tab‐
1.13 lished
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Miscellaneous
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450387 450386 16 bits 4096 Monitored Number of Mask FF00h 3000XT rees‐
easYgen communicating tab‐
lished
Load
share
Diag‐
nostic
450388 450387 16 bits 4097 Monitored Number of LS5 Mask FF00h 3500XT rees‐
communicating tab‐
lished
LS-5
Diag‐
nostic
450389 450388 16 bits 4098 Device number of missing Mask FFFFh 3500XT rees‐
LS-5 (33-48) tab‐
lished
LS-5
Diag‐
nostic
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450390 450389 16 bits 4099 Device number of missing Mask FFFFh 3500XT rees‐
LS-5 (49-64) tab‐
lished
LS-5
Diag‐
nostic
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450391 450390 16 bits 181 Phase angle busbar1-gen‐ 0.1 ° 3000XT New
erator L1-L2
450392 450391 16 bits 184 Phase angle mains- 0.1 ° 3000XT New
busbar1 L1-L2
450393 450392 16 bits 4641 Delta voltage busbar1-gen‐ 0.1 % 3000XT New
erator
450394 450393 16 bits 4640 Delta frequency busbar1- 0.01 Hz 3000XT New
generator
450395 450394 16 bits 4607 Phase angle compensated 0.1 ° 3000XT New
generator-busbar1 L1-L2
450396 450395 16 bits 139 Generator power factor L1 0.001 3000XT New
450397 450396 16 bits 203 Generator power factor L2 0.001 3000XT New
450398 450397 16 bits 204 Generator power factor L3 0.001 3000XT New
450399 450398 16 bits 8850 Voltage increase monitored 0.01 % 3000XT New
value
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Int32
(Long)
450411 450410 32 bits signed 135 Total gen. active power 1 W 3000XT
450413 450412 32 bits signed 136 Total gen. reactive power 1 var 3000XT
450415 450414 32 bits signed 137 Total gen. apparent power 1 VA 3000XT
450417 450416 32 bits signed 170 Average Gen. Wye-Voltage 0.1 V 3000XT
450419 450418 32 bits signed 171 Average Gen. Delta- 0.1 V 3000XT
Voltage
450421 450420 32 bits signed 216 Average Busbar Delta- 0.1 V 3000XT
Voltage
450423 450422 32 bits signed 185 Av. Gen. Current 0.001 A 3000XT
450431 450430 32 bits signed 161 Meas. ground current 0.001 A 3000XT
450433 450432 32 bits signed 159 Calculated ground current 0.001 A 3000XT
450435 450434 32 bits signed 108 Gen. voltage L1-L2 0.1 V 3000XT
450437 450436 32 bits signed 109 Gen. voltage L2-L3 0.1 V 3000XT
450439 450438 32 bits signed 110 Gen. voltage L3-L1 0.1 V 3000XT
450441 450440 32 bits signed 114 Gen. voltage L1-N 0.1 V 3000XT
450443 450442 32 bits signed 115 Gen. voltage L2-N 0.1 V 3000XT
450445 450444 32 bits signed 116 Gen. voltage L3-N 0.1 V 3000XT
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450453 450452 32 bits signed 182 Busbar 1: voltage L1-L2 0.1 V 3000XT
450455 450454 32 bits signed 2520 Gen. real energy 0,01 MWh 3000XT
450457 450456 32 bits signed 2522 Gen. positive reactive 0,01 Mvar 3000XT
energy h
450459 450458 32 bits signed 2568 Gen. hours of operation 0,01 h 3000XT
450461 450460 32 bits signed 5542 Setpoint active power 0,1 kW 3000XT
450465 450464 32 bits signed 234 Average Busbar Wye- 0.1 V 3000XT New
Voltage
450467 450466 32 bits signed 189 Busbar 1: voltage L2-L3 0.1 V 3500XT- New
P2
450469 450468 32 bits signed 193 Busbar 1: voltage L3-L1 0.1 V 3500XT- New
P2
AC Mains values
450473 450472 32 bits signed 140 Total mains active power 1 W 3000XT
450475 450474 32 bits signed 150 Total mains reactive power 1 var 3000XT
450477 450476 32 bits signed 173 Average Mains Wye- 0.1 V 3000XT
Voltage
450479 450478 32 bits signed 174 Av. Mains Delta-Voltage 0.1 V 3000XT
450481 450480 32 bits signed 207 Av. Mains Current 0.001 A 3000XT
450489 450488 32 bits signed 118 Mains voltage L1-L2 0.1 V 3000XT
450491 450490 32 bits signed 119 Mains voltage L2-L3 0.1 V 3000XT
450493 450492 32 bits signed 120 Mains voltage L3-L1 0.1 V 3000XT
450495 450494 32 bits signed 121 Mains voltage L1-N 0.1 V 3000XT
450497 450496 32 bits signed 122 Mains voltage L2-N 0.1 V 3000XT
450499 450498 32 bits signed 123 Mains voltage L3-N 0.1 V 3000XT
AC System values
450503 450502 32 bits signed 218 Real power in system (valid 1 kW 3000XT
if LDSS is on)
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
Engine Management
Active Diagnostic Trouble Code (DM1) 1-10 (All SPNs)
450513 450512 32 bits signed 15400 SPN of 1. entry full 19 bits of SPN 3000XT
450515 450514 32 bits signed 15403 SPN of 2. entry full 19 bits of SPN 3000XT
450517 450516 32 bits signed 15406 SPN of 3. entry full 19 bits of SPN 3000XT
450519 450518 32 bits signed 15409 SPN of 4. entry full 19 bits of SPN 3000XT
450521 450520 32 bits signed 15412 SPN of 5. entry full 19 bits of SPN 3000XT
450523 450522 32 bits signed 15415 SPN of 6. entry full 19 bits of SPN 3000XT
450525 450524 32 bits signed 15419 SPN of 7. entry full 19 bits of SPN 3000XT
450527 450526 32 bits signed 15422 SPN of 8. entry full 19 bits of SPN 3000XT
450529 450528 32 bits signed 15425 SPN of 9. entry full 19 bits of SPN 3000XT
450531 450530 32 bits signed 15428 SPN of 10. entry full 19 bits of SPN 3000XT
Engine Management
Values
450533 450532 32 bits signed 15201 Total engine hours (j1939- 1 h 3000XT
HOURS, SPN 247)
450535 450534 32 bits unsigned 2580 Period of use counter 0.01 h 3000XT New
450537 450536 32 bits 15319 Engine Total Fuel Used 0.1 L 3000XT Value
(SPN250) for
Error
indi‐
cator:
429496
7294
Value
for Not
avail‐
able:
429496
7295
LS5
450543 450542 32 bits unsigned 267 Average LS5 Delta Mains 0.1 V 3500XT
voltage L-L
450545 450544 32 bits unsigned 268 Average LS5 Wye Mains 0.1 V 3500XT
voltage L-N
450549 450548 32 bits signed 270 Reactive power LS5 1 var 3500XT
Miscellaneous
450563 450562 32 bits 231 Busbar Voltage L1-N 0.1 V 3500XT- New
P2
Modicon Start Size Format Param Description Multiplier (BUS- Unit Model Com‐
start addr. (*1) ID data * Multiplier ment
addr. = real value)
450565 450564 32 bits 232 Busbar Voltage L2-N 0.1 V 3500XT- New
P2
450567 450566 32 bits 233 Busbar Voltage L3-N 0.1 V 3500XT- New
P2
450569 450568 32 bits 5646 Setpoint reactive power 0.1 kvar 3000XT New
450575 450574 32 bits signed 155 Generator current slave 0.001 A 3000XT New
pointer L1
450577 450576 32 bits signed 156 Generator current slave 0.001 A 3000XT New
pointer L2
450579 450578 32 bits signed 157 Generator current slave 0.001 A 3000XT New
pointer L3
450581 450580 32 bits signed 128 Generator reactive power 1 var 3000XT New
L1
450583 450582 32 bits signed 129 Generator reactive power 1 var 3000XT New
L2
450585 450584 32 bits signed 130 Generator reactive power 1 var 3000XT New
L3
450587 450586 32 bits signed 131 Generator apparent power 1 VA 3000XT New
L1
450589 450588 32 bits signed 132 Generator apparent power 1 VA 3000XT New
L2
450591 450590 32 bits signed 133 Generator apparent power 1 VA 3000XT New
L3
450593 450592 32 bits signed 152 Mains total apparent power 1 VA 3000XT New
450595 450594 32 bits signed 158 Mains current slave pointer 0.001 A 3000XT New
L1
450597 450596 32 bits signed 0 (prepared Mains current 0.001 A 3000XT New
slave pointer L2)
450599 450598 32 bits signed 0 (prepared Mains current 0.001 A 3000XT New
slave pointer L3)
Data byte 0 Data byte Length in Param‐ Description EDS Multiplier Unit
Bytes eter ID
(Mux)
DEC HEX
Data byte 0 Data byte Length in Param‐ Description EDS Multiplier Unit
Bytes eter ID
(Mux)
DEC HEX
Data byte 0 Data byte Length in Param‐ Description EDS Multiplier Unit
Bytes eter ID
(Mux)
DEC HEX
Data byte 0 Data byte Length in Param‐ Description EDS Multiplier Unit
Bytes eter ID
(Mux)
DEC HEX
Data byte 0 Data byte Length in Param‐ Description EDS Multiplier Unit
Bytes eter ID
(Mux)
DEC HEX
Data byte 0 Data byte Length in Param‐ Description EDS Multiplier Unit
Bytes eter ID
(Mux)
DEC HEX
Data byte 0 Data byte Length in Param‐ Description EDS Multiplier Unit
Bytes eter ID
(Mux)
DEC HEX
Ensure Security!
Transmitting data from outside of the remote con‐
trol 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 com‐
munication.
Bit 1 Stop bit (rising edge) To stop, a 0 must be written and then
a1
Bit 0 Start bit (rising edge) To start, a 0 must be written and then
a1
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 (LogicsMan‐
ager 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 rising edge disables the
"Reset alarms" 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 internal flag.
"Shutdown command"
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".
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 fre‐
quency setpoint 2
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 set‐
point 2
Bit 3 = 1
Bit 2 = 1
Bit 1 = 1
Bit 0 = 1
AI # 1 2 3 4 5 6 7 8
AI # 9 10 11 12 13 14 15 16
AI # 1 2 3 4
[Sx] - Sign
{x}
[Sx] - Sign
{x}
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.
OR Logical OR
XOR Exclusive OR
Configuration of the command Using the values specified in the above table, the chain of com‐
chain mands of the LogicsManager (for example: operating the relays,
setting the flags, specification of the automatic functions) is config‐
ured as follows:
[Ax] = ( ( [C1] & [S1] ) & [O1] & ( [C2] & [S2] ) ) & [O2] & ( [C3] & [S3] )
NEW arranged
In comparison to easYgen the easYgen-XT series
comes with re-arranged LogicsManagers.
Some samples: ... in general ...
– easYgen group 00.xx and group 24.xx moved
to Part 2: LM results (group 80.xx to group
99.xx)
– Parameters that are similarly used for easYgen
and easYgen-XT come with the same ID/
number - maybe wording is updated
– NEW or remarkable changed parameters come
with new (intentionally different) ID/number
ID Numbers
The following tables list the "ID" numbers used e.g.
for Modbus communication.
01.01 10720 Alarm class A TRUE as long as an alarm of this alarm class is active or
latched (triggered)
01.02 10721 Alarm class B TRUE as long as an alarm of this alarm class is active or
latched (triggered)
01.03 10722 Alarm class C TRUE as long as an alarm of this alarm class is active or
latched (triggered)
01.04 10723 Alarm class D TRUE as long as an alarm of this alarm class is active or
latched (triggered)
01.05 10724 Alarm class E TRUE as long as an alarm of this alarm class is active or
latched (triggered)
01.06 10725 Alarm class F TRUE as long as an alarm of this alarm class is active or
latched (triggered)
01.07 10726 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 (triggered)
01.08 10727 Warning alarm TRUE as long as at least one alarm of the alarm classes A/B
is active or latched (triggered)
01.09 10728 Shutdown alarm TRUE as long as at least one alarm of the alarm classes
C/D/E/F is active or latched (triggered)
01.10 10729 Centralized alarm TRUE as long as at least one alarm of the alarm classes
B/C/D/E/F is active or latched (triggered)
01.11 11620 New alarm triggered TRUE if any alarm of the Alarm classes B/C/D/E/F has been
triggered until it is acknowledged
02.01 9180 LM FALSE Fixed value - often used for default setting
02.03 10732 Gen. voltage ok Generator voltage within operating TRUE as long as the generator voltage is within the
range operating range
02.04 10733 Gen. frequency Generator frequency within oper‐ TRUE as long as the generator frequency is within the
ok ating range operating range
02.05 10734 Gen. volt./freq. Generator voltage and frequency TRUE as long as the generator voltage and frequency
ok within operating ranges are within the operating ranges (02.03. and 02.04 are
TRUE)
02.06 10735 Busbar 1 Busbar 1 voltage within generator TRUE as long as the busbar 1 voltage is within the
voltage ok voltage operating range generator voltage operating range
02.07 10736 Busbar 1 freq. Busbar 1 frequency within fre‐ TRUE as long as the busbar 1 frequency is within the
ok quency voltage operating range generator frequency operating range
02.08 10737 Busb1 volt./freq. Busbar 1 voltage and frequency TRUE as long as the busbar 1 voltage and frequency
ok within generator voltage and fre‐ are within the generator voltage operating ranges
quency operating ranges (02.06. and 02.07 are TRUE)
02.09 10738 Mains voltage Mains voltage within operating TRUE as long as the mains voltage is within the oper‐
ok range ating range
02.10 10739 Mains frequency Mains frequency within operating TRUE as long as the mains frequency is within the
ok range operating range
02.11 10740 Mains volt./freq. Mains voltage and frequency within TRUE as long as the mains voltage and frequency are
ok operating ranges within the operating ranges (02.09. and 02.10 are
TRUE)
02.12 10741 Gen. rotation Generator voltage: rotating direc‐ TRUE as long as the respective rotation field is
CCW tion CCW detected in case of a three-phase voltage measure‐
ment at the respective measuring location
02.13 10742 Gen. rotation Generator voltage: rotating direc‐
CW tion CW
02.21 11630 Dead busbar1 Busbar 1 is dead TRUE as long as the busbar voltage is below the
value configured in parameter 5820 Ä p. 415 (Dead
bus detection max. volt.)
02.29 11649 Sync.Check Synchronize Check Relay: TRUE, if all of the following ranges matches:
gen./busb
Generator « Busbar (ANSI 25) n voltage
n frequency
n phase angle
n acceleration range
n lead angle
02.32 11641 Sync.Check Synchronize Check Relay: TRUE, if all of the following ranges matches:
mns/busb
Busbar « Mains (ANSI 25) n voltage
n frequency
n phase angle
n acceleration range
n lead angle
03.01 10750 Auxiliary services TRUE if an auxiliary services prerun or postrun is enabled
03.05 10754 Horn TRUE if the preglow (Diesel) or ignition (gas) relay is ener‐
gized
03.06 10755 Engine released TRUE if alarm class B to F is activated until the time until horn
reset is expired or it is acknowledged for the first time.
03.07 10756 Engine delay expired TRUE if the engine is requested and the start is released
03.08 10757 Break. delay expired TRUE after expiration of the "delayed engine monitoring" timer
until the fuel relay is de-energized
03.13 10762 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 10763 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 com‐
mand variable is only active if remote control of the ECU via
easYgen is activated.
03.19 Reserved
03.21 11650 Governor lower TRUE if the respective three-position controller issues the
respective control pulse
03.22 11651 AVR raise
03.27 11656 Stop solenoid TRUE if a stop signal is issued until the stop time of engine
expires
03.28 11657 Start/Gas TRUE if the fuel solenoid (Diesel) or gas valve (gas) relay is
energized
03.29 Reserved
03.30 11659 Aux. serv. prerun TRUE, if "Auxiliary services prerun" is active
03.31 11660 Aux. serv. postrun TRUE, if "Auxiliary services postrun" is active
03.32 11661 + PID1 controller TRUE if the respective three-position controller issues the
respective control pulse
03.33 11662 - PID1 controller
03.38 11667 Inhibit cranking TRUE if the easYgen inhibit cranking is activated
04.01 10770 Operat. mode AUTOMATIC operating mode TRUE in AUTOMATIC operating mode
AUTO active
04.02 10771 Operat. mode STOP operating mode active TRUE in STOP operating mode
STOP
04.03 10772 Operat. mode MANUAL operating mode active TRUE in MANUAL operating mode
MAN
04.04 12273 Operat. mode A lamp test is being performed TRUE if the lamp test is active
TEST
04.05 10774 Acknowledge "Acknowledge" push button has This condition is TRUE for approx. 40 ms and must be
been pressed or an external extended utilizing a delay time
acknowledgment via LogicsMan‐
ager
04.06 10775 GCB closed GCB is closed and TRUE if DI 8 (Reply GCB) is de-energized
04.07 10776 MCB closed MCB is closed only TRUE if DI 7 (Reply MCB) is de-energized
04.08 Reserved
04.09 10778 Emergency Emergency power operation active TRUE with the expiration of the emergency power
mode delay; FALSE with the expiration of the mains setting
time and the reply from the MCB is closed
04.10 10779 Cool down Engine cool-down cycle active TRUE as long as the cool down time is running
04.11 10780 Mains settling Mains settling time active Becomes TRUE with a mains failure and FALSE after
the mains settling timer has expired
04.12 10781 Start w/o load Start without closing GCB is active TRUE if Start w/o load is enabled
04.13 10782 Remote request Request over remote control to TRUE if the start bit is set via serial connection
activate a function (Modbus) or CAN bus (CANopen), (control word 503)
04.14 10783 Remote Request over remote control to TRUE if this bit is set via interface (control word 503)
acknowledge acknowledge
04.15 10784 Idle run active Idle mode is active TRUE if the idle mode is active. This may be used to
issue an "Idle" command to a speed controller.
04.16 Reserved
04.17 Reserved
04.18 10787 Synchron. GCB Synchronization GCB is active TRUE if the GCB shall be synchronized until the GCB
active is closed
04.19 10788 Opening GCB Opening GCB is active TRUE if a GCB open command is issued until DI 8
active (Reply GCB) is energized
04.20 10789 Closing GCB Closing GCB is active TRUE if a GCB close command is issued; same func‐
active tion as relay 6 in or
04.21 11670 Syn. MCB is Synchronization MCB is active TRUE if the MCB shall be synchronized until the MCB
active is closed
04.22 11671 Opening MCB Opening MCB is active TRUE if an MCB open command is issued until DI 7
active (Reply GCB) is energized
04.23 11672 Closing MCB Closing MCB is active TRUE if an MCB close command is issued; same
active function as relay 8 in
04.24 Reserved
04.25 Reserved
04.26 Reserved
04.27 11676 Critical mode Critical mode operation is enabled TRUE if critical mode is enabled
04.28 11677 Generator Generator unloading sequence is TRUE if a stop command has been issued until the
unloading active GCB is opened
04.29 11678 Mains unloading Mains unloading sequence is TRUE if a synchronization has been started until the
active MCB is opened
04.30 11679 Limited prerun Prerun operation with power limita‐ TRUE as long as the warm up load limitation is ena‐
tion is active bled
04.31 11680 Segment no.2 Load share group 2 is activated Internal calculation
act.
Refer to parameter 12929 Ä p. 245/Ä p. 853.
04.32 11681 Segment no.3 Load share group 3 is activated Internal calculation
act.
Refer to parameter 12928 Ä p. 245/Ä p. 853.
04.33 11682 Segment no.4 Load share group 4 is activated Internal calculation
act.
Refer to parameter 12927 Ä p. 245/Ä p. 853.
04.37 11686 Remote volt. Voltage setpoint 2 is enabled TRUE if this bit is set via interface (control word 504)
setp. 2
04.41 11690 Transition mode Breaker transition mode alternative Internal calculation
1 1
Refer to parameter 12931 Ä p. 213/Ä p. 853.
04.42 11691 Transition mode Breaker transition mode alternative Internal calculation
2 2
Refer to parameter 12932 Ä p. 214/Ä p. 853.
04.60 11709 Crit. mode Critical mode postrun is active TRUE as long as the critical mode postrun time is run‐
postrun ning
04.61 10773 Lamp test Releases the lamp test All illuminated buttons and signs at the front panel are
a short time illuminated for test
04.64 11970 Key activation ON if any key is activated Relevant for versions with front panel (HMI) only
05.12 Reserved
07.05 10854 Mains mismatched phase rotation (rotation field alarm) TRUE = alarm latched (trig‐
gered)
07.06 10855 Mains overfrequency (limit) 1
FALSE = alarm acknowl‐
07.07 10856 Mains overfrequency (limit) 2 edged
07.26 Reserved
08.09 Reserved
08.11 Reserved
08.12 Reserved
08.13 Reserved
08.14 Reserved
08.15 Reserved
08.20 Reserved
08.21 Reserved
08.23 Reserved
08.24 Reserved
08.25 Reserved
08.26 Reserved
08.33 Reserved
08.36 Reserved
09.01 10900 DI 1 (Discrete input [DI 01]) TRUE = logical "1" (delay
times and N.O./N.C. parame‐
09.02 10901 DI 2 (Discrete input [DI 02]) ters are ignored)
09.03 10902 DI 3 (Discrete input [DI 03]) FALSE = logical "0" (alarm
has been acknowledged or
09.04 10903 DI 4 (Discrete input [DI 04]) immediately after TRUE con‐
dition is not present anymore,
09.05 10904 DI 5 (Discrete input [DI 05]) if Control is configured as
alarm class)
09.06 10905 DI 6 (Discrete input [DI 06])
10.01 11072 Analog input AI 01 wire break TRUE = measured value out
of range
10.02 11073 Analog input AI 02 wire break
FALSE = logical "0" (alarm
10.03 11074 Analog input AI 03 wire break has been acknowledged, or
immediately after TRUE con‐
dition is not present anymore,
if Control is configured as
alarm class)
11.08 10947 Engine (running hours exceeded by) 1 hour Status changes every oper‐
ating hour
11.09 10948 Engine (running hours exceeded by) 10 hour Status changes every 10
operating hours
11.10 10949 Engine (running hours exceeded by) 100 hour Status changes every 100
operating hours
13.01 10980 Discrete output DO1 [R01] TRUE = logical "1" (this con‐
dition indicates the logical
13.02 10981 Discrete output DO2 [R02] status of the internal relays)
13.03 10982 Discrete output DO3 [R03] FALSE = logical "0" (this con‐
dition indicates the logical
13.04 10983 Discrete output DO4 [R04] status of the internal relays)
13.05 10984 Discrete output DO5 [R05]
15.01 11093 Flexible analog limit 1 (triggered) TRUE = limit value reached
86.09 10708 LM: Start req in AUTO The (boolean) result of the Log‐
icsManager
86.10 10709 LM: Stop req. in AUTO
87.17 11406 LM: PID1 ctrl.release The (boolean) result of the Log‐
icsManager
87.18 11407 LM: PID2 ctrl.release
87.23 Reserved
87.24 Reserved
87.25 Reserved
87.26 Reserved
87.27 Reserved
87.28 Reserved
87.29 Reserved
87.30 Reserved
87.61 Reserved
87.62 Reserved
88.01 11550 LM: Free alarm 1 The (boolean) result of the Log‐
icsManager
88.02 11551 LM: Free alarm 2
93.01 9704 AM Data source AO1 Data source analog output 1 is valid The boolean result BR
of the AnalogManager
93.02 9706 AM Data source AO2 Data source analog output 2 is valid
93.21 9717 AM Data s. ext. AO1 Data source of external analog output 1 is valid
93.22 9719 AM Data s. ext. AO2 Data source of external analog output 2 is valid
93.23 9721 AM Data s. ext. AO3 Data source of external analog output 3 is valid
93.24 9723 AM Data s. ext. AO4 Data source of external analog output4 is valid
99.01 11870 LM: Ready for op. OFF The flag “Ready for operation” ON would mean the device is
(negative logic) is OFF NOT READY for operation
B DIN 40 700
C ASA
US MIL (configurable)
D IEC617-12
1 2 3 4 5 6
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
LM: Start req in AUTO Start in AUTOMATIC operating mode (parameter 12120 Ä p. 277/Ä p. 850) 86.09 10708
LM: Stop req. in AUTO Stop in AUTOMATIC operating mode (parameter 12190 Ä p. 277/Ä p. 850) 86.10 10709
LM: Inhibit emerg.run Blocking or interruption of an emergency power operating in AUTOMATIC 86.11 10710
operating mode (parameter 12200 Ä p. 301/Ä p. 850)
LM: Undelay close GCB Immediately closing of the GCB after engine start without waiting for the engine 86.12 10711
delayed monitoring and generator stable timer to expire (param‐
eter 12210 Ä p. 217/Ä p. 850)
LM: LS interf. EthA Enables to switch load share interface between CAN and Ethernet A (param‐ 86.13 11987
eter 11986 Ä p. 243/Ä p. 592)
LM: Constant idle run Enables idle/rated speed modes (parameter 12550 Ä p. 173/Ä p. 852). 86.14 10713
LM: Ext. acknowledge The alarm acknowledgement is performed from an external source (param‐ 86.15 10714
eter 12490 Ä p. 391/Ä p. 852)
LM: Operat. mode Activation of the AUTOMATIC operating mode (parameter 12510 Ä p. 275/ 86.16 10715
AUTO Ä p. 852 )
LM: Operat. mode MAN Activation of the MANUAL operating mode (parameter 12520 Ä p. 275/ 86.17 10716
Ä p. 852)
LM: Operat. mode STOP Activation of the STOP operating mode (parameter 12530 Ä p. 276/Ä p. 852) 86.18 10717
LM: Start w/o load Starting the engine without closing the GCB (parameter 12540 Ä p. 277/ 86.19 10718
Ä p. 852/Ä p. 852)
LM: Auto idle mode Automatic idle mode (blocks the undervoltage, underfrequency, and under‐ 86.20 10719
speed monitoring for a configured time automatically, param‐
eter 12570 Ä p. 173/Ä p. 852)
LM: Discrete f/P + Raise frequency / real power setpoint (parameter 12900 Ä p. 274/Ä p. 852) 86.21 11600
LM: Discrete f/P - Lower frequency / real power setpoint (parameter 12901 Ä p. 274/Ä p. 852) 86.22 11601
LM: Discrete V/PF + Raise voltage / power factor setpoint (parameter 12902 Ä p. 274/Ä p. 852) 86.23 11602
LM: Discrete V/PF - Lower voltage / power factor setpoint (parameter 12903 Ä p. 274/Ä p. 852) 86.24 11603
LM: Freq. droop act. Activation of the frequency droop (parameter 12904 Ä p. 252/Ä p. 852) 86.25 11604
LM: Volt. droop act. Activation of the voltage droop (parameter 12905 Ä p. 230/Ä p. 852) 86.26 11605
LM: Ext. mns.decoupl. Activation of the mains decoupling function (parameter 12922 Ä p. 349/ 86.27 11606
Ä p. 853)
LM: Critical mode Activation of critical mode operation (parameter 12220 Ä p. 285/Ä p. 850) 86.28 11607
LM: Syn. mode CHECK Activation of CHECK synchronization mode (parameter 12906 Ä p. 222/ 86.38 11617
Ä p. 852)
LM: Syn. mode Activation of PERMISSIVE synchronization mode (parameter 12907 Ä p. 222/ 86.39 11618
PERMIS. Ä p. 852)
LM: Syn. mode RUN Activation of RUN synchronization mode (parameter 12908 Ä p. 222/ 86.40 11619
Ä p. 852)
LM: Setpoint 2 freq. Activates the frequency setpoint 2 (parameter 12918 Ä p. 252/Ä p. 853) 86.81 11910
LM: Setp. 2 load Activates the load setpoint 2 (parameter 12919 Ä p. 260/Ä p. 490/Ä p. 853) 86.82 11911
LM: Setp. 2 voltage Activates the voltage setpoint 2 (parameter 12920 Ä p. 229/Ä p. 853) 86.83 11912
LM: Setp.2 pwr.factor Activates the power factor setpoint 2 (parameter 12921 Ä p. 234/Ä p. 853) 86.84 11913
LM: Enable MCB Enables the MCB (parameter 12923 Ä p. 220/Ä p. 853) 86.85 11914
LM: LDSS enabled Activation of load-dependent start/stop (parameter 12930 Ä p. 290/Ä p. 484/ 86.86 11915
Ä p. 853)
LM: Segment no.2 act. Assigns the genset to load share segm. #2 (parameter 12929 Ä p. 245/ 86.87 11916
Ä p. 853)
LM: Segment no.3 act. Assigns the genset to load share segm. #3 (parameter 12928 Ä p. 245/ 86.88 11917
Ä p. 853)
LM: Segment no.4 act. Assigns the genset to load share segm. #4 (parameter 12927 Ä p. 245/ 86.89 11918
Ä p. 853)
LM: LDSS Priority 2 Sets the LDSS priority to 2 (parameter 12926 Ä p. 290/Ä p. 853) 86.90 11919
LM: LDSS Priority 3 Sets the LDSS priority to 3 (parameter 12925 Ä p. 290/Ä p. 853) 86.91 11920
LM: LDSS Priority 4 Sets the LDSS priority to 4 (parameter 12924 Ä p. 290/Ä p. 853) 86.92 11921
LM: Transition mode 1 Activates breaker transition mode 1 (parameter 12931 Ä p. 213/Ä p. 853) 86.93 11922
LM: Transition mode 2 Activates breaker transition mode 2 (parameter 12932 Ä p. 214/Ä p. 853) 86.94 11923
Reserved 87.23
Reserved 87.24
Reserved 87.25
Reserved 87.26
Reserved 87.27
Reserved 87.28
Reserved 87.29
Reserved 87.30
Reserved 87.61
Reserved 87.62
Priority hierarchy of the logical out‐ The following table contains the priority relationships between the
puts start conditions of the logical outputs in the LogicsManager:
Start req. in Auto The behavior of the system depends on the configuration of the
related parameters.
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 manage‐
ment 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.
Emergency power during Start The generator keeps on running without taking over load.
w/o load
Relay 1 If this logical output becomes true, the relay output 1 will be acti‐ 99.01 11870
vated
(Ready for opera‐
tion OFF)
Relay 2 If this logical output becomes true, the relay output 2 will be acti‐ 99.02 11871
vated
Relay 3 If this logical output becomes true, the relay output 3 will be acti‐ 99.03 11872
vated
Relay 4 If this logical output becomes true, the relay output 4 will be acti‐ 99.04 11873
vated
Relay 5 If this logical output becomes true, the relay output 5 will be acti‐ 99.05 11874
vated
Relay 6 If this logical output becomes true, the relay output 6 will be acti‐ 99.06 11875
vated
Relay 7 If this logical output becomes true, the relay output 7 will be acti‐ 99.07 11876
vated
Relay 8 If this logical output becomes true, the relay output 8 will be acti‐ 99.08 11877
vated
Relay 9 If this logical output becomes true, the relay output 9 will be acti‐ 99.09 11878
vated
Relay 10 If this logical output becomes true, the relay output 10 will be acti‐ 99.10 11879
vated
Relay 11 If this logical output becomes true, the relay output 11 will be acti‐ 99.11 11880
vated
Relay 12 If this logical output becomes true, the relay output 12 will be acti‐ 99.12 11881
vated
External DO 1 If this logical output becomes true, the external relay output 1 will 98.01 11892
be activated
External DO 2 If this logical output becomes true, the external relay output 2 will 98.02 11893
be activated
External DO 3 If this logical output becomes true, the external relay output 3 will 98.03 11894
be activated
External DO 4 If this logical output becomes true, the external relay output 4 will 98.04 11895
be activated
External DO 5 If this logical output becomes true, the external relay output 5 will 98.05 11896
be activated
External DO 6 If this logical output becomes true, the external relay output 6 will 98.06 11897
be activated
External DO 7 If this logical output becomes true, the external relay output 7 will 98.07 11898
be activated
External DO 8 If this logical output becomes true, the external relay output 8 will 98.08 11899
be activated
External DO 9 If this logical output becomes true, the external relay output 9 will 98.09 11900
be activated
External DO 10 If this logical output becomes true, the external relay output 10 98.10 11901
will be activated
External DO 11 If this logical output becomes true, the external relay output 11 98.11 11902
will be activated
External DO 12 If this logical output becomes true, the external relay output 12 98.12 11903
will be activated
External DO 13 If this logical output becomes true, the external relay output 13 98.13 11904
will be activated
External DO 14 If this logical output becomes true, the external relay output 14 98.14 11905
will be activated
External DO 15 If this logical output becomes true, the external relay output 15 98.15 11906
will be activated
External DO 16 If this logical output becomes true, the external relay output 16 98.16 11907
will be activated
External DO 17 If this logical output becomes true, the external relay output 17 98.17 11390
will be activated
External DO 18 If this logical output becomes true, the external relay output 18 98.18 11391
will be activated
External DO 19 If this logical output becomes true, the external relay output 19 98.19 11392
will be activated
External DO 20 If this logical output becomes true, the external relay output 20 98.20 11393
will be activated
External DO 21 If this logical output becomes true, the external relay output 21 98.21 11394
will be activated
External DO 22 If this logical output becomes true, the external relay output 22 98.22 11395
will be activated
External DO 23 If this logical output becomes true, the external relay output 23 98.23 11396
will be activated
External DO 24 If this logical output becomes true, the external relay output 24 98.24 11397
will be activated
External DO 25 If this logical output becomes true, the external relay output 25 98.25 11398
will be activated
External DO 26 If this logical output becomes true, the external relay output 26 98.26 11399
will be activated
External DO 27 If this logical output becomes true, the external relay output 27 98.27 11400
will be activated
External DO 28 If this logical output becomes true, the external relay output 28 98.28 11401
will be activated
External DO 29 If this logical output becomes true, the external relay output 29 98.29 11402
will be activated
External DO 30 If this logical output becomes true, the external relay output 30 98.30 11403
will be activated
External DO 31 If this logical output becomes true, the external relay output 31 98.31 11404
will be activated
External DO 32 If this logical output becomes true, the external relay output 32 98.32 11405
will be activated
[R 04] 45/46 LogicsManager; pre-assigned with 'Diesel: Fuel solenoid, Gas: Gas valve'
7794 Enable 2nd display brightness (Not 04.64 Key activation And True) And True
7799 Enable front foil heater (True And True) And True
11978 2nd load control setpoint ramp (False And 02.02 LM TRUE) And 02.02 LM TRUE
12120 Start req in AUTO (09.02 Discrete input 2 Or False) Or 04.13 Remote request
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
ID Name Function
ID Name Function
12490 Ext. acknowledge (09.05 Discrete input 5 And True) Or 04.14 Remote acknowledge
12580 Ready for op. OFF (False And False) And True
12853 Disable load setpoint ramp (02.01 LM 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
ID Name Function
12923 Enable MCB (09.06 Discrete input 6 And Not 08.07 MCB fail to close) And Not 07.05
Mns.ph.rot. mismatch
12927 Segment no.4 act. (02.01 LM FALSE And True) And True
12928 Segment no.3 act. (02.01 LM FALSE And True) And True
12929 Segment no.2 act. (02.01 LM FALSE 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
12989 Speed detection (02.36 Speed electr. Or 02.37 Speed rpm) And True
12999 Release eng.mon. (02.34 Firing speed electr. Or 02.35 Firing speed rpm) And 03.28
Start/Gas
Relay outputs
Simple (function) Extended (configuration) Result
In application mode
and = freely configurable relay (unas‐
signed)
In application mode to "Command:
close GCB"
Deactivated by default
In application mode , , , ,
, , , and = freely con‐
figurable relay (unassigned)
In application mode and "Command:
close MCB"
Deactivated by default
Discrete inputs
Number LM ID Alarm class Pre-assigned to
All analog values may be used as data sources for the analog out‐
puts (refer to Ä Chapter 4.4.2.5 “Analog Outputs” on page 191),
the flexible limit monitoring (refer to Ä Chapter 4.5.5 “Flexible
Limits” on page 386), and the controller setpoints (refer to
Ä Chapter 4.4.4 “Configure Controller” on page 225).
AnalogManager Variables
AnalogManager Results
Cascading: Use analog results
This analog results of an AnalogManager is avail‐
able as AnalogManager input additionally. Like the
other AnalogManager inputs they can be used as
input signal for (further) AnalogManagers.
'Internal'/Fixed AnalogManager The groups 90.xx to 99.xx contain analog outputs of fixed Analog‐
Values Managers.
The description/name of these analog variables starts always with
'AM ...'.
01.01 15730 Generator: Voltage wye average Gen.volt L-N [%] Percentage value related on Gener‐
ator Rated Voltage.
01.02 15731 Generator voltage L1-N Gen.volt L1-N [%] Percentage value related on Gener‐
ator Rated Voltage.
01.03 15732 Generator voltage L2-N Gen.volt L2-N [%] Percentage value related on Gener‐
ator Rated Voltage.
01.04 15733 Generator voltage L3-N Gen.volt L3-N [%] Percentage value related on Gener‐
ator Rated Voltage.
01.05 15734 Generator: Voltage delta average Gen.volt L-L [%] Percentage value related on Gener‐
ator Rated Voltage.
01.06 15735 Generator voltage L1-L2 Gen.volt L1-L2 [%] Percentage value related on Gener‐
ator Rated Voltage.
01.07 15736 Generator voltage L2-L3 Gen.volt L2-L3 [%] Percentage value related on Gener‐
ator Rated Voltage.
01.08 15737 Generator voltage L3-L1 Gen.volt L3-L1 [%] Percentage value related on Gener‐
ator Rated Voltage.
01.09 15738 Generator frequency Gen.frequency [%] Percentage value related on Gener‐
ator Nominal Frequency.
01.10 15739 Generator frequency L1-L2 Gen.freq.L1-L2 [%] Percentage value related on Gener‐
ator Nominal Frequency.
01.11 15740 Generator frequency L2-L3 Gen.freq.L2-L3 [%] Percentage value related on Gener‐
ator Nominal Frequency.
01.12 15741 Generator frequency L3-L1 Gen.freq.L3-L1 [%] Percentage value related on Gener‐
ator Nominal Frequency.
01.13 15742 Generator average current Gen.current [%] Percentage value related on Gener‐
ator Rated Current.
01.14 15743 Generator current L1 Gen.current L1 [%] Percentage value related on Gener‐
ator Rated Current.
01.15 15744 Generator current L2 Gen.current L2 [%] Percentage value related on Gener‐
ator Rated Current.
01.16 15745 Generator current L3 Gen.current L3 [%] Percentage value related on Gener‐
ator Rated Current.
01.17 15746 Dragged generator current L1 Gen.curr.max. L1 [%] Percentage value related on Gener‐
ator Rated Current.
01.18 15747 Dragged generator current L2 Gen.curr.max. L2 [%] Percentage value related on Gener‐
ator Rated Current.
01.19 15748 Dragged generator current L3 Gen.curr.max. L3 [%] Percentage value related on Gener‐
ator Rated Current.
01.20 15749 Generator power factor Gen. PF [%] Percentage value related on Power
Factor 1.
01.21 15750 Generator power factor L1 Gen. PF L1 [%] Percentage value related on Power
Factor 1.
01.22 15751 Generator power factor L2 Gen. PF L2 [%] Percentage value related on Power
Factor 1.
01.23 15752 Generator power factor L3 Gen. PF L3 [%] Percentage value related on Power
Factor 1.
01.24 15753 Total Generator real power Gen. act. power [%] Percentage value related on Gener‐
ator rated active power.
01.25 15754 Generator real power L1-N Gen.act.pwr. L1 [%] Percentage value related on Gener‐
ator rated active power.
01.26 15755 Generator real power L2-N Gen.act.pwr. L2 [%] Percentage value related on Gener‐
ator rated active power.
01.27 15756 Generator real power L3-N Gen.act.pwr. L3 [%] Percentage value related on Gener‐
ator rated active power.
01.28 15757 Total gen. reactive power Gen.react.pwr. [%] Percentage value related on Gener‐
ator rated reactive power.
01.29 15758 Generator reactive power L1-N Gen.react.pwr.L1 [%] Percentage value related on Gener‐
ator rated reactive power.
01.30 15759 Generator reactive power L2-N Gen.react.pwr.L2 [%] Percentage value related on Gener‐
ator rated reactive power.
01.31 15760 Generator reactive power L3-N Gen.react.pwr.L3 [%] Percentage value related on Gener‐
ator rated reactive power.
01.32 15761 Total gen. apparent power Gen.app.power [%] Percentage value related on Gener‐
ator rated active- and reactive power.
01.33 15762 Generator apparent power L1-N Gen.app.pwr. L1 [%] Percentage value related on Gener‐
ator rated active- and reactive power.
01.34 15763 Generator apparent power L2-N Gen.app.pwr. L2 [%] Percentage value related on Gener‐
ator rated active- and reactive power.
01.35 15764 Generator apparent power L3-N Gen.app.pwr. L3 [%] Percentage value related on Gener‐
ator rated active- and reactive power.
01.51 9730 Generator voltage wye average Gen volt L-N [V] Voltage Format
01.52 9731 Generator voltage 1-N Gen volt L1-N [V] Voltage Format
01.53 9732 Generator voltage L2-N Gen.volt L2-N [V] Voltage Format
01.54 9733 Generator voltage L3-N Gen.volt L3-N [V] Voltage Format
01.55 9734 Generator voltage delta average Gen.volt L-L [V] Voltage Format
01.56 9735 Generator voltage L1-L2 Gen.volt L1-L2 [V] Voltage Format
01.57 9736 Generator voltage L2-L3 Gen.volt L2-L3 [V] Voltage Format
01.58 9737 Generator voltage L3-L1 Gen.volt L3-L1 [V] Voltage Format
01.74 9753 Total Generator real power Gen. act. power [W] Power Format
01.75 9754 Generator real power L1-N Gen.act.pwr. L1 [W] Power Format
01.76 9755 Generator real power L2-N Gen.act.pwr. L2 [W] Power Format
01.77 9756 Generator real power L3-N Gen.act.pwr. L3 [W] Power Format
01.78 9757 Total generator reactive power Gen. react.pwr. [var] Reactive Power Format
01.79 9758 Generator reactive power L1-N Gen.react.pwr.L1[var] Reactive Power Format
01.80 9759 Generator reactive power L2-N Gen.react.pwr.L2[var] Reactive Power Format
01.81 9760 Generator reactive power L3-N Gen.react.pwr.L3[var] Reactive Power Format
01.82 9761 Total generator apparent power Gen.app.power [VA] Apparent Power Format
01.83 9762 Generator apparent power L1-N Gen.app.pwr. L1 [VA] Apparent Power Format
01.84 9763 Generator apparent power L2-N Gen.app.pwr. L2 [VA] Apparent Power Format
01.85 9764 Generator apparent power L3-N Gen.app.pwr. L3 [VA] Apparent Power Format
02.01 15780 Mains: Voltage wye average Mains volt L-N [%] Percentage value related on Mains
Rated Voltage.
02.02 15781 Mains voltage 1-N Mains volt L1-N [%] Percentage value related on Mains
Rated Voltage.
02.03 15782 Mains voltage 2-N Mains volt L2-N [%] Percentage value related on Mains
Rated Voltage.
02.04 15783 Mains voltage 3-N Mains volt L3-N [%] Percentage value related on Mains
Rated Voltage.
02.05 15784 Mains: Voltage delta average Mains volt L-L [%] Percentage value related on Mains
Rated Voltage.
02.06 15785 Mains voltage 1-2 Mains volt L1-L2 [%] Percentage value related on Mains
Rated Voltage.
02.07 15786 Mains voltage 2-3 Mains volt L2-L3 [%] Percentage value related on Mains
Rated Voltage.
02.08 15787 Mains voltage 3-1 Mains volt L3-L1 [%] Percentage value related on Mains
Rated Voltage.
02.09 15788 Mains frequency Mains frequency [%] Percentage value related on Nominal
Frequency.
02.10 15789 Mains frequency 1-2 Mains freq.L1-L2 [%] Percentage value related on Nominal
Frequency.
02.11 15790 Mains frequency 2-3 Mains freq.L2-L3 [%] Percentage value related on Nominal
Frequency.
02.12 15791 Mains frequency 3-1 Mains freq.L3-L1 [%] Percentage value related on Nominal
Frequency.
02.13 15792 Mains average current Mains current [%] Percentage value related on Mains
Rated Current.
02.14 15793 Mains current 1 Mains current L1 [%] Percentage value related on Mains
Rated Current.
02.15 15794 Mains current 2 Mains current L2 [%] Percentage value related on Mains
Rated Current.
02.16 15795 Mains current 3 Mains current L3 [%] Percentage value related on Mains
Rated Current.
02.17 15796 Dragged mains current 1 Mns.curr.max.L1 [%] Percentage value related on Mains
Rated Current.
02.18 15797 Dragged mains current 2 Mns.curr.max.L2 [%] Percentage value related on Mains
Rated Current.
02.19 15798 Dragged mains current 3 Mns.curr.max.L3 [%] Percentage value related on Mains
Rated Current.
02.20 15799 Mains powerfactor Mains PF [%] Percentage value related on Power
Factor 1.
02.21 15800 Mains powerfactor 1 Mains PF L1 [%] Percentage value related on Power
Factor 1.
02.22 15801 Mains powerfactor 2 Mains PF L2 [%] Percentage value related on Power
Factor 1.
02.23 15802 Mains powerfactor 3 Mains PF L3 [%] Percentage value related on Power
Factor 1.
02.24 15803 Total mains. real power Mains act. power [%] Percentage value related on Mains
rated active power.
02.25 15804 Mains power 1-N Mns.act.pwr.L1 [%] Percentage value related on Mains
rated active power.
02.26 15805 Mains power 2-N Mns.act.pwr.L2 [%] Percentage value related on Mains
rated active power.
02.27 15806 Mains power 3-N Mns.act.pwr.L3 [%] Percentage value related on Mains
rated active power.
02.28 15807 Total mains reactive power Mns.react. pwr. [%] Percentage value related on Mains
rated reactive power.
02.29 15808 Mains reactive power 1-N Mns.react.pwr.L1 [%] Percentage value related on Mains
rated reactive power.
02.30 15809 Mains reactive power 2-N Mns.react.pwr.L2 [%] Percentage value related on Mains
rated reactive power.
02.31 15810 Mains reactive power 3-N Mns.react.pwr.L3 [%] Percentage value related on Mains
rated reactive power.
02.32 15811 Total mains apparent power Mns.app.power [%] Percentage value related on Mains
rated active- and reactive power.
02.33 15812 Mains apparent power 1-N Mns.app.pwr.L1 [%] Percentage value related on Mains
rated active- and reactive power.
02.34 15813 Mains apparent power 2-N Mns.app.pwr.L2 [%] Percentage value related on Mains
rated active- and reactive power.
02.35 15814 Mains apparent power 3-N Mns.app.pwr.L3 [%] Percentage value related on Mains
rated active- and reactive power.
02.36 15815 Mains external measured active Mns.ext.act.pwr. [%] Percentage value related on Mains
power by AI rated active power.
02.37 15816 Mains external measured reactive Mns.ext.react.pwr[%] Percentage value related on Mains
power by AI rated reactive power.
02.38 15817 Mains calculated Power Factor by AI Mains ext. PF [%] Percentage value related on Power
Factor 1.
02.51 9780 Mains : Voltage wye average Mains volt L-N [V] Voltage Format
02.52 9781 Mains voltage 1-N Mains volt L1-N [V] Voltage Format
02.53 9782 Mains voltage 2-N Mains volt L2-N [V] Voltage Format
02.54 9783 Mains voltage 3-N Mains volt L3-N [V] Voltage Format
02.55 9784 Mains: Voltage delta average Mains volt L-L [V] Voltage Format
02.56 9785 Mains voltage 1-2 Mains volt L1-L2 [V] Voltage Format
02.57 9786 Mains voltage 2-3 Mains volt L2-L3 [V] Voltage Format
02.58 9787 Mains voltage 3-1 Mains volt L3-L1 [V] Voltage Format
02.60 9789 Mains frequency 1-2 Mains freq.L1-L2 [Hz] Frequency Format
02.61 9790 Mains frequency 2-3 Mains freq.L2-L3 [Hz] Frequency Format
02.62 9791 Mains frequency 3-1 Mains freq.L3-L1 [Hz] Frequency Format
02.63 9792 Mains average current Mains current [A] Current Format
02.74 9813 Total mains. real power Mains act. power [W] Power Format
02.78 9817 Total mains reactive power Mns.react.pwr. [var] Reactive Power Format
02.79 9818 Mains reactive power 1-N Mns.react.pwr.L1[var] Reactive Power Format
02.80 9819 Mains reactive power 2-N Mns.react.pwr.L2[var] Reactive Power Format
02.81 9820 Mains reactive power 3-N Mns.react.pwr.L3[var] Reactive Power Format
02.82 9821 Total mains apparent power Mns.app.power [VA] Apparent Power Format
02.83 9822 Mains apparent power 1-N Mns.app.pwr. L1 [VA] Apparent Power Format
02.84 9823 Mains apparent power 2-N Mns.app.pwr. L2 [VA] Apparent Power Format
02.85 9824 Mains apparent power 3-N Mns.app.pwr. L3 [VA] Apparent Power Format
02.86 9825 Mains external measured active Mns.ext.act.pwr. [W] Power Format
power by AI
02.87 9826 Mains external measured reactive Mns.ext.reac.pwr [var] Reactive Power Format
power by AI
02.88 9827 Mains calculated Power Factor by AI Mains ext. PF Power Factor Format
02.89 11571 Mains settling time Mains settl.time [s] Seconds format
03.01 15830 Busbar 1: voltage delta average [%] Busb1 volt. L-L [%] Percentage value related on Busbar 1
rated voltage.
03.02 15831 Busbar 1: voltage L1-L2 [%] Busb1 volt.L1-L2 [%] Percentage value related on Busbar 1
rated voltage.
03.05 15834 Busbar 1: Frequency [%] Busb1 frequency [%] Percentage value related on Nominal
Frequency.
03.06 15835 Busbar 1: Frequency L1-L2 [%] Busb1 freq.L1-L2 [%] Percentage value related on Nominal
Frequency.
03.51 9840 Busbar 1: Voltage delta average [V] Busb1 volt.L-L [V] Voltage Format
03.52 9841 Busbar 1: voltage L1-L2 [V] Busb1 volt.L1-L2 [V] Voltage Format
03.55 9844 Busbar 1: Frequency [Hz] Busb1 frequency [Hz] Frequency Format
03.56 9845 Busbar 1: Frequency L1-L2 [Hz] Busb1 freq.L1-L2 [Hz] Frequency Format
05.01 15860 Internal freq.setp.1 Internal f setp1 [%] Percentage value related on Nominal
Frequency.
05.02 15861 Internal freq.setp.2 Internal f setp2 [%] Percentage value related on Nominal
Frequency.
05.03 15862 Interface freq.setp. Interface f setp [%] Percentage value related on Nominal
Frequency.
05.04 15863 Internal pow.setp.1 Internal P setp1 [%] Percentage value related on Gener‐
ator rated active power.
05.05 15864 Internal pow.setp.2 Internal P setp2 [%] Percentage value related on Gener‐
ator rated active power.
05.06 15865 Interface pow.setp. Interface P setp [%] Percentage value related on Gener‐
ator rated active power.
05.07 15866 Internal volt.setp.1 Internal V setp1 [%] Percentage value related on Gener‐
ator rated voltage.
05.08 15867 Internal volt.setp.2 Internal V setp2 [%] Percentage value related on Gener‐
ator rated voltage.
05.09 15868 Interface volt.setp. Interface V setp [%] Percentage value related on Gener‐
ator rated voltage.
05.10 15869 Int.pow.factor setp1 Intern. PF setp1 [%] Percentage value related on Power
Factor 1.
05.11 15870 Int.pow.factor setp2 Intern. PF setp2 [%] Percentage value related on Power
Factor 1.
05.12 15871 Interface pow.factor Interface PF sp [%] Percentage value related on Power
Factor 1.
05.13 15872 Digital poti freq. Discrete f +/- [%] Percentage value related on Nominal
Frequency.
05.14 15873 Digital poti power Discrete P +/- [%] Percentage value related on Gener‐
ator rated active power
05.15 15874 Digital poti voltage Discrete V +/- [%] Percentage value related on Gener‐
ator rated voltage
05.16 15875 Dig. poti pow.factor Discrete PF +/- [%] Percentage value related on Power
Factor 1.
05.17 15876 Used freq.setp. Used f setp. [%] Percentage value related on Nominal
Frequency.
05.18 15877 Used freq.setp.ramp Used f setp.ramp [%] Percentage value related on Nominal
Frequency.
05.19 15878 Used pwr. setp. Used P setp. [%] Percentage value related on Gener‐
ator rated active power
05.20 15879 Used pwr. setp.ramp Used P setp.ramp [%] Percentage value related on Gener‐
ator rated active power
05.21 15880 Used volt.setp. Used V setp. [%] Percentage value related on Gener‐
ator rated voltage
05.22 15881 Used volt.setp.ramp Used V setp.ramp [%] Percentage value related on Gener‐
ator rated voltage
05.23 15882 Used PF setp. Used PF setp [%] Percentage value related on Power
Factor 1.
05.24 15883 Used PF setp.ramp Used PF sp ramp [%] Percentage value related on Power
Factor 1.
05.28 15887 Pred(F) P derating (f) [%] Percentage value related on Gener‐
ator rated active power
05.30 15889 Internal pow.setp.3 Internal P setp3 [%] Percentage value related on Gener‐
ator rated active power.
05.31 15501 Internal kvar setpoint 1 Int. kvar setp1 [%] Percentage value related on Gener‐
ator rated reactive power.
05.32 15502 Internal kvar setpoint 2 Int. kvar setp2 [%] Percentage value related on Gener‐
ator rated reactive power.
05.33 15503 Interface kvar setpoint Interf. kvar sp [%] Percentage value related on Gener‐
ator rated reactive power.
05.34 9188 Internal pow.setp.4 Internal P setp4 [%] Percentage value related on Gener‐
ator rated active power.
05.63 9883 Digital poti freq. Discrete f +/- [Hz] Frequency Format
05.65 9885 Digital poti voltage Discrete V +/- [V] Voltage Format
07.05 15924 SPN 95: Fuel Filter Difference Pressure 95:Fuel Filt.Diff. Pr.
07.06 15925 SPN 98: Engine Oil Level 98:Engine Oil Level
07.07 15926 SPN 100: Engine Oil Pressure 100:Engine Oil Press.
07.11 15930 SPN 106: Turbo Air Inlet Pressure 106:Air Intake Press.
07.12 15931 SPN 107: Air Filter 1 Difference Pressure 107:Air Filt1 Diff.Pr
07.19 15938 SPN 171: Ambient Air Temperature 171:Ambient Air Temp.
07.20 15939 SPN 172: Air Intake Temperature 172:Air Intake Temp.
07.21 15940 SPN 173: Exhaust Gas Temperature 173:Exhaust Gas Temp.
07.24 15943 SPN 176: Turbo Oil Temperature 176:Turbo Oil Temp.
07.42 15332 SPN 1137: Exhaust Gas Port 1 Tempera‐ 1137:Exh.Gas P.1 Temp
ture
07.43 15333 SPN 1138: Exhaust Gas Port 2 Tempera‐ 1138:Exh.Gas P.2 Temp
ture
07.44 15334 SPN 1139: Exhaust Gas Port 3 Tempera‐ 1139:Exh.Gas P.3 Temp
ture
07.45 15335 SPN 1140: Exhaust Gas Port 4 Tempera‐ 1140:Exh.Gas P.4 Temp
ture
07.46 15336 SPN 1141: Exhaust Gas Port 5 Tempera‐ 1141:Exh.Gas P.5 Temp
ture
07.47 15337 SPN 1142: Exhaust Gas Port 6 Tempera‐ 1142:Exh.Gas P.6 Temp
ture
07.48 15338 SPN 1143: Exhaust Gas Port 7 Tempera‐ 1143:Exh.Gas P.7 Temp
ture
07.49 15339 SPN 1144: Exhaust Gas Port 8 Tempera‐ 1144:Exh.Gas P.8 Temp
ture
07.50 15340 SPN 1145: Exhaust Gas Port 9 Tempera‐ 1145:Exh.Gas P.9 Temp
ture
07.51 15341 SPN 1146: Exhaust Gas Port 10 Tempera‐ 1146:Exh.Gas P.10 T
ture
07.52 15342 SPN 1147: Exhaust Gas Port 11 Tempera‐ 1147:Exh.Gas P.11 T
ture
07.53 15343 SPN 1148: Exhaust Gas Port 12 Tempera‐ 1148:Exh.Gas P.12 T
ture
07.54 15344 SPN 1149: Exhaust Gas Port 13 Tempera‐ 1149:Exh.Gas P.13 T
ture
07.55 15345 SPN 1150: Exhaust Gas Port 14 Tempera‐ 1150:Exh.Gas P.14 T
ture
07.56 15346 SPN 1151: Exhaust Gas Port 15 Tempera‐ 1151:Exh.Gas P.15 T
ture
07.57 15347 SPN 1152: Exhaust Gas Port 16 Tempera‐ 1152:Exh.Gas P.16 T
ture
07.58 15348 SPN 1153: Exhaust Gas Port 17 Tempera‐ 1153:Exh.Gas P.17 T
ture
07.59 15349 SPN 1154: Exhaust Gas Port 18 Tempera‐ 1154:Exh.Gas P.18 T
ture
07.60 15350 SPN 1155: Exhaust Gas Port 19 Tempera‐ 1155:Exh.Gas P.19 T
ture
07.61 15351 SPN 1156: Exhaust Gas Port 20 Tempera‐ 1156:Exh.Gas P.20 T
ture
07.62 15352 SPN 1157: Main Bearing 1 Temperature 1157:Main Bear.1 Temp
07.63 15353 SPN 1158: Main Bearing 2 Temperature 1158:Main Bear.2 Temp
07.64 15354 SPN 1159: Main Bearing 3 Temperature 1159:Main Bear.3 Temp
07.65 15355 SPN 1160: Main Bearing 4 Temperature 1160:Main Bear.4 Temp
07.66 15356 SPN 1161: Main Bearing 5 Temperature 1161:Main Bear.5 Temp
07.67 15357 SPN 1162: Main Bearing 6 Temperature 1162:Main Bear.6 Temp
07.68 15358 SPN 1163: Main Bearing 7 Temperature 1163:Main Bear.7 Temp
07.69 15359 SPN 1164: Main Bearing 8 Temperature 1164:Main Bear.8 Temp
07.70 15360 SPN 1165: Main Bearing 9 Temperature 1165:Main Bear.9 Temp
07.73 15363 SPN 1172: Turbo 1 Compressor Inlet Tem‐ 1172:Tb1 Compr.Int.T
perature
07.74 15364 SPN 1173: Turbo 2 Compressor Inlet Tem‐ 1173:Tb2 Compr.Int.T
perature
07.75 15365 SPN 1174: Turbo 3 Compressor Inlet Tem‐ 1174:Tb3 Compr.Int.T
perature
07.76 15366 SPN 1175: Turbo 4 Compressor Inlet Tem‐ 1175:Tb4 Compr.Int.T
perature
07.77 15367 SPN 1176: Turbo 1 Compressor Inlet pres‐ 1176:Tb1 Compr.Int.Pr
sure
07.78 15368 SPN 1177: Turbo 2 Compressor Inlet pres‐ 1177:Tb2 Compr.Int.Pr
sure
07.79 15369 SPN 1178: Turbo 3 Compressor Inlet pres‐ 1178:Tb3 Compr.Int.Pr
sure
07.80 15370 SPN 1179: Turbo 4 Compressor Inlet pres‐ 1179:Tb4 Compr.Int.Pr
sure
07.89 15379 SPN 1203: Engine Auxiliary Coolant Pres‐ 1203:Aux.Coolant Pr.
sure
07.91 15381 SPN 1212: Engine Auxiliary Coolant Tem‐ 1212:Aux.Coolant Temp
perature
07.92 15382 SPN 1382: Fuel Filter Difference Pressure 1382:Fuel Filt.DiffPr
07.97 15387 SPN 2433: Right Exhaust Gas Tempera‐ 2433:Right Exh.Gas T
ture
07.98 15388 SPN 2434: Left Exhaust Gas Temperature 2434:Left Exh.Gas T
09.12 12012 SPN 250 Engine Total Fuel Used 250: Total fuel used
09.13 12013 SPN 247 Total Engine hours 247: Total Eng. hours
09.16 12020 SPN 3719: DPF 1 Soot load 3719: DPF 1 Soot load
09.17 12021 SPN 3720: DPF 1 Ash load 3720: DPF 1 Ash load
10.04 15703 Battery voltage Battery voltage [%] Percentage value related on Battery
Voltage 24V.
10.06 15705 Calculated ground current Calc.ground curr.[%] Calculated Percentage value related
on Rated Ground Current
10.07 15706 Direct measured ground current Meas.ground curr.[%] Measured percentage value related
on Rated Ground Current
10.08 5570 Free PID 1 analog output (PID1 bias) AM PID1 bias
10.09 5597 Free PID 2 analog output (PID2 bias) AM PID2 bias
10.10 5682 Free PID 3 analog output (PID3 bias) AM PID3 bias
10.11 15710 Active nominal power in system System nominal P [%] Percentage value related on System
rated active power
10.12 15711 Total real power in system System real P [%] Percentage value related on System
rated active power
10.13 15712 Reserve real power in system Syst.res.real P [%] Percentage value related on System
rated active power
10.57 9857 Direct measured ground current Meas.ground curr.[A] Current format
10.61 9858 Active nominal power in system System nominal P [W] Power format
10.62 9859 Total real power in system System real P [W] Power format
10.63 9860 Reserve real power in system Syst.res.real P [W] Power format
10.66 15722 Total reactive power in system Syst.react.pwr.[var] Reactive Power Format
11.01 15700 Engine speed Engine speed [%] Percentage value related on Engine
rated Speed.
11.04 15704 Analog input D+ Analog input D+ [%] Percentage value related on Battery
Voltage 24V.
11.56 15716 Average Cylinder temp. bank 1 Cyl.temp.bank 1 [°C] Temperature Format
11.57 15717 Average Cylinder temp. bank 2 Cyl.temp.bank 2 [°C] Temperature Format
11.59 11566 Cooldown time Cooldown time [s] Seconds format. Remaining time only!
11.60 11567 Preglow time Preglow time [s] Seconds format. Remaining time only!
11.61 11568 Eng. monit. delay Eng. monit. delay [s] Seconds format. Remaining time only!
11.62 11569 Auxil.serv.prerun Auxil.serv.prerun [s] Seconds format. Remaining time only!
11.64 11572 Stop engine Stop engine [s] Seconds format. Remaining time only!
81.05 9316 Active power setpoint 1 source [W] AM ActPower SP1 [W]
81.06 9318 Active power setpoint 2 source [W] AM ActPower SP2 [W]
81.07 9321 Active power setpoint 3 source [W] AM ActPower SP3 [W]
81.08 9323 Active power setpoint 4 source [W] AM ActPower SP4 [W]
90.01 7693 Screen 1 row 1 AM Cust. screen 1.1 Customer defined screen
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.
VDO 120 °C 1 °C 69 °C 69
VDO 150 °C 1 °C 73 °C 73
5518 AM Frequency SP1[Hz] Analog1 ("A1 =") 05.51 Internal f setp1 [Hz]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5519 AM Frequency SP2[Hz] Analog1 ("A1 =") 05.52 Internal f setp2 [Hz]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5539 AM ActPower SP1 [W] Analog1 ("A1 =") 05.54 Internal P setp1 [W]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5540 AM ActPower SP2 [W] Analog1 ("A1 =") 05.55 Internal P setp2 [W]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5606 AM ActPower SP3 [W] Analog1 ("A1 =") 05.80 Internal P setp3 [W]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5609 AM ActPower SP4 [W] Analog1 ("A1 =") 05.84 Internal P setp4 [W]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5638 AM PF/var SP1[-/var] Analog1 ("A1 =") 05.10 Intern. PF setp1 [%]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5639 AM PF/var SP2[-/var] Analog1 ("A1 =") 05.11 Intern. PF setp2 [%]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5618 AM Voltage SP1 [V] Analog1 ("A1 =") 05.57 Internal V setp1 [V]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5619 AM Voltage SP2 [V] Analog1 ("A1 =") 05.58 Internal V setp2 [V]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5577 AM PID1 setpoint Analog1 ("A1 =") 05.75 Int. PID1 setpoint
Operators
Operators-Unary1 —————
Operators-Unary2 —————
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5590 AM PID2 setpoint Analog1 ("A1 =") 05.76 Int. PID2 setpoint
Operators
Operators-Unary1 —————
Operators-Unary2 —————
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5676 AM PID3 setpoint Analog1 ("A1 =") 05.77 Int. PID3 setpoint
Operators
Operators-Unary1 —————
Operators-Unary2 —————
Operators
Operators-Unary1 —————
Operators-Unary2 —————
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5200 AM Data source AO1 Analog1 ("A1 =") 11.03 Speed bias [%]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
5214 AM Data source AO2 Analog1 ("A1 =") 11.02 Voltage bias [%]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
10237 AM Data source ext.AO1 Analog1 ("A1 =") 11.03 Speed bias [%]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
10247 AM Data source ext.AO2 Analog1 ("A1 =") 11.03 Speed bias [%]
Operators
Operators-Unary1 —————
Operators-Unary2 —————
10257 AM Data source ext.AO3 Analog1 ("A1 =") 11.03 Speed bias [%]
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
10267 AM Data source ext.AO4 Analog1 ("A1 =") 11.03 Speed bias [%]
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
8891 AM Engine speed Analog1 ("A1 =") 11.51 Engine speed [rpm]
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
8893 AM Engine oil pressure Analog1 ("A1 =") 07.07 100:Engine Oil Press.
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
8897 AM Engine fuel level Analog1 ("A1 =") 06.03 Analog input 3
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
8899 AM Engine batt.voltage Analog1 ("A1 =") 10.54 Battery voltage [V]
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
8901 AM Engine coolant temp. Analog1 ("A1 =") 07.15 110:Eng.Coolant Temp.
Operators 5
Operators-Unary1 —————
Operators-Unary2 —————
Alarm class Visible in the dis‐ LED "Alarm" Relay "Command: Shut-down engine Engine blocked
play open GCB" until ack.
& horn 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:
n 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.
Shutdown Alarm With this alarm the GCB is opened and the engine is stopped. Coasting occurs.
n Alarm text + flashing LED "Alarm" + Relay centralized alarm (horn) + GCB open + Coasting + Engine stop.
Shutdown Alarm With this alarm the GCB is opened and the engine is stopped. Coasting occurs.
n Alarm text + flashing LED "Alarm" + Relay centralized alarm (horn) + GCB open + Coasting + Engine stop.
Shutdown Alarm With this alarm the GCB is opened immediately and the engine is stopped.
n Alarm text + flashing LED "Alarm" + Relay centralized alarm (horn) + GCB open + Engine stop.
Shutdown Alarm With this alarm the GCB is opened immediately and the engine is stopped.
n 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.
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 Ä p. 381) with
the alarm class configured to "F" (param‐
eter 2601 Ä p. 382).
Minimum run time Load dependent start/stop (LDSS) minimum run time
13276 Shows the current state of LDSS in the sequencing screen. A countdown of the configured minimum run
time will be displayed.
Gen. rev/red. pwr. 1 Generator reverse power, limit value 1 / Generator reduced power, limit value 1
2262 The generator power has exceeded the limit value 1 for generator reverse power / generator reduced
power for at least the configured time and does not fall below the value of the hysteresis.
Gen. rev/red. pwr. 2 Generator reverse power, limit value 2 / Generator reduced power, limit value 2
2263 The generator power has exceeded the limit value 2 for generator reverse power / generator reduced
power for at least the configured time and does not fall below the value of the hysteresis.
Oper.range failed 1 Measured values checked but not within operating range
Oper.range failed 2 An alarm will be issued if check x result is negative because measured values are not within the config‐
ured operating range. No alarm will be issued in idle mode.
Oper.range failed 3
For details refer to Ä Chapter 4.5.6.14 “Operating Range Failure” on page 409.
Oper.range failed 4
Notes
Oper.range failed 5
Check 6 to 10 are related to GGB and so NOT available in easYgen-3100XT/3200XT.
Oper.range failed 6
Oper.range failed 7
Oper.range failed 8
Oper.range failed 9
Oper.range failed 10
Oper.range failed 11
Oper.range failed 12
2665 to 2676
Message ID 10600 10601 10602 10603 10604 10605 10607 10608 10609 10610 10611 10612
Message ID 10018 10019 10020 10021 10022 10023 10024 10025 10026 10027
Flexible limit # 11 12 13 14 15 16 17 18 19 20
Message ID 10028 10029 10030 10031 10032 10033 10034 10035 10036 10037
Flexible limit # 21 22 23 24 25 26 27 28 29 30
Message ID 10038 10039 10040 10041 10042 10043 10044 10045 10046 10047
Flexible limit # 31 32 33 34 35 36 37 38 39 40
Message ID 10048 10049 10050 10051 10052 10053 10054 10055 10056 10057
9.6 Formulas
9.6.1 Load Dependent Start Stop (LDSS) Formulas
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
Preserve islanded 5760 Minimum permissible reserve power on busbar in islanded operation
Preserve parallel 5768 Minimum permissible reserve power on busbar 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
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
Starting the First Engine Combination (no engine supplies the PMNsetpoint – PMN real + PGN real active > PMOP minimum
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
Stopping the Last Engine Combination (load close to minimum PMN setpoint – PMN real + PGN real active < PMOPminimum – Physteresis
load) MOP
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)
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
Task Formula
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 minimum PMN setpoint – PMN real + PGN real active < PMOPminimum – Physteresis
load) MOP
LDSS dynamic
Dynamic characteristic = [(max. generator load – min. generator load) * dynamic] + (min. generator load)
Moderate dynamic = 50 %
High dynamic = 75 %
2 CAN-L N/A
3 Shield N/A
4 CAN-H N/A
4 - Reserved
5 - Reserved
7 - Reserved
11 Index
A G
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 GCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Free configurable . . . . . . . . . . . . . . . . . . . . . 391 Application . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Analog Fixed Values . . . . . . . . . . . . . . . . . . . . . 857 Synchronization . . . . . . . . . . . . . . . . . . . . . . 382
Analog Results . . . . . . . . . . . . . . . . . . . . . . . . . 857 Generator
Analog Variables . . . . . . . . . . . . . . . . . . . . . . . . 857 Ground Fault . . . . . . . . . . . . . . . . . . . . . . . . 330
AnalogManager Fixed Values . . . . . . . . . . . . . . 857 Inverse Time-Overcurrent . . . . . . . . . . . . . . 312
AnalogManager Results . . . . . . . . . . . . . . . . . . 857 Lagging Power Factor . . . . . . . . . . . . . . . . . 327
AnalogManager sample . . . . . . . . . . . . . . . 455, 456 Overfrequency . . . . . . . . . . . . . . . . . . . . . . . 308
AnalogManager Variables . . . . . . . . . . . . . . . . . 857 Overvoltage . . . . . . . . . . . . . . . . . . . . . . . . . 303
Phase Rotation . . . . . . . . . . . . . . . . . . . . . . . 333
B
Reverse/Reduced Power . . . . . . . . . . . . . . . 319
Battery
Speed Detection . . . . . . . . . . . . . . . . . . . . . . 337
Monitoring . . . . . . . . . . . . . . . . . . . . . . 400, 401
Unbalanced Load . . . . . . . . . . . . . . . . . . . . . 321
BDEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Underfrequency . . . . . . . . . . . . . . . . . . . . . . 309
C Undervoltage . . . . . . . . . . . . . . . . . . . . . . . . 304
CAN Voltage asymmetry . . . . . . . . . . . . . . . . . . . 306
J1939 Interface . . . . . . . . . . . . . . . . . . . . . . 394 Grid Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Monitoring . . . . . . . . . . . . . . . . . . . . . . 393, 394
H
Contact person . . . . . . . . . . . . . . . . . . . . . . . . . . 28
HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Critical Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Home Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Customer Service . . . . . . . . . . . . . . . . . . . . . . . . 28
I
D
Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Droop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
IOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
E islanded Parallel Operation . . . . . . . . . . . . . . . . 293
Engine J
Overspeed . . . . . . . . . . . . . . . . . . . . . . . . . . 335
J1939 Interface . . . . . . . . . . . . . . . . . 394, 397, 398
Shutdown Malfunction . . . . . . . . . . . . . . . . . 339
Speed Detection . . . . . . . . . . . . . . . . . . . . . . 337 L
Start Failure . . . . . . . . . . . . . . . . . . . . . . . . . 338 LDSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Underspeed . . . . . . . . . . . . . . . . . . . . . . . . . 336 Load Control . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Unintended Stop . . . . . . . . . . . . . . . . . . . . . 340 Load Dependent Start Stop . . . . . . . . . . . . . . . . 285
Engine/Generator Load Share Control . . . . . . . . . . . . . . . . . . . . . . 238
Active Power Mismatch . . . . . . . . . . . . . . . . 325
M
Unloading Mismatch . . . . . . . . . . . . . . . . . . . 326
Mains
Engine/Mains
Blocking protection . . . . . . . . . . . . . . . . . . . . 346
Active Power Mismatch . . . . . . . . . . . . . . . . 377
Change Of Frequency . . . . . . . . . . . . . . . . . 369
Ethernet
Decoupling . . . . . . . . . . . . . . . . . . . . . . . . . . 348
ToolKit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Export Power . . . . . . . . . . . . . . . . . . . . . . . . 376
Import Power . . . . . . . . . . . . . . . . . . . . . . . . 374
Lagging Power Factor . . . . . . . . . . . . . . . . . 378
O
Operating Range Failure . . . . . . . . . . . . . . . . . . 409
P
Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
PID Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Power Factor Control . . . . . . . . . . . . . . . . . . . . 230
Protective equipment . . . . . . . . . . . . . . . . . . . . . 34
S
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Symbols
in the instructions . . . . . . . . . . . . . . . . . . . . . . 26
T
Temperature
Cylinder Temperature . . . . . . . . . . . . . . . . . . 341
U
USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
V
VDE-AR-N 4105 . . . . . . . . . . . . . . . . . . . . . . . . 351
Voltage Control . . . . . . . . . . . . . . . . . . . . . . . . . 227
W
Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Woodward GmbH
Handwerkstrasse 29 - 70565 Stuttgart - Germany
Phone +49 (0) 711 789 54-510
Fax +49 (0) 711 789 54-101
[email protected]