Inteligen 500 g2 Global Guide
Inteligen 500 g2 Global Guide
Inteligen 500 g2 Global Guide
SW version 2.0.0
1 Document information 5
2 System overview 12
3 Applications overview 29
4 Installation and wiring 31
5 Controller setup 69
6 Communication 255
7 Technical data 277
8 Appendix 279
6 Communication 255
6.1 PC 255
6.1.1 Direct communication 255
6.1.2 Remote communication 257
6.2 Connection to 3rd party systems 262
6.2.1 SNMP 262
6.2.2 MODBUS-RTU, MODBUS/TCP 264
8 Appendix 279
8.1 Controller objects 279
8.1.1 List of controller objects types 279
8.1.2 Setpoints 279
8.1.3 Values 629
8.1.4 Logical binary inputs 692
8.1.5 Logical binary outputs 737
8.1.6 Logical analog inputs 802
8.1.7 PLC 811
8.2 Alarms 834
8.2.1 Alarm levels in the controller 834
8.2.2 Alarms level 1 834
8.2.3 Alarms level 2 881
8.3 AVR interfaces 917
8.3.1 AVR interfaces alphabetically 917
8.4 Speed governors interfaces 926
8.4.1 Electronic engines interface 926
8.4.2 Controller Speed Regulator Output
voltage limits 926
8.4.3 Speed governors interfaces
alphabetically 926
8.5 Modules 935
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.
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 a controller.
This manual only describes the product and is not guaranteed to be set for your application.
The following instructions are for qualified personnel only. To avoid personal injury do not perform any action
not specified in related guides for product.
EN 60068-2-1 (-20 °C/16 h) EN 60529 (front panel IP65, back side IP20)
Responsible Party:
Kevin Counts
Connector - Resistor
3 x Phases Grounding
male adjustable
Active Resistive
current Contact GSM sensor
sensor RPTC
GSM RS 232
Contactor
AirGate modem male
Controller RS 232
IG-AVRi
Alternating simplified female
current
Module IG-AVRi
Starter
Analog simplified TRANS
modem
Switch -
Current
Jumper manually
measuring
Battery operated
Current
Load Transformer
Binary measuring
output
USB type B
Diode Mains male
Breaker
contact
Ethernet USB type B
Mains female
Breaker male
contact
Voltage
Ethernet Mobile
measuring
female provider
Breaker
Passive Wi-fi / WAN
Fuel
current / LAN
solenoid
Breaker sensor
6 back to Document
information
Fuse Pick - up
Breaker
Note: Use the InteliConfig PC software to read, view and modify configuration from the controller or disk and
write the new configuration to the controller or disk.
The firmware of the controller contains a large number of logical binary inputs and outputs needed for all
necessary functions available. However, not all functions are required at the same time on the same Gen-set;
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.
The controller is shipped with a default configuration, which should be suitable for most standard applications.
This default 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 .aig4. 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 easily used for cloning controllers, i.e. preparing controllers with identical configuration
and settings.
2.4.2 WebSupervisor
Web-based system for monitoring and controlling of controllers. See more at the WebSupervisor webpage.
2.4.3 WinScope 1000
Special graphical controller monitoring software used mainly for commissioning and Gen-set troubleshooting.
See more in the WinScope 1000 Reference guide.
2.5.3 CM-RS232-485
Communication module with two communication ports.
RS232 and RS485 interface
Modbus RTU support
Serial connection to InteliConfig
2.5.4 EM-BIO8-EFCP
Hybrid current input and binary input/output extension module.
One additional AC current (CT) measuring for
Earth Fault Current protection (EFCP)
Wide range of measured current – one input for
1 A and 1 input for 5 A
Up to 8 additional configurable binary inputs or
outputs
Note: This protection is active ONLY when Engine
is running.
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-10 V),
current (0-20 mA) and PWM (5 V, adjustable
frequency 200 Hz-2.4 kHz))
Configuration 16/0
16 Binary inputs (options: pull up or pull down
logic)
0 Binary outputs
2 Analog outputs (options: voltage (0-10 V),
current (0-20 mA) and PWM (5 V, adjustable
frequency 200 Hz-2.4 kHz))
Supported sensors:
Resistor 3-wire input
Common resistor: 0-250 Ω, 0-2400 Ω, 0-
10 kΩ
Temperature sensor: Pt100, Pt1000,
Ni100, Ni1000
Current (active or passive sensors)
±20 mA, 0-20 mA, 4-20 mA
Voltage
±1 V, 0-2.4 V, 0-5 V, 0-10 V
Lambda probes
Thermocouples are not supported (the
measuring loop was designed for lambda
probes, which caused non-support of
thermocouples)
Impulse/RPM sensor:
RPM measuring pulses with frequency 4 Hz-
10 kHz
Impulse
Possibility to measure pulses from
electrometer, flowmeter (measurement of
total consumption, average fuel
consumption)
2.6.9 IGL-RA15
Remote annunciator.
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
2.6.11 I-CR-R
CAN Redundancy Module.
Provides intercontroller CAN bus redundancy
by adding parallel RS485 communication bus
Provides intercontroller bus extension as well
Intended for achieving high reliability of the
intercontroller communication in complex
applications where the parts of the technology
are separated from each other and the
intercontroller bus is exposed to a risk of
interruption.
I-CR-R may be used as a redundancy module
for a maximum of 20 controllers (counted all
controllers on the CAN2 bus)
Module is compatible with InteliGen 1000 and
InteliMains 1010 controllers if CAN
Intercontroller Comm Mode is set to 32C/8C
Shared modules are virtual modules used for sharing any binary or analog value via CAN2 intercontroller
communication.
There are four types of shared modules available: SHBIN, SHBOUT, SHAIN, SHAOUT.
Image 2.3 Example of correct configuration of sharing analog values of CU1 with CU2 and CU3
An alarm Wrn SHBIN Collision* (page 873) – 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 Wrn SHAIN 1* (page 870) to Wrn SHAIN 4* (page 870) is activated in case that
data are not received.
Select protection type, and whether screens and history columns shall be added.
Add module.
SHBOUT
SHBOUT virtual modules share binary values to other controllers via CAN2 intercontroller communication.
There are 6 modules, SHBOUT-1 to SHBOUT-6, which are firmly connected with SHBIN-1 to SHBIN-6.
Note: This means that you need to use module SHBOUT-1 if you wish to send data to SHBIN-1.
Select protection type, and whether screens and history columns shall be added.
Add module.
An alarm Wrn SHAIN Collision* (page 871) 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 Wrn SHBIN 1* (page 871) to Wrn SHBIN 6* (page 872) is activated in case that
data are not received.
Select protection type, and whether screens and history columns shall be added.
Add module.
Select protection type, and wether screens and history columns shall be added.
Add module.
3.1 SPtM
The typical scheme of a single parallel to mains application is shown below. The controller controls two
breakers – a mains breaker and a generator breaker. Feedback from both breakers is required.
Note: The package does not contain any communication or extension modules. The required modules
should be ordered separately.
① Plug-in module
Note: Dimension x depends on plug-in module.
Note: Enclosure Type rating with mounting instruction – For use on a Flat surface of a type 1 enclosure.
POWER
T25 COM T21 AI3 T11 BOUT7 T58 COM
SUPPLY, D+
T23 +5 V T18 ACOM T08 BOUT4 T03 BATT + USB HOST
RPM 16, 17
EMC Grounding
2
Note: Wiring terminal markings to included tightening torque: 0.5 N-m (4.5 lb-in)., and wire size: 2 mm (12-
26 AWG).
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 be wired with shielded cables, especially when the length is more than
3 m.
Tightening torque, allowable wire size and type, for the Field-Wiring Terminals:
For Mains Voltage, Generator Voltage and Current terminals
For the connections with 12 V DC power supply, the controller includes internal capacitors that allow the
controller to continue in operation during cranking if the batter voltage dip occurs. If the voltage dip goes to 0 V
during cranking and after 50 ms it recovers to 4 V, the controller continues operating. This cycle can repeat
several times. During this voltage dip the controller screen backlight can turn off.
Note: In case of the dip to 0 V the high-side binary outputs will be temporarily switched off and after
recovering to 4 V back on.
Note: Suitable conductor protection shall be provided in accordance with NFPA 70, Article 240.
Note: Low voltage circuits (35 volts or less) shall be supplied from the engine starting battery or an isolated
secondary circuit.
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. Diode should be able to withstand at
least 1 kV.
3 phase application
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.
IMPORTANT: It is necessary to ensure that potential difference between current COM terminal
and power supply "–" terminal is maximally ±2 V. To do so interconnect these two terminals.
SplPhL1L2 application
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.
IMPORTANT: It is necessary to ensure that potential difference between current COM terminal
and power supply "–" terminal is maximally ±2 V. To do so interconnect these two terminals.
SplPhL1L3 application
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.
IMPORTANT: It is necessary to ensure that potential difference between current COM terminal
and power supply "–" terminal is maximally ±2 V. To do so interconnect these two terminals.
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.
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.
IMPORTANT: It is necessary to ensure that potential difference between current COM terminal
and power supply "–" terminal is maximally ±2 V. To do so interconnect these two terminals.
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.
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 generator protections are evaluated from different voltages base d on Connection type (page 309)
setting:
3Ph 4W – Ph-Ph voltage, Ph-N voltage
High Leg D – Ph-Ph voltage, Ph-N voltage
3Ph 3W – Ph-Ph voltage
Image 4.14 Typical 3 Phase 4 Wires generator wiring, also known as 3ph High Y
Note: Connection type 277/480V 3-PHASE, Nominal Voltage 3Ph High Y (page 312).
Note: Connection type 120/208V 3-PHASE, Nominal Voltage 3Ph Low Y (page 312).
ConnectionType: SplPhL1L3
IMPORTANT: The second phase of split phase connection is connected to the terminal, where is
usually connected the third phase.
Note: Connection type 120/240V 1-PHASE, Nominal Voltage SplitPhase (page 313).
The generator protections are evaluated from different voltages based on Connection type (page 309)
setting:
3Ph 4W – Ph-Ph voltage, Ph-N voltage
3Ph 3W – Ph-Ph voltage
SplPhL1L2 – Ph-N voltage
SplPhL1L3 – Ph-N voltage
Split Ph – Ph-N voltage
Mono Ph – Ph-N voltage
Image 4.26 Typical 3 Phase 4 Wires generator wiring, also known as 3ph High Y
Note: Connection type 277/480V 3-PHASE, Nominal Voltage 3Ph High Y (page 312).
Note: Connection type 120/208V 3-PHASE, Nominal Voltage 3Ph Low Y (page 312).
IMPORTANT: The second phase of split phase connection is connected to the terminal, where is
usually connected the third phase.
IMPORTANT: The second phase of split phase connection is connected to the terminal, where is
usually connected the third phase.
Note: Connection type 120/240V 1-PHASE, Nominal Voltage SplitPhase (page 313).
Note: The name and function or alarm type for each binary input must be assigned during the configuration.
Note: Every single binary output can provide up to 0.5 A of steady current.
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+)
In the case of grounded sensors, connect the AI COM terminal to the engine body as near to the sensors
as possible.
In the case of isolated sensors, connect the AI COM 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.
Note: Schematics 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.
Image 4.44 Analog inputs as tristate Image 4.45 Analog inputs as binary
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.
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)
Note: Shielding shall be grounded at one end only. Shielding shall not be connected to CAN COM terminal.
For longer distances or in case of surge hazard (connection out of building, in case of storm etc.)
① Recommended PT5-HF-12DC-ST1
For longer distances or in case of surge hazard (connection out of building, in case of storm etc.)
① Recommended PT5HF-5DC-ST2
Note: Communication circuits shall be connected to communication circuits of Listed equipment.
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)
2Recommended 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
Balancing resistors
The transmission bus into the RS485 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, force the transmission line into a known state. By installing two 620Ω
balancing resistors at one node on the transmission line, a voltage divider is created that forces the voltage
between the differential pair to be less than 200 mV, which is the threshold for the receiver. 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 the jumpers PULL UP/PULL DOWN to connect the
balancing resistors.
4.4.13 Ethernet
Ethernet Cat5/Cat6 cable fitted with the RJ45 connector can be connected to the Ethernet interface.
Controller can be also powered by USB (only for service purpose like an uploading firmware, change of
configuration etc.).
IMPORTANT: Power supply by USB is only for service purpose. Binary inputs and outputs are in
logical 0. Also plug-in modules are not working.
Remove the back cover. To do this, press four holders which are located in corners.
After removing the back cover insert the plug-in module. The plug-in module must be inserted under holders.
Start with holders marked by arrows. After inserting plug-in module under holders press it down. This locks
the module in place.
After locking the plug-in module into holders, place back the back cover (small cover for connectors has to be
removed from back cover). Finally insert the small cover for connectors. Small covers are unique for each
plug-in module.
4.6 Maintenance
4.6.1 Backup battery replacement
This battery serves to maintain the run of RTC (real time clock) so that controller does not lose information
about time and date when disconnected from power supply.
The internal backup battery lifetime is approx. 6 years. If 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.
The battery is located in a holder on the circuit board. Remove the old battery with a small sharp
screwdriver and push the new battery into the holder using a finger.
Replace the rear cover. Use slight pressure to lock the snaps into the housing. Pay attention that the cover
is in correct position and not upside down!
Replace the plug-in modules and back cover.
Power the controller on, adjust date and time and check all setpoints.
5.2.1 USB
You may connect to the controller using the USB port. In this case standard USB A to B cable should be used.
5.2.2 RS232/RS485
It is possible to connect to the controller using RS232 or RS485 direct connection (serial port or USB to
RS232/RS485 converter may be used). The following settings should be checked in the controller:
COM1 Mode (page 574) = Direct
Controller Address (page 322) must be set
5.2.3 Ethernet
It is possible to connect to the controller using Ethernet port either directly or using ComAp's AirGate service.
Note: Ethernet connection can be acquired via Onboard Ethernet, CM3-Ethernet or CM2-4G-GPS plug-in
modules.
Direct connection
If you use a 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
should to be checked in the controller:
Controller Address (page 322) must be set to the same value as in the PC tool
IP Address Mode (page 623) can be set to AUTOMATIC when there is DHCP service available.
Otherwise it should be set to FIXED
IP Address (page 624) is either set automatically or it can be adjusted to a specific requested value
Subnet Mask (page 624) is either set automatically or it can be adjusted to a specific requested value
Gateway IP (page 625) can be set here when it is used
AirGate connection
You can use ComAp's AirGate service that allows you to connect to any controller via the internet regardless
of the restrictions of the local network (as long as the controller can connect to the internet AirGate service will
work). The following setpoints must be adjusted:
Controller Address (page 322) must be set to the same value as in the PC tool
IP Address Mode (page 623) can be set to AUTOMATIC when there is DHCP service available.
Otherwise it should be set to FIXED
IP Address (page 624) is either set automatically or it can be adjusted to a specific requested value
Subnet Mask (page 624) is either set automatically or it can be adjusted to a specific requested value
Gateway IP (page 625) can be set here when it is used
AirGate Address (page 584) currently there is one AirGate server running at URL global.airgate.link
(enter this URL into the setpoint)
IMPORTANT: AirGate Key has to be configured. User with administrator rights has a possibility to
set up or change AirGate Key via InteliConfig using Tools -˃ Access Administration -˃ Change
AirGate Key.
IMPORTANT: AirGate Key has to be configured. User with administrator rights has a possibility to
set up or change AirGate Key via InteliConfig using Tools -˃ Access Administration -˃ Change
AirGate Key.
IMPORTANT: AirGate Key has to be configured. User with administrator rights has a possibility to
set up or change AirGate Key via InteliConfig using Tools -˃ Access Administration -˃ Change
AirGate Key.
Control buttons
Position Picture Description
LEFT button. Use this button to move left or to change the mode. The button
can change the mode only if the main screen with the indicator of currently
selected mode is displayed.
Note: This button will not change the mode if the controller mode is forced
by one of binary inputs listed in the Reference Guide – "Operating modes"
chapter.
RIGHT button. Use this button to move right or to change the mode. The
button can change the mode only if the main screen with the indicator of
currently selected mode is displayed.
HORN RESET button. Use this button to deactivate the horn output without
acknowledging the alarms.
ENTER button. Use this button to finish editing a setpoint or moving right in
the history page.
START button. Works in MAN mode only. Press this button to initiate the
start sequence of the engine.
STOP button. Works in MAN mode only. Press this button to initiate the stop
sequence of the Gen-set. Repeated pressing of button will cancel current
phase of stop sequence (like cooling) and next phase will continue.
MCB button. Works in MAN mode only. Press this button to open or close
the MCB. This button also start the synchronization process.
GCB button. Works in MAN mode only. Press this button to open or close the
GCB. This button also start the synchronization process.
Multicolor (RGB) LED. The specified color and flashing function describes the actual
state of the unit. For more information see LED indication on page 1.
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:
Metering screen
Alarmlist
Setpoints
History
Trends
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). The Screen Editor tool
also has its own manual.
Special screens
There are 2 special screens stored in the unit:
Init screen
displayed during the booting procedure and in Administration menu
dedicated for specific user logo (by default predefined by ComAp)
Service screen
displayed in Administration menu
dedicated for useful technical information (by default predefined by ComAp)
Note: More information about Init and Service screen modification is described in concrete chapter of this
manual.
Dialogs
Values and parameters and other can be set in the controller via dialogs. There are several dialogs in the
GUI. Dialogs for numbers, texts and lists.
Note: Function and User buttons work on background (e.g. if any dialog is displayed).
IMPORTANT: Each dialog has its own structure corresponding to the value type.
IMPORTANT: QR Code is displayed on each dialog. Together with ComAp Smart Hint application
the QR Code is dedicated for further help. Simply read the QR Code using Smart Hint application
to get a help about actually edited setpoint.
Dialog Text
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.
Improved dialog for text inserting from version ICD 1.4.0 allows users better and user frinedly control. Arrows
are used for movement in letter table. Enter is used for letter selection/confirmation. Function buttons is used
for another functions. F1 button is used to delete letter. F2 button is used for changing the letter table to
special characters and vise versa. F3 and F4 buttons are used for movement inside the text field between the
letters. F5 button confirms the dialog and save changes. Menu button cancels the dialog without the saving
changes.
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.
Dialog 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.
Dialog Message
The dialog message has informal character about the result of any action. Enter or Menu button cancels the
dialog without saving. There is no need to confirm the selection. There two types of message dialogs :
Stop - dedicated for error indication
Information - dedicated for general message
Dialog Progress
The dialog progress has informal character about the result of any action. The progress bar and percents are
also displayed during the action performing. Enter or Menu button cancels the dialog without saving. There is
no need to confirm the selection.
Dialog 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
confirms the option. Menu button cancels the dialog without saving.
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.
GCB open, GCB close, etc.), jump to the specified page (e.g. alarmlist, history) or special functions on some
pages.
1. User button 1 – emitting the command to the controller or link to page in GUI or special function
2. User button 2 – emitting the command to the controller or link to page in GUI or special function
3. User button 3 – emitting the command to the controller or link to page in GUI or special function
4. User button 4 – emitting the command to the controller or link to page in GUI or special function
5. User button 5 – emitting the command to the controller or link to page in GUI or special function
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.
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.
6. PC connection – PC connection icon is active if the unit established connection to the PC using the USB
cable. Icon is inactive if there is not established connection to the PC.
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.
Metering screens
Metering screens are dedicated for important controller values and setpoints.
InteliGen 500 G2 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
Connected Plug-In modules
Configured CAN modules
Aftertreatment ECU list settings
5.3.3 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 color. These types of
alarms inform the user that something is wrong and need to be checked and confirmed.
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: Alarm reset button confirms all the unconfirmed alarms stored in controller.
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.
5.3.4 Setpoints
The setpoint page is intended for setting the controller values. Each type of controller has specific setpoints to
be set. The setpoints also depend on the type of application like SPtM and MINT. Availability of the setpoint
item also depends on configuration level settings in Administration page. Setpoint is set in 2 steps.
1st step – Setpoint group is selected using buttons arrow up and down and confirmed using enter button
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.
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.
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.
Login screen
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.
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.
5.3.5 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.
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.
Note: Pressing the enter button on the actually selected row the dialog with detailed information for selected
record is displayed.
5.3.6 Trends
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 color 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.
Trends settings
Trends settings page is dedicated for the available trends settings. The navigation in trends settings page is
done by buttons arrow up, arrow down, arrow left, arrow right, enter, user button 1 and 2.
1. Channel value – the channel value menu appears if the enter button is pressed just on the position.
Inside the channel value menu the requested channel value can be selected. The value availability
depends on the type of configuration stored in the controller.
2. Low limit value – the low limit value is intended for changing the low border of the value range. For the
best view of the displayed trends it is highly recommended to set this limit to the minimum expected value
with some reserve.
3. High limit value – the high limit value is intended for changing the high border of the value range. For the
best view of the displayed trends it is highly recommended to set this limit to the maximum expected value
with some reserve.
4. Quick channel removal – pressing the enter button on the trash bin icon the actual channel is not
configured.
5. Period – section is dedicated for setting of the sample time period.
6. Run – the section is intended for the selection of the run mode
a. once – trending only until the trend chart window is full
b. circular – cyclic mode (trending is repeated continuously) – be aware the samples are stored only in
internal temporal memory, the trend chart starts moving when the trend chart window is full, the
oldest samples are trashed out
7. Start option – The start of trends are triggered by the start option. There are 3 start options.
a. Binary state - the trigger is the bit of the selected binary value. Manual start and stop is still active.
b. Manual (by default) – the trigger is the start button called by user.
c. Home – the trigger is the return to the Home metering screen from any GUI position. Manual start
and stop is still active.
IMPORTANT: If the trending is started and the changes have been made in the settings the
trending is restarted based on the new settings.
IMPORTANT: Be aware the samples are stored only in internal temporal memory. Trend chart
starts moving when the trend chart window is full, the oldest samples are trashed out.
IMPORTANT: There is no option to store the trends to the external memories like USB stick, etc.
5.3.7 Values
The values page is intended to monitor the controller values. Each type of controller has specific set of values.
Values screen is visually similar to setpoins screen.
To list across the values the navigation, enter and menu buttons is used.
5.3.8 Administration
Note: Init screen is accessible using the buttons combination Enter + Menu just only from the metering
screens. Enter button has to be pressed first.
Controller Info
Controller info page is dedicated for important information about the entire unit. These information is useful
mainly for issue troubleshooting .
Controller info page is divided into 3 main blocks of information :
Integrated Color Display unit
Controller unit
Configuration
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
metering screens. Enter button has to be pressed first.
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
metering screens. Enter button has to be pressed first.
Electronic Devices
Electronic Devices screen is dedicated for important information about the connected ECU.
Note: The availability of the connected Electronic Device depends on the type of controller unit.
Note: Electronic Devices screen is accessible using the buttons combination Enter + Menu just only from the
metering screens. Enter button has to be pressed first.
1. Backlight Control – can be controlled using Internal settings or external signal over LBI Dark Mode
a. Internal – Backlight timeout and backlight intensity is respected from the manual settings
b. LBI Dark Mode – if controller LBI Dark Mode is activated then the Status LED and LCD backlight is
completely diabled. Be aware that the application and controller is still running. Keyboard is still in
functional state. The Backlight Timeout is still respected in this option.
2. Backlight Timeout – 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).
3. 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 given by the Analog Input settings in InteliConfig and
connected value of resistor, voltage or current (based on the type of the selected sensor).
4. Brightness intensity – the value is selected using the value dialog. Note the value is applied immediately
during the change of the value.
5. 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 genset or engine 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.
Languages
Language settings – the list of languages stored in the controller configuration is displayed in the list of
possible languages.
The integrated color display unit supports the following languages
English
Chinese
Japanese
The integrated color display unit partially supports 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 integrated color display unit supports 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, Katakana, Hangul
Jamo, Thai
IMPORTANT: Even the language is configured in InteliConfig the specific language is unavailable
if the language is available in configuration (but empty) or the language is not supported by
integrated color 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
metering screens. Enter button has to be pressed first.
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.
Export / Import
Import Package – is dedicated for integrated color display unit firmware updated, controller firmware
update, controller archive update. Extension modules firmware update is not supported.
If the USB stick is not connected the import function is not available and visually indicated as a
greyed text.
The message dialog (Controller unit is not ready) is displayed if the controller is not in state ready
for programming (e.g. Gen-set running)
Export Archive – is dedicated for the entire archive export.
If the USB stick is not connected the export function is not available and visually indicated as a
greyed text.
The archive files (*.aig4) is exported to the fixed directory in the USB stick (root:/IG500/Archive.
The directory structure is automatically created if does not exist.
Export function is not protected by password.
The message dialog (Controller unit is not ready) is displayed if the controller is not in state ready
for archive export (e.g. Gen-set running)
Waiting dialog is displayed during the export proccess.
The message dialog is displayed after archive proccess.
Archive Export Successful if successfully exported.
Archive Export Failed if any error occurs during the export proccess.
Integrated color display unit is restarted after export proccess.
Note: Once the USB stick is inserted to the display unit the directory and its subdirecotries are created
automatically if does not exist.
IMPORTANT: Requested files to be imported must be saved in the root directory on a USB Stick.
File selection – is available if the conditions above (in section Import Package) is fulfilled
Only files with pcg3 extension is displayed.
Maximum 100 files (*.pcg3) in root is displayed.
The message dialog (Package Incompatible) is displayed if the incompatible pcg3 file is used
The message dialog (Invalid File) is displayed if the pcg3 file is invalid or corrupted
Import proccess
Import process – is available if the correct and compatible file is selected conditions above (in section
Import Package) is fulfilled
The import process is not allowed if at least one file in the package is not compatible with each other
– the Import button is not displayed.
When the Import process is started it is not possible to interrupt it.
Bar Message is displayed
Package Import Successful (green colored) – if success
Package Import Failed (red colored) – if any error during the process
IMPORTANT: Integrated color display unit firmware is updated in two steps. Firstly the firmware
is uploaded to the internal memory (indicated by icon ). The second step is the firmware
update from internal memory. The firmware is updated immediately after reboot using bootloader
(Indicated by progress bars and messages in limited GUI). After all the unit is automatically
started with new firmware.
IMPORTANT: Only in some special cases the import process using USB stick must be performed
twice. This situation is always described in New Feature List with more detailed information.
IMPORTANT: Only FAT16 and FAT32 file system on USB stick are supported.
Note: If the USB stick is plugged in the Import/Export page is automatically displayed.
Note: If the import proccess fails try the import proccess again.
Note: If the import proccess fails try to create new package file using InteliConfig.
Note: Export / Import screen is accessible using the buttons combination Enter + Menu just only from the
metering screens. Enter button has to be pressed first.
Service QR Codes
Service QR Codes screen is dedicated for easy maintenance and technical support. Together with ComAp
Smart Hint application the usage of the small display is even easier.
1. Password Reset – Password Reset function is dedicated for simple handling of the password reset
procedure. Scan the QR code using the Smart Hint application and send the reset code to the ComAp
technical support.
2. Controller Statistics – Controller statistics data gathered during the controller operation. Smart Hint
application displays the controller statistic data in one place in a readable text form and could be further
investigated.
3. System Info – System data info in one place in Smart Hint application.
Note: Settings screen is accessible using the buttons combination Enter + Menu just only from the metering
screens. Enter button has to be pressed first.
Service screen
The service screen is the special screen (bitmap) defined and stored in the controller. The service screen is
also accessible from administration as a last list item. The purpose of the service screen is to allow the site
administrator to put into the display (resp. controller) important data for technical support. The status screen
can be uploaded using the InteliConfig. By default the service screen is predefined by ComAp.
Note: Service screen is accessible using the buttons combination Enter + Menu just only from the metering
screens. Enter button has to be pressed first.
Password item – the item dedicated for the login and logout to the controller.
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
Note: Each Access Rights password can be changed by inserting old password and new password.
IMPORTANT: If the setpoint is protected by password the password dialog appears when the
attempt to password change is performed.
IMPORTANT: Be aware there is a brute force algorithm protection implemented. If the brute force
protection is active then the user is informed by Invalid Password message even the password is
inserted correctly.
Important values
The important controllers values and system buttons are displayed by default and accessible from the Home,
Power and Synchro metering screens. The breaker status, controller status and system timer are also
displayed on the Home metering screen.
Note: The adjustment of the important values can be made using powerfull tool Screen Editor (in
InteliConfig).
Password change
The password change can be performed using the Password menu in Setpoint page.
1. Choose the item for which access right you want to change password.
2. Using password change dialog enter correct old and new requested password and confirm the choice.
3. The password for respective Access Rights level is changed.
Backlight Timeout – can be set at a range of 1 to 254 minutes or Disabled. Disabled means the backlight
never shuts down.
Brightness control
1. If the manual mode is chosen the user is responsible for his own backlight intensity.
2. If the External mode is chosen the display unit expects the external resistor (potentiometer) on its Analog
input. The type of sensor can be set in InteliConfig.
Brightness intensity – The backlight intensity can be adjusted using the value dialog from 1 up to 100%. It is
not possible to set 0 to avoid total shutdown of backlight intensity.
IMPORTANT: It is strongly recommended to use maximum backlight if it is really needed. The
temperature of the LCD grows linearly with the set of LCD backlight intensity. The product
lifetime is temperature dependent. In general it means higher temperature lower lifetime.
IMPORTANT: It is strongly recommended to set the Backlight Timeout to reasonable time (e.g 5
minutes). If the backlight is off then any button press switch on the backlight again.
State messages
Note: Lamps can by disabled during prestart phase. Checkbox: Ignore ECU lamps during prestart is located
in InteliConfig -> Controller Configuration -> Modules -> ECU module -> Electronic control unit settings.
Note: Aftertreatment support can be disabled. Aftertreatment HMI Screen is hidden and alarms related to
aftertreatment are not shown. Use the checkbox: Disable aftertreatment support located in InteliConfig ->
Controller Configuration -> Modules -> ECU module -> Electronic control unit settings.
Image 5.65 The lamp state will be solid when signal is value 1, 2 = blink, 5 = blink fast
Note: The automatic start of the Gen-set due to AMF function can be disabled by the binary inputs AMF
START BLOCK (PAGE 694) or MAINS FAIL BLOCK (PAGE 719).
If the setpoint MCB Opens On (page 395) is set to Gen Run, the MCB is opened once the generator
voltage is within limits (after Minimal Stabilization Time (page 332) elapses).
After Open Transfer Min Break (page 436) elapses, the GCB is closed and the Gen-set begins to supply
the load.
After the mains is restored to normal, the timer Mains Return Delay (page 383) begins to count down.
Maximum time between closing of MCB and opening GCB is given by the setpoint Open Transfer Min
Break (page 436). After GCB is opened, the Gen-set cools down and stops.
IMPORTANT: Controller has this behavior only in AUTO mode!
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 GCB UV coil output is active the whole time the Gen-set is running (not in idle or
cooling). The MCB UV coil output is active when the controller is switched on. The output
UV coil
is deactivated for at least 2 seconds in the moment the breaker has to be switched off.
The output is intended for control of undervoltage coils of circuit breakers.
IMPORTANT: If a breaker feedback is configured, it will be required all the time. Otherwise alarms
will be issued.
There are three different time delays for breaker failure detection – see following diagrams.
When binary output breaker close/open is in steady state and breaker feedback is changed the breaker
failure is detected immediately (no delay).
When binary output breaker close/open opens there is 2 sec delay for breaker failure detection.
When binary output breaker close/open closes there is 2 sec delay for breaker failure detection.
Note: The speed 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 441) and Speed Governor Bias (page 430) setpoints.
There are two ways to connect the gen-set to the load (bus bar). This depends on the state of MCB FEEDBACK
(PAGE 721) and on the measured mains/bus voltage.
MINT
The measured bus voltage is also taken in account – it must be below 2 % of the nominal bus voltage and with
the open MCB (evaluated by MCB FEEDBACK (PAGE 721)) and also others GCB have to be open to close the
GCB without synchronization.
Note: If the group of Gen-sets is activated and multiple Gen-sets have to start simultaneously and connect to
the empty bus bar, there is an internal logic to prevent closing of more GCBs to the bus bar at the same
moment without synchronization. One of the Gen-sets will close the GCB, the others will wait and then they
will synchronize to the first one.
Synchronization
Synchronization process
Behavior of synchronization process depends on, which breaker is used for synchronization and in which
Controller Mode (page 317) is controller switched.
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. 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.
Synchronization types
There are two types of synchronization. Type of synchronization is adjusted via setpoint Synchronization
Type (page 446).
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 447). If the
synchronization is not successful within this period of time, the Stp Synchronisation Fail (page 916) alarm
will be issued.
Voltage matching
The Gen-set bus voltage is regulated to match the mains/bus voltage with tolerance given by the setpoint
Voltage Window (page 447). The regulation is adjusted by the setpoints Voltage Gain (page 443) and
Voltage Int (page 443).
Frequency / angle matching
The Gen-set bus frequency is regulated to match the mains/bus frequency first. The frequency regulation
loop is active (setpoints Frequency Gain (page 432) and Frequency Int (page 432)). Once the frequency is
matched, the regulation loop is switched to match the angle (setpoint Angle Gain (page 433)). When the
angle is matched with tolerance ± Phase Window (page 448) for a time given by the setpoint Dwell Time
(page 448) and the voltage is matched too, then the GCB is closed.
Note: The matching loops will continue to run even if the GCB close command has been already issued until
the controller receives GCB FEEDBACK (PAGE 715) or a GCB fail alarm occurs. After the feedback has been
received, the control loops are switched to load and power factor loops or load and power factor sharing
respectively.
Slip synchronization
The slip synchronizing is based on frequency / angle matching. The maximum duration of synchronizing is
given by the setpoint Synchronization Timeout (page 447). If the synchronizing is not successful within this
period of time, the Sync Timeout alarm will be issued.
If the generator frequency goes out of the window (either because generator frequency changes or
Mains/Bus frequency changes or setpoint Slip Frequency Window (page 449) changes) the controller will
reactivate regulation loop and try to reach the target value again. The sync timeout timer runs regardless of
this. If the generator frequency reaches the target frequency again the regulations are frozen and if the
generator frequency remains in the window for the time longer than setpoint Dwell Time (page 448) the
controller will continue in the standard sequence as seen in the previous case. *If the sync timeout elapses
the controller will immediately stop synchronization.
The window is limited by the actual measured Mains/Bus frequency if one of the window limits is below this
value (e.g. for setting where setpoint Slip Frequency (page 449) is set to 0.1 Hz and setpoint Slip
Frequency Window (page 449) is set to 0.5 Hz).
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.
Note: Due to the nature of this function it is possible that in limit cases the Gen-set controller will regulate the
generator frequency outside of protection limits. Example: Mains/Bus frequency is high but within its
protection limits (e.g. 50.9 Hz, limit is 51 Hz). Slip Frequency (page 449) is set to 0.5 Hz. This will cause
regulation loop of the gen-set controller to push the gen-set frequency to 51.4 Hz and eventually the
controller will issue overfrequency delay. It is recommended to set the setpoint Slip Frequency (page 449)
as low as possible that still enables successful synchronization. This minimizes the risk of this problem
happening. Furthermore when slip synchronization is used it is recommended to set Mains/Bus Frequency
protection limits to more rigid values than the generator frequency protection limits. In this case the setpoint
Slip Frequency (page 449) can be set to 0.1 Hz and the Mains/Bus Frequency overfrequency protection
limit is set to 50.9 Hz instead of 51 Hz. This will ensure that problematic state cannot be reached.
All Gen-set / controllers in linked groups cooperate with each other and perform load sharing, VAr sharing
and power management together. These functionalities are performed independently in each group, when
the groups are separated.
Example: 4 Gen-sets 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 backup 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 with a Gen-set stopping, if power management evaluates that available Actual Reserve is high enough
to stop a Gen-set.
Redundant system is a general term for applications where there are two controllers at each Gen-set. One is
the main controller, which controls the Gen-set in normal conditions, the other is the redundant controller,
which takes over the control when the main controller fails. Both controllers have identical firmware and most
of the configuration and setpoints. Only several things need to be adjusted/configured differently because of
the redundancy function itself.
IMPORTANT: If there are shared binary or analog outputs used on the controller (e.g. for system
start/stop), it is necessary to prepare the configuration in the way so each controller uses binary
or analog output set with different address. Configuration in Gen-set controllers then need to be
altered so it can receive signals from both controllers (e.g. using built-in PLC functions).
This system uses the CAN bus for detection whether the main controller is operational or not. If the redundant
controller has not received two consequent messages from the main one (~100 ms) it will take over the
system control – it activates the LBO CONTROLLER HEARTBEAT FAIL DETECT* (PAGE 754), which has to be
wired in such a way, that it disconnects the dead main controller from the control, connects the redundancy
controller instead and activates it by deactivation of the LBI EMERGENCY MAN (PAGE 704).
As there can be up to 16 pairs of controllers at the CAN2 bus it is necessary to select which main controller
(address) belongs to which redundant one. The setpoint Watched Controller* (page 305) is used for this
purpose. It must be adjusted to address of the respective main controller in each redundant controller and it
must be adjusted to 0 in each main controller.
IMPORTANT: Correct wiring of all inputs and outputs that should be used both by the main and
the redundant controller needs to be done. Please refer to the corresponding chapter for wiring
of binary inputs and outputs (Binary inputs (page 57) and Binary Outputs (page 58)).
IMPORTANT: Do not use Shared Binary Inputs/Outputs for LBO CONTROLLER HEARTBEAT FAIL
DETECT* (PAGE 754) -> LBI EMERGENCY MAN (PAGE 704) connection since the failed controller may
not interpret it correctly.
In the picture above the signal of LBO CONTROLLER HEARTBEAT FAIL DETECT* (PAGE 754) is used to disable
the main controller if it is lost from can CAN2 bus or CAN2 communication from that controller becomes
erratic. It is used also to disable the redundant controller when the communication on CAN bus is alright (it is
negated).
IMPORTANT: Use pulse signals for control of circuit breakers. LBO MCB ON COIL (PAGE 782) and
LBO MCB OFF COIL (PAGE 781) should be used to prevent sudden opening for a short period of
time when the controller fails and to ensure proper function of redundancy.
3. LBI state received from CAN2 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 Remote
Start/Stop signal.
4. LBI function state transmitted via CAN2 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.4.10 Droop
IMPORTANT: Droop is relevant only for MINT application.
The DROOP is primarily intended for Multiple parallel operation in Island to ensure the load sharing and VAr
sharing when intercontroller communication fails. The Active and Reactive power is not regulated based on
data communicated between the units (isochronous regulation) but the speed request and voltage request is
calculated from actual voltage and actual frequency of the system (the measured Voltage and frequency of
whole system is always equal). Actually the speed request is correlative to active power and the voltage
request is correlative to reactive power. The correlation is the decreasing function and it creates the negative
feedback of regulation.
Function is activated via setpoint Load/Var Sharing Regulation Type (page 451). There are two droop
modes – emergency droop and droop.
Equation:
Required frequency = Nominal frequency – [(Nominal frequency * Frequency Droop Slope (page 452) /
100) * ( Active power / Nominal power – Frequency Droop Offset (page 453) / 100)).
Voltage droop
GAS engine
The setpoint Fuel Solenoid (page 324) must be switched to the Gas position.
The maximum duration that the output STARTER 1 (PAGE 794) is energized is determined by the setpoint
Maximum Cranking Time (page 326). If the engine does not start within this period, outputs STARTER 1
(PAGE 794) and FUEL SOLENOID (PAGE 763) are de-energized and a pause with length determined by
Cranking Fail Pause (page 326) will follow. PRESTART (PAGE 789), GLOW PLUGS (PAGE 771) and
IGNITION (PAGE 775) outputs are active during the pause. After the pause has elapsed, the next start
attempt is executed. The number of start attempts is given by the setpoint Cranking Attempts (page
325).
Once the engine is started, the Idle period follows. The binary output IDLE/NOMINAL (PAGE 775) remains
inactive (as it was during the start). The idle period duration is adjusted by the setpoint Idle Time (page
330).
After the idle period has finished, the output DESCRIPTION (PAGE 775) is activated and the start-up
sequence is finished. The Stabilization (page 222) phase follows.
The order of sequence is affected by the actual status of LBI STARTER PRIORITY (PAGE 734) (0-Starter 1, 1-
Starter 2). Can be used for disabling a particular starter.
LBIs STARTER 1 DISABLED (PAGE 734), STARTER 2 DISABLED (PAGE 734). If the LBI Starter 1,2 Disabled state
is 1 then the Starter 1 ,2 will be skipped in the sequence. Skipped starter is not counted as cranking attempt.
In case both starters are disabled, controller is in the state not ready.
Value Num Starts (page 668) stores the total successful starts of both starters.
In timer mode select Once. In timer settings adjust date and time of occurrence of timer. Also adjust the
duration of timer.
Daily mode
Set-up via InteliConfig
To set-up timer via InteliConfig go to the setpoint ribbon, setpoint group scheduler and setpoint Timer 1
Setup.
Note: First, the timer functions must be adjusted via setpoint Timer 1 Function (page 500).
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. Then select the xth day of repetition
(Timer 1 Refresh Period (page 506)) and behavior of timer on weekends (Timer 1 Weekends (page 507)).
Example: On image example first start of timer will be 1/1/2016 at 12:00. Duration will be 1 hour. Timer will
be activated again every 3rd day at 12:00 for 1 hour including weekends.
Weekly mode
Set-up via InteliConfig
To set-up timer via InteliConfig go to the setpoint ribbon, setpoint group scheduler and setpoint Timer 1
Setup.
Note: First, the timer functions must be adjusted via setpoint Timer 1 Function (page 500).
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. Then select the xth week of
repetition (Timer 1 Refresh Period (page 506)) and days when timer should be active (Timer 1 Day (page
504)).
Example: On image example first start of timer will be 1/1/2016 at 12:00. Duration will be 1 hour. Timer will
be again activated every 2nd week on Monday, Wednesday and Friday at 12:00 for 1 hour.
Monthly mode
Set-up via InteliConfig
To set-up timer via InteliConfig go to the setpoint ribbon, setpoint group scheduler and setpoint Timer 1
Setup.
Note: First, the timer functions must be adjusted via setpoint Timer 1 Function (page 500).
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. Then select the type of monthly
repetition and the xth day of repetition (Timer 1 Repeat Day In Month (page 504)). Than select the xth
month of repetition.
Example: On image example first start of timer will be 1/1/2016 at 12:00. Duration will be 1 hour. Timer will
be activated again every 2nd day in 2nd month at 12:00 for 1 hour.
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. Then select the type of monthly
repetition, the xth week of repetition and days in week. Than select the xth month of repetition.
Example: On image example first start of timer will be 1/1/2016 at 12:00. Duration will be 1 hour. Timer will
be activated again every 2nd week in 2nd month on Monday, Wednesday and Friday at 12:00 for 1 hour.
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. Then select the interval of
repetition (shorter than 1 day).
Example: On image example first start of timer will be 1/1/2016 at 12:00. Duration will be 1 hour. Timer will
be activated again every 4th hour for 1 hour.
5.4.16 E-Stop
Binary outputs for the control of some essential functions are internally wired as "safe", meaning that their
deactivation is directly bound with the dedicated Input E-STOP (not evaluated as the LBI in the controller).
These BO are fully configurable and are used e.g. for the Starter and Fuel control.
The emergency stop circuit must be secured.
The power supply of the associated binary outputs (BOUT1 and BOUT2) is supplied by the E-STOP input,
not by the + battery voltage.
Note: There is no difference in the way of configuration of all binary outputs. Binary outputs BO1 (Starter),
BO2 (Fuel Solenoid) are intended for these functions (not dedicated).
There is a measurement of E-STOP input voltage analogically and setting the binary value (representing
emergency stop input level) based on comparison of the measured voltage to two analog levels, which are
derived from the controller supply voltage (battery voltage) perceptually.
If the input voltage of E-stop is higher than high comparison level (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 (ex. lower than 60% of the supply voltage),
then E-stop is activated.
5.4.17 Firewall
The firewall function allows to restrict the access to the controller application services (ComAp/TCP server,
MODBUS/TCP server etc.) or to the specific computers or networks. Firewall can be activated on Ethernet port.
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.
Note: LBIs can be renamed during configuration. We suggest you to rename them based on used function.
IMPORTANT: You can not change value of setpoint which has active Forced Value function.
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 from tab LBI/LAI.
List of already configured Forced Values for specific setpoint. First row has highest priority.
Options for adding, removing and editing Forced Values and options for changing order.
Forced value button when at least one forced value is configured Forced value icon when setpoint is
for the setpoint. forced.
Note: Setpoint Connection Type doesn’t require to configure user setpoint. The alternative value can
be selected directly in forced value configuration.
Note: When the engine was running before and all above conditions are fulfilled, additional 2 s delay is
necessary to confirm "still engine".
When any engine running conditions are observed in still engine, then the Wrn Stop Fail (page 874) is
activated with the following delays:
For generator voltage from 10 V to < 50 % of nominal voltage, Wrn Stop Fail has delay 1 s
For generator voltage > 50 % of nominal voltage, Wrn Stop Fail has delay 200 ms
Oil pressure > Starting Oil Pressure (page 328), Wrn Stop Fail has delay 1 s
Binary input OIL PRESSURE (PAGE 724) is in logical 0, Wrn Stop Fail has delay 1 s
For detected RPM, there is no delay.
If the total stopping time will exceed setpoint Stop Time (page 336) then the Wrn Stop Fail (page 874) and
binary outputs for stopping are activated. The controller will continuously try to stop the engine.
Image 5.92 Engine stops after first Stop Time (page 336)
Note: It is possible to clear history on users demand. To execute history log clearing, navigate to History
page in InteliConfig and select the option ClearHistory.
Record structure
Note: When some setpoint is changed, its number of the communication object is written in the history log.
Vector
MCB GCB Vector Shift
Shift CB Action
status status Protection
Selector
MCB or Parallel or Enabled Opens MCB or GCB based on setpoint
1 1
GCB (No influence) Vector Shift CB Selector.
No
0 1 No influence No action (GCB stays alaways closed)
influence
No
1 0 Parallel No action MCB stays closed
influence
1 0 GCB Enabled No action MCB stays closed
1 0 MCB Enabled MCB opens
If a vector shift is detected and consequently the MCB is opened, however mains voltage and frequency
remain in limits, the MCB is then closed again (synchronized) after Mains Return Delay (page 383) as the
mains is evaluated as healthy.
If a vector shift is detected and consequently the GCB is opened, however mains voltage and frequency
remain in limits, the GCB is then closed again (synchronized) immediately (no delay).
ROCOF
The Rate of Change of Frequency function is the fast protection for mains decoupling. It monitors the change
of frequency and if it gets changed dramatically, the protection is issued.
Protection is enabled via setpoint ROCOF Protection (page 398). Limit of protection is adjusted via
setpoints ROCOF df_dt (page 399) and ROCOF Windows Length (page 399). When protection is
activated, the breaker is opened. Which breaker is opened is adjusted via setpoint Vector Shift CB Selector
(page 400).
Mains Measurement Q
If Mains Measurement Q (page 301) = Mains CT then Mains Measurement Q (page 301) is counted
from the current which is measured onMains current.
If Mains Measurement Q (page 301) = Analog Input then Mains Measurement Q (page 301) is taken
from the LAI MAINS MEASUREMENT Q (PAGE 809). Mains current can be still measured if Mains
Measurement P (page 300) = Mains CT.
If Mains Measurement Q (page 301) = None then Mains Measurement Q (page 301) is not counted
because there is no current measurement.
In order to ensure proper functionality you shall pay extra attention to settings ECU address and
Controller address. ECU address has to be always unique whereas Controller address is required to be set to
same value as Subgroup: Controller Address (page 322) of the Controller Unit that sends commands
frames to this ECU.
Note: Module name effects name of the value screen shown on the controller.
Note: ECU Blocks 5-8 are only available in the Extended features version.
IMPORTANT: The controller in MINT application does not control the MCB! Only the MCB position
is evaluated from the binary input MCB FEEDBACK (PAGE 721) and the position is the basic source
of information for switching between island and parallel to mains operation.
If the bus bar is empty, the first Gen-set will close its GCB 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 will close the GCB 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 730) is deactivated or the STOP button is pressed, the GCB will be opened and the Gen-set will go to
cool down phase.
Behavior of controllers is adjusted via Power management (page 198) settings. Please see this chapter for
more information.
The following binary inputs can be used to force one respective operating mode independent of the mode
setpoint selection:
Remote OFF (page 729)
Remote TEST (page 731)
Remote MAN (page 728)
Remote AUTO (page 728)
OFF
No start of the Gen-set is possible. If the Gen-set is running, it is not possible to switch directly to OFF mode.
First you have to stop the engine. After that the controller will stay in Not ready status and cannot be started
any way. The MCB is closed permanently (MCB Opens On (page 395) = GenRun) or is open or closed
according to whether the mains is present or not (MCB Opens On (page 395) = MainsFail). No AMF or
Power management function will be performed. The buttons MCB , GCB , Start and Stop
including the appropriate binary inputs for external buttons are not active.
Note: When engine is running, it is not possible to switch Gen-set to OFF mode
MAN
The engine can be started and stopped manually using the START and STOP buttons (or external buttons
wired to the appropriate binary inputs) in MAN mode.
When the engine is running and generator parameters are in the limits, GCB can be closed to a dead bus or
synchronization can be started by the GCB button.
Also MCB can be closed and opened manually using the MCB button, if mains is present. MCB can be
opened manually after mains failure (it is not tripped in case of mains failure), but it can not be closed with
failed mains.
Controller does not respond to external signals and/or conditions. The gen-set is fully in manual control; there
is no automatic way to stop it (except protections). The Gen-set stays running until STOP button is pressed.
Controller does not take place in Power management (page 198) in MINT application.
AUTO
Gen-set is controlled based on external signal (REMOTE START/STOP (PAGE 730)) or by conditions (AMF,
Power management system, …).
When one condition deactivates the engine does not stop if another condition for automatic starts is active.
The controller does not respond to buttons Start , Stop , MCB ON/OFF and GCB ON/OFF .
IMPORTANT: If a red alarm is present and the Gen-set is in AUT mode, it can start by itself after
all red alarms become inactive and are acknowledged!!! To avoid this situation, adjust the
setpoint Fault Reset To Manual (page 318) to the Enabled position.
TEST
The behavior of the controller in TEST mode depends mainly on the setting of the setpoints and binary inputs.
TEST mode can be activated via front panel of controller or via binary input REMOTE TEST (PAGE 731).
The Gen-set will be started when the controller is put to TEST mode and will remain running unloaded. If a
mains failure occurs, the MCB will be opened and after Open Transfer Min Break (page 436) the GCB will
be closed and the Gen-set will supply the load. After the mains have recovered, the delay Mains Return
Delay (page 383) will count down and if it elapses and the mains is still ok, the controller will transfer the load
back to the mains after Open Transfer Min Break (page 436) and the Gen-set will remain running unloaded
again until the mode is changed.
Power down
When a stop command is received the Gen-set load is ramped down before opening the GCB. The ramp
speed is given by the setpoint Load Ramp (page 440) and the end level is given by Generator Unload GCB
Open Level (page 439).
When the GCB button is pressed, the Gen-set load is ramped down before opening the GCB as well. But after
the GCB has been opened, the gen-set remains running until a stop command comes or the GCB is pressed
again to reclose the GCB.
Load control
If MCB FEEDBACK (PAGE 721) is active (parallel to mains operation) the load of group of the Gen-sets is
controlled to reach the power defined by setpoint #System BaseLoad (page 297). Each loaded Gen-set
takes equal part (relative to their nominal power) from #System BaseLoad (page 297) requested value. The
load is regulated locally in each controller by load control regulation loop, load-sharing regulation loop is not
active. The setpoint #System BaseLoad (page 297) is also used for determining which Gen-sets have to run
or not. Control is adjusted via setpoints Load Int (page 434) and Load Gain (page 434).
PF control
If MCB Feedback (page 721) is active (parallel to mains operation) the value of PF (power factor) of group of
the Gen-sets is controlled to reach the PF defined by setpoint #System Power Factor (page 297). The PF is
regulated locally in each controller by PF control regulation loop, VAr-sharing regulation loop is not active.
Control is adjusted via setpoints PF Gain (page 444) and PF Int (page 444).
Power down
When a stop command is received the Gen-set load is ramped down before opening the GCB. The ramp
speed is given by the setpoint Load Ramp (page 440) and the end level is given by Mains Unload MCB
Open Window (page 439).
When the GCB button is pressed, the Gen-set load is ramped down before opening the GCB as well. But after
the GCB has been opened, the Gen-set remains running until a stop command comes or the GCB is pressed
again to reclose the GCB.
Load control
Load control ensures that the gen-set keep the certain load in parallel to mains operation (MCB FEEDBACK
(PAGE 721) and GCB FEEDBACK (PAGE 715) = active).
There are available two modes of load control. Type of control is adjusted via setpoint Load Control PTM
Mode (page 290).
Note: In both modes, the lower level of the power is always limited by the setpoint MINIMAL POWER PTM
(PAGE 362). If the requested load (given by the active load control mode, e.g. Baseload, Import/Export) is
below this limit the requested load is limited to the level adjusted by this setpoint.
Baseload
Load Control PTM Mode (page 290) = Baseload. Gen-set produces amount of the power given by setpoint
Baseload (page 294). The rest of power is supplied from the mains or exported to the mains (depends on
proportions of load and Baseload (page 294) setpoint). Even in baseload control mode can be the
Import/Export limited. This function can be activated by setpoint Import/Export Limitation (page 296) =
Enabled. Then the request for the power of the Gen-set operating in baseload can be limited to prevent the
Import/Export go below the limit given by setpoint Import Load (page 295).
Example: Baseload = 1000 kW, load = 700 kW, Import load = 100 kW. Then the Baseload request will be
limited to 600 kW to prevent the Import power to go below 100 kW.
Example: Baseload = 1000 kW, load = 700 kW, Import load = -100 kW. Then the Baseload request will be
limited to 800 kW to prevent the Import power to go below -100 kW (actually it is limitation of the export).
It is possible to set the baseload by LAI LOAD CONTROL: ANEXT BASELOAD* (PAGE 808). For this purpose the
setpoint Load Request Source (page 291) has to be switched to Analog External Value.*
Note: *) Only available in the Extended features version. For more information see Extended features on
page 154.
PF control
PF control ensures that the Gen-set keep the certain reactive load in parallel to mains operation (MCB
Feedback (page 721) and GCB Feedback (page 715) = active).
There are available two modes of PF control. Type of control is adjusted via setpoint PF Control PTM Mode
(page 292).
Base PF
The power factor on the Gen-set is kept on the level given by the setpoint BasePower Factor (page 295)
regardless the load demand. The rest of demanded reactive power is supplied from the mains. Values >1
means that capacitive reactive power is supposed to be imported from mains, values <1 means that inductive
reactive power is imported from the mains.
Import/Export
Gen-set produces the certain amount of reactive power to keep constant PF imported from the mains
regardless the demand of the load. The requested power factor import is given by setpoint Import Power
Factor (page 296). Values >1 means that the Gen-set is pushing the capacitive power to the system (system
Gen-set – Load – Mains), values <1 means that the Gen-set is pushing the inductive power to the system.
Transfers of load
Type of transfer of load between mains and Gen-set and vice versa is adjusted via setpoints Transfer Gen
To Mains (page 438) and Transfer Mains To Gen (page 437).
Types of transfers
Transfer of the load from generator to mains and vice versa without parallel work and
Open synchronization (one breaker opens and second is closed – checking feedbacks). The
setpoint Open Transfer Min Break (page 436) sets the minimal duration of break.
Transfer of the load from generator to mains and vice versa with synchronization and
parallel work. The maximal time of parallel work is given by setpoint Close Transfer
Close Only
Max Duration (page 436).
In case of synchronization fail, MCB stays close and Gen-set is stopped.
Transfer of the load from generator to mains and vice versa with synchronization and
parallel work. The time of parallel work is given by setpoint Close Transfer Max
Close Primarily
Duration (page 436).
In case of synchronization fail, open transfer is done.
Logical
binary AUTO mode TEST mode
input
When activated: The Gen-set is started anyway due to the
starts Gen-set TEST mode.
the transfer of load from mains to When activated:
FORCE
generator is done the transfer of load from mains to
ISLAND
When deactivated: generator is done
(PAGE 705)
the transfer of load from generator to When deactivated:
mains is done the transfer of load from generator
cooling and stopping of the Gen-set to mains is done
When activated:
The Gen-set is started anyway due to the
starts Gen-set
TEST mode.
if mains parameters ok –
When activated:
Remote synchronize, run in parallel
if mains parameters ok –
Start/Stop if mains parameters not ok – run in
synchronize, run in parallel
(page 730) island
When deactivated:
When deactivated:
unloading, of the Gen-set, opening
unloading (if Gen-setwas in parallel),
GCB
cooling and stopping of the Gen-set
FORCE When activated: The Gen-set is started anyway due to the
Type of transfer of load between mains and Gen-set and vice versa is adjusted via setpoints Transfer Gen
To Mains (page 438) and Transfer Mains To Gen (page 437).
Number of
Number of blocks
PLC block blocks
Extended features
IG500 G2
OR/AND 32 64
XOR/RS 16 32
Comparator with
4 4
hysteresis (Comp Hyst)
Comparator with delay
18 18
(Comp Time)
Comp Win 4 4
Math Fc 2 4
Interpolation - 2
Math (AxB/C)±D - 2
Timer 2 2
Delay 8 8
Ramp - 2
Up/Down - 2
Inc/Dec - 2
LowPassFlt - 1
Note: To delete a PLC block just click on it and press delete button. Also the delete selection function can be
used.
Note: To see context help for selected PLC block just press the F1 button.
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 the following categories:
Bin. values – this category contains all binary values available in the controller as binary inputs,
logical binary outputs, fixed protection states, user buttons, user protection states.
PLC outputs – this category contains all PLC blocks binary outputs available in the controller.
If you create an analog input, you can select a source from the 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.
Outputs
Sheet output is located at the right side of a sheet. Follow the procedure below to add or edit an input.
Double-click on a free output position to add a new sheet output.
Double-click on an already created output to configure the output onto a controller output terminal or a
logical binary input (first some PLC block output must be connected to this output to enable configuration
of output).
IMPORTANT: It is necessary to click on Connect button after selecting the output. Otherwise PLC
output is not connected to output.
Creating wires
Wires can be created between PLC inputs and PLC blocks and between PLC blocks and PLC outputs.
IMPORTANT: Keep the order of starting and finishing connection points. Wires between inputs
and blocks have to start from inputs. Wires between blocks and outputs have to start from
blocks.
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 pointer, analog values are marked with green pointer.
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!!!
Hints
Use this function to enable or disable quick hints for blocks (controller help is not affected by this function).
PLC monitor
PLC Monitor is a powerful tool for monitoring your PLC. Just click on PLC Monitor button on main InteliConfig
page to see your PLC. Active inputs and outputs are a blue color. Also wires with active signals are blue color.
IMPORTANT: It is not possible to edit PLC in PLC Monitor tool.
Note: Prelubrication Cycle has to be enabled, i.e. Prelubrication Time (page 353) != OFF
In this situation alarm ALI Not Lubricated (page 867) is active until the first lubrication cycle is completed.
Start of the engine is blocked for this period.
After the period adjusted by Prelubrication Time (page 353) the LBO PRELUBRICATION PUMP (PAGE 788) is
deactivated for the period adjusted by Prelubrication Pause (page 353) after which whole cycle repeats.
The engine is allowed to be started up when LBO PRELUBRICATION PUMP (PAGE 788) is active due to standard
Prelubrication cycle. In this case LBO PRELUBRICATION PUMP (PAGE 788) is deactivated with activation of
LBO CRANKING (PAGE 754) and stays deactivated until the engine is running.
In case of unsuccessful start Prelubrication cycle starts with active phase (LBO PRELUBRICATION PUMP (PAGE
788) is activated). In case of successful start and subsequent STOP of the engine (no matter of purpose)
Prelubrication cycle continues with deactivated phase (LBO PRELUBRICATION PUMP (PAGE 788) is
deactivated).
Alarmlist indication +
1 AHI - - - - - - -
history record
Alarm only 1 - - - - - -
AL COMMON WRN
Warning 1 Wrn - - -
(PAGE 747)
AL COMMON SD
Shutdown 2 Sd
(PAGE 746)
Breaker Open & Cool AL COMMON BOC
2 BOC
Down (PAGE 745)
AL COMMON STP
Slow stop 2 Stp
(PAGE 746)
Shutdown Override 2 Sd -
Setpoint options
Options Description
Enable Protection is enabled
Disable Protection is blocked
Disabling of the protection can be forced by LBI PROTECTION FORCE DISABLE 1 (PAGE
ExtDisable
725)
Generator protections
Setpoint for protection ON / OFF Alarms / Protection name
Always active BOC Short Circuit (page 915)
IDMT Generator >A Protection (page 373) BOC Overcurrent IDMT (page 911)
Current
Generator Current Unbalance Protection
BOC Current Unbalance (page 884)
(page 374)
Generator Frequency Protection (page BOC Generator Overfrequency (page
379) 899)
Frequency
Generator Frequency Protection (page BOC Generator Underfrequency
379) (page 899)
Mains protections
Alarms / Protection name
Mains/Bus Overfrequency (page 880)
Frequency
Mains/Bus Underfrequency (page 880)
ALI Mains Ph L1 Inverted (page 857)
ALI Mains Ph L2 Inverted (page 857)
ALI Mains Ph L3 Inverted (page 858)
ALI Mains Ph Rotation Opposite (page 858)
Others
ALI Bus Ph L1 Inverted (page 843)
ALI Bus Ph L2 Inverted (page 843)
ALI Bus Ph L3 Inverted (page 843)
ALI Bus Ph Rotation Opposite (page 843)
MP Mains/Bus L1 Overvoltage (page 900)
MP Mains/Bus L1 Undervoltage (page 900)
MP Mains/Bus L2 Overvoltage (page 901)
MP Mains/Bus L2 Undervoltage (page 901)
MP Mains/Bus L3 Overvoltage (page 902)
MP Mains/Bus L3 Overvoltage (page 902)
MP Mains/Bus L1L2 Overvoltage (page 900)
Voltage
MP Mains/Bus L1L2 Undervoltage (page 901)
MP Mains/Bus L2L3 Overvoltage (page 902)
MP Mains/Bus L2L3 Undervoltage (page 902)
MP Mains/Bus L3L1 Overvoltage (page 903)
MP Mains/Bus L3L1 Undervoltage (page 903)
Mains Voltage Unbalance ph-n (page 858)
Mains Voltage Unbalance ph-ph (page 858)
Source
Analog values Binary states
Binary inputs
Analog inputs
Controller, Modules, ECU
Controller, Modules
Binary outputs
Values
PLC
ECU, Generator, Mains, others
Protection states
Statistics
LBOs
Protection activation
Type Name of activation Description
Over Limit Protection is activated if value is over limit.
Over Limit + Fls Protection is activated if value is over limit or in a fault state.
Analog Under Limit Protection is activated if value is under limit.
Under Limit + Fls Protection is activated if value is under limit or in a fault state.
Fls only Protection is activated if value is in a fault state.
True Protection is activated if value is Logical 1.
TrueOrFls Protection is activated if value is Logical 1 or in a fault state.
Binary
False Protection is activated if value is Logical 0.
FalseOrFls Protection is activated if value is Logical 0 or in a fault state.
Alarmlist indication +
1 AHI - - - - - - -
history record
Alarm only 1 - - - - - -
AL COMMON WRN
Warning 1 Wrn - - -
(PAGE 747)
AL COMMON SD
Shutdown 2 Sd
(PAGE 746)
Breaker Open & Cool AL COMMON BOC
2 BOC
Down (PAGE 745)
AL COMMON STP
Slow stop 2 Stp
(PAGE 746)
Shutdown Override 2 Sd -
Protection blocking
Block Type Description
All the time The protection is not blocked. It can be blocked only by LBI SD OVERRIDE (PAGE 733).
Run Only The protection is blocked depending on engine state and time defined by setpoint Run
Block Delay Only Block Delay (page 334). It can also be blocked by LBI SD OVERRIDE (PAGE 733).
The protection is blocked by LBI PROTECTION FORCE DISABLE 1 (PAGE 725) or by LBI SD
Force Block
OVERRIDE (PAGE 733).
The protection is blocked depending on engine state. It is unblocked once Maximal
Electrical
Stabilization Time (page 333) is elapsed or GCB is closed. It can also be blocked by LBI
Protection
SD OVERRIDE (PAGE 733).
Note: LBI SD OVERRIDE (PAGE 733) (Shutdown Override) does not block evaluation of user protection
conditions and their visualization. They are recorded into alarm list or history. It only blocks their actions.
Shutdown Override blocks all level 2 (Sd,BOC) protection. It does not block level 1 (Wrn, AHI, Hist) or
protection of type SD OVERRIDE (PAGE 733).
Image 5.104 Run only block delay and electrical protection blocking
History record
Always – History is recorded all the time.
Once – History is recorded only once after fault reset.
Selecting the protection type see Fixed Protection types on page 184.
Selecting if the occurrence of a protection is recorded every time or only once after a Fault
Reset.
If user protection state is checked then created user protection has LBO located in Bin Values
in the Group: User Protection States (page 678).
Selecting the protection type see Fixed Protection types on page 184.
Selecting if the occurrence of a protection is recorded every time or only once after a Fault
Reset.
Selecting the input for delay.
Setpoints must have the correct resolution 0.1 and dimension [s]
Existing setpoint
If user protection state is checked then created user protection has LBO located in Bin Values
in the Group: User Protection States (page 678).
Protection states
Protection states are states of fixed and user protections. These states can be configured as binary output or
used in PLC logic.
Alarm management
The controller evaluates two levels of alarms. Level 1 – yellow alarm – is a pre-critical alarm that is only
informative and does not take any action regarding Gen-set control. Level 2 – red alarm – represents a critical
situation, where an action must be taken to prevent damage of the Gen-set or technology.
Alarm handling
There are four different alarm categories regarding the period when the alarms are evaluated. The category is
selectable for alarms assigned to binary/analog inputs and fixed for built-in alarms. The categories are the
following:
The alarm is evaluated all the time the controller is switched on.
The alarm is evaluated only when the engine is running. This type should be used for e.g. oil pressure.
These alarms begin to be evaluated after the engine has been started with the delay given by the setpoint
Run Only Block Delay (page 334).
The alarm is evaluated only when the generator is excited. These alarms begin to be evaluated after the
engine has been started and Maximal Stabilization Time (page 333) has elapsed or the GCB has been
closed. They remain evaluated until cooling has finished. Only Generator under/overvoltage, Generator
voltage unbalance and Generator under/overfrequency belong to this category. This category is not
configurable to binary and analog input alarms.
The alarm is evaluated only when LBI PROTECTION FORCE DISABLE 1 (PAGE 725) is not active.
If an alarm is being evaluated and the appropriate alarm condition is fulfilled, the delay of evaluation will start
to run. The delay is adjustable by a setpoint (in the case of built-in alarms, analog input alarms) or is adjusted
via configuration window in InteliConfig (in the case of binary input alarms). If the conditions persist, the alarm
will activate. The alarm will not activate if the condition is dismissed while the delay is still running.
After pressing the Fault reset button or activating the binary input FAULT RESET BUTTON (PAGE 705), all active
alarms change to confirmed state. Confirmed alarms will disappear from the Alarm list as soon as the
respective condition dismisses. If the condition is dismissed before acknowledging the alarm, the alarm will
remain in the Alarm list as Inactive.
Note: The input SD OVERRIDE (PAGE 733) can be used for temporary disabling of red alarms to shutdown the
engine. This input may be used in situations where providing the power is extremely important – e.g. if the
Gen-set drives pumps for fire extinguishers (sprinklers).
Warning (Wrn)
The alarm appears in the Alarm list and is recorded into the history log. Activates the output AL COMMON WRN
(PAGE 747) as well as the standard alarm outputs (HORN (PAGE 773) and ALARM (PAGE 748)).
Alarm only
The alarm appears in the Alarm list. Standard alarm outputs (HORN (PAGE 773) and ALARM (PAGE 748)) are
activated.
IMPORTANT: The Gen-set can start by itself after acknowledging the alarms if there is no longer
an active red alarm and the controller is in AUTO or TEST mode!
Shutdown (Sd)
The alarm appears in the Alarm list and is recorded into the history log. It causes immediate stop of the Gen-
set without unloading and cooling phase. Also GCB breaker will open. The Gen-set cannot be started again
Shutdown override
nd
If the Logical binary input SD OVERRIDE (PAGE 733) is closed, all 2 level protections are disabled to allow the
Gen-set run in an emergency situation, e.g. sprinkler devices power supply.
All protections are shown in Alarmlist and recorded into History, but the controller does not stop the engine
because of them. If the input is deactivated and some protections are still active or not yet reset, the controller
starts to take these protections into account and consequently stops the engine.
nd
All 2 level protections are locked out, except of these:
Emergency stop
Overspeed
Underspeed
Binary and analog protections configured as Sd override type. In fact this protection type means
"Unoverridable shutdown", i.e. it works the same way as standard shutdown protection, however it cannot
be overridden (blocked) by the SD OVERRIDE (PAGE 733) input.
Offload
The alarm appears in the alarmlist and is recorded into the history log. It causes immediate opening of the
GCB. In AUTO mode the Gen-set remains running for 60 seconds and then it's stopped by the standard stop
sequence. In MAN mode the Gen-set 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 Gen-set
is automatically started back and connected to the load if the condition for the Gen-set to be running persists.
It activates the output AL COMMON OFF LOAD (PAGE ) as well as the standard alarm outputs (HORN (PAGE
773) and ALARM (PAGE 748)).
Alarm list
Alarm list 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.
ECU alarms
The ECU alarms are received from the ECU. 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 engine fault codes list must be used to determine the reason.
Units
Metric 20 °C 10.0 bar 11.4 l/h
US 68 °F 145 psi 3.01 gph
Power Format
Range of some setpoints and values is changed significantly when different Power Formats are selected.
Affected setpoint are displayed during selection of power format.
The Power management function decides how many Gen-sets should run and selects particular Gen-sets to
run. The power management is applicable in cases multiple Gen-sets 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 Gen-sets based on the load demand, it can vastly improve the
system fuel efficiency. In other words, an additional Gen-set starts when the load of the system raises above
certain level. The additional Gen-set stops, when the load of the system drops down below a certain level.
The process of determining Gen-set 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 Gen-
set is not available for the power management.
The power management evaluates so called load reserve. The load reserve is calculated as difference
between actual load and nominal power of running Gen-sets. The reserve is calculated as absolute value (in
kW / kVA) or relatively to the nominal power of Gen-set(s) (in %). The setpoint #Power Management Mode
(page 408) is used to select the absolute or relative mode.
The automatic priority swapping function focuses on efficient run of Gen-set in regards to running hours and
Gen-set size.
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 Gen-sets 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.
Function of power management can be temporarily blocked after REMOTE START/STOP (PAGE 730) activation
a count down of #System Start Delay (page 411). The delay is given by setpoint Power Management
Delay (page 407). In this delay all Gen-sets where power management is enabled are running. After this
period elapses, only the Gen-set(s) needed according to the Power Management calculation stay running
and the rest is stopped.
Setpoint #Overload Next Start Delay (page 425) is used in case that #Overload Next Start Protection
(page 425) is enabled and Gen-sets are running at #Overload Next Start Level (page 425) 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. 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
Case #1
This case is used in island operation.
Case #2
This case is used in parallel to mains operation.
List of abbreviations:
ARstrt .. Actual Absolute reserve in kW or kVA – for engine start calculation.
ARstp .. Actual Absolute reserves in kW or kVA – for engine stop calculation.
RRstrt .. Actual Relative reserve in % – for engine start calculation.
RRstp .. Actual Relative reserves in % – for engine stop calculation.
ΣPgNom .. Sum of Nominal power of all Gen-sets on the bus.
ΣPg*Nom .. Sum of Nominal power of all Gen-sets on the bus apart of the one, which is going to be
stopped.
ΣPgAct .. Sum of Actual power of all Gen-sets on the bus = system load.
BaseLd .. Baseload is given by the setpoint #System BaseLoad (page 297)
Note: System starting sequences may be very different due to their complexity (i.e. Gen-sets which do not
take part in power management, various nominal powers etc.). Each system should be considered
individually.
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 Gen-set 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 Gen-set is
requested to join the already running Gen-set(s) to the bus.
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 203) and Relative power management (page 206).
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 423), the next Gen-set is actually started. The
standard starting sequence follows. Once the synchronization procedure is done, the GCB breaker is closed
and the Gen-set 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 Gen-sets on the bus is increased by the nominal power of
the additional Gen-set.
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 Gen-set stops when the load of the system drops below certain level to
avoid inefficient run of the Gen-set. Following figure depicts the situation when a Gen-set is requested to stop
due to the 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 203) and Relative power management (page 206).
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 Start Delay (page 423), the next Gen-set is actually requested to stop.
Once the Gen-set is unloaded, the GCB breaker is opened. Please note the sum of nominal power of all Gen-
sets on the bus is decreased by the nominal power of the stopped Gen-set. The cooling sequence follows
before the Gen-set is actually stopped. The Gen-set is ready to be started if the system load increases again.
Example: An example of absolute power management is shown on the image below. There are three
Gen-sets with following choice of setpoints:
#Starting
#Power #Stopping
Gen- Nominal Power #Priority Load
management Priority Load
set power management Auto Swap Reserve
mode Reserve X
X
Gen-
200 kW ENABLED ABS (kW) 1 DISABLED 100 kW 125 kW
set #1
Gen-
500 kW ENABLED ABS (kW) 2 DISABLED 100 kW 125 kW
set #2
Gen-
1 000 kW ENABLED ABS (kW) 3 DISABLED 100 kW 125 kW
set #3
As it is shown on both images above, the additional Gen-set is added once the actual load reserve is below
the level given by the appropriate setpoint of load reserve. The additional Gen-set 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 Gen-set is requested to start. This
value of the load is linked with the setpoint #Starting Load Reserve 1 (page 412) (or other selected reserve
set) in following way:
Sum of nominal power for start – #Starting Load Reserve 1 (page 412) (or other selected reserve set) =
value of load when additional Gen-set requested to start (e.g.: 700 kW - 100 kW = 600 kW).
The red dashed line depicts the value of load at which the additional Gen-set is requested to stop. This value
of the load is linked with the setpoint #Stopping Load Reserve 1 (page 412) (or other selected reserve set)
in following way:
Sum of nominal power for stop – #Stopping Load Reserve 1 (page 412) (or other selected reserve set) =
value of load when additional Gen-set requested to stop (e.g.: 700 kW - 125 kW = 575 kW).
#Starting
#Power #Stopping
Gen- Nominal Power #Priority Rel Load
management Priority Rel Load
set power management Auto Swap Reserve
mode Reserve X
X
Gen-
200 kW ENABLED REL (%) 1 DISABLED 35 % 40 %
set #1
Gen-
500 kW ENABLED REL (%) 2 DISABLED 35 % 40 %
set #2
Gen-
1 000 kW ENABLED REL (%) 3 DISABLED 35 % 40 %
set #3
Priorities
The priority of the Gen-set within the group is given by the setpoint Priority (page 409). Lower number
represents "higher" priority, i.e. a Gen-set with lower number starts before another one with higher number. In
other words, the setpoint Priority (page 409) means order in which Gen-sets are started and connected to
the bus. An example is shown on the figure below. There are four Gen-sets with following choice of setpoints:
#Starting
#Power #Stopping
Gen- Nominal Power #Priority Load
management Priority Load
set power management Auto Swap Reserve
mode Reserve X
X
Gen-
200 kW ENABLED ABS (kW) 4 DISABLED 50 kW 70 kW
set #1
Gen-
200 kW ENABLED ABS (kW) 3 DISABLED 50 kW 70 kW
set #2
Gen-
200 kW ENABLED ABS (kW) 2 DISABLED 50 kW 70 kW
set #3
Gen-
200 kW ENABLED ABS (kW) 1 DISABLED 50 kW 70 kW
set #4
By choosing the setpoint Priority (page 409) = 1, the Gen-set #4 is running all the time in the example shown
on the image above (AUTO mode selected, Power management enabled and LBI REMOTE START/STOP
(PAGE 730) ctivated).
The LBI TOP PRIORITY (PAGE 736) can be used to force priority 0 into the setpoint PRIORITY (PAGE 409).
Priority 0 is the "highest" one, which means the Gen-set will be running all the time while the power
management is switched on.
If more than one Gen-set have the same priority, they will act as "one big" Gen-set. There are methods of
automatic optimization of the priorities to achieve specific behavior of the group such as equalizing engine
hours of the Gen-sets or selection of optimal Gen-sets to run according to their size and current load demand.
The Gen-set 1 runs for 100 hours to equalize the RHE of both Gen-sets. The Gen-set 1 keeps running until
the difference between RHE1 and RHE2 exceeds #Run Hours Max Difference (page 426) (i.e. 10h). The
Gen-set 1 runs 100 + #Run Hours Max Difference (page 426) + 1 = 100 + 10 + 1 = 111 hours. After 111
hours the Gen-sets 2 has the lowest RHE and the difference between RHE1 and RHE2 is higher than #Run
Hours Max Difference (page 426). The Gen-set 2 runs 11 hours to equalize the RHE of both Gen-sets and
then additional #Run Hours Max Difference (page 426) + 1 hours (i.e. 11 + 10 + 1 = 22 hours). The
evolution of RHE1 and RHE2 is shown on the figure below.
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 Gen-sets are swapped after the duration
determined by following formula:
Case #2:
Gen-set 1 running hours = 0 -> running hours considered in RHE = 0 (0-RunHoursBase)
Gen-set 2 running hours = 0 -> running hours considered in RHE = 0 (0-RunHoursBase)
Gen-set 3 running hours = 0 -> running hours considered in RHE = 0 (0-RunHoursBase)
Each Gen-set has the same RHE = 0 h. By applying the SwapTime formula, we get the run time of Gen-set 1
before next swapping:
SwapTimeG1 = 0 – 0 + 10 + 1 = 11
Similar way, we get the run time of Gen-set 2 before next swapping:
SwapTimeG2 = 11 – 11 + 10 + 1 = 11
Finally, we get the run time of Gen-set 3 before next swapping:
SwapTimeG2 = 11 – 0 + 10 + 1 = 22
Please refer to figure below to understand the evolution of RHE of Gen-sets 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:
Gen-set 1 running hours = 250 -> running hours considered in RHE = 100 (150-RunHoursBase)
Gen-set 2 running hours = 450 -> running hours considered in RHE = 200 (250-RunHoursBase)
Gen-set 3 running hours = 750 -> running hours considered in RHE = 250 (500-RunHoursBase)
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 426) = 5 does not mean that Gen-sets 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 426) is set to 0 and all Gen-set in the group are at the
same initial point (RHE are equal), the Gen-set swapping happens every hour.
Efficiency
The gen-sets 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 410) = Efficiency.
Algorithm of function:
Following table provide an example of Gen-set selection in respect to the system load evolution. The table is
an example of Efficiency priority optimization function (#Power Management Mode (page 408) = ABS (kW)
and #Starting Load Reserve 1 (page 412) = 20 kW).
Total Running
System Relative load
Running Gen-sets Description power within PM
Load [kW] of Gen-sets [%]
[kW]
40 5 100 40
60 5 100 60
5 2 start
80 LDS Swap 300 26
2 [0h] 5 stop
100 2 [10h] 200 50
120 2 [20h] 200 60
2 [30h] 3 start
120 RHE Swap 400 30
3 [10h] 2 stop
Setpoint #Min Run Power (page 422) is adjusted to 400 kW. Once the MIN RUN POWER ACT 1 (PAGE 722) 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 Gen-set #2 (nominal power 500 kW), the Gen-set keeps running as at least 400 kW
has to be available. The Gen-set#1 (nominal power 200 kW) is not enough.
Speed, Frequency, Load sharing, Load regulation loops have one common output = Speed request. The
value of this output is always composed from the contribution of each of the regulation loops.
Voltage, PF, VAr sharing have one common output = Voltage request. 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 automat. If no regulation loop is active the speed governor output is kept on the level given by setpoint
Speed Governor Bias (page 430) or Voltage Regulator Bias (page 441) in case of voltage regulator
output.
Note: All regulation loops are PID, but only PI components are visible as setpoints.
IMPORTANT: Be ready to press emergency stop button in case the regulation loop would start to
behave unacceptable while it is being adjusted.
Note: The calibration must be done at the operational point of the analog input (e.g. 80 °C, 4.0 Bar etc..)
Note: Curves can be modified via InteliConfig. Some standard curves are also prepared in InteliConfig.
IMPORTANT: For right behavior of function Total Fuel Consumption, curve for analog input FUEL
LEVEL (PAGE 807) has to be in percentage and setpoint Fuel Tank Volume (page 348) has to be
adjusted correctly.
5.4.41 Stabilization
When the Engine start (page 142) sequence is finished, the Gen-set goes into the stabilization phase. There
are two timers (setpoints) in this phase:
Minimal Stabilization Time (page 332) starts to count down just after the idle period has finished.
Generator voltage and frequency are not checked (respective protections are not evaluated) and the GCB
cannot be closed even if the generator voltage and frequency are within limits.
Maximal Stabilization Time (page 333) starts to count down just after the idle period has finished.
Generator voltage and frequency are not checked (respective protections are not evaluated), but contrary
to the previous timer, the GCB can be closed if generator voltage and frequency are within limits.
In situations where the GCB is closed automatically (AUTO, TEST modes), the closing of GCB will occur as
soon as the generator voltage and frequency will get into limits and the Minimal Stabilization Time (page
332) has elapsed.
In the event that the generator voltage or frequency are not within limits of the Maximal Stabilization Time
(page 333) period, the appropriate protection(s) will be activated and the Gen-set will be cooled down and
stopped.
Note: The limits for the generator voltage and frequency are given by setpoints in the Group: Generator
settings (page 361).
Note: The value of the Minimal Stabilization Time (page 332) setpoint has to be lower than the value of
Maximal Stabilization Time (page 333) setpoint.
Note: If all generator parameters are OK and Minimal Stabilization Time (page 332) elapsed, indicates
that GCB is possible to close. In AUTO Mode GCB is closed in this moment automatically.
Note: The start-up sequence can be interrupted atn any time by a stop request.
SUS seq break-1 MCB gets closed in SUS start sequence (MCB FEEDBACK (PAGE 721) gets active)
MCB is open, Mains voltage is higher then level given by setpoint Dead Bus Limit
SUS seq break-2
(page 476)
SUS seq break-3 Bus voltage is higher than limit given by setpoint Dead Bus Limit (page 476)
The GCB FEEDBACK (PAGE 715) does not response until the Prestart Time (page
SUS seq break-4
327) elapsed.
When the setpoint Excitation Control (page 471) = External. The LBI SUS
EXCITATION BLOCK (PAGE 735) is not active before the SUS sequence starts or is
SUS seq break-5
deactivated during the SUS sequence in advance the LBO READY TO EXCITE
(PAGE 791) gets active.
RPM reached window given by SUS RPM Window (page 472) and stayed there
SUS seq break-6
for a while, but run away
The setpoint GCB Control Mode = Follow. When the GCB is tripped externally, the
No History record
SUS sequence has to be canceled. However no history record is needed because
needed
the reason is described by history record "GCB opened Externally".
Examples
Example 1
Active Application (page 669) = SPtM, Excitation Control (page 471) = Internal
RPM reaches SUS RPM Window (page 472) in time of SUS RPM Window Time Out (page 473)
Example 2
Active Application (page 669) = SPtM, Excitation Control (page 471) = Internal
RPM does not reaches SUS RPM Window (page 472) in time ofSUS RPM Window Time Out (page 473)
Example 3
Active Application (page 669) = SPtM, Excitation Control (page 471) = External
RPM reaches SUS RPM Window (page 472) in time of SUS RPM Window Time Out (page 473).
Example 4
Active Application (page 669) = SPtM, Excitation Control (page 471) = External
RPM does not reach SUS RPM Window (page 472) in time ofSUS RPM Window Time Out (page 473).
Examples
Example 1
Active Application (page 669) = MINT, Excitation Control (page 471) = Internal, #SUS Min Power 1
(page 473) = 2x Nominal Power (page 306)
Condition #SUS Min Power 1 (page 473) is met.
First two Gen-sets are in SUS RPM Window (page 472) with active LBO Ready To Excite (page 791) so
the condition #SUS Min Power 1 (page 473) is met → G3 opens the GCB3 and G1, G2 are excited (LBO
Example 2
Active Application (page 669) = MINT, Excitation Control (page 471) = Internal, #SUS Min Power 1
(page 473) = 3x Gen-set Nominal Power (page 306)
Condition #SUS Min Power 1 (page 473) is not met.
First two Gen-sets are in SUS RPM Window (page 472) and with active LBO Ready To Excite (page 791).
#SUS Min Power 1 (page 473) is equeal to the Nominal Power (page 306) of 3 Gen-sets, but G3 did not
activate Ready To Excite (page 791) in time of SUS RPM Window Time Out (page 473) → G3 opens the
GCB3 ad it is switched to standard start.
From opening of GCB3 the #SUS Excitation Delay (page 475) is counted. When the timer is up, G1 and G2
are excited, then G3 can be synchronised to the bus standard way.
Example 3
Active Application (page 669) = MINT, Excitation Control (page 471) = External, #SUS Min Power 1
(page 473) is ignored when excitation is external
MINT application
Load control loop is active in parallel to mains mode only (MCB feedback closed). Switch off other engines
while adjusting.
1. Set #System BaseLoad (page 297) setpoint to 30 % of one Gen-set.
2. Set Load Gain (page 434) to the same value as Angle Gain (page 433). Set Load Int (page 434) to
zero.
3. Start the Gen-set in MAN Mode, press GCB ON/OFF button to synchronize and close Gen-set to mains.
4. When GCB is closed, Gen-set load slowly increases to #System BaseLoad (page 297) value. Check
that Gen-set power is positive (CT polarity).
5. Increase Load Int (page 434) to unstable load control and decrease value by 30 % to insure stable
performance. When Load Int (page 434) factor is set to zero Gen-set load can differ from required
#System BaseLoad (page 297).
6. To adjust and optimize Load Int (page 434) change #System BaseLoad (page 297) several times
between 30 and 70 % of Nominal Power (page 306). Usually setting Load Int (page 434) to 100 % gives
optimal performance.
7. When Gen-set is running under full load check if
a. Speed governor output voltage value is not limited (it does not reach Speed Governor Low Limit
(page 430) or Speed Governor High Limit (page 431))
b. Speed governor actuator is not mechanically limited or operates in a small section of the throttle
range.
SPtM application
Load control loop is active in parallel to mains mode only (MCB feedback closed).
1. Set Load Control PTM Mode (page 290) = BASELOAD, set Baseload (page 294) setpoint to 30 %
Nominal Power (page 306) of Gen-set.
2. Set Load Gain (page 434) to the same value as Angle Gain (page 433). Set Load Int (page 434) to
zero.
3. Start the Gen-set in MAN Mode, press GCB ON/OFF button to synchronize and close Gen-set to mains.
4. When GCB is closed, Gen-set load slowly increases to Baseload (page 294) value. Check that Gen-set
power is positive (CT polarity).
5. Increase Load Gain (page 434) to unstable load control and decrease value by 30 % to insure stable
performance. When Load Int (page 434) factor is set to zero Gen-set load can differ from required
Baseload (page 294).
Commands
Commands can be sent from third party device via Modbus or remote connection (WebSupervisor). Following
types are available:
Command Description
When a command ON is received, User Button is activated. Subsequent commands ON
ON/OFF when User Button is active have no effect. If a command OFF is received, User Button is
deactivated. Subsequent commands OFF when User Button is inactive have no effect.
When a command TOGGLE is received, User Button is activated. Next command
TOGGLE
TOGGLE when User Button is active deactivates User Button and so on.
When a command PULSE is received, User Button is activated for the set duration.
Pulse length is 200 ms (user can use this pulse in PLC to prolong it using e.g. block
Delay)
PULSE
Consequent commands PULSE sent during duration of the pulse prolong the duration
accordingly.
When the setting of pulse duration is changed while the pulse is active, the current pulse
Note:
COMMAND ON – User Button remains active until COMMAND OFF or COMMAND TOGGLE comes
COMMAND OFF or COMMAND TOGGLE – User Button deactivates until COMMAND ON,
COMMAND TOGGLE or COMMAND PULSE come
Note: Table provides data which has to be written into MODBUS registers 4207-4209 (count 3) using
function 16 for specific user button and command type.
PF adjustment
MINT application
Power factor control loop is active in parallel to mains mode only (MCB feedback closed). Switch off other
engines while adjusting.
Set the same values to PF Gain (page 444) and PF Int (page 444) as in the chapter Voltage
adjustment (page 239) for parameters Voltage Gain (page 443) and Voltage Int (page 443).
Set #System BaseLoad (page 297) = 30 % of Nominal Power (page 306) and #System Power Factor
(page 297) = 1.0.
Start and synchronize the Gen-set in MAN Mode by pressing GCB ON/OFF
When running in parallel to mains loaded on 30 %, increase slowly PF Gain (page 444) to unstable point
and then decrease the value by 30 % to insure stable performance.
Adjust PF Int (page 444) (usually setting to 100 % gives optimal performance).
Note: To judge optimal adjusting of the power factor induce generator power jumps by Voltage Regulator
Bias (page 441) change or by #System BaseLoad (page 297) change.
SPtM application
Power factor control loop is active in parallel to mains mode only (MCB feedback closed).
Set the same values to PF Gain (page 444) and PF Int (page 444) as in the chapter Voltage
adjustment (page 239) for parameters Voltage Gain (page 443) and Voltage Int (page 443).
Set Baseload (page 294) = 30 % of Nominal Power (page 306) and BasePower Factor (page 295) =
1.0.
Start and synchronize the Gen-set in MAN Mode by pressing GCB ON/OFF.
Note: To judge optimal adjusting of the power factor induce generator power jumps by Voltage Regulator
Bias (page 441) change or by Baseload (page 294) change.
5.4.49 Warming
This function sets maximal allowed load if Gen-Set synchronizes GCB to bus/mains and coolant temperature
is bellow limit.
The function is Enabled/Disabled via setpoint Warming Procedure (page 338) and the behavior is adjusted
via setpoints Warming Load (page 338), Warming Temperature Limit (page 339) and Maximum
Warming Time (page 339).
Principle of Warming
Warming is activated if setpoint Warming Procedure (page 338) = Enabled and Gen-set synchronizes GCB
to bus/mains with LAI COOLANT TEMP (PAGE 698) (or value from ECU) lower than Warming Temperature
Limit (page 339).
Alarm AHI Warming (page 876) is activated and Load is limited to Warming Load (page 338). Warming
Load (page 338) is related to Nominal Power (page 306)
Warming Load (page 338) set maximal allowed load, i.e. if Baseload (page 294) will be lower, Gen-set will
be limited by Baseload (page 294).
The warming will last until LAI COOLANT TEMP (PAGE 698) – (or value from ECU) reaches Warming
Temperature Limit (page 339) or period given by Maximum Warming Time (page 339) elapses.
If LAI COOLANT TEMP (PAGE 807) (or value from ECU) reaches Warming Temperature Limit (page 339),
warming is considered as done. This means that even if LAI COOLANT TEMP (PAGE 807) (or value from ECU)
drops bellow Warming Temperature Limit (page 339) again, warming is not reactivated.
6 back to Functions
Implicit account
At trusted interfaces there is an implicit user automatically logged-in at any time if no other explicit user is
logged-in at the respective interface. This allows terminal devices (e.g. internal display) to show controller
values even without the need for a specific person to be logged-in.
The implicit account is fixedly defined in the firmware.
The implicit account has fixed access level 0, unless production mode is activated (see Production
mode on page 243).
Implicit user is logged in any time no other user is logged in at the respective interface.
User login
To login to the controller the username and password must be provided into the login form of the
application (InteliConfig (page 15), WebSupervisor (page 15).
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 see Account break protection on page 249.
There is active alarm Wrn Production Mode (page 868) in the alarm list any time production mode is active.
To turn off the Production mode go to User management and uncheck the checkbox Production mode or go
to Production Mode display screen and select disable.
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 can be deleted.
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.
Note: There must always remain at least one administrator account in the system. The controller will not
allow deleting last administrator account.
Wrn Default Password appears in Alarm list when the default administrator password is set and
communication module is plugged in the controller. The purpose of alarm is to inform that the controller might
be or is connected to an untrusted interface and cybersecurity rules are not fulfilled because there is default
administrator password.
Adding an account
Click on the "+" button in the lower left corner of the user management window, then provide the account
properties as described in User accounts (page 242).
Note: Rules for the User accounts (page 242) credentials apply and some items are optional
Deleting an account
Select the account that has to be deleted and click on the "-" 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.
Cloning accounts
Cloning feature allows user to clone user accounts together with controller firmware and configuration.
Note: If the archive where the save of the clone is made is configured with the plug-in module, it's firmware
can also be a part of the clone.
Package protection
Set up password for clone file
Create clone
To load the clone to the controller click on the Create Clone icon.
Manage clones
Click on the ImEx clone icon for managing clones. Following window appears.
Importing clone
It is possible to import clone from any location. For importing the clone click on the Import clone icon.
Following window appears.
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.
Password protection
1. If a 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 the correct password is provided.
3. After the blocking period elapses, another 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 repeats 1-3 times further, the duration of the blocking period is multiplied by 2 in each
consequential cycle. However, the maximal blocking time is 20 minutes, the blocking time is never higher.
PIN protection
If a 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 this UID/PIN. The user must login with
username/password and change the PIN to unblock this login method again.
Reading data
The access level required for reading data from controller is fixedly adjusted to 0. That means reading of
data (except some system objects) is available for any user.
Writing data
The access level required to write (modify) application setpoints or invoke application commands is
configurable via InteliConfig.
Special situations
There are several operations that require administrator level:
Programming firmware
Programming configuration
Managing user accounts
Note: Permanent blocking cannot occur accidentally, just by user mistake. It can be practically triggered only
by a focused activity.
6.1 PC
6.1.1 Direct communication 255
6.1.2 Remote communication 257
Note: For information how to setup an AirGate connection, see AirGate connection on page 74.
The second way to get the static IP address is to switch the onboard ethernet or CM3-Ethernet to automatic
IP address mode. Adjust the setpointIP Address Mode (page 623)to AUTOMATIC. In that case all IP
settings are assigned by DHCP server. Then configure the DHCP server to assign always the same IP
address (i.e. static IP address) to the particular onboard ethernet or CM3-Ethernet according to its MAC
address.
Internet 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 onboard ethernet or CM3-Ethernet is connected to the Internet via a local Ethernet network then in
the most cases port forwarding must be created from the public IP address of the network gateway to
the local IP address of onboard ethernet or CM3-Ethernet at the port specified for ComAp protocol.
Different port numbers can be used to create multiple port forwarding rules in the same local network.
IMPORTANT: AirGate Key has to be configured. User with administrator rights has a possibility to
set up or change AirGate Key via InteliConfig using Tools -˃ Access Administration -˃ Change
AirGate Key.
SMS
Event SMS
The InteliGen 500 G2 controller equipped with the CM2-4G-GPS communication module is able to send
Event SMS according to the setting of setpoint:
Event Message (page 612)
Note: First, the setpoint Telephone Number 1 (page 594) must be adjusted to enable this function.
Alarm SMS
The InteliGen 500 G2 controller equipped with the CM2-4G-GPS communication module is able to send
Alarm SMS according to the setting of setpoints:
Wrn Message (page 613)
Stp Message (page 613)
Sd Message (page 612)
BOC Message (page 611)
Note: First, the setpoint Telephone Number 1 (page 594) must be adjusted to enable this function.
Message structure:
Gen-set Name
AL=(Alarm 1, Alarm 2, Alarm x)
Note: An asterisk means that alarm is unconfirmed and an exclamation mark means that alarm is active.
Emails
Event Email
The InteliGen 500 G2 controller equipped with the CM3-Ethernet communication module is able to send an
Event Email according to the setting of setpoint:
Event Message (page 612)
Note: Setpoints Email Address 1 (page 589) and SMTP Sender Address (page 618) or SMTP Server
Address (page 619) must be adjusted to enable this function.
Message structure:
Controller
-----------------------------------------------
Name: XXX
Serial number: XXX
SW branch: XXX
SW version: XXX
Application: XXX
Appl. version: XXX
Date: dd/mm/yyyy
Time: hh:mm:ss
Events
-----------------------------------------------
hh:mm:ss Event 1
hh:mm:ss Event 2
hh:mm:ss Event 3
Alarm Email
The InteliGen 500 G2 controller is able to send Alarm Emails according to the setting of setpoints:
Wrn Message (page 613)
Sd Message (page 612)
BOC Message (page 611)
Note: Setpoints Email Address 1 (page 589) and SMTP Sender Address (page 618) or SMTP Server
Address (page 619) must be adjusted to enable this function.
Message structure:
Controller
-----------------------------------------------
Name: XXX
Serial number: XXX
SW branch: XXX
SW version: XXX
Application: XXX
Appl. version: XXX
Date: dd/mm/yyyy
Time: hh:mm:ss
History events
-----------------------------------------------
0 dd/mm/yyyy hh:mm:ss.0 Event 1
-1 dd/mm/yyyy hh:mm:ss.0 Event 2
-2 dd/mm/yyyy hh:mm:ss.0 Event 3
Note: An asterisk means that alarm is unconfirmed and an exclamation mark means that alarm is active.
6 back to Communication
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 and SNMP v2
The SNMP Agent function is to be enabled by the setpoint SNMP Agent (page 621) in the CM-Ethernet
setpoint group. The setpoints SNMP RD Community String (page 621) and SNMP WR Community String
(page 622) in the same group can be used to customize the "community strings" for the read and write
operations which function like "passwords". All requests sent from the SNMP Manager must contain a
community string which matches with the community string adjusted in the controller otherwise the controller
will refuse the operation.
MIB table
The "MIB table" (Management Information Base) is a table which gives to the Manager a 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 also share 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 OID of the InteliGen 500 G2 controller is 1.3.6.1.4.1.28634.40. Under this node can be found
following sub-nodes:
Notifications group (SMI v2 only) contains definitions of all notification-type objects that the Agent may
send to the Manager.
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 the SMI version that it supports.
Typically, SMI v1 is used for SNMP v1 and vice versa, but it is not a rule. SMI v2 may also be used for SNMP
v1.
SNMP notifications
Except for 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 which 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 Ethernet setpoint group. If the Manager address is not adjusted the
particular notification channel is off. The controller will send the notifications in the format adjusted by the
setpoint SNMP Trap Format.
Each notification (kind of event) is identified by a unique identifier (Trap ID in SNMPv1 or Notification OID
in SNMPv2). This unique identifier gives the specific meaning to the notification message, e.g. Protection
1st 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.
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 the SMI version that it supports. Typically, SMI
v1 is used for SNMP v1 and vice versa, but it is not a rule and SMI v2 may also be used for SNMP v1.
Note: *)
For list of commands, arguments and description of the procedure of invoking commands see the description
of the Modbus protocol.
Note: Modbus-RTU serial communication mode is 8-N-1 – startbit 1, 8 data bits, no parity and 1 stopbit.
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.
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
Integer16 2-byte signed integer 1
LSB = value, LSB
MSB = value, MSB
Unsigned16 2-byte unsigned integer 1
LSB = value, LSB
MSB1 = value, byte 3 (MSB)
LSB1 = value, byte 2
Integer32 4-byte signed integer 2
MSB2 = value, byte 1
LSB2 = value, byte 0 (LSB)
MSB1 = value, byte 3 (MSB)
LSB1 = value, byte 2
Unsigned32 4-byte unsigned integer 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
Binary16 16-bit binary value 1
LSB = value, bits 0-7
MSB1 = value, bits 24-31
LSB1 = value, bits 16-23
Binary32 32-bit binary value 2
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.
LSB2 = ASCII value of the 4. character
…
LongStr Zero-terminated string of 16 MSB1 = ASCII value of the 1. character
Note:
*) 1 .. level 1 (yellow), 2 .. level 2 (red), 3 .. sensor fail
**) Bit0 – alarm is active, Bit1 – alarm is confirmed
***) String encoding is UTF-8
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
4214 1 read Unsigned8 Number of items in the Alarmlist
4215 - 4241 27 read Alarm 1. record in alarm list
4242 - 4268 27 read Alarm 2. record in alarm list
4269 - 4295 27 read Alarm 3. record in alarm list
4296 - 4322 27 read Alarm 4. record in alarm list
4323 - 4349 27 read Alarm 5. record in alarm list
4350 - 4376 27 read Alarm 6. record in alarm list
4377 - 4403 27 read Alarm 7. record in alarm list
4404 - 4430 27 read Alarm 8. record in alarm list
4431 - 4457 27 read Alarm 9. record in alarm list
4458 - 4484 27 read Alarm 10. record in alarm list
4485 - 4511 27 read Alarm 11. record in alarm list
4512 - 4538 27 read Alarm 12. record in alarm list
4539 - 4565 27 read Alarm 13. record in alarm list
4566 - 4592 27 read Alarm 14. record in alarm list
4593 - 4619 27 read Alarm 15. record in alarm list
4620 - 4646 27 read Alarm 16. record in alarm list
5000 1 read/write int16 RemoteControl2B 1
5001 1 read/write int16 RemoteControl2B 2
5002 1 read/write int16 RemoteControl2B 3
Note: *)
This action is an equivalent of pressing the front panel button
Table: Values
Allowed Modbus functions: 03, 04
Register
Com.Obj. Name Dimension Type Len Dec Min Max Group
address
Controller
01053 8213 BatteryVoltage V Integer 2 1 0 400
I/O
We read a value 240 from register 01053. From the table of Modbus registers we get the dimension of read
value and "Dec". Dec=1 means shift one decimal place to the right. So the battery voltage is 24.0 V.
Table: Values
Allowed MODBUS functions: 03, 04
Register
Com.Obj. Name Dimension Type Len Dec Min Max Group
address
Nominal
01227 9018 kW Integer 2 0 0 32767 Generator
Power
Table: Values
Allowed Modbus functions: 03, 04
Register
Com.Obj. Name Dimension Type Len Dec Min Max Group
address
Binary Controller
01089 8235 Binary#2 2 0 - -
Inputs I/O
Binary inputs is 00010010. This means Binary input 2 and binary input 5 are active.
Note: You can use Modbus function 4 instead of 3, the rest of the data remains the same (CRC differs).
Table: Binaries
Allowed Modbus functions: 01, 02
Addresses Source Name of Bit Name
C.O.#
Modbus Addr. = Value Value Bit # Activated by protection Group
State #
Prot. Addr. = State Name of State (s):
00000 Value 8235 Binary Inputs 1 GCB Feedback Controller I/O
00001 Value 8235 Binary Inputs 2 MCB Feedback Controller I/O
00002 Value 8235 Binary Inputs 3 Emergency Stop Controller I/O
The read data is 01. This means this binary input is active.
Note: You can use Modbus function 2 instead of 1, the rest of the data remains the same (CRC differs).
Number of
Register address Access Data type Meaning
registers
Writing:command argument
4207 - 4208 2 read/write Unsigned32
Reading: command return value
4209 1 write Unsigned16 Command code
Note: Command and argument may be written as one "packet" (function 16) or you can split it and write
argument (function 16) and then the command code (function 6).
Table: Setpoints
Allowed Modbus functions: 03, 04, 06, 16
Register
Com.Obj. Name Dimension Type Len Dec Min Max Group
address
Nominal Basic
03008 8276 kW Unsigned 2 0 1 5000
Power Settings
Table: Values
Allowed Modbus functions: 03, 04
Register
Com.Obj. Name Dimension Type Len Dec Min Max Group
address
BatteryVoltag Controller
01053 8213 V Integer 2 1 0 400
e I/O
We read a value of 240 from register 01053. From the table of Modbus registers we get the dimension of read
value and "Dec". Dec=1 means shift one decimal place to the right. So the battery voltage is 24.0 V.
6 back to Communication
Frequency input
4 Hz to 10 kHz
range
Frequency
measurement 0.2 % from measured value
tolerance
8.1.2 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 EEPROM memory, which
5
can be overwritten up to 10 times without risk of damage or data loss, but it may become
damaged, when the allowed number of writing cycles is exceeded.
For full list of setpoints go to the chapter List of setpoints (page 280).
Starting Oil Pressure 328 Protection 344 Subgroup: ECU Settings 355
Glow Plugs Time 328 Oil Pressure Delay 344 Open Param Governor
Oil Pressure Wrn 344 Speed Adjust 355
Idle RPM 329
Oil Pressure Sd 345 ECU Speed Adjustment 356
Subgroup: Starting Timers 330
Coolant Temp Delay 345 Group: Maintenance Timers 356
Fuel Solenoid Lead 330
Coolant Temp Wrn 345 Subgroup: Maintenance
Idle Time 330
Timer 1 356
Minimal Stabilization Coolant Temp BOC 346
Maintenance Timer 1
Time 332 Coolant Temp Low
RunHours 356
Maximal Stabilization Delay 346
Maintenance Timer 1
Time 333 Coolant Temp Low Wrn 346
Interval 357
GCB Delay 334 Fuel Level Delay 347
Maintenance Timer 1
Run Only Block Delay 334 Fuel Level Wrn 347 Protection 357
Sd Ventilation Time 335 Fuel Level BOC 347 Subgroup: Maintenance
Subgroup: Stopping 335 Subgroup: Fuel Theft Timer 2 358
Cooling Speed 335 Protection 348 Maintenance Timer 2
Subgroup: Stopping Fuel Tank Volume 348 RunHours 358
Timers 336 Maximal Fuel Drop 348 Maintenance Timer 2
Cooling Time 336 Maximal Fuel Drop Interval 358
Stop Time 336 Delay 348 Maintenance Timer 2
After Cooling Time 337 Subgroup: Fuel Pump 349 Protection 359
Short Circuit Delay 363 Reverse Power Level 371 Underspeed Protection 382
IDMT Generator >A Reverse Power Delay 371 Group: Mains Settings 383
Delay 363 Subgroup: Excitation Loss Subgroup: AMF Timers 383
Generator Current Protection 371 Emergency Start Delay 383
Unbalance 364 Excitation Loss Level 371 Mains Return Delay 383
Generator Current Excitation Loss Delay 372 MCB Close Delay 384
Unbalance Delay 365 Group: Protections 372 AMF Start 384
Subgroup: Earth Fault Subgroup: Overload Subgroup: Mains Voltage
Current Protection 365 Protection 372 Limits 384
IDMT Earth Fault Overload Protection 372 Mains Overvoltage 384
Current Sd 365 Subgroup: Current Mains Overvoltage
IDMT Earth Fault Protection 373 Delay 385
Current Delay 365 IDMT Generator >A Mains Overvoltage Hys 386
Subgroup: Voltage Protection 373
Mains Undervoltage 387
Protection 366 Generator Current
Mains Undervoltage
Generator Overvoltage Unbalance Protection 374
Delay 387
Sd 366 Subgroup: Earth Fault
Mains Undervoltage Hys388
Generator Overvoltage Current Protection 375
Wrn 366 Mains Voltage
IDMT Earth Fault
Unbalance 389
Generator Undervoltage Current Protection 375
Wrn 367 Mains Voltage
Subgroup: Voltage
Unbalance Delay 389
Generator Undervoltage Protection 376
BOC 367 Subgroup: Mains
Generator <> Voltage
Frequency Limits 389
Generator <> Voltage Protection 376
Delay 368 Mains Overfrequency 389
Generator V Unbalance
Generator V Unbalance 368 Mains Overfrequency
Protection 377
Hys 390
Generator V Unbalance Bus Measurement Error
Delay 368 Mains Underfrequency 391
Protection 378
Subgroup: Frequency Mains Underfrequency
Subgroup: Frequency
Protection 369 Hys 392
Protection 379
Generator Mains < > Frequency
Generator Frequency
Overfrequency BOC 369 Delay 393
Protection 379
Generator Subgroup: AMF Settings 393
Subgroup: Reverse Power
Overfrequency Wrn 369 Protection 380 Return From Island 393
Generator Reverse Power MCB Logic 394
Underfrequency Wrn 369 Protection 380 MCB Opens On 395
Generator 370 Subgroup: Excitation Loss 381 Subgroup: Mains 396
Subgroup: Application Selector
SPtM Single parallel to mains application. The controller controls two breakers – a mains
breaker and a generator breaker. Feedback from both breakers is required.
MINT Multiple island-parallel application without mains and multiple parallel application with
mains. The controller controls one breaker only, the generator breaker. Feedback from
the generator breaker is required. For parallel to mains operation also mains breaker
feedback is required.
Subgroup: Load Control
Local Baseload*
Gen-set produces amount of the power given by setpoint Baseload (page 294).
The rest of power is supplied from the mains or exported to the mains (depends on
proportions of load and Baseload (page 294) setpoint). Even in baseload control
mode can be the Import/Export limited. This function can be activated by setpoint
Import/Export Limitation (page 296) = Enabled. Then the request for the power
of the genset operating in baseload can be limited to prevent the Import/Export go
below the limit given by setpoint Import Load (page 295).
Example: Baseload = 1000 kW, load = 700 kW, Import load = 100. Then the
Baseload Baseload request will be limited to 600 kW to prevent the Import power go
below 100 kW
Example: Baseload = 1000 kW, load = 700 kW, Import load = -100. Then the
Baseload request will be limited to 800 kW to prevent the Import power go
below -100 kW (actually it is limitation of the export).
The load of the Gen-set group is controlled to keep constant level of base load of
the whole system. The level is adjusted by the setpoint #System BaseLoad (page
297).
Gen-set produces the certain amount of power to keep constant import/export from
the mains regardless the demand of the load. The requested import/export is given
Imp/Exp by setpoint Import Load (page 295). If the value of the setpoint is >0 the power is
imported from the mains, if setpoint value is <0, then the power is exported to the
mains.
Note: In both modes, the lower level of the power is always limited by the setpoint Minimal Power
PTM (page 362). If the requested load (given by the active load control mode, e.g. Baseload,
Import/Export) is below this limit the requested load is limited to the level adjusted by this setpoint.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
The load is sourced either from setpoint Baseload (Load Control PTM=Baseload) or
Setpoint
from Import Load (page 295) (Load Control PTM=IMP/EXP).
Analog The load is source from LAI LOAD CONTROL: ANEXT BASELOAD* (PAGE 808) (Load
External Control PTM=Baseload) or from LAI LOAD CONTROL: ANEXT IMP/EXP LOAD* (PAGE
Value 808) (Load Control PTM=IMP/EXP).
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
The power factor on the Gen-set is kept on the level given by the setpoint
BasePower Factor (page 295) regardless the load demand. The rest of
demanded reactive power is supplied from the mains. Values >1 means that
Base PF capacitive reactive power is supposed to be imported from mains, values <1
means that inductive reactive power is imported from the mains.
Gen-sets are controlled to keep the constant level of the power factor. The level
is adjusted by setpoint #System Power Factor (page 297).
Gen-set produces the certain amount of reactive power to keep constant PF
imported from the mains regardless the demand of the load. The requested
power factor import is given by setpoint Import Power Factor (page 296).
PF Imp/Exp
Values >1 means that the gen-set is pushing the capacitive power to the system
(sytem Gen-set – Load- Mains) , values <1 means that the Gen-set is pushing
the inductive power to the system.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
The total power of the group is controlled to constant level given by the setpoint
#System BaseLoad (page 297). Each loaded Gen-set 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 297) is also used for determining which Gen-
sets have to run or not.
Gen-sets load is controlled by InteliMains 210 controller to share the total load
(given by the setpoint #System BaseLoad (page 297)) with other loaded Gen-
Loadsharing
sets in such a way, that all loaded gen-sets will be loaded at the same level
(relative to gen-set nominal power). Load-sharing regulation loop is active.
Note: The Loadsharing mode shall be used in case a InteliMains 210 controller is present in the
system. In systems without InteliMains 210 the setpoint must be in the Baseload position.
Note: The power factor (PF) is regulated to constant level given by the setpoint #System PF Control
PTM (page 294) in parallel to mains operation and does not depend on active load control mode.
Baseload
Import Load
If the value of the setpoint is >0 the power is imported from the mains, if the setpoint value is <0, then the
power is exported to the mains.
Import/Export Limitation
Example: Baseload = 1000 kW, load = 700 kW, Import load = -100 kW. Then the Baseload request
will be limited to 800 kW to prevent the Import power go below -100 kW (actually it is limitation of the
export).
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
The EACH option should be used if each Gen-set has it's own neutral contactor. Four-
pole GCB must be used in this case.
The output is always opened while the Gen-set is not running
The output is always opened while the MCB is closed
While the Gen-set is running and GCB is open, the output closes when
Each generator voltage in at least one phase exceeds 85 % of the nominal voltage. It
opens when the generator voltage in all phases drops below 50 % of the
nominal voltage
While the Gen-set is running, MCB is open and GCB is closed, then the
position of the output is given by an internal algorithm, which ensures, that
always exactly one Gen-set connected to the bus has the neutral contactor
closed. It is always the Gen-set with lowest CAN address
The COMMON option should be used if there is one common neutral contactor for the
whole site. The NCB CLOSE/OPEN (PAGE 786) outputs from all controllers are
combined together and the combined signal is used to control the breaker. Three-pole
GCB must be used in this case.
The output is always opened while the Gen-set is not running
Common The output is always opened while the MCB is closed
While the Gen-set is running the output closes when generator voltage in at
least one phase exceeds 85 % of the nominal voltage. It opens when the
generator voltage in all phases drops below 50 % of the nominal voltage. That
means if at least one Gen-set in the site is running and having proper voltage,
the neutral contactor is closed
Note: Logical binary input NCB FEEDBACK (PAGE 724) has to be configured for proper functionality.
Note: For the SPtM application there is only 1 Gen-set so the setpoint #Neutral contactor control is
hidden and the NCB behave like it is setup to COMMON option.
No limitation of CB control in MAN mode (operator can close any breaker manually or
Full Ctrl
evoke the synchronization and consequential operation in parallel to mains)
Operator can control both MCB or MGCB breaker. However once transition is evoked
the controller performs the automatic transfer of the load (depends on adjustment of
setpoints Transfer Gen To Mains (page 438) and Transfer Mains To Gen (page
437)).
Controller performs synchronization across MCB, ifMGCB is closed and MCB button is
pushed. Load transfer is done after synchronization andMGCB is opened
automatically.
Controller performs synchronization acrossMGCB, if MCB is closed andMGCB button
is pushed. Load transfer is done after synchronization and MCB is opened
Aut Trans
automatically.
It is also possible to open currently closed breaker and keep the load non-energized.
Then it is possible to close MCB orMGCB to energize the load from a healthy source.
Note: Parallel operation with mains continues, if system already operates in
parallel with mains and setting is changed to Aut Trans. It is necessary to push
MCB or MGCB button to open a breaker.
Note: Open transfer is performed, if the Open option is selected with Transfer Gen
To Mains (page 438) or Transfer Mains To Gen (page 437).
Behaves like the full manual control but the Island operation is disabled.
Example: When MCB opened and MGCB is pressed, controller doesn’t go to
Islnd Disl
island.
Example: In parallel operation when MCB button pressed, MCB is not opened.
Mains Measurement P
The Mains Import Power is not measured and the duration of the load transfer in
None direction Mains to Generator is given exactly by the setpoint Close Transfer Max
Duration (page 436).
The Mains Import P (page 651) value is measured via Mains CTs. The load
Mains CT transfer in direction Mains to Generator is considered to be finished when the mains
is unloaded under certain level.
The Mains Import P (page 651) value is measured via analog input, accordingly
Analog LAI: MAINS IMPORT MEASUREMENT (PAGE 808). The load transfer in direction Mains
Input to Generator is considered to be finished when the mains is unloaded under certain
level.
Subgroup: Peak Shaving
Peak Shaving
The Peak Shaving function is active and the start command is activated when the
Enabled
conditions for Peaks Shaving activation were fulfilled.
The Peak Shaving function is BLOCKED and the start command can not be activated
Disabled
even the conditions for Peaks Shaving activation were fulfilled.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
The breaker is controlled only from controller. Any unexpected change of GCB
FEEDBACK (PAGE 715) causes Stp GCB Fail (page 892) immediately.
Incorrect reaction of the GCB FEEDBACK (PAGE 715) on internal GCB
Internal
Close/Open command causes Stp GCB Fail (page 892)
Anytime when the controller is synchronizing via GCB the External GCB closing
is being accepted in all GCB control modes.
GCB Openning GCB FEEDBACK (PAGE 715) = 0 is accepted from external
devices with history record "GCB Opened Externally".
Follow
Incorrect reaction of the GCB FEEDBACK (PAGE 715) to internal GCB Close/Open
command causes Stp GCB Fail (page 892)
Controller does not control the GCB at all. The GCB is controlled externally, when
the GCB FEEDBACK (PAGE 715) get changed, then the event "GCB Opened" or
"GCB Closed" is recorded to the history log.
Controller always accept the GCB FEEDBACK (PAGE 715) without of issuing any
External alarm.
When the Sd protection shuts down the engine, the GCB stays closed. The BOC
protection does not open the GCB, controller goes to cooling when the BOC
protection is tripped (GCB stays closed until opened externally).
IMPORTANT: Gen-set with closed GCB is not blocked against starting.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Subgroup: Controller Redundancy*
Note: *) Only available in the Extended features version. For more information see Extended features on
page 154.
Watched Controller*
Subgroup: Name
Gen-Set Name
Nominal Power
Note: This value can be also switch into one decimal power format (via InteliConfig PC tool). In this
case the range of value is decrease 10 times.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Nominal Current
Connection type
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Gen VT Ratio
Mains/Bus VT Ratio
Nominal Frequency
Gear Teeth
Controller 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
Note: Horn timeout starts again from the beginning if a new alarm appears before previous Horn
timeout has elapsed.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: It is not necessary to restart controller when this setpoint is changed. Change of this setpoint is
applied immediately.
Every time user login/logout to the controller, there is a message: User with user index
Enabled
(n) logged in/out … written in the history.
Disabled Login/logout message is not written into history.
Subgroup: Phase Rotation
Phase Rotation
Subgroup: Controller Address
Controller Address
Communication
Setpoint group Related FW 2.0.0
Settings
Range [units] 1 .. 32 [-]
Default value 1 Force value NO
Step 1
Comm object 24537 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Always
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.
Subgroup: RS485 Settings
RS485 Mode
Communication
Setpoint group Related FW 2.0.0
Settings
Range [units] Direct / MODBUS [-]
Default value Direct Force value NO
Step [-]
Comm object 24134 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Always
Description
Communication protocol switch for on-board RS485.
Communication
Setpoint group Related FW 2.0.0
Settings
Range [units] 9600 / 19200 / 38400 / 57600 / 115200 [bps]
Default value 57600 bps Force value NO
Step [-]
Comm object 24135 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Always
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.
Communication
Setpoint group Related FW 2.0.0
Settings
Range [units] 9600 / 19200 / 38400 / 57600 / 115200 [bps]
Default value 9600 bps Force value NO
Step [-]
Comm object 24141 Related applications MINT, SPtM
Config level Standard
Only if relevant module is installed + conditioned by the setpoint COM1 Mode (page
Setpoint visibility
574)
Description
If the MODBUS mode is selected on COM1 channel, the MODBUS communication speed can be adjusted
here.
Subgroup: Starting
Fuel Solenoid
Cranking Attempts
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Starting RPM
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: LBO PRESTART (PAGE 789) goes to logical zero when Fuel Solenoid Lead goes to logical one.
Note: This setpoint is used only for diesel Fuel Solenoid (page 324).
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Idle Time
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Subgroup: Stopping
Cooling Speed
Note: When ECU is connected the predefined value 900 RPM for Idle speed is requested.
Note: Binary output IDLE/NOMINAL (PAGE 775) must be configured and connected to speed governor.
Engine Idle speed must be adjusted on speed governor.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Cooling Time
Stop Time
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Warming Procedure
Warming Load
Subgroup: D+ Function
D+ Function
Enabled The D+ terminal is used for both functions – “running engine” detection and
charge fail detection.
ChargeFail The D+ terminal is used for charge fail detection only
Disabled The D+ terminal is not used.
Note: Delay of this function is adjusted via D+ Delay (page 341) setpoint, threshold of this function is
adjusted via D+ Level setpoint.
D+ Delay
D+ Alarm Type
Overspeed Sd
Underspeed Sd
Starting Overspeed Sd
Fuel Pump On
IMPORTANT: When binary input FUEL PUMP ON/OFF (PAGE 714) is configured then binary
output FUEL PUMP (PAGE 763) is control by this binary input. Setpoints Fuel Pump On and
Fuel Pump Off (page 350) are not evaluated!
Note: Value from analog input has higher priority than ECU.
IMPORTANT: When binary input FUEL PUMP ON/OFF (PAGE 714) is configured then binary
output FUEL PUMP (PAGE 763) is control by this binary input. Setpoints Fuel Pump On (page
349) and Fuel Pump Off are not evaluated!
Note: Value from analog input has higher priority than ECU.
Battery Undervoltage
Prelubrication Time
Prelubrication Pause
Group: Maintenance Timers
Subgroup: Maintenance Timer 1
Subgroup: Maintenance Timer 3
Overload BOC
Overload Wrn
Generator settings
Setpoint group Related FW 2.0.0
Mains
Range [units] 0.0 .. 600.0 [s]
Default value 5.0 s Force value NO
Step 0.1 s
Comm object 8281 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Always
Description
Delay for protections Overload BOC (page 361)Overload BOC (page 361) and Overload Wrn (page
361).
6 back to List of setpoints
Subgroup: Underload Protection
Short Circuit
Generator Overvoltage Sd
Note: When there is no control of breakers, the type of protection is Sd not BOC.
Generator V Unbalance
Group: Protections
Overload Protection
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Bus Measurement error is detected when the voltage on controller's bus terminals
is out of limits 20 seconds after:
GCB (own) was closed in MAN or AUTO mode.
Enabled: MCB (feedback) was closed in AUTO mode.
Any other GCB in power management group (on CAN bus) was closed.
The alarm is activated after 20 s. However, the GCB (own) closing is blocked
immediately for safety reasons.
Disabled: Protection is disabled.
Protection is enabled or disabled by the state of LBI PROTECTION FORCE DISABLE 1
By LBI:
(PAGE 725).
Protection is enabled or disabled by the state of LBI PROTECTION FORCE DISABLE 1
ExtDisable:
(PAGE 725).
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Underspeed Protection
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
AMF Start
Mains Overvoltage
Mains Overfrequency
Controller remains in AUT mode and the manual return to Mains is done via
MCB button. ALI Manual Restore (page 860) message is displayed in
alarmlist to notify operator – it will disappear automatically after MCB close
Manual button is pushed.
Note: Select MANUAL in case you need to manually control the moment
when the load is transferred back to the mains.
The MCB is closed automatically after the timer Mains Return Delay (page
Auto 383) elapses. The transfer of load from a generator to mains is given by the
setpoint Transfer Gen To Mains (page 438).
IMPORTANT: This is a fixed parameter, it isn't possible to adjust it in any manner. This
parameter isn't visible either in controller or in PC tools.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
MCB Opens On
Mains The command to open the MCB is given immediately after mains fail condition is
Fail evaluated. If the mains will return into parameters after MCB was opened and before
GCB is closed, timer MCB Close Delay (page 384) is applied before MCB closing.
Gen Run MCB will be opened when engine will be running and it will be possible to transfer load
from Mains to Gen-set (after stabilization phase).
Note: This option should be used for MCBs using 230V control and not equipped
with the undervoltage coil.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: The vectorshift protection is recorded into the history file, however it is not indicated in the Alarm
list. When it occurs the controller opens either MCB or GCB depending on the setpoint Vector Shift
CB Selector (page 400). If the MCB is not controlled in the particular application then GCB is opened.
Note: If a vector shift is detected and consequently the MCB is opened, however mains voltage and
frequency remain in limits, the MCB is then reclosed again after Mains Return Delay (page 383), as
the mains is evaluated as healthy.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: The ROCOF protection is recorded into the history file, however it is not indicated in the Alarm
list. When it occurs the controller opens either MCB or GCB depending on the setpoint Vector Shift
CB Selector (page 400). If the MCB is not controlled in the particular application then GCB is opened.
Note: If a ROCOF is detected and consequently the MCB is opened, however mains voltage and
frequency remain in limits, the MCB is then reclosed again after Mains Return Delay (page 383), as
the mains is evaluated as healthy.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
ROCOF df_dt
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Group: Load Shedding
Subgroup: Dummy Load
Dummy Load On
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Disabled The Load shedding function is disabled. All the outputs are open.
Gen only The function is active when Breaker State (page 670) = IsOper.
Load shedding outputs are activated / deactivated one by one in island
operation
All Loadshedding outputs are tripped once the Gen-set comes into the
island operation from "NO LOAD" operation (MCB and GCB were was
opened -> Gen-set started and GCB closed).
All the time Load shedding Outputs are controlled by the load shedding function regardless of
breaker positions.
Loadshedding is active in island operation, in parallel operation too.
All Loadshedding outputs are never tripped at once.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Rising edge on binary input MANUAL LOAD RECONNECTION (PAGE 719) resets
controller to the lower stage, but only if the load is under the Load Reconnection
Disabled
Level (page 405). Load Reconnection Delay (page 405) is not taken into account in
this case.
Load reconnection is automatic depend on setpoints Load Reconnection Level
Enabled (page 405) and Load Reconnection Delay (page 405). Binary input MANUAL LOAD
RECONNECTION (PAGE 719) has no function.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Power Management
The power management is based on actual active power and Gen-set nominal
ABS [kW]
power. The reserves are calculated and adjusted in kW.
This mode of Power Management is not supported in this controller. Alarm Wrn
Not Available
Unsupported PMS Mode (page 875) is active.
The power management is based on the relative load, i.e. ratio active power to
REL [%]
nominal power. The reserves are calculated and adjusted in %.
Note: If more than one gen-set have the same priority they will act as "one big" Gen-set.
IMPORTANT: Value of the setpoint Priority is taken into account only for absolute mode of
power management (#Power Management Mode (page 408) = ABS).
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
IMPORTANT: Binary input TOP PRIORITY (PAGE 736) can be used only if #Priority Auto Swap
(page 410) = Disabled.
Note: See Power management (page 198) chapter for more information.
Note: See Power management (page 198) chapter for more information.
Note: See Power management (page 198) chapter for more information.
Note: See Power management (page 198) chapter for more information.
Note: See Power management (page 198) chapter for more information.
Note: See Power management (page 198) chapter for more information.
Note: See Power management (page 198) chapter for more information.
Note: See Power management (page 198) chapter for more information.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Subgroup: Start/Stop Timing
Example: The difference in engine running hours has to be 11.0 hours, if #Run Hours Max
Difference is set to 10. The priorities shuffling is not done with the difference just 10.1 hours.
Control Group
Group Link L
Group: Speed Control
Group: Speed Control
Positive Raising the voltage on the governor remote speed input causes engine speed to rise.
Raising the voltage on the governor remote speed input causes engine speed to go
Negative
down.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Frequency Gain
Frequency Int
ALL THE TIME: This option activates the frequency regulation loop also while the Gen-set is
running without load and during the island operation. The controller maintains frequency at its
nominal value adjusted by setpoint Nominal Frequency (page 316).
Note: This option can be used e.g. for the elimination of the droop at governors that do not support
isochronous mode.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Angle Gain
Note: See the chapter Regulation loops (page 218) for more information.
Note: See the chapter Regulation loops (page 218) for more information.
Load Int
Delay after GCB opening to MCB closing during the return procedure. Delay after MCB opening to GCB
closing if the setpoint MCB Opens On (page 395) is set to GENRUN.
The time charts bellow show recommended setting of Transfer Delay setpoint.
If the Transfer Delay setpoint is set shorter than the time required for opening of the circuit breaker, the
controller closes GCB CLOSE/OPEN (PAGE 764) output straight away (100 ms) after the MCB FEEDBACK
(PAGE 721) input deactivates.
If some delay between MCB FEEDBACK (PAGE 721) deactivation and closing of GCB CLOSE/OPEN (PAGE
764) output is required, then the Transfer Delay must be set to sum of "MCB opening" + "Delay" time.
Delay used in SPtM function. This delay is used when load from first Gen-set is transferred to second Gen-
set. Delay starts to countdown when GCB of first Gen-set is open. When this delay countdown, GCB of
second Gen-set is closed. This delay is important for correct function of external interlock.
Transfer of the load from mains to generator without parallel work and
synchronization (one breaker opens and second is closed – checking
Open
feedbacks). The setpoint Open Transfer Min Break (page 436) sets the
minimal duration of break.
Transfer of the load from mains to generator with synchronization and parallel
work. The time of parallel work is given by setpoint Close Transfer Max
Close Only
Duration (page 436).
In case of synchronization fail, MCB stays close and Gen-set is stopped.
Transfer of the load from mains to generator with synchronization and parallel
work. The time of parallel work is given by setpoint Close Transfer Max
Close Prim
Duration (page 436).
In case of synchronization fail, open transfer is done.
Transfer of the load from mains to generator with parallel work and soft loading
of the Gen-set. This function is proceeded like the closed transfer, but there is
time limitation of loading of the Gen-set adjusted via setpoint Load Ramp (page
SoftTransf
440). The transfer is succeed only when the Gen-set is fully loaded – mains is
fully unloaded (level of load when mains is considered as unloaded is adjusted
via setpoint Mains Unload MCB Open Window (page 439)).
Note: Close transfer of load is also affected by setpoint Subgroup: Mains Import Measurement
(page 300).
Transfer of the load from generator to mains without parallel work and
synchronization (one breaker opens and second is closed – checking
Open
feedbacks). The setpoint Open Transfer Min Break (page 436) sets the
minimal duration of break.
Transfer of the load from generator to mains with synchronization and parallel
Close Only work. The time of parallel work is given by setpoint Close Transfer Max
Duration (page 436).
Transfer of the load from generator to mains with synchronization and parallel
work. The time of parallel work is given by setpoint Close Transfer Max
Close Prim
Duration (page 436).
In case of synchronization fail, open transfer is done.
Transfer of the load from generator to mains with parallel work and soft
unloading of the Gen-set. This function is proceeded like the closed transfer, but
there is time limitation of unloading of the Gen-set adjusted via setpoint Load
SoftTransf
Ramp (page 440). The transfer is succeed only when the Gen-set is fully
unloaded (level of load when Gen-set is considered as unloaded is adjusted via
setpoint Generator Unload GCB Open Level (page 439)).
Subgroup: Voltage Control
Raising the voltage on the remote voltage adjustment input causes the generator
Positive
voltage to raise.
Raising the voltage on the governor remote speed input causes engine speed to go
Negative
down.
Voltage Gain
Voltage Int
PF Int
Subgroup: Synchronisation
Synchronization Type
This type of synchronization is based on voltage and phase shift match. Limits are
adjusted via setpoints Voltage Window (page 447) and Phase Window (page
Phase Match
448). When voltage and phase shift are match, Dwell Time (page 448) starts
countdown. After that the command for breaker closing is activated.
This type of synchronization regulates the value of frequency to the value
Mains/Bus frequency + Slip Frequency (page 449) (Mains frequency in SPtM,
Bus frequency in MINT application). When this frequency is reached, Dwell Time
(page 448) starts countdown. After that the command for breaker closing is
activated. The closing breaker command is issued in advance due to latency of
breakers (adjusted via setpoints GCB Latency (page 450) and MCB Latency
(page 450).
Slip Synchro
Note: Condition of Voltage Window (page 447) has to be also fulfilled.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Voltage Window
Dwell Time
MCB Latency
Subgroup: Droop Settings
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
If the bus values are without the limits then the controller is prohibited to close it’s GCB
Disabled
because of safety reasons. Closing of GCB can be done manually in MAN mode.
If the bus values are without the limits, controller is allowed to close it´s GCB to the
Enabled
dead bus.
Subgroup: Frequency Droop
Subgroup: Voltage Droop
#Number Of Controller
Subgroup: User Buttons
User Button 1
Option Description
The LBO User Button 1 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 1 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 1 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 2 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 2 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 2 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 3 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 3 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 3 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 4 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 4 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 5 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 5 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 5 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 5 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 6 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 6 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 6 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 7 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 7 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 7 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 8 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 8 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 8 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 9 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 9 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 9 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 10 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 10 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 10 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 11 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 11 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 11 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 12 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 12 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 12 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 13 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 13 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 13 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 14 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 14 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 14 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 15 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 15 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 15 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 LBO User Button will be 1 until
command is received.
Option Description
The LBO User Button 16 is controlled by command from WebSupervisor or third
COMMAND
party device.
The LBO User Button 16 is controlled manually via the setpoint, value of the user
MAN OFF
button is still 0.
The LBO User Button 16 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 LBO User Button will be 1 until
command is received.
Group: SUS Control
Subgroup: SUS Control
Excitation Control
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
SUS RPM Window
#SUS Excitation Delay
Subgroup: Analog Switches 1
AIN Switch01 On
AIN Switch02 On
AIN Switch03 On
AIN Switch04 On
AIN Switch05 On
AIN Switch06 On
AIN Switch07 On
AIN Switch08 On
AIN Switch09 On
AIN Switch10 On
Group: Scheduler
Time
Activation, deactivation of the DST, and changing of the RTC Time value
AUTO accordingly is performed automatically by the controller. The user always sees
valid local time without any action from his side.
Activation, and deactivation of the DST is performed manually by the user via the
setpoint Time Mode (page 498). Changing of the RTC Time value accordingly is
MANUAL
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 498).
Time Mode (page 498) is fixedly set to STD and the function does not perform any
DISABLED
changes of RTC time.
Time Mode
Timer 1 Function
Timer 1 Duration
Timer 1 Repetition
Chose one day in month when Timer 1 Function (page 500) will
Repeated Day
be activated.
Chose days in one week when Timer 1 Function (page 500) will
Repeated Day In Week
be activated.
Range [units]: 1 .. 1000 [day]. This setpoint adjust that every X day the timer
will be activated.
Daily Example: If you have daily repetition and you set this setpoint to 2, then
every second day from first occurrence of Timer 1 Function (page 500),
the Timer 1 Function (page 500) will be activated.
Range [units]: 1 .. 60 [week]. This setpoint adjust that every X week the timer
will be activated.
Example: If you have weekly repetition and you set this setpoint to 2, then
Weekly
every second week from first occurrence of Timer 1 Function (page 500),
the Timer 1 Function (page 500) will be activated in selected days
adjusted by Timer 1 Day (page 504).
Range [units]: 1 .. 12 [month]. This setpoint adjust that every X month the timer
will be activated.
Example: If you have monthly repetition and you set this setpoint to 2, then
every second month from first occurrence of Timer 1 Function (page 500),
Monthly
the Timer 1 Function (page 500) will be activated in selected day of month
adjusted by Timer 1 Repeat Day In Month (page 504) or in selected days
of week of month adjusted by Timer 1 Day (page 504) and Timer 1
Repeat Week In Month (page 505).
Range [units]: [HH:MM]. This setpoint adjust that every X short period the timer
will be activated.
Short Period Example: If you have short period repetition and you set this setpoint to 2,
then every second minute from first occurrence of Timer 1 Function (page
500), the Timer 1 Function (page 500) will be activated.
Timer 1 Function (page 500) counter is running on the weekends and Timer 1
Including
Function (page 500) can be active.
Timer 1 Function (page 500) counter is running on the weekends but Timer 1
Skip
Function (page 500) isn’t active.
Timer 1 Function (page 500) counter isn’t running on the weekends and Timer 1
Function (page 500) isn’t active. If the activation of timer is counted on the
Postpone
weekend, than timer will be activated after weekend. Another activation of timer is
counted from original date of first occurrence date.
Timer 2 Function
Timer 1 has higher priority over Timer 2. So if Timer 1 Function (page 500) is configured for OFF mode
and Timer 2 Function (page 508) is over the same time configured for AUTO mode, controller will work in
OFF mode.
Controller activates timer whenever it is powered up even in period, where timer should be already
running.
Timer 2 Duration
Timer 2 Repetition
Chose one day in month when Timer 2 Function (page 508) will be
Repeated Day
activated.
Chose days in one week when Timer 2 Function (page 508) will be
Repeated Day In Week
activated.
Range [units]: 1 .. 1000 [day]. This setpoint adjust that every X day the timer
will be activated.
Daily Example: If you have daily repetition and you set this setpoint to 2, then
every second day from first occurrence of Timer 2 Function (page 508),
the Timer 2 Function (page 508) will be activated.
Range [units]: 1 .. 60 [week]. This setpoint adjust that every X week the timer
will be activated.
Example: If you have weekly repetition and you set this setpoint to 2, then
Weekly
every second week from first occurrence of Timer 2 Function (page 508),
the Timer 2 Function (page 508) will be activated in selected days
adjusted by Timer 2 Day (page 512).
Range [units]: 1 .. 12 [month]. This setpoint adjust that every X month the timer
will be activated.
Example: If you have monthly repetition and you set this setpoint to 2, then
every second month from first occurrence of Timer 2 Function (page 508),
Monthly
the Timer 2 Function (page 508) will be activated in selected day of month
adjusted by Timer 2 Repeat Day In Month (page 512) or in selected days
of week of month adjusted by Timer 2 Day (page 512) and Timer 2
Repeat Week In Month (page 513).
Range [units]: [HH:MM]. This setpoint adjust that every X short period the timer
will be activated.
Short Period Example: If you have short period repetition and you set this setpoint to 2,
then every second minute from first occurrence of Timer 2 Function (page
508), the Timer 2 Function (page 508) will be activated.
Timer 2 Function (page 508) counter is running on the weekends and Timer 2
Including
Function (page 508) can be active.
Timer 2 Function (page 508) counter is running on the weekends but Timer 2
Skip
Function (page 508) isn’t active.
Timer 2 Function (page 508) counter isn’t running on the weekends and Timer 2
Function (page 508) isn’t active. If the activation of timer is counted on the
Postpone
weekend, than timer will be activated after weekend. Another activation of timer is
counted from original date of first occurrence date.
Timer 3 Function
Timer 3 Duration
Timer 3 Repetition
Chose one day in month when Timer 3 Function (page 516) will be
Repeated Day
activated.
Chose days in one week when Timer 3 Function (page 516) will be
Repeated Day In Week
activated.
Range [units]: 1 .. 1000 [day]. This setpoint adjust that every X day the timer
will be activated.
Daily Example: If you have daily repetition and you set this setpoint to 3, then
every second day from first occurrence of Timer 3 Function (page 516),
the Timer 3 Function (page 516) will be activated.
Range [units]: 1 .. 60 [week]. This setpoint adjust that every X week the timer
will be activated.
Example: If you have weekly repetition and you set this setpoint to 3, then
Weekly
every second week from first occurrence of Timer 3 Function (page 516),
the Timer 3 Function (page 516) will be activated in selected days
adjusted by Timer 3 Day (page 520).
Range [units]: 1 .. 12 [month]. This setpoint adjust that every X month the timer
will be activated.
Example: If you have monthly repetition and you set this setpoint to 3, then
every second month from first occurrence of Timer 3 Function (page 516),
Monthly
the Timer 3 Function (page 516) will be activated in selected day of month
adjusted by Timer 3 Repeat Day In Month (page 520) or in selected days
of week of month adjusted by Timer 3 Day (page 520) and Timer 3
Repeat Week In Month (page 521).
Range [units]: [HH:MM]. This setpoint adjust that every X short period the timer
will be activated.
Short Period Example: If you have short period repetition and you set this setpoint to 3,
then every second minute from first occurrence of Timer 3 Function (page
516), the Timer 3 Function (page 516) will be activated.
Timer 3 Function (page 516) counter is running on the weekends and Timer 3
Including
Function (page 516) can be active.
Timer 3 Function (page 516) counter is running on the weekends but Timer 3
Skip
Function (page 516) isn’t active.
Timer 3 Function (page 516) counter isn’t running on the weekends and Timer 3
Function (page 516) isn’t active. If the activation of timer is counted on the
Postpone
weekend, than timer will be activated after weekend. Another activation of timer is
counted from original date of first occurrence date.
Timer 4 Function
Timer 4 Duration
Timer 4 Repetition
Chose one day in month when Timer 4 Function (page 524) will be
Repeated Day
activated.
Chose days in one week when Timer 4 Function (page 524) will be
Repeated Day In Week
activated.
Range [units]: 1 .. 1000 [day]. This setpoint adjust that every X day the timer
will be activated.
Daily Example: If you have daily repetition and you set this setpoint to 4, then
every second day from first occurrence of Timer 4 Function (page 524),
the Timer 4 Function (page 524) will be activated.
Range [units]: 1 .. 60 [week]. This setpoint adjust that every X week the timer
will be activated.
Example: If you have weekly repetition and you set this setpoint to 4, then
Weekly
every second week from first occurrence of Timer 4 Function (page 524),
the Timer 4 Function (page 524) will be activated in selected days
adjusted by Timer 4 Day (page 528).
Range [units]: 1 .. 12 [month]. This setpoint adjust that every X month the timer
will be activated.
Example: If you have monthly repetition and you set this setpoint to 4, then
every second month from first occurrence of Timer 4 Function (page 524),
Monthly
the Timer 4 Function (page 524) will be activated in selected day of month
adjusted by Timer 4 Repeat Day In Month (page 528) or in selected days
of week of month adjusted by Timer 4 Day (page 528) and Timer 4
Repeat Week In Month (page 529).
Range [units]: [HH:MM]. This setpoint adjust that every X short period the timer
will be activated.
Short Period Example: If you have short period repetition and you set this setpoint to 4,
then every second minute from first occurrence of Timer 4 Function (page
524), the Timer 4 Function (page 524) will be activated.
Timer 4 Function (page 524) counter is running on the weekends and Timer 4
Including
Function (page 524) can be active.
Timer 4 Function (page 524) counter is running on the weekends but Timer 4
Skip
Function (page 524) isn’t active.
Timer 4 Function (page 524) counter isn’t running on the weekends and Timer 4
Function (page 524) isn’t active. If the activation of timer is counted on the
Postpone
weekend, than timer will be activated after weekend. Another activation of timer is
counted from original date of first occurrence date.
Timer 5 Function
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.
Timer 5 Repetition
Chose one day in month when Timer 5 Function (page 532) will be
Repeated Day
activated.
Chose days in one week when Timer 5 Function (page 532) will be
Repeated Day In Week
activated.
Range [units]: 1 .. 1000 [day]. This setpoint adjust that every X day the timer
will be activated.
Daily Example: If you have daily repetition and you set this setpoint to 4, then
every second day from first occurrence of Timer 5 Function (page 532),
the Timer 5 Function (page 532) will be activated.
Range [units]: 1 .. 60 [week]. This setpoint adjust that every X week the timer
will be activated.
Example: If you have weekly repetition and you set this setpoint to 4, then
Weekly
every second week from first occurrence of Timer 5 Function (page 532),
the Timer 5 Function (page 532) will be activated in selected days
adjusted by Timer 5 Day (page 536).
Range [units]: 1 .. 12 [month]. This setpoint adjust that every X month the timer
will be activated.
Example: If you have monthly repetition and you set this setpoint to 4, then
every second month from first occurrence of Timer 5 Function (page 532),
Monthly
the Timer 5 Function (page 532) will be activated in selected day of month
adjusted by Timer 5 Repeat Day In Month (page 536) or in selected days
of week of month adjusted by Timer 5 Day (page 536) and Timer 5
Repeat Week In Month (page 537).
Range [units]: [HH:MM]. This setpoint adjust that every X short period the timer
will be activated.
Short Period Example: If you have short period repetition and you set this setpoint to 4,
then every second minute from first occurrence of Timer 5 Function (page
532), the Timer 5 Function (page 532) will be activated.
Timer 5 Function (page 532) counter is running on the weekends and Timer 5
Including
Function (page 532) can be active.
Timer 5 Function (page 532) counter is running on the weekends but Timer 5
Skip
Function (page 532) isn’t active.
Timer 5 Function (page 532) counter isn’t running on the weekends and Timer 5
Function (page 532) isn’t active. If the activation of timer is counted on the
Postpone
weekend, than timer will be activated after weekend. Another activation of timer is
counted from original date of first occurrence date.
Timer 6 Function
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.
Timer 6 Repetition
Chose one day in month when Timer 6 Function (page 540) will be
Repeated Day
activated.
Chose days in one week when Timer 6 Function (page 540) will be
Repeated Day In Week
activated.
Range [units]: 1 .. 1000 [day]. This setpoint adjust that every X day the timer
will be activated.
Daily Example: If you have daily repetition and you set this setpoint to 4, then
every second day from first occurrence of Timer 6 Function (page 540),
the Timer 6 Function (page 540) will be activated.
Range [units]: 1 .. 60 [week]. This setpoint adjust that every X week the timer
will be activated.
Example: If you have weekly repetition and you set this setpoint to 4, then
Weekly
every second week from first occurrence of Timer 6 Function (page 540),
the Timer 6 Function (page 540) will be activated in selected days
adjusted by Timer 6 Day (page 544).
Range [units]: 1 .. 12 [month]. This setpoint adjust that every X month the timer
will be activated.
Example: If you have monthly repetition and you set this setpoint to 4, then
every second month from first occurrence of Timer 6 Function (page 540),
Monthly
the Timer 6 Function (page 540) will be activated in selected day of month
adjusted by Timer 6 Repeat Day In Month (page 544) or in selected days
of week of month adjusted by Timer 6 Day (page 544) and Timer 6
Repeat Week In Month (page 545).
Range [units]: [HH:MM]. This setpoint adjust that every X short period the timer
will be activated.
Short Period Example: If you have short period repetition and you set this setpoint to 4,
then every second minute from first occurrence of Timer 6 Function (page
540), the Timer 6 Function (page 540) will be activated.
Timer 6 Function (page 540) counter is running on the weekends and Timer 6
Including
Function (page 540) can be active.
Timer 6 Function (page 540) counter is running on the weekends but Timer 6
Skip
Function (page 540) isn’t active.
Timer 6 Function (page 540) counter isn’t running on the weekends and Timer 6
Function (page 540) isn’t active. If the activation of timer is counted on the
Postpone
weekend, than timer will be activated after weekend. Another activation of timer is
counted from original date of first occurrence date.
Timer 7 Function
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.
Timer 7 Repetition
Chose one day in month when Timer 7 Function (page 548) will be
Repeated Day
activated.
Chose days in one week when Timer 7 Function (page 548) will be
Repeated Day In Week
activated.
Range [units]: 1 .. 1000 [day]. This setpoint adjust that every X day the timer
will be activated.
Daily Example: If you have daily repetition and you set this setpoint to 4, then
every second day from first occurrence of Timer 7 Function (page 548),
the Timer 7 Function (page 548) will be activated.
Range [units]: 1 .. 60 [week]. This setpoint adjust that every X week the timer
will be activated.
Example: If you have weekly repetition and you set this setpoint to 4, then
Weekly
every second week from first occurrence of Timer 7 Function (page 548),
the Timer 7 Function (page 548) will be activated in selected days
adjusted by Timer 7 Day (page 552).
Range [units]: 1 .. 12 [month]. This setpoint adjust that every X month the timer
will be activated.
Example: If you have monthly repetition and you set this setpoint to 4, then
every second month from first occurrence of Timer 7 Function (page 548),
Monthly
the Timer 7 Function (page 548) will be activated in selected day of month
adjusted by Timer 7 Repeat Day In Month (page 552) or in selected days
of week of month adjusted by Timer 7 Day (page 552) and Timer 7
Repeat Week In Month (page 553).
Range [units]: [HH:MM]. This setpoint adjust that every X short period the timer
will be activated.
Short Period Example: If you have short period repetition and you set this setpoint to 4,
then every second minute from first occurrence of Timer 7 Function (page
548), the Timer 7 Function (page 548) will be activated.
Timer 7 Function (page 548) counter is running on the weekends and Timer 7
Including
Function (page 548) can be active.
Timer 7 Function (page 548) counter is running on the weekends but Timer 7
Skip
Function (page 548) isn’t active.
Timer 7 Function (page 548) counter isn’t running on the weekends and Timer 7
Function (page 548) isn’t active. If the activation of timer is counted on the
Postpone
weekend, than timer will be activated after weekend. Another activation of timer is
counted from original date of first occurrence date.
Timer 8 Function
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.
Timer 8 Repetition
Chose one day in month when Timer 8 Function (page 556) will be
Repeated Day
activated.
Chose days in one week when Timer 8 Function (page 556) will be
Repeated Day In Week
activated.
Range [units]: 1 .. 1000 [day]. This setpoint adjust that every X day the timer
will be activated.
Daily Example: If you have daily repetition and you set this setpoint to 4, then
every second day from first occurrence of Timer 8 Function (page 556),
the Timer 8 Function (page 556) will be activated.
Range [units]: 1 .. 60 [week]. This setpoint adjust that every X week the timer
will be activated.
Example: If you have weekly repetition and you set this setpoint to 4, then
Weekly
every second week from first occurrence of Timer 8 Function (page 556),
the Timer 8 Function (page 556) will be activated in selected days
adjusted by Timer 8 Day (page 560).
Range [units]: 1 .. 12 [month]. This setpoint adjust that every X month the timer
will be activated.
Example: If you have monthly repetition and you set this setpoint to 4, then
every second month from first occurrence of Timer 8 Function (page 556),
Monthly
the Timer 8 Function (page 556) will be activated in selected day of month
adjusted by Timer 8 Repeat Day In Month (page 560) or in selected days
of week of month adjusted by Timer 8 Day (page 560) and Timer 8
Repeat Week In Month (page 561).
Range [units]: [HH:MM]. This setpoint adjust that every X short period the timer
will be activated.
Short Period Example: If you have short period repetition and you set this setpoint to 4,
then every second minute from first occurrence of Timer 8 Function (page
556), the Timer 8 Function (page 556) will be activated.
Timer 8 Function (page 556) counter is running on the weekends and Timer 8
Including
Function (page 556) can be active.
Timer 8 Function (page 556) counter is running on the weekends but Timer 8
Skip
Function (page 556) isn’t active.
Timer 8 Function (page 556) counter isn’t running on the weekends and Timer 8
Function (page 556) isn’t active. If the activation of timer is counted on the
Postpone
weekend, than timer will be activated after weekend. Another activation of timer is
counted from original date of first occurrence date.
Rental Timer 1
When the Rental Timer 1 (page 563) elapsed during engine run the Gen-set will not stop immediately.
The adjustable Rental Timer BOC (page 567) timer will start in this moment. The engine will be cooled
and stopped when the Rental Timer BOC (page 567) time elapsed.
The Running Hours Overrun counter will start increment when the engine is continue running after the
Rental Timer 1 (page 563) elapsed.
Note: There is no priority between Rental Timer 1 and Rental Timer 2. The sooner timer will activated
the Rental Timer BOC (page 567) protection.
Rental Timer 2
When the Rental Timer 2 (page 565) elapsed during engine run the Gen-set will not stop immediately.
The adjustable Rental Timer BOC (page 567) timer will start in this moment. The engine will be cooled
and stopped when the Rental Timer BOC (page 567) time elapsed.
The Running Hours Overrun counter will start increment when the engine is continue running after the
Rental Timer 2 (page 565) elapsed.
Note: There is no priority between Rental Timer 1 and Rental Timer 2. The sooner timer will activated
the Rental Timer BOC (page 567) protection.
Subgroup: Geo Fencing
Geo-Fencing
Fence 1 Protection (page 570) and Fence 2 Protection (page 572) are
Disabled
disabled.
Fence 1 Protection (page 570) and Fence 2 Protection (page 572) are
Enabled
enabled.
Fence 1 Protection (page 570) and Fence 2 Protection (page 572) are
LBI Enable enabled only when logical binary input .GEO-FENCING ENABLE (PAGE 717) is
active.
Subgroup: Position
Home Latitude
Note: This value can be also obtained automatically via logical binary input GEO HOME POSITION
(PAGE 716). In case of activation of this binary input for at least 2 seconds, setpoint will be adjusted
automatically from actual coordinates from GPS signal.
Note: This value can be also obtained automatically via logical binary input GEO HOME POSITION
(PAGE 716). In case of activation of this binary input for at least 2 seconds, setpoint will be adjusted
automatically from actual coordinates from GPS signal.
Fence 1 Protection
Protection types
HistRecOnl Position of gen-set 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
571).
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 571).
Sd Position of Gen-set is used for shutdown protection. Protection is activated when
position of the Gen-set is out of Fence 1 Radius (page 571).
BOC Position of Gen-set is used for BOC (Breaker Open and Cooling) protection.
Protection is activated when position of the Gen-set is out of Fence 1 Radius
(page 571).
Note: Protection is activated also when GPS signal is lost for Fence 1 Delay (page 571).
Fence 1 Delay
Fence 2 Protection
Protection types
HistRecOnl Position of gen-set 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
573).
Wrn Position of Gen-set is used for warning protection only. Protection is activated when
position of the Gen-set is out of Fence 2 Radius (page 573).
Sd Position of Gen-set is used for shutdown protection. Protection is activated when
position of the Gen-set is out of Fence 2 Radius (page 573).
BOC Position of Gen-set is used for BOC (Breaker Open and Cooling) protection.
Protection is activated when position of the Gen-set is out of Fence 2 Radius
(page 573).
Note: Protection is activated also when GPS signal is lost for Fence 2 Delay (page 573).
Fence 2 Delay
Subgroup: Slot A
Slot A
Subgroup: Slot B
Slot B
Group: CM-RS232-485
Subgroup: COM1 Setting
COM1 Mode
COM2 Mode
Group: CM-4G-GPS
Subgroup: Cellular Interface
Internet Connection
DNS Mode
Automatic DNS server addresses automatically obtained from a DHCP server are used
DNS IP Address 1 (page 582) and DNS IP Address 2 (page 583) 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
IP Firewall
AirGate Connection
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
584).
IMPORTANT: When this setpoint is changed the controller has to be restarted to apply
changes.
AirGate Address
CM-4G-GPS; CM-
Setpoint group Related FW 2.0.0
Ethernet
Range [units] [-]
Default value global.airgate.link Force value NO
Step [-]
Comm object 24364 Related applications MINT, SPtM
Config level Standard
Only if relevant module is installed + conditioned by the setpoint Internet
Setpoint visibility
Connection (page 577)
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.
Note: This setpoint is common for in-build Ethernet, CM3-Ethernet and CM2-4G-GPS modules.
Direct Connection
CM-Ethernet
Setpoint group Related FW 2.0.0
CM-4G-GPS
Range [units] 0 .. 600 [s]
Default value 60 s Force value NO
Step 1s
Comm object 24098 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
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.
6 back to List of setpoints
Email Address 1
CM-4G-GPS
Setpoint group CM-Ethernet Related FW 2.0.0
Ethernet
Range [units] 0 .. 63 characters [-]
Default value [-] Force value NO
Step [-]
Comm object 24298 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
Enter in this setpoint a valid e-mail address where the alarm and event e-mails shall be sent. Leave this
setpoint blank if alarm and event email should not be send.
Note: This setpoint is common for in-build Ethernet, CM3-Ethernet and CM2-4G-GPS modules.
CM-4G-GPS
Setpoint group CM-Ethernet Related FW 2.0.0
Ethernet
Range [units] 0 .. 63 characters [-]
Default value [-] Force value NO
Step [-]
Comm object 24297 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
Enter in this setpoint a valid e-mail address where the alarm and event e-mails shall be sent. Leave this
setpoint blank if alarm and event email should not be send.
Note: This setpoint is common for in-build Ethernet, CM3-Ethernet and CM2-4G-GPS modules.
Email Address 3
CM-4G-GPS
Setpoint group CM-Ethernet Related FW 2.0.0
Ethernet
Range [units] 0 .. 63 characters [-]
Default value [-] Force value NO
Step [-]
Comm object 24145 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
Enter in this setpoint a valid e-mail address where the alarm and event e-mails shall be sent. Leave this
setpoint blank if alarm and event email should not be send.
Note: This setpoint is common for in-build Ethernet, CM3-Ethernet and CM2-4G-GPS modules.
CM-4G-GPS
Setpoint group CM-Ethernet Related FW 2.0.0
Ethernet
Range [units] 0 .. 63 characters [-]
Default value [-] Force value NO
Step [-]
Comm object 24144 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
Enter in this setpoint a valid e-mail address where the alarm and event e-mails shall be sent. Leave this
setpoint blank if alarm and event email should not be send.
Note: This setpoint is common for in-build Ethernet, CM3-Ethernet and CM2-4G-GPS modules.
Subgroup: Message Settings
E-mail/SMS Language
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] Depends on CU languages [-]
Default value English Force value YES*
Step [-]
Comm object 24299 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
Use this setpoint to set the language of SMS and e-mail.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] ON / OFF [-]
Default value ON Force value YES*
Step [-]
Comm object 10926 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
This setpoint enables or disables Event Messages.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Wrn Message
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] ON / OFF [-]
Default value ON Force value YES*
Step [-]
Comm object 8482 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
This setpoint enables or disables Wrn Messages.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] ON / OFF [-]
Default value ON Force value YES*
Step [-]
Comm object 10566 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
This setpoint enables or disables BOC Messages.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Sd Message
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] ON / OFF [-]
Default value ON Force value YES*
Step [-]
Comm object 8484 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
This setpoint enables or disables Sd Message.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] ON / OFF [-]
Default value ON Force value YES*
Step [-]
Comm object 8485 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
This setpoint enables or disables sending of Slow Stop Messages.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Telephone Number 1
Telephone Number 3
Subgroup: GPS Settings
GPS Tracking
NTP Server
Time Zone
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] GMT-12:00 .. GMT+13:00 [hours]
Default value GMT+1:00 hour Force value NO
Step [-]
Comm object 24366 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
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.
Note: This setpoint is common for in-build Ethernet, CM3-Ethernet and CM2-4G-GPS modules.
Subgroup: TCP/IP Settings
IP Address Mode
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.
Subnet Mask
DNS Mode
Automatic DNS server addresses automatically obtained from a DHCP server are used
DNS IP Address 1 (page 602) and DNS IP Address 2 (page 602) 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 2
Subgroup: AirGate Settings
AirGate Port
DISABLED: This is a standard mode in which the controller listens to the incoming traffic and
answers the TCP/IP queries addressed to it. This mode requires the controller to
be accessible from the remote device (PC), i.e. it must be accessible at a public
and static IP address if you want to connect to it from the internet.
ENABLED This mode enables the AirGate service. The AirGate server address is adjusted by
the setpoint AirGate Address (page 584). Also the standard TCP/IP is enabled.
Direct Connection
Subgroup: MODBUS Settings
MODBUS Server
NTP Server
CM-4G-GPS; CM-
Setpoint group Related FW 2.0.0
Ethernet
Range [units] DISABLED / ENABLED [-]
Default value DISABLED Force value NO
Step [-]
Comm object 23934 Related applications MINT, SPtM
Config level Standard
Only if relevant module is installed + conditioned by the setpoint Internet
Setpoint visibility
Connection (page 577)
Description
This setpoint is used to enable/disable controller time synchronization with exact time from an NTP server.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
SNMP Agent
Subgroup: E-mail Settings
SMTP UserName
SMTP Encryption
BOC Message
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] ON / OFF [-]
Default value ON Force value YES*
Step [-]
Comm object 10566 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
This setpoint enables or disables BOC Messages.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
E-mail/SMS Language
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] Depends on CU languages [-]
Default value English Force value YES*
Step [-]
Comm object 24299 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
Use this setpoint to set the language of SMS and e-mail.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] ON / OFF [-]
Default value ON Force value YES*
Step [-]
Comm object 10926 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
This setpoint enables or disables Event Messages.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Sd Message
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] ON / OFF [-]
Default value ON Force value YES*
Step [-]
Comm object 8484 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
This setpoint enables or disables Sd Message.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] ON / OFF [-]
Default value ON Force value YES*
Step [-]
Comm object 8482 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
This setpoint enables or disables Wrn Messages.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Stp Message
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] ON / OFF [-]
Default value ON Force value YES*
Step [-]
Comm object 8485 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
Description
This setpoint enables or disables sending of Slow Stop Messages.
This setpoint is common for CM3-Ethernet and CM2-4G-GPS modules.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
NTP Server
CM-4G-GPS
Setpoint group Related FW 2.0.0
CM-Ethernet
Range [units] GMT-12:00 .. GMT+13:00 [hours]
Default value GMT+1:00 hour Force value NO
Step [-]
Comm object 24366 Related applications MINT, SPtM
Config level Standard
Setpoint visibility Only if relevant module is installed
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.
Note: This setpoint is common for in-build Ethernet, CM3-Ethernet and CM2-4G-GPS modules.
Group: Ethernet
Subgroup: AirGate Settings
AirGate Port
DISABLED: This is a standard mode in which the controller listens to the incoming traffic and
answers the TCP/IP queries addressed to it. This mode requires the controller to
be accessible from the remote device (PC), i.e. it must be accessible at a public
and static IP address if you want to connect to it from the internet.
ENABLED This mode enables the AirGate service. The AirGate server address is adjusted by
the setpoint AirGate Address (page 584). Also the standard TCP/IP is enabled.
Direct Connection
Subgroup: E-mail Settings
SMTP UserName
SMTP Encryption
Subgroup: MODBUS Settings
MODBUS Server
Subgroup: RTC Synchronization
NTP Server
SNMP Agent
IP Address Mode
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.
Subnet Mask
DNS Mode
Automatic DNS server addresses automatically obtained from a DHCP server are used.
DNS IP Address 1 (page 626) and DNS IP Address 2 (page 626) 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 2
Group: EM-BIO8-EFCP
Subgroup: EFCP Settings
8.1.3 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 a full list of values go to the chapter List of values (page 630).
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 failure 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.
Group: Engine 633 Generator Voltage L2-L3 641 Group: Load 649
RPM 633 Generator Voltage L2-N 642 Load P 649
ECU State 633 Generator Voltage L3-L1 642 Load Q 649
ECU Frequency Select 633 Generator Voltage L3-N 642 Load Power Factor 649
ECU AIN 1 634 Nominal Current 642 Group: Mains 649
ECU AIN 2 634 Nominal Power 643 Mains Frequency 649
ECU AIN 3 634 Nominal Voltage 643 Mains Voltage L1-N 650
ECU AIN 4 634 Slip Angle 643 Mains Voltage L2-N 650
ECU AIN 5 635 Slip Frequency 643 Mains Voltage L3-N 650
ECU AIN 6 635 Generator Current L1 644 Mains Voltage L1-L2 650
ECU AIN 7 635 Generator Load Current L2644 Mains Voltage L2-L3 650
ECU AIN 8 635 Load Current L3 644 Mains Voltage L3-L1 651
ECU AIN 9 636 Generator P 644 Max Vector Shift 651
ECU AIN 10 636 Generator P L1 644 Mains Import P 651
ECU AIN 11 636 Generator P L2 645 Mains Import Q 651
ECU AIN 12 636 Generator P L3 645 Mains PF 652
ECU AIN 13 637 Generator Q 645 Mains Load Character 652
ECU AIN 14 637 Generator Q L1 645 Mains Load Character L1 652
ECU AIN 15 637 Generator Q L2 645 Mains Load Character L2 652
ECU AIN 16 637 Generator Q L3 646 Mains Load Character L3 653
ECU AIN 17 638 Generator S 646 ROCOF 653
ECU AIN 18 638 Generator S L1 646 Max ROCOF 653
ECU AIN 19 638 Generator S L2 646 Group: User Buttons 653
ECU AIN 20 638 Generator S L3 646 User Button 1 653
ECU-AIN-EXT-1 639 Generator Power Factor 647 Group: Controller I/O 654
Running Nominal Power In Time Till Empty 2 668 Log Bout 9 677
PM 661 Time Till Empty 3 668 Group: Fixed Protection
Running Nominal Power Num Starts 668 States 677
Of All 661 Pulse Counter 1 669 Fixed Protections States 1 677
Available Nominal Power Pulse Counter 2 669 Fixed Protections States 2 677
In PM 661 Running Hours 669 Fixed Protections States 3 678
Group: Speed/Load Control 662 Fixed Protections States 4 678
Group: Info 669
Required P Target 662 Active Application 669 Fixed Protections States 5 678
Loadsharing Output 662 Application 670 Group: User Protection
Speed Regulator Output 662 States 678
Breaker State 670
Group: Voltage/PF Control 662 User Protections States 1 678
Connection Type 670
Required P 662 Group: SH Modules 679
Engine State 670
Reactive Q 663 SHAIN-1 1 679
SW Key Feature List 671
Required PF Character 663 SHAIN-1 2 679
CAN16 671
Required Qrel 663 SHAIN-1 3 679
CAN32 671
Varsharing Output 663 SHAIN-1 4 680
CAN48 671
Voltage Regulator Output 663 SHAIN-2 1 680
CAN64 672
Voltage Request 664 SHAIN-2 2 680
RPM
ECU State
ECU AIN 2
ECU AIN 3
ECU AIN 4
ECU AIN 6
ECU AIN 7
ECU AIN 8
ECU AIN 10
ECU AIN 11
ECU AIN 12
ECU AIN 14
ECU AIN 15
ECU AIN 16
ECU AIN 18
ECU AIN 19
ECU AIN 20
ECU-AIN-EXT-2
Speed Request
Engine
Value group Related FW 2.0.0
Speed/Load Control
Units %
Comm object 10137 Related applications MINT, SPtM
Description
This value contains the speed control signal expressed in %. This value is used for digital interfacing (via a
communication bus) with ECUs that require the requested speed in %.
Note: Accelerator pedal position will be 0 if the engine is not running or loaded.
DEF Level
Generator Frequency
Nominal Current
Nominal Voltage
Slip Angle
Slip Frequency
Load Current L3
Generator P
Generator P L1
Generator P L3
Generator Q
Generator Q L1
Generator Q L2
Generator S
Generator S L1
Generator S L2
Generator S L3
Load P
Load Q
Group: Mains
Mains Frequency
Mains Import P
Mains Import Q
ROCOF
Max ROCOF
Group: User Buttons
User Button 1
Battery Volts
D+
Analog Input 1
Analog Input 2
Analog Input 3
Binary Inputs
Coolant Temp
Fuel Level
E-Stop
Binary Outputs
Start Reserve
Stop Reserve
Note: DSR is used by power management only when it operates in the absolute mode (#Power
Management Mode (page 408) is set to ABS (kW)).
Note: DSR is received automatically from the IS-NTC HYBRID controller via CAN2 bus.
Note: DSRO is used by power management only when it operates in the absolute mode (#Power
Management Mode (page 408) is set to ABS (kW)).
Note: DSRO is received automatically from the IS-NTC HYBRID controller via CAN2 bus.
Engine Priority
Total Running P
Total Running S
Required P Target
Loadsharing Output
Required P
Required PF Character
Required Qrel
Varsharing Output
Group: Statistics
Genset kWh
Genset kVArh
Mains kWh
Mains kVArh
Rental 1
Rental 2
Shutdowns
Num Starts
Pulse Counter 2
Running Hours
Group: Info
Active Application
IL Info
Value group Related FW 2.0.0
Info
Units [-]
Comm object 8480 Related applications MINT, SPtM
Description
The value contains actual application in controller.
Example: GC or AGC (Gen-set controller or advanced Gen-set controller).
Breaker State
IL Info
Value group Related FW 2.0.0
Info
Units [-]
Comm object 9245 Related applications MINT, SPtM
Description
The value contains actual "breaker state" message which is shown on the main screen of the controller.
Connection Type
IL Info
Value group Related FW 2.0.0
Info
Units [-]
Comm object 12944 Related applications MINT, SPtM
Description
The text of this value represents the connection type which is adjusted in setpoint Connection type (page
309).
Engine State
IL Info
Value group Related FW 2.0.0
Info
Units [-]
Comm object 9244 Related applications MINT, SPtM
Description
The value contains actual "engine state" message which is shown on the main screen of the controller.
CAN16
CAN32
CAN48
Reg16
Reg32
FW Branch
IL Info
Value group Related FW 2.0.0
Info
Units [-]
Comm object 8707 Related applications MINT, SPtM
Description
The value contains actual branch of firmware in controller.
IL Info
Value group Related FW 2.0.0
Info
Units [-]
Comm object 24339 Related applications MINT, SPtM
Description
Major and minor firmware version number.
Gen Loaded 16
Gen Loaded 32
IL Info
Value group Related FW 2.0.0
Info
Units [-]
Comm object 24501 Related applications MINT, SPtM
Description
Name of controller which is used in InteliConfig in command bar.
IL Info
Value group Info Related FW 2.0.0
Load shedding
Units [-]
Comm object 9591 Related applications MINT, SPtM
Description
The value contains actual "load shedding stage". The Value can get the values of the range 0 to 52, where
0 means no load shedding stage is active and 1, 2, 3, 4 or 5 means that the corresponding load shedding
stage is active.
SPI Module A
IL Info
Value group Related FW 2.0.0
Info
Units [-]
Comm object 14447 Related applications MINT, SPtM
Description
The name of plug-in module which is inserted in slot A.
SPI Module B
IL Info
Value group Related FW 2.0.0
Info
Units [-]
Comm object 14448 Related applications MINT, SPtM
Description
The name of plug-in module which is inserted in slot B.
IL Info
Value group Related FW 2.0.0
Info
Units [-]
Comm object 10040 Related applications MINT, SPtM
Description
The value contains the numeric code of the "Current process timer" text which is shown on the main
screen of the controller.
The assignment of texts to the codes can be obtained using InteliConfig. Open any connection (also offline
with a previously saved archive) and go to the Tools ribbon -> Generate CFG image (all). The resulting file
will contain the assignment of texts to the codes.
Timer Value
IL Info
Value group Related FW 2.0.0
Info
Units [HH:MM:SS]
Comm object 14147 Related applications MINT, SPtM
Description
The value contains the "Current process timer" value which is shown on the main screen of the controller.
Log Bout 1
Log Bout 2
Log Bout 4
Log Bout 5
Log Bout 6
Log Bout 7
Log Bout 9
Fixed Protection
Value group Related FW 2.0.0
States
Units [-]
Comm object 20744 Related applications MINT, SPtM
Description
Values of LBO Fixed Protections State.
Fixed Protection
Value group Related FW 2.0.0
States
Units [-]
Comm object 20745 Related applications MINT, SPtM
Description
Values of LBO Fixed Protections State.
Fixed Protection
Value group Related FW 2.0.0
States
Units [-]
Comm object 20746 Related applications MINT, SPtM
Description
Values of LBO Fixed Protections State.
Fixed Protection
Value group Related FW 2.0.0
States
Units [-]
Comm object 20747 Related applications MINT, SPtM
Description
Values of LBO Fixed Protections State.
Fixed Protection
Value group Related FW 2.0.0
States
Units [-]
Comm object 20748 Related applications MINT, SPtM
Description
Values of LBO Fixed Protections State.
SHAIN-1 1
SHAIN-1 2
SHAIN-1 3
SHAIN-2 1
SHAIN-2 2
SHAIN-2 3
SHBIN-1
SHBIN-3
SHBIN-5
SHBOUT-1
SHBOUT-3
SHBOUT-5
Group: Date/Time
Date
Time
EM BIO A
EM BIO B
Group: PLC
PLC-BOUT 1
PLC-BOUT 2
PLC-BOUT 4
PLC-BOUT 5
PLC-BOUT 6
PLC-BOUT 7
PLC Resource 2
PLC Resource 3
PLC Resource 4
PLC Resource 5
PLC Resource 7
PLC Resource 8
For a full list of Logical binary inputs go to the chapter Logical binary inputs alphabetically (page 693).
Access Lock 694 ECU Wait To Start Fast Pulse Counter 1 726
AMF Start Block 694 Blink 703 Pulse Counter 2 726
ATT DEF Level Lamp ECU Wait To Start Solid 703 Rem TEST On Load 727
Blink 695 ECU Yellow Lamp Blink 703 Remote AUTO 728
ATT DEF Level Lamp ECU Yellow Lamp Fast Remote Ctrl Lock 728
Fast Blink 695 Blink 703
Remote MAN 728
ATT DEF Level Lamp ECU Yellow Lamp Solid 704
Remote OFF 729
Solid 695 Emergency MAN 704
Remote Start/Stop 730
ATT DPF Lamp Blink 695 Emergency Stop 704
Remote TEST 731
ATT DPF Lamp Fast Blink695 External Mains Fail Relay 705
Sd Override 733
ATT DPF Lamp Solid 696 Fault Reset Button 705
Start Blocking 733
ATT Force Regen 696 Force Droop Oper 705
Start Button 734
ATT HEST Lamp Blink 696 Force Island 705
Starter 1 Disabled 734
ATT HEST Lamp Fast Force Parallel 706
Starter 2 Disabled 734
Blink 696
Fuel Pump On/Off 714
Starter Priority 734
ATT HEST Lamp Solid 696
GCB Button 714
Stop Button 734
ATT Inhibit Regen 697
GCB Disable 714
Top Priority 736
ATT Inhibited Lamp Blink 697
GCB Feedback 715
Total Emergency Stop 736
ATT Inhibited Lamp Fast
Geo Home Position 716
Blink 697
Geo-Fencing Enable 717 6 back to Controller
ATT Inhibited Lamp Solid 697 objects
Group Link 717
ATT Interlock 697
Horn Reset Button 717
ATT SCR Error Lamp
Idle Speed 717
Blink 698
Load Res 2 Active 718
ATT SCR Error Lamp
Fast Blink 698 Mains Fail Block 719
Application MINT
Application SPTM
LBI: B
Battery Charger
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 623
Description
When binary input is active and its delay Battery Charger Fail Delay (page 352) is out of time then alarm
Wrn Battery Charger Fail (page 842) is activated.
LBI: C
Coolant Temp
LBI: E
ECU Communication Fail Block
LBI: F
Fault Reset Button
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 191
Description
Binary input has the same function as Fault Reset button on the InteliGen 500 G2 front panel.
Fuel Level
IMPORTANT: When binary input FUEL PUMP ON/OFF (PAGE 714) is configured then binary
output FUEL PUMP (PAGE 763) is control by this binary input.
IMPORTANT: It is necessary to configure analog input FUEL LEVEL (PAGE 807) for proper
function of this binary input.
LBI: G
GCB Button
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 193
Description
Binary input has the same function as the GCB button on the InteliGen 500 G2 front panel. It is
evaluated in MAN mode only.
LBI: H
Horn Reset Button
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 192
Description
Binary input has the same function as Horn reset button on the InteliGen 500 G2 front panel.
LBI: I
Idle Speed
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 624
Description
This binary input changes cooling speed from nominal to idle.
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.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
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.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
LBI: M
Mains Fail Block
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 622
Description
If the input is active, the automatic start of the Gen-set at Mains failure is blocked. In case of running Gen-
set in AUTO mode, timer Mains Return Delay (page 383) is started and when it elapses GCB is opened,
Gen-set goes to cooling procedure and stops. When GCB is opened after Open Transfer Min Break
(page 436) the MCB is closed.
Note: This input simulates healthy Mains.
This binary input has the same function as MCB button on the InteliGen 500 G2 front panel. It is
evaluated in MAN mode only.
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.
IMPORTANT: All controllers cooperating together in Power management must have the
same minimal running power 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. See the diagram of such
distribution in the description of the input LOAD RES 2 ACTIVE (PAGE 718).
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
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.
IMPORTANT: All controllers cooperating together in Power management must have the
same minimal running power 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. See the diagram of such
distribution in the description of the input LOAD RES 2 ACTIVE (PAGE 718).
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
LBI: O
Oil Pressure
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 43
Description
Binary input for Oil Pressure indication.
IMPORTANT: This binary input is also used for evaluating engine running condition.
Example: Normally close connection – when LBI is active then oil pressure is OK and is higher than
starting oil pressure.
Note: In case that you want to use binary input Oil Pressure just for protection please create new
binary input with User protection.
LBI: P
Prestart Bypass
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 42
Description
While this LBI is active, Gen-set skips prestart phase.
Note: Some of the fixed protections has possibility to turn off. These protections has dedicated
setpoints located in setpoint group Protections. Setpoints have options: Enabled, Disabled (protection
is turned off), ExtDisabled (protection is turned off by LBI).
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Run Indication 2*
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
Note: *) Only available in the Extended features version. For more information see Extended
features on page 154.
LBI: S
Sd Override
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 44
Description
If this input is active, all alarms except Emergency Stop and Overspeed are suppressed. The suppressed
alarms will be displayed in the alarm list, but they will not take effect regarding the Gen-set control.
Note: Sd Override (page 733) is indicated in the alarm list if Sd Override mode is active to inform the
operator that the engine is not protected.
Binary input has the same function as Start Button on the InteliGen 500 G2 front panel. It is evaluated
in MAN mode only.
Binary input has the same function as Stop Button on the InteliGen 500 G2 front panel. It is evaluated
in MAN Mode only.
For a full list of Logical binary inputs go to the chapter Logical binary outputs alphabetically (page 738).
AIN Switch01 740 ATT Regen ACK Lamp 751 GCB Close/Open 764
AIN Switch02 740 ATT SCR Error Lamp 751 MGCB OFF Coil 766
AIN Switch03 741 AVR Down 752 MGCB ON Coil 767
AIN Switch04 741 AVR Up 752 MGCB UV Coil 769
AIN Switch05 742 Bus Healthy 752 GeneratorBus Healthy 771
AIN Switch06 742 Common Alarm Active Gen-set Active 771
AIN Switch07 743 Level 1 752 Glow Plugs 771
AIN Switch08 743 Common Alarm Active Heartbeat 773
Level 2 753
AIN Switch09 744 Horn 773
Common Alarm Level 1 753
AIN Switch10 744 HornRes Button Echo 774
Common Alarm Level 2 753
Air Valves 745 Idle/Nominal 775
Cooling 753
AL Common BOC 745 Idle/Nominal Pulse 775
Cooling Pump 754
AL Common Fls 745 Ignition 775
Display Fail 755
Common Mains Ignition On 776
Protection 746 Dummy Load Stage 1 755
In Synchronism 777
AL Common Sd 746 Dummy Load Stage 2 755
Initialized 777
AL Common Stp 746 Dummy Load Stage 3 755
kWh Pulse 777
AL Common Wrn 747 Dummy Load Stage 4 755
Load Shedding Stage 1 778
AL Gen Freq Wrn 747 Dummy Load Stage 5 755
Load Shedding Stage 2 778
AL GenBus Frequency 747 ECU Comm OK 757
Load Shedding Stage 3 778
AL GenBus Voltage 747 ECU Comm Error 758
Load Shedding Stage 4 778
AL Gen Voltage Wrn 747 ECU Power Relay 758
Load Shedding Stage 5 779
AL Maintenance 1 748 ECU Red Lamp 759
Mains Healthy 779
AL Maintenance 2 748 ECU Run Stop 759
Manual Ready 779
AL Maintenance 3 748 ECU Wait To Start 759
MCB Button Echo 780
AL Overcurrent 748 ECU Yellow Lamp 759
MCB Close/Open 780
Alarm 748 Electrical Alarm 759
MCB OFF Coil 781
Alarm Flashing 749 Engines Swapped 760
MCB ON Coil 782
AL Mains Fail 749 Exercise Timer 1 760
MCB UV Coil 784
AL Mains Frequency 749 Exercise Timer 2 760
Mode AUTO 785
AL Mains Voltage 749 Exercise Timer 3 760
Mode MAN 786
ATT DEF Level Lamp 750 Exercise Timer 4 761
Mode OFF 786
ATT DPF Lamp 750 FltRes Button Echo 762
Mode TEST 786
ATT HEST Lamp 750 Forward Synchronization 762
NCB Close/Open 786
ATT Inhibited Lamp 751 Frequency Select 762
Nominal/Idle Pulse 787
ATT Interlock Status 751 Fuel Pump 763
Not In AUTO 787
ATT PCD Lamp 751 Fuel Solenoid 763
Not Used 787
GCB Button Echo 764
6 back to Controller
objects
LBO: B
Bus Healthy
Related FW 2.0.0 Related applications MINT
Comm object 79
Description
This output is active when the bus voltage and frequency are within limits. The limits for under/overvoltage
and under/overfrequency are the same as for generator voltage / frequency and can be found in the
Generator Settings setpoint group.
It works only with Default Application Select (page 289)= MINT, the output is always inactive with
Default Application Select (page 289) = SPTM.
LBO: C
Common Alarm Active Level 1
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 13
Description
This output is closed when there is at least one Alarms level 1 (page 834) in the alarmlis.
Cranking
Cranking Procedure
IMPORTANT: This LBO also affects evaluation of Sd ECU 1 Communication Fail (page 885)
or Wrn ECU Communication Fail (page 847) alarms. With configured LBO ECU Power
Relay, these alarms are evaluated only when this LBO is active. Without configured LBO
ECU Power Relay, these alarm are evaluated all the time.
LBO: F
FltRes Button Echo
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 592
Description
This output provides 1s pulse when:
Fault Reset button is pressed on the controller front facia or
Fault Reset button is pressed on any of external local/remote terminals or
Fault Reset command is received via communication line or
The input FAULT RESET BUTTON (PAGE 705) is activated.
LBO: G
GCB Button Echo
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 35
Description
This output provides 1s pulse when:
GCB button is pressed on the controller front facia or
GCB button is pressed on any of external local/remote terminals or
GCB command is received via communication line or
the input GCB BUTTON is activated.
When the Glow Plugs Time (page 328) is longer than Cranking Fail Pause (page 326) then the Glow
Plugs Time (page 328) in Cranking Fail Pause (page 326) as long as Cranking Fail Pause (page
326).
LBO: H
Heartbeat
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 81
Description
This output toggles on/off in a period of 500 ms whenever the controller is switched on and functional.
LBO: I
Idle Run
Note: Connect binary output Idle/Nominal to speed governor to switch the speed:
opened = Idle
closed = Nominal
(for normally open contact type)
Comm object 80
Description
This output is closed during synchronization when all synchro conditions have been fulfilled.
The output is deactivated either when:
The synchro conditions are lost or
The corresponding breaker has been closed or
The sychronizing was interrupted or timed out.
Synchro conditions are following:
Phase shift between generator and mains (bus) voltage must be within range of ±Phase Window
(page 448) for period longer than Dwell Time (page 448).
Voltage difference between generator and mains (bus) voltage (in all phases) must be lower or
equal to Voltage Window (page 447) for period longer than Dwell Time (page 448).
LBO: K
kWh Pulse
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 206
Description
This output generates a 100ms pulse whenever the internal kWh counter is incremented.
The load shedding outputs are activated (load is being shedd) in the order 1, 2, 3, 4, 5.
The load shedding outputs are deactivated (load is being reconnected) in the order 5, 4, 3, 2, 1.
The load disconnected by the LBO Nr.1 is the less essential load of these three possible loads instances.
The load shedding outputs are activated (load is being shedd) in the order 1, 2, 3, 4, 5.
The load shedding outputs are deactivated (load is being reconnected) in the order 5, 4, 3, 2, 1.
The load disconnected by the LBO Nr.1 is the less essential load of these three possible loads instances.
The load shedding outputs are activated (load is being shedd) in the order 1, 2, 3, 4, 5.
The load shedding outputs are deactivated (load is being reconnected) in the order 5, 4, 3, 2, 1.
The load disconnected by the LBO Nr.1 is the less essential load of these three possible loads instances.
The load shedding outputs are activated (load is beeing shedd) in the order 1, 2, 3, 4, 5.
The load shedding outputs are deactivated (load is beeing reconnected) in the order 5, 4, 3, 2, 1.
The load disconnected by the LBO Nr.1 is the less essential load of these three possible loads instances.
The load shedding outputs are activated (load is beeing shedd) in the order 1, 2, 3, 4, 5.
The load shedding outputs are deactivated (load is beeing reconnected) in the order 5, 4, 3, 2, 1.
The load disconnected by the LBO Nr.1 is the less essential load of these three possible loads instances.
LBO: M
Mains Healthy
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 78
Description
This output is active while mains failure is not detected and mains voltage and frequency is within limits.
Mains Healthy is active when mains f and V are within the protection limits
Mains Healthy deactivates when there is active mains protection level 2
Mains Healthy cannot be activated when there is inactive not confirmed alarm Sd Emergency
Stop (page 889) in the alarmlist
Note: Mains Healthy cannot be activated when there is active ALI Mains Ph Rotation Opposite
(page 858) or ALI Mains Ph L1 Inverted (page 857), ALI Mains Ph L2 Inverted (page 857) or ALI
Mains Ph L3 Inverted (page 858).
LBO: N
NCB Close/Open
Related FW 2.0.0 Related applications MINT
Comm object 50
Description
Neutral circuit breaker Close/Open output controls the generator neutral circuit breaker. It is intended for
contactors – provides a continual active signal if NCB should be closed.
LBO: P
Peak Shaving Active
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 2118
Description
Active anytime, when the peak shaving start condition is fulfilled.
When the Prestart Time (page 327) is longer than Cranking Fail Pause (page 326) then the Prestart
Time (page 327) in Cranking Fail Pause (page 326) is long as Cranking Fail Pause (page 326) minus
100 ms.
LBO: R
Ready
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 62
Description
The binary output is active when the engine is stopped and it is possible to start it i.e. no red alarm is
activated or SD OVERRIDE (PAGE 733) is active.
The binary output is switch on when the Ready state occurs.
The binary output is switch off when the Prestart or the Not Ready or the Stop state occurs i.e. always
except Ready state.
Starting
Note: If Additional running engine indications (page 117) went off during 5 s pause than Stop
Solenoid is not activated again otherwise stop solenoid is activated again.
LBO: T
Temperature Switch
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 563
Description
This is an output from the Temperature switch function. The behavior of the switch depends on the
adjustment of the setpoints Temperature Switch On and Temperature Switch Off.
Note: Setpoints Temperature Switch On and Temperature Switch Off are invisible until
configuration of this LBO.
LBO: V
Ventilation
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 38
Description
This logical binary output is activated at the beginning of start procedure together with PRESTART (PAGE
789) LBO. Ventilation output is deactivated when engine stops revolving.
Ventilation LBO is also deactivated immediately when EMERGENCY STOP (PAGE 704) (or E-Stop) is
activated or when controller is switched to OFF mode.
Note: The output is intended for control of an engine room ventilation fan, engine container ventilation
fan, container louvres or similar running gen-set technology.
For a full list of Logical analog inputs go to the chapter Logical analog inputs alphabetically (page 803).
6 back to Controller
objects
IMPORTANT: This analog input has no protection. Input is designed only to control
appropriate logical binary output.
IMPORTANT: This analog input has no protection. Input is designed only to control
appropriate logical binary output.
IMPORTANT: This analog input has no protection. Input is designed only to control
appropriate logical binary output.
IMPORTANT: This analog input has no protection. Input is designed only to control
appropriate logical binary output.
IMPORTANT: This analog input has no protection. Input is designed only to control
appropriate logical binary output.
IMPORTANT: This analog input has no protection. Input is designed only to control
appropriate logical binary output.
IMPORTANT: This analog input has no protection. Input is designed only to control
appropriate logical binary output.
IMPORTANT: This analog input has no protection. Input is designed only to control
appropriate logical binary output.
IMPORTANT: This analog input has no protection. Input is designed only to control
appropriate logical binary output.
IMPORTANT: This analog input has no protection. Input is designed only to control
appropriate logical binary output.
LAI: C
Coolant Temp
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 67
Description
Logical analog input designed for coolant temperature value received from analog sensor.
LAI: F
Fuel Level
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 78
Description
Logical analog input designed for fuel level value received from analog sensor.
IMPORTANT: For right behavior of this function, curve for analog input has to be in
percentage and setpoint Fuel Tank Volume (page 348) has to be adjusted correctly.
LAI: M
Mains Import Measurement
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 67
Description
Logical analog input designed for Mains import measurement (page 165). Load transfer is considered
to be finished when this value is lower then Mains Unload MCB Open Window (page 439).
LAI: N
Not Used
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 230
Description
Input has no function.
LAI: O
Oil Pressure
Related FW 2.0.0 Related applications MINT, SPtM
Comm object 9
Description
Logical analog input designed for oil pressure value received from analog sensor.
Note: This analog function can by also configured on binary input as binary function. In this case
choose OIL PRESSURE (PAGE 724) binary input in the list of binary inputs. Delay of this binary input is
adjusted via the same setpoint like for analog function.
OR/AND
PLC group Basic logical functions
Related FW 2.0.0
Comm object 1
Inputs
Outputs
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
Input 1 Input 2 Output
0 0 0
0 1 1
1 0 1
1 1 1
Function AND
Input 1 Input 2 Output
0 0 0
0 1 0
1 0 0
1 1 1
There have to be at least 2 inputs every time. There may be up to 8 inputs configured.
Function XOR
Input 1 Input 2 Output
0 0 0
0 1 1
1 0 1
1 1 0
The block contains a setting for RS dominance. This setting is available in the block dialog window (i.e.
this setting is constantly set by configuration and cannot be changed dynamically in operation).
Function RS
R-latch S-latch E-latch JK-latch
Input 1 (S) Input 2 (R)
Q
-1 -1 -1 -1
0 0 Q Q Q Q
0 1 0 0 0 0
1 0 1 1 1 1
-1 -1
1 1 0 1 Q NOT(Q )
Outputs
Description
The block compares the input value with the comparative levels. The behavior depends on whether the
ON level is higher than OFF level or vice versa.
Note: Level On and Level Off can be constants or values from controller.
IMPORTANT: In case that the values on inputs have different decimal numbers, then the
values are converted and the name of block is red. It is strongly recommended to use
values with the same decimal numbers.
Outputs
Description
The block works as an analog switch. It compares the input value with the comparative level. The output
will switch on if the input is equal or higher than the comparative level for time longer than the delay.
Outputs
Description
The block output is switched on whenever the input value is in the range defined by Lo and Hi levels.
Related FW 2.0.0
Comm object 17
Inputs
Outputs
Description
This block performs basic mathematical operations of 2 to 8 operands based on selected function.
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)
IMPORTANT: In case that values on inputs have different decimal numbers or dimensions
than the values are converted and the name of block is red. It is strongly recommended to
use values with the same decimal numbers.
Related FW 2.0.0
Comm object 34
Inputs
Outputs
Description
This block performs a linear transformation of the input. The transformation function is defined by two pairs
Outputs
Description
The block realizes the mathematical operation AxB/C ±D. 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.
Outputs
Description
Note: If Input time up or Input time down value is <0, this input is internally set to zero.
Note: Input time up and Input time down values can be constants or values from controller.
Note: Use Pulse on edge option to choose between delay and pulse mode.
Related FW 2.0.0
Comm object 38
Inputs
Outputs
Description
The block works as a countdown timer which is decreased by 1 every PLC cycle. The timer initial value is
adjustable by the "Reload value" input. The timer is automatically reloaded with the initial value when it
reaches zero or it can be reloaded at any other time using the "reload" input. The timer remains at reload
value until the reload input is deactivated. The timer output is inverted always when the timer is reloaded.
Note: If you want the output to start at logical 0, tick First down option. Otherwise the output will start at
logical 1.
IMPORTANT: If the inputs are not connected and First down option is not ticked, then the
output is active.
Outputs
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.
Related FW 2.0.0
Comm object 20
Inputs
Description
This block works as an analog ramp controlled by binary inputs Up and Down with a defined rite 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.
Related FW 2.0.0
Comm object 22
Inputs
Outputs
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.
The Output has a Resolution and Dimension according to the block settings.
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.
Outputs
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.
Outputs
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 32767. The counter value is lost when the controller is
switched off. The output is activated when the counter value is equal or higher than Input Preset Limit and
Related FW 2.0.0
Comm object 24
Inputs
Outputs
Description
The block converts the input analog value to binary form and provides selected bits as binary outputs.
Outputs
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.S
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.
Outputs
Description
The block converts Input based on selected resolution and dimension and reflects this to Output .
Note: Conversion is done to Integer32, if the input value is out of Integer32 range, output value is set
to invalid status.
Outputs
Description
The block is switching Input 1 and Input 2 based on value of Input SW. The Output has resolution and
dimension based on setting of the block.
IMPORTANT: In case that values on inputs have different decimal numbers or dimensions
than the values are converted and the name of block is red. It is strongly recommended to
use values with the same decimal numbers.
8.2 Alarms
What alarms are:
The controller evaluates two levels of alarms. For more information see Alarm management on page 193.
AL Fuel Transfer Failed 838 Wrn ECU Yellow Lamp 847 Wrn Generator L1
AL Transferring Fuel 838 Wrn ECU Communication Undervoltage 853
Wrn Alarm Email 1 Fail 838 Fail 847 Wrn Generator L1L2
Wrn ECUDiagBlocked 847 Overvoltage 853
Wrn Alarm Email 2 Fail 838
Wrn EM(A) - a message Wrn Generator L1L2
Wrn Alarm Email 3 Fail 838
lost 847 Undervoltage 854
Wrn Alarm Email 4 Fail 839
Wrn EM(A) - configuration Wrn Generator L2
Wrn Alarm SMS 1 Fail 839
mistake 848 Overvoltage 854
Wrn Alarm SMS 2 Fail 839
Wrn EM(A) - insufficient 848 Wrn Generator L2
Wrn Alarm SMS 3 Fail 839 Undervoltage 854
Wrn EM(A) - missing or
Wrn Alarm SMS 4 Fail 840 Wrn Generator L2L3
damaged 848
Wrn ATT DEF Level Overvoltage 855
Wrn EM(B) - a message
Lamp 840 Wrn Generator L2L3
lost 848
Wrn ATT DPF Lamp 840 Undervoltage 855
Wrn EM(B) - configuration
Hst ATT Force Regen mistake 849 Wrn Generator L3
Active 840 Overvoltage 855
Wrn EM(B) - insufficient 849
Wrn ATT HEST Lamp 840 Wrn Generator L3
Wrn EM(B) - missing or
Hst ATT Inhib Regen Undervoltage 855
damaged 849
Active 841 Wrn Generator L3L1
Wrn Emergency Droop
Wrn ATT Inhibited Lamp 841 Overvoltage 856
Active 849
Wrn ATT Interlock Active 841 Wrn Generator L3L1
Wrn Event Email 1 Fail 849
Undervoltage 856
Wrn ATT SCR Error Wrn Event Email 2 Fail 850
Lamp 841 Wrn Generator
Wrn Event Email 3 Fail 850
Overfrequency 856
Wrn Battery Charger Fail 842
Wrn Event Email 4 Fail 850
Wrn Generator
Wrn Battery Overvoltage 842
Wrn Event SMS 1 Fail 850 Uderfrequency 856
Wrn Battery Undervoltage842
Wrn Event SMS 2 Fail 851 Wrn Charging Alternator
Wrn Brute Force
Wrn Event SMS 3 Fail 851 Fail 857
Protection Active 842
Wrn Event SMS 4 Fail 851 Wrn Load IMP/EXP Fail 857
ALI Bus Ph L1 Inverted 843
ALI External Mains Fail 851 ALI Mains Ph L1 Inverted 857
ALI Bus Ph L2 Inverted 843
Wrn Fence 1 Alarm 851 ALI Mains Ph L2 Inverted 857
ALI Bus Ph L3 Inverted 843
Wrn Fence 2 Alarm 852 ALI Mains Ph L3 Inverted 858
ALI Bus Ph Rotation
Wrn Fuel Theft 852 ALI Mains Ph Rotation
Opposite 843
ALI Gen Ph L1 Inverted 852 Opposite 858
ALI Dead Bus GCB
ALI Gen Ph L2 Inverted 852 Mains Voltage Unbalance
blocked 843
ph-n 858
Wrn Default Password 844 ALI Gen Ph L3 Inverted 853
Mains Voltage Unbalance
Wrn Display Fail 844 ALI Gen Ph Rotation
ph-ph 858
Opposite 853
Wrn ECU Red Lamp 846
Wrn Maintenance Timer 1
Wrn Generator L1
Wrn ECU Wait To Start 846 Interval 859
Overvoltage 853
6 back to Alarms
Description
Description
Note: Gen-set cannot be started until this alarm is inactive and reset.
Sd Current Unbalance 884 BOC Coolant Temp 892 BOC Generator L2L3
Undervoltage 898
Sd Earth Fault Current 884 Stp GCB Fail 892
BOC Generator L3L1
Sd ECU 1 Sd GCB Fail To Close 892
Undervoltage 899
Communication Fail 885 Sd GCB Fail To Open 892
BOC Generator
Sd ECU 2 BOC Gen Voltage
Overfrequency 899
Communication Fail 885 Unbalance Ph-N 892
BOC Generator
Sd ECU 2 BOC Gen Voltage
Underfrequency 899
Communication Fail 885 Unbalance Ph-Ph 893
Sd Charging Alternator
Sd ECU 3 Sd Generator L1
Fail 899
Communication Fail 886 Overvoltage 893
Sd IDMT Earth Fault
Sd ECU 4 Sd Generator L2
Current 900
Communication Fail 886 Overvoltage 894
MP Mains/Bus L1
Sd ECU 5 Sd Generator L3
Overvoltage 900
Communication Fail 886 Overvoltage 894
MP Mains/Bus L1
Sd ECU 6 Sd Generator L1L2
Undervoltage 900
Communication Fail 886 Overvoltage 894
MP Mains/Bus L1L2
Sd ECU 7 Sd Generator L2L3
Overvoltage 900
Communication Fail 887 Overvoltage 895
MP Mains/Bus L1L2
Sd ECU 8 Sd Generator L3L1
Undervoltage 901
Communication Fail 887 Overvoltage 895
MP Mains/Bus L2
Sd EM(A) - a message BOC Generator L1
Overvoltage 901
lost 887 Undervoltage 895
MP Mains/Bus L2
Sd EM(B) - a message BOC Generator L2
Undervoltage 901
lost 888 Undervoltage 896
MP Mains/Bus L2L3
Sd EM(A) - configuration BOC Generator L3
Overvoltage 902
mistake 888 Undervoltage 896
MP Mains/Bus L2L3
Sd EM(B) - configuration BOC Generator L1L2
Undervoltage 902
mistake 888 Undervoltage 896
MP Mains/Bus L3
Sd EM(A) - insufficient 888 BOC Generator L2L3
Overvoltage 902
Sd EM(B) - insufficient 889 Undervoltage 896
MP Mains/Bus L3
Sd EM(A) - missing or BOC Generator L3L1
Overvoltage 902
damaged 889 Undervoltage 897
MP Mains/Bus L3L1
Sd EM(B) - missing or BOC Generator L1
Overvoltage 903
damaged 889 Undervoltage 897
MP Mains/Bus L3L1
Sd Emergency Stop 889 BOC Generator L2
Undervoltage 903
BOC Excitation Loss 890 Undervoltage 897
MP Mains/Bus
BOC Fence 1 Alarm 890 BOC Generator L3 898
Overfrequency 903
Sd EM(A) -
insufficient
Alarm Type SD
Alarmlist EM(A) -
message insufficient
Alarm
All the time
evaluated
Related MINT,
applications SPtM
This alarm
indicates
that
module
Description
does not
support all
required
features.
Sd Emergency Stop
Alarm
SD
Type
Sd
Alarmlist
Emergency
message
Stop
Alarm
evaluate All the time
d
Related
applicati MINT, SPtM
ons
Descripti Alarm is
on
Voltage/PF Control:
Voltage Regulator Character = NEGATIVE
Voltage Regulator Bias = 0,50 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 1,00 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Catterpillar CDVR
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -6,00 V
Voltage Regulator High Limit = 6,00 V
Catterpillar DVR
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 2,00 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 4,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 1,00 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 2,00 V
Catterpillar VR6-B
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
ENGGA WT- 3
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Voltage Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = -0,20 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 1,00 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 2,00 V
AVRi output is connected instead of Remote voltage trimmer 470 Ω to terminal ST4.
Module R726 is not required.
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 1,00 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 2,00 V
AVRi output is connected instead of Remote voltage trimmer 470 Ω to terminal J2. module
R726 is not required.
Voltage/PF Control:
Voltage Regulator
Character = POSITIVE
Voltage Regulator Bias
= -1,00 V
Voltage Regulator Low
Limit = -2,10 V
Voltage Regulator High
Limit = 2,10 V
Module R726 is not required. AVRi trim to minimum counter clockwise +5%.
Voltage/PF Control:
Voltage Regulator Character =
POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00
V
Voltage Regulator High Limit = 2,00
V
Voltage Control:
Remove Link J4 and replace through R500 Voltage Regulator Character = POSITIVE
Primary voltage setting with resistors connected: 230V Voltage Regulator Bias = 0,00 V
progress hint: Voltage Regulator Low Limit = -2,00 V
Disconnect one wire (OUT 1), set voltage on running Generator to U = nom. Voltage Regulator High Limit = 2,00 V
Stop gen-set and connect when equal Voltage and polarity is achieved
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 1,00 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 1,00 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 1,00 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 2,00 V
Use Avri instead pf potentiometer 1000 Ω. Read Leroy Somer R 450 manual before use.
Marathon DVR2000E
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -5,00 V
Voltage Regulator High Limit = 5,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,60 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 4,00 V
MarelliMotori (M40FA610A)
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -3,50 V
Voltage Regulator High Limit = 3,50 V
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -3,50 V
Voltage Regulator High Limit = 3,50 V
Voltage Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0.00 V
Voltage Regulator Low Limit = -10.00 V
Voltage Regulator High Limit = 10.00 V
Remove jumpers connecting input 27 to 28 and input 31 to 32.
Note: For values exceeding the limits of ±10 V the external input is automatically
disabled.
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,50 V
Voltage Regulator High Limit = 2,50 V
Piller
Voltage Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = -0,44 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Voltage/PF Control:
Voltage Regulator Character = NEGATIVE
Voltage Regulator Bias = 1,20 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 6,00 V
Stamford AS480
Voltage/PF Control:
Voltage Regulator Character = NEGATIVE
Voltage Regulator Bias = 1,00 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 2,00 V
Stamfrod MX 341
Voltage Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 1,00 V
Voltage Regulator Low Limit = 0,00 V
Voltage Regulator High Limit = 2,00 V
Disconnect the droop CT ( terminal S1&S2) and short the droop CT leads.
Voltage/PF Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
Stamford SX 460
Voltage Control:
Voltage Regulator Character = POSITIVE
Voltage Regulator Bias = 0,00 V
Voltage Regulator Low Limit = -2,00 V
Voltage Regulator High Limit = 2,00 V
6 back to Appendix
Speed/Load control:
Speed Governor Bias = 5,10 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 0,00
V
Speed Governor High Limit =
10,00 V
Caterpillar ADEM
Speed/Load control:
Speed Governor Bias = 5,10 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 0,00
V
Speed Governor High Limit =
10,00 V
Speed/Load control:
Speed Governor Bias = 5,10 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 0,00
V
Speed Governor High Limit =
10,00 V
Caterpillar PEEC
Speed/Load control:
Speed Governor PWM rate = 500
Hz
Speed/Load control:
Speed Governor Bias = 6,40 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 5,00
V
Speed Governor High Limit = 7,80
V
Spurious operation of the controller push buttons is caused by excessive interference from the speed
controller when capacitor is not connected between power supply terminals 1 and 2.
Cummins ECPG
Speed/Load control:
Speed Governor Bias = 2,50 V
Speed Regulator Character =
POSITIVE
Cummins GCS
Speed/Load ctrl:
Speed Governor Bias = 5,00 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 2,50
V
Speed Governor High Limit =
7,50 V
Speed/Load ctrl:
Speed Governor Bias =
5,00 V
Speed Regulator Character
= POSITIVE
DEUTZ BF6M
Speed/Load ctrl:
Speed Governor Bias = 2,50 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 0,50
V
Speed Governor High Limit = 4,50
V
ECON 4
Speed/Load ctrl:
Speed Governor Bias = 5,10 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 0,0 V
Speed Governor High Limit =
10,00 V
Speed/Load ctrl:
Speed Governor Bias = 5,00 V
Speed Regulator Character =
NEGATIVE
Speed Governor Low Limit = 4,00
V
Speed Governor High Limit = 6,00
V
GAC ESD 5330
Speed/Load ctrl:
Speed Gov Bias = 5,00 V
Speed Regulator Character =
NEGATIVE
Heinzmann E6
Speed/Load ctrl:
Speed Governor Bias = 5,00 V
Speed Regulator Character =
POSITIVE
Speed/Load ctrl:
Speed Governor Bias = 0,00 V
Speed Regulator Character =
POSITIVE
Heinzmann KG-1-03F
Speed/Load ctrl:
Speed Governor Bias = 0,00 V
Speed Regulator Character =
POSITIVE
Speed/Load ctrl:
Speed Governor Bias = 5,00 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 0,80
V
For connection w/o resistor refer
to the next setting
Speed/Load ctrl:
Speed Governor Bias = 2,50 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 0,80V
Speed Governor High Limit = 4,50
V
Speed/Load ctrl:
Speed Governor Bias = 2,50 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 0,50
V
Speed Governor High Limit = 4,50
V
Above mentioned pin numbers refer to the Customer Interface Connector. The J1 connector on ECM
has the following numbering:
20 = J1/3; 24 = J1/17
TOHO
Speed/Load ctrl:
Speed Governor Bias = 4,00 V
Speed Regulator Character =
POSITIVE
Speed/Load ctrl:
Speed Governor Bias = 5,00 V
Speed Regulator Character =
POSITIVE
Speed/Load ctrl:
Speed Governor Bias = 5,00 V
Speed Regulator Character =
POSITIVE
Speed/Load ctrl:
Speed Governor Bias = 5,00 V
Speed Regulator Character =
POSITIVE
Speed/Load ctrl:
Speed Governor Bias = 2,50 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 0,00
V
Speed Governor High Limit = 5,00
V
WOODWARD EPG
Speed/Load ctrl:
Speed Governor Bias = 0,00 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = -3,00
V
Speed Governor High Limit = 3,00
For Woodward EPG speed governor (revision F) are limits: V
Speed Governor Low Limit = -3,00 V
Speed Governor High Limit = +2,00 V
Speed Governor Bias = -0,50 V
Speed/Load ctrl:
Speed Governor Bias = 0,00 V
WOODWARD L - series
Speed/Load ctrl:
Speed Governor Bias = 2,50 V
Speed Regulator Character =
POSITIVE
Speed Governor Low Limit = 0,00
V
Speed Governor High Limit = 5,00
V
6 back to Appendix
8.5 Modules
8.5.1 Plug-in modules
IMPORTANT: 2nd generation of InteliGen 500 G2 controllers does not support new modules and
3rd generation does not support all old modules.
CM3-Ethernet
CM2-4G-GPS
CM-RS232-485
EM-BIO8-EFCP
Communication modules
CM-RS232-485 936
CM3-Ethernet 938
CM2-4G-GPS 940
IMPORTANT: Any manipulation with plug-in module shall be done with disconnected power
supply to controller.
Note: Balancing resistors should both be closed at only one device in the whole RS485 network.
Maximal distance of line is 10 m for RS232 line and 1200 m for RS485 line.
Terminator 120 Ω
Balancing resistor +5 V
Technical data
40 mA / 8 VDC
26 mA / 12 VDC
Power consumption
14 mA / 24 VDC
10 mA / 36 VDC
Isolation Galvanic separation
Firmware upgrade
Download the newest FW of module from ComAp website (in form of PSI file or installation package)
Install package to computer or open PSI to install it into InteliConfig
Plug the module into the controller and power the controller on.
Open a connection with controller via InteliConfig
Go the menu Tools -> Firmware upgrade, select the Plug-in modules tab and select the appropriate
CM3-Ethernet
CM3-Ethernet is a plug-in card with Ethernet 10/100 Mbit interface in RJ45 connector. It provides an interface
for connecting a PC through ethernet/internet network, for sending active e-mails and for integration of the
controller into a building management (MODBUS TCP and SNMP protocols).
IMPORTANT: Any manipulation with plug-in module shall be done with disconnected power
supply to controller.
Use an Ethernet UTP cable with a RJ45 connector for linking the module with your Ethernet network. The
module can also be connected directly to a PC using cross-wired UTP cable.
Technical data
General
Width × Height × Depth 73.8 × 50.3 × 21
Module setup
All settings related to the module are to be adjusted via the controller setpoints. The respective setpoints are
located in the setpoint Group: CM-Ethernet (page 599).
All actual operational values like actual IP address etc. are available in controller values in a specific group as
well.
Status LED
Blinking frequency Color
Green – everything is OK
Red – some of following errors occurred:
1 Hz unplugged Ethernet cable
module cannot connect to AirGate
module can not obtain IP address from DHCP
Green – firmware is currently being programmed
10 Hz
Red – no firmware present in the module
Firmware upgrade
Download the newest FW of module from ComAp website (in form of PSI file or installation package)
Install package to computer or open PSI to install it into InteliConfig
Plug the module into the controller and power the controller on.
Open a connection with controller via InteliConfig
Go the menu Tools -> Firmware upgrade, select the Plug-in modules tab and select the appropriate
firmware you want to program into the module (in InteliConfig).
Press the OK button to start upgrade of firmware.
The firmware update process may be performed via any kind of connection including connection via the same
module in which the firmware is to be updated. The connection is re-established again automatically when the
update process is finished.
IMPORTANT: Any manipulation with plug-in module shall be done with disconnected power
supply to controller.
Note: Cellular data service must be enabled in your SIM card by your mobile operator for successful
operation.
4G module types
If the anthenna is CELLULAR only and has 1 cable (OT1A4GXXMCX), it is connected to the 4G-MAIN
connector.
If the anthenna is CELLULAR only and has 2 cables, cables are connected to the 4G-MAIN or 4G-DIV
connectors (does not matter which cable to which connector).
If the anthenna is a combination of CELLULAR/GPS and has 2 cables (OT1A4GGPSCX), then cable
"4G/LTE" needs to be connected to the 4G-MAIN connector and "GPS" cable to the GPS connector.
If the anthenna is a combination of CELLULAR/GPS and has 3 cables (OT2A4GGPSCX), then cables
"4G/LTE" need to be connected to the 4G-MAIN and 4G-DIV connectors (does not matter which cable to
which connector) and "GPS" cable to the GPS connector.
Technical data
General
Width × Height × Depth 73.8 × 50.3 × 15
Weight ~35 g
Power supply 8-36 V DC
Power consumption 1.7 W
Peak power consumption 10 W
Operating temperature -30 ˚C to +70 ˚C
Storage temperature -40 ˚C to +80 ˚C
GNSS
Antenna interface SMA female, 2.8 V / 20 mA
Antenna type Active
Cellular
2G (GSM/GPRS/EDGE) Quad band,
850/900/1800/1900 MHz
3G (UMTS/HSPA+) Seven band, 800
(BdXIX) / 850 (BdV) / 900 (BdVIII) / AWS
(BdIV) / 1800 (BdIX) / 1900 (BdII) /
Supported networks and frequency bands
2100MHz (BdI)
4G (LTE) Twelve band, 700 (Bd12 <MFBI
Bd17>, Bd28) 800 (Bd18, Bd19, Bd20) 850
(Bd5) / 900 (Bd8) / AWS (Bd4) / 1800 (Bd3)
/ 1900 (Bd2) / 2100 (Bd1) / 2600MHz (Bd7)
Antenna interface 2x SMA female (Main and Diversity)
Contact your mobile operator for getting packet data APN (APN = Access Point Name), username and
password.
Example: APN Name = "internet", UserName = [blank], Password = [blank].
Make sure SIM card does not require PIN code. Use any mobile phone to switch the SIM PIN security off.
Place the SIM card into slot on CM2-4G-GPS card
Connect the antenna to Cellular module antenna connector.
If you want to use the built-in GPS receiver, also connect an active GPS antenna to the GPS antenna
connector.
Switch off the controller.
Insert CM2-4G-GPS module into controller
Power up the controller.
Select the mode of CM2-4G-GPS module by adjusting setpoint Internet Connection (page 577).
Activate CM2-4G-GPS module by switching the setpoint Internet Connection (page 577) to enabled
Enter correct APN Name, APN User Name and APN User Password in controller's setpoint group CM-4G-
GPS which is accessible by PAGE button from any measurement screen on controller. Setpoints can be
set on controller’s front panel keyboard or by InteliConfig.
Enter correct Access Point Name (this information is provided by Mobile Operator). Setpoint can be set
on controller's front panel or by InteliConfig.
Switch the controller off and on.
Wait for approx 2 – 4 minutes for first connection of the system to AirGate. AirGate will automatically
generate the AirGate ID value. Then navigate to measurement screens where you will find signal strength
bar and AirGate ID identifier.
GSM Diag Code – Common list of diagnostic codes for cellular modules
Code Description
0 OK. No error.
1 Not possible to hang up.
2 Modul is switched off
3 Module is switched on
4 Module – error in initialization
5 Module – not possible to set the APN
6 Module – not possible to connect to GPRS network
7 Module – not possible to retrieve IP address
8 Module – not accepted DNS IP address
9 Error in modem detection
AirGate Status
Code Description
Not defined Setpoint AirGate Connection is Disabled
Wait to connect Waiting to connect
Resolving Resolving
Connecting Connecting
Creat sec chan Creating secure channel
Registering Registering
Conn inoperable Connected, inoperable
Conn operable Connected, operable
Susp AGkeyEmpty AirGate is not set in the controller
Firmware upgrade
Download the newest FW of module from ComAp website (in form of PSI file or installation package)
Install package to computer or open PSI to install it into InteliConfig
Plug the module into the controller and power the controller on.
Open a connection with controller via InteliConfig
Go the menu Tools -> Firmware upgrade, select the Plug-in modules tab and select the appropriate
firmware you want to program into the module (in InteliConfig).
Press the OK button to start upgrade of firmware.
The firmware update process may be performed via any kind of connection including connection via the same
module in which the firmware is to be updated. The connection is re-established again automatically when the
update process is finished.
Extension modules
EM-BIO8-EFCP 945
EM-BIO8-EFCP
EM-BIO8-EFCP is optional plug-in card. Through this card, the controller can accommodate one AC current
(CT) measuring input (1A or 5A input) and up to 8 binary inputs or outputs. In InteliConfig PC configuration
tool it is possible to easily choose whether particular I/O will be binary input or output.
IMPORTANT: Any manipulation with plug-in module shall be done with disconnected power
supply to controller.
Power supply
Power supply range 8-36 VDC
40 mA / 8 VDC
27 mA / 12 VDC
Power consumption
22 mA / 24 VDC
19 mA / 36 VDC
Binary inputs
Number Up to 8, non-isolated
Close/Open 0-2 VDC close contact
indication >6 VDC open contact
Binary outputs
Number Up to 8 , non-isolated
Max. current 0,5A
Switching to positive supply terminal
Firmware upgrade
Download the newest FW of module from ComAp website (in form of PSI file or installation package)
Install package to computer or open PSI to install it into InteliConfig
Plug the module into the controller and power the controller on.
Open a connection with controller via InteliConfig
Go the menu Tools -> Firmware upgrade, select the Plug-in modules tab and select the appropriate
firmware you want to program into the module (in InteliConfig).
Press the OK button to start upgrade of firmware.
The firmware update process may be performed via any kind of connection including connection via the same
module in which the firmware is to be updated. The connection is re-established again automatically when the
update process is finished.
IMPORTANT: In slot 3, 4 and 5 CAN modules Inteli IO8/8 and Inteli IO16/0 are supported without
analog outputs. Analog outputs of these CAN modules are supported only in slot 1 and 2.
Extension modules
Inteli AIN8 949
Inteli IO8/8 955
IGS-PTM 962
Inteli AIN8TC 968
Inteli AIO9/1 972
IGL-RA15 977
Inteli AIN8
Inteli AIN8 module is an extension module equipped with analog inputs. Inteli AIN8 module is connected to
controller by CAN1 bus.
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.
IMPORTANT: Impulse input is not supported in controller.
Supported sensors
Sensors
User curves NI100 [°F] (fix) 0-5 V
PT100 [°C] (fix) NI1000 [°F] (fix) 0-10 V
PT1000 [°C] (fix) 4-20 mA passive
NI100 [°C] (fix) 0-2400 Ω 4-20 mA active
CAN address
DIP switch determinates CAN address for analog inputs.
Note: When setting the CAN address to zero, the appropriate group of signals is deactivated.
Programming firmware
Firmware upgrade process:
1. Disconnect all terminals from the unit.
2. Remove the top cover of module
3. Put the TEST jumper on pins
4. Connect the unit with PC via RS232-null modem cable and AT-Link conv
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
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
Protection IP20
Storage temperature -40 °C to +80 °C
Operating temperature -30 °C to +70 °C
Dimensions (WxHxD) 110 × 110 × 46 mm (4.3" × 4.3" × 1.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 Ω
Inteli IO8/8
Inteli IO8/8 module is an extension module equipped with binary inputs, binary outputs and analog outputs.
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
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.
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.
Note: When setting the CAN address to zero, the appropriate group of signals is deactivated.
Programming firmware
Firmware upgrade process:
1. Disconnect all terminals from the unit.
2. Remove the top cover of module
3. Put the TEST jumper on pins
LED indication
Binary input
Each binary input has an 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 an LED which indicates output signal. Binary output LED is shining when binary
output is set. When this LED is shining, then the module is configured as 8 binary inputs and 8 binary outputs.
When this LED is dark, the module is configured as 16 binary inputs.
LED at power connector – status LED
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 example of binary input is connected between
BIN2 and COM (COM is connected internally to the GND (-) – dashed line).
In lower picture is an example of wiring between BIN2 and GND (-). Both ways are correct.
Binary inputs – pull down
There are two options of wiring. In the upper picture you can see an example of binary input connected
between BIN2 and COM (COM is connected internally to the Ucc (+) – dashed line).
In the lower picture is an example of wiring between BIN2 and Ucc (+). Both ways are correct.
When high side setting of outputs is chosen – binary output must be connected to the negative potential
directly Terminal VHS (voltage High side) must 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 positive potential of
power supply directly. Negative potential is connected internally – dashed line.
Analog outputs
IMPORTANT: Terminator for analog output has special analog ground (AGND), which must not be
connected to the GND.
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
Protection IP20
Storage temperature -40 °C to +80 °C
Analog outputs
Number of channels 2
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
IGS-PTM
IGS-PTM module is extension module equipped with binary inputs, binary outputs, analog inputs and analog
output. IGS-PTM module is connected to controller by CAN1 bus.
Analog inputs
Analog inputs can be configured for:
Resistance measurement
Current measurement
Voltage measurement
The type of analog input is configured via jumpers RUI located on lower PCB.
Supported sensors
Sensors
PT100 [°C] (fix) User curves
NI100 [°C] (fix) 0-100 mV
PT100 [°F] (fix) 0-2400 Ω
NI100 [°F] (fix) ±20 mA
Address configuration
If InteliGen 500 G2 controller type is selected (by IGS jumper), address of IGS-PTM could be modified via
jumpers labeled ADR1 and ADR2.
BOUT
ADR1 ADR2 ADR offset BIN module AIN 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
Programming firmware
Firmware upgrade is available 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 FlashProg PC
tool should be used.
LED indication
Binary input
Each binary input has an 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 an LED which indicates output signal. Binary output LED is shining when binary
output is set.
LED at power connector – status LED
LED status Description
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.
Binary outputs
Resistance sensor
Voltage sensor
Analog outputs
Technical data
General data
Power supply 8 to 36 V DC
Current consumption 100 mA at 24V ÷ 500 mA
Interface to controller CAN1
Protection IP20
Storage temperature -40 °C to +80 °C
Operating temperature -30 °C to +70 °C
Dimensions (WxHxD) 95 × 96 × 43 mm (3.7" × 3.8" × 1.7")
Analog inputs
Number of channels 8
Range 0-100 mV
Voltage
Accuracy: 1.5 % ±1 mV out of measured value
Range: 0-20 mA
Current
Accuracy: 2.5 % ±0.5 Ω out of measured value
Range: 0-250 Ω
Resistive
Accuracy: 1 % ±2 Ω out of measured value
Binary inputs
Number of channels 8
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
Number of channels 8
Max current 500 mA
Max switching voltage 36 V DC
Number of channels 8
Range 0-100 mV
Voltage
Accuracy: 1.5 % ±.1 mV out of measured value
Range: 0-20 mA
Current
Accuracy: 2.5 % ± 0.5 Ω out of measured value
Range: 0-250 Ω
Resistive
Accuracy: 1 % ±2 Ω out of measured value
Inteli AIN8TC
Inteli AIN8TC module is an extension module equipped with 8 analog inputs dedicated for thermocouple
sensors only.
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.
Analog inputs
8 channels
can be configured as thermocouple sensors only
Supported sensors
Sensors
Thermocpl J [°C] (fix)
Thermocpl K [°C] (fix)
Thermocpl L [°C] (fix)
Thermocpl J [°F] (fix)
Thermocpl K [°F] (fix)
Thermocpl L [°F] (fix)
Thermocpl (nc) J [°C] (fix)
Note: "nc" means not cold junction compensation (by external sensor). In this case is used internal
temperature sensor on the PCB
LED indication
Wiring
Analog inputs
Terminator
Power supply 8 to 36 V DC
Protection IP20
Current consumption 35 mA at 24 V ÷ 100 mA at 8 V
Storage temperature - 40 °C to + 80 °C
Operating temperature - 30 °C to + 70 °C
Heat radiation 2W
Thermocouples which are galvanically separated and galvanically non-separated are supported.
Inteli AIO9/1
Inteli AIO9/1 module is an extension module equipped with analog inputs and outputs – designed for DC
measurement.
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.
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Ω
Supported sensors
Sensors
User curves
PT1000 [°C] (fix)
NI1000 [°C] (fix)
PT1000 [°F] (fix)
NI1000 [°F] (fix)
0-2400 Ω (fix linear)
±65 V DC (fix linear)
±75 mV (fix linear)
Thermocpl J [°C] (fix)
Thermocpl K [°C] (fix)
Thermocpl L [°C] (fix)
Thermocpl (nc) J [°C] (fix)
Thermocpl (nc) K [°C] (fix)
Thermocpl (nc) L [°C] (fix)
Thermocpl (nc) J [°F] (fix)
Thermocpl (nc) K [°F] (fix)
Thermocpl (nc) L [°F] (fix)
LED indication
Wiring
The following diagrams show the correct connection of sensors.
Technical data
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
Power supply 8 to 36 V DC
Protection IP20
Current consumption 150 mA at 24 V ÷ 400 mA at 8 V
Storage temperature - 40 °C to + 80 °C
Operating temperature - 30 °C to + 80 °C
IGL-RA15
Remote annunciator (IGL-RA15) is designed as an extension signalling unit.
The unit is equipped with a fully configurable tricolor (red, orange, green) LED for intuitive operation
together with high functionality.
Terminals
Horn Horn
CAN CAN1 line
Power Power supply
CAN address
SW changing of CAN1 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 via the following steps:
Switch to programming mode (Hold the Horn reset and Lamp test when unit is powering on). Status led is
yellow
LED indication
Each LED color is adjusted independently of controller output settings. If controller output 1 is set as
"Common Shutdown" it does not mean red LED1 color for iGL-RA15. The LEDs color can be adjusted by
following steps:
Switch to programming mode (Hold the Horn reset and Lamp test when unit is powering on). Status led is
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 Lamp test three 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.
Status LED
The signals LEDs are handled like binary outputs. This means everything that can be configured to binary
outputs can be also configured to the LEDs of IGL-RA15.
LED status Description
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
LED status Description
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 be set via the 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 fifteen 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.
Wiring
* terminator resistor only when iGL-RA 15 is the last unit on the CAN1 bus.
Note: The shielding of the CAN bus cable must be grounded at one point only!
Note: See the section Technical data (page 277) for recommended CAN bus cable type.
General data
Power supply 8 to 36 V DC
0.35-0.1A (+1Amax horn output) depends on supply
Current consumption
voltage
Protection IP65
Humidity 85%
Storage temperature -30 °C to +80 °C
Operating temperature -20 °C to +70 °C
Dimensions (WxHxD) 180 × 120 × 55 mm
Weight 950 g
Horn output
Maximum current 1.0 A
Maximum switching voltage 36 V DC
6 back to Appendix