indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
Qualified Personnel
personnel qualified
Proper use of Siemens products
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
Disclaimer of Liability
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
The product/system described in this documentation may be operated only by
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Note the following:
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
for the specific
03/2019 Subject to change
Page 3
Preface
Legend:
①
X = placeholder for hardware product version
②
Firmware version
③
LEDs
④
Ethernet interface: Interface X1P1 with 1 x 8-pin RJ-45 jack
⑤
Designed for a redundant subnet
⑥
Label with MAC addresses
Validity and product names
RNA interface: Ports X2P1 / X2P2 with 2 x 8-pin RJ-45 jacks
Figure 1 CP 443-1 RNA
This description contains information on the following product
Current version of the manual and Information on the Internet
Firmware version V1.4.1
Communications processor for SIMATIC S7-400 / S7-400H
In this document, the term "CP" is used instead of the full product name.The name STEP 7 is used for the configuration tool instead of the names STEP 7 V5.5
and STEP 7 Professional.
● New ATEX/IECEx approval
● Editorial revision
Replaced manual edition 7/2017
The documentation for this device consists of the following parts:
● Manual Part A: Configuration manual "Configuring and Commissioning S7CPs for
Industrial Ethernet", see references /1/ (Page 67).
● Manual Part B: Manual "CP 443-1 RNA" (this manual)
● Program blocks for SIMATIC NET S7 CPs - programming manual, see references /4/
(Page 68)
Contains the detailed description of the program blocks for the following services:
– Open communications services
– Access coordination with FETCH/WRITE
– Connection and system diagnostics
You will find the current version of this document and further information (e.g. FAQs) on
using the CP on the Internet at the following address:
Select the appropriate entry type in the filter settings.
CP 443-1 RNA
4Manual, 03/2019, C79000-G8976-C299-04
Page 5
Preface
CP documentation in the Manual Collection (order no. A5E00069051)
Compatibility with other modules - service and maintenance
Note
Read the information regarding extended functions and restrictions in section
modules used with CP 443
Address label: Unique MAC address preset for the CP
License conditions
Note
Open source software
Read the license conditions for open source software carefully before using the product. The
acceptance of the disclaimers of liability and warranty it contains is a clear precondition of
the use of open source software.
You will find the license condition
following file name:
OSS_CP44x1RNA_86.pdf
Firmware
The "SIMATIC NET Manual Collection" DVD contains the device manuals and descriptions
of all SIMATIC NET products current at the time it was created. It is updated at regular
intervals.
Replacing the
-1 RNA (Page 52) of this manual!
The CP is supplied with a total of 2 default MAC addresses with the following assignment:
● Ethernet interface
● RNA interface
The two MAC addresses of the Ethernet interface and the RNA interface are printed on the
housing.
If you configure a MAC address (ISO transport connections), we recommend that you use
the MAC address of the relevant interface printed on the module for module configuration!
● This ensures that you assign a unique MAC address in the subnet!
● If you replace a module, the MAC address of the predecessor is adopted when you load
the configuration data; configured ISO transport connections remain operable.
s on the same data medium as this manual under the
The firmware is signed and encrypted. This ensures that only firmware created by Siemens
can be downloaded to the device.
5
Page 6
Preface
Security information
Recycling and disposal
SIMATIC NET glossary
Training, Service & Support
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is
necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial
security concept. Siemens’ products and solutions only form one element of such a concept.
Customer is responsible to prevent unauthorized access to its plants, systems, machines
and networks. Systems, machines and components should only be connected to the
enterprise network or the internet if and to the extent necessary and with appropriate security
measures (e.g. use of firewalls and network segmentation) in place.
Additionally, Siemens’ guidance on appropriate security measures should be taken into
account. For more information about industrial security, please visit
Link: (http://www.siemens.com/industrialsecurity)
Siemens’ products and solutions undergo continuous development to make them more
secure. Siemens strongly recommends to apply product updates as soon as available and to
always use the latest product versions. Use of product versions that are no longer supported,
and failure to apply latest updates may increase customer’s exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed under
Link: (http://www.siemens.com/industrialsecurity).
The product is low in pollutants, can be recycled and meets the requirements of the WEEE
directive 2012/19/EU "Waste Electrical and Electronic Equipment".
Do not dispose of the product at public disposal sites. For environmentally friendly recycling
and the disposal of your old device contact a certified disposal company for electronic scrap
or your Siemens contact.
Keep to the local regulations.
You will find information on returning the product on the Internet pages of Siemens Industry
Online Support:
Link: (https://support.industry.siemens.com/cs/ww/en/view/109479891)
Explanations of many of the specialist terms used in this documentation can be found in the
SIMATIC NET glossary.
You will find the SIMATIC NET glossary on the Internet at the following address:
You will find information on training, service and support in the multilanguage document
"DC_support_99.pdf" on the Internet pages of Siemens Industry Online Support:
1 Application and functions ........................................................................................................................ 9
2 Performance data ................................................................................................................................. 17
3 Requirements for use ............................................................................................................................ 23
A PRP-compatible devices ....................................................................................................................... 63
B Documentation references .................................................................................................................... 67
Index .................................................................................................................................................... 71
The Ethernet interface or the RNA interface can only be enabled as alternatives (one or the
other). Simultaneous use of both interfaces is not possible. These are activated during
configuration with STEP 7. Note further information in the section
(Page
The CP is intended for use in an S7400 or S7400H (faulttolerant) automation system. It
allows the S7400 / S7400H to be connected to Industrial Ethernet.
● Ethernet interface
The CP has a 100 Mbps Ethernet interface. The Ethernet interface can be used as an
alternative to the RNA interface. The Ethernet interface can, for example, be used to
connect to a PG/PC or to a higherlevel company network.
For special situations, each port can be set to a fixed mode manually using STEP 7, for
example 10 or 100 Mbps half duplex / full duplex.
● RNA interface
The RNA interface has 2 ports. These two ports are used as follows:
– PRP mode with both ports as a redundancy solution
– Port 1 as the only used port of the RNA interface with 100 Mbps full duplex (port 2 is
disabled)
The RNA interface only supports the "automatic setting" mode with 100 Mbps full duplex.
The communications partner must use the same settings.
Each port supports autocrossing and autonegotiation and is equipped with a combined
RXD/TXD / LINK dual LED for simple diagnostics.
Connection to port X1P1 of the Ethernet interface (ISO transport)
②
Connection of the RNA interface to a PRP network
③
Connection to port X2P1 of the RNA interface (ISO transport / ISO-on-TCP / TCP)
1.2
Communication services
S7 communication with the following functions:
Open communication services with the following functions:
1.1 Properties of the CP
Figure 1-1 CP 443-1 RNA - connection variants
Depending on the interface being used, the CP supports the following communications
services:
●
– PG functions;
– Operator monitoring and control functions;
– Data exchange over S7 connections.
●
– SEND/RECEIVE interface over ISO transport connections;
– SEND/RECEIVE interface over TCP connections, ISOonTCP and UDP connections;
With the SEND/RECEIVE interface via TCP connections, the CP supports the socket
interface to TCP/IP available on practically every end system.
UDP frame buffering on the CP can be disabled during configuration. When
necessary, this allows you to achieve a shorter reaction time between the arrival of a
UDP frame and its evaluation on the CPU.
– Multicast over UDP connection
The multicast mode is made possible by selecting a suitable IP address when
configuring connections.
– FETCH/WRITE services (server services; corresponding to S5 protocol) via ISO
transport connections, ISOonTCP connections and TCP connections;
Here, the SIMATIC S7400 with the CP is always the server (passive connection
establishment) while the fetch or write access (client function with active connection
CP 443-1 RNA
10Manual, 03/2019, C79000-G8976-C299-04
Page 11
Application and functions
Open TCP/IP communication
Interfaces used and communications services
Communications service
Ethernet interface
RNA interface
functions (ISO)
x x
- x
Data exchange over S7 connections (ISO)
x
x
Data exchange over S7 connections (TCP)
-
x
ISO transport connections
x
x
tions
- x
Multicast over UDP connection
-
x
FETCH/WRITE services (ISO)
x
x
FETCH/WRITE services (RFC, TCP)
-
x
nication
- x
Time of day
NTP mode and SIMATIC mode
-
x
via ISO x x
via TCP - x
1.3
Network topology with redundancy (PRP)
Redundant Network Access (RNA)
1.3 Network topology with redundancy (PRP)
establishment) is always initiated by a SIMATIC S5 or a device from another range /
PC.
– LOCK/UNLOCK with FETCH/WRITE services (CPUdependent; see section
Requirements for use (Page 23));
●
Open TCP/IP communication provides a program interface for the transfer of connectionoriented and connectionless services. The establishment and termination of connections
is initiated here only via the "dynamic" program interface.
STEP 7 provides a UDT for the connection parameter assignment as well as four FBs for
high-speed data exchange.
The CP supports communication via ISO-on-TCP connections for this interface.
The following table provides an overview of the services available at the interfaces.
S7 communication PG functions; operator control and monitoring
PG functions; operator control and monitoring
functions (ISO-on-TCP)
Open communications
services using
SEND/RECEIVE interface
Open TCP/IP commu-
H connections
TCP connections, ISOonTCP and UDP connec-
In Siemens Industry, Redundant Network Access (RNA) stands for devices and software that
support the redundancy protocol "Parallel Redundancy Protocol" (PRP). RNA allows the
connection of devices to redundant Ethernet network structures.
The product names of the RNA devices end with "RNA".
Some devices of the SCALANCE X-200RNA product line also support the redundancy
protocol "High-availability Seamless Redundancy" (HSR).
The Parallel Redundancy Protocol (PRP) is a redundancy protocol for Ethernet networks. It
is specified in IEC 62439-3.
The areas of application of PRP are distributed applications with high reliability demands that
depend on the high availability of the network. Compared with classic fault-tolerant networks,
bumpless path redundancy is possible with PRP.
PRP has the advantage that it uses parallel, separate networks made up of standard
network components. End devices that use this method are connected to both networks via
two ports of an interface of the device or via a SCALANCE X-200RNA or a RUGGEDCOM
RS950G. This means that data of the end device can be transferred at the same time via
both networks. If a transmission path is interrupted, the data reaches the communications
partner via the second parallel path.
If a network is interrupted, communication can be maintained with PRP via the second
network without any interruption. Reconfiguration times required with the other redundancy
protocols (e.g. MRP) do not therefore apply.
An end device with PRP capability can be connected to redundant networks by using the
PRP protocol. An end device that does not have PRP capability can be connected to a
redundant network via a SCALANCE X-200RNA or RUGGEDCOM RS950G that does have
PRP capability. This means that PRP can also be used by end devices without PRP
capability.
Devices with PRP capability are located in two independent networks with the same MAC
and IP address.
PRP is only possible when two end devices are connected via two independent networks
(LAN A and LAN B).
Each end device is represented in both networks LAN A and LAN B with the same MAC and
IP address.
CP 443-1 RNA
12Manual, 03/2019, C79000-G8976-C299-04
Page 13
Application and functions
Send
Received
Connecting up and cabling
Note
Cabling
Make sure that all the PRP ports of the nodes and the SCALANCE X204RNA /
RUGGEDCOM RS950G on LAN A and LAN B are connected correctly. A frame with the
identifier "LAN A" must be received at the corresponding port.
How is a redundant PRP network set up?
1.3 Network topology with redundancy (PRP)
PRP communication is handled using the following mechanisms:
●
An end device with PRP capability duplicates each frame to be sent on the PRP
interface. The two duplicates are sent via the 2 ports of the PRP interface via the two
separate networks LAN A and LAN B to the communications partner.
If the end device does not have PRP capability, the frame to be sent is duplicated by an
X-200RNA to which the end device is connected and sent via LAN A and LAN B to the
communications partner.
●
The two duplicates are received by an end device with PRP capability via LAN A and
LAN B on the two ports of the PRP interface.
If the end device does not have PRP capability, the receiving end device must be
preceded by an X-200RNA. The X-200RNA forwards the first frame to arrive to the
addressee. The second frame is discarded ((N-1) redundancy).
Each frame duplicate sent using the PRP mechanisms is given in identifier that specifies
whether it is sent via LAN A or LAN B.
The PRP ports of SIMATIC NET devices have the following identifiers. The CP ports are the
ports of the interface with PRP capability.
● Ports for connection to LAN A
– CPs: X2/P1
– SCALANCE X204RNA: PRP A
● Ports for connection to LAN B
– CPs: X2/P2
– SCALANCE X204RNA: PRP B
A network topology in which the Parallel Redundancy Protocol is used (PRP network)
consists of two separate Ethernet subnets. The structure of the two subnets does not need
to be identical.
A PRP network can be set up both with end devices with PRP capability as well as with
standard components. The following devices can be used:
● End devices with PRP capability (Double Attached Nodes PRP, Double Attached Node
implementing PRP, DANP), for example:
– CP 443-1 RNA
– PC with SOFTNET-IE RNA
– SIPROTEC protective devices with PRP capability
● Standard components (Singly Attached Nodes, SAN)
Standard components without PRP functionality, for example, can be connected to a PRP
network via SCALANCE X-200RNA or RuggedCom RS950G.
SANs can, however, also be connected to a PRP network without supporting the PRP
functionality.
All devices that are intended to use the PRP function in redundant networks must be able to
process frames with length of up to 1532 bytes (oversize frames). If this function is not
supported, data may be lost.
The following figure shows the options for connecting devices in a network topology in which
the Parallel Redundancy Protocol (PRP) is used.
Figure 1-2 Example of the configuration of a network topology with PRP
CP 443-1 RNA
14Manual, 03/2019, C79000-G8976-C299-04
Page 15
Application and functions
1.4
Further services and characteristics of the CP
Timeofday synchronization over the RNA interface using the following configurable
modes:
Addressable with the factoryset MAC address
SNMP agent on the RNA interface
Module access protection
IP access protection on the RNA interface (IPACL)
Web diagnostics on the RNA interface
Diagnostics buffer extract request
1.4 Further services and characteristics of the CP
●
– SIMATIC mode
or
– NTP mode (NTP: Network Time Protocol)
●
To assign the IP address to a new CP (direct from the factory), it can be accessed using
the preset MAC address on port X2P1 of the RNA interface. Online address assignment
is made in STEP 7.
The CP receives MMS timeofday messages and synchronizes its local time.
You can choose whether or not the time of day is forwarded. You can also decide on
the direction in which it is forwarded.
The CP sends timeofday queries at regular intervals to an NTP server and
synchronizes its local time of day.
The time can also be forwarded automatically to the CPU modules in the S7 station
allowing the time to be synchronized in the entire S7 station.
●
The CP supports data queries over SNMP in version V1 (Simple Network Management
Protocol). It delivers the content of certain MIB objects according to the MIB II standard
(RFC 1213), PRP-MIB IEC62439 (IEC-62439-3-MIB) and Automation MIB.
●
To protect the module from accidental or unauthorized access, protection can be
configured at various levels.
●
Using IP access protection gives you the opportunity of restricting communication over
the CP of the local S7 station to partners with specific IP addresses.
●
With the aid of Web diagnostics, you can read out the diagnostics data from a station
connected via the CP to a PG/PC with a Web browser.
The Web pages contain the following information:
– Module and status information
●
With the aid of a Web browser, the CP supports the option of obtaining an extract of the
diagnostics buffer containing the most recent diagnostics events of the CPUs and CPs
located in the same S7 station as the CP.
Note
Effects of connections in the SPEED SEND/RECV mode
Note the effects of connections on the SEND/RECEIVE interface that are used in the
SPEED SEND/RECEIVE mode.
The maximum configuration limits of S7 communic
connection using the SPEED SEND/RECV mode.
2.3
SEND/RECEIVE interface
2.3.1
Characteristic data
The following characteristics are important:
Characteristic
Explanation / values
cannot
by the sender (approximately 150200 messages per second).
program blocks.
2.3 SEND/RECEIVE interface
ation are reduced by each configured
The SEND/RECEIVE interface provides access to communication over TCP, ISOonTCP,
ISO transport and UDP connections.
Number of SEND/RECEIVE connections
Number of SEND/RECV connections in
SPEED SEND/RECV mode
Maximum data length for AG_SEND and
AG_RECV program blocks
• TCP connections: 1...64
• ISO-on-TCP connections: 1...64
• ISO transport connections: 1...64
• Total number of UDP connections (specified and free) that can be
• Max. number of connections in total:
Refer to the example in section 5.1 (Page 17)
Notes:
•
The number depends on the CPU type being used.
• Per CPU 412/414 maximum 30
• Per CPU 416/417 maximum 62
AG_SEND and AG_RECV were shipped with other CPs of the S7-400
family and allowed the transfer of user data with a length of 1 to 240
bytes. The version of the CP described here continues to support these
1)
configured: 1 to 64 (of those up to 48 in multicast mode)
(ISO transport and ISOonTCP
+ TCP + UDP) <= 64
1)
Avoid overload at receiving end
The flow control on TCP connections
load of the recipient. You should therefore make sure that the processing capabilities of a receiving CP are not permanently exceeded
control permanent over-
CP 443-1 RNA
18Manual, 03/2019, C79000-G8976-C299-04
Page 19
Performance data
Characteristic
Explanation / values
2. UDP: 1 to 1452 bytes
Restrictions for UDP
2.3.2
Number of simultaneous SEND/RECEIVE calls
2.3 SEND/RECEIVE interface
Maximum data length for AG_LSEND and
AG_LRECV program blocks
Maximum data length for
AG_SSEND and AG_SRECV program blocks
LAN interface max. data field length generated by CP per protocol data unit
● Transfer is not acknowledged.
AG_LSEND and AG_LRECV allow the transfer of user data with the following lengths:
1. ISO-on-TCP, TCP, ISO transport: 1 to 8192 bytes
2. UDP: 1 to 2048 bytes
AG_SSEND and AG_SRECV allow the transfer of user data with the
following lengths:
1. ISO-on-TCP, TCP, ISO transport: 1 to 1452 bytes
• sending
ISO transport, ISOonTCP, TCP:
– 400 bytes / TPDU with AG_SEND / AG_LSEND
– 1452 bytes / TPDU with AG_SSEND
The transmission of UDP frames is unconfirmed, in other words the loss of messages is
not detected or displayed by the send blocks (AG_SEND or AG_LSEND).
● No receipt of UDP broadcast
To avoid overload due to high broadcast load, the CP does not allow reception of UDP
broadcasts.
As an alternative, use the multicast function over a UDP connection. This allows you to
register the CP as a node in a multicast group.
● UDP frame buffering
Length of the frame buffer with buffering enabled:
2 KB
Note:
Following a buffer overflow, newly arriving frames are discarded.
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.
In productive operation, the number of SEND/RECEIVE calls that can be used at one time
depends on the CPU resources being used. Note the information on the available CPU
resources in section System environment (Page 23).
The following CPU resources are required:
● Per SEND job short (AG_SEND) or long (AG_LSEND): 1 resource
● Per RECEIVE job short (AG_RECV): 1 resource
● Per RECEIVE job long (AG_LRECV): 2 resources
● Per SPEED SEND/RECV job (AG_SSEND, AG_SRECV): 0 resources
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:
*)
● SEND calls short (AG_SEND) or long (AG_LSEND): max. 32
*)
● RECEIVE calls short (AG_RECV): max. 64
● RECEIVE calls long (AG_LRECV): variable
*)
The higher values apply to the CPU 416 and CPU 417.
**)
The lower values apply to the CPU 412 and CPU 414.
***)
The number of AG_LRECV program blocks that can be used at the same time depends
/ 24
***)
**)
per CPU
on the number of SEND calls active at the same time (see tables below).
/ 12
**)
per CPU
Table 2- 1 Dependency of the maximum number of RECEIVE calls long (AG_LRECV FC60) used at the same time on
the number of SEND calls (CPU 412/414)
Max. number of simultane-
CP 443-1 RNA
20Manual, 03/2019, C79000-G8976-C299-04
19 18 17 16 15 14 13 12 11 10 9
Page 21
Performance data
Number of simultaneous
SEND calls
0 1 2
3, 4 5 6 7
8, 9 10
11
12
13,
14
15
16
CPU 416/417/41x-H
Number of simultaneous
SEND calls
17 18,
19
20 21 22 23,
24
25 26 27 28,
29
30 31 32
CPU 416/417/41x-H
2.4
Characteristics of open TCP/IP communication
Characteristic
Explanation / values
trial Ethernet
Max. data length
1452 bytes
2.5
Characteristic data of TCP connections for HTTP
Characteristic data of TCP connections for HTTP
2.4 Characteristics of open TCP/IP communication
Table 2- 2 Dependency of the maximum number of RECEIVE calls long (AG_LRECV FC60) used at the same time on
the number of SEND calls (CPU 416/417)
Max. number of simultaneous FC60s per
Max. number of simultaneous FC60s per
51 50 49 48 47 46 45 44 43 42 41 40 39 38
37 36 35 34 33 32 31 30 29 28 27 26 25
The maximum number of SPEED SEND/RECEIVE calls that can be used simultaneously
(FC53, FC63) depends only on the CPU (see above).
Open TCP/IP communication provides a program interface for the transfer of connectionoriented and connectionless services. The establishment and termination of connections is
initiated here only via the "dynamic" program interface.
The CP supports communication via ISO-on-TCP connections for this interface.
Table 2- 3 Open TCP/IP communication
Number of dynamically generated connections over Indus-
For HTTP access, up to 4 CP-internal TCP connections are available. When necessary,
these TCP connections are used by one or more Web browsers to display data of the CP.
CP-internal TCP connections do not affect the configuration limits of the configured TCP
connection resources.
a = multiprocessor mode
b = number of operable CPs
c = CPU resources for SEND/RECEIVE jobs 1)
d = LOCK/UNLOCK
a b c
d
CPU 414-3
..414-3XM05-0AB0
V5.3.2
+
14
24
+
CPU 414-3 PN/DP
..414-3EM05-0AB0
V5.3.2
+
14
24
+
CPU 414-3 PN/DP
..414-3FM06-0AB0
as of V6.0.2
+
14
24
+
CPU 416-2
..416-2XN05-0AB0
V5.3.2
+
14
64
+
CPU 416-3
..416-3XL04-0AB0
V5.3.2
+
14
64
+
CPU 416-3
..416-3XR05-0AB0
V5.3.2
+
14
64
+
CPU 416-3 PN/DP
..416-3ER05-0AB0
V5.3.2
+
14
64
+
PN/DP
PN/DP
PN/DP
CPU 417-4
..417-4XT05-0AB0
V5.3.2
+
14
64
+
CPU 412-3H 2)
..412-3HJ14-0AB0
V4.5.6
+
14
64
+
CPU 414H 2)
..414-4HM14-0AB0
V4.5.6
+
14
64
+
CPU 417H 2)
..417-4HR14-0AB0
V4.5.6
+
14
64
+
CPU 417-4H 2)
..417-4HT14-0AB0
V4.5.6
+
14
64
+
CPU 412-5H 2)
..412-5HK06-0AB0
V6.0.2
+
14
64
+
CPU 414-5H 2)
..414-5HM06-0AB0
V6.0.2
+
14
64
+
CPU 416-5H 2)
..416-5HS06-0AB0
V6.0.2
+
14
64
+
Legend:
+ => The characteristic is supported / the listed mode is possible
1) Note: The calculation of the maximum number of SEND/RECEIVE calls that can be used simultaneously per CP is d
2) Note: When operating with H
SEND/RECV interface is not supported.
See also
3.2 System environment
CPU 414-3 PN/DP ..414-3EM06-0AB0 as of V6.0.2 + 14 24 +
CPU 416F-3
CPU 416F-3
CPU 416F-3
CPU 417-5H 2) ..417-5HT06-0AB0 V6.0.2 + 14 64 +
- => The characteristic is not supported / the listed mode is not possible
scribed in the section "Characteristic data".
..416-3FR05-0AB0 V5.3.2 + 14 64 +
..416-3ES06-0AB0 as of V6.0.2 + 14 64 +
..416-3FS06-0AB0 as of V6.0.2 + 14 64 +
CPUs with a firmware version lower than V6.0, the SSEND / SRECV mode on the
e-
Project engineering (Page 25)
Number of simultaneous SEND/RECEIVE calls (Page 19)
CP 443-1 RNA
24Manual, 03/2019, C79000-G8976-C299-04
Page 25
Requirements for use
3.3
Project engineering
Configuration and downloading the configuration data
STEP 7 version and additional modules
CP 4431 RNA functionality
STEP 7 V5.5
3.4
Programming
Program blocks
Note
Using current block versions
We recommend that you always use the latest block versions for all module types.
You will find information on the curre
from the Internet in our Customer Support under entry ID:
Link: (
With older module types, this recommendation assumes that you are using the latest
firmware for the particular module type.
Using program blocks for the SEND/RECEIVE interface
3.3 Project engineering
It is possible to download the configuration data to the CP via MPI or LAN/Industrial
Ethernet. Downloading is possible over the RNA or the Ethernet interface of the CP. You
require STEP 7 with additional modules in the following version:
• as of STEP 7 V5.5 + Service Pack 2 + HSP1097
The full functionality as described in this document
can be used.
For some communications services, there are preprogrammed program blocks (FCs / FBs)
available as the interface in your STEP 7 user program.
Refer to the documentation of the program blocks in the online help of STEP 7 or in the
manual /4/ (Page 68).
nt block versions and the current blocks to download
As long as the "MAINT" LED is lit, there is an internal update taking place on the CP.
Check the entries in the diagnostics buffer of the device.
29
Page 30
LEDs
CP communications status / LED display patterns
LED
Display
Meaning
each port.
Symbol
Meaning
Module identification
Note
Module identification - make the port LEDs flash briefly
With the help of Web diagnostics or the online functions of STEP 7, you can search for and
identify the module in the rack. The options
•
•
When t
See also
TXD (green)
RXD (green)
X1P1
X2P1 / X2P2
(green / yellow)
Table 4- 2 Legend
ON OFF Flashing any
CP sending over Ethernet.
CP is receiving over Ethernet.
Port has no connection over Ethernet.
Existing connection over port to Ethernet (LINK status).
LED flashes yellow (constant light green):
Port is sending / receiving via Ethernet.
Note:
Here, all received / sent frames are signaled separately for
There is permanent data transfer via Ethernet at the port.
-
for this are as follows:
In Web diagnostics
You click the "Flash" button in the update center.
In STEP 7
You click the "Flash" button in the "Browse network" dialog
he "Flash" button is clicked, the port LED of the enabled interface flashes briefly.
Loading new firmware (Page 51)
CP 443-1 RNA
30Manual, 03/2019, C79000-G8976-C299-04
Page 31
5
5.1
Important notes on using the device
Safety notices on the use of the device
WARNING
Safety requirements for installation
5.1.1
Notices on use in hazardous areas
WARNING
WARNING
EXPLOSION HAZARD
Note the following safety notices when setting up and operating the device and during all
associated work such as installation, connecting up or replacing the device.
The devices are "open equipment" according to the standard IEC 61010-2-201or UL 508 /
CSA C22.2 No. 142. To fulfill requirements for safe operation with regard to mechanical
stability, flame retardation, stability, and protection against contact, the following alternative
types of installation are specified:
• Installation in a suitable cabinet.
• Installation in a suitable enclosure.
• Installation in a suitably equipped, enclosed control room.
The device may only be operated in an environment with pollution degree 1 or 2 (see IEC
60664-1).
Notices on use in hazardous areas according to ATEX / IECEx
WARNING
Requirements for the cabinet
5.1 Important notes on using the device
The equipment is designed for operation with Safety Extra-Low Voltage (SELV) by a
Limited Power Source (LPS).
This means that only SELV / LPS complying with IEC 60950-1 / EN 60950-1 / VDE 0805-1
must be connected to the power supply terminals. The power supply unit for the equipment
power supply must comply with NEC Class 2, as described by the National Electrical Code
(r) (ANSI / NFPA 70).
DO NOT CONNECT OR DISCONNECT EQUIPMENT WHEN A FLAMMABLE OR
COMBUSTIBLE ATMOSPHERE IS PRESENT.
SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR CLASS I, DIVISION
2 OR ZONE 2.
When used in hazardous environments corresponding to Class I, Division 2 or Class I,
Zone 2, the device must be installed in a cabinet or a suitable enclosure.
To comply with EC Directive 94/9 (ATEX95) or the conditions of IECEx, this enclosure or
cabinet must meet the requirements of at least IP54 in compliance with EN 60529.
CP 443-1 RNA
32Manual, 03/2019, C79000-G8976-C299-04
Page 33
Installation, connecting up, commissioning
WARNING
Cable
WARNING
5.1.3
Notices on use in hazardous areas according to UL HazLoc
WARNING
EXPLOSION HAZARD
5.2
Installation - procedure
5.2 Installation - procedure
If the cable or conduit entry point exceeds 70 °C or the branching point of conductors
exceeds 80 °C, special precautions must be taken. If the equipment is operated in an air
ambient in excess of 50 °C, only use cables with admitted maximum operating temperature
of at least 80 °C.
Take measures to prevent transient voltage surges of more than 40% of the rated voltage.
This is the case if you only operate devices with SELV (safety extra-low voltage).
DO NOT DISCONNECT WHILE CIRCUIT IS LIVE UNLESS AREA IS KNOWN TO BE
NON-HAZARDOUS.
This equipment is suitable for use in Class I, Division 2, Groups A, B, C and D or nonhazardous locations only.
This equipment is suitable for use in Class I, Zone 2, Group IIC or non-hazardous locations
only.
The steps for installing the CP are explained below.
Result: The CP is installed in the rack and the interfaces have been networked.
When using the universal rack UR1 or UR2 as an expansion rack, a communication bus
link is necessary!
See also
5.3
Commissioning - procedure
5.3 Commissioning - procedure
1. Plugging in the CP:
Fit the CP onto the rack from the top and push it in at the bottom.
The CP can be operated in central or universal racks.
2. Secure the CP with screws.
3. Turn on the power supply.
4. Connect the CP to Industrial Ethernet via one of the RJ45 jacks.
Network settings (Page 42)
The steps for commissioning the CP are explained below. Commissioning involves the
addressing and downloading the configuration data and user programs.
Result: The CP is reachable in the network and has been supplied with configuration data.
CP 443-1 RNA
34Manual, 03/2019, C79000-G8976-C299-04
Page 35
Installation, connecting up, commissioning
Follow the steps outlined below:
Note
You can connect the PG when configuring the CP as follows:
•
•
The PG/PC requires a LAN attachment, for example via a CP 1623 or CP 1411 and
must have the
IE). The TCP/IP protocol or ISO protocol must be installed. The protocol used must
then be applied to the S7ONLINE access point.
5.4
Replacing a module without a programming device
General procedure
Note
Configured MAC address is adopted
When setting the ISO protocol, remember that MAC address set previously during
configuration is transferred by the CPU to the new CP module.
5.4 Replacing a module without a programming device
1. Download the configuration data from your STEP 7 project to the S7400 station.
– Requirement:
You have configured the CP in a STEP 7 project for the properties and services you
want to use.
via MPI
via Industrial Ethernet
For further details, refer to the general part /1/ (Page 67) of this manual:
– Initial addressing (node initialization);
– Downloading the configuration
necessary software (for example the S71623 package or SOFTNET
2. Use the diagnostics functions during commissioning and to analyze problems.
You have the following options available:
– Hardware diagnostics and troubleshooting with STEP 7.
– Communication diagnostics with special diagnostics.
– Web diagnostics.
The configuration data of the CP is stored on the CPU. This makes it possible to replace this
module with a module of the same type (identical order number) without a PG.
For information on replacement using other modules, refer to the information in section
Replacing the modules used with CP 443-1 RNA (Page 52).
You can change the mode of the CP between RUN and STOP using the STEP 7
configuration software or using STEP 7 special diagnostics.
The CP loads configured and/or downloaded data into the work memory and then changes
to RUN mode.
The CP changes to STOP (transitional phase with LED display "Stopping").
The reaction is as follows in STOP:
● Established connections (ISO transport, ISOonTCP, TCP, UDP connections) are
terminated
● The following the functions are disabled:
– Time-of-day synchronization
● The following functions remain enabled:
– The configuration and diagnostics of the CP (system connections for configuration,
diagnostics, and PG channel routing are retained);
– Web diagnostics
CP 443-1 RNA
36Manual, 03/2019, C79000-G8976-C299-04
Page 37
6
6.1
Security recommendations
General
Physical access
Network attachment
Keep to the following security recommendations to prevent unauthorized access to the
system.
● You should make regular checks to make sure that the device meets these
recommendations and other internal security guidelines if applicable.
● Evaluate your plant as a whole in terms of security. Use a cell protection concept with
suitable products.
● Do not connect the device directly to the Internet. Operate the device within a protected
network area.
● Keep the firmware up to date. Check regularly for security updates of the firmware and
● Check regularly for new features on the Siemens Internet pages.
Restrict physical access to the device to qualified personnel.
Do not connect the PC directly to the Internet. If a connection from the CP to the Internet is
required, arrange for suitable protection before the CP, for example a SCALANCE S with
firewall.
use them.
– Here you will find information on industrial security:
Link: (http://www.siemens.com/industrialsecurity)
– Here you will find information on security industrial communication:
Use the options for security settings in the configuration of the product. These includes
among others:
● Protection levels
– Configure a protection level of the CPU.
– Configure the protection level "Status-dependent".
● Security function of the communication
– Enable the IP access protection of the CP (HW Config).
– Disable access to the Web server of the CPU (CPU configuration) and on the CP.
● Protection of the passwords of program blocks
Protect the passwords stored in data blocks for the blocks from being viewed. The
procedure is described below.
You can prevent the contents of data blocks (e.g. passwords) being read out by protecting
the block with the "KNOW_HOW_PROTECT" option. Follow the steps outlined below in
STEP 7:
1. Select the DB in the block folder.
2. Open the block in the editor.
3. Close the block in the editor.
4. Generate a source from the block in the editor.
5. Select the source of the DB in the sources folder.
6. Open the source.
7. Insert an empty line in the header of the source and write "KNOW_HOW_PROTECT" in
this line.
8. Compile the source.
Result: The block is protected. You can recognize this by the padlock symbol in the block
folder.
If you want to later change parameters in a DB, for example a password, remember the
following: The contents of a DB with know-how protection are no longer visible and can only
be changed via the source or by direct assignment of parameters.
● Define rules for the use of devices and assignment of passwords.
● Regularly update the passwords to increase security.
● Only use passwords with a high password strength. Avoid weak passwords for example
"password1", "123456789" or similar.
CP 443-1 RNA
38Manual, 03/2019, C79000-G8976-C299-04
Page 39
Configuration and operation
Protocols
Secure and non-secure protocols
Table: Meaning of the column titles and entries
Protocol / function
Port number (protocol)
Default of the port
Port status
Authentication
Protocol / function
Port number (protocol)
Default of the port
Port status
Authentication
HTTP
80 (TCP)
Open
Open after configuration
No
ISO-on-TCP
(RFC1006)
NTP
123 (UDP)
Closed
Open after configuration
No
SNMP
6.1 Security recommendations
● Make sure that all passwords are protected and inaccessible to unauthorized personnel.
See also the preceding section for information on this.
● Do not use one password for different users and systems.
● Only activate protocols that you require to use the system.
The following table provides you with an overview of the open ports on this device.
●
Protocols that the device supports.
●
Port number assigned to the protocol.
●
– Open
The port is open at the start of the configuration.
– Closed
The port is closed at the start of the configuration.
●
– Open
The port is always open and cannot be closed.
– Open according to configuration
The port is open if it has been configured.
– Open (login, when configured)
As default the port is open. After configuring the port, the communications partner
needs to log in.
●
Specifies whether or not the protocol authenticates the communications partner during
access.
161 (UDP) Open Open after configuration Yes (with SNMPv3)
Interface change - load configuration data only via other module
6.3
Memory reset / reset to factory defaults
Note
Data on the CP is deleted - CPU data is retained
The functi
the configuration data on the CPU! Only the data kept on the CP is deleted.
If you subsequently upload the configuration data from the CPU to a PG you will always
object the c
connections, IP address).
Note
Memory reset - ACL (access control list)
After a memory reset on the module, the following applies:
•
6.2 Switching over interfaces
The choice of the interface to be used, RNA interface or Ethernet interface is made in the
configuration of the CP. Each configuration or changeover of the interface therefore requires
that the configuration data is downloaded again.
If you change over the currently active interface and when you load the configuration data,
you will need to use an interface of the CPU or the interface of another CP to load the
configuration data.
If you load the configuration data via the interface of the CP 443-1 RNA, on which the
interface should be switched over, the loading cannot be completed.
The CP has a twolevel function available for resetting memory:
● Memory reset
● Resetting to factory setting
ons for resetting and resetting to factory defaults described here do not change
onfiguration data that was previously on the CP (with parameters,
ACL remains active.
CP 443-1 RNA
40Manual, 03/2019, C79000-G8976-C299-04
Page 41
Configuration and operation
How to use the functions
Clear/reset module - effects
Reset to factory defaults - effects
6.3 Memory reset / reset to factory defaults
You can start the memory reset functions in STEP 7. The CP must be in STOP. When you
reset memory using special diagnostics, the CP is automatically changed to STOP.
● Memory reset
– In STEP 7 V5.5 with the menu command "PLC" > "Clear/Reset"
– In STEP 7 special diagnostics with the "Operating Mode" > "Clear/Reset Module"
menu command
● Resetting to factory settings
– In STEP 7 V5.5 with the menu command "PLC" > "Edit Ethernet Node..." > Select CP
> "OK" > "Reset to Factory Defaults"
– In STEP 7 special diagnostics with the "Operating Mode" > "Reset to Factory Settings"
menu command
Following the memory reset, the CP retains the configured MAC address, the IP address and
the retentive parameters. The CP is therefore immediately ready for downloads using the IP
address.
The configuration data is retained on the CPU.
The CPU in the S7 station does not recognize that the CP memory was reset. The CP
changes to the "Stopped (STOP) with error" state (see LEDs (Page 27)). The configuration
data must then be reloaded. You can also initiate this loading by cycling power (OFF/ON).
After resetting to factory defaults, the CP always retains the factory set MAC address (as
supplied).
The IP address and the configuration data in the CP RAM are deleted. The configuration
data is retained on the CPU.
Transmission properties of the Ethernet and RNA interfaces
Automatic setting or individual network settings
Note
In normal situations, the basic setting ensures trouble
change this in exceptional situations.
Autocrossing mechanism
6.4 Network settings
Internally, the CP uses the following reserved MAC address:
00-1B-1B-31-4D-00
Do not use this MAC address for communications partners of the CP, otherwise no
communication is possible with the communications partner.
The common transmission characteristics of the two interfaces are described below.
The configuration of the network settings "Transmission medium / duplex" is made for the
Ethernet interfaces in the properties of the port in STEP 7/HW Config:
Row "X1P1": Port properties of the Ethernet interface
As default, the CP is configured for automatic detection (autosensing) for both interfaces.
The settings for the RNA interface are fixed.
If necessary, you can change the settings for the Ethernet interface.
Ethernet interface:
If you create a manual configuration for the CP and disable the autonegotiation option, the
automatic negotiation of the network settings (autonegotiation) is no longer effective. If, on
the other hand, the communications partner works with autonegotiation, it is not certain that
error-free communication will be established.
free communication. You should only
With the integrated autocrossing mechanism, it is possible to use a standard cable to
connect the PC/PG. A crossover cable is not necessary.
CP 443-1 RNA
42Manual, 03/2019, C79000-G8976-C299-04
Page 43
Configuration and operation
STEP 7 special diagnostics and Web diagnostics display the network setting
Further notes:
6.4 Network settings
Diagnostics of the port settings for the CP described here is possible using the entries in the
diagnostics buffer using SNMP, special diagnostics, and the LED displays.
You will find information on the currently used network settings in STEP 7 as follows:
● in special diagnostics under the diagnostics object "Industrial Ethernet" in the "Network
Attachment" group box;
● in STEP 7 with the menu command "PLC > Module Information";
● In Web diagnostics.
● 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.
● Forcing a specific mode instead of "Automatic settings"
If your application requires a specific mode instead of the automatic settings, you will
need to match up the partner devices.
● No reaction to Autonegotiation query with manual configuration
Remember that if you configure the CP manually and the "Autonegotiation" option is
disabled, it will not react to an autonegotiation query! As a result, a connected partner
may 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" and autonegotiation is disabled, a
CP connected as partner will set "100 Mbps - half duplex". Reason: Due to the fixed
setting, an autonegotiation reply is not possible. Although the connected partner detects
100 Mbps with autosensing, it remains at half duplex.
● Recommendation: Change individual network settings only over MPI
If you modify the LAN settings, these changes will be adopted by the CP and activated
when the configuration data is downloaded to the target system (STEP 7). In some
situations, the device may then no longer be obtainable over Ethernet.
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 via the LAN interface then, 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 settings" are now changed to 100 Mbps full duplex, the download
cannot be completed.
You can only assign the CP an IP address in the factory settings status.
To be able to assign an already configured CP a new IP address using PST or the STEP 7
function "Edit Ethernet node", you will need to reset this to its factory settings.
To save you timeconsuming troubleshooting in the network, the CP detects double
addressing in the network.
If the CP detects double addressing on the network (new node with an IP address that has
already been assigned), a message is generated in the diagnostics buffer and the bus fault
LED lights up.
The CP remains in RUN mode. After the device with the duplicate IP address has been
removed from the network, the bus fault LED goes off automatically.
If duplicate addressing is detected when the CP starts up, the CP remains in STOP. The bus
fault LED is lit and a diagnostics buffer entry is generated.
Restart the CP after the double addressing problem has been eliminated.
CP 443-1 RNA
44Manual, 03/2019, C79000-G8976-C299-04
Page 45
Configuration and operation
6.6
Time-of-day synchronization
General rules
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.
Note
Note the following about time
If an NTP frame is detected by the
synchronized externally), there is no forwarding on the K 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 bein
Project engineering
6.7
Recommendation for use with a high communications load
Reason
Known problems
6.6 Time-of-day synchronization
On the RNA interface, the CP supports the following two modes for timeofday
synchronization:
● SIMATIC mode
● NTP mode (NTP: Network Time Protocol)
ofday synchronization in NTP mode:
CP as "not exact" (example: NTP server is not
For more detailed information on configuration, refer to the online help of the "Time-of-day
synchronization" parameter group and in Part A of the manual /1/ (Page 67).
To avoid an overload situation on the CPU you are using, note the following information
about the CP.
● The program blocks for sending and receiving AG_SEND / AG_RECV (FC5/FC6,
g accessible.
FC50/60 or FC53/63) 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.
● HMI systems access data of the CPU too often using S7 functions. This slows down
communication overall and there may be resource bottlenecks on the CPU.
● Do not call communication program blocks cyclically in OB1!
Instead, call up communication time-controlled in a suitable time OB. The call interval of
this OB should be significantly higher than the average cycle time of OB1.
● Set a minimum cycle time that is higher than the average execution time of OB1. This
frees resources for communication on the CPU. Setting a minimum cycle time is a
suitable solution, for example, for existing applications when communication already
takes place cyclically in OB1.
● If necessary, reduce the time for processing communication on the CPU. The setting is
made with the "Cycle load due to communication" parameter in the properties of the CPU.
SNMP is a protocol for managing networks. To transmit data, SNMP uses the
connectionless UDP protocol.
The information on the properties of SNMPcompliant devices is entered in MIB files (MIB =
Management Information Base).
The CP supports data queries using SNMP in version 1. It supplies the content of certain
MIB objects according to MIB-II (RFC1213), PRP-MIB IEC62439 (IEC-62439-3-MIB) and
Automation System MIB.
You will find the MIB file and the SNMP profile file of the module in the STEP 7 installation in
the folders "S7DATA" > "snmp" under the name of the module.
For more detailed information on working with MIB files, refer to the documentation of the
SNMP client you are using (example of an SNMP client: SNMP OPC server from
SIMATIC NET).
You will find more information on the MIB on the Internet:
The CP supports the following groups of MIB objects of the standard MIB II according to
RFC1213:
● System
● Interfaces
● IP
● ICMP
● TCP
● UDP
● SNMP
The other groups of the MIB II standard are not supported:
● EGP
● Transmission
● at
The CP also supports the Automation System MIB and the PRP-MIB (IEC-62439-3-MIB).
Exceptions / restrictions:
● Write access is permitted only for the following MIB objects of the system group:
– sysContact
– sysLocation
– sysName
For all other MIB objects / MIB object groups, only read access is possible for security
reasons.
● Traps are not supported by the CP.
The "Interfaces" MIB object provides status information about the CP interfaces. The MIB
objects of the ifTable provide the status information of the interfaces. The "ifIndex" object
identifier is assigned to the CP interfaces as follows:
Call interface for open communications services SEND/RECV
Change call parameters only after job confirmation
Note
Note the following for the call interface of the program blocks AG_SEND / AG_LSEND /
AG_SSEND or AG_RECV / AG_LRECV / AG_SRECV:
Once the job has been triggered, you can only make changes again after the program block
has confirmed completion of the job with DONE=1 or with ERROR=1.
If this is ignored, it is possible that the execution of the job w
resources could be permanently occupied on the CPU.
6.9 Interface in the user program
The CP uses the following community names to control the access rights in the SNMP
agent:
Table 6- 2 Access rights in the SNMP agent
Read and write access private
If you use an SNMP tool, you will find the MIB files relevant to the CP in the STEP 7
installation in the following folder:
There, you will find, for example, the following MIB files:
● automationPS.mib
● automationSmi.mib
● automationSystem.mib
● automationTC.mib
● IEC-62439-3-MIB.mib
ill be aborted with an error and
CP 443-1 RNA
48Manual, 03/2019, C79000-G8976-C299-04
Page 49
Configuration and operation
6.9.2
Open TCP/IP communication
Note
Validity
The information in this section applies only to the RNA interface.
Use
Programming
Note
Note that the number of dynamically established connections also depends on the number of
configured, statically established connections.
You will receive corresponding
6.9 Interface in the user program
To allow the user program to exchange data with other TCP/IPcompliant communications
partners, STEP 7 provides a UDT for the connection parameter assignment and four
program blocks:
● UDT 65 "TCON_PAR" with the data structure for connection parameter assignment
● FB65 "TCON" for connection establishment
● FB66 "TDISCON" for connection termination
● FB63 "TSEND" for sending data
● FB64 "TRCV" for receiving data
TCP/IP communication is connectionoriented. Data can be transmitted only when a
connection has been established to the communications partner. The CPU can use several
connections to a communications partner at the same time.
The following protocol variants are supported:
● ISO on TCP according to RFC 1006
Make the following parameter settings in the connection description (UDT 65):
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.
condition codes on the call interface of the FBs.
Refer to the documentation of the program blocks in the online help and in the
documentation for STEP 7. There, you will also find examples of parameter assignment!
Pings with a packet size of more than 1000 bytes are evaluated as an attack and filtered by
the CP. This response is intentional and improves the robustness of the CP in an industrial
environment.
A ping simply serves to check reachability. There is therefore no need to support extremely
long ICMP packets.
In PRP mode, the first frame from an unknown node is discarded and remains unanswered.
This response must be taken into account with the services that do not generally cause any
frame repetitions such as:
● Firmware download (see also section Loading new firmware (Page 51))
● Searching the network
● PING
CP 443-1 RNA
50Manual, 03/2019, C79000-G8976-C299-04
Page 51
7
7.1
Loading new firmware
Options for a firmware update
How to download new firmware
The following alternative methods can be used to download new firmware to a SIMATIC NET
CP:
● Using the firmware loader supplied with STEP 7
Requirement for downloading:
– 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" software
package.
– The S7ONLINE interface must be set to the "ISO - Industrial Ethernet" protocol. It is
not possible to download using TCP/IP (and therefore not to other networks).
Always run the download using the active MAC address of the CP!
● Using the update center
You can reach the update center using Web diagnostics.
The CP supports the storage of several firmware versions. Using the firmware load
function in the update center, you can activate the required firmware version.
Requirement: The "Firmware download via Web" option is selected in the configuration
and the user rights have been set.
Note the descriptions of firmware downloads in the manual Part A /1/ (Page 67).
You can download the firmware via the active interface of the CP.
Follow the steps outlined below:
1. Connect the CP module to the PG/PC via a LAN cable.
2. Start the download on your PG/PC using one of the firmware download functions
described above.
The download involves two stages:
– Section 1: Downloading firmware
– Section 2: Activating firmware
You will find the LED displays in the section LEDs (Page 27)
If the download is aborted, RUN and STOP flash alternately.
3. After the firmware download, the CP goes through a warm restart.
A timeout may be indicated in PRP mode. In this case, restart the firmware download again.
7.2
Replacing the modules used with CP 443-1 RNA
Converting
Replacement of a CP 443-1 (EX20 / EX30)
7.2 Replacing the modules used with CP 443-1 RNA
If you start the download, this can lead to a timeout being indicated in PRP mode. In this
case, restart the download. You should also refer to the explanation in the section
Communication in PRP mode (Page 50)
Disturbances or collisions on the network can lead to packets being lost. In such cases, this
can lead to an interruption of the firmware download. The firmware loader then signals a
timeout or negative response from the module being loaded. En entry is made in the
diagnostics buffer. The CP restarts with the firmware that existed before the aborted
download.
Repeat the download using the active MAC address after the CP has started up again.
If you cannot start the download again following an aborted attempt, you should turn off the
entire rack and turn it on again. You can then restart the firmware download.
By adhering to certain rules and restrictions, you can replace other module types with the CP
443-1 RNA.
When replacing modules, the following module types can be considered:
● CP 443-1 EX20 / EX30
Taking into account the following information, the range of functions of the replaced module
will continue to be supported with the specified restrictions.
Note the following procedure when replacing modules:
CP 443-1 RNA
52Manual, 03/2019, C79000-G8976-C299-04
Page 53
Upkeep and maintenance
Adapting the configuration
Effects
7.2 Replacing the modules used with CP 443-1 RNA
1. In the STEP 7 configuration, replace the already configured CP with the new module; You
will find this in the hardware catalog.
2. As soon as you drag the new module from the catalog onto the module you are replacing,
the configured connections and data are adopted.
3. If necessary, modify the configuration according to your requirements, for example in the
Properties dialog for the Ethernet subnet.
4. Save and compile the project.
5. Download the configuration data to the target system again.
The CP 443-1 RNA adopts the settings of the EX20/EX30 as far as it supports them.
After the replacement, the CP is in the mode with the activated RNA interface with port 1 as
the only port in use (no PRP mode)
The following continues to apply:
● Functions, such as DHCP are not supported.
● The previously set IP parameters are adopted.
● If the replaced CP was configured as a PROFINET IO controller, the PROFINET line will
be detached from the module. The PROFINET line can then be assigned to another
PROFINET IO controller in STEP 7.
● Connections are assigned to the RNA interface.
● Explicit parameter assignments of the ports are lost since the CP 443-1 RNA does not
• Max. 100 m IE FC TP Standard Cable with IE FC RJ45 Plug 180
• Max. 90 m IE FC TP Standard Cable + 10 m TP Cord via IE FC RJ45 Outlet
* For details, refer to the IK PI catalog, cabling technology
** You will find the product functions in the section Application and functions (Page 9).
For further data, refer to section Performance data (Page 17)
In addition to this, all the information in the S7-400/M7-400 reference manual "Module Data"
/10/ (Page 70) in the section "General Technical Specifications" on the topics listed below
applies to the CP
● Electromagnetic compatibility
● Transportation/storage conditions
● Mechanical and climatic environmental conditions
● Information on insulation checks, protection class and degree of protection
CP 443-1 RNA
56Manual, 03/2019, C79000-G8976-C299-04
Page 57
9
Approvals issued
Note
Issued approvals on the type plate of the device
The specified approvals apply only when the corresponding mark is printed on the product.
You can check which
markings on the type plate.
Approvals for shipbuilding are not printed on the device type plate.
EC declaration of conformity
94/9/EC (ATEX explosion protection directive, up to 19.04.2016)
2014/34/EU (ATEX explosion protection directive, as of 20/04/2016)
2004/108/EC (EMC up to 19.04.2016)
2014/30/EU (EMC, as of 20/04/2016)
2011/65/EU (RoHS)
of the following approvals have been granted for your product by the
The CP meets the requirements and safety objectives of the following EU directives and it
complies with the harmonized European standards (EN) for programmable logic controllers
which are published in the official documentation of the European Union.
●
Directive of the European Parliament and the Council of March 23, 1994 on the
approximation of the laws of the Member States concerning equipment and protective
systems intended for use in potentially explosive atmospheres
●
Directive of the European Parliament and the Council of 26 Febrary 2014 on the
approximation of the laws of the Member States concerning equipment and protective
systems intended for use in potentially explosive atmospheres, official journal of the EU
L96, 29/03/2014, pages. 309-356
●
Directive of the European Parliament and of the Council of December 15, 2004 on the
approximation of the laws of the member states relating to electromagnetic compatibility.
●
EMC directive of the European Parliament and of the Council of February 26, 2014 on the
approximation of the laws of the member states relating to electromagnetic compatibility.;
official journal of the EU L96, 29/03/2014, pages. 79-106
●
Directive of the European Parliament and of the Council of 8 June 2011 on the restriction
of the use of certain hazardous substances in electrical and electronic equipment
The EC Declaration of Conformity is available for all responsible authorities at:
The conditions must be met for the safe deployment of the CP according to the section
Notices on use in hazardous areas according to ATEX / IECEx (Page 32).
You should also note the information in the document "Use of subassemblies/modules in a
Zone 2 Hazardous Area" that you will find on the Internet at the following address:
The product meets the requirements of EC Directive 94/9/EC "Equipment and Protective
Systems Intended for Use in Potentially Explosive Atmospheres" as of 19/04/2016 and the
CP 443-1 RNA
58Manual, 03/2019, C79000-G8976-C299-04
Page 59
Approvals
EMC
RoHS
requirements of EC Directive 2014/34/EU "Equipment and Protective Systems Intended for
Use in Potentially Explosive Atmospheres" as of 20/04/2016.
● nA
ATEX classification: II 3G Ex nA IIC T4 Gc
Certificate no.: KEMA 03ATEX1225 X
The products meet the requirements of the following standards:
– EN 60079-0 (Hazardous areas - Part 0: Equipment - General requirements)
– EN 60079-15 (Hazardous areas - Part 15: Equipment protection by type of protection
"n")
● ec
ATEX classification: II 3 G Ex ec nC IIC T4 Gc
Certificate no.: DEKRA 18ATEX0027 X
The products meet the requirements of the following standards:
– EN 60079-0 (Hazardous areas - Part 0: Equipment - General requirements)
– EN 60079-7 (Hazardous areas - Part 7: Equipment protection through increased
safety "e")
The current versions of the standards can be seen in the EU Declaration of Conformity, see
above.
The conditions must be met for the safe deployment of the product according to the section
Notices on use in hazardous areas according to ATEX / IECEx (Page 32).
You should also note the information in the document "Use of subassemblies/modules in a
Zone 2 Hazardous Area" that you will find on the Internet at the following address:
Until 19.04.2016 the CP meets the requirements of the EC Directive:2004/108/EC
"Electromagnetic Compatibility” (EMC directive) and as of 20.04.2016 the EC directive
2014/30/EC.
Applied standards:
● EN 61000-6-4
Electromagnetic compatibility (EMC) - Part 6-4: Generic standards - Emission standard
for industrial environments
● EN 61000-6-2
Electromagnetic compatibility (EMC) - Part 6-2: Generic standards - Immunity for
industrial environments
The CP meets the requirements of the EU directive 2011/65/EC on the restriction of the use
of certain hazardous substances in electrical and electronic equipment.
● Underwriters Laboratories, Inc.: UL 508 Listed (Industrial Control Equipment)
● Canadian Standards Association: CSA C22.2 No. 142 (Process Control Equipment)
Report / UL file: E85972 (NRAG, NRAG7)
Underwriters Laboratories, Inc.: cULus IND. CONT. EQ. FOR HAZ. LOC.
Applied standards:
● ANSI ISA 12.12.01
● CSA C22.2 No. 213-M1987
APPROVED for Use in:
● Cl. 1, Div. 2, GP. A, B, C, D T4
● Cl. 1, Zone 2, GP. IIC T4
Ta: Refer to the temperature class on the type plate of the CP
Report / UL file: E223122 (NRAG, NRAG7)
Note the conditions for the safe deployment of the CP according to the section Notices on
use in hazardous areas according to UL HazLoc (Page 33).
Factory Mutual Approval Standard Class Number 3600, 3611, 3810
Class I, Division 2, Group A, B, C, D, T4 or Class I, Zone 2, Group IIC, T4
Ta: Refer to the temperature class on the type plate of the CP
Certificate of Compliance: 3030463
The CP meets the requirements of the AS/NZS 2064 standards (Class A).
This class A digital device meets the requirements of the Canadian standard ICES-003.
CP 443-1 RNA
60Manual, 03/2019, C79000-G8976-C299-04
Page 61
Approvals
AVIS CANADIEN
Current approvals
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
SIMATIC NET products are regularly submitted to the relevant authorities and approval
centers for approvals relating to specific markets and applications.
If you require a list of the current approvals for individual devices, consult your Siemens
contact or check the Internet pages of Siemens Industry Online Support:
* Information about the product version (ES) or the firmware version (V) as of which PRP is supported.
CP 343-1 Advanced 6GK7343-1GX30-0XE0 V1.2
CP 443-1 Advanced 6GK7443-1GX20-0XE0 V2.1
CP 443-1 RNA
66Manual, 03/2019, C79000-G8976-C299-04
Page 67
B
B.1
Introduction to the documentation
Where to find Siemens documentation
B.2
On configuring, commissioning and using the CP
B.2.1
/1/
● Article numbers
You will find the article numbers for the Siemens products of relevance here in the
following catalogs:
– SIMATIC NET - Industrial Communication / Industrial Identification, catalog IK PI
– SIMATIC - Products for Totally Integrated Automation and Micro Automation, catalog
ST 70
You can request the catalogs and additional information from your Siemens
representative. You will also find the product information in the Siemens Industry Mall at
the following address:
Link: (https://mall.industry.siemens.com)
● Manuals on the Internet
You will find SIMATIC NET manuals on the Internet pages of Siemens Industry Online
Support:
Go to the required product in the product tree and make the following settings:
Entry type “Manuals”
● Manuals on the data medium
You will find manuals of SIMATIC NET products on the data medium that ships with many
of the SIMATIC NET products.
SIMATIC NET
S7 CPs for Industrial Ethernet
Configuring and Commissioning - configuration manual
manual Part A - General Applications
Siemens AG
Link: (https://support.industry.siemens.com/cs/ww/en/view/30374198)
SIMATIC NET
Commissioning PC Stations - Manual and Quick Start
Configuration Manual
Siemens AG
Link: (https://support.industry.siemens.com/cs/ww/en/ps/15362/man)
SIMATIC
Configuring Hardware and Connections with STEP 7
Siemens AG
Part of the documentation package "STEP 7 Basic Knowledge"
(Part of the online documentation in STEP 7)
Link: (https://support.industry.siemens.com/cs/ww/en/view/45531110)
SIMATIC NET
Program blocks for SIMATIC NET S7 CPs
Programming Manual
Siemens AG
(SIMATIC NET Manual Collection)
On the Internet under the following entry ID:
Link: (https://support.industry.siemens.com/cs/ww/en/view/60641662)
SIMATIC NET
Version history of the SIMATIC NET program blocks for S7 CPs
Reference manual
Siemens AG
Link: (https://support.industry.siemens.com/cs/ww/en/view/109474421)
CP 443-1 RNA
68Manual, 03/2019, C79000-G8976-C299-04
Page 69
Documentation references
B.4.3
/6/
B.4.4
/7/
B.4.5
/8/
B.4.6
/9/
B.4 On programming (S7 CPs / OPC)
SIMATIC
Programming with STEP 7
Siemens AG
(Part of the STEP 7 documentation package STEP 7 Basic Knowledge)
(Part of the online documentation in STEP 7)
Link: (https://support.industry.siemens.com/cs/ww/en/view/18652056)
SIMATIC
System and Standard Functions for S7-300/400 - Volume 1/2
Reference manual
Siemens AG
(Part of the STEP 7 documentation package STEP 7 Basic Knowledge)
(Part of the online documentation in STEP 7)
Link: (https://support.industry.siemens.com/cs/ww/en/view/1214574)
Open communications services, 4, 10
Open TCP/IP communication, 11, 21, 49
Operation with a high communications load, 26
Operator monitoring and control functions, 10