Genconfig руководство на русском

8/20/2019 Genconfig 3.0 Reference Guide

1/153

Copyright © 2008 ComAp a.s.

ComAp a.s. Kundratka 2359/17, 180 00 Prague 8, Czech
Republic

Tel: +420 246 012 111, Fax: +420 266 316
647E-mail: [email protected], www.comap.cz

REFERENCE GUIDE

GenConf ig

Conf igu rat ion Tool for Gen-set con trol lers

To be used with ComAp co ntro l lers from fol lowing prod uct l
ines:

InteliGen-NT, InteliSys-NT, InteliMains-NT

SW version 3.0, June 2013

mailto:[email protected]://www.comap.cz/http://www.comap.cz/mailto:[email protected]

8/20/2019 Genconfig 3.0 Reference Guide

2/153

GenConfig, SW version 3.0, ©ComAp – June 2013
2Genconfig-3.0-Reference guide.pdf

Table of contents

Table of contents
…………………………………………………………………………………………………………………….
2 

Document information
……………………………………………………………………………………………………………..
4 

Clarification of notation
…………………………………………………………………………………………………………
4 General guidelines
…………………………………………………………………………………………………………………..
5 

What is GenConfig?
……………………………………………………………………………………………………………..
5 Installation
…………………………………………………………………………………………………………………………..
5 

GenConfig
directories………………………………………………………………………………………………………..
6 

PC Hardware requirements
………………………………………………………………………………………………..
6 Basic and advanced modes
…………………………………………………………………………………………………..
7 

 Archive versus Configuration
…………………………………………………………………………………………………
7 How to check GenConfig version?
…………………………………………………………………………………………
8 

Working with GenConfig
…………………………………………………………………………………………………………..
9 Typical workflow
…………………………………………………………………………………………………………………
10

Open archive from disk
……………………………………………………………………………………………………….
11 Read archive from controller
………………………………………………………………………………………………..
11

Write configuration to the controller
………………………………………………………………………………………
11 Save archive to disk
……………………………………………………………………………………………………………
12 Configuration import
……………………………………………………………………………………………………………
12 

 Archive compatibility overview
………………………………………………………………………………………….
12 Controller firmware upgrade
………………………………………………………………………………………………..
13 

Importing new firmware
……………………………………………………………………………………………………
13 Firmware upgrade (default configuration)
…………………………………………………………………………..
14 Firmware upgrade (existing configuration)
………………………………………………………………………….
14 Cloning
………………………………………………………………………………………………………………………….
16 Programming firmware into a non-responding controller
………………………………………………………
17 

Controller configuration
………………………………………………………………………………………………………….
18 Essential configuration steps
……………………………………………………………………………………………….
18 Optional configuration steps
………………………………………………………………………………………………..
19

Configuration locking
………………………………………………………………………………………………………….
19 Modules…………………………………………………………………………………………………………………………….
20

Controller
……………………………………………………………………………………………………………………….
22 ECU
………………………………………………………………………………………………………………………………
23 Extension modules
………………………………………………………………………………………………………….
25 Shared virtual extension modules
……………………………………………………………………………………..
26 

Inputs and Outputs
……………………………………………………………………………………………………………..
29 Binary inputs
…………………………………………………………………………………………………………………..
29 Binary outputs
………………………………………………………………………………………………………………..
31

 Analog inputs
………………………………………………………………………………………………………………….
33  Analog outputs
……………………………………………………………………………………………………………….
37 

Setpoints
…………………………………………………………………………………………………………………………..
42  Adjusting setpoints
………………………………………………………………………………………………………….
42

 Access groups and rights
…………………………………………………………………………………………………
43 Setpoint value forcing
………………………………………………………………………………………………………
44 Timer settings
…………………………………………………………………………………………………………………
45 

Commands
………………………………………………………………………………………………………………………..
47 Universal analog protections
……………………………………………………………………………………………….
48 History
………………………………………………………………………………………………………………………………
53 User sensors
……………………………………………………………………………………………………………………..
54 Languages and Translator
…………………………………………………………………………………………………..
56 

Create language
……………………………………………………………………………………………………………..
56 Translating the texts
………………………………………………………………………………………………………..
57 

PLC Editor
…………………………………………………………………………………………………………………………
60 

Working with the editor
…………………………………………………………………………………………………….
60 

PLC Editor toolbar
…………………………………………………………………………………………………………..
69 

PLC blocks
…………………………………………………………………………………………………………………….
70 

8/20/2019 Genconfig 3.0 Reference Guide

3/153

GenConfig, SW version 3.0, ©ComAp – June 2013
3Genconfig-3.0-Reference guide.pdf

InteliVision Screen Editor
…………………………………………………………………………………………………….
71 Logical binary inputs
…………………………………………………………………………………………………………..
72 Logical analog inputs
………………………………………………………………………………………………………….
73 Other configuration items
…………………………………………………………………………………………………….
74 User MODBUS
…………………………………………………………………………………………………………………..
75 

Menu description
…………………………………………………………………………………………………………………..
76 

File menu
………………………………………………………………………………………………………………………….
76 Open archive from disk
……………………………………………………………………………………………………
76 

Save archive to disk
………………………………………………………………………………………………………..
76 Recently saved archives
………………………………………………………………………………………………….
76 Close archive
………………………………………………………………………………………………………………….
76 Read archive from controller
…………………………………………………………………………………………….
76 Write configuration to the controller
…………………………………………………………………………………..
77 Consistency check
………………………………………………………………………………………………………….
77 Select configuration language
…………………………………………………………………………………………..
77 Controller/Archive info
……………………………………………………………………………………………………..
77 Configuration export
………………………………………………………………………………………………………..
77 Configuration import
………………………………………………………………………………………………………..
78 Configuration image
………………………………………………………………………………………………………..
78 

Manual edit of the controller screens layout
……………………………………………………………………….
78 Controller firmware upgrade
……………………………………………………………………………………………..
79 

Options menu
…………………………………………………………………………………………………………………….
86 GenConfig settings
………………………………………………………………………………………………………….
86 Connection settings
…………………………………………………………………………………………………………
86 Overwrite setpoints option
………………………………………………………………………………………………..
91 Clear history option
…………………………………………………………………………………………………………
92

Reset from Init
………………………………………………………………………………………………………………..
92 Save history to archive
…………………………………………………………………………………………………….
92 Check consistency before save
………………………………………………………………………………………..
92 Import firmware
………………………………………………………………………………………………………………
92 Dictionary manager
…………………………………………………………………………………………………………
92 ECU List
………………………………………………………………………………………………………………………..
93 

DDE Server
………………………………………………………………………………………………………………………….
94 DDE Server status
……………………………………………………………………………………………………………..
94 

DDE Server error messages
………………………………………………………………………………………………..
95  Appendix
………………………………………………………………………………………………………………………………
96 

PLC toolbar functions
………………………………………………………………………………………………………….
96 PLC blocks
………………………………………………………………………………………………………………………
101 

8/20/2019 Genconfig 3.0 Reference Guide

4/153

GenConfig, SW version 3.0, ©ComAp – June 2013
4Genconfig-3.0-Reference guide.pdf

Document information

GENCONFIG — REFERENCE GUIDE 

WRITTEN BY: J AN TOMANDL, J AKUB
S AFANDA ©2009-2013 COM AP A.S.KUNDRATKA
2359/17, PRAGUE 8, CZECH
REPUBLIC PHONE: +420246012111, FAX: +420266316647WEB: HTTP://WWW.COMAP.CZ, E-MAIL: [email protected] 

DOCUMENT HISTORY 

REVISION NUMBER  RELATED SW. VERSION 
DATE 

1 2.4 30.6.2009

2 2.4.1 30.9.2009

3 2.4.2 20.1.2010

4 2.5 20.12.2010

5 2.6 30.9.2010

6 3.0 3.6.2013

Clari f icat ion of no tat ion  

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 can cause a damage orunproper function of
the equipment if not performed correctly and may not be clear at
first sight.

WARNING! This type of paragraph indicates things,
procedures, adjustments etc. which need high level ofattention,
otherwise can cause personal injury or death.

http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/http://www.comap.cz/

8/20/2019 Genconfig 3.0 Reference Guide

5/153

GenConfig, SW version 3.0, ©ComAp – June 2013
5Genconfig-3.0-Reference guide.pdf

General guidelines

What is GenConf ig?

GenConfig is Windows 2000/XP/Vista/Windows 7 based software
which provides following mainfunctions:

Read/write configuration from/into the controller

Load configuration from file, save it to file

Modify the controller configuration 

Controller firmware firmware upgrade 

 Adjust initial values of  setpoints 

NOTE: GenConfig supports InteliGen-NT® ,
InteliSys-NT®  and
InteliMains-NT®  controllers.

Instal lat ion

Execute the «ComAp PC Suite» installation package (e.g.
IGS-NT-Install-Suite-2.4.exe) to installGenConfig, controller
firmware and other components into your computer. If there is
GenConfigalready installed, the installation program will offer an
upgrade (if your current version is older) or re-installation (if
your current version is identical).

If your current version is older, then it is recommended to
perform the upgrade, as the controllerfirmware, that you are about
to install, may not be compatible with older GenConfig version.

NOTE: The latest version of the standard branch controller
firmware will be installed together with theGenConfig. New
firmwares can be installed into the GenConfig also later using
import of the IGCpackages. See the chapter  Firmware
upgrade. 

8/20/2019 Genconfig 3.0 Reference Guide

6/153

GenConfig, SW version 3.0, ©ComAp – June 2013
6Genconfig-3.0-Reference guide.pdf

GenConfig directories

GENCONFIG DIRECTORY STRUCTURE 

PC Hardware requirementsGenConfig is based on Windows
2000/XP/Vista/Windows 7 platform. Use PC suitable for thisplatform.
There are no special requirements for the PC hardware. GenConfig
requires approx. 10Mbyte of harddisk free space.

8/20/2019 Genconfig 3.0 Reference Guide

7/153

GenConfig, SW version 3.0, ©ComAp – June 2013
7Genconfig-3.0-Reference guide.pdf

Basic and advanced modes

There are two program modes available. Basic mode will fit
to those people, who do not need specialfeatures of the controller
and like simpler program interface, less settings etc. The
Advanced mode is

then for those, who need all functions and features.

Go to Options -> Settings -> Display to select the
program mode. 

NOTE: Each archive contains information about GenConfig
mode last time used for modification of it. If anarchive has been
modified with GenConfig running in advanced mode, it is no more
possible to workwith this archive in basic mode, so next time you
will open this archive (from the controller or from file)and the
GenConfig is set to basic mode, it will switch automatically and
temporarily into advancedmode.

NOTE:  Archives from older firmware versions, which do
not support the basic mode, are opened as
advancedautomatically.

Archive versus Conf igurat ion

The table below explains meaning of the terms archive and
configuration and difference betweenthem.

Archive 

Package of data which is read out from a controller and can be
stored in a file.File extension for IGS-NT family archives is
«ant». An archive contains followingdata:

Configuration

Setpoints

Current operational values

History (performance log)

Default archives  are distributed together with the
controller firmware andcontain default configuration and default
adjustment of setpoints. These archivesdo not contain operational
values and history.

Configuration 

 A segment of data (stored in the controller flash memory),
which contains

properties of attached modules, inputs, outputs, protections,
languages, PLCand other information. The configuration can be
changed only with GenConfig.Normally the configuration needs to be
changed only to adapt the controller tothe site requirements prior
to or during commisioning. Obviously there is no needto change it
during the lifecycle of the gen-set.NOTE: Configuration is
contained in each archive!

8/20/2019 Genconfig 3.0 Reference Guide

8/153

GenConfig, SW version 3.0, ©ComAp – June 2013
8Genconfig-3.0-Reference guide.pdf

How to c heck GenConf ig vers ion?

Use Help-> About  to display current GenConfig
version window.

8/20/2019 Genconfig 3.0 Reference Guide

9/153

GenConfig, SW version 3.0, ©ComAp – June 2013
9Genconfig-3.0-Reference guide.pdf

Working with GenConfig

In principle GenConfig software should be used as an off-line
tool to create or change the

configuration and write it to the controller. Communication with
the controller is running only while theconfiguration is being read
and written to the controller. During this time you can see the
InteliDDEserver running.

NOTE:  Although GenConfig can be started directly from
Windows start menu, it is intended to be started fromIntel
iMonitor :

1. Start InteliMonitor and click on Connection -> Open to
activate the Open connection window.

2. Create new site/gen-set in the Open connection window if
required or select Quick connect to

controller if you do not want to work with sites.

3. Select desired type of connection and click to Open
connection button.

4. Once the connection is running (InteliMonitor status line is
green..) start GenConfig by clickingon Tools -> GenConfig.
GenConfig will read the configuration from the controller

automatically.

8/20/2019 Genconfig 3.0 Reference Guide

10/153

GenConfig, SW version 3.0, ©ComAp – June 2013
10Genconfig-3.0-Reference guide.pdf

Typical workf low

Following diagram shows typical workflow of using GenConfig:

TYPICAL WORKFLOW OF USING GENCONFIG 

Click on the particluar operation in the diagram above to get
more detailed information andinstructions.

8/20/2019 Genconfig 3.0 Reference Guide

11/153

GenConfig, SW version 3.0, ©ComAp – June 2013
11Genconfig-3.0-Reference guide.pdf

Open archive from d isk

Click to icon or select File -> Open to activate a dialog for
opening an archive.

The default archives are located in shared documents
folder: C:Documents and SettingsAllUsersDocumentsComAp PC
SuiteGenConfigArchivesDefault 

The user created archives are intended to be in shared documents
folder as well: C:Documents

and SettingsAll UsersDocumentsComAp PC
SuiteGenConfigArchives, however

they can be read from anywhere in the computer.

Read archive from con trol ler

Click to icon or use File -> Read from controller to read out
the archive from a connected

controller.

CAUTION! Make sure that Connection settings are
adjusted properly prior to reading the archive. Wrongconnection
settings may cause you will read out the archive from different
controller than intended.

NOTE: If GenConfig is started from InteliMonitor, then the
connections settings are adjusted by InteliMonitorand the archive
is read out from the controller automatically.

Write con f igurat ion to the contro l ler

Click to icon or use File -> Write to controller to write the
configuration into the connected

controller. Administrator  is prompted to log-in to
complete this operation. Following options arerelated to writing
the configuration:

Overwrite setpoints 

Clear history 

CAUTION! Make sure that Connection settings are
adjusted properly prior to writing the configuration.
Wrongconnection settings may cause you will write the configuration
into different controller than intended.This situation might occur
especially if an ethernet connection is used.

NOTE: If GenConfig is started from InteliMonitor, then the
connections settings are adjusted by InteliMonitorand do not
require any user attention.

8/20/2019 Genconfig 3.0 Reference Guide

12/153

GenConfig, SW version 3.0, ©ComAp – June 2013
12Genconfig-3.0-Reference guide.pdf

Save archive to disk

Click to icon or use File -> Save to save the archive to
disk. If a filename is not assigned to the

archive yet, you will be asked for it, otherwise the archive
will be saved under the assigned filename.

Use File -> Save As to save the archive under different
filename.

Following options are related to saving the archive:

Save history to archive 

Check consistency before save 

Conf igurat ion impo rt

If you want to use a configuration from an archive, which is not
directly compatible with your firmware,the configuration import
must be used for importing of the configuration from the original
archive intothe compatible default archive according to your
firmware.

1. Open the target default archive into which you want to import
the configuration.

2. Go to menu File -> Import configuration wizard

3. Select the source archive and press Next button.

4. The following window shows differencies between the
configurations. You can not make anymodifications here.

5. Press Next button to execute the import function.

6. When the import is finished, press Next button to see the
information window with the results.

Here you will see possible warnings or errors that occurred
during the import.

7. Press OK button to finish the import.

CAUTION! Check the new configuration, especially if some
warnings or errors occurred. It may need manualcorrections. Manual
corrections are required if the configuration was imported from
different firmwarebranch or different application type, as certain
functions may not be present in the target firmware.

Archive compatibility overviewCompatible archives:

 Archives from different releases of the same firmware and
major + minor version (e.g. IG-NT-2.3 x IG-NT-2.3.1 x
IG-NT-2.3.2)

Incompatible archives:

 Archives from different major or minor versions of the
same firmware branch (IG-NT-2.2 x IG-NT-2.3)

 Archives from different firmware branches

 Archives from different controller types (IG-NT x
IS-NT)

8/20/2019 Genconfig 3.0 Reference Guide

13/153

GenConfig, SW version 3.0, ©ComAp – June 2013
13Genconfig-3.0-Reference guide.pdf

Contro l ler f irmw are upg rade

 Although the controllers are supplied always with latest
version of standard firmware it may be neededin some cases to
upgrade the firmware to newer version. Also customized firmware
branches requirethe controller firmware to be reprogrammed.

NOTE: Administrator  is prompted to log-in prior
to programming of firmware and/or configuration into
thecontroller.

Importing new firmware

Go to Options -> Import firmware menu to import new firmware
(obtained from e-mail, ComAp

web site etc.) into the GenConfig.

«Import firmware» window appears. Click on icon and select the
IGC file you want import.

You will see the contents of the IGC file in the lower part of
the window.

You can specify files for import by checking/unchecking box for
each file.

Select owerwriting method

Press «OK» button to import the firmware into the GenConfig.

8/20/2019 Genconfig 3.0 Reference Guide

14/153

GenConfig, SW version 3.0, ©ComAp – June 2013
14Genconfig-3.0-Reference guide.pdf

Firmware upgrade (default configuration)NOTE: This function
is intended for programming of firmware into new controllers or for
programming ofdifferent firmware branch. If you want to upgrade
firmware of the same branch in a controller which isalready in
operation, use the Firmware upgrade (existing
configuration) function.

The Firmware upgrade (default configuration) function will
program selected firmware into your

controller. After programming the controller will contain
default archive (SPtM application in case of

standard branch) which obviously needs to be modified according
to application requirements. See thechapter  Controller
configuration for information how to modify the
configuration.

Select required firmware from the list and press OK button. If
you do not see required firmware in the

list, you have to import it first.

CAUTION! Do not programm IS-NT firmware into IG-NT
controller and vice versa!

Firmware upgrade (existing configuration)NOTE: This
function is intended for upgrading firmware of the same branch in
an controller which is already inoperation. If you want to program
firmware into a new controller or program firmware of a
different

branch, use the Firmware upgrade (default
configuration) function.

The Firmware upgrade (existing configuration) function
automatically performs following operations:

1. An archive is downloaded from the controller and saved into a
file.2. A window with available firmwares and default archives
appear. The requested new firmware

is to be selected in this window and if the new firmware is not
compatible with the originalarchive then also default archive for
importing of the configuration must be selected in thiswindow as
well.

8/20/2019 Genconfig 3.0 Reference Guide

15/153

GenConfig, SW version 3.0, ©ComAp – June 2013
15Genconfig-3.0-Reference guide.pdf

INCOMPATIBLE FIRMWARE SELECTED 

COMPATIBLE FIRMWARE SELECTED 

3. If the new firmware is not compatible with the original
archive, then import of original

configuration into default configuration of the programmed
firmware is performed.4. The selected firmware is programmed into
the controller.5. The configuration is programmed into the
controller.6. Setpoints from the archive are written into the
controller.

NOTE: This function should reduce the effort needed for
upgrading the firmware in a controller that is beeingused at a
site. However, new firmwares can bring new or modified
functionality that may requirefurther user attention. Please always
read carefuly the New Features  document of the
firmware. 

8/20/2019 Genconfig 3.0 Reference Guide

16/153

GenConfig, SW version 3.0, ©ComAp – June 2013
16Genconfig-3.0-Reference guide.pdf

CloningUse cloning function to create an identical copy of one
controller to another one. This function canhelp you in following
situations:

Replacing defective controller with another controller on one
site.

Production of more identical gen-sets.

The procedure consists of following steps:

1. Save for later cloning 2. Create clone 

Contents of a clone:

Clone description file

Controller archiveController firmware according to the
archive

External display firmwares (optional, for terminals connected to
the dedicated terminal RS485line)

Graphic fonts (optional, only for controllers/terminals that
support graphic fonts)

Save for later cloning

Save for later clonning (controller only) function will save
currently opened configuration including all

changes that were made since opening it from disk or reading
from controller. This option does notsave firmwares of external
terminals and graphic fonts into the clone.

Save for later clonning (controller and displays) function
connects automatically to the controller,

reads the configuration from it and saves it into the clone.
Firmwares of external terminals connectedvia the dedicated RS485
bus and graphic fonts are saved into the clone as well.

NOTE: If you get an error message «Firmware XXXX was not
found» instead of opening the «Save clone»window, it means you do
not have on your disk the firmware, that is present in the
controller, so theclone can’t be saved. In such a case the proper
firmware has to be imported into the GenConfig.

Create clone

Use the function Create clone… to make the connected
controller identical (firmware, configuration,

setpoints, fonts..) with the original controller from which was
the clone saved. The function is intendedto be used either for the
purpose of complete backup of a site in case the controller or
terminal willneed to be replaced or for preparing of more identical
controllers.

1. Connect the target controller (and displays if needed) to the
PC.2. Start GenConfig and adjust properly connection
settings. 

3. Go to menu File -> Create clone… and then select
required clone.

4. Press OK to program the selected clone into the
controller.

Import/Export clone

Press the to export selected saved clone into one file for the
purpose of archivation, sending

per e-mail etc. Press the to import previously saved clone into
GenConfig.

8/20/2019 Genconfig 3.0 Reference Guide

17/153

GenConfig, SW version 3.0, ©ComAp – June 2013
17Genconfig-3.0-Reference guide.pdf

Programming firmware into a non-responding controllerIf the
controller does not contain valid firmware a new firmware can’t be
programmed by standard way.This situation can occur if the
connection between PC and the controller was interrupted
duringprevious firmware upgrade. In such a case the controller has
blank display and does not communicatewith the PC. The boot-jumper
must be used to get a valid firmware into the controller.

1. Disconnect power supply from the controller and close the
boot-jumper. See the controllermanual for details about boot-jumper
location.

2. Connect communication cable (appropriate type according to
the module used) between thecontroller and PC.

3. Select direct connection to controller address 1.

4. Go to menu Controller -> Programming and clonning ->
Firmware upgrade, select

appropriate firmware and press OK button.

5. Follow instructions given by a message appeared and finally
press OK button.

6. Another message will appear when programming is finished.
Follow instructions given there.

8/20/2019 Genconfig 3.0 Reference Guide

18/153

GenConfig, SW version 3.0, ©ComAp – June 2013
18Genconfig-3.0-Reference guide.pdf

Controller configuration

One of the key features of the controller is high level of
adaptability of the system to the needs ofevery particular
application. The way, how to achieve this, is the
configuration.

The firmware contains large number of logical  inputs
and outputs needed for all necessary functionsavailable in the
firmware. But not all functions are required at the same time
 on the same gen-setand also the controller hardware does not
have so many input and output terminals. One of mainfunctions of
the configuration is mapping of «logical» firmware inputs and
outputs to the»physical» hardware inputs and outputs.

PRINCIPLE OF BINARY INPUTS AND OUTPUTS CONFIGURATION 

Essent ial con f igurat ion steps

Following configuration steps must be performed at most of
applications:

1. Open default archive of the required application type
according to your firmware version andbranch

2. Define modules which are contained in the system
(i.e. engine ECU and/or extensionmodules)

3. Assign functions and/or protections to physical
inputs (input terminals), assign functions ofphysical outputs
(output terminals)

4. Assign access rights to setpoints, adjust initial
values of setpoints

8/20/2019 Genconfig 3.0 Reference Guide

19/153

GenConfig, SW version 3.0, ©ComAp – June 2013
19Genconfig-3.0-Reference guide.pdf

Opt ional conf igurat ion steps

Following configuration steps may not be needed to go through at
less complex applications:

1. Assign access rights to remote gen-set
control commands 

2. Create additional protections to any analog value3.
Modify content of the history header  4. Create
user-defined analog sensor conversion characteristics 5.
Add/Remove controller  languages, translate the
texts6. Create internal connections from logical outputs
to logical inputs 7. Create PLC program for
control of additional technology

NOTE: There are two modes of GenConfig operation — Basic
mode and Advanced mode. Some features arehidden in the basic mode.
Learn more in the chapter  Basic and advanced
modes. 

Conf igurat ion locking

It is possible to lock the archive against unauthorized usage.
If the archive is locked, the user 0password (administarator
password) is required to open and display the archive in
GenConfig.

NOTE: The configuration lock works only if the
configuration has been downloaded from the
controller  and requires password that was vaild in the
moment of downloading. The configuration lock is notactive in
configurations derived directly from default archives that were not
uploaded into the controlleryet.

8/20/2019 Genconfig 3.0 Reference Guide

20/153

GenConfig, SW version 3.0, ©ComAp – June 2013
20Genconfig-3.0-Reference guide.pdf

Modules

Modules

This is the main tab where the work with configuration should be
started. It is to define here thestructure of the system, i.e.
controller type, connected extension modules, ECU type and
other.

The left part of the tab contains a tree of all modules
that are available.

The right part shows currently configured modules and their
properties.

8/20/2019 Genconfig 3.0 Reference Guide

21/153

GenConfig, SW version 3.0, ©ComAp – June 2013
21Genconfig-3.0-Reference guide.pdf

MODULES TAB 

Follow this procedure to prepare a customized configuration from
a default one:

1. Select type of controller you are using in the left part and
press Insert button to add the

controller into your system. Note, that you can not switch
between IG-NT and IS-NTcontrollers, for this case you have to open
different archive, where IG-NT or IS-NT is pre-configured.

2. If you use an EFI engine equipped with an ECU, select desired
type from the left tree and

press Insert button to add the ECU to your system.

3. Select the ECU in the right tree and adjust it’s
properties:

ECU size adjusts the amount of inputs and outputs, that will be
available for

configuration of ECU values in the I/O tab.

Protection upon module failure selects which alarm type will be
issued when the ECU

stops communicating with the controller.

Use Display data as item to select, whether the analog values
read from ECU will be

displayed as bargraphs or as numbers only.4. Select appropriate
extension modules from the left tree and add them one by one into
your

system.5. Select each configured extension module in the right
tree and adjust properties of it:

Module index must match with the address setting on the module.
The picture at the

bottom of the window shows details about how to set the
appropriate addressaccording to the index. Normally it is not
necessary to change the module index, as it

is set to a free index automatically, when the module has been
inserted.

8/20/2019 Genconfig 3.0 Reference Guide

22/153

GenConfig, SW version 3.0, ©ComAp – June 2013
22Genconfig-3.0-Reference guide.pdf

NOTE: 

Some modules share physical CAN addresses and this can cause
using one type ofmodule with specific index will disable using
another module with specific index.Example: if AIN8 modules with
indexes 1 — 4 are configured, it will be not possible toconfigure
IGS-PTM module, as the IGS-PTM index 1 – 4 shares the CAN
addresses

with AIN8 modules. In such a case the solution is to configure
AIN8 modules toindexes 2-5 and the IGS-PTM to the index 1.

Protection upon module failure selects which alarm type will be
issued when the

module stops communicating with the controller.

Use Display data as item to select, whether the analog values
read from the module

will be displayed as bargraphs or as numbers only.

ControllerBelow version 2.5 of standard firmware

The controller type is fixedly configured in the archive and it
can not be changed. There are differentfirmware files and default
archives for IG-NT and for IS-NT controllers.

Changing of the controller type is possible only from IG-NT to
IG-EE and vice versa.

Version 2.5 of standard firmware and above

There are groups of compatible hardware modifications of the
controller and separate firmware andarchive for each group, which
works with each controller modification from the particular group.
Thegroups are following:

COMPATIBLE CONTROLLER MODIFICATIONS  FIRMWARE FILE 
ARCHIVE FILE 

IG-NT, IG-NTC, IG-EE(C), IG-NT-BB, IG-NTC-BB ig-nt-x.y.z.mhx
ig-appl-x.y.ant

IS-NT, IS-NTC-BB is-nt-x.y.z.mhx is-appl-x.y.ant

IM-NT, IM-NT-BB, IM-NTC-BB im-nt-x.y.z.mhx im-appl-x.y.ant

It is possible to change the controller modification to any of
the compatible modifications. GenConfigwill then show and hide
certain adjustments and configuration items according to what does
theselected modification support and what doesn’t.

NOTE: Default archives for the each group are configured to
IG-NT, IS-NT or IM-NT respectively. However, toget access to all
features and functions that are supported by your controller you
have to change thecontroller modification in the configuration to
match the target controller.

EXAMPLE: The default IG-NT-MINT archive is switched to
IG-NT modification, which does not support high sideswitches at the
outputs. If you have IG-NT-BB hardware, which supports HSS, you
have to change the

modification to IG-NT-BB and then you will be able to select the
HSS mode for controller outputs.

8/20/2019 Genconfig 3.0 Reference Guide

23/153

GenConfig, SW version 3.0, ©ComAp – June 2013
23Genconfig-3.0-Reference guide.pdf

NOTE: If the modification is not properly selected you will
have access to configuration of functions which willnot work in the
target controller or vice versa. However, the rest of functions,
which are supported byall modifications, will work normally.

1. List of compatible controller modifications2. Press this
button to change the modification to the highlighted one3.
Currently configured modification4. Thumbnail of the highlighted
modification5. Selection of output type (high side/low side)

ECUSelect ECU type according to your EFI engine and put it into
your configuration. ECU  sections willappear in the I/O
tab, where inputs and output of the ECU are to be configured.

Essential required configuration is done automatically when
the ECU is configured. Missingrequired item of configuration (e.g.
logical analog input engine speed) is indicated by red color.

EXAMPLE: If an ECU is configured the engine speed is taken
from the ECU instead of a magnetic pickup. That

means the logical analog input RPM Pickup must be configured
onto an ECU analog input where

Engine speed  is configured as source ECU value.

8/20/2019 Genconfig 3.0 Reference Guide

24/153

GenConfig, SW version 3.0, ©ComAp – June 2013
24Genconfig-3.0-Reference guide.pdf

MISSING REQUIRED ECU CONFIGURATION ITEM 

CORRECTLY CONFIGURED ECU ITEM 

NOTE: If the version of the particular ESF/ESC file
previously used for configuration of the ECU does notmatch the
current ESF/ESC file version, the engine name in the statusbar is
displayed in red. If anychange of the ECU I/O configuration is
needed, the ECU must be removed and configuredagain! 

8/20/2019 Genconfig 3.0 Reference Guide

25/153

GenConfig, SW version 3.0, ©ComAp – June 2013
25Genconfig-3.0-Reference guide.pdf

ESF/ESC FILE VERSION MISMATCH INDICATION 

Extension modules

Standard extensionThe Standard extension group contains all
«physical» extension modules, which can be connected to

the CAN1 bus.

Virtual extension

The Virtual extension group contains modules that exist only in
a form of software modules inside the

firmware. Inputs and outputs of these modules can be
interconnected with other modules only bymeans of logical
connections if the configuration.

VPIO module 

Shared modules 

ECU bridges

ECU bridges (I-CB modules) are available for selected EFI engine
types that support neither SAEJ1939 nor MODBUS protocol. An ECU
bridge is connected to CAN1 bus of the controller. The moduleacts
from the controller point of view as an extension module containing
certain number of groups ofanalog and binary inputs and
outputs.

NOTE: The configuration of I-CB module in the controller
must correspond to the configuration of the I-CBitself.

NOTE: The I-CB module firmware must correspond to the
specific engine type.

8/20/2019 Genconfig 3.0 Reference Guide

26/153

GenConfig, SW version 3.0, ©ComAp – June 2013
26Genconfig-3.0-Reference guide.pdf

How to configure an I-CB module:

1. Check whether the I-CB module contains appropriate firmware
according to your engine(ECU) type. The original firmware type and
version is indicated on the sticker at the I-CBmodule.

2. In ICBEdit open the default I-CB configuration according to
your engine type, modify it if

needed, and write it into the I-CB.3. Use ICBEdit menu File
-> Export… to export the I-CB configuration into a text
file.

4. In GenConfig put an I-CB of appropriate type into your
configuration and then go to the I/O

Tab and configure inputs and outputs. 

NOTE:  Always use electronic sensor  type
for analog inputs at ECU bridges.

Generic extension

There is also the I-CB (generic) available, which is not
prepared for any specific engine and by default

does not contain any inputs and outputs. Groups of inputs and
outputs must be configured then

manually using the generic modules from the Generic extension
group.

Shared virtual extension modulesShared virtual modules are
intended for transferring of binary and analog signals from one
sourcecontroller to other controllers over the CAN2 bus.

PRINCIPLE OF SHARED MODULES 

SHBOUT

The SHBOUT module is a block of 8 virtual binary outputs. The
signals configured on the outputs arebroadcasted over the CAN2 bus
and can be received in other connected controllers
using SHBIN module of the same index as the SHBOUT
has.

CAUTION! Only one controller containing SHBOUT module with
one particular index is allowed within a site.

8/20/2019 Genconfig 3.0 Reference Guide

27/153

GenConfig, SW version 3.0, ©ComAp – June 2013
27Genconfig-3.0-Reference guide.pdf

SHBIN

The SHBIN module is a block of 8 virtual binary inputs intended
for receiving of binary signals that arebroadcasted
by SHBOUT module.

NOTE: 

The receiving SHBIN module must have identical module index as
the broadcasting one.

SHAOUT

The SHAIN module is a block of 4 virtual analog outputs. The
signals configured on the outputs arebroadcasted over the CAN2 bus
and can be received in other connected controllers
using SHAIN module of the same index as the SHAOUT
has.

CAUTION! Only one controller containing SHAOUT module with
one particular index is allowed within a site.

SHAIN

The SHAIN module is a block of 4 virtual analog inputs intended
for receiving of analog signals that

are broadcasted by SHAOUT module.

NOTE: The receiving SHAIN module must have identical module
index as the broadcasting one.

NOTE:  Always use electronic sensor  type
for analog inputs of the SHAIN modules.

DISTBOUT

The DISTBOUT module is a block of 8 virtual binary outputs. The
signals configured on the outputsare broadcasted over the CAN2 bus
and can be received in other connected controllers
usingDISTBIN module of the same index as the DISTBOUT has.
DISTBOUT has always module index

equal to CAN address of controller.

NOTE: Only one DISTBOUT module per controller can be
configured.

NOTE: DISTBOUT module is available only in following
controllers:

1. IG-NT(C)-BB controllers with firmware 3.0 and higher and
LSM-PMS dongle installed. Moduleis not available in IG-NT GC
controller.

2. IS-NT controllers with firmware 3.0 and higher and LSM-PMS
dongle installed.3. IM-NT controllers with firmware 3.0 and higher
(no dongle required)

DISTBIN

The DISTBIN module is a block of 8 virtual binary inputs
intended for receiving of binary signals thatare broadcasted
by DISTBOUT module.

NOTE: The receiving DISTBIN module must have identical
module index as the broadcasting one.

NOTE: Up to 32 DISTBIN modules with unique index (1-32) can
be configured per controller.

8/20/2019 Genconfig 3.0 Reference Guide

28/153

GenConfig, SW version 3.0, ©ComAp – June 2013
28Genconfig-3.0-Reference guide.pdf

NOTE: DISTBIN module is available only in following
controllers:

1. IG-NT(C)-BB controllers with firmware 3.0 and higher and
LSM-PMS dongle installed. Moduleis not available in IG-NT GC
controller.

2. IS-NT controllers with firmware 3.0 and higher and LSM-PMS
dongle installed.

3. IM-NT controllers with firmware 3.0 and higher (no dongle
required)

8/20/2019 Genconfig 3.0 Reference Guide

29/153

GenConfig, SW version 3.0, ©ComAp – June 2013
29Genconfig-3.0-Reference guide.pdf

Inputs and Outputs

I/O

Configuration of inputs and outputs means assigning
functions and/or alarms to physical (or virtual)input terminals and
assigning functions to physical output terminals.

Binary inputs 

Binary outputs 

 Analog inputs 

 Analog outputs 

Binary inputs A binary input can be used as
functional and/or alarm (protection) input.

Configure binary functionFollow the procedure below to configure
a function to an input:

1. In the left tree select the physical input you wish to
configure.2. Click «Function» in the middle column.3. Select
requested logical input (function) in the right list. It is
possible to assign more functions

to one physical input.

4. Go back to the middle column and fill-in a suitable name into
the Name field. The length of the

name is limited to 14 characters.

CONFIGURING A BINARY INPUT AS FUNCTION 

8/20/2019 Genconfig 3.0 Reference Guide

30/153

GenConfig, SW version 3.0, ©ComAp – June 2013
30Genconfig-3.0-Reference guide.pdf

Configure binary protection

Follow the procedure below to configure an alarm to an
input:

1. In the left tree select the physical input you wish to
configure.2. Click «Protection» in the middle column.

3. Fill-in a suitable name into the Name field. The length of
the name is limited to 14 characters.

4. Select requested protection (alarm) type.5. Select whether
the alarm has to activate when the contact is closed (binary input
is energized)

or open (binary input is deenergized).6. Select a period when
the alarm has to be evaluated — i.e. always, at running engine
only, while

GCB is closed only etc..7. Select evaluation delay. Standard
delay is 500ms fixed, which should fit to most applications,

however there are several adjustable delays which can be
assigned to a binary input insteadof fixed delay.

CONFIGURING A BINARY INPUT AS ALARM (PROTECTION) 

ECU binary inputs

Most of ECU’s provide several binary signals, those can be
handled as binary inputs in the controller.»ECU» node will appear
in the section «binary inputs» of the left tree if an ECU is
configured. The nodewill contain a set of virtual binary inputs.
These inputs work the same way as physical terminals exceptthat
they require assign a source ECU value before configuration of a
function and or protection.

CONFIGURING SOURCE VALUE FOR AN ECU BINARY INPUT

NOTE: Essential required configuration of ECU inputs and
outputs is done automatically when the ECU isconfigured. See
also ECU subchapter in the modules chapter.

8/20/2019 Genconfig 3.0 Reference Guide

31/153

GenConfig, SW version 3.0, ©ComAp – June 2013
31Genconfig-3.0-Reference guide.pdf

Binary outputs A binary output terminal can be driven by
following sources:

Logical binary outputs (control outputs from the program
loop)

Informative binary values

 Alarm mirrors (analog, binary or built-in alarms)Binary
inputs mirrors (physical, virtual)

NOTE: The binary outputs of IG-NT-BB, IG-NTC-BB, IS-NTC-BB,
IM-NT-BB and IM-NTC-BB controllermodifications can be switched to
High side (HSS) or low side (LSS) mode. See the
chapter  Controller . 

Configure control output

Follow the procedure below to configure a control output:

1. In the left tree select the physical output you wish to
configure.2. Select requested logical output (control output) from
the «Log Bout» node in the right tree.3. The name of the physical
output is taken automatically from the assigned logical output. It
can

be modified in the middle column. The length of the name is
limited to 14 characters.4. Function of the physical output can by
inverted.

CONFIGURING A BINARY OUTPUT AS CONTROL 

Configure alarm mirror output

Follow the procedure below to configure an alarm mirror
output:

1. In the left tree select the physical output you wish to
configure.

2. Select requested alarm mirror from the Ana protections,
Bin protections or Prg States node inthe right tree.

 Ana protections contain all alarms assigned to analog
inputs. In the Level field it is

possible to select what alarms levels will be mirrored into the
output.

Bin protections contain all alarms assigned to binary
inputs.

Prg states contain all built-in alarms including alarms
generated by PLC blocks force

 protect .3. The name of the physical output is taken
automatically from the assigned alarm. It can be

modified in the middle column. The length of the name is limited
to 14 characters.4. Function of the physical output can by
inverted.

8/20/2019 Genconfig 3.0 Reference Guide

32/153

GenConfig, SW version 3.0, ©ComAp – June 2013
32Genconfig-3.0-Reference guide.pdf

CONFIGURING A BINARY OUTPUT AS ALARM MIRROR 

ECU binary outputs

Some of ECU’s receive a couple of binary signals, those can be
sent from the controller and handledas binary outputs. «ECU» node
will appear in the section «Binary outputs» of the left tree if an
ECU isconfigured. The node will contain a set of virtual binary
outputs. These outputs work the same way asphysical terminals
except that they require assign a destination ECU value before
configuration of asource function.

CONFIGURING DESTINATION ECU VALUE FOR AN ECU BINARY
OUTPUT 

NOTE: Essential required configuration of ECU inputs and
outputs is done automatically when the ECU isconfigured. See
also ECU subchapter in the modules chapter.

8/20/2019 Genconfig 3.0 Reference Guide

33/153

GenConfig, SW version 3.0, ©ComAp – June 2013
33Genconfig-3.0-Reference guide.pdf

Analog inputs An analog input can be used as
functional and/or alarm (protection) input. Follow the
procedure

below to configure analog input:

 ANALOG INPUT CONFIGURATION STEPS 

1. Select the desired analog input.2. Enter suitable name for
the input.3. Select physical dimension of the measured value. The
proper physical dimension depends on

sensor type.4. Select sensor type. There are three kinds of
sensors:

General sensors as for example 0-10V can measure many
different physical values withdifferent ranges. These sensors
provide electrical value (e.g. volts) which needs an
additionalconversion to physical value. Example of such a sensor is
linear fuel level sensor 0-50.0gal/0-

10V. The conversion is linear and the conversion ratio is to be
adjusted by the Sensor range

item. The range adjusts physical value representing the upper
value of the sensor electricalrange (e.g. 50.0gal at
10V). 

SENSOR RANGE SETTINGS

8/20/2019 Genconfig 3.0 Reference Guide

34/153

GenConfig, SW version 3.0, ©ComAp – June 2013
34Genconfig-3.0-Reference guide.pdf

Set Bargraph 0% and Bargraph100% parameters to define low and
high range on displayed

bargraph scale (for example if you want to have bargraph scale
limited to 40Hz…70Hz).

B ARGRAPH: B ARGRAPH 0%=40, BARGRAPH
100%=70 

Dedicated sensors as PT100 or Thermocouples convert
directly to the physical value and donot require range and
resolution adjustment.

Electronic sensor  is used for all virtual analog
inputs. This sensor does not perform anyconversion and leaves the
analog input value as it is received from the virtual
periphery.

NOTE: 

If you haven’t found your sensor in the list of predefined
sensors, then see the chapter  Usersensors for
information how to create an user-defined sensor.

5. Tick the Function checkbox if the analog input will be used
for a control purpose, e.g. for

control of the engine warming function.6. if (5) is ticked then
select the requested function for the input.

7. Tick the Protection checkbox if a protection (alarm) will be
assigned to the analog input.

8. If (7) is ticked then configure the protection:

8/20/2019 Genconfig 3.0 Reference Guide

35/153

GenConfig, SW version 3.0, ©ComAp – June 2013
35Genconfig-3.0-Reference guide.pdf

 ANALOG INPUT PROTECTION CONFIGURATION STEPS 

NOTE: 

See the controller reference guide for information about how
protections work.

1. Select protection type for the yellow (pre-critical)
level.

2. Select protection type for the red (critical) level if
needed.3. Select whether the protection will activate when the
analog value gets above the limit

or below the limit. Selecting the …+Fls item will cause
that the configured redprotection will occur also when sensor
failure is detected at the appropriate input. Ifthere is no red
protection configured, then the yellow one will occur.

4. Select how the protection will be recorded into the history
log. Once means that only

first occurence of the protection will be recorded until fault
reset is pressed, Always

means all occurences will be recorded.5. Select time period
while the protection will be enabled. E.g. Oil pressure must
be

enabled at running engine only.6. Rename limit and delay
setpoints and adjust their default values. The setpoints can be

readjusted any time later from InteliMonitor or directly from
the controller front panel.7. Select if sensor fail will be
evaluated. Sensor fail is an alarm, which is issued if the

measured quantity at the particular input is out of range
allowed for the assignedsensor. This occurs if the sensor cables
are interrupted or shorted or the the sensoritself is damaged.

NOTE: 

This independent option is available in the controller firmware
2.5 and above. In theprevious versions the sensor fail option was
selected automatically whenever aprotection of any level is
assigned to the input

8/20/2019 Genconfig 3.0 Reference Guide

36/153

GenConfig, SW version 3.0, ©ComAp – June 2013
36Genconfig-3.0-Reference guide.pdf

NOTE: 

The feature is intended for ECU analog inputs.

CAUTION! 

It is not reccomended to configure classic analog input with a
protection and withoutsensor fail option.

ECU analog inputs

Most of ECU’s provide analog values, that can be handled as
analog inputs in the controller. «ECU»node will appear in the
section «analog inputs» of the left tree if an ECU is configured.
The node willcontain a set of virtual analog inputs. These inputs
work the same way as physical inputs except that

they require to assign a source ECU value before configuration
of a function and or protection.

CONFIGURING SOURCE VALUE FOR AN

ECU ANALOG INPUT

The additional configuration item (compared to a classic analog
input) is the first line labeled «ECUvalue» in the middle column.
If you click on it (2), you will see a list of available source
values providedby the particular ECU unit. Then you have to select
one of them as the source for this particularanalog input (3). This
assignment is equivalent to connecting a physical sensor to a
physical analoginput. Then you can continue configuring function
and/or protection (4,5) in the same way as withclassic analog
inputs.

NOTE: Essential required configuration of ECU inputs and
outputs is done automatically when the ECU isconfigured. See
also ECU subchapter in the modules chapter.

8/20/2019 Genconfig 3.0 Reference Guide

37/153

GenConfig, SW version 3.0, ©ComAp – June 2013
37Genconfig-3.0-Reference guide.pdf

Cyliders configuration wizard

The wizard makes the configuration of cylinder temperature
inputs easier. It helps to configuremeasurement and 2-level
protection with common setpoints for up to 32 cylinder temperature
sensors.

Go to the I/O tab, then select the analog input where the first
cylinder is connected and press the

button to start the wizard.

Analog outputs An analog output can be used for driving of
a panel meter , for conventional interfacing of a
higher-level control/monitoring system or for sending
data into peripherial modules such
as ECU, SHAOUT etc. Follow the procedure below to
configure analog output:

 ANALOG OUTPUT CONFIGURATION STEPS 

1. Select the desired analog output.2. Select the analog value
which will be sent to the output.

3. Select the Convert item:

 Yes — The configured value will be transformed
linearly to the output range of therespective output, e.g. 0mV —
10000mV for physical outputs. The output range is 0 —

10000mV even if in fact the appropriate physical output is
0-20mA. In that case10000mV corresponds to 20mA.

No — The configured value will be sent to the output
directly without anytransformation. The only modification possible
is «normalizing», i.e. decimal resolutionchange. This setting is
used mostly for ECU and SHAOUT outputs.

4. If Convert is used, then press … to open the limits
calculator  which is used for defining of the

transformation function.

5. If Convert is not used, the Normalize function can be used to
change the decimal resolution

of the value before sending it to the output. I.e. the generator
voltage value, which is 230 inthe controller, can be sent as 230.0
(2300).

ECU analog outputs

ECU analog outputs are used to send analog values such as
requested speed into the ECU. Theconfiguration is similar as by
other analog outputs with the difference that:

The Convert must be set to NO in most cases.

There is an additional item ECU value. Click on it to select ECU
value where the analog

output has to be sent. List of available ECU values for the
configured ECU type will bedisplayed in the right column after
clicking on the ECU value item.

8/20/2019 Genconfig 3.0 Reference Guide

38/153

GenConfig, SW version 3.0, ©ComAp – June 2013
38Genconfig-3.0-Reference guide.pdf

Limits calculator

The calculator is used for defining of the linear transformation
function if Convert = YES. Enter two

points of the configured value and appropriate output level for
each point.

TRANSFORMATION OF 0-150KW TO
0-10V RESP. 0-20M A 

TRANSFORMATION OF 0-150KW TO 4-20M A 

 Analog output configuration examples

EXAMPLE:  Analog gauge 0-20mA showing oil pressure 0-6
Bar, driven by an analog output. The source value isconfigured to
the analog input «Oil press» and limits are 0;0 and 6.0;10000, what
means the analog

output will give 0mA at oil pressure 0 Bar and 20mA at 6Bar.

CONFIGURATION 

PROPERTY  VALUE 

SOURCE  Oil Press

CONVERT  Yes

LIMITS  [0.0;0]..[6.0;10000]

C ALCULATOR POINTS 

SOURCE  OUTPUT 

LOW  0.0 0

HIGH  6.0 10000

8/20/2019 Genconfig 3.0 Reference Guide

39/153

GenConfig, SW version 3.0, ©ComAp – June 2013
39Genconfig-3.0-Reference guide.pdf

EXAMPLE:  Analog interface of Genset voltage to a PLC
via 4-20mA signal with [email protected] and [email protected] Thesource value is
configured to the «Gen V» value and limits are 0;2000 and
300;10000, what means theanalog output will give 0mA at 0V and 20mA
at 300V.

CONFIGURATION 

PROPERTY  VALUE 

SOURCE  Gen V

CONVERT  Yes

LIMITS  [0;2000]..[300;10000]

C ALCULATOR POINTS 

SOURCE  OUTPUT 

LOW  0 2000

HIGH  300 10000

EXAMPLE: Speed control of a MTU engine via CAN. In this
case an I-CB/MTU module must be configured as aninterface
between the controller and MTU MDEC control unit. The I-CB requires
the requested speedto be sent in RPM.

NOTE:  As the source value (SpeedReq RPM) has the same
dimension and resolution as required by theanalog output (1 RPM),
there is no need for convert or normalize.

CONFIGURATION 

PROPERTY  VALUE 

SOURCE  SpeedReq RPM

CONVERT  No

NORMALIZE  No

8/20/2019 Genconfig 3.0 Reference Guide

40/153

GenConfig, SW version 3.0, ©ComAp – June 2013
40Genconfig-3.0-Reference guide.pdf

EXAMPLE: Speed control of a Volvo AUX engine via CAN J1939
(using APP value of VP_AUX propietary frame).The APP value of the
VP_AUX frame has range of 0-100.0%.

NOTE:  As the source value (Speed request) has the
same dimension and resolution as required by the

VP_AUX frame (0.1%), there is no need for convert or
normalize.

CONFIGURATION 

PROPERTY  VALUE 

SOURCE  Speed request

CONVERT  No

ECU VALUE   Accelerator Pedal Position

NORMALIZE  No

EXAMPLE: Speed control of a John Deere engine via CAN J1939
(using TSC1 frame). The TSC1 frame requiresthe requested speed in
RPM.

NOTE: 

 As the source value (SpeedReq RPM) has the same dimension
and resolution as required by theTSC1 frame (1 RPM), there is no
need for convert or normalize.

CONFIGURATION 

PROPERTY  VALUE 

SOURCE  SpeedReq RPM

CONVERT  No

ECU VALUE  Requested speed

NORMALIZE  No

NOTE: See the ComAp Electronic Engines Support guide
for detailed information about speed control of

electronic engines.

8/20/2019 Genconfig 3.0 Reference Guide

41/153

GenConfig, SW version 3.0, ©ComAp – June 2013
41Genconfig-3.0-Reference guide.pdf

Limits calculator (legacy)

The calculator is used for defining of the linear transformation
function if Convert = YES. Enter two

points of the configured value and appropriate output level for
each point.

NOTE: 

It may occur that you will see «N/A» in the «Computed limits»
column and the OK button will be

disabled. That means the particular transformation is not
allowed.

TRANSFORMATION OF 0-150KW TO
0-10V RESP. 0-20M A 

TRANSFORMATION OF 0-150KW TO 4-20M A 

8/20/2019 Genconfig 3.0 Reference Guide

42/153

GenConfig, SW version 3.0, ©ComAp – June 2013
42Genconfig-3.0-Reference guide.pdf

Setpoints

Setpoints

Setpoints are adjustable points of the controller that are used
to adjust the controller according to gen-set parameters (as e.g.
nominal values or protection limits) and to modify the controller
behavior.

GenConfig is used to write initial values of
setpoints after configuration is programmed. Thesetpoints are
then changed online with InteliMonitor  or directly from
the controller panel. Batchwriting of all setpoints after
programming of configuration can be enabled/disabled by checking
the

menu item Options -> Overwrite setpoints.

Adjusting setpointsNOTE: Use GenConfig to modify initial
settings of setpoints when you are creating the the configuration.
If theconfiguration has been already finished and programmed into
the controller, then use InteliMonitor or

controller front panel to readjust necessary setpoints.

NOTE:  As GenConfig does not work online, changing of
a setpoint does not cause any change in thecontroller. The change
affects the currently opened archive only will be propagated into
the controllerfirst after programming the configuration.

Select the Setpoints tab to change the setpoints. The setpoints
are separated into groups according to

their meaning. There are following types of setpoints:

Numbers — click on the setpoint value and then use keyboard
to enter numeric value. Allowedrange of the setpoint is displayed
as a hint when you point the mouse over the respectivesetpoint
value.

List — click on the setpoint value and then select the
requested choice from the list.

String — click on the setpoint value and then use keyboard
to enter the string.

Special — some numeric setpoints have end point values
displayed as text. Typically value 0(zero) is displayed as «OFF» by
some setpoints as adjusting of zero switches the particularfunction
off. Click on the setpoint value and then use keyboard to enter
numeric value or usearrow keys to increment/decrement the value by
1. Allowed range of the setpoint including theend points is
displayed as a hint when you point the mouse over the respective
setpoint value.

8/20/2019 Genconfig 3.0 Reference Guide

43/153

GenConfig, SW version 3.0, ©ComAp – June 2013
43Genconfig-3.0-Reference guide.pdf

Access groups and rightsEach setpoint belongs to one of 8 groups
of access level.

 Adjusting setpoints in the group 0 does not require any
password, the setpoints are accesiblewithout any limitation.

 Adjusting setpoints in the groups 1-7 require an user to
be logged-in who has access right intothe respective access level
group.

EXAMPLE: 

The picture below shows how to assign the whole setpoint group
ProcessControl  into access group 1with the exception
that the Baseload  setpoint will belong to the access
group 0, i.e. it will be accessible

without password.

8/20/2019 Genconfig 3.0 Reference Guide

44/153

GenConfig, SW version 3.0, ©ComAp – June 2013
44Genconfig-3.0-Reference guide.pdf

Eight different users can be created in the controller. User 0
is Administrator , who has permanentaccess into all
groups.

NOTE: Use the InteliMonitor to administrate users for the
particular controller and assign access groups tothem.

NOTE: Factory default password for each user is 0
(zero).

Setpoint value forcingThe setpoints are adjustable points of the
controller, which are adjusted from PC or controller frontpanel and
the adjustment is stored permanently in EEPROM memory. However it
may be required toforce temporarily different setting into a
setpoint by a binary input.

EXAMPLE: The genset nominal load is normally adjusted to
real rated power of the genset, but in hot summerdays when the
ambient temperature rises above certain level the nominal load
needs to be reduced to

prevent overheating. The force value function can be used to
solve this requirement.

Follow this procedure to configure force value function onto a
setpoint:

1. Go to the Setpoints tab, select the required setpoint and
click on the … button. If the button is

not displayed then the particular setpoint does not support
forcing.

2. Click on the Wizard button at the bottom of the force value
window.

3. Enter name for this force value item, e.g.
«ReducedNominal».4. Select a binary object that will be used for
activation of this force value item. It can be either a

physical binary input (e.g. if the force value item will be
activated by a switch on theswitchboard) or a logical binary output
(e.g. output from a PLC block). The wizard configuresautomatically
the forcing LBI onto selected binary object. The configuration of
the LBI can be

late checked or modified on the LBI tab.5. Select type
of setpoint that will be used for adjusting of the alternative
value.

8/20/2019 Genconfig 3.0 Reference Guide

45/153

GenConfig, SW version 3.0, ©ComAp – June 2013
45Genconfig-3.0-Reference guide.pdf

Use Select other object in case you want to force the same
alternative value into

more setpoints and you have already defined the forcing setpoint
by the previousforcing item.

Use Use default setpoint to create new forcing setpoint.

6. If new forcing setpoint is created then give a suitable name
to it (e.g. «Reduced Pnom») andadjust initial value of it.

NOTE: If there are more than one force value blocks
configured onto one setpoint then the highest priority hasthe block
with the lowest index (i.e. the first active block according to the
list displayed in GenConfig in

the Force value window at the related setpoint).

FORCE VALUE WINDOW 

1. Name of the target setpoint where the alternative
settings will be forced

2. Forcing item 13. Forcing item 24. Names of the
source setpoints for adjusting of the alternative settings5.
Initial setting of the alternative setpoints6. Names of the LBI
that are used to activate the forcing items7. Buttons for moving of
items in the list. If more items are active at the same time, the
one in

most upper position takes place.

Timer settingsTimers are special kind od setpoints located in
separate setpoint group which contain more adjustable

items depending on the main timer function. Click on … to
adjust the selected timer:

NOTE: There is a one LBO associated to group of four
timers.Timers 1-4 has LBO TimerAct 1-4, Timers 5-8 has LBO TimerAct
5-8  etc.

1. Timer off

TIMER IS OFF 

8/20/2019 Genconfig 3.0 Reference Guide

46/153

GenConfig, SW version 3.0, ©ComAp – June 2013
46Genconfig-3.0-Reference guide.pdf

2. Single activation (one shot)

 Adjust date, time and duration (hh:mm) of the timer.

 ADJUSTMENT OF AN ONE SHOT TIMER 

3. Repeated activation

 Adjust type of repetition:

Daily

Weekly

Monthly

Short period (interval)

The adjustment items vary according to selected repetition
type.

 ADJUSTMENT OF AN DAILY REPEATED TIMER 

8/20/2019 Genconfig 3.0 Reference Guide

47/153

GenConfig, SW version 3.0, ©ComAp – June 2013
47Genconfig-3.0-Reference guide.pdf

Commands

Commands

Commands are used e.g. for remote start and stop of the engine,
remote control of breakers or foradjusting or clearing of the
statistic values in the controller via remote communication (PC,
MODBUSetc). Each command belongs to one of 8 groups of access
level.

Commands in the group 0 does not require any password, they can
be invoked without anylimitation. The picture below shows a
configuration where no user is required to be logged into
control the genset remotely e.g. from InteliMonitor.

Commands in the groups 1-7 require an user to be logged-in who
has access right into therespective access level group. The picture
below shows a configuration where an user withaccess into the group
7 is required to invoke any other command such as clearing or
adjustingof the statistic counters.

Click on the required access level at the particular command to
switch the access level for thecommand.

8/20/2019 Genconfig 3.0 Reference Guide

48/153

GenConfig, SW version 3.0, ©ComAp – June 2013
48Genconfig-3.0-Reference guide.pdf

Universal analog protect ions

Protections

In addition to protections at analog inputs it is
possible to assign 1-level configurable protection at

each analog value in the controller, e.g. at computed electrical
values as Genset power or at analogoutputs from PLC blocks.

Select the Protections tab to see the list of already assigned
protections, add new one or remove

existing one. Grey rows belong to protections assigned in
the I/O tab to analog inputs. Theseprotections can be
neither modified nor deleted from here. Go to the I/O tab to modify
them.

LIST OF PROTECTIONS AT THE PROTECTION TAB 

PROTECTION CONFIGURATION WINDOW 

8/20/2019 Genconfig 3.0 Reference Guide

49/153

GenConfig, SW version 3.0, ©ComAp – June 2013
49Genconfig-3.0-Reference guide.pdf

Click on + button and follow instructions below to assign a
protection to an analog value:

1. First select the analog value to which the protection will be
assigned.2. Select the protection type. Note that this is 1-level
protection so only one protection type from

the list can be selected. For having 2-level protection you need
to assign two separateprotections with different levels to the same
value.

3. Select the group of setpoints, where limit setpoints of the
protection will be placed in.4. Select evaluation period. Use
standard (100ms) for all protections except extremely time-

critical protections.5. Select whether the protection will
activate when the analog value gets above the limit or below

the limit.

6. Select how the protection will be recorded into the history
log. Once means that only first

occurence of the protection will be recorded until fault reset
is pressed, Always means all

occurences will be recorded.7. Select whether the limit will be
constant or adjustable by a setpoint. If setpoint is used it is

possible to create new setpoint or share the setpoint with other
protection(s). Sharing of onesetpoint among more protections may be
helpful e.g. if there are more exhaust temperaturesensors in the
system and protection limit is same for all of them. If new
setpoint is createdthen change it’s name, adjust it’s range and
initial setting.

8. Select the delay setpoint/constant. Proceed as with the limit
setpoint.9. Select time period while the protection will be
enabled. Protections at certain values must be

blocked while the engine is not running.10. Select the message
that will be displayed in the alarmlist and history when the
protection

activates. You can either define new message or share message
with other protection(s). It isnot possible to share the message if
is used for another protection of the same level butdifferent
type.

 ALARM TYPES 

ALARM/EVENT KIND LEVEL DESCRIPTION

Warning 1

The alarm appears in the Alarmlist and is recorded into
thehistory log.

 Activates the output Common Wrn as well as the
standardalarm outputs.

 Alarm Only 1The alarm appears only in the Alarmlist.

 Activates the output Common Al as well as the standard
alarmoutputs.

HistRecOnly 1The 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 causedisappears.Standard
alarm outputs are not activated.

 A+H indication 1

The event is only indicated in the Alarmlist and recorded into
thehistory log.It disappear for the alarmist automatically as soon
as the causedisappears.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

8/20/2019 Genconfig 3.0 Reference Guide

50/153

GenConfig, SW version 3.0, ©ComAp – June 2013
50Genconfig-3.0-Reference guide.pdf

cooling phase.The gen-set can’t be started again while there is
a Shutdownalarm in the Alarmlist.

 Activates the output Common Sd as well as the standard
alarmoutputs.

Slow Stop 2

The alarm appears in the Alarmlist and is recorded into
thehistory 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 stopalarm in the
Alarmlist.

 Activates the output Common Stp as well as the standard
alarmoutputs.

Off Load 2

The event appears in the Alarmlist and is recorded into
thehistory log. It does not require confirmation, diappears by
itself.It causes immediate opening of the GCB. In AUT and SEMmodes
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 operationalstate
manually.If the controller is in AUT or SEM mode and all previously
activeOff load alarms disappeared the gen-set is automatically
startedback and connected to the load if the condition for the
gen-setto be running persists (e.g. Rem start/stop is active
..).This event is used to put the gen-set temporarily off the load
forany reason.

 Activates the output Common OfL.

Low Power 2

The event appears in the Alarmlist and is recorded into
thehistory log. It does not require confirmation, diappears by
itself.It causes reduction of the required gen-set load to the
MinPower PtM during parallel-to-mains operation or local
baseloadoperation. If all previously active Low power alarms
disappearedthe gen-set is automatically ramped back to the original
requiredload, which is given according to the currently active
loadcontrol 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
thehistory log. It causes immediate opening of the GCB
(withoutunloading) and then the standard stop sequence with
cooling

follows.The gen-set can’t be started again while there is a BOC
alarm inthe Alarmlist.

 Activates the output Common BOC as well as the
standardalarm outputs.

Mains Protect 2

The protection is only recorded into the history log.In
applications which control the MCB this protection causesopening of
the MCB. The gen-set can continue operation inisland mode if
required. The MCB can be closed back as soonas there isn’t any
mains protection active (including the built-inmains
protections).In applications which do not control the MCB this
protection

causes opening of the GCB. The controller waits then for theMCB
to open. After that the gen-set can continue operation in

8/20/2019 Genconfig 3.0 Reference Guide

51/153

GenConfig, SW version 3.0, ©ComAp – June 2013
51Genconfig-3.0-Reference guide.pdf

island mode if required. As soon as there isn’t any
mainsprotection active (including the built-in mains protections)
theGCB is opened again and the controller waits for the MCB
toclose. After that the gen-set can continue operation in
parallel-to-mains mode if required.

 Activates the output Common MP.

This alarm type is not overriden by the input Sd Override.

Sd Override 2

The alarm appears in the Alarmlist and is recorded into
thehistory log.It causes immediate stop of the gen-set without
unloading andcooling phase.The gen-set can’t be started again while
there is a Sd overridealarm in the Alarmlist.

 Activates the standard alarm outputs.This alarm type is
not overriden by the input Sd Override.

EXAMPLE: Complex protection — this example shows how
to use universal protections to create a complex

protection at analog input where coolant temperature is
measured. The protection will issue a warningalarm «Frost alert»
whenever the temperature drops below 0° (fixed limit) or
warning/shutdown alarm»Coolant Temp» when the teperature rises
above 95/100° (adjustable). The overtemperature will bechecked at
running engine only.

1. Go to the I/O tab and configure the appropriate analog
input. Give the name «Coolant Temp»

to it, configure appropriate sensor and other items. Tick
Protection and configure:

Protection type = Warning, Shutdown

 Active when = Over limit

History record = Always

Block type = RunOnlyBlkDel1

 Adjust initial values of limit setpoints to 95 and
100° 

2. Go to the Protections tab and click on + button to add new
protection.

3. Select Coolant Temp value and configure following
protection properties:

Protection type = Warning

Protection group = Analog protect

Evaluation period = Standard

 Active when = Under limit

Block type = All the time

History record = Always

Press the button New Message and enter text «Frost alert»

Select «Constant» for the limit and delay setpoints and adjust
0° as limit and 10s asdelay

EXAMPLE: Window protection — this example shows how to
use universal protections to create a windowprotection for the
battery voltage. The protection will issue a warning alarm «Batt
volt» whenever thebattery voltage drops below 18V or rises above
30V.

1. Go to the Protections tab and click on + button to add new
protection.

2. Select UBat  value from the Analog
CU  group and configure following protection
properties:

Protection type = WarningProtection group = Analog protect

8/20/2019 Genconfig 3.0 Reference Guide

52/153

GenConfig, SW version 3.0, ©ComAp – June 2013
52Genconfig-3.0-Reference guide.pdf

Evaluation period = Standard

 Active when = Under  limit

Block type = All the time

History record = Always

Press the button New Message and enter text «Batt Volt»

Select «New setpoint» for the limit setpoint, give name «Batt
Volt » to it, adjust range20 — 40V and adjust the limit to 30V

Select «Existing setpoint» for the delay setpoint and select the
previously created «BattVolt Del» setpoint.

8/20/2019 Genconfig 3.0 Reference Guide

53/153

GenConfig, SW version 3.0, ©ComAp – June 2013
53Genconfig-3.0-Reference guide.pdf

History

History

This tab is used to modify the contents of the history file
record. Each record contains date, time andcause 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 thehistory memory
immediately in the moment when the written event occurs. The rest
of the record maybe 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 tree2. Buttons for adding/removing values
into/from the record structure3. Buttons for ordering of the values
in the record structure4. Fast history separator. The fast part is
located above the separator5. Estimated number of records depending
on record size6. Record capacity usage indicator

NOTE: Values that are displayed in green color are
recommended to be placed in the fast part.

NOTE: 

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 theconfiguration.

8/20/2019 Genconfig 3.0 Reference Guide

54/153

GenConfig, SW version 3.0, ©ComAp – June 2013
54Genconfig-3.0-Reference guide.pdf

User sensors

User Sensors

It is possible to create an user-defined sensor if a particular
sensor type is not predefined in thecontroller firmware. However
you have to know the sensor characteristics. An user-defined sensor
willthen appear in the