LiteEdit 4.4 Reference Guide

LiteEdit
Monitoring Tool for ComAp Controllers

To be used with ComAp controllers:
IL MRSXX, IL AMFXX, IL-NT MRSXX, IL-NT AMFXX, IC-NT SPtM,

IC-NT MINT
SW Version 4.4, October 2009
REFERENCE GUIDE
Copyright © 2008 ComAp s.r.o.
ComAp, spol. s r.o.

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
Table of contents ..................................................................................................................................... 2
Document information ............................................................................................................................. 3
Clarification of notation........................................................................................................................ 3
What is LiteEdit?...................................................................................................................................... 4
Installation ........................................................................................................................................... 4
LiteEdit directories .......................................................................................................................... 5
PC Hardware requirements ............................................................................................................ 5
Help ..................................................................................................................................................... 6
Communication........................................................................................................................................ 7
Direct connection ................................................................................................................................ 8
Modem connection.............................................................................................................................. 9
Internet connection............................................................................................................................ 10
Predefined connection ...................................................................................................................... 12
Offline connection ............................................................................................................................. 14
Close connection / Save archive....................................................................................................... 15
DDE Server ....................................................................................................................................... 16
DDE Server status line ................................................................................................................. 16
DDE Server error messages ............................................................................................................. 16
Users/password ................................................................................................................................ 17
LiteEdit functions ................................................................................................................................... 19
Control window.................................................................................................................................. 19
Setpoints window .............................................................................................................................. 20
Values window .................................................................................................................................. 21
Statistics window............................................................................................................................... 23
Statistics setup.............................................................................................................................. 24
History window .................................................................................................................................. 24
Export data ........................................................................................................................................ 25
Controller configuration ..................................................................................................................... 26
Configuration window ................................................................................................................... 27
Configuration steps ....................................................................................................................... 27
Binary inputs ................................................................................................................................. 28
Binary outputs ............................................................................................................................... 29
Analog inputs ................................................................................................................................ 29
Analog outputs .............................................................................................................................. 31
Conversion curves ........................................................................................................................ 32
Extension modules........................................................................................................................ 33
Password protection ..................................................................................................................... 39
Units and power format selection ................................................................................................. 39
Init screen ..................................................................................................................................... 40
Controller languages ............................................................................................................................. 41
IL-NT, IC-NT...................................................................................................................................... 41
IL-Classic........................................................................................................................................... 42
Create language................................................................................................................................ 42
Making translations ........................................................................................................................... 43
IL-NT, IC-NT ................................................................................................................................. 43
IL-Classic ...................................................................................................................................... 46
Import language ................................................................................................................................ 47
Firmware upgrade ................................................................................................................................. 49
Importing new firmware..................................................................................................................... 49
Upgrading firmware........................................................................................................................... 49
Programming firmware into a non-responding controller .................................................................. 50
Cloning................................................................................................................................................... 51
LiteEdit-4.4, Reference guide, ©ComAp – October 2009 2

LiteEdit-4.4-Reference Guide.pdf
Document information
LITEEDIT - REFERENCE GUIDE
WRITTEN BY: JAN TOMANDL AND REVISED BY: FRANTISEK POUPE
©2009 COMAP LTD.
KUNDRATKA 17, PRAHA 8, CZECH REPUBLIC
PHONE: +420246012111, FAX: +420266316647
WEB: 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
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
unproper 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.

What is LiteEdit?
LiteEdit is Windows 2000/XP/Vista based software which provides following functions:
• Direct, off-line, modem or internet communication with the controller

• Controller configuration
• Controller firmware upgrade
• Read / write / adjust setpoints
• Read measured values
• Display controller history
• Export data into a XLS file
NOTE:
LiteEdit supports InteliLite®, InteliLite-NT® and InteliCompact-NT® controllers.
Installation
Execute the "ComAp PC Suite" installation package (i.e. IC-NT-Install-Suite-1.1.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.
NOTE:
The controller firmware will be installed together with the LiteEdit. New firmwares can be installed into
the LiteEdit also later using import of the IWE packages. See the chapter Firmware upgrade.

LiteEdit directories
LITEEDIT DIRECTORY STRUCTURE
PC Hardware requirements
LiteEdit is based on Windows 2000/XP/Vista platform. Use PC suitable for this platform. There are no
special requirements for the PC hardware. LiteEdit requires approx. 10 Mbyte of hard disc free space.
NOTE:
Use Help->About to display current LiteEdit version window.

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 setpoint,
values or configuration window will open the controller help with the context of currently selected
setpoint, value and binary input or output function.

Communication
There are following types of connection to a controller available:
• Direct cable
• Modem
• Internet
• Offline
See also controller manual for information about communication possibilities for the particular
controller.
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.
Open direct connection
Open modem connection
Open internet connection

Open off-line connection
Open predefined connection
Close connection
Direct connection
Connect RS232 or USB cable between InteliLite 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.
DIRECT CONNECTION TYPES
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.

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.
MODEM CONNECTION TYPES
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.
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.

INTERNET CONNECTION TYPES
Predefined connection
The connection setting can be saved to a file and used later as prefedined connection. All necessary
settings are stored in the file, so when openning 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 file *.con.

Offline connection
All data from a controller can be saved during any connection to an AIL file (called "archive") like a
snapshot and open later in offline mode using icon.

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>yyyymmddvv.ail.
• 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.
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!
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 -> Informationto get detailed information.
STATUS LINE COLOR MEANING
Running green The connection is running, no problems occured
Running - The connection is running, but checksum of setpoints is not valid

green
wrong setpoints (occurs typically after firmware is upgraded)
Running -
green The connection is running and history is beeing read
reading history
Preparing yellow The DDE server is building-up the connection to the controller
The connection failed. Use ALT-TAB, select DDE Server and press
Error red the "Last errors" button at the controller with appropriate address to
see more information
DDE Server error messages
Connected controller does not answer to DDE server requests.

Probable reasons:
Timeout (continuous)
• The controller is not connected or switched off

• The communication cable is wrong
• 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
Communication port is beeing used by other communication

TAPI: unavailable modem
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
TAPI: Can't create with the 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
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 can not be changed.
Use icons to enter or deactivate password. The icon also shows if the controller is currently
unlocked or not.
NOTE:
Password entering in LiteEdit enables to access Setpoints from LiteEdit only, not from controller front
panel and vice versa.
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 then 9999.

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 *.ail archive
Control window
Setpoints adjustment
Values window
History window
Users/password
Open configuration from an *.ail archive
Modify configuration
Languages/translator
Import Language
Control window
Control window is active for online connections only and has two basic functions:

• Controller mode change
• Manual genset control via buttons like from
Remote genset control
controller front panel.
• State machine indication.

• Mains, genset and breaker states LED indication.
Genset states indication and
• Alarm list, ECU Alarm list.
values reading
• Reading of actual values measured from genset.
Setpoints window
The setpoints window enables to adjust value of each setpoint present in the controller. Password
protected setpoints have gray 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.
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.

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.
• In case of some (BIO) Extension plug-in modules their channels can be configured as binary
input (labeled as IN:) or binary output (labeled 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.
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.

Statistics setup
• Password must be entered 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.
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 occured.
• 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.
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.

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 modifing the configuration.

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.
Configuration steps
• Binary inputs
• Binary outputs
• Analog inputs
• Analog outputs
• Extension modules
• Password protection
• Units and power format selection
• Init screen welcome text
Binary inputs
Go to the upper left part of the configuration window and click to the appropriate input to configure it.
• 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.
Binary outputs
Select desired function from the list at each output.
Analog inputs
Go to the lower left part of the configuration window and click to the appropriate input to configure it.

1. Configure the function of the input - Alarm input or not used input.
2. For Alarm inputs enter name of the input to the field in Name section.
3. Select type of the input in the config section. Analog input can be used as analog, binary or
tristate input.
4. 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)
5. 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.
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)

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.
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 loger 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 throug 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.
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)
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, 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 an user-definable sensor (Curve A,
Curve B, Curve C). When you select a predefined one, you can not modify points. For user-definable
sensors you can modify everything as desribed above.
NOTE:
There is an input range limitation. It is possible to insert only values from 0 to 15000 ohms.
Analog outputs
The curve definition window for the particular analog output opens when you press the
button in the analog output configuration window.
• 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).
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)

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.

Modules of analog inputs and analog outputs (e.g. IL-NT-AIO)
• 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.
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.

IOM/PTM module
Press button in the configuration window to configure IOM/PTM module.
• 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.

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 color selection can be modified on the RA15 directly during the setup process. Please
see the documentation of the RA15 module.

Electronic controlled engines
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 you your ECU type is not listed and the ECU communication protocol is based on SAE J1939, try to
select "Standard J1939 engine".

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

Controller languages
IL-NT, IC-NT
It is possible to have 2 languages in the controller. It is recommended to have english language in the
language slot #1 and customer language in the slot #2.
The procedure of adding a new language is following:
1. Open the target archive or connect to the controller. Use any type of connection.
2. Click on the button to open the Translator window.

3. Create new language
4. 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.
Preffered 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 controler itself!

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 can not be reverted back to english simple way.
Create language
Creating a latin language:
1. Use the button to remove the 2nd language and keep only the english one.

2. Click to the button and create new language based on english.
3. 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.
4. 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.
Making translations
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.

1. 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 an 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.
NOTE:
The translations are searched in the working dictionary first and if it is not found there, then
the default dictionary is used.
2. Now untranslated items (that are not present in any dictionary) are shown in cyan color,
translated by user dictionary are white and translated by default dictionary are gray.

3. 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)
4. 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.
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 can not 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 color,
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.

• 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.
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:
1. Open the target archive or connect to the controller. Use any type of connection.
2. When you click on the button Import language dialog appears.

3. Select language you would like to import on the left side of the dialog window (list of available
languages).
4. In case there is a free slot on the right side (in controller) you can add new language using
button.
5. In case the second controller slot is not free you can use button to replace
currently present language (in controller) by selected available language.
6. In case the second controller slot is not free you can use button to remove
second language from controller.
7. When the import 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.

Firmware upgrade
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.
Upgrading firmware
• 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 gray color.
• Press "OK" button to programm 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.
Programming firmware into a non-responding controller

If the controller does not contain valid firmware, a new firmware can not 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.
1. 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
bootjumper location.
2. Connect communication cable (appropriate type according to the module used) between the
controller and PC.
3. 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".
4. Go to menu Controller -> Programming and clonning -> Programming, 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.

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:
1. 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 Controler -> Programming and
cloning -> Save for cloning.
2. "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.
3. 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.
4. Now you can create one or more clones of the original controller. Go to menu Controler ->
Programming and cloning -> Create clone). This menu is available only if the connection is
closed.
5. 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).

6. Select the clone and press "OK" button to program it to the controller. Firmware, configuration,
setpoints, passwords and access code will be programmed to the controller.
7. You can repeat the whole cloning process if more clones shall be created.


LiteEdit 4.4 Reference Guide

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

LiteEdit 4.4 Reference Guide

Enviado por

Direitos autorais:

Formatos disponíveis

LiteEdit

Monitoring Tool for ComAp Controllers

IL MRSXX, IL AMFXX, IL-NT MRSXX, IL-NT AMFXX, IC-NT SPtM,

SW Version 4.4, October 2009

Copyright © 2008 ComAp s.r.o.

ComAp, spol. s r.o.

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 2

REVISION NUMBER RELATED SW. VERSION DATE

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 3

• Direct, off-line, modem or internet communication with the controller

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 4

LITEEDIT DIRECTORY STRUCTURE

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 5

• LiteEdit help will display this help.

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 6

Open direct connection

Open modem connection

Open internet connection

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 7

Open predefined connection

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 8

DIRECT CONNECTION TYPES

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 9

MODEM CONNECTION TYPES

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 10

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 11

The Open predefined window shows the list of predefined connections.

• Use buttons above the list to manage the connections.

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 12

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 13

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 14

Following dialog box appears during closing of connection:

Archive file is saved under automatic name: <gen-set name>yyyymmddvv.ail.

• Gen-set name is taken from the setpoint

Save as command enables change the name of the AIL file.

• Click on Last errors to see report of the last error message.

DDE Server status line

STATUS LINE COLOR MEANING

Running green The connection is running, no problems occured

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

DDE Server error messages

Connected controller does not answer to DDE server requests.

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 16

Occasional timeouts can be caused by overloading of your

TAPI: requested modem

Communication port is beeing used by other communication

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

It is not possible to open connection. Probable reasons:

• When "beeping" is audible during start of the connection,

Changing the password:

1. Open any type of online connection to the controller

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 18

LIST OF AVAILABLE FUNCTIONS

Save *.ail archive

Open configuration from an *.ail archive

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 19

• State machine indication.

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 20

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 21

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 22

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 23

• Password must be entered to enable statistic setup.

• Each record contains date and time it was recorded.

LiteEdit-4.4, Reference guide, ©ComAp – October 2009 24