Intelineo 530 Bess 1.0.0 Global Guide

InteliNeo 530
BESS
Controller For Parallel Hybrid
Microgrid Applications
SW version 1.0.0
1 Document information 5
2 System overview 13
3 Applications overview 37
4 Installation and wiring 38
5 Controller setup 68
6 Communication 236
7 Technical data 259
8 Appendix 261
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 5 2.7.2 Configuration parts 20
1.1 Declaration of Conformity 5 2.8 PC tools 21
1.2 Clarification of Notation 5 2.8.1 InteliConfig 21
1.3 About this Global Guide 6 2.8.2 WebSupervisor 21
1.4 Legal notice 6 2.8.3 WinScope 1000 22
1.5 Used open source software: 7 2.8.4 InteliSCADA 22
1.6 General warnings 9 2.9 Plug-in modules 22
1.6.1 Remote control and programming 9 2.9.1 CM3-Ethernet 22
1.6.2 SW and HW versions compatibility 9 2.9.2 CM2-4G-GPS 23
1.6.3 Dangerous voltage 9 2.9.3 CM-RS232-485 23
1.6.4 Adjust the setpoints 9 2.9.4 EM-BIO8-EFCP 23
1.7 Functions and protections 10 2.10 Displays 23
1.8 Certifications and standards 10 2.10.1 InteliVision 5.2 24
1.9 Document history 10 2.10.2 InteliVision 10Touch 24
1.10 Symbols in this manual 11 2.10.3 InteliVision 13Touch 25
2.10.4 InteliVision 18Touch G1/G2 25
2 System overview 13
2.11 CAN Extension Modules 26
2.1 General description 13
2.11.1 Inteli AIN8 26
2.1.1 The key features of InteliNeo 530
2.11.2 Inteli IO8/8 27
BESS 13
2.11.3 IGL-RA15 27
2.2 Getting Started 15
2.11.4 IGS-PTM 28
2.3 Measurement methods 16
2.11.5 Inteli AIO9/1 28
2.3.1 True RMS measurement 16
2.11.6 Inteli AIN8TC 29
2.3.2 Symmetrical components 16
2.11.7 I-AOUT8 29
2.4 AC measurement 17
2.11.8 IS-AIN8 29
2.4.1 AC measurement settings 17
2.11.9 IS-AIN8TC 30
2.4.2 Frequency measurement accuracy
2.11.10 IS-BIN16/8 30
and resolution 17
2.12 CAN Communication Modules 31
2.4.3 PF measurement and evaluation 17
2.12.1 I-CR 31
2.4.4 Waveform distortion measurements 18
2.13 Other Modules 31
2.5 DC measurement 18
2.13.1 Inteli DC4/4 31
2.5.1 DC Voltage Measurement 18
2.14 Virtual modules 32
2.5.2 DC Current Measurement 19
2.14.1 Shared modules 32
2.6 Communication peripherals 19
2.7 Configurability and monitoring 19
3 Applications overview 37
2.7.1 Supported configuration and
3.1 MINT 37
monitoring tools 19
InteliNeo 530 BESS 1.0.0 Global Guide 2

4 Installation and wiring 38 5.4.5 Configuration Override 115
4.1 Package content 38 5.4.6 Control Groups 116
4.2 Controller installation 39 5.4.7 Crash Dump 116
4.2.1 Dimensions 39 5.4.8 Distributed Power Management
4.2.2 Mounting 39 Signals 117
4.3 Terminal Diagram 40 5.4.9 E-STOP 122
4.4 Recommended wiring 42 5.4.10 Event History 124
4.4.1 General 43 5.4.11 Exercise Timers 127
4.4.2 Grounding 44 5.4.12 Firewall 134
4.4.3 Power supply 44 5.4.13 Forced Value 135
4.4.4 Measurement wiring 46 5.4.14 I/O Configuration 137
4.4.5 Binary Inputs 56 5.4.15 Load Shedding 142
4.4.6 Binary Outputs 57 5.4.16 Loss of Mains (Decoupling)

Protections 144
4.4.7 E-Stop 58
5.4.17 Modbus Client (Master) 145
4.4.8 Analog Inputs 58
5.4.18 Multiple ECU 150
4.4.9 CAN bus and RS485 wiring 61
5.4.19 Operating Modes 150
4.4.10 USB 64
5.4.20 PLC - Programmable Logic
4.4.11 Ethernet 65
Controller 152
4.5 External display 65
5.4.21 Power Formats And Units 163
4.5.1 InteliVision Displays 65
5.4.22 Protections 164
4.6 Maintenance 66
5.4.23 Sensor Curves 175
4.6.1 Backup battery replacement 66
5.4.24 Service Timers 177
5 Controller setup 68 5.4.25 System Start/Stop 178
5.1 Operator Guide 68 5.4.26 User Buttons 179
5.1.1 InteliVision 5.2 68 5.4.27 User Management And Data Access

Control 181
5.2 Controller configuration and PC tools
connection 98 5.4.28 User Setpoints 187
5.2.1 USB 98 5.4.29 Voltage Phase Sequence Detection 190
5.2.2 Ethernet 99 5.5 Application related functions 191
5.3 Default configuration 104 5.5.1 BESS Charging/Discharging Control 191
5.3.1 Binary inputs 104 5.5.2 BESS Forced power 192
5.3.2 Binary outputs 105 5.5.3 BESS Operation States 193
5.3.3 Analog inputs 105 5.5.4 BESS Operation Area 194
5.3.4 Analog Outputs 105 5.5.5 BESS Precharge Types 194
5.4 General Functions 105 5.5.6 InteliNeo 530 as Generic BESS

Controller 198
5.4.1 Alarm Management 106
5.5.7 BESS Stabilization 199
5.4.2 Breaker Control 109
5.5.8 Connecting To Load 200
5.4.3 CAN Bus Log 114
5.5.9 Deenergized DC Bus after BCB is 205
5.4.4 Configuration Lock 115

Opened in PQ Mode
5.5.10 Multiple Island Operation 206
5.5.11 Output Control – Frequency/Load 206
5.5.12 Output Control - Voltage/PF 208
5.5.13 Parallel To MainsOperation - MINT
Application 210
5.5.14 Power Management 213
5.5.15 Regulation Loops 233
5.5.16 Sunrise/Sunset 235
6 Communication 236
6.1 PC 236
6.1.1 Direct communication 236
6.1.2 Remote communication 237
6.2 Connection to 3rd party systems 239
6.2.1 SNMP 239
6.2.2 Modbus-RTU, Modbus/TCP 241
7 Technical data 259
8 Appendix 261
8.1 Controller objects 261
8.1.1 List of controller objects types 261
8.1.2 Renameable controller objects 262
8.1.3 Setpoints 262
8.1.4 Values 531
8.1.5 Application Curves 638
8.1.6 Logical binary inputs 641
8.1.7 Logical binary outputs 687
8.1.8 Logical analog inputs 731
8.1.9 Fixed Protection States 740
8.1.10 User Protection States 746
8.1.11 PLC 749
8.2 Alarms 804
8.2.1 Alarm levels in the controller 804
8.2.2 Alarms level 1 804
8.2.4 Other alarms 840
8.3 Modules 883
8.3.1 CAN modules 883
6 back to Table of contents

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

Supplier's Declaration of Conformity
47 CFR § 2.1077 Compliance Information
Unique identifier: INEO530BBAANU
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 530 BESS controllers family that shall be followed
during installation and maintenance of the controllers.
This manual provides general information how to install and operate InteliNeo 530 BESS 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 807) 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. The compatibility check is performed on two
levels.
The controller itself checks its hardware identification against the uploaded configuration at start up and
evaluates the match.
The configuration tool InteliConfig performs a compatibility check when the firmware upload menu is opened and
displays the compatible software for the connected controller.
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 any part of the system.
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) UKCA
EN 61000-6-4 EN 60068-2-2 (70 °C/16 h)
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)
1.9 Document history

Revision number Related sw. version Date Author
Jakub Slavata
1 1.0.0 10.11.2023
Filip Sulek

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
GSM
Energy simplified Resistor
Storage adjustable
Current GSM
Resistive
Binary measuring modem
sensor
output RPTC
Current
IG-AVRi
Breaker measuring RS 232
contact male
IG-AVRi
Danger
TRANS RS 232
Breaker
female
contact Danger -
Electric Jumper
Shaft
Breaker Hazard
Generator
DC to AC Load
Breaker Inverter Starter
Mains Switch -
Diode
Breaker manually
operated
Ethernet Mains
Capacitor male Transformer
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 13
2.2 Getting Started 15
2.3 Measurement methods 16
2.4 AC measurement 17
2.5 DC measurement 18
2.6 Communication peripherals 19
2.7 Configurability and monitoring 19
2.8 PC tools 21
2.9 Plug-in modules 22
2.10 Displays 23
2.11 CAN Extension Modules 26
2.12 CAN Communication Modules 31
2.13 Other Modules 31
2.14 Virtual modules 32
2.1 General description

The InteliNeo 530 BESS is an advanced energy management system for directly integrating the Battery
Management System (BMS) with the Power Conversion System (PCS) within a Battery Energy Storage System
(BESS) as well as control, monitoring and protection of the auxiliary systems to ensure the highest level of
Storage System performance.
2.1.1 The key features of InteliNeo 530 BESS

Grid forming (V/F), grid following (P/Q) and droop (VSG) modes supported
BMS to PCS integration via Modbus RTU/TCP device list
Control, monitoring and protection of auxiliary systems within the battery storage system
AC and DC voltage and current sensing
AC and DC startup sequence and breaker control
Compatible load/Var sharing and power management with other ComAp solutions
Alarm and fault management of all components within the battery storage system
Event-based history for fast and easy troubleshooting
Slots for plug-in modules for 4G and GPS, additional Ethernet port, RS232/485 connection or additional
binary inputs/outputs
Secure Modbus TCP interface for higher level external control systems
Built-in PLC interpreter with the use of ComAp's free PLC Editor
Remote control and monitoring of your battery storage system with WebSupervisor, our cloud-based fleet
management tool
AirGate 2.0 for easy connection to your equipment remotely, without worrying about your asset’s IP
address User-defined protections and setpoints on top of default parameters

Keeping your business and data as safe as possible with design to the ISA 62443 level 2 - level 3 security
requirements

2.2 Getting Started
Congratulations to your new InteliNeo 530 BESS 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 40) 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 807). 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 183). 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 185).

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

The InteliNeo 530 BESS 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 +Bus Voltage (page 554) and +Bus Voltage
Relative (page 554).
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 530 BESS 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 287) and Bus Voltage Input
Range (page 289).
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 282), BESS CT Ratio Sec (page 283), Aux CT Ratio PrimC (page 283) and Aux CT Ratio Sec (page
284).
2.4.2 Frequency measurement accuracy and resolution

The resolution of the measurement is in mHz within a 45–75 Hz range. Values Bus Frequency (page 552)
and BESS Frequency (page 547) 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 Local Base Power Factor (page 277) with a 0.001
resolution and #System Power Factor (page 278) with a 0.01 resolution.
Values for the Power factor are:

BESS Power Factor (page 544), BESS Load Character (page 544)
BESS Power Factor L1 (page 544), BESS Load Character L1 (page 544)
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 545)
Current Total Harmonic Distortion
where Ik is the True RMS current of kth harmonic.

Related values:
BESS Current THD L1 (page 546)
2.5 DC measurement
With InteliNeo 530 BESS it is possible to measure DC quantities using external module Inteli DC4/4 (page 31).
Module measures DC current and DC voltages and converts them into analog signals. InteliNeo 530 BESS use
dedicated LAIs with sensor curve to convert received signals into DC quantities. You can use for
DC Measurement on AIN 1 .. AIN 4. Other ways how to optain DC values are using Modbus, PLC ect., which
requires to map dedicated LAIs in controller configuration.
2.5.1 DC Voltage Measurement

To measure DC voltage use LAIs ES VOLTAGE MEAS (PAGE 737), PCS VOLTAGE MEAS (PAGE 738). You can
see measured values in ES Voltage Meas (page 538) and PCS Voltage Meas (page 540). Terminals for
voltage measurement on Inteli DC4/4 (page 31) are 18 - 14 for Channel 1 and 9 -13 for Channel 2.

2.5.2 DC Current Measurement
To measure DC current you can use PCS CURRENT MEAS (PAGE 738). Measured values you can see in PCS
Current Meas (page 540). Terminals for current measurement on Inteli DC4/4 (page 31) are 18 - 17 for
Channel 1 and 9 -10 for Channel 2.
2.6 Communication peripherals

InteliNeo 530 BESS contains 1x Ethernet terminal, 2x CAN terminals, 1x RS485 terminal 1x USB type A
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
CAN1 CAN bus wiring
combinations of modules (page 883) and Multiple ECU (page
(page 61)
150) for more information.
CAN2 This terminal is used for CAN intercontroller communication.
This terminal is used for Modbus-RTU, Modbus/TCP (page 241) RS485 wiring
RS485
communication. (page 62)
USB Type A USB host – FW upgrade, download/upload configuration.
Controller
configuration
This terminal is used for UART communication eg. InteliConfig,
USB Type B and PC tools
WinScope1000, etc.
connection
(page 98)
The Ethernet port is considered as Untrusted interface. It is used for
remote communication eg. InteliConfig, WinScope1000, etc. The Ethernet (page
Ethernet
user account with password has to be used in order to connect to 65)
the controller. It is also used for SMTP, SNMP and Modbus server.
You can see layout of the peripherals in the chapter Terminal Diagram (page 40).
2.7 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.7.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.7.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 104), 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.8 PC tools
2.8.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.8.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.8.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.8.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.9 Plug-in modules

2.9.1 CM3-Ethernet
Internet/Ethernet module including web server.
10/100 Mbit interface over RJ45 socket

Remote control and monitoring of the controller
via InteliConfig, WebSupervisor
Modbus TCP support
Full SNMP support including traps (v1 & v2c)
Active e-mail sending
AirGate 2.0 technology support for easy
connection – no need of public and static IP
address

2.9.2 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.3 CM-RS232-485
Communication module with two communication ports.
RS232 and RS485 interface
MODBUS
Serial connection to InteliConfig
2.9.4 EM-BIO8-EFCP
Input and binary input/output extension module.
Up to 8 additional configurable binary inputs or
outputs
2.10 Displays
Remote Displays / Panel PC Displays

2.10.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.10.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.10.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.10.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.11 CAN Extension Modules
2.11.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.11.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.11.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.11.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.11.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.11.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.11.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.11.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.11.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.11.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.12 CAN Communication Modules

2.12.1 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.13 Other Modules

2.13.1 Inteli DC4/4
Module for DC Voltage/Current measurement
Unipolar voltage measurement
2 galvanically isolated input measuring
channels, both having voltage + current
Analog Inputs
4 channels – 2 for Voltage and 2 for Current

measurement
Voltage input up to 1500 V DC – direct
measurement
Current loop input: Measurement with
external shunt up to 3000 A DC (0-100 mV
shunt voltage range)
Analog Outputs
4 channels – 2 for Voltage and 2 for Current

measurement
4 .. 20 mA current loop output

2.14 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 292).
2.14.1 Shared modules

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.
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 882)- is activated in case that more than just one controller has
configured SHBOUT module with same module index in CAN topology.
Proper alarm from a range SHBIN 1 (page 881) to SHBIN 6 (page 882) is activated in case that data are not
received.
Binary Inputs
SHBIN-1 (page 629)
Note: Value above is related to virtual module SHBIN-1. See values for other modules here: Group: SH
Modules (page 629)

Configuration
Image 2.2 Configuration of shared module SHBIN
SHBOUT
SHBOUT virtual modules share binary values to other controllers via CAN intercontroller communication. 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.
Binary Outputs
SHBOUT-1 (page 632)

Note: Value above is related to virtual module SHBIN-1. See values for other modules here: Group: SH
Modules (page 629)
Configuration
Image 2.3 Configuration of shared module SHBOUT
Analog shared modules

SHAIN
SHAIN virtual modules receives analog values from other controllers via CAN intercontroller communication.
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 881) is activated in case that more than just one controller has configured
SHAOUT module with same module index in CAN topology.
Proper alarm from a range SHAIN 1 (page 880) to SHAIN 2 (page 880) is activated in case that data are not
received.
Analog Inputs
SHAIN-1 1 (page 635)
Note: Value above is related to virtual module SHAIN-1. See values for other modules here: Group: SH
Modules (page 629)

Configuration
Image 2.4 Configuration of shared module SHAIN
SHAOUT
SHAOUT virtual modules share analog values to other controllers via CAN intercontroller communication. 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.

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

3 Applications overview
3.1 MINT 37
3.1 MINT
The typical scheme of Multiple Island-Parallel application without mains is shown below. The InteliNeo 530
BESS controller controls two breakers, the BESS breaker and Energy Storage breaker. Feedback from both
breakers is required.
6 back to Applications overview

4 Installation and wiring
4.1 Package content 38
4.2 Controller installation 39
4.3 Terminal Diagram 40
4.4 Recommended wiring 42
4.5 External display 65
4.6 Maintenance 66
4.1 Package content

The package contains:
Controller InteliNeo 530 BESS
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
Note: Dimension x depends on plug-in module.
Note: Dimensions are in millimeters.
Image 4.1 Controller dimensions
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.

Mounting in switchboard doors
The controller should be mounted onto the switchboard door. Requested cutout size is 187 × 132 mm. Use
the screw holders delivered with the controller to fix the controller into the door as described in pictures below.
Recommended torque for holders is 0.15 N·m.
Image 4.2 Controller mounting in the switchboard doors
4.3 Terminal Diagram

BINARY
CURRENT BESS / VOLTAGE BESS / MAINS VOLTAGE
AOUT1
MAINS AUX MAINS / BESS INPUTS
T30 COM T38 N T42 N T46 BI1 T55 COM
T31 L1 T39 L1 T43 L1 T47 BI2 T56 OUT
T32 L2 T40 L2 T44 L2 T48 BI3 CAN1
T33 L3 T41 L3 T45 L3 T49 BI4 T29 H

T34 COM T50 BI5 T28 COM
T35 L1 T51 BI6 T27 L
T52 BI7
T53 BI8

CAN2 ANALOG BINARY
E-STOP RS485
INPUTS OUTPUTS
T26 H T22 AI4 T12 BOUT8 T04 E-STOP T57 B
T25 COM T21 AI3 T11 BOUT7 POWER SUPPLY T58 COM
T24 L T20 AI2 T10 BOUT6 T01 BATT - T59 A
+5 V T19 AI1 T09 BOUT5 T02 N/A USB
T23 +5 V T18 ACOM T08 BOUT4 T03 BATT + USB HOST
AOUT2 T07 BOUT3
T15 PWM T06 BOUT2

EMC TERMINAL ETHERNET
T14 OUT T05 BOUT1
T13 COM

4.4 Recommended wiring
4.4.1 General 43
4.4.2 Grounding 44
4.4.3 Power supply 44
4.4.4 Measurement wiring 46
4.4.5 Binary Inputs 56
4.4.6 Binary Outputs 57
4.4.7 E-Stop 58
4.4.8 Analog Inputs 58
4.4.9 CAN bus and RS485 wiring 61
4.4.10 USB 64
4.4.11 Ethernet 65
Current inputs 30-35 Current measurement wiring (page 46)
BESS voltage inputs 38-41 Voltage measurement wiring (page 49)
Bus voltage inputs 42-45 Voltage measurement wiring (page 49)
Binary inputs 46-53 Binary Inputs (page 56)
AOUT1 54, 55
CAN1 H, COM, L CAN bus and RS485 wiring (page 61)
CAN2 H, COM, L CAN bus and RS485 wiring (page 61)

+5 V 23 Analog Inputs (page 58)
Analog inputs 18-22 Analog Inputs (page 58)
AOUT2 15, 14, 13
Binary outputs 05-12 Binary Outputs (page 57)
E-Stop 04 E-Stop (page 58)
Power supply "+", D, "-" Power supply (page 44)
EMC Grounding
RS485 A, B, C CAN bus and RS485 wiring (page 61)
USB USB B USB (page 64)
USB Host USB A USB (page 64)
Ethernet RJ45 Ethernet (page 65)
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

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.3 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.4 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 285), Bus Nominal Voltage Ph-N (page 287), Mains/Bus Nominal Voltage Ph-Ph (page 287),
BESS Nominal Voltage Ph-N (page 286), Gen Nominal Voltage Ph-Ph (page 286) and BESS Nominal
Current (page 282) 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

IMPORTANT: It is necessary to ensure that potential difference between current COM terminal
and power supply "–" terminal is maximally ±2 V. To do so ground properly both terminals.
The number of CT's is automatically selected based on selected value of setpoint Connection type (page 285)
[3Ph4Wire / High Leg D / 3Ph3Wire / SplPhL1L2 / SplPhL1L3 / Mono Ph].
BESS currents and power measurement are suppressed if current level is bellow <1 % of CT range.
2
Use cables of 2.5 mm
Use transformers to 5 A
Connect CT according to following drawings:
3 phase application
Image 4.5 3 phase application

Image 4.6 3 phase application India
Note: This wiring is recommended for Indian market.
SplPhL1L2 application
Image 4.7 SplPhL1L2 application application
Image 4.8 SplPhL1L2 application application India

SplPhL1L3 application
Image 4.9 SplPhL1L3 application
Image 4.10 SplPhL1L3 application India
IMPORTANT: If the second phase of the split phase application is phase L2 use current input 32,
if its phase L3 use current input 33.
Mono phase application

Connect CT according to following drawings. Terminals phase 2 and phase 3 are opened.

Image 4.11 Mono phase application
Image 4.12 Mono phase application India
Earth fault current measurement
Image 4.13 Typical Earth fault current measurement
Voltage measurement wiring

The BESS and Bus protections are evaluated from different voltages based on Connection type (page 285)
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 285) = 3Ph4Wire
Image 4.14 Controller wiring for voltage measurement of 3 phase application with neutral
Note: Fuse on "N" wire is not obligatory but recommended.
Image 4.15 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 285) = High Leg D
Image 4.16 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 285) = 3Ph3Wire
Image 4.17 3 Controller wiring for voltage measurement of 3 phase application without neutral
Image 4.18 Typical BESS wiring of 3 phase application without neutral

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

Image 4.20 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 285) = MonoPhase
Image 4.21 Controller wiring for voltage measurement of MonoPhase application

Image 4.22 Typical BESS wiring of MonoPhase application
Principle of two transformers measuring for 3 phase connections
Image 4.23 Principle of two voltage transformers measuring
4.4.5 Binary Inputs

2
Use 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.
Note: The name and function or alarm type for each binary input have to be assigned during the
configuration.

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 .. BO8). Every single binary output can provide up to 0.5
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.24 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 122).
Image 4.25 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.

Analog inputs are typically used for: Oil Pressure, Coolant Temperature and Fuel Level. All of these parameters
are connected with relevant protections.
Image 4.26 Grounded sensors Image 4.27 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.

Analog Voltage sensor
Controller is equipped with +5 V terminal which can be used as power supply for a voltage analog sensor.
Voltage sensors
Image 4.28 Analog Voltag sensor
Note: Maximal current of 5V output is 100 mA.
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 2400 Ω are evaluated as
sensor failure (short or open circuit). This can be used for example to prevent running the BESS with failed
temperature sensor, so it wont be overheated.
Image 4.30 Analog inputs as binary

Image 4.29 Analog inputs as tristate
Note: The name, sensor characteristic and alarm types for each analog input have to be assigned during
configuration.
Note: Tristate and binary sensors are not suitable for Analog Switch functions.

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 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 CAN1 (page 19) bus (extension modules, ECU) and CAN2 (page 19)
(Communication peripherals (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.31 CAN bus topology
Image 4.32 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.33 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.34 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.35 Balancing resistors
Image 4.36 RS485 on board
4.4.10 USB
The USB can be used for direct computer connection. Use the shielded USB A-B cable. See the chapter
Connection via USB (page 236) for more information.
Image 4.37 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.11 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 237)
for more information.
Image 4.38 Ethernet Connection
4.5 External display

External Remote Displays or PC Panel Displays are used when needed. InteliNeo 530 BESS 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 530 BESS 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 530 BESS at one time.
Image 4.39 Connection of InteliVision display to InteliNeo 530 BESS

Image 4.40 Multiple connection to a single controller via switch
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.6 Maintenance
4.6.1 Backup battery replacement
The internal backup battery lifetime is approx. 6 years. If alarm Wrn RTC Battery Flat (page 811) 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 68
5.2 Controller configuration and PC tools connection 98
5.3 Default configuration 104
5.4 General Functions 105
5.5 Application related functions 191
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 21).
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 68
Page Structure 72
StartUp screen 74
Connecting to the controller 76
Login to the controller 77
Setpoints 80
Metering screens 87
Alarmlist 87
History 89
Trends 91
Administration 92
Basic operating modes description 97
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 :activating System Start/Stopno function

Stop : stoping of the BESS no function
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 530 BESS - the function in InteliNeo 530 BESS 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 530 BESS 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 Communication peripherals (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 - Controller Address (page 295) 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. . 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 530 BESS Controller screens
InteliNeo 530 BESS 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 530 BESS metering screens

Home Statistics
Power Ethernet 1
BESS Ethernet 2
Mains Ethernet 3
Bus CAN modules
Synchronization ECU modules
Power Management Modbus Master Devices
Analog inputs Virtual modules
Binary Outputs
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 530 BESS 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 150)
The InteliNeo 530 BESS has the following controller operation modes: OFF, MAN , and AUT, and TEST .
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.
The button BCB does not react, the BTB cannot be closed.
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 695). Unloading is active only when
binary input MCB FEEDBACK (PAGE 670) is closed or other BESS is connected to bus. In other case
BCB CLOSE/OPEN (PAGE 695) opens immediately.
AUTO mode
BESS is controlled based on external signals REMOTE START/STOP (PAGE 683) 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 291) to the Enabled position.
5.2 Controller configuration and PC tools

connection
5.2.1 USB 98
5.2.2 Ethernet 99
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 Port. In this case standard USB A to B cable should be used - USB
(page 64) 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 Ethernet (page 43)
Note: See Communication peripherals (page 19) to see differences between these peripherals.

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 304) has to be set to the same value as in the PC tool.
IP Address Mode (page 298) can be set to AUTOMATIC when there is DHCP service is available.
Otherwise it needs to be set to FIXED.
IP Address (page 299) is either set automatically or it can be adjusted to a specific requested value.
Subnet Mask (page 299) is either set automatically or it can be adjusted to a specific requested.
Gateway IP (page 300) 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 Controller Address (page 295).
IMPORTANT: Never fill Access code!
IMPORTANT: In case of using Ethernet (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
(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 Controller Address (page 295).
IMPORTANT: In case of using Ethernet (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 (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 509) - has to be ENABLED
AirGate Address (page 510) - manually adjusted address of AirGate server
AirGate Port (page 510) - manually adjusted port for communication between Controller and AirGate
server
AirGate Status (page 599) - has to be connected, operable
AirGate ID (page 599) - 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 Controller Address (page 295). 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 Controller Address (page 295). 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 648)
BIN2 CU-BIN-02 Free slot Not Used

5.3.2 Binary outputs
Number Name Description Configured function
Indication of required BESS Circuit BCB CLOSE/OPEN (PAGE
BOUT1 BCB Close/Open
Breaker state 695)
BOUT2 BCB ON Coil Control of close coil of BCB BCB ON COIL (PAGE 698)
BOUT3 BCB OFF Coil Opening of BCB BCB OFF COIL (PAGE 696)
BOUT4 BCB UV Coil Control of undervoltage coil of BCB BCB UV COIL (PAGE 699)
BOUT5 CU-BOUT-05 Free slot Not Used
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 N/A Free slot
AOUT2 CU-AOUT-02 N/A Free slot
5.4 General Functions

5.4.1 Alarm Management 106
5.4.2 Breaker Control 109
5.4.3 CAN Bus Log 114
5.4.4 Configuration Lock 115
5.4.5 Configuration Override 115
5.4.6 Control Groups 116
5.4.7 Crash Dump 116
5.4.8 Distributed Power Management Signals 117
5.4.9 E-STOP 122
5.4.10 Event History 124
5.4.11 Exercise Timers 127
5.4.12 Firewall 134
5.4.13 Forced Value 135

5.4.14 I/O Configuration 137
5.4.15 Load Shedding 142
5.4.16 Loss of Mains (Decoupling) Protections 144
5.4.17 Modbus Client (Master) 145
5.4.18 Multiple ECU 150
5.4.19 Operating Modes 150
5.4.20 PLC - Programmable Logic Controller 152
5.4.21 Power Formats And Units 163
5.4.22 Protections 164
5.4.23 Sensor Curves 175
5.4.24 Service Timers 177
5.4.25 System Start/Stop 178
5.4.26 User Buttons 179
5.4.27 User Management And Data Access Control 181
5.4.28 User Setpoints 187
5.4.29 Voltage Phase Sequence Detection 190
General functions which are not directly related to the Microgrid application are described in this chapter.
5.4.1 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 109) with Fixed Protection States (page
740).
Each alarm is written to the Alarmlist (page 109).
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 165).
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
804)
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 818)

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 109). 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 109) or new
event is written in Event History (page 124). The message will contain a copy of the Alarmlist (page 109) or
reasons from Event History (page 124). To enable this function, adjust setpoints Sd Message (page 523), Wrn
Message (page 523), or Event Message (page 522) to ON. Also enter a valid email address to the setpoints, E-
mail Address 1 (page 521), E-mail Address 2 (page 521), E-mail Address 3 (page 521), or E-mail Address
4 (page 522).
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 170). 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.2 Breaker Control

The following power switches are controlled by the controller:
The BESS Circuit Breaker or contactor – BCB
The Neutral Contactor Breaker - NCB (see the chapter Neutral Contactor Breaker (page 112))
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. ESCB UV coil
output is active when the controller is switched on. The output is deactivated for at least 2
UV coil
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
ESCB Breaker
ESCB is a breaker between Energy Storage and inverter (PCS). It can be realized as a manual disconnector
with fuse or classic breaker . You can choose the type of ESCB via setpoint ESCB Type (page 394). In case
that ESCB Type (page 394) is fuse, BESS only monitor ESCB FEEDBACK (PAGE 655) . In another case,
BESS fully control the ESCB in the same way, as a standard breaker.
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 835) is issued. The alarm is
issued also after 500 ms when there is mismatch of LBI BCB FEEDBACK (PAGE 648) and LBI BCB
FEEDBACK NEGATIVE (PAGE 649) . 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 Sd BCB Fail To Open (page 837)/ 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 396). If feedback doesn't match after second try and 2 seconds
delay elapsed, the alarm Sd BCB Fail To Close (page 836)/Sd ESCB Fail To Close (page 822) 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.
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 397) is used to choose if EACH or COMMON behavior of the NCB will be
used.
For the SPTM application the NCB works like there is one common NCB for whole SPTM 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
724) 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 724) 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 673) and LBO NCB CLOSE/OPEN (PAGE 724) 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.3 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
Communication peripherals (page 19) which should be physicality connected to the observed CAN. The
Communication peripherals (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.
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.4 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.64 Configuration lock
5.4.5 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 530 BESS 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 530 BESS
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
Restart the controller
Image 5.65 Location of the DIP switch for Configuration override

5.4.6 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 426). 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 427) and Group Link R (page 427).
Controller sends via CAN2 (page 19) (Communication peripherals (page 19)) bus 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 663) is activated the controller will send information to
all controllers on CAN that the groups defined by setpoints Group Link L (page 427) and Group Link R
(page 427) 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.
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.7 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 98) or Ethernet (page 99).
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.66 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.8 Distributed Power Management Signals

Note: This chapter is relevant for all ComAp controllers working in Multiple Island-Parallel operation.
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
116). If you merge Control Groups together (GROUP LINK (PAGE 663)), 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 controller
Distributed signal Description for Mains controller
(MINT application)
LBI REMOTE START/STOP Accepted only in controllers
(PAGE 683) 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 CAN2 (page configured.
19) or Communication If the Distributed signal is
peripherals (page 19) to the
configured to any binary input
controllers in the same group.
(physical or virtual), the signal is
automatically shared to other
controllers via CAN2 (page 19) or
Min Run Power 1,
Communication peripherals
2, 3
(page 19) as CAN Distributed
signal.
N/A
If distributed signal is shared on
CAN2 (page 19) or
Load Reserve 1, 2,
Communication peripherals
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

Distributed
Scheme for Mains + Gen-set/Microgrid controllers
signal
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 CAN2 (page 19)
(Communication peripherals (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 CAN2 (page 19) (Communication peripherals (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 CAN2 (page 19) (Communication peripherals (page
19)) bus as System Start/Stop.
Image 5.67 Distributed signals case 1

2. LBI state received from CAN2 (page 19) (Communication peripherals (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 CAN2 (page 19) (Communication peripherals (page 19)) bus. Controller
follows state of the shared LBI signal then.
Image 5.68 Distributed signals case 1&2
3. LBI state received from CAN2 (page 19) (Communication peripherals (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 CAN2 (page 19) (Communication peripherals (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 CAN2 (page 19)
(Communication peripherals (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.9 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 (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 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.71 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
has voltage - state is OK, BO1 and BO2 can be activated
0
has no voltage - E-STOP (page 820) is active, BO1 and BO2 cannot be activated
For wiring information see E-Stop on page 58.

5.4.10 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.72 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
Controller I/O PSV Battery Voltage (page 566) -
Pwr BESS P (page 541) kW
Q BESS Q (page 542) kW
PF BESS Power Factor (page 544) -
LChr BESS Load Character (page 544) -
Bfrg BESS Frequency (page 547) Hz
Vbess1 BESS Voltage L1-N (page 547) V
Vbess2 BESS Voltage L2-N (page 547) V
BESS Vbess3 BESS Voltage L3-N (page 547) V
Vbess12 BESS Voltage L1-L2 (page 547) V
IL1 BESS Current L1 (page 549) A
IEFC Earth Fault Current - BIO8 (page 551) A
VesM ES Voltage Meas (page 538) V
Ves ES Voltage (page 538) V
Ies ES Current (page 539) V
A
Energy Storage
MxChPWR ES Max Charging Power (page 539) V
kW
ES Max Discharging Power (page
MxDiPWR V
kW
539)
VpcsM PCS Voltage Meas (page 540) -
Power Conversion
IpcsM PCS Current Meas (page 540) -
System
PpcsM PCS Power Meas (page 540) -

Category Column Name Value Unit
BusFrq Bus Frequency (page 552) Hz
VBus1 Bus Voltage L1-N (page 552) V
VBus2 Bus Voltage L2-N (page 552) V
Bus VBus3 Bus Voltage L3-N (page 552) V
VBus12 Bus Voltage L1-L2 (page 552) V
Ain1 Not Used -
Ain2 Not Used -
Ain3 Not Used -
Controller I/O
Ain4 Not Used -
BIN Binary Inputs (page 568) -
BOUT Binary Outputs (page 569) -
Frequency Regulator Output (page
Frequency/Load Control SRO V
562)
Voltage/PF Control VRO Voltage Regulator Output (page 564) V
Statistics RunH Running Hours (page 573) h
Mode Controller Mode (page 576) -
BEST BESS state (page 577)
BRST Breaker state (page 577)
PCSINF BESS Info (page 579)
Info
PCSINF PCS Info (page 579)
BMSINF BMS Info (page 580)
AUXINF AUX Info (page 580)
FVST Forced Value Status (page 580)
Running Nominal Power Of All (page
TRPN kW
560)
Power Management
Running Nominal Power In PM (page
APN kW
560)
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.

5.4.11 Exercise Timers
Mode Once 128
Mode Daily 129
Mode Weekly 130
Monthly mode 131
Mode Short period 133
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 460) Timer 1 Setup (page 461)
Related LBOs:
Exercise Timer 1 (page 715)

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 461).
Note: Setpoint Timer 1 Setup (page 461) is visible only if setpoint Timer 1 Function (page 460) has any
other value than disabled.
Image 5.73 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 460) setpoint.
Then go to Timer 1 Setup (page 461) 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 461)
Image 5.74 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 461) 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 461).
Image 5.75 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 461) 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 461).
There are two types of monthly repetition. First of them is based on repeating one day in month.
Image 5.76 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.77 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 461) 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 461).
Image 5.78 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.12 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 (page 19) port. The firewall
can be enabled by the setpoint IP Firewall in theGroup: Ethernet (page 298). 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.13 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 24 LBIs - FORCED VALUE INPUT 01 (PAGE 657) ... FORCED VALUE
INPUT 24 (PAGE 662). You can see current states of all LBIs in value Forced Value Status (page 580). 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.
Integrated color display / InteliVision 5.2
Image 5.79 : Force Value and Protected Setpoint Indication
InteliConfig
Image 5.80 : 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 531)), 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.81 : Force Value and Protected Setpoint Indication in IV 5.2
InteliConfig
Image 5.82 : 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.14 I/O Configuration

Binary Inputs 138
Binary Outputs 138
Analog Inputs 139
Analog Outputs 140
Functions Configuration 141
Protections Configuration 141
Transfer I/O Configuration 141
Remove I/O Configuration 142
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.83 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 141
Remove IO Configuration - see Remove I/O Configuration on page 142
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 141
4. Protections - the set of protections see Protections Configuration on page 141
Image 5.84 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 141
Image 5.85 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 175
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 141
12. Protections - the collection of protections see Protections Configuration on page 141

Image 5.86 Analog input configuration using linear sensor
Image 5.87 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.88 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 547) (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 164
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.89 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.15 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 576).
Load shedding outputs
Stage LBO
Stage 1 LOAD SHEDDING STAGE 1 (PAGE 721)
Stage 2 LOAD SHEDDING STAGE 2 (PAGE 721)-
How the load shedding controls the load shedding outputs

The Load Shedding function can be used if Controller Mode (page 290) != OFF.
Activation of the function is adjusted via setpoint Load Shedding Active (page 435). Function could be active
when:
Entering Breaker state (page 577) = IslOper/MultIslOp - all stages are disconnected.
Change from Breaker state (page 577) = ParalOper/MultParOp
to Breaker state (page 577) = IslOper/MultIslOp - all stages are disconnected.
During Breaker state (page 577) = 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 436) and the
minimal delay between two disconnections is adjusted via setpoint Load Shedding Delay (page 436). When
relative BESS P (page 541) exceeds Load Shedding Level (page 436) and delay Load Shedding Delay
(page 436) elapsed from last disconnection of stage, another stage is disconnected.

Image 5.90 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
438), Load Reconnection Level (page 437) and Load Reconnection Delay (page 437).
Manual reconnection
Conditions:
Setpoint Auto Load Reconnection (page 438) = Manual
LBI MANUAL LOAD RECONNECTION (PAGE 669) has to be configured
When relative BESS P (page 541) drops below Load Reconnection Level (page 437) rising edge of LBI
MANUAL LOAD RECONNECTION (PAGE 669) reconnects the highest disconnected stage.
Note: Setpoint Load Reconnection Delay (page 437) is not considered
Image 5.91 Manual Load reconnection

Auto reconnection
Conditions:
Setpoint Auto Load Reconnection (page 438) = Auto
When relative BESS P (page 541) drops below Load Reconnection Level (page 437) and delay Load
Reconnection Delay (page 437) elapsed from last reconnecting of stage, another stage is reconnected.
Image 5.92 Auto Load reconnection
5.4.16 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 Bus
Voltage L1-N (page 552).
Protection is enabled via setpoint Vector Shift Protection (page 368) and works in AUTO and MAN mode. Limit
of protection is adjusted via setpoint Vector Shift Limit (page 428). When protection is activated, the BCB
breaker is opened. Maximal value of vector shift is represented by value Max Vector Shift (page 554).
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).
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. This protection works in AUTO and
MAN mode and always opens BCB.
Common behavior
Protections are enabled/disabled by setpoints ROCOF1 Protection (page 369), ROCOF2 Protection (page
370), ROCOF3 Protection (page 371) and ROCOF4 Protection (page 372).
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 369)
Protection is evaluated from last ROCOF1 Windows Length (page 428) samples. If ROCOF1 (page
555) is over ROCOF1 df/dt (page 429), breaker is opened. Maximal measured ROCOF, from start of
evaluation, is stored in Max ROCOF1 (page 555).
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 429) period. If
ROCOF2 (page 555) is over ROCOF2 df/dt (page 430), breaker is opened. Maximal measured ROCOF,
from start of evaluation, is stored in Max ROCOF2 (page 556).
5.4.17 Modbus Client (Master)

The Controller InteliNeo 530 BESS 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 9 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. All modbus server devices share the common pool of inputs and
outputs which is limited on 256 Binary Inputs, 256 Binary Outputs, 288 Analog Inputs and 64 Analog Outputs
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 definitions 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 recommended 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 it is possible to define the Refresh Type parameter which offers these options:
Periodically - The writing operations is performed every period based on the settings of Refresh Rate
parameter regardless the real change of the output which is to be written.
On Change - The write operation is only performed on 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.18 Multiple ECU

InteliNeo 530 BESS allows you to configure, monitor and control multiple Electronic Control Units (ECUs), such
as Breakers and Modbus modules. At this moment there are 9 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. 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 706) ECU 1 Comm Fail (page 878)
For each ECU there is LBO which gets activated when communication issue with respective ECU is detected.
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.19 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 290) 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 682)
Remote MAN (page 682)
Remote AUTO (page 681)
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 97.
Switching Control Mode

Controller recognize two possible ways to change mode:
Setpoint
Controller mode is selected by Setpoint Controller Mode (page 290). 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
290).
Signalization of Control Mode

Controller offers two kinds of signalization:
Value
Current controller mode is always show in Value Controller Mode (page 576).
LBO
There is a dedicated LBO for each mode.
MODE OFF (PAGE 723)
MODE MAN (PAGE 723)
MODE AUTO (PAGE 723)
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.
No Power management function will be performed. The buttons 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.
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 213) in MINT application.
No Power management function will be performed.
Dead Bus Start behaves as if Setpoint Dead Bus Start = Disabled
AUTO
BESS is controlled based on external signal (REMOTE START/STOP (PAGE 683) ) or by conditions (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, and BCB ON/OFF.
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 291) to the Enabled position.
IMPORTANT: BESS will start if at least one external signal or condition is fulfilled.
5.4.20 PLC - Programmable Logic Controller

List of available PLC blocks 153
PLC Editor 153
PLC logic execution rules 159
PLC monitor 160
Other functions 162
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.93 PLC Editor - main page
List of available PLC blocks

In the table below you can find all available PLC blocks.
For more information about PLC blocks go to the chapter PLC (page 749)
6 back to PLC - Programmable Logic Controller
PLC Editor
Toolbar 153
Working with sheets 154
Blocks Selection Tree 154
Adding PLC blocks 155
PLC Block Configuration 156
Define inputs and outputs 157
Creating wires 158
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.94 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.95 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.96 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 749) 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.97 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.98 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.99 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.100 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.
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.101 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.102 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.103 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.104 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.105 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.106 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.21 Power Formats And Units

InteliNeo 530 BESS 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.22 Protections
Protection types 165
Protection activation 167
Protection blocking 167
Fixed protections 167
User protections 170
Protection states 175
InteliNeo 530 BESS combines Fixed protections (page 167) with User protections (page 170) 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 170) is limited to 200. The maximum number of configured fast User
protections (page 170) is limited to 50.

Protection types
Level 1 Protections
LBO COMMON ALARM LEVEL 1 (PAGE 703)
LBO COMMON ALARM ACTIVE LEVEL 1 (PAGE 703)
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 705)
704) (PAGE 704)

Level 2 Protections
LBO COMMON ALARM LEVEL 2 (PAGE 703); except Mains Protection
LBO COMMON ALARM ACTIVE LEVEL 2 (PAGE 703) ; except Mains Protection
Name Shutdown Shutdown Override Slow Stop

Abbreviation Sd Sd Stp
Alarm List indication
History record
Fault Reset needed
Action: CB open
Action: BESS stop
SD Override blocking
LBO Alarm activation
LBO Horn activation

COMMON SHUTDOWNMAINS
COMMON SHUTDOWN COMMON SLOW
Common LBO PROTECTIONBREAKER OPEN (PAGE
OVERRIDE (PAGE 704) STOP (PAGE 705)
704)
* It causes immediate opening of the BCB. In AUTO mode the BESS remains running for 60 seconds and then it's
stopped by the standard stop sequence. In MAN mode the BESS remains running until the operator changes it's
operational state manually.If the controller is in AUTO mode and all previously active Off load alarms
disappeared the BESS is automatically started back and connected to the load if the condition for the BESS to be
running persists.
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 170). 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 167).
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 326) 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 679)
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 825)
Sd Bus >>V L2-N (page 825)
BESS >>V Protection Sd BESS >>V L3-N (page 826) FIXED PROTECTIONS STATES 2
(page 356) WRN BESS >>V L1-L2 (page 826) (PAGE 742)
WRN BESS >>V L2-L3 (page 826)
WRN BESS >>V L3-L1 (page 826)
Sd BESS >V L1-N (page 827)
Sd BESS >V L2-N (page 827)
FIXED PROTECTIONS STATES 2
BESS >V Protection Sd BESS >V L3-N (page 827)
(PAGE 742)
(page 355) Sd BESS >V L1-L2 (page 827)
Sd BESS >V L2-L3 (page 828)
Sd BESS >V L3-L1 (page 828)
Sd BESS <V L1-N (page 828)
Sd BESS <V L2-N (page 828)
BESS <<V Protection Sd BESS <V L3-N (page 829)
(PAGE 742)
(page 357) Sd BESS <V L1-L2 (page 829)
Sd BESS <V L2-L3 (page 829)
Sd BESS <V L3-L1 (page 829)
Sd BESS V Unbalance Ph-N (page
Voltage Unbalance 830)
(PAGE 742)
Protection (page 357) Sd BESS V Unbalance Ph-Ph (page
831)
BESS Frequency Protections

BESS >f Protection (page
Sd BESS >f (page 830) (PAGE 742)
363)

BESS <f Protection (page
Sd BESS <f (page 830) (PAGE 742)
364)

BESS Load & Current Protections
Short Circuit Protection FIXED PROTECTIONS STATES 4
PVBO Short Circuit (page 833)
(page 350) (PAGE 744)
BESS IDMT >A FIXED PROTECTIONS STATES 4
Sd IDMT BESS >A (page 832)
Protection (page 350) (PAGE 744)
BESS Current Unbalance Sd BESS Current Unbalance (page FIXED PROTECTIONS STATES 2
Protection (page 352) 831) (PAGE 742)
BESS IDMT Overload FIXED PROTECTIONS STATES 4
Sd IDMT Overload (page 832)
Protection (page 349) (PAGE 744)
BESS Other Protections

Earth Fault Current Sd IDMT Earth Fault Current (page FIXED PROTECTIONS STATES 4
Protection (page 528) 831) (PAGE 744)
Phase Rotation (page
289)
Note: This protection
monitors phases rotation
and compares it with
Phase Rotation (page ALI BESS Ph Rotation Opposite (page
-
289), in case of 816)
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 815)
inconsistency of all ALI BESS Ph L2 Inverted (page 816) -
phases, proper alarm is
ALI BESS Ph L3 Inverted (page 816)
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
337) and BESS V Unbalance Delay
(page 337) When relative difference
between bus voltages is over setpoint
BESS V Unbalance (page 337) for time Bus V Unbalance Ph-N
longer than BESS V Unbalance Delay (page 858) FIXED PROTECTIONS STATES
(page 337) history record "Bus V
Bus V Unbalance Ph-Ph 3 (PAGE 743)
Unbalance Ph-N" or/and "Bus V
(page 859)
Unbalance Ph-Ph" is written to the
history.
IMPORTANT: Behavior of this protection
is influenced by setpoint Connection
type (page 285).
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 365) 4 (PAGE 744)
835)
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 170
Selecting the protection type see Protection types on page 165
Text input for Alarm / History message
Selecting the protection activation see Protection activation on page 167
Selecting the block type see Protection blocking on page 167
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 170
Selecting the protection type see Protection types on page 165
Text input for Alarm / History message
Selecting the protection activation see Protection activation on page 167
Selecting the block type see Protection blocking on page 167

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 530 BESS, which helps with better management of
alarms. Until now, you could only use LBO ALARM (PAGE 693) 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 167) 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 741)
User protections states

During the Configuration of protections in InteliConfig (page 170), 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 746), 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.23 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 530 BESS 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.24 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
471) 473) 474) 476)
Setpoints 1 Interval (page 2 Interval (page 3 Interval (page 4 Interval (page
472) 473) 475) 476)
1 Protection (page 2 Protection (page 3 Protection (page 4 Protection (page
472) 474) 475) 477)
1 RunHours (page 2 RunHours (page 3 RunHours (page 4 RunHours (page
573) 574) 574) 575)
Values
1 Interval (page 2 Interval (page 3 Interval (page 4 Interval (page
574) 574) 575) 575)
Maintenance 1 Maintenance 2 Maintenance 3 Maintenance 4
RunHours (page RunHours (page RunHours (page RunHours (page
860) 860) 861) 861)
Alarms
Maintenance 4
Maintenance 1 Maintenance 2 Maintenance 3
RunHours (page
Interval (page 859) Interval (page 860) Interval (page 860)
861)
AL Maintenance 1 AL Maintenance 2 AL Maintenance 3 AL Maintenance 4
LBOs
(page 692) (page 692) (page 693) (page 693)
Running hours counters

The value Running Hours (page 573) is used as a basic running hours counter and it is incrementing whenever
the BESS is turned on.
5.4.25 System Start/Stop

There is a LBI REMOTE START/STOP (PAGE 683) 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 683) 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 683) will be started
only if their LBI is activated.

5.4.26 User Buttons
User Buttons can be used to assign function of user's choice to button on the External display (page 65) 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 65).
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 65). 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 247).
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.27 User Management And Data Access Control
Types of interfaces 181
User accounts 182
Managing accounts 184
Account break protection 186
Access to controller data 187
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 Communication peripherals (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 (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 Communication peripherals (page 19) terminal.
This interface is used for Modbus Client (Master) (page 145) 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 Communication peripherals (page 19) = Trusted, Ethernet (page 19) = Trusted,
Communication peripherals (page 19) = Trusted, then it is possible to connect 6 ComAp clients and 3
Modbus clients on all three ports in sum.
Example: If Communication peripherals (page 19) = Trusted, Ethernet (page 19) = Untrusted,
Communication peripherals (page 19) = Modbus client, then 6 ComAp clients and 3 Modbus clients can
be connected to Communication peripherals (page 19), 8 ComAp clients and 3 Modbus clients can be
connected to Ethernet (page 19) and 3 Modbus clients can be connected to Communication
peripherals (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
Communication peripherals (page 19)).
PIN 4-digit “password” to be used together with UID.
Access level Determines Access to controller data (page 187)
Role mask Determines Access to controller data (page 187)
User login
To login to the controller the username and password must be provided into the login form of the
application (InteliConfig (page 21), WebSupervisor (page 21), External display (page 65) 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 186)

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 807) 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 182).
Note: Rules for the User accounts (page 182) 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 806) 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.Communication
peripherals (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.28 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.107 User setpoints tab in InteliConfig
Image 5.108 Setting parameters of Group/Subgroup

Image 5.109 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
Grid Codes User setpoints
Power Management User setpoints
User setpoints User setpoints
Loss of Mains Protections User Setpoints
Scheduler User Setpoints
Maintenance Timers User Setpoints
5.4.29 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 289).
6 back to General Functions

5.5 Application related functions
5.5.1 BESS Charging/Discharging Control 191
5.5.2 BESS Forced power 192
5.5.3 BESS Operation States 193
5.5.4 BESS Operation Area 194
5.5.5 BESS Precharge Types 194
5.5.6 InteliNeo 530 as Generic BESS Controller 198
5.5.7 BESS Stabilization 199
5.5.8 Connecting To Load 200
5.5.9 Deenergized DC Bus after BCB is Opened in PQ Mode 205
5.5.10 Multiple Island Operation 206
5.5.11 Output Control – Frequency/Load 206
5.5.12 Output Control - Voltage/PF 208
5.5.13 Parallel To MainsOperation - MINT Application 210
5.5.14 Power Management 213
5.5.15 Regulation Loops 233
5.5.16 Sunrise/Sunset 235
Functions directly related to the Microgrid application are described in this chapter.
5.5.1 BESS Charging/Discharging Control

This function allows managing of the charging and discharging process. The BESS power request can be
given by Load Sharing, Local Baseload or by any external device (for example InteliNeo 6000 or InteliNeo
5500). The setpoint HLC Control Mode (page 318) is used to select whether power request is controlled by
the standard ComAp way (Load Shar/Local Baseload) or by direct request from the High Level Controller (via
LAIs).
In case of Local Baseload the Energy Storage can be charged by negative request and discharged by
positive request from LAI or setpoint. There are two LBIs which can be used to Enable/Disable charging and
discharging process: LBI ES CHARGE ENABLE (PAGE 653) and LBI ES DISCHARGE ENABLE (PAGE 653). If both
LBIs are activated, the battery can be fully cycled (charged and discharged). If any LBI is deactivated the
respective process is blocked.
In case of Load Sharing the Energy Storage can be only discharged because Load Sharing does not support
negative power request.
Note: The positive values are used for discharging and negative values for charging.
Variable Max Power Output

The active charging and discharging power is primarily given by the setpoint BESSNominal power (page
280), but any external device such as BMS can limit maximal charging/discharging power by LAIs ES MAX
CHARGING CURRENT (PAGE 736) and ES MAX DISCHARGING CURRENT (PAGE 736). These LAIs are used to
calculate maximal ES Max Charging Power (page 539) and ES Max Discharging Power (page 539). If
calculated value is lower than nominal value the charging or discharging power will be limited.

State of Charge
The charging and discharging process of the BESS also depends on the State Of Charge (SOC). When the
value ES SOC (page 538) reach limit given by the setpoint SOC Low Target (page 322) the discharging
process is stopped and the LBO ES SOC DISCHARGE DISABLED (PAGE 709) is activated. When the value ES
SOC (page 538) reach limit given by the setpoint SOC High Target (page 321) the charging process is
stopped and the LBO ES SOC CHARGE DISABLED (PAGE 709)is activated. The charging/discharing process
can be activated again after the value ES SOC (page 538) leave the hysteresis which are defined by the
setpoints SOC Low Hysteresis (page 322) and SOC High Hysteresis (page 321). 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 ES CHARGE ENABLE (PAGE 653) and
ES DISCHARGE ENABLE (PAGE 653).
Note: All relative setpoints/values are related to the LAI/Value ES KWH CAPACITY (PAGE 736)ES Nominal
Capacity (page 538).
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 373). 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.110 State of charge
5.5.2 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.

5.5.3 BESS Operation States
Electric state machine
Init Initialization of the controller. The application is not active yet.

MCB is opened and BCB is opened (LBO BCB CLOSE/OPEN (PAGE 695) is not active
BrksOff
and LBI BCB FEEDBACK (PAGE 648) is not active either).
IslOper Island operation: MCB is opened and LBO BCB is closed.
BrksOff BCB and even the MCB (MCB Feedback in MINT application) are opened.
MainsOper BCB is opend and MCB is closed.
Synchro The Controller is in synchronisation process.
MultParOp Multiple Parallel Operation, the BCB and MCB is closed.
MultIslOp Multiple Island Operation, the BCB is closed, MCB is opened.
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.
Controller is waiting for information that ES is ready to start on LBI ES READY TO
ES Starting
START (PAGE 654). Controller Set the LBO ES RUN REQUEST (PAGE 709).
Only If Setpoint: Precharge Type (page 318) = DC Internal. Controller set the LBO
ESCB PRECHARGE RELAY (PAGE 726). The Precharge sequence has started and controller
Precharging evaluates the voltage match on values ES ES Voltage Meas (page 538) and PCS
Voltage Meas (page 540).
AC Only If Setpoint: Precharge Type (page 318) = AC External.
Precharging The Controller is waiting for external precharge is finished.
Controller set the LBO PCS RUN REQUEST (PAGE 726) and is waiting for infirmation via
Starting
LBI PCS Ready To Load.
The BESS AC output is energized and it is possible to close the BCB to the dead bus or
Energized
start the synhronisation process. This State is related to DC Precharge only.
Synchronisation to the alive bus is in process. This State is related to DC Precharge
Synchro
only.
BESS Connected to the alive bus starts the Soft Loading process according the
Soft Loading
settings of Load Ramp (page 382).
Loaded When the loading process is finished, the BESS steps to this state.
BESS power is ramping down according the length of the Soft Unload Ramp (page
Soft Unload
383).
BESS evaluates all stopped source conditions at this time and then goes to Ready
Stop
state or it issues the Stop Fail.

5.5.4 BESS Operation Area
The BESS Operation area is defined by Application Curves CAPABILITY L (PAGE 639) and CAPABILITY C (PAGE
640) and is important when BESS operates in mains parallel operation.. The Default configuration defines these
two curves to create the circle with radius equal to Samax (page 280). The vector of apparen power can only
operate inside this circle. If the apparent power required as the result of Required P and Q is to be cross this
circle, the Active power has always higher priority and reactive power is limited to keep the apparen power inside
the circle.
5.5.5 BESS Precharge Types

This function allows adjustment of the BESS pre-charging type. There is the Setpoint Precharge Type
(page 318) which enables the selection of AC external or DC external/internal precharge of an inverter. The
precharge process also affects the setpoint ESCB Type (page 394).This is a very influential factor in
determining the ability of an inverter to generate alternating voltage at its output.
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:
LBI ES CHARGE ENABLE (PAGE 653)

LBI ES DISCHARGE ENABLE (PAGE 653)
LAI ES VOLTAGE MEAS (PAGE 737)
LAI PCS CURRENT MEAS (PAGE 738)
LAI ES MAX CHARGING CURRENT (PAGE 736)
LAI ES MAX DISCHARGING CURRENT (PAGE 736)
LAI ES SOC (PAGE 736)
DC Precharge
There are 3 different schematic drawing that affects how to start sequence behaves:

Image 5.111 Precharge Types
a, Controlled ESCB Breaker and Controlled DC Precharge

b, Monitored ESCB disconnector/fuse and BMS is in charge of DC Precharging
c, Controlled ESCB Breaker and BMS is in charge of DC Precharging
Controlled ESCB and Controlled DC Precharge

Setpoint ESCB Type (page 394) = Breaker and Precharge Type (page 318) = DC Internal
Starting Sequence:
When start command is received, Start is sent to the battery via LBO ES RUN REQUEST (PAGE 709)= 1,
initiating the pre-charging process with the countdown of the Precharging TO (page 323) and waiting to
voltage in Value PCS Voltage Meas (page 540).
If the voltage is present Value PCS Voltage Meas (page 540) a compared to Value ES Voltage Meas
(page 538) in match (Setpoint DC Voltage Window (page 394)), ESCB is closed. The controller is
waiting for LBI PCS READY TO START (PAGE 676) = 1. At the moment when the LBI PCS READY TO START
(PAGE 676) = 1, Start is sent to the PCS via LBO PCS RUN REQUEST (PAGE 726) and timer Setpoint PCS
Ready To Load TO (page 324) is started to count down.
If LBI PCS READY TO LOAD (PAGE 676) = 1, Value Bus Voltage (page 553) and Value Bus Frequency
(page 552) are within limits after Minimal Stabilization Time (page 325) elapses, then BCB can be
closed and regulation loops are activated.
Error states:
When that LBI ES READY TO START (PAGE 654) drops to 0, AlarmWrn Energy Storage Not Ready
(page 808) is activated.
In case that LBI ES READY TO LOAD (PAGE 654) drops to 0 after it already has been in 1, Alarm Wrn
Unexpected PCS State is activated

If LBI PCS READY TO LOAD (PAGE 676) drops to 0 after it already has been in 1 and LBO PCS RUN
REQUEST (PAGE 726) = 1, Alarm Wrn Unexpected Source State is activated
If LBI ES READY TO LOAD (PAGE 654) is not received before timer ES Ready To Load TO (page 324)
elapses, AlarmSd Start Fail (page 834) is activated.
If ValuePCS Voltage Meas (page 540), does not receive voltage after precharge, Alarm Wrn DC
Measurement Error (page 807) is activated.
If Value PCS Voltage Meas (page 540) (obtained via LAI PCS VOLTAGE MEAS (PAGE 738)) compared to
Value ES Voltage Meas (page 538) does not get within Setpoint DC Voltage Window (page 394)
(voltage matching condition) before Precharging TO (page 323) elapses, then Alarm Sd Start Fail
If LBI PCS READY TO START (PAGE 676) and LBI PCS READY TO LOAD (PAGE 676) is not received before
timer Setpoint PCS Ready To Start TO (page 324) elapses, Alarm Sd Start Fail (page 834) is activated.
If Bus Voltage (page 553) and Value Bus Frequency (page 552) are not within limits before timer
Setpoint Maximal Stabilization Time (page 325) elapses, then proper alarm (AC Bus Voltage and/or AC
Bus Frequency) are activated.
Monitored ESCB disconnector/ fuse and BMS is in charge of DC Precharging

Setpoint ESCB Type (page 394) = Fuse/Disc. and Precharge Type (page 318) = DC External
Starting Sequence:
When Start command is received, Start is sent to the Battery via LBOES RUN REQUEST (PAGE 709) = 1,
timer ES Ready To Load TO (page 324) starts counting down and waits for LBI ES READY TO LOAD
(PAGE 654). If ValuePCS Voltage Meas (page 540) recieves voltage, timer setpoint PCS Ready To
Load TO (page 324) is started to count down and controller is waiting for LBI PCS READY TO START
(PAGE 676) = 1.
When LBI PCS READY TO START (PAGE 676)= 1, Start is sent to the PCS (LBO PCS RUN REQUEST (PAGE
726) = 1) and waiting for LBI PCS READY TO LOAD (PAGE 676) = 1. Regulation loops are activated (based
on setpoints setting).
After timer Setpoint Minimal Stabilization Time (page 325) elapses and Value Bus Voltage (page 553)
and Value Bus Frequency (page 552) are within limits, then BCB can be closed.
Error states:
In case that LBI ES READY TO START (PAGE 654) drops to 0, Alarm Wrn Wrn Energy Storage Not
Ready (page 808) is activated.
Unexpected Source State is activated
If LBI PCS READY TO LOAD (PAGE 676) drops to 0 after it already has been in 1 and LBO PCS RUN
REQUEST (PAGE 726) = 1, Alarm Wrn Unexpected Source State is activated
If Value PCS Voltage Meas (page 540) (obtained via LAI PCS VOLTAGE MEAS (PAGE 738)) compared to
Value ES Voltage Meas (page 538) does not get within Setpoint DC Voltage Window (page 394)
(voltage matching condition) before Precharging TO (page 323) elapses, then Alarm Sd Start Fail

Controlled ESCB and BMS is in charge of DC Precharging
Setpoint ESCB Type (page 394) = breaker and Precharge Type (page 318)= DC External
Starting Sequence:
When Start command is received ESCB is requested to be closed (LBO ESCB CLOSE/OPEN (PAGE 711) =
1). After receiving feedback from the breaker (LBI ESCB Feedback = 1) is Start sent to the Battery (LBO
ES RUN REQUEST (PAGE 709) = 1). Controller expects LBI ES READY TO LOAD (PAGE 654) before ES
Ready To Load TO (page 324) elapses.
After controller recievesPCS Voltage Meas (page 540), the ES Ready To Load TO (page 324) is stared
to counting down and waits until PCS READY TO START (PAGE 676) = 1
When LBI PCS READY TO START (PAGE 676) = 1, start is sent to the PCS LBO PCS RUN REQUEST (PAGE
726) and controller is waiting to LBI PCS READY TO LOAD (PAGE 676).Than regulation loops are activated
(based on setpoints setting).
After timer Setpoint Minimal Stabilization Time (page 325) elapses and Value Bus Voltage (page 553)
and Value Bus Frequency (page 552) are within limits, then BCB can be closed.
Error states:
In case that LBI ES READY TO START (PAGE 654) drops to 0, Alarm Wrn Wrn Energy Storage Not
Ready (page 808) is activated.
Unexpected Source State is activated
In case that LBI PCS READY TO LOAD (PAGE 676) drops to 0 after it already has been in 1 and LBO PCS
RUN REQUEST (PAGE 726) = 1, Alarm Wrn Unexpected PCS State is activated
If LBI ES READY TO LOAD (PAGE 654) is not received before timerES Ready To Load TO (page 324)
elapses Alarm Sd Start Fail (page 834) is activated
If Bus Voltage (page 553) and Value Bus Frequency (page 552) are not within limits before timer
Setpoint Maximal Stabilization Time (page 325) elapses, then proper alarm (AC Bus Voltage and/or AC
Bus Frequency) are activated.
AC Precharge
Setpoint ESCB Type (page 394) = Fuse/Disc. and Precharge Type (page 318)= AC External
Starting Sequence:
When Start command is received Start is sent to the Battery (LBOES RUN REQUEST (PAGE 709) = 1),
BESS State= AC Precharging, timer Setpoint ES Ready To Load TO (page 324) is started to count
down, Value Timer text = ES Ready To Load TO. If LBI ES READY TO LOAD (PAGE 654) is not received
before timer ES Ready To Load TO (page 324) elapses, Alarm Sd Start Fail (page 834) is activated.
When LBI ES READY TO LOAD (PAGE 654) = 1, the precharge sequence is considered as finished and
Controller set the LBO PCS RUN REQUEST (PAGE 726) once the LBI PCS Ready To Start gets active. At
this time the controller expect the confirmation as LBI PCS READY TO LOAD (PAGE 676).

Once the LBI PCS READY TO LOAD (PAGE 676) is recieved, the soft loading process can start and
Controller steps in to the Loaded State. If LBI PCS READY TO LOAD (PAGE 676) is not received before
timer Setpoint PCS Ready To Load TO elapses Alarm Sd Start Fail (page 834) is activated.
5.5.6 InteliNeo 530 as Generic BESS Controller

BESS can be installed as a unit operating within the ComAp ecosystem consisting of Gen-set, Mains or BTB
controllers (InteliGen, InteliMains). In this scenario it is connected directly to intercontroller CAN
communication line and it behaves like a standard unit.
Another option of integration of the BESS is to integrate it as a subordinated unit of some generic Higher
Level Controller (HLC), e.g. InteliNeo 6000, InteliNeo5500 or any generic 3rd party unit. InteliNeo 530 can be
integrated using the simple interface.
There is a setpoint Subgroup: BESS Control (page 317) for this purpose and it offers these options:
Disabled : HLC is not used and BESS is connected to Comap microgrid directly via CAN. BESS does
Load sharing or Local Baseload (description in Load control (page 211)
U-f Const: HLC is not used and the BESS is doing standard Load and Var Sharing while voltage and
frequency are regulated to their nominal values. It is expected that BESS 530 is alone (there is no CAN
communication with other ComAp units). There is no need and no way, how to control the voltage and
frequency externally in this mode.
U-f: The controller accept request from the HLC via LAIs HLC U-F CONTROL: Q REQUEST (PAGE 737) and
HLC U-F CONTROL: P REQUEST (PAGE 737). The physical meaning of this value is relative value in %
related to the BESS Nominal Power. The PID loop has to be integrated in the HLC. The BESS 530 only
follows the request of the HLC.
P-Q: The controller is forced to do Local Baseload and Local PF/Q. P, PF, and Q request are obtained via
LAIs LOAD CONTROL ANEXT: LOCAL BASELOAD (PAGE 738), Q CONTROL: ANEXT BASE Q (PAGE 739),
and PF CONTROL: ANEXT BASE PF (PAGE 739). If are configured Q CONTROL: ANEXT BASE Q (PAGE
739) and PF CONTROL: ANEXT BASE PF (PAGE 739) at the same time, Q CONTROL: ANEXT BASE Q
(PAGE 739) takes priority. The PID loop is integrated under the BESS. HLC is supposed to consider the
BESS as controller of the grid supporting source.
Note: It is important to recognize between the cooperation/relation HLC to the BESS and InteliNeo530 to
PCS. All optional control modes are limited or given by the options offered by the PCS. For Example if PCS
only supports the P-Q control mode and is to be connected to the grid via AC precharge sequence, then the
InteliNeo 530 should be set also to P-Q mode. On the other hand, when the PCS is configured to U-f control
mode, the HLC can control the BESS either in U-f mode or in P-Q mode.
Breaker Control and Precharging in combintion with HLC:

Obviously there is several combination how the BESS and HLC (InteliNeo 6000) can coopearate in term of
breaker control (setpoint ESCB Type (page 394)) and precharge type settings (setpoint Precharge Type
(page 318)). Lets see some scenarios.
HLC does not control the Breaker, InteliNeo 530 does control the BCB. In this senario Inteli Neo 530
controls the BCB in all possible modes and can do AC or DC Precharge as needed. InteliNeo 6000 should
have is BCB in External control mode and it should recieve the BCB feedback only.
Situation when both controllers do control of its BCB can lead to these scenarios with various precharging
type settings:

InteliNeo
The BESS
6000
AC AC InteliNeo 6000 closes its BCB to alive bus bar, then the BESS can close its
Precharge Precharge BCB and start the AC precharrhing sequence.
Inteli Neo 6000 send the Start Command to the InteliNeo 530. It does the
DC precharge sequence and closes the BCB to the dead bus bar. Then the
DC DC
InteliNeo 6000 synchronize the BESS to the common bus bar or it can
Precharge Precharge
close the BCB to the dead common bus bar. This combination is only
possible when setpoint BESS Control Mode From HLC = U-f.
Inteli Neo 6000 closes the BCB to the live common bus bar. And send the
AC DC
start command to the InteliNeo 530. It does the DC precharge sequence
Precharge Precharge
and close the BCB after synchroinisation to the bus.
DC AC This Combination is faulty. BESS can not be never connected to the
Precharge Precharge common bus bar.
IMPORTANT: The BESS restricts the power demand according to the values ES Max Charging
Power (page 539) and ES Max Discharging Power (page 539) only in P-Q mode. In the U-f mode
the HLC has to ensure operation within these limits.
5.5.7 BESS Stabilization

IMPORTANT: This chapter is relevant only if Precharge Type (page 318) 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 325) 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 325) 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 325) has already elapsed.
In the event that the BESS voltage or frequency are not within limits within the Maximal Stabilization Time
(page 325) 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
317).
Note: The value of the Minimal Stabilization Time (page 325) setpoint has to be lower than the value of
Maximal Stabilization Time (page 325) setpoint.

5.5.8 Connecting To Load
BESS 200
Connecting To Dead Bus 200
Synchronization 201
BESS
Before connecting of the BESS to the load the LBI REMOTE START/STOP (PAGE 683) 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 Precharge Type (page 318). In
case the AC external option is set and setpoint Subgroup: BESS Control (page 317) is P-Q mode, the BCB
breaker can be closed immediately after the BESS is in the running phase. Once the breaker is closed the
Precharging TO (page 323) is counted down and after it is elapsed the BESS is already synchronized and
loaded. 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 and setpoint Subgroup: BESS Control (page 317) is U-f mode, connecting of the
BESS to the load is same as for the Gen-set. See the text below.
When the BESS Stabilization (page 199) 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 325) 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 384) and Frequency Governor Bias (page 375) setpoints.
Connecting to load depends on the state of MCB FEEDBACK (PAGE 670) 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 200) is applied, in other case the Synchronization (page 201) process is
needed.
Connecting To Dead Bus

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 670) 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 201
Synchronization Types 202
Synchronization Process
Behavior of synchronization process depends on, which breaker is used for synchronization and on which
Controller Mode (page 290) 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 Bus Voltage and BESS
Voltage of respective phases during synchronization.
Note: Based on Connection type (page 285) this value may either relates to Ph-N or to Ph-Ph values.
Connection type (page 285) 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 :
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 MINT - Stp Bus Meas Error (page 835) 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 391) starts to be counted down again.
If the Synchronization Timeout (page 391) elapses alarm Stp Synchronization Fail (page 840) is
issued.
Synchronization via BCB in MAN mode

BESS synchronization to the Mains (common bus bar) via BCB:
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.
6 back to Synchronization
Synchronization Types
There are two types of synchronization. Type of synchronization is adjusted via setpoint Synchronization Type
(page 390).
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 391). If the
synchronization is not successful within this period of time, the Stp Synchronization Fail (page 840) alarm will
be issued.
Voltage matching
The BESS voltage is regulated to match the Bus voltage with tolerance given by the setpoint Voltage Window
(page 391). The regulation is adjusted by the setpoints Voltage Gain (page 387) and Voltage Int (page 387).
Frequency/angle matching
The BESS frequency is regulated to match the Bus frequency first. The frequency regulation loop is active
(setpoints Frequency Gain (page 378) and Frequency Int (page 379)). Once the frequency is matched, the
regulation loop is switched to match the angle (setpoint Angle Gain (page 379)). When the angle is matched

with tolerance +/- Phase Window (page 392) for a time given by the setpoint Dwell Time (page 392) 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 648)/MCB FEEDBACK (PAGE 670) or Sd BCB Fail To Close
(page 836)/Sd ESCB Fail To Close (page 822) 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 391). If the synchronizing is not successful within this period of
time, the Stp Synchronization Fail (page 840) alarm will be issued.
The Bus Left or BESS frequency is regulated to match the Bus Right or Bus frequency + Slip Frequency (page
393) value and the window is set by setpoint Slip Frequency Window (page 393). When the Bus Left or BESS
frequency reaches (Bus Right or 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 392) the controller will allow BCB or MCB closing. The controller calculates periodically so
called preclosing angle (based on the actual value Slip Frequency (page 551) and CB closing delay given by
the setpoints BCB Latency (page 393). 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.112 Slip synchronization
Whenever the BESS Frequency (page 547) leaves off the Slip Frequency Window (page 393) (either
because of BESS Frequency (page 547), Bus Frequency (page 552) or setpoint Slip Frequency Window
(page 393) changes) the controller will reactivate frequency regulation loop and try to reach the target value
again. The Synchronization Timeout (page 391) timer runs regardless of this while whole slip synchronization
process is repeated. If the BESS Frequency (page 547) reaches the target frequency again the regulations are
frozen and if the BESS Frequency (page 547) remains in the window for the time longer than setpoint Dwell
Time (page 392) the controller will continue in the standard sequence as seen in the previous case. *If the
Synchronization Timeout (page 391) elapses the controller will immediately stop synchronization and issue
alarm Stp Synchronization Fail (page 840).

The window is limited by the actual measured Bus Frequency (page 552) if one of the window limits is below
this value (e.g. for setting where setpoint Slip Frequency (page 551) is set to 0.1Hz and setpoint Slip
Frequency Window (page 393) 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.115 Slip synchonization - deadband
Note: Due to the nature of this function it is possible that in limit cases the controller will regulate the BESS or
BESS frequency outside of protection limits. Example: Bus frequency is high but within its protection limits (e.g.
50.9 Hz, limit is 51 Hz). Slip Frequency (page 393) 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 393) 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 Bus Frequency protection limits to more rigid values than the BESS frequency
protection limits. In this case the setpoint Slip Frequency (page 393) can be set to 0.1Hz and the 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.9 Deenergized DC Bus after BCB is Opened in PQ Mode

If the BCB is opened and BESS regulation is in PQ Mode (LBI BESS Output Control Mode U-f/P-Q is active),
the BESS stays energized (precharged) and cannot be synchronized to the bus, because voltage and
frequency cannot be regulated. This situation is handled by logic, which opens ESCB breaker and deenergize
DC intermediate circuit (between PCS and ES). History record DC Bus Deenergized is written into the history.
After this process BESS begins a new start sequence.

5.5.10 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 670) 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 194) 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
683) 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 213) settings. Please see this chapter for
more information.
5.5.11 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 Gov
Low Limit (page 376) and Frequency Gov Hi Lim (page 376). 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.
The direction of frequency regulation required by frequency regulator of the BESS is given by the setpoint
Frequency Reg Character (page 375). A full range change of the frequency governor output (from Frequency
Gov Low Limit (page 376) to Frequency Gov Hi Lim (page 376)) should cause 5-10% change of the BESS
frequency (Frequency Gov Low Limit (page 376) ~ 95% , Frequency Governor Bias (page 375) ~ 100%,
Frequency Gov Hi Lim (page 376) ~ 105% ).

IMPORTANT: governor has to be adjusted for optimum performance before /Load control adjusting.
Check BESS phase sequence before the first BCB connection.

The internal is transformed to Up/Down pulse control. These pulses get out of the controller via binary outputs
FREQUENCY UP (PAGE 718) and FREQUENCY DOWN (PAGE 718). Length of pulses FREQUENCY UP (PAGE 718) and
FREQUENCY DOWN (PAGE 718) depends on the difference of the actual frequency and requested frequency
(actual power and requested power) and on the parameter Tau Frequency Gov Actuator (page 377). Tau
Frequency Gov Actuator (page 377) defines the pulse duration which is needed for the to from 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 378) to 0 and start the BESS in MAN Mode.
2. Set the BESS frequency by Frequency Governor Bias (page 375), Frequency Gov Low Limit (page
376) and Frequency Gov Hi Lim (page 376) to achieve frequency according to setpoint Nominal
Frequency (page 290).
3. Increase Frequency Gain (page 378) to unstable frequency control and decrease value by 30 % to
insure stable performance.
4. Adjust Frequency Int (page 379) to stable (fast and smooth) frequency control.
5. Set Angle Gain (page 379) 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 379) control is off).
7. Set Angle Gain (page 379). Synchroscope on the controller measure screen should move slowly and
stop in “up“ position. Set Angle Gain (page 379) 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 670) is closed). Switch off other
parts of the system (BESSs) while adjusting.
1. Set #System Baseload (page 275) setpoint to 30 % of one BESS.
2. Set Load Gain (page 380) to the same value as Angle Gain (page 379) and Load Int (page 380) 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 275) value. Check
that BESS power is positive (CT polarity).

5. Increase Load Int (page 380) to unstable load control and decrease value by 30 % to insure stable
performance. When Load Int (page 380) factor is set to zero BESS load can differ from required
#System Baseload (page 275).
6. To adjust and optimize Load Int (page 380) change #System Baseload (page 275) several times
between 30 and 70 % of BESSNominal power (page 280).
7. When BESS is running under full load check if
a. Speed regulator output voltage value is not limited (it does not reach Frequency Gov Low Limit
(page 376) or Frequency Gov Hi Lim (page 376)).
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.
Note: Load Sharing adjustment is the similar to the load control adjustement but BESS is running in Muiltiple
Island Operation with second BESS. One BESS is in Local Baseload and another in Load Sharing. Change
Local Baseload (page 275) and set Load Sharing Gain (page 381)/Load Sharing Int (page 381) to get
stable Load Shar regulation.
5.5.12 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
565) is internal value of the regulator which is transformed to range -10 .. 10 V based on setpoints Voltage
Regulator Low Limit (page 385) and Voltage Regulator High Limit (page 385) and stored in value Voltage
Regulator Output (page 564). 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.
Analog output
Voltage control outputs

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

The internal Voltage Request (page 565) is transformed to Up/Down pulse control. These pulses get out of the
controller via binary outputs AVRVOLTAGE UP (PAGE 730) and AVRVOLTAGE DOWN (PAGE 730). Length of pulses
AVRVOLTAGE UP (PAGE 730) and AVRVOLTAGE DOWN (PAGE 730) 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 386). Tau Voltage Regulator Actuator (page 386)
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 387), Voltage Int (page 387) to 0 and Voltage Regulator Bias (page 384) to
the half of expected applicable range.
2. Start the BESS in MAN Mode without load.
3. Change Voltage Regulator Bias (page 384) to 0% and 100% to check BESS voltage control range
(typically ± 10 % of BESS Nominal Voltage Ph-N (page 286)).
4. Set the BESS voltage by Voltage Regulator Bias (page 384), Voltage Regulator High Limit (page
385) and Voltage Regulator Low Limit (page 385) to achieve voltage according to setpoint BESS
Nominal Voltage Ph-N (page 286).
5. Increase Voltage Gain (page 387) to unstable voltage control and decrease value by 30 % to insure
stable performance.
6. Adjust Voltage Int (page 387) to stable (fast and smooth) voltage control and change Voltage Regulator
Bias (page 384) back to value which should correspond to the BESS Nominal Voltage Ph-N (page
286).
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 670) is closed). Switch
off other parts of the system (Gen-sets) while adjusting.
1. Set PF Gain (page 388) to the same value as parameters Voltage Gain (page 387) and Voltage Int
(page 387) to 0.
2. Set #System Baseload (page 275) = 30 % of BESSNominal power (page 280) and #System Power
Factor (page 278) = 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 388) to unstable point
and then decrease the value by 30 % to insure stable performance.
5. Increase Load Int (page 380) to unstable load control and decrease value by 30 % to insure stable
performance. When Load Int (page 380) factor is set to zero BESS load can differ from required
#System Power Factor (page 278).
6. Now your PF/Q regulation loop setup is done.
Note: Var Sharing adjustment is the similar to the var control adjustment but Gen-set is running in Multiple
Island Operation with second Gen-set. One Gen-set is in Local Baseload and another in Load Sharing.
Change Local Baseload (page 275) and set Load Sharing Gain (page 381)/Load Sharing Int (page 381)
to get stable Load Shar regulation.

5.5.13 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 670) 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 670) 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.
Ramping the power

Power up
Ramp up starts when value BESS Required P Target (page 562) is increased above value BESS Required P
(page 562). The first phase of the Parallel To Mains operation is the ramp of the BESS up to the desired power
level derived from the . The speed of the ramp is given by the setpoint Load Ramp (page 382). The setpoint
adjusts the ramp time for a change from Ramp Start Level (page 383) to 100 % of BESSNominal power (page
280) of the BESS.
Power down
Ramp down starts when value BESS Required P Target (page 562) drops, value BESS Required P (page
562) is ramped from BESS P (page 541) down to the new value of BESS Required P Target (page 562) based
on Load Ramp (page 382). Setpoint Load Ramp (page 382) determines how long it shall take to ramp down
from BESSNominal power (page 280) 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 383) for ramp BESS P (page 541) to Generator Unload BCB Open Level (page
382). Setpoint Soft Unload Ramp (page 383) determines how long it shall take to ramp down from
BESSNominal power (page 280) of the gen-set to 0 kW.
Power up
Ramp up starts when value BESS Required P Target (page 562) is increased above value BESS Required P
(page 562). The first phase of the parallel to Mains operation is the ramp of the system up to the desired power
level. Ramp starts when value BESS Required P Target (page 562) rises. If the MGCB has been just closed,
value BESS Required P (page 562) is ramped from 0 kw up to the new value of BESS Required P Target
(page 562) based on Load Ramp (page 382), otherwise is value BESS Required P (page 562) ramped from
Actual Active Power In PM (page 560). Setpoint Load Ramp (page 382) determines how long it shall take to
ramp up from 0 kW to Running Nominal Power Of All (page 560).
Examples Description
Nominal Mains Import = 100 kW
MGCB gets closed, Required P is ramped from 0 kW
Load Ramp = 10 s
to 50 kW in 5 s.
#System Baseload = 50 kW
Nominal Mains Import = 100 kW MGCB is closed, Total Running P = 50 kW, #System
Load Ramp = 10 s Baseload is changed to 70 kW. Required P is

#System Baseload = 70 kW ramped from 50 kW To 70 kW in 2 s.
Power down
Ramp down starts when value BESS Required P Target (page 562) drops, value BESS Required P (page
562) is ramped from Actual Active Power In PM (page 560) down to the new value of BESS Required P
Target (page 562) based on Load Ramp (page 382). Setpoint Load Ramp (page 382) determines how long it
shall take to ramp down from BESSNominal power (page 280) to 0 kW.
Soft unload
When BCB is about to be opened (BCB open command or stop command have been received), controller uses
for ramping to Generator Unload BCB Open Level (page 382). Value from which is ramping performed is
adjusted by setpoint Soft Unload Ramp (page 434).
6 back to Parallel To MainsOperation - MINT Application
Load control
If MCB FEEDBACK (PAGE 670) is active (parallel to Mains operation) the load of Gen-set group is controlled to
reach the power defined by setpoint #System Baseload (page 275) or by Load Sharing line. If the setpoint
#System Load Control PTM (page 273) = 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 380) and Load Int (page 380).
Baseload
Baseload ensures that the BESS keeps certain BESS P (page 541), which is given by BESS Required P (page
562). BESS Required P (page 562) is ramped to BESS Required P Target (page 562) using Load Ramp
(page 382).
If #System Load Control PTM (page 273)is set to Baseload the BESS Required P Target (page 562) is given
by:
If Load Request Source (page 272) = Setpoint, BESS Required P Target (page 562) = #System
Baseload (page 275).
If Load Request Source (page 272) = Analog External Value, BESS Required P Target (page 562) is
equal to value from LAI LOAD CONTROL ANEXT: LOCAL BASELOAD (PAGE 738).
Note: In case LAI Load Control ANEXT: Local Baseload (page 738) is not configured or has Invalid flag
(page 531), the setpoint source is used instead of AIN.
Load Shar
If #System Load Control PTM (page 273) 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 273) 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 530 BESS offers 2 modes for controlling of load. Load control ensures that the system keeps the certain
Actual Active Power In PM (page 560) value in parallel to Mains operation MCB STATUS (PAGE 723) and BCB
STATUS (PAGE 699) are closed, i.e. Breaker state (page 577) = ParalOper and at least one gen-set is excited.

System Baseload
System baseload ensures that the system keeps certain Actual Active Power In PM (page 560), which is given
by BESS Required P (page 562). BESS Required P (page 562) is ramped to BESS Required P Target
(page 562) using Load Ramp (page 382).
PF/Q control
If MCB FEEDBACK (PAGE 670) 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 278)/#System Base Q (page 279).Var Sharing
line is used automatically if Load Sharing is active or while island operation. If the setpoint #System PF Control
PTM (page 277) = 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 388) and PF Int (page 388).
Base PF/Q Control

Base PF/Q Control ensures that the Gen-set keeps certain BESS Q (page 542) to provide required BESS
Power Factor (page 544).
Base PF
#System PF Control PTM (page 277) has to be adjusted to Base PF. The BESS Required PF (page 564) with
BESS Required PF Character (page 564) are based on:
PF/Q Request Source (page 276) = Setpoint, requested PF is given by the Setpoint #System Power
Factor (page 278) or
PF/Q Request Source (page 276) = Analog External Value, requested PF is given by value from LAI PF
CONTROL: ANEXT BASE PF (PAGE 739).
Base Q
#System PF Control PTM (page 277) has to be adjusted to Base Q Control. The BESS Required PF (page
564) with BESS Required PF Character (page 564) are based on:
PF/Q Request Source (page 276) = Setpoint, BESS Required Q (page 563) is given by #System
Base Q (page 279) or
PF/Q Request Source (page 276) = Analog External Value, BESS Required Q (page 563) is given by
value from LAI Q Control: ANEXT Base Q (page 739).
Var Shar
If #System PF Control PTM (page 277) is Var Shar the Gen-set PF/Q is controlled by InteliMains controller.

5.5.14 Power Management
Basic power management 213
Principle of power management 214
Load reserve 215
Dynamic Spinning Reserve 216
Starting sequence 216
Stopping sequence 217
Absolute power management 218
Relative power management 221
Priorities 223
Priority auto swap 224
Minimal running power 231
IMPORTANT: Power management is relevant only for MINT application.
IMPORTANT: The Mains 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 215). 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 400) is used to select the absolute or relative mode.
The Load Reserve can be influenced by the Dynamic Spinning Reserve (page 216) 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 224) 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.
Basic power management

The setpoint Power Management (page 398) 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 683).
The Logical binary input REMOTE START/STOP (PAGE 683)Remote Start/Stop requests the system to start or stop.
If the input is not active, the system stops with delay #System Stop Delay (page 403) 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 403) 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 683)Remote Start/Stop is activated., the option of setpoint Power Management
(page 398) = Enabled and the AUTO mode is selected.
Note: The Mains 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 683) activation a
count down of #System Start Delay (page 403). The delay is given by setpoint Power Management
DelayPower Management Delay (page 399). 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.
6 back to Power Management
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 Mains is started after delay given by the setpoint #Next Engine Start Delay (page
420) is elapsed. Once the Mains runs the controller evaluates stopping conditions based on load reserves and
priorities. If the reserve is sufficient enough to stop a particular Mains, it is stopped after delay given by the
setpoint #Next Engine Stop Delay (page 421) is elapsed. All the time the system stop condition – i.e. the
Logical binary inputs REMOTE START/STOP (PAGE 683)Remote Start/Stop deactivated – is evaluated as well.
Once the delay given by the setpoint #System Stop Delay (page 403) has elapsed all BESSs in AUTO mode
are stopped. Following figure depicts the system activation and deactivation logic.

Setpoint #Overload Next Start Delay (page 424) is used in case that #Overload Next Start Protection (page
423) is enabled and BESSs are running at #Overload Next Start Level (page 423) 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 InteliNeo
530 BESS 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 Mains on the bus.
ΣPg*Nom .. Sum of Nominal power of all Mains on the bus apart of the one, which is going to be stopped.
ΣPgAct .. Sum of Actual power of all Mains on the bus = system load.
BaseLd .. Baseload is given by the setpoint #System Baseload (page 275)
Note: System starting sequences may be very different due to their complexity (i.e. Mains 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 558) and Dynamic Spinning Reserve Offset (page 559) 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 558) is added to required load reserve given by setpoints #Starting Load
Reserve 1 (page 405) and #Stopping Load Reserve 1 (page 406) (according to actual load reserve set 1, 2, 3
or 4). The value Dynamic Spinning Reserve Offset (page 559) is added only to required stopping load reserve
given by setpoints #Stopping Load Reserve 1 (page 406) (according to actual load reserve set 1, 2, 3 or 4) to
create some dynamic offset between starting and stopping load reserve.
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 Mains 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 Mains is requested to join the
already running Mains(s) to the bus.
Image 5.116 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 218) and Relative power management (page 221).
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 420), 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.117 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 218) and Relative power management (page 221).
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 421), 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 400) is set to ABS [kW] mode.

Image 5.118 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.119 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 405) (or other selected reserve set) in
following way:
Sum of nominal power for start - #Starting Load Reserve 1 (page 405) (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 406) (or other selected reserve set) in
following way:
Sum of nominal power for stop - #Stopping Load Reserve 1 (page 406) (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 405) and #Stopping Load Reserve 1 (page 406)
#Starting Load Reserve 2 (page 408) and #Stopping Load Reserve 2 (page 409) considered if binary
input LOAD RES 2 ACTIVE (PAGE 666)Load Res 2 Active 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 400) is set to REL [%] mode.
Image 5.120 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.121 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 407) (or other selected reserve
set) in following way:
(100 % - #Starting Rel Load Reserve 1 (page 407) (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 407) (or other selected reserve set)
in following way:
(100 % - #Stopping Rel Load Reserve 1 (page 407) (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 407) and #Stopping Rel Load Reserve 1 (page 407)
#Starting Rel Load Reserve 2 (page 410) and #Stopping Rel Load Reserve 2 (page 411) considered
if binary input LOAD RES 2 ACTIVE (PAGE 666)Load Res 2 Active 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 PriorityPriority (page 401). Lower number
represents "higher" priority, i.e. a BESS with lower number starts before another one with higher number. In other
words, the setpoint PriorityPriority (page 401) 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.122 Example of priorities in power management
By choosing the setpoint PriorityPriority (page 401) = 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 683)Remote Start/Stop activated).
The LBI Top PriorityTOP PRIORITY (PAGE 686) can be used to force priority 0 into the setpoint PriorityPriority
(page 401). 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 223), 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 PriorityPriority (page 401). 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 402) = RUN HOURS.
The value of running hours which is used in run hours equalization is calculated by following formula:
RHE = Running Hours (page 573) - Run Hours Base (page 424)
RHE is considered value for running hours equalization, Running Hours (page 573) is a cumulative sum of run
hours available in statistic values of the controller, Run Hours Base (page 424) 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 425) (i.e.
#Run Hours Max Difference (page 425) + 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.123 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
424))

BESS 2 running hours = 450 -> running hours considered in RHE = 200 (250 - Run Hours Base (page
424))
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 425) 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 425) (i.e. 10h). The BESS 1
runs 100 + #Run Hours Max Difference (page 425) + 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 425). The BESS 2 runs 11 hours to equalize the RHE of both BESSs and then additional #Run Hours
Max Difference (page 425) + 1 hours (i.e. 11 + 10 + 1 = 22 hours). The evaluation of RHE1 and RHE2 is shown
on the figure below.
Image 5.124 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 425) +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 425) = 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 425) 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 402) = Efficiency.
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 400) = ABS (kW)
Nominal power of BESS > actual load demand + #Starting Load Reserve 1 (page 405)
#Power Management Mode (page 400) = REL (%)
Nominal power of BESS > (actual load demand × 100)/(100 - #Starting Rel Load Reserve 1
(page 407))
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.127 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 400) = ABS (kW) and
#Starting Load Reserve 1 (page 405) = 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
100 2 [10h] 200 50
120 2 [20h] 200 60
120 2 [30h] 3 start RHE Swap 400 30

Total Running
[kW]
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
4
680 5 start Gen#5 joins (LDS) 800 85
2
5
740 1 800 93

Total Running
[kW]
4
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 672), MIN RUN POWER ACT 2
(PAGE 672) and MIN RUN POWER ACT 3 (PAGE 673)Min Run Power Act 1, Min Run Power Act 2 and Min Run
Power Act 3 in IG 1000 or IM 1010 MC controllers.

Image 5.128 Minimal running power
Setpoints #Min Run Power 1 (page 419), #Min Run Power 2 (page 419) or #Min Run Power 3 (page 420)
are adjusted to 400 kW. Once the #Min Run Power 1 (page 419), #Min Run Power 2 (page 419) or #Min Run
Power 3 (page 420) 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.15 Regulation Loops
Regulation loops overview
Regulation loops overview
Related
Loop type Related setpoints Related Operation
applications
Unloaded Run
Frequency Gain (page 378)
Frequency MINT Synchronization
Frequency Int (page 379)
Single Island
Unloaded Run
Voltage Gain (page 387)
Voltage MINT Synchronization
Voltage Int (page 387)
Single Island
Angle
MINT Angle Gain (page 379) Phase Match Synchronization
regulation
Load Gain (page 380)
Load MINT Parallel To Mains
Load Int (page 380)
PF Gain (page 388)
PF control MINT Parallel To Mains
PF Int (page 388)
Load Sharing Gain (page 381)
Load sharing MINT Multiple Island
Load Sharing Int (page 381)
VAr Sharing Gain (page 389)
VAr sharing MINT Multiple Island
VAr Sharing Int (page 389)
Voltage, PF, VAr sharing have one common output = Voltage Request (page 565). 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 562) and
Voltage Regulator Output (page 564) are kept on the levels given by setpoints Frequency Governor Bias
(page 375) and Voltage Regulator Bias (page 384).
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 378).
The frequency regulation loop can be active after the Minimal Stabilization Time (page 325)
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 325)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.
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.129 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.
5.5.16 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 458) and works in all
controller modes. Setpoint Sunrise/Sunset Latitude (page 459) and setpoint Sunrise/Sunset Longtitude
(page 459) 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 685). Otherwise, these setpoints need to be set
manually. Values Real Sunrise Time (page 586), Real Sunset Time (page 586), Time To Sunrise (page
587), Time To Sunset (page 587) are calculated from setpoints Sunrise/Sunset Latitude (page 459) and
Sunrise/Sunset Longtitude (page 459). LBO DAY/NIGHT (PAGE 706) is active during the day (between
Sunrise and Sunset Time).
6 back to Application related functions

6 Communication
6.1 PC 236
6.2 Connection to 3rd party systems 239
6.1 PC
6.1.1 Direct communication 236
6.1.2 Remote communication 237
6.1.1 Direct communication

Computer can be connected to InteliNeo 530 BESS via USB, RS485 or ethernet interface.
Connection via USB

USB A to B cable can be used for communication via USB ports. The InteliNeo 530 BESS 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 296) 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 181) interface which is in default configured to port Communication
peripherals (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
6.1.2 Remote communication

The InteliNeo 530 BESS can be connected also remotely via built-in ethernet ports. For remote connection
the Untrusted (page 181) interface which is in default configured to port Ethernet (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 181) 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: Ethernet (page 298) .
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.
6.2 Connection to 3rd party systems

6.2.1 SNMP 239
6.2.2 Modbus-RTU, Modbus/TCP 241
6.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 306). The setpoints SNMP
RD Community String (page 515) and SNMP WR Community String (page 515) 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: Ethernet (page 298) by the setpoints SNMP Traps IP Address
1 (page 514) and SNMP Traps IP Address 2 (page 514). 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 307).
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
AMF start
Remote start

Stop commands
Stop button
AMF stop
Remote stop
Breaker records
Load on Microgrid
Load on Mains
Others
Test on load
Mains fail
Mains returned
6.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 . The serial speed for Modbus-RTU communication is adjusted by the
setpoint RS485 Modbus Speed (page 295) and the serial mode is adjusted by the setpoint RS485
Modbus Mode (page 296). Only 1 client can be connected at once through this type of connection.
Modbus/TCP (Modbus server) can be used with the Communication peripherals (page 19) / Ethernet
(page 19) / Communication peripherals (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 511).
Note: Setpoint Modbus Client Inactivity Timeout (page 513) is common for Communication
peripherals (page 19).
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 InteliNeo 530 BESS 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.
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).
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 243).
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 243).
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
LSB = value, LSB
MSB1 = value, byte 3 (MSB)
LSB1 = value, byte 2
MSB2 = value, byte 1
LSB2 = value, byte 0 (LSB)
MSB1 = value, byte 3 (MSB)
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.
…
Zero-terminated string of MSB1 = ASCII value of the 1. character
LongStr 16
max 31 ASCII characters. LSB1 = ASCII value of the 2. character

Number of
Data type Meaning Data maping
registers
MSB2 = ASCII value of the 3. character
…
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
MSB2 = Alarm level *)
LSB2 = Alarm status **)
Alarm An item of the Alarmlist 27 MSB3 = alarm string ***)
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
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.
4700 1 write Bool
Remote Start/Stop, AMF Start, Peak
Shaving). Set the coil to log1 to start the

Register Number of
addresses registers
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 625)
5100 - 5101 2 read/write Int32 RemoteControl4B 1 (page 627)
5200 1 read/write Binary16 RemoteControlBin (page 628)
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
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 Name of
Source
Modbus C.O.# Value Bit Name
= Value Bit # Group
Addr. State # Name of Activated by protection(s):
= State
Prot. Addr. State
Binary Controller
00000 Value 8235 0 MCBBCB Feedback
Inputs I/O
Binary Controller
00001 Value 8235 1 Remote Start/StopMCBCU-BIN-2
Inputs I/O
Binary Remote TESTCU-BIN- Controller
00002 Value 8235 2
Inputs 3BESS Ready To Load I/O
We will read state of MCBBCB 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 244)

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 247)

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

7 Technical data
Power supply
Power supply range 8-36 V DC
Power consumption (without modules) 6W
RTC battery Replaceable, 3V
Fusing power 5 A / 6 × 0.5 A BOUT
Fusing ESTOP 2A
Max. Heat Dissipation 10 W
Operating conditions
Protection degree IP65
Operating temperature -30 °C to +70 °C (-40 °C to +70 ˚C)*
Storage temperature -30 ˚C to +80 ˚C
95 % non-condensing
Operating humidity
(EN 60068-2-30)
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.
Voltage measurement
Measurement inputs 3ph-n Bus voltage
10-277 V AC / 10-480 V AC (EU)
Measurement range
10-346 V AC / 10-600 V AC (US/Canada)
Linear measurement and protection range
350 V AC Ph-N / 660 V AC Ph-Ph
(maximal voltage)
Accuracy 1%
Frequency range 30-70 Hz (accuracy 0.1 Hz)
Input impedance 0.72 MΩ ph-ph , 0.36 MΩ ph-n
AOut1/VRO
Isolation Isolated
Type max ±10 V DC
Aout2/SRO
Isolation Non-isolated
±10 V DC
Type
PWM selectable by jumper
Display
Type Build-in colour TFT 5"
Resolution 800 × 480 px
Communications
USB device Non-isolated, USB type B
USB host Non-isolated, USB type A
RS 485 Isolated
Ethernet 10/100 Mbit
CAN 1A Isolated, 250/50 kbps
CAN 2A Terminator impedance 120Ω

Current measurement
3ph BESS current
Measurement inputs
1ph Mains current
Measurement range 5A
Max. allowed current 10 A
Accuracy ±20 mA for 0-2 A; 1 % of value for 2-5 A
Input impedance 0.68 MΩ ph-ph , 0.34 MΩ ph-n
E-Stop
Dedicated terminal for safe Emergency Stop input.
Physical supply for binary outputs 1 & 2.
Binary inputs
Number 8, non-isolated
Close/Open 0-2 V DC close contact
indication 6-36 V DC open contact
Binary outputs
Number 8, non-isolated
Max. current BO 1-8 = 0.5 A
Switching to Positive supply terminal
Analog inputs
Number 4, switchable (R/U/I)
Range R = 0-2500 Ω; U = 0-10 V; I = 0-20 mA
R: ±2 % from value ±5 Ω in range 0-250 Ω
R: ±4 % from value in range 250 Ω-2500 Ω
Accuracy
U: 1 % from value ±100 mV
I: 1 % from value ±0.2 mA
+5 V Power supply output

Max. current 100 mA
Note: * If the device is powered on above -30 °C

8 Appendix
8.1 Controller objects 261
8.2 Alarms 804
8.3 Modules 883
8.1 Controller objects

8.1.1 List of controller objects types
8.1.3 Setpoints 262
8.1.4 Values 531
8.1.5 Application Curves 638
8.1.6 Logical binary inputs 641
8.1.7 Logical binary outputs 687
8.1.8 Logical analog inputs 731
8.1.9 Fixed Protection States 740
8.1.10 User Protection States 746
8.1.11 PLC 749

8.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.
8.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 264).
List of group of setpoints

Group: Process Control 272
Group: Basic settings 279
Group: Communication Settings 295
Group: Ethernet 298
Group: BESS settings 317

Group: Protections 329
Group: ES Protections 340
Group: Protections 349
Group: SpeedFrequency/Load Control 375
Group: Voltage/PF Control 384
Group: AC Synchronization 390
Group: Power Management 398
Group: Grid Codes 432
Group: Load Shedding 435
Group: User Buttons 438
Group: Analog Switches 446
Group: Scheduler 456
Group: Maintenance Timers 471
Group: Geo-Fencing 477
Group: Plug-In Modules 481
Group: CM-RS232-485 482
Group: CM-4G-GPS 486
Group: CM-Ethernet 505
Group: EM-BIO8-EFCP 526

List of setpoints
Group: Process Control 272 Mains/Bus Nominal Voltage Ph-Ph 287

Subgroup: Load Control 272 BESS VT Ratio 287
Load Request Source 272 BESS Voltage Input Range Select 288
#System Load Control PTM 273 Bus VT Ratio 288
Local Baseload 274 Bus Voltage Input Range 289
BESS P request source 274 Subgroup: Phase Rotation 289
Local Baseload 275 Phase Rotation 289
#System Baseload 275 Subgroup: Frequency settings 290
Subgroup: PF/Q Control 276 Nominal Frequency 290
PF/Q Request Source 276 Subgroup: Controller settings 290
#System PF Control PTM 277 Controller Mode 290
Local Base Power Factor 277 Power On Mode 291
#System Power Factor 278 Fault Reset To Manual 291
Local Base Q 278 Horn Timeout 292
#System Base Q 279 Fail Safe Binary State 292
Group: Basic settings 279 Run Hours Source 293
Subgroup: Name 279 User Logging Record 293
Controller Name 279 Subgroup: Power Supply Protections 294
Subgroup: Power settings 280 Power Supply <V 294
Samax 280 Power Supply >V 294
BESSNominal power 280 Power Supply <> Delay 294
PCS Efficiency 281 Group: Communication Settings 295
Subgroup: Current settings 281 Subgroup: Controller Address 295
ES Nominal Current 281 Controller Address 295
BESS Nominal Current 282 Subgroup: RS485 Settings 295
BESS CT Ratio Prim 282 RS485 Modbus Speed 295
BESS CT Ratio Sec 283 RS485 Modbus Mode 296
Aux CT Ratio PrimC 283 RS485 Mode 296
Aux CT Ratio Sec 284 RS485 Communication Speed 297
3Ph CT Location 284 Group: Ethernet 298
Subgroup: Voltage settings 284 Subgroup: TCP/IP Settings 298
ES Nominal Voltage 284 IP Address Mode 298
Connection type 285 IP Address 299
Evaluated Voltage Protections 285 Subnet Mask 299
BESS Nominal Voltage Ph-N 286 Gateway IP 300
Gen Nominal Voltage Ph-Ph 286 DNS Mode 300
Bus Nominal Voltage Ph-N 287 DNS IP Address 1 301

DNS IP Address 2 301 Wrn Message 315
IP Firewall 302 Subgroup: RTC Synchronization 316
Subgroup: AirGate Settings 302 Time Zone 316
AirGate Port 302 NTP Clock Synchronization 316
AirGate Address 303 NTP Server 317
AirGate Connection 303 Group: BESS settings 317
Subgroup: ComAp Client Settings 304 Subgroup: BESS Control 317
Direct Connection 304 HLC Control Mode 318
Direct Connection Port 304 Precharge Type 318
ComAp Client Inactivity Timeout 305 Subgroup: Energy Storage 319
Subgroup: Modbus Server Settings 305 ESCB Current Open Level 319
Modbus Server 305 ESCB Current Open Timeout 319
Modbus Client Inactivity Timeout 306 ES Safety Charging Current 319
Subgroup: SNMP Settings 306 ES Safety Discharging Current 320
SNMP Agent 306 System Safety Discharging Level 320
SNMP Trap Format 307 Subgroup: SOC Control 321
SNMP Traps IP Address 1 307 SOC High Target 321
SNMP Traps IP Address 2 307 SOC High Hysteresis 321
SNMP RD Community String 308 SOC Low Target 322
SNMP WR Community String 308 SOC Low Hysteresis 322
SNMP Engine User Name 308 Subgroup: Battery Cycles 323
SNMP Privacy Protocol 309 Max Battery Cycles Per Day 323
SNMP Authentication Protocol 309 Subgroup: Starting Timers 323
SNMP Security Level 309 Precharging TO 323
Subgroup: E-mail Settings 310 ES Ready To Load TO 324
SMTP Server Address 310 PCS Ready To Start TO 324
SMTP Sender Address 310 PCS Ready To Load TO 324
SMTP User Name 311 Minimal Stabilization Time 325
SMTP User Password 311 Maximal Stabilization Time 325
SMTP Encryption 312 Run Only Block Delay 1 326
E-mail Address 1 312 Run Only Block Delay 2 327
E-mail Address 4 313 Run Only Block Delay 3 328
E-mail Address 3 313 Subgroup: Stopping Timers 328
E-mail Address 2 313 Stop Time 328
Subgroup: Messages Settings 314 Subgroup: ECU Settings 329
E-mail/SMS Language 314 Open Param Governor Speed Adjust 329
Event Message 314 Group: Protections 329
Sd Message 315 Subgroup: Overload Protection 329
Stp Message 315 BESS 2POverload Evaluation Level 329

BESS 2POverload Evaluation Delay 330 Group: Group: PCS Protections 344
Subgroup: Current Protection 331 Subgroup: Current Protection 344
BESS Short Circuit 331 PCS Short Circuit Level 344
BESS Short Circuit Delay 332 PCS Short Circuit Delay 345
IDMT BESS >A Delay 332 PCS IDMT >A Delay 345
BESS Current Unbalance 333 Subgroup: Voltage Protection 346
BESS Current Unbalance Delay 333 PCS >V 346
Subgroup: Voltage Protection 334 PCS >V Delay 346
BESS >V 334 PCS >>V 347
BESS >V Delay 334 PCS >>V Delay 347
BESS >>V 335 PCS <V 347
BESS >>V Delay 335 PCS <V Delay 348
BESS <V 336 PCS <<V 348
BESS <V Delay 336 PCS <<V Delay 348
BESS V Unbalance 337 Group: Protections 349
BESS V Unbalance Delay 337 Subgroup: Overload Protection 349
Subgroup: Frequency Protection 338 BESS IDMT Overload Protection 349
BESS >f 338 Subgroup: Current Protection 350
BESS >f Delay 338 Short Circuit Protection 350
BESS <f 339 BESS IDMT >A Protection 350
BESS <f Delay 339 BESS Current Unbalance Protection 352
Subgroup: Earth Fault Current Protection 340 PCS Short Circuit Protection 352
IDMT Earth Fault Current Sd 340 PCS IDMT >A Protection 353
IDMT Earth Fault Current Delay 340 Subgroup: Voltage Protection 355
Group: ES Protections 340 BESS >V Protection 355

Subgroup: Voltage Protection 340 BESS >>V Protection 356
ES >V 340 BESS <<V Protection 357
ES >V Delay 341 Voltage Unbalance Protection 357
ES >>V 341 ES >V Protection 358
ES >>V Delay 341 ES >>V Protection 359
ES <V 342 ES <V Protection 359
ES < VDelay 342 ES <<V Protection 360
ES <<V 342 PCS >V Protection 360
ES <<V Delay 343 PCS >>V Protection 361
Subgroup: SOC Protection 343 PCS <V Protection 361
ES <SOC 343 PCS <<V Protection 362
ES >SOC 343 Subgroup: Frequency Protection 363
ES <<SOC 344 BESS >f Protection 363
ES >>SOC 344 BESS <f Protection 364

Subgroup: Bus Meas Error 365 Soft Unload Ramp 383
Bus Meas Error 365 Group: Voltage/PF Control 384
Subgroup: Phase Rotation Protection 365 Subgroup: Voltage Control 384
Phase Rotation Protection 365 Voltage Regulator Character 384
Subgroup: Earth Fault Current Protection 366 Voltage Regulator Bias 384
IDMT Earth Fault Current Protection 367 Voltage Regulator Low Limit 385
Subgroup: Loss of Mains Protections 368 Voltage Regulator High Limit 385
Vector Shift Protection 368 Tau Voltage Regulator Actuator 386
ROCOF1 Protection 369 PCS Voltage Droop Slope 386
ROCOF2 Protection 370 Subgroup: Regulation Loops 387
ROCOF3 Protection 371 Voltage Gain 387
ROCOF4 Protection 372 Voltage Int 387
Subgroup: SOC Protection 373 PF Gain 388
ES <SOC 373 PF Int 388
ES >SOC 373 VAr Sharing Gain 389
ES <<SOC 374 VAr Sharing Int 389
ES>>SOC 374 Group: AC Synchronization 390
Group: SpeedFrequency/Load Control 375 Subgroup: AC Synchronization 390
Subgroup: SpeedFrequency Control 375 Synchronization Type 390
Frequency Reg Character 375 Synchronization Timeout 391
Frequency Governor Bias 375 Voltage Window 391
Frequency Gov Low Limit 376 BESS to Bus Phase Shift 391
Frequency Gov Hi Lim 376 Phase Window 392
Frequency Governor PWM Rate 376 Dwell Time 392
Tau Frequency Gov Actuator 377 Slip Frequency 393
PCS Frequency Droop Slope 377 Slip Frequency Window 393
Subgroup: Regulation Loops 378 BCB Latency 393
Frequency Regulation Loop 378 Subgroup: DC Synchronization 394
Frequency Gain 378 DC Voltage Window 394
Frequency Int 379 Subgroup: Breaker Control 394
Angle Gain 379 ESCB Type 394
Load Gain 380 BCB Control Mode 394
Load Int 380 Attempts To Close Breaker 395
Load Sharing Gain 381 Delay Between Closing Attempts 396
Load Sharing Int 381 Waiting For Breaker Feedback 396
Subgroup: Load Transfer 382 #Neutral Contactor Control 397
Generator Unload BCB Open Level 382 Group: Power Management 398
Load Ramp 382 Subgroup: Power Management Control 398
Ramp Start Level 383 Power Management 398

Power Management Delay 399

#Power Management Mode 400 #Overload Next Start Delay 424
Priority 401 Subgroup: Run Hours Equalization 424
#Priority Auto Swap 402 Run Hours Base 424
#System Start Delay 403 #Run Hours Max Difference 425
#System Stop Delay 403 Subgroup: Efficient Mode 425
Dynamic Spinning Reserve 404 #Power Band Change Up Delay 425
Subgroup: Load Reserve Set 1 405 #Power Band Change Down Delay 426
#Starting Load Reserve 1 405 Subgroup: Group Settings 426
#Stopping Load Reserve 1 406 Control Group 426
#Starting Rel Load Reserve 1 407 Group Link L 427
#Stopping Rel Load Reserve 1 407 Group Link R 427
Subgroup: Load Reserve Set 2 408 Group: Loss of Mains Protections 428
#Starting Load Reserve 2 408 Subgroup: Loss of Mains Protections 428
#Stopping Load Reserve 2 409 Vector Shift Limit 428
#Starting Rel Load Reserve 2 410 ROCOF1 Windows Length 428
#Stopping Rel Load Reserve 2 411 ROCOF1 df/dt 429
Subgroup: Load Reserve Set 3 412 ROCOF2 Windows Length 429
#Starting Load Reserve 3 412 ROCOF2 df/dt 430
#Stopping Load Reserve 3 413 ROCOF3 Windows Length 430
#Starting Rel Load Reserve 3 414 ROCOF3 df/dt 431
#Stopping Rel Load Reserve 3 415 ROCOF4 Windows Length 431
Subgroup: Load Reserve Set 4 416 ROCOF4 df/dt 432
#Starting Load Reserve 4 416 Group: Grid Codes 432
#Stopping Load Reserve 4 417 Subgroup: Dynamic Support 432
#Starting Rel Load Reserve 4 418 Post VRT Priority 432
#Stopping Rel Load Reserve 4 418 Post VRT Ramp 433
Subgroup: Minimal Running Power 419 Subgroup: Soft Unload 433
#Min Run Power 1 419 Soft Unload Priority 433
#Min Run Power 2 419 Soft Unload Ramp 434
#Min Run Power 3 420 Group: Load Shedding 435
Subgroup: Start/Stop Timing 420 Subgroup: Load Shedding 435
#Next Engine Start Delay 420 Load Shedding Active 435
#Next Engine Stop Delay 421 Load Shedding Level 436
#Slow Stop Delay 421 Load Shedding Delay 436
Subgroup: Slow Stop Protection 422 Load Reconnection Level 437
Slow Stop Stay In Load Sharing 422 Load Reconnection Delay 437
Subgroup: Over Load Next Start Protection 423 Auto Load Reconnection 438
#Overload Next Start Protection 423 Group: User Buttons 438

Subgroup: User Buttons 438
#Overload Next Start Level 423
User Button 1 438

User Button 2 439 Subgroup: Analog Switch 9 454
User Button 3 439 AIN Switch09 On 454
User Button 4 440 AIN Switch09 Off 454
User Button 5 440 Subgroup: Analog Switch 10 455
User Button 6 441 AIN Switch10 On 455
User Button 7 441 AIN Switch10 Off 455
User Button 8 442 Group: Scheduler 456
User Button 9 442 Subgroup: Time & Date 456
User Button 10 443 Time 456
User Button 12 444 Date 456
User Button 13 444 Time Stamp Period 456
User Button 14 445 Time Zone 457
User Button 15 445 DST Switching Mode 457
User Button 16 446 Time Mode 458
Group: Analog Switches 446 DST Period Rule 458

Subgroup: Analog Switch 1 446 Subgroup: Sunrise/Sunset 458
AIN Switch01 On 446 Sunrise/Sunset Function 458
AIN Switch01 Off 447 Sunrise/Sunset Latitude 459
Subgroup: Analog Switch 2 447 Sunrise/Sunset Longtitude 459
AIN Switch02 On 447 Subgroup: Timer 1 460
AIN Switch02 Off 447 Timer 1 Function 460
Subgroup: Analog Switch 3 448 Timer 1 Setup 461
AIN Switch08 On 453 Group: Maintenance Timers 471
AIN Switch08 Off 453 Subgroup: Maintenance Timer 1 471

Maintenance Timer 1 RunHours 471 Subgroup: COM2 Setting 484
Maintenance Timer 1 Interval 472 COM2 Mode 484
Maintenance Timer 1 Protection 472 COM2 Communication Speed 484
Subgroup: Maintenance Timer 2 473 COM2 Modbus Mode 485
Maintenance Timer 2 RunHours 473 COM2 MODBUS Communication Speed 485
Maintenance Timer 2 Interval 473 Group: CM-4G-GPS 486
Maintenance Timer 2 Protection 474 Subgroup: Cellular Interface 486
Subgroup: Maintenance Timer 3 474 Internet Connection 486
Maintenance Timer 3 RunHours 474 Network Mode 486
Maintenance Timer 3 Interval 475 Access Point Name 486
Maintenance Timer 3 Protection 475 Connection Check IP1 487
Subgroup: Maintenance Timer 4 476 Connection Check IP2 488
Maintenance Timer 4 RunHours 476 Connection Check IP3 489
Maintenance Timer 4 Interval 476 Subgroup: TCP/IP Settings 490
Maintenance Timer 4 Protection 477 DNS Mode 490
Group: Geo-Fencing 477 DNS IP Address 1 490

Subgroup: Geo-Fencing 477 DNS IP Address 2 491
Geo-Fencing 477 IP Firewall 491
Subgroup: Position 478 Subgroup: AirGate Settings 492
Home Latitude 478 AirGate Connection 492
Home Longitude 478 AirGate Address 492
Subgroup: Fence 1 479 Airgate Port 493
Fence 1 Protection 479 Subgroup: ComAp Client Settings 493
Fence 1 Radius 479 ComAp Client Inactivity Timeout 493
Fence 1 Delay 480 Direct Connection 494
Subgroup: Fence 2 480 Direct Connection Port 494
Fence 2 Protection 480 Subgroup: E-mail Settings 495
Fence 2 Radius 481 SMTP Server Address 495
Fence 2 Delay 481 SMTP Sender Address 495
Group: Plug-In Modules 481 SMTP User Name 496
Subgroup: Slot A 481 SMTP User Password 496
Slot A 481 SMTP Encryption 497
Subgroup: Slot B 482 E-mail Address 1 497
Slot B 482 E-mail Address 4 498
Group: CM-RS232-485 482 E-mail Address 3 498
Subgroup: COM1 Setting 482 E-mail Address 2 498
COM1 Mode 482 Subgroup: Messages Settings 499
COM1 Communication Speed 483 Telephone Number 1 499
COM1 Modbus Mode 483 Telephone Number 2 499
COM1 MODBUS Communication Speed 484

Telephone Number 3 500 SNMP Traps IP Address 2 514
Telephone Number 4 500 SNMP RD Community String 515
E-mail/SMS Language 501 SNMP WR Community String 515
Event Message 501 SNMP Engine User Name 515
Sd Message 501 SNMP Privacy Protocol 516
Stp Message 502 SNMP Authentication Protocol 516
Wrn Message 502 SNMP Security Level 516
Subgroup: GPS Settings 502 Subgroup: E-mail Settings 517
GPS Tracking 502 SMTP Server Address 517
Subgroup: RTC Synchronization 503 SMTP Sender Address 517
Time Zone 503 SMTP User Name 518
NTP Clock Sync 503 SMTP User Password 518
NTP Server 504 SMTP Encryption 519
GPS Clock Sync 504 SMTP User Name 519
Group: CM-Ethernet 505 SMTP User Password 520
Subgroup: TCP/IP Settings 505 SMTP Encryption 520
IP Address Mode 505 E-mail Address 1 521
IP Address 506 E-mail Address 2 521
Subnet Mask 506 E-mail Address 3 521
Gateway IP 507 E-mail Address 4 522
DNS Mode 507 Subgroup: Messages Settings 522
DNS IP Address 1 508 E-mail/SMS Language 522
DNS IP Address 2 508 Event Message 522
IP Firewall 509 Sd Message 523
Subgroup: AirGate Settings 509 Stp Message 523
AirGate Connection 509 Wrn Message 523
AirGate Address 510 Subgroup: RTC Synchronization 524
AirGate Port 510 Time Zone 524
Subgroup: ComAp Client Settings 511 NTP Clock Synchronization 524
ComAp Client Inactivity Timeout 511 NTP Server 525
Direct Connection 511 Group: EM-BIO8-EFCP 526
Direct Connection Port 512 Subgroup: EFCP Settings 527
Subgroup: Modbus Server Settings 512 Earth Fault Current Protection 528
MODBUS Server 512 Earth Fault Delay 529
Modbus Client Inactivity Timeout 513 Earth Fault CT Input Range 529
Subgroup: SNMP Settings 513 Earth Fault CT Ratio 530
SNMP Agent 513 Earth Fault Current Sd 530
SNMP Trap Format 514 6 back to Controller objects
SNMP Traps IP Address 1 514

Group: Process Control
Subgroup: Load Control
Load Request Source
Setpoint group Process Control Related FW 1.0.0

Range [units] Setpoint / Analog External Value [-]
Default value Setpoint Force value YES
Step [-]
Comm object 20727 Related applications MINT
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts source type of requested load control.
Active Application (page 576) = MINT
Load Request Source Source

#System Baseload (page 275) or LOAD CONTROL ANEXT: LOCAL
Setpoint
BASELOAD (PAGE 738)
Analog External Value LOAD CONTROL ANEXT: LOCAL BASELOAD (PAGE 738)
See Load control (page 211) for more information.
6 back to List of setpoints

#System Load Control PTM

Range [units] Baseload / Load Shar [-]
Default value Baseload Force value NO
Step [-]
Setpoint visibility Only if Active Application (page 576) = 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 275). 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 275) 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 275)) 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 277) in parallel to Mains operation and does not depend on active load control
mode.

Local Baseload

Range [units] Disable / Enable [-]
Default value Disable Force value YES
Step -
Description
This setpoint in combination with LBI LOCAL BASELOAD (PAGE 668) Enables or Disables Local Baseload
function.
BESS P request source

Step -
Description
Source type of requested local baseload.

Local Baseload

-32000 .. 32000 [kW] (depends on the selected Power Formats And Units (page
Range [units]
163))
Default value 0 kW Force value YES
Step 1 kW (depends on the selected Power Formats And Units (page 163))
Description
This setpoint is used to adjust local baseload level. The gen-set maintains this load instead of performing
proportional load sharing whenever the total load is high enough.
Load variations are then equalized by the Gen-sets with lower priority (higher number) or by Gen-sets
with Local Baseload switched off. If the setpoint is adjusted to 0 (OFF) the function is off.
#System Baseload

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

Subgroup: PF/Q Control
PF/Q Request Source

Step [-]
Description
This setpoint adjust the source type requested of PF/Q control.
Active Application (page 576) = MINT
PF/Q
#System PF Control
Request Source
PTM (page 277)
Source
Base PF #System Power Factor (page 278)
Setpoint
Base Q #System Base Q (page 279)
Analog Base PF PF CONTROL: ANEXT BASE PF (PAGE 739)
External Value Base Q Q CONTROL: ANEXT BASE Q (PAGE 739)
See PF/Q control (page 212) 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 278).
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
279).
Local Base Power Factor

Range [units] OFF / 0 .. 1.999 [-]
Default value OFF / 0 Force value YES
Step 0,001
Description
This setpoint is used to adjust local base power factor level. The BESS maintains this PF independently
on the #System Power Factor (page 278).
Power factor variations are then equalized by units with lower priority (higher number) or by Gen-sets
with Local Base Power Factor switched off. If the setpoint is adjusted to 0 (OFF) the function is off.

#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 277) = 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.
Local Base Q

OFF / -32001 .. 32000 [kVAr] (depends on the selected Power Formats And
Range [units]
Units (page 163))
OFF / -32001 kVAr (depends on
Default value the selected Power Formats And Force value YES
Units (page 163))
Step 1 kVAr (depends on the selected Power Formats And Units (page 163))
Description
This setpoint is used to adjust local base reactive power level. The BESS maintains this reactive power
independently on the #System Base Q (page 279).
Reactive power variations are then equalized by the Gen-sets with lower priority (higher number) or by
Gen-sets with Local Base Q switched off. If the setpoint is adjusted to -32001 (OFF) the function is off.

#System Base Q

-32 000 .. 32 000 [kVAr] (depends on the selected Power Formats And Units
Range [units]
(page 163))
0 kVAr (depends on the selected Power
Step 1 kVAr (depends on the selected Power Formats And Units (page 163))
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 277) = Base Q
Group: Basic settings
Subgroup: Name
Controller Name
Setpoint group Basic settings Related FW 1.0.0

Range [units] 0 .. 15 characters [-]
Default value InteliNeo 530 BESS 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]
163))
200 kVA (depends on the selected
Default value Power Formats And Units (page Force value YES
163))
Step 1 kVA (depends on the selected Power Formats And Units (page 163))
Description
Maximal apparent power of the BESS.
BESSNominal power

Range [units] 1 .. 32 000 [kW] (depends on the selected Power Formats And Units (page 163))
200 kW (depends on the selected Power
Default value Force value YES
Description
Nominal power of the BESS.
BESS protections/functions such as BESS IDMT Overload Protection (page 349) and BESS
2POverload Evaluation Level (page 329), etc are related to this setpoint.

PCS Efficiency

Range [units] 80,0 .. 100,0 %
Default value 98 % Force value YES
Step 0,1 %
Description
Efficiency of the Power Conversion System defines ratio between input and output of the PCS. The
controller regulates charging and discharging power based on measurement on the AC bus side. This
setpoints is used to prevent overloading of the Energy Storage during discharging and limiting the
charging process during charging.
Subgroup: Current settings
ES Nominal Current

Range [units] 1 .. 10000 [A]
Default value 350 A Force value YES
Step 1 [A]
Description
Current limit for PCS/ES IDMT current protection and maximal continuous current.

BESS 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
Aux CT Ratio PrimC

Range [units] 1 .. 15000 [A]
Step 1A
Description
This setpoint is used for settings of primary CT ratio of Earth Fault Current measurement.
100/5, 500/5, 1000/1

Aux CT Ratio Sec

Range [units] /1A or /5A [-]
Default value /5A Force value YES
Step [-]
Description
This setpoint is used for settings of secondary CT ratio of Earth Fault Current measurement.
100/5, 500/5, 1000/1
3Ph CT Location

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

Range [units] 1 .. 1500 [V]
Default value 231 [V] Force value YES
Step 1 [V]
Description
ES Nominal Voltage (+ to -).

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 285) is set to 3Ph4Wire / High
Setpoint visibility
Leg D / SplitPhase
Description
This setpoint defines which voltage protections are evaluated.
Example: Connection type (page 285) is 3Ph4Wire and Evaluated Voltage Protections
(page 285) 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 285) 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 285) != High Leg D or Connection type (page
Setpoint visibility
285) != MonoPhase
Description
Nominal BESS voltage (phase to neutral).
Gen Nominal Voltage Ph-Ph

Range [units] 10 .. 60000 [V]
Step 1V
Description
Nominal BESS voltage (phase to phase).

Bus Nominal Voltage Ph-N

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

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

Range [units] 0.01 .. 500.00 [V/V]
Default value 1.00 V/V Force value YES
Step 0.1 V/V
Description
This setpoint adjusts the converting ratio of the voltage meas transformer used on
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 .
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 VT Ratio

Range [units] 0.01 .. 500.00 [V/V]
Default value 1.00 V/V Force value YES
Step 0.01 V/V
Description
This setpoint adjusts the converting ratio of the voltage meas transformer used on
Note: This setpoint is applied on all three phases of 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 .
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.
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 [-]
Default value Disabled Force value YES
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 683) 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 719) is never activated
1 .. 600 [s] Timeout for LBO HORN (PAGE 719). Output opens after this time elapses
Horn Reset LBO HORN (PAGE 719) 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 573).
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 573).
Source is forced to be always INTERNAL. Controller provides Running Hours
INTERNAL
(page 573).
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.

Subgroup: Power Supply Protections
Power Supply <V
Setpoint group BESS settings Related FW 1.0.0

Range [units] 8.0 V .. Power Supply >V (page 294) [V]
Default value 18.0 V Force value NO
Step 0.1 V
Description
Warning threshold for low power supply voltage.
Power Supply >V

Range [units] Power Supply <V (page 294) .. 40.0 [V]
Default value 36.0 V Force value NO
Step 0.1 V
Description
Warning threshold for high power supply voltage.
Power Supply <> Delay

Range [units] 0 .. 600 [s]
Default value 5s Force value NO
Step 1s
Description
Delay for which power supply voltage can be out of range given by setpoints Power Supply <V (page
294) and Power Supply >V (page 294). After this delay elapses, appropriate alarm (Wrn Battery
Undervoltage (page 806) or Wrn Battery Overvoltage (page 806)) is activated.

Group: Communication Settings
Subgroup: Controller Address
Controller Address
Communication
Setpoint group Related FW 1.0.0
Settings
Range [units] 1 .. 32 [-]
Default value 1 [-] Force value NO
Step 1 [-]
Description
Controller identification number. It is possible to set controller address different from the default value (1)
so that more controllers can be interconnected (via RS485) and accessed e.g. from MODBUS terminal.
Note: When opening connection to the controller it's address has to correspond with the setting in
PC tool.
Note: This setpoint is common for CM-Ethernet, CM-GPRS and CM-4G-GPS modules.
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 241).

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 241).
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
RS485 Mode
Communication
Settings
Range [units] Direct / MODBUS [-]
Default value Direct Force value NO
Step [-]
Description
Communication protocol switch for on-board RS485.
Direct InteliConfig communication protocol via serial cable.

MODBUS MODBUS protocol.

RS485 Communication Speed
Communication
Settings
Range [units] 9600 / 19200 / 38400 / 57600 / 115200 [bps]
Step [-]
Description
If the direct mode is selected on on-board RS485, the direct communication speed of controller part of line
can be adjusted here. Speed of second part of line has to be adjusted to the same value.

Group: Ethernet
Subgroup: TCP/IP Settings
IP Address Mode
Ethernet
Ethernet
Range [units] Manual / Automatic / Disabled [-]
Default value Automatic Force value NO
Step [-]
Description
This setpoint is used to select the method how the ethernet connection is adjusted on Ethernet (page
19).
Manual: The Ethernet connection is fixed by means of the setpoints IP Address (page
299), Subnet Mask (page 299), Gateway IP (page 300), DNS IP Address 1
(page 301), DNS IP Address 2 (page 301). 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 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
Setpoint group Ethernet Related FW 1.0.0

Default value 192.168.2.254 Force value NO
Step [-]
Setpoint visibility Only if IP Address Mode (page 298) = Manual
Description
The setpoint is used to select the method how the IP Address is adjusted on Ethernet (page 19).
If IP Address Mode (page 298) = Manual, this setpoint is used to adjust the IP address of the Ethernet
(page 19) interface of the controller. Ask your IT specialist for help with this setting.
If IP Address Mode (page 298) = Automatic this setpoint is inactive. The IP address is assigned by the
DHCP server.
Note: Only valid IP address can be inserted.
Subnet Mask

Step [-]
Description
The setpoint is used to select the method how the Subnet Mask is adjusted on Ethernet (page 19).
If IP Address Mode (page 298) = Manual this setpoint is used to adjust the Subnet Mask. Ask your IT
specialist for help with this setting.
If IP Address Mode (page 298) = Automatic this setpoint is inactive. The Subnet Mask is assigned by
the DHCP server.

Gateway IP

Step [-]
Description
This setpoint is used to select the method how the Gateway IP is adjusted.
If IP Address Mode (page 298) = Manual, this setpoint is used to adjust the Gateway IP address of the
Ethernet (page 19) interface of the controller. Ask your IT specialist for help with this setting.
If IP Address Mode (page 298) = 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.
DNS Mode
Ethernet
Ethernet
Range [units] Manual / Automatic [-]
Default value Automatic Force value
Step [-]
Setpoint visibility Only if IP Address Mode (page 298) = Automatic
Description
This setpoint enables to enter DNS server addresses for Ethernet (page 19) manually, even with the IP
Address Mode (page 298) set to Automatic.
Automatic: DNS server addresses are automatically obtained from a DHCP server.
DNS IP Address 1 (page 301) and DNS IP Address 2 (page 301) 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

Step [-]
Only if IP Address Mode (page 298) = Manual OR (IP Address Mode (page 298)
Setpoint visibility
= Automatic AND DNS Mode (page 300) = Manual)
Description
This setpoint allows to set DNS IP Address 1 for Ethernet (page 19) manually.
DNS IP Address 2

Step [-]
Only if IP Address Mode (page 298) = Manual OR (IP Address Mode (page 298)
Setpoint visibility
= Automatic AND DNS Mode (page 300) = Manual)
Description
This setpoint allows to set DNS IP Address 2 for Ethernet (page 19) manually.

IP Firewall
Ethernet
Ethernet
Default value Disabled Force value NO
Step [-]
Related
Comm object 24092 MINT
applications
Description
This setpoints enables or disables the built-in Firewall (page 134) functionality for Ethernet (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: AirGate Settings
AirGate Port
EthernetCM-4G-
GPSEthernet
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.

AirGate Address
EthernetCM-4G-
GPSEthernet
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 Connection
EthernetCM-4G-
GPSEthernet
Default value Enabled Force value YES
Step [-]
Description
This setpoint enables or disables AirGate connection (page 102) function.

Subgroup: ComAp Client Settings
Direct Connection
Ethernet
Ethernet
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
Ethernet
Ethernet
Range [units] 0 .. 65535 [-]
Step 1 [-]
Description
This port is used to listen for an incoming TCP connection on Ethernet (page 19).

ComAp Client Inactivity Timeout
EthernetEthernetCM-
4G-GPSEthernet
Range [units] 0 .. 65535 [s]
Default value 60 s Force value YES
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 305).
Subgroup: Modbus Server Settings
Modbus Server
Ethernet
Ethernet
Step [-]
Description
Enables or disables Modbus communication via Ethernet (page 19).

Modbus Client Inactivity Timeout
Ethernet
Ethernet
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: SNMP Settings
SNMP Agent
EthernetCM-4G-
GPSEthernet
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

Range [units] v1 Trap / v2 Notific / v2 Inform [-]
Default value v2 Inform Force value NO
Step [-]
Setpoint visibility Only if SNMP Agent (page 306) != 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 Traps IP Address 1
Setpoint group EthernetEthernet Related FW 1.0.0

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.

Range [units] Valid IP address [-]
Step [-]
Description

SNMP RD Community String

Range [units] 0..31 characters [-]
Default value public Force value NO
Step [-]
Description
SNMP Community String only for reading.
SNMP WR Community String

Default value private Force value NO
Step [-]
Setpoint visibility Only if SNMP Agent (page 306) = SNMP v1/v2c
Description
SNMP Community String for writing and reading.
SNMP Engine User Name

Step [-]
Setpoint visibility Only if SNMP Agent (page 306) = SNMP v3
Description
Defines SNMP v3 Engine User Name.

SNMP Privacy Protocol

Range [units] DES / 3DES / AES128 / AES256 [-]
Default value AES128 Force value NO
Step [-]
Description
Selects SNMP v3 Privacy Protocol.
SNMP Authentication Protocol

Range [units] MD5 / SHA / SHA256[-]
Default value SHA Force value NO
Step [-]
Description
Selects SNMP v3 Authentication Protocol.
SNMP Security Level

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: E-mail Settings
SMTP Server Address

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) or number of port (with colon like a first mark) of the SMTP server. Ask your internet
provider or IT manager for this information.
Note: You may use also any public SMTP server which does not require connection over SSL/TLS
channels.
SMTP Sender Address

Default value [-] Force value NO
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 User Name

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

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 Encryption

Range [units] NONE / SSL/TLS / STARTTLS [-]
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.
E-mail Address 1
EthernetCM-4G-
GPSEthernet
Step [-]
Description
Enter a valid e-mail address where event and alarm messages will be sent.

E-mail Address 4
EthernetCM-4G-
GPSEthernet
Step [-]
Description
E-mail Address 3
EthernetCM-4G-
GPSEthernet
Step [-]
Description
E-mail Address 2
EthernetCM-4G-
GPSEthernet
Step [-]
Description

Subgroup: Messages Settings
E-mail/SMS Language
EthernetCM-4G-
GPSEthernet
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.
Event Message
EthernetCM-4G-
GPSEthernet
Range [units] Enabled / Disabled [-]
Step [-]
Description
This setpoint enables or disables sending of Event Messages.

Sd Message
Ethernet
Setpoint group CM-4G-GPS Related FW 1.0.0
Ethernet
Step [-]
Description
This setpoint enables or disables sending of ShutdownMains ProtectionBreaker Open + FltRes
Messages.
Stp Message
CM-4G-GPS
Ethernet
Range [units] Enabled/Disabled
Default value Enabled Force value
Step [-]
Description
This setpoint enables or disables sending of SlowStop Messages.
Wrn Message
EthernetCM-4G-
GPSEthernet
Step [-]
Description
This setpoint enables or disables sending of Warning Messages.

Subgroup: RTC Synchronization
Time Zone

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.
NTP Clock Synchronization
Ethernet
Ethernet
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
Ethernet
Ethernet
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: BESS settings
Subgroup: BESS Control

HLC Control Mode

Range [units] Disabled / U-f / U-f Const / P-Q [-]
Default value Disabled Force value
Step [-]
Description
This setpoint sets P/Q (Load and Var Sharing) control mode of the control unit. It defines stance of the
InteliNeo 530 BESS towards other ComAp controllers or High Level Controller (HLC).
Disabled: The controller is part of ComAp microgrid system and it is communicating directly with
other ComAp controllers via CAN. HLC is not used.
U-f Const: The controller is doing standard Load and Var Sharing while voltage and frequency are
regulated to their nominal. It is expected that controller is alone (there is no CAN communication
with other units) and HLC is not used.
U-f: The controller accept request from the HLC via LAIs HLC U-f Control: Q Request (page
737) and HLC U-f Control: P Request (page 737). It is not communicating with any other
ComAp controller but following the request given by LAIs (-100 .. 100 % related to the
BESSNominal power (page 280)).
P-Q: The controller is forced to do Local Baseload and Local PF/Q. P, PF, and Q request are
obtained via LAIs Load Control ANEXT: Local Baseload (page 738), Q Control: ANEXT Base
Q (page 739), and PF Control: ANEXT Base PF (page 739).
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 194

Subgroup: Energy Storage
ESCB Current Open Level
Setpoint group BESS Settings Related FW 1.0.0

Range [units] 0 .. 10 [%]
Default value 2% Force value YES
Step 1 [%]
Description
This setpoint sets limit for opening of ESCB.
ESCB Current Open Timeout

Range [units] 0 .. 3600; No Timeout [s]
Step 1 [s]
Description
This setpoint sets a time limit to open the ESCB if the current is consistently below the limit ESCB
Current Open Level (page 319).
ES Safety Charging Current
Setpoint group Source Settings Related FW 1.0.0

Range [units] 1 .. 350 [A]
Default value 1 Force value YES
Step 1A
Description
In case the communication with BMS is lost (invalid value in the LAI ES MAX CHARGING CURRENT (PAGE
736)), the discharging current will be limited by this setpoint.

ES Safety Discharging Current

Step 1A
Description
In case the communication with BMS is lost (invalid value in the LAI ES MAX DISCHARGING CURRENT
(PAGE 736)), the discharging current will be limited by this setpoint.
System Safety Discharging Level

Range [units] 0,0 .. 50,0 [%]
Default value 2,0 Force value YES
Step 0,1 %
Description
This setpoints is used as threshold for the alarm Wrn Discharging - System Safety (page 807).
Note: The percents are related to the ES Max Discharging Power (page 539).

Subgroup: SOC Control
SOC High Target

Range [units] 50 .. 100 [%] of ES Nominal Capacity (page 538)
80 % of ES Nominal
Capacity (page 538)
Step 1 % of ES Nominal Capacity (page 538)
Description
This setpoint defines the relative maximal state of charge of the BESS. The value ES SOC (page 538)
cannot exceed this limit.
See the chapter State of Charge (page 192) for more information.
SOC High Hysteresis

70 % of ES Nominal
Capacity (page 538)
Description
This setpoint defines the relative level under which the value ES SOC (page 538) must drop so the
charging process can be activated again .

SOC Low Target

20 % of ES Nominal
Capacity (page 538)
Description
This setpoint defines the relative minimal state of charge of the BESS. The value ES SOC (page 538)
cannot drop under this limit.
SOC Low Hysteresis

30 % of ES Nominal
Capacity (page 538)
Description
This setpoint defines the relative level under which the value ES SOC (page 538) must exceed so the
discharging process can be activated again .

Subgroup: Battery Cycles
Max Battery Cycles Per Day

Range [units] OFF; 1 .. 250 [-]
Step 1
Description
This setpoint is used to define the maximal daily number of battery cycles.
See the chapter BESS Charging/Discharging Control (page 191) for more information.
Subgroup: Starting Timers
Precharging TO

Step 1s
Description
Setpoint for counting down the time during which the measured voltage is expected to reach the window
given by the setpoint DC Voltage Window (page 394).

ES Ready To Load TO

Step 1s
Description
This setpoint adjusts maximal waiting time for LBI ES Ready To Load (page 654) after LBO ES RUN
REQUEST (PAGE 709) has been closed.
PCS Ready To Start TO

Step 1s
Description
This setpoint adjusts maximal waiting time for LBI ES Ready To Load (page 654) after ESCB has been
closed (if ESCB Type (page 394) = Breaker) or after LBI ES READY TO LOAD (PAGE 654) = 1 (if ESCB
Type (page 394) = Fuse/Disc.).
PCS Ready To Load TO

Step 1s
Description
This setpoint adjusts maximal waiting time for LBI PCS READY TO LOAD (PAGE 676). If the LBI PCS
READY TO LOAD (PAGE 676) is not configured the BCB is closed after this timer elapsed.

Minimal Stabilization Time

Range [units] 1 .. Maximal Stabilization Time (page 325) [s]
Default value 2s Force value YES
Step 1s
Setpoint visibility Only if Precharge Type (page 318) = 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 Precharge Type (page 318) = DC.
Maximal Stabilization Time

Range [units] Minimal Stabilization Time (page 325) .. 3600 [s]
Step 1s
Setpoint visibility Only if Precharge Type (page 318) = 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 Precharge Type (page 318) = DC.
Image 7.1 Maximal Stabilization Time

Run Only Block Delay 1

Range [units] 0.0 .. 600.0 [s]
Default value 5.0 Force value YES
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.2 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: ECU Settings
Open Param Governor Speed Adjust

Range [units] 0.000..10.000 [%]
Default value 5.000 % Force value NO
Step 0.001 %
Description
This parameter will adjust engine control characteristics to suit special requirements for stability or
transient response.
Lower values will result in smaller control gains that offer improved steady state stability but
decreased transient response.
Higher values will provide better transient response but will result in decreased steady state
stability.
Note: Nominal value of 5 provides a good balance for most applications.
Group: Protections
Subgroup: Overload Protection
BESS 2POverload Evaluation Level
Setpoint group BESS Protections Related FW 1.0.0

Range [units] 100 .. 200 [%] of BESSNominal power (page 280)
150 % of
Default value BESSNominal power Force value YES
(page 280)
Step 1 % of BESSNominal power (page 280)
Description
This setpoint adjusts the relative power level, where the thermal overload protection starts to be
evaluated. See setpoint BESS IDMT Overload Protection (page 349)for complete explanation of the
protection.
Load Reaction time

2POvrldStEvDel 5s
level [s]
OverldStrtEval 150 %
100 no reaction

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
BESS 2POverload Evaluation Delay (page 330).
Note: Maximum reaction time is 3600 s after this time the protection is tripped.
BESS 2POverload 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 BESS IDMT
Overload Protection (page 349) for complete explanation of the protection.
Load Reaction time

level [s]
100 no reaction
2POvrldStEvDel 5s
110 no reaction
OverldStrtEval 150 %
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 BESS 2POverload Evaluation Level (page 329). The higher is the load the shorter
the reaction time will be.
Subgroup: Current Protection
BESS Short Circuit

Range [units] 100 .. 500 [%] of BESS Nominal Current (page 282)
150 % of BESS Nominal Current
(page 282)
Step 1 % of BESS Nominal Current (page 282)
Description
This setpoint specifies the relative current threshold level for Short Circuit Protection (page 350).
Note: When there is no control of breakers, the type of protection is Sd instead of BOC.

BESS 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 350).
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 BESS IDMT >A Protection (page 350).
IDMT curve shape selection. IDMT Overcurrent Delay is a reaction time of IDMT protection for 200%
overcurrent IBESS =2*BESS Nominal Current (page 282)
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.5 IDMT Overcurrent Delay
BESS Current Unbalance

50 % of BESSNominal
power (page 280)
Setpoint visibility Only if Connection type (page 285) != MonoPhase
Description
This setpoint specifies the relative current threshold level for BESS Current Unbalance Protection
(page 352).
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 352).

Subgroup: Voltage Protection
BESS >V

100 .. BESS >>V (page 335) of BESS Nominal Voltage Ph-N (page 286) and
Range [units]
Gen Nominal Voltage Ph-Ph (page 286) [%]
120 % of BESS Nominal Voltage Ph-
Default value N (page 286) and Gen Nominal Force value YES
Voltage Ph-Ph (page 286)
1 % of BESS Nominal Voltage Ph-N (page 286) and Gen Nominal Voltage Ph-
Step
Ph (page 286)
Description
This setpoint specifies the relative voltage threshold level for BESS >V Protection (page 355).
Note: BESS Voltage L1-N (page 547), BESS Voltage L2-N (page 547), BESS Voltage L3-N
(page 547), BESS Voltage L1-L2 (page 547), BESS Voltage L2-L3 (page 548) and BESS
Voltage L3-L1 (page 548) 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 355).

BESS >>V

BESS >V (page 334) .. 150 [%] of BESS Nominal Voltage Ph-N (page 286) and
Range [units]
Gen Nominal Voltage Ph-Ph (page 286)
150 % of BESS Nominal Voltage Ph-N
Default value (page 286) and Gen Nominal Voltage Force value YES
Ph-Ph (page 286)
Step
Ph (page 286)
Description
This setpoint specifies the relative voltage threshold level for BESS >>V Protection (page 356).
BESS >>V Delay

Range [units] 0.01 .. 600 [s]
Step 0.01 s
Description
This setpoint specifies the delay for BESS >>V Protection (page 356).

BESS <V

20 .. 99 [%] of BESS Nominal Voltage Ph-N (page 286) and Gen Nominal
Range [units]
90 % of BESS Nominal Voltage Ph-N
Default value (page 286) and Gen Nominal Force value YES
Step
Ph (page 286)
Description
This setpoint specifies the relative voltage threshold level for BESS <<V Protection (page 357).
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 357).

BESS V Unbalance

Range [units] 1 .. 200 [%]
Step 1%
Description
This setpoint specifies the relative voltage threshold level for Voltage Unbalance Protection (page
357).
BESS V Unbalance Delay

Range [units] 0.01 .. 600.00 [s]
Step 0.01 s
Description
This setpoint specifies the delay for Voltage Unbalance Protection (page 357).

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 363).
IMPORTANT: When Active Application (page 576) = MINT this setpoint also specifies the
maximal accepted frequency for Bus >f Protection.
Note: fmax = Nominal Frequency (page 290) + 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 363).
maximal accepted frequency for Bus >f 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 364).
maximal accepted frequency for Bus <f Protection.
Note: fmin = Nominal Frequency (page 290) - 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 364).
maximal accepted frequency for Bus <f Protection.

Subgroup: Earth Fault Current Protection
IDMT Earth Fault Current Sd

Range [units] 0..10000 [A]
Default value 10 A Force value NO
Step 1A
Description
This setpoint is used as "nominal" reference for the IDMT protection upon the Earth Fault Current..
IDMT Earth Fault Current Delay

Range [units] 0..600,0 [s]
Default value 5,0 s Force value NO
Step 0,1 s
Description
This setpoint is used for delay calculating for IDMT Earth Fault Current Protection.
Group: ES Protections
ES >V
Setpoint group ES Protections Related FW 1.0.0

Range [units] 100 % .. ES >>V (page 341)
Step 1 [%]
Description
This setpoint specifies the relative voltage threshold level for ES >V Protection (page 358).
Note: ES Voltage Meas (page 538) is used for this protection.

ES >V Delay

Range [units] 0,01 .. 600,00 [s]
Default value 2,00 s Force value YES
Step 0,01 [s]
Description
This setpoint specifies the delay for ES >V Protection (page 358).
ES >>V

Range [units] ES >V (page 340) .. 150 [%]
Step 1 [%]
Description
This setpoint specifies the relative voltage threshold level for ES >>V Protection (page 359).
ES >>V Delay

Range [units] 0,01 .. 600,00 [s]
Step 0,01 [s]
Description
This setpoint specifies the delay for ES >>V Protection (page 359).

ES <V

Range [units] ES <<V (page 342) .. 99 [%]
Step 1 [%]
Description
This setpoint specifies the relative voltage threshold level for ES <V Protection (page 359).
ES < VDelay

Range [units] 0,01 .. 600,00 [s]
Step 0,01 [s]
Description
This setpoint specifies the delay for ES <V Protection (page 359).
ES <<V

Range [units] 20 .. ES <V (page 342) [%]
Step 1 [%]
Description
This setpoint specifies the relative voltage threshold level for ES <<V Protection (page 360).

ES <<V Delay

Range [units] 0,01 .. 600,00 [s]
Step 0,01 [s]
Description
This setpoint specifies the delay for ES <<V Protection (page 360).
Subgroup: SOC Protection
ES <SOC

Range [units] ES <<SOC (page 344) .. 50 [%] of ES Nominal Capacity (page 538)
Default value 10 % of ES Nominal Capacity (page 538) Force value YES
Related
applications
Description
This setpoint specifies the relative state of charge threshold level for ES <SOC (page 373).
ES >SOC

Range [units] 50 .. ES >>SOC (page 344) [%] of ES Nominal Capacity (page 538)
90 % of ES Nominal
Capacity (page 538)
Description
This setpoint specifies the relative state of charge threshold level for ES >SOC (page 373).

ES <<SOC

Range [units] 0 .. ES <SOC (page 343) [%] of ES Nominal Capacity (page 538)
Related
applications
Description
This setpoint specifies the relative state of charge threshold level for ES <<SOC (page 374).
ES >>SOC

Range [units] ES >SOC (page 343) .. 120 [%] of ES Nominal Capacity (page 538)
Related
applications
Description
This setpoint specifies the relative state of charge threshold level for ES>>SOC (page 374).
Group: Group: PCS Protections
PCS Short Circuit Level
Setpoint group PCS Protections Related FW 1.0.0

Range [units] 100 .. 500 [%]
Step 1 [%]
Description
This setpoint specifies the relative current threshold level for PCS Short Circuit Protection (page 352).

Note: PCS Current Meas (page 540) is used for this protection.
PCS Short Circuit Delay

Range [units] 0,00 .. 10,00 [s]
Step 0,01 [s]
Description
This setpoint specifies the delay for PCS Short Circuit Protection (page 352).
PCS IDMT >A Delay

Range [units] 1,0 .. 600,0 [s]
Step 0,1 [s]
Description
This setpoint adjusts the delay for PCS IDMT >A Protection (page 353).
IDMT PCS Overcurrent Delay is a reaction time of IDMT protection for 200% overcurrent IBESS =2*BESS
Nominal Current (page 282)
IDMT is “very inverse” over current protection. Reaction time is not constant but depends on over current
level according to the following formula:
IBESS is maximal value of all measured phases of BESS current.
Overcurrent
≤ 100 % 101 % 110 %
0,2 s No action 20 s 2s
Reaction time 2s No action 200 s 20 s

Table 7.2 EXAMPLE of Reaction time for different PCS Overcurrent levels
Image 7.6 IDMT PCS Overcurrent Delay

Note: PCS Current Meas (page 540) is used for this protection.
PCS >V

Range [units] 100 % .. PCS >>V (page 347)
Step 1 [%]
Description
This setpoint specifies the relative voltage threshold level for PCS >V Protection (page 360).
Note: PCS Voltage Meas (page 540) is used for this protection.
PCS >V Delay

Range [units] 0,01 .. 600,00 [s]
Step 0,01 [s]
Description
This setpoint specifies the delay for ES >V Protection (page 358).

PCS >>V

Range [units] PCS >V (page 346) .. 150 [%]
Step 1 [%]
Description
This setpoint specifies the relative voltage threshold level for PCS >>V Protection (page 361).
PCS >>V Delay

Range [units] 0,01 .. 600,00 [s]
Step 0,01 [s]
Description
This setpoint specifies the delay for ES >>V Protection (page 359).
PCS <V

Range [units] PCS <<V (page 348) .. 99 [%]
Step 1 [%]
Description
This setpoint specifies the relative voltage threshold level for PCS <V Protection (page 361).

PCS <V Delay

Range [units] 0,01 .. 600,00 [s]
Step 0,01 [s]
Description
This setpoint specifies the delay for ES <V Protection (page 359).
PCS <<V

Range [units] 20 .. PCS <V (page 347) [%]
Step 1 [%]
Description
This setpoint specifies the relative voltage threshold level for PCS <<V Protection (page 362).
PCS <<V Delay

Range [units] 0,01 .. 600,00 [s]
Step 0,01 [s]
Description
This setpoint specifies the delay for ES <<V Protection (page 360).

Group: Protections
Subgroup: Overload Protection
BESS IDMT Overload Protection
Setpoint group Protections Related FW 1.0.0

Enabled / Disabled / Protection Force Disable 1 / Protection Force Disable 2 /
Range [units]
Protection Force Disable 3 [-]
Step [-]
Description
This setpoint enables or disables BESS IDMT Overload Protection.
Behavior of protection is adjusted via setpoints BESS 2POverload Evaluation Level (page 329) and
BESS 2POverload Evaluation Delay (page 330). This protection activates alarm Sd IDMT Overload
(page 832).
The reaction time is calculated by this formula:
IMPORTANT: If this protection is disabled, the BCB cannot be closed.
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 679) / PROTECTION FORCE DISABLE 2 (PAGE 679) /
PROTECTION FORCE DISABLE 3 (PAGE 680).

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 350) and BESS Short
Circuit Delay (page 332). When value of BESS Current L1 (page 549), BESS Current L2 (page 549)
and BESS Current L3 (page 549) related to BESS Nominal Current (page 282) cross over BESS
Short Circuit (page 331) for time longer than BESS Short Circuit Delay (page 332) alarm PVBO
Short Circuit (page 833) is activated.
Setpoint options:
Enabled / Disabled : Protection is enabled / disabled.
BESS IDMT >A Protection

Range [units]
Step [-]
Description
This setpoint enables or disables BESS IDMT >A Protection.
Behavior of protection is adjusted via setpoints IDMT BESS >A Delay (page 332). This protection
activates alarm Sd IDMT BESS >A (page 832).

IBESS = Maximum (BESS Current L1 (page 549)andBESS Current L1 (page 549)
Overcurrent
≤100 % 101 % 110 %
0.2 s No action 20 s 2s
Reaction Time
2s No action 200 s 20 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
333) and BESS Current Unbalance Delay (page 333). When relative difference between BESS
currents is over setpoint BESS Current Unbalance (page 333) for time longer than BESS Current
Unbalance Delay (page 333)alarm Sd BESS Current Unbalance (page 831) is activated.
IMPORTANT: Behavior of this protection is influenced by setpoint Connection type (page
285)
Connection
type (page Compared values (maximum difference)
285)
3Ph4Wire
High Leg D
(BESS Current L1 (page 549),BESS Current L1 (page 549)
3Ph3Wire
SplitPhase
MonoPhase No protection is evaluated.
Setpoint options:
Enabled / Disabled : Protection is enabled / disabled .
PCS Short Circuit Protection

Range [units]
Protection Force Disable 3 [-][-]
Step [-]

Description
This setpoint enables or disables PCS Short Circuit Protection.
Behavior of protection is adjusted via setpoints PCS Short Circuit Level (page 344) and PCS Short
Circuit Delay (page 345). When PCS current exceeds limit set by PCS Short Circuit Level (page 344)
for time longer than PCS Short Circuit Delay (page 345) appropriate 2nd level alarm is activated.
Setpoint options:
PCS IDMT >A Protection

Range [units]
Protection Force Disable 3 [-][-]
Step [-]
Description
This setpoint enables or disables PCS IDMT >A Protection.
Behavior of protection is adjusted via setpoints PCS IDMT >A Delay (page 345). If tripped this
protection activates appropriate 2nd level alarm.
Overcurrent
≤100 % 101 % 110 %
0.2 s No action 20 s 2s
Reaction Time
2s No action 200 s 20 s
Table 7.3 EXAMPLE of Reaction time for different PCS Overcurrent levels

Image 7.7 IDMT PCS Overcurrent Delay
Setpoint options:

BESS >V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables BESS >V Protection.
Protection is enabled. Behavior of protection is adjusted via setpoints BESS >V (page 334) and BESS
>V Delay (page 334). When BESS voltage exceeds limit set by BESS >V (page 334) for time longer
than BESS >V Delay (page 334) appropriate alarm is activated.
Value Alarm
BESS Voltage L1-N (page 547) Sd BESS >V L1-N (page 827)
BESS Voltage L1-L2 (page 547) Sd BESS >V L1-L2 (page 827)
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 335) and BESS >>V Delay (page
335). When BESS voltage exceeds limit set by BESS >>V (page 335) for time longer than BESS >>V
Delay (page 335) appropriate alarm is activated.
Value Alarm
BESS Voltage L1-N (page 547) Sd BESS >>V L1-N (page 825)
BESS Voltage L2-N (page 547) Sd Bus >>V L2-N (page 825)
BESS Voltage L3-N (page 547) Sd BESS >>V L3-N (page 826)
BESS Voltage L1-L2 (page 547) WRN BESS >>V L1-L2 (page 826)
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 336) and BESS <V Delay (page 336)
When BESS voltage drops below limit set by BESS <V (page 336) for time longer than BESS <V Delay
(page 336) appropriate alarm is activated.
Value Alarm
BESS Voltage L1-N (page 547) Sd BESS <V L1-N (page 828)
BESS Voltage L1-L2 (page 547) Sd BESS <V L1-L2 (page 829)
BESS Voltage L2-L3 (page 548) Sd BESS <V L2-L3 (page 829)
Setpoint options:
Voltage Unbalance Protection

Range [units]
Step [-]
Description

This setpoint enables or disables Voltage Unbalance Protection.
Behavior of protection is adjusted via setpoints BESS V Unbalance (page 337) and BESS V
Unbalance Delay (page 337). When relative difference between BESS voltages is over setpoint BESS
V Unbalance (page 337) for time longer than BESS V Unbalance Delay (page 337) alarm Sd BESS V
Unbalance Ph-N (page 830) or Sd BESS V Unbalance Ph-Ph (page 831) is activated.
IMPORTANT: Behavior of this protection is influenced by setpoint Connection type (page
285)
Connection
type (page Compared values (maximum difference)
285)
BESS Voltage L1-N (page 547), BESS Voltage L2-N (page 547) and BESS
Voltage L3-N (page 547)
3Ph4Wire OR
BESS Voltage L1-L2 (page 547), BESS Voltage L2-L3 (page 548) and
BESS Voltage L3-L1 (page 548)
High Leg D
3Ph3Wire
BESS Voltage L1-N (page 547), BESS Voltage L2-N (page 547) and BESS
SplitPhase
Voltage L3-N (page 547)
MonoPhase No protection is evaluated.
Setpoint options:
ES >V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables ES >V Protection.

Behavior of protection is adjusted via setpoints ES >V (page 340) and ES >V Delay (page 341). When
ES voltage exceeds limit set by ES >V (page 340) for time longer than ES >V Delay (page 341)
appropriate 1st level alarm is activated.
Setpoint options:
ES >>V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables ES >>V Protection.
Behavior of protection is adjusted via setpoints ES >>V (page 341) and ES >>V Delay (page 341).
When ES voltage exceeds limit set by ES >>V (page 341) for time longer than ES >>V Delay (page
341) appropriate 2nd level alarm is activated.
Setpoint options:
ES <V Protection

Range [units]
Step [-]
Description

This setpoint enables or disables ES <V Protection.
Behavior of protection is adjusted via setpoints ES <V (page 342) and ES < VDelay (page 342). When
ES voltage exceeds limit set by ES <V (page 342) for time longer than ES < VDelay (page 342)
appropriate 1st level alarm is activated.
Setpoint options:
ES <<V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables ES <<V Protection.
Behavior of protection is adjusted via setpoints ES <<V (page 342) and ES <<V (page 342). When ES
voltage exceeds limit set by ES <<V (page 342) for time longer than ES < VDelay (page 342)
appropriate 2nd level alarm is activated.
Setpoint options:
PCS >V Protection

Range [units]
Step [-]

Description
This setpoint enables or disables PCS >V Protection.
Behavior of protection is adjusted via setpoints PCS >V (page 346) and PCS >V Delay (page 346).
When PCS voltage exceeds limit set by PCS >V (page 346) for time longer than PCS >V Delay (page
346) appropriate 1st level alarm is activated.
Setpoint options:
PCS >>V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables PCS >>V Protection.
Behavior of protection is adjusted via setpoints PCS >>V (page 347) and PCS >>V Delay (page 347).
When PCS voltage exceeds limit set by PCS >>V (page 347) for time longer than PCS >>V Delay
(page 347) appropriate 2nd level alarm is activated.
Setpoint options:
PCS <V Protection

Range [units]
Step [-]

Description
This setpoint enables or disables PCS <V Protection.
Behavior of protection is adjusted via setpoints PCS <V (page 347) and PCS <V Delay (page 348).
When PCS voltage exceeds limit set by PCS <V (page 347) for time longer than PCS <V Delay (page
348) appropriate 1st level alarm is activated.
Setpoint options:
PCS <<V Protection

Range [units]
Step [-]
Description
This setpoint enables or disables PCS <<V Protection.
Behavior of protection is adjusted via setpoints PCS <<V (page 348) and PCS <<V Delay (page 348).
When PCS voltage exceeds limit set by PCS <<V (page 348) for time longer than PCS <<V Delay
(page 348) appropriate 2nd level alarm is activated.
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 338) and BESS >f Delay (page 338).
When BESS Frequency (page 547) exceeds maximal accepted frequency for period longer than BESS
>f Delay (page 338) alarm Sd BESS >f (page 830) is activated.
Note: fmax = Nominal Frequency (page 290) + BESS >f (page 338)
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 339) and BESS <f Delay (page 339).
When BESS Frequency (page 547) drops below minimal accepted frequency for period longer than
BESS <f Delay (page 339) alarm Sd BESS <f (page 830) is activated.
Note: fmin = Nominal Frequency (page 290) + BESS <f (page 339)
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 835) is activated if controller detects a mismatch between the
expected and currently measured voltage on the bus for period longer than 20 s.
Setpoint options:
Subgroup: Phase Rotation Protection
Phase Rotation Protection

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

Subgroup: Earth Fault Current Protection

IDMT Earth Fault Current Protection

Range [units]
Step [-]
Description
This setpoint enables or disables Earth Fault Current Protection.
Bbehavior is adjusted via setpoints Earth Fault Current Sd (page 530) and Earth Fault Delay (page
529). When the protection is triggered the alarm Sd IDMT Earth Fault Current (page 831) is activated.
Igen = Maximum (BESS Current L1 (page 549), BESS Current L2 (page 549), BESS Current L3
(page 549))
Example:
Earth Fault Current Sd (page 530) = 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
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 setpoint Vector Shift Limit (page 428). When measured vector
shift on Bus Voltage L1-N (page 552) is over the Vector Shift Limit (page 428), breaker is opened and
history record Vector Shift is written to the history.
Enabled Protection is always active while MCB is closed.

Parallel Only Protection is active only if Breaker state (page 577) = ParalOper.
Disabled Protection is disabled.

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 428) ROCOF1 df/dt
(page 429).
When measured ROCOF1 (page 555) on Bus Frequency (page 552) is over ROCOF1 df/dt (page 429)
in respective period given by ROCOF1 Windows Length (page 428), breaker is opened and history
record ROCOF is written to the history. Maximal ROCOF is stored in Max ROCOF1 (page 555) which is
reset every time when the breaker is closed again.


ROCOF2 Protection

Step [-]
Description
(page 430).
When measured ROCOF2 (page 555) on Bus Frequency (page 552) is over ROCOF2 df/dt (page
430) in respective time given by ROCOF2 Windows Length (page 429), breaker is opened and history


ROCOF3 Protection

Step [-]
Description
(page 431).


ROCOF4 Protection

Step [-]
Description
(page 432).


Subgroup: SOC Protection
ES <SOC

Range [units]
Step [-]
Description
This setpoint enables or disables BESS <SOC Protection. When ES SOC (page 538) exceeds limit set
by the setpoint ES <SOC (page 343) the alarm Wrn SOC Low Alarm (page 812).
Setpoint options:
ES >SOC

Range [units]
Step [-]
Description
This setpoint enables or disables BESS >SOC Protection. When ES SOC (page 538) exceeds limit set
by the setpoint ES >SOC (page 343) the alarm Wrn SOC High Alarm (page 812).
Setpoint options:

ES <<SOC

Range [units]
Step [-]
Description
This setpoint enables or disables BESS <<SOC Protection. When ES SOC (page 538) exceeds limit set
by the setpoint ES <<SOC (page 344) the alarm Sd SOC Critical Low (page 834).
Setpoint options:
ES>>SOC

Range [units]
Step [-]
Description
This setpoint enables or disables BESS >>SOC Protection. When ES SOC (page 538) exceeds limit set
by the setpoint ES >>SOC (page 344) the alarm Sd SOC Critical High (page 834).
Setpoint options:

Group: SpeedFrequency/Load Control
Subgroup: SpeedFrequency Control
Frequency Reg Character
Setpoint group Speed/Load Control Related FW 1.0.0

Range [units] Positive / Negative [-]
Default value Positive Force value YES
Step [-]
Description
This setpoint selects the characteristic of the Frequency Regulator Output (page 562). 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

Range [units] Frequency Gov Low Limit (page 376) .. Frequency Gov Hi Lim (page 376) [-]
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 562). This level
is present on the output, if no speed or power regulation loop is active.

Frequency Gov Low Limit

Range [units] -10,00 .. Frequency Gov Hi Lim (page 376) [V]
Default value -10,00 V Force value YES
Step 0,01 V
Description
The low limit of the Frequency Regulator Output (page 562).
Use this setpoint to adjust the regulator output range according to your BESS inverter regulator.
Frequency Gov Hi Lim

Range [units] Frequency Gov Low Limit (page 376) .. 10,00 [V]
Step 0,01 V
Description
Upper limit of the speed Frequency Regulator Output (page 562).
Use this setpoint to adjust the regulator output range according to your BESS inverter regulator.
Frequency Governor PWM Rate
Frequency/Load
Control
Range [units] 500..2900 [Hz]
Default value 500 Hz Force value NO
Step 1 Hz
Description
This setpoint adjusts the frequency of the speed governor PWM output.

Tau Frequency Gov 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 562)
to the pulses at the binary outputs FREQUENCY UP (PAGE 718) and FREQUENCY DOWN (PAGE 718).
Adjust the setpoint to the pulse duration which is needed for the regulator of BESS inverter to
regulatefrom minimal position to the maximal position.
PCS Frequency Droop Slope
Frequency/Load
Control
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 290)) on the range of the
requested power from 0 to 100% of BESSNominal power (page 280).

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 290).
Note: See the chapter Regulation Loops (page 233) for more information.
Frequency Gain

Range [units]
Step
Description
This setpoint adjusts the gain factor (P-factor) of the frequency control PI loop.

Frequency Int

Range [units]
Step
Description
This setpoint adjusts the integration factor (I-factor) of the frequency control PI loop.
Angle Gain

Range [units]
Step
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]
Step
Description
This setpoint adjusts the gain factor (P-factor) of the load control PI loop.
Load Int

Range [units]
Step
Description
This setpoint adjusts the integration factor (I-factor) of the load control PI loop.

Load Sharing Gain

Range [units]
Step
Description
This setpoint adjusts the gain factor (P-factor) of the load sharing control PI loop.
Load Sharing Int

Range [units]
Step
Description
This setpoint adjusts the integration factor (I-factor) of the load sharing control PI loop.

Subgroup: Load Transfer
Generator Unload BCB Open Level

10 % of BESSNominal power (page
280)
Description
This setpoint adjusts the required value of the BESS P (page 541) related to BESSNominal power
(page 280) 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.
Load Ramp

Step 1s
Description
This setpoint adjusts the ramping time of BESS Required P (page 562) to BESS Required P Target
(page 562) while loading/unloading.
The ramping time is set for ΔP which is given by the setpoint BESSNominal power (page 280).

Ramp Start Level

0 % of BESSNominal power
(page 280)
Description
This setpoint adjusts the load level at which the Load Ramp (page 382) 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 562) to the BESS Required P
Target (page 562) 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 BESSNominal power (page 280) if the Installed Power is OFF.
Note: This setpoint is shared with Soft Unload Ramp (page 434)

Group: Voltage/PF Control
Subgroup: Voltage Control
Voltage Regulator Character
Setpoint group Voltage/PF Control Related FW 1.0.0

Range [units] Positive / Negative [-]
Default value Positive Force value YES
Step [-]
Description
This setpoint selects the characteristic of the Voltage Regulator Output (page 564). 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 385) .. Voltage Regulator High Limit (page
Range [units]
385) [V]
Step 0,01 V
Description
This setpoint adjusts the initial level for the Voltage Regulator Output (page 564). 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 385) [V]
Default value -10,00 V Force value YES
Step 0,01 V
Description
Lower limit of the Voltage Regulator Output (page 564). Use this setpoint to adjust the governor output
range according to your governor type.
Voltage Regulator High Limit
Setpoint group AC Synchronization Related FW 1.0.0

Range [units] Voltage Regulator Low Limit (page 385) .. 10,00 [V]
Step 0,01 V
Description
Upper limit of the Voltage Regulator Output (page 564). 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 564) to
the pulsesat the binary outputs AVRVOLTAGE UP (PAGE 730) and AVRVOLTAGE DOWN (PAGE 730).
Adjust the setpoint to the pulse duration which is needed for the regulator of BESS inverter to
regulatefrom minimal position to the maximal position.
PCS Voltage Droop Slope
Frequency/Load
Control
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 BESS nominal voltage (BESS Nominal Voltage Ph-N (page 286)) 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 Gen Nominal Voltage Ph-Ph (page 286) whilst
the PF=0,8).

Subgroup: Regulation Loops
Voltage Gain

Range [units]
Step
Description
This setpoint adjusts the gain factor (P-factor) of the voltage control PI loop.
Voltage Int

Range [units]
Step
Description
This setpoint adjusts the integration factor (I-factor) of the voltage control PI loop.

PF Gain
Voltage/PF Control
PF Control
Range [units]
Step
Description
This setpoint adjusts the gain factor (P-factor) of the PF control PI loop.
PF Int
Voltage/PF Control
PF Control
Range [units]
Step
Description
This setpoint adjusts the integration factor (I-factor) of the PF control PI loop.

VAr Sharing Gain

Range [units]
Step
Description
This setpoint adjusts the gain factor (P-factor) of the VAr sharing control PI loop.
VAr Sharing Int

Range [units]
Step
Description
This setpoint adjusts the integration factor (I-factor) of the VAr sharing control PI loop.

Group: AC Synchronization
Subgroup: AC Synchronization
Synchronization Type

Range [units] PhaseMatch / SlipSynchr [-]
Default value PhaseMatch Force value YES
Step [-]
Description
This setpoint adjusts the type of Synchronization (page 201).
PhaseMatch
This type of synchronization is based on voltage and phase shift match. Limits are adjusted via
setpoints Voltage Window (page 391) and Phase Window (page 392). When voltage and phase
shift match the breaker close command is sent after Dwell Time (page 392) is elapsed.
SlipSynchr
This type of synchronization regulates the voltage to match Voltage Window (page 391) and BESS
Frequency (page 547) to match theBus Frequency (page 552) +Slip Frequency (page 393).
When this frequency is reached, Dwell Time (page 392) 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 393) / .
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 201).
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 Bus and BESS
for Synchronization (page 201). (BESS Voltage L1-N (page 547), Bus Voltage L1-N (page 552),
BESS Voltage L2-N (page 547),Bus Voltage L2-N (page 552), …)
BESS to Bus Phase Shift

Range [units] -120 .. 120 [°]
Default value 0° Force value YES
Step 1°
Comm object 9578 Related applications
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 390) = PhaseMatch
Description
This setpoint adjusts the maximal Slip Angle (page 551) for Synchronization (page 201).
In order to disable breaker close command, adjust this setpoint to 0. Synchronization procedure will be
active for Synchronization Timeout (page 391) 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 392) and
voltage difference within Voltage Window (page 391) 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 390) = SlipSynchr
Description
This setpoint adjusts the required BESS Frequency (page 547) during synchronization while
Synchronization Type (page 390) = SlipSynchr.
Note: Required BESS Frequency (page 547) = Bus Frequency (page 552) + 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 390) = 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 390) has SlipSynchro
value. Synchronization Type (page 390) setting value of this setpoint.

Subgroup: DC Synchronization
DC Voltage Window

Range [units] 0,0 .. 100,0 [%]
Default value 1 [%] Force value YES
Step 0,1 [%]
Description
This setpoint adjusts the maximal DC Voltage difference between respective DC phases of PCS and ES
for DC Synchronization (page 201) via ESCB.
This setpoint adjusts the maximal DC Voltage difference between DC Bus Left Converter Voltage and
DC Bus Right Converter Voltage for DC synchronization via BTB breaker.
Subgroup: Breaker Control
ESCB Type
Setpoint group Synchronization Related FW 1.0.0

Range [units] Fuse/Disc. / Breaker [-]
Default value Breaker Force value YES
Step [-]
Description
This setpoint is set according to the type of ESCB breaker used.
Fuse/Disc type
The ESCB is not breaker but Fuse or Manual Disconnector. ESCB is only monitored by the controller
and is expected to be closed all the time (LBI PVCB Feedback = 1). When LBI PVCB Feedback = 0
then Alarm Sd ESCB Fail is activated.
Breaker type
The ESCB breaker is controlled by controller.
BCB Control Mode

Range [units] Internal / Follow / External [-]
Default value Internal Force value YES

Step [-]
Description
This setpoint adjusts control mode of BCB.
The breaker is controlled only from controller. Any unexpected change of BCB
FEEDBACK (PAGE 648) causes Stp BCB Fail (page 835) immediately.
Internal
Incorrect reaction of the BCB FEEDBACK (PAGE 648) on internal BCB
Close/Open command causes Stp BCB Fail (page 835)
BCB Openning BCB FEEDBACK (PAGE 648) = 0 is accepted from external
devices with history record "BCB Opened Externally".
Follow
Incorrect reaction of the BCB FEEDBACK (PAGE 648) to internal BCB
Close/Open command causes Stp BCB Fail (page 835)
Controller does not control the BCB is controlled externally, when the BCB
FEEDBACK (PAGE 648) get changed, then the event "BCB Opened" or "BCB
Closed" is recorded to the history log.
Controller always accept the BCB FEEDBACK (PAGE 648) 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.
Attempts To Close Breaker

Step 1 [-]
Description
This setpoint adjusts the amount of attempts the controller performs when a breaker is requested to be
closed.
Example: If the breaker feedback is not received at the end of the attempt, an alarm is not issued,
unless it was the last attempt to close the breaker.

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.
Waiting For Breaker Feedback

Range [units] 1 .. Delay Between Closing Attempts (page 396) [s]
Step 1 [-]
Description
This setpoint adjusts the length of breaker closing attempt.
Example: When set to 10s, the LBO BCB ON COIL (PAGE 698) is set for 10 s.

#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 724) which is used for
neutral contactor control.
See more information in the chapter Neutral Contactor Breaker (page 112).
The EACH option should be used if each Gen-set and BESS has its own neutral contactor. The
NCB CLOSE/OPEN (PAGE 724) 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 724) 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 673) and LBO NCB CLOSE/OPEN (PAGE 724) has to be configured
for proper functionality.
Note: This setpoint is available only for the MINT application, in case of the SPTM application the
NCB automatically behaves like this setpoint is set to COMMON option.

Group: Power Management
Subgroup: Power Management Control
Power Management
Setpoint group Power Management Related FW 1.0.0

Step [-]
Description
This setpoint is used to enable or disable the Power Management (page 213) function in this particular
controller.
Disabled - Function is disabled. BESS is Started/Stopped only via LBI REMOTE START/STOP
(PAGE 683).
Enabled - Function is enabled. Starting/Stopping of BESS is affected by Power Management
(page 213) requirements.
IMPORTANT: Controller Mode (page 290) = AUTO, otherwise BESS is not controlled with
Power Management (page 213) 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

Default value 0s Force value YES
Step 1s
Description
Setpoint defines delay of the Power Management (page 213). When REMOTE START/STOP (PAGE 683)
signal is activated the Gen-sets are started. All Gen-sets (where Power Management (page 398) 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 683) 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 213) function mode.
The Power Management (page 213) is based on Actual Active Power In

ABS [kW]
PM (page 560) and BESSNominal power (page 280) of each unit.
Power Management mode which has been set via CAN2 (page 19)
N/A Mode (Communication peripherals (page 19)) is not supported in this controller.
Alarm Wrn Unsupported PMS Mode (page 813) is active.
The Power Management (page 213) is based on relative load, i.e. ratio of
REL [%] Actual Active Power In PM (page 560) to BESSNominal power (page
280).
IMPORTANT: This setpoint is shared via and/or . Change of this setpoint will be reflected in all
controllers.

Priority

Default value 1 [-] Force value YES
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 686) 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 213) function.
Optimization is disabled. Priorities are given directly by the values adjusted in

Disabled
the setpoint Priority (page 401).
This method changes the BESS Priority (page 557) (not the setpoint
Priority (page 401)) 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 425).
Power Management mode, which has been set via CAN2 (page 19)
N/A Mode
(Communication peripherals (page 19)), is not supported in this controller.
This method changes the BESS Priority (page 557) (not the setpoint
Priority (page 401)) to optimize which units are running according to their
Efficient BESSNominal power (page 280), 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 686) can be used only if #Priority Auto Swap =
Disabled.
controllers.

#System Start Delay

Step 1s
Description
This setpoint adjusts the delay of the system activation after the LBI REMOTE START/STOP (PAGE 683)
has been activated.
Note: System Start Delay countdown is changed to 1 second for parallel operation (Bus is in parallel
with Mains).
controllers.
#System Stop Delay

Step 1s
Description
This setpoint adjusts the delay of the system deactivation after the LBI REMOTE START/STOP (PAGE 683)
has been deactivated.
Note: System Stop Delay countdown is changed to 1 second for parallel operation (Bus is in parallel
with Mains).
controllers.


Step [-]
Description
This setpoint is used to enable/disable use of the Dynamic Spinning Reserve (page 216) functionality
in power management.
Note: If enabled option is selected the InteliNeo 530 BESS 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.

Subgroup: Load Reserve Set 1
#Starting Load Reserve 1

0 .. #Stopping Load Reserve 1 (page 406) [kW] (depends on the selected Power
Range [units]
60 kW (depends on the selected
Default value Power Formats And Units (page Force value NO
163))
Setpoint visibility Only if #Power Management Mode (page 400) = ABS [kW]
Description
This setpoint adjusts required minimal Actual Reserve (page 558) for Power Management (page 213)
function.
If Load Reserve Set 1 is activated and Actual Reserve (page 558) drops bellow this limit, next
Controller will be started.
The currently active reserve set is selected by binary inputs LOAD RES 2 ACTIVE (PAGE 666), LOAD RES 3
ACTIVE (PAGE 667) and LOAD RES 4 ACTIVE (PAGE 668). 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 408), #Starting Load Reserve 3 (page 412) or #Starting Load Reserve 4 (page
416) 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).
controllers.

#Stopping Load Reserve 1

#Starting Load Reserve 1 (page 405) .. 32000 [kW] (depends on the selected
Range [units]
Power Formats And Units (page 163))
Description
This setpoint adjusts required maximal Actual Reserve (page 558) for Power Management (page
213) function.
If Load Reserve Set 1 is activated and Actual Reserve (page 558) rises over this limit, next Controller
will be stopped.
Note: The reserve for stop must be always adjusted higher than the reserve for start.
controllers.

#Starting Rel Load Reserve 1

Range [units] 0 .. #Stopping Load Reserve 1 (page 406) [%]
Default value 60 % Force value NO
Step 1%
Setpoint visibility Only if #Power Management Mode (page 400) = REL [%]
Description
This setpoint adjusts required minimal Actual Relative Reserve (page 559) for Power Management
(page 213) function.
If Load Reserve Set 1 is activated and Actual Relative Reserve (page 559) drops below this limit, next
controllers.
#Stopping Rel Load Reserve 1

Range [units] #Starting Rel Load Reserve 1 (page 407) .. 110 [%]
Step 1%
Description
This setpoint adjusts required maximal Actual Relative Reserve (page 559) for Power Management
If Load Reserve Set 1 is activated and Actual Relative Reserve (page 559) rises over this limit, next
Controller will be stopped.
controllers.


Range [units]
163))
Description
function.
The currently active reserve set is selected by binary inputs LOAD RES 2 ACTIVE (PAGE 666)Load Res 2
Active, LOAD RES 3 ACTIVE (PAGE 667)Load Res 3 Active and LOAD RES 4 ACTIVE (PAGE 668)Load Res
4 Active in any other controller on CAN. 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 408), #Starting Load Reserve 3 (page 412) or #Starting Load Reserve 4 (page
416) 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).
controllers.


Range [units]
Description
213) function.
will be stopped.
selected.
controllers.


Range [units] 0 .. #Stopping Rel Load Reserve 2 (page 411) [%]
Step 1%
Description
selected.
controllers.


Step 1%
Description
selected.
controllers.


Range [units]
163))
Description
function.
selected.
controllers.


Range [units]
Description
213) function.
will be stopped.
selected.
controllers.


Step 1%
Description
selected.
controllers.


Step 1%
Description
selected.
controllers.


Range [units]
163))
Description
function.
controllers.


Range [units]
163))
Description
213) function.
will be stopped.
controllers.


Step 1%
Description
controllers.

Step 1%
Description
controllers.

Subgroup: Minimal Running Power
#Min Run Power 1

Range [units] 0 .. 65000 [kW] (depends on the selected Power Formats And Units (page 163))
Description
This setpoint adjusts required Minimal Running Nominal Power (page 561) 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
672).
controllers.
#Min Run Power 2

Description
672).
controllers.

#Min Run Power 3

Description
673).
controllers.
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 558) /
Actual Relative Reserve (page 559) drops bellow Starting Load Reserve of currently active Load
Reserve Set.
controllers.

#Next Engine Stop Delay

Step 1s
Description
This setpoint adjusts the delay before next Controller is stopped after Actual Reserve (page 558) /
Actual Relative Reserve (page 559) rises over Stopping Load Reserve of currently active Load
Reserve Set.
controllers.
#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.
controllers.

Subgroup: Slow Stop Protection
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
423) right after the delay #Overload Next Start Delay (page 424). #Overload Next Start Protection
requires Starting Load Reserve condition to be fulfilled in order to be used.

Protection is enabled. If Actual Active Power In PM (page 560) of PM
Controllers related to Running Nominal Power In PM (page 560) is over
Enabled
#Overload Next Start Level (page 423), another Controller is started after
#Overload Next Start Delay (page 424).
controllers.
#Overload Next Start Level

Range [units] 0 .. 100 [%] of Running Nominal Power In PM (page 560)
80 % of Running Nominal Power In
PM (page 560)
Step 1 % of Running Nominal Power In PM (page 560)
Setpoint visibility Only if #Overload Next Start Protection (page 423) = Enabled
Description
This setpoint adjusts the minimal load for #Overload Next Start Protection (page 423).
controllers.

#Overload Next Start Delay

Step 1s
Setpoint visibility Only if #Overload Next Start Protection (page 423) = Enabled
Description
This setpoint adjusts the delay for #Overload Next Start Protection (page 423).
controllers.
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 573).
RH = Running Hours (page 573) -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 573) of Controllers in
Power Management (page 213) function if #Priority Auto Swap (page 402).
If the difference between Running Hours (page 573) is over this limit, priorities are swapped.
controllers.
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 402) = Efficient.
controllers.

#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 402) = Efficient.
controllers.
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 116).

Group Link L

Step 1 [-]
Description
If the input GROUP LINK (PAGE 663) 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
116)). 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 663) 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
116)). 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 368) is not Disabled
Description
This setpoint adjusts the threshold level for the Vector Shift Protection (page 368).
Note: To adjust this setpoint properly, check the value Max Vector Shift (page 554). 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 369) is not Disabled
Description
This setpoint adjusts the time averaging level for the ROCOF1 Protection (page 369).
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 369).
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
Group: Grid Codes
Subgroup: Dynamic Support
Post VRT Priority
Setpoint group Grid Codes Related FW 1.0.0

Range [units] 0 .. 254; OFF [-]
Step 1 [-]
Description
This setpoint adjusts priority of Post VRT Ramp (page 433) which is used while LBO EVENT POST VRT
(PAGE 715) is closed.

Post VRT Ramp

Step 1s
Setpoint visibility Always.
Description
This setpoint adjusts ramping time of BESS Required P (page 562) to BESS Required P Target (page
562) if LBO EVENT POST VRT (PAGE 715) is closed.
The ramping time is set for ΔP which is given by the setpoint BESSNominal power (page 280) if the
Installed Power is OFF.
Priority of this ramp is given by Post VRT Priority (page 432).
Subgroup: Soft Unload
Soft Unload Priority

Range [units] 0 .. 254; OFF [-]
Step 1 [-]
Description
This setpoint adjusts priority of Soft Unload Ramp (page 434) which is used while LBO EVENT SOFT
UNLOAD (PAGE 715) is closed.
Note: Smaller number means higher priority, e.i. 0 has highest priority.

Soft Unload Ramp

Step 1s
Description
This setpoint adjusts the ramping time of the BESS Required P (page 562) to the BESS Required P
Target (page 562) 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 BESSNominal power (page 280) if the Installed Power is OFF.
Note: This setpoint is shared with Soft Unload Ramp (page 383)

Group: Load Shedding
Subgroup: Load Shedding
Load Shedding Active
Setpoint group Load Shedding Related FW 1.0.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 142) function.
Disabled – Function is disabled.
Island only – Function is active when Breaker state (page 577) = IslOper or Breaker state
(page 577) = MultIslOp.
Load shedding outputs (page 142) are closed/opened one by one in island operations
All Load shedding outputs (page 142) 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 577) is changed from ParalOper/MultParOp to
IslOper/MultIslOp .
Load shedding outputs (page 142) are closed/opened one by one in island operations
All Load shedding outputs (page 142) 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 142) 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 577).
All Load shedding outputs (page 142) are never tripped at once when BCB is closed into
parallel operation.
All Load shedding outputs (page 142) are tripped at once when BCB is closed into island
operation.

Load Shedding Level

Load Reconnection Level (page 437) .. 200 [%] of BESSNominal power (page
Range [units]
280)
80 % of BESSNominal power (page
280)
Step 1 % of or BESSNominal power (page 280)
Setpoint visibility Only if Load Shedding Active (page 435) is not Disabled
Description
This setpoint adjusts decisive level for load disconnection during Load Shedding (page 142) 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 142)
function.

Load Reconnection Level

20 % of BESSNominal power
(page 280)
Description
This setpoint adjusts the decisive level between load reconnection during Load Shedding (page 142)
function.
Load Reconnection Delay

Range [units] 0..600 [s]
Step 1s
Description
This setpoint adjusts the delay between load reconnection during Load Shedding (page 142) function.

Auto Load Reconnection

Step [-]
Description
This setpoint enables/disables Automatic Load Shedding (page 142).
Rising edge of LBI MANUAL LOAD RECONNECTION (PAGE 669) lowers the load
Disabled reduction stage by one while BESS P (page 541) drops under Load
Reconnection Level (page 437).
Load reduction stage is lowered by one when BESS P (page 541) drops under
Enabled Load Reconnection Level (page 437) and period of Load Reconnection Delay
(page 437) elapsed from last load reduction stage lowering.
Group: User Buttons
Subgroup: User Buttons
User Button 1
Setpoint group User Buttons Related FW 1.0.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 179).
COMMAND User Button 1 is controlled by command from External display (page 65).
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 65).

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
Group: Analog Switches
Subgroup: Analog Switch 1
AIN Switch01 On
Setpoint group Analog Switches Related FW 1.0.0

Range [units] 0..32 000 [-]
Default value 0 Force value
Step 1
Setpoint visibility Visible only if the logical analog input AIN Switch01 is configured
Description
Threshold level for switching the binary output AIN Switch01 on. The value is measured from AIN
Switch01 analog input.

AIN Switch01 Off

Range [units] 0..32 000 [-]
Step 1
Description
Threshold level for switching the binary output AIN Switch01 off. The value is measured from AIN
AIN Switch02 On

Range [units] 0..32 000 [-]
Step 1
Description
AIN Switch02 Off

Range [units] 0..32 000 [-]
Step 1
Description

AIN Switch03 On

Range [units] 0..32 000 [-]
Step 1
Description
AIN Switch03 Off

Range [units] 0..32 000 [-]
Step 1
Description

AIN Switch04 On

Range [units] 0..32 000 [-]
Step 1
Description
AIN Switch04 Off

Range [units] 0..32 000 [-]
Step 1
Description

AIN Switch05 On

Range [units] 0..32 000 [-]
Step 1
Description
AIN Switch05 Off

Range [units] 0..32 000 [-]
Step 1
Description

AIN Switch06 On

Range [units] 0..32 000 [-]
Step 1
Description
AIN Switch06 Off

Range [units] 0..32 000 [-]
Step 1
Description

AIN Switch07 On

Range [units] 0..32 000 [-]
Step 1
Description
AIN Switch07 Off

Range [units] 0..32 000 [-]
Step 1
Description

AIN Switch08 On

Range [units] 0..32 000 [-]
Step 1
Description
AIN Switch08 Off

Range [units] 0..32 000 [-]
Step 1
Description

AIN Switch09 On

Range [units] 0..32 000 [-]
Step 1
Description
AIN Switch09 Off

Range [units] 0..32 000 [-]
Step 1
Description

AIN Switch10 On

Range [units] 0..32 000 [-]
Step 1
Description
AIN Switch10 Off

Range [units] 0..32 000 [-]
Step 1
Description

Group: Scheduler
Subgroup: Time & Date
Time
Setpoint group Scheduler Related FW 1.0.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 458).
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 457) 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.
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 458) = 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 459) 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 458) = 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 459) are calculated values in function Sunrise/Sunset.

Subgroup: Timer 1
Timer 1 Function

Disabled / Manual On / No Func / Mode OFF / Rem Start/Stop / TEST / Test OnLd /
Range [units]
MFail Blk [-]
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 461).
Once the Timer is activated the LBO EXERCISE TIMER 1 (PAGE 715) 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.
Rem The binary output of the Timer is internally connected to the binary input Remote
Start/Stop Start/Stop.
TEST The binary output of the Timer is internally connected to the binary input Remote
TEST.
TEST OnLd The binary output of the Timer is internally connected to the Remote TEST On
Load binary input.
MFail Blk The binary output of the Timer is internally connected to theMains Fail Block
binary input.

Timer 1 Setup

Default value N/A [-] Force value NO
Step N/A [-]
Setpoint visibility Only if Timer 1 Function (page 460) is not Disabled or Manual On
Description
Use this setpoint to setup the exercise Timer 1. See Exercise Timers (page 127) for step by step
manual.

Subgroup: Timer 2
Timer 2 Function

Range [units]
MFail Blk [-]
Default value Disabled [-] Force value YES
Step [-]
Description

purposes).
input.
TEST.
Load binary input.
MFail Blk The binary output of the Timer is internally connected to the Mains Fail Block
binary input.

Timer 2 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 3
Timer 3 Function

Range [units]
MFail Blk [-]
Step [-]
Description

purposes).
input.
TEST.
Load binary input.
binary input.

Timer 3 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 4
Timer 4 Function

Range [units]
MFail Blk [-]
Step [-]
Description

purposes).
input.
TEST.
Load binary input.
binary input.

Timer 4 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 5
Timer 5 Function

Range [units]
MFail Blk [-]
Step [-]
Description

purposes).
input.
TEST.
Load binary input.
binary input.

Timer 5 Setup

Step N/A [-]
Description
manual.

Subgroup: Timer 6
Timer 6 Function

Range [units]
MFail Blk [-]
Step [-]
Description

purposes).
input.
TEST.
Load binary input.
binary input.

Timer 6 Setup

Step N/A [-]
Description
manual.
Group: Maintenance Timers
Subgroup: Maintenance Timer 1
Maintenance Timer 1 RunHours
Setpoint group Maintenance Timers Related FW 1.0.0

Range [units] 1 .. 9999 [h] / Disabled
Step 1h
Description
This setpoint defines how much BESS running hours (Running Hours (page 573)) needs to be counted
down by the maintenance timer until value Maintenance Timer 1 RunHours (page 573) reach zero and
alarm Maintenance 1 RunHours (page 860) with LBO AL MAINTENANCE 1 (PAGE 692) 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 574) reach zero and alarm Maintenance 1 Interval (page 859)
with LBO AL MAINTENANCE 1 (PAGE 692) 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 471) / Maintenance 1 RunHours (page 860) and
Maintenance Timer 1 Interval (page 472) / Maintenance 1 Interval (page 859).


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.0.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 479). Delay for protection is adjusted by setpointFence 1 Delay (page 480).
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 479).
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 479).
Sd: Position of BESS is used for shutdown protection. Protection is activated when position of the
BESS is out of Fence 1 Radius (page 479).
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 479).
Note: Protection is activated also when GPS signal is lost for Fence 1 Delay (page 480).
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 479) is activated
afterFence 1 Delay (page 480).

Fence 1 Delay

Default value 0s Force value
Step 1s
Description
Delay for Fence 1 Protection (page 479).
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 481). Delay for protection is adjusted by setpointFence 2 Delay (page 481).
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 481).
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 479).
Note: Protection is activated also when GPS signal is lost forFence 2 Delay (page 481).

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 479) is activated
afterFence 1 Delay (page 480).
Fence 2 Delay

Default value 0s Force value
Step 1s
Description
Delay forFence 2 Protection (page 480).
Group: Plug-In Modules
Subgroup: Slot A
Slot A
Setpoint group Plug-In Modules Related FW 1.0.0

Range [units] ENABLED / DISABLED [-]
Default value ENABLED Force value NO
Step [-]
Description
This setpoint enable or disable module in slot A.

Subgroup: Slot B
Slot B
Setpoint group Plug-In Modules Related FW 1.0.0

Default value ENABLED Force value NO
Step [-]
Description
This setpoint enable or disable module in slot B.
Group: CM-RS232-485
Subgroup: COM1 Setting
COM1 Mode
Setpoint group CM-RS232-485 Related FW 1.0.0

Range [units] Direct / MODBUS / DualSlave / Dual Master [-]
Step [-]
Setpoint visibility Only if relevant module is installed
Description
Communication protocol switch for the COM1 channel.

DualSlave Dual operation protocol – slave function
DualMaster Dual operation protocol – master function

COM1 Communication Speed

Range [units] 9600 / 19200 / 38400 / 57600 / 115200[bps]
Step [-]
Only if relevant module is installed + conditioned by the setpoint COM1 Mode (page
Setpoint visibility
482)
Description
If the direct mode is selected on COM1 channel, the direct communication speed of controller part of line
COM1 Modbus Mode

Range [units] 8N1 / 8N2 / 8E1 [-]
Step [-]
Description
This setpoint adjusts communication mode of Modbus-RTU.
Possible options

COM1 MODBUS Communication Speed

Range [units] 9600 / 19200 / 38400 / 57600 / 115200 [bps]
Step [-]
Setpoint visibility
482)
Description
If the MODBUS mode is selected on COM1 channel, the MODBUS communication speed can be adjusted
here.
Subgroup: COM2 Setting
COM2 Mode

Range [units] Direct / MODBUS / DualSlave / Dual Master [-]
Step [-]
Description
Communication protocol switch for the COM2 channel.

DualSlave Dual operation protocol – slave function
DualMaster Dual operation protocol – master function
COM2 Communication Speed

Range [units] 9600 / 19200 / 38400 / 57600 / 115200[bps]
Step [-]

Setpoint visibility
484)
Description
If the direct mode is selected on COM2 channel, the direct communication speed of controller part of line
COM2 Modbus Mode

Range [units] 8N1 / 8N2 / 8E1 [-]
Step [-]
Description
This setpoint adjusts communication mode of Modbus-RTU.
Possible options
COM2 MODBUS Communication Speed

Range [units] 9600 / 19200 / 38400 / 57600 / 115200 [bps]
Step [-]
Setpoint visibility
484)
Description
If the MODBUS mode is selected on COM2 channel, the MODBUS communication speed can be adjusted
here.

Group: CM-4G-GPS
Subgroup: Cellular Interface
Internet Connection

Step [-]
Description
This setpoint adjust the communication mode of module.
Network Mode

Range [units] 2G / 3G / 4G / Automatic [-]
Step [-]
Description
This setpoint adjusts preferred connection type of CM-4G-GPS module.
Access Point Name

Default value internet Force value NO
Step [-]
Only if relevant module is installed + conditioned by the setpoint Internet
Setpoint visibility
Connection (page 486)
Description
APN (Access Point Name) of the network, provided by GSM operator.

Connection Check IP1

Range [units] [-]
Default value "empty" Force value NO
Step [-]
Setpoint visibility
Description
IP address of reliable server in the internet.
To provide maximal reliability of wireless cellular connection the module is equipped with function that
periodically checks the data connection over the cellular network is working.
This function is based on periodical sending of ICMP messages (known as "ping") to reliable servers in the
internet and checking of their responses. If there is not any response received from any of the servers (at
least one setpoint Connection Check IP1, IP2, IP3 is filled with IP address) for certain time period, the
cellular connection is considered as non-working and the module will close and reestablish the
connection.
If all three servers are not defined (setpoints Connection Check IP1, IP2, IP3 have empty addresses) then
the cellular connection check is disabled


Range [units] [-]
Step [-]
Setpoint visibility
Description
connection.


Range [units] [-]
Step [-]
Setpoint visibility
Description
connection.

DNS Mode

Range [units] Automatic / Manual [-]
Step [-]
Description
This setpoint enables to enter DNS server addresses manually, even with the Internet Connection (page
486) set to Automatic.
Automatic DNS server addresses automatically obtained from a DHCP server are used
Manual
do not work
DNS IP Address 1

Step [-]
Description
The setpoint is used to select the method how the DNS Address 1 is adjusted.
If DNS Mode (page 490) is MANUAL this setpoint is used to adjust the domain name server (DNS), which
is needed to translate domain names in email addresses and server names into correct IP addresses.
If DNS Mode (page 490) is AUTOMATIC this setpoint is inactive. The DNS server IP address is assigned
by the DHCP server.

DNS IP Address 2

Step [-]
Description
If DNS Mode (page 490) is FIXED this setpoint is used to adjust the domain name server (DNS), which is
needed to translate domain names in email addresses and server names into correct IP addresses.
If DNS Mode (page 490) is AUTOMATIC this setpoint is inactive. The DNS server IP address is assigned
by the DHCP server.
IP Firewall

Default value DISABLED Force value NO
Step [-]
Description
This setpoints enables to switch on the built-in Firewall functionality.
DISABLED The firewall function is switched off

The firewall function is switched on, use InteliConfig to setup the firewall rules
ENABLED
(configuration card Others – Firewall)

AirGate Connection

Range [units] Disabled/ Enabled [-]
Step [-]
Setpoint visibility
Description
This setpoint enable or disable AirGate connection via CM-4G-GPS.
DISABLED: Only SMS are sent. Internet-enabled SIM card is not required. AirGate is not used.
ENABLED This mode uses the "AirGate" service. Internet-enabled SIM card must be used.
The AirGate server address is adjusted by the setpoint AirGate Address (page
510).
IMPORTANT: When this setpoint is changed the controller has to be restarted to apply
changes.
AirGate Address
EthernetCM-4G-
GPSEthernet
Step [-]
Description

Airgate Port

Range [units] 1 .. 65535 [-]
Step 1
Setpoint visibility
Description
EthernetEthernetCM-
4G-GPSEthernet
Range [units] 0 .. 65535 [s]
Step 1s
Description

Direct Connection

Step [-]
Description
Use this 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.

Range [units] 1 .. 65535 [-]
Step [-]
Description
This port is used to listen for an incoming TCP connection if Direct Connection is ENABLED.

SMTP Server Address

Step [-]
Description
74.125.39.109) or number of port (with colon like a first mark) of the SMTP server. Ask your internet
provider or IT manager for this information.
channels.
SMTP Sender Address

Step [-]
Description
followed.

SMTP User Name

Step [-]
Related
applications
Description
SMTP User Password

Step [-]
Description

SMTP Encryption

Step [-]
Description

STARTTLS
E-mail Address 1
EthernetCM-4G-
GPSEthernet
Step [-]
Description

E-mail Address 4
EthernetCM-4G-
GPSEthernet
Step [-]
Description
E-mail Address 3
EthernetCM-4G-
GPSEthernet
Step [-]
Description
E-mail Address 2
EthernetCM-4G-
GPSEthernet
Step [-]
Description

Telephone Number 1

Step [-]
Setpoint visibility (missing or bad snippet)
Description
Enter in this setpoint a valid GSM phone number where the alarm messages shall be sent. For GSM
numbers use either the national format (i.e. the number you would dial if you wanted to make a local call)
or the full international format beginning with a "+" character followed by the country prefix.
IMPORTANT: Telephone number has to be entered without spaces.
Telephone Number 2

Step [-]
Description

Telephone Number 3

Step [-]
Description
Telephone Number 4

Step [-]
Description

E-mail/SMS Language
EthernetCM-4G-
GPSEthernet
Step [-]
Description
Event Message
EthernetCM-4G-
GPSEthernet
Step [-]
Description
Sd Message
Ethernet
Ethernet
Step [-]
Description
Messages.

Stp Message
CM-4G-GPS
Ethernet
Step [-]
Description
Wrn Message
EthernetCM-4G-
GPSEthernet
Step [-]
Description
Subgroup: GPS Settings
GPS Tracking

Step [-]
Setpoint visibility
Description
If GPS tracking is enabled the module sends position/speed data to the controller with period 10 s.

Time Zone

Step [-]
Description
NTP Clock Sync

Range [units] DISABLED / ENABLED [-]
Step [-]
Description
This setpoint is used to enable/disable controller time synchronization with exact time from an NTP server.
The period of synchronization is 1 hour or when the cotnroller is reset or when the setpoint is reset
(Enabled->Disabled->Enabled).

NTP Server

Range [units] [-]
Step [-]
Description
NTP server address.
GPS Clock Sync

Step [-]
Setpoint visibility
Description
This setpoint is used to enable/disable synchronization of the controller's time with the exact time from
GPS.
The module sends UTC timestamp to the controller after reset/power on and then in period of 60 minutes.

Group: CM-Ethernet
IP Address Mode
Setpoint group CM-Ethernet Related FW 1.0.0

Range [units] MANUAL / AUTOMATIC / DISABLED [-]
Default value AUTOMATIC Force value NO
Step [-]
Description
The setpoint is used to select the method how the ethernet connection is adjusted.
MANUAL The Ethernet connection is fixed by means of the setpoints IP Addr, NetMask,
GateIP, DNS IP Address.
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 setting is obtained automatically from the DHCP
server. The obtained settings are then copied to the related setpoints. If the
process of obtaining the settings from the DHCP server is not successful, the
value 000.000.000.000 is copied to the setpoint IP address and the module
continues to try to obtain the settings.
DISABLED The Ethernet terminal is disabled.

IP Address

Step [-]
Only if relevant module is installed + conditioned by the setpoint IP Address Mode
Setpoint visibility
(page 505)
Description
The setpoint is used to set the address when you are in static mode .
If IP Address Mode (page 505) is MANUAL this setpoint is used to adjust the IP address of the ethernet
interface of the controller. Ask your IT specialist for help with this setting.
If IP Address Mode (page 505) is AUTOMATIC this setpoint is inactive. The IP address is assigned by
the DHCP server.
If IP Address Mode (page 505) is DISABLED Ethernet terminal is disabled.
Subnet Mask

Step [-]
Setpoint visibility
(page 505)
Description
The setpoint is used to select the method how the Subnet Mask is adjusted.
If IP Address Mode (page 505) is MANUAL this setpoint is used to adjust the Subnet Mask. Ask your IT
If IP Address Mode (page 505) is AUTOMATIC this setpoint is inactive. The Subnet Mask is assigned by
the DHCP server.

Gateway IP

Step [-]
Setpoint visibility
(page 505)
Description
The setpoint is used to select the method how the Gateway IP is adjusted.
If IP Address Mode (page 505) is MANUAL this setpoint is used to adjust the Subnet Mask. Ask your IT
If IP Address Mode (page 505) is AUTOMATIC this setpoint is inactive. The Subnet Mask is assigned by
the DHCP server.
A gateway is a device which connects the respective segment with the other segments and/or Internet.
DNS Mode

Range [units] Automatic / Manual [-]
Step [-]
Description
This setpoint enables to enter DNS server addresses manually, even with the IP Address Mode (page
505) set to Automatic.
Automatic DNS server addresses automatically obtained from a DHCP server are used
Manual
do not work

DNS IP Address 1

Step [-]
Description
The setpoint is used to select the method how the DNS Address 1 is adjusted .
If IP Address Mode (page 505) is MANUAL this setpoint is used to adjust the domain name server
(DNS), which is needed to translate domain names in email addresses and server names into correct IP
addresses.
If IP Address Mode (page 505) is AUTOMATIC this setpoint is inactive. The DNS server IP address is
DNS IP Address 2

Step [-]
Description
If IP Address Mode (page 505) is MANUAL this setpoint is used to adjust the domain name server
(DNS), which is needed to translate domain names in email addresses and server names into correct IP
addresses.
If IP Address Mode (page 505) is AUTOMATIC this setpoint is inactive. The DNS server IP address is

IP Firewall

Step [-]
Description
This setpoints enables to switch on the built-in Firewall functionality.
DISABLED The firewall function is switched off

The firewall function is switched on, use InteliConfig to setup the firewall rules
ENABLED
(configuration card Others – Firewall)
AirGate Connection

Step [-]
Description
This setpoint enables or disables AirGate connection (page 102) function.

AirGate Address
EthernetCM-4G-
GPSEthernet
Step [-]
Description
AirGate Port

Range [units] 0 .. 65535 [-]
Step 1 [-]
Description

EthernetEthernetCM-
4G-GPSEthernet
Range [units] 0 .. 65535 [s]
Step 1s
Description
Direct Connection

Step [-]
Description
Use this 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.


Range [units] 1 .. 65535 [-]
Step [-]
Description
This port is used to listen for an incoming TCP connection if Direct Connection is ENABLED.
Subgroup: Modbus Server Settings
MODBUS Server

Step [-]
Description
Enable or disable Modbus communication via ethernet interface.

Modbus Client Inactivity Timeout
Ethernet
Ethernet
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: SNMP Settings
SNMP Agent

Step [-]
Description
Enable or disable SNMP Agent.

SNMP Trap Format

Range [units] v1Trap / v2Notif / v2Inform [-]
Default value v1Trap Force value NO
Step [-]
Description
This setpoint adjusts type of SNMP traps.

Step [-]
Description

Step [-]
Description

SNMP RD Community String

Default value public Force value NO
Step [-]
Description
SNMP Community String only for reading.
SNMP WR Community String

Default value private Force value NO
Step [-]
Setpoint visibility Only if SNMP Agent (page 306) = SNMP v1/v2c
Description
SNMP Community String for writing and reading.
SNMP Engine User Name

Step [-]
Description
Defines SNMP v3 Engine User Name.

SNMP Privacy Protocol

Range [units] DES / 3DES / AES128 / AES256 [-]
Default value AES128 Force value NO
Step [-]
Comm object 23853 Related applications (missing or bad snippet)
Description
Selects SNMP v3 Privacy Protocol.
SNMP Authentication Protocol

Range [units] MD5 / SHA / SHA256[-]
Default value SHA Force value NO
Step [-]
Description
Selects SNMP v3 Authentication Protocol.
SNMP Security Level

Range [units] NONE/ AUTH-NOPRIV / AUTH-PRIV [-]
Step [-]
Description
Selects SNMP v3 security level. If NONE the agent will work in SNMP v2c mode..

SMTP Server Address
EthernetCM-4G-
GPSEthernet
Step [-]
Description
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".
channels.
SMTP Sender Address
EthernetCM-4G-
GPSEthernet
Step [-]
Description
followed.

SMTP User Name
EthernetCM-4G-
GPSEthernet
Step [-]
Related
applications
Description
SMTP User Password
EthernetCM-4G-
GPSEthernet
Step [-]
Description

SMTP Encryption
EthernetCM-4G-
GPSEthernet
Step [-]
Description

STARTTLS
SMTP User Name

Step [-]
Related
Comm object 23880 (missing or bad snippet)
applications
Description

SMTP User Password

Step [-]
Description
SMTP Encryption

Step [-]
Description

STARTTLS

E-mail Address 1
EthernetCM-4G-
GPSEthernet
Step [-]
Description
E-mail Address 2
EthernetCM-4G-
GPSEthernet
Step [-]
Description
E-mail Address 3
EthernetCM-4G-
GPSEthernet
Step [-]
Description

E-mail Address 4
EthernetCM-4G-
GPSEthernet
Step [-]
Description
E-mail/SMS Language
EthernetCM-4G-
GPSEthernet
Step [-]
Description
Event Message
EthernetCM-4G-
GPSEthernet
Step [-]
Description

Sd Message
Ethernet
Ethernet
Step [-]
Description
Messages.
Stp Message
CM-4G-GPS
Ethernet
Step [-]
Description
Wrn Message
EthernetCM-4G-
GPSEthernet
Step [-]
Description

Time Zone

Step [-]
Description
NTP Clock Synchronization

Step [-]
Description
This setpoint is used to enable/disable controller time synchronization with exact time from an NTP server.
The period of synchronization is 1 hour or when the cotnroller is reset or when the setpoint is reset
(Enabled->Disabled->Enabled).

NTP Server

Range [units] [-]
Step [-]
Description
NTP server address.

Group: EM-BIO8-EFCP

Subgroup: EFCP Settings

Earth Fault Current Protection

Range [units]
Step [-]
Description
This setpoint enables or disables Earth Fault Current Protection.
Bbehavior is adjusted via setpoints Earth Fault Current Sd (page 530) and Earth Fault Delay (page
529). When the protection is triggered the alarm Sd IDMT Earth Fault Current (page 831) is activated.
Igen = Maximum (BESS Current L1 (page 549), BESS Current L2 (page 549), BESS Current L3
(page 549))
Example:
Earth Fault Current Sd (page 530) = 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
Setpoint options:

Earth Fault Delay

Range [units] 0.1 .. 600.0 [s]
Step 0.1 s
Description
This setpoint specifies the delay for Earth Fault Current Protection (page 528).
Earth Fault CT Input Range
Setpoint group EM-BIO8-EFCP Related FW 1.0.0

Range [units] 1 [A] / 5 [A]
Default value 5A Force value NO
Step [-]
Description
There are 2 physical inputs for Earth Fault Current Protection (page 528). Value of this setpoint has to
be set on value of physical input which is presently in use.

Earth Fault CT Ratio
Setpoint group EM-BIO8-EFCP Related FW 1.0.0

Range [units] 1 .. 2000 [1/(1or5) A]
Default value 500 1/(1or5)A Force value NO
Step 1 A/ 1A; 1 A/5 A
Description
Earth Fault current transformer ratio.
Note: Type of units depends on setpoint Earth Fault CT Input Range (page 529) which have to be
set before this setpoint.
Earth Fault Current Sd

Step 1 [A]
Description
This setpoint specifies the current threshold level for Earth Fault Current Protection (page 528).

8.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 532)
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: Energy Storage 538
Group: Power Conversion System 540
Group: BESS 541
Group: Mains/Bus 552
Group: Power Management 557
Group: SpeedLoad Control 562
Group: Voltage/PF Control 563
Group: User Buttons 566
Group: Controller I/O 566
Group: Statistics 569
Group: Info 576
Group: Log Bout 582
Group: Scheduler 586
Group: CM-4G-GPS 589
Group: CM-Ethernet 595
Group: Ethernet 599
Group: PLC 603
Group: Remote Control 625
Group: Plug-in 629
Group: SH Modules 629

List of values
Group: Energy Storage 538 BESS Current THD L1 546

ES Nominal Capacity 538 BESS Current THD L2 546
ES SOC 538 BESS Current THD L3 546
ES Voltage Meas 538 BESS Frequency 547
ES Voltage 538 BESS Voltage L1-N 547
ES Current 539 BESS Voltage L2-N 547
ES Max Charging Power 539 BESS Voltage L3-N 547
ES Max Discharging Power 539 BESS Voltage L1-L2 547
ES Temperature 539 BESS Voltage L2-L3 548
Group: Power Conversion System 540 BESS Voltage L3-L1 548
PCS Voltage Meas 540 BESS Voltage 548
PCS Current Meas 540 BESS V Unbalance Ph-N 548
PCS Power Meas 540 BESS V Unbalance Ph-Ph 549
Group: BESS 541 BESS Current L1 549
BESS P 541 BESS Current L2 549
BESS P L1 541 BESS Current L3 549
BESS P L2 541 BESS Current Unbalance 550
BESS P L3 541 Earth Fault Current 550
BESS Q 542 Nominal Power 550
BESS Q L1 542 Nominal Voltage 550
BESS Q L2 542 Nominal Current 551
BESS Q L3 542 Slip Frequency 551
BESS S 543 Slip Angle 551
BESS S L1 543 Earth Fault Current - BIO8 551
BESS S L2 543
Group: Mains/Bus 552
BESS S L3 543 Bus Frequency 552
BESS Power Factor 544 Bus Voltage L1-N 552
BESS Load Character 544 Bus Voltage L2-N 552
BESS Power Factor L1 544 Bus Voltage L3-N 552
BESS Load Character L1 544 Bus Voltage L1-L2 552
BESS Power Factor L2 544 Bus Voltage L2-L3 553
BESS Load Character L2 545 Bus Voltage L3-L1 553
BESS Power Factor L3 545 Bus Voltage 553
BESS Load Character L3 545 Bus V Unabalance Ph-N 553
BESS Voltage THD L1 545 Bus V Unbalance Ph-Ph 554
BESS Voltage THD L2 546 +Bus Voltage 554
BESS Voltage THD L3 546

+Bus Voltage Relative 554 BESS Required PF 564
Max Vector Shift 554 BESS Required PF Character 564
ROCOF1 555 Voltage Regulator Output 564
Max ROCOF1 555 Voltage Request 565
ROCOF2 555 PCS Voltage Request 565
Max ROCOF2 556 PCS Voltage Offset Request 565
ROCOF3 556 PCS Q Request % 565
Max ROCOF3 556 Group: User Buttons 566
ROCOF4 557 User Buttons 566
Max ROCOF4 557 Group: Controller I/O 566
Group: Power Management 557 Battery Voltage 566
BESS Priority 557 D+ 566
Actual Reserve 558 CU-AIN-01 567
Actual Reserve 558 CU-AIN-02 567
Stop Reserve 558 CU-AIN-03 567
Dynamic Spinning Reserve 558 CU-AIN-04 567
Dynamic Spinning Reserve Offset 559 Binary Inputs 568
Actual Relative Reserve 559 E-STOP 568
Start Relative Reserve 559 Binary Outputs 569
Stop Relative Reserve 559 Group: Statistics 569
Actual Active Power In PM 560 BESS Charging Cycles 569
Actual Reactive Power In PM 560 Batt. Discharge kWh 570
Running Nominal Power In PM 560 BESS Discharge Annual kWh 570
Running Nominal Power Of All 560 BESS Discahrge Month kWh 570
Available Nominal Power 560 BESS Discharge Week kWh 570
Minimal Running Nominal Power 561 BESS Discharge Daily kWh 571
Actual Power Band 561 BESS Charge kWh 571
Next Power Band 561 BESS Charge Annual kWh 571
Group: SpeedLoad Control 562 BESS Charge Month kWh 571

BESS Required P Target 562 BESS Charge Week kWh 572
BESS Required P 562 BESS Charge Daily kWh 572
HLC P Request 562 PCC kWh 572
Frequency Regulator Output 562 PCC kVArh 572
PCS Frequency Request 563 PCC kVAh 573
PCS Frequency Offset Request 563 Running Hours 573
PCS P Request 563 Num Starts 573
Group: Voltage/PF Control 563 Maintenance Timer 1 RunHours 573

BESS Required Q 563 Maintenance Timer 1 Interval 574
BESS Required Qrel Lim 563 Maintenance Timer 2 RunHours 574
HLC Q Request 564 Maintenance Timer 2 Interval 574

Maintenance Timer 3 RunHours 574 Log Bout 5 583
Maintenance Timer 3 Interval 575 Log Bout 6 583
Maintenance Timer 4 RunHours 575 Log Bout 7 583
Maintenance Timer 4 Interval 575 Log Bout 8 584
Num E-Stops 575 Log Bout 9 584
Shutdowns 576 Log Bout 10 584
Group: Info 576 Log Bout 11 584
Active Application 576 Log Bout 11 584
Controller Mode 576 Log Bout 12 585
Load Shedding Status 576 Log Bout 13 585
BESS state 577 Log Bout 14 585
Breaker state 577 Log Bout 15 585
Timer Text 577 Group: Scheduler 586
Connection Type 577 Time 586
SPI Module A 577 Date 586
SPI Module B 578 Real Sunrise Time 586
Timer Value 578 Real Sunset Time 586
ID String 578 Time To Sunrise 587
FW Version 578 Time To Sunset 587
Application 578 Time Mode 587
FW Branch 579 Exercise Timer 1 587
BESS State Machine 579 Exercise Timer 2 588
Breaker State Machine 579 Exercise Timer 3 588
BESS Info 579 Exercise Timer 4 588
PCS Info 579 Exercise Timer 5 588
BMS Info 580 Exercise Timer 6 589
AUX Info 580 Group: CM-4G-GPS 589
Forced Value Status 580 Signal Strength 589
CAN16 580 Network Status 589
CAN32 581 Network Name 589
Reg16 581 Network Mode 590
Reg32 581 Modem Status 590
Gen Loaded 16 582 IP Address 590
Gen Loaded 32 582 Primary DNS 590
Group: Log Bout 582 Secondary DNS 591

Log Bout 1 582 Last E-mail Result 592
Log Bout 2 582 GPS Status 593
Log Bout 3 583 Latitude 593
Log Bout 4 583 Longitude 593

HomePosDist 594 PLC-AOUT 7 604
Active Satellites 594 PLC-AOUT 8 604
Speed 594 PLC-AOUT 9 604
AirGate ID 594 PLC-AOUT 10 605
AirGate Status 595 PLC-AOUT 11 605
AirGate Servicing Node 595 PLC-AOUT 12 605
Modem FW Version 595 PLC-AOUT 13 605
Group: CM-Ethernet 595 PLC-AOUT 14 605
ETH Interface Status 595 PLC-AOUT 15 606
Current IP Address 596 PLC-AOUT 16 606
Current Subnet Mask 596 PLC-AOUT 17 606
Current Gateway 596 PLC-AOUT 18 606
Primary DNS 596 PLC-AOUT 19 606
Secondary DNS 597 PLC-AOUT 20 607
Last E-mail Result 598 PLC-AOUT 24 607
MAC Address 598 PLC-AOUT 25 608
Ethernet PHY mode 598 PLC-AOUT 26 608
Group: Ethernet 599 PLC-AOUT 27 608
MAC Address 600 PLC-AOUT 31 609
Ethernet PHY mode 600 PLC-AOUT 32 609
Current IP Address 600 PLC-AOUT 33 609
Current Subnet Mask 601 PLC-AOUT 34 609
Current Gateway 601 PLC-AOUT 35 610
Primary DNS 601 PLC-AOUT 36 610
Secondary DNS 601 PLC-AOUT 37 610
ETH Interface Status 601 PLC-AOUT 38 610
Last E-mail Result 602 PLC-AOUT 39 610
Group: PLC 603 PLC-AOUT 40 611
PLC-AOUT 1 603 PLC-AOUT 41 611
PLC-AOUT 6 604

PLC-AOUT 46 612 PLC-BOUT 21 620
PLC-AOUT 58 614 PLC Resource 1 622
PLC-BOUT 1 616 PLC Resource 8 623
PLC-BOUT 10 617 Group: Remote Control 625
PLC-BOUT 11 618 RemoteControl2B 1 625

RemoteControl4B 3 628
RemoteControl4B 4 628
RemoteControlBin 628
Group: Plug-in 629
EM BIO A 629
EM BIO B 629
Group: SH Modules 629
SHBIN-1 629
SHBIN-2 630
SHBIN-3 630
SHBIN-4 631
SHBIN-5 631
SHBIN-6 632
SHBOUT-1 632
SHBOUT-2 633
SHBOUT-3 633
SHBOUT-4 634
SHBOUT-5 634
SHBOUT-6 635
SHAIN-1 1 635
SHAIN-1 2 635
SHAIN-1 3 636
SHAIN-1 4 636
SHAIN-2 1 636
SHAIN-2 2 636
SHAIN-2 3 637
SHAIN-2 4 637
6 back to Controller objects

Group: Energy Storage
ES Nominal Capacity
Value group Value Group BESS Related FW 1.0.0

Units kWh
Description
This value shows nominal capacity of the Energy Storage.
6 back to List of values
ES SOC

Units %
Comm
15857 Related applications MINT
object
Description
Actual state of charge of the Energy Storage.
ES Voltage Meas
Value group Energy Storage Related FW 1.0.0

Units V
Description
Energy Storage DC Voltage measured by physical AIN. This values is used for ES DC protections.
ES Voltage

Units V
Comm
object
Description
Energy Storage DC Voltage measured by BMS.

ES Current

Units A
Comm
object
Description
Energy Storage DC Voltage measured by BMS.
ES Max Charging Power

Units kW
Comm
object
Description
Maximal charging power of the Energy Storage computed by BMS.
ES Max Discharging Power

Units kW
Comm
object
Description
Maximal discharging power of the Energy Storage computed by BMS.
ES Temperature

Units °C
Comm
object
Description
Actual BESS temperature.

Group: Power Conversion System
PCS Voltage Meas

Units []
Comm
object
Description
Power Conversion System DC Voltage measured by physical AIN. This value is used for PCS
DC protections.
PCS Current Meas

Units []
Comm
object
Description
Power Conversion System DC Current measured by physical AIN. This value is used for PCS
DC protections.
PCS Power Meas

Units []
Comm
object
Description
Power Conversion System DC Power computed from Current and Voltage meas. This values is used for
PCS DC protections.

Group: BESS
BESS P

Units kW
Description
Active power of the BESS.
Note: This value can be also switched into one decimal see Power Formats And Units (page 163).
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 544) = 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 544) = 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
547).

BESS Voltage THD L2

Units %
Description
547).
BESS Voltage THD L3

Units %
Description
547).
BESS Current THD L1

Units %
Description
This value represents Current Total Harmonic Distortion (page 18) of BESS Current L1 (page 549).
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 547), BESS Voltage
L2-N (page 547), BESS Voltage L3-N (page 547) at a given moment.
Note: Difference of the values and the evaluation of the protection is influenced by the setpoint
Connection type (page 285).

BESS V Unbalance Ph-Ph

Units V
Description
This value contains the maximum difference of values BESS Voltage L1-L2 (page 547), BESS Voltage
L2-L3 (page 548), BESS Voltage L3-L1 (page 548) 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 549), BESS Current L2
(page 549) and BESS Current L3 (page 549).
Earth Fault Current
Value group BESS Related FW 1.0.0

Units A
Description
Measured fault value for evaluation of Earth Fault Current Protection (page 528).
Nominal Power

Units [kW]
Comm
object
Description
This value is used for adjusting the BESS's nominal (rated) power.
Nominal Voltage

Units [V]
Comm
object
Description
This setpoint is used for adjusting the BESS's nominal voltage.

Nominal Current

Units [A]
Comm
object
Description
This setpoint is used for adjusting the BESS's nominal current.
Slip Frequency
Value group Mains/Bus Related FW 1.0.0

Units Hz
Description
Slip frequency during synchronization.
Slip Angle

Units °
Description
Slip angle during synchronization.
Earth Fault Current - BIO8

Units [A]
Comm
object
Description
Measured fault value for evaluation of Earth Fault Current Protection (page 528).

Group: Mains/Bus
Bus Frequency

Units Hz
Description
Frequency of Bus.
Bus Voltage L1-N
Value group Value Group Bus Related FW 1.0.0

Units V
Description
Value of Bus voltage on phase 1.
Bus Voltage L2-N

Units V
Description
Bus Voltage L3-N

Units V
Description
Bus Voltage L1-L2

Units V
Description
Value of Bus phase to phase voltage between L1 and L2 phases.

Bus Voltage L2-L3

Units V
Description
Bus Voltage L3-L1

Units V
Description
Bus Voltage

Units V
Description
Average value of all BusVoltage phases.
Bus V Unabalance Ph-N

Units V
Description
This value contains the maximum difference of values Bus Voltage L1-N (page 552), Bus Voltage L2-
N (page 552), Bus Voltage L3-N (page 552) at a given moment.

Bus V Unbalance Ph-Ph

Units V
Description
This value contains the maximum difference of values Bus Voltage L1-L2 (page 552), Bus Voltage L2-
L3 (page 553), Bus Voltage L3-L1 (page 553) at a given moment.
+Bus Voltage

Units V
Description
Value of +Bus voltage measured by Symmetrical components (page 16)
+Bus Voltage Relative

Units V
Description
Value of +Bus voltage measured by Symmetrical components (page 16) which is related to Bus
Nominal Voltage Ph-N (page 287) or Mains/Bus Nominal Voltage Ph-Ph (page 287).
Max Vector Shift

Units °
Description
Maximal measured value of Vector shift (page 144) of the Mains. It is reset to zero always when:
Vector Shift Protection (page 368) = Parallel Only - controller goes to parallel toMains
operation
Vector Shift Protection (page 368) = Enabled - MCB gets closed

ROCOF1

Units Hz/s
Description
This value contains actual rate of change of frequency measured by ROCOF1 Protection (page 369).
See ROCOF (page 144) for more information.
Max ROCOF1

Units Hz/s
Description
This value contains maximal rate of change of frequency measured by ROCOF1 Protection (page 369)
since the protection got active.
Setting Reset of value
ROCOF1 Protection (page 369) = When MCB closes.

Enabled When BCB closes.
ROCOF1 Protection (page 369) = After entering parallel operation (Breaker state (page
Parallel Only 577) = ParalOper)
ROCOF2

Units Hz/s
Description

Max ROCOF2

Units Hz/s
Description

ROCOF3

Units Hz/s
Description
Max ROCOF3

Units Hz/s
Description


ROCOF4

Units Hz/s
Description
Max ROCOF4

Units Hz/s
Description

Group: Power Management
BESS Priority
Value group Power Management Related FW 1.0.0

Units -
Description
This value shows current priority number of the unit. It corresponds to the setpoint Priority (page 401)
except following situations:
If at least one of binary inputs TOP PRIORITY (PAGE 686) is configured on some source and is
active
#Priority Auto Swap (page 402) is active

Actual Reserve

Units kW
Description
Actual absolute reserve in Power Management (page 213).
Actual Reserve

Units kW
Description
Required minimal Actual Reserve (page 558) for starting of next unit in the Power Management (page
213).
Stop Reserve

Units kW
Description
Required maximal Actual Reserve (page 558) for stopping of next unit in the Power Management
(page 213).

Units kW
Description
The value Dynamic Spinning Reserve is added to required load reserve given by setpoints #Starting
Load Reserve 1 (page 405) and #Stopping Load Reserve 1 (page 406) (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 406) (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 213).
Start Relative Reserve

Units %
Description
Required minimal Actual Relative Reserve (page 559) for starting of next unit in the Power
Management (page 213).
Stop Relative Reserve

Units %
Description
Required maximal Actual Relative Reserve (page 559) 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 213).
Actual Reactive Power In PM

Units kVAr
Description
Actual value of reactive power from all controllers running in Power Management (page 213).
Running Nominal Power In PM

Units kW
Description
Actual nominal power of all running controllers on inter-controller CAN in Power Management (page
213).
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 213).

Minimal Running Nominal Power

Units kW
Description
Actual minimal nominal power of all Controllers, which are running.
Actual Power Band

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 402) = Efficient.
Next Power Band

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.
Note: Value is taken into account only if #Priority Auto Swap (page 402) = Efficient.

Group: SpeedLoad Control
BESS Required P Target
Value group Speed/Load Control Related FW 1.0.0

Units kW
Description
This value shows required active power at the end of ramping.
BESS Required P

Units kW
Description
This value shows required active power relative to the ramping procedure i.e. required active power right
now.
HLC P Request

Units % of BESSNominal power (page 280)
Description
Relative value of requested power from HLC.
Frequency Regulator Output

Units V
Description
This is the actual voltage on the frequency regulator output of the controller.
In case the Analog Output (page 206) is switched to PWM mode, the relation is:
10 V = ~100 % PWM.
-10 V = 0 % PWM

PCS Frequency Request

Units Hz
Description
Requested PCS frequency in Hz.
PCS Frequency Offset Request

Units Hz
Description
Relative value of requested power of the PCS.
PCS P Request

Units %
Description
Relative request for PCS kW/Hz output in %.
Group: Voltage/PF Control
BESS Required Q
Value group Voltage/PF Control Related FW 1.0.0

Units kVAr
Description
Required reactive power.
BESS Required Qrel Lim

Units %
Description
Required relative reactive power.

HLC Q Request

Units %
Description
Relative value of requested reactive power from HLC.
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 206) 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.
PCS Voltage Request

Units V
Description
Requested PCS output Voltage in V.
PCS Voltage Offset Request

Units %
Description
Requested offset from the PCS nominal output Voltage in V (positive or negative).
PCS Q Request %

Units %
Description
Relative value of requested reactive power of the PCS.

Group: User Buttons
User Buttons
Value group User Buttons Related FW 1.0.0

Units [-]
Description
State of User Buttons (page 179).
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: Controller I/O
Battery Voltage
Value group Controller I/O Related FW 1.0.0

Units V
Description
Controller's supply voltage.
D+

Units V
Description
D+ terminal voltage.

CU-AIN-01

Units Configurable
Description
This is the value of the analog input 1 of the controller.
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 104) to see default binary inputs names.
E-STOP

Units [-]
Description
Value of .
Log .1 - E-STOP has voltage - alarm E-STOP (page 820) is inactive
Log. 0 - E-STOP has no voltage - alarm E-STOP (page 820) 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 104) to see default binary outputs names.
Group: Statistics
BESS Charging Cycles
Value group Statistics Related FW 1.0.0

Units [-]
Description
This statistical value shows the charging cycles of the BESS. It is incremented together with LAI ES
CHARGING CYCLES (PAGE 735) 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 541)) of the BESS.
BESS 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 541)) of the BESS.
BESS 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 541)) of the BESS.
BESS 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

BESS 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
BESS 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 541)) of the BESS.
BESS 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 541)) of the BESS.
BESS Charge Month kWh

Units kWh
Description
This statistical value is showing the total kWh consumed by the BESS from the system per month. The

BESS Charge Week kWh

Units kWh
Description
This statistical value is showing the total kWh consumed by the BESS from the system per week. The
BESS Charge Daily kWh

Units kWh
Description
This statistical value is showing the total kWh consumed by the BESS from the system per day. The
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 541)) 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 542)) 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 543)) of the BESS.
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 293).
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 471).


Units hours
Description
Countdown days until next maintenance. Initial value can be set in Maintenance Timer 1 Interval (page
472).

Units hours
Description

Units hours
Description
473).

Units hours
Description


Units hours
Description
475).

Units hours
Description

Units hours
Description
476).
Num E-Stops

Units [-]
Description
This value counts amount of BESS shutdowns which are triggered by E-STOP (page 820) or
Emergency Stop (page 820).
Note: Value is incremented only if BESS was running during alarm activation.

Shutdowns

Units [-]
Description
This counter counts occurrences of a Shutdown (page 820) 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 820) and Emergency Stop (page
820). These are counted separately in Num E-Stops (page 575).
Group: Info
Active Application
Value group Info Related FW 1.0.0

Units [-]
Description
This value reflects which application is used for the controller at the moment.
IMPORTANT: Application Mode can be changed only if Controller Mode (page 576) = OFF.
Controller Mode

Units [-]
Description
Controller mode.
Load Shedding Status

Units [-]
Description
This value contains actual active highest stage of Load shedding stages (page 142). 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 285).
SPI Module A

Units [-]
Description
Detected Plug-in module in the slot A.

SPI Module B

Units [-]
Description
Detected Plug-in module in the slot B.
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 577).
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.
BESS State Machine

Units [-]
Description
This value show bits for each state in the internal BESS state machine.
Breaker State Machine

Units [-]
Description
This value show bits for each state in the internal breaker state machine.
BESS Info

Units [-]
Description
This value show general information about Battery Energy Storage System based on internal logic of
controller unit. Bits of this value can be used for any PLC logic or 3rd party devices.
PCS Info

Units [-]
Description
This value show information about Power Conversion System which is obtained from 3rd party devices
via LBIs. Bits of this value can be used for any PLC logic or 3rd party devices.

BMS Info

Units [-]
Description
This value show information about Battery Management System which is obtained from 3rd party
devices via LBIs. Bits of this value can be used for any PLC logic or 3rd party devices.
AUX Info

Units [-]
Description
This value show information about auxiliary systems such as HVAC, PSU, transformer, etc. which is
obtained from 3rd party devices via LBIs. Bits of this value can be used for any PLC logic or 3rd party
devices.
Forced Value Status

Units [-]
Description
This value contains list of all 32 LBIs for Forced Value (page 135). Logical 1 means that the respective
LBI is currently activated.
CAN16

Units [-]
Description
This value contains binary information about controllers connected via CAN2 (page 19) and/or
Communication peripherals (page 19) with Controller Address (page 295) = <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
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
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
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).

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
Log. 1 - controller with this CAN address is currently loaded
Log. 0 - controller with this CAN address is currently not loaded
Group: Log Bout
Log Bout 1
Value group Log Bout Related FW 1.0.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 11

Units [-]
Description

Log Bout 12

Units [-]
Description
Log Bout 13

Units [-]
Description
Log Bout 14

Units [-]
Description
Log Bout 15

Units [-]
Description

Group: Scheduler
Time
Value group Date/Time Related FW 1.0.0

Units HH:MM:SS
Related
applications
Description
Shows setup time.
Date

Units DD.MM.YYYY
Description
Shows setup date.
Real Sunrise Time
Value group Scheduler Related FW 1.0.0

Units [hh:mm.ss]
Comm
object
Description
This value indicates the time until sunrise.
Real 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.
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)
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
Group: CM-4G-GPS
Signal Strength
Value group CM-4G-GPS Related FW 1.0.0

Units [%]
Comm
object
Description
This value represents signal strenght in the percentage.
Network Status

Units
Comm
object
Description
Status of attachment into packet data network (status of PDP context).
Network Name

Units
Comm
object
Description
Operator name or MCC-MNC code.

Network Mode

Units
Comm
object
Description
Mode of the network (2G/3G/4G).
Modem Status

Units
Comm
object
Description
The text of this value represents the status of the modem.
IP Address

Units
Comm
object
Description
IP address of the module.
Primary DNS

Units
Comm
object
Description
Address of the primary DNS.

Secondary DNS

Units
Comm
object
Description
Address of the secondary DNS.

Last E-mail Result

Units
Comm
object
Description
Result of last email, which was sent by controller.
Code Description
0 Email was successfully sent.
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.
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.
20 QUIT command was refused.
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.
28 Error during encoding process.
30 SMTP server address translation error (from DNS server).

GPS Status

Units
Comm
object
Description
Value describing the GPS signal status.
Code Description
Undefined GPS signal is not available. Check antenna connection.
Searching Looking up for signal from available satellites.
Fixed GPS signal available.
Latitude

Units
Comm
object
Description
Actual GPS latitude. Positions on north hemisphere have positive value, position on south hemisphere
have negative value.
Longitude

Units
Comm
object
Description
Actual GPS longitude. Positions on east hemisphere have positive value, position on west hemisphere
have negative value.

HomePosDist

Units
Comm
object
Description
Actual distance from home position. Home position is adjusted via setpoints Home Latitude (page 478)
and Home Longitude (page 478) or by binary input GEO HOME POSITION (PAGE 662).
Active Satellites

Units
Comm
object
Description
Number of available satellites for GPS location.
Speed

Units
Comm
object
Description
Actual speed of the controller calculated from the GPS coordinates.
AirGate ID

Units
Comm
object
Description
Identification string generated by AirGate server for the purpose of establishing communication via
InteliConfig or any other supported PC tool.

AirGate Status

Units
Comm
object
Description
Diagnostic code for AirGate connection. Helps in troubleshooting.
AirGate Servicing Node

Units
Comm
object
Description
IP address of AirGate 2 node to which the module is currently attached.
Modem FW Version

Units
Comm
object
Description
Description.
Group: CM-Ethernet
ETH Interface Status
Value group CM-Ethernet Related FW 1.0.0

Units
Comm
object
Description
Description.

Current IP Address

Units
Comm
object
Description
Description.
Current Subnet Mask

Units
Comm
object
Description
Description.
Current Gateway

Units
Comm
object
Description
Description.
Primary DNS

Units
Comm
object
Description
Description.

Secondary DNS

Units
Comm
object
Description
Description.
AirGate ID

Units
Comm
object
Description
Description.
AirGate Status

Units
Comm
object
Description
Description.

Units
Comm
object
Description
Description.

Last E-mail Result

Units
Comm
object
Description
Description.
MAC Address

Units
Comm
object
Description
Description.
Ethernet PHY mode

Units
Comm
object
Description
Description.

Group: Ethernet
AirGate Status
Value group Ethernet Related FW 1.0.0

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.


Units [-]
Description
This value displays the IP address to Servicing node to which is controller connected in order to use
AirGate connection.
MAC Address

Units [-]
Description
Current MAC address of the controller's ethernet interface.
Ethernet PHY mode

Units [-]
Description
This value reflects what communication mode is used on the Ethernet Port 2.
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
100- HD 100 Mbit Half-Duplex
100- FD 100 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.
Current IP Address

Units [-]
Related
applications
Description
Current IP address of the Ethernet (page 19) interface.

Current Subnet Mask

Units [-]
Description
Current subnet mask of the Ethernet (page 19) interface.
Current Gateway

Units [-]
Description
Current IP gateway address of the Ethernet (page 19) communications.
Primary DNS

Units [-]
Description
Current domain name server of the Ethernet (page 19) interface.
Secondary DNS

Units [-]
Description
Backup domain name server of the Ethernet (page 19) interface.
ETH Interface Status

Units [-]
Description
Current status of the Ethernet (page 19) communication.

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.
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.
Group: PLC
PLC-AOUT 1
Value group PLC Related FW 1.0.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.0.0

Units -
Description
This value contains user data written over Modbus-RTU, Modbus/TCP (page 241). 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: Plug-in
EM BIO A

Units
Comm
object
Description
Description.
EM BIO B

Units
Comm
object
Description
Description.
Group: SH Modules
SHBIN-1
Value group SH Modules Related FW 1.0.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.
IMPORTANT: This value is received (and visible) only when it is configured with sensor
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".

8.1.5 Application Curves
List of Application Curves
Capability L 639
Capability C 640

Capability L
Related FW 1.0.0 Related applications MINT

App Curve ID 4
Description
This curve defines BESS Operation Area (page 194) within which it can deliver reactive power
continuously without overheating while BESS Load Character (page 544) = L.
X-axe is relative value of BESS P (page 541) to BESSNominal power (page 280).
Y-axe is relative value of BESS Q (page 542) to Samax (page 280).
Note: The samax value is counted from BESS Nominal Current (page 282) and BESS Nominal
Voltage Ph-N (page 286) (or Gen Nominal Voltage Ph-Ph (page 286)) in case that Samax (page
280) = OFF.
Default values
X-axe [%] Y-axe [%]

-10 0
0 0
100 106
102 106
Default appearance
6 back to Application Curves

Capability C

App Curve ID 5
Description
This curve defines BESS Operation Area (page 194) within which it can deliver reactive power
continuously without overheating while BESS Load Character (page 544) = C.
X-axe is relative value of BESS P (page 541) to BESSNominal power (page 280).
Y-axe is relative value of BESS Q (page 542) to Samax (page 280).
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 BESS Nominal Current (page 282) and BESS Nominal
Voltage Ph-N (page 286) (or Gen Nominal Voltage Ph-Ph (page 286)) in case that Samax (page
280) = OFF.
Default values
X-axe [%] Y-axe [%]

-10 0
0 0
100 -60
102 -60
Default appearance
6 back to Application Curves

8.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 644
LBI: B 646
LBI: E 652
LBI: F 657
LBI: G 662
LBI: H 663
LBI: I 665
LBI: L 666
LBI: M 669
LBI: N 673
LBI: P 673
LBI: R 681
LBI: S 683
LBI: T 685
For full list of Logical binary inputs go to the chapter Logical binary inputs alphabetically (page 642).

Logical binary inputs alphabetically
LBI: A 644 ES Discharge Enable 653 Forced Value Input 23 662

Access Lock 644 ES Discharging 653 Forced Value Input 24 662
All ES Connection OK 644 ES Ready To Load 654 LBI: G 662
Any BMS HW Fault 644 ES Ready To Start 654 Geo Home Position 662
Any ES Charge Over ESCB Feedback 655 Geo-Fencing Enable 662
Current 644 ESCB Feedback Negative 656 Group link 663
Any ES Connection Not Ext Supply Fail 656 LBI: H 663
OK 644 Horn Reset Button 663
Ext Supply OK 656
Any ES Current Diff Too HVAC Alarm Level 1 663
LBI: F 657
High 645
Fault Reset Button 657 HVAC Alarm Level 2 663
Any ES Discharge Over
Fire Suppression Activated657 HVAC Communication
Current 645
Fire Suppression Alarm Failure 664
Any ES High Temperature 645
Level 1 657 HVAC High External
Any ES Low Temperature 645 Temperature 664
Fire Suppression Alarm
Any ES Over Voltage 645 HVAC High Internal
Level 2 657
Any ES Under Voltage 645 Temperature 664
Forced Value Input 01 657
Any ES Voltage Diff Too HVAC Low External
High 646 Temperature 664
ARMED - Fire suppression HVAC Low Internal
is ready 646 Temperature 664
LBI: B 646 HVAC Running 664
BCB Button 646 Forced Value Input 06 658
LBI: I 665
BCB Close 646 Forced Value Input 07 659
Ignore Low SOC 665
BCB Disable 647 Forced Value Input 08 659
Insulation Resistance
BCB Feedback 648 Forced Value Input 09 659 Critical Low 665
BCB Feedback Negative 649 Forced Value Input 10 659 Insulation Resistance Low 665
BCB Secondary Feedback 650 Forced Value Input 11 659 LBI: L 666
BCB Secondary Feedback Forced Value Input 12 660 Load Res 2 Active 666
Negative 651 Forced Value Input 13 660 Load Res 3 Active 667
BCB Open 651 Forced Value Input 14 660 Load Res 4 Active 668
BESS Door Opened 652 Forced Value Input 15 660 Local Baseload 668
BMS Alarm Level 1 652 Forced Value Input 16 660 LBI: M 669
BMS Alarm Level 2 652 Forced Value Input 17 661 Manual Load
Forced Value Input 18 661 Reconnection 669
LBI: E 652
Emergency MAN 652 Forced Value Input 19 661 MCB Feedback 670
Emergency Stop 653 Forced Value Input 20 661 MCB Feedback Negative 671
ES Charge Enable 653 Forced Value Input 21 661 Min Run Power Act 1 672
ES Charging 653 Forced Value Input 22 662 Min Run Power Act 2 672

Min Run Power Act 3 673 PSU Over/Under Voltage 681
LBI: N 673 PSU Overload 681
NCB Feedback 673 LBI: R 681
LBI: P 673 Remote AUTO 681
PCS AC Over Frequency 673 Remote Ctrl Lock 682
PCS AC Over Voltage 674 Remote MAN 682
PCS AC Overload 674 Remote OFF 682
PCS AC Under Frequency 674 Remote Start/Stop 683
PCS AC Under Voltage 674 LBI: S 683
PCS Alarm Level 1 674 Sd Override 683
PCS Alarm Level 2 674 Soft Unload Enable 683
PCS Communication SOH Critical Low 684
Failure 675 SOH Low 684
PCS Critical Temperature 675 Source Not Operable 684
PCS DC Over Voltage 675 Start Blocking 684
PCS DC Overload 675 Start Button 684
PCS DC Under Voltage 675 Stop Button 685
PCS Derating 675 Sunrise/Sunset Home
PCS High Temperature 676 Position 685
PCS Output Control Mode Synchronization Disabled 685
U-f/P-Q 676 LBI: T 685
PCS PQ Mode 676 TEST ROCOF 685
PCS Ready To Load 676 Test Vector Shift 685
PCS Ready To Start 676 Top Priority 686
PCS Running 677 TX Critical Temperature 686
PCS Saturated 677 TX High Temperature 686
PCS Start Disabled 677 6 back to Controller objects
PCS Starting 677
PCS Stopped 677
PCS Stopping 677
PCS VF Const Freq 678
PCS VF Droop 678
Precharge Finished 678
Protection Force Disable 1 679
PSU Alarm Level 1 680
PSU Alarm Level 2 680
PSU Critical Temperature 680
PSU High Temperature 681

LBI: A
Access Lock

LBI ID 1
Description
When this input is closed, no setpoints can be adjusted from controller’s front panel and Microgrid mode
(OFF / MAN / AUTO / TEST) cannot be changed.
Note: Access Lock does not protect setpoints and mode changing from InteliConfig. To avoid
unqualified changes the selected setpoints have to be password protected. Also the buttons Fault
Reset and Horn Reset are not blocked at all and buttons Start and Stop in MAN mode are not
blocked.
6 back to Logical binary inputs alphabetically
All ES Connection OK

LBI ID 1257
Description
The status of this LBI is mirrored in group BMS Info (page 580)
Any BMS HW Fault

LBI ID 1256
Description
Any ES Charge Over Current

LBI ID 1269
Description
Any ES Connection Not OK

LBI ID 1264
Description

Any ES Current Diff Too High

LBI ID 1266
Description
Any ES Discharge Over Current

LBI ID 1270
Description
Any ES High Temperature

LBI ID 1271
Description
Any ES Low Temperature

LBI ID 1272
Description
Any ES Over Voltage

LBI ID 1267
Description
Any ES Under Voltage

LBI ID 1268
Description

Any ES Voltage Diff Too High

LBI ID 1265
Description
ARMED - Fire suppression is ready

LBI ID 1285
Description
The status of this LBI is mirrored in group AUX Info (page 580)
LBI: B
BCB Button

LBI ID 193
Description
Binary input has the same function as BCB button on an External display (page 65).
BCB Close

LBI ID 273
Description
This LBI serves for demandingBCB to close.
If the breaker is opened and a pulse comes to this LBI breaker is internally requested to be closed. This
can either cause immediate closing of breaker (for example to dead bus) or synchronization before
closing the breaker.
If the breaker is closed this LBI has no effect.
When this LBI is received by the controller, history record "BCB Close Requested" is written to the
history. In case that closing sequence of the breaker is blocked, history record "BCB Close Blocked" is
written to the history.
Note: LBI BCB Open has higher priority.

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 GCB 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.8 BCB Feedback 1
This input is used for connection of the normally open feedback contact from the BESS 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
695) within time adjusted in Setpoint Waiting For Breaker Feedback (page 396), 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 835) 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 BESS 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 648). Maximal allowed time the both inputs are in the
same position is 500ms, after this time the Alarm Stp BCB Fail (page 835) is issued.
Image 7.10 BCB Feedback Negative 1

BCB Secondary Feedback

LBI ID 548
Description

BCB Secondary Feedback Negative

LBI ID 982
Description
This input is logically inverted against LBI BCB SECONDARY FEEDBACK (PAGE 650).
Image 7.14 BCB Feedback Secondary Negative 1
Image 7.15 BCB Feedback Secondary Negative 2
BCB Open

LBI ID 274
Description
This LBI serves for demanding BCB to open and preventing its closing.
If the breaker is closed and a pulse comes to this LBI, the unloading sequence is initiated. When Value
BESS P (page 541) gets below the Setpoint Generator Unload BCB Open Level (page 382) or after
Setpoint Soft Unload Ramp (page 383) elapses. In case there is no other source that can take the load,
BCB is opened immediately.
If the breaker is opened and this LBI is active, breaker closing is not accepted.
When this LBI is received by the controller, history record "BCB Open Requested, Close Blocked" is
written to the history. If this LBI is deactivated or controller mode is changed to one that does not support
this LBI, history record "BCB Close Unblocked" is written to the history.
Note: This LBI has higher priority than LBI BCB Close.

BESS Door Opened

LBI ID 1299
Description
BMS Alarm Level 1

LBI ID 1254
Description
BMS Alarm Level 2

LBI ID 1255
Description
LBI: E
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 820) is activated.
ES Charge Enable

LBI ID 1105
Description
This logical input enables charging process of the battery.
ES Charging

LBI ID 1263
Description
ES Discharge Enable

LBI ID 1106
Description
This logical input enables discharging process of the battery.
ES Discharging

LBI ID 1262
Description

ES Ready To Load

LBI ID 1165
Description
Logical binary input signaling that the Energy Storage is ready to be switched into the load.
ES Ready To Start

LBI ID 1164
Description
Logical binary input for Energy Storagereadiness.

ESCB Feedback

LBI ID 1169
Description
Use this input to indicate whether the Energy Storage circuit breaker is opened or closed.
This input is used for connection of the normally open feedback contact from the Energy Storage circuit
breaker or contactor. If the input is active, the controller will consider the ESCB as closed.
If the feedback does not respond to a change of the control output LBO ESCB CLOSE/OPEN (PAGE
711) within time adjusted in Setpoint Waiting For Breaker Feedback (page 396), 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 Sd ESCB Fail (page 823) will be issued immediately.

ESCB Feedback Negative

LBI ID 1170
Description
Use this input to indicate whether the Energy Storage circuit breaker is opened or closed.
This input is used for connection of the normally closed feedback contact from the ES 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 ESCB FEEDBACK (PAGE 655). Maximal allowed time the both inputs are in the same
position is 500ms, after this time the Alarm Sd ESCB Fail (page 823) is issued.
Ext Supply Fail

LBI ID 1294
Description
Ext Supply OK

LBI ID 1293
Description

LBI: F
Fault Reset Button

LBI ID 191
Description
Binary input has the same function as Fault Reset button on an External display (page 65).
Fire Suppression Activated

LBI ID 1286
Description
Fire Suppression Alarm Level 1

LBI ID 1283
Description
Fire Suppression Alarm Level 2

LBI ID 1284
Description
Forced Value Input 01

LBI ID 19
Description
This LBI is used for activation of preconfigured Forced Value (page 135) 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: G
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 478) and Home Longitude (page 478) 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 479) and Fence 2 Protection (page
480) if Geo-Fencing (page 477) is adjusted to value "LBI Enable".
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 427) and Group Link R (page 427). If the input is active, then the two selected
groups will perform Power Management (page 213), 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.
LBI: H
Horn Reset Button

LBI ID 192
Description
Binary input has the same function as Horn reset button on an External display (page 65).
HVAC Alarm Level 1

LBI ID 1275
Description
HVAC Alarm Level 2

LBI ID 1276
Description

HVAC Communication Failure

LBI ID 1277
Description
HVAC High External Temperature

LBI ID 1281
Description
HVAC High Internal Temperature

LBI ID 1279
Description
HVAC Low External Temperature

LBI ID 1282
Description
HVAC Low Internal Temperature

LBI ID 1280
Description
HVAC Running

LBI ID 1278
Description

LBI: I
Ignore Low SOC

LBI ID 1186
Description
This LBI ignore low SOC which allows for discharging of the battery when ValueES SOC (page 538)
is below Setpoint SOC Low Hysteresis (page 322) or Setpoint SOC Low Target (page 322) (note:
LBI ES DISCHARGE ENABLE (PAGE 653) has to be active too).
Insulation Resistance Critical Low

LBI ID 1298
Description
Insulation Resistance Low

LBI ID 1297
Description

LBI: L
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 213)) instead of the set #1, which is active by default. The set #2 is adjusted by
setpoints:
#Starting Load Reserve 2 (page 408) and #Stopping Load Reserve 2 (page 409) if the power
management is switched to absolute mode
#Starting Rel Load Reserve 2 (page 410) and #Stopping Rel Load Reserve 2 (page 411) 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:
Local Baseload

LBI ID 1172
Description
This logical input is used to activate Local Baseload operation if BCB is closed and setpoint Local
Baseload (page 274) is set to Enabled. If Local Baseload is not active, Load Sharing operation is used
instead.

LBI: M
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 437). This works only if automatic
reconnection is disabled, i.e. the setpoint Auto Load Reconnection (page 438) = Disabled.

MCB Feedback

LBI ID 65
Description
Use this input to indicate whether the Mainsmains circuit breaker is opened or closed.
Image 7.20 MCB Feedback 1

MCB Feedback Negative

LBI ID 66
Description
Use this input to indicate whether the Mainsmains circuit breaker is opened or closed.
This input is logically inverted against LBI MCB FEEDBACK (PAGE 670).

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 1 (page 419).
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 666).
Min Run Power Act 2

LBI ID 53
Description

Min Run Power Act 3

LBI ID 54
Description
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 397) which is used for selecting of the NCB mode (Each / Common).
LBI: P
PCS AC Over Frequency

LBI ID 1244
Description
The status of this LBI is mirrored in group PCS Info (page 579)

PCS AC Over Voltage

LBI ID 1242
Description
PCS AC Overload

LBI ID 1246
Description
PCS AC Under Frequency

LBI ID 1245
Description
PCS AC Under Voltage

LBI ID 1243
Description
PCS Alarm Level 1

LBI ID 1232
Description
PCS Alarm Level 2

LBI ID 1233
Description

PCS Communication Failure

LBI ID 1234
Description
PCS Critical Temperature

LBI ID 1250
Description
PCS DC Over Voltage

LBI ID 1239
Description
PCS DC Overload

LBI ID 1241
Description
PCS DC Under Voltage

LBI ID 1240
Description
PCS Derating

LBI ID 1248
Description

PCS High Temperature

LBI ID 1249
Description
PCS Output Control Mode U-f/P-Q

LBI ID 1109
Description
This logical input is used to choose what BESS Output Control method will be used. By default (log 0) the
U-f option is used.
PCS PQ Mode

LBI ID 1251
Description
PCS Ready To Load

LBI ID 121
Description
Logical binary input signaling that the PCS is ready to be switched into the load.
PCS Ready To Start

LBI ID 1163
Description
Logical binary input for PCS readiness.

PCS Running

LBI ID 1236
Description
PCS Saturated

LBI ID 1247
Description
PCS Start Disabled

LBI ID 1185
Description
This LBI can be used to keep the BESS in idle operation.
PCS Starting

LBI ID 1235
Description
PCS Stopped

LBI ID 1238
Description
PCS Stopping

LBI ID 1237
Description

PCS VF Const Freq

LBI ID 1252
Description
PCS VF Droop

LBI ID 1253
Description
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 194).

Protection Force Disable 1

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
PSU Alarm Level 1

LBI ID 1287
Description
PSU Alarm Level 2

LBI ID 1288
Description
PSU Critical Temperature

LBI ID 1292
Description

PSU High Temperature

LBI ID 1291
Description
PSU Over/Under Voltage

LBI ID 1289
Description
PSU Overload

LBI ID 1290
Description
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 TEST
Remote MAN
Remote AUTO (Lowest Priority)

Remote Ctrl Lock

LBI ID 4
Description
If the input is active, the controller will not accept any actions regarding the system control - e. g. writing
of commands and setpoints change via remote communication interfaces.
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 TEST
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 TEST
Remote MAN

Remote Start/Stop

LBI ID 38
Description
Use this input to start and stop theBESS in AUTO and TEST mode. This information is shared to all
controllers in the same group connected to the master controller via CAN.
Taken action in MINT application (AUTO Mode)

Starts the BESS after #System Start Delay (page 403) if Power
Active
Management (page 398) = Enabled, otherwise it is started immediately.
Stops the BESS after #System Start Delay (page 403) if Power
Inactive
Management (page 398) = Enabled, otherwise it is stopped immediately.
LBI: S
Sd Override

LBI ID 44
Description
If this input is active, all alarms except Emergency Stop (page 820),and E-STOP (page 820) 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 810) 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 170) with protection type Shutdown Override (page 166) are also NOT
suppressed.
IMPORTANT: MISUSE OF THIS INPUT CAN CAUSE DAMAGE TO THE BESS!
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.

SOH Critical Low

LBI ID 1274
Description
SOH Low

LBI ID 1273
Description
Source Not Operable

LBI ID 985
Description
This binary input signalizes not operable BESS. While it is activated the BESS can not be started (BESS
state (page 577) = NotReady).
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 816) 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 65).

Stop Button

LBI ID 190
Description
Binary input has the same function as Stop Button on an External display (page 65).
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

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 401).
IMPORTANT: This binary input can be used only if setpoint #Priority Auto Swap (page 402) =
Disabled.
TX Critical Temperature

LBI ID 1296
Description
TX High Temperature

LBI ID 1295
Description

8.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 690
LBO: B 695
LBO: C 703
LBO: D 705
LBO: E 706
LBO: F 717
LBO: G 718
LBO: H 718
LBO: I 720
LBO: K 720
LBO: L 721
LBO: M 722
LBO: N 724
LBO: O 725
LBO: P 725
LBO: R 726
LBO: S 727
LBO: V 729
For full list of Logical binary outputs go to the chapter Logical binary outputs alphabetically (page 688).

Logical binary outputs alphabetically
LBO: A 690 BESS Active 702 Engines Swapped 708

AIN Switch01 690 BESS Capability C Limit 702 ES Charge Disabled 709
AIN Switch02 690 BESS Capability L Limit 702 ES Discharge Disabled 709
AIN Switch03 690 BESS Healthy 702 ES Run Request 709
AIN Switch04 690 Bus Healthy 703 ES SOC Charge Disabled 709
AIN Switch05 691 LBO: C 703 ES SOC Discharge
AIN Switch06 691 Common Alarm Active Disabled 709
AIN Switch07 691 Level 1 703 ES Start Pulse 710
AIN Switch08 691 Common Alarm Active ES Stop Pulse 710
Level 2 703 ESCB Close/Open 711
AIN Switch09 692
Common Alarm Level 1 703 ESCB ON Coil 712
AIN Switch10 692
Common Alarm Level 2 703 ESCB OFF Coil 713
Alarm Flashing 692
Common Alarm Only 704 ESCB UV Coil 714
AL Maintenance 1 692
Common History Record 704 ESCB Status 715
Common ShutdownMains Event Post VRT 715
ProtectionBreaker Open 704
AL Maintenance 4 693 Event Soft Unload 715
Common Shutdown
Alarm 693 Exercise Timer 1 715
Override 704
Alarm BESS Frequency 693 Exercise Timer 2 716
Common Slow Stop 705
Alarm BESS Overcurrent 693 Exercise Timer 3 716
Common Warning 705
Alarm BESS Voltage 694 Exercise Timer 4 716
Controller HeartBeat Fail
All Available Gen-sets Run 694 Detect 705 Exercise Timer 5 716
Any GCB Closed 694 Exercise Timer 6 717
LBO: D 705
Any Other GCB Closed 694 Daily Batt Cycles Reached 705 External CB Block 717
LBO: B 695 Day/Night 706 LBO: F 717

BCB Button Echo 695 DC Circuit Closed 706 FltRes Button Echo 717
BCB Close/Open 695 Display Fail 706 Forward Synchronization 717
BCB Close/Open Frequency Down 718
LBO: E 706
Secondary 695 ECU 1 Comm Fail 706 Frequency Up 718
BCB OFF Coil 696 ECU 2 Comm Fail 706 LBO: G 718
BCB OFF Coil Secondary 697 ECU 3 Comm Fail 707 GPS Coordinates
BCB ON Coil 698 Detected 718
ECU 4 Comm Fail 707
BCB ON Coil Secondary 699 LBO: H 718
ECU 5 Comm Fail 707
BCB Status 699 Heartbeat 718
ECU 6 Comm Fail 707
BCB UV Coil 699 Horn 719
ECU 7 Comm Fail 707
BCB UV Coil Secondary 701 Horn Flashing 719
ECU 8 Comm Fail 707
BESS In Loadsharing 701 HornRes Button Echo 719
ECU 9 Comm Fail 708
BESS Parallel Oper 702 HW AC Voltage
Energized 708
Measurement Error 719

LBO: I 720 Soft Unload 728
In Synchronism 720 Start Blocked 728
Initialized 720 Start Button Echo 728
LBO: K 720 Starting 728
kWh Pulse 720 Stop Button Echo 728
LBO: L 721 Stopping 729
Load Shedding Stage 1 721 System Ready 729
Load Shedding Stage 2 721 System Reserve OK 729
Load Shedding Stage 3 721
LBO: V 729
Load Shedding Stage 5 722 Vector Shift Active 729
Loaded 722 AVRVoltage Up 730
LBO: M 722 AVRVoltage Down 730
Manual Ready 722
MCB Status 723
Mode AUTO 723
Mode MAN 723
Mode OFF 723
LBO: N 724
NCB Close/Open 724
Not In Auto 724
Not Ready 724
Not Used 724
LBO: O 725
Operational 725
LBO: P 725
PCS Ready To Load 725
PCS Run Request 725
PCS Run Request 726
Peripheral Module Comm
Fail 726
Precharge Relay 726
LBO: R 726
Ready 726
ROCOF 1 Active 726
ROCOF 2 Active 727
ROCOF 3 Active 727
ROCOF 4 Active 727
LBO: S 727
Sd Override 727
Soft Load 727

LBO: A
AIN Switch01

LBO ID 1400
Description
This is an output from the General Analog Input 01 switch function. The behavior of the switch depends
on the adjustment of the setpoints AIN Switch01 On (page 446) and AIN Switch01 Off (page 447).
The value is measured from AIN SWITCH01 (PAGE 733) analog input.
6 back to Logical binary outputs alphabetically
AIN Switch02

LBO ID 1401
Description
AIN Switch03

LBO ID 1402
Description
AIN Switch04

LBO ID 1403
Description

AIN Switch05

LBO ID 1787
Description
AIN Switch06

LBO ID 1788
Description
AIN Switch07

LBO ID 1789
Description
AIN Switch08

LBO ID 1790
Description

AIN Switch09

LBO ID 1791
Description
AIN Switch10

LBO ID 1792
Description
Alarm Flashing

LBO ID 28
Description
This is the flashing alternative of the output ALARM (PAGE 693), i.e. the output flashes with 1 Hz period
while the output Alarm is closed.
AL Maintenance 1

LBO ID 2211
Description
This output is active when alarm Maintenance 1 RunHours (page 860) or Maintenance 1 Interval
(page 859) 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 363) or BESS <f
Protection (page 364) 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 350) or BESS IDMT >A Protection (page 350).

Alarm BESS Voltage

LBO ID 1263
Description
This output is active when at least 1 alarm caused by BESS >>V Protection (page 356), BESS >V
Protection (page 355) or BESS <<V Protection (page 357) is present in the alarmlist.
All Available Gen-sets Run

LBO ID 122
Description
This output is closed when all available BESSs within the Control Group (page 426) are loaded.
Note: BESS is available if Power Management (page 398) = Enabled, Controller Mode (page 576) =
AUTO and there is not present Alarms level 2 (page 818) in the alarmlist.
Any GCB Closed

LBO ID 222
Description
This output is active when a GCB of any controller connected via and/or is closed.
Note: This function works on CAN16 (page 580) - CAN32 (page 581) 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 and/or is closed.
Note: This function works on CAN16 (page 580) - CAN32 (page 581) 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 time adjusted in Setpoint Waiting For Breaker
Feedback (page 396) 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 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.25 BCB Close command
BCB OFF Coil

LBO ID 43
Description
The output is intended for opening of primary master BESS circuit breaker.
The output provides pulses, which length is adjusted by Setpoint Waiting For Breaker Feedback (page
396), when circuit breaker has to open with pause 1 second between each pulse. If the LBI BCB
FEEDBACK (PAGE 648) does not match after second pulse elapses, Alarm Sd BCB Fail To Open (page
837) is issued.
Image 7.26 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 provides pulses, which length is adjusted by Setpoint Waiting For Breaker Feedback (page
396), when circuit breaker has to open with pause 1 second between each pulse. If the LBI BCB
SECONDARY FEEDBACK NEGATIVE (PAGE 651) does not match after second pulse elapses, Alarm Stp
BCB Secondary Fail To Open (page 839) is issued.
Image 7.27 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 provides pulse, which length is adjusted by Setpoint Waiting For Breaker Feedback (page
396), when breaker has to close. The amount of pulses provided by the controller is based on Setpoint
Attempts To Close Breaker (page 395). The pause between attempts is given by Setpoint Delay
Between Closing Attempts (page 396).
When the last attempt elapses and LBI BCB FEEDBACK (PAGE 648) does not match Alarm Sd BCB Fail
To Close (page 836) is issued.
Image 7.28 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 provides pulse, which length is adjusted by Setpoint Waiting For Breaker Feedback (page
396), when breaker has to close. The amount of pulses provided by the controller is based on Setpoint
Attempts To Close Breaker (page 395). The pause between attempts is given by Setpoint Delay
Between Closing Attempts (page 396)
Image 7.29 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 648) and BCB FEEDBACK NEGATIVE (PAGE 649).
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 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 the
duration set by Setpoint Waiting For Breaker Feedback (page 396) 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.30 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 the
duration set by Setpoint Waiting For Breaker Feedback (page 396) when the BCB has to open.
Image 7.31 BCB UV Coil close command
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 192).

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 Active

LBO ID 60
Description
This output is closed after start command and opens when BESS is stopped.
BESS Capability C Limit

LBO ID 1427
Description
This output is closed when the BESS Required PF (page 564) (while BESS Required PF Character
(page 564) = C) or BESS Required Q (page 563) is out of capacitive limits in which is the BESS allowed
to run.
Limits are given by adjusting the CAPABILITY C (PAGE 640).
BESS Capability L Limit

LBO ID 1428
Description
This output is closed when the BESS Required PF (page 564) (while BESS Required PF Character
(page 564) = L) or BESS Required Q (page 563) is out of inductive limits in which is the BESS allowed
to run.
Limits are given by adjusting the CAPABILITY L (PAGE 639).
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.

Bus Healthy

LBO ID 78
Description
This output is closed while Bus parameters (voltage & frequency) are considered as healthy, i. e. within
limits.
Application Mode Setting of Limits

BESS >>V (page 335) BESS >f (page 338)
MINT BESS >V (page 334) BESS <f (page 339)
BESS <V (page 336)
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 804) 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 818) 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 804) 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 818) 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 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 817) occurs.
Note: When any History Record alarm is activated the history record is logged into history.
Common ShutdownMains ProtectionBreaker Open

LBO ID 4
Description
This output is closed when there is at least one active alarm of type Shutdown (page 820)Protection
types (page 165)Protection types (page 165) present in the alarmlist.
Note: When any MainsShutdown 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 166)
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 683).

Common Slow Stop

LBO ID 5
Description
This output is closed when there is at least one alarm of type Slow Stop (page 835) 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
421) 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.
Note: When any Stp alarm is activated LBO System Start/Stop is immediately set to 0 and MGCB
breaker is opened according to the Load Transfer settings.
Common Warning

LBO ID 3
Description
This output is closed when there is at least one alarm of type Warning (page 806) present in the
alarmlist.
Controller HeartBeat Fail Detect

LBO ID 125
Description
XYZ.
LBO: D
Daily Batt Cycles Reached

LBO ID 2704
Description
This output is active always when the number of daily battery cycles is reached.

Day/Night

LBO ID 5931
Description
This LBO is active during the day.(If the current time is between Sunrise Time and Sunset Time)
DC Circuit Closed

LBO ID 2784
Description
This LBO is a miror of the LBI PRECHARGE FINISHED (PAGE 678). It is active all the time when DC circuit of
the BESS is closed.
Display Fail

LBO ID 2223
Description
This output indicates controller display failure.
LBO: E
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
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.
Image 7.32 Running
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 402) if it is setup to Run Hours Equal.

ES Charge Disabled

LBO ID 5554
Description
This logical output is activated if charging should be disabled because of too high SOC.
ES Discharge Disabled

LBO ID 5555
Description
This logical output is activated if discharging should be disabled because of too low SOC.
ES Run Request

LBO ID 2763
Description
This output is used to send "start" request to the Energy Storage.
ES 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.
ES 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.

ES Start Pulse

LBO ID 2764
Description
One second pulse is issued at this output when the Energy Storage enters starting phase.
ES Stop Pulse

LBO ID 2765
Description
One second pulse is issued at this output when the Energy Storage is required to stop - disconnect the
battery and enter stand-by mode.

ESCB Close/Open

LBO ID 2767
Description
The output controls the ES circuit breaker. Its state represents the breaker position requested by the
controller..
Image 7.33 ES Close command

ESCB ON Coil

LBO ID 2768
Description
The output is intended for control of close coil of ES circuit breaker.
The output gives at least 2 second pulse in the moment the breaker has to be closed.The output provides
pulse, which length is adjusted by Setpoint Waiting For Breaker Feedback (page 396), when breaker
has to close. The amount of pulses provided by the controller is based on Setpoint Attempts To Close
Breaker (page 395). The pause between attempts is given by Setpoint Delay Between Closing
Attempts (page 396).
When the last attempt elapses and LBI ESCB FEEDBACK (PAGE 655) does not match Alarm Sd ESCB
Fail To Close (page 822) is issued.
Image 7.34 ES ON Coil close command

ESCB OFF Coil

LBO ID 2769
Description
The output is intended for opening of ES 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 ESCB FEEDBACK (PAGE 655) does not match after second pulse elapses, Alarm
Sd ESCB Fail To Open (page 822) is issued.
Image 7.35 ES OFF Coil command

ESCB UV Coil

LBO ID 2770
Description
The output is intended for control of undervoltage coil of ES circuit breaker.
The output is closed after the BESShas been started..ES 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 the duration set by Setpoint Waiting For Breaker Feedback (page 396) when the ES has to
open.
The output is closed again and remains closed while the ES voltage and frequency are within limits if the
Running phase follows after the opening of the ES (e.g. in MAN). The output remains open if the Cooling
phase follows after the opening of the ES.
Image 7.36 ES UV Coil close command

ESCB Status

LBO ID 2771
Description
This output indicates the ES circuit breaker position as it is internally considered by the controller.
The position is based on ESCB FEEDBACK (PAGE 655) and ESCB FEEDBACK NEGATIVE (PAGE 656).
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 ES circuit breaker position according to
feedbacks.
Feedbacks do not match each other - output indicates last position when feedbacks matched.
Event Post VRT

LBO ID 1438
Description
This output is closed when Post VRT Ramp (page 433) is in use.
Event Soft Unload

LBO ID 1437
Description
This output is closed when Soft Unload Ramp (page 434) 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 460) 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.
External CB Block

LBO ID 2761
Description
This logical output makes 200 ms pulse always when the CU is going to close the BCB to the deadbus.
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 65).

Fault Reset command is received via communication line
LBI FAULT RESET BUTTON (PAGE 657) 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 699) closes.

Frequency Down

LBO ID 57
Description
This output together with the complementary output FREQUENCY UP (PAGE 718) 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 718) are designed for
frequency and power control of the BESS where the BESS inverter regulatorspeed governor 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..
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 804) is activated and stays closed until:
Fault reset is pressed
Horn reset is pressed

Horn Timeout (page 292) elapses
Horn Flashing

LBO ID 29
Description
This is the flashing alternative of the output HORN (PAGE 719), 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.
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 551) between BESS and Bus Voltage is within range given by Phase Window
(page 392) for time longer than Dwell Time (page 392). Required if Synchronization Type
(page 390) = PhaseMatch.
Slip Frequency (page 551) between between BESS and Bus Frequency is withing range given
by Slip Frequency Window (page 393) for time longer than Dwell Time (page 392). Required if
Synchronization Type (page 390) = SlipSynchr.
Voltage difference between BESS and Bus voltage in all phases must be lower or equal to
Voltage Window (page 391) for time longer than Dwell Time (page 392). 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.
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 Shedding Stage 1

LBO ID 51
Description
This is an output of Load Shedding (page 142).
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 142).

LBO ID 52
Description
The load disconnected by LBO LOAD SHEDDING STAGE 1 (PAGE 721) is the least essential load.

LBO ID 53
Description

LBO ID 452
Description

LBO ID 453
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.
LBO: M
Manual Ready

LBO ID 1258
Description
This output is active when Controller Mode (page 576) = MAN and the BESS is stopped and it is
possible to start it. i.e. no red alarm is activated or SD OVERRIDE (PAGE 683) is active (Output READY
(PAGE 726) is active).

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 670) and MCB FEEDBACK NEGATIVE (PAGE 671).
In case that only MCB FEEDBACK (PAGE 670) is used, this output mirrors the input.
In case that both MCB FEEDBACK (PAGE 670) and MCB FEEDBACK NEGATIVE (PAGE 671) are
used and
Feedback match - output indicates MCB position according to feedbacks.
Feedback do not match - output indicates last position when feedbacks matched.
Mode AUTO

LBO ID 19
Description
This output is active whenever Controller Mode (page 576) = AUTO, i.e. when LBO NOT IN AUTO (PAGE
724) is opened.
Mode MAN

LBO ID 18
Description
This output is active whenever Controller Mode (page 576) = MAN.
Mode OFF

LBO ID 17
Description
This output is active whenever Controller Mode (page 576) = 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 576) != AUTO, i.e. when LBO MODE AUTO
(PAGE 723) 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:
Controller Mode (page 576) = OFF
LBI START BLOCKING (PAGE 684) 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.
LBO: P
PCS 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 PCS READY TO LOAD (PAGE 676) is closed or PCS Ready To Load TO (page 324) elapsed
if the LBI is not configured
Minimal Stabilization Time (page 325) 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
PCS Run Request

LBO ID 2268
Description
This output is closed when PCS Ready To Start TO (page 324) elapses and is opened when inverter is
turned off.

PCS Run Request

LBO ID 2268
Description
This output is closed when PCS Ready To Start TO (page 324) elapses and is opened when inverter is
turned off.
Peripheral Module Comm Fail

LBO ID 115
Description
This output is closed when there is no communication with at least one configured peripheral module.
Precharge Relay

LBO ID 2782
Description
This LBO relates to the BESS start sequence decribed in BESS Precharge Types (page 194).
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 678) gets
active. Both signals are mandatory for correct operation.
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 818) present in the alarmlist
LBI SD OVERRIDE (PAGE 683) is opened
ROCOF 1 Active

LBO ID 1005
Description
This output is closed for 3 seconds when ROCOF1 Protection (page 369) 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 369) 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 683) input is active and opened if SD OVERRIDE (PAGE 683)
input is inactive. This output is usually used to send information about SD OVERRIDE (PAGE 683) input into
ECU.
Soft Load

LBO ID 71
Description
This output is closed when BCB closes and BESS is being soft loaded via Load Ramp (page 382). Later
change of BESS P (page 541) 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 434).
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 684) 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 Precharging TO (page 323) period and opens after starting
phase is finished or when Sd Start Fail (page 834) 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.
Note: Output is also closed if the engine begins to rotate spontaneously.
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 560) is above the Minimal
Running Nominal Power (page 561)
System Reserve OK

LBO ID 87
Description
This output is closed when Actual Reserve (page 558) is higher than the Actual Reserve (page 558).
LBO: V
Vector Shift Active

LBO ID 93
Description
This output is closed for 3 seconds when Vector Shift Protection (page 368) is activated.

AVRVoltage Up

LBO ID 54
Description
This output together with the complementary output AVRVOLTAGE DOWN (PAGE 730) are designed for
voltage and power factor control of the BESS, where the BESS inverter regulatorAVR does not support
analogue control.
AVRVoltage Down

LBO ID 55
Description
This output together with the complementary output AVRVOLTAGE UP (PAGE 730) are designed for
voltage and power factor control of the BESS, where the BESS inverter regulatorAVR does not support
analogue control.

8.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: A 733
LAI: D 735
LAI: E 735
LAI: H 737
LAI: L 738
LAI: P 738
LAI: Q 739
For full list of Logical analog inputs go to the chapter Logical analog inputs alphabetically (page 732).

Logical analog inputs alphabetically
LAI: A 733 PCS Current Meas 738

AIN Switch01 733 PCS P Request 738
AIN Switch02 733 PCS Q Request 738
AIN Switch03 733 PCS Voltage Meas 738
AIN Switch04 733 PF Control: ANEXT Base
AIN Switch05 733 PF 739
AIN Switch06 734 LAI: Q 739
AIN Switch07 734 Q Control: ANEXT Base Q 739
AIN Switch08 734 6 back to Controller objects

AIN Switch09 734
AIN Switch10 734
LAI: D 735
Dynamic Spinning
Reserve 735
Dynamic Spinning
Reserve Offset 735
LAI: E 735
ES Charge kWh 735
ES Charging Cycles 735
ES Current 735
ES Discharge kWh 736
ES kWh Capacity 736
ES Max Charging Current 736
ES Max Discharging
Current 736
ES SOC 736
ES Temperature 737
ES Voltage 737
ES Voltage Meas 737
LAI: H 737
HLC U-f Control: Q
Request 737
HLC U-f Control: P
Request 737
LAI: L 738
Load Control ANEXT:
Local Baseload 738
LAI: P 738

LAI: A
AIN Switch01

LAI ID 209
Description
LAI is representing value of AIN Switch 1.
6 back to Logical analog inputs alphabetically
AIN Switch02

LAI ID 210
Description
AIN Switch03

LAI ID 211
Description
AIN Switch04

LAI ID 212
Description
AIN Switch05

LAI ID 278
Description

AIN Switch06

LAI ID 279
Description
AIN Switch07

LAI ID 280
Description
AIN Switch08

LAI ID 281
Description
AIN Switch09

LAI ID 282
Description
AIN Switch10

LAI ID 283
Description

LAI: D

LAI ID 192
Description
This LAI is used as source of the value Dynamic Spinning Reserve (page 558).
Dynamic Spinning Reserve Offset

LAI ID 233
Description
This LAI is used as source of the value Dynamic Spinning Reserve Offset (page 559).
LAI: E
ES 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.
ES Charging Cycles

LAI ID 428
Description
This analog input is used as source for the statistic value BESS Charging Cycles (page 569) and for
the function BESS Charging/Discharging Control (page 191).
ES Current

LAI ID 535
Description
This LAI is used for reading of the Energy Storage DC current from the BMS.

ES 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.
ES kWh Capacity

LAI ID 370
Description
Capacity of the Energy Storage.
ES Max Charging Current

LAI ID 536
Description
This LAI is used for limiting charging of energy storage.
ES Max Discharging Current

LAI ID 537
Description
This LAI is used for limiting discharging of energy storage.
ES SOC

LAI ID 368
Description
This LAI is used to monitor actual state of charge of the BESS.

ES Temperature

LAI ID 371
Description
This LAI is used as input for temperature of the BESS.
ES Voltage

LAI ID 534
Description
This LAI is used for reading of the Energy Storage DC voltage from the BMS.
ES Voltage Meas

LAI ID 527
Description
This LAI is used for measurement of Energy Storage DC voltage.
LAI: H
HLC U-f Control: Q Request

LAI ID 567
Description
This logical analog input is used as relative (-100 .. 100 %) P/f request related to the BESSNominal
power (page 280) for U-f control mode.
HLC U-f Control: P Request

LAI ID 568
Description
This logical analog input is used as relative (-100 .. 100 %) Q/V request related to the BESSNominal
power (page 280) for U-f control mode.

LAI: L
Load Control ANEXT: Local Baseload

LAI ID 405
Description
This LAI is source of requested local baseload when Local Baseload Source = Analog External Value or
when HLC Control Mode (page 318) = P-Q.
LAI: P
PCS Current Meas

LAI ID 530
Description
This LAI is used for measurement of Power Conversion System DC current.
PCS P Request

LAI ID 420
Description
LAI is used for adjusting BESS Power Request while Charging / Discarding process.
PCS Q Request

LAI ID 429
Description
LAI is used for adjusting BESS Reactive Power Request while Charging / Discarding process.
PCS Voltage Meas

LAI ID 528
Description
This LAI is used for measurement of Power Conversion System DC voltage.

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 276) = Analog
External Value or when HLC Control Mode (page 318) = P-Q.
The Base PF is active if
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.
LAI: Q
Q Control: ANEXT Base Q

LAI ID 171
Description
This LAI is a source value for control of the Power Factor if PF/Q Request Source (page 276) = Analog
External Value or when HLC Control Mode (page 318) = P-Q.
The Base Q is active if
Note: If all setpoints are adjusted as mentioned above and Breaker state (page 577) = ParalOper, and
at least one gen-set is connected to the bus, but this LAI is not configured, alarm Wrn Q Control Fail

8.1.9 Fixed Protection States
List of Fixed Protection States
Fixed Protections States 1 741

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 806)
2. Not Used
3. Not Used
4. Sd PCS Short Circuit (page 833)
5. Sd PCS IDMT >A (page 832)
6. Sd ESCB Fail (page 823)
7. Sd ESCB Fail To Open (page 822)
8. Sd ESCB Fail To Close (page 822)
9. Sd ESCB Not Closed (page 824)
10. Not Used
11. Not Used
12. Not Used
13. Not Used
14. Not Used
15. Not Used
16. Wrn Battery Undervoltage (page 806)
17. Wrn Battery Overvoltage (page 806)
18. ALI BCB Closing Is Blocked (page 815)
19. Not Used
20. Not Used
21. Wrn Energy Storage Not Ready (page 808)
22. Sd BESS Not Operable (page 821)
23. Wrn Override All Sd (page 810)
24. Not Used
25. Not Used
26. Not Used
27. Not Used
6 back to Fixed Protection States


Comm object 20745
Description
1. Sd BESS >V L1-N (page 827)
4. Sd BESS >V L1-L2 (page 827)
7. Sd BESS >>V L1-N (page 825)
8. Sd Bus >>V L2-N (page 825)
9. Sd BESS >>V L3-N (page 826)
10. WRN BESS >>V L1-L2 (page 826)
13. Sd BESS <V L1-N (page 828)
16. Sd BESS <V L1-L2 (page 829)
19. Sd BESS V Unbalance Ph-N (page 830)
20. Sd BESS V Unbalance Ph-Ph (page 831)
21. Sd BESS >f (page 830)
22. Sd BESS <f (page 830)
23. Not Used
24. Not Used
25. Sd IDMT Overload (page 832)
26. PVBO Short Circuit (page 833)
27. Sd IDMT BESS >A (page 832)
28. Sd IDMT Earth Fault Current (page 831)
29. Sd BESS Current Unbalance (page 831)
30. ALI BESS Ph Rotation Opposite (page 816)


Comm object 20746
Description
1. Emergency Stop (page 820)
2. ALI Daily Battery Cycles Reached (page 815)
3. Not used
4. Not used
5. Wrn Stop Fail (page 812)
6. Wrn SOC Low Alarm (page 812)
7. Wrn SOC High Alarm (page 812)
8. Sd SOC Critical Low (page 834)
9. Sd SOC Critical High (page 834)
10. Not used
11. Wrn SpeedFrequency Regulation Limit (page 810)
12. Wrn Voltage Regulation Limit (page 813)
13. Stp Synchronization Fail (page 840)
14. Not used
15. Stp BCB Fail (page 835)
16. Stp BCB Secondary Fail (page 838)
17. Sd NCB Fail (page 832)
18. Stp BCB Secondary Fail To Open (page 839)
19. Stp BCB Secondary Fail To Close (page 838)
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. Bus >V L1-N (page 843)
4. Bus >V L1-L2 (page 844)
5. Bus >V L2-L3 (page 845)
6. Bus >V L3-L1 (page 846)
7. Bus >>V L1-N (page 846)
8. Bus >>V L2-N (page 847)
9. Bus >>V L3-N (page 847)
10. Bus >>V L1-L2 (page 848)
11. Bus >>V L2-L3 (page 849)
12. Bus >>V L3-L1 (page 849)
13. Bus <V L1-N (page 850)
14. Bus <V L2-N (page 850)
15. Bus <V L3-N (page 851)
16. Bus <V L1-L2 (page 852)
17. Bus <V L2-L3 (page 852)
18. Bus <V L3-L1 (page 853)
19. Bus <<V L1-N (page 853)
20. Bus <<V L2-N (page 854)
21. Bus <<V L3-N (page 855)
22. Bus <<V L1-L2 (page 855)
23. Bus <<V L2-L3 (page 856)
24. Bus <<V L3-L1 (page 856)
25. Bus V Unbalance Ph-Ph (page 859)
26. Bus V Unbalance Ph-N (page 858)


Comm object 20748
Description
1. Bus >f (page 857)
2. Not Used
3. Bus <f (page 858)
4. Not Used
5. Reserved
6. ALI Bus Ph Rotation Opposite (page 814)
7. Not Used
8. Stp Bus Meas Error (page 835)
9. Hst BESS Anti Islanding (page 820)
10. Not Used
11. Not Used
12. Not Used
13. Not Used
14. WrnVRT Protection Trip (page 883)
15. Not Used
16. Not Used
17. Wrn Fence 1 Alarm (page 809)
18. Sd Fence 1 Alarm (page 825)
19. Not Used
20. Wrn Fence 2 Alarm (page 809)
21. Fence 1 Alarm
22. Sd Fence 2 Alarm (page 825)
23. Not Used
24. Fence 2 Alarm
25. Wrn ES >V (page 807)
26. Sd ES >>V (page 824)
27. Wrn ES <V (page 808)
28. Sd ES <<V (page 824)
29. Wrn PCS >V (page 810)
30. Sd PCS >>V (page 833)
31. Wrn PCS <V (page 811)
32. Sd PCS <<V (page 833)

8.1.10 User Protection States
List of User Protection States
User Protections States 1 747

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.0.0 5Related applications MINT

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

8.1.11 PLC
List of PLC blocks
Group: Logical functions 751
OR/AND 751
XOR/RS 753
Group: Comparators 754
Comp Delay 754
Comp Hyst 755
Comp Win 756
Group: Time functions 757
Delay 757
Timer 759
Group: Math operations 761
Interpolation 761
AxB/C±D 762
Math Fc. 763
Group: Regulators 765
PID 765
Up/Down Ctrl Block 769
Group: Ramp functions 772
Inc/Dec 772
LowPassFlt 773
Mov Avg 774
Ramp 775
Up/Down 776
Group: Other functions 777
Analog Switch 777
Analog Switch 8 778
Bit Sum 16 780
Circuit Breaker 782
Convert 785
Counter 787
Comp. 4 788
Comp. 16 789
Decomp. 4 790
Decomp. 16 791
Differ 793
Heartbeat 794

Hold 796
PF Conv 797
Poly Appx 799
PWR Calc 800
Validator 803

Group: Logical functions
OR/AND
PLC group Logical functions
Related FW 1.0.0
Related applications MINT
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.37 Configuration of OR/AND block
6 back to List of PLC blocks

XOR/RS
PLC group Logical functions
Related FW 1.0.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.38 Configuration of XOR/RS block
Group: Comparators
Comp Delay
PLC group Comparators

Related FW 1.0.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.39 Configuration of Comp Delay block
Comp Hyst

Related FW 1.0.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.40 Different On and Off levels

Image 7.41 Configuration of Comp Hyst block
Comp Win

Related FW 1.0.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.42 Principle of delay

Image 7.43 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.0.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.44 Delay modes principles
Image 7.45 Configuration of Delay block

Timer
PLC group Time functions
Related FW 1.0.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 622) to
PLC Resource 16 (page 625)>
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.46 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.0.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.47 Principle of Interpolation
Image 7.48 Configuration of Interpolation block
AxB/C±D
PLC group
Related FW 1.0.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.49 Configuration of Math AxB/C±D block
Math Fc.
PLC group
Related FW 1.0.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.50 Configuration of Math Fc. block
Group: Regulators
PID
PLC group
Related FW 1.0.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.51 Configuration of PID block
Up/Down Ctrl Block
PLC group
Related FW 1.0.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.52 Configuration of Up/Down Ctrl Block
Group: Ramp functions
Inc/Dec
PLC group
Related FW 1.0.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.53 Configuration of Inc/Dec block
LowPassFlt
PLC group
Related FW 1.0.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.54 Configuration of LowPassFlt block
Mov Avg
PLC group
Related FW 1.0.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.55 Configuration of Moving Average block
Ramp
PLC group
Related FW 1.0.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.56 Configuration of Ramp block
Up/Down
PLC group
Related FW 1.0.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.57 Configuration of Up/Down block
Group: Other functions
Analog Switch
PLC group Others

Related FW 1.0.0
PLC Block ID 5
Inputs

32 32
Input 1 Analog No -2 .. 2 Input value 1
32 32
Input SW Binary No 0/1 Switching between Input value 1 and 2
Outputs

32 32
Output Analog No -2 .. 2 Switch output
Description
The block is switching Input 1 and Input 2 based on value of Input SW (0 = Input1, 1 = Input2). The
Output has resolution and dimension based on setting of the block.
Image 7.58 Configuration of Analog Switch block
Analog Switch 8
PLC group Others
Related FW 1.0.0
PLC Block ID 45
Inputs

32 32
32 32
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.59 Configuration of Analog Switch 8 block
Bit Sum 16
PLC group Others
Related FW 1.0.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.60 Configuration of Bit Sum 16 block
Circuit Breaker
PLC group Others
Related FW 1.0.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.61 Configuration of Circuit Breaker block
« back to List of PLC blocks

Convert
PLC group Others

Related FW 1.0.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.62 Configuration of Convert block

Counter
PLC group Others

Related FW 1.0.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 622) to
PLC Resource 16 (page 625)>
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.63 Configuration of the Counter block

Comp. 4
PLC group Others
Related FW 1.0.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.64 Configuration of Comp. 4 block

Comp. 16
PLC group Others
Related FW 1.0.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.65 Configuration of Comp. 16 block
Decomp. 4
PLC group Others
Related FW 1.0.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.66 Configuration of Decomp. 4 block
Decomp. 16
PLC group Others
Related FW 1.0.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.67 Configuration of Decomp. 16 block

Differ
PLC group Others

Related FW 1.0.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.68 Configuration of the Differ block

Heartbeat
PLC group Others
Related FW 1.0.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.69 Configuration of Heartbeat block

Hold
PLC group Others

Related FW 1.0.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.70 Principle of the Hold modes

Image 7.71 Configuration of the Hold block
PF Conv
PLC group Others
Related FW 1.0.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.72 Power factor formats ranges

Image 7.73 Configuration of PfConv block
Poly Appx
PLC group Others
Related FW 1.0.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.74 Configuration of Polynomial Approximation block
PWR Calc
PLC group Others
Related FW 1.0.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.75 Configuration of PWR Calc block

Validator
PLC group Others

Related FW 1.0.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.76 Configuration of Validator block

8.2 Alarms
What alarms are:
The controller evaluates two levels of alarms. For more information see Alarm Management on page 106.
8.2.1 Alarm levels in the controller

8.2.4 Other alarms 840
8.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 806 ALI Bus Ph L2 Inverted 814

Wrn Battery Overvoltage 806 ALI Bus Ph L3 Inverted 814
Wrn Battery Undervoltage 806 ALI Bus Ph Rotation
Wrn Brute Force Opposite 814
Protection Active 806 ALI Daily Battery Cycles
Wrn DC Measurement Reached 815
Error 807 ALI BCB Closing Is
Wrn Default Password 807 Blocked 815
Wrn Discharging - System ALI BESS Ph L1 Inverted 815
Safety 807 ALI BESS Ph L2 Inverted 816
Wrn ES >V 807 ALI BESS Ph L3 Inverted 816
Wrn ES <V 808 ALI BESS Ph Rotation
Wrn Energy Storage Not Opposite 816
Ready 808 ALI Start Blocking 816
Wrn Event e-mail 1 Fail 808 ALI Wrong Power Format 817
Wrn Event e-mail 2 Fail 808 Alarm List + History
Wrn Event e-mail 3 Fail 809 Indication 817
Wrn Event e-mail 4 Fail 809 History Record Only 817
Wrn SpeedFrequency Hst ROCOF 1 817

Regulation Limit 810 Hst ROCOF2 817
Wrn Override All Sd 810 Hst ROCOF3 817
Wrn Password reset e-mail Hst ROCOF4 818
addr is not set 810 Hst Vector Shift 818
Wrn PCS >V 810 6 back to Alarms
Wrn PCS <V 811
Wrn Q Control Fail 811
Wrn RTC Battery Flat 811
Wrn Safety mode 811
Wrn SOC High Alarm 812
Wrn SOC Low Alarm 812
Wrn Stop Fail 812
Wrn Unsupported PMS
Mode 813
Wrn Voltage Regulation
Limit 813
Wrong PLC Configuration 813
Alarm List Indication 814
ALI Bus Ph L1 Inverted 814

Warning
Wrn Battery Overvoltage
Alarm Type Warning (page 165)

Alarmlist message Wrn Battery Overvoltage
Alarm evaluated All the time
Alarm ID 941
This alarm is activated when Battery Voltage (page 566) is over Power
Supply >V (page 294) for period longer than Power Supply <> Delay (page
Description
294).
This alarm has FPS - FIXED PROTECTIONS STATES 1 (PAGE 741)
6 back to List of alarms level 1
Wrn Battery Undervoltage

Alarmlist message Wrn Battery Undervoltage
Alarm ID 940
This alarm is activated when Battery Voltage (page 566) is bellow Power
Supply <V (page 294) for period longer than Power Supply <> Delay (page
Description
294).
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 186) rules.
This alarm has FPS - FIXED PROTECTIONS STATES 1 (PAGE 741).
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 DC Measurement Error

Alarmlist message Wrn DC Measurement Error
Alarm ID 1654
This alarm is activated when controller expects to measure DC voltage but
Description
values are 0.
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 Discharging - System Safety

Alarmlist message Wrn Discharging - System Safety
Alarm ID 2242
The alarm is activated when Controller is in Load Sharing, LBI ES
DISCHARGE ENABLE (PAGE 653) = 0, the BESS is forced to discharge and the
Description
output power exceeds the level given by the Setpoint System Safety
Discharging Level (page 320).
Wrn ES >V

Alarmlist message Wrn ES >V
Alarm ID 1657
This alarm is activated when Energy Storage Volts over ES >V (page 340)
Description
for period longer than ES >V Delay (page 341)

Note: This alarm has FPS - Fixed Protections States 5 (page 745)
Wrn ES <V

Alarmlist message Wrn ES <V
Alarm ID 1659
This alarm is activated when Energy Storage Volts is bellow ES <V (page
Description 342) for period longer than ES < VDelay (page 342)
Wrn Energy Storage Not Ready

Alarmlist message Wrn Energy Storage Not Ready
Alarm ID 1651
Description This alarm is activated when LBI ES READY TO START (PAGE 654) is 0.
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 521) and email
wasn’t send.

Alarm ID 735
Description The alarm indicates that there was a request to send an event email to email

address which is adjusted by setpoint E-mail Address 2 (page 521) and email
wasn’t send.

Alarm ID 736
wasn’t send.

Alarm ID 737
wasn’t send.
Wrn Fence 1 Alarm
Alarm Type WRN
Alarmlist message Wrn Fence 1 Alarm
Alarm evaluated Only if Geo-Fencing (page 477) != Disabled
This alarm evaluates the GPS position of BESS.
Description

Wrn Fence 2 Alarm
Alarm Type WRN
Alarmlist message Wrn Fence 2 Alarm
Description

Wrn SpeedFrequency Regulation Limit

Alarmlist message Wrn SpeedFrequency Regulation Limit
Alarm evaluated While BESS is running
Alarm ID 151
This alarm is activated when Frequency Regulator Output (page 562) stays
close to Frequency Gov Low Limit (page 376) or Frequency Gov Hi Lim
Description (page 376) for at least 2 seconds and will remain active as long as the cause is
present.
Wrn Override All Sd

Alarmlist message Override All Sd
Alarm evaluated Only if LBI SD OVERRIDE (PAGE 683) is configured
Alarm ID 674
This alarm is activated when LBI SD OVERRIDE (PAGE 683) 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 PCS >V

Alarmlist message Wrn PCS >V
Alarm ID 2231
This alarm is activated when PCS (Power Conversion System)Volts is over
Description
PCS >V (page 346) for period longer than PCS >V Delay (page 346)

Wrn PCS <V

Alarmlist message Wrn PCS <V
Alarm ID 2233
This alarm is activated when PCS (Power Conversion System)Volts is
bellow PCS <V (page 347) for period longer than PCS <V Delay (page
Description 348)
Wrn Q Control Fail

Alarmlist message Wrn Q Control Fail
Only when PF/Q Request Source (page 276) = Analog External Value, HLC
Alarm evaluated
Control Mode (page 318) and Breaker state (page 577) = ParalOper
Alarm ID 1049
This alarm is activated when least one gen-set is connected to the bus, but LAI
Description
Q CONTROL: ANEXT BASE Q (PAGE 739) is not configured.
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 66).
Wrn Safety mode

Alarmlist message Wrn Safety Mode
Alarm evaluated Before start of application

Alarm ID 2331
This alarm is activated when the necessary LAI and safety setpoints is not
configured correctly.
Safety Mode is activated when the BMS connection has been severed or the
values that are read through LAIs are invalid.
LAI ES MAX CHARGING CURRENT (PAGE 736) or LAI ES MAX
Description DISCHARGING CURRENT (PAGE 736) reads an invalid value - BMS
connection is lost
LAI ES MAX CHARGING CURRENT (PAGE 736) < Setpoint ES Safety
Charging Current (page 319) or
LAI ES MAX DISCHARGING CURRENT (PAGE 736) < Setpoint ES Safety
Discharging Current (page 320)
Wrn SOC High Alarm

Alarmlist message Wrn SOC High Alarm
Alarm ID 1595
This alarm is activated by ES >SOC (page 373).
Description
Wrn SOC Low Alarm

Alarmlist message Wrn SOC Low Alarm
Alarm ID 1594
This alarm is activated by ES <SOC (page 373).
Description
Wrn Stop Fail

Alarmlist
Wrn Stop Fail
message
Alarm
Only when BESS should be stopped
evaluated
Related MINT

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 Unsupported PMS Mode

Alarmlist message Wrn Unsupported PMS Mode
Alarm ID 1044
This alarm is active if setpoint #Power Management Mode (page 400) = 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 564) stays close
to Voltage Regulator Low Limit (page 385) or Voltage Regulator High
Description Limit (page 385) 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 152) 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 List Indication
ALI Bus Ph L1 Inverted
Alarm Type Alarm List Indication (page 165)

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 289) is set to Clockwise and actual rotation is
Description
Counterclockwise, on the Bus side.

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 323) is reached.
ALI BCB Closing Is Blocked

Alarmlist message ALI BCB Closing Is Blocked
Alarm ID 1445
Alarm is active in case the BCB breaker is blocked due to some of the BESS
protections being disabled:
BESS <f Protection (page 364)
BESS >f Protection (page 363)
Description
BESS <<V Protection (page 357)
BESS >V Protection (page 355) and BESS >>V Protection (page
356)
Short Circuit Protection (page 350)
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
This alarm is activated when controller detects wrong phase rotation, e.g.
Phase Rotation (page 289) is set to Clockwise and actual rotation is
Description
Counterclockwise, on the BESS side.
ALI Start Blocking

Alarmlist
ALI Start Blocking
message
Alarm evaluated Only if LBI START BLOCKING (PAGE 684) is configured
Related
MINT
applications
Alarm ID 56
This alarm is active if LBI START BLOCKING (PAGE 684) 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 163) on any controller which is connected via CAN2 (page 19) or
Communication peripherals (page 19).
Alarm List + History Indication
History Record Only
Hst ROCOF 1
Alarm Type History Record Only (page 165)

Alarmlist message Hst ROCOF 1
Only if ROCOF1 Protection (page 369) = Enabled or (ROCOF1 Protection
Alarm evaluated
(page 369) = Parallel Only and MCB FEEDBACK (PAGE 670) is active)
Alarm ID 851
This alarm is activated by ROCOF1 Protection (page 369).
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 370)
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 368) = Enabled or (Vector Shift
Alarm evaluated Protection (page 368) = Parallel Only and MCB FEEDBACK (PAGE 670) is
closed)
Alarm ID 850
Description This alarm is activated when Vector shift (page 144) is detected.
8.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 820 Sd BESS Current

Emergency Stop 820 Unbalance 831
E-STOP 820 Sd IDMT PCS Overload
Hst BESS Anti Islanding 820 Protection 831
Sd DC Circuit Close Fail 821 Sd IDMT Earth Fault

Current 831
Sd BESS Not Operable 821
Sd IDMT BESS >A 832
ES Configuration Incorrect 821
Sd IDMT Overload 832
Sd ESCB Fail To Close 822
Sd NCB Fail 832
Sd ESCB Fail To Open 822
Sd PCS IDMT >A 832
Sd ESCB Fail 823
Sd PCS >>V 833
Sd ESCB Not Closed 824
Sd PCS Short Circuit 833
Sd ES >>V 824
Sd PCS <<V 833
Sd ES <<V 824
PVBO Short Circuit 833
Sd BESS >>V L1-N 825
Sd SOC Critical High 834
Sd Bus >>V L2-N 825
Sd SOC Critical Low 834
Sd BESS >>V L3-N 826
Sd Start Fail 834
WRN BESS >>V L1-L2 826
Slow Stop 835
Stp Bus Meas Error 835
Stp BCB Fail 835
Sd BESS >V L1-N 827
Sd BCB Fail To Close 836
Sd BESS >V L2-N 827
Sd BCB Fail To Open 837
Sd BESS >V L3-N 827
Stp BCB Secondary Fail 838
Sd BESS >V L1-L2 827
Stp BCB Secondary Fail
To Close 838
Sd BESS <V L1-N 828 To Open 839
Sd BESS <V L2-N 828 Stp Synchronization Fail 840
Sd BESS <V L3-N 829 6 back to Alarms
Sd BESS <V L1-L2 829
Sd BESS >f 830
Sd BESS <f 830
Sd BESS V Unbalance Ph-
N 830
Sd BESS V Unbalance Ph-
Ph 831

Shutdown
Emergency Stop
Alarm Type Shutdown (page 166)Shutdown (page 166)

Alarmlist message Emergency Stop
Alarm evaluated Only if EMERGENCY STOP (PAGE 653) is configured
Alarm ID 44
This alarm is activated by LBI EMERGENCY STOP (PAGE 653). 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 653) 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 166)

Alarmlist message E-STOP
Alarm ID 853
Alarm is activated when dedicated E-STOP (page 122) 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 678) gets inactive (DC circuit is
opened) unexpectedly.
Sd BESS Not Operable

Alarmlist message Sd BESS Not Operable
Alarm evaluated Only if LBI SOURCE NOT OPERABLE (PAGE 684) is configured
Alarm ID 1097
This alarm is activated/deactivated by closing/opening of LBI SOURCE NOT
Description OPERABLE (PAGE 684).
ES Configuration Incorrect
Alarm Type Sd
Alarmlist message ES Configuration Incorrect
Alarm evaluated Before start of application
Alarm ID 2226
This alarm will be issued if one or more of the related IOs is not configured.
User should configure all the necessary IOs and safety setpoints before the
Energy Storage can be fully utilized.
LBI ES Charge Enable
LBI ES Discharge Enable
Description LAI DC ES Voltage Meas

LAI DC Converter Voltage Meas
LAI DC Converter Current Meas
LAI ES Max Charging Current
LAI ES Max Discharging Current
LAI Energy Storage SOC

Sd ESCB Fail To Close

Alarmlist
Sd ESCB Fail To Close
message
Alarm
Only if ESCB Type (page 394) is not Fuse/Disc.
evaluated
Related
MINT
applications
Alarm ID 1646
This alarm is activated when there is a problem with circuit breaker position while
closing.
LBO ESCB CLOSE/OPEN (PAGE 711) closed but LBI ESCB FEEDBACK (PAGE
655) did not closed in Waiting For Breaker Feedback (page 396) seconds.
Description
Image 7.77 ESCB Fail To Close
Sd ESCB Fail To Open

Alarmlist
Sd ESCB Fail To Open
message
Alarm
evaluated
Related
MINT
applications
Alarm ID 1645
opening.
Description
LBO ESCB CLOSE/OPEN (PAGE 711) opened but LBI ESCB FEEDBACK (PAGE
655) did not opened in 2 seconds.

Image 7.78 ESCB Fail To Open
Sd ESCB Fail

Alarmlist
Sd ESCB Fail
message
Alarm
evaluated
Related
MINT
applications
Alarm ID 1644
This alarm is activated when there is a problem with position of the circuit breaker.
LBI ESCB FEEDBACK (PAGE 655) does not match expected position given by
LBO ESCB CLOSE/OPEN (PAGE 711).
There is a mismatch between LBI ESCB FEEDBACK (PAGE 655) and ESCB
FEEDBACK NEGATIVE (PAGE 656).
Description

Image 7.79 ESCB Fail
Sd ESCB Not Closed

Alarmlist message Sd ESCB Not Closed
Alarm evaluated Only if ESCB Type (page 394) is not Breaker
Related
MINT
applications
Alarm ID 2229
If Setpoint ESCB Type (page 394) = Fuse/Disc you need configure LBI ESCB
Description
FEEDBACK (PAGE 655) = 1 otherwise alarm Sd ESCB Not Closed is active.
Sd ES >>V
Alarm Type Sd
Alarmlist message Sd ES >>V
Alarm evaluated
Alarm ID 1658
This alarm is activated by ES >>V (page 341)
Description
Sd ES <<V
Alarm Type Sd
Alarmlist message Sd ES <<V
Alarm evaluated
Alarm ID 1660
Description This alarm is activated by ES <<V (page 342)


Sd Fence 1 Alarm
Alarm Type Shutdown
Alarmlist message Sd Fence 1 Alarm
Description

Sd Fence 2 Alarm
Alarm Type Shutdown
Alarmlist message Sd Fence 2 Alarm
Description
Sd BESS >>V L1-N

Alarmlist message Sd BESS >>V L1-N
Alarm evaluated Only if BESS >>V Protection (page 356) != Disabled
Alarm ID 1098
This alarm is activated by BESS >>V Protection (page 356).
Description
Sd Bus >>V L2-N

Alarm ID 1099
Description

Sd BESS >>V L3-N

Alarm ID 1100
Description
WRN BESS >>V L1-L2

Alarmlist message Sd BESS >>V L1-L2
Alarm ID 1101
Description
WRN BESS >>V L2-L3

Alarm ID 1102
Description
WRN BESS >>V L3-L1

Alarm ID 1103
Description

Sd BESS >V L1-N
Protection types (page 165)History Record Only (page 165) Shutdown

Alarm Type
(page 166) Warning (page 165)
Alarmlist message Sd BESS >V L1-N
Alarm evaluated Only if BESS >V Protection (page 355) != Disabled
Alarm ID 98
This alarm is activated by BESS >V Protection (page 355).
Description
6 back to List of alarms level 26 back to List of alarms level 1
Sd BESS >V L2-N

Alarm Type
Alarm evaluated Only if BESS >V Protection (page 355)!= Disabled
Alarm ID 99
Description
Sd BESS >V L3-N

Alarm Type
Alarm ID 100
Description
Sd BESS >V L1-L2

Alarm Type
Alarmlist message Sd BESS >V L1-L2
Alarm ID 107
Description This alarm is activated by BESS >V Protection (page 355).

Sd BESS >V L2-L3

Alarm Type
Alarm ID 108
Description
Sd BESS >V L3-L1

Alarm Type
Alarm ID 109
Description
Sd BESS <V L1-N

Alarm Type
Alarmlist message Sd BESS <V L1-N
Alarm ID 95
Description
Sd BESS <V L2-N

Alarm Type

Alarm ID 96
Description
Sd BESS <V L3-N

Alarm Type
Alarm ID 97
This alarm is activated by BESS <<V Protection (page 357).
Description
Sd BESS <V L1-L2

Alarm Type
Alarmlist message Sd BESS <V L1-L2
Alarm ID 104
Description
Sd BESS <V L2-L3

Alarm Type
Alarm ID 105
Description
Sd BESS <V L3-L1
Alarm Type Protection types (page 165)History Record Only (page 165) Shutdown

Alarm ID 106
Description
Sd BESS >f

Alarm Type
Alarmlist message Sd BESS >f
Alarm evaluated Only if BESS >f Protection (page 363) != Disabled
Alarm ID 121
This alarm is activated by BESS >f Protection (page 363).
Description
Sd BESS <f

Alarm Type
Alarmlist message Sd BESS <f
Alarm evaluated Only if BESS >f Protection (page 363) != Disabled
Alarm ID 120
This alarm is activated by BESS <f Protection (page 364).
Description
Sd BESS V Unbalance Ph-N

Alarm Type
(page 166)
Alarmlist message Sd BESS V Unbalance Ph-N
Alarm ID 589
This alarm is activated by Voltage Unbalance Protection (page 357).
Description

Sd BESS V Unbalance Ph-Ph

Alarm Type
(page 166)
Alarmlist message Sd BESS V Unbalance Ph-Ph
Alarm ID 588
This alarm is activated by Voltage Unbalance Protection (page 357).
Description
Sd BESS Current Unbalance
Alarm Type Protection types (page 165) Shutdown (page 166)

Alarmlist message Sd BESS Current Unbalance
Alarm evaluated Only if BESS Current Unbalance Protection (page 352) != Disabled
Alarm ID 591
This alarm is activated by BESS Current Unbalance Protection (page 352).
Description
Sd IDMT PCS Overload Protection

Alarmlist message Sd IDMT PCS Overload Protection
Alarm evaluated All the Time
Alarm ID 2237
Description This alarm is activated by Setpoint PCS IDMT >A Protection (page 353)
Sd IDMT Earth Fault Current

Alarmlist message Sd IDMT Earth Fault Current
Alarm evaluated Only if Earth Fault Current Protection (page 528) != Disabled
Alarm ID 598
This alarm is activated by Earth Fault Current Protection (page 528).
Description

Sd IDMT BESS >A
Alarm Type Protection types (page 165) Shutdown (page 166)

Alarmlist message Sd IDMT BESS >A
Alarm evaluated While BESS is loaded, if BESS IDMT >A Protection (page 350) != Disabled
Alarm ID 597
This alarm is activated by BESS IDMT >A Protection (page 350).
Description
Sd IDMT Overload
Protection types (page 165)Protection types (page 165) Shutdown (page

Alarm Type
166)
Alarmlist message Sd IDMT Overload
While Gen-set is excited, Only if BESS IDMT Overload Protection (page 349)
Alarm evaluated
!= Disabled
Alarm ID 147
This alarm is activated by BESS IDMT Overload Protection (page 349).
Description
Sd NCB Fail

Alarmlist message Sd NCB Fail
Alarm evaluated While Gen-set is excited, Only if NCB FEEDBACK (PAGE 673) is configured
Alarm ID 148
This alarm is activated when LBI NCB FEEDBACK (PAGE 673) does not match
Description expected position given by LBO NCB CLOSE/OPEN (PAGE 724).
Sd PCS IDMT >A

Alarmlist message Sd PCS IDMT >A
Alarm ID 2236
This alarm is activated by Setpoint BESS IDMT >A Protection (page 350)
Description
This alarm has FPS - Fixed Protections States 1 (page 741)

Sd PCS >>V
Alarm Type Sd
Alarmlist message Sd PCS >>V
Alarm evaluated
Alarm ID 2232
This alarm is activated by PCS >>V (page 347)
Description
Sd PCS Short Circuit
Alarm Type Sd
Alarmlist message Sd PCS Short Circuit
Alarm evaluated
Alarm ID 2235
This alarm is activated by Setpoint PCS Short Circuit Delay (page 345)
Description
This alarm has Fixed Protections States 1 (page 741)
Sd PCS <<V
Alarm Type Sd
Alarmlist message Sd PCS<<V
Alarm evaluated
Alarm ID 2234
This alarm is activated by ES <<V (page 342)
Description
PVBO Short Circuit
Alarm Type Protection types (page 165)Shutdown (page 166)

Alarmlist message PVBO Short Circuit
Alarm evaluated Only if Short Circuit Protection (page 350) != Disabled
Alarm ID 595
This alarm is activated by Short Circuit Protection (page 350).
Description

Sd SOC Critical High

Alarmlist message Sd SOC Critical High
Alarm ID 1597
This alarm is activated by ES>>SOC (page 374).
Description
Sd SOC Critical Low

Alarmlist message Sd SOC Critical Low
Alarm ID 1596
This alarm is activated by ES <<SOC (page 374).
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 (ES Ready To Load
Description
TO (page 324) or PCS Ready To Start TO (page 324) elapses).

Slow Stop
Stp Bus Meas Error
Alarm Type Slow Stop (page 166)Warning (page 165)

Alarmlist message Stp Bus Meas Error
Alarm evaluated Bus Meas Error (page 365) != 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 670) was detected (physically or via CAN2) →
Breaker State = MultParOp, BUS HEALTHY (PAGE 703) is active and
Controller Mode (page 290) = AUTO
Any other controller in Control Group (page 426) 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
Own MCB and BCB (in case of BCB application) was closed and LBO
Bus Healthy (page 703) is active
Description
Any other controller in Control Group (page 426) closed BCB
with closed BCB
Own BTB was closed and LBO Bus Healthy (page 703) is active →
mismatch detected on Bus Left
Own BTB was closed and LBO BESS Healthy (page 702) is active →
mismatch detected on Bus Right
Any other controller in Group Link L closed BCB → mismatch detected
on Bus Left
Any other controller in Group Link R closed BCB → mismatch detected
on Bus Right
with closed BCB
Stp BCB Fail

Alarmlist
Stp BCB Fail
message

Alarm
Only if BCB Control Mode (page 394) != External
evaluated
Related
MINT
applications
Alarm ID 91
LBI BCB FEEDBACK (PAGE 648) does not match expected position given by LBO
BCB CLOSE/OPEN (PAGE 695).
There is a mismatch between LBI BCB FEEDBACK (PAGE 648) and BCB
FEEDBACK NEGATIVE (PAGE 649).
Description
Image 7.80 BCB Fail
Sd BCB Fail To Close

Alarmlist
Sd BCB Fail To Close
message
Alarm
evaluated
Related
MINT
applications
Alarm ID 1555

closing.
LBO BCB CLOSE/OPEN (PAGE 695) closed but LBI BCB FEEDBACK (PAGE 648)
did not closed in Waiting For Breaker Feedback (page 396) seconds.
Description
Image 7.81 BCB Fail To Close
.This alarm has FPS-FIXED PROTECTIONS STATES 3 (PAGE 743)
Sd BCB Fail To Open

Alarmlist
Sd BCB Fail To Open
message
Alarm
evaluated
Related
MINT
applications
Alarm ID 1554
opening.
LBO BCB CLOSE/OPEN (PAGE 695) opened but LBI BCB FEEDBACK (PAGE 648)
did not opened in 2 seconds.
Description
Image 7.82 BCB Fail To Open


Alarmlist
message
Only if LBI BCB SECONDARY FEEDBACK (PAGE 650) or LBI BCB SECONDARY
Alarm FEEDBACK NEGATIVE (PAGE 651) or BCB CLOSE/OPEN SECONDARY (PAGE 695) is
evaluated configured
Related
MINT
applications
Alarm ID 451
LBI BCB SECONDARY FEEDBACK (PAGE 650) does not match expected position
given by LBO BCB CLOSE/OPEN SECONDARY (PAGE 695).
There is a mismatch between LBI BCB SECONDARY FEEDBACK (PAGE 650) and
BCB SECONDARY FEEDBACK NEGATIVE (PAGE 651).
Description
Image 7.83 BCB Secondary Fail
Stp BCB Secondary Fail To Close

Alarmlist
Stp BCB Secondary Fail To Close
message
Alarm Only if LBI BCB SECONDARY FEEDBACK (PAGE 650) or LBI BCB SECONDARY

FEEDBACK NEGATIVE (PAGE 651) or BCB CLOSE/OPEN SECONDARY (PAGE 695) is
evaluated configured
Related
MINT
applications
Alarm ID 1557
closing.
LBO BCB CLOSE/OPEN SECONDARY (PAGE 695) closed but LBI BCB
SECONDARY FEEDBACK (PAGE 650) did not closed in Waiting For Breaker
Feedback (page 396) seconds.
Description
Image 7.84 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 650) or LBI BCB SECONDARY FEEDBACK
Alarm
NEGATIVE (PAGE 651) or BCB CLOSE/OPEN SECONDARY (PAGE 695) is configured
evaluated
Related
MINT
applications
Alarm ID 1556
opening.
Description
LBO BCB CLOSE/OPEN SECONDARY (PAGE 695) opened but LBI BCB
SECONDARY FEEDBACK (PAGE 650) did not opened in 2 seconds.

Image 7.85 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 391) elapses.
8.2.4 Other alarms

List of other alarms
Bus >V L1-N 843 DISTIN 05 863 DISTIN 45 873

Bus >V L1-L2 844 DISTIN 08 863 DISTIN 48 873
Bus >>V L1-N 846 DISTIN 11 864 DISTIN 51 874
Bus >>V L1-L2 848 DISTIN 14 865 DISTIN 54 875
Bus <V L1-N 850 DISTIN 17 866 DISTIN 57 876
Bus <V L1-L2 852 DISTIN 20 866 DISTIN 60 876
Bus <<V L1-N 853 DISTIN 23 867 DISTIN 63 877
Bus <<V L2-N 854 DISTIN 24 867 DISTIN 64 877
Bus <<V L3-N 855 DISTIN 25 868 DISTOUT 878
Bus <<V L1-L2 855 DISTIN 26 868 ECU 1 Comm Fail 878
Bus >f 857 DISTIN 29 869 ECU 4 Comm Fail 879
Bus <f 858 DISTIN 30 869 ECU 5 Comm Fail 879
Bus V Unbalance Ph-N 858 DISTIN 31 869 ECU 6 Comm Fail 879
Bus V Unbalance Ph-Ph 859 DISTIN 32 869 ECU 7 Comm Fail 879
Maintenance 1 Interval 859 DISTIN 33 870 ECU 8 Comm Fail 880
Maintenance 1 RunHours 860 DISTIN 34 870 ECU 9 Comm Fail 880
Maintenance 2 Interval 860 DISTIN 35 870 SHAIN 1 880
Maintenance 2 RunHours 860 DISTIN 36 870 SHAIN 2 880
Maintenance 3 Interval 860 DISTIN 37 871 Wrn SHAIN Collision 881
Maintenance 3 RunHours 861 DISTIN 38 871 SHBIN 1 881
Maintenance 4 Interval 861 DISTIN 39 871 SHBIN 2 881
Maintenance 4 RunHours 861 DISTIN 40 871 SHBIN 3 881
DISTIN 01 862 DISTIN 41 872 SHBIN 4 882
DISTIN 04 862 DISTIN 44 872 Wrn SHBIN Collision 882

VRT Protection Trip 883
6 back to Alarms

Bus >V L1-N
Active Application
Alarm Type
(page 576)
Alarm Type MINT History Record Only (page 165)
Protection types (page 165)
History Record Only (page 165)
Alarmlist message Bus >V L1-N
Active Application (page 576) Evaluated

Alarm evaluated
MINT All the time

Alarm ID 125
This alarm is activated when Bus Voltage L1-N (page 552) rises over preset
value.
Active Application
Behavior
(page 576)
Description Protection is always active. Alarm is activated
when relative value of Bus Voltage L1-N (page
MINT 552) related to Bus Nominal Voltage Ph-N
(page 287) rises over BESS >V (page 334) for
period longer than BESS >V Delay (page 334).
Bus >V L2-N
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 126
This alarm is activated when Bus Voltage L2-N (page 552) rises above preset
Description
value.

Active Application
Behavior
(page 576)
Protection is always active. Alarm is activated
Bus >V L3-N
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 127
value.
Active Application
Behavior
(page 576)
Bus >V L1-L2
Active Application
Alarm Type
(page 576)
Alarmlist message Bus >V L1-L2

Alarm evaluated
MINT All the time

Alarm ID 131
This alarm is activated when Bus Voltage L1-L2 (page 552) rises over preset
value.
Active Application
Behavior
(page 576)
Description
when relative value of Bus Voltage L1-L2 (page
552) related to Mains/Bus Nominal Voltage Ph-
MINT
Ph (page 287) rises over BESS >V (page 334)
for period longer than BESS >V Delay (page
334).
Bus >V L2-L3
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 132
value.
Active Application
Behavior
(page 576)
Description
MINT
334).

Bus >V L3-L1
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 133
value.
Active Application
Behavior
(page 576)
Description
MINT
334).
Bus >>V L1-N
Active Application
Alarm Type
(page 576)
Alarmlist message Bus >>V L1-N

Alarm evaluated
MINT All the time

Alarm ID 1080
Description
value.

Active Application
Behavior
(page 576)
(page 287) rises over BESS >>V (page 335) for
period longer than BESS >>V Delay (page 335).
Bus >>V L2-N
Active Application
Alarm Type
(page 576)
Alarmlist message Mains/Bus >>V L2-NMP Mains >>V L2-NHst Bus Left >>V L2-N

Alarm evaluated
MINT All the time

Alarm ID 1082
value.
Active Application
Behavior
(page 576)
period longer than BESS >>V Delay (page 335).
Bus >>V L3-N
Active Application
Alarm Type
(page 576)
Alarmlist message M Bus >>V L3-N

Alarm evaluated
MINT All the time

Alarm ID 1084
value.
Active Application
Behavior
(page 576)
period longer than BESS >>V (page 335).
Bus >>V L1-L2
Active Application
Alarm Type
(page 576)
Alarmlist message Bus >>V L1-L2

Alarm evaluated
MINT All the time

Alarm ID 1086
value.
Active Application
Behavior
(page 576)
Description
MINT
Ph (page 287) rises over BESS >>V (page 335)
for period longer than BESS >>V Delay (page
335).

Bus >>V L2-L3
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 1088
value.
Active Application
Behavior
(page 576)
Description
MINT
335).
Bus >>V L3-L1
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 1090
Description
value.

Active Application
Behavior
(page 576)
MINT
335).
Bus <V L1-N
Active Application
Alarm Type
(page 576)
Alarmlist message Bus <V L1-N

Alarm evaluated
MINT All the time

Alarm ID 122
This alarm is activated when Bus Voltage L1-N (page 552) drops below preset
value.
Active Application
Behavior
(page 576)
(page 287) drops below BESS <V (page 336) for
period longer than BESS <V Delay (page 336).
Bus <V L2-N
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 123
value.
Active Application
Behavior
(page 576)
Bus <V L3-N
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 124
value.
Active Application
Behavior
(page 576)

Bus <V L1-L2
Active Application
Alarm Type
(page 576)
Alarmlist message Bus <V L1-L2

Alarm evaluated
MINT All the time

Alarm ID 128
This alarm is activated when Bus Voltage L1-L2 (page 552) drops below
preset value.
Active Application
Behavior
(page 576)
Description
MINT
Ph (page 287) drops below BESS <V (page
336) for period longer than BESS <V Delay
(page 336).
Bus <V L2-L3
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 129
Description
preset value.

Active Application
Behavior
(page 576)
MINT
(page 336).
Bus <V L3-L1
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 130
preset value.
Active Application
Behavior
(page 576)
Description
MINT
(page 336).
Bus <<V L1-N
Active Application
Alarm Type
(page 576)

Alarmlist message Bus <<V L1-N

Alarm evaluated
MINT All the time

Alarm ID 1081
value.
Active Application
Behavior
(page 576)
Bus <<V L2-N
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 1083
value.
Active Application
Behavior
(page 576)

Bus <<V L3-N
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 1085
value.
Active Application
Behavior
(page 576)
Bus <<V L1-L2
Active Application
Alarm Type
(page 576)
Alarmlist message Bus <<V L1-L2

Alarm evaluated
MINT All the time

Alarm ID 1087
Description
preset value.

Active Application
Behavior
(page 576)
MINT
(page 336).
Bus <<V L2-L3
Active Application
Alarm Type
(page 576)

Alarm evaluated
MINT All the time

Alarm ID 1089
preset value.
Active Application
Behavior
(page 576)
Description
MINT
(page 336).
Bus <<V L3-L1
Active Application
Alarm Type
(page 576)


Alarm evaluated
MINT All the time

Alarm ID 1091
preset value.
Active Application
Behavior
(page 576)
Description
MINT
(page 336).
Bus >f
Active Application
Alarm Type
(page 576)
Alarmlist message Bus >f

Alarm evaluated
MINT All the time

Alarm ID 135
This alarm is activated when Bus Frequency (page 552), rises over preset
value.
Active Application
Behavior
(page 576)
Description
when Bus Frequency (page 552) rises over
MINT
BESS >f (page 338) for period longer than
BESS >f Delay (page 338).

Bus <f
Active Application
Alarm Type
(page 576)
Alarmlist message Bus <f

Alarm evaluated
MINT All the time

Alarm ID 134
This alarm is activated when Bus Frequency (page 552), drops below preset
value.
Active Application
Behavior
(page 576)
Description
when Bus Frequency (page 552) drops below
MINT
BESS <f (page 339) for period longer than
BESS <f Delay (page 339).
Bus V Unbalance Ph-N
Active Application
Alarm Type
(page 576)
Alarmlist message Bus V Unbalance Ph-N

Alarm evaluated
MINT All the time

Alarm ID 593
This alarm is activated when relative difference between Bus Voltage L1-N
Description (page 552), Bus Voltage L2-N (page 552) or Bus Voltage L3-N (page 552)
rises over preset value.

Active Application
Behavior
(page 576)
when relative difference between bus voltages
MINT rises over BESS V Unbalance (page 337) for
period longer than BESS V Unbalance Delay
(page 337).
Bus V Unbalance Ph-Ph
Active Application
Alarm Type
(page 576)
Alarmlist message Bus V Unbalance Ph-Ph

Alarm evaluated
MINT All the time

Alarm ID 592
This alarm is activated when relative difference between Bus Voltage L1-L2
(page 552), Bus Voltage L2-L3 (page 553) or Bus Voltage L3-L1 (page 553)
rises over preset value.
Active Application
Behavior
(page 576)
Description
when relative difference between bus voltages
MINT rises over BESS V Unbalance (page 337) for
period longer than BESS V Unbalance Delay
(page 337).
Maintenance 1 Interval
Alarm Type Based on configuration (Warning (page 165)/Slow Stop (page 166))
Alarmlist message Wrn/Stp Maintenance 1 Interval
Alarm evaluated Only if Maintenance Timer 1 Interval (page 472) != Disabled
Alarm ID 1072
Description This alarm is activated when setpoint Maintenance Timer 1 Interval (page

472) elapses i.e. the value Maintenance Timer 1 Interval (page 574) = 0 and
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 471) != Disabled
Alarm ID 585
This alarm is activated when setpoint Maintenance Timer 1 RunHours (page
Description 471) elapses i.e. the value Maintenance Timer 1 RunHours (page 573) = 0
and lasts until the setpoint is set to value > 0 or "Disabled".
Alarm ID 1073
This alarm is activated when setpoint Maintenance Timer 2 Interval (page
Description 473) elapses i.e. the value Maintenance Timer 2 Interval (page 574) = 0 and
Alarm ID 586
This warning is activated when setpoint Maintenance Timer 2 RunHours
Description (page 473) elapses i.e. the value Maintenance Timer 2 RunHours (page
574) = 0 and lasts until the setpoint is set to value > 0 or "Disabled".

Alarm ID 1074
Alarm ID 587
Alarm ID 1519
Alarm evaluated Only if Maintenance Timer 4 RunHours (page 476) or != Disabled
Alarm ID 1518

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
Controller Address (page 295) = 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
Alarm evaluated 1. ECU with protection configured in ECU slot 1
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

Alarm ID 946
ECU 3 Comm Fail

Alarm ID 947

ECU 4 Comm Fail

Alarm ID 948
ECU 5 Comm Fail

Alarm ID 949
ECU 6 Comm Fail

Alarm ID 950
ECU 7 Comm Fail

Alarm ID 951
Description This alarm is activated when there is no communication received from ECU

configured in ECU slot 7.
ECU 8 Comm Fail

Alarm ID 952
ECU 9 Comm Fail

Alarm ID 953
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

Alarmlist message Wrn/MP VRT Protection Trip
Only when Dynamic Support = Enabled and and Breaker state (page 577) =
Alarm evaluated
ParalOper
Alarm ID 1043
This alarm indicates active Dynamic Support protection.
Description
8.3 Modules
8.3.1 CAN modules
Supported combinations of modules 883
Module's protections 884
Theory of binary inputs and outputs 885
Extension modules 888
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 530 BESS has the following amount
of the generic modules:
AI generic: 1016
AO generic: 8
BI generic: 16

BO generic: 1216
AI32 generic: 2
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 530 BESS.
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 885
Binary outputs 886
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 530 BESS 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 888
Inteli IO8/8 894
IGL-RA15 901
IGS-PTM 906
Inteli AIO9/1 911
Inteli AIN8TC 916
I-AOUT8 920
IS-AIN8 924
IS-AIN8TC 934
IS-BIN16/8 938
Inteli AIN8
Inteli AIN8 module is extension module equipped with analog inputs and Impulse/RPM input. The module is
connected to controller by CAN1 (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.86 Inteli AIN8
Image 7.87 Inteli AIN8 dimensions
Note: All dimensions are in mm.

Terminals
Analog input 8 analog Inputs

CAN1 CAN1 (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 CAN1 (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 CAN1 (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.88 Inteli IO8/8
Image 7.89 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 CAN1 (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 CAN1 (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.90 IGL-RA15
Image 7.91 IGL-RA15 dimensions
Terminals
Horn Horn
CAN CAN1 (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 CAN1 (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 CAN1 (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 904)
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 905) 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 CAN1 (page 19) bus. It is possible to connect up to 4 IGS-
PTM external units to one controller.
Image 7.92 IGS-PTM
Image 7.93 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 CAN1 (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.94 Inteli AIO9/1
Image 7.95 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 CAN1 (page 19) bus. It is possible to connect up to 10 Inteli
AIO9/1 external units to one controller.

Image 7.96 Inteli AIN8TC
Image 7.97 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 CAN1 (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.4 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.5 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.98 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 CAN1 (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.6 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.7 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.8 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 CAN1 (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.10 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.11 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 930) 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 CAN1 (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.13 Tx / Rx LED status
Wiring
Image 7.99 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 885) (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.14 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 530 Bess 1.0.0 Global Guide

Uploaded by

Copyright:

Available Formats

Intelineo 530 Bess 1.0.0 Global Guide

Uploaded by

Document Information

Original Title

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 530 Bess 1.0.0 Global Guide

Uploaded by

Copyright:

Available Formats

InteliNeo 530

Copyright © 2023 ComAp a.s.

InteliNeo 530 BESS 1.0.0 Global Guide 2

4.3 Terminal Diagram 40 5.4.9 E-STOP 122

4.4 Recommended wiring 42 5.4.10 Event History 124

4.4.1 General 43 5.4.11 Exercise Timers 127

4.4.2 Grounding 44 5.4.12 Firewall 134

4.4.3 Power supply 44 5.4.13 Forced Value 135

4.4.4 Measurement wiring 46 5.4.14 I/O Configuration 137

4.4.5 Binary Inputs 56 5.4.15 Load Shedding 142

4.4.6 Binary Outputs 57 5.4.16 Loss of Mains (Decoupling)

5 Controller setup 68 5.4.25 System Start/Stop 178

5.1 Operator Guide 68 5.4.26 User Buttons 179

5.1.1 InteliVision 5.2 68 5.4.27 User Management And Data Access

5.2.1 USB 98 5.4.29 Voltage Phase Sequence Detection 190

5.2.2 Ethernet 99 5.5 Application related functions 191

5.3 Default configuration 104 5.5.1 BESS Charging/Discharging Control 191

5.3.1 Binary inputs 104 5.5.2 BESS Forced power 192

5.3.2 Binary outputs 105 5.5.3 BESS Operation States 193

5.3.3 Analog inputs 105 5.5.4 BESS Operation Area 194

5.3.4 Analog Outputs 105 5.5.5 BESS Precharge Types 194

5.4 General Functions 105 5.5.6 InteliNeo 530 as Generic BESS

InteliNeo 530 BESS 1.0.0 Global Guide 3

7 Technical data 259

InteliNeo 530 BESS 1.0.0 Global Guide 4

6 back to Table of contents

1.1 Declaration of Conformity

Unique identifier: INEO530BBAANU

Tel: +1 815 636 2541

FCC Compliance Statement

1.2 Clarification of Notation

InteliNeo 530 BESS 1.0.0 Global Guide 5

1.3 About this Global Guide

1.4 Legal notice

InteliNeo 530 BESS 1.0.0 Global Guide 6

1.5 Used open source software:

InteliNeo 530 BESS 1.0.0 Global Guide 7

Copyright (c) 2011, 2013 Mutsuo Saito,

Copyright (c) 2013-2015, Scott Vokes

InteliNeo 530 BESS 1.0.0 Global Guide 8

1.6 General warnings

1.6.2 SW and HW versions compatibility

1.6.3 Dangerous voltage

1.6.4 Adjust the setpoints

InteliNeo 530 BESS 1.0.0 Global Guide 9

1.7 Functions and protections

* extension module IGL-RA15 required

1.8 Certifications and standards

EN 61000-6-4 EN 60068-2-2 (70 °C/16 h)

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 530 BESS 1.0.0 Global Guide 10

InteliNeo 530 BESS 1.0.0 Global Guide 11

InteliNeo 530 BESS 1.0.0 Global Guide 12

6 back to Table of contents

2.1 General description

2.1.1 The key features of InteliNeo 530 BESS

InteliNeo 530 BESS 1.0.0 Global Guide 13