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
maintenance are required to ensure that the products operate safely and without any problems. The permissible
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
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
Drives
05/2017 Subject to change
Page 3
Preface
Validity of this manual
CP 1243-1
This document contains information on the following telecontrol product:
●
Article number 6GK7 243-1BX30-0XE0
Hardware product version 2
Firmware version V3.0
The CP 1243-1 is the communications processor for connecting the SIMATIC S7-1200 to
control center systems via the public infrastructure (e.g. DSL).
With the help of VPN technology and the firewall, the CP allows protected access to the
S7-1200.
The CP can also be used as an additional interface of the CPU for S7 communication.
Behind the top hinged cover of the module housing, you will see the hardware product
version to the right of the article number printed as a placeholder "X". If the printed text is, for
example, "X 2 3 4", "X" would be the placeholder for hardware product version 1.
You will find the firmware version of the CP as supplied behind the top hinged cover of the
housing to the left below the LED field.
You will find the MAC address under the lower hinged cover of the housing.
●
These abbreviations are used below instead of the full product name CP 1243-1:
●
This abbreviation ill be used below for the "TeleControl Server Basic", version V3.
●
This short form will be used below for the STEP 7 Basic / Professional configuration tool.
●
PC with the STEP 7 project
This manual describes the properties of this module and supports you when installing and
commissioning it.
The required configuration steps are described as an overview and there are explanations of
the relationship between firmware functions and configuration.
You will also find information about the diagnostics options of the device.
● New hardware product version 2
● New functions in the firmware version named above include:
– Expansion of the telecontrol protocols DNP3 and IEC
– Sending messages even without telecontrol communicaton
– Changed behavior during time-of-day synchronization, see section Time-of-day
– Expansion of the supported data types, refer to the section Datapoint types (Page 89).
● Functional improvement of data point configuration as of STEP 7 V14 SP1. see section
Data point configuration (Page 82).
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).
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:
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)
You will find information on Training, Service & Support in the multi--language document
"DC_support_99.pdf" on the data medium supplied with the documentation.
5 Program blocks ................................................................................................................................... 117
6 Diagnostics and upkeep ...................................................................................................................... 121
7 Technical data .................................................................................................................................... 133
A Approvals ............................................................................................................................................ 135
B Dimension drawings ............................................................................................................................ 139
C Documentation references .................................................................................................................. 141
S7 communication and PG/OP communication with the following functions:
The CP is intended for operation in an S7-1200 automation system. The CP allows
connection of the S7-1200 to Industrial Ethernet or via the Internet to the following control
center systems:
● Telecontrol server (OPC server application TCSB V3)
● DNP3 master station
● IEC master station
With the combination of different security functions such as firewall and protocols for data
encryption, the CP protects the station and even entire automation cells from unauthorized
access and protects the communication between the remote S7 station and the master
station (TCSB) from espionage and manipulation.
The following communications services are supported:
●
The CP is a communications processor of the SIMATIC S7-1200 for system attachment
to the control center systems named above. The CP can communicate with redundant
control systems.
For each control center system the relevant telecontrol protocol is activated on the CP
("Type of communication"). The protocols allow IP-based data transmission for telecontrol
applications.
You will find the usable security functions in the section Security functions (Page 13).
●
With special events, the CP can send messages as e-mails.
You will find the requirements and functions in the section E-mail configuration (Page 69).
●
– PUT/GET as client and server for data exchange with S7 stations
Due to the data point configuration in STEP 7, programming program blocks in order to
transfer the process data is unnecessary. The individual data points are processed oneto-one in the control system.
●
– IPv4 / IPv6
The CP supports IP addresses according to IPv4 and IPv6.
For telecontrol applications in IPv6 networks, an IPv6 address can be used in addition
to an IPv4 address.
– Address assignment
The IP address, the subnet mask and the address of a gateway can be set manually
in the configuration.
As an alternative, the IP address can be obtained from a DHCP server or by other
means outside the configuration.
●
The CP supports various methods of time-of-day synchronization. You will find
information in the section Time-of-day synchronization (Page 42).
For information on the format of the time stamp, refer to the section Datapoint types
(Page 89).
●
The CP can store events of different classes chronologically and transfer them
spontaneously or together to the telecontrol server.
●
The telecontrol communication with the communications partner is triggered in two ways:
– After a request by the master or an OPC client connected to TCSB
– Unsolicited, triggered by various selectable criteria
●
Analog values can be preprocessed on the CP according to various methods.
From the engineering station you can access the station via the CP with the online
functions of STEP 7.
The following online functions are available:
– Downloading project or program data from the STEP 7 project to the station
– Querying diagnostics data on the station
– Downloading firmware files to the CP
For information on the online functions, refer to the section Online functions and
TeleService (Page 123).
●
As an SNMP agent, the CP supports data queries using SNMP (Simple Network
Management Protocol).
For more detailed information, refer to section SNMP (Page 125).
With Industrial Ethernet Security, individual devices, automation cells or network segments
of an Ethernet network can be protected. The data transfer via the CP can be protected from
the following attacks by a combination of different security measures:
● Data espionage
● Data manipulation
● Unauthorized access
Secure underlying networks can be operated via additional Ethernet/PROFINET interfaces of
the CPU.
The security functions can be used independently of telecontrol communication.
As an integrated (unconfigurable) security function, the protocol encrypts the data for
transfer.
You configure the interval of the key exchange between the CPU and telecontrol
server in STEP 7 in the parameter group "Ethernet interface (X1) > Advanced options
> Transmission settings".
–
To authenticate the CP with the telecontrol server
●
The security functions specific to DNP3 can be used.
●
For the IEC protocol there are no protocol-specific security functions available.
As a result of using the CP, as a security module, the following security functions are
accessible to the S7-1200 station on the interface to the external network:
●
– IP firewall with stateful packet inspection (layer 3 and 4)
– Firewall also for "non-IP" Ethernet frames according to IEEE 802.3 (layer 2)
– Limitation of the transmission speed ("Bandwidth limitation")
– Global firewall rules
●
VPN tunnel communication allows the establishment of secure IPsec tunnels for
communication with one or more security modules.
The CP can be put together with other modules to form VPN groups during configuration.
IPsec tunnels (VPN) are created between all security modules of a VPN group. All
internal nodes of these security modules can communicate securely with each other
through these tunnels.
●
To allow monitoring, events can be stored in log files that can be read out using the
configuration tool or can be sent automatically to a Syslog server.
●
For the secure transfer of e-mails
●
For secure transfer during time-of-day synchronization
Note
Plants with security requirements - recommendation
Use the following options:
•
•
See also section
1.5
Configuration limits and performance data
Number of CMs/CPs per station
Connection resources
Telecontrol connections
1.5 Configuration limits and performance data
●
For secure transmission of network analysis information safe from eavesdropping
●
The protection provided by the firewall can cover individual devices, several devices or
even entire network segments.
If you have systems with high security requirements, use the secure protocols
NTP (secure), HTTPS and SNMPv3.
If you connect to public networks, you should use the firewall. Think about the services
you want to allow access to the station via public networks. By using the "bandwidth
limitation" of the firewall, you can restrict the possibility of flooding and DoS attacks.
Security recommendations (Page 37).
For configuring the security functions refer to the section Security (Page 63).
You will find further information on the functionality and configuration of the security functions
in the information system of STEP 7 and in the manual /4/ (Page 142).
In each S7-1200 station, up to three CMs/CPs can be plugged in and configured; this allows
three CP 1243-1 modules.
To use telecontrol communication, three CP 1243-1 modules can be plugged in per station.
●
With the various telecontrol protocols the CP can establish connections to the following
master station types:
– To non-redundant or redundant telecontrol servers (TCSB).
– To up to four non-redundant or redundant DNP3 masters
– To up to four non-redundant or redundant IEC masters
With the Telecontrol Basic protocol, in addition to this, inter-station communication with
up to 15 S7 stations with a CP 1243-1 can be operated via the telecontrol server.
15
Page 16
Application and properties
S7 connections and TCP / UDP / ISO-on-TCP connections
Online functions
PG/OP connections
Number of data points for the data point configuration
User data
Frame memory (send buffer)
Messages (e-mail)
IPsec tunnel (VPN)
1.5 Configuration limits and performance data
●
Max. 14 connection resources, can be distributed as required for:
– S7 connections (PUT/GET)
– Connections via program blocks (OUC) to S7 stations
●
1 connection resource is reserved for online functions.
●
– 1 connection resource for PG connections
– 3 connection resources for OP connections
The maximum number of configurable data points is 200.
The data to be transferred by the CP is assigned to various data points in the STEP 7
configuration.
The size of the user data per data point depends on the data type of the relevant data point.
You will find details in the section Datapoint types (Page 89).
The CP has a frame memory (send buffer) for the values of data points configured as an
event and that are sent to the communications partner.
The send buffer has a maximum size of 64000 events divided into equal parts for all
configured communications partners. The size of the frame memory can be set in STEP 7,
refer to the section SNMP (Page 53).
With the Telecontrol Basic protocol the send buffer can also be used for up to three partners
for inter-station communication You create the configuration in the "Partner" parameter
group.
● Sending of up to 10 messages (e-mails) can be configured with the message editor.
● Sending e-mails via the TMAIL_C program block
Up to 8 IPsec terminals can be established for secure communication with other security
modules.
Telecontrol with a non-redundant master station (TCSB)
Communication between S7 stations and a master station (TCSB)
1.6 Configuration examples
Figure 1-2
In the telecontrol applications of the example shown, SIMATIC S7 stations communicate with
a non-redundant telecontrol server (TCSB) in the master station.
● Telecontrol communication between stations and master station
The communication is via the following paths and communications modules:
– Communication via the Internet: S7-1200 with CP 1243-1
– Communication via the GSM network and the Internet: S7-1200 with CP 1242-7 or
The establishment of terminal connections with encryption is initiated automatically by the
telecontrol protocol used by the various communications modules.
The creation of VPN connections between the CP 1243-1 and telecontrol server is
optional.
The telecontrol server monitors the connections established by the remote stations.
● Inter-station communication
Stations of the same type, for example S7-1200 with CP 1243-1, can communicate with
each other by sending the frames via the telecontrol server.
Configuration example with a non-redundant control center
1.6 Configuration examples
The following example describes a configuration with a non-redundant control center in
which all nodes are located in 1 IP subnet.
In this example, the DNP3 protocol is used; in other words, the stations are equipped with a
CP 1243-1.
A configuration in which the IEC protocol is used would have the same setup.
Figure 1-4 Configuration example with a non-redundant control center and stations in one IP subnet
The S7-1200 stations are connected to the Internet via the CP and connected to the control
center.
When using the DNP3 protocol, for example, SIMATIC PCS 7 TeleControl or the system of a
third-party provider can be used as the control center. If you use SIMATIC PCS 7
TeleControl as the DPN3 master in the control center, you require the necessary DPN3
driver.
Configuration example with connections over the Internet
Addressing
1.6 Configuration examples
The following example contains a configuration with a non-redundant control center.
In this example, the DNP3 protocol is used. A configuration in which the IEC protocol is used
would have the same setup.
The S7-1200 stations are connected to the Internet via the CP and connected to the control
center.
When using the DNP3 protocol, for example, SIMATIC PCS 7 TeleControl or the system of a
third-party provider can be used as the control center. If you use SIMATIC PCS 7
TeleControl as the DPN3 master in the control center, you require the necessary DPN3
driver.
Figure 1-5 Configuration example with connections over the Internet
As an alternative to the router SCALANCE 812, you can also use a standard DSL modem
and establish the VPN connection with a security module SCALANCE S.
Refer to the information in the section DNP3 / IEC (Page 41).
Location of the display elements and the electrical connectors
Opening the covers of the housing
The LEDs for the detailed display of the module statuses are located behind the upper cover
of the module housing.
The Ethernet connector is located behind the lower hinged cover of the module.
Open the upper or lower cover of the housing by pulling it down or up as shown by the
arrows in the illustration. The covers extend beyond the housing to give you a grip.
The LED symbols in the following tables have the following significance:
Table 2- 3
-
Page 27
LEDs and connectors
Note
LED colors when the module starts up
When the module starts up, all its LEDs are lit for a short time. Multicolored LEDs display a
color mixture. At this point in time, the color of the LEDs is not clear.
Display of the basic statuses of the CP ("DIAG" LED)
DIAG
(red / green)
Meaning
(if more than one point listed: alternative meaning)
Basic statuses of the CP
green
flashing green
flashing red-green
2.2 LEDs
Table 2- 4 Display of the basic statuses of the CP
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.
If power is supplied to the module or station over longer power cables or networks, the
coupling in of strong electromagnetic pulses onto the power supply cables is possible. This
can be caused, for example by lightning strikes or switching of higher loads.
The connector of the external power supply is not protected from strong electromagnetic
pulses. To protect it, an external overvoltage protection module is necessary. The
requirements of EN61000-4-5, surge immunity tests on power supply lines, are met only
when a suitable protective element is used. A suitable device is, for example, the Dehn
Blitzductor BVT AVD 24, article number 918 422 or a comparable protective element.
Notices on use in hazardous areas according to IECEx / ATEX
WARNING
Requirements for the cabinet/enclosure
WARNING
3.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).
If the equipment is connected to a redundant power supply (two separate power supplies),
both must meet these requirements.
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 EU Directive 94/9 (ATEX95), the enclosure or cabinet must meet the
requirements of at least IP54 in compliance with EN 60529.
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.
Notices regarding use in hazardous areas according to UL HazLoc
WARNING
EXPLOSION HAZARD
3.1.4
Notices on use in hazardous areas according to FM
WARNING
EXPLOSION HAZARD
WARNING
EXPLOSION HAZARD
3.1 Important notes on using the device
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.
Do not connect or disconnect while the circuit is live or unless the area is known to be free
of ignitible concentrations.
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 equipment is intended to be installed within an ultimate enclosure. The inner service
temperature of the enclosure corresponds to the ambient temperature of the module. Use
installation wiring connections with admitted maximum operating temperature of at least
30 ºC higher than maximum ambient temperature.
Read the system manual "S7-1200 Programmable Controller"
Pulling/plugging the module
NOTICE
Turning off the station when plugging/pulling the module
Dimensions for installation
3.2 Installing, connecting up and commissioning
Prior to installation, connecting up and commissioning, read the relevant sections in the
system manual "S7-1200 Programmable Controller", refer to the documentation in the
Appendix.
When installing and connecting up, keep to the procedures described in the system manual
"S7-1200 Programmable Controller".
Before pulling or plugging the module, always turn off the power supply to the station.
Figure 3-1 Dimensions for installation of the S7-1200
* Width B: The distance between the edge of the housing and the center of the hole in the DIN rail mounting clip
DIN rail clamps, control panel installation
Installation location
NOTICE
Installation location
Device position / permitted temperature range
Installation location
3.2 Installing, connecting up and commissioning
Table 3- 1 Dimensions for installation (mm)
CPU (examples)
CPU 1214C 110 mm 55 mm
Communications interfaces (examples)
CP 1242-7, CP 1243-1, CP 1243-7, CP 1243-8 IRC 30 mm 15 mm
You will find detailed dimensions of the module in the section Dimension drawings
(Page 139).
All CPUs, SMs, CMs and CPs can be installed on the 35 mm DIN rail in the cabinet. Use the
pull-out DIN rail mounting clips to secure the device to the rail. These mounting clips also
lock into place when they are extended to allow the device to be installed in a switching
panel. The inner dimension of the hole for the DIN rail mounting clips is 4.3 mm.
The module must be installed so that its upper and lower ventilation slits are not covered,
allowing adequate ventilation. Above and below the device, there must be a clearance of 25
mm to allow air to circulate and prevent overheating.
Remember that the permitted temperature ranges depend on the position of the installed
device. You will find the permitted temperature ranges in the section Technical
specifications of the CP 1243-1 (Page 133).
Installing, connecting up and commissioning the module
Note
Connection with power off
Only wire up the
Step
What to do
Notes and explanations
1
The slots to the left of the CPU are permitted.
2
Secure the DIN rail.
3
data (Page 133).
4
Turn on the power supply.
5
6
them closed during operation.
3.3
Note on operation
NOTICE
Closing the front panels
3.3 Note on operation
One requirement for the commissioning of the module is the completeness of the STEP 7
project data (see below, step 5).
S7-1200 with the power turned off.
Table 3- 2 Procedure for installation and connecting up
Mount the CP on the DIN rail and connect it to
the module to its right.
Connect the Ethernet cable to the CP. You will find the pinout of the interface in the section Technical
The remaining steps in commissioning involve
downloading the STEP 7 project data.
Close the front covers of the module and keep
Use a 35 mm DIN rail.
The STEP 7 project data of the CP is transferred when you
load to the station. To load the station, connect the engineering station on which the project data is located to the Ethernet
interface of the CPU.
You will find more detailed information on loading in the following sections of the STEP 7 information system:
• "Loading project data"
• "Using online and diagnostics functions"
To ensure interference-free operation, keep the front panels of the module closed during
operation.
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 or use the CP 1543SP-1.
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.
You will find information on this in the information system of STEP 7.
● Security function of the communication
– Enable the security functions of the CP and set up the firewall.
If you connect to public networks, you should use the firewall. Think about the services
you want to allow access to the station via public networks. By using the "bandwidth
limitation" of the firewall, you can restrict the possibility of flooding and DoS attacks.
– Use the secure protocol variants NTP (secure) and SNMPv3.
– Using the security functions of the telecontrol protocols.
– Leave access to the Web server of the CPU (CPU configuration) and to the Web
server of the CP disabled.
● Logging function
Enable the function in the security configuration and check the logged events regularly for
unauthorized access.
● 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.
● 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.
● Use secure protocols when access to the device is not prevented by physical protection
measures.
– The NTP protocol provides a secure alternative with NTP (secure) if you do not use
telecontrol communication.
– The HTTP protocol provides a secure alternative with HTTPS when accessing the
For information on avoiding opening the port during diagnostics, see section Online
security diagnostics via port 8448 (Page 123).
39
Page 40
Configuration
4.2
Configuration in STEP 7
Configuration in STEP 7
Fitting CPs in a rack
Requirement for configuring the communication
How to configure telecontrol communication in STEP 7
Loading and storing the configuration data
4.2 Configuration in STEP 7
You configure the modules and networks in SIMATIC STEP 7. You will find the required
version in the section Software requirements (Page 23).
You can configure a maximum of three CMs/CPs per station.
One requirement for configuring communication between the CP and the communications
partner is the programming of the assigned CPU and the input and output data of the station.
PLC tags must also be created to assign the user data to the data points.
For more detailed information, refer to the following sections.
Follow the steps below when configuring:
1. Create a STEP 7 project.
2. Insert the required SIMATIC stations.
Configuration of control center devices and applications and connections between the CP
and partner is neither possible nor necessary.
3. Insert the CPs and the required input and output modules in the stations.
4. Create an Ethernet network.
5. Connect the stations to the Ethernet subnet.
6. Configure the inserted CPs.
For details on configuring the communication, refer to the following section.
7. Save the project.
You will find more detailed information on configuring the CP in the Information system of
STEP 7 and in the following sections.
When you load the station, the project data of the station including the configuration data of
the CP is stored on the CPU.
You will find information on loading the station in the STEP 7 information system.
Configurations with connections over the Internet: VPN connections
4.4
Time-of-day synchronization
Synchronization method of the CP
Note
Time-of-day synchronization of the CP
With applications that require time
synchronize the time of day of the CP regularly. If you do not synchronize the time of day of
the CP regularly, there may be deviations of several seconds per day in the time information
of the CP.
With security functions enabled, you
Note
Recommendation for setting the time
Synchronization with a external clock at intervals of approximately 10 seconds is
recommended. This achieves as small a deviation as possible between the internal time and
the absolute time.
4.4 Time-of-day synchronization
● Port number of the listener port of the master
● DNS server address(es)
You require the DNS server address if you address the master using a name that can be
resolved by DNS.
For connections running via the Internet, dynamic IP addresses can be used.
To allow communication in both directions and to ensure that the data is protected during
transfer, a connection with a VPN tunnel is necessary. For this the security modules of the
SCALANCE S or SCALANCE M series are available.
Remember the following points when configuring:
● You configure the master IP address as normal.
● When configuring the CP interface, configure the IP address of the router.
● You create the VPN configuration with SCALANCE S/M both for the station end and for
the control center end in STEP 7.
-of-day synchronization (e.g. telecontrol), you need to
The CP supports the following methods of time-of-day synchronization:
●
The CP adopts the time-of-day from the communications partner in the master station.
Only when telecontrol communication is enabled.
●
The time of day is synchronized by an NTP server in the connected network.
The method can also be used when the telecontrol communication is enabled.
With CPs as of firmware version V3, the address of the NTP server can also be entered
as a URL, e.g. <ntp.server.com>. For this a DNS server is required.
●
The secure method NTP (secure) uses symmetrical keys according to the hash
algorithms MD5 or SHA-1.
On the CP you specify the servers used.
You configure NTP servers of the type NTP (secure) in the global security settings of
STEP 7.
●
As of V4.2, the CPU synchronizes all CMs/CPs of the station with a synchronization cycle
of 10 seconds.
Parameters of the CPU:
If for the CPU the option "CPU synchronizes the modules of the device" is enabled, all
smart modules of the station (CPs with of firmware ≥ V2.1.77) are synchronized with the
CPU time in a synchronization cycle of 10 seconds.
You can configure time-of-day synchronization in the following parameter groups:
●
Here you create the configuration under the following conditions:
– Telecontrol communication is disabled.
– The security functions are disabled.
●
Here you create the configuration under the following condition:
Depending on the firmware version of the modules involved, the time
forwarded to the CPU in different ways:
•
•
CP firmware ≤ V2.1.6x
CP firmware ≥ V2.1.77 and CPU firmware ≥ V4.2
4.5
Communication types
"Communication types" parameter group
Enable telecontrol communication
4.5 Communication types
-of-day of the CP is
Optional forwarding of the CP time to the CPU using a PLC tag
Obligatory forwarding of the CP time to the CPU via the backplane bus
The forwarding of the CP time to the CPU depends on the firmware version of the CP and
the CPU. Note the following behaviour.
●
With this firmware version the CP can make the time-of-day available to the CPU as an
option via a PLC tag. When this PLC tag is read cyclically by the CPU, the CPU adopts
the CP time.
In the parameter group "Communication with the CPU", you can set whether or not the
current time of day of the CP will be made available to the CPU via a PLC tag. For TLC
tags, see parameter group "Communication with the CPU" of the CP.
●
If both modules in the station have the named firmware versions, the time of day of the
CP is automatically forwarded to the CPU.
Since the CPU automatically adopts the CP time, you no longer require the forwarding
option using the PLC tag.
If for the CPU the option "CPU synchronizes the modules of the device" is enabled in
"PROFINET interface > Time synchronization", all smart modules of the station are
synchronized with the CPU time.
In this parameter group, you enable the communication types of the CP.
To minimize the risk of unauthorized access to the station via Ethernet, you need to enable
the communications services that the CP will execute individually. You can enable all options
but at least one option should be enabled.
●
– TeleControl Basic
– DNP3
– IEC 60870-5
Note that if you change the telecontrol communication type later, all specific parameters
are deleted. These also include data point and partner information among other things.
45
Page 46
Configuration
Activate online functions
Enabling S7 communication
4.6
Ethernet interface
4.6.1
CP identification
CP addressing
4.6.2
Time-of-day synchronization
Time-of-day synchronization
4.6 Ethernet interface
●
Enables access to the CPU for the online functions via the CP (diagnostics, loading
project data etc.). If the function is enabled, the engineering station can access the CPU
via the CP.
If the option is disabled, you have no access to the CPU via the CP with the online
functions. Online diagnostics of the CPU with a direct connection to the interface of the
CPU however remains possible.
●
Enables the functions of S7 communication with a SIMATIC S7 on the CP.
If you configure S7 connections to the relevant station, and these run via the CP, you will
need to enable this option.
The parameter group is available only when telecontrol communication is enabled.
The parameter group is used for addressing and identification of the CP in the network.
● TeleControl Basic
You will find the parameters for the TeleControl Basic protocol in "Security", refer to the
section CP iIdentifcation with the TeleControl Basic protocol (Page 64).
● DNP3
The station address is the DNP address.
Entry of the station address (digits only). Permitted range of values: 1...65519.
● IEC
The station address is the “common address of the ASDU" or the address of the
information object.
Entry of the station address (digits only). Permitted range of values: 1...65534.
For the configuration of the time-of-day synchronization read the section Time-of-day
synchronization (Page 42).
The settings made here apply globally to all configured TCP connections of the CP.
Note the option of overwriting the values configured here for individual communications
partners, refer to the section Partner stations (Page 54).
●
Function: If there is no data traffic within the TCP connection monitoring time, the CP
sends a keepalive to the communications partner.
Default setting: 180 s. Permitted range: 1...65535 s.
–
The monitoring time is configured for the Ethernet interface globally for all TCP
connections. The parameter is preset to 180 seconds as default.
–
The parameter "TCP connection monitoring time" occurs again with the individual
partners in the parameter group "Connection to partner". This parameter applies only
to the individual partner. The value of 180 seconds preset on the Ethernet interface is
adopted for the individual partners.
If for any reason you want to change the value of the TCP connection monitoring time
for individual partners, you can adapt the value for every partner individually in
"Partner stations". If. for example, you want to check the connection at shorter
intervals, reduce the value.
●
After sending a keepalive, the CP expects a reply from the communications partner within
the keepalive monitoring time. If the CP does not receive a reply within the configured
time, it terminates the connection.
Default setting: 10 s. Permitted range: 1...65535 s.
–
The monitoring time is configured for the Ethernet interface as a global setting for all
TCP connections.
–
As with the TCP connection monitoring time, the value of "Partner stations" can be
adapted for each partner individually.
If the partner cannot be reached, connection establishment via the mobile wireless
network can take several minutes. This may depend on the particular network and current
network load.
Depending on your contract, costs may result from each connection establishment
attempt.
Send monitoring time
Watchdog monitoring time
4.6 Ethernet interface
●
The settings made here apply to the connection to the telecontrol server.
The reconnection delay is the waiting time between repeated attempts to establish the
connection by the CP when the telecontrol server is not reachable or the connection has
aborted.
This waiting time avoids continuous connection establishment attempts at short intervals
if there are connection problems.
A basic value is configured for the waiting time before the next connection establishment
attempt. Starting at the basic value, the current waiting time is doubled after every 3
unsuccessful retries up to a maximum value of 900 s.
Default setting: 10 s. Permitted range of values for the basic value: 10...300 s
Example:
A configured basic value 20 results in the following intervals (waiting times) between the
attempts to re-establish a connection:
– three times 20 s
– three times 40 s
– three times 80 s
– etc. up to max. 900 s
●
Time for the arrival of the acknowledgment from the partner (Telecontrol server) after
sending unsolicited frames. The time is started after sending an unsolicited frame. If no
acknowledgement has been received from the partner when the send monitoring time
elapses, the frame is repeated up to three times. After three unsuccessful attempts, the
connection is terminated and re-established.
Default setting: 60 s. Permitted range: 1...65535 s.
●
With the watchdog cycle, the CP checks the connection to the telecontrol server. The
watchdog cycle is the interval without data exchange between the CP and telecontrol
server after which the CP sends a watchdog frame to the telecontrol server. The
watchdog cycle is only configured with TCSB (parameter "Keepalive monitoring time").
The value configured in TCSB is transferred by the telecontrol server to the CP the first
time the connection is established.
Each time the CP transfers data to TCSB and receives the acknowledgment from the
telecontrol server, the CP starts the watchdog cycle. When the watchdog cycle has
expired the CP sends a watchdog frame to the telecontrol server.
After sending a watchdog frame, the CP starts the watchdog monitoring time within which
the CP expects a reply from the telecontrol server. If the CP does not receive a reply from
the Telecontrol server within the monitoring time, it terminates and re-establishes the
connection.
Default setting: 30 s. Permitted range: 0...65535 s. If you enter 0 (zero), the function is
disabled.
●
Here, you enter the interval in hours after which the key is exchanged again between the
CP and the telecontrol server. The key is a security function of the telecontrol protocol
used by the CP and TCSB V3.
Default setting: 8 s. Permitted range: 0...65535 s. If you enter 0 (zero), the function is
disabled.
●
The disturbance bit can be used as bit 1.6 (IIN1.6) of the "Internal Indication Bytes" to
indicate to the master when the CPU is in STOP mode.
●
Max. duration (seconds) between Select and Operate. For a Select command to be
transferred to the CPU and to take effect, no other frame may be sent to the station
between Select and Operate.
Permitted range: 1..65535
Default setting: 1
●
Number of frame repetitions at the Data Link Layer if no acknowledgement is received
from the master.
Permitted range: 0 ... 255
Default setting: 0
If you enter 0 (zero), the function is disabled.
●
Condition for the CP to request a connection confirmation from the master (never,
always, only with segmented frames).
Time (in seconds) within which an acknowledgement is expected from the master.
Permitted range: 0...65535
Default setting: 2
If you enter 0 (zero), the function is disabled.
●
Transfer mode for events
– Spontaneous
Event frames are transferred immediately.
– Conditional spontaneous
Event messages are only sent when spontaneous frames are sent or the partner
establishes the connection.
●
Maximum number of repetitions of unsolicited frames if no acknowledgement is received
from the communications partner .
Permitted range: 0...255
Default setting: 3
●
Time (in seconds) within which an acknowledgement of unsolicited frames is expected
from the master.
Permitted range: 1...65535
Default setting: 5
●
Here, for each of the three event classes you specify the number of events after which
the stored events are sent to the communications partner.
Permitted range: 1 ... 255.
●
Here, for each of the three event classes you specify the maximum time in seconds the
events can be stored in the send buffer before they are sent to the communications
partner.
Permitted range: 0 ... 65535
If you enter 0 (zero), the function is disabled.
●
Selection of an event class in which only the last current values are stored in the send
buffer.
In the default setting all values of events of classes 1 and 2 are stored in the send buffer,
of class 3 only the current values (image memory procedure).
When configuring the monitoring times t
corresponding settings on the master so that there are no unwanted error messages or
connection aborts.
4.6 Ethernet interface
You will find details of how the image buffer and send buffer work as well as the options for
transferring data in the section Process image, type of transmission, event classes, triggers
(Page 97).
●
Max. duration (seconds) between Select and Operate. For a Select command to be
transferred to the CPU and to take effect, no other frame may be sent to the station
between Select and Operate.
Permitted range: 1..65535
Default setting: 1
●
(t0)
Monitoring time for the connection establishment (t
) in seconds. If the communications
0
partner does not confirm connection establishment within the monitoring time, the CP
attempts to establish the connection again.
Permitted range: 1..255
Default setting: 30
●
(t1)
Monitoring time in seconds for the acknowledgement of frames sent by the CP by the
communications partner. The monitoring time applies to all frames sent by the CP in I, S
and U format.
If the partner does not send an acknowledgment during the monitoring time, the CP
terminates the connection to the partner.
Difference between send sequence number N(S) and receive sequence number N(R)
Max. number of unacknowledged data frames
4.6 Ethernet interface
●
(t2)
Monitoring time in seconds for the acknowledgment of data frames of the master by the
CP.
After receiving data from the master, the CP acknowledges the received data as follows:
– If the CP sends data to the master itself within t
received from the master during t
at the same time along with the sent data frame (I
2
, it acknowledges the data frames
2
format).
– The CP sends an acknowledgment frame (S format) to the master of the latest when t
elapses.
Permitted range: 1 ... 255
Default setting: 10
The value of t
●
should be less than that of t1.
2
(t3)
Monitoring time in seconds during which the CP has not received any frames from the
master.
When t
elapses, the CP sends a test/control frame (U format) to the master.
3
This parameter is intended for situations in which longer idle periods occur; in other
words, times when there is no data traffic.
Permitted range: 1 ... 255
Default setting: 30
●
The difference between the send sequence number and receive sequence number of a
frame.
(k)
2
The master returns the send sequence number of a frame from the CP that the sending
CP then saves as the receive sequence number. Frames whose send sequence number
is lower than the receive sequence number after the difference configured here is added
are evaluated as having been successfully transferred and are deleted from the send
buffer of the CP.
Permitted range: 1 ... 64
Default setting: 12
●
(w)
w: Maximum number of received data frames (I-APDUs), after which the oldest frame
received from the master must be acknowledged.
Permitted range: 1..8
Default setting: 8
The value must be less than the value of "Difference between send and receive
sequence number" (k).
With each sent data frame, the CP sends a continuous send sequence number. The data
frame remains initially stored in the send buffer.
When it receives the data frame, the master sends the send sequence number from this or
(if several frames are received) the last frame as an acknowledgement to the CP. The CP
saves the send sequence number returned by the master as a receive sequence number
and uses it as an acknowledgement.
Frames whose send sequence number is equal to or lower than the current receive
sequence number are evaluated as having been successfully transferred and are deleted
from the send buffer of the CP.
Recommendations of the specification:
● w should not be higher than 2/3 of k.
● Recommended value for k: 12
● Recommended value for w: 8
The CP supports the following SNMP versions:
●
Available with security functions disabled.
Note that with this read and write access to the module is possible. In this case, other
settings are not possible.
The configuration of the community strings is only possible if the security functions are
enabled.
The CP uses the following community strings to authenticate access to its SNMP agent
via SNMPv1:
Read and write access private
●
Available only when security functions are enabled
For information on the configuring SNMPv3, refer to the section SNMP (Page 70).
The station address of the telecontrol server is assigned automatically by the system if
telecontrol communication is enabled.
– DNP3
For identification the station address mut be configured on the master.
– IEC
Common ASDU address
●
IP address or host name (FQDN) of the partner. This can, for example, also be the FQDN
of a DynDNS service.
– Note on TeleControl Basic
If the CP is connected to a TCSB redundancy group (TCSB V3), here configure the
public IP address of the DSL router via which the telecontrol server can be reached
from the Internet. Set the port forwarding on the DSL router so that the public IP
address (external network) is led to the virtual IP address of the TCSB server PCs
(internal network). The station does not therefore receive any information telling it
which of the two computers of the redundancy group it is connected to.
See also section Addressing in the redundant TCSB system (Page 57).
●
When the function is enabled, the connection to the communications partner is monitored
by sending keepalive frames.
The TCP connection monitoring time is set for all TCP connections of the CP in the
parameter group of the Ethernet interface. The setting applies to all TCP connections of
the CP.
Here in the parameter group "Partner stations", the globally set TCP connection
monitoring time can be set separately for the partner. The value set here for the partner
overwrites the global value that was set in the "Ethernet interface (X1) > Advanced
options > TCP connection monitoring" parameter group.
Function: If there is no data traffic within the TCP connection monitoring time, the CP
sends a keepalive to the communications partner.
Default setting: 180 s. Permitted range: 1...65535 s.
The monitoring time is specified at a higher level for the Ethernet interface as the default
for all configured TCP connections.
–
The monitoring time is configured for the Ethernet interface globally for all TCP
connections. The parameter is preset to 180 seconds as default.
–
The parameter "TCP connection monitoring time" occurs again with the individual
partners in the parameter group "Connection to partner". This parameter applies only
to the individual partner. The value of 180 seconds preset on the Ethernet interface is
adopted for the individual partners.
If for any reason you want to change the value of the TCP connection monitoring time
for individual partners, you can adapt the value for every partner individually in
"Partner stations". If. for example, you want to check the connection at shorter
intervals, reduce the value.
●
If the value configured here differs from the value configured in the Ethernet interface
parameter group, the monitoring time of the "Partner stations" parameter group is used.
After sending a keepalive, the CP expects a reply from the communications partner within
the keepalive monitoring time. If the CP does not receive a reply within the configured
time, it terminates the connection.
Default setting: 10 s. Permitted range: 1...65535 s.
–
The monitoring time is configured for the Ethernet interface as a global setting for all
TCP connections.
–
As with the TCP connection monitoring time, the value of "Partner stations" can be
adapted for each partner individually.
●
In the "Permanent" connection mode, there is a permanent connection to the
communications partner.
The CP only supports this connection mode.
●
Specifies the communications partner that establishes the connection (always the CP).
Addressing of the TCSB redundancy group by the stations using one IP address
4.8 Partner stations
●
Selection of the protocol type on the transport layer: TCP / UDP
●
Number of the listener port of the telecontrol server.
●
In the LAN in the master station to which the TCSB server PCs and the DSL router (e.g.
SCALANCE M) are connected, the Network Load Balancing (NLB) of the computer
operating system will assign a common virtual IP address to the two server PCs.
This IP address is configured depending on the network setup:
– If only one CP without a DSL router is connected, the virtual address assigned by the
NLB must be configured in the CP as the IP address of the telecontrol server.
– If a DSL router is used, only one IP address will be configured to address the
redundant telecontrol server in the stations, the public address of the DSL router.
Set the port forwarding on the DSL router so that the public IP address (external
network) is led to the virtual IP address of the TCSB server PCs (internal network).
Only the public IP address is reachable from the Internet. The station does not
therefore receive any information telling it which of the two computers of the
redundancy group it is connected to.
As soon as the fill level drops below 50%, bits 2 and 3 are reset to 0.
Bits 4 to 15 of the PLC tags are not used and do not need to be evaluated in the program.
In this table, you specify the S7 stations with which the current station will use inter-station
communication. Connections for inter-station communication run via the telecontrol server.
The partner number is assigned by the system. It is required during data point configuration
to assign data points to their communications partners.
For inter-station communication, the partner is addressed with the parameters "Project",
"Station" and "Slot".
Here, enter the project number of the CP in the partner station. (Parameter group "Security >
CP identification" on the partner)
Here, enter the station number of the CP in the partner station. (Parameter group "Security >
CP identification" on the partner)
Here, enter the slot number of the CP in the partner station via which the connection will be
established.
Activate the option for enabling inter-station communication.
The frames are stored in the send buffer (frame memory) of the CP if the connection is
disturbed. Note that the capacity of the frame memory is shared by all communications
partners.
The access ID displayed here is formed from the hexadecimal values of project number,
station number and slot. The parameter of the type DWORD is allocated as follows:
● Bits 0 - 7: Slot
● Bits 8 - 20: Station number
● Bits 21 - 31: Project number
●
If the CP does not receive a sign of life from the communications partner within the
configured time, the CP interprets this as a fault/error on the partner. The CP aborts the
connection and attempts to re-establish it.
If you enter 0, the function is deactivated.
●
Indicates the DNP3 implementation level supported by the CP
In the DNP3 specification, various levels of protocol conformity are and they describe the
supported range of functions (subset) of a master or a station. These levels
(implementation levels) are known as "DNP3 Application Layer protocol Level" and
abbreviated with DNP3-L1 to DNP3-L4.
For the communication between the CP and the master, the DNP3 level supported by the
master must be known.
The selection of the level used by the DNP3 CP which must correspond to that of the
connected master is set separately in STEP 7 for each individual communications partner
(DNP3 master).
The CP supports the following implementation levels:
– Level 1
– Level 2
– Level 3
– Level 4
– Level 4+
The implementation level known here as Level 4+ that is not specified in the standard
contains the range of functions of Level 4 and in addition support of the following DNP3
data types / variations:
– 64-bit analog value as floating-point number without time of day
– 64-bit analog value as floating-point number with time of day
– Counter event with time of day in 16-bit format
– Counter event with time of day in 32-bit format
●
Mode with which DNP events are transferred to this communications partner:
– Chronological transfer of individual frames
or
– Transfer of collected frames per data point as a block.
●
If the "Report partner status" function is enabled, the CP signals the status of the
communication to the remote partner.
– Bit 0 of "PLC tag for partner status" (data type WORD) is set to 1 if the partner can be
reached.
– Bit 1 is set to 1 if all the paths to the remote partner are OK (useful with redundant
paths).
– Bit 2 indicates the status of the send buffer (frame memory).
The following values are possible:
- 0: Send buffer OK
- 1: Send buffer threatening to overflow (more than 80 % full).
As soon as the fill level drops below 50%, bit 3 is reset to 0.
Bits 3 to 15 of the PLC tags are not used and do not need to be evaluated in the program.
Using the first three parameters you specify the CPU access by the CP in the CPU scan
cycle. You will find the structure of the CPU scan cycle in the section Read cycle (Page 96).
The fourth parameter "Frame memory size" decides the size of the send buffer on the CP for
frames of data points that are configured as an event.
●
Wait time between two scan cycles of the CPU memory area
●
Maximum number of write jobs to the CPU memory area within a CPU scan cycle
●
Maximum number of low-priority read jobs from the CPU memory area within a CPU scan
cycle.
●
Here, you set the size of the frame memory for events (send buffer).
The size of the frame memory is divided equally among all configured communications
partners. You will find the size of the frame memory in the section Configuration limits
and performance data (Page 15).
You will find details of how the send buffer works (storing and sending events) as well as
the options for transferring data in the section Process image, type of transmission, event
classes, triggers (Page 97).
●
Via the watchdog bit the CPU can be informed of the status of the telecontrol
communication of the CP.
●
Using this function, the CP can make its time of day available to the CPU.
You will find details in the STEP 7 information system.
Note
Fast setting of the diagnostics trigger variable
Triggers mu
Frame memory overflow
Frame memory size
Date of last successful logon to TCSB
Date of last unsuccessful logon to TCSB
TeleService status
4.8 Partner stations
With the parameter group, you have the option of reading out advanced diagnostics data
from the CP using PLC tags.
●
Enable the option to be able to use advanced CP diagnostics.
If the option is enabled, at least the "Diagnostics trigger tag" must be configured.
The following PLC tags for the individual items of diagnostics data can be enabled
selectively.
●
If the PLC tag (BOOL) from the user program of the CPU is set to 1, the CP updates the
values of the PLC tags that can then be configured for the advanced diagnostics.
After writing the current values to the following PLC tags, the CP sets the "Diagnostics
trigger tag" to 0 signaling the CPU that the updated values can be read from the PLC
tags.
st not be set faster than a minimum interval of 500 milliseconds.
●
PLC tag (data type byte) for the send buffer overflow pre-warning. Bit 0 is set to 1 when
80% of the fill level of the send buffer is reached.
●
PLC tag (data type DWord) for the occupation of the send buffer. The number of saved
frames is displayed.
●
Only for the TeleControl Basic protocol
PLC tag (data type DTL) for the date on which the CP last logged in to the telecontrol
server.
●
Only for the TeleControl Basic protocol
PLC tag (data type DTL) for the date on which the CP was last unable to log in to the
telecontrol server.
●
The PLC tag (BOOL) indicates whether a TeleService session is active.
CP iIdentifcation with the TeleControl Basic protocol
4.9 Security
●
Here you make the settings for the SNMP agent on the CP.
See section SNMP (Page 70).
●
See section Certificate manager (Page 72).
In the global security settings of STEP 7 among other things you will find the following
parameter groups:
●
Here you configure the VPN communication, refer to the section VPN (Page 74).
●
Here you configure the users, roles and rights for the TeleService access, refer to the
section Configuration of the TeleService access (Page 80).
In the "CP identification" parameter group, you configure the following information for
authenticating the CP with the telecontrol server:
● Project number
The project number is the same for all telecontrol CPs in a STEP 7 project. TCSB
evaluates project numbers from 1 ... 2000.
If you change the project number, this parameter is changed for all CPs in the STEP 7
project.
● Station number
For each S7-1200 station with a telecontrol CP, an individual station number is
configured. TCSB evaluates station numbers from 1 ... 8000.
● Telecontrol password
Password for the authentication of the CP on the telecontrol server
8 ... 29 characters of the ASCII character set 0x20...0x7e
The password can be the same for all CPs of the STEP 7 project. The same password is
configured in TCSB for this station.
● Access ID
The displayed Access ID is formed from the hexadecimal values of project number,
station number and slot. The parameter of the type DWORD is allocated as follows:
Preliminary remarks: Authentication and key exchange
Parameters
Enable DNP3 security options
IKE mode
Security statistics
4.9 Security
If the security function is enabled, the DNP3 master and CP authenticate themselves with a
secret key, the pre-shared key.
With the help of the common pre-shared key, after the first connection establishment
between master and CP session keys are agreed that are then renewed cyclically. Renewal
of the session keys is normally initiated by the master. The criteria for renewing the key are
specified in the following parameters.
● Key exchange interval
● Authentication requests before key exchange
As soon as one of these conditions is met, the session key is renewed.
●
Enable the option if you want to use the security mechanisms.
●
Selection of the mode for key exchange. Range of values:
– Aggressive Mode
– Main Mode
Default setting: Aggressive Mode
●
Specifies whether the statistics of security events are sent to the master. Security events
are authentication requests to the CP. If the option is enabled, all authentication requests
with date, time and result are saved on the CP and sent to the master for further
evaluation.
Range of values:
– Do not send security statistics
– Send security statistics
Default setting: Do not send security statistics
The Aggressive Mode is somewhat faster but transfers the identity unencrypted.
Setting to select whether the CP may use the secure hash algorithm SHA-1 if "SHA-256"
was configured as the Secure hash algorithm and the master does not support SHA-256.
Range of values:
– SHA-1 mode not allowed
The CP may not use SHA-1. If the master does not support SHA-256, no connection
will be established.
– SHA-1 mode allowed
The CP can use SHA-1 if the master does not support SHA-256.
Default setting: SHA-1 mode not allowed
●
Selection of the Secure Hash Algorithm (SHA)
Range of values:
– SHA-1
– SHA-256
Default setting: 256
●
Selection of the Advanced Encryption Standard (AES)
Range of values:
– AES-128
– AES-256
Default setting: AES-128
●
Specifies the length of the pre-shared key in bytes.
Permitted range: 16 - 128 Depending on the secure hash algorithm configured in STEP 7
above, the following lengths are preset:
– For SHA-1: 16
– For SHA-256: 32
The value 0 (zero) is not permitted.
●
If the configured number of statistics queries of the master is exceeded within the key
exchange interval, the CP enters a message in the diagnostics buffer of the CPU.
Maximum number of authentication requests of the CP with the master. When this
number is reached, the session key is renewed.
Range of values: 1...10000 Default setting: 1000
Recommendation: Set the number for the CP twice as high as for the master.
●
Period after which the key is exchanged again between the CP and the master. The
interval must be matched up on both communications partners.
Range of values: 0...65535 min. at 0 (zero), the key is never changed (function disabled).
Default setting: 15 min.
Recommendation: Set the key exchange interval for the CP twice as high as for the
master.
●
Maximum waiting time for the response from the master to an authentication request of
the CP.
Exceeding the wait time is evaluated as an error by the CP. In this case, the CP
generates a security event and sends this to the master.
Range of values: 1... 65535 s Default setting: 5
●
The pre-shared key can be configured in two ways:
– Manual configuration
Enter the pre-shared key in STEP 7 manually as a hexadecimal value.
– Import as file
Import the pre-shared key from the file system of the engineering station if the preshared key was generated by the master or another engineering system.
The pre-shared key of the CP must be identical to the pre-shared key of the master.
Each incoming or outgoing frame initially runs through the MAC firewall (layer 2). If the frame
is discarded at this level, it will not be checked by the IP firewall (layer 3). This means that
with suitable MAC firewall rules, IP communication can be restricted or blocked.
Notation for the source IP address (advanced firewall mode)
4.9.4.3
Firewall settings for configured connection connections via a VPN tunnel
IP rules in advanced firewall mode
See also
4.9.4.4
Settings for online security diagnostics and downloading to station with the firewall
activated
Setting the firewall for online functions
4.9 Security
If you specify an address range for the source IP address in the advanced firewall settings of
the CP, make sure that the notation is correct:
● Separate the two IP addresses only using a hyphen.
Correct: 192.168.10.0-192.168.10.255
● Do not enter any other characters between the two IP addresses.
Incorrect: 192.168.10.0 - 192.168.10.255
If you enter the range incorrectly, the firewall rule will not be used.
If you set up configured connection connections with a VPN tunnel between the CP and a
communications partner, you will need to adapt the local firewall settings of the CP:
In advanced firewall mode ("Security > Firewall > IP rules") select the action "Allow*" for both
communications directions of the VPN tunnel.
Settings for online security diagnostics and downloading to station with the firewall activated
(Page 68)
With the security functions enabled, follow the steps outlined below:
1. In the global security settings (see project tree), select the entry "Firewall > Services >
Define services for IP rules".
2. Select the "ICMP" tab.
3. Insert a new entry of the type "Echo Reply" and another of the type "Echo Request".
4. Now select the CP in the S7 station.
5. Enable the advanced firewall mode in the local security settings of the CP in the "Security
> Firewall" parameter group.
7. In the table, insert a new IP rule for the previously created global services as follows:
– Action: Allow; "From external -> To station " with the globally created "Echo request"
service
– Action: Allow; "From station -> to external" with the globally created "Echo reply"
service
8. For the IP rule for the Echo Request, enter the IP address of the engineering station in
"Source IP address". This ensures that only ICMP frames (ping) from your engineering
station can pass through the firewall.
With special events, e.g. CPU STOP, the CP can send e-mails. It does not depend on
whether telecontrol communication is used.
When using telecontrol communication, additionally configured events in the process image
of the CPU can trigger the sending of e-mails. Along with the e-mail process data can also
be sent.
You configure the individual e-mails in the message editor (entry "Messages"), see section
Messages (Page 113)
The following requirements must be met in the configuration for sending e-mails:
● The security functions are enabled.
● The time of the CP is synchronized.
● In the "E-mail configuration" entry, the protocol to be used and the data for access to the
With the default setting of the SMTP port 25, the module transfers unencrypted e-mails.
If your e-mail service provider only supports encrypted transfer, use one of the following
options:
● Port no. 587
e-mail server are configured.
By using STARTTLS, the module sends encrypted e-mails to the SMTP server of your email service provider.
Recommendation: If your e-mail provider offers both options (STARTTLS / SSL/TLS), you
should use STARTTLS with port 587.
● Port no. 465
By using SSL/TLS (SMTPS), the module sends encrypted e-mails to the SMTP server of
your e-mail service provider.
Communications problems if the value for system events is set too high
4.9.7
SNMP
SNMP
SNMP
"Enable SNMP"
4.9 Security
Ask your e.mail service provider which option is supported.
To be able to use encrypted transfer, you need to load the certificate of your e-mail account
in the certificate manager of STEP 7. You obtain the certificate from your e-mail service
provider.
Use the certificate by taking the following steps:
1. Save the certificate of your e-mail service provider in the file system of the engineering
station.
2. Import the certificate into your STEP 7 project with "Global security settings > Certificate
manager".
3. Use the imported certificate with every module that uses encrypted e-mails via the
"Certificate manager" table in the local "Security“ parameter group.
For the procedure, refer to the section Handling certificates (Page 72).
If the value for filtering the system events is set too high, you may not be able to achieve the
maximum performance for the communication. The high number of output error messages
can delay or prevent the processing of the communications connections.
In "Security > Log settings > Configure system events", set the "Level:" parameter to the
value "3 (Error)" to ensure the reliable establishment of the communications connections.
The range of functions of the CP for SNMP can be found in the section SNMP (Page 125).
If the security functions are enabled, you have the following selection and setting options.
●
If the option is enabled, communication via SNMP is released on the device. As default,
SNMPv1 is enabled.
If the option is disabled, queries from SNMP clients are not replied to either via SNMPv1
or via SNMPv3.
Enables the use of SNMPv1 for the CP. For information on the configuration of the
required community strings see below (SNMPv1).
●
Enables the use of SNMPv3 for the CP. For information on the configuration of the
required algorithms see below (SNMPv3).
The community strings need to be sent along with queries to the CP via SNMPv1.
●
The string is required for read access.
Leave the preset string "public" or configure a string.
●
If the option is enabled write access to the CP is released and the corresponding
community string can be edited.
●
The string is required for write access and can also be used for read access.
Leave the preset string "private" or configure a string.
Note the use of lowercase letters with the preset community strings!
The algorithms need to be configured for encrypted access to the CP via SNMPv3.
●
Select the authentication method to be used from the drop-down list.
●
Select the encryption method to be used from the drop-down list.
Note the information on security of the possible algorithms in the online help of the SCT.
In the user management that you will find in the global security settings, assign the various
users their role.
Below the properties of the roles you can see the rights list of the particular role, for example
the various types of access using SNMP. For new roles, you can freely configure individual
rights.
You will find information on users, roles and the password policy in the information system of
STEP 7.
Note
No certificate with security functions disabled.
If the security functions of the CP are disabled in the STE
generated for the CP.
4.9 Security
If you use communication with authentication for the module, for example SSL/TLS for
secure transfer of e-mails, certificates are required. You need to import certificates of nonSiemens communications partners into the STEP 7 project and download them to the
module with the configuration data:
1. Import the certificates of the communications partners using the certificate manager in the
global security settings.
2. Then assign the imported certificates to the module in the table below the local security
settings of the module.
For a description of the procedure, refer to the section Handling certificates (Page 72).
You will find further information in the STEP 7 information system.
If you have configured secure communication with authentication for the CP, own certificates
and certificates of the communications partner will be required for communication to take
place.
All nodes of a STEP 7 project with enabled security functions are supplied with certificates.
The STEP 7 project is the certification authority.
For the secure transfer of e-mails via SSL/TLS and SSL certificate is created for the CP. It is
visible in STEP 7 in "Global security settings > Certificate manager > Device certificates".
The table "Device certificates" shows the issuer, validity, use of a certificate
(service/application) and the use of a key. You can call up further information about a
certificate by selecting the certificate in the table and selecting the shortcut menu "Show".
The table also shows all other certificates generated by STEP 7 and all imported certificates.
Importing third-party certificates from communications partners
Assigning certificates locally
Exporting certificates for applications of third-party vendors (e.g. logging server)
4.9 Security
So that the CP can communicate with non-Siemens partners when the security functions are
enabled, the relevant certificates of the partners must be exchanged during communication.
To supply the CP with third-party certificates, follow the steps below:
1. Importing third-party certificates from communications partners
⇒ Global security settings of the project (certificate manager)
2. Assigning certificates locally
⇒ Local security settings of the CP ("Certificate manager" table)
These two steps are described in the next two sections.
Import the certificates of the communications partners of third-party vendors using the
certificate manager in the global security settings. Follow the steps outlined below:
1. Save the third-party certificate in the file system of the PC of the connected engineering
station.
2. In the STEP 7 project open the global certificate manager:
Global security settings > Certificate manager
3. Open the "Trusted certificates and root certification authorities" tab.
4. Click in a row of the table can select the shortcut menu "Import".
5. In the dialog that opens, import the certificate from the file system of the engineering
station into the STEP 7 project.
To be able to use an imported certificate for the CP, you need to specify it in the "Security"
parameter group of the CP. Follow the steps outlined below:
1. In the STEP 7 project select the CP.
2. Navigate to the parameter group "Security > Certificate manager".
3. In the table, double-click on the cell with the entry "<Add new>".
The "Certificate manager" table of the Global security settings is displayed.
4. In the table. select the required third-party certificate and to adopt it click the green check
mark below the table.
The selected certificate is displayed in the local table of the CP.
Only now will the third-party certificate be used for the CP.
For communication with applications of third-party vendors, the third-party application
generally also requires the certificate of the CP.
You export the certificate of the CP for communications partners from third-party vendors in
much the same way as when importing (see above). Follow the steps outlined below:
1. In the STEP 7 project open the global certificate manager:
Global security settings > Certificate manager
2. Open the "Device certificates" tab.
3. In the table select the row with the required certificate and select the shortcut menu
"Export".
4. Save the certificate in the file system of the PC of the connected engineering station.
Now you can transfer the exported certificate of the CP to the system of the third-party
vendor.
If you use a logging server in your system, export the SSL certificate for the authentication of
the CP on the server.
STEP 7 adopts the properties "DNS name", "IP address", and "URI" from the parameter
"Subject Alternative Name" (Windows: "Alternative applicant name") from the STEP 7
configuration data.
You can change this parameter of a certificate inn the certificate manager of the global
security settings. To do this, select the a certificate in the table of device certificates and call
the shortcut menu "Renew". Properties of the parameter "Alternative name of the certificate
owner" changed in STEP 7 are not adopted by the STEP 7 project.
Virtual Private Network (VPN) is a technology for secure transportation of confidential data in
public IP networks, for example the Internet. With VPN, a secure connection (tunnel) is set
up and operated between two secure IT systems or networks via a non-secure network.
One of the main features of the VPN tunnel is that it forwards all frames even from protocols
of higher layers (HTTP, FTP etc.).
The data traffic between two network components is transported practically unrestricted
through another network. This allows entire networks to be connected together via a
neighboring or intermediate network.
● VPN forms a logical subnet that is embedded in a neighboring (assigned) network. VPN
uses the usual addressing mechanisms of the assigned network, however in terms of the
data, it transports its own frames and therefore operates independent of the rest of this
network.
● VPN allows communication of the VPN partners with the assigned network.
● VPN is based on tunnel technology and can be individually configured.
● Communication between the VPN partners is protected from eavesdropping or
manipulation by using passwords, public keys or a digital certificate (authentication).
● Local area networks can be connected together securely via the Internet ("site-to-site"
connection).
● Secure access to a company network ("end-to-site" connection)
● Secure access to a server ("end-to-end" connection)
● Communication between two servers without being accessible to third parties (end-to-end
or host-to-host connection)
● Ensuring information security in networked automation systems
● Securing the computer systems including the associated data communication within an
automation network or secure remote access via the Internet
● Secure remote access from a PC/programming device to automation devices or networks
protected by security modules via public networks.
With Industrial Ethernet Security, individual devices or network segments of an Ethernet
network can be protected:
● Access to individual devices and network segments protected by security modules is
allowed.
● Secure connections via non-secure network structures becomes possible.
Due to the combination of different security measures such as firewall, NAT/NAPT routers
and VPN via IPsec tunnels, security modules protect against the following:
Creating a VPN tunnel for S7 communication between stations
Requirements
Note
Communication also possible via an IP router
Communication between the two stations is also possible via an IP router. To use this
communications path, however, you need to make further settings.
Procedure
Creating a security user
4.9 Security
To allow a VPN tunnel to be created for S7 communication between two S7 stations or
between an S7 station and an engineering station with a security CP (for example CP 1628),
the following requirements must be met:
● The two stations have been configured.
● The CPs in both stations must support the security functions.
● The Ethernet interfaces of the two stations are located in the same subnet.
To create a VPN tunnel, you need to work through the following steps:
1. Creating a security user
If the security user has already been created: Log on as a user.
2. Select the "Activate security features" check box
3. Creating the VPN group and assigning security modules
4. Configure the properties of the VPN group
5. Configure local VPN properties of the two CPs
You will find a detailed description of the individual steps in the following paragraphs of this
section.
To create a VPN tunnel, you require appropriate configuration rights. To activate the security
functions, you need to create at least one security user.
1. In the local security settings of the CP, click the "User login" button.
Result: A new window opens.
2. Enter the user name, password and confirmation of the password.
3. Click the "Logon" button.
You have created a new security user. The security functions are now available to you.
Creating the VPN group and assigning security modules
Note
Current date and current time on the CP for VPN connections
Normally, to establish a VPN connection and the associated recognition of the certificates to
be exchanged, the current date and the current time are required on both stations.
The establishment of a VPN connection to an engineering
server at the same time (TCSB installed), runs as follows along with the time of day
synchronization of the CP:
On the engineering station (with TCSB), you want the CP to establish a VPN connection.
The VPN connection
Otherwise the certificates used are evaluated as valid and the secure communication will
work.
Following connection establishment, the CP synchronizes its time of day with the PC
because the
Configure the properties of the VPN group
4.9 Security
After logging on, you need to select the "Activate security features" check box in the
configuration of both CPs.
You now have the security functions available for both CPs.
1. In the global security settings, select the entry "Firewall" > "VPN groups" > "Add new VPN
group".
2. Double-click on the entry "Add new VPN group", to create a VPN group.
Result: A new VPN group is displayed below the selected entry.
3. In the global security settings, double-click on the entry "VPN groups" > "Assign module
to a VPN group".
4. Assign the security modules between which VPN tunnels will be established to the VPN
group.
station that is also the telecontrol
is established even if the CP does not yet have the current time.
telecontrol server is the time master if telecontrol communication is enabled.
1. Double-click on the newly created VPN group.
Result: The properties of the VPN group are displayed under "Authentication".
2. Enter a name for the VPN group. Configure the settings of the VPN group in the
properties.
These properties define the default settings of the VPN group that you can change at any
time.
You specify the VPN propertie
group of the relevant module.
Result
4.9.10.3
VPN communication with SOFTNET Security Client (engineering station)
VPN tunnel communication works only if the internal node is disabled
4.9 Security
s of the CPs in the "Security" > "Firewall" > "VPN" parameter
You have created a VPN tunnel. The firewalls of the CPs are activated automatically: The
"Activate firewall" check box is selected as default when you create a VPN group. You
cannot deselect the check box.
Download the configuration to all modules that belong to the VPN group.
Setting up VPN tunnel communication between the SOFTNET Security Client and the CP is
essentially the same as described in Creating a VPN tunnel for S7 communication between
stations (Page 76).
Under certain circumstances the establishment of VPN tunnel communication between
SOFTNET Security Client and the CP fails.
SOFTNET Security Client also attempts to establish VPN tunnel communication to a lowerlevel internal node. This communication establishment to a non-existing node prevents the
required communication being established to the CP.
To establish successful VPN tunnel communication to the CP, you need to disable the
internal node.
Use the procedure for disabling the node as explained below only if the described problem
occurs.
Disable the node in the SOFTNET Security Client tunnel overview:
1. Remove the checkmark in the "Enable active learning" check box.
The lower-level node initially disappears from the tunnel list.
2. In the tunnel list, select the required connection to the CP.
3. With the right mouse button, select "Enable all members" in the shortcut menu.
The lower-level node appears again temporarily in the tunnel list.
4. Select the lower-level node in the tunnel list.
5. With the right mouse button, select "Delete entry" in the shortcut menu.
Result: The lower-level node is now fully disabled. VPN tunnel communication can be
established.
Configuration of a VPN connection between CP and TCSB
4.9.10.5
Establishment of VPN tunnel communication between the CP and SCALANCE M
4.9.10.6
CP as passive subscriber of VPN connections
Setting permission for VPN connection establishment with passive subscribers
4.9 Security
For secure communication via a VPN tunnel, the communications partners are assigned to a
common VPN group. The configuration of a VPN connection between CP and TCSB is not
directly possible because the telecontrol server cannot be configured in STEP 7.
To configure the communication between the CP 1243-1 and TCSB via a VPN connection,
follow the steps below:
● Create a PC station as a substitute for the telecontrol server.
This PC station serves as a placeholder for the telecontrol server only for configuration of
the security group and it is not required for any other purpose.
● To set up the security functions you then have the following alternative options:
– Install a CP 1628 (security module) on the computer of the telecontrol server and
assign the CP 1243-1 and the CP 1628 to the same security group in the
configuration.
– Install the SOFTNET Security Client (license required) on the computer of the
telecontrol server and configure the security functions in the STEP 7 project.
With both options you achieve the requirements at the TCSB end for secure communication
between the CPs of the remote station and the telecontrol server via secure VPN
connections.
Configure the security functions of the CPs as described above.
Create a VPN tunnel between the CP and a SCALANCE M router as described for the
stations.
VPN tunnel communication will only be established if you have selected the check box
"Perfect Forward Secrecy" in the global security settings of the created VPN group ("VPN
groups > Authentication").
If the check box is not selected, the CP rejects establishment of the tunnel.
If the CP is connected to another VPN subscriber via a gateway, you need to set the
permission for VPN connection establishment to "Responder".
This is the case in the following typical configuration:
VPN subscriber (active) ⇔ gateway (dyn. IP address) ⇔ Internet ⇔ gateway (fixed IP
address) ⇔ CP (passive)
The two tables "Roles" and "Rights of the role" become visible.
If necessary open the "Roles view" if this is hidden by the "Rights of the role" table.
In the "Roles" table (at the top) create a new user-defined role for TeleService.
3. In the "User" tab create a user that will later be allowed to execute the TeleService
functions for the CP.
Configure the following parameters:
– User name
Assign the name of the user that will have TeleService rights.
You require the user name at the start of a TeleService session.
– Authentication method
Select the authentication method "Password" for this user.
– Password
Assign the password.
You require the password at the start of a TeleService session.
Note:
You specify the password properties of the security functions in the "Password
policies" tab.
You enter the password on the engineering station when starting a TeleService
session.
– Maximum time of the session
The time that can be configured here is only required for access to SCALANCE S
modules. If the user is set up only for TeleService sessions, you can leave the default
value unchanged.
4. Click on the "Roles" tab.
5. Select the CP in the lower list "Rights of the role" under the "Module rights" group.
6. The available rights are displayed in the "List of rights" table.
The right "Use TeleService" is displayed.
7. Enable the "Use TeleService" right for the module.
8. Following this, set the S7 protocol to "allow" in Firewall.
Requirement: Created PLC tags and/or data blocks (DBs)
Note
Number of PLC tags
Remember the maximum possible number of PLC tags
configuration in the section
Access to the memory areas of the CPU
Configuring the data points and messages in STEP 7
4.10 Data points
No program blocks need to be programmed for telecontrol modules with data point
configuration to transfer user data between the station and communications partner.
The data areas in the memory of the CPU intended for communication with the
communications partner are configured data point-related on the module. Each data point is
linked to a PLC tag or the tag of a data block.
PLC tags or DBs must first be created in the CPU program to allow configuration of the data
points.
The PLC tags for data point configuration can be created in the standard tag table or in a
user-defined tag table. All PLC tags intended to be used for data point configuration must
have the attribute "Visible in HMI".
Address areas of the PLC tags are input, output or bit memory areas on the CPU.
Configuration limits and performance data (Page 15).
The formats and S7 data types of the PLC tags that are compatible with the protocol-specific
data point types of the module can be found in the section Datapoint types (Page 89).
The values of the PLC tags or DBs referenced by the data points are read and transferred to
the communications partner by the module.
Data received from the communications partner is written by the module to the CPU via the
PLC tags or DBs.
You configure the data points in STEP 7 in the data point and message editor. You can find
this using the project tree:
Project > directory of the relevant station > Local modules > CP
By double-clicking on the entry, the data point or message editor.
Using the two entries to the right above the table, you can switch over between the data
point and message editor.
Figure 4-2 Switching over between the two editors
With the data point or message editor open, create a new object (data point / message) by
double clicking "<Add object>" in the first table row with the grayed out entry.
A preset name is written in the cell. You can change the name to suit your purposes but it
must be unique within the module.
Figure 4-3 Data point table
You configure the remaining properties of every object using the drop-down lists of the other
table columns and using the parameter boxes shown at the bottom of the screen.
The mechanisms described here also apply when you need to assign the value of a
parameter to a PLC tag. The input boxes fro the PLC tag (e.g.: PLC tag for partner status
support the functions described here for selecting the PLC tag.
Arranging and copying objects
4.10 Data points
After creating it, you assign a new data point to its data source. Depending on the data type
of the data point a PLC tag can serve as the data source.
For the assignment you have the following options:
● Click on the table symbol
in the cell of the "PLC tag" column.
All configured PLC tags and the tags of the created data blocks are displayed. Select the
required data source with the mouse or keyboard.
● Click the symbol
.
A selection list of the configured PLC Tags and the blocks is displayed. From the relevant
table, select the required data source.
● In the name box of the PLC tag, enter part of the name of the required data source.
All configured PLC tags and tags of the data blocks whose names contain the letters you
have entered are displayed.
Select the required data source.
As with many other programs in the data point or message editor you can also arrange the
columns, sort the table according to your requirements and copy and insert objects.
● Arrange columns
If you click on a column header with the left mouse button pressed, you can move the
column.
● Sorting objects
If you click briefly with the left mouse button on a column header, you can sort the objects
of the table in ascending or descending order according to the entries in this column. The
sorting is indicated by an arrow in the column header.
After sorting in descending order of a column the sorting can be turned off by clicking on
the column header again.
You can reach this function with the following actions:
– Using the shortcut menu that opens when you click on a column header with the right
mouse key.
"Optimize width", "Optimize width of all columns"
– If you move the cursor close to the limit of a column header, the following symbol
appears:
When it does, click immediately on the column header. The column width adapts itself
to the broadest entry in this column.
● Showing / hiding columns
You call this function using the shortcut menu that opens when you click on a column
header with the right mouse key.
● Copying, pasting, cutting and deleting objects
If you click in a parameter box of an object in the table with the right mouse key, you can
use the functions named with the shortcut menu (copy, paste, cut, delete).
You can paste cut or copied objects within the table or in the first free row below the
table.
To simplify the engineering of larger plants, you can export the data points of a configured
module and import them into other modules in the project. This is an advantage particularly
in projects with many identical or similar stations or data point modules.
The export / import function is available when you select the module for example in the
network or device view and select the relevant shortcut menu.
Figure 4-4 Shortcut menu of the module
When it is exported the data point information of a module is written to a CSV file.
When you call the export function, the export dialog opens. Here, you select the module or
modules of the project whose data point information needs to be exported. When necessary,
you can export the data points of all modules of the project at one time.
In the export dialog, you can select the storage location in the file directory. When you export
the data of a module you can also change the preset file name.
When you export from several modules, the files are formed with preset names made up of
the station name and module name.
The file itself contains the following information in addition to the data point information:
● Module name
● Module type
● CPU name
● CPU type
You can edit the data point information in an exported CSV file. This allows you to use this
file as a configuration template for many other stations.
If you have a project with many stations of the same type, you can copy the CSV file with the
data points of a fully configured module for other as yet unconfigured stations and adapt
individual parameters to the particular station. This saves you having to configure the data
points for every module in STEP 7. Instead, you simply import the copied and adapted CSV
file to the other modules of the same type. When you import this file into another module, the
changed parameter values of the CSV file are adopted in the data point configuration of this
module.
The lines of the CSV file have the following content:
● Line 1: ,Name,Type,
This line must not be changed.
● Line 2: PLC,<CPU name>, <CPU type>,
Meaning: PLC (designation of the station class), CPU name, CPU type
Only the elements <CPU name> and <CPU type> may be changed.
The CPU type must correspond exactly to the name of the CPU in the catalog.
● Line 3: Module,<module name>, <module type>,
Meaning: Module (Designation of the module class), module type, module name
Only the elements <module name> and <module type> may be changed.
Be careful when changing the module names if you want to import data points into
several modules (see below).
The module type must correspond exactly to the name of the module in the catalog.
● Line 4: Parameter names (English) of the data points
This line must not be changed.
● Lines 5..n: Values of the parameters according to line 4 of the individual data points
You can change the parameter values for the particular station.
Before importing the data points make sure that the PLC tags required for the data points
have been created.
Note that when you import a CSV file all the data points existing on the module will be
deleted and replaced by the imported data points.
Select a module and select the import function from the shortcut menu of the module. The
import dialog opens in which you select the required CSV file in the file directory.
If the information on the assignment of the individual data points to the relevant PLC tags
matches the assignment in the original module, the data points will be assigned to the
corresponding PLC tags.
When you import data points into a module, but some required PLC tags have not yet been
created in the CPU, the corresponding data point information cannot be assigned. In this
case, you can subsequently create missing PLC tags and them assign them the imported
data point information. The "Assignment repair" function is available for this (see below).
If the names of the PLC tags in the module into which the import is made have different
names than in the module that exported, the corresponding data points cannot be assigned
to your PLC tags.
You can import the data points from several modules into the modules of a different project.
To do this in the import dialog select all the required CSV files with the control key.
Before importing the data points, make sure that the respective stations have been created
with CPUs of the same name, modules of the same name and PLC tags of the same name.
When you import the corresponding stations of the project are searched for based on the
module names in the CSV files. If a target station does not exist in the project or the module
has a different name, the import of the particular CSV file will be ignored.
In the following situations the import of data points will be aborted:
● An attribute required by the module is missing in the CSV file to be imported.
Example: If a data point to be imported uses a time trigger, the import will be aborted if no
time-of-day synchronization was configured for the module.
● The telecontrol protocol used by the module differs from that of the original module.
Only when importing into several modules:
● The import is aborted when a module or CPU name is different from the data in the CSV
CP 1243-1, CP 1243-8 IRC, TIM modules capable of DNP3
● IEC
CP 1243-1, CP 1243-8 IRC
Data points can be imported and exported between compatible modules.
If you have named the PLC tags in a station into which you want to import differently from
the station from which the CSV file was exported, the assignment between data point and
PLC tag is lost when you import.
You then have the option to either rename the existing PLC tags appropriately or add
missing PLC tags. You can then repair the assignment between unassigned data points and
PLC tags. This function is available either via the shortcut menu of the module (see above)
or with the following icon to the upper left in the data point editor:
If a PLC tag with a matching name is found for a data point by the repair function, the
assignment is restored. However the data type of the tag is not checked.
After the assignment repair make sure that you check whether the newly assigned PLC tags
are correct.
When you create a data point, a preset name "DataPoint_n" is adopted. In the data point
table and in the "General" tab of the data point you can change the name of the data point.
When assigning names only ASCII characters from the band 0x20 ... 0x7e (no. 32-126) may
be used with the exceptions listed below.
Forbidden characters:
● . ' [ ] / \ |
period, apostrophe, square brackets, slash, back slash, vertical line (pipe)
Note
Effect of the change of arrays for data points
If an array is modified later,
Data point types of the "TeleControl Basic" protocol
Format (memory requirements)
Data point type
Direction
S7 data types
Operand area
Bit
Digital input
in
Bool
I, Q, M, DB
Digital output
in
Bool
Q, M, DB
Byte
Digital input
in
Byte, Char, USInt
I, Q, M, DB
Digital output
out
Byte, Char, USInt
Q, M, DB
Integer with sign (16 bits)
Analog input
in
Int
I, Q, M, DB
Analog output
out
Int
Q, M, DB
Counter (16 bits)
Counter input
in
Word, UInt
I, Q, M, DB
Integer with sign (32 bits)
Analog input
in
DInt
Q, M, DB
Analog output
out
DInt
Q, M, DB
Counter (32 bits)
Counter input
in
UDInt, DWord
I, Q, M, DB
Floating-point number with sign (32
bits)
Analog input
in
Real
Q, M, DB
Analog output
out
Real
Q, M, DB
Floating-point number with sign (64
bits)
Analog input
out
LReal
Q, M, DB
Data block (1 .. 64 bytes)
Data
in / out
ARRAY 1)
DB
1)
For the possible formats of the ARRAY data type, refer to the following section.
Block of data (ARRAY)
4.10 Data points
Configure the user data to be transferred from the CPU that is referenced via PLC tags of
the CPU on the CP as data points.
The data point types supported by the CP along with the compatible S7 data types are listed
below for the various telecontrol protocols.
The direction relates to the direction of transfer:
● "in": Monitoring direction:
● "out": Control direction
the data point must be recreated.
Table 4- 1 Supported data point types and compatible S7 data types
Analog output out LReal Q, M, DB
Data in / out ARRAY 1) DB
With the ARRAY data type, contiguous memory areas up to a size of 64 bytes can be
transferred. The following S7 data types are compatible components of ARRAY:
● Byte, USInt (total of up to 64 per data block)
● Char (total of up to 64 per data block) - CP as of firmware version 2.1.77
Substitute object groups (of the table footnotes 1), 2), 3), 4))
4.10 Data points
5)
This object group can be configured in the Data point editor of STEP 7 using the substitute object group 12.
This object group can be configured in the Data point editor of STEP 7 using the substitute object group 20.
This object group can be configured in the Data point editor of STEP 7 using the substitute object group 22.
This object group can be configured in the Data point editor of STEP 7 using the substitute object group 41.
With these data point types, contiguous memory areas up to a size of 64 bytes can be transferred. All S7 data types with
Analog Input Event
Analog Output Sta-
Analog Output
Analog Output
Analog Output
Octet String / Oc-
[5, 7] in Real Q, M, DB
[3] out Real Q, M, DB
[3] out Real Q, M, DB
[5, 7] out Real Q, M, DB
[6, 8] out LReal Q, M, DB
[ - ] in, out
5)
DB
The initial data point types of the following object groups can be configured using the
substitute object groups listed above:
● 10 [2]
● 11 [1, 2]
● 21 [1, 2, 5, 6]
● 23 [1, 2, 5, 6]
● 40 [1, 2, 3]
● 42 [1, 2, 4, 5, 6, 7, 8]
To configure the DNP3 CP, use the specified substitute object group.
Assign each data point on the master using the configurable data point index in STEP 7. The
data point of the DNP3 CP is then assigned to the corresponding data point on the master.
Example of configuring the data point Binary Output (10 [2])
The data point is configured as follows:
On the DNP3 CP as Binary Command (12 [1])
On the master as Binary Output (10 [2])
With the data point types Binary Output Event (11) and Analog Output Event (42), you also
need to enable mirroring; refer to the next section.
91
Page 92
Configuration
Configuration of the mirroring back for output events (object groups 11 and 42)
Format of the time stamp
Data point types of the "IEC" protocol
Format (memory
requirements)
Data point type
IEC type
Direction
S7 data types
Operand area
Bit
Single-point information
<1>
in
Bool
I, Q, M, DB
CP56Time2a 1)
Single command
<45>
out
Bool
Q, M, DB
CP56Time2a 1)
CP56Time2a 1)
Byte
Step position information
<5>
in
Byte, USInt
I, Q, M, DB
tag CP56Time2a 1)
tag CP56Time2a 1)
Integer (16 bits)
Measured value, normalized value
<9>
in
Int
I, Q, M, DB
with time tag CP56Time2a 1)
Measured value, scaled value
<11>
in
Int
I, Q, M, DB
time tag CP56Time2a 1)
value
Set point command, scaled value
<49>
out
Int
Q, M, DB
value with time tag CP56Time2a 1)
with time tag CP56Time2a 1)
4.10 Data points
You first create the data point types Binary Output Event (object group 11) and Analog
Output Event (object group 42) as described above as data points of the object groups 12 or
41.
The local values of these two object groups can be monitored for change and the changes
transferred to the master (). Changing a local value can, for example, be caused by manual
operator input on site.
To allow the value resulting from local events or interventions to be transferred to the master,
the data point in question requires a channel for mirroring back. You configure this mirroring
back function is configured using the "Value monitoring" option in data point configuration,
General tab.
Remember that to use the mirror back function, you need to interconnect the local values in
the controller with the relevant PLC tag of the data point.
Time stamps are transferred in UTC format (48 bits) and contain milliseconds.
Table 4- 3 Supported data point types, IEC types and compatible S7 data types
For the format of the time stamp, see the following section.
For these data point types, create a data block with an array of precisely 2 bool.
With these data point types, contiguous memory areas up to a size of 32 bits can be transferred. Only the S7 Bool data
Time stamps are transferred according to the IEC specification in the "CP56Time2a" format.
Note that in the frames only the first 3 bytes for milliseconds and minutes are transferred.
93
Page 94
Configuration
4.10.4
Configuration of the data point index
Configuration of the data point index
Data point index with the TeleControl Basic protocol
Note
Index for data points with inter-station communication
Note that for inter
two corresponding data points (data point pair) must be identical on the sending and
receiving CP.
For information on the configuration, refer to the section
TeleControl Basic data points.
Data point index with the DNP3 protocol
Data point index with the IEC protocol
4.10 Data points
Below you will find the rules for configuring the data point index.
Within a CP, the indexes of the data point classes must comply with the following rules:
● Input
The index of an input data point must be unique throughout all data point types (digital
inputs, analog inputs etc.).
● Output
The index of an output data point must be unique throughout all data point types (digital
inputs, analog inputs etc.).
-station communication with a CP in another S7 station, the indexes of the
On a CP, data point indexes must be unique within each of the following object groups:
● Binary Input / Binary Input Event
● Binary Output / Binary Command
● Counter / Counter Event
● Analog Input / Analog Input Event
● Analog Output
● Octet String / Octet String Event
Indexes of two data points in different object groups can be identical.
The data point indexes must be unique in a CP.
Data point indexes assigned twice are indicated as errors in the consistency check and
prevent the project being saved.
Generation of events if a data point status changes
Status identifiers with the TeleControl Basic protocol
Bit
7 6 5 4 3 2 1
0
Flag name
EXISTENT
Meaning
undershot
Bit status
(always
0)
4.10 Data points
The status identifiers of the data points listed in the following tables are transferred along
with the value in each frame to the communications partner. They can be evaluated by the
communications partner.
The entries in the table row "Significance" relate to the entry in the table row "Bit status".
With data points that were configured as an event, the change to the status bit of the status
identifiers described below also leads to an event being generated.
Example: If the value of the status "RESTART" of a data point configured as an event
changes form 1 (value not yet updated) to 0 (value updated) when the station starts up, this
causes an event to be generated.
Depending on their status, the status bits (see table) are converted to the OPC quality code
by TCSB.
● Quality = BAD
Bit 2 or 7 = 1
● Quality = UNCERTAIN
Bit 1 or 3 or 5 = 1
● Quality = GOOD
Bits 1 and 2 and 3 and 5 and 6 = 0
Table 4- 4 Bit assignment of status byte 0
- NON_
- Data point
does not
exist or S7
address
unreachable
1 1 1 1 1 1 1
Substituted LOCAL_
Substitute
value
FORCED
Local operator control
CARRY OVER_
RANGE
Counted
value overflow before
reading the
value
Limit value
of the analog preprocessing
overshot /
The status IDs correspond to the following elements of the specification:
OBJECT FLAGS - DNP3 Specification, Volume 6, Data Object Library - Part 1
Table 4- 5 Bit assignment of the status byte
- - - LOCAL_
- - - Local opera-
The status IDs correspond to the following elements of the specification:
Quality descriptor - IEC 60870 Part 5-101
Table 4- 6 Bit assignment of the status byte
- - SB
- - Substitute
value
DISCONTI
Counted
tor control
1 1 1 1 1
value overflow before
reading the
value
- CY
- Counted
value overflow before
reading the
OVER_
Limit value of
the analog
preprocessing overshot /
OV
Value range
exceeded,
analog value
RESTART ONLINE
Value not yet
updated after
start
NT
Value not
updated
Value is valid
IV
Value is valid
1
1 1 1 0
The cyclic reading of the values of input data points from their assigned PLC tags on the
CPU can be prioritized.
Less important input data points do not need to be read in every CPU scan cycle. Important
input data points, on the other hand, can be prioritized for updating in every CPU scan cycle.
Process image, type of transmission, event classes, triggers
Saving the data point values
4.10 Data points
You can prioritize the data points in STEP 7 in the data point configuration in the "General"
tab with the "Read cycle" parameter. There you will find the two following options for input
data points:
● Fast cycle
● Normal cycle
The data points are read according to the method described below.
The cycle (including the pause) with which the CP scans the memory area of the CPU is
made up of the following phases:
●
The values of input data points with the scan priority "High-priority" are read in every scan
cycle.
●
Some of the values of input data points with the scan priority "Low-priority" are read in
every scan cycle.
The number of values read per cycle is specified for the CP in the "Communication with
the CPU" parameter group with the "Max. number of read jobs" parameter. The values
that exceed this value and can therefore not be read in one cycle are then read in the
next or one of the following cycles.
●
In every cycle, the values of a certain number of unsolicited write jobs are written to the
CPU. The number of values written per cycle is specified for the CP in the
"Communication with the CPU" parameter group with the "Max. number of write jobs"
parameter. The values whose number exceeds this value are then written in the next or
one of the following cycles.
●
This is the waiting time between two scan cycles. It is used to reserve adequate time for
other processes that access the CPU via the backplane bus of the station.
The values of data points are stored in the image memory of the CP and transferred only
when queried by the communications partner.
Events are also stored in the frame memory (send buffer) and can be transferred unsolicited.
Data points are configured as a static value or as an event using the "Type of transmission"
parameter (see below):
●
Static values are entered in the image memory (process image of the CP).
●
The values of data points configured as an event are also entered in the image memory
of the CP.
The values of events are also entered in the send buffer of the CP.
With DNP3, the value of the event is sent unsolicited to the communications partner if this
function is enabled by the master.
The image memory is the process image of the CP. All the current values of the configured
data points are stored in the image memory. New values of a data point overwrite the last
stored value in the image memory.
The values are sent after querying the communications partner, see "Transfer after call" in
the section "Types of transmission" below.
The send buffer of the CP is the memory for the individual values of data points that are
configured as an event. The maximum size of the send butter can be found in the section
Configuration limits and performance data (Page 15).
The configured number of events is divided equally among all configured and enabled
communications partners. For information on the configuration, refer to the parameter
"Frame memory size" in the section SNMP (Page 53).
If the connection to a communications partner is interrupted, the individual values of the
events are stored in the RAM of the CP. When the connection returns, the buffered values
are sent. The frame memory operates chronologically; in other words, the oldest frames are
sent first (FIFO principle).
If a frame was transferred to the communications partner, the transferred values are deleted
from the send buffer.
If frames cannot be transferred for a longer period of time and the send buffer is threatening
to overflow, the response is as follows:
If the send buffer reaches a fill level of 80%, the CP changes to the forced image mode. New
values of events are no longer added to the send buffer but rather they overwrite older
existing values in the image memory.
When the connection to the communications partner returns, the CP changes back to the
send buffer mode as soon as the fill level of the send buffer has fallen below 50%.
The current value of the data point is entered in the image memory of the CP. New
values of a data point overwrite the last stored value in the image memory.
After being called by the communications partner, the current value at the time is
transferred.
●
The values of data points configured as an event are entered in the image memory and
also in the send buffer of the CP.
The values of events are saved in the following situations:
– The configured trigger conditions are fulfilled (data point configuration > "Trigger" tab,
see below)
– The value of a status bit of the status identifiers of the data point changes see also the
section Status IDs of the data points (Page 95).
Example: When the value of a data point configured as an event is updated during
startup of the station by reading the CPU data for the first time, the status "RESTART"
of this data point changes (bit status change 1 → 0). This leads to generation of an
event.
When data points are configured as an event via the "Type of transmission" parameter,
the following event classes are available:
–
Each value change is entered in the send buffer in chronological order.
–
Only the last current value is entered in the send buffer. It overwrites the value stored
there previously.
Various trigger types are available for event-driven transfer:
●
The value of the data point is transferred when this reaches a certain threshold. The
threshold is calculated as the difference compared with the last stored value, refer to the
section Threshold value trigger (Page 101).
●
The value of the data point is transferred at configurable intervals or at a specific time of
day.
Resetting the trigger tag in the bit memory area / DB:
Transmission time of the frame (Transmission mode)
Spontaneous
Conditional spontaneous
4.10.8
"Trigger“ tab
Trigger
Saving the value of a data point configured as an event
Threshold value trigger
Time trigger
Event trigger (Trigger tag)
4.10 Data points
●
The value of the data point is transferred when a configurable trigger signal is fired. As
the trigger signal, the edge change (0 → 1) of a trigger bit is evaluated that is set by the
user program. When necessary, a separate trigger bit can be configured for each data
point.
If the memory area of the trigger tag is in the bit memory or in a data block, the trigger tag
is reset to zero when the data point value is transferred.
Whether the value of a data point is transferred to the communications partner immediately
after the trigger fires or after a delay depends on the setting of the parameter "Transmission
mode" in the "Trigger" tab of the data point:
●
The value is transferred immediately.
●
The value is transferred only when one of the two following conditions is fulfilled:
– The telecontrol server queries the station.
– The value of another event with the transmission mode "Unsolicited" is transferred.
Data points are configured as a static value or as an event using the "Type of transmission"
parameter:
Saving the value of a data point configured as an event in the send buffer (message
memory) can be triggered by various trigger types:
●
The value of the data point is saved when this reaches a certain threshold. The threshold
is calculated as the difference compared with the last stored value, refer to the section
Threshold value trigger (Page 101).
●
The value of the data point is saved at configurable intervals or at a specific time of day.
●
The value of the data point is saved when a configurable trigger signal is fired. For the
trigger signal, the edge change (0 → 1) of a trigger tag is evaluated that is set by the user
program. When necessary, a separate trigger tag can be configured for each data point.