Professional Documents
Culture Documents
Reference Guide
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
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
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.
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.
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\
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
Firmwares
\LiteEdit\ \App\
*.mhx, *ipt
Dictionaries
\Dict\
*.tm
\Displays\ Fonts
Default
\Archives\ \Default\ archives
*.aic, *.ail
User created
archives
\Connections\ *.con
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.
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.
Close connection
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.
CROSSED-WIRED
RS232 RS232 CABLE USB
RS232
IL-NT RS232
USB
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.
Ethernet
IL-NT RS232 RS232
LAN / WAN / RJ45
IL-NT RS232-485
GSM INTERNET
MODEM
BTS / Mobile
provider
OR
Ethernet
IL-NT RS232 RS232 LAN / WAN / RJ45
IL-NT RS232-485 INTERNET
ANALOG
MODEM
OR
NOTE:
Recommended modems are listed in IL-NT, IA-NT, IC-NT Communication Guide.
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!
NOTE:
A plug-in communication module is required for controllers IL-NT, IC-NT and derived types.
Static IP
Ethernet Ethernet
RJ45 LAN / WAN / RJ45
IB-Lite
INTERNET
Static (Public) IP
Ethernet
LAN / WAN / RJ45
IL-NT GPRS
INTERNET
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
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.
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
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.
When the prepared archive is finished save it by pressing button to archive file.
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.
NOTE:
Archive files are using different extensions according to the type of controller. InteliLite based
controllers use *.AIL, InteliCompact based *.AIC and InteliPro *.AIP.
CAUTION!
DDE server must be running during any connection except off-line. Do not close it manually!
Running (Reading
green The connection is running and history is being read
history)
TAPI: unavailable modem Communication port is being used by other communication device.
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.
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.
Control window
Setpoints adjustment
Values window
History window
Users/password
Modify configuration
Languages/translator
Import Language
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.
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.
NOTE:
Pressing F1 will open context help window for the selected value, if the help is available for the
particular controller firmware and value.
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.
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.
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.
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.
Press the Save as button to save the configuration to disk. This is recommended before writing it to
the controller for backup purpose.
Controller functions
Binary inputs
Binary outputs
Analog inputs
Analog outputs
Extension modules
Password protection
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.
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.
Select type of the input in the Config section. Analog input can be used as Analog, Binary or Tristate
input.
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.
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.
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.
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.
The left column contains the physical value of the configured value (object)
The right column contains the appropriate output level (always in % of PWM).
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.
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.
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.
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".
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".
Press button in the configuration window to change power format and ECU units.
Power format can be changed in Power format window.
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.
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.
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.
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.
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.
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.
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.
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.
"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.
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.
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.
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.
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.
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.
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.)
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.