CP 443-1 Advanced Manual Part B
CP 443-1 Advanced Manual Part B
Manual Part B
CP 443-1 Advanced
6GK7 443−1EX41−0XE0 Version 1 or higher (Firmware Version V1.0)
for SIMATIC S7−400
C−PLUG
LED displays
Mode selector
Port 1
Port 4
Release 12/2008
C79000-G8976-C214−03
Notes on the Product
Notice
Make sure that you read the information regarding extended functions and
restrictions in Chapter 9 of this manual!
Note
Please note the detailed description of the IT functionality in the Information
Technology in SIMATIC S7 manual (entry ID = 24845107) or Part A of the manual
(as of Release 04/2008, entry ID = 30335356). For the entry ID, refer to Section
14.
The CP 443-1 Advanced described here differs slightly In terms of the organization
of the file system. The information in this device-specific manual is valid.
You can also obtain this manual from the Internet:
http://support.automation.siemens.com/WW/view/en/1172744
Contents − Part A
S7-CPs for Ind. Ethernet − Configuring and Commissioning . . . . See General Part
Note
Please note Part A of the manual mentioned here. This also belongs to the
description of the CP. Among other things, this includes the explanation of the
safety notices used, Internet addresses and references as well as information that
applies to all S7−CPs for Industrial Ethernet.
The general Part A version 1/2005 or higher also belongs to this Part B of the
manual.
You can also obtain the current general Part A from the Internet at:
http://support.automation.siemens.com/WW/view/en/30374198
or
http://support.automation.siemens.com/WW/view/en/27103175
Contents − Part B
Notes on the Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−2
1 Properties and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−6
2 Requirements for Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−11
3 Installation and Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−13
3.1 Procedure / Steps in Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−13
3.2 C−PLUG (Configuration Plug) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−16
3.3 Module Replacement without PG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−18
4 Displays and Mode Selectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−20
5 Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−23
5.1 General Characteristic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−23
5.2 Characteristic Data for S7 Communication . . . . . . . . . . . . . . . . . . . . . . . B−24
5.3 SEND/RECEIVE Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−25
5.3.1 Characteristic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B−25
5.3.2 Number of simultaneous SEND/RECEIVE calls . . . . . . . . . . . . . . . . . . B−27
5.4 Characteristics of Open TCP/IP Communication . . . . . . . . . . . . . . . . . . B−28
5.5 Characteristic Data for PROFINET IO . . . . . . . . . . . . . . . . . . . . . . . . . . . B−29
5.6 Characteristic Data for PROFINET CBA . . . . . . . . . . . . . . . . . . . . . . . . . B−30
Application
The CP 443-1 Advanced communications processor is designed for operation in an
S7-400 (not fault-tolerant) programmable logic controller. It allows the S7-400 to be
attached to Industrial Ethernet.
To set up small local area networks or to connect several Ethernet devices, a
4-port switch with autocrossing and autosensing has been integrated in the
CP 443-1 Advanced.
Communication Services
The CP 443-1 Advanced supports the following communication services:
S PROFINET IO Controller
PROFINET IO allows direct access to IO devices over Ind. Ethernet.
S PROFINET CBA
Use of a SIMATIC S7−400 for Component based Automation on the basis of
the new PROFINET standard of the PNO. This standard allows:
− Component technology in automation
− Graphic configuration of communication between intelligent devices instead
of laborious programming
− Vendor−independent, plant−wide engineering
S S7 communication with
− PG functions
− Operator monitoring and control functions
− Data exchange over S7 connections
S S5-compatible communication with
− SEND/RECEIVE interface over ISO transport connections;
− SEND/RECEIVE interface over TCP connections, ISO-on-TCP and UDP
connections;
With the SEND/RECEIVE interface via TCP connections, the CP 443-1 IT
Advanced supports the socket interface to TCP/IP available on practically
every end system.
− Multicast over UDP connection
The multicast mode is made possible by selecting a suitable IP address
when configuring connections.
Project engineering
You can configure the CP 443-1 Advanced over MPI or LAN/Industrial Ethernet.
You require the following version of STEP 7 with NCM S7:
Table 1-1
Note
Note the recommendations in Section 10.4 on operation with a higher
communications load.
Table 1-2
To operate PROFINET CBA, you require the current service packs of SIMATIC
iMap containing the current FB88/FB90:
SIMATIC iMap as of V2.0 − Download Service Pack 2:
http://support.automation.siemens.com/WW/view/en/23291636
SIMATIC iMap STEP 7 add−on as of V3.0 − Download Service Pack 1:
http://support.automation.siemens.com/WW/view/en/26574438
Note: At the time of going to print, the entry ID for this download was not yet
available. As soon as the entry is available, you will also be able to locate it using
the search function provided with the link specified here.
Table 1-3
Function Requirement
Transfer of data fields <= 240 bytes S You require the blocks AG_SEND FC5 and AG_RECV
FC6 or alternatively the blocks AG_LSEND FC50
and AG_ LRECV FC60.
Transfer of data fields > 240 bytes S You require the blocks AG_LSEND FC50 and
AG_LRECV FC60.
For a detailed description of these blocks, refer to the general part of this manual
/Part A/).
Notice
We recommend that you always use the current block versions for all module
types.
You will find information on the current block versions and the current blocks to
download from the Internet in our customer support.
http://support.automation.siemens.com/WW/view/en/8797900
With the older module types, this recommendation assumes that you are using the
latest firmware for the particular block type.
Configuration Limits
When using the CP type described here, the following limits apply within a rack:
S Max. number of CPs: 14
S Number of CPs operating as PROFINET IO controllers: 4
S Number of CPs that can be configured for PROFINET CBA communication
within an S7 station: 1 (system property)
Notice
S The number of CPs operating as PROFINET IO controllers depends on the
number of CP 443−5 Extended modules operating as DP masters in the
S7−400 station. A total of 10 CPs can be operated as controllers for the
distributed I/O (PROFINET IO controllers or DP masters); of those, however,
only up to 4 as PROFINET IO controllers.
S Please note the following regarding multiprocessor mode: When operating the
CP as a PROFINET IO controller, only the process image of the assigned CPU
can be distributed via the CP.
System Environment
The CP 443-1 Advanced is supported by the S7-400 CPUs and CPU operating
systems with the order numbers as shown in the following table.
S The function block FB90 (PN_InOut_Fast) for PROFINET CBA is supported
with all CPUs as of version V4.1.
S Open TCP/IP communication is supported with all CPUs as of version V4.1.
The table also contains the following information:
S The number of CPs that can be operated with one CPU
S The number of AG_SEND or AG_RECV calls that can be used at the same
time on the SEND/RECEIVE interface
S Which CPUs support the LOCK/UNLOCK function with the FETCH/WRITE
services
S Which CPU supports operation of the CP as PROFINET IO controller.
CP 443−1 Advanced
Switch Switch
Switch
Caution
When installing the CP for use as a PROFINET IO controller, note the following
points about the power supply:
When using the CP in the central rack or in a universal rack operating as central
rack, you should not insert or remove the CP 443−1 Advanced when the power is
on. If you remove the CP when the power supply is on, the CPU changes to STOP
and indicates “I/O error” (in contrast to previous modules!).
After inserting the module with power applied, it is essential to turn the power
supply off and on again.
Note:
If the CP is operated without PROFINET IO, it is possible to insert and remove the
CP when the power is no without affecting the CPU.
Exchangeable C−PLUG
The CP has an exchangeable configuration plug (C-PLUG). This can store up to
32 MB of data in nonvolatile memory.
The retentive parameters include:
S IP address and IP parameters
S A newly set MAC address
S LAN settings
S Interconnection information for PROFINET CBA
S Data in the flash file system (see also Flash Area in Section 5.10 Memory
Organization)
S SNMP Variables (modifiable)
This configuration plug simplifies replacement of modules. By simply exchanging
the plug, all the data can be transferred to the replacement module.
Notice
The CP will not start up without a C-plug!
Area of Application
The C−PLUG is an exchangeable medium for storing configuration and project
engineering data of the basic device (CP 443−1 Advanced). This means that
configuration data remains available if the basic device is replaced.
Principle
The power is supplied by the basic device. When powered down, the C−PLUG
retains all data permanently.
Figure 3-1 Fitting the C−PLUG in the CP and Removing It from the CP with a Screwdriver
Function
If the C−PLUG has not yet been written to (as shipped), when the device starts up,
all the configuration data of the CP is saved automatically on it.
If the C−PLUG is inserted, the basic device automatically uses the configuration
data of the C−PLUG. This assumes that the data was written by a compatible
device type.
If a fault occurs, the basic device can then be replaced much faster and more
simply. If a device needs to be replaced, the C−PLUG is simply taken from the
failed component and inserted in the replacement. As soon as it starts up, the
replacement automatically has the same device configuration as the failed device.
Diagnostics
Inserting a C−PLUG containing the configuration of an incompatible device type or
general malfunctions of a C−PLUG are signaled by the diagnostic mechanisms of
the CP (F LED red).
General Procedure
The configuration data for the CP 443-1 Advanced is stored on the CPU; this
means that the module can be replaced with the module of the same type
(identical order number) without a PG.
For information on replacing previous modules, please refer to the section
“Compatibility”.
Notice
The “Replace module without PG” functionality (configuration data stored on the
CPU) can no longer be used fully after downloading PROFINET CBA
interconnections since the interconnection information is stored only on the CP.
You have the following two options:
S Using the C−PLUG in new modules
You insert the previously used C−PLUG in the replacement module;
interconnection information is then available again.
S Using a new module with a new C−PLUG
After replacing a module, you must download the interconnection information to
the new CP using SIMATIC iMap.
Notice
When replacing modules, remember that the factory-set MAC address of the new
module is different from the previous module. When the factory-set MAC address
of the new module is sent to the DHCP server, this will return either a different or
no IP address.
Ideally, you should therefore configure IP as follows:
Always configure a client ID if you want to obtain the same IP address from the
DHCP server after replacing the module.
If you have configured a new MAC address instead of the factory-set MAC
address (generally the exception), the DHCP server always receives the
configured MAC address and the CP obtains the same IP address as the replaced
module.
LED Display
The display on the front panel has seven LEDs to display the mode has been
extended by an additional display with two LEDs beside the RJ-45 jack to display
the communication status (covered by the front flap).
INTF
Front RJ-45 jack: LINK
EXTF
panel: BUSF
TXD RX/TX
RXD
INTF LED EXTF LED BUSF LED RUN LED STOP LED CP Operating Mode
(red) (red) (red) (green) (yellow)
Starting (STOP−>RUN)
Running (RUN)
Stopping (RUN−>STOP)
Stopped (STOP)
In the STOP mode, it is still possible to
configure and run diagnostics on the CP.
STOP with internal error or memory reset.
(For example IP double addressing
detected in the network)
In this status:
S The CPU and intelligent modules in
the rack are still accessible using PG
functions (over MPI or ISO protocol.
S The SNMP function and access over
HTTP or FTP are not possible
STOP
INTF LED EXTF LED BUSF LED RUN LED STOP LED CP Operating Mode
(red) (red) (red) (green) (yellow)
Ready for firmware loading (this mode is
active for ten seconds following power up
when the mode selector is set to STOP)
RUN with external error; One or more IO
devices are not obtainable.
RUN with external error; Diagnostic
information from one or more IO devices
is available.
Module fault / system error
CP Communication Status
In addition to the LEDs that signal the CP mode, the front panel and the RJ-45
socket also include LEDs that provide information about the status of the CP
interface to Industrial Ethernet.
Table 4-1
Force Mode
You can control the mode of the CP 443-1 Advanced as follows:
S Mode selector
S STEP 7 / NCM S7 configuration software
To control the mode from STEP 7 / NCM S7, the mode selector must be set to
RUN.
Mode Selector
With the mode selector, you can set the following modes:
S Switch from STOP to RUN:
The CP reads the configured and/or downloaded data into the work memory
and then changes to the RUN mode.
S Switch from RUN to STOP:
The CP changes to STOP with the following results:
− Established connections (ISO transport, ISO-on-TCP, TCP connections) are
terminated (transitional phase with LED display “STOPPING”);
The reaction is as follows in STOP:
− All connections are terminated
− The configuration and diagnostics of the CP is possible (system connections
for configuration, diagnostics, and PG channel routing are retained);
− The downloading of interconnections for PROFINET CBA communication is
not possible;
− FTP access to the file system is possible
− HTTP access is possible
− The routing function is active
− The time of day is not forwarded
− PROFINET CBA is disabled;
− PROFINET IO is disabled.
Note
If you plug in the CP with the mode selector set to STOP or turn on the power
supply, the display “Ready for Start of Firmware Download” appears for
approximately 10 seconds. When necessary, this function allows the current
firmware version to be updated. In normal operation, you can ignore this display
and switch to RUN immediately.
For more information on downloading new firmware, refer to Section 11.
5 Performance Data
Note
Measurements of transmission and reaction times in Ethernet, PROFIBUS and
PROFINET networks for a series of configurations can be found on the Internet at
the following address:
http://support.automation.siemens.com/WW/view/en/25209605
Example
You can, for example, operate:
64 S7 connections
30 ISO-on-TCP connections
10 TCP connections
10 UDP connections
8 ISO transport connections
If you require FTP and HTTP access at the same time,(for FTP 2 x TCP
connections and for HTTP 4 x TCP connections; see Section 5.7).
Table 5-2
Table 5-3
Notice
If you use the SEND/RECEIVE interface on the CP, one(!) system connection
resource is used by S7 functions. Remember this in conjunction with the maximum
number of CPU connection resources. Remember also that it is not normally
possible to use all the system connection resources available for S7 functions for
CPs.
The number of SEND/RECEIVE calls that can be used at the same time is limited
both by the CPU and by the CP.
If the maximum number of simultaneous SEND/RECEIVE calls is exceeded, the
value 8302H (no receive resources) is indicated in the STATUS of the surplus
SEND functions. This can, for example, happen when too many SEND/RECEIVE
calls are sent at the same time in OB1.
Limitation by the CP
A maximum of 64 SEND/RECEIVE connections can be operated by the CP.
At an assignment of 1 CP per CPU, the maximum number of SEND/RECEIVE
calls that can be used at one time is limited as follows:
S SEND calls short (FC5) or long (FC50): max. 32*) / 12**) per CPU
Table 5-4 Dependency of the maximum number of RECEIVE calls long (FC60) used at the same time
on the number of SEND calls (CPU 412/414)
Number of 0 1 2 3. 5 6 7 8 10 11 12
simultaneous SEND 4 9
calls
Max. number of 19 18 17 16 15 14 13 12 11 10 9
simultaneous FC60s
per CPU 412/414
Table 5-5 Dependency of the maximum number of RECEIVE calls long (FC60) used at the same time
on the number of SEND calls (CPU 416/417)
Number of 0 1 2 3. 5 6 7 8 10 11 12 13 15 16
simultaneous SEND 4 9 14
calls
Max. number of 51 50 49 48 47 46 45 44 43 42 41 40 39 38
simultaneous FC60s
per
CPU 416/417/41x–H
Number of 17 18 20 21 22 23 25 26 27 28 30 31 32
simultaneous SEND 19 24 29
calls
Max. number of 37 36 35 34 33 32 31 30 29 28 27 26 25
simultaneous FC60s
per
CPU 416/417/41x–H
Table 5-6
Table 5-7
Note
Note the following for PROFINET IO: If you use modules with >=32 bytes of
input/output data, this can lead to I/O access errors; access errors are entered in
the diagnostic buffer of the CPU.
These I/O errors occur during operation only in the “consistent user data” mode
and at a low OB1 cycle time.
Notice
In PROFINET IO, the number of possible slots is limited.
The maximum number of slots depends on the CPU being used:
CPU 416−3 PN/DP: 2173 slots
CPU 416−3F PN/DP: 2173 slots
CPU 414−3 PN/DP: 1632 slots
PROFINET CBA
Number of remote interconnection 32 64
partners
Total of all I/Os 600 600
Data length of all incoming I/Os 3200 bytes 8192 bytes 1452 bytes
Data length of all outgoing I/Os 3200 bytes 8192 bytes 1452 bytes
Data length for arrays and structures 2048 bytes 8192 bytes 1452 bytes
(acyclic interconnections), maximum
Data length for arrays and structures 450 bytes 450 bytes 450 bytes
(cyclic interconnections), maximum
Data length for arrays and structures − 2400 bytes 1452 bytes
(local interconnections), maximum
Device−internal interconnections
Number of device−internal 50 300
interconnections
Data length of all device−internal 400 bytes 2400 bytes
interconnections
Note
For information on the data length and data type in PROFINET CBA
communication, refer to the online help on SIMATIC iMap, the “Creating
PROFINET Components” manual and the “Configuring Plants with SIMATIC iMap”
manual.
Notice
With a large configuration or when using other services at the same time (for
example monitoring online), the configured frequency of transmission cannot be
guaranteed in all cases. To remedy this, we recommend that you increase the
frequency of transmission.
Extension of the
cycle time in ms 6 1
5
2
4
1
3
0
0 20 40 60 80 100 120 140 160 180 200
Number of PROFINET CBA interconnections
Legend:
1 OB1 cycle with 32 PROFINET CBA partners and network attachment on the
CPU 317−2 PN/DP.
2 OB1 cycle with 5 PROFINET CBA partners and network attachment on the
CPU 317−2 PN/DP.
OB1 cycle with an S7−400 station with CPU 416−2 and with network attachment on
3
the CP 443−1 Advanced (the number of PROFINET CBA partners has no influence).
Definition
The reaction time is the time from recognizing an input signal until the associated
output signal changes.
Influences
The actual reaction time is subject to certain fluctuations. The achievable reaction
times for PROFINET CBA communication depend on the following factors:
S Type of interconnection (cyclic or acyclic) and the transmission frequency or
scanning frequency;
S The size of the configuration on the component interface (size of the interface
DB for PROFINET CBA);
S CPU cycle time and CPU type;
S Parallel operations with other types of communication types such as
PROFINET IO or with services such as online monitoring.
As a result, the reaction times for cyclic PROFINET CBA interconnections may
exceed the configured value for the transfer frequency. You should therefore check
the reaction time that can be achieved during commissioning and, if necessary,
change the project engineering.
Measurement principle:
Output data is generated by station 1 and interconnected as input data with station
2. The input data is mirrored there and transferred over interconnections back to
station 1 where it is evaluated and forwarded etc. The time required for the
individual transfer and evaluation cycle is measured in station 1. This corresponds
to approximately twice the reaction time according to the definition above.
The CPU cycle time (cycle time of OB1) for this measurement is 6 ms.
Note: With shorter cycle times, the reaction times are further reduced and with
longer cycle times they are correspondingly extended.
Measurement results
From the following diagram, you can see the average values for the reaction time
of the cyclic interconnections depending on the size of the interface DB.
Average
70
reaction 1
time in ms 60
50 2
40
3
30
20
10
0
0 480 960 1440 1920 2400 2880
Size of the interface DB in bytes
Legend
The transfer frequency set in the parameters in SIMATIC
iMap is as follows for the recorded lines:
1 50 ms 2 20 ms 3 10 ms
Evaluation
From the diagram, you can see that the transfer frequencies configured at 10 ms
or 20 ms in the sample configured are not achieved. On the other hand, at a
configured transfer frequency of 50 ms, a corresponding reaction time of 50 ms
with 2400 bytes is kept to.
Note
The values of the utilization parameters displayed by SIMATIC iMap as of V2.0
with the “Edit / Check utilization” function relate to the data exchange as far as the
CP. They do not apply to data access from the user program.
Table 5-9
Note
Please note that the maximum block size in bytes is specified here and that the
maximum number of array elements is decided by the byte size of the array basic
data type.
Example
The CP 443-1 Advanced can transfer a maximum of 100 array elements of the
type DWORD or REAL with a read job since each element of the type DWORD or
REAL occupies four bytes.
Interconnection information
for PROFINET CBA
Battery
Non-volatile RAM file
backed RAM system (/sram)
area
Notice
Please note the detailed description of the FTP functionality in the Information
Technology in SIMATIC S7 manual (entry ID = 24845107) or Part A of the manual
(as of Release 04/2008, entry ID = 30335356). For the entry ID, refer to Section
14.
In terms of the organization of the file system, the characteristics of the
CP 443-1 Advanced described here differ slightly from those described there. The
information in this device-specific manual is valid.
Figure 5-1
Notice
The flash area of the file system allows a limited number of write cycles
(approximately 100 000). You should therefore avoid writing data cyclically.
If you are writing temporary data often, you should use the RAM file system
located in the subfolder /ram or /sram. The files of the RAM file system (/ram) are
lost if there is power down.
Memory Area for the File System − Flash area (non-volatile memory)
30 MB
− RAM area (volatile memory)
16 MB
− RAM (SRAM) − backed by the battery of the power supply
module
512 Kbytes
PN IO System in STEP 7
In principle, you configure for PROFINET IO as follows:
To be able to use the CP as a PROFINET IO controller, create a PROFINET IO
system in STEP 7 / HW Config. You can either assign an existing or a new
Ethernet subnet to the CP as the PROFINET IO system.
Then add the PROFINET IO devices to the PROFINET IO system. STEP 7
automatically assigns addresses that you can modify if necessary. The address
information is stored in the database of the CP. When the system starts up, the
PROFINET IO controller (CP) no transfers this address information to the IO
devices (Note: The I/O and diagnostic addresses remain on the IO controller).
Figure 6-1 Example of the CP 443−1 Advanced as a PROFINET IO Controller with a PROFINET IO
System
Notice
S CP slot in PROFINET IO mode
PROFINET IO operation is possible only with one CP located in the central
unit.
S CPU “startup” configuration when using the IE/PB Link PN IO
If you use the IE/PB Link PN IO as PROFINET IO device, you must select the
option “Startup when expected/actual config. differ” for the CPU in the “Startup”
tab. Otherwise your system will not start up automatically after power up or
following a power outage.
Configuration Limits
When using the CP type described here, the following limits apply within an
S7−400 station:
Number of CPs operating as PROFINET IO controllers: 4
Table 6-1
Block Meaning
SFB52 ”RDREC” Read data record.
SFB53 ”WRREC” Write data record.
SFB54 ”RALRM” Receive alarm.
SFB81 ”RD_DPAR” Read predefined parameters.
SFC70 ”GEO_LOG” Identify the start address of a module.
SFC71 ”LOG_GEO” Identify the slot belonging to a logical address.
For a detailed description of these blocks / functions, refer to the “System Software
for S7−300/400 System and Standard Functions” manual.
Notice
Replacing blocks:
S You can replace FB88 in your user program with FB90 without needing to run
the componentization again.
S If you replace FB90 in your user program with FB88, you will have to repeat the
componentization.
Notice
Only one of the two block types FB88 or FB90 can be used in the user program of
an S7−400 station. Componentization is rejected if both block types are used at
the same time.
Notice
ISO transport connections and S7 connections using the ISO protocol cannot be
operated!
For more detailed information on adopting configuration data in the SIMATIC iMap
engineering tool, please refer to the /6/ manual.
Ind. Ethernet
PROFIBUS DP
S7−400 stations
with
CP 443−1 Advance
d
S7−400 stations
with
CP 443−1 Advance
d
Note
When you reload user program blocks, data consistency is only guaranteed if the
CPU is first changed to STOP.
Caution
If problems occur while downloading interconnections from SIMATIC iMap, for
example power down on the target station, it is not always possible to download
the interconnections again when the power returns.
If this error occurs, SIMATIC iMap reports the station as being unreachable.
Remedy:
Using the module switch or the PG command, change the CP 443−1 Advanced
from STOP to RUN to bring the target station back an operational status and to
allow the interconnections to be downloaded again from SIMATIC iMap.
Note
For more detailed information on adopting the configuration from STEP 7 and use
with PROFINET CBA and the SIMATIC iMap engineering tool, refer to the
documentation on SIMATIC iMap /6/.
Notice
The information in this section applies only if a singleton component was created
from the S7−400 station. With a standard component, the connection information
configured in STEP 7 is lost.
Overview
Parallel operation of PROFINET CBA communication and standard communication
with the S7 communication and S5−compatible communication services is possible
with the CP.
This mode is important for your application when, for example, you want to
implement communication between existing “conventional” SIMATIC devices and
PROFINET CBA devices in an existing system.
The special feature is that the configuration of the communication for PROFINET
CBA devices is only possible in SIMATIC iMap. Communication with conventional
devices, on the other hand, requires that the connections are configured in
STEP 7.
Recommended Procedure
Here, we would like to give you a few tips and recommendations.
For communication between a PROFINET CBA device and a conventional device,
use S7 or TCP or ISO−on−TCP connections.
Configure the S7 and TCP connections in STEP 7 as follows:
S for S7 communication
Note
The data exchange for productive communication (S7 connections +
SEND/RECEIVE connections) always has a higher priority than data exchange
with the Web browser. This can lead to delays in the HTML process control in the
Web browser.
Web Browser
To access the HTML pages on the CP 443-1 Advanced, you require a Web
browser.
The following Web browsers are suitable for communication with the CP 443-1
Advanced (other browsers also possible):
S Netscape Communicator (recommended version: 4.7 or higher)
S Internet Explorer (recommended version: 5.0 or higher)
These Web browsers support all the requirements necessary for the
implementation of the IT functions (Java reference implementation − Java
Development Kit) 1.1.x is supported) in conjunction with the CP 443-1
Advanced.
You will find these Web browsers, information and addons on the Internet.
This is new:
Functional enhancements compared with 6GK7 443−1EX40−0XE0 V2.4
The CP 443−1 Advanced (6GK7 443−1EX41−0XE0) has an interface optimized for
operation of PROFINET IO. To interface PROFINET IO devices, some of the
SFCs/SFBs differ from those used with the predecessor module.
Operation as a PROFINET IO controller requires CPUs complying with version
V5.x.
If you use CPUs complying with version V4.x, all other services are supported with
the exception of PROFINET IO controller mode.
9.2 Restrictions
Compared with previous modules, please note the following general restrictions:
S The 15−pin D−sub female connector for connecting AUI or Ind. Twisted Pair
has been omitted (applies to EX41 and EX40).
S The CP is not intended for operation with an S7−400H programmable controller
(fault−tolerant system).
Notice
H connections are not yet supported when using this CP and configuring it with
STEP 7 version V5.4.
Explanation / Meaning
1. Remove the module you want to replace from the rack.
2. Insert the C−PLUG from the replaced module in the new module.
3. Insert the new module with the C−PLUG taken from the removed module (EX40)
in the rack.
Notes:
− You do not need to turn the power off and on.
− The C−PLUG taken from the removed module has the ID “EX40”; this has
no effect on operation of the new CP (EX41).
If, however, you do not want to keep this ID, you must either user the
C−PLUG supplied with the new CP or reformat the C−PLUG of the old
module. You must then, however, supply the CP with an IP address again
(node initialization).
Step 2: Adapting the configuration
Explanation / Meaning
4. In STEP 7 / HW Config, replace the previously configured CP with the new
module from the hardware catalog.
5. As soon as you drag the new module from the catalog to the module to be
replaced in HW Config, the configured connections and data are adopted.
6. if necessary, extend the configuration to meet your requirements, for example in
the Properties dialog of the Ethernet subnet.
7. Save and compile the project.
8. Download the configuration data to the target system again.
Step Procedure
1. Remove the module you want to replace from the rack.
2. Insert the new module in the rack.
Explanation / Meaning
1. In STEP 7 / HW Config, replace the previously configured CP with the new
module from the hardware catalog.
2. As soon as you drag the new module from the catalog to the module to be
replaced in HW Config, the configured connections and data are adopted.
The mode is automatically configured as “Data storage on the CPU”.
3. Save and compile the project.
4. Download the configuration data to the target system again.
Step Procedure
1. Remove the module you want to replace from the rack.
2. Insert the new module in the rack.
3. Download the configuration data from the project on the PG/PC to the
new module.
Result:
After downloading the configuration, the CP changes to RUN.
Note:
Following a power cycle (OFF/ON), the CP remains in STOP because there is
no longer a configuration available; the configuration must be downloaded
again.
From the following table 3-1, you can see which of the options described above
exist for the available module types. Refer to the description above for the possible
procedures.
Caution
When installing the CP for use as a PROFINET IO controller, note the following
points about the power supply:
When using the CP in the central rack or in a universal rack operating as central
rack, you should not insert or remove the CP 443−1 Advanced when the power is
on. If you remove the CP when the power supply is on, the CPU changes to STOP
and indicates “I/O error” (in contrast to previous modules!).
After inserting the module with power applied, it is essential to turn the power
supply off and on again.
Note:
If the CP is operated without PROFINET IO, it is possible to insert and remove the
CP when the power is no without affecting the CPU.
Notice
With the functions for memory reset and resetting to the factory settings described
here, the configuration data on the CPU is not changed! Only the data maintained
on the CP (C-PLUG and RAM areas) is deleted.
If you subsequently upload the configuration data from the CPU to a PG you will
always object the configuration data that were previously on the CP (with
parameters, connections, IP address).
Battery
Non-volatile RAM file
backed RAM system (/sram)
area
Note
Please note that the interconnection information for PROFINET CBA belongs to
the retentive parameters in the C−PLUG and will therefore be deleted when you
reset to the factory settings.
Autocrossing Mechanism
With the autocrossing mechanism integrated in the switch, it is possible to use a
standard cable to connect the PC/PG. A crossover cable is not necessary.
Notice
Manual configuration
If a port is set to manual configuration, the autocrossing mechanism is also
deactivated for this port. The port then behaves like the interface of a switch. In
this case, the following applies:
S Connecting an end device
To connect an end device that does not have the autocrossing mechanism (for
example CP 443−1 with order number 6GK7 443−1EX11−0XE0), you must not
use a crossover cable.
S Connecting to a switch
To connect a switch, that does not support the autocrossing mechanism, use a
crossover cable.
Diagnostics
Diagnostics of the port settings for the CP described here is possible only using the
entries in the diagnostic buffer over SNMP, NCM diagnostics, and the LED
displays.
Further Notes:
S 10/100 Mbps network components without “Autonegotiation”
If you use 10/100 Mbps network components that do not support
“Autonegotiation”, it is possible that you will have to set the mode manually.
S Forcing a specific mode instead of “Autonegotiation”
If your application requires a fixed mode instead of “Autonegotiation”, you will
need to match up the partner devices.
S No reaction to Autonegotiation query with manual configuration
Remember that if you configure the CP manually, it will not react to an
autonegotiation query! As a result, a connected partner will not be able to set
the required mode and communication will not be ideal.
Example:
If, for example, the CP is set to “100 Mbps − full duplex”, a CP connected as
partner will set “100 Mbps − half duplex”. Reason: Due to the fixed setting, no
autonegotiation response is possible; the connected partner recognizes the 100
Mbps with autosensing but nevertheless remains in half duplex.
S Recommendation: Change individual network settings only over MPI.
If you modify the LAN settings in the properties dialog of the CP in the “Port
Parameters” tab using the “Transmission medium/Duplex” option, these
changes will be adopted by the CP and activated when the configuration data is
downloaded to the CP.
We therefore recommend that you download configuration data to the S7
station over an MPI connection if you change this setting.
If you download the configuration data over the LAN interface, depending on
the selected setting, it is possible that the current download will not be
completed due to the changes to the configuration taking immediate effect and
an inconsistent configuration is reported.
Example:
The download is started initially with the setting TP/ITP at 10 Mbps half duplex.
If the “Individual network setting” is now changed to 100 Mbps full duplex, the
download cannot be completed.
Procedure
The CP supports the two modes explained below for time-of-day synchronization:
S SIMATIC mode
If the CP receives MMS time-of-day messages, its local time is synchronized
providing the NTP mode was not defined during configuration (MMS =
Manufacturing Message Specification).
The advantage of this mode is that it is generally more accurate than the NTP
mode (guaranteed +− 1 ms). In contrast to the NTP mode, it is not possible to
forward the time of day over routers; in other words, to other subnets.
S NTP mode (NTP: Network Time Protocol)
In the NTP mode, the CP sends time queries (in the client mode) at regular
intervals to the NTP server in the subnet (LAN). Based on the responses of the
server, the most reliable and most accurate time of day is calculated and the
time synchronized on the station (in all modules with time−of−day functionality).
The advantage of this mode is that time-of-day synchronization is possible over
different subnets. The accuracy depends on the quality of the NTP server used.
Note
No automatic changeover to daylight saving is defined in NTP. As a result, you
may need to implement this changeover using a program application.
Notice
Note the following regarding time−of−day synchronization in NTP mode:
If the CP recognizes an NTP frame as being “not exact” (example: NTP server is
not externally synchronized), it is not forwarded to the communication bus. If this
problem occurs, none of the NTP servers is displayed as “NTP master” in the
diagnostics; rather all NTP servers are displayed only as being accessible.
Background
When using the CP described here, the points below will help you to avoid
overload situations on your CPU.
In particular when you replace an older CP with the CP described here and are
then confronted with overload problems, you should check your application for the
pitfalls outlined below.
Known Problems
S The functions for sending and receiving (FC5/FC6 or FC50/60) are often called
cyclically in OB1. This leads to constant communication between the CPU and
CP. As a result, other types of communication such as PG functions cannot be
executed or only very slowly.
S HMI systems access data of the CPU too often using S7 functions. This slows
down communication generally and can lead to lack of resources on the CPU if
SEND/RECEIVE FCs are called in OB1 cyclically (effect: reduced data
throughput or increased reaction time).
Remedy
The recommendations below will help to avoid these situations:
S Do not call communication blocks cyclically in OB1!
Communication should be called time-controlled in a suitable cyclic-interrupt
OB. The call interval of this OB should be significantly higher than the average
cycle time of your program.
S You should set a minimum cycle time that is higher than the average runtime of
OB1. This frees resources for communication on the CPU. This is, for example,
a remedy for existing applications when communication already takes place
cyclically in OB1.
S If necessary, reduce the time taken for communication processing on the CPU
by changing the parameters set for “cyclic load due to communication” in the
properties dialog of the CPU.
Notice
After a job has been triggered, you may only change the call parameters on the
FC call interface of the FCs AG_SEND or AG_RECV again after the FC has
confirmed job execution with DONE=1 or ERROR=1.
If this is ignored, it is possible that the execution of the job will be aborted with an
error and resources could be permanently occupied on the CPU.
Note
If the CP is in PG STOP mode, the configuration is downloaded using FB55, the
CP then changes automatically to RUN.
Notice
When configuring specified connections in STEP 7 / NCM S7, the IP addresses of
the partners are entered automatically in the IP−ACL (IP Access Control List).
The IP addresses of partners with unspecified connections (passive end points)
and of partners on programmed communication paths are not entered in the
IP−ACL.
Use
To allow the user program to exchange data with other TCP/IP−compliant
communication partners, STEP 7 provides a UDT for the connection parameter
assignment and four FBs.
S UDT 65 “TCON_PAR” with the data structure for connection parameter
assignment
S FB65 “TCON” for connection establishment
S FB66 “TDISCON” for connection termination
S FB63 “TSEND” for sending data
S FB64 “TRCV” for receiving data
TCP/IP communication is connection−oriented. Data can be transmitted only when
a connection has been established to the communication partner. The CPU can
use several connections to a communications partner at the same time.
The following protocol variants are supported:
S ISO on TCP according to RFC 1006
Uses / Advantages
Higher data throughput than with the configured connections of the
SEND/RECEIVE interface.
Programming
Make the following parameter settings in the connection description (UDT 65):
S local_tsap_id: Byte 1 = 0xE0 (value mandatory for correct functionality)
S local_tsap_id: Byte 2 = Rack/slot number
S remote_tsap_id: Byte 1 = 0xE0 (value mandatory for correct functionality)
S remote_tsap_id: Byte 2 = Rack/slot number
Note: The TSAPs can be 2−16 bytes long. The first two bytes must be occupied as
described, you can use the other bytes to suit your task.
Notice
Note that the number of dynamically established connections also depends on the
number of configured, statically established connections.
You will obtain appropriate condition codes on the call interface of the FBs....
Please refer to the documentation of the FBs in the online help and in the
documentation on STEP 7. There, you will also find examples of parameter
settings!
Index ifDescr
1−4 Port 1−4
5 Internal CP interface
Notice
We expressly point out that automation networks must be isolated from the rest of
the company network by suitable gateways (for example using tried and tested
firewall systems). We do not accept any liability whatsoever, whatever the legal
justification, for damage resulting from non-adherence to this notice.
If you have questions on the use of firewall systems and IT security, please contact
your local Siemens office or representative. You will find the address in the
SIMATIC catalog IKPI or on the Internet at
http://www.automation.siemens.com/partner
Notice
If you obtain the IP address over DHCP, any S7 connections you may have
configured will not work. Reason: The configured IP address is replaced by the
address obtained over DHCP during operation.
Requirements
You download new firmware to a SIMATIC NET CP using the firmware loader
shipped with the STEP 7 / NCM S7.
To download firmware, you require an Industrial Ethernet CP module in the PG/PC
(for example, CP 1613) or a normal Ethernet module with the “Softnet PG”
software package.
Notice
When you download the firmware, only one LAN cable may be attached to the
4−port switch of the module. This LAN cable must provide a PtP connection to the
PG/PC with which you are downloading. Downloading over the existing Ethernet
network is not permitted.
12 Technical Specifications
Table 6-1 Technical Specifications
You will find the following information in the general Part A of the manual:
S A list of the documents require for configuration, commissioning and operation
(Preface)
S Detailed descriptions of configuration and commissioning of the module
S Description of the IT functions
S Description of Web diagnostics and NCM S7 Diagnostics
S The approvals of the device (Appendix)
S A glossary (Appendix)
The general Part A of the manual is available in the Manual Collection that ships
with the device or on the Internet at the following address:
http://support.automation.siemens.com/WW/view/en/30374198
Enter the ID of the relevant manual as a search key. The ID is shown below the
literature name in brackets.
Manuals that are installed with the online documentation of the STEP 7 installation
on your PG/PC, can be selected from the Start menu (Start > SIMATIC >
Documentation).
You fill find a overview of the SIMATIC documentation at:
http://www.automation.siemens.com/simatic/portal/html_76/techdoku.htm
/5/ SIMATIC
Configuring Hardware and Connections with STEP 7
Part of the STEP 7 documentation package STEP 7 Basic Knowledge”
Part of the online documentation of STEP 7
Siemens AG
/7/ Basic Help in the SIMATIC iMap Engineering Tool (online help)
Siemens AG
On programming
/10/ Version history of the SIMATIC NET function blocks and functions for SIMATIC S7
Reference work
Siemens AG
(SIMATIC NET Manual Collection)
/13/ SIMATIC S7
S7−300 Automation System
− CPU 31xC und 31x Installation: Operating Instructions (ID: 13008499)
− Module Data: Reference Manual (ID: 8859629)
Siemens AG
and
SIMATIC S7
S7−400, M7−400 Automation system
− Installation Manual (ID: 1117849)
− Module Data: Reference Manual (ID: 1117740)
Siemens AG
/14/ SIMATIC
PROFINET System Description
System Manual
Siemens AG
(Part of the Manual Collection)
/15/ SIMATIC
From PROFIBUS DP to PROFINET IO
Programming Manual
Siemens AG
(Part of the Manual Collection)
Other topics