Table of Contents ............................................................................................................................................... 2
Document information ........................................................................................................................................ 4
Available related documentation ........................................................................................................................ 5
General guidelines .............................................................................................................................................. 6
What is described in this manual? ................................................................................................................. 6
Dangerous voltage ......................................................................................................................................... 7
Adjust set points ............................................................................................................................................. 7
Clarification of notation ................................................................................................................................... 8
Available Firmware and Archive sets ................................................................................................................. 9
General description .......................................................................................................................................... 10
Basic description of MINT application .......................................................................................................... 10
Active and Reactive Power control modes in MINT ..................................................................................... 12
Power management ..................................................................................................................................... 12
Force value – step by step guide ................................................................................................................. 34
Values for continuous writing from external sources ................................................................................... 36
General Purpose Timers .............................................................................................................................. 36
History Related functions ............................................................................................................................. 37
User Buttons................................................................................................................................................. 39
Remote Control Function ............................................................................................................................. 39
Shared Inputs and Outputs .......................................................................................................................... 40
Distributed Binary Inputs and Outputs ......................................................................................................... 42
Modbus Reading and Writing ....................................................................................................................... 43
User MODBUS ............................................................................................................................................. 44
Analog Input Sensors and User Sensors ..................................................................................................... 44
Languages and Translator tool in GenConfig .............................................................................................. 45
Power Formats ............................................................................................................................................. 45
System Start/Stop ........................................................................................................................................ 46
User Mask function ...................................................................................................................................... 47
Multi language support ................................................................................................................................. 47
Protections and Alarm management ................................................................................................................ 49
Configuration of User configurable protections in GenConfig ...................................................................... 55
Gen-set operation states .................................................................................................................................. 58
Inputs and Outputs ........................................................................................................................................... 60
Virtual and physical modules ....................................................................................................................... 60
List of possible events ...................................................................................................................................... 62
Controller configuration and monitoring ........................................................................................................... 63
Direct connection to the PC ......................................................................................................................... 63
Value and setpoint codes ............................................................................................................................. 64
Technical data .............................................................................................................................................. 64
Language support ........................................................................................................................................ 64
Setpoint groups ................................................................................................................................................ 67
Setpoints - Force value ................................................................................................................................ 70
Setpoints - Power Management ................................................................................................................... 71
Setpoints - Process Control ......................................................................................................................... 72
Setpoints - Volt/PF Control ........................................................................................................................... 73
Value groups .................................................................................................................................................... 74
Values group - Analog CU ........................................................................................................................... 74
Values group - Bin inputs CU ....................................................................................................................... 74
Values group - Bin outputs CU ..................................................................................................................... 74
Values group - Engine values ...................................................................................................................... 74
Values group - Force value .......................................................................................................................... 74
Values group - Gener values ....................................................................................................................... 75
Values group - Info ....................................................................................................................................... 75
Values group - Log Bout .............................................................................................................................. 76
Values group - Load shedding ..................................................................................................................... 76
Values group - Bus values ........................................................................................................................... 76
Values group - Power management ............................................................................................................ 76
Values group - Statistics .............................................................................................................................. 76
Values group - Sync/Load ctrl ...................................................................................................................... 77
Values group - Volt/PF ctrl ........................................................................................................................... 77
Analog input functions ...................................................................................................................................... 80
Common functions ....................................................................................................................................... 81
Breaker control ............................................................................................................................................. 81
Control loops ................................................................................................................................................ 81
Power management ..................................................................................................................................... 81
Status information ........................................................................................................................................ 82
Table of setpoints ......................................................................................................................................... 84
Table of values ........................................................................................................................................... 196
Table of binary input functions ................................................................................................................... 230
Table of analog input functions .................................................................................................................. 275
Table of binary output functions ................................................................................................................. 284
Pressing F1 in the GenConfig and InteliMonitor setpoint, values or configuration window will
open the help with the context of currently selected setpoint, value and binary input or output
function.
General description of SPtM applications for
InteliGen-NT and InetliSys-NT. Contains
description of engine and generator control, control
of power in parallel to mains operation, list of all
Setpoints, Values, Logical Binary Inputs and
Logical Binary Output.
IGS-NT-SPI-3.0 Reference Guide.pdf
General description of SPI applications for
InteliGen-NT and InetliSys-NT. Contains
description of engine and generator control, control
of power in parallel to mains operation, list of all
Setpoints, Values, Logical Binary Inputs and
Logical Binary Output.
IGS-NT-MINT-3.0 Reference Guide.pdf
General description of MINT applications for
InteliGen NT and InetliSys NT. Contains
description of engine and generator control,
powermanagement, list of all Setpoints, Values,
Logical Binary Inputs and Logical Binary Output.
IGS-NT-Combi-3.0 Reference Guide.pdf
General description of Combi applications for
InteliGen-NT and InetliSys-NT. Contains
description of engine, and generator control in
SPTM, SPI and MINT mode, powermanagement,
list of all Setpoints, Values, Logical Binary Inputs
and Logical Binary Output.
IGS-NT-COX-3.0 Reference Guide.pdf
General description of COX applications for
InteliGen NT and InetliSys NT. Contains
description of engine and generator control,
powermanagement, list of all Setpoints, Values,
Logical Binary Inputs and Logical Binary Output.
IGS-NT Application Guide 05-2013.pdf
Applications of InteliGen NT, InetliSys NT and
InteliMains NT, examples of connection,
description of PLC functions, Virtual and Shared
peripheries.
IGS-NT Operator Guide 05-2013.pdf
Operator Guide for all hardware variation of
InteliGen NT and InetliSys NT, InteliVision 5 and
InteliVision 8.
IGS-NT Installation Guide 05-2013.pdf
Thorough description of installation and technical
information about InteliGen NT, InetliSys NT and
InteliMains NT and related accessories.
IGS-NT Communication Guide 05-2013.pdf
Thorough description of connectivity and
communication for InteliGen NT, InetliSys NT and
InteliMains NT and related accessories.
IGS-NT Troubleshooting Guide 05-2013.pdf
How to solve most common troubles with
InteliGen NT and InetliSys NT controllers. Including
the list of alarm massages.
IGS-NT & ID-DCU Accessory Modules 05-2013.pdf
Thorough description of accessory modules for
IGS-NT family, technical data, information about
installation of the modules, how to connect them to
controller and set them properly.
Following described machine complies with the appropriate basic safety and health
requirement of the EC Low Voltage Directive No: 73/23 / EEC and EC
Electromagnetic Compatibility Directive 89/336 / EEC based on its design and type,
as brought into circulation by us.
What is described in this manual?
This manual describes „MINT“ software configuration. The software configuration is designed for multiple
sets applications with internal load sharer and synchronizer.
What is the purpose of this manual?
This manual provides general information on how to configure and operate the controller.
This manual is intended for use by:
Operators of gen-sets
Gen-set control panel builders
For everybody who is concerned with installation, operation and maintenance of the gen-set
!! Warnings !!
The NT controller can be remotely controlled. In the event that maintenance needs to be done to the gen-set,
check the following to ensure that the engine cannot be started.
To be sure:
Disconnect remote control via RS232 line
Disconnect input REMOTE START/STOP
or
Disconnect output STARTER and outputs GCB CLOSE/OPEN and MCB CLOSE/OPEN
The controller contains a large number of configurable setpoints, because of this it is impossible to describe
all of its functions. These are subject to change from SW version to SW version. This manual only describes
the product and is not guaranteed to be set for your application on arrival.
Text
ESC (Capital letters in the frame) buttons on the front panel
Break Return (Italic) set points
Generator protections (Bold) Set point group
Cyan background Valid for IS-NT only
Conformity declaration
Note:
ComAp believes that all information provided herein is correct and reliable and reserves the right to update
at any time. ComAp does not assume any responsibility for its use unless otherwise expressly undertaken.
Be aware that the binary outputs can change state during and after software
reprogramming (before the controller is used again ensure that the proper
configuration and setpoint settings are set in the controller).
Every time you want to disconnect following NT controller terminals:
Mains voltage measuring and / or
Binary output for MCB control and / or
MCB feedback
Be aware that the MCB can be switched off and gen-set can start !!!
Switch the controller to MAN mode and disconnect the Binary outputs Starter and Fuel
to avoid unexpected automatic start of gen-set and GCB closing.
!!! CAUTION !!!
Dangerous voltage
The terminals for voltage and current measurement should never be touched.
Properly connect the grounding terminals.
Do not disconnect the CT terminals for any reason.
Adjust set points
All setpoints are preadjusted to their typical values. But the set points in the “Basic settings” settings
group !!must!! be adjusted before the first startup of the gen-set.
!!! WRONG ADJUSTMENT OF BASIC PARAMETERS
CAN DESTROY THE GEN-SET !!!
The following instructions are for qualified personnel only. To avoid personal injury do
not perform any action not specified in this User guide !!!
This type of paragraph points out details to help user installation/configuration.
NOTE:
This type of paragraph calls readers’ attention to a notice or related theme.
CAUTION!
This type of paragraph highlights a procedure, adjustment, etc. which may cause damage or improper
functioning of the equipment if not carried out correctly and may not be clear at first sight.
WARNING!
This type of paragraph indicates things, procedures, adjustments, etc. which demand a high level of
attention, otherwise personal injury or death may occur.
EXAMPLE:
This type of paragraph indicates examples of usage for illustrational purposes.
The MINT application is intended for sites where up to 32 gen-sets cooperate with each one. It includes
following main features:
Automatic startup and stop sequences with adjustable timing
Wide range of generator and engine protections, additional freely configurable protections
Multiple island operation with digital active and reactive load sharingParallel to the mains operationOne breaker control (GCB) including synchronizing to the busbar.
Soft loading and unloading
Power management - automatic starting and stopping of gen-sets according to the load demand,
running hours equalization and other optimalization features
Outputs STARTER, GCB CLOSE/OPEN and FUEL SOLENOID are not energized.
Gen-set cannot be started. If START,STOP,GCB ON/OFF buttons are pressed the controller will not
respond.
When the gen-set is running it is not possible to switch directly to OFF mode. First you have to stop the
engine.
MAN mode
1) START - starts the gen-set.
2) GCB ON/OFF
If generator voltage is out of the limits (adjusted in the set point group Gener protect) controller does
not respond to the GCB ON/OFF
a) controller closes GCB to dead bus.
b) controller starts GCB synchronizing when bus voltage is OK and MCB is closed or when other
gen-set(s) provide healthy voltage to the bus. Closes the GCB when synchronized and stays
running in parallel (island or mains parallel).
c) Unloads gen-set and opens the GCB if gen-set was running in parallel to the mains or to other
gen-set(s).
3) STOP
a) When gen-set is running in parallel: transfers the load to the mains or to other gen-set(s), opens
GCB, goes into cooling state and stops the engine.
b) When gen-set is running in single island (or in general there is no mains and no other gen-set(s)
to transfer the load to): opens GCB, goes into cooling state and stops the engine.
c) When engine is running unloaded: activates cooling sequence and then stops the engine.
d) During cooling state causes immediate engine stop.
HINT
The gen-set is permitted to run unloaded for unlimited time.
Controller does not automatically start the gen-set when SYS START/STOP input is closed.
Load control type in mains parallel depends on ProcessControl: #SysLdCtrlPtM = BASELOAD or
LDSHARING setpoint.
SEM
In SEM mode, pressing of START or STOP buttons performs a predefined sequence:
1) START – starts the engine, synchronizes and runs in parallel.
2) STOP – softly unloads the gen-set, opens GCB, provides cooldown and stops the engine.
AUT mode
1) All gen-sets necessary to cover selected LoadRes strt are started when binary input SYS START/STOP
is closed and Pwr management is ENABLED. Power management can be based on kW, kVA or on
relative % reserve.
a) 1 sec delayed when MCB FEEDBACK binary input is closed (mains parallel)
b) delayed #SysAMFstrt del when MCB FEEDBACK binary input is opened – start to island parallel
(multi AMF) situation
2) The first gen-set closes the GCB to the dead bus, the rest are synchronized to the bus.
3) When all necessary gen-sets are connected to the bus and LoadRes strt is achieved, SYST RES OK
output is closed. Output could be used to close the MGCB (Master GCB).
4) Total load and power factor are shared between parallel operating gen-sets.
5) Close input LOAD RESERVE 2 (or 3 or 4) and use setpoint LoadRes strt2(or 3 or 4) to switch to another
load reserve setting. E.g. high load reserve during system start to be able to switch-on big devices, then
during normal operation lower reserve to save engines (and fuel).
6) If total load increases and selected LoadRes strt is no more fulfilled, after a Next start del next ready
gen-set with the highest priority (lowest priority number) is started and synchronized to the bus.
7) If load decreases and selected LoadRes stp is exceeded, after a Next stop del the running gen-set with
the lowest priority is unloaded, got off line, cooled and stopped.
8) Complete gen-sets group stops when binary input SYS START/STOP opens. If the input MCB
FEEDBACK is closed (gen-sets are in parallel to mains) controllers softly transfer the load to the mains.
When gen-set is unloaded (see GCB open level or GCB open del) opens the output GCB
CLOSE/OPEN.
9) The Running hours balancing or Load demand engines swap can be activated in power management.
HINT
Controller does not respond to GCB ON/OFF , STOP, START buttons and corresponding remote
InteliMonitor or Modbus commands in AUT mode.
Set Basic setting: FltRes GoToMAN = ENABLED to avoid automatic engine start when pressing FAULT
RESET after any 2nd level alarm (Shutdown, Slow stop, Breaker Open&Cooldown).
Active and Reactive Power control modes in MINT
System Base load
Gen-set group is controlled on constant (or adjustable) power. The Baseload value can by changed by
setpoint or via analog input.
Important setpoints: ProcessControl: #SysLdCtrlPtM = BASELOAD; #SysBaseload; SysBaseLdMode.
Local Baseload
Selected gen-set from island or mains parallel running group can be loaded to constant LocalBaseload
value. This engine is taken out from Load sharing and Power management. LocalBaseload value is reduced
only when common group (actual) load is lower than this value. The gen-sets in the group will try to match
their LocalBaseloads (when more than one) based on their controller addresses, so the first limited would be
the one with the highest CAN address. I.e. this function will switch-off automatically in one or more
controllers if there is not enough load to cover all the requested LocalBaseloads.
Important setpoints: ProcessControl: LocalBaseload.
System Base power factor
Gen-set group is controlled in mains parallel to keep a constant (or adjustable) power factor.
Important setpoints: ProcessControl: #SysPFCtrlPtM = BASEPF; #SysPwrFactor.
Import-Export
Gen-set group is controlled to keep constant (or adjustable) Import or Export value. The external controller
InteliMains NT must be connected on the CAN2 to control gen-set group kW I/E.
Important setpoints: ProcessControl: #SysLdCtrlPtM = LDSHARING.
Import/Export power factor
Gen-set group is controlled to keep constant (or adjustable) Import or Export power factor.
Important setpoints: ProcessControl: #SysLdCtrlPtM = VSHARING. The external InteliMains NT controller
must be connected on the CAN2 to control gen-set group PF I/E.
Power management
Automatic gen-set start / stop function based on load changes and/or Running hours or Engine size.
Following functions are available:
Power management in kW
Guarantees adjustable load reserve (load step) in kW. Suitable for load demand-based optimization.
Activation:Pwr management:#Pwr mgmt mode = ABS (kW)
Guarantees that the engines are not continuously loaded more than to a certain level. Suitable for engine
life-based optimization.
Activation:Pwr management:#Pwr mgmt mode = REL (%)
Second lowest considered running hours –
Current lowest considered running hours +
#RunHrsMaxDiff
450 – 250 + 10 = 210 hours
ΣPg*
Nom
Sum of Nominal power of all gen-sets on the bus apart of the one, which is going to be
stopped.
ΣPg
Act
Sum of Actual power of all gen-sets on the bus = system load.
NOTE:
G1G2G3
Basic settings:
Contr. Addr = 2
Pwr management:
#PriorAutoSwap = RUN HOURS EQU
Priority ctrl = SLAVE
RunHoursBase = 200h
#RunHrsMaxDiff = 10h
Control group = COMMON
Basic settings:
Contr. Addr = 1
Pwr management:
#PriorAutoSwap = RUN HOURS EQU
Priority ctrl = SLAVE
RunHoursBase = 100h
#RunHrsMaxDiff = 10h
Control group = COMMON
Basic settings:
Contr. Addr = 3
Pwr management:
#PriorAutoSwap = RUN HOURS EQU
Priority ctrl = SLAVE
RunHoursBase = 300h
#RunHrsMaxDiff = 10h
Control group = COMMON
Basic settings:
Contr. Addr = 4
Pwr management:
#PriorAutoSwap = RUN HOURS EQU
Priority ctrl = MASTER
#RunHrsMaxDiff = 10h
Control group = COMMON
InteliMains
CAN
System starting sequences may be very different due to their complexity (i.e. gensets which do not take part
in power management, various nominal powers etc.). Each system should be considered individually.
Optional functions in absolute or relative Power management are:
- Running hours balancing (equalization) – in absolute or relative pwr mgmnt
- Load demand (different size) engines swap – in absolute pwr mgmnt only
- Power management of two or more gen-set groups (bus tie support) – in absolute or relative
pwr mgmnt
Running hours equalization (RHE)
The gen-sets priorities are automatically swapped to balance engine running hours. Up to 32 controllers are
supported.
Activation: Pwr management:#PriorAutoSwap = RUN HOURS EQU
Important setpoints: RunHoursBase, #RunHrsMaxDiff, Priority ctrl, Control group
Figure: Running Hours Equalization example
EXAMPLE:
In this example the system is shown in previous figure. InteliMains assumes the role of master in priority
swapping and swappes priority of the engines based on their running hours.
Gen-set 1 running hours = 250 -> running hours considered in RHE = 150 (250-RunHoursBase)
Gen-set 2 running hours = 450 -> running hours considered in RHE = 250 (450-RunHoursBase)
Gen-set 3 running hours = 750 -> running hours considered in RHE = 450 (750-RunHoursBase)
All the engines have the same nominal power which is 700 kW. Originally priority of gen-sets was G1 = 3, G2
= 2, G3 = 1. Load demand in this example is constant and it is 500 kW (so only one engine is running at any
time).
InteliMains will change priority of gen-set 1 to 1 because it has the lowest considered running hours and genset 1 will run for 210 hours.
After 210 hours, situation will change. Gen-set 2 will
now have the lowest considered running hours
(Gen-set 1 = 460, Gen-set 2 = 450, Gen-set 3 =
750). Gen-set 2 will now have priority 1 and it will run
for 20 hours. Then Gen-set 1 will run again for 20
hours. This will continue until both engines will have
running hours 770. Then the third engine will run. At that point engines will be swapping with period of 20
hours (2 x Pwr management:#RunHrsMaxDiff).
#PriorAutoSwap = LD DEMAND SWAP
Priority ctrl = SLAVE
#PwrBandContr1 = 1
#PwrBandContr2 = 2
#PwrBandContr3 = 2+3
#PwrBandChngDlUp = 10s
#PwrBandChngDlDn = 10s
Control group = COMMON
Basic settings:
Contr. Addr = 1
Pwr management:
#PriorAutoSwap = LD DEMAND SWAP
Priority ctrl = SLAVE
#PwrBandContr1 = 1
#PwrBandContr2 = 2
#PwrBandContr3 = 2+3
#PwrBandChngDlUp = 10s
#PwrBandChngDlDn = 10s
Control group = COMMON
Basic settings:
Contr. Addr = 3
Pwr management:
#PriorAutoSwap = LD DEMAND SWAP
Priority ctrl = SLAVE
#PwrBandContr1 = 1
#PwrBandContr2 = 2
#PwrBandContr3 = 2+3
#PwrBandChngDlUp = 10s
#PwrBandChngDlDn = 10s
Control group = COMMON
Basic settings:
Contr. Addr = 4
Pwr management:
#PriorAutoSwap = LD DEMAND SWAP
Priority ctrl = MASTER
#PwrBandContr1 = 1
#PwrBandContr2 = 2
#PwrBandContr3 = 2+3
#PwrBandChngDlUp = 10s
#PwrBandChngDlDn = 10s
Control group = COMMON
InteliMains
CAN
NOTE:
Core power management is still fully functional.
Priority setpoints are not actually changed. Virtual values are used. If changing of priority setpoints is
required, they need to be changed and RHE needs to disabled and enabled again for the changes to take
place
Different sized engines (Load demand) swap (LDS)
Up to three running engines (priorities) can be swapped based on load demand (e.g. one “small” engine may
run on “small” load and swaps to another one, “big” engine that runs when load increases). This function is
availatible only in combination with absolute power management.
#PwrBandChngDlUp, #PwrBandChngDlDn, Load reserve setpoints (depending on selected load reserve
set), Priority ctrl, Control group.
EXAMPLE:
In this example the system is shown in previous figure. InteliMains assumes the role of master in priority
swapping and swappes priority of the engines based on user defined power bands. In power band 1, gen-set
with CAN address 1 will be running, in power band 2, gen-set with CAN address 2 will be running and in
power band 3, gen-sets with address 2 and 3 will be running.
Power bands are changed up if:
or down if:
Power management using control groups
When a Bus-tie separates the gen-set groups, they can operate separately (power management, load
control, mode of function etc.). When GROUPLINK is active, all the gen-sets in according groups are controlled
by InteliMains with lower CAN address only.
Important setpoints: Control group, GroupLinkLeft, GroupLinkRight
Figure: Power management using control groups
EXAMPLE:
In the example above, bus tie breaker separates gen-sets into two groups. BTB is operated manually in this
example. If BTB is opened, each control group is working independently. If the BTB closes, controller
number 3 sends signal via CAN bus and groups COMMON and 2 are connected together. One InteliMains
(the one with lower CAN address) takes over and controls both groups. It is not possible to use both
InteliMains parallel to the Mains when BTB is closed and InteliMains with lower CAN address takes over the
control. In this case gen-sets are controlled only by this InteliMains and the second InteliMains does not have
any means to control its parallel function.
Load shedding
All LOAD SHED outputs are activated (closed) to trip the unessential load when gen-set goes to island:
a) When GCB is closed after mains fail and gen-set starts in SEM / AUT mode.
b) When MCB opens from parallel to mains operation in SEM / AUT mode.
c) Before MCB is opened in MAN mode by button.
The load shedding function is active in all controller modes except OFF.
Load shedding has three steps and each step is linked with its own Load shed x binary output. There is only
one load shed level and delay for all three steps as well as recon level and delay. Load shed can only move
from one step to the next, e.g. No LoadShed to LdShed S1 to LdShed S2 to LdShed S3 and vice versa.
If manual reconnection of the load is desired, the AutoLd recon setpoint needs to be disabled (AutoLd recon = DISABLED) and the MAN load recon binary input needs to be configured.
Rising edge on this input resets the controller to a lower stage, but only if the load is under the Ld recon level
at that moment.
HINT
If no Load Shedding outputs are configured, there is no record to history and no scrren timer indication of the
activity of this function.
Engine params: Starting RPM
Prestart time
MaxCrank time
CrnkFail pause
Crank attempts
Idle time
Fuel solenoid
Starting
Stop solenoid
Starter
Prestart
Cranking
Crank procedure
Idle/Nominal
Idle run
Ignition
Operational
HINT
To use Prelubrication, configure Binary output PRELUBR PUMP first.
Prelubrication is disabled in controller OFF mode or if Prelubr time is set to zero.
Binary output PRELUBR PUMP is opened when engine is running.
Prelubrication cycle starts with PrelubrPause after engine stop.
Prelubrication cycle starts immediately when controller power supply is switched on or when mode changes
from OFF to MAN or AUT or after Emergency stop was reset. An Alarmlist message “Not lubricated” is active
until this first lubrication cycle has been completed.
Engine cooling
Engine warming
Service time alarm
Engine starting procedures
Engine starting procedure if Engine params: Fuel solenoid = DIESEL ENGINE with different setting of
FuelSol offset.
Negative values possible only
with DIESEL setting.
BO: Fuel solenoid
BO: Fuel solenoid
0 s offset means that Fuel
solenoid is activated together
with Starter.
FuelSol offset
+5s
RPM > Starting RPM or
Oil pressure > Starting POil or
RunIndication1,2,3 = 1
BO: Fuel solenoid
BO: Fuel solenoid
RPM > 30
BO: Starter
0 s FuelSol offset
activates
the Fuel solenoid
immediately if RPM > 30.
FuelSol ofset countdown is
started if RPM > 30.
Max up to 5s
Fuel solenoid activation
FuelSol offset
+5s
= 231 V
Idle run
BI: Sys Start /stop
BO: Starter
BO: Fuel solenoid
RPM
GenNomV
< Starting RPM
= 1000 V
Cranking
GenNomV is forced during
BO: Starter is deactivated
Starting RPM > 1000
cranking untill
Engine starting procedure if Engine params: Fuel solenoid = GAS ENGINE
Engine starting procedure with own starting procedure:
Engine is started after Starting RPM reach starting leve or other condition. BO: Starter is deactivated only if
one of those condition is fulfilled.
Generator nominal voltage is 231V but during Cranking is forced to 1000V until engine in Idle state (at least
one of condition has to be fulfilled).
Unsuccessful start – no Engine params: Starting RPM reached
- D+ terminal active and Engine params: D+ function = ENABLED or
- Active Binary input RunIndication1 or
26
- Active Binary input RunIndication2 or
- Active Binary input RunIndication3 or
- Vgen > 15 V (any phase).
“Still engine” conditions
- Engine speed (RPM) = 0 and
- AI: Oil press < Starting POil and
- D+ terminal not active and
- BI: RunIndication 1 and 2 and 3 = not active and
- Generator voltage < 15V (all phases) and
- Generator frequency = 0 Hz and
- if all above conditions are fulfilled, additional 2s delay is necessary to confirm “still engine”
NOTE:
If any of the functions not used (e.g. BI RunIndication3 not configured), it’s state is omitted in the evaluation.
This is not valid for RPM comparisons, this condition is always active.
In the following text, “CB” abbreviation is used for MCB or GCB respectively.
Related binary inputs:
- CB fdb – CB feedback binary input
- CB fdb neg – negative CB feedback binary input. Used for increasing the reliability of CB status
evaluated by the controller. In case that it is not configured, negative value of CB fdb is calculated
internally within the controller.
Related binary outputs:
- CB close/open – output for circuit breaker. Equals to 1 during the time when CB is requested o be
closed.
- CB ON coil – output for closing coil of the CB. 2s pulse (5s if synchronising is not provided by the
particuilar CB) is used for closing the CB.
- CB OFF coil – output for opening coil of the CB. 2s pulse (5s if synchronising is not provided by the
particuilar CB) is used for opening the CB.
- CB UV coil – output for undervoltage coil of the CB. Permanently active, 2s negative pulse (5s if
synchronising is not provided by the particuilar CB) is used for CB opening request
- CB status – output indicating CB status as evaluated by the controller. This signal is used for lighting
LEDs on the panel, switching the regulations, CB fail evaluation, etc.
If the CB is not closed after
the first attempt, it is only reset
by OFF pulse and no CB fail is
issued. This would be issued
after the second unsuccessfull
attempt.
BO: CB status = 0
BI: CB fdb neg = 1
BI: CB fdb = 0
BO: CB fail
ON pulse has finished and CB
status is not =1. CB fail is
issued immediatelly
CB fail – If any inconsistence between
the two feedback signals is detected, CB
fail is issued.
ON pulse is shortened/interrupted
and replaced by UV and OFF pulse
OFF pulse is activated until both
feedbacks return to the correct
position +2 seconds.
2s
BO: CB OFF coil
BI: CB fdb neg
BI: CB fdb
BO: CB close/open
BO: CB UV coil
During CB opening the CB status
LBO is deactivated with change of
the first feddback status
Further behavior of UV output
depends on the system status. In
case of transition to cooling stays
off, if the Cb was opened manually
and the engine keeps running, it
activates again after timeout
elapses.
FwRet break dealy is between MCB
status deactivation and command for
GCB closing.
BO: MCB close/open
Generator voltage is within limits
BO: GCB close/open
BO: GCB ON coil
If mains returns in this moment,
starting sequence is interrupted
and MCB stays closed. It is valid
until the moment when generator
voltage is within limits.
MCB opens on = GENRUN:
Other CB fail reasons:
When the BO CB close/open is in steady state and CB feedback is changed, the CB fail is detected
immediately (no delay).
When the BO CB close/open opens, there is 5 resp. 2 sec delay for the breaker to respond before a CB
fail is detected. In such case, if CB OFF coil is used for opening the CB and CB fail occurs during
Not valid for MCB:
MCB fail is not detected in this case.
If BI Ext MF relay is active, controller switches to Island
operation. If BI Ext MF relay is not active and Mains is
OK, controller synchronizes back to the mains and tries
to close MCB.
32
Alarm: GCB fail
BO GCB close/open
BI GCB feedback
active
opened
opened
Time delay
5 sec
opening the CB, the signal CB OFF coil is automatically extended until the breaker opening is detected
(evaluated as CB status).
2 sec when the CB is used for synchronizing
5 sec in other cases
In case that CB fail is detected after switching the controller on (CB is closed), the CB OFF coil output is
activated immediatelly.
Remote Alarm Messaging
It is possible to use up to five channels for Active Call, Email and SMS upon defined type of Alarm. It is
possible to define protection type for all ENABLED channels to react. All the possibilities in the controller are:
History record, Alarm only, Warning, Mains protect and Mains protect with Reset. Find more information
about alarm types in the chapter Protections and alarm management.
Communication Types for Remote Alarm Messaging
Below there all types of communication available for each Active Call channel.
DATA-ANA: This option sends a complete archive to the recipient's PC via analog modem. An analog
modem must be connected either to one of controller COM ports or to one of I-LB modules connected to the
controller via CAN2 bus. The channel address must contain complete telephone number of the recipient's
PC where InteliMonitor is running in Active call receiving mode.
DATA-GSM: This option sends a complete archive to the recipient's PC via GSM modem. A GSM modem
with activated CSD data transfers must be connected either to one of controller COM ports or to one of I-LB
modules connected to the controller via CAN2 bus. The channel address must contain complete telephone
number of the recipient's PC where InteliMonitor is running in Active call receiving mode.
DATA-ISDN: This option sends a complete archive to the recipient's PC via ISDN modem. An ISDN modem
must be connected either to one of controller COM ports or to one of I-LB modules connected to the
controller via CAN2 bus. The channel address must contain complete telephone number of the recipient's
PC where InteliMonitor is running in Active call receiving mode.
DATA-CDMA: This option sends a complete archive to the recipient's PC via CDMA modem. A CDMA
modem must be connected either to one of controller COM ports or to one of I-LB modules connected to the
controller via CAN2 bus. The local CDMA network must allow point-to-point data transfers. The channel
address must contain complete telephone number of the recipient's PC where InteliMonitor is running in
Active call receiving mode.
SMS-GSM: This option sends a short text message (SMS) containing the actual Alarmlist contents to the
recipient's mobile phone via the GSM modem. The channel address must contain complete telephone
number of the recipient's mobile phone.
SMS-CDMA: This option sends a short text message (SMS) containing the actual Alarmlist contents to the
recipient's mobile phone via the CDMA modem. The channel address must contain complete telephone
number of the recipient's mobile phone.
IB-E-MAIL: This option sends an e-mail containing the actual Alarmlist contents and latest 20 history records
(only date, time, reason) to the recipient's mailbox via the IB-COM module or IG-IB module. The channel
address must contain valid e-mail address of the recipient.
NOTE:
The SMTP settings (SMTP authent,SMTP user name, SMTP password, SMTP address, Contr mailbox) must
be properly adjusted for sending e-mails.
There is an example of setting of Remote Alarm Messaging. In this case active calls we be triggered on
Mains protect and Mains protect with Reset alarms. Message is sent via email to
emailAddress@domain.com (Channel 1 – available for NTC controller or with any controller with connected
IB-NT or I-LB+), archive is sent via ISDN modem to the number +111222333444 (Channel 2) and SMS is
sent to the number +999111333555 (Channel 3).
It is also possible to adjust number of attempts that controller performs in case of not successful Active Call –
Comms settings:ActCallAttempt. The language of messages can be changed –
Comms settings:Acall+SMS lang (use Translator and Languages tabs in GenConfig to adjust languages).
Up to five channels can be used.
Controller Redundancy
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 rendundancy function itself.
CAUTION!
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 needs to be altered so it can receive signals from both
controllers (e.g. using built-in PLC functions).
Redundant systems using binary signals
It is not possible to use this redundancy system since correct function of the ccontroller depends on CAN bus
communication and thus CAN redundancy should be always used.
Redundant systems using CAN bus
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 (~100ms) it will take
over the system control - it activates the binary output CTRLHBEAT FD, 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 binary input EMERG. MANUAL.
As there can be up to 16 pairs of controllers at the CAN bus it is necessary to select which main controller
(address) belongs to which redundant one. The setpoint ProcessControl:Watched Contr 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.
CAUTION!
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.
Do not use Shared Binary Inputs/Outputs for CTRLHBEAT FD->EMERG.MANUAL connection since the failed
controller may not interpret it correctly!
In the figure above the signal of logical function CtrlHBeat FD is used to disable the main controller if it is lost
from CAN bus or CAN bus 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). For more information on
Virtual Binary Inputs and Outputs (VPIO) please refer to the chapter about Shared Binary Inputs and Outputs
and Virtual Binary Inputs and Outputs.
NOTE:
Use pulse signals for control of circuit breakers. MCBONCOIL,MCBOFFCOIL,MGCBONCOIL and MGCB
OFFCOIL should be used to prevent sudden opening for a short period of time when the controller fails and
to ensure proper function of redundancy.
Force value – step by step guide
In this chapter there is complete step by step guide which shows how to use Force value function of the
controller.
Forcing of values is used to change particular setpoint temporarily by activation of related Binary Input. This
is used to change function of controller under given conditions (e.g. there are two different periods during the
day when Export limit given by distribution network is required or not).
WARNING!
Setpoints must not be written continuously (e.g. via Modbus connection)! If continuous change of setpoints
is required, combination of External values and Force value function needs to be used. The memory that
holds setpoints is designed for up to 105 writings. Than memory may be damaged!
Setpoints that are available for forcing may be identified by Force value button on the right side in GenConfig
(see the figure below).
Figure: Example of redundancy function
When the button is clicked, Force value dialog appears.
Change position of Force value functions (priority)
Change the name of the source setpoint
(available only for Force value 1-16 setpoints)
Select the value that should be forced (i.e.
the value of the particular setpoint)
Rename binary input that
triggers the forcing
ID of binary input
(1 for ForceValueIn 1 etc.)
Select source setpoint or value
For example if we add Force value:Force value 1 to be forced to ProcessControl:Export limit as value 0
(DISABLED) by Binary Input FORCEVALUEIN 1 we can change the function of Export limit from ENABLED to
DISABLED by activation of FORCEVALUEIN 1. It is possible to rename the setpoint to e.g.
Force value:ExportDisabled and Binary Input as well to e.g. DISABLEEXPLIM. The function will not change
(only the corresponding names).
It is possible to use several force value functions for one setpoint. If more than one forcing Binary Input is
active, the one with the highest position (lowest number in the Force value dialog) is used.
It is possible as well to use one Binary Input to force multiple setpoints (e.g. in case of complex function
change).
NOTE:
It is possible only to force value or setpoint in other setpoint if their dimension and range are the same (e.g.
only value with dimension in hours and which is Integer 16 to a setpoint with dimension hours and which is
as well Integer 16). You may use PLC block Convert to change the dimension and range if needed.
Values for continuous writing from external sources
ONCE
This is a single shot mode. The timer will be activated only once at preset date/time for
preset duration.
DAILY
The timer is activated every "x-th" day. The day period "x" is adjustable. Weekends can
be excluded. E.g. the timer can be adjusted to every 2nd day excluding saturdays and
sundays.
WEEKLY
The timer is activated every "x-th" week on selected weekdays. The week period "x" is
adjustable. E.g. the timer can be adjusted to every 2nd week on monday and friday.
MONTHLY
The timer is activated every "x-th" month on the selected day. The requested day can
be selected either as "y-th" day in the month or as "y-th" weekday in the month. E.g. the
timer can be adjusted to every 1st month on 1st tuesday.
This function is especially designed for continuous writing of setpoints from external sources (e.g. via
Modbus connection).
WARNING!
Setpoints must not be written continuously (e.g. via Modbus connection)! If continuous change of setpoints
is required, combination of External values and Force value function needs to be used. The memory that
holds setpoints is designed for up to 105 writings. Than memory may be damaged!
It is possible to use up to four different External values for continuous writing from external sources. The
values are adjusted by setpoints in Force value group. Default (also initial) value may be adjusted, rate of
change of ExtValueX (by Binary Inputs EXTVALUEX UP and EXTVALUEX DOWN) can be adjusted as well as
high and low limit of the value.
There are two way, how to adjust External values. One is using Binary Inputs mentioned above. Second one
is to write the value directly using e.g. Modbus. External values then may be converted using PLC block
convert and force into setpoint which is then continuously forced (note: NOT WRITTEN) by the value of
ExtValueX. This way internal memory is safe and no damage may occur.
External values are reverted back to their default (initial) value (given by corresponding setpoint) when
Binary Input for their reset is active (and they change to the previous value after Binary Input deactivates).
When the Binary Input is active the External value cannot be changed by Modbus writing or by using Binary
Inputs for up and down value.
NOTE:
External values are not available for external writing when any Binary Input (up, down or reset) related to
them is active.
Note also that when the controller is reset (powered down and up again), all external values are reverted
back to their default (initial) values.
HINT
For information on how to write (or read) objects from controller via Modbus, please refer to the latest
Communication guide for InteliGen and InteliSys.
General Purpose Timers
There is 16 general-purpose timers in the controller, each 4 of them are joined together to one output. That
means there are 4 fully independent timer blocks including 4 timer channels each. The combined outputs
from the timer blocks are TIMERACT 1-4, TIMERACT 5-8, TIMERACT 9-12ANDTIMERACT 13-16.
The timers are intended for scheduling of any operations such as e.g. periodic tests of the gen-set,
scheduled transfer of the load to the gen-set prior to an expected disconection of the mains etc. Each timer
channel can be activated only once within a single day. The activation time and duration of each channel is
adjustable (both as hh:mm).
The timer is repeated with adjusted period (hh:mm). The timer duration is included in
the preriod.
The mode of each timer channel is adjusted by an assigned setpoint. The setpoints are located int the Timer
settings group and can be adjusted via InteliMonitor and GenConfig.
Figure: Principial scheme of one block containing 4 timers
EXAMPLE:
Below is an example how to use the timers for periodic tests of the gen-set performed every sunday with
duration of 30 minutes and also for scheduled transfer of the load before expected mains failure announced
by the local electricity distribution company to 1.5.2010 from 01:00 to 04:00.
1. The output TIMERACT 1-4 is configured internally in GenConfig (LBI tab) to the logical binary
inputs REMOTE TEST and TESTONLOAD.
2. The setpoint Timer settings:TimerChannel 1 is adjusted to "repeated" mode, "weekly" period, only
sundays, starting date/time next sunday at 0:00, timer duration 0:30 min.
3. The setpoint Timer settings:TimerChannel 2 is adjusted to "once" mode, starting date/time 1.5.2010
at 01:00, timer duration 3:00 hrs.
History Related functions
History Records Adjustment
It is possible to change History records content. Each record contains date, time and cause of the record as
obligatory columns. The rest of columns are configurable.
The history record structure has two parts. The upper part is so-called fast and is written into the history
memory immediately in the moment when the written event occurs. The rest of the record may be written
with a delay max. 100ms. The fast part is intended for fast changing values as e.g. currents, voltages or
power. The parts are separated by a line in the record content list.
1. Values selection tree
2. Buttons for adding/removing values into/from the record structure
3. Buttons for ordering of the values in the record structure
4. Fast history separator. The fast part is located above the separator
5. Estimated number of records depending on record size
6. Record capacity usage indicator
NOTE:
Values that are displayed in green color are recomended to be placed in the fast part.
If the checkbox Add modules to history automatically.. in the Modules tab is checked then all values of a
module are automatically added into the history record when the module is inserted into the configuration.
Time Stamp function
The controller allows user to define when the history records are written even though there is no other
reason for history record (so called Time Stamp).
It is possible to disable time stamping function (for example when time stamping is not needed and just
floods the history). It may be conditioned by activation of logical Binary Input function (TIMESTAMPACT) or it
may be enabled always.
Period of time stamping may be adjusted from 1 to 240 minutes.
NOTE:
Beware of History flooding by to many Time Stamps (vital information may be overwritten).
Time and Date Intercontroller Sharing
Time and Date are used mainly for History records. These values are shared between controllers that are
connected to CAN. When the value is changed in one controller, it sends its new value to all other controllers
that are connected to the same CAN bus and they update their time and date values and setpoints
accordingly.
Summer Time Mode
Summer Time Mode function may be enabled and disabled by user. It is possible to set if the controller is
located in the northern or southern hemisphere as well.
SummerTimeMode implemented in ComAp controllers is based on CET summer time which means:
Clock goes forward 1 hour at 2:00 a.m. on the last Sunday in March
Clock goes backwards 1 hour at 3:00 a.m. on the last Sunday in Octorber
NOTE:
Please be aware that in other regions summer time adjustments may be done in different time.
Pressing the button changes the state of log. Binary Output USER BUTTON X to closed.
When the output is closed and the button is pressed state is not changed.
OFF
Pressing the button changes the state of log. Binary Output USER BUTTON X to opened.
When the output is opened and the button is pressed state is not changed.
ON/OFF
Pressing the button changes the state of log. Binary Output USER BUTTON X to opened or
closed depending on previous state (it is changed to the opposite state).
PULSE ON
Pressing the button issues log. Binary Output USER BUTTON X to close for one second.
NOTE:
Repeated pressing of button during the closed period (one second) causes issuing other
puls of length of one second to be generated from the moment of button pushing.
There are several User Buttons available in the controller. It is possible to set them on Soft Buttons in
InteliVision 5 or 8.
Available functions for soft buttons are listed in the following table.
HINT
It is possible to lock User Button with password (go to tab Commands in GenConfig). User Buttons 1-5, 6-8
and 9-16 can be locked separately. It is also possible to use User Buttons in SCADA diagrams.
Remote Control Function
It is possible to remotely control several Binary Outputs in the controller. You can either use Remote
Switches tool in InteliMonitor (select Remote switches in menu for corresponding controller), import Remote
Switches tool to a SCADA diagram in Line Diagram Editor or use external device via Modbus (register
#46361 and command #26 (1A hex), for more information on Modbus please refer to the InteliGen/InteliSys
Communication guide).
Remote Switch will activate or deactivate depending on remote control so it can be used to manually control
devices, simulate malfunctions while commissioning etc.
Figure: Remote Switches tool in InteliMonitor, Remote Switches tools in Line Diagram Editor and Mobus commands
Remote Switches may be easily used to trigger logical Binary Input function and all other related functions as
normal switch on Binary Input. Module VPIO (Virtual Peripheral Inputs- Outputs) can be added to
configuration and it will copy the state of Remote Switch on virtual output to its counterpart virtual input.
Refer to the figure below for example.
Figure: Using of Remote Switches to trigger logical binary inputs
Virtual Peripheral Inputs-Outputs (VPIO) module
For the controller there are several modules available. One of them is Virtual Peripheral Inputs-Outputs
module which is particularly usefull for connection of logical Binary Output functions to logical Binary Input
functions. This way internal controller function may easily trigger other internal controller functions without
unnecessary wiring or usage of PLC functions.
Module is functioning the same way as normal module with 8 outputs and 8 inputs, but the difference is, that
each input copies its counterpart output. It is possible to select any logical Binary Output function for one of
the outputs of VPIO module. Inputs on VPIO module work the same way as standard input of the controller
(i.e. it can be assigned function and protection).
For example of this function please refer to the chapter Remote Control function.
Shared Inputs and Outputs
It is possible to share Binary and Analog values between all the controllers via CAN bus, thus saving
physical Inputs and Outputs and excess wiring.
Shared Binary Inputs and Outputs may be used exactly in the same way as standard physical Inputs and
Outputs. If SHBIN or SHAIN modules are configured, at least one corresponding module of SHBOUT or
SHAOUT (respectively) is needed. If it is not configured, corresponding protection appears because SHBIN
or SHAIN will be missing. See the figure below for more information.
CAUTION!
For proper function of Shared Binary and Analog Inputs and Outputs, only one source of Shared Binary or
Analog Outputs must be configured (i.e. it is not possible to configure in one controller SHBOUT1 and to
another one as well SHBOUT1).
HINT
Controller sends Shared Binary Outputs each 100ms if there are any changes in any bit position. If there are
no changes, controller sends the information with period 1s.
Figure: Adding of various modules
Figure: Principal Scheme (same for shared Binary I/O and shared Analogue I/O
It is possible to share Binary and Analog values between all the controllers via CAN bus, thus saving
physical Inputs and Outputs and excess wiring.
DISTBIN and DISTBOUT work in a different way than SHBIN and SHBOUT. Each controller has one pack of
eight DISTBOUT available (if not configured or no function is assigned to any output, it does not broadcast
them). The number of DISTBOUT module is not shown in the configuration and it is always corresponding to
the CAN address of the controller (e.g. the controller with address 5 will be broadcasting DISTBOUT-05
which can be received if module DISTBIN-05 is configured in another controller. Up to 32 DISTBIN modules
can be configured (meaning that the controller will be receiving all DISTBOUT from all the controller, even
his own).
It is not possible to change the name of DISTBIN inputs or add protections.
In the example below you can see 4 controllers with various DISTBIN and DISTBOUT configuration.
NOTE:
HINT
Controller sends Distributed Binary Outputs each 100ms if there are any changes in any bit position. If there
are no changes, controller sends the information with period 1s.
NOTE:
DISTBIN and DISTBOUT function is not available for IM-NT-GC controller.
Controller supports Modbus Slave functions (an external device may write or read from a controller). Modbus
registers corresponding to objects in the controller can be exported to text form in GenConfig.
Figure: Exporting of Modbus registers
If Modbus Master function is required extension module I-CB/Modbus connected via CAN1 can be used. For
more information on how to use this module please refer to InteliGen/InteliSys Communication Guide and to
I-CBEdit manual.
Resolution and Range of the sensor (in
some cases this is fixed by sensor type
and cannot be changed)
Interpretation of
the received value
in bar graph form
Offset of the
received value
User MODBUS
Users can define Modbus registers from 42873 to 43000. Values, setpoints and Alarm states can be
specified for these new Modbus registers to prepare the Modbus protocol for batch reading and writing or to
standardize Modbus protocol between FW versions or branches.
NOTE:
User MODBUS function is not available for IM-NT-GC controller.
Analog Input Sensors and User Sensors
Controller and/or some extension modules allow connection of sensor outputs to Analog Inputs. There is
whole variety of common sensor output characteristics prepared in configuration by default. Although if there
is sensor that is not in the list, it is possible to prepare custom characteristics (up to 16) with up to 31
definition points.
There is “electronic” type of sensor available for Shared Analog Inputs which can be used to interpret shared
data over CAN bus.
Languages and Translator tool in GenConfig
For detailed description of Languages and Translator tool please refer to GenConfig interactive help (press
F1 when in corresponding tab or open Help -> GenConfig Help).
Power Formats
IGS-NT family allows user to choose from several Power Formats that affect dimensions in which values and
some setpoints are interpreted or adjusted. Power formats may be changed in Miscellaneous tab in
GenConfig. There are following Power Formats available:
1 kW kVAr kVA kX V
0,1 kW kVAr kVA kX V
0,01 MW MVAr MVA MX kV
0,01 MW MVAr MVA MX V
NOTE:
Range of some setpoints and values is changed significantly when different Power Formats are selected.
Last Power Format is designed to be used in combined Power/High Voltage and Low Voltage instalations.
High voltage is then interpreted in Volts (e.g. 33256V instead of 33kV).
Last two Power Formats can be used in combination on one CAN bus.
For proper function of the system, System start and stop signal needs to be used properly. Below there is
scheme that shows how to use the Binary Output SYS START/STOP in the system using just CAN wiring (no
physical wiring is needed to share the starting and stoping signal into all controllers in the system).
Figure: Preparation of correct system start/stop function for two logical groups
In GenConfig you can easily set any object in Screen Editor to show or hide based on activation of particular
Logical Binary Input available for users. Below, there is diagram showing the setup of User Mask function in
Screen Editor.
NOTE:
Masking of screens in InteliVision 5 supports only Show function
Use also other masking functions (masking can react on several internal states, e.g. activation of Timers).
PLC functions
See description in IGS-NT-Application Guide 05-2013.pdf.
Multi language support
NT family controllers support up to five Languages that is possible to switch during controller duty. Every
terminal (i.e. Remote display or PC-InteliMonitor) can be switched to different language. Use PC-GenConfig
- Translator tool to translate texts to another language.
Default application archives contain all texts in English only.
ECU interface customizing
The list of available ECU interfaces can be found in GenConfig / Modules / ECU list.
This function enables to change the following CAN values transmitted to ECU via J1939 or binary output
only. The change can be provided by setpoint or via Binary input. There are four Bin selector channels
available.
The alarm appears in the Alarmlist and is recorded into the history log.
Activates the output Common Wrn as well as the standard alarm outputs.
Alarm Only
1
The alarm appears only in the Alarmlist.
Activates the output Common Al as well as the standard alarm outputs.
HistRecOnly
1
The event is recorded into the history.
Activates the output Common Hst for one second. Standard alarm outputs
are not activated.
AL indication
1
The event is only indicated in the Alarmlist.
It disappear for the alarmist automatically as soon as the cause
disappears.
Standard alarm outputs are not activated.
A+H indication
1
The event is only indicated in the Alarmlist and recorded into the history
log.
It disappear for the alarmist automatically as soon as the cause
disappears.
Standard alarm outputs are not activated.
Shutdown
2
The alarm appears in the Alarmlist and is recorded into the history log.
It causes immediate stop of the gen-set without unloading and cooling
phase.
The gen-set can't be started again while there is a Shutdown alarm in the
Alarmlist.
Activates the output Common Sd as well as the standard alarm outputs.
Slow Stop
2
The alarm appears in the Alarmlist and is recorded into the history log.
It causes stop of the gen-set by the standard stop sequence, i.e. including
unloading and cooling phase.
The gen-set can't be started again while there is a Slow stop alarm in the
Alarmlist.
Activates the output Common Stp as well as the standard alarm outputs.
Off Load
2
The event appears in the Alarmlist and is recorded into the history log. It
does not require confirmation, diappears by itself.
It causes immediate opening of the GCB. In AUT and SEM modes the genset remains running for 60 seconds and then it is 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 AUT or SEM 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
(e.g. Rem start/stop is active ..).
This event is used to put the gen-set temporarily off the load for any
reason.
Activates the output Common OfL.
The event appears in the Alarmlist and is recorded into the history log. It
does not require confirmation, diappears by itself.
It causes reduction of the required gen-set load to the Min Power PtM
during parallel-to-mains operation or local baseload operation.
If all previously active Low power alarms disappeared the gen-set is
automatically ramped back to the original required load, which is given
according to the currently active load control mode (Load ctrl PtM) in PtM
operation.
Activates the output Common LoP.
This alarm type is not overriden by the input Sd Override.
Note:
Available in IS-NT only.
BrkOpen&CoolDn
2
The event appears in the Alarmlist and is recorded into the history log.
It causes immediate opening of the GCB (without unloading) and then the
standard stop sequence with cooling follows.
The gen-set can't be started again while there is a BOC alarm in the
Alarmlist.
Activates the output Common BOC as well as the standard alarm outputs.
Sd Override
2
The alarm appears in the Alarmlist and is recorded into the history log.
It causes immediate stop of the gen-set without unloading and cooling
phase.
The gen-set can't be started again while there is a Sd override alarm in the
Alarmlist.
Activates the standard alarm outputs.
This alarm type is not overriden by the input Sd Override.
HINT
The Standard alarm outputs are Alarm and Horn.
Sensor fail detection (FLS)
If the measured resistance, voltage or current on an analog input gets out of valid range, the sensor fail will
be detected and a sensor fail message will appear in the alarmlist. The valid range is defined by the most-left
(RL) and most-right (R
) points of the sensor characteristic ±12.5% from R
H
H-RL
.
HINT
The sensor fail alarm does not influence the gen-set operation
The alarms are beeing evaluated all the time the controller is switched on.
RunOnlyBlkDel1
The alarms are beeing evaluated only while the gen-set is running. The evaluation
begins RunOnlyBlkDel1 seconds after the engine has been started.
RunOnlyBlkDel2
The alarms are beeing evaluated only while the gen-set is running. The evaluation
begins RunOnlyBlkDel2 seconds after the engine has been started.
RunOnlyBlkDel3
The alarms are beeing evaluated only while the gen-set is running. The evaluation
begins RunOnlyBlkDel3 seconds after the engine has been started.
Force block 1
The alarms are beeing evaluated while the input Force block 1 is not active. The
evaluation begins ForceBlockDel1 seconds after the input has been deactivated.
Force block 2
The alarms are beeing evaluated while the input Force block 2 is not active. The
evaluation begins ForceBlockDel2 seconds after the input has been deactivated.
Force block 3
The alarms are beeing evaluated while the input Force block 3 is not active. The
evaluation begins ForceBlockDel3 seconds after the input has been deactivated.
El. prot
The alarms are beeing evaluated while the generator is expected to provide correct
voltage and frequency. That means the alarms start to be evaluated after transition
form Idle to Running phase when the period of Max stab time has already elapsed,
remain beeing evaluated while the gen-set is running at nominal speed (regardless
of GCB position) and stop to be evaluated by transition to the Cooling phase.
BOC L31 under
BOC L12 over
BOC L23 over
BOC L31 over
Gen V L1-L2
BOC fg under
BOC fg over
Gen freq
Gen V L2-L3
Gen V L3-L1
Basic settings:
VoltProtSelect = PHASE-PHASE
Gener protect: Gen >V BOC Gen <V BOC
Gen V Sd
Gen V del
Gen >f
Gen <f
Gen f del
Generator voltage and frequency protections - limits and indications
Shutdown override
If the Binary input shutdown override (Sd override) is closed, all 2nd level protections are disabled to allow
engine run in an emergency situation, e.g. sprinkler devices power supply.
All protections are shown in Alarmlist and recorded into History, but the controller doesn’t 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.
HINT
All 2nd level protections are locked out, except of these:
- Emergency stop
- Overspeed
- Underspeed (only if Fuel solenoid = GAS ENGINE)
- 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 can not
be overriden (blocked) by the Sd override input.
- once = only when it is trigged
for the first time
Defines when the protection
is active
User custom setpoint for
level 1 limit (enables when
level 1 protection type is
selected)
User custom setpoint for
level 2 limit (enables when
level 2 protection type is
selected)
Delay of the protection
evaluation for both levels
(enables when at least one
protection type is selected)
Existing custom protections
list
Add protection
Delete protection
Select the value for the
protection
Select the protection type
Select if the protection is
under or over limit and if it
should have fail sensor
protection
Defines when the protection
is active
Add new message for
protections
Select message from existing
ones
Select
protection group
(setpoints for
this protection
will be placed in
corresponding
group)
Select wheter the
protection should be
evaluated each 100ms
or each 20 ms.
Protection is
written to the
history
- alway = when it is
trigged
- once = only when
it is trigged for the
first time
Select whether new setpoint should
be created to limit the protection or
an existing one should be used or if
the limit should be constant
Limit the new setpoint value range
Select whether new setpoint should
be created todelay the protection
or an existing one should be used or
if the delay should be constant
HINT
Fail Sensor protection (when activated) does not affect the function of the system itself. If you adjust “Active
when” to Under limit + Fls or Over limit + Fls the protection will considered the value that is out of range
(failed sensor) to be under or over limit (depending on the setting) and it will issue corresponding alarm after
the delay of the protection. This can be used for example when the function of the particular sensor
connected to an analog input is crucial for the operation of the system and its failure requires the system to
be affected (open breakers etc.).
Custom configurable protection
Open Protections tab in GenCofig and adjust parameters that are described below.
HINT
You need to prepare two separate protections for level 1 and level 2.
Select the value for protection first and then use Wizard – it will take you through all the steps and help you
Pressing of the fault reset button (at any terminal or external button) resets
only inactive alarms. Active alarms remain in the alarmlist unchanged and must be reset
again when they become inactive.
ENABLED
Pressing of the fault reset button (at any terminal or external button) resets all alarms that
are currently present in the alarm list. Inactive alarms disappear from the alarm list
immediately, active alarms are changed to "confirmed" state and disappear when the
alarm condition disappear or the alarm starts to be blocked.
It is possible to determine the behavior of alarms that are in alarm list when Fault Reset button is pressed.
Select behavior with ComProtSetting:ResetActAlarms.
NOTE:
ENABLED position corresponds to the method how the IG-classic and IS-classic controllers handled the
alarms.
PLC x x x x - Programmable (internal) logic module.
Virtual and physical modules
Number of I/O can be extended and project wiring can be reduced using the following extension and virtual
modules.
HINT
For more details about Virtual peripherals (Shared and Internal virtual I/O periphery and PLC) see IGS-NTApplication guide-2.4.pdf.
CAUTION!
Usage of any 3rd-party peripheral modules in cooperation with ComAp controller is not recommended.
ComAp can’t guarantee the proper function of controller with none-ComAp peripheral modules.
Setpoints are analog, binary or special data objects, that are used for adjusting the controller to the specific
environment. Setpoints are collected to groups according to their meaning. Setpoints can be adjusted from
the controller front panel, PC, MODBUS etc.
Password protection
Any setpoint can be password protected - 7 levels of protection are available. There can be up to 8 users
defined, each one with different access rights (levels of protection). Every user has it’s own password. The
password is a four-digit number. Only setpoints protected by the protection level that is covered by currently
logged-in user’s access rights can be modified.
If a user logs in from a particular terminal (e.g. the controller front panel), this does not unlock the other
terminals for him, e.g. InteliMonitor connected directly or via modem.
Setpoints opened from front panel are automatically closed 15 minutes (return to measurement screens)
after the last setpoint change or when wrong value of password is set.
System administrator (User 0 – always present in the system) can reset the password for any other user.
The controller programming (configuration) requires the highest - password 7 level, so only User 0 is able to
modify the controller configuration or firmware.
Continuous internal evaluation of setpoints validity
In case of detection of Setpoints checksum (validity) evaluation error, the Shutdown alarm “Setpoint CS
error” is issued to prevent the controller to run the engine with incorrect setting. The evaluation is provided at
controller startup and continuously during the standard operation. I.e. in case of detection of such error, the
engine is shut down immediatelly.
Setpoint synchronization
Setpoints, that are marked with "#" sign at the begin of their names, are synchronized with other controllers
present on the CAN bus line, i.e. the system will ensure that the respective setpoint will have identical value
in each connected controller. If the setpoint is changed in one controller, the same change will occur in all
other controllers. This function is necessary especially for MINT application, where the system of Power
management is based on fact that the respective setpoints are identical in all controllers.
CAUTION!
Do not perform repeated writing of setpoints (e.g. power control from a PLC by repeated writing of baseload
setpoint via Modbus) The setpoints are stored in EEPROM memory, which can be overwritten up to 105
times without risk of damage or data loss, however it may become damaged, when allowed number of
writing cycles is exceeded!
IGS-NT istallation pack contains separate PC software tools: GenConfig (GC) and InteliMonitor (IM).
GC and IM are based on Windows 95/98/NT/ME/2000/XP or higher platform and require approximately 30
Mbyte of hard disc free space.
Direct connection to the PC
IGS-NT controller can be connected directly with PC via RS232 or USB interface. Use the crossed RS232 or
USB cable to connect PC with controller.
HINT
Make sure the grounding system on controller and PC – COM port (negative of the PC DC supply) are
identical – before the first direct connection. There must not be any voltage between these two points
otherwise the internal PTC protection activates and interrupts RS232 communication. In such case
disconnect RS232 line wait a minute for PTC recovery and try again. The simple solution is to assure, that
the PC supply 240/20V is ground free (GND terminal is not connected).
GenConfig functions
Extension modules addressing
All I/O function or protection configuration
Setpoints adjusting
Sensor characteristics modification
History record modification
Password level protection modification (password value must be changed in DriveMonitor)
Controller firmware (mhx file) upgrade
Controller application file Up/Down load
Language translator enables
o Create Dictionary between two languages (Dictionary can be used repeatedly)
o Translate current text in Controller (in any language)
o Add new language (up to five)
Configuration steps
Following configuration steps are available in GenConfig software:
Select Extension modules when more inputs and outputs are required
Configure J1939 interface when Electronic engine is connected
Configure Binary inputs as Protection or Function
Configure Binary outputs
Configure Analog inputs as Protection or Function
Define user sensors
Configure History record
Configure password protection
Add/Translate the language
On-line direct, Modem or Internet single or multiple engine monitoring
Active Modem or Internet call from the controller to PC (activated by selected Alarm)
On-line or Off-line History record listing
Setpoints listing and adjusting (password protected)
Statistics value (e.g. Running hours) Set/Reset
Password and Access code change
Modbus protocol
Standard protocol enables receive/transmit any data or command from a Master system:
Direct connection: RS232, RS422, RS485
Modem connection
9600, 19200, 38400 or 57600 bps, 8 data bits, 1 stop bit, no parity
Transfer mode RTU
Function 3 (Read Multiply Registers)
Function 6 (Write Single Register)
Function 16 (Write Multiply Registers)
The response to an incoming message depends on the communication speed. The delay is not shorter
than the time needed to send/receive 3 and ½ characters.
The complete description of Modbus communication protocol can be found in Modbus Protocol Reference Guide PI-MBUS-300 and Open Modbus Specification Release 1.0. Both documents are available from web
site at http://www.modicon.com/openmbus/ .
HINT
Detail Modbus command description see in ComAp InteliCommunication guide.
Value and setpoint codes
HINT
It is possible to export actual values, setpoints and history file on-line from the controller or off-line from the
archive using InteliMonitor – Monitor – Export data… function.
Technical data
HINT
Technical data of the controller and extension modules find in the IGS-NT-Installation guide-x.y.pdf.
Language support
IG-NT from display firmware version 1.4 supports following language code pages:
Do not perform repeated writing of setpoints (e.g. power control from a PLC by repeated writing of baseload
setpoint via Modbus) The setpoints are stored in EEPROM memory, which can be overwritten more than 105
times without risk of damage or data loss, but it may become damaged, when allowed number of writing
cycles is exceeded!
This setpoint is used to adjust the requested load for the whole gen-set group
in system baseload mode (i.e. #SysLdCtrl PtM = BASELOAD). Each gen-set
takes proprtionally equal part of this total required value. The number of running
gen-sets is resolved by the power management function according to the
requested total load, gen-sets nominal power and adjusted reserves.
Group
Process control
Range [units]
OFF, 1 .. Nomin power [kW]
Related FW
3.0
Force value
possible
YES
Description
This setpoint is used to adjust local baseload level. The gen-set maintains this
load instead of performing proportional load sharing whenever the total load is
high enough. Load variations are then equalized by the gen-sets with lower
priority (higher number) or by gen-sets with local baseload switched off. If the
setpoint is adjusted to 0 (OFF) the function is off. Description of the function is
available in the chapter Local baseload.
Group
Process Control
Range [units]
0.60 .. 1.20 [-]
Related FW
3.0
Description
The setpoint is used for adjusting the requested gen-set power factor during the
parallel-to-mains operation if #SysPFCtrl PtM = BASEPF and also during the local
This setpoint is used to adjust the power control mode in parallel-to-mains
operation.
BASELOAD: The gen-set is controlled by the load control loop (i.e. as in
SPtM) to provide constant proportional part of the requested system
baseload (see SysBaseLdMode). The proportional parts of all running
gen-sets are equal relative to their nominal power.
LDSHARING: The gen-set load controlled by the load sharing loop as in
island operation. This option is intended only for systems with InteliMains,
where the InteliMains controls the power of the group via the load sharing
line (e.g. in Import/Export mode).
Group
Process Control
Range [units]
BASEPF, VSHARING [-]
Related FW
3.0
Description
This setpoint is used to adjust the power factor control mode in parallel-to-mains
operation.
BASEPF: The gen-set power factor is controlled to a preadjusted level
#SysPwrFactor.
VSHARING: The power factor is equalized with other gen-sets according
to the actual reactive load.
NOTE:
If the power factor control mode is switched to VSHARING the load control mode
must be switched to LDSHARING.
Group
Process control
Range [units]
INTERNAL, EXTERNAL [-]
Related FW
3.0
Force value
possible
YES
Description
This setpoint selects from where the System Base load value is taken if the load
control mode in parallel-to-mains operation is switched to baseload (i.e.
The baseload is adjusted by the setpoint #SysBaseLoad.
EXTERNAL
The baseload is adjusted by the logical (functional) analog
input MLC:AnExSysBld.
NOTE:
If the external source is selected the logical analog input must be configured at
each gen-set to the identical source. The shared peripherial modules can be used
to distribute the value over the controllers via the CAN2 bus.
One controller measures the value physically on it's analog input and the
function MLC:AnExSysBld is configured onto this physical input. But the
value is also beeing transmitted from this controller to the CAN bus via
one shared analog output (e.g. SHAOUT #1.1).
The other controllers reads the value from their shared analog inputs (e.g.
SHAIN #1.1) and the function MLC:AnExSysBld is configured onto these
shared inputs.
The transmitting controller must be always switched on!
Group
Process control
Range [units]
INTERNAL, EXTERNAL [-]
Related FW
3.0
Force value
possible
YES
Description
This setpoint selects from where the System Power Factor value is taken if the PF
control mode in parallel-to-mains operation is switched to BasePF (i.e. #SysPFCtrl
PtM = BASEPF).
INTERNAL
The required power factor is adjusted by the setpoint
#SysPwrFactor.
EXTERNAL
The baseload is adjusted by the logical (functional) analog
input MPF:AnExSysBPF.
NOTE:
If the external source is selected the logical analog input must be configured at
each gen-set to the identical source. See the note at the setpoint
This setpoint is used for adjusting the starting point of the Power derating 1
function, where the gen-set nominal power is still 100% of the setpoint Nomin
power.
See the chapter Power derating for details.
NOTE:
The setpoint actual physical dimension depends on configuration of the physical
analog input to which the logical input PowerDerating1 is assigned.
Group
Process control
Range [units]
-32000 .. +32000 [x]
Related FW
3.0
Force value
possible
YES
Description
This setpoint is used for adjusting the end point of the Power derating 1 function,
where the gen-set nominal power is reduced to the value adjusted by setpoint
Derated1 pwr.
See the chapter Power derating for details.
NOTE:
The setpoint actual physical dimension depends on configuration of the physical
analog input to which the logical input PowerDerating1 is assigned.
Group
Process control
Range [units]
0 .. 100 [%]
Related FW
3.0
Force value
possible
YES
Description
This setpoint is used for adjusting the final power level for the Power derating 1
function. The nominal power is not reduced below this setpoint even if the
respective analog input increases further.
This setpoint is used for adjusting the starting point of the Power derating 2
function, where the gen-set nominal power is still 100% of the setpoint Nomin
power.
See the chapter Power derating for details.
NOTE:
The setpoint actual physical dimension depends on configuration of the physical
analog input to which the logical input PowerDerating2 is assigned.
Group
Process control
Range [units]
-32000 .. +32000 [x]
Related FW
3.0
Force value
possible
YES
Description
This setpoint is used for adjusting the end point of the Power derating 2 function,
where the gen-set nominal power is reduced to the value adjusted by setpoint
Derated2 pwr.
See the chapter Power derating for details.
NOTE:
The setpoint actual physical dimension depends on configuration of the physical
analog input to which the logical input PowerDerating1 is assigned.
Group
Process control
Range [units]
0 .. 100 [%]
Related FW
3.0
Force value
possible
YES
Description
This setpoint is used for adjusting the final power level for the Power derating 2
function. The nominal power is not reduced below this setpoint even if the
respective analog input increases further.
The setpoint is used for enable/disable forward and reverse synchronization.
NONE: No synchronizing is enabled.
FORWARD: GCB synchronizing is enabled.
REVERSE: MCB synchronizing is enabled.
BOTH: GCB and MCB synchronizing are enabled.
NOTE:
Although synchronizing of the particular breaker is disabled the breaker can be
closed to a "dead" (voltage-free) bus.
NOTE:
See table with examples in the description of the setpoint MFStart enable.
Group
Process control
Range [units]
EACH, COMMON [-]
Related FW
3.0
Description
The setpoint is used for adjusting the behavior of the Neutral CB C/O output
according to actual site wiring.
The neutral contactor is used to connect the neutral wire (N) with the protective
wire (PE) in a TN-S system. This connection must exist in one moment at one point of the circuit only.
The EACH option should be used if each gen-set has it's own neutral contactor.
Four-pole GCB must be used for 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
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.
NOTE:
Functional CAN2 communication between the controllers is required for
this function.
The COMMON option should be used if there is one common neutral contactor for
the whole site. The outputs Neutral CB C/O from all controllers are combined
together and the combined signal is used to control the breaker. Three-pole GCB
must be used for 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 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 breaker is closed.
NOTE:
If there are more logical groups the "common" option is related to the group. That
means one common neutral contactor is expected for each group.
PRINCIPIAL SCHEME OF A SITE IF NEUTRAL CONT =COMMON
As there is always a connection between the N and PE wires at the mains side the
generator neutral contactors are always open when the mains breaker is closed.
Group
Process Control
Range [units]
0 .. 16 [min]
Related FW
3.0
Description
This setpoint is used at redundant controller to specify the address of the related
main controller in CAN-based rendundant systems. Adjust this setpoint to 0 if the
controller is not used as redundant or if wired rendundancy system is used.
Group
Basic Settings
Range [units]
1 .. 32000 [kW]
Related FW
3.0
Force value
possible
YES
Description
This setpoint is used for adjusting the gen-set nominal (rated) power, i.e. the
maximum allowed gen-set power level.
IS-NT controllers provide two independent power derating functions, which can be
used for derating of the gen-set according to an analog value (e.g. temperature).
See the setpoints Derating1 strt and Derating2 strt.
The nominal power or derated nominal power is used as the basis (100%) for genset power protections, as the upper limit of the requested power in the parallel-tomains operation, for power management and other functions.
NOTE:
The actual setpoint units and range depend on setting of the Power format in
GenConfig.
Group
This setpoint is used for adjusting the generator nominal current.
The nominal current is used as the basis (100%) for generator thermal-
overcurrent protection (2Inom del), and for short current protection (Ishort).
NOTE:
The setpoints CT ratio prim and CT ratio sec must be adjusted properly to obtain
correct generator current readings.
CAUTION!
The maximum measurable input current to the controller current terminals is 11A.
WARNING!
Do not discconnect the CT terminals from the controller while there is nonzero
current in the CT primary circuit!
Group
Basic Settings
Range [units]
1 .. 15000 [A]
Related FW
3.0
Description
Nominal current of the primary side of the generator current transformers. The
secondary side is adjusted by setpoint CT ratio sec.
Group
Basic settings
Range [units]
/5A, /1A [-]
Related FW
3.0
Description
Nominal current of the secondary side of the generator current transformers. The
primary side is adjusted by setpoint CT ratio prim.
NOTE:
The CT secondary nominal current is adjustable only in IG-NTC and IS-NT. The
IG-NT has the CT secondary nominal current adjusted fixedly to 5A regardless of
this setpoint.
Group
Basic settings
Range [units]
1 .. 15000 [A]
Related FW
3.0
Description
Nominal current of the primary side of the current transformer connected to the
controller terminals labeled IN. The secondary side is adjusted by setpoint
The IN terminals are used for measurement of earth fault current.
Group
Basic settings
Range [units]
/5, /1 [A]
Related FW
3.0
Description
Nominal current of the secondary side of the current transformer connected to
the controller terminals labeled IN. The primary side is adjusted by setpoint
Im3/ErFlCurCTp.
NOTE:
The IN terminals can be used either for measurement of earth current or mains
current (mains import). See also the setpoint I/E-Pm meas.
NOTE:
The CT secondary nominal current is adjustable only in IG-NTC and IS-NT. The
IG-NT has the CT secondary nominal current adjusted fixedly to 5A regardless of
this setpoint.
Group
Basic Settings
Range [units]
0.1 .. 500.0 [V/V]
Related FW
3.0
Description
The setpoint is used to adjust the generator voltage transformers ratio.
NOTE:
Adjust the setpoint to the value of 1.0 if the generator voltage is connected directly
to the controller terminals, i.e. without transformers.
NOTE:
Example: if you have transformers with ratio 6000/100V adjust the setpoint to the
value of 60.0.
NOTE:
The range of the generator voltage inputs must be adjusted properly. See the
setpoint Vg InpRangeSel.
Group
Basic settings
Range [units]
277V, 120V [-]
Related FW
3.0
Description
This setpoint selects the range of the generator voltage terminals. The 120V
range is available only in IG-NTC and IS-NT. The IG-NT has the range adjusted
The 277V range is suitable for both European (230V) and American (277V)
measurement. The range 120V is intended for high-voltage applications where
voltage transformers with 100V secondary range are used or for alternative
American (120V) measurement.
Group
Basic Settings
Range [units]
0.1 .. 500.0 [V/V]
Related FW
3.0
Description
The setpoint is used to adjust the bus voltage transformers ratio.
NOTE:
See all notes mentioned above.
Group
Basic settings
Range [units]
277V, 120V [-]
Related FW
3.0
Description
This setpoint selects the range of the mains voltage terminals. The 120V range is
available only in IG-NTC and IS-NT. The IG-NT has the range adjusted fixedly to
277V regardless of this setpoint.
NOTE:
The 277V range is suitable for both European (230V) and American (277V)
measurement. The range 120V is intended for high-voltage applications where
voltage transformers with 100V secondary range are used or for alternative
American (120V) measurement.
Group
Basic settings
Range [units]
277V, 120V [-]
Related FW
3.0
Description
This setpoint selects the range of the bus voltage terminals. The 120V range is
available only in IG-NTC and IS-NT. The IG-NT has the range adjusted fixedly to
277V regardless of this setpoint.
This setpoint is used to adjust the nominal (rated) generator voltage (phase to
neutral). If you do not know the phase-neutral nominal voltage, you can adjust the
phase-phase nominal voltage GenNomVph-ph. The controller will then recalculate
the phase-neutral nominal voltage automatically.
NOTE:
The actual setpoint units and range depend on setting of the Power format in
GenConfig.
NOTE:
If different voltage on gen-set and on Bus/Mains is required the following
procedure is required:
Both setpoints (BusNomV and GenNomV) must be adjusted to the same values
according to the value of actual generator nominal voltage. E.g. gen-set nominal is
231 V but Bus/Mains nominal is 240 V.
In this case both setpoints need to be adjusted to 231 V and setpoints of
corresponding protections for Bus/Mains need to be set assymetrically.
For 240 V on Bus/Mains it is typical to open MCB when voltage reaches 254 V or
225 V. Since the setpoint is adjusted to 231 V corresponding protection setpoints
need to be adjusted to Mains >V MP = 106% and Mains <V MP = 97 % (hence
the desired values are reached).
Group
Basic Settings
Range [units]
17 .. 60000 [V]
Related FW
3.0
Description
This setpoint is used to adjust the nominal (rated) generator voltage (phase to
phase). This setpoint is also recalculated automatically when the phase-neutral
nominal voltage GenNomV is changed.
This setpoint can be used if you know the phase-phase nominal voltage only. The
controller will recalculate the phase-neutral nominal voltage automatically when
this setpoint is changed.
NOTE:
The actual setpoint units and range depend on setting of the Power format in
GenConfig.
NOTE:
If different voltage on gen-set and on Bus/Mains is required the following
procedure is required:
Both setpoints (GenNomVph-ph and BusNomVph-ph) must be adjusted to the
same values according to the value of actual generator nominal voltage. E.g. genset nominal is 400 V but Bus/Mains nominal is 415 V.
In this case both setpoints need to be adjusted to 400 V and setpoints of
corresponding protections for Bus/Mains need to be set assymetrically.
For 415 V on Bus/Mains it is typical to open MCB when voltage reaches 440 V or
390 V. Since the setpoint is adjusted to 400 V corresponding protection setpoints
need to be adjusted to Mains >V MP = 106% and Mains <V MP = 97 % (hence
the desired values are reached).
Group
Basic Settings
Range [units]
10 .. 34641 [V]
Related FW
3.0
Description
This setpoint is used to adjust the nominal bus voltage (phase to neutral). If you
do not know the phase-neutral nominal voltage, you can adjust the phase-phase
nominal voltage BusNomVph-ph. The controller will then recalculate the phaseneutral nominal voltage automatically.
NOTE:
The actual setpoint units and range depend on setting of the Power format in
GenConfig.
NOTE:
If different voltage on gen-set and on Bus/Mains is required the following
procedure is required:
Both setpoints (BusNomV and GenNomV) must be adjusted to the same values
according to the value of actual generator nominal voltage. E.g. gen-set nominal is
231 V but Bus/Mains nominal is 240 V.
In this case both setpoints need to be adjusted to 231 V and setpoints of
corresponding protections for Bus/Mains need to be set assymetrically.
For 240 V on Bus/Mains it is typical to open MCB when voltage reaches 254 V or
225 V. Since the setpoint is adjusted to 231 V corresponding protection setpoints
need to be adjusted to Mains >V MP = 106% and Mains <V MP = 97 % (hence
the desired values are reached).
Group
Basic settings
Range [units]
17 .. 60000 [V]
Related FW
3.0
Description
In application MINT and COX.
This setpoint is used to adjust the nominal bus voltage (phase to phase). This
setpoint is also recalculated automatically when the phase-neutral nominal voltage
BusNomV is changed.
This setpoint can be used if you know the phase-phase nominal voltage only. The
controller will recalculate the phase-neutral nominal voltage automatically when
this setpoint is changed.
NOTE:
The actual setpoint units and range depend on setting of the Power format in
GenConfig.
NOTE:
If different voltage on gen-set and on Bus/Mains is required the following
procedure is required:
Both setpoints (GenNomVph-ph and BusNomVph-ph) must be adjusted to the
same values according to the value of actual generator nominal voltage. E.g. genset nominal is 400 V but Bus/Mains nominal is 415 V.
In this case both setpoints need to be adjusted to 400 V and setpoints of
corresponding protections for Bus/Mains need to be set assymetrically.
For 415 V on Bus/Mains it is typical to open MCB when voltage reaches 440 V or
390 V. Since the setpoint is adjusted to 400 V corresponding protection setpoints
need to be adjusted to Mains >V MP = 106% and Mains <V MP = 97 % (hence
the desired values are reached).
Group
Basic settings
Range [units]
PHASE-NEUTRAL, PHASE-PHASE [-]
Related FW
3.0
Description
PHASE-NEUTRAL: The generator and mains/bus voltage protections are based
on phase-neutral voltages and the phase-neutral nominal voltages are taken as
100%.
PHASE-PHASE: The generator and mains/bus voltage protections are based on
phase-phase voltages and the phase-phase nominal voltages are taken as 100%.
NOTE:
Both options require different settings of protection levels to achieve identical
results.
EXAMPLE:
Phase-nominal voltage is 231V, actual voltages are L1N = 231V, L2N = 231V,
L3N = 219.5V => the L3N voltage is at 95% of the nominal. The same situation
evaluated from phase-phase voltages gives following results: nominal phasephase voltage is 400V, measured voltages are L12 = 400V, L23 = 390V, L31 =
390V => the L23 and L31 are at 97.5% of the nominal. It is obvious that if the
situation is evaluated from phase-neutral voltages the tripping level must be
adjusted to 95%, whereas the same situation evaluated from phase-phase
voltages require tripping level adjusted to 97.5%.
Group
Basic Settings
Range [units]
50 Hz, 60 Hz [-]
Related FW
3.0
Force value
possible
YES
Description
The setpoint adjusts nominal system frequency (choose 50 Hz or 60 Hz).
Setpoint Nom frq offset is used for setting offset to the chosen nominal frequency
(-2 to +2 Hz with step 0.01 Hz). Controller regulates to the Nominal Freq + Nom
frq offset frequency.
The value Nominal Freq + Nom frq offset is used as 100% for generator and
mains/bus frequency protections and as requested value for frequency regulation
(except synchronizing) if the setpoint Freq reg loop is set to ALL THE TIME.
Group
Basic Settings
Range [units]
-2.00 .. 2.00 [Hz]
Related FW
3.0
Force value
possible
YES
Description
The setpoint adjusts offset of nominal system frequency (Nominal Freq) with step
0.01 Hz.
Controller regulates to the Nominal Freq + Nom frq offset frequency.
The value Nominal Freq + Nom frq offset is used as 100% for generator and
mains/bus frequency protections and as requested value for frequency regulation
(except synchronizing) if the setpoint Freq reg loop is set to ALL THE TIME.
Group
Basic Settings
Range [units]
1 .. 500 [-]
Related FW
3.0
Description
Number of teeth on the engine’s flywheel for the pick-up sensor. Adjust the
setpoint to Fgen->RPM (0), if the pick-up sensor is not used. Then the engine
speed will be calculated from the generator frequency.
NOTE:
Generator voltage must be higher than 10V effective to measure the speed from
the frequency correctly. If this condition is not fulfiled at low speeds (cranking) it is
reccommended using additional running indication as e.g. D+ signal to prevent
overcranking of the engine. See the binary output Starter for additional
information.
CAUTION!
The starting procedure of gas engine may not work without the pickup. The pickup
must me always used for gas engines.
The setpoint adjusts the nominal gen-set speed.
The nominal speed is used:
As 100% for the overspeed protection (setpoint Overspeed)
For current speed calculation if it is calculated from generator frequency.
See the setpoint Gear teeth.
NOTE:
The setpoints Nominal RPM and system frequency (Nominal Freq + Nom frq
offset) must correspond to each other, i.e. if the engine speed is at nominal value
then the generator frequency must be at nominal value as well.
Group
Basic Settings
Range [units]
OFF, MAN, SEM, AUT, TEST [-]
Related FW
3.0
Description
This setpoint can be used to select the controller mode. It is equivalent to
selecting the mode by the buttons on the front panel. Currently active mode is
displayed on the controller main screen.
NOTE:
If any of the mode forcing inputs Remote OFF, Remote MAN, Remote AUT or
Remote TEST is active, then the currenly active mode can be different than the
mode selected by the setpoint (resp. panel buttons).
OFF
The GCB is opened and the engine is immediately stopped in this
mode without unloading and cooling. After that the controller is in
Not ready state and can not be started any way. The MCB is closed
permanently (MCB Opens On = GENRUN) or is open or closed
according to the mains is present or not (MCB Opens On =
MAINSFAIL).
MAN
The engine can be started and stopped manually using START and
STOP buttons (or external buttons wired to appropiate binary inputs)
in MAN mode. When the engine is running, GCB can be closed to a
dead bus or synchronizing can be started by the GCB button. Also
MCB can be closed and opened manually using the MCB button,
regardless the mains is present or not. No autostart is performed. No
reaction to the inputs Sys Start/Stop or Rem Start/Stop.
SEM
(IS-NT only) - The gen-set is started and stopped only manually
using START and STOP buttons (or external buttons wired to
appropiate binary inputs), however the the full start sequence up to
the moment when the engine is loaded is automatic as well as
unloading and stop sequence. The only case when the gen-set
starts automatically in SEMI is the start/stop initiated by the AMF
function.
AUT
This is fully automatic operation. The engine is started and stopped
by:
Binary input Rem Start/Stop (SPtM, SPI, COMBI)
Mains import dependent autostart function (peak start/stop)
(SPtM, SPI, Combi)
AMF function (SPtM, Combi)
Power management (MINT, Combi)
Buttons MCB, GCB, START, STOP including the appropriate binary
inputs for external buttons are not active. The full start sequence up
to the moment when the engine is loaded is automatic as well as
unloading and stop sequence.
WARNING!
If an red alarm is present and the gen-set is in AUT mode, it can
start by self after all red alarms becomes inactive and are
acknowledged!!! If you want to avoid this situation, adjust the
setpoint FltRes GoToMAN to the ENABLED position.
TEST
(SPtM, Combi) - the gen-set is started when the controller is
switched to TEST mode and remains running unloaded until the
mode is changed. If a mains failure occurs, the gen-set takes over
the load.
Group
Basic Settings
Range [units]
DISABLED,ENABLED [-]
Related FW
3.0
Force value
possible
YES
Description
This setpoint can be used to aviod possible unexpected automatic start of the
gen-set in AUT mode after the gen-set was stopped by a protection and then fault
reset was pressed.
ENABLED
The controller mode is automatically changed from any mode
except OFF to MAN if any red-level protection is
acknowledged by pressing of the fault reset.
DISABLED
The automatic change of the controller mode is disabled.
NOTE:
The function will not work if the current controller mode is forced by one of the
inputs Remote AUT or Remote TEST.
Group