Ppu 300 Designers Handbook 4189341097 Uk

DESIGNER'S HANDBOOK
PPU 300
Paralleling and Protection Unit
4189341097S
1. About the Designer's handbook
1.1 Intended users of the Designer's handbook............................................................................................................................................................ 14
1.2 Symbols and conventions.................................................................................................................................................................................................. 14
1.3 Software versions................................................................................................................................................................................................................... 16
1.4 Technical support .................................................................................................................................................................................................................. 16
1.5 Warnings and safety.............................................................................................................................................................................................................. 17
1.6 Legal information.................................................................................................................................................................................................................... 19
2. System principles
2.1 About the controllers............................................................................................................................................................................................................ 21
2.1.1 About.....................................................................................................................................................................................................................................21
2.1.2 Controller types................................................................................................................................................................................................................ 21
2.1.3 About the display unit DU 300....................................................................................................................................................................................22
2.1.4 Display unit DU 300 options........................................................................................................................................................................................22
2.2 Application as a system...................................................................................................................................................................................................... 25
2.2.1 How it works.......................................................................................................................................................................................................................25
2.2.2 Application single-line diagram.................................................................................................................................................................................. 27
2.2.3 Change controller type.................................................................................................................................................................................................. 28
2.2.4 Maximum number of controllers................................................................................................................................................................................ 29
2.2.5 Control and command structure................................................................................................................................................................................ 30
2.2.6 Priority of input sources................................................................................................................................................................................................ 31
2.3 Control and modes................................................................................................................................................................................................................. 31
2.3.1 About the control modes...............................................................................................................................................................................................31
2.3.2 Switchboard control........................................................................................................................................................................................................ 32
2.3.3 Local control (default).................................................................................................................................................................................................... 33
2.3.4 Remote control................................................................................................................................................................................................................. 33
2.3.5 Command sources.......................................................................................................................................................................................................... 33
2.3.6 Controller not powered.................................................................................................................................................................................................. 35
2.4 Controller functions............................................................................................................................................................................................................... 36
2.5 CODESYS (optional).............................................................................................................................................................................................................. 36
2.5.1 Inputs and outputs...........................................................................................................................................................................................................36
2.5.2 Activating controller outputs........................................................................................................................................................................................ 37
2.6 Alarms and protections....................................................................................................................................................................................................... 37
2.6.1 How alarm processing works......................................................................................................................................................................................37
2.6.2 Alarm parameters............................................................................................................................................................................................................ 41
2.6.3 Common alarm actions................................................................................................................................................................................................. 45
2.6.4 Alarm levels........................................................................................................................................................................................................................47
2.6.5 Operate time...................................................................................................................................................................................................................... 48
2.6.6 Acknowledge an alarm.................................................................................................................................................................................................. 48
2.6.7 Alarm latch and reset..................................................................................................................................................................................................... 49
2.6.8 Shelve an alarm............................................................................................................................................................................................................... 50
2.6.9 Out of service an alarm................................................................................................................................................................................................. 51
2.6.10 Alarm test......................................................................................................................................................................................................................... 51
2.6.11 Alarm status digital outputs....................................................................................................................................................................................... 52
2.6.12 Customising alarms......................................................................................................................................................................................................54
2.6.13 Customised inhibits...................................................................................................................................................................................................... 54
2.6.14 Suppress action inhibit................................................................................................................................................................................................55
2.7 CustomLogic..............................................................................................................................................................................................................................55
2.7.1 Use CustomLogic............................................................................................................................................................................................................ 55
DESIGNER'S HANDBOOK 4189341097S EN Page 2 of 396

2.7.2 Enable CustomLogic...................................................................................................................................................................................................... 55
2.7.3 Digital inputs and outputs (optional)........................................................................................................................................................................ 56
2.7.4 Custom parameters........................................................................................................................................................................................................ 56
2.7.5 Activate controller outputs............................................................................................................................................................................................56
2.7.6 CustomLogic and Modbus........................................................................................................................................................................................... 56
2.7.7 Restrictions.........................................................................................................................................................................................................................57
2.8 Emulation..................................................................................................................................................................................................................................... 57
2.9 Custom parameters................................................................................................................................................................................................................57
2.10 Date and time.......................................................................................................................................................................................................................... 57
2.10.1 About date and time settings....................................................................................................................................................................................57
2.10.2 Set the time manually..................................................................................................................................................................................................59
2.10.3 Use external NTP servers......................................................................................................................................................................................... 59
2.11 Permissions............................................................................................................................................................................................................................. 59
2.11.1 User settings....................................................................................................................................................................................................................61
2.11.2 Group settings................................................................................................................................................................................................................ 61
2.11.3 Default users................................................................................................................................................................................................................... 62
2.11.4 Default group permissions......................................................................................................................................................................................... 63
2.12 Event log.................................................................................................................................................................................................................................... 68
2.13 Non-Essential Loads (NEL)............................................................................................................................................................................................. 68
2.13.1 Non-essential load trip (NEL) function................................................................................................................................................................. 68
2.14 Lamp test...................................................................................................................................................................................................................................71
2.15 Alive..............................................................................................................................................................................................................................................72
3. Busbar sections and load sharing

3.1 About busbar sections......................................................................................................................................................................................................... 74
3.1.1 Dynamic busbar sections............................................................................................................................................................................................. 74
3.1.2 Externally controlled bus tie breaker....................................................................................................................................................................... 75
3.1.3 Externally controlled shore connection...................................................................................................................................................................76
3.1.4 Ring busbar connection................................................................................................................................................................................................ 77
3.2 Busbar section load sharing............................................................................................................................................................................................. 77
3.2.1 Busbar section characteristics................................................................................................................................................................................... 77
3.2.2 DEIF network load sharing.......................................................................................................................................................................................... 77
3.3 Load sharing alarms.............................................................................................................................................................................................................. 78
3.3.1 P load sharing failure..................................................................................................................................................................................................... 78
3.3.2 Q load sharing failure..................................................................................................................................................................................................... 79
3.3.3 External breaker # position failure............................................................................................................................................................................ 80
3.3.4 Any bus tie breaker position failure.......................................................................................................................................................................... 80
3.4 Network alarms.........................................................................................................................................................................................................................81
3.4.1 Blackout detection mismatch...................................................................................................................................................................................... 81
3.4.2 Missing all controllers.....................................................................................................................................................................................................81
3.4.3 Missing controller ID #................................................................................................................................................................................................... 81
3.4.4 Duplicate controller ID................................................................................................................................................................................................... 82
3.4.5 Single-line missing/none active................................................................................................................................................................................. 82
3.4.6 Different single-line configurations........................................................................................................................................................................... 82
3.4.7 Controller not part of system.......................................................................................................................................................................................82
3.4.8 Missing any controller.................................................................................................................................................................................................... 82
3.4.9 DEIF network redundancy broken............................................................................................................................................................................ 83
3.4.10 DEIF network top ring redundancy broken.........................................................................................................................................................83

4. AC configuration and nominal settings
4.1 AC configuration......................................................................................................................................................................................................................84
4.1.1 [Source] and [Busbar] for each controller type....................................................................................................................................................86
4.1.2 [Source] AC configuration............................................................................................................................................................................................ 86
4.1.3 [Busbar] AC configuration............................................................................................................................................................................................ 89
4.1.4 Voltage and frequency as digital outputs...............................................................................................................................................................90
4.1.5 4th current input configuration....................................................................................................................................................................................91
4.2 Nominal settings...................................................................................................................................................................................................................... 91
4.2.1 About the nominal settings.......................................................................................................................................................................................... 91
4.2.2 Nominal power calculations........................................................................................................................................................................................ 93
4.2.3 Power transformer...........................................................................................................................................................................................................93
4.3 AC measurement filters....................................................................................................................................................................................................... 94
4.3.1 About AC measurement filters................................................................................................................................................................................... 94
4.3.2 AC measurement filters................................................................................................................................................................................................ 94
4.4 AC measurements as analogue outputs.................................................................................................................................................................... 94
4.4.1 About AC measurements as analogue outputs ................................................................................................................................................. 94
4.4.2 [Source] AC measurements........................................................................................................................................................................................ 95
4.4.3 [Busbar] AC measurements........................................................................................................................................................................................ 99
4.4.4 4th current input.............................................................................................................................................................................................................101
4.5 Source AC protections...................................................................................................................................................................................................... 101
4.5.1 About AC protections.................................................................................................................................................................................................. 101
4.5.2 [Source] over-voltage (ANSI 59).............................................................................................................................................................................102
4.5.3 [Source] under-voltage (ANSI 27).......................................................................................................................................................................... 102
4.5.4 [Source] voltage unbalance (ANSI 47)................................................................................................................................................................ 103
4.5.5 Negative sequence voltage (ANSI 47)................................................................................................................................................................. 104
4.5.6 Zero sequence voltage (ANSI 59Uo)....................................................................................................................................................................105
4.5.7 Over-current (ANSI 50TD)........................................................................................................................................................................................ 106
4.5.8 Fast over-current (ANSI 50/50TD)......................................................................................................................................................................... 106
4.5.9 Current unbalance (ANSI 46)...................................................................................................................................................................................107
4.5.10 Directional over-current (ANSI 67)...................................................................................................................................................................... 108
4.5.11 Inverse time over-current (ANSI 51)................................................................................................................................................................... 109
4.5.12 Negative sequence current (ANSI 46)............................................................................................................................................................... 112
4.5.13 Zero sequence current (ANSI 51Io).................................................................................................................................................................... 113
4.5.14 [Source] over-frequency (ANSI 81O)................................................................................................................................................................. 114
4.5.15 [Source] under-frequency (ANSI 81U)............................................................................................................................................................... 114
4.5.16 Overload (ANSI 32)....................................................................................................................................................................................................115
4.5.17 Reverse power (ANSI 32R).................................................................................................................................................................................... 116
4.5.18 Overload reverse power (ANSI 32R)..................................................................................................................................................................116
4.5.19 Reactive power export (ANSI 40O).....................................................................................................................................................................117
4.5.20 Reactive power import (ANSI 40U)..................................................................................................................................................................... 118
4.5.21 Generator differential current protection (ANSI 87G).................................................................................................................................. 118
4.5.22 Synchronisation check, including blackout close (ANSI 25).....................................................................................................................119
4.6 Busbar AC protections...................................................................................................................................................................................................... 120
4.6.1 [Busbar] over-voltage (ANSI 59).............................................................................................................................................................................120
4.6.2 [Busbar] under-voltage (ANSI 27).......................................................................................................................................................................... 121
4.6.3 [Busbar] voltage unbalance (ANSI 47)................................................................................................................................................................ 122
4.6.4 [Busbar] over-frequency (ANSI 81O)....................................................................................................................................................................123
4.6.5 [Busbar] under-frequency (ANSI 81U)................................................................................................................................................................. 124

4.7 Other AC protections.......................................................................................................................................................................................................... 124
4.7.1 Lockout relay (ANSI 86)............................................................................................................................................................................................. 124
4.7.2 Earth inverse time over-current (ANSI 51G)..................................................................................................................................................... 126
4.7.3 Neutral inverse time over-current (ANSI 51N).................................................................................................................................................. 127
5. Alarms and protections

5.1 Non-essential loads............................................................................................................................................................................................................. 129
5.1.1 NEL # over-current....................................................................................................................................................................................................... 129
5.1.2 NEL # under-frequency.............................................................................................................................................................................................. 129
5.1.3 NEL # overload.............................................................................................................................................................................................................. 130
5.1.4 NEL # reactive overload............................................................................................................................................................................................. 131
5.2 General system alarms...................................................................................................................................................................................................... 131
5.2.1 System not OK............................................................................................................................................................................................................... 131
5.2.2 Critical process error................................................................................................................................................................................................... 132
5.2.3 Configuration update delayed..................................................................................................................................................................................132
5.2.4 Not under remote control........................................................................................................................................................................................... 132
5.2.5 Fieldbus connection missing.................................................................................................................................................................................... 132
5.2.6 Fieldbus conflict............................................................................................................................................................................................................. 133
5.2.7 Controller ID not configured......................................................................................................................................................................................133
5.2.8 Trip AVR output not configured............................................................................................................................................................................... 133
5.2.9 NTP server not connected........................................................................................................................................................................................ 133
5.2.10 NTP server no response......................................................................................................................................................................................... 133
5.2.11 Live power detected (emulation).......................................................................................................................................................................... 133
5.2.12 Emulation disabled (live power)........................................................................................................................................................................... 133
5.3 Custom input alarms...........................................................................................................................................................................................................134
5.3.1 Digital input (DI) alarms.............................................................................................................................................................................................. 134
5.3.2 Analogue input (AI) alarms....................................................................................................................................................................................... 134
5.4 General hardware module alarms................................................................................................................................................................................135
5.4.1 Software mismatch on hardware module(s)...................................................................................................................................................... 135
5.4.2 Required I/O card(s) not found................................................................................................................................................................................135
5.5 Power supply module PSM3.1....................................................................................................................................................................................... 136
5.5.1 PSM3.1 1 supply voltage low alarm...................................................................................................................................................................... 136
5.5.2 PSM3.1 1 supply voltage high alarm.................................................................................................................................................................... 136
5.6 Power supply module PSM3.2....................................................................................................................................................................................... 137
5.6.1 PSM3.2 1 supply voltage low alarm...................................................................................................................................................................... 137
5.6.2 PSM3.2 1 supply voltage high alarm.................................................................................................................................................................... 137
5.7 Alternating current module ACM3.1........................................................................................................................................................................... 137
5.7.1 [Source]/[Busbar] L1-L2-L3 wire break................................................................................................................................................................ 137
5.7.2 [Source]/[Busbar] L# wire break............................................................................................................................................................................. 138
5.7.3 ACM 1 data is missing................................................................................................................................................................................................ 139
5.7.4 ACM 1 protections not running................................................................................................................................................................................139
5.8 Engine interface module EIM3.1................................................................................................................................................................................... 140
5.8.1 EIM3.1 # supply voltage low or missing alarm................................................................................................................................................. 140
5.8.2 EIM3.1 # supply voltage high alarm...................................................................................................................................................................... 140
5.8.3 Magnetic pickup wire break alarm......................................................................................................................................................................... 141
5.8.4 EIM3.1 # relay 4 wire break alarm......................................................................................................................................................................... 141
5.8.5 EIM3.1 safety shutdown still has control............................................................................................................................................................. 141
5.8.6 EIM3.1 safety shutdown configuration is not correct..................................................................................................................................... 141
5.9 Governor and AVR module GAM3.2........................................................................................................................................................................... 142

5.9.1 GAM3.2 1 status not OK............................................................................................................................................................................................ 142
5.9.2 GAM3.2 1 supply voltage low or missing............................................................................................................................................................ 142
5.9.3 GAM3.2 1 supply voltage high alarm....................................................................................................................................................................142
5.10 Processor and communication module PCM3.1...............................................................................................................................................143
5.10.1 Controller temperature too high............................................................................................................................................................................143
5.10.2 PCM clock battery failure alarm........................................................................................................................................................................... 143
5.10.3 Network protocol incompatible..............................................................................................................................................................................143
5.11 CODESYS alarms............................................................................................................................................................................................................... 143
5.11.1 CODESYS application not OK.............................................................................................................................................................................. 143
5.11.2 CODESYS configuration conflict.......................................................................................................................................................................... 143
6. Breakers, synchronisation and de-loading

6.1 About........................................................................................................................................................................................................................................... 145
6.1.1 How it works.................................................................................................................................................................................................................... 145
6.1.2 Regulation required for synchronisation..............................................................................................................................................................145
6.1.3 Regulation required for de-loading........................................................................................................................................................................ 145
6.2 Synchronisation in each control mode.....................................................................................................................................................................146
6.2.1 Synchronisation in LOCAL mode........................................................................................................................................................................... 146
6.2.2 Synchronisation in REMOTE mode...................................................................................................................................................................... 146
6.2.3 Synchronisation in switchboard control............................................................................................................................................................... 146
6.3 Configuring breakers.......................................................................................................................................................................................................... 147
6.3.1 Breaker commands...................................................................................................................................................................................................... 147
6.3.2 Pulse breaker..................................................................................................................................................................................................................147
6.3.3 Compact breaker...........................................................................................................................................................................................................149
6.3.4 Continuous breaker...................................................................................................................................................................................................... 152
6.3.5 Redundant breaker feedback.................................................................................................................................................................................. 154
6.3.6 Breaker state outputs.................................................................................................................................................................................................. 155
6.4 Synchronisation functions.............................................................................................................................................................................................. 155
6.4.1 Dynamic synchronisation...........................................................................................................................................................................................155
6.4.2 Static synchronisation................................................................................................................................................................................................. 159
6.4.3 Regulator synchronisation parameters................................................................................................................................................................ 162
6.4.4 Synchronisation status outputs............................................................................................................................................................................... 163
6.5 Synchronisation and breaker alarms.........................................................................................................................................................................163
6.5.1 Breaker synchronisation failure...............................................................................................................................................................................163
6.5.2 De-load failure................................................................................................................................................................................................................ 164
6.5.3 Vector mismatch............................................................................................................................................................................................................ 165
6.5.4 Breaker opening failure.............................................................................................................................................................................................. 165
6.5.5 Breaker closing failure................................................................................................................................................................................................ 166
6.5.6 Breaker position failure............................................................................................................................................................................................... 166
6.5.7 Breaker trip (external)................................................................................................................................................................................................. 167
6.5.8 Breaker short circuit..................................................................................................................................................................................................... 167
6.5.9 Phase sequence error.................................................................................................................................................................................................168
6.5.10 Breaker configuration failure..................................................................................................................................................................................168
7. Regulation
7.1 About regulation....................................................................................................................................................................................................................169
7.1.1 How it works.................................................................................................................................................................................................................... 169
7.1.2 Analogue regulation..................................................................................................................................................................................................... 169
7.1.3 Relay regulation.............................................................................................................................................................................................................172
7.1.4 Droop..................................................................................................................................................................................................................................174

7.1.5 Regulation rules.............................................................................................................................................................................................................176
7.1.6 Freeze regulation.......................................................................................................................................................................................................... 179
7.2 Governor regulation modes............................................................................................................................................................................................ 180
7.2.1 How it works.................................................................................................................................................................................................................... 180
7.2.2 Deactivate regulation...................................................................................................................................................................................................180
7.2.3 Fixed frequency............................................................................................................................................................................................................. 180
7.2.4 Fixed power..................................................................................................................................................................................................................... 181
7.2.5 Frequency droop........................................................................................................................................................................................................... 184
7.2.6 Power load sharing.......................................................................................................................................................................................................185
7.2.7 Manual regulation......................................................................................................................................................................................................... 186
7.2.8 Governor stand-alone mode.....................................................................................................................................................................................188
7.2.9 Frequency synchronisation....................................................................................................................................................................................... 190
7.2.10 Phase synchronisation............................................................................................................................................................................................. 190
7.3 AVR regulation modes....................................................................................................................................................................................................... 191
7.3.1 How it works.................................................................................................................................................................................................................... 191
7.3.2 Deactivate regulation...................................................................................................................................................................................................191
7.3.3 Fixed voltage...................................................................................................................................................................................................................192
7.3.4 Fixed reactive power................................................................................................................................................................................................... 192
7.3.5 Fixed cos phi................................................................................................................................................................................................................... 196
7.3.6 Voltage droop..................................................................................................................................................................................................................198
7.3.7 Reactive power load sharing.................................................................................................................................................................................... 199
7.3.8 Manual regulation......................................................................................................................................................................................................... 201
7.3.9 AVR stand-alone mode...............................................................................................................................................................................................202
7.4 External communication................................................................................................................................................................................................... 204
7.4.1 How it works.................................................................................................................................................................................................................... 204
7.4.2 External set point (network)...................................................................................................................................................................................... 204
7.4.3 External set points........................................................................................................................................................................................................ 206
7.5 Governor.................................................................................................................................................................................................................................... 208
7.5.1 Governor regulation function.................................................................................................................................................................................... 208
7.5.2 Governor analogue regulation function............................................................................................................................................................... 210
7.5.3 Governor relay regulation function........................................................................................................................................................................ 212
7.6 Automatic voltage regulator........................................................................................................................................................................................... 213
7.6.1 AVR regulation function.............................................................................................................................................................................................. 213
7.6.2 AVR analogue regulation function..........................................................................................................................................................................216
7.6.3 AVR relay regulation parameters........................................................................................................................................................................... 217
7.7 Configuration alarms.......................................................................................................................................................................................................... 218
7.7.1 GOV relay setup incomplete.................................................................................................................................................................................... 218
7.7.2 AVR relay setup incomplete..................................................................................................................................................................................... 219
7.7.3 GOV output selection failure.................................................................................................................................................................................... 219
7.7.4 AVR output selection failure..................................................................................................................................................................................... 219
7.7.5 GOV stand-alone configuration error....................................................................................................................................................................219
7.7.6 AVR stand-alone configuration error.....................................................................................................................................................................220
7.8 Regulation alarms................................................................................................................................................................................................................ 220
7.8.1 GOV regulation error................................................................................................................................................................................................... 220
7.8.2 AVR regulation error.................................................................................................................................................................................................... 221
7.8.3 GOV regulation mode not selected....................................................................................................................................................................... 222
7.8.4 AVR regulator mode not selected.......................................................................................................................................................................... 222
7.8.5 P load sharing failure...................................................................................................................................................................................................223

7.8.6 Q load sharing failure.................................................................................................................................................................................................. 223
8. Engine interface communication

8.1 About........................................................................................................................................................................................................................................... 225
8.1.1 How it works.................................................................................................................................................................................................................... 225
8.1.2 Example configuration for an ECU........................................................................................................................................................................ 226
8.2 Generic J1939......................................................................................................................................................................................................................... 228
8.2.1 J1939 measurements..................................................................................................................................................................................................228
8.3 ECU functions.........................................................................................................................................................................................................................233
8.3.1 ECU Power configuration.......................................................................................................................................................................................... 233
8.4 ECU protections.................................................................................................................................................................................................................... 234
8.4.1 ECU Communication failure alarm........................................................................................................................................................................ 234
8.4.2 ECU CAN bus off.......................................................................................................................................................................................................... 234
8.4.3 ECU Red stop lamp alarm........................................................................................................................................................................................ 234
8.4.4 ECU Amber warning lamp alarm............................................................................................................................................................................ 235
8.4.5 ECU Protect lamp alarm............................................................................................................................................................................................ 235
8.4.6 ECU Malfunction indicator lamp alarm.................................................................................................................................................................235
9. GENSET controller
9.1 About the GENSET controller........................................................................................................................................................................................ 237
9.1.1 GENSET controller functions................................................................................................................................................................................... 237
9.2 GENSET controller principles........................................................................................................................................................................................ 238
9.2.1 GENSET controller nominal settings.................................................................................................................................................................... 238
9.2.2 Run coil or stop coil...................................................................................................................................................................................................... 239
9.2.3 Running detection......................................................................................................................................................................................................... 240
9.2.4 Regulation........................................................................................................................................................................................................................ 244
9.2.5 Ready for operation......................................................................................................................................................................................................244
9.2.6 AC configuration............................................................................................................................................................................................................ 244
9.2.7 Breaker configuration.................................................................................................................................................................................................. 244
9.3 Engine start.............................................................................................................................................................................................................................. 244
9.3.1 Engine start function.................................................................................................................................................................................................... 244
9.3.2 Engine start flowchart..................................................................................................................................................................................................248
9.3.3 Engine start sequence................................................................................................................................................................................................ 249
9.3.4 Interruption of the start sequence.......................................................................................................................................................................... 252
9.4 Engine stop.............................................................................................................................................................................................................................. 252
9.4.1 Engine stop function.................................................................................................................................................................................................... 252
9.4.2 Engine stop flowchart.................................................................................................................................................................................................. 255
9.4.3 Engine stop sequence................................................................................................................................................................................................ 256
9.4.4 Engine shutdown flowchart....................................................................................................................................................................................... 257
9.5 Generator breaker................................................................................................................................................................................................................ 257
9.5.1 How it works.................................................................................................................................................................................................................... 257
9.5.2 Generator breaker close flowchart........................................................................................................................................................................ 258
9.5.3 Generator breaker blackout close flowchart...................................................................................................................................................... 259
9.5.4 Generator breaker open flowchart......................................................................................................................................................................... 261
9.5.5 Generator breaker trip flowchart............................................................................................................................................................................. 263
9.6 Other GENSET controller functions........................................................................................................................................................................... 263
9.6.1 Priming.............................................................................................................................................................................................................................. 263
9.6.2 Temperature-dependent power derating............................................................................................................................................................. 264
9.6.3 Engine operating values as analogue outputs..................................................................................................................................................265

9.6.4 Engine states as digital outputs.............................................................................................................................................................................. 265
9.6.5 Counters........................................................................................................................................................................................................................... 265
9.6.6 Trip AVR............................................................................................................................................................................................................................ 266
9.7 GENSET controller alarms...............................................................................................................................................................................................267
9.7.1 GENSET controller protections............................................................................................................................................................................... 267
9.7.2 Alarm actions.................................................................................................................................................................................................................. 268
9.7.3 Inhibits................................................................................................................................................................................................................................268
9.7.4 Breaker alarms............................................................................................................................................................................................................... 269
9.7.5 AC alarms.........................................................................................................................................................................................................................269
9.7.6 Emergency stop.............................................................................................................................................................................................................271
9.7.7 Overspeed........................................................................................................................................................................................................................271
9.7.8 Underspeed..................................................................................................................................................................................................................... 272
9.7.9 Crank failure.................................................................................................................................................................................................................... 272
9.7.10 Primary running feedback failure......................................................................................................................................................................... 273
9.7.11 Start failure.................................................................................................................................................................................................................... 273
9.7.12 Start enable removed during start....................................................................................................................................................................... 274
9.7.13 Stop failure.................................................................................................................................................................................................................... 274
9.7.14 Engine started (external)......................................................................................................................................................................................... 274
9.7.15 Engine stopped (external).......................................................................................................................................................................................275
9.7.16 Total running hours notification............................................................................................................................................................................. 275
9.7.17 Trip running hours notification............................................................................................................................................................................... 275
9.7.18 Voltage or frequency not OK................................................................................................................................................................................. 276
9.7.19 Other GENSET controller alarms........................................................................................................................................................................ 276
10. HYBRID controller

10.1 About the HYBRID controller....................................................................................................................................................................................... 277
10.1.1 HYBRID controller functions.................................................................................................................................................................................. 277
10.2 HYBRID controller principles.......................................................................................................................................................................................278
10.2.1 HYBRID controller nominal settings................................................................................................................................................................... 278
10.2.2 Start inverter or stop inverter................................................................................................................................................................................. 279
10.2.3 Running detection...................................................................................................................................................................................................... 279
10.2.4 Ready for operation................................................................................................................................................................................................... 280
10.2.5 AC configuration......................................................................................................................................................................................................... 280
10.2.6 Breaker configuration................................................................................................................................................................................................281
10.3 Inverter start..........................................................................................................................................................................................................................281
10.3.1 Inverter start function................................................................................................................................................................................................ 281
10.3.2 Inverter start flowchart.............................................................................................................................................................................................. 282
10.3.3 Inverter start sequence............................................................................................................................................................................................ 282
10.3.4 Interruption of the start sequence........................................................................................................................................................................283
10.4 Inverter stop.......................................................................................................................................................................................................................... 283
10.4.1 Inverter stop function................................................................................................................................................................................................ 283
10.4.2 Inverter stop flowchart.............................................................................................................................................................................................. 284
10.4.3 Inverter stop sequence.............................................................................................................................................................................................285
10.4.4 Inverter trip and stop flowchart............................................................................................................................................................................. 286
10.5 Inverter breaker................................................................................................................................................................................................................... 287
10.5.1 Introduction................................................................................................................................................................................................................... 287
10.5.2 Inverter breaker close flowchart........................................................................................................................................................................... 287
10.5.3 Inverter breaker open flowchart............................................................................................................................................................................289
10.5.4 Inverter breaker trip flowchart............................................................................................................................................................................... 290

10.6 Other HYBRID controller functions.......................................................................................................................................................................... 291
10.6.1 Temperature-dependent power derating.......................................................................................................................................................... 291
10.6.2 Percentage-dependent power derating.............................................................................................................................................................292
10.6.3 Inverter operating values as analogue outputs..............................................................................................................................................292
10.6.4 Inverter states as digital outputs.......................................................................................................................................................................... 292
10.6.5 Counters......................................................................................................................................................................................................................... 293
10.6.6 Trip AVR......................................................................................................................................................................................................................... 294
10.7 HYBRID controller protections................................................................................................................................................................................... 295
10.7.1 HYBRID controller alarms.......................................................................................................................................................................................295
10.7.2 Alarm actions................................................................................................................................................................................................................296
10.7.3 Inhibits............................................................................................................................................................................................................................. 296
10.7.4 Breaker alarms............................................................................................................................................................................................................ 297
10.7.5 AC alarms...................................................................................................................................................................................................................... 297
10.7.6 Emergency stop.......................................................................................................................................................................................................... 298
10.7.7 Start failure.................................................................................................................................................................................................................... 299
10.7.8 Stop failure.................................................................................................................................................................................................................... 299
10.7.9 Inverter started (external)........................................................................................................................................................................................300
10.7.10 Inverter stopped (external)................................................................................................................................................................................... 300
10.7.11 Total running hours notification...........................................................................................................................................................................301
10.7.12 Trip running hours notification............................................................................................................................................................................ 301
10.7.13 Voltage or frequency not OK............................................................................................................................................................................... 302
10.7.14 Other HYBRID controller alarms....................................................................................................................................................................... 302
11. SHAFT generator controller

11.1 About the SHAFT generator controller...................................................................................................................................................................303
11.1.1 SHAFT generator controller functions................................................................................................................................................................303
11.2 SHAFT generator controller principles.................................................................................................................................................................. 304
11.2.1 Nominal settings..........................................................................................................................................................................................................304
11.3 Shaft generator breaker.................................................................................................................................................................................................. 305
11.3.1 Introduction.................................................................................................................................................................................................................... 305
11.3.2 Shaft generator breaker close flowchart........................................................................................................................................................... 305
11.3.3 Shaft generator breaker open flowchart............................................................................................................................................................306
11.3.4 Shaft generator breaker blackout close flowchart.........................................................................................................................................307
11.3.5 Shaft generator breaker trip flowchart................................................................................................................................................................310
11.4 Other SHAFT generator controller functions...................................................................................................................................................... 310
11.4.1 Shaft generator regulation...................................................................................................................................................................................... 310
11.4.2 Counters......................................................................................................................................................................................................................... 312
11.4.3 Trip AVR..........................................................................................................................................................................................................................313
11.5 SHAFT generator controller protections............................................................................................................................................................... 313
11.5.1 SHAFT generator controller alarms.................................................................................................................................................................... 313
11.5.2 Alarm actions................................................................................................................................................................................................................ 314
11.5.3 Inhibits............................................................................................................................................................................................................................. 314
11.5.4 Breaker alarms.............................................................................................................................................................................................................315
11.5.5 AC alarms...................................................................................................................................................................................................................... 315
12. SHORE connection controller

12.1 About the SHORE connection controller.............................................................................................................................................................. 318
12.1.1 SHORE connection controller functions........................................................................................................................................................... 318
12.2 SHORE connection controller principles.............................................................................................................................................................. 319
12.2.1 Nominal settings......................................................................................................................................................................................................... 319

12.3 Shore connection breaker............................................................................................................................................................................................. 319
12.3.1 Introduction................................................................................................................................................................................................................... 319
12.3.2 Shore connection breaker close flowchart.......................................................................................................................................................320
12.3.3 Shore connection breaker open flowchart....................................................................................................................................................... 321
12.3.4 Shore connection breaker blackout close flowchart.................................................................................................................................... 322
12.3.5 Shore connection breaker trip flowchart........................................................................................................................................................... 325
12.4 Other SHORE connection controller functions................................................................................................................................................. 325
12.4.1 Counters......................................................................................................................................................................................................................... 325
12.5 SHORE connection controller protections.......................................................................................................................................................... 327
12.5.1 SHORE connection controller alarms................................................................................................................................................................ 327
12.5.2 Alarm actions................................................................................................................................................................................................................327
12.5.3 Inhibits............................................................................................................................................................................................................................. 327
12.5.4 Breaker alarms............................................................................................................................................................................................................ 328
12.5.5 AC alarms...................................................................................................................................................................................................................... 328
13. BUS TIE breaker controller

13.1 About the BUS TIE breaker controller.................................................................................................................................................................... 331
13.1.1 BUS TIE breaker controller functions.................................................................................................................................................................331
13.2 BUS TIE breaker controller principles.................................................................................................................................................................... 331
13.2.1 Configure a BUS TIE breaker controller........................................................................................................................................................... 331
13.2.2 Nominal settings......................................................................................................................................................................................................... 332
13.3 BUS TIE breaker controller sequences.................................................................................................................................................................. 333
13.3.1 Bus tie breaker close flowchart.............................................................................................................................................................................333
13.3.2 Bus tie breaker open flowchart............................................................................................................................................................................. 334
13.3.3 Bus tie breaker blackout close flowchart.......................................................................................................................................................... 336
13.3.4 Bus tie breaker trip flowchart................................................................................................................................................................................. 338
13.4 Other BUS TIE breaker controller functions....................................................................................................................................................... 338
13.4.1 Counters......................................................................................................................................................................................................................... 338
13.5 BUS TIE breaker controller alarms and protections....................................................................................................................................... 340
13.5.1 BUS TIE breaker controller protections............................................................................................................................................................ 340
13.5.2 Alarm actions................................................................................................................................................................................................................340
13.5.3 Inhibits............................................................................................................................................................................................................................. 340
13.5.4 Breaker alarms............................................................................................................................................................................................................ 340
13.5.5 AC alarms...................................................................................................................................................................................................................... 341
14. Modbus
14.1 Modbus in the controller................................................................................................................................................................................................ 343
14.1.1 How it works................................................................................................................................................................................................................. 343
14.1.2 Warnings........................................................................................................................................................................................................................ 343
14.2 Modbus implementation in the controller.............................................................................................................................................................343
14.2.1 Modbus TCP protocol............................................................................................................................................................................................... 343
14.2.2 Modbus communication port................................................................................................................................................................................. 344
14.2.3 Controller identifier..................................................................................................................................................................................................... 344
14.2.4 Data handling............................................................................................................................................................................................................... 344
14.3 Modbus tables......................................................................................................................................................................................................................345
14.3.1 Download Modbus tables........................................................................................................................................................................................345
14.3.2 About the Modbus tables........................................................................................................................................................................................ 345
14.4 Specific Modbus function groups............................................................................................................................................................................. 346
14.4.1 CustomLogic: Modbus signal................................................................................................................................................................................ 346

14.4.2 Breaker priority: Buffered value............................................................................................................................................................................ 346
14.5 Setting up Modbus............................................................................................................................................................................................................ 349
14.5.1 Setting up Modbus TCP/IP communication.................................................................................................................................................... 349
14.6 Modbus alarm.......................................................................................................................................................................................................................349
14.6.1 Modbus communication timeout.......................................................................................................................................................................... 349
15. Hardware characteristics

15.1 General characteristics................................................................................................................................................................................................... 350
15.1.1 Frame ground characteristics................................................................................................................................................................................350
15.1.2 Power supply characteristics................................................................................................................................................................................. 350
15.1.3 Relay output characteristics and configuration.............................................................................................................................................. 352
15.1.4 Digital input characteristics and configuration................................................................................................................................................ 355
15.1.5 Analogue input characteristics and configuration......................................................................................................................................... 356
15.1.6 Analogue output characteristics and configuration...................................................................................................................................... 358
15.2 Power supply module PSM3.1.................................................................................................................................................................................... 359
15.2.1 Power supply voltage as an analogue output.................................................................................................................................................359
15.2.2 Relay output characteristics................................................................................................................................................................................... 359
15.2.3 Internal communication............................................................................................................................................................................................ 360
15.3 Power supply module PSM3.2.................................................................................................................................................................................... 360
15.3.1 Power supply voltage as an analogue output.................................................................................................................................................360
15.3.3 Internal communication............................................................................................................................................................................................ 361
15.4 Alternating current module ACM3.1........................................................................................................................................................................ 361
15.4.1 Voltage measurement characteristics................................................................................................................................................................361
15.4.2 Current measurement characteristics................................................................................................................................................................ 362
15.5 Differential current module ACM3.2.........................................................................................................................................................................362
15.5.1 Current measurement characteristics................................................................................................................................................................ 362
15.6 Input/output module IOM3.1......................................................................................................................................................................................... 362
15.6.1 Changeover relay output characteristics.......................................................................................................................................................... 362
15.6.2 Digital input characteristics.....................................................................................................................................................................................362
15.7.2 Analogue multifunctional output characteristics............................................................................................................................................ 363
15.7.4 Analogue multifunctional input characteristics............................................................................................................................................... 363
15.8.1 Analogue multifunctional input characteristics............................................................................................................................................... 364
15.9.1 Digital output characteristics and configuration............................................................................................................................................. 364
15.10 Engine interface module EIM3.1.............................................................................................................................................................................. 366
15.10.1 Power supply characteristics.............................................................................................................................................................................. 366
15.10.2 Auxiliary power supply voltage as an analogue output............................................................................................................................366
15.10.3 Magnetic pickup unit (MPU) input characteristics...................................................................................................................................... 367
15.10.4 W input characteristics.......................................................................................................................................................................................... 367
15.10.5 Analogue input (AI) characteristics...................................................................................................................................................................368
15.10.6 Relay output with wire break detection characteristics............................................................................................................................ 369
15.10.7 EIM3.1 standalone.................................................................................................................................................................................................. 369

15.11 Governor and AVR module GAM3.1...................................................................................................................................................................... 375
15.11.1 Analogue output (AO) characteristics.............................................................................................................................................................. 375
15.11.2 Pulse width modulation (PWM) output characteristics............................................................................................................................. 375
15.11.3 Analogue input (AI) characteristics................................................................................................................................................................... 376
15.12 Governor and AVR module GAM3.2...................................................................................................................................................................... 377
15.12.1 Analogue output (AO) characteristics............................................................................................................................................................. 377
15.12.2 Pulse width modulation (PWM) output characteristics............................................................................................................................. 377
15.12.3 Relay output characteristics................................................................................................................................................................................ 378
15.13 Processor and communication module PCM3.1............................................................................................................................................ 378
15.13.1 PCM3.1 clock battery............................................................................................................................................................................................. 378
15.14 Display unit DU 300........................................................................................................................................................................................................ 379
15.14.1 Relay output characteristics................................................................................................................................................................................ 379
15.15 DEIF Ethernet network.................................................................................................................................................................................................. 379
15.15.1 About communication.............................................................................................................................................................................................379
15.15.2 DEIF Ethernet network characteristics........................................................................................................................................................... 380
15.15.3 Controller rack communication settings......................................................................................................................................................... 380
15.15.4 Controller rack Ethernet port settings..............................................................................................................................................................381
15.15.5 Display communication settings........................................................................................................................................................................ 381
15.15.6 Restrictions................................................................................................................................................................................................................. 381
15.16 DEIF internal communication................................................................................................................................................................................... 382
15.16.1 Internal communication......................................................................................................................................................................................... 382
16. Glossary
16.1 Terms and abbreviations................................................................................................................................................................................................384
16.2 Units.......................................................................................................................................................................................................................................... 390
16.3 Symbols...................................................................................................................................................................................................................................391
16.3.1 Mathematical symbols.............................................................................................................................................................................................. 391
16.3.2 Drawing symbols........................................................................................................................................................................................................ 392
16.3.3 Flowchart symbols..................................................................................................................................................................................................... 394
16.3.4 Module faceplate symbols...................................................................................................................................................................................... 395

1. About the Designer's handbook
1.1 Intended users of the Designer's handbook

The Designer's handbook is intended for the designer of the system where the controllers are installed. It can also be used during
commissioning to check the design drawings and the controller parameters. Operators may find the Designer's handbook useful for
understanding the system and for troubleshooting.
1.2 Symbols and conventions

Functions
The Designer's handbook descriptions are based on functions. Each function description includes the associated input and output
functions, and parameters.
Function or parameter path notation
A function or parameter path is stated in this document as follows:
Generator > Nominal settings > Nominal settings 1 > Voltage (V)
The above path is for the Voltage (V) parameter under Nominal settings 1 for the Generator.
Inputs and outputs
Most of the controller inputs and outputs are configurable. You can assign functions to inputs or outputs with either the display or
PICUS. These functions are assigned to a hardware module and set of corresponding terminals. Functions can also be assigned to
an ECU, if the ECU is configured in Fieldbus.
To configure a function:
1. Open the page: Configure > Input/output.

2. Select the hardware module (or ECU) to use.
3. Select the set of terminals to configure.
4. Select Function to assign the function to the terminals. *
NOTE * Only functions applicable for the type of terminal are listed.
Parameters
You can select and change the parameters with either the display or PICUS.
To configure a parameter:
1. Open the page: Configure > Parameters.

2. Search or browse the parameter list.
3. Select the parameter to configure. *
NOTE * Some parameters are only visible after a corresponding input or output function has been configured.

Multi-function parameters and I/Os
Some parameters and inputs or outputs can be used by more than one function. Search the whole Designer's handbook to see the
impact of a change.
Parameter used by more than one function example
For a GENSET controller:
Generator > Nominal settings > Nominal settings 1 > Voltage (V)
This parameter is for the genset Nominal voltage for the first set of nominal settings. The Nominal voltage is the basis for
all of the voltage alarms.
General names
Square brackets [ ] are used to create general names. General names are used to avoid repeating the same function description.
Use of square brackets examples
[Source] represents the Generator for a GENSET controller.
[Hardware module] represents the relevant controller hardware module.
[Breaker] represents the Generator breaker for a GENSET controller.
Numbers
The hash symbol # is used when there are several numbered possibilities.
Use of hash # example
Controller ID #: # represents 1 to 64. That is, the system can have up to 32 controllers, each with their own unique
Controller ID between 1 and 64.
Symbols for hazard statements
DANGER!
This shows dangerous situations.

If the guidelines are not followed, these situations will result in death, serious personal injury, and equipment damage or
destruction.
WARNING
This shows potentially dangerous situations.

If the guidelines are not followed, these situations could result in death, serious personal injury, and equipment damage
or destruction.

CAUTION
This shows low level risk situation.

If the guidelines are not followed, these situations could result in minor or moderate injury.
NOTICE
This shows an important notice

Make sure to read this information.
Symbols for general notes
NOTE This shows general information.
More information
This shows where you can find more information.
Example
This shows an example.
How to ...
This shows a link to a video for help and guidance.
1.3 Software versions

The information in this document relates to software versions:
Software Details Version
PCM APPL Controller application 1.0.21.x
DU APPL Display unit application 1.0.20.x
PICUS PC software 1.0.19.x
1.4 Technical support

Technical documentation
Download the technical documentation from the DEIF website: https://www.deif.com/documentation/ppu-300/
Service and support

DEIF is committed to being available to our customers and partners 24 hours a day, seven days a week, to guarantee the highest
levels of service and support.
https://www.deif.com/support
Training
DEIF arranges training courses at DEIF offices worldwide.
https://www.deif.com/training

Additional service
DEIF offers service with design, commissioning, operating and optimisation.
https://www.deif.com/support/local-office
1.5 Warnings and safety

Safety during installation and operation
When you install and operate the equipment, you may have to work with dangerous currents and voltages. The installation must
only be carried out by authorised personnel who understand the risks involved in working with electrical equipment.
DANGER!
Hazardous live currents and voltages

Do not touch any terminals, especially the AC measurement inputs and the relay terminals, as this could lead to injury or
death.
Controller power supply
The controller must have a reliable power supply and a backup power supply. The switchboard design must ensure sufficient
protection of the system, if the controller power supply fails.
If the controller has no power supply, it is OFF and does not provide any protection. The controller cannot enforce any trips,
shutdowns or latches when it is off. The controller does not provide any control or load sharing. All the controller relays de-energise.
Connect the controller protective earth
DANGER!
Failure to ground
Failure to ground the controller (or extension rack) could lead to injury or death.
You must ground the controller (or extension rack) to a protective earth.
Switchboard control
In Switchboard control, the operator operates the equipment from the switchboard. When Switchboard control is activate:
• The controller trips the breaker and/or shuts down the engine, if an alarm situation arises that requires a trip and/or shutdown.
• The controller does not accept operator commands.
• The controller cannot and does not prevent manual operator actions.
The switchboard design must protect the system when the controller is in Switchboard control.
DANGER!
Manual override of alarm action

Do not use switchboard or manual control to override the alarm action of an active alarm.
An alarm may be active because it is latched, or because the alarm condition is still active. If the alarm action is
manually overridden, the latched alarm provides no protection.

Factory settings
The controller is delivered pre-programmed from the factory with a set of default settings. These settings are based on typical values
and may not be correct for your system. You must therefore check all parameters before using the controller.
PLC design and testing
The controllers require an operator, a PLC, and/or CustomLogic or CODESYS to control the system. The controllers do not do
system calculations or system power management. Each controller simply follows the commands that it receives. The controllers do
not evaluate whether the commands are appropriate for the system state.
CAUTION
Incorrect PLC commands

The PLC must be programmed correctly and thoroughly tested, to ensure safety, and avoid situations where the PLC
gives the controllers incorrect commands and set points.
The PLC is supplied by a third-party. DEIF is not responsible for the PLC design and testing.
System protection example
The class society may require limitation of the parallel time for a shaft generator and diesel genset. The controller does
NOT monitor whether the shaft generator and diesel genset are in parallel. The controller does NOT trip any breaker
because the maximum parallel time is exceeded.
Regulation set point example
The controller does not evaluate whether regulation set points are appropriate. The controller simply attempts to regulate
to achieve the set point. If the operating value exceeds an alarm set point, then the controller activates the alarm action.
Electrostatic discharge
Protect the equipment terminals from electrostatic discharge when not installed in a grounded rack. Electrostatic discharge can
damage the terminals.
Shelving and taking alarms out of service
DANGER!
Shelved and out of service alarms are completely disabled.

These alarms cannot be activated by the operating conditions, and provide NO protection. Shelving or taking out of
service also automatically acknowledges the alarm and resets the latch.
You can shelve and/or take selected alarms out of service. However, only qualified personnel should shelve and/or take alarms out
of service. This must be done carefully, and only as a temporary measure, for example, during commissioning.

Do not manually override active alarm actions
DANGER!
Manual override of latched alarm action

If the alarm action is manually overridden, a latched alarm does NOT provide any protection.
Do not override the alarm action of an active alarm. An alarm may be active because it is latched, or because the alarm
condition is still present.
Latched Over-current alarm example
The controller trips a breaker because of over-current. The operator then manually (that is, not using the controller) closes
the breaker while the Over-current alarm is still latched.
If another over-current situation arises, the controller does not trip the breaker again. The controller regards the original
Over-current latched alarm as still active, and it does not provide protection.
Do not use unsupported hardware modules
Only use the hardware modules that are listed in the Technical specifications. Unsupported hardware modules can make the
controller malfunction.
Data security
To minimise the risk of data security breaches we recommend:

• If possible, avoid to expose controllers and networks to public networks and the Internet.
• Use additional security layers like a VPN for remote access.
• Install a firewall.
• Restrict access to authorised persons.
1.6 Legal information

Third party equipment
DEIF takes no responsibility for the installation or operation of any third party equipment, including the genset.
Warranty
The rack may only be opened to remove, replace, and/or add a hardware module or the internal battery on PCM3.1. The procedure
in the Installation instructions must be followed. If the rack is opened for any other reason, and/or the procedure is not followed,
then the warranty is void.
If the display unit is opened, then the warranty is void.
Open source software
This product contains open source software licensed under, for example, the GNU General Public License (GNU GPL) and GNU
Lesser General Public License (GNU LGPL). The source code for this software can be obtained by contacting DEIF at
support@deif.com. DEIF reserves the right to charge for the cost of the service.

Trademarks
DEIF, power in control and the DEIF logo are trademarks of DEIF A/S.
Bonjour® is a registered trademark of Apple Inc. in the United States and other countries.
Adobe®, Acrobat®, and Reader®are either registered trademarks or trademarks of Adobe Systems Incorporated in the United
States and/or other countries.
CANopen® is a registered community trademark of CAN in Automation e.V. (CiA).
SAE J1939® is a registered trademark of SAE International®.
CODESYS® is a trademark of CODESYS GmbH.
EtherCAT®, EtherCAT P®, Safety over EtherCAT®, are trademarks or registered trademarks, licensed by Beckhoff Automation
GmbH, Germany.
Modbus® is a registered trademark of Schneider Automation Inc.
Windows® is a registered trademark of Microsoft Corporation in the United States and other countries.
All trademarks are the properties of their respective owners.
Copyright
© Copyright DEIF A/S. All rights reserved.
Disclaimer
DEIF A/S reserves the right to change any of the contents of this document without prior notice.
The English version of this document always contains the most recent and up-to-date information about the product. DEIF does not
take responsibility for the accuracy of translations, and translations might not be updated at the same time as the English document.
If there is a discrepancy, the English version prevails.

2. System principles
2.1 About the controllers

2.1.1 About
The PPU 300 Paralleling and Protection Unit is a highly configurable controller designed for marine use. The controller contains the
functions required to protect and control a generator or inverter and its breaker (specifically, a diesel generator, an inverter with
power source, a shaft generator, a shore connection, or a bus tie breaker). You can connect up to 32 controllers to create one
system, with load sharing sections.
The PPU 300 can be ordered with a PLC environment (CODESYS) as an add-on option. CODESYS can be used to extend the
controller functionality and/or create custom CODESYS projects for the controller.
Typically, CODESYS or an operator will send commands to the PPU 300 to close or open the breaker. CODESYS or an operator
can also send commands to start or stop the generator or inverter, change the regulation mode, and change the regulation set
points.
You can also use an alternative PLC to send commands to the PPU 300.
AC measurements can be configured with average filters for use on noisy or oscillating systems. This is only for the displayed
values. All calculations and protections continue to use the actual values. *
The controller display unit can have push-buttons for the operator to change the controller mode, close and open the breaker, and
start and stop a generator or inverter. The colour graphic screen shows status and info messages. Visual synchronisation screen
shows the synchronisation state and values. The screen also allows access to live data, and alarm management. With the right
authorisation, the operator can also check and/or change the input/output and parameter configuration. The light indicators of the
display unit show the system status.
Each controller includes processors and high-speed internal communication. This provides fast protection functions.
The controller design is modular, and hardware modules may be replaced or added in the field.
PICUS is a proprietary, free PC software interface to the controller. The designer can use PICUS to create a flexible application
diagram for the system, and configure the inputs, outputs, and parameters for all the controllers in the system. PICUS also offers
system emulation, supervision, management of permissions, backups, trending, and firmware updates.
The network communication can be configured for IP address settings and for type of Ethernet port and connection node.
Engine communication with CAN bus J1939 can be configured to communicate with an ECU.
More information
See the Engine interface communication manual for supported engines, protocols, and functions.
NOTE * Measurement averaging is not enabled in the default configuration. It may not be allowed for some Maritime classification
approval societies.
More information
You can find additional technical documentation at www.deif.com/documentation/ppu-300/
2.1.2 Controller types
The GENSET controller type controls both a breaker and the genset engine. The HYBRID controller type controls both the inverter
breaker and the inverter. The SHAFT generator, SHORE connection, and BUS TIE breaker controller types each control one
breaker.

The hardware listed is for the recommended configuration. Additional modules may be ordered and mounted as required. A
customised PPU 300 controller may also be ordered. For example, you may need additional inputs and outputs.
The general PPU 300 controller features apply to all controller types. The GENSET controller includes a number of additional
features, due to engine control and regulation.
Type Application Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7
Control and protection of

GENSET PSM3.1 ACM3.1 IOM3.1 EIM3.1 GAM3.1 IOM3.1 PCM3.1
a diesel generator
Control and protection of

HYBRID an inverter and power PSM3.1 ACM3.1 IOM3.1 EIM3.1 GAM3.1 IOM3.1 PCM3.1
source.
SHAFT Control and protection for Blind module Blind module Blind module
PSM3.1 ACM3.1 IOM3.1 PCM3.1
generator a shaft generator
SHORE Control and protection for Blind module Blind module Blind module
connection a shore connection
BUS TIE Control and protection for Blind module Blind module Blind module
breaker a bus tie breaker
2.1.3 About the display unit DU 300
The controller can run with or without a display, but we recommend to use the DU 300 display unit. Alternatively, you can use a
touch display from the DEIF AGI 400 series.
The display unit is the operator's interface to the controller. The 5-inch colour graphic display shows real-time operating information,
and it supports all languages with UTF-8 fonts.
The power supply terminals include circuit protection against load dump transients and JEM177 surge transients (rugged design).
1. Top part
Switchboard control P1
Home 12:00
• Same for all DU 300 display units
2. Bottom strip with control
Configure Tools Info
• Different for each controller type (shown
1
for GENSET controller)
Log on Alarm Log Live data
2.1.4 Display unit DU 300 options
The bottom strip of the front of the display can include LEDs that show the equipment and controller status, as well as push-buttons
for operator actions.

Bottom strip with no function or LEDs
Functions
• No LEDs for inverter, engine, generator, breaker and busbar status

Blank display
• No display push-buttons
• Remote control only

Control mode ◦ Remote commands start sequences (from digital input, PICUS, Modbus, and/or
CustomLogic or CODESYS)
Bottom strip with application LEDs

Figure 2.1 Example of display unit with application LEDs
Functions
• LEDs for Source and Busbar V&Hz

Display with application
• LED for breaker status
LEDs
• No display push-buttons
• Remote control only

Control mode ◦ Remote commands start sequences (from digital input, PICUS, Modbus, and/or
Display with breaker push-buttons

Normally used with BUS TIE breaker (BTB) controllers.
Figure 2.2 Example of display with breaker push-buttons
Functions
• LEDs for Source and Busbar V&Hz

Display with breaker push- • LED for breaker status
buttons • Display push-buttons
◦ Change control mode (local/remote)

Functions
◦ Sequences for breaker open and close
• Remote control
◦ Remote commands start sequences (from digital input, PICUS, Modbus, and/or
Control modes ◦ Display push-buttons for sequences are ignored
• Local control
◦ Display push-buttons start sequences
◦ Remote commands for sequences are ignored
Display for GENSET controller

This folio is only for the GENSET controller.
Figure 2.3 Example of display for GENSET with full functionality
Functions
• LEDs for generator and busbar V&Hz

• LEDs for engine and breaker status
Display with full • Display push-buttons
functionality ◦ Change control mode (local/remote)
◦ Sequences for genset start and stop
• Remote control
• Local control
Display for HYBRID controller

These folios are only for the HYBRID controller.

Figure 2.4 Example of display for HYBRID with full functionality
Functions
• LEDs for inverter and busbar V&Hz

• LEDs for battery storage and breaker status
Display with full • Display push-buttons
functionality ◦ Change control mode (local/remote)
◦ Sequences for inverter start and stop
• Remote control
• Local control
2.2 Application as a system

2.2.1 How it works
A number of controllers are used together to create a controller system. Each controller has configurable hardware, which in turn
has configurable inputs and outputs. The controller gets information from the measurements, the inputs, and the DEIF Ethernet
network. The controller sends out information using the outputs, and the DEIF Ethernet network.

Busbar
Switchboard 2 Display
Other 3
PLC 2 9
3 9
10
1
8 Controller
2
3 Controller
1
11
1
5 Extension
rack
6 10
AVR
2 AGI
ECU
3 Computer
G
7 GOV 4 Other
Point Type Description Uses
Protection, running detection, control,

The controller measures the AC voltage and current
1 AC measurements synchronisation, power management, and
from the genset and the voltage on the busbar.
logging.
Analogue and digital measurement devices on the

A wide variety of purposes, including
genset can be connected to the controller. The
Analogue and digital protection, user inputs, various levels of
2 controller can also receive analogue and digital
inputs alarms, power management, running
inputs from breakers, CODESYS, a PLC, the
detection, and logging.
switchboard, and other sources.
The controller can send analogue and digital

A wide variety of purposes, including
Analogue and digital outputs to the genset, breakers, CODESYS, a PLC,
3 control, status and alarm indicators, and as
outputs the switchboard (for example, for lights and meters),
input to CODESYS or a PLC.
and other equipment.
Analogue or digital The controller can control the genset governor Regulate the genset frequency, and/or
4 outputs for governor (GOV) using digital outputs (relay control), or active power (depending on the system
control analogue outputs. configuration).
The controller can control the genset automatic Regulate the genset voltage and/or reactive
Analogue or digital
5 voltage regulator (AVR) using digital outputs (relay power (depending on the system
outputs for AVR control
control), or analogue outputs. configuration).
Read the engine data, and control the

The controller sends control information to and/or
CAN bus genset frequency and power, protection,
6 fetches information from the engine control unit
communication various levels of alarms, running detection,
(ECU) using CAN bus communication.
and logging.
ECU controls GOV

7
(future use)
The controllers produce a voltage proportional to the

percentage of their nominal power for the load Equal load sharing (active and/or reactive)
8 Analogue load sharing
sharing line, and then use the voltage on the load between 2 or more gensets.
sharing line to adjust their genset set points.
The DEIF equipment communicates with other DEIF Send inputs from the display to the
9 DEIF network
equipment using this network. controller, and information from the

Point Type Description Uses
controller to the display. Send information

from one controller to another.
Allows external devices to communicate with the A wide variety of purposes, including
10 Modbus TCP/IP controller using the Modbus TCP/IP communication monitoring, off site control, and alarm
protocol. handling.
Allows DEIF controllers to communicate with DEIF Extend controller functionality by adding
11 Internal communication extension racks. The communication ports are additional inputs and outputs to one or
located on the power supply modules (PSM). more extension units.
Configurable hardware
After you assign a function to an input or output, you can assign parameters to that function. Each controller type has a default
configuration.
Most of the controller inputs and outputs can be assigned any function. Functions are not restricted to specific hardware modules.
For example, governor and AVR control functions can use any inputs and outputs, and do not have to use the inputs and outputs on
the Governor and AVR modules (GAM3.1 and/or GAM3.2).
Variety of input and output types

The controllers allow the same function to use a number of alternative types of inputs and/or outputs. This makes the controllers
versatile and compatible with a wide range of equipment and systems.
For example, a breaker close can be initiated by an operator using the display unit, PICUS, a digital input, CustomLogic, or an
external system using a Modbus or CODESYS command.
Similarly, the generator excitation (AVR) can be controlled using an analogue output, or digital outputs.
The DEIF network allows the controller to use information from other controllers.
Each controller's display only displays the operating information for the paired controller.
2.2.2 Application single-line diagram
The system (application) is defined by the Application single-line diagram created with PICUS.
The diagram defines for the system:

• How many controllers
• What type of controllers
• Non-essential loads (NEL)
Additional breaker settings, measurements, and feedbacks can be configured.
The single-line diagram is created in PICUS and must be broadcast to all connected controllers in the same system. If different
single-line diagrams are detected in the system, the controller activates an alarm.
Example PPU application

SC 1 : Shore connection controller
HY 4 : HYBRID controller
SGB 1 : SHAFT generator controller
GB 4 : GENSET controller
NEL 1 : Non-essential load 1
NEL 2 : Non-essential load 2
More information
See the PICUS manual for how to create and broadcast the Application single-line diagram.
2.2.3 Change controller type
You can change the type of the controller from the application's single-line diagram. This feature requires the necessary permission
in order to access it.
Restrictions on changing type

Changing the controller type is restricted by the initial type of the controller.
• GENSET or HYBRID controllers can be changed to any other PPU 300 controller type.
• SHAFT generator, SHORE connection, or BUS TIE breaker controllers can only be changed to one of these three types.
You can only change the controller type if it is safe for commissioning:
1. The engine must be stopped (not applicable to BUS TIE breaker controller).
2. The breaker must be open.
3. The controller must be in switchboard control.
or
1. The controller is in emulation mode.

Changing the controller type resets the default I/O configuration. The I/O configuration must checked and reconfigured as necessary
after changing the controller type. It is recommended to take a backup of your settings before changing the controller type.
Change controller types
NOTICE
Configure controller IDs before application

A new controller has a Controller ID factory setting of 0 by default. It MUST be configured to the required ID number,
otherwise the alarm Controller ID not configured becomes active.
Configure the Controller IDs on all connected controllers in the system BEFORE creating the application single-line
diagram in PICUS.
Create the controller types as follows:

1. Use each display or PICUS to configure all the Controller IDs.
a. Use Tools > Communication to configure the Controller ID for each controller.
b. Give each controller a unique Controller ID as part of the system design.
2. Create a single-line diagram for the system in PICUS.
a. Use Connect in PICUS to connect and log on to all the controllers in the system.
b. Use Application, drag icons for the controllers in the system onto the canvas.
3. Edit each controller and assign the correct Controller ID.
4. Broadcast the single-line diagram to all the controllers.
5. System response: For each Controller ID, if the controller type on the single-line diagram does not match the controller, then the
controller is changed to the new controller type.
• The controller type change resets the controller. The default inputs, outputs, and parameters for the controller type are
configured.
NOTICE
Configuration reset
If a Controller ID is assigned a new controller type on the single-line diagram, then all of the controller's existing
configuration is deleted, this also includes the log. The IP address configuration and permissions (both users and
groups) are not deleted.
It is recommended to take a backup of your controller before changing controller type if you require the settings.
More information
See Application in the PICUS manual for how to create the application single-line diagram.
2.2.4 Maximum number of controllers
There can be up to a total of 32 controllers per DEIF Ethernet network ring. That is, you can assign up to 32 unique Controller ID
numbers out of a possible range of 64.
A system can consist of PPU 300 controllers in the same DEIF Ethernet network. It is also possible to include other ML 300
controllers (using Modbus communication) in the system.
Types Possible Notes
GENSET controller 1 to 32 There must be at least one GENSET controller.
HYBRID controller 0 to 32
SHAFT generator controller 0 to 31

Types Possible Notes
SHORE connection controller 0 to 31
BUS TIE breaker controller 0 to 31
2.2.5 Control and command structure
The controllers communicate with each other using the Ethernet connections between controllers. This is a virtual network referred
to as the DEIF Ethernet network. The Ethernet connections can also be used by other systems, such as SCADA or alarm systems.
Commands to start sequences

The controller can receive external commands to start controller sequences. For example, a controller in remote control can respond
to an external command to close the breaker. If the controller is in local control, then the controller displays an information message
and ignores the external command.
An external command can only start a sequence if all the conditions are met, and the controller mode allows the external command
to start the sequence.
The controller provides several different ways in which to start the same sequence.
Commands to start sequences

Default
Command Example
mode
Using Modbus communication, an A PLC has a Modbus connection to the required controller. The PLC writes 1
operator, a SCADA system, a (True) to Modbus address 1000 in the discrete output coil using the Modbus
controller with CODESYS installed, function code 05 or 15.
Remote
or a PLC sets a Modbus address in
the function group Command to 1
The controller gets the command, and starts the sequence to start the genset.
(True).
A button on the switchboard is wired to a digital input on IOM3.1 in Slot 6,

terminals 22, 23 of the controller rack. These terminals are assigned the
Engine > Command > Start engine function.
A digital input, which is assigned an
external command function, is Remote
The operator presses the button on the switchboard, to activate the digital input.
activated.
The controller detects that the digital input is activated, and starts the sequence
to start the genset.
The operator presses the controller Start button on the Supervision page in
The operator selects a virtual PICUS.
display push-button on the Remote
Supervision page in PICUS.
The controller gets the command over the DEIF network, and starts the
sequence to start the genset.
A function is programmed in CustomLogic. The CustomLogic rung has the

conditions that need to be met. There is a Normally open coil with the function
Engine > Command > Start engine at the end of the rung.
CustomLogic activates an external
Remote
command function. The conditions are met, and CustomLogic activates the function.
The controller detects that the function is activated, and starts the sequence to
start the genset.
The operator presses a push-button The operator presses the Start button on the display unit.
Local
on the display unit.

Default
Command Example
mode
The controller gets the command over the DEIF Ethernet network, and starts
the sequence to start the genset.
The controller ignores the command and displays an information message if the controller cannot execute the command. For
example, if a controller is in local control, it ignores a remote Start engine command. The controller displays the information
message Not under remote control.
2.2.6 Priority of input sources
Each controller can receive inputs from a number of sources. The rules for when a source can be used, as well as how the controller
handles conflicting inputs, are described below.
Digital input functions

Digital input functions can be activated by wiring connected to hardware, Modbus and/or CustomLogic coils or CODESYS
commands.
Rules for digital input functions:

1. If a digital input function is assigned to hardware, you cannot assign that function to a CustomLogic coil (that is, a normally open
or normally closed coil).
2. If a digital input function is assigned to a CustomLogic coil, you cannot assign that function to hardware.
• If you try to assign a digital input that is already assigned to a CustomLogic coil to hardware, it may seem possible. However,
if you refresh the hardware view, you will see that the input has not been assigned.
3. If a digital input function is assigned to CODESYS, the function will not be available in the hardware. If the function has already
been assigned to the hardware, an alarm will occur.
4. For pulse functions:
a. If there is a command from Modbus, then the controller can activate the function. This is true even if the function is assigned
to hardware.
b. The controller always responds to the most recent input, without considering the source.
5. For continuous functions:
a. If the function is assigned to hardware: If Modbus sends a command, then the command is not allowed and has no effect.
b. If the function is not assigned to hardware: If Modbus and CustomLogic send conflicting signals, then the controller uses the
CustomLogic signal.
Commands from display unit push-buttons have the same priority as wiring connected to hardware.
Analogue input functions

Analogue input functions can receive inputs from wiring connected to hardware, Modbus, and/or CustomLogic coils or CODESYS.
Rules for analogue input functions:
1. If the analogue input function is assigned to hardware, Modbus can only read the input value. Modbus and CustomLogic or
CODESYS cannot modify the input value.
2. If the analogue input function is not assigned to hardware, Modbus and CustomLogic or CODESYS can modify the input value.
3. If Modbus and CustomLogic or CODESYS send conflicting signals, then the controller uses the CustomLogic or CODESYS
signal.
2.3 Control and modes

2.3.1 About the control modes
The controllers use control modes to distinguish between operator and external control.

The following control modes are possible:
• LOCAL control (default)
• REMOTE control
• Switchboard control
Controllers always start in LOCAL control.
2.3.2 Switchboard control
In Switchboard control, the operator controls and operates the equipment from the switchboard. The operator can manually regulate
the frequency and voltage using digital inputs (if configured) or Modbus.
In Switchboard control, the controller does not accept any commands from the display or other external sources (for example, PLC
and Modbus) to open or close the breaker. The GENSET controller does not accept any commands to start or stop the engine.
However, the controller alarms can still trip the breaker, and the GENSET controller alarms can shut down the engine.
Manual slope
These parameters are active when the controller is in switchboard control, and the operator manually controls the regulator. They
are only visible if a governor or AVR output is configured.
[Regulator] is either GOV or AVR.
Regulators > [Regulator] analogue configuration > Manual slope

Parameter Range Default Notes
The controller increases or decreases the analogue output by this

amount when the digital input is activated.
Manual GOV 1 %/s of genset
0 to 200 %/s
slope nominal power
For relay outputs, depending on the relay output settings, the effect
might not be linear.
The controller increases or decreases the analogue output by this

10 %/s of genset amount when the digital input is activated.
Manual AVR
0 to 200 %/s nominal reactive
slope
power For relay outputs, depending on the relay output settings, the effect
might not be linear.
Alarms in switchboard control

In Switchboard control with a switchboard design that provides for this, the operator can perform a manual synchronisation (for
example, by using switchboard buttons for relay speed control of the genset) and then close the breaker. This command does not go
through the controller, and the switchboard design must therefore ensure that the breaker synchronisation is always checked before
closing.
If an action is performed from the switchboard that activates a controller alarm while the controller is under Switchboard control, the
controller will execute the associated alarm action. For example, if an alarm with an alarm action Trip generator breaker and
shutdown engine is activated while the controller is under Switchboard control, then the controller trips the breaker and shuts down
the engine.
Alarm actions under switchboard control example
For a GENSET controller, you can create a low oil pressure alarm (based on an analogue input from a sensor) that has the
action Trip generator breaker and shutdown engine. If there is a low oil pressure, then this alarm shuts down the engine
when the controller is under Switchboard control.
You can create a low oil pressure alarm with the Warning alarm action. If there is a low oil pressure, then this alarm
activates and the warning appears even if the controller is in Switchboard control.

The non-essential load (NEL) trips are active in Switchboard control. If a condition is present that activates a non-essential load trip
alarm, the non-essential loads are disconnected.
Mode after switchboard control

The controller continues with the same mode (that is, local or remote) that it had during switchboard control. You cannot change the
controller mode during switchboard control.
2.3.3 Local control (default)
By default, the controllers run in local control. While in local control, the operator can use the display push-buttons for breaker open
and close (as well as engine start and stop for a GENSET controller).
Inputs and outputs

Function I/O Type Details
If the controller is in remote control, the controller is placed in local

Local > Mode > Local
Digital input Pulse control when this input is activated. This input has the same effect as
control
pressing the local push-button on the display.
Local > Mode > Under
Digital output Continuous Activated if the controller is in local control.
local control
2.3.4 Remote control
While in remote control, the display ignores the push-buttons for breaker open and close (as well as engine start and stop for a
GENSET controller).
Inputs and outputs

If the controller is in local control, the controller is placed in remote

Local > Mode > Remote
Digital input Pulse control when this input is activated. This input has the same effect as
control
pressing the remote push-button on the display.
Local > Mode > Under
Digital output Continuous Activated if the controller is in remote control.
remote control
2.3.5 Command sources
You can prohibit certain command sources from use in the system. For example, you could restrict the display function for start/stop
of the engine. Command sources can be configured as parameter settings or dynamically with CustomLogic or Modbus.
You can configure different restrictions for when in either LOCAL or REMOTE mode.
Parameters
You can use parameters to enable or disable the display command sources.
Local > Command sources > Active [mode] sources *

Parameter Range Symbol Default Notes
Not enabled,
PICUS commands - Enabled Allow or prohibit PICUS commands to be used.
Enabled
Not enabled,
Modbus commands - Enabled Allow or prohibit Modbus commands to be used.
Enabled
Not enabled,
I/O commands - Enabled Allow or prohibit I/O commands to be used.
Enabled

Parameter Range Symbol Default Notes
CustomLogic Not enabled,
- Enabled Allow or prohibit CustomLogic commands to be used.
commands Enabled
Not enabled, Allow or prohibit CODESYS commands to be used,

CODESYS commands ** - Enabled
Enabled only if CODESYS is installed on the controller.
Allow or prohibit the operator to use the display to

Remote/Local or Enabled
change to LOCAL or REMOTE mode.
Mute alarm Enabled Allow or prohibit the operator to mute alarms.

Display commands
Allow or prohibit the operator to start or stop the
Start/stop engine or Not enabled
engine or power source.
Allow or prohibit the operator to open or close the

Open/close breaker or Not enabled
breaker.
NOTE * Where [mode] is either LOCAL or REMOTE.

NOTE ** Only shown if CODESYS is installed and active on the controller. CustomLogic is not enabled if CODESYS is installed.
Dynamic control
You can use a CustomLogic function to dynamically enable or not enable the command source parameter by setting the value. The
value is represented as a bits value.
Example CustomLogic project
In this example, a GENSET controller has a digital input is associated with an OPERATE block for the function Display
commands. The value set in the OPERATE block relates to value for the command source.
When the digital input is not active the OPERATE value is set to 0. No push-buttons can be used.
When the digital input is active the OPERATE value is set to 31. All push-buttons can be used.
Parameters > Local > Command sources > Active [source] sources *
To enable these commands set the OPERATE value to 1.
To not enable these commands set the OPERATE value to 0.
Parameter OPERATE value Notes
0 = Not enabled
PICUS commands Allow or prohibit PICUS commands.
1 = Enabled
0 = Not enabled
Modbus commands Allow or prohibit Modbus commands.
1 = Enabled
0 = Not enabled
I/O commands Allow or prohibit I/O commands to be used.
1 = Enabled
0 = Not enabled
CustomLogic commands Allow or prohibit CustomLogic commands to be used.
1 = Enabled
0 = Not enabled Allow or prohibit CODESYS commands to be used, only if CODESYS is installed
CODESYS commands
1 = Enabled on the controller.

NOTE * Where [source] is either REMOTE or LOCAL.
Display push-button commands

The display push-buttons commands are controlled by the bit value, which depends on the type of controller.
GENSET or HYBRID controllers

Command Bit OPERATE value
REMOTE/LOCAL 0 1
Mute alarm 1 2
Start/stop engine 2 4
Open/close breaker 3 8
BUS TIE breaker, SHAFT generator, or SHORE connection controllers

REMOTE/LOCAL 0 1
Mute alarm 1 2
Example 1
In this example, we enable only the Start/stop engine, and Open/close breaker push-buttons on a GENSET controller.
Start/stop engine 2 4
Bit 2 + Bit 3 = 4 + 8 = OPERATE value 12
2.3.6 Controller not powered
A controller is not powered if it loses power, for example, because the power supply is disconnected. When a controller has no
power, none of its protections and functions are active.
A not powered controller does not communicate with the rest of the system, and is invisible to the rest of the system.
The following alarms activate when a controller detects that one of the system's controllers is not powered:
• Missing controller ID #
Effect of the not powered controller hardware

DEIF Ethernet network links through the not powered controller are broken. If a redundant DEIF Ethernet network link is not
available, the controllers on either side of the not powered controller cannot communicate with each other. If a redundant DEIF

Ethernet network link is available, then the controllers on either side of the not powered controller communicate through the
redundant link.
All relays return to their de-energised hardware condition. For example, on IOM3.1 there is a changeover switch on terminals 1 to 3.
If the controller loses power, then there will be an open circuit between terminals 1 and 2 (the normally open terminals of the
changeover switch), and a closed circuit between terminals 2 and 3.
The analogue output terminals on GAM3.1 (terminals 12 and 13, and terminals 16 and 17) and GAM3.2 (terminals 3 and 4, and
terminals 5 and 6) will have a resistance of over 10 MΩ.
Even though a controller relay may be configured as normally energised, it is also de-energised if the controller loses power.
NOTE
Maritime classification requires backup power supply

Maritime classification approval societies require that there is an independent backup power supply for the controller.
This avoids having a not powered controller.
2.4 Controller functions

Each type of controller has a default configuration. After you assign a function to an input or output, you can assign parameters to
that function.
Most of the controller inputs and outputs can be assigned any function. Functions are not restricted to specific hardware modules.
For example, governor and AVR control functions can use any inputs and outputs, and do not have to use the inputs and outputs on
the Governor and AVR module (GAM3.1).
The controllers allow the same function to use a number of alternative types of inputs and/or outputs. This makes the controllers
very versatile and compatible with a wide range of equipment and systems.
Each controller's display only displays the operating information for that controller. However, the controller processor also has
access to operating information from the rest of the system.
2.5 CODESYS (optional)

As an option, you can buy a controller that allows a CODESYS application to run on the controller.
When CODESYS is installed on the controller, it is no longer possible to use CustomLogic on the controller.
More information
See the Multi-line 300 CODESYS guidelines for a description of how to use CODESYS with the controller.
2.5.1 Inputs and outputs
Assign CODESYS inputs and outputs under Configure > Input/output. Select the hardware module, then select the input/output to
configure. These inputs and outputs must first be defined in the CODESYS program, and written to the controller before they can be
used.

Local > CODESYS > Pulse/ If this input is activated, then the controller activates the
Digital input
CODESYS digital input (× 40) continuous corresponding CODESYS digital input function.
Local > CODESYS > Outputs >

Pulse/ If CODESYS activates the digital output function, then the
CODESYS digital output (× Digital output
continuous controller activates the digital output.
40)
If the CODESYS_application_OK output value is "True" and

Local > CODESYS > State >
Digital output Continuous there are no communication errors, then the controller
CODESYS application OK
activates the digital output.
Local > CODESYS >

Analogue As the value of this input changes, the corresponding
CODESYS analogue input (× -
input CODESYS analogue input value changes.
40)
Local > CODESYS > As CODESYS changes the value of this analogue output, the
Analogue
CODESYS analogue output (× - corresponding analogue output value on the controller
output
40) changes.
2.5.2 Activating controller outputs
CODESYS cannot directly activate controller outputs that are configured for controller functions. For example, CODESYS cannot
activate the [Breaker] > Control > Open digital output.
However, CODESYS can activate external commands, for example, the [Breaker] > Open command. The CODESYS command has
the same effect as, for example, the [Breaker] > Command > Open digital input. The controller only follows the command if the
controller is under remote control.
2.6 Alarms and protections

2.6.1 How alarm processing works
CAUTION
Incorrect alarm configuration

Incorrect configuration of the alarm parameters could result in unwanted operational conditions and possible injury to
personnel or damage to the equipment.
You can not configure some alarms, as the system must maintain a basic level of protection.
Alarm detection
The controller alarms prevent unwanted, damaging, or dangerous situations from occurring. The alarm handling is an adaptation of
the ISA 18.2 standard. You can configure alarm parameters to suit your design and operational needs.
Some of the alarms are Enabled by default in the controller. You can enable or disable certain alarms and configure their alarm
settings (typically the Set point and Delay) as required.
An alarm is detected when the Alarm condition is met (typically, the operating value reaches the Set point), the controller starts the
Time delay. During this period the controller checks whether the Alarm condition remains active. If the Alarm condition is not
longer active, the alarm is not activated. If the Alarm condition continues after the time delay has expired the Alarm action is
activated.

1. The controller detects an Alarm condition.
Start 2. The controller checks if the alarm is enabled:
• If the alarm is not enabled the controller ignores
the alarm.
1.
3. The controller checks if the alarm has an active
Alarm inhibit.
detected • If the alarm has an active inhibit the controller
ignores the alarm.
4. The controller checks if the Alarm condition is still
2. active:
• If the Alarm condition is no longer active the
Enabled Normal controller ignores the alarm.
alarm? No 5. While the Alarm condition is active, the controller
checks if the Time delay has expired:
Yes • If the Alarm condition is no longer active
3.
before the Time delay expires, the controller
ignores the alarm.
Inhibit
active? • If the Alarm condition continues and the Time
Yes
delay expires, the controller activates the alarm
and the Alarm action.
No
4.
Alarm
condition?
No
Yes
5.
Delay
expired? No
Yes
ALARM
The alarm results in both a visual and audible indication (subject to design of your system) for the operator. The system controls the
alarm states as necessary based upon the operational conditions.
Some alarms can be configured to be automatically acknowledged. Auto acknowledge can be useful during commissioning and
troubleshooting. However, DEIF does not recommend Auto acknowledge during normal operation. The Auto-acknowledge feature is
not be approved for use by some Maritime classification societies.
During operation the system continues to monitor the Alarm condition(s) and moves alarms between different states as necessary.
Operator action can also move the alarm(s) to other states.
Alarm processing states

Alarms can be active in the system in different states:
Alarm Alarm
State Symbol Acknowledge Notes
condition action
Not
State A - Not active - Normal state
active

Alarm Alarm
State Symbol Acknowledge Notes
condition action
• The alarm is not active in the system.
Unacknowledged alarm
• An alarm condition occurred.
• An alarm action is active.
State B Active Active Unacknowledged
or • An alarm requires acknowledgement.
• An alarm requires action to clear the alarm
condition.
Acknowledged alarm
• An alarm condition occurred.
• An alarm action is active.
State C Active Active Acknowledged
or • An alarm is acknowledged.
• An alarm requires action to clear the alarm
condition.
Normal state but unacknowledged

Not • An alarm condition occurred, but was cleared.
State D Not active Unacknowledged
or active • An alarm action is inactive.
• An alarm requires acknowledgement.
Unacknowledged latched alarm

• An alarm condition has cleared.
State E Not active Active Unacknowledged • An alarm action is active.
or
• An alarm requires acknowledgement.
• An alarm latch requires reset.
Acknowledged latched alarm

• An alarm condition has cleared.
State F Not active Active Acknowledged • An alarm action is active.
or
• An alarm is acknowledged.
• An alarm latch requires reset.
Shelved alarm
Active or Not Not • An alarm is shelved for a period of time.
State G -
or active active • An alarm returns automatically after the period has
expired.
Out of service alarm

• An alarm is marked out of service for an indefinite
Active or Not Not
State I - period.
or active active
• An alarm does not return automatically and must be
returned to service manually.
Active or Not Not

State H - An alarm is inhibited to occur.
or active active
The three special Shelve (Stage G), Inhibited (Stage H), and Out of service (State I) are not shown in this diagram.

State A
Normal
Alarm
detected
Auto
acknowledge?
No
Yes
State C Operator State B

Acknowledged acknowledges Unacknowledged
alarm alarm alarm
Alarm Alarm
condition condition
clears? No clears? No
Yes Yes
State D Operator
Latched Latched Return to normal
acknowledges
alarm? No alarm? No
Unacknowledged
alarm alarm
Yes Yes
Operator State F Operator State E

resets Acknowledged acknowledges Unacknowledged Alarm
alarm latch latched alarm alarm latched alarm condition?
No
Yes
Alarm Alarm
condition? condition?
No No
Yes Yes
NOTE Alarms configured with a Latch continue to have the Alarm action active even if the Alarm condition is no longer active.
The alarm requires first acknowledgement and then reset by an operator before the alarm can be cleared and return to
normal.
Inhibited, Shelved, or Out of service alarms are forced to be not active in the system, even if the Alarm condition is present.
Automatic actions
The controller controls the following automatic actions:
• Horn/siren output
• Inhibits alarms (if applicable)
• Auto-acknowledges alarms (if configured)
• Controls the alarm state
• Suppress action (if configured)
Operator alarm actions *

An operator controls the following alarm actions:
• Acknowledge
• Shelve
• Out of service
• Latch reset
• Silence alarm horn/siren

NOTE * The actions an operator can use are controlled by the group and user permissions granted to their login.
2.6.2 Alarm parameters
The alarm settings are configured as parameter settings in the controller. Each alarm parameter is explained in detail in the following
sections. Some alarm settings are not configurable and may not be shown for some alarms.
# Parameter Range Notes
Not enabled,
1 Enable Enabled alarms activate in the system if the Alarm condition occurs.
Enabled
2 Set point The setting at which the alarm activates.
3 Reset hysteresis Varies See Reset hysteresis for more information.
4 Delay Varies A time delay before the Alarm action becomes active.
5 Action Varies The Alarm action to be taken.

Inhibit(s) #1 to
6 Varies Inhibit(s), that if active, can inhibit the alarm from becoming active.
#32
Not enabled,
7 Auto acknowledge If Enabled the alarm is automatically acknowledged when it occurs. *
Enabled
Not enabled, If Enabled the alarm is latched when it occurs and requires both
8 Latch
Enabled acknowledgement and reset (unlatch) to clear the Alarm action.
Not enabled, If Enabled the alarm action is suppressed. The alarm message will appear in
9 Suppress action
Enabled the alarm list.
10 Reset counter Set or reset the alarm counter value.
Select Start test to start an alarm test. Starting an alarm test also activates the
Start test, Stop alarm action.
11 Alarm test
test
Select Stop test to stop the alarm test.

Set point
The Set point is the reference value that is compared by the controller to decide whether the Alarm condition is present in the
system.
When the operating value, that the alarm is based on, reaches the Set point, the controller starts the Time delay (if applicable) for
the alarm. The Set point is often a percentage of the controller's nominal setting. Most alarms require a Set point to be configured.
For example, the Set point for the Over-current 1 alarm can be 100 %. This means that the current from the equipment must be 100
% (or more) of the nominal current to activate the alarm.
Reset hysteresis
The Reset hysteresis prevents the operating value from being too close to the alarm Set point when the alarm is reset. The Reset
hysteresis makes the system more stable by imposing hysteresis on the alarm Set point. The Reset hysteresis is a value that is
subtracted from the set point of high alarms (and added to the Set point of low alarms).
A Reset hysteresis can only be used where the alarm is based on an analogue value.
Overspeed example Value

Set
An Overspeed alarm with a Set point of 110 % of nominal speed and a Reset point
hysteresis of 10 %. The alarm cannot be reset until the operating value falls below
100 % of nominal speed. The red line in the figure shows that the alarm is activated Reset
when the value exceeds the Set point. The alarm is only deactivated when the 0
value drops below the reset value. time
Under-speed example
Value
An Under-speed alarm with a Set point of 80 % of the nominal speed and a Reset Reset
hysteresis of 5.0 %. The alarm is only reset when the operating value is above 85.0
Set
% of the nominal speed.
point
time
Delay
When the alarm Set point is exceeded and an alarm Delay is configured, the controller starts the timer for the alarm. If the
operational value stops exceeding the Set point, the timer is stopped and reset. If the value exceeds the alarm Set point for the
whole of the Delay, the controller activates the alarm.
Delay for a high alarm based on an analogue operating value
Value
tdelay tdelay
Set
point
0
time

Delay for a high alarm based on a digital input
Digital
input
t1 t2
HIGH
LOW
Time
The total delay before the alarm Action is activated is the Operate time for the alarm plus the Delay parameter.
Trigger level
If the reference value must be equal to or higher than the Set point to activate the alarm, a High Trigger level is selected in the alarm
configuration.
Similarly, if the reference value must be equal to or lower than the Set point to activate the alarm, a Low Trigger level is selected in
the alarm configuration.
For most alarms the Trigger level is set and cannot be changed. Custom I/O alarms can be configured for High or Low setting of the
Trigger level.
Auto acknowledge
When Auto acknowledge is selected, the alarm is immediately marked as acknowledged in the alarm display when the alarm is
activated.
Alarms that have a Latch configured, even if automatically acknowledged, still require unlatching by the operator.
Action
The Alarm action is the response that you allocate to the Alarm condition. Each alarm can only be assigned one Alarm action.
The controllers are delivered with pre-defined alarm actions. You can change the Alarm action for most alarms.
Alarm actions are used to assign a set of responses for each alarm. Each Alarm action consists of a group of actions that the
system takes when the Alarm condition is met. Alarm actions act as a type of alarm categorisation. Minor alarm situations may be
assigned warnings, while a critical situation may trip the breaker and shutdown the genset.
The Alarm actions are effective as long as the operating value exceeds the alarm Set point (including the Reset hysteresis if
configured) or the alarm is latched.
Priority of alarm action

If two or more alarm actions are active for the same equipment at the same time, the controller performs the Alarm actionwith the
highest priority. A later Alarm actionwith a lower priority does not change the controller's execution of the earlier Alarm actionwith
the higher priority. Similarly, if a more severe Alarm action is activated after a less severe Alarm action, the controller performs the
more severe Alarm action.
Alarm action priority example
One alarm activates Trip generator breaker and stop engine, and at the same time another alarm activates Trip generator
breaker and shutdown engine. Trip generator breaker and stop engine includes a cooldown period, while Trip generator
breaker and shutdown engine does not. The controller shuts down the engine without cooling, regardless of the order of
the alarms.

Inhibits
Inhibits stop the Alarm action. When an inhibit is active, the controller does not activate the Alarm action, even if all the other
alarm conditions are met. Inhibits are automatic and are not controlled by the operator.
If an inhibit with active conditions is created for an active, unacknowledged alarm (with or without a latch), then the alarm state
changes to an inactive, unacknowledged alarm (with or without a latch). The alarm must be acknowledged (and unlatched) before it
is removed from the alarm list.
Inhibited alarms are not shown in the alarm list, unless they have occurred and are unacknowledged before they were inhibited.
The controller types are delivered with default inhibits for each alarm. You can remove these inhibits, and/or add more inhibits. In
addition to the default inhibits, you can also configure three customisable I/O inhibits for selection.
More information
See Customised inhibits for how to configure customisable I/O inhibits.
For example, for a GENSET controller, for generator under-voltage, the inhibits Engine not running is selected. This means that if
the genset is either starting up, or if there is no running detection, the generator under-voltage alarm is disabled.
In addition to the default inhibits available, some alarms include permanent inhibit conditions. These inhibits are not configurable,
and are described under the alarm that uses them.
For some alarms, inhibits are not applicable. The controller will not allow you to select any inhibits for these alarms.
Suppress action
For all controller types, an alarm action is suppressed when Suppress action is Enabled for the alarm, and the function Alarm
system > Additional functions > Suppress alarm action is activated by a digital input, PICUS, Modbus, and/or
CustomLogic.
If the Alarm action is suppressed, when the alarm is activated, the alarm is shown in the alarm handling system, but the Alarm
action is only Warning.
Latch
You can configure a Latch on any alarm. When an alarm with a Latch is activated, the Alarm actionremains in force until the alarm
is acknowledged and then reset (unlatched). Alarm latching provides an extra layer of safety.
For example, you can create a low oil pressure alarm with a latch and a Trip generator breaker and shutdown engine alarm action.
Then, if there is low oil pressure, the controller trips the breaker and stops the engine. The engine remains stopped and will not be
able to start until the alarm is reset.
NOTICE
Effective action with latch

Enabling a Latch on an alarm is not enough for safety protection. To be effective, the alarm must also be Enabled, and
the alarm Action must be effective against the unsafe situation. For example, a Latch on an alarm with the action
Warning offers little extra protection.
Enable *
Some alarms can be Not enabled or Enabled, according to your requirements.
If the alarm is Not enabled, it does not respond to changes in the operating values, and is never activated.
If the alarm is Enabled, it is activated when the alarm Set point and Delay are exceeded. However, if the conditions for one or more
inhibits are met, then the alarm and its Action are inhibited, and not activated.

Do not change an active alarm to Not enabled. If you change an active alarm to Not enabled the Alarm action continues. The
Alarm action cannot be reset until after the alarm is enabled again.
NOTE * Some alarms settings are not configurable. You can not configure some alarms, as the system must maintain a basic
level of protection.
Alarm test
The alarm test activates the alarm and its Alarm action. You can use the alarm test parameter to test individual alarms, for
example, during commissioning.
NOTICE
Alarm tests activate alarm actions

Alarm tests activate alarm actions, some of which can force the system to switchboard control, trip breakers, create a
blackout, and shut down engines. Use extreme care when performing alarm tests during normal operation.
Alarm tests of individual alarms can be stopped one at a time using the parameter, or at the same time using the Stop test button on
the Alarms page in PICUS.
Additional alarm information

The additional alarm information provides information about the state of the alarm. This information can be useful during
commissioning and trouble shooting.
Information Notes
Reset counter value Changes the Counter parameter value to the selected value.
2.6.3 Common alarm actions
Warning
Controller types All
Priority Low
Effect The controller activates a warning alarm.
Block
Priority -
Breaker closing is blocked: If the breaker is open, the controller will not close it. (If the breaker is
closed, this Alarm action does not open the breaker.)
Effect
Genset start is blocked: If the genset is stopped, the controller will not start it. (If the genset is running,
this Alarm action does not stop the genset.)
Trip [Breaker]
Priority High
Effect The controller trips the [Breaker] (that is, without de-loading).

Trip generator breaker and stop engine
Controller types GENSET controllers
Priority High
The controller trips the genset breaker (that is, without de-loading). After the cooldown period, the
Effect
controller stops the engine.
Trip breaker and stop inverter
Controller types HYBRID controllers
Priority High
Effect The controller trips the inverter breaker (without de-loading) and stops the inverter at the same time.
Trip generator breaker and shutdown engine
Controller types GENSET controllers
Priority Highest
The controller trips the genset breaker (that is, without de-loading). The controller shuts down the
Effect
engine, without a cooldown period.
Trip AVR
Controller types GENSET, HYBRID, and SHAFT generator controllers
Priority High
Effect The controller trips the AVR (that is, stops voltage or reactive power regulation).
Trip generator breaker + AVR
Controller types GENSET and SHAFT generator controllers
Priority High
The controller trips the genset or shaft generator breaker (that is, without de-loading) and the AVR (that
Effect
is, stops reactive power regulation).
Trip breaker + AVR
Priority High
The controller trips the inverter breaker (that is, without de-loading) and the AVR (that is, stops reactive
Effect
power regulation).
Trip generator breaker + AVR + stop engine
Controller types GENSET controller
Priority High
The controller trips the genset breaker (that is, without de-loading) and the AVR (that is, stops reactive
Effect
power regulation). After the cooldown period, the controller stops the engine.

Trip breaker and AVR and stop inverter
Priority High
The controller trips the inverter breaker (that is, without de-loading) and the AVR (that is, stops reactive
Effect
power regulation). The controller stops the inverter.
Trip generator breaker + AVR + shutdown engine
Controller types GENSET controller
Priority Highest
The controller trips the genset breaker (that is, without de-loading) and the AVR (that is, stops reactive
Effect
power regulation). The controller shuts down the engine, without a cooldown period.
Stop inverter
Controller types HYBRID controller
Priority High
Effect The controller stops the inverter without checking the breaker position.
2.6.4 Alarm levels
Alarm levels refers to configuring a number of alarms for one reference value. For each alarm level, the Set point, Time delay,
Alarm action and other parameters are configured.
Example of alarm levels

This example shows the busbar voltage alarms that are present by default, that is, Busbar over-voltage 1, Busbar over-voltage 2,
Busbar under-voltage 1 and Busbar under-voltage 2.
Over-voltage 2
115
Voltage [% of nominal voltage]
Over-voltage 1
105
100 No voltage alarms
95
Under-voltage 1
80
Under-voltage 2
70
0 1 2 3 4 5 Delay [s]
If the operation is in the green area, the controller does not activate any busbar voltage alarms.
In the example, an over-voltage Warning alarm is activated if the busbar voltage has been over 105 % of the busbar's nominal
voltage for 5 seconds. If the busbar voltage is over 115 % of the nominal voltage for more than 3 seconds, the controller activates
the Trip [Breaker] alarm action. Both alarms will be active if the busbar voltage is over 115 % of the nominal voltage for more than 5
seconds. The alarm action Trip [Breaker] has a higher priority than Warning.

The graph shows two protection levels for under-voltage. In the example, if the busbar voltage is under 95 % of the nominal voltage
for more than 5 seconds, a Warning is activated. If the busbar voltage is under 80 % of the nominal voltage for more than 3 seconds,
the Trip [Breaker] Alarm action is activated.
2.6.5 Operate time
The operate time is the total time that the controller takes to respond to a change in the operating conditions. The operate time is a
controller characteristic, and not a configurable parameter.
The controller operate time is listed for each AC protection. The operate time starts when the AC conditions change so that the
alarm set point is exceeded. The operate time is completed when the controller has changed its output(s) accordingly.
Operate time = measurement time + calculation time + time to change the controller output(s)
For example, the operate time may be "< 100 ms". This means that the controller protection responds to the change in the
alternating current conditions within 100 ms.
The operate times do not include any provision for the time delay configured for the AC protection. For example, over-voltage has an
operate time of < 100 ms, but the default time delay for Over-voltage 1 is 5 seconds. The Over-voltage 1 alarm action is therefore
between 5.0 and 5.1 seconds after the alarm set point is exceeded.
2.6.6 Acknowledge an alarm
Alarms must be acknowledged. The operator must take action regarding the Alarm condition. The operator can mark the alarm as
acknowledged. Alarms that have Auto-acknowledge do not require acknowledge by operator action.
NOTICE
Active alarm action

Acknowledging an alarm has no influence on the alarm Action.
Table 2.1 Acknowledgement status and operator actions
Acknowledged? Latch? Alarm condition? Alarm action * Required operator actions
• The alarm condition must be corrected.

Active Active • The alarm must be acknowledged.
Latch • The alarm must be reset (unlatched).
• The alarm must be acknowledged.

Unacknowledged Inactive Active
• The alarm must be reset (unlatched).

Active Active
No latch • The alarm must be acknowledged.
Inactive Inactive • The alarm must be acknowledged.

Active Active
Latch
Acknowledged Inactive Active
Active Active • The alarm condition must be corrected.

No latch
Inactive Inactive • No further action is required.
NOTE * Alarm action is controlled automatically by the controller.

Inhibited, shelved, and out of service alarms all have an inactive alarm Action.
Digital inputs
Alarm system > Command > When this input is activated, the controller acknowledges all its
Digital input Pulse
Acknowledge all alarms alarms.
Power management > When this input is activated, the controller acknowledges all its
Acknowledge all alarms in Digital input Pulse own alarms, along with all the alarms in all the other controllers in
system the system.
2.6.7 Alarm latch and reset
An additional layer of protection can be added by using a Latch on most alarms. When a Latch is Enabled on an alarm, there is an
extra confirmation that must be made by the operator, before the alarm can be cleared. The Alarm action remains active, even if
the Alarm condition clears, until the operator resets the latched alarm.
A latched alarm can only be reset by an operator after both the alarm has been acknowledged and the Alarm condition has
cleared. Acknowledging the alarm does not Reset the alarm latch.
For example, you can configure a low oil pressure alarm with a latch enabled, with a Trip generator breaker and shutdown engine
alarm action and an Engine not running inhibit. If there is low oil pressure, the controller trips the breaker and shuts down the
engine. The engine remains stopped and will not be able to start until the operator acknowledges the alarm AND resets the latch.
1. 1. An alarm activates in the system as either:

• Unacknowledged (State B)
ALARM
• Acknowledged (State C) *
2. The controller checks if the Alarm condition has cleared.
2.
• If the Alarm condition continues, the Alarm action
Alarm remains active.
condition
clears? No 3. The controller checks if the alarm has a latch configured:
• If the alarm has a latch configured, the controller
Yes continues from step 6.
3. 4. 5.
4. The controller checks if the alarm is acknowledged:
Alarm Operator
Alarm • If the alarm is acknowledged the alarm returns to normal
has a acknowledged? acknowledges
State A.
latch? No No alarm
5. The operator acknowledges the alarm. After the
Yes Yes acknowledgement the alarm returns to normal State A.
6.
6. A latched alarm in the system is either:
State E or F State A • Unacknowledged (State E)
ALARM NORMAL
• Acknowledged (State F)
7. The controller checks if the alarm is acknowledged:
7. 8. • If the alarm is acknowledged, the controller continues
Operator from step 9.
Alarm
acknowledged? acknowledges 8. The operator acknowledges the alarm, and the alarm the
No alarm latch can then be reset.
Yes
9. The operator resets the latch on the alarm, and the alarm
9.
returns to normal State A.
Operator
resets
alarm latch
State A
NORMAL

NOTE * The alarm may have Auto-acknowledge configured. Auto-acknowledge can be useful during commissioning and
troubleshooting. However, DEIF does not recommend the use of Auto acknowledge during normal operation. The Auto-
acknowledge feature is not be approved for use by some Maritime classification societies.
Digital input (optional)

Alarm system > Command > Reset The controller resets all latched alarms (that are ready to be
Digital input Pulse
all latched alarms reset) when this input is activated.
2.6.8 Shelve an alarm
The operator can shelve each alarm for a period of time, during any alarm state (except if the alarm is already Out of service).
If an unacknowledged alarm is shelved, the alarm is automatically acknowledged. If a latched alarm is shelved, the latch on the
alarm is reset. While the alarm is shelved, the alarm action is not active.
When the period expires, the alarm is automatically unshelved. Alternatively, an operator can manually unshelve the alarm. The
alarm then responds as normal to alarm conditions.
CAUTION
Shelved alarms
Shelving certain alarms can disable critical protections. In addition, shelving automatically acknowledges the alarm and
resets the latch.
1. 1. The alarm can be in any state.

Any state 2. The operator shelves the alarm for a specific period of time.
3. The alarm is now shelved (State G).
2.
4. The operator unshelves the alarm, the alarm returns back to its original state.
Operator 5. The controller checks if the shelve period has expired:
Shelves • If the shelve period has not expired, the alarm remains as shelved.
alarm
6. The system unshelves the alarm if the shelve period has expired.
4. 3.
Operator
Unshelves State G
alarm Shelved
5.
Shelve
period
expired? No
Yes
6.
System
Unshelves
alarm
Return

2.6.9 Out of service an alarm
You can take any alarm Out of service, during any alarm state (except if the alarm is already Shelved). When an alarm is Out of
service, the alarm is suspended indefinitely.
CAUTION
Out of service alarms

Taking certain alarms Out of service can disable critical protections. In addition, taking Out of service automatically
acknowledges the alarm and resets the latch.
1. 1. The alarm can be in any state.

Any state 2. The operator removes the alarm from service.
3. The alarm is now out of service (State I).
2. 4. The operator returns the alarm to service, the alarm returns back to its original state.
Operator
Removes from
service
3.
State I
Out of service
4.
Operator
Returns to
service
Return
NOTE The system does not automatically return an Out of service alarm, an operator must perform this action.
2.6.10 Alarm test
An alarm test activates the controller alarms and all their Alarm actions. You can activate alarm tests from the PICUS Alarms page,
or by starting an alarm test for an individual alarm using the alarm's Alarm test parameter.
CAUTION
Do not use during normal operation

DO NOT use the alarm test during normal operation. The alarm actions will force the system under switchboard control,
trip all the breakers, and create a blackout.
More information
See Alarms in the PICUS manual for the alarm test buttons available on the Alarms page in PICUS.
Before the test

Make sure that a blackout is acceptable, before you use the alarm test function. Be aware that it may take you some time to get the
system back to normal after an alarm test.

During the test
When the test is Enabled, the alarms appear on the display and in the alarm list, and are recorded in the log. Test alarms appear in
green text on the display, and are marked with a grey dot in the T column in the PICUS alarm list.
If an alarm was acknowledged before the test, the alarm status changes to unacknowledged during the alarm test.
If an alarm is acknowledged during the test, the alarm remains on the alarm list, and the alarm action continues until the alarm test
stops.
• Latched alarms: Alarms with latches can be acknowledged and the latches reset manually during the test. If an alarm latch is
reset during the test, then the alarm is removed from the alarm list, and the alarm action stops.
• Shelved alarms: The alarm test unshelves these alarms, and they remain unshelved after the test.
• Out of service alarms: The alarm test returns these alarms to service. These alarms remain in service after the test.
After the test

When the test is Not enabled, the tested alarms remain active until they are acknowledged and, if required, their latches are
removed. The alarms are rechecked, and reactivated if the alarm conditions are still present. All the test alarms remain in the log,
and are indicated with a grey dot in the T column.
Alarms that were acknowledged before the alarm test are still acknowledged when the alarm test stops.
2.6.11 Alarm status digital outputs
You can configure a digital output with a function for an alarm status. The controller activates the digital output if the alarm status is
present.
Table 2.2 Alarm status digital output functions
Function Type Details GENSET HYBRID SHAFT SHORE BTB
Activated if the power supply to

PSM3.1 is OK, and all of the controller
hardware module self-checks were
OK.
Status OK is always configured on

Local > System OK > terminals 3 and 4 of PCM3.1. Status
Continuous ● ● ● ● ●
Status OK OK can also be configured on any
other digital output terminals.
This digital output has a safety

function. The controller deactivates
this output if there is a problem with
the controller.
Alarm system > State > Activated if there are any warning
Any warning alarm alarm active in the controller.
Activated if there is any active alarm in

Alarm system > State >
Continuous the controller with the alarm action ● ● ● ● ●
Any block alarm
Block.

Continuous the controller with the alarm actions ●
Any GB trip alarm
Trip generator breaker.

Continuous the controller with the alarm actions ●
Any breaker trip alarm
Trip breaker.

Function Type Details GENSET HYBRID SHAFT SHORE BTB
Alarm system > State > Activated if there is any active alarm in
Any GB trip and stop Continuous the controller with the alarm action Trip ●
alarm generator breaker and stop engine.

the controller with the alarm action Trip
Any GB trip and Continuous ●
generator breaker and shutdown
shutdown alarm
engine.
Alarm system > State > Activated if there is any active alarm in
Any breaker trip and Continuous the controller with the alarm action Trip ●
stop inverter alarm breaker and stop inverter.
Activated if there are any

Alarm system > State > acknowledged, unacknowledged or
Any alarm alarms with active latches in the
controller.
Alarm system > State > Activated if there are any
Any unacknowledged Continuous unacknowledged alarms in the ● ● ● ● ●
alarm controller.
Alarm system > State > Activated if there are any active alarms
Any latched alarm with active latches in the controller.
Alarm system > State > Activated if there are any shelved
Any shelved alarm alarms in the controller.
Activated if any alarms in the controller
Any out of service Continuous ● ● ● ● ●
are out of service.
alarm

Continuous the controller with the alarm action Trip ●
Any SGB trip alarm
shaft generator breaker.

Any SCB trip alarm
shore connection breaker.

Any BTB trip alarm
bus tie breaker.
Alarm system > State > Activated if there is any active alarm
Continuous ● ● ●
Any AVR trip alarm with the alarm action Trip AVR.
Activated if there is any active alarm

Continuous with the alarm action Trip generator ●
Any GB + AVR alarm
breaker + AVR.
Activated if there is any active alarm

Continuous with the alarm action Trip generator ●
Any SGB + AVR alarm
breaker + AVR.
Any breaker + AVR Continuous with the alarm action Trip breaker + ●
alarm AVR.
Any GB + AVR + stop Continuous with the alarm action Trip generator ●
engine alarm breaker + AVR + stop engine.
Any GB + AVR + stop Continuous with the alarm action Trip breaker and ●
inverter alarm AVR and stop inverter.

Applications
A digital output with an alarm status may be wired to a switchboard light, to help the operator. For example, you can configure a
relay with the Alarm system > State > Any latched alarm function, and wire it to a light on the switchboard. When there
are any alarms with active latches, the light is lit. The operator then knows that there are alarms that must be checked and
unlatched.
Alarm test
The alarm test activates these outputs. Acknowledging the test alarms deactivates the outputs.
2.6.12 Customising alarms
You can customise the alarms for your system by configuring the alarm parameters. The parameters that you can configure are
restricted for some alarms.
You can also create custom alarms for the input/output configurations for both analogue and digital terminals.
Limitations on alarm parameters that cannot be customised

Not customisable Notes
The list of alarms is fixed, and you cannot add more alarms.
Additional alarms
If an alarm is not available, you can set it up in CustomLogic. However, it will not be part of the alarm
list, or the alarm management system.
Some alarms cannot be disabled. For example, the Phase sequence error protection (which prevents
Certain alarms synchronisation when the phase sequence is not the same on either side of the breaker) is always
Enabled.
You cannot change certain alarm actions. For example, for Voltage or frequency not OK, the action is
Certain alarm actions
always Block, to stop the breaker from closing.
You cannot create additional alarm actions. You can only choose alarm actions from the list of alarm
actions.
Additional alarm actions
You can set up responses to operating values or conditions in CustomLogic, but these will not be
available as alarm actions to the alarms.
You cannot add more inhibits to the list of inhibits available for selection for the controller type. For
example, you cannot select the Tie breaker closed inhibit, as this is not applicable to the GENSET
Inhibits that are not controller.
configured for the
controller type
However, there are three custom inhibits for each controller. You can activate a custom inhibit using a
digital input, Modbus, and/or CustomLogic.
Change the Trigger level Most alarms have a fixed Trigger level. For example, Busbar over-voltage is always a High alarm, while
for certain alarms Busbar under-frequency is always a Low alarm.
2.6.13 Customised inhibits
In addition to the default inhibits, you can also use three custom inhibit functions (Inhibit 1, Inhibit 2 and Inhibit 3). You can activate a
custom inhibit using a digital input, PICUS, Modbus, and/or CustomLogic or CODESYS.
Digital input
Alarm system > Inhibits > When the digital input is activated, then the controller
Digital input Continuous
Activate inhibit # * applies Inhibit # *
NOTE * Where # is 1 to 3.

If you use CustomLogic, you do not have to wire up a digital input, and assign the Activate inhibit # function to the input.
Parameters
Select the customised inhibit:
[Alarm] > Inhibit > #[number]
Where [Alarm] represents any alarm, and [number] represents the number of the inhibit field.
Table 2.3 Inhibit parameters
Range Notes
The controller inhibits, plus Inhibit #, where # is 1 If you select Inhibit #, and the digital input Activate inhibit # is activated, then
to 3 the controller inhibits the alarm.
2.6.14 Suppress action inhibit
It can be useful to use a digital input function to suppress the alarm action for certain alarms. You can activate the function using a
digital input, PICUS, Modbus, and/or CustomLogic or CODESYS.
Digital input
Alarm system > Additional
When the digital input is activated, then the controller
functions > Suppress alarm Digital input Continuous
suppresses all the alarms with Suppress action enabled.
action
2.7 CustomLogic
2.7.1 Use CustomLogic
CustomLogic is used in PICUS to create and configure customised logical operations for use in the system. These functions are built
using ladder logic elements and can include interaction with external equipment, or more advanced logic interfaces.
When CODESYS is installed on the controller, it is no longer possible to use CustomLogic on the controller.
More information
See CustomLogic in the PICUS manual for how to use CustomLogic.
2.7.2 Enable CustomLogic
Local > CustomLogic > Configuration

Parameter Range Default Comment
Not enabled: The controller ignores the CustomLogic projects. The inputs and
Not enabled, outputs remain assigned to CustomLogic and cannot be used elsewhere.
Enable Not enabled
Enabled
Enabled: The controller executes the CustomLogic project.

2.7.3 Digital inputs and outputs (optional)
If this input is activated, then the controller activates the

corresponding CustomLogic digital input function.
Local > CustomLogic >
Digital Pulse/
CustomLogic digital The controller can execute the logic in a CustomLogic Project once
input continuous
input * every 200 milliseconds. If an input signal is not available for at least
200 milliseconds there is a risk that the input signal will not be
detected by the controller.
Local > CustomLogic >
Digital Pulse/ If CustomLogic activates the digital output function, then the
Outputs > CustomLogic
output continuous controller activates the digital output.
digital output *
If the parameter Configure > Parameters > Local >

Local > CustomLogic > Digital
Continuous CustomLogic > Configuration > Enable is Enabled, then
State > Is enabled output
the controller activates this output.
NOTE * There are 20 available CustomLogic digital inputs or outputs.
2.7.4 Custom parameters
Custom parameters can be used with CustomLogic for reading, comparing, or writing values. Up to 50 customer parameters can be
configured.
Configure custom parameters under Custom parameters.
Custom parameter # *
Not enabled: The parameter is not used.

Enable # Not enabled, Enabled Not enabled
Enabled: The parameter can be used in a CustomLogic project.
Integer # - 2147483647 to 2147483647 0 The range for the integer value to be stored.
Float # - 2147480000 to 2147480000 0.0000 The range for the float value to be stored.
NOTE * Where # is the parameter number from 0 to 49.
2.7.5 Activate controller outputs
CustomLogic cannot directly activate controller outputs that are configured for controller functions. For example, CustomLogic
cannot activate the [Breaker] > Control > Open digital output.
However, CustomLogic can activate external commands, for example, the [Breaker] > Open command. The CustomLogic
command has the same effect as, for example, the [Breaker] > Command > Open digital input. The controller only follows the
external command if the controller is in remote control.
2.7.6 CustomLogic and Modbus
Each controller has 20 Modbus signals that can be assigned to contacts and coils.
When a Modbus signal is assigned to a contact, the contact can be activated and deactivated using the correct Modbus address for
the signal number.

When a Modbus signal is assigned to a coil, the state of the coil can be read using the correct Modbus address for the signal
number. It is not possible to use a Modbus interface to write a value to a Modbus signal that has been assigned to a coil.
2.7.7 Restrictions
CustomLogic reset on save

If you make a change to the CustomLogic and then save the change to the controller, all the CustomLogic states and timers are
reset.
CustomLogic under switchboard control

CustomLogic remains enabled when the controller is in switchboard control.
However, the controller does not accept external commands in switchboard control. For example, if CustomLogic activates a
command to open a breaker, the controller ignores the command.
If the logic should not be processed while the controller is in switchboard control, a open normally closed contact should be added to
the logic lines where necessary. Set the normally closed contact to Mode > Inputs > Under switchboard control.
2.8 Emulation
With emulation you can run your controllers in a virtual operating mode. During emulation you can simulate various real-world
actions, such as starting or stopping the genset without actually having any genset connected. You can also test and configure your
controller, and mimic inputs or outputs that are configured.
More information
See Emulation in the PICUS manual for how to use and configure the emulation feature.
2.9 Custom parameters

You can configure up to 50 custom parameters for use in CustomLogic, CODESYS applications or Modbus.
Configure custom parameters under Custom parameters.
Custom parameter # *
Not enabled: The parameter is not used.

Enable # Not enabled, Enabled Not enabled
Enabled: The parameter can be used in a CustomLogic project.
Integer # - 2147483647 to 2147483647 0 The range for the integer value to be stored.
Float # - 2147480000 to 2147480000 0.0000 The range for the float value to be stored.
NOTE * Where # is the parameter number from 0 to 49.
2.10 Date and time

2.10.1 About date and time settings
The date and time can be set manually from PICUS or the display, or automatically obtained from an external time server.
The time is stored locally on each controller, and automatically synchronised between all DEIF controllers connected in the same
network. The alarms, logs, and display unit use the time.

Time master
The time master's time is synchronised to all the other controllers. The synchronisation is achieved by using a Network Time
Protocol (NTP) client and server system. The controller that has been powered ON for the longest time on the Ethernet network is
the time master. When a new controller is added to the network, it fetches the time from the time master in the network.
If two Ethernet networks with DEIF controllers are joined, then the time from the network with the controller that has been powered
on for the longest is used.
If the time master fails, the controllers in the network determine which controller has been ON the longest. The controller that has
been on the longest, then becomes the new time master.
Synchronisation interval and performance

Each controller checks the time from the time master at regular intervals. The frequency of these checks adapts to the
synchronisation quality. If the synchronisation is poor, then the controller uses shorter intervals between checks.
The time difference can initially be a few seconds. This is adjusted down over time. The time synchronisation can take some time
(for example, 30 minutes) to synchronise the controllers.
Table 2.4 Date and time settings
Setting Range Default Notes
• YYYY-MM-DD
• YY-MM-DD
• DD-MM-YYYY
Date format YYYY-MM-DD
• DD-MM-YY
• MM-DD-YYYY
• MM-DD-YY
If an NTP server is configured, then you are not able to change

Date 2018-01-01 to 2037-12-31
the date manually.
The adjustment for daylight saving is based on the time zone, and
is automatically applied by the controller.
Time zone Selectable list Etc/UTC
Daylight savings is not applied to the controller when you select
the Etc/UTC time zone.
• 12 hour clock The AM/PM selector for Time is only visible when 12 hour clock is
Time format 24 hour clock
• 24 hour clock selected.
• 00:00:00 to 23:59:59 If an NTP server is configured, then you are not able to change
Time
• 12:00:00 AM to 11:59:59 PM the time manually.
NOTE If a setting is changed on any controller in the network, the new setting is synchronised to all controllers in the network.
Table 2.5 Network time protocol settings
Type the IP address or server address of the NTP server in this field. When either of the Host
Host * -
fields have data inside them, it is no longer possible to configure the date or time manually.
Unicast: The controller sends requests to the specified host and to request the date and time.
The controller updates the date and time when the host responds to the request.
• Unicast
Mode * Unicast
• Multicast
Multicast: The controller waits for a date and time to be broadcast from a server on the host
location. The controller updates the date and time when a broadcast is received.

NOTE * You can configure 1 or 2 NTP servers.
2.10.2 Set the time manually
Use the Configure > Time settings page in PICUS or the display to set the time manually.
When you change the time on any controller in the network, the new time is shared with all the controllers in the network through the
time master.
2.10.3 Use external NTP servers
To use external NTP servers, the network design must allow the controllers to access the NTP server(s).
If two NTP servers are configured, then the NTP server with the lowest Stratum is the server used. If the NTP servers have the
same Stratum, then the NTP server configured in Server 1 is the server used.
2.11 About permissions

Access to the controllers' configuration and functionality is protected with user permission access. The controller is supplied with a
number of default Groups, Users and Passwords. Only users with the correct permission may access, configure, or update the
configuration.
Permission structure
The permissions structure allows the creation and maintenance of users and groups within each controller configuration. These are
stored locally on each controller, and therefore each controller can store its own set of user permissions and groups.
Figure 2.5 User profiles on controllers
DEIF
network
Controller Controller
1 2
User 4
User 1 User 3
User 2
User 5
However, you can also Broadcast these settings to any or all of the other connected controller(s), which creates the same
permissions on them.

Figure 2.6 Broadcast user profiles to all controllers
DEIF
network
Controller Controller Controller

1 2 3
User 1 Broadcast User 1 User 1

permissions
User 2 User 2 User 2
Create the same permissions on all the connected controllers. If a controller must have different permission settings, do not
broadcast these settings.
Each user is a member of a group. The group gives the user permissions to associated features or functions of the controller.
When a user is assigned to a group, they inherit the permissions for that group.
In the following diagram, you can see the permissions that User 1 and User 2 have to the controller. Both User 1 and User 2 are
members of a basic permission group, and they inherit the permissions from that specific group.
Figure 2.7 Simple permission example
Basic group
User 1
Read access User 2
No access
Alarms Log Tools Configure
In the diagram, User 1 and User 2 are members of the Basic group. They have read access to the Alarms, and Log, but they have
no access to the Tools or Configure functions.
Permissions access enables you to easily control which user can access which function. This provides a layer of control for the
operation of the controller.

NOTICE
Permissions access
You can only access the user permissions option if you are a member of a group that has access to that function.
2.11.1 User settings
The following information is stored for each of the Users on the controller.
Table 2.6 User settings
Setting Type Notes
User name Required Minimum 2 characters.
Organisation Optional
Group Required Selectable from list.
Mobile number Optional
Direct number Optional
Email (primary) Optional
Email (secondary) Optional
Notes Optional
Password Required Minimum 8 characters.
2.11.2 Group settings
Permissions are divided into group settings and the permission levels under that group.
Group settings
The Group settings contain the general information about the permission group.
Setting Type Notes
Name Required
Owner Optional
Date of creation Automatic System created
Users in group Automatic List of users assigned to this group
Notes Optional
Group permissions
The group permissions grant or remove access to each of the different areas in the software.
Table 2.7 Access levels
Setting Notes
Read access Allows settings to be read from the controller.
Read/write access Allows settings to be read or written back to the controller.
No access Allows no access for the function or setting.
Mixed access Where permissions are different at different levels within the permission area.

Setting Notes
Assigned automatically by system.
Table 2.8 Permission areas and features
Software area Tasks
Live Data Live Data
• Single-line creator
Application • Emulation
• Single-line supervision
• Alarm acknowledge
• Alarm reset latch
Alarms
• Alarm out of service
• Alarm shelved
I/O status I/O status
• Log
Log
• Engine interface J1939 DM2
• Translations
• Report
• Backup
• Restore
• Restore configuration
• Trending
Tools • Communication
• Regulator status
• Alarm test
• Advanced
◦ Firmware
◦ Change controller
◦ Permissions
• Date and time

• View design
• Input/output configuration
• Parameters
Configure • Counters
• CustomLogic
• Flexible Modbus
• Fieldbus configuration
• Fieldbus supervision
2.11.3 Default users
NOTICE
Secure your system

Ensure that all default passwords are changed to reduce any security risk to your system. Additionally, it is
recommended to adjust or edit the group and user permissions according to your own operational needs.

Default users
The controller is supplied with a number of default users, groups, and passwords. These provide initial access to the controller and
should be changed during commissioning.
Table 2.9 Default users
Password (before PCM APPL Password (PCM APPL

User Group
1.0.13.x) 1.0.13.x or later)
Operator 00000000 0 Operators
Service 00000002 0 Service engineers
Designer 00000003 0 Designers
Admin 00000004 0 Administrators
2.11.4 Default group permissions
Table 2.10 Operators group
Permission Read Read write No access Mixed access
Live data ●
Live data ●
Application ●
Single-line creator ●
Single-line supervision ●
Alarms ●
Alarm acknowledge ●
Alarm reset latch ●
Alarm out of service ●
Alarm shelved ●
Log ●
Log ●
Engine interface ●
Tools ●
Translations ●
Report ●
Backup ●
Restore ●
Restore configuration ●
Communication ●
Regulator status ●
Alarm test ●
Tools > Advanced ●
Firmware ●
Permissions ●
Configure ●

Date and time ●
View design ●
Input/output
●
configuration
Parameters ●
Counters ●
CustomLogic ●
Flexible Modbus ●
Fieldbus configuration ●
Fieldbus supervision ●
Table 2.11 Service engineers group
Live data ●
Live data ●
Application ●
Alarms ●
Alarm shelved ●
Logs ●
Log ●
Tools ●
Translations ●
Report ●
Backup ●
Restore ●
Communication ●
Alarm test ●
Firmware ●
Permissions ●
Configure ●
Date and time ●

view design ●
Input/output
●
configuration
Parameters ●
Counters ●
CustomLogic ●
Flexible Modbus ●
Table 2.12 Designers group
Live data ●
Live data ●
Application ●
Alarms ●
Alarm shelved ●
Logs ●
Log ●
Tools ●
Translations ●
Report ●
Backup ●
Restore ●
Communication ●
Alarm test ●
Firmware ●
Permissions ●
Configure ●
Date and time ●
View design ●

Input/output
●
configuration
Parameters ●
Counters ●
CustomLogic ●
Flexible Modbus ●
NOTE You cannot delete the Administrators group.
Table 2.13 Administrators group
Live data ●
Live data ●
Application ●
Alarms ●
Alarm shelved ●
Logs ●
Log ●
Tools ●
Translations ●
Report ●
Backup ●
Restore ●
Communication ●
Alarm test ●
Firmware ●
Permissions ●
Configure ●
Date and time ●

View design ●
Input/output
●
configuration
Parameters ●
Counters ●
CustomLogic ●
Flexible Modbus ●
NOTE You cannot delete the Display group.
Table 2.14 Display group
Live data ●
Live data ●
Application ●
Alarms ●
Alarm shelved ●
Logs ●
Log ●
Tools ●
Translations ●
Report ●
Backup ●
Restore ●
Communication ●
Alarm test ●
Firmware ●
Permissions ●
Configure ●

Date and time ●
View design ● ●
Input/output
●
configuration
Parameters ●
Counters ●
CustomLogic ●
Flexible Modbus ●
2.12 Event log

The controller stores a maximum of 2000 log entries. When the log is full, the controller discards the excess log entries using first in,
first out.
If an ECU has been configured, you can also switch to see the DM2 logs.
2.13 Non-Essential Loads (NEL)

You can assign a non-essential load to a GENSET, HYBRID, EMERGENCY genset, SHAFT generator and/or SHORE connection
controller.
You cannot assign a non-essential load to a BUS TIE breaker controller.
NEL configuration options

Name Details
Label Customisable label for the non-essential load.
NEL ID Select NEL 1, NEL 2 or NEL 3. IDs that are already used are not shown.
NEL trip signal # Select a controller from the list. Controllers that are not in the same section are not shown.
New NEL trip If there are other controllers in the section that the NEL trip signal can be connected to, you can
signal(s) select these in the New NEL trip signal list.
The NEL must be assigned to the controller on the Application single-line diagram in order for the NEL functions to be visible under
the controller inputs and outputs.
More information
See the PICUS manual for how to create the Application single-line diagram and add a non-essential load.
2.13.1 Non-essential load trip (NEL) function
Non-essential load trip (NEL) groups are tripped to protect the busbar against imminent blackout. The NEL can be configured to trip
(that is, disconnect) if over-current, low busbar frequency, overload and/or reactive overload is measured by a controller.
Each non-essential load (NEL) trip is a function with a warning alarm. The trip is active until the measurement that activated the
alarm returns to normal (unless the alarm is latched; then the trip remains active until the latch is reset). The operator can then
reconnect the non-essential load.
For NEL alarms, you can only set the set point and the delay. You cannot assign other alarm actions.

Up to three non-essential loads (NEL) can be defined per controller. The NELs are tripped individually, that is, a trip of NEL 1 does
not directly influence NEL 2 or NEL 3. Inhibits are used to prevent a NEL trip when the breaker to the busbar is open.
The NEL trip relay is activated when one or more of the NEL alarms is activated. It remains active whenever there is at least one
NEL alarm, even if the original NEL alarm is deactivated.
NOTE In this description, # represents the NEL ID where # is 1, 2 or 3.

Wiring examples
Figure 2.8 Example of three non-essential loads that are connected for full redundancy
NEL 1 NEL 2 NEL 3
G G G G
For redundancy and secure operation, DEIF strongly recommends that all controller NEL trip settings are identical.

Figure 2.9 Example of 12 non-essential loads that are connected with no redundancy
N N N N N N N N N N N N
E E E E E E E E E E E E
L L L L L L L L L L L L
1 2 3 1 2 3 1 2 3 1 2 3
G G G G
DEIF recommends that you connect each non-essential load to each controller, so that any controller can trip the non-essential
loads. As a minimum, each non-essential load should be connected to at least two controllers. However, it is possible to connect
each controller to up to three non-essential loads, with no interaction from the other controllers.
Digital output
For each controller assign the non-essential load outputs. The NEL must be added to the application single-line diagram before you
can configure this digital output.
The controller activates the output when a non-essential load alarm is

activated.
Non-essential
load trip > Non- Digital
Continuous The digital output will be activated as long as at least one NEL alarm is active.
essential load output
trip # That is, if the operating value no longer exceeds the set point, the digital
output is normally deactivated. However, if an NEL alarm has a latch, the
digital output will not be deactivated until latch is reset.
Parameter
The non-essential load parameter is only visible when the Non-essential load trip # function is configured.
Non-essential load trip > Trip # > Settings

Not enabled: Controller breaker trips have no direct effect on the non-
essential load trips.
Trip when Not enabled,
Not enabled
breaker trips Enabled Enabled: Whenever the controller breaker trips, then the controller also
activates the Non-essential load trip # output. The NEL trip remains active as
long as the breaker trip is active.

How the NEL function works
Example NEL 1 over-current, without a latch
1. Current: The current fluctuates based on the

demand. When the current exceeds the set
point, the alarm's delay timer starts. If the
current is over the set point for the delay time,
the alarm is activated and the NEL breaker trips.
In response, the current drops.
2. NEL 1 over-current: The controller activates the
NEL alarm when the operating value is above
the set point for the delay time.
• The alarm is deactivated when the alarm
value returns to normal.
3. NEL trip: Non-essential load trip > Non-
essential load trip # (digital output): The
controller activates this output when an NEL
alarm is activated. The output is deactivated
when all the NEL alarm values return to normal.
4. NEL breaker: The NEL breaker disconnects the
NEL when the controller activates the NEL trip
output. The operator has to close the breaker to
reconnect the NEL.
5. Operator: Operator intervention is required to
reconnect the NEL.
Example NEL 1 over-current, with a latch
1. Current: See the previous example.

2. NEL 1 over-current: The controller activates the
NEL alarm when the operating value is above
the set point for the delay time.
• The alarm is reset when the latch is reset.
3. NEL trip: Non-essential load trip > Non-
essential load trip # (digital output): The
controller activates this output when an NEL
alarm is activated. The output is deactivated
when all the NEL alarm values are normal, and
all latches are reset.
4. NEL breaker: The NEL breaker disconnects the
NEL when the controller activates the NEL trip
output. The operator has to close the breaker to
reconnect the NEL.
5. Operator: Operator intervention is required to
reset the latch and reconnect the NEL.
2.14 Lamp test

The lamp test lights all the LEDs on the display. The test cycles through the LED colours for the time configured in the lamp test
parameters.
During the lamp test a message box is shown on the display.

Digital inputs (optional)
Test functions > Lamp test > Activating this input has the same effect as enabling the lamp
Digital input Pulse
Start lamp test test Activate parameter.
Test functions > Lamp test > If this input is activated while a lamp test is in progress, the
Digital input Pulse
Stop lamp test controller stops the lamp test.
Parameters
Test functions > Lamp test
Not enabled: There is no lamp test.
Enabled: When the parameter is saved, the lamp test starts. After the lamp
Not enabled,
Activate Not enabled test, the controller automatically changes the parameter to Not enabled.
Enabled
Alternatively, you can start the lamp test from the display unit (Tools >
Advanced > Lamp test) or a digital input (see above).
Duration 1 s to 1 h 18 s The time for the lamp test.
The time that each colour is lit. The colour cycle is green, yellow, red. The
Color cycle color cycle repeats for the duration of the lamp test.
1 s to 1 h 3s
time
For the default settings, the lamp test will cycle through all the colours twice.
2.15 Alive
To confirm that the controller is operational, a digital output can be configured to activate for a specified amount of time in a time
period. If the signal does not repeat within the defined time period, then the controller is no longer operational.
Digital output (optional)

The output is set to high for the Duty cycle time each Period.
Local > Alive Digital
Pulse
> Alive output For example, if the Duty cycle is set to 50 % and the Period is set to 2 s, then the output
is high for 1 s and low for 1 s. This signal repeats while the controller is operational.

Parameters
Local > Alive > Alive configuration
The percentage of the Period that the signal is high.
Duty cycle 0 to 100 % 50 % If the Duty cycle is set to 0 %, then the I/O output is always low.
If the Duty cycle is set to 100 %, the output is always high.

Period 0.1 s to 60 s 2s The time between the start of a high signal to the start of the next high signal.

3. Busbar sections and load sharing
3.1 About busbar sections

3.1.1 Dynamic busbar sections
The bus tie breakers create busbar sections. The bus tie breakers can be externally controlled, or controlled by a BUS TIE breaker
controller.
The busbar sections are dynamic. That is, the sections change whenever bus tie breakers are opened or closed.
Figure 3.1 Example of busbar sections
Bus tie Bus tie Bus tie

breaker 1 breaker 2 breaker 3
Section 1 Section 2
Bus tie
breaker 4
Section 4 Section 3
When the breaker(s) are open, each busbar section is independent from the other section(s). The controllers in the section can
share the load in that section.
If the breaker(s) are closed, then the connected busbar sections together form one busbar section, as shown in the example below.
The controllers in the connected busbar section can share the load for the combined busbar section.

Figure 3.2 Example of busbar sections created by closing two bus tie breakers
Bus tie Bus tie Bus tie

breaker 1 breaker 2 breaker 3
Section 1-2-3 Section 1-2-3
Bus tie
breaker 4
Section 4 Section 1-2-3
NOTE The busbar sections are numbered here to make it easier to understand sections. However, busbar section numbers are
not used in PICUS.
3.1.2 Externally controlled bus tie breaker
The externally controlled bus tie breaker function allows an externally controlled bus tie breaker to be present. This breaker is
opened or closed by the operator. The DEIF controllers only receive position feedback from the breaker, and do not control it.
Additional equipment
You should install a check sync relay or a paralleling relay in the switchboard, to check the synchronisation before closing, for
example, the DEIF CSQ-3 or HAS.
Wiring example
More information
See Wiring examples for controller functions, Breaker wiring in the Installation instructions for an example of
external breaker wiring.
Inputs and outputs

Assign the externally controlled bus tie breaker inputs in the chosen controller under Configure > Input/output. Select the hardware
module, then select the digital input to configure.
Table 3.1 Hardware required in addition to the minimum standard controller wiring
Breakers > External breaker #> Feedback > The feedback ensures that the controller system
External breaker # closed* knows when the external breaker is closed.
Breakers > External breaker # > Feedback > The feedback ensures that the controller system
External breaker # open* knows when the external breaker is open.

Table 3.2 Optional hardware
Breakers > External breaker #> State > External breaker # is

Digital output Continuous Activated when the breaker is open.
open*
Breakers > External breaker # > State > External breaker # is Activated when the breaker is
Digital output Continuous
closed* closed.
*Note: # represents the external breaker number. Up to 4 external breakers can be assigned to a controller.
How to use the externally controlled bus tie breaker

To close the externally controlled bus tie breaker, the operator, CODESYS, or PLC must synchronise the busbar sections and then
close the breaker.
Alarm
More information
See Busbar sections and load sharing, Load sharing alarms, External breaker # position failure for more information
about the alarm.
3.1.3 Externally controlled shore connection
The externally controlled shore connection function allows an externally controlled shore connection to be present. You can also use
this to connect other feeders to the busbar. This breaker is opened or closed by the operator. The DEIF controllers only receive
position feedback from the breaker, and do not control it.
If configured, the externally controlled shore connection is shown on the Supervision page in PICUS. The externally controlled
shore connection has no influence on the busbar sections, or on the operation of any controllers.
Single-line diagram
You can assign a total of up to 4 external breakers (these can be bus tie breakers and/or shore connections) to each controller.
Each external breaker can be assigned to any controller type, anywhere in the single-line diagram.
If the system includes a generator that is not controlled by a PPU 300, include this generator on the single-line diagram as an
externally controlled shore connection.
Additional equipment
You should install a check sync relay or a paralleling relay in the switchboard, to check the synchronisation before closing, for
example, the DEIF CSQ-3 or HAS.
Wiring example
More information
See Wiring examples for controller functions, Breaker wiring in the Installation instructions for an example of
external breaker wiring.
Inputs and outputs

Assign the externally controlled shore connection inputs in the chosen controller under Configure > Input/output. Select the
hardware module, then select the digital input to configure.

Table 3.3 Hardware required in addition to the minimum standard controller wiring
External breaker # closed* knows when the external breaker is closed.
External breaker # open* knows when the external breaker is open.
Table 3.4 Optional hardware
Breakers > External breaker # > State > External breaker # is

open*
Breakers > External breaker # > State > External breaker # is Activated when the breaker is
closed* closed.
*Note: # represents the external breaker number. Up to 4 external breakers can be assigned to a controller.
How to use the externally controlled shore connection

To close the externally controlled shore connection, the operator or PLC must synchronise the busbar sections and then close the
breaker.
Alarm
More information
See Busbar sections and load sharing, Load sharing alarms, External breaker # position failure for more information
about the alarm.
3.1.4 Ring busbar connection
BUS TIE breaker controllers and/or externally controlled bus tie breakers can be installed in system with a ring busbar.
A ring busbar connection is only allowed if there are at least two bus tie breakers in the single-line diagram. These bus tie breakers
can be controlled by BUS TIE breaker controllers and/or externally controlled.
3.2 Busbar section load sharing

3.2.1 Busbar section characteristics
The busbar sections have the following effect:

• GENSET or HYBRID controllers can load share with other GENSET controller(s) in the same busbar section.
◦ GENSET or HYBRID controllers do not attempt to load share with GENSET controllers in different busbar sections.
• GENSET controllers with external set point (network) activated automatically respond to the set point(s) from controllers in the
same busbar section.
◦ The GENSET controllers respond to set point(s) from the SHAFT generator, SHORE connection and/or BUS TIE breaker
controllers in the busbar section.
◦ The GENSET controllers ignore set points from outside the section.
◦ For BUS TIE breaker controllers, separate set points are sent to busbar A and to busbar B.
3.2.2 DEIF network load sharing
The controllers can share the load (both active power (P) and reactive power (Q)) over the DEIF network.

Load sharing over the DEIF network occurs when the load sharing mode is activated in all of the GENSET controllers that must
share the load. The load sharing mode can be activated using digital inputs, Modbus and/or CustomLogic or CODESYS.
The load is shared equally between the GENSET controllers in the same section with load sharing mode activated. The gensets
each run at the same percentage of nominal load. This allows differently sized gensets to share the load.
NOTE Only DEIF controllers can be used for load sharing over the DEIF network. No other vendors' controllers can be used for
load sharing over the DEIF network.
Hardware
Name Type Details
DEIF network Ethernet The DEIF network can be used for equal load sharing (active and/or reactive power).
GOV control Various Required for active power load sharing.
AVR control Various Required for reactive power sharing.
Example
Equal load sharing example
A 1000 kW genset is supplying a load of 900 kW. A 500 kW genset is then connected to the same section. Load sharing is
activated in both GENSET controllers.
Together, the gensets run at 900 kW / (1000 kW + 500 kW) = 0.6 = 60 % of their nominal load. Therefore, the 1000 kW
genset supplies 600 kW, and the 500 kW genset supplies 300 kW.
Alarms that can affect network load sharing

Genset and generator breaker problems can affect load sharing. For example, GB position failure, and a variety of other GENSET
controller alarms can affect load sharing.
The following alarms can affect the DEIF network load sharing:
• External breaker # position failure

• Any bus tie breaker position failure
• Missing all controllers
• Missing controller ID #
• Missing any controller
• Controller ID not configured
• Duplicate controller ID
• Single-line missing / none active
• Different single-line configurations
• Controller not part of system
If any of these alarms are present, load sharing can be unpredictable. You must therefore find and correct the cause.
Switchboard control
If a controller is under switchboard control, then that controller does not control load, and therefore it cannot participate in load
sharing.
3.3 Load sharing alarms

3.3.1 P load sharing failure
This alarm is for genset active power load sharing failure.

The alarm is based on the absolute value of the difference between the measured value and the internal controller set point, as a
percentage of the genset nominal power.
The controller activates the alarm if the difference between the reference and measured values is outside the activation range for
longer than the delay.
This alarm is not activated when the deviation of the error swings in and out of the activation range above and below the set point.
This is because this alarm is only activated when the deviation of the error stays either above or below the activation range for the
delay time.
Regulators > GOV monitoring > P load sharing failure

Parameter Range Default
Set point 0 to 50 % regulation deviation 15 %
Delay 0 s to 1 h 30 s
Enable Not enabled, Enabled Not enabled
Alarm action Warning
3.3.2 Q load sharing failure
This alarm is for genset reactive power load sharing failure.
percentage of the genset nominal reactive power.
The controller activates the alarm if the difference between the reference and measured values is outside the activation range for a
time longer than the delay.
delay time.
Regulators > AVR monitoring > Q load sharing failure


3.3.3 External breaker # position failure
1
Breaker
open
feedback
0
This alarm is for an externally controlled breaker position failure.
1
The alarm is based on the externally controlled breaker feedback signals, which are digital Breaker
closed
inputs to the controller. The alarm is activated if the breaker Closed and Open feedbacks are feedback
both missing for longer than the delay time. The alarm is also activated if the breaker Closed 0
and Open feedbacks are both present for longer than the delay time.
1
Delay
Breaker
position
OK
0
Time
Breakers > [Breaker] monitoring > Position failure

The parameter is only visible if there is an external breaker is on the single-line diagram. This alarm is always enabled. The alarm
action is Warning, Latch enabled.

Delay 0.1 s to 5.0 s 1s
3.3.4 Any bus tie breaker position failure
1 1
This alarm is for any bus tie breaker position Breaker Breaker
failure. open open
feedback feedback
0 0
The alarm is based on the breaker feedback
signals, which are digital inputs to the controller.
1 1
The alarm is activated if the breaker Closed and Breaker Breaker
Open feedbacks are both missing for longer than closed closed
the delay time. The alarm is also activated if the feedback feedback
breaker Closed and Open feedbacks are both 0 0
present for longer than the delay time.
1 1
Delay Delay
The alarm is activated in ALL of the controllers in Breaker Breaker
the sections connected to the bus tie breaker. position position
OK OK
0 0
Time Time
System > Monitoring > Any bus tie breaker position failure
This alarm is always enabled.


Effect of redundant breaker feedback
If redundant breaker feedback is configured for the bus tie breaker, then this alarm only activates when a bus breaker position failure
is detected on each breaker feedback.
3.4 Network alarms

3.4.1 Blackout detection mismatch
Controller B
100
Voltage [%]
This alarm communicates that not all controllers in the section detected the blackout. 0
The alarm is based on the blackout detection for all the controllers in the section. The alarm 100
Controller A
Voltage [%]
is activated when one or more controllers detect a blackout, while one or more controllers in
the same section do not detect a blackout, and this continues for longer than the delay time.
0
This alarm is present in GENSET, HYBRID, SHAFT generator and SHORE connection
controllers.
1
Delay
Blackout
mismatch
0
Time
System > Monitoring > Blackout detection mismatch

Delay 0 s to 1 h 1s
• Not enabled
Enable Not enabled
• Enabled
Action Warning
3.4.2 Missing all controllers
This alarm communicates a network failure.
The alarm is based on the network between the controllers included in the single-line diagram. The alarm is activated when the
controller cannot communicate over the network with any other controllers. If this alarm is activated, the Missing controller ID #
alarms are not activated.
System > Monitoring > Missing all controllers


Action Warning
3.4.3 Missing controller ID #
This alarm communicates a communication failure with one or more controllers in the single-line diagram.

The alarm is activated when a controller is present on the single-line diagram, but the controller displaying the alarm cannot
communicate with it.
The alarm is always enabled, and the alarm action is Warning. The alarm parameters are not visible.
3.4.4 Duplicate controller ID
This alarm communicates that there is another controller with the same Controller ID in the network.
The alarm is based on the network between the controllers included in the single-line diagram. The alarm is activated when the
controller detects another controller with the same Controller ID as itself.
System > Monitoring > Duplicate controller ID


Action Warning
3.4.5 Single-line missing/none active
This alarm communicates that the single-line diagram cannot be read from the controller, or that no single-line diagram is configured
for the controller.
The alarm is always enabled and the action is Warning. The alarm parameters are not visible.
3.4.6 Different single-line configurations
This alarm communicates that different single-line diagrams are present on one or more controllers in the system.
This alarm is activated when a single-line diagram is written to a controller, but not Broadcast to the remaining controllers. The alarm
is always enabled, and the action is Warning. The alarm parameters are not visible.
3.4.7 Controller not part of system
This alarm occurs if the controller has a Controller ID that is not included in the application single-line diagram. Check or configure
the system under Application.
The alarm is always Enabled, and the action is Warning. The alarm parameters are not visible.
Stand-alone applications
You must also create a single-line diagram if the controller is in a stand-alone application. The application single-line diagram has
only that controller.
3.4.8 Missing any controller
This alarm occurs if a controller in the application single-line diagram is missing from the network.
System > Monitoring > Missing any controller


Action Warning

3.4.9 DEIF network redundancy broken
This alarm applies to the DEIF network connection between the controller PCM modules. The alarm is activated when there is no
redundant communication between the controllers. This alarm is based on the single-line diagram and the application
communication. That is, all of the controllers in the network must be included in the application single-line diagram.
Communication > DEIF network > DEIF network redundancy broken

Enable Not enabled, Enabled Enabled
NOTE This alarm must either be Enabled for all the controllers in the system, or Not enabled for all the controllers in the system.
3.4.10 DEIF network top ring redundancy broken
This alarm only applies to top ring topology in a configuration using CODESYS. This alarm applies to the DEIF network connection
between the controller PCM modules in a top ring configuration. The alarm is activated when there is no redundant communication
for the top ring connections between each group of connected controllers. This alarm only applies to top ring topology in a
configuration using CODESYS.
Communication > DEIF network > DEIF network top ring redundancy broken
NOTE This alarm must either be Enabled for all the controllers in the system, or Not enabled for all the controllers in the system.
More information
See the Multi-line 300 CODESYS guidelines for more information about the network restrictions when using a top ring
network configuration.

4. AC configuration and nominal settings
4.1 AC configuration
Phase configuration: AC configuration
This parameter must be the same for all the controllers in the system.
[Source] > AC setup > Phase configuration

Three-phase: The generator and busbar are three-phase, and there

are current measurements on all three phases. Voltage and current
measurement on the neutral phase (N) is optional.
Three-phase (2 CT, L1-L3): The generator and busbar are three-

phase. However, the controller only uses the current measurements on
L1 and L3. Voltage and current measurement on the neutral phase (N)
is optional.
Split-phase L1-L3: The waveforms are offset by a half-cycle (180

degrees) from the neutral wire. This is sometimes called single-phase in
the USA.
Split-phase L1-L2: The waveforms are offset by a half-cycle (180

degrees) from the neutral wire. This is sometimes called single-phase in
• Three-phase
the USA.
• Three-phase (2 CT,
L1-L3)
Split-phase L2-L3 The waveforms are offset by a half-cycle (180
• Split-phase L1-L3 degrees) from the neutral wire. This is sometimes called single-phase in
AC Three-
• Split-phase L1-L2 the USA.
configuration phase
• Split-phase L2-L3
• Single-phase L1 Single-phase L1: The generator and busbar are single-phase. Use the
• Single-phase L2 L1 terminal for the voltage and current measurements (not the L2 or L3
terminals). The current measurement on the neutral phase (N) is
• Single-phase L3
optional.
Single-phase L2: The generator and busbar are single-phase. Use the
L2 terminal for the voltage and current measurements (not the L1 or L3
optional.
Single-phase L3: The generator and busbar are single-phase. Use the
L3 terminal for the voltage and current measurements (not the L1 or L2
optional.
Some of the controller protections are irrelevant in a single-phase

configuration (for example, Current unbalance, Voltage unbalance and
Phase sequence).
More information
See System AC configuration in the Installation instructions for examples of three-phase, single-phase wiring, and
split-phase wiring.

Phase configuration: AC setup
Set this parameter if you do not want the AC measurements that the controller uses for the alarms to be phase-to-phase. This
parameter defines whether the controller uses phase-to-phase or phase-to-neutral voltages.
Measurements from the neutral line can be present for phase-to-phase measurements.
This parameter does not affect the nominal voltages. The nominal voltages are always phase-to-phase voltages.
[Source] > Voltage protections

Phase-phase: The controller uses the phase-to-phase voltages for the alarms (that is,
L1-L2, L2-L3, and L3-L1). See the Installation instructions for a wiring examples
for a phase-to-phase AC configuration.
• Phase-
phase Phase-
AC setup Phase-neutral: The controller uses the phase-to-neutral voltages for the alarms (that is,
• Phase- phase
L1-N, L2-N, and L3-N). Measurements from the neutral line must be present in a phase-
neutral
to-neutral system.
If you select Single-phase L1 (or L2 or L3), you must also select Phase-neutral.
More information
See System AC configuration in the Installation instructions for examples of three-phase, single-phase wiring, and
split-phase wiring.
Phase direction: AC phase rotation

Set this parameter if the AC phase rotation is not L1-L2-L3.
This parameter must be the same in all the controllers in the system.
[Source] > AC setup > Phase direction

L1-L2-L3: The global standard phase rotation is L1-L2-L3. Using an alternative

wiring can lead to confusion, fatal accidents and serious damage to equipment.
Voltage
[V] L1 L2 L3
AC phase • L1-L2-L3
L1-L2-L3 Time [s]
rotation • L1-L3-L2
L1-L3-L2: We do not recommend that you wire the system L1-L3-L2, due to the
potential for confusion. However, this parameter allows the controller to function
correctly even though the generator is wired L1-L3-L2.

Voltage
[V]
L1 L3 L2
Time
[s]
DANGER!
Different phase rotation

Never attempt to connect gensets to the same busbar if they do not have the same phase rotation.
CAUTION
Incorrect parameter use

Do not use this parameter to attempt to correct for incorrect wiring of the controller's AC measurement terminals. Rewire
the terminals correctly.
4.1.1 [Source] and [Busbar] for each controller type
The names used for [Source] and [Busbar] for the AC configuration of each controller type:
Controller type [Source] (ACM3.1 terminals 5 to 8) [Busbar] (ACM3.1 terminals 1 to 4)
GENSET Generator Busbar
HYBRID Inverter Busbar
SHAFT generator Generator Busbar
SHORE connection Shore connection Busbar
BUS TIE breaker Busbar A Busbar B
4.1.2 [Source] AC configuration
Voltage transformer
These parameters relate to the terminals on the ACM3.1.
Set these parameters if there is a voltage transformer on the source's voltage measurement.
If Primary:Secondary ratio is 1, the controller uses the voltage measurement without any correction for a voltage transformer.
The controller does not need information about the voltage transformer type (for example, open delta, star-star, and so on).

[Source] > AC setup > Voltage transformer
Primary 10 V to 150 kV 400 V The voltage transformer primary side (source side) value.
The voltage transformer secondary side (controller side) value.
Phase shift is not allowed in the voltage transformer. The phase angle must be
Secondary 17 to 690 V 400 V NOTE the same on the high and low voltage sides of the voltage measurement
transformer.
The minimum normal operating voltage for the controller is 100 V. However, this
NOTE
range starts at 17 V to allow switchboard tests.
More information
See [Source] AC configuration in the Installation instructions for an example of generator voltage transformer wiring.
Current transformer
These parameters relate to the terminals on the ACM3.1.
CAUTION
Current transformer changes

Changing the current transformer settings, changes the protection range for the over-current and fast over-current
protections.
If you change the current transformer values and the set points for the over-current and fast over-current protections are out of the
set point range, then the Protection set point out of range alarm activates. The alarm action is warning, and cannot be configured.
You must set these parameters for the current transformer on the source's current measurement. These parameters only apply to
the current measurements on L1, L2 and L3.
More information
See ACM3.1 terminal connections and default wiring in the Installation instructions for examples of generator current
transformer wiring.
[Source] > AC setup > Current transformer

Primary 5 to 9000 A 1000 A The current transformer primary side (source side) nominal current.
The current transformer secondary side (controller side) nominal current. You can select
Secondary 1 or 5 A 1A
either 1 A or 5 A.
CT - ACM3.2 - Consumer side

These parameters are only visible if you have an ACM3.2 installed.
More information
transformer wiring.

[Source] > AC setup > CT - ACM3.2 - Consumer side
Primary 5 to 9000 A 1000 A The current transformer primary side nominal current for terminals 1 to 6.
The current transformer secondary side nominal current for terminals 1 to 6.

You can select either 1 A or 5 A.
Defines if the current transformer direction is installed towards or away from

the protected object for terminals 1 to 6.
S1 S2 Protected
Current • Towards prot. obj.
Towards prot. object
reference • Away from prot.
obj. Towards:
dir. obj.
S2 S1 Protected
object
Away:
CT - ACM3.2 - Neutral side

These parameters are only visible if you have an ACM3.2 installed.
More information
transformer wiring.
[Source] > AC setup > CT - ACM3.2 - Neutral side

Primary 5 to 9000 A 1000 A The current transformer primary side nominal current for terminals 7 to 12.
The current transformer secondary side nominal current for terminals 7 to

12. You can select either 1 A or 5 A.
Defines if the current transformer direction is installed towards or away from

the protected object for terminals 7 to 12.
S1 S2 Protected
Current • Towards prot. obj.
Towards prot. object
reference • Away from prot.
obj. Towards:
dir. obj.
S2 S1 Protected
object
Away:
Voltage and frequency OK

The controller uses these parameters to calculate whether the voltage and frequency from the source measurements are OK, so
that the breaker can close.
[Source] > AC setup > Voltage and frequency OK

Voltage
If the voltage and frequency are OK for this time in seconds, then the
and
0 s to 1 h 2s equipment's LED becomes steady green. The breaker is not allowed to
frequency
close before the LED is steady green (that is, not flashing).
OK
Minimum OK The voltage must be above this voltage (as a percent of nominal voltage) for
70 to 100 % 95 %
voltage the breaker to start to synchronise and close.

Maximum OK The voltage must be below this voltage (as a percent of nominal voltage) for
100 to 120 % 105 %
Minimum OK The frequency must above this frequency (as a percent of nominal
70 to 100 % 99 %
frequency frequency) for the breaker to start to synchronise and close.
Maximum OK The frequency must below this frequency (as a percent of nominal
100 to 110 % 101 %
Voltage and frequency OK (blackout start)

For the GENSET, EMERGENCY genset, SHAFT generator or SHORE connection controllers.
During a blackout, the controller uses these parameters to calculate whether the voltage and frequency from the generator
measurements are OK, so that the breaker can close.
[Source] > AC setup > Voltage and frequency OK (blackout start)

Voltage
If the voltage and frequency from the source are OK for this time in
and
0 s to 1 h 2s seconds, then the equipment LED becomes steady green. The breaker is
frequency
not allowed to close before the LED is steady green (that is, not flashing).
OK
Minimum OK The voltage must be above this voltage (as a percent of nominal voltage) for
70 to 100 % 95 %
Maximum OK The voltage must be below this voltage (as a percent of nominal voltage) for
100 to 120 % 105 %
Minimum OK The frequency must above this frequency (as a percent of nominal
70 to 100 % 94 %
Maximum OK The frequency must below this frequency (as a percent of nominal
100 to 110 % 106 %
4.1.3 [Busbar] AC configuration
Voltage transformer
Set these parameters if there are voltage transformers on the busbar voltage measurement.
If Primary:Secondary ratio is 1, the controller uses the voltage measurement without any correction for a voltage transformer.
The controller does not need information about the voltage transformer type (for example, open delta, star-delta, and so on).
[Busbar] > AC setup > Voltage transformer

Primary 10 to 150 kV 400 V The voltage transformer primary side (busbar side) value.
The voltage transformer secondary side (controller side) value.
Secondary 17 to 690 V Note: No phase shift is allowed in the voltage transformer. That is, the phase angle must be
400 V
the same on the high and low voltage sides of the busbar voltage measurement transformer.
Note: The minimum normal operating voltage for the controller is 100 V. However, this range
starts at 17 V to allow switchboard tests.
More information
See [Busbar] AC configuration in the Installation instructions for an example of busbar voltage transformer wiring.

The controller uses these parameters to calculate whether the voltage and frequency from the busbar measurements are OK.
[Busbar] > AC setup > Voltage and frequency OK

If the busbar voltage and frequency are OK for this time in seconds, then the
Voltage and
0 s to 3600 s 0s busbar LED becomes steady green. The breaker is not allowed to close before
frequency OK
the busbar LED is steady green (that is, not flashing).
Minimum OK The voltage must be above this voltage (as a percent of nominal voltage) for the
70 to 100 % 95 %
voltage breaker to start to synchronise and close.
Maximum OK The voltage must be below this voltage (as a percent of nominal voltage) for the
100 to 120 % 105 %
voltage breaker to start to synchronise and close.
Minimum OK The frequency must above this frequency (as a percent of nominal frequency) for
70 to 100 % 98 %
frequency the breaker to start to synchronise and close.
Maximum OK The frequency must below this frequency (as a percent of nominal frequency) for
100 to 110 % 102 %
frequency the breaker to start to synchronise and close.
Blackout detection
[Busbar] > AC setup > Blackout detection
The controller does not allow the breaker to blackout close, or any other blackout
Blackout
0 to 3600 s 0 s actions, unless blackout is still present after this time. All the Blackout delay timers in the
delay
section must run out before any controller can allow a blackout close.
4.1.4 Voltage and frequency as digital outputs
For the [Source] and the [Busbar], you can configure digital outputs with functions for Voltage and frequency OK and No voltage and
frequency. These functions are based on the AC measurements and parameters, and can be useful for troubleshooting.
Digital outputs
Activated if the voltage and frequency from the source are within the
[Source] > State > range specified in:
Digital
Voltage and frequency Continuous
output
OK Configure > Parameters > [Source] > AC setup >
[Source] > State > No Digital Activated if the phase-to-phase voltage from the source is less than
Continuous
voltage and frequency output 10 % of the nominal voltage.
Activated if the voltage and frequency at the [Busbar] are within the
[Busbar] > State > range specified in:
Digital
Voltage and frequency Continuous
output
OK Configure > Parameters > [Busbar] > AC setup >
[Source] > State > No Digital Activated if the phase-to-phase voltage at the [Busbar] is less than
Continuous
voltage and frequency output 10 % of the nominal voltage.

4.1.5 4th current input configuration
Nominal current
Local > 4th current input > Nominal settings > Nominal settings # > Current (I4) *
Nominal setting Nominal setting Nominal setting Nominal setting
Parameter Range Notes
1 2 3 4
The maximum 4th

Nominal (4th) 1 A to 9 kA 867 A 345 A 345 A 345 A current flow during
normal operation.
Current transformer
Set these parameters if there is a current transformer on the 4th current input measurement.
Local > 4th current input > Current transformer (I4)

Primary (I4) 5 A to 9 kA 1 kA The current transformer primary side (measurement side) nominal current.
The current transformer secondary side (controller side) nominal current. Select either 1
Secondary (I4) 1 or 5 A 1A
A or 5 A.
More information
See the Installation instructions for examples of 4th current input wiring for the neutral phase.
4.2 Nominal settings

4.2.1 About the nominal settings
The controller nominal settings are used in a number of key functions. These include power management and protections. Many
protection settings are based on a percentage of the nominal settings.
Each controller can store four sets of nominal settings. You can easily change the active set of nominal settings by changing the
parameter, using a digital input, analogue input, or an external source (for example, Modbus).
Always check that the conditions are safe to change the nominal settings. Changing nominal settings while a genset is running with
a load could lead to unexpected actions. For example, the generator breaker can trip due to an under frequency alarm when
changing the nominal frequency from 50 Hz to 60 Hz.
The nominal settings for the controller are mainly the alternating current (AC) settings. Changing the nominal settings set also
changes the engine nominal speed, and analogue governor and AVR offsets.
More information
See each controller type for more information about the nominal settings and regulation for more information about the
analogue regulator offsets.
This is how the AC measurements on the ACM3.1 module relate to the controller types:

1. [Busbar] voltage measurements
ACM3.1 2. [Source] voltage measurements

• For example: GENSET controller: The voltage at the genset
L1
3. [Source] current measurements
L2
1 • For example: GENSET controller: The current from the genset
L3
4. 4th current measurement
N
• For example: Earth current
L1
L2
2
L3
S1
L1
S2
S1
L2 3
S2
S1
L3
S2
S1
*4 4
S2
Nominal settings inputs and outputs *

Local > Nominal settings > The controller changes the active nominal setting
Controller nominal setting > Digital input Pulse group to the nominal setting group assigned to the
Nominal setting # digital input.
Local > Nominal settings > Activated if the active nominal setting group is the
Controller nominal setting > Digital output Continuous same as the nominal setting group configured to the
Nominal setting # selected output.
The controller changes the active nominal setting

Local > Nominal settings >
Analogue Supervised group to the nominal setting group assigned to the
Controller nominal setting >
input binary input analogue input. The input signal is treated by the
Nominal setting #
controller as a pulse signal.
Local > Nominal settings > The controller outputs a number correlating to the
Analogue
Controller nominal setting > 0 to 3 active nominal setting group. Where Nominal setting
output
Nominal setting # selected 1 is zero.
Parameters
More information
See each controller type for the nominal setting parameters for voltage, current and generator speed (if applicable).
Local > Nominal settings > Controller nominal setting

• Nominal setting 1 The selected nominal setting group for the controller.
Selection Nominal setting 1
• Nominal setting 2

• Nominal setting 3 Changing the nominal setting group using a digital input, analogue input,
• Nominal setting 4 or external command changes this parameter.
4.2.2 Nominal power calculations
Reactive power (Q) nominal

Some alarms and regulators use the nominal reactive power (Q). However, Q is not defined in the controller's nominal settings. The
controller therefore always calculates Q. You can select the method that the controller uses here.
[Source] > Nominal settings > Nominal settings # > Calculation method *
Q nominal calculated: The controller calculates Q nominal based

on S nominal and the power factor.
Reactive • Q nominal calculated

Q nominal Q nominal = P nominal: The controller uses the nominal power
power (Q) • Q nominal = P nominal
calculated as the nominal reactive power.
nominal • Q nominal = S nominal
Q nominal = S nominal: The controller uses the nominal

apparent power as the nominal reactive power.
It is normally not necessary to change these defaults.
No calculation: P nominal has the value entered in the Power (P)

nominal parameter. S nominal has the value entered in the Apparent
• No calculation power (S) nominal parameter.
• P nominal
P or S No
calculated P nominal calculated: The controller uses the nominal apparent power
nominal calculation
• S nominal (S) and nominal power factor (PF) to calculate the nominal power.
calculated
S nominal calculated: The controller uses the nominal power (P) and
the nominal power factor (PF) to calculate the nominal apparent power.
4.2.3 Power transformer
For GENSET or HYBRID controllers, you can optionally use either a step-up or step-down power transformer connected to the
ACM3.1.You can configure the Phase shift, and to use either the nominal voltages or user defined values.
Parameters
Power transformer > Nominal settings # *
Use nominal voltages: The controller uses the

Winding nominal voltage • Use nominal voltages Use nominal
nominal voltage settings.
source • User defined voltages

User defined: The controller uses the values

configured below for voltage settings.
Busbar side winding
10 V to 150 kV 400 V Voltage on the busbar side.
nominal voltage **
Generator side winding

10 V to 150 kV 400 V Voltage on the generator side.
nominal voltage **
Phase shift -180 to 180 deg 0 deg Phase shift value in degrees (°)
** These parameters are only visible if Winding nominal voltage source is set as User defined and written to the
controller.
4.3 AC measurement filters

4.3.1 About AC measurement filters
You can configure average filtering on the primary AC measurements for smooth measurement readout on noisy or oscillating
systems.
The AC filtered measurements are used on the values shown in Live data, CustomLogic, Modbus, CODESYS and other shown
operational values. The internal calculations and protections continue to use the actual values.
AC measurement filters can be configured as:

• No filter - Always show the actual value.
• Averaged : 200 ms - Show an averaged value based on a 200 ms sample.
• Averaged : 800 ms - Show an averaged value based on an 800 ms sample.
4.3.2 AC measurement filters
Local > AC measurement filters > Primary AC measurements

Voltage No filter, Averaged (200 ms), Averaged (800 ms) No filter
Current No filter, Averaged (200 ms), Averaged (800 ms) No filter
Active power No filter, Averaged (200 ms), Averaged (800 ms) No filter
Reactive power No filter, Averaged (200 ms), Averaged (800 ms) No filter
Apparent power No filter, Averaged (200 ms), Averaged (800 ms) No filter
Power factor and cos phi No filter, Averaged (200 ms), Averaged (800 ms) No filter
Frequency from voltage No filter, Averaged (200 ms), Averaged (800 ms) No filter
Frequency from current No filter, Averaged (200 ms), Averaged (800 ms) No filter
4.4 AC measurements as analogue outputs

4.4.1 About AC measurements as analogue outputs
You can configure an analogue output with the function for an alternating current (AC) operating value. This value may be measured
directly or calculated from the AC measurements. The controller then adjusts the analogue output to reflect the AC operating value.

Applications
An analogue output with a function for an alternating current (AC) operating value may be wired to a switchboard instrument, to help
the operator. For example, the total kW from a generator can be displayed.
Alternatively, an analogue output may be wired to a switchboard instrument, to help troubleshooting. For example, the voltage
unbalance between two phases (Busbar | L-L unbalanced [V]) can be displayed.
4.4.2 [Source] AC measurements
Function names
The [Source] AC measurement function names follow these formats:
[Source] > [Physical quantity] > [Equipment] | [Measurement] [[unit]].
Example
Shore busbar > Phase angle > Shore | Phase angle L3-L1 [degrees]
[Source] AC measurement function names for each controller type
Controller type [Source] [Equipment]
GENSET Generator Generator
HYBRID Inverter Inverter
SHAFT generator Generator Generator
SHORE connection Shore busbar Shore
BUS TIE breaker Busbar A Busbar B
[Source] voltage analogue output functions

[Source] > Voltage (V)
Function Details
[Equipment] | L1-N [V AC] The controller outputs the L1-N voltage from the source.
[Equipment] | N [V AC] The controller outputs the N voltage from the source, relative to the star point.
[Equipment] | L1-L2 [V AC] The controller outputs the L1-L2 voltage from the source.
[Equipment] | Positive sequence [V
The controller outputs the magnitude of the positive sequence voltage.
AC]
[Equipment] | Negative sequence [V

The controller outputs the magnitude of the negative sequence voltage.
AC]
The controller outputs the magnitude of the zero sequence voltage from the
[Equipment] | Zero sequence [V AC]
source.
The controller outputs the lowest L-N voltage (that is, for the phase with the
[Equipment] | L-N min. [V AC]
lowest L-N voltage).
The controller outputs the highest L-N voltage (that is, for the phase with the
[Equipment] | L-N max. [V AC]
highest L-N voltage).

Function Details
The controller outputs the L-N unbalanced voltage from the source, relative to the
[Equipment] | L-N unbalanced [V AC]
zero of the star point.
The controller outputs the lowest L-L voltage (that is, for the phases with the
[Equipment] | L-L min. [V AC]
lowest L-L voltage).
The controller outputs the highest L-L voltage (that is, for the phases with the
[Equipment] | L-L max. [V AC]
highest L-L voltage) from the source.
The controller outputs the L-L unbalanced voltage between the phases of the
[Equipment] | L-L unbalanced [V AC]
source.
[Source] frequency analogue output functions

[Source] > Frequency (f) (from voltage)
Function Details
[Equipment] | L1 [Hz] The controller outputs the L1 frequency (based on the voltage measurement).
The controller outputs the frequency of the phase with the lowest frequency (based on the voltage
[Equipment] | Min. [Hz]
measurement).
The controller outputs the frequency of the phase with the highest frequency (based on the
[Equipment] | Max. [Hz]
voltage measurement).
[Equipment] | L1 [Hz] The controller outputs the L1 frequency (based on the current measurement).
The controller outputs the frequency of the phase with the lowest frequency (based on the current
measurement).
current measurement).
[Source] current analogue output functions

[Source] > Current (I)
Function Details
[Equipment] | L1 [A] The controller outputs the L1 current from the source.
[Equipment] | N [A] The controller outputs the N current from the source, relative to the star point.
[Equipment] | Positive sequence
The controller outputs the magnitude of the positive sequence current.
[A]
[Equipment] | Negative sequence

The controller outputs the magnitude of the negative sequence current.
[A]
The controller outputs the magnitude of the zero sequence current from the
[Equipment] | Zero sequence [A]
source.
[Equipment] | Min. [A] The controller outputs the lowest phase current.
[Equipment] | Max. [A] The controller outputs the highest phase current.

Function Details
[Equipment] | Unbalanced nominal The controller outputs the unbalanced current from the source, calculated using
[A] the nominal method.
[Equipment] | Unbalanced average The controller outputs the unbalanced current from the source, calculated using
[A] the average method.
[Source] current - ACM3.2 analogue output functions

[Source] > Current (I) - ACM3.2
Function Details
[Equipment] | L1 (Consumer side)
The controller outputs the L1 current from the consumer side.
[A]

[A]

[A]
[Equipment] | Min (Consumer side)

The controller outputs the lowest phase current from the consumer side.
[A]
[Equipment] | Max (Consumer side)

The controller outputs the highest phase current from the consumer side.
[A]
[Equipment] | L1 (Neutral side) [A] The controller outputs the L1 current from the neutral side.
[Equipment] | Min (Neutral side)
The controller outputs the lowest phase current from the neutral side.
[A]
[Equipment] | Max (Neutral side)

The controller outputs the highest phase current from the neutral side.
[A]
The controller outputs the difference between the consumer and the neutral side
[Equipment] | L1 differential [A]
of the L1 current.
of the L2 current.
of the L3 current.
The controller outputs the lowest difference between the consumer and the
[Equipment] | Min differential [A]
neutral side phase currents.
The controller outputs the highest difference between the consumer and the
[Equipment] | Max differential [A]
neutral side phase currents.
[Equipment] | L1 restraint [A] The controller outputs the L1 restraint current.
[Equipment] | Min. restraint [A] The controller outputs the lowest phase restraint current.
[Equipment] | Max. restraint [A] The controller outputs the highest phase restraint current.
The controller outputs the frequency of the phase with the highest frequency
[Equipment] | Frequency [Hz]
(based on the ACM3.2 current measurements).

[Source] power analogue output functions
[Source] > Power (P)
Function Details
[Equipment] | L1 [kW] The controller outputs the L1 power.
[Equipment] | Total [kW] The controller outputs the total power.
[Equipment] | Min. [kW] The controller outputs the power of the phase with the lowest power.
[Equipment] | Max. [kW] The controller outputs the power of the phase with the highest power.
[Equipment] | Total [%] The controller outputs the total power, as a percentage of the source's nominal power.
The controller outputs the available power for the source in kW. Available power = Nominal
[Equipment] | Available [kW]
power - Total power
The controller outputs the available power for the source, as a percentage of the source's
[Equipment] | Available [%]
nominal power. Available power = Nominal power - Total power
[Source] reactive power analogue output functions

[Source] > Reactive power (Q)
Function Details
[Equipment] | L1 [kvar] The controller outputs the L1 reactive power.
[Equipment] | Total [kvar] The controller outputs the total reactive power.
[Equipment] | Min. [kvar] The controller outputs the reactive power of the phase with the lowest reactive power.
[Equipment] | Max. [kvar] The controller outputs the reactive power of the phase with the highest reactive power.
The controller outputs the total reactive power, as a percentage of the source's nominal
[Equipment] | Total [%]
reactive power.
[Equipment] | Available The controller outputs the available reactive power for the source in kvar. Available
[kvar] reactive power = Nominal reactive power - Total reactive power
The controller outputs the available reactive power for the source, as a percentage of the
[Equipment] | Available [%] source's nominal reactive power. Available reactive power = Nominal reactive power -
Total reactive power
[Source] apparent power analogue output functions

[Source] > Apparent power (S)
Function Details
[Equipment] | L1 [kVA] The controller outputs the L1 apparent power.
[Equipment] | Total [kVA] The controller outputs the total apparent power.
[Equipment] | Min. [kVA] The controller outputs the apparent power of the phase with the lowest apparent power.
[Equipment] | Max. [kVA] The controller outputs the apparent power of the phase with the highest apparent power.
The controller outputs the total apparent power, as a percentage of the source's nominal
[Equipment] | Total [%]
apparent power.

Function Details
The controller outputs the available apparent power for the source in kVA. Available
[Equipment] | Available [kVA]
apparent power = Nominal apparent power - Total apparent power
The controller outputs the available apparent power for the source, as a percentage of the
[Equipment] | Available [%] source's nominal apparent power. Available apparent power = Nominal apparent power -
Total apparent power
[Source] power factor analogue output functions

[Source] > Power factor (PF)
Function Details
[Equipment] | cos phi The controller outputs the power factor, calculated as cos phi.
[Equipment] | Power factor The controller outputs the power factor.
[Source] phase angle analogue output functions

[Source] > Phase angle
Function Details
[Equipment] | Phase angle L1-L2
The controller outputs the phase angle between L1 and L2.
[degrees]

[degrees]

[degrees]
[Equipment] | A-B phase angle L1 The controller outputs the phase angle between L1 of the source and L1 of
[degrees] the busbar.
4.4.3 [Busbar] AC measurements
Function names
The busbar AC measurement function names follow these formats:
[Busbar] > [Physical quantity] > [Equipment] | [Measurement] [[unit]].
Example
Busbar A > Apparent power (S) > Busbar A | Total [kVA]
[Busbar] AC measurement function names for each controller type
Controller type [Busbar] [Equipment]
GENSET Busbar Busbar
HYBRID Busbar Busbar
SHAFT generator Busbar Busbar

Controller type [Busbar] [Equipment]
SHORE connection Ship busbar Busbar
BUS TIE breaker Busbar B Busbar B
[Busbar] voltage analogue output functions

[Busbar] > Voltage (V)
Function Details
[Equipment] | L1-N [V AC] The controller outputs the L1-N voltage from the busbar.
[Equipment] | N [V AC] The controller outputs the N voltage from the busbar.
[Equipment] | L1-L2 [V AC] The controller outputs the L1-L2 voltage from the busbar.
[Equipment] | L2-L3 [V AC] The controller outputs the L2-L3 voltage from the busbar.
[Equipment] | L3-L1 [V AC] The controller outputs the L3-L1 voltage from the busbar
[Equipment] | Positive sequence [V
The controller outputs the magnitude of the positive sequence voltage.
AC]
[Equipment] | Negative sequence [V

The controller outputs the magnitude of the negative sequence voltage.
AC]
[Equipment] | Zero sequence [V AC] The controller outputs the magnitude of the zero sequence voltage.
The controller outputs the lowest L-N voltage (that is, for the phase with the
[Equipment] | L-N min. [V AC]
lowest L-N voltage).
The controller outputs the highest L-N voltage (that is, for the phase with the
[Equipment] | L-N max. [V AC]
highest L-N voltage).
[Equipment] | L-N unbalanced [V AC] The controller outputs the L-N unbalanced voltage.
The controller outputs the lowest L-L voltage (that is, for the phases with the
[Equipment] | L-L min. [V AC]
lowest L-L voltage).
The controller outputs the highest L-L voltage (that is, for the phases with the
[Equipment] | L-L max. [V AC]
highest L-L voltage).
[Equipment] | L-L unbalanced [V AC] The controller outputs the L-L unbalanced voltage.
[Busbar] frequency analogue output functions

[Busbar] > Frequency (f)
Function Details
The controller outputs the frequency of the phase with the lowest frequency (based on the voltage
measurement).
voltage measurement).

[Busbar] phase angle analogue output functions
[Busbar] > Phase angle
Function Details
[Equipment] | Phase angle L1-L2 [degrees] The controller outputs the phase angle between L1 and L2.
4.4.4 4th current input
Assign the AC measurement function to an analogue output.
Analogue outputs
Function Details
Local > 4th current input > Current (I) > The controller outputs the 4th current (based on the 4th current
L4 [A] measurement).
Local > 4th current input > Frequency (f) The controller outputs the 4th frequency (based on the 4th current
> L4 [Hz] measurement).
Local > 4th current input > Power (P) > The controller outputs the 4th power (based on the 4th current
L4 [kW] measurement and the [Busbar] L1 voltage).
Local > 4th current input > Reactive The controller outputs the 4th reactive power (based on the 4th current
power (Q) > L4 [kvar] measurement and the [Busbar] voltage).
Local > 4th current input > Apparent The controller outputs the 4th apparent power (based on the 4th current
power (S) > L4 [kVA] measurement and the [Busbar] voltage).
Local >4th current input > Power factor The controller outputs the power factor, calculated as cos phi (based on
(PF) > L4 | cos phi the 4th current measurement and the [Busbar] voltage).
Local > 4th current input > Power factor The controller outputs the power factor (based on the 4th current
(PF) > L4 | Power factor measurement and the [Busbar] voltage).
Local > 4th current input > Phase angle > The controller outputs the phase angle between the 4th current
L4 [degrees] measurement and the [Busbar] L1 voltage measurement.
4.5 Source AC protections

4.5.1 About AC protections
This section describes the AC protections based on the controller's measurements on the [Source] side of the breaker.
Controller type [Source] [Breaker]
GENSET Diesel genset GB
HYBRID Inverter Breaker
SHAFT generator Shaft generator SGB
SHORE connection Shore connection SCB
BUS TIE breaker Busbar A BTB
The controllers include the following alternating current (AC) protections, according to IEEE Std. C37.2-1996 (R2008).

4.5.2 [Source] over-voltage (ANSI 59)
Protection IEC symbol (IEC60617) ANSI (IEEE C37.2) Operate time
Over-voltage U>, U>> 59 < 100 ms
Alarm present in controller types
GENSET HYBRID SHAFT SHORE connection BUS TIE breaker
● ● ● ● ●
Value
Delay
The alarm response is based on the highest phase-to-phase voltage, or the highest phase-to-
neutral voltage, from the source, as measured by the controller. The phase-to-phase voltage is Set
point
the default.
time
[Source] > Voltage protections > Over-voltage # *

Parameter Range Over-voltage 1 Over-voltage 2
Set point 80 to 120 % of nominal voltage 105 % 115 %
Time delay 0.00 s to 1 h 5.00 s 1.00 s
Enable Not enabled, Enabled Not enabled Not enabled
Latch Not enabled, Enabled Not enabled Enabled
Action Warning Block
NOTE * Where # is 1 or 2.
Default inhibits
Controller type Inhibit(s)
GENSET Generator breaker closed
HYBRID Inverter breaker closed
SHAFT generator Shaft breaker closed
SHORE connection Shore breaker closed
4.5.3 [Source] under-voltage (ANSI 27)
Under-voltage U<, U<< 27 < 100 ms
● ● ● ● ●

Value
Delay
The alarm response is based on the lowest phase-to-phase voltage, or the lowest phase-to- Set
neutral voltage, from the source, as measured by the controller. The phase-to-phase voltage is point
the default.
time
[Source] > Voltage protections > Under-voltage # *

Parameter Range Under-voltage 1 Under-voltage 2
Enable Not enabled, Enabled Enabled Enabled
Default inhibits
• Generator breaker closed

GENSET • Engine not running
• Idle run active
• Inverter breaker closed

HYBRID
• Inverter not running
• Shaft breaker closed

SHAFT generator
• Shaft generator not running
SHORE connection • Shore breaker closed
4.5.4 [Source] voltage unbalance (ANSI 47)
Voltage unbalance (voltage asymmetry) UUB> 47 < 200 ms *
NOTE * This operate time includes the minimum user-defined delay of 100 ms.
● ● - - ●

The alarm response is based on the highest difference between any of the three phase-to-
Value
phase voltage or phase-to-neutral true RMS values and the average voltage, as measured by
the controller. The phase-to-phase voltage is the default. Delay
Set
If phase-to-phase voltages are used, the controller calculates the average phase-to-phase point
voltage. The controller then calculates the difference between each phase-to-phase voltage
and the average voltage. Finally, the controller divides the maximum difference by the average
time
voltage to get the voltage unbalance.
[Source] > Voltage protections > Voltage unbalance

Parameter Range Voltage unbalance
Set point 0 to 50 % 10 %
Delay 0.1 s to 1 h 10.00 s
Action Warning
Default inhibits
GENSET ACM wire break
HYBRID ACM wire break
SHAFT generator ACM wire break
SHORE connection ACM wire break
BUS TIE breaker ACM wire break
Voltage unbalance example
A GENSET controller controls a genset with a nominal voltage of 230 V. The L1-L2 voltage is 235 V, the L2-L3 voltage is
225 V, and the L3-L1 voltage is 210 V.
The average voltage is 223.3 V. The difference between the phase-to-phase voltage and the average is 12.7 V for L1-L2,
2.7 V for L2-L3 and 13.3 V for L3-L1.
The voltage unbalance is 13.3 V/223.3 V = 0.06 = 6.0 %.
4.5.5 Negative sequence voltage (ANSI 47)
Negative sequence voltage 47 < 200 ms *
● ● - - ●

L1
Negative sequence voltages arise when the virtual representation of the phase rotation for an
unbalanced system appears negative.
Negative sequence voltages can occur where there are single phase loads, unbalanced line
short circuits and open conductors, and/or unbalanced phase-to-phase or phase-to-neutral
loads.
L2 L3
The alarm response is based on the estimated phase-to-neutral voltage phasors, as measured
from the source.
[Source] > Voltage protections > Negative sequence voltage

Parameter Range Negative sequence voltage
Set point 1 to 100 % of nominal voltage 5%
Time delay 0.1 s to 1 h 0.5 s
Action Warning
4.5.6 Zero sequence voltage (ANSI 59Uo)
Zero sequence voltage 59Uo < 200 ms *
● ● - - ●
Zero sequence voltages arise when the phases rotation is positive, but the vector zero value
(star point) is displaced. This zero sequence voltage protection can be used instead of using
zero voltage measurement or summation transformers (zero sequence transformers).
This protection is used for detecting earth faults.

-L3
1 -L2
L
The alarm response is based on the estimated phase-to-neutral voltage phasors, as measured
from the source.
[Source] > Voltage protections > Zero sequence voltage

Parameter Range Zero sequence voltage
Set point 1 to 100 % of nominal voltage 5%
Action Warning

4.5.7 Over-current (ANSI 50TD)
Over-current 3I>, 3I>> 50TD < 100 ms
● ● ● ● ●
Value
Delay
The alarm response is based on the highest phase current true RMS values from the source, Set
as measured by the controller. point
time
[Source] > Current protections > Over-current # *

Parameter Range Over-current 1 Over-current 2
Set point Variable. Depends on current transformer settings. 100 % 110 %
Time delay 0.00 s to 1 h 20 s 60 s
Alarm action Warning Trip [Breaker]
4.5.8 Fast over-current (ANSI 50/50TD)
Fast over-current 3I>>> 50/50TD * < 50 ms
NOTE * ANSI 50 applies when the Delay parameter is 0 s.
● ● ● ● ●
Value
Delay
The alarm response is based on the highest phase current true RMS values from the source, Set
as measured by the controller. point
time

[Source] > Current protections > Fast over-current # **
Parameter Range Fast over-current 1 Fast over-current 2
Set point Variable. Depends on current transformer settings. 200 % 300 %
Delay 0.00 s to 1 h 0.00 s 0.00 s
Latch Not enabled, Enabled Enabled Enabled
Action Trip [Breaker] Trip [Breaker]
NOTE ** Where # is 1 or 2.
4.5.9 Current unbalance (ANSI 46)
Current unbalance IUB> 46 < 200 ms *
● ● - - ●
The alarm response is based on the highest difference between any of the three phase current
Value
true RMS values, as measured by the controller. You can choose either the Average method
(ANSI) or the Nominal method to calculate the Current unbalance. Delay
Set
point
time
Average method
The Average method uses the ANSI standard calculation method to determine current unbalance. The controller calculates the
average current for the three phases. The controller then calculates the difference between each phase current and the average
current. Finally, the controller divides the maximum difference by the average current to get the current unbalance.
[Source] > Current protections > Current unbalance (average calc.)

Parameter Range Current unbalance (average calc.) Current unbalance (nominal calc.)
Set point 0 to 100 % 30 % 30 %
Delay 0.10 s to 1 h 10.00 s 10.00 s
Enable Not enabled, enabled Enabled Enabled
Action Warning Warning
Average method example
A GENSET controller controls a genset with a nominal current of 100 A. The L1 current is 80 A, the L2 current is 90 A, and
the L3 current is 60 A.

The average current is 76.7 A. The difference between the phase current and the average is 3.3 A for L1, 13.3 A for L2
and 16.7 A for L3.
The current unbalance is therefore 16.7 A / 76.7 A = 0.22 = 22 %.
Nominal method
The controller calculates the difference between the phase with the highest current, and the phase with the lowest current. Finally,
the controller divides the difference by the nominal current to get the current unbalance.
[Source] > Current protections > Current unbalance (nominal calc.)

Parameter Range Current unbalance (average calc.) Current unbalance (nominal calc.)
Set point 0 to 100 % 30 % 30 %
Delay 0.10 s to 1 h 10.00 s 10.00 s
Enable Not enabled, enabled Enabled Enabled
Nominal method example
A GENSET controller controls a genset with a nominal current of 100 A. The L1 current is 80 A, the L2 current is 90 A, and
the L3 current is 60 A.
The current unbalance is (90 A - 60 A) / 100 A = 0.3 = 30 %.
4.5.10 Directional over-current (ANSI 67)
Directional over-current 67 < 100 ms
● ● - - -
Value
Delay
The alarm response is based on the highest phase current true RMS value, with the direction Set
from the active power from the source, as measured by the controller. point
time
[Source] > Current protections > Directional over-current # *

Parameter Range Directional over-current 1 Directional over-current 2
Set point -300 to 300 % of nominal current 110 % 130 %
Delay 0.00 s to 1 h 0.10 s 0.10 s

For a positive set point, the alarm trigger level is High. When a negative set point is written to the controller, then the controller
automatically changes the alarm trigger level to Low.
4.5.11 Inverse time over-current (ANSI 51)
Inverse time over-current It> 51 -
● ● ● ● ●
t(I)
[s]
The alarm response is based on the highest phase current true RMS
values, based on IEC 60255 part 151, as measured by the controller.
The alarm response time depends on an approximated integral of the

current measurement over time. The integral is only updated when the
measurement is above the activation threshold (indicated in the diagram to
the right by the value 1.1 INOM). See the description below for more details.
Note: The diagram on the right is a simplified representation of this alarm

and does not show the integral over time.
1.1 = Threshold default setting.
INOM 1.1 INOM I [A]
Inverse time over-current calculation method

The controller uses this equation from IEC 60255 to calculate the time that the current measurement may be over the set point
before the inverse time over-current alarm is activated:
k
t(G) = TMS α +c
G -1
GS
where:
t(G) Theoretical operating time constant value of G, in seconds

k, c and α Constants for the selected curve (k and c in seconds, α (alpha) has no unit)
G Measured value, that is, Iphase
GS Alarm set point (GS = Inom * LIM / 100 %)
TMS Time multiplier setting

Parameters
[Source] > Current protections > Inverse time over-current
Three-phase inverse time over-current alarm default parameters
Parameter Range Inverse time over-current

Curve See the table below IEC inverse
Limit (the set point, also known as LIM) 2 to 200 % of nominal current 110 %
Time multiplier setting (TMS) 0.01 to 100.0 1.0
Threshold (GT) 1.0 to 1.3 1.1
k* 0.001 s to 2 min 0.14 s
c* 0.000 s to 1 min 0s
alpha (α, or a) * 0.001 to 1 min 0.02
Latch Not enabled, Enabled Enabled

Alarm action Trip [Breaker]
NOTE * Only used if custom curve is selected.

Standard inverse time over-current curves
The controller includes these standard inverse time over-current curves, in accordance with IEC 60255.
Table 4.1 Parameters for the inverse time over-current curves
Curve name k c alpha (α, or a)
IEC inverse 0.14 s 0s 0.02
IEC very inverse 13.5 s 0s 1
IEC extremely inverse 80 s 0s 2
IEEE moderately inverse 0.0515 s 0.114 s 0.02
IEEE very inverse 19.61 s 0.491 s 2
IEEE extremely inverse 28.2 s 0.1217 s 2
Custom characteristic Customisable Customisable Customisable

Figure 4.1 Standard curve shapes for inverse time over-current, with time multiplier setting (TMS) = 1
1000
time
[s]
100
10
IEC Inverse
IEEE Moderately inverse

1
IEC Very inverse
IEEE Very inverse
IEC Extremely inverse

IEEE Extremely inverse
0.1
1 10 G / Gs 100
Definite time characteristic

GD is the point where the alarm shifts from an inverse curve to a definite time characteristic, as the following graph shows. That is,
after this point, the curve is flat, and a current increase does not have any effect on the alarm response time. In IEC60255, this point
is defined as GD = 20 × GS.

Figure 4.2 Inverse time over-current time characteristic graph
t(G)
[s]
GS GT 2 GS GD
(1.1 GS) G
In this controller, if the rated secondary current of the current measurement transformer is 1 A (that is, the current transformer rating
is -/1 A), then GD = 17.5 × ICT primary for this protection. However, if the rated secondary current of the current transformer is 5 A
(that is, -/5 A), then GD = 3.5 × ICT primary .
Influence of the CT primary current rating on GD example
A current transformer has a primary rating of 500 A and a secondary rating of 5 A. The nominal current of the system is
350 A, and the three-phase inverse time over-current alarm Limit is 100 %.
GD of the inverse time over-current characteristic graph according to IEC60255 is 7000 A.

• GD = 20 × GS = 20 × (Inom × (Limit / 100)) = 20 × (350 × (1 / 1)) = 7000 A
However, the highest GD value where measurements can be made is 1750 A.

• Because the secondary current rating is 5 A, the formula to calculate the measurable GD is GD = 3.5 × ICT primary.
• GD = 3.5 × ICT primary = 3.5 × 500 = 1750 A
If the performance of the inverse time over-current protection is important, DEIF recommends using a current transformer that is
rated for a 1 A secondary current (that is, -/1 A).
4.5.12 Negative sequence current (ANSI 46)
Negative sequence current 46 < 200 ms *
● ● - - ●

Negative sequence currents arise when the virtual representation of the phase rotation for an
unbalanced system appears negative.
L1
Negative sequence currents can occur where there are single phase loads, unbalanced line
short circuits and open conductors, and/or unbalanced phase-phase or phase-neutral loads.
This protection is used to prevent the generator from overheating. Negative sequence currents
produce a magnetic field in the generator counter-rotating to the rotor. This field crosses the
rotor at twice the rotor velocity, inducing double-frequency currents in the field system and in
the rotor body. L2 L3
The alarm response is based on the estimated phase-to-neutral current phasors, from the
source, as measured by the controller.
[Source] > Current protections > Negative sequence current

Parameter Range Negative sequence current
Set point 1 to 100 % of nominal current 20 %
Action Warning
4.5.13 Zero sequence current (ANSI 51Io)
Zero sequence current 51Io < 200 ms *
● ● - - ●
Zero sequence currents arise when the phases rotation is positive, but the vector zero value
(star point) is displaced.
This protection is used for detecting earth faults.

-L3
1 -L2
The alarm response is based on the estimated phase-to-neutral current phasors from the L
source, as measured by the controller.
[Source] > Current protections > Zero sequence current

Parameter Range Zero sequence current
Set point 1 to 100 % of nominal current 20 %
Action Warning

4.5.14 [Source] over-frequency (ANSI 81O)
Over-frequency f>, f>> 81O < 100 ms
● ● ● ● ●
Value
Delay
The alarm response is based on the lowest fundamental frequency (based on phase voltage),
from the source. This ensures that the alarm only activates when all of the phase frequencies Set
point
are above the set point.
time
[Source] > Frequency protections > Over-frequency # *

Parameter Range Over-frequency 1 Over-frequency 2
Set point 80 to 120 % of nominal frequency 105 % 107 %
Default inhibits
GENSET Generator breaker closed
HYBRID Inverter breaker closed
SHAFT generator Shaft breaker closed
SHORE connection Shore breaker closed
4.5.15 [Source] under-frequency (ANSI 81U)
Under-frequency f<, f<< 81U < 100 ms
● ● ● ● ●

Value
Delay
The alarm response is based on the highest fundamental frequency (based on phase voltage), Set
from the source. This ensures that the alarm only activates when all of the phase frequencies point
are below the set point.
time
[Source] > Frequency protections > Under-frequency # *

Parameter Range Under-frequency 1 Under-frequency 2
Default inhibits
• Generator breaker closed

GENSET • Engine not running
• Idle run active

HYBRID
• Shaft breaker closed

SHAFT generator
• Shaft generator not running
SHORE connection • Shore breaker closed
4.5.16 Overload (ANSI 32)
Overload P>, P>> 32 < 100 ms
Value
Delay
The alarm response is based on the active power (all phases), from the source, as measured Set
by the controller. point
time
[Source] > Power protections > Overload #

Parameter Range Overload 1 Overload 2
Set point 0 to 200 % of nominal power 95 % 110 %

Parameter Range Overload 1 Overload 2
4.5.17 Reverse power (ANSI 32R)
Reverse power P<, P<< 32R < 100 ms
● ● ● ● -
Value
Delay
The alarm response is based on the active power (all phases), to the source, as measured by Set
the controller. point
time
[Source] > Power protections > Reverse power # *

Parameter Range Reverse power 1 Reverse power 2
Set point 0 to 200 % of nominal power 8.0 % 15.0 %
Latch Not enabled, Enabled Enabled Enabled
Action Trip [Breaker] Trip [Breaker]
Default inhibits
SHAFT generator Power take home active
4.5.18 Overload reverse power (ANSI 32R)
Overload reverse power 32R < 100 ms

- ● - - -
Value
Delay
The alarm response is based on the active power (all phases), to the source, as measured by Set
the controller. point
time
Inverter > Power protections > Overload reverse power # *

Parameter Range Overload reverse power 1 Overload reverse power 2
Set point 0 to 200 % of nominal power 95.0 % 110.0 %
Time delay 0.00 s to 1 h 30 s 30 s
Action Warning Trip breaker
Table 4.2 Default inhibits
Operating mode PTI (Power take in)

HYBRID controller
Operating mode standby
4.5.19 Reactive power export (ANSI 40O)
Reactive power export (over-excitation) Q>, Q>> 40O < 100 ms
● ● ● ● ●
Value
Delay
The alarm response is based on the reactive power (Q) from the source, as measured and Set
calculated by the controller. point
time

[Source] > Reactive power protections > Reactive power export # *
Parameter Range Reactive power export 1 Reactive power export 2
Set point 0 to 100 % of nominal reactive power 60 % 75 %
4.5.20 Reactive power import (ANSI 40U)
Reactive power import (loss of excitation/under-excitation) Q<, Q<< 40U < 100 ms
● ● ● ● ●
Value
Delay
The alarm response is based on the reactive power (Q) to the source, as measured and Set
calculated by the controller. point
time
[Source] > Reactive power protections > Reactive power import # *

Parameter Range Reactive power import 1 Reactive power import 2
Set point 0 to 150 % of nominal reactive power (Q) 50 % 70 %
4.5.21 Generator differential current protection (ANSI 87G)
Generator stabilised differential current Id> 87G < 55 ms

Generator high set differential current Id>> 87G < 55 ms

The differential current protection detects current faults in the protected
Differential Region 1 Region 2 Region 3
zone between the current transformers. The differential current
current
protection consists of two parts, the stabilised differential current
[%]
protection and the high set differential current protection.
The alarm response of the stabilised differential current protection is

dependent on the operating characteristic and the measured restraint I diff min
and differential currents (evaluation is made per phase). The operating
characteristic separates the operation area (grey) and the restraint area 0 Restraint current [%]
(white) in the figure. The restraint current is the highest value of neutral
and consumer side RMS currents. The differential current is the RMS
value of the fundamental frequency part of the sum (or difference) of the
neutral side and consumer side currents.
The alarm response of the high set differential current protection only
depends on the differential current. That is, the RMS value of the
fundamental frequency part of the sum (or difference) of the neutral side
and consumer side currents.
More information
See [Source] AC configuration for changing the reference direction of the current transformer.
Generator > Current protections > Stabilised differential current

I diff. min. 5 to 100 % of Inom 15 %
Region 1: End 10 to 150 % of Inom 75 %
Region 2: Slope 10 to 50 % of Inom 20 %
Region 2: End 100 to 1000 % of Inom 200 %
Region 3: Slope 30 to 100 % of Inom 75 %
Delay 0 to 60 s 0.00 s
Alarm action Trip generator breaker + AVR + stop engine*
Generator > Current protections > High set differential current

Set point 50 to 1200 % of Inom 800 %
Delay 0 to 60 s 0.00 s
Alarm action Trip generator breaker + AVR + stop engine*
4.5.22 Synchronisation check, including blackout close (ANSI 25)
Synchronisation check (including blackout close) - 25 -

Voltage
For all breakers under power management system (PMS) control, the sync check ensures [V]
that the voltages, frequencies, and phase angles are within the allowed limits before the
controller closes the breaker.
The synchronisation check includes blackout close. That is, if equipment is trying to close a Frequency
breaker to a busbar that does not have voltage, the breaker is allowed to close without [Hz]
synchronisation.
The check is based on the frequency difference, the voltage difference, and the phase Phase
angle across the breaker, as measured by the controller. angle [°]
L1
The synchronisation check does not have an alarm or inhibits. However, if the controller
cannot synchronise within the time allowed, there will be a sync failure alarm. L3 L2
time
The synchronisation check is based on the parameters under:
Breakers > [Breaker] configuration > Synchronisation setting
4.6 Busbar AC protections

4.6.1 [Busbar] over-voltage (ANSI 59)
Over-voltage U>, U>> 59 < 50 ms
● ● ● ● ●
Value
The alarm response is based on the highest phase-to-phase voltage, or the highest phase-to- Delay
neutral voltage, from the busbar, as measured by the controller. Set
point
For the BUS TIE breaker controller, these voltages are measured on busbar B.
time
[Busbar] > Voltage protections > Over-voltage # *

Parameter Range Busbar over-voltage 1 Busbar over-voltage 2
Delay 0.00 s to 1 h 5.00 s 3.00 s
Action Warning Trip [Breaker]

Default inhibits
GENSET • Generator breaker open
HYBRID • Inverter breaker open
SHAFT generator • Shaft breaker open
SHORE connection • Shore breaker open
4.6.2 [Busbar] under-voltage (ANSI 27)
Under-voltage U<, U<< 27 < 50 ms
● ● ● ● ●
Value
The alarm response is based on the lowest phase-to-phase voltage, or the lowest phase-to- Delay
neutral voltage, from the busbar, as measured by the controller. Set
point
For the BUS TIE breaker controller, these voltages are measured on busbar B.
time
[Busbar] > Voltage protections > Under-voltage # *

Parameter Range Busbar under-voltage 1 Busbar under-voltage 2
Delay 0.00 s to 1 h 5.00 s 3.00 s
Default inhibits
• Generator breaker open

GENSET
• ACM wire break
• Inverter breaker open

HYBRID
• ACM wire break

• ACM wire break
• Shore breaker open

SHORE connection
• ACM wire break
BUS TIE breaker • ACM wire break
4.6.3 [Busbar] voltage unbalance (ANSI 47)
Voltage unbalance (voltage asymmetry) UUB> 47 < 200 ms *
● ● ● ● ●
The alarm response is based on the highest difference between any of the three busbar phase-
to-phase voltage or phase-to-neutral true RMS values and the average voltage, as measured
by the controller. The phase-to-phase voltage is the default. Value
Delay
If phase-to-phase voltages are used, the controller calculates the average phase-to-phase Set
voltage. The controller then calculates the difference between each phase-to-phase voltage point
and the average voltage. Finally, the controller divides the maximum difference by the average
voltage to get the voltage unbalance. See the example.
time
For the BUS TIE breaker controller, these are the voltages measured on busbar B.
[Busbar] > Voltage protections > Voltage unbalance

Parameter Range Busbar voltage unbalance
Set point 0 to 50 % of nominal voltage 10 %
Delay 0.1 s to 1 h 10.0 s
Action Warning
Default inhibits
GENSET ACM wire break
HYBRID ACM wire break
SHAFT generator ACM wire break
SHORE connection ACM wire break
BUS TIE breaker ACM wire break

Busbar voltage unbalance example
The busbar has a nominal voltage of 230 V. The L1-L2 voltage is 235 V, the L2-L3 voltage is 225 V, and the L3-L1 voltage
is 210 V.
The average voltage is 223.3 V. The difference between the phase-to-phase voltage and the average is 12.7 V for L1-L2,
2.7 V for L2-L3 and 13.3 V for L3-L1.
The busbar voltage unbalance is 13.3 V / 223.3 V = 0.06 = 6 %
4.6.4 [Busbar] over-frequency (ANSI 81O)
Over-frequency f>, f>> 81O < 50 ms
● ● ● ● ●
Value
The alarm response is based on the lowest fundamental frequency (based on phase voltage),
Delay
from the busbar. This ensures that the alarm only activates when all of the phase frequencies
are above the set point. Set
point
For the BUS TIE breaker controller, this is the frequency measured on busbar B.
time
[Busbar] > Frequency protections > Over-frequency # *

Parameter Range Busbar over-frequency 1 Busbar over-frequency 2
Delay 0.00 s to 1 h 5.00 s 8.00 s
Default inhibits
GENSET • Generator breaker open
HYBRID • Inverter breaker open
SHORE connection • Shore breaker open

4.6.5 [Busbar] under-frequency (ANSI 81U)
Under-frequency f<, f<< 81U < 50 ms
● ● ● ● ●
Value
The alarm response is based on the highest fundamental frequency (based on phase voltage), Delay
from the busbar. This ensures that the alarm only activates when all of the phase frequencies Set
are below the set point. point
For the BUS TIE breaker controller, this is the frequency measured on busbar B.
time
[Busbar] > Frequency protections > Under-frequency # *

Parameter Range Busbar under-frequency 1 Busbar under-frequency 2
Delay 0.00 s to 1 h 10.00 s 5.00 s
Table 4.3 Default inhibits
• Generator breaker open

GENSET
• ACM wire break
• Inverter breaker open

HYBRID
• ACM wire break
• Shaft breaker open

SHAFT generator
• ACM wire break
• Shore breaker open

SHORE connection
• ACM wire break
BUS TIE breaker • ACM wire break
4.7 Other AC protections

4.7.1 Lockout relay (ANSI 86)
The lockout relay ensures that the alarm action continues for an alarm, until the lockout relay is reset. The controller can function as
a lockout relay for alarm conditions which have the Latch parameter enabled. The protection is in effect until the alarm condition is
cleared, the alarm acknowledged and the latch is reset.

The lockout relay applies to all latched alarms, and does not activate a specific alarm or have any inhibits.
Lockout relay 86 Dependent on protection
1. Alarm condition
t1
2. Controller protection active
3. Alarm
4. Acknowledge alarm
5. Latch
6. Clear latch (reset)
1. Alarm condition
• When an alarm condition occurs, an alarm-dependent delay timer activates.
• If the alarm condition occurs for longer than the delay timer, the protection activates.
2. Controller protection active
• If a latch is enabled for the protection, the latch activates when the controller protection activates.
• The protection will remain active until the latch is reset, even if the alarm condition clears.
3. Alarm
• The alarm output, for example, an alarm horn, remains active until the alarm is acknowledged.
• When the alarm is acknowledged, the protection remains active if a latch is enabled.
4. Acknowledge alarm
• The alarm can be acknowledged while the alarm condition is still active, or when the alarm condition has cleared.
• If a latch is active and the alarm is acknowledged after the alarm condition has cleared, the protection will remain active.
5. Latch
• If a latch is enabled for the alarm, the alarm latch will activate when the controller protection activates.
• While the latch is active, the alarm protection will also be active.
6. Clear latch (reset)
• The alarm latch can only be removed once the alarm condition is no longer active and the alarm is acknowledged.
• The protection will remain active until the latch is cleared.
For most alarms, a latch can be Enabled as a parameter under [Alarm location] > [Alarm] > Latch
[Alarm location] is the location of the alarm parameters, for example, Busbar > Voltage protections.

[Alarm] is the alarm name.
NOTICE
Not powered controller de-energises relays

If the controller is not powered, the controller relays de-energise.
NOTICE
Latched alarms do not trip breaker again if breaker manually operated

Alarms that are latched do not trip the breaker again if the breaker is closed manually by the operator.
Optional: Configuring an external lockout relay

An external lockout relay with manual reset functionality can be connected to a digital output. The digital output activates if a specific
alarm condition is triggered by the controller. For example: Under Configure > Input/output, a digital output can be
configured to activate if Any latched alarm is present. When the digital output is activated, the lockout relay connected to it is also
activated. If the alarm condition is cleared on the controller, an operator must manually reset the lockout relay.
When the controller is connected to an external lockout relay, the controller interfaces with the lockout relay. When the controller
interfaces with an external lockout relay, the controller is not seen as the lockout relay for the system.
4.7.2 Earth inverse time over-current (ANSI 51G)
Earth inverse time over-current 51G -
t(I)
[s]
The alarm response is based on the ground current, as measured by the
4th current measurement filtered to attenuate the third harmonic (at least 18
dB). A 128 tap FIR low pass filter is applied. The busbar frequency, as
measured by the controller (f0), is used as the cutoff frequency. The filter
has 0 dB attenuation at f0, and 33 dB attenuation at 3 × f0.

measurement is above the activation threshold.
Note: The diagram on the right is a simplified representation of this alarm.

The diagram does not show the integral over time.
INOM 1.1 INOM I [A]
Wiring
You must wire the 4th current measurement on ACM3.1 (terminals 15,16) to measure the ground current.
The Earth inverse time over-current and Neutral inverse time over-current alarms each require the 4th current measurement. You
therefore cannot have both of these protections at the same time.

Local > 4th current input > Earth inverse time over-current
Earth inverse time
Parameter Range
over-current
Curve See the reference IEC Inverse
Limit (the set point, also known as LIM) 2 to 200 % of nominal current (4th current input) 10 %

Threshold 1.0 to 1.3 1.1
k* 0.001 s to 2 min 0.14 s
c* 0 s to 1 min 0s
alpha (α, or a) * 0.001 to 1 0.02

Alarm action Trip breaker
More information
See Inverse time over-current (ANSI 51N) for the calculation method, the standard curves, and information about the
definite time characteristic.
4.7.3 Neutral inverse time over-current (ANSI 51N)
Neutral inverse time over-current 51N -
t(I)
[s]
The alarm response is based on the unfiltered (except for anti-aliasing)

neutral current, as measured by the 4th current measurement.

measurement is above the activation threshold.
Note: The diagram on the right is a simplified representation of this alarm.

The diagram does not show the integral over time.
INOM 1.1 INOM I [A]
Wiring
You must wire the 4th current measurement on ACM3.1 (terminals 15,16) to measure the neutral current.
More information
See Wiring examples for controller functions in the Installation instructions for an example of how to wire the neutral
current measurement.

The Earth inverse time over-current and Neutral inverse time over-current alarms each require the 4th current measurement. You
therefore cannot have both of these protections at the same time.
Local > 4th current input > Neutral inverse time over-current
Neutral inverse time
Parameter Range
over-current
Curve See the reference IEC Inverse
Limit (the set point, also known as LIM) 2 to 200 % of nominal current (4th current input) 30 %

Threshold 1.0 to 1.3 1.1
k* 0.001 s to 2 min 0.14 s
c* 0 s to 1 min 0s
alpha (α, or a) * 0.001 to 1 0.02

Alarm action Trip [Breaker]
More information
See Inverse time over-current (ANSI 51) for the calculation method, the standard curves, and information about the definite
time characteristic.

5. Alarms and protections
5.1 Non-essential loads

5.1.1 NEL # over-current
These non-essential load trips (NELs) are for over-current protection. The over-current trip may,
for example, be activated by inductive loads and an unstable power factor (PF < 0.7), which Value
increase the current. Delay
Set
The trip response is based on the highest phase current true RMS values from the source, as point
measured by the controller.
time
By default, up to three NEL trips are available.
Non-essential load trip > Trip # > Over-current *

These parameters are only visible if the non-essential loads are configured on the application single-line diagram.
Parameter Range Trip 1 > Over-current Trip 2 > Over-current Trip 3 > Over-current
Set point 50 to 200 % of nominal current 100 % 100 % 100 %
Delay 0.1 s to 1 h 5.0 s 8.0 s 10.0 s
Enable Not enabled, Enabled Not enabled Not enabled Not enabled
Action ** Warning Warning Warning
NOTE * where # is 1 to 3.
** The NEL function also trips NEL #. You cannot reconnect the NEL until the alarm is deactivated. The alarm action cannot
be changed.
Inhibits: The trips are inhibited if the breaker to the busbar is open.
5.1.2 NEL # under-frequency
These NEL trips are for busbar under-frequency protection. Value

Delay
Set
The trip response is based on the lowest frequency in the 3-phase voltage from the busbar, as
point
By default, up to three NEL trips are available. time
Non-essential load trip > Trip # > Under-frequency *

Parameter Range Trip 1 > Under-frequency Trip 2 > Under-frequency Trip 3 > Under-frequency
70 to 100 % of nominal
Set point 95 % 95 % 95 %
frequency
Delay 0.1 s to 1 h 5.0 s 8.0 s 10.0 s

Parameter Range Trip 1 > Under-frequency Trip 2 > Under-frequency Trip 3 > Under-frequency
be changed.
5.1.3 NEL # overload
These non-essential load trips (NEL) are for overload protection. Tripping the NEL groups
reduces the active power load at the busbar, and thus reduce the load percentage on all the
running gensets. This can prevent a possible blackout at the busbar due to overloading the Value
running gensets. Delay
Set
The alarm response is based on the active power (all phases), supplied by the source, as point
time
By default, up to six NEL trips are available. You can configure Overload 1 for three overload
trips, and Overload 2 for three fast overload trips.
Non-essential load trip > Trip # > Overload 1 *

Parameter Range Trip 1 > Overload 1 Trip 2 > Overload 1 Trip 3 > Overload 1
Set point 10 to 200 % of nominal power 100 % 100 % 100 %
Delay 0.1 s to 1 h 5.0 s 8.0 s 10.0 s
be changed.
Non-essential load trip > Trip # > Overload 2 *
Parameter Range Trip 1 > Overload 2 Trip 2 > Overload 2 Trip 3 > Overload 2
Set point 10 to 200 % of nominal power 110 % 110 % 110 %
Delay 0.1 s to 100 s 1.0 s 1.0 s 1.0 s
be changed.

5.1.4 NEL # reactive overload
These non-essential load trips (NELs) are for reactive overload protection. Tripping the NELs
reduces the reactive power load at the busbar, and thus reduce the load percentage on all the Value
running gensets. This can prevent a possible blackout at the busbar due to overloading the
Delay
running gensets.
Set
point
The alarm response is based on the reactive power (all phases), supplied by the source, as
time
By default, up to three NEL trips are available.
Non-essential load trip > Trip # > Reactive overload *

Trip 1 > Reactive Trip 2 > Reactive Trip 3 > Reactive

Parameter Range
overload overload overload
10 to 200 % of nominal reactive

Set point 110 % 110 % 110 %
power
Delay 0.1 s to 1 h 5.0 s 8.0 s 10.0 s
be changed.
5.2 General system alarms

5.2.1 System not OK
This alarm communicates that there is a problem with one of the hardware modules in the
controller.
1
The system is okay if all of the following conditions are met: Alarm >
Status OK
• All the modules in the rack are sending an OK signal.
• All the modules in the rack have a software version that is compatible with the 0
Time
controller application software.
• All the modules required for a specific controller type are present in the rack.
• The alternating current module has received all the required settings (wiring mode,
nominal settings, and so on) at start-up.
• The controller software has started and is running OK.
By default, the Status OK alarm output is configured to terminals 3 and 4 of the power
supply module of the controller. This configuration cannot be removed or changed.
Local > Monitoring > System not OK


Action Warning
More information
See Alarm status digital outputs for how the Status OK alarm is configured.
5.2.2 Critical process error
The alarm communicates that the controller's critical communication and/or processing are disrupted.
The alarm action is Warning and the alarm is always enabled. The controller also activates the System not OK alarm. The alarm
parameters are not visible.
It is unlikely that customers will see this alarm. If you do see this alarm take the following actions:
1. Restart the controller.
2. If restarting does not help, update the controller software to the latest version.
3. Contact DEIF.
5.2.3 Configuration update delayed
The controller activates this alarm if an operator and/or external equipment is changing the controller configuration too quickly. For
example, a programming error on a PLC can create a storm of Modbus changes.
To protect the controller's internal memory, the excess configuration changes are not stored immediately. The delay can be up to 10
minutes. If the controller loses power during this time, the changes may be lost.
The alarm is always enabled. The alarm action is Warning. The alarm is automatically acknowledged when the configuration
changes are stored. The alarm parameters are not visible.
5.2.4 Not under remote control
Local > Mode > Not under remote control

This alarm communicates that the controller is not under remote control (that is, the controller is under local control).
This alarm ignores switchboard control. If the controller is in remote control when switchboard control is activated, then the alarm is
active.

Delay 0 s to 1 h 1s
Action Warning
5.2.5 Fieldbus connection missing
This alarm is for the internal communication between the controller and its extension units. If there is a redundancy connection, this
alarm communicates that an Ethernet connection is missing or broken.
The alarm is always enabled, and the alarm action is Block. The alarm parameters are not visible.

5.2.6 Fieldbus conflict
This alarm is for the internal communication between the controller and its extension units. If there is a hardware change or
hardware failure, this alarm communicates that the hardware configuration does not match the previous hardware configuration. Use
Configure > Fieldbus configuration in PICUS to correct the hardware configuration.
The alarm is always enabled, and the alarm action is Block. The alarm parameters are not visible.
5.2.7 Controller ID not configured
This alarm communicates that the user has never configured the Controller ID. When this alarm is active, the controller is always
under Switchboard control.
5.2.8 Trip AVR output not configured
This alarm communicates that there is an alarm configured that has a Trip AVR alarm action, but the Trip AVR output is not
configured.
The Trip AVR digital output can be configured under Generator > AVR > Trip AVR on the Input/output page. Alternatively the
output can be configured using Modbus.
5.2.9 NTP server not connected
The alarms NTP server 1 not connected, NTP server 2 not connected, or No NTP server(s) connected are activated when the NTP
server(s) are configured, but the controller did not connect to the server(s) within 10 minutes after the configuration is written to the
controller. These alarms are triggered if the controller network cannot access the NTP server(s), or if the NTP server(s) are not set
up correctly.
Configure the parameters for these alarms under Communication > NTP. The alarm action is always Warning and cannot be
changed.
5.2.10 NTP server no response
The alarms NTP server 1 no response, NTP server 2 no response, or No NTP server time synchronisation are activated when the
controller was successfully connected to NTP server(s), but the server(s) did not respond to the controller for up to 22 minutes.
Configure the parameters for these alarms under Communication > NTP. The alarm action is Warning and cannot be changed.
5.2.11 Live power detected (emulation)
This alarm informs the operator that live power was detected during emulation.
The controller activates this alarm if Test functions > Emulation > Emulation active is Enabled and live power is
detected on ACM3.1.
The alarm is always enabled. You cannot see or change the alarm parameters.
5.2.12 Emulation disabled (live power)
This alarm informs the operator that emulation has been disabled (because live power was detected during emulation).

The controller activates this alarm if Test functions > Emulation > Emulation active is Enabled and live power is
detected on ACM3.1. The alarm changes the emulation parameter to Not enabled on all controllers in the system.
5.3 Custom input alarms

5.3.1 Digital input (DI) alarms
You can configure custom alarms for any of the controller digital inputs (DI). When the digital input (DI) is triggered the alarm
becomes active in the system and the controller does the associated alarm action.
HIGH input trigger example Digital

input
t1 t2
Select High for the alarm trigger level.
HIGH
By default, a digital input (DI) is normally open, and the
alarm is activated if the digital input is closed for longer than
the Time delay.
LOW
Time
LOW input trigger example Digital

input
t1 t2
Alternatively, configure the digital input (DI) so that the alarm
is activated if the digital input is open for longer than the HIGH
Time delay.
Select Low for the alarm trigger level.
LOW
Time
Input/output > [Hardware module] > DI > Alarms

Name Text - Name for the alarm
Trigger level Low, High - Whether the alarm is triggered at High or Low.
Auto acknowledge Not enabled, Enabled Not enabled
Latch Not enabled, Enabled Not enabled
Action Selectable list -
Inhibit(s) Selectable list -
5.3.2 Analogue input (AI) alarms
You can configure custom alarms for the controller analogue inputs (AI). When the analogue input alarm set point is exceeded for
longer than the delay time, then the alarm becomes active in the system and the controller does the associated alarm action.
Configure the analogue input (AI) sensor setup (including the scale) before creating an alarm for the input. The configuration of the
analogue input determines the configuration of the alarm. For example, the analogue input can be configured as a 0 to 20 mA
current input that corresponds to a percentage. The analogue input alarm is then configured for a certain percentage set point.

More information
See Analogue input characteristics and configuration for how to configure sensor failure alarms.
Input/output > [Hardware module] > AI > Alarms

Name Text Name for the alarm
Trigger level Low, High High Whether the alarm is triggered at High or Low.
Auto acknowledge Not enabled, Enabled Not enabled
Set point Varies - Depends upon selected input scale unit
Reset hysteresis Varies - Depends upon selected input scale unit
Action Selectable list -
Inhibit(s) Selectable list -
Low oil pressure analogue input alarm example
Configure the analogue input for the oil pressure sensor under Configure > Input/output > [Hardware module] > AI >
Sensor setup. In this example, the sensor provides a 4 to 20 mA signal, which corresponds linearly to 0 to 10 bar.
Configure the sensor as follows:

Sensor = 0 to 25 mA
Units = bar
Select an unused Custom input scale #.
Input (mA), Minimum = 4, Maximum = 20
Output (bar), Minimum = 0, Maximum = 10
Create two points for the curve: 4 mA and 0 bar; and 20 mA and 10 bar.
Configure the alarm as follows:

Name = Low oil pressure
Trigger level = Low
Enable = Enabled
Delay = 0.1 seconds
Set point = 1 bar
Action = Trip generator breaker and shutdown engine
Inhibit = Engine not running
If the engine is running, but the oil pressure falls below 1 bar (this corresponds to an analogue input of less than 5.6 mA)
for more than 0.1 seconds, then the alarm is activated. The controller trips the breaker and shuts down the engine.
5.4 General hardware module alarms

5.4.1 Software mismatch on hardware module(s)
This alarm is activated if any of the hardware modules in the controller have a software version installed that differs from the
expected version. The alarm action is Warning. This alarm activates the System not OK alarm. The alarm parameters are not visible.
NOTE This alarm is only activated if you install a replacement hardware module in the controller. The new module can have
different software to the rest of the controller. Reinstall or update the controller firmware to fix the problem.
5.4.2 Required I/O card(s) not found
This alarm communicates that some of the default hardware modules for the controller type were not found. The alarm action is
Warning.

If one or more default controller hardware modules are missing, then this alarm is activated on start-up. The controller also activates
the System not OK alarm. The alarm parameters are not visible.
5.5 Power supply module PSM3.1

5.5.1 PSM3.1 1 supply voltage low alarm
Value
This default alarm is for power supply voltage protection. Delay
Set
point
The alarm is based on the power supply voltage measured by the PSM. The alarm is activated
when the power supply voltage is less than the set point for the delay time.
time
Hardware > PSM3.1 1 > Low voltage alarm

Parameter Range PSM3.1 1 supply voltage low
Set point 8.0 to 32.0 V DC 18.0 V DC
Delay 0 s to 1 h 1.0 s
Action Warning
5.5.2 PSM3.1 1 supply voltage high alarm
Value
Set
The alarm is based on the power supply voltage measured by the PSM. The alarm is activated point
when the power supply voltage exceeds the set point for the delay time.
time
Hardware > PSM3.1 1 > High voltage alarm

Parameter Range PSM3.1 1 supply voltage high
Action Warning

5.6.1 PSM3.2 1 supply voltage low alarm
Value
Set
point
The alarm is based on the power supply voltage measured by the PSM. The alarm is activated
time
Hardware > PSM3.2 1 > Low voltage alarm

Parameter Range PSM3.2 1 supply voltage low
Action Warning
5.6.2 PSM3.2 1 supply voltage high alarm
Value
Set
The alarm is based on the power supply voltage measured by the PSM. The alarm is activated point
time
Hardware > PSM3.2 1 > High voltage alarm

Parameter Range PSM3.2 1 supply voltage high
Action Warning
5.7 Alternating current module ACM3.1

5.7.1 [Source]/[Busbar] L1-L2-L3 wire break
Controller types: GENSET, HYBRID, SHAFT generator, SHORE connection and BUS TIE breaker controllers

These alarms alert the operator to a voltage measurement failure: L1 L2 L3
• [Source] L1-L2-L3 wire break
• [Busbar] L1-L2-L3 wire break
Generator
The controller only activates the alarm when all of these conditions are met:
voltage
• The generator breaker is closed
• Voltage is detected by one set of ACM voltage measurements
• No voltage is detected on all three phases for the other set of ACM voltage L1 L2 L3
measurements
Busbar
voltage
1
Busbar
L1-L2-L3
Wire break
0
Time
[Source] > AC setup > Multiple phase wire break

Action Warning
[Busbar] > AC setup > Multiple phase wire break

Action Warning
5.7.2 [Source]/[Busbar] L# wire break
Controller types: GENSET, HYBRID, SHAFT generator, SHORE connection and BUS TIE breaker controllers

These alarms alert the operator to a measurement failure on a phase: L1 L2 L3
• [Source] L1 wire break
Generator
voltage
• [Busbar] L1 wire break
• [Busbar] L2 wire break
• [Busbar] L3 wire break L1 L2 L3
The controller only activates the alarm when all of these conditions are met: Busbar
voltage
• No voltage is detected on one of the phases for the other set of ACM voltage
measurements
1
Busbar
L1
Wire break
0
Time
[Source] > AC setup > L# wire break *

Action Warning
[Busbar] > AC setup > L# wire break *

Action Warning
5.7.3 ACM 1 data is missing
Applicable to ACM3.1 and ACM3.2.
The alarm communicates that the data protocol in the alternating current module (ACM) is not correct.
This can occur when the ACM software version is incorrect. Contact DEIF support if you see this error.
The alarm action is Warning, and the alarm is always enabled. The alarm parameters are not visible.
5.7.4 ACM 1 protections not running
This alarm communicates that the configuration data for protections and measurements are not correct in the controller alternating
current module (ACM).

This alarm can occur if the ACM has unintentionally restarted, or if the ACM configuration data was not received within the time limit.
Contact DEIF support if you see this error.
The alarm action is Warning, and the alarm is always enabled. The alarm parameters are not visible.
5.8 Engine interface module EIM3.1

5.8.1 EIM3.1 # supply voltage low or missing alarm
Value
This default alarm is for auxiliary power supply voltage protection. Delay
Set
point
The alarm is based on the power supply voltage measured by the EIM. The alarm is activated
time
Hardware > EIM3.1 # > Low voltage alarm *

Parameter Range EIM3.1 # supply voltage low or missing
Action Warning
NOTE * Where # is the module number.
5.8.2 EIM3.1 # supply voltage high alarm
Value
Set
The alarm is based on the power supply voltage measured by the EIM. The alarm is activated point
time
Hardware > EIM3.1 # > High voltage alarm *

Parameter Range EIM3.1 # supply voltage high
Action Warning

5.8.3 Magnetic pickup wire break alarm
[RPM]
This alarm is for magnetic pickup wire break. If the engine is running but there is no
pulse for 2 seconds, then the controller monitors the cable. If there is no change during
COM
the alarm delay time, then the controller activates the alarm. 2s 10 s
time
Engine > Running detection > Magnetic pickup wire break

Parameter Range Magnetic pickup wire break
Action Warning
Inhibit Engine not running
NOTICE
Third part equipment also connected to magnetic pickup

If third party equipment is connected to the magnetic pickup unit, the wire break detection might not work.
5.8.4 EIM3.1 # relay 4 wire break alarm
This alarm is for EIM3.1 # relay 4 (terminals 9,10) wire break detection (where # is 1 to
3). The wire break monitoring is only active when the relay is de-energised. Hardware:
EIM 3.1 *
Relay 4 can be configured for any digital output function, for example, Stop coil. This
alarm then acts as stop coil wire break detection.
Hardware > EIM3.1 # > Relay 4 supervision *

Parameter Range EIM3.1 # relay 4 wire break
Delay 0 s to 1 h 1s
Action Warning
5.8.5 EIM3.1 safety shutdown still has control
This alarm activates if the shutdown has been executed by the EIM3.1 hardware module, and manual reset is not set high after, or if
an alarm is running then application is started up again.
5.8.6 EIM3.1 safety shutdown configuration is not correct
Activates if the required configuration for active standalone is not correct.

More information
See EIM3.1 standalone for the required configuration.
5.9 Governor and AVR module GAM3.2

5.9.1 GAM3.2 1 status not OK
This alarm communicates that the GAM3.2 cannot perform stand-alone regulation. This may be due to incomplete or incorrect
configuration.
The alarm is always enabled, and the alarm action is Warning. The alarm parameters are not visible.
5.9.2 GAM3.2 1 supply voltage low or missing
Value
Set
point
The alarm is based on the power supply voltage measured by the GAM. The alarm is activated
time
Hardware > GAM3.2 1 > Low voltage alarm

Parameter Range GAM3.2 1 supply voltage low or missing
Action Warning
5.9.3 GAM3.2 1 supply voltage high alarm
Value
Set
The alarm is based on the power supply voltage measured by the GAM. The alarm is activated point
time
Hardware > GAM3.2 1 > High voltage alarm

Parameter Range GAM3.2 1 supply voltage high
Action Warning

5.10 Processor and communication module PCM3.1
5.10.1 Controller temperature too high
This is a built-in alarm for the controller internal temperature, as measured on PCM3.1. The alarm is triggered when the controller
internal temperature is higher than 80 °C (176 °F). The alarm action is Warning. The alarm parameters are not visible.
If the controller operates at internal temperatures higher than 80 °C (176 °F), the performance and the lifetime of the controller is
significantly reduced.
5.10.2 PCM clock battery failure alarm
The PCM clock battery failure alarm is activated when the battery in PCM3.1 needs to be replaced. The alarm action is Warning.
The alarm parameters are not visible.
More information
See the Operator's manual for how to change the battery.
5.10.3 Network protocol incompatible
The alarm communicates that the controller has a different network protocol from the rest of the controllers in the system.
The alarm can for example activate when a controller with a newer software version than the other controllers is added to the
network. This includes different DEIF products in the same system, for example, PPU 300 controllers and PPM 300 controllers.
Update all the controllers in the system to the latest software.
The alarm action is Warning. You cannot see or change the alarm parameters.
5.11 CODESYS alarms

5.11.1 CODESYS application not OK
This alarm alerts the operator that there is a communication problem between CODESYS
CODESYS and the controller. communication Delay
Active
If communication between CODESYS and the controller was active and became
inactive, the delay timer starts. If the communication does not become active within the
delay period, the alarm is triggered. Inactive
Time
Controller types: This alarm is present in all controllers that have CODESYS installed.
CODESYS > Monitoring > Application not OK

Startup time 0 to 600 s 60 s
Delay 0 to 300 s 1s
Action Warning
5.11.2 CODESYS configuration conflict
This alarm alerts the operator that the same I/O is configured on the controller and on CODESYS.

If an I/O is configured on both CODESYS and the controller at the same time, this alarm is triggered.
To clear the alarm, delete the I/O from either the controller or CODESYS, then do a warm reset of CODESYS.
Controller types: This alarm is present in all controllers that have CODESYS installed.
More information
See the Multi-line 300 CODESYS guidelines for more warm reset information.
CODESYS > Monitoring > I/O config conflict


Action Warning

6. Breakers, synchronisation and de-loading
6.1 About
6.1.1 How it works
A number of power sources can supply power to the same busbar. These power sources must be synchronised in order to safely
connect them. Synchronisation consists of matching the voltage, frequency and phases on both sides of the breaker that must be
closed.
The GENSET controllers can adjust the frequency and phase of the genset(s) by regulating their governors.
The GENSET controllers can adjust the voltage of the genset(s) by regulating their AVRs.
Each controller type monitors the voltage, frequency and phase across its breaker. If the measurements are within the configured
limits, the controller can activate the Breakers > [Breaker] > Control > [*B] close output.
More information
See Regulation for information on the regulation of the gensets.
See each controller type for information on each controller's breaker sequences.
6.1.2 Regulation required for synchronisation
GENSET and SHAFT generator controllers

When a GENSET or SHAFT generator controller gets a Close breaker command, the controller ignores the selected regulator
mode and external set points. The controller uses the voltage, frequency and phase regulation parameters to synchronise to the
busbar.
Other controller types

The SHORE connection and BUS TIE breaker controllers do not regulate.
When one of these controllers gets a Close breaker command, it broadcasts over the network the voltage, frequency and phase that
it requires to synchronise. In response, the GENSET controller(s) in the same section that have External set point (network)
activated then regulate according to the network set point.
6.1.3 Regulation required for de-loading
GENSET and SHAFT generator controllers

When a GENSET or SHAFT generator controller gets an Open breaker command, the controller ignores the selected regulator
mode and external set points. The controller uses the fixed power parameters for regulation to de-load.
When a GENSET or SHAFT generator controller gets an Open breaker command and it is the only connected power source on the
busbar section, the controller will open the breaker without de-loading.
More information
See GENSET controller for more information about the generator breaker open sequence.
Other controller types

The SHORE connection and BUS TIE breaker controllers do not regulate.
When one of these controllers gets an Open breaker command, it broadcasts over the network the active and reactive power set
point that it requires to de-load. In response, the GENSET controller(s) in the same section that have External set point (network)
activated then regulate according to the network set point.

More information
See Reactive power ramp down in the Regulation chapter.
6.2 Synchronisation in each control mode

6.2.1 Synchronisation in LOCAL mode
If the controller is under local control, to start synchronisation, the operator must press the push-button Close breaker on the
display unit. The controller automatically closes the breaker if the synchronisation meets the requirements within the time allowed.
6.2.2 Synchronisation in REMOTE mode
If the controller is under remote control, to start synchronisation, the controller must receive an external command (for example, from
a digital input, PICUS, Modbus, and/or CustomLogic or CODESYS or a PLC). The controller monitors the synchronisation, and
automatically closes the breaker if the synchronisation meets the requirements within the time allowed.
6.2.3 Synchronisation in switchboard control
If the controller is in switchboard control, the synchronisation must be done manually.
To get in switchboard control, the controller must receive an external signal. This is normally done using a switch on the switchboard
that is connected to one of the controller's digital inputs. That digital input is then assigned the Local > Mode > Switchboard
control function.
Manual regulation during switchboard control using controller inputs

The switchboard manual regulation buttons can be connected to digital inputs on the controller, and configured with the following
functions:
• Regulators > GOV > Manual > Manual GOV increase
• Regulators > GOV > Manual > Manual GOV decrease
• Regulators > AVR > Manual > Manual AVR increase
• Regulators > AVR > Manual > Manual AVR decrease
During switchboard control, when the operator presses the buttons, the controller adjusts the governor and/or AVR output.
More information
See Control and modes for more information.
Synchronising during switchboard control

During switchboard control, if the operator wants to synchronise and close a breaker, the operator must use the switchboard to
operate the system. The operator manually adjusts the speed of the relevant equipment until the frequencies are almost the same.
The operator then finely adjusts the speed until the power sources are in phase. The phase synchronisation of the power sources
must be shown by a switchboard instrument, for example, a synchroscope. When the phases are within the synchronisation limits,
the operator closes the breaker.
Protections during switchboard control

During switchboard control, there are no proactive checks on the operator inputs. For example, an operator could increase the
genset speed above the normal operating speed by repeatedly pressing the GOV up switchboard push-button. Similarly, the
operator could press a Breaker close switchboard push-button even though the phases are not within the synchronisation limits.

NOTICE
Operator errors during switchboard control

The controller protections will not protect the system against all possible operator errors during switchboard control. For
example, if the operator closes the breaker even though the power sources are not synchronised, there can be an
explosion or fire. For this reason, a well-designed switchboard (including a sync check relay) is essential for
switchboard control.
The controller protections are still active during switchboard control. These protections minimise the damage that an operator can do
during switchboard control. For example, if the engine speed reaches 120 % of the nominal speed, the controller will shut down the
engine.
6.3 Configuring breakers

6.3.1 Breaker commands
Digital inputs (optional)

The following inputs are not part of the breaker configuration and are optional. They can be used for commands to the controller.

Breakers > [Breaker] > This input has the same effect as pressing the Breaker open
Digital input Pulse
Command > [*B] open button on the display unit.
Breakers > [Breaker] > This input has the same effect as pressing the Breaker close
Digital input Pulse
Command > [*B] close button on the display unit.
Breakers > [Breaker] > The controller does not allow the breaker to close while this
Command > Block [*B] close input is active.
Breakers > [Breaker] > If the controller is under remote control, then activating this
Command > [*B] open without Digital input Pulse digital input opens the breaker without de-loading the
de-loading breaker.
6.3.2 Pulse breaker
A pulse breaker closes or opens in response to a pulse from the controller.
Wiring examples
More information
See Breaker wiring in the Installation instructions for an example of pulse breaker wiring.
Inputs and outputs

Breakers > [Breaker] > The controller activates the Close output to close the
Digital output Pulse
Control > [*B] close breaker.
Breakers > [Breaker] >
Digital output Pulse The controller activates the Open output to open the breaker.
Control > [*B] open
The controller activates the Trip output when an alarm with a

trip breaker action activates.
Control > [*B] trip
The output remains active until all alarms with a trip breaker
action are resolved.
Breakers > [Breaker] > Wire this feedback from the breaker, to inform the controller
Feedback > [*B] open when the breaker is open.

Breakers > [Breaker] > Wire this feedback from the breaker, to inform the controller
Feedback > [*B] closed when the breaker is closed.
Optional: Wire this feedback from the breaker, to inform the
Feedback > [*B] short Digital input Continuous
controller if a short circuit occurs.
circuit
Parameters
Breakers > [Breaker] configuration > Configuration
• Pulse breaker
Pulse This breaker requires a pulse signal to close, and a different pulse
Breaker type • Compact breaker
breaker signal to open.
• Continuous breaker
The length of the synchronisation pulse (that is, the maximum

amount of time that the Breakers > [Breaker] > Control >
[*B] close output is activated).
Pulse time ON 0.0 to 60.0 s 1.0 s
If the controller receives breaker closed feedback within this time,

the controller stops activating the breaker close output.
The breaker is de-loaded when the power flowing through the

Open point 1.0 to 20.0 % of nominal
5% breaker is less than this set point. The nominal power is the nominal
(de-loading) power
power of the source.
Sequence diagram
Table 6.1 Closing a pulse breaker
Pulse on (Parameters > Breakers > [Breaker] > Pulse

t1 t1
time ON)
(1) Close
breaker To close a pulse breaker:
1. Close breaker: Breakers > [Breaker] > Control > [*B] close
(digital output). The controller activates this output until there is breaker
Breaker closed feedback, or for the Pulse time ON.
(2) closed
feedback 2. Breaker closed feedback: Breakers > [Breaker] > Feedback >
[*B] closed (digital input). This input is activated when the breaker is
closed.
Breaker
(3) open 3. Breaker open feedback: Breakers > [Breaker] > Feedback >
feedback [*B] open (digital input). This input is deactivated when the breaker is
closed.

Table 6.2 Opening a pulse breaker
Pulse on (Parameters > Breakers > [Breaker] > Pulse

t1 t1
time ON)
(1) Open
breaker To open a pulse breaker:
1. Open breaker: Breakers > [Breaker] > Control > [*B] open
Breaker open feedback, or for the Pulse time ON.
(2) closed
feedback 2. Breaker closed feedback: Breakers > [Breaker] > Feedback >
[*B] closed (digital input). This input is deactivated when the breaker
is opened.
Breaker
(3) open 3. Breaker open feedback: Breakers > [Breaker] > Feedback >
feedback [*B] open (digital input). This input is activated when the breaker is
opened.
Table 6.3 Trip a pulse breaker
2 Pulse on (Parameters > Breakers >

t1
Number of [Breaker] > Pulse time ON)
1
(1) trip breaker
alarms 0 To trip a pulse breaker:
1. Number of trip breaker alarms: The number of active
alarms with a Trip [breaker] (or similar) alarm action.
2. Trip breaker: Breakers > [Breaker] > Control
(2) Trip
breaker > [*B] trip (digital output). The controller activates
this output until all alarms with a Trip [breaker] (or
similar) alarm action are not active.
t1 3. Open breaker: Breakers > [Breaker] >
Open Control > [*B] open (digital output). The
(3)
breaker controller activates this output until there is breaker
open feedback, or for the Pulse time ON.
4. Breaker closed feedback: Breakers > [Breaker]
Breaker
> Feedback > [*B] closed (digital input). This
(4) closed
feedback input is deactivated when the breaker is opened.
5. Breaker open feedback: Breakers > [Breaker]
Breaker > Feedback > [*B] open (digital input). This input
(5) open is activated when the breaker is opened.
feedback
6.3.3 Compact breaker
To close a compact breaker, the controller sends an open pulse to load the spring, followed by a pause, and then a close pulse.
Wiring examples
More information
See Wiring for controller functions, Breaker wiring in the Installation instructions for an example of compact breaker
wiring.

Inputs and outputs
Function IO Type Details
Breakers > [Breaker] > Digital When the power sources are synchronised, the controller
Pulse
Control > [*B] close output activates the [*B] close output to close the breaker.
The controller activates the [*B] open output to open the breaker.
Breakers > [Breaker] > Digital
Pulse The controller also activates the [*B] open output to spring-load
Control > [*B] open output
the breaker.
The controller activates the Trip output when an alarm with a trip
breaker action activates.
Continuous
Control > [*B] trip output
The output remains active until all alarms with a trip breaker
action are resolved.
Breakers > [Breaker] > Wire this feedback from the breaker, to inform the controller when
Feedback > [*B] closed the breaker is closed.
Breakers > [Breaker] > Wire this feedback from the breaker, to inform the controller when
Feedback > [*B] open the breaker is open.
Optional. The breaker sends this pulse when it is spring loaded.
Feedback > [*B] spring Digital input Pulse
There is also a timer for spring loading.
loaded

Optional: Wire this feedback from the breaker, to inform the
Feedback > ['B] short Digital input Continous
controller if a short circuit occurs.
circuit
The following inputs and outputs are not part of the breaker configuration and are all optional.
Function IO Type Details

Breaker > [Breaker] > Command This input has the same effect as pressing the Breaker open
Digital input Pulse
> [*B] open button on the display unit.
Breaker > [Breaker] > Command This input has the same effect as pressing the Breaker close
Digital input Pulse
> [*B] close button on the display unit.
Breaker > [Breaker] > Command The controller does not allow the breaker to close while this
> Block [*B] close input is active.
Parameters
Compact breaker: This is a type of pulse breaker. In addition, a

compact breaker has a spring loaded opening mechanism, which must
• Pulse breaker
Pulse be allowed to charge before the compact breaker is allowed to close.
Breaker type • Compact breaker
breaker
• Continuous breaker
To see the compact breaker parameters, you must change the breaker
type, then write the change to the controller, and refresh.
The length of the synchronisation pulse (that is, the maximum amount of
time that the Breakers > [Breaker] > Control > [*B] close output is
Pulse time activated).
0.0 to 10.0 s 1.0 s
ON
If the controller receives breaker closed feedback within this time, the
controller stops activating the breaker close output.
Pulse time During the close sequence, after spring-loading, the controller will not
0.0 to 10.0 s 0.5 s
OFF send the [*B] close pulse until after this time has elapsed.

Spring load At the start of the close sequence, for spring loading, the controller
0.0 to 30.0 s 1.0 s
time activates the [*B] open output for the Spring load time.
The breaker is de-loaded when the power flowing through the breaker is
Open point 1.0 to 20.0 % of
5% less than this set point. The nominal power is the nominal power of the
(de-loading) nominal power
source.
Sequence diagrams
Table 6.4 Closing a compact breaker
Spring load time (Breakers > [Breaker]

t1 t1
configuration > Spring load time)
(1) Open
breaker Wait after spring-loading (Breakers > [Breaker] >
t2
Pulse time OFF)
Spring- t3 Pulse on (Breakers > [Breaker] > Pulse time ON)

(2) loaded
feedback
t2 t3
(3) Close
breaker
Breaker
(4) closed
feedback
To close a compact breaker:
1. Open breaker: Breakers > [Breaker] > Control > [*B] open (digital output). To spring load the breaker, the
controller activates this output until there is spring loaded feedback, or for the Spring load time. After the breaker is spring
loaded, the controller waits for the Pulse time OFF.
2. Optional: Spring loaded feedback: Breakers > [Breaker] > Feedback > [*B] spring loaded (digital input). This
input is activated when the breaker is spring loaded.
3. Close breaker: Breakers > [Breaker] > Control > [*B] close (digital output). The controller activates this output
until there is breaker open feedback, or for the Pulse time ON.
4. Breaker closed feedback: Breakers > [Breaker] > Feedback > [*B] closed (digital input). This input is activated
when the breaker is closed.
Table 6.5 Opening a compact breaker
t1 Pulse on (Breakers > [Breaker] > Pulse time ON)

t1
(1) Open To open a compact breaker:
breaker
1. Open breaker: Breakers > [Breaker] > Control > [*B] open
Breaker open feedback, or for the Pulse time ON.
(2) closed 2. Breaker closed feedback: Breakers > [Breaker] > Feedback >
feedback [*B] closed (digital input). This input is deactivated when the breaker
is opened.
Breaker 3. Breaker open feedback: Breakers > [Breaker] > Feedback >
(3) open [*B] open (digital input). This input is activated when the breaker is
feedback
opened.

Table 6.6 Trip a compact breaker
2 Pulse on (Breakers > [Breaker] > Pulse

t1
Number of time ON)
1
(1) trip breaker
alarms 0 To trip a pulse breaker:
1. Number of trip breaker alarms: The number of active
alarms with a Trip [breaker] (or similar) alarm action.
2. Trip breaker: Breakers > [Breaker] > Control
(2) Trip
breaker > [*B] trip (digital output). The controller activates
this output until all alarms with a Trip [breaker] (or
similar) alarm action are not active.
t1 3. Open breaker: Breakers > [Breaker] >
Open Control > [*B] open (digital output). The controller
(3)
breaker activates this output until there is breaker open
feedback, or for the Pulse time ON.
4. Breaker closed feedback: Breakers > [Breaker]
Breaker
> Feedback > [*B] closed (digital input). This
(4) closed
feedback input is deactivated when the breaker is opened.
Breaker > Feedback > [*B] open (digital input). This input
(5) open is activated when the breaker is opened.
feedback
6.3.4 Continuous breaker
NOTICE
Not suitable for marine use

Due to class requirements, this breaker type is not suitable for marine use. This is because, if the controller failed, then
the breaker would open and the ship would lose power.
You can configure a continuous breaker to use a open breaker signal, an close breaker signal, or an open and a close breaker
signal to open and close the breaker. Configuring both an open and a close breaker signal for a continuous breaker ensures that
synchronisation is precise and that AC protections meet the required operation times.
Wiring examples
More information
See Breaker wiring in the Installation instructions for an example of continuous breaker wiring.
Inputs and outputs

For a continuous breaker, DEIF recommends installing both of the breaker control relays to ensure precise synchronisation and AC
protection operate times.
The controller activates the Close output to close the breaker. To

Continuous open the breaker, the controller deactivates the Close output. The
Control > [*B] close output
Close relay ensures precise synchronisation.
The controller activates the Open output when the breaker must
Breakers > [Breaker] > Digital open. The controller deactivates the Open output when the breaker
Continuous
Control > [*B] open output must close. The Open relay ensures the AC protection operate
times.

The controller activates the Trip output when an alarm with a trip
breaker action activates.
Continuous
Control > [*B] trip output
The output remains active until all alarms with a trip breaker action
are resolved.
Breakers > [Breaker] > Wire this feedback from the breaker to inform the controller when
Feedback > [*B] closed the breaker is closed. *
Breakers > [Breaker] > Wire this feedback from the breaker to inform the controller when
Feedback > [*B] open the breaker is open. *
Optional. Wire this feedback from the breaker if a short circuit
Feedback > [*B] short Digital input Continuous
occurs.
circuit
NOTE * There must be at least one breaker feedback.

Parameters
Continuous breaker: This breaker receives a continuous signal to close if

[B*] close, or the [B*] close and [B*] open functions are configured. If this
signal stops, the breaker opens.
• Pulse breaker
Breaker Pulse
• Compact breaker If only the [B*] open is configured, the breaker receives a continuous
type breaker
• Continuous breaker signal to open. If this signal stops, the breaker synchronises and closes.
Due to class requirements, this breaker type is not suitable for marine use.
This is because the ship would lose power if the controller failed.
Open point The breaker is de-loaded when the power flowing through the breaker is
1.0 to 20.0 % of
(de- 5% less than this set point. The nominal power is the nominal power of the
nominal power
loading) source.
Sequence diagrams
Table 6.7 Closing a continuous breaker
1. Close breaker: Breakers > [Breaker] > Control > [*B]

(1) Close close (digital output). The controller activates this output to close the
breaker breaker.
2. Breaker closed feedback: Breakers > [Breaker] > Feedback >
Breaker [*B] closed (digital input). This input is activated when the breaker is
(2) closed closed.
feedback 3. Open breaker: Breakers > [Breaker] > Control > [*B] open
(digital output). The controller deactivates this output to close the
breaker.
Open
(3) breaker 4. Breaker open feedback: Breakers > [Breaker] > Feedback >
[*B] closed (digital input). This input is deactivated when the breaker
is closed.
Breaker
(4) open
feedback

Table 6.8 Opening a continuous breaker
1. Close breaker: Breakers > [Breaker] > Control > [*B]

(1) Close close (digital output). The controller deactivates this output to open the
breaker
breaker.
2. Breaker closed feedback: Breakers > [Breaker] > Feedback >
Breaker [*B] closed (digital input). This input is deactivated when the breaker
(2) closed is opened.
feedback 3. Open breaker: Breakers > [Breaker] > Control > [*B] open
(digital output). The controller activates this output to open the breaker.
Open 4. Breaker open feedback: Breakers > [Breaker] > Feedback >
(3)
breaker [*B] open (digital input). This input is activated when the breaker is
opened.
Breaker
(4) open
feedback
Table 6.9 Trip a continuous breaker
1. Number of trip breaker alarms: The number of

2
Number of active alarms with a Trip [breaker] (or similar) alarm
1
(1) trip breaker action.
alarms 0
2. Trip breaker: Breakers > [Breaker] >
Control > [*B] trip (digital output). The
controller activates this output until all alarms with a
Trip Trip [breaker] (or similar) alarm action are not active.
(2)
breaker 3. Close breaker: Breakers > [Breaker] >
Control > [*B] close (digital output). The
controller deactivates this output to open the breaker.
Close 4. Breaker closed feedback: Breakers >

(3)
breaker [Breaker] > Feedback > [*B] closed (digital
input). This input is deactivated when the breaker is
opened.
Breaker 5. Open breaker: Breakers > [Breaker] >
(4) closed
Control > [*B] open (digital output). The
feedback
controller activates this output to open the breaker.
(5) Open > Feedback > [*B] open (digital input). This
breaker
input is activated when the breaker is opened.
Breaker
(6) open
feedback
6.3.5 Redundant breaker feedback
Redundant breaker feedback can be configured on bus tie breaker controllers and externally controlled breakers.
Wiring examples
More information
See Breaker wiring in the Installation instructions for an example of redundant breaker feedback wiring.

Digital inputs
The redundant breaker feedback inputs are only visible if a redundant breaker feedback was configured to the controller.

Breakers > Breaker feedback # > Wire this feedback from the breaker, to inform the
Feedback > Breaker # feedback open * controller when the breaker is open.
Breakers > Breaker feedback # >
Wire this feedback from the breaker, to inform the
Feedback > Breaker # feedback closed Digital input Continuous
controller when the breaker is closed.
*
NOTE * Where # is the number of the breaker that has it's redundant breaker feedback assigned to the controller.
6.3.6 Breaker state outputs
Digital outputs (optional)

The outputs are not part of the breaker configuration and are optional.

Breakers > [Breaker] > State > [*B] is
open

Digital output Continuous Activated when the breaker is closed.
closed
Breakers > [Breaker] > State > [*B] is Activated when the system is synchronising the
synchronising breaker.
Breakers > [Breaker] > State > [*B] is Activated when the system is de-loading the
de-loading breaker.
Only for compact breakers.

preparing Activated when the system is loading the spring
on a compact breaker.
Application
A digital output with a breaker state may be wired to a switchboard light, to help the operator.
For example, for a SHAFT generator controller, a digital output may have the Shaft generator breaker > State > SGB is
de-loading function. A switchboard light is lit when the controller system is de-loading the shaft generator breaker.
6.4 Synchronisation functions

6.4.1 Dynamic synchronisation
During dynamic synchronisation, the synchronising genset can run at a slightly different speed to the genset(s) on the busbar. This
speed difference is called the slip frequency. Dynamic synchronisation is recommended where fast synchronisation is required, and
where the synchronising genset is able to take load when the breaker closes.
The synchronising genset is typically run with a positive slip frequency. That is, the synchronising genset runs at a slightly higher
speed than the genset(s) on the busbar. This is to avoid a reverse power trip after synchronisation.
This type of synchronisation is relatively fast because of the minimum and maximum frequency differences. Synchronisation is
possible while the controller is still busy regulating the frequency towards the set point. The frequency does not have to be the same
as the busbar frequency. As long as the frequency difference is within the limits and the phase angles are matched, the controller
can send the close breaker signal.

NOTE Dynamic synchronisation is recommended where fast synchronisation is required, and where the incoming gensets are
able to take load when the breaker closes.
Inputs and outputs
This function uses the controller AC measurements, regulators, and breaker configuration.
Parameters
Name Range Default Notes
Sync. type Dynamic, Static Dynamic Dynamic must be selected.
For synchronisation: Add Delta frequency min. to the busbar frequency,

for the minimum frequency of the synchronising generator.
Delta frequency
-2.0 to 2.0 Hz -0.1 Hz
min.
If this value is too low, there can be reverse power when the breaker
closes.
For synchronisation: Add Delta frequency max. to the busbar frequency,

Delta frequency for the maximum frequency of the synchronising generator.
-2.0 to 2.0 Hz 0.3 Hz
max.
Delta frequency max. must always be higher than Delta frequency min.
Delta voltage 2 to 10 % of nominal The maximum that the voltage of the synchronising generator may be
5%
min. voltage below the voltage of the busbar for the breaker to close.
5%
max. voltage above the voltage of the busbar for the breaker to close.
Breaker close The time between when the close breaker signal is sent and when the
40 to 300 ms 50 ms
time breaker actually closes.
Frequency window example
Busbar frequency: 50.1 Hz

Delta frequency min.: -0.1 Hz
Delta frequency max.: 0.3 Hz
The generator frequency must be between 50.0 Hz and 50.4 Hz for synchronisation.
For a SHAFT generator controller, the synchronisation settings for power take home (PTH) can be configured separately. These are
under Synchronisation setting (PTH).
More information
See Power take home (PTH) for how to configure these settings.
Slip frequency
The slip frequency is calculated as follows:
Slip frequency = (Delta frequency min. + Delta frequency max.)/2
Slip frequency example

The slip frequency is 0.1 Hz.

When the dynamic synchronisation starts, the frequency control function regulates the synchronising genset frequency towards the
following set point:
fset point = fbusbar + Slip frequency
Slip frequency bad example

The slip frequency is 0.0 Hz. There is a risk that there will be no movement, and thus no synchronisation.
Speed up for slip frequency under 0.3 Hz

If the slip frequency is under 0.3 Hz, the controller automatically speeds up the synchronisation rotation until the phase angle
difference is 30 degrees. This cannot be configured or disabled.
Dynamic synchronisation principle

The dynamic synchronisation principle is shown in the following example.
Figure 6.1 Dynamic synchronisation principle, with vector diagrams
GB GB
1500 RPM 1503 RPM

G G
50.0 Hz 50.1 Hz
Connected genset Synchronising genset
Synchronised
Rotation (relative) Rotation (relative)

L1 L1 L1 L1 L2 L3 L1
L2 L3
L1 L1
L3 L2 L3 L2 L3 L2 L3 L2 L3 L2
L3 L1 L2
L1 (genset) - L1 (busbar) [°]
270
180
90
0
0 2.5 5.0 7.5 Time [s]
The two power sources are the three-phase electricity from the generator and the three-phase electricity at the busbar.
Synchronisation minimises the phase angle difference between the power sources.
In this example, the synchronising genset is running at 1503 RPM (about 50.1 Hz). The online genset is running at 1500 RPM
(about 50.0 Hz). This gives the synchronising genset a positive slip frequency of 50.1 Hz - 50.0 Hz = 0.1 Hz. If the slip frequency is

less than Delta frequency max., and more than Delta frequency min., then the controller can close the breaker when the power
sources are synchronised.
In the example above, the difference in the phase angle between the synchronising genset and the busbar gets smaller and smaller.
When difference in the phase angle is near zero, the controller will send the breaker close signal based on the Breaker closing time
(this is not shown in the example). In this way, the breaker physically closes when the genset is exactly synchronised with the
busbar.
When the generator is running with a positive slip frequency of 0.1 Hz relative to the busbar, the two systems will be synchronised
every 10 seconds:
Tsync = 1 / (fsync genset - fonline genset) = 1 / (50.1 Hz - 50.0 Hz) = 10 s
The phases for both three-phase systems rotate. However, in this example, the vectors for the busbar are shown as stationary to
simplify the explanation. This is because we are only interested in the phase angle difference to calculate when to send the
Breakers > [Breaker] > Control > [*B] Close signal.
Load distribution after synchronisation

When the breaker closes, the synchronising genset will take some of the load if it has a positive slip frequency. A negative slip
frequency may lead to reverse power in the synchronising genset.
The proportion of the load that the synchronising genset takes depends on the frequency difference, and the prime mover
characteristics.
The following example shows that at a given positive slip frequency, the synchronising genset will export power to the load after the
breaker closes.
Figure 6.2 Example of load distribution after synchronisation with a positive slip frequency
GB Fuel injection GB Fuel injection
0% 100 % 0% 100 %
Power Power
G G
The following example shows that at a given negative slip frequency, the synchronising genset will receive power from the
connected genset when the breaker closes. This can cause a reverse power trip.

Figure 6.3 Example of load distribution after synchronisation with a negative slip frequency
GB Fuel injection GB Fuel injection
0% 100 % 0% 100 %
Power Power
G G
NOTE To avoid trips caused by reverse power, configure the synchronisation parameters for a positive slip frequency.
Close breaker signal
The controller always calculates when to send the close breaker signal to get the best possible synchronisation of the power
sources. The close breaker signal is sent just before the power sources are synchronised. The close breaker signal is timed so that
the breaker is closed when the difference in the phase angle of the L1 vectors is zero.
The timing of the close breaker signal depends on the Breaker closing time and the slip frequency.
For example, if the response time of the circuit breaker (tCB) is 250 ms, and the slip frequency (fslip) is 0.1 Hz:
degreesCLOSE = 360 degrees × tCB × fslip = 360 degrees × 0.25 s × 0.1 Hz = 9 degrees
In this example, the controller will start the close breaker signal when the difference between the phase angles of the sources is 9
degrees.
6.4.2 Static synchronisation
During static synchronisation, the synchronising genset runs very close to the same speed as the generator on the busbar. The aim
is to let the gensets run at exactly the same speed, with the phase angles of the source and the busbar matching exactly. Static
synchronisation is most suited to systems with a very stable busbar frequency.
Static synchronisation is recommended where a slip frequency is not acceptable.
Static synchronisation should only be used with an analogue output (that is, not relay outputs).
Static synchronisation application example
Use static synchronisation during commissioning, to synchronise the genset to the busbar while the breaker closing is
disabled. The commissioning engineer can then measure the voltages across the breaker, as a safety check.
Inputs and outputs

This function uses the controller AC measurements, regulators, and breaker configuration.

Parameters
• Dynamic Static must be selected. To see the static synchronisation parameters,

Sync. type Dynamic
• Static write the change to the controller, and refresh.
For synchronisation: Add Delta frequency min. to the busbar

Delta frequency frequency, for the minimum frequency of the synchronising generator.
-2.0 to 2.0 Hz -0.1 Hz
min.
This value must be negative for static synchronisation.
For synchronisation: Add Delta frequency max. to the busbar

frequency, for the maximum frequency of the synchronising
Delta frequency generator.
0.0 to 2.0 Hz 0.3 Hz
max.
Delta frequency max. must always be higher than Delta frequency
min.
5%
min. voltage below the voltage of the busbar for the breaker to close.
5%
max. voltage above the voltage of the busbar for the breaker to close.
Breaker close The time between when the close breaker signal is sent and when the
40 to 300 ms 50 ms
time breaker actually closes. This is not used for static synchronisation.
Phase window * 0.0 to 45.0 deg 5.0 deg The maximum phase angle difference allowed for synchronisation.
To close the breaker, the measurements must show that the controller
Minimum time in
0.1 s to 15 min 1.0 s will be able to keep the phase angle difference within the phase
phase window *
window for this minimum time.
NOTE * These parameters are only used for static synchronisation.
Frequency window example
Busbar frequency: 50.1 Hz

The generator frequency must be between 50.0 Hz and 50.4 Hz for synchronisation.
For a SHAFT generator controller, the synchronisation settings for power take home (PTH) can be configured separately. These are
under Synchronisation setting (PTH).
More information
See Power take home (PTH) for how to configure these settings.
Static synchronisation principle

The static synchronisation principle is shown below. In the example, the frequency difference is 0.03 Hz. Phase synchronisation
regulation reduces the phase angle difference from 30 degrees to 0 degrees.

Figure 6.4 Static synchronisation principle
GB GB
1500 RPM 1501 RPM

G G
50.0 Hz 50.03 Hz
Synchronised
Rotation (relative) Rotation (relative)

L1 L1 L1 L1 α α α
L1 L1
L1 L1
L3 L3
L3
L3 L2 L3 L2 L3 L2 L3 L2 L3 L2
L2 L2 L2
L1 (genset) - L1 (busbar) [°]

30
20
10
0
Time [s]
Phase synchronisation regulation

When static synchronisation starts, the frequency regulation regulates the synchronising genset frequency towards the busbar
frequency.
When the genset-busbar difference is 50 mHz, the phase synchronisation function takes over. The controller now ignores fset point.
The controlling parameter for the phase synchronisation regulation is the phase angle difference between the synchronising genset
and the busbar.
Close breaker signal

Breaker > [Breaker] > Control > [*B] Close is activated when phase angle difference between phase L1 of the
synchronising generator and the busbar is within the Phase window (after the Minimum time in phase window timer has run out).
The voltage differences must also be within the configured range (Delta voltage min. and Delta voltage max.). This is shown in the
following drawing. In addition, the frequency differences must be within the configured range (Delta frequency min. and Delta
frequency max.).
The response time of the breaker is not relevant when using static synchronisation, because the slip frequency should be either very
small or zero.

Figure 6.5 Voltage and phase angle difference for static synchronisation
- Phase window + Phase window
Vbusbar Direction of
rotation
Vbusbar + Delta voltage max
Vbusbar – Delta voltage min
Vgenset
Load distribution after synchronisation

The difference between the frequencies of the sources is low. The load distribution therefore does not change much when the
breaker closes.
6.4.3 Regulator synchronisation parameters
During synchronisation the controller regulates the governor to change the frequency and phase angle. These settings are only used
during synchronisation, and can be configured to optimise the synchronisation speed for the system.
Analogue synchronisation parameters

Regulators > GOV analogue configuration > Frequency synchronisation
Kp 0 to 60 2.5 The PID gain for the regulator.
The PID control integral time.
Ti 0 s to 1 min 2.5 s
To turn off the integral component, set Ti to 0. This might cause unexpected regulator
behaviour.
Td 0 to 2 s 0s The PID control derivative.
Regulators > GOV analogue configuration > Phase synchronisation

The phase synchronisation parameters are only used when static synchronisation is selected.

behaviour.

Relay synchronisation parameters
Regulators > GOV relay configuration > Frequency synchronisation
Kp 0 to 100 10 The gain for the regulator.
Regulators > GOV relay configuration > Phase synchronisation

The phase synchronisation parameter are only used when static synchronisation is selected.

Kp 0 to 100 10 The gain for the regulator.
6.4.4 Synchronisation status outputs
Synchronisation status outputs are available in Modbus, CustomLogic and CODESYS.
Outputs
For CustomLogic contacts, access the synchronisation status outputs under Functions > Breakers > [Breaker] >
Outputs > Sync. status. These outputs are all optional.
Synchronisation status
Function Type Details
Delta frequency above Activated when the [Source] side frequency is above the sum of the [Busbar] side frequency
Continuous
max. and Delta frequency max.*
Delta frequency below Activated when the [Source] side frequency is below the sum of the [Busbar] side frequency
Continuous
min. and Delta frequency min.*
Delta voltage above Activated when the [Source] side voltage is above the sum of the [Busbar] side voltage and
Continuous
max. Delta voltage max.*
Delta voltage below Activated when the [Source] side voltage is below the sum of the [Busbar] side voltage and
Continuous
min. Delta voltage min.*
Activated when the difference in phase angles on either side of the breaker is outside the
Vector mismatch alarm set point. However, this function does not use a low frequency
Vector mismatch Continuous
inhibit. Also, the vector mismatch detection is active all the time (and is not affected by the
breaker state).
Phase angle outside Activated when the phase angle difference is outside the Phase window* (only available for
Continuous
window Static or Automatic synchronisation).
6.5 Synchronisation and breaker alarms

6.5.1 Breaker synchronisation failure
Sync
This alarm alerts the operator about a breaker synchronisation failure.
1
The alarm is based on the synchronisation of the source to the busbar, as measured by the
controller. The alarm is activated if the controller has not been able to synchronise within the Delay
delay time. 0
Time

Breakers > [Breaker] monitoring > Synchronisation failure
• GENSET, SHAFT generator, SHORE connection controllers: 1 min

Delay 30 s to 5 min
• BUS TIE breaker controller: 2 min
Action Trip [Breaker] breaker
6.5.2 De-load failure
Value
This alarm alerts the operator to breaker de-load failure. Delay
The alarm is based on the load across the breaker, as measured by the controller. When the
controller internal set point has ramped down to the breaker open point, the timer starts. The Set
controller activates the alarm if the load across the breaker is not reduced to the Open point (de- point
0
loading) within the delay time. Time
Breakers > [Breaker] monitoring > De-load failure

The Open point (de-loading) is configured under Breakers > [Breaker] configuration > Configuration.

Delay 0.0 s to 1 h 10.0 s
Action Warning
Effect of de-load ramp example

Power
The genset is running at 50 % of nominal power. The 50 %

breaker open point is 5 % of nominal power. The graph
shows the power set point in blue, and the genset power in
black. The breaker opens in time, and there is no de-load
error. Open
5%
point
Time
Effect of slow de-loading example

Power
The genset is running at 50 % of nominal power. The 50 %

breaker open point is 5 % of nominal power. The graph
shows the power set point in blue, and the genset power in
black. The de-loading is a lot slower than the power set
point ramp down. The breaker does not open in time, and Open
5%
point
there is a de-load error alarm.
Time
More information
See Regulation for more information about de-loading.

6.5.3 Vector mismatch
-20o L1+20o
L1
This alarm alerts the operator to a vector mismatch during synchronisation.
The alarm is based on the difference between the phase angles on either side of the breaker, L3
as measured by the controller. The alarm is activated when synchronisation is ON and the L3 L2
difference in the phase angles is more than the set point.
L2
On the diagram to the right, the vector diagram for the busbar is black, and the mismatch that is Value
allowed by default is green. The vector diagram for the source is red. L2 is outside the allowed Delay
window.
Set
point
0
Time
Breakers > [Breaker] monitoring > Vector mismatch

Set point 1 to 20 degrees 20 degrees
10 s
Delay 5 s to 1 min DEIF recommends that this delay is lower than the genset Breaker synchronisation failure
delay.
Action Warning
Frequency-based inhibit
The Vector mismatch alarm is inhibited outside of the synchronisation window. That is, it is inhibited if the frequency from the source
is more than the Delta frequency min. below the busbar frequency, or the Delta frequency max. above the busbar frequency. These
parameters are defined under Synchronisation settings.
6.5.4 Breaker opening failure
Breaker
open
This alarm alerts the operator to a breaker open failure if a breaker open feedback is present.
1
The alarm is based on the breaker feedback signal, which is a digital input to the controller. The
alarm timer starts when the controller sends the signal to open the breaker. The alarm is Delay
activated if the breaker feedback does not change from Closed to Open within the delay time. 0
Time
Breakers > [Breaker] monitoring > Opening failure

The alarm is always enabled when at least one breaker feedback is configured. The alarm action is always Latch enabled.
If no breaker feedback is configured in the Input/output for the breaker, then the parameters are not visible.

Delay 0.1 to 10.0 s 2.0 s
Action Block
6.5.5 Breaker closing failure
Breaker
This alarm is for breaker closing failure. close
1
The alarm is based on the breaker feedback signal, which is a digital input to the controller. The
alarm timer starts when the controller sends the signal to close the breaker. The alarm is
activated if the breaker feedback signal does not change from Open to Closed within the delay Delay
time. 0
Time
Breakers > [Breaker] monitoring > Closing failure

This alarm is always enabled when at least one breaker feedback is configured for the breaker. The alarm action is Trip [Breaker]
and Latched.
If no breaker feedback is configured in the Input/output for the breaker, then the parameters are not visible.

Delay 0.1 to 30.0 s 2.0 s
6.5.6 Breaker position failure
This alarm is for breaker position failure. The

alarm is present where both open and closed
feedback are configured. 1 1
Breaker Breaker
open open
The alarm is based on the breaker feedback feedback feedback
signals, which are digital inputs to the controller. 0 0
The alarm is activated if the breaker Closed and
Open feedbacks are both missing for longer than 1 1
the delay time. The alarm is also activated if the Breaker Breaker
breaker Closed and Open feedbacks are both closed closed
feedback feedback
present for longer than the delay time.
0 0
1 1
Delay Delay
Breaker Breaker
position position
OK OK
0 0
Time Time
Breakers > [Breaker] monitoring > Position failure

The alarm is always Enabled and Latched when both breaker feedback functions are configured for the breaker. The alarm action is
Warning for external breakers and Block for all other breakers.
If only one or no breaker feedbacks are configured in the Input/output for the breaker, then the parameters are not visible.

Delay 0.1 to 5.0 s 1.0 s

6.5.7 Breaker trip (external)
Breaker
Delay
This alarm alerts the operator to an externally-initiated breaker trip.
Closed
The alarm is activated if the controller did not send an open signal, but the breaker feedback
shows that the breaker is open.
Open
Time
Breakers > [Breaker] monitoring > Tripped (external)

For the tie breaker, the alarm action is always Trip tie breaker and Latched. For all other breakers, the alarm action is always Block
and Latched.
The delay is always 0.1 s.

Inhibit Controller under SWBD control
6.5.8 Breaker short circuit
1
The alarm response is based on the digital input with the Breaker > Feedback > [*B] short Breaker >
circuit function (see below). This digital input is typically wired to the breaker's short circuit Feedback >
feedback. Short circuit
0
Time
Parameter
Breakers > [Breaker] monitoring > Short circuit
The alarm action is Trip [Breaker].

Enable Enabled, Not enabled Enabled
Latch Enabled, Not enabled Enabled
Digital input
• Required for short circuit detection, when the breaker is tripped

Breakers >
independently due to a short circuit. One input is required for each
[Breaker] >
Digital input Continuous breaker.
Feedback > [*B]
short circuit • The breaker activates this input when it detects a short circuit. The
controller then activates the [Breaker] short circuit alarm.

6.5.9 Phase sequence error
L1
-40o +40o
The controller continuously checks the line voltage vectors on either side of the breaker against 70 %
the orientation defined in the controller. If the voltage is more than the detection voltage, and
the phase angle differs from the expected angle by more than ±40º, the alarm is activated. This
means that the alarm will also detect if the phase rotation is different from the direction of L3 L2
rotation defined in the controller.
There are two alarms for each controller. These alarms correspond to the controller's AC
Value
measurements. There is one alarm for the voltage from the [Source] (terminal B), and another
alarm for the voltage on the [Busbar] (terminal A). Delay
Set
point
time
[Source] > AC setup > Phase sequence error

The alarm action is Trip [Breaker] and cannot be changed.
Detection voltage * 30 to 90 % of nominal source/busbar voltage 70 %*

Delay 1 to 10 s 1s
NOTE * The alarm is inhibited if the voltage is below this set point.
[Busbar] > AC setup > Phase sequence error
The alarm action is Trip [Breaker] and cannot be changed.
Detection voltage * 30 to 90 % of nominal source/busbar voltage 70 %*

Delay 1 to 10 s 1s
NOTE * The alarm is inhibited if the voltage is below this set point.
6.5.10 Breaker configuration failure
This alarm blocks breaker operation if the breaker is not properly configured. The alarm is activated if a breaker is present on the
Application single-line diagram, but the Input/output functions that are required for the breaker type are not fully configured.
This alarm is always enabled, and has the alarm action Block, Latch enabled. You cannot see or change the parameters for this
alarm.

7. Regulation
7.1 About regulation

7.1.1 How it works
The GENSET controllers can use analogue and/or relay control functions for regulation.
There are five governor regulation modes and six automatic voltage regulator (AVR) regulation modes (including manual regulation)
that can be selected on the controller to control the genset regulators. These modes can be activated by configuring the phactivation
function to a digital input, or by using CustomLogic, or by sending the activation signal over Modbus. To change from one regulation
mode to another regulation mode, select the new regulation mode using your configured activation function.
If you have a GAM3.2 module installed, then the controller also has a stand alone regulation mode for both governor and AVR.
When the controller is in Switchboard control, or when certain alarm conditions are active, regulation must be done manually.
More information
See Switchboard control for how to control the regulators manually through the controller.
All the input and output information in this chapter is written from the DEIF controller point of view, except if clearly stated otherwise.
Overview of analogue control and relay control

Analogue control generally achieves finer control results than relay control. Analogue control also allows the controller to use a pulse
width modulation (PWM) output, for governors and automatic voltage regulators that support this as an input (as opposed to an
analogue input to the governor or AVR). DEIF recommends that you use the full capability of analogue control in situations which
require precision, such as static synchronisation.
Relay control is not able to produce the same precision as a well-tuned analogue controller. However, setting up relay control is
simpler. To extend the life of relays, the controller has a range around the set point where the controller does not send regulation
signals to the governor or automatic voltage regulator when using relay control. This range is called the regulation deadband.
Analogue regulation does not have a deadband area, which contributes to more accurate regulation of the governor or AVR.
7.1.2 Analogue regulation
For regulation, an analogue output is a continuous signal.
Configuring analogue outputs

Assign the analogue output regulation function(s) under Configure > Input/output.
Configure the parameter Regulators > [Regulator] general configuration > Regulator output > Output type
to Analogue (where [Regulator] is Governor or AVR).
Configuring pulse width modulation

Some governors require a pulse width modulation (PWM) input. The controller converts the analogue output to a PWM signal for the
PWM terminals.
Connect the governor to the controller's PWM terminals.
Assign the Regulators > GOV > GOV output [%] function to the PWM terminals.
More information
See Pulse width modulation (PWM) output characteristics for the relationship between duty cycles and the PWM output.

Analogue PID controller
A schematic of the analogue PID controller is given below. Analogue control is continuous, and consists of these steps:
1. The controller measures the operating value(s).
2. The controller deducts the measured value from the reference value (that is, the set point) to determine the error (also known as
the deviation).
3. The controller modifies the error using a PID controller, and sends the result to the output modifier.
4. The output modifier converts the modified error to a suitable signal for the governor or AVR.
5. The governor or AVR then adjusts the genset.
Figure 7.1 Simplified overview of the analogue PID controller
Controller
P-part
(1)
Reference value
Gain I-part Output

∑ ∑ G
(Kp) (Ti) modifier
D-part
(Td)
Measured value
PID control
The PID controller consists of three parts.
Part Contribution (Laplace domain) Configurable parameters
Proportional part 1 Kp
Integral part 1 / ( Ti x s ) Kp, Ti
Derivative part Td x s Kp, Td
Gain
The gain (Kp) determines the amplitude of a signal. The amplitude increases for a gain higher than 1, and decreases for a gain
between 0 and 1.
The same gain (Kp) is applied to each part of the analogue controller. That is, increasing the gain not only increases the
proportional part, but also increases the integral part and the derivative part.
Proportional part
The proportional part contributes the amplified error to the PID output.
Gain (Kp) is the only term in the proportional part of the controller. That is, the contribution of the proportional part of the controller is
directly proportional to the calculated error. For example, if Kp is 15 and the calculated error is +0.02, the proportional contribution is
+0.30.

A high Kp makes the system respond strongly to the error. However, the response can be too large, and can lead to long settling
times. A high Kp may make operation unstable.
A low Kp makes the system respond more weakly to the error. A low Kp reduces the settling time. However, the response can be too
small, and therefore ineffective.
Integral part
The integral part eliminates the steady-state error.
The integral part is determined by:

• The amplified error
• The integral action time (Ti)
• The error history
Ti is the time it takes for the contribution of the integral part to be equal to the contribution of the proportional part. If Ti is shorter, the
contribution of the integral part is higher.
Do not set Ti too low. This can make the operation unstable (the effect is similar to a very high gain).
The figures below show the effect of Ti (a constant error is used to simplify the example).
When the system is far away from the reference point the integral part will have a large contribution to the correction. When the
system is close to the reference value, the integral part will have a small contribution to the correction.
I contribution
Ti Ti
I contribution
Contribution
Contribution
P contribution P contribution
Error Error
0 1 2 3 Time [s] 0 1 2 3 Time [s]
The error history is calculated using integration.
Set Ti to zero to turn off the integral part.
Derivative part
The derivative part stabilises operation, allowing higher gain and lower integral action times. The derivative part can improve the
settling time.
The derivative part is determined by:

• The amplified error
• The derivative action time (Td)
• The current rate of change of the error
The derivative part uses a linear extrapolation of the current rate of change over Td to predict the future error. This works well for
slower systems, since they are easier to predict than faster systems. If Td is higher than the optimal time, the settling time can be
very long. For very high values, the system might not be able to settle at the reference value (the effect is similar to a very high
gain).
From experience, the derivative part can improve regulation during load sharing, power regulation and static synchronisation, when
the parameter is properly tuned.

Use the derivative part if the situation requires very precise regulation (for example, static synchronisation). If the derivative part is
used, it MUST be properly tuned.
Set Td to zero to turn off the derivative part.
Tuning the controller PID

You can tune each of the PID parts to optimise the controller regulation for your system.
7.1.3 Relay regulation
Relay control activates or deactivates the [Regulator] increase and [Regulator] decrease relays to increase or decrease the control
signal, based on the output of the controller (where [Regulator] is either GOV, or AVR).
Configuring digital outputs

To use relay outputs to communicate with the governor or AVR, assign the digital output regulation functions under Configure >
Input/output.
Configure the parameter Regulators > [Regulator] general configuration > Regulator output > Output type
to Relay (where [Regulator] is Governor or AVR).
Relay regulation ranges

The controller determines whether the output should be increased or decreased by comparing the measured value to the set point.
The controller determines how far the deviation (also known as the error) is from the set point, and selects an output range. The
output can be in one of three ranges, which are summarised in the table below:
Range Relay position Notes
The measured value is far away from the reference value. The [Regulator] increase * or
[Regulator] decrease * relay is activated for the maximum time allowed by the Period time and the
Closed or
Constant Maximum ON time percentage. If the measured value is still far away after the maximum time was
intermittent reached, then the relay is reactivated after the Period time is reached.
range
open/close
See point 1 on the figures below for an example where the Maximum ON time is set to 100 %.
The measured value is approaching the reference value, but is not in the deadband range yet. The
[Regulator] increase * or [Regulator] decrease * relay pulses. The signal from the relay is thus
intermittent.
Variable Intermittent The length of the pulse is dependent on the distance from the reference value, the period time and
range open/close the controller gain, Kp. If the measured value is further away from the reference value, the
controller uses a longer pulse. If the measured value is closer to the reference value, the controller
uses a shorter pulse. You can define the minimum pulse width.
See points 2, 3, 4 and 5 on the figures below.
The measured value is so close to the reference value that it is within the deadband percentage of
the reference value. The deadband is specific to the control type that is active, and you can define
Deadband the deadband value. The [Regulator] increase * and [Regulator] decrease * relays remain
Open
range deactivated continuously.
See point 6 on the figures below.
NOTE * [Regulator] is either GOV, or AVR.
If the output is in either the constant or the variable range, the controller activates the configured relay (governor increase or
decrease, or AVR increase or decrease) for the required time. The figures below show how the time decreases from the value set for
Period time to the value set for Minimum ON time as the measured value gets closer to the set point for high Kp values and low Kp
values. The Maximum ON time parameter is set to 100 %.

Figure 7.2 Up and down relay on time for different deviations from the set point
Relay up
1 on time [%]
High Kp
2 100
Low Kp
3 75
4 50
25
5
Frequency [Hz]
6
25
50
75
100
Relay down
on time [%]
Figure 7.3 Relay action based on measurements at the end of the period time
Relay
status
1 2 3 4 5 6
ON
min
min
min
min
min
OFF Period [ms]

Period time
Pulse properties
A relay control pulse has three main properties:
• Period time
• Minimum ON time
• Maximum ON time
The Period time is measured from the start time of one pulse to the start time of the next pulse.
The Minimum ON time sets the minimum amount of time a relay is allowed to be closed. This should be similar to the minimum time
required for the system to respond to the output signal.
The Maximum ON time sets the maximum amount of time a relay is allowed to be closed when the regulation is in the constant
range. The parameter is a percentage of the Period time.
The pulse length is never shorter than the Minimum ON time. Once the pulse length is equal to or greater than the period time, the
controller shifts from the variable range to the constant range, if the Maximum ON time is set to 100 %. The deviation where this shift
occurs depends on Kp and the period time. As Kp increases, the variable range decreases. As Kp decreases, the variable range
increases.

7.1.4 Droop
The droop percentage for a genset governor is a measure of how much the engine speed changes when there is a change in the
genset power output. Similarly, for a genset AVR, the droop percentage shows the relationship between the generator voltage and
the reactive power output.
Table 7.1 Droop definitions
Droop name Description
The droop setting of the governor or AVR.

Governor or AVR
droop
The governor droop and AVR droop is always active when it is activated in the governor or AVR.
The droop setting in the controller. This refers to the Frequency droop parameter, the Voltage droop
parameter, or both parameters.
Controller droop
The controller droop setting is only active when the frequency droop and/or voltage droop is the selected
regulation mode. When the regulation mode is active, the controller sends signals to the governor and/or AVR
to follow the droop curve based on the controller droop.
This droop value is related to the engine speed. Since engine speed and the generator frequency are
Speed droop
proportional, you can also use the generator frequency to calculate speed droop.
Voltage droop The droop value that is related to the generator voltage.
Regulation of a genset using frequency droop or voltage droop might be required under certain system conditions. For example,
when the controller cannot communicate with all the controllers in the system.
When the controller is in Frequency droop or Voltage droop mode, the regulation of the governor and AVR simulates a situation
where the load sharing is only controlled by the droop. For example, when there is a higher load, the controller regulates the
governor to get a slightly lower frequency. The droop setting in the controller does not change the actual droop in the governor or
AVR.
The genset frequency follows the frequency of the busbar when more than one power generating equipment or mains is connected
to the busbar. The power output is related to the frequency by the droop curve when droop is activated on the governor, or when
frequency droop is the active regulation mode on the controller. When the load on the busbar changes (for example, when a load is
added or removed), all the gensets that are connected to the busbar that are in droop mode will adjust their power output according
to the droop curve at the same frequency. If the gensets have the same droop value, then the load is shared equally between the
gensets.
Figure 7.4 Example of a frequency droop curve for a genset with 4% frequency droop
Governor
frequency [Hz] 50
49
48
0 50 100
Genset
load [%]

The reactive power output is related to the voltage by the voltage droop curve when droop is activated on the AVR ,or when voltage
droop is the active regulation mode on the controller. The reactive power load during voltage droop is shared in a similar was as
active power is shared during frequency droop.
Gensets with the same droop setting example
Gensets A, B and C have a nominal power of 1500 kW each and operate at a nominal frequency of 50 Hz. Each genset
has a 4 % controller droop. The droop curve for each genset is the same, and is shown in the figure below.
Figure 7.5 Droop curve for gensets A, B and C
Governor
frequency [Hz] 50
49
48
0 50 100
Genset
load [%]
All of the gensets are connected to the busbar and are running frequency droop as the active regulation mode. When the
load on the busbar increases from 0 to 2250 kW, the gensets are able to share the load equally because they have the
same droop. The new frequency of the busbar and the gensets is 49 Hz (50 Hz × (1 - 0.04 × 750 kW / 1500 kW) = 49 Hz).
At a total load of 2250 kW, the system runs at 49 Hz. Gensets A, B and C each supply 750 kW (50 % of nominal power).
Power Power Power
750
kW
750 750
kW kW
4% 4% 4%
droop droop droop
Genset A Genset B Genset C
If the gensets that are connected to the same busbar section have different droop settings, the genset(s) with a lower droop will be
loaded more. When the droop curve for one or more gensets are different from the other gensets on the busbar, the gensets take a
different proportion of the load at the same frequency value due to the different droop curves.
Gensets with different droop settings example
Gensets A, B and C have a nominal power of 1500 kW each and operate at a nominal frequency of 50 Hz. Genset A has a
3 % droop and gensets B and C each have a 4 % droop.

Figure 7.6 Droop curves for gensets A, B and C
Governor Governor Governor

frequency 50 frequency 50 frequency 50
[Hz] 49.1 [Hz] 49.1 [Hz] 49.1
48.5
48 48
0 60 100 Genset 0 50 100 Genset 0 50 100 Genset

Genset A load [%] Genset B load [%] Genset C load [%]
3 % droop 4 % droop 4 % droop
All of the gensets are connected to the busbar and are running frequency droop as the active regulation mode. When the
load on the busbar increases from 0 to 2250 kW, the load is not shared equally between the gensets. The new frequency
on the busbar is 49.1 Hz. Because all the generators on the busbar operate at the same frequency, Genset A takes more
of the load than gensets B and C.
At a total load of 2250 kW, the system runs at 49.1 Hz. Genset A supplies 900 kW (60 % of nominal power), while Gensets
B and C each supply 675 kW (45 % of nominal power).
Power Power Power
900
kW
675 675
kW kW
3% 4% 4%
droop droop droop
Genset A Genset B Genset C
More information
See Frequency droop and Voltage droop for information about these regulation modes.
7.1.5 Regulation rules
The controller regulates the genset as follows:

• Not connected: Frequency control at the nominal frequency (with optional frequency offset). The regulation mode and other
inputs are ignored.
• Synchronising: The controller synchronises the genset to the busbar. The regulation mode and other inputs are ignored.
• Connected: According to the selected regulation mode and inputs.
During regulation of the system, the guidelines for the controller mode selection should be followed. The suggested regulation mode
in the table is always for the equipment on the left side of the busbar in the image.

Suggested regulation modes for a genset controller under specific conditions
Suggested Suggested AVR

Condition Set point source
governor mode mode
The generator • No mode • No mode • Genset

breaker is selection selection nominal
open and the required required frequency
genset is (governor)
running. • Genset
nominal
G This can be a voltage (AVR)
stand-alone • Modbus
genset, or a frequency set
genset in a point
system. (governor)
• Modbus
voltage set
point (AVR)
The generator • No mode • No mode

breaker is selection selection
open and the required required
GENSET
controller
receives a
close breaker
command.
The controller
sends
G G
commands to
synchronise
genset to the
busbar
frequency and
voltage.
The genset is • Power load • Reactive power • Controller set

connected to share load share point
the busbar and (Recommended) (Recommended) • External set
producing • Fixed power • Fixed reactive point
power. power
• Frequency ◦ Modbus
droop • Fixed cos phi ◦ Analogue
The genset
• External set • External set
can be a stand
point point
alone genset,
or a genset
G G running in
parallel to
another power
producing
component on
the busbar.

governor mode mode
The genset is • No mode • No mode

running in selection selection
parallel with required required
another power
producing
component on
the busbar.
The GENSET
controller
receives a
open breaker
command.
G G
The controller
sends
commands to
de-load the
generator
breaker.
There is at • External set • External set • Connecting

least one point (network) point (network) equipment
genset controller (for
connected to example, a
the busbar. shaft
The SHAFT generator or
generator shore
controller or connection)
SHORE
connection
controller
receives a
close breaker
command.
G G All the gensets

connected to
the same
busbar that the
equipment is
connecting to,
must change
mode to
External set
point
(network).
There is at • External set • External set • Disconnecting

least one point (network) point (network) equipment
genset controller (for
connected to example,
the busbar. shaft
The SHAFT generator or
generator shore
controller or connection)
G G SHORE
connection
controller
receives a

governor mode mode
open breaker
command.
All the gensets

connected to
the same
busbar that the
equipment is
disconnecting
from, must
change mode
to External set
point
(network).
A BUS TIE • External set • External set • BUS TIE

breaker point (network) point (network) breaker
controller controller
receives a
close breaker
command
between two
live busbars.
All the
connected
G G gensets in one
of the busbar
sections, must
change mode
to External set
point
(network).
A BUS TIE • External set • External set • BUS TIE

breaker point (network) point (network) breaker
controller controller
receives an
open breaker
command.
All the
connected
gensets on the
busbar that will
G G split sections,
must change
mode to
External set
point
(network).
7.1.6 Freeze regulation
You can use the Freeze regulator digital input to override the regulation settings on a genset. The Freeze regulator command stops
regulation on the governor and the AVR when it is activated.

Digital input
Regulators > Common > The operator activates this input to override any regulation
Freeze regulator settings on the governor and the AVR.
When the Freeze regulation input is active the Regulator status screen on the display will show No regulation.
7.2 Governor regulation modes

7.2.1 How it works
The genset regulation system consists of a number of basic control modes for the governor. Each controller processes the input
information and calculates what action the genset should take to reach the required operating value. The calculated value is then
modified according to the governor interface, and sent to the governor.
NOTICE
Parameters require input/output configuration

To see the parameters, you must have a governor configured in the controller with Input/output (relay output or
analogue output).
When a generator breaker is closed and a governor regulator is configured, the operator, CustomLogic, CODESYS or PLC must
select a regulation mode. If no mode is selected, then the Governor regulator mode not selected alarm activates informing the
operator that no regulation mode is selected.
While the generator breaker is closed, the operator, CustomLogic, CODESYS or PLC can change the regulation mode by activating
a different regulation mode. When a new regulation mode is selected, the previous regulation mode is deactivated automatically. If
multiple regulation modes are written to the controller at almost the same time, the mode that was received last will be the new
active mode.
In some cases the operator might want to deactivate regulation. This can be done with the Deactivate regulation functions.
7.2.2 Deactivate regulation
When the genset is running, it is recommended to always have a regulation mode selected. It is possible to change the regulation
mode from one regulation mode to another without deactivating the current regulation mode first. In some special cases you might
want to deactivate the controller regulation mode.
When the Deactivate regulation governor regulation mode is selected, the current regulation mode is deactivated and the governor
regulation status is No regulation. While no governor regulation mode is selected, the controller does not send any regulation signals
to the governor. It is also not possible to send manual regulation signals to the governor through the controller inputs (Manual GOV
increase and Manual GOV decrease). This means that the genset has the same frequency and power production (if governor
droop is active) as before the regulation mode was deactivated, unless the changes are directly caused by the genset.
Digital input
Regulators > GOV > Modes > The operator activates this input to deactivate the current
Digital input Pulse
Deactivate regulation governor regulation mode.
7.2.3 Fixed frequency
If a genset is operating as a stand-alone genset, the operator, CustomLogic, CODESYS or PLC can select fixed frequency
regulation, so that the controller uses the nominal frequency as the regulation set point.

Alternatively the fixed frequency set point can be determined by an analogue input, CustomLogic, Modbus, or CODESYS.
More information
See External communication how the fixed frequency set point is configured using an analogue input or Modbus.
Digital inputs and outputs

Regulators > GOV > Modes > Activate The operator activates this input to activate
Digital input Pulse
fixed frequency fixed frequency regulation.
Regulators > GOV > Modes > Deactivate The operator activates this input to deactivate
Digital input Pulse
fixed frequency fixed frequency regulation.
Regulators > GOV > Modes > Deactivate
Digital input Pulse Disables any active governor regulation mode.
regulation
Regulators > GOV > State > Fixed The relay activates when fixed frequency
frequency regulation is selected regulation is selected.
Regulators > GOV > State > Fixed The relay activates when fixed frequency
frequency regulation is active regulation is active.
Analogue governor output frequency parameters

The frequency regulation parameters define analogue regulation when the controller regulates the frequency.
Regulators > GOV analogue configuration > Frequency regulation

Ti 0 s to 1 min 2.5 s The PID control integral time.
Relay governor output frequency parameters

The frequency regulation parameters define relay regulation when the controller regulates the frequency.
Regulators > GOV relay configuration > Frequency regulation

Kp 0 to 100 10 This is the gain for the regulator.
Deadband 0.2 to 10 % 0.5 % The deadband for the regulator, as a percentage of the nominal frequency.
7.2.4 Fixed power
If a genset is connected to the busbar along with other power generating equipment, the controller can use fixed power (that is,
active power) regulation to ensure that the genset provides a constant amount of power to the busbar regardless of the busbar
frequency. The genset that is under fixed power regulation will provide a constant amount of power to the busbar, regardless of the
frequency on the busbar. This means that there must be other power generating equipment on the busbar, to regulate the frequency
of the busbar.
If only one genset is connected to a busbar without any other power generating equipment, then fixed power regulation is not
possible. In this situation changing the goevrnor output only changes the frequency of the genset, and not the power.
The controller also uses fixed power regulation when ramping up the power of a genset (increasing the load), or when ramping down
the power of a genset (decreasing the load).

If multiple gensets are connected to the same busbar section, the controller can regulate its genset to provide fixed power.
Connected gensets automatically run at the same engine speed. Therefore, decreasing the fuel to the genset automatically
decreases the power that it provides, and increases the load on the other power generating equipment. Increasing the fuel to the
genset automatically increases the power that it provides, and decreases the load on the other power generating equipment.
If more than one genset is connected to the busbar, then the total load on the busbar must be greater than the fixed power set point.
To ensure that the busbar frequency is stable, you must have more gensets under load sharing regulation than fixed power
regulation.
Alternatively the fixed power set point can be determined by an analogue input, CustomLogic, Modbus, or CODESYS.
More information
See External communication how the fixed power set point is configured using an analogue input or Modbus.

Regulators > GOV > Modes > The operator activates this input to activate fixed
Digital input Pulse
Activate fixed power power regulation.
Regulators > GOV > Modes > The operator activates this input to deactivate fixed
Digital input Pulse
Deactivate fixed power power regulation.
Regulators > GOV > Active power The operator activates this input to add the Offset 1
offset > Active power offset 1 value for fixed power to the fix power set point.
Regulators > GOV > Modes >
Deactivate regulation
Regulators > GOV > State > Fixed The relay activates when fixed power regulation is
power regulation is selected selected.
Regulators > GOV > State > Fixed The relay activates when fixed power regulation is
power regulation is active active.
Parameters
Regulators > GOV regulation set points > Fixed power
0 % of nominal genset The regulation set point for fixed power, as a percentage of the genset's
Set point -100 to 100 %
power nominal power.
0 % of nominal genset This value is added to the fixed power set point when the Active power
Offset 1 -100 to 100 %
power offset 1 digital input is activated.
Offset 2 -100 to 100 %
Offset 3 -100 to 100 %
This value is the upper or lower limit for the power set point for fixed power
0 % of nominal genset
Limit 1 -300 to 300 % regulation.
power

It does not matter whether Limit 1 is higher or lower than Limit 2 when the
controller determines the set point range.
This value is the upper or lower limit for the power set point for fixed power
regulation.
100 % of nominal
Limit 2 -300 to 300 %
genset power
Adding offsets to the fixed power set point example
A genset that is running parallel to other gensets is under fixed power regulation. The fixed power set point is 30 % of the
nominal genset power. Offset 1 is set to -5 %, Offset 2 is set to 5 %, and Offset 3 is set to 10 %.
1. Active power offset 1 is activated. The fixed power set point changes from 30 % to 25 %.
• New set point = Current set point + offset = 30 % + (-5 %) = 25 %
2. Active power offset 1 is deactivated. The fixed power set point changes from 25 % to 30 %.
• New set point = Current set point - offset = 25 % - (-5 %) = 30 %
3. Active power offset 2 and Active power offset 3 are activated. The fixed power set point changes from 30 % to 45
%.
• New set point = Current set point + offset 2 + offset 3 = 30 % + 5 % + 10 % = 45 %
Limiting the fixed power set point example
A genset that is running parallel to other gensets is under fixed power regulation. The fixed power set point is 30 % of the
nominal genset power. Offset 1 is set to 20 %, Offset 2 is set to 30 %, and Offset 3 is set to 40 %. Limit 1 is set to 2 %
and Limit 2 is set to 100 %.
If Active power offset 1, Active power offset 2 and Active power offset 3 are activated at the same time, then the
calculated set point is 120 % of nominal genset power. But this value is higher than Limit 2. The power set point is 100 %,
because the calculated value is outside of the set point range that is determined by Limit 1 and Limit 2.
Limit 1 is changed to 80 % and Limit 2 is changed to 40 % and all other parameters remain the same as earlier in the
example. The set point range is 40 % to 80 %.
1. The genset has a fixed power set point of 40 % when no offsets are activated. This is because the Set point (30 %) is
lower than the lower limit (Limit 2 = 40 %).
• Because the Set point (30 %) is lower than the set point range, the set point is adjusted to the lower limit of the
range (Limit 2 = 40 %).
2. If Active power offset 1 is activated, the set point changes from 40 % to 50 %.
• New set point = current set point + offset = 30 % +20 % = 50 %.
• The new set point is within the set point range, and is not adjusted by Limit 1 and Limit 2.
3. If Active power offset 1 and Active power offset 3 are activated at the same time, then the fixed power set point is
80 %.
• New set point = current set point + offset 1 + offset 3 = 30 % + 20 % + 40 % = 90 %
• The new set point is not inside the set point range. The set point is adjusted to the upper limit of the range (Limit 1
= 80 %).
Analogue governor output power parameters

The power regulation parameters define analogue regulation when the controller regulates the governor to change the genset active
power output.

Regulators > GOV analogue configuration > Power regulation
Ti 0 s to 1 min 5s The PID control integral time.
Relay governor output power parameters

The power regulation parameters define relay regulation when the controller regulates the governor to change the genset active
power output.
Regulators > GOV relay configuration > Power regulation

Deadband 0.2 to 10 % 2% The deadband for the regulator, as a percentage of the nominal power.
7.2.5 Frequency droop
If a genset is connected to the busbar, with or without other power generating equipment connected to the same busbar section, the
controller can use frequency droop to regulate the genset frequency/power.
This setting does not provide optimal regulation of the genset, and should only be used if there is a specific design reason for its
use.
During frequency droop regulation the controller regulates the governor output to follow the droop setting of the controller.
More information
See Droop for the relationship between the controller droop and the governor droop.

Digital input Pulse
frequency droop frequency droop regulation.
Digital input Pulse
frequency droop frequency droop regulation.
regulation
Regulators > GOV > State > Frequency The relay activates when frequency droop
droop regulation is selected regulation is selected.
Regulators > GOV > State > Frequency The relay activates when frequency droop
droop regulation is active regulation is active.
Parameters
Regulators > GOV analogue configuration > Frequency droop
The droop percentage that the controller is regulating towards. The controller droop does not
have to be the same as the genset's governor droop.
Droop 0 to 10 % 4 %
A high droop setting results in high frequency deviations from nominal frequency.

A too low droop setting results in not adding the necessary stability to the system.
Regulators > GOV relay configuration > Frequency droop

The droop percentage that the controller is regulating towards. The controller droop does not
have to be the same as the genset's governor droop.
Droop 0 to 10 % 4 %
A high droop setting results in high frequency deviations from nominal frequency.
The droop setting for an analogue regulator is not linked to the droop setting for a relay regulator. This means that if you change
from an analogue output to a relay output (or from a relay output to an analogue output), you must check the droop setting and
correct it if required.
7.2.6 Power load sharing
During power (kW) load sharing, the controller uses the nominal frequency as a reference to regulate the governor output to the
genset. The nominal frequency reference can be adjusted by contributing a weighted amount of the power set point to the reference
value.
Power (kW) load sharing can be used in a system where more than one genset is connected to the same busbar section. At least
two of these gensets must have power load sharing regulation mode activated in order to share the load between them.
All gensets on the same busbar section that have power load sharing active, will share an equal percentage of the load.
More information
See Busbar sections and load sharing.

Digital input Pulse
power load sharing power load sharing.
Digital input Pulse
power load sharing power load sharing.
regulation
Regulators > GOV > State > Power load The relay activates when active power load
sharing is selected sharing (kW) is selected.
Regulators > GOV > State > Power load The relay activates when active power load
sharing is active sharing (kW) is active.
Analogue governor output power load sharing parameters

The power load sharing parameters define analogue regulation when the controller regulates the genset active power output for load
sharing.

Regulators > GOV analogue configuration > Power load sharing regulation
If P weight is 100 %, the controller uses the power and frequency set points equally during load
sharing regulation. If P weight is 0 %, the controller ignores the power set point during load
sharing regulation.
P weight 0 to 100 % 15 %
DEIF recommends that you start with the default value, and then, if necessary, adjust this
parameter. If P weight is too low, the load sharing will not be effective and the load will float
between the controllers. If P weight is too high, the frequency regulation will be too slow, for
example, when a big load connects.
Relay governor output power load sharing parameters

The power load sharing parameters define relay regulation when the controller regulates the genset active power output for load
sharing.
Regulators > GOV relay configuration > Power load sharing regulation
The frequency deadband for the regulator, as a percentage of nominal frequency.
f deadband 0.2 to 10 % 1 % The default deadband is ± 1 %. That is, for a genset with a nominal frequency of 50 Hz, the
deadband is 1 Hz. When the controller frequency set point is 50 Hz, the regulator will not
control the frequency if it is between 49.5 and 50.5 Hz.
The power deadband for the regulator, as a percentage of nominal power.
P deadband 0.2 to 10 % 2 % The default deadband is ± 2 %. That is, for a genset with a nominal power of 100 kW, the
deadband is 4 kW. When the controller power set point is 50 kW, the regulator will not control
the power if it is between 48 and 52 kW.
If P weight is 100 %, the controller uses the power and frequency set points equally during
load sharing regulation. If P weight is 0 %, the controller ignores the power set point during
load sharing regulation.
P weight 0 to 100 % 10 %
parameter. If P weight is too low, the load sharing will not be effective and the load will float
between the controllers. If P weight is too high, the frequency regulation will be too slow, for
example, when a big load connects.
7.2.7 Manual regulation
When Manual regulation is the active regulation mode, the operator controls the governor output manually. The operator can
increase or decrease governor output of the genset using digital inputs (if configured) or Modbus. During Manual regulation, both the
synchronisation and the de-loading must also be manually controlled.

Regulators > GOV >
Digital
Modes > Activate Pulse The operator activates this input to activate manual regulation.
input
manual regulation
Regulators > GOV >

Digital
Modes > Deactivate Pulse The operator activates this input to deactivate manual regulation.
input
manual regulation
When this input is activated during Manual regulation, the controller

increases the output to the governor. This affects the Regulators >
GOV > Control > GOV increase digital output, or the Regulator
Regulators > GOV >
Digital > GOV > Control > GOV output [%] analogue output.
Manual > Manual GOV Continuous
input
increase
Set the percentage change of the governor analogue output value per
second for manual analogue regulation under Regulators > GOV
analogue configuration > Manual slope.
When this input is activated during Manual regulation, the controller

decreases the output to the governor. This affects the Regulators >
GOV > Control > GOV decrease digital output, or the Regulator
Regulators > GOV >
Digital > GOV > Control > GOV output [%] analogue output.
input
decrease
Set the percentage change of the governor analogue output value per
second for manual analogue regulation under Regulators > GOV
analogue configuration > Manual slope.
Regulators > GOV >

Digital
Modes > Deactivate Pulse Disables any active governor regulation mode.
input
regulation
Regulators > GOV >

Digital The relay activates when Manual regulation is the active governor
State > Manual GOV Continuous
output regulation mode.
regulation is active
Parameters
Regulators > GOV analogue configuration > Manual slope
This parameter is only visible if a governor analogue output is configured.
The controller increases or decreases the GOV output [%] analogue output by this
Manual GOV slope 0 to 200 %/s 10 %/s amount when the Manual GOV increase or Manual GOV decrease digital inputs are
activated.
Regulators > GOV relay configuration > Manual configuration

These parameters adjust the controller's relay control output when the selected regulation mode is Manual regulation.
You can make the governor response faster by decreasing the Period time. However, if the
Period 40 ms to 1 rest of the system is slow anyway, you can reduce the wear on the relays by increasing the
2000 ms
time h Period time.

Although a relay controller is capable of fast responses, the Period time should be similar to
the response of the system to extend the relay life.
The Minimum ON time must be long enough to ensure that the governor can detect the
shortest pulse that the controller sends to it. You can increase the Minimum ON time to
force a slow system to respond more to the controller's regulation.
If the controller needs to increase the governor output, the GOV increase digital output is
Minimum ON 40 ms to 1
200 ms activated for at least the Minimum ON time. While the controller is increasing the governor
time h
output, the GOV decrease digital output is not activated.
If the controller needs to decrease the governor output, the GOV decrease digital output is
activated for at least the Minimum ON time. While the controller is decreasing the governor
output, the GOV increase digital output is not activated.
You can decrease the Maximum ON time to force a fast system to respond less to the
controller's regulation. The Maximum ON time is a percentage of the Period time.
If the controller needs to increase the governor output, the GOV increase digital output is
Maximum ON 0 to 100 activated for no longer than the Maximum ON time. While the controller is increasing the
100 %
time % governor output, the GOV decrease digital output is not activated.
If the controller needs to decrease the governor output, the GOV decrease digital output is
activated for no longer than the Maximum ON time. While the controller is decreasing the
governor output, the GOV increase digital output is not activated.
7.2.8 Governor stand-alone mode
Stand-alone mode allows an operator to send regulation signals manually to regulate the governor using only a GAM3.2. This mode
can be used if the rest of the controller is disabled, or if the main controller power supply fails. For stand-alone mode, the controller
must have a correctly configured GAM3.2 module.
If you want to use stand-alone mode during emergencies, DEIF recommends a reliable back-up power supply for GAM3.2.
NOTE Governor stand-alone mode is not related to a stand-alone genset.
NOTICE
Manual regulation inputs override other regulation in stand-alone mode

The manual regulation inputs in stand-alone mode override any other regulation. The GAM3.2 does not stop the user
from sending regulation signals that might damage the genset.
The operator can create a dangerous situation during stand-alone mode. The rest of the controller could be disabled
during stand-alone mode, and therefore be unable to provide protection. The system design and operator training must
take these dangers into account.
NOTICE
Manual control must be configured on GAM3.2

All inputs or outputs used for manual control must be configured on the GAM3.2. The controller must not have any
other governor inputs or outputs.

The operator activates this input to activate stand-alone mode.

Regulators > GOV >
Digital If you want one digital input to activate both GOV and AVR stand-alone
Modes > Stand-alone Continuous
input mode, also configure Regulators > AVR > Modes > Stand-alone
mode
mode on the same input.
When this input is activated during stand-alone mode, the GAM3.2

Regulators > GOV >
Digital increases the output to the governor. That is, the Regulator > GOV >
input Control > GOV output [%] analogue output, or the Regulators >
increase
GOV > Control > GOV increase digital output.

Regulators > GOV >
Digital decreases the output to the governor. That is, the Regulator > GOV >
input Control > GOV output [%] analogue output, or the Regulators >
decrease
GOV > Control > GOV decrease digital output.
Configure either an analogue governor output (GOV output [%]), or two

Governor output - - relay governor outputs (GOV increase and GOV decrease), on the
GAM3.2.
Regulators > GOV >
Digital Optional. The relay activates when stand-alone mode is the active
State > Stand-alone Continuous
is active
The digital inputs Manual GOV increase and Manual GOV decrease are also used for manual regulation.
More information
See Synchronisation in switchboard control for information about manual regulation.
More information
See Configuration alarms for information about the incorrect configuration alarm.
How it works during normal controller operation

When the Stand-alone mode digital input is activated during normal operation, the controller status changes to Manual regulation.
For relay regulation, the GAM3.2 activates the relay outputs in response to the manual inputs.
For analogue regulation, the GAM3.2 initially keeps the analogue output at its last value. The GAM3.2 then adjusts the analogue
output in response to the manual inputs.
How it works if the rest of the controller is disabled

The rest of the controller can be disabled in the following situations:
• PSM3.1 loses power.
• The controller is in service mode, downloading software, and/or internal communication is not working.
The GAM3.2 regards the rest of controller disabled when it cannot communicate with the rest of the controller. As long as the
GAM3.2 has power and the required wiring, you can use it for stand-alone manual regulation.
All inputs or outputs used for manual control must be configured on the GAM3.2. The controller must not have any other governor
inputs or outputs.
When the controller is disabled, activate the Stand-alone mode digital input. The GAM3.2 then sends regulation signals based on
manual regulation inputs.
For analogue regulation, the GAM3.2 initially keeps the analogue output at a preset value. The GAM3.2 then adjusts the analogue

How it works when stand-alone mode is deactivated
If Stand-alone mode is deactivated, the controller determines the regulation mode and the regulation set point.
For analogue regulation, the GAM3.2 initially keeps the governor analogue output at its last value. Before taking over control from
GAM3.2, the controller adjusts the regulation set point for bumpless transfer.
7.2.9 Frequency synchronisation
The controller uses the frequency synchronisation parameters to synchronise the frequency of a synchronous prime mover to the
frequency of the busbar. These regulation parameters are used automatically when the controller receives the Close breaker
command and any regulation mode (except Manual regulation) is active on the controller.
Analogue governor output frequency synchronisation parameters

The frequency synchronisation parameters define analogue regulation when the controller regulates the frequency for breaker
synchronisation.
Regulators > GOV analogue configuration > Frequency synchronisation

Relay governor output frequency synchronisation parameters

The frequency synchronisation parameter defines relay regulation when the controller regulates the frequency for breaker
synchronisation.
Regulators > GOV relay configuration > Frequency synchronisation

7.2.10 Phase synchronisation
The controller uses the phase synchronisation parameters to synchronise the phase angle of a synchronous prime mover to the
phase angle of the busbar during static synchronisation. These regulation parameters are used automatically when the controller
receives the Close breaker command and any regulation mode (except Manual regulation) is active on the controller.
Analogue governor output phase synchronisation parameters

The phase synchronisation parameters define analogue regulation when the controller regulates the phase angle for breaker static
synchronisation.
Regulators > GOV analogue configuration > Phase synchronisation

Relay governor output phase synchronisation parameters

The phase synchronisation parameter defines relay regulation when the controller regulates the phase angle for breaker static
synchronisation.

Regulators > GOV relay configuration > Phase synchronisation
7.3 AVR regulation modes

7.3.1 How it works
The genset regulation system consists of a number of basic control modes for the AVR. Each controller processes the input
information and calculates what action the genset should take to reach the required operating value. The calculated value is then
modified according to the AVR interface, and sent to the AVR.
NOTICE

To see the parameters, you must have an AVR configured in the controller with Input/output (relay output or analogue
output) and no governor mode is active.
When a generator breaker is closed and an AVR regulator is configured, the operator, CustomLogic, CODESYS or PLC must select
a regulation mode. If no mode is selected, then the Regulation mode not selected alarm activates (if enabled) informing the operator
that no regulation mode is selected.
While the generator breaker is closed, the operator, CustomLogic, CODESYS or PLC can change the regulation mode by activating
a different regulation mode. When a new regulation mode is selected, the previous regulation mode is deactivated automatically. If
multiple regulation modes are written to the controller at almost the same time, the mode that was received last will be the new
active mode.
In some cases the operator might want to deactivate the regulation mode. To do this the operator must activate the Deactivate digital
input.
NOTICE
Genset start and regulation mode

The controller does not automatically select a regulation mode when the genset is started.
7.3.2 Deactivate regulation
When the genset is running, it is recommended to always have a regulation mode selected. It is possible to change the regulation
mode from one regulation mode to another without deactivating the current regulation mode first. In some special cases you might
want to deactivate the controller regulation mode.
When the Deactivate regulation AVR regulation mode is selected, the current regulation mode is deactivated and the AVR
regulation status is No regulation mode selected. While no AVR regulation mode is selected, the controller does not send any
regulation signals to the AVR. It is also not possible to send manual regulation signals to the AVR through the controller inputs
(Manual AVR increase and Manual AVR decrease). This means that the genset has the same voltage and reactive power
production (if AVR droop is active) as before the regulation mode was deactivated, unless the changes are directly caused by the
genset.
Digital input
Regulators > AVR > Modes > The operator activates this input to deactivate the current
Digital input Pulse
Deactivate regulation AVR regulation mode.

7.3.3 Fixed voltage
The controller can regulate and maintain the genset voltage at its nominal voltage by sending a signal to the AVR to adjust the
exciter current.
When the genset is not connected to the busbar and fixed voltage is selected, the controller regulates the voltage to the genset
nominal voltage. During synchronisation the controller regulates the voltage to the busbar voltage. If a genset is already connected
to a load, the controller matches the generator voltages before closing an additional generator breaker.
Alternatively the fixed voltage set point can be determined by an analogue input, CustomLogic, Modbus, or CODESYS.
More information
See External communication how the fixed voltage set point is configured using an analogue input or Modbus.

Regulators > AVR > Modes > Activate The operator activates this input to activate
Digital input Pulse
fixed voltage fixed voltage regulation.
Regulators > AVR > Modes > Deactivate The operator activates this input to deactivate
Digital input Pulse
fixed voltage fixed voltage regulation.
regulation
Regulators > AVR > State > Fixed The relay activates when fixed voltage
voltage is active regulation is active.
Analogue AVR output voltage parameters

The voltage regulation parameters define analogue regulation when the controller regulates the voltage.
Regulators > AVR analogue configuration > Voltage regulation

Relay AVR output voltage parameters

The voltage regulation parameters define relay regulation when the controller regulates the voltage.
Regulators > AVR relay configuration > Voltage regulation

Deadband 0 to 10 % 2% The deadband for the regulator, as a percentage of the nominal voltage.
7.3.4 Fixed reactive power
If a genset is connected to the busbar along with other power generating equipment or mains, the controller can use fixed reactive
power regulation to ensure that the genset provides a constant amount of reactive power to the busbar regardless of the active
power produced by the genset. The controller can regulate and maintain the reactive power (kvar) of the genset at its set point by
sending a signal to the AVR to adjust the exciter current. This changes the phase angle between the current and the voltage, hereby
regulating the reactive power.

If a genset is connected to the busbar along with other power generating equipment, the controller can use fixed reactive power
regulation to ensure that the genset provides a constant amount of reactive power to the busbar.
The controller also uses fixed reactive power regulation when ramping up the reactive power of a genset (increasing the load), or
when ramping down the reactive power of a genset (decreasing the load).
If multiple gensets are connected to the same busbar section, the controller can regulate its genset to provide fixed reactive power.
Connected gensets automatically run at the same voltage. Therefore, decreasing the excitation in the generator automatically
decreases the reactive power that it provides, and increases the load on the other power generating equipment. Increasing the
excitation in the generator automatically increases the reactive power that it provides, and decreases the load on the other power
generating equipment.
NOTICE
Genset forced to deliver fixed reactive power

By forcing a genset to deliver a fixed reactive power, the other gensets will have to compensate for this genset's fixed
position. This might cause the other gensets to produce too much capacitive or inductive reactive power.
Alternatively the fixed reactive power set point can be determined by an analogue input, CustomLogic, Modbus, or CODESYS.
More information
See External communication how the fixed reactive power set point is configured using an analogue input or Modbus.

Regulators > AVR > Modes > The operator activates this input to activate fixed
Digital input Pulse
Activate fixed reactive power reactive power regulation.
Regulators > AVR > Modes > The operator activates this input to deactivate fixed
Digital input Pulse
Deactivate fixed reactive power reactive power regulation.
Regulators > AVR > Reactive power The operator activates this input to add the Offset 1
offset > Cos phi/Reactive power Digital input Continuous value for fixed reactive power or fixed cos phi to the
offset 1 set point.
offset 2 set point.
offset 3 set point.
Regulators > AVR > Modes >
Digital input Pulse Disables any active AVR regulation mode.
Regulators > AVR > State > Fixed The relay activates when fixed reactive power
reactive power is active regulation is active.
Parameters
Regulators > AVR regulation set points > Fixed reactive power
0 % of The regulation set point for fixed reactive power, as a percentage of the
nominal genset's nominal reactive power.
Set point -100 to 100 %
reactive
power The genset's nominal reactive power is calculated by the controller.

See AC configuration and nominal settings, Nominal settings,

Nominal power calculations for more information about how the controller
calculates the nominal reactive power.
If the generator production requires reactive power from the system, it is a

capacitive production with a leading cos phi value.
Inductive,
Set point Inductive
Capacitive
If the generator production supplies reactive power to the system, it is an
inductive production with a lagging cos phi value.
Preferred: The set point will remain at the fixed set point, but in certain
situations, for example during de-load of another breaker, the produced
Set point Preferred,
Preferred power is allowed to change.
adjustment Locked
Locked: The controller will always regulate to the selected set point.
This value is added to the fixed reactive power set point when the Reactive
Offset 1 0 to 100 % 0%
Select whether the offset has a lagging cos phi value (inductive), or a leading
cos phi value (capacitive).
Inductive,
Offset 1 Inductive
Capacitive If the offset has the same value (inductive or capacitive) as the set point, then
the offset is added to the set point. If the offset has a different value (inductive
or capacitive) as the set point, then the offset is subtracted from the set point.
Offset 2 0 to 100 % 0%
Inductive,
Offset 2 Inductive
Offset 3 0 to 100 % 0%
Inductive,
Offset 3 Inductive
This value is the upper or lower limit for the reactive power set point for fixed
0 % of reactive power regulation.
nominal
Limit 1 -300 to 300 %
reactive
power
This value is the upper or lower limit for the reactive power set point for fixed
100 % of reactive power regulation.
nominal
Limit 2 -300 to 300 %
reactive
power
Adding offsets to the fixed reactive power set point example

A genset that is running parallel to mains is under fixed reactive power regulation. The fixed reactive power set point is 30
% of the nominal reactive power. Offset 1 is set to 5 %, Offset 2 is set to 10 %, and Offset 3 is set to 15 %. The set point
and all the offsets are set to Inductive.
1. Reactive power offset 1 is activated. The fixed reactive power set point changes from 30 % inductive to 35 %
inductive.
• New set point = Current set point + offset = 30 % + 5 % = 35 %
2. Reactive power offset 1 is deactivated. The fixed reactive power set point changes from 35 % inductive to 30 %
inductive.
• New set point = Current set point - offset = 35 % - 5 % = 30 %
3. Reactive power offset 2 and Reactive power offset 3 are activated. The fixed reactive power set point changes from
30 % inductive to 55 % inductive.
• New set point = Current set point + offset 2 + offset 3 = 30 % + 10 % + 15 % = 55 %
Offset 1 changes to 5 % Capacitive.
Reactive power offset 1 is activated. The fixed reactive power set point changes from 30 % inductive to 25 % inductive.
• New set point = Current set point - offset = 30 % - 5 % = 25 %
• The offset is subtracted from the set point because the set point is an inductive value and the offset is a capacitive
value.
Limiting the fixed reactive power set point example
A genset that is running parallel to mains is under fixed reactive power regulation. The fixed reactive power set point is 30
% of the nominal reactive power. Offset 1 is set to 20 %, Offset 2 is set to 30 %, and Offset 3 is set to 40 %. Limit 1 is set
to 2 % and Limit 2 is set to 100 %. The set point and all the offsets are set to Inductive.
If Reactive power offset 1, Reactive power offset 2 and Reactive power offset 3 are activated at the same time, then
the calculated set point is 120 % (inductive) of nominal reactive power. But this value is higher than Limit 2. The reactive
power set point is 100 % (inductive), because the calculated value is outside of the set point range that is determined by
Limit 1 and Limit 2.
Limit 1 is changed to 80 % and Limit 2 is changed to 40 % and all other parameters remain the same as earlier in the
example. The set point range is 40 % to 80 %.
1. The genset has a fixed reactive power set point of 40 % when no offsets are activated. This is because the Set point
(30 %) is lower than the lower limit (Limit 2 = 40 %).
• Because the Set point (30 %) is lower than the set point range, the set point is adjusted to the lower limit of the
range (Limit 2 = 40 %).
2. If Active power offset 1 is activated, the set point changes from 40 % inductive to 50 % inductive.
• New set point = current set point + offset = 30 % +20 % = 50 %.
• The new set point is within the set point range, and is not adjusted by Limit 1 and Limit 2.
3. If Active power offset 1 and Active power offset 3 are activated at the same time, then the fixed reactive power set
point is 80 % inductive.
• New set point = current set point + offset 1 + offset 3 = 30 % + 20 % + 40 % = 90 %
• The new set point is not inside the set point range. The set point is adjusted to the upper limit of the range (Limit 1
= 80 %).
Analogue AVR output reactive power parameters

The reactive power regulation parameters define analogue regulation when the controller regulates the genset reactive power
output.

Regulators > AVR analogue configuration > Reactive power regulation
Relay AVR output reactive power parameters

The reactive power regulation parameters define relay regulation when the controller regulates the genset reactive power output.
Regulators > AVR relay configuration > Reactive power regulation

Deadband 0 to 10 % 2% The deadband for the regulator, as a percentage of the nominal reactive power.
7.3.5 Fixed cos phi
The controller can send regulation signals to the genset's AVR to keep the genset's cos phi value at the controller set point. When
fixed cos phi is the active regulation mode, the controller sends signals to the AVR to adjust the exciter current when the cos phi
value changes due to loads that were added to or removed from the busbar. By keeping the cos phi value at a fixed value, the
reactive power is regulated according to the amount of active power being produced by the genset.
NOTICE
Genset forced to deliver fixed reactive power

By forcing a genset to deliver a fixed reactive power instead of using fixed cos phi regulation, the other gensets will
have to compensate for this genset's fixed position. This might cause the other gensets to produce too much capacitive
or inductive reactive power.
Alternatively the fixed cos phi set point can be determined by an analogue input, CustomLogic, Modbus, or CODESYS.
The fixed cos phi mode will only be used when multiple gensets are connected to the same busbar section. If only one genset is
connected, then the cos phi value is decided by the system and regulation will not work.
More information
See External communication how the fixed cos phi set point is configured using an analogue input or Modbus.

Regulators > AVR > Modes > The operator activates this input to activate fixed cos
Digital input Pulse
Activate fixed cos phi phi regulation.
Regulators > AVR > Modes > The operator activates this input to deactivate fixed
Digital input Pulse
Deactivate fixed cos phi cos phi regulation.
Regulators > AVR > Cos phi / The operator activates this input to add the Offset 1
reactive power offset > Cos phi/ Digital input Continuous value for fixed reactive power or fixed cos phi to the
Reactive power offset 1 set point.

Regulators > AVR > Modes >
Regulators > AVR > State > Fixed The relay activates when fixed cos phi regulation is
cos phi is active active.
Parameters
Regulators > AVR regulation set points > Fixed cos phi
If the generator production requires reactive power from the system, it is a capacitive
production with a leading cos phi value.
Inductive,
Set point Inductive
Capacitive
If the generator production supplies reactive power to the system, it is an inductive
production with a lagging cos phi value.
This value is added to the cos phi set point when the fixed cos phi Offset 1 digital input
Offset 1 0 to 1 0
is activated.
Select whether the offset has a lagging cos phi value (inductive), or a leading cos phi
value (capacitive).
Inductive,
Offset 1 Inductive
Capacitive If the offset has the same value (inductive or capacitive) as the set point, then the offset
is subtracted from the set point. If the offset has a different value (inductive or
capacitive) to the set point, then the offset is added to the set point.
Offset 2 0 to 1 0
is activated.
value (capacitive).
Inductive,
Offset 2 Inductive
Offset 3 0 to 1 0
is activated.
value (capacitive).
Inductive,
Offset 3 Inductive
This value is the upper or lower limit for the cos phi set point for fixed cos phi
regulation.
Limit 1 0 to 1 0.8
It does not matter whether Limit 1 is higher or lower than Limit 2 when the controller
determines the set point range.
Inductive, Select whether the limit has a lagging cos phi value (inductive), or a leading cos phi
Limit 1 Inductive
Capacitive value (capacitive).
This value is the upper or lower limit for the cos phi set point for fixed cos phi
Limit 2 0 to 1 1 regulation.

It does not matter whether Limit 2 is higher or lower than Limit 1 when the controller
determines the set point range.
Inductive, Select whether the limit has a lagging cos phi value (inductive), or a leading cos phi
Limit 2 Inductive
Capacitive value (capacitive).
Examples
The examples below demonstrate how the cos phi offset is added to the set point.
Adding an inductive cos phi offset to an inductive cos phi set point example
cos phi = 1
cos phi = 0.9I

cos phi = 0.65I
cos phi = 0C cos phi = 0I

Capacitive Inductive
The cos phi Set point is set to the default value of 0.9 inductive. Offset 1 is set to 0.25 inductive. The set point
range (determined by Limit 1 and Limit 2) is not taken into account for this example.
When the Cos phi/Reactive power offset 1 digital input is activated the cos phi set point changes to 0.9I +0.25I =
0.65 inductive.
Adding a capacitive cos phi offset to an inductive cos phi set point example
cos phi = 1
cos phi = 0.85C cos phi = 0.9I
cos phi = 0C cos phi = 0I

Capacitive Inductive
The cos phi Set point is set to the default value of 0.9 inductive. Offset 1 is set to 0.25 capacitive. The set point
range (determined by Limit 1 and Limit 2) is not taken into account for this example.
When the Cos phi/Reactive power offset 1 digital input is activated the cos phi set point changes to 0.9I +0.25C =
0.85 capacitive.
7.3.6 Voltage droop
If a genset is connected to the busbar, with or without other power generating equipment connected to the same busbar section, the
controller can use voltage droop to regulate the genset voltage/reactive power.
This setting does not provide optimal regulation of the genset, and should only be used if there is a specific design reason for its
use. For example, another genset that cannot communicate with the controller is connected to the same busbar section.
During voltage droop regulation the controller regulates the AVR output to follow the droop setting of the controller.
More information
See Droop for the relationship between the controller droop and the AVR droop.

Digital input Pulse
voltage droop voltage droop regulation.
Digital input Pulse
voltage droop voltage droop regulation.
Regulators > AVR > Modes > Deactivate
regulation
Regulators > AVR > State > Voltage The relay activates when voltage droop
droop is selected regulation is selected.
Regulators > AVR > State > Voltage The relay activates when voltage droop
droop is active regulation is active.
Parameters
Regulators > AVR analogue configuration > Voltage droop
The droop percentage that the controller emulates. The controller droop does not have to be the
same as the genset's AVR droop.
Droop 0 to 10 % 4 %
A high droop setting results in high voltage/reactive power deviations from nominal voltage.
Regulators > AVR relay configuration > Voltage droop

The droop percentage that the controller emulates. The controller droop does not have to be the
same as the genset's AVR droop.
Droop 0 to 10 % 4 %
A high droop setting results in high voltage/reactive power deviations from nominal voltage.
The droop setting for an analogue regulator is not linked to the droop setting for a relay regulator. This means that if you change
from an analogue output to a relay output (or from a relay output to an analogue output), you must check the droop setting and
correct it if required.
7.3.7 Reactive power load sharing
During reactive power (kvar) load sharing, the controller uses the nominal voltage as a reference to regulate the AVR output to the
genset. The nominal voltage reference can be adjusted by contributing a weighted amount of the reactive power set point to the
reference value.
Reactive power load sharing can be used in a system where more than one genset is connected to the same busbar section. At
least two of these gensets must have reactive power load sharing activated in order to share the load between them.
All gensets on the same busbar section that have reactive power load sharing active, will share an equal percentage of the load.
More information
See Busbar sections and load sharing.

Digital input Pulse
reactive power load sharing reactive power load sharing.
Digital input Pulse
reactive power load sharing reactive power load sharing.
Regulators > AVR > Modes > Deactivate The input disables any active AVR regulation
Digital input Pulse
regulation mode.
Regulators > AVR > State > Reactive The relay activates when reactive power load
power load sharing is selected sharing (kW) is selected.
Regulators > AVR > State > Reactive The relay activates when reactive power load
power load sharing is active sharing (kW) is active.
Analogue AVR output reactive power load sharing parameters

The reactive power load sharing parameters define analogue regulation when the controller regulates the AVR to change the genset
reactive power output for load sharing.
Regulators > AVR analogue configuration > Reactive power load sharing regulation
behaviour.
If Q weight is 100 %, the controller uses the reactive power and voltage set points equally
during load sharing regulation. If Q weight is 0 %, the controller ignores the reactive power set
point during load sharing regulation.
Q weight 0 to 100 % 15 %
parameter. If Q weight is too low, the reactive power load sharing will not be effective and the
load will float between the controllers. If Q weight is too high, the voltage regulation will be too
slow, for example, when a new heavy consumer connects.
Relay AVR output reactive power load sharing parameters

The reactive power load sharing parameters define relay regulation when the controller regulates the AVR to change the genset
reactive power output for load sharing.
Regulators > AVR relay configuration > Reactive power load sharing regulation
V deadband 0 to 10 % 1% The voltage deadband for the regulator, as a percentage of the nominal voltage.
The reactive power deadband for the regulator, as a percentage of the nominal reactive
Q deadband 0 to 10 % 2%
power.
If Q weight is 100 %, the controller uses the reactive power and voltage set points equally
during load sharing regulation. If Q weight is 0 %, the controller ignores the reactive power
set point during load sharing regulation.
Q weight 0 to 100 % 15 %
parameter. If Q weight is too low, the reactive power load sharing will not be effective and the

load will float between the controllers. If Q weight is too high, the voltage regulation will be too
slow, for example, when a new heavy consumer connects.
7.3.8 Manual regulation
When Manual regulation is the active regulation mode, the operator controls and operates the equipment from the switchboard. The
operator can increase or decrease voltage output of the genset using digital inputs (if configured) or Modbus.

Regulators > AVR >
Digital
Modes > Activate Pulse The operator activates this input to activate manual regulation.
input
manual regulation
Regulators > AVR >

Digital
Modes > Deactivate Pulse The operator activates this input to deactivate manual regulation.
input
manual regulation
This input only has an effect when Manual regulation is the selected
regulation mode.
When this input is activated, the controller increases the output to the
Regulators > AVR > AVR. This affects the Regulators > AVR > Control > AVR
Digital
Manual > Manual AVR Continuous increase digital output, or the Regulator > AVR > Control >
input
increase AVR output [%] analogue output.
Set the percentage change of the AVR voltage per second for manual
analogue regulation under Regulators > AVR analogue
configuration > Manual slope.
This input only has an effect when Manual regulation is the selected
regulation mode.
When this input is activated, the controller decreases the output to the
Regulators > AVR > AVR. This affects the Regulators > AVR > Control > AVR
Digital
Manual > Manual AVR Continuous decrease digital output, or the Regulator > AVR > Control >
input
decrease AVR output [%] analogue output.
Set the percentage change of the AVR voltage per second under
Regulators > AVR analogue configuration > Manual
slope.
Regulators > AVR >

Digital
Modes > Deactivate Pulse Disables any active AVR regulation mode.
input
regulation
Regulators > AVR >

Digital The relay activates when Manual regulation is the active AVR regulation
State > Manual AVR Continuous
output mode.
regulation is active
Parameters
Regulators > AVR analogue configuration > Manual slope
This parameter is only visible if an AVR analogue output is configured.

The controller increases or decreases the AVR output [%] analogue output by this
Manual AVR slope 0 to 200 %/s 10 %/s amount when the Manual AVR increase or Manual AVR decrease digital inputs are
activated.
Regulators > AVR relay configuration > Manual configuration

These parameters adjust the controller's relay control output.
You can make the AVR response faster by decreasing the Period time. However, if the rest
of the system is slow anyway, then decreasing the Period time will provide no additional
Period 40 ms to 1 benefits.
2000 ms
time h
Although a relay controller is capable of fast responses, it is recommended to set the Period
time to be similar to the response of the system.
The Minimum ON time must be long enough to ensure that the AVR can detect the shortest
pulse that the controller sends to it. You can increase the Minimum ON time to force a slow
system to respond to the controller's regulation.
If the controller needs to increase the AVR output, the AVR increase digital output is
200 ms activated for at least the Minimum ON time. While the controller is increasing the AVR
time h
output, the AVR decrease digital output is not activated.
If the controller needs to decrease the AVR output, the AVR decrease digital output is
activated for at least the Minimum ON time. While the controller is decreasing the AVR
output, the AVR increase digital output is not activated.
controller's regulation.
Maximum ON 0 to 100 activated for no longer than the Maximum ON time. While the controller is increasing the
100 %
time % AVR output, the AVR decrease digital output is not activated.
activated for no longer than the Maximum ON time. While the controller is decreasing the
AVR output, the AVR increase digital output is not activated.
7.3.9 AVR stand-alone mode
Stand-alone mode allows an operator to send regulation signals manually to regulate the automatic voltage regulator (AVR) using
only a GAM3.2. This mode can be used if the rest of the controller is disabled, or if the main controller power supply fails. For stand-
alone mode, the controller must have a correctly configured GAM3.2 module.
If you want to use stand-alone mode during emergencies, DEIF recommends a reliable back-up power supply for GAM3.2.
NOTE AVR stand-alone mode is not related to a stand-alone genset.

NOTICE
Manual regulation inputs override other regulation in stand-alone mode

The manual regulation inputs in stand-alone mode override any other regulation. The GAM3.2 does not stop the user
from sending regulation signals that might damage the genset.
The operator can create a dangerous situation during stand-alone mode. The rest of the controller could be disabled
during stand-alone mode, and therefore be unable to provide protection. The system design and operator training must
take these dangers into account.
NOTICE
Manual control must be configured on GAM3.2

All inputs or outputs used for manual control must be configured on the GAM3.2. The controller must not have any
other governor inputs or outputs.

The operator activates this input to activate stand-alone mode.

Regulators > AVR >
Digital If you want one digital input to activate both GOV and AVR stand-alone
Modes > Stand-alone Continuous
input mode, also configure Regulators > GOV > Modes > Stand-alone mode
mode
on the same input.

Regulators > AVR >
Digital increases the output to the AVR. That is, the Regulator > AVR > Control
Manual > Manual AVR Continuous
input > AVR output [%] analogue output, or the Regulators > AVR > Control >
increase
AVR increase digital output.

Regulators > AVR >
Digital decreases the output to the AVR. That is, the Regulator > AVR > Control
Manual > Manual AVR Continuous
input > AVR output [%] analogue output, or the Regulators > AVR > Control >
decrease
AVR decrease digital output.
Configure either an analogue AVR output (AVR output [%]), or two relay
AVR output - -
AVR outputs (AVR increase and AVR decrease), on the GAM3.2.
Regulators > AVR >
Digital Optional. The relay activates when stand-alone mode is the active
State > Stand-alone Continuous
is active
More information
See Automatic voltage regulator for general information on regulation.
The digital inputs Manual AVR increase and Manual AVR decrease are also used for manual regulation.
More information
See Synchronisation in switchboard control for more information on manual regulation.
More information
See Configuration alarms for the incorrect configuration alarm.
How it works during normal controller operation

When the Stand-alone mode digital input is activated during normal operation, the controller status changes to Manual regulation.
For relay regulation, the GAM3.2 activates the relay outputs in response to the manual inputs.

For analogue regulation, the GAM3.2 initially keeps the analogue output at its last value. The GAM3.2 then adjusts the analogue
How it works if the rest of the controller is disabled

The rest of the controller can be disabled in the following situations:
• PSM3.1 loses power.
• The controller is in service mode, downloading software, and/or internal communication is not working.
The GAM3.2 regards the rest of controller disabled when it cannot communicate with the rest of the controller (you could even
remove the GAM3.2 from the rack). As long as the GAM3.2 has power and the required wiring, you can use it for stand-alone
manual regulation.
When the controller is disabled, activate the Stand-alone mode digital input. The GAM3.2 then sends regulation signals based on
manual regulation inputs.
For analogue regulation, the GAM3.2 initially keeps the analogue output at a preset value. The GAM3.2 then adjusts the analogue
How it works when stand-alone mode is deactivated

If Stand-alone mode is deactivated, the controller determines the regulation mode and the regulation set point.
For analogue regulation, the GAM3.2 initially keeps the AVR analogue output at its last value. Before taking over control from
GAM3.2, the controller adjusts the regulation set point for bumpless transfer.
7.4 External communication

7.4.1 How it works
For certain actions and in some regulation modes it is possible to for the controller to receive its set point from an external source.
This source can for example be an analogue input, or a set point from CustomLogic, Modbus, or CODESYS.
NOTICE

The parameters are only visible, if a governor and/or AVR is configured in the controller Input/output (relay output or
analogue output).
7.4.2 External set point (network)
If a SHAFT generator controller, SHORE connection controller or BUS TIE breaker controller is included in the system, then you
must configure the external set point digital input functions on all GENSET controllers. The function must be activated on the
connected gensets in a busbar section in order to synchronise or de-load the breaker of these controllers.
Inputs and outputs

These inputs and outputs are only visible if a regulation output (either relay or analogue) is configured.

Regulators > [Regulator]* >
When activated, the controller sends regulation signals
External set points > Activate Digital input Pulse
according to the set points received over the DEIF
external set point (network)

network. These set points overwrite the controller's

internal set points.
When activated, the controller stops sending regulation

signals according to the set points received over the
External set points > Deactivate Digital input Pulse
DEIF network. The controller uses the internal set
external set point (network)
points to regulate the genset.
Regulators > [Regulator]* > State
Digital Optional. The relay activates when regulation over the
> External set point (network) is Continuous
output DEIF network is selected.
selected
Regulators > [Regulator]* > State

Digital Optional. The relay activates when regulation over the
> External set point (network) is Continuous
output DEIF network is active.
active
NOTE * [Regulator] is either Governor or AVR, depending on which regulator is configured for the controller.
How to synchronise using external communication over the DEIF network
For a SHAFT generator controller or SHORE connection controller:
1. When the controller receives a close breaker command, the controller waits for the busbar to synchronise with the shaft
generator or shore connection.
2. To synchronise the busbar section, activate the Activate external set point (network) digital input for all the connected GENSET
controllers on the busbar section.
3. The GENSET controllers now receive their synchronisation set points from the connecting SHAFT generator controller or
SHORE connection controller.
4. Once the busbar is synchronised, the controller closes the breaker.
5. After the breaker closes, activate the Deactivate external set point (network) digital input on all the connected GENSET
controllers.
6. The GENSET controllers can now to resume operation in a normal regulation mode (for example, Fixed frequency).
For a BUS TIE breaker controller:
1. When the controller receives a close breaker command, the controller waits for the busbar sections to synchronise.
2. To synchronise the busbar section(s), activate the Activate external set point (network) digital input for all the connected
GENSET controllers on the synchronising busbar section(s).
• The PLC can control which busbar(s) to synchronise by using the Activate external set point (network) digital input for the
gensets on that busbar(s).
3. The GENSET controllers on the synchronising busbar section(s) now receive their synchronisation set points from the BUS TIE
breaker controller.
4. Once the busbar sections are synchronised, the controller closes the bus tie breaker.
5. After the breaker closes, activate the Deactivate external set point (network) digital input on all the connected GENSET
controllers.
6. The GENSET controllers can now resume operation in a normal regulation mode (for example, Fixed frequency).
How to de-load using external communication over the DEIF network

For a SHAFT generator controller or SHORE connection controller:
1. When the controller receives an open breaker command, the controller waits for the breaker to de-load before opening.
2. To de-load the breaker, activate the Activate external set point (network) digital input for all the connected GENSET controllers
on the busbar section.
3. The GENSET controllers now receive their de-load set points from the SHAFT generator controller or SHORE connection
controller.
4. Once the breaker is de-loaded, the controller opens the breaker.

5. After the breaker opens, activate the Deactivate external set point (network) digital input on all the connected GENSET
controllers.
For a BUS TIE breaker controller:
1. When the controller receives an open breaker command, the controller waits for the breaker to de-load before opening.
2. To de-load the breaker, activate the Activate external set point (network) digital input for all the connected GENSET controllers
on both sides of the bus tie breaker.
• The PLC can control which busbar(s) to de-load to by using the Activate external set point (network) digital input for the
gensets on that busbar(s).
3. The GENSET controllers now receive their de-load set points from the BUS TIE breaker controller.
4. Once the bus tie breaker is de-loaded, the controller opens the bus tie breaker.
5. After the breaker opens, activate the Deactivate external set point (network) digital input on all the connected GENSET
controllers.
7.4.3 External set points
You can use set point values from an external source, for example analogue inputs or Modbus, instead of using the controller
internal set points.
Configure the external set point digital input functions on the GENSET controller. When the functions are active, the controller
ignores the internal set points configured in the parameters and uses the set points it receives from the external source.
Inputs from external set points must come from the same source. That is, either from analogue inputs or from Modbus. If an
analogue input is configured for an external set point and Modbus communication is available, then the controller will always receive
its external set point value from the analogue input. The Modbus address for that external set point becomes a read-only value,
which is equal to the value of the analogue input for that set point.
Inputs and outputs

Use the digital inputs and output in the table below to activate, deactivate, and to see the activation status of the external set point.
The analogue inputs are used to send the external set point value to the controller. When an external communication input is
assigned to an analogue input, it is not possible to send the assigned external communication set point to the controller with another
communication method (for example, Modbus).
These inputs and outputs are only visible if a regulation output (either relay or analogue) is configured.

Regulators > [Regulator]* > When activated, the controller sends regulation signals
External set points > Digital input Pulse according to the external set points settings. These set points
Activate external set point overwrite the controller's internal set points.
When activated, the controller stops sending regulation
External set points >
Digital input Pulse signals according to the external set point settings. The
Deactivate external set
controller uses the internal set points to regulate the genset.
point

Optional. The relay activates when regulation from an external
State > External set point Digital output Continuous
set point is selected.
is selected

Optional. The relay activates when regulation from and
State > External set point Digital output Continuous
external set point is active.
is active

When configured, the controller receives the frequency offset

Regulators > GOV > Analogue value from this analogue input. This offset is added or
Frequency offset [%] input subtracted from the nominal frequency.
fnew = fnom + (fnom × Frequency offset)
When configured, the controller receives the active power set

Regulators > GOV > Power Analogue
point from this analogue input. The internal controller value for
set point [%] input
the active power set point is ignored.
When configured, the controller receives the voltage offset

Regulators > AVR > Voltage Analogue value from this analogue input. The offset is added or
offset [%] input subtracted from the nominal voltage.
Vnew = Vnom + (Vnom × Voltage offset)
When configured, the controller receives the reactive power

Regulators > AVR > Reactive Analogue
set point from this analogue input. The internal controller
power set point [%] input
value for the reactive power set point is ignored.
When configured, the controller receives the cos phi set point
Regulators > AVR > Cos phi Analogue
from this analogue input. The internal controller value for the
set point input
cos phi set point is ignored.
NOTE * [Regulator] is either Governor or AVR, depending on which regulator is configured for the controller.
It is also possible activate and deactivate the controller mode, including the external communication modes, using CustomLogic,
Modbus, or CODESYS. This is only possible if the function has not been assigned to a digital input in PICUS.
More information
See Discrete output coil (01; 05; 15) in the Modbus tables for more information about the Modbus functions and their
properties.
Modbus parameters
The parameters are not visible in the controller or PICUS. To configure these parameters, you must have a Modbus interface to the
controller.
Modbus Valid
Modbus Scaling
Parameter function Modbus Unit Comment
address (10-x)
codes range
If the operator activates Activate external set

point, the frequency offset is determined by
the value set in Modbus.
Regulators >
Governor > 8008 03; 06; 16 -100 to 100 1 %
Frequency offset The value entered is the percentage of the
nominal frequency that is added to or
subtracted from the nominal frequency to
determine the new set point.
Regulators > If the operator activates Activate external set
Governor > Power 8009 03; 06; 16 0 to 100 0 % point, the power set point is determined by
set point the value set in Modbus.
If the operator activates Activate external set

point, the voltage offset is determined by the
value set in Modbus.
Regulators > AVR
8010 03; 06; 16 -100 to 100 1 %
> Voltage offset The value entered is the percentage of the
nominal voltage that is added to or subtracted
from the nominal voltage to determine the
new set point.

Modbus Valid
Modbus Scaling
Parameter function Modbus Unit Comment
address (10-x)
codes range
Regulators > AVR If the operator activates Activate external set
> Reactive power 8011 03; 06; 16 0 to 100 0 % point, the reactive power set point is
set point determined by the value set in Modbus.
Regulators > AVR If the operator activates Activate external set
> cos phi set 8012 03; 06; 16 60 to 100 2 - point, the cos phi set point is determined by
point the value set in Modbus.
More information
See Holding register (03;06;16) in the Modbus tables for more information about the Modbus functions and their
properties.
7.5 Governor
7.5.1 Governor regulation function
A governor is external equipment used to control the engine speed for the genset. During frequency regulation, when the speed
drops below the required speed, the governor increases the fuel supply to the engine which increases the engine speed. Similarly,
by decreasing the fuel supply, the engine speed also decreases. The frequency of the genset is directly related to engine speed and
the number of poles in the generator.
The governor must allow external adjustment (digital inputs or analogue input), to let the GENSET controller bias the governor
internal set point.
Digital inputs
The operator activates this input to use curve 1 during power

ramp up and power ramp down.
Regulators > GOV >
Command > Activate ramp Digital input Pulse
1 If ramp 2 was selected as the active ramping method when you
activate ramp 1, the ramping method is immediately changed to
ramp 1.
The operator activates this input to use curve 2 during power

ramp up and power ramp down.
Regulators > GOV >
Command > Activate ramp Digital input Pulse
2 If ramp 1 was selected as the active ramping method when you
activate ramp 2, the ramping method is immediately changed to
ramp 2.
The operator activates this input to pause the power ramp up or

power ramp down process.
Regulators > GOV >
Command > Pause ramping
When the power ramp up or power ramp down is paused, the
operator can deactivate this input to unpause the process.
Parameters for governor general configuration

The governor general configuration settings apply to all the controller's governor regulation outputs (for example, relay, analogue,
pulse width modulation, and so on).
Regulator output
If a governor analogue regulation output and both governor relay regulation outputs are configured, then one output must be
selected as the output that sends feedback to the governor.

Regulators > GOV general configuration
Off: The controller does not attempt to regulate the governor, and ignores any
configured hardware.
• Off
Regulator Relay: The controller uses the relay outputs to regulate the governor (only visible if both
• Relay Relay
output relays for the governor regulation are configured).
• Analogue
Analogue: The controller uses an analogue output to regulate the governor (only visible
if a governor analogue regulator output is configured).
Regulation delay
This parameter sets the time the controller waits before starting to regulate the genset. The delay time starts after the running
feedback confirms that the genset is running. It is not desirable to start regulation exactly when running feedback is achieved.
Frequency and voltage are still low compared to the nominal value at this point. The regulation delay is intended to delay regulation
until the frequency and voltage have stabilised at their preset values. This prevents regulation overshoot at start-up.
Regulators > GOV general configuration

The controller waits for the amount of time specified by this parameter, before regulating
Regulator delay 0 s to 1 h 0 s the genset.
This time can for example be used to set the regulation mode.
Parameters for governor regulation set point

The governor regulation set point settings apply to all the controller's governor regulation outputs (for example, relay, analogue,
pulse width modulation, and so on).
Active power ramp up

This parameter defines the speed of the ramp up of the genset active power when the genset is connected to a busbar or when the
fixed power set point changes. The ramping functionality ramps the regulation set points to follow the configurable curve towards the
final set point. This reduces the mechanical strain on the genset when the breaker closes and the genset starts to supply power to
the system. Limiting the power ramp up speed also increases the system stability.
The parameter consists of two curves. Each curve can consist of 2 to 10 coordinates for the time and the percentage of the genset
nominal power.
Regulators > GOV regulation set points > Active power ramp up
Parameter Range Default ramp 1 Default ramp 2 Notes

[s] 0 to 3600 s 0 s; 50 s 0 s; 1000 s The time coordinate for the active power ramp up curve.
The percentage of nominal active power of the genset coordinate for

[%] 0 to 100 % 0 %; 100 % 0 %; 100 %
the active power ramp up curve.
Active power ramp up example
You want a 100 kW genset to ramp up to 50 % of its nominal power at 5 %/s, and 10%/s between 50 % and a 100 % of its
nominal power. This means that it will take at least 15 seconds to ramp up the genset load from 0 kW to 100 kW.
The coordinates for the primary power ramp up curve are: (0 s; 0 %), (10 s; 50 %) and (15 s; 100 %).
This means that the controller regulates the genset to follow a slope of 5 kW/s for the first 50 % of the genset's nominal
power. And the controller regulates the genset to follow a slope of 10 kW/s between 50 % and a 100 % of the genset's
nominal power.

If the genset load is 0 kW, and 50 kW is required from the genset, it takes at least 10 seconds to ramp up the genset load.
If the genset load is 0 kW, and 70 kW is required from the genset, it takes at least 12 seconds to ramp up the genset load.
Active power ramp down

This parameter defines the speed of the ramp down of the genset active power when the fixed power set point changes or when the
genset disconnects from the busbar. This reduces the mechanical strain on the genset and breaker when the breaker opens and the
genset stops supplying power to the system. Limiting the power ramp down speed also increases the system stability.
The parameter consists of two curves. Each curve can consist of 2 to 10 coordinates for the time and the percentage of the genset
nominal power.
Regulators > GOV regulation set points > Active power ramp down
Parameter Range Default ramp 1 Default ramp 2 Notes
[s] 0 to 3600 s 0 s; 20 s 0 s; 1000 s The time coordinate for the power ramp down curve.
The percentage of nominal power of the genset coordinate for the

[%] 0 to 100 % 100 %; 0 % 100 %; 0 %
power ramp down curve.
Power ramp down example
You want a 100 kW genset to ramp down to 50 % of its nominal power at 10 %/s, and 5%/s between 50 % and a 0 % of its
nominal power. This means that it will take at least 15 seconds to ramp down the genset load from 1000 kW to 0 kW.
This means that the controller regulates the genset to follow a slope of 10 kW/s between 100 % and 50 % of the genset's
nominal power. And the controller regulates the genset to follow a slope of 5 kW/s between 50 % and a 0 % of the genset's
nominal power.
If the genset load is 50 kW, and 0 kW is required from the genset, it takes at least 10 seconds to ramp down the genset
load.
If the genset load is 70 kW, and 0 kW is required from the genset, it takes at least 12 seconds to ramp down the genset
load.
7.5.2 Governor analogue regulation function
You can configure an analogue output on the controller to regulate the governor. You can also set a number of parameters for the
governor analogue regulation function.
Example of analogue output wiring for governor regulation
Regulators > GOV > GOV output [%]

Example of pulse width modulation analogue output wiring for governor regulation
Regulators > GOV > GOV output [%]
Inputs and Outputs

Function I/O Units Details
Regulators > GOV >
When the operator activates this digital input, the analogue
Command > Reset GOV to Digital input Pulse
output is reset to the GOV output offset value.
offset
The controller adjusts this output to regulate the governor.

Regulators > GOV > GOV Analogue
-100 to 100 %
output [%] output DEIF recommends that you use the full range of the output, that
is from -100 % to 100 %, when you configure the output.
NOTE The setup and parameters for governor regulation using pulse width modulation (PWM) is exactly the same as for an
analogue output.
More information
See Input/Output in the PICUS manual for how to configure an analogue output.
Parameters
Regulators > GOV analogue configuration > Offset
To see the governor analogue control parameters, you must assign the function to an analogue output.
When you start and/or run a genset, you might want to adjust the starting point for analogue regulation. This is done by changing the
output offset.
The offset is added to the GOV analogue output. The number of

the offset relates to the nominal settings set. If you select
Nominal settings 1, then the controller uses GOV output offset 1.
The nominal settings set also determine the values of other
nominal settings and engine RPM.
GOV output offset 1

When the genset starts, it starts from the offset value, allowing
GOV output offset 2
-100 to 100 % 0% the genset to reach the set point quickly. Ideally, the governor
GOV output offset 3
should be tuned so that if there is no signal, the genset runs at
GOV output offset 4
its nominal frequency if there is no load. However, if this is not
possible, GOV output offset allows you to compensate the
output to the governor.
To set this parameter, start with GOV output offset = 0 %.

Change the offset value in small increments to fine tune the

frequency output of the genset. When you reach the desired

genset frequency output, the offset is tuned.
7.5.3 Governor relay regulation function
You can configure relay outputs on the controller to regulate the governor. You can also set a number of parameters for the governor
relay regulation function.
Wiring example
Regulators > GOV > Control > GOV increase
Regulators > GOV > Control > GOV decrease
Digital outputs
Regulators > GOV > Variable- The controller activates this output to regulate the governor to
Digital output
Control > GOV increase length pulse increase the engine speed or power.
Regulators > GOV > Variable- The controller activates this output to regulate the governor to
Digital output
Control > GOV decrease length pulse decrease the engine speed or power.
Parameters
These parameters are only visible, if you assign the functions to digital outputs.
Regulators > GOV relay configuration > Automatic configuration

You can make the governor response faster by decreasing the

Period time. However, if the rest of the system is slow anyway,
you can reduce the wear on the relays by increasing the Period
250 ms to 32.5 time.
Period time 1500 ms
s
Although a relay controller is capable of fast responses, the
Period time should be similar to the response of the system to
extend the relay life.
The Minimum ON time must be long enough to ensure that the

governor can detect the shortest pulse that the controller sends
to it. You can increase the Minimum ON time to force a slow
Minimum ON time 10 ms to 6.5 s 200 ms system to respond more to the controller's regulation.
If the controller needs to increase the governor output, the GOV

increase digital output is activated for at least the Minimum ON

time. While the controller is increasing the governor output, the

GOV decrease digital output is not activated.
If the controller needs to decrease the governor output, the GOV

decrease digital output is activated for at least the Minimum ON
time. While the controller is decreasing the governor output, the
GOV increase digital output is not activated.
You can decrease the Maximum ON time to force a fast system

to respond less to the controller's regulation.
If the controller needs to increase the governor output, the GOV

increase digital output is activated for no longer than the
Maximum ON time. While the controller is increasing the
governor output, the GOV decrease digital output is not
Maximum ON time 0 to 100 % 100 %
activated.
If the controller needs to decrease the governor output, the GOV

decrease digital output is activated for no longer than the
Maximum ON time. While the controller is decreasing the
governor output, the GOV increase digital output is not
activated.
7.6 Automatic voltage regulator

7.6.1 AVR regulation function
An AVR is used to control the excitation of the genset. When the current to the exciter is increased, the magnetic field of the exciter
also increases. During voltage regulation, this increases the voltage output from the genset. Similarly, by decreasing the current to
the exciter, the voltage output from the genset is decreased. Reactive power is adjusted in the attempt to increase or decrease
voltage.
The AVR must be prepared for external adjustment (digital inputs or analogue input), to let the genset controller bias the AVR
internal set point.
The sections below describe the input and output setup and common input parameters for the automatic voltage regulator (AVR).
Optional digital input

If there is a shaft generator, shore connection or bus tie breaker in the system, the network external set points must be configured
for the genset controllers. The network external set point is required to synchronise and de-load shaft generators, shore connections
and bus tie breakers. The Modbus external set points are optional.
The operator activates this input to pause the voltage ramp up or voltage
Regulators > AVR > ramp down process.
Command > Pause Digital input Continuous
ramping When the voltage ramp up or voltage ramp down in paused, the
operator can deactivate this input to unpause the process.
Parameters
The AVR general configuration and AVR regulation set point settings apply to all the controller's AVR regulation
outputs (for example, relay or analogue).
These parameters are only visible, if you configure an AVR output function.

Regulators > AVR genaral configuration > Regulator output
If a governor analogue regulation output and both governor relay regulation outputs are configured, then one output must be
selected as the output that sends feedback to the governor.
Off: The controller does not attempt to regulate the AVR, and ignores any configured
hardware.
• Off
Regulator Relay: The controller uses the configured relay outputs to regulate the AVR (only visible
• Relay Relay
output if both relays for governor regulation are configured).
• Analogue
Analogue: The controller uses the configured analogue output to regulate the governor
(only visible if a governor analogue regulator output is configured).
Regulators > AVR genaral configuration > Regulator delay

This parameter sets the time the controller waits before starting to regulate the genset. The delay time starts after the running
feedback confirms that the genset is running. It is not desirable to start regulation exactly when running feedback is achieved.
Frequency and voltage are at this point, still low compared to nominal value. The regulation delay is intended to delay regulation
until the governor and AVR have settled frequency and voltage on their preset values. This prevents regulation overshoot at start-up.
The controller waits for the amount of time specified by this parameter, before regulating
the genset.
Regulator delay 0 s to 1 h 2 s
This time can for example be used to set the regulation mode.
Regulators > AVR regulation set points > Reactive power ramp up
These parameters are only visible, if you configure an AVR output function.
This parameter limits the speed of the ramp up of the genset reactive power when the genset is connected to a busbar or when the
fixed reactive power set point changes. This reduces the mechanical strain on the generator when the breaker closes and the
generator starts to supply reactive power to the system. Limiting the reactive power ramp up speed also increases the system
stability.
In Island regulation mode for power load sharing, the power ramp up is only used an initial power ramp up to the load share set point
during initial connection. Afterwards the ramp is not used.
The curve can consist of 2 to 10 coordinates for the time and the percentage of the genset nominal reactive power.

[s] 0 to 3600 s 0 s; 50 s The time coordinate for the reactive power ramp up curve.
The percentage of nominal reactive power of the genset coordinate for the reactive power
[%] 0 to 100 % 0 %; 100 %
ramp up curve.
Reactive power ramp up using reactive power curve example
You want a 100 kvar genset to ramp up to 50 % of its nominal reactive power at 5 %/s, and 10%/s between 50 % and a
100 % of its nominal reactive power. This means that it will take at least 15 seconds to ramp up the genset reactive power
from 0 kvar to 100 kvar.

This means that the controller regulates the genset to ensure that the reactive power ramp up does not exceed 5 kvar/s for
the first 50 % of the genset's nominal reactive power. And the controller regulates the genset to ensure that the reactive
power ramp up does not exceed 10 kvar/s between 50 % and a 100 % of the genset's nominal reactive power.
If the genset reactive power is 0 kvar, and 50 kvar is required from the genset, it takes at least 10 seconds to ramp up the
genset reactive power.
If the genset reactive power is 0 kvar, and 70 kvar is required from the genset, it takes at least 12 seconds to ramp up the
genset reactive power.
Regulators > AVR regulation set points > Reactive power ramp down
This parameter limits the speed of the ramp down of the genset reactive power when the fixed reactive power set point changes or
when the genset disconnects from the busbar. This reduces the mechanical strain on the generator and breaker when the breaker
opens and the generator stops supplying reactive power to the system. Limiting the reactive power ramp up speed also increases
the system stability.
The curve can consist of 2 to 10 coordinates for the time and the percentage of the genset nominal reactive power.
When Fixed cos phi is selected as the ramping method, and the active power
reaches the Cos phi reset point, the controller stops using a fixed cos phi value for
the remainder of the ramping down of the reactive power.
Cos phi
0 to 100 % 5% When the active power reaches the Cos phi reset point, the cos phi value is
reset point
regulated to 1 in the remaining de-load time.
The Cos phi reset point is a percentage of the active power before the breaker open
point.
[s] 0 to 3600 s 0 s; 20 s The time coordinate for the reactive power ramp down curve.
The percentage of nominal reactive power of the genset coordinate for the reactive
[%] 0 to 100 % 100 %; 0 %
power ramp down curve.
The cos phi value at the start of the breaker de-load sequence is maintained until the active power reaches the cos phi reset point.
During the breaker de-load sequence the controller does not use the cos phi set point (internal or external) as the fixed cos phi
value.
Reactive power ramp down example
You want a 100 kvar genset to ramp down to 50 % of its nominal reactive power at 10 %/s, and 5 %/s between 50 % and a
0 % of its nominal reactive power. This means that it will take at least 15 seconds to ramp down the genset reactive power
from 100 kvar to 0 kvar.
The coordinates for the power ramp up curve are: (0 s; 100 %), (5 s; 50 %) and (15 s; 0 %).
This means that the controller regulates the genset to ensure that the reactive power ramp down does not exceed 10
kvar/s between 100 % and 50 % of the genset's nominal reactive power. And the controller regulates the genset to ensure
that the reactive power ramp down does not exceed 5 kvar/s between 50 % and a 0 % of the genset's nominal reactive
power.
If the genset reactive power is 50 kvar, and 0 kvar is required from the genset, it takes at least 10 seconds to ramp down
the genset reactive power.
If the genset reactive power is 70 kvar, and 0 kvar is required from the genset, it takes at least 12 seconds to ramp down
the genset reactive power.

Cos phi reset point example
A 100 kW genset ramps down from 80 % of its nominal active power and 0.92 inductive cos phi to the breaker open point
at 5 %/s (default ramp down curve). This means that it will take 15 seconds to reach breaker open point.
The cos phi reset point is 5 % before the open point. In this example the cos phi value will be regulated to 1 between 14.25
and 15 seconds. The reactive power will respond accordingly. The resultant ramp down can be seen in the image below:
Cos phi
Active power [%]
[-]
80
10
5% 0.92 I
5
1
14.25 15 Time [s]
7.6.2 AVR analogue regulation function
You can configure an analogue output on the controller to regulate the AVR. You can also set a number of parameters for the AVR
analogue regulation function.
Example of analogue output wiring for AVR regulation
Regulators > AVR > AVR output [%]
Example of pulse width modulation analogue output wiring for AVR regulation
Regulators > AVR > AVR output [%]

Inputs and outputs
Regulators > AVR > Command > Reset When the operator activates this digital input, the
Digital input Pulse
AVR to offset output is set to the offset value.
Regulators > AVR > AVR output [%] Analogue output The controller adjusts this output to regulate the AVR.
NOTE The setup and parameters for AVR regulation using pulse width modulation (PWM) is exactly the same as for an analogue
output.
Parameters
To see the AVR analogue control parameters, you must assign the Regulators > AVR > AVR output [%] function to an
analogue output (that is, AO or PWM).
Regulators > AVR analogue configuration > Offset

When you start and/or run a genset, you might want to adjust the starting point for analogue regulation. This is done by changing the
output offset.
The offset is added to the AVR analogue output. The number of the offset relates to
the nominal settings set. If you select Nominal settings 1, then the controller uses
AVR output offset 1. The nominal settings set also determine the values of other
AVR output nominal settings and engine RPM.
offset 1
AVR output
When the genset is started, it will start from the offset value, allowing the genset to
offset 2 -100 to
0% reach the set point quickly. Ideally, the AVR should be tuned so that if there is no
AVR output 100 %
signal, the genset runs at its nominal voltage if there is no load. However, if this is not
offset 3
possible, AVR output offset allows you to compensate the output to the AVR.
AVR output
offset 4
To set this parameter, start with AVR output offset = 0 %. Change the offset value in
small increments to fine tune the voltage output of the genset. When you reach the
desired genset voltage output, the offset is tuned.
7.6.3 AVR relay regulation parameters
You can configure relay outputs on the controller to regulate the AVR. You can also set a number of parameters for the AVR relay
regulation function.
Wiring example
Regulators > AVR > Control > AVR increase
Regulators > AVR > Control > AVR decrease

Digital outputs
Regulators > AVR > Control Variable-length The controller activates this output to send a signal to the
Digital output
> AVR increase pulse AVR to increase the voltage or reactive power.
Regulators > AVR > Control Variable-length The controller activates this output to send a signal to the
Digital output
> AVR decrease pulse AVR to decrease the voltage or reactive power.
Parameters
Regulators > AVR relay configuration > Automatic configuration
These parameters adjust the controller's relay control output. To see these parameters, you must assign the functions to digital
outputs.
You can make the AVR response faster by decreasing the Period time. However, if the rest
of the system is slow anyway, then decreasing the Period time will provide no additional
Period 50 ms to benefits.
500 ms
time 15 s
Although a relay controller is capable of fast responses, it is recommended to set the Period
time to be similar to the response of the system.
The Minimum ON time must be long enough to ensure that the AVR can detect the shortest
pulse that the controller sends to it. You can increase the Minimum ON time to force a slow
system to respond to the controller's regulation.
100 ms activated for at least the Minimum ON time. While the controller is increasing the AVR
time s
output, the AVR decrease digital output is not activated.
controller's regulation.
Maximum ON activated for at least the Minimum ON time. While the controller is increasing the AVR
0 to 100 % 100 %
time output, the AVR decrease digital output is not activated.
7.7 Configuration alarms

7.7.1 GOV relay setup incomplete
The alarm is based on the Input/output configuration of the controller. The controller activates the alarm when only one of the
following digital outputs is configured:
• Regulators > GOV > Control > GOV increase
• Regulators > GOV > Control > GOV decrease
The alarm action is Warning and the alarm remains active until the configuration is corrected.
The alarm is always enabled. The alarm parameters are not visible.

7.7.2 AVR relay setup incomplete
The alarm is based on the Input/output configuration of the controller. The controller activates the alarm when only one of the
following digital outputs are configured:
• Regulators > AVR > Control > AVR increase
• Regulators > AVR > Control > AVR decrease
The alarm action is Warning and the alarm remains active until the configuration is corrected.
The alarm is always enabled. The alarm parameters are not visible.
7.7.3 GOV output selection failure
The controller activates the alarm if an output, either relay or analogue, was selected as the regulation output, but the selected
output is then removed from the Input/output configuration.
The alarm remains active until either:

• The deleted output is added to the Input/output configuration
• The correct manual output is selected under Regulators > GOV general configuration > Regulator output >
Output type
7.7.4 AVR output selection failure
The controller activates the alarm if an output, either relay or analogue, was selected as the regulation output, but the selected
output is then removed from the Input/output configuration.
The alarm remains active until either:

• The deleted output is added to the Input/output configuration
• The correct manual output is selected under Regulators > AVR: common settings > Regulator output > Output
type
7.7.5 GOV stand-alone configuration error
The controller activates this alarm if a GAM3.2 is present, but the GAM3.2 does not have inputs and outputs that are correctly
configured for governor stand-alone mode.
The following configuration is required for governor stand-alone mode:

• One governor regulation output on the GAM3.2. For example:
◦ Two regulation digital outputs (GOV increase and GOV decrease).
◦ One regulation analogue output (AO or PWM, GOV output [%]).
• If an analogue governor regulation output is used, the slope of the output curve must be positive.
◦ That is, there must be a lower governor output % for a lower voltage or current, and a higher governor output % for a higher
voltage or current.
• No governor regulation outputs on any other hardware modules.
• A Manual GOV increase digital input on the GAM3.2.
• A Manual GOV decrease digital input on the GAM3.2.
• The Regulators > GOV > Modes > Stand-alone mode digital input on the GAM3.2
• The parameter Regulators > GOV general configuration > Stand-alone configuration > GOV stand-
alone activation must be configured High or Low.

◦ If using the AVR stand-alone on the same input, this GOV setting must be set the same as the AVR stand-alone activation,
otherwise a configuration conflict alarm activates. Both must be configured High or Low. If one is High and the other Low, the
alarm activates.
Parameters
Regulators > GOV general configuration > Stand-alone configuration error
Delay 0 s to 1 h 1 min
7.7.6 AVR stand-alone configuration error
The controller activates this alarm if a GAM3.2 is present, but the GAM3.2 does not have inputs and outputs that are correctly
configured for AVR stand-alone mode.
The following configuration is required for AVR stand-alone mode:

• One AVR regulation output on the GAM3.2. For example:
◦ Two regulation digital outputs (AVR increase and AVR decrease).
◦ One regulation analogue output (AO or PWM, AVR output [%]).
• If an analogue AVR regulation output is used, the slope of the output curve must be positive.
◦ That is, there must be a lower AVR output % for a lower voltage or current, and a higher AVR output % for a higher voltage or
current.
• No AVR regulation outputs on any other hardware modules.
• A Manual AVR increase digital input on the GAM3.2.
• A Manual AVR decrease digital input on the GAM3.2.
• The Regulators > AVR > Modes > Stand-alone mode digital input on the GAM3.2.
• The parameter Regulators > AVR general configuration > Stand-alone configuration > AVR stand-
alone activation must be configured High or Low.
◦ If using the GOV stand-alone on the same input, this AVR setting must be set the same as the GOV stand-alone activation,
otherwise a configuration conflict alarm activates. Both must be configured High or Low. If one is High and the other Low, the
alarm activates.
Parameters
Regulators > AVR general configuration > Stand-alone configuration error
Delay 0 s to 1 h 1 min
7.8 Regulation alarms

7.8.1 GOV regulation error
This alarm shows when there is an error with the governor controlled regulation.
The alarm is based on the difference between the measured value and the required set point, as a percentage of the set point. The
larger the set point, the more the measured value is allowed to differ from the set point.
The alarm activates if the measured value is outside of the permitted range for longer than the delay.

This alarm is not activated when the genset frequency swings in and out of the permitted range above and below the set point. This
is because this alarm only activates when the measured value is constantly above the upper limit, or constantly below the lower limit
for the entire delay period.
Parameters
Do not set the alarm set point lower than the deadband percentage for relay regulation. Doing so might activate the alarm in an area
where regulation is not possible.
Regulators > GOV monitoring > Regulation error

Set point (absolute value) 1 to 100 % regulation deviation 30 %

Alarm deviation examples
1. The controller is trying to control the genset to run at 50 Hz, and the measured frequency is 49.5 Hz.
• The deviation from the set point is |(49.5 Hz - 50 Hz)| / 50 Hz =0.01 = 1 %.
• The deviation is less than the alarm set point, and the alarm is not activated.
2. The controller is trying to control the genset to run at 60 Hz and the measured speed is 62 Hz.
• The deviation from the set point is |(62 Hz - 60 Hz)| / 60 Hz = 0.03 = 3.3 %.
3. The controller is controlling 1500 kW genset, and is running fixed power regulation with a set point of 1000 kW. The
measured power is 600 kW.
• The deviation from the set point is |(600 kW - 1000 kW)| / 1000 kW = 0.4 = 40 %
• The deviation is more than the alarm set point. If the measured power is stays below 700 kW for longer than the
delay, then the alarm activates.
7.8.2 AVR regulation error
This alarm shows when there is an error with the AVR controlled regulation.
The alarm is based on the difference between the measured value and the required set point, as a percentage of the set point. The
larger the set point, the more the measured value is allowed to differ from the set point.
The alarm activates if the measured value is outside of the permitted range for longer than the delay.
This alarm is not activated when the genset voltage swings in and out of the permitted range above and below the set point. This is
because this alarm only activates when the measured value is constantly above the upper limit, or constantly below the lower limit
for the entire delay period.
Parameters
Do not set the alarm set point lower than the deadband percentage for relay regulation. Doing so might activate the alarm in an area
where regulation is not possible.
Regulators > AVR monitoring > Regulation error

Set point (absolute value) 1 to 100 % regulation deviation 30 %


Alarm deviation examples
1. The controller is running fixed voltage regulation with a set point of 400 V, and the measured voltage is 250 V.
• The deviation from the set point is |(250 V - 400 V)| / 400 V × 100 = 38 %.
• The deviation is more than the alarm set point. If the measured power is stays below 280 V for longer than the
delay, then the alarm activates.
2. The controller is running fixed reactive power regulation with a set point of 0 % of nominal reactive power, and the
measured value is 2 % of nominal reactive power.
• The deviation from the set point is 2 %.
3. The controller is running fixed cos phi regulation with a set point of 0.9 I, and the measured value is 0.95 C.
• The deviation from the set point is |(0.95 C - 0.9 I)| / 0.9 I × 100 = 17 %.
7.8.3 GOV regulation mode not selected
This alarm can only be activated if a governor output is configured.
When the genset is running and the generator breaker is closed, a governor regulation mode must be selected when the controller is
not under switchboard control.
The regulation mode can be one of the following:
• Fixed frequency
• Fixed power
• Power load sharing
• Frequency droop
• Manual regulation
If a regulation mode is not selected within the alarm delay, the alarm is activated. While no governor regulation mode is selected, no
regulation will take place.
Parameters
Regulators > GOV monitoring
Delay 0 s to 1 h 2s
7.8.4 AVR regulator mode not selected
This alarm can only be activated if an AVR output is configured.
When the genset is running and the generator breaker is closed, an AVR regulation mode must be selected when the controller is
not under switchboard control.

The regulation mode can be one of the following:
• Fixed voltage
• Fixed reactive power
• Fixed cos phi
• Reactive power load sharing
• Voltage droop
• Manual regulation
If a regulation mode is not selected within the alarm delay, the alarm is activated. While no AVR regulation mode is selected, no
regulation will take place.
Parameters
Regulators > AVR monitoring
Delay 0 s to 1 h 2s
7.8.5 P load sharing failure
This alarm is for genset active power load sharing failure.
percentage of the genset nominal power.
The controller activates the alarm if the difference between the reference and measured values is outside the activation range for
longer than the delay.
delay time.
Regulators > GOV monitoring > P load sharing failure

7.8.6 Q load sharing failure
This alarm is for genset reactive power load sharing failure.
percentage of the genset nominal reactive power.
The controller activates the alarm if the difference between the reference and measured values is outside the activation range for a
time longer than the delay.

delay time.
Regulators > AVR monitoring > Q load sharing failure


8. Engine interface communication
8.1 About
8.1.1 How it works
The controller can receive information from an ECU using the CAN bus communication. The information can be used as input for the
controller functions. The controller also uses the information as display values, alarms, and as values to be transmitted through
Modbus.
Display
Switchboard control P1
1
Home 12:00
SCADA
Configure Tools Info
Log on Alarm Log Live data
2
AMS
External network
External network
1
Extension Controller 2
CAN bus communication to ECU

PSM3.2
PSM3.1
PCM
AVR ECU
IN IN 4
OUT OUT 5
EtherCAT
GOV
Standard network (sub-ring)
1
Controller 2
PCM
PSM
Table 8.1
No. Notes
1 CAN bus communication to ECU
2 DEIF network communication to controllers, displays, AMS.
3 Internal communication to extension racks.
Most of the engine communication protocols are based on the SAE J1939 standard. J1939 is a very large standard, and most of it is
irrelevant to engine communication. The controller supports only relevant parts of J1939, as described in Generic J1939.
The ECU is wired to the CAN bus A communication on the controller's PCM3.1 module. The ECU is added to the controller using
the Fieldbus configuration and assigned the source address.

More information
See CAN bus A communication wiring in the Installation instructions for more information about how to wire an ECU
to the controller.
Once added to your controller, the ECU can be accessed from PICUS or the display as an additional hardware selection. For
example, you can configure the ECU input or output settings, functions, or alarms. You can also include the ECU on the I/O status
page to see the status of the analogue inputs, or see the ECU on Live data. Alarms (DM1) and logs (DM2) can also be accessed.
Priority of engine information with an ECU and analogue input values

A controller can be configured with both an ECU and an EIM3.1 using analogue inputs for values like Engine oil pressure, Coolant
level, and more. In this situation, the analogue input values have first priority over the ECU values. If the analogue input values are
not able to be read, the controller uses the ECU values in their place.
8.1.2 Example configuration for an ECU
This example shows how to configure an ECU to read and use the value of the engine oil level.
PGN: Parameter group number

SPN: Suspect parameter number
P: J1939 priority
S: Object's start bit in the CAN telegram
L: Object's length. By default, the value is in bits.
Unit: Unit in display (bar/°C can be changed to psi/°F)
Engine > ECU > Lube oil

Text PGN S L P SPN Unit J1939-71 scaling Offset
Engine oil level 65263 16 8 6 98 % 0.4 %/bit 0.0 %
Add the ECU

The ECU is added to the controller by using the Fieldbus configuration.
1. Launch PICUS and connect to the controller.
2. Open the Fieldbus configuration page:

• Configure > Fieldbus configuration
3. Select the controller rack:
•
4. Under CAN A, select the protocol Generic J1939.
5. Enter the source address, if different from the default address 0.
6. Select Write to update the controller.

Configure the ECU power setting (optional)
The default ECU Power setting is Auto, which uses either the engine run coil setting, ECU Power digital output, or otherwise
assumes the power is always on.
1. If required, use PICUS to configure the ECU Power configuration:

• Configure > Parameters > Communication> Fieldbus > CAN bus > ECU > ECU Power configuration
2. Configure the setting as required.
Access ECU information with PICUS or display

The ECU can now be accessed on different pages in PICUS or the display as an additional hardware selection.
• Live data
◦ Additional panel for engine speed, coolant temperature, and oil pressure.
• Input/output functions
◦ Digital inputs or Supervised binary inputs
◦ Analogue outputs
• Alarms (DM1)
• Logs (DM2)
How to configure ECU functions and custom alarms on input/output
1. Use PICUS to access the Input/output page:

• Configure > Input/output
2. Select the ECU under the hardware selection:
•
3. The ECU information is now shown.
4. You can now:
• Configure functions
• Configure the sensor setup for the curve/function
• Create and configure custom alarms
5. Select Save to save the changes in PICUS.
View the ECU values on I/O status

You can also see the ECU values in PICUS on the I/O status page.
1. Use PICUS to see the I/O status page.

2. Select the ECU under Select hardware, and also select Show physical values:
•
3. The ECU Engine oil level can be found in the list:

•
Use the ECU values in CustomLogic

You can also use the ECU Engine oil level in CustomLogic as a function, for example with a Compare block:
More information
See Fieldbus configuration in the PICUS manual for how to configure and supervise Fieldbus.
8.2 Generic J1939

8.2.1 J1939 measurements
These are the J1939 measurements that the controller supports. Not all measurements are supported by all engines (see the
specific engine description).
By default, the engine is expected to use source address 0 (the most commonly used setting on ECUs). If a different source address
is required, you can configure it on the Fieldbus configuration page and assign a different source address. The range is 0 to 255.
PGN: Parameter group number

SPN: Suspect parameter number
P: J1939 priority
S: Object's start bit in the CAN telegram
L: Object's length. By default, the value is in bits.
Unit: Unit in display (bar/°C can be changed to psi/°F)
Measurements can be viewed in PICUS on the I/O status page by selecting the configured ECU.
Measurements can be read from the Modbus tables.
You can also configure an Analogue Output function to read the measurement:
Engine > ECU > Air ambient

Atmospheric pressure 65269 0 8 6 108 kPa 0.5 kPa/bit 0.0 kPa
Ambient air temperature 65269 24 16 6 171 °C 0.03125 °C/bit -273.0 °C

Engine > ECU > Coolant
Engine coolant temperature 65262 0 8 6 110 °C 1.0 °C/bit -40.0 °C
Coolant level 65263 56 8 6 111 % 0.4 %/bit 0.0 %
Coolant pressure 65263 48 8 6 109 kPa 2.0 kPa/bit 0.0 kPa
Coolant filter differential pressure 65270 56 8 6 112 kPa 0.5 kPa/bit 0.0 kPa
Engine coolant temperature 2 64870 0 8 6 4076 °C 1.0 °C/bit -40.0 °C
Engine coolant temperature 3 64870 56 8 6 6209 °C 1.0 °C/bit -40.0 °C
Engine coolant pump outlet temperature 64870 8 8 6 4193 °C 1.0 °C/bit -40.0 °C
Engine auxiliary coolant temperature 65172 8 8 6 1212 °C 1.0 °C/bit -40.0 °C
Engine auxiliary coolant pressure 65172 0 8 6 1203 kPa 4.0 kPa/bit 0.0 kPa
Engine > ECU > DPF

Diesel particulate filter lamp command 64892 0 3 6 3697 1.0 /bit 0.0
Diesel particulate filter active

64892 10 2 6 3700 1.0 /bit 0.0
regeneration status
Diesel particulate filter regeneration

64892 12 3 6 3701 1.0 /bit 0.0
status
Diesel particulate filter active

64892 18 2 6 3703 1.0 /bit 0.0
regeneration inhibited
Aftertreatment 1 diesel exhaust fluid tank

65110 0 8 6 1761 % 0.4 %/bit 0.0 %
level
Aftertreatment 1 diesel exhaust fluid tank

65110 8 8 6 3031 °C 1.0 °C/bit -40.0 °C
temperature
Aftertreatment 1 intake NOx 61454 0 16 6 3216 ppm 0.05 ppm/bit -200.0 ppm
Aftertreatment 1 outlet NOx 61455 0 16 6 3226 ppm 0.05 ppm/bit -200.0 ppm
Aftertreatment 1 DEF actual dosing

61475 0 16 3 4331 g/h 0.3 g/h/bit 0.0 g/h
quantity
Aftertreatment 1 DEF doser absolute

61475 40 8 3 4334 kPa 8.0 kPa/bit 0.0 kPa
pressure
Aftertreatment 1 SCR dosing air assist

64833 8 8 6 4336 % 0.4 %/bit 0.0 %
valve
Aftertreatment 1 DEF dosing requested

61476 0 16 3 4348 g/h 0.3 g/h/bit 0.0 g/h
quantity
Aftertreatment 1 SCR catalyst intake gas

64830 0 16 5 4360 °C 0.03125 °C/bit -273.0 °C
temperature
Aftertreatment 1 SCR catalyst outlet gas

64830 24 16 5 4363 °C 0.03125 °C/bit -273.0 °C
temperature
Aftertreatment 2 intake NOx 61456 0 16 6 3255 ppm 0.05 ppm/bit -200.0 ppm
Aftertreatment 2 outlet NOx 61457 0 16 6 3265 ppm 0.05 ppm/bit -200.0 ppm
Aftertreatment 2 DEF actual dosing

61478 0 16 3 4384 g/h 0.3 g/h/bit 0.0 g/h
quantity
Aftertreatment 2 DEF dosing absolute

61478 40 8 3 4387 kPa 8.0 kPa/bit 0.0 kPa
pressure

Aftertreatment 2 SCR dosing air assist

64827 8 8 6 4389 % 0.4 %/bit 0.0 %
valve
Aftertreatment 2 DEF dosing requested

61479 0 16 3 4401 g/h 0.3 g/h/bit 0.0 g/h
quantity
Aftertreatment 2 SCR catalyst intake gas

64824 0 16 6 4413 °C 0.03125 °C/bit -273.0 °C
temperature
Aftertreatment 2 SCR catalyst outlet gas

64824 24 16 6 4415 °C 0.03125 °C/bit -273.0 °C
temperature
Aftertreatment SCR operator inducement

65110 37 3 6 5245 1.0 /bit 0.0
active
Aftertreatment SCR operator inducement

65110 45 3 6 5246 1.0 /bit 0.0
severity
Aftertreatment 1 DPF outlet gas

64947 16 16 6 3246 °C 0.03125 °C/bit -273.0 °C
temperature
Aftertreatment 1 DPF time to next active 0.000277777777777

64697 0 32 6 5978 h 0.0 h
regeneration 7778 h/bit
Diesel particulate filter 1 soot load

64891 0 8 6 3719 % 1.0 %/bit 0.0 %
percent
Aftertreatment 1 DEF average

64878 0 16 6 3826 L/h 0.05 L/h/bit 0.0 L/h
consumption
Aftertreatment 1 intake percent oxygen

61454 16 16 6 3217 % 0.000514 %/bit -12.0 %
1
Aftertreatment 1 outlet percent oxygen 1 61455 16 16 6 3227 % 0.000514 %/bit -12.0 %
Engine > ECU > Engine counters

Engine Hours 65253 0 32 6 247 h 0.05 h/bit 0.0 h
Trip engine running time 65200 64 32 7 1036 h 0.05 h/bit 0.0 h
Trip idle time 65200 16 32 7 1037 h 0.05 h/bit 0.0 h
Engine > ECU > Engine load

Drivers demand engine percent torque 61444 8 8 3 512 % 1.0 %/bit -125.0 %
Actual engine - percent torque 61444 16 8 3 513 % 1.0 %/bit -125.0 %
Percent load at current speed 61443 16 8 3 92 % 1.0 %/bit 0.0 %
Nominal power 65214 0 16 7 166 kW 0.5 kW/bit 0.0 kW
Nominal friction - percent torque 65247 0 8 6 514 % 1.0 %/bit -125.0 %
Engine demand - percent torque 61444 56 8 3 2432 % 1.0 %/bit -125.0 %
Engine > ECU > Exhaust gas

Exhaust gas temperature 65270 40 16 6 173 °C 0.03125 °C/bit -273.0 °C
Particulate trap inlet pressure 65270 0 8 6 81 kPa 0.5 kPa/bit 0.0 kPa
Exhaust temperature right 65031 0 16 6 2433 °C 0.03125 °C/bit -273.0 °C

Exhaust temperature left 65031 16 16 6 2434 °C 0.03125 °C/bit -273.0 °C
Exhaust port temperature 01 65187 0 16 7 1137 °C 0.03125 °C/bit -273.0 °C
Engine exhaust gas oxygen sensor

64841 32 4 6 4240 1.0 /bit 0.0
closed loop operation
Engine > ECU > Fuel

Fuel temperature 65262 8 8 6 174 °C 1.0 °C/bit -40.0 °C
Fuel rate 65266 0 16 6 183 L/h 0.05 L/h/bit 0.0 L/h
Fuel delivery pressure 65263 0 8 6 94 kPa 4.0 kPa/bit 0.0 kPa
Water in fuel indicator 65279 0 2 6 97 1.0 /bit 0.0
Engine trip fuel 65257 0 32 6 182 L 0.5 L/bit 0.0 L
Engine total fuel used 65257 32 32 6 250 L 0.5 L/bit 0.0 L
Trip fuel gaseous 65199 0 32 7 1039 kg 0.5 kg/bit 0.0 kg
Total fuel used gaseous 65199 32 32 7 1040 kg 0.5 kg/bit 0.0 kg
Mean trip fuel consumption 65203 32 16 7 1029 L/h 0.05 L/h/bit 0.0 L/h
Fuel supply pump inlet pressure 65130 8 8 6 1381 kPa 2.0 kPa/bit 0.0 kPa
Fuel filter (suction side) differential

65130 16 8 6 1382 kPa 2.0 kPa/bit 0.0 kPa
pressure
Engine fuel filter differential pressure 65276 16 8 6 95 kPa 2.0 kPa/bit 0.0 kPa
Engine filtered fuel delivery pressure 64735 8 8 6 5579 kPa 4.0 kPa/bit 0.0 kPa

Engine > ECU > Information
Number of actual faults 65230 0 8 6 1218 1.0 /bit 0.0
Battery potential voltage switched 65271 48 16 6 158 V DC 0.05 V DC/bit 0.0 V DC
Crankcase pressure 65263 32 16 6 101 kPa 0.0078125 kPa/bit -250.0 kPa
Exhaust system high temperature lamp

64892 50 3 6 3698 1.0 /bit 0.0
command
Engine ECU temperature 65188 16 16 6 1136 °C 0.03125 °C/bit -273.0 °C
Ambient conditions 2 specific humidity 64992 16 16 6 4490 g/kg 0.01 g/kg/bit 0.0 g/kg
Engines desired operating speed 65247 8 16 6 515 RPM 0.125 RPM/bit 0.0 RPM
Engine operating state 64914 0 4 3 3543 1.0 /bit 0.0
Source address of controlling device 61444 40 8 3 1483 1.0 /bit 0.0
ECU identification information 64965 -8 1600 6 2902 1.0 /bit 0.0
Engine operating derate request 64914 56 8 3 3644 % 0.4 %/bit 0.0 %
SW identification 65242 8 1600 6 234 1.0 /bit 0.0
Engine throttle actuator 1 control

61466 0 16 4 3464 % 0.0025 %/bit 0.0 %
command
Long-term fuel trim 64841 0 16 6 4237 % 0.1 %/bit -100.0 %
Short-term fuel trim 64841 16 16 6 4236 % 0.1 %/bit -100.0 %
Engine desired ignition timing no 1 65159 0 16 7 1433 ° 0.0078125 °/bit -200.0 °
Engine actual ignition timing 65159 48 16 7 1436 ° 0.0078125 °/bit -200.0 °
Engine amber warning lamp command 64775 2 2 6 5078 1.0 /bit 0.0
Engine red stop lamp command 64775 4 2 6 5079 1.0 /bit 0.0
Engine > ECU > Intake

Boost pressure 65270 8 8 6 102 kPa 2.0 kPa/bit 0.0 kPa
Air inlet temperature 65269 40 8 6 172 °C 1.0 °C/bit -40.0 °C
Engine intake manifold 1 temperature 65270 16 8 6 105 °C 1.0 °C/bit -40.0 °C
Air inlet pressure 65270 24 8 6 106 kPa 2.0 kPa/bit 0.0 kPa
Air filter differential pressure 65270 32 8 6 107 kPa 0.05 kPa/bit 0.0 kPa
Engine intercooler temperature 65262 48 8 6 52 °C 1.0 °C/bit -40.0 °C
Engine intake manifold 1 absolute

64976 32 8 6 3563 kPa 2.0 kPa/bit 0.0 kPa
pressure
Air filter differential pressure 2 64976 0 8 6 2809 kPa 0.05 kPa/bit 0.0 kPa
Engine intake manifold 2 temperature 65189 0 8 7 1131 °C 1.0 °C/bit -40.0 °C
Engine charge air cooler 1 outlet

65129 48 16 6 2630 °C 0.03125 °C/bit -273.0 °C
temperature
Engine > ECU > Lube oil

Engine oil pressure 65263 24 8 6 100 kPa 4.0 kPa/bit 0.0 kPa
Engine oil temperature 65262 16 16 6 175 °C 0.03125 °C/bit -273.0 °C

Engine oil filter differential pressure 65276 24 8 6 99 kPa 0.5 kPa/bit 0.0 kPa
Engine oil level 65263 16 8 6 98 % 0.4 %/bit 0.0 %
Engine oil-filter outlet pressure 65130 32 8 6 3549 kPa 4.0 kPa/bit 0.0 kPa
Engine > ECU > Speed

Engine speed 61444 24 16 3 190 RPM 0.125 RPM/bit 0.0 RPM
Accelerator pedal position 61443 8 8 3 91 % 0.4 %/bit 0.0 %
Engine rated speed 65214 16 16 7 189 RPM 0.125 RPM/bit 0.0 RPM
Engine speed at idle point 1 65251 0 16 6 188 RPM 0.125 RPM/bit 0.0 RPM
Engine > ECU > Turbo charger

Turbo oil temperature 65262 32 16 6 176 °C 0.03125 °C/bit -273.0 °C
Engine turbocharger 1 turbine intake

65176 0 16 6 1180 °C 0.03125 °C/bit -273.0 °C
temperature
Engine turbocharger 2 turbine intake

65176 16 16 6 1181 °C 0.03125 °C/bit -273.0 °C
temperature
Engine turbocharger 1 speed 65245 8 16 6 103 RPM 4.0 RPM/bit 0.0 RPM
8.3 ECU functions

8.3.1 ECU Power configuration
This configures how the controller expects the ECU to be powered. The ECU can be powered by:
• The engine run coil digital output
• The ECU Power digital output function (see below)
• Externally powered
The ECU must be configured in the Fieldbus configuration for the functions and alarms to be shown.
Digital output
Function Type Details
Engine > Control > ECU Power Continuous Connect this to the ECU power control.
Parameter
Communication> Fieldbus > CAN bus > ECU > ECU Power configuration
Range Default Comment
Auto : The controller expects either the engine run coil or ECU power digital output. If neither of these
Auto, Always are configured it is expected to be always on.
Auto
ON
Always ON : The controller expects the ECU is powered externally and is always powered on.

8.4 ECU protections
8.4.1 ECU Communication failure alarm
Communication > Fieldbus > CAN bus > ECU > ECU Communication failure
Delay 0 s to 120 s 1s
8.4.2 ECU CAN bus off
Alarm parameters
Communication > Fieldbus > CAN bus > Bus off > CAN-A bus off
Enable - Enabled
Communication > Fieldbus > CAN bus > Bus off > CAN-B bus off
Enable - Enabled
8.4.3 ECU Red stop lamp alarm
Engine > ECU > Diagnostic alarms > ECU Red stop lamp
Enable - Enabled *
Latch - Enabled *
Alarm action Trip generator breaker and shutdown engine
Engine > ECU > Diagnostic alarms > ECU Red stop lamp (ECU2)
Enable - Enabled *
Latch - Enabled *
Alarm action Trip generator breaker and shutdown engine
NOTE * Always enabled and cannot be changed.

8.4.4 ECU Amber warning lamp alarm
Engine > ECU > Diagnostic alarms > ECU Amber warning lamp
Enable - Enabled *
Engine > ECU > Diagnostic alarms > ECU Amber warning lamp (ECU2)
Enable - Enabled *
8.4.5 ECU Protect lamp alarm
Engine > ECU > Diagnostic alarms > ECU Protect lamp
Enable - Enabled *
Latch - Enabled *
Engine > ECU > Diagnostic alarms > ECU Protect lamp (ECU2)
Enable - Enabled *
Latch - Enabled *
8.4.6 ECU Malfunction indicator lamp alarm
Engine > ECU > Diagnostic alarms > ECU Malfunction indicator lamp
Enable - Enabled *
Engine > ECU > Diagnostic alarms > ECU Malfunction indicator lamp (ECU2)
Enable - Enabled *


9. GENSET controller
9.1 About the GENSET controller

A GENSET controller controls and protects a diesel engine and generator (that is, a genset), as well as the generator breaker. A
system can include a number of GENSET controllers.
Each GENSET controller can connect up to three non-essential load groups (NEL).
Example application with non-essential loads
9.1.1 GENSET controller functions
Functions
• Genset start sequence and genset stop sequence

◦ Running detection (Multiple feedback options: Frequency, MPU/W/NPN/PNP (RPM), Digital
input, Oil pressure)
◦ Run coil and/or stop coil for engine control
Pre-programmed
◦ Temperature-dependent cooldown
sequences
• Breaker sequences
◦ Generator breaker close sequence (with synchronisation)
◦ Generator breaker open sequence (with de-loading)
• Generator breaker blackout close
• PID regulators for analogue outputs

• P regulators for relay outputs
◦ Relay period time and Minimum ON time configurable
Genset regulation • Set point selection
◦ Select mode or external set point, using digital input, Modbus, and/or CustomLogic or
CODESYS
• Governor modes

Functions
◦ Fixed frequency
◦ Fixed active power
◦ Active power load sharing
◦ Frequency droop (controller regulation emulates droop)
◦ External set point: Frequency offset, or Power set point
◦ Manual
◦ Off
• AVR modes
◦ Fixed voltage
◦ Fixed reactive power
◦ Fixed cos phi
◦ Reactive power load sharing
◦ Voltage droop (controller regulation emulates droop)
◦ External set point: Voltage offset, Reactive power set point, or cos phi set point
◦ Manual
◦ Off
• External set point
◦ From the network, to synchronise/de-load another controller
◦ From Modbus
• Configurable: Power ramp up, power ramp down
• Temperature-dependent power derate settings
• Optional inputs: Manual regulation
4th current Measurement for earth or neutral protections
• Display unit counters, to edit or reset

◦ Start attempts
◦ Running hours (total and trip)
◦ Running minutes (total and trip)
Counters ◦ Breaker operations and trips
◦ Energy export (active and reactive)
◦ External breaker operations
• Energy counters with configurable digital outputs (for external counters)
◦ Energy export to system (active and reactive)
Other sequences • Priming sequence
9.2 GENSET controller principles

9.2.1 GENSET controller nominal settings
The controller nominal settings are used in a number of key functions. For example, many protection settings are based on a
percentage of the nominal settings.
[Source] nominal settings

[Source] > Nominal settings > Nominal settings # *
Nominal setting Range Default Notes
Voltage (V) 10 V to 150 kV 400 V The phase-to-phase ** nominal AC voltage for the genset.
The maximum current flow in one phase (that is, L1, L2 or L3) from the
Current (I) 1 A to 9 kA 866 A
genset during normal operation.

The system nominal frequency, typically either 50 Hz or 60 Hz. All the

Frequency (f) 20 to 100 Hz 50 Hz
controllers in the system should have the same nominal frequency.
Power (P) 1 kW to 0.9 GW 480 kW The nominal active power may be on the genset nameplate.
The nominal apparent power should be on the genset or generator

Apparent power (S) 1 kVA to 1 GVA 600 kVA
nameplate.
Power factor (PF) 0.6 to 1 0.8 The power factor should be on the genset or generator nameplate.
** In a single-phase set up the nominal AC voltage is phase-to-neutral.

Calculation method Options Default
Q nominal calculated
Reactive power (Q) nominal Q nominal = P nominal Q nominal calculated
Q nominal = S nominal
No calculation
P or S nominal P nominal calculated No calculation
S nominal calculated
More information
See Nominal power calculations for how these are used.
Busbar nominal settings

Busbar > Nominal settings > Nominal settings # *
Use generator nominal voltage:

• The phase-to-phase nominal voltage for the busbar is the same as
Use generator Use generator
Nominal value the generator nominal voltage.
nominal voltage nominal
source User defined:
User defined voltage
• You can configure the phase-to-phase nominal voltage for the
busbar.
The phase-to-phase nominal voltage for the busbar. If there are no

Voltage (V) ** 10 V to 150 kV 400 V transformers between the genset and the busbar, the nominal voltage
for the busbar will be the same as the nominal voltage for the genset.
** The Nominal value source must be configured as User defined and written to the controller, for the nominal
voltage setting to be visible.
9.2.2 Run coil or stop coil
The engine start and stop functions are suitable for genset start systems with either a run coil or a stop coil. Marine classification
societies generally require stop coil systems. A set of controller digital output terminals must be connected to and configured for
either the run coil output, or the stop coil output.

Digital outputs
For a Stop coil, if wire break detection is required, use EIM relay 4 ( * ) (terminals 9,10).
Run coil and stop coil outputs

If all power to the controller is lost, then the genset stops.

Engine > Control > Run
coil
Required if there is no Stop coil.
If all power to the controller is lost, then the genset keeps running.
Engine > Control > Stop
coil
Required if there is no Run coil.
9.2.3 Running detection
The controller can be configured to receive engine running feedback from a variety of measurements. There can be more than one
running feedback measurement.
Running detection is a state calculated by the controller, and used by a number of functions. It is either OFF or ON. If any running
feedback measurements show that the engine is running, then Running detection is ON.
Inputs and outputs

Engine > Feedback > Digital Optional. External equipment activates the digital input
running detection when the engine is running.
The controller can also use the following inputs for running feedback.
Always present. The controller uses the generator voltage measurements

to calculate the frequency. The controller then compares the frequency
with the detection set point.
Generator voltage
Frequency Continuous Note: The controller cannot measure the frequency at very low voltages.
measurements
See the Data sheet for the measurement range. The voltage must also
be at least 10 % of nominal for the controller to use the frequency for
running detection. For safety, DEIF recommends that you install at least
one other running detection input.
Optional. The MPU input (on the first EIM3.1 in the controller rack) is
MPU HSDI Continuous
connected to an MPU mounted on the engine.
Optional. The W input (on the first EIM3.1 in the controller rack) is
connected to the battery recharging generator and measures the engine
W HSDI Continuous
speed. Alternatively, the W input can be connected to an NPN/PNP
sensor.
Engine >
Running Pressure in Optional. This set of analogue input terminals are connected to a
Analogue input
detection > bar transducer for the engine oil pressure.
Oil [bar]

Parameters
Engine > Nominal settings > Nominal settings # *
Nominal Nominal Nominal Nominal
Parameter Range Comment
setting 1 setting 2 setting 3 setting 4
When an MPU/W/NPN/PNP is used

100 to to measure the engine speed, then
Nominal
50000 1500 RPM 1500 RPM 1800 RPM 1800 RPM the nominal engine speed is used for
RPM
RPM the overspeed and underspeed
alarms.
Engine > Nominal settings > Nominal settings # > Number of teeth *
Number of magnetic The controller uses the number of teeth to calculate the engine speed from
1 to 10000 1
pickup teeth the MPU/W/NPN/PNP measurement signal.
Engine > Running detection > Feedback type
Select one of the inputs as the primary running feedback.

Primary The available running
running feedbacks (depends on Frequency If the Primary running feedback does not detect running, but any other
feedback hardware) running feedback detects running, then the controller activates the
Primary running feedback failure alarm.
Engine > Running detection > Detection set point

Running detection is ON when the engine speed measured by the

MPU 0 to 50000 RPM 1000 RPM
MPU/W/NPN/PNP input is above this set point.
Running detection is ON when the frequency measured by the generator

voltage measurements is above this set point.
Frequency 10 to 100 Hz 32 Hz
For example: For a 60 Hz system, you can use a detection set point of 45 Hz.
Not enabled: The MPU/W/NPN/PNP measurement (connected to the first

Use magnetic Not enabled, EIM3.1 in the controller rack) is ignored and not used for running detection.
Enabled
pickup Enabled Enabled: The MPU/W/NPN/PNP measurement (connected to the first EIM3.1
in the controller rack) is used as a running detection input.
Running detection is ON when the engine oil pressure measured by the

Oil pressure ** 0 to 10 bar 3 bar
analogue input is above this set point.
Not enabled: The engine oil pressure is ignored and not used for running
Use oil Not enabled,
Enabled detection.
pressure ** Enabled
Enabled: The engine oil pressure is used as a running detection input.
NOTE ** This parameter is only visible if the analogue input is configured.

Frequency running detection hysteresis
For stable operation, running detection has a fixed 2 Hz hysteresis.
Frequency running detection hysteresis examples

Example 1: The detection set point for frequency is 32 Hz. When the frequency rises above 32 Hz, running detection
changes to ON. However, the frequency has to drop below 30 Hz for running detection to change to OFF.
Example 2: The detection set point for frequency is 45 Hz. When the frequency rises above 45 Hz, running detection
changes to ON. However, the frequency has to drop below 43 Hz for running detection to change to OFF.
MPU/W input running detection hysteresis

For stable operation, running detection has a fixed 5 % hysteresis on the genset RPM.
Oil pressure running detection hysteresis

For stable operation, running detection has a fixed 5 % hysteresis on the oil pressure.
Example: Running detection ON

The following sequence diagram is an example of how Running detection changes during an engine start. Running detection
changes from OFF to ON when one running feedback detects that the engine is running.
Figure 9.1 Running detection ON sequence diagram
(1) Frequency Set point
Set point
(2) RPM
Digital
(3) running
detection
Running
(4)
detection
1. Frequency: The engine starts and the frequency rises above the set point.
2. RPM: (MPU/W/NPN/PNP input). The engine starts and the RPM rises above the set point.
3. Digital running detection: Engine > Feedback > Digital running detection (digital input). In the example, the response of this
input is slower than the other running detection inputs.
4. Running detection: Running detection changes from OFF to ON when any running feedback (in this case, the frequency) rises
above the Detection set point.
Example: Running detection OFF

The following sequence diagram is an example of how Running detection changes during an engine stop. Running detection
changes from ON to OFF when none of the running feedbacks detect that the engine is running.

Figure 9.2 Running detection OFF sequence diagram
(1) Frequency Set point
Set point
(2) RPM
Digital
(3) running
detection
Running
(4)
detection
1. Frequency: The engine slows down and the frequency drops to 2 Hz below the set point.
2. RPM: (MPU/W/NPN/PNP input). The engine slows down and the RPM drops to 5 % below the set point.
3. Digital running detection: Engine > Feedback > Digital running detection (digital input). In the example, the response of this
input is slower than the other running detection inputs.
4. Running detection: Running detection changes from ON to OFF when none of the running feedbacks detect that the engine is
running.
Risks when using only frequency for running detection

It is possible to only use frequency for running detection. However, using only frequency for running detection increases the risk of
not detecting that the genset is running.
The software only uses the frequency measurements when the voltage is at least 10 % of the nominal voltage. This could cause
trouble, since the voltage does not necessarily increase linearly with speed (this depends on the AVR).
If the frequency curve for the genset start up has a dip around the detection set point, the controller can interpret the dip as no
running detection, and stop the genset. Increasing or decreasing the set point away from the dip would solve this problem.
Frequency running detection example
A genset start up frequency curve is given below.
Frequency
[Hz]
50
4
40 3
2
30
20
1
10
0 1 2 3 4 Time
[s]
1. Crank begins.
2. Fuel in.
3. If the running detection set point is 30 Hz, running detection is ON.

4. If the running detection set point is 30 Hz, the frequency drops 2 Hz below the set point, and running detection from
frequency is OFF.
• If there are no other running detection inputs, the controller immediately deactivates the run coil and/or activates the
stop coil.
9.2.4 Regulation
The GENSET controller can regulate both a governor (GOV) and an AVR.
More information
See Regulation for how regulation works.
9.2.5 Ready for operation
The genset associated with a GENSET controller is ready for operation when the following conditions are met:
• There are no alarms blocking the start.
• If configured, the Start enable digital input is activated.
• The controller is not in switchboard control.
9.2.6 AC configuration
How the general AC configuration description applies to the GENSET controller:
GENSET General name
Generator [Source]
Busbar [Busbar]
More information
The AC configuration and nominal settings for general information about AC configuration.
9.2.7 Breaker configuration
For the GENSET controller, replace [Breaker] with "Generator breaker" in the descriptions.
More information
See Breakers, synchronisation and de-loading for how to configure breakers.
9.3 Engine start

9.3.1 Engine start function
The controller software includes a pre-programmed engine start sequence. For the engine's start function, you must configure these
inputs and outputs, and parameters.
If a parameter needs an input or output to be configured, then that parameter is not visible until an input or output is configured with
the relevant function.
More information
See [Controller] protections for the engine start protections, and how to configure them.
Controller modes
Under remote and local control, the controller uses these inputs and outputs, and parameters to start the genset.

When the operator starts the genset under switchboard control, the controller is not involved. These sequences do not apply to
starting a genset under switchboard control.
Inputs and outputs

Required engine start output
Engine > Control > Crank Digital output Continuous Connect this output to the engine crank.
Optional engine start inputs and outputs

Engine >
Digital Optional. If this input is configured, it must be activated for the engine start
Function > Start Continuous
input sequence to start.
enable
Optional. The Start prepare digital output may, for example, be wired to start a
pump, so that the engine oil pressure can build up before cranking. Note that
Start prepare does not have any provision for feedback. The Start prepare
function is only a timer, and does not check whether, for example, the pump
Engine > Control Digital
Continuous start was successful.
> Start prepare output
The Start prepare digital output is not needed if the third party engine controller
ensures that all start prepare conditions are okay before activating the Start
enable digital input.
Engine > Control Digital Optional. Connect this output to the engine idle run if supported. Not all engines
Continuous
> Idle run output support this feature.
Engine > Idle
Digital Optional. The operator or another system can activate this input to request the
run > End idle Pulse
input controller to end the engine start idle run.
start
Optional. The engine controller activates this input. In response, the GENSET
controller deactivates the Crank output, although the Crank on timer continues
Engine >
to run.
Function >
Digital
Remove start Pulse
input This input is useful when only frequency is used for Running detection, but the
(release crank
relay) genset frequency increases slowly, and the crank must be removed before there
is Running detection. Even when this input is activated, the start sequence tries
to detect that the engine is running for the whole of the Crank on time.
Optional engine start commands

Optional. When the controller is under remote control, the operator or

Engine > Command >
Digital input Pulse another system can activate this input to request the controller to start
Start engine
the engine.
Optional. The operator or another system can activate this input so that
Engine > Command >
Digital input Continuous the controller cannot start the engine. The input blocks the start in both
Block engine start
remote and local control.
Engine > Command >
Optional. When the controller is under remote control, the operator or
Start engine and
Digital input Pulse another system can activate this input to request the controller to start
close generator
the engine and then synchronise and close the breaker.
breaker

Required parameters
Engine > Start sequence > Crank
For the Crank on part of the start sequence, the controller activates the Crank
Crank on 1 s to 3 min 5s
output for this period.
If there is no running detection during Crank on, then the controller deactivates the
Crank off 1 s to 3 min 5s
Crank output for this period.
The controller deactivates the Crank output when the engine speed reaches this
set point, although the Crank on timer continues to run. This parameter only has
an effect if an engine speed measurement (for example, an MPU/W/NPN/PNP) is
Disengage
1 to 2000 RPM 400 RPM configured.
crank
Even when Disengage crank is used, the start sequence tries to detect that the
engine is running for the whole of the Crank on time.
Engine > Start sequence > Start attempts

This parameter limits the wear on the genset from too many start attempts. This is the maximum
number of start attempts.
Normal 1 to 10 3
If the genset does not start after these attempts, the Start failure alarm is activated.
Engine > Running detection > Engine ready

After Running detection is ON, the engine must run for this period before the breaker close
Delay 1 s to 5 min 2 s
sequence can start.
Parameters (optional)
Engine > Start sequence > Start prepare
You must configure the Engine > Start prepare digital output to see these parameters.
Optional. If the start conditions are OK, the controller activates the Start prepare
Start prepare 0 s to 5 min 5 s output for this time. When the Start prepare timer expires, the controller activates the
Crank output. See Start prepare in the Engine start sequence.
Extended start Optional. The controller keeps the Start prepare output activated for this time during
0 to 20 s 0s
prepare cranking.
Engine > Start sequence > Run coil

You must configure the Engine > Run coil digital output to see these parameters.

Run coil Optional. The controller activates the Run coil output for this time before the
0 s to 3 min 1s
before crank Crank output is activated.
Follow crank: If the start attempt fails, the controller deactivates the Crank
output and the Run coil.
During start Follow crank,
Follow crank
attempts Always on Always on: If the start attempt fails, the controller deactivates the Crank
output. However, the Run coil remains activated until the maximum number
of start attempts is reached.

Engine > Start sequence > Stop coil
You must configure the Engine > Stop coil digital output to see these parameters.
Activated: The stop coil is activated during the start sequence if there is no
running detection and the crank is off.
During crank Activated, Not
Activated
off activated
Not activated: The stop coil is not activated during the start sequence if there is
no running detection and the crank is off.
Optional idle run start

You can configure an idle run start period for the engine. This allows the engine to warm-up before running at nominal speed.
Idle run may not be allowed with certain maritime classification societies.
If this is configured, the controller will activate the digital output Engine > Control > Idle run before starting the engine. The
controller then waits for one of the engine conditions (coolant temperature, oil temperature, external input condition, or the maximum
timer) to be fulfilled before increasing to nominal speed.
During the idle run start period, the operator can override the period and press Start on the display, the controller then cancels
the idle run start period and increases to nominal speed.
Additionally, during the idle run start period, the operator can press Stop to abort the engine start sequence and run the engine
stop sequence..
Optional. You must configure the Engine > Control > Idle run digital output to see these parameters.
NOTICE
Inhibited alarms before PCM APPL 1.0.14.x

The Idle run function requires a number of alarms to be inhibited, for example an inhibit on the under-frequency # alarm, in order
for the engine to run at idle speed. For existing applications, which have been upgraded to PCM APPL 1.0.14.x or later, you must
configure these inhibits manually on those protections. For each protection, for example Under-frequency 1, configure the inhibit
Idle run active. For all new controllers supplied from DEIF from PCM APPL 1.0.14.x pre-installed, all the inhibits are configured by
default.
Optional idle run start parameters

Engine > Idle run start > Idle run
Enables the engine to idle run until a condition is true before changing to
nominal speed.
This extends the inhibit period after the idle run is complete, so that
Extended
0 s to 60 min 2s while the engine is changing to nominal speed, certain alarms are not
inhibit
activated.
Engine > Idle run start > Minimum

Uses minimum set point to determine if the engine is ready to increase to nominal
Use Not enabled, Enabled Enabled
speed.
Delay 0 s to 120 min 5s This is the minimum time the idle run start is active. *

NOTE
* The minimum period can be overridden by pressing Start to cancel the idle run start period and increases to nominal
speed.
Engine > Idle run start > Coolant temperature

Uses coolant temperature set point to determine if the engine is ready to increase
to nominal speed.
Set point - 50 to 200 ⁰C 50 ⁰C The temperature the engine coolant must reach before ending the idle run start.
Engine > Idle run start > Oil temperature

Uses oil temperature set point to determine if the engine is ready to increase to
nominal speed.
Set point - 50 to 200 ⁰C 40 ⁰C The temperature the engine oil must reach before ending the idle run start.
Engine > Idle run start > External condition

Uses the external condition to determine if the engine is ready to increase to nominal
speed.
Not enabled,
Use Enabled
Enabled
The external condition is configured with the digital input Engine > Idle run > End
idle run start , or with CustomLogic or CODESYS.
Engine > Idle run start > Maximum

Uses maximum set point to determine if the engine is ready to increase to nominal
speed.
Delay 1 s to 120 min 60 s This is the maximum time the idle run start can operate.
9.3.2 Engine start flowchart
This flowchart does not apply to switchboard control. Under switchboard control, if the operator presses the push-button Start
on the display, the controller ignores the command and shows an info message.

Table 9.1 Engine start flowchart *
Genset
start command
Command
and mode Info message 1. Command and mode match: The controller checks that the
No
match command source and the controller mode match.
Yes 2. Start conditions OK: The controller checks whether the start
conditions are OK:
Start • If configured, the Start enable digital input is activated.
conditions Info message
No • There are no active or unacknowledged alarms to prevent the
OK
genset start. These alarm actions prevent a genset start:
Yes
◦ Block GB
◦ Trip generator breaker and stop engine
Crank output ◦ Trip generator breaker and AVR and stop engine
activated ◦ Trip generator breaker and shutdown engine
◦ Trip generator breaker and AVR and shutdown engine
3. Crank output activated: If all the start conditions are OK, the
controller activates the Crank output and a timer.
4. Running detection ON: While the start timer runs, the controller
Crank on Running
checks whether Running detection is ON.
timer detection No
No
expired ON • When the controller detects that the genset is running, the
Yes genset start is complete.
Yes 5. Crank on timer expired: If Running detection is OFF after the
Genset Crank on timer runs out, the controller checks the number of start
Max start started attempts:
attempts No • If the maximum number of start attempts has not been
reached, the controller attempts to start the genset again.
Yes
Crank output • If the maximum number of start attempts has been reached,
deactivated the controller activates the Start failure alarm and stops the
engine.
Alarm
Genset stop
sequence
NOTE * Both Start prepare and Idle run start functions are not shown here.
9.3.3 Engine start sequence
Engine start sequence for a stop coil system

In this example, the Engine > Start sequence > Stop coil > During crank off parameter is Activated. The engine
speed (RPM measurement) and/or the Remove start (release crank relay) digital input do not disengage the crank before there is
Running detection.

Figure 9.3 Successful engine start sequence for a stop coil system
Start
(1)
attempts
1
t1
(2) Crank
Running
(3)
detection
t1 = Crank on (Parameters > Engine > Start sequence > Crank > Crank on)
1. Start attempts: The engine starts during the first start attempt.
2. Crank: Engine > Crank (digital output). The controller activates the Crank output. If Running detection changes from OFF to
ON, cranking stops.
3. Running detection. The engine is regarded as started when Running detection is ON.
Figure 9.4 Failure of engine start sequence for a stop coil system
Start
(1)
attempts
1 2 3
t1 t2
(2) Crank
t2 t3
(3) Stop coil
Running
(4)
detection
(5) Start failure
t1 Crank on (Parameters > Engine > Start sequence > Crank > Crank on)
t2 Crank off (Parameters > Engine > Start sequence > Crank > Crank off)
t3 Extended stop (Parameters > Engine > Stop sequence > Extended stop) (optional)
Failure of engine start sequence for a stop coil system:

1. Start attempts: Parameters > Engine > Start sequence > Start attempts > Normal = 3.
2. Crank: Engine > Crank (digital output). The controller activates the Crank output for the Crank on time, and deactivates it for
Crank off time.
3. Stop coil: Engine > Stop coil (digital output). If Running detection is OFF after the Crank on time, then the controller activates
the Stop coil for the time in the Crank off parameter. If all start attempts fail, the controller also activates the Stop coil for the time
in Extended stop > Stop coil activated. This ensures that the engine is stopped if the engine start was not detected. The engine
cannot be started during the Extended stop > Stop coil activated time.
4. Running detection. There is no running detection.
5. Start failure. The controller activates the Start failure alarm after the last unsuccessful start attempt.

Engine start sequence for a run coil system
In this example, the Engine > Start sequence > Run coil > During start attempts parameter is set to Follow
crank. The engine speed (RPM measurement) and/or the Remove start (release crank relay) digital input do not disengage the
crank before there is Running detection.
Table 9.2 Successful engine start sequence for a run coil system
t1 = Run coil before crank (optional)

Start
(1) t2 = Crank on (Parameters > Engine > Start sequence > Crank >
attempts
1 Crank on)
1. Start attempts: The engine starts during the first start attempt.
(2) Run coil 2. Run coil: Engine > Run coil (digital output). The controller activates
t1 t2 the Run coil at the time in the Run coil before crank parameter. If Running
detection is ON, the engine is regarded as started, and the Run coil
(3) Crank remains activated.
3. Crank: Engine > Crank (digital output). The controller activates the
Crank output. If Running detection changes from OFF to ON, cranking
Running stops.
(4)
detection
4. Running detection. The engine is regarded as started when Running
detection is ON.
Figure 9.5 Failure of engine start sequence for a run coil system
Start
(1)
attempts
1 2 3
(2) Run coil
t1 t2 t3
(3) Crank
Running
(4)
detection
(5) Start failure
t1 Run coil before crank (optional)
t2 Crank on (Parameters > Engine > Start sequence > Crank > Crank on)
t3 Crank off (Parameters > Engine > Start sequence > Crank > Crank off)
1. Start attempts: Parameters > Engine > Start sequence > Start attempts > Normal = 3.
2. Run coil: Engine > Run coil (digital output). The controller activates the Run coil at the time in the Run coil before crank
parameter. If Running detection is still OFF after cranking, the controller deactivates the Run coil for the time in the Crank off
parameter. This ensures that the engine is stopped if the engine start was not detected. The engine cannot be started during the
Crank off time.
3. Crank: Engine > Crank (digital output). The controller activates the Crank output for the Crank on time, and deactivates it for
Crank off time.
4. Running detection. There is no running detection.
5. Start failure. The controller activates the Start failure alarm after the last unsuccessful start attempt.

Optional start prepare
You can use the optional Engine > Start prepare digital output with a stop coil or a run coil system.
Table 9.3 Successful engine start sequence with start prepare
t1 = Start prepare (Parameters > Engine > Start sequence >

Start
(1) Start prepare > Start prepare)
attempts
1 t2 = Extended start prepare (Parameters > Engine > Start
sequence > Start prepare > Extended start prepare)
t1 t2
Start 1. Start attempts
(2)
prepare 2. Start prepare: Engine > Start prepare (digital output) (optional).
a. At the start of each start sequence, the controller activates the
Start prepare output for the time in the Start prepare parameter
(t1). All other engine start outputs (that is, Stop coil, Crank ) are
(3) Crank
not activated during this time.
b. If there is an Extended start prepare time (t2), then the Start
prepare output remains activated for this time during cranking. If
cranking stops before the extended start prepare timer stops,
then the controller deactivates the Start prepare output.
3. Crank: Engine > Crank (digital output). After the Start prepare
time, the controller activates the Crank output.
9.3.4 Interruption of the start sequence
These actions interrupt the engine start sequence:

• The Emergency stop digital input is activated (for example, from the operator, or a PLC).
• There is a Stop engine command. For example: Under local control, the operator pushes the push-button Stop on the
display unit.
• The following alarm actions:
◦ Trip generator breaker and stop engine
◦ Trip generator breaker and shutdown engine
The Block alarm action will not interrupt the genset start sequence after it has begun. However, the Block alarm action prevents a
new genset start sequence from starting.
When the start sequence is interrupted, the controller does the following:
• Deactivates the Crank output.
• Activates the Stop coil output (if present). Alternatively, deactivates the Run coil output (if present).
• Deactivates the Start prepare output (if present).
There is no cooldown period when the engine start sequence is interrupted.
NOTE If Running detection is ON, the controller regards the engine as started. When the engine has started, the actions listed
here do not interrupt the engine start sequence, but result in a engine stop instead. The engine stop normally includes the
cooldown period configured in the controller. However, for a shutdown, there is no cooldown period.
9.4 Engine stop

9.4.1 Engine stop function
For a normal genset stop, the controller ensures that the genset runs for a cooldown period before stopping. If a shutdown alarm
action shuts down the genset, there is no cooldown period. You can also configure an idle run stop period before the engine shuts
down.

The controller software includes pre-programmed genset stop sequences. For the engine's stop function, you must configure these
Parameters that need a hardware function are not visible until the function is assigned to an input or output.
More information
See GENSET controller alarms for more information on how the engine stop alarms work, and how to configure them.
Controller modes
Under remote and local control, the controller uses these inputs and outputs, and parameters to stop the genset.
When the operator stops the genset under switchboard control, the controller is not involved. These sequences do not apply to
stopping a genset under switchboard control.
Optional inputs and outputs

Optional. When the controller is under remote control, the operator

Engine > Command >
Digital input Pulse or another system can activate this input to request the controller to
Stop engine
stop the engine.
Optional. Connect this output to the engine idle run if supported. Not
all engines support this feature.
Engine > Control >
Idle run
This digital output is needed to use either idle run start and/or idle
run stop.
Engine > Idle run > Optional. The operator or another system can activate this input to
Digital input Pulse
End idle stop request the controller to end the engine stop idle run.
Engine > Command >
Optional. When the controller is under remote control, the operator
Open generator
Digital input Pulse or another system can activate this input to request the controller to
breaker and stop
de-load and open the breaker, and then stop the engine.
engine
Engine > Cooldown > Optional. This input measures the engine water temperature, and is
Analogue input Units = °C
Coolant water [C] used for temperature-dependent cooldown.
Parameters
Engine > Stop sequence > Cooldown
After the engine stop signal or command, the engine runs for this period before
Cooldown time 1 s to 3 h 240 s
the controller activates the Stop coil (or deactivates the Run coil).
Temperature Optional. The engine cooldown stops if the engine coolant water temperature
0 to 150 °C 0 °C
threshold reaches this threshold before the cooldown timer expires.
Engine > Stop sequence > Extended stop

Stop coil The Stop coil remains activated for this period after Running detection is OFF.
1 s to 3 min 5 s
activated During this period a new start attempt is not possible.
Optional idle run stop

You can optionally configure an idle run stop period for the engine, allowing the engine to cool-down after taking load.

If this is configured, the controller will activate the digital output Engine > Control > Idle run before stopping the engine. The
controller then waits for one of the engine conditions (coolant temperature, oil temperature, external input condition, or the maximum
timer) to be fulfilled before stopping the engine.
During the idle run stop period, the operator can override the period and press Stop on the display, the controller then cancels
the idle run stop period and stops the engine.
Additionally, during the idle run stop period, the operator can press Start to abort the engine stop sequence and run the engine
start sequence.
Optional. You must configure the Engine > Control > Idle run digital output to see these parameters.
NOTICE
Inhibited alarms before PCM APPL 1.0.14.x

The Idle run function requires a number of alarms to be inhibited, for example an inhibit on the under-frequency # alarm, in order
for the engine to run at idle speed. For existing applications, which have been upgraded to PCM APPL 1.0.14.x or later, you must
configure these inhibits manually on those protections. For each protection, for example Under-frequency 1, configure the inhibit
Idle run active. For all new controllers supplied from DEIF from PCM APPL 1.0.14.x pre-installed, all the inhibits are configured by
default.
Optional parameters
Engine > Idle run stop > Idle run
Enables the engine to idle run until a condition is true before stopping the
engine.
Engine > Idle run stop > Minimum

Use Not enabled, Enabled Enabled Uses minimum set point to determine if the engine is ready to stop.
Delay 0 s to 120 min 5s This is the minimum time the idle run stop is active.
Engine > Idle run stop > Coolant temperature

Use Not enabled, Enabled Enabled Uses coolant temperature set point to determine if the engine is ready to stop.
Set point - 50 to 200 ⁰C 90 ⁰C The temperature the engine coolant must reach before ending the idle run stop.
Engine > Idle run stop > Oil temperature

Use Not enabled, Enabled Enabled Uses oil temperature set point to determine if the engine is ready to stop.
Set point - 50 to 200 ⁰C 60 ⁰C The temperature the engine oil must reach before ending the idle run stop.
Engine > Idle run stop > External condition

Not enabled, Uses the external condition to determine if the engine is ready to stop.
Use Enabled
Enabled

The external condition is configured with the digital input Engine > Idle run >
End idle run stop, or with CustomLogic or CODESYS.
Engine > Idle run stop > Maximum

Use Not enabled, Enabled Enabled Uses maximum set point to determine if the engine is ready to stop.
Delay 1 s to 120 min 60 s This is the maximum time the idle run stop can operate.
9.4.2 Engine stop flowchart
The following flowchart shows how the controller normally stops a genset. An engine shutdown is described later.
This flowchart does not apply to switchboard control. When the controller is under switchboard control, it will not stop the genset. If,
for example, the operator presses the push-button Stop on the display unit, the controller ignores this command, and the
controller display unit shows an info message.
Table 9.4 Engine stop flowchart *
1. Command and mode match: The controller checks that the command
Genset stop
source and the controller mode match.
command
2. GB open: The controller checks whether the genset breaker is open. If the
genset breaker is not open, the controller cancels the stop sequence and the
display unit shows an info message.
Command
and mode Info message 3. Cooldown timer expired: The genset runs without load for the cooldown
No
match time. The controller checks whether the cooldown timer has expired or the
Yes stop button was pressed again.
• If the cooldown timer has not expired, but the engine stop button was
pressed again, the controller stops the cooldown.
GB open Info message 4. Stop engine: To stop the engine:
No
• Stop coil system: The controller activates the Stop coil output.
Yes
• Run coil system: The controller deactivates the Run coil output.
5. Running detection OFF: The controller checks whether the engine has
stopped.
Cooldown Stop
timer pressed • If Running detection is ON, the controller activates an alarm.
No No
expired again • If Running detection is OFF, the engine has stopped and the stop
sequence has been completed successfully.
Yes Yes
Stop engine
Running
detection Alarm
No
OFF
Yes
Genset
stopped
NOTE * Idle run stop function is not shown here.

9.4.3 Engine stop sequence
Figure 9.6 Engine stop sequence for a stop coil system
(1) Stop
(2) Cooldown t1
*
(3) Stop coil t2
Running
(4)
detection
Figure 9.7 Engine stop sequence for a run coil system
(1) Stop
(2) Cooldown t1
*
t2
(3) Run coil
Running
(4)
detection
t1 Cooldown (Configure > Parameters > Engine > Stop sequence > Cooldown > Normal)
Extended stop (Configure > Parameters > Engine > Stop sequence > Extended stop > Stop coil
t2
activated)
* Up to this point, the engine can be restarted immediately, without completing the stop sequence.
1. Stop. The stop command can come from the controller, an operator, or an external source. See Engine stop flowchart.
2. Cooldown (optional). The controller allows the genset to run for the time configured. There is no cooldown for shutdowns, an
emergency stop, or an operator stop by pressing the engine stop push-button again. Temperature-dependent cooldown is also
possible (see below).
3. Stop engine:
• Stop coil: Engine > Stop coil (digital output). The controller activates the stop coil digital output until running feedback
is OFF. The controller then keeps the stop coil activated for the time in the (optional) Extended stop parameter.
• Run coil: Engine > Run coil (digital output). The controller deactivates the run coil digital output after the cooldown
period. The genset cannot restart during the time in the (optional) Extended stop parameter.
4. Running detection. When the running detection is OFF, the controller regards the engine as stopped.
Temperature-dependent cooldown
Temperature-dependent cooldown stops the engine cooldown when the engine coolant water temperature reaches the configured
threshold before the cooldown timer expires. The cooldown can be shorter than when just a timer is used, which reduces fuel use.

Configure an analogue input with the Engine > Cooldown > Coolant water [C] function and Engine > Stop sequence
> Cooldown > Temperature threshold.
NOTE You must configure the analogue input function to see the parameters.
9.4.4 Engine shutdown flowchart
The engine is shut down for the following alarm action:

• Trip generator breaker and shutdown engine
The engine is also shutdown if the controller's Emergency stop input is deactivated.
Table 9.5 Engine shutdown flowchart
Genset 1. GB open: The controller checks whether the generator breaker is open. If not,
shutdown the controller trips the generator breaker.
command 2. Stop engine: The controller shuts down the engine:
• Stop coil system: The controller activates the Stop coil output.
• Run coil system: The controller deactivates the Run coil output.
3. Running detection OFF: If Running detection is still ON after the time
allowed, the controller activates the Stop failure alarm.
GB open Trip GB
No
NOTE The controller does not require the engine stop conditions to be met
Yes
for an engine shutdown. Similarly, there is no cooldown time for an
engine shutdown.
Stop engine
Running
detection Alarm
No
OFF
Yes
Genset
stopped
9.5 Generator breaker

9.5.1 How it works
The generator breaker (GB) connects the genset to the busbar. The genset must be running, and synchronised with the busbar, for
the generator breaker to close. The generator breaker is an important part of the system safety, and trips to protect the genset from
problems on the busbar. The generator breaker also trips to stop genset problems from disturbing the busbar.
General breaker information

More information
See Breakers, synchronisation and de-loading for how synchronisation and breakers work. This includes the inputs and
output functions and the parameters to configure.
[Breaker] refers to Generator breaker. The breaker abbreviation ([*B]) is GB.

9.5.2 Generator breaker close flowchart
This flowchart does not apply to switchboard control. When the controller is in switchboard control, it will not close the breaker. If, for
example, the operator presses the push-button Close breaker on the display, the controller ignores this command.
More information
See Generator breaker blackout close flowchart for how to allow the genset to connect to a dead busbar.
GB close
command
2. GB open: The controller checks whether the generator breaker is open. If
the generator breaker is already closed, the sequence stops, and an info
message is shown.
Command
and mode Info message 3. Genset V & Hz OK: The controller checks whether the voltage and
No
match frequency from the genset are within the allowed range*. If these are not in
Yes the range, then the controller cancels the close command and displays an
info message.
4. Busbar V & Hz OK: The controller checks whether the voltage and
GB open Info message frequency on the busbar are within range*. If these are not in the range,
No
then the controller cancels the close command and displays an info
Yes message.
5. Sync GB: The controller tries to synchronise the genset to the busbar.
• When the genset and busbar are synchronised, the controller activates
Genset
V & Hz Info message the Breakers > Generator breaker > Control > GB close output to close
No
OK the breaker.
Yes • If the genset and busbar do not synchronise within the time allowed, the
controller activates a GB synchronisation failure alarm.
6. GB closed: The controller checks whether the generator breaker has
Busbar
V & Hz Info message closed.
No
OK • If the generator breaker has closed, the generator breaker close
Yes sequence has been completed successfully.
• If the generator breaker has not closed, the controller activates the GB
closing failure alarm.
Sync GB
Synchronised Timer expired

No No
Yes Yes
Alarm
Close GB
GB closed Alarm
No
Yes
GB closed

NOTE * See Configure > Parameters > [Source] / [Busbar] AC setup > Voltage and frequency OK for
these ranges.
9.5.3 Generator breaker blackout close flowchart
The Blackout close function sets the action that the controller allows when a dead busbar is detected. If the parameter is not Off,
then an operator or a remote input can close the breaker directly to the black busbar.
DANGER!
Incorrect settings
Incorrect blackout close parameter settings can lead to equipment damage or loss of life.
Blackout conditions
A blackout is present if the phase-to-phase voltage is less than 10 % of the nominal voltage (VL-L < 10 % of Vnom). This percentage
is fixed.
Conditions that prevent blackout close

If any of the following conditions are present, the controller will not allow the blackout close:
• The breaker position is unknown.

• There is a short circuit.
◦ A digital input with the function Breakers > Generator breaker > Feedback > GB short circuit was activated.
• There is a blocking alarm.
◦ The alarm action determines whether the alarm is a blocking alarm.
• The busbar and/or generator AC measurements are not OK.
◦ A measurement failure is detected on one or more of the phases.
Parameters
Breakers > Generator breaker configuration
Off: The controller will never activate the close breaker relay if any blackout
is detected.
Generator is dead, busbar OK *: If a blackout is detected at the Generator,

• Off but the Busbar is stable, then the controller allows the breaker to close.
• Generator is dead,
busbar OK Generator Generator OK, busbar is dead: If a blackout is detected at the Busbar and
Blackout
• Generator OK, OK, busbar the Generator is stable, then the controller allows the breaker to close.
close
busbar is dead is dead
• One busbar is alive One busbar is alive *: If a blackout is detected at the Generator or the
• On Busbar, and the live busbar is stable, then the controller allows the breaker
to close.
On *: If a blackout is detected at the Generator and/or at the Busbar, then

the controller allows the breaker to close.
CAUTION
Protection of system
The system must be adequately protected if you use the (*) options for genset applications.

Blackout close flowchart
Breaker close
command
Breaker close
Blackout
No flowchart
Yes
Check Blackout
close parameter
Parameter:
Parameter:
Generator is Parameter: One
Parameter: Off Generator OK, Parameter: On
dead, busbar busbar is alive
busbar is dead
OK
Only Only Only

Info message Generator is Busbar is one live
No No No
dead dead busbar
Yes Yes Info message Yes Info message
Info message
Activate close
breaker relay
Breaker
closed? No
Yes Alarm
GB closed
1. Breaker close command: An operator or a remote command attempts to close the breaker.
2. Blackout: The controller detects a blackout on one or both of the busbars, and the conditions for blackout close are met.
3. Check Blackout close parameter:
a. Off: The controller does not allow the breaker to close. The controller shows an info message, and the sequence ends.
b. Generator is dead, busbar OK: The controller checks whether the blackout was detected only at the Generator.
• Blackout only at the Generator: The controller activates the close breaker relay.
• Blackout was only at the Busbar or on both sides of the breaker: The controller shows an info message, and the
sequence ends.
c. Generator OK, busbar is dead: The controller checks whether the blackout was detected only at the Busbar.
• Blackout only at the Busbar: The controller activates the close breaker relay.
• Blackout only at the Generator or on both sides of the breaker: The controller shows an info message and the sequence
ends.
d. One busbar is alive: The controller checks if the blackout was detected only at the Generator, or only at the Busbar.
• Blackout only at the Generator, or only at the Busbar: The controller activates the close breaker relay.
• Blackout on both sides of the breaker: The controller shows an info message and the sequence ends.
e. On: If there is a blackout on either/both busbars, the controller activates the close breaker relay.

4. Breaker closed: The controller checks whether the generator breaker has closed.
• If the generator breaker has closed, the blackout close sequence has been completed successfully.
• If the generator breaker has not closed the controller activates the GB closing failure alarm.
9.5.4 Generator breaker open flowchart
The flowchart shows the sequence that the controller normally uses to open the generator breaker.
The alarm action Block does not open a closed breaker, although it stops an open breaker from closing. If the controller or an
operator sends a GB open command while Block is active, the controller uses this sequence.
The sequence to trip the generator breaker is described in another flowchart.
This flowchart does not apply to switchboard control. When the controller is under switchboard control, it will not open the breaker
(except for a trip). If, for example, the operator presses the push-button Open breaker on the display unit, the controller ignores
this command.

GB open
command
Command
and mode Info message
No
match
Yes
GB
Info message
closed No
Yes
The only All other

connected feeders are De-load genset
No de-loading No
feeder
Yes Yes
De-load
Load < open timer
set point No No
expired
Yes
Yes
Open GB Alarm
GB opened Alarm
No
Yes
GB opened
1. Command and mode match: The controller checks that the command source and the controller mode match.
2. GB closed: The controller checks whether the generator breaker is closed. If the generator breaker is open, the sequence
ends.
3. The only connected feeder: The controller checks whether the genset is the only connected power source in the section.
• If the genset is the only connected power source in the section, then the controller opens the breaker without deloading.
4. All other feeders are de-loading: If there are other connected power sources in the section, the controller checks whether the
power sources are busy deloading.
• If all of the other power sources are busy de-loading, then the controllers opens the breaker without de-loading.
5. De-load genset: If there is at least one other power source connected that is not busy de-loading, then the controller adjusts
the regulation to de-load the genset:
• When the load is less than the set point for the breaker to open, the controller activates the Generator breaker > Control >
GB open output.
• If the controller cannot de-load the breaker before the de-load timer expires, the controller activates the GB de-load failure
alarm. The controller continues to try to de-load the breaker.
6. GB opened: The controller checks whether the generator breaker has opened:
• If the generator breaker has opened, the generator breaker open sequence has been completed successfully.
• If the generator breaker has not opened, the controller activates the GB opening failure alarm.

9.5.5 Generator breaker trip flowchart
The controller automatically trips the generator breaker (GB) for these alarm actions:
• Trip generator breaker
• Trip generator breaker and stop engine
The generator breaker also trips if the controller's Emergency stop input is deactivated.
The controller does not require the genset stop conditions to be met for a breaker trip. Similarly, the breaker is not de-loaded for a
trip.
Generator
breaker trip
Open GB 1. Open GB: When a trip is required, the controller activates the Breakers >
Generator breaker > Control > GB Open output to open the breaker.
2. GB opened: The controller checks whether the breaker has opened:
• If the breaker has opened, the trip is successful.
GB opened Alarm • If the breaker has not opened, the controller activates the GB opening failure
No alarm.
Yes
GB tripped
9.6 Other GENSET controller functions

9.6.1 Priming
The priming function activates an output at regular intervals while the engine is not running. Priming is not active while the engine is
starting or stopping. For example, priming can be used for an engine heater or lube oil pump. For the priming function, you must
configure the following output and parameters.
Digital output
Optional. Use this output to prime the engine at regular

Engine > Control > Priming Digital output Continuous
intervals.
Parameters
Engine > Maintenance > Priming
To see these parameters, you must assign the Priming function to a digital output.
Not enabled: The controller does not activate the Priming output.

Enabled: After the engine stops, the controller activates the Priming output for
the period configured under ON timer. The controller then deactivates the

output for the period configured under OFF timer. The on and off cycle repeats
until the engine starts.
ON timer 0 s to 1 h 5s The priming period.
OFF timer 0 s to 1 h 30 s The interval between each priming.
9.6.2 Temperature-dependent power derating
The temperature-dependent power derating function reduces the genset nominal load by reducing the genset nominal power used
by load sharing. The derating function can be configured for up to three temperature measurements.
Analogue input
Engine > Power derate > This can measure any temperature,
The measurement must be
Temperature > Derate # Analogue input for example, the engine cooling water.
in °C.
temperature [C] *
Parameters
Engine > Temperature > Power derate # *
The analogue input(s) must be configured to see the power derate parameter and curve.
Not enabled: The load sharing uses the genset nominal power, no matter
what the derate temperature is.
Not enabled,
Enable derate Not enabled
Enabled
Enabled: The controller uses the power derating curve to derate the power for
load sharing within the configured range. See How it works.
Setup Use this section to set up the power derate curve.
How it works
You can create a customised curve for each temperature input.
Power derate affects load sharing and fixed power regulation, since these are based on a percentage of nominal power.
The derating does not affect the alarms.
Temperature-dependent power derating example
There are two 1000 kW gensets in the system. For genset A, the power derate curve is 100 % until 80 °C, then linearly
down to 70 % at 100 °C. Genset B does not have power derating.
The genset A temperature is 90 °C. The system load is 1480 kW.
The derated nominal power for genset A is 85 % of the nominal power, that is, 850 kW. The total genset nominal power is
1850 kW.
For equal load sharing, each genset runs at 1480 kW / 1850 kW × 100 % = 80 % of their nominal load. Genset A runs at
680 kW, and genset B runs at 800 kW.

9.6.3 Engine operating values as analogue outputs
You can configure an analogue output with a function for an engine operating value. The controller receives this value from an
engine measurement. The controller then adjusts the analogue output to reflect the engine operating value.
Analogue outputs
Engine > Power derate The controller outputs the derate temperature. For this function
Analogue
> Derate # temperature -50 to 200 °C to work, there must be an analogue input to the controller with
output
[C] * the engine derate temperature.
The controller outputs the engine oil pressure. For this function
Engine > Running Analogue
0 to 10 bar to work, there must be an analogue input to the controller with
detection > Oil [bar] output
the engine oil pressure.
The controller outputs the engine speed. For this function to

Engine > Running Analogue 0 to 20,000
work, there must be an active MPU/W/NPN/PNP input to the
detection > MPU [RPM] output RPM
controller with the engine speed.
The controller outputs the engine coolant water temperature.

Engine > Cooldown > Analogue
-50 to 200 °C For this function to work, there must be an analogue input to the
Coolant water [C] output
controller with the engine coolant water temperature.
Applications
An analogue output with an engine operating value may be wired to a switchboard instrument, to help the operator with
troubleshooting. For example, the engine speed measured by the MPU (Engine > Running detection > MPU [RPM]) can be
displayed.
9.6.4 Engine states as digital outputs
You can configure a digital output with a function for an engine state. The controller activates the digital output if the engine state is
present. These can be useful for troubleshooting.
Digital outputs
Engine > State > Running Digital output Continuous Activated if there is running detection for the engine.
Engine > State > Not
Digital output Continuous Activated if there is no running detection for the engine.
running
Engine > State > Not ready Activated if there is any condition that would block the
to start controller from starting the engine.
Engine > State > Ready to Activated if there are no conditions that would block the
start controller from starting the engine.
Activated while the controller works through the pre-

Engine > State > Starting Digital output Continuous
programmed start sequence.
Engine > State > Cooldown Digital output Continuous Activated while the controller cooldown timer is running.
9.6.5 Counters
You can view, edit and reset all the counters on the display unit under Configure > Counters.
The counters include:

• Start attempts
• Total running hours and minutes

• Trip running hours and minutes
• Generator breaker operations and trips
• Energy export (active and reactive)
Running hours trip works like a car trip meter. For example, you can use this counter to track the running hours since the last
maintenance.
Energy counter outputs

For each energy counter, you can configure a digital output to send a pulse every time a certain amount of energy is transferred.
Digital outputs
You must configure the digital output function to see the parameters.

Generator > Production counters > Active energy export pulse Digital output Pulse
Generator > Production counters > Reactive energy export pulse Digital output Pulse
Parameters
Generator > Production counters > Active energy export
Pulse every 1 kWh to 10 MWh 10 kWh The value when a digital output sends a pulse.
The length of the pulse that is sent. This value should be long enough so the pulse
Pulse length 0.1 s to 1 h 1s
can be registered by the external counter.
Generator > Production counters > Reactive energy export

Pulse every 1 kvarh to 10 Mvarh 10 kvarh The value when a digital output sends a pulse.
Table 9.6 Energy counter function and corresponding parameter full names
[Counter pulse] [Counter]
Active energy export pulse 1 Active energy export
Reactive energy export pulse 1 Reactive energy export
Application example for an energy counter output
1. Connect the digital output to an external counter.

2. Configure the digital output using the display unit or PICUS to Active energy export pulse 1.
3. Configure the Pulse every parameter to the value where you would like to send a pulse. For example, 100 kWh.
4. Configure the Pulse length to the required length of the pulse for your external counter. For example, 1 second.
With the example setup the controller sends a 1 second pulse to the external counter for each 100 kWh the controller logs.
9.6.6 Trip AVR
The Trip AVR output ensures that excitation is stopped when an alarm activates with a Trip AVR alarm action. In cases where there
is high voltage present, stopping the excitation reduce the time required to stop an engine in case of an emergency.

The Trip AVR output and alarm action does not initiate a breaker trip. To trip the breaker and the AVR, digital outputs for both actions
must be configured and the correct alarm action must selected. For example, the Trip breaker + AVR alarm action.
Digital output
When this output is configured it is possible to assign alarm actions that trip the
AVR.
[Source] > AVR Digital
Continuous When an alarm with a Trip AVR action activates, the Trip AVR digital output
> Trip AVR output
activates and stays activated until all alarms with a Trip AVR action are resolved.
When the output is active, the controller pauses AVR regulation.
Trip AVR sequence diagram
2 To trip the AVR:

Number of 1. Number of trip AVR alarms: The number of active
1
(1) trip AVR alarms with a Trip AVR (or similar) alarm action.
alarms 0
2. Trip AVR: [Source] > AVR > Trip AVR (digital
output). The controller activates this output until all
alarms with a Trip AVR (or similar) alarm action are not
(2) Trip active.
AVR
9.7 GENSET controller alarms

9.7.1 GENSET controller alarms
These alarms are in addition to the AC protections and general alarms for PPU 300 controllers.
Table 9.7 Alarms for the GENSET controller
Alarms
Emergency stop
Overspeed (2 alarms)
Under-speed (2 alarms)
Crank failure
Primary running feedback failure
Start failure
Engine Stop failure
Engine stop (external)
Engine start (external)
Start enable removed during start
Total running hours notification
Trip running hours notification
Magnetic pickup wire break
Generator Voltage or frequency not OK

Alarms
GOV regulation error
GOV regulation mode not selected
GOV stand-alone configuration error *
GOV relay setup incomplete

Regulation
AVR regulation error
AVR regulation mode not selected
AVR stand-alone configuration error *
AVR relay setup incomplete
• Up to 3 non-essential loads per controller

• Can connect each controller to the same 3 non-essential load breakers
NEL # over-current (1 alarm for each non-essential load)

Non-essential load (NEL)
NEL # under-frequency (1 alarm for each non-essential load)
NEL # overload 1 and 2 (2 alarms for each non-essential load)
NEL # reactive overload (1 alarm for each non-essential load)
Other Trip AVR output not configured
NOTE * Only in GAM3.2.
9.7.2 Alarm actions
The controller has the following alarm actions:

• Warning
• Block
• Trip generator breaker
• Trip generator breaker and stop engine
• Trip AVR *
• Trip generator breaker + AVR *
• Trip generator breaker + AVR + stop engine *
• Trip generator breaker + AVR + shutdown engine *
NOTE * These alarm actions are only available if the Trip AVR digital output is configured.
9.7.3 Inhibits
Inhibit Disables the alarm when ...

Engine running Digital running detection is ON.
Engine not running Digital running detection is OFF.
Generator breaker closed The Breakers > Generator breaker > Feedback > GB closed digital input is activated.
Generator breaker open The Breakers > Generator breaker > Feedback > GB open digital input is activated.
Generator voltage present The generator voltage is above 10 % of the nominal voltage.
No generator voltage The generator voltage is below 10 % of the nominal voltage.
Generator frequency
The generator frequency is above 10 % of the nominal frequency.
present

No generator frequency The generator frequency is below 10 % of the nominal frequency.
Controller under SWBD The Local > Mode > Switchboard control digital input is activated, OR a system problem
control forced the controller under switchboard control.
All these conditions are met:
ACM wire break • Voltage is detected by one set of ACM voltage measurements
• No voltage is detected on a phase, or on all three phases for the other set of ACM voltage
measurements
Inhibit 1 The Alarm system > Inhibits > Activate inhibit 1 digital input is activated.
Inhibit 2 The Alarm systems > Inhibits > Activate inhibit 2 digital input is activated.
9.7.4 Breaker alarms
More information
See Breakers, synchronisation and de-loading for breaker handling and alarms in general.
GENSET alarm Parameters General name

Breakers > Generator breaker monitoring >
GB synchronisation failure Breaker synchronisation failure
Synchronisation failure
Breakers > Generator breaker monitoring > De-

GB de-load failure Breaker de-load failure
load failure

Vector mismatch Vector mismatch
Vector mismatch

GB opening failure Breaker opening failure
Opening failure

GB closing failure Breaker closing failure
Closing failure

GB position failure Breaker position failure
Position failure

GB trip (external) Breaker trip (external)
Tripped (external)

GB short circuit Breaker short circuit
Short circuit
GB configuration failure - Breaker configuration failure
Generator phase sequence error Generator > AC setup > Phase sequence error Phase sequence error
Busbar phase sequence error Busbar > AC setup > Phase sequence error Phase sequence error
9.7.5 AC alarms
More information
See AC configuration and nominal settings for information about the AC alarms in general.

Generator AC alarm names for GENSET controller
Controller alarm Parameters General name
Generator > Voltage protections > Over-voltage
Generator over-voltage 1 or 2 Over-voltage
1 or 2
Generator > Voltage protections > Under-voltage

Generator under-voltage 1 or 2 Under-voltage
1 or 2
Generator > Voltage protections > Voltage

Generator voltage unbalance Voltage unbalance
unbalance
Generator > Voltage protections > Negative

Negative sequence voltage Negative sequence voltage
sequence voltage
Generator > Voltage protections > Zero sequence

Zero sequence voltage Zero sequence voltage
voltage
Generator > Current protections > Over-current

Generator over-current 1 or 2 Over-current
1 or 2
Generator > Current protections > Fast over-

Fast over-current 1 or 2 Fast over-current
current 1 or 2
Generator > Current protections > Current Current unbalance

Current unbalance (average calc.)
unbalance (average calc.) (average calc.)
Generator > Current protections > Current Current unbalance (nominal
Current unbalance (nominal calc.)
unbalance (nominal calc.) calc.)
Generator > Current protections > Directional
Directional over-current 1 or 2 Directional over-current
over-current 1 or 2
Generator > Current protections > Inverse time

Inverse time over-current Inverse time over-current
over-current
Generator > Current protections > Negative

Negative sequence current Negative sequence current
sequence current
Generator > Current protections > Zero sequence

Zero sequence current Zero sequence current
current
Generator > Current protections > Stabilised Stabilised differential

Stabilised differential current
differential current current
Generator > Current protections > High set
High set differential current High set differential current
differential current
Generator > Frequency protections > Over-

Generator over-frequency 1 or 2 Over-frequency
frequency 1 or 2
Generator > Frequency protections > Under-

Generator under-frequency 1 or 2 Under-frequency
frequency 1 or 2
Overload 1 or 2 Generator > Power protections > Overload 1 or 2 Overload

Generator > Power protections > Reverse power 1
Reverse power 1 or 2 Reverse power
or 2
Generator > Reactive power protections >

Reactive power export 1 or 2 Reactive power export
Reactive power export 1 or 2

Reactive power import 1 or 2 Reactive power import
Reactive power import 1 or 2
Busbar AC alarm names for GENSET controller

Busbar over-voltage 1 or 2 Busbar > Voltage protections > Over-voltage 1 or 2 Busbar over-voltage
Busbar under-voltage 1 or 2 Busbar > Voltage protections > Under-voltage 1 or 2 Busbar under-voltage

Busbar voltage unbalance Busbar > Voltage protections > Voltage unbalance Busbar voltage unbalance
Busbar > Frequency protections > Over-frequency 1
Busbar over-frequency 1 or 2 Busbar over-frequency
or 2
Busbar > Frequency protections > Under-frequency 1

Busbar under-frequency 1 or 2 Busbar under-frequency
or 2
9.7.6 Emergency stop
Digital
input
tdelay
You can configure one of the controller's digital inputs as the emergency stop. high
When this input is present, the alarm is always enabled. The alarm parameters are not
visible. The alarm action is Trip generator breaker and shutdown engine, latch enabled.
low
time

Alarm system > Wire the emergency stop digital input so that it is normally activated.
Additional functions > Digital input Continuous If the emergency stop digital input is not activated, then controller
Emergency stop activates the Emergency stop alarm.
CAUTION
The Emergency stop is part of the safety chain

The Emergency stop is part of the safety chain, and this digital input function should only be used to inform the controller
of the emergency stop. However, the controller's emergency stop input cannot be used as the system's only emergency
stop. For example, if the controller is unpowered, it cannot respond to the emergency stop digital input.
9.7.7 Overspeed
Value
These two alarms are for overspeed protection. Delay
Set
The alarm response is based on the genset speed, as measured by the MPU/W/NPN/PNP point
input.
time
Engine > Protections > Overspeed # *

In addition to these overspeed alarms, one of the controller's digital inputs can be connected to hardware that detects overspeed. A
customised alarm for overspeed can then be configured on that digital input.
Parameter Range Overspeed 1 Overspeed 2

Set point 10 to 150 % of nominal speed 110 % 120 %
Delay 0 s to 3 min 5s 1s

Parameter Range Overspeed 1 Overspeed 2
Action Warning Trip generator breaker and shutdown engine
9.7.8 Underspeed
Value
This alarm alerts the operator that a genset is running too slowly. Delay
Set
point
The alarm response is based on the engine speed as a percentage of the nominal speed. If the
engine speed drops below the set point for the delay time, then the alarm is activated.
time
Engine > Protections > Underspeed # *

Parameter Range Underspeed 1 Underspeed 2
Set point (lower than) 0 to 100 % of nominal speed 90 % 80 %

Delay 0 s to 3 min 5s 1s
• Engine not running • Engine not running

Inhibit(s)
• Idle run active • Idle run active
9.7.9 Crank failure
Value
The alarm response is based on the MPU/W/NPN/PNP input. This alarm is only available if the Set
magnetic pickup (MPU) has been chosen as the primary running feedback. point
tdelay
The timer starts when cranking starts (that is, when the Crank output is activated). The alarm is
activated if the set point has not been reached within the delay time. 0
time
Engine > Start sequence > Crank failure

Set point (lower than) 1 to 400 RPM 50 RPM

Delay 0 s to 3 min 20 s
Action Warning

9.7.10 Primary running feedback failure
This alarm is for genset running feedback failure. This alarm is only
available if more than one running feedback is present. The alarm is Start
(1)
activated if running is detected on any of the secondary running feedbacks attempt
1
but not on the primary running feedback.
The sequence diagram on the right shows how the primary running (2) Crank
feedback failure alarm works.
1. Start attempt: The controller gets a start signal.
Primary
2. Crank: The controller activates the Crank output.
(3) running
3. Primary running feedback: If the primary running feedback has failed, feedback
it does not detect the genset start.
4. Secondary running feedback: The secondary running feedback Secondary
detects the genset start. The crank stops after running is detected. The (4) running
alarm timer starts when running is detected on the secondary running feedback
feedback, but not on the primary running feedback. t1
5. Alarm: If the primary running feedback does not detect that the genset (5) Alarm
has started within the delay time (t1), the Primary running feedback
failure alarm is activated.
Engine > Running detection > Primary running feedback failure

This alarm is always Enabled.

Delay 0 s to 3 min 2s
Action Warning
9.7.11 Start failure
Attempts
This alarm is for genset start failure.

Set
If the genset has not started after the maximum number of start attempts are completed (see the point
parameter Normal), the controller activates this alarm.
0
time
Engine > Start sequence > Start attempts

Normal 1 to 10 3
Engine > Start sequence > Start failure

Action Block

9.7.12 Start enable removed during start
The alarm response is based on the engine start-up sequence. This alarm is activated if the engine start-up procedure is interrupted
by the loss of the Start enable input before the engine has started.
Engine > Start sequence > Start enable remove during start
9.7.13 Stop failure
Running
detection
This alarm is for genset stop failure. tdelay
ON
The controller attempts to stop the genset by activating the Stop coil output (if present) or
alternatively, by deactivating the Run coil output (if present). If Running detection is still ON
after the delay time, the controller activates this alarm. OFF
time
Engine > Stop sequence > Stop failure

Delay 0 s to 5 m 30 s
Action Warning
9.7.14 Engine started (external)
Running
detection Delay
This alarm is to alert the operator to an externally-initiated engine start.
On
The alarm is activated if the controller did not initiate an engine start, but Running detection
shows that the engine is running.
Off
Time
Engine > Start sequence > Engine started (external)

Action Warning

9.7.15 Engine stopped (external)
Running
detection Delay
This alarm alerts the operator to an externally-initiated engine stop.
On
The alarm is activated if the controller did not initiate an engine stop, but Running detection
shows that the engine has stopped.
Off
Time
Engine > Stop sequence > Engine stopped (external)

Action Block
9.7.16 Total running hours notification
Value
This alarm notifies the operator when the total running hours exceeds the set point.
Set
point
The alarm response is based on the Total running hours counter.
0
time
Engine > Maintenance > Running hours total

Parameter Range Running hours total
Set point 0 to 1,000,000 hours 500 hours
Action Warning
9.7.17 Trip running hours notification
Value
This alarm notifies the operator when the trip running hours exceeds the set point.
Set
point
The alarm response is based on the Trip running hours counter.
0
time
Engine > Maintenance > Running hours trip

Parameter Range Running hours trip
Action Warning

9.7.18 Voltage or frequency not OK
This alarm alerts the operator that the voltage or frequency is not in the required operation Value tdelay
range within a specified time after running detection is active. V OK
V
A delay timer starts when running detection activates. If the voltage and frequency are not in
the required operation ranges when the delay timer expires the alarm activates. f OK f
0
The alarm response is based on the voltage and frequency from the source. time
[Source] > AC setup > Voltage or frequency not OK

The alarm action is always Block.
Parameter Range Voltage or frequency not OK

• Engine not running

Inhibit(s) • [Breaker] closed
• Idle run active
9.7.19 Other GENSET controller alarms
The following alarms are also included on the GENSET controller:

• EIM # relay 4 wire break
• Magnetic pickup wire break
• P load sharing failure
• Q load sharing failure

10. HYBRID controller
10.1 About the HYBRID controller

A HYBRID controller controls an inverter with power source, and the inverter breaker. A system can include a number of HYBRID
controllers.
The HYBRID controller only directly controls an inverter and the inverter breaker. It does not control or provide any management of
the actual power source, for example a Battery Management System (BMS). The customer must ensure that the necessary
management system for the power source is installed and approved, according to the applicable Maritime classification societies.
Each HYBRID controller can control up to three non-essential load groups (NEL).
Example application
Busbar
DEIF network
HYBRID
controller
Breaker
Inverter
Power source
10.1.1 HYBRID controller functions
Functions
• Inverter start sequence and inverter stop sequence

◦ Running detection (Digital input)
◦ Start inverter and/or stop inverter for inverter control
Pre-programmed
• Breaker sequences
sequences
◦ Inverter breaker close sequence (with synchronisation)
◦ Inverter breaker open sequence (with de-loading)
• Inverter breaker blackout close

Counters ◦ Start attempts
◦ Running hours (total and trip)

Functions
◦ Running minutes (total and trip)

◦ Inverter breaker operations and trips
◦ Energy export to system (active and reactive)
◦ Energy import from system (active and reactive)
• Local mode
◦ Inverter start and stop with the start/stop push-buttons, and the breaker is controlled by the
close/open push-buttons.
Control modes
• Remote mode
◦ Inverter and breaker controlled from CustomLogic, a PLC or integrated Codesys * combined
with parameter settings.
10.2 HYBRID controller principles

10.2.1 HYBRID controller nominal settings
Inverter > Nominal settings > Nominal settings # *

Voltage (V) 10 V to 150 kV 400 V The phase-to-phase ** nominal AC voltage for the inverter.
inverter during normal operation.

Power (P) 1 kW to 0.9 GW 480 kW The nominal active power may be on the inverter nameplate.
Apparent power (S) 1 kVA to 1 GVA 600 kVA The nominal apparent power should be on the inverter nameplate.
Power factor (PF) 0.6 to 1 0.8 The power factor should be on the inverter nameplate.
Calculation method
Inverter > Nominal settings > Nominal settings # > Calculation method *
No calculation

More information
See Nominal power calculations for how these are used and calculated.


busbar.

10.2.2 Start inverter or stop inverter
Digital outputs
For a Inverter stop, if wire break detection is required, use EIM relay 4 ( * ) (terminals 9,10).
Requests the inverter to start using the configured inverter start

Inverter > Control > Start Digital output Pulse
sequence.
Requests the inverter to stop using the configured inverter stop

Inverter > Control > Stop Digital output Pulse
sequence.
10.2.3 Running detection
The controller uses digital running detection to receive inverter running feedback.
Running detection is a state calculated by the controller, and used by a number of functions. It is either OFF or ON. If digital running
detection shows that the inverter is running, then Running detection is ON.
Digital input
Inverter > Feedback > Digital running
Digital input Continuous Required to show the inverter is running.
detection
Example: Running detection ON
The following sequence diagram is an example of how Running detection changes during an inverter start. Running
detection changes from OFF to ON when running feedback detects that the inverter is running.

1. Start inverter: Request to start the inverter.
2. Inverter running: The inverter starts running after the start
request.
3. Digital running detection: Inverter > Feedback >
Digital running detection (digital input).
4. Running detection: Running detection changes from OFF to
ON.
Example: Running detection OFF
The following sequence diagram is an example of how Running detection changes during an inverter stop. Running
detection changes from ON to OFF when running feedback detects that the inverter is not running.
1. Stop inverter: Request to stop the inverter.

1. Stop inverter
2. Inverter running: The inverter stops running after the stop
request.
3. Digital running detection: Inverter > Feedback >
Digital running detection (digital input).
2. Inverter running
4. Running detection: Running detection changes from ON to
OFF.
3. Digital
running detection
4. Running detection
10.2.4 Ready for operation
The inverter associated with a HYBRID controller is ready for operation when there are no alarms blocking the start.
10.2.5 AC configuration
More information
The AC configuration and nominal settings chapter describes the AC configuration in general.
The following table shows how the general AC configuration description applies to the HYBRID controller.
HYBRID General name
Inverter [Source]
Busbar [Busbar]

10.2.6 Breaker configuration
More information
The Breakers, synchronisation and de-loading chapter describes breaker configuration in general. For the HYBRID
controller, replace "[Breaker]" with "Inverter breaker" in these descriptions.
10.3 Inverter start

10.3.1 Inverter start function
The controller software includes a pre-programmed inverter start sequence. For the inverter's start function, you must configure
these inputs and outputs, and parameters.
More information
See Start failure for how the inverter start alarm works, and how to configure it.
Controller modes
In LOCAL and REMOTE mode, the HYBRID controller uses these inputs and outputs, and parameters to start the inverter. See the
following sections for the inverter start flowcharts and sequences.
When the operator starts the inverter in switchboard control, the HYBRID controller is not involved. These sequences do not apply to
starting an inverter in switchboard control.
Required inverter start and run digital outputs

Inverter > Control > Start Digital output Pulse Connect this output to the inverter start.
Inverter > Control > Run Digital output Continuous This output is high when the inverter should run.
Optional inverter start digital inputs
Optional. When the controller is in LOCAL mode, the operator or another

Inverter > Command > Digital
Pulse system can activate this input to request the controller to start the
Start inverter input
inverter.
Optional. The operator or another system can activate this input so that
Inverter > Command > Digital the controller cannot start the inverter. The input blocks the start in both
Continuous
Block inverter start input LOCAL and REMOTE mode. However, the input will not prevent an
inverter start when the controller is under switchboard control.
Inverter > Command > Optional. When the controller is in LOCAL mode, the operator or another
Digital
Connect (Inverter/ Pulse system can activate this input to request the controller to connect the
input
breaker) inverter, synchronise and close the breaker.
Required parameters
Inverter > Start sequence
Breaker is open, Breaker is

Restrictions > Allow The controller allows the start of the inverter only if
closed, Breaker in any Breaker is open
start when the inverter breaker is in the state required.
state
If there is no running detection during the inverter

Start > Start on 1 s to 3 min 5s
start, then a start failure is activated.

10.3.2 Inverter start flowchart
This flowchart does not apply to switchboard control. In switchboard control, if the operator presses the push-button Start on the
display unit, the controller ignores the command and shows an info message.
Inverter 1. The controller checks if the command and mode match.

start command 2. The controller checks if the start conditions are OK:
• There are no active or unacknowledged alarms to prevent the inverter
start. These alarm actions prevent a inverter start:
1.
◦ Block
Command ◦ Trip breaker and stop inverter
match? No ◦ Trip breaker and AVR and stop inverter
◦ Stop inverter
Yes • Inverter start sequence restrictions are OK:
2.
◦ If configured as Breaker is open, breaker must be open.
Start ◦ If configured as Breaker is closed, breaker must be closed.
OK? No ◦ If configured as Breaker in any state, breaker can be open or
closed.
Yes 3. The controller activates the Start output and a timer.
3.
4. The controller checks if the Start on timer has expired:
Start output • If timer has expired, the controller activates the Start failure alarm.
activated 5. The controller checks the inverter Running detection:
• If Running detection is ON, the inverter has started.
• If Running detection is OFF, the controller continues checking while the
4. 5. Start on timer has not expired.
Running
Timer detection
expired? No ON? No
Yes Yes
Inverter
ALARM
started
10.3.3 Inverter start sequence
t1 = Start on (Inverter > Start sequence > Start > Start on)
Successful inverter start sequence
1. Start attempts
t1
2. Start inverter
1. Start attempts: The inverter starts during the first start attempt.
2. Start inverter: The inverter starts before the Start on timer expires.
3. Running detection: The inverter is regarded as started when Running detection is ON.

Failure of inverter start sequence
1. Start attempts
t1
2. Start inverter
4. Start failure
1. Start attempts: The inverter start attempt.

2. Start inverter: The inverter is requested to start.
3. Running detection: There is no running detection.
4. Start failure: The controller activates the Start failure alarm after the unsuccessful start attempt.
10.3.4 Interruption of the start sequence
These actions interrupt the inverter start sequence:

• The Emergency stop digital input is activated (for example, from the operator, or a PLC)
• When the controller is in LOCAL mode, there is a Stop inverter command. For example: The operator pushes the push-button
Stop on the display.

• The following alarm action:
◦ Trip breaker and stop inverter
The Block alarm action will not interrupt the inverter start sequence after it has begun. However, the Block alarm action prevents a
new inverter start sequence from starting.
If Running detection is ON, the controller regards the inverter as started. When the inverter has started, the actions listed here do
not interrupt the inverter start sequence, but result in a inverter stop instead.
10.4 Inverter stop

10.4.1 Inverter stop function
The controller software includes pre-programmed inverter stop sequences. For the inverter's stop function, you must configure these
More information
See Stop failure for how the inverter stop alarm works, and how to configure it.
Controller modes
In LOCAL and REMOTE mode, the HYBRID controller uses these inputs and outputs, and parameters to stop the inverter.
When the operator stops the inverter under switchboard control, the controller is not involved. These sequences do not apply to
stopping an inverter in switchboard control.

Required inverter stop digital outputs
Inverter > Control > Stop Digital output Pulse Connect this output to the inverter stop.
Inverter > Control > Run Digital output Continuous This output is low when the inverter is stopped.
Optional inverter stop digital inputs

Digital input Pulse
Stop inverter system can activate this input to request the controller to start the inverter.
Disconnect (Inverter/ Digital input Pulse system can activate this input to request the controller to disconnect the
breaker) inverter; deload and open the breaker.
Required parameters
Inverter > Stop sequence
Restrictions > Allow Breaker is open, Breaker is The controller allows the stop of the inverter only if
Breaker is open
stop when closed, Breaker in any state the inverter breaker is in the state required.
If there is running detection during the inverter stop,

Stop failure 1 s to 3 min 5s
then a stop failure is activated.
10.4.2 Inverter stop flowchart
This flowchart does not apply to switchboard control. When the controller is under switchboard control, it will not stop the inverter. If,
for example, the operator presses the push-button Stop on the display unit, the controller ignores this command, and the
controller display unit shows an info message.

Inverter 1. The controller checks that the command source and the
stop command controller mode match.
2. The controller checks the break state.
1.
3. The controller checks whether the stop sequence
Command restriction on the breaker state is OK:
match? No • If configured as Breaker in any state
Yes ◦ Breaker can be open or closed and the controller
2. either deloads or stops the inverter.
Breaker • If configured as Breaker is open
closed? No ◦ Breaker must be open to start deloading
Yes
otherwise an information message.
3. 3. • If configured as Breaker is closed
Inverter Inverter ◦ Breaker must be closed and then deloaded
stop sequence Info message stop sequence Info message
OK? No OK? No otherwise an information message.
Yes
4. The controller starts deloading the breaker..
Yes
4.
• The controllers checks if the load has reached the
Deload open set point.
breaker
• Deload timer:
◦ If the deload timer has not expired, the controller
continues to deload the breaker.
◦ If the deload timer has expired and load has not
Load < open Timer
set point? No expired? No reached the open set point, an alarm is
activated.
Yes Yes
◦ The controller continues attempt to deload the
ALARM breaker.
5. 5. The controllers attempts to stop the inverter and starts
the stop timer.
Stop
inverter • If the stop timer has expired and running detection is
ON, the controller activates the Stop failure alarm.
• If the stop timer has not expired, the controller
checks if running detection is OFF.
Running
Timer detection ◦ If running detection is OFF the inverter is
expired? No OFF? No
stopped.
Yes Yes ◦ If running detection is ON, the timer continues.
Inverter
ALARM
stopped
10.4.3 Inverter stop sequence
t1 = Stop failure (Inverter > Stop sequence > Stop failure)
Successful inverter stop sequence
1. Stop attempts
t1
2. Stop inverter
1. Stop attempts: The inverter stops during the first stop attempt.

2. Stop inverter: The inverter stops before the Stop failure timer expires.
3. Running detection: When the running detection is OFF, the controller regards the inverter as stopped.
Failure of inverter stop sequence
1. Stop attempts
t1
2. Stop inverter
4. Stop failure
1. Stop attempts: The inverter stop attempt.

2. Stop inverter: The inverter is requested to stop.
3. Running detection: There is running detection.
4. Stop failure: The controller activates the Stop failure alarm after the unsuccessful stop attempt.
10.4.4 Inverter trip and stop flowchart
The inverter breaker is tripped and the inverter stopped if either:

• Any alarm with action: Trip breaker and stop inverter
• The controller's Emergency stop input is deactivated.
Inverter 1. The controller checks whether the inverter breaker is open.

stop command • If the breaker is closed, the controller trips the inverter breaker.
2. The controller stops the inverter.
1. 3. The controller checks if the Stop failure timer has expired:
• If the Stop failure timer has expired, the controller activates the Stop
Trip failure alarm.
breaker
4. The controller checks if running detection is OFF:
• If Running detection is OFF the inverter is stopped.
2. • If Running detection is ON, the Stop failure timer continues.
Stop
inverter
3. 4.
Running
Timer detection
expired? No OFF? No
Yes Yes
Inverter
ALARM
stopped

10.5 Inverter breaker
10.5.1 Introduction
The inverter breaker connects the inverter to the busbar. The inverter breaker is an important part of the system safety, and trips to
protect the inverter from problems on the busbar. The inverter breaker also trips to stop inverter problems from disturbing the
busbar.
Configure the inverter breaker open or close conditions under Breakers > Inverter breaker configuration.
Table 10.1 Required inverter start and run output
Function Range Default Details
• Inverter started : The inverter must be running and synchronised with

Inverter is started, the busbar, before the inverter breaker can close.
Allow breaker Inverter is stopped, Inverter is • Inverter stopped : The inverter must not be running, before the inverter
close when Inverter is in any started breaker can close.
state • Inverter is in any state : The state of the inverter does not stop the
breaker closing.
• Inverter started : The inverter must be running and synchronised with

Inverter is started, the busbar, before the inverter breaker can open.
Allow breaker Inverter is stopped, Inverter is in • Inverter stopped : The inverter must not be running, before the inverter
open when Inverter is in any any state breaker can open.
state • Inverter is in any state : The state of the inverter does not stop the
breaker opening.
General breaker information

More information
See the Breakers, synchronisation and de-loading chapter for more information on synchronisation and breakers. This
includes the inputs and output functions and the parameters to configure.
[Breaker] refers to Inverter breaker. The breaker abbreviation ([*B]) is Breaker.
10.5.2 Inverter breaker close flowchart
This flowchart does not apply to switchboard control. When the controller is under switchboard control, it will not close the breaker.
If, for example, the operator presses the push-button Close breaker on the display unit, the controller ignores this command.

Breaker 1. The controller checks that the command source and the controller mode
close command match.
2. The controller checks if the close conditions are OK. The following
conditions must be met:
1. • The controller checks whether the inverter breaker is open. If the
inverter breaker is already closed, the sequence stops, and an info
Command
and mode Info message message is shown.
match? No • Inverter breaker configuration restrictions for Allow breaker close
when are OK:
Yes
◦ If configured as Inverter is started, inverter must be running.
2.
◦ If configured as Inverter is stopped, inverter must be stopped.
Close ◦ If configured as Inverter in any state, inverter can be running or
OK? No stopped.
• If the digital input Inverter breaker > Command > Block
Yes breaker close is activated, an info message is shown.
3.
3. The controller checks if the inverter is running.
Inverter
• If the inverter is not running, the controller continues from step 7.
No
running? 4. The controller checks if the voltage and frequency from the inverter are
in the allowed range *. If these are not in the range, then the controller
cancels the close command and displays an info message.
Yes
4. 5. The controller checks if the voltage and frequency on the busbar are in
the allowed range **. If these are not in the range, then the controller
Inverter cancels the close command and displays an info message.
V & Hz Info message
OK? No 6. The controller attempts to synchronise the inverter to the busbar.
• When the inverter and busbar are synchronised, the controller
Yes activates the Breakers > Inverter breaker > Control >
5. Breaker Close output to close the breaker.
Busbar • If the inverter and busbar do not synchronise within the time allowed,
V & Hz Info message the controller activates a Breaker synchronisation failure alarm.
OK? No
7. The controller checks if the inverter breaker is closed:
Yes • If the inverter breaker has closed, the inverter breaker close
6. sequence has been completed successfully.
• If the inverter breaker has not closed, the controller activates the
Sync
Breaker closing failure alarm.
breaker
NOTE * See Inverter > AC setup > Voltage and frequency

OK for the Inverter ranges.
** See Busbar > AC setup > Voltage and frequency
OK for the Busbar ranges.
Synchronised? Timer
No expired? No
Yes Yes
7.
Close ALARM
breaker
Breaker
ALARM
closed? No
Yes
Breaker
closed
10.5.3 Inverter breaker open flowchart
The following flowcharts shows the sequence that the controller normally uses to open the inverter breaker. The sequence depends
upon the active mode.
operator sends a Breaker open command while Block is active, the controller uses this sequence.
this command.

Breaker 1. The controller checks that the command source and the controller mode
open command match.
2. The controller checks whether the open conditions are OK. The following
conditions must be met:
1. • The system must have at least one other source of power running and
connected to the busbar (for example, another genset, a shaft
Command
and mode Info message generator or a shore controller).
match? No • The remaining gensets must not be overloaded after the breaker
opens.
Yes
• Inverter breaker configuration restrictions for Allow breaker open when
2.
are OK:
Open ◦ If configured as Inverter is started, inverter must be running.
OK? No ◦ If configured as Inverter is stopped, inverter must be stopped.
◦ If configured as Inverter in any state, inverter can be running or
Yes stopped.
3. • If the digital input Inverter breaker > Command > Block
breaker open is activated, an info message is shown.
Breaker
Info message 3. The controller checks whether the breaker is closed.
closed?
No
• If the breaker is open, an info message is shown.
Yes 4. The power management system de-loads the inverter:
4.
• When the load is outside the set point for the breaker to open, the
controller activates the Breaker > Control > Open output.
Deload
breaker • If the controller cannot de-load the breaker before the de-load timer
expires, the controller activates the Breaker de-load failure alarm. The
controller continues to try to de-load the breaker.
5. The controller checks whether the breaker has opened:
• If the breaker has opened, the breaker open sequence has been
Load
completed successfully.
outside of Timer
set point? No expired? No • If the breaker has not opened, the controller activates the Breaker
opening failure alarm.
Yes Yes
5.
Open ALARM
breaker
6.
Breaker
ALARM
open? No
Yes
Breaker
opened
10.5.4 Inverter breaker trip flowchart
The controller automatically trips the inverter breaker for these alarm actions:
• Trip breaker
• Trip breaker and stop inverter
• Trip AVR
• Trip breaker + AVR
• Trip breaker + AVR + stop inverter

The inverter breaker also trips if the controller's Emergency stop input is deactivated.
Table 10.2 Inverter breaker trip flowchart
Inverter breaker
trip
Open inverter 1. Open breaker: When a trip is required, the controller activates the Breakers >
breaker
breaker > Control > Open output to open the breaker.
2. Breaker opened: The controller checks whether the breaker has opened:
Breaker • If the breaker has not opened, the controller activates the Opening failure
ALARM
open No alarm.
Yes
Inverter
breaker tripped
10.6 Other HYBRID controller functions

10.6.1 Temperature-dependent power derating
The temperature-dependent power derating function reduces the inverter nominal load by reducing the inverter nominal power used
by load sharing. The derating function can be configured for up to three temperature measurements.
Analogue input
Inverter > Power derate > Derate # The measurement must be in This can measure any
Analogue input
temperature [C] (where # is 1 to 3) °C. temperature.
Parameters
Inverter > Power derate # *
Not enabled: The load sharing uses the inverter nominal power, no matter
what the derate temperature is.
Not enabled,
Enabled
load sharing within the configured range.
NOTE * Where # is 1, 2 or 3.
How it works
By default, the inverter nominal power is 100 % for temperatures up to 90 °C. If there is a Derate temperature input, then the power
is derated linearly to 80 % at 130 °C. However, you can create a customised curve for each temperature input.
Power derate affects load sharing, since load sharing is based on a percentage of nominal power.
The derating does not affect the alarms.

10.6.2 Percentage-dependent power derating
The percentage-dependent power derating function reduces the inverter nominal load by reducing the inverter nominal power used
by load sharing.
Analogue input
Inverter > Power derate > Percentage > Derate
Analogue input The measurement must be in %.
percentage [%]
Parameters
Inverter > Power derate > Percentage
Not enabled: The load sharing uses the inverter nominal power, no matter
what the derate percentage is.
Not enabled,
Enabled
load sharing within the configured range.
10.6.3 Inverter operating values as analogue outputs
You can configure an analogue output with a function for an inverter operating value. The controller receives this value from an
inverter measurement. The controller then adjusts the analogue output to reflect the inverter operating value.
Table 10.3 Analogue output

Inverter > Power derate > The controller outputs the derate temperature. For this
Analogue
Derate # temperature [C], where -50 to 200 °C function to work, there must be an analogue input to
output
# is 1 to 3 the controller with the inverter derate temperature.
10.6.4 Inverter states as digital outputs
You can configure a digital output with a function for an inverter state. The controller activates the digital output if the inverter state is
present. These can be useful for troubleshooting.
Digital outputs
Inverter > State > Running Digital output Continuous Activated if there is running detection for the inverter.
Inverter > State > Ready to Activated if there are no conditions that would block the
start controller from starting the inverter.

Inverter > State > Starting Digital output Continuous
programmed start inverter sequence.

Inverter > State > Stopping Digital output Continuous
programmed stop inverter sequence.

Inverter > State > Voltage
Digital output Continuous Voltage and frequency are within range.
and frequency OK
Inverter > State > No voltage

Digital output Continuous Voltage and frequency are not present or not measurable.
and frequency
10.6.5 Counters

• Start attempts
• Total running hours and minutes
• Trip running hours and minutes
• Inverter breaker operations and trips
• Energy export (active and reactive)
Running hours trip works like a car trip meter. For example, you can use this counter to track the running hours since the last
maintenance.

For each energy counter, you can configure a digital output to send a pulse every time a certain amount of energy is transferred. You
must configure the digital output function to see the parameters.
Digital outputs

Generator >
Production counters Digital
Pulse
> Active energy output
export pulse
Generator >
Pulse
> Reactive energy output
export pulse
Generator >
Pulse
> Active energy output
import pulse
Generator >
Pulse
> Reactive energy output
import pulse
Parameters
Inverter > Production counters > Active energy export

Inverter > Production counters > Reactive energy export
The length of the pulse that is sent. This value should be long enough so the
pulse can be registered by the external counter.
Inverter > Production counters > Active energy import

Inverter > Production counters > Reactive energy import

Active energy import pulse 1 Active energy import
Reactive energy import pulse 1 Reactive energy import

10.6.6 Trip AVR
The Trip AVR output ensures that AVR regulation is stopped when an alarm activates with a Trip AVR alarm action. In cases where
there is high voltage present, stopping the AVR regulation reduces the time required to stop an inverter in case of an emergency.
Inputs and outputs

Assign the Trip AVR output under Configure > Input/output. Select the hardware module, then select the output to configure.

AVR.
Inverter > AVR > Digital
Trip AVR output
Table 10.5 Trip AVR sequence diagram
2 To trip the AVR:

1
alarms 0
2. Trip AVR: [Source] > AVR > Trip AVR (digital output).
The controller activates this output until all alarms with
a Trip AVR (or similar) alarm action are not active.
(2) Trip
AVR
10.7 HYBRID controller protections

10.7.1 HYBRID controller alarms
These alarms are in addition to the AC protections and other alarms for PPU 300 controllers.
Alarms and protections
Emergency stop
Start sequence failure
Inverter Stop sequence failure
Total running hours notification
Trip running hours notification
GOV regulation error
GOV regulation mode not selected
GOV stand-alone configuration error *
GOV relay setup incomplete
P load sharing failure

Regulation
AVR regulation error
AVR regulation mode not selected
AVR stand-alone configuration error *
AVR relay setup incomplete
Q load sharing failure
Hybrid-SG max. parallel time

Maximum parallel time
Hybrid-SC max. parallel time



10.7.2 Alarm actions
The HYBRID controller has the following alarm actions:

• Warning
• Block
• PMS-controlled stop
• Trip breaker
• Trip breaker and stop inverter
• Trip AVR *
• Trip breaker + AVR *
• Trip breaker + AVR + stop inverter *
10.7.3 Inhibits
The controller includes the following inhibits:

Inverter running Digital running detection is ON.
Inverter not running Digital running detection is OFF.
The Breakers > Inverter breaker > Feedback > Breaker closed digital input is
Inverter breaker closed
activated.
Inverter breaker open The Breakers > Inverter breaker > Feedback > Breaker open digital input is activated.
Inverter voltage present The inverter voltage is above 10 % of the nominal voltage.
No inverter voltage The inverter voltage is below 10 % of the nominal voltage.
Inverter frequency present The inverter frequency is above 10 % of the nominal frequency.
No inverter frequency The inverter frequency is below 10 % of the nominal frequency.
• The inverter breaker is closed
measurements
PTI running The Alarm system > Inhibits > PTI running digital input is activated.

PTO running The Alarm system > Inhibits > PTO running digital input is activated.
Standby running (Hybrid) The Alarm system > Inhibits > Standby running (Hybrid) digital input is activated.
More information
The Breakers, synchronisation and de-loading chapter describes breaker handling and alarms in general.
The following table shows where to configure these alarms for the HYBRID controller, as well as which general alarm corresponds to
each HYBRID controller alarm.
Table 10.6 Breaker alarm names for the HYBRID controller
HYBRID alarm Configure > Parameters > General name
Breakers > Inverter breaker monitoring > Synchronisation

Breaker synchronisation failure Breaker synchronisation failure
failure
Breaker de-load failure Breakers > Inverter breaker monitoring > De-load failure Breaker de-load failure
Vector mismatch Breakers > Inverter breaker monitoring > Vector mismatch Vector mismatch
Breaker opening failure Breakers > Inverter breaker monitoring > Opening failure Breaker opening failure
Breaker closing failure Breakers > Inverter breaker monitoring > Closing failure Breaker closing failure
Breaker position failure Breakers > Inverter breaker monitoring > Position failure Breaker position failure
Breaker trip (external) Breakers > Inverter breaker monitoring > Tripped (external) Breaker trip (external)
Breaker short circuit Breakers > Inverter breaker monitoring > Short circuit Breaker short circuit
Breaker configuration failure - Breaker configuration failure
Inverter phase sequence error Inverter > AC setup > Phase sequence error Phase sequence error
10.7.5 AC alarms
More information
The AC configuration and nominal settings chapter describes AC alarms in general.
The following tables show where to configure these alarms for the HYBRID controller.
Table 10.7 Inverter AC alarm names for the GENSET controller
Controller alarm Configure > Parameters > General name
Inverter over-voltage 1 or 2 Inverter > Voltage protections > Over-voltage 1 or 2 Over-voltage
Inverter under-voltage 1 or 2 Inverter > Voltage protections > Under-voltage 1 or 2 Under-voltage
Inverter voltage unbalance Inverter > Voltage protections > Voltage unbalance Voltage unbalance
Negative sequence voltage Inverter > Voltage protections > Negative sequence voltage Negative sequence voltage
Zero sequence voltage Inverter > Voltage protections > Zero sequence voltage Zero sequence voltage

Inverter over-current 1 or 2 Inverter > Current protections > Over-current 1 or 2 Over-current
Fast over-current 1 or 2 Inverter > Current protections > Fast over-current 1 or 2 Fast over-current
Inverter > Current protections > Current unbalance (average Current unbalance (average
calc.) calc.)
Inverter > Current protections > Current unbalance (nominal Current unbalance (nominal
calc.) calc.)
Directional over-current 1 or 2 Inverter > Current protections > Directional over-current 1 or 2 Directional over-current
Inverse time over-current Inverter > Current protections > Inverse time over-current Inverse time over-current
Negative sequence current Inverter > Current protections > Negative sequence current Negative sequence current
Zero sequence current Inverter > Current protections > Zero sequence current Zero sequence current
Stabilised differential
Stabilised differential current Inverter > Current protections > Stabilised differential current
current
High set differential current Inverter > Current protections > High set differential current High set differential current
Inverter over-frequency 1 or 2 Inverter > Frequency protections > Over-frequency 1 or 2 Over-frequency
Inverter under-frequency 1 or 2 Inverter > Frequency protections > Under-frequency 1 or 2 Under-frequency
Overload 1 or 2 Inverter > Power protections > Overload 1 or 2 Overload
Reverse power 1 or 2 Inverter > Power protections > Reverse power 1 or 2 Reverse power
Overload reverse power 1 or 2 Inverter > Power protections > Overload reverse power 1 or 2 Overload reverse power
Inverter > Reactive power protections > Reactive power export

Reactive power export 1 or 2 Reactive power export
1 or 2
Inverter > Reactive power protections > Reactive power import

Reactive power import 1 or 2 Reactive power import
1 or 2
Table 10.8 Busbar AC alarm names for the HYBRID controller
Busbar over-voltage 1 or 2 Busbar > Voltage protections > Over-voltage 1 or 2 Busbar over-voltage
Busbar under-voltage 1 or 2 Busbar > Voltage protections > Under-voltage 1 or 2 Busbar under-voltage
Busbar over-frequency 1 or 2 Busbar > Frequency protections > Over-frequency 1 or 2 Busbar over-frequency
Busbar under-frequency 1 or 2 Busbar > Frequency protections > Under-frequency 1 or 2 Busbar under-frequency
10.7.6 Emergency stop
Digital
input
tdelay
You can configure one of the controller's digital inputs as the emergency stop. high
When this input is present, the alarm is always enabled. The alarm parameters are not
visible. The alarm action is Trip breaker and stop inverter.
low
time
Assign the Emergency stop input under Configure > Input/output. Select the hardware module, then select the input to configure.

Wire the emergency stop digital input so that it is normally activated. If

Alarm system > Additional
Digital input Continuous the emergency stop digital input is not activated, then controller
functions > Emergency stop
activates the Emergency stop alarm.
CAUTION
The Emergency stop is part of the safety chain

The Emergency stop is part of the safety chain, and this digital input function should only be used to inform the controller
of the emergency stop. However, the controller's emergency stop input cannot be used as the system's only emergency
stop. For example, if the controller is unpowered, it cannot respond to the emergency stop digital input.
10.7.7 Start failure
Attempts
This alarm is for inverter start failure.

Set
If the inverter has not started after the Start on delay and/or the restriction on breaker state is not point
correct, the controller activates this alarm.
0
time
Configure the start failure parameters under Configure > Parameters > Inverter > Start sequence > Start failure.
Table 10.9 Default parameters
Action Block
Configure the start failure parameters under Configure > Parameters > Inverter > Start sequence.
Table 10.10 Other parameters
Start > Start on 1 s to 3 min 5s
Restrictions > Allow start when Breaker is open, Breaker is closed, Breaker in any state Breaker is open
10.7.8 Stop failure
Running
detection
tdelay
This alarm is for inverter stop failure. ON
The controller attempts to stop the inverter. If Running detection is still ON after the delay time
and/or the restriction on breaker state is not correct, the controller activates this alarm.
OFF
time

Configure the parameters under Configure > Parameters > Inverter > Stop sequence > Stop failure.
Delay 0 s to 5 m 5s
Action Warning
Configure the start failure parameters under Configure > Parameters > Inverter > Start sequence > Restrictions.
Table 10.12 Other parameters
Allow stop when Breaker is open, Breaker is closed, Breaker in any state Breaker is open
10.7.9 Inverter started (external)
Running
detection Delay
This alarm is to alert the operator to an externally-initiated inverter start.
On
The alarm is activated if the controller did not initiate an inverter start, but Running detection
shows that the inverter is running.
Off
Time
Configure the parameters under Configure > Parameters > Inverter > Start sequence > Inverter started (external).
Action Warning
10.7.10 Inverter stopped (external)
Running
detection Delay
This alarm alerts the operator to an externally-initiated inverter stop.
On
The alarm is activated if the controller did not initiate an inverter stop, but Running detection
shows that the inverter has stopped.
Off
Time
Configure the parameters under Configure > Parameters > Inverter > Stop sequence > Inverter stopped (external).

Action Block
10.7.11 Total running hours notification
Value
This alarm notifies the operator when the total running hours exceeds the set point.
Set
point
The alarm response is based on the Total running hours counter.
0
time
Configure these parameters under Configure > Parameters > Inverter > Maintenance > Running hours total.
Parameter Range Running hours total
Action Warning
10.7.12 Trip running hours notification
Value
This alarm notifies the operator when the trip running hours exceeds the set point.
Set
point
The alarm response is based on the Trip running hours counter.
0
time
Configure these parameters under Configure > Parameters > Inverter > Maintenance > Running hours trip.
Parameter Range Running hours trip
Action Warning

10.7.13 Voltage or frequency not OK
This alarm alerts the operator that the voltage or frequency is not in the required operation range Value tdelay
within a specified time after running detection is active. V OK
V
A delay timer starts when running detection activates. If the voltage and frequency are not in the
required operation ranges when the delay timer expires the alarm activates. f OK f
0
The alarm response is based on the voltage and frequency from the source. time
See Configure > Parameters > Inverter > AC setup. The parameters that the alarm is based on are under Voltage and
frequency OK. The alarm is configured under Voltage or frequency not OK.
The alarm action is always Block.
Parameter Range Voltage or frequency not OK

Inhibit(s)
10.7.14 Other HYBRID controller alarms
The following alarms are also included on the HYBRID controller:

• EIM # relay 4 wire break
More information
See Hardware characteristics and configuration for more information.

11. SHAFT generator controller
11.1 About the SHAFT generator controller

A SHAFT generator controller controls and protects the system when a shaft generator is connected. The SHAFT generator
controller also controls and protects the shaft generator breaker.
11.1.1 SHAFT generator controller functions
Functions
Running detection • Multiple feedback options: Frequency, MPU/W/NPN/PNP (RPM), Digital input
Synchronisation and de-

• Broadcast the set point for GENSET controllers
loading

◦ Breaker operations and trips
◦ Energy import (active and reactive)
Counters
• Regulators for relay outputs and analogue outputs

◦ Regulation delay
• Governor regulation
Regulation
◦ Fixed power
◦ Active power load sharing
◦ Active power ramp down

Functions
◦ Frequency-dependent power droop

• AVR regulation
◦ Fixed cos phi
◦ Fixed reactive power
◦ Reactive power load sharing
◦ Voltage droop
• Configurable: Power ramp up, power ramp down
11.2 SHAFT generator controller principles

11.2.1 Nominal settings
Generator nominal settings

Generator > Nominal settings > Nominal settings # *
Voltage (V) 10 V to 150 kV 400 V The phase-to-phase nominal voltage for the shaft generator.
shaft generator during normal operation.

Power (P) 1 kW to 900 MW 480 kW The nominal active power may be on the shaft generator nameplate.
Apparent power (S) 1 kVA to 1 GVA 600 kVA The nominal apparent power should be on the shaft generator nameplate.
Power factor (PF) 0.6 to 1 0.8 The power factor should be on the shaft generator nameplate.
The controller uses the nominal settings to calculate the nominal reactive power (nominal Q) for the shaft generator. The controller
can be configured to calculate the nominal active power (nominal P) or the nominal apparent power (nominal S). In this case, the
controller uses the calculated values, and ignores any entered values.
More information
See Nominal power calculations.


busbar.


11.3 Shaft generator breaker

11.3.1 How it works
The shaft generator breaker (SGB) connects the shaft generator to the busbar. For the shaft generator breaker to close, the shaft
generator must be running, and the busbar must be synchronised with the shaft generator. The shaft generator breaker is an
important part of the system safety, and trips to protect the shaft generator from problems on the busbar. The shaft generator
breaker also trips to stop shaft generator problems from disturbing the busbar.
More information
See Breakers, synchronisation and de-loading for information about synchronisation and breakers. This includes the inputs
and output functions and the parameters to configure.
For the SHAFT generator controller, the breaker abbreviation ([*B]) is SGB. [Breaker] refers to Shaft generator breaker.
11.3.2 Shaft generator breaker close flowchart
More information
See Shaft generator breaker blackout close flowchart for how to allow the shaft generator to connect to a dead busbar.

Shaft generator breaker (SGB) close flowchart
SGB close
command
2. SGB open: The controller checks whether the breaker is open. If the breaker
is already closed, the sequence stops, and an info message is shown.
Command 3. SG V&Hz OK: The controller checks whether the voltage and frequency from
and mode Info message the generator are within the allowed range. If these are not in the range, then
No
match the controller cancels the close command and displays an info message.
Yes 4. Busbar V&Hz OK: The controller checks whether the voltage and frequency
on the busbar are within range. If these are not in the range, then the
controller cancels the close command and displays an info message.
SGB open Info message 5. Synchronised: The controller broadcasts the required set point on the
No
busbar section. The GENSET controllers that have external network set point
Yes activated then use this set point for regulation.
• If the shaft generator and busbar are synchronised, the controller
activates the Breakers > Shaft generator breaker > Control
SG V&Hz Info message > SGB close output to close the breaker.
OK No
• If the shaft generator and busbar do not synchronise within the time
Yes allowed, the controller activates an SGB synchronisation failure alarm.
6. SGB closed: The controller checks whether the breaker has closed.
Busbar V&Hz • If the breaker has closed, the breaker close sequence has been
Info message
OK No completed successfully.
• If the breaker has not closed, the controller activates the SGB closing
Yes
failure alarm.
Broadcast set
point to busbar
section
Synchronised Sync timer

No expired No
Yes Yes
Alarm
Close SGB
SGB closed Alarm

No
Yes
SGB closed
11.3.3 Shaft generator breaker open flowchart
operator sends an SGB open command while Block is active, the controller uses the shaft generator breaker open sequence, shown
below, to open the SGB.

(except for a trip). If, for example, the operator presses the push-button Open breaker on the display, the controller ignores this
command.
Shaft generator breaker (SGB) open flowchart

1. Command and mode match: The controller checks
SGB open
that the command source and the controller mode
command
match.
2. SGB closed: The controller checks whether the breaker
is closed. If the breaker is open, the sequence ends.
Command
and mode Info message 3. Load < open set point: The controller broadcasts the
No
match required set point on the busbar section. The GENSET
Yes controllers that have external network set point activated
then use this set point for regulation.
• When the load is less than the set point for the
SGB
Info message breaker to open, the controller activates the
closed No
Breakers > Shaft generator breaker >
Yes Control > SGB open output.
• If the controller cannot de-load the breaker before
the de-load timer expires, the controller activates the
Broadcast set SGB de-load failure alarm. The controller continues
point to busbar to try to de-load the breaker.
section
4. SGB opened: The controller checks whether the
breaker has opened:
• If the breaker has opened, the shaft generator
Deload breaker open sequence has been completed
Load < open timer
No successfully.
set point expired No
• If the breaker has not opened, the controller
Yes
Yes activates the SGB opening failure alarm.
Yes Alarm
Open SGB
SGB opened Alarm

No
Yes
SGB opened
NOTICE
Open breaker blackout

Opening the shaft generator breaker may cause a blackout.
Activate network set point for all the GENSET controllers on the busbar section. If the network set point is only activated for one
GENSET controller, that controller tries to take the whole load.
11.3.4 Shaft generator breaker blackout close flowchart
The Blackout close function sets the action that the controller allows when a dead busbar is detected. If the parameter is not Off,
then an operator or a remote input can close the breaker directly to the black busbar.

DANGER!
Incorrect blackout close settings

Blackout conditions
is fixed.


◦ A digital input with the function Breakers > Shaft generator breaker > Feedback > SGB short circuit was activated.
• The busbar and/or shaft generator AC measurements are not OK.
• The parameter Busbar > AC setup > Blackout detection > Blackout delay timer has not expired.
Blackout close parameters

Breakers > Shaft breaker configuration
Off: The controller will never activate the close breaker relay if any blackout is
detected.
• Off Generator is dead, busbar OK*: If a blackout is detected at the Generator, but
the Busbar is stable, then the controller allows the breaker to close.
• Generator is dead,
busbar OK
Blackout Generator OK, busbar is dead: If a blackout is detected at the Busbar and the
• Generator OK, Off
close Generator is stable, then the controller allows the breaker to close.
busbar is dead
• One busbar is alive
One busbar is alive*: If a blackout is detected at the Generator or the Busbar,
• On and the live busbar is stable, then the controller allows the breaker to close.
On*: If a blackout is detected at the Generator and/or at the Busbar, then the
controller allows the breaker to close.
DANGER!
System protection
The system must be adequately protected if you use the (*) options for generator applications.

Breaker close
command
Breaker close
Blackout
No flowchart
Yes
Check Blackout
close parameter
Parameter:
Parameter:
Generator is Parameter: One
Parameter: Off Generator OK, Parameter: On
dead, busbar busbar is alive
busbar is dead
OK
Only Only Only

Info message Generator is Busbar is one live
No No No
dead dead busbar
Info message
Activate close
breaker relay
Breaker
closed? No
Yes Alarm
GB closed
3. Check Blackout close parameter: The controller checks the Blackout close parameter:
a. Off: The controller takes does not allow the breaker to close. The controller shows an info message, and the sequence ends.
b. Generator is dead, busbar OK: The controller checks whether the blackout was detected only at the Generator.
• Blackout only at the Generator: The controller activates the close breaker relay.
• Blackout was only at the Busbar or on both sides of the breaker: The controller shows an info message, and the
sequence ends.
c. Generator OK, busbar is dead: The controller checks whether the blackout was detected only at the Busbar.
• Blackout only at the Busbar: The controller activates the close breaker relay.
• Blackout only at the Generator or on both sides of the breaker: The controller shows an info message and the sequence
ends.
d. Only one live busbar: The controller checks if the blackout was detected only at the Generator, or only at the Busbar.
• Blackout only at the Generator, or only at the Busbar: The controller activates the close breaker relay.

4. Breaker closed: The controller checks whether the shaft generator breaker has closed.
• If the shaft generator breaker has closed, the blackout close sequence has been completed successfully.
• If the shaft generator breaker has not closed the controller activates the SGB closing failure alarm.
11.3.5 Shaft generator breaker trip flowchart
The controller automatically trips the shaft generator breaker (SGB) for this alarm action:
• Trip shaft generator breaker
The breaker is not de-loaded for a trip.
Shaft generator breaker trip flowchart

1. Open SGB: When a trip is required, the controller activates the Breakers >
Shaft generator
breaker trip Shaft generator breaker > Control > SGB open output to open the
breaker.
2. SGB opened: The controller checks whether the breaker has opened:
Yes
Open SGB
• If the breaker has not opened, the controller activates the SGB opening failure
alarm.
SGB opened Alarm

No
Yes
SGB tripped
11.4 Other SHAFT generator controller functions

11.4.1 Shaft generator regulation
You can use the SHAFT generator controller regulate a shaft generator, in just the same way as you would use a GENSET
controller to regulate a genset. You can use shaft generator regulation to transfer load directly from one shaft generator to another.
NOTICE
Shaft must support regulation

To use this function, the shaft generator must support regulation.
DANGER!
Ship speed during shaft generator regulation

During shaft generator regulation, the ship crew cannot use the shaft to regulate the ship speed.
More information
See Regulation for detailed description about regulation.

Required shaft generator regulation input and outputs
The controller only activates shaft generator

regulation if this input is configured and activated.
Regulators > Common
> Regulation ON
Note: This input is only visible after configuring a
regulator.
Analogue output Depends on the output

Governor regulation See the Regulation chapter.
Digital output type
Analogue output Depends on the output

AVR regulation See the Regulation chapter.
Digital output type
When the regulation outputs are configured, all of the other regulation inputs and outputs become available.
Parameters
When the regulation outputs are configured, all of the regulation parameters become available.
For regulation, you must configure the SHAFT generator running feedback measurement. See Running detection under GENSET
controller.
How it works
When Regulation ON is activated, the SHAFT generator controller can receive regulation set points from other controllers on the
DEIF network. The SHAFT generator controller can send regulation signals to adjust the frequency and/or voltage of the shaft
generator.
You can use any of the following for shaft generator regulation:
• The regulation inputs and outputs
• The regulation parameters
• The regulation alarms
• The regulation modes
• External regulation set points
• Stand-alone GAM3.2
Shaft generator regulation does not include the following:

• Shaft prime mover start and stop
• Overspeed and underspeed protections
Shaft generator load transfer without connecting gensets example
The system has two shaft generators (SG1 and SG2). SG1 has shaft generator regulation.
SG1 is running and is connected to the busbar. To transfer the load from SG1 to SG2:
1. If it is not already running, start SG2.
2. Activate Regulation ON on SG1.
3. Select the External set point (Network) regulation mode on SG1.
4. Activate Close SGB on SG2.
• SG1 regulates its frequency and voltage to match the set point from SG2.
• When the shaft generators are synchronised, the breaker for SG2 closes.
5. After SG1 and SG2 are connected, activate Open SGB on SG1.
• SG1 de-loads and opens its breaker.
The load has successfully been transferred from SG1 to SG2.

11.4.2 Counters
You can view some counters on one of the live data pages in the display unit and PICUS.
You can view, edit and reset all the counters on the display unit under Configure > Counters. The counters include breaker
operations and trips, active and reactive power export, and active and reactive power import. There are also counters for the
associated external breaker operations.
Energy counter digital outputs

For each energy counter, you can configure a digital output to send a pulse every time a certain amount of energy is transferred.
Digital outputs
Function I/O Type

Generator > Production counters > Active energy export pulse Digital output Pulse
Generator > Production counters > Reactive energy export pulse Digital output Pulse
Parameters
You must configure the digital output function to see these parameters.
Generator > Production counters > Active energy export

Generator > Production counters > Reactive energy export

Generator > Production counters > Active energy import

Generator > Production counters > Reactive energy import


Active energy export pulse Active energy export
Reactive energy export pulse Reactive energy export
Active energy import pulse Active energy import
Reactive energy import pulse Reactive energy import

2. Configure the digital output using the display unit or PICUS to Active energy export pulse.
11.4.3 Trip AVR
The Trip AVR output ensures that excitation is stopped when an alarm activates with a Trip AVR alarm action. In cases where there
is high voltage present, stopping the excitation reduce the time required to stop an engine in case of an emergency.
Digital output
AVR.
[Source] > AVR Digital
> Trip AVR output
Trip AVR sequence diagram
2 To trip the AVR:

1
alarms 0
2. Trip AVR: [Source] > AVR > Trip AVR (digital
output). The controller activates this output until all
alarms with a Trip AVR (or similar) alarm action are not
(2) Trip active.
AVR
11.5 SHAFT generator controller protections

11.5.1 SHAFT generator controller protections

Running feedback Primary running feedback failure
• GOV regulation error

• GOV regulation mode not selected
• GOV stand-alone configuration error *
• P load sharing failure
Regulation
• AVR regulation error
• AVR regulation mode not selected
• AVR stand-alone configuration error *
• Q load sharing failure



• Warning
• Block
• Trip shaft breaker
• Trip AVR *
• Trip generator breaker + AVR *
• Trip generator breaker + AVR + stop engine *
• Trip generator breaker + AVR + shutdown engine *
11.5.3 Inhibits
SHAFT generator controller inhibits

Shaft breaker closed The Shaft generator breaker > Feedback > SGB closed digital input is activated.
Shaft breaker open The Shaft generator breaker > Feedback > SGB open digital input is activated.
Generator voltage present The shaft generator voltage is above 10 % of the nominal voltage.
No generator voltage The shaft generator voltage is below 10 % of the nominal voltage.
Generator frequency
The shaft generator frequency is above 10 % of the nominal frequency.
present
No generator frequency The shaft generator frequency is below 10 % of the nominal frequency.
Controller under SWBD The Mode > Switchboard control digital input is activated, OR a system problem forced the
control controller under switchboard control.
ACM wire break All these conditions are met:

• The shaft generator breaker is closed
measurements
Inhibit 1 The Inhibits > Activate inhibit 1 digital input is activated.
More information
See Breakers, synchronisation and de-loading for a description of breaker handling and alarms in general.
The following table shows where to configure these alarms for the SHAFT generator controller, as well as which general alarm
corresponds to each SHAFT generator controller alarm.
Breaker alarm names for the SHAFT generator controller

SHAFT generator alarm Parameters General name
Breakers > Shaft breaker monitoring >
SGB synchronisation failure Breaker synchronisation failure
Breakers > Shaft breaker monitoring > De-load

SGB de-load failure Breaker de-load failure
failure
Breakers > Shaft breaker monitoring > Vector

mismatch
Breakers > Shaft breaker monitoring > Opening

SGB opening failure Breaker opening failure
failure
Breakers > Shaft breaker monitoring > Closing

SGB closing failure Breaker closing failure
failure
Breakers > Shaft breaker monitoring > Position

SGB position failure Breaker position failure
failure
Breakers > Shaft breaker monitoring > Tripped

SGB trip (external) Breaker trip (external)
(external)
Breakers > Shaft breaker monitoring > Short

SGB short circuit Breaker short circuit
circuit
SGB configuration failure - Breaker configuration failure
Generator phase sequence error Generator > AC setup > Phase sequence error Phase sequence error
11.5.5 AC alarms
More information
See AC configuration and nominal settings for a description of AC alarms in general.
The following tables show where to configure these alarms for the SHAFT generator controller.

Generator AC alarm names for the SHAFT generator controller
Generator over-voltage 1 Over-voltage
1

Generator over-voltage 2 Over-voltage
2

Generator under-voltage 1 Under-voltage
1

Generator under-voltage 2 Under-voltage
2
Generator > Voltage protections > Voltage

Generator voltage unbalance Voltage unbalance
unbalance

Generator over-current 1 Over-current
1

Generator over-current 2 Over-current
2

Fast over-current 1 Fast over-current
current 1

current 2
Current unbalance (average Generator > Current protections > Current Current unbalance (average
calc.) unbalance (average calc.) calc.)
Current unbalance (nominal Generator > Current protections > Current Current unbalance (nominal
calc.) unbalance (nominal calc.) calc.)
Directional over-current 1 Directional over-current
over-current 1

Directional over-current 2 Directional over-current
over-current 2
Generator > Current protections > Inverse time

over-current
Generator > Current protections > Stabilised Stabilised differential

Stabilised differential current
differential current current
Generator > Current protections > High set
High set differential current High set differential current
differential current

Generator over-frequency 1 Over-frequency
frequency 1

Generator over-frequency 2 Over-frequency
frequency 2

Generator under-frequency 1 Under-frequency
frequency 1

Generator under-frequency 2 Under-frequency
frequency 2
Overload 1 Generator > Power protections > Overload 1 Overload
Overload 2 Generator > Power protections > Overload 2 Overload
Reverse power 1 Generator > Power protections > Reverse power 1 Reverse power
Reverse power 2 Generator > Power protections > Reverse power 2 Reverse power
Reactive power export 1 Reactive power export
Reactive power export 1


Reactive power import 1 Reactive power import
Reactive power import 1

Busbar AC alarm names for the SHAFT generator controller

Busbar over-voltage 1 Busbar > Voltage protections > Over-voltage 1 Busbar over-voltage
Busbar under-voltage 1 Busbar > Voltage protections > Under-voltage 1 Busbar under-voltage
Busbar over-frequency 1 Busbar > Frequency protections > Over-frequency 1 Busbar over-frequency
Busbar under-frequency 1 Busbar > Frequency protections > Under-frequency 1 Busbar under-frequency

12. SHORE connection controller
12.1 About the SHORE connection controller

A SHORE connection controller controls and protects the system and the shore connection breaker when a shore connection is
connected.
12.1.1 SHORE connection controller functions
Functions
Synchronisation and de-

• Broadcast the set point for GENSET controllers
loading

◦ Breaker operations and trips
Counters

12.2 SHORE connection controller principles
Shore busbar nominal settings

Shore connection > Nominal settings > Nominal settings # *
Voltage (V) 10 V to 150 kV 400 V The phase-to-phase nominal voltage for the shore connection.
Current (I) 1 A to 9 kA 867 A The maximum current from the shore connection during normal operation.
The system nominal frequency. All the controllers in the system should
have the same nominal frequency.
Configure the value according to the shore connection. Set the value to
Power (P) 1 kW to 900 MW 480 kW ensure the shore connection over-power alarm is triggered at the correct
time.
Apparent power (S) 1 kVA to 1 GVA 600 kVA Shore connection apparent power.
Power factor (PF) 0.6 to 1 0.8 Shore connection power factor.
The controller uses the nominal settings to calculate the nominal reactive power (nominal Q) for the shore connection. The controller
can be configured to calculate the nominal active power (nominal P) or the nominal apparent power (nominal S). In this case, the
controller uses the calculated values, and ignores any entered values.
More information
See Nominal power calculations.
Ship busbar nominal settings


busbar.

12.3 Shore connection breaker

12.3.1 How it works
The shore connection breaker (SCB) connects the shore connection to the busbar. For the shore connection breaker to close, the
shore connection must be live, and the ship busbar must be synchronised with the shore connection. The shore connection breaker

is an important part of the system safety, and trips to protect the shore connection from problems on the busbar. If it is configured
correctly, the shore connection breaker also trips to stop shore connection problems from disturbing the busbar.
More information
See Breakers, synchronisation and de-loading for more information about synchronisation and breakers. This includes the
inputs and output functions and the parameters to configure.
For the SHORE connection controller, the breaker abbreviation ([*B]) is SCB. [Breaker] refers to Shore connection breaker.
12.3.2 Shore connection breaker close flowchart
More information
See Shore connection breaker blackout close flowchart for how to allow the shore connection to connect to a dead busbar.

Shore connection breaker (SCB) close flowchart
SCB close
command
2. SCB open: The controller checks whether the breaker is open. If the breaker
Command 3. SC V&Hz OK: The controller checks whether the voltage and frequency from
and mode Info message the shore connection are within the allowed range. * If these are not in the
No
match range, then the controller cancels the close command and displays an info
Yes message.
4. Busbar V&Hz OK: The controller checks whether the voltage and frequency
on the ship busbar are within range. * If these are not in the range, then the
SCB open Info message controller cancels the close command and displays an info message.
No
5. Broadcast set point to busbar section: The controller broadcasts the
Yes required set point on the ship busbar section. The GENSET controllers that
have external network set point activated then use this set point for
regulation.
SC V&Hz Info message • If the shore connection and ship busbar are synchronised, the controller
OK No
activates the Breakers > Shore connection breaker >
Yes Control > SCB close output to close the breaker.
• If the shore connection and ship busbar do not synchronise within the
time allowed, the controller activates an SCB synchronisation failure
Busbar V&Hz Info message alarm.
OK No
6. SCB closed: The controller checks whether the breaker has closed.
Yes
• If the breaker has closed, the breaker close sequence has been
completed successfully.
Broadcast set • If the breaker has not closed, the controller activates the SCB closing
point to busbar failure alarm.
section

No expired No
Yes Yes
Alarm
Close SCB
SCB closed Alarm

No
Yes
SCB closed
NOTE * See [Source] / [Busbar] > AC setup > Voltage and frequency OK for these ranges.
12.3.3 Shore connection breaker open flowchart
operator sends an SCB open command while Block is active, the controller uses this sequence.

This flowchart does not apply to switchboard control. When the controller is in switchboard control, it will not open the breaker
(except for a trip caused by an alarm). If, for example, the operator presses the push-button Open breaker on the display unit,
the controller ignores this command.
Shore connection breaker (SCB) open flowchart

SCB open
command
match.
2. SCB closed: The controller checks whether the breaker
Command
and mode Info message 3. Broadcast set point to busbar section: The controller
No
match broadcasts the required set point on the busbar section.
Yes The GENSET controllers that have external network set
point activated then use this set point for regulation.
• When the load is less than the set point for the
SCB
Info message breaker to open, the controller activates the
closed No
Breakers > Shore connection breaker >
Yes Control > SCB open output.
the de-load timer expires, the controller activates the
Broadcast set SCB de-load failure alarm. The controller continues
point to busbar to try to de-load the breaker.
section
4. SCB opened: The controller checks whether the
breaker has opened:
• If the breaker has opened, the shore connection
Deload breaker open sequence has been completed
Load < open timer
No successfully.
Yes
Yes activates the SCB opening failure alarm.
Yes Alarm
Open SCB
SCB opened Alarm

No
Yes
SCB opened
NOTICE
Open breaker blackout

Opening the shore connection breaker may cause a blackout.
Activate network set point for all the GENSET controllers on the busbar section. If the network set point is only activated for one
GENSET controller, that controller tries to take the whole load.
12.3.4 Shore connection breaker blackout close flowchart
The Blackout close function sets the action that the controller allows when a dead busbar is detected. An operator or a remote input
can close the breaker even though there is a blackout (if the parameter is not Off).

DANGER!
Incorrect blackout close settings

Blackout conditions
is fixed.

If any of the following conditions are present, the controller will not start the blackout close:

◦ A digital input with the function Breakers > Shore connection breaker > Feedback > SCB short circuit
was activated.
• The ship busbar and/or shore busbar AC measurements are not OK.
◦ A measurement failure is detected on one or more of the phases of the busbar.
• The parameter Busbar > AC setup > Blackout detection > Blackout delay timer has not expired.
Blackout close parameters

Breakers > Shore breaker configuration
Off: The controller will never activate the close breaker relay if any blackout is
detected.
• Off Shore busbar is dead, ship busbar OK: If a blackout is detected at the shore
busbar, but the ship busbar is stable, then the controller allows the breaker to
• Shore busbar is
close.
dead, ship busbar
OK
Shore busbar OK, ship busbar is dead: If a blackout is detected at the ship
Blackout • Shore busbar OK,
Off busbar and the shore busbar is stable, then the controller allows the breaker to
close ship busbar is
close.
dead
• One busbar is
One busbar is alive: If a blackout is detected at the shore busbar or the ship
alive
busbar, and the live busbar is stable, then the controller allows the breaker to
• On close.
On: If a blackout is detected at the shore busbar and/or at the ship busbar, then
the controller allows the breaker to close.

Breaker close
command
Breaker close
Blackout
No flowchart
Yes
Check Blackout
close parameter
Parameter: Parameter:
Shore busbar is Shore busbar Parameter: One
Parameter: Off Parameter: On
dead, ship OK, ship busbar busbar is alive
busbar OK is dead
Only Only Only

Info message shore busbar ship busbar one live
No No No
is dead is dead busbar
Info message
Activate close
breaker relay
Breaker
closed? No
Yes Alarm
SCB closed
3. Check Blackout close parameter:
b. Shore busbar is dead, ship busbar OK: The controller checks whether the blackout was detected only at the shore busbar.
• Blackout only at the shore busbar: The controller activates the close breaker relay.
• Blackout was only at the ship busbar or on both sides of the breaker: The controller shows an info message, and the
sequence ends.
c. Shore busbar OK, ship busbar is dead: The controller checks whether the blackout was detected only at the ship busbar.
• Blackout only at the ship busbar: The controller activates the close breaker relay.
• Blackout only at the shore busbar or on both sides of the breaker: The controller shows an info message and the
sequence ends.
d. Only one live busbar: The controller checks if the blackout was detected only at the shore busbar, or only at the ship
busbar.
• Blackout only at the shore busbar, or only at the ship busbar: The controller activates the close breaker relay.

4. Breaker closed: The controller checks whether the shore connection breaker has closed.
• If the shore connection breaker has closed, the blackout close sequence has been completed successfully.
• If the shore connection breaker has not closed the controller activates the SCB closing failure alarm.
12.3.5 Shore connection breaker trip flowchart
The controller automatically trips the shore connection breaker (SCB) for this alarm action:
• Trip shore connection breaker
The breaker is not de-loaded for a trip.
Shore connection breaker trip flowchart

Shore 1. Open SCB: When a trip is required, the controller activates the Breakers >
connection Shore connection breaker > Control > SCB open output to open the
breaker trip breaker.
2. SCB opened: The controller checks whether the breaker has opened:
Yes
Open SCB
• If the breaker has not opened, the controller activates the SCB opening failure
alarm.
SCB opened Alarm

No
Yes
SCB tripped
12.4 Other SHORE connection controller functions

12.4.1 Counters

• Shore connection breaker operations and trips
• Active and reactive energy export (to the shore connection)
• Active and reactive energy import (to the ship busbar)
• External breaker operations

Digital outputs

Function I/O Type
Shore connection > Production counters > Active
energy export pulse
Shore connection > Production counters >

Reactive energy export pulse
Shore connection > Production counters > Active

energy import pulse
Shore connection > Production counters >

Reactive energy import pulse
Parameters
Shore connection > Production counters > Active energy export
Shore connection > Production counters > Reactive energy export

Shore connection > Production counters > Active energy import

Shore connection > Production counters > Reactive energy import


12.5 SHORE connection controller protections

12.5.1 SHORE connection controller protections
SC-DG maximum parallel time
SC-SC maximum parallel time

Maximum parallel time
SC-SG maximum parallel time
SC-Hybrid maximum parallel time


• Warning
• Block
• PMS-controlled open breaker
• Trip shore connection breaker
12.5.3 Inhibits
The SHORE connection controller includes the following inhibits:
Shore connection breaker The Breakers > Shore connection breaker > Feedback > SCB closed digital input is
closed activated.
Shore connection breaker The Breakers > Shore connection breaker > Feedback > SCB open digital input is
open activated.
Shore voltage present The shore busbar voltage is above 10% of the nominal voltage.
No shore voltage The shore busbar voltage is below 10% of the nominal voltage.
Shore frequency present The shore busbar frequency is above 10% of the nominal frequency.
No shore frequency The shore busbar frequency is below 10% of the nominal frequency.

Ship-to-ship active
• The shore connection breaker is closed
measurements
More information
The following table shows where to configure these alarms for the SHORE connection controller, as well as which general alarm
corresponds to each SHORE connection controller alarm.
Table 12.2 Breaker alarm names for the SHORE connection controller
SHORE connection alarm Parameters General name

Breakers > Shore breaker monitoring >
SCB synchronisation failure Breaker synchronisation failure
Breakers > Shore breaker monitoring > De-load

SCB de-load failure Breaker de-load failure
failure
Breakers > Shore breaker monitoring > Vector

mismatch
Breakers > Shore breaker monitoringr > Opening

SCB opening failure Breaker opening failure
failure
Breakers > Shore breaker monitoring > Closing

SCB closing failure Breaker closing failure
failure
Breakers > Shore breaker monitoring > Position

SCB position failure Breaker position failure
failure
Breakers > Shore breaker monitoring > Tripped

SCB trip (external) Breaker trip (external)
(external)
Breakers > Shore breaker monitoring > Short

SCB short circuit Breaker short circuit
circuit
SCB configuration failure - Breaker configuration failure

Shore connection > AC setup > Phase sequence
Shore phase sequence error Phase sequence error
error
12.5.5 AC alarms
More information
See AC configuration and nominal settings for a description of AC alarms in general.

The following tables show where to configure these alarms for the SHORE connection controller, as well as which general alarm
corresponds to each SHORE connection controller alarm.
Table 12.3 AC alarm names for the SHORE connection controller

Shore connection > Voltage protections > Over-
Shore connection over-voltage 1 Over-voltage
voltage 1
Shore connection > Voltage protections > Over-

Shore connection over-voltage 2 Over-voltage
voltage 2
Shore connection > Voltage protections > Under-

Shore connection under-voltage 1 Under-voltage
voltage 1
Shore connection > Voltage protections > Under-

Shore connection under-voltage 2 Under-voltage
voltage 2
Shore connection voltage Shore connection > Voltage protections >

Voltage unbalance
unbalance Voltage unbalance
Shore connection > Current protections > Over-

Shore connection over-current 1 Over-current
current 1
Shore connection > Current protections > Over-

Shore connection over-current 2 Over-current
current 2
Shore connection > Current protections > Fast

over-current 1
Shore connection > Current protections > Fast

over-current 1
Shore connection > Current protections > Current unbalance

Current unbalance (average calc.) (average calc.)
Shore connection > Current protections > Current unbalance
Current unbalance (nominal calc.) (nominal calc.)
Shore connection > Current protections >
Inverse time over-current
Shore connection > Frequency protections >

Shore connection over-frequency 1 Over-frequency
Over-frequency 1
Shore connection > Frequency protections >

Shore connection over-frequency 2 Over-frequency
Over-frequency 2
Shore connection under-frequency Shore connection > Frequency protections >

Under-frequency
1 Under-frequency 1
Shore connection under-frequency Shore connection > Frequency protections >

Under-frequency
2 Under-frequency 1
Shore connection > Power protections > Overload

Overload 1 Overload
1
Shore connection > Power protections > Overload

Overload 2 Overload
2
Shore connection > Power protections > Reverse

Reverse power 1 Reverse power
power 1
Shore connection > Power protections > Reverse

Reverse power 2 Reverse power
power 2
Shore connection > Reactive power protections >




Table 12.4 Busbar AC alarm names for the SHORE connection controller

13. BUS TIE breaker controller
13.1 About the BUS TIE breaker controller

Each BUS TIE breaker controller controls one bus tie breaker.
There is no restriction on the number of BUS TIE breaker controllers. There can be a ring busbar connection.
Example application
13.1.1 BUS TIE breaker controller functions
Functions
Synchronisation and de- • Broadcast the set point for GENSET controllers
loading ◦ In the busbar A section, and in the busbar B section

◦ Bus tie breaker operations and trips
◦ Energy export (active and reactive) (to busbar B)
◦ Energy import (active and reactive) (to busbar A)
◦ Energy differential (active and reactive)
Counters
◦ Energy export (active and reactive) (to busbar B)
◦ Energy import (active and reactive) (to busbar A)
◦ Energy differential (active and reactive)
13.2 BUS TIE breaker controller principles

13.2.1 Configure a BUS TIE breaker controller
Configure each BUS TIE breaker controller on the application single-line diagram with PICUS.
The BUS TIE breaker controller measures the current and voltage on busbar A. The BUS TIE breaker controller also measures the
voltage on busbar B. Busbar A for one BUS TIE breaker controller can be busbar B for the next BUS TIE breaker controller.

Each BUS TIE breaker controller and each externally controlled breaker creates a new busbar section.
More information
See Busbar sections and load sharing for more information about busbar sections.
Busbar A nominal settings

Busbar A > Nominal settings > Nominal settings # *
Voltage (V) 10 V to 160 kV 400 V The phase-to-phase ** nominal AC voltage for busbar A.
The maximum current flow in one phase (that is, L1, L2 or L3) in busbar A
during normal operation.

The nominal active power for the bus tie breaker. Ignored if P nominal
Power (P) 1 kW to 900 MW 480 kW
calculated is selected.
The nominal apparent power for the bus tie breaker. Ignored if S nominal
Apparent power (S) 1 kVA to 1 GVA 530 kVA
calculated is selected.
Power factor (PF) 0.6 to 1 0.9 The nominal power factor at the bus tie breaker.
Busbar A > Nominal settings > Nominal settings # > Calculation method *
No calculation
More information
See Nominal power calculations for more information.
Busbar B nominal settings

Busbar B > Nominal settings > Nominal settings # *
The phase-to-phase nominal voltage for busbar B. If there is no transformer between

Voltage (V) 10 V to 160 kV 400 V busbar A and busbar B, the nominal voltage for busbar B is the same as the nominal
voltage for busbar A.
The system nominal frequency, typically either 50 Hz or 60 Hz. All the controllers in
the system should have the same nominal frequency.

13.3 BUS TIE breaker controller sequences

13.3.1 Bus tie breaker close flowchart
This is the sequence that the controller normally uses to close the bus tie breaker.
More information
See Bus tie breaker blackout close flowchart for how to allow the bus tie breaker connect to a dead busbar.

Table 13.1 Bus tie breaker (BTB) close flowchart
BTB close
command
2. BTB open: The controller checks whether the breaker is open. If the breaker
Command 3. Busbar A V&Hz OK: The controller checks whether the voltage and
and mode Info message frequency from busbar A are within the allowed range*. If these are not in the
No
match range, then the controller cancels the close command and displays an info
Yes message.
4. Busbar B V&Hz OK: The controller checks whether the voltage and
frequency on busbar B are within range *. If these are not in the range, then
BTB open Info message the controller cancels the close command and displays an info message.
No
5. Broadcast set point to busbars A & B sections: The controller broadcasts
Yes the required set points on the busbar A section and the busbar B section. The
GENSET controller(s) that have external network set point activated then use
these set points for regulation.
Busbar A
V&Hz Info message • If busbar A and busbar B are synchronised, the controller activates the
No
OK Breakers > Bus tie breaker > Control > BTB close output to close the
Yes breaker.
• If the busbars do not synchronise within the time allowed, the controller
activates a BTB synchronisation failure alarm.
Busbar B Info message 6. BTB closed: The controller checks whether the breaker has closed.
V&Hz OK No
• If the breaker has closed, the breaker close sequence has been
Yes completed successfully.
• If the breaker has not closed, the controller activates the BTB closing
Broadcast set failure alarm.
point to busbars
A and B
sections

No expired No
Yes Yes
Alarm
Close BTB
BTB closed Alarm

No
Yes
BTB closed
NOTE * See parameters: [Source] / [Busbar] > AC setup > Voltage and frequency OK for these ranges.
13.3.2 Bus tie breaker open flowchart
The following flowchart shows the sequence that the controller normally uses to open the bus tie breaker.
operator sends a BTB open command while Block is active, the controller uses this sequence.

The sequence to trip the bus tie breaker is described in another flowchart.
this command.
Table 13.2 Bus tie breaker (BTB) open flowchart

BTB open
command
match.
2. BTB closed: The controller checks whether the breaker
Command
and mode Info message 3. Broadcast set point to busbars A and B sections:
No
match The controller broadcasts the required set points on the
Yes busbar sections. The GENSET controllers that have
external network set point activated then use these set
points for regulation.
BTB
Info message • When the load is less than the set point for the
closed No
breaker to open, the controller activates the
Yes Breakers > Bus tie breaker > Control >
BTB open output.
Broadcast set
point to busbars the de-load timer expires, the controller activates the
A and B BTB de-load failure alarm. The controller continues
sections to try to de-load the breaker.
4. BTB opened: The controller checks whether the
breaker has opened:
Deload • If the breaker has opened, the bus tie breaker open
Load < open timer
No sequence has been completed successfully.
Yes
Yes activates the BTB opening failure alarm.
Yes Alarm
Open BTB
BTB opened Alarm

No
Yes
BTB opened
CAUTION
Possible blackout
Opening the bus tie breaker may cause a blackout.
Activate set point for all the connected GENSET controllers on both busbar sections. If the network set point is only activated for one
GENSET controller, that controller tries to regulate to de-load the bus tie breaker, which may cause a trip.

13.3.3 Bus tie breaker blackout close flowchart
The Blackout close function sets the action that the controller allows when a dead busbar is detected. An operator or a remote input
can close the breaker even though there is a blackout (if the parameter is not OFF).
DANGER!
Incorrect blackout parameter settings

Blackout conditions
is fixed.


◦ A digital input with the function Breakers > Bus tie breaker > Feedback > BTB short circuit was activated.
• The busbar A and/or busbar B AC measurements are not OK.
• The Busbar B > AC setup > Blackout detection > Blackout delay timer has not expired.
Parameters
Breakers > Bus tie breaker configuration
Off: The breaker is not allowed to close, unless both busbars are live and
synchronised.
• Off Busbar A is dead, busbar B OK: If a blackout is detected on busbar A, but

busbar B is stable, then the controller allows the breaker to close.
• Busbar A is dead,
busbar B OK
Blackout Busbar A OK, busbar B is dead: If a blackout is detected on busbar B and
• Busbar A OK, Off
close busbar A is stable, then the controller allows the breaker to close.
busbar B is dead
• One busbar is alive
One busbar is alive: If a blackout is detected on busbar A or busbar B, and the
• On live busbar is stable, then the controller allows the breaker to close.
On: If a blackout is detected on busbar A and/or busbar B, then the controller

allows the breaker to close.

Breaker close
command
Breaker close
Blackout
No flowchart
Yes
Check Blackout
close parameter
Parameter: Parameter:
Busbar A is Busbar A OK, Parameter: One
Parameter: Off Parameter: On
dead, busbar B busbar B is busbar is alive
OK dead
Only Only Only

Info message Busbar A is Busbar B is one live
No No No
dead dead busbar
Info message
Activate close
breaker relay
Breaker
closed? No
Yes Alarm
BTB closed
3. Check Blackout close parameter: The controller checks the Blackout close parameter:
b. Busbar A is dead, busbar B OK: The controller checks whether the blackout was detected only on busbar A.
• Blackout only on busbar A: The controller activates the close breaker relay.
• Blackout was only on busbar B or on both sides of the breaker: The controller shows an info message, and the sequence
ends.
c. Busbar A OK, busbar B is dead: The controller checks whether the blackout was detected only on busbar B.
• Blackout only on busbar B: The controller activates the close breaker relay.
• Blackout only on busbar A or on both sides of the breaker: The controller shows an info message and the sequence ends.
d. One busbar is alive: The controller checks if the blackout was detected only on busbar A, or only on busbar B.
• Blackout only on busbar A, or only on busbar B: The controller activates the close breaker relay.
4. Breaker closed: The controller checks whether the bus tie breaker has closed.

• If the bus tie breaker has closed, the blackout close sequence has been completed successfully.
• If the bus tie breaker has not closed the controller activates the BTB closing failure alarm.
13.3.4 Bus tie breaker trip flowchart
The controller automatically trips the bus tie breaker (BTB) for this alarm action:
• Trip bus tie breaker
The bus tie breaker is not de-loaded for a trip.
Bus tie breaker trip flowchart
1. Open BTB: When a trip is required, the controller activates the Breakers > Bus tie
Bus tie breaker
breaker > Control > BTB open output to open the breaker.
trip
2. BTB opened: The controller checks whether the breaker has opened:
• If the breaker has not opened, the controller activates the BTB opening failure
Open BTB alarm.
BTB opened Alarm

No
Yes
BTB tripped
13.4 Other BUS TIE breaker controller functions

13.4.1 Counters
You can view, edit and reset all the counters on the display unit under Configure > Counters. The counters include:
• Bus tie breaker operations and trips
• Active and reactive energy export (to busbar B)
• Active and reactive energy import (to busbar A)
• Active and reactive energy differential (the difference between the energy export and import)
• External breaker operations

Configure the digital outputs under Busbar A > Production counters > [Counter pulse].
Parameters
Busbar A > Production counters > Active energy export

Busbar A > Production counters > Reactive energy export
Busbar A > Production counters > Active energy import

Busbar A > Production counters > Reactive energy import

Busbar A > Production counters > Active energy differential

Busbar A > Production counters > Reactive energy differential

Active energy differential pulse 1 Active energy differential
Reactive energy differential pulse 1 Reactive energy differential


13.5 BUS TIE breaker controller alarms and protections

13.5.1 BUS TIE breaker controller protections
All the BUS TIE breaker controller alarms are included in the AC protections and general alarms for PPU 300 controllers.

• Warning
• Block bus tie breaker
• Trip bus tie breaker
13.5.3 Inhibits
Controller under The Mode > Switchboard control digital input is activated, OR a system problem forced the
SWBD control controller under switchboard control.
• The bus tie breaker is closed
measurements
Breaker alarm names for the BUS TIE breaker controller
BUS TIE breaker alarm Parameter General name

Breakers > Bus tie breaker monitoring >
BTB synchronisation failure Breaker synchronisation failure
Breakers > Bus tie breaker monitoring > De-

BTB de-load failure Breaker de-load failure
load failure
Breakers > Bus tie breaker monitoring > Vector

mismatch

BTB opening failure Breaker opening failure
Opening failure

BTB closing failure Breaker closing failure
Closing failure

BTB position failure Breaker position failure
Position failure

BTB trip (external) Breaker trip (external)
Tripped (external)

BUS TIE breaker alarm Parameter General name
Breakers > Bus tie breaker monitoring > Short
BTB short circuit Breaker short circuit
circuit
BTB configuration failure - Breaker configuration failure
Busbar A phase sequence error Busbar A > AC setup > Phase sequence error Phase sequence error
Busbar B phase sequence error Busbar B > AC setup > Phase sequence error Phase sequence error
More information
13.5.5 AC alarms
Busbar A AC alarms for the BUS TIE breaker controller
BUS TIE breaker alarm Parameters General name

Busbar A over-voltage 1 Busbar A > Voltage protections > Over-voltage 1
Over-voltage
Busbar A over-voltage 2 Busbar A > Voltage protections > Over-voltage 2
Busbar A under-voltage 1 Busbar A > Voltage protections > Under-voltage 1

Under-voltage
Busbar A under-voltage 2 Busbar A > Voltage protections > Under-voltage 2
Busbar A > Voltage protections > Voltage

Busbar A voltage unbalance Voltage unbalance
unbalance
Busbar A > Voltage protections > Negative Negative sequence

Negative sequence voltage
sequence voltage voltage
Busbar A > Voltage protections > Zero sequence Zero sequence
Zero sequence voltage
voltage voltage
Busbar A over-current 1 Busbar A > Current protections > Over-current 1
Over-current
Busbar A over-current 2 Busbar A > Current protections > Over-current 2
Busbar A > Current protections > Fast over-

Fast over-current 1 current 1
Fast over-current
Fast over-current 2 Busbar A > Current protections > Fast over-
current 2
Current unbalance (average Busbar A > Current protections > Current Current unbalance
calc.) unbalance (average calc.) (average calc.)
Current unbalance (nominal Busbar A > Current protections > Current Current unbalance
calc.) unbalance (nominal calc.) (nominal calc.)
Busbar A > Current protections > Directional
over-current 1
Directional over-current 1 Busbar A > Current protections > Directional
Directional over-current 2 over-current 2 Directional over-
Directional over-current 3 Busbar A > Current protections > Directional current
Directional over-current 4 over-current 3
Busbar A > Current protections > Directional
over-current 4
Busbar A > Current protections > Inverse time Inverse time over-
Inverse time over-current
over-current current
Busbar A > Current protections > Negative Negative sequence
Negative sequence current
sequence current current
Busbar A > Current protections > Zero sequence Zero sequence
Zero sequence current
current current

BUS TIE breaker alarm Parameters General name
Busbar A > Frequency protections > Over-
Busbar A over-frequency 1 frequency 1
Over-frequency
Busbar A over-frequency 2 Busbar A > Frequency protections > Over-
frequency 2
Busbar A > Frequency protections > Under-

Busbar A under-frequency 1 frequency 1
Under-frequency
Busbar A under-frequency 2 Busbar A > Frequency protections > Under-
frequency 2
Busbar A > Reactive power protections > Reactive

Reactive power export 1 power export 1 Reactive power
Reactive power export 2 Busbar A > Reactive power protections > Reactive export
power export 2
Busbar A > Reactive power protections > Reactive

Reactive power import 1 power import 1 Reactive power
Reactive power import 2 Busbar A > Reactive power protections > Reactive import
power import 2
Busbar B AC alarm names for the BUS TIE breaker controller
BUS TIE breaker alarm Configure > Parameters > General name
Busbar B over-voltage 1 Busbar B > Voltage protections > Over-voltage 1
Busbar over-voltage
Busbar B over-voltage 2 Busbar B > Voltage protections > Over-voltage 2
Busbar B under-voltage 1 Busbar B > Voltage protections > Under-voltage 1

Busbar under-voltage
Busbar B under-voltage 2 Busbar B > Voltage protections > Under-voltage 2
Busbar voltage
Busbar B voltage unbalance Busbar B > Voltage protections > Voltage unbalance
unbalance
Busbar B > Frequency protections > Over-frequency
Busbar B over-frequency 1 1 Busbar over-
Busbar B over-frequency 2 Busbar B > Frequency protections > Over-frequency frequency
2
Busbar B > Frequency protections > Under-frequency

Busbar B under-frequency 1 1 Busbar under-
Busbar B under-frequency 2 Busbar B > Frequency protections > Under-frequency frequency
2
More information
See AC configuration and nominal settings for general information about the AC alarms.

14. Modbus
14.1 Modbus in the controller

14.1.1 How it works
Modbus is generally accepted as a standard communication protocol between intelligent industrial devices. This means that the
Modbus protocol is used as a standard method to represent and communicate data in intelligent industrial devices.
The controller includes a built-in Modbus TCP/IP slave. The Modbus TCP/IP slave allows external devices to communicate with the
controller using the Modbus TCP/IP communication protocol. For example:
• A PLC can request that specific data is read from the controller, such as the settings for the nominal AC configuration.
• A PLC can send commands to the controller using the Modbus TCP/IP protocol.
This document will only describe the information required to communicate with the controller using the Modbus TCP/IP protocol. For
more information about Modbus in general and the Modbus TCP/IP protocol, refer to the documentation freely available at http://
www.modbus.org.
Refer to the Modbus tables, available for download at www.deif.com, to see how the controller data is mapped to the Modbus
addresses.
NOTE All values in this chapter are decimal values, unless specifically stated that a value is hexadecimal.
14.1.2 Warnings
DANGER!
Access to controller settings with Modbus TCP

All controller settings can be accessed and modified through Modbus TCP.
This includes disabling critical controller protections by changing settings and alarms. Use the Modbus tables provided
by DEIF to ensure that you do not disable critical protections.
NOTICE
Cyber security
The DEIF controllers do not include a firewall or other Internet security measures.
It is the customer's own responsibility to protect the network. The controller provides no access restrictions (for example
group and user permissions) when accessed through Modbus TCP. If the controllers are connected to a network
connection outside of the controller network, the controller can be accessed and configured through Modbus TCP by
anyone connected to the network.
14.2 Modbus implementation in the controller

14.2.1 Modbus TCP protocol
The controller uses the Modbus TCP protocol to communicate with an external device over the Modbus network and through the
internet. The communication protocol uses static IPv4 addresses to send information. Dynamic IPv4 addresses (created by a
dynamic host configuration protocol server (DHCP server)) and IPv6 addresses are not supported by the controller for Modbus
communication purposes.

More information
See the Operator's manual or the PICUS manual for how to configure the controller communication settings.
14.2.2 Modbus communication port
By default the controller uses port 502 (standard for Modbus TCP protocol) for TCP communication. Create a custom Modbus server
to use a different communication port.
Each controller can process up to 10 communication requests at a single time.
14.2.3 Controller identifier
The Modbus TCP protocol will always use the controller IPv4 address to identify the controller that the master wants to communicate
with. However, some Modbus communication tools will still require/automatically add a Modbus Slave ID, also known as a unit
identifier, for the unit that the server is communicating with. For these cases the controller accepts Modbus Slave IDs from 1 to 247.
This is the case for all ML 300 controllers in the network that communicate using the Modbus TCP protocol.
If two Modbus servers are enabled at the same time that use the same communication port, then a unique Modbus Slave ID must
be configured for each server.
Specific controller identifiers can be selected for the controller when you configure a custom server.
14.2.4 Data handling
NOTICE
Check Modbus protocol address information

Check the Modbus protocol address information using PICUS to ensure that you are referencing the correct Modbus
address for the function that you are executing.
NOTE Always document and store changes that you make to the way that the controller interprets Modbus data.
Data format (endian)
To ensure that the correct data is retrieved from the controller, the request from the Modbus master must match the data format of
the selected address. The data format is configured in the Modbus server, and are applied to the Holding register and the Input
register.
Sign
In general, the integer data (16-bit and 32-bit) that is accessed from the controller through Modbus TCP are signed integer values.
Conversion
Data in the Holding register and Input register of the Modbus table is converted according to the conversion template selected for
that address. When data is read using Modbus, then the Formula is used to convert the Modbus data. When data is written using
Modbus, then the Reverse formula is used to convert the data into a form that can be stored in the Modbus protocol.
Conversions can also be used to force unit conversions on specific addresses.

NOTE Reverse formulas are NOT automatically determined.
Modbus data conversion example
The parameter nominal power factor is assigned to an unused address in a custom Modbus protocol. The controller can
process inputs to the forth decimal value (for example, 0.8002) for the nominal power factor. To read and write values
correctly using Modbus a conversion template X * 10000 is assigned to the address. The Formula equal to x*10000 and a
Reverse formula equal to x*0.0001.

This means that when a value of 0.8002 is read from the controller, the displayed value is:
Result = Formula => Result = x * 10000 => Result = 0.8002 * 10000 => Result = 8002
To write a value of 0.85 to the controller using Modbus, the value that should be written to the controller is:
Result = Reverse formula => Result = x * 0.0001 => 0.85 = x * 0.0001 => x = 8500
Refresh rate
Data stored in the Modbus addresses is refreshed at the following maximum rates:
Data Maximum refresh rate Function group example
AC measurements 20 ms [Source] ACM measurements
Values 40 ms Alarm parameter: Enable
14.3 Modbus tables

14.3.1 Download Modbus tables
To download the Modbus tables, follow these steps:
1. Visit the DEIF website at: www.deif.com for your product:

• PPU 300: https://www.deif.com/documentation/ppu-300/
2. Under the section Reference, select Communication
3. Select the Modbus tables to start the download.
14.3.2 About the Modbus tables

®
The Modbus tables are stored in a Microsoft Excel file that contains five spreadsheets with Modbus data. The table below gives a
short description of each of the spreadsheets in the file.
Spreadsheet name Description
This spreadsheet contains an overview of the other four spreadsheets. The information includes a
Descriptions
description of each function group listed in the tables spreadsheets.
You can read or write information to the addresses that are listed in this spreadsheet. Use Modbus function
Discrete output coil code 01 to read whether a coil is on or off. Use Modbus function code 05 or 15 to toggle the coil value.
Read-only addresses will return a 0 value if you try to write to them.
Discrete input You can only read information from the addresses that are listed in this spreadsheet. Use Modbus function
contact code 02 to read whether the contact is on or off.
You can read or write information to the addresses that are listed in this spreadsheet. Use Modbus function
Output holding code 03 to read the information stored at the requested Modbus address(es). Use Modbus function code 06
register or 16 to write information to the Modbus address(es). Read-only addresses will return a 0 value if you try to
write to them.
You can only read information from the addresses that are listed in this spreadsheet. Use Modbus function
Input register
code 04 to read the information stored at the requested Modbus address(es).
This spreadsheet contains an overview of texts associated to Modbus output values. This association is
Controller text
only available for selected Modbus addresses.

14.4 Specific Modbus function groups
14.4.1 CustomLogic: Modbus signal
You can find the function group CustomLogic: Modbus signal in the Discrete output coil (01; 05; 15) and the Discrete input contact
(02) sheets of the Modbus table. The function group allows you to interact with the CustomLogic of the controller using Modbus.
When you read a value from these addresses, the controller will return a value to show if the flag for the signal is active (true, 1) or
not active (false, 0). When you write a value to the addresses in the Discrete output coil, the value stored in the address changes to
the new value.
NOTE You cannot write values to Modbus signals that have been assigned to coils in CustomLogic.
More information
See CustomLogic in the PICUS manual for how to assign a Modbus signal to CustomLogic elements.
14.4.2 Breaker priority: Buffered value
How it works
You can find the function group Breaker priority: Buffered value in the Holding register of the Modbus table. The function group acts
as a temporary storage area for the breaker priority values that will be written to the controller using the function group Breaker
priority: Write values.
When you read a value from these addresses, the breaker priority that you want to assign to the breaker that is stored in the
address is returned to you. When you write a value to these addresses, the value is stored and ready to be written to the controller
when you activate Breaker priority: Write values.
CAUTION
Breaker priorities and the Modbus addresses

The breaker priorities and the Modbus address associated to a specific breaker is dependent on the application single-
line configuration. If you change the application single-line configuration, you will change the associated Modbus
addresses. If you add or remove GENSET controllers from the application single-line configuration, the breaker
priorities can change.
Breaker priority allocation

These rules apply when breaker priorities are assigned:
• Only GENSET controllers receive a breaker priority value that is greater than zero (0).
• All other controller types receive a breaker value of zero (0).
• An EMERGENCY genset controller uses two Modbus addresses, the first for the tie breaker and the second for the generator
breaker. Both breakers have a breaker priority of zero (0).
• Breaker priorities are assigned to the first available breaker priority, according to the order in which controllers are added to the
application single-line diagram.
• Breaker priority Modbus addresses are assigned to the first available breaker priority Modbus address, according to the order in
which controllers are added to the application single-line diagram.

Example of how breaker priority works
BTB
Busbar A Busbar B
GB1 SCB SGB GB2 TB
Emergency
load
G G G
SHORE GB3
Genset 1 connection Genset 2
Genset 3
In this example, it is assumed that the application single-line diagram was drawn by placing the components in the diagram in the
following order:
1. Genset 1
2. Shore connection
3. Bus tie breaker
4. Shaft generator
5. Genset 2
6. Emergency genset
This means that the breakers were assigned the values and priorities:
Modbus address (Holding Breaker priority: Buffered

Component Breaker priority: Value
register and input register) value
Genset 1 14001 0 1
Shore connection 14002 0 0
Bus tie breaker 14003 0 0
Shaft generator 14004 0 0
Genset 2 14005 0 2
14006 0 0
Emergency genset
14007 0 0
The Modbus addresses are assigned to the breaker for the controller. This means an emergency genset always uses two Modbus
addresses for breaker priority, one for each breaker. The Modbus addresses are assigned to the components in the order that they
were inserted into the application single-line diagram. The Modbus address(es) assigned to a component will not change when the
controller ID changes.
Only genset breakers will be assigned a breaker priority value that is between 1 and 128. All other components and addresses
which are unassigned (for example 14008 in the example above) have a breaker priority value of 0. Both the breakers for an
emergency genset always have a breaker priority of 0. Breakers with a breaker priority of 0 assigned to them, cannot be changed.
If a component is removed from the application single-line diagram, the Modbus address becomes free and can be reassigned. The
breaker priorities are automatically reassigned for all the remaining components in the application single-line diagram. For example
if we remove Genset 1 and the emergency genset from the example above the table will look as follows:

Updated breaker priority values and Modbus addresses after removing components
- 14001 0 0
Genset 2 14005 0 1
- 14006 0 0
- 14007 0 0
If we add the emergency genset to the application single-line diagram and then add Genset 1, the table will look as follows:
Updated breaker priority values and Modbus addresses after adding components
Emergency genset (TB) 14001 0 0
Genset 2 14005 0 1
Emergency genset (GB3) 14006 0 0
Genset 1 14007 0 2
The table above shows that the breakers are assigned the first open Modbus address in the Modbus table. This means that it is
possible for an emergency genset to have its breakers assigned to Modbus addresses that do not follow directly on one another.
Because Genset 1 has a higher Modbus address (14007) than Genset 2 (14005), by default it is assigned a lower priority than
Genset 2 after the change was made in the application single-line diagram.
When you want to change the breaker priorities by using Modbus, write the desired priority value to the Modbus address in the
function group Breaker priority: Buffered value. When you are satisfied with the breaker priorities, activate Breaker priorities: Write
values to write the values to the controller. Only values between 1 and 128 are accepted inputs for breaker priorities. Breakers that
already have a priority of 0 assigned to them, cannot be changed. You cannot write the breaker priorities to the controller if there are
duplicate non-zero entries in Breaker priority: Buffered value. The tables below show the results after new breaker priorities were
written to the buffered values, and after the buffered values were written to the controller.
Breaker priority values after writing new values to the buffer addresses
Genset 2 14005 2 1
Genset 1 14007 1 2

Breaker priority values after writing the buffered values to the controller
Genset 2 14005 2 2
Genset 1 14007 1 1
14.5 Setting up Modbus

14.5.1 Setting up Modbus TCP/IP communication
In order to communicate with a controller through Modbus TCP, the following conditions must be met:
• The device interfacing with the controller must be connected to one of the following:
◦ An Ethernet connection on the controller communication module (that is, PCM3.1).
◦ Another controller in the DEIF network.
• The controller must have a unique IPv4 address which is active.
• Modbus TCP communication software must be installed on the device communicating with the controller.
More information
See Wiring the communication in the Installation instructions for more information about how to wire the Ethernet
connection to the controller.
14.6 Modbus alarm

14.6.1 Modbus communication timeout
The controller activates this alarm if there are no Modbus requests within the delay time.
Communication > Modbus > Modbus communication timeout

Delay 0.1 s to 1 h 10 s
Action Warning

15. Hardware characteristics
15.1 General characteristics

Some terminal types are common to a number of different hardware modules.
The descriptions may include references to hardware modules that are not supported by the controller type. The supported
hardware modules are listed in the Data sheet.
Technical specifications
More information
See the Data sheet for technical specifications for the hardware modules and terminals.
15.1.1 Frame ground characteristics
Symbol Hardware modules
PSM3.1
PSM3.2
EIM3.1
GAM3.2
DU 300
The frame ground is required by classification societies. Among other things, it makes the equipment more robust, for example
against lightning.
CAUTION
Frame ground
The frame ground is connected to the power supply terminals through transient voltage suppression diodes (commonly
known as transorbs).
To protect the frame ground and power supply, no more than 36 V is allowed between the frame ground and the power
supply terminals.
15.1.2 Power supply characteristics
PSM3.1
PSM3.2
EIM3.1
GAM3.2
DU 300
The power supply is connected to these terminals.

CAUTION
Frame ground
The frame ground is connected to the power supply terminals through transient voltage suppression diodes (commonly
known as transorbs).
In order to protect the frame ground and power supply, no more than 36 V allowed across the frame ground and the
power supply terminals.
Backup power
The DEIF equipment does not contain a backup power supply. The power supply source must therefore include the power backup
needed.
Start current
When the power supply is connected, the start current may briefly exceed the current that corresponds to the maximum power on
the data sheet.
Battery-powered systems normally do not have a problem with start current.
For other types of power supply, for example, an AC-to-DC supply, the start current may be a problem. The minimum rating for the
power supply current limiter is therefore included on the data sheet.
Reverse polarity
The power supply is protected against reverse polarity. That is, if the power supply terminals are switched, the DEIF equipment will
not be damaged. However, the DEIF equipment will not be able to operate until the power supply has been connected correctly.
Diode compensation
Diode compensation is available in PSM3.1, PSM3.2, EIM3.1 and GAM3.2.
Hardware > [PSM3.1 1, PSM3.2 1, EIM3.1 1 or GAM3.2 1] > Diode compensation

This corrects the power supply measurement values used for the supply voltage alarms.
Diode offset 0 to 1 V DC 0 V DC
Use this to compensate for a small decrease in voltage over the diode.

Figure 15.1 Example of a voltage decrease over a diode
Supply 2 24 V DC
Supply 1 24 V DC
F1 F2
∆V = 0.7 V
+
23.3 V
-
0V
0 V DC
0 V DC
Heat emission
For the heat emission from the equipment, use the maximum power consumption for the power supply (or power supplies).
15.1.3 Relay output characteristics and configuration
PSM3.1
EIM3.1
GAM3.1
GAM3.2
IOM3.2
DU 300 (terminals 6,7)
IOM3.1
DU 300 (terminals 3,4,5)
The controller can use relay outputs for many purposes. Examples: Activate alarm devices, open and close breakers, and genset
speed and voltage regulation.
Configuration
All relay outputs are configurable, except for PSM3.1 terminals 3,4 (Status OK), GAM3.2 terminals 14,15 (GAM3.2 1 Status OK),
and the DU 300 relays. A controller can have a number of relay outputs.
You can assign a digital output function or an alarm for a relay output.
You can also create customised digital output functions using CustomLogic, and assign a relay output.
Controller types and single-line diagram

The controller type determines which digital output functions are available.

To see certain digital output functions, you must include the corresponding equipment in the single-line diagram.
Relay state
The relay state (whether it is open or closed) depends on the relay hardware, the coil state and the function (or alarm) state. The
following table shows how these combine to give the relay state.
Table 15.1 Relay state
Hardware Coil configuration Function (or alarm) Relay state

Normally open Normally de-energised Not activated Open
Normally open Normally de-energised Activated Closed
Normally open Normally energised Not activated Closed
Normally open Normally energised Activated Open
Normally closed Normally de-energised Not activated Closed
Normally closed Normally de-energised Activated Open
Normally closed Normally energised Not activated Open
Normally closed Normally energised Activated Closed
The effect of the relay hardware, the coil state and the function (or alarm) state is also shown below under Coil state.
Relay hardware
The relay hardware can be normally open or normally closed. The relay hardware returns to its normal state when the controller has
no power. The relay hardware type is shown on the hardware module faceplate.
Normally open relay hardware:

• All PSM3.1 relays
• IOM3.1 terminals 1,2
• All EIM3.1 relays
• All GAM3.1 relays
• All GAM3.2 relays
Normally closed relay hardware:

Coil state
You can configure the normal coil state in the display unit or PICUS. For input/output terminals, select Normally de-energised (the
default) or Normally energised for the Coil state.

Table 15.2 Relay, normally de-energised coil
NO
(1) Function
1. Function: The digital output function assigned to the terminals. The controller
software activates the function. For example: Breakers > [Breaker] >
(2) Coil
Command > [*B] Close.
2. Coil: The controller energises the relay coil when the function is activated.
3. Normally open circuit: The normally open circuit closes when the coil is
(3) NO circuit
energised.
Table 15.3 Relay, normally energised coil
NO
(1) Function
1. Function: The digital output function assigned to the terminals. The controller
(2) Coil
2. Coil: The controller de-energises the relay coil when the function is activated.
3. Normally open circuit: The normally open circuit opens when the coil is de-
(3) NO circuit
energised.

Table 15.4 Changeover relay, normally de-energised coil
NO NC
(1) Function
(2) Coil 1. Function: The digital output function assigned to the terminals. The controller
(3) NO circuit 2. Coil: The controller energises the relay coil when the function is activated.
3. Normally open circuit: The normally open circuit closes when the coil is
energised.
(4) NC circuit 4. Normally closed circuit: The normally closed circuit opens when the coil is
energised.
Table 15.5 Changeover relay, normally energised coil
NO NC
(1) Function
(2) Coil 1. Function: The digital output function assigned to the terminals. The controller
(3) NO circuit 2. Coil: The controller de-energises the relay coil when the function is activated.
3. Normally open circuit: The normally open circuit opens when the coil is de-
energised.
(4) NC circuit 4. Normally closed circuit: The normally closed circuit closes when the coil is
de-energised.
15.1.4 Digital input characteristics and configuration
IOM3.1
IOM3.2
IOM3.4
EIM3.1
GAM3.2

The controller can use digital inputs for many purposes. Examples: Command buttons, breaker feedback, and alarms.
Polarity
The digital input is a bi-directional input. The wiring to the input and common terminals may be changed around without affecting its
operation.
Each group of digital inputs (that is, each group of digital inputs that share a common terminal) must share the same reference
polarity (high or low). However, different groups of digital input terminals can have different reference polarities.
In general, the controller activates the associated digital input function for a HIGH digital input. However, for the Emergency stop
safety function, the controller activates the digital input function for a LOW digital input.
Configuration
All digital inputs are configurable. A controller can have a number of digital inputs.
For each digital input, you can assign digital input function(s) and/or configure an alarm.
You can also create responses to digital inputs using CustomLogic. You can also activate some digital input functions using a
Modbus command.

The controller type determines which digital input functions are available.
To see certain digital input functions, you must include the corresponding equipment in the single-line diagram.
Controller operation
Some of the digital input functions are only applicable in certain controller modes. If the controller is in another mode, it ignores the
digital input.
15.1.5 Analogue input characteristics and configuration
GAM3.1 (current or voltage inputs)
EIM3.1 (current or resistance inputs)
The controller can use an analogue input to receive operating data. The controller can also activate alarms based on the analogue
input.
Analogue input function

Assigning a function to the analogue input is optional.
You can assign one (or more) of the controller's analogue input functions to the input. You can only select functions that use the
same units.
Alternatively, if you want to use the analogue input as a supervised binary input, you can assign one (or more) of the controller's
digital input functions to the input.
Analogue input sensor setup

The sensor setup is required.
The sensor setup requires a curve. The curve allows the controller to convert the analogue input to the selected function's value.
You can select a previously customised curve, select a pre-configured curve, or customise a curve.

NOTICE
Pt100 or Pt1000
If you choose a Pt100 pre-configured curve, for the sensor output you must select Pt100 ohm.
If you choose a Pt1000 pre-configured curve, for the sensor output you must select Pt1000 ohm.
Sensor failure
You can configure customised alarms for sensor failure. The Below range alarm is activated when the analogue input is below the
specified value. Similarly, the Above range alarm is activated when the analogue input is above the specified value.
NOTICE
Use of sensor failure alarms

Do not use the sensor failure alarms to respond to ordinary operating data. Configure customised analogue input
alarms instead.
Supervised binary input

Analogue inputs used for supervised binary inputs should be configured using the sensor output Dry contact.
Use an analogue input curve to define the supervised binary input. As shown in the examples, for the supervised binary input the
curve is a step function. That is, the curve consists of a horizontal line (with the value 0 or 1), a vertical line (the point where the
curve changes), and another horizontal line (with the value 1 or 0).
If the sensor output corresponds to the change point, the controller uses the last point specified in the curve. For the Supervised
GB short circuit example, if the sensor output is exactly 150 Ω, then the function input is 0.
To avoid instability, configure the curve so that the change point is far away from the input closed and open values.
If the analogue input measurement corresponds to a function input that is not zero, then the controller uses one as the function
input.
Supervised GB short circuit example
The designer creates the following wiring for a GB short circuit digital input:
COM GB short
200 Ω
circuit
50 Ω
When the GB short circuit is open, the circuit has a resistance of around 200 Ω. When the GB short circuit is closed, the
circuit has a resistance of around 40 Ω (the combined resistance of the 50 Ω and 200 Ω resistors in parallel).
If the GB short circuit digital input is activated, the controller activates the GB short circuit alarm.

The designer configures a customised function curve with an output of 1 up to 150 Ω, and an output of 0 above 150 Ω. The
short circuit sensor failure is below 5 Ω. The wire break sensor failure is above 250 Ω.
Supervised Emergency stop example
The designer creates the following wiring for an Emergency stop digital input:
COM Emergency
300 Ω
stop
100 Ω
When the Emergency stop is closed, the circuit has a resistance of around 75 Ω (the combined resistance of the 100 Ω
and 300 Ω resistors in parallel). When the Emergency stop is open, the circuit has a resistance of around 300 Ω.
The Emergency stop function requires that the digital input is normally activated. If the Emergency stop digital input is not
activated, the controller activates the Emergency stop alarm.
The designer therefore configures a customised function curve with an output of 0 up to 200 Ω, and an output of 1 above
200 Ω. The short circuit sensor failure is below 10 Ω. The wire break sensor failure is above 325 Ω.
Analogue input alarms

You must complete the Sensor setup before configuring any analogue input alarms.
You can configure any number of alarms for an analogue input. However, you cannot exceed the maximum number of customised
alarms for the controller.
15.1.6 Analogue output characteristics and configuration
IOM3.2 (PWM)
GAM3.1 (PWM)
GAM3.2 (PWM)
IOM3.2 (current or voltage)

GAM3.1 (current or voltage)
GAM3.2 (current or voltage)
More information
See the Data sheet for the technical specifications for each module terminal and connection.
An analogue output (AO) can be used for regulation (for example, governor regulation or AVR regulation). Alternatively, the AO can
be used to output operating data to provide a reading on a switchboard instrument.
Analogue output function

Assign one function to the analogue output.

Analogue output setup
The output setup is required, and requires a curve. The curve allows the controller to convert the selected function's value to the
analogue output.
You can select a previously customised curve, select a pre-configured curve, or customise a curve.
Output for a switchboard instrument

Output Generator power example
The customer has a 1 MW genset, and wants to display the power from the genset on the switchboard. He uses a DEIF
DQ-96x with a scale from -100 to 1500 kW.
The designer creates the following wiring for a Generator > Power (P) > Generator | Total [kW] analogue
output:
+
-
The designer configures a customised function curve with an output of 4 mA for -100 kW, and 20 mA for 1500 kW.

15.2.1 Power supply voltage as an analogue output
You can configure an analogue output with a function for the power supply voltage. The controller then adjusts the analogue output
to reflect the operating value.
Analogue output
The controller measures the power supply voltage over

Hardware > Power supply >
the power supply terminals. The controller uses the
PSM3.1 1 > PSM3.1 1 supply Analogue output 0 to 60 V DC
configured curve to convert this value to an analogue
voltage [V DC]
output.
Application
An analogue output with the power supply voltage may be wired to a switchboard instrument to help the operator.
15.2.2 Relay output characteristics
The first relay output (terminals 3,4) on PSM3.1 is reserved for the Status OK function. You cannot change the function for this relay.
The two other relay outputs on PSM3.1 are configurable (that is, terminals 5,6 and terminals 7,8 can be assigned any function).
More information
See Relay output characteristics and configuration.

15.2.3 Internal communication
The controllers communicate with their extension units using the Ethernet cables and the internal communication ports (OUT and IN,
marked with a red border on the PSM3.1 and PSM3.2). This is type of communication is referred to as Internal communication.
For communication redundancy, the extension units can be connected in a ring. If there is a disruption or failure, the DEIF
proprietary ring protocol changes the communication path within 100 milliseconds.
The order that the extension units are wired, determines in which order they appear in the software. The controller the extension
units are connected to is always the first unit in the order.
NOTE Extension racks must be powered off when exchanging or re-connecting to another controller. If the extension rack is not
powered off, there could be unintended actions from the rack modules.
Internal communication restrictions
• Up to five extension units can be connected to each other in each network chain or ring.
• Only Network chain or Network ring controller configurations are supported.
◦ Do not connect switches or other non-DEIF network equipment as part of the network chain or ring.
• The Ethernet cables must not be longer than 100 metres, point-to-point.
• The Ethernet cables must meet or exceed the SF/UTP CAT5e specification.
Hardware changes that do not activate a Fieldbus conflict alarm

The controller logs the following hardware changes. However, they do not activate a Fieldbus conflict alarm:
• A hardware module is replaced by the same type of hardware module, in the same position.
• Two of the same type of hardware modules swap position.
• An extension rack is replaced with an extension rack with identical hardware.
Factory settings
The hardware configuration for each controller is created in the factory. If the hardware is changed, the controller activates a
Fieldbus conflict alarm. The controller hardware configuration must be confirmed in PICUS.
When a new extension rack is connected, the controller always activates a Fieldbus conflict alarm. The extension rack hardware
configuration must be confirmed in PICUS.
More information
See EtherCAT connections in the Installation instructions for network topology examples and how you can wire the
connections.

15.3.1 Power supply voltage as an analogue output
You can configure an analogue output with a function for the power supply voltage. The controller then adjusts the analogue output
to reflect the operating value.
Analogue output
The controller measures the power supply voltage over

the power supply terminals. The controller uses the
PSM3.2 1 > PSM3.2 1 supply Analogue output 0 to 60 V DC
configured curve to convert this value to an analogue
voltage [V DC]
output.
Application
An analogue output with the power supply voltage may be wired to a switchboard instrument to help the operator.

The first relay output (terminals 3,4) on PSM3.2 is reserved for the Status OK function. You cannot change the function for this relay.
The two other relay outputs on PSM3.2 are configurable (that is, terminals 5,6 and terminals 7,8 can be assigned any function).
More information

Factory settings
More information
connections.
15.4 Alternating current module ACM3.1

15.4.1 Voltage measurement characteristics
The ACM has two sets of terminals for voltage measurement. The first set of terminals (1 to 4) measures the voltage on the busbar.
The second set of terminals (5 to 8) measures the voltage from the source. The ACM uses these measurements for logging, alarms
and protective functions. For power functions, the second set of voltage measurements (terminals 5 to 7) and the current
measurements (terminals 9 to 14) from the ACM are used together.

For 3-phase systems, you do not have to connect and measure the neutral lines (terminals 4 and 8).
15.4.2 Current measurement characteristics
The ACM measures the current, then uses these measurements for logging, alarms and protective functions. For power functions,
the second set of voltage measurements (terminals 5 to 7) and the current measurements (terminals 9 to 14) from the ACM are
used together.
You do not have to connect and measure the 4th current input (terminals 15,16). You can measure the neutral line, the earth current
or a custom current with the 4th current input.
15.5 Differential current module ACM3.2

15.5.1 Current measurement characteristics
The ACM3.2 has two sets of terminals for current measurement. The first set of terminals (1 to 6) measures the current at the
consumer side of the generator. The second set of terminals (7 to 12) measures the current at the neutral side of the generator. The
ACM3.2 uses these measurements for logging, alarms and protective functions relating to differential current protection in the
system.
15.6 Input/output module IOM3.1

15.6.1 Changeover relay output characteristics
IOM3.1 has 4 groups of changeover relay outputs on terminals 1 to 3, 4 to 5, 7 to 8, 10 to 12.
Normally open relay hardware:

IOM3.1 terminals 1,2
Normally closed relay hardware:

More information
See Relay output characteristics and configuration for standard changeover relay characteristics.
15.6.2 Digital input characteristics
IOM3.1 has 10 digital inputs on terminals 13 to 22, with a common on terminal 23.
More information
See Digital input characteristics and configuration .

IOM3.2 has 4 relay outputs on terminals 1 to 2, 3 to 4, 5 to 6, 7 to 8. Default state for all relay outputs is normally open.
More information
See the IOM3.2 wiring in the Installation instructions for the relay wiring.
More information
See Relay output characteristics and configuration for standard relay output characteristics.
15.7.2 Analogue multifunctional output characteristics
IOM3.2 has 4 analogue multifunctional outputs on terminals 9 to 10, 11 to 12, 13 to 14, 15 to 16. Terminals 9 to 10 and 11 to 12 can
also be used as pulse width modulation (PWM) outputs.
The analogue outputs are active, that is, they have their own power supply, and they must not be connected to an external supply.
Using a configured or selected output curve, the controller converts the operating value to the corresponding current (-25 to 25 mA)
or voltage (-10 to 10 V).
More information
See the IOM3.2 wiring in the Installation instructions for the different wiring possibilities and how to connect these to the
module.
More information
See Analogue output characteristics and configuration for the general characteristics.
Using an analogue output with a switchboard instrument

The analogue output can be connected directly to a 4 to 20 mA switchboard instrument.
IOM3.2 has 4 digital inputs on terminals 17 to 20, with a common on terminal 21.
More information
15.7.4 Analogue multifunctional input characteristics
IOM3.2 has 4 analogue multifunctional inputs on terminals 22 to 23, 24 to 25, 26 to 27, 28 to 29.
The I/O configuration determines whether the input is current or resistance. For resistance, the I/O configuration also determines the
type of resistance input. Using a configured or selected input curve, the controller converts the input to a corresponding value. You
can also configure the input to activate functions and/or alarms.

NOTICE
BEFORE connecting external transmitter

Configure the terminals correctly (that is, for current or for voltage) before connecting the external transmitter.
More information
module.
More information
See Analogue input characteristics and configuration for general analogue input characteristics.

15.8.1 Analogue multifunctional input characteristics
IOM3.3 has 10 analogue multifunctional inputs on terminals 1 to 3, 4 to 6, 7 to 9, 10 to 12, 13 to 15, 16 to 18, 19 to 21, 22 to 24, 25
to 27, and 28 to 30.
The I/O configuration determines whether the input is current or resistance. For resistance, the I/O configuration also determines the
type of resistance input. Using a configured or selected input curve, the controller converts the input to a corresponding value. You
can also configure the input to activate functions and/or alarms.
NOTICE
BEFORE connecting external transmitter

Configure the terminals correctly (that is, for current or for voltage) before connecting the external transmitter.
More information
module.
More information
See Analogue input characteristics and configuration for general analogue input characteristics.

15.9.1 Digital output characteristics and configuration
IOM3.4
The controller can use transistor outputs for many purposes. Examples: Activate alarm devices, open and close breakers, and
genset speed and voltage regulation.
Configuration
All transistor outputs are configurable. You can assign a digital output function, or configure one alarm, for a transistor output.
You can program customised transistor output functions using CustomLogic.
You can also create customised digital output functions using CustomLogic, and assign a transistor output.

The controller type determines which digital output functions are available.
To see certain digital output functions, you must include the corresponding equipment in the single-line diagram.
Transistor state
The transistor hardware itself is normally open. The transistor output state (whether it is open or closed) depends on the
configuration in software and the function (or alarm) state. The following table shows how these combine to give the transistor state.
Configuration in software Function (or alarm) Transistor state

Normally de-energised Not activated Open
Normally de-energised Activated Closed
Normally energised Not activated Closed
Normally energised Activated Open
Configured state
You can configure the normal transistor state in software in the display unit or PICUS. For the terminals, select Normally de-
energised (the default) or Normally energised for the Coil state.
Table 15.6 Transistor, configured in software as normally de-energised
Normally
de-energised
NO
(1) Function 1. Function: The digital output function assigned to the terminals. The
controller software activates the function. For example: Breakers >
[Breaker] > Command > [*B] Close.
2. Transistor: The controller closes the transistor when the function is
(2) Transistor
activated.
Table 15.7 Transistor, configured in software as normally energised
Normally
energised
NO
(1) Function 1. Function: The digital output function assigned to the terminals. The
controller software activates the function. For example: Breakers >
[Breaker] > Command > [*B] Close.
2. Transistor: The controller opens the transistor when the function is
(2) Transistor
activated.

IOM3.4 has 2 groups of 8 digital inputs, a total of 16 digital inputs. The first group is terminals 15 to 22, with a common on terminal
23. The second group is terminals 24 to 31, with a common on terminal 32. The groups are not connected to each other.
More information
15.10Engine interface module EIM3.1

15.10.1 Power supply characteristics
If the EIM power supply fails or is not connected, the PSM will supply power to the EIM. If the PSM power supply fails, the EIM will
run on its independent power supply. However, the EIM will not supply power to the PSM.
NOTICE
Independent power supply requirement

Class societies require an independent power supply for the EIM. The EIM must therefore not be connected to the
same power supply source as the PSM.
More information
See Power supply characteristics.
15.10.2 Auxiliary power supply voltage as an analogue output
You can configure an analogue output with a function for the auxiliary power supply voltage. The controller then adjusts the
analogue output to reflect the operating value.
Analogue output
Function IO Units Details
The controller measures the auxiliary power supply voltage

Analogue over the EIM power supply terminals. The controller uses
EIM3.1 # > EIM3.1 # supply 0 to 60 V DC
output the configured curve to convert this value to an analogue
voltage [V DC]
output.
Application
An analogue output with the power supply voltage may be wired to a switchboard instrument. The operator can then see if the
auxiliary power supply fails.

15.10.3 Magnetic pickup unit (MPU) input characteristics
Figure 15.2 MPU (inductive) voltage-time graph
Voltage
The magnetic pickup unit (MPU) input can be
[V]
used for an MPU input. This input can be
useful during startup, when the generator
frequency is too low to be a reliable indication
of genset speed.
0
By default, the MPU input is used as a backup Time
running detection. However, the MPU input [s]
can be used as the primary running detection.
NOTICE
MPU and W input

You cannot use both the MPU and W input at the same time.
Parameters
The MPU input measures the number of pulses as metal teeth on the flywheel pass the detector. It is therefore important to
configure the number of teeth correctly, since engine speed (RPM) = pulses per minute / (number of teeth).
More information
See Running detection under GENSET controller principles for the parameter to configure the number of teeth for the
MPU.
Notes on an MPU input

The MPU input terminal connections on the DEIF equipment can be changed around without any problem.
If an MPU is used, a wire break can be detected and activate an alarm.
15.10.4 W input characteristics
The W input is a signal from one of the Figure 15.3 W voltage-time graph
phases of the generator, or from an NPN/
PNP. This input can be useful during
startup, when the generator frequency is Voltage
too low to be a reliable indication of genset [V]
speed.
0
By default, the W input is used as a backup Time
running detection. However, the W input [s]
can be used as the primary running
detection.

Figure 15.4 NPN/PNP (Hall sensor) voltage-time graph
Voltage
[V]
0
Time
[s]
NOTICE
MPU and W input

You cannot use both the MPU and W input at the same time.
Parameters
The W input is an oscillating signal. Use the generator gear ratio and the number of fields in the generator to configure a "number of
teeth" to convert the wave to the engine speed.
More information
See Running detection under GENSET controller principles for the parameter to configure the number of teeth.
Notes on a W input
The engine speed calculated from the W input can differ from the actual engine speed. The accuracy depends on the genset design
and is producer-specific.
Notes on an NPN/PNP input

NPN/PNP detectors include a transistor that is powered by a direct current supply, and produce a square wave signal.
15.10.5 Analogue input (AI) characteristics
This analogue input can be configured as either current (0 to 25 mA) or resistance (0 to 2500 ohm). Using a configured or selected
input curve, the controller converts the input to a corresponding value. You can also configure the input to activate functions and/or
alarms.
Maximum voltage
This input is protected against voltages higher than 2.5 V. At higher voltages, the measurement circuit is shut off and gives an error
reading. However, if the maximum voltage in the Data sheet is exceeded (that is, 36 V), then this input or the equipment may be
damaged.
Current input
The current input may be either active or passive, and a combination of active and passive inputs may be used.
Resistance input
The resistance inputs are always passive inputs. The controller sends a small current through the external equipment and measures
the resistance.
There is no software compensation for the wire length to the resistance input. Create a custom curve for the analogue input to adjust
for errors due to wire length.
If you use a resistance input as a supervised binary input, then the maximum circuit resistance is 330 Ω.

More information
See Analogue input characteristics and configuration.
More information
See the Installation instructions for information about wiring details.
15.10.6 Relay output with wire break detection characteristics
There is one relay with wire break detection on EIM3.1, that is, terminals 9,10.
NOTICE
Wire break detection current

The wire break detection uses a small constant current for wire break detection. The wire break detection current can
activate small relays, and cannot be turned off.
More information
See Relay output with wire break detection in the Installation instructions for examples of relay wiring and more
information about the wire break detection current.
More information
15.10.7 EIM3.1 standalone
The EIM3.1 can operate in standalone mode, where it can act as a hot standby shutdown unit in case the application should be not
capable of handling the engine shutdown. The EIM runs in one of two possible modes.
Passive mode (normal operation)

In normal operation the EIM operates as a passive module in the system. It samples inputs and communicates these to the
EtherCAT master and the opposite for the outputs. The application and not the EIM, handles all alarms and controls the stop, run
and other coils. The EIM continues to check all the alarms and their set point and timer delays, but the EIM does not control the
relay activation. The relays are only changed based on control from the application. This is done to prohibit the alarm timer on the
EIM starting from 0 when it enters active mode.
Active mode (standalone)

If the connection to the EtherCAT master or the application is lost, due to loss of main power, damaged communication lines, or the
application has not yet started, the EIM enters the standalone mode. This mode must be enabled.
Engine > Safety shutdown

Not enabled : The EIM operates in Passive mode and the application
controls alarms and actions.
Not enabled,
Enable Not enabled
Enabled
Enabled : The EIM operates in Active mode and controls alarms and
actions.
Keeps the stop coil activated.

Keep stop coil Not enabled,
Not enabled
active Enabled
This is used only in the shutdown sequence with manual reset. See below.
In active mode, the EIM takes over the function of performing the necessary actions for any alarm conditions that might occur. These
actions are pre-configured and stored in the EIM module so that it can enter standalone mode directly from start-up. The EIM does
not know what the individual alarms indicate. It only knows the input, set point and timer delay associated with each alarm and then

evaluates the alarms according to these. It is the role of the application to understand the configuration of, for example, a low oil
pressure alarm related to the EIM’s configuration of multi input 2.
During active standalone mode the EIM can evaluate and action both inhibit and shutdown override inputs. These must already
have been configured and wired to the EIM module. If the communication with the EtherCAT master and application is restored and
no engine shutdown is currently active, the EIM returns the control back to the application.
Required configuration for Active standalone mode

The configuration for the standalone mode must include the following:
1. Inputs
a. Running feedback
• Digital input, MPU or oil pressure.
• At least 1 is mandatory and up to 3 are possible.
b. Inhibits
• Up to 3 are possible.
c. Shutdown override
• Up to 1 is possible.
d. Manual reset
• Up to 1 is possible.
• This is only relevant for alternative shutdown sequence (see below).
2. Outputs
a. Stop coil
b. Run coil
3. Alarms
a. At least 1 alarm with trip and shutdown or trip AVR and shutdown on EIM inputs
b. Requires the same parameters as in the normal application.
4. Extended stop timer
5. Keep stop coil active until manual reset
• This is only relevant for shutdown sequence with manual reset (see below).
6. Inhibit values
a. For example Engine running.
Engine analogue inputs

Function I/O Type Notes
Engine > Measurements > Pressure > When configured, the controller receives the oil pressure
Analogue input
Oil pressure level from this analogue input.
Engine > Measurements > When configured, the controller receives the coolant
Analogue input
Temperature > Coolant water wanter temperature from this analogue input.
Engine > Measurements > When configured, the controller receives the oil
Analogue input
Temperature > Oil temperature temperature from this analogue input.
Engine > Measurements > Level > When configured, the controller receives the coolant level
Analogue input
Coolant from this analogue input.
Safety shutdown status digital output

Function I/O Type Notes
Engine > Safety shutdown > If activate the configuration of safety shutdown is correct and
Status OK no inputs have wire breaks.

Alarm handling and alarms
EIM alarm
evaluation
1. 2.
Alarm Set point

inhibit? exceeded?
No No
Yes Yes
3.
Timer
expired? No
Yes
4.
Shutdown
override ALARM
enabled? No
Yes
5.
Shutdown
override ALARM
enabled? No
Yes
End
Any alarms configured with the fail class shutdown are used on the first EIM3.1 hardware module:
• Relay 4 supervision
• Emergency stop
• Digital and analogue custom alarms
• Above alarms on inputs
• Below alarms on inputs
• Oil pressure alarms
• Oil temperature alarms
• Coolant temperature alarms
• Coolant level alarms
• Under speed alarms
• Over speed alarms
• MPU wirebreak detection
Table 15.8 Engine analogue input alarms
Alarm Set point Action Notes
Oil pressure 1 2.0 bar Warning
Oil pressure 2 1.0 bar Trip generator breaker and shutdown engine
Oil temperature 1 120.0 C Warning

Alarm Set point Action Notes
Oil temperature 2 140.0 C Trip generator breaker and stop engine
Coolant pressure 1 20.0 % Warning
Coolant pressure 2 10.0 % Trip generator breaker and stop engine
Coolant pressure 3 5.0 % Trip generator breaker and shutdown engine
Coolant temperature 1 100.0 C Warning
Coolant temperature 2 110.0 C Trip generator breaker and stop engine
Coolant temperature 3 115.0 C Trip generator breaker and shutdown engine
Shutdown sequences
The shutdown sequence can be configured with or without a manual reset. The shutdown sequence with manual reset, which must
be both configured and operated before the shutdown is completed.
The manual reset is configured by using the parameter Engine > Safety shutdown > Keep stop coil active (see
above).
It is important to remember that with a manual reset configured, the EIM must have a manual reset in order to complete the
sequence. If no manual reset occurs the engine remains stopped and can only be restarted by power cycling.

Figure 15.5 Shutdown sequence 1. The application or EtherCAT is checked to see if it is
still active or connection has been lost.
• If active then the application continues control.
Start
2. Running feedback is checked it see if it is detected.
• If there is no running feedback the engine is
considered stopped.
Application or • Engine not active inhibit is activated.
EtherCAT End
No
lost? • Engine running inhibit is deactivated.
Yes 3. Alarms are checked to see if any active alarms are
present.
• If there are no active alarms the engine continues
Running
End operation.
feedback? No
4. With active alarms a shutdown is initiated.
Yes • Stop coil is actived.
• Run coil is deactivated.
Active • Engine stopping inhibit is activated.
End
alarms? No 5. Shutdown is pending until there is no running feedback
from the engine.
Yes
• When no running feedback is detected the engine is
considered stopped.
Shutdown 6. Shutdown initiated.
initiated • Engine not running inhibit activated.
• Engine running inhibit deactivated.
• Engine stopping inhibit deactivated.
7. The extended stop timer delay starts.
Shutdown
pending 8. Reset
• The stop coil is deactivated.
• All alarms are reset.
Running Shutdown
feedback? No
Yes
Extended
stop timer
No
expired?
Yes
Reset
End

Figure 15.6 Shutdown sequence with manual reset 1. The application or EtherCAT is checked
to see if it is still active or connection
has been lost.
Start
• If active then the application
continues control.
2. Running feedback is checked it see if it
Application or
is detected.
End
EtherCAT No • If there is no running feedback the
lost? engine is considered stopped.
Yes • Engine not active inhibit is
activated.
Running • Engine running inhibit is
feedback? End
No deactivated.
3. Alarms are checked to see if any active
Yes
alarms are present.
• If there are no active alarms the
Active engine continues operation.
End
alarms? No
4. With active alarms a shutdown is
initiated.
Yes
• Stop coil is actived.
• Run coil is deactivated.
Shutdown • Engine stopping inhibit is activated.
initiated
5. Shutdown is pending until there is no
running feedback from the engine.
• When no running feedback is
detected the engine is considered
Shutdown stopped.
pending
6. Shutdown initiated.
• Engine not running inhibit activated.
• Engine running inhibit deactivated.
Running Shutdown • Engine stopping inhibit deactivated.
feedback? No
7. The extended stop timer delay starts.
Yes 8. Checks if a stop coil must be kept
active until a manual reset.
Extended • If the stop coil does not need to be
stop timer kept active, then the stop coil is
No
expired?
deactivated.
Yes 9. Manual reset is checked.
• Manual reset must be activated in
Keep stop order to complete the sequence.
coil active until Deactive
manual reset? No stop coil 10. Reset
• The stop coil is deactivated.
Yes
• All alarms are reset.
Manual
reset? No
Reset
End

Additional standalone alarms
These alarms are only present if safety shutdown has been enabled on the EIM module.
Table 15.9 Additional alarms
Alarm Notes
EIM3.1 hardware revision does not support

Activates if EIM3.1 hardware module is revision E or older.
stand-alone
Number of configured stand-alone alarms Activates if more than 23 alarms have been configured. Above and below using 2
is too high alarms.
Activates if the shutdown has been executed by EIM3.1 hadware module, and
EIM3.1 safety shutdown still has control manual reset is not set high after, or if an alarm is running then application is started
up again.
EIM3.1 safety shutdown configuration is not Activates if the required configuration for active standalone is not correct. See
correct Required configuration for Active standalone mode above.
15.11Governor and AVR module GAM3.1

15.11.1 Analogue output (AO) characteristics
Using a configured or selected output curve, the controller converts the regulation output or operating data to the corresponding
current (-25 to 25 mA) or voltage (-10 to 10 V).
More information

15.11.2 Pulse width modulation (PWM) output characteristics
The pulse width modulation (PWM) output is a regulation output for low power circuits. It may be used to regulate an electronic
engine, but not an actuator.
The PWM output (0 to 100 %) is configured as a curve, in the same way as the other analogue outputs.
More information
Duty cycles
The PWM uses duty cycles for its output. The PWM frequency determines the cycle length. One cycle is therefore 1/500 Hz = 0.002
seconds long, ±10 %. The following table illustrates the output for various duty cycles.

Table 15.10 Relationship between duty cycles and the PWM output
Duty cycle Graph
Voltage Cycle
[V]
6.85
5.5
100 %
0.5
0
0.002 0.004 time [s]
Voltage Cycle
[V]
6.85
5.5
50 %
0.5
0
0.002 0.004 time [s]
Voltage Cycle
[V]
6.85
5.5
12.5 %
0.5
0
0.002 0.004 0.006 time [s]
15.11.3 Analogue input (AI) characteristics
This analogue input can be configured as either current (0 to 24 mA) or voltage (-10 to 10 V). Using a configured or selected input
curve, the controller converts the input to a corresponding value. You can also configure the input to activate functions and/or
alarms.
More information
See Analogue input characteristics and configuration for the general characteristics.
Galvanic connection
The two analogue inputs on GAM3.1 are galvanically connected. You therefore cannot use the analogue inputs on GAM3.1 in series
with each other (for example, for a back-up measurement).
If you need two analogue inputs in series, you can use an analogue input on another hardware module in series with an analogue
input on GAM3.1 (since the hardware modules are galvanically isolated from each other).
Current input
The current input may be either active or passive, and a combination of active and passive inputs may be used.
More information
See the Installation instructions for more information about the current input wiring.

Voltage input
More information
See the Installation instructions for more information about the voltage input wiring.
15.12Governor and AVR module GAM3.2

15.12.1 Analogue output (AO) characteristics
Using a configured or selected output curve, the controller converts the regulation output or operating data to the corresponding
current (-25 to 25 mA) or voltage (-10 to 10 V).
More information

15.12.2 Pulse width modulation (PWM) output characteristics
The pulse width modulation (PWM) output is a regulation output for low power circuits. It may be used to regulate an electronic
engine, but not an actuator.
The PWM output (0 to 100 %) is configured as a curve, in the same way as the other analogue outputs.
More information
Duty cycles
The PWM uses duty cycles for its output. The PWM frequency determines the cycle length. One cycle is therefore 1/500 Hz = 0.002
seconds long, ±10 %. The following table illustrates the output for various duty cycles.

Table 15.11 Relationship between duty cycles and the PWM output
Duty cycle Graph
Voltage Cycle
[V]
6.85
5.5
100 %
0.5
0
0.002 0.004 time [s]
Voltage Cycle
[V]
6.85
5.5
50 %
0.5
0
0.002 0.004 time [s]
Voltage Cycle
[V]
6.85
5.5
12.5 %
0.5
0
0.002 0.004 0.006 time [s]
The first relay output (terminals 14,15) on GAM3.2 is reserved for the Status OK function. You cannot change the function for this
relay.
The four other relay outputs on GAM3.2 are configurable (that is, terminals 16,17; 18,19; 20,21; and 22,23 can be assigned any
function).
More information
See Relay output characteristics and configuration for the general characteristics.
15.13Processor and communication module PCM3.1

15.13.1 PCM3.1 clock battery
PCM3.1 includes an internal battery for timekeeping during a power supply failure. If there is no power supplied to the controller or
the PCM module, the controller uses the battery power for its internal clock.
During normal operation, the controller power supply powers the internal clock.
If both the power supply and clock battery fail, the controller internal clock time is lost.

For normal operation at a temperature under 40 °C, the battery should last 10 years before it needs replacing.
If the clock battery fails, there is a PCM clock battery failure alarm.
More information
See Hardware, Controller hardware, Processor and communication module PCM3.1 in the Data sheet for more
information about the type of battery.
More information
See Maintenance, PCM3.1 internal battery, Changing the battery in the Operator's manual for information about
changing the battery.
15.14Display unit DU 300

Changeover relay, terminals 3,4,5

For future use. You cannot configure this relay.
Status OK relay, terminals 6,7

The relay output on terminals 6,7 is used for the display unit Status OK. If the display unit loses communication with the controller, or
an internal failure occurs, then the display unit deactivates the relay.
You cannot change the relay configuration. The relay is always energised when the communication is OK.
More information
See Relay output characteristics and configuration for the general characteristics.
15.15DEIF Ethernet network

15.15.1 About communication
The controllers communicate with each other to manage the system over the DEIF Ethernet network. Controllers are connected
together in a network with Ethernet cables.
Controllers must only be connected with Network chain or Network ring configuration. Do not include display units or other
equipment in the chain or ring.
Connect the controller in a Network ring configuration for communication redundancy. If there is a disruption or failure to one of the
connections, the DEIF proprietary ring protocol changes the communication path within 100 milliseconds.
You can use either the Display or PICUS to configure the controller rack communication. You must use the Display to configure the
display specific IP address settings. Changes to communication settings require a
A new controller has a default Controller ID of 0 (zero). You must configure the ID to the required ID number, otherwise an alarm
occurs. The controller ID must be the same as on the application single-line diagram.
DANGER!
Power cycle
The controller or display must be powered off and powered on for communication changes to apply.
This must be done by authorised personnel who understand the risks involved in accessing the power supply or
installation design. Take extreme care in the enclosure next to the ACM terminals. The controllers must not be in
operation and the controlled breakers must be open.

More information
See Communication in either the Operator's manual or the PICUS manual for how to configure the communication
settings.
More information
See PCM3.1 network connections in the Installation instructions for topology examples.
15.15.2 DEIF Ethernet network characteristics
Category Details
• Internet Protocol version 6 (IPv6, Auto), or Internet Protocol version 4 (IPv4, Static)
◦ IPv6 is used by default until Static is specified as the IP address mode
Specifications
• Up to 32 controllers per system
• Configure and optionally restrict Ethernet ports 1 to 5 on PCM3.1 module.
• Load sharing communication

• Authentication (non-DEIF equipment cannot disrupt communication)
• Connects the controller(s) to:
Functions ◦ Controller display unit
◦ Other controllers
• Password protection
◦ Customisable permission levels
15.15.3 Controller rack communication settings
If you change the controller ID

using the display, you must
update the controller ID in the
PICUS application diagram.
Controller ID 1 to 64 0
The system can have up to 32

controllers, with controller IDs
in the given range.
IPv6 address No default This cannot be changed.
Enabled uses IPv4 address.

Static IPv4 Enabled, Not enabled Not enabled Not enabled uses IPv6
address.
Static IPv4 address for the

IPv4 address 0.0.0.0, 255.255.255.255 * No default
controller.
Subnet mask 0.0.0.0, 255.255.255.255 * No default Depends on the IPv4 address.
Default gateway 0.0.0.0, 255.255.255.255 * No default
Preferred DNS 0.0.0.0, 255.255.255.255 * No default
Alternate DNS 0.0.0.0, 255.255.255.255 * No default
NOTE * The range of addresses that you can actually use depends on your network design. If you select Static, then you must
give the controller a unique IPv4 address. In addition, some addresses in this range are reserved.
The controller must be powered off and powered on again for changes to these settings to take effect.

15.15.4 Controller rack Ethernet port settings
Standard node (sub-ring) :

• Standard node (sub-ring) Standard • Allows only interconnection between ML 300 controllers.
Network
• Interconnection node node (sub-
mode
(major ring) ring) Interconnection node (major ring) :
• Allows only interconnection between Standard (sub-ring)s.
Automatic :
• The port automatically detects the type of device or connection.
Standard (sub-ring):
• Allows only interconnection between ML 300 controllers.
• Automatic
• Standard (sub-ring)
Interconnection (major ring):
• Interconnection (major
Port 1 to 5 Automatic • Select to specify the port as part of a major ring.
ring)
• External network/PICUS
• Disabled * External network/PICUS:
• Select to specify external network (Modbus, external switch,
utility software, etc. ) or PICUS utility software.
Disabled:
• Select to stop any Ethernet communication on the port.
NOTE * You cannot configure all Ethernet ports as Disabled. At least one Ethernet port must remain configured.
15.15.5 Display communication settings
IPv6 address No default
Preferred DNS 0.0.0.0, 255.255.255.255 * No default
Alternate DNS 0.0.0.0, 255.255.255.255 * No default
Enabled uses IPv4 address.

Static IPv4 * Enabled, Not enabled Not enabled Not enabled uses IPv6
address.
Static IPv4 address for the

IPv4 address 0.0.0.0, 255.255.255.255 * No default
display.
Subnet mask 0.0.0.0, 255.255.255.255 * No default Depends upon IPv4 address.
Default gateway 0.0.0.0, 255.255.255.255 * No default
NOTE * The range of addresses that you can actually use depends on your network design. If you select Static, then you must
give the display a unique IPv4 address. In addition, some addresses in this range are reserved.
More information
See Communication in the Operator's manual for how to configure communication from the display.
15.15.6 Restrictions
• Up to 32 controllers can be connected to each other in each network chain or ring.

• Display units can be connected to the controllers, but must not be used as part of the network chain or ring.
• Configurable switches and fiber extenders can be included in the network.
◦ It is the customer's responsibility to configure and test these.
◦ DEIF is not responsible for the performance or functionality of any non-DEIF equipment in the network.
• The Interconnection (major ring) can only be used for infrastructure network.
NOTICE
Marine applications
For marine applications, you must use a marine-approved managed switch to connect the DEIF network to your own
network. The switch must support and be enabled for Rapid Spanning Tree Protocol (RSTP), otherwise there will be a
network failure.
15.16DEIF internal communication


Factory settings

More information
connections.

16. Glossary
16.1 Terms and abbreviations
Term Abbreviation Explanation
Action The pre-defined set of actions that an alarm initiates. Also known as fail class.
The number of alarms that can be assigned to an operating value. For example, the
Alarm levels
Over-current protection by default has two alarm levels.
Alarm monitoring Third party equipment used to monitor the controller system's alarms, for example, by
AMS
system using Modbus TCP/IP communication.
Alternating current AC
Alternating current A replaceable PCB with voltage and current measurement inputs. Used in the DEIF
ACM3.1
module 3.1 controller.
American National
ANSI
Standards Institute
American wire gauge AWG A standardised wire gauge system, also known as the Brown & Sharpe wire gauge.
Terminals on a controller hardware module that the controller uses to measure an

analogue input. The analogue input type and range are typically selected during
Analogue input AI commissioning from a list of pre-configured voltage, current, and resistance
measurement input ranges. A pre-configured analogue input function or alarm can also
be assigned to the input.
Terminals on a controller hardware module that the controller uses to send an analogue
output. The analogue output type and range are typically selected during commissioning
Analogue output AO
from a list of pre-configured voltage and current output ranges. A pre-configured
analogue output function can also be assigned to the output.
Apparent power S The 3-phase apparent power, measured in kVA.
Automatic voltage Regulates the genset voltage. The AVR is external equipment. The AVR can have a
AVR
regulator fixed voltage set point. Alternatively, the DEIF controller can control the AVR.
The generator supplies a constant load. For GENSET controllers, configure the
Base load
asymmetric load sharing parameters to have a base load from a specific genset.
The wiring to a controller's digital input and common terminals may be swapped around
Bi-directional input
without affecting the input's operation.
The busbar voltage is less than 10 % of the nominal voltage, and all generator breakers
Blackout
are open.
A hardware module that consists of only a module faceplate. These are installed over
Blind module
empty slots, to protect the controller electronics.
A mechanical switching device that closes to connect power sources to the busbar, or to
Breaker connect busbar sections. The breaker opens to disconnect the power sources or to split
the busbar.
The copper conductors which connect the power sources to the power consumers.
Represented on the single-line diagram as the line that connects all the power sources
Busbar and power consumers. If the bus tie breaker is open, there are two separate and
independent busbar sections. Similarly, if the bus tie breaker is closed, there is only one
busbar.
The busbar side of the breaker. For a SHORE connection controller, this is the ship
[Busbar]
busbar. For a BUS TIE breaker controller, this is Busbar B.
Physically disconnects two main busbars from each other, so that they operate as two
Bus tie breaker BTB separate (split) busbars. Also reconnects split busbars so that they operate as one
busbar. A BUS TIE breaker controller can control a bus tie breaker.

BUS TIE breaker Controls and protects a bus tie breaker. The controller ensures that the two busbars are
controller synchronised before closing the bus tie breaker.
Canadian Electrical A standard published for the installation and maintenance of electrical equipment in
CEC
Code Canada.
The careful and systematic process that takes place after installation and before the
Commissioning system is handed over to the operator. Commissioning must include checking and
adjusting the controller.
This is generally connected to either a power source, or the supply return. See the
Common terminal COM
wiring examples for more information.
Assigning input and output functions to terminals, and setting parameters, so that the
Configuration controller is suitable for the application where it is installed. Configuration also refers to
the arrangement of hardware and wiring.
The product meets the legal requirements described in the applicable directive(s). All
Conformité
CE products with CE marking have free access to markets in the European Economic Area
Européenne
(EEA).
A generator is connected to the system if it is running, synchronised with the busbar,

Connected
and its breaker is closed.
DEIF equipment that measures system conditions and then uses outputs to make the
Controller
system respond appropriately.
A transformer for a current measurement, so that the current at the controller is within
Current transformer CT
the controller's specifications.
The ladder logic system included in the controller software, which can be configured for
CustomLogic
customised responses to measured or calculated values.
Diesel generator DG A GENSET controller can control a diesel generator.
Differential current A replaceable PCB with current measurement inputs on consumer and neutral sides.
ACM3.2
module Used in the DEIF controller.
Terminals on a controller hardware module that the controller uses to measure a digital
Digital input DI
input. A pre-configured digital input function or alarm can be assigned to the input.
Terminals on a controller hardware module that the controller uses to send a digital
Digital output DO
output. A pre-configured digital output function can be assigned to the output.
Direct current DC
Electromagnetic An equipment characteristic relating to the equipment's performance in the presence of

EMC
compatibility electromagnetic interference, as well as its emission of electromagnetic interference.
Electromagnetic The radiation emitted by the equipment as well as radiation that can affect the
EMI
interference performance of equipment.
Electrostatic
ESD
discharge
A controller test environment, accessible from PICUS, that does not require live AC
Emulation
power. A virtual operation mode, to simulate the effect of various real world actions.
Endian refers to how the order of bytes in a multi-byte value is perceived or acted upon.
Endian It is the system of ordering the individual elements in a digital word in a computer’s
memory as well as describing the order of transmission of byte data over a digital link.
Engine interface A replaceable PCB, with its own power supply. This module includes 4 relay outputs, 4
EIM3.1
module 3.1 digital inputs, an MPU and W input, and 3 analogue inputs.
Standards issued by the European Committee for Standardisation (also known as

European Norm EN
Comité Européen de Normalisation).

Software that is installed in the controller. This software enables the controller to:
Firmware process inputs and outputs, display operating data, keep track of the equipment status,
and so on.
The breaker between a generator (for example, a genset) and the busbar. The GENSET
Generator breaker GB
and EMERGENCY genset controllers can control a generator breaker.
Generator tacho A generator tacho measurement. This can be used as a backup measurement for
W
(measurement/output) generator speed.
Controls and protects a genset. This includes control of the generator breaker. The
GENSET controller Power Management System can automatically start and stop gensets to ensure that the
required power is available.
Governor GOV Regulates the engine speed.
A replaceable PCB, which includes load sharing capability. This module also includes 4
Governor and AVR
GAM3.1 relay outputs, 2 analogue current or voltage outputs, a pulse width modulation output,
module 3.1
and 2 analogue current or voltage inputs.
Governor and AVR A replaceable PCB with its own power supply, two analogue outputs, a pulse width
GAM3.2
module 3.2 modulation output, five digital inputs, a status relay output, and four relay outputs.
A connection between the equipment and earth. For marine applications, a ground is a
Ground
connection to the ship's frame.
Regional standards maintained by the Euro-Asian Council for Standardization,

GOST
Metrology and Certification.
High speed digital

HSDI MPU/W/NPN/PNP sensor digital input.
input
The controller's digital output(s) that can be connected to a horn, a siren, lights, or other
Horn output
equipment. This alerts the operator that one or more alarms are activated.
HYBRID controller Controls and protects an inverter with battery energy storage and the inverter breaker.
Hysteresis An offset added to prevent rapid switching when a value is near the control point.
Ingress Protection
The degree of protection against solids and water provided by mechanical casings and
Rating, or International IP
electrical enclosures.
Protection Rating
A pre-defined condition that inhibits the alarm action. For example, for the inhibit ACM
wire break, if the controller detects a wire break on the voltage measurements, the
Inhibit
voltage unbalance alarm is prevented from occurring. Inhibited alarms are not shown in
the alarm display.
Input output module

IOM3.1 A replaceable PCB, with 4 relay outputs, and 10 digital inputs.
3.1
Input output module A replaceable PCB, with 4 relay outputs, 4 analogue multifunctional outputs, 4 digital
IOM3.2
3.2 inputs, and 4 analogue multifunctional inputs.
Input output module

IOM3.3 A replaceable PCB, with 10 analogue multifunctional inputs.
3.3
Input output module

IOM3.4 A replaceable PCB, with 12 transistor outputs, and 16 digital inputs.
3.4
Institute of Electrical
and Electronics IEEE
Engineers
International
Association of
IACS
Classification
Societies

International
Electrotechnical IEC
Commission
International
Organization for ISO
Standardization
Internet Protocol A protocol for communication across networks. IPv4 currently routes the most traffic on
IPv4
version 4 the Internet, but will gradually be replaced by IPv6.
Internet Protocol A protocol for communication across networks. Among other things, IPv6 has a much
IPv6
version 6 larger address space than IPv4.
JEM-TR177 Japan Electrical Manufacturers Association's noise standard.
Inverter Equipment that changes the direct current to alternating current for the busbar.
An extra layer of protection that keeps the alarm action activated. When the alarm is not
Latch
active and acknowledged, it can be unlatched.
Light emitting diode LED Used to show the controller and equipment status and alarms.
The screen of the display unit. The information displayed varies, depending on the
Liquid crystal display LCD
controller mode, the equipment operation and the operator input.
The controllers adjust the gensets so that each genset supplies the right amount of the
Load sharing total power. For equal load sharing, each genset supplies the same proportion of its
nominal power.
A controller operating mode. Operator commands using the display unit push-buttons
Local control LOCAL (for example, close breaker) start pre-programmed sequences in the controller. Remote
commands are ignored.
Measures the genset speed (that is, RPM). This sensor is normally located at the genset
Magnetic pickup MPU
flywheel.
Mean Time Between

MTBF
Failures
Mean Time To Failure MTTF
A standardised, replaceable printed circuit board that is mounted in the rack. For
Module
example, PSM3.1 is a hardware module that supplies power to the rest of the rack.
Multi-line 300 ML 300 A DEIF product platform. PPM 300 is part of ML 300.
All controllers perform all the power management calculations, based on shared
Multi-master system
information.
Square brackets show that the name inside the square bracket must be adapted
Name [] according to the controller type. For example, for a GENSET controller, [Source] is
"Generator".
National Electrical A standard for the safe installation of electrical wiring and equipment in the United
NEC
Code States.
Used to synchronise the time of a computer client or server to another server or

Network time protocol NTP
reference time source.
Neutral N The neutral line in a three-phase electrical system.
An Ethernet connection topology where the controllers are connected in a line, and the
Network ring
last controller is connected back to the first.
Network chain An Ethernet connection topology where the controllers are connected in a line.
The expected voltage and frequency for the system, and each power source's maximum
Nominal setting nom or NOM load and current. Many of the controller's alarms are based on percentages of the
nominal settings.

A load that is not critical to the system. These may be disconnected by the controller in
Non-essential load NEL
the event of over-load, over-current, or busbar under-current.
NPN A type of transistor.
Hash represents a number. The description is the same for each item in the range. For
Number #
example, "Controller ID #" represents any of the possible controller IDs.
Oil pressure OP
The time that the controller takes to measure, calculate, and change the controller
Operate time output. For each alarm, the reaction time is based on the minimum setting for the time
delay.
A state that an alarm can be assigned to by an operator. Out of service alarms are
Out of service inactive alarms. Out of service alarms do not automatically return to service and require
operator action.
A value, or set point, used to determine the controller's operation. Parameters include
Parameter nominal values, the configuration options for the configurable inputs and outputs, and
alarm settings.
Personal computer PC Used to run the PICUS software. For example, a laptop computer.
The power line for one phase of a three-phase electrical system. Corresponds to R in
Germany, Red in the UK and Pacific, Red in New Zealand, Black in the USA, and U on
Phase L1 L1
electrical machine terminals. The above colour codes are for guidance only. If uncertain
perform a phase measurement.
The power line for one phase of a three-phase electrical system. Corresponds to S in
Germany, Yellow in the UK and Pacific, White in New Zealand, Red in the USA, and V
Phase L2 L2
on electrical machine terminals. The above colour codes are for guidance only. If
uncertain perform a phase measurement.
The power line for one phase of a three-phase electrical system. Corresponds to T in
Germany, Blue in the UK and Pacific, Blue in New Zealand, Blue in the USA, and W on
Phase L3 L3
electrical machine terminals. The above colour codes are for guidance only. If uncertain
perform a phase measurement.
A complex plane representation (that is, a magnitude and direction) of a sinusoidal

Phasor
wave.
Power P The 3-phase active power, measured in kW.
Power factor PF The 3-phase power factor.
Power in Control Utility

PICUS The DEIF utility software, used to design, configure, troubleshoot and monitor a system.
Software
Power supply module A replaceable PCB that powers the controller. This module includes three relay outputs
PSM3.1
3.1 for status signals. Used in the DEIF controller.
Power take home PTH The shaft generator is used as a motor to drive the ship's propellor.
A mode only on the HYBRID controller where power is taken in to the inverter which
Power take in PTI
charges the power source.
A mode only on the HYBRID controller where power is taken out from the inverter which
Power take off PTO
discharges the power source.
Printed circuit board PCB Supports and electrically connects components.
Processor and
A replaceable PCB, which contains the controller processor, as well as the CAN bus
communication PCM3.1
connections and Ethernet communication connections. Used in the DEIF controller.
module 3.1
Programmable logic
PLC A digital computer used for the automation of electromechanical processes.
controller

Proportional integral
PID A feedback controller.
derivative
Pt100, Pt1000 Platinum temperature sensors
Pulse width Terminals with an output that uses variable pulse widths, and behaves as an analogue
PWM
modulation output.
PNP A type of transistor.
An aluminium box with a rack system that houses the hardware modules. Each
Rack
controller consists of a rack and a number of hardware modules.
Rapid spanning tree

RSTP A protocol used to compute the topology of a local area network.
protocol
Reactive power Q The 3-phase reactive power, measured in kvar.
A controller operating mode. Remote commands (for example, close breaker) start pre-
Remote control REMOTE programmed sequences in the controller. The remote commands can come from a PLC,
PICUS or a digital input. Commands from the display unit push-buttons are ignored.
Resistance
RMI Variable resistance device, used for some of the input terminals on genset controllers.
measurement input
Refers to the mean magnitude of a sinusoidal wave. For example, RMS V refers to the
Root mean squared RMS
mean AC voltage.
A genset is regarded as running if the engine is started and there is running detection. A
Running
running engine does not necessarily have to be synchronised with the busbar.
SD card External memory
Part of the busbar that is isolated from the rest of the busbar because bus tie breaker(s)
Section are open. Busbar sections can run independently of each other, and do not have to be
synchronised.
Shaft generator SG A generator installed on the ship's main shaft that produces electricity.
Shaft generator The breaker between the shaft generator and the main busbar/switchboard. A SHAFT
SGB
breaker generator controller can control a shaft generator breaker.
SHAFT generator
Controls and protects the power supply from the shaft generator.
controller
A temporary state that an alarm can be assigned to by an operator. Shelved alarms are
inactive alarms, but only for a selected period by the operator. When the period of time
Shelve
expires, the alarm is automatically unshelved by the system restoring the alarm to the
previous alarm state. Alarm conditions are checked again.
Shielded foiled twisted

SFTP SFTP cables are used to minimise electromagnetic interference.
pair
The ship is supplied with electricity from land while in harbour through the shore
Shore connection SC
connection.
Shore connection The breaker between the shore connection and the main busbar/switchboard. A SHORE
SCB
breaker connection controller can control a shore connection breaker.
SHORE connection
Controls and protects the power supply from the shore connection.
controller
Shutdown An emergency or fast stop of the genset engine. No cooldown time is allowed.
A system where the load is connected between one phase and the neutral. Note:
Single-phase Single-phase does NOT mean a 3-wire single-phase distribution system, where the
waveforms are offset by a half-cycle (180 degrees) from the neutral wire.
The source side of the breaker. For GENSET, EMERGENCY genset, and SHAFT
[Source] generator controllers, this is the generator. For a SHORE connection controller, this is
the shore connection. For a BUS TIE breaker controller, this is Busbar A.

A mode only on the HYBRID controller where the inverter is started and the inverter
breaker is closed to the busbar but is not supplying any power. Standby allows the
Standby
controller to very quickly supply additional power to the busbar if needed, such as when
a Heavy consumer needs to start.
A PICUS function to monitor the operation of the entire system, and to send commands
Supervision
to any of the controllers.
Supervisory control
and data acquisition SCADA
system
The cabinet where the power sources are connected to the power consumers. See
Switchboard
Busbar too.
A controller operating mode. Power management and operator commands to the

controller are disabled. The operator controls the system using the switchboard. The
Switchboard control SWBD control
controller monitors operation, and the controller protections are active (that is, if an
operating value activates an alarm, the controller does the alarm action).
The gensets, the other power sources, all breakers, the busbars, and all their
System controllers. Within the system, the DEIF controllers work together to supply the power
required safely and efficiently.
Equipment other than the DEIF controller. For example: The genset, the genset engine
Third-party equipment
control system, the wiring, the busbars, and the switchboard.
Time t
An alarm must exceed its set point continuously for the period in its Time delay
Time delay
parameter before the alarm is activated.
Transmission control
The Internet protocol suite. It provides end-to-end connectivity by specifying data
protocol/internet TCP/IP
handling.
protocol
An emergency or fast opening of a breaker. No attempt is made to de-load the breaker

Trip
before it opens.
United Kingdom UK
United States of The USA sometimes requires different technical standards. They also use their own
US, USA
America system of units.
Universal serial bus USB Communication protocol.
UL 94 A plastics flammability standard released by Underwriters Laboratories of the USA.
Electrical potential difference. U is used as an abbreviation for voltage in most of

Voltage V
Europe, Russia and China.
For certain controller actions, both the voltage and frequency must be within the
Voltage and
V & Hz specified range. For example, for busbar OK, or to start synchronising a genset to the
frequency
busbar.
A transformer for a voltage measurement, so that the voltage at the controller is within
Voltage transformer VT
the controller's specifications.
16.2 Units
The table below lists the units used in the documentation, as well as the US units where these are different. In the documentation,
the US units are given in brackets, for example, 80 °C (176 °F).

Unit Name Measures US unit US name Conversion Alternative units
A ampere Current
1 bar = 0.980665
atmosphere (atm)
pounds per square
bar bar Pressure psi 1 bar = 14.5 psi
inch
1 bar = 100,000
Pascal (Pa)
T[ºC] = (T[ºF] - 32 º) × 5 / T[ºC] = T[Kelvin (K)]

ºC degrees Celsius Temperature ºF Fahrenheit
9 - 273.15
Noise or interference
dB decibel
(a logarithmic scale)
g gram Weight oz ounce 1 g = 0.03527 oz
g gravitational force Gravity, g = 9.8 m/s2 ft/s2 g = 32.2 ft/s2
h hour Time
Frequency (cycles per

Hz hertz
second)
kg kilogram Weight lb pound 1 kg = 2.205 lb
pounds per square

kPa kilopascal Pressure psi 1 kPa = 0.145 psi
inch
m metre Length ft foot (or feet) 1 m = 3.28 ft
mA milliampere Current
min minute Time
mm millimetre Length in inch 1 mm = 0.0394 in
ms millisecond Time
N·m newton metre Torque lb-in pound-force inch 1 N·m = 8.85 lb-in
revolutions per Frequency of rotation

RPM
minute (rotational speed)
s second Time
V volt Voltage
volt (alternating Voltage (alternating

V AC
current) current)
Voltage (direct
V DC volt (direct current)
current)
W watt Power
Ω ohm Resistance
16.3 Symbols
16.3.1 Mathematical symbols
Abbreviation Symbolises Example
+ Addition 2+3=5
- Subtraction 5-2=3
x Multiplication (numbers) 2×3=6
/ Division 15 / 3 = 5

Abbreviation Symbolises Example
· Multiplication (units) 5 N·m = 5 Newton metres
Σ Summation Σ Nominal power for connected gensets = 1000 kW + 1500 kW + 500 kW = 3000 kW
16.3.2 Drawing symbols
The drawings use EU symbols.
Electrical symbols
Symbol Symbol name
3-phase breaker
Capacitor
A1
Contactor Contactor with RC snubber
A2
Connector dot
S2
Current transformer (S1 and · show "current in"; S2 shows "current out")
S1
Diode
F Fuse
Ω Ohmmeter
A1
Relay Relay with freewheeling diode
A2
R Resistor (IEC-60617)
Single-line diagram closed breaker
Single-line diagram open breaker
Temporary connection dot (for example, connection to a meter)
Voltage transformer. This is a generic voltage transformer, without any information about the transformer
connections. These could for example be: open delta, star-star, closed delta, and so on.

Icons used in drawings
Symbol Symbol name
Display DU 300
Laptop
Server or desktop PC
First-angle projection
G Genset
G Shaft generator
Shore connection
SHORE
connection
N
E Non-essential load
L

Symbol Symbol name
Rack R7
Part of a module faceplate, to show examples of terminal wiring
16.3.3 Flowchart symbols
Symbol Notes
#.
Decision
No
# shows step number.
Yes
Process
ALARM Alarm
Info message Information message
Start or end

16.3.4 Module faceplate symbols
Terminals
Symbol Symbol name
Frame ground
Power supply
L1, L2, L3 and N Three-phase voltage measurements
Current transformer
COM Common
Digital input
Relay output (normally open)
* Relay with wire break detection (normally open)
Relay output (changeover relay, with normally open and normally closed terminals)
Analogue current or voltage input
Analogue current or resistance measurement input (RMI)
Magnetic pickup (MPU)
W W input (for a generator tacho output or NPN/PNP sensor)
Analogue current or voltage output
Pulse width modulation (PWM) output
Analogue input ground

Analogue output ground
Pulse width modulation (PWM) ground
P Active P load sharing (future use)
Q Reactive Q load sharing (future use)
+ Transistor positive supply
Transistor output
- Transistor common
H, CAN-A, L CAN bus A connection (future use)
H, CAN-B, L CAN bus B connection (future use)
LEDs
Symbol Symbol name
CAN-A CAN bus A (PCM)
CAN-B CAN bus B (PCM)
Network and DEIF network (PCM)
Internal communication in (PSM)

Symbol Symbol name
Internal communication out (PSM)
Internal communication status (PSM)
Power supply status (PSM)
System status (PCM)
Other
Symbol Symbol name
RJ45 connections at the top of the hardware module
RJ45 connections at the bottom of the hardware module
SD card
Terminal groups
Example Explanation
The vertical line to the right of the symbols shows terminal groups. In the example, the digital inputs have the
same common.
COM

Ppu 300 Designers Handbook 4189341097 Uk

Uploaded by

Copyright:

Available Formats

Ppu 300 Designers Handbook 4189341097 Uk

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ppu 300 Designers Handbook 4189341097 Uk

Uploaded by

Copyright:

Available Formats

DESIGNER'S HANDBOOK

DESIGNER'S HANDBOOK 4189341097S EN Page 2 of 396

3. Busbar sections and load sharing

DESIGNER'S HANDBOOK 4189341097S EN Page 3 of 396

DESIGNER'S HANDBOOK 4189341097S EN Page 4 of 396

5. Alarms and protections

DESIGNER'S HANDBOOK 4189341097S EN Page 5 of 396

6. Breakers, synchronisation and de-loading

DESIGNER'S HANDBOOK 4189341097S EN Page 6 of 396

DESIGNER'S HANDBOOK 4189341097S EN Page 7 of 396

8. Engine interface communication

DESIGNER'S HANDBOOK 4189341097S EN Page 8 of 396

10. HYBRID controller

DESIGNER'S HANDBOOK 4189341097S EN Page 9 of 396

11. SHAFT generator controller

12. SHORE connection controller

DESIGNER'S HANDBOOK 4189341097S EN Page 10 of 396

13. BUS TIE breaker controller

DESIGNER'S HANDBOOK 4189341097S EN Page 11 of 396

15. Hardware characteristics

DESIGNER'S HANDBOOK 4189341097S EN Page 12 of 396

DESIGNER'S HANDBOOK 4189341097S EN Page 13 of 396

1.1 Intended users of the Designer's handbook

1.2 Symbols and conventions

Function or parameter path notation

A function or parameter path is stated in this document as follows:

Inputs and outputs

1. Open the page: Configure > Input/output.

1. Open the page: Configure > Parameters.

DESIGNER'S HANDBOOK 4189341097S EN Page 14 of 396

Parameter used by more than one function example

For a GENSET controller:

Use of square brackets examples

[Source] represents the Generator for a GENSET controller.

[Hardware module] represents the relevant controller hardware module.

[Breaker] represents the Generator breaker for a GENSET controller.

Use of hash # example

Symbols for hazard statements

This shows dangerous situations.

This shows potentially dangerous situations.

DESIGNER'S HANDBOOK 4189341097S EN Page 15 of 396

This shows low level risk situation.

This shows an important notice

Symbols for general notes

NOTE This shows general information.

This shows an example.

1.3 Software versions

Software Details Version

PCM APPL Controller application 1.0.21.x

DU APPL Display unit application 1.0.20.x

PICUS PC software 1.0.19.x

1.4 Technical support

Service and support

DESIGNER'S HANDBOOK 4189341097S EN Page 16 of 396

1.5 Warnings and safety

Hazardous live currents and voltages

Controller power supply

Connect the controller protective earth

Manual override of alarm action

DESIGNER'S HANDBOOK 4189341097S EN Page 17 of 396