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
02/2015 Subject to change
Page 3
Preface
Validity of this manual
TCSB:
This document contains information on the following product:
● CP1243-7 LTE-EU
Article number 6GK7 243-7KX30-0XE0
Hardware product version 1
Firmware version V2.1
The device is the communications processor for connecting the SIMATIC S7-1200 via
LTE, UMTS or GSM mobile wireless networks.
Behind the top hinged cover of the module housing, next to the article number you will see
the hardware product version printed as a placeholder "X" (for example X 2 3 4). In this case,
"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 IMEI under the lower hinged cover of the housing.
Unless explicitly stated differently in the text, the way in which telecontrol communication
works relates to a telecontrol server with the application "TeleControl Server Basic V3".
3
Page 4
Preface
Abbreviations/acronyms
TCSB
Mobile wireless network
Purpose of the manual
New in this issue
Replaced manual issue
Current manual release on the Internet
Required experience
● CP
Simplified designation of the product CP 1243-7 LTE-EU
●
TeleControl Server Basic V3, OPC server for telecontrol communication
●
The mobile wireless network(s) that support or use the relevant CP.
The precise standards and frequency bands which the two CPs support can be found in
the sections Connecting the S7-1200 to a mobile wireless network (Page 11) and
Technical specifications (Page 113).
This manual describes the properties of these modules and supports you when installing and
commissioning the device.
The necessary configuration steps are described in the form of an overview.
You will also find instructions for operation and information about the diagnostics options of
the device.
First issue
None
You will also find the current version of this manual on the Internet pages of Siemens
Industry Online Support under the following entry ID:
You will find license conditions in the following documents on the supplied data medium:
● DOC_OSS-S7CMCP_74.pdf
● DOC_OSS-CP124x-7_76.pdf
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, solutions, machines, equipment and/or networks. They are
important components in a holistic industrial security concept. With this in mind, Siemens’
products and solutions undergo continuous development. Siemens recommends strongly
that you regularly check for product updates.
For the secure operation of Siemens products and solutions, it is necessary to take suitable
preventive action (e.g. cell protection concept) and integrate each component into a holistic,
state-of-the-art industrial security concept. Third-party products that may be in use should
also be considered. For more information about industrial security, visit
http://www.siemens.com/industrialsecurity.
To stay informed about product updates as they occur, sign up for a product-specific
newsletter. For more information, visit http://support.automation.siemens.com.
The firmware is signed and encrypted. This ensures that only firmware created by Siemens
can be downloaded to the device.
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.
The following and possibly other names not identified by the registered trademark sign ® are
registered trademarks of Siemens AG:
A Dimension drawings ............................................................................................................................ 117
B Approvals ............................................................................................................................................ 119
C Accessories ........................................................................................................................................ 125
D Documentation references .................................................................................................................. 129
Connecting the S7-1200 to a mobile wireless network
Type of communication, mobile wireless standards, frequency bands
CP 1243-7 LTE-EU
Changing the mobile wireless standard if the network is not available
National approvals
The CP is intended for use in industrial environments.
Using the CP, the S7-1200 SIMATIC controller can be connected to mobile wireless
networks of the following standards:
●
The CP supports the following mobile wireless standards:
– LTE 800 (B20) / 1800 (B3) / 2600 (B7)
– UMTS 900 (B8) / 2100 (B1)
You will also find the supported frequency bands in the section General technical
specifications (Page 113).
If the establishment of a connection via a mobile wireless network with the LTE standard
fails, the CP attempts to dial in to an available network with the next lower mobile wireless
standard. Fallback response of the CP 1243-7 LTE-EU: LTE → UMTS → GSM.
This is only possible if the corresponding mobile wireless standard is enabled in the
configuration of the CP.
The CP allows the following types of WAN communication:
● Communication from remote stations to the telecontrol server (TCSB) in the master
● Inter-station communication
● Direct communication
– GSM 850 / 900, DCS 1800, PCS 1900
station (telecontrol communication)
Communication between stations and the master station (telecontrol communication)
Direct communication between stations (Open User Communication)
In countries in which the CP is approved, you will find this on the Internet on the pages of
Siemens Industry Online Support under the following entry ID:
102255422 (http://support.automation.siemens.com/WW/view/en/102255422)
On the Internet page, select the "Entry list" tab and the "Certificates" entry type.
Refer also to the appendix "Approvals (Page 119)" of the manual.
IP-based WAN communication via mobile wireless networks
Note:
1.1 Connecting the S7-1200 to a mobile wireless network
The CP allows WAN communication from remote stations with a master station,
communication between stations via a master station (inter-station communication) and
direct communication between stations.
The CP supports the following services for communication via the mobile wireless network or
via the mobile wireless network and the Internet:
● Data services
Transfer of process data via mobile wireless networks with the following standards:
– GPRS (General Packet Radio Service) / EDGE
The packet-oriented services for data transmission GPRS/EDGE are handled via the
GSM network.
The CP is not suitable for GSM networks in which the code multiplex method
Direct communication via Open User Communication (OUC)
1.2 Communications services
The CP is intended for use in an industrial environment. The following applications are
supported by the CP:
The following applications are possible if telecontrol communication is enabled in the
configuration of the CP.
● Communication with a control center
Remote S7-1200 stations communicate via the mobile wireless network and the Internet
with a telecontrol server in the master station. The telecontrol server communicates with a
higher-level control system using the integrated OPC server function.
● Event-driven sending of messages using SMS or e-mail
Via the mobile wireless network, the CP sends SMS messages to mobile phones or emails to PCs with an Internet connection.
Both types of messages are configured in telecontrol communication in STEP 7. The use
of program blocks is not necessary.
For information on the configuration, refer to sections E-mail configuration (Page 75) and
Messages (Page 86).
● Inter-station communication between S7-1200 stations via the telecontrol server
In this application, the CP establishes a connection to the telecontrol server via the
mobile wireless network. The telecontrol server forwards the messages to the destination
station.
For this communications service, the CP and TCSB use their own protocol on OSI layer 7
that among other things supports certain security functions, see section Other services and
properties (Page 14).
The program blocks of Open User Communication provide the CP with the following
communication options:
● Communication between S7-1200 stations via the mobile wireless network
For this, the CP must be assigned a fixed IP address, see section Other services and
properties (Page 14).
● SMS and e-mail messages via the mobile wireless network
– Sending and receiving SMS messages on mobile phones or S7 stations
– Sending e-mails to PCs with an Internet connection
In contrast to the two corresponding services of telecontrol communication (see above),
to transfer SMS messages/e-mails via OUC, program blocks need to be used, see
section Program blocks for OUC (Page 91).
You will find examples of applications in the section Configuration examples (Page 21).
Reading / writing data from / to a CPU via the mobile wireless network is possible if S7
communication is enabled in the configuration of the CP.
The following instructions are supported:
● PUT / GET
You will find details on the program blocks in the information system of STEP 7
For S7 communication, the CP requires a fixed IP address, see section Other services and
properties (Page 14).
TeleService is possible if the online functions are enabled in the configuration of the CP.
A TeleService connection can be established between an engineering station (PC with
STEP 7) and a remote S7-1200 station via the mobile wireless network and the Internet.
You can use the TeleService connection for the following purposes:
● Downloading project or program data from the STEP 7 project to the station
● Querying diagnostics data on the station
You will find application examples of the structure in the section Configuration examples
(Page 21).
For more detailed information, refer to section Calling a TeleService connection (Page 55).
●
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.
●
The CP is assigned a dynamic or a fixed IP address by the mobile wireless network
provider:
– Dynamic IP address
When using telecontrol communication, the mobile wireless network provider generally
assigns the CP a dynamic IP address. You set this in STEP 7 in the parameter group
"Ethernet interface > Ethernet addresses".
– Fixed IP address
To use S7 communication or to receive data via Open User Communication, the CPU
must be reachable via a fixed IP address. In this case, enter the fixed IP address
assigned by the mobile wireless network provider in the same parameter group.
Note
Plants with security requirements - recommendation
Use the following option:
•
•
Industrial Ethernet Security - Security functions of the CP
1.3 Other services and properties
The CP supports the following Security functions:
●
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 > Transfer
settings".
●
To authorize nodes allowed to establish a connection to the CP during telecontrol
communication.
●
To authenticate the CP with the telecontrol server
●
For the secure transfer of e-mails
●
For secure transfer during time-of-day synchronization (with telecontrol communication
disabled)
●
For secure access to the Web server of the CPU
If you have systems with high security requirements, use the secure protocols
NTP (secure) and HTTPS.
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.
The following Security functions can be used independently of telecontrol communication.
With Industrial Ethernet Security, individual devices, automation cells or network segments
of an IP-based network can be protected. The data transfer via the CP can be protected from
the following attacks by a combination of different security measures:
Number of simultaneous connections for telecontrol communication
Number of possible partners for inter-station communication
1.4 Performance data and configuration limits
Secure underlying networks can be operated via additional Ethernet/PROFINET interfaces of
the CPU.
As a result of using the CP, as a Security module, the following additional 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 a secure IPsec tunnel for
communication with a Security module.
The CP can be put together with other modules to form VPN groups during configuration.
IPsec tunnels 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 information on configuring the Security functions, refer to the section Security functions
(Page 58).
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 /5/ (Page 130).
● 1 reserved connection for user data exchange with the telecontrol server
● Max. 13 CPs as partners for inter-station communication
Of which:
– Max. 3 sending partners
– Max. 10 receiving partners
● Partners can be S7-1200 mobile wireless CPs with a data point configuration.
Number of simultaneous connections for S7 communication and Open User Communication
Number of connections to NTP servers
User data
Number of PLC tags for data point configuration
Frame memory (send buffer)
1.4 Performance data and configuration limits
● Max. 1 TeleService connection
A maximum total of 14 connection resources for S7 communication and Open User
Communication
The maximum number can be divided up as required into:
● S7 connections (PUT/GET)
● TCP connections
● ISO-on-TCP connections
● UDP connections
● Max. 1 connection to an NTP server
With the connection types listed below, the user data of a frame represent a consistent data
area in terms of the time of transfer.
User data per frame with the various connection types:
● For TCP connections: Max. 8192 bytes
● For ISO-on-TCP connections: Max. 1452 bytes
● For UDP connections: Max. 1472 bytes
With frames of telecontrol communication, the individual values of the data points are time
stamped.
The maximum number of PLC tags that can be used for data point configuration is 100.
The CP has a frame memory (send buffer) for data points configured as an event.
The send buffer has a maximum size of 64 000 events divided into equal parts for all
configured communications partners. The size of the frame memory can be set in STEP 7.
See also section Process image, type of transmission, event classes, triggers (Page 51).
Up to 10 messages can be configured in STEP 7 and sent as e-mails or SMS messages.
Maximum number of characters that can be transferred per SMS message: 160 ASCII
characters including any value sent at the same time
Maximum number of characters that can be transferred per e-mail: 256 ASCII characters
including any value sent at the same time
An IPsec tunnel can be established for secure communication with another Security module.
The maximum number of firewall rules in advanced firewall mode is limited to 256.
The firewall rules are divided up as follows:
● Maximum 226 rules with individual addresses
● Maximum 30 rules with address ranges or network addresses
(e.g. 140.90.120.1 - 140.90.120.20 or 140.90.120.0/16)
● Maximum 128 rules with limitation of the transmission speed ("Bandwidth limitation")
Apart from the CP in the remote S7-1200, the following hardware is also required:
● A CPU with firmware version as of V4.1
● An external antenna for the CP
Use only antennas from the accessories program for the CP, refer to the appendix
Antenna (Page 125).
● For telecontrol communication, a PC with an Internet connection is required for the
telecontrol server in the master station.
● If you intend to use TeleService via mobile wireless, a TeleService gateway with Internet
access is required for configurations without a telecontrol server. This is a PC on which
the "TS Gateway" software is installed, see appendix TS Gateway (Page 125).
Program blocks for Open User Communication and S7 communication
Software for telecontrol communication and TeleService
Requirements for using mobile wireless services
1.5 Requirements for operation
To configure the module, the following configuration tool is required:
STEP 7 Basic V13 + SP1
For Open User Communication and S7 communication, program blocks are required, see
section Communications services (Page 13).
The CP is configured in "Telecontrol" mode.
● For the telecontrol communication
The telecontrol server requires the "TCSB" software in the master station.
● For TeleService
For TeleService a switching station is required between the CP and the engineering
station (with STEP 7 in the version specified above).
This is either the telecontrol server or a TeleService gateway:
– When using telecontrol communication, the telecontrol server is the switching station.
– To use TeleService without a telecontrol server, the "TS Gateway" software is required
for the TeleService gateway.
The software and the manual describing it are on the DVD that ships with the CP.
For the documentation of the application, see /4/ (Page 130) or /3/ (Page 130) in the
References.
● A contract with a suitable mobile wireless network provider
The contract must allow the transfer of data.
IP address:
– For communication with the telecontrol server, a private (fixed) or public (dynamic) IP
address assigned by the mobile wireless network provider can be used.
– For direct communication between S7 stations (S7 communication and Open User
Communication via T blocks) the mobile wireless network provider must assign a fixed
IP address to the CP and forward the frames to the destination nodes.
● The SIM card and PIN belonging to the mobile wireless contract
The SIM card is inserted in the CP.
With mobile wireless contracts in which the network provider does not assign a PIN, no
PIN is necessary for the configuration of the CP.
● Local availability of a mobile wireless network in the range of the station.
Below, you will find configuration examples for stations with a CP 1243-7 LTE.
Figure 1-1 Sending messages by SMS from an S7-1200 station
The CP can send SMS messages to a mobile phone or a configured S7-1200 station and
receive from these nodes. The mechanisms for this are as follows:
● SMS messages generated and sent as the result of an event.
For a description of the configuration, refer to the sections Configuring data points and
messages (Page 47) and Messages (Page 86).
● SMS messages that are sent or received due to calling the corresponding program blocks
of Open User Communication.
You will find information on the blocks in the section Program blocks for OUC (Page 91),
you will find the description of the programming in the STEP 7 information system.
● Using a mobile phone, a diagnostics SMS can be requested, see section Diagnostics
options (Page 105).
For all mobile phones that send SMS messages to the CP, the authorize phone number
must be specified in the STEP 7 configuration of the CP (parameter group "Security >
Authorized phone number").
The CP can send e-mails to a PC with an Internet connection or a mobile phone. The
mechanisms for this are as follows:
● E-mails generated and sent as the result of an event.
For a description of the configuration, refer to the sections Configuring data points and
messages (Page 47), Messages (Page 86) and E-mail configuration (Page 75).
● E-mails sent as a result of calling the program block TMAIL_C.
You will find information on the blocks in the section Program blocks for OUC (Page 91),
you will find the description of the programming in the STEP 7 information system.
Figure 1-2 Communication between S7-1200 stations and a control center
In the telecontrol applications, the CP communicates with a telecontrol server with an
Internet connection via the mobile wireless network. The "TeleControl Server Basic V3"
(TCSB) application is installed on the telecontrol server in the master station. This results in
the following use cases:
● Communication between a station and a control room with OPC client
The station communicates with the telecontrol server. Using its integrated OPC server,
the telecontrol server exchanges data with the OPC client of the control room.
The OPC client and telecontrol server can be located on a single computer, for example
when TCSB is installed on a control center computer with WinCC.
● Inter-station communication via a control center
Inter-station communication is possible with S7 stations equipped with a suitable
telecontrol CP: CP 1243-1, CP 1242-7 GPRS V2, CP 1243-7 LTE
To allow inter-station communication, the telecontrol server forwards the messages of the
sending station to the receiving station.
Figure 1-3 Direct communication between two S7-1200 stations
In this configuration, two SIMATIC S7-1200 stations communicate directly with each other
using the CP via the mobile wireless network. Each CP has a fixed IP address. The relevant
service of the network provider must allow this.
In TeleService via the mobile wireless network, an engineering station on which STEP 7 is
installed communicates via the mobile wireless network and the Internet with the CP in the
S7-1200.
Since the firewall of the network provider is normally closed for connection requests from the
outside, a switching station between the remote station and the engineering station is
required. This switching station can be a telecontrol server or, if there is no telecontrol server
in the configuration, a TeleService gateway.
Location of the display elements and the electrical connectors
Opening the housing
The LEDs for the detailed display of the module statuses are located behind the upper cover
of the module housing.
The socket for the power supply is located on the top of the module.
The connector for the external antenna is located on the bottom of the module.
The compartment for inserting the SIM card is located behind the upper hinged cover of the
module.
Open the upper or lower cover of the housing by pulling it down or up as shown in the
illustration. The covers extend beyond the housing to give you a grip.
Wireless interface for the mobile wireless network
More detailed information on the electrical connections
2.3 Electrical connectors
An extra antenna is required for communication in the mobile wireless network. This is
connected via the SMA socket of the CP. The SMA socket is located behind the lower front
cover of the CP.
You will find a suitable antenna for indoor and outdoor use in the section Accessories
(Page 125).
For technical information on the electrical connections, refer to the section Technical
specifications (Page 113).
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.
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.
General notices on use in hazardous areas according to ATEX
WARNING
Requirements for the cabinet/enclosure
WARNING
WARNING
3.1.3
Notices regarding use in hazardous areas according to UL HazLoc
WARNING
EXPLOSION HAZARD
3.1 Important notes on using the device
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.
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.
Read the system manual "S7-1200 Programmable Controller"
Configuration
Inserting the SIM card
Note
Inserting and removing the SIM card
Do not insert or r
3.2 Installing the CP 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".
One requirement for the commissioning of the CP is the completeness of the STEP 7 project
data (see below). You should also read the section "Configuration and operation (Page 41)".
* Width B: The distance between the edge of the housing and the center of the hole in the DIN rail mounting clip
DIN rail mounting clips
3.2 Installing the CP and commissioning
Figure 3-1 Dimensions for installation of the S7-1200
Table 3- 1 Dimensions for installation (mm)
CPU
(Examples)
Signal modules
(Examples)
Communications interfaces
(Examples)
8 or 16 digital I/Os
2, 4 or 8 analog I/Os
Thermocouple, 4 or 8 I/Os
16 analog I/Os
CM 1243-5 (PROFIBUS master)
All CPUs, SMs, CMs and CPs can be installed on the 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.
Note
Power supply from the power outputs of the CPU
The external power supply of the CP must be supplied via the power outputs of the CPU.
Keep within the maximum load of the power outputs of the CPU.
You will find data relating to the current consumption and power loss of the CP in the section
General technical specifications
3.2 Installing the CP and commissioning
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 General technical
specifications (Page 113).
Note
Turning off the station when plugging/pulling the CP
Do not only turn off the power supply to the CP. Always turn off the power supply for the
entire station.
Step
Execution
Notes and explanations
1
The slots to the left of the CPU are permitted.
2
Secure the DIN rail.
3
output of the CPU.
4
in the socket on the top of the CP.
socket for the external power supply (Page 116).
5
CP.
Notice
6
Turn on the power supply.
7
them closed during operation.
8
3.2 Installing the CP and commissioning
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.
Secure the power supply wires to the power
Secure the wires of the power supply to the
plug supplied with the CP and insert the plug
Connect the antenna to the SMA socket of the
• Protect the antenna connector using suitable overvoltage protection equipment if the antenna cable is long-
er than 30 m.
• Protect the antenna connector with suitable lightning protection if you install the antenna outdoors.
• If you install several CPUs close to each other, keep to a minimum clearance of 50 cm between the anten-
nas.
Close the front covers of the module and keep
The remaining steps in commissioning involve
downloading the STEP 7 project data.
Use a 35 mm DIN rail.
The pinning is shown beside the socket on the top of the housing. You will also find this in the section Pin assignment of the
Lower surface of the CP
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 online help:
Configuring communication with the CPU (data point configuration)
The device may only be operated when the distance between the device (or antenna) and
user is at least 20 cm.
To ensure interference-free operation, keep the front panels of the module closed during
operation.
You configure the modules, networks and connections in an engineering station in SIMATIC
STEP 7. You will find the required version in the section Requirements for operation
(Page 19).
You can configure a maximum of three CMs/CPs per station. If you insert several CPs in an
S7-1200, you can, for example, establish redundant communications paths.
CP communication is not programmed using program blocks but configured using data
points.
One requirement for data point configuration is the programming of the assigned CPU and
the input and output data of the station. To assign the user data to be transferred
(input/output data) to the data points, you need to create PLC tags.
Note
Configured PIN and PIN on the SIM card must match.
If you enter the PIN of the SIM card of the CP incorrectly during STEP 7 configuration and
download the
by the CP only once so that the SIM card is not locked.
If you change the PIN of the SIM card externally to the incorrectly configured PIN (new PIN
of the SIM card = incorrectl
checking it.
Note
Solution after entering an incorrect PIN:
To avoid the PIN being rejected by the CP again, use a PIN that is different from the
incorrectly entered PIN. Procedure:
•
•
– Reload the station.
4.3 Information required for configuration
The following information is required for the STEP 7 configuration of the CP:
● Own phone number of the CP (required for TeleService)
● Authorized phone numbers
Phone numbers of the nodes that are allowed to send an SMS to the CP.
● APN
Name of the access point (APN) from the mobile wireless network to the Internet
(information from the mobile wireless network provider)
● APN user name
User name for the access point of the mobile wireless network provider
● APN password
Password for the access point of the mobile wireless network provider
● Node number of the SMS master station (SMSC) when using SMS
● PIN of the SIM card
station, the CP stores the wrong PIN. An incorrectly entered PIN is transferred
y entered PIN in STEP 7), the CP rejects this PIN again without
If the PIN of the SIM card was not changed:
– Configure the PIN in STEP 7 with the PIN of the SIM card.
– Reload the station.
If the original PIN of the SIM card was changed externally to the PIN that was previously
incorrectly entered in STEP 7:
– Change the PIN of the SIM card externally to a new PIN that has not yet been
incorrectly configured in STEP 7.
– Change the configured PIN in STEP 7 to the newly assigned PIN of the SIM card.
Information required for telecontrol communication
CP parameter for configuring the telecontrol server
4.3 Information required for configuration
The following information is required for the STEP 7 configuration of the CP:
● Address of the telecontrol server
– IP address
or
– Name of the telecontrol server that can be resolved by DNS
– IPT listener port (55097)
IPT listener port of the telecontrol server. Default setting: 55097
If only connections with TCSB are used (no direct communication), a dynamic IP address
can be assigned to the CP by the Internet service provider.
For addressing a redundant TCSB system, refer to the section Partner stations >
Telecontrol server (Page 70).
● DNS server address(es)
You require the DNS server address if you address the telecontrol server using a name
that can be resolved by DNS and the DNS is not operated by the network provider. You
configure DNS in the parameter group "DNS configuration":
– If you do not specify an address, the DNS server address is obtained automatically
from the network provider (recommended procedure).
– If you want to use a different DNS server, enter its IP address. In this case, DNS
servers of the network provider are not taken into account.
The following parameters from the STEP 7 configuration of the CP are also required for the
configuration of the telecontrol server:
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 the can be used for data point
configuration in the section
Access to the memory areas of the CPU
4.5 Configuring data points and messages
No program blocks need to be programmed for the CP to transfer user data between the
station and communications partner. The data areas in the memory of the CPU intended for
communication with the partner are configured data point-related on the CP. Each data point
is linked to a PLC tag or a data block on the CPU.
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.
The formats and S7 data types of the PLC tags that are compatible with the protocol-specific
data point types of the CP can be found in the section Datapoint types (Page 48).
The values of the PLC tags or DBs referenced by the data points are read and transferred to
the communications partner by the CP.
Data received from the communications partner is written by the CP to the CPU via the PLC
tags or DBs.
Performance data and configuration limits (Page 17).
Configuring the data points and messages in STEP 7
4.6
Datapoint types
4.6 Datapoint types
You configure the data points in STEP 7 in the editor for the data point and message
configuration. You can find this using the project tree:
Project > directory of the relevant station > Local modules > CP 1200
Figure 4-1 Configuring data points and messages
You will find more information on configuration in the following sections and in the STEP 7
information system.
During the configuration of the user data to be transferred by the CP, each data point is
assigned a protocol-specific data point type. The data point types supported by the CP along
with the compatible S7 data types are listed below. They are grouped according to format
(memory requirements).
The cyclic updating of the values of input data points of the CP by reading the current values
of the 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.
You can prioritize the data points in STEP 7 in the data point configuration in the "General"
tab with the "Priority in the scan cycle" parameter. There you will find the two following
options for input data points:
● High priority
● Low priority
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.
Since no fixed time can be configured for the cycle and since the individual phases cannot
be assigned a fixed number of objects, the duration of the scan cycle is variable and can
change dynamically.
Process image, type of transmission, event classes, triggers
The image memory, the process image of the CP
The send buffer (frame memory)
The forced image mode
4.8 Process image, type of transmission, event classes, triggers
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
Performance data and configuration limits (Page 17).
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 Communication with the CPU (Page 74).
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 if the fill level of the send buffer has
fallen below 50%.
Status identifiers: Generating an event on a status change
Type of transmission / event classes
Transfer after call
Every value triggered
Current value triggered
4.8 Process image, type of transmission, event classes, triggers
Data points are configured as a static value or as an event using the "Type of transmission"
parameter (see below):
●
The values of data points that are not configured as an event ("Transfer after call") are
entered in the image memory of the CP and transferred to the communications partner
when it requests this value.
●
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 changes.
With data points that are configured as an event, the change to the status bit leads to an
event being generated, refer also to the section Status IDs of data points (Page 54).
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.
The following types of transmission are available:
●
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.
The current value at the time is transferred only after being called by the communications
partner.
●
The data point is configured as an event.
Each value change is entered in the send buffer in chronological order.
●
The data point is configured as an event.
Only the last current value is entered in the send buffer. It overwrites the value stored
there previously.
Resetting the trigger tag in the bit memory area / DB:
Transmission mode
4.8 Process image, type of transmission, event classes, triggers
Various trigger types are available for starting 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 78).
●
The value of the data point is transferred at configurable intervals or at a specific time of
day.
●
The value of the data point is transferred 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.
You specify whether the value of a data point is transferred to the communications partner
immediately after the trigger fires or after a delay in the "Transmission mode" parameter.
The transmission mode of a frame is set in the "Trigger" tab of the data point. With the two
options, you specify whether frames of events are sent immediately or following a delay:
● Unsolicited
● Conditional spontaneous
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.
The value is transferred immediately.
The value is transferred only when one of the two following conditions is fulfilled:
– The communications partner queries the station.
– The value of another event with the transmission mode "Unsolicited" is transferred.
Note
Connection interrupted by the mobile wireless network provider
When using mobile wireless services, remember that existing connections can be
interrupted by mobile wireless network providers for maintenance purposes.
4.9 Status IDs of 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 status identifiers are transferred in 2 bytes. Byte 1 is not used.
The meaning relates to the bit status in the last row of each table.
Table 4- 2 Byte assignment of the status byte for data points
- NON_
- Data point
does not
exist or S7
address
unreacha-
● Connection to the telecontrol server
The connection to the telecontrol server is always established by the CP.
If a connection established by the CP is interrupted, the CP automatically attempts to reestablish the connection. Note the settings for re-establishing the connection in STEP 7,
refer to the section Ethernet interface (X1) (Page 67).
SB
Substituted
Substitute
value
LOCAL_
FORCED
Local operator control
CY
CARRY
Counted
value overflow before
reading the
value
OVER_
RANGE
Analog
value: Value range
exceeded
RESTART ONLINE
Value not
updated
after start
Value is
invalid
● Connections with direct communication (Open User Communication) and S7
communication
Connections are established as soon as the corresponding program blocks are called on
the CPU.
This also applies to the situation when a different S7 station sends data. In this case, the
corresponding receive blocks are called by the receiving station.
Requirement for the engineering station and the STEP 7 project
Requirement for connection establishment
4.11 Acknowledgment
The receipt of a frame is monitored and acknowledged in different ways. The mechanisms
differ depending on the type of communication:
●
Frames received from TCSB are acknowledged immediately by the CP.
Frames sent by the CP are acknowledged by TCSB.
●
Received frames are acknowledged immediately by the CP. The acknowledgment frame
is forwarded by the telecontrol server to the destination CP.
For sent frames, this applies in the opposite direction.
●
The successful sending and receipt of frames is indicated by status displays of the
program blocks.
With TCP segments, the protocol-specific acknowledgement mechanisms are used.
● The STEP 7 project with the CP is stored on the engineering station.
● The required configuration steps have been performed, see section Configuration of the
TeleService access (Page 45).
The request for connection establishment is triggered by the engineering station. The
connection is established by the CP.
With TeleService via the mobile wireless network, a switching station is required between the
remote station and engineering Station, see section Requirements for operation (Page 19).
This switching station can be a telecontrol server or, if there is no telecontrol server in the
configuration, a TeleService gateway.
For documentation of the two systems, refer to Documentation references (Page 129).
Settings for establishing a TeleService connection
Telecontrol server / TeleService gateway...
Authentication ...
Requirements in the security configuration of the CP
Procedure for connection establishment for TeleService
Note
No TeleService connection establishment using "Online" > "Go online"
If you attempt to establish a TeleService connection by selecting the CPU and then selecting
the menu or shortcut menu command "Online" > "Connect online", STEP 7 will automatically
attempt to connect via Ethernet. Reason: In STEP 7, the last connection path used to
download the project data is stored.
Note
TeleService to 1 station only from 1 TIA Portal instance
You can operate TeleService with an S7 station only from 1 engineering station (1 TIA Portal
instance; 1 STEP 7 project). TeleService by more than one engineering station at the same
time with 1 station is not possible.
4.12 Calling a TeleService connection
In the dialog "Establish mobile wireless remote connection", enter the previously configured
data under the following headings:
●
● Selection whether the TeleService switching station is located on the PC of the
engineering station or in the network or can be reached via the Internet.
– In the latter case, enter the address of the TeleService server.
IP address or name and port number of the telecontrol server that can be resolved by
DNS or of the TeleService gateway
– Server password
If the option is enabled and the server password is configured in TCSB, enter the
password to authenticate the CP with the telecontrol server.
The server password is not required for TeleService via a TeleService gateway.
●
– User name and password
– Here, enter the data for the TeleService user that you configured in STEP 7 in the
global Security settings, see also section Configuration of the TeleService access
(Page 45).
For the remote station, TeleService can only be used if the engineering station (with CP
1628 or via SCALANCE S) and the CP are configured in a common VPN group.
For TeleService, you need to enable the option "Allow S7 protocol" in the IP rules of the
firewall configuration.
Note
Canceling a TeleService connection when calling online dialogs
An existing TeleService
station or a node.
When there is an existing TeleService connection, do not select any of the menu commands
"Go online", "Online & Diagnostics", "Load to device", "Extended download to device"
"Accessible nodes".
Terminating a TeleService connection
User data connections and TeleService
4.12 Calling a TeleService connection
connection is canceled when you attempt to access an additional
or
Follow the steps below to establish a TeleService connection to the remote station via the
mobile wireless network from the engineering station:
1. Select the CPU of the remote station in the STEP 7 project.
2. Select the "Online" > "Online & Diagnostics" menu.
The "Online access" dialog opens.
3. Choose the entry "TeleService via mobile wireless" in the "Type of interface" drop-down
list.
4. Choose the entry "Mobile wireless TeleService board" in the "PG/PC interface" drop-
down list.
5. Click on the
icon next to the "PG/PC interface" drop-down list.
The "Establish remote connection" dialog box opens.
6. Make the necessary entries in this dialog.
You will find information on the necessary entries in the tooltips of the STEP 7 online
help.
On completion of the TeleService session, terminate the TeleService connection again using
the "Go offline" button. The connection is terminated after approximately 5 minutes.
Connections between a CP and telecontrol server for transferring user data are not
interrupted by a TeleService connection.
Note the range and application of the security functions of the CP, refer to the section Other
services and properties (Page 14).
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 telecontrol protocols of the application layer 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 in the subnet 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/PG to automation devices or networks protected by
security modules via public networks.
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.
4.13 Security functions
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:
● Data espionage
● Data manipulation
● Unwanted access
In normal mobile wireless networks it is not possible to reach a dynamic IP address assigned
to the CP by the mobile wireless network provider from the Internet. For this reason, for
incoming connections make sure that the CP is assigned a fixed public IP address by the
mobile wireless network provider.
You must also make sure that apart from this IP address, the ports required for VPN are
reachable from the Internet.
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.
● All receiving stations require a fixed IP address to be reachable via the public networks.
For this, a special mobile wireless contract is normally necessary for the mobile wireless
CP.
Creating the VPN group and assigning security modules
4.13 Security functions
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.
With all further logons, log on as user.
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.
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
The establishment of a VPN connection to an engineering station that is also the telecontrol
server at the same time (TCSB installed), runs as follows along with the time of da
synchronization of the CP:
On the engineering station (with TCSB), you want the CP to establish a VPN connection.
The VPN connection is established even if the CP does not yet have the current time.
Otherwise the certificates used are evaluated as valid
work.
Following connection establishment, the CP synchronizes its time of day with the PC
because the telecontrol server is the time master if telecontrol communication is enabled.
Configure the properties of the VPN group
Note
Specifying the VPN properties of the CPs
You specify the VPN properties of the CPs in the "Security" > "Firewall" > "VPN" parameter
group of the relevant module.
Result
4.13 Security functions
exchanged, the current date and the current time are required on both stations.
y
and the secure communication will
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 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.
VPN communication with SOFTNET Security Client (engineering station)
VPN tunnel communication works only if the internal node is disabled
4.13.1.5
Connection to the telecontrol server
No VPN connection between CP and TCSB
4.13 Security functions
Setting up VPN tunnel communication between the SOFTNET Security Client and CP has
essentially same requirements and procedure as described in the section Creating a VPN
tunnel for S7 communication between stations (Page 59).
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. Disable the option "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. Select "Delete Entry" in the shortcut menu.
Result: The lower-level node is now fully disabled. VPN tunnel communication to the CP can
be established.
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
possible because the telecontrol server cannot be configured in STEP 7.
Thanks to the encrypted telecontrol protocol, the connection between the CP and telecontrol
server is already protected.
Setting permission for VPN connection establishment with passive subscribers
4.13.2
Firewall
4.13.2.1
Firewall sequence when checking incoming and outgoing frames
4.13.2.2
Notation for the source IP address (advanced firewall mode)
4.13.2.3
Firewall settings for S7 connections via a VPN tunnel
IP rules in advanced firewall mode
4.13 Security functions
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)
Configure the permission for VPN connection establishment for the CP as a passive
subscriber as follows:
1. In STEP 7, go to the devices and network view.
2. Select the CP.
3. Open the "VPN" tab.
4. For each VPN connection with the CP as a passive VPN subscriber, change the default
setting "Initiator/Responder" to the setting "Responder".
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.
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 S7 connections with a VPN tunnel between the CP and a communications
partner, you will need to adapt the local firewall settings of the CP:
Select the "Allow*" action for S7 connections in advanced firewall mode ("Security > Firewall
> IP rules") for both communications directions of the VPN tunnel.
Communications problems if the value for system events is set too high
4.14
Time-of-day synchronization
Procedure for time-of-day synchronization
Time from partner
NTP / NTP (secure)
4.14 Time-of-day synchronization
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.
With applications that require time-of-day synchronization (e.g. telecontrol), you need to
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.
The CP supports the two methods of time-of-day synchronization:
●
The time of the CP is synchronized by a telecontrol server.
Only with communication type "Telecontrol" activated.
●
Only with communication type "Telecontrol" deactivated.
The method NTP (secure) can only be selected if the security functions are enabled.
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.
"Accept time from non-synchronized NTP servers" option
Time-of-day synchronization of the CPU
4.14 Time-of-day synchronization
Depending on the configured communication types and security functions, time-of-day
synchronization is configured differently:
● Telecontrol communication enabled
With telecontrol communication enabled, the time of day of the CP is synchronized
automatically by the TCSB computer.
– Security functions enabled:
The time-of-day synchronization is configured in the "Security" parameter group.
● Telecontrol communication not enabled
The time of day of the CP can only be synchronized with NTP mechanisms:
– Security functions enabled:
The time-of-day synchronization is configured in the "Security" parameter group. NTP
and NTP (secure) are available as the synchronization methods.
– Security functions not enabled:
The time-of-day synchronization is configured in the "Ethernet interface > Time
synchronization" parameter group. Only NTP is available as the synchronization
method.
For more information on configuration, refer to the STEP 7 online help of the "Time
synchronization" parameter group.
If you use Security functions, a valid time of day is extremely important. It is recommended to
use the NTP (secure) method.
The secure method NTP (secure) uses authentication with symmetrical keys according to
the hash algorithms MD5 or SHA-1.
You can create and manage additional NTP servers also of the type NTP (secure) in the
global Security settings of the STEP 7 project.
If the option is enabled, the CP also accepts the time-of-day from non-synchronized NTP
servers with stratum 16.
If the option is disabled, the response is as follows: If the CP receives a time of day frame
from an unsynchronized NTP server with stratum 16, the time of day is not set according to
the frame. In this case, none of the NTP servers is displayed as "NTP master" in the
diagnostics; but rather only as being "reachable".
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.
If there are discrepancies between the following descriptions and the information in STEP 7 /
Professional V13, the information in this document is valid.
4.15.1
Communication types
"Communication types" parameter group
Enable telecontrol communication
Activate online functions
Enabling S7 communication
4.15 STEP 7 configuration of individual parameters
Below, you will find information on the configuration of individual functions grouped
according to parameter groups in STEP 7.
In this parameter group, you enable the communication type of the CP.
To minimize the risk of unauthorized access to the station via mobile wireless, 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.
●
Enables communication with a Telecontrol server on the CP.
Note:
To enable telecontrol communication, the Security functions must also be enabled.
●
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 on the CP.
Open User Commmunication does not need to be enabled since you then need to create the
relevant program blocks. Unintended access to the CP is therefore not possible.
Ethernet interface (X1) > Ethernet addresses > IP protocol
Dynamic IP address
Fixed IP address from the mobile wireless network provider
4.15 STEP 7 configuration of individual parameters
In this parameter group, you configure the phone number of the CP, the PIN and the SMSC.
You continue to enable the required mobile wireless services. You can enable individual
mobile wireless services or all of them. If you do nit enable a mobile wireless service, the CP
behaves as if all mobile wireless services were enabled and the choice of the mobile
wireless service used is made based on the data on the SIM card.
In this parameter group, you configure the APN data.
In this parameter group, you specify the dial-in behavior of the CP into various mobile
wireless networks.
In this parameter group, you specify the connection parameters for the TeleService
server(s).
The CP does not have a physical Ethernet interface.
In STEP 7, the Ethernet interface is used as a placeholder for the configuration of various
address and monitoring parameters.
Enter you configure IP address of the CP.
●
Enable this option if the CP is assigned the IP address dynamically by the network
provider.
●
Enable this option if you have a mobile wireless contract with which the network provider
assigns the CP a fixed IP address.
This is necessary when using S7 communication and Open User Communication.
Ethernet interface(X1) > Advanced options > Transfer settings
Reconnection delay
4.15 STEP 7 configuration of individual parameters
The settings made here apply globally to all configured TCP connections of the CP. If
telecontrol communication is enabled, this is the connection to the telecontrol server.
Note the option of overwriting the general value configured here for individual
communications partners, refer to the section Partner stations (Page 70).
(Note: The settings made here do not apply to connections programmed for Open User
Communication with the program blocks.)
Function: If there is no data traffic within the connection monitoring time, the CP sends a
keepalive to the communications partner.
The monitoring time is configured for the Ethernet interface as the default for all TCP
connections. The default value can be adapted individually for each connection in "Partner
stations".
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.
The monitoring time is configured for the Ethernet interface as the default for all TCP
connections. The default value can be adapted individually for each connection in "Partner
stations".
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.
Range of values for the basic value: 10 to 600 s.
Example: The basic value 20 results in the following intervals (waiting times) between the
attempts to re-establish a connection:
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.
Dependi
Send timeout
Watchdog cycle
Watchdog monitoring time
Key exchange interval
4.15 STEP 7 configuration of individual parameters
ng on your contract, costs may result from each connection establishment attempt.
Time for the arrival of the acknowledgment from the 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 connection monitoring time
elapses, the frame is repeated up to three times. After three unsuccessful attempts, the
connection is terminated and re-established.
Interval at which a watchdog frame is sent to the telecontrol server if there is no productive
data exchange.
After sending a watchdog frame, an answer is expected from the Telecontrol server within
the watchdog monitoring time (timeout). If the CP does not receive a reply from the
Telecontrol server within the monitoring time, it terminates and re-establishes the
connection.
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.
Partner stations > "Telecontrol server > "Connection to partner"
Partner IP address
Connection monitoring
4.15 STEP 7 configuration of individual parameters
●
The partner number for the telecontrol server is assigned automatically by the system if
telecontrol communication is enabled.
●
The station address of the telecontrol server is assigned automatically by the system if
telecontrol communication is enabled.
●
IP address of the telecontrol server
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.
●
When the function is enabled, the connection to the communications partner (telecontrol
server) 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 > Telecontrol server", the globally set TCP
connection monitoring time can be set separately for the telecontrol server. The value set
here overwrites the global value for the telecontrol server that was set in the "Ethernet
interface (X1) > Advanced options > TCP connection monitoring" parameter group.
4.15 STEP 7 configuration of individual parameters
●
The monitoring time is specified at a higher level for the Ethernet interface as the default
for all configured TCP connections, see also section Ethernet interface (X1) (Page 67).
The default value for the Ethernet interface can be adapted for the connection to the
telecontrol server individually in the "Partner stations" parameter group. If the monitoring
time in the "Partner stations" parameter group has a different value from the monitoring
time in the Ethernet interface parameter group, the monitoring time of the "Partner
stations" parameter group is used.
Function: If there is no data traffic within the connection monitoring time, the CP sends a
keepalive to the telecontrol server.
Permitted range: 0 to 65535 s. Default: 180 s.
If you enter 0 (zero), the function is disabled.
●
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. Permitted range: 0 to 65535 s. Default: 1 s. If you enter
0 (zero), the function is deactivated. The monitoring time is configured for the Ethernet
interface as the default for all TCP connections. The default value can be adapted
individually for each connection in "Partner stations".
●
Specifies the communications partner that establishes the connection (always the CP).
●
Number of the listener port of the telecontrol server.
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 communications partners of the CP for inter-station
communication. The communications partner is a CP in the partner S7 station.
Connections for inter-station communication run via the telecontrol server.
Note the special features when configuring the data points for inter-station communication in
the section Partner stations: Configuring the inter-station communication (Page 85).
The partner number is assigned by the system. It is required during data point configuration
to assign data points to their communications partners.
You specify the partner CP for inter-station communication with the parameters "Project",
"Station" and "Slot".
Here, enter the project number of the CP in the partner station.
You will find the parameter in the parameter group "Security > CP identification" on the
partner CP.
Here, enter the station number of the CP in the partner station.
You will find the parameter in the parameter group "Security > CP identification" on the
partner CP.
4.15 STEP 7 configuration of individual parameters
Here, enter the slot number of the CP in the partner station.
You will find the parameter in the parameter group "General" on the partner CP.
When enabled, 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.
If the option is disabled, even frames for events are only stored in the image memory of the
CP; in other words if there are problems on the connection older values are overwritten by
new values.
The access ID of the partner CP is displayed here.
The Access ID (DWORD) is formed from the hexadecimal values of project number, station
number and slot:
4.15 STEP 7 configuration of individual parameters
The parameter group is displayed as soon as telecontrol communication is enabled.
●
Here, you set the size of the send buffer for events.
A maximum of 64000 events divided up equally among the communications partners can
be buffered.
You will find a description of the send buffer and the functions involved in the section
Process image, type of transmission, event classes, triggers (Page 51).
In the parameter group "CP diagnostics", you have the option of reading out advanced
diagnostics data from the CP using PLC tags.
●
If you want to use advanced CP diagnostics, you need to configure the "Diagnostics
trigger tag".
If the user program of the CPU sets the PLC tag "Diagnostics trigger tag" (BOOL) to 1,
the CP updates the values of the configured PLC tags for advanced diagnostics. After
writing the current values to the PLC tags for advanced diagnostics, the CP sets the
"Diagnostics trigger tag" to 0 signaling the CPU that the updated values can be read from
the PLC tags.
Reading out the following diagnostics data can be enabled selectively:
●
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.
●
PLC tag (data type String) for the current IP address of the CP.
●
PLC tag (data type UInt) for the signal quality of the local mobile wireless network as this
is displayed by the "SIGNAL QUALITY" LED.
●
PLC tag (data type INT) for the signal quality of the local mobile wireless network as a
dBm value.
4.15 STEP 7 configuration of individual parameters
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.
To import the certificate, follow these steps:
1. Save the certificate from your e-mail service provider in the file system of the engineering
station.
2. In STEP 7, select the entry "Global security settings > Certificate manager" in the "Project
tree".
3. Change to the "Trusted certificates and root certification authorities" tab.
4. Select any row in the table "Trusted certificates and root certification authorities".
5. Select the "Import" entry in the shortcut menu.
6. In the dialog that follows, select the required certificate.
When a data point is created, the name of the PLC tag is initially adopted. In the "General"
tab of the data point you can change the name of the data point.
When assigning the name, only the following ASCII characters can be used: ASCII
characters 0x20 ... 0x7e with the exception of the characters listed below.
The following characters are forbidden since they do not adhere to the syntax rules of TCSB
for OPC items:
Threshold value trigger: How the integrattion calculation works
The calculation cycle
4.15 STEP 7 configuration of individual parameters
Analog inputs that are configured as an event are processed on the CP in the following
sequence:
1. Reading the data from the input area of the CPU
2. Analog value preprocessing (part 1)
Processing involves the following steps:
– Mean value generation
if configured: Calculation and then continue at point 4.
if not configured: Continue with "Unipolar transfer".
– Unipolar transfer (if configured)
– Error suppression time (if configured)
– Smoothing (if configured)
3. Threshold value calculation (if Threshold value trigger is configured)
4. Analog value preprocessing (part 2)
– Set limit value 'low' / Set limit value 'high' (if configured)
5. Storage of the value in the send buffer
Transfer of the value to the partner if trigger and threshold value conditions are met.
The CP calculates the value for the threshold value trigger after the analog value
preprocessing, refer to the section Analog value preprocessing (Page 79).
To calculate the threshold value trigger, the integration method is used.
In the integration threshold value calculation, it is not the absolute value of the deviation of
the process value from the last stored value that is evaluated but rather the amount of the
integrated deviation.
The integration threshold value calculation works with a cyclic comparison of the integrated
current value with the last stored value. The calculation cycle in which the two values are
compared is 500 milliseconds.
(Note: The calculation cycle must not be confused with the scan cycle of the CPU memory
areas).
The deviations of the current process value are totaled in each calculation cycle. The trigger
is set only when the totaled value reaches the configured value of the threshold value trigger
and a new process value is entered in the send buffer.
4.15 STEP 7 configuration of individual parameters
The method is explained based on the following example in which a threshold value of 2.0 is
configured.
Table 4- 3 Example of the integration calculation of a threshold value configured with 2.0
0.5 20.3 +0.3 0.3
In this example, a value of 2.0 was configured for the threshold value trigger.
With the changes in the process value shown in the example, the threshold value trigger
fires twice, if the value 2.0 is reached:
● At the time 3.5 s: The value of the integrated deviation is at 2.0. The new process value
stored in the send buffer is 20.5.
● At the time 6.0 s: The value of the integrated deviation is at 2.1. The new process value
stored in the send buffer is 19.9.
In this example, if a deviation of the process value of approximately 0.5 should fire the
trigger, then with the behavior of the process value shown here a threshold value of
approximately 1.5 ... 2.5 would need to be configured.
CPs with data point configuration support analog value preprocessing with some or all of the
functions described below.
If you have configured an error suppression time and then enable mean value generation,
the value of the error suppression time is grayed out but no longer used. If
generation is enabled, the error suppression time is set to 0 (zero) internally.
4.15 STEP 7 configuration of individual parameters
With unipolar transfer, negative values are corrected to zero. This can be desirable if values
from the underrange should not be transferred as real measured values.
Exception: The value -32768 / 8000
Unipolar transfer cannot be configured at the same time as mean value generation.
With this parameter, acquired analog values are transferred as mean values.
The current values of an analog data point are acquired cyclically and totaled. The number of
acquired values per time unit depends on the read cycle of the CPU and the CPU scan cycle
of the CP. The mean value is calculated from the accumulated values as soon as the
transfer is triggered by a time trigger. Following this, the accumulation starts again so that
the next mean value can be calculated.
The mean value can also be calculated if the transmission of the analog value message is
triggered by a request from the communications partner. The duration of the mean value
calculation period is then the time from the last transmission (for example triggered by the
trigger) to the time of the request. Once again, the accumulation restarts so that the next
mean value can be calculated.
Acquisition of a value in the overflow or underflow range results in the mean calculation
being stopped immediately. The value 32767 / 7FFF
invalid mean value for the current mean value calculation period and sent when the next
analog value message is triggered. The calculation of a new mean value is then started. If
the analog value remains in the overflow or underflow range, this new value is again saved
immediately as an invalid mean value and sent when the next frame is triggered.
for wire break of live zero inputs is transferred.
Recommendation for finished values that were preprocessed by the CPU:
4.15 STEP 7 configuration of individual parameters
Analog values that fluctuate quickly can be evened out using the smoothing function.
The smoothing factors are calculated according to the following formula as with S7 analog
input modules.
where
= smoothed value in the current cycle
y
n
= value acquired in the current cycle n
x
n
k = smoothing factor
The following values can be configured for the module as the smoothing factor.
● 1 = No smoothing
● 4 = Weak smoothing
● 32 = Medium smoothing
● 64 = Strong smoothing
The smoothing factor cannot be configured at the same time as mean value generation.
An analog value in the overflow range (32767 / 7FFFh) or underflow range (-32768 / 8000h)
is not transferred for the duration of the fault suppression time. This also applies to live zero
inputs. The value in the overflow/underflow range is only sent after the fault suppression time
has elapsed, if it is still pending.
If the value returns to the measuring range before the fault suppression time elapses, the
current value is transferred immediately.
A typical use case for this parameter is the suppression of peak current values when starting
up powerful motors that would otherwise be signaled to the control center as a disruption.
The suppression is adjusted to analog values that are acquired by the S7 analog input
modules as raw values. These modules return the specified values for the overflow or
underflow range for all input ranges (also for live zero inputs).
The fault suppression time cannot be configured at the same time as mean value generation.
If the CPU makes preprocessed finished values available in bit memory or in a data block,
suppression is only possible or useful if these finished values also adopt the values listed
above 32767 / 7FFF
case, the parameter should not be enabled for preprocessed values.
or -32768 / 8000h in the overflow or underflow range. If this is not the
4.15 STEP 7 configuration of individual parameters
In these two input boxes, you can set a limit value in the direction of the start of the
measuring range or in the direction of the end of the measuring range. You can also
evaluate the limit values, for example as the start or end of the measuring range.
If the limit value is overshot or undershot, the status identifier "OVER_RANGE" of the data
point is set. This status identifiers are described in the section Status IDs of data points
(Page 54).
The "OVER_RANGE" bit of the status identifier of the data point is set as follows when the
relevant analog value is transferred:
● Limit value 'high':
– If the limit value is exceeded: OVER_RANGE = 1
– If the value falls below the limit value: OVER_RANGE = 0
● Limit value 'low':
– If the value falls below the limit value : OVER_RANGE = 1
– If the value then exceeds the limit value: OVER_RANGE = 0
● Configuration of the threshold trigger for this data point
● PLC tag in the bit memory operand area or data area
The analog value data point must be linked to a PLC tag in the bit memory or data area
(data block). For hardware modules (input operand area) limit value configuration is not
possible.
The configuration of limit values is pointless for measured values that have already been
preprocessed on the CPU.
If the analog value fluctuates quickly, it may be useful to smooth the analog value first if limit
values are configured. If the analog value fluctuates close to a limit value for a longer period
of time, with a smoothed value you avoid a status change each time the value exceeds/falls
below the limit value and so triggers a transfer.
Partner stations: Configuring the inter-station communication
Options for specifying the communications partner
Telecontrol server activated / Enable partner for inter-station communication
Partner number for inter-station communication:
Data point index
Note:
4.15 STEP 7 configuration of individual parameters
If no partner was enabled for inter-station communication, the "Telecontrol server activated"
option is selected automatically. In this case, the telecontrol server is the only
communications partner of the data point.
If instead a CP of an S7 station should be the communications partner of the data point,
select the option "Activate partner for inter-station communication".
The telecontrol server and a CP in an S7 station cannot be selected as the partner at the
same time.
Specify the partner CP for inter-station communication for this data point by selecting the
partner number from the drop-down list.
The partners you specified in the table of the "Partner stations" > "Partner for inter-station
communication" can be selected. The access ID of the relevant partner is shown in brackets.
Index of the corresponding data point on the communications partner.
● The data pair of the sending and receiving CP must have an identical data point index. A
receiving data point of CP 2 corresponds to a sending data point of CP 1 with the same
data point index.
● For the opposite communications direction, a second pair of data points must be created:
A sending data point of CP 2 corresponds to the receiving data point of CP 1. Once
again, both have an identical data point index.
4.15 STEP 7 configuration of individual parameters
If important events occur, the CP can send SMS messages. The recipient can be a mobile
phone or an S7-1200.
You configure the SMS message in STEP 7 in the data point and message configuration.
You can find this using the project tree:
Project > directory of the relevant station > Local modules > CP
For the view in STEP 7, refer to the section Configuring data points and messages
(Page 47).
You will find the character set supported for the text of the SMS message in the section
Programming SMS messages via OUC (Page 93).
If important events occur, the CP can send e-mails. The recipient can be a PC with an
Internet connection or an S7-1200.
You configure the e-mails in STEP 7 in the data point and message configuration. You can
find this using the project tree:
Project > directory of the relevant station > Local modules > CP
For the view in STEP 7, refer to the section Configuring data points and messages
(Page 47).
One of the following events triggers sending of the message:
● CPU changes to STOP.
● CPU changes to RUN.
● The connection to the partner is interrupted.
● The connection to the partner is re-established.
● Connection establishment has failed.
● Weak mobile wireless network (signal quality)
● A trigger signal is fired.
For the trigger signal to send the message, 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 message.
If the memory area of the trigger bit is in the bit memory or in a data block, the trigger bit
is reset to zero when the message is sent.
Text of the message optionally with the value of a PLC tag
Enable status identifier / External status
Status
Meaning
0000
Transfer completed free of errors
4.15 STEP 7 configuration of individual parameters
Remember the following requirements in the CP configuration for the transfer of messages:
● Enabling telecontrol communication ("Communication types") parameter group
● Activating security functions
● Additionally for e-mails: Configuring the "E-mail configuration" parameter group
To do this, you require the following information:
– Access data of the SMTP server: Address, port number, user name, password
When using STARTTLS or SSL/TLS: Certificate of the e-mail service provider
– Email address of the recipient
In the text of every message, you can not only transfer the configured text but also the value
of a PLC tag. To do this enter "$$" as a placeholder for the value to be sent in the message
text. For the configuration, refer to the next section "Include value".
If this option is enabled in STEP 7, a status is output on the CP that provides information
about the processing status of the sent message. The status is written to a PLC tag of the
type DWORD that is specified in the "External status" box.
The meaning of the statuses is as follows:
Table 4- 4 SMS: Meaning of the status ID output in hexadecimal format
8001 Error in the transfer, possible causes:
• SIM card invalid
• No network
• Wrong destination phone number (number not reachable)
No TCP/IP connection could be established to the SMTP server.
8405
The SMTP server has denied the login request.
SMTP client.
8407
Request to use SSL was denied.
8408
The client could not obtain a socket for creating a TCP/IP connection to the mail server.
reset the connection or the connection aborted.
terminated the connection or the connection was aborted.
8411
Sending the e-mail failed. Cause: There was not enough memory space for sending.
8412
The configured DNS server could not resolve specified domain name.
8413
Due to an internal error in the DNS subsystem, the domain name could not be resolved.
8414
An empty character string was specified as the domain name.
8415
An internal error occurred in the cURL module. Execution was aborted.
8416
An internal error occurred in the SMTP module. Execution was aborted.
aborted.
8418
Sending the e-mail was aborted. Possible cause: Execution time exceeded.
8419
The channel was interrupted and cannot be used before the connection is terminated.
8420
Certificate chain from the server could not be verified with the root certificate of the CP.
8421
Internal error occurred. Execution was stopped.
8450
Action not executed: Mailbox not available / unreachable. Try again later.
SMTP protocol.
Try sending e-mails without authentication (no user name).
4.15 STEP 7 configuration of individual parameters
Table 4- 5 E-mails: Meaning of the status ID output in hexadecimal format
82xx Other error message from the e-mail server
Apart from the leading "8", the status corresponds to the three-digit error number of the
SMTP protocol.
8401 No channel available
Possible cause: There is already an e-mail connection via the CP. A second connection
8406 An internal SSL error or a problem with the structure of the certificate was detected by the
8409 It is not possible to write via the connection. Possible cause: The communications partner
8410 It is not possible to read via the connection. Possible cause: The communications partner
8417 Requests to SMTP on a channel already being used or invalid channel ID. Execution was
84xx Other error message from the e-mail server
Apart from the leading "8", the status corresponds to the three-digit error number of the
8500 Syntax error: Command unknown.
This also includes the error of having a command chain that is too long. The cause may be
that the e-mail server does not support the LOGIN authentication method.
8501 Syntax error. Check the following configuration data:
Apart from the leading "8", the status corresponds to the three-digit error number of the
If you enable the option "Include value", the CP sends a value for the placeholder $$ from
the memory area of the CPU in the message. To do this, you configure a PLC tag whose
value is integrated in the message.
The value is entered in the message text instead of the placeholder $$.
The Web server of the S7-1200 station is located in the CPU. Via the LAN interface of the
CP, you have access to the Web server of the CPU.
Access using HTTPS: When there is secure access (HTTPS) to the Web server using the IP
address of the CP, the SSL certificate of the CPU is displayed.
Using the program blocks for Open User Communication (OUC)
Note
Different program block versions
Note that in STEP 7 you cannot use different
Supported program blocks for OUC
The instructions (program blocks) listed below are required for direct communication
between S7 stations via the mobile wireless network.
In contrast to other communication types, Open User Communication does not need to be
enabled in the configuration of the CP because corresponding program blocks need to be
created for this. You will find details on the program blocks in the information system of
STEP 7.
To use the Open User Communication, the CP requires a fixed IP address to be assigned by
the mobile wireless network provider.
The following instructions in the specified minimum version are available for programming
Open User Communication:
● TSEND_C V3.0 / TRCV_C V3.0
Compact blocks for connection establishment/termination and sending / connection
establishment/termination and receiving
Transfer of data or SMS message
or
● TCON V4.0 / TDISCON V2.1
Connection establishment / connection termination
● TUSEND V4.0 / TURCV V4.0
Sending and receiving data via UDP
● TSEND V4.0 / TRCV V4.0
versions of a program block in a station.
– Sending and receiving data via TCP or ISOonTCP
– Sending and receiving SMS messages
● TMAIL_C V4.0
Sending e-mails
The program block can be found in STEP 7 in the "Instructions > Communication > Open
User Communication" window.
Connection descriptions in system data types (SDTs)
Creating an SDT for the data blocks
Using the SDT
TCON_Param
TADDR_Param
TCON_IP_RFC
TCON_Phone
TMail_V4
TMail_V6
Connection establishment and termination
Note
Connection abort
If an existing connection is aborted by the communications partner or due to disturbances on
the network, the connection must also be terminated by calling TDISCON. Make sure that
you take this into account in your programming.
5.1 Program blocks for OUC
For the connection description, the blocks listed above use the parameter CONNECT (or
MAIL_ADDR_PARAM with TMAIL_C). The connection description is stored in a data block
whose structure is specified by the system data type (SDT).
You create the SDT required for every connection description as a data block. You generate
the SDT type in STEP 7 by entering the name "TCON_Param" or "TCON_Phone" in the
"Data type" box manually in the declaration table of block instead of selecting an entry from
the "Data type" drop-down list. The corresponding SDT is then created with its parameters.
●
For transferring frames via TCP
●
For transferring frames via UDP
●
For transferring frames via ISO-on-TCP (direct communication between two S7-1200
stations)
●
For transferring SMS messages
●
For transferring e-mails addressing the e-mail server using an IPv4 address
●
For transferring e-mails addressing the e-mail server using an IPv6 address
You will find the description of the SDTs with their parameters in the STEP 7 information
system under the relevant name.
You will find notes on programming SMS messages in the section Programming SMS
messages via OUC (Page 93).
Connections are established using the program block TCON. Note that a separate program
block TCON must be called for each connection.
A separate connection must be established for each communications partner even if
identical blocks of data are being sent.
After a successful transfer of the data, a connection can be terminated. A connection is also
terminated by calling "TDISCON".
Transferring e-mails / SMS messages via OUC or telecontrol communication
Programming SMS messages
Sending SMS messages to one partner
Receiving SMS messages from one partner
Receiving SMS messages from several partners
Message text to be sent in the "DATA" parameter
Reading out the message text from the "DATA" parameter
5.2 Programming SMS messages via OUC
The event-driven sending of e-mails or SMS messages using telecontrol communication is
configured in STEP 7 in the message editor, refer to the section Messages (Page 86). No
program blocks are required for this.
You only require the program blocks and system data types (SDTs) described below to
transfer SMS messages using Open User Communication.
To do this, create the following blocks or system data types (alternatives):
● TCON + TDISCON + TSEND + TCON_PHONE
● TSEND_C + TCON_PHONE
To do this, create the following blocks or system data types (alternatives):
● TCON + TDISCON + TRCV + TCON_PHONE
● TRCV_C + TCON_PHONE
If you do not program a phone number in the "PhoneNumber" parameter of the
TCON_PHONE system data type, the CP cannot receive any SMS messages.
As an alternative, you can create a separate block set for each partner as described above
for 1 partner or a single block set with the following special feature in the TCON_PHONE
block:
If you enter an asterisk (*) after the phone number body in the "PhoneNumber" parameter of
the TCON_PHONE block, the asterisk acts as a placeholder for all authorized phone
numbers with this phone number body.
You configure the phone numbers authorized for access to the CP in STEP 7 in the
"Security" parameter group of the CP.
You enter the message text as a string in the "DATA" parameter of TSEND or TSEND_C.
A message can contain up to 160 characters. If the message text contains more than 160
characters, the text is distributed over two or more SMS messages.
To receive an SMS message, program the message text to be read out in the TRCV /
TRCV_C in the "DATA" parameter via a data block of the data type "Struct".
When creating this structure (DB of the data type "Struct"), no optimized block access can be
configured.
The structure should have a size of 194 bytes and the following structure to store the
relevant data of the received SMS message:
● DTL
12 bytes for the time stamp of the received SMS message (time stamp from the network)
● String[22]
String of 22 bytes for the phone number of the sender
● String[160]
String of 160 bytes for the message text
The SMS message text can contain max. 160 characters.
● Byte
Status of the SMS message:
– 0 = Invalid
1 = Unread
2 = Read
You can output up to 10 received SMS messages from the receive block by making the entry
"SMSSTORE" for the "PhoneNumber" parameter of TCON_PHONE.
In this case, you need to create an adequately large structure (1940 bytes) for the "DATA"
parameter of the receiving block to save the received data of 10 SMS messages. The
structure is then organized as follows:
● Received data SMS 1 (DTL, String[22], String[160], Byte)
● Received data SMS 2 (DTL, String[22], String[160], Byte)
... to
● Received data SMS 10 (DTL, String[22], String[160], Byte)
TC_CONFIG for changing configuration data of the CP
Meaning
Call interface in FBD representation
5.3 TC_CONFIG for changing configuration data of the CP
With the program block TC_CONFIG , you can modify parameters of a the CP configured in
STEP 7. The configured values are not overwritten retentively. The overwritten values
remain valid until TC_CONFIG is called again or until the station starts up again (cold restart
after cycling power).
If the STEP 7 configuration data of the CP needs to be changed permanently, the block
needs to be called again each time the station restarts (cold restart) or a modified project
must be downloaded to the station.
The CONFIG parameter points to the memory area with the configuration data. The
configuration data is stored in a data block (DB). The DB cannot be created with optimized
block access. The structure of the DB is specified by the system data type (SDT) IF_CONF.
The configuration data to be modified on the CP is put together as necessary in blocks in
IF_CONF "IF_CONF_..." for the individual parameters.
Parameters that are not intended to change as a result of the block are not entered in
IF_CONF. They retain the value configured in STEP 7.
For detailed information on programming IF_CONF, refer to the section IF_CONF: SDT for
the configuration data of the CP (Page 99).
The INTERFACE parameter references the name of the interface of the mobile wireless CP.
You will find the name of the interface in the STEP 7 project in the standard tag table of the
station in the "System constants" tab under the entry with the value of the "Hardware
identifier" of the CP.
Structure of the system data type IF_CONF for the TC_CONFIG program block
Creating the DB and the IF_CONF structures
5.4 IF_CONF: SDT for the configuration data of the CP
The CONFIG parameter of the TC_CONFIG program block references the memory area
containing the configuration data of the CP to be modified. The configuration data stored in a
data block is described as a structure of the IF_CONF system data type (SDT).
IF_CONF is made up of a header followed by fields that correspond to the parameters or
parameter areas of the CP in the device properties of the STEP 7 project.
The CP configuration data to be modified is collected together as IF_CONF fields.
Parameters that will not be modified are ignored in the IF_CONF structure and remain as
they were configured in the STEP 7 project.
You can create the parameters of the CP within the IF_CONF DB in one or more structures
each with one or more fields.
You will need to type in the data types of the fields using the keyboard. They are not
displayed in the selection list. The data types are not case-sensitive.
Follow the steps below to create IF_CONF:
1. Create a data block of the type "global DB" with block access "Standard".
2. Create a structure (data type "Struct") in the table of the parameter configuration of the
DB.
You can specify any name.
3. Under this structure add a header by assigning the name of the header and typing it in in
the cell of the data type "IF_CONF_Header".
The header of the structure and its three parameters (see below) is created.
4. Create a field for the first parameter to be changed by typing in the required data type (for
example "IF_CONF_APN") in the cell of the data type.
5. Repeat the last step for all parameters you want to change on the CP using the
TC_CONFIG instruction.
6. Finally, update the number of fields in the header in the "subfieldCnt" parameter.
The permanent configuration data is replaced by the parameter fields of IF_CONF.
5.4 IF_CONF: SDT for the configuration data of the CP
Table 5- 1 IF_CONF_Header
2 ... 3 fieldId UINT Field ID: Must always be 0.
Each field has the following general parameters:
● Id
This parameter identifies the field and must not be modified.
● Length
This parameter indicates the length of the field. The value serves as information.
Fields with strings and / or arrays have a variable length. Due to hidden bytes, the actual
length of fields can be greater than the sum of the displayed parameters.
● Mode
The following values are permitted to these parameters:
Table 5- 2 Values of "Mode"
1 Permanent validity of the configuration data
Not relevant for the CP
2 Temporary validity of the configuration data, including deleting of existing permanent