Software Installation and Configuration - EN
Software Installation and Configuration - EN
and configuration
IEC-line series
update: 11-01-2014
Table of contents
1. Installing the software .......................................................................................................... 3
1.1. Installing CoDeSys ...................................................................................................................... 4
1.2. Installing IEC-line........................................................................................................................ 4
www.web-plc.com/Download.html
www.overdigit.com/Download.html
The compressed file obtained from this page contains two executable setup files. The first is the
standard setup of CoDeSys, as well as available on the 3S website, while the second is the setup
program specifically for the IEC-line series. The setup of CoDeSys must be executed first because
the second provides for the completion of CoDeSys with all supporting files relating to the PLC of
IEC-line series.
After installation, a folder is created in the Start menu of desktop, which also includes the CoDeSys
main manual in PDF format:
The Target Support Package is a set of files that must be installed on Personal Computers to inform
CoDeSys about the specific characteristics of the target. With the installation of the TSP some files
are added in special folders of the CoDeSys installation path which provide the tools to work with
the specific device.
In particular, are installed the configuration files for the PLC resources, the library files for the
management of specific parts of the target and the online help files integrated in the CoDeSys
menu.
To install TSP must be run the setup program IEC-line_V23xxxx.exe (xxxx current version) of the
installation package:
Follow the instructions of the setup Wizard until the end of the installation process.
With the IEC-line package will be installed all the TSP files under the Targets folder of CoDeSys
standard installation. The Overdigit/IEC-line subfolder will be created (under Programs folder of
PC) containing all the documentation, example programs, a backup copy of RTS files (already pre-
installed on PLC) and other files and programs to support the use of IEC-line series. The setup
program also installs the CHIPTOOL program that allows access and management of the PLC using
some utilities (such as FTP client) to be used in particular for the RTS software update.
The Run Time System consists of a set of files that must be installed on the device to make it work
as a PLC. Normally this is not necessary because RTS files are already installed on the device. Only
in the case of software update may be necessary the replacing of these files. In the following, a
brief description of main parts of RTS.
The main executable file is the RTS program of PLC (for example WP240_RTS.EXE), that runs the
device as PLC programmable with CoDeSys. This file must be present on the FLASH disk (in
"A:\SYSTEM") and its execution must be started at power-on by the AUTOEXEC.BAT file.
In the "A:\SYSTEM" folder there are also some executable files for disks driver and USB auxiliary
programming port (also these exe files are called by the AUTOEXEC.BAT) and some utility and
support applications.
In the root directory "A:\" two very important files are stored.
The first is the CHIP.INI file for general configuration of the system that contains several sections,
each with specific parameters. The file contains the preinstalled optimal parameters for many
applications. However, generally must be redefined the addresses for Ethernet network connection
and any username and password for access. For this purpose, a graphical user interface, based on
the PLC Web server, configures the main parameters.
The second is the AUTOEXEC.BAT file that lists the programs to launch automatically when the CPU
is powered on. It allows you to install the drivers of external hard-disks (USB memory and SD card),
the driver of the USB port (to define a virtual COM for CoDeSys programming), to execute some
support applications and finally the RTS program as PLC engine.
Finally, it is necessary the "A:\PLC_PRG" folder for storing all files of the IEC application program
developed with CoDeSys and executed by RTS.
A complete files/folders copy of standard setup for the target is available in the "Disk_A_image"
folder of the specific PLC under the installation on PC of the IEC-line package.
Address: 192.168.1.101/admin/admin.html
Username: web_user0
Password: web_password0
The home page of PLC administration site contains some general information such as the RTS
software version:
To configure the various parameters follow the instructions in the specific section.
NOTE: After setting one or more configuration values in the page fields, the data must be writed to
the PLC via Send button of the same page.
• IP address
• Netmask
• Gateway
The value of IP address is the network address of the device. Normally in a private network this
address is 192.168.xxx.xxx where xxx marked fields are different for each device on the network.
Netmask defines the value of a bits mask that separate the IP address part used for routing within
the local network (bits to 0) than that used to addressing outside the local network (bits to 1).
Gateway is the specific address of a device connected to the network that performs the functions
of "exit door" between the local network (LAN) and the external network (Internet). In a local area
network the Gateway usually coincides with a modem-router.
Ultimately in a local network there will be multiple devices (modem-routers, Personal Computers,
printers, devices such as the PLC and others) each of which will have its own IP address. When one
of these devices must communicate with another it will send a data packet to the IP address of the
recipient device. If the destination address is internal to the local network (and this is known by the
Netmask), the packet reaches this through the router, but if the address is not internal to the LAN
this is sent to the Gateway which will send the packet outside the network.
In particular the CHIP.INI file of the CPU is preconfigured with the following parameters:
[IP]
ADDRESS=192.168.1.101
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DHCP=0
The predefined local network is using the fourth field to address the connected devices. In
particular, the PLC is at 101 final while the modem router at 1. The Gateway, in this case the
modem-router, has the network address 192.168.1.1.
The choice of the network address of a device can be done either manually (by choosing for
example the value 101), or automatically using the DHCP (Dynamic Host Configuration Protocol)
feature.
In manual configuration must be carefully assigned a unique address to each device connected to a
network. When networks are complex, this assignment requires significant attention by the
network administrator.
In the automatic configuration, toggled by setting the DHCP parameter of CHIP.INI file, the PLC asks
the network Host that is assigned an IP number currently available.
In a typical case of a small local network, where the Host functions are performed by the modem-
router, the DHCP server resides within this unit. The CPU with the parameter DHCP=1 performs the
function of DHCP clients and waits the IP address assignment from the Host. For example, if the
network is already connected to a PC (which has already been assigned the address 192.168.1.2)
and then is connected a PLC, the address 192.168.1.3 can be assigned to this device.
The reason why for the default setting of CPU is preferred not to use this service (DHCP=0) is due to
the fact that, with the dynamic assignment, the addresses order can be different every time
(depending on the active devices on the network). If you do not known the local network address
of the PLC is not possible for the modem-router to open specific ports accessible from outside the
network using NAT functionality.
The NAT (Network Address Translation) service makes the connection from outside the local
network, via the Internet, through translations of addresses. The table of translations associates a
particular request of a service (Web server, FTP server and remote CoDeSys programming) from
outside the network to an internal device of LAN and for this you need to know in advance the IP
address. In a next paragraph will be provided all the information needed to use this feature.
However, in some types of networks, the Web interface could not be immediately accessible
because the network configuration parameters could not be compatible with those programmed
as default inside PLC. For this it is necessary, initially, set the PLC network values in a manner
compatible with the LAN using the CHIPTOOL utility program:
With the start of the CHIPTOOL program is constantly scanned the network for all PLC devices
connected (the scanning can be stopped later with Stop button).
The window shows some information about the PLC connected and in particular the network
parameters currently set on the CHIP.INI configuration file.
To change the value of the DHCP parameter (for the service enabling) and others network
parameters, position the mouse cursor on the specific line of the device and press the right button
to activate the context menu as follows:
The IP address of the PLC is automatically proposed while the User and Password fields should be
properly set equal to the values currently stored on the CHIP.INI file.
In the CPU pre-installation the default values are:
Username: ftp_user0
Password: ftp_password0
The CHIP.INI file provides for the possibility of having two separate users (0 and 1) each with its
own User and Password values.
An extract of the file section on CHIP.INI for the FTP connection parameters is as follows:
[FTP]
…
USER0=ftp_user0
PASSWORD0=ftp_password0
…
USER1=ftp_user1
PASSWORD1=ftp_password1
In the absence of definition lines regarding USER and PASSWORD by default are defined two special
users:
The connection option "Use passive mode" must be enabled in the case of remote connection via
the Internet.
Confirming the connection with the "Connect" button to access the files window:
On the left side is available the folders/files tree of the Personal Computer while, on the right side,
the files of the PLC.
This tool allows the execution of some commands such as view, edit, copy, move and delete files
and folders and perform the PLC FLASH disk operations. In this way the CHIP.INI and
AUTOEXEC.BAT files can be customized and can be managed all the files of the IEC program in the
"A:\PLC_PRG" folder.
www.java.com/download/index.jsp
To access Web pages created by CoDeSys, in the case of PLC configured with default parameters,
use the following values:
Address: 192.168.1.101
Username: web_user0
Password: web_password0
After loading the Java application on the PC, the home page, created in the IEC program, will be
viewed. Each page corresponds to an XML file (generated by CoDeSys and transferred to the PLC)
that will be downloaded and subsequently interpreted by the local Java program, leaving to the
network communication only the exchange of the values displayed on the page.
The two Personal Computers, with the DHCP client enabled (option "Obtain an IP address
automatically" in the properties of the TCP/IP Internet protocol), make request to the router of its
own unique network address. The modem-router then assigns the network address 192.168.1.74,
192.168.1.2 to the PC's.
The PLC, with DHCP automatic assignment disabled, is configured at 192.168.1.101 as programmed
in the CHIP.INI configuration file.
At this point the Gateway (ADSL modem), the two Personal Computers and the PLC form a private
network. Through each of the two PCs, the CPU disk can be accessed with FTP connection, the PLC
can be programmed and the pages of CoDeSys visualization viewed by a Web browser. The PLC
can also directly access outside the network, for example by sending E-mail or synchronizing the
clock with a NTP server.
FTP 21
HTTP (Web browser) 80
Telnet 23
CoDeSys 1200
In this example the NAT service is accessible via the "Port Mapping" menu. It should be added the 4
rows in the table of virtual servers. Normally there is a predefined list of virtual servers such as FTP,
HTTP and Telnet. It may be possible to manually define all four services with the "Custom Virtual
Server":
The purpose of this table is to redirect an external request of a particular service directly to the IP
address of the LAN device that offers this service.
For example, when CoDeSys wants to remotely access the PLC, it sends packets with the TCP/IP
internet address associated with the ADSL modem and the port address 1200. The modem-router,
looking at this table, will send packets to address 192.168.1.101 of the PLC. At this point, the PLC
responds to the sender, transmitting own data packets. As the answer destination is outside the
local network, the Gateway (or modem) sends this data to the external network and so the replay
is returned to the remote PC on which CoDeSys operates.
Similarly are accessed from the outside, on a different port addresses, other services such as Web
server and the FTP connection.
The presence of a dynamic IP makes it very difficult to access from outside the services locally
performed by a network device because this address may vary and consequently the remote
computer will not have the address information.
For this reason, could be necessary the use of a Dynamic DNS (Domain Name System) capable of
continuously match the value of dynamic IP address to a well-defined naming convention.
The DNS servers are very important for Internet because it can translate a name of a website into
the corresponding IP address as it happens in a telephone directory for a name and the related
telephone number. It is much easier to type the name of a site rather than its IP address.
The service provided by "dyndns.com" and other similar sites, as “no-ip.com”, is also very useful in
the case of dynamic IP addresses. Normally these sites offer the service with an inexpensive
subscription but are also possible free accounts as in the case of "no-ip.com".
Now will be recorded, by way of example, the third level domain "myplc.no-ip.org" to be
associated with the IP of the modem-router which is connected to the PLC:
Using the "Sign Up Now" button a simple registration form of the service is visualized:
In the Hostname field, type the name chosen for the PLC (in the example "myplc").
Confirming the subscription, the following page is viewed:
To complete the registration, must be accessed the E-mail account, specified in the previous form,
clicking on the link received in the confirmation E-mail.
At this point, the registration of the name associated with the PLC is ended.
To maintain updated, on the DNS server, the correspondence between the dynamic IP address and
the Internet "myplc.no-ip.org" address, the modem-router must be configured with the
information about this service:
In particular, under the "Dynamic DNS" menu you have to add a row to the table providing the full
name of the Host ("myplc.no-ip.org"), the Username and Password chosen when registering to
the service and selecting the DNS server provider ("no-ip.com").
The modem-router, so configured, will operate as a dynamic DNS client, and the dynamic IP will be
constantly updated on the DNS server.