Intelineo 6000 1.3.0 Global Guide

InteliNeo
6000
Controller for parallel hybrid
microgrid applications
SW version 1.3.0
1 Document information 6
2 System overview 14
3 Applications overview 40
4 Installation and wiring 44
5 Controller setup 82
6 Grid Codes 294
7 Communication 306
8 Technical data 330
9 Appendix 332
Copyright © 2023 ComAp a.s.

Written by ComAp
Prague, Czech Republic
ComAp a.s., U Uranie 1612/14a,
170 00 Prague 7, Czech Republic
Tel: +420 246 012 111
E-mail: [email protected], www.comap-control.com Global Guide
Table of contents
1 Document information 6 2.7.3 WinScope 1000 23
1.1 Declaration of Conformity 6 2.7.4 InteliSCADA 23
1.2 Clarification of Notation 6 2.8 Displays 23
1.3 About this Global Guide 7 2.8.1 InteliVision 5.2 24
1.4 Legal notice 7 2.8.2 InteliVision 10Touch 24
1.5 Used open source software: 8 2.8.3 InteliVision 13Touch 25
1.6 General warnings 10 2.8.4 InteliVision 18Touch G1/G2 25
1.6.1 Remote control and programming 10 2.9 Plug-in Modules 25
1.6.2 SW and HW versions compatibility 10 2.9.1 CM2-4G-GPS 26
1.6.3 Dangerous voltage 10 2.9.2 CM-4G-GPS 26
1.6.4 Adjust the setpoints 10 2.9.3 EM-BIO8-EFCP 26
1.7 Functions and protections 11 2.10 CAN Extension Modules 27
1.8 Certifications and standards 11 2.10.1 Inteli AIN8 27
1.9 Document history 11 2.10.2 Inteli IO8/8 28
1.10 Symbols in this manual 12 2.10.3 IGL-RA15 28
2.10.4 IGS-PTM 29
2 System overview 14
2.10.5 Inteli AIO9/1 29
2.1 General description 14
2.10.6 Inteli AIN8TC 30
2.1.1 The key features of InteliNeo 6000 14
2.10.7 I-AOUT8 30
2.2 Getting Started 15
2.10.8 IS-AIN8 30
2.3 Measurement methods 16
2.10.9 IS-AIN8TC 31
2.3.1 True RMS measurement 16
2.10.10 IS-BIN16/8 31
2.3.2 Symmetrical components 16
2.11 CAN Communication Modules 32
2.4 AC measurement 17
2.11.1 InteliGateway 300 32
2.4.1 AC measurement settings 17
2.11.2 I-CR 32
2.4.2 Frequency measurement accuracy
2.12 Virtual modules 32
and resolution 17
2.12.1 Distributed modules 33
2.4.3 PF measurement and evaluation 17
2.12.2 Shared modules 35
2.4.4 Waveform distortion measurements 18
2.5 Communication peripherals 18 3 Applications overview 40
2.6 Configurability and monitoring 20 3.1 SPTM 41
2.6.1 Supported configuration and 3.2 MINT 42
monitoring tools 20
2.6.2 Configuration parts 20 4 Installation and wiring 44
2.7 PC tools 22 4.1 Package content 44
2.7.1 InteliConfig 22 4.2 Controller installation 45
2.7.2 WebSupervisor 22 4.2.1 Dimensions 45
InteliNeo 6000 1.3.0 Global Guide 2

4.2.2 Mounting 45 5.4.7 CAN Intercontroller Communication 132
4.3 Terminal Diagram 47 5.4.8 CAN1 ECU/IO Modules Splitting 133
4.4 Recommended wiring 49 5.4.9 Configuration Lock 135
4.4.1 General 51 5.4.10 Configuration Override 135
4.4.2 Grounding 51 5.4.11 Control Groups 136
4.4.3 Power supply 52 5.4.12 Crash Dump 137
4.4.4 Measurement wiring 53 5.4.13 Distributed Power Management
4.4.5 Binary Inputs 65 Signals 138
4.4.6 Binary Outputs 66 5.4.14 E-STOP 143
4.4.7 E-Stop 67 5.4.15 Event History 145
4.4.8 Analog Inputs 67 5.4.16 Exercise Timers 149
4.4.9 Analog Outputs 70 5.4.17 Firewall 157
4.4.10 CAN bus and RS485 wiring 71 5.4.18 Forced Value 158
4.4.11 USB 74 5.4.19 Hot Swap Redundancy 160
4.4.12 Ethernet 75 5.4.20 I/O Configuration 166
4.4.13 Cellular Connection 76 5.4.21 Load Shedding 170
4.5 External display 79 5.4.22 Loss of Mains (Decoupling)

Protections 173
4.5.1 InteliVision Displays 79
5.4.23 Mains Import Measurement 175
4.6 Maintenance 81
5.4.24 Modbus Client (Master) 175
4.6.1 Backup battery replacement 81
5.4.25 Multiple ECU 180
5 Controller setup 82 5.4.26 Operating Modes 181
5.1 Operator Guide 82 5.4.27 PLC - Programmable Logic
5.1.1 InteliVision 5.2 82 Controller 183
5.2 Controller configuration and PC tools 5.4.28 Power Formats And Units 196
connection 112 5.4.29 Protections 197
5.2.1 USB 112 5.4.30 Pulse Counters 211
5.2.2 Ethernet 113 5.4.31 PV Inverter Slots 212
5.3 Default configuration 118 5.4.32 SD Card Storage 215
5.3.1 Binary inputs 118 5.4.33 Sensor Curves 216
5.3.2 Binary outputs 119 5.4.34 Service Timers 218
5.3.3 Analog inputs 119 5.4.35 Sunrise/Sunset 219
5.3.4 Analog Outputs 119 5.4.36 Sunspec 219
5.4 General Functions 119 5.4.37 System Start/Stop 219
5.4.1 3V3 Reference Voltage Measurement121 5.4.38 SW Key Features 219
5.4.2 Access lock 121 5.4.39 User Buttons 220
5.4.3 Alarm Management 122 5.4.40 User Management And Data Access
5.4.4 AMF Function 125 Control 222
5.4.5 Breaker Control 126 5.4.41 User Setpoints 228
5.4.6 CAN Bus Log 131 5.4.42 Voltage Phase Sequence Detection 231

5.5 Application related functions 231 through - LVRT-2ph
5.5.1 Application & System Variability 233 6.6.3 1-pole undervoltage failure ride
5.5.2 BESS Charging/Discharging Control 235 through - LVRT-1ph 300
5.5.3 BESS Forced power 237 6.6.4 Overvoltage failure ride through -
OVRT 300
5.5.4 BESS Operation States 237
6.6.5 Post VRT 301
5.5.5 BESS Output Control 239
6.7 P For Q 301
5.5.6 BESS Precharge Types 240
6.7.1 UQ Area 301
5.5.7 BESS Stabilization 241
6.7.2 PQ Area 301
5.5.8 BESS/PV PF/Q Control 242
6.8 Q&U Protection 302
5.5.9 Connecting To Load 243
6.9 Synchronization & Connection Conditions 302
5.5.10 Curtailment Counter 249
6.9.1 Network connection/reconnection
5.5.11 Multiple Island Operation 251
conditions 302
5.5.12 Output Control – Frequency/Load 251
6.9.2 Network connection/reconnection
5.5.13 Output Control - Voltage/PF 254
conditions after Mains Fail 303
5.5.14 Parallel To MainsOperation - MINT
6.10 After Mains Trip Period 303
Application 256
6.11 Pave 304
5.5.15 Parallel To Mains Operation - MPTM
6.12 Moving Average 304
Application 258
6.12.1 10-minutes averages 304
5.5.16 Power Management 269
6.12.2 1-minute averages 305
5.5.17 PV Curtailment 290
6.13 BESS Operation Area 305
5.5.18 Regulation Loops 290
7 Communication 306
6 Grid Codes 294
7.1 PC 306
6.1 What are Grid Codes 294
7.1.1 Direct communication 306
6.2 Testing of Grid Codes 294
7.1.2 Remote communication 307
6.3 Power Regulation Based On Over/Under
Frequency 294 7.2 Connection to 3rd party systems 309
6.3.1 Power reduction by over frequency - 7.2.1 SNMP 309

PoF 294 7.2.2 Modbus-RTU, Modbus/TCP 311
6.3.2 Power increase by under frequency -
PuF 295 8 Technical data 330
6.3.3 Return from over/under frequency 296

9 Appendix 332
6.4 Power Regulation Based On Actual Mains
9.1 Controller objects 332
Voltage 297
9.1.1 List of controller objects types 332
6.4.1 P Instal (Um) 297
9.1.2 Renameable controller objects 333
6.4.2 P Actual (Um) 297
9.1.3 Setpoints 333
6.5 Load Reduction 298
9.1.4 Values 652
6.6 Dynamic Support - VRT 299
9.1.5 Application Curves 857
6.6.1 3-pole undervoltage failure ride
through - LVRT-3ph 299 9.1.6 Logical binary inputs 876
6.6.2 2-pole undervoltage failure ride 9.1.7 Logical binary outputs 920
300

9.1.8 Logical analog inputs 980
9.1.9 Fixed Protection States 1016
9.1.10 User Protection States 1024
9.1.11 PLC 1027
9.2 Alarms 1080
9.2.1 Alarm levels in the controller 1080
9.2.2 Alarms level 1 1080
9.2.4 Other alarms 1132
9.3 Modules 1184
9.3.1 Plug-in modules 1184
9.3.2 CAN modules 1189
6 back to Table of contents

1 Document information
1.1 Declaration of Conformity 6
1.2 Clarification of Notation 6
1.3 About this Global Guide 7
1.4 Legal notice 7
1.5 Used open source software: 8
1.6 General warnings 10
1.7 Functions and protections 11
1.8 Certifications and standards 11
1.9 Document history 11
1.10 Symbols in this manual 12
1.1 Declaration of Conformity

Supplier's Declaration of Conformity
47 CFR § 2.1077 Compliance Information
Unique identifier: INEO6000BBB
Responsible Party:
Kevin Counts
10 N Martingale Rd #400
60173 - Schaumburg, IL
USA
Tel: +1 815 636 2541

E-mail: [email protected]
FCC Compliance Statement

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) This device may not cause harmful interference, and (2) this device must accept any interference
received, including interference that may cause undesired operation.
1.2 Clarification of Notation

Note: This type of paragraph calls the reader’s attention to a notice or related theme.
IMPORTANT: This type of paragraph highlights a procedure, adjustment etc., which can cause a
damage or improper function of the equipment if not performed correctly and may not be clear at
first sight.

WARNING: This type of paragraph highlights a procedure, adjustment etc., which can cause a
damage or improper function of the equipment if not performed correctly and may not be clear at
first sight.
Example: This type of paragraph contains information that is used to illustrate how a specific function
works.
1.3 About this Global Guide

This manual contains important instructions for InteliNeo 6000 controllers family that shall be followed during
installation and maintenance of the controllers.
This manual provides general information how to install and operate InteliNeo 6000 controllers.
This manual is dedicated for:
Operators
Control panel builders
For everybody who is concerned with installation, operation and maintenance
1.4 Legal notice

This End User's Guide/Manual as part of the Documentation is an inseparable part of ComAp’s Product
and may be used exclusively according to the conditions defined in the “END USER or Distributor LICENSE
AGREEMENT CONDITIONS – COMAP CONTROL SYSTEMS SOFTWARE” (License Agreement) and/or in
the “ComAp a.s. Global terms and conditions for sale of Products and provision of Services” (Terms) and/or in
the “Standardní podmínky projektů komplexního řešení ke smlouvě o dílo, Standard Conditions for Supply of
Complete Solutions” (Conditions) as applicable.
ComAp’s License Agreement is governed by the Czech Civil Code 89/2012 Col., by the Authorship Act
121/2000 Col., by international treaties and by other relevant legal documents regulating protection of the
intellectual properties (TRIPS).
The End User and/or ComAp’s Distributor shall only be permitted to use this End User's Guide/Manual with
ComAp Control System Registered Products. The Documentation is not intended and applicable for any
other purpose.
Official version of the ComAp’s End User's Guide/Manual is the version published in English. ComAp
reserves the right to update this End User's Guide/Manual at any time. ComAp does not assume any
responsibility for its use outside of the scope of the Terms or the Conditions and the License Agreement.
Licensed End User is entitled to make only necessary number of copies of the End User's Guide/Manual. Any
translation of this End User's Guide/Manual without the prior written consent of ComAp is expressly
prohibited!
Even if the prior written consent from ComAp is acquired, ComAp does not take any responsibility for the
content, trustworthiness and quality of any such translation. ComAp will deem a translation equal to this End
User's Guide/Manual only if it agrees to verify such translation. The terms and conditions of such verification
must be agreed in the written form and in advance.
For more details relating to the Ownership, Extent of Permitted Reproductions Term of Use of the
Documentation and to the Confidentiality rules please review and comply with the ComAp’s License
Agreement, Terms and Conditions available on www.comap-control.com.
Security Risk Disclaimer

Pay attention to the following recommendations and measures to increase the level of security of ComAp
products and services.
Please note that possible cyber-attacks cannot be fully avoided by the below mentioned recommendations
and set of measures already performed by ComAp, but by following them the cyber-attacks can be
considerably reduced and thereby to reduce the risk of damage. ComAp does not take any responsibility for
the actions of persons responsible for cyber-attacks, nor for any damage caused by the cyber-attack.
However, ComAp is prepared to provide technical support to resolve problems arising from such actions,
including but not limited to restoring settings prior to the cyber-attacks, backing up data, recommending other
preventive measures against any further attacks.
Warning: Some forms of technical support may be provided against payment. There is no legal or factual
entitlement for technical services provided in connection to resolving problems arising from cyber-attack or
other unauthorized accesses to ComAp's Products or Services.
General security recommendations and set of measures
1. Production mode
Disable production mode BEFORE the controller is put into regular operation.
2. User accounts
Change password for the existing default administrator account or replace that account with a
completely new one BEFORE the controller is put into regular operation mode.
Do not leave PC tools (e.g. InteliConfig) unattended while a user, especially administrator, is logged in.
3. AirGate Key
Change the AirGate Key BEFORE the device is connected to the network.
Use a secure AirGate Key – preferably a random string of 8 characters containing lowercase,
uppercase letters and digits.
Use a different AirGate Key for each device.
4. MODBUS/TCP
The MODBUS/TCP protocol (port TCP/502) is an instrumentation protocol designed to exchange data
between locally connected devices like sensors, I/O modules, controllers etc. By it's nature it does not
contain any kind of security – neither encryption nor authentication. Thus it is intended to be used only
in closed private network infrastructures.
Avoid using MODBUS/TCP in unprotected networks (e.g. Internet).
5. SNMP
The SNMP protocol (port UDP/161) version 1 and version 2 are not encrypted. They are intended to be
used only in closed private network infrastructures.
Avoid using SNMP v1 and v2 in unprotected networks (e.g. Internet).
IMPORTANT: Controller issues Wrn Default Password (page 1086) alarm, if the factory default
password is used. It is necessary to change the factory default settings of password to be able to
clear the alarm.
1.5 Used open source software:

Name of
Modified Type License condition web address
software
CMSIS Copyright (C) 2020 Amazon.com, Inc. or
MIT license
FreeRTOS its affiliates. All Rights Reserved.

Copyright (C) Amazon Web Services, Inc.
FreeRTOS MIT license
or its affiliates. All rights reserved.
Copyright (C) 2006-2015, ARM Limited,
Mbed TLS Apache 2.0 license
All Rights Reserved
Copyright (c) 2001-2004 Swedish Institute
lwIP BSD 3 license
of Computer Science. All rights reserved.
Copyright (C) 1991-2, RSA Data Security,
Free ad-
MD5 – license Inc. Created 1991. All rights reserved
hoc license
RSA Data Security, Inc. MD5 Message-Digest Algorithm
Embedded
Copyright (c) 2016 jwellbelove
Template MIT license
www.etlcpp.com
Library
STM32Cube_
BSD 3 license
FW_H7
Copyright (C) 20xx, ChaN, all right
reserved.
Modify This software is provided by the copyright holder and
FatFs license contributors "AS IS" and any warranties related to this
BSD
software are DISCLAIMED. The copyright owner or
contributors be NOT LIABLE for any damages caused
by use of this software.
Copyright (c) 2011, 2013 Mutsuo Saito,

Tiny Mersenne Makoto Matsumoto, Hiroshima University
– BSD 3 license
Twister and The University of Tokyo All rights
reserved.
Copyright (c) 2018 STMicroelectronics
International N.V. All rights reserved
THIS SOFTWARE IS PROVIDED BY
STMICROELECTRONICS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS, IMPLIED OR STATUTORY
WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NON-
INFRINGEMENT OF THIRD PARTY INTELLECTUAL
PROPERTY RIGHTS ARE DISCLAIMED TO THE
FULLEST EXTENT PERMITTED BY LAW. IN NO
USB SLA0044 license EVENT SHALL STMICROELECTRONICS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
Copyright (c) 2013-2015, Scott Vokes

heatshrink – ISC license
<[email protected]> All rights reserved

Permission to use, copy, modify, and/or distribute this
software for any purpose with or without fee is hereby
granted, provided that the above copyright notice and
this permission notice appear in all copies.
license
GCC Runtime GCC Runtime Library Exception - GNU
– GPL 3 exception,
Library Project - Free Software Foundationd
license
1.6 General warnings

1.6.1 Remote control and programming
The controller can be controlled remotely. In the event that maintenance of the site has to be done, or the
controller has to be programmed, check the following points to ensure that any part of the site will not react
unpredictably (unwanted/random start of the BESS or any other part of the system).
To be sure:
Disconnect remote control
Disconnect binary outputs
1.6.2 SW and HW versions compatibility

Be aware to use the proper combination of SW and HW versions.
1.6.3 Dangerous voltage

In no case touch the terminals for voltage and current measurement!
Always connect grounding terminals!
In no case do not disconnect controller CT terminals!
1.6.4 Adjust the setpoints

All parameters are adjusted to their typical values. However, the setpoints have to be checked and adjusted to
their real values before the first starting of the BESS .
IMPORTANT: Wrong adjustment of setpoints can destroy the BESS.
Note: The controller contains a large number of configurable setpoints, because of this it is impossible to
describe all of its functions. Some functions can be changed or have different behavior in different SW versions.
Always check the Global guide and New feature list for SW version which is used in controller. This manual only
describes the product and is not guaranteed to be set for your application.
IMPORTANT: Be aware that the binary outputs can change state during and after software
reprogramming (before the controller is used again ensure that the proper configuration and
setpoint settings are set in the controller).
The following instructions are for qualified personnel only. To avoid personal injury do not perform any action not
specified in related guides for product.

1.7 Functions and protections
Support of functions and protections as defined by ANSI (American National Standards Institute):
ANSI
Description ANSI code Description ANSI code Description
code
Master unit 1 Load shedding 32P AC circuit breaker 52
Stopping device 5 Master sequence device 34 Power factor 55
Multi-function device 11 Undercurrent 37 Overvoltage 59
Speed and frequency matching
15 Unit sequence starting 44 Alarm relay * 74
device
16EFT
Data communications device Current unbalance 46 Vector shift 78
16SC
Starting-to-running transition
19 Voltage unbalance 47 Reclosing relay 79
contractor
Distance relay 21 Incomplete sequence relay 48 Overfrequency 81H
Synchronizing-check 25 Temperature monitoring 49T Underfrequency 81U
Thermal relay 26 Overcurrent 50/50TD ROCOF 81R
Undervoltage 27 Earth fault current 50N+64 Auto selective control/transfer 83
Annunciator 30 Overcurrent IDMT 51 Regulating device 90
Overload 32 Earth fault current IDMT 51+64
* extension module IGL-RA15 required
1.8 Certifications and standards

EN 61000-6-2 EN 60068-2-1 (-40 °C/16 h) UL6200 *
EN 61000-6-4 EN 60068-2-2 (70 °C/16 h) UKCA
EN 61010-1 EN 60068-2-6 (2÷25 Hz / ±1,6 mm; 25÷100 Hz / 4,0
EN 60255-1 g)
2
EN 60529 (IP20) EN 60068-2-27 (a=500 m/s ; T=6 ms)
EN 60068-2-30 (25/55 °C, RH 95%, 48 h)

* ULC 6200:2019 Certified (see the NFL File for the FW version with the Witness test if it is required by the certification of the end product)
1.9 Document history

Revision number Related sw. version Date Author
5 1.3.0 27.11.2023 ComAp
4 1.2.0 24.10.2023 ComAp
3 1.1.1.1 20.9.2023 ComAp
Adam Stocek
2 1.1.0 10.2.2023
Jakub Slavata
1 1.0.0 14.10.2022 Jakub Slavata

1.10 Symbols in this manual
Passive
Fuel
3 x Phases Coil current
solenoid
sensor
Active
Connector -
current Fuse Pick - up
female
sensor
Connector -
Fuse switch Relay coil
AirGate male
Relay coil of
Contact Generator slow-
Alternating
current operating
Generator
Contactor Renewable
Analog schematic
modem s
Controller
Grounding
simplified
Battery Resistor
Module
Battery GSM
simplified Resistor
Energy
adjustable
Storage
Current GSM
System Resistive
measuring modem
sensor
Binary
RPTC
output Current
IG-AVRi
measuring RS 232
Breaker male
contact IG-AVRi
Danger
TRANS RS 232
Breaker female
Danger -
contact Jumper
Electric
Shaft
Hazard
Generator
Breaker
DC to AC Load
Inverter Starter
Breaker
Mains Switch -
Diode
manually
Breaker operated
Ethernet Mains
male Transformer
Capacitor Mobile
Ethernet provider USB type B
female
male

USB type B
female
Voltage
measuring
Wifi / WAN /
LAN
6 back to Document
information

2 System overview
2.1 General description 14
2.2 Getting Started 15
2.3 Measurement methods 16
2.4 AC measurement 17
2.5 Communication peripherals 18
2.6 Configurability and monitoring 20
2.7 PC tools 22
2.8 Displays 23
2.9 Plug-in Modules 25
2.10 CAN Extension Modules 27
2.11 CAN Communication Modules 32
2.12 Virtual modules 32
2.1 General description

InteliNeo 6000 is a comprehensive Battery Energy Storage System (BESS) controller containing predefined
control loops for typical applications of microgrid systems connected in parallel to on-grid and off-grid primary
power sources.
The controller is user configurable and has expanded PLC capabilities to suit different levels of complexity to
allow for greater flexibility in meeting various customer applications. The Modbus client (master) capability allows
for modular connection of renewable energy sources such as BESS and PV to Gen-sets and Mains without
compromising power stability.
Built within the ComAp ecosystem, the InteliNeo 6000 is compatible to ComAp controllers via CAN2 line. ComAp
controllers may require firmware updates to support compatibility with the InteliNeo 6000.
2.1.1 The key features of InteliNeo 6000

Hot Swap - Controller Redundancy function
CAN Intercontroller Communication Redundancy
Up to 64 controllers on CAN
Grid Codes
MPTM and MINT can be switched without controller restart needed
Easy-to-use operation and installation
Various customizations are possible thanks to its configurability
Excellent remote communication capabilities
Support of Modbus Client (Master) allowing connection of up to 16 devices
Sunspec Modbus compatible with additional predefined Modbus Server Device list for PV & BESS
inverters
High reliability

2.2 Getting Started
Congratulations to your new InteliNeo 6000 ComAp BESS controller. Follow these steps bellow for first run of
your controller.
Note: For a better experience with our controller, do not forget to see the InteliConfig manual before starting
the configuration.
1. Connect controller to power supply

Controller requires power supply between 8-36 V DC. Plug +BAT to the terminal no. 03 and GND to
the terminal no. 01.
See Terminal Diagram (page 47) for more information
2. Connect your computer to the controller
We suggest you to use USB or ETH 1 - Trusted Interface for the first connection to your new controller.
Plug the USB/ETH cable to USB type B/Ethernet 1 terminal on the controller. Open InteliConfig and
select "Connect to controller". Now you can use "Detected controllers" feature, which should offer you
the controller.
3. Authorizing as Administrator
The alarmlist should show Wrn Default Password (page 1086). If this alarm is not present, this
procedure bellow will not work. You will need to use your changed password or Reset accounts to
factory default (page 224). If you see the warning, use function "Enter password" which is located in
tab "Control".
Username = administrator
Password = serial number of your controller

Serial number is located at the front of your controller or you can see it in left top corner of InteliConfig
when connected to the controller.
You can verify that you have been successfully logged in by seeing opened lock with number "3". This
means that you verified on the highest level - administrator and you have all possible rights.
4. Changing Administrator Password
You should change the default password as soon as possible via InteliConfig. In the InteliConfig select
tab "Tools", function "User administration" and "Change password". Do not forget to add your email
address which is used in case of lost access to the account.
5. Adding another users

If you are loged in as any account with permissions level 3, you can add another user. The whole
procedure is explained in chapter Adding account (page 226).

6. Connecting external display
For InteliVision displays wiring diagram see the chapter InteliVision Displays (page 79).
See more information about using the display in the chapter Operator Guide (page 82).
2.3 Measurement methods

The InteliNeo 6000 contains two methods for measuring physical quantities. The method of Symmetrical
components is measured all the time and the values are used whenever Grid Codes standard requires them.
In all other cases True RMS method is used.
Only values from Symmetrical components, visible to user, are +Mains/Bus Voltage (page 733) and
+Mains/Bus Voltage Relative (page 733).
2.3.1 True RMS measurement

This controller measures AC values based on True RMS principle. This principle corresponds exactly to the
physical definition of alternating voltage effective values. Under normal circumstances the Mains voltage
should have a pure sinusoidal waveform. However some nonlinear elements connected to the Mains produce
harmonic waveforms with frequencies of multiples of the basic Mains frequency and this may result in
deformation of the voltage waveforms. The True RMS measurement gives accurate readings of effective
values not only for pure sinusoidal waveforms, but also for deformed waveforms.
Note: The harmonic deformation causes that the Power Factor of a BESS working parallel with the Mains
cannot reach values in a certain range around the PF 1.00. The higher the deformation, the wider the power
factor dead range. If the requested power factor is adjusted inside the dead range, the controller cannot
reach the requested value because of this fact.
2.3.2 Symmetrical components

The method of symmetrical components simplifies analysis of unbalanced three-phase power systems under
both normal and abnormal conditions. The basic idea is that an asymmetrical set of N phasors can be
expressed as a linear combination of N symmetrical sets of phasors by means of a complex linear
transformation.In the most common case of three-phase systems, the resulting "symmetrical" components
are referred to as direct (or positive), inverse (or negative) and zero (or homopolar). The analysis of power
system is much simpler in the domain of symmetrical components, because the resulting equations are
mutually linearly independent if the circuit itself is balanced.

Note:
These images are based on:
https://upload.wikimedia.org/wikipedia/commons/e/e0/Unbalanced_symmetrical_components.pdf
Which has license: https://creativecommons.org/publicdomain/zero/1.0/deed.en
2.4 AC measurement
With InteliNeo 6000 it is possible to easily set the parameters for measuring.
2.4.1 AC measurement settings

AC Voltage measurement settings
The value of the AC voltage measured on the terminals of the controller can be adapted according to the used
meas voltage. For measuring AC voltage use setpoints BESS VT Ratio (page 374) and Bus Voltage Input
Range (page 375).
AC Current measurement settings

The value of the AC current measured on the terminals of the controller can be adapted phase application with
neutral according to the used meas current. For measuring AC current use setpoints BESS CT Ratio Prim
(page 369), BESS CT Ratio Sec (page 370), Mains/Bus CT Ratio Prim / EFC (page 370) and Mains/Bus CT
Ratio Sec / EFC (page 371).
2.4.2 Frequency measurement accuracy and resolution

The resolution of the measurement is in mHz within a 45–75 Hz range. Values Mains/Bus Frequency (page
731) and BESS Frequency (page 670) are used for visualization of measured frequency.
2.4.3 PF measurement and evaluation

Power factor of BESS and mains is measured with a resolution of 0.001.
Setpoints used for setting the Power factor regulation are Base Power Factor (page 352), Import Power
Factor (page 352) with a 0.001 resolution and #System Power Factor (page 353) with a 0.01 resolution.
Values for the Power factor are:

BESS Power Factor (page 667), BESS Load Character (page 667)
BESS Power Factor L1 (page 667), BESS Load Character L1 (page 667)
Load Power Factor (page 720), Load Character (page 720)
Mains PF (page 737), Mains Load Character (page 737)
2.4.4 Waveform distortion measurements

The controller also measures Total Harmonic Distortion (THD) for current and voltage using formulas bellow.
Voltage Total Harmonic Distortion
Where Vk is the True RMS voltage of kth harmonic.

Related values:
BESS Voltage THD L1 (page 668)
Current Total Harmonic Distortion
where Ik is the True RMS current of kth harmonic.

Related values:
BESS Current THD L1 (page 669)
2.5 Communication peripherals

InteliNeo 6000 contains 3x Ethernet terminals, 4x CAN terminals, 1x RS485 terminal and 1x USB type B
terminal. Each terminal functions are slightly different, which depends on the purpose of usage.
IMPORTANT: Use correct terminal according to your purpose of usage for correct function.

Peripherals Description Relevant links
This terminal is used for connecting of external modules and
Electronic Control Units. See the chapters Supported
combinations of modules (page 1189) and Multiple ECU (page
CAN1A 180) for more information.
Note: In case the function CAN1 ECU/IO Modules Splitting
(page 133) is used this terminal is used only for communication
with ECU.
This terminal is used for communication between Master and
CAN bus wiring
Backup Controller if the Hot Swap Redundancy (page 160)
(page 71)
function is used.
CAN1B
Note: In case the function CAN1 ECU/IO Modules Splitting
(page 133) is used this terminal is used only for communication
with external modules.
This terminal is used for CAN Intercontroller Communication
CAN2A
(page 132).
This terminal is used for CAN Intercontroller Communication
CAN2B
Redundancy (page 132).
This terminal is used for Modbus-RTU, Modbus/TCP (page 311) RS485 wiring
RS485
communication. (page 72)
Controller
This terminal is used for UART communication eg. InteliConfig, configuration
USB Type B WinScope1000, etc. It is considered as Trusted (page 222) and PC tools
terminal and the default account is used for connection. connection
(page 112)
In the default configuration port Ethernet 1 is configured as Trusted
(page 222) interface. It is used for LAN communication eg. Display,
Ethernet port 1
Ethernet 1 InteliConfig, WinScope1000, Modbus Server. The default account is
(page 395)
used for connection. Use this interface for local connection
only.
In the default configuration port Ethernet 2 is configured as
Untrusted (page 222) interface. It is used for remote
Ethernet port 2
Ethernet 2 communication eg. InteliConfig, WinScope1000, etc. The user
(page 396)
account with password has to be used in order to connect to the
controller.
In the default configuration port Ethernet 3 is configured as Modbus
(page 222) interface. It is used for Modbus Client (Master) (page Ethernet port 3
Ethernet 3
175) or Modbus server. It is not possible to use Modbus interface as (page 397)
a terminal connection (Inteliconfig, WinScope 1000, etc.).
You can see layout of the peripherals in the chapter Terminal Diagram (page 47).
Note: The controller has one common MAC address. Do not connect more than 1 Ethernet into the same
internet network.

2.6 Configurability and monitoring
One of the key features of the controller is the system’s high level of adaptability to the needs of each
individual application and wide possibilities for monitoring. This can be achieved by configuring and using the
powerful PC/mobile tools.
2.6.1 Supported configuration and monitoring tools

InteliConfig - complete configuration and single/multi controller monitoring
WebSupervisor - web-based system for monitoring and controlling
WebSupervisor mobile - supporting application for smart-phones
WinScope 1000 - special graphical monitoring software
InteliSCADA - customizable SCADA diagram for monitoring
The firmware of controller contains a large number of binary inputs and outputs needed for all necessary
functions available. However, not all functions are required at the same time on the same controller and also
the controller hardware does not have so many input and output terminals. One of the main tasks of the
configuration is mapping of “logical” firmware inputs and outputs to the “physical” hardware inputs and
outputs.
2.6.2 Configuration parts

Mapping of logical binary inputs (functions) or assigning alarms to physical binary input terminals
Mapping of logical binary outputs (functions) to physical binary output terminals
Mapping of logical analog inputs (functions) to physical analog input terminals, assigning sensor
characteristics (curves) or assigning alarms to analog inputs
Mapping of values to physical analog outputs, assigning output HW type with conversion characteristic
Selection of peripheral modules, which are connected to the controller, and doing the same (as mentioned
above) for them
Selection of ECU (electronic control unit) type
Changing the language of the controller interface

Image 2.1 Principle of inputs and outputs configuration
The controller is shipped with a Default configuration (page 118), which should be suitable for most
standard applications. This configuration can be changed only by using a PC with the InteliConfig software.
See InteliConfig documentation for details.
Once the configuration is modified, it can be saved to a file for later usage with another controller or for
backup purposes. The file is called archive and has the file extension .aig3. An archive contains a full image of
the controller at the time of saving (if the controller is online for the PC) except the firmware. Besides
configuration it also contains current adjustment of all setpoints, all measured values, a copy of the history log
and a copy of the alarm list.
The archive can be simply used for cloning controllers, i.e. preparing controllers with identical configuration
and settings.

2.7 PC tools
2.7.1 InteliConfig
PC Tool for configuration and monitoring of controllers. See more in the InteliConfig Global Guide.
This tool provides the following functions:

Direct or remote internet communication
with the controller
Offline or online controller configuration
Controller and module configuration,
programming and cloning
Remote display programming
Reading/writing/adjustment of setpoints
Reading of measured values
Controllers and ECU Alarm monitoring +
complete real time history
Exporting data into a XLS file
Controller language translation
Power format and ECU unit selection
Embedded manuals and F1 helps
Auto-hiding of unused setpoints and values
2.7.2 WebSupervisor
Cloud-based system designed for monitoring and management of ComAp and 3rd party devices via the
internet. See more in the WebSupervisor Global Guide.

Site and fleet monitoring
Reading of measured values
Browsing of controller history records
On-line notification of alarms
Email notification
Also available as a smart-phone application
WebSupervisor available at: www.websupervisor.net

Demo account:
Login: comaptest
Password: ComAp123

2.7.3 WinScope 1000
Special graphical controller monitoring software used mainly for commissioning and BESS troubleshooting.
See more in the WinScope 1000 Global Guide.

Monitoring and archiving of ComAp controller’s
parameters and values
View of actual/historic trends in the controller
On-line change of controller's parameters for
easy regulator setup
2.7.4 InteliSCADA
InteliSCADA is a Windows based software for monitoring of multiple controllers. See more in the InteliSCADA
Global Guide.

Basic (auto-generated) SCADA in a few minutes
Broad range of instruments with easy and fast
configuration
Fully customizable SCADA diagram
Browsing of all measured and computed values
Browsing of controllers' history records
2.8 Displays
Remote Displays / Panel PC Displays

2.8.1 InteliVision 5.2
Remote colour display for ComAp controllers, designed as an easy-to-use Plug & Play display for monitoring
and control of single BESS in various applications. See more in the InteliVision 5.2 Global Guide.
This Display unit provides the following

functions:
5" colour screen with a resolution of 800 × 480
pixels
Plug & Play operation (auto configuration
based on the controller application)
Easy screen customization using Screen
Editor in InteliConfig)
5 configurable user buttons under the screen
Multi-language support
Trends monitoring screen (up to 4 channels)
Communication with controller via Ethernet
Front face protection compliant with IP65
2.8.2 InteliVision 10Touch

Panel PC Display equipped with a projective capacitive touch display. See more in the InteliVision 10Touch
Global Guide.
This Panel PC Display provides the following

functions:
10.1” touch screen with a resolution 1280 x 800
pixels
ComAp PC tools pre-installed
Direct monitoring (and control) of 3rd party
devices via Modbus (using InteliFieldbus
Gateway)
Possibility to remotely connect to the display
using for example Remote Desktop
2 Ethernet ports
Support of IP camera

2.8.3 InteliVision 13Touch
Marine certified Panel PC Display with multi-controller support and buttons for brightness change on its front
face. See more in the InteliVision 13Touch Global Guide.
This Panel PC Display provides the following

functions:
13.3" touch screen with a resolution 1920 ×
1080 pixels
ComAp PC tools pre-installed
Multi-controller support for up to 4 controllers
Buttons for brightness change on front face
2 Ethernet ports
2.8.4 InteliVision 18Touch G1/G2

Panel PC Display perfectly suitable for the most complex applications and also the simple ones. With
InteliVision 18Touch you can easily monitor and control sites consisting of many controllers, or you can use it
for your CHP or Hybrid application. See more in the InteliVision 18Touch Global Guide G1 / InteliVision
18Touch Global Guide G2.
This Panel PC Display unit provides the

following functions:
18,5“ touch screen with a resolution 1366 × 768
pixels
ComAp PC tools preinstalled
Display for monitoring and control of the entire
site
History logs of all controllers
Multi-controller support for up to 32 controllers
Onscreen keyboard
2 Ethernet ports
2.9 Plug-in Modules

(missing or bad snippet)

2.9.1 CM2-4G-GPS
GSM/4G module
GSM/4G Internet module and GPS locator
Global 4G (LTE) module with 3G/2G backup
Remote control and monitoring of the controller
via InteliConfig, WebSupervisor
Active e-mail and SMS support
AirGate 2 technology support for easy
connection – no need of public and static IP
address
Tracking via GNSS (GPS,GLONASS) module
2.9.2 CM-4G-GPS
GSM/4G Internet module and GPS locator
Wireless integrated solution
Quick and easy installation
Support of WebSupervisor
Instant alarm SMS notification
System control over SMS
Quad Band GPRS/EDGE modem,
850/900/1800/1900 MHz, FDD LTE: Band 1,
Band 2, Band 3, Band 4, Band 5, Band 7, Band
8, Band 20, all bands with diversity,
WCDMA/HSDPA/HSUPA/HSPA+: Band 1,
Band 2, Band 5, Band 8, all bands with
diversity
GPRS multi-slot class 10
Tracking via GNSS (GPS,GLONASS) module
2.9.3 EM-BIO8-EFCP
Input and binary input/output extension module.
Up to 8 additional configurable binary inputs or
outputs

2.10 CAN Extension Modules
2.10.1 Inteli AIN8
The module allows users to expand the amount of analog inputs for sensors and add Impulse/RPM input that can
be attached to a controller. Up to 8 configurable inputs (sensors) can be attached to the module. See more
information on web page Inteli AIN8.
Supported sensors:
Resistor 3-wire input
Common resistor: 0-250Ω, 0-2400Ω, 0-10kΩ
Temperature sensor: Pt100, Pt1000, Ni100, Ni1000
Current (active or passive sensors)
±20mA , 0-20mA, 4-20mA
Voltage
±1V, 0-2,4V, 0-5V, 0-10V
Lambda probes
Thermocouples are not supported (the measuring loop was
designed for lambda probes, what caused non-support of
thermocouples)
Impulse/RPM sensor:
RPM measuring pulses with frequency 4Hz – 10kHz
Impulse
Possibility to measure pulses from electrometer, flowmeter,
etc.
IMPORTANT: Impulse input is not supported by the controller.
6 back to CAN Extension Modules

2.10.2 Inteli IO8/8
The module to expand the amount of binary inputs and outputs for ComAp controllers. It is possible to
configure the unit to have 8 binary inputs, 8 binary outputs, and 2 analog outputs, or 16 binary inputs, 0 binary
outputs and 2 analog outputs via switches inside the controller. See more information on web page Inteli
IO8/8.
Configuration 8/8
8 Binary inputs (options: pull up or pull down logic)
8 Binary outputs (options: Low side switch (LSS) or High side switch
(HSS))
2 Analog outputs (options: voltage (0-10V), current (0-20mA) and
PWM (5V, adjustable frequency 200Hz-2,4kHz))
Configuration 16/0
16 Binary inputs (options: pull up or pull down logic)
0 Binary outputs
2 Analog outputs (options: voltage (0-10V), current (0-20mA) and
PWM (5V, adjustable frequency 200Hz-2,4kHz))
2.10.3 IGL-RA15
Remote annunciator. See more information on web page IGL-RA15.
15 programmable LEDs with configurable
colors red-green-yellow
Lamp test function with status LED
Customizable labels
Local horn output
Maximal distance 200 m from the controller
Up to 4 units can be connected to the controller
UL certified
IMPORTANT: This module is not compatible with different than 250 kbps communication speed. If
the ECU module with 125 kbps communication speed is connected the whole system will
automatically switch to the 125 kbps, and IGL-RA15 module will stop communicating.

2.10.4 IGS-PTM
The module expands the amount of binary/analog inputs and outputs for ComAp controllers. It is possible to
configure the unit to have 8 binary inputs, 8 binary outputs, 4 analog inputs and 1 analog output. See more
information on web page IGS-PTM.
Configurable 8 binary and 4 analog inputs
Configurable 8 binary and 1 analog output
LEDs indicate the state of binary inputs/outputs
Measures values from Pt100 and Ni100
sensors
Analog inputs (resistance range 0-250 Ohms,
voltage range 0-100mV, current range 0-20mA
- selectable via jumper)
UL certified
2.10.5 Inteli AIO9/1

The module is suitable for measurement and control of analog inputs and output through CAN interface. It is
possible to configure the unit to have 9 analog inputs and 1 analog output. See more information on web page
Inteli AIO9/1.
4x differential voltage inputs for measurement in range of ±65 V
DC
4x shielded, galvanic separated sensors: thermocouples J,K,L,
±75 mV inputs
Resistance analog input (sensors: 0-2400Ω, PT1000 or NI1000)
Analog output with options : 0-20mA, 0-10V or PWMt

2.10.6 Inteli AIN8TC
The module allows customers to configure up to 8 analog input channels for measuring temperature by
thermocouples. The Inteli AIN8TC is useful in situations where extremely accurate temperature readings is
required. See more information on web page Inteli AIN8TC.
Supported sensors:
J, K or L thermocouples
Thermocouples with and without cold junction compensation are
supported
2.10.7 I-AOUT8
The module allows customers to configure up to 8 analog outputs. AGND terminals are on the same potential.
See more information on web page I-AOUT8.
Each analog output can be switched to

0 to 10 V DC
0/4 to 20 mA DC
1,2 kHz PWM (Pulse With Modulatio)
2.10.8 IS-AIN8
The module is equipped with 8 analog inputs. This module is compatible with MTU ECU-7 at communication
speed 125 kbps when uploaded with firmware 1.2.0 and higher. See more information on web page IS-AIN8.

Precision of inputs is 1%
2/3 wire resistive, current, voltage sensors
Predefined sensors (Pt100, Pt1000, Ni100, Ni1000, thermocouple
type J/K/L)
Current and voltage inputs 0-20mA and 0-10V
2.10.9 IS-AIN8TC
The module is equipped with 8 analog inputs dedicated for thermocouple sensors only. See more information
on web page Inteli AIN8TC.
J, K or L thermocouples
Thermocouples with and without cold junction compensation are
supported
2.10.10 IS-BIN16/8
The module allows users to expand the amount of binary inputs and outputs, and add 2 impulse inputs. It is
possible to configure the unit to have 16 binary inputs (galvanic separated) and 8 binary outputs (galvanic
separated), 2 pulse inputs (frequency measurement or pulse counting). See more information on web page
IS-BIN16/8.
To operate external modules:

Configurable 16 galvanically separated inputs
Configurable 8 outputs
2 pulse inputs (frequency measurement or pulse counting)
LEDs indicate the state of binary inputs and outputs
Note: CAN address 0 disables corresponding CAN message (Group data are not send).

IMPORTANT: Impulse inputs are not supported by the controller.
2.11 CAN Communication Modules

2.11.1 InteliGateway 300
IFG is communication gateway with configurable interfaces between Modbus TCP/RTU, ComAp CAN,
WebSupervisor and InteliScada protocols allowing user-defined interconnection of all attached devices. See
more information on web page InteliGateway.
Bidirectional connectivity of 3rd party Modbus devices to ComAp
controllers
Data buffering capability for avoiding loss of data during
connectivity outage
Inbuilt support of energy industry Modbus controlled devices
such as Inverters, BESS, from leading manufacturers
Support for customizable user templates for any additional
Modbus devices that are not inbuilt
Dual ethernet interfaces decoupling trusted (private) and
untrusted (public) network segments for enhanced cyber security
Terminals: 2x Ethernet, 2x RS485, 3x CAN
2.11.2 I-CR
If the distance between units is too high to fit into the 200 m limit (or 900 m for 8 controllers), CAN repeater
module (I-CR) can be used to extend it. See more information on web page I-CR.
Intercontroller CAN bus repeater

Supported CAN modes: CAN8C and CAN32C
CAN bus redundancy
One or more I-CR modules can be used
Intercontroller CAN bus bus-tie bridging - makes groups of controllers
in CAN segments A and B "invisible" one for another depending on
bus-tie breaker state
2.12 Virtual modules

Note: The protection for all virtual modules' values is working only if the User protection is set for the specific
bit of the virtual module. If the protection is set and communication with virtual module is lost, all bits with user
protection will show ####.

Note: When communication with any virtual module is lost the behavior of the value is defined according to
the setpoint Fail Safe Binary State (page 380).
2.12.1 Distributed modules

DIST-IN
DIST-IN virtual modules receives binary and analog values from other controllers via CAN Intercontroller
Communication (page 132). There are 64 modules, DIST-IN 1 to DIST-IN64, which are firmly connected with
CAN Controller Address (page 385).
IMPORTANT: This means that if you need to receive data from Controller Unit with CAN Controller
Address (page 385) = 5, you need to use module DIST-IN 5.
Proper alarm from a range DISTIN 01 (page 1159) to DISTIN 64 (page 1174) is activated in case that data are
not received from the Controller Unit.
Binary Inputs
32 binary states are paired by eight to two shared values:
Binary inputs 1 1-8 (page 832)
Note: Values above are related to virtual module DIST-IN 1. See values for other modules here:
GROUP: DIST-IN 1-32 (PAGE 832)
IMPORTANT: Binary inputs X 9-16 and higher can be shared only if CAN Intercontroller Comm Mode
(page 389) = 64C CAN FD or 32C CAN FD or 8C CAN FD.
Analog Inputs
Up to 4 analog values are shared:
DISTAIN-1 1 (page 834)
Note: Values above are related to virtual module DIST-IN 1. See values for other modules here:
IMPORTANT: Analog values can be shared only if CAN Intercontroller Comm Mode (page 389) = 64C
CAN FD or 32C CAN FD or 8C CAN FD.
Note: If the CAN communication is lost, the DIST-IN analog inputs become invalid and the values are shown as
'####'.
Configuration
Configuration of the virtual module itself, binary and analog outputs is done via InteliConfig. As with other
modules, you can choose whether history columns and display screens are added as well as select type of

protection upon module failure.
Image 2.2 Configuration of virtual module DIST-IN
DIST-OUT
This virtual module shares binary and analog values to other controller units via CAN Intercontroller
Communication (page 132).
In case that there is detected module failure, alarm DISTOUT (page 1175) is activated. The CAN connection is
lost with another CU or this module is not configured.
Binary Outputs
32 binary states are paired by eight to four shared values:
Binary outputs 1-8 (page 854)
IMPORTANT: Binary outputs 9-16 and higher can be shared only if CAN Intercontroller Comm Mode
(page 389) = 64C CAN FD or 32C CAN FD or 8C CAN FD.
Analog Outputs
Up to 4 analog values can be shared.
IMPORTANT: Analog values can be shared only if CAN Intercontroller Comm Mode (page 389) = 64C
CAN FD or 32C CAN FD or 8C CAN FD.
Configuration
Configuration of the virtual module itself, binary and analog outputs is done via InteliConfig. As with other
modules, you can choose whether history columns and display screens are added as well as select type of
protection upon module failure.

Image 2.3 Configuration of virtual module DIST-OUT
2.12.2 Shared modules

Shared modules are not connected with CAN Controller Address (page 385), which means that you need to
pay close attention during configuration so that you do not create collision. Each SHBOUT and SHAOUT module
index can be used only once in CAN topology.
Binary shared modules

SHBIN
SHBIN virtual modules receives binary values from other controllers via CAN Intercontroller Communication
(page 132). There are 6 modules, SHBIN-1 to SHBIN-6, which are firmly connected with SHBOUT-1 to
SHBOUT-6.
IMPORTANT: This means that you need to use module SHBIN-1 if you wish to receive data from
SHBOUT-1.
An alarm Wrn SHBIN Collision (page 1183)- is activated in case that more than just one controller has
configured SHBOUT module with same module index in CAN topology.
IMPORTANT: Shared modules work only if CAN Intercontroller Comm Mode (page 389) = 8C, 16C or
32C.
Proper alarm from a range SHBIN 1 (page 1181) to SHBIN 6 (page 1183) is activated in case that data are not
received.
Binary Inputs
SHBIN-1 (page 846)
Note: Value above is related to virtual module SHBIN-1. See values for other modules here: Group: SH
Modules (page 846)

Configuration
Image 2.4 Configuration of shared module SHBIN
SHBOUT
SHBOUT virtual modules share binary values to other controllers via CAN Intercontroller Communication
(page 132). There are 6 modules, SHBOUT-1 to SHBOUT-6, which are firmly connected with SHBIN-1 to
SHBIN-6.
IMPORTANT: This means that you need to use module SHBOUT-1 if you wish to send data to SHBIN-
1.
32C.
Binary Outputs
SHBOUT-1 (page 849)
Note: Value above is related to virtual module SHBIN-1. See values for other modules here: Group: SH
Modules (page 846)

Configuration
Image 2.5 Configuration of shared module SHBOUT
Analog shared modules

SHAIN
SHAIN virtual modules receives analog values from other controllers via CAN Intercontroller Communication
(page 132). There are 2 modules, SHAIN-1 and SHAIN-2, which are firmly connected with SHAOUT-1 and
SHAOUT-2.
IMPORTANT: This means that you need to use module SHAIN-1 if you wish to receive data from
SHAOUT-1.
An alarm Wrn SHAIN Collision (page 1181) is activated in case that more than just one controller has
configured SHAOUT module with same module index in CAN topology.
32C.
Proper alarm from a range SHAIN 1 (page 1181) to SHAIN 2 (page 1181) is activated in case that data are not
received.
Analog Inputs
SHAIN-1 1 (page 852)
Note: Value above is related to virtual module SHAIN-1. See values for other modules here: Group: SH
Modules (page 846)

Configuration
Image 2.6 Configuration of shared module SHAIN
SHAOUT
SHAOUT virtual modules share analog values to other controllers via CAN Intercontroller Communication
(page 132). There are 2 modules, SHAOUT-1 and SHAOUT-2, whicha re firmly connected with SHAIN-1 and
SHAIN-2.
IMPORTANT: This means that you need to use module SHAOUT-1 if you wish to send data to SHAIN-
1.
32C.

Configuration
Image 2.7 Configuration of shared module SHAOUT
6 back to System overview

3 Applications overview
3.1 SPTM 41
3.2 MINT 42

3.1 SPTM
The typical scheme of a Microgrid Parallel To Mains application is shown below. The InteliNeo6000 controller
controls up to three breakers – a mains breaker, battery energy storage system breaker and a photovoltaic
(renewable source) breaker. Feedback from all breakers is required.
Note: The Application & System Variability (page 233) allows user to configure the system in following
variants: BESS only, PV (renewables) only, or BESS + PV (renewables).
IMPORTANT: In the MPTM scheme dashed line at BCB breaker is for AC precharge and full line is
for DC precharge.
Image 3.1 Microgrid Parallel To Mains application

3.2 MINT
The typical scheme of Multiple Island-Parallel application for on grid is shown below. The cooperation of
Microgrid, Gen-set, and Mains controllers can be seen in the picture below. The InteliNeo6000 controller
controls up to two breakers, the battery energy storage system breaker and photovoltaic (renewable source)
breaker. Feedback from the both breakers is required.
Note: The Application & System Variability (page 233) allows user to configure whether the microgrid
contains BESS, PV (renewables), Gen-sets or Mains.
IMPORTANT: The InteliNeo6000 can work together with multiple Gen-set and Mains controllers,
but it cannot work with any other Microgrid/BESS controller. Only one InteliNeo6000 per site is
supported.
IMPORTANT: In the MINT scheme dashed line at BCB breaker is for AC precharge and full line is
for DC precharge.

Image 3.2 Multiple island-parallel application with mains
6 back to Applications overview

4 Installation and wiring
4.1 Package content 44
4.2 Controller installation 45
4.3 Terminal Diagram 47
4.4 Recommended wiring 49
4.5 External display 79
4.6 Maintenance 81
4.1 Package content

The package contains:
Controller InteliNeo6000
Terminal blocks
Note: The package does not contain a communication or extension modules. The required modules should be
ordered separately.

4.2 Controller installation
4.2.1 Dimensions
Image 4.1 Controller dimensions
Note: Dimensions are in millimeters.
Note: The controller is mounted into panel doors as a standalone unit using provided holders. The requested
cutout size is 187 × 132 mm. Use the screw holders delivered with the controller to fix the controller into the
door.
4.2.2 Mounting
The controller unit should be mounted onto the backside of the switchboard door and after the installation it
should be inaccessible for nonauthorized people. There are two ways how to mount the CU.

Mounting on DIN rail
Mount the controller on the DIN rail as described on the picture below.
Image 4.2 Controller mounting on DIN rail
Mounting in switchboard doors

The upper part of the back side of the controller cover is not same as the lower part, the spacers have to be
placed between switchboard doors and the controller cover. Use the 10 mm spacers for the upper part of the
CU cover and the 5 mm spacers for the lower part of the CU cover. Use the screws and spacers to fix the
controller into the door as described on the picture below.
Image 4.3 Controller mounting in the switchboard doors

4.3 Terminal Diagram
46 N 65 BI1 89 H
① 47 L1 66 BI2
⑧ 88 COM
BESS CAN2A
48 L2 67 BI3 87 L
VOLTAGE
49 L3 68 BI4 86 H
50 N 69 BI5
⑨ 85 COM
② 51 L1 ⑥ 70 BI6
CAN1B
84 L
MAINS/BUS BINARY
52 L2 71 BI7 83 H
VOLTAGE
53 L3
INPUTS
72 BI8
⑩ 82 COM
CAN1A
58 AO1 COM 73 BI9 81 L
③④ 59 AO1 OUT 74 BI10 E1 Ethernet 1
ANALOG
60 AO2 COM 75 BI11
⑪⑫⑬ E2 Ethernet 2
OUTPUTS ETHERNET
61 AO2 OUT 76 BI12 E3 Ethernet 3
92 H
⑤ SD SD Card
⑦ 91 COM
⑭ U1 USB
SD Card CAN2B USB
90 L

93 B 31 AI4 16 BO12
⑮ RS 485 94 COM ⑱ 30 AI3 15 BO11
95 A ANALOG 29 AI2 14 BO10
45 L1k INPUTS 28 AI1 13 BO9
44 L1l 27 ACOM 12 BO8
⑯ 43 L2k 11 BO7
⑲ 26
+5V
㉒ BINARY
BESS
42 L2l +5V SENSOR SENSOR 10 BO6
CURRENT OUTPUTS
41 L3k ⑳ 09 BO5
40 L3l GROUNDING 00 GROUND 08 BO4
07 BO3
39 LAk
03 + 06 BO2
⑰ AUX
02 D+ 05 BO1
CURRENT ㉑ POWER
38 LAl E-
SUPPLY, D+ 01 - ㉓ E-STOP 04
STOP

4.4 Recommended wiring
4.4.1 General 51
4.4.2 Grounding 51
4.4.3 Power supply 52
4.4.4 Measurement wiring 53
4.4.5 Binary Inputs 65
4.4.6 Binary Outputs 66
4.4.7 E-Stop 67
4.4.8 Analog Inputs 67
4.4.9 Analog Outputs 70
4.4.10 CAN bus and RS485 wiring 71
4.4.11 USB 74
4.4.12 Ethernet 75
4.4.13 Cellular Connection 76
max 600 V
BESS voltage inputs Voltage measurement wiring (page 57)
AC Ph-Ph
max 600 V
Mains/Bus voltage inputs Voltage measurement wiring (page 57)
AC Ph-Ph
max ± 10 V
Analog Output Analog Outputs (page 70)
DC
max ± 10 V
Analog Output Analog Outputs (page 70)
DC

SD card slot
max 36 V
Binary inputs Binary Inputs (page 65)
DC
CAN2B H, COM, L CAN bus and RS485 wiring (page 71)
CAN2A H, COM, L CAN bus and RS485 wiring (page 71)
CAN1B H, COM, L CAN bus and RS485 wiring (page 71)
CAN1A H, COM, L CAN bus and RS485 wiring (page 71)
Ethernet 1 ETH 1 Ethernet (page 75)
USB USB (page 74)
RS485 A, COM, B CAN bus and RS485 wiring (page 71)
BESS current max 5 A AC Current measurement wiring (page 53)
Aux current max 5 A AC Current measurement wiring (page 53)
max 10 V
Analog inputs Analog Inputs (page 67)
DC
5 V DC
Sensor power supply max 100
mA
+, N/A, -
Power supply 8 - 36 V DC Power supply (page 52)
max 7,5 A
Improves resistance to electrical interference if
Grounding
connected to the ground.
max 36 V;
Binary outputs Binary Outputs (page 66)
0,5 A
E-stop max 1 A E-Stop (page 67)

4.4.1 General
To ensure proper function:
Use grounding terminals.
Wiring for binary inputs and analog inputs must not be run with power cables.
Analog and binary inputs should use shielded cables, especially when the length is more than 3 m.
Tightening torque and allowable wire size and type for the Field-Wiring Terminals:
For BESS Voltage and Mains Voltage terminals
Specified tightening torque is 0.5 Nm (4.425 In-lbs).
Use only diameter 2.0 - 0.5 mm (12 - 26 AWG) copper

conductor rated for 90 °C minimum.
For Current terminals

For other controller field wiring terminals

4.4.2 Grounding
2
The shortest possible length of wire should be used for controller grounding. Use cable min 2.5 mm .
The negative " - " battery terminal used as power supply for CU must be properly grounded.
Switchboard must be grounded at common point. Use as short cable as possible to the grounding point.

4.4.3 Power supply
To ensure proper function:
Use power supply cable min. 1.5 mm2
Maximum continuous DC power supply voltage is 36 V DC
Minimum continuous DC power supply voltage is 8 V DC
It is strongly recommended to use 8 A fusing (12xBOUT 0.5 A)
The controller’s power supply terminals are protected against large pulse power disturbances. When there is a
potential risk of the controller being subjected to conditions outside its capabilities, an outside protection device
should be used.
Note: The controller should be grounded properly in order to protect against lighting strikes. The maximum
allowable current through the controller’s negative terminal is 4 A (without consumption of the binary outputs).
The controller includes internal capacitors that allows the controller to continue in operation if the voltage dip
occurs. The capacitors are useful mainly during short cranking voltage dips for the connections with 12 V battery
power supply. If the voltage dip goes during cranking to 0 V and after 50 ms it recovers to 8 V, the controller
continues operating. When this situation occurs the binary outputs are temporarily switched off and after
recovering to 8 V back on. This cycle can be repeated several times.
Note: It is also possible to further support the controller by connecting the external capacitor and separating
diode. The capacitor size depends on required time. It shall be approximately thousands of μF. The capacitor
size should be 5 000 μF to withstand 150 ms voltage dip under following conditions: Voltage before dip is 12 V,
after 150 ms the voltage recovers to min. allowed voltage, i.e. 8 V.
Image 4.4 Controllers power supply with external capacitor, separating diode and fusing

IMPORTANT: It is strongly recommended to use fusing in-line with the battery positive terminal to
the controller and modules.
Note: Suitable conductor protection shall be provided in accordance with NFPA 70, Article 240.
Power supply fusing

It is strongly recommended to use 4 A fuse in-line with the battery positive terminal to the controller and modules.
These electronics should never be connected directly to the starting battery. Fuse value and type depends on
number of connected devices and wire length. It is recommended to use slow blow fuse T4 A. The fast blow fuse
is inappropriate due to internal capacitors charging during power up.
Image 4.5 Controllers power supply fusing
IMPORTANT: 8 A fuse is calculated without BOUT consumption nor extension modules. Real value
of fuse depends on consumption of binary outputs and modules.
Example: Maximal consumption of binary outputs can be 22 A

2 x 10 A on high current outputs (for 10 seconds)
2 A on all others binary outputs
4.4.4 Measurement wiring

2 2
Use 1.5 mm cables for voltage connection and 2.5 mm for current transformers connection. Adjust Connection
type (page 371), Mains/Bus Nominal Voltage Ph-N (page 373), Mains/Bus Nominal Voltage Ph-Ph (page
374), BESS Nominal Voltage Ph-N (page 373), BESS Nominal Voltage Ph-Ph (page 373) and Nominal
Current (page 369) by appropriate setpoints in the Basic Settings group.
IMPORTANT: Risk of personal injury due to electric shock when manipulating voltage
terminals under voltage. Be sure the terminals are not under voltage before touching
them.
Do not open the secondary circuit of current transformers when the primary circuit is
closed. Open the primary circuit first.
Current measurement wiring

The number of CT's is automatically selected based on selected value of setpoint Connection type (page 371).
Current and power measurement is suppressed if current level is bellow 1 % of CT range.
The auxiliary current measurement (T38, T39) is used for the Mains/Bus measurement.

ConnectionType: 3Ph4Wire / High Leg D / 3Ph3Wire
Connection type (page 371) = 3Ph4Wire / High Leg D / 3Ph3Wire
Image 4.6 BESS current measurement Image 4.7 AUX Mains/Bus current measurement
wiring wiring
ConnectionType: SplitPhase
Connection type (page 371) = SplitPhase
wiring wiring

ConnectionType: MonoPhase
Connection type (page 371) = MonoPhase
wiring wiring
Principle of two transformers measuring for 3 phase connections
Image 4.12 Principle of two current transformers measuring

IMPORTANT: Check measurement connections carefully! Failure is possible if phases are
connected in wrong order (WrongPh Sequence detected by the controller) but this is not
detected if the phases are just rotated (i.e. instead of phase sequence L1, L2, L3, phase
sequence is e.g. L2, L3, L1.
EFC measurement wiring

The auxiliary current measurement (T38, T39) is used for the Earth Fault Current measurement.

Simple earth fault current measurement wiring
The simple earth fault current arrangement covers all zones from the BESS inverter to the final circuits in the load
network.
Image 4.13 AUX Simple EFC measurement wiring
EFC measurement wiring for load network only

This arrangement covers earth faults in the load network only.
Image 4.14 AUX EFC measurement wiring for load network only

EFC measurement wiring for restricted earth protection
This arrangement is necessary for restricted earth fault protection. The location of the neutral earthing point in
relation to the protection current transformers in the neutral conductor determines whether four or five current
transformers are employed.
Image 4.15 AUX EFC measurement wiring for restricted earth protection
Voltage measurement wiring

The BESS and Bus protections are evaluated from different voltages based on Connection type (page 371)
setting:
3Ph4Wire – Ph-Ph voltage, Ph-N voltage
High Leg D – Ph-N voltage, Ph-N voltage
3Ph3Wire – Ph-Ph voltage
SplitPhase – Ph-N voltage, Ph-N voltage
MonoPhase – Ph-N voltage

ConnectionType: 3 Phase 4 Wires
Connection type (page 371) = 3Ph4Wire
Image 4.16 Controller wiring for voltage measurement of 3 phase application with neutral
Note: Fuse on "N" wire is not obligatory but recommended.
Image 4.17 Typical BESS wiring of 3 phase application with neutral
Note: Terminals marked by Tx in the picture above are BESS's terminals. These markers are not the same
as markers for the controller wiring.

ConnectionType: High Leg D
Connection type (page 371) = High Leg D
Image 4.18 Controller wiring for voltage measurement of High Leg Delta application
Table 4.1 Typical BESS wiring of High Leg Delta application

ConnectionType: 3 Phase 3 Wires
Connection type (page 371) = 3Ph3Wire
Image 4.19 3 Controller wiring for voltage measurement of 3 phase application without neutral
Image 4.20 Typical BESS wiring of 3 phase application without neutral

ConnectionType: SplitPhase
Connection type (page 371) = SplitPhase
Image 4.21 Controller wiring for voltage measurement of SplitPhase application

Image 4.22 Typical BESS wiring of SplitPhase application
Note: Terminals marked by Tx in the pictures above are BESS's terminals. These markers are not the same

ConnectionType: Mono Phase
Connection type (page 371) = MonoPhase
Image 4.23 Controller wiring for voltage measurement of MonoPhase application

Image 4.24 Typical BESS wiring of MonoPhase application
Principle of two transformers measuring for 3 phase connections
Image 4.25 Principle of two voltage transformers measuring

4.4.5 Binary Inputs
InteliNeo 6000 offers switchable types of inputs. You can select from Pull Up and Pull Down settings. Use
2
minimally 1 mm cables for wiring of Binary inputs. It is recommended to separate inputs by diodes when two or
more binary inputs are connected in parallel to avoid wrong input activation when one controller is switched off.
See the chapter Binary inputs (page 1191) for more information about Pull Up and Pull Down settings.
Note: The name and function or alarm type for each binary input have to be assigned during the
configuration.
Image 4.26 Wiring binary inputs - Pull Up Image 4.27 Wiring binary inputs - Pull Down
Image 4.28 Separation of connected binary inputs by diodes

4.4.6 Binary Outputs
2
Use min. 1 mm cables for wiring of binary outputs. Use external relays as indicated on the schematic below for
all outputs except those where low-current loads are connected (LED signalization etc.). There are two Binary
Output groups, the first one is powered by E-STOP (BO1 and BO2) and second one is powered by the controllers
main power supply connector (BO3 .. BO12). Every group of outputs can provide steady current of up to 2 A.
Every single binary output can provide up to 0.5 A of steady current unless the total current of the group of
outputs does not exceed 2 A.
IMPORTANT: Use suppression diodes on all relays and other inductive loads even if they are not
connected directly to the controller Binary Outputs.
Image 4.29 Binary outputs wiring

4.4.7 E-Stop
The E-Stop is commonly used for quick emergency stop of the BESS. It has dedicated terminal T04 which
should be wired trough the Emergency Stop button to the battery voltage. The E-Stop is also used as power
supply for binary output 1 (T05) and binary output 2 (T06). . So, these binary outputs will not work if the E-Stop
is not powered up, that means higher security and faster disconnection of these outputs. For more information
about E-Stop functions see chapter E-STOP (page 143).
Image 4.30 E-Stop wiring
Note: Recommended fusing is 1 A fuse.
Note: Grey dashed line symbolizes internal connection between E-Stop and binary outputs 1 and 2.
Note: For proper functionality of E-Stop, the terminal T04 must be always wired. Terminal can be connected
to battery+ or to terminal T03 (BATT+)
IMPORTANT: Use suppression diodes on all relays and other inductive loads even if they are not
connected directly to the controller Binary Outputs.
4.4.8 Analog Inputs

On each analog input there is possibility to connect a voltage, current, or resistive sensor.
Resistive sensors
The analog inputs for resistive automotive type sensors like VDO or DATCON are connected either by one wire
(the second pole is the sensor body) or by two wires.
In the case of grounded sensors, connect the ACOM terminal to the ground as near to the sensors as
possible.
In the case of isolated sensors, connect the ACOM terminal to the negative power supply terminal of the
controller as well as one pole of each sensor.

Image 4.31 Grounded sensors Image 4.32 Isolated sensors
Note: Schemes show only analog input connection overview, not actual wiring.
Note: The name, sensor characteristic and alarm types for each analog input have to be assigned during
configuration.
Voltage sensors
Recommended wiring for the voltage measurement with voltage divider. The voltage sensor is displayed as
voltage source which is usually powered from battery or any external DC power source. The ACOM terminal is
connected to the negative power supply terminal of the controller as well as negative pole of each sensor.
Image 4.33 Wiring of analog input with voltage sensor
Note: The voltage divider is only relevant for sensors which are outside the 0-10 VDC range.
Current sensors
Recommended wiring connections for the active and passive current sensors. The active sensor is displayed as
current source which is usually powered from battery or any external DC power source. The passive sensor is
displayed as resistive load which is placed between battery + and AIN. The passive sensor does not require
additional power supply.

Image 4.34 Wiring of analog input with active Image 4.35 Wiring of analog input with passive
current sensor current sensor
Analog as binary or tristate inputs

Analog inputs can be used also as binary or tri-state, i.e. for contact sensors without or with circuit check. The
threshold level is 750 Ω. In the case of tri-state, values lower than 10 Ω and values over 2500 Ω are evaluated as
sensor failure (short or open circuit), values over 750 Ω are evaluated as log 0 and values below 750 Ω are
evaluated as log 1. This can be used for example to prevent running the engine with failed temperature sensor,
so it wont be overheated.
Image 4.36 Analog inputs as tristate Image 4.37 Analog inputs as binary
Note: The name, sensor characteristic and alarm types for each analog input have to be assigned during
configuration.

Curve of tristate sensor is prepared for resistive analog inputs 0 .. 2500 Ω.
Tristate sensor has 3 states:
Fls – fail of sensor
1 – value is in logical 1
0 – value is in logical 0
Curve of sensor:
< 10 Ω – fail of sensor
10 .. 750 Ω – logical 1
750 .. 2500 Ω – logical 0
> 2500 – fail of sensor
4.4.9 Analog Outputs
Image 4.38 Analog outputs - Wiring
Analog outputs can be used for any purpose and their outputs can be switched according to options below.
Note: The jumper switch next to the terminal 61 is a short switch of 10k serial resistor at analog output 2. By
default, the jumper is switched off (the resistor is included in the circuit).
Voltage
Output range: -10 to +10 V
Maximum load: 5 mA
Output accuracy: 1 % from set value ±100 mV (measured at load 10 kΩ)
Minimum step: 1/10000 of full range (approx. 14bit resolution)
Step response: 10 ms max. (measured between 10 and 90 %)
Output ripple: 30 mV max. (measured at 50% duty cycle at 3000 Hz PWM)
Current
Output range -20 to +20 mA
Maximum load: 500 Ω
Output accuracy: 1 % from set value ±200 µA

Step response: 10 ms max. (measured between 10 and 90 %)
Output ripple: 60 µA max. (measured at 50% duty cycle at 3000 Hz PWM)
PWM
Output voltage levels: 0 V / 5 V
Maximum load: 10 mA
Output High level: >4 V @ 10 mA
Output Low level: <1 V @ 10 mA
Frequency range: 500 to 3000 Hz (settable during configuration)
4.4.10 CAN bus and RS485 wiring

CAN bus wiring
The wiring of the CAN bus should be provided in such a way that the following rules are observed:
The maximum length of the CAN bus depends on the communication speed. For a speed of 250 kbps,
which is used on the CAN1A (page 19) bus (extension modules, ECU) and CAN2A (page 19) (CAN2B
(page 19)) bus, the maximum length is 200 m.
The bus must be wired in linear form with termination resistors at both ends. No nodes are allowed except
on the controller terminals.
Shielded cable1 has to be used, shielding has to be connected to the terminal T01 (Grounding).
External units can be connected on the CAN bus line in any order, but keeping line arrangement (no tails,
no star) is necessary.
The CAN bus has to be terminated by 120 Ohm resistors at both ends use a cable with following
parameters:
Cable type Shielded twisted pair

Impedance 120 Ω
Propagation velocity ≥ 75% (delay ≤ 4.4 ns/m)
2
Wire crosscut ≥ 0.25 mm
Attenuation (@1MHz) ≤ 2 dB/100 m
Note: Communication circuits shall be connected to communication circuits of Listed equipment.
Note: A termination resistor at the CAN (120 Ω) is already implemented on the PCB. For connecting, close the
jumper near the appropriate CAN terminal.
1Recommended data cables: BELDEN (http://www.belden.com) - for shorter distances: 3105A Paired - EIA
Industrial RS-485 PLTC/CM (1x2 conductors); for longer distances: 3106A Paired - EIA Industrial RS-485
PLTC/CM (1x2+1 conductors)

Image 4.39 CAN bus topology
Image 4.40 CAN bus wiring for shorter distances
Note: Shielding shall be grounded at one end only. Shielding shall not be connected to CAN COM terminal.
Note: In case of surge hazard (long distances, connection out of building, storms, etc.), consider using surge
protection1.
RS485 wiring
The wiring of the RS485 communication should be provided in such a way that the following rules are observed:
Note: A termination resistor at the RS485 (120 Ω) is already implemented on the PCB. For connecting, close the
jumper near the RS485 terminal.
Standard maximum bus length is 1000 m.

Shielded cable2 has to be used, shielding has to be connected to the terminal T00 (Grounding).
External units can be connected on the RS485 line in any order, but keeping line arrangement (no tails, no
star) is necessary.
The line has to be terminated by 120 Ohm resistors at both ends.
1Protections recommended: Phoenix Contact (http://www.phoenixcontact.com): PT 5-HF-12DC-ST with PT2x2-

BE (base element) or Saltek (http://www.saltek.cz): DM-012/2 R DJ
2Recommended data cables: BELDEN (http://www.belden.com) - for shorter distances: 3105A Paired - EIA
Industrial RS-485 PLTC/CM (1x2 conductors); for longer distances: 3106A Paired - EIA Industrial RS-485
PLTC/CM (1x2+1 conductors)

For shorter distances (connection within one building).
Image 4.41 RS485 wiring for shorter distances
For longer distances or in case of surge hazard (connection out of building, in case of storm etc.)
Image 4.42 RS485 wiring for longer distances
① Recommended PT5HF-5DC-ST1
Note: Communication circuits shall be connected to communication circuits of Listed equipment.
1Recommended protections: Phoenix Contact (http://www.phoenixcontact.com): PT 5-HF-5DC-ST with PT2x2-

BE (base element)(or MT-RS485-TTL) or Saltek (http://www.saltek.cz): DM-006/2 R DJ

On board RS485 description
Balancing resistors
The transmission bus into the RS-485 port enters an indeterminate state when it is not being transmitted to. This
indeterminate state can cause the receivers to receive invalid data bits from the noise picked up on the cable. To
prevent these data bits, you should force the transmission line into a known state. By installing two 560 Ohm
balancing resistors at one node on the transmission line, you can create a voltage divider that forces the voltage
between the differential pair to be less than 200 mili-Volts, the threshold for the receiver. You should install these
resistors on only one node. The figure below shows a transmission line using bias resistors. Balancing resistors
are placed directly on the PCB of controller. Use jumpers PULL UP/PULL DOWN to connect the balancing
resistors.
Image 4.43 Balancing resistors
Image 4.44 RS485 on board
4.4.11 USB
The USB can be used for direct computer connection. Use the shielded USB A-B cable. See the chapter
Connection via USB (page 306) for more information.
Image 4.45 USB connection
The USB cannot be used instead of power supply. The controller will not be turned on when the USB is
connected and the controller is not powered from power supply.

4.4.12 Ethernet
Ethernet Cat5/Cat6 cable fitted with the RJ45 connector can be connected to the ethernet interface. The
ethernet can be used for direct computer connection. See the chapter Connection via Ethernet (page 307)
for more information.
Image 4.46 Ethernet Connection
IMPORTANT: The InteliNeo6000 is using same MAC address for all Ethernet ports so it is not
possible to use more than one Ethernet port in the same network. If you connect for example
Ethernet 1 and 2 to the same network the communication will breakdown.
In the image below you can see the topology using all 3 Ethernet ports with one Modbus Client. The ETH1 is
used for connection of displays (IV5.2) or it can be also used for remote LAN connection. The ETH2 is used
for remote connection using the internet (WAN). The ETH3 is used for Modbus Server and Client which are
connected to the LAN with Modbus Devices.
Image 4.47 Advanced Ethernet Topology With One Modbus Client

In the image below you can see the topology using all 3 Ethernet ports with multiple Modbus Clients (CU 1 is
the first level client, CU 2 and CU 3 are second level clients). The ETH1 is used for Modbus Server,
connection of displays (IV5.2), or it can be also used for remote LAN connection. The ETH2 is used for
remote connection using the internet (WAN). The ETH3 is used for Modbus Clients which are connected
between CU 1 and other CUs, and between other CUs and Modbus Devices.
Image 4.48 Advanced Ethernet Topology With Multiple Modbus Clients
Note: The IP address of each device in the same network must vary.
Note: InteliVision 5.2 is used for illustrative purposes, the same wiring diagrams apply for all supported displays
mentioned in Displays (page 23).
4.4.13 Cellular Connection

Cellular connection of controllers can be created by using a router, which is a device that represents the
gateway between the controllers and the Internet.
It creates a Local Area Network (LAN) in which the controllers are connected
On the opposite side it is connected to Internet (Wide Area Network, WAN)

Image 4.49 Example of a topology
Note: The picture above is only an example of the topology. An additional switch/switches may be needed to
match the required network topology (i.e. number and location of the LAN connection points). Please consult
this topic with ethernet network specialist.
While selecting a suitable cellular router following aspects should be considered:

What cellular network technology and frequency bands are available in the target region?
Is the cellular connection the primary Internet connection or just a backup connection while the primary
one is wired ethernet?
Power supply and operating conditions
Note: We recommend to only use devices designed for industrial applications.

Cellular network technology
There are multiple cellular technologies available on the market. They are called either as "generations" (G)
or abbreviations are used.
Technology Description
Current, most advanced, technology. It is being deployed rapidly in some
areas it may replace the legacy 2G networks. We recommend using this
4G (LTE) technology if it is available in the target area
Provides highest data throughput rate and lowest latency
Best user experience – like a wired connection
Successor of 2G. It is in operation in some areas, but it is not expanding
anymore.
3G (UMTS, HSPA, CDMA)
Provides lower throughput rate and higher latency then 4G*
Still quite good user experience
Very first digital cellular network technology. It is still available in many
areas, however it is slowly starting to decline.
2G (GSM, GPRS, EDGE) Provides lowest throughput rate and quite high latency
Generally not suitable for connection of multiple ComAp devices
via a router
Frequency bands
It is very important that selected cellular router matches the frequency bands used by providers in the target
country or area. 4G networks worldwide use many of frequency bands and manufacturers of cellular modules
and routers sell their devices in multiple variants according to the region. A useful overview of LTE frequency
bands is available at Wikipedia page.
Note: Consult the technical documentation and/or technical support of the router's manufacturer to get more
information about ordering proper regional version of your selected router.
Additional router functions

Backup WAN connection
Router may provides secondary SIM card slot which is used as a backup connection when the main
connection is lost. You can also combine cellular and wired Internet connection as the main and backup one.
Connection alive check

Router may periodically checks whether the cellular connection is alive - has access to the Internet. When
there is not access to the Internet, router may perform automatic reboot to reinitialize the connection or switch
to backup SIM card.
Automatic scheduled reboot

Router may perform periodically scheduled reboot. This function is a bit "harder" alternative to the
Connection alive check (page 78).
Note: It may be very helpful at remote sites where freezing of the connection would require traveling to the
site.

Typical router configuration
Note: Please always refer to the documentation of the specific router for detailed setup procedure.
IMPORTANT: When configuring a router, the very first step to do should be changing the
username and password for administration access.
Cellular network
Usually the only setpoint that needs to be adjusted is the APN name. A frequent APN name is "internet", but if
you are not sure ask your SIM card provider for proper APN name.
WAN interface
If the router contains also ethernet socket for WAN connection it may be required to select cellular module as
the main WAN interface.
LAN setup
Most routers do not require any changes in the LAN configuration as their default configuration contains
DHCP server activated. Clients will get IP settings automatically.
Cellular router examples

Teltonika RUT955 – comprehensive industrial LTE router based on Linux and customized OpenWRT
distribution.
Gemalto ELS61T – industrial cellular modem with LTE router function based on Linux and OpenWRT
distribution.
4.5 External display

InteliNeo 6000 does not have an integrated display. External Remote Displays or PC Panel Displays are used
when needed. InteliNeo 6000 package does not include any external displays. External displays must be
acquired separately, see the chapter Displays (page 23).
4.5.1 InteliVision Displays

Wiring diagrams
IMPORTANT: Fixed IP address must be configured if the terminal is not connected to the DHCP
server.
For display connection it is recommended to use Ethernet 1 (trusted interface in default). Direct connection of
InteliVision display to InteliNeo 6000 via ethernet cable can be used only for connection of single device.
Using switch for connection allows you to connect multiple devices such as display, computer and Modbus to
InteliNeo 6000 at one time.

Image 4.50 Connection of InteliVision display to InteliNeo 6000
Image 4.51 Multiple connection to a single controller via switch

4.6 Maintenance
4.6.1 Backup battery replacement
The internal backup battery lifetime is approx. 6 years. If alarm Wrn RTC Battery Flat (page 1099) is present,
replacement of backup battery is needed. Follow these instructions:
Connect the controller to a PC and save an archive for backup purposes (not necessary but
recommended).
Disconnect all terminals from the controller and remove the controller from the switchboard.
Release the rear cover using a flat screwdriver or another suitable tool.
The battery is located in a holder on the circuit board. Remove the old battery with a small sharp
screwdriver and push with a finger the new battery into the holder.
Warning – Risk of fire if battery is replaced with incorrect type or polarity. Dispose of used batteries
according to instructions. The CR1632 3V Lithium battery have to be used."
Note: The picture above is only illustrative and actual battery placement may vary.
Put the rear cover back. Use slight pressure to lock the snaps into the housing. Pay attention that the
cover is in correct position and not upside down!
Put back the back cover.
Power the controller on, adjust date and time and check all setpoints.
6 back to Installation and wiring

5 Controller setup
5.1 Operator Guide 82
5.2 Controller configuration and PC tools connection 112
5.3 Default configuration 118
5.4 General Functions 119
5.5 Application related functions 231
5.1 Operator Guide

Note: This chapter is relevant only for users who want to use external displays. If you want to operate /
monitor / configure your site using the computer with installed PC tool see the chapter PC tools (page 22).
See the chapter Displays (page 23) if you want to use any PC panel display, for example with installed
InteliSCADA PC tool. In above mentioned chapters you can find links to Global Guide for each product.
5.1.1 InteliVision 5.2

Front panel elements 82
Page Structure 86
StartUp screen 88
Connecting to the controller 90
Login to the controller 91
Setpoints 94
Metering screens 101
Alarmlist 101
History 103
Trends 105
Administration 106
Basic operating modes description 111
Note: The images used in the Operator Guide are only illustrative. The screens shown in the images are
compatible with the InteliGen 1000 Controller, but the functionality of the IV 5.2 Display such as Connection,
Login, Setpoints Settings, Display Settings, etc. remains the same.
Front panel elements

Front panel of the unit uses hardware buttons for configuring, moving, scrolling, commands and other
functions.

Image 5.1 : Front panel overview
Navigation buttons
Arrow buttons on the front panel are mainly used for navigation inside the entire graphical user interface. In
addition the arrows left and right are used for changing the controller mode if the actual position is any
metering screen.
Arrow left and right
Image 5.2 : Arrow left and right
The buttons are used for :

Changing the controller mode (only on metering screens)
Movement between history columns
Movement in the dialogs
Arrow up and down
Image 5.3 : Arrow up and down

The buttons are used for :
Cyclical movement between the metering Screens
Movement in the dialogs
Changing the value in the dialogs
Movement in menus
Listing on pages
Enter
Image 5.4 : Enter button
The button is used for :

Confirming the values
Confirming the selections
Confirming the listing options
Menu
Image 5.5 : Menu button
The button is used for :

Escape function
Step back function
Cyclical change of the page (from any metering screen)
Function buttons
Function buttons are dedicated for the performing of the concrete function. By pressing the button the
controller action or controller command is performed (see bellow).
Image 5.6 : Function buttons (Start, Stop, Alarm/Horn reset, Horn reset)
Start : starting of the BESS

Stop : stoping of the BESS
Alarm/Horn reset : resets the horn and confirms all the alarms in the alarmlist
Horn reset : resets only the horn

User buttons
Image 5.7 : User button
User button is dedicated for predefined user function.

Performing the controller command
Jump to the specific page or metering screen
special function on the pages
Special and button combination

In this manual the shortcut is a term for the combination of the buttons or long press of the button.
+
Image 5.8 : Shortcut (jump to the administration)
Enter + Menu : performs the jump to the administration. Enter button has to be pressed first.
Long press of the arrow up or down button
in the menus : performs the cyclical listing
in the dialog : velocity of the changing value is increased
based on special algorithm
Status LED
There is one multicolor (RGB) LED on the front panel of the unit. The specified color and flashing function
describes the actual state of the unit.
Image 5.9 : Status LED
LED intensity is directly connected with the actual setting of the backlight intensity in Administration menu
"Settings" accessible by shortcut Enter + Menu
the intensity respects the value of the Manual or External brigness control
The flashing of the status LED and indicative Alarm icon in the top statusbar have the same period
Meaning of the status LED colors is described below

Priority LED State Description
Active unconfirmed level2 (shutdown) alarm
Inactive unconfirmed level2 (shutdown) alarm
1 Red is flashing
Lost of internal communication line
Controller unit in init state
Active confirmed level2 (shutdown) alarm
Display unit in init state
2 Red lights
Display unit booting procedure
Lost of communication line with controller unit
3 Cyan lights temperature inside the housing exceeded the 85°C (185°F)
Active unconfirmed level1 (warning) alarm
Inactive unconfirmed level1 (warning) alarm
Active confirmed level1 (warning) alarm
4 Yellow lights
Active unconfirmed fail sensor alarm
Inactive unconfirmed fail sensor alarm
Active confirmed fail sensor alarm
5 Green lights unit is running correctly without any errors or alarms
Page Structure
Pages
There are several screens called pages in the graphical user interface (GUI), which are accessible by
pressing the Menu button or concrete user button in the bottom status bar. Each page has a different function
and different structure. Pages are described in special chapters in this manual.
The actual GUI consists of 6 different pages :
Setpoints
Metering screen
Alarmlist
History
Trends
Administration
Page administration is accessible only by pressing the combination of the Enter and Menu buttons
from only Metering screen.
Screens
Each type of controller has special set of screens stored in the controller configuration. The description of the
each metering screens is by default predefined by ComAp. Scrolling between the screens is performed using
the arrow up and down buttons.
Note: The metering screens are adjustable using the Screen Editor (in InteliConfig). See chapter Screen
Editor for more information. The Screen Editor tool also has its own manual.

Status bars
Bottom status bar

The bottom status bar is used for the user button functions. There are several status bars in the GUI. Bottom
status bar consists of 5 areas (user buttons) dedicated for emitting the command to the controller unit (e.g.
MCB and BCB Close/Open), jump to the specified page (e.g. alarmlist, history) or special functions on some
pages.
Image 5.10 : Bottom status bar on Home metering screen
1. User button 1 - MCB Close/Open

2. User button 2 - BCB
3. User button 3 - Show Alarm List
4. User button 4 - Show History
5. User button 5 - Show Home Screen
Note: The button press is visually indicated by black frame around the button area. The indication does not
mean that requested command is performed, it is only press indication.
Note: Concrete status bar views for concrete page are described in specific chapters in this manual.
Note: Inactive buttons are visually indicated as grayed button. It means that the button is not available for any
reason (e.g. password protected button).
Top status bar

The top status bar can NOT be adjusted. Information in the top status bar is fixed and controlled by ComAp.
Image 5.11 Top Status Bar description

Image 5.12 : Top Status Bar - Mode selector dialog
1. Mode selector - Mode selector is dedicated for the controller mode selection. Using arrow left and right
the controller mode is changed (only on the metering screens). The choice must be always confirmed by
enter button. There is 5s timer for the automatic mode selector dialog cancellation. The mode selector
dialog can be also canceled by menu button.
2. Page title - Each page and each metering screen has its own title. The first number in square brackets
describes the actual metering screen position. The second number describes the total available number of
metering screens.
3. Trending - The icon is active when the trending is running. Icon is inactive when the trending is stopped.
4. USB Stick - The icon is active if the USB stick is plugged in the display unit. Icon is inactive if there is no
USB stick plugged in.
5. Access Lock - Access lock icon is active if the display is locked for security reasons. Icon is inactive if the
controller unit is not locked.
InteliNeo 6000 - the function in InteliNeo 6000 is connected to the specific user account. It means only
the user with sufficient rights can operate the controller or deactivate access lock function.
Icon ( - Single Lock) is displayed if the controller is locked and actually logged-in user is the lock
owner. User is able to operate the controller or to deactivate the access lock function.
Icon ( - Double Lock) is displayed if the controller is locked and actually logged-in user is NOT
the lock owner. Also the Access Lock function can not be deactived because of insufficient access
rights. See chapter Access Lock for more information.
6. PC connection - PC connection icon is not supported in InteliVision 5.2.
7. Alarm indication - The alarm icon is flashing red if there is at least one unconfirmed alarm (shutdown or
warning) in the alarmlist. The icon lights red if there is at least one confirmed active alarm and no
unconfirmed alarm in the alarmlist. The icon is inactive if the alarmlist is empty.
8. User - The user icon lights green if the user is logged in to the controller. The icon is inactive if the user is
logged out.
StartUp screen
The StartUp screen is defined in firmware and can not be adjusted. The screen is used as a default point in
user interface. The main purpose of the screen is to handle all the necessary messages from the display to

the user. If the StartUp screen is displayed it is possible to Import the new display firmware, to see the
InteliVision Info screen, to set new communication parameters or to set other display parameters.
StartUp screen is displayed :
during the booting procedure
if the connection with controller is not established or interrupted
Image 5.13 : StartUp screen
1. Init logo - Init screen logo

2. Status panel with message - see Messages table below for more info
green - if the device is running, initialization, controller programming
red - other than running state (communication error, connecting to the controller)
3. User button 1 - Import - Firmware Import
4. User button 2 - IV Info- InteliVision Info screen
5. User button 3 - Comm- Communication settings screen
6. User button 4 - Settings- Display settings screen
7. User button 5 - Login- Login to the controller
Inactive if comm. channel between display and controller is not established
Active if comm. channel between display and controller is established
Status panel message table
Message / color Message description

Running The device is running without any issue.
Initialize control unit Booting procedure and handshaking of internal processes.
Control unit is
Connected controller is programmed.
programmed
Detecting main CU
Internal communication error.
failed
Not compatible
Unsupported display or controller branch. Display and communication bridge
application branch in
are not compatible.
CU

Firmware is corrupted Display firmware or bootloader is corrupted.
Display does not support configuration in controller. Configuration reading
Unsupported
failed for any reason. Issues with controller configuration. Issues with display
configuration format
memory allocation for controller configuration.
Unsupported screen Display does not support screen format in controller configuration controller.
format Language identicator has not been found in controller configuration
Wrong configuration Issues with the content of the controller configuration. Corrupted content of
content controller configuration.
Controller unit is (has been) disconnected for any reason. Transition state
Disconnected
when the contoller unit is programmed.
Connecting Display tries to establish the secured communiction channel with controller.
Secured communication channel between display and controller is
Connected
established.
Controller
TCP/IP socket can not be created for any reason.
unreachable
Controller TCP/IP socket was established but the communication inside the socket does
identification timeout not run.
Controller
Display unit acquired unknown public key from the controller unit.
authentication failed
Secure connection
Secured connection with controller can not be established.
was not established
Attempt to login to the controller is refused. The wrong credentials has been
Wrong Credentials
inserted (Username, Passeword, UID or PIN)
Brute force protection. Controller is temporary blocked because of to many
Access Blocked
attempt of inccorect login.
Attempt for login using UID/PIN on untrasted interface. Only controlller
Wrong Interface
Ethernet 1 port accepts the login using UID and PIN.
Note: Connecting and connected state are marked red because at that moment the user is not logged in yet.
Login procedure is automatic to InteliNeo 6000 controller on StartUp screen (user with access rights 0 is
always loged in). Due to this fact the connecting and connected state are the transition states only on StartUp
screen.
Connecting to the controller

The procedure of connecting display to the controller slightly differ based on which Ethernet terminal is used. In
case of using Ethernet 1 (page 19) will not be required user login for connection and basic operations because
the terminal is considered as Trusted. Any other terminal is considered as Untrusted and before actual
connection user login is required.
Note: If display is not used (button is not pressed) for longer period, the user is logged out. This would cause
disconnection from the controller if an Untrusted terminal is being used.

1. Accept Unknown Certificate - Connection acceptation of the unknown devices (with unknown public
keys) or not supported branches.
a. Never (by default) - display unit never accepts the unknown devices.
b. Always - display unit always accepts the unknown devices.
2. IP Controller - IP address of the controller unit to be connected.
3. IP Port - IP port of the controller unit to be connected. Default IP Port is 23.
4. Address - Terminal Comm Address (page 385) of the controller.
5. IP Mode - there are two modes :
a. Automatic - display unit ethernet communication parameters are acquired automatically from the
DHCP server (which must exist in the network infrastructure).
b. Manual (by default) - display unit ethernet communication parameters are configured manually by
user.
6. IP InteliVision (by default 192.168.1.101) - The IP address of the display. Note that IP InteliVision
address and IP Controller address must be in the same network to establish the connection.
7. IP Subnet Mask (by default 255.255.255.0) - Mask of the network where the ethernet communication is
established.
8. IP Gateway (by default 192.168.1.101) - The gateway in network on which the packets are directed.
9. User button 1 : Connect - By pressing the button the communication automat is restarted to newly set
parameters. Until the button is not pressed the previous communictaion channel is still in progress.
Login to the controller

Login via Untrusted terminal
If an Untrusted terminal is being used, the display stays connected to the controller but awaits user login,
otherwise the controller does not provide any data. Login with an user to proceed to measurement screens.

Login via Trusted terminal
If the Trusted terminal is being used, the display automatically logs on to the controller with inbuilt user account
level 0. The measurement screens are immediately showed and an user login is required only for specific
functions which are set in configuration.
The group Password is not setpoint group. This Password item is manually placed to the first group position on
the program code level just for this controller unit.
Image 5.14 : Main Setpoints Page
Password item - the item dedicated for the login and logout to the controller.
Image 5.15 : Setpoints Password Page

Image 5.16 : Login Dialog
Currently Logged-in User - the information about actually logged in user or his ID if loged using ID and PIN.
Access Rights - Access rights of the actually logged in user
0 - user has access rights 0, which means "logged-out" user
0,1 - user has access rights 0 + 1 access rights
0,1,2 - user has access rights 0 + 1 + 2 access rights
0,1,2,3 - user has access rights 0 + 1 + 2 + 3, which means administrator rights
Login and Logout buttons
Login button calls the login dialog.
Logout button performs the logout action.
Enter Password
The dialog password is dedicated for password insertion. When the dialog is active the buttons arrow up and
down are used for number selection. Enter button confirms the option. Menu button cancels the dialog without
saving.
Image 5.17 : Dialog Password overview
Password Change
The dialog password change is dedicated for password change. When the dialog is active the buttons arrow
up and down are used for number selection. Enter button confirms the first option and the same password

must be inserted again. Enter button after insertion the second cell performs the password change (in case
the password are same). Menu button cancels the dialog without saving.
Image 5.18 : Dialog Password Change overview
Note: The user must be logged in with respective rights to be able to change password for respective rights.
Setpoints
The setpoint page is intended for setting the controller values. Each type of controller has specific setpoints to
be set. The setpoints also depend on the type of application like MPTMMCB and MINT. Availability of the
setpoint item also depends on configuration level settings in Administration page. Setpoint is set in 2 steps.
1st step - Setpoint group is selected using buttons arrow up and down and confirmed using enter button
Image 5.19 : Setpoints Page overview
1. Setpoints group - the column setpoint group displays the available groups based on the controller,
application type and configuration level settings. Respective setpoint group is selected using enter button.
2. Available setpoints in actually selected group - each setpoint group contains specific setpoints. The
informative column Setpoint name displays the available set of setpoints to be set in each Setpoint group.

This column is only informative and can NOT be set using the arrow left and right. The setpoint setting is
done using the 2nd step - see below.
2nd step - Setpoint item is selected using the buttons arrow up and down and the dialog for value setting is
called using the enter button. The dialogs are described in the chapter Dialogs.
Image 5.20 : Group Setpoints Page
1. Setpoint name - Setpoint is set using the enter button. Specific dialog is displayed and the value can be
set. There are several types of dialogs (text, numeric, stringlist) and the type of called dialog depends on
the setpoint type. The dialogs are described in the chapter Dialogs.
2. Actual value - Informative actual value for specific setpoint is displayed. Value range, original value and
default value for the selected setpoint are displayed inside the dialog.
Protected Setpoint Indication

If the setpoint is protected by password then the icon (crossed hand) is displayed just behind the setpoint
value. The setpoint protection is set using PC Tool InteliConfig.
Force Value Indication

If the setpoint is forced by another setpoint then the icon (double right arrow) is displayed just behind the
setpoint value.
Green Icon - Forcing is active
Grey Icon - Force Value is set to the specific setpoint and forcing is inactive

Image 5.21 : Force Value and Protected Setpoint Indication
IMPORTANT: If the controller is locked (Access Lock function is active) then the attempt for
setpoint editation is denied and the information dialog is displayed (Controller is Locked). See
chapter Administration and Access Lock.
Numeric change
Value
The dialog value is dedicated for number setting. When the dialog is active the buttons arrow up and down are
used for number selection. Enter button confirms the option. Menu button cancels the dialog without saving.
Image 5.22 : Dialog Value overview
Value Extended
The dialog value extended is dedicated for number setting with combination with one or more string value.
When the dialog is active the buttons arrow up and down are used for number/item selection. Enter button
confirms the option. Menu button cancels the dialog without saving.

Image 5.23 : Dialog Value Extended overview
IP address
The dialog IP address is dedicated for IP address insertion. When the dialog is active the buttons arrow up
and down are used for number selection. Arrows left and right are used for moving between the IP cells. Enter
button confirms the option. Menu button cancels the dialog without saving.
Image 5.24 : Dialog IP address overview
String List Selection

The dialog string list is dedicated for list item selection. When the dialog is active the buttons arrow up and
down are used for item selection. Enter button confirms the option. Menu button cancels the dialog without
saving.

Image 5.25 : Dialog String List overview
Text Edit
The dialog text is dedicated for text inserting or modification. When the dialog is active the buttons arrow up
and down are used for letter selection. Arrow up means the selection in left direction, arrow down means the
selection in right direction. Arrows right/left are used for moving between the letters to the next/previous letter
position in the text field. If actual position is very right letter then the arrow right inserts new letter to the right.
Letter DEL deletes actualy selected letter (using left or right arrow). Insert letter (empty letter - just behind the
DEL letter) inserts the letter to the actual position (using left or right arrow) Enter button confirms the text
modification. Menu button cancels the dialog without saving.
Image 5.26 : Dialog Text overview
Note: Enter button is used for dialog confirmation and saving the entire text to the configuration and because
of this the DEL and INS letter is inserted using the left or right arrow button.
Time and date edit
Date
The dialog date is dedicated for date setting. When the dialog is active the buttons arrow up and down are
used for number selection. Arrows left and right are used for moving between the date cells. Enter button

Image 5.27 : Dialog Date overview
Time
The dialog time is dedicated for date setting. When the dialog is active the buttons arrow up and down are
used for number selection. Arrows left and right are used for moving between the time cells. Enter button
Image 5.28 : Dialog Time overview
Timer settings
The dialog timer is dedicated for timer setting. When the dialog is active the buttons arrow left and right are
used for the line option selection. Enter button confirms the actual option in the line and the next option can be
performed. Enter button on the last line confirms all the option in dialog and save the timer settings to the
controller. Menu button cancels the dialog without saving.

Image 5.29 : Dialog Timer (Off) overview
Image 5.30 : Dialog Timer (Once) overview

Image 5.31 : Dialog Timer (Repeated) overview
Metering screens
InteliNeo 6000 Controller screens
InteliNeo 6000 metering screens are predefined by ComAp and covers all the application types.
the movement between the metering screens is done using the arrow up and down buttons in the front
panel
the entire screens and instruments on the screens are dynamically displayed or hidden based on the
following state of the controller unit :
Application type
Wiring controller settings
Configured CAN modules
ECU list settings
InteliNeo 6000 metering screens

Home Statistics
Power Ethernet 1
BESS Ethernet 2
Mains Ethernet 3
Bus Hot Swap Redundancy
Synchronization CAN modules
Power Management ECU modules
Analog inputs Modbus Master Devices
Binary Outputs Virtual modules
Binary Inputs
Grid Codes
Alarmlist
The alarmlist page is intended for displaying the controller alarms. If any of the following type of the controller
alarm occurs The alarmlist page is displayed and also the alarm icon in the Top status bar starts flashing
RED, even if it is not the shutdown alarm. The Automatic jump to the Alarmlist page is performed only in case
the actual GUI position is the Home metering screen. The alarm icon in the top status bar is informative icon
where the display unit informs the user that there is any alarm stored in the controller unit. Pressing the User

button 3 opens the alarmlist page. The alarmlist page is displayed until the alarmlist contains at least one
unconfirmed alarm.
There are 4 different types of controller alarms :
Warning (often also known as 1st level alarm) - represented by the YELLOW colour. These types of
alarms inform the user that something is wrong and need to be checked and confirmed.
Shutdown (often also known as 2nd level alarm) - represented by the RED colour. These types of
alarms protects the BESS during the wrong state.
ECU alarm - represented by the BLUE colour. This type of alarm comes from the connected external ECU
units.
Image 5.32 : Alarmlist Page
1. Alarm item number - displays the number of the concrete alarm.

2. Alarm item star - describes if the alarm is CONFIRMED or NOT COFIRMED. The confirmation action is
performed by the Alarm reset button in the front panel
a. Star is displayed - alarm is NOT CONFIRMED
b. Star is not displayed - alarm is CONFIRMED (using alarm reset button)
3. Alarm description - The short description of the alarm
4. Alarm coloring - There are specified the color and asterix combination
level 1 (warning) alarm
Active/unconfirmed : * / yellow background / dark text (asterix active)
Active/confirmed : yellow background / dark text (asterix inactive)
Inactive/unconfirmed : * / dark background / yellow text / asterix active

level 2 (shutdown) alarm
Active/unconfirmed : * / red background / white text (asterix active)
Active/confirmed : red background / white text (asterix inactive)
Inactive/unconfirmed : * / dark background / red text (asterix active)

ECU alarm
Active/unconfirmed : * / blue background / white text (asterix active)
Active/confirmed : blue background / white text (asterix inactive)

Inactive/unconfirmed : * / dark background / blue text (asterix active)
5. Topstatus bar Alarmlist icon - The alarm icon is fashing red if there is at least one unconfirmed alarm
(shutdown or warning) in the alarmlist. The icon lights red if there is at least one confirmed active alarm
and no unconfirmed alarm in the alarmlist. The icon is inactive if the alarmlist is empty. This is information
that something is wrong and need to be checked and resolved.
Note: The Alarmlist displays maximum 8 alarm items at the same time. If there is more than 8 alarms in the
alarmlist it is possible to list in the page to another alarm items by arrow up and down buttons.
Note: The alarmlist page is automatically displayed and backlight is turned on if the new alarm appears (only
in case the actual GUI position is the Home metering screen).
IMPORTANT: InteliVision 5.2 displays maximum 16 alarms.
IMPORTANT: Alarm reset button confirms all the unconfirmed alarms stored in controller and
resets the horn. Horn reset button resets only the horn.
IMPORTANT: If the actual GUI position is Alarmlist page and there is at least one uncofirmed
alarm in the Alarmlist the jump to the home metering screen and backlight timeout are ignored.
History
The history page displays the records of the important moments in the controller history.
There are 2 types of history records :
Event records - are also known as standard history records. This type of record appears in case the
controller event has been made. The time stamp history also belongs in the event history. The time record
is stored for a specified period of time.
System records - are also known as text history record. These type of records are generated during the
user login/off, controller programming or other system actions.
Image 5.33 : History page overview
1. Fixed column - has a different shade of colour. Fixed column is always merged and anchored on the left
side of the history page.

2. Event history record - this type of record appears in case the controller event has been made.The time
stamp history also belongs in the event history. The time record is stored for a specified period of time.
Pressing the enter button the dialog with detailed information for selected record is displayed.
3. System history record - this type of record appears in case the controller system action has been
made.The time stamp history also belongs in the event history. The time record is stored for a specified
period of time. Pressing the enter button the dialog with detailed information for selected record is
displayed.
4. Jump to first row and column - the jump to the first row and first column is performed if the button is
pressed.
5. Listing mode - by pressing this button the listing mode is changed. There are available 3 modes : listing
by 1 item, listing by 1 page, listing by 10 page. The mode is useful if the history is full of records. Listing
mode is also automatically changed if the listing buttons arrow up and down are pressed for longer time.
Original mode is set when the listing buttons are released.
Image 5.34 : History page - Item detail dialog
Note: Pressing the enter button on the actually selected row the dialog with detailed information for selected
record is displayed.
IMPORTANT: Each controller unit supports the specific number of history records. E.g. controller
InteliNeo 6000 supports 1000 history records. Default configuration consists of 33 columns.
Maximal column amount is approximately 100 columns based on the type of the observed value.

Trends
Image 5.35 : Trends page overview
The Trends page is divided on to 3 main blocks :

Main Trends Window is intended to display all trends. The view and chart movement is fully automatic.
Channel panel displays the actual values and sample period.
Function buttons is intended for start, stop and settings of the trends.
Image 5.36 : Trends page description
1. X axis -X axis displays the time stamps. The view of X axis is fully automatic.
2. Y axis - If the default range is not suitable for the displaying of the value it can be adjusted in settings
option. See bellow for more information.
3. Grid - the grid is displayed behind the trends charts. The grid is fully automatic.
4. Trend line - each channel have different colour for better value identification. The color of the trend line
match to the Value color in channel panel.
5. Actual period - Actual period settings. The period can be adjusted in settings option.
6. Actual channel value panels - display the values of the newest (actual) sample.

7. Trend Icon (Top Status bar) -if the trends are running the informative icon is shown in the top status bar
8. Start / Stop button - the button is dedicated for manual start and stop of the trends. It is possible to setup
the automatic start of trending based on the trigger. There are 2 triggers : Return to Home metering screen
and the specified bit of the available binary value.
9. Channel settings button - There are some settings available for the trends. See more information
bellow.
Administration
Administration menu screen is accessible by using the buttons combination Enter + Menu just only from the
metering screens. Enter button has to be pressed first.
+
Image 5.37 : Shortcut (jump to the administration)
Configuration Level
Image 5.38 : Administration Page - Configuration Level
Standard - Limited amount of settings are available for configuration. The description which settings are
available in chapters concerning to controller functions.
Advanced - Set by factory default. All the settings are available for configuration. Be aware that only
experiences users should perform the settings of extended functions.
Note: By default the Advanced settings is selected which means all the setpoints are available by default. To
restrict the availability the Standard setting must be performed. The advanced and standard category are set
in InteliConfig PC application.
Note: Configuration Level screen is accessible using the buttons combination Enter + Menu just only from
the metering screens. Enter button has to be pressed first.

Display settings
Image 5.39 : Administration Page - Settings
1. Backlight Time - if the cell area is pressed the dialog for time settings is displayed. The user is able to set
the period from 1 up to 241 minutes. There is also the option to set NO Timeout which means the display
unit is backlighted forever. Note that in remote displays like IntelIVision 5.2 the Backlight Timeout option is
not mirrored with controller setpoint Backlight Timeout (it is mirrored in Integrated Color Display).
2. Brightness Control :
a. Manual (by default) - the value of the backlight is set manually using the value dialog (point 3)
b. External - the value of the backlight is controlled by the external resistor or potentiometer. Resistor 5-
2400 Ω corresponds to 0-100% backlight. If the resistor value is out of range, the manual option is
used.
3. Brightness intensity - the value is selected using the value dialog. Note the value is applied immediately
during the change of the value.
4. Internal Temperature information- gives the actual inside temperature of the unit. There is implemented
automatic mechanism for lowering the backlight intensity based the internal derating backlight curve. If the
inside temperature exceeds 35 °C the area behind the temperature lights yellow. The yellow color
indicates that the display backlight curve is applied and automatically starts derate the backlight intensity.
The backlight intensity returns to normal when the temperature is decreased bellow 35 °C. This feature
saves the lifetime of the internal components.
IMPORTANT: It is strongly recommended to use backlight on the standard level max. 60%.
Maximal backlight intensity level of 100% is suitable only for application with higher amount of
the ambient light. Be aware that higher intensity level means higher surface front glass
temperature and lower lifetime.
IMPORTANT: It is strongly recommended to use Backlight Time (timer) set on the reasonable
amount of time (approximately 30 minutes) during the normal running BESS phase. It is because
of saving lifetime of the display unit. The display unit is still running if the backlight is off. For
switching on the LCD backlight the simple pressing any button is necessary.
Note: Settings screen is accessible using the buttons combination Enter + Menu just only from the metering
screens. Enter button has to be pressed first.

Languages
Image 5.40 : Administration Page - Languages
Language settings - the list of languages stored in the controller configuration is displayed in the list of
possible languages.
The InteliVision 5.2 and Integrated Color Display units support the following languages
English
Chinese
Japanese
The InteliVision 5.2 and Integrated Color Display units partially support the following languages
Bulgarian, Taiwan, Czech, German, Greek, Spanish, Finnish, French, Hungarian, Icelandic, Italian,
Korean, Dutch - Netherlands, Norwegian, Polish, Roman, Russian, Croatian, Slovak, Swedish,
Turkish, Ukrainian, Slovenian, Estonian, Latvian, Lithunian, Vietnamese, Italian, Portuguese, Bosnian
The InteliVision 5.2 and Integrated Color Display units support the following Unicode standard character
sets
Basic Latin, Latin-1 Supplement, Latin Extended-A, Latin Extended-B, Latin Extended Additional,
Cyrillic, Greek, Greek Extended, Arabic, Arabic Supplement, General Punctuation, Superscripts and
Subscripts, Currency Symbols, Arrows, CJK Unified Ideographs, Kanji, Hiragana (full width), Katakana
(full width), Hangul Jamo, Thai
IMPORTANT: Even the language is configured in InteliConfig the specific language is unavailable
if the language is empty or the language is not supported by the display unit.
Note: The flag is not displayed if the language is supported but the flag icon does not exist in the integrated
color display unit.
Note: Languages screen is accessible using the buttons combination Enter + Menu just only from the

Controller Info
Controller Info screen in InteliVision 5.2 is dedicated for important information about the connected controller
unit. These information is useful mainly for issues troubleshooting.
Controller info page is divided into 2 main blocks of information :
Controller unit
ID String
Software Version
Serial Number
Controller Type (HW)
Application Type (HW)
Application Branch (HW)
Hardware Type (PCB)
Hardware Version
ID Chip Version
Hardware Features
Configuration
Application Version
Controller Type (SW)
Application Type (SW)
Application Branch (SW)
Application
Configuration Format / Configuration Terminal Format
Configured by
Image 5.41 : Administration Page - Controller Info
Note: Similar values with similar structure can be displayed using InteliConfig PC tool.
Note: Controller Info screen is accessible using the buttons combination Enter + Menu just only from the
IMPORTANT: Integrated Color Display information in Controller Info screen is not available in
remote displays.

Modules Info
Modules Info screen is dedicated for important information about the connected CAN and Plug-In modules
information. The page Modules Info displays the information from the following type of connected modules :
Plug-In modules
CAN peripheral extension modules
Image 5.42 : Administration Page - Modules Info
Note: The availability of the connected module depends on the type of controller unit.
Note: Modules Info screen is accessible using the buttons combination Enter + Menu just only from the

ECU Modules Info
Electronic Control Unit Modules screen is dedicated for important information about the connected modules
information.
The screen ECU Modules displays the information from the following type of connected modules :
ECU Modules
Image 5.43 : Administration Page - ECU Modules
Note: The availability of the connected ECU module depends on the type of controller unit.
Note: ECU Modules screen is accessible using the buttons combination Enter + Menu just only from the
Basic operating modes description

This chapter contains brief information on how the controller behaves in different modes of operation. If you
require more information on separate functions of the controller please go to the chapter Operating Modes
(page 181)
The InteliNeo6000 has the following controller operation modes: OFF, MAN , and AUT .
OFF mode
No start of the BESS is possible and starting command cannot be issued.
No reaction if buttons START , STOP , MCB ON/OFF , BCB ON/OFF are pressed.
Note: When the BESS is running, it is not possible to switch the controller to OFF mode.
MAN mode
To start the BESS press START.
When the BESS voltage is within limits, the BESS icon will light green.
Press BCB ON/OFF to close the BCB. If the BESS voltage is out of the limits, controller does not respond
to the BCB ON/OFF .
If controller detects dead bus, immediately closes output.
If controller detects voltage on the bus, starts synchronizing.
When the breaker is closed, the breaker icon will light green.

To stop the BESS press STOP
Controller unloads the BESS, opens BCB CLOSE/OPEN (PAGE 926). Unloading is active only when
binary input MCB FEEDBACK (PAGE 902) is closed or other BESS is connected to bus. In other case
BCB CLOSE/OPEN (PAGE 926) opens immediately.
AUTO mode
BESS is controlled based on external signals REMOTE START/STOP (PAGE 915) or conditions (AMF, Peak
shaving, Power management system, etc.).
When one condition deactivates the BESS, it will not stop if another condition for automatic starts is active.
Controller does not respond to BCB ON/OFF, MCB ON/OFF, STOP, START buttons and corresponding
remote InteliScada or Modbus commands.
IMPORTANT: If a red alarm is present and the controller is in the AUT mode, the BESS can start
by itself after all red alarms become inactive and are acknowledged (fault reset is pressed)! To
avoid this situation, adjust the setpoint Fault Reset To Manual (page 379) to the Enabled position.
5.2 Controller configuration and PC tools

connection
5.2.1 USB 112
5.2.2 Ethernet 113
6 back to Controller setup

This chapter contains brief introduction into the specifics of firmware and archive upload and connection of
various PC tools to the controller. If you require detailed information on each PC tool please use the included
Help in those PC tools or download their Reference Guides.
5.2.1 USB
You may connect to the controller using the ⑭ USB (page 47) Port. In this case standard USB A to B cable
should be used - USB (page 74) connection.
Connection using InteliConfig
Image 5.44 First screen of InteliConfig - select connect to controller

Image 5.45 Second screen of InteliConfig - Select your controller from list of Detected
controllers.
Select your controller from the list of Detected controllers. You need to know your contoller's serial number.
Note: You do not need to be using user account while connecting via USB.
Connection using WinScope
Image 5.46 WinScope screen - Select your controller from list of Detected controllers.
Select your controller from the list of Detected controllers. You need to know your contoller's serial number.
Note: You do not need to be using user account while using WinScope1000 connected via USB.
5.2.2 Ethernet
You may connect to the controller using any of the Ethernet 1 (page 50), Ethernet 2 (page 50), or Ethernet 3
(page 50) ports, if correct Ethernet Port Configuration settings are applied (Ethernet port 1 (page 395),
Ethernet port 2 (page 396), Ethernet port 3 (page 397)).
Note: See Communication peripherals (page 18) to see differences between these peripherals.

Note: Go to Types of interfaces (page 222) to see types of ethernet interfaces and possibilities of
connections.
Direct connection
When you use direct connection the controller needs to be reachable directly from the PC you use (i.e. one
LAN or WAN without any firewalls and other points that may not allow the connection). The following settings
need to be checked in the controller:
Direct Connection Port (page 403) has to be set to the same value as in the PC tool.
IP Address Mode (page 398) can be set to AUTOMATIC when there is DHCP service is available.
Otherwise it needs to be set to FIXED.
IP Address (page 399) is either set automatically or it can be adjusted to a specific requested value.
Subnet Mask (page 399) is either set automatically or it can be adjusted to a specific requested.
Gateway IP (page 400) can be set here when it is used.
Note: The connection speed might be significantly limited when you connect the controller directly from the
PC and your Ethernet card is setup to Energy-Efficient Ethernet option.

Image 5.48 Second screen of InteliConfig - select Ethernet
Use IP address which is stored in proper value (based on selected Ethernet peripheral) and fill Controller
address - this needs to be same as value of Terminal Comm Address (page 385).
IMPORTANT: Never fill Access code!
IMPORTANT: In case of using Ethernet 2 (page 19) you need to fill Username and Password of
actual user account.
Image 5.49 Second option of connection via InteliConfig
You can also select controller from "Detected controllers" feature. If this controller is connected via Ethernet 2
(page 19) you will be prompted to fill Username and Password of actual user account.

Image 5.50 WinScope screen - select Ethernet
Use IP address which is stored in proper value (based on selected Ethernet peripheral) and fill Controller
address - this needs to be same as value of Terminal Comm Address (page 385).
IMPORTANT: In case of using Ethernet 2 (page 19) you need to fill Username and Password of
actual user account.
AirGate connection
You may connect to the controller using AirGate which works only via Ethernet 2 (page 19). If the AirGate key in
the Access Administration is empty the controller will not connect to the AirGate despite the function is enabled.
Access Administration is available in Tools of the InteliConfig.
Setpoints and values related to connection via AirGate:
AirGate Connection (page 408) - has to be ENABLED
AirGate Address (page 409) - manually adjusted address of AirGate server
AirGate Port (page 409) - manually adjusted port for communication between Controller and AirGate
server
AirGate Status (page 802) - has to be connected, operable
AirGate ID (page 802) - 9 numbers long ID of the controller
IMPORTANT: Controller has to be connected to the Internet.

Image 5.52 Second screen of InteliConfig - AirGate
Use AirGate ID, AirGate server with proper port (54441 for global.airgate.link), AirGate Key and Controller
address - this needs to be same as value of Terminal Comm Address (page 385). Valid user account -
Username and Password - is required for the connection.
Note: Ask your administrator for AirGate Key. Administrator can always change the key via InteliConfig using
"Tools -> Access administration -> Change AirGate key"

Image 5.53 WinScope1000 screen - select AirGate
Use AirGate ID, AirGate Server with proper port (54441 for global.airgate.link), Device Access Key and
Controller Address - this needs to be same as value of Terminal Comm Address (page 385). Valid user
account - Username and Password - is required for the connection.
5.3 Default configuration

5.3.1 Binary inputs
Number Name Description Configured function
BIN1 BCB Feedback BESS circuit breaker feedback BCB FEEDBACK (PAGE 881)
BIN2 MCB Feedback Mains circuit breaker feedback MCB FEEDBACK (PAGE 902)
BESS Ready To BESS READY TO LOAD (PAGE
BIN3 BESS is ready to be loaded
Load 885)
Photovoltaic (renewables) circuit
BIN4 PVCB Feedback PVCB FEEDBACK (PAGE 912)
breaker feedback
BIN5 Remote OFF Switch controller to OFF mode REMOTE OFF (PAGE 914)
BIN6 CU-BIN-06 Free slot Not Used
BIN7 Sd Override Suppression of alarms SD OVERRIDE (PAGE 915)

5.3.2 Binary outputs
Number Name Description Configured function
BOUT1 CU-BOUT-01 Free slot Not Used
INVERTER RUN REQUEST
BOUT2 BESS Run Request Request to start BESS
(PAGE 953)
Indication of required BESS Circuit BCB CLOSE/OPEN (PAGE
BOUT3 BCB Close/Open
Breaker state 926)
Indication of required Mains Circuit MCB CLOSE/OPEN (PAGE
BOUT4 MCB Close/Open
Breaker state 959)
Activation of any devices before
BOUT5 Prestart PRESTART (PAGE 967)
BESS start
BESS READY TO LOAD
BOUT6 Ready To Load BESS can be connected to load
(PAGE 936)
BOUT7 Alarm Indication of unconfirmed alarm ALARM (PAGE 924)
5.3.3 Analog inputs

Configured
Number Configured sensor Configured function
sensor
AIN1 CU-AIN-01 Not configured Not Used
5.3.4 Analog Outputs

Number Name Output HW type Configured function
AOUT1 CU-AOUT-01 U [-10 V, 10 V] VRO
AOUT2 CU-AOUT-02 U [-10 V, 10 V] FRO
5.4 General Functions

5.4.1 3V3 Reference Voltage Measurement 121
5.4.2 Access lock 121
5.4.3 Alarm Management 122
5.4.4 AMF Function 125
5.4.5 Breaker Control 126

5.4.6 CAN Bus Log 131
5.4.7 CAN Intercontroller Communication 132
5.4.8 CAN1 ECU/IO Modules Splitting 133
5.4.9 Configuration Lock 135
5.4.10 Configuration Override 135
5.4.11 Control Groups 136
5.4.12 Crash Dump 137
5.4.13 Distributed Power Management Signals 138
5.4.14 E-STOP 143
5.4.15 Event History 145
5.4.16 Exercise Timers 149
5.4.17 Firewall 157
5.4.18 Forced Value 158
5.4.19 Hot Swap Redundancy 160
5.4.20 I/O Configuration 166
5.4.21 Load Shedding 170
5.4.22 Loss of Mains (Decoupling) Protections 173
5.4.23 Mains Import Measurement 175
5.4.24 Modbus Client (Master) 175
5.4.25 Multiple ECU 180
5.4.26 Operating Modes 181
5.4.27 PLC - Programmable Logic Controller 183
5.4.28 Power Formats And Units 196
5.4.29 Protections 197
5.4.30 Pulse Counters 211
5.4.31 PV Inverter Slots 212
5.4.32 SD Card Storage 215
5.4.33 Sensor Curves 216
5.4.34 Service Timers 218
5.4.35 Sunrise/Sunset 219
5.4.36 Sunspec 219
5.4.37 System Start/Stop 219
5.4.38 SW Key Features 219
5.4.39 User Buttons 220
5.4.40 User Management And Data Access Control 222
5.4.41 User Setpoints 228
5.4.42 Voltage Phase Sequence Detection 231
General functions which are not directly related to the Microgrid application are described in this chapter.

5.4.1 3V3 Reference Voltage Measurement
The 3V3 reference voltage is critical for the right functionality of analog/digital converters (ADC). If the 3V3
reference is out of the limit (less than 3.2 V or more than 3.4 V) all voltage measurements will be distorted. In this
case, the LBO HW AC VOLTAGE MEASUREMENT ERROR (PAGE 952) is activated. It is recommended to use this
LBO to activate user protection which will open the BCB and turn off the BESS to prevent any damage to
theBESS, load, or Mains.
The input value for the LBO is given by the average of all 3 measured reference voltages which increases the
robustness of the protection. The reference voltage should be always fixed and within the limit. Wrong reference
voltage might mean the controller unit is going to fail. The LBO HW AC VOLTAGE MEASUREMENT ERROR (PAGE
952) is deactivated immediately after the average value of the reference voltage is back within the limit. If the
LBO is still being active, you can try to power off and power on the controller unit. If it doesn't help, it is
recommended to contact the technical support.
5.4.2 Access lock

The Access lock function allows any user with Access level 1 and higher to Lock the controller configuration for
other users. So, only the user who locked the controller will be able to use the controller buttons, change
setpoints or write configuration into the locked controller. All LBIs will be still operable, using the PLC the LBO
ACCESS LOCKED (PAGE 923) can be used to block any LBIs. The configuration can be unlocked only by the user
who locked it or by the administrator. This function can be especially useful if more people are remotely
connected to the same controller. The access lock works the same way for configuration via the InteliVision
display.
There are 5 types of buttons in the InteliConfig that signalize the actual state of the Access lock.
1. Default state: The controller configuration is unlocked and the user has permission to lock it for other
users.
2. The controller configuration is locked by you.
3. The controller configuration is locked by another user and you can unlock it because you are logged in as
administrator.
4. The controller configuration is locked by another user and you cannot unlock it.
5. The controller configuration is unlocked and your Access level is too low to lock it.
Configurable Access Lock behavior

The extension of functionality is based on the requirement that the machinery is equipped with more operator
stations and the control must have only one of them at any time.
The lock is required for control in Exclusive mode, i.e. user have to activate Access lock with his account to
control the controller.

Access Lock release request
Any user with permission to control the lock will be able to send a request to hand over control when the control is
locked by another user. The request is automatically deactivated when the lock is unlocked.
The user who is the owner of the locked lock will see on the display that the unlock request is active and the lock
icon will change. The icon will also change on the side of the user who sent the request.
In case of emergency, you can use the option to unlock the Access Lock by a user with an administrator role.
The owner of the lock may hand over control to the applicant by confirming the release of the lock.
The release request indication is canceled by unlocking the lock and this occurs in 3 cases:
The owner of the lock will unlock it
The administrator will unlock it
Automatic unlocking if the owner of the lock no longer has any sessions. Applies to setpoint Automatic
Access Lock Release (page 392) settings Enabled.
Concurrent sessions limit

You can set the number of concurrent sessions for a logged-in user. It is possible not to limit this number and this
option does not apply to the administrator role or implicit user.
For more details see User sessions limit (page 392)
5.4.3 Alarm Management

Alarms purpose is to indicate occurrence of unwanted situation such as unexpected opening of breaker,
generator overvoltage etc. But in certain situations, we use alarms as a way to visualize information that affects
current behavior of the controller.
The controller evaluates two levels of alarms. Level 1 – yellow alarm – is a non-critical alarm that is only
informative and does not take any action regarding the BESS control. Level 2 – red alarm – represents a critical
situation, where an action must be taken to prevent damage of the BESS or technology.
One alarm of level 1 and one alarm of level 2 can be assigned to each binary input
Multiple protections can be assigned on each analog input.
There are also Controller integrated protections (page 125) with Fixed Protection States (page
1016).
Each alarm is written to the Alarmlist (page 125).
Each alarm causes a record to be written into the history log.
Each alarm activates the Alarm and Horn output.
Each alarm can cause sending of a SMS message or an email.

Image 5.54 Analog input alarm evaluation principle
Alarm states
An alarm can have following states:
Active alarm: the alarm condition persists, alarm delay has elapsed.
Inactive alarm: the alarm condition has disappeared, but the alarm has not been confirmed.
Confirmed alarm: the alarm condition persists, but the alarm has already been confirmed.
Image 5.55 Alarm List
Visual interpretation of alarm is decided by terminal side. Commonly for active alarms whole row background
is colored (yellow/red/blue). Inactive alarms have transparent background color and text is colored
(yellow/red/blue)
Alarm types
The controller recognize 3 basic types of the alarm. Each type of alarm is paired with specific types of Protection
types (page 198).
Alarm Level 1
The level 1 alarm indicates that a value or parameter is out of normal limits, but has still not reached critical level.
This alarm does not cause any actions regarding the BESS control. For whole list see Alarms level 1 (page
1080)
Alarm Level 2
The level 2 level alarm indicates that a critical level of the respective value or parameter has been reached. For
whole list see Alarms level 2 (page 1112)

Note: It is not possible to start the BESS if any red level protection is active or not confirmed.
IMPORTANT: The BESS can start by itself after acknowledging the alarms if there is no longer an
active red alarm and the controller is in AUTO mode!
Sensor fail detection (Fls)

If the measured resistance on an analog input exceeds the valid range, a sensor fail will be detected and a
sensor fail message will appear in the Alarmlist (page 125). The valid range is defined by the most-left (RL)
and most-right (RH) points of the sensor characteristic ±12.5% from RH-RL.
Note: Sometimes there can be problem with lower limit of valid range which can be counted as negative
number. In this case the lower limit is set as one half of the RL point of the sensor curve characteristic.
Image 5.56 Sensor fail detection principle
Remote alarm messaging

The controller can sends emails at the moment when a new alarm appears in the Alarmlist (page 125) or new
event is written in Event History (page 145). The message will contain a copy of the Alarmlist (page 125) or
reasons from Event History (page 145). To enable this function, adjust setpoints Sd Message (page 411), Wrn
Message (page 410), or Event Message (page 410) to ON. Also enter a valid email address to the setpoints, E-
mail Address 1 (page 412), E-mail Address 2 (page 413), E-mail Address 3 (page 413), or E-mail Address
4 (page 413).
The list of all supported terminals shows the table below:
Terminal Event email Warning email Shutdown email

RS485 NO NO NO
USB NO NO NO
Ethernet YES YES YES

Alarmlist
Alarmlist is a container of active and inactive alarms. It will appear automatically on the controller display, if a new
alarm occurs, or can be displayed manually from the display menu.
Active alarms are shown as inverted, not yet confirmed alarms are marked with asterisk before them.
Alarmlist contains three types of alarms:
Controller built-in alarms
User configured alarms
ECU alarms
Controller integrated protections

An alarm message in the alarmlist begins with a prefix, which represents the alarm type (e.g. Wrn, Al, Hst, ALI,
PVBO). Then the alarm name follows. In some cases the prefix can be omitted.
User configured protections

An alarm message in the alarmlist begins with a prefix, which represents the protection type (e.g. Wrn, Al, Hst,
ALI). Protection type and alarm name are selected by user during the Configuration of protections in
InteliConfig (page 205). Then the alarm name follows.
ECU alarms
The ECU alarms are received from the Electronic Control Unit. The alarms are represented by the Diagnostic
Trouble Code, which contains information about the subsystem where the alarm occurred, the alarm type and the
alarm occurrence counter.
The most common fault codes are translated into text form. Other fault codes are displayed as a numeric code
and the ECU fault codes list must be used to determine the reason.
5.4.4 AMF Function

IMPORTANT: This chapter is relevant only for MPTM application.
For the InteliNeo6000 the AMF function is used only for automatic Mains failure and healthy detection. There is
no emergency start related to the technology when Mains fails because it is expected that renewables and BESS
are already running.
Related setpoints are:
AMF Timers AMF Settings

Mains Stabilization Delay (page 526) MCB Logic (page 360)
MCB Close Delay (page 526)
Mains failure detection

The Mains is considered as faulty when one or more of the following conditions are valid:
The Mains voltage is out of the limits given by the setpoints Mains <V (page 518) (Mains <<V (page
519)) and Mains >V (page 514)Mains >V (page 514)(Mains >>V (page 515)) for a time period longer
than Mains <V Delay (page 518) respectively Mains >V Delay (page 514) (Mains <<V Delay (page
520), Mains >>V Delay (page 516)).
The Mains voltage unbalance is out of limit given by setpoint Mains V Unbalance (page 521) for a time
period longer than Mains V Unbalance Delay (page 521).

The Mains frequency is out of the limits given by the setpoints Mains <f (page 524) (Mains <<f (page
525)) and Mains >f (page 522) (Mains >>f (page 523)) for a time period longer than Mains <f Delay
(page 524) respectively Mains >f Delay (page 522) (Mains <<f Delay (page 525), Mains >>f Delay
(page 523)).
The MCB close command was not successful and the alarm Wrn MCB Fail (page 1089) is present in the
alarmlist.
Alarm ALI Mains Ph Rotation Opposite (page 1109) is active.
Healthy Mains detection

The Mains is considered to be healthy when all of following conditions are valid:
The Mains voltage is within the limits given by the setpoints Mains <V (page 518) (Mains <<V (page
519)) and Mains >V (page 514)Mains >V (page 514)(Mains >>V (page 515)).
The mains voltage unbalance is within the limits given by the setpoint Mains V Unbalance (page 521).
The Mains frequency is within the limits given by the setpointsMains <f (page 524) (Mains <<f (page
525)) and Mains >f (page 522) (Mains >>f (page 523)).
The alarm Wrn MCB Fail (page 1089) is not present in the alarmlist.
Alarm ALI Mains Ph Rotation Opposite (page 1109) is not active.
5.4.5 Breaker Control

The following power switches are controlled by the controller:
The BESS Circuit Breaker or contactor – BCB
The PV Circuit Breaker or contactor – PVCB (breaker for renewables)
The Mains Circuit Breaker or contactor – MCB (see the chapter MCB special requirements (page 127))
The Neutral Contactor Breaker - NCB (see the chapter Neutral Contactor Breaker (page 129))
The closing of PVCB and BCB breakers is limited by precharge type of used inverters. It is expected that AC
precharge type is always used for the PV so the PVCB can be closed (synchronized) only if the bus is healthy
(there is AC voltage on the bus). The BESS inverter can use AC or DC precharge. For the AC option the
conditions are the same as for the PV. For the DC option the BCB can be closed to the dead bus or
synchronized to the healthy bus. See more information in the chapter BESS Precharge Types (page 240).
It is possible to use either a motorized circuit breaker or contactor. Below is a list of available control outputs
that should fit all types of contactors or breakers. The following rules must be kept to when designing the
wiring of power switches:
The control outputs must be configured and wiring of the power switches must be provided in such a way,
that the controller has full control over the breakers – i.e. the controller can open and close the breaker at
any time.
The breaker must respond within max. 2 seconds to a close and open command. Special attention should
be paid to opening of motorized circuit breakers, as it could take more than 2 seconds on some types. In
such cases it is necessary to use an undervoltage coil for fast opening.
After opening the breaker, there is internal delay for another closing of breaker. Delay is 6 seconds - 5
seconds for OFF coil and 1 second for UV coil. After these 6 seconds, breaker can be closed again. For
opening of breaker there is no delay.

Breaker control outputs
An output for control of a contactor. Its state represents the breaker position requested
Close/Open by the controller. The breaker must react within 2 seconds to a close or open command,
otherwise an alarm is issued.
An output giving a 2 second pulse in the moment the breaker has to be closed. The
ON coil
output is intended for control of close coils of circuit breakers.
An output giving a pulse in the moment the breaker has to be opened. The pulse lasts
OFF coil until the feedback deactivates, but at least for 2 seconds. The output is intended for
control of open coils of circuit breakers.
The BCB UV coil output is active the whole time the BESS is running. The MCB and
PVCB UV coil output is active when the controller is switched on. The output is
UV coil
deactivated for at least 2 seconds in the moment the breaker has to be switched off. The
output is intended for cont rol of undervoltage coils of circuit breakers.
Image 5.57 Breaker control outputs
MCB special requirements

If a contactor is used on the MCB position, it is recommended that the wiring be provided in such a way
that the contactor will be normally closed and will open if the logical binary output MCB CLOSE/OPEN
(PAGE 959) closes. This behavior is called "negative logic" and can be adjusted by the setpoint MCB
Logic (page 360). The negative logic will prevent accidental opening of the MCB when the controller is
switched off.
Breaker fail detection

Breaker fail detection is based on binary output breaker close/open comparing with binary input breaker
feedback. If breaker feedback is not configured and breaker control mode is internal, the alarm will be activated
always because the change of the breaker close/open will not be followed by breaker feedback.

There is an exception for the MCB breaker. If the breaker feedback indicates the MCB has unexpectedly opened
without any command given by the breaker close/open the controller will accept it and following behavior will
depend on Mains condition. The MCB breaker stay opened if Mains fails or is closed if Mains is healthy.
There are three different alarm types, see following diagrams.
When binary output breaker close/open is in steady state and breaker feedback is changed the breaker
fail is detected immediately without delay and alarm Stp BCB Fail (page 1124) is issued. The alarm is
issued also after 500 ms when there is mismatch of LBI BCB FEEDBACK (PAGE 881) and LBI BCB
FEEDBACK NEGATIVE (PAGE 882) . Except opening of MCB.
Image 5.58 Breaker fail - breaker close/open in steady position - open
Image 5.59 Breaker fail - breaker close/open in steady position - close
When binary output breaker close/open is opened, there is 2 seconds waiting time for feedback If
feedback doesn't match, the alarm Stp BCB Fail To Open (page 1125)/Wrn MCB Fail To Open (page
1091) is issued.

Image 5.60 Breaker fail - breaker close/open opens
When binary output breaker close/open is closed there is 2 seconds waiting time for feedback. If the
feedback doesn't match the output, close/open is opened and closed again after delay defined by setpoint
Delay Between Closing Attempts (page 363). If feedback doesn't match after second try and 2 seconds
delay elapsed, the alarm Stp BCB Fail To Close (page 1125)/Wrn MCB Fail To Close (page 1090) is
issued.
Image 5.61 Breaker fail - breaker close/open closes
Note: In case of using both feedbacks (standard and negative), both of them have to be in correct position,
otherwise breaker fail is issued after 500 ms.
A new alarm ALI GCB Closing Is Blocked (page 1) is activated in case Setpoint BCB Control Mode
(page 362) is set to Internal and any of following generator protections are switched to Disabled
Generator <f Protection
Generator >f Protection
Generator <V Protection
Generator >V and >>V Protection (both overvoltage must be disabled)
Short Circuit Protection
Neutral Contactor Breaker

Note: This chapter is common for Gen-sets and BESS.

The neutral contactor is used to connect the neutral wire (N) with the protective wire (PE) in a TN-S system. This
connection is used to ground the parasitic capacities and inductions and at one moment there can be only one
connection like this in the whole electric circuit. So, once the Site is connected to the Mains, the Site NCB must
be opened because the Mains has its own grounding.
For the MINT application there are two possible ways how to use the NCB. The first option is having a NCB for
each unit in the system, the second option is having one common NCB for all units in the system. The setpoint
#Neutral Contactor Control (page 355) is used to choose if EACH or COMMON behavior of the NCB will be
used.
For the MPTM application the NCB works like there is one common NCB for whole MPTM system.
Note: The information mentioned in the breaker control outputs and fail detection chapters above are not
related to the NCB breaker. The NCB has only one avialable output (Close/Open) and only basic NCB fail
detection without repeated command for breaker closing.
EACH
The EACH option should be used if each Gen-set has its own neutral contactor. The NCB CLOSE/OPEN (PAGE
963) output on each Gen-set is given by an internal algorithm, which ensures, that always exactly one Gen-
set connected to the bus with the lowest CAN address has the neutral contactor closed.
Four-pole MCB, MGCB, and GCBs have to be used in this case - all running Gen-sets that are not
connected to the bus have their own NCB closed.
The output is always opened while the Gen-set is not running.
The output is always opened while the MCB + MGCB (only for MGCB application) + GCB are closed
(Genset is running parallel to Mains).
The output is closed while the Gen-set is running and at least one Generator Ph-Ph voltage exceeds 85%
of the nominal voltage. It opens when the generator voltage in all phases drops below 50% of the nominal
voltage.
Image 5.62 NCB wired for each Gen-set

COMMON
The COMMON option should be used if there is only one common neutral contactor for the whole site. The
NCB CLOSE/OPEN (PAGE 963) outputs from all controllers are combined together and the combined signal is
used to control the breaker. If at least one Gen-set in the site is running and has a proper voltage, the neutral
contactor is closed.
Four-pole MCB, MGCB, and three-pole GCBs have to be used in this case - all running Gen-sets
with open GCB (not connected to the bus) must be connected to the common neutral contactor.
The output is always opened while the Gen-set is not running.
The output is always opened while the MCB + MGCB (only for MGCB application) are closed.
The output is closed while the Gen-set is running and at least one Generator Ph-Ph voltage exceeds 85%
of the nominal voltage. It opens when the generator voltage in all phases drops below 50% of the nominal
voltage.
Image 5.63 One common NCB wired for all Gen-sets
Note: LBI NCB FEEDBACK (PAGE 905) and LBO NCB CLOSE/OPEN (PAGE 963) has to be configured for
proper functionality.
Note: For both option the MGCB is taken in account only if there is any extra breaker between GCB and the
MCB.
5.4.6 CAN Bus Log

This function is used to log communication between the CU, ECU, and I/O modules on the CAN line. These logs
can be shared with our technical support and used for solving specific problems. The CAN Bus Log uses CAN2B
(page 19) which should be physicality connected to the observed CAN. The CAN2B (page 19) will works as
another device on the CAN line and it is necessary to do wiring in accordance with rules for wiring the CAN line.
IMPORTANT: The bus must be wired in linear form with termination resistors at both ends. No
nodes are allowed except on the controller terminals.

IMPORTANT: The CAN bus log works only if CAN Intercontroller Communication Redundancy is
not used.
To activate the CAN bus log function, go to the Tools in InteliConfig and press the button CAN Bus Log to open
the settings. You need to log in as at least a level 2 user. In the settings, you will choose the Output directory in
your PC, the Logging option (CAN for modules + communication speed or type of the Intercontroller CAN), and
press Start. The Logging status will be changed from Logging is stopped to Logging is running.
5.4.7 CAN Intercontroller Communication

CAN Intercontroller Communication is used for sharing information (data needed for regulations, power
management, shared signals, etc.) between ComAp controllers via CAN interface.
This communication is present on ⑧ CAN2A (page 47). In case of using CAN Intercontroller Communication
Redundancy (page 132), then the redundant communication is present on ⑦ CAN2B (page 47) .
The communication can run in different modes. Select your required mode by setpoint CAN Intercontroller
Comm Mode (page 389). The mode is changed only during powering up of the controller and actual mode is
stored in value CAN Intercontroller Comm Mode (page 780). In case that there is a mismatch between the
setpoint and the value, alarm ALI CAN Mode Inconsistency (page 1105) is activated. Restart the controller to
change the communication mode to the selected mode and to get rid of the alarm.
For easy detection of empty CAN you can set CAN Intercontroller Empty Check (page 390) to Enabled. Wrn
CAN2 Empty (page 1085) is activated every time when controller doesn't see any other controller connected via
⑧ CAN2A (page 47) and ⑦ CAN2B (page 47) (if the redundancy is used).
IMPORTANT: Options 64C CAN FD or 32C CAN FD or 8C CAN FD are compatible only with
controllers which support the CAN FD communication. Set correct mode by setpoint CAN
Intercontroller Comm Mode (page 389) otherwise controller will not communicate with each other.
Relevant setpoints
CAN Controller Address (page 385)
CAN Intercontroller Comm Mode (page 389)
Usage
Power Management (page 269)
MINT - Load Sharing, Var Sharing, and Shared signals

IMPORTANT: This is a premium function which requires SW Key in order to be used!
This function duplicates whole Intercontroller communication, which is on CAN2A (page 19) and sends it via
CAN2B (page 19).
The same wiring principles apply to CAN2B (page 19) as to CAN2A (page 19) (see CAN bus wiring (page
71)).

Step by step guide
Note: Following steps have to be done for each controller in the system.
1. Insert the SW Key (page 381) for CAN Intercontroller Redundancy

2. Restart the controller
3. Check the value SW Key Feature List (page 783) - CAN Intercontroller Redundancy has to be
enabled
4. Switch the setpoint CAN Intercontroller Comm Redund (page 388) to Enabled
5. Restartthe controller
6. Check that the value CAN Intercontroller Comm Redundancy (page 780) is Enabled
In case of mismatch between the value CAN Intercontroller Comm Redundancy (page 780) and the setpoint
CAN Intercontroller Comm Redund (page 388), alarm ALI Redundant CAN Error (page 1107) is raised.
In case of inconsistency of data on ⑧ CAN2A (page 47) and ⑦ CAN2B (page 47) line, alarm Wrn Redundant
CAN inconsistency (page 1099) is activated
In case of attempt to use this function without of valid SW Key alarm Wrn SW Key CAN Redundancy Error
(page 1102) is activated. See chapter SW Key Features (page 219) for more information.
Note: It is also possible to use CAN Intercontroller Communication Redundancy if there is a ComAp
controller in the system, wich does not support this feature (e.g. IM1010 + IG1000 + IGS-NT generation
controller). The redundancy will work (for the IG1000 and IM1010 controllers), but there will be Wrn
Redundant CAN inconsistency (page 1099) alarm active (because of the IGS-NT controller which doesn't
support the redundancy).
5.4.8 CAN1 ECU/IO Modules Splitting

This function allows the user to change the behavior of CAN1 communication terminals.
In default configuration:
CAN1A terminal is used for communication with ECU and IO Modules.
CAN1B terminal is used for Hot Swap Redundancy (page 160)

Image 5.64 Hot Swap Redundancy connection
If the setpoint CAN1 ECU/IOModules Split (page 394) is enabled, the behavior of CAN1A terminal is changed:
CAN1A terminal can be used only for communication with ECU
CAN1B terminal can be used only for communication with IO Modules
IMPORTANT: In case that CAN1 ECU/IOModules Split (page 394) is enabled, the Hot Swap
Redundancy (page 364) is disabled (and vice versa).
Image 5.65 CAN1 ECU/IO Modules Split connection
Note: The splitting of CAN1 enables to prevent overloading the bus line.

5.4.9 Configuration Lock
The Configuration lock function allows the user to lock the the Controller Configuration by the password and
encrypt the PLC data. The Controller Configuration can be locked by the checkbox Configuration Lock inside of
the Controller Configuration next to the button Consistency check. Once the checkbox is hit, the user will be
asked for the password, after this step all PLC data will be encrypted. Once the user will try access to the locked
Controller Configuration, the InteliConfig will automatically ask the user for the password. If the correct password
is submitted the Controller Configuration will be unlocked and PLC data decrypt. Without correct password the
user cannot open the Controller Configuration and see configuration in it.
Image 5.66 Configuration lock
5.4.10 Configuration Override

There may appear a situation, when controller reprogramming is not possible for some reason. The typical
example is a situation, when the controller is configured to be always in Remote AUT mode. So, the controller
cannot be switched to OFF mode to change the configuration. To enable controller configuration change in these
cases, the InteliNeo 6000 is offering a DIP switch located under the front cover of the controller. If the switch is
enabled the controller configuration is forced to the invalid state so it is possible to upgrade the controller's FW or
import new configuration. The older controllers are using the boot jumper to do the same thing and it is called
"Boot Jumper Programming" or "Unsuccessful Controller Programming".
Process of configuration overriding

Remove front cover of InteliNeo 6000
Enable the DIP switch
Restart the controller
Connect to the controller via InteliConfig
Log-in as level 3 user
Go to the Control and Import new configuration (button Configuration Import)
Disable the DIP switch

Image 5.67 Location of the DIP switch for Configuration override
5.4.11 Control Groups

Note: This chapter is relevant for all ComAp controllers working in Multiple Island-Parallel operation.
The physical group of the controllers (i.e. the site) can be separated into smaller logical groups, which can work
independently even if they are interconnected by the CAN2 bus. The logical groups are intended to reflect the
real topology of the site when the site is divided into smaller groups separated from each other by bus-tie
breakers. If the bus-tie breakers are closed the sub-groups have to work as one large group (system) and if the
bus-tie breakers are open, the sub-groups have to work independently.
The group which the particular controller belongs to is adjusted by the Control Group (page 507). Use
the default setting 1 with all controllers, if there is no bus-tie breaker.
The information which groups are currently linked together is being distributed via the CAN. Each
controller can provide information about one BTB breaker. The breaker position is detected by the input
function GroupLink (i.e. this input is to be connected to the breaker feedback).
The two groups which are connected together by the BTB, are defined with parameters Group Link L
(page 508) and Group Link R (page 508). BTB controller sends via CAN2A (page 19) (CAN2B (page
19)) information that controllers from groups Group Link L and Group Link R are linked together.
If external BTB is used (there is no CAN communication between external BTB and other controllers) or in
case of redudant information about BTB position is required , the Group link function in any ComAp
controller can be used. If the LBI GROUP LINK (PAGE 893) is activated the controller will send information to
all controllers on CAN that the groups defined by setpoints Group Link L (page 508) and Group Link R
(page 508) are connected together.
A history record is written into every controller that is affected by the group link whenever the BTB is
closed / opened (control groups are linked / unlinked).
Note: The "group link" function is independent on the group, where the controller itself belongs to. The controller
can provide "group link" information about any two groups and it may not belong to one of the groups.
All controllers in linked groups cooperate with each other and perform Power Management, Load sharing
and VAr sharing together. Thementioned functions are performed independently in each group, when the
groups are separated.

Example: 4 controllers separated by a BTB breaker into two groups of 2. The BTB position is detected by
the controllers 2 and 3. The reason, why there are 2 controllers used for detection of the BTB position, is to
have a redundant source of the group link information, if the primary source (controller) is switched off.
Image 5.68 Example of control groups
Once the BTB breaker is closed, the control groups 2 and 3 become new group 2+3. Power management, Load
sharing and VAr sharing are performed within newly established group 2+3. Merging of the groups may result in
a BESS/BESS stopping, if power management evaluates that available Actual Reserve is high enough to stop a
BESS/BESS.
5.4.12 Crash Dump

Crash dump is new functionality which allows controller to collect and store important information related to
controller's failure before the controller is restarted. These information are stored in controller's nonvolatile
memory for later evaluation and easier solution of a problem.
Collecting crash dump

To collect Crash Dump from the controller, you need to connect to the controller using InteliConfig either via USB
(page 112) or Ethernet (page 113).
Log in as user with administrator rights.
In top right corner click wrench icon and select "Collect logs".
InteliConfig begins to collect Crash Dump data from the controller and also adds its own crash logs. User
is informed about the ongoing process in InteliConfig, before prompt to save *.zip file appears.

Image 5.69 Crash Dump Collection
Note: It is recommended to use connection via Ethernet to reduce time required for data collection.
IMPORTANT: This action may take significantly long period.
Contacting TSUP with crash dump

After collection of Crash Dump, you shall contact TSUP. To help resolve your issue:
Send description of the issue from your side of view
Send approximated time of the event
Send Crash Dump data collected in *.zip file
5.4.13 Distributed Power Management Signals

Note: This chapter is relevant for all ComAp controllers working in Multiple Island-Parallel operation.
Note: In case the InteliNeo6000 cooperates with controllers which CAN Intercontroller Comm Mode (page
389) doesn't support 64C CAN FD, the maximum units in power management is 32.
Signals which are considered to be visible the same way for every controller on CAN. Synchronization of these
signals is the internal part of the Power management function.
Basic principle:
For every signal, there is a LBI with the same function as the signal.
If the LBI is not configured on any input (physical binary, virtual in PLC etc.), its value is taken from CAN
and the value is not being shared back on CAN.
If the LBI is configured, its value is taken from the input and the value is shared on CAN.
The relevant function is activated only by the state of the signal, which is configured on LBI. That
means that function cannot be activated by the state of relevant CAN signal.
In case of the collision, there is a predefined behavior. If any controller with configured LBI receives a
logical "1", it then activates the signal on CAN.
Distributed Power Management Signals are shared only in the scope of logical Control Groups (page
136). If you merge Control Groups together (GROUP LINK (PAGE 893)), signals are applied in both groups.
The BTB controller is used to connect the groups together. When the Bus Tie Breaker is closed the BTB
informs appropriate controllers that their groups has been connected.

Description for the BESS/Microgrid
Distributed signal Description for Mains controller
controller (MINT application)
LBI REMOTE START/STOP Accepted only in controllers
(PAGE 915) is the request to belonging to the same logical
start the group (part of the group.
system). It is shared to LBO Accepted only in controllers where
System Start/Stop System Start/Stop and the Distributed signal is not
distributed trough CAN2A configured.
(page 19) or CAN2B (page 19) If the Distributed signal is
to the controllers in the same
configured to any binary input
group.
(physical or virtual), the signal is
automatically shared to other
Min Run Power 1, controllers via CAN2A (page 19) or
2, 3 CAN2B (page 19) as CAN
Distributed signal.
N/A
If distributed signal is shared on
Load Reserve 1, 2, CAN2A (page 19) or CAN2B
3, 4 (page 19) by more sources, it is
accepted from any of them.
The Mains controller set this
Accepted only in controllers
signal on whenever there is a
belonging to the same logical group
closed path between the Mains
as the source Mains Controller only.
MCB Feedback and the Load side.
Accepted only in controllers where
The signal is shared only inside
the Distributed signal is not
the logical group (or
configured.
interconnected logical groups).

Distributed
Scheme for Mains + Gen-set/Microgrid controllers
signal
System
Start/Stop
Min Run
Power 1, 2, 3
Load Res 1,
2, 3, 4
Sharing of multiple Logical Binary Input (LBI) functions is critical for power management system operation,
because several power management functionality require simultaneous activation of LBI functions in controllers,
which are involved in power management operation. It can be done either automatically using CAN2A (page 19)
(CAN2B (page 19)) bus link between controllers or using dedicated LBI functions.
These LBI functions are shared automatically:
System Start/Stop
Min Run Power Act
Load Res Active
MCB Feedback
The following rules applies to the automatic sharing of the selected signals between Mains / Gen-set /
Microgrid controllers.

1. LBI state is automatically shared via CAN2A (page 19) (CAN2B (page 19)) bus, if corresponding LBI
function is not configured in a controller.
Example: Logical input Remote Start/Stop is configured with a controller. State of the signal is
automatically transmitted to other controllers via CAN2A (page 19) (CAN2B (page 19)) bus as System
Start/Stop.
Image 5.70 Distributed signals case 1
2. LBI state received from CAN2A (page 19) (CAN2B (page 19)) bus is automatically used, if corresponding
LBI function is not configured in a controller.
Example: LBI Remote Start/Stop is not configured with a controller, but automatically shared System
Start/Stop is received from CAN2A (page 19) (CAN2B (page 19)) bus. Controller follows state of the
shared LBI signal then.
Image 5.71 Distributed signals case 1&2

3. LBI state received from CAN2A (page 19) (CAN2B (page 19)) bus is not used, if corresponding LBI
function is configured in a controller.
Example: LBI Remote Start/Stop is configured with a controller. Controller follows only state of signal
linked with the Remote Start/Stop function. The function is not activated by a shared System Start/Stop
signal.

4. LBI function state transmitted via CAN2A (page 19) (CAN2B (page 19)) bus is used only by controllers,
which are in the same group as controller, which is source of the shared signal. Signal coming from controller
in a different group is accepted only if the “source controller” group is linked with the “receiving controller”
group.
5. LBI function can be configured with multiple controllers, which transmit through CAN2A (page 19) (CAN2B
(page 19)) bus state of the function. Or function applies to the function evaluation in controllers, in which the
function is not configured. It means that function is activated by shared signal coming from any controller (rule
4. applies).
5.4.14 E-STOP
The E-Stop is mainly used for emergency stop of the BESS but it is also used as power supply for binary outputs
1 and 2. These binary outputs are designated for some essential functions and they are internally wired as "safe".
It means, that their deactivation is directly binded with the dedicated Input ㉓ E-STOP (page 48) (not evaluated
as the LBI in the controller). These outputs are fully configurable and in the default configuration are used for the
BESS Run Request.
The emergency stop circuit must be secured.
No accidental activation on the PCB can disable the operation of the emergency stop.
The power supply of the associated binary outputs (BOUT1 and BOUT2) is supplied by the ㉓ E-STOP
(page 48) input, not by the + battery voltage.

Note: There is no difference in the way of configuration of all binary outputs. Binary output BO2
(BESS Run Request) is intended for this function (not dedicated).
The CU is measuring actual input voltage of the E-STOP which activation level depends on the actual controller
supply voltage (battery voltage). The E-STOP is activated if input voltage drops below approximately 60 % of the
Controller supply voltage.
Image 5.74 SW principle of E-STOP
If the input voltage of E-stop is higher than high comparison level (for ex. higher than 80% of the supply
voltage), then E-stop is not activated.
If the input voltage of E-stop is lower than low comparison level (for ex. lower than 60% of the supply
voltage), then E-stop is activated.
If the input voltage of E-stop is located somewhere between low and high comparison levels (for ex.
between 60 and 80 %of the supply voltage, then E-stop binary value will stay on its previous state (means
E-stop binary value will not change).
Visualization on CU screen
1
㉓ E-STOP (page 48) has voltage - state is OK, BO1 and BO2 can be activated
0
㉓ E-STOP (page 48) has no voltage - E-STOP (page 1114) is active, BO1 and BO2 cannot be
activated
For wiring information see E-Stop on page 67.

5.4.15 Event History
The history log is an area in the controller’s non-volatile memory that records “snapshots” of the system at
moments when important events occur. The history log is important especially for diagnostics of failures and
problems. When the history file is full, the oldest records are removed.
Each record has the same structure and contains:
The event which caused the record (e.g. Overfrequency alarm, undervoltage alarm, MCB closed, BCB
closed, etc.).
The date and time when it was recorded.
All important data values like frequency, kW, voltages, etc. from the moment that the event occurred.
The number of events is fixed to 1000 lines.
Values are recorded based on actual column selected, on special events values are recorded in text form.
Special events:
When the user logs in
Modifying a setpoint
Fault Reset
Horn Reset
Start/Stop
Configurable history
It is possible to configure the columns (values) which will be displayed in the History window. The
configuration can be found in the Controller Configuration → Others → History. See the picture below.
Image 5.75 Configurable history
In the left part of the configuration window there are all available binary and analog values (columns) which
can be configured to history event log. In the right side of the configuration window there is a table with all
already configured columns. By buttons Add and Remove in the middle of the configuration window or by

double click on value in the left / right part of the configuration, it is possible to add / remove any analog or
binary value to / from the history event log.
Under the table with already configured values there are buttons for the operations. By the buttons Move up
and Move down it is possible to change the position of the history columns so you can sort all columns
according to your priorities. Next to these buttons there are buttons for export and import data so you can
import history columns configuration from another controller. And it is also possible to change the
abbreviation for each history column. In the down part of the configuration window there is a progress bar
which shows how much memory for history events is used. For one history record maximum 499 Bytes can
be used.
In the next chapter are shown history columns used in the default archive.

Default history columns
Category Column Name Value Unit
Info Mode Controller Mode (page 777) -
Controller I/O VBat Battery Voltage (page 759) V
Pwr BESS P (page 664) kW
Pwr1 BESS P L1 (page 664) kW
Q BESS Q (page 665) kVAr
Q1 BESS Q L1 (page 665) kVAr
PF BESS Power Factor (page 667) -
LChr BESS Load Character (page 667) -
PF1 BESS Power Factor L1 (page 667) -
LCh1 BESS Load Character L1 (page 667) -
BESS LCh2 BESS Load Character L2 (page 668) -
LCh3 BESS Load Character L3 (page 668) -
Gfrq BESS Frequency (page 670) Hz
Vg1 BESS Voltage L1-N (page 670) V
Vg12 BESS Voltage L1-L2 (page 670) V
IL1 BESS Current L1 (page 672) A
IEFC Earth Fault Current (page 673) A

Mfrq Mains/Bus Frequency (page 731) Hz
Vm1 Mains/Bus Voltage L1-N (page 731) V
Vm12 Mains/Bus Voltage L1-L2 (page 732) V
Mains/Bus
Im Mains L1 Current (page 734) A
PwrM Mains Import P (page 734) kW
Qm Mains Import Q (page 735) kVAr
PFm Mains PF (page 737) -
LChm Mains Load Character (page 737) -
Pld Load P (page 720) kW
Qld Load Q (page 720) kVAr
Load
PFld Load Power Factor (page 720) -
LCld Load Character (page 720) -
Ain1 CU-AIN-01 (page 759) -
Controller I/O Ain4 CU-AIN-04 (page 760) -
BIN Binary Inputs (page 760) -
ESTP E-STOP (page 761) -
BOUT Binary Outputs (page 761) -
Frequency/Load Control SRO Frequency Regulator Output (page 754) V
Voltage/PF Control VRO Voltage Regulator Output (page 758) V
Forced Values Status FVST Forced Value Status (page 782) -
PoF P Over Frequency Curve (page 721) %
PuF P Under Frequency Curve (page 722) %
Qum Q(Um) Curve (page 722) kVAr
QrUl Qref/Ulim Curve (page 722) kVAr
Q(P) Q(P) Curve (page 723) kVAr
Grid Codes
PFp PF(P) Curve (page 723) -
Red1 Load Reduction 1 Occurrence (page 724) -

Prio BESS Priority (page 748) -
ResA Actual Reserve (page 748) kW
TRPN Running Nominal Power Of All (page 751) kW
Power Management
APN Available Nominal Power (page 751) kW
Minimal Running Nominal Power (page
Pmin kW
751)
Premortem History
The fast history running in background is mirrored into the controller history records when a second level alarm
occurs. Premortem history contains the same values in the history as the configuration done by configuration
tool. When any new alarm appears for the second time, only the new history records are added into the controller
history log. Premortem History is filled in to internal buffer (16kB) and number of premortem records depends on
how many history columns is configured. Example: for default History columns it can be up to 85 premortem
records, for maximal History columns can be saved in to buffer at least 32 records.
The time of the premortem history is adjustable by a setpoint Premortem History Period (page 615)
5.4.16 Exercise Timers

Mode Once 151
Mode Daily 152
Mode Weekly 153
Monthly mode 154
Mode Short period 156
The exercise (general-purpose) timers in controller are intended for scheduling of any operations such as e.g.
periodic tests of the BESS, scheduled transfer of the Load to the BESS prior to an expected disconnection of the
Mains etc. These timers can be also used in the PLC.
The function of each timer can be changed by respective Timer Function setpoint. The functions which are
supposed to change the Controller Mode requires controller running in AUTO mode. The following timer
functions are available:
Disabled - The Timer is disabled.
Manual On - The Timer is disabled but his binary output is activated (can be used for testing purposes).
No Func - There is no any other function, only binary output of the Timer is activated once the condition is
fulfilled.
Mode OFF - The binary output of the Timer is internally connected to the Remote OFF binary input.
The activation condition of each Timer is configured via respective Timer Setup setpoint.
Each Timer has its LBO Exercise Timer which is closed regardless of chosen timer function once the Timer is
activated. If the CU is switched off when the Timer should be activated, the Timer will be activated immediately
after the CU is switched on if the Timer condition is still fulfilled. The LBO is activated always when the Timer
should be activated e.g. even when controller is in different mode than AUTO.
See the list of related setpoints and LBOs below.
Related setpoints for choosing of the timer function: Related setpoints for the timer setup:
Timer 1 Function (page 617) Timer 1 Setup (page 618)

Timer 11 Function (page 637) Timer 11 Function (page 637)
Related LBOs:
Exercise Timer 1 (page 946) Exercise Timer 7 (page 947)
Exercise Timer 7 (page 947)
Exercise Timer 9 (page 948)
Related Values:

Note: This manual shows step by step guide only for Timer 1 setup because the procedure is same for the all
timers.
Available modes of each timer:

This is a single shot mode. The timer will be activated only once at preset date/time for
Once
preset duration.
The timer is activated every "x-th" day. The day period "x" is adjustable. Weekends can be
Daily excluded. E.g. the timer can be adjusted to every 2nd day excluding Saturdays and
Sundays.
The timer is activated every "x-th" week on selected weekdays. The week period "x" is
Weekly
adjustable. E.g. the timer can be adjusted to every 2nd week on Monday and Friday.
The timer is activated every "x-th" month on the selected day. The requested day can be
Monthly selected either as "y-th" day in the month or as "y-th" weekday in the month. E.g. the timer
can be adjusted to every 1st month on 1st Tuesday.
Short The timer is repeated with adjusted period (hh:mm). The timer duration is included in the
period period.
Mode Once
Set-up via InteliConfig
To set-up timer via InteliConfig go to the setpoint ribbon, setpoint group scheduler and setpoint Timer 1 Setup
(page 618).
Note: Setpoint Timer 1 Setup (page 618) is visible only if setpoint Timer 1 Function (page 617) has any
other value than disabled.
Image 5.76 Mode Once - InteliConfig

In timer mode select Once. In timer settings adjust date and time of occurrence of timer. Also adjust the duration
of timer.
Set-up via external display

Navigate to the Scheduler setpoint group. Select the function of timer via Timer 1 Function (page 617) setpoint.
Then go to Timer 1 Setup (page 618) and press enter button.
Note: Use left and right arrow to move in a single row. Use up and down arrow to adjust time or date. Use
enter button for confirmation.
6 back to Exercise Timers
Mode Daily
(page 618)
Image 5.77 Daily mode - InteliConfig
In timer mode select Repeat. In repetition type select Daily. In timer settings adjust date and time of first
occurrence of timer. Also adjust the duration of each occurrence of timer. Than select the x-th day of repetition
and behavior of timer on weekends.
Example: On image example first start of timer will be 2015-01-01 at 12:00. Duration will be 5 minutes.
Timer will be again activated every 3rd day at 12:00 for 5 minutes including weekends.

Then go to Timer 1 Setup (page 618) and press enter button.
Select mode Repeat and confirm it. After that, you will set the first occurrence date, time of occurrence and
duration. Select Daily occurrence, set amount of days between occurrences and decide which behavior shall be
applied during weekends.
Mode Weekly
(page 618).
Image 5.78 Mode Weekly - InteliConfig
In timer mode select Repeat. In repetition type select Weekly. In timer settings adjust date and time of first
occurrence of timer. Also adjust the duration of each occurrence of timer. Than select the x-th week of repetition
and days when timer should be active.
Timer will be again activated every 2nd week on Monday, Wednesday and Friday at 12:00 for 5 minutes.

Then go to Timer 1 Setup (page 618) and press enter button. Select mode Repeat and confirm it. After that, you
will set the first occurrence date, time of occurrence and duration. Select Weekly occurrence, set amount of
weeks between occurrences and select days which will be timer triggered (use arrows left, right for
activating/deactivating of day and arrow up, down for moving to another day).
Monthly mode
(page 618).
There are two types of monthly repetition. First of them is based on repeating one day in month.
Image 5.79 Mode Monthly - InteliConfig
In timer mode select Repeat. In repetition type select Monthly. In timer settings adjust date and time of first
occurrence of timer. Also adjust the duration of each occurrence of timer. Than select the type of monthly
repetition and the x-th day of repetition. Than select the x-th month of repetition.
Timer will be again activated every 2nd day in 2nd month at 12:00 for 5 minutes.

Second type of monthly repetition is based on repeating days in week in month.
Image 5.80 Mode Monthly - InteliConfig
In timer mode select Repeat. In repetition type select Monthly. In timer settings adjust date and time of first
occurrence of timer. Also adjust the duration of each occurrence of timer. Than select the type of monthly
repetition, the x-th week of repetition and days in week. Than select the x-th month of repetition.
Timer will be again activated every 2nd week in 2nd month on Monday, Wednesday and Friday at 12:00
for 5 minutes.

There are two types of monthly repetition. First of them is based on repeating one day in month.
will set the first occurrence date, time of occurrence and duration. Select Monthly occurrence, then Daily and
choose which day in a month will be timer triggered. Set amount of months between occurrences and confirm the
selection
Second type of monthly repetition is based on repeating days in week in month.
Than go to Timer 1 Setup (page 618) and press enter button. Select mode Repeat and confirm it. After that, you
will set the first occurrence date, time of occurrence and duration. Select Monthly occurrence, then Weekly and
choose which week and week days in a month will be timer triggered. Set amount of months between
occurrences and confirm the selection
Note: Select mode Repeat and confirm it. After that, you will set the first occurrence date, time of occurrence and
duration.

Mode Short period
(page 618).
Image 5.81 Mode Short period - InteliConfig
In timer mode select Repeat. In repetition type select Short period. In timer settings adjust date and time of first
occurrence of timer. Also adjust the duration of each occurrence of timer. Than select the interval of repetition
(shorter than 1 day).
Example: On image example first start of timer will be 2015-01-01 at 12:00. Duration will be 1 hours.
Timer will be again activated every 4th hour for 1 hour.

will set the first occurrence date, time of occurrence and duration. Select Period occurrence, then set period of
repetition (shorter than 1 day).
Note: Select mode Repeat and confirm it. After that, you will set the first occurrence date, time of occurrence and
duration.

5.4.17 Firewall
The firewall function allows to restrict the access to the controller application services (ComAp/TCP server,
MODBUS/TCP server etc.), to the specific computers, or networks using Ethernet 1 (page 19) and Ethernet 2
(page 19) ports. The firewall can be enabled by the setpoint IP Firewall in the Group: ETH Interface 1 - Trusted
(page 398) and Group: ETH Interface 2 - Untrusted (page 404). The firewall settings is made in the
InteliConfig: Control → Controller Configuration → Others → Firewall.
Example:
Adress: 192.168.1.0
Netmask: 255.255.255.0
Port: 23
Any computer with IP address from the network range 192.168.1.0 - 192.168.1.255 can connect to
ComAp/TCP server (= connect to the controller with InteliConfig via Ethernet).
Example:
Adress: 192.168.1.100
Netmask: 255.255.255.255
Port: 502
Only the single computer with IP address 192.168.1.100 can connect to MODBUS/TCP server
IMPORTANT: When enabling the firewall, If the rules are not set up properly and the connection is
made remotely, loss of connection can happen.

5.4.18 Forced Value
This function allows forcing of preconfigured value into selected setpoints via activation of LBI. Each LBI can
force only one value into one setpoint. There are 32 LBIs - FORCED VALUE INPUT 01 (PAGE 887) ... FORCED VALUE
INPUT 32 (PAGE 893). You can see current states of all LBIs in value Forced Value Status (page 782). Setpoints
for which is Forced Value already configured are marked with gray arrow in InteliConfig and on display.
Note: LBIs can be renamed during configuration. We suggest you to rename them based on used function.
IMPORTANT: You cannot change value of setpoint which has active Forced Value function.
Force Value Indication

setpoint value.
InteliVision 5.2
Image 5.82 : Force Value and Protected Setpoint Indication
InteliConfig
Image 5.83 : Force Value Indication in InteliConfig
Note: Setpoints that are currently being forced their arrow turns to green color and they also have the option
for writing of different value manually disabled.
Forced Value Priority

One setpoint can have multiple configured Forced Values which are ordered from highest to lowest
priority (1 .. 32). In case of conflict highest priority value, which is valid, is used.
In case that Forced Value is out of setpoint's range, value is capped by either maximal or minimal limit or
respective setpoint.

In case that Forced Value is invalid (see Invalid flag (page 652)), another active Forced Value is used
based on priority order. If there is not any other active (or configured) Forced Value which could be used,
the setpoint keeps it's value.
setpoint value.
InteliVision 5.2
Image 5.84 : Force Value and Protected Setpoint Indication in IV 5.2
InteliConfig
Image 5.85 : Force Value Indication in Inteli Config
Note: Setpoints that are currently being forced their arrow turns to green color and they also have the option
for writing of different value manually disabled.
Configuration of Forced Value

Forced Value can be configured only via InteliConfig during standard configuration of the controller and only for
selected setpoints. Setpoints to which Forced Value can apply are marked with flag button. Clicking that button
opens pop-up window containing all already configured Forced Values conditions. Priority of configured Forced
Values is given by order and is descendent - first row has highest priority.

Source from which is setpoint going to be forced. Source has to have same resolution and
dimension as target setpoint.
Name of LBI which activates the Forced Value
Note: This can be also changed in Controller Configuration - Functions
Used trigger which is connected wit Forcing LBI.
List of already configured Forced Values for specific setpoint. First row has highest priorit.
Options for adding, removing and editing Forced Values and options for changing order.
5.4.19 Hot Swap Redundancy

Essential signals and wiring diagram 161
Hot Swap – step by step 163
IMPORTANT: This is a premium function which requires SW Key in order to be used!
Hot Swap Redundancy is a feature designed to increase the reliability of the control system. Its principle is
based on the fact that the control system consists of two pair controllers, "MASTER" and "BACKUP". The
BACKUP controller is ready to take over the control of the BESS anytime when MASTER controller fails.
Assumptions: We assume that both pair controllers have the same information about the controlled system that
they obtain through their inputs and communication lines. This information is supplemented by so-called
synchronization data, which the MASTER controller sends via the Hot Swap Synchronization Line. The second
fundamental assumption is that both controllers have the same configuration in terms of control functions.
Detection of failure of the pair controller and speed of the transition: The BACKUP controller evaluates
the competence of the MASTER controller via a heartbeat signal. Due to its high frequency BACKUP is able to
detect MASTER failure quickly enough to be able to respond in a way that the entire system does not register the
transition to BACKUP at all. This usually happens approximately in 3 ms. The LBO Hot Swap Heart Beat of
MASTER controller must be interconnected with the LBI Hot Swap Heart Beat Detect of the pair BACKUP
controller and vice versa. So, both controllers monitor each other and they are ready to respond accordingly.

Essential signals and wiring diagram
Note: This is a set of recommendations to ensure maximum reliability of the Hot Swap system. The actual
configuration may vary from case to case.
Image 5.86 Wiring diagram and recommended connection
Polarity of binary inputs: The polarity of the Hot Swap Heartbeat pulse signal requires that the controller
binary inputs has to be set to the "Pull Down" configuration.
Hot Swap Heartbeat and other control signals

Hot Swap Heartbeat - The LBO HOT SWAP HEARTBEAT (PAGE 952) of MASTER controller must be
interconnected with the LBI HOT SWAP HEARTBEAT DETECT (PAGE 895) of the pair BACKUP controller and
vice versa.
Hot Swap Switch - The function of Hot Swap necessarily requires the configuration of the LBO HOT
SWAP SWITCH (PAGE 952) signal on the armature of relay Km / Kb , which ensures turn over or
disconnection of technology inputs / outputs and communication lines. It is possible to use multiple pole
relays and combine more control signals together or use a number of independent relays powered by a
common physical output of the controller. Then it is necessary to keep the maximum permissible load of
one output, or to divide the LBO HOT SWAP SWITCH (PAGE 952) function among several physical binary
outputs. Alternatively use one central Hot Swap Switch relay designed to supply all other control relays.
The Hot Swap functionality necessarily requires the configuration of the LBI HOT SWAP CTRL BLOCK
(PAGE 895) input on both paired controllers. The input is to be handled by the LBO HOT SWAP SWITCH

(PAGE 952) signal of the pair controller and ensures the switching of the controller that has been evaluated
as defective to a state where it cannot effect the technology control.
Interconnection of inputs and outputs of Hot Swap pair controllers

Configuration of inputs to polarity "Pull Down" in combination, where inputs and outputs of controllers are
interconnected further requires galvanic separation with optocouplers or connection of anti-series diodes
to controller outputs. For more information see Binary Inputs (page 65) and Binary Outputs (page 66).
Powering
We recommend a 24V power supply system for the Hot Swap system. The MASTER and BACKUP
controllers should be powered from an independent source.
Binary inputs
The binary inputs (with the exception of the control binary inputs of the Hot Swap function) always lead to
both pair controllers at the same time, in the same position without the need of separation by relays. They
must be set to "Pull Down" polarity on both controllers.
Binary outputs
It is strongly recommend to connect the binary outputs controlling the technology via a pair of relays with a
disconnecting function. This ensures that a controller that is defective cannot disturb the operation of the
application under any circumstances.
Analog inputs
The analog inputs must be connected via paired relays with a switching function. The exception is the
configuration where the analog inputs are set as voltage 0-10 V.
Analog outputs
The analog outputs controlling the technology, namely AOUT1 and AOUT2, must be connected via a pair
of relays with a switching function.
Communication lines
Technological lines CAN1A (ECU and I/O modules), CAN2A (Intercontroller Communication), CAN2B
(Rendundant Intercontroller Communication). These lines are recommended to be connected to both pair
controllers via relays with disconnecting function.
The ETHERNET 3 (technology line with function Modbus Client) is connected to both controllers in the
classic way at the same time. The IP address of the pair controllers on this line must be different. In the
case of using the hotswap function, it will happen that when the master controller fails, backup controller
will start taking care of the device on the modbus. Hotswap function is only possible if the Modbus master
is connected via Ethernet (TCP). Both controllers read the same values via modbus, but only one writes.
At the moment of switching to backup controller, the roles of writing and controlling are changed.
Terminal lines ETHERNET 1, ETHERNET 2 are connected to both controllers in the classic way at the
same time.
RS485 (Modbus Server/Master communication) is connected to both controllers in the classic way at the
same time. Both pair controllers has different device address on this line. In case of connection via RS485
there is no possibility to use hotswap. It is not possible to read from two devices and write at the same
time.

Hot Swap Synchronisation Line
MASTER AND BACKUP has to be interconnected via so called Hot Swap Synchronisation Line. Actually
it is point to point interconnecting of CAN1B communication ports via this synchronization is performed.
Even in the event of a failure of this line, BACKUP is ready to take control of the system, but a completely
smooth transition can no longer be guaranteed.
Display
The Hot Swap system does not support a common display for both paired controllers. Each controller is
equipped with its own display.
Fault Reset
The Fault Reset button signal is not propagated from MASTER to BACKUP automatically. It is
recommended to set the connection in a configuration where the LBO FLTRES BUTTON ECHO (PAGE 949)
of MASTER controller handles the LBI FAULT RESET BUTTON (PAGE 886) of BACKUP controller.
Alternative configuration with disconnection of the MASTER controller from the

power supply:
Wiring and configuration described above is recommended however it may follow the specific
requirements of the installation. Instead of using disconnecting relays, it is also possible to disconnect the
MASTER controller completely from the power supply. However, the shutdown of the MASTER controller
is then bit slower and there is a higher risk of unwanted intervention of the faulty MASTER controller in the
control process. In this case, it is not possible to perform a system recovery without a hard reset of both
controllers at one time. We do not recommend this connection, however, the above recommended
connection can be extended by disconnecting the MASTER controller from the power supply.
6 back to Hot Swap Redundancy
Hot Swap – step by step

If we have a ready HW configuration according to the diagram, we can proceed to put the Hot Swap function into
operation. In this chapter, we will walk you through all the steps to run up the Hot Swap system and explain how
to solve several problems that you could be heading.
The configuration and commissioning of the Hot Swap system:
1. SW key
a. The Hot Swap function is conditioned by software licence - SW Key. The apropriate SW Key must be
inserted to the setpoint SW Key (page 381).
2. Base configuration
a. Check that the signals LBO HOT SWAP HEARTBEAT (PAGE 952) and LBI HOT SWAP HEARTBEAT
DETECT (PAGE 895) are properly configured – crosswired between MASTER and BACKUP.
b. It is also necessary to configure the LBO HOT SWAP SWITCH (PAGE 952) signal and the LBI HOT
SWAP CTRL BLOCK (PAGE 895) signal to the corresponding binary output / input - again crosswired
between MASTER and BACKUP.
c. These signals can be configured for any binary output and binary input of the controller (they must
not be configured on peripheral or virtual modules). The binary inputs must be configured in "Pull
Down" mode. This polarity must then be taken into account when designing the entire control
system. Failure to comply with this configuration causes that the Hot Swap function is not working
and it is Disabled.

d. If any mandatory LBI or LBO is not correctly configured the alarm Wrn Hot Swap Configuration
Incorrect (page 1087) is activated.
3. Setting of the setpoints
a. Set the setpoint Hot Swap Redundancy (page 364) = Master on the controller that is to perform the
MASTER role, and set this setpoint = Backup on the controller in the BACKUP role. MASTER and
BACKUP share the same address, set the setpoint CAN Controller Address (page 385) in the
same way. Pay attention, changing the settings of all the above setpoints will not take effect until both
controllers are power cycled. Verify the configuration and settings by setting the system to the
"default state", ie the MASTER controls the system, the BACKUP is ready to take over the control.
b. In case of using two sets of I/O modules (modules redundancy), set the setpoint Hot Swap
Redundancy (page 364) = Master + Modules Redundancy for MASTER controller and Backup +
Modules Redundancy for BACKUP controller. The rest stays the same as above.
4. From the point of view of the control system
We want the hot swap system to behave as one device - one control system. For this reason, we set the
CAN Address on the Intercontroller CAN line Setpoint CAN Controller Address (page 385) on the
MASTER and on the BACKUP controller identically. This ensures a smooth transition in terms of Load /
Var sharing, Powermanagement and virtual peripheries. On the contrary, from the point of view of
monitoring, it is necessary to distinguish both devices from each other. The address for Monitoring via
RS485 is set using the setpoint Terminal Comm Address (page 385). This communication line is
therefore permanently connected to both controllers and it is not necessary to switch it over the pair
controllers.
5. Resetting the Hot Swap System to the default state
It is possible to reset the system by power-cycling of both controllers. Disconnect the power supply from
both pair controllers, first connect the power supply to the MASTER controller, then connect the power
supply to the BACKUP controller. If the base configuration is OK, the alarmilist on the MASTER or
BACKUP should not contain any alarm related to Hot Swap. Check the value Hot Swap Redundancy
Status (page 784), to confirm that the Hot Swap system is in the default state. The basic check of the
default state can be easily performed by changing the Controller Mode on MASTER controller. Controller
mode can be changed only from the MASTER controller. BACKUP then only reflects this state and it is not
possible to change its Controller Mode directly.
6. Hot Swap Recovery
If the Wrn Master Controller Failed (page 1089) or Wrn Backup Controller Failed (page 1084) alarm
is present in the Alarmlist of one of the controllers, it means that the pair controller was not detected
correctly according to the Hot Swap Heartbeat signal. The cause is probably a faulty configuration or
wrong wiring. Check the wiring and configuration of the LBO HOT SWAP HEARTBEAT (PAGE 952) and LBI
HOT SWAP HEARTBEAT DETECT (PAGE 895) signals. If everything is OK, reset the Hot Swap system. This
can be achieved without the need to restart both controllers using the LBI HOT SWAP RECOVERY (PAGE
895). The LBI responds to the edge, so a pulse needs to be applied to inputs of the both controllers at one
time.
7. Performing the Hot Swap function
If the Hot Swap system is in the default state, we will perform a Hot Swap function test. Interrupt the Hot
Swap Heart Beat signal leading from the MASTER to BACKUP. The alarm Wrn Master Controller
Failed (page 1089) appears in the alarm list of the BACKUP controller and BACKUP actively takes over
the control of the system. In all consequences it means that:
a. BACKUP activates the LBO HOT SWAP SWITCH (PAGE 952), which controls all relays according to the
diagram. The MASTER is disconnected from all critical lines and signals and the other signals

(Analog inputs and Analog Outputs) are switched to the BACKUP controller. At the same time, with
this signal, the Master controller is switched to the so-called Listening Mode using its LBI HOT SWAP
CTRL BLOCK (PAGE 895). This mode ensures that the MASTER will be silenced on the CAN
communication lines and thus will not collide with the data that is already being sent by BACKUP for
this purpose.
b. At this point, BACKUP switches from listening mode to Talking Mode, thus representing the Hot
Swap system on CAN communication lines.
c. Have a look at value Hot Swap Redundancy Status. The individual signals now correspond to a
situation where the system has successfully entered a state where BACKUP is in the role of who
controls the system.
Note: In case of using two sets of I/O modules (modules redundancy): Failure of one of the Master’s CAN
modules causes the Hot Swap – the Backup controller takes over the control of the system.
Failure of one of the Backup’s CAN modules causes: Master considers Backup to be dead (therefore the
Backup is no longer available for the Hot Swap function).
8. Smooth transition to Backup

When the BESS is running or is loaded while the MASTER controller fails, then the BACKUP should take
over the control of the BESS smoothly without any bumbs on the frequency, voltage and power values,
even in dynamic states such as loading, unloading or ongoing synchronization. BACKUP will ensure a
smooth transition in the following aspects:
a. ECU communication
b. Serving of CAN peripheral modules
c. Serving of virtual peripheries - Distributed and Shared signals
d. Communication on Intercontroller line - Load Sharing / Var Sharing
9. Hot Swap Synchronization Line
The states of the state automat, Controller Mode, and controller outputs are synchronized via the Hot
Swap Synchronization Line between MASTER and BACKUP controller. In case of synchronization failure
on the Hot Swap Synchronisation Line, BACKUP loses data needed for the smooth transition. If this
happens, BACKUP is internally switched to Emergency Manual mode, where it is still able to take over
control of the system, but a smooth transition can not be guaranteed. The failure of the Hot Swap
Synchronisation Line is accompanied by the following alarms:
a. Wrn Hot Swap Data Synchro Fail (page 1088) - takes place on both the MASTER and the
BACKUP controller in the event of a communication failure on this line. This status is also indicated in
the Hot Swap Redundancy Status value.
b. Wrn Backup Not Ready (page 1084) - This status is indicated by MASTER in the alarm list and in
the value Hot Swap Redundancy Status. This means that BACKUP has an announced 2nd level
alarm, while MASTER does not have such an alarm. Thus, BACKUP is unable to take over control of
BESS. This is a marginal issue that might be caused due to the wrong configuration.
10. Shared setpoints
All setpoints prefixed by "#" character - Due to the identical CAN address of the MASTER and the
BACKUP controller, there is a problem with writing Shared setpoints and it takes these consequences. If
we consider that the Hot Swap system is in the default state then:
a. Inserting a shared setpoint to the BACKUP controller will not be reflected in any of the other
controllers on the CAN (even not in its pair MASTER controller).

b. Inserting a shared setpoint in the MASTER controller will be reflected in all controllers on the CAN
except for its paired BACKUP controller.
IMPORTANT: Ensuring the synchronity of shared setpoints must be ensured by the
operator!
11. Time synchronization

Synchronizing shared setpoints, changing the Time setpoint will not be reflected throughout the system.
Therefore, time synchronization must again be ensured by the operator. With the advantage it is possible
to use the function of time synchronization via SNTP server. This ensures that each controller
synchronizes the exact time independently of the other controllers.
6 back to Hot Swap Redundancy
5.4.20 I/O Configuration

Binary Inputs 167
Binary Outputs 167
Analog Inputs 167
Analog Outputs 168
Functions Configuration 169
Protections Configuration 169
Transfer I/O Configuration 169
Remove I/O Configuration 170
Note: This is only quick illustration for I/O configuration, see the InteliConfig manual for more information
about configuration via PC tool InteliConfig.
Image 5.87 I/O Configuration window

A. Device tree – contains groups of devices with inputs/outputs to configure
B. Configuration panel – the list of available inputs/outputs related to device tree selection
C. Tool bar
Expand All Details - Expands the configuration part of all inputs/outputs
Transfer IO Configuration - see Transfer I/O Configuration on page 169
Remove IO Configuration - see Remove I/O Configuration on page 170
Binary Inputs
The configuration of the binary input consists of:
1. Name - the name identification of the binary input
2. ECU Value - electronic control unit value, available only for ECU devices (otherwise disabled)
3. Functions - the set of functions see Functions Configuration on page 169
4. Protections - the set of protections see Protections Configuration on page 169
Image 5.88 Binary input configuration
Binary Outputs
The configuration of the binary output consists of:
1. Name - the identification name of the binary output
2. Source - the source value for the binary output
3. Contact Type - represents the default state of output (Normally Open/Normally Closed)
5. Protections - the set of protections see Protections Configuration on page 169
Image 5.89 Binary output configuration
Analog Inputs
The configuration of the analog input consists of:
1. Name - the identification name of the analog input
2. Sensor - sensor used for the analog input see Sensor Curves on page 216
3. Dimension - dimension used for analog input (Can be set directly in form if the electronic sensor is
configured, otherwise it can be set in sensor configuration.)
4. Resolution - resolution used for analog input (Can be set directly in form if the electronic sensor is
configured, otherwise it can be set in sensor configuration.)

5. Sensor Range - range used for linear sensor (Range for measured values is defined by Offset + Sensor
Range)
6. Offset - offset used for linear sensor
7. Bargraph 0% - lower bargraph limit displayed on the controller display
8. Bargraph 100% - upper bargraph limit displayed on the controller display
10. History Abbreviation - shortcut used in the History.
11. Functions - the collection of functions see Functions Configuration on page 169
12. Protections - the collection of protections see Protections Configuration on page 169
Image 5.90 Analog input configuration using linear sensor
Image 5.91 Analog input configuration using user sensor
Analog Outputs
The configuration of the analog output consists of:
1. Source - the source value for the analog output
2. Output Curve - definition of the transferring output curve
a. The output curve is not available if the "No Conversion" parameter is checked.
3. No Conversion - Define whether the source value is converted by the output curve or not
4. PWM Frequency - setting of the PWM frequency
a. The PWM frequency can be set only if the output curve is a type of PWM.

Image 5.92 Analog output configuration
IMPORTANT: Output Curves are in Int16 format (range -32768 to 32767). Therefore if the source
value is a decimal value, the range is reduced accordingly.
Example: When BESS Frequency (page 670) (0.001 resolution) is used as a source value, it has to be
converted to a lower resolution in PLC (e.g. 0.01) in order to work correctly. Otherwise the upper level of
the curve's input would be cut to 32.767.
Functions Configuration
It is possible to assign more functions (Logical Binary Inputs) to the specific input (BIN, AIN)
Add new function to the input
Remove function from the input

For the binary input functions the contact type for each function can be set
- Normally Closed/Normally Open
Each function (LBI) has the link to the help through button
Protections Configuration
It is possible to assign one level 1 and level 2 protection to the specific input or output (BINT, BOUT, AIN).
Add new protection
Remove protection
Edit protection
For more information about protections see Protections on page 197
Transfer I/O Configuration

This functionality offers to transfer the whole input/output configuration to another compatible input/output in
the same category. The icon for transfer is available in the bottom toolbar.
After clicking on the transfer icon is displayed window for selecting the target input/output. Offered are only
compatible inputs/outputs of the same category. When the required input/output is selected and confirmed by
the OK button, the transfer operation starts.
Note: The configuration is transferred completely (functions, protections, sensor, PLC configuration) except
Modbus definition.

Image 5.93 The window for selecting the target for I/O configuration transfer
Remove I/O Configuration

This functionality offers to remove the whole input/output configuration. The icon for remove is available in
the bottom toolbar. The name of input/output is after remove set to "Not Used".
Note: The configuration is removed completely (functions, protections, sensor, PLC configuration) except
Modbus definition.
5.4.21 Load Shedding

The Load Shedding is controlled disconnection of less important load groups when the object consumption is too
high.
Load shedding stages

The Load Shedding function consists of 8 stages which are numbered 1-8. Stages are disconnected in
ascending order up to the last configured stage. Reconnecting of stages is in descending order and starts with
higher configured stage. Stage is considered as configured when respective Load Shedding Output is
configured. Highest activated load shedding stage is stored in value Load Shedding Status (page 777).
Load shedding outputs
Stage LBO
Stage 1 LOAD SHEDDING STAGE 1 (PAGE 954)
Stage 2 LOAD SHEDDING STAGE 2 (PAGE 954)-

How the load shedding controls the load shedding outputs

The Load Shedding function can be used if Controller Mode (page 378) != OFF.
Activation of the function is adjusted via setpoint Load Shedding Active (page 592). Function could be active
when:
Entering Breaker state (page 778) = IslOper/MultIslOp - all stages are disconnected.
Change from Breaker state (page 778) = ParalOper/MultParOp
to Breaker state (page 778) = IslOper/MultIslOp - all stages are disconnected.
During Breaker state (page 778) = IslOper/MultIslOp - only one stage is disconnected/reconnected at a
moment
Decisive level for disconnecting of load is adjusted via setpoint Load Shedding Level (page 593) and the
minimal delay between two disconnections is adjusted via setpoint Load Shedding Delay (page 593). When
relative BESS P (page 664) exceeds Load Shedding Level (page 593) and delay Load Shedding Delay
(page 593) elapsed from last disconnection of stage, another stage is disconnected.
Image 5.94 Load shedding

Reconnection of load
Disconnected load can be also reconnected. Reconnecting of stages is in descending order and begins with
highest disconnected stage. Behavior of this function is adjusted via setpoints Auto Load Reconnection (page
595), Load Reconnection Level (page 594) and Load Reconnection Delay (page 594).
Manual reconnection
Conditions:
Setpoint Auto Load Reconnection (page 595) = Manual
LBI MANUAL LOAD RECONNECTION (PAGE 901) has to be configured
When relative BESS P (page 664) drops below Load Reconnection Level (page 594) rising edge of LBI
MANUAL LOAD RECONNECTION (PAGE 901) reconnects the highest disconnected stage.
Note: Setpoint Load Reconnection Delay (page 594) is not considered
Image 5.95 Manual Load reconnection
Auto reconnection
Conditions:
Setpoint Auto Load Reconnection (page 595) = Auto
When relative BESS P (page 664) drops below Load Reconnection Level (page 594) and delay Load
Reconnection Delay (page 594) elapsed from last reconnecting of stage, another stage is reconnected.
Image 5.96 Auto Load reconnection

5.4.22 Loss of Mains (Decoupling) Protections
Vector shift
The vector shift function is the fast protection for Mains decoupling (loss of mains). It monitors the Load angle of
the BESSand if it gets changed dramatically, the protection is issued. The Vector shift is evaluated from the
Mains/Bus Voltage L1-N (page 731).
Protection is enabled via setpoint Vector Shift Protection (page 584) . Limit of protection is adjusted via
setpoint Vector Shift Limit (page 509). When protection is activated, the breaker is opened. Which breaker is
opened is adjusted via setpoint Vector Shift/ROCOF CB Selector (page 513). Maximal value of vector shift is
represented by value Max Vector Shift (page 740).
Note: VectorShift protection gets active (is unblocked) right 500 ms after the condition for activation of protection
gets fulfilled = when Controller goes to parallel to Mains operation (When Vector Shift Protection = PARALLEL
ONLY) or when MCB gets closed (when Vector shift protection = Enabled).
The settings can lead to these situations:
BCB
MCB Vector Vector Shift
STATUS
STATUS Shift/ROCOF CB Protection Action
(PAGE
(PAGE 961) Selector (page 513) (page 584)
931)
Enabled or Opens MCB or BCB based on
1 1 MCB or BCB Parallel Only(no Vector Shift/ROCOF CB Selector
influence) (page 513)
Enabled or
MCB or BCB (no No action (BCB stays always
0 1 Parallel Only(no
influence) closed)
influence)
MCB or BCB (no
1 0 Parallel Only No action (MCB stays closed)
influence)
1 0 MCB Enabled Opens MCB
1 0 BCB Enabled No action (MCB stays closed)
If a vector shift is detected and consequently the MCB is opened, however Mains voltage and frequency remain
in limits, the MCB is then closed again (synchronized) as the Mains is evaluated as healthy.
If a vector shift is detected and consequently the BCB is opened, however Mainsvoltage and frequency remain in
limits, the BCB is then closed again (synchronized) immediately (no delay).
ROCOF
The Rate of Change of Frequency function is the fast protection for Mains decoupling (loss of Mains). It monitors
the change of frequency and if it gets changed dramatically, the protection is issued.
There are in total 4 independent ROCOF protections devided to 2 kinds.
Common behavior
Protections are enabled/disabled by setpoints ROCOF1 Protection (page 585), ROCOF2 Protection (page
586), ROCOF3 Protection (page 587) and ROCOF4 Protection (page 588).

Vector Shift/ROCOF CB
Option Behavior
Selector (page 513)
MCB Protection is reactivated with closing of MCB
Enabled
BCB Protection is reactivated with closing of BCB
Parallel Protection is reactivated with entering Parallel Operation
Not relevant
Only Mode Breaker state (page 778) = ParalOper
Sample based ROCOF

These protections are based on controller's sampling. This means that protection is evaluated after certain
amount of samples have been obtained by the controller.
ROCOF1 Protection (page 585)
Protection is evaluated from last ROCOF1 Windows Length (page 509) samples. If ROCOF1 (page
744) is over ROCOF1 df/dt (page 510), breaker selected by Vector Shift/ROCOF CB Selector (page
513) is opened. Maximal measured ROCOF, from start of evaluation, is stored in Max ROCOF1 (page
745).
Time based ROCOF

These protections are based on specified time period. This means that protection is evaluated from all samples
that have been received in that period.
Protection is evaluated from samples received in last ROCOF2 Windows Length (page 510) period. If
ROCOF2 (page 745) is over ROCOF2 df/dt (page 511), breaker selected by Vector Shift/ROCOF CB
Selector (page 513) is opened. Maximal measured ROCOF, from start of evaluation, is stored in Max
ROCOF2 (page 746).
ROCOF3 (page 747).
ROCOF4 (page 748).

5.4.23 Mains Import Measurement
This functionality is available only when the Application Mode (page 777) = MPTM. The Mains measurement
can be measured by dedicated CT terminals or by analog inputs, and it is divided to Mains Measurement P
(page 357) and Mains Measurement Q (page 358). The Mains Measurement P has to be enabled for proper
work of active power Import/Export. The both measurements has to be enabled for proper work of reactive power
Import/Export and power factor control.
IMPORTANT: The Earth Fault Current Protection (page 583) and Mains Import Measurement
shares same physical input ⑰ AUX CURRENT (page 48) . At one moment this input can be used
only for one purpose. The protection will work only if Mains Measurement P (page 357) and Mains
Measurement Q (page 358) != Mains CT.
Mains Measurement P
If Mains Measurement P (page 357) = Mains CT then Mains Import P (page 734) is counted from the
current which is measured on ⑰ AUX CURRENT (page 48) .
If Mains Measurement P (page 357) = Analog Input then Mains Import P (page 734) is taken from LAI
MAINS MEASUREMENT P (PAGE 992). Mains current can still be measured if Mains Measurement Q (page
358) = Mains CT.
If Mains Measurement P (page 357) = None then Mains Import P (page 734) is not counted because
there is no current measurement. This affects load transfering.
Note: When Mains Measurement P (page 357) is set to None or Analog Input (and LAI MAINS
MEASUREMENT P (PAGE 992) is not configured or has invalid value) alarm Wrn Load IMP/EXP Fail (page
1088) is activated if Import/Export P is required and alarm Wrn PF/Q IMP/EXP Fail (page 1093) is activated
if Import/Export Q is required.
MainsMeasurement Q
If Mains Measurement Q (page 358) = MainsCT then Mains Import Q (page 735) is counted from the
current which is measured on ⑰ AUX CURRENT (page 48) .
If Mains Measurement Q (page 358) = Analog Input then Mains Import Q (page 735) is taken from the
LAI MAINS MEASUREMENT P (PAGE 992). Mains current can be still measured if Mains Measurement P
(page 357) = Mains CT.
If Mains Measurement Q (page 358) = None then Mains Import Q (page 735) is not counted because
there is no current measurement. This affects load transferring.
Note: When Mains Measurement Q (page 358) is set to None or Analog Input (and LAI MAINS
MEASUREMENT P (PAGE 992) is not configured or has invalid value) alarm Wrn Wrn PF/Q IMP/EXP Fail
(page 1093) is activated if Import/Export Q is required.
5.4.24 Modbus Client (Master)

The Controller InteliNeo 6000 is equipped by the function of Modbus Client (Master). Actually it means that
controller can play the role of the device which initiate the modbus communication, i.e. controller can ask and
command other devices being in role of modbus server (slave). In standard terms role of modbus client (master)
on modbus TCP or RTU. The communication protocol with server device is a matter of configuration.

Modbus Client (Master) configuration step by step
Controller is able to communicate with up to 16 devices at one time. The modbus server device is configured like
the ECU module, it is part of Multi ECU configuration. Modbus server devices uses the same pool (resources) for
the inputs and outputs as standard ECUs.
Modbus Server Devices Predefined by ComAp

ComAp offers several predefined Modbus Server Devices. These devices can be found in Standard ECU list
(i.e. under Inverters – Photovoltaic).
Once the device is added into the configuration there are the same options for extending the definitions of
inputs and outputs configuration as for user device. All custom inputs and outputs will be always signed by "
(User)" suffix after the name of the signal. This is the way how to recognize custom definitions from ComAp
definitions which can not be edited and how to prevent creating duplicity signals by user definitions.
User defined Modbus Server Devices
1. Adding Modbus Server Device

Open the Controller Configuration in InteliConfig, go to section Modules, and click on Add New Module in
ECU section. Then under Electronic Control Unit select ECU list - Standard and choose User device -
Modbus - Modbus User Device to define your own device definition. Then confirm the settings by pressing
the button Add Module. Now your modbus server device is added into the configuration.

2. Modbus Server Device Settings
Once the device was added into the configuration you need to edit its setting such as number of each type of
Inputs/Outputs, Device Address, etc. Keep in mind that all devices uses inputs and outputs from the limited
pool common with ECU. Inserting the "Device address" is required for both Connection Types (Modbus RTU
or Modbus TCP).
3. MODBUS Registers (Datapoints) definition

Open the section MODBUS registers for editing or creating new registers (datapoints). The list of registers is
actually a set of definitions belonging to your specific device and has no direct connection to specific control
signals in the controller. So, you can create large set of registers without any limitation. Register defintions for
all devices are integrated into the configuration and uploaded into the controller. Therefore there is no need to

share the "original Modbus Device List" containing all registers, when editing the configuration which was not
created in your computer.
Block of registers reading

As modbus protocol allows reading of block of registers using one operation Modbus Master functionality
offers this option. If possible using of this operation is strongly recomended to decrees the numbers of polls in
modbus communication. The block reading is a matter of the configuration in InteliConfig. It allows to merge
more datapoints into the group or to define each input datapoint directly under this group. The Gropu
eperation (modbus function) is then defined by the first datapoint which was added (or created) inside this
group. Configuration tool automatically construct the modbus poll operation based on the renge of register
adresses inside this group.
Write on change option

For writing operation there is possible to define the Refresh Type parameter which offers these options:
Periodically - The writing operations is performed every period based on the settinfs of Refresh Rate
parameter regardless the real change of the output which is to be written.
On Change - The write operation is only performedon change of output value.
On Change & Periodically - The Write operation is always performed on change as same as
periodically. This allows to set relatively slow refresh rate but accept the change of the output at the same
time.

4. Configuration of Inputs And Outputs
Now, when the definition of your Modbus Server Device was created, go to section I/O Configuration and
assign the specified registers to inputs and outputs. Then assign the functions for inputs and outputs. You can
select from the list of standard logical signals or use your inputs and outputs in the PLC configuration.

5. Clonning of The Modbus Server Device
When using more then one instance of a specific Modbus Server Device in one configuration, or when
needed the Modbus Server Device definition for configuration of another controller, there is a way how to
Export and Import the definitions. Go to section MODBUS registers in Modules and select the icon for
exporting data.
Insert the name and select the target folder for exporting data. You will be informed about successful
exporting of your device definition.
After that select the icon for importing data in a new configuration.
Select one of your Modbus Server Device definition files and Import it into the configuration for a new instance
of your device.
5.4.25 Multiple ECU

InteliNeo 6000 allows you to configure, monitor and control multiple Electronic Control Units (ECUs), such as
Breakers and Modbus modules. At this moment there are 16 ECU slots available, each slot can contain one
ECU/Modbus Master which settings can be separately configured. ECU can be configured via InteliConfig
(Control → Configuration → Modules → Electronic Control Unit).
In order to ensure proper functionality you shall pay extra attention to the ECU settings. ECU address has to be
always unique whereas Controller address is required to be set to the same value as CAN Controller Address
(page 385) of the Controller Unit that sends commands frames to this ECU. Aftertreatment can be enabled only
for one ECU, enable it by using a check box.
ECU I/O can be configured in I/O Configuration.

Controller objects related to ECU
ECU
LBO Alarm
Slot
1 ECU 1 COMM FAIL (PAGE 940) ECU 1 Comm Fail (page 1175)
For each ECU there is LBO which gets activated when communication issue with respective ECU is detected.
For easier detection whether all configured ECUs are communicating, there is LBO ECU COMM OK (PAGE 943).
During detected communication issue an alarm is issued for respective ECU.
All protections which evaluation depends on values from the ECU with communication error are blocked in order
to pervent showing of invalid protections in the Alarm list.
5.4.26 Operating Modes

The operating mode can be selected by pressing Left and Right buttons on the front panel/display, by
changing the Controller Mode (page 378) setpoint, or by activating respective LBI.
Note: If the setpoint is configured as password-protected, the correct password must be entered prior to
attempting to change the mode.
The following binary inputs can be used to force one respective operating mode independent of the mode
setpoint selection:
Remote OFF (page 914)
Remote MAN (page 914)
Remote AUTO (page 913)
If the respective input is active the controller will change the mode to the respective position according to the
active input. If multiple inputs are active, the mode will be changed according to priorities of the inputs. The
priorities match the order in the list above. If all inputs are deactivated, the mode will return to the original position
given by the setpoint.
Another chapter related to the Operating modes is in the Operator Guide see Basic operating modes
description on page 111.

Switching Control Mode
Controller recognize two possible ways to change mode:
Setpoint
Controller mode is selected by Setpoint Controller Mode (page 378). Change of this setpoint will change
controller mode. Terminals such as InteliConfig, InteliSCADA or Displays uses this setpoint to change
controller mode, but they use their own visualization for it.
MODBUS can be used to change this setpoint as well.
LBI
Dedicated LBIs to change mode have higher priority than the setpoint. When LBI is activated th setpoint is
unchanged.
When all LBIs are deactivated controller mode is changed to one that is in Setpoint Controller Mode (page
378).
Signalization of Control Mode

Controller offers two kinds of signalization:
Value
Current controller mode is always show in Value Controller Mode (page 777).
LBO
There is a dedicated LBO for each mode.
MODE OFF (PAGE 963)
MODE MAN (PAGE 962)
MODE AUTO (PAGE 962)
OFF
Start of the BESS is blocked, the controller will stay in Not Ready state, and starting command cannot be issued.
If the BESS is already running, it is not possible to switch directly to the OFF mode. Firstly you have to stop the
BESS and after that switch to the OFF mode.
For MPTM application, if Mains is healthy and MCB is opened, then MCB is automatically closed after the delay
given by setpoint MCB Close Delay.
No Power management function will be performed. The buttons MCB ON/OFF , BCB ON/OFF , START
, and STOP including the appropriate binary inputs for external buttons are not active.
Note: When BESS is running, it is not possible to switch the controller to OFF mode.
MAN
The BESS can be started and stopped manually using the START and STOP buttons (or external buttons wired
to the appropriate binary inputs) if no 2nd level alarm is active. When the BESS is running and BESS parameters
are in the limits, BCB can be closed to a dead bus or synchronization can be started by the BCB button.
The MCB (in case of MPTM application) can be closed and opened manually using the MCB button, if Mains is
present. MCB can be opened manually after Mains failure (it is not tripped in case of Mains failure).
Opening and closing of breakers depends on the setpoint CB Control In MAN Mode (page 355).

Controller does not respond to external signals and/or conditions. The BESS is fully in manual control; there is no
automatic way to stop it (except protections). The BESS stays running until STOP button is pressed. Controller
does not take place in Power Management (page 269) in MINT application.
No AMF or Power management function will be performed.
AUTO
BESS is controlled based on external signal (REMOTE START/STOP (PAGE 915) ) or by conditions (Peak shaving,
Power management system, etc.). When one condition deactivates the BESS does not stop if another condition
for automatic starts is active. System Start/Stop can be received from other controllers via Intecontroller
Communication.
The controller does not respond to the buttons START, STOP, MCB ON/OFF, and BCB ON/OFF.
If peak shaving stop condition occurs, but REMOTE START/STOP (PAGE 915) is active, BESS stays running.
IMPORTANT: If a red alarm is present and the controller is in the AUT mode, the BESS can start by
itself after all red alarms become inactive and are acknowledged (fault reset is pressed)! To avoid
this situation, adjust the setpoint Fault Reset To Manual (page 379) to the Enabled position.
IMPORTANT: BESS will start if at least one external signal or condition is fulfilled.
5.4.27 PLC - Programmable Logic Controller

List of available PLC blocks 185
PLC Editor 186
PLC logic execution rules 192
PLC monitor 193
Other functions 195
The Programmable Logic Controller (PLC) built into the ComAp controllers is generally a simple process unit
used for the automation of processes. The major benefit of the PLC is you don’t need any extra control
devices in your control system. The PLC is tightly integrated with the standard line of controllers. That allows
the PLC editor to be a seamless experience directly in the programming software. Flexibility is at the core of
ComAp's software design and the PLC meets both simple and complex application requirements while using
the same intuitive interface. PLC Editor is a powerful tool that helps you to create your own PLC scheme. It
has a user-friendly graphical interface which makes it easy to use.
ComAp PLC Editor has been developed to help you deal with even the most demanding applications. It
allows you to add control logic, additional alarm functions, or even new features to meet complex or unique
requirements. This easy-to-use PLC Editor means you can customize the way the controller works to match
the application precisely without compromise or limitation.
Intuitive design, visual programming, and easy modification.
All PLC function blocks can be moved both horizontally and vertically.
Color-coded and linked to relevant functions.
Blocks can be organized to reflect the real process flow.
Groups of blocks can be separated on each sheet to form sub-sets within the design.
Detailed descriptions of inputs and outputs come complete with useful hints

Image 5.97 PLC Editor - main page

List of available PLC blocks
In the table below you can find all available PLC blocks.
Group PLC blocks Number of blocks

OR/AND (page 1029) 255
Logical
XOR/RS (page 1031) 255
Comp Delay (page 1032) 16
Comparators Comp Hyst (page 1033) 32
Comp Win (page 1034) 32
Delay (page 1035) 48
Time functions
Timer (page 1037) 8
AxB/C±D (page 1040) 32
Math Operations Interpolation (page 1039) 16
Math Fc. (page 1041) 48
PID (page 1043) 4
Regulators
Up/Down Ctrl Block (page 1047) 8
Inc/Dec (page 1050) 4
LowPassFlt (page 1051) 8
Ramp functions Mov Avg (page 1052) 8
Ramp (page 1053) 8
Up/Down (page 1054) 4
Analog Switch 8 (page 1055) 32
Bit Sum 16 (page 1057) 4
Circuit Breaker (page 1059) 8
Comp. 4 (page 1064) 8
Comp. 16 (page 1065) 8
Convert (page 1062) 16
Counter (page 1063) 8
Decomp. 4 (page 1066) 8
Others
Decomp. 16 (page 1067) 8
Differ (page 1069) 4
Heartbeat (page 1070) 16
Hold (page 1072) 4
PF Conv (page 1073) 4
Poly Appx (page 1075) 4
PWR Calc (page 1076) 4
Validator (page 1079) 16
For more information about PLC blocks go to the chapter PLC (page 1027)
6 back to PLC - Programmable Logic Controller

PLC Editor
Toolbar 186
Working with sheets 186
Blocks Selection Tree 187
Adding PLC blocks 188
PLC Block Configuration 188
Define inputs and outputs 190
Creating wires 191
The PLC Editor is available in InteliConfig Control tab: use Control → Controller Configuration → PLC Editor.
Toolbar
In the upper part of the PLC editor panel there is a toolbar with buttons for working with PLC blocks and PLC
sheets.
Operations PLC Sheets

Select all elements in sheets Add and remove sheets
Unselect all selected elements Move selected sheet down and up
Delete all selected elements Import sheet
Rerote selected items - wiring optimization Export selected sheet
Delete whole content of currently selected sheet Expand and Colapse all sheets
Others
Enable/Disable hints
6 back to PLC Editor
Working with sheets

PLC editor supports working with multiple sheets. You can add or delete sheets and move them up and down.
Every sheet can be also renamed by double-click on sheet name "Sheet 1". Each sheet can be re-sized
according to your needs by dragging the sheet edges. InteliConfig also supports importing and exporting of
the individual sheet.
Note: The number of PLC blocks on one PLC sheet is limited to 30 blocks.

Image 5.98 Adjusting PLC sheet
Blocks Selection Tree

On the left side of PLC Editor panel is available PLC blocks selection tree. Blocks are grouped into groups of
similar functionality next to the name of each block the number of used /available blocks of that type is
indicated in brackets.
Image 5.99 Blocks selection treet

Adding PLC blocks
Adding PLC block is using simple and intuitive drag and drop system. Follow the procedure below to add PLC
block.
Select required PLC block by LMB (left mouse button) from the list of available PLC blocks on the left side
and drag it into the sheet.
Connect the block inputs and outputs by drawing wires in the sheet. It is also possible to connected inputs
and outputs via properties of selected PLC block.
Note: To delete PLC block just click on it and press delete button. Also delete selection function can be used.
Note: To see context help for selected PLC block just press F1 button.
Image 5.100 Adding PLC blocks
PLC Block Configuration

Double-click on the block by LMB (left mouse button) to invoke the configuration panel specific for each block
type. In general, the definition of the block inputs and outputs is accompanied by some settings of block
properties. See PLC (page 1027) for more information about blocks.

Selecting the Inverted input check box means using negated input when evaluating the block.
Selecting the Inverted output check box means issuing a negated output value after the block has been
internally evaluated.
The binary values can be either controller Values, Setpoints or PLC binary outputs.
The analog values can be either controller Values, Setpoints, PLC analog outputs or entered as direct
constant block values. Non-numeric Setpoint values (e.g. IP address) cannot be used.
If a variable (binary signal) is connected via wire, the connection appears directly in the field - otherwise
the variable (binary signal) can be set using the dialog invoked by the '...' button.
Specific properties of the block (e.g. function type, mode of operation, etc.) can be set in the
corresponding panel object (list box, check box).
If the block has a variable number of inputs, the '+' button (in the upper left corner) adds an additional input
(channel) up to the maximum number of channels. Use 'X' button to remove a channel.
Note: If the constants are used (i.e. set by block configuration dialog) they cannot be changed dynamically
during PLC execution.

Define inputs and outputs
Image 5.101 PLC Inputs and Outputs
Inputs
Sheet inputs are located at the left side of a sheet. Follow the procedure below to add or edit an input.
Double-click on a free input position or existing input to add new input or edit the existing one.
Select the source for the input.
If you create a binary input, you can select a source from following categories:
Bin. Values - this category contains all binary values available in the controller as binary inputs, logical
binary outputs etc.
PLC Outputs - You can connect any PLC Output to another PLC Input.
If you create an analog input, you can select a source from following categories:
Ana. Values - this category contains all analog values available in the controller as analog inputs,
electrical values, values from ECU etc.
All Setpoints - this category contains all setpoints of the controller except the dedicated PLC setpoints.
Names, resolutions and dimensions of these setpoints can not be modified.
Image 5.102 PLC Inputs

Outputs
Sheet outputs are located at the right side of a sheet. Follow the procedure below to add or edit an output.
Double-click on a free output position to add new sheet output (binary or analog).
Draw the wire from the PLC block output to the PLC output on the right side of the sheet.
Doubleclick on an already created output to open it's configuration.
Use the button + Connect to connect the PLC output onto a controller output terminal or a logical binary
input.
Use the button - Disconnect to disconnect the PLC output from a controller output terminal or a logical
binary input.
Note: PLC block output has to be connected to the PLC output to enable configuration of the PLC output.
Note: It is necessary to click on the Connect button after selecting the output. Otherwise PLC output is not
connected to output.
Image 5.103 PLC Outputs
Creating wires
Wires can be created between PLC inputs and PLC block inputs, PLC block outputs nad PLC block inputs, or
PLC block outputs and PLC outputs.
Follow the procedure below to create wire.
Locate the mouse pointer over the starting point of the wire (dot). If the area under the mouse pointer is a
connection point, the connection point changes to bold dot.
Press and hold the left mouse button and drag the wire to the destination of required connection point
(from dot to dot connection). If you point over a valid connection point, the connection point changes to
bold dot.

Release the left mouse button to create a wire between the two points (dots). The wire is routed
automatically.
Note: It is possible to make connection only between the outputs and inputs with the same type of value
(binary or analog). Binary values are marked by black dot, analog values are marked with green dot.
Note: To delete wire just click on it and press delete button. Also delete selection function can be used.
IMPORTANT: In case that values on inputs have different decimal numbers than the values are
converted and the name of block is displayed as red in the PLC Monitor. It is strongly
recommended to fix the configuration = use the signals/values with the same range and decimal
numbers.
Image 5.104 Wiring PLC blocks

PLC logic execution rules

The PLC program is executed every 100 ms (this time is given by the PLC controller system integration) and
cannot be changed. PLC execution starts automatically after the ComAp controller is powered on and the
firmware initialization is completed. Of course the PLC program can only be executed with valid configuration
and/or valid SW key(s) for using the Extended PLC blocks.
The inital values for PLC inputs are given by the respective signals (e.g. actual power value) or determined by the
specific PLC block settings.
PLC blocks are executed in the order of the block numbers (Item numbers), that appear in each block. Block
numbers are assigned automatically according to the block position on the sheet based on the following scheme.

Image 5.105 PLC execution logic
IMPORTANT: Please always check that the blocks are ordered correctly, especially if you use direct
feedbacks from outputs to inputs within one sheet. Wrong order may lead to incorrect results!
The execution order is Item 1 → Item 2 → Item 3, so in the second case the AND block evaluation will use
Timer block output before the update.
PLC monitor
PLC monitor is a powerful tool for monitoring your PLC. Just click on PLC Monitor button on main InteliConfig
page to see you PLC in the run time. The refresh rate is given by the system integration. The PLC Monitor is
available in InteliConfig Control tab.
PLC monitor supports working with multiple controllers - on the left side of the panel there is a selection tree for
choosing the desired controller for PLC monitoring.

Image 5.106 PLC Monitor panel with multiple controllers
Note: In the PLC Monitor it is not possible to modify the PLC, not even the position of the blocks.
Active binary inputs, outputs and wires are blue, analog inputs, outputs and values are green. The values of
analog signals (as well as constants set in the blocks configuration) are also visible.
Image 5.107 PLC Monitor sheet with invalid value
Note: If the analog signal have an invalid value, the red "####" string is displayed and the connecting wire is
also red.
The PLC monitor also supports multi-sheet monitoring - individual sheets can be hidden/expanded using the
button in the top title bar.

Image 5.108 PLC Monitor with multiple sheets
Other functions
Consistency check
This performs a check of the PLC schematic
for the validity of the block interconnection = all inputs that are in internal design rules marked as
mandatory are connected and/or configured
for the consistency of the dimensions (setting attribute Dimension) and the number of decimal place
(setting attribute Resolution) at both ends of the interconnection wire
Image 5.109 Consistency Check valid output
Use this function during the design phase to check if all inputs and outputs of PLC block are connected
properly, and the design is consistent. The check is also performed automatically when the configuration may
be written to controller.
If the Consistency Check detect any problems, all findings will be displayed in the message window.
Image 5.110 Consistency Check report output

Message Meaning Remedy
Connected wire is not Probably Resolution and/or Use correct Resolution and/or
supported for function block Dimension mismatch on Dimension on both ends of
(Item X) the wire wire
Mandatory inputs of the
Not connected connector/s for Connect and/or configure all
block are not connected /
function block (item X) mandatory inputs
configured
Some connectors which must Probably Resolution and/or Use correct Resolution and/or
have same unit or resolution Dimension mismatch on Dimension on both ends of
are different for function block the wire or on Inputs and/or wire of between block inputs
(Item X) Output and output
Note: The Consistency Check checks whole configuration so it can report findings outside the PLC
configuration.
Delete whole content of sheet

Use this function to delete the whole content of sheet (including blocks, wires, inputs, outputs, etc...).
IMPORTANT: The sheet content is deleted immediately, without confirmation dialog (and there is
not any Undo or Redo button)!
Hints
Use this function to enable or disable quick hints for blocks (controller help is not affected by this function).
Note: Each PLC block has help which is opened by selecting the block and pressing "F1".
5.4.28 Power Formats And Units

InteliNeo 6000 allows users to choose from several Power Formats that affect dimensions in which values and
some setpoints are interpreted or adjusted. Power formats and units can be changed with InteliConfig in the
following way. Control tab → Controller configuration → Others tab → Units/Power format
Power formats are available in decimal and non decimal format. Units can be changed to metric or US units.
Units
Metric 20 °C 10.0 bar 11.4 l/h
US 68 °F 145 psi 3.01 gph
Power Format
Small 0.1 kW / kVA / kVAr 1V
Standard 1 kW / kVA / kVAr 1V
Large HV 0.01 MW / MVA / MVAr 0.01 kV
Large LV 0.01 MW / MVA / MVAr 1V
Note: Range of some setpoints and values is changed significantly when different Power Formats are selected.
Affected setpoint are displayed during selection of power format.

5.4.29 Protections
Protection types 198
Protection activation 200
Protection blocking 200
Fixed protections 200
User protections 205
Protection states 210
InteliNeo 6000 combines Fixed protections (page 200) with User protections (page 205) which allows
users to configure their own protections to any analog or binary input. Multiple protections can be configured
on each analog input, number of configured protections are not limited. Only one protection of 1st level
and/or one protection of 2nd level can be configured on logical binary output. The maximum number of
configured User protections (page 205) is limited to 200. The maximum number of configured fast User
protections (page 205) is limited to 50.

Protection types
Level 1 Protections
LBO COMMON ALARM LEVEL 1 (PAGE 937)
LBO COMMON ALARM ACTIVE LEVEL 1 (PAGE 936)
Action: CB open
Action: BESS stop
SD Override blocking
Alarm List +
History Alarm List
Name Warning Alarm Only History Record
Record Only Indication
Indication
Abbreviation Wrn Al Hst ALI AHI
Alarm List indication
History record
Fault Reset needed
LBO Alarm activation
LBO Horn activation

COMMON COMMON
COMMON
ALARM HISTORY
Common LBO WARNING
ONLY (PAGE RECORD
(PAGE 939)
937) (PAGE 937)

Level 2 Protections
LBO COMMON ALARM LEVEL 2 (PAGE 937); except Mains Protection
LBO COMMON ALARM ACTIVE LEVEL 2 (PAGE 936) ; except Mains Protection
Shutdown Mains PVCB Open

Name Shutdown Slow Stop
Override Protection
Abbreviation Sd Sd Stp MP PVBO
Alarm List indication
History record
Fault Reset needed
Action: CB open
Action: BESS stop
SD Override blocking
LBO Alarm activation
LBO Horn activation

COMMON COMMON
COMMON COMMON MAINS COMMON
SHUTDOWN SLOW
Common LBO SHUTDOWN PROTECTION PVCB OPEN
OVERRIDE STOP
(PAGE 938) (PAGE 937) (PAGE 938)
(PAGE 938) (PAGE 938)
6 back to Protections

Protection activation
The table below shows the availability of conditions for analog and binary values
Type Name of activation Protection is activated if value is

Over Limit over limit
Over Limit+Fls over limit or in fault state
Analog Under Limit under limit
Under Limit+Fls under limit or in fault state
Fls only in fault state
True logical 1
TrueOrFls logical 1 or in fault state*
Binary
False logical 0
FalseOrFls logical 0 or in fault state*
* Fault state can occur if there is loss of communication with configured CAN module.
Protection blocking
It is possible to configure one Protection Blocking to any User protections (page 205). This function is used to
block certain protections when their function is unwanted or meaningless. Each user protection has an option to
set the blocking condition.
The blocking conditions can be also applied on the Fixed protections (page 200).
General protections
Each of the LBI Protection Force Disable 1 is paired with an option of protection condition "Force Block 1–3" and
can be used for Blocking / Disabling of protections, however on user defined protections the option causes
protection Blocking instead of Disabling.
Run only protections

Each of the setpoint Run Only Block Delay 1 (page 434) is paired with an option of protection condition "Run
Only Block Delay 1–3". The protection
Fixed protections
Some selected fixed protections has an option to DISABLE the protection.
The setting is done by using the setpoint which is associated to the fixed protection. Each setpoint offers these
options.
Setpoint options
Alarms Fixed Protection States
Enable Protection is enabled
Disable Protection is disabled
PROTECTION FORCE DISABLE 1 (PAGE 906)
Disabling of the protection can be forced by LBI

Setpoint options
Alarms Fixed Protection States
BESS Voltage Protections

Protection Alarms / Protection name Fixed Protection States
Sd BESS >>V L1-N (page 1115)
Sd Mains/Bus >>V L2-N (page 1115)
BESS >>V Protection Sd BESS >>V L3-N (page 1116) FIXED PROTECTIONS STATES 2
(page 566) Sd BESS >>V L1-L2 (page 1116) (PAGE 1018)
Sd BESS >>V L2-L3 (page 1116)
Sd BESS >>V L3-L1 (page 1116)
Sd BESS >V L1-N (page 1117)
FIXED PROTECTIONS STATES 2
BESS >V (page 565) (PAGE 1018)
Sd BESS >V L1-L2 (page 1117)
Sd BESS <V L1-N (page 1118)
Sd BESS <V L2-N (page 1118)
BESS <V Protection Sd BESS <V L3-N (page 1119)
(PAGE 1018)
(page 567) Sd BESS <V L1-L2 (page 1119)
Sd BESS <V L2-L3 (page 1119)
Sd BESS <V L3-L1 (page 1119)
Sd BESS V Unbalance Ph-N (page
BESS V Unbalance 1120)
(PAGE 1018)
Protection (page 567) Sd BESS V Unbalance Ph-Ph (page
1120)
BESS Frequency Protections

BESS >f Protection (page
Sd BESS >f (page 1120) (PAGE 1018)
575)

BESS <f Protection (page
Sd BESS <f (page 1120) (PAGE 1018)
576)

BESS Load & Current Protections
Short Circuit Protection FIXED PROTECTIONS STATES 4
PVBO Short Circuit (page 1122)
(page 562) (PAGE 1020)
IDMT BESS >A FIXED PROTECTIONS STATES 4
Sd IDMT BESS >A (page 1121)
Protection (page 562) (PAGE 1020)
BESS Current Unbalance Sd BESS Current Unbalance (page FIXED PROTECTIONS STATES 2
Protection (page 564) 1121) (PAGE 1018)
IDMT Overload FIXED PROTECTIONS STATES 4
Sd IDMT Overload (page 1121)
BESS Other Protections

Earth Fault Current Sd IDMT Earth Fault Current (page FIXED PROTECTIONS STATES 4
Protection (page 583) 1121) (PAGE 1020)
Phase Rotation (page
377)
Note: This protection
monitors phases rotation
and compares it with
Phase Rotation (page ALI BESS Ph Rotation Opposite (page
-
377), in case of 1106)
inconsistency, proper
alarm is activated
Note: This protection can't

be disabled.
Inverted Phase
Note: This protection
monitors phases inversion
and in case of ALI BESS Ph L1 Inverted (page 1106)
inconsistency of all ALI BESS Ph L2 Inverted (page 1106) -
phases, proper alarm is
ALI BESS Ph L3 Inverted (page 1106)
activated
Note: This protection can

not be disabled.

Bus Voltage Protections
Protection Alarms / Protection name Fixed Protection State
Bus V Unbalance Protection
Behavior of protection is adjusted via
setpoints BESS V Unbalance (page
445) and BESS V Unbalance Delay
(page 445) When relative difference
between bus voltages is over setpoint
BESS V Unbalance (page 445) for time Mains/Bus V Unbalance
longer than BESS V Unbalance Delay Ph-N (page 1155) FIXED PROTECTIONS STATES
(page 445) history record "Bus V
Mains/Bus V Unbalance 3 (PAGE 1019)
Unbalance Ph-N" or/and "Bus V
Ph-Ph (page 1155)
Unbalance Ph-Ph" is written to the
history.
IMPORTANT: Behavior of this protection
is influenced by setpoint Connection
type (page 371).
Note: This protection can not be disabled.
Bus Other Protections

Protection Alarms / Protection name Fixed Protection State
FIXED PROTECTIONS STATES
Stp Bus Meas Error (page
Bus Meas Error (page 581) 4 (PAGE 1020)
1124)
Mains Voltage Protections

Mains/Bus >>V L1-N (page 1139)
Mains/Bus >>V L2-N (page 1140)
Mains >>V Protection Mains/Bus >>V L3-N (page 1141) FIXED PROTECTIONS STATES 3
(page 570) Mains/Bus >>V L1-L2 (page 1141) (PAGE 1019)
Mains/Bus >>V L2-L3 (page 1142)
Mains/Bus >>V L3-L1 (page 1143)
Mains/Bus >V L1-N (page 1135)
Mains >V Protection (PAGE 1018)
(page 568) FIXED PROTECTIONS STATES 3
Mains/Bus >V L1-L2 (page 1137)
(PAGE 1019)
Mains <V Protection Mains/Bus <V L1-N (page 1144) FIXED PROTECTIONS STATES 2
(page 572) Mains/Bus <V L2-N (page 1144) (PAGE 1018)

Mains Voltage Protections
Mains/Bus <V L3-N (page 1145)
Mains/Bus <V L1-L2 (page 1146) FIXED PROTECTIONS STATES 3
Mains/Bus <V L2-L3 (page 1147) (PAGE 1019)
Mains/Bus <V L3-L1 (page 1147)
Mains/Bus <<V L1-N (page 1148)
Mains/Bus <<V L2-N (page 1149)
Mains <V Protection Mains/Bus <<V L3-N (page 1150) FIXED PROTECTIONS STATES 3
(page 573) Mains/Bus <<V L1-L2 (page 1150) (PAGE 1019)
Mains/Bus <<V L2-L3 (page 1151)
Mains/Bus <<V L3-L1 (page 1152)
Mains/Bus V Unbalance Ph-N (page FIXED PROTECTIONS STATES 2
Mains V Unbalance 1155) (PAGE 1018)
Protection (page 574) Mains/Bus V Unbalance Ph-Ph (page FIXED PROTECTIONS STATES 3
1155) (PAGE 1019)
Mains Frequency Protections

Fixed Protection
Protection Alarms / Protection name
States
FIXED PROTECTIONS
Mains >>f Protection
Mains/Bus >>f (page 1153) STATES 3 (PAGE
(page 578)
1019)
FIXED PROTECTIONS
Mains >f Protection
Mains/Bus >f (page 1153) STATES 3 (PAGE
(page 577)
1019)
Frequency
FIXED PROTECTIONS
Mains <f Protection
Mains/Bus <f (page 1154) STATES 3 (PAGE
(page 579)
1019)
FIXED PROTECTIONS
Mains <<f Protection
Mains/Bus <<f (page 1154) STATES 3 (PAGE
(page 580)
1019)
Loss of Mains Protections

Vector Shift Protection FIXED PROTECTIONS STATES 4
Hst Vector Shift (page 1112)
(page 584) (PAGE 1020)
ROCOF1 Protection
Hst ROCOF 1 (page 1111) -
(page 585)
ROCOF2 Protection
Hst ROCOF2 (page 1111) -
(page 586)

Loss of Mains Protections
ROCOF3 Protection
(page 587)
ROCOF4 Protection
(page 588)
Grid Codes Protections

Mains 10min Avg >V FIXED PROTECTIONS STATES 2
-
Mains Params/MP
Synchronization (page AHI SyncNotAllowed (page 1110)
(PAGE 1017)
527)
Q&U Protection (page FIXED PROTECTIONS STATES 1
Wrn Q&U Protection (page 1097)
549) (PAGE 1017)
Pave (page 560) Hst Pave (page 1111) -
Dynamic Support (page FIXED PROTECTIONS STATES 1
VRT Protection Trip (page 1183)
552) (PAGE 1017)
User protections
Source upon which the protection is configured can be selected. It can be any analog value or binary state.
Source
Analog values Binary states
Analog inputs Binary inputs
Controller, Modules Controller, Modules, ECU, Shared I/O
Values Modbus server, Modbus Master
ECU, Measured values, Application, Binary outputs
PLC, Shared I/O PLC
Modbus server, Modbus Master Protection states
Statistics LBOs
Configuration of protections in InteliConfig

Control tab → Controller configuration → Protections tab → Analog / Binary protections

Select the desired protections to be configured (Analog protections / Binary protections).
Add protection by clicking on the icon
Delete selected protection by clicking on the icon.
Edit selected protection by clicking on the icon.

Adding analog protection
Selecting the input source see User protections on page 205
Selecting the protection type see Protection types on page 198
Text input for Alarm / History message
Selecting the protection activation see Protection activation on page 200
Selecting the block type see Protection blocking on page 200
Selecting if the occurrence of a protection is recorded every time or only once after a Fault
Reset.
Selecting the evaluation period

If Protection State is checked the protection is then shown in the Values in the group User
Protection States.
Selecting the input for limit.
Setpoints must have the correct resolution and dimension as protection source value.
Existing setpoint
New user setpoint
Existing user setpoint
Prefix is added to the name based on protection type / level
Selecting the input for delay.
Setpoints must have the correct resolution 0.1 and dimension [s]
Existing setpoint
New user setpoint
Prefix is added to the name based on protection type / leve

Adding binary protection
Selecting the input source see User protections on page 205
Selecting the protection type see Protection types on page 198
Text input for Alarm / History message
Selecting the protection activation see Protection activation on page 200
Selecting the block type see Protection blocking on page 200

Selecting if the occurence of a protection is recorded every time or only once after a Fault
Reset.
If Protection State is checked the protection is then shown in setpoints under the group User
setpoints.
Selecting the input for delay.

Setpoints must have the correct resolution 0.1 and dimension [s]
Existing setpoint
New user setpoint
Protection states
Protection states is a new feature introduced inInteliNeo 6000, which helps with better management of alarms.
Until now, you could only use LBO ALARM (PAGE 924) which did not specify what is going on. Protection states
work in similar way, like any other LBO. The difference is, that protection state gets active only when there is
specific alarm present in the alarm list. Thanks to this, you can create PLC logic, which will react to specific
alarms only.
Fixed protection states

Important Fixed protections (page 200) have a protection state. The protection state is (usually) named exactly
as the alarm. Fixed protection states are in a group of 32.
Protection states groups:
FIXED PROTECTIONS STATES 1 (PAGE 1017)
User protections states

During the Configuration of protections in InteliConfig (page 205), you can decide whether you want to add
user protection state for the protection. The name is exactly same as the alarm's message.
When you're adding user protection state, it will try to fill in gaps (if there are any present) in an actual list of User
Protection States (page 1024), if there is no gap, it will be automatically added to the end. User protection
states are in a group of 32 with maximally 10 groups i.e. 320 user protection states are available.
Note: Group of User protection states is showed only when there is at least 1 protection state in it.

5.4.30 Pulse Counters
InteliNeo 6000 has 4 internal counters 2 of them are physically configured to the specific binary inputs which
makes them faster than another 2 "slow" pulse counters which are using LBIs. Value of the each pulse counter is
increased by one step whenever the number of pulses counted reaches the value of setpoint Conversion
Coefficient Pulse. The fast pulse counters are able to count reliably pulses longer than 10 ms ON / 10 ms OFF
whereas the "slow" pulse counters are able to count reliably pulses longer than 200 ms ON / 200 ms OFF.
Conversion setpoint Value Binary Input

Conversion Coeff. Fast Pulse 1 (page Fast Pulse Counter 1 (page
BI9
383) 775)
Conversion Coeff. Fast Pulse 2 (page Fast Pulse Counter 2 (page
BI10
383) 775)
Conversion Coefficient Pulse 1 (page PULSE COUNTER 1 (PAGE
Pulse Counter 1 (page 776)
384) 908)
Conversion Coefficient Pulse 2 (page PULSE COUNTER 2 (PAGE
Pulse Counter 2 (page 776)
384) 908)
Note: Value of the internal counters remains even if the controller is unplugged from power.
Note: Counter counts leading edges.

5.4.31 PV Inverter Slots
This chapter deals with the integration of PV and possibly WT into a microgrid system. For applications with
InteliNeo6000 with a larger range of PV usage, it is typical that PV is integrated into the system using multiple
inverters. InteliNeo6000 then communicates with individual inverters independently, obtains data from them and
commands them.
The set of signals from each inverter always has the same format for PV looks like this:
Image 5.111 PV Invertor Slots configuration

Image 5.112 Aggregated values from all PV slots and individual values of each PV slot
Each of these sets can be seen as a separate channel (slot) through which InteliNeo6000 aggregates signals
from individual inverters as PV quantities. InteliNeo6000 supports up to 16 PV inverters in this way. The
configuration, i.e. the binding of these LAI values to the datapoints read from the individual inverters, must be
done manually (the binding is done automatically only in case of a single PV inverter configuration).
Aggregation of all acquired signals into common quantities is already automatic and therefore it is not
necessary to aggregate the common quantities using user logic in the PLC. The common PV quantities can
then be monitored in the controller as PV Aggregated quantities. Incidentally, the quantities integrated by the
individual PV channels can also be monitored in the PV quantity group.
In the case of WT support, the situation is very similar. InteliNeo6000 supports up to 8 WT inverters. The
system aggregates the total quantities of all data which are available. Thus, even just one channel (slot) is
enough to provide valid data. If the device, that is configured to a particular slot, is not communicating, is out
of service or in error (device error and subsequent inability to supply to the common bus is detected by LBI PV
X operable), then its values are simply not included in the aggregated data.

Communication with InteliGateway 300
InteliNeo6000 allows up to 16 Modbus devices to be connected directly via the integrated Modbus Client
(Master) (page 175) function. In certain cases (if it is necessary to connect more modbus devices than 16), there
is the possibility to provide communication with InteliNeo6000 via the InteliGateway 300 (page 32)
communication bridge (gateway). In this case, the aggregation of common data from multiple PV inverters takes
place on the InteliGateway 300 (page 32) side. The acquired data then enters into InteliNeo6000 via the
inverter slots (LBIs and LAIs) as if it were a single PV inverter. The InteliGateway 300 (page 32) in this case
works as a data concentrator and virtualizes multiple inverters into a single PV system.
More information about InteliGateway 300 (page 32) is available at this link: inteligateway-300
6 back to PV Inverter Slots

5.4.32 SD Card Storage
IMPORTANT: Only SanDisk Industrial XI microSD Cards (vendor order codes SDSDQAF3–xxxG-
XI) are currently supported.
Note: 16 GB Industrial memory card is also available in ComAp portfolio (ComAp product number
OT1C16GBXQX)
The controller is equipped with a ⑤ SD Card (page 47) slot for a possibility of storing large amount of data.
Formatting process
IMPORTANT: It is strongly recommended to perform the formatting of SD Card in OFF mode.
Alarm ALI SD Card Formatting/Mounting (page 1108) is displayed during the formatting process.
After changing the setpoint SD Card File System (page 393) to Format, the controller checks whether the
inserted SD card is supported - ALI SD Card Not Compatible (page 1107) alarm is displayed if it is not. If the
formatting is not successful, the value SD Card Status (page 781) shows Formatting Failed, the alarm ALI
SD Card Not Compatible (page 1107) is activated, and controller will not try formatting process again SD Card
File System (page 393) is automatically set to Mounted).
If the formatting is successful, the SD Card File System (page 393) is automatically changed to Mounted and
the card is ready for operation.
Mounting the SD Card

For enabling the SD card functions, setpoint SD Card File System (page 393) has to be set to option Mount.
IMPORTANT: It is strongly recommended to perform the mounting of SD Card in OFF mode.
Alarm ALI SD Card Formatting/Mounting (page 1108) is displayed during the mounting process.
In case that it is not possible to read or write to the SD Card, alarm Wrn SD Card Failed (page 1100) is
activated. The alarm is also activated in case the SD card is not inserted. See the value SD Card Status (page
781) for further information about the fail.
Alarm ALI SD Card Full (page 1108) is displayed if value SD Card Free Space drops below 10 %.
In case that the card has a wrong file system, alarm Wrn SD Card File System Failed (page 1100) is displayed.
Therefore formatting process should be performed again.
Unmounting the SD Card

If the setpoint SD Card File System (page 393) is set to Unmount, the controller is able to detect the SD card,
but it will not do any reading or writing of the data. The SD Card Status (page 781) will show Unmount, and in
case the card is still in the slot, the alarm ALI SD Card In Slot (page 1108) is issued.
Long term history

If an SD Card is successfully mounted, the controller is able to store history records onto the SD Card. This
function is activated by adjusting setpoint Long Term History (page 393) to Enabled.
Long Term History data are stored in folder named "HISTORY_SN" wheren SN is serial number of respective
controller that stored the data. Inside this folder there is another folder named "YYMMDDhhmmss" which is
created at the moment of switching the setpoint Long Term History (page 393) to Enabled. Inside this folder
you may find two files:

SN_YYMMDDhhmmss.hist - which contains history records.
SN_YYMMDDhhmmss.cfg - which contains important related data required in order to elaborate history
records.
Reading the data

1. Download the history records files from your SD card into the PC.
2. Open the InteliConfig, go to Tools and select Long Term History.
3. In the opened window choose the Input directory (destination of the SN_YYMMDDhhmmss.hist file) and
Output directory.
4. Choose Delimiter parameter and press Start.
5. The file containing the readable data should be created at the Output directory when conversion is
finished.
5.4.33 Sensor Curves

Default sensor curves
There are 16 default resistive curves available. The following table provides information on minimum/maximum
values of respective sensors. Actual values especially of temperature curves may differ.
Curve Min X [Ω] Max X [Ω] Min Y Max Y Units Y

General line 1 0 1 0 1 Ω
Note: Curves can be modified via InteliConfig. In InteliConfig are also prepared some standard curves.
Sensor curve HW configuration

InteliNeo 6000 analog inputs allows you to select Input HW type. Three HW configuration options are available:

0-15 kΩ
0-10 V
0-20 mA passive
Setup controller analog input in this way to use other than the default HW configuration (0-15 kΩ):
1. Start with a sensor configuration and select requested HW configuration
2. Use the adjusted sensor with an analog input and the requested HW configuration will be used with the analog
input automatically. There is no need to use a jumper, configured Input HW type is used by controller
automatically.

5.4.34 Service Timers
Maintenance timers
There are 4 maintenance timers which are used as counters which are counting down months and BESS running
hours. How much months / BESS running hours will be counted down is setup by the setpoints Maintenance
Timer Interval / Maintenance Timer RunHours. The actual state of the timer is visible in the values Maintenance
Timer RunHoursOnce / Maintenance Timer Interval. Once any timer reach zero value (days / running hours) the
alarm Maintenance Timer RunHours/ Maintenance Timer Interval will be activated together with the LBO AL
Maintenance. The type of the alarm (Wrn / Sd) can be defined by the setpoint Maintenance Timer Protection.
Each timer has its Setpoints, Values, Alarms and LBOs according to the table below.
Maintenance Timers Maintenance Timers Maintenance Timers Maintenance Timers

1 2 3 4
Maintenance Timer Maintenance Timer Maintenance Timer Maintenance Timer
1 RunHours (page 2 RunHours (page 3 RunHours (page 4 RunHours (page
640) 642) 643) 645)
Setpoints 1 Interval (page 2 Interval (page 3 Interval (page 4 Interval (page
641) 642) 644) 645)
1 Protection (page 2 Protection (page 3 Protection (page 4 Protection (page
641) 643) 644) 646)
1 RunHours (page 2 RunHours (page 3 RunHours (page 4 RunHours (page
772) 773) 773) 774)
Values
1 Interval (page 2 Interval (page 3 Interval (page 4 Interval (page
773) 773) 774) 774)
Maintenance 1 Maintenance 2 Maintenance 3 Maintenance 4
RunHours (page RunHours (page RunHours (page RunHours (page
1156) 1157) 1158) 1158)
Alarms
Maintenance 1 Maintenance 2 Maintenance 3 Maintenance 4
Interval (page Interval (page Interval (page RunHours (page
1156) 1157) 1157) 1158)
AL Maintenance 1 AL Maintenance 2 AL Maintenance 3 AL Maintenance 4
LBOs
(page 923) (page 923) (page 923) (page 923)
Running hours counters

There are 8 running hours counters. One counter is used as a basic running hours counter and it is incrementing
whenever the BESS is turned on. The other two counters are conditioned so they are incrementing when the
condition is fulfilled. The condition is fulfilled once the proper LBI is activated. See the table below.
Running Hours Conditioned Hours Counter 1 Conditioned Hours Counter 2

Running Hours Conditioned Running Hours 1 Conditioned Running Hours 2
Values
(page 771) (page 772) (page 772)

Conditioned Hours Counter 1 Conditioned Hours Counter 2
LBI N/A
(page 885) (page 885)
5.4.35 Sunrise/Sunset
Based on GPS coordinates, date and actual timezone can controller calculate real sunrise and sunset time.
This functionality is enabled/disabled by setpoint Sunrise/Sunset Function (page 615) and works in all
controller modes. Setpoint Sunrise/Sunset Latitude (page 616) and setpoint Sunrise/Sunset Longtitude
(page 616) are automatically set from GPS module. If coordinates are valid. they will be written on the rising
edge of LBI SUNRISE/SUNSET HOME POSITION (PAGE 917). Otherwise, these setpoints need to be set
manually. Values Sunrise Time (page 793), Sunset Time (page 793), Time To Sunrise (page 793),
Time To Sunset (page 794) are calculated from setpoints Sunrise/Sunset Latitude (page 616) and
Sunrise/Sunset Longtitude (page 616). LBO DAY/NIGHT (PAGE 940) is active during the day (between
Sunrise and Sunset Time).
5.4.36 Sunspec
SunSpec is an application-layer communications protocol designed to achieve interoperability between
Distributed Energy Resource (DER) components and smart grid applications. SunSpec has not static Modbus
registers, it uses block of registers in predefined order, but for each device is necessary to calculate Modbus
address. Register blocks are in row (where first ends, second starts).
5.4.37 System Start/Stop

There is a LBI REMOTE START/STOP (PAGE 915) that is used to start and stop BESS remotely in AUT mode.
In case of using System Start/Stop functionality with multiple controllers proper configuration of the system is
necessary to ensure correct operation. For the system using just CAN wiring no physical wiring of binary logic is
needed to share the starting and stopping signal into all controllers in the same group. LBI REMOTE START/STOP
(PAGE 915) should be configured in one "master" controller which will be used to control starting and stopping of
other controllers in the group. All controllers with configured LBI REMOTE START/STOP (PAGE 915) will be started
only if their LBI is activated.
5.4.38 SW Key Features

The controller offers premium features which are unlocked by software key.
The SW key is stored in setpoint SW Key (page 381) which is protected against rewriting during configuration
update. Value SW Key Feature List (page 783) contains actual list of features which requires SW key in order
to be used. When there is logical 1 respective function is unlocked and can be used without of limitation.
Note: Each SW Key is unique and valid only for specific serial number of a controller.
Using of SW Key
Insert your SW Key into setpoint SW Key (page 381)
Check value SW Key Feature List (page 783) whether functions were unlocked

Note: Please contact technical support in case that functions which were supposed to get unlocked after
inserting the SW key did not get unlocked
List of SW Key Features

SW Key Feature More information Order Code
CAN bus redundancy SKREDCAN201
(page 132)
Hot Swap Redundancy Hot Swap Redundancy (page 160) SKHOTSWAP01
SW Key Feature Order Code
Deep Sea Electronics support SKDSESUPP01
Intercontroller Expansion SKCAN2EXP01
IMPORTANT: Activation of deep Sea CAN software key will replace ComAp communication protocol
on intercontroller CAN line. This will prevent communication to ComAp controllers connected via
CAN2.
5.4.39 User Buttons

User Buttons can be used to assign function of user's choice to button on the External display (page 79) or like
remote switch. There are 32 user buttons and the behavior of each of them can be adjusted by it's relative
setpoint.
Each setpoint has these options:
Option Description
COMMAND The relative User Button is controlled by command from External display (page 79).
The relative User Button is controlled manually via the setpoint. Value of the user button
MAN OFF
is still 0.
The relative User Button is controlled manually via the setpoint. Value of the user button
is still 1.
MAN ON
Note: You should always switch from MAN ON to MAN OFF before switching to
COMMAND, otherwise value of the User Button will be 1 until command is received.
Commands
If relative setpoint is set to COMMAND, the User Button will react to commands sent via button from External
display (page 79). Type of command is selected during controller configuration in Screen Editor.
There are following commands:
Command Description
While this command is selected, pressing the button negate the actual value of the user
ON/OFF
button
While this command is selected, pressing the button sets the actual value of the user
ON button to 1.
Note: Will not have any effect if the value is already 1.
OFF
button to 0.

Note: Will not have any effect if the value is already 0.
Pulse ON button to 1 for 200 ms.
Note: The command reacts only to rising edge of the button.
See list of MODBUS comands in chapter List of commands and arguments (page 319).
Configuration of user button command

To configure Command on User Button, navigate to Configuration in InteliConfig
Select Screen Editor tab
Select Status bar
Add "Button CMD", for example to position
Select required user button and COMMAND

5.4.40 User Management And Data Access Control
Types of interfaces 222
User accounts 223
Managing accounts 225
Account break protection 227
Access to controller data 228
Accessing, monitoring and controlling the device via any communication interface require an user to be
logged-in.
When a task (read data, write data , control) is to be performed the access level of the user who is
currently logged-in must be higher or equal to the access level required for the particular task.
User must have user account defined by the administrator of the controller before the user can log-in into
the controller and perform monitoring, control or configuration tasks.
Types of interfaces
The controller communication interfaces are split into three categories according to what kind of environment the
interface is exposed.
Trusted
Are USB Type B (page 19) and in the default configuration Ethernet 1 (page 19) terminals.
It is expected that these interfaces are operated locally inside a closed environment / infrastructure where
additional measures against misuse or attack take place (e.g. physical access limitation).
Due to nature of this interface less strict cyber-security rules apply at it and that is why Implicit account is
introduced here to make working with the controller simpler.
Untrusted
Is in the default configuration Ethernet 2 (page 19) terminal.
This interface is a general-purpose one and it is expected that it may be exposed to public networks, such
as Internet, which are not under control of the entity operating the controller.
Thus, strict cyber-security rules apply for this type of interface.
The correct user account with password has to be used in order to connect to the controller.
This interface can be also used for SMTP and SNMP protocols.
Modbus
Is in the default configuration Ethernet 3 (page 19) terminal.
This interface is used for Modbus Client (Master) (page 175) or server.
It is expected that this interface is operated locally inside a closed environment / infrastructure where
additional measures against misuse or attack take place (e.g. physical access limitation).
Due to nature of this interface and fact that it is not possible to use it for connection to the controller, less
strict cyber-security rules apply at it.
Connections to ethernet interfaces

Either ComAp clients (InteliConfig, WebSupervisor, WinScope, InteliVision displays, etc.) or Modbus clients
can connect to the controller's ethernet interfaces. Number of possible connections is listed in the table below.

Type of interface ComAp clients Modbus clients
Trusted 6 3
Untrusted 8 3
Modbus 0 3
Example: If Ethernet 1 (page 19) = Trusted, Ethernet 2 (page 19) = Trusted, Ethernet 3 (page 19) =
Trusted, then it is possible to connect 6 ComAp clients and 3 Modbus clients on all three ports in sum.
Example: If Ethernet 1 (page 19) = Trusted, Ethernet 2 (page 19) = Untrusted, Ethernet 3 (page 19) =
Modbus client, then 6 ComAp clients and 3 Modbus clients can be connected to Ethernet 1 (page 19), 8
ComAp clients and 3 Modbus clients can be connected to Ethernet 2 (page 19) and 3 Modbus clients can
be connected to Ethernet 3 (page 19).
6 back to User Management And Data Access Control
User accounts
User account must be created in the controller by administrator before the particular user can login to the
controller.
Note: User accounts must be created for each controller separately and manually. It is not possible to transfer
the accounts from one controller to another.
User account has following properties:
Consists of 6-15 alphanumeric characters, must contain at least 1 letter. This

Username
is the main identifier of the particular user account.
Consists of 6-15 alphanumeric characters, must contain at least 1 letter and 1
Password digit. This is the password that is used together with user name to
authenticate (log-in).
Optional 4-digit identification string which can be used for simplified login at
User identifier (UID) trusted interfaces (e.g. from InteliVision display when connected via Ethernet
1 (page 19)).
PIN 4-digit “password” to be used together with UID.
Access level Determines Access to controller data (page 228)
Role mask Determines Access to controller data (page 228)
User login
To login to the controller the username and password must be provided into the login form of the
application (InteliConfig (page 22), WebSupervisor (page 22), External display (page 79) etc.).
Alternatively, at trusted interfaces, it is possible to login using UID and PIN instead of username and
password. This method of login is designed to simplify the login procedure at devices without alphanumeric
keyboard (e.g. InteliVision).
Note: The controller is featured with a protection against brute force attack to user account credentials. For
details please refer to the - Account break protection (page 227)

Changing password and PIN
The password and/or PIN for currently logged user can be changed. The user must be logged with username and
password even if PIN has to be changed.
Implicit account
There is one implicit user account in the system. This user account can not be deleted. This account is
automatically logged in at a trusted interfacewhile communication channel is open and there is not any other
user logged in. The account is fixedly assigned to role 1.
Factory default accounts

Each controller comes from the production with one factory default administrator account having following
credentials:
Username: “administrator”
Password: <serial number of the controller>
This account is member of role with index 0 (administrator role)
When the controller is being configured for operation the desired user accounts including the administrator
account should be created and then the factory default account must be deleted.
The controller issues warning alarm Wrn Default Password (page 1086) all the time the above default account
(username and password) is present in the controller.
IMPORTANT: Adjust the backup e-mail address before you delete the default administrator account. This
address is used as second authentication factor in password reset request and the password reset action
code will be sent to this and only this e-mail address.
Administrator account
There may be multiple accounts which are members of the administrator role. There must always remain at least
one account with administrator role.
Note: there must always remain at least one administrator account in the system. The controller will not allow
deleting last administrator account.
Reset accounts to factory default

If credentials (username and/or password) for administrator account are lost, it is possible to reset all user
accounts to the factory default state.
1. Connect InteliConfig to the controller

2. Read the Password Reset Request Code (PRRC)
3. You may disconnect from the InteliConfig now

4. Put the PRRC code into the “IntelliBot” application at https://www.comap-control.com/support or e-mail the
code to [email protected].
5. A unique, one-time Password Reset Action Code (PRAC) will be sent to the backup e-mail address adjusted in
the controller.
6. Connect via InteliConfig to the controller again
7. Enter the Password Reset Action Code into the appropriate form
8. Now the user accounts are in factory default state

Managing accounts
User accounts can be managed from InteliConfig while an online connection to the controller is established. The
right to manage accounts is explicitly and fixedly given only to administrator role (index 0). This right can not be
granted to any other role. The administrator must be logged with username/password and is prompted to re-enter
accounts password before the user management dialog is opened.
IMPORTANT: The total available number of accounts in the controller is 30.

Adding account
Click on “+” button in the lower left corner of the user management window, then provide the account properties
as described in User accounts (page 223).
Note: Rules for the User accounts (page 223) credentials apply and some items are optional
Deleting account
Select the account that has to be deleted and click on “-“ button in the lower left part of the user management
window.
Note: you can not delete your own administrator account unless there is another administrator account present
in the controller.
Deleting account properties

Select the account that has to be deleted and click on “-“ button in the lower left part of the user management
window. Then modify the desired property or properties. You can modify one or more properties at once.

Note: It is not possible to change user name or UID. Instead of this create a new account with the required
changes and delete the original one.
Account break protection

The controller is protecting the user accounts against breaking by a brute-force attack, i.e against breaking into
the controller by fast repeating attempts to login with credentials generated from the range of all possible
combinations.
If the account break protection detects a possible attack and blocks an account or interface the alarm Wrn Brute
Force Protection Active (page 1085) is activated. The alarm can be used to send an active message (e.g. e-
mail) to inform about that situation The detailed behavior of the controller depends on situation.
Password protection
1. If an user performs five consecutive attempts to login using username/password, providing correct
username but incorrect password, the respective user account is blocked for a time period of 1
minute. The attempts count regardless of the interface from which it is performed.
2. During the blocking period it is not possible to login with the respective account (username) from any
interface even if correct password is provided.
3. After the blocking period elapsed next attempt to login with the respective account (username) is possible.
If this attempt fails again the account is blocked again, now for period of 2 minutes.
4. The points 1-3 repeats further, the blocking period is multiplied by 2 in each next cycle. However, the
maximal blocking time is 20 minutes, the blocking time is never higher.
PIN protection
If an user performs ten consecutive attempts to login using UID/PIN, providing correct UID but incorrect PIN,
the user account is permanently blocked for login using UID/PIN. The user must login with username/password
and change the PIN to unblock this login method again.
Interface protection
If anyone performs twenty consecutive attempts to login via one particular interface (e.g.Ethernet 1 (page
19)) and does not neither provide a valid username nor a valid uid the respective interface is blocked for 2
minutes. During this period it is not possible to use that interface for any login. The blocking period is not
progressive in this case.

Access to controller data

Every request for reading data from the controller or writing data into it requires an user to be logged and that
user must have access rights higher or equal to the role defined for the particular object and operation.
Access right is the relation between an User and an Object inside the controller.
There are 10 roles with indexes 0..9 in the system.
Role 0 is administrator role. All objects/commands are fixedly assigned to this role.
Roles 1..7 are configurable roles. Each communication object/command can be assigned independently
to each of these roles.
Role 8 is Modbus client. Each communication object/command can be assigned to this role.
Role 9 is SNMP Manager. Each communication object/command can be assigned to this role.
Note:
Modbus and SNMP clients do not have implicit access to all objects. The access is limited by mapping
tables present in configuration. So, successful writing of an object require that object 1) to be present in
the respective mapping table, 2) to be assigned to the respective role.
Example: If a setpoint X shall be adjustable by Modbus this setpoint must be 1) mapped to a holding
register, 2) assigned to role 8.
Reading data
For each object the Access right "Read" (R) is fixedly granted to each role*. That means reading of data (except
some system objects) is available for any user.
Writing data
For each object the Access right "Write" (W) can be granted to one or more roles (indexes 1..9). For each object
the Access right "Write" (W) is fixedly granted to administrator role (index 0).
Special situations
There are several operations that require administrator role:
Programming firmware
Programming configuration
Managing user accounts. This right can not be granted to any other role.
5.4.41 User Setpoints

Controller allows user to create their own setpoints, groups and subrgroups. You can also edit and delete the
created setpoints/groups/subgroups and choose a group in which the setpoint or subgroup will be located.
Number of setpoints created by user is limited to 2047. The Comm. object number (CO) can be found via
InteliConfig (Tools tab → Generate Cfg image (COM)). User setpoints can be used to manage User protections
and PLC.

Add Groups/Subrgoups or User setpoint
Delete selected Groups/Subrgoups or User setpoint
Edit selected Groups/Subrgoups or User setpoint
Image 5.113 User setpoints tab in InteliConfig
Image 5.114 Setting parameters of Group/Subgroup

Image 5.115 Setting parameters of an user setpoint
Contents of the user Group/subrgroup

Max. 32 characters
Name Note: Does not consider duplicities (It is possible to have groups/subgroups with the
same name, but it is not recommended.)
Type Group type can be Group or Subgroup.
If you are creating a subgroup, parent group must be selected from created groups,
Parent group
except for exceptions.
Contents of the user setpoint

Max. 32 characters
Name Note: Does not consider duplicities (It is possible to have setpoints with the same
name, but it is not recommended.)
Can be chosen from a list or
Dimension
User can create their own with a limit of 32 characters.
Resolution Max. 4 decimal place
Range of the data type INT32 (restricted by resolution).
Low Limit Value is set as a constant (can not be set as setpoint).
Max. value cannot exceed High Limit.
Range of the data type INT32 (restricted by resolution).
High Limit Value is set as a constant (can not be set as setpoint).
Min. value cannot be lower than Low Limit.
Default value Must be in range between Low and High Limit (restricted by resolution).
Group Group in which setpoint will be shown.
Subgroup SubGroup in which setpoint will be shown.

Available groups and subgroups
The user setpoint can be put into some selected groups and subgroups.
Note: Setpoint is always added as last in selected subgroup.
List of available groups and it's subgroups:
Group Subgroup
Process control User setpoints
Basic Settings User setpoints
BESS Settings User setpoints
BESS Protections
BESS Protections
User setpoints
Protections User setpoints
Mains Protections
Mains Settings
User setpoints
Grid Codes User setpoints
Power Management User setpoints
User setpoints User setpoints
Analog Protections Analog Protections 1 – Analog Protections 8
5.4.42 Voltage Phase Sequence Detection

Controller detects phase sequence on both voltage terminals. This protection is important after controller
installation to avoid wrong voltage phase connection. The phase sequence is adjusted via setpoint Phase
Rotation (page 377).
6 back to General Functions
5.5 Application related functions

5.5.1 Application & System Variability 233
5.5.2 BESS Charging/Discharging Control 235
5.5.3 BESS Forced power 237
5.5.4 BESS Operation States 237
5.5.5 BESS Output Control 239
5.5.6 BESS Precharge Types 240
5.5.7 BESS Stabilization 241
5.5.8 BESS/PV PF/Q Control 242
5.5.9 Connecting To Load 243
5.5.10 Curtailment Counter 249
5.5.11 Multiple Island Operation 251
5.5.12 Output Control – Frequency/Load 251
5.5.13 Output Control - Voltage/PF 254
5.5.14 Parallel To MainsOperation - MINT Application 256
5.5.15 Parallel To Mains Operation - MPTM Application 258
5.5.16 Power Management 269

5.5.17 PV Curtailment 290
5.5.18 Regulation Loops 290
Functions directly related to the Microgrid application are described in this chapter.

5.5.1 Application & System Variability
The Microgrid site may consist of various elements such as BESS, renewables (PV/wind mills), Mains, and
Generators. Each site is different and the InteliNeo 6000 is a solution for most system variants.
The InteliNeo 6000 is not in position of the "master" controller, but it closely cooperates with all controllers in-site
so the InteliNeo 6000 can offer various statistics related to BESS, renewables, and Gen-sets. The HMI, visibility
of setpoints and values are changed based on settings defined by the setpoints in the Subgroup: System
Variability (page 365). The HMI also shows power flows through the system including information about power
from Mains and Gen-set controllers. The user can easily observe how the system operates with power, see the
pictures below.
Image 5.116 MINT HMI - PV, BESS, Gen-sets and Mains
Image 5.117 MINT HMI - actual power flow information

BESS
The main purpose of the InteliNeo 6000 is control the BESS, but it can still be used in case when the BESS is not
installed. In this case the setpoint BESS (page 365) should be set to Not Installed option and the following
groups will be hidden.
Note: This settings is related to the MINT and MPTM applications.
Setpoints Values
Group: BESS (page 664)
Group: BESS settings (page 425)
Group: Frequency/Load Control (page
Group: BESS Protections (page 561)
753)
Group: Frequency/Load Control (page 457)
Group: Voltage/PF Control (page 756)
Group: Voltage/PF Control (page 470)
The BESS statistics in the Group:
The most of the setpoints in the Group: BESS
Statistics (page 762)
Protections (page 437)
Group: Synchronization (page 476)
PV
The controller directly controls only the PVCB, the Modbus Client (Master) (page 175) is used to interact with
the PV inverter. In case there are not any renewables installed or the controller should not use any functions
related to the renewables the setpoint PV (page 365) should be set to Not Installed option and the following
groups will be hidden.
Note: This settings is related to the MINT and MPTM applications.
Setpoints Values
Group: PV Settings (page 451) Group: PV (page 675)
The PV statistics in the Group: Statistics (page 762)
Gensets
The controller is not used to control Gen-sets in any way, instead the Gen-set controllers must be used. In case
the Gen-sets are not part of the system the setpoint Gensets (page 366) should be set to Not Installed option.
The HMI will be changed and Gen-sets statistics in the Group: Statistics (page 762) will be hidden.
Note: This settings is related only to the MINT application.
Mains
In case the system is working as island microgrid the setpoint Mains (page 366) should be set to Not Installed
option and Mains will be removed from the HMI.
Note: This settings is related only to the MINT application.

5.5.2 BESS Charging/Discharging Control
This function allows managing of the charging process (storage of energy from the bus = Mains / Gen-sets /
renewables) and discharging process(providing stored energy to the load) of the BESS. There are two LBIs
which can be used to Enable/Disable charging and discharging process: LBI BATT CHARGE ENABLE (PAGE
879) and LBI BATT DISCHARGE ENABLE (PAGE 879). If both LBIs for charging and discharging are activated,
the battery cycling is applied. The battery will be cycling between charging/discharging targets given by
setpoints SOC Low Target (page 431) and SOC High Target (page 430)).
The source for the BESS active power output request can be selected by the Setpoint BESS P request
source (page 427). There are three types of sources:
Analog: The controller receives a BESS P REQUEST (PAGE 984) from the LAI BESS P REQUEST (PAGE
984). This LAI is used as a direct BESS Power Request.
Setpoint: The value of BESS P REQUEST (PAGE 984) is given by setpoints BESS Charge Power (page
427) or BESS Discharge Power (page 428).
Balance: The BESS P REQUEST (PAGE 984) is calculated using internal controller's algorithms. This
calculation maintain the balance of energy flow trough the system. For example, in OFF Grid application
the battery is only charged using the excess power in the system. Any extra Gen-set power is not required
to charge.
Note: All sources are influenced by LBIs mentioned above. When LBI BATT CHARGE ENABLE (PAGE 879) is
not active the Charge Request is unavailable. In case the LBI BATT DISCHARGE ENABLE (PAGE 879) is not
active, the discharge request is not available. If both LBIs are activated at the same time, the discharge
process has a higher priority.
BATT CHARGE ENABLE BATT DISCHARGE ENABLE BESS P Request

Charge/Discharge
(PAGE 879) (PAGE 879) Source
0 0 Blocked 0
BESS Discharge Power
0 1 Discharge
(page 428)
BESS Charge Power
1 0 Charge
(page 427)
1 1 Battery cycling
(page 428)
Variable Max Power Output

The active power of charging and discharging is primarily given by the setpoint Nominal power (page 368).
But in some cases the BESS cannot work on this power level. In these cases the variable maximal power
output is used and the maximal charging/discharging power is limited according the LAIs BESS MAX
CHARGE P (PAGE 984) and BESS MAX DISCHARGE P (PAGE 983).
These LAIs are used to limit BESS charging/discharging no matter what source/algorithm is used for the
BESS Required P Target (page 753) calculation. This function also affects calculations in the functions PV
Curtailment (page 290) and Dynamic Spinning Reserve (page 272).

Load Control Balance - Calculation of BESS P Request
The Power output of the BESS is controlled in way to consume excess or support deficit of power in the
system. The power balance of the system is given by equation:
Gen P Min (page 456) + PV Actual P (page 676) - Load P (page 720) = - BESS P (page 664)
Priority is to produce minimum power from Gen-sets (diesel), however in long term the Gen-sets have to
operate on some certain minimal power level. This level is given by the setpoint Gen P Min (page 456).
Excess of the power in the system is consumed by the BESS until it is running on -100% of its nominal
power, than the Gen-sets have to leave the Gen P Min (page 456) and ramp down. The function PV
Curtailment (page 290) can be used to limit output power of the PV inverter in order to keep the Gen-sets
running on their Gen P Min (page 456).
Deficit of power is firstly covered by the BESS until it is running on 100 % of its nominal power, then Gen-
sets start helping the BESS to cover the load.
If SOC is low or BESS cannot discharging for any reason, then the BESS output is limited to 0 and the
power demand has to be covered by Genset.
State of Charge
The charging and discharging process of the BESS also depends on the State Of Charge (SOC). When the
value BESS SOC (page 673) reach limit given by the setpoint SOC Low Target (page 431) the discharging
process is stopped and the LBO SOC DISCHARGE DISABLED (PAGE 975) is activated. When the value BESS
SOC (page 673) reach limit given by the setpoint SOC High Target (page 430) the charging process is
stopped and the LBO SOC CHARGE DISABLED (PAGE 975)is activated. The charging/discharing process can
be activated again after the value BESS SOC (page 673) leave the hysteresis which are defined by the
setpoints SOC Low Hysteresis (page 431) and SOC High Hysteresis (page 430). So, once the SOC
Actual reach the low target then the BESS cannot be discharged anymore until the BESS is cahrged at least
on the level of SOC Hysterezis.
Note: Charging and discharging is influenced all the time by the LBIs BATT CHARGE ENABLE (PAGE 879) and
BATT DISCHARGE ENABLE (PAGE 879).
Note: All relative setpoints/values are related to the LAI/Value BESSCAPACITY (PAGE 983)BESS Nominal
Capacity (page 673).
In the picture below you can see the red and orange (Sd and Wrn) alarm areas. The aopropirate alarm is
activated when SOC Actual trips the SOC alarm level given by setpoints in the Subgroup: SOC Protection
(page 589). The green area is Safety Operation Area and SOC targets should be placed in it. The battery
should cycle between these targets in the green area.
Image 5.118 State of charge

Daily Battery Cycles Control
The number of battery cycles per day can be limited by the setpoint Max Battery Cycles Per Day (page
432). In one day the statistic value Batt. Charging Cycles (page 765) cannot be increased more times than
the setpoint Max Battery Cycles Per Day (page 432) specifies. If the daily number of battery cycles is
reached the LBO DAILY BATT CYCLES REACHED (PAGE 939) and ALI Daily Battery Cycles Reached (page
1106) are activated and the battery cannot be discharged anymore. On the given day only battery charging is
allowed. One day is counted from midnight to midnight, so the LBO and alarm are deactivated at the earliest
midnight.
Note: Usually one charging cycle is defined as complete discharge of fully charged battery or a series of
partial drains equal to the battery’s capacity.
5.5.3 BESS Forced power

The BESS can require specific Power Limitations which occurs in certain situations. In order to use this limitation,
Forced power condition has to be fulfilled.
Forced power condition

Forced Power Condition of the BESS is applied to prevent overloading or reverse power of any unit in the system
connected to the bus. If the power of the system is too low or too high the controller which is not included in Load
Sharing (for example CU using local baseload) with the lowest priority, will be forced to increase or decrease
power according to the Load Sharing. The system always needs to keep at least one unit running on Load
Sharing line, so the system is capable of reacting to the changes in the load.
For InteliNeo6000 the BESS is running in "variable local baseload". It means that the controller controls charging
or discharging of the BESS independently on Load Sharing. The priority is to keep the BESS in this state, but if
the power of the system cannot be handled, the BESS is forced to join Load Sharing. The first case when the
BESS is forced to join Load Sharing can be when Gen-sets power goes under Gen P Min (page 456) and the
function PV Curtailment (page 290) is disabled or the PV power is already reduced to the minimum. The other
case can be when Gen-sets are overloaded and PV is already running on its maximum.
5.5.4 BESS Operation States

BESS state machine
Init Initialization of the controller. The application is not active yet.

BESS is not ready to start.
NotReady
Example: When shutdown alarm is active or unit is in OFF mode.
Ready BESS is ready to run.
Prestart Prestart sequence in process, PRESTART (PAGE 967) output is closed.
Starting BESS is starting until LBI Ready To Load is activated or timer BESS Start TO elapsed.
BESS is started and prepared to be precharged in case of AC precharge or it is already
Running precharged in case of DC precharge. See the chapter BESS Precharge Types (page
240).
Soft load BESS power is ramping up
Loaded BESS is running at nominal frequency and BCB FEEDBACK (PAGE 881) is closed.

Soft unld BESS power is ramping down
Stop.
Stop
Example: Automatic or manual stop command was issued.
Shutdown Shut-down alarm activated.
EMERGENCY MAN (PAGE 886) BESS operation.
EmergMan
Example: Used for bypass the controller and BESS manual start.
Electric state machine
Init Initialization of the controller. The application is not active yet.

MCB is opened (LBO MCB CLOSE/OPEN (PAGE 959) is not active and LBI MCB
BrksOff FEEDBACK (PAGE 902) is not active either) and BCB is opened (LBO BCB CLOSE/OPEN
(PAGE 926) is not active and LBI BCB FEEDBACK (PAGE 881) is not active either).
IslOper Island operation: MCB is opened and LBO BCB is closed.
MainsOperation: LBO MAINS/BUS HEALTHY (PAGE 959) is active, MCB is closed and
MainsOper
BCB is opened.
BESS is in parallel with mains (MAINS/BUS HEALTHY (PAGE 959) is active and MCB +
ParalOper
BCB are closed)
RevSync This state is active during synchronization via MCB.
Synchro BESS is synchronizing (MCB is closed, BCB is opened).
Mains Fails: this state is active when LBO MAINS/BUS HEALTHY (PAGE 959) is
MainsFlt
deactivated.
MainsRet Mains recover after fail.
ValidFlt State activated after Emergency start del.

5.5.5 BESS Output Control
In general there are two types of output control of the BESS inverter. It depends on what input can be send to
the BESS inverter as request. One option is that the inverter accept only P-Q request, another option is U-f
request or both. Because each option has its requirements and limits the LBI BESS OUTPUT CONTROL MODE
U-F/P-Q (PAGE 884) is used to choose what output control method will be used by InteliNeo6000 controller.
P-Q Output Control

In this case the input request for the BESS inverter output is given by active and reactive power. The active
and reactive power request is given by the controller's values BESS Required P (page 753) and BESS
Required Q (page 757) in case of absolute values, or BESS Required Relative P (page 754) and
BESS Required Relative Q (page 757) in case of relative values.
The BESS inverter using this output control method is able to work only in Grid Supporting mode because it
cannot control voltage and frequency level on it's output. In this case the BESS cannot be connected to the
grid without Mains/Gen-sets. It is not possible to close BCB if there is not healthy voltage on the bus.
Note: The AC precharge type should be used because the controller cannot use active synchronization
properly (it cannot control voltage and frequency levels). See the chapter BESS Precharge Types (page
240) for more information.
Note: If the BESS is connected to the Grid alone after Gen-set/Mains is disconnected, the BCB is opened
because of anti islanding protection (Hst BESS Anti Islanding (page 1114)).
U-f Output Control

In this case the input request for the BESS inverter output is given by frequency and voltage. The frequency
and voltage request is given by the controller's values Frequency Regulator Output (page 754) and
Voltage Regulator Output (page 758).
The BESS inverter using this output control method is able to work in Grid Forming mode because it can
control voltage and frequency level on it's output. In this case the BESS can be connected to the grid without
Mains/Gen-sets. The BCB can be closed to the dead bus if DC precharge type is used.
Note: The values described above are send to the BESS inverter via Modbus Client (Master) (page 175)
function for both cases.
U-f Output Control with droop

The controller of BESS (Battery Energy Storage System) generates the values for control of the BESS output.
Specific BESS as devices requires the different approach of control in u-f mode and it means it requires the
control inputs in different format. InteliNeo offers the most typical formats of values dedicated for BESS output
control. It provides control values for both active and reactive requirement.
For Active Power and Frequency control these values specificaly are: BESS Frequency Required (page
754), BESS Frequency Offset (page 754), BESS P Required (page 755)
All these values are calculated based on the Frequency regulator output and definition of the droop settings of
the BESS. It uses the Setpoint: BESS Frequency Droop Slope (page 459) for calculation. This Setpoint has
to be set acordingly to the actual BESS (PCS) frequency droop slope settings.
For Reactive Power and Voltage control these values specificaly are: BESS Voltage Required (page
758), BESS Voltage Offset (page 758), BESS Q Required % (page 759)

All these values are calculated based on the Voltage regulator output and definition of the droop settings of
the BESS. It uses the Setpoint: BESS Voltage Droop Slope (page 472) for calculation. This Setpoint has to
be set acordingly to the actual BESS (PCS) voltage droop slope settings.
5.5.6 BESS Precharge Types

This function allows adjustment of the BESS pre-charging type. There is the Setpoint BESS Precharge Type
(page 426) which enables the selection of AC or DC precharge of an inverter. This is a very influential factor
in determining the ability of an inverter to generate alternating voltage at its output.
InteliNeo supports two methods of BESS starting sequences. The selection of the appropriate method is
determined by how the battery inverter (PCS) DC circuit BCS connects to the battery before the inverter
connects to an energized AC bus. For the battery and PCS DC circuit to be connected via an internal DC
contactor, both must have the same DC voltage. Providing the additional potential required by the PCS is
called a 'precharge' procedure where the PCS DC circuit is charged either internally by its DC bus (batteries)
or from the AC side. This is known as 'DC precharge' or 'AC precharge', respectively.
Controller forces the user to configure all the necessary inputs, outputs and safety setpoints before the ES
can be fully utilized. If something is not configured correctly, Alarm Sd ES Configuration Incorrect.
Necessary configured inputs and outputs:
DC Precharge
DC precharge start sequence applies to PCS with the ability to black start itself from the DC bus of the
batteries.
InteliNeo uses two signals to coordinate DC precharge, the LBO PRECHARGE REQUEST (PAGE 968) and
LBI PRECHARGE FINISHED (PAGE 906). Both signals are mandatory.
Once the internal DC contactor between batteries and PCS are closed, the inverter can energize its AC
output.
LBI INVERTER START DISABLED (PAGE 896) is to be sent once the precharge procedure has been finished.
Controller then waits for confirmation LBI BESS READY TO LOAD (PAGE 885) (if this LBI is configured as
not all battery inverters have an idle mode), or the BESS is ready once the period set in Timer BESS
Ready To load elapses (only if LBI BESS READY TO LOAD (PAGE 885) is not configured).
BESS protections unlocks and BCB can be closed to allow BESS to energize the dead bus.
AC Precharge
AC precharge start sequence applies to PCS that requires energization from the AC side to close the internal
DC circuit to the batteries. The AC bus must be healthy with voltage and frequency within the acceptable
range of the PCS.
InteliNeo uses two signals to coordinate AC precharge, the LBO PRECHARGE REQUEST (PAGE 968) and
LBI PRECHARGE FINISHED (PAGE 906). Both signals are mandatory.
AC precharge starts by closing the BCB to the bus. The inverter must be able to moderate the inrush
current when connected to the AC bus via the BCB.
Once the DC voltage for the batteries and PCS are level and the internal DC circuit is closed, the
precharge of the inverter is complete.
InteliNeo provides LBO Inverter Run Request to the inverter to begin operation.

InteliNeo waits for confirmation LBI BESS READY TO LOAD (PAGE 885) (if this LBI is configured), or the
BESS is ready once the period set in Timer BESS Ready To load elapses (only if LBI BESS READY TO
LOAD (PAGE 885) is not configured).
BESS protections unlocks and inverter starts running unless postponed by the LBI INVERTER START
DISABLED (PAGE 896). If LBI Inverter Start Disabled is configured, the inverter and controller stays ready
but idle until LBO INVERTER RUN REQUEST (PAGE 953) is received.
Once inverter is running, InteliNeo has direct control of P and Q output of BESS. Since the bus was
energized by some other AC voltage source at the beginning, the BESS is operating in grid supporting
mode.
Note: There can be other limitations for the precharge type given by the BESS Output Control (page
239)method.
5.5.7 BESS Stabilization

IMPORTANT: This chapter is relevant only if BESS Precharge Type (page 426) is set to DC option.
When theBESS start is finished, the BESS goes into the stabilization phase. There are two timers (setpoints) in
this phase:
Minimal Stabilization Time (page 432) starts to count down just after the idle period has finished. BESS
voltage and frequency are not checked (respective protections are not evaluated) and the BCB cannot be
closed even if the BESS voltage and frequency are within limits.
Maximal Stabilization Time (page 433) starts to count down just after the idle period has finished. BESS
voltage and frequency are not checked (respective protections are not evaluated) but, opposite to the
previous timer, the BCB can be closed if BESS voltage and frequency are within limits.
In situations where the BCB is closed automatically (AUTO mode), the closing of BCB or starting of
synchronization will occur in the first moment when the BESS voltage and frequency will get into limits and the
Minimal Stabilization Time (page 432) has already elapsed.
In the event that the BESS voltage or frequency are not within limits within the Maximal Stabilization Time
(page 433) period, the appropriate protection(s) will be activated and the BESS will be cooled down and stopped.
Note: The limits for the BESS voltage and frequency are given by setpoints in the Group: BESS settings (page
425).
Note: The value of the Minimal Stabilization Time (page 432) setpoint has to be lower than the value of
Maximal Stabilization Time (page 433) setpoint.

5.5.8 BESS/PV PF/Q Control
PV PF/Q Control
In the parallel with mains operation or PV PF/Q regulation is realized using the setpoint PV Power Factor
Request (page 451). This setpoints defines the constant PF which is required from PV inverter. In the island
operation the PID PLC block should be used to regulate PF/Q of the PV so the Gen-sets has the constant PF.
In case the system has the BESS the value of the Required PF/Q which is defined by the setpoint PV Power
Factor Request (page 451) is sent to the PV inverter using the Modbus Client (Master) (page 175)
function.
BESS PF/Q Control

The PF/Q Controll of the BESS is regulated according to the setpoint BESS Q request source (page 429).
There are two types of sources:
Analog: The reactive power is regulated according to the the LAI BESS Q REQUEST (PAGE 984). This LAI
is used as a direct BESS Reactive Power Request.
Balance: The PF of the BESS is regulated using internal calculation so the BESS covers reactive power
peaks so Gen-sets (system) has the constant PF which is defined by the setpoint Gensets PF Required
(page 429).
The PF/Q regulation is limited by the apparent power of the BESS. The Capability L (page 864) and
Capability C (page 865) curves are used to circle area regulation defined as:
2 2
√(BESS P Actual + BESS Q Required ) = S BESS < Smax
Regulations in the Grid Forming Mode

MINT with IM 1010 controller
#System PF Control PTM (page 351) = VAr Sharing
PF/Q Regulation Type (page 351) = Base PF/Q Control or Import/Export PF/Q Control
The PV and BESS (no matter what source is set by the setpoint) will cover part of the PF/Q Request and
the Gen-sets will cover the rest.
MINT without IM 1010 controller
#System PF Control PTM (page 351) = Base PF or Base Q
The PV and BESS (no matter what source is set by the setpoint) will cover part of the PF/Q Request
and the Gen-sets will cover the rest.
PF/Q Regulation Type (page 351) = Base PF/Q Control
The PV will cover part of the PF/Q Request and the Gen-sets will cover the rest.
The BESS will cover part of the PF/Q Request only if LAI is used as source.

5.5.9 Connecting To Load
BESS 243
PV 243
Connecting To Dead Bus 244
Synchronization 244
BESS
Before connecting of the BESS to the load the LBI REMOTE START/STOP (PAGE 915) must be activated in case of
AUT mode or start button must be pressed in case of MAN mode.
The connection of the BESS to the bus/load differs according to the setpoint BESS Precharge Type (page 426).
In case the AC option is set, the BCB breaker can be closed immediately after the BESS is in the running phase.
No stabilization time is counted because the inverter with AC precharge is not able to generate AC voltage on its
output without being connected to the healthy bus. In this case the synchronization and connecting to the
deadbus options are not available.
In case the DC option is set , connecting of the BESS to the load is same as for the Gen-set. See the text below.
When the BESS Stabilization (page 241) phase is finished, the BESS can be connected to the load. The
command for connecting the BESS to the load is issued either automatically (AUTO mode) or manually by
pressing the BCB button. The following conditions must be valid:
The BESS is running and the Minimal Stabilization Time (page 432) timer has elapsed.
The BESS voltage and frequency are within limits.
Note: The frequency governor and AVR must be adjusted properly to achieve these limits as the controller does
not perform any regulation and the regulation outputs have constant values given by the Voltage Regulator
Bias (page 471) and Frequency Governor Bias (page 458) setpoints.
Connecting to load depends on the state of MCB FEEDBACK (PAGE 902) and on the measured bus voltage. In
case the Load is without power (bus voltage is below 2 % of nominal voltage and MCB is opened) the
Connecting To Dead Bus (page 244) is applied, in other case the Synchronization (page 244) process is
needed.
PV
The connection of the PV to the bus/load is not related to the LBI REMOTE START/STOP (PAGE 915) or start button
in any way. Instead the LBO PV/WT RUN REQUEST (PAGE 969) is activated always when the CU is in the AUT or
MAN mode and the controller expect activation of the LBI PV Operable. It is expected that PV inverter is always
using AC precharge so the PVCB can be closed once the LBI is active an the bus is healthy. So in this point
behavior is the same as it is for the BESS with AC precharge. The PVCB cannot be closed to the deadbus or
synchronized because PV inverter is not able to generate AC voltage on its own.
Connecting Mains to Load
Connecting to load depends on application, for BCB application it depends on the state of BCB FEEDBACK (PAGE
881) and on the measured bus voltage. In case of MCB application depends only on measured bus voltage. In
case the Load is without power (bus voltage is below 2 % of nominal voltage or BCB is opened) the connecting to
dead bus is applied, in other case the synchronization process (reverse synchronization) is needed. See more
information about synchronization process in chapter Synchronization (page 244).
Connecting to load (closing BTB) depends on the measured Bus Left and Bus Right voltage. In case one of the
side of BTB is without power (Bus Left or Bus Right voltage is below 2 % of nominal voltage) the connecting to

dead bus is applied, in other case the synchronization process is needed. See more information about
synchronization process in chapter Synchronization (page 244).
Connecting To Dead Bus

MPTM
If the MCB is open, the bus bar is considered as dead and the BCB is closed without synchronization.
MINT
The measured bus voltage is taken in account, it must be below 2% of the nominal bus voltage together with the
open MCB (evaluated by LBI MCB Feedback (page 902) or internally via CAN intercontroller communication if
the LBI is not configured), and also others BCB have to be opened, to close the BCB without synchronization.
Note: If the group of / multiple BESSs have to start simultaneously and connect to the empty bus bar, there is an
internal logic to prevent closing of more BCBs to the bus bar at the same moment without synchronization. One
of the BESSs will close the BCB, the others will wait and then they will synchronize to the first one.
IMPORTANT: The function described above works only if all controllers can see each other on
CAN intercontroller line. You can use Emergency Droop function to detect missing controller
on CAN.
Note: There also is a protection of “Bus power loss sensing”. The “Bus Measure Error” is detected in MINT
application when the voltage on the controller’s bus terminals is out of limits 20 seconds after:
BCB (own) was closed in MAN or AUT mode
MCB (feedback) was closed in AUT mode
Any other BCB in power management group (on CAN bus) was closed.
The alarm is activated after 20s. However, the BCB (own) closing is blocked immediately for safety reasons. This
protection can avoid e.g. potential direct closing of BCB while the controller’s bus conductors are unintentionally
unplugged from the terminals.
Synchronization
Synchronization Process 244
Synchronization Types 246
Synchronization Process
Behavior of synchronization process depends on, which breaker is used for synchronization and on which
Controller Mode (page 378) is controller switched to.
Note: When the controller starts to synchronize and the main measuring screen is displayed, it will be
automatically changed to the synchroscope screen for the entire duration of synchronization. The screen will
also show value Voltage Match 321 to inform you better about synchronization process. After synchronization
the synchroscope screen is automatically changed back to the main measuring screen. It is also possible to
change screens manually (arrows up and down) after displaying the synchroscope screen. In this case there is
no automatic return to the main measuring screen after synchronization is finished.
Voltage match 321

This value consists of 3 bits which are filled separately with logical 0 or logical 1 based on Mains/Bus Voltage and
BESS Voltage of respective phases during synchronization.
Note: Based on Connection type (page 371) this value may either relates to Ph-N or to Ph-Ph values.

Connection type (page 371) Relates to
3Ph4Wire
High Leg D Ph-Ph
3Ph3Wire
SplitPhase
Ph-N
MonoPhase
1st Bit, logical 1 when:
2nd Bit, logical 1 when:
3rd Bit, logical 1 when:
IMPORTANT: Bits are counted from right to left!
Synchronization via BCB in AUTO mode

BESS synchronization to the Mains (common bus bar) via BCB (available for MPTM and MINT):
If the Mains (bus) voltage or the Mains (bus) frequency gets out of the limits then the synchronization
continues until the Mains fail is confirmed. Then:
In MPTM - MCB is opened and BCB is closed.
In MINT - Stp Bus Meas Error (page 1124) alarm is issued.
If the BESS voltage or frequency gets out of the limits during the synchronization the synchronization
process is interrupted. The synchronization starts again when BESS parameters are restored. The
Synchronization Timeout (page 477) starts to be counted down again.
If the Synchronization Timeout (page 477) elapses alarm Stp Synchronization Fail (page 1128) is
issued.
Synchronization via BCB in MAN mode

BESS synchronization to the Mains (common bus bar) via BCB (available for MPTM and MINT:
Behavior is exactly the same as in AUTO mode - but the synchronization does not start again
automatically when parameters of the BESS gets out of limits and back. The breaker control button must
be pressed again.
When the BCB button is pressed during the synchronization, then the synchronization process is
interrupted.

Synchronization via MCB in AUTO mode
BESS synchronization to the Mains via MCB (available only for MPTM):
if the Mains voltage or the Mains frequency gets out of the limits during synchronization, then the
synchronization process is interrupted and can continue again when Mains parameters gets restored).
if the BESS voltage or frequency gets out of the limits during the synchronization, the synchronization
process continues until the BESSparameters fail is confirmed.
If the synchronization timeout gets elapsed the Wrn Reverse Synchronization Fail (page 1100)
protection gets active and BCB stays closed. Synchronization is stopped.
Synchronization via MCB in MAN mode

BESS synchronization to the Mains via MCB (available only for MPTM):
Behavior is exactly the same as in AUTO mode - but the synchronization does not start again
automatically when parameters of the Mains gets out of limits and back. The breaker control button must
be pressed again.
When the MCB button is pressed during the synchronization, then the synchronization process is
interrupted.
6 back to Synchronization
Synchronization Types
There are two types of synchronization. Type of synchronization is adjusted via setpoint Synchronization Type
(page 476).
Phase Match
The phase match synchronization consists of voltage matching and frequency/angle matching. The maximum
duration of synchronization is given by the setpoint Synchronization Timeout (page 477). If the
synchronization is not successful within this period of time, the Stp Synchronization Fail (page 1128) alarm will
be issued.
Voltage matching
The BESS voltage is regulated to match the Mains/Bus voltage with tolerance given by the setpoint Voltage
Window (page 477). The regulation is adjusted by the setpoints Voltage Gain (page 473) and Voltage Int
(page 473).
Frequency/angle matching
The BESS frequency is regulated to match the Mains/Bus frequency first. The frequency regulation loop is active
(setpoints Frequency Gain (page 460) and Frequency Int (page 461)). Once the frequency is matched, the
regulation loop is switched to match the angle (setpoint Angle Gain (page 461)). When the angle is matched
with tolerance +/- Phase Window (page 478) for a time given by the setpoint Dwell Time (page 478) and the
voltage is matched too, then the BCB or MCB is closed.
Note: The matching loop will continue to run even if the BCB or MCB close command has been already issued
until the controller receives BCB FEEDBACK (PAGE 881)/MCB FEEDBACK (PAGE 902) or Stp BCB Fail To Close
(page 1125)/Wrn MCB Fail To Close (page 1090) alarm occurs. After the feedback has been received, the
control loops are switched to load and power factor loops respectively to load and power factor sharing.

Slip Synchronization
The slip synchronizing is based on frequency/angle matching. The maximum duration of synchronizing is given
by the setpoint Synchronization Timeout (page 477). If the synchronizing is not successful within this period of
time, the Stp Synchronization Fail (page 1128) alarm will be issued.
The BESS frequency is regulated to match the Mains/Bus frequency + Slip Frequency (page 479) value and
the window is set by setpoint Slip Frequency Window (page 479). When the BESS frequency reaches
(Mains/Bus Frequency + Slip frequency) value regulation loop is stopped (output is frozen at the actual value). If
the BESS frequency reMains inside the window for the time longer than setpoint Dwell Time (page 478) the
controller will allow BCB or MCB closing. The controller calculates periodically so called preclosing angle (based
on the actual value Slip Frequency (page 674) and CB closing delay given by the setpoints BCB Latency
(page 479) or MCB Latency (page 480)). When the preclosing angle is reached the controller issues CB closing
command. The breaker will close and CB feedback confirms that to the controller. When the breaker is closed the
controller goes to parallel and activates regulation loops again (parallel to Mains regulation loop).
Image 5.119 Slip synchronization
Whenever the BESS Frequency (page 670) leaves off the Slip Frequency Window (page 479) (either
because of BESS Frequency (page 670), Mains/Bus Frequency (page 731) or setpoint Slip Frequency
Window (page 479) changes) the controller will reactivate frequency regulation loop and try to reach the target
value again. The Synchronization Timeout (page 477) timer runs regardless of this while whole slip
synchronization process is repeated. If the BESS Frequency (page 670) reaches the target frequency again the
regulations are frozen and if the BESS Frequency (page 670) remains in the window for the time longer than
setpoint Dwell Time (page 478) the controller will continue in the standard sequence as seen in the previous
case. *If the Synchronization Timeout (page 477) elapses the controller will immediately stop synchronization
and issue alarm Stp Synchronization Fail (page 1128).

The window is limited by the actual measured Mains/Bus Frequency (page 731) if one of the window limits is
below this value (e.g. for setting where setpoint Slip Frequency (page 674) is set to 0.1Hz and setpoint Slip
Frequency Window (page 479) is set to 0.5Hz).
Slip synchronization has a dead band. When the dead band is reached the frequency regulation is disabled.
Once it is disabled it will be enabled again only when the frequency goes out of the slip frequency window. Dead
band is introduced to allow the controller to detect the match.

Image 5.122 Slip synchonization - deadband
Note: Due to the nature of this function it is possible that in limit cases the controller will regulate the BESS
frequency outside of protection limits. Example: Mains/Bus frequency is high but within its protection limits (e.g.
50.9 Hz, limit is 51 Hz). Slip Frequency (page 479) is set to 0.5Hz. This will cause regulation loop of the
controller can push the BESS frequency to 51.4 Hz and eventually the controller will issue overfrequency alarm.
It is recommended to set the setpoint Slip Frequency (page 479) as low as possible that still enables succesfull
synchronization. This minimizes the risk of this problem happening. Furthermore when slip synchronization is
used it is recommended to set Mains/Bus Frequency protection limits to more rigid values than the BESS
frequency protection limits. In this case the setpoint Slip Frequency (page 479) can be set to 0.1Hz and the
Mains/Bus Frequency overfrequency protection limit is set to 50.9Hz instead of 51Hz. This will ensure that
problematic state cannot be reached.
6 back to Synchronization
5.5.10 Curtailment Counter

The Curtailment Counter is a crucial component of the microgrid controller, tasked with quantifying and
reporting energy losses attributed to curtailment in a photovoltaic (PV) system. Curtailment, in this context,
refers to the controlled reduction of energy generation to prevent grid overload or under-utilization. This
function calculates and reports the energy loss resulting from curtailment within the PV system.
How it Works:
1. Estimating Potential Energy: Using data from the irradiation sensors and the PV array area values, the
controller calculates the area of each array. It then multiplies this area by the irradiation data from sensors
1 to 4 to determine the potential PV output of each array.
2. Measuring Actual Energy: The controller measures the actual energy produced by each PV array within
the microgrid. This measurement typically relies on data from PV inverters or other monitoring devices.

3. Curtailment Energy Calculation: The energy lost due to curtailment is determined by calculating the
difference between the potential energy output (calculated in step 1) and the actual energy output
(measured in step 2) for each PV array.
Inputs
These sensors provide data on the amount of sunlight received at different points within the microgrid.
IRRADIATION OF PV ARRAY 1 (PAGE 990)
PV Arrays and Their Areas

The area of each array is determined by the respective setpoint value, and this area is further multiplied by
the irradiation data from sensors 1 through 4 to calculate the potential PV output of each array.
PV Array Area 1 (page 452)
Corrections
Output of Each particular PV Array in kW can be corrected using the offset which is defined setpoints:
PV Calib. Offset 1 (page 453)
Statistical Outputs
PV Total Curtailed kWh (page 763)
PV Curtailed Annual kWh (page 763)
PV Curtailed Monthly kWh (page 763)
PV Curtailed Weekly kWh (page 763)
PV Curtailed Daily kWh (page 764)
Curtailed Power
PV Max P (page 677)
PV Curtailed P (page 677)
PV Curtailed P Relative (page 678)
These statistical outputs provide valuable insights into the efficiency of the microgrid's PV system, enabling
operators and system administrators to make informed decisions to optimize energy utilization and
curtailment strategies within the microgrid.

Curtailment - Ramp Up / Down
The PV output request is directly influenced by the Value: Curtailment Output (page 703). This Value says
what is the maximal allowed PV output. Normally it is kept on the value 100% if there is no need to limit the PV
output. If the system needs to curtail the PV, then it does it using this value. The dynamic of the curtailment
output change is given by the settings of regulation loops of curtailment function. However the maximal rate of
change of Curtailment Output is limited by Setppoint: PV/WT Ramp Up (page 456) and Setpoint PV/WT
Ramp Down (page 457). These Setpoints says what is the duration of change from 0 to 100 % of the ramp.
5.5.11 Multiple Island Operation

This chapter describes the situation where the BESS and multiple Gen-sets are running parallel to each other
but not with mains. This situation will occur either when:
The common bus bar is dead due to opened MCB or there is no mains at all and the BESS and group of
Gen-sets has been connected to the bus, or
The group was running parallel to mains and the MCB has been opened.
IMPORTANT: The controller in MINT application does not control the MCB! Only the MCB position is
evaluated from the binary input MCB FEEDBACK (PAGE 902) and the position is the basic source of
information for switching between island and parallel to mains operation. If MCB Feedback is not
configured the state is automatically shared via intercontroller CAN.
Note: The following description is common for Gen-set and BESS only in case the BESS Precharge Types
(page 240) is set to DC. Otherwise the BESS cannot synchronize and it must be firstly precharged by closing
the BCB and connecting dead output of the inverter to the healthy bus.
If the bus bar is empty, the first Gen-set/BESS will close its GCB/BCB without synchronization. Following Gen-
sets will synchronize to the already energized bus bar. In the event that multiple Gen-sets start simultaneously
and the bus bar is empty, the system will prevent closing of multiple GCBs to the bus bar without synchronization.
Instead of this, one of the Gen-sets/BESS will close the GCB/BCB and energize the bus bar and the others will
wait and then synchronize to the bus bar.
When a stop command is received, e.g. from the power management or binary input REMOTE START/STOP (PAGE
915) is deactivated or the STOP button is pressed, the GCB/BCB will be opened, the BESS will be stopped and
Gen-sets will go to cool down phase.
Behavior of controllers is adjusted via Power Management (page 269) settings. Please see this chapter for
more information.
5.5.12 Output Control – Frequency/Load

The frequency control output is used to control the frequency or the power of the BESS. The frequency
regulation, load regulation and load sharing are realized through the frequency control. The Frequency Request
is internal value of the regulator which is transformed to range -10 .. 10 V based on setpoints Frequency
Governor Low Limit (page 458) and Frequency Governor High Limit (page 458). This value of frequency
request is then transformed to request which comes out of the controller. The analog or binary pulse outputs can
be send to the BESS inverter via MOBDUS client (master) function.
Analog output
ECU speed control
Binary pulse control

Frequency control outputs
Analog Output
The frequency regulator of the BESS is controlled by the analog signal from controller. Please see the chapter
Analog Outputs (page 70)
The direction of frequency regulation required by frequency regulator of the BESS is given by the setpoint
Frequency Regulator Character (page 457). A full range change of the frequency governor output (from
Frequency Governor Low Limit (page 458) to Frequency Governor High Limit (page 458)) should cause 5-
10% change of the BESS frequency (Frequency Governor Low Limit (page 458) ~ 95% Nominal Frequency
(page 377), Frequency Governor Bias (page 458) ~ 100%Nominal Frequency (page 377), Frequency
Governor High Limit (page 458) ~ 105% Nominal Frequency (page 377)).
IMPORTANT: Frequency governor has to be adjusted for optimum performance before
Frequency/Load control adjusting. Check BESS phase sequence before the first BCB connection.

The internal Frequency Request is transformed to Up/Down pulse control. These pulses get out of the controller
via binary outputs FREQUENCY UP (PAGE 950) and FREQUENCY DOWN (PAGE 950). Length of pulses FREQUENCY
UP (PAGE 950) and FREQUENCY DOWN (PAGE 950) depends on the difference of the actual frequency and
requested frequency (actual power and requested power) and on the parameter Tau Frequency Governor
Actuator (page 459). Tau Frequency Governor Actuator (page 459) defines the pulse duration which is
needed for the regulator of BESS inverter to regulatefrom minimal position to the maximal position. The
Maximum length of pulses is limited to 5 s, the minimal length of pulses is limited to 150 ms and minimal length
between the pulses is 200 ms.
Frequency/Load Control Adjustment

IMPORTANT: Prior to Frequency/Load control adjustment, the Voltage/PF control has to be adjusted.
Frequency & Synchronization Adjustment

Frequency and Angle control loop is active during synchronization process.
1. Set Frequency Gain (page 460) to 0 and start the BESS in MAN Mode.
2. Set the BESS frequency by Frequency Governor Bias (page 458), Frequency Governor Low Limit
(page 458) and Frequency Governor High Limit (page 458) to achieve frequency according to setpoint
Nominal Frequency (page 377).
3. Increase Frequency Gain (page 460) to unstable frequency control and decrease value by 30 % to
insure stable performance.
4. Adjust Frequency Int (page 461) to stable (fast and smooth) frequency control.
5. Set Angle Gain (page 461) to 0 and start the synchronization by pressing BCB ON/OFF button. To stop
synchronization press again BCB ON/OFF .
6. Synchroscope movement on the controller measure screen should slow down and stop (in any position,
because Angle Gain (page 461) control is off).
7. Set Angle Gain (page 461). Synchroscope on the controller measure screen should move slowly and
stop in “up“ position. Set Angle Gain (page 461) to unstable value (synchroscope swings) and decrease
value by 30 % to insure stable performance.
8. Now your speed regulation loop setup is done.

Load Control Adjustment
MINT application
Load control loop is active in parallel to Mains mode only (MCB FEEDBACK (PAGE 902) is closed). Switch off other
parts of the system (BESSs) while adjusting.
1. Set #System Baseload (page 348) setpoint to 30 % of one BESS.
2. Set Load Gain (page 462) to the same value as Angle Gain (page 461) and Load Int (page 462) to 0.
3. Start theBESS in MAN Mode, press BCB ON/OFF button to synchronize and close BESS to Mains.
4. When BCB is closed, BESS load slowly increases to the #System Baseload (page 348) value. Check
that BESS power is positive (CT polarity).
5. Increase Load Int (page 462) to unstable load control and decrease value by 30 % to insure stable
performance. When Load Int (page 462) factor is set to zero BESS load can differ from required
#System Baseload (page 348).
6. To adjust and optimize Load Int (page 462) change #System Baseload (page 348) several times
between 30 and 70 % of Nominal power (page 368).
7. When BESS is running under full load check if
a. Speed regulator output voltage value is not limited (it does not reach Frequency Governor Low
Limit (page 458) or Frequency Governor High Limit (page 458)).
b. Speed governor actuator is not mechanically limited or operates in a small section of the throttle
range.
8. Now your Load regulation loop setup is done.
MPTM application
Load control loop is active in parallel to Mains mode only (MCB FEEDBACK (PAGE 902) is closed).
1. Set Load Control PTM Mode (page 345) = BASELOAD, BESS P request source (page 427) =
Setpoint, BESS Charge Power (page 427)/BESS Discharge Power (page 428) setpoint to 30 %
Nominal power (page 368) of BESS and activate LBI BATT CHARGE ENABLE (PAGE 879)/BATT
DISCHARGE ENABLE (PAGE 879).
2. Set Load Gain (page 462) to the same value as Angle Gain (page 461). Set Load Int (page 462) to
zero.
3. Start the BESS in MAN Mode, press BCB ON/OFF button to synchronize and close BESS to Mains.
4. When BCB is closed, BESS load slowly increases to BESS Charge Power (page 427)/BESS Discharge
Power (page 428) value.
5. Increase Load Gain (page 462) to unstable load control and decrease value by 30 % to insure stable
BESS Charge Power (page 427)/BESS Discharge Power (page 428).
6. To adjust and optimize Load Int (page 462) change BESS Charge Power (page 427)/BESS Discharge
Power (page 428) several times between 30 and 70 % of Nominal power (page 368). Usually setting
Load Int (page 462) to 100% gives optimal performance.
7. When BESS is running under full load check if speed governor output voltage value is not limited (it does
not reach Frequency Governor Low Limit (page 458) or Frequency Governor High Limit (page
458)).
8. Now your Load regulation loop setup is done.

5.5.13 Output Control - Voltage/PF
The voltage control output is used to control the voltage or the power factor of the Gen-set. The voltage
regulation, PF regulation and VAr sharing are realized through the voltage control. The Voltage Request (page
758) is internal value of the regulator which is transformed to range -10 .. 10 V based on setpoints Voltage
Regulator Low Limit (page 471) and Voltage Regulator High Limit (page 471) and stored in value Voltage
Regulator Output (page 758). This value is transformed to a request which comes out of the controller. The
analog or binary pulse outputs can be send to the BESS inverter via MOBDUS client (master) function.
Voltage control outputs

Analog output
The voltage regulator of the BESS is controlled by the analog signal from controller. Please see the chapter
Analog Outputs (page 70)
The direction of voltage regulation required by voltage regulator of the BESS is given by the setpoint Voltage
Regulator Character (page 470). A full range change of the voltage regulator (from Voltage Regulator Low
Limit (page 471) to Voltage Regulator High Limit (page 471)) should cause 5-10% change of the voltage
(Voltage Regulator Low Limit (page 471) ~ 95% of BESS Nominal Voltage Ph-N (page 373), Voltage
Regulator Bias (page 471) ~ 100% BESS Nominal Voltage Ph-N (page 373), Voltage Regulator High Limit
(page 471) ~ 105% of BESS Nominal Voltage Ph-N (page 373)).

The internal Voltage Request (page 758) is transformed to Up/Down pulse control. These pulses get out of the
controller via binary outputs VOLTAGE UP (PAGE 979) and VOLTAGE DOWN (PAGE 978). Length of pulses VOLTAGE
UP (PAGE 979) and VOLTAGE DOWN (PAGE 978) depends on the difference of actual voltage and requested
voltage (actual reactive power and requested reacted power, actual PF and requested PF) and on the parameter
Tau Voltage Regulator Actuator (page 472). Tau Voltage Regulator Actuator (page 472) defines the pulse
duration which is needed for the regulator of BESS inverter to regulatefrom minimal position to the maximal
position. The Maximum length of pulses is limited to 5 s, the minimal length of pulses is limited to 150 ms and
minimal length between the pulses is 200 ms.
Voltage/PF control adjustment

Voltage Adjustment
1. Set Voltage Gain (page 473), Voltage Int (page 473) to 0 and Voltage Regulator Bias (page 471) to
the half of expected applicable range.
2. Start the BESS in MAN Mode without load.
3. Change Voltage Regulator Bias (page 471) to 0% and 100% to check BESS voltage control range
(typically ± 10 % of BESS Nominal Voltage Ph-N (page 373)).
4. Set the BESS voltage by Voltage Regulator Bias (page 471), Voltage Regulator High Limit (page
471) and Voltage Regulator Low Limit (page 471) to achieve voltage according to setpoint BESS
Nominal Voltage Ph-N (page 373).
5. Increase Voltage Gain (page 473) to unstable voltage control and decrease value by 30 % to insure
stable performance.
6. Adjust Voltage Int (page 473) to stable (fast and smooth) voltage control and change Voltage Regulator
Bias (page 471) back to value which should correspond to the BESS Nominal Voltage Ph-N (page

373).
7. Now your voltage regulation loop setup is done.
PF Adjustment
MINT application
Power factor control loop is active in parallel to mains mode only (MCB FEEDBACK (PAGE 902) is closed). Switch
off other parts of the system (Gen-sets) while adjusting.
1. Set PF Gain (page 474) to the same value as parameters Voltage Gain (page 473) and Voltage Int
(page 473) to 0.
2. Set #System Baseload (page 348) = 30 % of Nominal power (page 368) and #System Power Factor
(page 353) = 1.0.
3. Start and synchronize the BESS in MAN Mode by pressing BCB ON/OFF.
4. When running in parallel to mains loaded on 30%, increase slowly PF Gain (page 474) to unstable point
and then decrease the value by 30 % to insure stable performance.
5. Increase Load Int (page 462) to unstable load control and decrease value by 30 % to insure stable
#System Power Factor (page 353).
6. Now your PF/Q regulation loop setup is done.
MPTM application
Power factor control loop is active in parallel to mains mode only (MCB FEEDBACK (PAGE 902) is closed).
1. Set the same values to PF Gain (page 474) and PF Int (page 474) as in the chapter Voltage
Adjustment (page 254) for parameters Voltage Gain (page 473) and Voltage Int (page 473).
2. Set BESS Charge Power (page 427)/BESS Discharge Power (page 428) = 30 % of Nominal power
(page 368) and Base Power Factor (page 352) = 1.0.
3. Start and synchronize the BESS in MAN Mode by pressing BCB ON/OFF.
4. When running in parallel to mains loaded on 30%, increase slowly PF Gain (page 474) to unstable point
and then decrease the value by 30 % to insure stable performance.
5. Adjust PF Int (page 474) (usually setting to 100% gives optimal performance).
6. Now your PF/Q regulation loop setup is done.
Note: To judge optimal adjusting of the power factor induce BESS power jumps by Voltage Regulator Bias
(page 471) change or by BESS Charge Power (page 427)/BESS Discharge Power (page 428) change.

5.5.14 Parallel To MainsOperation - MINT Application
This chapter describes the situation where the BESS and multiple Gen-sets are running parallel to mains. This
situation will occur when the common bus bar is connected to the mains (MCB FEEDBACK (PAGE 902) is present)
and the BESS and group of Gen-sets has been connected to the bus. If the bus bar is healthy, all Gen-sets/BESS
will synchronize to the already energized bus bar.
IMPORTANT: The controller in MINT application does not control the MCB! Only the MCB position is
evaluated from the binary input MCB FEEDBACK (PAGE 902) and the position is the basic source of
information for switching between island and parallel to mains operation. If MCB Feedback is not
configured the state is automatically shared via intercontroller CAN.
The InteliNeo6000 Load and PF/Q control is different from Gen-set controllers. It is expected that renewables
(PV) and BESS should run with maximal priority so the Load Sharing is applied only in some critical cases. Se the
chapters BESS Charging/Discharging Control (page 235), BESS/PV PF/Q Control (page 242), and PV
Curtailment (page 290) for more information.
Ramping the power

Power up
Ramp up starts when value BESS Required P Target (page 753) is increased above value BESS Required P
(page 753). The first phase of the Parallel To Mains operation is the ramp of the BESS up to the desired power
level derived from the BESS Charging/Discharging Control (page 235). The speed of the ramp is given by the
setpoint Load Ramp (page 468). The setpoint adjusts the ramp time for a change from Ramp Start Level
(page 469) to 100 % of Nominal power (page 368)/Installed Power (page 368) of the BESS.
Note: Setpoints Ramp Start Level (page 469) and Load Ramp (page 468) are related to Installed Power
(page 368) only if Installed Power (page 368) != OFF, otherwise they relate to Nominal power (page 368).
Power down
Ramp down starts when value BESS Required P Target (page 753) drops, value BESS Required P (page
753) is ramped from BESS P (page 664) down to the new value of BESS Required P Target (page 753) based
on Load Ramp (page 468). Setpoint Load Ramp (page 468) determines how long it shall take to ramp down
from Nominal power (page 368)/Installed Power (page 368) of the BESS to 0 kW.
Soft unload
When BCB is about to be opened (BCB open command or stop command have been received), controller uses
Soft Unload Ramp (page 470) for ramp BESS P (page 664) to Generator Unload BCB Open Level (page
467). Setpoint Soft Unload Ramp (page 470) determines how long it shall take to ramp down from Nominal
power (page 368)/Installed Power (page 368) of the gen-set to 0 kW.
6 back to Parallel To MainsOperation - MINT Application
Load control
If MCB FEEDBACK (PAGE 902) is active (parallel to Mains operation) the load of Gen-set group is controlled to
reach the power defined by setpoint #System Baseload (page 348) or by Load Sharing line. If the setpoint
#System Load Control PTM (page 347) = Load Shar the system load is regulated by the InteliMains supervisor
controller, otherwise the load is controlled locally in each controller by load control regulation loop. The regulation
loop is adjusted via setpoints Load Gain (page 462) and Load Int (page 462).
Current Load control mode is always showed in System Load Control (page 755) value (SPTM only).

Baseload
Baseload ensures that the BESS keeps certain BESS P (page 664), which is given by BESS Required P (page
753). BESS Required P (page 753) is ramped to BESS Required P Target (page 753) using Load Ramp
(page 468).
If #System Load Control PTM (page 347)is set to Baseload the BESS Required P Target (page 753) is given
by:
If Load Request Source (page 346) = Setpoint, BESS Required P Target (page 753) = #System
Baseload (page 348).
If Load Request Source (page 346) = Analog External Value, BESS Required P Target (page 753) is
equal to value from LAI LOAD CONTROL: ANEXT BASELOAD (PAGE 989) .
Note: In case LAI LOAD CONTROL: ANEXT BASELOAD (PAGE 989) is not configured or has Invalid flag (page
652), the setpoint source is used instead of AIN.
Load Shar
If #System Load Control PTM (page 347) is Load Shar the system Load is controlled by InteliMains controller.
Note: Mains controller plays active role in case of load control only in case that the sepoint #System Load
Control PTM (page 347) is set to Load sharing . If this setpoint is set to Baseload the load control is controlled
from gen-set controllers and their load control loops.
InteliNeo 6000 offers 2 modes for controlling of load. Load control ensures that the system keeps the certain
Actual Active Power In PM (page 750) value in parallel to Mains operation MCB STATUS (PAGE 961) and BCB
STATUS (PAGE 931) are closed, i.e. Breaker state (page 778) = ParalOper and at least one gen-set is excited.
PF/Q control
If MCB FEEDBACK (PAGE 902) is active (Parallel To Mains Operation) the PF/Q of Gen-set is controlled to reach
the PF/Q defined by setpoint #System Power Factor (page 353)/#System Base Q (page 354).Var Sharing
line is used automatically if Load Sharing is active or while island operation. If the setpoint #System PF Control
PTM (page 351) = Var Shar the system PF/Q is regulated by the InteliMains supervisor controller, otherwise the
load is controlled locally in each controller by var control regulation loop. The regulation loop is adjusted via
setpoints PF Gain (page 474) and PF Int (page 474).
Current PF/Q control mode is always showed in System PF/Q Control (page 756) value (SPTM only).
Base PF/Q Control

Base PF/Q Control ensures that the Gen-set keeps certain BESS Q (page 665) to provide required BESS
Power Factor (page 667).
Base PF
#System PF Control PTM (page 351) has to be adjusted to Base PF. The BESS Required PF (page 757) with
BESS Required PF Character (page 757) are based on:
PF/Q Request Source (page 350) = Setpoint, requested PF is given by the Setpoint #System Power
Factor (page 353) or
PF/Q Request Source (page 350) = Analog External Value, requested PF is given by value from LAI PF
CONTROL: ANEXT BASE PF (PAGE 992).

Note: Alarm Wrn PF Control Fail (page 1093) is activated if LAI PF CONTROL: ANEXT BASE PF (PAGE 992) is
not configured or has Invalid flag (page 652). Power is controlled as if PF/Q Request Source (page 350) =
Setpoint.
Base Q
#System PF Control PTM (page 351) has to be adjusted to Base Q Control. The BESS Required PF (page
757) with BESS Required PF Character (page 757) are based on:
PF/Q Request Source (page 350) = Setpoint, BESS Required Q (page 757) is given by #System
Base Q (page 354) or
PF/Q Request Source (page 350) = Analog External Value, BESS Required Q (page 757) is given by
value from LAI Q Control: ANEXT Base Q (page 1004).
Note: Alarm Wrn Q Control Fail (page 1096) is activated if LAI Q CONTROL: ANEXT BASE Q (PAGE 1004) is
Setpoint.
Var Shar
If #System PF Control PTM (page 351) is Var Shar the Gen-set PF/Q is controlled by InteliMains controller.
5.5.15 Parallel To Mains Operation - MPTM Application
After the BESS has been synchronized to the mains, the parallel to mains operation follows.
The InteliNeo6000 Load and PF/Q control is different from Gen-set controllers. It is expected that renewables
(PV) and BESS should run with maximal priority so the Load Sharing is applied only in some critical cases. Se the
chapters BESS Charging/Discharging Control (page 235), BESS/PV PF/Q Control (page 242), and PV
Curtailment (page 290) for more information.
Ramping the power

IMPORTANT: Power ramping may be affected by Grid Codes (page 294) if any of them is enabled.
Power up
The first phase of the parallel to mains operation is the ramp of the BESS up to the desired power level. Ramp up
starts when value BESS Required P Target (page 753) rises. If the BCB has been just closed, value BESS
Required P (page 753) is ramped from Ramp Start Level (page 469) up to the new value of BESS Required P
Target (page 753) based on Load Ramp (page 468), otherwise is value BESS Required P (page 753) ramped
from BESS P (page 664). Setpoint Load Ramp (page 468) determines how long it shall take to ramp up from 0
kW to Installed Power (page 368) of the BESS.
Note: Ramp Start Level (page 469) and Load Ramp (page 468) are related to Installed Power (page 368)
only if Installed Power (page 368) != OFF, otherwise they relate to Nominal power (page 368).

Examples Description
Nominal Power = 100 kW
Installed Power = OFF
BCB gets closed, Required P is ramped from 10 kW
Ramp Start Level = 10 %
to 50 kW in 4 s.
Load Ramp = 10 s
Baseload = 50 kW
Installed Power = OFF BCB is closed, BESS P = 50 kW, Baseload is
Ramp Start Level = 10 % changed to 70 kW. Required P is ramped from 50
Load Ramp = 10 s kW to 70 kW in 2 s.
Baseload = 70 kW
Installed Power = 100 kW
BCB gets closed, Required P is ramped from 10 kW
Ramp Start Level = 10 %
to 50 kW in 4 s.
Load Ramp = 10 s
Baseload = 50 kW
Power down
Ramp down starts when value BESS Required P Target (page 753) drops, value BESS Required P (page
753) is ramped from BESS P (page 664) down to the new value of BESS Required P Target (page 753) based
on Load Ramp (page 468). Setpoint Load Ramp (page 468) determines how long it shall take to ramp down
from Installed Power (page 368) of theBESS to 0 kW.
Note: Setpoint Load Ramp (page 468) is related to Installed Power (page 368) only if Installed Power (page
368) != OFF, otherwise it relates to Nominal power (page 368).
Soft unload
When BCB is about to be opened (BCB open command or stop command have been received), controller uses
for ramping BESS P (page 664) to Generator Unload BCB Open Level (page 467). Setpoint determines how
long it shall take to ramp down from Installed Power (page 368) of the BESS to 0 kW.
Note: Setpoint Load Ramp (page 468) is related to Installed Power (page 368) only if Installed Power (page
368) != OFF, otherwise it relates to Nominal power (page 368).
6 back to Parallel To Mains Operation - MPTM Application
Load control
InteliNeo 6000 offers 2 modes for controlling of load. Load control ensures that the BESS keeps the certain
BESS P (page 664) value in parallel to Mains operation MCB STATUS (PAGE 961) and BCB STATUS (PAGE 931)
are closed, i.e. Breaker state (page 778) = ParalOper.
Current Load control mode is always showed in the value System Load Control (page 755).
Baseload
Baseload ensures that the BESS keeps certain BESS P (page 664), which is given by BESS Required P (page
753). BESS Required P (page 753) is ramped to BESS Required P Target (page 753) using Load Ramp
(page 468) or actual active ramp based on Grid Codes (page 294).

Load Control PTM Mode (page 345) has to be adjusted to Baseload and BESS Required P Target (page
753) is given by:
If BESS P request source (page 427) = Setpoint, BESS Required P Target (page 753) =
BESS Charge Power (page 427)/BESS Discharge Power (page 428) while LBI BATT CHARGE
ENABLE (PAGE 879)/BATT DISCHARGE ENABLE (PAGE 879) is active.
Note: BESS Required P Target (page 753), (Mains Import P (page 734)) can be lower/higher in case of
applied Grid Codes (page 294), BESS Forced power (page 237).
If Load Request Source (page 346) = Analog External Value, BESS Required P Target (page 753) is
equal to value from LAI LOAD CONTROL: ANEXT BASELOAD (PAGE 989).
Note: In case LAI LOAD CONTROL: ANEXT BASELOAD (PAGE 989) is not configured or has Invalid flag (page
652), function is evaluated as if Load Request Source (page 346) = Setpoint.
Import/Export
Import/Export ensures that the Gen-set regulates its BESS P (page 664) to keep certain Mains Import P (page
734). BESS P (page 664) is given by BESS Required P (page 753) which is ramped to BESS Required P
Target (page 753) using Load Ramp (page 468) or actual active ramp based on Grid Codes (page 294).
Load Control PTM Mode (page 345) has to be adjusted to Import/Export and BESS Required P Target (page
753) is given by:
If Load Request Source (page 346) = Setpoint, Mains Import P (page 734) = Import Load (page
348).
If Load Request Source (page 346) = Analog External Value, Mains Import P (page 734) is equal to
value from LAI LOAD CONTROL: ANEXT IMP/EXP LOAD (PAGE 990).
Note: Alarm Wrn Load IMP/EXP Fail (page 1088) is activated if:
Mains Measurement P (page 357) = None
Mains Measurement P (page 357) = Analog Input and LAI MAINS MEASUREMENT P (PAGE 992) is either
not configured or has Invalid flag (page 652).
Note: In case LAI LOAD CONTROL: ANEXT IMP/EXP LOAD (PAGE 990) is not configured or has Invalid flag
(page 652), function is evaluated as if Load Request Source (page 346) = Setpoint.
PF/Q Control
PF Control 261
PF(Pm) 262
Q Control 262
Q(Um) 263

Q(P) 264
Qref/Ulim 265
InteliNeo 6000 offers 6 modes for controlling of PF/Q. PF/Q control ensures that the BESS keeps a certain BESS
Power Factor (page 667) or BESS Q (page 665) (based on selected mode) in parallel to Mains operation MCB
STATUS (PAGE 961) and BCB STATUS (PAGE 931) are active, i.e. Breaker state (page 778) = ParalOper.
In case that the BESS Q (page 665) is out of tolerance given by Q Deadband (page 555), Q Ramp (page 555)
is used.
Current PF/Q control mode is always showed in System PF/Q Control (page 756).
PF Control
PF Control ensures that the Gen-set keeps certain BESS Q (page 665) to provide required BESS Power Factor
(page 667). To enable this control, adjust PF/Q Control PTM Mode (page 349) to PF Control.
Base PF
PF/Q Regulation Type (page 351) has to be adjusted to Base PF/Q Control. The BESS Required PF (page
System PF/Q Control (page 756) = PF Control BASE and
PF/Q Request Source (page 350) = Setpoint, requested PF is given by the Setpoint #System
Power Factor (page 353) or
PF/Q Request Source (page 350) = Analog External Value, requested PF is given by value from LAI
PF CONTROL: ANEXT BASE PF (PAGE 992).
Note: Alarm Wrn PF Control Fail (page 1093) is activated if LAI PF CONTROL: ANEXT BASE PF (PAGE 992) is
Setpoint.
Import/Export PF
PF/Q Regulation Type (page 351) has to be adjusted to Import/Export PF/Q Control. The BESS Required PF
(page 757) with BESS Required PF Character (page 757) are based on:
System PF/Q Control (page 756) = PF Control IMP/EXP and
PF/Q Request Source (page 350) = Setpoint, requested Mains PF (page 737) is given by Import
Power Factor (page 352) or
PF/Q Request Source (page 350) = Analog External Value, Mains PF (page 737) is given by value
from LAI PF CONTROL: ANEXT IMP/EXP PF (PAGE 993).
Note: Alarm Wrn PF Control Fail (page 1093) is activated if LAI PF CONTROL: ANEXT IMP/EXP PF (PAGE 993)
is not configured or has Invalid flag (page 652). Power is controlled as if PF/Q Request Source (page 350) =
Setpoint.
Note: Alarm Wrn PF/Q IMP/EXP Fail (page 1093) is activated if:
Mains Measurement Q (page 358) = None
Mains Measurement Q (page 358) = Analog Input and LAI MAINS MEASUREMENT Q (PAGE 992) is either
6 back to PF/Q Control

PF(Pm)
BESS Q (page 665) is automatically adjusted to correspond with predefined PF upon change of BESS P (page
664). The predefined PF is adjusted by application curve PF(P) (PAGE 861). To enable this control, adjust PF/Q
Control PTM Mode (page 349) to PF(Pm).
Base PF(Pm)
System PF/Q Control (page 756) = PF (Pm) BASE and
PF/Q Request Source (page 350) = Setpoint, requested PF is given by PF(P) (PAGE 861) curve in x-
axe range 0 to 100 %. Actual value of the curve is stored in PF(P) Curve (page 723). Or
PF/Q Request Source (page 350) = Analog External Value, alarm Wrn PF(Pm) Fail (page 1094) is
immediately activated because this control mode does not support external analog value. Power is
controlled as if PF/Q Request Source (page 350) = Setpoint.
Note: Alarm Wrn PF(Pm) Fail (page 1094) is activated if PF(P) (PAGE 861) curve is not configured or invalid.
Power is controlled as if PF/Q Control PTM Mode (page 349) = PF Control.
Import/Export PF(Pm)
System PF/Q Control (page 756) = PF (Pm) IMP/EXP and
PF/Q Request Source (page 350) = Setpoint, requested Mains PF (page 737) is given by PF(P)
(PAGE 861) curve in x-axe range -100 to 100 %. Actual value of the curve is stored in PF(P) Curve
(page 723). Or
PF/Q Request Source (page 350) = Analog External Value, alarm Wrn PF(Pm) Fail (page 1094) is
immediatelly activated because this control mode does not support external analog value. Power is
controlled as if PF/Q Request Source (page 350) = Setpoint.
Note: Alarm Wrn PF(Pm) Fail (page 1094) is activated if PF(P) (PAGE 861) curve is not configured or invalid.
Power is controlled as if PF/Q Control PTM Mode (page 349) = PF Control.
Q Control
BESS Power Factor (page 667) is adjusted to reach BESS Required Q (page 757). To enable this control,
adjust PF/Q Control PTM Mode (page 349) to Q Control.

Base Q
System PF/Q Control (page 756) = Q Control BASE and
PF/Q Request Source (page 350) = Setpoint, BESS Required Q (page 757) is given by Base Q
(page 353) or
PF/Q Request Source (page 350) = Analog External Value, BESS Required Q (page 757) is given
by value from LAI Q Control: ANEXT Base Q (page 1004).
Setpoint.
Import/Export Q
System PF/Q Control (page 756) = Q Control IMP/EXP and
PF/Q Request Source (page 350) = Setpoint, Mains Import Q (page 735) is given by Import Q
(page 354) or
PF/Q Request Source (page 350) = Analog External Value, Mains Import Q (page 735) is given by
value from LAI Q CONTROL: ANEXT IMP/EXP Q (PAGE 1004).
Setpoint.
Q(Um)
BESS Q (page 665) is automatically adjusted to correspond with predefined BESS Required Q (page 757)
upon change of relative Mains voltage. The predefined BESS Required Q (page 757) is adjusted by application
curve Q(UM) (PAGE 858) To enable this control, adjust PF/Q Control PTM Mode (page 349) to Q(Um).
Base Q(Um)
System PF/Q Control (page 756) = Q(Um) BASE and
PF/Q Request Source (page 350) = Setpoint, BESS Required Q (page 757) is given by Q(UM)
(PAGE 858) curve. The curve can be offset horizontally by Q(Um) 0 Reference (page 556) and in case
of Mains Voltage changes too fast, there is Q(Um) Deadband (page 556). Actual value of the curve is

stored in Q(Um) Curve (page 722) Or
PF/Q Request Source (page 350) = Analog External Value, BESS Required Q (page 757) is still
given by Q(UM) (PAGE 858) curve, but the horizontal offset is given by value of LAI Q(UM): 0 REF
ANEXT BASE Q (PAGE 1005)System PF/Q Control (page 756) Q(Um) Deadband (page 556) can
also be applied. Actual value of the curve is stored in Q(Um) Curve (page 722).
Note: Alarm Wrn Q(Um) Fail (page 1098) is activated if LAI Q(UM): 0 REF ANEXT BASE Q (PAGE 1005) is not
configured or has Invalid flag (page 652). Power is controlled as if PF/Q Request Source (page 350) =
Setpoint.
Import/Export Q(Um)
System PF/Q Control (page 756) = Q(Um) IMP/EXP and
PF/Q Request Source (page 350) = Setpoint, Mains Import Q (page 735) is given by Q(UM) (PAGE
858) curve. The curve can be offset horizontally by Q(Um) 0 Reference (page 556) and in case of too
fast Mains Voltage changes, there is Q(Um) Deadband (page 556). Actual value of the curve is stored
in Q(Um) Curve (page 722). Or
Q(UM) (PAGE 858) curve, but the horizontal offset is given by value of LAI Q(UM): 0 REF ANEXT
IMP/EXP Q (PAGE 1006)System PF/Q Control (page 756) Q(Um) Deadband (page 556) can also be
applied. Actual value of the curve is stored in Q(Um) Curve (page 722).
Note: Alarm Wrn Q(Um) Fail (page 1098) is activated if LAI Q(UM): 0 REF ANEXT BASE Q (PAGE 1005) is not
configured or has Invalid flag (page 652). Power is controlled as if PF/Q Request Source (page 350) =
Setpoint.
Q(P)
based on BESS P (page 664). The predefined BESS Required Q (page 757) is adjusted by application curve Q
(P) (PAGE 860) To enable this control, adjust PF/Q Control PTM Mode (page 349) to Q(P).
Base Q(P)
PF/Q Regulation Type (page 351) has to be adjusted to Base PF/Q Control. The BESS Q (page 665) is based
on:
System PF/Q Control (page 756) = Q(P) BASE and
PF/Q Request Source (page 350) = Setpoint, BESS Required Q (page 757) is given by Q(P) (PAGE
860) curve in x-axe range 0 to 100 %. To prevent oscilation use Q(P) Deadband (page 558) Actual

value of the curve is stored in Q(P) Curve (page 723). Or
PF/Q Request Source (page 350) = Analog External Value, alarm Wrn Q(P) Fail (page 1097) is
controled as if PF/Q Request Source (page 350) = Setpoint.
Note: Alarm Wrn Q(P) Fail (page 1097) is activated if Q(P) (PAGE 860) curve is not configured or invalid. Power
is controlled as if PF/Q Control PTM Mode (page 349) = PF Control.
Import/Export Q(P)
PF/Q Regulation Type (page 351) has to be adjusted to Import/Export PF/Q Control. The BESS Required Q
(page 757)is based on:
System PF/Q Control (page 756) = Q(P) IMP/EXP and
PF/Q Request Source (page 350) = Setpoint, Mains Import Q (page 735) is given by Q(P) (PAGE
860) curve in x-axe range -100 to 100 %. To prevent oscilation use Q(P) Deadband (page 558) Actual
value of the curve is stored in Q(P) Curve (page 723). Or
PF/Q Request Source (page 350) = Analog External Value, alarm Wrn Q(P) Fail (page 1097) is
controled as if PF/Q Request Source (page 350) = Setpoint.
Note: Alarm Wrn Q(P) Fail (page 1097) is activated if Q(P) (PAGE 860) curve is not configured or invalid. Power
is controlled as if PF/Q Control PTM Mode (page 349) = PF Control.
Qref/Ulim
upon change of relative Mains voltage. The predefined BESS Required Q (page 757) is adjusted by application
curve QREF/ULIM (PAGE 859). To enable this control, adjust PF/Q Control PTM Mode (page 349) to Qref/Ulim.
Base Qref/Ulim
System PF/Q Control (page 756)= Qref/Ulim BASE and
PF/Q Request Source (page 350) = Setpoint, BESS Required Q (page 757) is given by QREF/ULIM
(PAGE 859) curve. The curve can be offset vertically by Qref/Pnom Shift (page 557) and in case of too
fast Mains Voltage changes, there is Qref/Ulim Deadband (page 557) Actual value of the curve is
stored in Qref/Ulim Curve (page 722). Or
PF/Q Request Source (page 350) = Analog External Value, BESS Required Q (page 757) is still
given by QREF/ULIM (PAGE 859) curve, but the horizontal offset is given by value of LAI QREF/ULIM:

ANEXT QREF/PNOM B Q (PAGE 1007)System PF/Q Control (page 756) Qref/Ulim Deadband (page
557) can also be applied. Actual value of the curve is stored in Qref/Ulim Curve (page 722).
Note: Alarm Wrn Qref/Ulim Fail (page 1098) is activated if LAI QREF/ULIM: ANEXT QREF/PNOM B Q (PAGE
1007) is not configured or has Invalid flag (page 652). Power is controlled as if PF/Q Request Source (page
350) = Setpoint.
Import/Export Qref/Ulim
PF/Q Regulation Type (page 351) has to be adjusted to Import/Export PF/Q Control. The BESS Required Q
(page 757) is based on:
System PF/Q Control (page 756) = Qref/Ulim IMP/EXP and
PF/Q Request Source (page 350) = Setpoint, Mains Import Q (page 735) is given by QREF/ULIM
(PAGE 859) curve. The curve can be offset vertically by Qref/Pnom Shift (page 557) and in case of too
fast Mains Voltage changes, there is Qref/Ulim Deadband (page 557) Actual value of the curve is
stored in Qref/Ulim Curve (page 722). Or
QREF/ULIM (PAGE 859) curve, but the offset is given by value of LAI QREF/ULIM: ANEXT QREF/PNOM
I/E Q (PAGE 1008)System PF/Q Control (page 756) Qref/Ulim Deadband (page 557) can also be
applied. Actual value of the curve is stored in Qref/Ulim Curve (page 722).
Note: Alarm Wrn Qref/Ulim Fail (page 1098) is activated if LAI QREF/ULIM: ANEXT QREF/PNOM I/E Q (PAGE
1008) is not configured or has Invalid flag (page 652). Power is controlled as if PF/Q Request Source (page
350) = Setpoint.

Transfers of load
Type of transfer of load between mains and BESS and vice versa is adjusted via setpoints Transfer BESS To
Mains (page 466) and Transfer Mains To BESS (page 465).

Types of transfers
Transfer of the load from BESS to mains and vice versa without parallel work and
Open synchronization (one breaker opens and second is closed - checking feedbacks). The
setpoint Open Transfer Min Break (page 464) sets the minimal duration of break.
Transfer of the load from BESS to mains and vice versa with synchronization and
parallel work. The maximal time of parallel work is given by setpoint Close Transfer
Close Only
Max Duration (page 464).
In case of synchronization fail, MCB stays close and BESS is stopped.
Transfer of the load from BESS to mains and vice versa with synchronization and
parallel work. The time of parallel work is given by setpoint Close Transfer Max
Close Primarily
Duration (page 464).
In case of synchronization fail, open transfer is done.
Transfer of the load from BESS to mains and vice versa with parallel work and soft
loading/unloading of the BESS. This function is proceeded like the closed transfer, but
there is time limitation of loading/unloading of the BESS adjusted via setpoint Load
Ramp (page 468). The transfer is succeed only when the BESS is fully
Soft Transfer
loaded/unloaded (level of load when mains is considered as unloaded - BESS is loaded
is adjusted via setpoint Mains Unload MCB Open Window (page 467)), level of load
when BESS is considered as unloaded is adjusted via setpoint Generator Unload
BCB Open Level (page 467)).
Transfer of load in MAN mode

Behavior of transfer of load in MAN mode is adjusted via setpoint CB Control In MAN Mode (page 355). For
details see the setpoint description.
Transfer of load in AUTO mode

Behavior of transfer of load in AUTO mode is affected by binary inputs FORCE ISLAND (PAGE 886), FORCE
PARALLEL (PAGE 887) and REMOTE START/STOP (PAGE 915).
When more binary inputs are activated at the same time, their priority is shown in the list below:
FORCE ISLAND (PAGE 886) (highest priority).
REMOTE START/STOP (PAGE 915).
FORCE PARALLEL (PAGE 887) (lowest priority).
Note: AMF function has the highest priority (if it is enabled).

Logical binary input AUTO mode
When activated:
starts BESS
FORCE ISLAND (PAGE the transfer of load from mains to BESS is done
886) When deactivated:
the transfer of load from BESS to mains is done
stopping of the BESS
When activated:
starts BESS
REMOTE START/STOP if mains parameters ok - synchronize, run in parallel

(PAGE 915) if mains parameters not ok - run in island
When deactivated:
unloading (if BESS was in parallel) and stopping of the BESS
When activated:
check mains parameters - if not ok no action, if ok the procedure follows
starts the BESS, synchronize, parallel operation
FORCE PARALLEL
in case of mains fail - BESS is stopped (if AMF function is disabled,
(PAGE 887)
otherwise it goes to island operation)
When deactivated:
unloading and stopping of the BESS
Type of transfer of load between mains and BESS and vice versa is adjusted via setpoints Transfer BESS To
Mains (page 466) and Transfer Mains To BESS (page 465).

5.5.16 Power Management
Role of InteliNeo6000 in Power management 269
Basic power management 270
Principle of power management 270
Load reserve 271
Dynamic Spinning Reserve 272
Starting sequence 273
Stopping sequence 274
Absolute power management 275
Relative power management 277
Priorities 280
Priority auto swap 281
Minimal running power 288
IMPORTANT: Power management is relevant only for MINT application.
IMPORTANT: The BESS and BESS will take part of the power management (will be active) only if the
controller is in AUTO mode!
The Power management function decides how many BESSs should run and selects particular BESSs to run. The
power management is applicable in cases multiple BESSs run in parallel to Mains or in the island operation. The
function is based on the load evaluation in order to provide enough of available running power. Since it allows the
system to start and stop BESSs based on the load demand, it can vastly improve the system fuel efficiency. In
other words, an additional BESS starts when the load of the system raises above certain level. The additional
BESS stops, when the load of the system drops down below a certain level. The process of determining BESS
start and stop is done in each controller; there is no "master slave" system. Therefore, the system is very robust
and resistant to failures of any unit in the system. Each of the controllers can be switched off without influencing
the whole system. Except the situation the respective BESS is not available for the power management.
The power management evaluates so called Load reserve (page 271). The load reserve is calculated as
difference between actual load and nominal power of running BESSs. The reserve is calculated as absolute
value (in kW / kVA) or relatively to the nominal power of BESS(s) (in %). The setpoint #Power Management
Mode (page 482) is used to select the absolute or relative mode.
The Load Reserve can be influenced by the Dynamic Spinning Reserve (page 272) which is used to provide
the system with extra power (running BESSs) in case of anticipated output drop of a renewable source of energy.
The function Priority auto swap (page 281) focuses on efficient run of BESS in regards to running hours and
BESS size (power).
IMPORTANT: The function of the controller is designed to handle the maximum sum of nominal
power at 32000 kW (or 3200,0 with decimal number).
Example: There are 20 BESSs each with 1000 kW of nominal power. The sum of the nominal power is
20000 kW. Therefore the decimal power format in 0.1 kW cannot be used because the sum exceeds
32000. Therefore power format in kW needs to be chosen.
Role of InteliNeo6000 in Power management

The Power management are the principles (rules) which the system decides whether it is necessary to start or
stop other resources to cover the current consumption and the required load reserve. Power management is a

distributed logic and each controller makes decisions autonomously based on commonly shared information.
InteliNeo6000 in the MINT application is part of the ComAp ecosystem and behaves according to the general
rules of power management. It provides reserve in the form of unused power capacity from the BESS according
to the valid conditions of the Power Management function (AUT mode, Power management setpoint Enabled)
and also according to the conditions specific to the BESS battery storage. Specifically, it depends on whether the
battery is in a state where the discharge request can be accepted. This is based on the conditions of the BESS
Charging/Discharging Control (page 235), or according to the status of the LBI BATT DISCHARGE ENABLE
(PAGE 879). One of the important parametrers evaluated in power management is a priority of the source (Gen-
set, BESS).
To ensure the automatic change between the zero diesel mode based on the actual renewables output, load
conditions, SOC of the battery and required reserve, it is recommended to keep the Priority setpoint in the
InteliNeo6000 set to "1". Then if gen-sets have higher priority number ("2", "3", ...) it is possible to smoothly
change the mode of operation between gen-sets Running/Stopped. The output of the renewable sources served
by InteliNeo6000 and integrated in the system can undirectly effect the power management due to the load
reserve increase/decrease request. This principle is based on the Dynamic Spinning Reserve (page 272).
6 back to Power Management
Basic power management

The setpoint Power Management (page 480) enables and disables the BESS to be active within the power
management and makes automatic load dependent starts and stops. If the power management is disabled, the
start and stop of the BESS do not depend on the load of the group. If the BESS remains in AUTO mode, the
running condition depends only on the Logical binary inputs REMOTE START/STOP (PAGE 915).
The Logical binary input REMOTE START/STOP (PAGE 915) requests the system to start or stop. If the input is not
active, the system stops with delay #System Stop Delay (page 485) after the input has been deactivated and
will not start again if in AUTO mode. If the input is activated again, the delay #System Start Delay (page 485)
starts to count down. Once the delay elapsed, the system is activated and can be started by the power
management. In other words, the power management is activated only if the Logical binary inputs REMOTE
START/STOP (PAGE 915) is activated, the option of setpoint Power Management (page 480) = Enabled and the
AUTO mode is selected.
Note: The BESS performs load and VAR sharing whenever it is connected to the bus bar i.e. it is independent on
whether the controller is in AUTO or MAN mode or whether the power management is active or not.
Function of power management can be temporarily blocked after REMOTE START/STOP (PAGE 915) activation a
count down of #System Start Delay (page 485). The delay is given by setpoint Power Management Delay
(page 481). In this delay all BESSs where power management is enabled are running. After this period elapses,
only the BESSs needed according to the Power Management calculation stay running and the rest is stopped.
Principle of power management

Internal conditions based on remaining load reserves and priorities are evaluated once a delay is elapsed. If the
load reserve is insufficient the BESS is started after delay given by the setpoint #Next Engine Start Delay (page
501) is elapsed. Once the BESS runs the controller evaluates stopping conditions based on load reserves and
priorities. If the reserve is sufficient enough to stop a particular BESS, it is stopped after delay given by the
setpoint #Next Engine Stop Delay (page 502) is elapsed. All the time the system stop condition – i.e. the
Logical binary inputs REMOTE START/STOP (PAGE 915) deactivated – is evaluated as well. Once the delay given
by the setpoint #System Stop Delay (page 485) has elapsed all BESSs in AUTO mode are stopped. Following
figure depicts the system activation and deactivation logic.

Setpoint #Overload Next Start Delay (page 505) is used in case that #Overload Next Start Protection (page
504) is enabled and BESSs are running at #Overload Next Start Level (page 504) or more of their nominal
power.
Load reserve
The power management is based on the load reserve concept. The load reserve is defined as a difference of the
running nominal power of the group within power management and the total load of the system. In the
InteliNeo6000 controller the running nominal power is given by the actual power of the renewables (if they are
used) and by the nominal power of the BESS. There are two ways how to determine the load reserve. The
absolute power management allows the system to keep the load reserve higher or equal to value in kW given by
a relevant setpoint. The relative power management assures that load reserve is kept higher or equal to relative
portion in % of the nominal power of the group given by a relevant setpoint. Depending of the situation, load
reserves are calculated differently in two cases:

Island operation
Reserve Actual Reserve Start condition Stop condition

ARstrt = ∑PgNom - ∑PgAct ARstrt < ARstp >
Absolute kW
ARstp = ∑Pg*Nom - ∑PgAct #LoadResStrt #LoadResStop
RRstrt = [(∑PgNom - ∑PgAct) / ∑PgNom].100% RRstrt < RRstp >
Relative %
RRstp = [(∑Pg*Nom - ∑PgAct) / ∑Pg*Nom].100% #%LdResStrt #%LdResStop
Parallel to mains operation
Reserve Actual Reserve Start condition Stop condition

ARstrt = ∑PgNom - BaseLoad ARstrt < ARstp >
Absolute kW
ARstp = ∑Pg*Nom - BaseLoad #LoadResStrt #LoadResStop
RRstrt = [(∑PgNom - BaseLoad) / ∑PgNom].100% RRstrt < RRstp >
Relative %
RRstp = [(∑Pg*Nom - BaseLoad) / ∑Pg*Nom].100% #%LdResStrt #%LdResStop
List of abbreviations:
ARstrt .. Actual Absolute reserve in kW or kVA - for BESS start calculation.
ARstp .. Actual Absolute reserves in kW or kVA - for BESS stop calculation.
RRstrt .. Actual Relative reserve in % - for BESS start calculation.
RRstp .. Actual Relative reserves in % - for BESS stop calculation.
ΣPgNom .. Sum of Nominal power of all BESS on the bus.
ΣPg*Nom .. Sum of Nominal power of all BESS on the bus apart of the one, which is going to be stopped.
ΣPgAct .. Sum of Actual power of all BESS on the bus = system load.
BaseLd .. Baseload is given by the setpoint #System Baseload (page 348)
Note: System starting sequences may be very different due to their complexity (i.e. BESS which do not take part
in power management, various nominal powers etc.). Each system should be considered individually.
Dynamic Spinning Reserve

The values Dynamic Spinning Reserve (page 749) and Dynamic Spinning Reserve Offset (page 749) are
used to affect power management operation in case of anticipated output drop of a renewable source of energy.
It enables to shift the load reserve start level and load reserve stop level for power management. The value
Dynamic Spinning Reserve (page 749) is added to required load reserve given by setpoints #Starting Load
Reserve 1 (page 488) and #Stopping Load Reserve 1 (page 489) (according to actual load reserve set 1, 2, 3
or 4). The value Dynamic Spinning Reserve Offset (page 749) is added only to required stopping load reserve
given by setpoints #Stopping Load Reserve 1 (page 489) (according to actual load reserve set 1, 2, 3 or 4) to
create some dynamic offset between starting and stopping load reserve.
The InteliNeo6000 controller can provide the values Dynamic Spinning Reserve (page 749) and Dynamic
Spinning Reserve Offset (page 749) on the CAN line based on option selected in the setpoint Dynamic
Spinning Reserve Source.
In case the function is Disabled the InteliNeo6000 is not calculating and providing Dynamic Spinning
Reserve (page 749) and Dynamic Spinning Reserve Offset (page 749) at all.

In case option External Analog Value is used the InteliNeo6000 receives these values from the LAIs
DYNAMIC SPINNING RESERVE (PAGE 988) and DYNAMIC SPINNING RESERVE OFFSET (PAGE 988) and its
provide them via CAN line to the Gen-set controllers.
In case option Internal Calculation is selected the DYNAMIC SPINNING RESERVE OFFSET (PAGE 988) is
received from LAI and DYNAMIC SPINNING RESERVE (PAGE 988) is calculated according to the fallowing
formula:
DSR [kW] = Solar Coverage Ratio (page 487) * PV Actual P (page 676) + Nominal power (page
368) - BESS MAX DISCHARGE P (PAGE 983)
If the BESS is in the state when it cannot be discharged (LBI BESS Discharging Enable = false) the
only first part of the formula is used for the DSR calculation.
If the setpoint Dynamic Spinning Reserve (page 749) is enabled the InteliNeo6000 controller also participate
on DSR in the same way as Gen-set controllers. But the main idea of renewables is to run with the maximal
priority. So, in this case the Microgrid site will not react on Load Reserve + DSR starting because it should
already run. In InteliNeo6000 controller this setpoint should be used only to have the same calculation of Load
Reserve and DSR as rest of controllers in group.
Starting sequence
As written above, the power management is based on the load evaluation in order to provide enough of available
running power. An additional BESS starts when the load of the system raises above certain level to keep the load
reserve big enough. Following figure depicts the situation when an additional BESS is requested to join the
already running BESS(s) to the bus.
Image 5.123 Start sequence of power management

As shown above, the load of the system has increased above the level defined by the start condition – i.e. the
load reserve is not sufficient as required by the appropriate setpoint. Further explanation is provided in chapters
Absolute power management (page 275) and Relative power management (page 277).
The level is illustrated by the green dashed line. If the load reserve keeps insufficient for longer time than defined
by the setpoint #Next Engine Start Delay (page 501), the next BESS is actually started. The standard starting
sequence follows. Once the synchronization procedure is done, the BCB breaker is closed and the BESS power
is ramping up. Once loaded, the system load reserve is raised and becomes sufficient again. Please note the
sum of nominal power of all BESSs on the bus is increased by the nominal power of the additional BESS.
Stopping sequence
As it is written above, the power management is based on the load evaluation in order to provide enough of
available running power. An additional BESS stops when the load of the system drops below certain level to
avoid inefficient run of the BESS. Following figure depicts the situation when a BESS is requested to stop due to
the power management.
Image 5.124 Stopping sequence of power management
As shown above, the system load has decreased below the level defined by the stop condition – i.e. the load
reserve is over a limit given by the appropriate setpoint. Further explanation is provided in chapters Absolute
power management (page 275) and Relative power management (page 277).
The level is illustrated by the red dashed line. If the load reserve keeps over this limit for longer time than defined
by setpoint #Next Engine Stop Delay (page 502), the next BESS is actually requested to stop. Once the BESS
is unloaded, the BCB breaker is opened. Please note the sum of nominal power of all BESSs on the bus is
decreased by the nominal power of the stopped BESS. The cooling sequence follows before the BESS is actually
stopped. The BESS is ready to be started if the system load increases again.

Absolute power management

The power management based on absolute load reserves can be successfully used in cases the load portions
are similar to the BESS capacity or even bigger. The goal of the absolute reserve mode is to provide the same
load reserve all the time independently on how many BESSs are currently running. The mode perfectly fits for
industrial plants with large loads.
The absolute power management guarantees adjustable load reserve in kW. This mode is active when #Power
Management Mode (page 482) is set to ABS [kW] mode.
Image 5.125 Power management based on absolute load reserve
Example: An example of absolute power management is shown on the figure below. There are three
BESSs with following choice of setpoints:

#Starting
#Power #Priority #Stopping
Nominal Power Load
BESS management Priority Auto Load
power management Reserve
mode Swap Reserve X
X
BESS
200 kW Enabled ABS (kW) 1 Disabled 100 kW 125 kW
#1
BESS
#2
BESS
1 000 kW Enabled ABS (kW) 3 Disabled 100 kW 125 kW
#3
Image 5.126 Absolute power management example
As it is shown on both figures above, the additional BESS is added once the actual load reserve is below the level
given by the appropriate setpoint of load reserve. The additional BESS is removed once the actual load reserve
is above the level set by appropriate setpoint of load reserve.

The green dashed line depicts the value of load at which the additional BESS is requested to start. This value of
the load value is linked with the setpoint #Starting Load Reserve 1 (page 488) (or other selected reserve set) in
following way:
Sum of nominal power for start - #Starting Load Reserve 1 (page 488) (or other selected reserve set) = value of
load when additional BESS requested to start (e.g.: 700 kW – 100 kW = 600 kW).
The red dashed line depicts the value of load at which the additional BESS is requested to stop. This value of the
load value is linked with the setpoint #Stopping Load Reserve 1 (page 489) (or other selected reserve set) in
following way:
Sum of nominal power for stop - #Stopping Load Reserve 1 (page 489) (or other selected reserve set) = value
of load when additional BESS requested to stop (e.g.: 700 kW – 125 kW = 575 kW).
There are 2 sets of setpoints for starting and stopping BESSs in absolute power management.
#Starting Load Reserve 1 (page 488) and #Stopping Load Reserve 1 (page 489)
#Starting Load Reserve 2 (page 491) and #Stopping Load Reserve 2 (page 492) considered if binary
input LOAD RES 2 ACTIVE (PAGE 898) is activated
Note: All controllers cooperating together in Power management must have the same load reserve set selected.
Relative power management

The power management based on relative load reserves perfectly fits to those applications with such load
portions connected to the group at once are much lower than the BESS nominal power. This mode helps to
achieve the maximal lifetime of the BESSs, as they can be operated within optimal load range. The maximal size
of the load connected at once depends on number of actually working BESSs. The more BESSs are connected
to the bus bar the bigger load portion can be connected at once.
The relative power management guarantees that the engines are not continuously loaded more than to a certain
level. This mode is active when #Power Management Mode (page 482) is set to REL [%] mode.

Image 5.127 Power management based on relative load reserve
Example: An example of relative power management is shown on the figure below. There are three
BESSs with following choice of setpoints:
#Starting
Nominal Power Rel Load
BESS management Priority Auto Rel Load
mode Swap Reserve X
X
BESS
200 kW Enabled REL (%) 1 Disabled 35 % 40 %
#1
BESS
500 kW Enabled REL (%) 2 Disabled 35 % 40 %
#2
BESS
1 000 kW Enabled REL (%) 3 Disabled 35 % 40 %
#3

Image 5.128 Relative power management example
As it is shown on both figures above, the additional BESS is added once the actual load reserve is below the level
given by the appropriate setpoint of load reserve. The additional BESS is removed once the actual load reserve
is above the level set by appropriate setpoint of load reserve.
The green dashed line depicts the value of load at which the additional BESS is requested to start. This value of
the load value is linked with the setpoint #Starting Rel Load Reserve 1 (page 490) (or other selected reserve
set) in following way:
(100 % - #Starting Rel Load Reserve 1 (page 490) (or other selected reserve set)) * Sum of Nominal power =
Value of load when additional BESS requested to start in kW (in % of nominal power), e.g.: (100 % – 35 %) * 700
kW = 455 kW (65 % of nominal power).
The red dashed line depicts the value of load at which the additional BESS is requested to stop. This value of the
load value is linked with the setpoint #Stopping Rel Load Reserve 1 (page 490) (or other selected reserve set)
in following way:

(100 % - #Stopping Rel Load Reserve 1 (page 490) (or other selected reserve set)) * Sum of Nominal power =
Value of load when additional BESS requested to stop in kW (in % of nominal power), e.g.: (100 % – 40 %) * 700
kW = 420 kW (60 % of nominal power).
There are 2 sets of setpoint for starting and stopping BESSs in relative power management.
#Starting Rel Load Reserve 1 (page 490) and #Stopping Rel Load Reserve 1 (page 490)
#Starting Rel Load Reserve 2 (page 493) and #Stopping Rel Load Reserve 2 (page 493) considered
if binary input LOAD RES 2 ACTIVE (PAGE 898) is activated
Note: All controllers cooperating together in Power management must have the same load reserve set selected.
Priorities
The priority of the BESS within the group is given by the setpoint Priority (page 483). Lower number represents
"higher" priority, i.e. a BESS with lower number starts before another one with higher number. In other words, the
setpoint Priority (page 483) means order in which BESSs are started and connected to the bus. An example is
shown on the figure below. There are four BESSs with following choice of setpoints:
#Starting
Nominal Power Load
BESS management Priority Auto Load
mode Swap Reserve X
X
BESS
#1
BESS
#2
BESS
#3
BESS
#4

Image 5.129 Example of priorities in power management
By choosing the setpoint Priority (page 483) = 1, the BESS #4 is running all the time in the example shown on
the figure above (AUTO mode selected, Power management enabled and LBI REMOTE START/STOP (PAGE 915)
activated).
The LBI TOP PRIORITY (PAGE 918) can be used to force priority 0 into the setpoint Priority (page 483). Priority 0
is the "highest" one, which means the BESS will be running all the time while the power management is switched
on.
If more than one BESS have the same priority, they will act as "one big" BESS. There are methods of automatic
optimization of the priorities to achieve specific behavior of the group such as equalizing engine hours of the
BESSs or selection of optimal BESSs to run according to their size and current load demand.
Priority auto swap

As stated in the chapter Priorities (page 280), the operator is able to select the order of BESS starting. There is
also the option of automatic priority selection. The controllers are sharing data concerning the running hours and
all important information relevant to the actual load. Thanks to the Automatic priority swapping function the
controllers choose the BESS(s) to be running with consideration of their running hours and the actual load.

The running hours equalization function keeps a constant maximal difference of BESS’s running hours. The
efficient function keeps running only the BESSs with suitable nominal power to avoid inefficient fuel consumption
or BESS overload.
Note: The Automatic priority swapping function does not change the setpoint Priority (page 483). The function
sets the order of BESSs by virtual values “engine priority”.
Run hours equalization

The BESSs engine priorities are automatically swapped to balance engine running hours. In other words, the
controllers compare running hours of each BESS and select BESS(s) to run in order to maintain constant
maximal difference of running hours. Up to 32 controllers are supported. This function is activated via setpoint
#Priority Auto Swap (page 484) = RUN HOURS.
The value of running hours which is used in run hours equalization is calculated by following formula:
RHE = Running Hours (page 771) - Run Hours Base (page 505)
RHE is considered value for running hours equalization, Running Hours (page 771) is a cumulative sum of run
hours available in statistic values of the controller, Run Hours Base (page 505) is a setpoint. This setpoint may
be used in the case of BESSs with different runs hours are intended to be set at the same initial point (e.g. a new
BESS and a used BESS after retrofit maintenance inspection).
The Running hours equalization function compares RHE value of each controller in the group. Once the
difference between RHE of individual controllers is higher than #Run Hours Max Difference (page 506) (i.e.
#Run Hours Max Difference (page 506) + 1), the BESS(s) with the lowest RHE is/are started.
Example: The system structure and its settings is shown on the figure below.
Image 5.130 Example of the system
3 cases are considered:

Case #1: 2 Gen-sets available
Case #2: 3 Gen-sets available with same initial RHE.
Case #3: 3 Gen-sets available with different initial RHE.
Case #1:
BESS 1 running hours = 250 -> running hours considered in RHE = 100 (150 - Run Hours Base (page
505))

BESS 2 running hours = 450 -> running hours considered in RHE = 200 (250 - Run Hours Base (page
505))
Both BESSs have the same nominal power of 700 kW. Originally, priority of BESSs was G1 = 2, G2 = 1. Load
demand in this example is constant and it is 500 kW (i.e. only one engine is running at any time). In this case, the
controllers set the engine priority of the BESS 1 to 1 because it has the lowest considered RHE and the
difference between RHE2 (i.e. considered RHE of BESS 2) and RHE1 is higher than #Run Hours Max
Difference (page 506) that is set to 10h.
Run hours #RunHoursBase RHE

BESS #1 250 150 100
BESS #2 450 250 200
The BESS 1 runs for 100 hours to equalize the RHE of both BESSs. The BESS 1 keeps running until the
difference between RHE1 and RHE2 exceeds #Run Hours Max Difference (page 506) (i.e. 10h). The BESS 1
runs 100 + #Run Hours Max Difference (page 506) + 1 = 100 + 10 + 1 = 111 hours. After 111 hours the BESSs
2 has the lowest RHE and the difference between RHE1 and RHE2 is higher than #Run Hours Max Difference
(page 506). The BESS 2 runs 11 hours to equalize the RHE of both BESSs and then additional #Run Hours
Max Difference (page 506) + 1 hours (i.e. 11 + 10 + 1 = 22 hours). The evaluation of RHE1 and RHE2 is shown
on the figure below.
Image 5.131 Run hours equalization - case #1
Step 0 1 2 3 4 5
RHE1 100 211 211 233 233 255
RHE2 200 200 222 222 244 244
Run G1 (ΔRHE1) 0 111 0 22 0 22
Run G2 (ΔRHE2) 0 0 22 0 22 0
From the example of the case #1, it can be concluded that the BESSs are swapped after the duration determined
by following formula:
SwapTime = Second lowest considered running hours – Current lowest considered running hours + #Run Hours
Max Difference (page 506) +1

Case #2:
BESS 1 running hours = 0 -> running hours considered in RHE = 0 (0-RunHoursBase)
Each BESS has the same RHE = 0 h. By applying the SwapTime formula, we get the run time of BESS 1 before
next swapping:
SwapTimeG1 = 0 – 0 + 10 + 1 = 11
Similar way, we get the run time of BESS 2 before next swapping:
SwapTimeG2 = 11 – 11 + 10 + 1 = 11
Finally, we get the run time of BESS 3 before next swapping:
SwapTimeG2 = 11 – 0 + 10 + 1 = 22
Please refer to figure below to understand the evaluation of RHE of BESSs in this particular case.
step 0 1 2 3 4 5 6 7 8 9 10 11 12 13
RHE1 0 11 11 11 11 33 33 33 33 55 55 55 55 77
RHE2 0 0 11 11 22 22 33 33 44 44 55 55 66 66
RHE3 0 0 0 22 22 22 22 44 44 44 44 66 66 66
Run G1
0 11 0 0 0 22 0 0 0 22 0 0 0 22
(ΔRHE1)
Run G2
0 0 11 0 11 0 11 0 11 0 11 0 11 0
(ΔRHE2)
Run G3
0 0 0 22 0 0 0 22 0 0 0 22 0 0
(ΔRHE3)
Case #3:
The BESS 1 has the lowest RHE1 = 100 h. By applying the SwapTime formula, we get the run time of BESS 2
before next swapping:

SwapTimeG1 = 200 – 100 + 10 + 1 = 111
Till the step 5, the evaluation of the BESS swapping is the same as in the case #1, just BESS 1 and BESS 2
involve. In the step 6 the BESS 2 can run only 17 hours (previously 22 hours) because the BESS 3 involves. The
evaluation of RHE1, RHE2 and RHE3 is shown on the figure below.
step 0 1 2 3 4 5 6 7 8 9 10 11 12 13
RHE1 100 211 211 232 233 255 255 255 272 272 272 288 288 288
RHE2 200 200 222 222 244 244 261 261 261 277 277 277 294 294
RHE3 250 250 250 250 250 250 250 266 266 266 283 283 283 299
Run G1
(ΔRHE 0 111 0 22 0 22 0 0 17 0 0 16 0 0
1)
Run G2
(ΔRHE 0 0 22 0 22 0 17 0 0 16 0 0 17 0
2)
Run G3
(ΔRHE 0 0 0 0 0 0 0 16 0 0 17 0 0 16
3)
Note: Setting #Run Hours Max Difference (page 506) = 5 does not mean that BESSs swap every 5 hours. The
Swap time is determined by the formula stated above. Please read the entire chapter Running hours
equalization for better understanding.
Note: In the case #Run Hours Max Difference (page 506) is set to 0 and all BESS in the group are at the same
initial point (RHE are equal), the BESS swapping happens every hour.
Efficiency
The BESSs engine priorities are automatically swapped to best fit to the actual load demand (load demand swap
- LDS). Also engine running hours are taken to the calculation (run hours equalization - RHE). This function is
activated via setpoint #Priority Auto Swap (page 484) = Efficiency.
The BESSs which should be currently running with actual load are shown in the values Actual Power Band 32
(page 752) and Actual Power Band 64 (page 752). The BESSs which should be running after #Power Band

Change Up Delay (page 506) or #Power Band Change Down Delay (page 507) elapsed, if load is increased
or decreased, are shown in the values Next Power Band 32 (page 752) and Next Power Band 64 (page 753).
Algorithm of function:
In the first step, the BESSs are sorted according to their nominal power.
In the second step, the BESSs with the same nominal power are sorted according to their RHE
The BESS(s) with nominal power which fits the most actual load demand are chosen. From those with
same nominal power, the BESS(s) with lowest RHE are chosen. Selection formula:
#Power Management Mode (page 482) = ABS (kW)
Nominal power of BESS > actual load demand + #Starting Load Reserve 1 (page 488)
#Power Management Mode (page 482) = REL (%)
Nominal power of BESS > (actual load demand × 100)/(100 - #Starting Rel Load Reserve 1
(page 490))
If two or more BESSs are available for taking over the load always the one with the lowest CAN address is
chosen.
If load demand is higher than nominal power of the biggest BESS, this one is fixed and the whole process
repeats from point the third bullet.
Example: The system structure and its settings is shown on the figure below.
Image 5.134 Example of the system
Following table provide an example of BESS selection in function of system load evaluation. The table is an
example of Efficiency priority optimization function (#Power Management Mode (page 482) = ABS (kW) and
#Starting Load Reserve 1 (page 488) = 20 kW).
Total Running
System Relative load
Running BESSs Description power within PM
Load [kW] of BESSs [%]
[kW]
40 5 100 40
60 5 100 60
5 2 start
80 LDS 300 26
2 [0h] 5 stop

Total Running
[kW]
100 2 [10h] 200 50
120 2 [20h] 200 60
2 [30h] 3 start
120 RHE Swap 400 30
3 [10h] 2 stop
120 3 [20h] 200 60
140 3 [30h] 200 70
3 [40h] 1 start
180 LDS 500 36
1 3 stop
200 1 300 67
240 1 300 80
1
280 5 start Gen#5 joins (LDS) 400 70
5
1
340 400 85
5
1
4 start
380 5 LDS + RHE Swap 600 63
5 stop
4 [20h]
1
400 500 80
4
1
440 500 88
4
1
480 4 5 start Gen#5 joins (LDS) 600 80
5
1
540 4 600 90
5
1
4 2 start
580 LDS 800 73
5 5 stop
2 [30h]
1
600 4 700 86
2
1
640 4 700 91
2
1
680 5 start Gen#5 joins (LDS) 800 85
4

Total Running
[kW]
2
5
1
4
740 800 93
2
5
1
4
3 start
780 2 LDS 1000 78
5 stop
5
3 [40h]
1
4
800 900 89
2
3
1
4
840 900 93
2
3
1
4
880 2 5 start Gen#5 joins (LDS) 1000 88
3
5
1
4
940 2 1000 94
3
5
Minimal running power

Minimum Running Power function is used to adjust a minimum value of the sum of nominal power of all running
Controllers. If the function is active, then the Controllers would not be stopped, although the reserve for stop is
fulfilled. Function is activated via logical binary input MIN RUN POWER ACT 1 (PAGE 904), MIN RUN POWER ACT 2
(PAGE 904) and MIN RUN POWER ACT 3 (PAGE 905).

Image 5.135 Minimal running power
Setpoints #Min Run Power (page 500), #Min Run Power 2 (page 500) or #Min Run Power 3 (page 501) are
adjusted to 400 kW. Once the #Min Run Power (page 500), #Min Run Power 2 (page 500) or #Min Run
Power 3 (page 501) is activated, the available nominal running power has to be equal or higher to 400 kW. Even
if the load reserve is big enough to stop the Controller #2 (nominal power 500 kW), the Controller keeps running
as at least 400 kW has to be available. The Controller#1 (nominal power 200 kW) is not enough.

5.5.17 PV Curtailment
This function allows to limit power generated by PV (renewable source) inverter. The PI regulation (setpoints
Gain (page 455) and Int (page 456)) is used to regulate relative power of PV if the setpoint Curtailment
(page 455) is Enabled, BESS is not present in the system or it cannot consume any more power from the
system and power of Gen-sets goes below Gen P Min (page 456). The power of the PV is regulated
according to the PI regulation loop until the power of Gen-sets is equal to Gen P Min (page 456). The
PI regulation loop is also used to increase power of the PV if the relative power of the Gen-sets is above the
Gen P Min (page 456) and PV is not already running on 100 % of its nominal power.
If the function Curtailment is Disabled the setpoint Gen P Min (page 456) is still used in the function Load
Control Balance - Calculation of BESS P Request (page 236) because the BESS can still react on power
excess. The LBO CURTAILMENT ENABLE (PAGE 939) is activated always when the curtailment is used to
regulate power of the PV. The actual maximal power of the PV inverter in percents is shown by the value
Curtailment Output (page 703).
Note: The maximal charging power of the BESS depends on the LAI BESS MAX CHARGE P (PAGE 984).
5.5.18 Regulation Loops

Regulation loops overview
Regulation loops overview
Related
Loop type Related setpoints Related Operation
applications
Unloaded Run
Frequency Gain (page 460)
Frequency MINT, MPTM Synchronization
Frequency Int (page 461)
Single Island
Unloaded Run
Voltage Gain (page 473)
Voltage MINT, MPTM Synchronization
Voltage Int (page 473)
Single Island
Angle
MINT, MPTM Angle Gain (page 461) Phase Match Synchronization
regulation
Load Gain (page 462)
Load MINT, MPTM Parallel To Mains
Load Int (page 462)
PF Gain (page 474)
PF control MINT, MPTM Parallel To Mains
PF Int (page 474)
Load Sharing Gain (page 463)
Load sharing MINT Multiple Island
Load Sharing Int (page 463)
VAr Sharing Gain (page 475)
VAr sharing MINT Multiple Island
VAr Sharing Int (page 475)
Voltage, PF, VAr sharing have one common output = Voltage Request (page 758). The value of this output is
always composed from the contribution of each of the regulation loop.
Each of the regulation loops is active in some certain time during the process, which is given by the state of the
electronic state machine. If no regulation loop is active the Frequency Regulator Output (page 754) and

Voltage Regulator Output (page 758) are kept on the levels given by setpoints Frequency Governor Bias
(page 458) and Voltage Regulator Bias (page 471).
Note: All regulation loops are PID, but only PI components are visible as setpoints.
MINT Regulation Loops
Loop type Description

The frequency loop is active in the first phase of synchronization when the BESS frequency is
regulated to match the Mains/bus frequency and in single-island operation. The loop can be
also active all the time (while the BESS is running without load at nominal frequency ), see the
Frequency
setpoint Frequency Regulation Loop (page 460).
The frequency regulation loop can be active after the Minimal Stabilization Time (page 432)
elapsed in case of DC precharge or after BESS is loaded in case of AC precharge.
The voltage regulation loop is active in the first phase of synchronization when the BESS
voltage is regulated to match the Mains/bus voltage and in single-island operation. The loop is
Voltage also active when BESS is running without load (GCB opened) after Minimal Stabilization
Time (page 432)elapsed in case of DC precharge or after BESS is loaded in case of
AC precharge.
Angle The differential angle control loop is active during the second phase of synchronization to
regulation match the gen/bus angle when phase match synchronization type is used.
The load regulation loop is active when BESS is running in parallel with Mains and during load
Load
transfers from Mains to BESS or vice versa.
PF control The PF/Q regulation loop is active when BESS is running in parallel with Mains.
Load
The load sharing loop is active only in multiple-island operation.
sharing
VAr sharing The VAr sharing loop is active only in multiple-island operation.

MPTM Regulation Loop
Loop type Description

The frequency loop is active in the first phase of synchronization when the BESS frequency is
regulated to match the Mains/bus frequency and in single-island operation. The loop can be
also active all the time (while the BESS is running without load at nominal frequency ), see the
Frequency
setpoint Frequency Regulation Loop (page 460).
The frequency regulation loop can be active after the Minimal Stabilization Time (page 432)
elapsed in case of DC precharge or after BESS is loaded in case of AC precharge.
The voltage regulation loop is active in the first phase of synchronization when the BESS
voltage is regulated to match the Mains/bus voltage, in single-island operation, and when
Voltage
BESS is running without load (GCB opened) after Minimal Stabilization Time (page
432)elapsed in case of DC precharge or after BESS is loaded in case of AC precharge.
Angle The differential angle control loop is active during the second phase of synchronization to
regulation match the gen/bus or Mains/bus angle when phase match synchronization type is used.
The load regulation loop is active when BESS is running in parallel with Mains and during load
Load
The PF control loop is active when BESS is running in parallel with Mains and during load
PF control
Adjustment of regulation loops

The regulation loops have two adjustable factors: P-factor and I-factor (except angle regulation loop, which has
P-factor only). The P-factor (gain) influences the stability and overshoot of the regulation loop and the I-factor
(int) influences the steady-state error as well as the settling time. See the picture below for typical responses of a
PI regulation loop.
Image 5.136 Typical responses of PI regulator
For manual tuning of a control loop use following method:

Set both the I-factor and P-factor to 0.
Increase the P-factor slightly until the system starts to oscillate.
Adjust the P-factor back to approx. one half of the value where the oscillations started.
Increase the I-factor slightly to achieve optimal resulting response.

IMPORTANT: Be ready to press emergency stop button in case the regulation loop would start to
behave unacceptable while it is being adjusted.
6 back to Application related functions

6 Grid Codes
6.1 What are Grid Codes 294
6.2 Testing of Grid Codes 294
6.3 Power Regulation Based On Over/Under Frequency 294
6.4 Power Regulation Based On Actual Mains Voltage 297
6.5 Load Reduction 298
6.6 Dynamic Support - VRT 299
6.7 P For Q 301
6.8 Q&U Protection 302
6.9 Synchronization & Connection Conditions 302
6.10 After Mains Trip Period 303
6.11 Pave 304
6.12 Moving Average 304
6.13 BESS Operation Area 305
6.1 What are Grid Codes

Grid Codes are technical specifications which defines the parameters a facility connected to a public electric
network has to meet to ensure safe, secure and economic proper functioning of the electric system. The facility
can be an power generation plant, a solar farm, or any other grid connected source.
6.2 Testing of Grid Codes

Grid Codes functions can be tested. To enable Grid Codes testing setpoint Grid Codes Test (page 527) has to
be Enabled. When testing mode is active, alarm Wrn Test UPQF (page 1103) is present in the alarmlist.
LAIs related to testing:
LAI TESTF (PAGE 1008)
LAI TESTP (PAGE 1009)
LAI TESTQ (PAGE 1009)
LAI TESTU (PAGE 1009)
6.3 Power Regulation Based On Over/Under

Frequency
In case of over/under frequency, BESS must be able to reduce/increase the BESS P (page 664).
To enable these functions, setpoint Power Over/Under Frequency (page 535) has to be Enabled.
6.3.1 Power reduction by over frequency - PoF

The BESS must be able to reduce BESS P (page 664) in Mains/Bus Frequency (page 731) - range of
<Nominal Frequency (page 377) + 0,2 Hz, Nominal Frequency (page 377) + 1,5 Hz>. When Mains/Bus
Frequency (page 731) is in range defined by PoF for time longer than Power Over/Under Frequency Delay
(page 535), power reduction will begin. If the Mains/Bus Frequency (page 731) is over Nominal Frequency
(page 377) + 1,5 Hz, BESS can disconnect from the mains.

Note: Power Over/Under Frequency (page 535) has to be Enabled, otherwise PoF is not applied.
Power reduction is defined by Application Curve POWER OVER FREQUENCY (PAGE 866) which shall be adjusted
according to this formula:
After Mains/Bus Frequency (page 731) reaches (Nominal Frequency (page 377) + 0,2 Hz), BESS P (page
664) is stored in Pmom (page 721) and from this value is the power decreased.
Power is decreased/increased based on ramp (BESS Required P (page 753) is ramped to BESS Required P
Target (page 753)) that is corresponding with actual active event.
Note: If representative priority setpoint of actual active event is adjusted to OFF, then BESS Required P
(page 753) is ramped to BESS Required P Target (page 753) based on Load Ramp (page 468).
Event Used Ramp

LBO EVENT MAINS FREQUENCY RISE (PAGE 944) Mains Frequency Rise Ramp (page 538)
LBO EVENT MAINS FREQUENCY FALL (PAGE 944) Mains Frequency Fall Ramp (page 539)
While power is reduced due to over frequency, LBO P OVER FREQUENCY ACTIVE (PAGE 965) is closed.
PoF related settings

Setpoints Values
Power Over/Under Frequency (page 535) Pmom (page 721)
Power Over/Under Frequency Delay (page 535) P Over Frequency Curve (page 721)
Mains Frequency Rise Priority (page 538) BESS Required P (page 753)
Mains Frequency Rise Ramp (page 538) BESS Required P Target (page 753)
Mains Frequency Fall Priority (page 539) LBOs
Mains Frequency Fall Ramp (page 539) P OVER FREQUENCY ACTIVE (PAGE 965)
Application Curves P OVER FREQUENCY CURVE INVALID (PAGE 965)
POWER OVER FREQUENCY (PAGE 866) EVENT MAINS FREQUENCY RISE (PAGE 944)
EVENT MAINS FREQUENCY FALL (PAGE 944)
Grid Codes Test (page 527) = Enabled
6.3.2 Power increase by under frequency - PuF

The BESS must be able to increase BESS P (page 664) in Mains/Bus Frequency (page 731) range of
<Nominal Frequency (page 377) - 2,5 Hz, Nominal Frequency (page 377) - 0,2 Hz>. When Mains/Bus
Frequency (page 731) is in range defined by PuF for time longer than Power Over/Under Frequency Delay
(page 535), power increase will begin. If the Mains/Bus Frequency (page 731) is under Nominal Frequency
(page 377) - 2,5 Hz, BESS can disconnect from the mains.
Note: Power Over/Under Frequency (page 535) has to be Enabled, otherwise PuF is not applied.
Power increase is defined by Application Curve POWER UNDER FREQUENCY (PAGE 867) which shall be adjusted
according to this formula:

.
After Mains/Bus Frequency (page 731) drops bellow (Nominal Frequency (page 377) - 0,2 Hz), BESS P
(page 664) is stored in Pmom (page 721) and from this value is the power increased.
Power is decreased/increased based on ramp (BESS Required P (page 753) is ramped to BESS Required P
Target (page 753)) that is corresponding with actual active event.
Note: If representative priority setpoint of actual active event is adjusted to OFF, then BESS Required P
(page 753) is ramped to BESS Required P Target (page 753) based on Load Ramp (page 468).
Event Used Ramp

LBO EVENT MAINS FREQUENCY RISE (PAGE 944) Mains Frequency Rise Ramp (page 538)
LBO EVENT MAINS FREQUENCY FALL (PAGE 944) Mains Frequency Fall Ramp (page 539)
While power is increased due to under frequency, LBO P UNDER FREQUENCY ACTIVE (PAGE 965) is closed.
PuF related settings

Setpoints Values
Power Over/Under Frequency (page 535) Pmom (page 721)
Power Over/Under Frequency Delay (page 535) P Over Frequency Curve (page 721)
Mains Frequency Rise Priority (page 538) BESS Required P (page 753)
Mains Frequency Rise Ramp (page 538) BESS Required P Target (page 753)
Mains Frequency Fall Priority (page 539) LBOs
Mains Frequency Fall Ramp (page 539) P UNDER FREQUENCY ACTIVE (PAGE 965)
Application Curves P UNDER FREQUENCY CURVE INVALID (PAGE 965)
POWER UNDER FREQUENCY (PAGE 867) EVENT MAINS FREQUENCY RISE (PAGE 944)
EVENT MAINS FREQUENCY FALL (PAGE 944)
6.3.3 Return from over/under frequency

After Mains/Bus Frequency (page 731) returns into range (Nominal Frequency (page 377) - 0,2 Hz, Nominal
Frequency (page 377) + 0,2 Hz), EVENT RETURN OVER/UNDER FREQUENCY (PAGE 945) begins.
The start of the event can be delayed by the setpoint Return Over/Under Frequency Delay (page 536), once
the delay timer is elapsed the LBO EVENT RETURN OVER/UNDER FREQUENCY (PAGE 945) is closed for the period
given by the setpoint Return Over/Under Frequency Period (page 536). When the event is active, BESS
Required P (page 753) is always ramped to the BESS Required P Target (page 753) based on Return From
Over/Under Frequency Ramp (page 537).
Each Grid Code has its priority over the other Grid Codes. The priority of the Return from over/under frequency is
given by the setpoint Return From Over/Under Frequency Priority (page 537).
Note: If Return From Over/Under Frequency Priority (page 537) = OFF, then BESS Required P (page
753) is ramped to BESS Required P Target (page 753) based on Load Ramp (page 468).

6.4 Power Regulation Based On Actual Mains
Voltage
The BESS's BESS P (page 664) is regulated based on value +Mains/Bus Voltage Relative (page 733). In
case that +Mains/Bus Voltage Relative (page 733) is over 100 %, application curve P(Um) (page 862) is
activated and BESS P (page 664) becomes limited. Ramping of value BESS Required P (page 753) to BESS
Required P Target (page 753) is affected by setpoint P Ramp Filter (page 545).
There are two modes modes of this function.
6.4.1 P Instal (Um)

Setpoint P(Um) (page 544) has to be adjusted to P Instal (Um). This mode is then related to the setpoint
Installed Power (page 368). Maximal allowed BESS P (page 664) is calculated as:
P Instal (Um) related settings

Setpoints Values
Installed Power (page 368) P(Um) Curve (page 723)
P(Um) (page 544) LBOs
P Ramp Filter (page 545) EVENT P(UM) (PAGE 945)
P(Um) Priority (page 546)
P(Um) Ramp (page 546) Grid Codes Test (page 527) = Enabled
Application Curves LAI TESTU (PAGE 1009)
P(UM) (PAGE 862)
6.4.2 P Actual (Um)

Setpoint P(Um) (page 544) has to be adjusted to P Instal (Um). This mode is then related to value Pmom
(page 721). Value Pmom (page 721) is filled with BESS P (page 664) at the moment of activation of this
function. Maximal allowed BESS P (page 664) is calculated as:
PuF related settings

Setpoints Values
P(Um) (page 544) Pmom (page 721)
P Ramp Filter (page 545) P(Um) Curve (page 723)
P(Um) Priority (page 546) LBOs
P(Um) Ramp (page 546) EVENT P(UM) (PAGE 945)
Application Curves
POWER UNDER FREQUENCY (PAGE 867)
LAI TESTU (PAGE 1009)

6.5 Load Reduction
The controller allows remote load control of the BESS. This mechanism is dedicated for purposes when utility
company wants to control the BESS's load on predefined load levels. To enable this function it is necessary to set
setpoint Load Reduction (page 540) to Enabled and activate the LBI LOAD REDUCTION ENABLE (PAGE 897).
Each state of the Load Reduction is activated by the specific LBI Load Reduction and each LBI is connected with
the same named setpoint which adjust relative maximal power produced by the BESS. Or the maximal allowed
load of the BESS can be defined by the LAI LOAD REDUCTION (PAGE 990). Always the lowest load defined by the
LAI or by LBIs is allowed. If more than 1 LBI Load Reduction is activated, then reduction with the smallest
setpoint value is applied. When any Load Reduction state is active the LBO LOAD REDUCTION ACTIVE (PAGE 954)
is closed.
Note: The LAI LOAD REDUCTION (PAGE 990) allows the power reduction on the analog signal, but the statistic will
not be fulfilled.
The activation of the Load Reduction event is being signalized by closing the LBO EVENT LOAD REDUCTION (PAGE
944). Once the LBO is closed the BESS Required P (page 753) will be ramped to the BESS Required P
Target (page 753) according to the ramp which maximum is given by the setpoint Installed Power (page 368)
or by the setpoint Nominal power (page 368) if the Installed Power is OFF. The duration of the whole ramp
(from the maximum to the 0) is given by the setpoint Load Reduction Ramp (page 543).
The event and LBO EVENT LOAD REDUCTION (PAGE 944) stays active after deactivation of all LBIs until BESS
Required P (page 753) is ramped to the new unreduced BESS Required P Target (page 753) according to
Load Reduction Ramp (page 543). So, the event Load Reduction is active for both reducing and increasing the
power.
Each Grid Code has its priority over the other Grid Codes. The priority of the Load Reduction is given by the
setpoint Load Reduction Priority (page 542). If this priority is set to OFF, then BESS Required P (page 753)
will be ramped to the BESS Required P Target (page 753) according to the Load Ramp (page 468).
IMPORTANT: LBI LOAD REDUCTION ENABLE (PAGE 897) has to be closed and setpoint Load Reduction
(page 540) has to be Enabled, otherwise Load Reduction is not activated by any of LBIs mentioned
bellow.
List of LBIs and related setpoints

LBI Setpoint
LOAD REDUCTION 1 (PAGE 896) Load Reduction 1 (page 540)
Example: When LBI LOAD REDUCTION 1 (PAGE 896) is activated and setpoint Load Reduction 1 (page
540) = 50%, then BESS's load will be limited to 50% of Installed Power (page 368) or Nominal power
(page 368).

6.6 Dynamic Support - VRT
Dynamic Support keeps the BESS voltage during short Mains failures on medium or high voltage site for
unwanted disconnection of big power sources which could reduce Mains unbalances.
There are 4 kinds of Dynamic Support protections. To enable any of them setpoint Dynamic Support (page
552) != Disabled and behavior of the protections is adjusted via Dynamic Support Protection Type (page
552).
For a critical undervoltage there is special setpoint LVRT Level Severe (page 553) when relative mains voltage
drops bellow this limit, LBO LVRT SEVERE (PAGE 958) is closed for at least 500 ms, no further action is taken.
Note: You can deactivate PF/Q regulation while VRT function is active, use setpoint Dynamic Support PF/Q
Control (page 553) to select whether Voltage Regulator Output (page 758) will be frozen at the moment of
activation of the VRT function.
Image 5.137 VRT - Under voltage failure
6.6.1 3-pole undervoltage failure ride through - LVRT-3ph

This protection is defined by LVRT 3-PHASE (PAGE 872) curve and requires all three phases to be below allowed
limit in order to activate the protection.
Relative value of Mains/Bus Voltage L1-N (page 731), Mains/Bus Voltage L2-N (page 731) and
Mains/Bus Voltage L3-N (page 732) to Mains/Bus Nominal Voltage Ph-N (page 373)
Relative value of Mains/Bus Voltage L1-L2 (page 732), Mains/Bus Voltage L2-L3 (page 732) and
Mains/Bus Voltage L3-L1 (page 732) to Mains/Bus Nominal Voltage Ph-Ph (page 374)
When the curve is tripped, LBO LVRTCURVETRIP (PAGE 958) is closed, for at least 3 seconds, together with LBO
LVRT ACTIVE (PAGE 958), which stays closed for whole time the protection is active. Proper alarm/history record
is activated based on Dynamic Support Protection Type (page 552).

Note: Mains <V Protection (page 572) and Mains <V Protection (page 573) are still being evaluated! In case
that LVRT 3-PHASE (PAGE 872) is not configured correctly or is missing, LBO LVRT 3-PHASE INVALID (PAGE 958)
is closed and the protection is not evaluated.

This protection is defined by LVRT 2-PHASE (PAGE 873) curve and requires at least two phases to be below
allowed limit in order to activate the protection.

This protection is defined by LVRT 1-PHASE (PAGE 874) curve and requires at least one phase to be below
allowed limit in order to activate the protection.
6.6.4 Overvoltage failure ride through - OVRT

This protection is defined by OVRT (PAGE 875) curve and requires at least one phase to be above allowed limit in
order to activate the protection.
When the curve is tripped, LBO OVRTCURVETRIP (PAGE 964) is closed, for at least 3 seconds, together with LBO
OVRT ACTIVE (PAGE 964), which stays closed for whole time the protection is active. Proper alarm/history record

Note: Mains >V Protection (page 568) and Mains >>V Protection (page 570) are still being evaluated! In
case that OVRT (PAGE 875) is not configured correctly or is missing, LBO OVRT INVALID (PAGE 964) is closed
and the protection is not evaluated.
6.6.5 Post VRT

If the Application Mode (page 777) = MPTM, the protection is activated once LBO OVRT ACTIVE (PAGE 964) or
LBO LVRT ACTIVE (PAGE 958) is closed for a period longer than 5 seconds and BESS's current is higher than the
nominal current. In this case, the LBO EVENT POST VRT (PAGE 945) is closed and BESS P (page 664) is
decreased in order to keep circuit breakers closed. So, the BESS Required P (page 753) is ramped to the
BESS Required P Target (page 753) based on the ramp which maximum is given by the setpoint Installed
Power (page 368) or by the setpoint Nominal power (page 368) if the Installed Power is OFF and the duration
of the ramp is given by the setpoint Post VRT Ramp (page 554). The Post VRT is active for the maximal time
period of 60 seconds, after this period the standard Mains protection has to be evaluated.
If the Application Mode (page 777) = MINT the Post VRT can be activated only by activating the LBI POST VRT
(PAGE 905). In this case, the Post VRT is activated (the LBO EVENT POST VRT (PAGE 945) is closed) if BESS's
current is higher than the nominal current and the LBI is active.
6.7 P For Q
The Grid codes connection requirements, namely for the medium voltage system, require a possibility of BESS
BESS P (page 664) reduction in order to achieve required BESS Q (page 665).
The function is enabled/disabled by setpoint P For Q Limitation (page 547) and behavior is adjusted by P For
Q Deadband (page 547).
If relative value of BESS Required Q (page 757) will be over limit, BESS P (page 664) will be decreased to
reach BESS Required Q (page 757). To prevent oscilation of BESS P (page 664) adjust properly P For Q
Deadband (page 547).
6.7.1 UQ Area
UQ area defines maximal reachable BESS Q (page 665) based on actual Mains voltage (Um). This area is
adjusted by P FOR Q UQ L (PAGE 868) - inductive part, and P FOR Q UQ C (PAGE 869) - capacity part.
Note: Um is counted as average of Mains/Bus Voltage L1-N (page 731), Mains/Bus Voltage L2-N (page
731) and Mains/Bus Voltage L3-N (page 732) related to Mains/Bus Nominal Voltage Ph-N (page 373).
The area is used while BESS P (page 664) = +-5% of Installed Power (page 368) and BESS P (page 664) can
be reduced only if the required BESS Q (page 665) is inside this area, otherwise LBO UQ-C AREA LIMIT (PAGE
978) respectively LBO UQ-L AREA LIMIT (PAGE 978) is closed and BESS P (page 664) is not reduced. In case
this is fulfilled, LBO P FOR Q ACTIVE (PAGE 965) is closed and BESS P (page 664) begins to be reduced using P
For Q Ramp (page 548). LBO EVENT P FOR Q (PAGE 945) is closed while P For Q Ramp (page 548) is being
used.
Note: P For Q Ramp (page 548) has priority given by P For Q Priority (page 548), different ramp with
higher priority can be active.
6.7.2 PQ Area
PQ area defines maximal reachable BESS Q (page 665) based on actual BESS P (page 664) related to
Installed Power (page 368). This area is adjusted by P FOR Q PQ L (PAGE 870) - inductive part, and P FOR Q
PQ C (PAGE 871) - capacity part.

The area is used while BESS P (page 664) is bellow Installed Power (page 368) and BESS P (page 664) can
be reduced only if the required BESS Q (page 665) is inside this area, otherwise LBO PQ-C AREA LIMIT (PAGE
967) respectively LBO PQ-L AREA LIMIT (PAGE 967) is closed and BESS P (page 664) is not reduced. In case
this is fulfilled, LBO P FOR Q ACTIVE (PAGE 965) is closed and BESS P (page 664) begins to be reduced using P
For Q Ramp (page 548). LBO EVENT P FOR Q (PAGE 945) is closed while P For Q Ramp (page 548) is being
used.
Note: P For Q Ramp (page 548) has priority given by P For Q Priority (page 548), different ramp with
higher priority can be active.
6.8 Q&U Protection

This protection watches behavior of the BESS in case of the drop of Mains Voltage and uses measurement
method of Symmetrical components (page 16).
BESS must be disconnected from the mains in case that Mains Voltage drops below a certain value of
Mains/Bus Nominal Voltage Ph-N (page 373) or Mains/Bus Nominal Voltage Ph-Ph (page 374) and BESS
is under excited.
The protection is enabled by setpoint Q&U Protection (page 549) and the behavior is adjusted by setpoints
Q&U < V (page 550), Q&U < Q (page 550), Q&U Protection Delay (page 551) and Q&U CB Selector (page
551).
When Mains/Bus Voltage L1-N (page 731) drops below relative limit given by Q&U < V (page 550) and at the
same time BESS Q (page 665) drops below limit given by Q&U < Q (page 550) minimally for period set by Q&U
Protection Delay (page 551), then breaker, selected by Q&U CB Selector (page 551), will be opened and
alarm Wrn Q&U Protection (page 1097) is activated.
Note: Breaker can not be reclosed if the alarm Wrn Q&U Protection (page 1097) is still present in alarm list.
6.9 Synchronization & Connection Conditions

Grid codes requires specific conditions to be fulfilled in order to synchronize BESS to the Mains. These
conditions take effect when BESS is running if setpoint Mains Params/MP Synchronization (page 527) =
Enabled.
This protection is checking mains voltage and frequency, if the parameters are not within limits, BESS is not
allowed to synchronize with the Mains. The alarm AHI SyncNotAllowed (page 1110) is activated and stays
active until the problem persists or BESS is stopped, then LBO SYNC TO MAINS ALLOWED (PAGE 977) is opened.
Note: This protection is evaluated only if BESS is running and is not synchronized with Mains.
6.9.1 Network connection/reconnection conditions

Synchronization is forbidden if:
Mains Params/MP Synchronization (page 527) = Enabled and
At least one of the Ph-N voltages such as Mains/Bus Voltage L1-N (page 731) or Ph-Ph voltages such
as Mains/Bus Voltage L1-L2 (page 732) (depends on the type of wiring) is out of the relative limit
adjusted by Mains Synchronization V Max (page 528) and Mains Synchronization V Min (page 528).
Mains/Bus Frequency (page 731) is out of the limit adjusted by Mains Synchronization f Max (page
529) and Mains Synchronization f Min (page 529).
Note: Alarm AHI SyncNotAllowed (page 1110) is active while synchronization is forbidden.

Note: Network connection/reconnection conditions after Mains Fail (page 303) has higher priority
while it is active.
6.9.2 Network connection/reconnection conditions after Mains

Fail
When the Mains Fail occurs (MAINS/BUS HEALTHY (PAGE 959)) is opened), there is a requirement to prevent the
connection to the unstable mains. Timer After MP Synchronization Period (page 532) is activated and
synchronization to Mains is forbidden for this time (LBO SYNC TO MAINS ALLOWED (PAGE 977) is opened and
alarm AHI SyncNotAllowed (page 1110) is active).
For Mains Params/MP Synchronization (page 527) = Enabled the synchronization is allowed only if all Mains
parameters are within the limit for the whole time of the After MP Synchronization Period (page 532).
All of the Ph-N voltages such as Mains/Bus Voltage L1-N (page 731) and Ph-Ph voltages such as
Mains/Bus Voltage L1-L2 (page 732) (depends on the type of wiring) have to be within the limit adjusted
by After MP Synchronization V Max (page 530) and After MP Synchronization V Min (page 531).
Mains/Bus Frequency (page 731) have to be within the limit adjusted by After MP Synchronization f
Max (page 531) and After MP Synchronization f Min (page 532).
Note: Timer After MP Synchronization Period (page 532) resets every time parameters are not within limits.
6.10 After Mains Trip Period

When the Mains returns from failure, it is recommended to load it slowly to prevent another failure. To activate
this function it is necessary to set setpoint After Mains Trip (page 533) to Enabled. Once the Mains is healthy
(LBO MAINS/BUS HEALTHY (PAGE 959) is closed) and timer After MP Synchronization Period (page 532) is
elapsed or Mains Params/MP Synchronization (page 527) is disabled the LBO EVENT MAINS TRIP (PAGE 945)
is closed for time given by the setpoint After Mains Trip Period (page 533).
Note: Timer After Mains Trip Period (page 533) resets every time MAINS/BUS HEALTHY (PAGE 959) re-
closes.
If the BESS starts to being unloaded in order to transfer Load to Mains and the LBO EVENT MAINS TRIP (PAGE
945) is closed, the BESS Required P (page 753) will be ramped to the BESS Required P Target (page 753)
according to the ramp. So, the Mains is loaded according to the ramp which maximum is given by the setpoint
Installed Power (page 368) or by the setpoint Nominal power (page 368) if the Installed Power is OFF and the
duration of the ramp is given by the setpoint After Mains Trip Period Ramp (page 534).
Each Grid Code has its priority over the other Grid Codes. The priority of the After Mains Trip Period is given by
the setpoint After Mains Trip Period Priority (page 534).

6.11 Pave
The Pave function controls whether exported power to the grid is inside allowed range. The setpoint Pave
Protection (page 560) != Disabled in order to enable this function. Maximal allowed exported power is adjusted
by setpoint Pave (page 560). Exported power has to be measured in all 3 phases and preferably by using
InteliPro Sync and send via CAN Intercontroller Communication (page 132) to LAI PMOM (PAGE 993). From
LAI PMOM (PAGE 993) and setpoint Pave (page 560) is calculated value Pmom/Pave (page 724) which is used
in application curve P MOM/PAVE MAX (PAGE 863). When Pmom/Pave (page 724) is above the curve P
MOM/PAVE MAX (PAGE 863), LBO PAVE (PAGE 966) is closed and if the value is above allowed limit for period
longer than is allowed by the application curve, the MCB is opened and alarm Hst Pave (page 1111) is
activated.
Note: When Pave Protection (page 560) != Disabled but LAI PMOM (PAGE 993) is not configured or has
invalid value, LBO PAVE FLS (PAGE 966) is closed.
Pave related settings

Setpoints Values
Pave Protection (page 560) Pmom/Pave (page 724)
Pave (page 560) LBOs
Application Curves PAVE (PAGE 966)
P MOM/PAVE MAX (PAGE 863) PAVE FLS (PAGE 966)
LAIs
PMOM (PAGE 993)
6.12 Moving Average

The controller is measuring moving averages of selected values. This means that in specific time window is
measured value stored and average is counted from these data.
After reaching maximal amount of samples, i.e. value has been measured for whole required time, oldest sample
is always replaced with new sample.
6.12.1 10-minutes averages

These values hold average of corresponding physical quantity for last 10 minutes.
BESS P 10 min Avg

Calculation is started with closing BCB breaker and is stopped after the breaker opens. The calculation is stored
in value BESS P 10min Avg (page 674).
IMPORTANT: The value BESS P 10min Avg (page 674) is erased every time BCB breaker opens.
BESS Q 10 min Avg

in value BESS Q 10min Avg (page 675).
IMPORTANT: The value BESS Q 10min Avg (page 675) is erased every time BCB breaker opens.
BESS S 10 min Avg

in value BESS S 10min Avg (page 675).
IMPORTANT: The value BESS S 10min Avg (page 675) is erased every time BCB breaker opens.

Mains Voltage 10 min Avg
Calculation is carried out continuously whole time the controller is powered on. The calculation is made
separately for each phase and depends on setpoint Connection type (page 371).
Ph-Ph connection types uses values Mains Voltage 10min Avg L1-L2 (page 743), Mains Voltage 10min
Avg L2-L3 (page 743) and Mains Voltage 10min Avg L3-L1 (page 743).
Ph-N connection types uses values Mains Voltage 10min Avg L1-N (page 741), Mains Voltage 10min Avg
L2-N (page 741) and Mains Voltage 10min Avg L3-N (page 741).
IMPORTANT: The values mentioned above are erased when the controller is switched off.
6.12.2 1-minute averages

These values hold average of corresponding physical quantity for last 1 minute.
Mains Voltage 1 min Avg

Calculation is carried out continuously whole time the controller is powered on. The calculation is made
separately for each phase and depends on setpoint Connection type (page 371).
Ph-Ph connection types uses values Mains Voltage 1min Avg L1-L2 (page 743), Mains Voltage 1min Avg
L2-L3 (page 744) and Mains Voltage 1min Avg L3-L1 (page 744).
Ph-Pn connection types uses values Mains Voltage 1min Avg L1-N (page 742), Mains Voltage 1min Avg
L2-N (page 742) and Mains Voltage 1min Avg L3-N (page 742).
IMPORTANT: The values mentioned above are erased when the controller is switched off.
6.13 BESS Operation Area

It is possible to adjust the BESS operation area in more details, using application curves. The curves represent
inductive and capacitive halves of the PQ diagram.
Inductive operation area is adjusted by CAPABILITY L (PAGE 864) and if the required BESS Power Factor
(page 667) with BESS Load Character (page 667) = L are behind the limit, LBO BESS CAPABILITY L
LIMIT (PAGE 935) is closed and actual power factor stays on the edge of the curve.
Inductive operation area is adjusted by CAPABILITY C (PAGE 865) and if the required BESS Power Factor
(page 667) with BESS Load Character (page 667) = C are behind the limit, LBO BESS CAPABILITY C
LIMIT (PAGE 935) is closed and actual power factor stays on the edge of the curve.
IMPORTANT: The both Capability C and L curves have to be setup according to the Capability
curves of the worst (weakest) BESS in order to ensure right functionality of the whole system.

7 Communication
7.1 PC 306
7.2 Connection to 3rd party systems 309
7.1 PC
7.1.1 Direct communication 306
7.1.2 Remote communication 307
7.1.1 Direct communication

Computer can be connected to InteliNeo6000 via USB, RS485 or ethernet interface.
Connection via USB

USB A to B cable can be used for communication via USB ports. The InteliNeo6000 is using Human Interface
Devices (HID) protocol which support auto detection of the connected HW. The USB is not industrial interface
and it is not recommended to use it for long term purposes because of interference which can cause lost of
communication.
Image 6.1 Shielded USB type A cable is used
Connection via RS485

On board RS485 connector can be used for communication via RS485 connection. This interface uses
RS485 Modbus Mode (page 386) port of the controller. It is also possible to use RS485-USB convertor.
Image 6.2 Built-in RS485 is used
Image 6.3 RS485 and USB is used

Connection via Ethernet
Ethernet Cat5/Cat6 cable fitted with the RJ45 connector can be used for communication via Ethernet.
Controllers in local network are automatically detected byInteliConfig PC tool. For the direct connection it is
recommended to use Trusted (page 222) interface which is in default configured to port Ethernet 1 (page
19). This communication is more reliable than the USB because it is more robust against interference.
Image 6.4 Ethernet cable is used
Image 6.5 Onboard Ethernet cable is used
6 back to Communication
7.1.2 Remote communication

The InteliNeo6000 can be connected also remotely via built-in ethernet ports. For remote connection the
Untrusted (page 222) interface which is in default configured to port Ethernet 2 (page 19) should be used.
Ethernet LAN connection

Direct IP LAN connection is intended to be used to connect more than one controller at the same time while
controllers are connected to the local are network (LAN). For LAN connections, it is recommended to use
Trusted (page 222) interface which is in default configured to port Ethernet 1. If there is not any device which
would provide DHCP for the LAN the static (manual) IP address must be used.
Image 6.6 Ethernet LAN connection

Setting-up static IP address
This settings is related to Group: ETH Interface 1 - Trusted (page 398), Group: ETH Interface 2 -
Untrusted (page 404) and Group: ETH Interface 3 - Modbus (page 422) .
There are two basic ways how to setup static IP address for remote ethernet connection. The first way is to
switch the Ethernet to manual IP address mode. Adjust the setpoint IP Address Mode to Manual option. In this
moment values for related Ethernet port are immediately changed to the default or previously setup values of
setpoints IP Address, Subnet Mask, Gateway IP, DNS IP, etc. If you are using this Ethernet port for
connection to the controller you will lost the connection.
If this method is used several basic rules should be kept to avoid conflicts with the remaining network
infrastructure:
The static IP used in the controller must be selected in accordance with the local network in which the
controller is connected.
The static IP used in the controller must be excluded from the pool of addresses which is assigned by
DHCP server, which is in charge of the respective local network.
The local infrastructure must generally allow using devices with manually assigned IP addresses.
There must not be any other device using the same static IP address. This can be tested from a computer
connected to the same network using "ping <required_ip_address>" command issued from the command
line. The IP address is not occupied if there is not any response to the ping command.
Note: The list above contains only basic rules. Other specific restrictions/rules may take place depending on
the local network security policy, technology used, topology etc.
The second way is to switch the Ethernet to manual IP address mode. Adjust the setpoint IP Address Mode to
Manual option. In this moment values for related Ethernet port are immediately changed to values given by
the DHCP server for the LAN. If you are using this Ethernet port for connection to the controller you will lost
the connection. It is possible to configure the DHCP server to assign always the same IP address (i.e. static
IP address) to the particular controller according to it's MAC address.
Internet WAN connection

WAN connection is intended to be used to connect the controller using the internet. It is recommended to use
Ethernet 2 (untrusted interface) for remote connection using internet.
Image 6.7 Ethernet WAN connection

Public static IP
If public static IP connection is to be used from the Internet, the IP address, which is entered into the client
computer, must be static and public in scope of the Internet.
If the controller is connected to Internet via a local ethernet network then in most cases port forwarding must
be created from the public IP address of the network gateway to the local IP address of the controller at the
port specified for ComAp protocol. Different port numbers can be used to create multiple port forwarding rules
in the same local network.
7.2 Connection to 3rd party systems

7.2.1 SNMP 309
7.2.2 Modbus-RTU, Modbus/TCP 311
7.2.1 SNMP
SNMP is an UDP-based client-server protocol used for providing data and events into a supervisory system
(building management system). The controller plays the role of a "SNMP Agent" while the supervisory system
plays the role of a "SNMP Manager".
Supported versions – SNMP v1, SNMP v2c and SNMP v3
The SNMP Agent function is to be enabled by the setpoint SNMP Agent (page 416). The setpoints SNMP
RD Community String (page 417) and SNMP WR Community String (page 418) in the same group can
be used to customize the "community strings" for the read and write operations which have function like
"passwords". All requests sent from the SNMP Manager have to contain community string which match with
the community string adjusted in the controller otherwise the controller refuses the operation.
MIB table
The "MIB table" (Management Information Base) is a table which gives to the Manager description of all
objects provided by the Agent.
The MIB table is specific for each controller type and configuration
The MIB table is to be exported from the controller configuration using InteliConfig
Controllers with identical firmware and configuration share also identical MIB table, however if the
configuration and/or firmware is not identical the MIB table is different and must be exported separately for
each controller.
The root node of the MIB table of InteliLite controller is enterprises.comapProjekt.il, which is
1.3.6.1.4.1.28634.14. Under this node there are following sub-nodes :
Notifications group (SMI v2 only) contains definitions of all notification-type objects that the Agent may
send to the Manager.
GroupRdFix contains read-only objects that exist in all controller regardless of the firmware version/type
and configuration.
GroupRdCfg contains read-only objects that depend on the firmware version/type and configuration.
GroupWrFix contains read-write objects that exist in all controller regardless of the firmware version/type
and configuration.

GroupWrCfg contains read-write objects that depend on the firmware version/type and configuration.
GroupW contains write-only objects.
NotificationData group contains objects that are accessible only as bindings of the notification messages.
SMI version
In InteliConfig the MIB table may be exported in two different formats – SMI v1 and SMI v2. The format which
shall be used for export depends on the SNMP Manager and SMI version that it does support.
Typically, SMI v1 is used for SNMP v1 and vice versa, but it is not a rule and SMI v2 may be also used for
SNMP v1.
SNMP reserved objects
Name OID Access Data type Meaning

Writing: command argument
pfActionArgument groupWrFix.24550 read,write Gauge32 Reading: command return
value
pfActionCommand groupW.24551 write Integer32 Command code 1)
pfPassword groupW.24524 write Integer32 Password
1) For list of commands, arguments and description of the procedure of invoking commands see the
description of the MODBUS protocol.
SNMP notifications
Except the request-response communication model, in which the communication is controlled by the
Manager, there are also messages that the Agent sends without any requests. These messages are called
„Notifications“ and inform the Manager about significant events occurred in the Agent.
The controller can send notifications to two different SNMP Managers (two different IP addresses). The
addresses are to be adjusted in the Group: ETH Interface 2 - Untrusted (page 404) by the setpoints SNMP
Traps IP Address 1 (page 418) and SNMP Traps IP Address 2 (page 418). If the Manager address is not
adjusted the particular notification channel is off. The controller will send the notifications in format adjusted
by the setpoint SNMP Trap Format (page 417).
Each notification (kind of event) is identified by an unique identifier (Trap ID in SNMPv1 or Notification OID
in SNMPv2/v3). This unique identifier gives the specific meaning to the notification message, e.g.
Protection 1. level - Fuel Level - alarm activated.
All possible notifications and their identifiers are listed in the MIB table.
The notification message also contains controller name, serial number and textual description of the
event.
Operational events
This events are used for SNMP traps. See the list below:
Start commands
Start button
Remote start

Stop commands
Stop button
Remote stop
Breaker records
Load on Microgrid
Load on Mains
Others
Mains fail
Mains returned
7.2.2 Modbus-RTU, Modbus/TCP

Modbus protocol is used for integration of the controller into a building management system or for remote
monitoring via 3rd party monitoring tools.
Modbus-RTU can be used via ⑮ RS 485 (page 48) . The serial speed for Modbus-RTU communication is
adjusted by the setpoint RS485 Modbus Speed (page 386) and the serial mode is adjusted by the
setpoint RS485 Modbus Mode (page 386). Only 1 client can be connected at once through this type of
connection.
Modbus/TCP (Modbus server) can be used with the Ethernet 1 (page 19) / Ethernet 2 (page 19) /
Ethernet 3 (page 19). Up to 3 clients can be connected simultaneously through each Ethernet port. The
Modbus Server must be activated by the appropriate setpoint Modbus Server related to the respective
Ethernet interface. Timeout after which controller would terminate an inactive connection (when client is
not sending any requests) is set by setpoint ComAp Client Inactivity Timeout (page 421).
Note: Setpoint Modbus Client Inactivity Timeout (page 425) is common for both Ethernet 1 (page
19), Ethernet 2 (page 19) and Ethernet 3 (page 19) interfaces.
DO NOT READ ALARM LIST FROM MORE THAN 1 CLIENT! LOSS OF INFORMATION MAY OCCUR.
Modbus, Modbus/TCP protocol can be used simultaneously with direct Ethernet connection and the SNMP
agent.
Note: Recommended timeout for Modbus client is 300 ms.
IMPORTANT: Do not use setpoints for real-time control from super-ordinate systems. Frequent
repeated writing of setpoints would cause the history file getting overwritten and losing
important records.
IMPORTANT: The InteliNeo6000 is using same MAC address for all Ethernet ports so it is not
possible to use more than one Ethernet port in the same network. If you connect for example
Ethernet 1 and 2 to the same network the communication will breakdown.
In the image below you can see the topology using all 3 Ethernet ports. The ETH1 is used for Modbus Server,
remote connection using the internet (WAN). The ETH3 is used for Modbus Client which is connected to the
LAN.
In the image below you can see the topology using all 3 Ethernet ports with one Modbus Client. The ETH1 is
used for connection of displays (IV5.2) or it can be also used for remote LAN connection. The ETH2 is used

for remote connection using the internet (WAN). The ETH3 is used for Modbus Server and Client which are
connected to the LAN with Modbus Devices.
Image 6.8 Advanced Ethernet Topology With One Modbus Client
In the image below you can see the topology using all 3 Ethernet ports with multiple Modbus Clients (CU 1 is
the first level client, CU 2 and CU 3 are second level clients). The ETH1 is used for Modbus Server,
remote connection using the internet (WAN). The ETH3 is used for Modbus Clients which are connected
between CU 1 and other CUs, and between other CUs and Modbus Devices.

Image 6.9 Advanced Ethernet Topology With Multiple Modbus Clients
Address space
The object address space is separated into several areas as described in the table below. The actual
mapping of specific controller data objects to specific Modbus addresses, which depends on configuration,
can be exported into a text file from the appropriate controller archive using InteliConfig. There are several
special registers with fixed meaning (reserved registers) which are listed in a separate table in this chapter.
Modbus MODICON object

Meaning Access Modbus function
address type
0000 .. Binary
Read only Discrete Inputs Read: 01, 02
0999 objects
1000 ..
Values Read only Input Registers Read: 03, 04
2999
3000 .. Read: 03, 04
Setpoints Read/Write Holding Registers
3999 Write: 06, 16
4200 .. Reserved Read/Write, depends on Input Registers Read: 03, 04
7167 registers each specific register Holding Registers Write: 06, 16

Configurable part of the map
The contents of the configurable part of the map is specified in the configuration table. It can be changed by
the customer as well as exported in a human-readable format using the configuration tool.
Discrete inputs
The discrete inputs are read-only objects located in the address range 0-999. The source ComAp objects for
discrete inputs can be:
Single bit of any value of any binary type.
Protection (e.g. 2nd-level protection of the state "xyz"). The input is high if the protection is active
regardless of if it is configured or not.
Input registers
The input registers are read-only numeric values located in the address range 1000-2999. The source
ComAp objects can be:
Any controller value of any data type. The mapping of the particular data type into registers is described in
Mapping data types to registers (page 314).
Holding registers
The holding registers are read-write numeric values located in the address range 3000-3999. The source
ComAp objects can be:
Any controller setpoint of a primitive data type. The mapping of the particular data type into registers is
described in Mapping data types to registers (page 314).
Note: Setpoint must be configured with access level 0 to allow writing it via MODBUS.
Mapping data types to registers

As there are multiple data types in the controller but only one data type in MODBUS (the register, which is 2
byte long), a mapping table is necessary to compose and decompose the MODBUS messages correctly.
Number of
Data type Meaning Data maping
registers
MSB = sign extension
Integer8 1-byte signed integer 1
LSB = value
MSB = 0
Unsigned8 1-byte unsigned integer 1
LSB = value
MSB = value, MSB
LSB = value, LSB
MSB = value, MSB
Unsigned16 2-byte unsigned integer 1
LSB = value, LSB
MSB1 = value, byte 3 (MSB)
LSB1 = value, byte 2
MSB2 = value, byte 1
LSB2 = value, byte 0 (LSB)
Unsigned32 4-byte unsigned integer 2 MSB1 = value, byte 3 (MSB)

Number of
registers
LSB1 = value, byte 2
MSB2 = value, byte 1
LSB2 = value, byte 0 (LSB)
MSB = 0
Binary8 8-bit binary value 1
LSB = value, bits 0-7
MSB = value, bits 8-15
LSB = value, bits 0-7
MSB1 = value, bits 24-31
LSB1 = value, bits 16-23
MSB2 = value, bits 8-15
LSB2 = value, bits 0-7
MSB = 0
Char 1-byte ASCII character 1
LSB = ASCII value of the character
MSB = 0
StrList Index into a list of strings 1
LSB = index into the list
MSB1 = ASCII value of the 1. character
LSB1 = ASCII value of the 2. character
Zero-terminated string of
ShortStr 8 MSB2 = ASCII value of the 3. character
max 15 ASCII characters.
…
MSB1 = ASCII value of the 1. character
Zero-terminated string of
LongStr 16 MSB2 = ASCII value of the 3. character
max 31 ASCII characters.
…
MSB1 = BCD (dd)
LSB1 = BCD (mm)
Date Date (dd-mm-yy) 2
MSB2 = BCD (yy)
LSB2 = 0
MSB1 = BCD (hh)
LSB1 = BCD (mm)
Time Time (hh-mm-ss) 2
MSB2 = BCD (ss)
LSB2 = 0
MSB1 = reserved for future use
LSB1 = reserved for future use
Alarm An item of the Alarmlist 27 MSB2 = Alarm level *)
LSB2 = Alarm status **)
MSB3 = alarm string ***)

Number of
registers
LSB3 = alarm string
MSB4 = alarm string
LSB5 = alarm string
…
*) 1 .. level 1 (yellow), 2 .. level 2 (red)
**) Bit0 – alarm is active, Bit1 – alarm is confirmed
***) String encoding is UTF-8
Error codes (exception codes)

Exception code is returned by the controller (server) if the query sent from the client could not be completed
successfuly.
The controller responds with the error codes in as follows:
01 – Ilegal function is returned if an incompatible type of operation is applied for a specific object, e.g. if
function 03 is applied to a binary object.
02 – illegal address is returned if the client tries to perform an operation with a object address that is not
related to any existing object or that is located inside an object which is composed by multiple addresses
(registers).
04 – device error is returned in all other errorneous situations. More detailed specification of the problem
can be consequently obtained by reading the registers 4205 – 4206.
Reserved registers
There are several registers with specific meaning. These registers are available in all controllers regardless of
the configuration.
Register Number of
Access Data type Meaning
addresses registers
4200 - 4201 2 read/write Time RTC Time in BCD code
4202 - 4203 2 read/write Date RTC Date in BCD code
Index of the language that is used for
4204 1 read/write Unsigned8 text data provided by Modbus (e.g.
alarmlist messages).
Last application error. To be read after
the device returns the exception code
4205 - 4206 2 read Unsigned32
04. It contains specific information about
the error.
Writing:command argument
4207 - 4208 2 read/write Unsigned32
Reading: command return value
4209 1 write Unsigned16 Command code
4010 1 - - Not implemented
4211 1 write Unsigned16 Password
4212 - 4213 2 read Unsigned32 Communication status

Register Number of
addresses registers
Reading: Number of items in the
Alarmlist
4214 1 read/write Unsigned8
Writing: Required record format, 0 = text
(default), 1 = binary
4215 - 4241 27 read Alarm 1. record in alarm list
Remote start/Stop: Suplements the set
of starting requests in AUTO mode (e.g.
Remote Start/Stop. Set the coil to log1 to
4700 1 write Bool
start the BESS, set the coil to log0 to
stop the BESS. There are no conditions
in relation to user access settings.
5000 1 read/write Int16 RemoteControl2B 1 (page 829)
5100 - 5101 2 read/write Int32 RemoteControl4B 1 (page 831)
5200 1 read/write Binary16 RemoteControlBin (page 832)

Alarmlist reading
An item of the Alarmlist has the following structure:
Byte Value Meaning

MSB 1 0 Always zero for reverse compatibility
0 ComAp Text
1 ComAp Binary
LSB 1
2 ECU Text
3 ECU Binary
0 Undefined
1 Level 1
MSB 2
2 Level 2
3 Sensor fail
0 Inactive
1 Active, Confirmed
LSB 2
2 Inactive, Unconfirmed
3 Active, Unconfirmed
If Alarm format = ComAp Text or ECU Text:
MSB 3 alarm string

LSB 3 alarm string
... ... ...
MSB 27 alarm string
LSB 27 alarm string
If Alarm format = ECU Binary:
MSB 3 FC[3]
error ID (SPN) high word
LSB 3 FC[2]
MSB 4 FC[1]
error ID (SPN) low word
LSB 4 FC[0]
MSB 5 0
LSB 5 FMI failure mode identifier
MSB 6 0
LSB 6 OC occurence
MSB 7 0
LSB 7 SRC_ADDR ECU address
MSB 8 0
LSB 8 SRC_IDX ECU unit index
If Alarm format = ComAp Binary:

Reason Text IDX*
MSB 3 REASON_TEXT_IDX[1]
*configuration-dependent, can be found in
exported data from InteliConfig (CFG
LSB 3 REASON_TEXT_IDX[0]
Image), table "AlarmReasonNames"
List of commands and arguments

IMPORTANT: Only commands configured with access level 0 can be invoked via Modbus.
"Commands" are used to invoke a specific action in the controller via the communication channel. The list of
available actions is in the table below. The general procedure of writing a command via Modbus is as follows:
1. Write the command argument into the registers 44208-44209 (register addresses 4207-4208). Use
function 16.
2. Write the command code into the register 44210 (register address 4209). Use function 6.
3. (Optional) Read the command return value from the registers 44208-44209 (register addresses 4207-
4208). Use function 3.
4. If the command was executed the return value is as listed in the table. If the command was accepted but
there was an error during execution the return value indicates the reason:
a. 0x00000001 – invalid argument
b. 0x00000002 – command refused (e.g. controller not in MAN, breaker can not be closed in the
specific situation etc.)
Command code Action Argument

BESS start* 0x01FE 0000
BESS cmd BESS stop* 0x02FD 0000
0x01 Fault reset* 0x08F7 0000
Horn reset* 0x04FB 0000
BCB toggle* 0x11EE 0000
Breaker cmd
BCB on 0x11EF 0000
0x02
BCB off 0x11F0 0000
MCB toggle* 0x12ED 0000
Breaker cmd
MCB on 0x12EE 0000
0x02
MCB off 0x12EF 0000
OFF Mode 0x0000 0000
Mode cmd
MAN Mode 0x0001 0000
0x03
AUTO Mode 0x0003 0000
Access lock Remove Access lock 0x0010 0000
0x197 Set Access lock 0x0020 0000

User Button 1: Pulse 0x000A 0000
User Button 1: ON/OFF 0x000B 0000
User Button 1: ON 0x000C 0000
User Button 1: OFF 0x000D 0000
User Button 2: Pulse 0x0014 0000
User Button 2: ON/OFF 0x0015 0000
User Button 2: ON 0x0016 0000
User Button 2: OFF 0x0017 0000
User Button 3: Pulse 0x001E 0000
User Button 3: ON/OFF 0x001F 0000
User Button 4: ON 0x002A 0000
User Buttons 1 .. 8 User Button 4: OFF 0x002B 0000
0x0047 User Button 5: Pulse 0x0032 0000
User Button 6: Pulse 0x003C 0000
User Butto 6: ON/OFF 0x003D 0000
User Button 6: ON 0x003E 0000
User Button 6: OFF 0x003F 0000

User Button 9: Pulse 0x005A 0000
User Button 9: ON/OFF 0x005B 0000
User Button 9: ON 0x005C 0000
User Button 9: OFF 0x005D 0000
User Buttons 9 .. 16 User Button 12: OFF 0x007B 0000
0x0048 User Button 13: Pulse 0x0082 0000
User Button 16: Pulse 0x00A0 0000
User Button 16: ON/OFF 0x00A1 0000
User Button 16: ON 0x00A2 0000
User Button 16: OFF 0x00A3 0000

User Button 17: Pulse 0x00AA 0000
User Button 17: ON/OFF 0x00AB 0000
User Button 17: ON 0x00AC 0000
User Button 17: OFF 0x00AD 0000
User Button 18: Pulse 0x00B4 0000
User Button 18: ON/OFF 0x00B5 0000
User Button 18: ON 0x00B6 0000
User Button 18: OFF 0x00B7 0000
User Button 19: Pulse 0x00BE 0000
User Button 19: ON/OFF 0x00BF 0000
User Button 19: ON 0x00C0 0000
User Button 19: OFF 0x00C1 0000
User Button 20: Pulse 0x00C8 0000
User Button 20: ON/OFF 0x00C9 0000
User Button 20: ON 0x00CA 0000
User Buttons 17 .. 24 User Button 20: OFF 0x00CB 0000
0x00A8 User Button 21: Pulse 0x00D2 0000
User Button 21: ON/OFF 0x00D3 0000
User Button 21: ON 0x00D4 0000
User Button 21: OFF 0x00D5 0000
User Button 22: Pulse 0x00DC 0000
User Butto 22: ON/OFF 0x00DD 0000
User Button 22: ON 0x00DE 0000
User Button 22: OFF 0x00DF 0000
User Button 23: Pulse 0x00E6 0000
User Button 23: ON/OFF 0x00E7 0000
User Button 23: ON 0x00E8 0000
User Button 23: OFF 0x00E9 0000
User Button 24: Pulse 0x00F0 0000
User Button 24: ON/OFF 0x00F1 0000
User Button 24: ON 0x00F2 0000
User Button 24: OFF 0x00F3 0000

User Button 25 Pulse 0x00FA 0000
User Button 25 ON/OFF 0x00FB 0000
User Button 25 ON 0x00FC 0000
User Button 25 OFF 0x00FD 0000
Usser Buttons 25 .. 32 User Button 28: OFF 0x011B 0000
0x00A9 User Button 29: Pulse 0x0122 0000
* This action is an equivalent of pressing the front panel button

Modbus RTU examples
Reading of Battery voltage
Export table of values from InteliConfig
Table: Values
Allowed MODBUS functions: 03, 04
Register
Com.Obj. Name Dimension Type Len Dec Min Max Group
(s)
BatteryVoltag Controller
01036 8213 V Integer 2 1 0 400
e I/O
Request: (Numbers in Hex)

01 03 04 1D 00 01 15 3C
Register
address
Controller address Modbus function Number of registers CRC
041Dhex
1053dec
Response: (Numbers in Hex)

01 03 02 00 F0 B8 00
Length of data Data
Controller address Modbus function 02hex 00F0hex CRC
2 bytes read 240dec
We read value 240 from register 01036. From table of modbus registers we get dimension of read value and
"Dec". Dec=1 means shift one decimal place to the right. So battery voltage is 24.0 V.

Reading Nominal power
Export table of values from InteliConfig
Table: Values
Register
(s)
Nominal Basic
01228 9018 kW Integer 2 0 0 32767
Power Settings

01 03 04 CC 00 01 45 05
Register address
Controller address Modbus function 04CChex Number of registers CRC
1228dec

01 03 02 00 C8 B9 D2
Length of data Data
Controller address Modbus function 02hex 00C8hex CRC
2 bytes read 200dec
Read nominal power is 200 kW.

Reading all binary inputs as modbus register
Table: Values
Register
(s)
Binary Controller
01068 8235 Binary#2 2 0 - -
Inputs I/O

01 03 04 2C 00 01 44 F3
Register address
Controller address Modbus function 042Chex Number of registers CRC
1068dec

01 03 02 00 12 38 49
Length of data Data
Controller
Modbus function 02hex 0012hex CRC
address
2 bytes read 00010010bin
Binary inputs is 00010010. It means Binary input 2 and binary input 5 are active.
Note: You can use Modbus function 4 instead of 3, rest of data remain same (CRC differs).

Reading specific binary inputs
Table: Binaries
Addresses Source Name of Bit Name
C.O.#
Modbus Addr. = Value Value Bit # Activated by protection Group
State #
Prot. Addr. = State Name of State (s):
00000 Value 8235 Binary Inputs 0 BCB Feedback Controller I/O
00001 Value 8235 Binary Inputs 1 MCB Controller I/O
00002 Value 8235 Binary Inputs 2 BESS Ready To Load Controller I/O
We will read state of BCB Feedback binary input.

01 01 00 01 00 01 AC 0A
Register
address
Controller address Modbus function Number of registers CRC
0001hex
0001dec

01 01 01 01 90 48
Length of data Data
Controller address Modbus function 01hex 01hex CRC
1 byte read active
The readed data is 01, it means this binary input is active.

Note: You can use Modbus function 2 instead of 1, rest of data remains same (CRC differs).

Starting the BESS
User with access level 0 must have full access for BESS Cmd otherwise the command will not be invoked.
Table Reserved registers (page 316)

Register Number of
addresses registers
Writing:command argument
4207 - 4208 2 read/write Unsigned32 Reading: command return
value
4209 1 write Unsigned16 Command code
Table List of commands and arguments (page 319)

Action Command code Argument Return value
BESS start 0x01 0x01FE0000 0x000001FF
BESS stop 0x01 0x02FD0000 0x000002FE
Request 1/2: (Numbers in Hex)

01 10 10 6F 00 03 06
Modbus function Register address
Controller address Number of registers Data length in bytes
10hex = 16dec 106Fhex = 4207dec
Request 2/2: (Numbers in Hex)

01 FE 00 00 00 01 68 0B
Argument Command code CRC
Note: Command and argument may be written as one "packet" (function 16) or you can split it and write
argument (function 16) and after that write command code (function 6).

Nominal Power – writing
Table: Setpoints
Allowed MODBUS functions: 03, 04, 06, 16
Register
(s)
Nominal Basic
03008 8276 kW Unsigned 2 0 1 5000
Power Settings

01 06 0B C0 00 64 8A 39
Data
Register address
Controller address Modbus function 0064hex = CRC
0BC0hex = 3008dec
100dec

01 06 0B C0 00 00 8B D2
Register address
Controller address Modbus function Allways zero CRC
0BC0hex = 3008dec
Writen setpoint nominal power is 100 kW.

CRC calculation
The check field allows the receiver to check the validity of the message. The check field value is the Cyclical
16 15 2
Redundancy Check (CRC) based on the polynomial x +x +x +1. CRC is counted from all message bytes
preceding the check field.
Online CRC calculator: http://www.lammertbies.nl/comm/info/crc-calculation.html Use CRC-16 (Modbus)
Write LSB first.
For writing nominal power 100 kW the CRC is calculated from this data: 01060BC00064hex
6 back to Connection to 3rd party systems

8 Technical data
Power supply
Power supply range 8-36 V DC
Power consumption 16 W
RTC battery Replaceable, type CR1632 3V
Fusing power 8A
Consumption 2.5 A Controller + 10 x 0.5 A BOUTs @ 8 V
Fusing E-STOP 1A
Max. Heat Dissipation 16 W
Operating conditions
Operating temperature -40 °C to +70 °C
Storage temperature -40 ˚C to +80 ˚C
25/55°C, 48hours,95 % non-condensing
Operating humidity (norm 60068-2-30)
(EN 60068-2-30)
Protection degree IP20
5-25 Hz, ± 1.6 mm
Vibration
25-100 Hz, a = 4 g
2
Shocks a = 500 m/s
Surrounding air temperature rating 70 °C.
Suitable for pollution degree 2.
AC Current measurement
3ph BESS current
Measurement inputs
1ph Mains current (Auxiliary current)
Measurement range 1A/5A
Maximum continuous current 2 A / 10 A
Allowed overload 18 A for 15 sec.
Accuracy ±3 mA / ±15 mA for 0.0 to 0.4 A / 0.0 to 2.0 A0.75 % of value for 0.4 to 1.0 A / 2.0 to 5.0 A
Frequency range 40-70 Hz (accuracy 0.002 %)
Input impedance 0.68 MΩ ph-ph , 0.34 MΩ ph-n
AC Voltage measurement
3ph-n BESS voltage
Measurement inputs
3ph-n Mains voltage
115 V ph-N / 200 V ph-ph
suitable also for VTs output
Measurement range
231 V ph-N / 400 V ph-ph
UL, cUL: 346 V ph-N / 600 V ph-ph
Linear measurement and protection
433 V ph-N / 750 V ph-ph
range (maximal voltage)
Accuracy 0.25 %
Frequency range 40-70 Hz (accuracy 0.002 %)
Input impedance 0.72 MΩ ph-ph , 0.36 MΩ ph-n
Measurement category CAT III, overvoltage category III
E-Stop
Dedicated terminal for safe Emergency Stop input.
Physically disconnects BO 1 & BO 2 from power supply.
Binary inputs
Number 12, non-isolated
Close/Open 0-2 V DC close contact
indication 6-36 V DC open contact
Configurable Pull-up / Pull-down
Pulse input Bin 9 and 10 max. 50 Hz

Binary outputs
Number 12, non-isolated
Max. current 0.5 A
Switching to Positive supply terminal
Analog inputs
Number 4, switchable (R/U/I)
Range R = 0-10000 Ω; U = 0-10 V; I = 0-20 mA
R: 2 % from value for 0-250 Ω
R: 4% from value for 250-2500 Ω
Accuracy R: 6 % from value for 5000-10000 Ω
U: 1% from value ±100 mV
I: 1% from value ±200 uA
Analog output 1
Protection Reinforced isolation
Type Switchable: U ±10 V, I ±20 mA, PWM: 0 V/5 V
U: 1 % from value ±100 mV
Accuracy
I: 1 % from value ±200 uA
Analog output 2
Protection Basic isolation
Type Switchable: U ±10 V, I ±20 mA, PWM: 0 V/5 V
U: 1 % from value ±100 mV
Accuracy
I: 1 % from value ±200 uA
Communications
USB Device Basic isolation, USB type B
RS 485 Basic isolation
ETH1
ETH2 10/100 Mbit
ETH3
CAN 1A
CAN 2A Basic isolation, 1000/250/50 kbps
CAN 1B , nominal impedance 120 Ω
CAN 2B
Weight
Controller 750 g
Package 920 g
Controller handles 300 million records into the History, which represents roughly 1 record per second during 9,5 years. Shall be the History recording faster,
the controller lifetime will become smaller.

9 Appendix
9.1 Controller objects 332
9.2 Alarms 1080
9.3 Modules 1184
9.1 Controller objects

9.1.1 List of controller objects types
9.1.3 Setpoints 333
9.1.4 Values 652
9.1.5 Application Curves 857
9.1.6 Logical binary inputs 876
9.1.7 Logical binary outputs 920
9.1.8 Logical analog inputs 980
9.1.9 Fixed Protection States 1016
9.1.10 User Protection States 1024
9.1.11 PLC 1027

9.1.2 Renameable controller objects
It is possible to rename some controller objects in InteliConfig under Controller Configuration -> Others ->
User texts tab. The User texts include communication objects, group names, subgroup names, alarms, etc.
The user can name those objects according his needs.
9.1.3 Setpoints
What setpoints are:
Setpoints are analog, binary or special data objects which are used for adjusting the controller to the specific
environment. Setpoints are organized into groups according to their meaning. Setpoints can be adjusted from
the controller front panel, PC, MODBUS, etc.
All setpoints can be protected by a password against unauthorized changes. Password protection can be
assigned to the setpoints during the configuration procedure.
IMPORTANT: Do not write setpoints repeatedly (e.g. power control from a PLC by repeated
writing of baseload setpoint via Modbus). The setpoints are stored in FRAM memory, which is
14
designed to withstand up to 10 read/write cycles without risk of damage or data loss, but it may
become damaged, when the allowed number of reading/writing cycles is exceeded.
For full list of setpoints go to the chapter List of setpoints (page 335).
List of group of setpoints

Group: Process Control 344
Group: Basic settings 366
Group: Communication Settings 385
Group: Ethernet Port Configuration 395
Group: ETH Interface 1 - Trusted 398

Group: ETH Interface 2 - Untrusted 404
Group: ETH Interface 3 - Modbus 422
Group: BESS settings 425
Group: BESS Protections 437
Group: PV Settings 451
Group: WT Settings 454
Group: Frequency/Load Control 457
Group: Voltage/PF Control 470
Group: Synchronization 476
Group: Power Management 480
Group: Mains Settings 514
Group: Grid Codes 527
Group: BESS Protections 561
Group: Load Shedding 592
Group: User Buttons 595
Group: Scheduler 611
Group: Maintenance Timers 640
Group: Geo-Fencing 646

List of setpoints
Group: Process Control 344 PVCB Control Mode 363

Subgroup: Application Selector 344 Delay Between Closing Attempts 363
Default Application Select 344 Subgroup: Controller Redundancy 364
Subgroup: Load Control 345 Hot Swap Redundancy 364
Load Control PTM Mode 345 Subgroup: System Variability 365
Load Request Source 346 BESS 365
#System Load Control PTM 347 PV 365
Import Load 348 WT 365
#System Baseload 348 Mains 366
Subgroup: PF/Q Control 349 Gensets 366
PF/Q Control PTM Mode 349 Group: Basic settings 366
PF/Q Request Source 350 Subgroup: Name 366
PF/Q Regulation Type 351 Controller Name 367
#System PF Control PTM 351 Subgroup: Power settings 367
Base Power Factor 352 Samax 367
Import Power Factor 352 Nominal power 368
#System Power Factor 353 Installed Power 368
Base Q 353 Subgroup: Current settings 369
Import Q 354 Nominal Current 369
#System Base Q 354 BESS CT Ratio Prim 369
Subgroup: Neutral Contactor 355 BESS CT Ratio Sec 370
#Neutral Contactor Control 355 Mains/Bus CT Ratio Prim / EFC 370
Subgroup: Process Limitation 355 Mains/Bus CT Ratio Sec / EFC 371
CB Control In MAN Mode 355 3Ph CT Location 371
Subgroup: Mains Import Measurement 357 Subgroup: Voltage settings 371
Mains Measurement P 357 Connection type 371
Mains Measurement Q 358 Evaluated Voltage Protections 372
Subgroup: Peak Shaving 358 BESS Nominal Voltage Ph-N 373
Peak Shaving 358 BESS Nominal Voltage Ph-Ph 373
Peak Shaving Start Level 359 Mains/Bus Nominal Voltage Ph-N 373
Peak Shaving Stop Level 359 Mains/Bus Nominal Voltage Ph-Ph 374
Peak Shaving Start/Stop Delay 360 BESS VT Ratio 374
Subgroup: Breaker Control 360 BESS Voltage Input Range Select 374
MCB Logic 360 Bus 375
MCB Control Mode 361 Bus Voltage Input Range 375
BCB Control Mode 362 Bus Dead Level 376

Subgroup: Phase Rotation 377 Subgroup: SD Card Settings 393
Phase Rotation 377 SD Card File System 393
Subgroup: Frequency settings 377 Long Term History 393
Nominal Frequency 377 Subgroup: CAN1 ECU/IO Modules Split 394
Subgroup: Controller settings 378 CAN1 ECU/IOModules Split 394
Controller Mode 378 Group: Ethernet Port Configuration 395
Power On Mode 378 Ethernet port 1 395
Fault Reset To Manual 379 Ethernet port 2 396
Horn Timeout 379 Ethernet port 3 397
Fail Safe Binary State 380 Group: ETH Interface 1 - Trusted 398
Run Hours Source 380 Subgroup: TCP/IP Settings 398
SW Key 381 IP Address Mode 398
User Logging Record 381 IP Address 399
Fuel Genset Consumption 381 Subnet Mask 399
Subgroup: 382 Gateway IP 400
Battery Undervoltage 382 IP Firewall 400
Battery Overvoltage 382 Subgroup: SNMP Settings 401
Battery <> Voltage Delay 382 SNMP Privacy Protocol 401
Subgroup: Pulse counters 383 SNMP Authentication Protocol 401
Conversion Coeff. Fast Pulse 1 383 SNMP Security Level 401
Conversion Coeff. Fast Pulse 2 383 Subgroup: Modbus Server Settings 402
Conversion Coefficient Pulse 1 384 Modbus Server 402
Conversion Coefficient Pulse 2 384 Modbus Client Inactivity Timeout 402
Group: Communication Settings 385 Subgroup: ComAp Client Settings 403

Subgroup: Controller Address 385 Direct Connection Port 403
CAN Controller Address 385 ComAp Client Inactivity Timeout 403
Terminal Comm Address 385 Group: ETH Interface 2 - Untrusted 404
Subgroup: RS485 Settings 386 Subgroup: TCP/IP Settings 404
RS485 Modbus Speed 386 IP Address Mode 404
RS485 Modbus Mode 386 IP Address 405
Subgroup: History Settings 387 Subnet Mask 405
LB/UART Log 387 Gateway IP 406
Subgroup: Intercontroller Settings 388 IP Firewall 406
CAN Intercontroller Comm Redund 388 DNS Mode 407
CAN Intercontroller Comm Mode 389 DNS IP Address 1 407
CAN Intercontroller Empty Check 390 DNS IP Address 2 408
Access Lock Mode 391 Subgroup: AirGate Settings 408
Automatic Access Lock Release 392 AirGate Connection 408
User sessions limit 392 AirGate Address 409

AirGate Port 409

Subgroup: Messages Settings 410 Gateway IP 424
Event Message 410 Subgroup: Modbus Settings 425
Wrn Message 410 Modbus Type 425
Sd Message 411 Modbus Client Inactivity Timeout 425
E-mail Language 411 Group: BESS settings 425
Time Zone 412 Subgroup: Inverter Precharge Settings 425
Subgroup: E-mail Settings 412 BESS Precharge Type 426
E-mail Address 1 412 BESSReady to Load TO 426
E-mail Address 2 413 Subgroup: BESS P Control 427
E-mail Address 3 413 BESS P request source 427
E-mail Address 4 413 BESS Charge Power 427
SMTP User Name 414 BESS Discharge Power 428
SMTP User Password 414 Gen P Min 428
SMTP Server Address 415 Subgroup: BESS Q Control 429
SMTP Sender Address 415 BESS Q request source 429
SMTP Encryption Type 416 Gensets PF Required 429
Subgroup: SNMP Settings 416 Subgroup: SOC Control 430
SNMP Agent 416 SOC High Target 430
SNMP Trap Format 417 SOC High Hysteresis 430
SNMP RD Community String 417 SOC Low Target 431
SNMP WR Community String 418 SOC Low Hysteresis 431
SNMP Traps IP Address 1 418 Subgroup: Battery Cycles 432
SNMP Traps IP Address 2 418 Max Battery Cycles Per Day 432
SNMP Engine User Name 419 Subgroup: Starting Timers 432
Subgroup: Modbus Server Settings 419 Minimal Stabilization Time 432
Modbus Server 419 Maximal Stabilization Time 433
Modbus Client Inactivity Timeout 420 Run Only Block Delay 1 434
Subgroup: ComAp Client Settings 420 Run Only Block Delay 2 435
Direct Connection 420 Run Only Block Delay 3 436
Direct Connection Port 421 Subgroup: Stopping Timers 436
ComAp Client Inactivity Timeout 421 Stop Time 436
Subgroup: NTP Settings 422 Subgroup: Power Switch 437
NTP Clock Synchronization 422 Power Switch On 437
NTP Server 422 Power Switch Off 437
Group: ETH Interface 3 - Modbus 422 Group: BESS Protections 437

Subgroup: TCP/IP Settings 422 Subgroup: Overload Protection 437
IP Address Mode 422 2POverload Start Evaluation Level 437
IP Address 423 2POverload Start Evaluation Delay 438
Subnet Mask 423 Subgroup: Current Protection 439

Short Circuit 439 PV Calib. Offset 2 453
Short Circuit Delay 440 PV Calib. Offset 3 454
IDMT BESS >A Delay 440 PV Calib. Offset 4 454
BESS Current Unbalance 441 Group: WT Settings 454
BESS Current Unbalance Delay 441 Subgroup: PF Control 454
Subgroup: Voltage Protection 442 WT Power Factor Request 454
BESS >V 442 Group: Curtailment 455
BESS >V Delay 443 Subgroup: Curtailment 455
BESS >>V 443 Curtailment 455
BESS >>V Delay 444 Gain 455
BESS <V 444 Int 456
BESS <V Delay 445 Gen P Min 456
BESS V Unbalance 445 Subgroup: PW/WT Ramp 456
BESS V Unbalance Delay 445 PV/WT Ramp Up 456
Subgroup: Frequency Protection 446 PV/WT Ramp Down 457
BESS >f 446 Group: Frequency/Load Control 457
BESS >f Delay 446 Subgroup: Frequency Control 457
BESS <f 447 Frequency Regulator Character 457
BESS <f Delay 447 Frequency Governor Bias 458
Subgroup: Bus Meas Error 448 Frequency Governor Low Limit 458
Bus Meas Error 448 Frequency Governor High Limit 458
Subgroup: Earth Fault Current Protection 448 Tau Frequency Governor Actuator 459
IDMT Earth Fault Current Sd 448 BESS Frequency Droop Slope 459
IDMT Earth Fault Current Delay 449 Subgroup: Regulation Loops 460
Subgroup: SOC Protection 449 Frequency Regulation Loop 460
BESS <f Delay 449 Frequency Gain 460
SOC High Alarm 450 Frequency Int 461
SOC Critical Low 450 Angle Gain 461
SOC Critical High 451 Load Gain 462

Load Int 462
Group: PV Settings 451
Subgroup: PF Control 451 Load Sharing Gain 463
PV Power Factor Request 451 Load Sharing Int 463
Subgroup: PV Areas 452 Subgroup: Load Transfer 464
PV Array Area 1 452 Close Transfer Max Duration 464
PV Array Area 2 452 Open Transfer Min Break 464
PV Array Area 3 452 Transfer Mains To BESS 465
PV Array Area 4 453 Transfer BESS To Mains 466
Subgroup: PV Calibration Offset 453 Generator Unload BCB Open Level 467
PV Calib. Offset 1 453 Mains Unload MCB Open Window 467

Load Ramp 468

Ramp Start Level 469 Dynamic Spinning Reserve 486
Soft Unload Ramp 470 Solar Coverage Ratio 487
Group: Voltage/PF Control 470 Wind Coverage Ratio 487
Subgroup: Voltage Control 470 Subgroup: Load Reserve Set 1 488
Voltage Regulator Character 470 #Starting Load Reserve 1 488
Voltage Regulator Bias 471 #Stopping Load Reserve 1 489
Voltage Regulator Low Limit 471 #Starting Rel Load Reserve 1 490
Voltage Regulator High Limit 471 #Stopping Rel Load Reserve 1 490
Tau Voltage Regulator Actuator 472 Subgroup: Load Reserve Set 2 491
BESS Voltage Droop Slope 472 #Starting Load Reserve 2 491
Subgroup: Regulation Loops 473 #Stopping Load Reserve 2 492
Voltage Gain 473 #Starting Rel Load Reserve 2 493
Voltage Int 473 #Stopping Rel Load Reserve 2 493
PF Gain 474 Subgroup: Load Reserve Set 3 494
PF Int 474 #Starting Load Reserve 3 494
VAr Sharing Gain 475 #Stopping Load Reserve 3 495
VAr Sharing Int 475 #Starting Rel Load Reserve 3 496
Group: Synchronization 476 #Stopping Rel Load Reserve 3 496
Subgroup: Synchronization 476 Subgroup: Load Reserve Set 4 497
Synchronization Type 476 #Starting Load Reserve 4 497
Synchronization Timeout 477 #Stopping Load Reserve 4 498
Voltage Window 477 #Starting Rel Load Reserve 4 499
BESS to Mains/Bus Phase Shift 477 #Stopping Rel Load Reserve 4 499
Phase Window 478 Subgroup: Minimal Running Power 500
Dwell Time 478 #Min Run Power 500
Slip Frequency 479 #Min Run Power 2 500
Slip Frequency Window 479 #Min Run Power 3 501
BCB Latency 479 Subgroup: Start/Stop Timing 501
MCB Latency 480 #Next Engine Start Delay 501
Group: Power Management 480 #Next Engine Stop Delay 502
Subgroup: Power Management Control 480 Subgroup: Slow Stop Protection 502
Power Management 480 #Slow Stop Delay 502
Power Management Delay 481 Slow Stop Stay In Load Sharing 503
#Power Management Mode 482 Subgroup: Over Load Next Start Protection 504
Priority 483 #Overload Next Start Protection 504
#Priority Auto Swap 484 #Overload Next Start Level 504
#System Start Delay 485 #Overload Next Start Delay 505
#System Stop Delay 485 Subgroup: Run Hours Equalization 505
Subgroup: Dynamic Spinning Reserve 486 Run Hours Base 505
Dynamic Spinning Reserve Source 486

#Run Hours Max Difference 506 Mains >f 522
Subgroup: Efficient Mode 506 Mains >f Delay 522
#Power Band Change Up Delay 506 Mains >f Hys 522
#Power Band Change Down Delay 507 Mains >>f 523
Subgroup: Group Settings 507 Mains >>f Delay 523
Control Group 507 Mains >>f Hys 523
Group Link L 508 Mains <f 524
Group Link R 508 Mains <f Delay 524
Group: Loss of Mains Protections 509 Mains <f Hys 524
Subgroup: Loss of Mains Protections 509 Mains <<f 525
Vector Shift Limit 509 Mains <<f Delay 525
ROCOF1 Windows Length 509 Mains <<f Hys 525
ROCOF1 df/dt 510 Subgroup: Mains Fault Timers 526
ROCOF2 Windows Length 510 Mains Stabilization Delay 526
ROCOF2 df/dt 511 MCB Close Delay 526
ROCOF3 Windows Length 511 Group: Grid Codes 527
ROCOF3 df/dt 512 Subgroup: Grid Codes Test 527
ROCOF4 Windows Length 512 Grid Codes Test 527
ROCOF4 df/dt 513 Subgroup: Mains Params/MP Synchronization 527
Vector Shift/ROCOF CB Selector 513 Mains Params/MP Synchronization 527
Group: Mains Settings 514 Mains Synchronization V Max 528
Subgroup: Mains Voltage Protections 514 Mains Synchronization V Min 528
Mains >V 514 Mains Synchronization f Max 529
Mains >V Delay 514 Mains Synchronization f Min 529
Mains >V Hys 515 Mains Synchronization Period 530
Mains >>V 515 After MP Synchronization V Max 530
Mains >>V Delay 516 After MP Synchronization V Min 531
Mains >>V Hys 516 After MP Synchronization f Max 531
Mains 10min Avg >V 517 After MP Synchronization f Min 532
Mains 10min Avg >V Delay 517 After MP Synchronization Period 532
Mains <V 518 Subgroup: After Mains Trip Period 533
Mains <V Delay 518 After Mains Trip 533
Mains <V Hys 519 After Mains Trip Period 533
Mains <<V 519 After Mains Trip Period Priority 534
Mains <<V Delay 520 After Mains Trip Period Ramp 534
Mains <<V Hys 520 Subgroup: Power Over/Under Frequency 535
Mains V Unbalance 521 Power Over/Under Frequency 535
Mains V Unbalance Delay 521 Power Over/Under Frequency Delay 535
Subgroup: Mains Frequency Protection 522 Return Over/Under Frequency Delay 536

Return Over/Under Frequency Period 536 Q Ramp 555
Return From Over/Under Frequency Priority 537 Q Deadband 555
Return From Over/Under Frequency Ramp 537 Subgroup: Q(Um) 556
Mains Frequency Rise Priority 538 Q(Um) 0 Reference 556
Mains Frequency Rise Ramp 538 Q(Um) Deadband 556
Mains Frequency Fall Priority 539 Subgroup: Qref/Ulim 557
Mains Frequency Fall Ramp 539 Qref/Pnom Shift 557
Subgroup: Load Reduction 540 Qref/Ulim Deadband 557
Load Reduction 540 Subgroup: Q(P) 558
Load Reduction 1 540 Q(P) Deadband 558
Load Reduction 2 541 Subgroup: Soft Unload 558
Load Reduction 3 541 Soft Unload Priority 558
Load Reduction 4 542 Soft Unload Ramp 559
Load Reduction Priority 542 Subgroup: Pave 560
Load Reduction Ramp 543 Pave Protection 560
Subgroup: P(Um) 544 Pave 560
P(Um) 544 Group: BESS Protections 561
P Ramp Filter 545 Subgroup: Overload Protection 561
P(Um) Priority 546 IDMT Overload Protection 561
P(Um) Ramp 546 Subgroup: Current Protection 562
Subgroup: P For Q 547 Short Circuit Protection 562
P For Q Limitation 547 IDMT BESS >A Protection 562
P For Q Deadband 547 BESS Current Unbalance Protection 564
P For Q Priority 548 Subgroup: Voltage Protection 565
P For Q Ramp 548 BESS >V 565
Subgroup: Q&U Protection 549 BESS >>V Protection 566
Q&U Protection 549 BESS <V Protection 567
Q&U < V 550 BESS V Unbalance Protection 567
Q&U < Q 550 Mains >V Protection 568
Q&U Protection Delay 551 Mains >>V Protection 570
Q&U CB Selector 551 Mains 10min Avg >V Protection 571
Subgroup: Dynamic Support 552 Mains <V Protection 572
Dynamic Support 552 Mains <V Protection 573
Dynamic Support Protection Type 552 Mains V Unbalance Protection 574
Dynamic Support PF/Q Control 553 Subgroup: Frequency Protection 575
LVRT Level Severe 553 BESS >f Protection 575
Post VRT Priority 554 BESS <f Protection 576
Post VRT Ramp 554 Mains >f Protection 577
Subgroup: Q Ramp 555 Mains >>f Protection 578

Mains <f Protection 579 User Button 12 601
Mains <<f Protection 580 User Button 13 601
Subgroup: Bus Meas Error 581 User Button 14 602
Bus Meas Error 581 User Button 15 602
Subgroup: Earth Fault Current Protection 582 User Button 16 603
Earth Fault Current Protection 583 User Button 17 603
Subgroup: Loss of Mains Protections 584 User Button 18 604
Vector Shift Protection 584 User Button 19 604
ROCOF1 Protection 585 User Button 20 605
Subgroup: SOC Protection 589 User Button 24 607
BESS <SOC Protection 589 User Button 25 607
BESS >SOC Protection 589 User Button 26 608
BESS <<SOC Protection 590 User Button 27 608
BESS >>SOC Protection 590 User Button 28 609
BESS SOC Not Configured 591 User Button 29 609
BESS SOC Not Available 591 User Button 30 610
Group: Load Shedding 592 User Button 31 610
Subgroup: Load Shedding 592 User Button 32 611
Load Shedding Active 592 Group: Scheduler 611
Load Shedding Level 593 Subgroup: Time & Date 611
Load Shedding Delay 593 Time 611
Load Reconnection Level 594 Date 612
Load Reconnection Delay 594 Time Stamp Period 612
Auto Load Reconnection 595 Time Zone 613
Group: User Buttons 595 DST Switching Mode 613
Subgroup: User Buttons 595 Time Mode 614
User Button 1 595 DST Period Rule 614
User Button 2 596 Premortem History Period 615
User Button 3 596 Subgroup: Sunrise/Sunset 615
User Button 4 597 Sunrise/Sunset Function 615
User Button 5 597 Sunrise/Sunset Latitude 616
User Button 6 598 Sunrise/Sunset Longtitude 616
User Button 7 598 Subgroup: Timer 1 617
User Button 8 599 Timer 1 Function 617
User Button 9 599 Timer 1 Setup 618
User Button 10 600 Subgroup: Timer 2 619

Timer 2 Function 619 Maintenance Timer 2 Interval 642
Timer 2 Setup 620 Maintenance Timer 2 Protection 643
Subgroup: Timer 3 621 Subgroup: Maintenance Timer 3 643
Timer 3 Function 621 Maintenance Timer 3 RunHours 643
Timer 3 Setup 622 Maintenance Timer 3 Interval 644
Subgroup: Timer 4 623 Maintenance Timer 3 Protection 644
Timer 4 Function 623 Subgroup: Maintenance Timer 4 645
Timer 4 Setup 624 Maintenance Timer 4 RunHours 645
Subgroup: Timer 5 625 Maintenance Timer 4 Interval 645
Timer 5 Function 625 Maintenance Timer 4 Protection 646
Timer 5 Setup 626 Group: Geo-Fencing 646
Subgroup: Timer 6 627 Subgroup: Geo-Fencing 646
Timer 6 Function 627 Geo-Fencing 646
Timer 6 Setup 628 Subgroup: Position 647
Subgroup: Timer 7 629 Home Latitude 647
Timer 7 Function 629 Home Longitude 647
Timer 7 Setup 630 Subgroup: Fence 1 648
Subgroup: Timer 8 631 Fence 1 Protection 648
Timer 8 Function 631 Fence 1 Radius 648
Timer 8 Setup 632 Fence 1 Delay 649
Subgroup: Timer 9 633 Subgroup: Fence 2 649
Timer 9 Function 633 Fence 2 Protection 649
Timer 9 Setup 634 Fence 2 Radius 650
Subgroup: Timer 10 635 Fence 2 Delay 650
Timer 10 Function 635 Group: CM-4G-GPS 651
Timer 10 Setup 636 Subgroup: RTC Synchronization 651
Subgroup: Timer 11 637 Time Zone 651
Timer 11 Function 637 6 back to Controller objects
Timer 11 Setup 638
Subgroup: Timer 12 639
Timer 12 Function 639
Timer 12 Setup 640
Group: Maintenance Timers 640
Subgroup: Maintenance Timer 1 640
Maintenance Timer 1 RunHours 640
Maintenance Timer 1 Interval 641
Maintenance Timer 1 Protection 641
Subgroup: Maintenance Timer 2 642
Maintenance Timer 2 RunHours 642

Group: Process Control
Subgroup: Application Selector
Default Application Select
Setpoint group Process Control Related FW 1.3.0

Range [units] MPTM / MINT [-]
Default value MINT Force value NO
Step [-]
Comm object 12157 Related applications MINT, MPTM
Config level Advanced
Setpoint visibility Always
Description
This setpoint selects default controller's application mode while any application LBI is not activated.
Current controller's application mode is stored in value Application Mode (page 777).
IMPORTANT: Controller Mode (page 777) has to be OFF, otherwise controller application
can not be changed.
Single parallel to mains application. The controller controls up to three breakers – a mains
MPTM breaker (MCB), BESS breaker (BCB), and/or PV breaker (PVCB). Feedbacks from all used
breakers are required.
Multiple island-parallel application without mains and multiple parallel application with mains.
MINT The controller controls up to two breakers – a BESS breaker and/or PV breaker. For parallel
to mains operation also mains breaker feedback is required.
Note: For more information about Applications, see chapter Applications overview (page 40).
Note: The controller also controls the NCB, check the chapter Breaker Control (page 126) for more
information about breakers.
6 back to List of setpoints

Subgroup: Load Control
Load Control PTM Mode

Range [units] Baseload / Imp / Exp [-]
Default value Baseload Force value YES
Step [-]
Comm object 8638 Related applications MPTM
Config level Standard
Setpoint visibility Only if Application Mode (page 777) = MINT
Description
This setpoint adjusts the type of load control.
BESS produces amount of the power. Source or requested power is given by

setpoint Load Request Source (page 346) The rest of power is supplied from the
Mains or exported to the Mains. Even in baseload control mode can be the
Import/Export limited. This function can be activated by setpoint Import/Export
Limitation (page 1) = Enabled. Then the request for the power of the BESS
operating in baseload can be limited to prevent the Import/Export go below the
limit given by setpoint Import Load (page 348).
Example: Baseload = 1000 kW, load = 700 kW, Import load = 100. Then
Baseload
the Baseload request will be limited to 600 kW to prevent the Import power
go below 100 kW
Example: Baseload = 1000 kW, load = 700 kW, Import load = -100. Then
the Baseload request will be limited to 800 kW to prevent the Import power
go below -100 kW (actually it is limitation of the export).
The load of the BESS is controlled to keep constant level of base load of the whole
system. The level is adjusted by the setpoint #System Baseload (page 348).
BESS produces the certain amount of power to keep constant import/export from
Imp/Exp the Mains regardless the demand of the load. The source of requested
import/export is given by setpoint Load Request Source (page 346).

Load Request Source

Range [units] Setpoint / Analog External Value [-]
Default value Setpoint Force value YES
Step [-]
Description
This setpoint adjusts source type of requested load control.
Application Mode (page 777) = MPTM
Load Control PTM

Load Request Source Source
Mode (page 345)
BESS Charge Power (page
Baseload
Setpoint 427)/BESS Discharge Power (page 428)
Imp/Exp Import Load (page 348)
LOAD CONTROL: ANEXT BASELOAD (PAGE
Baseload
989)
Analog External Value
LOAD CONTROL: ANEXT IMP/EXP LOAD
Imp/Exp
(PAGE 990)
See Load control (page 259)Load control (page 256) for more information.
Application Mode (page 777) = MINT
Load Request Source Source

Setpoint #System Baseload (page 348)
Analog External Value LOAD CONTROL: ANEXT BASELOAD (PAGE 989)
See Load control (page 256) for more information.

#System Load Control PTM

Range [units] Baseload / Load Shar [-]
Default value Baseload Force value NO
Step [-]
Comm object 8774 Related applications MINT
Description
Load control mode in parallel to Mains operation of the whole controller group.
The total power of the group is controlled to constant level given by the setpoint
#System Baseload (page 348). Each loaded unit takes equal part (relative to
their nominal power) from this requested value. The load is regulated locally in
Baseload
each controller by Load control regulation loop, load-sharing is not active. The
setpoint #System Baseload (page 348) is also used for determining which unit
have to run or not.
The load is controlled by the supervisor (IM1010) controller to share the total load
(given by the setpoint #System Baseload (page 348)) with other loaded units in
Load Shar
such a way, that all loaded units will be loaded at the same level (relative to their
nominal power). Load-sharing regulation loop is active.
Note: The Load Shar mode shall be used in case the supervisor (IM1010) controller is present in the
system. In systems without the supervisor (IM1010) controller the setpoint must be setup to the
Baseload option.
Note: The power factor (PF) is regulated to constant level given by the setpoint #System PF
Control PTM (page 351) in parallel to Mains operation and does not depend on active load control
mode.

Import Load

-32 000 .. 32 000 [kW] (depends on the selected Power Formats And Units (page
Range [units]
196))
0 kW (depends on the selected
Default value Power Formats And Units (page Force value NO
196))
Step 1 kW (depends on the selected Power Formats And Units (page 196))
Description
Defines actual imported (exported) active power in parallel to Mains operations in Import/Export mode or
the minimal imported (maximal exported) active power from the Mains in Baseload with I/E Limit mode.
The value from this Setpoint is used if:
Setpoint Load Control PTM Mode (page 345) = Import/Export or
Setpoint Load Control PTM Mode (page 345) = Baseload and Import/Export Limitation (page
1) = Enabled.
See chapter Load control (page 259)Load control (page 256) for more information.
Note: If the value of the setpoint is >0 the power is imported from the Mains, if the setpoint value is
<0, then the power is exported to the Mains.
#System Baseload

Range [units] 0 .. 32 000 [kW] (depends on the selected Power Formats And Units (page 196))
1 000 kW (depends on the selected Power
Default value Force value NO
Formats And Units (page 196))
Description
Required total active power of the controller group in parallel to Mains operation in Baseload mode.
Setpoint #System Load Control PTM (page 347) = Baseload
See chapter Load control (page 256) for more information.
Note: The # setpoints are shared with all controllers on site via intercontroller CAN line.

Subgroup: PF/Q Control
PF/Q Control PTM Mode

Range [units] PF Control / PF(Pm) / Q Control / Q(Um) / Q(P) / Qref / Ulim [-]
Default value PF Control Force value NO
Step [-]
Description
This setpoint adjust the type of PF/Q control.
The BESS Power Factor (page 667) is controlled according to preset required
PF Control
value. See PF Control (page 261)PF/Q control (page 257) for more information.
Grid Codes specific functionality where the power factor depends on the actual
PF(Pm) power of the BESS. See PF(Pm) (page 262)PF/Q control (page 257) for more
information.
The BESS Q (page 665) is controlled according to preset required value. See PF
Q Control
Control (page 261)PF/Q control (page 257) for more information.
Grid Codes specific functionality where the BESS Required Q (page 757) depends
on the mains voltage (Mains/Bus Voltage L1-N (page 731), Mains/Bus Voltage
Q(Um)
L2-N (page 731) and Mains/Bus Voltage L3-N (page 732)). See Q(Um) (page
263)PF/Q control (page 257) for more information.
Q(P) on the BESS P (page 664). See Q(P) (page 264)PF/Q control (page 257) for
more information.
on the mains voltage (Mains/Bus Voltage L1-N (page 731), Mains/Bus Voltage
Qref/Ulim L2-N (page 731) and Mains/Bus Voltage L3-N (page 732)) with a modified
behavior. See Qref/Ulim (page 265)PF/Q control (page 257) for more
information.
Actual selected control mode is available in System PF/Q Control (page 756).

PF/Q Request Source

Range [units] Setpoint / Analog External Value [-]
Step [-]
Description
This setpoint adjust the source type requested of PF/Q control.
Application Mode (page 777) = MPTM
PF/Q
PF/Q Regulation Type PF/Q Control PTM
Request Source
(page 351) Mode (page 349)
Source
Base Power Factor (page
PF Control
Base PF/ Q Control 352)
Q Control Base Q (page 353)
Setpoint
Import Power Factor (page
PF Control
Imp/Exp PF/ Q Control 352)
Q Control Import Q (page 354)
PF CONTROL: ANEXT BASE
PF Control
PF (PAGE 992)
Base PF/ Q Control
Q CONTROL: ANEXT BASE Q
Q Control
Analog (PAGE 1004)
External Value PF CONTROL: ANEXT
PF Control
IMP/EXP PF (PAGE 993)
Imp/Exp PF/ Q Control
Q CONTROL: ANEXT IMP/EXP
Q Control
Q (PAGE 1004)
See PF Control (page 261)PF/Q control (page 257) for more information.
Application Mode (page 777) = MINT
PF/Q
#System PF Control
Request Source
PTM (page 351)
Source
Base PF #System Power Factor (page 353)
Setpoint
Base Q #System Base Q (page 354)
Analog Base PF PF CONTROL: ANEXT BASE PF (PAGE 992)
External Value Base Q Q CONTROL: ANEXT BASE Q (PAGE 1004)
See PF/Q control (page 257) for more information.

PF/Q Regulation Type

Range [units] Base PF/Q Control / Import/Export PF/Q Control [-]
Default value Base PF/Q Control Force value YES
Step [-]
Description
This setpoint adjust the regulation type of PF/Q control.
BESS produces requested amount of the power, i.e. Mains Import/Export is

Base PF/Q adjusted so BESS produces exactly requested power. See PF Control (page
Control 261)PF/Q control (page 257) for more information.
Mains Import/Export is exactly as requested, i.e. BESS power is adjusted to

Import/Export
fulfill Import/Export requirements. See PF Control (page 261)PF/Q control
PF/Q Control
(page 257) for more information.
#System PF Control PTM

Range [units] Base PF / Base Q / Var Shar [-]
Default value Base PF Force value NO
Step [-]
Description
Power factor control mode in parallel to Mains operation of the whole controller group.
PF of the BESS is controlled by their PF control loops to provide constant system

Base PF
power factor adjusted by setpoint #System Power Factor (page 353).
Var Shar PF of the BESS (reactive power) is controlled through the VAr sharing line.
Reactive power of the BESS is controlled by their Q control loops to provide
Base Q constant BESSs reactive power adjusted by setpoint #System Base Q (page
354).

Base Power Factor

Range [units] 0,001 .. 1,999 [-]
Default value 1 [-] Force value YES
Step 0,001 [-]
Setpoint visibility Only if Application Mode (page 777) = MPTM
Description
Required BESS power factor when the BESS is running in parallel to the mains in PF Control BASE
mode.
Setpoint PF/Q Regulation Type (page 351) = Base PF/Q Control and
Setpoint PF/Q Control PTM Mode (page 349) = PF Control.
See chapter PF Control (page 261) for more information.
Import Power Factor

Range [units] 0,001 .. 1,999 [-]
Default value 1 [-] Force value NO
Step 0,001 [-]
Description
Defines required power factor in parallel to Mains operation in PF Control IMP/EXP mode.
Setpoint PF/Q Regulation Type (page 351) = Import/Export PF/Q Control and
Setpoint PF/Q Control PTM Mode (page 349) = PF Control.
See chapter PF Control (page 261)PF/Q control (page 257) for more information.
Note: If the setpoint value is >1 the Mains Load Character is C, if the setpoint value is <0 the Mains
Load Character is L.

#System Power Factor

Range [units] 0,60 .. 1,20 [-]
Default value 1,00 [-] Force value NO
Step 0,01 [-]
Description
Required total power factor of the controller group in parallel to Mains operation in PF Control BASE
mode.
Setpoint #System PF Control PTM (page 351) = Base PF
Note: If the setpoint value is >1 the BESS Load Character is C, if the setpoint value is <0 the BESS
Load Character is L.
Base Q

-32 000 .. 32 000 [kVAr] (depends on the selected Power Formats And Units
Range [units]
(page 196))
0 kVAr (depends on the selected Power
Default value Force value YES
Step 1 kVAr (depends on the selected Power Formats And Units (page 196))
Description
Required Gen-set reactive power in parallel to mains operation in Q Control BASE mode.
Setpoint PF/Q Regulation Type (page 351) = Base PF/Q Control and
Setpoint PF/Q Control PTM Mode (page 349) = Q Control.
See chapter Q Control (page 262) for more information.

Import Q

-32000 .. 32000 [kVAr]
Range [units]
(depends on the selected Power Formats And Units (page 196))
Default value 0 kVAr Force value NO
Description
Defines actual imported (exported) reactive power in parallel to Mains operations in Q Control IMP/EXP
Mode.
Setpoint PF/Q Regulation Type (page 351) = Import/Export PF/Q Control and
Setpoint PF/Q Control PTM Mode (page 349) = Q Control.
See chapter Q Control (page 262)PF/Q control (page 257) for more information.
Note: If the value of the setpoint is >0 the power is imported from the Mains, if the setpoint value is
<0, then the power is exported to the Mains.
#System Base Q

-32 000 .. 32 000 [kVAr] (depends on the selected Power Formats And Units
Range [units]
(page 196))
0 kVAr (depends on the selected Power
Description
Required total reactive power of the controller group in parallel to Mains operation in Q Control BASE
mode.
Setpoint #System PF Control PTM (page 351) = Base Q

Subgroup: Neutral Contactor
#Neutral Contactor Control

Range [units] Each / Common [-]
Default value Each Force value NO
Step [-]
Description
This setpoint changes the behavior of binary output NCB CLOSE/OPEN (PAGE 963) which is used for
neutral contactor control.
See more information in the chapter Neutral Contactor Breaker (page 129).
The EACH option should be used if each Gen-set and BESS has its own neutral contactor. The
NCB CLOSE/OPEN (PAGE 963) output on each Gen-set and BESS is given by an internal
algorithm, which ensures, that always exactly one Gen-set or BESS connected to the bus with the
lowest CAN address has the neutral contactor closed.
The COMMON option should be used if there is only one common neutral contactor for the whole
site. The NCB CLOSE/OPEN (PAGE 963) outputs from all controllers are combined together and the
combined signal is used to control the breaker. If at least one Gen-set or BESS in the site is
running and has a proper voltage, the neutral contactor is closed.
Note: LBI NCB FEEDBACK (PAGE 905) and LBO NCB CLOSE/OPEN (PAGE 963) has to be configured
for proper functionality.
Note: This setpoint is available only for the MINT application, in case of the MPTM application the
NCB automatically behaves like this setpoint is set to COMMON option.
Subgroup: Process Limitation
CB Control In MAN Mode

Range [units] Full Ctrl / Aut Trans / Islnd Disl [-]
Default value Full Ctrl Force value YES
Step [-]
Description
The behavior of transition of load in MAN mode is adjusted via this setpoint.

No limitation of CB control in MAN mode (operator can close any breaker
Full Ctrl manually or evoke the synchronization and consequential operation in parallel to
Mains)
Operator can control both MCB or BCB breaker. However once transition is
evoked the controller performs the automatic transfer of the load (depends on
adjustment of setpoints Transfer BESS To Mains (page 466) and Transfer
Mains To BESS (page 465)).
Controller performs synchronization across MCB, if BCB is closed and MCB
button is pushed. Load transfer is done after synchronization and BCB is opened
automatically.
Controller performs synchronization across BCB , if MCB is closed and BCB
button is pushed. Load transfer is done after synchronization and MCB is opened
Aut Trans automatically.
It is also possible to open currently closed breaker and keep the load non-
energized. Then it is possible to close MCB or BCB to energize the load from a
healthy source.
Note: Parallel operation with Mains continues, if system already operates in
parallel with Mains and setting is changed to Aut Trans. It is necessary to push
MCB or BCB button to open a breaker.
Note: Open transfer is performed, if the Open option is selected with Transfer
BESS To Mains (page 466) or Transfer Mains To BESS (page 465)
Behaves like the full manual control but the Island operation is disabled.
Example: When MCB is opened and BCB is pressed, controller does not
Islnd Disl go to island.
Example: In parallel operation when MCB button is pressed, MCB is not

opened.

Subgroup: Mains Import Measurement
Mains Measurement P

Range [units] None / Mains CT / Analog Input [-]
Default value None Force value NO
Step [-]
Description
Defines source value of the Mains Import P (page 734).
The value Mains Import P (page 734) is not measured. The duration of the load
None transfer in direction Mains to BESS is given exactly by the setpoint Close
Transfer Max Duration (page 464).
The value Mains Import P (page 734) is measured via Mains CT which is located
Mains CT on phase L1. The load transfer in direction Mains to BESS is considered to be
finished when the Mains is unloaded under certain level.
The value Mains Import P (page 734) is measured via analog input, accordingly
Analog
LAI: MAINS MEASUREMENT P (PAGE 992). The load transfer in direction Mains to
Input
BESS is considered to be finished when the Mains is unloaded under certain level.

Mains Measurement Q

Range [units] None / Mains CT / Analog Input [-]
Default value None Force value NO
Step [-]
Description
Defines source value of the Mains Import Q (page 735).
The value Mains Import Q (page 735) is not measured. The duration of the load
None transfer in direction Mains to BESS is given exactly by the setpoint Close
Transfer Max Duration (page 464).
The value Mains Import Q (page 735) is measured via Mains CT which is located
Mains CT on phase L1. The load transfer in direction Mains to BESS is considered to be
finished when the Mains is unloaded under certain level.
The value Mains Import Q (page 735) is measured via analog input, accordingly
Analog
LAI: MAINS MEASUREMENT Q (PAGE 992). The load transfer in direction Mains to
Input
BESS is considered to be finished when the Mains is unloaded under certain level.
Subgroup: Peak Shaving
Peak Shaving

Range [units] Enabled / Disabled [-]
Default value Disabled Force value YES
Step [-]
Comm object 11601 Related applications SPTM
Description
This setpoint enables/disables peak shaving function.
The Peak shaving (page 1) function is active and its behaviour is set by setpoints
Enabled Peak Shaving Start Level (page 359), Peak Shaving Stop Level (page 359)
and Peak Shaving Start/Stop Delay (page 360).
The Peak shaving (page 1) function is BLOCKED and the start command can not
Disabled
be activated even the conditions for Peaks Shaving activation were fulfilled.

Peak Shaving Start Level

Peak Shaving Stop Level (page 359) .. 32000 [kW]
Range [units]
1000 kW (depends on the selected Power
Only if Application Mode (page 777) = MPTM and Peak Shaving (page 358) =
Setpoint visibility
Enabled
Description
This setpoint starts BESS, when the value of the load consumption Load P (page 720) exceeds the
value given by this setpoint for the time of Peak Shaving Start/Stop Delay (page 360).
The BESS is synchronized to the Mains (kept in the parallel to the Mains) and the BESS power is
controlled according to the settings in the Groups Process Control and Speed/Load Control.
The BESS stays running until the conditions for Peak Shaving run are active. Conditions of deactivation
are given by the setpoint Peak Shaving Stop Level (page 359) and Peak Shaving Start/Stop Delay
(page 360).
Peak Shaving Stop Level

0 .. Peak Shaving Start Level (page 359) [kW]
Range [units]
Setpoint visibility
Enabled
Description
This setpoint stops BESS, of the load consumption Load P (page 720) decreases under the value given
by this setpoint for the time of Peak Shaving Start/Stop Delay (page 360).

Peak Shaving Start/Stop Delay

Range [units] 0 .. 600 [s]
Default value 600 s Force value YES
Step 1s
Setpoint visibility
Enabled
Description
Defines the delay of activation or deactivation of the Peak shaving (page 1).
The value of the load consumption Load P (page 720) exceeds the value given
Starts when
by the setpoint Peak Shaving Start Level (page 359).
The value of the load consumption Load P (page 720) decreases under the
Stop when
value given by the setpoint Peak Shaving Stop Level (page 359)
Subgroup: Breaker Control
MCB Logic
Setpoint group Mains Settings Related FW 1.3.0

Range [units] Close-On / Close-Off [-]
Default value Close-Off Force value YES
Step [-]
Description
This setpoint adjusts the behavior of LBO MCB CLOSE/OPEN (PAGE 959) and LBI MCB FEEDBACK (PAGE
902).
When LBO MCB CLOSE/OPEN (PAGE 959) is closed – LBI MCB

Close On
FEEDBACK (PAGE 902) should be closed.
When LBO MCB CLOSE/OPEN (PAGE 959) is closed – LBI MCB
Close Off
FEEDBACK (PAGE 902) should be opened.

Image 7.1 Close-On
Image 7.2 Close-Off
Note: LBO MCB CLOSE/OPEN (PAGE 959) as well as this setpoint is used only for contactors.
MCB Control Mode

Range [units] Internal / External [-]
Default value Internal Force value YES
Step [-]
Description
This setpoint adjusts control mode of MCB.
The MCB breaker is controlled by controller.

The controller accepts the opening of MCB from the external device (Mains
relay). When the MCB is opened externally then:
The event "MCB opened Externally" is recorded in history log
Internal
Controller starts to count down the MCB Close Delay and is going to be
closed to the MCB once it elapses.
Incorrect reaction of the MCB FEEDBACK (PAGE 902) to internal MCB
Close/Open command causes Wrn MCB Fail (page 1089)

Controller does not control the MCB at all. The MCB is controlled externally,
when the MCB FEEDBACK (PAGE 902) gets changed, then the event "MCB
Opened" or "MCB Closed" is recorded to the history log.
Controller always accepts the MCB FEEDBACK (PAGE 902) without of issuing
External any alarm.
The controller informs the superordinate system about the status of the breaker
automaton using the signals
LBO FORWARD SYNCHRONIZATION (PAGE 949)
LBO REVERSE SYNCHRONIZATION (PAGE 974)
BCB Control Mode

Range [units] Internal / Follow / External [-]
Step [-]
Description
This setpoint adjusts control mode of BCB.
The breaker is controlled only from controller. Any unexpected change of BCB
FEEDBACK (PAGE 881) causes Stp BCB Fail (page 1124) immediately.
Internal
Incorrect reaction of the BCB FEEDBACK (PAGE 881) on internal BCB
Close/Open command causes Stp BCB Fail (page 1124)
BCB Openning BCB FEEDBACK (PAGE 881) = 0 is accepted from external
devices with history record "BCB Opened Externally".
Follow
Incorrect reaction of the BCB FEEDBACK (PAGE 881) to internal BCB
Close/Open command causes Stp BCB Fail (page 1124)
Controller does not control the BCB is controlled externally, when the BCB
FEEDBACK (PAGE 881) get changed, then the event "BCB Opened" or "BCB
Closed" is recorded to the history log.
Controller always accept the BCB FEEDBACK (PAGE 881) without of issuing
External any alarm.
When the Sd protection shuts down the BESS, the BCB stays closed. BCB
stays closed until it is opened externally.
IMPORTANT: BESS with closed BCB is not blocked against starting.
IMPORTANT: Anytime when the controller is synchronizing via BCB the External BCB
closing is being accepted in all BCB control modes.

PVCB Control Mode

Range [units] Internal / External [-]
Step [-]
Setpoint visibility Only if Application Mode (page 777) = PVCB
Description
This setpoint allows you to manage the circuit breaker in your PV system in three different ways: Internal,
Follow, and Not Installed.
The controller takes full control of the PV Circuit Breaker (PVCB), using its built-in
Internal
settings and logic. It doesn't listen to external commands; it operates by itself.
The controller still manages the PVCB, just like in "Internal" mode. However, it can
Follow
also listen to external command for opening the circuit breaker.
Not The PV Circuit Breaker isn't part of your system. In this case, the controller runs
Installed your PV system on its own, as if the PVCB doesn't exist.
Delay Between Closing Attempts

Default value 20 [s] Force value NO
Step 1 [s]
Description
This setpoint adjusts the delay between breaker closing attempts the controller performs when a breaker
is requested to be closed. Delay is one second longer than you set here due breaker's safety.
Example: If this setpoint is set to 10 seconds, the delay between another attempt to close the
breaker will be 11 seconds.

Subgroup: Controller Redundancy
Hot Swap Redundancy

Disabled / Master / Backup / Master + Modules Redundancy / Backup + Modules
Range [units]
Redundancy [-]
Step -
Description
This setpoint adjusts behavior of Hot Swap Redundancy (page 160) function.
Disabled The Hot Swap Redundancy function is disabled.

The controller is expected to be used as Master controller in the hot swap
Master
function. One set of CAN modules for a Master-Backup pair is used.
The controller is expected to be used as Backup controller (redundant
Backup controller) in the hot swap function. One set of CAN modules for a Master-
Backup pair is used.
The controller is expected to be used as Master controller in the hot swap
Master + Modules
function. Separate set of CAN modules is used for each controller in a
Redundancy
Master-Backup pair.
The controller is expected to be used as Backup controller (redundant
Backup + Modules
controller) in the hot swap function. Separate set of CAN modules is used
Redundancy
for each controller in a Master-Backup pair.
Note: Hot Swap Redundancy function can be enabled only if you have correct SW Key (page 381).

Subgroup: System Variability
BESS

Range [units] Installed / Not Installed
Default value Installed Force value NO
Step [-]
Description
This setpoint defines the topology of the Microgrid system. If the BESS is included in the system this
setpoint should be set to Installed. The visibility of the setpoints and values related to the BESS is
dependent on this setpoint.
PV

Step [-]
Description
This setpoint defines the topology of the Microgrid system. If the PV or any other renewable source is
included in the system this setpoint should be set to Installed. The visibility of the setpoints and values
related to the PV is dependent on this setpoint.
WT

Step [-]
Description
This setpoint defines the topology of the Microgrid system. If the WT or any other renewable source is

included in the system this setpoint should be set to Installed. The visibility of the setpoints and values
related to the WT is dependent on this setpoint.
Mains

Step [-]
Description
This setpoint defines the topology of the Microgrid system. If the Mains is included in the system this
setpoint should be set to Installed. The visibility of the setpoints and values related to the Mains is
Gensets

Step [-]
Description
This setpoint defines the topology of the Microgrid system. If the Gen-sets are included in the system this
setpoint should be set to Installed. The visibility of the setpoints and values related to the Gen-sets is
Group: Basic settings
Subgroup: Name

Controller Name
Setpoint group Basic settings Related FW 1.3.0

Range [units] 0 .. 15 characters [-]
Default value InteliNeo6000 Force value NO
Step [-]
Description
User defined name, used for the controller identification at remote phone or mobile connection.
Controller Name is maximally 15 characters long and can be entered using InteliConfig or from
controller’s configuration menu.
Subgroup: Power settings
Samax

OFF; 0 .. 32000 [kVA] (depends on the selected Power Formats And Units (page
Range [units]
196))
200 kVA (depends on the selected
Default value Power Formats And Units (page Force value YES
196))
Step 1 kVA (depends on the selected Power Formats And Units (page 196))
Description
Maximal apparent power of the BESS.

Nominal power

MINT,
Comm object 8276 Related applications
MPTM
Description
Nominal power of the BESS.
BESS protections/functions such as IDMT Overload Protection (page 561) and 2POverload Start
Evaluation Level (page 437), etc are related to this setpoint.
Installed Power

OFF; 1 .. Nominal power (page 368) [kW] (depends on the selected Power
Range [units]
Default value OFF Force value Yes
Step 1 [kW] (depends on the selected Power Formats And Units (page 196))
Related
Comm object 16183 MINT, MPTM
applications
Description
This setpoint adjusts the maximum power agreed for parallel to mains mode i.e. Breaker state (page
778) = ParalOper/MultParOp.
This setpoint influences:
Load Shedding (page 170)
Generator Unload BCB Open Level (page 467)
Grid Codes (page 294)

Subgroup: Current settings
Nominal Current

Range [units] 1 .. 10000 [A]
Default value 350A Force value YES
Step 1A
Description
Current limit for BESS current protections and maximal continuous BESS current. Nominal current can
be different from mains rated current value.
BESS CT Ratio Prim

Range [units] 1 .. 15000 [A]
Default value 500A Force value NO
Step 1A
Description
This setpoint defines the primary range of the current transformer used for the BESS current
measurement.
Note: The setpoint is applied on all three phases of the BESS current.
Note: The CT is usually described by this definition: CT Ratio Prim / CT Ratio Sec: Example:
100/5, 500/5, 1000/1

BESS CT Ratio Sec

Range [units] /5A or /1A [-]
Default value /5A Force value NO
Step [-]
Description
This setpoint defines the secondary range of the current transformer used for the BESS current
measurement.
Note: This setpoint is applied on all three phases of the BESS current.
100/5, 500/5, 1000/1
Mains/Bus CT Ratio Prim / EFC

Range [units] 1 .. 15000 [A]
Default value 300 A Force value YES
Step 1A
Description
This setpoint is used for settings of primary CT ratio of Mains L1 Current (page 734) measurement,
which is used for Mains Import P (page 734) calculation for needs of Soft Unload function.
IMPORTANT: L1 Mains current must be measured otherwise the power will be calculated
wrongly.
100/5, 500/5, 1000/1

Mains/Bus CT Ratio Sec / EFC

Range [units] /1A or /5A [-]
Default value /5A Force value YES
Step [-]
Description
This setpoint is used for settings of secondary CT ratio of Mains L1 Current (page 734) measurement,
which is used for Mains Import P (page 734) calculation for needs of Soft Unload function.
IMPORTANT: L1 Mains current must be measured otherwise the power will be calculated
wrongly.
100/5, 500/5, 1000/1
3Ph CT Location

Range [units] BESS/Mains
Default value BESS Force value YES
Step [-]
Description
This setpoint is used to switch measurement of 3 phase current between BESS/Mains.
Subgroup: Voltage settings
Connection type

Range [units] 3ph4Wire / High Leg D / 3ph3Wire / SplitPhase / MonoPhase [-]
Default value 3Ph4Wire [-] Force value NO
Step [-]

Description
This setpoint defines connection type of the installation.
3Ph4Wire Grounded Star (Grounded Wye) connection – 3PY

Three phase voltage measurement L1,L2,L3 with 120° phase shift
3x CT (Current Transformer)
High Leg D High Leg Delta connection
Three phase voltage measurement L1,L2,L3
3Ph3Wire Ungrounded Delta connection
Open Delta
Ungrounded Wye
Corner-Grounded Delta
Split Phase Delta
Three phase voltage measurement L1,L2,L3 with 120° phase shift
No neutral is available 3x CT (Current Transformer)
SplitPhase Double Delta connection
Split Phase
Two phase voltage measurement L1,L2 with 180° phase shift
Mono Phase Single phase voltage measurement L1-N
Evaluated Voltage Protections

Range [units] Both / Phase-Phase / Phase-Neutral [-]
Default value Both [-] Force value NO
Step [-]
Only in case Setpoint Connection type (page 371) is set to 3Ph4Wire / High
Setpoint visibility
Leg D / SplitPhase
Description
This setpoint defines which voltage protections are evaluated.
Example: Connection type (page 371) is 3Ph4Wire and Evaluated Voltage Protections
(page 372) is set to Phase-Phase, the voltage protections will be evaluated only from Phase-
Phase voltage, does not matter what is the Phase-Neutral voltage.
IMPORTANT: Controller Mode has to be OFF, otherwise Evaluated Voltage Protections

(page 372) can not be changed and the failure dialog window is issued.

BESS Nominal Voltage Ph-N

Range [units] 10 .. 34641 [V]
Default value 231 V Force value YES
Step 1V
Only ifConnection type (page 371) != High Leg D or Connection type (page
Setpoint visibility
371) != MonoPhase
Description
Nominal BESS voltage (phase to neutral).
BESS Nominal Voltage Ph-Ph

Range [units] 10 .. 60000 [V]
Step 1V
Description
Nominal BESS voltage (phase to phase).
Mains/Bus Nominal Voltage Ph-N

Range [units] 10 .. 34641 [V]
Step 1V
Only ifConnection type (page 371) != High Leg D or Connection type (page
Setpoint visibility
371) != MonoPhase
Description
Nominal Mains/Bus voltage (phase to neutral).

Mains/Bus Nominal Voltage Ph-Ph

Range [units] 10 .. 60000 [V]
Step 1V
Description
Nominal Mains/Bus voltage (phase to phase).
BESS VT Ratio

Range [units] 0.01 .. 6000.00 [V/V]
Default value 1.00 V/V Force value NO
Step 0.01 V/V
Description
This setpoint adjusts the converting ratio of the voltage meas transformer used on ① BESS VOLTAGE
Note: This setpoint is applied on all three phases of BESS voltage.
Example:
No VT is in use - voltage conversion is 1/1
BESS VT Ratio = 1.00
VT 22kV/100V - voltage conversion is 22000/100
VT 3.3kV/110V - voltage conversion is 3300/110
BESS Voltage Input Range Select

Range [units] 200V / 400V / 600V [-]
Step [-]

Description
This setpoint adjusts the range of Ph-Ph AC Voltage measurement settings (page 17) on the ① BESS
VOLTAGE .
Note: It is possible to accurately measure Ph-Ph voltage which is maximally 25 % above the selected
range. So the maximal accurately measured voltage for the controller is 433 V Ph-N / 750 V Ph-Ph
with the selected range 600 V.
Note: If MonoPhase wiring is used the ranges are approximately corresponding to 116 V, 231 V, and
346 V Ph-N.
IMPORTANT: The range has to be set to fit the expected range of the AC voltage.
Bus

Range [units] 0.01 .. 6000.00 [V/V]
Default value 1.00 V/V Force value NO
Step 0.01 V/V
Description
This setpoint adjusts the converting ratio of the voltage meas transformer used on ② MAINS/BUS
VOLTAGE
Note: This setpoint is applied on all three phases of Mains/Bus voltage.
Example:
No VT is in use - voltage conversion is 1/1
Bus VT Ratio = 1.00
VT 22kV/100V - voltage conversion is 22000/100
Bus VT Ratio = 220.00
VT 3.3kV/110V - voltage conversion is 3300/110
Bus VT Ratio = 30.00
Bus Voltage Input Range

Range [units] 200V / 400V / 600V [-]
Step [-]

Description
This setpoint adjusts the range of Ph-Ph AC Voltage measurement settings (page 17) on the
② MAINS/BUS VOLTAGE.
Note: It is possible to accurately measure Ph-Ph voltage which is maximally 25 % above the selected
range. So, the maximal accurately measured voltage for the controller is 433 V Ph-N / 750 V Ph-Ph
with the selected range 600 V.
Note: If MonoPhase wiring is used the ranges are approximately corresponding to 116 V, 231 V, and
346 V Ph-N.
IMPORTANT: The range has to be set to fit the expected range of the AC voltage.
Bus Dead Level

0.0 .. 13.0 [%] of Mains/Bus Nominal Voltage Ph-N (page 373) and Mains/Bus
Range [units]
Nominal Voltage Ph-Ph (page 374)
6.5 % of Mains/Bus Nominal
Voltage Ph-N (page 373) and
Mains/Bus Nominal Voltage
Ph-Ph (page 374)
0.1 % of Mains/Bus Nominal Voltage Ph-N (page 373) and Mains/Bus Nominal
Step
Voltage Ph-Ph (page 374)
Setpoint
Always
visibility
Description
This setpoint defines the percentage voltage level below which is Bus considered as dead.

Subgroup: Phase Rotation
Phase Rotation

Range [units] Clockwise / Counterclockwise [-]
Default value Clockwise Force value YES
Step [-]
Description
This setpoint adjust the phase sequence of voltage terminals.
Subgroup: Frequency settings
Nominal Frequency

Range [units] 33.00 .. 520.00 [Hz]
Default value 50,00 Hz Force value YES
Step 0.01 Hz
Description
Nominal frequency of system (usually 50 or 60 Hz).
IMPORTANT: While BESS is running, this setpoint can be changed only inside currently
selected range. The ranges are 45-54 Hz and 55-65 Hz.

Subgroup: Controller settings
Controller Mode

Range [units] OFF / MAN / AUTO [-]
Default value OFF Force value NO
Step [-]
Description
This setpoint can be used for changing the controller’s mode remotely, e.g. via Modbus.
InteliConfig: Use the mode selector on the main screen for changing the mode from the front panel.
Display: Use mode selector by pressing (Right arrow) and (Left arrow). Confirm it by pressing (enter).
Power On Mode

Range [units] Previous / OFF [-]
Default value Previous Force value NO
Step [-]
Description
This setpoint adjusts controller mode after power on of controller.
Previous Controller is switched into the last mode before power off.
OFF Controller is switched into OFF mode.
Note: Remote modes - In case that some LBI remote mode is activated during power on of controller
than this LBI has higher priority than this setpoint - controller mode is forced into mode selected via
LBI. After deactivation of LBI, controller is switched into value selected via setpoint Power On Mode

Fault Reset To Manual

Range [units] Disabled / Enabled [-]
Step [-]
Description
If this function is enabled, the controller will switch automatically to MAN mode when there is a red alarm
in the alarm list and fault reset button is pressed. This is a safety function that prevents the BESS starting
again automatically in specific cases when fault reset button is pressed.
Example: Controller is in AUTO mode, there is red inactive unconfirmed alarm, and fault reset
button is pressed. The BESS will start automatically if LBI REMOTE START/STOP (PAGE 915) is
active.
Horn Timeout

Range [units] Disabled = 0; 1 .. 600; Horn Reset [s]
Default value 10 s Force value NO
Step 1s
Description
This setpoint affects horn's behavior.
Disabled Horn sound is disabled e.g. LBO HORN (PAGE 951) is never activated
1 .. 600 [s] Timeout for LBO HORN (PAGE 951). Output opens after this time elapses
Horn Reset LBO HORN (PAGE 951) is active until button Horn Reset is pressed.
Note: Horn timeout starts again from the beginning if any new alarm appears before previous Horn
timeout has elapsed.

Fail Safe Binary State

Range [units] Log0 / Log1 / Last Valid State [-]
Default value Last Valid State Force value YES
Step [-]
Description
This setpoint adjusts behavior of all binary inputs while the received value is invalid (communication lost).
Changes of the setpoint will not be applied on peripherals which are already in fail safe binary state.
Log0 The value is logical zero.

Log1 The value is logical one.
Last Valid State The value is replaced by last valid state.
Run Hours Source

Range [units] AUTO / ECU / INTERNAL [-]
Default value AUTO Force value YES
Step [-]
Description
This setpoint adjusts source for Running Hours (page 771).
Source is selected automatically between INTERNAL and ECU. ECU source is

AUTO
prioritized.
ECU Source is forced to be always ECU. ECU provides Running Hours (page 771).
Source is forced to be always INTERNAL. Controller provides Running Hours
INTERNAL
(page 771).

SW Key

Range [units] 31 characters [-]
Default value AUTO Force value NO
Step [-]
Description
This setpoint is designed for SW Key which unlocks premium features.
Note: The controller has to be power cycled after inserting the SW Key.
User Logging Record

Range [units] Enabled / Disabled
Default value Enabled Force value NO
Step [-]
Description
This setpoint enables recording of user login in/out to the controller history.
Example: The fallowing records will be shown in the history if enabled: User with user index (0)
loegged in via ETH.
Fuel Genset Consumption

Range [units] 0,0 .. 10 000,0 g/kWh
Default value 237,3 [g/kWh] Force value
Step 0,1 [g/kWh]
Description
Fuel consumed by the Gen-set per 1 kWh.

Subgroup:
Battery Undervoltage
Setpoint group BESS settings Related FW 1.3.0

Range [units] 8.0 V .. Battery Overvoltage (page 382) [V]
Default value 18.0 V Force value NO
Step 0.1 V
Description
Warning threshold for low battery/power supply voltage.
Battery Overvoltage

Range [units] Battery Undervoltage (page 382) .. 40.0 [V]
Default value 36.0 V Force value NO
Step 0.1 V
Description
Warning threshold for high battery/power supply voltage.
Battery <> Voltage Delay

Default value 5s Force value NO
Step 1s
Description
Delay for which battery/power supply voltage can be out of range given by setpoints Battery
Undervoltage (page 382) and Battery Overvoltage (page 382). After this delay elapses, appropriate
alarm (Wrn Battery Undervoltage (page 1085) or Wrn Battery Overvoltage (page 1084)) is
activated.

Subgroup: Pulse counters
Conversion Coeff. Fast Pulse 1

Range [units] OFF / 0 .. 65000 [-]
Default value OFF Force value YES
Step 1 [-]
Description
This setpoint adjusts the rate of increasing of the Fast Pulse Counter 1 (page 775) which is physically
configured to binary input 9.
Set this setpoint to OFF to turn the function off. See the chapter Pulse Counters (page 211) for more
information.
Conversion Coeff. Fast Pulse 2

Range [units] OFF / 0 .. 65000 [-]
Step 1 [-]
Description
This setpoint adjusts the rate of increasing of the Fast Pulse Counter 2 (page 775) which is physically
configured to binary input 10.
information.

Conversion Coefficient Pulse 1

Range [units] OFF / 0 .. 65000 [-]
Step 1 [-]
Description
This setpoint adjusts the rate of increasing of the "slow" Pulse Counter 1 (page 776) which is connected
with LBI PULSE COUNTER 1 (PAGE 908).
information.
Conversion Coefficient Pulse 2

Range [units] OFF / 0 .. 65000 [-]
Step 1 [-]
Description
This setpoint adjusts the rate of increasing of the "slow" Pulse Counter 2 (page 776) which is connected
with LBI PULSE COUNTER 2 (PAGE 908).
information.

Group: Communication Settings
Subgroup: Controller Address
CAN Controller Address
Communication
Setpoint group Related FW 1.3.0
Settings
Range [units] 1 .. 64 [-]
Step 1 [-]
Description
This setpoint adjusts Controller's CAN Address which is used for CAN Intercontroller Communication
(page 132).
This type of communication is used to share information between other ComAp controllers via CAN
interface (Communication peripherals (page 18)).
Note: Each controller connected via CAN has to have unique address, i.e. maximally 64 controllers
can be connected together.
Note: There is an exception, if the function Hot Swap Redundancy (page 160) is used, the Master
and Backup controllers has to have same address because they act like one controller unit for the
rest of the site.
Terminal Comm Address
Communication
Settings
Step 1 [-]
Description
This setpoint adjusts Controller’s Terminal Address which is used for communication with other devices
using terminals ETH1, ETH2, and RS485 (Communication peripherals (page 18)). This type of
communication is used fore remote or local connection of the computer (InteliConfig), Display, Modbus
Server, etc.

Subgroup: RS485 Settings
RS485 Modbus Speed
Communication
Settings
Range [units] 9600 / 19200 / 38400 / 57600 / 115200 [bps]
Default value 9600 bps Force value NO
Step [-]
Description
This setpoint adjusts communication speed ofModbus-RTU, Modbus/TCP (page 311).
RS485 Modbus Mode
Communication
Settings
Range [units] 8N1 / 8N2 / 8E1 [-]
Default value 8N1 Force value NO
Step [-]
Description
This setpoint adjusts communication mode of Modbus-RTU, Modbus/TCP (page 311).
Possible options
8N1 8 data bits, 1 stop bit, no parity
8N2 8 data bits, 2 stop bits, no parity
8E1 8 data bits, 1 stop bit, even parity

Subgroup: History Settings
LB/UART Log
Communication
Settings
Default value Disabled Force value NO
Step [-]
Description
This setpoint enables/disables logging of connection/disconnection of each remote terminal. The record
is written to the history.
Note: The terminal is disconnected automatically after 1 min of inactivity and next communication
request from the same terminal is considered as a new connection. When logging is enabled in
certain conditions the history may be filled up with large number of records related to the
communication and important record may be overwritten quite fast.
Disabled Logging is disabled.

Logging is enabled. Connection/Disconnection over ETH1, ETH2 or USB
(Communication peripherals (page 18)) causes history log.
Enabled
Note: Connection over USB is recognized after reading of/writing to a
communication object.

Subgroup: Intercontroller Settings
CAN Intercontroller Comm Redund
Communication
Settings
Step [-]
Description
This setpoint enables or disables CAN Intercontroller Communication Redundancy (page 132).
Note: In case that there is a mismatch between this setpoint and actual state of ⑦ CAN2B (page 47)
alarm ALI Redundant CAN Error (page 1107) is activated.

CAN Intercontroller Comm Mode
Communication
Settings
Range [units] 32C / 16C / 8C / 64C CAN FD / 32C CAN FD / 8C CAN FD [-]
Default value 8C Force value NO
Step [-]
Description
This setpoint selects the mode of intercontroller communication. Options 32C or 8C are necessary to use
in order to ensure the communication between InteliNeo6000 and older controllers such as IGS-NT,
IG2GSC, IG200, IG500. Options 64C CAN FD, 32C CAN FD and 8C CAN FD are compatible only with
controllers which support the CAN FD communication.
Note: It is strongly recommended to use CAN FD modes if all controllers on-site support the CAN FD
communication.
Mode Arbitration Bit-Rate Data Bit-Rate Maximal Bus Length Max Bus Length With Repeater
32C 250 kbit 250 kbit 200 m 800 m
16C 125 kbit 125 kbit 400 m 1600 m
8C 50 kbit 50 kbit 900 m 3600 m
64C CAN FD 250 kb 2 Mbit 200 m Not tested
32C CAN FD 125 kb 1 Mbit 400 m Not tested
8C CAN FD 50 kb 400 kbit 900 m Not tested
IMPORTANT: All controllers communicating on common CAN have to use the same mode of
this setpoint.
IMPORTANT: All changes made to the setpoint takes effect after the restart of the controller.
Note: In case that there is a mismatch between this setpoint and value CAN Intercontroller Comm
Mode (page 780), alarm ALI CAN Mode Inconsistency (page 1105) is activated.

CAN Intercontroller Empty Check
Communication
Settings
Step [-]
Description
This setpoint enable or disable CAN2 Intercontroller Empty Check.
Disabled Detection of CAN Intercontroller Empty Check is disabled.

Detection of CAN Intercontroller Empty Check is enabled. If controller does
Enabled not see any other controller on the⑧ CAN2A (page 47) or⑦ CAN2B (page
47) the Wrn CAN2 Empty (page 1085) will be activated.

Access Lock Mode
Communication
Settings
Range [units] Optional/ Required[-]
Default value Optional Force value NO
Step [-]
Description
Switching the Access Lock mode of operation so that the lock can be forced to be used to control the
controller.
Option Optional = Locking the lock does not condition the ability to operate the machine, it only allows
you to cut off other users if necessary.
Unlocked The controller can be controlled by anyone

Locked The controller can only be operated by the owner of the lock
Option Required = The lock is required for control, i.e. I have to lock with my account to control the
controller.
Unlocked No one can control the controller

Locked The controller can only be operated by the owner of the lock

Automatic Access Lock Release
Communication
Settings
Range [units] Disabled/ Enabled [-]
Step [-]
Description
Option to automatically unlock Access Lock if the owner of the lock is no longer logged into any active
session on the controller.
when the controller detects that the lock is locked but its owner is no longer
ENABLED
logged in any session, it automatically unlocks the lock
the lock remains locked regardless of whether the owner is logged in or not, it is
DISABLED
only unlocked manually (by the owner or administrator)
User sessions limit
Communication
Settings
Range [units] Disabled; 1 .. 10 [-]
Step [-]
Description
The number of concurrent sessions in which the same user is allowed to log in.
In the DISABLED state the controller behaves as it does in standard version, i.e. does not limit the
number of connections in which the same user is logged in. A user can log in with several connections at
the same time.
In the active state, each individual user can log into as many connections as is set by this setpoint.
Note: This feature does not apply to users in the administrator role and does not apply to the implicit
user.

Subgroup: SD Card Settings
SD Card File System
Communication
Settings
Range [units] Unmount / Mount / Format [-]
Default value Unmount Force value NO
Step [-]
Description
This setpoint determines whether the SD card is mounted, unmounted, or should be formatted. After
formatting, the setpoint is automatically switched to the mount option. If the setpoint is set to unmount no
interaction with the SD card is allowed, the controller will only detect that the SD card is inserted.
IMPORTANT: This setpoint has to be set to Mount in order to allow any writing function to
the SD card.
Long Term History
Communication
Settings
Step [-]
Description
This setpoint enables/disables writing of long term history onto the SD card.
Note: Setpoint SD Card File System (page 393) - has to be adjusted to Mount.
Disabled Long Term History is not written onto the SD card.

Enabled Long Term History is written onto the SD card.

Subgroup: CAN1 ECU/IO Modules Split
CAN1 ECU/IOModules Split
Communication
Settings
Range [units] Disabled/Enabled
Step -
Setpoint visibility When setpoint Hot Swap Redundancy (page 364) = Disabled
Description
This setpoint allows to change the behavior on CAN1 communication terminals.
By default, CAN1A terminal is used for communication with ECU and IO Modules, CAN1B terminal is
used for Hot Swap Redundancy (page 160). By enabling this setpoint, the CAN1A terminal can be
used only for ECU, the CAN1B can be used only for IO Modules.
Note: In case that CAN1 ECU/IOModules Split (page 394) is enabled, the Hot Swap Redundancy
(page 160) is disabled (and vice versa).

Group: Ethernet Port Configuration
Ethernet port 1
Ethernet Port
Configuration
Trusted Interface / Untrusted Interface / Modbus Interface / Trusted
Range [units]
Mirroring / Untrusted Mirroring / Modbus Mirroring [-]
Trusted
Interface
Step [-]
Description
This setpoint is used to select the interface type on ethernet slot 1.
Trusted Interface - It is expected that these interfaces are operated locally inside a closed
environment / infrastructure where additional measures against misuse or attack take place (e.g.
physical access limitation). Due to nature of this interface less strict cybersecurity rules apply at it and
that is why Implicit account is introduced here to make working with the controller simpler.
Untrusted Interface - This interface is a general-purpose one and it is expected that it may be
exposed to public networks, such as Internet, which are not under control of the entity operating the
controller. Thus, strict cybersecurity rules apply for this type of interface.
Modbus Interface - This type of interface is used for Modbus communication. It is not possible to
connect to the controller using this interface.
Trusted Mirroring/Untrusted Mirroring/Modbus Mirroring - If mirroring mode is selected for a
socket, the switch will be configured that except sending traffic belonging normally to that socket, it
will also copy to that socket all traffic from other sockets assigned to the same network.
Note: Only one socket can be adjusted to mirroring function. If multiple sockets are adjusted to
mirroring function the alarm ALI Ethernet Port Inconsistency will be still displayed after the CU restart.

Ethernet port 2
Ethernet Port
Configuration
Trusted Interface / Untrusted Interface / Modbus Interface / Trusted Mirroring /
Range [units]
Untrusted Mirroring / Modbus Mirroring [-]
Default value Trusted Interface Force value NO
Step [-]
Description
Modbus Interface - This type of interface is used for Modbus communication. It is not possible to

Ethernet port 3
Ethernet Port
Configuration
Trusted Interface / Untrusted Interface / Modbus Interface / Trusted Mirroring /
Range [units]
Untrusted Mirroring / Modbus Mirroring [-]
Default value Modbus Interface Force value NO
Step [-]
Description
Modbus Interface -This type of interface is used for Modbus communication. It is not possible to

Group: ETH Interface 1 - Trusted
Subgroup: TCP/IP Settings
IP Address Mode
ETH Interface 1 -
Trusted
Range [units] Manual / Automatic / Disabled [-]
Default value Automatic Force value YES
Step [-]
Description
This setpoint is used to select the method how the ethernet connection is adjusted on Ethernet 1 (page
19).
Manual: Manual: The Ethernet connection is fixed by means of the setpoints IP

Address (page 399), Subnet Mask (page 399), Gateway IP (page 400). This
method should be used for a classic Ethernet or internet connection. When this
type of connection opens, the controller is specified by its IP address. This
means that it would be inconvenient if the IP address were not fixed (static).
Automatic: The Ethernet connection settings is obtained automatically from the DHCP
server. The obtained settings is shown in related values. If the process of
obtaining the settings from the DHCP server is not successful, the values
000.000.000.000 are shown.
Disabled: The Ethernet terminal is disabled.
IMPORTANT: When the mode is switched from Automatic to Manual the TCP/IP settings
will be changed to the values in the related setpoints. In case you are using Ethernet 1 to
connect the CU you will be disconnected. Turn off the setpoint hiding function to
manually change the TCP/IP settings to same values obtained via DHCP so you will not be
disconnected when changing mode.

IP Address
ETH Interface 1 -
Trusted
Default value 192.168.1.1 Force value NO
Step [-]
Setpoint visibility Only if IP Address Mode (page 398) = Manual
Description
The setpoint is used to select the method how the IP Address is adjusted on Ethernet 1 (page 19).
If IP Address Mode (page 398) = Manual, this setpoint is used to adjust the IP address of the Ethernet
1 (page 19) interface of the controller. Ask your IT specialist for help with this setting.
If IP Address Mode (page 398) = Automatic this setpoint is inactive. The IP address is assigned by the
DHCP server.
Note: Only valid IP address can be inserted.
Subnet Mask
ETH Interface 1 -
Trusted
Step [-]
Description
The setpoint is used to select the method how the Subnet Mask is adjusted on Ethernet 1 (page 19).
If IP Address Mode (page 398) = Manual, this setpoint is used to adjust the Subnet Mask. Ask your IT
specialist for help.
If IP Address Mode (page 398) = Automatic this setpoint is inactive. The Subnet Mask is assigned by
the DHCP server.

Gateway IP
ETH Interface 1 -
Trusted
Step [-]
Description
This setpoint is used to select the method how the Gateway IP is adjusted on Ethernet 1 (page 19) .
If IP Address Mode (page 398) = Manual, this setpoint is used to adjust the IP address of the gateway
of the network segment where the controller is connected.
If IP Address Mode (page 398) = Automatic this setpoint is used to display the gateway IP which has
been assigned by the DHCP server.
A gateway is a device which connects the respective segment with the other segments and/or the
internet.
IP Firewall
ETH Interface 1 -
Trusted
Step [-]
Description
This setpoints enables or disables the built-in Firewall (page 157) functionality for Ethernet 1 (page
19).
Disabled: The firewall function is switched off

Enabled: The firewall function is switched on.
IMPORTANT: Loss of connection can happen when enabling the firewall and using remote
connection via Internet

Subgroup: SNMP Settings
SNMP Privacy Protocol
ETH Interface 2 -
Untrusted
Range [units] DES / 3DES / AES128 / AES256 [-]
Default value AES128 Force value NO
Step [-]
Setpoint visibility Only if SNMP Agent (page 416) = SNMP v3
Description
Selects SNMP v3 Privacy Protocol.
SNMP Authentication Protocol
ETH Interface 2 -
Untrusted
Range [units] MD5 / SHA / SHA256[-]
Default value SHA Force value NO
Step [-]
Description
Selects SNMP v3 Authentication Protocol.
SNMP Security Level
ETH Interface 2 -
Untrusted
Range [units] NONE/ AUTH-NOPRIV / AUTH-PRIV [-]
Default value NONE Force value NO
Step [-]
Description
Selects SNMP v3 security level. If NONE the agent will work in SNMP v2c mode..

Subgroup: Modbus Server Settings
Modbus Server
ETH Interface 1 -
Trusted
Step [-]
Description
This setpoint enables or disables Modbus communication via Ethernet 1 (page 19).
Modbus Client Inactivity Timeout
ETH Interface 1 -
Trusted
ETH Interface 2 -
Untrusted
ETH Interface 3 -
Modbus
Range [units] 0 .. 65535 [s]
Step 1s
Description
Modbus connection (TCP socket) is closed by controller, if a Modbus client does not communicate for
this time.
Note: This setpoint is shared with other Modbus Client Inactivity Timeout setpoints.

Subgroup: ComAp Client Settings
Direct Connection Port
ETH Interface 1 -
Trusted
Range [units] 0 .. 65535 [-]
Step 1 [-]
Description
This port is used to listen for an incoming TCP connection on Ethernet 1 (page 19).
ComAp Client Inactivity Timeout
ETH Interface 1 -
Setpoint group TrustedETH Interface 2 Related FW 1.3.0
- Untrusted
Range [units] 0 .. 65535 [s]
Step 1s
Description
Connection (TCP socket) is closed by controller, if a client (e.g. InteliConfig) does not communicate for
this time. This timeout applies to both direct and AirGate connection.
Note: This setpoint is shared with ComAp Client Inactivity Timeout (page 403).

Group: ETH Interface 2 - Untrusted
IP Address Mode
ETH Interface 2 -
Setpoint group Untrusted Related FW 1.3.0
Ethernet
Default value Automatic Force value NO
Step [-]
Description
19).
Manual: The Ethernet connection is fixed by means of the setpoints IP Address (page
405), Subnet Mask (page 405), Gateway IP (page 406), DNS IP Address 1
(page 407), DNS IP Address 2 (page 408). This method should be used for a
classic Ethernet or internet connection. When this type of connection opens,
the controller is specified by its IP address. This means that it would be
inconvenient if the IP address were not fixed (static).
000.000.000.000 are shown.
IMPORTANT: When the mode is switched from Automatic to Manual the TCP/IP settings
will be changed to the values in the related setpoints. In case you are using Ethernet 2 to
connect the CU you will be disconnected. Turn off the setpoint hiding function to
manually change the TCP/IP settings to same values obtained via DHCP so you will not be
disconnected when changing mode.

IP Address
ETH Interface 2 -
Untrusted
Step [-]
Description
DHCP server.
Subnet Mask
ETH Interface 2 -
Untrusted
Step [-]
Description
If IP Address Mode (page 404) = Manual this setpoint is used to adjust the Subnet Mask. Ask your IT
specialist for help with this setting.
the DHCP server.

Gateway IP
ETH Interface 2 -
Untrusted
Step [-]
Description
This setpoint is used to select the method how the Gateway IP is adjusted.
If IP Address Mode (page 404) = Manual, this setpoint is used to adjust the Gateway IP address of the
Ethernet 2 (page 19) interface of the controller. Ask your IT specialist for help with this setting.
If IP Address Mode (page 404) = Automatic this setpoint is inactive. The Gateway IP address is
assigned by the DHCP server.
A gateway is a device which connects the respective segment with the other segments and/or Internet.
IP Firewall
ETH Interface 2 -
Ethernet
Step [-]
Related
applications
Description
This setpoints enables or disables the built-in Firewall (page 157) functionality for Ethernet 2 (page
19).
Disabled: The firewall function is switched off

Enabled: The firewall function is switched on.
IMPORTANT: Loss of connection can happen when enabling the firewall and using remote
connection via Internet

DNS Mode
ETH Interface 2 -
Ethernet
Range [units] Manual / Automatic [-]
Default value Automatic Force value
Step [-]
Setpoint visibility Only if IP Address Mode (page 404) = Automatic
Description
This setpoint enables to enter DNS server addresses for Ethernet 2 (page 19) manually, even with the
IP Address Mode (page 404) set to Automatic.
Automatic: DNS server addresses are automatically obtained from a DHCP server.
DNS IP Address 1 (page 407) and DNS IP Address 2 (page 408) can be
adjusted manually. Use this option to resolve e.g. internet access policy related
Manual:
issue, if local DNS server addresses automatically obtained from a DHCP server
do not work
DNS IP Address 1
ETH Interface 2 -
Untrusted
Step [-]
Only if IP Address Mode (page 404) = Manual OR (IP Address Mode (page 404)
Setpoint visibility
= Automatic AND DNS Mode (page 407) = Manual)
Description
This setpoint allows to set DNS IP Address 1 for Ethernet 2 (page 19) manually.

DNS IP Address 2
ETH Interface 2 -
Untrusted
Step [-]
Only if IP Address Mode (page 404) = Manual OR (IP Address Mode (page 404)
Setpoint visibility
= Automatic AND DNS Mode (page 407) = Manual)
Description
This setpoint allows to set DNS IP Address 2 for Ethernet 2 (page 19) manually.
Subgroup: AirGate Settings
AirGate Connection
ETH Interface 2 -
Untrusted
Default value Enabled Force value YES
Step [-]
Description
This setpoint enables or disables AirGate connection (page 116) function.

AirGate Address
ETH Interface 2 -
Untrusted
Default value global.airgate.link Force value NO
Step [-]
Description
This setpoint is used for entering the domain name or IP address of the AirGate server. Use the free
AirGate server provided by ComAp at global.airgate.link.
AirGate Port
ETH Interface 2 -
Untrusted
Range [units] 0 .. 65535 [-]
Step 1 [-]
Description
This port is used for TCP communication with the AirGate server.
Note: Use port 5440 for standard ComAp AirGate service.

Subgroup: Messages Settings
Event Message
ETH Interface 2 -
Untrusted
Step [-]
Description
This setpoint enables or disables sending of Event Messages.
Wrn Message
ETH Interface 2 -
Untrusted
Step [-]
Description
This setpoint enables or disables sending of Warning Messages.

Sd Message
ETH Interface 2 -
Untrusted
CM-4G-GPS
Ethernet
Step [-]
Description
This setpoint enables or disables sending of Shutdown Messages.
E-mail Language
ETH Interface 2 -
Untrusted
Range [units] Depends on controller’s supported languages. [-]
Default value English Force value NO
Step [-]
Description
Use this setpoint to set the language of Event, Warning, etc. e-mails.

Time Zone
ETH Interface 2 -
Untrusted
Range [units] GMT-12:00 .. GMT+13:00 [hours]
Default value GMT+1:00 Force value YES
Step [-]
Description
This setpoint is used to select the time zone where the controller is located. See your computer time zone
setting (click on the time indicator located in the rightmost position of the Windows task bar) if you are not
sure about your time zone.
Note: If the time zone is not selected properly the active e-mails may contain incorrect information
about sending time, which may result in confusion when the respective problem actually occurred.
Subgroup: E-mail Settings
E-mail Address 1
ETH Interface 2 -
Untrusted
Range [units] 0..63 characters [-]
Default value [-] Force value NO
Step [-]
Description
Enter a valid e-mail address where event and alarm messages will be sent.

E-mail Address 2
ETH Interface 2 -
Untrusted
Step [-]
Description
E-mail Address 3
Setpoint group ETH Interface 2 - Untrusted Related FW 1.3.0

Step [-]
Description
E-mail Address 4
ETH Interface 2 -
Untrusted
Step [-]
Description

SMTP User Name
ETH Interface 2 -
Untrusted
Step [-]
Related
applications
Description
Use this setpoint to enter the username for the SMTP server. Leave the setpoint blank if the SMTP
server does not require authentication.
SMTP User Password
ETH Interface 2 -
Untrusted
Step [-]
Description
Use this setpoint to enter the password for the SMTP server. Leave the setpoint blank if the SMTP server
does not require authentication.

SMTP Server Address
ETH Interface 2 -
Untrusted
Default value global.airgate.link:9925 Force value NO
Step [-]
Description
This setpoint is used for entering the domain name (e.g. smtp.yourprovider.com) or IP address (e.g.
74.125.39.109) and port number (e.g. :9925) of the SMTP server. Ask your internet provider or IT
manager for this information.
Example: Enter the IP address "74.125.39.109" and port number "9925" as
"74.125.39.109:9925".
Note: You may use also any public SMTP server which does not require connection over SSL/TLS
channels.
SMTP Sender Address
ETH Interface 2 -
Untrusted
Step [-]
Description
Enter an existing email address into this setpoint. This address will be used as sender address in active
e-mails that will be sent from the controller.
Note: It is not needed to enter an existing email address, nevertheless valid email format needs to be
followed.
IMPORTANT: This item is obligatory when emails are configured.

SMTP Encryption Type
ETH Interface 2 -
Untrusted
Range [units] NONE / SSL/TLS / STARTTLS [-]
Default value NONE Force value NO
Step [-]
Description
This setpoint selects encryption type for SMTP session.
NONE Session is without of any encryption.

SSL/TLS Encrypted channel is created first and only after that session is created.
Session is created without of encryption and after command STARTTLS it
STARTTLS
is switched to encrypted session.
Subgroup: SNMP Settings
SNMP Agent
ETH Interface 2 -
Untrusted
Range [units] Disabled / SNMP v1/v2c / SNMP v3 [-]
Step [-]
Description
This setpoints Enables or disables Simple Network Management Protocol (SNMP) Agent.
Note: SNMP v3 has upgraded encryption, remote configuration, and security (extra setpoints are
available).
Note: It is supported only User-Based security model (USM, RFC-3414). View-based Access
Control Model (VACM, RFC-3415) is not supported.

SNMP Trap Format
ETH Interface 2 -
Untrusted
Range [units] v1 Trap / v2 Notific / v2 Inform [-]
Default value v2 Inform Force value NO
Step [-]
Setpoint visibility Only if SNMP Agent (page 416) != Disabled
Description
This setpoint selects format of the SNMP trap messages.
v1 Trap SNMPv1 trap format is used

v2 Notific SNMPv2c Notification format is used
v2 Inform SNMPv2c Inform format is used
SNMP RD Community String
ETH Interface 2 -
Untrusted
Default value public Force value NO
Step [-]
Description
SNMP Community String only for reading.

SNMP WR Community String
ETH Interface 2 -
Untrusted
Default value private Force value NO
Step [-]
Setpoint visibility Only if SNMP Agent (page 416) = SNMP v1/v2c
Description
SNMP Community String for writing and reading.
SNMP Traps IP Address 1
ETH Interface 2 -
Untrusted
Default value - Force value NO
Step [-]
Description
IP address 1 for receiving SNMP Traps. Leave this setpoint blank if SNMP traps should not be send.
SNMP Traps IP Address 2
ETH Interface 2 -
Untrusted
Range [units] Valid IP address [-]
Step [-]
Description
IP address 2 for receiving SNMP Traps. Leave this setpoint blank if SNMP traps should not be send.

SNMP Engine User Name
ETH Interface 2 -
Untrusted
Step [-]
Description
Defines SNMP v3 Engine User Name.
Subgroup: Modbus Server Settings
Modbus Server
ETH Interface 2 -
Untrusted
Step [-]
Description
Enables or disables Modbus communication via Ethernet 2 (page 19).

ETH Interface 1 -
Trusted
ETH Interface 2 -
Untrusted
ETH Interface 3 -
Modbus
Range [units] 0 .. 65535 [s]
Step 1s
Description
this time.
Subgroup: ComAp Client Settings
Direct Connection
ETH Interface 2 -
Untrusted
Step [-]
Description
Use this setpoint to enable/disable direct connection of a ComAp client (e.g. InteliConfig) to the IP
address of the controller.
Note: For Direct connection the controller IP address must be reachable from the client IP
address.

Direct Connection Port
ETH Interface 2 -
Untrusted
Range [units] 0 .. 65535 [-]
Step 1 [-]
Description
This port is used to listen for an incoming TCP connection on Ethernet 2 (page 19).
ComAp Client Inactivity Timeout
ETH Interface 1 -
Setpoint group TrustedETH Interface 2 Related FW 1.3.0
- Untrusted
Range [units] 0 .. 65535 [s]
Step 1s
Description
Connection (TCP socket) is closed by controller, if a client (e.g. InteliConfig) does not communicate for
this time. This timeout applies to both direct and AirGate connection.
Note: This setpoint is shared with ComAp Client Inactivity Timeout (page 421).

Subgroup: NTP Settings
NTP Clock Synchronization
ETH Interface 2 -
Untrusted
Step [-]
Description
This setpoint is used to enable/disable synchronization of the controller's time with the exact time from a
NTP server.
NTP Server
ETH Interface 2 -
Untrusted
Default value pool.ntp.org Force value NO
Step [-]
Description
NTP server address for time synchronization.
Note: Only valid IP address or domain can be inserted.
Group: ETH Interface 3 - Modbus
IP Address Mode
ETH Interface 3 -
Modbus
Default value Automatic Force value NO
Step [-]

Setpoint visibility Only if relevant module is installed
Description
19).
Manual: The Ethernet connection is fixed by means of the setpoints IP Address (page
423), Subnet Mask (page 423) and Gateway IP (page 424). This method
should be used for a classic Ethernet or internet connection. When this type of
connection opens, the controller is specified by its IP address. This means that
it would be inconvenient if the IP address were not fixed (static).
000.000.000.000 are shown.
IP Address
ETH Interface 3 -
Modbus
Step [-]
Description
DHCP server.
Subnet Mask
ETH Interface 3 -
Modbus

Step [-]
Description
If IP Address Mode (page 422) = Manual this setpoint is used to adjust the Subnet Mask. Ask your IT
specialist for help with this setting.
the DHCP server.
Gateway IP
ETH Interface 3 -
Modbus
Step [-]
Description
This setpoint is used to select the method how the Gateway IP is adjusted.
If IP Address Mode (page 422) = Manual, this setpoint is used to adjust the Gateway IP address of the
Ethernet 3 (page 19) interface of the controller. Ask your IT specialist for help with this setting.
If IP Address Mode (page 422) = Automatic this setpoint is inactive. The Gateway IP address is
assigned by the DHCP server.
A gateway is a device which connects the respective segment with the other segments and/or Internet.

Subgroup: Modbus Settings
Modbus Type
ETH Interface 3 -
Modbus
Range [units] Modbus Client / Modbus Server / Disabled [-]
Step [-]
Description
This setpoint enables the Modbus Client or Server on the Modbus Interface.
ETH Interface 1 -
Trusted
ETH Interface 2 -
Untrusted
ETH Interface 3 -
Modbus
Range [units] 0 .. 65535 [s]
Step 1s
Description
this time.
Group: BESS settings
Subgroup: Inverter Precharge Settings

BESS Precharge Type

Range [units] AC / DC [-]
Default value AC Force value YES
Step [-]
Description
This setpoint adjust Controller's behavior during BESS Precharge Sequence.
For more information see BESS Precharge Types on page 240
The BESS inverter cannot produce AC voltage on its output without being
connected to the healthy bus. The BESS must be precharged by AC voltage
AC Precharge
for time given by the setpoint Precharge Time (page 1). The BCB is allowed
to be closed only if the bus is helthy.
The BCB is allowed to be closed and connect healthy output of the BESS to
DC Precharge the dead bus. But If the bus is healthy and output of the BESS inverter is dead,
BCB cannot be closed.
BESSReady to Load TO

Step 1s
Description
This setpoint adjusts maximal waiting time for LBI BESS READY TO LOAD (PAGE 885) after the Prestart
Time (page 1) elapsed. If the LBI BESS READY TO LOAD (PAGE 885) is not configured the BCB is closed
after this timer elapsed.

Subgroup: BESS P Control
BESS P request source

Range [units] Analog/Setpoint/Balance
Step
Description
This setpoints defines the source for the BESS power output request.
See more information in the chapter BESS Charging/Discharging Control (page 235).
The controller receives a BESS P REQUEST (PAGE 984) from the LAI
Analog
BESS P REQUEST (PAGE 984) which is used as direct BESS Power Request.
The value of BESS P REQUEST (PAGE 984) is given by setpoints BESS Charge
Setpoint
Power (page 427) or BESS Discharge Power (page 428).
The BESS P REQUEST (PAGE 984) is calculated using internal controller's
Balance
algorithms. This calculation maintain the balance of energy flow trough the system.
BESS Charge Power

Range [units] 0 .. Nominal power (page 368) [kW]
Default value 100 kW Force value YES
Step 1 kW
Description
This setpoint defines the required charge power during the charging process. Charging process is
displayed as negative power.
Note: Note: The setpoint is inactive when LBI BATT DISCHARGE ENABLE (PAGE 879) is not active.


Range [units] 0 .. Nominal power (page 368) [kW]
Step 1 kW
Setpoint visibility Alwaysl
Description
This setpoint defines the required discharge power during the discharging process. Discharging process
is displayed as positive power.
Note: Note: The setpoint is inactive when LBI BATT DISCHARGE ENABLE (PAGE 879) is not active.
Gen P Min
Setpoint group Curtailment Related FW 1.3.0

Range [units] 0 .. 100 [%] of nominal power of Gen-sets running in PM
20 % of nominal power of
Gen-sets running in PM
Step 1 % of nominal power of Gen-sets running in PM
Description
In long term the Gen-sets have to operate on some minimal power level. This setpoint set the minimal
relative power level of Gen-sets working in power management.

Subgroup: BESS Q Control
BESS Q request source

Range [units] Analog/Balance
Default value Balance Force value YES
Step
Description
This setpoints defines the source which will be used for PF/Q regulations.
See more information in the chapter BESS/PV PF/Q Control (page 242).
The reactive power is regulated according to the the LAI BESS Q REQUEST (PAGE
Analog
984) which is used as direct BESS Power Request.
The PF of the BESS is regulated so the Gen-sets (system) has the constant PF
Balance
which is defined by the setpoint Gensets PF Required (page 429).
Gensets PF Required

Range [units] 0.001 .. 1.999
Default value 1.000 Force value YES
Step 0.001
Description
This setpoints defines the PF which is required from Gen-sets (system). The BESS will regulate its PF so
it covers peaks and the Gen-sets has constant PF.
Note: This setpoint applies only if the BESS Q request source (page 429) = Balance.

Subgroup: SOC Control
SOC High Target

Range [units] 50 .. 100 [%] of BESS Nominal Capacity (page 673)
80 % of BESS Nominal
Capacity (page 673)
Step 1 % of BESS Nominal Capacity (page 673)
Description
This setpoint defines the relative maximal state of charge of the BESS. The value BESS SOC (page
673) cannot exceed this limit.
See the chapter State of Charge (page 236) for more information.
SOC High Hysteresis

Capacity (page 673)
Description
This setpoint defines the relative level under which the value BESS SOC (page 673) must drop so the
charging process can be activated again .

SOC Low Target

Capacity (page 673)
Description
This setpoint defines the relative minimal state of charge of the BESS. The value BESS SOC (page 673)
cannot drop under this limit.
SOC Low Hysteresis

Capacity (page 673)
Description
This setpoint defines the relative level under which the value BESS SOC (page 673) must exceed so the
discharging process can be activated again .

Subgroup: Battery Cycles
Max Battery Cycles Per Day

Range [units] OFF; 1 .. 250 [-]
Default value 2 Force value YES
Step 1
Description
This setpoint is used to define the maximal daily number of battery cycles.
See the chapter Daily Battery Cycles Control (page 237) for more information.
Subgroup: Starting Timers
Minimal Stabilization Time

Range [units] 1 .. Maximal Stabilization Time (page 433) [s]
Default value 2s Force value YES
Step 1s
Setpoint visibility Only if BESS Precharge Type (page 426) = DC
Description
After the BESS has been started. The controller will wait for a period adjusted by this setpoint before
closing BCB, even if the BESS voltage and frequency are already in limits.
Note: This setpoint is relevant only if BESS Precharge Type (page 426) = DC.

Maximal Stabilization Time

Range [units] Minimal Stabilization Time (page 432) .. 3600 [s]
Step 1s
Setpoint visibility Only if BESS Precharge Type (page 426) = DC
Description
After the BESS has been started. The BESS voltage and frequency must get within limits within this
period of time, otherwise an appropriate shutdown alarm (BESS voltage and/or frequency) is issued.
Note: This setpoint is relevant only if BESS Precharge Type (page 426) = DC.

Run Only Block Delay 1

Range [units] 0.0 .. 600.0 [s]
Step 0.1
Related
applications
Description
This setpoint influences the blocking condition if any protection is configured with blocking condition "Run
Only Block Delay 1". The protection blocking is based on the operating state of the BESS state machine.
Once the BESS state machine reaches the "Running" state, the protection with this blocking is unblocked
after this delay elapses.
Image 7.3 Run Only Block Delay 1


Range [units] 0.0 .. 600.0 [s]
Step 0.1
Description


Range [units] 0.0 .. 600.0
Step 0.1
Description
Subgroup: Stopping Timers
Stop Time

Step 1s
Description
Under normal conditions the BESS must certainly stop within this period.

Subgroup: Power Switch
Power Switch On

MINT,
MPTM
Setpoint visibility Only if LBO POWER SWITCH (PAGE 967) is configured
Description
Threshold level for switching the LBO POWER SWITCH (PAGE 967) on.
Power Switch Off

MINT,
MPTM
Setpoint visibility Only if LBO POWER SWITCH (PAGE 967) is configured
Description
Threshold level for switching the LBO POWER SWITCH (PAGE 967) off.
Group: BESS Protections
Subgroup: Overload Protection
2POverload Start Evaluation Level
Setpoint group BESS Protections Related FW 1.3.0

Range [units] 100 .. 200 [%] of Nominal power (page 368)
120 % of Nominal
power (page 368)
Step 1 % of Nominal power (page 368)

Description
This setpoint adjusts the relative power level, where the thermal overload protection starts to be
evaluated. See setpoint IDMT Overload Protection (page 561)for complete explanation of the
protection.
Load Reaction time

level [s] 2POvrldStEvDel 5s
100 no reaction OverldStrtEval 120 %
110 no reaction
120 600
130 60
140 30
150 20
160 15
170 12
180 10
190 8.6
200 7.5
210 6.7
220 6
230 5.5
240 5
250 4.6
The reaction time of the thermal overload protection is not fixed and is specified by the parameter
2POverload Start Evaluation Delay (page 438).
Note: Maximum reaction time is 3600 s after this time the protection is tripped.
2POverload Start Evaluation Delay

Range [units] 0.1 .. 600.0 [s]
Default value 5.0 s Force value YES
Step 0.1 s
Description
This setpoint adjusts the default delay for the thermal overload protection. See setpoint IDMT Overload

Protection (page 561) for complete explanation of the protection.
Load Reaction time

level [s]
2POvrldStEvDel 5s
100 no reaction
OverldStrtEval 120 %
110 no reaction
3600 (max.
120
value)
130 60
140 30
150 20
160 15
170 12
180 10
190 8.6
200 7.5
210 6.7
220 6
230 5.5
240 5
250 4.6
The reaction time of the thermal overload protection is not fixed; it depends on how much is the load
above the limit of 2POverload Start Evaluation Level (page 437). The higher is the load the shorter
the reaction time will be.
Subgroup: Current Protection
Short Circuit

Range [units] 100 .. 500 [%] of Nominal Current (page 369)
150 % of Nominal Current (page
369)
Step 1 % of Nominal Current (page 369)
Description
This setpoint specifies the relative current threshold level for Short Circuit Protection (page 562).

Short Circuit Delay

Range [units] 0.00 .. 10.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for Short Circuit Protection (page 562).
IDMT BESS >A Delay

Range [units] 1.0 .. 600.0 [s]
Default value 4.0 s Force value NO
Step 0.1 s
Description
This setpoint adjusts the delay for IDMT BESS >A Protection (page 562).
IDMT curve shape selection. IDMT Overcurrent Delay is a reaction time of IDMT protection for 200%
overcurrent IBESS =2*Nominal Current (page 369)
IDMT is “very inverse” over current protection. Reaction time is not constant but depends on over current
level according to the following formula:
Note: Reaction time is limited to 3600 s = 60 minutes. IDMT protection is not active for Reaction time
values longer than 60 minutes.
IBESS is maximal value of all measured phases of BESS current.

Table 7.1 EXAMPLE of Reaction time for different over current levels
Overcurrent
Overcurrent IDMT Delay
≤ 100 % 101 % 110 %
0,2 s No action 20 s 2s
Reaction time 2s No action 200 s 20 s
20 s No action 2000 s 200 s

Image 7.6 IDMT Overcurrent Delay
BESS Current Unbalance

50 % of Nominal
power (page 368)
Setpoint visibility Only if Connection type (page 371) != MonoPhase
Description
This setpoint specifies the relative current threshold level for BESS Current Unbalance Protection
(page 564).
BESS Current Unbalance Delay

Range [units] 0.0 .. 600.0 [s]
Default value 5.0 s Force value NO
Step 0.1 s
Description
This setpoint specifies the delay for BESS Current Unbalance Protection (page 564).

Subgroup: Voltage Protection
BESS >V

Enabled / Disabled / Protection Force Disable 1 / Protection Force Disable 2 /
Range [units]
Protection Force Disable 3 [-]
Step [-]
Description
This setpoint enables or disables BESS >V Protection.
Protection is enabled. Behavior of protection is adjusted via setpoints BESS >VUndervoltage (page 1)
and BESS >V Delay (page 443). When BESS voltage exceeds limit set by BESS >VUndervoltage
(page 1) for time longer than BESS >V Delay (page 443) appropriate alarm is activated.
Value Alarm
BESS Voltage L1-N (page 670) Sd BESS >V L1-N (page 1117)
BESS Voltage L1-L2 (page 670) Sd BESS >V L1-L2 (page 1117)
Setpoint options:
Enabled / Disabled: Protection is enabled / disabled.
Protection Force Disable 1 / 2 / 3: Protection is enabled or disabled by the state of LBI
PROTECTION FORCE DISABLE 1 (PAGE 906) / PROTECTION FORCE DISABLE 2 (PAGE 907) /
PROTECTION FORCE DISABLE 3 (PAGE 907).
IMPORTANT: If this protection is disabled, the BCB cannot be closed.

BESS >V Delay

Range [units] 0.01 .. 600 [s]
Step 0.01 s
Description
This setpoint specifies the delay for BESS >V (page 565).
BESS >>V

Generator >V (page 1) .. 150 [%] of BESS Nominal Voltage Ph-N (page 373)
Range [units]
and BESS Nominal Voltage Ph-Ph (page 373)
150 % of BESS Nominal Voltage Ph-N
Default value (page 373) and BESS Nominal Force value YES
1 % of BESS Nominal Voltage Ph-N (page 373) and BESS Nominal Voltage
Step
Ph-Ph (page 373)
Description
This setpoint specifies the relative voltage threshold level for BESS >>V Protection (page 566).
Note: BESS Voltage L1-N (page 670), BESS Voltage L2-N (page 670), BESS Voltage L3-N
(page 670), BESS Voltage L1-L2 (page 670), BESS Voltage L2-L3 (page 671) and BESS
Voltage L3-L1 (page 671) are used for this protection.

BESS >>V Delay

Range [units] 0.01 .. 600 [s]
Step 0.01 s
Description
This setpoint specifies the delay for BESS >>V Protection (page 566).
BESS <V

20 .. 99 [%] of BESS Nominal Voltage Ph-N (page 373) and BESS Nominal
Range [units]
90 % of BESS Nominal Voltage Ph-N
Default value (page 373) and BESS Nominal Force value YES
1 % of BESS Nominal Voltage Ph-N (page 373) and BESS Nominal Voltage
Step
Ph-Ph (page 373)
Description
This setpoint specifies the relative voltage threshold level for BESS <V Protection (page 567).
Note: BESS Voltage L1-N (page 670), BESS Voltage L2-N (page 670), BESS Voltage L3-N
(page 670), BESS Voltage L1-L2 (page 670), BESS Voltage L2-L3 (page 671) and BESS
Voltage L3-L1 (page 671) are used for this protection.

BESS <V Delay

Range [units] 0.01 .. 600.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for BESS <V Protection (page 567).
BESS V Unbalance

Range [units] 1 .. 200 [%]
Default value 10 % Force value YES
Step 1%
Description
This setpoint specifies the relative voltage threshold level for BESS V Unbalance Protection (page
567).
BESS V Unbalance Delay

Range [units] 0.01 .. 600.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for BESS V Unbalance Protection (page 567).

Subgroup: Frequency Protection
BESS >f

Range [units] 0.00 .. 5.00 [Hz]
Default value 1.50 Hz Force value YES
Step 0.01 Hz
Description
This setpoint adjusts maximal accepted frequency for BESS >f Protection (page 575).
IMPORTANT: When Application Mode (page 777) = MINT this setpoint also specifies the
maximal accepted frequency for Bus >f Protection.
Note: fmax = Nominal Frequency (page 377) + BESS >f
BESS >f Delay

Range [units] 0.01 .. 600.0 [s]
Step 0.01 s
Description
This setpoint specifies the delay for BESS >f Protection (page 575).
maximal accepted frequency for Bus >f Protection.

BESS <f

Range [units] 0.00 .. 5.00 [Hz]
Step 0.01 Hz
Description
This setpoint adjusts maximal accepted frequency for BESS <f Protection (page 576).
maximal accepted frequency for Bus <f Protection.
Note: fmin = Nominal Frequency (page 377) - BESS <f
BESS <f Delay

Range [units] 0.01 .. 600.0 [s]
Step 0.01 s
Description
This setpoint specifies the delay for BESS <f Protection (page 576).
maximal accepted frequency for Bus <f Protection.

Subgroup: Bus Meas Error
Bus Meas Error

Range [units]
Step [-]
Description
This setpoint enables or disables Bus Measurement Error protection.
Alarm Stp Bus Meas Error (page 1124) is activated if controller detects a mismatch between the
expected and currently measured voltage on the bus for period longer than 20 s. Mismatch means that
measured voltage is lower/higher than Bus Dead Level (page 376), although the controller receives
information about closed/opened breaker.
Setpoint options:
Enabled / Disabled : Protection is enabled / disabled .
Subgroup: Earth Fault Current Protection
IDMT Earth Fault Current Sd

Range [units] 0 .. 1000 [A]
Default value 10 A Force value YES
Step 1 [A]
Description
This setpoint specifies the current threshold level for Earth Fault Current Protection (page 583).

IDMT Earth Fault Current Delay

Range [units] 0.1 .. 600.0 [s]
Step 0.1 s
Description
This setpoint specifies the delay for Earth Fault Current Protection (page 583).
Subgroup: SOC Protection
BESS <f Delay

Range [units] SOC Critical Low (page 450) .. 50 [%] of BESS Nominal Capacity (page 673)
Default value 10 % of BESS Nominal Capacity (page 673) Force value YES
Related MINT,
Comm object 20263
applications MPTM
Description
This setpoint specifies the relative state of charge threshold level for BESS <SOC Protection (page
589).

SOC High Alarm

Range [units] 50 .. SOC Critical High (page 451) [%] of BESS Nominal Capacity (page 673)
90 % of
Default value BESS Nominal Force value YES
Capacity (page 673)
Description
This setpoint specifies the relative state of charge threshold level for BESS >SOC Protection (page
589).
SOC Critical Low

Range [units] 0 .. BESS <f Delay (page 449) [%] of BESS Nominal Capacity (page 673)
Related MINT,
Comm object 20261
applications MPTM
Description
This setpoint specifies the relative state of charge threshold level for BESS <<SOC Protection (page
590).

SOC Critical High

Range [units] SOC High Alarm (page 450) .. 120 [%] of BESS Nominal Capacity (page 673)
Related MINT,
Comm object 20262
applications MPTM
Description
This setpoint specifies the relative state of charge threshold level for BESS >>SOC Protection (page
590).
Group: PV Settings
Subgroup: PF Control
PV Power Factor Request
Setpoint group PV Related FW 1.3.0

Range [units] 0.001 .. 1.999
Step 0.001
Description
Required power factor of the PV in parallel to mains operation.

Subgroup: PV Areas
PV Array Area 1

2
Range [units] 0 .. 32000 [m ]
Step 1
Description
Defines the area and target energy output for the PV array 1 and is associated with the LAI: IRRADIATION
OF PV ARRAY 1 (PAGE 990).
PV Array Area 2

2
Range [units] 0 .. 32000 [m ]
Step 1
Description
PV Array Area 3

2
Range [units] 0 .. 32000 [m ]
Step 1
Description

PV Array Area 4

2
Range [units] 0 .. 32000 [m ]
Step 1
Description
Subgroup: PV Calibration Offset
PV Calib. Offset 1

Range [units] -32000 .. 32000 [kW]
Step 1
Description
This parameter represents the correction offset for PV Array 1 in kilowatts (kW). The value of this
correction can be either positive or negative and is used to correct the output of PV Array 1.
PV Calib. Offset 2

Range [units] -32000 .. 32000 [kW]
Step 1
Description

PV Calib. Offset 3

Range [units] -32000 .. 32000 [kW]
Step 1
Description
PV Calib. Offset 4

Range [units] -32000 .. 32000 [kW]
Step 1
Description
Group: WT Settings
Subgroup: PF Control
WT Power Factor Request
Setpoint group WT Settings Related FW 1.3.0

Range [units] 0.001 .. 1.999
Step 0.001
Description
Required power factor of the WT in parallel to mains operation.

Group: Curtailment
Subgroup: Curtailment
Curtailment

Range [units] Enabled/Disabled
Step
Description
This setpoints enables the function PV Curtailment (page 290) used to regulate power of the PV
according to the PI regulation loop when the actual power of Gen-sets goes below Gen P Min (page
456).
Gain

Range [units] 0,0 .. 200,0 [-]
Default value 10,00 Force value YES
Step 0,01
Description
This setpoints adjust the gain factor of PI curtailment regulation.

Int

Range [units] 0,10 .. 60,00 [-]
Default value 10,00 s Force value YES
Step 0,01 s
Description
This setpoints adjust the int factor of PI curtailment regulation.
Gen P Min

Range [units] 0 .. 100 [%] of nominal power of Gen-sets running in PM
20 % of nominal power of
Gen-sets running in PM
Step 1 % of nominal power of Gen-sets running in PM
Description
In long term the Gen-sets have to operate on some minimal power level. This setpoint set the minimal
relative power level of Gen-sets working in power management.
Subgroup: PW/WT Ramp
PV/WT Ramp Up

Range [units] OFF; 1 .. 1800 [s]
Step 1
Description
Defines the maximal rate of rise of the value Curtailment Output.

PV/WT Ramp Down

Range [units] OFF; 1 .. 1800 [s]
Step 1
Description
Defines the maximal rate of fall of the value Curtailment Output.
Group: Frequency/Load Control
Subgroup: Frequency Control
Frequency Regulator Character
Setpoint group Speed/Load Control Related FW 1.3.0

Range [units] Positive / Negative [-]
Default value Positive Force value YES
Step [-]
Description
This setpoint selects the characteristic of the Frequency Regulator Output (page 754). Adjust it
according to the behavior of the BESS inverter.
Raising the voltage on the BESS inverter regulator causes BESS frequency
Positive
to rise.
Raising the voltage on the BESS inverter regulator causes BESS frequency
Negative
to go down.

Frequency Governor Bias

Frequency Governor Low Limit (page 458) .. Frequency Governor High Limit
Range [units]
(page 458) [-]
Default value 0,00 V Force value YES
Step 0,01 V
Description
This setpoint adjusts the initial voltage level for the Frequency Regulator Output (page 754). This level
is present on the output, if no speed or power regulation loop is active.
Frequency Governor Low Limit

Range [units] -10,00 .. Frequency Governor High Limit (page 458) [V]
Default value -10,00 V Force value YES
Step 0,01 V
Description
The low limit of the Frequency Regulator Output (page 754).
Use this setpoint to adjust the regulator output range according to your BESS inverter regulator.
Frequency Governor High Limit

Range [units] Frequency Governor Low Limit (page 458) .. 10,00 [V]
Step 0,01 V
Description
Upper limit of the speed Frequency Regulator Output (page 754).
Use this setpoint to adjust the regulator output range according to your BESS inverter regulator.

Tau Frequency Governor Actuator

Range [units] 1,0 .. 300,0 [s]
Step 0,1 s
Description
This setpoint is used to adjust the transformation ratio of the Frequency Regulator Output (page 754)
to the pulses at the binary outputs FREQUENCY UP (PAGE 950) and FREQUENCY DOWN (PAGE 950).
Adjust the setpoint to the pulse duration which is needed for the regulator of BESS inverter to
regulatefrom minimal position to the maximal position.
BESS Frequency Droop Slope
Frequency/Load
Control
Range [units] 0 .. 20 [%]
Default value 2 Force value NO
Step 0.01
Description
This setpoint defines the slope of the load droop correlation. The slope is set as a droop of frequency in
percentages of the requested system frequency (Nominal Frequency (page 377)) on the range of the
requested power from 0 to 100% of Nominal power (page 368).

Subgroup: Regulation Loops
Frequency Regulation Loop

Range [units] Sync Only / All The Time [-]
Default value Sync Only Force value YES
Step [-]
Description
This setpoint selects when the frequency regulation loop is active.
SYNC ONLY: The frequency regulation loop is active only during synchronizing to match the
BESS, Mains, or Bus frequencies together. It is assumed that in all other situations where the
frequency is to be regulated the BESS governor maintains itself.
ALL THE TIME: This option activates the frequency regulation loop also while the BESS is
running without load and during the island operation. The controller maintains frequency at its
nominal value adjusted by setpoint Nominal Frequency (page 377).
Note: See the chapter Regulation Loops (page 290) for more information.
Frequency Gain

Range [units] 0,00 .. 200,00 [-]
Default value 10,00 [-] Force value YES
Step 0,01 [-]
Description
This setpoint adjusts the gain factor (P-factor) of the frequency control PI loop.

Frequency Int

Range [units] 0,10 .. 60,00 [s]
Default value 2,00 [s] Force value YES
Step 0,01 [s]
Description
This setpoint adjusts the integration factor (I-factor) of the frequency control PI loop.
Angle Gain

Range [units] 0,00 .. 200,00 [-]
Step 0,01 [-]
Description
This setpoint is used for adjusting of the gain factor (P-factor) of the phase angle P-control loop.
Note: During synchronization, first the frequency loop is started to match the BESS frequency with
the Mains or bus and after that the phase angle loop is started to match the phase angle.

Load Gain

Range [units] 0,00 .. 200,00 [-]
Step 0,01 [-]
Description
This setpoint adjusts the gain factor (P-factor) of the load control PI loop.
Load Int

Range [units] 0,10 .. 60,00 [s]
Step 0,01 [s]
Description
This setpoint adjusts the integration factor (I-factor) of the load control PI loop.

Load Sharing Gain

Range [units] 0,00 .. 200,00 [-]
Step 0,01 [-]
Description
This setpoint adjusts the gain factor (P-factor) of the load sharing control PI loop.
Load Sharing Int

Range [units] 0,10 .. 60,00 [s]
Step 0,01 [s]
Description
This setpoint adjusts the integration factor (I-factor) of the load sharing control PI loop.

Subgroup: Load Transfer
Close Transfer Max Duration

Range [units] < 0,1 = 0,0; 0,1 .. 600,0 [s]
Step 0,1 s
Description
The time of parallel work of BESS and Mains in close transition. Physical time of close transfer is always
longer than this setpoint (it takes time to detect the closing of the breaker, etc.).
Open Transfer Min Break

Range [units] < 0,1 = 0,0; 0,1 .. 600,0 [s]
Step 0,1 s
Description
Minimal duration of break in open transition when Transfer BESS To Mains (page 466) or Transfer
Mains To BESS (page 465) is chosen as open transfer.

Transfer Mains To BESS

Range [units] Open / Close Only / Close Prim / SoftTransf [-]
Default value SoftTransf Force value YES
Step [-]
Description
This setpoint defines the type of transfer of load from Mains to BESS.
Transfer of the load from Mains to BESS without parallel work and
synchronization (one breaker opens and second is closed - checking
Open
feedbacks). The setpoint Open Transfer Min Break (page 464) sets the
minimal duration of break.
Transfer of the load from Mains to BESS with synchronization and parallel
work. The time of parallel work is given by setpoint Close Transfer Max
Close Only
In case of synchronization fail, MCB stays close and BESS is stopped.
Transfer of the load from Mains to BESS with synchronization and parallel
Close Prim
Transfer of the load from Mains to BESS with parallel work and soft loading of
the BESS. This function is proceeded like the closed transfer, but there is time
limitation of loading of theBESS adjusted via setpoint Load Ramp (page
SoftTransf
468). The transfer is succeed only when theBESS is fully loaded – Mains is
fully unloaded (level of load when Mains is considered as unloaded is adjusted
via setpoint Mains Unload MCB Open Window (page 467)).
Note: Close transfer of load is also affected by setpoint Mains Measurement P (page 357).
Note: The behavior of transition of load in MAN mode is adjusted via setpoint CB Control In MAN
Mode (page 355).

Transfer BESS To Mains

Range [units] Open / Close Only / Close Prim / SoftTransf [-]
Default value SoftTransf Force value YES
Step [-]
Description
This setpoint defines the type of transfer of load from BESS to Mains.
Transfer of the load from BESS to Mains without parallel work and
synchronization (one breaker opens and second is closed - checking
Open
feedbacks). The setpoint Open Transfer Min Break (page 464) sets the
minimal duration of break.
Transfer of the load from BESS to Mains with synchronization and parallel
Close Only
In case of synchronization fail, BCB stays closed and BESS keeps running.
Transfer of the load from BESS to Mains with synchronization and parallel
Close Prim
Transfer of the load from BESS to Mains with parallel work and soft unloading
of the BESS. This function is proceeded like the closed transfer, but there is
time limitation of unloading of the BESS adjusted via setpoint Load Ramp
SoftTransf
(page 468). The transfer is succeed only when the BESS is fully unloaded
(level of load when BESS is considered as unloaded is adjusted via setpoint
Generator Unload BCB Open Level (page 467)).
Note: The behavior of transition of load in MAN mode is adjusted via setpoint CB Control In MAN
Mode (page 355).

Generator Unload BCB Open Level

Range [units] 0 .. 100 [%] of Nominal power (page 368) or Installed Power (page 368)
10 % of Nominal power (page 368) or
Installed Power (page 368)
Step 1 % of Nominal power (page 368) or Installed Power (page 368)
Comm object 8547 Related applications MINT, , SPTM
Description
This setpoint adjusts the required value of the BESS P (page 664) related to Nominal power (page
368)/Installed Power (page 368) for opening the BCB breaker during unloading of the BESS.
Note: This setpoint is usually higher than 0 to prevent the BESS going to reverse power.
Note: The value of this setpoint relates to Installed Power (page 368) only if Installed Power
(page 368) != OFF, otherwise it relates to Nominal power (page 368).
Mains Unload MCB Open Window

Default value 1 % of Nominal power (page 368) Force value YES
Description
This setpoint adjusts the value which defines the level where the Mains is considered as unloaded. When
this window is reached and it is required to open MCB, the MCB will be opened and remaining load in the
window will be transfer to BESS.
IMPORTANT: If the window is set too high the Mains can be considered as unloaded
and MCB will be opened while there is not enough reserve power on BESS. This can
cause overload of BESS and blackout.
IMPORTANT: This window and the setpoint Minimal Power PTM (page 1) must be set in
the way where MCB opening will not be blocked by Minimal Power PTM level while all
available BESSs are running in Load Shar.
Note: This setpoint is window. It means that when you adjust this setpoint to 10%, there is window
from -10% to +10%. The reason is Import/Export function.

Load Ramp

Step 1s
Description
This setpoint adjusts the ramping time of BESS Required P (page 753) to BESS Required P Target
(page 753) while loading/unloading.
The ramping time is set for ΔP which is given by the setpoint Installed Power (page 368) or by the
setpoint Nominal power (page 368) if the Installed Power is OFF.
Example: Installed Power (page 368) = 20 kW, Load Ramp = 10 seconds. The ramp is changing
with speed 20 kW per 10 seconds (2 kW/s) to the zero value.

Ramp Start Level

Range [units] 0 .. 100 [%] of Nominal power (page 368) or Installed Power (page 368)
0 % of Nominal power (page 368)
or Installed Power (page 368)
Step 1 % of Nominal power (page 368) or Installed Power (page 368)
Description
This setpoint adjusts the load level at which the Load Ramp (page 468) starts after the BCB has been
closed.

Soft Unload Ramp

Step 1s
Description
This setpoint adjusts the ramping time of the BESS Required P (page 753) to the BESS Required P
Target (page 753) while soft unloading when BCB is requested to be opened.
The Required P reach the zero value at the end of the timer. The ramping time is set for ΔP which is given
by the setpoint Installed Power (page 368) or by the setpoint Nominal power (page 368) if the
Installed Power is OFF.
Example: Installed Power (page 368) = 20 kW, Soft Unload Ramp = 10 seconds. The ramp is
changing with speed 20 kW per 10 seconds (2 kW/s) to the zero value.
Note: This setpoint is shared with Soft Unload Ramp (page 559)
Group: Voltage/PF Control
Subgroup: Voltage Control
Voltage Regulator Character
Setpoint group Voltage/PF Control Related FW 1.3.0

Range [units] Positive / Negative [-]
Default value Positive Force value YES
Step [-]
Description
This setpoint selects the characteristic of the Voltage Regulator Output (page 758). Adjust it according
to the behavior of the remote voltage input of the governor.
Raising the voltage on the remote voltage adjustment input causes the BESS
Positive
voltage to raise.
Raising the voltage on the remote voltage adjustment input causes the BESS
Negative
voltage to go down.

Voltage Regulator Bias

Voltage Regulator Low Limit (page 471) .. Voltage Regulator High Limit (page
Range [units]
471) [V]
Step 0,01 V
Description
This setpoint adjusts the initial level for the Voltage Regulator Output (page 758). This level is present
on the output if no regulation loop is active.
Voltage Regulator Low Limit

Range [units] -10,00 .. Voltage Regulator High Limit (page 471) [V]
Default value -10,00 V Force value YES
Step 0,01 V
Description
Lower limit of the Voltage Regulator Output (page 758). Use this setpoint to adjust the governor output
range according to your governor type.
Voltage Regulator High Limit
Setpoint group Synchronization Related FW 1.3.0

Range [units] Voltage Regulator Low Limit (page 471) .. 10,00 [V]
Step 0,01 V
Description
Upper limit of the Voltage Regulator Output (page 758). Use this setpoint to adjust the governor output
range according to your governor type.

Tau Voltage Regulator Actuator

Range [units] 1,0 .. 300,0 [s]
Step 0,1 s
Description
This setpoint is used to adjust the transformation ratio of the Voltage Regulator Output (page 758) to
the pulsesat the binary outputs VOLTAGE UP (PAGE 979) and VOLTAGE DOWN (PAGE 978).
Adjust the setpoint to the pulse duration which is needed for the regulator of BESS inverter to
regulatefrom minimal position to the maximal position.
BESS Voltage Droop Slope
Frequency/Load
Control
Range [units] 0 .. 20 [%]
Default value 1 Force value NO
Step 0.001
Description
This setpoint defines the slope of the droop correlation. The slope is set as a droop of voltage in
percentages of the generator nominal voltage (BESS Nominal Voltage Ph-N (page 373)) on the range
of the requested reactive power from 0 to 100% of nominal reactive power (value of nominal reactive
power is not given by setpoint but it is calculated from setpoint BESS Nominal Voltage Ph-Ph (page
373) whilst the PF=0,8).

Subgroup: Regulation Loops
Voltage Gain

Range [units] 0.00 .. 200.00 [-]
Default value 10.00 [-] Force value YES
Step 0.01 [-]
Description
This setpoint adjusts the gain factor (P-factor) of the voltage control PI loop.
Voltage Int

Range [units] 0.10 .. 60.00 [s]
Default value 2.00 [s] Force value YES
Step 0.01 [s]
Description
This setpoint adjusts the integration factor (I-factor) of the voltage control PI loop.

PF Gain

Range [units] 0.00 .. 200.00 [-]
Step 0.01 [-]
Description
This setpoint adjusts the gain factor (P-factor) of the PF control PI loop.
PF Int

Range [units] 0.10 .. 60.00 [s]
Step 0.01 [s]
Description
This setpoint adjusts the integration factor (I-factor) of the PF control PI loop.

VAr Sharing Gain

Range [units] 0.00 .. 200.00 [-]
Step 0.01 [-]
Description
This setpoint adjusts the gain factor (P-factor) of the VAr sharing control PI loop.
VAr Sharing Int

Range [units] 0.10 .. 60.00 [s]
Step 0.01 [s]
Description
This setpoint adjusts the integration factor (I-factor) of the VAr sharing control PI loop.

Group: Synchronization
Subgroup: Synchronization
Synchronization Type

Range [units] PhaseMatch / SlipSynchr [-]
Default value PhaseMatch Force value YES
Step [-]
Description
This setpoint adjusts the type of Synchronization (page 244).
PhaseMatch
This type of synchronization is based on voltage and phase shift match. Limits are adjusted via
setpoints Voltage Window (page 477) and Phase Window (page 478). When voltage and phase
shift match the breaker close command is sent after Dwell Time (page 478) is elapsed.
SlipSynchr
This type of synchronization regulates the voltage to match Voltage Window (page 477) and BESS
Frequency (page 670) to match theMains/Bus Frequency (page 731) +Slip Frequency (page
479). When this frequency is reached, Dwell Time (page 478) starts to be counted down and when
elapses, breaker close command is sent.
IMPORTANT: The breaker close command is sent in advance due to breaker latency
which is set via setpoint BCB Latency (page 479) / MCB Latency (page 480).
Note: Synchronization is not allowed if there is any already synchronized Mains Controller in the
control group.

Synchronization Timeout

Range [units] 1 .. 1800 [s] / No Timeout
Step 1s
Description
This setpoint adjusts the maximum duration of Synchronization (page 244).
Note: If this setpoint is adjusted to No Timeout then automatic restart of synchronization occurs
every 180s. This method helps to synchronize successfully even in difficult conditions.
Voltage Window

Range [units] 0.0 .. 100.0 [%]
Default value 10.0 % Force value YES
Step 0.1 %
Description
This setpoint adjusts the maximal AC Voltage difference between respective phases of Mains/Bus and
BESS for Synchronization (page 244). (BESS Voltage L1-N (page 670), Mains/Bus Voltage L1-N
(page 731), BESS Voltage L2-N (page 670),Mains/Bus Voltage L2-N (page 731), …)
BESS to Mains/Bus Phase Shift

Range [units] -120 .. 120 [°]
Default value 0° Force value YES
Step 1°
Description
This setpoint is used to compensate phase shift which is caused by transformer.

Phase Window

Range [units] 0 .. 90 [°]
Default value 10 ° Force value YES
Step 1°
Setpoint visibility Only if Synchronization Type (page 476) = PhaseMatch
Description
This setpoint adjusts the maximal Slip Angle (page 674) for Synchronization (page 244).
In order to disable breaker close command, adjust this setpoint to 0. Synchronization procedure will be
active for Synchronization Timeout (page 477) or until breaker is closed from an external device.
Dwell Time

Range [units] 0,0 .. 25,0 [s]
Step 0,1 s
Description
The period of time that the phase angle difference must be within Phase Window (page 478) and
voltage difference within Voltage Window (page 477) before the breaker is closed.

Slip Frequency

Range [units] -0,50 .. 0,50 [Hz]
Default value -0,25 Hz Force value YES
Step 0,01 Hz
Setpoint visibility Only if Synchronization Type (page 476) = SlipSynchr
Description
This setpoint adjusts the required BESS Frequency (page 670) during synchronization while
Synchronization Type (page 476) = SlipSynchr.
Note: Required BESS Frequency (page 670) = Mains/Bus Frequency (page 731) + Slip
Frequency.
Slip Frequency Window

Range [units] 0,01 .. 0,50 [Hz]
Default value 0,15 Hz Force value YES
Step 0,01 Hz
Description
Window of slip frequency for slip synchronization (Synchronization Type (page 476) = SlipSynchr).
BCB Latency

Range [units] 20 .. 1 000 [ms]
Default value 80 ms Force value YES
Step 1 ms
Description
Latency of BCB. This setpoint is enable, when Synchronization Type (page 476) has SlipSynchro
value. Synchronization Type (page 476) setting value of this setpoint.

MCB Latency

Range [units] 20 .. 1 000 [ms]
Default value 80 ms Force value YES
Step 1 ms
Description
Latency of MCB.
IMPORTANT: This setpoint is enable, when Synchronization Type (page 476) has Split
Synchro value
Group: Power Management
Subgroup: Power Management Control
Power Management
Setpoint group Power Management Related FW 1.3.0

Step [-]
Description
This setpoint is used to enable or disable the Power Management (page 269) function in this particular
controller.
Disabled - Function is disabled. BESS is Started/Stopped only via LBI REMOTE START/STOP
(PAGE 915).
Enabled - Function is enabled. Starting/Stopping of BESS is affected by Power Management
(page 269) requirements.
IMPORTANT: Controller Mode (page 378) = AUTO, otherwise BESS is not controlled with
Power Management (page 269) function.
Note: The main idea of renewables is to run with the maximal priority. So it is expect the Microgrid
site will not be influenced by the power management because BESS and renewables shloud always
run.

Power Management Delay

Step 1s
Description
Setpoint defines delay of the Power Management (page 269). When REMOTE START/STOP (PAGE 915)
signal is activated the Gen-sets are started. All Gen-sets (where Power Management (page 480) is
enabled) are started and stay running for time period specified by this parameter.
After this period elapses, only the unit(s) needed according to the Power Management calculation stay
running and the rest is stopped.
Example: This delay is useful, when you need to start gen-sets to an unknown load. Setting for
example 360s (6 minutes) and activating REMOTE START/STOP (PAGE 915) will force all gen-sets to
start and run for 6 minutes despite of the power management setting.
Note: By setting “0” the Power Management function is enabled immediately.

#Power Management Mode

Range [units] ABS [kW] / N/A Mode / REL [%]
Default value ABS [kW] Force value NO
Step [-]
Description
This setpoint selects the Power Management (page 269) function mode.
The Power Management (page 269) is based on Actual Active Power In

ABS [kW] PM (page 750) and Nominal power (page 368) or Installed Power (page
368) of each unit.
Power Management mode which has been set via CAN2A (page 19) (CAN2B
N/A Mode (page 19)) is not supported in this controller. Alarm Wrn Unsupported PMS
Mode (page 1103) is active.
The Power Management (page 269) is based on relative load, i.e. ratio of
REL [%] Actual Active Power In PM (page 750) to Nominal power (page 368) or
Installed Power (page 368).
IMPORTANT: This setpoint is shared via ⑧ CAN2A (page 47) and/or ⑦ CAN2B (page 47) .
Change of this setpoint will be reflected in all controllers.

Priority

Step 1 [-]
Description
This setpoint adjusts the priority of the unit within the control group. A lower number represents a “higher”
priority, i.e. a BESS with lower number will start before another one with higher number.
Note: If the binary input Top Priority (page 918) is active, the unit gets the highest priority (0)
independent of the setpoint setting.
Note: If more than one unit have the same priority they will act as “one big” unit.
Note: The main idea of renewables is to run with the maximal priority. So it is expect the Microgrid
site will not be influenced by the power management because BESS and renewables shloud always
run.

#Priority Auto Swap

Range [units] Disabled / RunHourEq / N/A Mode / Efficient [-]
Step [-]
Description
This setpoint selects the optimization of Power Management (page 269) function.
Optimization is disabled. Priorities are given directly by the values adjusted in

Disabled
the setpoint Priority (page 483).
This method changes the BESS Priority (page 748) (not the setpoint
Priority (page 483)) to equalize running hours of the units or to keep
Run Hours Equal
maximal difference of running hours set by #Run Hours Max Difference
(page 506).
Power Management mode, which has been set via CAN2A (page 19)
N/A Mode
(CAN2B (page 19)), is not supported in this controller.
This method changes the BESS Priority (page 748) (not the setpoint
Priority (page 483)) to optimize which units are running according to their
Efficient Nominal power (page 368)/Installed Power (page 368), requested Load
reserve and Run Hours. For units with the same nominal power also run hour
equalization is being performed.
IMPORTANT: LBI Top Priority (page 918) can be used only if #Priority Auto Swap =
Disabled.

#System Start Delay

Step 1s
Description
This setpoint adjusts the delay of the system activation after the LBI REMOTE START/STOP (PAGE 915)
has been activated.
Note: System Start Delay countdown is changed to 1 second for parallel operation (Bus is in parallel
with Mains).
#System Stop Delay

Step 1s
Description
This setpoint adjusts the delay of the system deactivation after the LBI REMOTE START/STOP (PAGE 915)
has been deactivated.
Note: System Stop Delay countdown is changed to 1 second for parallel operation (Bus is in parallel
with Mains).

Subgroup: Dynamic Spinning Reserve
Dynamic Spinning Reserve Source

Range [units] Disabled/External Analog Value/Internal Calculation
Default value Internal Calculation Force value YES
Step [-]
Description
This setpoint is used to select the source for the function Dynamic Spinning Reserve (page 272).
Disabled: The CU is not calculating and providing Dynamic Spinning Reserve (page 749) and
Dynamic Spinning Reserve Offset (page 749) at all.
External Analog Value: The CU receives these values from the LAIs DYNAMIC SPINNING
RESERVE (PAGE 988) and DYNAMIC SPINNING RESERVE OFFSET (PAGE 988).
Internal Calculation: The DYNAMIC SPINNING RESERVE OFFSET (PAGE 988) is received from LAI
and DYNAMIC SPINNING RESERVE (PAGE 988) is calculated by CU.

Step [-]
Description
This setpoint is used to enable/disable use of the Dynamic Spinning Reserve (page 272) functionality
in power management.
Note: If enabled option is selected the InteliNeo6000 controller also participate on DSR in the same
way as Gen-set controllers setpoint should be used only to have the same calculation of Load
Reserve and DSR as rest of controllers in group.

Solar Coverage Ratio

Range [units] 0 .. 100 [%] of PV Actual P (page 676)
100 % of PV Actual P
(page 676)
Step 1 % of PV Actual P (page 676)
Description
This setpoint defines how much percent from actual power of the PV (renewables) should be covered by
(counted in) Dynamic Spinning Reserve (page 272) in case Internal Calculation is used.
Wind Coverage Ratio

Range [units] 0 .. 100 [%] of WT Actual P (page 702)
100 % of WT Actual P
(page 702)
Step 1 % of WT Actual P (page 702)
Description
This setpoint defines how much percent from actual power of the WT should be covered by (counted in)
Dynamic Spinning Reserve (page 272) in case Internal Calculation is used.

Subgroup: Load Reserve Set 1
#Starting Load Reserve 1

0 .. #Stopping Load Reserve 1 (page 489) [kW] (depends on the selected Power
Range [units]
196))
Setpoint visibility Only if #Power Management Mode (page 482) = ABS [kW]
Description
This setpoint adjusts required minimal Actual Reserve (page 748) for Power Management (page 269)
function.
If Load Reserve Set 1 is activated and Actual Reserve (page 748) drops bellow this limit, next
Controller will be started.
The currently active reserve set is selected by binary inputs LOAD RES 2 ACTIVE (PAGE 898), LOAD RES 3
ACTIVE (PAGE 899) and LOAD RES 4 ACTIVE (PAGE 900). If none of these inputs is active the Load
Reserve Set 1 is selected.
Note: If the absolute power management is selected, this setpoint (or the setpoints #Starting Load
Reserve 2 (page 491), #Starting Load Reserve 3 (page 494) or #Starting Load Reserve 4 (page
497) depending on which load reserve set is selected) determines also the number of Controllers
(that are part of the power management) which will start (according to their priority and nominal
power).

#Stopping Load Reserve 1

#Starting Load Reserve 1 (page 488) .. 32000 [kW] (depends on the selected
Range [units]
Power Formats And Units (page 196))
Description
This setpoint adjusts required maximal Actual Reserve (page 748) for Power Management (page
269) function.
If Load Reserve Set 1 is activated and Actual Reserve (page 748) rises over this limit, next Controller
will be stopped.
Note: The reserve for stop must be always adjusted higher than the reserve for start.

#Starting Rel Load Reserve 1

Range [units] 0 .. #Stopping Load Reserve 1 (page 489) [%]
Default value 60 % Force value NO
Step 1%
Setpoint visibility Only if #Power Management Mode (page 482) = REL [%]
Description
This setpoint adjusts required minimal Actual Relative Reserve (page 750) for Power Management
(page 269) function.
If Load Reserve Set 1 is activated and Actual Relative Reserve (page 750) drops below this limit, next
#Stopping Rel Load Reserve 1

Range [units] #Starting Rel Load Reserve 1 (page 490) .. 110 [%]
Step 1%
Description
This setpoint adjusts required maximal Actual Relative Reserve (page 750) for Power Management
If Load Reserve Set 1 is activated and Actual Relative Reserve (page 750) rises over this limit, next
Controller will be stopped.


Range [units]
196))
Description
function.
Note: If the absolute power management is selected, this setpoint (or the setpoints #Starting Load
Reserve 2 (page 491), #Starting Load Reserve 3 (page 494) or #Starting Load Reserve 4 (page
497) depending on which load reserve set is selected) determines also the number of Controllers
(that are part of the power management) which will start (according to their priority and nominal
power).


Range [units]
Description
269) function.
will be stopped.


Range [units] 0 .. #Stopping Rel Load Reserve 2 (page 493) [%]
Step 1%
Description

Step 1%
Description


Range [units]
196))
Description
function.


Range [units]
Description
269) function.
will be stopped.


Step 1%
Description

Step 1%
Description


Range [units]
196))
Description
function.


Range [units]
196))
Description
269) function.
will be stopped.


Step 1%
Description

Step 1%
Description

Subgroup: Minimal Running Power
#Min Run Power

Range [units] 0 .. 65000 [kW] (depends on the selected Power Formats And Units (page 196))
Description
This setpoint adjusts required Minimal Running Nominal Power (page 751) of Controllers and BESS if
Minimal Running Power 1 is chosen.
There are 3 Minimal Running Power options. This one is activated by LBI MIN RUN POWER ACT 1 (PAGE
904).
#Min Run Power 2

Description
904).

#Min Run Power 3

Description
905).
Subgroup: Start/Stop Timing
#Next Engine Start Delay

Range [units] 0 .. 3 600 [s]
Step 1s
Description
This setpoint adjusts the delay before next Controller is started after Actual Reserve (page 748) /
Actual Relative Reserve (page 750) drops bellow Starting Load Reserve of currently active Load
Reserve Set.

#Next Engine Stop Delay

Step 1s
Description
This setpoint adjusts the delay before next Controller is stopped after Actual Reserve (page 748) /
Actual Relative Reserve (page 750) rises over Stopping Load Reserve of currently active Load
Reserve Set.
Subgroup: Slow Stop Protection
#Slow Stop Delay

Step 1s
Description
This setpoint adjusts for how long the next Controllers will suppress their own Slow Stop alarms to give
chance to another Controller to start and replace the defective one.
Note: If there is no Controller available to start, the Slow Stop alarms are not suppressed.

Slow Stop Stay In Load Sharing

Range [units] Yes / No [-]
Default value No Force value NO
Step [-]
Description
This setpoint defines if the BESS stays in loadsharing once the slow stop is initiated. The Slow Stop
protection takes an effect in Multiple Island as same as in Multiple parallel operation.
TheBESS with active Slow Stop protection regulates its power to value 20% of its
Nominal Power but only in if does not lead to overloading of other gensets or running
No them under 20%. Then it stays in load sharing. This mode is ended once the capacity of
other genset with lowest priority is available (load reserve is sufficient) or latest when
Slow Stop Delay elapsed.
The BESS with active Slow Stop protection stay in load sharing until another gen-set is
Yes
connected to the bus or after the Slow Stop Delay is elapsed.

Subgroup: Over Load Next Start Protection
#Overload Next Start Protection

Step [-]
Description
This setpoint enables or disables Overload Next Start Protection. It makes the next Controller (in priority
order) to start when the load excises the value given by the setpoint #Overload Next Start Level (page
504) right after the delay #Overload Next Start Delay (page 505). #Overload Next Start Protection
requires Starting Load Reserve condition to be fulfilled in order to be used.
Disabled Protection is disabled.

Protection is enabled. If Actual Active Power In PM (page 750) of PM
Controllers related to Running Nominal Power In PM (page 751) is over
Enabled
#Overload Next Start Level (page 504), another Controller is started after
#Overload Next Start Delay (page 505).
#Overload Next Start Level

Range [units] 0 .. 100 [%] of Running Nominal Power In PM (page 751)
80 % of Running Nominal Power In
PM (page 751)
Step 1 % of Running Nominal Power In PM (page 751)
Setpoint visibility Only if #Overload Next Start Protection (page 504) = Enabled
Description
This setpoint adjusts the minimal load for #Overload Next Start Protection (page 504).

#Overload Next Start Delay

Step 1s
Setpoint visibility Only if #Overload Next Start Protection (page 504) = Enabled
Description
This setpoint adjusts the delay for #Overload Next Start Protection (page 504).
Subgroup: Run Hours Equalization
Run Hours Base

Range [units] 0.0 .. 200000.0 [h]
Default value 0.0 h Force value YES
Step 0.1 h
Description
This setpoint adjusts the correction of actual Running Hours (page 771).
RH = Running Hours (page 771) -Run Hours Base
Note: RH can not be adjusted below 0
Example:
BESS 1 actual Running hours = 1000 h.
BESS 2 actual Running hours = 2000 h.
Adjust this setpoint forBESS 1 = 1000 h and for BESS 2 = 2000 h to be on the same base for
Running Hours Equalization.

#Run Hours Max Difference

Range [units] 0 .. 65000 [h]
Default value 100 h Force value NO
Step 1h
Description
This setpoint adjusts the maximal difference between Running Hours (page 771) of Controllers in
Power Management (page 269) function if #Priority Auto Swap (page 484).
If the difference between Running Hours (page 771) is over this limit, priorities are swapped.
Subgroup: Efficient Mode
#Power Band Change Up Delay

Range [units] 0 .. 3 600 [s]
Step [s]
Description
This setpoint is used for adjusting the delay of changing the power band if the load demand rose above
the upper limit of the current power band. Setpoint is taken into account only if #Priority Auto Swap
(page 484) = Efficient.

#Power Band Change Down Delay

Range [units] 0 .. 3 600 [s]
Step [s]
Description
This setpoint is used for adjusting the delay of changing the power band if the load demand drops below
the lower limit of the current power band. Setpoint is taken into account only if #Priority Auto Swap
(page 484) = Efficient.
Subgroup: Group Settings
Control Group

Step 1 [-]
Description
This setpoint adjusts control group in which the particular controller belongs to.
If there are no logical groups on the site, adjust this setpoint to 1. See more information in chapter
Control Groups (page 136).

Group Link L

Step 1 [-]
Description
If the input GROUP LINK (PAGE 893) of this particular controller is used to provide the "group link"
information for two Control groups (to get more information refer to the chapter Control Groups (page
136)). This setpoint is used to select which group is located at the left side of the group link breaker. (bus
tie breaker). If this particular controller is not used for the group link function, adjust this setpoint to 1.
Group Link R

Step 1 [-]
Description
If the input GROUP LINK (PAGE 893) of this particular controller is used to provide the "group link"
information for two Control groups (to get more information refer to the chapter Control Groups (page
136)). This setpoint is used to select which group is located at the right side of the group link breaker.
(bus tie breaker). If this particular controller is not used for the group link function, adjust this setpoint to 1.

Group: Loss of Mains Protections
Subgroup: Loss of Mains Protections
Vector Shift Limit
Loss of Mains
Protection
Range [units] 1 .. 45 [°]
Default value 10 ° Force value YES
Step 1°
Setpoint visibility Only if Vector Shift Protection (page 584) != Disabled
Description
This setpoint adjusts the threshold level for the Vector Shift Protection (page 584).
Note: To adjust this setpoint properly, check the value Max Vector Shift (page 740). The value is
available in InteliConfig, contains the maximal measured vector shift value since the BESS has been
synchronized to the mains and after opening of BCB or MCB it is "frozen". In normal conditions the
value should not be higher than 3 º and the most common setting of the threshold is about 7 º.
ROCOF1 Windows Length
Loss of Mains
Protection
Step 1 [-]
Setpoint visibility Only if ROCOF1 Protection (page 585) != Disabled
Description
This setpoint adjusts the time averaging level for the ROCOF1 Protection (page 585).
It defines the number of periods of the mains voltage in which the ROCOF protection is evaluated. The
higher length of the ROCOF window means less sensitive protection for short oscillations of the
frequency to both directions from the nominal value. Also, the delay of evaluation is higher.

ROCOF1 df/dt
Loss of Mains
Protection
Range [units] 0.01 .. 10.00 [Hz/s]
Default value 1.00 Hz/s Force value YES
Step 0.01 Hz/s
Description
This setpoint adjusts the trip level for ROCOF1 Protection (page 585).
Loss of Mains
Protection
Range [units] 0.1 .. 2.5 [s]
Step 0.1 s
Description
It defines the time interval for which the ROCOF protection is evaluated. The higher length of the ROCOF
window means less sensitive protection for short oscillations of the frequency to both directions from the
nominal value. Also, the delay of evaluation is higher.

ROCOF2 df/dt
Loss of Mains
Protection
Range [units] 0.01 .. 10.00 [Hz/s]
Step 0.01 Hz/s
Description
Loss of Mains
Protection
Range [units] 0.1 .. 2.5 [s]
Step 0.1 s
Description

ROCOF3 df/dt
Loss of Mains
Protection
Range [units] 0.01 .. 10.00 [Hz/s]
Step 0.01 Hz/s
Description
Loss of Mains
Protection
Range [units] 0.1 .. 2.5 [s]
Step 0.1 s
Description

ROCOF4 df/dt
Loss of Mains
Protection
Range [units] 0.01 .. 10.00 [Hz/s]
Step 0.01 Hz/s
Description
Vector Shift/ROCOF CB Selector
Loss of Mains
Protection
Range [units] MCB / BCB [-]
Default value MCB Force value YES
Step [-]
Only if Application Mode (page 777) = MPTM and
Vector Shift Protection (page 584)!= Disabled or
ROCOF1 Protection (page 585)!= Disabled or
Setpoint visibility
ROCOF4 Protection (page 588)!= Disabled .
Description
This setpoint adjusts which breaker will be opened when Vector Shift Protection (page 584), ROCOF1
Protection (page 585), ROCOF2 Protection (page 586), ROCOF3 Protection (page 587) or
ROCOF4 Protection (page 588) is detected.
Note: If the BCB is selected and a mains failure occurs the BCB will be opened immediately when
the vector shift or ROCOF is detected, however MCB will be also opened due to other mains
protections such as Mains <f Protection (page 579) or Mains <V Protection (page 572).

Group: Mains Settings
Subgroup: Mains Voltage Protections
Mains >V

100.0 .. Mains >>V (page 515) of Mains/Bus Nominal Voltage Ph-N (page 373)
Range [units]
and Mains/Bus Nominal Voltage Ph-Ph (page 374) [%]
110.0 % of Mains/Bus Nominal Voltage
Default value Ph-N (page 373) and Mains/Bus Nominal Force value YES
Step
Description
This setpoint specifies the relative voltage threshold level for Mains >V Protection (page 568).
Note: Mains/Bus Voltage L1-N (page 731), Mains/Bus Voltage L2-N (page 731), Mains/Bus
Voltage L3-N (page 732), Mains/Bus Voltage L1-L2 (page 732), Mains/Bus Voltage L2-L3 (page
732) and Mains/Bus Voltage L3-L1 (page 732) are used for this protection.
Mains >V Delay

Range [units] 0.00 .. 600.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for Mains >V Protection (page 568).

Mains >V Hys

Range [units]
0.0 [%] of Mains/Bus Nominal Voltage
Default value Ph-N (page 373) and Mains/Bus Force value NO
Step
Description
This setpoint adjusts the hysteresis for return from Mains >V Protection (page 568).
Mains >>V

Mains >V (page 514) .. 130.0 [%] of Mains/Bus Nominal Voltage Ph-N (page
Range [units]
373) and Mains/Bus Nominal Voltage Ph-Ph (page 374)
Step
Description
This setpoint specifies the relative voltage threshold level for Mains >>V Protection (page 570).

Mains >>V Delay

Range [units] 0.00 .. 600.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for Mains >>V Protection (page 570).
Mains >>V Hys

Range [units]
Default value Ph-N (page 373) and Mains/Bus Force value YES
Step
Setpoint
Only if Application Mode (page 777) = MPTM
visibility
Description
This setpoint adjusts the hysteresis for return from Mains >>V Protection (page 570).

Mains 10min Avg >V

Range [units] 100.0 .. 150.0 [%] of Mains/Bus Nominal Voltage Ph-Ph (page 374)
Step 0.1 % of Mains/Bus Nominal Voltage Ph-Ph (page 374)
Description
This setpoint specifies the relative voltage threshold level for Mains 10min Avg >V Protection (page
571).
Mains 10min Avg >V Delay

Range [units] 0.00 .. 600.00 [s]
Step 0.01 s
Description
This setpoints adjust delay for Mains 10min Avg >V Protection (page 571).

Mains <V

Mains <<V (page 519) .. 99.0 [%] of Mains/Bus Nominal Voltage Ph-N (page
Range [units]
60 % of Mains/Bus Nominal Voltage Ph-
Default value N (page 373) and Mains/Bus Nominal Force value YES
1 % of Mains/Bus Nominal Voltage Ph-N (page 373) and Mains/Bus Nominal
Step
Description
This setpoint specifies the relative voltage threshold level for Mains <V Protection (page 572).
Mains <V Delay

Range [units] 0.00 .. 600.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for Mains <V Protection (page 572).

Mains <V Hys

Range [units]
Step
Description
This setpoint adjusts the hysteresis for return from Mains <V Protection (page 572).
Mains <<V

10.0 .. Mains <V (page 518) [%] of Mains/Bus Nominal Voltage Ph-N (page
Range [units]
Step
Description
This setpoint specifies the relative voltage threshold level for Mains <V Protection (page 573).

Mains <<V Delay

Range [units] 0.00 .. 600.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for Mains <V Protection (page 573).
Mains <<V Hys

Range [units]
Step
Description
This setpoint adjusts the hysteresis for return from Mains <V Protection (page 573).

Mains V Unbalance

1 .. 200 [%] of Mains/Bus Nominal Voltage Ph-N (page 373) and Mains/Bus
Range [units]
10 % of Mains/Bus Nominal Voltage
1 % of Mains/Bus Nominal Voltage Ph-N (page 373) and Mains/Bus Nominal
Step
Description
This setpoint specifies the relative voltage threshold level for Mains V Unbalance Protection (page
574).
Mains V Unbalance Delay

Range [units] 0.00 .. 600.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for Mains V Unbalance Protection (page 574).

Subgroup: Mains Frequency Protection
Mains >f

Range [units] 0.00 ..Mains >>f (page 523) [Hz]
Step 0.01 Hz
Description
This setpoint adjusts maximal accepted frequency for Mains >f Protection (page 577).
Mains >f Delay

Range [units] 0.00 .. 1000.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for Mains >f Protection (page 577).
Mains >f Hys

Range [units] 0.00 .. 2.50 [Hz]
Step 0.01 Hz
Description
This setpoint adjusts the hysteresis for return from Mains >f Protection (page 577).

Mains >>f

Range [units] Mains >f (page 522) .. 10.00 [Hz]
Step 0.01 Hz
Description
This setpoint adjusts maximal accepted frequency for Mains >>f Protection (page 578).
Mains >>f Delay

Range [units] 0.00 .. 1000.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for Mains >>f Protection (page 578).
Mains >>f Hys

Range [units] 0.00 .. 2.50 [Hz]
Step 0.01 Hz
Description
This setpoint adjusts the hysteresis for return from Mains >>f Protection (page 578).

Mains <f

Range [units] Mains <<f (page 525) .. 0.00 [Hz]
Default value -1.50 Hz Force value YES
Step 0.01 Hz
Description
This setpoint adjusts minimal accepted frequency for Mains <f Protection (page 579).
Mains <f Delay

Range [units] 0.00 .. 1000.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for Mains <f Protection (page 579).
Mains <f Hys

Range [units] 0.00 .. 2.50 [Hz]
Step 0.01 Hz
Description
This setpoint adjusts the hysteresis for return from Mains <f Protection (page 579).

Mains <<f

Range [units] -10.00 .. Mains <f (page 524) [Hz]
Step 0.01 Hz
Description
This setpoint adjusts maximal accepted frequency for Mains <<f Protection (page 580).
Mains <<f Delay

Range [units] 0.00 .. 1000.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for Mains <<f Protection (page 580).
Mains <<f Hys

Range [units] 0.00 .. 2.50 [Hz]
Step 0.01 Hz
Description
This setpoint adjusts the hysteresis for return from Mains <<f Protection (page 580).

Subgroup: Mains Fault Timers
Mains Stabilization Delay

Range [units] 0.0 .. 60.0 [s]
Step 0.1 s
Description
This setpoint adjusts the time that Mains parameters need to remain within limits of voltage and
frequency protections before the return to Mains is initiated. This delay is active only when the BCB is not
closed and the load is not powered from the BESS or PV. After this delay elapsed, the procedure
continues by counting down the MCB Close Delay (page 526).
MCB Close Delay

Range [units] 0.0 .. 60.0 [s]
Step 0.1 s
Description
This setpoint adjusts the delay before MCB is closed after Mains returns.

Group: Grid Codes
Subgroup: Grid Codes Test
Grid Codes Test
Setpoint group Grid Codes Related FW 1.3.0

Step [-]
Description
This setpoint enables/disables simulation mode for some Grid Codes and Q(Um) regulation:
Power Regulation Based On Over/Under Frequency (page 294)
P For Q (page 301)
While this setpoint is Enabled, alarm Wrn Test UPQF (page 1103) is active.
Subgroup: Mains Params/MP Synchronization
Mains Params/MP Synchronization

Step [-]
Description
This setpoint enables/disables Synchronization & Connection Conditions (page 302).
Disabled Synchronization & Connection Conditions (page 302) is disabled.

Enabled Synchronization & Connection Conditions (page 302) is enabled.

Mains Synchronization V Max

Mains Synchronization V Min (page 528) .. 130 [%] of Mains/Bus Nominal
Range [units]
110 % of Mains/Bus Nominal
Step 1 % of Mains/Bus Nominal Voltage Ph-Ph (page 374)
Only if Application Mode (page 777) = MPTM and Mains Params/MP
Setpoint visibility
Synchronization (page 527) = Enabled
Description
This setpoint adjusts maximal accepted Mains/Bus Voltage for Network connection/reconnection
conditions (page 302).
Mains Synchronization V Min

10 .. Mains Synchronization V Max (page 528) [%] of Mains/Bus Nominal
Range [units]
Setpoint visibility
Description
This setpoint adjusts minimal accepted Mains/Bus Voltage for Network connection/reconnection
conditions (page 302).

Mains Synchronization f Max

Range [units] 0.00 .. 2.00 [Hz]
Step 0.01 Hz
Setpoint visibility
Description
This setpoint adjusts maximal accepted Mains/Bus Frequency (page 731) for Network
connection/reconnection conditions (page 302).
Mains Synchronization f Min

Range [units] -2.50 .. 0.00 [Hz]
Step 0.01 Hz
Setpoint visibility
Description
This setpoint adjusts minimal accepted Mains/Bus Frequency (page 731) for Network
connection/reconnection conditions (page 302) .

Mains Synchronization Period

Step 1s
Setpoint visibility
Description
This setpoint adjusts period for which is active Network connection/reconnection conditions (page
302) after LBO MAINS/BUS HEALTHY (PAGE 959) gets closed again.
Note: This period resets every time LBO MAINS/BUS HEALTHY (PAGE 959) recloses.
After MP Synchronization V Max

After MP Synchronization V Min (page 531) .. 130 [%] of Mains/Bus Nominal
Range [units]
Setpoint visibility
Description
This setpoint adjusts maximal accepted Mains/Bus Voltage for Network connection/reconnection
conditions after Mains Fail (page 303).

After MP Synchronization V Min

10 .. After MP Synchronization V Max (page 530) [%] of Mains/Bus Nominal
Range [units]
Setpoint visibility
Description
This setpoint adjusts minimal accepted Mains/Bus Voltage for Network connection/reconnection
conditions after Mains Fail (page 303).
After MP Synchronization f Max

Range [units] 0.00 .. 2.00 [Hz]
Step 0.01 Hz
Setpoint visibility
Description
This setpoint adjusts maximal accepted Mains/Bus Frequency (page 731) for Network
connection/reconnection conditions after Mains Fail (page 303).

After MP Synchronization f Min

Range [units] -2.50 .. 0.00 [Hz]
Step 0.01 Hz
Setpoint visibility
Description
This setpoint adjusts minimal accepted Mains/Bus Frequency (page 731) for Network
connection/reconnection conditions after Mains Fail (page 303).
After MP Synchronization Period

Step 1s
Setpoint visibility
Description
This setpoint adjusts period for which is active Network connection/reconnection conditions after
Mains Fail (page 303) after LBO MAINS/BUS HEALTHY (PAGE 959) gets closed again.
Note: This period resets every time LBO MAINS/BUS HEALTHY (PAGE 959) recloses.

Subgroup: After Mains Trip Period
After Mains Trip

Step [-]
Description
This setpoint enables/disables After Mains Trip Period (page 303).
Disabled After Mains Trip Period (page 303) is disabled

Enabled After Mains Trip Period (page 303) is enabled
After Mains Trip Period

Step 1s
Only if Application Mode (page 777) = MPTM and After Mains Trip (page 533) =
Setpoint visibility
Enabled
Description
This setpoint adjusts the period for how long is After Mains Trip Period active and LBO EVENT MAINS TRIP
(PAGE 945) is closed. The period starts once the Mains is healthy (LBO MAINS/BUS HEALTHY (PAGE 959)
is closed) and timer After MP Synchronization Period (page 532) is elapsed or Mains Params/MP
Synchronization (page 527) is disabled.
Note: This period resets every time LBO EVENT MAINS TRIP (PAGE 945) re-closes.

After Mains Trip Period Priority

Range [units] 0 .. 254; OFF [-]
Step 1 [-]
Only if Application Mode (page 777) = MPTM and Power Over/Under
Setpoint visibility
Frequency (page 535) = Enabled
Description
This setpoint adjusts the priority of After Mains Trip Period Ramp (page 534) which is used while LBO
EVENT MAINS TRIP (PAGE 945) is closed.
Note: Smaller number means higher priority, i.e. 0 has the highest priority.
After Mains Trip Period Ramp

Step 1s
Only if Application Mode (page 777) = MPTM and After Mains Trip (page 533) =
Setpoint visibility
Enabled
Description
This setpoint adjusts ramping time of the BESS Required P (page 753) to the BESS Required P
Target (page 753) if the LBO EVENT MAINS TRIP (PAGE 945) is closed.
Priority of this ramp is given by After Mains Trip Period Priority (page 534).
Example: Installed Power (page 368) = 20 kW, After Mains Trip Period Ramp = 10 seconds.
The ramp is changing with speed 20 kW per 10 seconds (2 kW/s).

Subgroup: Power Over/Under Frequency
Power Over/Under Frequency

Step [-]
Description
This setpoint enables/disables Power Regulation Based On Over/Under Frequency (page 294).
Disabled Power Regulation Based On Over/Under Frequency (page 294) is disabled

Enabled Power Regulation Based On Over/Under Frequency (page 294) is enabled
Power Over/Under Frequency Delay

Range [units] 0.0 .. 2.0 [s]
Step 0.1 s
Setpoint visibility
Description
This setpoint adjusts behavior of Power Regulation Based On Over/Under Frequency (page 294)
and defines minimal period for which Mains/Bus Frequency (page 731) has to be inside of PoF/PuF
range.
This setpoint adjusts delay for activation of Power regulation based on over frequency/under frequency.

Return Over/Under Frequency Delay

Step 1s
Setpoint visibility
Description
This setpoint defines the delay for Return Over/Under Frequency function. After this delay elapsed the
LBO EVENT RETURN OVER/UNDER FREQUENCY (PAGE 945) is closed.
Return Over/Under Frequency Period

Step 1s
Setpoint visibility
Description
This setpoint adjusts the period for how long is Return Over/Under Frequency active and LBO EVENT
RETURN OVER/UNDER FREQUENCY (PAGE 945) is closed.

Return From Over/Under Frequency Priority

Step 1 [-]
Setpoint visibility
Description
This setpoint adjusts the priority of Return From Over/Under Frequency Ramp (page 537) which is
used while LBO EVENT RETURN OVER/UNDER FREQUENCY (PAGE 945) is closed.
Return From Over/Under Frequency Ramp

Step 1s
Setpoint visibility
Description
This setpoint adjusts ramping time of BESS Required P (page 753) to BESS Required P Target (page
753) if LBO EVENT RETURN OVER/UNDER FREQUENCY (PAGE 945) is closed.
Priority of this ramp is given by Return From Over/Under Frequency Priority (page 537)
Example: Installed Power (page 368) = 20 kW, Return From Over/Under Frequency Ramp = 10
seconds. The ramp is changing with speed 20 kW per 10 seconds (2 kW/s).

Mains Frequency Rise Priority

Step 1 [-]
Setpoint visibility
Description
This setpoint adjusts Mains Frequency Rise Ramp (page 538) which is used while LBO EVENT MAINS
FREQUENCY RISE (PAGE 944) is closed.
Mains Frequency Rise Ramp

Step 1s
Setpoint visibility
Description
753) if LBO EVENT MAINS FREQUENCY RISE (PAGE 944) is closed.
Priority of this ramp is given by Mains Frequency Rise Priority (page 538)
Example: Installed Power (page 368) = 20 kW, Mains Frequency Rise Ramp = 10 seconds. The
ramp is changing with speed 20 kW per 10 seconds (2 kW/s).

Mains Frequency Fall Priority

Step 1 [-]
Setpoint visibility
Description
This setpoint adjusts the priority of Mains Frequency Fall Ramp (page 539) which is used while LBO
EVENT MAINS FREQUENCY FALL (PAGE 944) is closed.
Mains Frequency Fall Ramp

Step 1s
Setpoint visibility
Description
753) if LBO EVENT MAINS FREQUENCY FALL (PAGE 944) is closed.
Priority of this ramp is given by Mains Frequency Fall Priority (page 539).
Example: Installed Power (page 368) = 20 kW, Mains Frequency Fall Ramp = 10 seconds. The
ramp is changing with speed 20 kW per 10 seconds (2 kW/s).

Subgroup: Load Reduction
Load Reduction

Step [-]
Description
This setpoint enables/disables Load Reduction (page 298).
Disabled Load Reduction (page 298) is disabled

Enabled
Note: LBI Load Reduction Enable (page 897) has to be closed, otherwise this Setpoint has no
effect.
Load Reduction 1

Range [units] 0 .. 100 [%] of Installed Power (page 368) or Nominal power (page 368)
100 % of Installed Power (page 368) or
Nominal power (page 368)
Step 0.1 % of Installed Power (page 368) or Nominal power (page 368)
Only if Application Mode (page 777) = MPTM and Load Reduction (page 540) =
Setpoint visibility
Enabled
Description
This setpoint adjusts maximal allowed load of BESS while LBI LOAD REDUCTION 1 (PAGE 896) is closed.
Always the lowest load defined by the LAI LOAD REDUCTION (PAGE 990) or by LBIs, LOAD REDUCTION 1
(PAGE 896), LOAD REDUCTION 2 (PAGE 896), etc. is allowed.

Load Reduction 2

60 [%] of Installed Power (page 368) or
Setpoint visibility
Enabled
Description
Load Reduction 3

Setpoint visibility
Enabled
Description

Load Reduction 4

10 %of Installed Power (page 368) or
Setpoint visibility
Enabled
Description
Load Reduction Priority

Step 1 [-]
Setpoint visibility
Enabled
Description
This setpoint adjusts the priority of Load Reduction Ramp (page 543) which is used while LBO EVENT
LOAD REDUCTION (PAGE 944) is closed.
Note: If priority is set to OFF, Load Reduction Ramp (page 543) is not applied.

Load Reduction Ramp

Step 1s
Setpoint visibility
Enabled
Description
Target (page 753) if the LBO EVENT LOAD REDUCTION (PAGE 944) is closed.
Priority of this ramp is given by After Mains Trip Period Priority (page 534).
Example: Installed Power (page 368) = 20 kW, Load Reduction Ramp = 10 seconds. The ramp
is changing with speed 20 kW per 10 seconds (2 kW/s).

Subgroup: P(Um)
P(Um)

Range [units] Disabled / P Instal (Um) / P Actual (Um)
Step -
Description
This setpoint enables/disables and selects mode of Power Regulation Based On Actual Mains
Voltage (page 297).
Power Regulation Based On Actual Mains Voltage (page 297) is

Disabled
disabled.
enabled. Function is evaluated according to P(Um) (page 862) curve and the
P Instal (Um)
reduction is based on the setpoint Installed Power (page 368). Value Pmom
(page 721) is not used in this case.
enabled. Function is evaluated according to P(Um) (page 862) curve and the
P Actual (Um)
reduction is based on the actual value of BESS P (page 664).Value Pmom
(page 721) is used in this case.

P Ramp Filter

Range [units] Disabled / Enabled
Step -
Only if Application Mode (page 777) = MPTM and P(Um) (page 544) !=
Setpoint visibility
Disabled
Description
This setpoint enables/disables PT1 filtering for P(Um) Ramp (page 546) during ramping of BESS
Required P (page 753) to BESS Required P Target (page 753).
PT1 filtering is disabled.
Disabled
Pt1 filtering is enabled
Enabled

P(Um) Priority

Range [units] 0 .. 254 / OFF [-]
Step 1 [-]
Setpoint visibility Only if Application Mode (page 777) = MPTM and P(Um) (page 544) != Disabled
Description
This setpoint adjusts priority of P(Um) Ramp (page 546) which is used while LBO EVENT P(UM) (PAGE
945) is closed.
Note: Smaller number means higher priority, e.i. 0 has highest priority.
P(Um) Ramp

Range [units] 0 .. 1800 s
Step 1s
Setpoint visibility Only if Application Mode (page 777) = MPTM and P(Um) (page 544) != Disabled
Description
753) if LBO EVENT P(UM) (PAGE 945) is closed. The ramping behavior is affected by P Ramp Filter
(page 545) which can enable the PT1 filtering.
Priority of this ramp is given by P(Um) Priority (page 546).
Example: Installed Power (page 368) = 20 kW, P(Um) Ramp = 10 seconds. The ramp is
changing with speed 20 kW per 10 seconds (2 kW/s).

Subgroup: P For Q
P For Q Limitation

Step [-]
Description
This setpoint enables/disables P For Q (page 301).
Disabled P For Q (page 301) is disabled

Enabled P For Q (page 301) is enabled
P For Q Deadband

1 % of Installed Power (page 368)
or Nominal power (page 368)
Step 1 % of Installed Power (page 368) or Nominal power (page 368)
Only if Application Mode (page 777) = MPTM and P For Q Limitation (page
Setpoint visibility
547) = Enabled
Description
This setpoint adjusts the sensitive of P For Q (page 301) function. Use it to prevent oscillation of BESS
P (page 664).

P For Q Priority

Step 1 [-]
Setpoint visibility
547) = Enabled
Description
This setpoint adjusts the priority of P For Q Ramp (page 548) which is used while LBO EVENT P FOR Q
(PAGE 945) is closed.
Note: If priority is set to OFF, P For Q Ramp (page 548) is not applied.
P For Q Ramp

Step 1s
Setpoint visibility
547) = Enabled
Description
753) if LBO EVENT P FOR Q (PAGE 945) is closed.
Priority of this ramp is given by P For Q Priority (page 548)
Example: Installed Power (page 368) = 20 kW, P For Q Ramp = 10 seconds. The ramp is

Subgroup: Q&U Protection
Q&U Protection

Range [units]
Step [-]
Description
This setpoint enables/disables Q&U Protection (page 302).
Protection is enabled. Behavior of protection is adjusted via setpoints Q&U < V

(page 550), Q&U < Q (page 550), Q&U Protection Delay (page 551) and
Q&U CB Selector (page 551). When relative value of Mains/Bus Voltage L1-
N (page 731) drops bellow Q&U < V (page 550) of Mains/Bus Nominal
Enabled
Voltage Ph-N (page 373) value BESS Q (page 665) is bellow Q&U < Q (page
550) for period longer than Q&U Protection Delay (page 551), alarm Wrn
Q&U Protection (page 1097) is activated and breaker selected by Q&U CB
Selector (page 551) is opened.
Protection
Protection is enabled or disabled by the state of LBI PROTECTION FORCE
Force Disable
DISABLE 1 (PAGE 906).
1
Protection
Force Disable
2
Protection
Force Disable
3
Note: This protection is evaluated only if Application Mode (page 777) = MPTM and Breaker state
(page 778) = ParalOper.

Q&U < V

Range [units] 70.0 .. 100.0 [%] of Mains/Bus Nominal Voltage Ph-N (page 373)
Voltage Ph-N (page 373)
Step 0.1 % of Mains/Bus Nominal Voltage Ph-N (page 373)
Only if Application Mode (page 777) = MPTM and Q&U Protection (page 549) !=
Setpoint visibility
Disabled
Description
This setpoint adjusts minimal relative required Mains/Bus Voltage L1-N (page 731) for Q&U
Protection (page 549).
Q&U < Q

-32000 .. 32000 [kVAr] (depends on the selected Power Formats And Units
Range [units]
(page 196))
Default value 0 kVAr Force value YES
Setpoint visibility
Disabled
Description
This setpoint adjusts minimal relative required BESS Q (page 665) for Q&U Protection (page 549).

Q&U Protection Delay

Range [units] 0.00 .. 600.00 [s]
Step 0.01 s
Setpoint visibility
Disabled
Description
This setpoint adjusts reaction delay for Q&U Protection (page 549).
Q&U CB Selector

Range [units] MCB / BCB [-]
Default value BCB Force value YES
Step [-]
Setpoint visibility
Disabled
Description
This setpoint adjusts which breaker opens in case that Q&U Protection (page 549) is activated.
MCB When Q&U Protection (page 549) is activated, MCB breaker opens.
BCB When Q&U Protection (page 549) is activated, BCB breaker opens.
Note: Reclosing of breaker is forbidden if Wrn Q&U Protection (page 1097) is present in the alarm list.

Subgroup: Dynamic Support
Dynamic Support

Enabled / Disabled / Protection Force Disable 1 / Protection Force Disable 2
Range [units]
/ Protection Force Disable 3 [-]
Step [-]
Description
This setpoint enables/disables Dynamic Support - VRT (page 299) defined by >V and <V ride through
curves. The standard mains protections are still active.
Protection is enabled. Behavior of protection is adjusted

via application curves LVRT 3-phase (page 872), LVRT
Enabled
2-phase (page 873), LVRT 1-phase (page 874) and
OVRT (page 875).
Protection is enabled or disabled by the state of LBI
Protection Force Disable 1
Dynamic Support Protection Type

Range [units] No Protection / History Record / Warning / Mains Protection [-]
Default value Mains Protection Force value YES
Step [-]
Only if Application Mode (page 777) = MPTM and Dynamic Support (page 552)
Setpoint visibility
!= Disabled
Description
This setpoint adjusts protection type of Dynamic Support (page 552).

Dynamic Support PF/Q Control

Range [units] Active / Stopped [-]
Default value Active Force value YES
Step [-]
Setpoint visibility
!= Disabled
Description
This setpoint adjusts behavior of Voltage Regulator Output (page 758) while Dynamic Support - VRT
(page 299) is active.
Active Voltage Regulator Output (page 758) is still being regulated

Voltage Regulator Output (page 758) is frozen at the moment of activation
Stopped
the VRT function.
LVRT Level Severe

Range [units] 0,0 .. 100,0 [%] of relative Mains Voltage
50,0 % of relative
Mains Voltage
Step 0,1 % of relative Mains Voltage
Setpoint visibility
!= Disabled
Description
This setpoint adjusts critical undervoltage. If relative Mains Voltage drops bellow this limit, LBO LVRT
SEVERE (PAGE 958) is closed for at least 500 ms.

Post VRT Priority

Step 1 [-]
Setpoint visibility
!= Disabled
Description
This setpoint adjusts priority of Post VRT Ramp (page 554) which is used while LBO EVENT POST VRT
(PAGE 945) is closed.
Post VRT Ramp

Step 1s
Setpoint visibility
!= Disabled
Description
753) if LBO EVENT POST VRT (PAGE 945) is closed.
Priority of this ramp is given by Post VRT Priority (page 554).
Example: Installed Power (page 368) = 20 kW, Post VRT Ramp = 10 seconds. The ramp is

Subgroup: Q Ramp
Q Ramp

Step 1s
Description
This setpoint adjusts ramping time of BESS Required Q (page 757) from actual value to the new one
while PF/Q Control PTM Mode (page 349) = Q Control.This ramp is activated in case the BESS
Required Q (page 757) cross the limit defined by the setpoint Q Deadband (page 555).
See PF/Q Control (page 260)PF/Q control (page 257) for more information.
Q Deadband

Range [units] 0,0 .. 5,0 [%] of BESS Q (page 665)
Default value 2,0 % of BESS Q (page 665) Force value YES
Step 0,1 % of BESS Q (page 665)
Description
This setpoint prevents oscillation of BESS P (page 664) while PF/Q Control PTM Mode (page 349) =
Q Control.In case the BESS Required Q (page 757) cross the limit defined by this setpoint Q Ramp
(page 555) is activated.
See PF/Q Control (page 260)PF/Q control (page 257) for more information.

Subgroup: Q(Um)
Q(Um) 0 Reference

Range [units] 75 .. 125 [%] of Q(Um) (page 858)
Default value 100 % of Q(Um) (page 858) Force value YES
Step 1 % of Q(Um) (page 858)
Description
This setpoint adjusts horizontal offset of Q(Um) (page 858) curve.
See Q(Um) (page 263)PF/Q control (page 257) for more information.
Q(Um) Deadband

Range [units] 0.0 .. 5,0 [%] of BESS Q (page 665)
Description
Q(Um).In case the voltage cross the limit defined by this setpoint, the new value of BESS Required Q
(page 757) is calculated according to Q(Um) (page 858) curve.

Subgroup: Qref/Ulim
Qref/Pnom Shift

Range [units] -33 .. 33 [%] of Qref/Ulim (page 859)
Default value 0 % of Qref/Ulim (page 859) Force value YES
Step 1 % of Qref/Ulim (page 859)
Description
This setpoint adjusts vertical offset of Qref/Ulim (page 859) curve.
See Qref/Ulim (page 265)PF/Q control (page 257) for more information.
Qref/Ulim Deadband

Description
Qref/Ulim.In case the voltage cross the limit defined by this setpoint, the new value of BESS Required Q
(page 757) is calculated according to Qref/Ulim (page 859) curve.
See Qref/Ulim (page 265)PF/Q control (page 257) for more information.

Subgroup: Q(P)
Q(P) Deadband

Description
Q(P). In case the voltage cross the limit defined by this setpoint, the new value of BESS Required Q
(page 757) is calculated according to Q(P) (page 860) curve.
See Q(P) (page 264)PF/Q control (page 257) for more information.
Subgroup: Soft Unload
Soft Unload Priority

Step 1 [-]
Description
This setpoint adjusts priority of Soft Unload Ramp (page 559) which is used while LBO EVENT SOFT
UNLOAD (PAGE 946) is closed.
Note: Smaller number means higher priority, e.i. 0 has highest priority.

Soft Unload Ramp

Step 1s
Description
Target (page 753) while soft unloading when BCB is requested to be opened.
The Required P reach the zero value at the end of the timer. The ramping time is set for ΔP which is given
by the setpoint Installed Power (page 368) or by the setpoint Nominal power (page 368) if the
Installed Power is OFF.
Example: Installed Power (page 368) = 20 kW, Soft Unload Ramp = 10 seconds. The ramp is
changing with speed 20 kW per 10 seconds (2 kW/s) to the zero value.
Note: This setpoint is shared with Soft Unload Ramp (page 470)

Subgroup: Pave
Pave Protection

Range [units]
Step [-]
Description
This setpoint enables/disables Pave (page 304) function.
Protection is enabled. Behavior of protection is adjusted via

Enabled
setpoint Pave (page 560).
Pave

Step 1 kW
Only if Application Mode (page 777) = MPTM and Pave Protection (page 560)
Setpoint visibility
!= Disabled
Description
This setpoint defines the maximum exported power agreed with the grid.
According to this setpoint and LAI PMOM (PAGE 993) is calculated value Pmom/Pave (page 724) which
is used in application curve P MOM/PAVE MAX (PAGE 863). It is used by the Pave (page 304) function.

Group: BESS Protections
Subgroup: Overload Protection
IDMT Overload Protection

Range [units]
Step [-]
Description
This setpoint enables or disables IDMT Overload Protection.
Behavior of protection is adjusted via setpoints 2POverload Start Evaluation Level (page 437) and
2POverload Start Evaluation Delay (page 438). This protection activates alarm Sd IDMT Overload
(page 1121).
The reaction time is calculated by this formula:
Setpoint options:

Subgroup: Current Protection
Short Circuit Protection

Range [units]
Protection Force Disable 3 [-] [-]
Step [-]
Description
This setpoint enables or disables Short Circuit Protection.
Behavior of protection is adjusted via setpoints Short Circuit Protection (page 562) and Short Circuit
Delay (page 440). When value of BESS Current L1 (page 672), BESS Current L2 (page 672) and
BESS Current L3 (page 672) related to Nominal Current (page 369) cross over Short Circuit (page
439) for time longer than Short Circuit Delay (page 440) alarm PVBO Short Circuit (page 1122) is
activated.
Setpoint options:
Enabled / Disabled : Protection is enabled / disabled.
IDMT BESS >A Protection

Range [units]
Step [-]
Description
This setpoint enables or disables IDMT BESS >A Protection.
Behavior of protection is adjusted via setpoints IDMT BESS >A Delay (page 440). This protection
activates alarm Sd IDMT BESS >A (page 1121).

IBESS = Maximum (BESS Current L1 (page 672)andBESS Current L1 (page 672)
Note: Reaction time is limited to 3600 s = 60 minutes. IDMT protection is not active for Reaction time
values longer than 60 minutes.
Overcurrent
Overcurrent IDMT Delay
≤100 % 101 % 110 %
0.2 s No action 20 s 2s
Reaction Time
2s No action 200 s 20 s
20 s No action 2000 s 200 s
Setpoint options:

BESS Current Unbalance Protection

Range [units]
Step [-]
Description
This setpoint enables or disables BESS Current Unbalance Protection.
Protection is enabled. Behavior of protection is adjusted via setpoints BESS Current Unbalance (page
441) and BESS Current Unbalance Delay (page 441). When relative difference between BESS
currents is over setpoint BESS Current Unbalance (page 441) for time longer than BESS Current
Unbalance Delay (page 441)alarm Sd BESS Current Unbalance (page 1121) is activated.
IMPORTANT: Behavior of this protection is influenced by setpoint Connection type (page
371)
Connection
type (page Compared values (maximum difference)
371)
3Ph4Wire
High Leg D
(BESS Current L1 (page 672),BESS Current L1 (page 672)
3Ph3Wire
SplitPhase
MonoPhase No protection is evaluated.
Setpoint options:

Subgroup: Voltage Protection
BESS >V

Range [units]
Step [-]
Description
This setpoint enables or disables BESS >V Protection.
Protection is enabled. Behavior of protection is adjusted via setpoints BESS >VUndervoltage (page 1)
and BESS >V Delay (page 443). When BESS voltage exceeds limit set by BESS >VUndervoltage
(page 1) for time longer than BESS >V Delay (page 443) appropriate alarm is activated.
Value Alarm
Setpoint options:

BESS >>V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables BESS >>V Protection..
Behavior of protection is adjusted via setpoints BESS >>V (page 443) and BESS >>V Delay (page
444). When BESS voltage exceeds limit set by BESS >>V (page 443) for time longer than BESS >>V
Delay (page 444) appropriate alarm is activated.
Value Alarm
BESS Voltage L1-N (page 670) Sd BESS >>V L1-N (page 1115)
BESS Voltage L2-N (page 670) Sd Mains/Bus >>V L2-N (page 1115)
BESS Voltage L3-N (page 670) Sd BESS >>V L3-N (page 1116)
BESS Voltage L1-L2 (page 670) Sd BESS >>V L1-L2 (page 1116)
Setpoint options:

BESS <V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables BESS <V Protection.
Behavior of protection is adjusted via setpoints BESS <V (page 444) and BESS <V Delay (page 445)
When BESS voltage drops below limit set by BESS <V (page 444) for time longer than BESS <V Delay
(page 445) appropriate alarm is activated.
Value Alarm
BESS Voltage L1-N (page 670) Sd BESS <V L1-N (page 1118)
BESS Voltage L1-L2 (page 670) Sd BESS <V L1-L2 (page 1119)
BESS Voltage L2-L3 (page 671) Sd BESS <V L2-L3 (page 1119)
Setpoint options:
BESS V Unbalance Protection

Range [units]
Step [-]
Description

This setpoint enables or disables BESS V Unbalance Protection.
Behavior of protection is adjusted via setpoints BESS V Unbalance (page 445) and BESS V
Unbalance Delay (page 445). When relative difference between BESS voltages is over setpoint BESS
V Unbalance (page 445) for time longer than BESS V Unbalance Delay (page 445) alarm Sd BESS V
Unbalance Ph-N (page 1120) or Sd BESS V Unbalance Ph-Ph (page 1120) is activated.
371)
Connection
type (page Compared values (maximum difference)
371)
BESS Voltage L1-N (page 670), BESS Voltage L2-N (page 670) and BESS
Voltage L3-N (page 670)
3Ph4Wire OR
BESS Voltage L1-L2 (page 670), BESS Voltage L2-L3 (page 671) and
BESS Voltage L3-L1 (page 671)
High Leg D
3Ph3Wire
BESS Voltage L1-N (page 670), BESS Voltage L2-N (page 670) and BESS
SplitPhase
Voltage L3-N (page 670)
Setpoint options:
Mains >V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables Mains >V Protection.

Behavior of protection is adjusted via setpoints Mains >V (page 514), Mains >V Delay (page 514) and
Mains >V Hys (page 515). When Mains voltage exceeds limit set by Mains >V (page 514) for period
longer than Mains >V Delay (page 514) relevant history records is written to the history and MCB is
opened if:
Controller Mode (page 378) = OFF
Controller Mode (page 378) = MAN
and Breaker state (page 778) = ParalOper
Controller Mode (page 378) = AUTO
Return from Mains >V can have hysteresis set by Mains >V Hys (page 515).
Value History Record

Mains/Bus Voltage L1-N (page 731) MAINS/BUS >V L1-N (PAGE 1135)
Mains/Bus Voltage L1-L2 (page 732) MAINS/BUS >V L1-L2 (PAGE 1137)
Setpoint options:

Mains >>V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables Mains >>V Protection.
Behavior of protection is adjusted via setpoints Mains >>V (page 515), Mains >>V Delay (page 516)
and Mains >>V Hys (page 516). When Mains voltage exceeds limit set by Mains >>V (page 515) for
period longer than Mains >>V Delay (page 516) relevant history records is written to the history and
MCB is opened if:
Return from Mains >>V can have hysteresis set by Mains >>V Hys (page 516).

Mains/Bus Voltage L1-N (page 731) MAINS/BUS >>V L1-N (PAGE 1139)
Mains/Bus Voltage L1-L2 (page 732) MAINS/BUS >>V L1-L2 (PAGE 1141)
Setpoint options:

Mains 10min Avg >V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables Mains 10min Avg >V Protection.
Behavior of protection is adjusted via setpoint Mains 10min Avg >V (page 517). When measured value
exceeds limit set by Mains 10min Avg >V (page 517) and the Mains 10min Avg >V Delay (page 517)
is elapsed the relevant history records is written to the history and MCB is opened if:

Mains Voltage 10min Avg L1-N (page 741) MP Mains 10minAvg >V L1-N
Mains Voltage 10min Avg L1-L2 (page 743) MP Mains 10minAvg >V L1-L2
Setpoint options:

Mains <V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables Mains <V Protection.
Behavior of protection is adjusted via setpoints Mains <V (page 518), Mains <V Delay (page 518) and
Mains <V Hys (page 519). When Mains voltage drops bellow limit set by Mains <V (page 518) for
period longer than Mains <V Delay (page 518) relevant history records is written to the history and MCB
is opened if:
Return from Mains <V can have hysteresis set by Mains <V Hys (page 519).

Mains/Bus Voltage L1-N (page 731) MAINS/BUS <V L1-N (PAGE 1144)
Mains/Bus Voltage L1-L2 (page 732) MAINS/BUS <V L1-L2 (PAGE 1146)
Setpoint options:

Mains <V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables Mains <<V Protection.
Behavior of protection is adjusted via setpoints Mains <<V (page 519), Mains <<V Delay (page 520)
and Mains <<V Hys (page 520). When Mains voltage drops bellow limit set by Mains <<V (page 519)
for period longer than Mains <<V Delay (page 520) relevant history records is written to the history and
MCB is opened if:
Return from Mains <<V can have hysteresis set by Mains <<V Hys (page 520).

Mains/Bus Voltage L1-N (page 731) MAINS/BUS <<V L1-N (PAGE 1148)
Mains/Bus Voltage L1-L2 (page 732) MAINS/BUS <<V L1-L2 (PAGE 1150)
Setpoint options:

Mains V Unbalance Protection

Range [units]
Step [-]
Description
This setpoint enables or disables Mains V Unbalance Protection.
Behavior of protection is adjusted via setpoints Mains V Unbalance (page 521) and Mains V
Unbalance Delay (page 521). When relative difference between Mains current is over setpoint Mains V
Unbalance (page 521) for time longer than Mains V Unbalance Delay (page 521) alarm Mains/Bus
V Unbalance Ph-N (page 1155) or Mains/Bus V Unbalance Ph-Ph (page 1155) is activated.
371)
Connection type
Compared values (maximum difference)
(page 371)
Mains/Bus Voltage L1-N (page 731), Mains/Bus Voltage L2-N (page
731) and Mains/Bus Voltage L3-N (page 732)
3Ph4Wire OR
Mains/Bus Voltage L1-L2 (page 732), Mains/Bus Voltage L2-L3 (page
732) and Mains/Bus Voltage L3-L1 (page 732)
High Leg D
3Ph3Wire
Mains/Bus Voltage L1-N (page 731), Mains/Bus Voltage L2-N (page
SplitPhase
731) and Mains/Bus Voltage L3-N (page 732)
List of History Records

Mains V Unbalance Ph-N
Mains V Unbalance Ph-Ph
Setpoint options:

Subgroup: Frequency Protection
BESS >f Protection

Range [units]
Step [-]
Description
This setpoint enables or disables BESS >f Protection.
Behavior of protection is adjusted via setpoints BESS >f (page 446) and BESS >f Delay (page 446).
When BESS Frequency (page 670) exceeds maximal accepted frequency for period longer than BESS
>f Delay (page 446) alarm Sd BESS >f (page 1120) is activated.
Note: fmax = Nominal Frequency (page 377) + BESS >f (page 446)
Setpoint options:

BESS <f Protection

Range [units]
Step [-]
Description
This setpoint enables or disables BESS <f Protection.
Behavior of protection is adjusted via setpoints BESS <f (page 447) and BESS <f Delay (page 447).
When BESS Frequency (page 670) drops below minimal accepted frequency for period longer than
BESS <f Delay (page 447) alarm Sd BESS <f (page 1120) is activated.
Note: fmin = Nominal Frequency (page 377) + BESS <f (page 447)
Setpoint options:

Mains >f Protection

Range [units]
Step [-]
Description
This setpoint adjusts the behavior Mains >f Protection.
Behavior of protection is adjusted via setpoints Mains >f (page 522), Mains >f Delay (page 522) and
Mains >f Hys (page 522). When Mains/Bus Frequency (page 731) exceeds maximal accepted
frequency for period longer than Mains >f Delay (page 522)alarm MAINS/BUS >F (PAGE 1153) is
activated.
Return from Mains >f can have hysteresis set by Mains >f Hys (page 522).
Note: fmax = Nominal Frequency (page 377) + Mains >f (page 522)
Setpoint options:

Mains >>f Protection

Range [units]
Step [-]
Description
This setpoint adjusts the behavior Mains >>f Protection.
Behavior of protection is adjusted via setpoints Mains >>f (page 523), Mains >>f Delay (page 523) and
Mains >>f Hys (page 523). When Mains/Bus Frequency (page 731) exceeds maximal accepted
frequency for period longer than Mains >>f Delay (page 523) alarm MAINS/BUS >>F (PAGE 1153) is
activated.
Return from Mains >>f can have hysteresis set by Mains >>f Hys (page 523).
Note: fmax = Nominal Frequency (page 377) + Mains >>f (page 523)
Setpoint options:

Mains <f Protection

Range [units]
Step [-]
Description
This setpoint adjusts the behavior Mains <f Protection.
Behavior of protection is adjusted via setpoints Mains <f (page 524), Mains <f Delay (page 524) and
Mains <f Hys (page 524). When Mains/Bus Frequency (page 731) drops bellow minimal accepted
frequency for period longer than Mains <f Delay (page 524) alarm MAINS/BUS <F (PAGE 1154) is
activated.
Return from Mains <f can have hysteresis set by Mains <f Hys (page 524).
Note: fmin = Nominal Frequency (page 377) - Mains <f (page 524)
Setpoint options:

Mains <<f Protection

Range [units]
Step [-]
Description
This setpoint adjusts the behavior Mains <<f Protection.
Behavior of protection is adjusted via setpoints Mains <<f (page 525), Mains <<f Delay (page 525) and
Mains <<f Hys (page 525). When Mains/Bus Frequency (page 731) drops bellow minimal accepted
frequency for period longer than Mains <<f Delay (page 525) alarm MAINS/BUS <<F (PAGE 1154) is
activated.
Return from Mains <<f can have hysteresis set by Mains <<f Hys (page 525).
Note: fmin = Nominal Frequency (page 377) - Mains <<f (page 525)
Setpoint options:

Subgroup: Bus Meas Error
Bus Meas Error

Range [units]
Step [-]
Description
This setpoint enables or disables Bus Measurement Error protection.
Alarm Stp Bus Meas Error (page 1124) is activated if controller detects a mismatch between the
expected and currently measured voltage on the bus for period longer than 20 s. Mismatch means that
measured voltage is lower/higher than Bus Dead Level (page 376), although the controller receives
information about closed/opened breaker.
Setpoint options:

Subgroup: Earth Fault Current Protection

Earth Fault Current Protection

Range [units]
Step [-]
Description
This setpoint enables or disables Earth Fault Current Protection.
Bbehavior is adjusted via setpoints IDMT Earth Fault Current Sd (page 448) and IDMT Earth Fault
Current Delay (page 449). When the protection is triggered the alarm Sd IDMT Earth Fault Current
(page 1121) is activated.
Igen = Maximum (BESS Current L1 (page 672), BESS Current L2 (page 672), BESS Current L3
(page 672))
Example:
IDMT Earth Fault Current Sd (page 448) = 10 A
Igen [A]
Delay [s]
≤10 A 11 A 20 A
0.1 No Reaction 1 0.1
Reaction Time
1 No Reaction 10 1
[s]
10 No Reaction 100 10

IMPORTANT: The Earth Fault Current Protection and Mains Import Measurement (page
175) shares same physical input ⑰ AUX CURRENT (page 48) . At one moment this input
can be used only for one purpose. The protection will work only if Mains Measurement P
(page 357) and Mains Measurement Q (page 358) != Mains CT.
Setpoint options:
Subgroup: Loss of Mains Protections
Vector Shift Protection

Range [units] Enabled / Parallel Only / Disabled [-]
Step [-]
Description
This setpoint enables or disables the function of the built-in Vector Shift protection.
Behavior of protection is adjusted via setpoints Vector Shift Limit (page 509) and Vector Shift/ROCOF
CB Selector (page 513). When measured vector shift on Mains/Bus Voltage L1-N (page 731) is over
the Vector Shift Limit (page 509), breaker specified in Vector Shift/ROCOF CB Selector (page 513)
is opened and history record Vector Shift is written to the history.
Note: If a vector shift is detected and consequently the MCB is opened, however Mains voltage and
frequency remain in limits, the MCB is reclosed again after Mains Return Delay (page 1), as the
Mains is evaluated as healthy.
Enabled Protection is always active while MCB is closed.

Protection is active only if Breaker state (page 778) = ParalOper i.e. MCB and
Parallel Only
BCB are closed.

ROCOF1 Protection

Step [-]
Description
This setpoint enables or disables the function of the built-in ROCOF1 Protection.
Behavior of protection is adjusted via setpoints ROCOF1 Windows Length (page 509), ROCOF1 df/dt
(page 510) and Vector Shift/ROCOF CB Selector (page 513).
When measured ROCOF1 (page 744) on Mains/Bus Frequency (page 731) is over ROCOF1 df/dt
(page 510) in respective period given by ROCOF1 Windows Length (page 509), breaker specified in
Vector Shift/ROCOF CB Selector (page 513) is opened and history record ROCOF is written to the
history. Maximal ROCOF is stored in Max ROCOF1 (page 745) which is reset every time when the
breaker is closed again.
Note: If a ROCOF is detected and consequently the MCB is opened, however Mains voltage and
frequency remain in limits, the MCB is reclosed again after MCB Close Delay (page 526), as the Mains is
evaluated as healthy.

Parallel Only
BCB are closed.

ROCOF2 Protection

Step [-]
Description
(page 511) in respective time given by ROCOF2 Windows Length (page 510), breaker specified in
frequency remain in limits, the MCB is reclosed again after MCB Close Delay (page 526), as the Mains
is evaluated as healthy.

Protection is active only if Breaker state (page 778) = ParalOper i.e. MCB
Parallel Only
and BCB are closed.

ROCOF3 Protection

Step [-]
Description

Parallel Only
BCB are closed.

ROCOF4 Protection

Step [-]
Description

Protection is active only if Breaker state (page 778) = ParalOper i.e. MCB
Parallel Only
and BCB are closed.

Subgroup: SOC Protection
BESS <SOC Protection

Range [units]
Step [-]
Setpoint visibility Only if the setpoint BESS (page 365) = Installed
Description
This setpoint enables or disables BESS <SOC Protection. When BESS SOC (page 673) exceeds limit
set by the setpoint BESS <f Delay (page 449) the alarm Wrn SOC Low Alarm (page 1101).
Setpoint options:
BESS >SOC Protection

Range [units]
Step [-]
Description
This setpoint enables or disables BESS >SOC Protection. When BESS SOC (page 673) exceeds limit
set by the setpoint SOC High Alarm (page 450) the alarm Wrn SOC High Alarm (page 1101).
Setpoint options:

BESS <<SOC Protection

Range [units]
Step [-]
Description
This setpoint enables or disables BESS <<SOC Protection. When BESS SOC (page 673) exceeds limit
set by the setpoint SOC Critical Low (page 450) the alarm Sd SOC Critical Low (page 1122).
Setpoint options:
BESS >>SOC Protection

Range [units]
Step [-]
Description
This setpoint enables or disables BESS >>SOC Protection. When BESS SOC (page 673) exceeds limit
set by the setpoint SOC Critical High (page 451) the alarm Sd SOC Critical High (page 1122).
Setpoint options:

BESS SOC Not Configured

Step [-]
Description
This setpoint enables or disables configuration of BESS SOC.
BESS SOC Not Available

Step [-]
Description
This setpoint enables or disables BESS SOC.

Group: Load Shedding
Subgroup: Load Shedding
Load Shedding Active
Setpoint group Load Shedding Related FW 1.3.0

Range [units] Disabled / Island only / IsL+Trip paral / All the time [-]
Step [-]
Setpoint visibility Allways
Description
This setpoint adjusts the activation of the Load Shedding (page 170) function.
Disabled – Function is disabled.
Island only – Function is active when Breaker state (page 778) = IslOper or Breaker state
(page 778) = MultIslOp.
Load shedding outputs (page 170) are closed/opened one by one in island operations
All Load shedding outputs (page 170) are closed at once when the BESS comes into the
island operation if MCB and BCB were opened -> BESS started -> BCB closed.
IsL+Trip paral – Function behaves same as Load Shedding Active = Island only and adds load
shedding when Breaker state (page 778) is changed from ParalOper/MultParOp to
IslOper/MultIslOp .
Load shedding outputs (page 170) are closed/opened one by one in island operations
All Load shedding outputs (page 170) are closed at once when the BESS changes into
island operation state in this way: MCB and BCB were opened -> BESS started -> BCB closed.
All Load shedding outputs (page 170) are closed at once when the BESS changes into
island operation state in this way: MCB and BCB were closed -> MCB opened.
All the time – Function is active regardless of Breaker state (page 778).
All Load shedding outputs (page 170) are never tripped at once when BCB is closed into
parallel operation.
All Load shedding outputs (page 170) are tripped at once when BCB is closed into island
operation.

Load Shedding Level

Load Reconnection Level (page 594) .. 200 [%] of Installed Power (page 368)
Range [units]
or Nominal power (page 368)
Setpoint visibility Only if Load Shedding Active (page 592) != Disabled
Description
This setpoint adjusts decisive level for load disconnection during Load Shedding (page 170) function.
Load Shedding Delay

Range [units] 0.0..600.0 [s]
Step 1s
Description
This setpoint adjusts the delay between load disconnections during Load Shedding (page 170)
function.

Load Reconnection Level

20 % of Installed Power (page
Default value 368) or Nominal power (page Force value YES
368)
Description
This setpoint adjusts the decisive level between load reconnection during Load Shedding (page 170)
function.
Load Reconnection Delay

Range [units] 0..600 [s]
Step 1s
Description
This setpoint adjusts the delay between load reconnection during Load Shedding (page 170) function.

Auto Load Reconnection

Step [-]
Description
This setpoint enables/disables Automatic Load Shedding (page 170).
Rising edge of LBI MANUAL LOAD RECONNECTION (PAGE 901) lowers the load
Disabled reduction stage by one while BESS P (page 664) drops under Load
Reconnection Level (page 594).
Load reduction stage is lowered by one when BESS P (page 664) drops under
Enabled Load Reconnection Level (page 594) and period of Load Reconnection Delay
(page 594) elapsed from last load reduction stage lowering.
Group: User Buttons
Subgroup: User Buttons
User Button 1
Setpoint group User Buttons Related FW 1.3.0

Range [units] COMMAND / MAN ON / MAN OFF [-]
Default value COMMAND Force value YES
Step [-]
Description
This setpoint adjusts behavior of User Button 1 which is part of User Buttons (page 220).
COMMAND User Button 1 is controlled by command from External display (page 79).
Value of the User Button 1 is still 1.
Note: You should always switch from MAN ON to MAN OFF before
MAN ON
switching to COMMAND, otherwise value of the User Button 1 will be 1 until
command is received.
MAN OFF Value of the User Button 1 is still 0.

User Button 2

Step [-]
Description
MAN ON
User Button 3

Step [-]
Description
MAN ON

User Button 4

Step [-]
Description
MAN ON
User Button 5

Step [-]
Description
MAN ON

User Button 6

Step [-]
Description
COMMAND User Button 6 is controlled by command fromExternal display (page 79).

MAN ON
User Button 7

Step [-]
Description
MAN ON

User Button 8

Step [-]
Description
MAN ON
User Button 9

Step [-]
Description
MAN ON

User Button 10

Step [-]
Description
MAN ON

User Button 11
Step [-]
Description
MAN ON

User Button 12

Step [-]
Description
MAN ON
User Button 13

Step [-]
Description
MAN ON

User Button 14

Step [-]
Description
MAN ON
User Button 15

Step [-]
Description
MAN ON

User Button 16

Step [-]
Description
MAN ON
User Button 17

Step [-]
Description
MAN ON

User Button 18

Step [-]
Description
MAN ON
User Button 19

Step [-]
Description
MAN ON

User Button 20

Step [-]
Description
MAN ON
User Button 21

Step [-]
Description
MAN ON

User Button 22

Step [-]
Description
MAN ON
User Button 23

Step [-]
Description
MAN ON

User Button 24

Step [-]
Description
MAN ON
User Button 25

Step [-]
Description
MAN ON

User Button 26

Step [-]
Description
MAN ON
User Button 27

Step [-]
Description
MAN ON

User Button 28

Step [-]
Description
MAN ON
User Button 29

Step [-]
Description
MAN ON

User Button 30

Step [-]
Description
MAN ON
User Button 31

Step [-]
Description
MAN ON

User Button 32

Step [-]
Description
MAN ON
Group: Scheduler
Subgroup: Time & Date
Time
Setpoint group Scheduler Related FW 1.3.0

Range [units] HH:MM:SS [-]
Default value 0:0:0 Force value NO
Step [-]
Description
Real time clock adjustment.

Date

Range [units] YYYY-MM-DD [-]
Default value 2017-01-01 Force value NO
Step [-]
Description
Actual date adjustment.
Time Stamp Period

Range [units] Off / 1 .. 240 [min]
Default value 60 min Force value YES
Step 1 min
Description
Time interval for periodic history records.
Note: History record is made only when BESS is running.

Time Zone
Scheduler; CM-4G-
GPS
Default value GMT+1:00 Force value NO
Step [-]
Description
DST Switching Mode

Range [units] Disabled / Auto / Manual
Step [-]
Description
This setpoints is used to enable or disable daylight saving time.
AUTO - activation / deactivation of the DST, and changing of the RTC Time value accordingly is
performed automatically by the controller. The user always sees valid local time without any action
from his side.
MANUAL - activation, and deactivation of the DST is performed manually by the user via the
setpoint Time mode. Changing of the RTC Time value accordingly is then performed
automatically by the controller. So the user does not need to readjust the RTC time, he only needs
to select the proper Time Mode (page 614).
DISABLED - Time mode is fixedly set to STD and the function does not perform any changes of
RTC time.

Time Mode

Range [units] STD / DST
Default value STD Force value NO
Step [-]
Setpoint visibility Only if DST Switching Mode = Manual
Description
In manual DST Switching Mode (page 613) this input is used to adjust the actual time mode. If DST
Switching Mode is set to any other option, this input is not taken into account.
DST Period Rule

Range [units] Australia / Chile / Europe / Mexico / New Zealand / Paraguay / US/Canada
Default value Europe Force value NO
Step [-]
Setpoint visibility Only if DST Switching Mode = Auto
Description
Selection of the rule that will be applied for the calculation of the DST validity period.

Premortem History Period

Range [units] 100 ms, 300 ms, 500 ms, 1 s, 3 s
Step [-]
Description
This setpoint adjusts the period with which premortem history (fast history) records are written.
Note: There is always buffer for 60 records, no matter what the period is.
The fast history running in background is mirrored into the controller history records when a second level
alarm occurs. Alarms that initialized flipping of the post-mortem history are: Shut down (SD), Slow stop
(STP), Overspeed, Short Current, Breaker open & cool-down (BOC), Low power (LOP), Off load (OFL).
Premortem history contains the same values in the history as the configuration done by configuration tool
(GenConfig, InteliConfig). When any new alarm (SD, BOC, LOP, OFL, STP, Overspeed, short current)
appears for the second time, only the new history records are added into the controller history log.
Subgroup: Sunrise/Sunset
Sunrise/Sunset Function

Range [units] N/A [-]
Step N/A [-]
Description
This setpoint enables the Sunrise/Sunset function.

Sunrise/Sunset Latitude

Range [units] [° N]
Default value -90 ° N Force value YES
Step 0,0001 ° N
Setpoint visibility Only if Sunrise/Sunset Function (page 615) = Enabled
Description
This setpoint is automatically set, if the coordinates from the GPS module are valid. From this setpoint
and the setpoint Sunrise/Sunset Longtitude (page 616) are calculated values in function
Sunrise/Sunset.
Sunrise/Sunset Longtitude

Range [units] [° E]
Default value -180 ° E Force value YES
Step 0,0001 ° E
Setpoint visibility Only if Sunrise/Sunset Function (page 615) = Enabled
Description
This setpoint is automatically set, if the coordinates from the GPS module are valid. From this setpoint
and the setpoint Sunrise/Sunset Latitude (page 616) are calculated values in function Sunrise/Sunset.

Subgroup: Timer 1
Timer 1 Function

Range [units] Disabled / Manual On / No Func / Mode OFF [-]
Default value Disable Force value YES
Step [-]
Description
This setpoint defines and enables the function of the Timer 1. The functions which are supposed to
change the Controller Mode requires controller running in AUTO mode. The activation condition of the
Timer is configured via setpoint Timer 1 Setup (page 618).
Once the Timer is activated the LBO EXERCISE TIMER 1 (PAGE 946) is closed regardless of chosen timer
function. If the CU is switched off when the Timer should be activated, the Timer will be activated
immediately after the CU is switched on if the Timer condition is still fulfilled.
IMPORTANT: The LBO is activated always when the Timer should be activated e.g. even
when controller is in different mode than AUTO.
IMPORTANT: In case that Timer 1, Timer 2, etc. should be activated at the same time, the
Timer with selected higher priority function is executed.
Disabled The Timer is disabled.

Manual On The Timer is disabled but his binary output is activated (can be used for testing
purposes).
No Func There is no any other function, only binary output of the Timer is activated once the
condition is fulfilled.
Mode OFF The binary output of the Timer is internally connected to the Remote OFF binary
input.

Timer 1 Setup

Default value N/A [-] Force value NO
Step N/A [-]
Setpoint visibility Only if Timer 1 Function (page 617) != Disabled or Manual On
Description
Use this setpoint to setup the exercise Timer 1. See Exercise Timers (page 149) for step by step
manual.

Subgroup: Timer 2
Timer 2 Function

Default value Disabled [-] Force value YES
Step [-]
Description

purposes).
input.

Timer 2 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 3
Timer 3 Function

Step [-]
Description

purposes).
input.

Timer 3 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 4
Timer 4 Function

Step [-]
Description

purposes).
input.

Timer 4 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 5
Timer 5 Function

Step [-]
Description

purposes).
input.

Timer 5 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 6
Timer 6 Function

Step [-]
Description

purposes).
input.

Timer 6 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 7
Timer 7 Function

Step [-]
Description

purposes).
input.

Timer 7 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 8
Timer 8 Function

Step [-]
Description

purposes).
input.

Timer 8 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 9
Timer 9 Function

Step [-]
Description

purposes).
input.

Timer 9 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 10
Timer 10 Function

Step [-]
Description

purposes).
input.

Timer 10 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 11
Timer 11 Function

Step [-]
Description

purposes).
input.

Timer 11 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 12
Timer 12 Function

Step [-]
Description

purposes).
input.

Timer 12 Setup

Step N/A [-]
Description
manual.
Group: Maintenance Timers
Subgroup: Maintenance Timer 1
Maintenance Timer 1 RunHours
Setpoint group Maintenance Timers Related FW 1.3.0

Range [units] 1 .. 9999 [h] / Disabled
Step 1h
Description
This setpoint defines how much BESS running hours (Running Hours (page 771)) needs to be counted
down by the maintenance timer until value Maintenance Timer 1 RunHours (page 772) reach zero and
alarm Maintenance 1 RunHours (page 1156) with LBO AL MAINTENANCE 1 (PAGE 923) are activated.
Once the alarm is activated the timer continue counting down to negative values. The value 10 000 will
disable the Maintenance Timer function and the counter value disappears from controllers statistics.
Note: Setpoint itself does not change during countdown of timer.

Maintenance Timer 1 Interval

Range [units] 1 .. 36 [mo] / Disabled
Step 1 mo
Description
This setpoint defines how much months needs to be counted down by the maintenance timer until value
Maintenance Timer 1 Interval (page 773) reach zero and alarm Maintenance 1 Interval (page 1156)
with LBO AL MAINTENANCE 1 (PAGE 923) are activated.
Once the alarm is activated the timer continue counting down to negative values. The value 37 will
Maintenance Timer 1 Protection

Range [units] Warning / Stp [-]
Default value Warning Force value NO
Step [-]
Description
This setpoint defines type of the maintenance timer alarm (Wrn / Stp) for both setpoints / alarms
Maintenance Timer 1 RunHours (page 640) / Maintenance 1 RunHours (page 1156) and
Maintenance Timer 1 Interval (page 641) / Maintenance 1 Interval (page 1156).


Step 1h
Description

Step 1 mo
Description


Step [-]
Description

Step 1h
Description


Step 1 mo
Description

Step [-]
Description


Step 1h
Description

Step 1 mo
Description


Step [-]
Description
Group: Geo-Fencing
Subgroup: Geo-Fencing
Geo-Fencing
Setpoint group Geo-Fencing Related FW 1.3.0

Range [units] Disable/Enable/LBI Enable
Default value Disable Force value
Step
Setpoint visibility Only if relevant modules is installed.
Description
This setpoint enables or disables geo-fencing function.

Subgroup: Position
Home Latitude

Range [units] -90,0000..90,0000 []
Default value 0,0000 Force value
Step 0,0001
Setpoint visibility Only if relevant module is installed.
Description
This setpoint adjust latitude of "home" position. Home is position where BESS should runs. Positions on
north hemisphere have positive value, position on south hemisphere have negative value.
Note: This value with Home Latitude are used for counting Fence Radius 1 and Fence Radius 2.
Note: This value can be also obtained automatically via logical binary input Geo Home Position. In
case of activation of this binary input for at least 2 seconds, setpoint will be adjusted automatically
from actual coordinates from GPS signal.
Home Longitude

Range [units] -180,0000..180,0000 []
Default value 0,0000 Force value
Step 0,0001
Description
This setpoint adjust longitude of "home" position. Home is position where BESS should runs. Positions
on east hemisphere have positive value, position on west hemisphere have negative value.
Note: This value with Home Longitude are used for counting Fence Radius 1 and Fence Radius 2.
Note: This value can be also obtained automatically via logical binary input Geo Home Position. In
case of activation of this binary input for at least 2 seconds, setpoint will be adjusted automatically
from actual coordinates from GPS signal.

Subgroup: Fence 1
Fence 1 Protection

Range [units] HistRecOnl/Wrn/Sd/BOC
Default value HistRecOnl Force value
Step
Description
Protection type for geo-fencing 1 protection. Fence of circle area is adjusted by setpoint Fence 1 Radius
(page 648). Delay for protection is adjusted by setpointFence 1 Delay (page 649).
Protection Types:
HistRecOnl: Position of BESS is only measured and displayed on the LCD screen but not used for
protection. History record is made if position is out of Fence 1 Radius (page 648).
Wrn: Position of gen-set is used for warning protection only. Protection is activated when position of
the gen-set is out of Fence 1 Radius (page 648).
Sd: Position of BESS is used for shutdown protection. Protection is activated when position of the
BESS is out of Fence 1 Radius (page 648).
BOC:Position of gen-set is used for BOC (Breaker Open and Cooling) protection. Protection is
activated when position of the BESS is out of Fence 1 Radius (page 648).
Note: Protection is activated also when GPS signal is lost for Fence 1 Delay (page 649).
Fence 1 Radius

Range [units] 0..99,9 [km]
Default value 0 km Force value
Step 0,1 km
Description
Radius for circle area 1. When the BESS leaves this area,Fence 1 Protection (page 648) is activated
afterFence 1 Delay (page 649).

Fence 1 Delay

Default value 0s Force value
Step 1s
Description
Delay for Fence 1 Protection (page 648).
Subgroup: Fence 2
Fence 2 Protection

Range [units] HistRecOnl/Wrn/Sd/BOC
Default value HistRecOnl Force value
Step
Description
Protection type for geo-fencing 1 protection. Fence of circle area is adjusted by setpoint Fence 2 Radius
(page 650). Delay for protection is adjusted by setpointFence 2 Delay (page 650).
Protection Types:
HistRecOnl: Position of BESS is only measured and displayed on the LCD screen but not used for
protection. History record is made if position is out of Fence 2 Radius (page 650).
Wrn: Position of BESS is used for warning protection only. Protection is activated when position of the
Sd: Position of BESS is used for shutdown protection. Protection is activated when position of the
BOC:Position of BESS is used for BOC (Breaker Open and Cooling) protection. Protection is
activated when position of the BESS is out of Fence 1 Radius (page 648).
Note: Protection is activated also when GPS signal is lost forFence 2 Delay (page 650).

Fence 2 Radius

Range [units] 0..99,9 [km]
Default value 0 km Force value
Step 0,1 km
Description
Radius for circle area 1. When the BESS leaves this area,Fence 1 Protection (page 648) is activated
afterFence 1 Delay (page 649).
Fence 2 Delay

Default value 0s Force value
Step 1s
Description
Delay forFence 2 Protection (page 649).

Group: CM-4G-GPS
Subgroup: RTC Synchronization
Time Zone
Scheduler; CM-4G-
GPS
Default value GMT+1:00 Force value NO
Step [-]
Description

9.1.4 Values
What values are:
Values (or quantities) are analog or binary data objects, measured or computed by the controller, that are
intended for reading from the controller screen, PC, MODBUS, etc. Values are organized into groups
according to their meaning.
For full list of values go to the chapter List of values (page 654)
Invalid flag
If valid data is not available for a particular value, the invalid flag is set to it. This situation may be due to the
following:
The value is not being evaluated in the scope of the current application and configuration.
Sensor fail has been detected on an analog input.
The configured ECU or extension module does not provide the particular value.
The communication with the ECU or extension module is interrupted.
A value containing the invalid flag is displayed as “####” in InteliConfig and on the controller screen. If such a
value is read out via MODBUS, it will contain the data 32768 in the case of signed values and 65535 in the
case of unsigned values.
List of group of values

Group: BESS 664
Group: PV 675
Group: WT 702
Group: Renewables 716
Group: Hybrid System 717
Group: Gensets 718
Group: Mains 719
Group: Load 720
Group: Mains/Bus 731
Group: Power Management 748
Group: Frequency/Load Control 753
Group: Voltage/PF Control 756
Group: Controller I/O 759
Group: Statistics 762
Group: Info 777
Group: User Buttons 789
Group: Log Bout 789
Group: Scheduler 792
Group: Ethernet 797
Group: PLC 806

Group: Remote Control 829
Group: DIST-IN 1-32 832
Group: DIST-IN 33-64 839
Group: SH Modules 846
Group: Virtual Shared OUT 854

List of values
Group: BESS 664 BESS V Unbalance Ph-Ph 672

BESS P 664 BESS Current L1 672
BESS P L1 664 BESS Current L2 672
BESS P L2 664 BESS Current L3 672
BESS P L3 664 BESS Current Unbalance 673
BESS Q 665 Earth Fault Current 673
BESS Q L1 665 BESS Nominal Capacity 673
BESS Q L2 665 BESS SOC 673
BESS Q L3 665 BESS Temperature 674
BESS S 666 Slip Frequency 674
BESS S L1 666 Slip Angle 674
BESS S L2 666 BESS P 10min Avg 674
BESS S L3 666 BESS Q 10min Avg 675
BESS Power Factor 667 BESS S 10min Avg 675
BESS Load Character 667 Group: PV 675
BESS Power Factor L1 667 Subgroup: PV Aggregated 675
BESS Load Character L1 667 PV Nominal P 675
BESS Power Factor L2 667 PV Actual P 676
BESS Load Character L2 668 PV Actual Q 676
BESS Power Factor L3 668 PV Actual S 676
BESS Load Character L3 668 PV Actual Power Factor 676
BESS Voltage THD L1 668 PV Actual Load Character 677
BESS Voltage THD L2 669 Curtailment Output 677
BESS Voltage THD L3 669 Subgroup: PV Curtailment Counter 677
BESS Current THD L1 669 PV Max P 677
BESS Current THD L2 669 PV Curtailed P 677
BESS Current THD L3 669 PV Curtailed P Relative 678
BESS Frequency 670 Subgroup: PV 1 678
BESS Voltage L1-N 670 PV 1 Nominal P 678
BESS Voltage L2-N 670 PV 1 Actual P 678
BESS Voltage L3-N 670 PV 1 Actual Q 678
BESS Voltage L1-L2 670 PV 1 Actual S 679
BESS Voltage L2-L3 671 PV 1 Actual Power Factor 679
BESS Voltage L3-L1 671 PV 1 Actual Load Character 679
BESS Voltage 671 Subgroup: PV 2 679
BESS V Unbalance Ph-N 671 PV 2 Nominal P 679

PV 2 Actual P 680 PV 7 Actual Load Character 688
PV 2 Actual Q 680 Subgroup: PV 8 688
PV 2 Actual S 680 PV 8 Nominal P 688
PV 2 Actual Power Factor 680 PV 8 Actual P 689
PV 2 Actual Load Character 681 PV 8 Actual Q 689
Subgroup: PV 3 681 PV 8 Actual S 689
PV 3 Nominal P 681 PV 8 Actual Power Factor 689
PV 3 Actual S 682 PV 9 Actual P 690
PV 3 Actual Power Factor 682 PV 9 Nominal P 690

PV 13 Actual Q 696 WT 1 Actual Power Factor 705
PV 13 Actual S 697 WT 1 Actual Load Character 705
PV 13 Actual Power Factor 697 Subgroup: WT 2 705
PV 13 Actual Load Character 697 WT 2 Nominal P 705
Subgroup: PV 14 697 WT 2 Actual P 705
PV 14 Nominal P 697 WT 2 Actual Q 706
PV 14 Actual P 698 WT 2 Actual S 706
Group: WT 702 WT 5 Actual P 710
Subgroup: WT Aggregated 702 WT 5 Actual Q 710
WT Nominal P 702 WT 5 Actual S 710
WT Actual P 702 WT 5 Actual Power Factor 711
WT Actual Q 702 WT 5 Actual Load Character 711
WT Actual S 703 Subgroup: WT 6 711
WT Actual Power Factor 703 WT 6 Nominal P 711
WT Actual Load Character 703 WT 6 Actual P 711
Curtailment Output 703 WT 6 Actual Q 712
Subgroup: WT 1 704 WT 6 Actual S 712
WT 1 Nominal P 704 WT 6 Actual Power Factor 712
WT 1 Actual P 704 WT 6 Actual Load Character 712
WT 1 Actual Q 704 Subgroup: WT 7 713
WT 1 Actual S 704 WT 7 Nominal P 713

WT 7 Actual P 713 Pmom 721
WT 7 Actual Q 713 Test Frequency 721
WT 7 Actual S 713 P Over Frequency Curve 721
WT 7 Actual Power Factor 714 P Under Frequency Curve 722
WT 7 Actual Load Character 714 Q(Um) Curve 722
Subgroup: WT 8 714 Qref/Ulim Curve 722
WT 8 Nominal P 714 Q(P) Curve 723
WT 8 Actual P 714 PF(P) Curve 723
WT 8 Actual Q 715 P(Um) Curve 723
WT 8 Actual S 715 Pmom/Pave 724
WT 8 Actual Power Factor 715 Load Reduction 1 Occurrence 724
WT 8 Actual Load Character 715 Load Reduction 2 Occurrence 724
Group: Renewables 716 Load Reduction 3 Occurrence 724
REN Nominal P 716 Load Reduction 4 Occurrence 725
REN Actual P 716 Load Reduction 1 hrs Actual Month 725
REN Actual Q 716 Load Reduction 1min Actual Month 725
REN Actual S 716 Load Reduction 1 hrs Last Month 725
REN Actual Power Factor 717 Load Reduction 1 min Last Month 726
REN Actual Load Character 717 Load Reduction 1 hrs Accumulated 726
Group: Hybrid System 717 Load Reduction 1 min Accumulated 726
Total P 717 Load Reduction 2 hrs Actual Month 726
Total Q 717 Load Reduction 2 min Actual Month 727
Total S 718 Load Reduction 2 hrs Last Month 727
Total PF 718 Load Reduction 2 min Last Month 727
Total Load Character 718 Load Reduction 2 hrs Accumulated 727
Group: Gensets 718 Load Reduction 2 min Accumulated 728
Gensets P 718 Load Reduction 3 hrs Actual Month 728
Gensets Q 719 Load Reduction 3 min Actual Month 728
Gensets Power Factor 719 Load Reduction 3 hrs Last Month 728
Gensets Load Character 719 Load Reduction 3 min Last Month 729
Group: Mains 719 Load Reduction 3 hrs Accumulated 729
Mains Import P Monitoring 719
Load Reduction 3 min Accumulated 729
Mains Import Q Monitoring 719
Load Reduction 4 hrs Actual Month 729
Group: Load 720
Load Reduction 4 min Actual Month 730
Load P 720
Load Reduction 4 hrs Last Month 730
Load Q 720
Load Reduction 4 min Last Month 730
Load Power Factor 720
Load Reduction 4 hrs Accumulated 730
Load Character 720
Load Reduction 4 min Accumulated 731
Group: Mains/Bus 731
Grid Codes Version 721

Mains/Bus Frequency 731 Mains Current THD L1 740
Mains/Bus Voltage L1-N 731 Mains Current THD L2 740
Mains/Bus Voltage L2-N 731 Mains Current THD L3 740
Mains/Bus Voltage L3-N 732 Max Vector Shift 740
Mains/Bus Voltage L1-L2 732 Mains Voltage 10min Avg L1-N 741
Mains/Bus Voltage 732 Mains Voltage 1min Avg L1-N 742
Mains/Bus V Unabalance Ph-N 733 Mains Voltage 1min Avg L2-N 742
Mains/Bus V Unbalance Ph-Ph 733 Mains Voltage 1min Avg L3-N 742
+Mains/Bus Voltage 733 Mains Voltage 10min Avg L1-L2 743
+Mains/Bus Voltage Relative 733 Mains Voltage 10min Avg L2-L3 743
Mains L1 Current 734 Mains Voltage 10min Avg L3-L1 743
Mains Import P 734 ROCOF1 744
Mains P L1 735 Max ROCOF1 745
Mains P L2 735 ROCOF2 745
Mains P L3 735 Max ROCOF2 746
Mains Import Q 735 ROCOF3 746
Mains Import Q L1 735 Max ROCOF3 747
Mains Import Q L2 736 ROCOF4 747
Mains Import Q L3 736 Max ROCOF4 748
Mains/BusMainsBus Left Import S 736 Group: Power Management 748
Mains S L1 736 BESS Priority 748
Mains S L2 736 Actual Reserve 748
Mains S L3 737 Start Reserve 749
Mains PF 737 Stop Reserve 749
Mains Load Character 737 Dynamic Spinning Reserve 749
Mains Power Factor L1 737 Dynamic Spinning Reserve Offset 749
Mains Load Character L1 738 Actual Relative Reserve 750
Mains Power Factor L2 738 Start Relative Reserve 750
Mains Load Character L2 738 Stop Relative Reserve 750
Mains Power Factor L3 738 Actual Active Power In PM 750
Mains Load Character L3 739 Actual Reactive Power In PM 750
Mains Voltage THD L1 739 Running Nominal Power In PM 751
Mains Voltage THD L2 739 Running Nominal Power Of All 751
Mains Voltage THD L3 739 Available Nominal Power 751

Minimal Running Nominal Power 751 PV Daily kWh 763
Actual Power Band 32 752 PV Total Curtailed kWh 763
Actual Power Band 64 752 PV Curtailed Annual kWh 763
Next Power Band 32 752 PV Curtailed Monthly kWh 763
Next Power Band 64 753 PV Curtailed Weekly kWh 763
Group: Frequency/Load Control 753 PV Curtailed Daily kWh 764
BESS Required P Target 753 WT kWh 764
BESS Required P 753 WT Annual kWh 764
BESS Required Relative P 754 WT Monthly kWh 764
Frequency Regulator Output 754 WT Weekly kWh 765
BESS Frequency Required 754 WT Daily kWh 765
BESS Frequency Offset 754 Batt. Charging Cycles 765
BESS P Required 755 Batt. Discharge kWh 765
System Load Control 755 Batt. Discharge Annual kWh 766
Group: Voltage/PF Control 756 Batt. Discahrge Month kWh 766
System PF/Q Control 756 Batt. Discharge Week kWh 766
BESS Required Q 757 Batt. Discharge Daily kWh 766
BESS Required Qrel Lim 757 Batt. Charge kWh 767
BESS Required Relative Q 757 Batt. Charge Annual kWh 767
BESS Required PF 757 Batt. Charge Month kWh 767
BESS Required PF Character 757 Batt. Charge Week kWh 767
Voltage Regulator Output 758 Batt. Charge Daily kWh 768
Voltage Request 758 Hours Of Silent 768
BESS Voltage Required 758 Carbon Offset Equivalent 768
BESS Voltage Offset 758 Gen kWh 768
BESS Q Required % 759 Gen Annual kWh 768
Group: Controller I/O 759 Gen Daily kWh 769
Battery Voltage 759 Gen Monthly kWh 769
CU-AIN-01 759 Gen Weekly kWh 769
CU-AIN-02 759 Fuel Used 769
CU-AIN-03 760 Fuel Annual 769
CU-AIN-04 760 Fuel Monthly 770
Binary Inputs 760 Fuel Weekly 770
E-STOP 761 Fuel Daily 770
Binary Outputs 761 PCC kWh 770
Group: Statistics 762 PCC kVArh 770
PV kWh 762
PCC kVAh 771
PV Annual kWh 762
Mains kWh 771
PV Monthly kWh 762
Mains kVArh 771
PV Weekly kWh 762

Running Hours 771 Hot Swap Redundancy Status 784
Conditioned Running Hours 1 772 CAN16 785
Conditioned Running Hours 2 772 CAN32 785
Num Starts 772 CAN48 785
Maintenance Timer 1 RunHours 772 CAN64 786
Maintenance Timer 1 Interval 773 Reg16 786
Maintenance Timer 2 RunHours 773 Reg32 786
Maintenance Timer 2 Interval 773 Reg48 787
Maintenance Timer 3 RunHours 773 Reg64 787
Maintenance Timer 3 Interval 774 Gen Loaded 16 787
Maintenance Timer 4 RunHours 774 Gen Loaded 32 788
Maintenance Timer 4 Interval 774 Gen Loaded 48 788
Num E-Stops 774 Gen Loaded 64 788
Shutdowns 775 Group: User Buttons 789
Fast Pulse Counter 1 775 User Buttons 789
Fast Pulse Counter 2 775 Group: Log Bout 789
Pulse Counter 1 776 Log Bout 1 789
Pulse Counter 2 776 Log Bout 2 789
Group: Info 777 Log Bout 3 790

Application Mode 777 Log Bout 4 790
Controller Mode 777 Log Bout 5 790
Load Shedding Status 777 Log Bout 6 790
BESS state 778 Log Bout 7 790
Breaker state 778 Log Bout 8 791
Timer Text 778 Log Bout 9 791
Connection Type 778 Log Bout 10 791
Timer Value 778 Log Bout 11 791
ID String 779 Log Bout 12 791
FW Version 779 Log Bout 13 792
Application 779 Log Bout 14 792
FW Branch 779 Group: Scheduler 792
CAN Intercontroller Comm Mode 780 Time 792
CAN Intercontroller Comm Redundancy 780 Date 792
SD Card Status 781 Time Mode 793
SD Card Capacity 781 Sunrise Time 793
SD Card Free Space 781 Sunset Time 793
History Lifetime 782 Time To Sunrise 793
Forced Value Status 782 Time To Sunset 794
SW Key Feature List 783 Exercise Timer 1 794

Exercise Timer 2 794

Exercise Timer 3 794 ETH Interface Status 806
Exercise Timer 4 795 Group: PLC 806
Exercise Timer 5 795 PLC-AOUT 1 806
Group: Ethernet 797 PLC-AOUT 9 808

Subgroup: Common For All Interfaces 797 PLC-AOUT 10 808
MAC Address 797 PLC-AOUT 11 808
Subgroup: Ethernet Port Status 797 PLC-AOUT 12 809
ETH Port 1 Status 797 PLC-AOUT 13 809
Subgroup: Trusted Interface 799 PLC-AOUT 16 809
Current IP Address 799 PLC-AOUT 17 810
Current Subnet Mask 799 PLC-AOUT 18 810
Current Gateway 799 PLC-AOUT 19 810
ETH Interface Status 799 PLC-AOUT 20 810
Subgroup: Untrusted Interface 800 PLC-AOUT 21 810
Primary DNS 800 PLC-AOUT 25 811
Secondary DNS 801 PLC-AOUT 26 811
ETH Interface Status 801 PLC-AOUT 27 812
AirGate Status 802 PLC-AOUT 28 812
AirGate ID 802 PLC-AOUT 29 812
AirGate Servicing Node 803 PLC-AOUT 30 812
Last E-mail Result 804 PLC-AOUT 31 812
Subgroup: Modbus Interface 805 PLC-AOUT 32 813
Primary DNS 806 PLC-AOUT 36 813
Secondary DNS 806 PLC-AOUT 37 814

PLC-AOUT 38 814 PLC-BOUT 13 822
PLC-AOUT 58 818 PLC Resource 1 826
PLC-BOUT 1 819 PLC Resource 8 827
PLC-BOUT 10 821 Group: Remote Control 829
PLC-BOUT 11 821 RemoteControl2B 1 829
PLC-BOUT 12 821 RemoteControl2B 2 829

RemoteControl2B 3 829 Binary inputs 34 17-24 844
RemoteControl2B 4 830 Binary inputs 34 25-32 844
RemoteControl2B 5 830 DISTAIN-34 1 845
RemoteControl4B 1 831 Group: SH Modules 846
RemoteControl4B 2 831 SHBIN-1 846
RemoteControlBin 832 SHBIN-4 848
Group: DIST-IN 1-32 832 SHBIN-5 848

Binary inputs 1 1-8 832 SHBIN-6 849
Binary inputs 1 9-16 833 SHBOUT-1 849
DISTAIN-1 1 834 SHBOUT-4 851
DISTAIN-1 4 835 SHAIN-1 1 852
Binary inputs 2 1-8 836 SHAIN-1 2 852
DISTAIN-2 4 839 Group: Virtual Shared OUT 854
Group: DIST-IN 33-64 839 Binary outputs 1-8 854
Binary inputs 33 1-8 839 Binary outputs 9-16 855
Binary inputs 33 25-32 841 6 back to Controller objects
DISTAIN-33 1 841
DISTAIN-33 2 842
DISTAIN-33 3 842
DISTAIN-33 4 842
Binary inputs 34 1-8 843
Binary inputs 34 9-16 843

Group: BESS
BESS P
Value group Value Group BESS Related FW 1.3.0

Units kW
Description
Active power of the BESS.
Note: This value can be also switched into one decimal see Power Formats And Units (page 196).
6 back to List of values
BESS P L1

Units kW
Description
Active power of the L1 phase of the BESS.
BESS P L2

Units kW
Description
BESS P L3

Units kW
Description

BESS Q

Units kVAr
Description
Reactive power of the BESS.
BESS Q L1

Units kVAr
Description
Reactive power of the L1 phase of the BESS.
BESS Q L2

Units kVAr
Description
BESS Q L3

Units kVAr
Description

BESS S

Units kVA
Description
Apparent power of the BESS.
BESS S L1

Units kVA
Description
Apparent power of the L1 phase of the BESS.
BESS S L2

Units kVA
Description
BESS S L3

Units kVA
Description

BESS Power Factor

Units [-]
Description
Power factor of the BESS.
BESS Load Character

Units [-]
Description
Load character of the BESS.
L = inductive load, C = capacitive load, and R = resistive load (BESS Power Factor (page 667) = 1).
BESS Power Factor L1

Units [-]
Description
Power factor of the L1 phase of the BESS.
BESS Load Character L1

Units [-]
Description
Load character of the L1 phase of the BESS.
L = inductive load, C = capacitive load, and R = resistive load (BESS Power Factor L1 (page 667) = 1).

Units [-]
Description


Units [-]
Description

Units [-]
Description

Units [-]
Description
BESS Voltage THD L1

Units %
Description
This value represents Voltage Total Harmonic Distortion (page 18) of BESS Voltage L1-N (page
670).

BESS Voltage THD L2

Units %
Description
670).
BESS Voltage THD L3

Units %
Description
670).
BESS Current THD L1

Units %
Description
This value represents Current Total Harmonic Distortion (page 18) of BESS Current L1 (page 672).
BESS Current THD L2

Units %
Description
BESS Current THD L3

Units %
Description

BESS Frequency

Units Hz
Description
This is the value of BESS Frequency.
BESS Voltage L1-N

Units V
Description
Voltage of the L1 phase of the BESS.
BESS Voltage L2-N

Units V
Description
BESS Voltage L3-N

Units V
Description
BESS Voltage L1-L2

Units V
Description
Phase to phase voltage between the L1 and L2 phases of the BESS.

BESS Voltage L2-L3

Units V
Description
BESS Voltage L3-L1

Units V
Description
BESS Voltage

Units V
Description
Average value of all voltage phases of the BESS.
BESS V Unbalance Ph-N

Units V
Description
This value contains the maximum difference of values BESS Voltage L1-N (page 670), BESS Voltage
L2-N (page 670), BESS Voltage L3-N (page 670) at a given moment.
Note: Difference of the values and the evaluation of the protection is influenced by the setpoint
Connection type (page 371).

BESS V Unbalance Ph-Ph

Units V
Description
This value contains the maximum difference of values BESS Voltage L1-L2 (page 670), BESS Voltage
L2-L3 (page 671), BESS Voltage L3-L1 (page 671) at a given moment.
BESS Current L1

Units A
Description
Current of the L1 phase of the BESS.
BESS Current L2

Units A
Description
BESS Current L3

Units A
Description

BESS Current Unbalance

Units A
Description
This value contains the maximum difference of values BESS Current L1 (page 672), BESS Current L2
(page 672) and BESS Current L3 (page 672).
Earth Fault Current

Units A
Description
Measured fault value for evaluation of Earth Fault Current Protection (page 583).
Note: This value is filled with 0 all the time if Application Mode (page 777) = MPTM and Mains
Measurement P (page 357) = CT.
BESS Nominal Capacity

Units kWh
Description
This value shows nominal capacity of the Energy Storage.
BESS SOC

Units %
Comm
15857 Related applications MINT, MPTM
object
Description
Actual state of charge of the Energy Storage.

BESS Temperature

Units °C
Comm
object
Description
Actual BESS temperature.
Slip Frequency
Value group Mains/Bus Related FW 1.3.0

Units Hz
Description
Slip frequency during synchronization.
Slip Angle

Units °
Description
Slip angle during synchronization.
BESS P 10min Avg

Units kW
Description
This value contains 10-minutes average of BESS P (page 664).
See 10-minutes averages (page 304) for more information.
Note: This value can be also switched into one decimal see Power Formats And Units (page
196).Value is reset to 0 with opening of BCB.

BESS Q 10min Avg

Units kVAr
Description
This value contains 10-minutes average of BESS Q (page 665).
BESS S 10min Avg

Units kVA
Description
This value contains 10-minutes average of BESS S (page 666).
Group: PV
Subgroup: PV Aggregated
PV Nominal P
Value group PV Related FW 1.3.0

Units kW
Comm
object
Description
This value shows nominal power of PV inverters.

PV Actual P

Units kW
Comm
object
Description
Actual active power produced by PV inverters.
PV Actual Q

Units kVAr
Comm
object
Description
Actual reactive power produced by PV inverters.
PV Actual S

Units kVA
Comm
object
Description
Actual apparent power produced by PV inverters.
PV Actual Power Factor

Units [-]
Comm
object
Description
This value represents the actual power factor of PV inverters.

PV Actual Load Character

Units [-]
Comm
object
Description
This value represents actual load character of the PV inverters.
Curtailment Output

Units % of PV Nominal P (page 675)
Comm
object
Description
This value shows maximal percentage power which can be provided by the output of the PV inverter in
case the PV Curtailment (page 290) function is used.
Subgroup: PV Curtailment Counter
PV Max P

Units kW
Comm
object
Description
The total potential PV output across all arrays.
PV Curtailed P

Units kW
Comm
object
Description
The value of actual curtailed power.

PV Curtailed P Relative

Units kW
Comm
object
Description
This value represents the ratio of actual curtailed power (PV Curtailed P (page 677)) to the total
potential PV output (PV Max P (page 677)).
Subgroup: PV 1
PV 1 Nominal P

Units kW
Comm
object
Description
This value shows nominal power of PV inverter 1.
PV 1 Actual P

Units kW
Comm
object
Description
Actual active power produced by PV inverter 1.
PV 1 Actual Q

Units kVAr
Comm
object
Description
Actual reactive power produced by PV inverter 1.

PV 1 Actual S

Units kVA
Comm
object
Description
Actual apparent power produced by PV inverter 1.
PV 1 Actual Power Factor

Units [-]
Comm
object
Description
This value represents the actual power factor of PV inverter 1.
PV 1 Actual Load Character

Units [-]
Comm
object
Description
This value represents actual load character of the PV inverter 1.
Subgroup: PV 2
PV 2 Nominal P

Units kW
Comm
object
Description

PV 2 Actual P

Units kW
Comm
object
Description
PV 2 Actual Q

Units kVAr
Comm
object
Description
PV 2 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description


Units [-]
Comm
object
Description
Subgroup: PV 3
PV 3 Nominal P

Units kW
Comm
object
Description
PV 3 Actual P

Units kW
Comm
object
Description
PV 3 Actual Q

Units kVAr
Comm
object
Description

PV 3 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description

Units [-]
Comm
19862 Related applications (missing or bad snippet)
object
Description
Subgroup: PV 4
PV 4 Nominal P

Units kW
Comm
object
Description

PV 4 Actual P

Units kW
Comm
object
Description
PV 4 Actual Q

Units kVAr
Comm
object
Description
PV 4 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description


Units [-]
Comm
object
Description
Subgroup: PV 5
PV 5 Nominal P

Units kW
Comm
object
Description
PV 5 Actual P

Units kW
Comm
object
Description
PV 5 Actual Q

Units kVAr
Comm
object
Description

PV 5 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description

Units [-]
Comm
object
Description
Subgroup: PV 6
PV 6 Nominal P

Units kW
Comm
object
Description

PV 6 Actual P

Units kW
Comm
object
Description
PV 6 Actual Q

Units kVAr
Comm
object
Description
PV 6 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description


Units [-]
Comm
object
Description
Subgroup: PV 7
PV 7 Nominal P

Units kW
Comm
object
Description
PV 7 Actual P

Units kW
Comm
object
Description
PV 7 Actual Q

Units kVAr
Comm
object
Description

PV 7 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description

Units [-]
Comm
object
Description
Subgroup: PV 8
PV 8 Nominal P

Units kW
Comm
object
Description

PV 8 Actual P

Units kW
Comm
object
Description
PV 8 Actual Q

Units kVAr
Comm
object
Description
PV 8 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description


Units [-]
Comm
object
Description
Subgroup: PV 9
PV 9 Actual P

Units kW
Comm
object
Description
PV 9 Nominal P

Units kW
Comm
object
Description
PV 9 Actual Q

Units kVAr
Comm
object
Description

PV 9 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description

Units [-]
Comm
object
Description
Subgroup: PV 10
PV 10 Nominal P

Units kW
Comm
object
Description

PV 10 Actual P

Units kW
Comm
object
Description
PV 10 Actual Q

Units kVAr
Comm
object
Description
PV 10 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description


Units [-]
Comm
object
Description
Subgroup: PV 11
PV 11 Nominal P

Units kW
Comm
object
Description
PV 11 Actual P

Units kW
Comm
object
Description
PV 11 Actual Q

Units kVAr
Comm
object
Description

PV 11 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description

Units [-]
Comm
object
Description
Subgroup: PV 12
PV 12 Nominal P

Units kW
Comm
object
Description

PV 12 Actual P

Units kW
Comm
object
Description
PV 12 Actual Q

Units kVAr
Comm
object
Description
PV 12 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description


Units [-]
Comm
object
Description
Subgroup: PV 13
PV 13 Nominal P

Units kW
Comm
object
Description
PV 13 Actual P

Units kW
Comm
object
Description
PV 13 Actual Q

Units kVAr
Comm
object
Description

PV 13 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description

Units [-]
Comm
object
Description
Subgroup: PV 14
PV 14 Nominal P

Units kW
Comm
object
Description

PV 14 Actual P

Units kW
Comm
object
Description
PV 14 Actual Q

Units kVAr
Comm
object
Description
PV 14 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description


Units [-]
Comm
object
Description
Subgroup: PV 15
PV 15 Nominal P

Units kW
Comm
object
Description
PV 15 Actual P

Units kW
Comm
object
Description
PV 15 Actual Q

Units kVAr
Comm
object
Description

PV 15 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description

Units [-]
Comm
object
Description
Subgroup: PV 16
PV 16 Nominal P

Units kW
Comm
object
Description

PV 16 Actual P

Units kW
Comm
object
Description
PV 16 Actual Q

Units kVAr
Comm
object
Description
PV 16 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description


Units [-]
Comm
object
Description
Group: WT
Subgroup: WT Aggregated
WT Nominal P
Value group WT Related FW 1.3.0

Units kW
Comm
object
Description
This value shows nominal power of Wind Turbines.
WT Actual P

Units kW
Comm
object
Description
Actual active power produced by Wind Turbines.
WT Actual Q

Units kVAr
Comm
object
Description
Actual reactive power produced by Wind Turbines.

WT Actual S

Units [-]
Comm
object
Description
Actual apparent power produced by Wind Turbines.
WT Actual Power Factor

Units [-]
Comm
object
Description
This value represents the actual power factor of the Wind Turbines.
WT Actual Load Character

Units [-]
Comm
object
Description
This value represents actual load character of the Wind Turbines.
Curtailment Output

Units % of PV Nominal P (page 675)
Comm
object
Description
This value shows maximal percentage power which can be provided by the output of the PV inverter in
case the PV Curtailment (page 290) function is used.

Subgroup: WT 1
WT 1 Nominal P

Units kW
Comm
object
Description
This value shows nominal power of WT 1.
WT 1 Actual P

Units kW
Comm
object
Description
Actual active power produced by WT 1.
WT 1 Actual Q

Units kVAr
Comm
object
Description
Actual reactive power produced by WT 1.
WT 1 Actual S

Units kVA
Comm
object
Description
Actual apparent power produced by WT 1.

WT 1 Actual Power Factor

Units [-]
Comm
object
Description
This value represents the actual power factor of the WT 1.
WT 1 Actual Load Character

Units [-]
Comm
object
Description
This value represents actual load character of the WT 1.
Subgroup: WT 2
WT 2 Nominal P

Units kW
Comm
object
Description
WT 2 Actual P

Units kW
Comm
object
Description

WT 2 Actual Q

Units kVAr
Comm
object
Description
WT 2 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description

Units [-]
Comm
object
Description

Subgroup: WT 3
WT 3 Nominal P

Units kW
Comm
object
Description
WT 3 Actual P

Units kW
Comm
object
Description
WT 3 Actual Q

Units kVAr
Comm
object
Description
WT 3 Actual S

Units kVA
Comm
object
Description


Units [-]
Comm
object
Description

Units [-]
Comm
object
Description
Subgroup: WT 4
WT 4 Nominal P

Units kW
Comm
object
Description
WT 4 Actual P

Units kW
Comm
object
Description

WT 4 Actual Q

Units kVAr
Comm
object
Description
WT 4 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description

Units [-]
Comm
object
Description

Subgroup: WT 5
WT 5 Nominal P

Units kW
Comm
object
Description
WT 5 Actual P

Units kW
Comm
object
Description
WT 5 Actual Q

Units kVAr
Comm
object
Description
WT 5 Actual S

Units kVA
Comm
object
Description


Units [-]
Comm
object
Description

Units [-]
Comm
object
Description
Subgroup: WT 6
WT 6 Nominal P

Units kW
Comm
object
Description
WT 6 Actual P

Units kW
Comm
object
Description

WT 6 Actual Q

Units kVAr
Comm
object
Description
WT 6 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description

Units [-]
Comm
object
Description

Subgroup: WT 7
WT 7 Nominal P

Units kW
Comm
object
Description
WT 7 Actual P

Units kW
Comm
object
Description
WT 7 Actual Q

Units kVAr
Comm
object
Description
WT 7 Actual S

Units kVA
Comm
object
Description


Units [-]
Comm
object
Description

Units [-]
Comm
object
Description
Subgroup: WT 8
WT 8 Nominal P

Units kW
Comm
object
Description
WT 8 Actual P

Units kW
Comm
object
Description

WT 8 Actual Q

Units kVAr
Comm
object
Description
WT 8 Actual S

Units kVA
Comm
object
Description

Units [-]
Comm
object
Description

Units [-]
Comm
object
Description

Group: Renewables
REN Nominal P
Value group Renewables Related FW 1.3.0

Units kW
Comm
object
Description
This value shows nominal power of all renewables in the system.
REN Actual P

Units kW
Comm
object
Description
Actual active power produced by all renewables in the system.
REN Actual Q

Units kVAr
Comm
object
Description
Actual reactive power produced by all renewables in the system.
REN Actual S

Units kVA
Comm
object
Description
Actual apparent power produced by all renewables in the system.

REN Actual Power Factor

Units [-]
Comm
object
Description
This value represents the actual power factor of all renewables in the system.
REN Actual Load Character

Units [-]
Comm
object
Description
This value represents actual load character of all renewables in the system.
Group: Hybrid System
Total P

Units kW
Comm
object
Description
Total power produced by the Microgrid System.
Total Q

Units kVAr
Comm
object
Description
Total reactive power produced by the Microgrid System.

Total S

Units kVA
Comm
object
Description
Total apparent power produced by the Microgrid System.
Total PF

Units
Comm
object
Description
This value represents the total power factor of the Microgrid System.
Total Load Character

Units
Comm
object
Description
This value represents the total load character of the Microgrid System.
Group: Gensets
Gensets P
Value group Gensets Related FW 1.3.0

Units [-]
Description
This value represents the total power of all running Gen-sets.

Gensets Q

Units [-]
Description
This value represents the reactive power of all running Gen-sets.
Gensets Power Factor

Units [-]
Description
This value represents the total power factor of all running Gen-sets.
Gensets Load Character

Units [-]
Description
This value represents the total character of all running Gen-sets.
Group: Mains
Mains Import P Monitoring
Value group Mains Related FW 1.3.0

Units kW
Description
Imported apparent power [kW] from Mains.
Mains Import Q Monitoring
Value group Mains Related FW 1.3.0

Units kVAr
Description
Imported reactive power [kVAr] from Mains.

Group: Load
Load P
Value group Load Related FW 1.3.0

Units kW
Description
Load's active power.
Load Q

Units kVAr
Description
Load's reactive power.
Load Power Factor
Load Load Related FW 1.3.0

Units [-]
Description
Load's power factor.
Load Character

Units [-]
Related
applications
Description
Load's character. "L" means inductive load, "C" is capacitive and "R" is resistive load (Load Power
Factor (page 720) = 1).

Group: Grid Codes
Grid Codes Version
Value group Grid Codes Related FW 1.3.0

Units [-]
Description
This value shows the Grid Codes module version.
Pmom

Units kW
Description
This value contains BESS P (page 664) at the moment of start of either Power Regulation Based On
Over/Under Frequency (page 294) or Power Regulation Based On Actual Mains Voltage (page
297). This value is used for calculations.
Test Frequency

Units Hz
Description
This value contains frequency for testing of Grid Codes (page 294). Grid Codes Test (page 527) has
to be Enabled and alarm Wrn Test UPQF (page 1103) active. The value is filled as Nominal
Frequency (page 377) + value from LAI TESTF (PAGE 1008).
P Over Frequency Curve

Units %
Description
This value contains actual y-axe value of POWER OVER FREQUENCY (PAGE 866) curve while LBO P OVER
FREQUENCY ACTIVE (PAGE 965) is closed, otherwise it has Invalid flag (page 652).

P Under Frequency Curve

Units %
Description
This value contains actual y-axe value of POWER UNDER FREQUENCY (PAGE 867) curve while LBO P
UNDER FREQUENCY ACTIVE (PAGE 965) is closed, otherwise it has Invalid flag (page 652).
Q(Um) Curve

Units kVAr
Description
This value contains target of required reactive power based on Q(UM) (PAGE 858) curve while PF/Q
Control PTM Mode (page 349) = Q(Um) and Breaker state (page 778) = ParalOper, otherwise it has
Invalid flag (page 652).
Qref/Ulim Curve

Units kVAr
Description
This value contains target of required reactive power based on Qref/Ulim (page 859) curve while PF/Q
Control PTM Mode (page 349) = Qref/Ulim and Breaker state (page 778) = ParalOper, otherwise it
has Invalid flag (page 652).
See Qref/Ulim (page 265)PF/Q control (page 257)for more information.

Q(P) Curve

Units kVAr
Description
This value contains target of required reactive power based on Q(P) (PAGE 860) curve while PF/Q
Control PTM Mode (page 349) = Q(P) and Breaker state (page 778) = ParalOper, otherwise it has
Invalid flag (page 652).
See Q(P) (page 264)PF/Q control (page 257) for more information.
PF(P) Curve

Units kVAr
Description
This value contains target of required power factor based on PF(P) (PAGE 861) curve while PF/Q
Control PTM Mode (page 349) = PF(P) and Breaker state (page 778) = ParalOper, otherwise it
has Invalid flag (page 652).
See PF(Pm) (page 262)PF/Q control (page 257) for more information.
P(Um) Curve

Units kW
Description
This value contains actual value of P(Um) (page 862) curve while Power Regulation Based On Actual
Mains Voltage (page 297) is active.
The value is either related to value Pmom (page 721) or Installed Power (page 368) based on selected
mode of P(Um) (page 544).

Pmom/Pave

Units kW
Description
This value contais actual ratio of LAI PMOM (PAGE 993) to Pave (page 560) and is used by application
curve P Mom/Pave Max (page 863).
Load Reduction 1 Occurrence

Units [-]
Description
This value contains cumulative amount of occurrence of closed LBI LOAD REDUCTION 1 (PAGE 896).
See Load Reduction (page 298) for more information.
Note: This value is never reset, you can change its value via "Set Statistics" in InteliConfig.

Units [-]
Description

Units [-]
Description


Units [-]
Description
Load Reduction 1 hrs Actual Month

Units h
Description
This value contains total hours of active LBI LOAD REDUCTION 1 (PAGE 896) in actual month.
st
Note: Data are moved to Last Month every 1 day of month at 0:00.
Load Reduction 1min Actual Month

Units min
Description
This value contains minutes (up to 59) of active LBI LOAD REDUCTION 1 (PAGE 896) in actual month.
Note: Data are moved to Last Month every 1st day of month at 0:00.
Load Reduction 1 hrs Last Month

Units h
Description
This value contains total hours of active LBI LOAD REDUCTION 1 (PAGE 896) in last month.
st
Note: Data are replaced with the value Load Reduction 1 hrs Actual Month (page 725) every 1
day of month at 0:00.

Load Reduction 1 min Last Month

Units min
Description
This value contains minutes (up to 59) of active LBI LOAD REDUCTION 1 (PAGE 896) in last month.
st
Note: Data are replaced with the value Load Reduction 1min Actual Month (page 725) every 1
Load Reduction 1 hrs Accumulated

Units h
Description
This value contains accumulated hours of active LBI LOAD REDUCTION 1 (PAGE 896) from last reset of
this value.
Note: You can reset this value via "Set Statistics" in InteliConfig.
Load Reduction 1 min Accumulated

Units min
Description
This value contains minutes (up to 59) of active LBI LOAD REDUCTION 1 (PAGE 896) from last reset of this
value.

Units h
Description
st

Load Reduction 2 min Actual Month

Units min
Description
st

Units h
Description
st

Units min
Description
st
Note: Data are replaced with the value Load Reduction 2 min Actual Month (page 727) every 1

Units h
Description
this value.


Units min
Description
value.

Units h
Description
st

Units min
Description
st

Units h
Description
st


Units min
Description
st

Units h
Description
this value.

Units min
Description
value.

Units h
Description
st


Units min
Description
st

Units h
Description
st

Units min
Description
st

Units h
Description
this value.

Grid
Value group Related FW 1.3.0
Codes
Units min
Description
value.
Group: Mains/Bus
Mains/Bus Frequency

Units Hz
Description
Frequency of Mains/Bus.
Mains/Bus Voltage L1-N
Value Group
Mains/Bus
Units V
Description
Value of Mains/Bus voltage on phase 1.
Value Group
Mains/Bus
Units V
Description

Value Group
Mains/Bus
Units V
Description
Mains/Bus Voltage L1-L2

Units V
Description
Value of Mains/Bus phase to phase voltage between L1 and L2 phases.

Units V
Description

Units V
Description
Mains/Bus Voltage

Units V
Description
Average value of all Mains/BusVoltage phases.

Mains/Bus V Unabalance Ph-N
Value Group
Mains/Bus
Units V
Description
This value contains the maximum difference of values Mains/Bus Voltage L1-N (page 731),
Mains/Bus Voltage L2-N (page 731), Mains/Bus Voltage L3-N (page 732) at a given moment.
Mains/Bus V Unbalance Ph-Ph

Units V
Description
This value contains the maximum difference of values Mains/Bus Voltage L1-L2 (page 732),
Mains/Bus Voltage L2-L3 (page 732), Mains/Bus Voltage L3-L1 (page 732) at a given moment.
+Mains/Bus Voltage

Units V
Description
Value of +Mains/Bus voltage measured by Symmetrical components (page 16)
+Mains/Bus Voltage Relative

Units V
Description
Value of +Mains/Bus voltage measured by Symmetrical components (page 16) which is related to
Mains/Bus Nominal Voltage Ph-N (page 373) or Mains/Bus Nominal Voltage Ph-Ph (page 374).

Mains L1 Current

Units A
Description
Mains' current.
Note: This value is filled with 0 all the time if Mains Measurement P (page 357) != CT.
Mains L1 Current

Units A
Description
Current of the L1 phase of the Mains/Bus.
Mains L2 Current

Units A
Description
Mains L2 Current

Units A
Description
Mains Import P

Units kW
Description
Imported active power [kW] from Mains.

Mains P L1

Units kW
Description
Imported active power [kW] from L1 phase of the Mains.
Mains P L2

Units kW
Description
Mains P L3

Units kW
Description
Mains Import Q

Units kVAr
Description
Imported reactive power [kVAr] from Mains.
Mains Import Q L1

Units kW
Description
Imported reactive power [kVAr] from L1 phase of the Mains.

Mains Import Q L2

Units kW
Description
Mains Import Q L3

Units kW
Description
Mains/BusMainsBus Left Import S

Units kVA
Description
Imported apparent power [kVA] from Mains.
Mains S L1

Units kVA
Description
Imported apparent power [kVA] from L1 phase of the Mains.
Mains S L2

Units kVA
Description

Mains S L3

Units kVA
Description
Mains PF

Units [-]
Description
Power factor of the Mains.
Mains Load Character

Units [-]
Description
Character of Mains load. "L" means inductive load, "C" is capacitive and "R" is resistive load (Mains PF
(page 737) = 1).
Load character of the Mains.
L = inductive load, C = capacitive load, and R = resistive load (Mains PF (page 737) = 1).
Mains Power Factor L1
Value
Mains/Bus Related FW 1.3.0
group
Units [-]
Comm
object
Description
Power factor of the L1 phase of the Mains/Bus.

Mains Load Character L1

Units [-]
Description
Load character of the L1 phase of the Mains.
L = inductive load, C = capacitive load, and R = resistive load (Mains Power Factor L1 (page 737) = 1).

Units [-]
Description

Units [-]
Description

Units [-]
Description


Units [-]
Description
Mains Voltage THD L1

Units %
Description
This value represents Voltage Total Harmonic Distortion (page 18) Mains/Bus Voltage L1-N (page
731).

Units %
Description
This value represents Voltage Total Harmonic Distortion (page 18) of Mains/Bus Voltage L2-N
(page 731).

Units %
Description
This value represents Voltage Total Harmonic Distortion (page 18) of Mains/Bus Voltage L3-N
(page 732).

Mains Current THD L1

Units %
Description
This value represents Current Total Harmonic Distortion (page 18) of Mains L1 Current (page 734).

Units %
Description
This value represents Current Total Harmonic Distortion (page 18) of .

Units %
Description
This value represents Current Total Harmonic Distortion (page 18) of .
Max Vector Shift

Units °
Description
Maximal measured value of Vector shift (page 173) of the Mains. It is reset to zero always when:
Vector Shift Protection (page 584) = Parallel Only - controller goes to parallel to mains
operation
Vector Shift Protection (page 584) = Enabled - MCB gets closed

Mains Voltage 10min Avg L1-N
Value Group
Mains/Bus
Units V
Description
This value contains 10-minutes average of Mains/Bus Voltage L1-N (page 731).
Note: Value is reset when controller is switched off.
Value Group
Mains/Bus
Units V
Description
Value Group
Mains/Bus
Units V
Description

Value Group
Mains/Bus
Units V
Description
This value contains 1-minute average of Mains/Bus Voltage L1-N (page 731).
See 1-minute averages (page 305) for more information.
Value Group
Mains/Bus
Units V
Description
Value Group
Mains/Bus
Units V
Description

Mains Voltage 10min Avg L1-L2

Units V
Description
This value contains 10-minutes average of Mains/Bus Voltage L1-L2 (page 732).

Units V
Description

Units V
Description

Units V
Description
This value contains 1-minute average of Mains/Bus Voltage L1-L2 (page 732).


Units V
Description

Units V
Description
ROCOF1

Units Hz/s
Description
This value contains actual rate of change of frequency measured by ROCOF1 Protection (page 585).
See ROCOF (page 173) for more information.

Max ROCOF1

Units Hz/s
Description
This value contains maximal rate of change of frequency measured by ROCOF1 Protection (page 585)
since the protection got active.
Setting Reset of value

When MCB closes.
ROCOF1 Protection Selector (page 513) = MCB
(page 585) = Enabled Vector Shift/ROCOF CB
When BCB closes.
Selector (page 513) = BCB
ROCOF1 Protection After entering parallel operation
(page 585) = Parallel (Breaker state (page 778) =
Only ParalOper)
ROCOF2

Units Hz/s
Description

Max ROCOF2

Units Hz/s
Description

When MCB closes.
When BCB closes.
Only ParalOper)
ROCOF3

Units Hz/s
Description

Max ROCOF3

Units Hz/s
Description

When MCB closes.
When BCB closes.
Only ParalOper)
ROCOF4

Units Hz/s
Description

Max ROCOF4

Units Hz/s
Description

When MCB closes.
When BCB closes.
Only ParalOper)
Group: Power Management
BESS Priority
Value group Power Management Related FW 1.3.0

Units -
Description
This value shows current priority number of the unit. It corresponds to the setpoint Priority (page 483)
except following situations:
If at least one of binary inputs TOP PRIORITY (PAGE 918) is configured on some source and is
active
#Priority Auto Swap (page 484) is active
Actual Reserve

Units kW
Description
Actual absolute reserve in Power Management (page 269).

Start Reserve

Units kW
Description
Required minimal Actual Reserve (page 748) for starting of next unit in the Power Management (page
269).
Stop Reserve

Units kW
Description
Required maximal Actual Reserve (page 748) for stopping of next unit in the Power Management
(page 269).

Units kW
Description
The value Dynamic Spinning Reserve is added to required load reserve given by setpoints #Starting
Load Reserve 1 (page 488) and #Stopping Load Reserve 1 (page 489) (according to actual load
reserve set 1, 2, 3 or 4) to shift the actual load reserve settings in dynamic way.
Dynamic Spinning Reserve Offset

Units kW
Description
The value Dynamic Spinning Reserve Offset is added only to required stopping load reserve given by
setpoints #Stopping Load Reserve 1 (page 489) (according to actual load reserve set 1, 2, 3 or 4) to
create some dynamic offset between starting and stopping load reserve.

Actual Relative Reserve

Units %
Description
Actual relative reserve in Power Management (page 269).
Start Relative Reserve

Units %
Description
Required minimal Actual Relative Reserve (page 750) for starting of next unit in the Power
Management (page 269).
Stop Relative Reserve

Units %
Description
Required maximal Actual Relative Reserve (page 750) for stopping of next unit in the Power
Actual Active Power In PM

Units kW
Description
Actual value of active power from all controllers running in Power Management (page 269).
Actual Reactive Power In PM

Units kVAr
Description
Actual value of reactive power from all controllers running in Power Management (page 269).

Running Nominal Power In PM

Units kW
Description
Actual nominal power of all running controllers on inter-controller CAN in Power Management (page
269).
Running Nominal Power Of All

Units kW
Description
Actual nominal power of all running controllers on inter-controller CAN.
Available Nominal Power

Units kW
Description
Available nominal power of all controllers on inter-controller CAN in Power Management (page 269).
Minimal Running Nominal Power

Units kW
Description
Actual minimal nominal power of all Controllers, which are running.

Actual Power Band 32

Units [-]
Description
Required state of the Controllers with CAN address between 1 .. 32 in the actual power band of Power
Log 0: Controller should be stopped
Log 1: Controller should be running
Note: Actual power band = group of Controllers which should be running with actual load.
Note: Value is taken into account only if #Priority Auto Swap (page 484) = Efficient.
Actual Power Band 64

Units [-]
Description
Required state of the Gen-sets with CAN address between 33 .. 64 in the actual power band of Power
Log 0: Gen-set should be stopped
Log 1: Gen-set should be running
Note: Actual power band = group of Gen-sets which should be running with actual load.
Next Power Band 32

Units -
Description
Required state of the Gen-sets with CAN address between 1 .. 32 in the next power band of Power
Log 0: Gen-set should be stopped if load is decreased
Log 1: Gen-set should be started if load is increased
Note: Next power band = group of Gen-sets which should be running after load change.

Next Power Band 64

Units -
Description
Required state of the Gen-sets with CAN address between 33 .. 64 in the next power band of Power
Log 0: Gen-set should be stopped if load is decreased
Log 1: Gen-set should be started if load is increased
Note: Next power band = group of Gen-sets which should be running after load change.
Group: Frequency/Load Control
BESS Required P Target
Frequency/Load
Control
Units kW
Description
This value shows required active power at the end of ramping.
BESS Required P
Frequency/Load
Control
Units kW
Description
This value shows required active power relative to the ramping procedure i.e. required active power right
now.

BESS Required Relative P
Frequency/Load
Control
Units % of Nominal power (page 368)
Description
Relative value of required power of the BESS.
Frequency Regulator Output
Frequency/Load
Control
Units V
Description
This is the actual voltage on the frequency regulator output of the controller.
In case the Analog Output (page 252) is switched to PWM mode, the relation is:
10 V = ~100 % PWM.
-10 V = 0 % PWM
BESS Frequency Required
Frequency/Load
Control
Units Hz
Description
Requested BESS frequency in Hz.
BESS Frequency Offset
Frequency/Load
Control
Units Hz
Description
Relative value of requested power of the BESS.

BESS P Required
Frequency/Load
Control
Units %
Description
Relative request for BESS kW/Hz output in %.
System Load Control
Frequency/Load
Control
Units [-]
Description
This value contains the actual LoadControl mode that the BESS is currently using. This value may differ
from setpoint Load Control PTM Mode (page 345) which contains requested Load Control mode.
List of possible states:
None The system is not operating.

Island The system operates in the Island mode.
The system operates in Baseload mode which is adjusted by the setpoint
BESS Charge Power (page 427)/BESS Discharge Power (page 428)
Baseload
while LBI BATT CHARGE ENABLE (PAGE 879)/BATT DISCHARGE ENABLE
(PAGE 879) is active.
The system operates in Baseload mode with import/export limitation.
Requested load is adjusted by the setpoint BESS Charge Power (page
Baseload with I/E
427)/BESS Discharge Power (page 428) while LBI BATT CHARGE
Limit
ENABLE (PAGE 879)/BATT DISCHARGE ENABLE (PAGE 879) is active but it
is limitated by the setpoint Import Load (page 348).
The system operates in Import/Export mode which is adjusted by the
Import/Export
setpoint Import Load (page 348).

Group: Voltage/PF Control
System PF/Q Control
Value group Voltage/PF Control Related FW 1.3.0

Units [-]
Description
This value contains the actual PF/Q Control mode that the BESS is currently using. This value may differ
from setpoint PF/Q Control PTM Mode (page 349) which contains requested PF/Q Control mode.
List of possible states:
None The system is not operating.

Island The system operates in the Island mode.
The system operates in PF Control mode which is adjusted by the setpoint #System Power Factor
PF Control BASE
(page 353).
The system operates in PF(Pm) mode which is adjusted by the application curve PF(P) (PAGE 861) in
PF(Pm) BASE
x-axe range 0 to 100%.
The system operates in Q Control mode which is adjusted by the setpoint #SYSTEM BASE Q (PAGE
Q Control BASE
354).
The system operates in Q(Um) mode which is adjusted by the application curve Q(UM) (PAGE 858)
Q(Um) BASE
with possible offset by the setpoint Q(UM) 0 REFERENCE (PAGE 556).
The system operates in Q(P) mode which is adjusted by the application curve Q(P) (PAGE 860) in x-
Q(P) BASE
axe range 0 to 100%.
The system operates in Qref/Ulim mode which is adjusted by the application curve QREF/ULIM (PAGE
Qref/Ulim BASE
859) with possible offset by the setpoint QREF/PNOM SHIFT (PAGE 557).
The system operates in PF Control mode which is adjusted by the setpoint IMPORT POWER FACTOR
PF Control IMP/EXP
(PAGE 352).
The system operates in PF(Pm) mode which is adjusted by the application curve PF(P) (PAGE 861) in
PF(Pm) IMP/EXP
x-axe range -100 to 100%.
Q Control IMP/EXP The system operates in Q Control mode which is adjusted by the setpoint IMPORT Q (PAGE 354).
Q(Um) IMP/EXP
with possible offset by the setpoint Q(UM) 0 REFERENCE (PAGE 556).
The system operates in Q(P) mode which is adjusted by the application curve Q(P) (PAGE 860) in x-
Q(P) IMP/EXP
axe range -100 to 100%.
Qref/Ulim IMP/EXP
859) with possible offset by the setpoint QREF/PNOM SHIFT (PAGE 557).
The system operates in PF Control mode which is adjusted by the LAI PF CONTROL: ANEXT BASE PF
PF Control ANEXT BASE
(PAGE 992).
The system operates in Q Control mode which is adjusted by the LAI Q CONTROL: ANEXT BASE Q
Q Control ANEXT BASE
(PAGE 1004).
Q(Um) ANEXT BASE
with possible offset by the LAI Q(UM): 0 REF ANEXT BASE Q (PAGE 1005).
Qref/Ulim ANEXT BASE
859) with possible offset by the LAI QREF/ULIM: ANEXT QREF/PNOM B Q (PAGE 1007).
The system operates in PF Control mode which is adjusted by the LAI PF CONTROL: ANEXT IMP/EXP
PF Control ANEXT IMP/EXP
PF (PAGE 993).
The system operates in Q Control mode which is adjusted by the LAI Q(UM): 0 REF ANEXT IMP/EXP Q
Q Control ANEXT IMP/EXP
(PAGE 1006).
Q(Um) ANEXT IMP/EXP
with possible offset by the LAI Q(UM): 0 REF ANEXT BASE Q (PAGE 1005).
Qref/Ulim ANEXT IMP/EXP
859) with possible offset by the LAI QREF/ULIM: ANEXT QREF/PNOM I/E Q (PAGE 1008).

BESS Required Q

Units kVAr
Description
Required reactive power.
BESS Required Qrel Lim

Units %
Description
Required relative reactive power.
BESS Required Relative Q

Units %
Description
Relative value of required reactive power of the BESS.
BESS Required PF

Units [-]
Description
Required Power Factor.
BESS Required PF Character

Units [-]
Description
Required Power Factor Character.

Voltage Regulator Output

Units V
Description
This is the actual voltage on the voltage governor output of the controller.
In case the Analog Output (page 252) is switched to PWM mode, the relation is:
10 V = ~100 % PWM.
-10 V = 0 % PWM
Voltage Request

Units %
Description
This value contains the voltage control signal expressed in % for internal Voltage Request of internal
Voltage Regulator.
BESS Voltage Required

Units V
Description
Requested BESS output Voltage in V.
BESS Voltage Offset

Units %
Description
Requested offset from the BESS nominal output Voltage in V (positive or negative).

BESS Q Required %

Units %
Description
Relative value of requested reactive power of the BESS.
Group: Controller I/O
Battery Voltage
Value group Controller I/O Related FW 1.3.0

Units V
Description
Controller's supply voltage.
CU-AIN-01

Units Configurable
Description
This is the value of the analog input 1 of the controller.
Note: Name of this value is changed according to the controller configuration.
CU-AIN-02

Units Configurable
Description

CU-AIN-03

Units Configurable
Description
CU-AIN-04

Units Configurable
Description
Binary Inputs

Units [-]
Description
States of the binary inputs of the controller.
01. CU-BIN-01
02. CU-BIN-02
03. CU-BIN-03
04. CU-BIN-04
05. CU-BIN-05
06. CU-BIN-06
07. CU-BIN-07
08. CU-BIN-08
09. CU-BIN-09
10. CU-BIN-10
11. CU-BIN-11
12. CU-BIN-12
Note: Names are changed based on names of representative binary inputs. See Default
configuration (page 118) to see default binary inputs names.

E-STOP

Units [-]
Description
Value of ㉓ E-STOP (page 48) .
Log .1 - E-STOP has voltage - alarm E-STOP (page 1114) is inactive
Log. 0 - E-STOP has no voltage - alarm E-STOP (page 1114) is active
Binary Outputs

Units [-]
Description
State of the binary outputs of the controller.
01. CU-BOUT-01
02. CU-BOUT-02
03. CU-BOUT-03
04. CU-BOUT-04
05. CU-BOUT-05
06. CU-BOUT-06
07. CU-BOUT-07
08. CU-BOUT-08
09. CU-BOUT-09
10. CU-BOUT-10
11. CU-BOUT-11
12. CU-BOUT-12
Note: Names are changed based on names of representative binary outputs. See Default
configuration (page 118) to see default binary outputs names.

Group: Statistics
PV kWh
Value group Statistics Related FW 1.3.0

Units kWh
Description
This statistical value is showing the total kWh produced by the PV (renewables). The value is obtained by
counting the active power (PV Actual P (page 676)) of the PV.
PV Annual kWh

Units kWh
Description
This statistical value is showing the total kWh produced by the PV (renewables) per year. The value is
obtained by counting the active power (PV Actual P (page 676)) of the PV.
PV Monthly kWh

Units kWh
Description
This statistical value is showing the total kWh produced by the PV (renewables) per month. The value is
PV Weekly kWh

Units kWh
Description
This statistical value is showing the total kWh produced by the PV (renewables) per week. The value is

PV Daily kWh

Units kWh
Description
This statistical value is showing the total kWh produced by the PV (renewables) per day. The value is
PV Total Curtailed kWh

Units kWh
Description
The total energy lost due to curtailment across all PV arrays.
PV Curtailed Annual kWh

Units kWh
Description
The energy lost due to curtailment over the course of a year.
PV Curtailed Monthly kWh

Units kWh
Description
Monthly energy losses due to curtailment.
PV Curtailed Weekly kWh

Units kWh
Description
Weekly energy losses due to curtailment.

PV Curtailed Daily kWh

Units kWh
Description
Daily energy losses due to curtailment.
WT kWh

Units kWh
Description
This statistical value is showing the total kWh produced by the WT. The value is obtained by counting the
active power (WT Actual P (page 702)) of the WT.
WT Annual kWh

Units kWh
Description
This statistical value is showing the total kWh produced by the WT per year. The value is obtained by
counting the active power (WT Actual P (page 702)) of the WT.
WT Monthly kWh

Units kWh
Description
This statistical value is showing the total kWh produced by the WT per month. The value is obtained by

WT Weekly kWh

Units kWh
Description
This statistical value is showing the total kWh produced by the WT per week. The value is obtained by
WT Daily kWh

Units kWh
Description
This statistical value is showing the total kWh produced by the WT per day. The value is obtained by
Batt. Charging Cycles

Units [-]
Description
This statistical value shows the charging cycles of the BESS. It is incremented together with LAI BATTERY
CHARGING CYCLES (PAGE 983) which is the input for this value.
Note: Usually one charging cycle is defined as complete discharge of fully charged battery or a
series of partial drains equal to the battery’s capacity.
Batt. Discharge kWh

Units kWh
Description
This statistical value is showing the total kWh provided by the BESS to the system. The value is obtained
by counting the positive active power (BESS P (page 664)) of the BESS.

Batt. Discharge Annual kWh

Units kWh
Description
This statistical value is showing the total kWh provided by the BESS to the system per year. The value is
obtained by counting the positive active power (BESS P (page 664)) of the BESS.
Batt. Discahrge Month kWh

Units kWh
Description
This statistical value is showing the total kWh provided by the BESS to the system per month. The value
is obtained by counting the positive active power (BESS P (page 664)) of the BESS.
Batt. Discharge Week kWh

Units kWh
Description
This statistical value is showing the total kWh provided by the BESS to the system per week. The value is
Batt. Discharge Daily kWh

Units kWh
Description
This statistical value is showing the total kWh provided by the BESS to the system per day. The value is

Batt. Charge kWh

Units kWh
Description
This statistical value is showing the total kWh consumed by the BESS from the system. The value is
obtained by counting the negative active power (BESS P (page 664)) of the BESS.
Batt. Charge Annual kWh

Units kWh
Description
This statistical value is showing the total kWh consumed by the BESS from the system per year. The
value is obtained by counting the negative active power (BESS P (page 664)) of the BESS.
Batt. Charge Month kWh

Units kWh
Description
This statistical value is showing the total kWh consumed by the BESS from the system per month. The
Batt. Charge Week kWh

Units kWh
Description
This statistical value is showing the total kWh consumed by the BESS from the system per week. The

Batt. Charge Daily kWh

Units kWh
Description
This statistical value is showing the total kWh consumed by the BESS from the system per day. The
Hours Of Silent

Units h
Description
This statistical value is showing diesel-off operation compared to total hours in hours.
Carbon Offset Equivalent

Units t
Description
This statistical value is showing saved CO2 produced by diesel/gas genset per generated kWh by
alternative source of energy in tons.
Gen kWh

Units kWh
Description
This statistical value is showing the total sum of energy in kWh.
Gen Annual kWh

Units kWh
Description
This statistical value is showing the sum of energy in kWh per year.

Gen Daily kWh

Units kWh
Description
This statistical value is showing the sum of energy in kWh per day.
Gen Monthly kWh

Units kWh
Description
This statistical value is showing the sum of energy in kWh per month.
Gen Weekly kWh

Units kWh
Description
This statistical value is showing the sum of energy in kWh per week.
Fuel Used

Units l
Description
This statistical value is showing the total fuel consumption from all gensets in litres.
Fuel Annual

Units l
Description
This statistical value is showing the fuel consumption from all gensets in litres per year.

Fuel Monthly

Units l
Description
This statistical value is showing the fuel consumption from all gensets in litres per month.
Fuel Weekly

Units l
Description
This statistical value is showing the fuel consumption from all gensets in litres per week.
Fuel Daily

Units l
Description
This statistical value is showing the fuel consumption from all gensets in litres per day.
PCC kWh

Units kWh
Description
This statistical value is showing the total kWh produced by the BESS. The value is obtained by counting
the active power (BESS P (page 664)) of the BESS.
PCC kVArh

Units kVArh
Description
This statistical value is showing the total kVArh produced by the BESS. The value is obtained by counting
the reactive power (BESS Q (page 665)) of the BESS.

PCC kVAh

Units kVAh
Description
This statistical value is showing the total kVAh produced by the BESS. The value is obtained by counting
the apparent power (BESS S (page 666)) of the BESS.
Mains kWh

Units kVAh
Description
Counter of Mains Import P (page 734), when the value is negative
Mains kVArh

Units kVArh
Description
Counter of Mains Import Q (page 735), when the value is negative
Running Hours

Units hours
Description
BESS operation hours counter. The BESS hours are incremented in the controller while the BESS is
running. Source of running hours is adjusted via setpoint Run Hours Source (page 380).

Conditioned Running Hours 1

Units hours
Description
This value contains counted hours while corresponding LBI is active.
Conditioned Running Hours 2

Units hours
Description
This value contains counted hours while corresponding LBI is active.
Num Starts

Units [-]
Description
BESS start commands counter. The counter is increased only by 1 even if the particular start command
will take more than one attempt.

Units hours
Description
Countdown running hours until next maintenance. Initial value can be set in Maintenance Timer 1
RunHours (page 640).


Units hours
Description
Countdown days until next maintenance. Initial value can be set in Maintenance Timer 1 Interval (page
641).

Units hours
Description

Units hours
Description
642).

Units hours
Description


Units hours
Description
644).

Units hours
Description

Units hours
Description
645).
Num E-Stops

Units [-]
Description
This value counts amount of BESS shutdowns which are triggered by E-STOP (page 1114) or
Emergency Stop (page 1114).
Note: Value is incremented only if BESS was running during alarm activation.

Shutdowns

Units [-]
Description
This counter counts occurrences of a Shutdown (page 1114) alarm which actually shutdowns the
BESS. If 2 shutdown alarms are received at the same time, this value is increased only by 1.
Note: This value does not count occurrences of E-STOP (page 1114) and Emergency Stop (page
1114). These are counted separately in Num E-Stops (page 774).
Fast Pulse Counter 1

Units [-]
Description
This is the Statistic value of the Fast Pulse Counter 1 which is physically configured to binary input 9.
Change the conversion rate via setpoint Conversion Coeff. Fast Pulse 1 (page 383).
See the chapter Pulse Counters (page 211) for more information.
Note: The Value can be set via InteliConfig in the interface "Set Statistics".
Fast Pulse Counter 2

Units [-]
Description
This is the Statistic value of the Fast Pulse Counter 2 which is physically configured to binary input 10.
Change the conversion rate via setpoint Conversion Coeff. Fast Pulse 2 (page 383).

Pulse Counter 1

Units [-]
Description
This is the Statistic value of the Pulse Counter 1 which is connected with LBI PULSE COUNTER 1 (PAGE
908). Change the conversion rate via setpoint Conversion Coefficient Pulse 1 (page 384).
Pulse Counter 2

Units [-]
Description
This is the Statistic value of Pulse the Counter 2 which is connected with LBI PULSE COUNTER 2 (PAGE
908). Change the conversion rate via setpoint Conversion Coefficient Pulse 2 (page 384).

Group: Info
Application Mode
Value group Info Related FW 1.3.0

Units [-]
Description
This value reflects which application is used for the controller at the moment.
The application is selected based on setpoint Default Application Select (page 344), LBI APPLICATION
MINT (PAGE 879) and APPLICATION MPTM (PAGE 879)
LBI APPLICATION LBI APPLICATION LBI APPLICATION

Application Mode
MINT (PAGE 879) MPTM (PAGE 879) SPI (PAGE 1)
Based on Default
0 0 0 Application Select (page
344)
0 1 0 MPTM
1 0 0 MINT
1 1 0 MPTM
IMPORTANT: Application Mode can be changed only if Controller Mode (page 777) = OFF.
Controller Mode

Units [-]
Description
Controller mode.
Load Shedding Status

Units [-]
Description
This value contains actual active highest stage of Load shedding stages (page 170). Value has range
from 0 to 8 , where 0 means no load shedding stage is active.

BESS state

Units [-]
Description
This value contains actualBESS state message.
Breaker state

Units [-]
Description
This value contains actual breaker state message.
Timer Text

Units [-]
Description
This value contains actual timer text message.
Connection Type

Units [-]
Description
This value contains name of currently selected connection type, which is adjusted via Connection type
(page 371).
Timer Value

Units [MM:SS]
Description
This value contains time of active timer which is counted down, name of the timer is in value Timer Text
(page 778).

ID String

Units [-]
Description
Name of controller which is used in InteliConfig in command bar.
FW Version

Units [-]
Description
Major and minor firmware version number.
Application

Units [-]
Description
The value contains actual application in controller.
FW Branch

Units [-]
Description
The value contains actual branch of firmware in controller.

CAN Intercontroller Comm Mode

Units [-]
Description
This value contains actual mode of CAN Intercontroller Communication (page 132).
Note: In case that there is a mismatch between this value and setpoint CAN Intercontroller Comm
CAN Intercontroller Comm Redundancy

Units [-]
Description
This value informs if CAN Intercontroller communication Redundancy is enabled or not.
Note: In case that there is a mismatch between this value and setpoint CAN Intercontroller Comm

SD Card Status

Units [-]
Description
This value shows the actual status of the SD Card.
Value Meaning
Mount In Progress The SD Card is being booted.
Not Inserted There is no SD Card in the SD card slot detected.
The SD card is inserted but the setpoint SD Card File System
Unmount
(page 393) is set to Unmount option.
Ready To Use SD Card is mounted and ready to be used.
Format Required The wrong file system format of the SD Card is detected.
Formatting The formatting process of the SD Card is active.
Formatting Failed The formatting process failed.
Write Protected It is not possible to write data on SD Card (Read Only mode).
Used SD Card is not supported (wrong parameters of the SD
Not Supported
card).
This status is used for any other errors which are not covered by
Error
the states above.
SD Card Capacity

Units [GB]
Description
This value provides information about SD Card storage capacity in GB.
SD Card Free Space

Units [%]
Description
This value shows relative free space of SD Card storage.

History Lifetime

Units [%]
Description
This value shows the lifetime usage of non-volatile memory which is used for storing of history records.
Please refer to the table below for detailed information.
Value [%] Meaning

-1 Memory's lifetime usage can not be obtained.
10 Memory's lifetime usage is between 0-10%.
20 Memory's lifetime usage is between 11-20%..
110 Memory's lifetime usage is over 100 %. The memory may fail.
Forced Value Status

Units [-]
Description
This value contains list of all 32 LBIs for Forced Value (page 158). Logical 1 means that the respective
LBI is currently activated.

SW Key Feature List

Units [-]
Description
This value contains list of premium features which are unlocked by SW key. Logical 1 means that the
feature is activated and can be used without of restrictions.
1. CAN Intercontroller Redundancy
2. Modbus Master
3. Hot Swap Redundancy
4. PLC Extended
5. Variable Speed BESS

Hot Swap Redundancy Status

Units [-]
Description
This value contains list of status bits related to Hot Swap Redundancy. If Hot Swap Redundancy (page
364) = Master, at least one of the bits 01-04 is active, bits 05-08 are never active. If Hot Swap
Redundancy (page 364) = Backup, at least one of the bits 05-08 is active, bits 01-04 are never active. If
Hot Swap Redundancy (page 364) = Disabled, none of the bits is active.
Master: Backup this controller is the master

Alive the master is receiving heartbeat from backup
this controller is the master
Master: Backup the master is considered to be dead by the backup controller

Control the master is forced to the listening mode
the backup is controlling
this controller is the master
Master: Ready to
the master is alive
Control
the master is controlling/the master is ready to control
Master: Data this controller is the master

Synchro Fail the master is not receiving data from backup
Backup: Master this controller is the backup

Alive the backup is receiving heartbeat from master
this controller is the backup
Backup: Master the backup is considered to be dead by the master controller

Control the backup is forced to the listening mode
the master is controlling
this controller is the backup
Backup: Ready
the backup is alive
to Control
the backup is controlling/the backup is ready to control
Backup: Data this controller is the backup

Synchro Fail the backup is not receiving data from master

CAN16

Units [-]
Description
This value contains binary information about controllers connected via CAN2A (page 19) and/or CAN2B
(page 19) with CAN Controller Address (page 385) = <1,16>. Each bit represent controller with the
same CAN address as number of the bit.
Log. 1 - this controller receives messages from the controller with specific CAN address
Log. 0 - this controller does not receive messages from the controller with specific CAN address
CAN32

Units [-]
Description
CAN48

Units [-]
Description

CAN64

Units [-]
Description
Reg16

Units [-]
Description
Log. 1 - controller with this CAN address is in the same group (is connected to the same bus).
Log. 0 - controller with this CAN address is NOT in the same group (is NOT connected to the
same bus).
Reg32

Units [-]
Description
same bus).

Reg48

Units [-]
Description
same bus).
Reg64

Units [-]
Description
same bus).
Gen Loaded 16

Units [-]
Description
Log. 1 - controller with this CAN address is currently loaded
Log. 0 - controller with this CAN address is currently not loaded

Gen Loaded 32

Units [-]
Description
Gen Loaded 48

Units [-]
Description
Gen Loaded 64

Units [-]
Description

Group: User Buttons
User Buttons
Value group User Buttons Related FW 1.3.0

Units [-]
Description
State of User Buttons (page 220).
1. User Button 1 11. User Button 11 21. User Button 21 31. User Button 31
2. User Button 2 12. User Button 12 22. User Button 22 32. User Button 32
3. User Button 3 13. User Button 13 23. User Button 23
Group: Log Bout
Log Bout 1
Value group Log Bout Related FW 1.3.0

Units [-]
Description
State of binary outputs.
Log Bout 2

Units [-]
Description

Log Bout 3

Units [-]
Description
Log Bout 4

Units [-]
Description
Log Bout 5

Units [-]
Description
Log Bout 6

Units [-]
Description
Log Bout 7

Units [-]
Description

Log Bout 8

Units [-]
Description
Log Bout 9

Units [-]
Description
Log Bout 10

Units [-]
Description
Log Bout 11

Units [-]
Description
Log Bout 12

Units [-]
Description

Log Bout 13

Units [-]
Description
Log Bout 14

Units [-]
Description
Group: Scheduler
Time
Value group Scheduler Related FW 1.3.0

Units HH:MM:SS
Related
applications
Description
Shows setup time.
Date

Units DD.MM.YYYY
Description
Shows setup date.

Time Mode

Units [-]
Related
applications
Description
Shows setup time mode.
STD - Standard zone time (e.g GMT+1 for Prague)
DST - Daylight Saving Time = STD+1 (e.g. GMT+2 for Prague)
Sunrise Time

Units [hh:mm.ss]
Comm
object
Description
This value indicates the time until sunrise.
Sunset Time

Units [hh:mm.ss]
Comm
object
Description
This value indicates the time until sunset.
Time To Sunrise

Units [min]
Comm
object
Description
This value shows remaining time until sunrise.

Time To Sunset

Units [min]
Comm
object
Description
This value shows remaining time until sunset.
Exercise Timer 1

Units [hh:mm.ss]
Comm
object
Description
Value for Exercise Timer 1.
Exercise Timer 2

Units [hh:mm.ss]
Comm
object
Description
Exercise Timer 3

Units [hh:mm.ss]
Comm
object
Description

Exercise Timer 4

Units [hh:mm.ss]
Comm
object
Description
Exercise Timer 5

Units [hh:mm.ss]
Comm
object
Description
Exercise Timer 6

Units [hh:mm.ss]
Comm
object
Description
Exercise Timer 7

Units [hh:mm.ss]
Comm
object
Description

Exercise Timer 8

Units [hh:mm.ss]
Comm
object
Description
Exercise Timer 9

Units [hh:mm.ss]
Comm
object
Description
Exercise Timer 10

Units [hh:mm.ss]
Comm
object
Description
Exercise Timer 11

Units [hh:mm.ss]
Comm
object
Description

Exercise Timer 12

Units [hh:mm.ss]
Comm
object
Description
Group: Ethernet
Subgroup: Common For All Interfaces
MAC Address
Value group Ethernet Related FW 1.3.0

Units [-]
Description
Current MAC address of the controller's ethernet interface.
Subgroup: Ethernet Port Status
ETH Port 1 Status

Units [-]
Description
This value reflects what communication mode is used on the Ethernet Port 1.
Link Down There is no connected cable to the Ethernet Port (socket) or the cable is broken.
10- HD 10 Mbit Half-Duplex
10- FD 10 Mbit Full-Duplex
Note: Note: At one time the Half-Duplex can only send or receive the information whereas Full-
Duplex can do both at once.

ETH Port 2 Status

Units [-]
Description
ETH Port 3 Status

Units [-]
Description

Subgroup: Trusted Interface
Current IP Address

Units [-]
Description
Current IP address of the Ethernet 1 (page 19) interface.
Current Subnet Mask

Units [-]
Description
Current subnet mask of the Ethernet 1 (page 19) interface.
Current Gateway

Units [-]
Description
Current gateway address the Ethernet 1 (page 19) communication.
ETH Interface Status

Units [-]
Description
Current status.of the Ethernet 1 (page 19) communication.

Subgroup: Untrusted Interface
Current IP Address

Units [-]
Related
applications
Description
Current Subnet Mask

Units [-]
Description
Current Gateway

Units [-]
Description
Current IP gateway address of the Ethernet 2 (page 19) communications.
Primary DNS

Units [-]
Description
Current domain name server of the Ethernet 2 (page 19) interface.

Secondary DNS

Units [-]
Description
Backup domain name server of the Ethernet 2 (page 19) interface.

Units [-]
Description
Current status of the Ethernet 2 (page 19) communication.

AirGate Status

Units [-]
Description
Diagnostic code for AirGate connection. Helps with troubleshooting.
IMPORTANT: If the AirGate key in the Access Administration is empty the controller will
not connect to the AirGate despite the function is enabled. Access Administration is
available in Tools of the InteliConfig.
Code Value Description

Not trying to connect to AirGate. This is initial value of the
0 Not defined
status.
1 Waiting to connect Waiting for the next attempt to connect to a node.
Resolving the domain name of the node to which it is
2 Resolving
attempting to connect.
3 Connecting Attempting to estabilish TCP link to the node.
4 Creating secure channel Encrypted channel is being negotiated.
5 Registration Encrypted channel has been estabilished.
6 Connected, inoperable AirGate server has not sent an authorization yet.
AiGate server authorized the connection and the AirGate
7 Connected, operable
connection is up and running.
The service is enabled but suspended due to empty
8 Suspended, empty key
AirGate key.
AirGate ID

Units [-]
Description
Identification string generated by AirGate server for the purpose of establishing communication via
InteliConfig or any other supported PC tool.

AirGate Servicing Node

Units [-]
Description
This value displays the IP address to Servicing node to which is controller connected in order to use
AirGate connection.

Last E-mail Result

Units [-]
Description
Result of last email, which was sent by controller.
Code Description
0 Email was successfully sent.
1 SIMCom declined connection request.
2 It is not possible to establish connection with SMTP server.
3 SMTP server is not ready for communication.
4 Maximum transmitted data length not defined.
5 No response from SMTP server.
6 Command to SMTP server not sent.
7 Did not receive data from SMTP server.
8 HELO command was refused.
9 EHLO command was refused.
10 SMTP server does not support 8-bit encoding.
11 AUTH LOGIN command was refused.
12 Wrong user name.
13 Wrong password.
14 MAIL FROM command was refused.
15 RCPT TO command was refused.
16 DATA command was refused.
17 Sending of email failed.
18 SMTP server rejected email data.
19 SMTP server rejected email data.
20 QUIT command was refused.
21 There is no valid server IP address.
22 Process of sending email aborted.
23 Closing connection error.
24 Failed to accept server response after connection is established.
25 It is impossible to create data for command DATA.
26 It is impossible to read data for command DATA.
27 Email address can???t be read.
28 Error during encoding process.
29 Error during HMAC MD5 encoding process.
30 There is no attempt for sending email yet.

31 Cannot resolve SMTP server's IP address.
32 Error while reading CO 24327 (base64 email data)
33 Problem with authorization type (i.e. smtp.gmail.com support only STARTTLS)
34 SMTP server does not support STARTTLS command.
35 STARTTLS command was refused.
36 There is a problem during TLS handshake process.
Subgroup: Modbus Interface
Current IP Address
ETH Interface 3 -
Modbus
Units [-]
Description
Current Subnet Mask
ETH Interface 3 -
Modbus
Units [-]
Description
Current Gateway
ETH Interface 3 -
Modbus
Units [-]
Description
Current IP gateway address of the Ethernet 3 (page 19) communications.

Primary DNS
ETH Interface 3 -
Modbus
Units [-]
Description
Current domain name server of the Ethernet 3 (page 19) interface.
Secondary DNS
ETH Interface 3 -
Modbus
Units [-]
Description
Backup domain name server of the Ethernet 3 (page 19) interface.
ETH Interface 3 -
Modbus
Units [-]
Description
Current status of the Ethernet 3 (page 19) communication.
Group: PLC
PLC-AOUT 1
Value group PLC Related FW 1.3.0

Units [-]
Description
State of analog output of PLC.

PLC-AOUT 2

Units [-]
Description
PLC-AOUT 3

Units [-]
Description
PLC-AOUT 4

Units [-]
Description
PLC-AOUT 5

Units [-]
Description
PLC-AOUT 6

Units [-]
Description

PLC-AOUT 7

Units [-]
Description
PLC-AOUT 8

Units [-]
Description
PLC-AOUT 9

Units [-]
Description
PLC-AOUT 10

Units [-]
Description
PLC-AOUT 11

Units [-]
Description

PLC-AOUT 12

Units [-]
Description
PLC-AOUT 13

Units [-]
Description
PLC-AOUT 14

Units [-]
Description
PLC-AOUT 15

Units [-]
Description
PLC-AOUT 16

Units [-]
Description

PLC-AOUT 17

Units [-]
Description
PLC-AOUT 18

Units [-]
Description
PLC-AOUT 19

Units [-]
Description
PLC-AOUT 20

Units [-]
Description
PLC-AOUT 21

Units [-]
Description

PLC-AOUT 22

Units [-]
Description
PLC-AOUT 23

Units [-]
Description
PLC-AOUT 24

Units [-]
Description
PLC-AOUT 25

Units [-]
Description
PLC-AOUT 26

Units [-]
Description

PLC-AOUT 27

Units [-]
Description
PLC-AOUT 28

Units [-]
Description
PLC-AOUT 29

Units [-]
Description
PLC-AOUT 30

Units [-]
Description
PLC-AOUT 31

Units [-]
Description

PLC-AOUT 32

Units [-]
Description
PLC-AOUT 33

Units [-]
Description
PLC-AOUT 34

Units [-]
Description
PLC-AOUT 35

Units [-]
Description
PLC-AOUT 36

Units [-]
Description

PLC-AOUT 37

Units [-]
Description
PLC-AOUT 38

Units [-]
Description
PLC-AOUT 39

Units [-]
Description
PLC-AOUT 40

Units [-]
Description
PLC-AOUT 41

Units [-]
Description

PLC-AOUT 42

Units [-]
Description
PLC-AOUT 43

Units [-]
Description
PLC-AOUT 44

Units [-]
Description
PLC-AOUT 45

Units [-]
Description
PLC-AOUT 46

Units [-]
Description

PLC-AOUT 47

Units [-]
Description
PLC-AOUT 48

Units [-]
Description
PLC-AOUT 49

Units [-]
Description
PLC-AOUT 50

Units [-]
Description
PLC-AOUT 51

Units [-]
Description

PLC-AOUT 52

Units [-]
Description
PLC-AOUT 53

Units [-]
Description
PLC-AOUT 54

Units [-]
Description
PLC-AOUT 55

Units [-]
Description
PLC-AOUT 56

Units [-]
Description

PLC-AOUT 57

Units [-]
Description
PLC-AOUT 58

Units [-]
Description
PLC-AOUT 59

Units [-]
Description
PLC-AOUT 60

Units [-]
Description
PLC-AOUT 61

Units [-]
Description

PLC-AOUT 62

Units [-]
Description
PLC-AOUT 63

Units [-]
Description
PLC-AOUT 64

Units [-]
Description
PLC-BOUT 1

Units [-]
Description
State of binary outputs of PLC.
PLC-BOUT 2

Units [-]
Description

PLC-BOUT 3

Units [-]
Description
PLC-BOUT 4

Units [-]
Description
PLC-BOUT 5

Units [-]
Description
PLC-BOUT 6

Units [-]
Description
PLC-BOUT 7

Units [-]
Description

PLC-BOUT 8

Units [-]
Related
applications
Description
PLC-BOUT 9

Units [-]
Description
PLC-BOUT 10

Units [-]
Description
PLC-BOUT 11

Units [-]
Description
PLC-BOUT 12

Units [-]
Description

PLC-BOUT 13

Units [-]
Description
PLC-BOUT 14

Units [-]
Description
PLC-BOUT 15

Units [-]
Description
PLC-BOUT 16

Units [-]
Related
applications
Description
PLC-BOUT 17

Units [-]
Description

PLC-BOUT 18

Units [-]
Description
PLC-BOUT 19

Units [-]
Description
PLC-BOUT 20

Units [-]
Description
PLC-BOUT 21

Units [-]
Description
PLC-BOUT 22

Units [-]
Description

PLC-BOUT 23

Units [-]
Description
PLC-BOUT 24

Units [-]
Description
PLC-BOUT 25

Units [-]
Description
PLC-BOUT 26

Units [-]
Description
PLC-BOUT 27

Units [-]
Description

PLC-BOUT 28

Units [-]
Description
PLC-BOUT 29

Units [-]
Description
PLC-BOUT 30

Units [-]
Description
PLC-BOUT 31

Units [-]
Description
PLC-BOUT 32

Units [-]
Description

PLC Resource 1

Units [-]
Description
Internal value of PLC block.
PLC Resource 2

Units [-]
Description
PLC Resource 3

Units [-]
Description
PLC Resource 4

Units [-]
Description
PLC Resource 5

Units [-]
Description

PLC Resource 6

Units [-]
Description
PLC Resource 7

Units [-]
Description
PLC Resource 8

Units [-]
Description
PLC Resource 9

Units [-]
Description
PLC Resource 10

Units [-]
Description

PLC Resource 11

Units [-]
Description
PLC Resource 12

Units [-]
Description
PLC Resource 13

Units [-]
Description
PLC Resource 14

Units [-]
Description
PLC Resource 15

Units [-]
Description

PLC Resource 16

Units [-]
Description
Group: Remote Control
RemoteControl2B 1
Value group Remote Control Related FW 1.3.0

Units -
Description
This value contains user data written over Modbus-RTU, Modbus/TCP (page 311). Data type of this
value is Int16.
RemoteControl2B 2

Units -
Description
value is Int16.
RemoteControl2B 3

Units -
Description
value is Int16.

RemoteControl2B 4

Units -
Description
value is Int16.
RemoteControl2B 5

Units -
Description
value is Int16.
RemoteControl2B 6

Units -
Description
value is Int16.
RemoteControl2B 7

Units -
Description
value is Int16.

RemoteControl2B 8

Units -
Description
value is Int16.
RemoteControl4B 1

Units -
Description
value is Int32.
RemoteControl4B 2

Units -
Description
value is Int32.
RemoteControl4B 3

Units -
Description
value is Int32.

RemoteControl4B 4

Units -
Description
value is Int32.
RemoteControlBin

Units -
Description
value is Binary16.
Group: DIST-IN 1-32
Binary inputs 1 1-8
Value group DIST-IN 1-32 Related FW 1.3.0

Units [-]
Description
This value contains first 8 Binary Inputs of distributed binary inputs from DIST-IN (page 33) module 1.
Received data are from Controller Unit with CAN Controller Address (page 385) = 1.
1. DISTBIN-1 1
2. DISTBIN-1 2
3. DISTBIN-1 3
4. DISTBIN-1 4
5. DISTBIN-1 5
6. DISTBIN-1 6
7. DISTBIN-1 7
8. DISTBIN-1 8

Binary inputs 1 9-16

Units [-]
Description
This value contains second 8 Binary Inputs of distributed binary inputs from DIST-IN (page 33) module
1.
IMPORTANT: This value is supported only when CAN Intercontroller Comm Mode (page
389) = 64C CAN FD or 32C CAN FD or 8C CAN FD!
1. DISTBIN-1 9
2. DISTBIN-1 10
3. DISTBIN-1 11
4. DISTBIN-1 12
5. DISTBIN-1 13
6. DISTBIN-1 14
7. DISTBIN-1 15
8. DISTBIN-1 16

Units [-]
Description
This value contains third 8 Binary Inputs of distributed binary inputs from DIST-IN (page 33) module 1.
1. DISTBIN-1 17
2. DISTBIN-1 18
3. DISTBIN-1 19
4. DISTBIN-1 20
5. DISTBIN-1 21
6. DISTBIN-1 22
7. DISTBIN-1 23
8. DISTBIN-1 24


Units [-]
Description
This value contains fourth 8 Binary Inputs of distributed binary inputs from DIST-IN (page 33) module 1.
1. DISTBIN-1 25
2. DISTBIN-1 26
3. DISTBIN-1 27
4. DISTBIN-1 28
5. DISTBIN-1 29
6. DISTBIN-1 30
7. DISTBIN-1 31
8. DISTBIN-1 32
DISTAIN-1 1

Units Based on configuration
Description
This value contains data of first distributed analog input from DIST-IN (page 33) module which are
received from Controller Unit with CAN Controller Address (page 385) = 1.
IMPORTANT: This value is received (and visible) only when it is configured with sensor
type "Electronic".

DISTAIN-1 2

Description
This value contains data of second distributed analog input from DIST-IN (page 33) module which are
type "Electronic".
DISTAIN-1 3

Description
This value contains data of third distributed analog input from DIST-IN (page 33) module which are
type "Electronic".
DISTAIN-1 4

Description
This value contains data of fourth distributed analog input from DIST-IN (page 33) module which are
type "Electronic".

Binary inputs 2 1-8

Units [-]
Description
1. DISTBIN-2 1
2. DISTBIN-2 2
3. DISTBIN-2 3
4. DISTBIN-2 4
5. DISTBIN-2 5
6. DISTBIN-2 6
7. DISTBIN-2 7
8. DISTBIN-2 8

Units [-]
Description
This value contains second 8 Binary Inputs of distributed binary inputs from DIST-IN (page 33) module
2.
1. DISTBIN-2 9
2. DISTBIN-2 10
3. DISTBIN-2 11
4. DISTBIN-2 12
5. DISTBIN-2 13
6. DISTBIN-2 14
7. DISTBIN-2 15
8. DISTBIN-2 16


Units [-]
Description
This value contains third 8 Binary Inputs of distributed binary inputs from DIST-IN (page 33) module 2.
1. DISTBIN-2 17
2. DISTBIN-2 18
3. DISTBIN-2 19
4. DISTBIN-2 20
5. DISTBIN-2 21
6. DISTBIN-2 22
7. DISTBIN-2 23
8. DISTBIN-2 24

Units [-]
Description
This value contains fourth 8 Binary Inputs of distributed binary inputs from DIST-IN (page 33) module 2.
1. DISTBIN-2 25
2. DISTBIN-2 26
3. DISTBIN-2 27
4. DISTBIN-2 28
5. DISTBIN-2 29
6. DISTBIN-2 30
7. DISTBIN-2 31
8. DISTBIN-2 32

DISTAIN-2 1

Description
type "Electronic".
DISTAIN-2 2

Description
type "Electronic".
DISTAIN-2 3

Description
type "Electronic".

DISTAIN-2 4

Description
type "Electronic".
Group: DIST-IN 33-64

Units [-]
Description
1. DISTBIN-33 1
2. DISTBIN-33 2
3. DISTBIN-33 3
4. DISTBIN-33 4
5. DISTBIN-33 5
6. DISTBIN-33 6
7. DISTBIN-33 7
8. DISTBIN-33 8


Units [-]
Description
This value contains last 8 Binary Inputs of distributed binary inputs from DIST-IN (page 33) module 33.
389) = 64C CAN FD or 8C CAN FD!
1. DISTBIN-33 9
2. DISTBIN-33 10
3. DISTBIN-33 11
4. DISTBIN-33 12
5. DISTBIN-33 13
6. DISTBIN-33 14
7. DISTBIN-33 15
8. DISTBIN-33 16

Units [-]
Description
1. DISTBIN-33 17
2. DISTBIN-33 18
3. DISTBIN-33 19
4. DISTBIN-33 20
5. DISTBIN-33 21
6. DISTBIN-33 22
7. DISTBIN-33 23
8. DISTBIN-33 24


Units [-]
Description
1. DISTBIN-33 25
2. DISTBIN-33 26
3. DISTBIN-33 27
4. DISTBIN-33 28
5. DISTBIN-33 29
6. DISTBIN-33 30
7. DISTBIN-33 31
8. DISTBIN-33 32
DISTAIN-33 1

Description
type "Electronic".

DISTAIN-33 2

Description
type "Electronic".
DISTAIN-33 3

Description
type "Electronic".
DISTAIN-33 4

Description
type "Electronic".


Units [-]
Description
1. DISTBIN-34 1
2. DISTBIN-34 2
3. DISTBIN-34 3
4. DISTBIN-34 4
5. DISTBIN-34 5
6. DISTBIN-34 6
7. DISTBIN-34 7
8. DISTBIN-34 8

Units [-]
Description
This value contains last 8 Binary Inputs of distributed binary inputs from DIST-IN (page 33) module 34.
1. DISTBIN-34 9
2. DISTBIN-34 10
3. DISTBIN-34 11
4. DISTBIN-34 12
5. DISTBIN-34 13
6. DISTBIN-34 14
7. DISTBIN-34 15
8. DISTBIN-34 16


Units [-]
Description
1. DISTBIN-34 17
2. DISTBIN-34 18
3. DISTBIN-34 19
4. DISTBIN-34 20
5. DISTBIN-34 21
6. DISTBIN-34 22
7. DISTBIN-34 23
8. DISTBIN-34 24

Units [-]
Description
1. DISTBIN-34 25
2. DISTBIN-34 26
3. DISTBIN-34 27
4. DISTBIN-34 28
5. DISTBIN-34 29
6. DISTBIN-34 30
7. DISTBIN-34 31
8. DISTBIN-34 32

DISTAIN-34 1

Description
type "Electronic".
DISTAIN-34 2

Description
type "Electronic".
DISTAIN-34 3

Description
type "Electronic".

DISTAIN-34 4

Description
type "Electronic".
Group: SH Modules
SHBIN-1
Value group SH Modules Related FW 1.3.0

Units [-]
Description
This value contains Binary Inputs of shared binary inputs from SHBIN module 1.
1. SHBIN-1 1
2. SHBIN-1 2
3. SHBIN-1 3
4. SHBIN-1 4
5. SHBIN-1 5
6. SHBIN-1 6
7. SHBIN-1 7
8. SHBIN-1 8

SHBIN-2

Units [-]
Description
1. SHBIN-2 1
2. SHBIN-2 2
3. SHBIN-2 3
4. SHBIN-2 4
5. SHBIN-2 5
6. SHBIN-2 6
7. SHBIN-2 7
8. SHBIN-2 8
SHBIN-3

Units [-]
Description
1. SHBIN-3 1
2. SHBIN-3 2
3. SHBIN-3 3
4. SHBIN-3 4
5. SHBIN-3 5
6. SHBIN-3 6
7. SHBIN-3 7
8. SHBIN-3 8

SHBIN-4

Units [-]
Description
1. SHBIN-4 1
2. SHBIN-4 2
3. SHBIN-4 3
4. SHBIN-4 4
5. SHBIN-4 5
6. SHBIN-4 6
7. SHBIN-4 7
8. SHBIN-4 8
SHBIN-5

Units [-]
Description
1. SHBIN-5 1
2. SHBIN-5 2
3. SHBIN-5 3
4. SHBIN-5 4
5. SHBIN-5 5
6. SHBIN-5 6
7. SHBIN-5 7
8. SHBIN-5 8

SHBIN-6

Units [-]
Description
1. SHBIN-6 1
2. SHBIN-6 2
3. SHBIN-6 3
4. SHBIN-6 4
5. SHBIN-6 5
6. SHBIN-6 6
7. SHBIN-6 7
8. SHBIN-6 8
SHBOUT-1

Units [-]
Description
This value contains Binary Inputs of shared binary outputs from SHBOUT module 1.
1. SHBOUT-1 1
2. SHBOUT-1 2
3. SHBOUT-1 3
4. SHBOUT-1 4
5. SHBOUT-1 5
6. SHBOUT-1 6
7. SHBOUT-1 7
8. SHBOUT-1 8

SHBOUT-2

Units [-]
Description
1. SHBOUT-2 1
2. SHBOUT-2 2
3. SHBOUT-2 3
4. SHBOUT-2 4
5. SHBOUT-2 5
6. SHBOUT-2 6
7. SHBOUT-2 7
8. SHBOUT-2 8
SHBOUT-3

Units [-]
Description
1. SHBOUT-3 1
2. SHBOUT-3 2
3. SHBOUT-3 3
4. SHBOUT-3 4
5. SHBOUT-3 5
6. SHBOUT-3 6
7. SHBOUT-3 7
8. SHBOUT-3 8

SHBOUT-4

Units [-]
Description
1. SHBOUT-4 1
2. SHBOUT-4 2
3. SHBOUT-4 3
4. SHBOUT-4 4
5. SHBOUT-4 5
6. SHBOUT-4 6
7. SHBOUT-4 7
8. SHBOUT-4 8
SHBOUT-5

Units [-]
Description
1. SHBOUT-5 1
2. SHBOUT-5 2
3. SHBOUT-5 3
4. SHBOUT-5 4
5. SHBOUT-5 5
6. SHBOUT-5 6
7. SHBOUT-5 7
8. SHBOUT-5 8

SHBOUT-6

Units [-]
Description
1. SHBOUT-6 1
2. SHBOUT-6 2
3. SHBOUT-6 3
4. SHBOUT-6 4
5. SHBOUT-6 5
6. SHBOUT-6 6
7. SHBOUT-6 7
8. SHBOUT-6 8
SHAIN-1 1

Units [-]
Description
This value contains data of first shared analog input from SHAOUT module 1.
type "Electronic".
SHAIN-1 2

Units [-]
Description
This value contains data of second shared analog input from SHAOUT module 1.
type "Electronic".

SHAIN-1 3

Units [-]
Description
This value contains data of third shared analog input from SHAOUT module 1.
type "Electronic".
SHAIN-1 4

Units [-]
Description
This value contains data of fourth shared analog input from SHAOUT module 1.
type "Electronic".
SHAIN-2 1

Units [-]
Description
This value contains data of first shared analog input from SHAOUT module 2.
type "Electronic".
SHAIN-2 2

Units [-]
Description
This value contains data of second shared analog input from SHAOUT module 2.
type "Electronic".

SHAIN-2 3

Units [-]
Description
This value contains data of third shared analog input from SHAOUT module 2.
type "Electronic".
SHAIN-2 4

Units [-]
Description
This value contains data of fourth shared analog input from SHAOUT module 2.
type "Electronic".
Group: Virtual Shared OUT
Binary outputs 1-8
Value group Virtual Shared OUT Related FW 1.3.0

Units [-]
Description
This value contains first 8 Binary Outputs of distributed binary outputs from DIST-OUT (page 34)
module.
1. DISTBOUT 1
2. DISTBOUT 2
3. DISTBOUT 3
4. DISTBOUT 4
5. DISTBOUT 5
6. DISTBOUT 6
7. DISTBOUT 7
8. DISTBOUT 8

Binary outputs 9-16

Units [-]
Description
This value contains second 8 Binary Outputs of distributed binary outputs from DIST-OUT (page 34)
module.
1. DISTBOUT 9
2. DISTBOUT 10
3. DISTBOUT 11
4. DISTBOUT 12
5. DISTBOUT 13
6. DISTBOUT 14
7. DISTBOUT 15
8. DISTBOUT 16
Binary outputs 17-24

Units [-]
Description
This value contains third 8 Binary Outputs of distributed binary outputs from DIST-OUT (page 34)
module.
1. DISTBOUT 17
2. DISTBOUT 18
3. DISTBOUT 19
4. DISTBOUT 20
5. DISTBOUT 21
6. DISTBOUT 22
7. DISTBOUT 23
8. DISTBOUT 24

Binary outputs 25-32

Units [-]
Description
This value contains fourth 8 Binary Outputs of distributed binary outputs from DIST-OUT (page 34)
module.
1. DISTBOUT 25
2. DISTBOUT 26
3. DISTBOUT 27
4. DISTBOUT 28
5. DISTBOUT 29
6. DISTBOUT 30
7. DISTBOUT 31
8. DISTBOUT 32

9.1.5 Application Curves
List of Application Curves
Q(Um) 858
Qref/Ulim 859
Q(P) 860
PF(P) 861
P(Um) 862
P Mom/Pave Max 863
Capability L 864
Capability C 865
Power Over Frequency 866
Power Under Frequency 867
P For Q UQ L 868
P For Q UQ C 869
P For Q PQ L 870
P For Q PQ C 871
LVRT 3-phase 872
LVRT 2-phase 873
LVRT 1-phase 874
OVRT 875
6 back to Controller objects

Q(Um)
Related FW 1.3.0 Related applications MPTM

App Curve ID 0
Description
This curve is used during Q(Um) (page 263)PF/Q control (page 257) power control.
X-axe is relative value of Umains to Mains/Bus Nominal Voltage Ph-N (page 373).
Y-axe is relative value of BESS Required Q (page 757) to Samax (page 367).
Note: Umains is average value of Mains/Bus Voltage L1-N (page 731), Mains/Bus Voltage L2-N
(page 731) and Mains/Bus Voltage L3-N (page 732).
Default values
X-axe [%] Y-axe [%]

60.00 33
96.00 33
100.00 0
104.00 -33
140.00 -33
Default appearance
6 back to Application Curves

Qref/Ulim

App Curve ID 1
Description
This curve is used during Qref/Ulim (page 265)PF/Q control (page 257) power control.
X-axe is relative value of Umains to Mains/Bus Nominal Voltage Ph-N (page 373)
Default values
X-axe [%] Y-axe [%]

60.00 33
94.00 33
96.00 0
100.00 0
104.00 -33
140.00 -33
Default appearance

Q(P)

App Curve ID 2
Description
This curve is used during Q(P) (page 264)PF/Q control (page 257) power control.
X-axe is relative value of BESS P (page 664) to Installed Power (page 368) (or Nominal power (page
368) in case Installed Power (page 368) = OFF).
Default values
X-axe [%] Y-axe [%]

-100.00 33
-90.00 33
-60.00 5
-50.00 0
-10.00 0
0.00 0
10.00 0
50.00 0
60.00 -5
90.00 -33
100.00 -33
Default appearance

PF(P)

App Curve ID 3
Description
This curve is used during PF(Pm) (page 262)PF/Q control (page 257) power control.
X-axe is relative value of Umains to Mains/Bus Nominal Voltage Ph-N (page 373)
Y-axe is BESS Required PF (page 757) in combination with BESS Required PF Character (page
757).
Default values
X-axe [%] Y-axe [-]

-100.00 1.050
-80.00 1.050
-50.00 1.000
-20.00 0.950
0.00 0.950
20.00 0.950
50.00 1.000
80.00 1.050
100.00 1.050
Default appearance

P(Um)

App Curve ID 16
Description
This curve is used during Power Regulation Based On Actual Mains Voltage (page 297).
Y-axe is relative value of BESS Required P Target (page 753) to Installed Power (page 368) or
Pmom (page 721) based on P(Um) (page 544).
Default values
X-axe [%] Y-axe [%]

60.00 0
100.00 0
110.00 0
112.00 -100
120.00 -100
Default appearance

P Mom/Pave Max

App Curve ID 17
Description
This curve is used during Pave (page 304) function.
X-axe is time in seconds
Y-axe is value of LAI PMOM (PAGE 993) related to setpoint Pave (page 560)
Default values
X-axe [s] Y-axe [-] X-axe [s] Y-axe [-]

0.00 1.670 2.00 1.125
0.80 1.670 2.40 1.125
0.90 1.603 2.80 1.082
1.00 1.543 3.20 1.054
1.10 1.489 3.60 1.035
1.20 1.440 4.00 1.023
1.30 1.396 4.40 1.015
1.40 1.357 4.80 1.010
1.50 1.321 5.20 1.007
1.60 1.289 5.60 1.004
1.70 1.260 6.00 1.002
1.80 1.234 7.00 1.001
2.00 1.190 10.00 1.000
Default appearance

Capability L
Related FW 1.3.0 Related applications MINT, MPTM

App Curve ID 4
Description
This curve defines BESS Operation Area (page 1) within which it can deliver reactive power
continuously without overheating while BESS Load Character (page 667) = L.
X-axe is relative value of BESS P (page 664) to Nominal power (page 368).
Y-axe is relative value of BESS Q (page 665) to Samax (page 367).
Note: The samax value is counted from Nominal Current (page 369) and BESS Nominal Voltage Ph-
N (page 373) (or BESS Nominal Voltage Ph-Ph (page 373)) in case that Samax (page 367) = OFF.
Default values
X-axe [%] Y-axe [%]

-10 0
0 0
100 106
102 106
Default appearance

Capability C

App Curve ID 5
Description
This curve defines BESS Operation Area (page 1) within which it can deliver reactive power
continuously without overheating while BESS Load Character (page 667) = C.
X-axe is relative value of BESS P (page 664) to Nominal power (page 368).
Y-axe is relative value of BESS Q (page 665) to Samax (page 367).
IMPORTANT: The Capability C curve have to be setup according to the Capability curve of
the worst (weakest) BESS in order to ensure right functionality of the whole system.
Note: The samax value is counted from Nominal Current (page 369) and BESS Nominal Voltage Ph-
N (page 373) (or BESS Nominal Voltage Ph-Ph (page 373)) in case that Samax (page 367) = OFF.
Default values
X-axe [%] Y-axe [%]

-10 0
0 0
100 -60
102 -60
Default appearance

Power Over Frequency

App Curve ID 6
Description
This curve is used duringPower reduction by over frequency - PoF (page 294).
X-axe is Δf = Mains/Bus Frequency (page 731) - Nominal Frequency (page 377).
Y-axe is relative value of BESS Required P (page 753) to Installed Power (page 368) (or Nominal
power (page 368) in case Installed Power (page 368) = OFF).
Note: Δf has to be higher than 0.
Default values
X-axe [Hz] Y-axe [%]

0.000 0.00
0.200 0.00
1.500 -52.00
2.700 -100.00
Default appearance

Power Under Frequency

App Curve ID 7
Description
This curve is used duringPower increase by under frequency - PuF (page 295).
X-axe is Δf = Mains/Bus Frequency (page 731) - Nominal Frequency (page 377).
Y-axe is relative value of BESS Required P (page 753) to Installed Power (page 368) (or Nominal
power (page 368) in case Installed Power (page 368) = OFF).
Note: Δf has to be lower than 0.
Default values
X-axe [Hz] Y-axe [%]

-2.700 100.00
-2.500 92.00
-0.200 0.00
0.000 0.00
Default appearance

P For Q UQ L

App Curve ID 8
Description
This curve is used to define UQ area where the BESS can operate during P For Q (page 301) while
BESS Load Character (page 667) = L.
Default values
X-axe [%] Y-axe [%]

0.00 00
90.00 00
90.00 33
107.50 33
110.00 0
200.00 0
Default appearance

P For Q UQ C

App Curve ID 9
Description
This curve is used to define UQ area where the BESS can operate during P For Q (page 301) while
BESS Load Character (page 667) = C.
Default values
X-axe [%] Y-axe [%]

0.00 00
90.00 00
92.50 -33
110.00 -33
110.00 0
200.00 0
Default appearance

P For Q PQ L

App Curve ID 10
Description
This curve is used to define PQ area where the BESS can operate during P For Q (page 301) while
BESS Load Character (page 667) = L.
Y-axe is relative value of BESS Q (page 665) to Installed Power (page 368).(or Nominal power (page
Default values
X-axe [%] Y-axe [%]

0.00 0
9.00 2
10.00 2
10.00 10
20.00 33
100.00 33
Default appearance

P For Q PQ C

App Curve ID 11
Description
This curve is used to define PQ area where the BESS can operate during P For Q (page 301) while
BESS Load Character (page 667) = C.
Y-axe is relative value of BESS Q (page 665) to Installed Power (page 368).(or Nominal power (page
Default values
X-axe [%] Y-axe [%]

0.00 0
9.00 -5
10.00 -5
10.00 -10
20.00 -33
100.00 -33
Default appearance

LVRT 3-phase

App Curve ID 12
Description
This curve is used during Dynamic Support - VRT (page 299). All of Mains/Bus Voltage L1-N (page
731), Mains/Bus Voltage L2-N (page 731) and Mains/Bus Voltage L3-N (page 732) has to be under
Mains/Bus Nominal Voltage Ph-N (page 373) to activate LVRT.
X-axe is time for which values have to be over the limit.
Y-axe is relative value of Umains to Mains/Bus Nominal Voltage Ph-N (page 373).
Default values
X-axe [s] Y-axe [%]

0.00 30.0
0.15 30.0
0.70 70.0
1.50 70.0
60.00 85.0
60.00 90.0
61.00 90.0
Default appearance

LVRT 2-phase

App Curve ID 13
Description
This curve is used during Dynamic Support - VRT (page 299). At least 2 of Mains/Bus Voltage L1-N
(page 731), Mains/Bus Voltage L2-N (page 731) and Mains/Bus Voltage L3-N (page 732) has to be
under Mains/Bus Nominal Voltage Ph-N (page 373) to activate LVRT.
Default values
X-axe [s] Y-axe [%]

0.00 30.0
0.22 30.0
0.22 60.0
0.70 60.0
1.50 75.0
3.00 75.0
3.00 85.0
60.00 85.0
60.00 90.0
61.00 90.0
Default appearance

LVRT 1-phase

App Curve ID 14
Description
under Mains/Bus Nominal Voltage Ph-N (page 373) to activate LVRT.
Default values
X-axe [s] Y-axe [%]

0.00 30.0
0.15 30.0
0.15 70.0
0.70 70.0
1.50 85.0
60.00 85.0
60.00 90.0
61.00 90.0
Default appearance

OVRT

App Curve ID 15
Description
over Mains/Bus Nominal Voltage Ph-N (page 373) to activate LVRT.
Default values
X-axe [s] Y-axe [%]

0.00 125.0
0.10 125.0
0.10 120.0
5.00 120.0
5.00 115.0
60.00 115.0
60.00 110.0
61.00 110.0
Default appearance

9.1.6 Logical binary inputs
What Logical binary inputs are:
Logical binary inputs are inputs for binary values and functions.
Alphabetical groups of Logical binary inputs

LBI: A 879
LBI: B 879
LBI: C 885
LBI: E 885
LBI: F 886
LBI: G 893
LBI: H 894
LBI: I 896
LBI: L 896
LBI: M 900
LBI: N 905
LBI: P 905
LBI: R 913
LBI: S 915
LBI: T 917
LBI: W 918
For full list of Logical binary inputs go to the chapter Logical binary inputs alphabetically (page 877).

Logical binary inputs alphabetically
LBI: A 879 Forced Value Input 10 889 Load Reduction 2 896

Application MINT 879 Forced Value Input 11 889 Load Reduction 3 897
Application MPTM 879 Forced Value Input 12 889 Load Reduction 4 897
LBI: B 879 Forced Value Input 13 889 Load Reduction Enable 897
BATT Discharge Enable 879 Forced Value Input 14 889 Load Res 2 Active 898
BATT Charge Enable 879 Forced Value Input 15 890 Load Res 3 Active 899
BCB Button 880 Forced Value Input 16 890 Load Res 4 Active 900
BCB Disable 880 Forced Value Input 17 890 LBI: M 900
BCB Feedback 881 Forced Value Input 18 890 Mains Fail Block 900
BCB Feedback Negative 882 Forced Value Input 19 890 Manual Load
BCB Secondary Feedback Forced Value Input 20 891 Reconnection 901
Negative 883 MCB Button 901
Forced Value Input 21 891
BCB Secondary Feedback 884 MCB Disable 901
BESS Output Control MCB Feedback 902
Mode U-f/P-Q 884 MCB Feedback Negative 903
BESS Ready To Load 885 Min Run Power Act 1 904
LBI: C 885 Min Run Power Act 2 904
Conditioned Hours
Forced Value Input 27 892 Min Run Power Act 3 905
Counter 1 885
Forced Value Input 28 892 LBI: N 905
Conditioned Hours
NCB Feedback 905
Counter 2 885 Forced Value Input 29 892
LBI: P 905
LBI: E 885 Forced Value Input 30 893
Post VRT 905
ECU Key Switch 885 Forced Value Input 31 893
Precharge Finished 906
Emergency MAN 886 Forced Value Input 32 893
Protection Force Disable 1 906
Emergency Stop 886 LBI: G 893
LBI: F 886 Group link 893
Fault Reset Button 886 Geo Home Position 893
Pulse Counter 1 908
Force Island 886 Geo-Fencing Enable 894
Pulse Counter 2 908
Force Parallel 887 LBI: H 894
Horn Reset Button 894 PV 01 Operable 908
Hot Swap Ctrl Block 895 PV 02 Operable 908
Hot Swap Heartbeat PV 03 Operable 908
Detect 895 PV 04 Operable 909
Hot Swap Recovery 895 PV 05 Operable 909
LBI: I 896 PV 06 Operable 909
Inverter Start Disabled 896 PV 07 Operable 909
LBI: L 896 PV 08 Operable 909
Load Reduction 1 896 PV 09 Operable 910

PV 10 Operable 910
PV 11 Operable 910
PV 12 Operable 910
PV 13 Operable 910
PV 14 Operable 911
PV 15 Operable 911
PV 16 Operable 911
PVCB Button 911
PVCB Disable 912
PVCB Feedback 912
PVCB Feedback Negative 913
LBI: R 913
Remote AUTO 913
Remote MAN 914
Remote OFF 914
Remote Start/Stop 915
LBI: S 915
Sd Override 915
Soft Bus Energize 916
Soft Unload Enable 916
Start Blocking 916
Start Button 916
Stop Button 917
Sunrise/Sunset Home
Position 917
Synchronization Disabled 917
LBI: T 917
TEST ROCOF 917
Test Vector Shift 917
Top Priority 918
LBI: W 918
WT 01 Operable 918
WT 02 Operable 918
WT 03 Operable 918
WT 04 Operable 919
WT 05 Operable 919
WT 06 Operable 919
WT 07 Operable 919
WT 08 Operable 919

LBI: A
Application MINT

LBI ID 1007
Description
Activation of this binary input switches the controller Application Mode (page 777) to MINT.
IMPORTANT: The Controller Mode (page 777) has to be OFF, otherwise controller application
can not be changed.
Note: This binary input has lower priority than LBI APPLICATION MPTM (PAGE 879).
6 back to Logical binary inputs alphabetically
Application MPTM

LBI ID 1006
Description
Activation of this binary input switches the controller Application Mode (page 777) to MPTM.
IMPORTANT: The Controller Mode (page 777) has to be OFF, otherwise controller application
can not be changed.
Note: This binary input has higher priority than LBI APPLICATION MINT (PAGE 879).
LBI: B
BATT Discharge Enable

LBI ID 1106
Description
This logical input enables discharging process of the battery.
BATT Charge Enable

LBI ID 1105
Description
This logical input enables charging process of the battery.

BCB Button

LBI ID 193
Description
Binary input has the same function as BCB button on an External display (page 79)Internal display.
BCB Disable

LBI ID 62
Description
This function is used to prevent BCB closing and opening.
If the input is active during synchronizing, the controller will continue synchronizing without
issuing the BCB closing command until the input is deactivated or Sync timeout is elapsed.
If the input is active and the BCB button is pressed in MAN mode to close the BCB to dead bus,
the BCB will not be closed until the input is deactivated and the BCB button pressed again.
If the input is active and the BCB should be closed to dead bus automatically, the BCB will not be
closed until the input is deactivated.
If the input is active and the BCB is already closed, the breaker will not open automatically. BCB
can be opened with BCB Button (or the corresponding command).

BCB Feedback

LBI ID 63
Description
Use this input to indicate whether the BESS circuit breaker is opened or closed.
Image 7.7 BCB Feedback 1
This input is used for connection of the normally open feedback contact from the generator circuit
breaker or contactor. If the input is active, the controller will consider the BCB as closed and vice versa.
If the feedback does not respond to a change of the control output LBO BCB CLOSE/OPEN (PAGE
926) within time adjusted in Setpoint Waiting For Breaker Feedback (page 1), and it was
already last attempt the specific alarm based on current breaker position is issued.
If the feedback changes it's position unexpectedly without any command given by the control
output, the Alarm Stp BCB Fail (page 1124) will be issued immediately.

BCB Feedback Negative

LBI ID 64
Description
This input is used for connection of the normally closed feedback contact from the generator circuit
breaker or contactor. This input is optional and if it is configured, it must be always in inverse position to
the normally open input LBI BCB FEEDBACK (PAGE 881). Maximal allowed time the both inputs are in the
same position is 500ms, after this time the Alarm Stp BCB Fail (page 1124) is issued.
Image 7.9 BCB Feedback Negative 1
Image 7.10 BCB Feedback Negative 2

BCB Secondary Feedback Negative

LBI ID 982
Description
This input is logically inverted against LBI BCB SECONDARY FEEDBACK (PAGE 884).
Image 7.11 BCB Feedback Secondary Negative 1
Image 7.12 BCB Feedback Secondary Negative 2

BCB Secondary Feedback

LBI ID 548
Description
BESS Output Control Mode U-f/P-Q

LBI ID 1109
Description
This logical input is used to choose what BESS Output Control (page 239) method will be used. By
default (log 0) the U-f option is used.

BESS Ready To Load

LBI ID 121
Description
Activation of this LBI signalizes that BESS is ready to be loaded. Once this LBI gets active and the BESS
finished the stabilization phase, BESS state (page 778) goes to Running.
If this LBI is configured and it is not activated before BESSReady to Load TO (page 426)
elapsed the alarm Sd Start Fail (page 1123) is activated.
If this LBI is not configured the BCB is closed after BESSReady to Load TO (page 426)
elapsed.
Note: BCB can be closed only when this LBI is active and has to be configured.
Note: There is no BCB control limitation when BCB Control Mode (page 362) = External.
LBI: C
Conditioned Hours Counter 1

LBI ID 1094
Description
This binary input is used as customer condition for the value Conditioned Running Hours 1 (page
772).
Conditioned Hours Counter 2

LBI ID 1095
Description
This binary input is used as customer condition for the value Conditioned Running Hours 2 (page
772).
LBI: E
ECU Key Switch

LBI ID 951
Description
Activation of this binary input activates LBO ECU POWER RELAY (PAGE 943) without starting of the
BESS. This can be used for reading electronic control unit values when BESS does not run.

Emergency MAN

LBI ID 45
Description
This input is designed to allow the BESS and breakers to be controlled externally (not by the controller).
This feature can be useful in case of some failure, which disables the BESS and breakers to be
controlled by the controller, but the BESS itself is operational.
The controller behaves in the following way:
Stops all functions regarding the BESS andbreaker control, deactivates all outputs related to it.
Stop Fail alarm is not being evaluated and stop solenoid is not activated if nonzero speed is
detected.
When the input is deactivated, the controller takes control according to the situation in the
moment of deactivation, i.e. the BESS remains running loaded if it was running and BCB was
closed in the moment the input was deactivated.
Emergency Stop

LBI ID 40
Description
When this binary input is activated, BESS is immediately stopped, binary outputs are disconnected and
alarm Emergency Stop (page 1114) is activated.
LBI: F
Fault Reset Button

LBI ID 191
Description
Binary input has the same function as Fault Reset button on an External display (page 79)Internal
display.
Force Island
Related FW 1.3.0 Related applications MINT,

LBI ID 787
Description
Activation of this LBI starts the BESS and forces island operation. Transfer method of the load from
Mains is adjusted via setpoint Transfer Mains To BESS (page 465).

Force Parallel

LBI ID 786
Description
Activation of this LBI starts the BESS and forces parallel operation if MAINS/BUS HEALTHY (PAGE 959) is
closed. Island operation is not allowed while this LBI is closed.
Forced Value Input 01

LBI ID 19
Description
This LBI is used for activation of preconfigured Forced Value (page 158) to setpoint.
Note: This LBI can be renamed during configuration.

LBI ID 20
Description

LBI ID 21
Description

LBI ID 22
Description


LBI ID 23
Description

LBI ID 24
Description

LBI ID 25
Description

LBI ID 26
Description

LBI ID 27
Description


LBI ID 28
Description

LBI ID 29
Description

LBI ID 30
Description

LBI ID 31
Description

LBI ID 32
Description


LBI ID 33
Description

LBI ID 34
Description

LBI ID 839
Description

LBI ID 840
Description

LBI ID 841
Description


LBI ID 842
Description

LBI ID 843
Description

LBI ID 844
Description

LBI ID 845
Description

LBI ID 846
Description


LBI ID 847
Description

LBI ID 848
Description

LBI ID 849
Description

LBI ID 850
Description

LBI ID 851
Description


LBI ID 852
Description

LBI ID 853
Description

LBI ID 854
Description
LBI: G
Group link

LBI ID 59
Description
This input is used for logical connection and disconnection of two BESS groups selected with setpoints
Group Link L (page 508) and Group Link R (page 508). If the input is active, then the two selected
groups will perform Power Management (page 269), load sharing and Var sharing together as one
large group.
Note: This function is independent on the group which the particular controller belongs to, i.e. the
controller can provide linking function e.g. for groups 3,4 although it belongs to group 2.
Geo Home Position

Comm object 219
Description
This binary input can be used to adjust home position of BESS. In case that binary input is active,
setpoints Home Latitude (page 647) and Home Longitude (page 647) are adjusted automatically from
actual coordinates from GPS signal.
Note: Input has to be activated for at least 2 seconds.
Geo-Fencing Enable

Comm object 218
Description
This binary input enables or disables Fence 1 Protection (page 648) and Fence 2 Protection (page
649) if Geo-Fencing (page 646) is adjusted to value "LBI Enable".
LBI: H
Horn Reset Button

LBI ID 192
Description
Binary input has the same function as Horn reset button on an External display (page 79)Internal
display.

Hot Swap Ctrl Block

LBI ID 1047
Description
This LBI is used to detect if this controller is considered to be dead by the second Hot Swap
Redundancy (page 160) controller.
If the LBI is activated this controller is considered to be dead and it is forced to the listening mode. The
controller in listening mode does not send any messages to other controllers but only reads what is being
transmitted. This LBI has to be physically wired to the LBO HOT SWAP SWITCH (PAGE 952) of the second
Hot Swap Redundancy (page 160) controller.
Note: If both Master and Backup controllers are alive, the Master is in control and the Backup is
automatically in the listening mode. This LBI is used only to force the listening mode on controller
which is considered to be dead by the second controller.
IMPORTANT: This input has to be configured to physical input of the controller.
IMPORTANT: This input has to be configured on both Master and Backup controllers.
Hot Swap Heartbeat Detect

LBI ID 1037
Description
This LBI is used for detection that the second Hot Swap Redundancy (page 160) is alive.
This LBI has to be physically wired to the LBO HOT SWAP HEARTBEAT (PAGE 952) of the second Hot
Swap Redundancy (page 160) controller. If the Heartbeat signal is not received, this controller
activates LBO Hot Swap Switch (page 952).
IMPORTANT: This input has to be configured to physical input of the controller.
IMPORTANT: This input has to be configured on both Master and Backup controllers.
Hot Swap Recovery

LBI ID 1048
Description
This binary input is used to recover the Hot Swap Redundancy (page 160) system in case of Wrn
Master Controller Failed (page 1089) or Wrn Backup Controller Failed (page 1084) alarm is present
in the Alarm list.
Note: If warnings remains after the recovery, the wiring and configuration should be checked.

LBI: I
Inverter Start Disabled

LBI ID 1185
Description
This LBI can be used to keep the BESS in idle operation.
LBI: L
Load Reduction 1

LBI ID 544
Description
This LBI activates Load Reduction (page 298) if setpoint Load Reduction (page 540) = Enabled and
LBI LOAD REDUCTION ENABLE (PAGE 897) is closed. Load/power of the BESS is limited by the setpoint
Load Reduction 1 (page 540).
Note: If more than 1 Load Reduction LBIs are closed, Load Reduction with smallest value in setpoint is
chosen.
Load Reduction 2

LBI ID 545
Description
chosen.

Load Reduction 3

LBI ID 546
Description
chosen.
Load Reduction 4

LBI ID 547
Description
chosen.
Load Reduction Enable

LBI ID 615
Description
This LBI enables Load Reduction (page 298) while it is closed.
Note: Setpoint Load Reduction (page 540) has to be Enabled, otherwise this LBI has no effect.

Load Res 2 Active

LBI ID 49
Description
This input is used to activate the load reserve set #2 (learn more about load reserve in the chapter Power
Management (page 269)) instead of the set #1, which is active by default. The set #2 is adjusted by
setpoints:
#Starting Load Reserve 2 (page 491) and #Stopping Load Reserve 2 (page 492) if the power
management is switched to absolute mode
#Starting Rel Load Reserve 2 (page 493) and #Stopping Rel Load Reserve 2 (page 493) if
the power management is switched to relative mode.
IMPORTANT: All controllers cooperating together in Power management must have the same
load reserve set selected.
Note: It is possible to use virtual peripheries for distribution of the binary signal from one physical switch
connected to one controller to all other controllers over the CAN bus.

Load Res 3 Active

LBI ID 50
Description
setpoints:

Load Res 4 Active

LBI ID 51
Description
setpoints:
LBI: M
Mains Fail Block

LBI ID 622
Description
This logical input simulates healthy Mains even if the Mains parameters are not OK.

Manual Load Reconnection

LBI ID 60
Description
This input is used for manual reconnection of the last disconnected part of the load, if the load has
dropped below the setpoint Load Reconnection Level (page 594). This works only if automatic
reconnection is disabled, i.e. the setpoint Auto Load Reconnection (page 595) = Disabled.
MCB Button

LBI ID 194
Description
This binary input has the same function as MCB button on an External display (page 79)Internal
display.
MCB Disable

LBI ID 124
Description
This binary input is used to prevent MCB closing and opening.
If the input is active during synchronizing, the controller will continue synchronizing without
issuing the MCB closing command until the input is deactivated or Sync timeout is elapsed.
If the input is active and the MCB Button is pressed in MAN mode to close the MCB to dead bus,
the MCB will not be closed until this input is deactivated and the MCB Button is pressed again.
If the input is active and the MCB is to be closed to dead bus automatically, the MCB will not be
closed until this input is deactivated.
If the input is active and MCB is already closed, the breaker will not open.

MCB Feedback

LBI ID 65
Description
Use this input to indicate whether the mains circuit breaker is opened or closed.
Image 7.15 MCB Feedback 1

MCB Feedback Negative

LBI ID 66
Description
Use this input to indicate whether the mains circuit breaker is opened or closed.
This input is logically inverted against LBI MCB FEEDBACK (PAGE 902).

Min Run Power Act 1

LBI ID 52
Description
This input is used to activate the function Minimal running power #1, which is adjusted by setpoint #Min
Run Power (page 500).
Note: The default value of minimal running power, which takes place while none of the inputs Min Run
Power x Act, is 0 kW.
Note: If more then one binary input for Min Run Power is activated, the one with the higher index has
higher priority and it is used.
minimal running power selected.
connected to one controller to all other controllers over the CAN bus. See the diagram of such
distribution in the description of the input LOAD RES 2 ACTIVE (PAGE 898).
Min Run Power Act 2

LBI ID 53
Description
Run Power 2 (page 500).

Min Run Power Act 3

LBI ID 54
Description
Run Power 3 (page 501).
LBI: N
NCB Feedback

LBI ID 67
Description
This input is used for connection of feedback contact from the neutral contactor. If the input is active, the
controller will consider the neutral contactor as closed and vice versa. See also the setpoint #Neutral
Contactor Control (page 355) which is used for selecting of the NCB mode (Each / Common).
LBI: P
Post VRT

LBI ID 955
Description
Activation of this LBI activates Post VRT (page 301) if at least one of BESS Current L1 (page 672),
BESS Current L2 (page 672) or BESS Current L3 (page 672) is over Nominal Current (page 369).
Note: This is the only way to activate Post VRT function in MINT application, signal shall be sent from
the IM controller.

Precharge Finished

LBI ID 1171
Description
This signal is to be used as a confirmation, that the DC circuit inside the BESS is closed (the battery is
connected to the DC circuit of the inverter).
It is actually the feedback of the DC relay situated between the battery and the inverter. State of this relay
can be monitored using the LBO DC Circuit closed which just simply mirror the information about the DC
circuit state.
This LBI relates to the BESS start sequence decribed in BESS Precharge Types (page 240).

LBI ID 16
Description
Activation of this LBI disables selected protections.
Proper history record is written to the history log.
Protection Force Disable 1 active
Protection Force Disable 1 inactive


LBI ID 17
Description

LBI ID 18
Description

Pulse Counter 1

LBI ID 87
Description
This is the input of the "slow" Pulse Counters (page 211) function which is connected with LBI PULSE
COUNTER 1 (PAGE 908).
Pulse Counter 2

LBI ID 88
Description
This is the input of the "slow" Pulse Counters (page 211) function which is connected with LBI PULSE
COUNTER 2 (PAGE 908).
PV 01 Operable

LBI ID 1103
Description
This logical input is used to detect whether the PV inverter is operable or not. If it is not activated the
PVCB cannot be closed.
PV 02 Operable

LBI ID 1121
Description
PV 03 Operable

LBI ID 1122
Description

PV 04 Operable

LBI ID 1123
Description
PV 05 Operable

LBI ID 1124
Description
PV 06 Operable

LBI ID 1125
Description
PV 07 Operable

LBI ID 1126
Description
PV 08 Operable

LBI ID 1127
Description

PV 09 Operable

LBI ID 1128
Description
PV 10 Operable

LBI ID 1129
Description
PV 11 Operable

LBI ID 1130
Description
PV 12 Operable

LBI ID 1131
Description
PV 13 Operable

LBI ID 1132
Description

PV 14 Operable

LBI ID 1133
Description
PV 15 Operable

LBI ID 1134
Description
PV 16 Operable

LBI ID 1134
Description
PVCB Button

LBI ID 1114
Description
Binary input has the same function as PVCB button.

PVCB Disable

LBI ID 1104
Description
This function is used to prevent PVCB closing and opening.
If the input is active during synchronizing, the controller will continue synchronizing without issuing
the PVCB closing command until the input is deactivated or Sync timeout is elapsed.
If the input is active and the PVCB button is pressed in MAN mode to close the PVCB to dead bus,
the PVCB will not be closed until the input is deactivated and the PVCB button pressed again.
If the input is active and the PVCB should be closed to dead bus automatically, the PVCB will not
be closed until the input is deactivated.
If the input is active and the PVCB is already closed, the breaker will not open.
PVCB Feedback

LBI ID 1101
Description
Use this input to indicate whether the PV circuit breaker is opened or closed.
Image 7.19 PVCB Feedback 1
Image 7.20 PVCB Feedback 2

PVCB Feedback Negative

LBI ID 1102
Description
Use this input to indicate whether the PV circuit breaker is opened or closed.
This input is logically inverted against LBI PVCB FEEDBACK (PAGE 912).
Image 7.21 PVCB Feedback Negative 1
Image 7.22 PVCB Feedback Negative 2
LBI: R
Remote AUTO

LBI ID 620
Description
The controller is switched to the AUTO mode when this binary input is closed. When opens controller is
switched back to previous mode.
This binary input has the lowest priority from Remote OFF / MAN / AUTO binary inputs
Remote control priority:
Remote OFF (Highest priority)
Remote MAN
Remote AUTO (Lowest Priority)

Remote MAN

LBI ID 618
Description
The controller is switched to the MAN mode when this binary input is closed. When opens controller is
Remote MAN
Remote OFF

LBI ID 617
Description
The controller is switched to the OFF mode when this binary input is closed. When opens controller is
Remote MAN

Remote Start/Stop

LBI ID 38
Description
Use this input to start and stop theBESS in AUTO mode. This information is shared to all controllers in
the same group connected to the master controller via CAN.
Taken action in MPTM application (AUTO Mode)

Start BESS, synchronization, parallel operation (baseload/Imp/Exp),
Regardless the Mains parameters OK.
Active
Start the BESS to Island if Mains Not OK
Reverse synchronization when Mains gets restored
Inactive Unloading of the BESS if it is running in parallel, stop the BESS.
Taken action in MINT application (AUTO Mode)
Starts the BESS after #System Start Delay (page 485) if Power
Active
Management (page 480) = Enabled, otherwise it is started immediately.
Stops the BESS after #System Start Delay (page 485) if Power
Inactive
Management (page 480) = Enabled, otherwise it is stopped immediately.
Note: In the MPTM application there are more LBIs that can influence the state of the application and
can be in the collision with the Common LBI Remote Start/Stop.
LBI: S
Sd Override

LBI ID 44
Description
If this input is active, all alarms except Emergency Stop (page 1114)and E-STOP (page 1114) are
suppressed. The suppressed alarms will be displayed in the alarm list, but they will not take effect
regarding the BESS control.
Note: Wrn Override All Sd (page 1091) is indicated in the alarm list if Sd Override mode is active to
inform the operator that the BESS is not protected.
Note: User protections (page 205) with protection type Shutdown Override (page 199) are also NOT
suppressed.
IMPORTANT: MISUSE OF THIS INPUT CAN CAUSE DAMAGE TO THE BESS!

Soft Bus Energize

LBI ID 1192
Description
This logical input should be used to soft energize the dead bus (load, transformer) while the DC
precharge is used. During the start sequence when precharge is finished the BCB is firstly closed to the
dead bus and then the LBO INVERTER RUN REQUEST (PAGE 953) is activated. If the inverter supports the
voltage ramp up, the bus should be energized with limited inrush current.
Soft Unload Enable

LBI ID 1049
Description
In case the communication with other controllers is lost, the soft unload is being proceeded only if this
logical binary input is active. If this input is not active the BCB is opened immediately after the stop
request is detected or the BCB button is pressed.
Note: This function is used when there is any non-detected unit which is able to take over the load of the
BESS which is being unloaded.
Start Blocking

LBI ID 68
Description
Start of the BESS is blocked if this binary input gets active before Start command is issued. While start is
blocked, alarm ALI Start Blocking (page 1110) is active.
Note: Activation of this LBI while BESS is already running (or is about to be started) has no effect.
Start Button

LBI ID 189
Description
Binary input has the same function as Start Button on an External display (page 79)Internal display.

Stop Button

LBI ID 190
Description
Binary input has the same function as Stop Button on an External display (page 79)Internal display.
Sunrise/Sunset Home Position

LBI ID 1120
Description
Rising edge on this input make the setpoint Sunrise/sunset Latitude and Sunrise/Sunset Longitude
synchronized with the current position received from the GPS plug-in module (only if valid and available).
Synchronization Disabled

LBI ID 277
Description
This binary input is used to disable the forward and reverse synchronization process so the controller
won't attempt to close breaker(s) if synchronization would be needed.This LBI is useful if user want to set
the additional condition for start of the synchronization.
LBI: T
TEST ROCOF
Related FW 1.3.0 Related applications MINT

LBI ID 1116
Description
A rising edge on this LBI triggers the same event in the controller as the actual ROCOF 1 protection trip.
Test Vector Shift

LBI ID 1117
Description
A rising edge on this LBI triggers the same event in the controller as the actual Vector Shift protection trip.

Top Priority

LBI ID 199
Description
If this input is active, the controller will have the highest priority in the group independent of the setpoint
Priority (page 483).
IMPORTANT: This binary input can be used only if setpoint #Priority Auto Swap (page 484) =
Disabled.
LBI: W
WT 01 Operable

LBI ID 1136
Description
This logical input is used to detect whether the WT inverter is operable or not. If it is not activated the
WT 02 Operable

LBI ID 1137
Description
WT 03 Operable

LBI ID 1138
Description

WT 04 Operable

LBI ID 1139
Description
WT 05 Operable

LBI ID 1140
Description
WT 06 Operable

LBI ID 1141
Description
WT 07 Operable

LBI ID 1142
Description
WT 08 Operable

LBI ID 1143
Description

9.1.7 Logical binary outputs
What Logical binary outputs are:
Logical binary outputs are outputs for binary values and functions.
Alphabetical groups of Logical binary outputs

LBO: A 923
LBO: B 926
LBO: C 936
LBO: D 939
LBO: E 940
LBO: F 949
LBO: G 950
LBO: H 951
LBO: I 953
LBO: K 953
LBO: L 954
LBO: M 959
LBO: N 963
LBO: O 964
LBO: P 965
LBO: R 974
LBO: S 975
LBO: U 978
LBO: V 978
LBO: W 979
For full list of Logical binary outputs go to the chapter Logical binary outputs alphabetically (page 921).

Logical binary outputs alphabetically
LBO: A 923 BESS Ready To Load 936 ECU 14 Comm Fail 942
Access Locked 923 LBO: C 936 ECU 15 Comm Fail 942
AL Maintenance 1 923 Common Alarm Active ECU 16 Comm Fail 943
AL Maintenance 2 923 Level 1 936 ECU Comm OK 943
AL Maintenance 3 923 Common Alarm Active ECU Power Relay 943
Level 2 936
AL Maintenance 4 923 ECU Run Stop 943
Common Alarm Level 1 937
Alarm 924 Energized 944
Common Alarm Level 2 937
Alarm BESS Frequency 924 Engines Swapped 944
Common Alarm Only 937
Alarm BESS Overcurrent 924 Event Load Reduction 944
Common History Record 937
Alarm BESS Voltage 924 Event Mains Frequency
Common Mains Protection 937 Fall 944
Alarm Flashing 924
Common PVCB Open 938 Event Mains Frequency
Alarm BESS 925
Common Shutdown 938 Rise 944
Alarm BESS Frequency 925
Common Shutdown Event Mains Trip 945
Alarm BESS Voltage 925
Override 938 Event P for Q 945
All Available Gen-sets Run 925
Common Slow Stop 938 Event P(Um) 945
Any GCB Closed 926
Common Warning 939 Event Post VRT 945
Any Other GCB Closed 926
Curtailment Enable 939 Event Return Over/Under
LBO: B 926
LBO: D 939 Frequency 945
BCB Button Echo 926
Daily Batt Cycles Reached 939 Event Soft Unload 946
BCB Close/Open 926
DC Circuit Closed 939 Exercise Timer 1 946
BCB Close/Open
Deadbus 939 Exercise Timer 2 946
Secondary 927
Day/Night 940 Exercise Timer 3 946
BCB OFF Coil 928
LBO: E 940 Exercise Timer 4 947
BCB OFF Coil Secondary 929
ECU Comm Fail 940 Exercise Timer 5 947
BCB ON Coil 930
ECU 1 Comm Fail 940 Exercise Timer 6 947
BCB ON Coil Secondary 931
BCB Status 931
BCB Primary Status 932
BCB Secondary Status 932
BCB UV Coil 932
BCB UV Coil Secondary 934
BESS Active 934
ECU 8 Comm Fail 941
BESS Capability C Limit 935 LBO: F 949
ECU 9 Comm Fail 941 FltRes Button Echo 949
BESS Capability L Limit 935
ECU 10 Comm Fail 942 Forward Synchronization 949
BESS Healthy 935
ECU 11 Comm Fail 942 Frequency Down 950
BESS In Loadsharing 935
ECU 12 Comm Fail 942 Frequency Up 950
BESS Parallel Oper 936
ECU 13 Comm Fail 942

LBO: G 950 Manual Ready 959 PV Operable 968
GPS Coordinates MCB Button Echo 959 PV/WT Run Request 969
Detected 950 MCB Close/Open 959 PVCB Button Echo 969
GridCodes Power MCB OFF Coil 960 PVCB Close/Open 969
Limitation 950
MCB ON Coil 961 PVCB OFF Coil 970
LBO: H 951
MCB Status 961 PVCB ON Coil 971
Heartbeat 951
MCB UV Coil 962 PVCB Status 972
Horn 951
Mode AUTO 962 PVCB UV Coil 973
Horn Flashing 951
Mode MAN 962 LBO: R 974
HornRes Button Echo 951
Mode OFF 963 Ready 974
Hot Swap Heartbeat 952
LBO: N 963 Reverse Synchronization 974
Hot Swap Switch 952
NCB Close/Open 963 ROCOF 1 Active 974
HW AC Voltage
Not In Auto 963 ROCOF 2 Active 974
Measurement Error 952
Not Ready 963 ROCOF 3 Active 974
LBO: I 953
Not Used 963 ROCOF 4 Active 975
In Synchronism 953
LBO: O 964 LBO: S 975
Initialized 953
Operational 964 Sd Override 975
Inverter Run Request 953
OVRT Active 964 SOC Discharge Disabled 975
LBO: K 953
OVRT Invalid 964 SOC Charge Disabled 975
kWh Pulse 953
OVRTCurveTrip 964 Soft Load 975
LBO: L 954
Load Reduction Active 954 LBO: P 965 Soft Unload 976
P for Q Active 965 Start Blocked 976
Load Shedding Stage 1 954
P Over Frequency Active 965 Start Button Echo 976
P Over Frequency Curve Starting 976
Invalid 965 Stop Button Echo 976
P Under Frequency Active 965 Stopping 977
P Under Frequency Curve Sync To Mains Allowed 977
Invalid 965
Load Shedding Stage 8 956 System Ready 977
Pave 966
Loaded 957 System Reserve OK 977
Pave FLS 966
Logical 0 957 LBO: U 978
Peak Shaving Active 966
UQ-C Area Limit 978
Logical 1 957
Peripheral Module Comm
UQ-L Area Limit 978
LVRT 1-phase Invalid 957 Fail 966
LBO: V 978
LVRT 2-phase Invalid 957 Power Switch 967
Vector Shift Active 978
LVRT 3-phase Invalid 958 PQ-C Area Limit 967
Voltage Down 978
LVRT Active 958 PQ-L Area Limit 967
Voltage Up 979
LVRT Severe 958 Prestart 967
LBO: W 979
LVRTCurveTrip 958 Precharge 968
WT Operable 979
LBO: M 959 Precharge Request 968
Mains/Bus Healthy 959 Process Power Limitation 968

LBO: A
Access Locked

LBO ID 2480
Description
This output is closed when the function Access lock (page 121) is activated and it can be used to block
any LBIs which are required to be locked.
6 back to Logical binary outputs alphabetically
AL Maintenance 1

LBO ID 2211
Description
This output is active when alarm Maintenance 1 RunHours (page 1156) or Maintenance 1 Interval
(page 1156) is present in the alarm list.
AL Maintenance 2

LBO ID 2212
Description
AL Maintenance 3

LBO ID 2213
Description
AL Maintenance 4

LBO ID 2650
Description

Alarm

LBO ID 2
Description
The output is designed to be used as external alarm indication such as a red bulb in the control room etc.
The output is active when at least one unconfirmed alarm is present in the alarmlist and remains active
until confirmation of alarm.
Alarm BESS Frequency

LBO ID 1266
Description
This output is active when at least 1 protection caused by BESS >f Protection (page 575) or BESS <f
Protection (page 576) is active.
Alarm BESS Overcurrent

LBO ID 109
Description
This output is active while at least one of the following overcurrent protection is active Short Circuit
Protection (page 562) or IDMT BESS >A Protection (page 562).
Alarm BESS Voltage

LBO ID 1263
Description
This output is active when at least 1 alarm caused by BESS >>V Protection (page 566), BESS >V
(page 565) or BESS <V Protection (page 567) is present in the alarmlist.
Alarm Flashing

LBO ID 28
Description
This is the flashing alternative of the output ALARM (PAGE 924), i.e. the output flashes with 1 Hz period
while the output Alarm is closed.

Alarm BESS

LBO ID 197
Description
This output is active when at least 1 protection caused by Mains >>V Protection (page 570), Mains >V
Protection (page 568) or Mains <V Protection (page 572), Mains <V Protection (page 573), Mains
>>f Protection (page 578), Mains >f Protection (page 577), Mains <f Protection (page 579), Mains
<<f Protection (page 580) is active.
Alarm BESS Frequency

LBO ID 1271
Description
This output is closed when at least 1 protection caused by Mains >>f Protection (page 578) Mains >f
Protection (page 577), Mains <f Protection (page 579) or Mains <<f Protection (page 580) is active.
Alarm BESS Voltage

LBO ID 1270
Description
This output is closed when at least 1 protection caused by Mains >>V Protection (page 570) Mains >V
Protection (page 568), Mains <V Protection (page 572) or Mains <V Protection (page 573) is
active.
All Available Gen-sets Run

LBO ID 122
Description
This output is closed when all available BESSs within the Control Group (page 507) are loaded.
Note: BESS is available if Power Management (page 480) = Enabled, Controller Mode (page 777) =
AUTO and there is not present Alarms level 2 (page 1112) in the alarmlist.

Any GCB Closed

LBO ID 222
Description
This output is active when a GCB of any controller connected via ⑧ CAN2A (page 47) and/or ⑦ CAN2B
(page 47) is closed.
Note: This function works on CAN16 (page 785) - CAN64 (page 786) values, therefore it ignores
Any Other GCB Closed

LBO ID 1827
Description
This output is active when a GCB of any other controller connected via ⑧ CAN2A (page 47) and/or
⑦ CAN2B (page 47) is closed.
Note: This function works on CAN16 (page 785) - CAN64 (page 786) values, therefore it ignores
LBO: B
BCB Button Echo

LBO ID 35
Description
This output is closed for 1s every time BCB Button is pressed.
That means:
BCB button is pressed on the controller front panel or
BCB button is pressed on any of external local/remote terminals or
BCB close/open command is received via communication line
BCB Close/Open

LBO ID 41
Description
The output controls the primary BESS circuit breaker. Its state represents the breaker position
requested by the controller.
If the feedback does not respond to a change within 2 seconds to a close or open command and it was
already the last attempt, an specific alarm based on the current breaker position is issued.

Image 7.23 BCB Close command
BCB Close/Open Secondary

LBO ID 1058
Description
The output controls the secondary BESS circuit breaker. Its state represents the breaker position
requested by the controller.
If the feedback does not respond to a change within time adjusted in 2 seconds to a close or open
command and it was already the last attempt, an specific alarm based on the current breaker position is
issued.
Image 7.24 BCB Close command

BCB OFF Coil

LBO ID 43
Description
The output is intended for opening of primary BESS circuit breaker.
The output gives a pulse in the moment the breaker has to be opened. The pulse lasts until the feedback
deactivates, but at least for 2 seconds, when circuit breaker has to open with pause 1 second between
each pulse. If the LBI BCB FEEDBACK (PAGE 881) does not match after second pulse elapses, Alarm Stp
BCB Fail To Open (page 1125) Wrn MCB Fail To Open (page 1091) is issued.
Image 7.25 BCB OFF Coil command

BCB OFF Coil Secondary

LBO ID 1068
Description
The output is intended for opening of secondary BESS circuit breaker.
The output gives a pulse in the moment the breaker has to be opened. The pulse lasts until the feedback
deactivates, but at least for 2 seconds, when circuit breaker has to open with pause 1 second between
each pulse. If the LBI BCB SECONDARY FEEDBACK NEGATIVE (PAGE 883) does not match after second
pulse elapses, Alarm Stp BCB Secondary Fail To Open (page 1128) is issued.
Image 7.26 BCB OFF Coil command

BCB ON Coil

LBO ID 42
Description
The output is intended for control of close coil of primary BESS circuit breaker.
The output gives at least 2 second pulse in the moment the breaker has to be closed. The pause
between attempts is 3 seconds.
When the last attempt elapses and LBI BCB FEEDBACK (PAGE 881) does not match Alarm Stp BCB Fail
To Close (page 1125) is issued.
Image 7.27 BCB ON Coil close command

BCB ON Coil Secondary

LBO ID 1067
Description
The output is intended for control of close coil of secondary BESS circuit breaker.
The output gives at least 2 second pulse in the moment the breaker has to be closed. The pause
between attempts is 3 seconds
Image 7.28 BCB ON Coil close command
BCB Status

LBO ID 84
Description
This output indicates the BCB position as it is internally considered by the controller.
The position is based on BCB FEEDBACK (PAGE 881) and BCB FEEDBACK NEGATIVE (PAGE 882).
In case that only positive feedback is used, this output mirrors the feedback.
In case that both feedbacks are used and
Feedbacks match each other - the output indicates BCB position according to feedbacks.
Feedbacks do not match each other - output indicates last position when feedbacks matched.

BCB Primary Status

LBO ID 2541
Description
This output indicates the Primary BCB position as it is internally considered by the controller.
The position is based on BCB FEEDBACK (PAGE 881) and BCB FEEDBACK NEGATIVE (PAGE 882).
In case that only BCB FEEDBACK (PAGE 881) is used, this output mirrors the input.
In case that both BCB FEEDBACK (PAGE 881) and BCB FEEDBACK NEGATIVE (PAGE 882) are used
and
Feedbacks match - output indicates BCB position according to feedbacks.
Feedbacks do not match - output indicates last position when feedbacks matched.
BCB Secondary Status

LBO ID 2542
Description
This output indicates the Secondary BCB position as it is internally considered by the controller.
The position is based on BCB SECONDARY FEEDBACK (PAGE 884) and BCB SECONDARY FEEDBACK
NEGATIVE (PAGE 883).
In case that only BCB SECONDARY FEEDBACK (PAGE 884) is used, this output mirrors the input.
In case that both BCB SECONDARY FEEDBACK (PAGE 884) and BCB SECONDARY FEEDBACK
NEGATIVE (PAGE 883) are used and
Feedbacks match - output indicates BCB position according to feedbacks.
BCB UV Coil

LBO ID 44
Description
The output is intended for control of undervoltage coil of primary BESS circuit breaker.
The output is closed after the BESShas been started, min stab time has elapsed and the BESS voltage
and frequency have got into limits.BCB closing command is blocked for 1 sec after the UV coil has been
closed to allow the breaker's mechanical system to get ready for closing. The output is opened for 2
seconds when the BCB has to open.
The output is closed again and remains closed while the BESS voltage and frequency are within limits if
the Running phase follows after the opening of the BCB (e.g. in MAN). The output remains open if the
Cooling phase follows after the opening of the BCB.

Image 7.29 BCB UV Coil close command

BCB UV Coil Secondary

LBO ID 1069
Description
The output is intended for control of undervoltage coil of secondary BESS circuit breaker.
The output is closed after the BESShas been started, min stab time has elapsed and the BESS voltage
and frequency have got into limits.BCB closing command is blocked for 1 sec after the UV coil has been
closed to allow the breaker's mechanical system to get ready for closing. The output is opened for 2
seconds when the BCB has to open.
Image 7.30 BCB UV Coil close command
BESS Active

LBO ID 60
Description
This output is closed at the beginning of the Prestart Time (page 1) period and opens when BESS is
stopped.

BESS Capability C Limit

LBO ID 1427
Description
This output is closed when the BESS Required PF (page 757) (while BESS Required PF Character
(page 757) = C) or BESS Required Q (page 757) is out of capacitive limits in which is the BESS allowed
to run.
Limits are given by adjusting the CAPABILITY C (PAGE 865).
BESS Capability L Limit

LBO ID 1428
Description
This output is closed when the BESS Required PF (page 757) (while BESS Required PF Character
(page 757) = L) or BESS Required Q (page 757) is out of inductive limits in which is the BESS allowed
to run.
Limits are given by adjusting the CAPABILITY L (PAGE 864).
BESS Healthy

LBO ID 77
Description
This output is closed while BESS is running and its parameters (voltage & frequency) are considered as
healthy, i.e. within limits.
BESS In Loadsharing

LBO ID 2699
Description
This output is active always when the BESS is forced to join the Load Sharing due to Forced power
condition (page 237).

BESS Parallel Oper

LBO ID 459
Description
This output is active always when the BESS is running in parallel operation with any Gen-set, Mains, or
PV (renewable source of energy).
BESS Ready To Load

LBO ID 58
Description
The output is closed when the BESS is ready to be loaded (conditions below are fulfilled).
In case of DC precharge is used and there are not any external conditions the BCB breaker can be
closed.
In case of AC precharge is used the BCB breaker cannot be closed until healthy bus is detected.
BESS is running
LBI BESS READY TO LOAD (PAGE 885) is closed or BESSReady to Load TO (page 426)
elapsed if the LBI is not configured
Minimal Stabilization Time (page 432) elapsed (DC precharge only)
Stabilization phase finished (DC precharge only)
BESS's Voltage & Frequency (DC precharge only)
Must be within limits if BCB is opened
Can be out of limits for the time specified by a protection delay if BCB is closed
LBO: C
Common Alarm Active Level 1

LBO ID 13
Description
This output is closed when there is at least one Alarms level 1 (page 1080) in the alarmlist.
Common Alarm Active Level 2

LBO ID 15
Description
This output is closed when there is at least one Alarms level 2 (page 1112) in the alarmlist.

Common Alarm Level 1

LBO ID 14
Description
This output is closed when there is at least one unconfirmed Alarms level 1 (page 1080) in the
alarmlist.
Common Alarm Level 2

LBO ID 16
Description
This output is closed when there is at least one unconfirmed Alarms level 2 (page 1112) in the
alarmlist.
Common Alarm Only

LBO ID 11
Description
This output is closed when there is at least one alarm of type Alarm Only (page 1104) present in the
alarmlist.
Common History Record

LBO ID 12
Description
This output is closed for 1 second every time alarm of type History Record Only (page 1111) occurs.
Note: When any History Record alarm is activated the history record is logged into history.
Common Mains Protection

LBO ID 10
Description
This output is closed when there is at least one active alarm of type Mains Protection (page 199).
Note: When any Mains Protection alarm is activated the Mains fail is signalized and AMF Function
(page 125) is started if it is enabled.

Common PVCB Open

LBO ID 187
Description
This output is closed when there is at least one alarm of type PV Breaker Open (page 1131) present in
the alarmlist.
Common Shutdown

LBO ID 4
Description
This output is closed when there is at least one active alarm of type Shutdown (page 1114) present in
the alarmlist.
Note: When any Shutdown alarm is activated the BCB opens and BESS stops immediately.
Common Shutdown Override

LBO ID 251
Description
This output is closed 2 seconds after there is at least one alarm of type Shutdown Override (page 199)
present in the alarmlist.
Note: When any Sd Override alarm is activated the BCB opens and BESS stops immediately. This
protection type can not be blocked (overridden) by active LBI (function) SD OVERRIDE (PAGE 915).
Common Slow Stop

LBO ID 5
Description
This output is closed when there is at least one alarm of type Slow Stop (page 1124) present in the
alarmlist.
Note: When any Stp alarm is activated and there is another BESS that is currently not running
loaded and it is Ready for Power management the controller will wait for #Slow Stop Delay (page
502) and than starts unloading if it is possible. If there is no other BESS in such state the controller
starts unloading immediately without the delay.

Common Warning

LBO ID 3
Description
This output is closed when there is at least one alarm of type Warning (page 1083) present in the
alarmlist.
Curtailment Enable

LBO ID 2691
Description
This output is active when the function curtailment is used to regulate power of the PV.
LBO: D
Daily Batt Cycles Reached

LBO ID 2704
Description
This output is active always when the number of daily battery cycles is reached.
DC Circuit Closed

LBO ID 2784
Description
This LBO is a miror of the LBI PRECHARGE FINISHED (PAGE 906). It is active all the time when DC circuit of
the BESS is closed.
Deadbus

LBO ID 2675
Description
This output is active when the Bus is considered to be dead (Bus voltage is below relative value set by
the setpoint Bus Dead Level (page 376)).

Day/Night

LBO ID 5931
Description
This LBO is active during the day.(If the current time is between Sunrise Time and Sunset Time)
LBO: E
ECU Comm Fail

LBO ID 114
Description
This output is closed when there is no communication with at least one configured ECU.
ECU 1 Comm Fail

LBO ID 1998
Description
This output is closed when there is no communication with ECU configured in ECU slot 1.
ECU 2 Comm Fail

LBO ID 1999
Description
ECU 3 Comm Fail

LBO ID 2000
Description

ECU 4 Comm Fail

LBO ID 2001
Description
ECU 5 Comm Fail

LBO ID 2002
Description
ECU 6 Comm Fail

LBO ID 2003
Description
ECU 7 Comm Fail

LBO ID 2004
Description
ECU 8 Comm Fail

LBO ID 2005
Description
ECU 9 Comm Fail

LBO ID 2006
Description

ECU 10 Comm Fail

LBO ID 2007
Description
ECU 11 Comm Fail

LBO ID 2008
Description
ECU 12 Comm Fail

LBO ID 2009
Description
ECU 13 Comm Fail

LBO ID 2010
Description
ECU 14 Comm Fail

LBO ID 2011
Description
ECU 15 Comm Fail

LBO ID 2012
Description

ECU 16 Comm Fail

LBO ID 2013
Description
ECU Comm OK

LBO ID 347
Description
This output is closed when all configured ECUs are communicating without any issue.
ECU Power Relay

LBO ID 116
Description
This output should be used for control of “keyswitch” input of an ECU. If the particular ECU does not have
keyswitch or a similar input, it can be used for control of DC power for the ECU.
The output closes together with PRESTART (PAGE 967) and remains closed for the entire duration that the
BESS is running. It is opened at the moment that the BESS is stopped.
IMPORTANT: This LBO also affects evaluation of ECU Communication Fail alarms. With
configured LBO ECU Power Relay, these alarms are evaluated only when this LBO is active.
Without configured LBO ECU Power Relay, these alarm are evaluated all the time.
Note: This output can be also activated by LBI ECU KEY SWITCH (PAGE 885). In that case alarms related
to ECU Communication Fail alarms are not evaluated.
ECU Run Stop

LBO ID 958
Description
Signal for starting and stopping of ECU.

Energized

LBO ID 67
Description
The output is designed to be used as an indication that the BESS is running. The out remains closed until
BESS stop.
Engines Swapped

LBO ID 208
Description
When the master controller (controller with the lowest Controller Address) swaps priority of two
Controllers, the master controller generates 100 ms pulse with the output. The output works with the
setpoint #Priority Auto Swap (page 484) if it is setup to Run Hours Equal.
Event Load Reduction

LBO ID 1434
Description
This output is closed when Load Reduction Ramp (page 543) is in use.
Event Mains Frequency Fall

LBO ID 1433
Description
This output is closed when Mains Frequency Fall Ramp (page 539) is in use.
See Power increase by under frequency - PuF (page 295) for more information.
Event Mains Frequency Rise

LBO ID 1432
Description
This output is closed when Mains Frequency Rise Ramp (page 538) is in use.
See Power reduction by over frequency - PoF (page 294) for more information.

Event Mains Trip

LBO ID 1435
Description
This output is closed when the Grid Code function After Mains Trip Period is in an active state.
It is closed once the timer After MP Synchronization Period (page 532) is elapsed until the timer After
Mains Trip Period (page 533) is elapsed. Once the BESS starts to being unloaded and this output is
closed the Mains will be loaded slowly according to the After Mains Trip Period Ramp (page 534).
Event P for Q

LBO ID 1436
Description
This output is closed when P For Q Ramp (page 548) is in use.
See P For Q (page 301) for more information.
Event P(Um)

LBO ID 1786
Description
This output is closed when BESS P (page 664) and BESS Required P Target (page 753) are limited
due to Power Regulation Based On Actual Mains Voltage (page 297).
Event Post VRT

LBO ID 1438
Description
This output is closed when Post VRT Ramp (page 554) is in use.
See Dynamic Support - VRT (page 299) for more information.
Event Return Over/Under Frequency

LBO ID 1785
Description
This output is closed when Return From Over/Under Frequency Ramp (page 537) is in use.
See Return from over/under frequency (page 296) for more information.

Event Soft Unload

LBO ID 1437
Description
This output is closed when Soft Unload Ramp (page 559) is in use.
Exercise Timer 1

LBO ID 1250
Description
This output is closed when the Exercise timer 1 is activated. The output can be used to make periodic
tests of the BESS, breakers, any external logic etc. and its activation depends on the setpoints in the
Subgroup: Timer 1 (page 617) subgroup.
Note: If more than one timer is active at the same time, timer with selected higher priority function is
applied.
Exercise Timer 2

LBO ID 1251
Description
applied.
Exercise Timer 3

LBO ID 1946
Description
applied.

Exercise Timer 4

LBO ID 1947
Description
applied.
Exercise Timer 5

LBO ID 1948
Description
Exercise Timer 6

LBO ID 1949
Description
applied.
Exercise Timer 7

LBO ID 1950
Description
applied.

Exercise Timer 8

LBO ID 1951
Description
applied.
Exercise Timer 9

LBO ID 2630
Description
applied.
Exercise Timer 10

LBO ID 2631
Description
applied.

Exercise Timer 11

LBO ID 2632
Description
applied.
Exercise Timer 12

LBO ID 2633
Description
applied.
LBO: F
FltRes Button Echo

LBO ID 30
Description
This output provides 1 s pulse when:
Fault Reset button is pressed on an External display (page 79)Internal display.

Fault Reset command is received via communication line
LBI FAULT RESET BUTTON (PAGE 886) is activated.
Forward Synchronization

LBO ID 68
Description
This output is closed when forward synchronization is active (synchronization via BCB breaker) and
opens when LBO BCB STATUS (PAGE 931) closes.

Frequency Down

LBO ID 57
Description
This output together with the complementary output FREQUENCY UP (PAGE 950) are designed for
frequency and power control of the BESS where the BESS inverter regulator does not support analogue
control.
Frequency Up

LBO ID 56
Description
This output together with the complementary output FREQUENCY DOWN (PAGE 950) are designed for
frequency and power control of the BESS where the BESS inverter regulator does not support analogue
control.
LBO: G
GPS Coordinates Detected

LBO ID 5930
Description
This LBO is active if the GPS coordinates obtained from the GPS module are valid..
GridCodes Power Limitation

LBO ID 2365
Description
This output is closed when power is reduced due to Grid Codes requirements:
Power reduction by over frequency - PoF (page 294)
Load Reduction (page 298)
P For Q (page 301)
Dynamic Support - VRT (page 299)

LBO: H
Heartbeat

LBO ID 81
Description
This output toggles on/off in a period of 500 ms whenever the controller is switched on and functional.
Horn

LBO ID 1
Description
This output is closed when any Alarms (page 1080) is activated and stays closed until:
Fault reset is pressed
Horn reset is pressed

Horn Timeout (page 379) elapses
Horn Flashing

LBO ID 29
Description
This is the flashing alternative of the output HORN (PAGE 951), i.e. the output flashes with 1 Hz period
while the output Horn is closed.
HornRes Button Echo

LBO ID 31
Description
This output is closed for 1 s every time Horn Reset Button is pressed.

Hot Swap Heartbeat

LBO ID 2447
Description
This output is used to inform the second Hot Swap Redundancy (page 160) controller about the fact
that this controller is alive.
This LBO has to be physically wired to the LBI HOT SWAP HEARTBEAT DETECT (PAGE 895) of the second
Hot Swap Redundancy (page 160) controller. If the signal is not sent, the second controller activates
LBO HOT SWAP SWITCH (PAGE 952).
IMPORTANT: This output has to be configured to physical output of the controller.
IMPORTANT: This output has to be configured on both Master and Backup controllers.
Hot Swap Switch

LBO ID 2469
Description
This output is activated when the LBI HOT SWAP HEARTBEAT DETECT (PAGE 895) of this controller do not
receive the LBO HOT SWAP HEARTBEAT (PAGE 952) signal from the second Hot Swap Redundancy
(page 160) controller.
This output is used as control signal for switches / switch disconnectors that are used to disconnect
specific terminals of the second Hot Swap Redundancy (page 160) controller. It is also used as
physical input for LBI HOT SWAP CTRL BLOCK (PAGE 895) of the second controller.
IMPORTANT: This output has to be configured to physicall output of the controller.
IMPORTANT: This output has to be configured on both Master and Backup controllers.
HW AC Voltage Measurement Error

LBO ID 2560
Description
This logical binary output is activated once the wrong 3V3 reference voltage is detected.
It is recommended to use it to activate user protection which will open MCB/BCB and turn off the BESS to
prevent any damage to the BESS, load or mains.
IMPORTANT: This LBO only works on HW revision D and higher.

LBO: I
In Synchronism

LBO ID 80
Description
This output is closed during synchronization when Slip Angle, Slip Frequency and Voltages are inside
required windows.
Required windows are:
Slip Angle (page 674) between BESS and Bus Voltage is within range given by Phase Window
(page 478) for time longer than Dwell Time (page 478). Required if Synchronization Type
(page 476) = PhaseMatch.
Slip Frequency (page 674) between between BESS and Bus Frequency is withing range given
by Slip Frequency Window (page 479) for time longer than Dwell Time (page 478). Required if
Synchronization Type (page 476) = SlipSynchr.
Voltage difference between BESS and Bus voltage in all phases must be lower or equal to
Voltage Window (page 477) for time longer than Dwell Time (page 478). Required always.
Initialized

LBO ID 1222
Description
This output is activated after the controller is initialized. It can be used to block some PLC logic blocks
while controller initialization is being proceeded.
Inverter Run Request

LBO ID 2268
Description
This output is closed when Prestart Time (page 1) elapses and is opened when inverter is turned off.
LBO: K
kWh Pulse

LBO ID 206
Description
This output is active for 100 ms every time the Genset kWh is increased by one.

LBO: L
Load Reduction Active

LBO ID 1245
Description
This output is closed when Load Reduction (page 298) is active.
Load Shedding Stage 1

LBO ID 51
Description
This is an output of Load Shedding (page 170).
The load shedding outputs are activated in the order 1, 2, 3, …, X.
The load shedding outputs are deactivated in the order X, …, 3, 2, 1.
The load disconnected by this LBO is the least essential load.
Note: X is the highest configured Load shedding outputs (page 170).

LBO ID 52
Description
The load disconnected by LBO LOAD SHEDDING STAGE 1 (PAGE 954) is the least essential load.


LBO ID 53
Description

LBO ID 452
Description

LBO ID 453
Description


LBO ID 454
Description

LBO ID 455
Description

LBO ID 456
Description

Loaded

LBO ID 72
Description
This output is closed while the BESS is loaded.
Note: Output is opened when BESS starts unloading or opens the BCB without of unloading.
Logical 0

LBO ID 26
Description
Logical binary output which is still in logical 0.
Logical 1

LBO ID 27
Description
Logical binary output which is still in logical 1.
LVRT 1-phase Invalid

LBO ID 2352
Description
This output is closed if any value on the y-axis of the LVRT 1-PHASE (PAGE 874) curve is equal to or
higher than 100% or when the curve is not configured.

LBO ID 2353
Description


LBO ID 2354
Description
LVRT Active

LBO ID 2313
Description
This output is closed while LVRT Protection is active and stays closed for at least 500 ms.
LVRT Severe

LBO ID 2317
Description
This output is closed while BESS Voltage drops under level adjusted by LVRT Level Severe (page 553)
and stays closed for at least 500 ms.
Note: BESS Voltage L1-N (page 670), BESS Voltage L2-N (page 670) and BESS Voltage L3-N
(page 670) is considered.
LVRTCurveTrip

LBO ID 2315
Description
This output is closed when the BESS Voltage drops below the line of LVRT curve and opens when the
BESS Voltage rises above the line of LVRT curve. This output is always closed at least for 3 seconds.
Note: LVRT 1-PHASE (PAGE 874), LVRT 2-PHASE (PAGE 873) and LVRT 3-PHASE (PAGE 872) are
considered.
(page 670) are considered.

LBO: M
Mains/Bus Healthy

LBO ID 78
Description
This output is closed while Mains/Bus parameters (voltage & frequency) are considered as healthy, i. e.
within limits.
Application Mode Setting of Limits

BESS >>V (page 443) BESS >f (page 446)
MINT Generator >V (page 1) BESS <f (page 447)
BESS <V (page 444)
Mains >>V (page 515) Mains >>f (page 523)
Mains >V (page 514) Mains >f (page 522)
MPTM
Mains <<V (page 519) Mains <<f (page 525)
Mains <V (page 518) Mains <f (page 524)
Manual Ready

LBO ID 1258
Description
This output is active when Controller Mode (page 777) = MAN and the BESS is stopped and it is
possible to start it. i.e. no red alarm is activated or SD OVERRIDE (PAGE 915) is active (Output READY
(PAGE 974) is active).
MCB Button Echo

LBO ID 34
Description
This output is closed for 1 s every time MCB Button is pressed.
MCB Close/Open

LBO ID 45
Description
The output controls the mains circuit breaker. Its state represents the breaker position requested by the
controller.
If the feedback does not respond in 2 seconds and it was already the last attempt the specific alarm

based on the current breaker position is issued.
Image 7.31 MCB Close command
MCB OFF Coil

LBO ID 47
Description
The output is intended for opening of mains circuit breaker.
The output provides pulses, which length is 2 seconds when breaker has to open with pause 1 second
between each pulse. If the LBI MCB FEEDBACK (PAGE 902) does not match after second pulse elapses
Alarm Wrn MCB Fail To Open (page 1091) is issued.
Image 7.32 MCB OFF Coil command

MCB ON Coil

LBO ID 46
Description
The output is intended for control of close coil of mains circuit breaker.
The output provides pulse, which length is 2 seconds and the pause between attempts is 3 seconds.
Image 7.33 MCB ON Coil close command
MCB Status

LBO ID 85
Description
This output indicates the MCB position as it is internally considered by the controller. The position is
based on MCB FEEDBACK (PAGE 902) and MCB FEEDBACK NEGATIVE (PAGE 903).
In case that only MCB FEEDBACK (PAGE 902) is used, this output mirrors the input.
In case that both MCB FEEDBACK (PAGE 902) and MCB FEEDBACK NEGATIVE (PAGE 903) are
used and
Feedback match - output indicates MCB position according to feedbacks.
Feedback do not match - output indicates last position when feedbacks matched.

MCB UV Coil

LBO ID 48
Description
The output is intended for control of undervoltage coil of mains circuit breaker.
The output is closed while mains values are within limits. Breaker closing command is blocked for 1 sec
after the UV coil has been closed to allow the breaker mechanical system to get ready for closing. The
output is opened for 2 seconds when the breaker has to open.
Image 7.34 MCB UV Coil close command
Mode AUTO

LBO ID 19
Description
This output is active whenever Controller Mode (page 777) = AUTO, i.e. when LBO NOT IN AUTO (PAGE
963) is opened.
Mode MAN

LBO ID 18
Description
This output is active whenever Controller Mode (page 777) = MAN.

Mode OFF

LBO ID 17
Description
This output is active whenever Controller Mode (page 777) = OFF.
LBO: N
NCB Close/Open

LBO ID 50
Description
Neutral circuit breaker Close/Open output controls the BESS neutral circuit breaker. It is intended for
contactors – provides a continual active signal if NCB should be closed.
Not In Auto

LBO ID 1248
Description
This output is closed whenever Controller Mode (page 777) != AUTO, i.e. when LBO MODE AUTO
(PAGE 962) is opened.
Not Ready

LBO ID 63
Description
This output is closed when the BESS is not operable and is not ready to be started.
Closed if:
LBI START BLOCKING (PAGE 916) is closed
Not Used

LBO ID 286
Description
Output has no function.

LBO: O
Operational

LBO ID 61
Description
This output is closed when the BESS is ready for operation or is currently in operation.
OVRT Active

LBO ID 2314
Description
This output is closed while OVRT Protection is active and stays closed for at least 500 ms.
OVRT Invalid

LBO ID 2351
Description
This output is closed if any value on the y-axis of theOVRT (PAGE 875) curve is equal to or higher than
100% or when the curve is not configured.
OVRTCurveTrip

LBO ID 2316
Description
This output is closed when the BESS Voltage rises above the line of OVRT (PAGE 875) curve and opens
when the BESS Voltage drops bellow the line of OVRT (PAGE 875) curve.
This output is always closed at least for 3 seconds.
(page 670) are considered.

LBO: P
P for Q Active

LBO ID 1546
Description
This output is closed when BESS P (page 664) is reduced in order to achieve BESS Required Q (page
757).
Note: Output is opened if there is another reduction active.
P Over Frequency Active

LBO ID 1183
Description
This output is closed when the BESS P (page 664) starts to be forced to increase due to Power
reduction by over frequency - PoF (page 294).
P Over Frequency Curve Invalid

LBO ID 2196
Description
This output is closed when POWER OVER FREQUENCY (PAGE 866) curve is not configured.
P Under Frequency Active

LBO ID 2115
Description
This output is closed when the BESS P (page 664) starts to be forced to increase due to Power
increase by under frequency - PuF (page 295).
P Under Frequency Curve Invalid

LBO ID 2197
Description
This output is closed when POWER UNDER FREQUENCY (PAGE 867) curve is not configured.

Pave

LBO ID 2248
Description
This output is closed when value Pmom/Pave (page 724) is above the curve P Mom/Pave Max (page
863) and stays closed for 5 seconds.
Pave FLS

LBO ID 2249
Description
This output is closed when Pave Protection (page 560) != Disabled and LAI PMOM (PAGE 993) is either
not configured or has invalid value.
Peak Shaving Active

LBO ID 2118
Description
This output is closed when Peak shaving (page 1) is activated.
Peripheral Module Comm Fail

LBO ID 115
Description
This output is closed when there is no communication with at least one configured peripheral module.

Power Switch

LBO ID 290
Description
This is an output from the Power switch function. The behavior of the switch depends on the adjustment
of the setpoints Power Switch On (page 437) and Power Switch Off (page 437)
When the dummy load function is used the switching ON of Power switch is blocked while the BESS isn’t
running and is allowed 30 s after start of the BESS.
The Power Switch is activated when BESS P (page 664) reach relative On Level which is related to the
Image 7.35 Power Switch Example
Note: Setpoints Power Switch On (page 437) and Power Switch Off (page 437) are invisible until
configuration of this LBO.
PQ-C Area Limit

LBO ID 2244
Description
This output is closed when the BESS Required Q (page 757) is outside the P FOR Q PQ C (PAGE 871).
PQ-L Area Limit

LBO ID 2243
Description
This output is closed when the BESS Required Q (page 757) is outside the P FOR Q PQ L (PAGE 870).
Prestart

LBO ID 36
Description
This output can be used for control of any device, which has to be activated just before BESS start. The
output is closed for time period of Prestart Time (page 1) and opens 100 ms before the BESS state
(page 778) = Starting .
Precharge

LBO ID 2783
Description
This LBO relates to the BESS start sequence decribed in BESS Precharge Types (page 240).
State of precharge.
Precharge Request

LBO ID 2782
Description
This LBO relates to the BESS start sequence decribed in BESS Precharge Types (page 240).
This LBO initiates the BESS start sequence as a request to get the BESS to the precharge state. The
precharge sequence is considered to be finished once the LBI PRECHARGE FINISHED (PAGE 906) gets
active. Both signals are mandatory for correct operation.
Process Power Limitation

LBO ID 2241
Description
This output is closed while BESS P (page 664) is being reduced due to: Import/Export Limitation
(page 1) = Enabled.
PV Operable

LBO ID 2753
Description
This LBO is active if at least one of PV 01 OPERABLE (PAGE 908) is operable

PV/WT Run Request

LBO ID 2690
Description
This output is used to signalize run request of the PV inverter and it is closed all the time when the CU is
not in the OFF mode.
PVCB Button Echo

LBO ID 2710
Description
This output is closed for 1 s every time PVCB Button is pressed.
PVCB Close/Open

LBO ID 2685
Description
The output controls the PV circuit breaker. Its state represents the breaker position requested by the
controller. The breaker must react within 2 seconds to a close or open command, otherwise an alarm Wrn
PVCB Fail (page 1095) is activated.
Image 7.36 PVCB Close command
Image 7.37 Repeated PVCB Close command

PVCB OFF Coil

LBO ID 2687
Description
The output is intended for control of open coil of PVCB circuit breaker. The output gives a pulse in the
moment the breaker has to be opened. The pulse lasts until the feedback deactivates, but at least for 2
seconds.
Image 7.38 PVCB OFF Coil command

PVCB ON Coil

LBO ID 2686
Description
The output is intended for control of close coil of PVCB circuit breaker. The output gives at least 2 second
pulse in the moment the breaker has to be closed.
Image 7.39 PVCB ON Coil close command

Image 7.40 Repeated PVCB ON coil close command
PVCB Status

LBO ID 2689
Description
This output indicates the PVCB position as it is internally considered by the controller.
The position is based on PVCB FEEDBACK (PAGE 912) and PVCB FEEDBACK NEGATIVE (PAGE 913).
In case that onlyPVCB FEEDBACK (PAGE 912) is used, this output mirrors the input.
In case that both PVCB FEEDBACK (PAGE 912) and PVCB FEEDBACK NEGATIVE (PAGE 913) are
used and
Feedbacks match - output indicates PVCB position according to feedbacks.

PVCB UV Coil

LBO ID 2688
Description
The output is intended for control of undervoltage coil of PV circuit breaker. The output is active the whole
time when the controller is switched on. The output is deactivated for at least 2 seconds in the moment the
breaker has to be switched off.
Image 7.41 PVCB UV Coil close command
Image 7.42 PVCB UV Coil open command

LBO: R
Ready

LBO ID 62
Description
This output is closed when the BESS is stopped and it is possible to start it.
No Alarms level 2 (page 1112) present in the alarmlist
LBI SD OVERRIDE (PAGE 915) is opened
Reverse Synchronization

LBO ID 69
Description
The output is closed when reverse synchronization is active (synchronization via MCB breaker) and
opens when LBO MCB STATUS (PAGE 961) closes.
ROCOF 1 Active

LBO ID 1005
Description
This output is closed for 3 seconds when ROCOF1 Protection (page 585) is activated.
ROCOF 2 Active

LBO ID 2724
Description
ROCOF 3 Active

LBO ID 2725
Description
This output is closed for 3 seconds whenROCOF1 Protection (page 585) is activated.

ROCOF 4 Active

LBO ID 2726
Description
LBO: S
Sd Override

LBO ID 962
Description
The output is closed if SD OVERRIDE (PAGE 915) input is active and opened if SD OVERRIDE (PAGE 915)
input is inactive. This output is usually used to send information about SD OVERRIDE (PAGE 915) input into
ECU.
SOC Discharge Disabled

LBO ID 2701
Description
This output is active when state of charge of the BESS is too low and BESS cannot be discharged
anymore.
SOC Charge Disabled

LBO ID 2700
Description
This output is active when state of charge of the BESS is too high and BESS cannot be charged
anymore.
Soft Load

LBO ID 71
Description
This output is closed when BCB closes and BESS is being soft loaded via Load Ramp (page 468). Later
change of BESS P (page 664) does not close this output again.

Soft Unload

LBO ID 73
Description
This LBO is active while controller perform soft unloading.
This output is closed when BCB is requested to be opened and BESS is being soft unloaded via Soft
Unload Ramp (page 559).
Start Blocked

LBO ID 1226
Description
This output is closed while start of the BESS is blocked due to at least one of these reasons:
LBI START BLOCKING (PAGE 916) is closed
Application Mode (page 777) = MPTM, Controller Mode (page 777) = AUTO, LBO MAINS/BUS
HEALTHY (PAGE 959) is opened and LBI FORCE PARALLEL (PAGE 887) is closed
Start Button Echo

LBO ID 33
Description
This output is closed for 1 s every time Start Button is pressed.
Starting

LBO ID 65
Description
This output is closed at the beginning of the Prestart Time (page 1) period and opens after starting
phase is finished or when Sd Start Fail (page 1123) alarm is activated.
Stop Button Echo

LBO ID 32
Description
This output is closed for 1 s every time Stop Button is pressed.

Stopping

LBO ID 75
Description
This output i closed during stopping sequence after stop command is received and opens after the BESS
is considered to be stopped.
Sync To Mains Allowed
MPTM
Related FW 1.3.0 Related applications
LBO ID 1057
Description
This output is closed when synchronization to the mains is allowed or Breaker state (page 778) =
ParalOper.
See Synchronization & Connection Conditions (page 302) for more information.
System Ready

LBO ID 86
Description
This output is closed if the controller group has enough capacity to fulfill the requested power reserve. If
the output is opened, then the group has not enough capacity to fulfill the reserve even if all the units will
run.
Note: Fulfilled reserve means that Available Nominal Power (page 751) is above the Minimal
Running Nominal Power (page 751)
System Reserve OK

LBO ID 87
Description
This output is closed when Actual Reserve (page 748) is higher than the Start Reserve (page 749).

LBO: U
UQ-C Area Limit

LBO ID 2246
Description
This output is closed when the BESS Required Q (page 757) is outside the P FOR Q UQ C (PAGE 869).
UQ-L Area Limit

LBO ID 2245
Description
This output is closed when the BESS Required Q (page 757) is outside the P FOR Q UQ L (PAGE 868).
LBO: V
Vector Shift Active

LBO ID 93
Description
This output is closed for 3 seconds when Vector Shift Protection (page 584) is activated.
Voltage Down

LBO ID 55
Description
This output together with the complementary output VOLTAGE UP (PAGE 979) are designed for voltage
and power factor control of the BESS, where the BESS inverter regulator does not support analogue
control.

Voltage Up

LBO ID 54
Description
This output together with the complementary output VOLTAGE DOWN (PAGE 978) are designed for voltage
and power factor control of the BESS, where the BESS inverter regulator does not support analogue
control.
LBO: W
WT Operable

LBO ID 2754
Description
This LBO is active if at least one of WT 01 OPERABLE (PAGE 918) is operable

9.1.8 Logical analog inputs
What Logical analog inputs are:
Logical analog inputs are inputs for analog values.
Alphabetical groups of Logical analog inputs

LAI: B 983
LAI: C 985
LAI: D 988
LAI: I 988
LAI: L 989
LAI: M 991
LAI: P 992
LAI: Q 1004
LAI: T 1008
LAI: W 1009
For full list of Logical analog inputs go to the chapter Logical analog inputs alphabetically (page 981).

Logical analog inputs alphabetically
LAI: B 983 Irradiation of PV Array 1 990 PV 06 kWh 997

Battery Discharge kWh 983 Irradiation of PV Array 2 990 PV 06 Nominal P 997
Battery Charge kWh 983 Irradiation of PV Array 3 991 PV 07 Actual P 997
Battery Charging Cycles 983 Irradiation of PV Array 4 991 PV 07 Actual Q 997
BESSCapacity 983 LAI: M 991 PV 07 kWh 998
BESS Max Discharge P 983 Mains Import P Monitoring 991 PV 07 Nominal P 998
BESS Max Charge P 984 Mains Import Q Monitoring 991 PV 08 Actual P 998
BESS P Request 984 Mains Measurement P 992 PV 08 Actual Q 998
BESS Q Request 984 Mains Measurement Q 992 PV 08 kWh 998
BESS SOC 984 LAI: P 992 PV 08 Nominal P 998
BESS Temperature 984 PF Control: ANEXT Base PV 09 Actual P 999
PF 992
LAI: C 985 PV 09 Actual Q 999
Cold Temp 1 985 PF Control: ANEXT
PV 09 kWh 999
Imp/Exp PF 993
Cold Temp 2 985 PV 09 Nominal P 999
Pmom 993
Cold Temp 3 985 PV 10 Actual P 999
PV 01 Actual P 993
Cold Temp 4 986 PV 10 Actual Q 999
PV 01 Actual Q 993
Cold Temp 5 986 PV 10 kWh 1000
PV 01 kWh 994
PV 01 Nominal P 994
Cold Temp 7 987 PV 11 Actual P 1000
PV 02 Actual P 994
Cold Temp 8 987 PV 11 Actual Q 1000
PV 02 Actual Q 994
Cold Temp 9 987 PV 11 kWh 1000
PV 02 kWh 994
PV 02 Nominal P 994
LAI: D 988 PV 12 Actual P 1001
Dynamic Spinning PV 03 Actual P 995
PV 12 Actual Q 1001
Reserve 988 PV 03 Actual Q 995
PV 12 kWh 1001
Dynamic Spinning PV 03 kWh 995
PV 12 Nominal P 1001
Reserve Offset 988 PV 03 Nominal P 995
PV 13 Actual P 1001
LAI: I 988 PV 04 Actual P 995
PV 13 Actual Q 1001
Irradiation of PV Array 1 988 PV 04 Actual Q 995
PV 13 kWh 1002
Irradiation of PV Array 2 989 PV 04 kWh 996
PV 13 Nominal P 1002
Irradiation of PV Array 3 989 PV 04 Nominal P 996
PV 14 Actual P 1002
Irradiation of PV Array 4 989 PV 05 Actual P 996
PV 14 Actual Q 1002
LAI: L 989 PV 05 Actual Q 996
Load Control: ANEXT PV 14 kWh 1002
PV 05 kWh 996
Baseload 989 PV 14 Nominal P 1002
PV 05 Nominal P 996
Load Control: ANEXT PV 15 Actual P 1003
PV 06 Actual P 997
Imp/Exp Load 990 PV 15 Actual Q 1003
PV 06 Actual Q 997
Load Reduction 990 PV 15 kWh 1003

PV 16 Actual P 1003 WT 05 Actual P 1012
PV 16 Actual Q 1003 WT 05 kWh 1013
PV 16 kWh 1004 WT 06 Actual P 1013
LAI: Q 1004 WT 06 kWh 1013
Q Control: ANEXT Base WT 06 Nominal P 1013
Q 1004 WT 07 Actual P 1013
Q Control: ANEXT WT 07 Actual Q 1014
Imp/Exp Q 1004
WT 07 kWh 1014
Q(Um): 0 Ref ANEXT
WT 07 Nominal P 1014
Base Q 1005
WT 08 Actual P 1014
Q(Um): 0 Ref ANEXT
Imp/Exp Q 1006 WT 08 Actual Q 1014
Qref/Ulim: ANEXT WT 08 kWh 1014

Qref/Pnom B Q 1007 WT 08 Nominal P 1015
Qref/Ulim: ANEXT 6 back to Controller objects
Qref/Pnom I/E Q 1008
LAI: T 1008
TestF 1008
TestP 1009
TestQ 1009
TestU 1009
LAI: W 1009
WT 01 Actual P 1009
WT 01 Actual Q 1010
WT 01 kWh 1010
WT 02 Actual P 1010
WT 02 Actual Q 1010
WT 02 kWh 1010
WT 03 Actual P 1011
WT 03 Actual Q 1011
WT 03 kWh 1011
WT 04 Actual P 1011
WT 04 Actual Q 1012
WT 04 kWh 1012

LAI: B
Battery Discharge kWh

LAI ID 427
Description
This LAI defines the amount of discharged energy from the BESS and it is used as source for statistic
values.
6 back to Logical analog inputs alphabetically
Battery Charge kWh

LAI ID 426
Description
This LAI defines the amount of charged energy to the BESS and is used as a source for statistic values.
Battery Charging Cycles

LAI ID 428
Description
This analog input is used as source for the statistic value Batt. Charging Cycles (page 765) and for the
function Daily Battery Cycles Control (page 237).
BESSCapacity

LAI ID 370
Description
Capacity of the BESS.
BESS Max Discharge P

LAI ID 425
Description
This LAI defines maximal allowed discharge power of the BESS.

BESS Max Charge P

LAI ID 424
Description
Maximal allowed charging power of the BESS.
BESS P Request

LAI ID 420
Description
LAI is used for adjusting BESS Power Request while Charging / Discarding process.
BESS Q Request

LAI ID 429
Description
LAI is used for adjusting BESS Reactive Power Request while Charging / Discarding process.
BESS SOC

LAI ID 368
Description
This LAI is used to monitor actual state of charge of the BESS.
BESS Temperature

LAI ID 371
Description
This LAI is used as input for temperature of the BESS.

LAI: C
Cold Temp 1

LAI ID 56
Description
This LAI is used for compensation of thermocouple temperature measurement. It is used when there is a
significant temperature difference between on-board terminal and a module terminal (such as Inteli
AIN8TC). This input compensate the CAN module configured with address (index) 1.
Note: The compensation is only for thermocouples without internal compensation "Thermo (nc) …" (not
cold junction compensation).
Cold Temp 2

LAI ID 57
Description
Cold Temp 3

LAI ID 58
Description

Cold Temp 4

LAI ID 59
Description
Cold Temp 5

LAI ID 341
Description
Cold Temp 6

LAI ID 342
Description

Cold Temp 7

LAI ID 343
Description
Cold Temp 8

LAI ID 344
Description
Cold Temp 9

LAI ID 418
Description

Cold Temp 10

LAI ID 419
Description
LAI: D

LAI ID 192
Description
This LAI is used as source of the value Dynamic Spinning Reserve (page 749).
Dynamic Spinning Reserve Offset

LAI ID 233
Description
This LAI is used as source of the value Dynamic Spinning Reserve Offset (page 749).
LAI: I
Irradiation of PV Array 1

LAI ID 544
Description
This parameter represents the irradiation data for PV Array 1, providing information about the amount of
sunlight received at the specific location within the microgrid.


LAI ID 545
Description
This parameter represents the irradiation data for PV Array 2, offering insights into the amount of sunlight
received at the specific location within the microgrid.

LAI ID 546
Description
This parameter provides irradiation data for PV Array 3, indicating the amount of sunlight received at the
specific location within the microgrid.

LAI ID 547
Description
This parameter offers irradiation data for PV Array 4, providing information about the amount of sunlight
LAI: L
Load Control: ANEXT Baseload

LAI ID 1
Description
This LAI is source value for control of Active Power if Load Request Source (page 346) = Analog
External Value.
The Baseload is active if
MINT: #System Load Control PTM (page 347) = Baseload
MPTM: Load Control PTM Mode (page 345) = Baseload

Load Control: ANEXT Imp/Exp Load

LAI ID 2
Description
This LAI is source value for control of Active Power if Load Request Source (page 346) = Analog
External Value.
The Import/Export is active if Load Control PTM Mode (page 345) = Import/Export.
Load Reduction

LAI ID 193
Description
This LAI adjusts maximal allowed load of the BESS while Setpoiont LOAD REDUCTION (PAGE 540) is
Enabled and LBI LOAD REDUCTION ENABLE (PAGE 897) is closed.
Always the lowest load defined by this LAI or by LBIs, LOAD REDUCTION 1 (PAGE 896), LOAD REDUCTION
2 (PAGE 896), etc. is allowed.

LAI ID 544
Description
This parameter represents the irradiation data for PV Array 1, providing information about the amount of
sunlight received at the specific location within the microgrid.

LAI ID 545
Description
This parameter represents the irradiation data for PV Array 2, offering insights into the amount of sunlight


LAI ID 546
Description
This parameter provides irradiation data for PV Array 3, indicating the amount of sunlight received at the
specific location within the microgrid.

LAI ID 547
Description
This parameter offers irradiation data for PV Array 4, providing information about the amount of sunlight
LAI: M
Mains Import P Monitoring

LAI ID 430
Description
This analog input is used as source for monitoring of Mains active power import which is used in
calculations.
Mains Import Q Monitoring

LAI ID 431
Description
This analog input is used as source for monitoring of Mains reactive power import which is used in
calculations.

Mains Measurement P

LAI ID 5
Description
This LAI is designed for Mains Import Measurement (page 175), when Mains Measurement P (page
357) = Analog Input. Value from this input is used in load transfer from Mains to BESS.
Load transfer is considered to be finished when this value is lower than Mains Unload MCB Open
Window (page 467)
Mains Measurement Q

LAI ID 6
Description
This LAI is designed for Mains Import Measurement (page 175), when Mains Measurement Q (page
358) = Analog Input. Value from this input is used in load transfer from mains to BESS.
Load transfer is considered to be finished when this value is lower than Mains Unload MCB Open
Window (page 467)
LAI: P
PF Control: ANEXT Base PF

LAI ID 3
Description
This LAI is a source value for control of the Power Factor if PF/Q Request Source (page 350) = Analog
External Value .
The Base PF is active if
MINT: #System PF Control PTM (page 351) = Base PF
MPTM: PF/Q Control PTM Mode (page 349) = PF Control and PF/Q Regulation Type (page
351) = Base PF/Q Control
Analog value Cos phi factor

<0.600 0.6L
0.600 .. 1.000 0.6L .. 1.00
1.001 .. 1.200 0.99C .. 0.80C
Note: Always use a three decimal number for this LAI. Thus the range for this LAI is 0.600 to 1.200.
Note: If all setpoints are adjusted as mentioned above and Breaker state (page 778) = ParalOper, but
this LAI is not configured, alarm Wrn PF Control Fail (page 1093) is activated.

PF Control: ANEXT Imp/Exp PF

LAI ID 4
Description
External Value.
The Import/Export PF is active if PF/Q Control PTM Mode (page 349) = PF Control and PF/Q
Regulation Type (page 351) = Import/Export PF/Q Control.
Analog value Cos phi factor

<0.600 0.6L
0.600 .. 1.000 0.6L .. 1.00
1.001 .. 1.200 0.99C .. 0.80C
Note: Always use a three decimal number for this LAI.
this LAI is not configured, alarm Wrn PF Control Fail (page 1093) is activated.
Pmom

LAI ID 340
Description
This LAI is used for receiving exported power measured in all 3 phases and is used during Pave (page
304) function. The value can be received via CAN Intercontroller Communication (page 132) from
InteliPro Sync, InteliPro, InteliMains or connected to physical analog input.
PV 01 Actual P

LAI ID 358
Description
This LAI is designed to monitor actual power of the PV 1.
PV 01 Actual Q

LAI ID 359
Description
This LAI is designed to monitor actual reactive power of the PV 1.

PV 01 kWh

LAI ID 361
Description
This LAI defines the amount of energy produced by PV 1 and is used as a source for statistic values.
PV 01 Nominal P

LAI ID 360
Description
This LAI is used to define nominal power of the PV 1 used in the system.
PV 02 Actual P

LAI ID 449
Description
PV 02 Actual Q

LAI ID 464
Description
PV 02 kWh

LAI ID 479
Description
PV 02 Nominal P

LAI ID 434
Description

PV 03 Actual P

LAI ID 450
Description
PV 03 Actual Q

LAI ID 465
Description
PV 03 kWh

LAI ID 480
Description
PV 03 Nominal P

LAI ID 435
Description
PV 04 Actual P

LAI ID 451
Description
PV 04 Actual Q

LAI ID 466
Description

PV 04 kWh

LAI ID 481
Description
PV 04 Nominal P

LAI ID 436
Description
PV 05 Actual P

LAI ID 452
Description
PV 05 Actual Q

LAI ID 467
Description
PV 05 kWh

LAI ID 482
Description
PV 05 Nominal P

LAI ID 437
Description

PV 06 Actual P

LAI ID 453
Description
PV 06 Actual Q

LAI ID 468
Description
PV 06 kWh

LAI ID 483
Description
PV 06 Nominal P

LAI ID 438
Description
PV 07 Actual P

LAI ID 454
Description
PV 07 Actual Q

LAI ID 469
Description

PV 07 kWh

LAI ID 484
Description
PV 07 Nominal P

LAI ID 439
Description
PV 08 Actual P

LAI ID 455
Description
PV 08 Actual Q

LAI ID 470
Description
PV 08 kWh

LAI ID 485
Description
PV 08 Nominal P

LAI ID 440
Description

PV 09 Actual P

LAI ID 456
Description
PV 09 Actual Q

LAI ID 471
Description
PV 09 kWh

LAI ID 486
Description
PV 09 Nominal P

LAI ID 441
Description
PV 10 Actual P

LAI ID 457
Description
PV 10 Actual Q

LAI ID 472
Description

PV 10 kWh

LAI ID 487
Description
PV 10 Nominal P

LAI ID 442
Description
PV 11 Actual P

LAI ID 458
Description
PV 11 Actual Q

LAI ID 473
Description
PV 11 kWh

LAI ID 488
Description
PV 11 Nominal P

LAI ID 443
Description

PV 12 Actual P

LAI ID 459
Description
PV 12 Actual Q

LAI ID 474
Description
PV 12 kWh

LAI ID 489
Description
PV 12 Nominal P

LAI ID 444
Description
PV 13 Actual P

LAI ID 460
Description
PV 13 Actual Q

LAI ID 475
Description

PV 13 kWh

LAI ID 490
Description
PV 13 Nominal P

LAI ID 445
Description
PV 14 Actual P

LAI ID 461
Description
PV 14 Actual Q

LAI ID 476
Description
PV 14 kWh

LAI ID 491
Description
PV 14 Nominal P

LAI ID 446
Description

PV 15 Actual P

LAI ID 462
Description
PV 15 Actual Q

LAI ID 477
Description
PV 15 kWh

LAI ID 492
Description
PV 15 Nominal P

LAI ID 447
Description
PV 16 Actual P

LAI ID 463
Description
PV 16 Actual Q

LAI ID 478
Description

PV 16 kWh

LAI ID 493
Description
PV 16 Nominal P

LAI ID 448
Description
LAI: Q
Q Control: ANEXT Base Q

LAI ID 171
Description
External Value .
The Base Q is active if
MINT: #System PF Control PTM (page 351) = Base Q
MPTM: PF/Q Control PTM Mode (page 349) = Q Control and PF/Q Regulation Type (page
351) = Base PF/Q Control
this LAI is not configured, alarm Wrn Q Control Fail (page 1096) is activated.
Q Control: ANEXT Imp/Exp Q

LAI ID 195
Description
External Value.
The Import/Export Q is active if PF/Q Control PTM Mode (page 349) = Q Control and PF/Q Regulation
Type (page 351) = Import/Export PF/Q Control.
this LAI is not configured, alarm Wrn Q Control Fail (page 1096) is activated.

Q(Um): 0 Ref ANEXT Base Q
MINT,
Related FW 1.3.0 Related applications
MPTM
LAI ID 326
Description
This LAI is used to shift Q(UM) (PAGE 858) curve left or right if PF/Q Control PTM Mode (page 349) = Q
(Um), PF/Q Request Source (page 350) = Analog External Value and PF/Q Regulation Type (page
351) = Base PF/Q Control.
this LAI is not configured, or is out of sensor range alarm Wrn Q(Um) Fail (page 1098) is activated.

Q(Um): 0 Ref ANEXT Imp/Exp Q

LAI ID 327
Description
This LAI is used to shift Q(UM) (PAGE 858) curve left or right if PF/Q Control PTM Mode (page 349) = Q
(Um), PF/Q Request Source (page 350) = Analog External Value and PF/Q Regulation Type (page
351) = Import/Export PF/Q Control.
this LAI is not configured, or is out of sensor range alarm Wrn Q(Um) Fail (page 1098) is activated.

Qref/Ulim: ANEXT Qref/Pnom B Q

LAI ID 328
Description
This LAI is used to shift part of the QREF/ULIM (PAGE 859) curve up or down if PF/Q Control PTM Mode
(page 349) = Qref/Ulim, PF/Q Request Source (page 350) = Analog External Value and PF/Q
Regulation Type (page 351) = Base PF/Q Control.
this LAI is not configured, or is out of sensor range, alarm Wrn Qref/Ulim Fail (page 1098) is activated.

Qref/Ulim: ANEXT Qref/Pnom I/E Q

LAI ID 329
Description
This LAI is used to shift part of the QREF/ULIM (PAGE 859) curve up or down if PF/Q Control PTM Mode
(page 349) = Qref/Ulim, PF/Q Request Source (page 350) = Analog External Value and PF/Q
Regulation Type (page 351) = Import/Export PF/Q Control.
this LAI is not configured, or is out of sensor range, alarm Wrn Qref/Ulim Fail (page 1098) is activated.
LAI: T
TestF

LAI ID 194
Description
This LAI is used for adjusting mains frequency while Testing of Grid Codes (page 294) function is
enabled. Value received via this input is stored in Test Frequency (page 721) as Nominal Frequency
(page 377) + value of this input.
Note: Setpoint Grid Codes Test (page 527) has to be Enabled and alarm Wrn Test UPQF (page
1103) has to be active, otherwise this LAI has no effect.

TestP

LAI ID 231
Description
This LAI is used for adjusting generator's active power while Testing of Grid Codes (page 294)
function is enabled.
TestQ

LAI ID 232
Description
This LAI is used for adjusting generator's reactive power while Testing of Grid Codes (page 294)
TestU

LAI ID 385
Description
This LAI is used for adjusting generator's active power while Testing of Grid Codes (page 294)
Value received via this input is considered as relative value of Mains Voltage Ph-N related to Mains/Bus
Nominal Voltage Ph-N (page 373) or as relative value of Mains Voltage Ph-Ph related to Mains/Bus
Nominal Voltage Ph-Ph (page 374) based on Connection type (page 371).
LAI: W
WT 01 Actual P

LAI ID 502
Description
This LAI is designed to monitor actual power of the WT 1.

WT 01 Actual Q

LAI ID 510
Description
This LAI is designed to monitor actual reactive power of the WT 1.
WT 01 kWh

LAI ID 518
Description
This LAI defines the amount of energy produced by WT 1 and is used as a source for statistic values.
WT 01 Nominal P

LAI ID 494
Description
This LAI is used to define nominal power of the WT 1 used in the system.
WT 02 Actual P

LAI ID 503
Description
WT 02 Actual Q

LAI ID 511
Description
WT 02 kWh

LAI ID 519
Description

WT 02 Nominal P

LAI ID 495
Description
WT 03 Actual P

LAI ID 504
Description
WT 03 Actual Q

LAI ID 512
Description
WT 03 kWh

LAI ID 520
Description
WT 03 Nominal P

LAI ID 496
Description
WT 04 Actual P

LAI ID 505
Description

WT 04 Actual Q

LAI ID 513
Description
WT 04 kWh

LAI ID 521
Description
WT 04 Nominal P

LAI ID 497
Description
WT 05 Nominal P

LAI ID 498
Description
WT 05 Actual Q

LAI ID 514
Description
WT 05 Actual P

LAI ID 506
Description

WT 05 kWh

LAI ID 522
Description
WT 06 Actual P

LAI ID 507
Description
WT 06 Actual Q

LAI ID 515
Description
WT 06 kWh

LAI ID 523
Description
WT 06 Nominal P

LAI ID 499
Description
WT 07 Actual P

LAI ID 508
Description

WT 07 Actual Q

LAI ID 516
Description
WT 07 kWh

LAI ID 524
Description
WT 07 Nominal P

LAI ID 500
Description
WT 08 Actual P

LAI ID 509
Description
WT 08 Actual Q

LAI ID 517
Description
WT 08 kWh

LAI ID 525
Description

WT 08 Nominal P

LAI ID 501
Description

9.1.9 Fixed Protection States
List of Fixed Protection States
Fixed Protections States 1 1017

Fixed Protections States 1

Comm object 20744
Description
This is a group of fixed protection states.
List of protection states by bits:
1. Wrn Brute Force Protection Active (page 1085)
2. Wrn Redundant CAN inconsistency (page 1099)
3. Wrn CAN2 Empty (page 1085)
4. Wrn SHBIN Collision (page 1183)
5. Wrn SHAIN Collision (page 1181)
6. ALI GCB Closing Is Blocked (page 1)
7. Not Used
8. Not Used
9. Not Used
10. Not Used
11. Not Used
12. Not Used
13. Not Used
14. Not Used
15. Not Used
16. Wrn Battery Undervoltage (page 1085)
17. Wrn Battery Overvoltage (page 1084)
18. Wrn SD Card Failed (page 1100)
19. Wrn Long Term History Fail (page 1089)
20. Not Used
21. Not Used
22. Not Used
23. Wrn Override All Sd (page 1091)
24. Wrn Load IMP/EXP Fail (page 1088)
25. Wrn PF/Q IMP/EXP Fail (page 1093)
26. Wrn PF Control Fail (page 1093)
27. Wrn Q Control Fail (page 1096)
28. Wrn Q(Um) Fail (page 1098)
29. Wrn Qref/Ulim Fail (page 1098)
30. Wrn Q(P) Fail (page 1097)
31. Wrn PF(Pm) Fail (page 1094)
32. Wrn P(Um) Fail (page 1092)
6 back to Fixed Protection States


Comm object 20745
Description
1. Sd BESS >V L1-N (page 1117)
4. Sd BESS >V L1-L2 (page 1117)
7. Sd BESS >>V L1-N (page 1115)
8. Sd Mains/Bus >>V L2-N (page 1115)
9. Sd BESS >>V L3-N (page 1116)
10. Sd BESS >>V L1-L2 (page 1116)
11. Sd BESS >>V L2-L3 (page 1116)
12. Sd BESS >>V L3-L1 (page 1116)
13. Sd BESS <V L1-N (page 1118)
16. Sd BESS <V L1-L2 (page 1119)
19. Sd BESS V Unbalance Ph-N (page 1120)
20. Sd BESS V Unbalance Ph-Ph (page 1120)
21. Sd BESS >f (page 1120)
22. Sd BESS <f (page 1120)
23. Not Used
24. Not Used
25. Sd IDMT Overload (page 1121)
26. PVBO Short Circuit (page 1122)
27. Sd IDMT BESS >A (page 1121)
28. Sd IDMT Earth Fault Current (page 1121)
29. Sd BESS Current Unbalance (page 1121)
30. ALI BESS Ph Rotation Opposite (page 1106)


Comm object 20746
Description
1. Emergency Stop (page 1114)
2. Not Used
3. Not Used
4. Not Used
5. Wrn Stop Fail (page 1102)
6. Wrn SOC Low Alarm (page 1101)
7. Wrn SOC High Alarm (page 1101)
8. Sd SOC Critical Low (page 1122)
9. Sd SOC Critical High (page 1122)
10. Not Used
11. Wrn Frequency Regulation Limit (page 1087)
12. Wrn Voltage Regulation Limit (page 1103)
13. Stp Synchronization Fail (page 1128)
14. Wrn Reverse Synchronization Fail (page 1100)
15. Stp BCB Fail (page 1124)
16. Stp BCB Secondary Fail (page 1126)
17. Sd NCB Fail (page 1122)
18. Not Used
19. Not Used
20. Not Used
21. Not Used
22. Not Used
23. Not Used
24. Not Used
25. Not Used
26. Not Used
27. Not Used
28. Not Used
29. Not Used
30. Not Used
31. Not Used
32. Not Used


Comm object 20747
Description
1. Mains/Bus >V L1-N (page 1135)
4. Mains/Bus >V L1-L2 (page 1137)
7. Mains/Bus >>V L1-N (page 1139)
10. Mains/Bus >>V L1-L2 (page 1141)
13. Mains Avg >V L1-N (page 1130)
16. Mains Avg >V L1-L2 (page 1130)
19. Mains/Bus <V L1-N (page 1144)
22. Mains/Bus <V L1-L2 (page 1146)
25. Mains/Bus <<V L1-N (page 1148)
28. Mains/Bus <<V L1-L2 (page 1150)
31. Mains/Bus V Unbalance Ph-Ph (page 1155)
32. Mains/Bus V Unbalance Ph-N (page 1155)


Comm object 20748
Description
1. Mains/Bus >f (page 1153)
2. Mains/Bus >>f (page 1153)
3. Mains/Bus <f (page 1154)
4. Mains/Bus <<f (page 1154)
5. ALI Mains Ph Rotation Opposite (page 1109)
6. ALI Bus Ph Rotation Opposite (page 1105)
7. Wrn MCB Fail (page 1089)
8. Stp Bus Meas Error (page 1124)
9. Wrn SD Card File System Failed (page 1100)
10. Wrn Test UPQF (page 1103)
11. AHI SyncNotAllowed (page 1110)
12. Wrn P for Q Fail (page 1092)
13. Wrn Q&U Protection (page 1097)
14. Wrn VRT Protection Trip (page 1183)
15. MP VRT Protection Trip (page 1183)
16. Wrn Soft Transfer Fail (page 1102)
17. Not Used
18. Not Used
19. Not Used
20. Not Used
21. Not Used
22. Not Used
23. Not Used
24. Not Used
25. Not Used
26. Not Used
27. Not Used
28. Not Used
29. Not Used
30. Not Used
31. Not Used
32. Not Used


Comm object 20749
Description
1. ECU 1 Comm Fail (page 1175)


Comm object 20750
Description
1. Wrn Alarm e-mail 1 Fail (page 1083)
5. Wrn SNMP TRAP 1 Fail (page 1100)
6. Wrn SNMP TRAP 2 Fail (page 1101)
7. Wrn Maintenance 1 RunHours (page 1156)
8. Maintenance 1 RunHours (page 1156)
15. Wrn Maintenance 1 Interval (page 1156)
16. Maintenance 1 Interval (page 1156)
23. Wrn MCB Fail To Open (page 1091)
24. Wrn MCB Fail To Close (page 1090)
25. Stp BCB Fail To Open (page 1125)
26. Stp BCB Fail To Close (page 1125)
27. Stp BCB Secondary Fail To Open (page 1128)
28. Stp BCB Secondary Fail To Close (page 1127)
29. ALI SD Card Not Compatible (page 1107)
30. ALI SD Card In Slot (page 1108)
31. ALI SD Card Full (page 1108)
32. ALI SD Card Formatting/Mounting (page 1108)

9.1.10 User Protection States
List of User Protection States
User Protections States 1 1025

User Protections States 1

Comm object 20759
Description
This is a group of user protection states.
6 back to User Protection States

Comm object 20760
Description
Related FW 1.3.0 5Related applications MINT, MPTM

Comm object 20761
Description

Comm object 20762
Description

Comm object 20763
Description


Comm object 20764
Description

Comm object 20765
Description

Comm object 20766
Description

Comm object 20767
Description

Comm object 20768
Description

9.1.11 PLC
List of PLC blocks
Group: Logical functions 1029
OR/AND 1029
XOR/RS 1031
Group: Comparators 1032
Comp Delay 1032
Comp Hyst 1033
Comp Win 1034
Group: Time functions 1035
Delay 1035
Timer 1037
Group: Math operations 1039
Interpolation 1039
AxB/C±D 1040
Math Fc. 1041
Group: Regulators 1043
PID 1043
Up/Down Ctrl Block 1047
Group: Ramp functions 1050
Inc/Dec 1050
LowPassFlt 1051
Mov Avg 1052
Ramp 1053
Up/Down 1054
Group: Other functions 1055
Analog Switch 8 1055
Bit Sum 16 1057
Circuit Breaker 1059
Convert 1062
Counter 1063
Comp. 4 1064
Comp. 16 1065
Decomp. 4 1066
Decomp. 16 1067
Differ 1069
Heartbeat 1070
Hold 1072

PF Conv 1073
Poly Appx 1075
PWR Calc 1076
Validator 1079

Group: Logical functions
OR/AND
PLC group Logical functions
Related FW 1.3.0
Related applications MINT, MPTM
PLC Block ID 1
Inputs
Input Type Negation Range Function

Input 1 Binary Yes 0/1 Input 1
Input 3 Binary Yes 0/1 Input 3 (optional)
Outputs
Output Type Negation Range Function

Output Binary Yes 0/1 Result of the logical operation
Description
The block performs logical operation OR / AND of 2 - 8 binary operands. The inputs as well as the output
can be inverted.
Function OR Function AND

Input 1 Input 2 Output Input 1 Input 2 Output
0 0 0 0 0 0
0 1 1 0 1 0
1 0 1 1 0 0
1 1 1 1 1 1
There have to be at least 2 inputs every time. There may be up to 8 inputs configured.

Image 7.43 Configuration of OR/AND block
6 back to List of PLC blocks

XOR/RS
PLC group Logical functions
Related FW 1.3.0
PLC Block ID 39
Inputs

Input 1..2 Binary Yes 0/1 Inputs 1..2
Outputs

Output Binary Yes 0/1 Result of the logical operation
Description
The block performs logical (boolean) XOR operation of two binary operands or several variants of the RS
flipflop function. Both Inputs and Output can be inverted.
Function type XOR

Input 1 Input 2 Output
0 0 0
0 1 1
1 0 1
1 1 0
The result of XOR operation between two binary inputs (Input 1 and Input 2) is defined by table below.
Function type RS
R-latch S-latch E-latch JK-latch
Input 2 (R) Input 1 (S)
Q
-1 -1 -1 -1
0 0 Q Q Q Q
0 1 1 1 1 1
1 0 0 0 0 0
-1 -1
1 1 0 1 Q NOT(Q )
-1
The Q denotes the state of the RS block output in the last evaluation cycle.
The block Output value is given by the selected RS flip-flop variant evaluation:
R-latch: When both inputs (R, S) are set the Reset input is dominant.
S-latch: When both inputs (R, S) are set the Set input is dominant.
E-latch: When both inputs (R, S) are set the previous output is preserved.
JK-latch: When both inputs (R, S) are set the block output is negated.
The block has the setting for the variant functions of the RS flip-flop circuit. This setting is

available in the block configuration dialog (i.e. it is done in the configuration and cannot be
changed dynamically while the PLC is running).
Image 7.44 Configuration of XOR/RS block
Group: Comparators
Comp Delay
PLC group Comparators

Related FW 1.3.0
PLC Block ID 46
Inputs

32 32
Input 1 Analog No -2 .. 2 Compared value
32 32
Input 2 Analog No -2 .. 2 Comparation level
Delay Analog No 0.0 .. 3000.0 [s] Comparative delay
Outputs

Output Binary Yes 0/1 Comparator output
Description
This PLC block compares the Input value with the Reference comparison level using the selected
Relation. The Output will switch on if the Input is equal/higher/smaller/etc. than the Reference
comparison level for a time longer than the Delay. All Relation operations between the Input and the
Reference are described in the table below.
Relation Name
">" (default) greater than
">=" greater than equal
"==" equal
"<=" less than equal
"<" less than

Image 7.45 Configuration of Comp Delay block
Comp Hyst

Related FW 1.3.0
PLC Block ID 3
Inputs

32 32
Input Analog No -2 .. 2 Compared value
32 32 Comparative level for

Input ON Analog No -2 .. 2
switching on
32 32 Comparative level for

Input OFF Analog No -2 .. 2
switching off
Outputs

Output Binary No 0/1 Comparator output
Description
TThe block compares the Input value with two comparison levels I-ON and I-OFF. The evaluation of the
block depends on whether the I-ON level is higher than the I-OFF level or vice versa.
Image 7.46 Different On and Off levels

Image 7.47 Configuration of Comp Hyst block
Comp Win

Related FW 1.3.0
PLC Block ID 18
Inputs

32 32
Input Analog No -2 .. 2 Compared value
32 32
Input HIGH Analog No -2 .. 2 Upper window limit
32 32
Input LOW Analog No -2 .. 2 Lower window limit
Outputs

Output Binary No 0/1 Comparator output
Description
The block output is switched on whenever the input value is in the range defined by Lo and Hi levels.
Image 7.48 Principle of delay

Image 7.49 Configuration of Comp Time block
Note: All inputs and can be constants or values from controller.
Group: Time functions
Delay
PLC group Time functions
Related FW 1.3.0
PLC Block ID 33
Inputs

Input Binary No 0/1 Input signal to be delayed
Delay of the rising edge resp.
Input time 0 .. 214 748 364,7
Analog No pulse length generated by rising
up [s, m, h]
edge of the input
Delay of the falling edge resp.
Input time 0 .. 214 748 364,7
Analog No pulse length generated by falling
down [s, m, h]
edge of the input
Resets the output to logical 0. The
output remains in logical 0 until
Input reset Binary No 0/1 new rising edge appears on Input
(when Input reset is deactivated
already)
Outputs

Output Binary No 0/1 Output signal
Description
This block can operate in two operating modes (Delay mode, Pulse mode) = the block mode is defined by
the Pulse on edge checbox option - if checked, the Pulse mode is active.
Delay mode - the rising edge at the Output is generated with a delay of the Input time up lenght
when arising edge is detected on the Input. A falling edge at the Output is generated with a delay
of the Input time down length when a falling edge is detected on the Input. If the delayed falling

edge at the Output arrived before the delayed rising edge, then no pulse would be generated at
the Output.
Pulse mode - a pulse of Input time up length is generated at the Output when a rising edge is
detected, a pulse of Input time down length is generated at the Output when a falling edge is
detected.
Note: Because of 100 ms tact, the analog inputs are limited to resolution 0,1 s.
Note: If Input time up or Input time down value is <0, this input is internally set to zero.
Note: Use Pulse on edge option to choose between delay and pulse mode.
Image 7.50 Delay modes principles
Image 7.51 Configuration of Delay block

Timer
PLC group Time functions
Related FW 1.3.0
PLC Block ID 38
Inputs

The timer runs only if this input
Run Binary No 0/1
is active or not connected
This input reloads the timer to
Reload Binary No 0/1
the initial value
Reload
Analog No 0,0 .. 214 748 364,7 [s] Initial value of the timer
value
Outputs

Output Binary No 0/1 Timer output
Analog value that shows Actual Timer Value
Actual
Lowest available value from:
Timer Analog No N/A
Value <PLC Resource 1 (page 826) to
PLC Resource 16 (page 829)>
Description
The block performs countdown Timer according to the selected Timer mode and actual inputs values.
The Timer mode could be selected as:
ComAp timer mode = if the Timer block is to generate a periodic signal at its Output
Timer mode TP = if the Timer block is to generate a pulse signal of defined width at its Output
Timer mode TON = if the Timer block is to delay the rising edge of the Input by a defined time.
Timer mode TOFF = if the Timer block is to delay the falling edge of the Iutput by a defined time.
Timer mode ComAp
The Timer is counting down only when the Run is on and Reset is off. It is also reset to the Reload
value if it reaches 0 or Reset is enabled. The state of the binary Output is negated whenever the
Timer value is zero.
Timer mode TP

The Timer counts down when Run is on.The Reset accepts only the rising edge and is required to
load the Reload value to the actual Timer value. The Output is set as long as the Actual Timer Value
is not equal to 0 (the countdown is in progress).
Timer mode TON

The Timer starts counting down with the rising edge of Run. The falling edge of Run, like the rising
edge of Reset, reloads the Reload value to actual Timer value. The Output is set when the Actual
Timer Value is 0 (the countdown is finished).
Timer mode TOF

The Timer starts counting down with the falling edge of the Run. The rising edge of Run, like the rising
edge of Reset, reloads the Reload value to actual Timer value. The Output is set if the Actual Timer
Value is not equal to 0 (the countdown is in progress).
Image 7.52 Configuration of Timer block

Note: For ComAp Timer mode: if you want the Output to start at logic 0, check the First down option.
Otherwise, the Output will start at logical 1.
IMPORTANT: For ComAp Timer mode: if no inputs are connected and the First down option
is not checked, the Output is active.
Group: Math operations
Interpolation
PLC group
Related FW 1.3.0
PLC Block ID 34
Inputs
Input Type Range Function

32 32
Input Analog -2 .. 2 Input value
32 32
X1 Analog -2 .. 2 Low X limit of definition
32 32
X2 Analog -2 .. 2 High X limit of definition
32 32
Y1 Analog -2 .. 2 Low Y limit of definition
32 32
Y2 Analog -2 .. 2 High Y limit of definition
Outputs
Output Type Range Function

Output Analog Y1 .. Y2 Transformed value
Out of Range Binary 0/1 Closed when input is out of range <X1, X2>
Data Invalid Binary 0/1 Closed when value on analog output is invalid
Description
This block performs a linear transformation of the input. The transformation function is defined by two
pairs of points [X1, Y1] and [X2, Y2]. If the Input lies inside of the interval <X1, X2> the Output is given
by the conversion. If the Input is lying outside of this interval, Output is saturated either on high or low
limit given by Y1 or Y2 and Out of Range is closed. If any of the inputs gets invalid, Data Invalid is closed
and Output is set to invalid value. The Output, Y1, Y2 has resolution and dimension based on settings of
the block. The resolution and dimensions of the X1 and X2 is same as resolution of the Input.

Image 7.53 Principle of Interpolation
Image 7.54 Configuration of Interpolation block
AxB/C±D
PLC group
Related FW 1.3.0
PLC Block ID 51
Inputs
Input Abbr. Type Range Function

32 32
Input A A Analog -2 -1 .. +2 -1 First multiplicant
32 32
Input B B Analog -2 -1 .. +2 -1 Second multiplicant
32 32
Input C C Analog -2 -1 .. +2 -1 Divider
32 32
Input D D Analog -2 -1 .. +2 -1 Additive term (optional)
Outputs

Output Abbr. Type Range Function
Output O Binary
32 32
-2 -1 .. +2 -1 Result of the
operation
Set when Output is out of
Data
Err Binary 0/1 range or when dividing by zero
invalid
occurrs
Description
The block realizes the mathematical operation AxB/C±D. The operation ± is selected by Function
typeselector. In case of any invalid data on any of the inputs, the Output is set to invalid value and Data
Invalid is closed. The Output has resolution and dimension based on setting of the block.
Image 7.55 Configuration of Math AxB/C±D block
Math Fc.
PLC group
Related FW 1.3.0
PLC Block ID 17
Inputs

32 32
Input 1 Analog No -2 .. 2 Input 1
32 32
32 32
32 32
32 32
32 32
32 32
32 32
Outputs
32 32 Result of the mathematical

Output Analog No -2 .. 2
operation
Description
This block performs basic mathematical operations of 2 to 8 operands based on selected function.All
invalid inputs are ignored. If any configured input contains an invalid value and at least one configured
input is valid, the output has value counted from only valid configured inputs based on the selected
function. If all configured inputs are invalid output has an invalid value.
The Output has a Resolution and Dimension according to the block settings.
Function Output
ADD - Addition Input 1 + Input 2 + … + Input N
SUB - Substraction Input 1 - Input 2 - … - Input N
|SUB| - Absolute value of substraction ABS(Input 1 - Input 2 - … - Input N)
AVG - Average Input 1 + Input 2 + … + Input N) / N
MIN - Minimal value MIN(Input 1, Input 2, … ,Input N)
MAX - Maximal value MAX(Input 1, Input 2, … ,Input N)
Note: In case of AVG operation type the N is number of inputs with valid value.

Image 7.56 Configuration of Math Fc. block
Group: Regulators
PID
PLC group
Related FW 1.3.0
PLC Block ID 41
Inputs

32 32 Actual (controlled) value

Input Value Analog No -2 .. 2
"process value".
Requested 32 32 Required value "setpoint
Analog No -2 .. 2
Value value".
When PID Enable is not true
or there is an invalid value on
the Input Value of the
PID Enable Binary Yes 0/1 controller the output of the PID
block has a Init Value. If this
input is not connected the
controller is enabled.
Gain of the controller K. The
value 0 turns the controller off.
Negative values are not
Gain Analog No -100,00 .. 100,00
allowed, use the Reverse
Output parameter for such a
purpose.
Integration time constant of
Int Analog No 0,00 .. 120,00 s the controller Ti. The value 0
disables the integrating part.
Derivation time constant of the
Der Analog No 0,00 .. 4,00 s controller Td. The value 0
disables the derivating part.
The output value is in the Init
Value mode when PID Enable
is not active or there is an
invalid value on the Input
Value of the controller. The Init
Init Value Analog No -10 000 .. 10 000 Value is not limited by the Low
Limit and High Limit. Output
value in the Init mode is given
in a whole range of regulator
output (from -10 000 to 10
000).
Evaluation period (decimation
factor of default PLC period =
100ms). The period should be
adjusted according to the
Period Analog No 0,1 - 3250,0 s
response speed of the
system, e.g. longer period for
slower systems, a shorter
period for faster systems.
Reverse Binary Yes 0/1 Reverse Output:

off - higher controller output →
higher process value (default)
Output
on - higher controller output →
lower process value
This value defines the low limit
Low Limit Analog No -10 000 .. 10 000 (minimum) of the controller
output.
This value defines the high
High Limit Analog No -10 000 .. 10 000 limit (maximum) of the
controller output.
FeedForward 32 32
Analog No -2 .. 2 Feedforward control value.
Value
Feedforward control value
FeedForward ±38 ±38
Analog No -3,4 .. 3,4 weight Wff (default 0 %) [Float
Weight
data type]
Controller output value in
MANual mode. There is a
difference to the Init Value
(inactive PID block) = manual
Manual Value Analog No -10 000 .. 10 000
value is available only while
the PID Enable is true and is
limited by the High Limit and
Low Limit.
Manual Mode:
off - AUTomatic mode
MANual Mode Binary Yes 0/1
(default)
on - MANual mode
Outputs

Process value (controller output)
Output Analog No -10 000 .. 10 000
"control value".
Output Derivation of controller output
Analog No -10 000 .. 10 000
Velocity "speed of control value".
Control Control deviation (= "requested
Analog No -10 000 .. 10 000
Deviation value" - "actual value").
Out Low Controller output reaches the Low
Binary Yes 0/1
Limit Limit.
Out High Controller output reaches the High
Binary Yes 0/1
Limit Limit.
Description
The PID block is a PID controller, created by combining a proportional, an integration and a derivative
controller together (all forming the feed-back controller) with an optional forward control path (intended
for the feedforward control).

The main purpose of using a PID controller is to eliminate the entry control deviation by changing the
output control value (also called the manipulated value). The Control Deviation is evaluated as the
difference between the Requested Value (setpoint value) and the Input Value (process value). If the
controller is operating in automatic mode (MANual mode input is inactive), the action value is calculated
according to the control law equation. In the case of manual control (MAN mode input is active), the value
of the Manual Value is used instead. In both cases, the Output value is limited by the Low Limit and High
Limit limit values.
The PID block features::
Standard controller parameters (ISA Form).
Limitation of the control (process) value (block output).
Adjustable evaluation period.
Feed-forward input (with feed-forward gain parameter).
AUT/MAN switch with manual setpoint value.
RACT switch (reversing of control value polarity).
The function of the PID controller can be disabled by the PID Enable. While the regulator is disabled, the
output is set to a Init Value.
Note: Negative values of Gain are not allowed, use the Reverse Output input for such a purpose.
Note: There is a difference between Init Value (inactive PID block) and Manual Value - Manual Value
is available only while the PID Enable is true, MAN mode is enabled and is limited by the High Limit
and low Limit.
Rules for re-calculation

Parameter ComAp ISA form ComAp → ISA form ISA form → ComAp
isa_gain = comap_gain / comap_gain = isa_gain *
Gain [%] [-]
100.0 100.0
Int [%] [s] isa_int = 100 / comap_int comap_int = 100 / isa_int
Der [%] [s] isa_der = comap_der * 0.06 comap_der = isa_der / 0.06

Image 7.57 Configuration of PID block
Up/Down Ctrl Block
PLC group
Related FW 1.3.0
PLC Block ID 42

Inputs

-10 000 .. Control value (Input) = obviously velocity
Input Value Analog No
10 000 output of antecedent PID control block.
Control deviation (= "requested value" -
Control -10 000 .. "actual value") of antecedent block (usually
Analog No
deviation 10 000 PID controller). Works with Deadband
parameter.
When U/D Enable is not true or there is an
invalid value on the Input Value of the block,
U/D Enable Binary Yes 0/1 both the outputs (Output Up or Output Down)
has a value off. If this input is not connected
the controller is enabled.
Period of evaluation (decimation factor of
default PLC period 100ms). The time interval
between the start time of one pulse to start
0,1 ..
Period Analog No time of the next pulse. The period should be
3250,0 s
adjusted according to the Actuator Time and
shouldn't be shorter than the antecedent PID
controller evaluation period.
It is time that the actuator (servo, etc.) needs
Actuator 0,1 ..
Analog No for changing its position from fully closed to
Time 3250,0 s
fully open.
The minimum amount of time a relay is
Min On 0,1 ..
Analog No allowed to be closed (Output Up or Output
Time 3250,0 s
Down is on).
The minimum amount of time a relay is
Min Off 0,1 .. opened (Output Up or Output Down is off)
Analog No
Time 3250,0 s during the constant switching control range.
This time could be zero.
Deadband range (of input Control deviation,
-10 000 .. presumed symmetrical interval) → both
Deadband Analog No
10 000 outputs (Output Up or Output Down) are
inactive (off).
Antecedent controller output reaches the
Low Limit Binary Yes 0/1
Low Limit.
Antecedent controller output reaches the
High Limit Binary Yes 0/1
High Limit.

In MANual mode force the SCU to activate
Manual Up Binary Yes 0/1
(Manual Down must be inactive) Output Up.
Manual In MANual mode force the SCU to activate
Binary Yes 0/1
Down (Manual Up must be inactive) Output Down.
Manual Mode:
MANual
Binary Yes 0/1 off - AUTomatic mode (default)
Mode
on - MANual mode
Outputs

Output Up Binary Yes 0/1 Actuator control - Raise
Output
Binary Yes 0/1 Actuator control - Lower
Down
Description
The PLC block performs the function of Up/Down Control Unit (Relay Control block) with binary outputs
Up/Down and adjustable regulation period. The function of the block can be disabled by the binary input
U/D Enable. The Input signal corresponds to the speed (velocity = the change of the action variable)
output of the primary controller (Output Velocity of the PID block). The input signal value is expected in
range <-10000; +10000>.
If the Deadband parameter is non-zero, the switching of the outputs (Output Up or Output Down) is
suppressed for input signal Control Deviation smaller than the value of Deadband. The remaining
switching pulse length is still maintained for future evaluation.
If inputs Low Limit or High Limit (primary controller output reaches its limits - due to this the Input signal is
zero), the remaining pulse time is maintained accordingly to perform appropriate output (Output Up or
Output Down) switching.
By activating the binary input MAN, the inputs Manual Up or Manual Down are respected on the outputs
(Output Up or Output Down) - when both the Manual Up or Manual Down is active, both the outputs
Output Up and Output Down are inactive.
Use case:
The U/D Ctrl block (Up/Down relay Control block) is intended for use as an output stage of the
primary controller, converting its analog control action to up/down outputs (PWM controlled).
Block parameters are therefore set according to the characteristics of the actuator connected
onward.
The PID block and U/D Ctrl block connected together thus forms PID controller with relay contrlled
Up / Down outputs.
The U/D Ctrl block itself could also act as converting block from analog value to PWM modulated
signals.
If the U/D Ctrl block is operating in MANual mode, the manual setting of respective outputs
(Output Up / Output Down) is possible.

Image 7.58 Configuration of Up/Down Ctrl Block
Group: Ramp functions
Inc/Dec
PLC group
Related FW 1.3.0
PLC Block ID 22
Inputs

Rising edge increase value of Output
Increment Binary No 0/1
by 1
Risinge edge decrease value of
Decrement Binary No 0/1
Output by 1
Rising edge resets Output to Default
Reset Binary No 0/1
32 32
Maximum Analog No -2 .. 2 Maximum value of Output
32 32
Default Analog No -2 .. 2 Initial value of Output
Outputs

32
Output Analog No -2 .. Maximum Output value
Description
The block increments/decrements Output based on rising edge on Increment/Decrement.
If the Increment and Decrement edges arrive simultaneously, the Output value does not change.
If the counter value is at Maximum and incrementation is coming, the counter will be 0 again.
If the counter value is at 0 and decrementing is coming, the counter will have be at Maximum.
The Output can be reset by rising edge on Reset.
Note: If both the inputs Increment and Decrement are active, the Output value is not changed.
IMPORTANT: When the controller is powered off the Output value is not preserved.
Image 7.59 Configuration of Inc/Dec block
LowPassFlt
PLC group
Related FW 1.3.0
PLC Block ID 40
Inputs

32 32
Input Analog No -2 .. 2 Input Value
Time Constant of the
Tau Analog No 0,0 .. 60,0 [s]
filter
Outputs

32 32
Output Analog No -2 .. 2 Filtered Input
Description

The block performs the function of the first-order low pass filter. Typical usage of this function is filtering
of a value whose instantaneous value fluctuates rapidly around its mean, which is changing slower. The
Output has resolution and dimension based on setting of the block.
Image 7.60 Configuration of LowPassFlt block
Mov Avg
PLC group
Related FW 1.3.0
PLC Block ID 7
Inputs

32 32
Input Analog No -2 .. 2 Input Value
Filter Filter length = length of
Analog No 1 .. 16
Length sample train
Sampling Time interval between
Analog No 0,1 .. 3600,0 [s]
Period samples
Reset (clearing) of filter
Reset Binary No 0/1
internal memory
Filter processing enable
(If this input is not
Enable Binary No 0/1
connected the block is
enabled.)
Outputs

32 32
Output Analog No -2 .. 2 Filtered Input
Description
The block calculates the arithmetic mean of the N most recent samples of the input value with a
selectable sampling interval. The filter uses sample train (sequence of successive samples) for
computation of the filtered value as arithmetic average of N last samples of the input value. The simple

average computation is used: Typical usage of this function is filtering of a value whose instantaneous
value fluctuates rapidly around its mean, which is changing slower. The Output has resolution and
dimension based on setting of the block.
Image 7.61 Configuration of Moving Average block
Ramp
PLC group
Related FW 1.3.0
PLC Block ID 19
Inputs

32 32
Input Analog No -2 .. 2 Value to be ramped
32 32 Maximal rising rate of the

Up Analog No -2 .. 2
Output per second
32 32 Maximal lowering rate of the

Down Analog No -2 .. 2
Output per second
Outputs

32 32
Output Analog No -2 .. 2 Ramped value
Description
This block limits maximal rate of change of Output. The maximal rates Up and Down are adjustable
separately and ramping is based on enabled ramps. The Output has resolution and dimension based on
setting of the block.
Function Description
Enabled Up Output can be ramped only up.
Enabled Down Output can be ramped only down.
Enabled Up/Down Output can be ramped up and down.

Image 7.62 Configuration of Ramp block
Up/Down
PLC group
Related FW 1.3.0
PLC Block ID 20
Inputs

32 32
Limit 1 Analog No -2 .. 2 First limit of Output
32 32
Limit 2 Analog No -2 .. 2 Second limit of Output
Resets Output to Default
Reset Binary No 0/1
Output Value when active
Speed 32 32 Rising rate of Output per
Analog No -2 .. 2
Up second
Speed 32 32 Lowering rate of Output
Analog No -2 .. 2
Down per second
Up Binary No 0/1 Activates rising of Output
Activates lowering of
Down Binary No 0/1
Output
Default
32 32
Output Analog No -2 .. 2 Initial value of Output
Value
Outputs

Output Analog No Limit 1 .. Limit 2 Output value

Description
This block works as an analog ramp controlled by binary inputs Up and Down with a defined rate of
increase/decrease.
The ramp speed is adjusted by Speed Up and Speed Down.
The Output limitation is set by Limit 1 and Limit 2. The default value of Output is set by Default Output
Value.
Activate Reset to reset Output to Default Output Value. The Output has resolution and dimension
based on setting of the block.
IMPORTANT: If both the inputs Up and Down are active, the Output is set to Default
Output Value.
Image 7.63 Configuration of Up/Down block
Group: Other functions
Analog Switch 8
PLC group Others
Related FW 1.3.0
Inputs

32 32
Input 1 Analog No -2 .. 2 Input value 1
32 32
Input 2 Analog No -2 .. 2 Input value 2
32 32 Input value 3
Input 3 Analog No -2 .. 2
(optional)
32 32 Input value 4
(optional)
32 32 Input value 5
(optional)
32 32 Input value 6
(optional)
32 32 Input value 7
(optional)
32 32 Input value 8
(optional)
Input SW 1 Binary No 0/1 Switch input 1
Outputs

Switch output
32 32
Output Analog No -2 .. 2 according to the SW 1,
SW 2 and SW 3
Description
The block works as an analog multiplexer. The output value could be selected from up to 8 inputs
according to the 'Input SW 3', 'Input SW 2' and 'Input SW 1' state is appropriate input value copied to the
output, see the table below.
Input SW 3 Input SW 2 Input SW 1 Output

0 0 0 Input 1
0 0 1 Input 2
0 1 0 Input 3
0 1 1 Input 4
1 0 0 Input 5
1 0 1 Input 6
1 1 0 Input 7
1 1 1 Input 8

Image 7.64 Configuration of Analog Switch 8 block
Bit Sum 16
PLC group Others
Related FW 1.3.0
PLC Block ID 53
Inputs


Outputs

Output value = sum of active inputs
Output 1 Analog No 0 .. Max [-]
(InputX has value true)
Output value = sum of inactive inputs
Output 0 Analog No 0 .. Max [-]
(InputX has value false)
Description
The PLC block performs active/inactive inputs summation and it gives analog value output as a summary
of activated Binary input signals or vice versa as secondary analog output summary of deactivated
Binary input signals.

Image 7.65 Configuration of Bit Sum 16 block
Circuit Breaker
PLC group Others
Related FW 1.3.0
PLC Block ID 58
Inputs

According to the Close/Open value
Close/Open C/O Binary 0/1 the circuit breaker closes/opens
(level control)
The rising edge of the Close signal
Close Close Binary 0/1
forces the breaker to close (edge

control)
The rising edge of the Open signal
Open Open Binary 0/1 forces the breaker to open (edge
control)
Feedback from breaker (aux.)
Feedback FB Binary 0/1
contactor
Negative Feedback NFB Binary 0/1 Inverted Feedback
Disabled Dis Binary 0/1 Control (closing) disabled
Breaker (spring) charged (has
Charged Chrg Binary 0/1
tension)
Outputs

ON Coil ON Binary 0/1 On (switching) coil
OFF Coil OFF Binary 0/1 Off (tripping) coil
UV Coil UV Binary 0/1 Under voltage coil
Output Close/Open C/O Binary 0/1 Close / Open signal
Status Close/Open Status Binary 0/1 State of circuit breaker control
Fail to Close FtC Binary 0/1 Failed to close
Description
This block performs general Circuit Breaker (CB) control based on the state machine principle.
Inputs
Close/Open: Input for level control of breaker close/open control. Since the block contains a state
machine and the possibility of impulse (edge) control is required, an edge response is also
introduced for level control as well, i.e., the rising edge is interpreted as a CB Close request and a
falling edge as a CB Open request.
Close: The request to switch on (Close CB) - minimum pulse length is 200 ms - manual issue,
edge responsive.
Open: The request to switch off (Open CB) - minimum pulse length is 200 ms - manual issue,
edge responsive.
Feedback: Feedback from auxiliary breaker contacts, not required to configure. (If not configured,
the mismatch between requested and breaker state is not evaluated; it is assumed that the
breaker is currently in the desired state).
Feedback Negative: It is not required to be configured together with the CBFeedback input.
However, if Feedback Negative is configured, the Feedback input must be configured too. Then,
not only the mismatch between the desired state and the feedback is always evaluated, but also
the mismatch between the two feedbacks.
Disable: If the CB is disconnected (opened), the Disable input will blocks its switching (closing). If
the CB has already been switched on, this input does not open it. It is not necessary to configure
this input = if the input is not configured, it is evaluated as inactive.
Charged: This input has the same function (but in inverse logic) as CBDisabled, it is used only in
conjunction with information about the breaker spring tension. Configuration of the input is not
required; if the input is not configured, it is evaluated as active.

Outputs
ON Coil: Switching signal for ON (closing) CB coil - pulse lenght of 5 sec (the feedback
confirmation is expected within this 5 sec).
OFF Coil: Tripping signal for OFF (opening) CBcoil - pulse lenght of 5 sec (the feedback
confirmation is expected within this 5 sec).
UV Coil: Level signal for UV (under voltage) CB coil = remains on till the CB should be opened.
Output Close/Open: Request signal for closing/opening the circuit breaker (level control).
Status Close/Open: Information about the breaker status based on the evaluation of the
Feedback and/or Feedback Negative signals.
Failed To Close: In case of a failed attempt to close the CB (second attempt), a 5s pulse is
generated at the output. A user protection may be configured on it.
Failed To Open: In case of a failed attempt to open the CB, a 5s pulse is generated at the output.
A user protection may be configured on it.
Other Fail: Information about other non-correlated CB events (states). A 5s pulse is generated at
the breaker output in the event of a mismatch between Feedback and Feedback Negative
and/or where Feedback is lost or, conversely, Feedback is set in a situation where a change in
CB state is unexpected.
Image 7.66 Configuration of Circuit Breaker block
« back to List of PLC blocks

Convert
PLC group Others

Related FW 1.3.0
PLC Block ID 52
Inputs

32 32
Input Analog No -2 .. 2 Input value
Outputs
32 32 Converted Input
value
The attribute of
Output Binary Yes 0/1 invalid data on
output
Description
The block converts the Input based on selected resolution and dimension, and reflects it to the Output.
Dimension is converted based on user configuration without any extra recalculation. Resolution is
converted and recalculation is used.
Example: If the input is 100,5 W and the convert block is used to convert dimensions to kW with
resolution 1, the output shows 101 kW.
Note: Conversion is done to Integer32, if the input value is out of Integer32 range, output value is set to
invalid status and error output is activated.
Image 7.67 Configuration of Convert block

Counter
PLC group Others

Related FW 1.3.0
PLC Block ID 13
Inputs

Input at which the edges
Input Count Up Binary No 0/1
are counted
32 Counter value limit for

Input Preset Limit Analog No 0 .. 2
activation of the output
Input Clear Binary No 0/1 Reset input
Outputs

Output is activated when the counter value
Output Binary No 0/1
exceeds the limit
Analog value that shows Actual Counter
Actual Value
Counter Analog No N/A Lowest available value from:
Value <PLC Resource 1 (page 826) to
PLC Resource 16 (page 829)>
Description
The block works as a counter of edges (selectable rising, falling or both) with reset input and adjustable
counting limit. The maximal counter value is 2 147 483 647. The counter value is lost when the controller
is switched off. The output is activated when the counter value is equal to or higher than Input Preset
Limit and stays active until the block reset is done using Input Clear. Activating of the Input Clear resets
the counter value to 0 and deactivates the output. Holding the Input Clear active blocks the counting.
IMPORTANT: The counter value is lost when the controller is switched off.
Image 7.68 Configuration of the Counter block

Comp. 4
PLC group Others
Related FW 1.3.0
PLC Block ID 49
Inputs

Bit 0,4,8,12,16,20,24,28 -
Input 1 Binary Yes 0/1
according to selected group of bits.
Bit 1,5,9,13,17,21,25,29 -
Bit 2,6,10,14,18,22,26,30 -
Bit 3,7,11,15,19,23,27,31 -
Outputs

-2 147 483 647 .. 2 147 483 Value to be
Output Analog No
647 "composed" to bits
Description
The block converts selected input bits to analog form and provides the output analog value.The resulting
quad of bits is placed in the Output value within the selected bit range (Bits).
Image 7.69 Configuration of Comp. 4 block

Comp. 16
PLC group Others
Related FW 1.3.0
PLC Block ID 50
Inputs

According to selected group of
bits.
bits.
... ... ... ... ...
bits.
bits.
Outputs

-2 147 483 647 .. 2 147 483 Value to be
Output Analog No
647 "decomposed" to bits
Description
The block converts selected input bits to analog form and provides the output analog value.It is possible
to select lower bits 0-15 or upper bits 16-31 so it is possible to compose 32 bit value by using of two
composers.

Image 7.70 Configuration of Comp. 16 block
Decomp. 4
PLC group Others
Related FW 1.3.0
PLC Block ID 24
Inputs

32 32
Input Analog No -2 .. 2 Value to be "decomposed" to bits
Outputs

Bit 0,4,8,12,16,20,24,28 -
Output 1 Binary Yes 0/1
Bit 1,5,9,13,17,21,25,29 -

Bit 2,6,10,14,18,22,26,30 -
Bit 3,7,11,15,19,23,27,31 -
Description
The block converts the input analog value to binary form and provides selected bits as binary
outputs.The input four bits are selected by bit range selection (Bits).
Image 7.71 Configuration of Decomp. 4 block
Decomp. 16
PLC group Others
Related FW 1.3.0
PLC Block ID 48
Inputs

32 32
Input Analog No -2 .. 2 Value to be "decomposed" to bits
Outputs

bits.
bits.
... ... ... ... ...
bits.
bits.
Description
The block converts the input analog value to binary form and provides selected bits as binary outputs.It is
possible to select lower bits 0-15 or upper bits 16-31 so it is possible to decompose 32 bit value by using
of two decomposers.
Image 7.72 Configuration of Decomp. 16 block

Differ
PLC group Others

Related FW 1.3.0
PLC Block ID 55
Inputs

32 32
Input Analog No -2 -1 .. +2 -1 Input value
Clear Binary Yes 0/1 Clear (reset) internalvalues
Sampling Sampling period (interval
Analog No 0,1 - 3600,0 s
Interval between samples)
Outputs

Difference-by-Time of Input
/ 32 32
Analog No -2 -1 .. +2 -1 values evaluated over four
Difference
samples
The Input value sample
32 32 delayed one step (given by
Z-1 Analog No -2 -1 .. +2 -1
the sampling interval
parameter)
Description
The block performs difference-by-time evaluation of analog input. Internally the block have memory for 4
consecutive values (sample train), a one-step delayed sample is available at output Z-1. The time
interval between the samples is a block parameter and is selected by the user during the block
configuration. The sampling interval can be multiple of 0,1 sec only.
Output is calculated from four successive internal values based on this equation :
Image 7.73 Configuration of the Differ block

Heartbeat
PLC group Others
Related FW 1.3.0
PLC Block ID 43
Inputs

Incoming binary (rising) edge leads to
reset Heartbeat counter. If there is
Input 1 Binary Yes 0/1 configured Input 2, the Reset action is
dependent on the selected operation
between inputs 1 and 2 (OR/ XOR).
The optional input signal, if it is
configured, the Reset action is
dependent on the selected operation
between inputs 1 and 2 (OR / XOR).
HeartBeat checking/counting period
(max. approx. 100 min). It should be at
Checking
Analog No 0,2 .. 6500,0 s least twice the incoming checked signal
Period
period (at least 2 PLC execution
periods).
Reset Active value of this input clear output to
Binary Yes 0/1
Output default (off) value.
Heartbeat block enable. When Enable is
not active or there is an invalid value on
Input 1 of the block, the output (Output)
Enable Binary Yes 0/1 has a value off, the internal Heartbeat
counter is reset to the default value. If
this input is not connected the block is
enabled.
Outputs

Output Binary Yes 0/1 Output value
Description
The PLC block performs Heart Beat signal checking.
The Checking Period parameter specifies both the Heart Beat checking period and the reload value
of the internal counter. The resolution of the counter is 0,1 seconds.
The internal counter is re-set to the Checking Period value in the cases (Reset Action):
The Enable input is false.
The internal counter reaches the zero value.
The Heart Beat check operation is valid:
On Input 1 is detected rising edge (only Input 1 is configured) or on the Input 2 is detected rising

edge (only Input 2 is configured).
Both Input 1 and Input 2 are configured:
OR mode:
If the rising edge is detected either on Input 1 or Input 2.
XOR mode:
If the rising edge is detected on Input 1 and followed by detecting the falling edge on Input
2.
If the falling edge is detected on Input 2 and followed by detecting the rising edge on Input
1.
The above conditions must be met before the counter counts down to zero to ensure that the
incoming heartbeat signal is live. The Output binary signal is set (on) if the internal counter counts
down to zero. If the Reset Output input is configured and the input is active (Reset Output is set), the
Output is cleared to the default (off) value. If the Reset Output input is not configured, the Output can
be cleared by any successful check operation described above.
If the Enable input is configured and the input is inactive (Enable is reset), the internal counter is
reloaded to the Checking Period value, counting stops and the Output is cleared to default (off) value.
If the Enable input is not configured or the input is active (Enable is set), the internal counter is
counting down and the Heart Beat checking functionality is excuted.
Image 7.74 Configuration of Heartbeat block

Hold
PLC group Others

Related FW 1.3.0
PLC Block ID 37
Inputs

32 32
Input Analog No -2 .. 2 Input value
Hold Binary No 0/1 Input triggering the function
Outputs

32 32
Output Analog No -2 .. 2 Hold output
Description
The block is holding Input value based on value of Hold and selected mode. The Output has resolution
and dimension based on setting of the block.
Mode Description
The block behaves like analog memory. Input Hold behaves like the reload trigger and
Edge
reacts on rising edge. The initial value of the Output after restart of the controller is 0.
The block is like a mirror of the Input while the Hold is inactive. The value of Output is
Level
latched at the last value while Hold is active.
Image 7.75 Principle of the Hold modes

Image 7.76 Configuration of the Hold block
PF Conv
PLC group Others
Related FW 1.3.0
PLC Block ID 57
Inputs

Input Power 32 32
* PF Analog -2 -1 .. +2 -1 Power Factor
factor
PF ASCII annotation:
32 32 "L" = inductive, lagging; "R" =
Input Character Char Analog -2 -1 .. +2 -1
resistive; "C" = capacitive,
leading
Outputs

Output Power 32 32
PF Analog -2 -1 .. +2 -1 Power Factor
Factor
PF ASCII annotation:
32 32 "L" = inductive, lagging; "R" =
Output Character Char Analog -2 -1 .. +2 -1
resistive; "C" = capacitive,
leading
Load type indication: 0 =
32 32
Output Load Type Type Analog -2 -1 .. +2 -1 inductive, lagging; 1 =
capacitive, leading
32 32
Data Invalid Err Analog -2 -1 .. +2 -1 Ramped value
Description
This block perform format conversion of Input Power Factor to Output Power Factor format. The
conversion type is set using the Conversion option.
There are three power factor formats:

ComAp1 format: power factor value in the range <0,000 ; 2,000>
• value in the interval <0,000; 1,000) denotes the lagging (L) power factor
• value in the interval (1,000; 2,000> denotes the leading (C) power factor
• value 1,000 denotes the resistive (R) power factor
ComAp2 format: power factor value in the range <0,000; 1,000> + additional load character value
{'L', 'R', 'C'} = 8 bit character
• value in the interval <0,000; 1,000) + 'L' character denotes the lagging (L) power factor
• value in the interval <0,000; 1,000) + 'C' denotes the leading (C) power factor
• value 1,000 + 'R' character denotes the resistive (R) power factor
R = 82 ASCII / L = 76 ASCII / C = 67 ASCII
EEI format: power factor value in the range <-1,000 ; 1,000>
• value in the interval <-1,000; 0,000) denotes the lagging (L) power factor
The following figure explains the relations between the power factor formats used.
Image 7.77 Power factor formats ranges

Image 7.78 Configuration of PfConv block
Poly Appx
PLC group Others
Related FW 1.3.0
PLC Block ID 47
Inputs

32 32
Input 1 Analog Yes -2 .. 2 Input value
Low Limit Analog Yes Same as Input Low limit of output value
High Limit Analog Yes Same as Input High limit of output value
Outputs
32 32 Result of the polynomial

approximation of input value.
Description
The PLC block performs the polynomial approximation function of the input variable by calculating a
polynomial (up to 6th order). The result is limited by lower and upper bound parameters (limitation) and
passed to the output variable.

Image 7.79 Configuration of Polynomial Approximation block
PWR Calc
PLC group Others
Related FW 1.3.0
PLC Block ID 56
Inputs

Input Active 32 32
P Analog -2 -1 .. +2 -1 Active power
Power
Input Reactive 32 32
Q Analog -2 -1 .. +2 -1 Reactive power
Power
Input Apparent 32 32
S Analog -2 -1 .. +2 -1 Apparent power
Power
Input Power 32 32
PF Analog -2 -1 .. +2 -1 Power factor
Factor
32 32 Load type (0 = inductive,

Input Load Type Type Binary -2 -1 .. +2 -1
lagging; 1 = capacitive, leading)
Outputs

Output Active 32 32
P Analog -2 -1 .. +2 -1 Active power
Power
Output Reactive 32 32
Q Analog -2 -1 .. +2 -1 Reactive power
Power
Output Apparent 32 32
S Analog -2 -1 .. +2 -1 Apparent power
Power
Output Power 32 32
PF Analog -2 -1 .. +2 -1 Power Factor
Factor
Output Deformed 32 32 Deformed Power (only with all
D Analog -2 -1 .. +2 -1
Power powers P, Q, S are provided)
32 32
Data Invalid Err Binary -2 -1 .. +2 -1 Data invalid
Description
The block calculates the output power variable values from the selected input values (for example: needs
of Q and PF from provided P and S). The calculation type is set using the Calculation option, the
calculation of the remaining output values is performed if the necessary 2 analog inputs are set correctly.
Note: The Power Factor input value is expected in the ComAp PF1 format (value in the range <0,000 ;
2,000>) with following meaning:
• value in the interval <0,000; 1,000) denotes the lagging (L) power factor
Note: The block performs the Resolution conversion.
Oper P Q S PF D
In
P,Q
P Q not valid
Out
S,PF
In
P,S
P S not valid
Out
Q, PF
In
P,PF
P PF not valid
Out
Q,S

In
Q,S
Q S not valid
Out
P,PF
In
Q,PF
Q PF not valid
Out
P,S
In
P,Q,S
P Q S
Out
D,PF
Image 7.80 Configuration of PWR Calc block

Validator
PLC group Others

Related FW 1.3.0
PLC Block ID 54
Inputs

32 32
Validate Analog No -2 -1 .. +2 -1 Input value
32 32
Replace Analog No -2 -1 .. +2 -1 Replacement value
Force Binary Yes 0/1 Forcing of replacement
Outputs

Output set to Validate or Replace
32 32
Output Analog No -2 -1 .. +2 -1 based on the value of Validate
and/or Force inputs
Validate input has an invalid
Invalid Binary Yes 0/1
value
Description
Block checks (validate) if the input value has a valid value (i.e. is not marked with Invalid Flag). The
Output value is determined according to the following rules:
Function Validate
Input Validate Input Force Output O Output Err
Valid value 0 Validate 0
Invalid value 0 Replace 1
Valid value 1 Replace 0
Invalid value 1 Replace 1
Image 7.81 Configuration of Validator block

9.2 Alarms
What alarms are:
The controller evaluates two levels of alarms. For more information see Alarm Management on page 122.
9.2.1 Alarm levels in the controller

9.2.4 Other alarms 1132
9.2.2 Alarms level 1

What alarms level 1 are:
The level 1 alarm indicates that a value or parameter is out of normal limits, but has still not reached critical
level.

List of alarms level 1
Warning 1083 Wrn P(Um) Fail 1092 ALI Bus Ph L1 Inverted 1104
Wrn Alarm e-mail 1 Fail 1083 Wrn PF Control Fail 1093 ALI Bus Ph L2 Inverted 1104
Wrn Alarm e-mail 2 Fail 1083 Wrn PF/Q IMP/EXP Fail 1093 ALI Bus Ph L3 Inverted 1104
Wrn Alarm e-mail 3 Fail 1083 Wrn PF(Pm) Fail 1094 ALI Bus Ph Rotation
Wrn Alarm e-mail 4 Fail 1083 Wrn PVCB Fail To Close 1094 Opposite 1105
Wrn Backup Controller Wrn PVCB Fail To Open 1095 ALI BCB Closing Is
Failed 1084 Blocked 1105
Wrn PVCB Fail 1095
Wrn Backup Not Ready 1084 ALI CAN Mode
Wrn Q Control Fail 1096
Wrn Battery Overvoltage 1084 Inconsistency 1105
Wrn Q&U Protection 1097
Wrn Battery ALI Daily Battery Cycles
Wrn Q(P) Fail 1097
Undervoltage 1085 Reached 1106
Wrn Q(Um) Fail 1098
Wrn Brute Force ALI BESS Ph L1 Inverted 1106
Wrn Qref/Ulim Fail 1098
Protection Active 1085 ALI BESS Ph L2 Inverted 1106
Wrn Redundant CAN
Wrn CAN2 Empty 1085 ALI BESS Ph L3 Inverted 1106
inconsistency 1099
Wrn Default Password 1086 ALI BESS Ph Rotation
Wrn RTC Battery Flat 1099
Wrn ECU Communication Opposite 1106
Wrn Reverse
Fail 1086 ALI Redundant CAN
Synchronization Fail 1100
Wrn Event e-mail 1 Fail 1086 Error 1107
Wrn SD Card Failed 1100
Wrn Event e-mail 2 Fail 1086 ALI SD Card Not
Wrn SD Card File System Compatible 1107
Wrn Event e-mail 3 Fail 1087 Failed 1100
ALI SD Card In Slot 1108
Wrn Event e-mail 4 Fail 1087 Wrn SNMP TRAP 1 Fail 1100
ALI SD Card Full 1108
Wrn Frequency Wrn SNMP TRAP 2 Fail 1101
Regulation Limit 1087 ALI SD Card
Wrn SOC High Alarm 1101 Formatting/Mounting 1108
Wrn Hot Swap
Wrn SOC Low Alarm 1101 ALI Mains Ph L1 Inverted 1109
Configuration Incorrect 1087
Wrn Soft Transfer Fail 1102 ALI Mains Ph L2 Inverted 1109
Wrn Hot Swap Data
Synchro Fail 1088 Wrn Stop Fail 1102 ALI Mains Ph L3 Inverted 1109
Wrn Load IMP/EXP Fail 1088 Wrn SW Key CAN ALI Mains Ph Rotation
Redundancy Error 1102 Opposite 1109
Wrn Long Term History
Fail 1089 Wrn SW Key Hot Swap ALI Start Blocking 1110
Error 1102
Wrn Master Controller ALI Wrong Power Format 1110
Failed 1089 Wrn Test UPQF 1103
Alarm List + History
Wrn MCB Fail 1089 Wrn Unsupported PMS Indication 1110
Mode 1103 AHI SyncNotAllowed 1110
Wrn MCB Fail To Close 1090
Wrn Voltage Regulation
Wrn MCB Fail To Open 1091 History Record Only 1111
Limit 1103
Wrn Override All Sd 1091 Hst Pave 1111
Wrong PLC Configuration1103
Wrn Password reset e- Hst ROCOF 1 1111
Alarm Only 1104
mail addr is not set 1092 Hst ROCOF2 1111
Alarm List Indication 1104
Wrn P for Q Fail 1092 Hst ROCOF3 1111

Hst ROCOF4 1112
Hst Vector Shift 1112
6 back to Alarms

Warning
Wrn Alarm e-mail 1 Fail
Alarm Type Warning (page 198)

Alarmlist message Wrn Alarm e-mail 1 Fail
Alarm evaluated All the time
Alarm ID 815
The alarm indicates that there was a request to send an alarm email to email
address which is adjusted by setpoint E-mail Address 1 (page 412) and email
Description
wasn’t send.
This alarm has FPS - FIXED PROTECTIONS STATES 7 (PAGE 1023).
6 back to List of alarms level 1

Alarm ID 816
Description
wasn’t send.

Alarm ID 817
Description
wasn’t send.


Alarm ID 818
Description
wasn’t send.
Wrn Backup Controller Failed

Alarmlist message Wrn Backup Controller Failed
Alarm evaluated Only if Hot Swap Redundancy (page 364) != Disabled
Alarm ID 1289
This alarm is activated on Hot Swap Redundancy (page 160) master
Description controller when master controller does not detect the HOT SWAP HEARTBEAT
(PAGE 952) signal from backup.
Wrn Backup Not Ready

Alarmlist message Wrn Backup Not Ready
Alarm evaluated Only if Hot Swap Redundancy (page 364) = Master
Alarm ID 1146
This alarm is related to the Hot Swap Redundancy (page 160). It is activated
when the BACKUP controller has announced any 2nd level alarm while the
Description MASTER controller does not indicate such alarm.
In this case, the BACKUP is unable to take over the control if Master controller
fails. This is a marginal issue and may be caused due to wrong configuration.
Wrn Battery Overvoltage

Alarmlist message Wrn Battery Overvoltage
Alarm ID 941
This alarm is activated when Battery Voltage (page 759) is over Battery
Overvoltage (page 382) for period longer than Battery <> Voltage Delay
Description
(page 382).
This alarm has FPS - FIXED PROTECTIONS STATES 1 (PAGE 1017)

Wrn Battery Undervoltage

Alarmlist message Wrn Battery Undervoltage
Alarm ID 940
This alarm is activated when Battery Voltage (page 759) is bellow Battery
Undervoltage (page 382) for period longer than Battery <> Voltage Delay
Description
(page 382).
Wrn Brute Force Protection Active

Alarmlist message Wrn Brute Force Protection Active
Alarm ID 1237
This alarm is activated when account break protection detects possible attack
and at least one account is blocked according to Account break protection
(page 227) rules.
Note: In case that the alarm stays active even that it should already be
Description inactive, do the following to get rid of it:
1. Disconnect all peripheries (displays, ethernet, etc.)
2. Wait for 20 minutes - the alarm should become inactive
3. Connect with InteliConfig using USB - Quick connection
4. Acknowledge the alarm
Wrn CAN2 Empty

Alarmlist message Wrn CAN Intercontroller Empty
Alarm evaluated Only if CAN Intercontroller Empty Check (page 390) = Enabled
Alarm ID 46
This alarm is activated when controller is alone on Intercontroller CAN
(⑧ CAN2A (page 47) and/or ⑦ CAN2B (page 47) ) and setpoint CAN
Description
Intercontroller Empty Check (page 390) = Enabled.

Wrn Default Password

Alarmlist message Wrn Default Credentials
Alarm ID 1071
This alarm is active until the default password for administrator account is
Description
changed.
Wrn ECU Communication Fail

Alarmlist message Wrn ECU Communication Fail
With configured LBO ECU POWER RELAY (PAGE 943) - only when this LBO is
Alarm evaluated active.
Without configured LBO ECU POWER RELAY (PAGE 943) - all the time
This alarm occurs when an ECU is configured, but the communication with the
Description
ECU is not established or has dropped out.
Wrn Event e-mail 1 Fail

Alarmlist message Wrn Event e-mail 1 Fail
Alarm ID 734
The alarm indicates that there was a request to send an event email to email
Description address which is adjusted by setpoint E-mail Address 1 (page 412) and email
wasn’t send.

Alarm ID 735
wasn’t send.


Alarm ID 736
wasn’t send.

Alarm ID 737
wasn’t send.
Wrn Frequency Regulation Limit

Alarmlist message Wrn Frequency Regulation Limit
Alarm evaluated While BESS is running
Alarm ID 151
This alarm is activated when Frequency Regulator Output (page 754) stays
close to Frequency Governor Low Limit (page 458) or Frequency
Description Governor High Limit (page 458) for at least 2 seconds and will remain active
as long as the cause is present.
Wrn Hot Swap Configuration Incorrect

Alarmlist message Wrn Hot Swap Configuration Incorrect
Only if Hot Swap Redundancy (page 364) != Disabled and Wrn SW Key Hot
Alarm evaluated
Swap Error (page 1102) is not present in the alarmlist

Alarm ID 1465
This alarm is activated when Hot Swap Redundancy (page 160) is missing
the correct configuration of mandatory LBI and LBO.
List of mandatory objects:
LBI HOT SWAP CTRL BLOCK (PAGE 895)
Description LBI HOT SWAP HEARTBEAT DETECT (PAGE 895)

LBO HOT SWAP SWITCH (PAGE 952)
LBO HOT SWAP HEARTBEAT (PAGE 952)
IMPORTANT: All mandatory objects have to be configured to physical

input/output of the controller.
Wrn Hot Swap Data Synchro Fail

Alarmlist message Wrn Hot Swap Data Synchro Fail
Alarm ID 1426
This alarm is activated when communication between Hot Swap Redundancy
(page 160) master and backup controllers failed.This can be caused because
Description
of wrong configuration or wiring. While this alarm is active the backup controller
doesn't have the data which needs for the smooth transition.
Wrn Load IMP/EXP Fail

Alarmlist message Wrn Load IMP/EXP Fail
Alarm evaluated Only if Application Mode (page 777) = MPTM
Alarm ID 1448
This alarm is active when Load Control PTM Mode (page 345) = Imp/Exp but
Mains Measurement P is unavailable.
When this alarm is active, load is controlled as if Load Control PTM Mode
(page 345) = Baseload.
Alarm is caused by:
Description Mains Measurement P (page 357) = None
Mains Measurement P (page 357) = Analog Input and
LAI MAINS MEASUREMENT P (PAGE 992) is not configured
Value from LAI Mains Measurement P (page 357) has Invalid flag
(page 652)

Wrn Long Term History Fail

Alarmlist message Wrn Long Term History Fail
Alarm evaluated Only when Long Term History (page 393) = Enabled
Alarm ID 1281
This alarm is activated when Long Term History (page 393) = Enabled but for
Description any reason it is not possible to write the history onto the SD card.
Wrn Master Controller Failed

Alarmlist message Wrn Master Controller Failed
Alarm ID 1288
This alarm is activated on Hot Swap Redundancy (page 160) backup
Description controller when backup controller does not detect the HOT SWAP HEARTBEAT
(PAGE 952) signal from master.
Wrn MCB Fail

Alarmlist
Wrn MCB Fail
message
Alarm
Only if MCB Control Mode (page 361) = Internal
evaluated
Related
MPTM
applications
Alarm ID 90
This alarm is activated when there is a problem with position of the circuit breaker.
LBI MCB FEEDBACK (PAGE 902) does not match expected position given by LBO
MCB CLOSE/OPEN (PAGE 959).
There is a mismatch between LBI MCB FEEDBACK (PAGE 902) and MCB
FEEDBACK NEGATIVE (PAGE 903).
Description
Self-opening of breaker with mains parameters without limits – not
considered as fault, MCB open command is issued when Mains fails according to
the setpoint MCB Opens On (page 1).
Self-closing of breaker with mains parameters with limits – not considered
as fault, MCB close command is issued after MCB Close Delay (page 526).

Image 7.82 MCB Fail
Wrn MCB Fail To Close

Alarmlist
Wrn MCB Fail To Close
message
Alarm
evaluated
Related
MPTM
applications
Alarm ID 1553
This alarm is activated when there is a problem with circuit breaker position while
closing.
LBO MCB CLOSE/OPEN (PAGE 959) closed but LBI MCB FEEDBACK (PAGE 902)
Description
did not closed in 2 seconds.
Self-closing of breaker with mains parameters with limits – not considered
as fault, MCB close command is issued when Mains fails.

Image 7.83 MCB Fail To Close
Wrn MCB Fail To Open

Alarmlist
Wrn MCB Fail To Open
message
Alarm
evaluated
Related
MPTM
applications
Alarm ID 1552
opening.
LBO MCB CLOSE/OPEN (PAGE 959) opened but LBI MCB FEEDBACK (PAGE 902)
did not opened in 2 seconds.
Self-opening of breaker with mains parameters without limits - not
considered as fault, MCB open command is issued when Mains fails.
Description
Image 7.84 MCB Fail To Open
Wrn Override All Sd

Alarmlist message Override All Sd
Alarm evaluated Only if LBI SD OVERRIDE (PAGE 915) is configured
Alarm ID 674
This alarm is activated when LBI SD OVERRIDE (PAGE 915) is closed.
Description
Wrn Password reset e-mail addr is not set

Alarmlist message Wrn Password reset e-mail addr is not set
Alarm ID 1292
This alarm is active when password reset e-mail address is not filled. Fill out the
Description
password reset e-mail via InteliConfig to remove this alarm.
Wrn P for Q Fail

Alarmlist message Wrn P for Q Fail
Alarm evaluated Only when P For Q Limitation (page 547) = Enabled
Related applications MPTM
Alarm ID 1106
This alarm indicates P for Q Fail which can be caused by wrongly configured
curves:
P FOR Q UQ C (PAGE 869)
Description P FOR Q UQ L (PAGE 868)

P FOR Q PQ C (PAGE 871)
P FOR Q PQ L (PAGE 870)
Wrn P(Um) Fail

Alarmlist message Wrn P(Um) Fail
Alarm evaluated Only if P(Um) (page 544) != Disabled
Alarm ID 1255
This alarm indicates Power Regulation Based On Actual Mains Voltage
Description
(page 297) fail. Application Curve P(Um) (page 862) is either not configured or

invalid.
Wrn PF Control Fail

Alarmlist message Wrn PF Control Fail
Only when PF/Q Request Source (page 350) = Analog External Value, PF/Q
Control PTM Mode (page 349) = PF Control and Breaker state (page 778) =
Alarm evaluated
ParalOper

Alarm ID 1053
This alarm indicates PF Control Fail which can be caused by:
If PF/Q Regulation Type (page 351) = Base PF/Q Control
LAI PF CONTROL: ANEXT BASE PF (PAGE 992) is not configured
Value from LAI PF CONTROL: ANEXT BASE PF (PAGE 992) is out of
sensor range (i.e. "###")
If PF/Q Regulation Type (page 351)
Description LAI PF CONTROL: ANEXT IMP/EXP PF (PAGE 993) is not configured
Value from LAI PF CONTROL: ANEXT IMP/EXP PF (PAGE 993) is out
of sensor range (i.e. "###")
When this alarm is active, BESS Required PF (page 757) is taken from Base
Power Factor (page 352) or Import Power Factor (page 352), based on
setpoints setting.
Wrn PF/Q IMP/EXP Fail

Alarmlist message Wrn PF/Q IMP/EXP Fail
Alarm evaluated Only if Application Mode (page 777) = MPTM
Alarm ID 1054
This alarm is active when PF/Q Regulation Type (page 351) = Import/Export
PF/Q Control but Mains Measurement P or Q is unavailable.
When this alarm is active, PF/Q is controlled as if PF/Q Regulation Type
(page 351) = Base PF/Q Control.
Description
Alarm is caused by:
Mains Measurement P (page 357) = Analog Input and
LAI MAINS MEASUREMENT P (PAGE 992) is not configured

Value from LAI Mains Measurement P (page 357) has Invalid flag
(page 652)
Mains Measurement Q (page 358) = Analog Input and
LAI MAINS MEASUREMENT Q (PAGE 992) is not configured
Value from LAI Mains Measurement Q (page 358) has Invalid flag
(page 652)
Wrn PF(Pm) Fail

Alarmlist message Wrn PF(Pm) Fail
Alarm evaluated Only when PF/Q Control PTM Mode (page 349) = PF(Pm)
Alarm ID 1048
This alarm indicates PF(Pm) Control Fail which can be caused by:
PF/Q Request Source (page 350) = Analog External Value and
Breaker state (page 778) = ParalOper
Note: Function is evaluated as PF/Q Request Source (page 350) =
Setpoint
Description curve is not available in configuration - evaluated during controller

initialization only
Note: Function is evaluated as PF/Q Control PTM Mode (page 349) =
PF Control
curve has changed resolution

Wrn PVCB Fail To Close

Alarmlist
Wrn PVCB Fail To Close
message
Alarm
evaluated
Related
MINT, MPTM
applications
Alarm ID 1591
Description closing.
LBO PVCB CLOSE/OPEN (PAGE 969) closed but LBI PVCB FEEDBACK (PAGE

912) did not closed in 2 seconds.
Image 7.85 PVCB Fail To Close
Wrn PVCB Fail To Open

Alarmlist
Wrn PVCB Fail To Open
message
Alarm
evaluated
Related
MINT, MPTM
applications
Alarm ID 1590
opening.
LBO PVCB CLOSE/OPEN (PAGE 969) opened but LBI PVCB FEEDBACK (PAGE
912) did not opened in 2 seconds.
Description
Image 7.86 PVCB Fail To Open
Wrn PVCB Fail

Alarmlist
Wrn PVCB Fail
message

Alarm
evaluated
Related
MINT, MPTM
applications
Alarm ID 1589
LBI PVCB FEEDBACK (PAGE 912) does not match expected position given by
LBO PVCB CLOSE/OPEN (PAGE 969).
There is a mismatch between LBI PVCB FEEDBACK (PAGE 912) and PVCB
FEEDBACK NEGATIVE (PAGE 913).
Description
Image 7.87 PVCB Fail
Wrn Q Control Fail

Alarmlist message Wrn Q Control Fail
Only when PF/Q Request Source (page 350) = Analog External Value, PF/Q
Alarm evaluated Control PTM Mode (page 349) = Q Control and Breaker state (page 778) =
ParalOper
Alarm ID 1049
This alarm indicates Q Control Fail which can be caused by:
Description

LAI Q CONTROL: ANEXT BASE Q (PAGE 1004) is not configured
Value from LAI Q CONTROL: ANEXT BASE Q (PAGE 1004) is out of
LAI Q CONTROL: ANEXT IMP/EXP Q (PAGE 1004) is not configured
Value from LAI Q CONTROL: ANEXT IMP/EXP Q (PAGE 1004) is out
of sensor range (i.e. "###")
When this alarm is active, BESS Required Q (page 757) is taken from Base Q
(page 353) or Import Q (page 354), based on setpoints setting.
Wrn Q&U Protection

Alarmlist message Wrn Q&U Protection
Only when Q&U Protection (page 549) = Enabled and Breaker state (page
Alarm evaluated
778) = ParalOper
Alarm ID 584
This alarm indicates activeQ&U Protection (page 549). At least one actual
mains voltage value is lower than allowed relative ratio (Uactual/Unominal) set
Description by Q&U < V (page 550) and value BESS Q (page 665) is lower than Q&U < Q
(page 550) for longer time then Q&U Protection Delay (page 551).
Wrn Q(P) Fail

Alarmlist message Wrn Q(P) Fail
Only when PF/Q Control PTM Mode (page 349) = Q(P) and at least one Gen-
Alarm evaluated
set is excited
Alarm ID 1051
This alarm indicates Q(P) Control Fail which can be caused by:
PF/Q Request Source (page 350) = Analog External Value and
Note: Function is evaluated as PF/Q Request Source (page 350) =
Description Setpoint
Q(P) (PAGE 860) curve is not available in configuration - evaluated

during controller initialization only.
PF Control

Q(P) (PAGE 860) curve has changed resolution
Wrn Q(Um) Fail

Alarmlist message Wrn Q(Um) Fail
Alarm evaluated Only if PF/Q Control PTM Mode (page 349) = Q(Um)
Alarm ID 1050
This alarm indicates Q(Um) Control Fail which can be caused by:
If PF/Q Request Source (page 350) = Analog External Value and
LAI Q(UM): 0 REF ANEXT BASE Q (PAGE 1005) is not configured
Value LAI Q(UM): 0 REF ANEXT BASE Q (PAGE 1005) is out of

If PF/Q Regulation Type (page 351) = Import/Export PF/Q Control
LAI Q(UM): 0 REF ANEXT IMP/EXP Q (PAGE 1006) is not
configured
Description
Value LAI Q(UM): 0 REF ANEXT IMP/EXP Q (PAGE 1006) is out of
Note: In both cases is the function evaluated as PF/Q Request
Source (page 350) = Setpoint
Q(UM) (PAGE 858) curve is not available in configuration - evaluated

PF Control
Q(UM) (PAGE 858) curve has changed resolution

Wrn Qref/Ulim Fail

Alarmlist message Wrn Qref/Ulim Fail
Only if PF/Q Control PTM Mode (page 349) = Qref/Ulim and at least one Gen-
Alarm evaluated
set is excited
Alarm ID 1052
Description This alarm indicates Qref/Ulim Control Fail which can be caused by:

If PF/Q Request Source (page 350) = Analog External Value and
LAI QREF/ULIM: ANEXT QREF/PNOM B Q (PAGE 1007) is not
configured
Value LAI QREF/ULIM: ANEXT QREF/PNOM B Q (PAGE 1007) is
out of sensor range (i.e. "###")
If PF/Q Regulation Type (page 351) = Import/Export PF/Q Control
LAI QREF/ULIM: ANEXT QREF/PNOM I/E Q (PAGE 1008) is not
configured
Value LAI QREF/ULIM: ANEXT QREF/PNOM I/E Q (PAGE 1008) is
out of sensor range (i.e. "###")
Note: In both cases is the function evaluated as PF/Q Request
Source (page 350) = Setpoint
QREF/ULIM (PAGE 859) curve is not available in configuration - evaluated

PF Control
QREF/ULIM (PAGE 859) curve has changed resolution

Wrn Redundant CAN inconsistency

Alarmlist message Wrn Redundant CAN inconsistency
Alarm evaluated Only when CAN Intercontroller Comm Redund (page 388) = Enabled
Alarm ID 1079
This alarm is issued when there is inconsistency between CAN2A (page 19)
Description and CAN2B (page 19).
Wrn RTC Battery Flat

Alarmlist message Wrn RTC Battery Flat
Alarm evaluated Only during power-on of the controller
Alarm ID 42
This alarm indicates that the controller detected a flat RTC Battery during
Description
power-on. The RTC battery is considered to be flat if its voltage drops bellow 2.8

V. To remove this alarm follow the Backup battery replacement (page 81).
Wrn Reverse Synchronization Fail

Alarmlist message Wrn Reverse Synchro Fail
Alarm evaluated Only if LBO REVERSE SYNCHRONIZATION (PAGE 974) is closed
Alarm ID 93
This alarm is activated when Reverse Synchronization fails. Reverse
Description Synchronization is activated when synchronization is done over MCB breaker.
Wrn SD Card Failed

Alarmlist message Wrn SD Card Fail
Alarm evaluated Only when Long Term History (page 393) = Mount or Format
Alarm ID 1280
This alarm is activated when it is not possible to read or write to the SD card.
The alarm is also displayed in case that the setpoint SD Card File System
(page 393) is set to Mount or Format but the SD card is not inserted. This alarm
Description
will not be activated if the card is not compatible (ALI SD Card Not Compatible
(page 1107) is active).
Wrn SD Card File System Failed

Alarmlist message Wrn SD Card File System Failed
Alarm evaluated Only when Long Term History (page 393) = Mount
Alarm ID 1639
This alarm is activated when there is a wrong file system on the SD Card.
Description The alarm is not activated if the SDcard is not compatible.
Wrn SNMP TRAP 1 Fail

Alarmlist message Wrn SNMP TRAP 1 Fail
Only when SNMP Agent (page 416) = Enabled and SNMP Traps IP Address
Alarm evaluated
1 (page 418) is set.
Alarm ID 823
This alarm is activated if sending of SNMP trap to IP address set by SNMP
Description Traps IP Address 1 (page 418) failed.
Wrn SNMP TRAP 2 Fail

Alarmlist message Wrn SNMP TRAP 2 Fail
Only when SNMP Agent (page 416) = Enabled and SNMP Traps IP Address
Alarm evaluated
2 (page 418) is set.
Alarm ID 824
This alarm is activated if sending of SNMP trap to IP address set by SNMP
Description Traps IP Address 2 (page 418) failed.
Wrn SOC High Alarm

Alarmlist message Wrn SOC High Alarm
Alarm evaluated Only if BESS (page 365) = Installed
Alarm ID 1595
This alarm is activated by BESS >SOC Protection (page 589).
Description
Wrn SOC Low Alarm

Alarmlist message Wrn SOC Low Alarm
Alarm ID 1594
This alarm is activated by BESS <SOC Protection (page 589).
Description

Wrn Soft Transfer Fail

Alarmlist message Wrn Soft Transfer Fail
Alarm evaluated During transition of load
Alarm ID 852
This alarm is activated when loading/unloading was not finished in time Load
Description Ramp (page 468) +10%.
Wrn Stop Fail

Alarmlist
Wrn Stop Fail
message
Alarm
Only when BESS should be stopped
evaluated
Related
MINT, MPTM
applications
Alarm ID 48
This alarm is activated when BESS is expected to be stopped but there is at least one
symptom such as too high voltage or frequency which is not fulfilled.
Description
Note: BESS cannot be started while this alarm is active.
Wrn SW Key CAN Redundancy Error

Alarmlist message Wrn SW Key CAN Redundancy Error
Alarm evaluated Only when CAN Intercontroller Comm Redund (page 388) = Enabled
Alarm ID 1463
This alarm is activated when there is an attempt to enable premium feature
Description CAN Intercontroller Communication Redundancy (page 132) without of
valid SW Key (page 381).
Wrn SW Key Hot Swap Error

Alarmlist message Wrn SW Key Hot Swap Error

Alarm ID 1461
This alarm is activated when there is an attempt to enable premium feature Hot
Description
Swap Redundancy (page 160) without valid SW Key (page 381).
Wrn Test UPQF

Alarmlist message Wrn Test UPQF
Alarm ID 583
This alarm has informative meaning. It indicates, that Test mode for U, P, Q and
Description f is enabled, i.e. Grid Codes Test (page 527) = Enabled.
Wrn Unsupported PMS Mode

Alarmlist message Wrn Unsupported PMS Mode
Alarm ID 1044
This alarm is active if setpoint #Power Management Mode (page 482) = N/A
Description
Mode.
Wrn Voltage Regulation Limit

Alarmlist message Wrn Voltage Regulation Limit
Alarm evaluated While BESS is running
Alarm ID 152
This alarm is issued when Voltage Regulator Output (page 758) stays close
to Voltage Regulator Low Limit (page 471) or Voltage Regulator High
Description Limit (page 471) for at least 2 seconds and will remain active as long as the
cause is present.
Wrong PLC Configuration

Alarmlist message Wrong PLC Configuration
Alarm evaluated Always
Alarm ID 41
This alarm is activated when the PLC - Programmable Logic Controller
(page 183) configuration is invalid.Once the alarm is active the whole PLC does
Description
not work. This alarm will be active until the PLC configuration is not fixed and
the archive is written to the controller.
Alarm Only
Alarm List Indication
ALI Bus Ph L1 Inverted
Alarm Type Alarm List Indication (page 198)

Alarmlist message ALI Bus Ph L1 Inverted
Alarm ID 928
Description This alarm is activated when Bus Phase L1 is inverted.

Alarm ID 929

Alarm ID 930

ALI Bus Ph Rotation Opposite

Alarmlist message ALI Bus Ph Rotation Opposite
Alarm ID 847
This alarm is activated when controller detects wrong phase rotation, e.g.
Phase Rotation (page 377) is set to Clockwise and actual rotation is
Description
Counterclockwise, on the Bus side.
ALI BCB Closing Is Blocked

Alarmlist message ALI BCB Closing Is Blocked
Alarm ID 2339
Alarm is active in case the BCB breaker is blocked due to some of the
generator protections being disabled:
BESS <f Protection (page 576)
Description BESS >f Protection (page 575)

BESS <V Protection (page 567)
BESS >V (page 565) and BESS >>V Protection (page 566)
Short Circuit Protection (page 562)
ALI CAN Mode Inconsistency

Alarmlist message ALI CAN Mode Inconsistency
Alarm ID 1291
This alarm is active when there is mismatch between setpoint CAN
Intercontroller Comm Mode (page 389) and value CAN Intercontroller
Description Comm Mode (page 780).
After changing the setpoint CAN Intercontroller Comm Mode (page 389), it is
needed to power cycle the controller to get rid of the alarm.

ALI Daily Battery Cycles Reached

Alarmlist message ALI Daily Battery Cycles Reached
Alarm ID 1605
This alarm is activated if number of daily battery cycles specified by the setpoint
Description
Max Battery Cycles Per Day (page 432) is reached.
ALI BESS Ph L1 Inverted

Alarmlist message ALIBESS Ph L1 Inverted
Alarm ID 922
Description This alarm is activated whenBESS Phase L1 is inverted.

Alarmlist message ALIBESS Ph L2 Inverted
Alarm ID 923
Description This alarm is activated whenBESS Phase L2 is inverted.

Alarmlist message ALI BESS Ph L3 Inverted
Alarm ID 924
Description This alarm is activated when BESS Phase L3 is inverted.
ALI BESS Ph Rotation Opposite

Alarmlist message ALI BESS Ph Rotation Opposite

Alarm ID 154
Description
Counterclockwise, on the BESS side.
ALI Redundant CAN Error

Alarmlist message ALI Redundant CAN Error
Alarm ID 1290
This alarm is active when Value CAN Intercontroller Comm Redundancy
(page 780) and Setpoint CAN Intercontroller Comm Redund (page 388)
Description does not match.
After changing the setpoint CAN Intercontroller Comm Redund (page 388),
it is needed to power cycle the controller to get rid of the alarm.
ALI SD Card Not Compatible

Alarmlist
ALI SD Card Not Compatible
message
Related
MINT, MPTM
applications
Alarm ID 1610
This alarm is activated when the value SD Card Status (page 781) shows Status:
Not Supported.
Description Alarm is active all the time until the card is unmounted, or a compatible card is
inserted.

ALI SD Card In Slot

Alarmlist
ALI SD Card In Slot
message
Alarm evaluated Only when Long Term History (page 393) = Unmount
Related
MINT, MPTM
applications
Alarm ID 1611
This alarm is activated when SD Card File System (page 393) is set to Unmount
Description but SD Card is detected in the slot.
ALI SD Card Full

Alarmlist
ALI SD Card Full
message
Alarm evaluated Only when Long Term History (page 393) = Mount
Related
MINT, MPTM
applications
Alarm ID 1621
This alarm is activated if value SD Card Free Space (page 781) drops below 10 %.
Description
ALI SD Card Formatting/Mounting

Alarmlist
ALI SD Card Formating/Mounting
message
Related
MINT, MPTM
applications
Alarm ID 1638
This alarm is activated when the process of mounting or formatting is active.
Description

ALI Mains Ph L1 Inverted

Alarmlist message ALI Mains Ph L1 Inverted
Alarm ID 925
Description This alarm is activated when Mains Phase L1 is inverted.

Alarm ID 926

Alarm ID 927
ALI Mains Ph Rotation Opposite

Alarmlist message ALI Mains Ph Rotation Opposite
Alarm ID 158
Description
Counterclockwise, on the Mains side.

ALI Start Blocking

Alarmlist
ALI Start Blocking
message
Alarm evaluated Only if LBI START BLOCKING (PAGE 916) is configured
Related
MINT, MPTM
applications
Alarm ID 56
This alarm is active if LBI START BLOCKING (PAGE 916) is closed before BESS is
Description
started.
ALI Wrong Power Format

Alarmlist message ALI Wrong Power Format
Alarm ID 149
This alarm is activated when there is inconsistency of Power Formats And
Description Units (page 196) on any controller which is connected via CAN2A (page 19) or
CAN2B (page 19).
Alarm List + History Indication
AHI SyncNotAllowed
Alarm Type Alarm List + History Record Indication (page 198)

Alarmlist message AHI SyncNotAllowed
When MAINS/BUS HEALTHY (PAGE 959) = 1 and Mains Params/MP
Alarm evaluated
Alarm ID 452
This alarm is activated when synchronization of BESS with Mains is blocked by
Description Synchronization & Connection Conditions (page 302).

History Record Only
Hst Pave
Alarm Type History Record Only (page 198)

Alarmlist message Hst Pave
Alarm evaluated Only if Pave Protection (page 560) != Disabled
Alarm ID 1078
This alarm is activated when value Pmom/Pave (page 724) is equal to or
Description bigger than 1 for period longer that is allowed by application curve P Mom/Pave
Max (page 863) and MCB gets opened.
Hst ROCOF 1

Alarmlist message Hst ROCOF 1
Only if ROCOF1 Protection (page 585) = Enabled or (ROCOF1 Protection
Alarm evaluated
(page 585) = Parallel Only and MCB FEEDBACK (PAGE 902) is active)
Alarm ID 851
This alarm is activated by ROCOF1 Protection (page 585).
Note: There are 4 ROCOF Protections which can be enabled.

Description
Hst ROCOF2

Alarmlist message Hst ROCOF2
Alarm evaluated
Alarm ID 1112
Description This alarm is activated by ROCOF2 Protection (page 586)
Hst ROCOF3


Alarm evaluated
Alarm ID 1113
Hst ROCOF4

Alarm evaluated
Alarm ID 1114
Hst Vector Shift

Alarmlist message Hst Vector Shift
Only if Vector Shift Protection (page 584) = Enabled or (Vector Shift
Alarm evaluated Protection (page 584) = Parallel Only and MCB FEEDBACK (PAGE 902) is
closed)
Alarm ID 850
Description This alarm is activated when Vector shift (page 173) is detected.
9.2.3 Alarms level 2

What alarms level 2 are:
The level 2 level alarm indicates that a critical level of the respective value or parameter has been reached.

List of alarms level 2
Shutdown 1114 PVBO Short Circuit 1122

Emergency Stop 1114 Sd SOC Critical High 1122
E-STOP 1114 Sd SOC Critical Low 1122
Hst BESS Anti Islanding 1114 Sd Start Fail 1123
Sd DC Circuit Close Fail 1115 Slow Stop 1124
Sd ECU Communication Stp Bus Meas Error 1124
Fail 1115 Stp BCB Fail 1124
Sd BESS >>V L1-N 1115 Stp BCB Fail To Close 1125
Sd Mains/Bus >>V L2-N 1115 Stp BCB Fail To Open 1125
Sd BESS >>V L3-N 1116 Stp BCB Secondary Fail 1126
Sd BESS >>V L1-L2 1116 Stp BCB Secondary Fail
Sd BESS >>V L2-L3 1116 To Close 1127
Sd BESS >>V L3-L1 1116 Stp BCB Secondary Fail
Sd BESS >V L1-N 1117 To Open 1128
Sd BESS >V L2-N 1117 Stp Synchronization Fail 1128
Sd BESS >V L3-N 1117 Mains Protection 1130
Sd BESS >V L1-L2 1117 Mains Avg >V L1-N 1130
Sd BESS <V L1-N 1118 Mains Avg >V L1-L2 1130
Sd BESS <V L1-L2 1119 PV Breaker Open 1131

PVBO PV Anti Islanding 1131
Sd BESS <V L2-L3 1119
PVBO PV Not Operable 1131
Sd BESS <V L3-L1 1119
Sd BESS >f 1120 6 back to Alarms
Sd BESS <f 1120

Sd BESS V Unbalance
Ph-N 1120
Sd BESS V Unbalance
Ph-Ph 1120
Sd BESS Current
Unbalance 1121
Sd IDMT Earth Fault
Current 1121
Sd IDMT BESS >A 1121
Sd IDMT Overload 1121
Sd NCB Fail 1122

Shutdown
Emergency Stop
Alarm Type Shutdown (page 199)Shutdown (page 199)

Alarmlist message Emergency Stop
Alarm evaluated Only if EMERGENCY STOP (PAGE 886) is configured
Alarm ID 44
This alarm is activated by LBI EMERGENCY STOP (PAGE 886). The BESS shuts
down in the moment the input is activated and starting is blocked until the input
is deactivated and fault reset is pressed.
Note: Use red emergency button placed on the switchboard door and connect
it to a binary input of the controller. Then configure the function EMERGENCY
Description
STOP (PAGE 886) to that binary input. It is recommended to use NC contact of
the button.
Note: The MCB control is not affected by this alarm.
E-STOP
Alarm Type Shutdown (page 199)

Alarmlist message E-STOP
Alarm ID 853
Alarm is activated when dedicated E-STOP (page 143) input is not closed. The
Description BESS shuts down in the moment the input is opened and starting is blocked
until the input is closed and fault reset is pressed.
Hst BESS Anti Islanding
Alarm Type History Record

Alarmlist message Hst BESS Anti Islanding
Alarm ID 1602
This alarm is activated at the moment when there is no grid forming source of
Description power such as Mains or Gen-set on the Bus and the BESS is controlled by P-Q
method (grid support mode).

Sd DC Circuit Close Fail

Alarmlist message Sd DC Circuit Close Fail
Alarm evaluated
Alarm ID 1655
This alarm gets active anytime when the BESS DC circuit is expected to be
Description closed but the LBI PRECHARGE FINISHED (PAGE 906) gets inactive (DC circuit is
opened) unexpectedly.
Sd ECU Communication Fail

Alarmlist message Sd ECU Communication Fail
With configured LBO ECU POWER RELAY (PAGE 943) - Only when this LBO is
Alarm evaluated active
Without configured LBO ECU POWER RELAY (PAGE 943) - All the time
This alarm occurs when an ECU is configured, but the communication with the
Description
ECU is not established or has dropped out.
Sd BESS >>V L1-N

Alarmlist message Sd BESS >>V L1-N
Alarm evaluated Only if BESS >>V Protection (page 566) != Disabled
Alarm ID 1098
This alarm is activated by BESS >>V Protection (page 566).
Description
Sd Mains/Bus >>V L2-N

Alarm ID 1099
Description

Sd BESS >>V L3-N

Alarm ID 1100
Description
Sd BESS >>V L1-L2

Alarmlist message Sd BESS >>V L1-L2
Alarm ID 1101
Description
Sd BESS >>V L2-L3

Alarm ID 1102
Description
Sd BESS >>V L3-L1

Alarm ID 1103
Description

Sd BESS >V L1-N
Alarm Type Shutdown (page 199) Warning (page 198)

Alarmlist message Sd BESS >V L1-N
Alarm evaluated Only if BESS >V (page 565) != Disabled
Alarm ID 98
This alarm is activated by BESS >V (page 565).
Description
Sd BESS >V L2-N

Alarm evaluated Only if BESS >V (page 565)!= Disabled
Alarm ID 99
Description
Sd BESS >V L3-N

Alarm ID 100
Description
Sd BESS >V L1-L2

Alarmlist message Sd BESS >V L1-L2
Alarm ID 107
Description

Sd BESS >V L2-L3

Alarm ID 108
Description
Sd BESS >V L3-L1

Alarm ID 109
Description
Sd BESS <V L1-N

Alarmlist message Sd BESS <V L1-N
Alarm ID 95
Description
Sd BESS <V L2-N

Alarm ID 96
Description

Sd BESS <V L3-N

Alarm ID 97
This alarm is activated by BESS <V Protection (page 567).
Description
Sd BESS <V L1-L2

Alarmlist message Sd BESS <V L1-L2
Alarm ID 104
Description
Sd BESS <V L2-L3

Alarm ID 105
Description
Sd BESS <V L3-L1

Alarm ID 106
Description

Sd BESS >f

Alarmlist message Sd BESS >f
Alarm evaluated Only if BESS >f Protection (page 575) != Disabled
Alarm ID 121
This alarm is activated by BESS >f Protection (page 575).
Description
Sd BESS <f

Alarmlist message Sd BESS <f
Alarm evaluated Only if BESS >f Protection (page 575) != Disabled
Alarm ID 120
This alarm is activated by BESS <f Protection (page 576).
Description
Sd BESS V Unbalance Ph-N

Alarmlist message Sd BESS V Unbalance Ph-N
Alarm ID 589
This alarm is activated by BESS V Unbalance Protection (page 567).
Description
Sd BESS V Unbalance Ph-Ph

Alarmlist message Sd BESS V Unbalance Ph-Ph
Alarm ID 588
This alarm is activated by BESS V Unbalance Protection (page 567).
Description

Sd BESS Current Unbalance

Alarmlist message Sd BESS Current Unbalance
Alarm evaluated Only if BESS Current Unbalance Protection (page 564) != Disabled
Alarm ID 591
This alarm is activated by BESS Current Unbalance Protection (page 564).
Description
Sd IDMT Earth Fault Current

Alarmlist message Sd IDMT Earth Fault Current
Alarm evaluated Only if Earth Fault Current Protection (page 583) != Disabled
Alarm ID 598
This alarm is activated by Earth Fault Current Protection (page 583).
Description
Sd IDMT BESS >A

Alarmlist message Sd IDMT BESS >A
Alarm evaluated While BESS is loaded, if IDMT BESS >A Protection (page 562) != Disabled
Alarm ID 597
This alarm is activated by IDMT BESS >A Protection (page 562).
Description
Sd IDMT Overload

Alarmlist message Sd IDMT Overload
Alarm evaluated Only if IDMT Overload Protection (page 561) != Disabled
Alarm ID 147
This alarm is activated by IDMT Overload Protection (page 561).
Description

Sd NCB Fail

Alarmlist message Sd NCB Fail
Alarm evaluated Only if NCB FEEDBACK (PAGE 905) is configured
Alarm ID 148
This alarm is activated when LBI NCB FEEDBACK (PAGE 905) does not match
Description expected position given by LBO NCB CLOSE/OPEN (PAGE 963).
PVBO Short Circuit

Alarmlist message PVBO Short Circuit
Alarm evaluated Only if Short Circuit Protection (page 562) != Disabled
Alarm ID 595
This alarm is activated by Short Circuit Protection (page 562).
Description
Sd SOC Critical High

Alarmlist message Sd SOC Critical High
Alarm ID 1597
This alarm is activated by BESS >>SOC Protection (page 590).
Description
Sd SOC Critical Low

Alarmlist message Sd SOC Critical Low
Alarm ID 1596
This alarm is activated by BESS <<SOC Protection (page 590).
Description

Sd Start Fail

Alarmlist message Sd Start Fail
Alarm evaluated During starting of BESS
Alarm ID 55
This alarm is activated after attempt to start BESS failed (BESS Start TO
Description elapsed).

Slow Stop
Stp Bus Meas Error
Alarm Type Slow Stop (page 199)

Alarmlist message Stp Bus Meas Error
Alarm evaluated Bus Meas Error (page 581) != Disabled
Alarm ID 143
This protection is activated in case that voltage mismatch on Bus side is
detected for longer than 20 seconds.The mismatch is detected according to the
conditions below:
Own BCB was closed
MCB FEEDBACK (PAGE 902) was detected (physically or via CAN2) →
Breaker State = MultParOp, MAINS/BUS HEALTHY (PAGE 959) is active
and Controller Mode (page 378) = AUTO
Description
Any other controller in Control Group (page 507) closed BCB
Note: Alarm is activated after 20 s, but BCB closing is blocked

immediately.
BTB connected another Control Group with MCB Feedback or controller

with closed BCB
Stp BCB Fail

Alarmlist
Stp BCB Fail
message
Alarm
Only if BCB Control Mode (page 362) != External
evaluated
Related
MINT, MPTM
applications
Alarm ID 91
Description

Image 7.88 BCB Fail
Stp BCB Fail To Close

Alarmlist
Stp BCB Fail To Close
message
Alarm
evaluated
Related
MINT, MPTM
applications
Alarm ID 1555
closing.
LBO BCB CLOSE/OPEN (PAGE 926) closed but LBI BCB FEEDBACK (PAGE 881)
did not closed in Waiting For Breaker Feedback (page 1) seconds.
Description
Image 7.89 BCB Fail To Close
Stp BCB Fail To Open

Alarmlist
Stp BCB Fail To Open
message
Alarm
evaluated
Related
MINT, MPTM
applications
Alarm ID 1554
opening.
LBO BCB CLOSE/OPEN (PAGE 926) opened but LBI BCB FEEDBACK (PAGE 881)
did not opened in 2 seconds.
Description
Image 7.90 BCB Fail To Open
Stp BCB Secondary Fail

Alarmlist
Stp BCB Secondary Fail
message
Only if LBI BCB SECONDARY FEEDBACK (PAGE 884) or LBI BCB SECONDARY
Alarm FEEDBACK NEGATIVE (PAGE 883) or BCB CLOSE/OPEN SECONDARY (PAGE 927) is
evaluated configured
Related
MINT, MPTM
applications
Alarm ID 451
LBI BCB SECONDARY FEEDBACK (PAGE 884) does not match expected position
Description given by LBO BCB CLOSE/OPEN SECONDARY (PAGE 927).
There is a mismatch between LBI BCB SECONDARY FEEDBACK (PAGE 884) and
BCB SECONDARY FEEDBACK NEGATIVE (PAGE 883).

Image 7.91 BCB Secondary Fail
Stp BCB Secondary Fail To Close

Alarmlist
Stp BCB Secondary Fail To Close
message
Only if LBI BCB SECONDARY FEEDBACK (PAGE 884) or LBI BCB SECONDARY
Alarm FEEDBACK NEGATIVE (PAGE 883) or BCB CLOSE/OPEN SECONDARY (PAGE 927) is
evaluated configured
Related
MINT, MPTM
applications
Alarm ID 1557
closing.
Description LBO BCB CLOSE/OPEN SECONDARY (PAGE 927) closed but LBI BCB
SECONDARY FEEDBACK (PAGE 884) did not closed in Waiting For Breaker
Feedback (page 1) seconds.

Image 7.92 BCB Secondary Fail To Close
Stp BCB Secondary Fail To Open

Alarmlist
Stp BCB Secondary Fail To Open
message
Only if LBI BCB SECONDARY FEEDBACK (PAGE 884) or LBI BCB SECONDARY FEEDBACK
Alarm
NEGATIVE (PAGE 883) or BCB CLOSE/OPEN SECONDARY (PAGE 927) is configured
evaluated
Related
MINT, MPTM
applications
Alarm ID 1556
opening.
LBO BCB CLOSE/OPEN SECONDARY (PAGE 927) opened but LBI BCB
SECONDARY FEEDBACK (PAGE 884) did not opened in 2 seconds.
Description
Image 7.93 BCB Secondary Fail To Open
Stp Synchronization Fail

Alarmlist message Stp Synchronization Fail
Alarm evaluated During synchronization
Alarm ID 94
This alarm is activated if the synchronization fails, e.g. Synchronization
Description Timeout (page 477) elapses.

Mains Protection
Mains Avg >V L1-N
Alarm Type Mains Protection (page 199)

Alarmlist message Mains Avg >V L1-N
Alarm evaluated Only if Mains 10min Avg >V (page 517) != Disabled
Alarm ID 1466
This alarm is activated by Mains 10min Avg >V (page 517) protection.
Description
Mains Avg >V L2-N

Alarm ID 1467
Description
Mains Avg >V L3-N

Alarm ID 1468
Description
Mains Avg >V L1-L2

Alarmlist message Mains Avg >V L1-L2
Alarm ID 1144
Description

Mains Avg >V L2-L3

Alarm ID 1145
Description
Mains Avg >V L3-L1

Alarm ID 1146
Description
PV Breaker Open
PVBO PV Anti Islanding
Alarm Type PV Braker Open

Alarmlist message PVBO PV Anti Islanding
Alarm ID 1593
This alarm is activated at the moment when there is no grid forming source of
Description power such as Mains, Gen-set, or BESS controlled by U-f method on the Bus
and the PV inverter is alone on the Bus.
PVBO PV Not Operable
Alarm Type PV Braker Open

Alarmlist message PVBO PV Not Operable
Alarm ID 1592
This alarm is activated when the PV is not operable because its inverter is in the
Description
fault state.

9.2.4 Other alarms

List of other alarms
Mains/Bus >V L1-N 1135 DISTIN 01 1159 DISTIN 41 1169

Mains/Bus >V L1-L2 1137 DISTIN 04 1159 DISTIN 44 1169
Mains/Bus >>V L1-N 1139 DISTIN 07 1160 DISTIN 47 1170
Mains/Bus >>V L1-L2 1141 DISTIN 10 1161 DISTIN 50 1171
Mains/Bus <V L1-N 1144 DISTIN 13 1162 DISTIN 53 1172
Mains/Bus <V L1-L2 1146 DISTIN 16 1162 DISTIN 56 1172
Mains/Bus <<V L1-N 1148 DISTIN 19 1163 DISTIN 59 1173
Mains/Bus <<V L1-L2 1150 DISTIN 22 1164 DISTIN 62 1174
Mains/Bus >f 1153 DISTIN 25 1165 DISTOUT 1175
Mains/Bus >>f 1153 DISTIN 26 1165 ECU 1 Comm Fail 1175
Mains/Bus <f 1154 DISTIN 27 1165 ECU 2 Comm Fail 1175
Mains/Bus <<f 1154 DISTIN 28 1165 ECU 3 Comm Fail 1175
Mains/Bus V Unbalance DISTIN 29 1166 ECU 4 Comm Fail 1176
Ph-N 1155 DISTIN 30 1166 ECU 5 Comm Fail 1176
Mains/Bus V Unbalance DISTIN 31 1166 ECU 6 Comm Fail 1177
Ph-Ph 1155 DISTIN 32 1166 ECU 7 Comm Fail 1177
Maintenance 1 Interval 1156 DISTIN 33 1167 ECU 8 Comm Fail 1177
Maintenance 1 RunHours 1156 DISTIN 34 1167 ECU 9 Comm Fail 1178

ECU 16 Comm Fail 1180
SHAIN 1 1181
SHAIN 2 1181
Wrn SHAIN Collision 1181
SHBIN 1 1181
SHBIN 2 1182
SHBIN 3 1182
SHBIN 4 1182
SHBIN 5 1182
SHBIN 6 1183
Wrn SHBIN Collision 1183
VRT Protection Trip 1183
6 back to Alarms

Mains/Bus >V L1-N
Application Mode
Alarm Type
(page 777)
Alarm Type MPTM Mains Protection (page 199)
MINT History Record Only (page 198)
Alarmlist message Mains/Bus >V L1-N
Application Mode
Evaluated
(page 777)
Alarm evaluated Only if Mains >V Protection (page 568)!=
MPTM
Disabled
MINT All the time

Alarm ID 125
This alarm is activated by Mains >V Protection (page 568).
This alarm is activated when Mains/Bus Voltage L1-N (page 731) rises over
preset value.
Application Mode
Behavior
(page 777)
Alarm is activated by Mains >V Protection
MPTM
Description (page 568)
Protection is always active. Alarm is activated
when relative value of Mains/Bus Voltage L1-N
(page 731) related to Mains/Bus Nominal
MINT
Voltage Ph-N (page 373) rises over
GeneratorBus Right >V (page 1) for period
longer than BESS >V Delay (page 443).
Mains/Bus >V L2-N
Application Mode
Alarm Type
(page 777)

Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 126
This alarm is activated when Mains/Bus Voltage L2-N (page 731) rises above
preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Mains/Bus >V L3-N
Application Mode
Alarm Type
(page 777)
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 127
Description This alarm is activated when Mains/Bus Voltage L3-N (page 732) rises over
preset value.

Application Mode
Behavior
(page 777)
MPTM
(page 568)
MINT
Mains/Bus >V L1-L2
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus >V L1-L2
Application Mode
Evaluated
(page 777)
Alarm evaluated Only if Mains >V Protection (page 568) !=
MPTM
Disabled
MINT All the time

Alarm ID 131
This alarm is activated when Mains/Bus Voltage L1-L2 (page 732) rises over
preset value.
Application Mode
Behavior
(page 777)
MPTM
when relative value of Mains/Bus Voltage L1-L2
MINT
Voltage Ph-Ph (page 374) rises over

Mains/Bus >V L2-L3
Application Mode
Alarm Type
(page 777)
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 132
preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Mains/Bus >V L3-L1
Application Mode
Alarm Type
(page 777)

Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 133
preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Mains/Bus >>V L1-N
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus >>V L1-N
Application Mode
Evaluated
(page 777)
Alarm evaluated Only if Mains >>V Protection (page 570)!=
MPTM
Disabled
MINT All the time

Alarm ID 1080
This alarm is activated by Mains >>V Protection (page 570).
Description This alarm is activated when Mains/Bus Voltage L1-N (page 731) rises over
preset value.

Application Mode
Behavior
(page 777)
Alarm is activated by Mains >>V Protection
MPTM
(page 570)
MINT
Voltage Ph-N (page 373) rises over BESS >>V
(page 443) for period longer than BESS >>V
Delay (page 444).
Mains/Bus >>V L2-N
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus >>V L2-N
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 1082
preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Delay (page 444).

Mains/Bus >>V L3-N
Application Mode
Alarm Type
(page 777)
Alarmlist message M Mains/Bus >>V L3-N
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 1084
preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
(page 443).
Mains/Bus >>V L1-L2
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus >>V L1-L2

Application Mode
Evaluated
(page 777)
Alarm evaluated Only if Mains >>V Protection (page 570) !=
MPTM
Disabled
MINT All the time

Alarm ID 1086
preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Voltage Ph-Ph (page 374) rises over BESS >>V
Delay (page 444).
Mains/Bus >>V L2-L3
Application Mode
Alarm Type
(page 777)
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 1088
Description This alarm is activated when Mains/Bus Voltage L2-L3 (page 732) rises over
preset value.

Application Mode
Behavior
(page 777)
MPTM
(page 568)
MINT
Delay (page 444).
Mains/Bus >>V L3-L1
Application Mode
Alarm Type
(page 777)
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 1090
preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Delay (page 444).

Mains/Bus <V L1-N
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus <V L1-N
Application Mode
Evaluated
(page 777)
Alarm evaluated Only if Mains <V Protection (page 572) !=
MPTM
Disabled
MINT All the time

Alarm ID 122
This alarm is activated by Mains <V Protection (page 572).
This alarm is activated when Mains/Bus Voltage L1-N (page 731) drops
below preset value.
Application Mode
Behavior
(page 777)
Alarm is activated by Mains <V Protection
MPTM
MINT
Voltage Ph-N (page 373) drops below BESS <V
(page 444) for period longer than BESS <V
Delay (page 445).
Mains/Bus <V L2-N
Application Mode
Alarm Type
(page 777)

Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 123
below preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Delay (page 445).
Mains/Bus <V L3-N
Application Mode
Alarm Type
(page 777)
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 124
Description This alarm is activated when Mains/Bus Voltage L3-N (page 732) drops
below preset value.

Application Mode
Behavior
(page 777)
MPTM
(page 572)
MINT
Delay (page 445).
Mains/Bus <V L1-L2
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus <V L1-L2
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 128
This alarm is activated when Mains/Bus Voltage L1-L2 (page 732) drops
below preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Voltage Ph-Ph (page 374) drops below BESS
<V (page 444) for period longer than BESS <V
Delay (page 445).

Mains/Bus <V L2-L3
Application Mode
Alarm Type
(page 777)
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 129
below preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Delay (page 445).
Mains/Bus <V L3-L1
Application Mode
Alarm Type
(page 777)

Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 130
below preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Delay (page 445).
Mains/Bus <<V L1-N
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus <<V L1-N
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 1081
Description This alarm is activated when Mains/Bus Voltage L1-N (page 731) drops
below preset value.

Application Mode
Behavior
(page 777)
MPTM
(page 573)
MINT
Delay (page 445).
Mains/Bus <<V L2-N
Application Mode
Alarm Type
(page 777)
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 1083
below preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Delay (page 445).

Mains/Bus <<V L3-N
Application Mode
Alarm Type
(page 777)
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 1085
below preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Delay (page 445).
Mains/Bus <<V L1-L2
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus <<V L1-L2

Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 1087
below preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Delay (page 445).
Mains/Bus <<V L2-L3
Application Mode
Alarm Type
(page 777)
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 1089
Description This alarm is activated when Mains/Bus Voltage L2-L3 (page 732) drops
below preset value.

Application Mode
Behavior
(page 777)
MPTM
(page 573)
MINT
Delay (page 445).
Mains/Bus <<V L3-L1
Application Mode
Alarm Type
(page 777)
Application Mode
Evaluated
(page 777)
MPTM
Disabled
MINT All the time

Alarm ID 1091
below preset value.
Application Mode
Behavior
(page 777)
MPTM
MINT
Delay (page 445).

Mains/Bus >f
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus >f
Application Mode
Evaluated
(page 777)
Alarm evaluated Only if Mains >f Protection (page 577) !=
MPTM
Disabled
MINT All the time

Alarm ID 135
This alarm is activated by Mains >f Protection (page 577).
This alarm is activated when Mains/Bus Frequency (page 731), rises over
preset value.
Application Mode
Behavior
(page 777)
Description Alarm is activated by Mains >f Protection (page
MPTM
577)
when Mains/Bus Frequency (page 731) rises
MINT
over BESS >f (page 446) for period longer than
BESS >f Delay (page 446).
Mains/Bus >>f
Alarm Type
Alarmlist message Mains/Bus >>f
Alarm evaluated Only if Mains >>f Protection (page 578) != Disabled
Alarm ID 1092
This alarm is activated by Mains >>f Protection (page 578).
This alarm is activated when Mains/Bus Frequency (page 731), rises over
Description
preset value.

Mains/Bus <f
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus <f
Application Mode
Evaluated
(page 777)
Alarm evaluated Only if Mains <f Protection (page 579) !=
MPTM
Disabled
MINT All the time

Alarm ID 134
This alarm is activated by Mains >f Protection (page 577).
This alarm is activated when Mains/Bus Frequency (page 731), drops below
preset value.
Application Mode
Behavior
(page 777)
Description Alarm is activated by Mains <f Protection (page
MPTM
579)
when Mains/Bus Frequency (page 731) drops
MINT
below BESS <f (page 447) for period longer than
BESS <f Delay (page 447).
Mains/Bus <<f
Alarm Type
Alarmlist message Mains/Bus <<f
Alarm evaluated Only if Mains <<f Protection (page 580) != Disabled
Alarm ID 1093
This alarm is activated by Mains <<f Protection (page 580).
This alarm is activated when Mains/Bus Frequency (page 731), drops below
Description
preset value.

Mains/Bus V Unbalance Ph-N
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus V Unbalance Ph-N
Application Mode
Evaluated
(page 777)
Alarm evaluated Only if Mains V Unbalance Protection (page
MPTM
574) != Disabled
MINT All the time

Alarm ID 593
This alarm is activated by Mains V Unbalance Protection (page 574)
This alarm is activated when relative difference between Mains/Bus Voltage
L1-N (page 731), Mains/Bus Voltage L2-N (page 731) or Mains/Bus
Voltage L3-N (page 732) rises over preset value.
Application Mode
Behavior
(page 777)
Description Alarm is activated by Mains V Unbalance
MPTM
Protection (page 574)
when relative difference between bus voltages
MINT rises over BESS V Unbalance (page 445) for
period longer than BESS V Unbalance Delay
(page 445).
Mains/Bus V Unbalance Ph-Ph
Application Mode
Alarm Type
(page 777)
Alarmlist message Mains/Bus V Unbalance Ph-Ph

Application Mode
Evaluated
(page 777)
Alarm evaluated Only if Mains V Unbalance Protection (page
MPTM
574) != Disabled
MINT All the time

Alarm ID 592
This alarm is activated by Mains V Unbalance Protection (page 574)
This alarm is activated when relative difference between Mains/Bus Voltage
L1-L2 (page 732), Mains/Bus Voltage L2-L3 (page 732) or Mains/Bus
Voltage L3-L1 (page 732) rises over preset value.
Application Mode
Behavior
(page 777)
Description Alarm is activated by Mains V Unbalance
MPTM
Protection (page 574)
when relative difference between bus voltages
MINT rises over BESS V Unbalance (page 445) for
period longer than BESS V Unbalance Delay
(page 445).
Maintenance 1 Interval
Alarm Type Based on configuration (Warning (page 198)/Slow Stop (page 199))
Alarmlist message Wrn/Stp Maintenance 1 Interval
Alarm evaluated Only if Maintenance Timer 1 Interval (page 641) != Disabled
Alarm ID 1072
This alarm is activated when setpoint Maintenance Timer 1 Interval (page
641) elapses i.e. the value Maintenance Timer 1 Interval (page 773) = 0 and
Description
lasts until the setpoint is set to value > 0 or "Disabled".
Maintenance 1 RunHours
Alarmlist message Wrn/Stp Maintenance 1 Protection
Alarm evaluated Only if Maintenance Timer 1 RunHours (page 640) != Disabled
Alarm ID 585

This alarm is activated when setpoint Maintenance Timer 1 RunHours (page
640) elapses i.e. the value Maintenance Timer 1 RunHours (page 772) = 0
Description
and lasts until the setpoint is set to value > 0 or "Disabled".
Alarm ID 1073
Description
Alarm ID 586
This warning is activated when setpoint Maintenance Timer 2 RunHours
(page 642) elapses i.e. the value Maintenance Timer 2 RunHours (page
Description
773) = 0 and lasts until the setpoint is set to value > 0 or "Disabled".
Alarm ID 1074
Description

Alarm ID 587
Description
Alarm ID 1519
Description
Alarm evaluated Only if Maintenance Timer 4 RunHours (page 645) or != Disabled
Alarm ID 1518
Description

DISTIN 01
Alarm Type Based on configuration

Alarmlist message Wrn/Sd DISTIN 01
Alarm evaluated Only if DIST-IN 01 is configured
Alarm ID 1156
This alarm is activated when DIST-IN data are not received from controller with
Description
CAN Controller Address (page 385) = 1.
6 back to List of other alarms
DISTIN 02

Alarm ID 1157
Description
DISTIN 03

Alarm ID 1158
Description
DISTIN 04

Alarm ID 1159
Description

DISTIN 05

Alarm ID 1160
Description
DISTIN 06

Alarm ID 1161
Description
DISTIN 07

Alarm ID 1162
Description
DISTIN 08

Alarm ID 1163
Description

DISTIN 09

Alarm ID 1164
Description
DISTIN 10

Alarm ID 1165
Description
DISTIN 11

Alarm ID 1166
Description
DISTIN 12

Alarm ID 1167
Description

DISTIN 13

Alarm ID 1168
Description
DISTIN 14

Alarm ID 1169
Description
DISTIN 15

Alarm ID 1170
Description
DISTIN 16

Alarm ID 1171
Description

DISTIN 17

Alarm ID 1172
Description
DISTIN 18

Alarm ID 1173
Description
DISTIN 19

Alarm ID 1174
Description
DISTIN 20

Alarm ID 1175
Description

DISTIN 21

Alarm ID 1176
Description
DISTIN 22

Alarm ID 1177
Description
DISTIN 23

Alarm ID 1178
Description
DISTIN 24

Alarm ID 1179
Description

DISTIN 25

Alarm ID 1180
Description
DISTIN 26

Alarm ID 1181
Description
DISTIN 27

Alarm ID 1182
Description
DISTIN 28

Alarm ID 1183
Description

DISTIN 29

Alarm ID 1184
Description
DISTIN 30

Alarm ID 1185
Description
DISTIN 31

Alarm ID 1186
Description
DISTIN 32

Alarm ID 1187
Description

DISTIN 33

Alarm ID 1344
Description
DISTIN 34

Alarm ID 1345
Description
DISTIN 35

Alarm ID 1346
Description
DISTIN 36

Alarm ID 1347
Description

DISTIN 37

Alarm ID 1348
Description
DISTIN 38

Alarm ID 1349
Description
DISTIN 39

Alarm ID 1350
Description
DISTIN 40

Alarm ID 1351
Description

DISTIN 41

Alarm ID 1352
Description
DISTIN 42

Alarm ID 1353
Description
DISTIN 43

Alarm ID 1354
Description
DISTIN 44

Alarm ID 1355
Description

DISTIN 45

Alarm ID 1356
Description
DISTIN 46

Alarm ID 1357
Description
DISTIN 47

Alarm ID 1358
Description
DISTIN 48

Alarm ID 1359
Description

DISTIN 49

Alarm ID 1360
Description
DISTIN 50

Alarm ID 1361
Description
DISTIN 51

Alarm ID 1362
Description
DISTIN 52

Alarm ID 1363
Description

DISTIN 53

Alarm ID 1364
Description
DISTIN 54

Alarm ID 1365
Description
DISTIN 55

Alarm ID 1366
Description
DISTIN 56

Alarm ID 1367
Description

DISTIN 57

Alarm ID 1368
Description
DISTIN 58

Alarm ID 1369
Description
DISTIN 59

Alarm ID 1370
Description
DISTIN 60

Alarm ID 1371
Description

DISTIN 61

Alarm ID 1372
Description
DISTIN 62

Alarm ID 1373
Description
DISTIN 63

Alarm ID 1374
Description
DISTIN 64

Alarm ID 1375
Description

DISTOUT

Alarmlist message Wrn/Sd DISTOUT
Alarm evaluated Only if DIST-OUT is configured
Description This alarm is activated when failure of virtual module DIST-OUT is detected.
ECU 1 Comm Fail

Alarmlist message Name of ECU in ECU slot 1
1. ECU with protection configured in ECU slot 1
2. LBI ECU COMMUNICATION FAIL BLOCK (PAGE 1) and ECU
Alarm evaluated COMMUNICATION FAIL BLOCK 1 (PAGE 1) not activated
3. LBO ECU POWER RELAY (PAGE 943) is closed or all the time when is not
configured
Alarm ID 945
This alarm is activated when there is no communication received from ECU
Description configured in ECU slot 1.
ECU 2 Comm Fail

configured
Alarm ID 946
ECU 3 Comm Fail

configured
Alarm ID 947
ECU 4 Comm Fail

configured
Alarm ID 948
ECU 5 Comm Fail

configured
Alarm ID 949

ECU 6 Comm Fail

configured
Alarm ID 950
ECU 7 Comm Fail

configured
Alarm ID 951
ECU 8 Comm Fail

configured

Alarm ID 952
ECU 9 Comm Fail

configured
Alarm ID 953
ECU 10 Comm Fail

configured
Alarm ID 954
ECU 11 Comm Fail

Alarm evaluated

COMMUNICATION FAIL BLOCK 11 (PAGE 1) not activated
configured
Alarm ID 955
ECU 12 Comm Fail

configured
Alarm ID 956
ECU 13 Comm Fail

configured
Alarm ID 957

ECU 14 Comm Fail

configured
Alarm ID 958
ECU 15 Comm Fail

configured
Alarm ID 959
ECU 16 Comm Fail

configured
Alarm ID 960
Description This alarm is activated when there is no communication received from ECU

configured in ECU slot 16.
SHAIN 1

Alarmlist message Wrn/Sd SHAIN 1
Alarm evaluated Only if SHAIN 1 is configured
Alarm ID 36
This alarm is activated when shared analog inputs are not received from SHAIN
Description
module 1.
SHAIN 2

Alarmlist message Wrn/Sd SHAIN 2
Alarm evaluated Only if SHAIN 2 is configured
Alarm ID 233
This alarm is activated when shared analog inputs are not received from SHAIN
Description
module 2.
Wrn SHAIN Collision

Alarmlist message Wrn SHAIN Collision
Alarm evaluated Only if SHIN 1 or SHAIN 2 module is configured
Alarm ID 38
This alarm is activated when controller receives shared analog inputs of any
Description SHAIN module from more than just one controller.
SHBIN 1

Alarmlist message Wrn/Sd SHBIN 1
Alarm evaluated Only if SHBIN 1 is configured

Alarm ID 32
This alarm is activated when shared binary inputs are not received from SHBIN
Description
module 1.
SHBIN 2

Alarm ID 33
Description
module 2.
SHBIN 3

Alarm ID 34
Description
module 3.
SHBIN 4

Alarm ID 35
Description
module 4.
SHBIN 5


Alarm ID 216
Description
module 5.
SHBIN 6

Alarm ID 217
Description
module 6.
Wrn SHBIN Collision

Alarmlist message Wrn SHBIN Collision
Alarm evaluated Only if at least one of SHBIN 1 to SHBIN 6 modules is configured
Alarm ID 37
This alarm is activated when controller receives shared binary inputs of any
Description SHBIN module from more than just one controller.
VRT Protection Trip
Alarm Type Based on Dynamic Support Protection Type (page 552)

Alarmlist message Wrn/MP VRT Protection Trip
Only when Dynamic Support (page 552) = Enabled and and Breaker state
Alarm evaluated
(page 778) = ParalOper
Alarm ID 1043
This alarm indicates active Dynamic Support (page 552) protection.
Description

9.3 Modules
9.3.1 Plug-in modules
IMPORTANT: 2nd generation of InteliNeo 6000 controllers does not support new modules and 3rd
generation does not support all old modules.
The available communication plug-in modules are:

CM-RS232-485 – communication module for connection via RS232 or RS485 line
CM2-4G-GPS – communication module for connection via 4G
CM3-Ethernet – communication module for internet connection via Ethernet
The available extension plug-in modules are:
EM-BIO8-EFCP – extension module with 8 binary inputs/outputs and with earth fault current protection
Note: Controller has 2 plug-in module slots.
Supported combinations of plug-in modules

Module CM-Ethernet CM-4G-GPS CM-RS232-485 EM-BIO8-EFCP
CM-Ethernet
CM-4G-GPS
CM-RS232-485
EM-BIO8-EFCP
Communication modules
CM2-4G-GPS 1184
CM2-4G-GPS
CM2-4G-GPS plug-in module containing a GPS receiver and GSM/WCDMA/LTE modem which can work in
two modes of operation.
Image 7.94 CM2-4G-GPS module

IMPORTANT: Any manipulation with plug-in module shall be done with disconnected power
supply to controller.
IMPORTANT: Operating temperature of module is from -30 °C to +75 °C.
Note: Cellular data service must be enabled in your SIM card by your mobile operator for successful
operation.
CM2-4G-GPS module works with:

WebSupervisor – internet-based remote monitoring solution
AirGate – powerful connection technology to make internet access as simple as possible
CM2-4G-GPS module also works like GPS locator. Geo-fencing function can be used with this module.
4G module types
If the anthenna is CELLULAR only and has 1 cable (OT1A4GXXMCX), it is connected to the 4G-MAIN
connector.
If the anthenna is CELLULAR only and has 2 cables, cables are connected to the 4G-MAIN or 4G-DIV
connectors (does not matter which cable to which connector).
If the anthenna is a combination of CELLULAR/GPS and has 2 cables (OT1A4GGPSCX), then cable
"4G/LTE" needs to be connected to the 4G-MAIN connector and "GPS" cable to the GPS connector.
If the anthenna is a combination of CELLULAR/GPS and has 3 cables (OT2A4GGPSCX), then cables
"4G/LTE" need to be connected to the 4G-MAIN and 4G-DIV connectors (does not matter which cable to
which connector) and "GPS" cable to the GPS connector.
Note: Type of the cable is labeled on its side.
Technical data
General
Width × Height × Depth 73.8 × 50.3 × 15
Weight ~35 g
Power supply 8-36 V DC
Power consumption 1.7 W
Peak power consumption 10 W
Operating temperature -30 ˚C to +70 ˚C
Storage temperature -40 ˚C to +80 ˚C

GNSS
Antenna interface SMA female, 2.8 V / 20 mA
Antenna type Active
Cellular
2G (GSM/GPRS/EDGE) Quad band,
850/900/1800/1900 MHz
3G (UMTS/HSPA+) Seven band, 800
(BdXIX) / 850 (BdV) / 900 (BdVIII) / AWS
(BdIV) / 1800 (BdIX) / 1900 (BdII) /
Supported networks and frequency bands
2100MHz (BdI)
4G (LTE) Twelve band, 700 (Bd12 <MFBI
Bd17>, Bd28) 800 (Bd18, Bd19, Bd20) 850
(Bd5) / 900 (Bd8) / AWS (Bd4) / 1800 (Bd3)
/ 1900 (Bd2) / 2100 (Bd1) / 2600MHz (Bd7)
Antenna interface 2x SMA female (Main and Diversity)
SIM card settings

SIM card must be adjusted as follows:
SMS service enabled
Packet data (Internet access) enabled (when required for the selected mode of operation)
PIN code security disabled
How to start using CM2-4G-GPS module

You will need a controller, CM2-4G-GPS module, antenna and SIM card with SMS and packet data
service.
Note: Make sure that your SIM supports the packet data network type you want to use. – i.e. if you want to
use the module in LTE (4G) network you have to confirm with the operator that the particular SIM card
supports 4G network.
Contact your mobile operator for getting packet data APN (APN = Access Point Name), username and
password.
Example: APN Name = "internet", UserName = [blank], Password = [blank].
Make sure SIM card does not require PIN code. Use any mobile phone to switch the SIM PIN security off.
Place the SIM card into slot on CM2-4G-GPS card
Connect the antenna to Cellular module antenna connector.
If you want to use the built-in GPS receiver, also connect an active GPS antenna to the GPS antenna
connector.
Switch off the controller.
Insert CM2-4G-GPS module into controller
Power up the controller.
Select the mode of CM2-4G-GPS module by adjusting setpoint Internet Connection (page 1).
Activate CM2-4G-GPS module by switching the setpoint Internet Connection (page 1) to enabled.

Enter correct APN Name, APN User Name and APN User Password in controller's setpoint group CM-4G-
GPS which is accessible by PAGE button from any measurement screen on controller. Setpoints can be
set on controller’s front panel keyboard or by InteliConfig.
Enter correct Access Point Name (this information is provided by Mobile Operator). Setpoint can be set
on controller's front panel or by InteliConfig.
Switch the controller off and on.
Wait for approx 2 – 4 minutes for first connection of the system to AirGate. AirGate will automatically
generate the AirGate ID value. Then navigate to measurement screens where you will find signal strength
bar and AirGate ID identifier.
Firmware upgrade
Download the newest FW of module from ComAp website (in form of PSI file or installation package)
Install package to computer or open PSI to install it into InteliConfig
Plug the module into the controller and power the controller on.
Open a connection with controller via InteliConfig
Go the menu Tools -> Firmware upgrade, select the Plug-in modules tab and select the appropriate
firmware you want to program into the module (in InteliConfig).
Press the OK button to start upgrade of firmware.
The firmware update process may be performed via any kind of connection including connection via the same
module in which the firmware is to be updated. The connection is re-established again automatically when the
update process is finished.
Extension modules
EM-BIO8-EFCP 1187
EM-BIO8-EFCP
EM-BIO8-EFCP is optional plug-in card. Through this card, the controller can accommodate one AC current
(CT) measuring input (1A or 5A input) and up to 8 binary inputs or outputs. In InteliConfig PC configuration
tool it is possible to easily choose whether particular I/O will be binary input or output.
Image 7.95 EM-BIO8-EFCP interface

Note: This protection is active ONLY when Engine is running.
IMPORTANT: Any manipulation with plug-in module shall be done with disconnected power
supply to controller.
IMPORTANT: Earth fault current measurement is supported by controller only in slot A.
Image 7.96 Overview of EM-BIO8-EFCP
Image 7.97 EM-BIO8-EFCP wiring
EM-BIO8-EFCP technical data
Power supply
Power supply range 8-36 VDC
40 mA / 8 VDC
27 mA / 12 VDC
Power consumption
22 mA / 24 VDC
19 mA / 36 VDC

Binary inputs
Number Up to 8, non-isolated
Close/Open 0-2 VDC close contact
indication >6 VDC open contact
Binary outputs
Number Up to 8 , non-isolated
Max. current 0,5A
Switching to positive supply terminal
Current measuring input

Number of inputs 2
Nominal input current 1A/5A
Load (CT output impedance) < 0,1
Max measured current from CT 10 A
Current measurement
2% from Nominal current
tolerance
Max peak current from CT 150 A / 1 s
Max continuous current 10 A
Firmware upgrade
Download the newest FW of module from ComAp website (in form of PSI file or installation package)
Install package to computer or open PSI to install it into InteliConfig
Plug the module into the controller and power the controller on.
Open a connection with controller via InteliConfig
Go the menu Tools -> Firmware upgrade, select the Plug-in modules tab and select the appropriate
firmware you want to program into the module (in InteliConfig).
Press the OK button to start upgrade of firmware.
The firmware update process may be performed via any kind of connection including connection via the same
module in which the firmware is to be updated. The connection is re-established again automatically when the
update process is finished.
9.3.2 CAN modules

Supported combinations of modules 1189
Module's protections 1190
Theory of binary inputs and outputs 1191
Extension modules 1195
Supported combinations of modules

The maximal number of CAN modules is limited by the number of the controller's generic modules. Once the
physical module is configured, it allocates necessary generic modules. So, it is possible to configure as many
CAN modules as many generic modules are available. The maximum number of CAN modules is also limited

by the number of addresses (indexes) that can be configured for each type of the generic module. CAN
modules and generic modules share indexes.
Example: If you configure Inteli IO8/8 module which is using 1x BI, BO, and AO generic module with index
(address) 1, any other module using same generic modules will not be able to be configured with index
(address) 1 (IGS-PTM, Inteli AIO9/1).
Each generic module has 8 "terminals" (inputs/outputs) and the InteliNeo 6000 has the following amount of
the generic modules:
AI generic: 10
AO generic: 8
BI generic: 16
BO generic: 12
In the table below, you can see how many generic modules are necessary for each CAN module and how
many indexes are available for each type of CAN module in the InteliNeo 6000.
Max number of
CAN Module AI generic AO generic BI generic BO generic
indexes
Inteli AIN8 10 1 0 0 0
Inteli IO 8/8 12 0 1 1 1
Inteli IO 16/0 8 0 1 2 0
IGL-RA15 4 0 0 0 2
IGS-PTM 4 1 1 1 1
Inteli AIO9/1 5 2 1 0 0
Inteli AIN8TC 10 1 0 0 0
I-AOUT8 4 0 1 0 0
IS-AIN8 10 1 0 0 0
IS-AIN8TC 10 1 0 0 0
IS-BIN16/8 7 0 0 2 1
Note: When configuring modules do not forget to let first 4 indexes free for modules which can't use high
addresses such as IGL-RA15, IGS-PTM, AIO9/1, I-AOUT8.
Note: Module Inteli IO8/8 has available AOUT only if it is configured with index number below 9 and Inteli
AIO9/1 has available AOUT only if it is configured with index number below 5.
Note: Module Inteli IO8/8 with older FW than 1.3.1.2 has available AOUT only if it is configured with index
number below 5.
Module's protections
Each configured CAN module can has it's own protection and protection state. For setup: connect the
controller via InteliConfig → Control → Controller Configuration → Modules → Module Settings.
Protection Upon Module Failure
None - No alarm will be activated if module fails. It is not possible to use the User Protection State.
Warning - Wrn alarm is activated if module fails.
Shutdown - Sd alarm is activated if module fails.

Note: The name and color of the alarm is automatically generated according to the options Protection Upon
Module Failure, Module Name, and Module Index. The module name is automatically generated or
renamed by the user.
Protection State - If you check the check box the new User Protection State will be displayed in the User
Protection States group in the Values after the configuration is imported to the CU.
Note: The name of the User Protection State is automatically generated according to the options Protection
Upon Module Failure, Module Name, and Module Index. The module name is automatically generated or
renamed by the user.
Example: Wrn Inteli AIN8 10 = Warning upon module failure of the Inteli AIN8 module with index 10.
Theory of binary inputs and outputs

Binary inputs 1191
Binary outputs 1193
Type of the binary inputs/outputs of some configured modules using BINs or BOUTs can be changed via Inteli
Config. For setup: connect the controller via InteliConfig → Control → Controller Configuration → Modules →
Module Settings → Binary Inputs Type / Binary Outputs Type.
See the fallowing chapters for more details.
Binary inputs
Pull Down
The pull-down logic is used when it is required to ensure that the logical value of inputs settles at the expected
logical level whenever external devices are turned off, or they are at a high impedance state. It ensures that
input is at a defined low logic level when the connection with external devices is lost. In the controller
(module), the pull-down resistor is used to connect the input to the -BAT (0 V), so the log 0 (open state) is
represented by 0 V. This connection is used as prevention against fluctuations and an undefined state at the
input.
The principle of internal connection is shown in the picture below.
The bulb represents internal state of binary input.
In case the “COM” (+Ucc) is not connected to the input terminal “BIN” then the internal state is logical 0.
In case the “COM” (+Ucc) is connected to the input terminal “BIN” then the internal state is logical 1.

Note: There is not any COM terminal on the controller, the wire is directly connected to the input terminal
"BIN", so if input signal is log 1 the +Ucc is directly connected to the "BIN".
Pull Up
The pull-up logic is used when it is required to establish an additional loop over the critical components while
making sure that the voltage is well-defined even when the switch is open. It ensures that input and wiring is
at a defined high logical level in the absence of an input signal. In the controller (module), the pull-up resistor
is used to connect the input to the +BAT (+Ucc), so the log 0 (open state) is represented by +Ucc. This
connection is used as prevention against fluctuations and an undefined state at the input.
The bulb represents internal state of binary input.
In case the input terminal “BIN” (+Ucc) is not connected to the “COM” (GND) then the internal state is
logical 0.
In case the input terminal “BIN” (+Ucc) is connected to the “COM” (GND) then the internal state is logical
1.

Note: There is not any COM terminal on the controller, the wire is directly connected to the input terminal
"BIN", so if input signal is log 1 the GND is directly connected to the "BIN".
6 back to Theory of binary inputs and outputs
Binary outputs
High side switch - HSS

The high side logic is used when load is permanently connected to the ground (GND) and when it is required
to ensure that the logical value of outputs settles at the expected logical level whenever the controller
(module) is turned off, or at a high impedance state. It ensures that external devices will not be randomly
activated when the connection is lost.
The bulb represents internal state of binary output.
By activating of binary output terminal (BOUT), the switch is closed, which causes connection of the load
to the VHS (Voltage High side) and +Ucc, so the external state of the load is logical 1.

Low side switch - LSS
The low side logic is used when load is permanently connected to the voltage (+Ucc). In case module will be
turned off or the connection will be lost the external devices will be activated. It can be used as inverse logic
for the detection of the lost connection.
The bulb represents internal state of binary output.
By activating of binary output terminal (BOUT), the switch is closed, which causes connection of the load
to the ground (GND), so the external state of the load is logical 1.
Note: Because of safety reasons, the Low side switch is not supported in the InteliNeo 6000 controller. In
case you need BOUT to BIN logical communication between controllers using Pull Up BIN logic, you must
use an external module with LSS BOUT logic or any converter which converts the HSS controller's BOUT to
LSS. The solution above is not recommended! Try to reconsider your options and use the Pull Down BIN
logic.

6 back to Theory of binary inputs and outputs
Extension modules
Inteli AIN8 1195
Inteli IO8/8 1201
IGL-RA15 1208
IGS-PTM 1213
Inteli AIO9/1 1218
Inteli AIN8TC 1223
I-AOUT8 1227
IS-AIN8 1231
IS-AIN8TC 1241
IS-BIN16/8 1245
Inteli AIN8
Inteli AIN8 module is extension module equipped with analog inputs and Impulse/RPM input. The module is
connected to controller by CAN1A (page 19) bus. It is possible to connect up to 10 Inteli AIN8 external units
to one controller.
The detection of communication speed is indicated by fast flashing of status LED. Once the speed is detected
the module remains set for the speed even when the communication is lost. Renewal of communication
speed detection is done by reset of the module.

Image 7.98 Inteli AIN8
Image 7.99 Inteli AIN8 dimensions
Note: All dimensions are in mm.

Terminals
Analog input 8 analog Inputs

CAN1 CAN1A (page 19) line
Power Power supply
CAN LED Tx, Rx Indication transmitted or received data
Status LED LED indication of correct function
CAN terminator Terminating CAN resistor (active in position “ON” - switch both switches)
IMPORTANT: Impulse input is not supported by the controller.
Analog inputs
8 channels
can be configured as:
resistor three wire input
current input
voltage input
All inputs can be configured to any logical function or protection.
Supported sensors
Sensors
PT100 [°C] (fix) PT100 [°F] (fix) +-1V 4-20mA passive 0-250 ohm
PT1000 [°C] (fix) PT1000 [°F] (fix) 0-2.4V 4-20mA active 0-2400 ohm
NI100 [°C] (fix) NI100 [°F] (fix) 0-5V 0-20mA passive 0-10k ohm
NI1000 [°C] (fix) NI1000 [°F] (fix) 0-10V +-20mA active
Note: It is also possible to use User Curves as sensor.

CAN address
DIP switch determinates CAN address for analog inputs.
Note: In case of setting the CAN address to zero, the appropriate group of signals is deactivated.
Firmware upgrade process:
1. Disconnect all terminals from the unit.
2. Separate the top cover of module
3. Put the TEST jumper on a pins
4. Connect the unit with PC via RS232-null modem cable and AT-Link conv
5. Connect power supply of the module (status LED lights continuously)

6. Launch FlashPgr.exe PC software (version 4.2 or higher)
7. In FlashPrg program choose card Inteli AIN8 and load FW for the module
8. Set the proper COM port (connected with the unit) and press Start button
9. Wait till process is done (If the process doesn’t start – after 60 second the “Timeout” will be evaluated. In
this case please check:
You have proper connection with the unit
COM port selection is correct
Module has power supply, (no CAN bus connection, status LED lights continuously)
10. After successful programming disconnect AT-Link conv , remove TEST jumper and disconnect power
supply

11. Connect power supply again (status LED should blinking)
12. Module FW is upgraded
LED indication
LED status Description

Dark Fw in module does not work correctly.
Flashing Module does not communicate with controller (in case non-zero CAN address).
Power supply is in the range and the communication between Inteli AIN8 and controller
works properly.
Lights
Or power supply is in range and zero CAN address is set. (in case zero CAN address
module doesn’t communicate with the controller).
Wiring
The following diagrams show the correct connection of sensors.
Terminator
Resistance sensor - 3 wires
Note: Ranges: Pt100, Pt1000, Ni100, Ni1000, 0 – 2400 Ω, 0 – 10 kΩ

Resistance sensor - 2 wires
Note: Ranges: Pt100, Pt1000, Ni100, Ni1000, 0 – 2400 Ω, 0 – 10 kΩ
Current sensor - active
Note: Ranges: ±20 mA, 4 – 20 mA
Current sensor - passive
Note: Ranges: 0 – 20 mA, 4 – 20 mA

Voltage sensor
Note: Ranges: ±1 V, 0 – 2,5 V, 0 – 5 V, 0 – 10 V
Technical data
General data
Power supply 8 to 36 V DC
Current consumption 35 mA at 24 V ÷ 100 mA at 8 V
Interface to controller CAN1A (page 19)
Protection IP20
Storage temperature - 40 °C to + 80 °C
Operating temperature - 30 °C to + 70 °C
Dimensions (WxHxD) 110x110x46 mm (4,3”x4,3”x1,8”)
Weight 221,5 grams
Analog inputs
Number of channels 8
Range 0-10 V
Voltage
Accuracy: ± 0,25 % of actual value + ± 25 mV
Range: ±20 mA
Current
Accuracy: ± 0,25 % of actual value + ± 50 µA
Range: 0- 10 kΩ
Resistive
Accuracy: ± 0,5 % of actual value + ± 2 Ω
6 back to Extension modules
Inteli IO8/8
Inteli IO8/8 module is an extension module equipped with binary inputs, binary outputs and analog outputs.
The module is connected to controller by CAN1A (page 19) bus.
Inteli IO8/8 is the name of the module, but it is possible to configure the module (by internal switch) to two
configurations:
Inteli IO8/8 - 8 binary inputs, 8 binary outputs and 2 analog outputs
Inteli IO16/0 - 16 binary inputs, 0 binary outputs and 2 analog outputs
It is possible to connect up to 12 Inteli IO8/8 or 8 Inteli IO 16/0 external units to one controller.

Image 7.100 Inteli IO8/8
Image 7.101 Inteli IO8/8 dimensions
Note: All dimensions are in mm.

Terminals
Binary inputs 8 binary inputs

Binary outputs 8 binary outputs (8 binary inputs)
Analog outputs 2 analog outputs
CAN1 CAN1A (page 19) line
Power Power supply
Binary inputs LEDs 8 LEDs for binary input indication
Binary outputs LEDs 8 LEDs for binary output indication
CAN LED Indication transmitted or received data
Status LED indication of correct function
Inputs and outputs

Binary inputs
8 channels
pull up
pull down
All 8 inputs are configured to one type together.
All inputs can be configured to any logical function or protection.
Binary outputs

8 channels
High side switch
Low side switch
Always all 8 inputs are configured to one type (HSS/LSS) together. All 8 outputs can be modified to inputs by
switch on the PCB ( Inteli IO8/8 to Inteli IO16/0).
Analog outputs
2 channels
voltage 0-10V
current 0-20mA
PWM (level 5V, with adjustable frequency from 200Hz to 2400Hz, with step 1Hz)
All inputs/outputs can be configured to any logical function or protection.
Output state check

Output state check function evaluates in real time the state of binary outputs and adjusted (required) state. In
case of failure (different state of required state and real state) history record and alarm are issued (type of the
alarm is set by “Protection upon module failure” - (No protection / Warning / Shutdown)).
This function is designed for short-circuit or other failure, which causes change of set state of binary output.
CAN address
In Inteli IO8/8 mode CAN address for binary inputs is determined by DIP switch A, CAN address for binary
output and analog outputs is determined by DIP switch B.
In Inteli IO16/0 mode CAN address for binary inputs is determined by DIP switch A, first group of 8 input has
address A, second group of 8 inputs has address A+1. CAN address of analog outputs is set by DIP switch B.
Firmware upgrade process:
1. Disconnect all terminals from the unit.
2. Separate the top cover of module
3. Put the TEST jumper on a pins

4. Connect the unit with PC via RS232-null modem cable and AT-Link conv
5. Connect power supply of the module (status LED lights continuously)

6. Launch FlashPgr.exe PC software (version 4.2 or higher)
7. In FlashPrg program choose card Inteli IO8/8 and load FW for the module
8. Set the proper COM port (connected with the unit) and press Start button
9. Wait till process is done (If the process doesn’t start – after 60 second the “Timeout” will be evaluated. In
this case please check:
You have proper connection with the unit
COM port selection is correct
Module has power supply, (no CAN bus connection, status LED lights continuously)
10. After successful programming disconnect AT-Link conv , remove TEST jumper and disconnect power
supply
11. Connect power supply again (status LED should blinking)
12. Module FW is upgraded
LED indication
Binary input
Each binary input has LED which indicates input signal. LED is shining when input signal is set, and LED is
dark while input signal has other state.
Binary output
Each binary output has LED which indicates output signal. Binary output LED is shining when binary output is
set. When this LED is shining, then module is configured as 8 binary inputs and 8 binary outputs. When this
LED is dark, then the module is configured as 16 binary inputs.
LED at power connector - status LED

Flashing Module does not communicate with controller (in case non-zero CAN address).
Power supply is in the range and the communication between Inteli IO8/8 and controller
works properly.
Lights
Or power supply is in range and zero CAN address is set. (in case zero CAN address
module doesn’t communicate with the controller).
Wiring
The following diagrams show the correct connection of inputs and outputs.
Binary inputs - pull up
There are two options of wiring. On upper picture you can see case when binary input is connected between
BIN2 and COM (COM is connected internally to the GND (-) - dashed line).
On lower picture is case of wiring between BIN2 and GND (-). Both ways are correct.
Binary inputs - pull down
There are two options of wiring. On upper picture you can see case when binary input is connected between
BIN2 and COM (COM is connected internally to the Ucc (+) - dashed line).
On lower picture is case of wiring between BIN2 and Ucc (+). Both ways are correct.

Binary outputs - high side
When high side setting of outputs is chosen - binary output must be connected to the minus potential directly
Terminal VHS (voltage High side) has to be connected to positive potential directly. Maximal current of each
binary output is 500 mA. Size of fuse depends on load.
Binary outputs - low side
When low side setting of outputs is chosen - binary output must be connected to the plus potential of power
supply directly. Minus potential is connected internally - dashed line.
Analog outputs
Note: Limit of analog ground (AGND) is 100mA.
IMPORTANT: Terminator for analog output has special analog ground (AGND), which must not be
connected to the GND.
Technical data
General data
Protection IP20

Dimensions (WxHxD) 110x110x46 mm (4,3”x4,3”x1,8”)
Weight 240 grams
Analog outputs
Range 0-10 V
Voltage Accuracy: ± 20 mV + ±0,5 % of actual value
Imax 5 mA
Range: 0-20 mA
Current Accuracy: ± 100 µA + ±0,5 % of actual value
Rmax 500 Ω
Level 5 V
PWM Frequency - adjustable 200÷2400 Hz
Imax 20 mA
Binary inputs
Number of channels 8 for Inteli IO8/8, 16 for Inteli IO16/0
Input resistance 4400 Ω
Input range 0 to 36 V DC
Switching voltage level for open contact
0 to 2 V DC
indication
Max voltage level for close contact
6 to 36 V DC
indication
Binary outputs
Number of channels 8 for Inteli IO8/8, 0 for Inteli IO16/0
Max current 500 mA
Max switching voltage 36 V DC
IGL-RA15
Remote annunciator (IGL-RA15) is designed as an extension signaling unit. The module is connected to
controller by CAN1A (page 19) bus. It is possible to connect up to 4 IGL-RA15 external units to one
controller.
The unit is equipped with a fully configurable tri-color (red, orange, green) LED for intuitive operation
together with high functionality.

Image 7.102 IGL-RA15
Image 7.103 IGL-RA15 dimensions
Terminals
Horn Horn
CAN CAN1A (page 19) line
Power Power supply
CAN address
Address Jumper A Jumper B

1 OPEN OPEN
5+6 CLOSED OPEN
Customer defined CLOSED CLOSED
SW changing of CAN1A (page 19) address is enabled only when both jumpers are closed. Any one of these
addresses (1+2 or 3+4 or 5+6 or 7+8) can be set by following steps:
Switch to programming mode (Hold the Horn reset and Lamp test when unit is powering on). Status led is
yellow

Press Lamp test sixteen times
Set the address up by pressing Horn reset.
The number of red luminous LEDs means the CAN1A (page 19) addresses (two for addresses 1+2,
four for addresses 3+4, six for addresses 5+6 and eight for addresses 7+8)
Press Lamp test
LED indication
Each LED color is adjusted independently of controller output settings. If controller output 1 is set as
“Common Shutdown” it doesn’t mean red LED1 color for iGL-RA15. The LEDs color can by adjust by
following steps:
yellow
Press Horn reset to change the LED1 color (green, yellow, red)
Press Lamp test to switch to the next LED color adjusting
Continue to adjust all LEDs color
After LED15 color adjusting press three times Lamp test
Note: If there is no operator action during address setting, color adjusting or timeout setting, the unit returns
to normal operation without changes saving.
Status LED
The signals LEDs are handled like binary outputs. It means all what can be configured to binary outputs can
be also configured to the LEDs of IGL-RA15.

Lights Configured logical output is active on the controller
Dark green LED Configured logical output is not active on the controller
Configured logical output is not active on the controller and horn reset was
Dark yellow or red LED
pressed.
Configured logical output is not active on the controller and horn reset was still
Yellow or red LED blinks
not pressed.
Power LED

Blinking green The unit is OK and the communication to the master controller is OK.
Blinking red The unit is OK, but the communication to the master controller is not running.
Blinking yellow EEPROM check not passed OK after power on
Yellow Horn timeout or controller address adjustment
Horn setting
The horn output is activated if any of red or yellow LED is on. Output is on until pressing Horn reset or horn
timeout counts down. The timeout can by set by following steps:
yellow
Press Lamp test fifteen times

Set the horn timeout by pressing Horn reset.
The number of green luminous LEDs means timeout in 10 s (none for disabling horn output, 1 for 10s
timeout, 2 for 10s timeout, 15 for disabling horn timeout).
Press Lamp test two times
Note: If there is no operator action during address setting, color adjusting or timeout setting, the unit returns
to normal operation without changes saving.
The horn is activated if:

Some of red or yellow LED lights up or
At the end of the extended lamp test. See chapter Lamp and horn test (page 1211)
The horn can be silenced:
By pressing horn reset button or
It silences automatically after adjusted time
Lamp and horn test

Pressing and holding lamp test button for less than 2 s execute the basic lamp test. All LEDs light up with the
configured colour. If the button is hold longer than 2 s, an extended test is started. Every LED is tested step-
by-step in green colour and then in red colour. The horn is activated at the end of the test. After that the unit
returns to normal operation. The horn can be silenced with horn reset.
Wiring
* use terminator resistor only when IGL-RA 15 is the last unit on the CAN1A bus.
Note: The shielding of the CAN bus cable has to be grounded at one point only!
Note: See the section Technical data (page 1212) for recommended CAN bus cable type

Technical data
General data
0.35-0.1A (+1Amax horn output) depends on supply
Current consumption
voltage
Protection IP65
Humidity 85%
Dimensions (WxHxD) 180x120x55 mm
Weight 950 g
Horn output
Maximum current 1.0 A
Maximum switching voltage 36 V DC
CAN bus interface

Galvanic separated
Maximal CAN bus length 200 m
Speed 250 kbps
Nominal impedance 120 Ω
Cable type twisted pair (shielded)
Following dynamic cable parameters are important especially for maximal 200 meters CAN bus
length
Nominal Velocity of Propagation min. 75 % (max. 4,4 ns/m)
2
Wire crosscut min.0,25 mm
Maximal attenuation (at 1 MHz) 2 dB/100m
Recommended Industrial Automation & Process Control Cables
3082A DeviceBus for Allen-Bradley DeviceNet
3086A DeviceBus for Honeywell SDS
BELDEN (www.belden.com) 3087A DeviceBus for Honeywell SDS
3105A Paired EIA Industrial RS485 cable
Unitronic BUS DeviceNet Trunk Cable
Unitronic BUS DeviceNet Drop Cable
LAPP CABLE (www.lappcable.com)
Unitronic BUS CAN
Unitronic-FD BUS P CAN UL/CSA

IMPORTANT: This module is not compatible with different than 250 kbps communication speed. If
the ECU module with 125 kbps communication speed is connected the whole system will
automatically switch to the 125 kbps, and IGL-RA15 module will stop communicating.
IGS-PTM
IGS-PTM module is extension module equipped with binary inputs, binary outputs, analog inputs and analog
output. The module is connected to controller by CAN1A (page 19) bus. It is possible to connect up to 4 IGS-
PTM external units to one controller.
Image 7.104 IGS-PTM
Image 7.105 IGS-PTM dimensions

Terminals
Binary inputs 8 binary inputs

Analog inputs 4 analog inputs
Analog outputs 1 analog output
Binary outputs 8 binary outputs
RS232-TTL Interface for programming
Power Power supply
Analog inputs
Analog inputs can be configured for:
Resistance measurement
Current measurement
Voltage measurement
The type of analog inputs is configured via jumpers RUI located on lower PCB.
RUI Analog input configuration

1-2 Resistance measuring
2-3 Current measuring
no jumper Voltage measuring
Supported sensors
Sensors
PT100 [°C] (fix) User curves
NI100 [°C] (fix) 0-100 mV
PT100 [°F] (fix) 0-2400 ohm
NI100 [°F] (fix) ±20 mA

CAN address
Controller type selection
The type of controller to be used with IGS-PTM must be selected via jumper labeled IGS accessible at the
lower PCB.
IGS jumper Controller type

OPEN IL-NT, IC-NT
CLOSE IG-NT, IS-NT, InteliLite
Address configuration
If InteliLite controller type is selected (by IGS jumper), address of IGS-PTM could be modified via jumpers
labeled ADR1 and ADR2.
BIN BOUT AIN

ADR1 ADR2 ADR offset
module module module
Open Open 0 (default) 1 1 1
Close Open 1 2 2 2
Open Close 2 3 3 3
Close Close 3 4 4 4
Programing firmware
Firmware upgrade is via AT-link (TTL). For programming is necessary to close jumper BOOT. RESET jumper
is used to reset the device. Close jumper to reset the device. For programming is used FlashProg PC tool.
LED indication
Binary input
Each binary input has LED which indicates input signal. LED is shining when input signal is set, and LED is
dark while input signal has other state.
Binary output
Each binary output has LED which indicates output signal. Binary output LED is shining when binary output is
set.
LED at power connector - status LED

Dark No required power connected.
Quick flashing Program check failure.
One flash and pause Compensation fail.
Three flashes and
Compensation successful.
pause
Flashes There is no communication between IGS-PTM and the controller.
Power supply is in the range and communication between IGS-PTM and
Lights
controller properly works.

Wiring
Binary inputs
Binary outputs
Resistance sensor
Note: Range: 0- 2400 Ω
IMPORTANT: Physical analog input range is 0-250 Ω. In sensor configuration in PC tool it is

necessary to chose 0-2400 Ω sensor HW type to ensure proper function of analog input.
Voltage sensor
Note: Range 0-100 mV

Current sensor - passive
Note: Range: ± 0-20 mA
IMPORTANT: Physical analog input range is 0-20mA. In sensor configuration in PC tool it is

necessary to chose +- 20mA active sensor HW type to ensure proper function of analog input.
Analog outputs
Note: Range: 0 to 20 mA ± 0,33 mA
Technical data
General data
Current consumption 100 mA at 24V ÷ 500 mA
Protection IP20
Dimensions (WxHxD) 95×96×43 mm (3.7’×3.8’×1.7’)
Analog inputs
Range 0-100 mV
Voltage
Accuracy: 1,5 % ± 1 mV out of measured value
Range: 0-20 mA
Current
Accuracy: 2.5 % ± 0,5 ohm out of measured value
Range: 0- 250 Ω
Resistive
Accuracy: 1 % ± 2 ohm out of measured value

Analog outputs
Range: 0 to 20 mA ± 0,33 mA
Current
Resolution 10 bit
Binary inputs
Input resistance 4700 Ω
Input range 0 to 36 V DC
Switching voltage level for open contact
0 to 2 V DC
indication
Max voltage level for close contact
8 to 36 V DC
indication
Binary outputs
Max current 500 mA
Max switching voltage 36 V DC
Range 0-100 mV
Voltage
Accuracy: 1,5 % ± 1 mV out of measured value
Range: 0-20 mA
Current
Accuracy: 2.5 % ± 0,5 ohm out of measured value
Range: 0- 250 Ω
Resistive
Accuracy: 1 % ± 2 ohm out of measured value
Inteli AIO9/1
Inteli AIO9/1 module is an extension module equipped with analog inputs and outputs – designed for DC
measurement. The module is connected to controller by CAN1A (page 19) bus. It is possible to connect up to
5 Inteli AIO9/1 external units to one controller.
The detection of communication speed is indicated by rapid flashing of status LED. Once the speed is
detected the module remains set for this speed even when the communication is lost. Renewal of
communication speed detection is done by resetting of the module.

Image 7.106 Inteli AIO9/1
Image 7.107 Inteli AIO9/1 dimensions

Terminals
ANALOG INPUT 9 channels

ANALOG OUTPUTS 1 channel
CAN CAN1 line
POWER Power supply
CAN LED Tx, Rx Indication transmitted or received data
CAN terminator Terminating CAN resistor (active in position "ON")
TEST jumper Upgrade of SW
AT-LINK Connector for AT-LINK (Upgrade of SW)
Analog inputs
4 channels AIN1 – AIN4 can be configured as:
Sensor ±65V (determined for measurement of battery voltage)
4 channels AIN5 – AIN8 can be configured as:
Thermocouples – type J,K or L (in °C or °F)
Sensor ±75mV DC – (for connecting current shunts)
1 channel AIN9 can be configured as:
RTD (Pt1000, Ni1000)
Common resistance 0-2400Ω

Analog outputs
1 channel AOUT1. Type of output:
0-10V DC
0-20mA
PWM (5 V, freq 2.4 Hz ÷2.4 kHz)
Analog output has 4-pins connector – GND and one pin for each type of output.
All analog inputs can be configured to any logical function or protection.
Supported sensors
Sensors
User curves ±65 V DC (fix linear) Thermocpl (nc) K [°C] (fix)
PT1000 [°C] (fix) ±75 mV (fix linear) Thermocpl (nc) L [°C] (fix)
NI1000 [°C] (fix) Thermocpl J [°C] (fix) Thermocpl (nc) J [°F] (fix)
PT1000 [°F] (fix) Thermocpl K [°C] (fix) Thermocpl (nc) K [°F] (fix)
NI1000 [°F] (fix) Thermocpl L [°C] (fix) Thermocpl (nc) L [°F] (fix)
0-2400 Ω (fix linear) Thermocpl (nc) J [°C] (fix)
Address and DIP switch setting

Address configuration
DIP switch determinates CAN address for analog inputs and outputs.
Programming Firmware
Firmware upgrade is available via AT-link (TTL). For programming it is necessary to close jumper TEST and
switch OFF and ON the power supply.
For programming use FlashProg PC tool version 4.4 or higher.
LED indication

Flashing Module does not communicate with controller (in case non-zero CAN address)
Fast flashing Detection of CAN communication speed
Power supply is in the range and the communication between Inteli AIN8TC and
controller works properly.
Lights
Or power supply is in range and zero CAN address is set. (in case zero CAN
address module doesn’t communicate with the controller)

Wiring
Measuring resistance – AIN9

2 – wire measurement
Ranges: Pt1000, Ni1000, 0 – 2400 Ω.

Analog input 9 is determined for measuring resistance only.
Technical data
General data
Dimension (W × H × D) 110 × 110 × 46 mm (4.3” × 4.3” × 1.8”)
Weight 248 grams
CAN1 – galvanic separated from power
Interface to controller
supply and measurement,
Analog inputs (not electric separated)

9 channels
0-65 V ± 0.25 % of actual value + ± 120 mV
Measurement is not galvanic separated from
Range
AIN1-AIN4 – Voltage inputs power supply, but IN- is not interconnected with
GND – there is floating measurement.
Accuracy of ± 0,1 % of actual value + ± 100 µV (± 3 °C)

measurement
Range ± 75 mV (nominal) (measurement up to ±80 mV)
AIN5-AIN8 – Voltage inputs Accuracy of ± 0.1 % of actual value + ± 75 µV
measurement Galvanic separated from power supply
Range 0- 2400 Ω
± 0.5 % of actual value + ± 4 Ω Pt1000, Ni1000 ±
AIN9 resistance input Accuracy of
2,5 °C
measurement
It is not galvanic separated from power supply.
Analog output
I 0-20mA /500Rmax. ± 1 % of actual value + ± 200 uA
U 0-10V ± 0.5 % of actual value + ± 50 mV
PWM – 5 V, 200 Hz-2.4kHz 15 mA max.
Galvanic separated from power supply
Galvanic
CAN bus is galvanic separated from the measurement and power supply
separation
Protection IP20
The product is fully supported in firmware IGS-NT 3.1.1 or higher.

For information about support of this module in IGS-NT fw branches and ID-DCU – please read New Feature
Lists.
Inteli AIN8TC
Inteli AIN8TC module is extension module equipped with 8 analog inputs dedicated for thermocouple sensors
only. The module is connected to controller by CAN1A (page 19) bus. It is possible to connect up to 10 Inteli
AIO9/1 external units to one controller.

Image 7.108 Inteli AIN8TC
Image 7.109 Inteli AIN8TC dimensions

Terminals
Analog input 8 analog Inputs

Power Power supply
CAN LED Tx,
Indication transmitted or received data
Rx
Analog inputs
8 channels
Can be configured as thermocouple sensors only
All inputs can be configured to any logical function or protection
Supported sensors
Sensors
Thermocpl J [°C] (fix) Thermocpl (nc) J [°C] (fix)
Thermocpl K [°C] (fix) Thermocpl (nc) K [°C] (fix)
Thermocpl L [°C] (fix) Thermocpl (nc) L [°C] (fix)
Thermocpl J [°F] (fix) Thermocpl (nc) J [°F] (fix)
Thermocpl K [°F] (fix) Thermocpl (nc) K [°F] (fix)
Thermocpl L [°F] (fix) Thermocpl (nc) L [°F] (fix)

Note: “nc” means“ not cold junction compensation (by external sensor).In this case is used internal
temperature sensor on the PCB
CAN address
DIP switch determinates CAN address for analog inputs.
Firmware is upgraded via AT-link (TTL). For programming it is necessary to close jumper TEST.
For programming FlashProg PC tool version 4.2 or higher must be used.
LED indication

Flashing Module does not communicate with controller (in case non-zero CAN address)
Fast flashing Detection of CAN communication speed
Power supply is in the range and the communication between Inteli AIN8TC and
controller works properly.
Lights
Or power supply is in range and zero CAN address is set. (in case zero CAN
address module doesn’t communicate with the controller)
Wiring
Thermocouple

Terminator
Technical data
General data
Protection IP20
Dimensions (WxHxD) 110 × 110 × 46 mm (4.3” × 4.3” × 1.8”)
Weight 237.5 grams
Analog inputs
Number of channels 8, no galvanic separated
Range: ± 100 mV
Voltage Accuracy: ± 0.1 % of actual value + ± 100 µV
(± 3 °C)
I-AOUT8
I-AOUT8 is an extension unit with 8 analog outputs. Each analog output can be switched to
0 to 20 mA DC
0 to 10 V DC
PWM (Pulse With Modulation on 1,2 kHz)
The module is connected to controller by CAN1A (page 19) bus. It is possible to connect up to 4 I-AOUT8
external units to one controller. The corresponding module Address 1 to 4 (default 1) must be set on module
(by Adr.1 and Adr.2 jumpers) and in controller configuration. CAN1 terminating 120 ohm resistor jumper is
connected as default. AGND terminals are on the same potential.

Dimensions
Unit is 35 mm DIN rail mounted.
Connectors
POWER Power supply

CAN 1 CAN1 line
OUT1 - OUT8 Analog output
FLASH AT-link
J1 – J8 Output mode
A1, A2 CAN 1 address
CAN-R Terminating resistor

BOOT Programming
RESET Programming / reset
Tx, Rx CAN 1data
ST Power/module state
Address and jumpers setting
CAN Address
The module CAN address is set by jumpers A1 and A2. Set module CAN address correspondingly to
configuration according table below.
CAN Address A1 A2
1 Open Open
2 Close Open
3 Open Close
4 Close Close
Table 7.2 Setting CAN address
Output mode
Follow the p – I – I – U symbols on the module sticker. There are two equivalent positions for current output.
AOUT Symbol Function
PWM
p
Pulse-Width-Modulation
l 0 to 20 mA DC
U 0 to 10 V DC
Table 7.3 Setting output mode
Firmware upgrade is via AT-link (TTL). For programming it is necessary to close jumper BOOT. RESET
jumper is used to reset the device. Close jumper to reset the device. For programming is used FlashProg PC
tool.
CAN1 termination
I-AOUT8 has own CAN terminating resistor (120 ohm). Close jumper CAN-R to connect terminating resistor
to CAN bus, open jumper CAN-R disconnecting terminating resistor.

Wiring
PWM output
PWM output
1200 Hz
Current
Current output 0 to 20
output 0 to
mA DC
20 mA DC
Current
Current output 0 to 20
output 0 to
mA DC
20 mA DC
Voltage
Voltage output 0 to 10
output 0 to
V DC
10 V DC
Image 7.110 Possible output modes
Technical data
Dimension (W × H × D) 95 × 96 × 43 mm (3.7’ × 3.8’ × 1.7’)

Interface to controller CAN
Output 8 analog, no galvanic separation
Type of analog output

0 to 10V DC ± 1 % , max 5 mA DC
0 to 20 mA DC ± 1 % , max 500 Ω
PWM 1200 Hz, 5V DC level, max 10 mA DC
Analog output refreshment 320 ms
Current consumption max 300 mA (100 mA at 24 V)
RS232 interface TTL, firmware upgrade via AT-link.
Storage temperature -40 °C to +80 °C
Heat radiation 2.5 W
IS-AIN8
IS-AIN8 is input extension module equipped with 8 analog inputs which can be configured to:
Resistor two wire input
Resistor three wire input
Current input

Thermocouple input
Voltage input
All inputs can be configured to any logical function or protection. It is possible to connect up to 10 IS-AIN
external units to one controller. IS-AIN8 is connected to controller CAN1A (page 19) bus.
This module is compatible with MTU ECU-7 at communication speed 125 kbps when uploaded with firmware
1.2.0 and higher.

Terminals
AIN1 – AIN8 8 analog inputs

CAN CAN1 line
POWER Power supply

POWER State indication
Rx, Tx Data transmitted and received on CAN1 line
LDD CAN1 adress
Supported sensors
Sensors
PT100 [°C] (fix) PT100 [°F] (fix) +-1V 4-20mA passive 0-250 ohm
PT1000 [°C] (fix) PT1000 [°F] (fix) 0-2.4V 4-20mA active 0-2400 ohm
NI100 [°C] (fix) NI100 [°F] (fix) 0-5V 0-20mA passive 0-10k ohm
NI1000 [°C] (fix) NI1000 [°F] (fix) 0-10V +-20mA active
Note: It is also possible to use User Curves as sensor.
TC Sensors
CAN Address
CAN 1 address is set by following procedure:
1. Press Address button during IS-AIN8 power supply on to switch to addressing mode.
2. Then repeatedly press or keep pressed address button to adjust required address according to controller
configuration.
3. After setting requested address, release the buttons and wait until the digits blink – it indicates writing of
the change address to EEPROM memory.
CAN 1 Address
1. IS-AIN8 1
2. IS-AIN8 2
3. IS-AIN8 3
4. IS-AIN8 4
5. IS-AIN8 5
6. IS-AIN8 6
7. IS-AIN8 7

8. IS-AIN8 8
9. IS-AIN8 9
10. IS-AIN8 0
Table 7.4 Table of recommended CAN1 address setting
SW version check
Let suppose IS-AIN8 of SW version 1.4. Shortly press address button. Following sequence appears on the
display: number “1”, one second pause, number “4”, two second pause, number “1”, one second pause,
number “4”, two second pause and finally IS-AIN8 actual address. Error message (e.g. SD BOUT2) appears
on Controller screen when Binary input or output Address x is configured but corresponding unit is not
recognized (no message is received from CAN bus). Check IS configuration and corresponding external IS-
AIN8, IS-BIN8/16 unit address setting.
LED indication
Power LED Address LDD

Lighting Blink Lighting Blink
Power supply and CAN CAN1 address is adjusted
Displaying current Displaying current
address are with no different in IS-AIN8 and in
CAN1 address SW version
problems controller
Table 7.5 LED / LDD status
Tx Rx
Any data are
Any data are transmitted Data are transmitted on the CAN1 Data are received
received on the
on the CAN1 line line on the CAN1 line
CAN1 line
Table 7.6 Tx/Rx LED status
Wiring

Note: CAN bus line has to be terminated by 120 Ω resistors on the both ends.
For longer distances is recommended to connect CAN COM terminals between all controllers and cable
shielding to the ground in one point!External units can be connected on the CAN bus line in any order, but
line arrangement (no tails no star) is necessary.
Recommended CAN bus data cables see in Chapter Technical data.
IG-MU and IG-IB units are connected to CONTROLLER CAN2 bus.
Select sensor characteristic from the list or define user sensor characteristic in PC configuration tool.
Resistor sensor input – two wire connection.

Range 0 to 2400 Ω.
Pt100, Pt1000, Ni100, Ni1000
D terminal is shielding
Resistor sensor input – three wire connection.

Range 0 to 2400 Ω.
Pt100, Pt1000, Ni100, Ni1000 – recomended.
Passive current sensor (current source is in IS-AIN8)

Range 0 to +20 mA or 4 to + 0 mA
Active current sensor (current source is in sensor)

Range –20mA to +20 mA or 4 to +20 mA
Thermocouple J, K, L D terminal is shielding

From IS-AIN8 hardware version 5.1 can be B terminal
grounded to frame

Voltage input
Range 0 to + 2500 mV.
Voltage range is 0 to ±1000 mV.
For 10 V input voltage range connects external

resistors R1, R2 and select sensor characteristic 10 V
R1=10 kΩ, R2=2.7 kΩ.
Note: If the thermocouples are connected to IS-AIN8, appropriate jumpers must be removed (see rear
sticker). (jumpers are placed under the cover)
Cold Junction Compensation (CJC)

Cold junction compensation is also called reference junction compensation. When measuring temperature
using thermocouples, the reference terminal may not be held at 0°C, but at the surrounding temperature of
T1°C instead. Without any compensation, the thermocouple output will be changed (reduced) by T1°C. This
is compensated by adding potential difference to the IS-AIN8 corresponding to T1°C.

2
Example 1 shows the correct temperature measurement. The 3rd metal (the cable between IS-AIN8 and
thermocouple) is connected in cold bath which temperature is 0°C. This is very difficult to provide in real
application.
thermocouple) is connected in ambient environment which temperature is not 0°C, but T1°C. Resultant
temperature is correct, because is compensated by internal IS-AIN8 temperature sensor. The
temperature of IS-AIN8 and junction is the same T-T1+T1 (reduced and compensated by T1).
Example 3 shows the incorrect temperature measurement. The 3rd metal (the cable between IS-AIN8
and thermocouple) is connected in ambient environment which temperature is not 0°C, but T1°C.
Resultant temperature is T-T1 (reduced by T1). Internal IS-AIN8 compensation should not by used
because measures T2 temperature, not T1!
thermocouple) is connected in ambient environment which temperature is not 0°C, but T1°C. Resultant
temperature is correct, because is compensated by external temperature sensor, T+T1 (reduced and
compensated by T1).

Cold Junction Compensation (CJC) settings
Example 1 is not a practical in regard of ice bath. In this case should any of not compensated (nc) sensors
for analog input be selected base on used thermocouple.
Example 2 is a standard wiring between thermocouple sensor and IS-AIN8. IS-AIN8 is placed in the
same ambient temperature as thermocouple terminal; it means IS-AIN8’s internal temperature sensor
measures the same temperature as is on thermocouple terminal. In this case, could junction
compensation is done by IS-AIN8 itself. Any of standard (compensated) sensors should be selected.
Example 3 is a standard wiring between thermocouple sensor and IS-AIN8. Regardless selected type of
sensor the resultant temperature will be incorrect
Not compensated sensor – temperature T1 is not calculated
Compensated sensor – IS-AIN8 measures different T2 temperature, not T1
Example 4 External temperature T1sensor is included. Resultant temperature is correct if
Any of not compensated sensors (nc) is selected
External sensor has a function Cold Temp 1

Note: LAI (logical analog input) Cold Temp 1 compensates every of 8 thermocouples inputs of IS-AIN8 on
address 1IS-AIN8 on address 2 – 10 is not compensated by this LAI Cold Temp1.
Any of non thermocouple configured input is not compensated anyway
Any of non thermocouple input with sensor adjusted as compensated is not compensated by external
compensation (IS-AIN8 compensates it itself)
IS-AIN8 on address 2 – 10 is not compensated by this LAI Cold Temp1.
LAI Cold Temp 2 compensates every of 8 thermocouples inputs of IS-AIN8 on address 2, etc.
Up to 32 (Cold Temp 1-4 times 8 analog input of IS-AIN8) may by compensated by external sensor.
Even only one external sensor may be configured for more than one LAI Cold Temp.
Technical data
Dimension (W × H × D) 146 × 160 × 46 mm (5.79’ × 6.6’ × 1.83’)

Interface to Controler CAN1
Analog inputs 8, galvanic separated from power supply, 16 bit *
Current consumption 250 mA at 24 V
Protection front panel IP20
Humidity 95% without condensation
Heat radiation 2W
* each analog input can be software configured to:

Measuring range Accuracy
From To
Resistance 0Ω 2400 Ω ± 0.5 %
0Ω 250 Ω ± 1.0 %
Current Passive 0/4 mA 20 mA ± 0.5 %
Active 4 mA 20 mA ± 0.5 %
Active 0 mA ± 20 mA ± 0.5 %
Voltage Thermocouples J, K, L type ± 0.2 %
0 mV 100 mV ± 0.2 %
- 1000 mV + 1000 mV ± 0.5 %
0 mA 2500 mV ± 0.5 %
Standard conformity
Low Voltage Directive EN 61010-1:95 +A1:97
EN 50081-1:94, EN 50081-2:96
Electromagnetic Compatibility
EN 50082-1:99, EN 50082-2:97

IS-AIN8TC
IS-AIN8 is input extension module equipped with 8 analog inputs dedicated for thermocouple sensors only.
All inputs can be configured to any logical function or protection. It is possible to connect up to 10 IS-AIN8TC
external units to one controller. IS-AIN8TC is connected to controller CAN1A (page 19) bus.

Terminals
AIN1 – AIN8 8 analog inputs

CAN CAN1 line
POWER Power supply
POWER State indication
Rx, Tx Data transmitted and received on CAN1 line
LDD CAN1 address
Supported sensors
Sensors
CAN Address
CAN1 address is set by following procedure:

1. Press Address button during IS-AIN8TC power supply on to switch to addressing mode.
2. Then repeatedly press or keep pressed address button to adjust required address according to controller
configuration.
3. After setting requested address, release the buttons and wait until the digits blink – it indicates writing of
the change address to EEPROM memory.
CAN11 Address
1. IS-AIN8TC 1
2. IS-AIN8TC 2
3. IS-AIN8TC 3
4. IS-AIN8TC 4
5. IS-AIN8TC 5
6. IS-AIN8TC 6
7. IS-AIN8TC 7
8. IS-AIN8TC 8
9. IS-AIN8TC 9
10. IS-AIN8TC 0
SW version check
Shortly press address button. Following sequence appears on the display: number “1”, one second pause,
number “4”, two second pause, number “1”, one second pause, number “4”, two second pause and finally IS-
AIN8TC actual address.
Error message (e.g. SD BOUT2) appears on Controller screen when Binary input or output Address x is
configured but corresponding unit is not recognized (no message is received from CAN bus). Check IS
configuration and corresponding external IS-AIN8TC, IS-BIN8/16 unit address setting.
LED indication
Power LED Address LDD

Power supply and CAN CAN1 address is
Displaying current Displaying current SW
address are with no adjusted different in IS-
CAN1 address version
problems AIN8TC and in controller
Table 7.8 LED/LDD status
Tx Rx
Dark Blink Dark Blink
Any data are transmitted Data are transmitted on Any data are received Data are received on
on the CAN1 line the CAN1 line on the CAN1 line the CAN1 line
Table 7.9 Tx/Rx LED status

Wiring
Note: CAN bus line has to be terminated by 120 ohm resistors on the both ends.
shielding to the ground in one point!
External units can be connected on the CAN bus line in any order, but line arrangement (no tails no star) is
necessary.
IG-MU and IG-IB units are connected to CONTROLLER CAN2 bus.
Select sensor characteristic from the list or define user sensor characteristic in PC configuration tool.
Thermocouple J, K, L, D terminal is shielding
Cold Junction Compensation (CJC) settings

Please have a look at Cold Junction Compensation (CJC) (page 1237) IS-AIN8 chapter.
Technical data
Dimension (W × H × D) 110 × 110 × 46 mm (4.3” × 4.3” × 1.8”)

Weight 237.5 grams
Interface to controller CAN1
Analog inputs (not electric separated) 8, no galvanic separated

Measuring ±100 mV
Accuracy ± 0.1 % of actual value + ± 100 µV (± 3 °C)

Internal sensor for measuring cold junction - ±1 °C in temperature range -20 °C ÷ +70
Accuracy °C
CANbus is galvanic separated from the
measurement and power supply.
All analog inputs are galvanic separated
Galvanic separation
from power supply.
Analog inputs are not galvanic separated
between channels
Protection IP20
Heat radiation 2W
IS-BIN16/8
IS-BIN16/8 is an extension module with 16 binary inputs (galvanic separated) and 8 binary output (galvanic
separated), 2 pulse inputs (frequency measurement or pulse counting). All I/O can be configured to any
logical function or protection. It is possible to connect up to 7 IS-BIN16/8 external units to one controller.
External modules IS-BIN16/8 is connected to controller CAN1A (page 19) bus. To operate external modules:
Connect all external modules to CAN1 bus line
On each module adjust I/O CAN1 address in the range of 1 to 7 for IS-BIN16/8 output, 1,3,5,7,9,11,13 for
IS-BIN18/8 inputs
In case of use generic module in configuration you can set CAN address from 1 – 12
In case of set 0 CAN address - inputs/ outputs are deactivated
Input output address is displayed on the front panel LCD’s
Use PC configuration tool to configure controller according external modules setting
IS-BIN16/8 module has two separate CAN1 addresses for binary inputs Group 1, Group 2 and binary output
Group (total three addresses). The CAN1 address for BI Group 1 and for BO Group 2 can be adjusted on the
IS-BIN16/8. The address for BI Group 2 is set automatically to the address following BI Group 1.
Note: CAN address 0 disables corresponding CAN message (Group data are not send).

Terminals
CAN CAN1 line

BINARY INPUTS 16 binary inputs
BINARY OUTPUT 8 binary output
RPM1, RPM2 2 frequency inputs
POWER Power supply
INPUTS LDD CAN address
OUTPUT LDD CAN address
CAN Address
CAN 1 address is setting by following procedure:
Press Address buttons (for INPUTS address and OUTPUT address) during IS-BIN8 power supply on to
switch to addressing mode.
Then repeatedly press or keep pressed address button to adjust required address according to
CONTROLLER configuration.
After setting requested address, release the buttons and wait until the digits blink – it indicates write the
changed address to EEPROM memory.
CAN 1 Address
Inputs Output
1. IS-BIN16/8 1 1
2. IS-BIN16/8 3 2
3. IS-BIN16/8 5 3

4. IS-BIN16/8 7 4
5. IS-BIN16/8 9 5
6. IS-BIN16/8 11 6
7. IS-BIN16/8 16 7
SW version check
Let suppose IS-AIN8 of SW version 1.4. Shortly press address button. Following sequence appears on the
display: number “1”, one second pause, number “4”, two second pause, number “1”, one second pause,
number “4”, two second pause and finally IS-AIN8 actual address.
Error message (e.g. SD BOUT2) appears on Controller screen when Binary input or output Address x is
configured but corresponding unit is not recognized (no message is received from CAN bus). Check IS
configuration and corresponding external IS-AIN, IS-BIN unit address setting.
LED indication
Tx Rx
Dark Blink Light Dark Blink Light
Any data are Data are Any data are Data are
transmitted on the transmitted on the received on the received on the
CAN1 line CAN1 line CAN1 line CAN1 line
Table 7.11 Tx / Rx LED status
Wiring
Image 7.111 CAN bus line has to be terminated by 120 ohm resistors on the both ends.
Note: CAN bus line has to be terminated by 120 ohm resistors on the both ends.
shielding to the ground in one point!
External units can be connected on the CAN bus line in any order, but line arrangement (no tails no star) is
necessary-

Binary inputs
There are two groups of eight Binary inputs BI1 to BI8 and BI9 to BI16. Each group has a separate Common
terminal COM1 and COM2. The Common terminal can be connected to positive or negative pole – see
following drawing. Binary inputs are galvanically separated from IS-BIN16/8 power supply.
Note: See the Theory of binary inputs and outputs (page 1191) (Pull Up,Pull Down, High side switch,
Low side switch).
Binary inputs Common terminal is connected to Binary inputs common terminal is connected to
positive supply terminal, Binary inputs contacts are negative supply terminal, Binary inputs contacts are
closed to negative supply terminals. closed to positive supply terminals.
Input voltage range for opened contact is from 8 VDC to Power supply VDC. Input voltage range for closed
contact is from 0 to 2 VDC. Voltage level is defined between Binary input and Binary input COM terminal and
does not depend on “positive” or “negative” connection.
IMPORTANT: Impulse inputs are not supported by the controller.
Binary output
The Common terminal can be connected to positive or negative pole (HW3.0 only) – see following drawing.
Binary outputs are galvanic separated from IS-BIN16/8 power supply (have a look at technical data). The
maximum load values are 0.5 A / 36V for one output.
Binary output common terminal is connected to Binary output common terminal is connected to
negative supply terminal, Binary output contacts are positive supply terminal, Binary output contacts are
closed to positive supply terminals. closed to negative supply terminals.

Power supply fusing
A (2) respectively (1) amp fuse should be connected in-line with the power to the controller and modules,
these items should never bee connected directly to the starting battery.
Take care for proper controller, extension units and relays power supply fusing. Fuse value and type depends
on number of connected devices and wire length.
Controller or unit Fuse

Controller T1A or T2A
IS-AIN8 T2A
IS-BIN16/8 T1A
Table 7.12 Recommended fuse (not fast) types
For more extension units use separate fusing according to the table above.
Controller power supply should never be connected to starter terminals.
Technical data
Dimension (W × H × D) 146 × 160 × 46 mm (5.79’ × 6.6’ × 1.83’)

Interface to controller CAN1
Binary inputs (galvanic separated)

Voltage level is defined between binary input and binary input COM terminal
Number of inputs 8+8
Input resistance 3000 Ω

Input voltage range 0-36 VDC
Input voltage level for open contact 8 to Power supply VDC
Input voltage level for close contact 0 to 2 VDC
Frequency inputs* (for IS-CU only)

RPM1
Type of sensor Magnetic pick-up
Minimum input voltage 2 Vpk-pk (from 4 Hz to 4 kHz)
Maximum input voltage 50 Veff
Maximum measured frequency 8 kHz (min. input voltage 6Vpk-pk), frequency mode
RPM2
Type of sensor Contact or Active sensor
Minimal pulse width 10 ms, integration mode
Maximum measured frequency 60 Hz, integration mode
Relays outputs (galvanic separated) only HW 3.0 (non galvanic separated) HW 2.1
Number of output 8
Maximum current 0.5A DC
Maximum switching voltage 36 VDC
Protection front panel IP20
Current consumption 250 mA** at 24 V
Humidity 95% without condensation
Heat radiation 2W
Standard conformity
Number of output 8
Low Voltage Directive EN 61010-1:95 +A1:97
EN 50081-1:94, EN 50081-2:96
Electromagnetic Compatibility
EN 50082-1:99, EN 50082-2:97
*RPM1, RPM2 are available in IS-CU only **During powering up current can be up to 1.5A

Intelineo 6000 1.3.0 Global Guide

Uploaded by

Copyright:

Available Formats

Intelineo 6000 1.3.0 Global Guide

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

Intelineo 6000 1.3.0 Global Guide

Uploaded by

Copyright:

Available Formats

InteliNeo

Copyright © 2023 ComAp a.s.

InteliNeo 6000 1.3.0 Global Guide 2

4.4.6 Binary Outputs 66 5.4.14 E-STOP 143

4.4.7 E-Stop 67 5.4.15 Event History 145

4.4.8 Analog Inputs 67 5.4.16 Exercise Timers 149

4.4.9 Analog Outputs 70 5.4.17 Firewall 157

4.4.11 USB 74 5.4.19 Hot Swap Redundancy 160

4.4.12 Ethernet 75 5.4.20 I/O Configuration 166

4.4.13 Cellular Connection 76 5.4.21 Load Shedding 170

4.5 External display 79 5.4.22 Loss of Mains (Decoupling)

5.4.5 Breaker Control 126 5.4.41 User Setpoints 228

InteliNeo 6000 1.3.0 Global Guide 3

6.3.1 Power reduction by over frequency - 7.2.1 SNMP 309

6.3.3 Return from over/under frequency 296

InteliNeo 6000 1.3.0 Global Guide 4

InteliNeo 6000 1.3.0 Global Guide 5

6 back to Table of contents

1.1 Declaration of Conformity

Unique identifier: INEO6000BBB

Tel: +1 815 636 2541

FCC Compliance Statement

1.2 Clarification of Notation

InteliNeo 6000 1.3.0 Global Guide 6

1.3 About this Global Guide

1.4 Legal notice

InteliNeo 6000 1.3.0 Global Guide 7

1.5 Used open source software:

InteliNeo 6000 1.3.0 Global Guide 8

Copyright (c) 2011, 2013 Mutsuo Saito,

Copyright (c) 2013-2015, Scott Vokes

InteliNeo 6000 1.3.0 Global Guide 9

1.6 General warnings

1.6.2 SW and HW versions compatibility

1.6.3 Dangerous voltage

1.6.4 Adjust the setpoints

InteliNeo 6000 1.3.0 Global Guide 10

* extension module IGL-RA15 required

1.8 Certifications and standards

EN 61000-6-4 EN 60068-2-2 (70 °C/16 h) UKCA

EN 61010-1 EN 60068-2-6 (2÷25 Hz / ±1,6 mm; 25÷100 Hz / 4,0

EN 60068-2-30 (25/55 °C, RH 95%, 48 h)

1.9 Document history

InteliNeo 6000 1.3.0 Global Guide 11

InteliNeo 6000 1.3.0 Global Guide 12

InteliNeo 6000 1.3.0 Global Guide 13

6 back to Table of contents

2.1 General description

2.1.1 The key features of InteliNeo 6000

InteliNeo 6000 1.3.0 Global Guide 14

1. Connect controller to power supply

Password = serial number of your controller

5. Adding another users

InteliNeo 6000 1.3.0 Global Guide 15

2.3 Measurement methods

2.3.1 True RMS measurement

2.3.2 Symmetrical components

InteliNeo 6000 1.3.0 Global Guide 16

2.4.1 AC measurement settings

AC Current measurement settings