QUESTION:
Why does an error occur when downloading the configuration via
LAN into the IE-CP?
ANSWER:
You are using one of the following multiprotocol communications
processors, via which you want to download the configuration into
the IE-CP:
|
CP 443-1 A2
|
6GK7 443-1EX10-0XE0
|
(V1.0.0 and higher)
|
|
CP 443-1 A2
|
6GK7 443-1EX11-0XE0
|
(V1.0.0 and higher)
|
|
CP 443-1 IT
|
6GK7 443-1GX10-0XE0
|
(V1.0.0 and higher)
|
|
CP 443-1 IT
|
6GK7 443-1GX11-0XE0
|
(V1.0.0 and higher)
|
All stations are connected via an Industrial Ethernet
communications process to the LAN (local area network).
In this case it is possible to provide all stations centrally with
a configuration via this LAN.
Note:
If a communications process is in "STOP" mode, then no other
modules can be reached via the LAN via the K bus in the same rack.
This applies both for downloading processes and for diagnostics
connections.
However, the CP itself can be diagnosed in the STOP mode.
If data management is on the CP and the CPU is therefore not the
carrier of the configuration data, then the configuration for the
communications processor can also be downloaded via the LAN in STOP
mode.
Example:
A station is available with an S7-400 CPU and an Industrial
Ethernet CP. The data management is in the communications processor
itself. After triggering the download process from the hardware
configuration, the following dialog is displayed:
_NET_Projektierung_LAN_1_e.gif)
Since the data management is in the communications processor and
this is in "STOP", only the CP 443-1 can be selected as component
to be downloaded. The download process starts but is very quickly
aborted with the following warning message:
_NET_Projektierung_LAN_2_e.gif)
Cause:
No connection to the CPU can be set up to generate the system data.
The connection is necessary, because the downloading tool generates
new system data blocks (SDBs) in the hardware configuration when
downloading the configuration. In doing so it reads the numbers of
the SDBs already available in the CPU. This is to prevent that a
station is generated twice with the same number for different SDBs.
Without this consistency check there could be an SDB with the
identical both on the CPU and on the CP. This would not have any
negative effects as such, but is not desirable for the overall
concept of maintaining data consistency.
Remedy:
If a CP is to be downloaded despite the "STOP" mode, then you can
ignore the message. The station will still start up properly
afterwards.
This procedure can be useful, for example, to interrupt
communications to other CPs when changing the parameters of the
communications processor.
Note:
After such a download you should still reload the complete station
to ensure station-wide consistency in compliance with STEP 7
philosophy.
Keywords:
Hardware configuration, Download, Operating mode
|