|
QUESTION:
Can automation systems be started up only via IE?
ANSWER:
Under certain circumstances it is possible to start up
automation systems exclusively via IE. Node initiation via MPI is
then no longer necessary.
Hardware requirements:
- Automation system S7-300 or S7-400 with IE CP
- PG/PC/Notebook with Ethernet network cared (e.g. CP1612,
CP1613, etc.)
The following CPs with IE interface can be used:
- CP343-1 with EX11 release 02 and higher, FW 2.0.0, at least
STEP 7 V5.1+SP2
- CP343-1 IT with GX11 release 01 and higher, FW 2.0.7, at least
STEP 7 V5.1 +SP3
- CP443-1 with 6GK7 443-1EX11-0XE0 release 3 and higher, FW
V2.0
- CP443-1 IT with 6GK7 443-1GX11-0XE0 release 2 and higher, FW
V2.0
Software requirements:
- STEP 7 with NCM S7 for IE and SOFTNET-PG. Remark: STEP 7
includes NCM in versions STEP 7 V 5.x and higher.
- PC with LAN connection, ISO protocol must be installed (the
S7ONLINE access point must be assigned to this).
Function:
At the "Initial Startup" via IE, the controller system is addressed
via the MAC address of the CP. The Ethernet CPs are provided in the
works with a unique MAC address, which is printed on the modules
and must be entered when configuring the CP. In the case of
addressing via MAC address, you must make sure that S7ONLINE access
point is set to "ISO protocol". You do this setting in the SIMATIC
Manager:
Fig. 1 ( 36 KB )
In this example the following configuration has been
selected:
- Rack CR3
- PS 405, 4A
- CPU416-2 DP
- CP443-1 IT
Note:
The modules are taken directly out of the original packaging and
are not configured!
There are in principle several options for starting up an
automation system for the first time via IE:
- Via direct connection between CP and PC (STEP 7 is installed
on the PC):
The twisted-pair cable connects the J45 connections of
the CP with the Ethernet network card of the PC. In the case of
direct connections, you must use a crossed twisted-pair
cable.
The CP is connected with the STEP 7 PC via an active
network component (e.g. hub, switch bridge) via a twisted-pair
cable. Routers cannot be used for initial addressing.
Below are the configuration steps for initial startup of the
above-mentioned system illustrated with screen shots.
- Create an S7 project and the hardware configuration, open the
Properties dialog for parameterizing the CP and select the
properties:
Fig.
2 ( 41 KB )
- In the Properties dialog you must enter the MAC address printed
on the CP in the works (2a). Here via the subnetwork mask you can
also define the IP address for later addressing via TCP/IP. The
initial addressing of the module however must be done via the
MAC address. The CP must still first be networked (2b).
Fig.
3 ( 42 KB )
- Checking that the CP is networked:
Fig.
4 ( 41 KB )
- Saving and compiling the hardware configuration (generation of
the SDB):
Fig.
5 ( 38 KB )
- Loading the configuration into the controller. There is a
display of the address the PC uses to connect to the CPU: the CP is
connected to the CPU via the backplane bus.
Fig.
6 ( 41 KB )
- Loading the system data deletes the data blocks generated in
the CPU by SFC. Acknowledge this procedure positively. >
- During loading the CPU is set to STOP and the system queries
whether the module should run a restart. Acknowledge this procedure
positively.
- Whilst the module is being restarted, for the initial
addressing via IE, you have the following system behavior: the
connection between CP and PC clears down for a short time. This
connection clear-down is shown in the task bar.>
Fig.
7 ( 74 KB )
- After a short time the connection sets up again. Repeat the
procedure. The hardware configuration is then loaded successfully.
The LED displays of the automation system light green.
Fig. 8 ( 45 KB )
Note:
This system behavior occurs in automation systems in which the
CP is connected directly with the STEP 7 PC. This only happens the
very first time the hardware configuration is loaded via CP using
IE. The modules are original modules straight from the packaging
without any previous configuration. If there is already a
configuration on the automation system, this system behavior does
not occur.
|