You are on page 1of 52

LiteEdit

Monitoring Tool for ComAp Controllers


To be used with ComAp controllers:

InteliLiteNT AMF, InteliLiteNT MRS


InteliCompactNT SPtM, InteliCompactNT MINT, MainsCompactNT
InteliATSNT STD, InteliATSNT PWR, InteliLite AMF, InteliLite MRS
InteliDrive Lite, InteliDrive EM, InteliDrive FLX, InteliPro

SW Version 4.6, January 2013

Reference Guide

Copyright © 2013 ComAp a.s.

ComAp a.s.
Kundratka 17, 180 00 Praha 8, Czech Republic
Tel: +420 246 012 111, Fax: +420 266 316 647
E-mail: info@comap.cz, www.comap.cz
Table of contents
1 Document information ................................................................................................................. 4
1.1 Clarification of notation ........................................................................................................... 4
2 What is LiteEdit? ........................................................................................................................... 5
2.1 Installation .............................................................................................................................. 5
2.1.1 LiteEdit directories ............................................................................................................. 7
2.1.2 PC Hardware requirements ............................................................................................... 8
2.2 Help ........................................................................................................................................ 8
3 Communication ............................................................................................................................. 9
3.1 Direct connection ................................................................................................................. 10
3.2 Modem connection ............................................................................................................... 11
3.3 Internet connection ............................................................................................................... 12
3.4 AirGate connection ............................................................................................................... 13
3.4.1 How can you get controller’s AirGate ID .......................................................................... 14
3.5 Offline connection ................................................................................................................ 14
3.6 Predefined connection ......................................................................................................... 16
3.7 Close connection / Save archive .......................................................................................... 17
3.8 DDE Server .......................................................................................................................... 17
3.8.1 DDE Server status line .................................................................................................... 17
3.9 DDE Server error messages ................................................................................................ 18
3.10 Users/password ................................................................................................................... 18
3.10.1 Changing the password: .............................................................................................. 19
4 LiteEdit functions........................................................................................................................ 20
4.1 Control window ..................................................................................................................... 20
4.1.1 Customization of Values rows ......................................................................................... 21
4.2 Setpoints window ................................................................................................................. 22
4.3 Values window ..................................................................................................................... 23
4.4 Statistics window .................................................................................................................. 24
4.4.1 Statistics setup ................................................................................................................. 24
4.5 History window ..................................................................................................................... 25
4.6 Configuration image generating ........................................................................................... 25
4.7 Export data ........................................................................................................................... 26
4.8 Controller configuration ........................................................................................................ 26
4.8.1 Configuration window ...................................................................................................... 27
4.8.2 Configuration steps .......................................................................................................... 27
4.8.3 Controller functions .......................................................................................................... 28
4.8.4 Binary inputs .................................................................................................................... 28
4.8.5 Binary outputs .................................................................................................................. 29
4.8.6 Analog inputs ................................................................................................................... 29
4.8.7 Analog outputs ................................................................................................................. 31
4.8.8 Conversion curves ........................................................................................................... 31
4.8.9 Extension modules .......................................................................................................... 33
4.8.10 Engine control unit ....................................................................................................... 36
4.8.11 Password protection .................................................................................................... 37
4.8.12 Units and power format selection ................................................................................ 37
4.8.13 Init screen .................................................................................................................... 38
5 Controller languages .................................................................................................................. 39
5.1 IL-NT, IC-NT, IA-NT, ID-Lite, InteliPro etc. .......................................................................... 39
5.2 IL-Classic.............................................................................................................................. 39
5.3 Create language ................................................................................................................... 40
5.4 Making translations .............................................................................................................. 40
5.4.1 IL-NT, IC-NT .................................................................................................................... 40
5.4.2 IL-Classic ......................................................................................................................... 42
5.5 Import language ................................................................................................................... 43
6 Firmware upgrade ....................................................................................................................... 45
6.1 Importing new firmware ........................................................................................................ 45
LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 2
LiteEdit-4.6-Reference Guide_r1.pdf
6.2 Upgrading firmware .............................................................................................................. 45
6.3 Programming firmware into a non-responding controller ..................................................... 47
7 Archive/Configuration upgrade ................................................................................................. 48
8 Cloning ......................................................................................................................................... 51

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 3


LiteEdit-4.6-Reference Guide_r1.pdf
1 Document information
LITEEDIT - REFERENCE GUIDE
W RITTEN BY: JAN TOMANDL AND REVISED BY: JAN DONAT
©2013 COMAP A.S.
KUNDRATKA 17, PRAHA 8, CZECH REPUBLIC
PHONE: +420246012111, FAX: +420266316647
W EB: HTTP://WWW.COMAP.CZ, E-MAIL: INFO@COMAP.CZ

DOCUMENT HISTORY
REVISION NUMBER RELATED SW. VERSION DATE

1 3.2 20.3.2008

2 4.0 23.5.2008

3 4.1 10.9.2008

4 4.2 12.11.2008

5 4.3 28.2.2009

6 4.4 23.10.2009

7 4.6 28.01.2013

1.1 Clarification of notation


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 or
improper 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 of
attention, otherwise can cause personal injury or death.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 4


LiteEdit-4.6-Reference Guide_r1.pdf
2 What is LiteEdit?
LiteEdit is Windows 2000/XP/Vista/7 based software which provides following functions:
 Remote monitoring via direct, modem or internet connection with the controller
 Offline preparing of controller configuration for next usage
 Controller configuration
 Controller firmware upgrade and archive/configuration upgrade
 Read / write / adjust setpoints
 Read measured values
 Display controller history
 Export data into a XLS file
 Translate controller to other languages

NOTE:
® NT® NT® NT® NT®
LiteEdit supports InteliLite , InteliLite , InteliCompact , MainsCompact , InteliATS ,
® ® ® ®
InteliDrive Lite, InteliDrive EM, InteliDrive FLX and InteliPro controllers.

2.1 Installation
Execute the "ComAp PC Suite" installation package (i.e. IC-NT-Install-Suite-4.6.exe) to install LiteEdit,
controller firmware and other components into your computer. If there is LiteEdit already 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 controller
firmware, that you are about to install, may not be compatible with older LiteEdit version

Select (or unselect) components of LiteEdit you want to install to your computer. It is recommended to
use Full installation. Press Next.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 5


LiteEdit-4.6-Reference Guide_r1.pdf
Select options for Backup, Additional icons and rules of files overwrite.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 6


LiteEdit-4.6-Reference Guide_r1.pdf
2.1.1 LiteEdit directories
Windows XP
Program Files\ComAp PC Suite\ \LiteEdit\ Executables, LiteEdit Help, Libraries

Windows 7
Program Files\ComAp PC Suite\

Windows XP
Documents and Settings\All Users (selected \Bitmaps\ pictures
user)\Application Data\ComAp PC Suite\
Windows 7
Application Data\ComAp PC Suite\

\Database\ *.esc, *.esl, *.xml

\Index Files\ *.idx

\LiteEdit\ LiteEdit settings and working files

Windows XP
Documents and Settings\All Users (selected \Sites\
user)\Documents\ComAp PC Suite\

Windows 7
User\Public\Documents\ComAp PC Suite\
\Curves\ Input and output curves

\Help\ Controller units help files

Firmwares
\LiteEdit\ \App\
*.mhx, *ipt

Dictionaries
\Dict\
*.tm

\Displays\ Fonts

Default
\Archives\ \Default\ archives
*.aic, *.ail

User created
archives

\Clones\ Saved clones

\Connections\ *.con

LITEEDIT DIRECTORY STRUCTURE


LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 7
LiteEdit-4.6-Reference Guide_r1.pdf
2.1.2 PC Hardware requirements
LiteEdit is based on Windows 2000/XP/Vista/7 platform. Use PC suitable for this platform. There are
no special requirements for the PC hardware. LiteEdit requires approx. 15 MB of hard disc free space.

NOTE:
Use Help->About to display current LiteEdit version window.

2.2 Help
Go to Help menu to display the LiteEdit or controller help.
LiteEdit help will display this help.
Controller help will display help for the controller firmware according to the currently opened archive if
the help is available.

NOTE:
If the controller help is available and does support context help, then pressing F1 in the setpoints,
values or configuration window will open the controller help with the context of currently selected
setpoint, value and binary input or output function.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 8


LiteEdit-4.6-Reference Guide_r1.pdf
3 Communication
There are following types of connection to a controller available:
 Direct cable
 Modem
 Internet
 AirGate
 Offline

See also controller manual for information about communication possibilities for the particular
controller.

First possibility of connection type selecting is in “Select connection type” window which appears
immediately after LiteEdit start-up.

Other options of selecting connection type are by using of individual icons placed in icon bar or via
item Connection in menu bar.

CONNECTION TYPES

NOTE:
As you can see in the picture above there are also links to recently saved archives under the
Connection LiteEdit menu item.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 9


LiteEdit-4.6-Reference Guide_r1.pdf
Open direct connection

Open modem connection

Open internet connection

Open AirGate connection

Open offline connection

Open predefined connection

Close connection

3.1 Direct connection


Connect RS232 or USB cable between the supported controller and PC. Use Connection -> Open
direct to open the communication with the controller.

Go to Options -> Communication to select COM port and make other communication settings like
controller address. Tick the checkbox Ask for address and/or Ask for COM if you want to be asked for
these parameters each time the direct connection is to be opened. If the items are not checked, the
default values adjusted in this window are used.

NOTE:
A plug-in communication module is required for controllers IL-NT, IC-NT and derived types.

NOTE:
If USB connection is used (either external USB to RS232 converter or USB communication module),
the USB is to be handled as a virtual COM port of your computer, which is created by the USB module
driver.

NOTE:
Only the COM ports, that are actually installed and present in the computer, are displayed. If an USB
connection is used, but USB module is actually not attached, the relevant COM port is not displayed!
Attach the converter to see it in the LiteEdit. It is recommended to attach the USB modules always to
the same USB socket. It should prevent the computer operating system from assigning different COM
port number to the same module.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 10


LiteEdit-4.6-Reference Guide_r1.pdf
CROSS-WIRED
RS232 RS232
IL-NT RS232 RS232 CABLE
IL-NT RS232-485
Physical COM Port

RS485 RS485 CABLE RS485


IL-NT RS232-485

Physical COM Port

CROSSED-WIRED
RS232 RS232 CABLE USB
RS232
IL-NT RS232
USB

Virtual COM Port

Shielded USB „A“


USB USB
cable
IL-NT S-USB

Virtual COM Port

DIRECT CONNECTION TYPES

3.2 Modem connection


Use Connection -> Open modem to open the modem communication with the controller. Enter the
phone number, controller address and access code.

Go to Options -> Communication to select which of installed modems shall be used as default
modem. Tick the checkbox Ask for modem if you want to be asked for selecting the modem each time
the modem connection is to be opened. If it is not checked, the default modem selected in this window
is used.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 11


LiteEdit-4.6-Reference Guide_r1.pdf
NOTE:
A plug-in communication module with RS232 port is required for connection of a modem to the
controllers IL-NT, IC-NT and derived types.

Ethernet
IL-NT RS232 RS232
LAN / WAN / RJ45
IL-NT RS232-485
GSM INTERNET
MODEM
BTS / Mobile
provider

OR

IL-NT RS232 RS232


IL-NT RS232-485
GSM GSM
MODEM MODEM

Ethernet
IL-NT RS232 RS232 LAN / WAN / RJ45
IL-NT RS232-485 INTERNET
ANALOG
MODEM

OR

IL-NT RS232 RS232


IL-NT RS232-485
ANALOG ANALOG
MODEM MODEM

MODEM CONNECTION TYPES

NOTE:
Recommended modems are listed in IL-NT, IA-NT, IC-NT Communication Guide.

3.3 Internet connection


Use Connection -> Open internet to open the internet communication with the controller. Enter the IP
address of the Internet Bridge, controller address and access code.

NOTE:
The last separated IP address is a public address dedicated for testing connection to controller
situated in ComAp office. Feel free to try it!

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 12


LiteEdit-4.6-Reference Guide_r1.pdf
NOTE:
If more users are connected to a controller at the same time, only one of them is allowed to change
setpoints and control the genset (first one who performs this action). The other users are switched to
"monitoring mode", which is shown in the LiteEdit application title. Return back to normal mode is
automatic after the user finishes changing setpoints or commanding the controller.

NOTE:
A plug-in communication module is required for controllers IL-NT, IC-NT and derived types.

Ethernet CROSS-WIRED Ethernet


RJ45 ETHERNET CABLE RJ45
IB-Lite

Static IP

Ethernet Ethernet
RJ45 LAN / WAN / RJ45
IB-Lite
INTERNET

Static (Public) IP

Ethernet
LAN / WAN / RJ45
IL-NT GPRS
INTERNET

Static (Public) IP BTS / Mobile


provider
INTERNET CONNECTION TYPES

3.4 AirGate connection


AirGate connection technology makes access to the internet as simple as possible. AirGate
technology was designed to overcome the issues commonly faced when trying to connect remote
equipment using internet based communications.

It allows ComAp’s controllers to connect to the internet using the existing network infrastructure,
negotiating firewalls and VPN systems and removing the requirement for static IP addresses.

Ethernet
RJ45
IB-Lite

LAN / WAN /
Non-static non-public IP
Only AirGate ID
INTERNET
(controller nickname) Ethernet
RJ45

LAN / WAN /
IL-NT GPRS
INTERNET

Non-static non-public IP BTS / Mobile


Only AirGate ID Ethernet
provider
(controller nickname) RJ45

AIRGATE CONNECTION TYPES

For using of AirGate connection go to Connection -> Open AirGate… and fill in Controller address,
AirGate Address (“airgate.comap.cz” as default), Access Code and AirGate ID.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 13


LiteEdit-4.6-Reference Guide_r1.pdf
3.4.1 How can you get controller’s AirGate ID
1. Connect the communication module (IB-Lite or IL-NT GPRS) to the controller according to
their relevant guides. In the case of IB-Lite connect the internet cable.
2. Turn on the controller.
3. Setup the Communication modules according to their relevant guides.

NOTE:
Relevant guides for Communication modules:
- IB-Lite: IB-Lite Reference Guide; IL-NT, IA-NT, IC-NT Communication Guide
- IL-NT GPRS: IL-NT-GPRS Quick Guide; IL-NT, IA-NT, IC-NT Communication Guide

4. Setup “Comms Settings” directly on the controller:


- Press “Page” button. Choose “Comms Settings” by using of arrows ▲▼ and press
“Enter”.
- Setup “AirGate” as ENABLED. “AirGate IP” as “airgate.comap.cz”.
- Wait a while (or turn the controller off and on).
- Check the “AirGate ID”: Press few time ▲ on the basic controller display to see
GSM/Modem status. Remember the AirGate ID.
5. Use this AirGate ID in Open AirGate connection window.

NOTE:
It is not possible to change controller’s configuration (as is described in Controller configuration
chapter) when the GPRS module is used. In this case there is allowed to change setpoints and to
monitor control unit only.

3.5 Offline connection


Offline connection is actually a possibility of offline controller archive opening. Use Connection ->
Open offline… or press button for opening of offline archive (*.AIX file). The “Open archive”
window appears. Choose the archive you would like to open and press Open button.
NOTE:
Archive files are using different extensions according to the type of controller. InteliLite based
controllers use *.AIL, InteliCompact based *.AIC and InteliPro *.AIP.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 14


LiteEdit-4.6-Reference Guide_r1.pdf
The offline connection is mainly used for inspection of saved archives (e.g. in case of troubleshooting)
or for preparing of new archives for next usage. In the offline mode it is possible to change/pre-set all
setpoints just as input/output and extension modules configuration.

When the prepared archive is finished save it by pressing button to archive file.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 15


LiteEdit-4.6-Reference Guide_r1.pdf
NOTE:
It is possible to save the archive including all data from the controller during any other online
connection and to use it later e.g. in offline mode.

3.6 Predefined connection


The connection setting can be saved to a file and used later as predefined connection. All necessary
settings are stored in the file, so when opening a predefined connection, you have to select the file
only, nothing else.

The Open predefined window shows the list of predefined connections.


Use buttons above the list to manage the connections.
Click on a connection in the list to open it (connect to the controller using the predefined setting)

Following Edit connection window appears when defining new or editing a connection. Select type of
connection and adjust all related parameters. Use and icons to import and export connection
to a *.con file.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 16


LiteEdit-4.6-Reference Guide_r1.pdf
3.7 Close connection / Save archive
Use Connection -> Close to close the communication with the controller. You will be prompted by a
Save archive? question. Answer yes, if you want to store all data including the configuration into an
AIL archive file.
Following dialog box appears during closing of connection:

Archive file is saved under automatic name: <gen-set name>_yyyymmdd_vv.aix.


Gen-set name is taken from the setpoint
YYYY ... year
MM ... month
DD ... day
VV ... ordinal number
Save as command enables change the name of the AIL file.

NOTE:
Archive files are using different extensions according to the type of controller. InteliLite based
controllers use *.AIL, InteliCompact based *.AIC and InteliPro *.AIP.

3.8 DDE Server


DDE Server provides the communication interface between PC and Controller. It is started
automatically from LiteEdit. Use ALT+TAB to view DDE server window.
Click on Last errors to see report of the last error message.
Click on Stop to pause the communication (not to close the connection).

CAUTION!
DDE server must be running during any connection except off-line. Do not close it manually!

3.8.1 DDE Server status line


Status of the DDE Server (Running / Preparing / Error) is visible on the bottom line of the LiteEdit
window. Double click on it or use Connection -> Information to get detailed information.

STATUS LINE COLOUR MEANING

Running green The connection is running, no problems occurred

Running - wrong The connection is running, but checksum of setpoints is not


green
setpoints valid (occurs typically after firmware is upgraded)

Running (Reading
green The connection is running and history is being read
history)

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 17


LiteEdit-4.6-Reference Guide_r1.pdf
The DDE server is building-up the connection to the
Preparing yellow
controller

The DDE server has just build-up the connection and is


Reading history #% yellow
reading history for the first time while connected

The connection failed. Use ALT-TAB, select DDE Server


Error red and press the "Last errors" button at the controller with
appropriate address to see more information

3.9 DDE Server error messages

Connected controller does not answer to DDE server requests.


Probable reasons:
The controller is not connected or switched off
The communication cable is wrong
Timeout (continuous)
The COM port number is not correctly selected
Setpoints in the controller related to the communication are not
correctly adjusted
The communication module in the controller is damaged

Occasional timeouts can be caused by overloading of your


Timeout (time to time)
operating system

TAPI: requested modem


The selected modem is not attached or properly installed
(#) not found

TAPI: unavailable modem Communication port is being used by other communication device.

TAPI: Line unexpectedly Modem is configured in Windows, but it is not connected or it is


closed failed.

It is not possible to open connection. Probable reasons:


When "beeping" is audible during start of the connection, the line
quality is bad or the other modem is not compatible with the
TAPI: Can't create
originating one.
connection
When busy tone is audible during start of connection, the
destination number is busy or wrong.
When no tone is audible, no phone line is connected to the Modem

Pop-up window with a The selected COM port is occupied by other program or is not
message Can't open installed. Check if there is other program using the COM port
COM running or select proper COM port

3.10 Users/password
The controller has 1-level protection system. Each setpoint and command can be assigned to be
protected during configuration. Programming firmware and configuration changes are protected by
highest level and this cannot be changed.
Use icons to enter or deactivate password. The icon also shows if the controller is currently
unlocked or not.
LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 18
LiteEdit-4.6-Reference Guide_r1.pdf
NOTE:
Password entering in LiteEdit enables to access Setpoints from LiteEdit only, not from controller front
panel and vice versa.

3.10.1 Changing the password:


1. Open any type of online connection to the controller
2. Enter password
3. Go to menu Controller -> Change password, and then write new password into both fields.

NOTE:
There is a limitation that new password cannot be higher than 9999.

HINT:
The password can be changed directly from the controller also. For more information see the
Reference Guides or Operator Guides of supported controllers.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 19


LiteEdit-4.6-Reference Guide_r1.pdf
4 LiteEdit functions
Main functions of LiteEdit are viewing and changing setpoints, viewing operational quantities and
history log and changing the controller configuration.

LIST OF AVAILABLE FUNCTIONS


Save archive

Control window

Setpoints adjustment

Values window

History window

Users/password

Open configuration from an archive

Modify configuration

Languages/translator

Import Language

4.1 Control window


Control window is active for online connections only and has two basic functions:

Controller mode change


Remote genset control Manual genset control via buttons like from controller
front panel.

State machine indication.


Genset states indication and values Mains, genset and breaker states LED indication.
reading Alarm list, ECU Alarm list.
Reading of actual values measured from genset.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 20


LiteEdit-4.6-Reference Guide_r1.pdf
NOTE:
In case of AirGate connection when reading history the Control window is disabled until history is fully
downloaded.

4.1.1 Customization of Values rows


It is possible to customize visible objects in the section of Values in Control Window. For the
customization right-click at the Values section and choose one of offered options: Edit Row…, Add
new row or Restore defaults.

When pressed the Edit row… or Add new row option the Customize object window appears. It is
possible to configure Value or Setpoint which is available in the controller. You can choose one of
them from the list which is hidden behind the button or from the visual Values and Setpoint tree
which you can open by clicking of button next to the Com Obj column.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 21


LiteEdit-4.6-Reference Guide_r1.pdf
4.2 Setpoints window
The setpoints window enables to adjust value of each setpoint present in the controller. Password
protected setpoints have grey background and can't be changed until a password of proper level is
entered. It is possible to change any setpoint without password in Off-line mode, but password will be
required later, when the modified archive will be written into the controller.

All the setpoints changed from the moment Setpoints window is opened are emphasized using light
blue colour. It is possible to see original value in the column Original setting. Original values inform
about setting/situation at the moment when the Setpoint window is opened. New values can be seen
in the column Actual setting. Once the Setpoint window is closed all the information about differences
are lost. The whole process of comparison is started again once the Setpoint window is opened.

In the Setpoints window can be some setpoints emphasized by yellow and red colour too. Red colour
means the setpoint is not valid in the used firmware or branch. Yellow colour means that the set value
is out of define range.

Setpoints limits and protection status is visible when the mouse is located over the setpoint field.

NOTE:
Pressing F1 will open context help window for the selected setpoint, if context help is available for the
particular controller firmware and setpoint.

NOTE:
In case of AirGate connection when reading history the Setpoints window is disabled until history is
fully downloaded.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 22


LiteEdit-4.6-Reference Guide_r1.pdf
4.3 Values window
This window shows current measured and computed values. The values are separated to groups
according to their meaning.

NOTE:
Pressing F1 will open context help window for the selected value, if the help is available for the
particular controller firmware and value.

It is also possible to see current state of binary inputs and outputs.


To see more details about binary values of certain module press next to the appropriate module in
Values window.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 23


LiteEdit-4.6-Reference Guide_r1.pdf
In case of some (BIO) Extension plug-in modules their channels can be configured as binary input
(labelled as IN:) or binary output (labelled as OUT:).

In case a channel of BIO module is not configured its value is neither 0 nor 1, it takes the value "x".

NOTE:
The IN: and OUT: prefixes are also visible (in case BIO module is configured) in the Control window.

4.4 Statistics window


Statistic values (counters) are one of groups in Values window. The difference from other values is
that statistic values can be reset to zero or set to some value and they are stored in the controller even
if the power is off.

4.4.1 Statistics setup


Password must be entered and the controller has to be on-line to enable statistic setup.
Go to Controller -> Set statistic menu.

Set statistic value(s) to desired value in the right white column and press Set button.
Wait until the value in the left grey column changes to the new value.

You can change and set values one by one or change all of them first and the set all together by
pressing Set all button.

All statistic values can be reset to zero using Reset all button.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 24


LiteEdit-4.6-Reference Guide_r1.pdf
4.5 History window
This window displays the history log from the controller. The history log is displayed as a table, where
each row contains one record (event) and the columns contains data values recorded in the moment
the event occurred.

Each record contains date and time it was recorded.

Each record contains a short text describing the reason of the record.

The most recent record is displayed in the first row of the table, older records are below.

NOTE:
The first history record after the controller is switched on, programmed or watchdog reset occurs
contains diagnostic values instead of operational. Some fields in these records seem to have
nonsense values. Do not take these values into account.

NOTE:
The history log is not available in all types of controllers.

NOTE:
Columns of history are partially customizable. It is possible to add or delete some of columns
associated with ECU, External or Plug-in modules. This can be done by ticking of “Add to history”
while configuring ECU, External or Plug-in modules in Configuration window.

4.6 Configuration image generating


Use Controller -> Generate Cfg image menu. You can choose then from:
- Generate Cfg Image (Comm. Objects)… for generating of communication objects list
- Generate Cfg Image (Modbus Registers – all)… for generating of all Modbus registers

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 25


LiteEdit-4.6-Reference Guide_r1.pdf
- Generate Cfg Image (Modbus Registers – used)… for generating of used Modbus
registers
- Generate SNMP MIB table… for generating of SNMP MIB table
NOTE:
Controller firmware must support SNMP function as well to enable using it in IB-Lite. Please
refer to the controller New Feature lists for information about this support.

4.7 Export data


Use Controller -> Software configuration -> Export data menu. Dialog box Export data allow
separately save to PC tables of Setpoints, Values, History or Software configuration in XLS or CSV
format.

4.8 Controller configuration


Configuration is a process of assigning of functions to input and output terminals of the controller,
defining of attached modules, ECU units and others.

NOTE:
The configuration is available only if password of highest level is entered!

NOTE:
Enter names of inputs, outputs etc. in English language. Make translation after configuration is
finished using Translator function.

NOTE:
Create a connection before viewing or modifying the configuration.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 26


LiteEdit-4.6-Reference Guide_r1.pdf
4.8.1 Configuration window

Use Controller -> Configuration -> Modify to modify current configuration.


Use Controller -> Configuration -> Select to import the configuration from an archive.
Press the OK button to write the modified configuration to the controller.

Press the Save as button to save the configuration to disk. This is recommended before writing it to
the controller for backup purpose.

4.8.2 Configuration steps

Controller functions
Binary inputs
Binary outputs
Analog inputs
Analog outputs

Extension modules

Engine control unit

Password protection

Units and power format selection

Init screen - welcome text

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 27


LiteEdit-4.6-Reference Guide_r1.pdf
4.8.3 Controller functions

Press button to open window of Controller functions for reducing number of visible setpoints
which can simplify the controller interface and configuration in case some of the controller
functions/features are not used. In case you unselect such a function from the “Controller functions”
list all logical functions (logical binary input and output), setpoints and values connected with this
function will be hidden and invisible in the interface (controller screens and LiteEdit windows).

HINT:
Hiding of not logical functions, setpoints and values is done based on “Controller functions” setting, but
also automatically according to configuration of analog inputs, extension modules and ECU.

NOTE:
This function is not available unless it is also supported in the respective controller.

4.8.4 Binary inputs


Go to the upper left part of the configuration window and click to the appropriate input to configure it.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 28


LiteEdit-4.6-Reference Guide_r1.pdf
Configure the function of the input - Alarm (e.g. Low oil level) or Control (e.g. GCB feedback)
For Control inputs select function from the list in Name section.
For Alarm inputs enter name of the input to the field in Name section

For Alarm inputs select alarm type from the list and select if the alarm shall be active at running engine
only (e.g. oil pressure)
Select type of the contact. NO = NormallyOpen, active when closed. NC = NormallyClosed, active
when opened.

4.8.5 Binary outputs


Select desired function from the list at each output.

4.8.6 Analog inputs


Go to the lower left part of the configuration window and click to the appropriate input to configure it.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 29


LiteEdit-4.6-Reference Guide_r1.pdf
Configure the function of the input - Alarm, Monitoring or not used input.
For Alarm inputs enter name of the input to the field in Name section.

Select type of the input in the Config section. Analog input can be used as Analog, Binary or Tristate
input.

Select alarm properties:


 Alarm direction: select if the alarm shall be activated in the moment the analog value drops
below the limit or gets over the limit.
 Alarm evaluation period: select if the alarm shall be evaluated at running engine only (e.g. oil
pressure) or always.
 Alarm type: assign alarm type. It can be yellow type only (warning) or combination of yellow
and red types (e.g. warning and shutdown)

Configure sensor points or contact type (depends on whether the input is used as Analog or as
Binary/Tristate. See chapters below.

NOTE:
The analog input 1 has fixed meaning as oil pressure. If an ECU is configured, the oil pressure is read
from the ECU and Analog input 1 of the InteliLite is free to be used for any other measurement.

NOTE:
In the case the Monitoring option is chosen all protections available for Alarm option are disabled and
the analog input is then used only for monitoring.

NOTE:
It is possible to change Names of Analog inputs, analog curves and units only in case of using default
language.

4.8.6.1 Configure input as Analog


Press button to open a window for selecting or defining conversion curve, dimension and
number of decimal places.

Select area the alarm shall be active (under/over the limit)

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 30


LiteEdit-4.6-Reference Guide_r1.pdf
4.8.6.2 Configure input as Binary/Tristate
Select type of the contact. NO = NormallyOpen, active when closed. NC = NormallyClosed, active
when opened.

Threshold level in case an analog input is configured as binary or tristate is 750 Ohm.
In case an analog input is configured as tristate, values <10 Ohm and >2400Ohm are evaluated as
sensor failure (short or open circuit).

NOTE:
See controller reference guide for more details.

4.8.7 Analog outputs


NOTE:
This chapter refers to the NT line controllers only. The Classic line does not support analog outputs.

Go to the lower right part of the configuration window and click to the appropriate output to configure it.
Go to the lower right part of the configuration window (for version 4.3.1 and older) or to analog output
module in Extension plug-in modules configuration (for versions 4.4 and higher) and click to the
appropriate output to configure it.

Press "Select" button to configure the value (quantity) that has to control the output. Press “Not used"
if the output is no longer used.

Press the button to define the output curve to be used for the appropriate analog output.

NOTE:
The analog outputs are open collector (low side switch) types with PWM modulation. So the output
physical quantity is always in %. 0% PWM means no current flows through the output, 100% means
full current. The full current is given by the supply voltage and resistance of the attached gauge. Learn
more about analog output wiring in the controller reference guide, section Installation.

NOTE:
The analog output on the IGS-PTM module is a 0-20mA current source, where 0% PWM is 0mA and
100% PWM is 20mA output current.

4.8.8 Conversion curves


Conversion curves are used for analog inputs (sensor-to-physical value conversion) as well as for
analog outputs (physical-to-gauge value conversion)

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 31


LiteEdit-4.6-Reference Guide_r1.pdf
4.8.8.1 Analog inputs
The curve definition window for the particular analog input opens when you press the

button in the analog input configuration window.

Use the button to load a predefined curve from disk


Use the button to save created or modified curve to disk
Use the and buttons to add and remove points

You can modify name of the curve, resolution of the output value and dimension of the output value
For IOM/PTM inputs you have to select also the primary electrical quantity the input shall measure
(Ohm, V, and mA). This setting must correspond with the setting on the IOM/PTM module for the
particular input. The inputs on the controller have resistive measurements only.

NOTE:
For some older versions of IL-classic and IL-NT the Sensor name is not editable, it is a selection
instead. You have to select either some predefined sensor or a user-definable sensor (Curve A, Curve
B, Curve C). When you select a predefined one, you cannot modify points. For user-definable sensors
you can modify everything as described above.

NOTE:
There is an input range limitation. It is possible to insert only values from 0 to 15000 ohms.

4.8.8.2 Analog outputs


The curve definition window for the particular analog output opens when you press the

button in the analog output configuration window.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 32


LiteEdit-4.6-Reference Guide_r1.pdf
Use the button to load a predefined curve from disk. The physical dimensions in the curve must
match with the physical dimension of the configured value on the left ("primary") side and with "%" on
the right ("converted") side. If it does not match, you will receive an error message.
Use the button to save created or modified curve to disk
Use the and buttons to add and remove points

The left column contains the physical value of the configured value (object)
The right column contains the appropriate output level (always in % of PWM).

4.8.9 Extension modules


Following extension modules are available to be connected to controller (IL, IL-NT and IC-NT):
Extension plug-in modules
IOM/PTM module
Remote annunciator RA15
ECU of an electronic controlled engine (J1939, Modbus)

4.8.9.1 Extension plug-in modules

Press button in the configuration window to configure Extension plug-in modules.

You can choose out of several modules:


 IL-NT-AOUT8
 IL-NT-BIO8
 IC-NT-CT-BIO7
 IL-NT-IO1
 IL-NT-AIO, etc.

They can be configured following way:


Modules of binary inputs and/or binary outputs (e.g. IL-NT-BIO8)

Press to configure channel as binary input.

Press to configure channel as binary output.

Press to configure channel as not used.


Check "Add to history" box if Extension plug-in module values should be included in controller history.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 33


LiteEdit-4.6-Reference Guide_r1.pdf
Modules of analog inputs and analog outputs (e.g. IL-NT-AIO)

Press to configure channel as analog input.

Press to configure channel as analog output.

Press to configure channel as not used.


Check "Add to history" box if Extension plug-in module values should be included in controller history.

NOTE:
Analog inputs are included in controller history only in case they are configured and the "Add to
history" box is checked. Not configured analog inputs are not included in controller history even though
the "Add to history" box is checked.

4.8.9.2 IOM/PTM module

Press button in the configuration window to configure IOM/PTM module.


LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 34
LiteEdit-4.6-Reference Guide_r1.pdf
Check the box if IOM or PTM module is connected
Configure all inputs and outputs the same way as on InteliLite.
Check "Add to history" box if IOM or PTM module values should be included in controller history.

NOTE:
Analog inputs are included in controller history only in case they are configured and the "Add to
history" box is checked. Not configured analog inputs are not included in controller history even though
the "Add to history" box is checked.

4.8.9.3 Remote annunciator RA15

Press button in the configuration window to configure RA15 module.


Check the box if RA15 module is connected.

Select function of each LED indicator. The list of functions is identical as for binary outputs.
LED colour selection can be modified on the RA15 directly during the setup process. Please see the
documentation of the RA15 module.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 35


LiteEdit-4.6-Reference Guide_r1.pdf
4.8.10 Engine control unit

Press button in the configuration window to configure an ECU controlled engine.


Check the box if an ECU equipped engine is connected to communication line of the InteliLite.
Select type of the ECU from the list.

If an ECU is configured, the oil pressure is read from the ECU and Analog input 1 of the InteliLite is
free to be used for any other measurement.
Check "Add to history" box if ECU values (FC and FMI) should be included in controller history.

NOTE:
If your ECU type is not listed and the ECU communication protocol is based on SAE J1939, try to
select "Standard J1939 engine".

4.8.10.1 ESL files


ESL file is a file with list of supported electronic controlled engines. Each supported engine is
described in separate "description" file - ESF file. ESF and ESL files are imported together with the
firmware. The ESL file, that has to be used for configuration of electronic controlled engines, can be
selected in menu Options -> ESL files.

ESL file is different for Genset and DCU controllers.


Select "ECU list - Gensets.esl" for genset controllers (default setting)
Select "ECU list - Allspeed.esl" for DCU controllers

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 36


LiteEdit-4.6-Reference Guide_r1.pdf
4.8.11 Password protection

Press button in the configuration window to configure password protection for setpoints and
commands. Password protection can be assigned on each setpoint individually or on complete
groups. Switch "Yes" or "No" at the appropriate setpoint to assign password protection to it or
select/deselect the password protection for the whole group in the field All items in the group".

4.8.12 Units and power format selection

Press button in the configuration window to change power format and ECU units.
Power format can be changed in Power format window.

ECU units can be changed in ECU window.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 37


LiteEdit-4.6-Reference Guide_r1.pdf
4.8.13 Init screen

Press button in the configuration window to configure welcome text, which will be displayed on
Initial controller screen.
Check the "Disable init screen" box in case the Init screen shouldn't be visible on controller display.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 38


LiteEdit-4.6-Reference Guide_r1.pdf
5 Controller languages
5.1 IL-NT, IC-NT, IA-NT, ID-Lite, InteliPro etc.
It is possible to have 2 languages in the controller. In the slot #1 is firmly stored English language.
Language in the slot #2 can be changed by the user.
The procedure of adding a new language is following:
Open the target archive or connect to the controller. Use any type of connection.
Click on the button to open the Translator window.
Create new language
Make the translation

NOTE:
If there is a default dictionary available for the required language and the user does not want to
change the translations, the function Language import can be used for easy replacing of the
language in the slot #2 of the controller.

Once you finished adding the language, use Controller -> Language menu to select the language in
which the controller texts (values names, setpoints names, history texts etc.) have to be displayed.
Preferred language can be selected in Options -> Settings window. This language will be used each
time the selected language will be found in the controller. Otherwise default language will be used.

NOTE:
These settings affect LiteEdit only, not the controller itself!

5.2 IL-Classic
There is one language only in the classic line of InteliLite. Following description shows how to
translate the controller texts.

NOTE:
Once translated, the iL-classic line cannot be reverted back to English simple way.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 39


LiteEdit-4.6-Reference Guide_r1.pdf
5.3 Create language
Creating a Latin language:
Use the button to remove the 2nd language and keep only the English one.

Click to the button and create new language based on English.

Then give a suitable name to the language and select locale ID and time/date format. Code page will
be completed automatically after locale ID is selected.
Click to the Translator tab to continue to translations.

NOTE:
It is not recommended to remove the English language. It is not possible to provide technical support
without having English language in the controller!

If you are creating a graphic language like Chinese, use the default language 2 (do not remove it!!)
and modify only the name and locale ID. Then continue with translation.

5.4 Making translations

5.4.1 IL-NT, IC-NT


It is possible to have 2 languages defined in the controller. The language must be created prior to
making a translation.

Click on the button to open the “Language and translator” window.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 40


LiteEdit-4.6-Reference Guide_r1.pdf
Click on the icon to open a working dictionary. A window with a list of dictionaries will open.
Select proper one or create new if it does not exist. It is also possible to perform the translation without
working dictionary and using the default only, but in such case it is not possible to modify the
translation texts.

NOTE:
To prevent user translations from overwriting by new version of default dictionary, the user translations
are stored in a user-created working dictionary. The default dictionaries, which are delivered together
with the software, are read-only and can't be used as working dictionaries.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 41


LiteEdit-4.6-Reference Guide_r1.pdf
NOTE:
The translations are searched in the working dictionary first and if it is not found there, then the default
dictionary is used.

Now the untranslated items (that are not present in any dictionary) are shown in cyan colour,
translated by user dictionary are white and translated by default dictionary are grey.

Translate untranslated items by editing them directly in the column of the appropriate language. Items
are added to the dictionary automatically. Go through all groups of texts (select group in the left part of
the window).

Using icons in the toolbar of the Languages window you can mark all or one text as translated while
leaving the original text. It is possible also revert translated item to original text and mark it as
untranslated back.

5.4.2 IL-Classic
There is one language only in the classic line iL. Following description shows how to translate the
controller texts.

NOTE:
Once translated, the iL-classic line cannot be reverted back to English simple way.
Click on the icon to open a dictionary. A window with a list of dictionaries will open. Select proper
one or create new if it does not exist.

Now untranslated items (that are not present in the dictionary) are shown in cyan colour, translated
are white.

You can also work without a dictionary, but next time you will have to make all translation again, it
won't be stored.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 42


LiteEdit-4.6-Reference Guide_r1.pdf
Translate untranslated items by editing them directly in the column Translated text. Items are added to
the dictionary automatically. Go through all groups of texts (select group in the left part of the window).

Using icons in the toolbar of the Languages window you can mark all or one text as translated while
leaving the original text. It is possible also revert translated item to original text and mark it as
untranslated back.

5.5 Import language


NOTE:
There are two language slots in IL-NT and IC-NT controllers. Slot 1 is reserved for the default
language (English) and slot 2 can be used for the additional language.

Use the language import function to add new language into the additional language slot of the
controller. Default English-to-xxxx dictionary is required for this function. Default dictionaries are
distributed together with the firmware.

The procedure of language import is following:


Open the target archive or connect to the controller. Use any type of connection.
When you click on the button Import language dialog appears.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 43


LiteEdit-4.6-Reference Guide_r1.pdf
Select language you would like to import on the left side of the dialog window (list of available
languages).

In case there is a free slot on the right side (in controller) you can add new language using
button.
In case the second controller slot is not free you can use button to replace currently
present language (in controller) by selected available language.
In case the second controller slot is not free you can use button to remove second
language from controller.
When import process is finished press OK. The new language can be modified now in the Translator
window. See more in the Controller languages chapter.

NOTE:
It is not possible to import language which is already present in controller.

NOTE:
It is not possible to remove or replace default (English) language.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 44


LiteEdit-4.6-Reference Guide_r1.pdf
6 Firmware upgrade
NT
Firmware of ComAp controllers compatible with LiteEdit (InteliLite Classic, InteliLite ,
NT NT NT
InteliCompact , MainsCompact , InteliATS , InteliDrive-Lite, InteliDrive-EM, InteliDrive-FLX and
InteliPro) is embraced in IWE package file. This IWE package contains:
- Actual Firmware
- Controller help files
- Curves (for Analog Inputs)
- Basic dictionaries
- Updated ECU databases
- Default archives
- Other databases (for Extension modules etc.)

6.1 Importing new firmware


Go to Options -> Import firmware menu to import new firmware (obtained from e-mail, ComAp web
site etc.) to the LiteEdit.

"Import firmware" window appears. Click on icon and select the IWE file you want import.
You will see the contents of the IWE file in the lower part of the window.
Press "Import" button to import the firmware to the LiteEdit.

6.2 Upgrading firmware


Before you start the Firmware upgrade it is recommended to save your original archive and to
make an Archive/Configuration upgrade.
Open any type of online connection.
Press the button on the toolbar to save current archive.

Go to Controller -> Programming and cloning -> Programming and select firmware you want program
to the controller. Firmwares, which are not compatible with the controller, are indicated by grey colour.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 45


LiteEdit-4.6-Reference Guide_r1.pdf
Press "OK" button to programme the firmware to the controller.

After programming is finished, open configuration window and perform the configuration process
manually. There is no compatibility of the configuration between different firmware versions.
Open setpoints window and then go to Setpoints -> Open alternative setpoints menu. Then select the
archive saved at the beginning of the upgrading process.

Go to Setpoints -> Import alternative setpoints to import saved setpoints. Some setpoints like
controller name and controller address are not written by cloning. These setpoints must be adjusted
manually.

In some cases the "wrong setpoints" message can occur in the DDE server status line and the
controller is blocked showing "Init" state. Use Controller -> Reset from Init state menu item to put the
controller to normal operation. Be sure you have checked all setpoints before.

CAUTION!
Check the statistic value "Engine hours" after firmware upgrade. Readjust the value if necessary. The
last valid value can be found in the archive saved before upgrading the firmware.

NOTE:
LiteEdit automatically detect if the firmware in connected controller is up-to-date in relation to imported
ones. If not it automatically offers the newer version.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 46


LiteEdit-4.6-Reference Guide_r1.pdf
6.3 Programming firmware into a non-responding controller
If the controller does not contain valid firmware, a new firmware cannot be programmed standard way.
This situation can occur if the connection between PC and the controller was interrupted e.g. during
previous firmware upgrade. In such a case the controller has blank display and does not communicate
with the PC. The boot-jumper must be used to get a valid firmware into the controller.
Disconnect power supply from the controller, insert a communication module and close the boot-
jumper. See the controller manual for details about communication modules and boot jumper location.
Connect communication cable (appropriate type according to the module used) between the controller
and PC.

IL-NT-RS232 COMMUNICATION MODULE WITH BOOT JUMPER (P1)

IL-NT-S-USB COMMUNICATION MODULE WITH BOOT JUMPER

IL-NT-232-485 COMMUNICATION MODULE WITH BOOT JUMPER (P4)

Start LiteEdit and open connection according to the module used. Select controller address 1. Wait
until the bottom line of LiteEdit will show red line with text "DDE server: Error".
Go to menu Controller -> Programming and cloning -> Programming, select appropriate firmware and
press OK button.

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


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

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 47


LiteEdit-4.6-Reference Guide_r1.pdf
7 Archive/Configuration upgrade
It is possible to upgrade group of archives from older version to the newer one.

Upgrade procedure/dialog can be started from LiteEdit menu Controller → Programming and
cloning… → Archive/Configuration upgrade…

When you start the dialog (picture below) you have to proceed in following way:
1. Press button to choose archive or archives (it has to be the same application
type! For example application SPtM as in the picture below) you would like to upgrade to
target software version.
2. All the chosen archives are then visible in the list of “Input archives”.
3. Choose target archive / target software version.
4. Choose output directory where all the upgraded archives will be stored including upgrade
reports in case there is any warning or error.
5. Once all the above steps are finished you can proceed to next step pressing
button.

Once you do that you will see “Upgrade summary” – the list of archives you would like to upgrade.
Make sure the list is complete. In case you would like to adjust this list you can go back by using of
button and adjust the list by using of , or buttons.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 48


LiteEdit-4.6-Reference Guide_r1.pdf
After you decide to start the upgrade procedure (pressing button) you will see progress
and also state of particular updates in the “Status” column.

After the process is finished you can see report of the upgrade process. When you press
button in “Report” column new window with report is opened (see below). There you
can see information about upgrade including all warnings and/or error messages.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 49


LiteEdit-4.6-Reference Guide_r1.pdf
All report which include either warnings or error messages are also stored in .txt document together
with upgraded archives in the target directory (this may be opened directly from the “Upgrade
summary” window after the upgrade process is finished).

Limitations:
 Archive upgrade is supported for all SW versions based on IL-NT controller (i.e. InteliLite
Classic Line controller archives are NOT supported!)
 Support of target archive versions is limited to all versions including Configuration format 4
and higher (i.e. it is not possible to convert archives into version with Configuration format 3
and lower)

 Only one TYPE of archive can be upgraded at the same time (multiple upgrade is only
possible for archives with the same type of application)
 Source archives may be chosen anywhere on your PC, but in case of multiple upgrade the
archives have to have different names (same names in one upgrade list are not allowed)
 Target SW version is chosen only from archives available on(imported to respective PC (in
case intended SW version is not available in the list it has to be imported into your PC first)
 It is not possible to convert one type of application to another one (AMF to MRS, AMF25 to
AMF20, SPtM to MINT, etc.)

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 50


LiteEdit-4.6-Reference Guide_r1.pdf
8 Cloning
Use cloning function to create an identical copy of one controller to another one. This function can
help you in following situations:
 Replacing defective controller with another controller on one site.
 Production of more identical gen-sets.

The procedure:
A clone must be saved before it has to be used to create a cloned controller. To do this, create any
connection to the "original" controller and go to menu Controller -> Programming and cloning -> Save
for cloning.

"Save clone" window will appear. File name and description of the clone can be modified in this
window. Press "OK" button to save the clone. Clones are stored in "clones" subdirectory in the LiteEdit
home directory.

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 the
clone can't be saved. In such a case the proper firmware has to be imported to the LiteEdit.

Now you can create one or more clones of the original controller. Go to menu Controller ->
Programming and cloning -> Create clone). This menu is available only if the connection is closed.

A window with list of available clones will appear. Please note, that only clones of the same type as
destination controller can be used (e.g. IL-NT AMF25).

Select the clone and press "OK" button to program it to the controller. LiteEdit will now establish the
connection with the controller and the firmware, configuration, setpoints, passwords and access code
will be programmed to the controller.
LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 51
LiteEdit-4.6-Reference Guide_r1.pdf
NOTE:
During establishing of connection you will be asked for controller address and password filling in.

You can repeat the whole cloning process if more clones shall be created.

LiteEdit-4.6, Reference guide Rev.1, ©ComAp – January 2013 52


LiteEdit-4.6-Reference Guide_r1.pdf